GNOME Bugzilla – Bug 485913
crash in Gimmie: tried running gimmie fro...
Last modified: 2007-10-14 13:59:56 UTC
What were you doing when the application crashed? tried running gimmie from a terminal 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-386 #2 Sun Sep 23 19:47:10 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Crux Icon Theme: Crux 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 (4441 sec old) --------------------- ** Message: Viewer state: STOPPED ** Message: totem_embedded_set_error: 'An error occurred', 'The movie could not be read.' ** Message: done opening fd://0 ** Message: StopStream signal received ** Message: totem_embedded_set_error: 'An error occurred', 'There is no plugin to handle this movie.' ** Message: NewStream mimetype 'video/quicktime' URL 'http://www.pixar.com/theater/shorts/kk/quicktime/kk_320.mov' ** Message: Should be dual type 'video/quicktime', making sure now ** Message: Is not dual type 'video/quicktime' ** (totem-plugin-viewer:22446): WARNING **: Error in bacon_video_widget_play: There is no plugin to handle this movie. ** Message: DestroyStream reason 2 ** Message: URLNotify URL 'http://www.pixar.com/theater/shorts/kk/quicktime/kk_320.mov' reason 2 ** Message: totemPlugin dtor [0x908d010] ** Message: NP_Shutdown ** Message: totemNarrowSpacePlugin dtor [0xa1644f8] -------------------------------------------------- Gimmie Version: 0.2.7 TypeError: <lambda>() takes exactly 2 arguments (1 given)
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 ***