GNOME Bugzilla – Bug 428306
crash in Gimmie: viewing an image in Eye ...
Last modified: 2007-04-12 22:31:50 UTC
What were you doing when the application crashed? viewing an image in Eye of gnome! Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.0 2007-03-13 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-14-generic #2 SMP Mon Apr 2 20:37:49 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Human Icon Theme: Gion 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 (81 sec old) --------------------- checking for valid crashreport now /usr/bin/webhttrack: line 152: 17907 Segmentation fault (core dumped) ${BINPATH}/htsserver "${DISTPATH}/" path "${HOME}/websites" lang "${LANGN}" $@ checking for valid crashreport now checking for valid crashreport now /usr/bin/webhttrack(18366): launching /usr/bin/x-www-browser /usr/bin/webhttrack(18366): spawning regular browser.. /usr/bin/webhttrack(18366): waiting for browser to terminate.. /usr/bin/webhttrack: line 152: 18381 Segmentation fault (core dumped) ${BINPATH}/htsserver "${DISTPATH}/" path "${HOME}/websites" lang "${LANGN}" $@ checking for valid crashreport now checking for valid crashreport now checking for valid crashreport now Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x4400003 (Brasero); these messages lack timestamps and therefore suck. <gtk.Menu object (GtkMenu) at 0x84d7a04> cell = combo.get_child().get_cell_renderers()[0] <gtk.Menu object (GtkMenu) at 0x84d7a04> -------------------------------------------------- Traceback (most recent call last):
+ Trace 126612
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 ***