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 424059 - crash in Gimmie: I have just click on the...
crash in Gimmie: I have just click on the...
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-03-29 09:18 UTC by j.leuenberg
Modified: 2007-03-29 22:29 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description j.leuenberg 2007-03-29 09:18:52 UTC
What were you doing when the application crashed?
I have just click on the "Library button"


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.20-1.2933.fc6 #1 SMP Mon Mar 19 11:00:19 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

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 ---------------------
    btn = PlacesMenuButton(tooltips)
  • File "/usr/lib64/python2.4/site-packages/gimmie/gimmie_documents.py", line 283 in __init__
    self.set_menu(PlacesMenu())
  • File "/usr/lib64/python2.4/site-packages/gimmie/gimmie_documents.py", line 246 in __init__
    for item in device_source.get_items():
  • File "/usr/lib64/python2.4/site-packages/gimmie/gimmie_base.py", line 219 in get_items
    for i in self.get_items_uncached():
  • File "/usr/lib64/python2.4/site-packages/gimmie/gimmie_computer.py", line 217 in get_items_uncached
    yield DriveItem(drive)
  • File "/usr/lib64/python2.4/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 0x2aaabec39d70>'
** (bug-buddy:3953): WARNING **: Impossible de charger l'icône pour Ouvrir le dossier
--------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib64/python2.4/site-packages/gimmie/gimmie_gui.py", line 386, in do_clicked
    self.topic_win = self.topic.get_topic_window()
  File "/usr/lib64/python2.4/site-packages/gimmie/gimmie_base.py", line 377, in get_topic_window
    self.topic_window = TopicWindow(self)
  File "/usr/lib64/python2.4/site-packages/gimmie/gimmie_topicwin.py", line 1131, in __init__
    self._add_toolbar_items()
  File "/usr/lib64/python2.4/site-packages/gimmie/gimmie_topicwin.py", line 1155, in _add_toolbar_items
    for i in self.topic.get_toolbar_items(self.tooltips):
  File "/usr/lib64/python2.4/site-packages/gimmie/gimmie_documents.py", line 396, in get_toolbar_items
    btn = PlacesMenuButton(tooltips)
  • File "/usr/lib64/python2.4/site-packages/gimmie/gimmie_documents.py", line 283 in __init__
    self.set_menu(PlacesMenu())
  • File "/usr/lib64/python2.4/site-packages/gimmie/gimmie_documents.py", line 246 in __init__
    for item in device_source.get_items():
  • File "/usr/lib64/python2.4/site-packages/gimmie/gimmie_base.py", line 219 in get_items
    for i in self.get_items_uncached():
  • File "/usr/lib64/python2.4/site-packages/gimmie/gimmie_computer.py", line 217 in get_items_uncached
    yield DriveItem(drive)
  • File "/usr/lib64/python2.4/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 0x2aaabec39d70>'

Comment 1 Tony Tsui 2007-03-29 22:29: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 ***