GNOME Bugzilla – Bug 436082
crash in Gimmie: I haven't been using com...
Last modified: 2007-05-26 00:58:09 UTC
What were you doing when the application crashed? I haven't been using computer when crash occured. I have no idea what caused it. Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: MurrinaAquaIsh 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 (1280 sec old) --------------------- alarm-notify.c:393 (cal_opened_cb) contacts:/// - Calendar Status 0 alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-notify.c:349 (alarm_msg_received) - 0x80dcfb8: Received at thread b3527b90 alarm-queue.c:2008 (alarm_queue_add_async) - 0x80 (gnome-panel:5731): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -9 and height 24 ** Message: <information> Połączono z siecią przewodową. /usr/lib/python2.5/site-packages/UpdateManager/Common/SimpleGladeApp.py:335: GtkWarning: Failed to set text from markup due to error parsing markup: Błąd w wierszu 1 przy znaku 68: Element "b" zosta return gtk.glade.XML(self.glade_path, root, domain) *** CLB *** Initializing Google Browser Sync... *** CLB *** Instanciating core objects... *** CLB *** Registering with XPCOM... *** CLB *** Adding categories... *** CLB *** Google Browser Sync initialized succesfully! -------------------------------------------------- Traceback (most recent call last):
+ Trace 132531
acct_doc = parse(self.accounts_path)
from xml.dom import expatbuilder
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 417988 ***