python2.6 crashed with IOError: [Errno 30] Read-only file system

Bug #368058 reported by Martin Schaaf on 2009-04-27
This bug affects 1 person
Affects Status Importance Assigned to Milestone
sbackup (Ubuntu)

Bug Description

Binary package hint: python2.6

This happened during the start of the gnome session.

ProblemType: Crash
Architecture: i386
 libgcc1 1:4.3.3-5ubuntu4 [modified: lib/]
 zlib1g 1: [modified: lib/]
 gcc-4.3-base 4.3.3-5ubuntu4
 findutils 4.4.0-2ubuntu4 [modified: usr/bin/xargs usr/bin/find usr/bin/oldfind]
 libc6 2.9-4ubuntu6 [modified: lib/ usr/lib/pt_chown usr/bin/iconv usr/bin/getent usr/bin/getconf usr/bin/localedef usr/bin/locale usr/bin/zdump usr/bin/rpcinfo usr/sbin/zic usr/sbin/iconvconfig]
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/python2.6
InterpreterPath: /usr/bin/python2.6
Package: python2.6-minimal 2.6.2-0ubuntu1 [modified: usr/bin/python2.6]
ProcCmdline: /usr/bin/python /usr/sbin/sbackupd
 PATH=(custom, no user)
PythonArgs: None
SourcePackage: python2.6
Title: python2.6 crashed with IOError: [Errno 30] Read-only file system
Traceback: IOError: [Errno 30] Read-only file system
Uname: Linux 2.6.28-11-generic i686

Martin Schaaf (mascha) wrote :
tags: removed: need-duplicate-check
Martin Schaaf (mascha) on 2009-04-27
visibility: private → public
Krzysztof Klimonda (kklimonda) wrote :

It doesn't seem to be a python error - more likely sbackupd doesn't catch an exception at some point.
Also there is not enough data - Could you provide a full traceback?
Probably either a partition you were doing backup to or the one you were backing up was mounted in read-only mode. Either because of mount flags or because of some filesystem failure.

affects: python2.6 (Ubuntu) → sbackup (Ubuntu)
Changed in sbackup (Ubuntu):
status: New → Incomplete

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in sbackup (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers