the gnome-panel freezes when selecting "Quit..." from the "System" menu

Bug #55742 reported by Ryan Johns
2
Affects Status Importance Assigned to Milestone
gnome-session (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-panel

The gnome-panel freezes when I try to logout/reboot/shutdown by selected either System->Quit... or by clicking the "Quit" panel applet. I have used several different Dapper installs in the past with no problems, however, with my current install this freeze occurs every time I try to quit the gnome session. I simply run 'killall gnome-panel' from the command line to allow gnome to restart the panel and everything behaves normally except when again trying to quit. I tried reinstalling dapper completely without saving any files from the / or /home partitions just to be sure it wasn't a corrupted conf file or something like that. I tried removing everything from the panel but still experienced the hang. I made a backtrace and a strace but unfortunately don't think they will be very useful. I'm running the most up-to-date standard dapper install on an x86. The only non dapper software installed is gaim 2.0.0beta3, firefox 1.5.0.6 (mozilla build), gnucash 2.0.1, and azureus 2.4.0.2. Please let me know if there is any other information/debugging procedures you need from me. Thanks so much.

Revision history for this message
Ryan Johns (ryanjohns) wrote :
Revision history for this message
Ryan Johns (ryanjohns) wrote :
description: updated
Revision history for this message
Daniel Holbach (dholbach) wrote :

Thanks for your bug report. Can you check if the 'lo' interface is configured and for the date that is set? Are there any processes like applets pulling 100% CPU or something else ominous?

Changed in gnome-panel:
assignee: nobody → desktop-bugs
importance: Untriaged → Medium
status: Unconfirmed → Needs Info
Revision history for this message
Ryan Johns (ryanjohns) wrote :

The lo interface is configured but I'm not sure what you mean by "and for the date that is set." All other processes/applets seem fine and my CPU is completely idle.

output for 'ifconfig lo':
lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:538 errors:0 dropped:0 overruns:0 frame:0
          TX packets:538 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:85299 (83.2 KiB) TX bytes:85299 (83.2 KiB)

Revision history for this message
Ryan Johns (ryanjohns) wrote :

I figured out the problem. I had written a script that uses iptables to setup a basic firewall. I had set the default policy on the input chain to drop and forgotten to allow traffic on the 'lo' interface. I feel like an idiot for not figuring this one out sooner but thanks Daniel for starting me on the right track. This bug should be closed since it is not actually a bug just me being stupid. :-)

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for the bug update. That's probably the same issue than bug #26419 then, marking as duplicate.

Changed in gnome-panel:
status: Needs Info → Rejected
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.