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 760039 - Can’t join a re-join a redirected room
Can’t join a re-join a redirected room
Status: RESOLVED DUPLICATE of bug 758267
Product: polari
Classification: Applications
Component: general
3.18.x
Other Linux
: Normal major
: ---
Assigned To: Polari maintainers
Polari maintainers
: 766029 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2015-12-31 22:34 UTC by Daniel Aleksandersen
Modified: 2016-05-15 07:26 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Daniel Aleksandersen 2015-12-31 22:34:48 UTC 
Steps to reproduce:
1. Join chat.freenode.net (but don’t identify with NickServe!)
2. Joing the #fedora room

You’ll get an empty room with no participants for #fedora, and you’ll also join a second room called #fedora-unregistered where you’re told to identify with NickServe and then try to join #fedora again.

3. Identify with NickServe
4. Click on the #fedora room in the sidebar

Nothing happens. There is no way to rejoin.

5. Right-click on Fedora and choose to Leave channel
6. Join #fedora again using the Join channel dialog

Expected: You should be able to rejoin #fedora once you’ve done as you’re told in #fedora-unregistered.

Actual: Fedora will always show up with no members and you can’t join the room.

Notes:
As the list of room is re-joined automatically when you start Polari, this bug becomes very annoying very fast. Users must remember to leave #fedora before exiting Polari to be able to identify with NickServe first and then join #fedora afterwards.

System info:
Polari 3.18.1 as distributed with 64-bit Fedora 23.
Comment 1 Juraj Fiala 2016-05-15 05:42:42 UTC 
*** Bug 766029 has been marked as a duplicate of this bug. ***
Comment 2 Juraj Fiala 2016-05-15 05:54:46 UTC 
This happens to me too,  it used to work once but oddly it stopped working.

Also what might be related:

1. I used to have two manually added servers, GNOME and Freenode. 3.20 came out and I deleted the manually added Freenode and added it with the recommended preset values. I didn't do the same for GNOME because I had saved history there I wanted to keep. Joining the Archlinux room used to work at the time.
2. When the Archlinux room stopped working I tried deleting and readding it, but I added it to GNOME by mistake (which it oddly completed), and I got a room (can't remember whether locked or not) with history from the Archlinux room from the old Freenode connection. The title was just plain 'archlinux'
3. Now I cannot connect to GNOME, it's just loading fail loading fail loading FAIL in quick succession. All the rooms are locked there.
Comment 3 Juraj Fiala 2016-05-15 05:55:33 UTC 
polari 3.20.2-1 on Arch.
Comment 4 Florian Müllner 2016-05-15 07:26:34 UTC 
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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