GNOME Bugzilla – Bug 481393
crash in Deskbar: Pressed 'F3' shortcut to...
Last modified: 2007-09-29 16:10:59 UTC
What were you doing when the application crashed? Pressed 'F3' shortcut to invoke deskbar, and it crashed immediately. Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.0 2007-09-17 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 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 (140 sec old) --------------------- (evolution:11018): camel-CRITICAL **: camel_object_is: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed (evolution:11018): camel-CRITICAL **: camel_stream_write: assertion `CAMEL_IS_STREAM (stream)' failed (evolution:11018): camel-WARNING **: Trying to check junk data is OBJECT 'CamelStream' (evolution:11018): camel-CRITICAL **: camel_object_is: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed (evolution:11018): camel-CRITICAL **: camel_stream_printf: assertion `CAMEL_IS_STREAM (stream)' failed (evolution:11018): camel-WARNING **: Trying to check junk data is OBJECT 'CamelStream' (evolution:11018): camel-CRITICAL **: camel_object_is: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed (evolution:11018): camel-CRITICAL **: camel_stream_write: assertion `CAMEL_IS_STREAM (stream)' failed -------------------------------------------------- Traceback (most recent call last):
+ Trace 166249
reply_handler(*message.get_args_list(**get_args_opts))
reply_handler = lambda hits: self.recieve_hits(qstring, hits, max),
matches.append(TrackerLiveSearchMatch (output))
self.add_all_actions (get_actions_for_uri(result['uri']))
mime = gnomevfs.get_mime_type(uri)
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 474131 ***