EEE pc 701 on my side I can start ubiquity and get it to the installer
- didn't try to install anything yet though -
it seems to be running fine for me - alpha3 - using unetbooting on
fat16 usbstick
On Sun, Feb 13, 2011 at 3:11 PM, danstowell <email address hidden> wrote:
> UH I get a really bad crash when I try ubiquity now. (Seems to kill X.)
> Can someone please report back: have you successfully run ubiquity from
> a gazpacho alpha?
>
> --
> 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.
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~puredyne-team
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~puredyne-team
> More help : https://help.launchpad.net/ListHelp
>
EEE pc 701 on my side I can start ubiquity and get it to the installer
- didn't try to install anything yet though -
it seems to be running fine for me - alpha3 - using unetbooting on
fat16 usbstick
On Sun, Feb 13, 2011 at 3:11 PM, danstowell <email address hidden> wrote: /bugs.launchpad .net/bugs/ 712659 ubiquity/ source live/filesystem .squashfs ubiquity/ source live/filesystem .squashfs /var/lib/ ubiquity/ source ubiquity/ install. py", line 608, in <module> ubiquity/ install. py", line 122, in run ubiquity/ install. py", line 299, in copy_all exists( fs_size) , "Missing filesystem.size." _______ _______ _______ _______ _______ _____ /launchpad. net/~puredyne- team /launchpad. net/~puredyne- team /help.launchpad .net/ListHelp
> UH I get a really bad crash when I try ubiquity now. (Seems to kill X.)
> Can someone please report back: have you successfully run ubiquity from
> a gazpacho alpha?
>
> --
> You received this bug notification because you are a member of puredyne
> team, which is the registrant for Puredyne Live.
> https:/
>
> 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/
> 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/
> 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/
> 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/
> 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/
> Feb 3 16:48:55 puredyne python: install.run()
> Feb 3 16:48:55 puredyne python: File "/usr/share/
> Feb 3 16:48:55 puredyne python: self.copy_all()
> Feb 3 16:48:55 puredyne python: File "/usr/share/
> Feb 3 16:48:55 puredyne python: assert os.path.
> 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.
>
>
>
> _______
> Mailing list: https:/
> Post to : <email address hidden>
> Unsubscribe : https:/
> More help : https:/
>