lubuntu-qa team mailing list archive

[Nio Wiklund <nio.wiklund@xxxxxxxxx>]

On 2013-09-16 10:56, Nio Wiklund 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
> 

1. I have installed a virtual machine using KVM, qemu, and virt-manager
according to a tip from Phill to use this wiki page

https://help.ubuntu.com/community/KVM/VirtManager

It is installed in the Lubuntu 64-bit saucy-daily system in my Toshiba
(describe above).

The KVM system can install Lubuntu 64-bit saucy-daily, and the installed
system works :-)

It is fast (and does not hang at the reboot button like the VBox system
does in my old Asus). It behaves very similar to installing and running
in a real system (only the old bug 966480).

-o-

2. I don't know, but I suspect that the desktop installer for the 64-bit
systems needs more RAM than the corresponding installer for 32-bits.
Could it be that 1.25 GB is not enough, so that the installer hangs
because of low RAM? And this is what causes VBox to fail? (I have only 2
GB in that old Asus host, a it might be hard to give more than 1.25 GB
to the guest (it is already complaining about it). Or could it be a bug
specifically for VBox?

Can someone test with VBox and various amounts of RAM allocated, also
more than 1.25GB?

Best regards
Nio