GNOME Bugzilla – Bug 497093
crash in Gimmie: je l'installais
Last modified: 2007-11-24 17:11:51 UTC
What were you doing when the application crashed? je l'installais Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.0 2007-09-17 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70000000 Selinux: No Accessibility: Disabled GTK+ Theme: Beastie 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 --------------------- alarm-notify.c:337 (alarm_msgport_replied) - 0x80d79c8: Replied to GUI thread alarm-notify.c:349 (alarm_msg_received) - 0x80d78c8: Received at thread b5d73b90 alarm-queue.c:2003 (alarm_queue_add_async) - 0x80cecd0 alarm-queue.c:581 (load_alarms_for_today) - From Thu Nov 15 17:19:53 2007 to Thu Nov 15 17:19:53 2007 alarm-queue.c:518 (load_alarms) alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80d78c8: 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/usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format /home/philippe/.themes/Beastie/gtk-2.0/gtkrc:55: Clearlooks configuration option "menuitemstyle" is not supported and will be ignored. /home/philippe/.themes/Beastie/gtk-2.0/gtkrc:56: Clearlooks configuration option "listviewitemstyle" is not supported and will be ignored. /home/philippe/.themes/Beastie/gtk-2.0/gtkrc:57: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored. -------------------------------------------------- Gimmie Version: 0.2.7 Traceback (most recent call last):
+ Trace 177909
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 ***