Hello Timo,
Timo Aaltonen <[EMAIL PROTECTED]> writes:
> The log wasn't that helpful.. Unless you have ideas I can only close the
> bug :)
Could the screen saver might have played a role? I wasn't in front of
the computer during the whole update so the screen saver has started
several times.
Otherwise, I've gone through the log files and found this in
/var/log/apport.log.4.gz:
apport (pid 20697) Wed Dec 26 14:12:25 2007: called for pid 5498, signal 11
apport (pid 20697) Wed Dec 26 14:12:25 2007: Unhandled exception:
Traceback (most recent call last):
File "/usr/share/apport/apport", line 275, in <module>
info.add_proc_info(pid)
File "/var/lib/python-support/python2.5/apport/report.py", line 368, in
add_proc_info
assert os.path.exists(self['ExecutablePath'])
File "posixpath.py", line 171, in exists
st = os.stat(path)
TypeError: stat() argument 1 must be (encoded string without NULL bytes), not
str
pid: 20697, uid: 1000, gid: 1000, euid: 0, egid: 0
environment: {'CORE_GID': '1000', 'CORE_TIME': '1198674744', 'CORE_EXECUTABLE':
'gnome-panel', 'CORE_HOSTNAME': 'morgana', 'CORE_SIGNAL': '11',
'CORE_REAL_RLIM': '0', 'CORE_PID': '5498', 'CORE_UID': '1000'}
apport (pid 20734) Wed Dec 26 14:12:29 2007: called for pid 4830, signal 6
apport (pid 20734) Wed Dec 26 14:12:29 2007: Unhandled exception:
Traceback (most recent call last):
File "/usr/share/apport/apport", line 275, in <module>
info.add_proc_info(pid)
File "/var/lib/python-support/python2.5/apport/report.py", line 368, in
add_proc_info
assert os.path.exists(self['ExecutablePath'])
File "posixpath.py", line 171, in exists
st = os.stat(path)
TypeError: stat() argument 1 must be (encoded string without NULL bytes), not
str
pid: 20734, uid: 0, gid: 0, euid: 0, egid: 0
environment: {'CORE_GID': '0', 'CORE_TIME': '1198674748', 'CORE_EXECUTABLE':
'Xorg', 'CORE_HOSTNAME': 'morgana', 'CORE_SIGNAL': '6', 'CORE_REAL_RLIM': '0',
'CORE_PID': '4830', 'CORE_UID': '0'}
Could it be related, especially the second report?
> Possibly you were just unlucky that the crash happened during
> update. It could be a hardware problem that makes the system crash under
> load (the update progressed for about an hour, which means intense disk
> access and cpu usage).
Maybe. But I had this hardware for years and never had an issue with it.
Yours,
d.
--
X crashes while upgrading from Feisty to Gutsy
https://bugs.launchpad.net/bugs/179515
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
