painful dist- upgrade as OFTEN, files and programs missing after various
futile attempts . when will come the day for no-issue Ubuntu upgrade?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1555237
Upgrades are working for Ubuntu GNOME, but screensaver issues exist, see
Bug 1565177 w/ proposed fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1555237
Title:
Upgrade from 14.04.4→ 16.04 dies
ftr - got an upgraded from 14.04 system here now (vanilla virtual - but
even so ...)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1555237
Title:
Upgrade from 14.04.4→ 16.04 dies midway taking out
This bug was fixed in the package dbus - 1.10.6-1ubuntu3
---
dbus (1.10.6-1ubuntu3) xenial; urgency=medium
* debian/dbus.preinst: divert the dbus-daemon-launch-helper if upgrading
from < 1.9.4-2~. This will make sure we keep the setuid bit during upgrade.
(LP: #1555237)
*
Mathew, please, pretty please stop removing tasks, even if they're
marked Invalid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1555237
Title:
Upgrade from 14.04.4→ 16.04 dies midway taking out
** No longer affects: ubuntu-release-upgrader (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1555237
Title:
Upgrade from 14.04.4→ 16.04 dies midway taking out the session.
To manage
@ Tim Lunn, I typically turn off screen lock and set blank screen to
never before beginning my upgrade tests but I suppose this time I should
leave screen lock on and just increase blank screen to 30 minutes or so.
Then if things seem even remotely buggy I'll compare the results between
Ubuntu and
^ shouldn't cause epic upgrade failures
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1555237
Title:
Upgrade from 14.04.4→ 16.04 dies midway taking out the session.
To manage notifications about
This bug was fixed in the package systemd - 229-3ubuntu2
---
systemd (229-3ubuntu2) xenial; urgency=medium
* udev.postinst: Quiesce error message if /sys/class/net/eno* does not
exist. (LP: #1560112)
* Fix assertion crash when processing a (broken) device without a sysfs
http://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?h=ubuntu=b585d9d7ad5
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: dbus (Ubuntu)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => In Progress
** Changed in: dbus (Ubuntu)
Status: New => In Progress
** Changed
There's also the issue with dbus's helper which is what causes compiz
crashes taking down the session when screensaver fires (which tends to
break upgrade even before udev / udisks2 clash). I'm testing a fix for
that now.
** Changed in: dbus (Ubuntu)
Milestone: None => ubuntu-16.04
--
You
Mathieu found the culprit, many thanks! This is due to some cleanup code
in udevd which wreaks havoc when not running under systemd, as it
assumes that it runs in its own cgroup (normally /system.slice/systemd-
udevd.service). src/udev/udevd.c on_post() has:
} else if
It is completely normal that X will exit on distribution upgrades. You
should never Upgrade a Linux system while running X! The normal way is
to update the sources, apt-get update, apt-get upgrade and reboot,
followed by apt-get dist-upgrade.
--
You received this bug notification because you are
** Changed in: compiz (Ubuntu)
Status: Confirmed => Invalid
** No longer affects: compiz (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1555237
Title:
Upgrade from 14.04.4→ 16.04
Here's some updated info on the "compiz crash" bug:
1- the "crash" only occurs in amd64 systems (in i386 I am able to successfully
dist-upgrade)
2- it is not a "compiz crash". Xserver stops because it receives the SIGKILL
signal => compiz, metacity and other wm stop as a consequence of that
just noticed that steve already wrote about sigkill etc :) sorry for the
double info
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1555237
Title:
Upgrade from 14.04.4→ 16.04 dies midway taking out
Context in /var/log/syslog shows:
Mar 25 22:31:39 trusty-upgrade udisksd[2392]: Acquired the name
org.freedesktop.UDisks2 on the system message bus
Mar 25 22:31:39 trusty-upgrade kernel: [ 7166.057324] init: dbus main process
(374) killed by KILL signal
Mar 25 22:31:39 trusty-upgrade kernel: [
The only reference I find to SIGKILL is in invoke-rc.d, which uses it
only in its force-stop command and only when pid1 is systemd. So I
currently have no explanation for this behavior.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I was able to reproduce this problem in a VM. Running X and compiz
under gdb, I find that compiz is dying after the X server is killed with
SIGKILL.
I also see this in /var/log/syslog:
Mar 25 22:31:40 trusty-upgrade kernel: [ 7167.438442] init: lightdm
post-stop process (2433) killed by KILL
In order to recreate things I virtualized my laptop (backup and restore
into a VM). So from now an, it should be much easier :-)
However, I'm bit struck. Performed the upgrade once more with same
result: system is some kind of frozen. Compared the distupgrader's logs
with my previous attempt and
Looks like bluez is stuck:
octoquad@ugqa:~$ ps aux | grep dpkg
root 3672 0.0 0.3 21080 7920 ?Ss 13:06 0:00 /usr/bin/dpkg
--force-overwrite --status-fd 71 --configure libc-bin:amd64 locales:all
libcap-ng0:amd64 libdbus-1-3:amd64 libexpat1:amd64 dbus:amd64 libnih1:amd64
If you kill the bluez process and run sudo dpkg --reconfigure -a a bunch
of packages get setup but will get stuck on bluez again:
octoquad@ugqa:~$ sudo dpkg --configure -a
Setting up fonts-sil-abyssinica (1.500-1) ...
Setting up libquadmath0:amd64 (5.3.1-12ubuntu4) ...
Setting up linux-sound-base
** Attachment added: "Upgrade Logs"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1555237/+attachment/4611098/+files/dist-upgrade-logs.tar.bz2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I tried upgrading in Virtualbox while tailing the dist-upgrade logs and
in the UI it says it is configuring libparted2 and then the UI freezes.
However the apt-term.log is still receiving writes and then writing
stops at bluez:
...
Setting up libparted2:amd64 (3.2-15) ...
Setting up parted
I logged into ssh and ran dpkg --configure -a before reboot and my
upgrade was successful. Unfortunately, not everyone is going to be so
lucky.
I think it was in the middle of configuring bluez when the server stops.
It's interesting that dpkg process remains in a stopped state when X
goes away.
On Thu, Mar 24, 2016 at 6:19 AM, Tim wrote:
> gnome-screensaver is no longer used on GNOME (its builtin as part of
> gnome-shell) so those quirks won't work there, I also thought Unity
> moved away from it as well?
>
> on GNOME I think the following gsetting would disable
gnome-screensaver is no longer used on GNOME (its builtin as part of
gnome-shell) so those quirks won't work there, I also thought Unity
moved away from it as well?
on GNOME I think the following gsetting would disable screensaver
org.gnome.desktop.session idle-delay to 0
--
You received this
I always disable the screensaver before I begin my upgrade tests.
(screen lock = off and blank screen = never) This has happened to me
both with Ubuntu and Ubuntu GNOME. Please see duplicate bug #1549067.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1555237
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I disabled the screensaver in my tests, and it still crashed - just
later on.
I SSH'd in to the box and ran compiz like this:
$ DISPLAY=:0 compiz --replace --debug
and then started the upgrade (with the screensaver disabled). This is
the error I got:
XIO: fatal IO error 11 (Resource
It doesn't seem like the screensaver really is properly disabled during
upgrades, at least looking very naively at what happens during the
upgrade -- if I go out of my way to disable it, I got the screen to
completely freeze (but at least everything did not crash down to
lightdm).
FWIW, I've
** Changed in: ubuntu-release-upgrader (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1555237
Title:
Upgrade from
Its worth noting DistUpgradeQuirks.py contains some code to disable
gnome-screensaver.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1555237
Title:
Upgrade from 14.04.4→ 16.04 dies midway taking
The interesting thing to notice here is that if I don't let the
screensaver come up doing a manual upgrade (because I'm watching it
more), it seems like compiz doesn't crash. It needs more testing, but it
looks like the only reason the upgrade failed was because the
screensaver kicked in.
**
** Changed in: ubuntu-release-upgrader (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/1555237
Title:
Upgrade from 14.04.4→ 16.04 dies midway taking out the
** Tags added: 1604-upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1555237
Title:
Upgrade from 14.04.4→ 16.04 dies midway taking out the session.
To manage notifications about this bug go
I've not been able to get the kernel panic logs, I've attached a
screenshot in the vain hope it might help.
** Attachment added: "kernpan.png"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1555237/+attachment/4594284/+files/kernpan.png
--
You received this bug
Ignore comment 4.
I had an active shell via SSH still but when I tried to reboot the box it
froze. When I reset the machine and try to boot I now have a kernel panic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
>From Dave's Apt Term Log he got as far as being asked a question in the
terminal:
There are services installed on your system which need to be restarted
when certain libraries, such as libpam, libc, and libssl, are upgraded.
Since these restarts may cause interruptions of service for the system,
Note, I did not see a complete session crash.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1555237
Title:
Upgrade from 14.04.4→ 16.04 dies midway taking out the session.
To manage notifications
Happens on both hardware and kvm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1555237
Title:
Upgrade from 14.04.4→ 16.04 dies midway taking out the session.
To manage notifications about this bug
42 matches
Mail list logo