GNOME Bugzilla – Bug 419271
crash in Gimmie: Installing an RPM packag...
Last modified: 2007-10-08 05:28:54 UTC
What were you doing when the application crashed? Installing an RPM package. Happens when installing or installing any graphical application, so likely in the %post - either to do with updating the system menus or the desktop entry cache. Distribution: Mandriva Linux release 2007.1 (Cooker) for i586 Gnome Release: 2.18.0 2007-03-15 (Mandriva) BugBuddy Version: 2.18.0 System: Linux 2.6.20.3-tmb-desktop-1mdvsmp #1 SMP Wed Mar 14 03:02:53 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Tango Memory status: size: 88039424 vsize: 88039424 resident: 29868032 share: 14823424 rss: 29868032 rss_rlim: 4294967295 CPU usage: start_time: 1174126255 rtime: 164 utime: 156 stime: 8 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gimmie' (no debugging symbols found) Using host libthread_db library "/lib/i686/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1212111152 (LWP 384)] (no debugging symbols found) 0xb7fb2410 in __kernel_vsyscall ()
+ Trace 119356
Thread 1 (Thread -1212111152 (LWP 384))
----------- .xsession-errors (58745 sec old) --------------------- *** Reloading TopicRunningList: Active Conversations *** Window startup-id matches launcher path: file:///usr/share/applications/gaim.desktop *** Window startup-id matches launcher path: file:///usr/share/applications/mandriva-mozilla-firefox.desktop *** Window startup-id matches launcher path: file:///usr/share/applications/evolution.desktop *** Window startup-id matches launcher path: file:///usr/share/applications/xchat-gnome.desktop *** Window startup-id matches launcher path: file:///usr/share/applications/revelation.desktop *** Window startup-id matches launcher path: file:///usr/share/applications/gnome-terminal.desktop *** Reloading TopicRunningList: Computer Running Source *** Window startup-id matches launcher path: file:///usr/share/applications/gaim.desktop *** Window startup-id matches launcher path: file:///usr/share/applications/mandriva-mozilla-firefox.desktop *** Window startup-id matches launcher path: file:///usr/share/applications/evolution.desktop *** Window startup-id matches launcher path: file:///usr/share/applications/xchat-gnome.desktop *** Window startup-id matches launcher path: file:///usr/share/applications/revelation.desktop *** Window startup-id matches launcher path: file:///usr/share/applications/gnome-terminal. ...Too much output, ignoring rest... --------------------------------------------------
This is a regression - it doesn't happen with 0.2.4. As I said in the automated report, it happens whenever installing or removing a graphical application. In Mandriva, such applications by policy run a couple of macros to update the system menus and the .desktop files cache in %post and %postun, so I suspect this is when the crash happens.
Okay, I attempted a fix in SVN change #367. Can you please give it a try, and let me know how it goes? Closing for now...
Nope. Still crashes. Updated trace: Distribution: Mandriva Linux release 2007.1 (Cooker) for i586 Gnome Release: 2.18.0 2007-03-15 (Mandriva) BugBuddy Version: 2.18.0 System: Linux 2.6.20.3-tmb-desktop-1mdvsmp #1 SMP Wed Mar 14 03:02:53 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Tango Memory status: size: 87220224 vsize: 87220224 resident: 29216768 share: 14970880 rss: 29216768 rss_rlim: 4294967295 CPU usage: start_time: 1174192118 rtime: 138 utime: 129 stime: 9 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gimmie' (no debugging symbols found) Using host libthread_db library "/lib/i686/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1212868912 (LWP 31164)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xb7efa410 in __kernel_vsyscall ()
+ Trace 119627
Thread 1 (Thread -1212868912 (LWP 31164))
----------- .xsession-errors (38 sec old) --------------------- *** Window startup-id matches launcher path: file:///usr/share/applications/revelation.desktop *** Window class matches launcher command: gnome-terminal == gnome-terminal *** Window startup-id matches launcher path: file:///usr/share/applications/mandriva-mozilla-firefox.desktop *** Window class matches launcher command: nautilus == nautilus --no-desktop --browser %U *** Window startup-id matches launcher path: file:///usr/share/applications/xchat-gnome.desktop *** Reloading TopicRunningList: Running Applications *** Reloading TopicRunningList: Opened Documents *** Reloading TopicRunningList: Active Conversations *** Window startup-id matches launcher path: file:///usr/share/applications/evolution.desktop *** Window startup-id matches launcher path: file:///usr/share/applications/revelation.desktop *** Window class matches launcher command: gnome-terminal == gnome-terminal *** Window startup-id matches launcher path: file:///usr/share/applications/mandriva-mozilla-firefox.desktop *** Window class matches launcher command: nautilus == nautilus --no-desktop --browser %U *** Window startup-id matches launcher path: file:///usr/share/applications/xchat-gnome.desktop *** Reloading TopicRunningList: Computer Running Source --------------------------------------------------
Whoops, I'm sorry: didn't have -debug installed. Here's the trace with -debug installed. Distribution: Mandriva Linux release 2007.1 (Cooker) for i586 Gnome Release: 2.18.0 2007-03-15 (Mandriva) BugBuddy Version: 2.18.0 System: Linux 2.6.20.3-tmb-desktop-1mdvsmp #1 SMP Wed Mar 14 03:02:53 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Tango Memory status: size: 87846912 vsize: 87846912 resident: 30220288 share: 14843904 rss: 30220288 rss_rlim: 4294967295 CPU usage: start_time: 1174192270 rtime: 187 utime: 179 stime: 8 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gimmie' (no debugging symbols found) Using host libthread_db library "/lib/i686/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1212868912 (LWP 31356)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xb7efa410 in __kernel_vsyscall ()
+ Trace 119628
Thread 1 (Thread -1212868912 (LWP 31356))
----------- .xsession-errors (188 sec old) --------------------- *** Window startup-id matches launcher path: file:///usr/share/applications/revelation.desktop *** Window class matches launcher command: gnome-terminal == gnome-terminal *** Window startup-id matches launcher path: file:///usr/share/applications/mandriva-mozilla-firefox.desktop *** Window class matches launcher command: nautilus == nautilus --no-desktop --browser %U *** Window startup-id matches launcher path: file:///usr/share/applications/xchat-gnome.desktop *** Reloading TopicRunningList: Running Applications *** Reloading TopicRunningList: Opened Documents *** Reloading TopicRunningList: Active Conversations *** Window startup-id matches launcher path: file:///usr/share/applications/evolution.desktop *** Window startup-id matches launcher path: file:///usr/share/applications/revelation.desktop *** Window class matches launcher command: gnome-terminal == gnome-terminal *** Window startup-id matches launcher path: file:///usr/share/applications/mandriva-mozilla-firefox.desktop *** Window class matches launcher command: nautilus == nautilus --no-desktop --browser %U *** Window startup-id matches launcher path: file:///usr/share/applications/xchat-gnome.desktop *** Reloading TopicRunningList: Computer Running Source --------------------------------------------------
*** Bug 419815 has been marked as a duplicate of this bug. ***
*** Bug 419818 has been marked as a duplicate of this bug. ***
*** Bug 419878 has been marked as a duplicate of this bug. ***
*** Bug 420030 has been marked as a duplicate of this bug. ***
*** Bug 420118 has been marked as a duplicate of this bug. ***
*** Bug 420124 has been marked as a duplicate of this bug. ***
*** Bug 420530 has been marked as a duplicate of this bug. ***
*** Bug 420593 has been marked as a duplicate of this bug. ***
*** Bug 420745 has been marked as a duplicate of this bug. ***
wow, I never filed a bug this popular before...
*** Bug 420885 has been marked as a duplicate of this bug. ***
*** Bug 421258 has been marked as a duplicate of this bug. ***
Not fixed by the 'shot in the dark' you filed this morning: still happens with 385. You need the trace again?
Nah. It's the strangest thing. When run standalone using ./gimmie/gimmie_applet --window, the events from gmenu when the menus change is handled correctly. When run as a panel applet the event causes the crash described. Can someone else confirm this? Just run gimmie_applet --window, and fire up alacarte, change an item's visibility and see if it crashes.
*** Bug 421262 has been marked as a duplicate of this bug. ***
Just to note, I don't use gimmie as a panel applet. I use it as my sole panel. This is the mode in which I am seeing the crash. I will try the --window thing later, I'm a bit busy right now.
(In reply to comment #18) > > Can someone else confirm this? Just run gimmie_applet --window, and fire up > alacarte, change an item's visibility and see if it crashes. > OK, I tried to do this by launching gimmie with '/usr/libexec/gimmie_applet --window'. Once displayed, I changed a couple of menu entries with the menu editor; nothing happened immediately until I clicked on the 'Program' button, and then I get the traceback below. << [deji@agape ~]$ /usr/libexec/gimmie_applet --window ** (gimmie_applet:12314): WARNING **: IPP request failed with status 1030 ** (gimmie_applet:12314): WARNING **: IPP request failed with status 1030 !!! net.sf.gaim.GaimService D-BUS service not available. Is Gaim2 running? Running gimmie instance: <gnome.applet.Applet object (PanelApplet) at 0x1447960> None Traceback (most recent call last):
+ Trace 121140
self._show()
self.topic_win = self.topic.get_topic_window()
self.topic_window = TopicMenu(self)
TopicView.__init__(self, topic)
self.sidebar = Sidebar(topic)
self.add_sources()
for child in self.get_children():
>> Hope that helps.
(In reply to comment #21) > OK, I tried to do this by launching gimmie with '/usr/libexec/gimmie_applet > --window'. Once displayed, I changed a couple of menu entries with the menu > editor; nothing happened immediately until I clicked on the 'Program' button, > and then I get the traceback below. This looks like a crash we were seeing in Gimmie 0.2.4. What version of Gimmie are you running? I'm only really interested in how a recent SVN version behaves. Thanks!
*** Bug 421383 has been marked as a duplicate of this bug. ***
*** Bug 421425 has been marked as a duplicate of this bug. ***
*** Bug 421464 has been marked as a duplicate of this bug. ***
Okay, I'm just disabling the menu change notification monitor, and releasing 0.2.6. People will have to restart Gimmie to see menu changes, but that's better than crashing.
(In reply to comment #22) > (In reply to comment #21) > > OK, I tried to do this by launching gimmie with '/usr/libexec/gimmie_applet > > --window'. Once displayed, I changed a couple of menu entries with the menu > > editor; nothing happened immediately until I clicked on the 'Program' button, > > and then I get the traceback below. > > This looks like a crash we were seeing in Gimmie 0.2.4. What version of Gimmie > are you running? I'm only really interested in how a recent SVN version > behaves. Thanks! > Oops, sorry this is with stock 0.2.5, I'd forgotten to apply the said patch.
*** Bug 421871 has been marked as a duplicate of this bug. ***
*** Bug 421862 has been marked as a duplicate of this bug. ***
*** Bug 422832 has been marked as a duplicate of this bug. ***
*** Bug 422035 has been marked as a duplicate of this bug. ***
*** Bug 423960 has been marked as a duplicate of this bug. ***
*** Bug 423963 has been marked as a duplicate of this bug. ***
*** Bug 425014 has been marked as a duplicate of this bug. ***
*** Bug 424685 has been marked as a duplicate of this bug. ***
*** Bug 424678 has been marked as a duplicate of this bug. ***
*** Bug 428316 has been marked as a duplicate of this bug. ***
*** Bug 429067 has been marked as a duplicate of this bug. ***
*** Bug 442602 has been marked as a duplicate of this bug. ***
Hey guys, I am not able to reproduce this bug and it hasn't been reported for a long time... Is this still happening for you, or can we close this?
See comment #26. Alex worked around it, but didn't fix it. Hence it should really stay open.
*** Bug 474069 has been marked as a duplicate of this bug. ***
As orph points out, this issue has been fixed in the gnome-menus bug 442747. This feature therefore can now be re-enabled.
Okay, SVN now builds a fixed version of the gmenu bindings itself, since Ubuntu Feisty's are still broken. This seems to work well, so closing FIXED.
Can this be disabled in cases where the system gmenu bindings are okay?