GNOME Bugzilla – Bug 490880
crash in Gimmie: searching for screen
Last modified: 2007-10-27 23:25:31 UTC
What were you doing when the application crashed? searching for screen Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.0 2007-09-17 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 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 (61 sec old) --------------------- err:ole:CoMarshalInterface Failed to marshal the interface {00000001-0000-0000-c000-000000000046}, 80004002 err:ole:CoGetClassObject no class object {a65b8071-3bfe-4213-9a5b-491da4461ca7} could be created for context 0x1 fixme:win:EnumDisplayDevicesW ((null),0,0x7d7c84d0,0x00000000), stub! fixme:d3d9:IDirect3DDevice9Impl_CreateQuery (0x12e718) call to IWineD3DDevice_CreateQuery failed fixme:wave:DSD_CreateSecondaryBuffer (0x2441808,0x7d7c9074,4,0,0x19b79a0,0x18a362c,0x19b7980): stub err:ole:CoCreateInstance apartment not initialised err:ole:CoCreateInstance apartment not initialised err:ole:CoCreateInstance apartment not initialised err:ole:CoCreateInstance apartment not initialised *********************************WARN_ONCE********************************* File r300_render.c function r300Fallback line 469 Software fallback:ctx->Multisample.Enabled *************************************************************************** fixme:quartz:Filtergraph_QueryInterface unknown interface {fc4801a3-2ba9-11cf-a229-00aa003d7352} fixme:dinput:SysMouseAImpl_Acquire Clipping cursor to (0,51)-(640,531) -------------------------------------------------- Gimmie Version: 0.2.7 Traceback (most recent call last):
+ Trace 173292
printer.connect("attributes_changed", lambda p: self.emit("reload"))
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 475020 ***