Description of problem: A dialog appeared in top right of screen, with a message that an internal system error has occurred. Version-Release number of selected component (if applicable): gnome-packagekit-2.28.3-0.1.20091211git.fc12.x86_64 kernel-2.6.32.9-70.fc12.x86_64 PackageKit-0.5.7-1.fc12.x86_64 rpm-4.7.2-1.fc12.x86_64 rpm-python-4.7.2-1.fc12.x86_64 yum-3.2.27-2.fc12.noarch How reproducible: at the moment, easily. eg try yum Steps to Reproduce: 1. gnome + firefox + termi windows + nautilus windows + audacity 2. suspend 3. resume 4. after a while error dialog appears. Actual results: "An internal system error has occurred A problem that we were not expecting has occurred. Please report this bug in your distribution bugtracker with the error description. More Details: Error Type: <type 'exceptions.IOError'> Error Value: [Errno 30] Read-only file system File : /usr/lib/python2.6/site-packages/urlgrabber/grabber.py, line 1089, in _retrieve self.fo.write(buf)" Expected results: Lets say yum/pk can't write to disk. The error message could be clearer: 1. at least say which application generated it. (2). nice the error up eg. "An error was returned to pkit indicating that the operating system is having trouble accessing information at "/where/ever". It appears that manual intervention will be required to determine the cause and resolution of the underlying problem." Additional info: The machine was resumed from suspension (overnight). While the cause of the error is unclear, it seems to be correct in that from the time the dialog was shown, both terminal and gnome apps seem to be having trouble with my disks eg. nautilus copy paste a file: " There was an error copying the file into /home/infrastructure/software/linux/fedora/13/x86_64. Error opening file '/home/infrastructure/software/linux/fedora/13/x86_64/Fedora-13-Beta (copy).TC0_TC1-x86_64-DVD.diso': Read-only file system " Note: I am also hoping to reproduce a random crasher in audacity ( https://bugzilla.redhat.com/show_bug.cgi?id=577297 ), and left it open before suspend. It was still working after the resume.
Was this the full output? Error Type: <type 'exceptions.IOError'> Error Value: [Errno 30] Read-only file system File : /usr/lib/python2.6/site-packages/urlgrabber/grabber.py, line 1089, in _retrieve self.fo.write(buf)" I can certainly catch IOError, but I need to know where it came from.
I've added a load of catches for this exception whenever we do a low-level yum call in the PackageKit yum backend: commit 6f293f11aa49c0421cdc5a3a4035f6714299bd4c Author: Richard Hughes <richard> Date: Wed Apr 7 09:40:26 2010 +0100 yum: catch exceptions.IOError whenever we do a low-level yum call. Fixes rh#577549
(In reply to comment #1) > Was this the full output? > > Error Type: <type 'exceptions.IOError'> > Error Value: [Errno 30] Read-only file system > File : /usr/lib/python2.6/site-packages/urlgrabber/grabber.py, line 1089, in > _retrieve > self.fo.write(buf)" It seems that for some reason, the mount containing the yum cache was re-mounted readonly, ie due to something else ( ) an related error. I tried a few ways to fix that, but a reboot resolved it without further effort. > I can certainly catch IOError, but I need to know where it came from. /var/log/messages: shows: Mar 28 10:31:18 localhost kernel: EXT3-fs error (device dm-5): ext3_find_entry: reading directory #69124097 offset 0 Mar 28 10:31:18 localhost kernel: sd 2:0:0:0: [sdc] Unhandled error code Mar 28 10:31:18 localhost kernel: sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK Mar 28 10:31:18 localhost kernel: sd 2:0:0:0: [sdc] CDB: Read(10): 28 00 33 7c fa b0 00 00 08 00 Mar 28 10:31:18 localhost kernel: end_request: I/O error, dev sdc, sector 863828656 Mar 28 10:31:18 localhost kernel: EXT3-fs error (device dm-5): ext3_find_entry: reading directory #23855105 offset 0 Mar 28 10:31:18 localhost kernel: sd 2:0:0:0: [sdc] Unhandled error code Mar 28 10:31:18 localhost kernel: sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK Mar 28 10:31:18 localhost kernel: sd 2:0:0:0: [sdc] CDB: Read(10): 28 00 33 7c fa b0 00 00 08 00 Mar 28 10:31:18 localhost kernel: end_request: I/O error, dev sdc, sector 863828656 The trigger was possible due to multiple stanby-resume cycles.
PackageKit-0.6.4-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/PackageKit-0.6.4-1.fc13
PackageKit-0.6.4-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.