After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 444102 - crash in Gimmie: clicked library
crash in Gimmie: clicked library
Status: RESOLVED DUPLICATE of bug 421620
Product: gimmie
Classification: Deprecated
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Gimmie Maintainers
Gimmie Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-06-04 20:57 UTC by dankster
Modified: 2007-09-14 22:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description dankster 2007-06-04 20:57:19 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):
  • File "/usr/local/lib/python2.5/site-packages/gimmie/gimmie_gui.py", line 386 in do_clicked
    self.topic_win = self.topic.get_topic_window()
  • File "/usr/local/lib/python2.5/site-packages/gimmie/gimmie_base.py", line 377 in get_topic_window
    self.topic_window = TopicWindow(self)
  • File "/usr/local/lib/python2.5/site-packages/gimmie/gimmie_topicwin.py", line 1131 in __init__
    self._add_toolbar_items()
  • File "/usr/local/lib/python2.5/site-packages/gimmie/gimmie_topicwin.py", line 1155 in _add_toolbar_items
    for i in self.topic.get_toolbar_items(self.tooltips):
  • File "/usr/local/lib/python2.5/site-packages/gimmie/gimmie_documents.py", line 396 in get_toolbar_items
    btn = PlacesMenuButton(tooltips)
  • File "/usr/local/lib/python2.5/site-packages/gimmie/gimmie_documents.py", line 283 in __init__
    self.set_menu(PlacesMenu())
  • File "/usr/local/lib/python2.5/site-packages/gimmie/gimmie_documents.py", line 246 in __init__
    for item in device_source.get_items():
  • File "/usr/local/lib/python2.5/site-packages/gimmie/gimmie_base.py", line 219 in get_items
    for i in self.get_items_uncached():
  • File "/usr/local/lib/python2.5/site-packages/gimmie/gimmie_computer.py", line 217 in get_items_uncached
    yield DriveItem(drive)
  • File "/usr/local/lib/python2.5/site-packages/gimmie/gimmie_computer.py", line 106 in __init__
    raise ValueError, "Cannot find URI to open for drive '%s'" % drive
ValueError: Cannot find URI to open for drive '<gnomevfs.Drive object (GnomeVFSDrive) at 0x8794194>'

Comment 1 H. 2007-09-14 22:38:44 UTC
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 ***