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 433785 - crash in Gimmie: i pressed the library bu...
crash in Gimmie: i pressed the library bu...
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-04-27 04:40 UTC by almackska
Modified: 2007-05-03 03:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description almackska 2007-04-27 04:40:15 UTC
What were you doing when the application crashed?
i pressed 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.2944.fc6 #1 SMP Tue Apr 10 18:46:45 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
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 (35 sec old) ---------------------
URL: http://ocbmaurice.no-ip.org/slist/wbbvmelnrs/best/server.met
Response: 200 (Error: 0)
Download size: 2037
HTTP download thread ended
Shutting down aMule...
aMule dialog destroyed
Now, exiting main app...
aMule OnExit: Terminating core.

Saving PartFile 1 of 1
All PartFiles Saved.
aMule shutdown completed.
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
OIL: ERROR liboiltest.c 403: oil_test_check_impl(): function merge_linear_u8_sse2 in class merge_linear_u8 failed check (8295 > 0) || (outside=0)
OIL: ERROR liboiltest.c 403: oil_test_check_impl(): function merge_linear_u8_mmx in class merge_linear_u8 failed check (8545 > 0) || (outside=0)
--------------------------------------------------
Traceback (most recent call last):
  • 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 0xb3c5f694>'

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