puredyne-team team mailing list archive
-
puredyne-team team
-
Mailing list archive
-
Message #01541
[Bug 712659] [NEW] Ubiquity 2.4.8 crash on Eee 701
Public bug reported:
Ubiquity 2.4.8 crashes on my Eee 701. This is from /var/syslog:
Feb 3 16:48:54 puredyne python: mkdir /var/lib/ubiquity/source
Feb 3 16:48:54 puredyne ubiquity: /dev/loop1
Feb 3 16:48:54 puredyne ubiquity: : No such file or directory
Feb 3 16:48:54 puredyne python: log-output -t ubiquity losetup /dev/loop1#012 /live/image/live/filesystem.squashfs
Feb 3 16:48:54 puredyne ubiquity: mount: special device /dev/loop1
Feb 3 16:48:54 puredyne ubiquity: does not exist
Feb 3 16:48:54 puredyne ubiquity:
Feb 3 16:48:54 puredyne python: log-output -t ubiquity mount /dev/loop1#012 /var/lib/ubiquity/source
Feb 3 16:48:54 puredyne ubiquity: loop: can't delete device /dev/loop1
Feb 3 16:48:54 puredyne ubiquity: : No such file or directory
Feb 3 16:48:54 puredyne python: log-output -t ubiquity losetup -d /dev/loop1
Feb 3 16:48:54 puredyne python: log-output -t ubiquity mount -o loop /live/image/live/filesystem.squashfs /var/lib/ubiquity/source
Feb 3 16:48:55 puredyne python: Exception during installation:
Feb 3 16:48:55 puredyne python: Traceback (most recent call last):
Feb 3 16:48:55 puredyne python: File "/usr/share/ubiquity/install.py", line 608, in <module>
Feb 3 16:48:55 puredyne python: install.run()
Feb 3 16:48:55 puredyne python: File "/usr/share/ubiquity/install.py", line 122, in run
Feb 3 16:48:55 puredyne python: self.copy_all()
Feb 3 16:48:55 puredyne python: File "/usr/share/ubiquity/install.py", line 299, in copy_all
Feb 3 16:48:55 puredyne python: assert os.path.exists(fs_size), "Missing filesystem.size."
Feb 3 16:48:55 puredyne python: AssertionError: Missing filesystem.size.
Feb 3 16:48:55 puredyne python:
This is similar to problems we've had in the past, though I haven't found the right info in the archives yet. Previously the solution was to update ubiquity from 2.0.7 to 2.0.9 but we're way beyond that now.
** Affects: puredyne-live
Importance: Critical
Status: New
** Changed in: puredyne-live
Importance: Undecided => Critical
** Changed in: puredyne-live
Milestone: None => 10.10
--
You received this bug notification because you are a member of puredyne
team, which is the registrant for Puredyne Live.
https://bugs.launchpad.net/bugs/712659
Title:
Ubiquity 2.4.8 crash on Eee 701
Status in Puredyne liveCD/DVD/USB/HD:
New
Bug description:
Ubiquity 2.4.8 crashes on my Eee 701. This is from /var/syslog:
Feb 3 16:48:54 puredyne python: mkdir /var/lib/ubiquity/source
Feb 3 16:48:54 puredyne ubiquity: /dev/loop1
Feb 3 16:48:54 puredyne ubiquity: : No such file or directory
Feb 3 16:48:54 puredyne python: log-output -t ubiquity losetup /dev/loop1#012 /live/image/live/filesystem.squashfs
Feb 3 16:48:54 puredyne ubiquity: mount: special device /dev/loop1
Feb 3 16:48:54 puredyne ubiquity: does not exist
Feb 3 16:48:54 puredyne ubiquity:
Feb 3 16:48:54 puredyne python: log-output -t ubiquity mount /dev/loop1#012 /var/lib/ubiquity/source
Feb 3 16:48:54 puredyne ubiquity: loop: can't delete device /dev/loop1
Feb 3 16:48:54 puredyne ubiquity: : No such file or directory
Feb 3 16:48:54 puredyne python: log-output -t ubiquity losetup -d /dev/loop1
Feb 3 16:48:54 puredyne python: log-output -t ubiquity mount -o loop /live/image/live/filesystem.squashfs /var/lib/ubiquity/source
Feb 3 16:48:55 puredyne python: Exception during installation:
Feb 3 16:48:55 puredyne python: Traceback (most recent call last):
Feb 3 16:48:55 puredyne python: File "/usr/share/ubiquity/install.py", line 608, in <module>
Feb 3 16:48:55 puredyne python: install.run()
Feb 3 16:48:55 puredyne python: File "/usr/share/ubiquity/install.py", line 122, in run
Feb 3 16:48:55 puredyne python: self.copy_all()
Feb 3 16:48:55 puredyne python: File "/usr/share/ubiquity/install.py", line 299, in copy_all
Feb 3 16:48:55 puredyne python: assert os.path.exists(fs_size), "Missing filesystem.size."
Feb 3 16:48:55 puredyne python: AssertionError: Missing filesystem.size.
Feb 3 16:48:55 puredyne python:
This is similar to problems we've had in the past, though I haven't found the right info in the archives yet. Previously the solution was to update ubiquity from 2.0.7 to 2.0.9 but we're way beyond that now.
Follow ups
References