GNOME Bugzilla – Bug 561985
crash in Deskbar:
Last modified: 2008-12-03 13:31:36 UTC
What were you doing when the application crashed? Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.1 2007-10-19 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-15-386 #1 Tue Oct 21 23:10:30 GMT 2008 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 (69 sec old) --------------------- alarm-queue.c:436 (alarm_trigger_cb) - Notification sent:2 alarm-notify.c:337 (alarm_msgport_replied) - 0x80ee270: Replied to GUI thread alarm-notify.c:337 (alarm_msgport_replied) - 0x8113710: Replied to GUI thread alarm-notify.c:337 (alarm_msgpoUnable to open desktop file /home/francesca/Desktop/kalarm.desktop for panel launcher: No such file or directory DCOPClient::attachInternal. Attach failed Could not open network socket Unable to open desktop file /home/francesca/Desktop/gnome-terminal.desktop for panel launcher: No such file or directory DCOPClient::attachInternal. Attach failed Could not open network socket kbuildsycoca running... kalarm: ERROR: KAlarmApp::alarmShowing(): alarm type not found: KAlarm-613465571.785:2 KCrash: Application 'kalarm' crashing... X Error: BadWindow (invalid Window parameter) 3 Major opcode: 7 Minor opcode: 0 Resource id: 0x340006f Window manager warning: Invalid WM_TRANSIENT_FOR window 0x58 specified for 0x3400007 (KAlarm - T). -------------------------------------------------- Traceback (most recent call last):
+ Trace 210136
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 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 475351 ***