GNOME Bugzilla – Bug 510673
crash in Gimmie: Modificando las preferen...
Last modified: 2008-03-10 13:18:22 UTC
What were you doing when the application crashed? Modificando las preferencias de Gimmie: Para que deje de mostrar los los contactos en el penel. Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.1 2007-10-19 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: UbuntuStudio Icon Theme: UbuntuStudio 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 --------------------- alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80e2120: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) file:///home/familia/.evolution/memos/local/system - Calendar Status 0 alarm-queue.c:2052 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_received) - 0x80e8af0: Received at thread b4d72b90 alarm-queue.c:2003 (alarm_queue_add_async) - 0x80e9010 alarm-queue.c:581 (load_alarms_for_today) - From Sat Jan 19 16:58:46 2008 to Sat Jan 19 16:58:46 2008 alarm-queue.c:518 (load_alarms) alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80e8af0: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) contacts:/// - Calendar Status 0 alarm-queue.c:2052 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_rece/usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format -------------------------------------------------- Gimmie Version: 0.2.7 Traceback (most recent call last):
+ Trace 185997
acct = PidginAccount(node)
self.protocol = node.getElementsByTagName("protocol")[0].childNodes[0].data
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 457116 ***