GNOME Bugzilla – Bug 522425
crash in Deskbar: deleting the bar from th...
Last modified: 2008-03-15 00:23:11 UTC
What were you doing when the application crashed? deleting the bar from tha bottom of the screen Distribution: Ubuntu 8.04 (hardy) Gnome Release: 2.22.0 2008-03-10 (Ubuntu) BugBuddy Version: 2.21.90 System: Linux 2.6.24-11-generic #1 SMP Fri Feb 29 22:08:31 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Human-Murrine 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 (96 sec old) --------------------- Error - cannot end transaction. Rolling back... Error - cannot end transaction. Rolling back... Error - cannot end transaction. Rolling back... Error - cannot end transaction. Rolling back... Error - cannot end transaction. Rolling back... Error - cannot end transaction. Rolling back... Error - cannot end transaction. Rolling back... ** (synaptic:8481): WARNING **: TerminalTimeout in step: Configuring python SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ** (synaptic:8481): WARNING **: no statusfd changes/content updates in terminal for 120 seconds ** (synaptic:8481): WARNING **: TerminalTimeout in step: Configuring python (gnome-panel:5759): Wnck-CRITICAL **: wnck_screen_get_workspace_count: assertion `WNCK_IS_SCREEN (screen)' failed -------------------------------------------------- Traceback (most recent call last):
+ Trace 192396
self.load (f)
modules = self.import_module (filename)
if not getattr(module, "has_requirements" )():
if is_preferred_browser("epiphany"):
if http_handler.find(test) != -1:
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 518941 ***