lubuntu-qa team mailing list archive

[Nio Wiklund <nio.wiklund@xxxxxxxxx>]

Hi Phill and Ali,

It looks like it could be a problem with low RAM. The installer cannot
not handle it in a proper way, so it 'hangs'. Fortunately it has already
finished writing the installation to disk.

I did not mention it before, but I was 'managed to' make it hang earlier
(in VBox), and then there was no complete installation (it would not
boot). I think the 32-bit desktop installer needs less RAM than this
64-bit version.

I'll also try tomorrow with the boot option mem=xxxM in a real computer.
But it is good if many people try, so please try Ali :-)

Best regards
Nio


On 2013-09-17 20:56, Phill Whiteside wrote:
> Hi,
> 
> lubuntu-desktop-amd64 16th Sept build
> 
> with 512Mb in Vbox I observed the following.. 
> 'Try Lubuntu' started fine, but completely hangs when asked to reboot.
> 'Install Lubuntu' worked fine, but hangs when rebooting at the end of
> the install process. Doing a force reset re-starts the install, but you
> can now eject the 'cd' and a further force reset starts the VBox okay.
> Reboot and Shutdown then function okay.
> 
> with 512 in KVM I observed the following...
> 'Try Lubuntu' starts fine and reboots fine.
> 'Install Lubuntu' works fine, reboot at end of install hangs. Force
> reset and then start boots into the normal desktop. Further reboots are
> okay.
> 
> I'm going to ask Ali to try this on actual hardware to see if it is a
> gremlin in virtualisation or is a bug at the end of the installer.
> 
> @ Ali, can you please test on 'real' hardware and report back - Thanks!
> 
> Regards,
> 
> Phill.
> 
> 
> 
> 
> 
> On 17 September 2013 18:22, Phill Whiteside <PhillW@xxxxxxxxxx
> <mailto:PhillW@xxxxxxxxxx>> wrote:
> 
>     The alternates work fine with 512MB ram in both VBox and KVM, I'm
>     just downloading the desktop one to repeat the tests.
> 
>     Regards,
> 
>     Phill.
> 
> 
>     On 17 September 2013 18:16, Nio Wiklund <nio.wiklund@xxxxxxxxx
>     <mailto:nio.wiklund@xxxxxxxxx>> wrote:
> 
>         Kjetil,
> 
>         Do you think our problems depended on too low RAM in VBox?
> 
>         Best regards
>         Nio
> 
>         On 2013-09-17 19:00, Kjetil brinchmann Halvorsen wrote:
>         > I have now tried monday nights' daily (amd64), and now it
>         worked. But
>         > the I specified a virtual machine with 4GB of ram.
>         >
>         > Kjetil
>         >
>         > On Mon, Sep 16, 2013 at 10:56 AM, Nio Wiklund
>         <nio.wiklund@xxxxxxxxx <mailto:nio.wiklund@xxxxxxxxx>> wrote:
>         >> On 2013-09-16 10:40, Jörn Schönyan wrote:
>         >>> I had Kubuntu Saucy installed on my machine, a normal
>         install without
>         >>> virtualization. After updating, LightDM failed at boot. Endless
>         >>> Plymouth-screen. When I pressed Escape, I could read the
>         boot messages
>         >>> which stated that LightDM failed.
>         >>>
>         >>> I reported that bug, but noone else seems to have the
>         problem. My
>         >>> temporary workaround was logging into tty1 and startx.
>         >>>
>         >>> Am Montag, 16. September 2013, 10:19:59 schrieben Sie:
>         >>>> Joern,
>         >>>>
>         >>>> I have the installed system in the vbox now. I can retry
>         installing
>         >>>> again. So please describe exactly what you want, and at
>         what stage!
>         >>>
>         >> I installed the same Lubuntu saucy daily desktop amd64 system
>         into my
>         >> Toshiba in CSM mode
>         >>
>         >>
>         http://www.toshiba.se/laptops/satellite-pro/c850/satellite-pro-c850-19w/
>         >>
>         >> It worked better than vbox. It hangs in a different way. The
>         screen with
>         >> the message is closed, the graphical screen is shut down and
>         it hangs at
>         >> the text screen with one single message line:
>         >>
>         >> * Asking all remaining processes to terminate... [OK]
>         >>
>         >> And when I press Enter, it will reboot. So in the Toshiba, it
>         seems to
>         >> be the old bug, that there is no message to remove the boot
>         media and
>         >> press Enter, bug 966480.
>         >>
>         >> The installation was into a CSM system (not UEFI).
>         >>
>         >> The installed system boots and runs without any problem (that
>         I have
>         >> discovered yet).
>         >>
>         >> Best regards
>         >> Nio