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 445391 - crash in Gimmie: Clicked on Library butto...
crash in Gimmie: Clicked on Library butto...
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-08 07:13 UTC by jploh
Modified: 2007-07-04 17:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description jploh 2007-06-08 07:13:01 UTC 
What were you doing when the application crashed?
Clicked on Library button


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: Glossy
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 (226 sec old) ---------------------
Internet Systems Consortium DHCP Client V3.0.5-RedHat
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Listening on LPF/eth1/00:0c:f1:01:f1:57
Sending on   LPF/eth1/00:0c:f1:01:f1:57
Sending on   Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 4
DHCPOFFER from 192.168.0.1
DHCPREQUEST on eth1 to 255.255.255.255 port 67
DHCPACK from 192.168.0.1
bound to 192.168.0.133 -- renewal in 570764 seconds.
Stale pid file.  Removing
compiz: Screen 0 on display ":0.0" already has a window manager; try using the --replace option to replace the current window manager.
compiz: No manageable screens found on display :0.0
--------------------------------------------------
Traceback (most recent call last):

+ Trace 139286

  • 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 0x902b9dc>' 






Comment 1


André Klapper





          2007-07-04 17:53:33 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 ***