Perhaps @Rolf meant this bug?
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1754069
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1164016
Title:
restor
Public bug reported:
Ubuntu release: Ubuntu 15.10
Package version: not sure (upgrading from 225-1ubuntu9 to ??? during distro
upgrade)
In the dist-upgrade log, error is reported as:
error from dpkg for pkg: 'systemd': 'subprocess installed post-installation
script returned error exit status 1'
*** This bug is a duplicate of bug 1506404 ***
https://bugs.launchpad.net/bugs/1506404
** This bug has been marked a duplicate of bug 1506404
package systemd 225-1ubuntu7 failed to install/upgrade: subprocess installed
post-installation script returned error exit status 1
--
You received
*** This bug is a duplicate of bug 1506404 ***
https://bugs.launchpad.net/bugs/1506404
** This bug has been marked a duplicate of bug 1506404
package systemd 225-1ubuntu7 failed to install/upgrade: subprocess installed
post-installation script returned error exit status 1
--
You received
Also affects version: systemd 225-1ubuntu9
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1506404
Title:
package systemd 225-1ubuntu7 failed to install/upgrade: subprocess
Attaching log for dist upgrade that triggered the error
** Attachment added: "distribution upgrade (15.04 -> 15.10) log"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1506404/+attachment/4506780/+files/main.log
--
You received this bug notification because you are a member of Ubuntu
Judging by the number of different architectures affected, I speculate
that bug occurs on a specific class of hardware (specific set of
motherboard chipsets?)
I have had this same (or similar?) issue plaguing two of my desktop
machines out of three. All have Ubuntu 15.04 currently on all three, al
@xtrchessreal, I followed the recipe and removed everything but the most
recent kernel. However, my problem didn't go away. Seeing as the
symptoms are slightly different, I am probably suffering from a
different bug. Still no clue how to diagnose or fix it.
--
You received this bug notification b
** Changed in: systemd (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1464917
Title:
reboot hangs at 'Reached target Shutdo
I have a hunch that this bug only occurs on systems upgraded from a previous
Ubuntu version, perhaps with replacement of upstart with systemd, but not on
fresh Ubuntu 15.04 or 15.10 installations.
Everyone who is affected: is there anyone who started having this problem on a
fresh 15.04 or later
@xtrchessreal, yes, alt+SysRq+ REISUB didn't work. It did help me out in
some other strange glitches. I think in this case, the USB drivers were
already shut off, and since I have a USB keyborad, it was unresponsive.
Maybe an analog / laptop keyboard would have worked.
--
You received this bug no
@xtrchessreal, if Chromium background processes are the culprit on your
platform, this would mean we are suffering from different issues.
Indeed, my symptoms are actually a bit different from what's described
in the original bug report -- I'm seeing the "Reached target Shutdown"
when I actually try
Dear all, turns out, my system was suffering from completely different
bug with similar symptoms. It was a problem with the motherboard BIOS. I
upgraded the BIOS and the bug went away. I'm taking myself off the
mailing list for this bug.
If you're suffering from a similar issue even after the fix
Syslog starting with initiating shutdown from gui and ending right
before hard shutdown.
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917/+attachment/4530150/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Tou
Martin Pitt, I've tried all the recipes, here is what booting with
"debug" shows after shutdown (attached image).
Unfortunately, for me, SysRq doesn't work, the and the keyboard is
completely unresponsive. Is there any way to dig out what happened from
system logs post-factum, after next login?
I
15 matches
Mail list logo
