GNOME Bugzilla – Bug 447532
crash in Gimmie:
Last modified: 2007-06-23 17:26:36 UTC
What were you doing when the application crashed? Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: TuxnTosh 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 (409 sec old) --------------------- 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) - 0x80d30f0: Received at thread b4cfeb90 alarm-queue.c:2008 (alarm_queueNo se puede abrir el archivo de escritorio file:///home/gabriel/Desktop/kaffeine.desktop para el lanzador del panel: No existe el fichero ó directorio ** (nm-applet:5597): WARNING **: <WARNING> nmi_save_network_info (): Error saving secret for wireless network 'RIU' in keyring: 5 ** (nm-applet:5597): WARNING **: <WARNING> nmi_save_network_info (): Error saving secret for wireless network 'RIU' in keyring: 5 ** (nm-applet:5597): WARNING **: <WARNING> nmi_save_network_info (): Error saving secret for wireless network 'RIU' in keyring: 5 ** Message: <information> Ahora está conectado a la red inalámbrica RIU. -------------------------------------------------- Traceback (most recent call last):
+ Trace 140929
self._show()
self.topic_win = self.topic.get_topic_window()
self.topic_window = TopicMenu(self)
TopicView.__init__(self, topic)
self.sidebar = Sidebar(topic)
gtk.VBox.__init__(self, False, 4)
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 416060 ***