GNOME Bugzilla – Bug 447957
crash in Gimmie: Crash when external HD not connected
Last modified: 2007-06-23 17:15:41 UTC
What were you doing when the application crashed? This exception occurs every time I attempt to open Devices & Media without my external hard disk connected. With the hard disk connected and mounted, this error does not happen. This also happen when accessing other menus without the HD connected. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome 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 (777 sec old) --------------------- ** (evolution:3394): DEBUG: mailto URL program: evolution error getting update info: Cannot open/read repomd.xml file for repository: atrpms Loading "installonlyn" plugin Thank you for using Dia. CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... Increasing itip formatter search count to 1 Increasing itip formatter search count to 2 Increasing itip formatter search count to 3 Increasing itip formatter search count to 4 Decreasing itip formatter search count to 3 Decreasing itip formatter search count to 2 Decreasing itip formatter search count to 1 Decreasing itip formatter search count to 0 in emp_apps_open_in -------------------------------------------------- Traceback (most recent call last):
+ Trace 141258
for i in items:
for i in self.get_items_uncached():
yield DriveItem(drive)
raise ValueError, "Cannot find URI to open for drive '%s'" % drive
*** Bug 447955 has been marked as a duplicate of this bug. ***
*** Bug 447956 has been marked as a duplicate of this bug. ***
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 ***