Dialog that notifies of an applets death doesn't close properly

Bug #8240 reported by Nathan Howell
8
Affects Status Importance Assigned to Milestone
gnome-panel (Ubuntu)
Fix Released
Medium
Sebastien Bacher

Bug Description

Here's a way I've been able to reproduce this one.

- Add the Disk Mounter applet to the panel.
- Right click on the applet. Choose Preferences.
- Close the Preferences dialog (via Close)
- Remove the applet from the panel. The following dialog will appear:

The "Disk Mounter" applet appears to have died unexpectedly.

Do you want to reload this applet?

(If you choose not to reload it at this time you can always add it by right
clicking on the panel and clicking on the "Add to Panel" submenu)

- Neither the No or Yes button will close the dialog or reload the applet.

I've seen this with another applet as well, but can't remember now which it was,
possibly the gnome-pilot applet.

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

Could you paste the result of "/usr/bin/gdmflexiserver -a -c QUERY_LOGOUT_ACTION" ?

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

oups, sorry, comments on the wrong bug report.

applets doesn't crash here. any chance to backtrace them ?

basically:
- $ apt-get install gdb
- "$ gdb /usr/lib/gnome-applets/drivemount_applet2" in a gnome-terminal
(gdb) r
- the procedure you describe before
- "bt" in the gnome-terminal with gdb after the crash

Revision history for this message
Nathan Howell (neh) wrote :

No real info came from that. A lot of (no debugging symbols found) messages,
program exited normally, and no stack from the bt.

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

You get "The "Disk Mounter" applet appears to have died unexpectedly." and the
program exits normally ? That's weird ...

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

To be clear. You've run the applet from a gnome-terminal in gdb, then add it to
the panel, repeted the procedure and you don't get a crash anymore ? So the bug
is fixed ?

Revision history for this message
Nathan Howell (neh) wrote :

When I ran the applet in gdb, the applet appeared to exit normally, but I still
got the error dialog as described. I'm not sure the applet was ever crashing, it
seemed to be that the panel was confused. I've just tried it again, and can't
get that dialog to come up in similar situations any more.

I guess there were/are two bugs here:

1. The panel mistakenly thinking an applet had crashed.
2. The dialog notifying the user of an applet crash won't close when either
button on it is pressed.

The second bug may still be there, but I haven't been able to recreate the first
one in order to find out.

Revision history for this message
Vincent Untz (vuntz) wrote :

Nathan: were you using gnome-panel 2.8.0 or a previous release? There was a
similar bug reported on b.g.o, and it has been fixed.

> - Neither the No or Yes button will close the dialog or reload the applet.

Was the panel freezed? Or could you still use it?

Revision history for this message
Nathan Howell (neh) wrote :

The panel was fine. I could close the dialog with the close button (X) and keep
on going. I don't know exactly which version of gnome-panel it was, at least
2.8.0, IIRC. It's whatever was being installed when I reported the bug.

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

(In reply to comment #8)
> The panel was fine. I could close the dialog with the close button (X) and keep
> on going. I don't know exactly which version of gnome-panel it was, at least
> 2.8.0, IIRC. It's whatever was being installed when I reported the bug.

The current package was 2.8.0 in the moment of the bug report.
BTW do you still have the problem (you are using the past in this comment ...)

Revision history for this message
Nathan Howell (neh) wrote :

Comment #6 describes the current behaviour.

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

seems to be fixed, I'm closing it. Feel free to reopen it that happens again.

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.