It might have been a different crash from this one, though. Feel free to
report that separately.
--
[apport] oem-config crashed with IOError in cleanup()
https://bugs.launchpad.net/bugs/99211
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
oem-config (1.14) gutsy; urgency=low
* Add an apport hook to attach /var/log/oem-config.log.
* Strip binaries.
* Print usage message and exit if any non-option arguments are supplied to
oem-config; suggest oem-config-prepare (LP: #105940).
* Update Japanese keyboard layout handling to
Are you sure you're running oem-config as root (with sudo)? The crash
dump indicates that you're actually running it as the oem user.
(Yes, oem-config should fail more gracefully in this case.)
--
[apport] oem-config crashed with IOError in cleanup()
https://bugs.launchpad.net/bugs/99211
You
Quoting Colin Watson ([EMAIL PROTECTED]):
Are you sure you're running oem-config as root (with sudo)? The crash
dump indicates that you're actually running it as the oem user.
(Yes, oem-config should fail more gracefully in this case.)
I tried both:
sudo oem-config
and
sudo -s
oem-config
** Attachment added: Dependencies.txt
http://librarian.launchpad.net/7079290/Dependencies.txt
** Attachment added: ProcMaps.txt
http://librarian.launchpad.net/7079291/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://librarian.launchpad.net/7079292/ProcStatus.txt
** Attachment
Time was right (time is flying when you're having fun ;-)
I upgraded the machine (aptitude update; aptitude dist-upgrade)
reboot with latest kernel/xserver etc but still no go.
Installed strace and output is added to this bug report
** Attachment added: strace oem-config
