GNOME Bugzilla – Bug 624267
crash in Deskbar:
Last modified: 2010-07-14 03:50:08 UTC
What were you doing when the application crashed? Distribution: Ubuntu 10.04 (lucid) Gnome Release: 2.30.2 2010-06-25 (Ubuntu) BugBuddy Version: 2.28.0 System: Linux 2.6.32-23-generic #37-Ubuntu SMP Fri Jun 11 07:54:58 UTC 2010 i686 X Vendor: The X.Org Foundation X Vendor Release: 10706000 Selinux: No Accessibility: Disabled GTK+ Theme: Crux Icon Theme: HighContrastInverse GTK+ Modules: canberra-gtk-module 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 Traceback (most recent call last):
+ Trace 222825
from deskbar.ui.DeskbarApplet import DeskbarApplet
from deskbar.ui.AbstractCuemiacDeskbarIcon import AbstractCuemiacDeskbarIcon
from deskbar.ui.CuemiacWindowController import CuemiacWindowController
from deskbar.ui.preferences.DeskbarPreferences import DeskbarPreferences
from deskbar.ui.preferences.AccelEntry import AccelEntry
----------- .xsession-errors (1028 sec old) --------------------- (<unknown>:4237): Gdk-WARNING **: XID collision, trouble ahead (<unknown>:4237): Gdk-WARNING **: XID collision, trouble ahead (<unknown>:4237): Gdk-WARNING **: XID collision, trouble ahead (<unknown>:4237): Gdk-WARNING **: XID collision, trouble ahead ** (evolution:5051): DEBUG: mailto URL command: evolution %s ** (evolution:5051): DEBUG: mailto URL program: evolution ** (evolution:5195): DEBUG: mailto URL command: evolution %s ** (evolution:5195): DEBUG: mailto URL program: evolution Traceback (most recent call last): File "/usr/lib/python2.6/dist-packages/gwibber/microblog/network.py", line 32, in __init__ self.curl.perform() error: (28, 'Operation timed out after 15000 milliseconds with 21309 out of 150981 bytes received') --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 617299 ***