Marking glibc as invalid then.
** Changed in: glibc (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/223226
Title:
Upgrade from kubuntu Dapper requires manual
Dapper to Hardy upgrades are no longer supported for Kubuntu, so marking
kdm wontfix.
** Changed in: kdebase (Ubuntu)
Status: Confirmed = Won't Fix
--
Upgrade from kubuntu Dapper requires manual intervention and kdm shutdown
https://bugs.launchpad.net/bugs/223226
You received this bug
So why does it take six months to get a one-line change made to a single
web page???
Hmm well, there's a limited number of eyes looking at bugs and of people
fixing things, so patience is a virtue. You did mention you're impatient
though. :-)
Then again, it seems the fact that 'kdm' did require
KDM doesn't require manual stopping.
NSS is, KDM uses NSS so glibc suggests to restart KDM.
I am still thinking about this, but in my humble opinion this is really
an issue with the wording of the libc6 posinst script. It should advise
to do a KDM restart _after_ the upgrade. It really doesn't
On Mon, 6 Oct 2008, kko wrote:
So why does it take six months to get a one-line change made to a single
web page???
Hmm well, there's a limited number of eyes looking at bugs and of people
fixing things, so patience is a virtue. You did mention you're impatient
though. :-)
Yes, I posess
Thank you kko for confirming this bug and parsing the evidence out of the
log file for easy readibility.
I gave a suggested resolution in one of my first posts: A one-line warning
in the web page, instructing the user to use the server update process
from a console TTY, not from an terminal
To be clear:
For me, the issue with having to *shutdown* kdm *prior* to doing the
upgrade is separate from the issue of configuring 'libpam0g'. I don't
think I even had the dialog about libpam0g.
What I did have, however, was that the dist-upgrade started, downloaded
the package lists and
Re: several issues actually (the OP)
It seems there was the unconditional shutdown kdm requirement, and
then there were other interruptions, where options were given on how to
proceed. Could/should these be handled separately, actually?
--
Upgrade from kubuntu Dapper requires manual
Other issues should go to new reports.
--
Upgrade from kubuntu Dapper requires manual intervention and kdm shutdown
https://bugs.launchpad.net/bugs/223226
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Ok.
This bug needs a lot more information.
Does it happen in clean dapper - hardy upgrades?
What does the KDM-requires-restart-dialog say exactly?
When _exactly_ does it appear?
** Changed in: kdebase (Ubuntu)
Importance: High = Medium
--
Upgrade from kubuntu Dapper requires manual
What does the KDM-requires-restart-dialog say exactly?
When _exactly_ does it appear?
Apologies for puttings this directly in the comment, but it seems
sufficiently relevant and not excessively long. (Plus it's an extract of
a log already attached to the report.)
Based on the logs, I have also
I don't see any evidence in the logs to be honest.
Also, I did about 5 upgrade scenarios and in none of them I had to restart KDM
(which is indeed not required at all mid-upgrade).
However
Restarting services possibly affected by the upgrade:
kdm: stopping...starting...done.
Confirmed here for the kdm issue.
That said, stopping kdm manually was a non-issue (for me), because the
upgrader wouldn't get confused by being interrupted at this point and
having to start again (though I won't argue if the developers value not
having to stop xdm/kdm for upgrading as a more
I reassigned to kdm for now, please add additional bugtasks for the
various other packages that are affected.
--
Upgrade from kubuntu Dapper requires manual intervention and kdm shutdown
https://bugs.launchpad.net/bugs/223226
You received this bug notification because you are a member of Kubuntu
** Attachment added: apt.log
http://launchpadlibrarian.net/13983377/apt.log
** Attachment added: apt-term.log
http://launchpadlibrarian.net/13983378/apt-term.log
** Attachment added: main.log
http://launchpadlibrarian.net/13983379/main.log
** Attachment added: main_pre_req.log
** Description changed:
I just upgraded from Dapper to Hardy (Kubuntu) using the command-line
process described on the web site.
Several issues actually:
- part-way into the upgrade, it tells me that kdm has to be manually shut
down before it can proceed. Grrr! I'm running this in
16 matches
Mail list logo
