GNOME Bugzilla – Bug 430491
crash in Gimmie: run item ¨Devices and di...
Last modified: 2007-04-26 07:29:25 UTC
What were you doing when the application crashed? run item ¨Devices and disks¨ 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: 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 (75 sec old) ---------------------
+ Trace 128377
item_id = os.path.split(items[iter][3].get_desktop_file_path())[1]
i = p.rfind('/') + 1
Traceback (most recent call last):
** (gnome-panel:5600): WARNING **: Failed to establish a connection with GDM: Нет такого файла или каталога ** (gnome-panel:5600): WARNING **: Failed to establish a connection with GDM: Нет такого файла или каталога -------------------------------------------------- Traceback (most recent call last): 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 0xb5151cd4>'
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 ***