GNOME Bugzilla – Bug 493924
crash in Deskbar: This is similar to a pre...
Last modified: 2007-11-08 19:01:06 UTC
What were you doing when the application crashed? This is similar to a previous bug I reported. Hit the hotkey, typed "synaptic", hit enter, crash. Synaptic still started. 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 (45 sec old) --------------------- alarm-queue.c:518 (load_alarms) alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80dfaf0: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) file:///home/grant/.evolution/memos/local/system - Calendar Status 0 alarm-queue.c:2052 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_received) - 0x80de000: PID TTY TIME CMD ** Message: Error: Could not determine type of stream. gsttypefindelement.c(735): gst_type_find_element_activate (): /play/decodebin0/typefind totem-video-thumbnailer couln't open file 'file:///home/grant/Desktop/gv.com.1upshow.0708_640x360.wmv' Reason: Could not determine type of stream.. keybinding-properties-Message: title: Sound keybinding-properties-Message: title: Desktop keybinding-properties-Message: title: Desktop keybinding-properties-Message: title: Window Management -------------------------------------------------- Traceback (most recent call last):
+ Trace 175552
run_old(*args, **kwargs)
self.__target(*self.__args, **self.__kwargs)
function(*args, **kwargs)
if text.startswith(query):
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 475351 ***