Ubuntu QA:
BlogBrainstormPackage status
Log in
Ubuntu QA
Update manager
Idea sandbox Idea sandbox
Popular ideas Popular ideas
Ideas in development Ideas in development
Implemented ideas Implemented ideas

Popular ideas Here are this month's most popular ideas about Update manager. New to Brainstorm? Learn how it works!

Update manager should notify in advance if installing updates needs rebooting.  
Written by amoalsale the 3 May 12 at 04:52. New
Many times when we get notification that updates are available for the system we often click on install update button without even looking at the details as we know keeping the system up-to-date keeps it stable. But many times once updating is finished systems asks for reboot and everytime its not possible to reboot immediately. For example when we are working on remote sessions on telnet or ssh or editing something important on internet.
It may also be observed that untill you do not reboot the system it behaves irratically.
26
votes
up equal down
Solution #1: Update manager should notify if updates require reboot.
Written by amoalsale the 3 May 12 at 04:52.
a simple notification like
"Installing these updates will require reboot"
should be shown in advance.
5
votes
up equal down
Solution #2: Service restart
Written by benoyanthony the 15 May 12 at 10:09.
Other than complete reboot, system should initiate service restart with confirmation from user.

See the 5 comments or propose a solution >>

The update-manager is very outdated  
Written by fernando_silva the 2 May 12 at 00:43. New
The update-manager is very outdated and it's not integrated with the rest of the system.
6
votes
up equal down
Solution #1: Integrate the update-manager to the "Software Centre"
Written by fernando_silva the 2 May 12 at 00:43.
Add an new item on the top of the "Software Centre", on the right side, called "System Updates", and create a more simple user-interface for the update-manager, integrated to the "Software Centre".

See the 5 comments or propose a solution >>

Include prior kernels in the repositories  
Written by lewac the 7 May 12 at 15:38. New
Recently we upgraded to 12.04 from 11.10, kubuntu 32 bit. And lost google-earth in the process (OS freezes). There's a bug report on it but its not fixed yet. So to make things a bit easier why not retain a coupla previous kernels within the repositories? That way what worked prior to updates/upgrades will probably work again (if it happens to be a kernel issue like this one).

One may require some type of "Regress" checkbox within the package maintainers (synaptic, muon, whatever)... or a new source list could be implemented to make the prior kernel(s) available.

Of course would not normally regress unless a specific app critical to normal usage went bust from a subsequent kernel update (such as was my (and many others) situation).
3
votes
up equal down
Solution #1: Add a repository
Written by lewac the 7 May 12 at 15:38.
which would include at least a couple of past kernels.

See the 1 comments or propose a solution >>