Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: update-manager (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/883618
Marking as Triaged and high since this will affect a larger number of
users in the 10.04 LTS - 12.04 LTS transition. superm1 confirmed this
is still occuring in 12.04. His bug #933991 has screenshot and logs (it
is now marked as dup of this bug).
** Changed in: update-manager (Ubuntu)
Yes, I believe this used to be allright (do-relase-upgrade did not mess
with X11 at all, which is the correct way of behaving from my point of
view)
Xset says it 's unable to manipulate display emptystring,
which means DISPLAY=emptystring OR DISPLAY not being set at all.
By default DISPLAY
I noticed that this bug is tagged regression-release - did this used to
work with a previous version of update-manager? Thanks in advance.
Additionally, what is $DISPLAY set to?
** Changed in: update-manager (Ubuntu)
Importance: Undecided = Medium
** Changed in: update-manager (Ubuntu)
Allright.. fetching.
Althought I doubt that other than extreme-early error could lead to such
annoying and useless behavior
I have a screenshot saved somewhere
** Attachment added: Console upgrade desperately trying to touch not-running
X11
there are quite a lot of files... which ones do you want?
And no, I am not going to publish anything from that system without
reading briefly thru.
20110401-2157 20110401-2218 20111014-1920 apt.log
history.log main.log xorg_fixup.log
20110401-2205 20111014-1904
Sidenote - I don't understand why is apt-term.log protected from reading,
while screenlog.0 is not
While screenlog contains mix of apt-term.log, those xrandr errors and the
upgrader messages
Attaching'diff apt-term.log screenlog.0'from the point where the
upgrade started
The first
Important: This logs are from ARMEL machine (not x86).
Please ignore if you see armel or ports.ubuntu.com in the file.
I got the same problem on x86-based computers.
But I don't remember which one was run from VT instead of X11+uxterm (only the
1st case has the bug visible)
--
You received
Thanks for reporting this bug and sorry the unattended report. It would
be useful if you could attach some logs from the upgrade, if they are
still kept in your sytem, as there may be some error involved in the
update process. The logs should be at /var/log/dist-upgrade.
** Package changed:
