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 444568 - crash in Gimmie: Clicked Library on Gimmi...
crash in Gimmie: Clicked Library on Gimmi...
Status: RESOLVED DUPLICATE of bug 423474
Product: gimmie
Classification: Deprecated
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Gimmie Maintainers
Gimmie Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-06-06 00:41 UTC by Thomas Pifer
Modified: 2007-07-04 17:50 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Thomas Pifer 2007-06-06 00:41:30 UTC
What were you doing when the application crashed?
Clicked Library on Gimmie toolbar.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

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 (591 sec old) ---------------------
--- Hash table keys for warning below:
--> file:///home/thomas
(nautilus:3496): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
--- Hash table keys for warning below:
--> file:///home/thomas
(nautilus:3506): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
Loading "installonlyn" plugin
Loading "installonlyn" plugin
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID 8df56d05
Importing GPG key 0x8DF56D05 "Fedora Linux (RPMS) <security@fedora.us>" from http://macromedia.mplug.org/FEDORA-GPG-KEY
--------------------------------------------------
Traceback (most recent call last):
  • File "/usr/lib/python2.5/site-packages/gimmie/gimmie_applet.py", line 516 in do_button_press_event
    self._show()
  • File "/usr/lib/python2.5/site-packages/gimmie/gimmie_applet.py", line 521 in _show
    self.topic_win = self.topic.get_topic_window()
  • File "/usr/lib/python2.5/site-packages/gimmie/gimmie_applet.py", line 393 in get_topic_window_mod
    self.topic_window = TopicMenu(self)
  • File "/usr/lib/python2.5/site-packages/gimmie/gimmie_applet.py", line 251 in __init__
    self._add_toolbar_items()
  • File "/usr/lib/python2.5/site-packages/gimmie/gimmie_applet.py", line 368 in _add_toolbar_items
    for i in self.topic.get_toolbar_items(self.tooltips):
  • File "/usr/lib/python2.5/site-packages/gimmie/gimmie_documents.py", line 396 in get_toolbar_items
    btn = PlacesMenuButton(tooltips)
  • File "/usr/lib/python2.5/site-packages/gimmie/gimmie_documents.py", line 283 in __init__
    self.set_menu(PlacesMenu())
  • File "/usr/lib/python2.5/site-packages/gimmie/gimmie_documents.py", line 246 in __init__
    for item in device_source.get_items():
  • File "/usr/lib/python2.5/site-packages/gimmie/gimmie_base.py", line 219 in get_items
    for i in self.get_items_uncached():
  • File "/usr/lib/python2.5/site-packages/gimmie/gimmie_computer.py", line 217 in get_items_uncached
    yield DriveItem(drive)
  • File "/usr/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 0x92fdbbc>'

Comment 1 André Klapper 2007-07-04 17:50:52 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 423474 ***