pidgin chat rooms break twice on network failure

Bug #257916 reported by njh
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: pidgin

Whenever the network drops out and returns, pidgin closes all the currently subscribed rooms and puts () around the room's name. Rather than resubscribing, these rooms become 'locked'. To rejoin the room the user has to perform these steps:
a) close the room tab
b) rejoin the room
c) reclose the room
d) rejoin the room

after step b the room appears to be there, but is actually non functional. The most reasonable behaviour would be to automatically rejoin rooms when th network returns.

njh@thestral:~$ lsb_release -rd
Description: Ubuntu 8.04.1
Release: 8.04
njh@thestral:~$ apt-cache policy pidgin
pidgin:
  Installed: 1:2.4.1-1ubuntu2.1
  Candidate: 1:2.4.1-1ubuntu2.1
  Version table:
 *** 1:2.4.1-1ubuntu2.1 0
        500 http://us.archive.ubuntu.com hardy-updates/main Packages
        100 /var/lib/dpkg/status
     1:2.4.1-1ubuntu2 0
        500 http://us.archive.ubuntu.com hardy/main Packages

Revision history for this message
njh (njh-njhurst) wrote :

To recreate, ifdown/ifup is sufficient.

Revision history for this message
Magnus S (magnuss) wrote :

Hi, thanks for the report. Are you still able to reproduce this bug? If so, please do a backtrace (https://wiki.ubuntu.com/Backtrace), reproduce, and attach to this report.

Also run pidgin in debug mode (pidgin --debug > ~/pidgin-debug.txt), reproduce, and attach the file it creates in your home directory. Feel free to mask sensitive information, if any.

Thanks in advance.
//magnus

Changed in pidgin:
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in pidgin:
status: Incomplete → Invalid
Revision history for this message
Tim Cole (tcole) wrote :

This is neither a crash nor a hang, so a backtrace is not relevant here.

Changed in pidgin:
status: Invalid → Incomplete
status: Incomplete → New
Revision history for this message
Tim Cole (tcole) wrote :

(I can also reproduce the bug, by the way.)

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Do you get the same with Lucid or Maverick? Thanks in advance.

Changed in pidgin (Ubuntu):
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in pidgin (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.