GNOME Bugzilla – Bug 487726
crash in Gimmie:
Last modified: 2007-10-22 22:35:19 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 Sun Sep 23 19:50:39 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: OSX 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 --------------------- self.window_main.set_sensitive(False) (-5, '\xe6\xb2\x92\xe6\x9c\x89\xe6\xad\xa4\xe4\xb8\xbb\xe6\xa9\x9f\xe5\x90\x8d\xe7\xa8\xb1\xe6\x89\x80\xe5\xb0\x8d\xe6\x87\x89\xe7\x9a\x84\xe4\xbd\x8d\xe5\x9d\x80') (-5, '\xe6\xb2\x92\xe6\x9c\x89\xe6\xad\xa4\xe4\xb8\xbb\xe6\xa9\x9f\xe5\x90\x8d\xe7\xa8\xb1\xe6\x89\x80\xe5\xb0\x8d\xe6\x87\x89\xe7\x9a\x84\xe4\xbd\x8d\xe5\x9d\x80') (-5, '\xe6\xb2\x92\xe6\x9c\x89\xe6\xad\xa4\xe4\xb8\xbb\xe6\xa9\x9f\xe5\x90\x8d\xe7\xa8\xb1\xe6\x89\x80\xe5\xb0\x8d\xe6\x87\x89\xe7\x9a\x84\xe4\xbd\x8d\xe5\x9d\x80') Error reading all smiley in map file /home/realturner/.config/emesene1.0/tsao921_msn_com/custom_emoticons/map Protocol error: '' Emitting msnobj-changed Emitting msnobj-changed Emitting msnobj-changed Emitting msnobj-changed Emitting msnobj-changed Emitting msnobj-changed Emitting msnobj-changed Emitting msnobj-changed (8, 'EOF occurred in violation of protocol') -------------------------------------------------- Traceback (most recent call last):
+ Trace 171003
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 ***