Bug 1600226 - Polari - "Freenode requires password" - my previously working account is now locked and I can't even send msg to reset my password.
Summary: Polari - "Freenode requires password" - my previously working account is now ...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: polari
Version: 28
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Florian Müllner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-11 18:12 UTC by Paweł
Modified: 2019-05-28 21:50 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-05-28 21:50:16 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Screenshot of a locked client (106.11 KB, image/png)
2018-07-11 18:12 UTC, Paweł
no flags Details

Description Paweł 2018-07-11 18:12:51 UTC
Created attachment 1458200 [details]
Screenshot of a locked client

Description of problem:
I've used Polari before (even today) with my Freenode registered account and it was identifying me automatically to Freenode network on startup - no problems. 

Now I can see a "key" icon next to the Freenode network tab, on the side panel and when I click it, it says "Freenode requires password". I've tried entering my password, but it failed (I'm not sure it's the right one, I don't use it much).

Anyway, all of a sudden autologin stopped working for Freenode account in Polari. I can't even send "/msg NickServ SENDPASS youraccountnamehere" to reset my password.

Version-Release number of selected component (if applicable):
3.28.0

How reproducible:
Always as of right now - tried rebooting.

Steps to Reproduce:
1. Open Polari with Freenode account configured, and auto-identify option enabled
2. Try to use it
3.

Actual results:
Not usable - account locked, can't reset password - literally unusable app.

Expected results:
Actually using this buggy IRC client with Freenode network

Additional info:
-

Comment 1 Paweł 2018-07-11 18:34:54 UTC
OK, I've tried resetting my password with Freenode WebChat, and it seems that my ISP's Proxy got banned for spam, and since I use it, I got banned from accessing Freenode also.

On another ISP it works fine, so it's not a Polari bug - sorry, my bad.

Comment 2 Ben Cotton 2019-05-02 21:19:40 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Ben Cotton 2019-05-28 21:50:16 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.