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 444930 - crash in Gimmie: clicked on 'library
crash in Gimmie: clicked on 'library
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 23:28 UTC by chris
Modified: 2007-07-04 17:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description chris 2007-06-06 23:28:17 UTC 
What were you doing when the application crashed?
clicked on 'library


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:47:07 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
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 (20 sec old) ---------------------
mythbackend is stopped
mythbackend
mythbackend is stopped
mythbackend
mythbackend (pid 4510) is running...
MPlayer dev-SVN-rUNKNOWN-4.1.2 (C) 2000-2006 MPlayer Team
CPU: Intel(R) Core(TM)2 CPU          6300  @ 1.86GHz (Family: 6, Model: 15, Stepping: 6)
CPUflags:  MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 1
Compiled with runtime CPU detection.
Creating config file: /home/cje/.mplayer/config
mplayer: could not connect to socket
mplayer: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.
[skin] file ( /usr/share/mplayer/skins/default/skin ) not found.
Skin not found (default).
--------------------------------------------------
Traceback (most recent call last):

+ Trace 138910

  • File "/usr/lib64/python2.5/site-packages/gimmie/gimmie_applet.py", line 516 in do_button_press_event 
    self._show()
  • File "/usr/lib64/python2.5/site-packages/gimmie/gimmie_applet.py", line 521 in _show 
    self.topic_win = self.topic.get_topic_window()
  • File "/usr/lib64/python2.5/site-packages/gimmie/gimmie_applet.py", line 393 in get_topic_window_mod 
    self.topic_window = TopicMenu(self)
  • File "/usr/lib64/python2.5/site-packages/gimmie/gimmie_applet.py", line 251 in __init__ 
    self._add_toolbar_items()
  • File "/usr/lib64/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/lib64/python2.5/site-packages/gimmie/gimmie_documents.py", line 396 in get_toolbar_items 
    btn = PlacesMenuButton(tooltips)
  • File "/usr/lib64/python2.5/site-packages/gimmie/gimmie_documents.py", line 283 in __init__ 
    self.set_menu(PlacesMenu())
  • File "/usr/lib64/python2.5/site-packages/gimmie/gimmie_documents.py", line 246 in __init__ 
    for item in device_source.get_items():
  • File "/usr/lib64/python2.5/site-packages/gimmie/gimmie_base.py", line 219 in get_items 
    for i in self.get_items_uncached():
  • File "/usr/lib64/python2.5/site-packages/gimmie/gimmie_computer.py", line 217 in get_items_uncached 
    yield DriveItem(drive)
  • File "/usr/lib64/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 0x10d03c0>' 






Comment 1


André Klapper





          2007-07-04 17:51:09 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 ***