GNOME Bugzilla – Bug 422178
crash in Gimmie: Just launched gthumb and...
Last modified: 2007-05-12 16:09:33 UTC
What were you doing when the application crashed? Just launched gthumb and the gimp, but not via the menu Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.0 2007-03-13 (Ubuntu) BugBuddy Version: 2.18.0 System: Linux 2.6.20-11-generic #2 SMP Thu Mar 15 08:03:07 UTC 2007 i686 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 (12 sec old) --------------------- ** Message: URLNotify URL 'http://images.apple.com/movies/lionsgate/the_condemned/the_condemned-tlr_h.640.mov' reason 0 ** Message: url: http://trailers.apple.com/trailers/lions_gate/thecondemned/high.html ** Message: redirect: the_condemned-tlr_h640w.mov ** Message: Redirecting to 'http://images.apple.com/movies/lionsgate/the_condemned/the_condemned-tlr_h640w.mov' ** Message: Viewer state: STOPPED ** Message: totem_embedded_open_internal 'http://images.apple.com/movies/lionsgate/the_condemned/the_condemned-tlr_h640w.mov' is-browser-stream 0 ** Message: BEFORE _open ** Message: AFTER _open (ret: 1) ** Message: Viewer state: PLAYING ** Message: totemPlugin dtor [0xab91398] ** Message: NP_Shutdown checking for valid crashreport now current dist not found in meta-release file ** Message: drive = 0 ** Message: volume = 0 converting comment system...done. -------------------------------------------------- Traceback (most recent call last):
+ Trace 121677
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 ***