After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 759021 - Polari can't identify nickname to freenode on startup
Polari can't identify nickname to freenode on startup
Status: RESOLVED DUPLICATE of bug 709982
Product: polari
Classification: Applications
Component: general
3.18.x
Other Linux
: Normal normal
: ---
Assigned To: Polari maintainers
Polari maintainers
Depends on:
Blocks:
 
 
Reported: 2015-12-04 12:40 UTC by Paweł
Modified: 2016-02-24 09:22 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Paweł 2015-12-04 12:40:40 UTC 
After I run Polari, it shows up, brings last used irc rooms, with history of chat, but I can't input anything. There's a circle, like when refreshing a page in firefox next to serwer name.

After closing, and starting it again, I've got immediete information, that I'm identified and I can type.
Comment 1 Paweł 2016-02-23 14:49:18 UTC 
Now the status has changed: no matter what I do (open, close, reopen and so on) - it does not register my nickname with freenode. 

Since Polari does not support "/msg" I can only go to settings and try to input my password for the irc account again. Which at least once worked, but Polari still won't register at startup.
Comment 2 Florian Müllner 2016-02-23 22:09:51 UTC 
(In reply to Paweł from comment #1)
> Since Polari does not support "/msg"

Well, you *could* use "/query" instead ...
Comment 3 Paweł 2016-02-24 08:45:13 UTC 
(In reply to Florian Müllner from comment #2)
> (In reply to Paweł from comment #1)
> > Since Polari does not support "/msg"
> 
> Well, you *could* use "/query" instead ...

Sure, it works, thanks. But the main problem remains - Polari does not identify nickname at startup.
Comment 4 Florian Müllner 2016-02-24 09:22:39 UTC 
Yes, there's no nickserv support for the time being.

*** This bug has been marked as a duplicate of bug 709982 ***