On 04/03/2013 11:44 AM, Tracer wrote:
----- Original Message -----
From: Aere Greenway
I use Lubuntu successfully on a 450 megahertz, 512 megabyte RAM,
HP-Vectra. It also worked in the past on it when I only had 384
megabytes of RAM.

Yet I use Lubuntu on all of my machines (that are faster and have more
RAM) because it's noticeably faster, and easier to do color customization.
Thanks, Aere. I have a few questions for anyone who can answer....

After a bit of struggle to install, Lubuntu 12.x runs on old hardware,
but boot-up is EXCRUCIATINGLY slow.
With Lubuntu 10.04 it is 17 seconds from power-on; that's FAST !!!
( Win XP 60 seconds, Ubuntu 40s, Arch 25s, Sabayon 95s )

I have no fears about security, because the data is on a USB HDD
which is rarely connected. And I can reinstall Lubuntu in no time.
And who would target Lubuntu ? ( Are there any millionaires here
amongst us ? I guess not. )
But I am afraid any new hardware like printer/ scanner/ camera, etc
will not be recognised/supported by 10.04 and then I'll have to
consider new processor ( when this one is still running like new )
or I should learn to fix my own kernel somewhat like GENTOO Linux.

Before either of those, I will try tweaking Lubuntu.
Should I try to update drivers in 10.04 or
Should I try to trim 13.x to make it faster ?
( WILL IT HAVE DRIVERS FOR OLD CHIPS???!!! )

WHich is easier & more practical ?

Thanks & BR
Tracey

Tracey:

On my 450 megahertz HP Vectra, it is slow booting, but not slow enough to begin to worry if it is hung.

I haven't timed it, but it is probably a little more than a minute.

The problem I have with Lubuntu (and Xubuntu) on the 450 mhz HP Vectra, is that when I go to apply updates (using the software updater), the software updates window goes away, and updates go on being applied in the background, without any information being given to me of that fact.

The only way I knew it was still running was from looking at the task manager, noticing what processes were running.

It also gives me no indication of when the updating process is completed, other than CPU usage going down.

I reported this problem as a software bug submission, but an Ubuntu person declared the bug to be invalid, because I was using a processor slower than 1 gigahertz, and with less than 1 gigabytes of RAM. He said that I should use xubuntu or lubuntu (apparently he didn't read my bug report to see that was what I was actually using).

So even if lubuntu runs on the slow processor, if they refuse to fix the software updater (or similar system software) because our processors are not up the the ridiculous minimum requirements of Ubuntu, perhaps we can't use the slow machines anymore anyway.

I am actually thinking of scrapping my slowest machine of my test-bed (the HP Vectra) because of that refusal to fix the problem, and because of how excruciatingly slow the process of installing and updating has become when using it.

Below is a copy of the e-mail where they declared the bug I reported to be invalid:

the official Ubuntu Documentation recommends a 1 GHz Pentium 4 with 1
gigabyte of RAM and 5 gigabytes of hard drive space, or better.[44] For
less powerful computers, there are other Ubuntu distributions such as
Lubuntu and Xubuntu.

this is not a bug, we just dont support you.

** Changed in: update-manager (Ubuntu)
       Status: New => Invalid

-- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1159589 Title: When applying software updates, updater window disappears Status in “update-manager” package in Ubuntu: Invalid Bug description: On slow machines (450 megahertz, with 512 megabytes RAM in this case), when you request to install the selected software updates, the system updater window disappears. Yet updates are being installed in the background, invisible to the user. The only clue there is that this is happening, is if you watch what processes are executing, using the task manager. Eventually (after a very long time on this machine), the CPU usage goes down to an idle state, yet no notification of a reboot being necessary appears (though a new kernel was one of the updates). If at that point, I bring up the software updater, it then informs me that a reboot is required. Similar symptoms to this occur on Ubuntu-Studio (Xubuntu) 12.04, except that the update manager window stays visible, and eventually says that a reboot is required. I want to watch the update process. I don't want it to happen in the background (with no notification that it is finished) - especially on this slow machine. This doesn't happen on any of my other machines running Lubuntu 12.10, or Ubuntu-Studio 12.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: update-manager 1:0.174.4 ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6 Uname: Linux 3.5.0-26-generic i686 ApportVersion: 2.6.1-0ubuntu10 Architecture: i386 Date: Sun Mar 24 19:17:55 2013 DpkgHistoryLog.txt: Start-Date: 2013-03-24 19:11:12 Commandline: /usr/sbin/synaptic Remove: linux-image-3.5.0-21-generic:i386 (3.5.0-21.32), linux-image-extra-3.5.0-22-generic:i386 (3.5.0-22.34), linux-image-3.5.0-22-generic:i386 (3.5.0-22.34), linux-image-extra-3.5.0-21-generic:i386 (3.5.0-21.32) End-Date: 2013-03-24 19:13:51 GsettingsChanges: b'com.ubuntu.update-manager' b'first-run' b'false' b'com.ubuntu.update-manager' b'launch-time' b'1364163135' b'com.ubuntu.update-manager' b'show-details' b'true' b'com.ubuntu.update-manager' b'window-height' b'500' b'com.ubuntu.update-manager' b'window-width' b'600' InstallationDate: Installed on 2012-05-11 (317 days ago) InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Release i386 (20120423.1) MarkForUpload: True PackageArchitecture: all SourcePackage: update-manager UpgradeStatus: Upgraded to quantal on 2012-10-19 (156 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1159589/+subscriptions


--
Sincerely,
Aere


--
Lubuntu-users mailing list
[email protected]
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users

Reply via email to