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 422189 - crash in Gimmie: Clicked on Devices & Med...
crash in Gimmie: Clicked on Devices & Med...
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-24 08:16 UTC by linux_au
Modified: 2007-03-25 23:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description linux_au 2007-03-24 08:16:30 UTC 
What were you doing when the application crashed?
Clicked on Devices & Media Button


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

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

Traceback (most recent call last):

+ Trace 121688

  • File "/usr/lib/python2.4/site-packages/gimmie/gimmie_topicwin.py", line 625 in _idle_load_items 
    for i in items:
  • File "/usr/lib/python2.4/site-packages/gimmie/gimmie_base.py", line 219 in get_items 
    for i in self.get_items_uncached():
  • File "/usr/lib/python2.4/site-packages/gimmie/gimmie_computer.py", line 217 in get_items_uncached 
    yield DriveItem(drive)
  • File "/usr/lib/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 0xaf49884c>' 






Comment 1


Tony Tsui





          2007-03-25 23:00:02 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 ***