lubuntu-qa team mailing list archive

[Nio Wiklund <nio.wiklund@xxxxxxxxx>]

Hi everybody,

Finally, I tested the newest daily build (Sep 17 2013) of the 32-bit
Lubuntu saucy-desktop-i386.iso

in the same machine and with the same conditions.

RAM = 384, 512 MB, 768 MB

Finished gracefully, but froze after I clicked reboot. Working system
installed.

RAM = 1024 MB

No freeze, but waiting for Enter without any text prompting for it, bug
966480.

This is only slightly better than the 64-bit version, and it is much
worse that during early Saucy alpha (or pre-alpha) stages, when the
32-bit desktop installer for Lubuntu might work with 384 MB RAM, and
definitely worked with 512 MB RAM.

So I think *something bad is happening* when Lubuntu is to be switched
off. Nik Th and I have also noted that shutdown is much slower than it
used to be (also compared to earlier versions of Saucy).

The One Button Installer can do it with 128 MB RAM. I made a test right
now in this same Toshiba, and installed Saucybeta1.

Best regards
Nio

On 2013-09-18 11:08, Nio Wiklund wrote:
> Hi again,
> 
> This time testing the newest daily build (Sep 17 2013) of
> 
> saucy-desktop-amd64.iso
> 
> in my Toshiba (a direct install, no virtualisation)
> 
> http://www.toshiba.se/laptops/satellite-pro/c850/satellite-pro-c850-19w/
> 
> using mem=xxxM to limit the RAM usage
> 
> RAM = 512 MB, 768 MB and 1024 MB
> 
> 1. Finished gracefully, but froze after I clicked reboot. Working system
> installed (available after 'force reboot' looooong press of power
> button, SysRq REISUB not responding).
> 
> 2. Tried again and it froze very early, before copying files.
> 
> 3. Powered off for a long time. Removed the USB pendrive. Tried again
> and had the same result as the first time: Finished gracefully. I could
> peek behind the curtain with ctrl+alt+F1: I could see that a lot of data
> were swapped (more than 250 MB), which might not be available in a
> virtual system with a small virtual disk.
> 
> But it froze after I clicked reboot ... as the first time
> 
> Something in the system remembers old data. It seems that all variables
> are not initiated, which is a horrible bug. I've had such problems long
> ago, when I was developing and debugging programs. It is hard to tell if
> it is some firmware, the BIOS or Lubuntu that is guilty.
> 
> Tried only once with 768 MB RAM and 1024 MB: Finished gracefully, but
> froze after I clicked reboot.
> 
> RAM 1280 MB
> 
> Finished gracefully, and no freeze. "Please remove ... and press Enter"
> not visible because graphics mode, bug 966480. And it did reboot after
> pressing Enter. Working system installed.
> --
> Comment 1: Install was selected directly at the syslinux screen (not via
> live desktop). I did not use the mouse only keyboard keys, and used the
> very simplest install 'use the whole disk'.
> 
> Comment 2: at RAM = 1280 MB KVM behaved like the real computer except
> that plymouth run in graphical mode in the real computer, but in text
> mode in KVM.
> 
> Comment 3:
> 
> The options at the login screen work after logout only in the live
> session, but not in the installed system. But after installing
> 
> sudo add-apt-repository ppa:lightdm-gtk-greeter-team/daily
> 
> according to this mail from nikth, some of the options work (for example
> to select session, but the one for high contrast works for me only at
> the log in screen, never in the sessions).
> 
> -------- Original Message --------
> Subject: 	Bug #1213837 (I cannot select an Xsession after logout from
> Lubuntu Saucy Daily) - Fix Committed
> Date: 	Wed, 18 Sep 2013 04:18:03 +0200
> From: 	Nik Th <nikth@xxxxxxx>
> To: 	lubuntu-qa@xxxxxxxxxxxxxxxxxxx
> CC: 	lubuntu users mailing list <lubuntu-users@xxxxxxxxxxxxxxxx>
> 
> Thanks to all who participated and involved to this bug[1], now has been
> resolved.
> 
> A Fix committed to the package "lightdm-gtk-greeter" version 1.6.1 and
> the problem gone.
> 
> You can check it right away, by opening a terminal and apply the
> following commands (in order to upgrade to 1.6.1 version)
> 
> sudo add-apt-repository ppa:lightdm-gtk-greeter-team/daily
> sudo apt-get update
> sudo apt-get -y dist-upgrade
> 
> [1] -
> https://bugs.launchpad.net/ubuntu/+source/lightdm-gtk-greeter/+bug/1213837
> 
> Regards
> NikTh
> ----------------------------------------
> 
> Best regards
> Nio
> 
> On 2013-09-18 08:27, Nio Wiklund wrote:
>> Hi,
>>
>> Back to saucy-desktop amd64 16th Sept build... Just done trying install
>> on KVM (and default graphics) with
>>
>> RAM = 512 MB
>>
>> Froze early while copying files. No system installed.
>>
>> RAM = 784 MB and 1024 MB
>>
>> Finished gracefully, but froze after I clicked reboot. Working system
>> installed (available after 'force reboot').
>>
>> RAM = 1280 MB
>>
>> Finished gracefully, and no freeze. "Please remove ... and press Enter"
>> visible because text mode. And it did reboot after pressing Enter.
>> Working system installed.
>> --
>> Comment 1: Install was selected directly at the syslinux screen (not via
>> live desktop). I did not use the mouse only keyboard keys, and used the
>> very simplest install 'use the whole disk'.
>>
>> Comment 2: at RAM = 1280 MB VBox behaved like KVM at RAM = 784 MB and
>> 1024 MB, and I think this indicated problems because of low RAM. The
>> different levels of RAM is probably due to differences in configuration
>> of the virtual machines.
>> -----
>> I plan to continue testing in a real computer now.
>>
>> Best regards
>> Nio
>>
>> On 2013-09-17 22:58, Phill Whiteside wrote:
>>> Back to saucy-desktop amd64 16th Sept build... Just done an install on
>>> VBox with RAM = 1Gb. No hang at reboot, got the message to remove the CD
>>> and hit Enter... Rebooted fine and is a happy little VBox 13.10 lubuntu :D
>>>
>>> Thanks Sergio, you came onto IRC to answer how much RAM you use just at
>>> the right time!!!
>>>
>>> Regards,
>>>
>>> Phill.
>>>
>>>
>>>
>>> On 17 September 2013 21:54, Phill Whiteside <PhillW@xxxxxxxxxx
>>> <mailto:PhillW@xxxxxxxxxx>> wrote:
>>>
>>>     Hi,
>>>
>>>     yeah, we 're all good at complaining :P It really is a case of keep
>>>     an eye on which kernel you're on. kernel freeze 
>>>
>>>     Thurs Oct 03 - Kernel Freeze (~2 weeks away)
>>>
>>>     So, everyone.. keep your eyes open and ensure you do dist-upgrades
>>>     to running 13.10 instances and zsync up your ISO's before testing....
>>>
>>>     And also worth a
>>>     mention https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1213837 the
>>>     fix is in PPA for anyone who wants to check it out.
>>>
>>>     Regards,
>>>
>>>     Phill.
>>>
>>>
>>>     On 17 September 2013 21:46, Lars Noodén <lars.nooden@xxxxxxxxx
>>>     <mailto:lars.nooden@xxxxxxxxx>> wrote:
>>>
>>>         On 09/17/2013 11:41 PM, Phill Whiteside wrote:
>>>         > Hi Lars,
>>>         >
>>>         > confused @ phillw ...
>>>         >
>>>         http://iso.qa.ubuntu.com/qatracker/milestones/302/builds/52687/testcases
>>>         >
>>>         > Regards,
>>>         >
>>>         > Phill.
>>>
>>>         There were apparently no freezes on those days.  (If I recall
>>>         correctly.)  I'm usually good about complaining if something
>>>         goes awry.
>>>          As mentioned in the other thread, I can't get the freezes to
>>>         happen on
>>>         demand.
>>>
>>>         Regards,
>>>         /Lars
>