GNOME Bugzilla – Bug 470838
crash in Deskbar: Upgrade from feisty to g...
Last modified: 2007-09-18 16:49:07 UTC
What were you doing when the application crashed? Upgrade from feisty to gutsy, reboot, adding a deskbar while there is already a deskbar in the panel, (hoping this one would be "inline"), the crash came up just when i clicked on "add to panel") thanks. Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.19.6 2007-08-14 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-10-386 #1 Wed Aug 22 07:43:24 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Simple Icon Theme: Tango 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 (143 sec old) --------------------- alarm-queue.c:548 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80d9850: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) file:///home/gaby/.evolution/memos/local/system - Calendar Status 0 alarm-queue.c:2053 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_received) - 0x80cc678: Received at thread b3d89b90 alarm-queue.c:2004 (alarm_queue_add_async) - 0x80db560 alarm-queue.c:582 (load_alarms_for_today) - From Mon Aug 27 22:27:33 2007 to Mon Aug 27 22:27:33 2007 alarm-queue.c:519 (load_alarms) alarm-queue.c:548 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80cc678: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) contacts:/// - Calendar Status 0 alarm-queue.c:2053 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_received) - 0x80d9d98: Received PID TTY TIME CMD -------------------------------------------------- Traceback (most recent call last):
+ Trace 158290
self.__view.set_sensitive(True)
*** Bug 471588 has been marked as a duplicate of this bug. ***
*** Bug 471590 has been marked as a duplicate of this bug. ***
*** Bug 471598 has been marked as a duplicate of this bug. ***
*** Bug 471616 has been marked as a duplicate of this bug. ***
*** Bug 471760 has been marked as a duplicate of this bug. ***
*** Bug 472890 has been marked as a duplicate of this bug. ***
*** Bug 473065 has been marked as a duplicate of this bug. ***
*** Bug 473214 has been marked as a duplicate of this bug. ***
*** Bug 471031 has been marked as a duplicate of this bug. ***
*** Bug 471091 has been marked as a duplicate of this bug. ***
*** Bug 471212 has been marked as a duplicate of this bug. ***
*** Bug 471213 has been marked as a duplicate of this bug. ***
*** Bug 471288 has been marked as a duplicate of this bug. ***
*** Bug 471291 has been marked as a duplicate of this bug. ***
*** Bug 471302 has been marked as a duplicate of this bug. ***
*** Bug 471309 has been marked as a duplicate of this bug. ***
*** Bug 471311 has been marked as a duplicate of this bug. ***
*** Bug 471413 has been marked as a duplicate of this bug. ***
*** Bug 471449 has been marked as a duplicate of this bug. ***
*** Bug 471457 has been marked as a duplicate of this bug. ***
*** Bug 471924 has been marked as a duplicate of this bug. ***
*** Bug 471944 has been marked as a duplicate of this bug. ***
*** Bug 472141 has been marked as a duplicate of this bug. ***
*** Bug 472148 has been marked as a duplicate of this bug. ***
*** Bug 472367 has been marked as a duplicate of this bug. ***
*** Bug 472398 has been marked as a duplicate of this bug. ***
*** Bug 472401 has been marked as a duplicate of this bug. ***
*** Bug 472433 has been marked as a duplicate of this bug. ***
*** Bug 472441 has been marked as a duplicate of this bug. ***
*** Bug 472505 has been marked as a duplicate of this bug. ***
*** Bug 472582 has been marked as a duplicate of this bug. ***
*** Bug 472634 has been marked as a duplicate of this bug. ***
*** Bug 472699 has been marked as a duplicate of this bug. ***
*** Bug 472706 has been marked as a duplicate of this bug. ***
*** Bug 472711 has been marked as a duplicate of this bug. ***
*** Bug 473423 has been marked as a duplicate of this bug. ***
*** Bug 473571 has been marked as a duplicate of this bug. ***
*** Bug 473599 has been marked as a duplicate of this bug. ***
*** Bug 473733 has been marked as a duplicate of this bug. ***
*** Bug 473736 has been marked as a duplicate of this bug. ***
*** Bug 473860 has been marked as a duplicate of this bug. ***
Created attachment 95007 [details] [review] Correct race issue in __setup_mvc Looks like it's possible for the __on_loaded event to get called before the __setup_mvc completes creating __view, so switch the order of those events.
Marking as NEW due to dupes.
*** Bug 474117 has been marked as a duplicate of this bug. ***
*** Bug 474348 has been marked as a duplicate of this bug. ***
*** Bug 475999 has been marked as a duplicate of this bug. ***
*** Bug 476188 has been marked as a duplicate of this bug. ***
Patch looks fine. I already requested a Hard Code freeze break.
Sebastian wrote: > The patch really doesn't do anything fancy it just reorders the lines, > but it definitely solves this issue. i assume the "definitely" means that it is well-tested? :-) so, if someone (sebastian? tom? someone else?) could reliably reproduce this race condition, and could never reproduce the crash with tom's patch applied, this is the tentative release-team approval 1 of 2. clarification very appreciated, though!
Patch has been applied to svn trunk. Thanks for the help.
*** Bug 467477 has been marked as a duplicate of this bug. ***