GNOME Bugzilla – Bug 456917
crash in Gimmie: Start Gimmie
Last modified: 2007-08-29 22:38:45 UTC
What were you doing when the application crashed? Start Gimmie Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-11 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-16-generic #2 SMP Thu Jun 7 19:00:28 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Human 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 (64 sec old) --------------------- (Gecko:14418): Gtk-WARNING **: gtktreestore.c:897: invalid object type ` LoadPlugin: failed to initialize shared library /home/wouter/.mozilla/plugins/libflashplayer.so [/home/wouter/.mozilla/plugins/libflashplayer.so: verkeerde ELF-klasse: ELFCLASS32] ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) LoadPlugin: failed to initialize shared library /home/wouter/.mozilla/plugins/libflashplayer.so [/home/wouter/.mozilla/plugins/libflashplayer.so: verkeerde ELF-klasse: ELFCLASS32] LoadPlugin: failed to initialize shared library /home/wouter/.mozilla/plugins/libflashplayer.so [/home/wouter/.mozilla/plugins/libflashplayer.so: verkeerde ELF-klasse: ELFCLASS32] Liferea did receive signal 11 (Segmentatiefout). -------------------------------------------------- Traceback (most recent call last):
+ Trace 148023
trashdir = TrashDirectory(trash_uri)
self._trash_dir_changed()
for file in gnomevfs.open_directory(self.trash_uri):
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 413872 ***