GNOME Bugzilla – Bug 496029
crash in Deskbar: i was typing the path to...
Last modified: 2007-11-12 10:47:58 UTC
What were you doing when the application crashed? i was typing the path to my home folder and this bug reporting thingy appeared, however, the deskbar can still be used... 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: 70000000 Selinux: No Accessibility: Disabled GTK+ Theme: MurrinaNeo-Gilouche Icon Theme: nuoveXT.2.2 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) --------------------- to Mon Nov 12 10:03:17 2007 alarm-queue.c:518 (load_alarms) alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:349 (alarm_msg_received) - 0x80de208: Received at thread b4681b90 alarm-queue.c:2003 (alarm_queue_add_async) - 0x80dd5c0 alarm-notify.c:337 (alarm_msgport_replied) - 0x80dae20: Replied to GUI thread alarm-queue.c:581 (load_alarms_for_today) - From Mon Nov 12 10:03:17 2007 to Mon Nov 12 10:03:17 2007 alarm-queue.c:518 (load_alarms) alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:349 (alarm_msg_received) - 0x80da7a0: Received at thread b4681b90 alarm-queue.c/usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format PID TTY TIME CMD -------------------------------------------------- Traceback (most recent call last):
+ Trace 177126
run_old(*args, **kwargs)
self.__target(*self.__args, **self.__kwargs)
function(*args, **kwargs)
result += self._query_filefolder(query, True)
return [FileMatch(join(prefix, basename(completion)), "file://"+completion, priority=self.get_priority()) for completion in completions]
self.add_all_actions( get_actions_for_uri(absname) )
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 ***