This bug was fixed in the package glibc - 2.7-10ubuntu1
---
glibc (2.7-10ubuntu1) hardy; urgency=low
* Merge remaining changes from 2.7-10 (r2869:2892).
* If RELEASE_UPGRADE_MODE is set to `desktop', make the
glibc/restart-services,
glibc/restart-failed and glibc/upgrade ques
this was fixed in -9ubuntu1/2 (unless debconf or cdebconf is not
installed), although the priority is still at `critical'. What could we
do further?
- lower the severity
- don't show the question at all, if we can create an update-notifier, and use
this one instead.
--
asks termnal question o
Moving to 8.04 final; this isn't going to be fixed for beta now.
** Changed in: glibc (Ubuntu)
Target: ubuntu-8.04-beta => ubuntu-8.04
--
asks termnal question on dapper->hardy upgrade
https://bugs.launchpad.net/bugs/174002
You received this bug notification because you are a member of Ub
Michael,
How do you define which is the "safe" course of action here - is it
safer to immediately reload gdm, or to leave it up to the user to reboot
and possibly have graphical logins stop working until that happens?
Did the dapper gdm allow all users to reboot the system from the login
screen,
that should be gone in the -9ubuntu1 merge
** Changed in: glibc (Ubuntu)
Assignee: (unassigned) => Matthias Klose (doko)
--
asks termnal question on dapper->hardy upgrade
https://bugs.launchpad.net/bugs/174002
You received this bug notification because you are a member of Ubuntu
Bugs, whic
I don't really know what the right course of action is here, but I think
that we can not ask this type of question during the upgrade. It is
recommended to reboot after the ugprade so whatever the safe course of
action is should be taken.
Cheers,
Michael
** Changed in: glibc (Ubuntu)
Importan
Hmm. We haven't done this with debconf before, since debconf isn't
essential in Debian. However, I do notice that it's part of ubuntu-
minimal, so we can probably consider that tool here.
Do the dist-upgrader hints get through to someone on a server-based
installation? In practice the things th
libc.preinst asks to restart services which cannot be restarted
automatically. Surely we can comment out this test and the dist-upgrader
hints the user to restart these services after an upgrade/system
restart. Just asking with debconf would force the restart of gdm, which
might not be the action w
