GNOME Bugzilla – Bug 159762
Gnome-panel crashes and restarts when trying to change its properties or an application launcher's properties
Last modified: 2005-05-25 09:55:22 UTC
Distribution: Fedora Core release 3 (Heidelberg)
Version: GNOME2.8.0 2.8.x
Gnome-Distributor: Red Hat, Inc
Synopsis: Gnome-panel crashes and restarts when trying to change its properties or an application launcher's properties
BugBuddy-GnomeVersion: 2.0 (2.8.0)
Description of the crash:
When right-clicking on an application launcher icon or on the panel
itself and selecting 'properties' from the drop-down menu, the
'Launcher/panel properties' box shows up normally, and changes can be
made. Upon clicking 'close', however, the panel crashes, displaying the
error box saying 'The Appication "gnome-panel" has quit unexpectedly.'
Upon closing that dialog box the panel restarts, and any changes I made
are retained. A dialog box also appears saying 'I've detected a panel
already running, and will now exit.' The dialog reappears after clicking
Steps to reproduce the crash:
1. Right click on an application launcher or the panel.
2. Click 'properties'.
3. Close the properties dialog box.
The panel should not crash and restart.
How often does this happen?
Every time the above steps are carried out.
This does not happen when changing the properties of anything else on
the panel -- only application launchers and the panel itself. A related
issue may be the following: it is impossible to change the icon for an
application launcher; attempting to do so will crash the 'Browse icons'
dialog. All other setting can be changed.
Backtrace was generated from '/usr/bin/gnome-panel'
Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -151148320 (LWP 4761)]
0x005677a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
(Thread -151148320 (LWP 4761))
------- Bug moved to this database by firstname.lastname@example.org 2004-11-28 16:19 -------
Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "gnome-panel".
Setting to default milestone for this product, '---'
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
This bug either had no qa contact or an invalid one.
I suppose you're running with accessibility support enabled.
Btw, it looks similar to bugs 158408 & 159745
I have neither keyboard accessibility nor assistive technology support enabled,
if that's what you mean.
The relation is created by the call to Add-relation in libgalde, even if
accessibility is not enabled.
I am unable to reproduce this so I have no idea what is going wrong.
Padraig: is this bug useful for you or is there a way to get more informations?
I would like to know the versions of atk and libglade which has been used. Then
I might be able to reproduce.
Marking as NEEDINFO until we get David's answer.
libglade is 2.4.0. atk is 1.8.0.
It looks like the problem occurs when deleting the GnomeFileEntry in the
I am not seeing the crash so cannot analyse any further.
It looks like the crash occurs even when accessibility support is not enabled as
relations are created even in this case.
Padraig: is this bug useful or should we close it?
I do not think that it should be closed.
It also seems very similar to bug 170346.
I am getting this crash in Fedora Core 3 if I do the following:
Prerequisites: normal Gnome desktop (top panel and bottom panel) with several
application launchers, screenshot applet and gnome-monitor running.
1) Make your top panel slightly transparent
2) Right-click your desktop to change your background
3) Highlight a different background than the one you currently have (which
changes your current background) from within the wallpaper selector
4) Do this again, or twice (or, rapidly highlight different wallpapers)
5) Gnome-panel crashes approximately six times and when the dialogues go away,
gnome-panel is no longer running. You will have to restart it manually.
Forgive me if this isn't the right place to put this comment; I've never
submitted a bug before.
Brian: this is bug #146075 and this is fixed in GNOME 2.10.0.
*** This bug has been marked as a duplicate of 146075 ***