GNOME Bugzilla – Bug 432212
crash in Gimmie: I pressed after logon th...
Last modified: 2007-05-26 02:02:27 UTC
What were you doing when the application crashed? I pressed after logon the "Persons"-Button 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: Human Icon Theme: Tango 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:2008 (alarm_queue_add_async) - 0x80db140 alarm-queue.c:560 (load_alarms_for_today) - From Sun Apr 22 12:36:12 2007 to Sun Apr 22 12:36:12 2007 alarm-queue.c:497 (load_alarms) alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80db300: Replied to GUI thread alarm-notify.c:349 (alarm_msg_received) - 0x80da5f8: Received at thread b5dabb90 alarm-queue.c:2008 (alarm_queue_add_async) - 0x80dafc0 alarm-queue.c:560 (load_alarms_for_today) - From Sun Apr 22 12:36:12 2007 to Sun Apr 22 12:36:12 2007 alarm-queue.c:497 (load_alarms) alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80da5f8: Replied to GUI thread alarm-notify.c:349 (alarm_msg_received) - 0x80dc888: -------------------------------------------------- Traceback (most recent call last):
+ Trace 129697
self._show()
self.topic_win = self.topic.get_topic_window()
self.topic_window = TopicMenu(self)
self.find_first_button()
items = source.get_items()
self._reload()
contacts = gmail_reader.get_contacts()
self._login()
self.account_settings.do_open()
self.account_win.show()
self._init_account_settings()
self.keyring = gnomekeyring.get_default_keyring_sync() NoKeyringDaemonError
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 418806 ***