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 422806 - crash in Gimmie: i just pressed the "libr...
crash in Gimmie: i just pressed the "libr...
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-25 22:03 UTC by anowak
Modified: 2007-03-25 22:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description anowak 2007-03-25 22:03:03 UTC 
What were you doing when the application crashed?
i just pressed the "library" button and *POW*


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.19-1.2911.6.4.fc6 #1 SMP Sat Feb 24 14:39:04 EST 2007 i686
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 (87 sec old) ---------------------
Debug: Loading Beagle.Util.Conf+SearchingConfig from searching.xml
** (eggcups:5858): WARNING **: IPP request failed with status 1280
** (eggcups:5858): WARNING **: IPP request failed with status 1280
Introspect error: The name edu.duke.linux.yum was not provided by any .service files
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Window manager warning: Lost connection to the display ':0.0';
most likely the X server was shut down or you killed/destroyed
the window manager.
Autoselected keyboard map en-us
ERROR: cernts.cern.ch: unable to connect
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
--------------------------------------------------
Traceback (most recent call last):

+ Trace 122207

  • File "/usr/lib/python2.4/site-packages/gimmie/gimmie_applet.py", line 516 in do_button_press_event 
    self._show()
  • File "/usr/lib/python2.4/site-packages/gimmie/gimmie_applet.py", line 521 in _show 
    self.topic_win = self.topic.get_topic_window()
  • File "/usr/lib/python2.4/site-packages/gimmie/gimmie_applet.py", line 393 in get_topic_window_mod 
    self.topic_window = TopicMenu(self)
  • File "/usr/lib/python2.4/site-packages/gimmie/gimmie_applet.py", line 251 in __init__ 
    self._add_toolbar_items()
  • File "/usr/lib/python2.4/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.4/site-packages/gimmie/gimmie_documents.py", line 396 in get_toolbar_items 
    btn = PlacesMenuButton(tooltips)
  • File "/usr/lib/python2.4/site-packages/gimmie/gimmie_documents.py", line 283 in __init__ 
    self.set_menu(PlacesMenu())
  • File "/usr/lib/python2.4/site-packages/gimmie/gimmie_documents.py", line 246 in __init__ 
    for item in device_source.get_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 0xb0b1a93c>' 






Comment 1


Tony Tsui





          2007-03-25 22:58:34 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 ***