All:
The original bug (in the attached e-mail) was declared invalid because
it happened on a machine that doesn't meet the minimum system
requirements of Ubuntu/Unity-Desktop, even though I was using Lubuntu.
I since observed it to occur on a machine within the Ubuntu minimum
system requirements, and the attached e-mail came as a result of
reporting that event.
Yet the bug:
https://bugs.launchpad.net/bugs/1159589
Still shows up as being invalid.
I am wondering if once a bug is declared to be invalid, that nobody ever
sees it again, or any additional information posted to it - kind of a
black-hole that sucks up any additional information, consigning it to
some bit-bucket.
In light of the fact that I was using Lubuntu in the first place, and
that I have observed it happening on a machine running Ubuntu
Unity-Desktop (and within the minimum system requirements of
Ubuntu/Unity), is there any way the bug can be re-classified as
something that needs to be looked at?
- Aere
--- Begin Message ---
I just observed this problem on a 1.7 gigahertz machine having 1
gigabytes of RAM, which is within the minimum system requirements you
used as your rationale for ignoring the problem.
The system was reporting a crash in the system-updates notifier
(apport), and apparently that slowed down the system enough to expose
the bug, even on this faster machine.
--
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
--- End Message ---
--
Mailing list: https://launchpad.net/~lubuntu-qa
Post to : lubuntu-qa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~lubuntu-qa
More help : https://help.launchpad.net/ListHelp
