GNOME Bugzilla – Bug 444102
crash in Gimmie: clicked library
Last modified: 2007-09-14 22:38:44 UTC
What were you doing when the application crashed? clicked library 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 Wed May 23 01:46:23 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks 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 (162 sec old) --------------------- VLC media player 0.8.6 Janus Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a0007e (VLC media ) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. [00000303] ffmpeg decoder error: more than 5 seconds of late video -> dropping frame (computer too slow ?) [00000280] main playlist: nothing to play [00000280] main playlist: stopping playback ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) (synaptic:7145): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed -------------------------------------------------- Traceback (most recent call last):
+ Trace 138255
self.topic_win = self.topic.get_topic_window()
self.topic_window = TopicWindow(self)
self._add_toolbar_items()
for i in self.topic.get_toolbar_items(self.tooltips):
btn = PlacesMenuButton(tooltips)
self.set_menu(PlacesMenu())
for item in device_source.get_items():
for i in self.get_items_uncached():
yield DriveItem(drive)
raise ValueError, "Cannot find URI to open for drive '%s'" % drive
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 421620 ***