[Bug 1027648] Re: ubiquity crashed with ValueError in command(): I/O operation on closed file.
cjwatson at canonical.com
Tue Sep 25 22:29:25 UTC 2012
I've backported Dmitrijs' fix to our precise-proposed bzr branch.
** Changed in: ubiquity (Ubuntu Precise)
Status: Confirmed => In Progress
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
ubiquity crashed with ValueError in command(): I/O operation on closed
Status in “ubiquity” package in Ubuntu:
Status in “ubiquity” source package in Precise:
Status in “ubiquity” source package in Quantal:
I use Ubuntu12.10 Qantal daily build amd64 from 22.7.2012.
This occures on a installation try from a usb stick.
To be exactly on clicking the abort button on the Install Type
dialog(Whole disk, paritioning...).
This is the first time that I observe this on this daily build(some
runs this day).
So, I have no reliable reproducing procedure.
DistroRelease: Ubuntu 12.10
Package: ubiquity 2.11.17
ProcVersionSignature: Ubuntu 3.5.0-5.5-generic 3.5.0-rc7
Uname: Linux 3.5.0-5-generic x86_64
Date: Sun Jul 22 15:11:28 2012
InstallCmdLine: noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120718.1)
ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity gtk_ui
ProcEnviron: Error: [Errno 13] Permission denied: '/proc/15722/environ'
PythonArgs: ['/usr/lib/ubiquity/bin/ubiquity', 'gtk_ui']
Title: ubiquity crashed with ValueError in command(): I/O operation on closed file.
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
More information about the foundations-bugs