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

[Martin Schaaf]

Binary package hint: python2.6

This happened during the start of the gnome session.

ProblemType: Crash
Architecture: i386
Dependencies:
 libgcc1 1:4.3.3-5ubuntu4 [modified: lib/libgcc_s.so.1]
 zlib1g 1:1.2.3.3.dfsg-12ubuntu2 [modified: lib/libz.so.1.2.3.3]
 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/ld-2.9.so 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
ProcEnviron:
 SHELL=/bin/sh
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 LANGUAGE=de_DE:de:en_GB:en
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
UserGroups:

[Krzysztof Klimonda (kklimonda)]

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.

[xteejx (xteejx)]

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!