GNOME Bugzilla – Bug 481128
crash in Gimmie:
Last modified: 2007-09-28 11:23:01 UTC
What were you doing when the application crashed? Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-16-lowlatency #2 SMP PREEMPT Fri Aug 31 00:58:46 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: WinXP-Silver Icon Theme: Human Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0 CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 ----------- .xsession-errors (8971 sec old) --------------------- zip info: local extra (21 bytes) != central extra (13 bytes): chrome/chromeFiles/content/accelimation.js zip info: local extra (21 bytes) != central extra (13 bytes): chrome/chromeFiles/content/newscript.xul zip info: local extra (21 bytes) != central extra (13 bytes): chrome/chromeFiles/content/pages-overlay.xul zip info: local extra (21 bytes) != central extra (13 bytes): chrome/chromeFiles/content/manage.js zip info: local extra (21 bytes) != central extra (13 bytes): chrome/chromeFiles/content/default-config.xml zip info: local extra (21 bytes) != central extra (13 bytes): chrome/chromeFiles/content/manage.xul zip info: local extra (21 bytes) != central extra (13 bytes): chrome/chromeFiles/content/template.user.js zip info: local extra (21 bytes) != central extra (13 bytes): chrome/chromeFiles/content/install.js zip info: local extra (21 bytes) != central extra (13 bytes): chrome/chromeFiles/content/menucommander.js zip info: local extra (21 bytes) != central extra (13 bytes): chrome/chromeFiles/content/status_on.gif zip info: local extra (21 bytes) != central extra (13 bytes): chrome/chromeFiles/content/miscapis.js zip info: local extra (21 bytes) != central extra (13 bytes): chrome/chromeFiles/content/newscript.js zip info: local extra (21 bytes) != central extra (13 bytes): chrome/chromeFiles/content/install.xul ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 166053
signal = self.event_mapping[event]
I had un-mounted a partition from within gParted immediately before Gimmie crashed. It seemed to me to be in response to un-mounting the partition. I was not otherwise using Gimmie at the time, other than having it sitting on my Gnome Panel awaiting my attention.
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. Or (if you like bleeding edge) you can also try the latest SVN which should contain a patch for this crasher. Feel free to reopen this if you think it is not solved. *** This bug has been marked as a duplicate of 417686 ***