GNOME Bugzilla – Bug 483477
crash in Gimmie: switching panels Gimmie ...
Last modified: 2007-10-05 19:31:35 UTC
What were you doing when the application crashed? switching panels Gimmie crash Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.0 2007-09-17 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70000000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: nuoveXT.2.2 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 (439 sec old) --------------------- checking for valid crashreport now checking for valid crashreport now checking for valid crashreport now checking for valid crashreport now checking for valid crashreport now Segmentation fault (core dumped) checking for valid crashreport now Gtk-Message: Failed to load module "gnomebreakpad": libgnomebreakpad.so: cannot open shared object file: No such file or directory checking for valid crashreport now Gtk-Message: Failed to load module "gnomebreakpad": libgnomebreakpad.so: cannot open shared object file: No such file or directory JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] Gtk-Message: Failed to load module "gnomebreakpad": libgnomebreakpad.so: cannot open shared object file: No such file or directory Gtk-Message: Failed to load module "gnomebreakpad": libgnomebreakpad.so: cannot open shared object file: No such file or directory -------------------------------------------------- Gimmie Version: 0.2.7 Traceback (most recent call last):
+ Trace 167790
printer.connect("attributes_changed", lambda p: self.emit("reload"))
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. *** This bug has been marked as a duplicate of 475020 ***