I can try this weekend with 17.10, I never could install 17.10 via ISO
because my usb wifi stopped working there right at the installation also. I
spent several hours trying to understand the problem, but i couldn't.
Do you want me to test the ISO install of 17.10 this weekend and reply back
in this e-mail?
Cheers
On Wed, Oct 18, 2017 at 4:37 AM, Simon Quigley <email address hidden> wrote:
> Is this still an issue with the 17.10 ISO?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1699671).
> https://bugs.launchpad.net/bugs/1638420
>
> Title:
> LVM install with Lubuntu fails due to missing lvm2 package
>
> Status in Lubuntu Next:
> New
> Status in lubuntu-meta package in Ubuntu:
> Triaged
>
> Bug description:
> Attempting to install Lubuntu using LVM crashes because the lvm2
> package is missing from the image.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/lubuntu-next/+bug/1638420/+subscriptions
>
I can try this weekend with 17.10, I never could install 17.10 via ISO
because my usb wifi stopped working there right at the installation also. I
spent several hours trying to understand the problem, but i couldn't.
This is the card: /www.newegg. com/Product/ Product. aspx?Item= N82E16833320089
https:/
Do you want me to test the ISO install of 17.10 this weekend and reply back
in this e-mail?
Cheers
On Wed, Oct 18, 2017 at 4:37 AM, Simon Quigley <email address hidden> wrote:
> Is this still an issue with the 17.10 ISO? /bugs.launchpad .net/bugs/ 1638420 /bugs.launchpad .net/lubuntu- next/+bug/ 1638420/ +subscriptions
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1699671).
> https:/
>
> Title:
> LVM install with Lubuntu fails due to missing lvm2 package
>
> Status in Lubuntu Next:
> New
> Status in lubuntu-meta package in Ubuntu:
> Triaged
>
> Bug description:
> Attempting to install Lubuntu using LVM crashes because the lvm2
> package is missing from the image.
>
> To manage notifications about this bug go to:
> https:/
>