GNOME Bugzilla – Bug 470054
crash in Gimmie: Open a tar.bz2
Last modified: 2007-08-27 11:11:26 UTC
What were you doing when the application crashed? Open a tar.bz2 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-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Neu 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 (484 sec old) --------------------- File /home/simon/Desktop/linuxwacom-0.7.8-3/conftest has finished changing File /home/simon/Desktop/linuxwacom-0.7.8-3/conftest has finished changing File /home/simon/Desktop/linuxwacom-0.7.8-3/conftest.c has finished changing File /home/simon/Desktop/linuxwacom-0.7.8-3/conftest.c has finished changing File /home/simon/Desktop/linuxwacom-0.7.8-3/conftest.c has finished changing File /home/simon/Desktop/linuxwacom-0.7.8-3/conftest.o has finished changing File /home/simon/Desktop/linuxwacom-0.7.8-3/conftest.c has finished changing File /home/simon/Desktop/linuxwacom-0.7.8-3/conftest.c has finished changing File /home/simon/Desktop/linuxwacom-0.7.8-3/conftest.c has finished changing File /home/simon/Desktop/linuxwacom-0.7.8-3/conftest.o has finished changing File /home/simon/Desktop/linuxwacom-0.7.8-3/conftest.er1 has finished changing File /home/simon/Desktop/linuxwacom-0.7.8-3/conftest.err has finished changing File /home/simon/Desktop/linuxwacom-0.7.8-3/conftest.c has finished changing ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 157712
self.recent_items[recent_item.get_uri()] = recent_item
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 417988 ***