Thanks for your bugreport.
This bit in the logs indicate that for some reason the filesystem got remounted
read/only might be because of filesystem corruption or a hardwar e problem.
Could you please run fsck and check the output of dmesg?
"""
Preparing to replace metacity-common 1:2.18.2-0ubuntu1.1 (using
.../metacity-common_1%3a2.20.0-0ubuntu3_all.deb) ...
(gconftool-2:17346): GConf-CRITICAL **: Failed to load file
"/var/lib/gconf/defaults/%gconf-tree-ru.xml": Error reading
"/var/lib/gconf/defaults/%gconf-tree-ru.xml": Input/output error
Traceback (most recent call last):
File "/usr/sbin/gconf-schemas", line 55, in <module>
shutil.rmtree(tmp_home)
File "/usr/lib/python2.5/shutil.py", line 178, in rmtree
onerror(os.rmdir, path, sys.exc_info())
File "/usr/lib/python2.5/shutil.py", line 176, in rmtree
os.rmdir(path)
OSError: [Errno 30] Read-only file system: '/tmp/gconf-PPKegQ'
dpkg: warning - old pre-removal script returned error exit status 1
dpkg - trying script from the new package instead ...
dpkg: ... it looks like that went OK.
dpkg: error processing
/var/cache/apt/archives/metacity-common_1%3a2.20.0-0ubuntu3_all.deb (--unpack):
unable to flush updated status of `metacity-common': Read-only file system
Traceback (most recent call last):
"""
** Changed in: update-manager (Ubuntu)
Status: New => Incomplete
** Summary changed:
- Upgrade to 0710 crashed
+ hardware problem/fs-corruption? (was: Upgrade to 0710 crashed)
--
hardware problem/fs-corruption? (was: Upgrade to 0710 crashed)
https://bugs.launchpad.net/bugs/154857
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
