*** This bug is a duplicate of bug 1432265 ***
https://bugs.launchpad.net/bugs/1432265
** This bug has been marked a duplicate of bug 1432265
does not ask for LUKS passphrases without plymouth
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
*** This bug is a duplicate of bug 1502097 ***
https://bugs.launchpad.net/bugs/1502097
** This bug has been marked a duplicate of bug 1502097
packages fail to install/upgrade: Connection timed out
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
** Package changed: systemd (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1523029
Title:
Install on Lenovo S21e: Error fsyncing/closing /dev/mmcblk0rpmb:
** No longer affects: systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1524755
Title:
systemd support
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 1433320 ***
https://bugs.launchpad.net/bugs/1433320
** This bug has been marked a duplicate of bug 1433320
systemd-journald, udev, logind crashed with SIGABRT -- get killed by 1 min
watchdog timeout on longer kernel lockups
--
You received this bug
Dez 19 10:05:42 T3500 systemd[1]: Timed out waiting for device dev-disk-
by\x2duuid-a2892221\x2d07fe\x2d408c\x2d83de\x2d145505f4c01c.device.
You apparently have some mounts in /etc/fstab whose devices don't exist
any more, or at the moment. If they are intended to not exist sometimes
and you
As explained above, /run is mounted by initramfs-tools, thus changing
the package.
** Package changed: systemd (Ubuntu) => initramfs-tools (Ubuntu)
** Summary changed:
- systemd doesn't respect /etc/fstab for internal mounts
+ check /etc/fstab for custom /run mount options
--
You received
Please file crashes through the crash notification ("apport"), not like
that. This report contains no useful information about the crash that
could help the developers to investigate and fix it.
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification
*** This bug is a duplicate of bug 1484027 ***
https://bugs.launchpad.net/bugs/1484027
** This bug has been marked a duplicate of bug 1484027
systemd-tmpfiles-clean warns about duplicate /var/log line
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
I translated the bug title using Google translate. Please file bugs in
English and give some more details about what you are doing precisely.
** Summary changed:
- Камера в скайпе переврнута
+ The camera turned on Skype
** Package changed: systemd (Ubuntu) => ubuntu
** Changed in: ubuntu
*** This bug is a duplicate of bug 1502097 ***
https://bugs.launchpad.net/bugs/1502097
** This bug has been marked a duplicate of bug 1502097
packages fail to install/upgrade: Connection timed out
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
*** This bug is a duplicate of bug 1502097 ***
https://bugs.launchpad.net/bugs/1502097
** This bug has been marked a duplicate of bug 1502097
packages fail to install/upgrade: Connection timed out
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
** Also affects: systemd (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
*** This bug is a duplicate of bug 1502097 ***
https://bugs.launchpad.net/bugs/1502097
** This bug has been marked a duplicate of bug 1502097
packages fail to install/upgrade: Connection timed out
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
*** This bug is a duplicate of bug 1502097 ***
https://bugs.launchpad.net/bugs/1502097
** This bug has been marked a duplicate of bug 1502097
packages fail to install/upgrade: Connection timed out
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Please don't file bugs against "systemd" about random crashes and
problems, like this or bug 1522313. Apport pops up crash notifications
and sends these properly, with the necessary information for developers
and against the right package. Please send this crash like that.
** Changed in: systemd
*** This bug is a duplicate of bug 1502097 ***
https://bugs.launchpad.net/bugs/1502097
** This bug has been marked a duplicate of bug 1502097
packages fail to install/upgrade: Connection timed out
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
** Package changed: systemd (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1551148
Title:
cfg80211 kernel module crashes
To manage notifications about
*** This bug is a duplicate of bug 1502097 ***
https://bugs.launchpad.net/bugs/1502097
** This bug has been marked a duplicate of bug 1502097
packages fail to install/upgrade: Connection timed out
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
systemd < 228 had a race condition which caused occasional lockups on
upgrades or other operations which involved (re)starting processes,
systemctl daemon-reload, and similar. This got analyzed upstream in
https://github.com/systemd/systemd/issues/1505 and finally got fixed in
228. Thus I mark
The kernel spews out some oopses
(https://launchpadlibrarian.net/234191094/CurrentDmesg.txt) About the
connection error, that is mostly tracked in bug 1502097, so let's devote
this to the kernel error.
** Summary changed:
- package systemd 225-1ubuntu4 failed to install/upgrade: subprocess
*** This bug is a duplicate of bug 1032823 ***
https://bugs.launchpad.net/bugs/1032823
** This bug has been marked a duplicate of bug 1032823
package libdevmapper-event1.02.1 2:1.02.48-4ubuntu7.1 failed to
install/upgrade: ErrorMessage: dependency problems - leaving unconfigured
--
You
*** This bug is a duplicate of bug 1447654 ***
https://bugs.launchpad.net/bugs/1447654
Error getting authority: Error initializing authority: Error calling
StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached
(g-io-error-quark, 24)
Failed to execute operation: Connection
Removing systemd (225-1ubuntu9) ...
systemd is the active init system, please switch to another before removing
systemd.
dpkg: error processing package systemd (--purge):
subprocess installed pre-removal script returned error exit status 1
Err, yes, don't do that :-)
** Changed in: systemd
dpkg: cycle found while processing triggers:
chain of packages whose triggers are or may be responsible:
bamfdaemon -> bamfdaemon
packages' pending triggers which are or may be unresolvable:
dbus: /usr/share/dbus-1/system-services: /etc/dbus-1/system.d
gnome-menus: /usr/share/applications
*** This bug is a duplicate of bug 1032823 ***
https://bugs.launchpad.net/bugs/1032823
** This bug has been marked a duplicate of bug 1032823
package libdevmapper-event1.02.1 2:1.02.48-4ubuntu7.1 failed to
install/upgrade: ErrorMessage: dependency problems - leaving unconfigured
--
You
*** This bug is a duplicate of bug 1032823 ***
https://bugs.launchpad.net/bugs/1032823
** This bug has been marked a duplicate of bug 1032823
package libdevmapper-event1.02.1 2:1.02.48-4ubuntu7.1 failed to
install/upgrade: ErrorMessage: dependency problems - leaving unconfigured
--
You
Setting up libpam-systemd:amd64 (204-5ubuntu20.14) ...
initctl: Unable to connect to Upstart: Failed to connect to socket
/com/ubuntu/upstart-session/1000/1520: Connection refused
invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
dpkg: error processing package
*** This bug is a duplicate of bug 1502097 ***
https://bugs.launchpad.net/bugs/1502097
** This bug is no longer a duplicate of bug 1506404
package systemd 225-1ubuntu7 failed to install/upgrade: subprocess installed
post-installation script returned error exit status 1
** This bug has
*** This bug is a duplicate of bug 1502097 ***
https://bugs.launchpad.net/bugs/1502097
** This bug is no longer a duplicate of bug 1506404
package systemd 225-1ubuntu7 failed to install/upgrade: subprocess installed
post-installation script returned error exit status 1
** This bug has
** Also affects: systemd (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Released
** Changed in: systemd (Ubuntu Trusty)
Status: New => Triaged
** Changed in: systemd (Ubuntu Trusty)
Assignee: (unassigned) =>
I tested this on current Xenial amd64 with a LUKS partition for /opt.
Indeed when dropping "splash" from the command line I only get "Starting
cryptography for..." but no actual prompt. Theh same happens when I use
"console=ttyS0" and thus see the boot messages on the QEMU serial
console.
In this
The error message is pretty clear. src/util/virsystemd.c does
if (virDBusCallMethod(conn,
NULL,
,
"org.freedesktop.machine1",
"/org/freedesktop/machine1",
** Package changed: systemd (Ubuntu) => debconf (Ubuntu)
** Tags added: bot-stop-nagging
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1539488
Title:
package
** Also affects: systemd (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1473800
Title:
restarting logind during systemd
*** This bug is a duplicate of bug 1473800 ***
https://bugs.launchpad.net/bugs/1473800
Duplicate of bug 1473800 which was fixed in wily.
** This bug has been marked a duplicate of bug 1473800
restarting logind during systemd update causes screen to lock
--
You received this bug
command-not-found needs to be updated, machinectl is in the "systemd-
container" package.
** Summary changed:
- machinectl packaging broken
+ command-not-found needs updating for "machinectl"
** Package changed: systemd (Ubuntu) => command-not-found (Ubuntu)
** Changed in: command-not-found
Sorry, we are not going to implement an upstart parser into systemd,
and there is not even an 1-to-1 correspondence between upstart jobs and
systemd units. So this can only ever be a heuristics, and "working in
some cases" is worse (because not predictable) than "upstart overrides
don't affect
** Bug watch added: Debian Bug tracker #813671
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813671
** Also affects: installation-guide (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813671
Importance: Unknown
Status: Unknown
--
You received this bug
*** This bug is a duplicate of bug 1540568 ***
https://bugs.launchpad.net/bugs/1540568
** This bug has been marked a duplicate of bug 1540568
package udev 228-4ubuntu2 failed to install/upgrade: Service mountkernfs has
to be enabled to start service udev
--
You received this bug
OK. Packages don't have a good way of presenting such a warning, so this
would need to go into the release upgrader.
** Summary changed:
- Transition from upstart to systemd should honor /etc/init/*.override
+ Show warning on upgrade if there are /etc/init/*.override files
** Package changed:
> live-build: drop ubuntu-no-adjtime.patch
Actually, this isn't about setting UTC vs. LOCAL, just about the actual
time drift, so this can stay. Dropping task.
** Package changed: installation-guide (Debian) => mbr (Debian)
** Changed in: installation-guide (Ubuntu)
Status: New => Fix
** Bug watch added: Debian Bug tracker #813703
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813703
** Also affects: systemd (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813703
Importance: Unknown
Status: Unknown
--
You received this bug notification because
*** This bug is a duplicate of bug 1540568 ***
https://bugs.launchpad.net/bugs/1540568
** This bug has been marked a duplicate of bug 1540568
package udev 228-4ubuntu2 failed to install/upgrade: Service mountkernfs has
to be enabled to start service udev
--
You received this bug
Archive grep finished. I reviewed all matches of "default/rcS" and
"adjtime", notes are below. "rcSNOUTC" means "sources /etc/default/rcS,
but does not use UTC flag" (often uses VERBOSE, sometimes FSCKFIX)
These are the packages that need fixing:
installation-guide: drop our delta to revert docs
*** This bug is a duplicate of bug 1540568 ***
https://bugs.launchpad.net/bugs/1540568
** This bug has been marked a duplicate of bug 1540568
package udev 228-4ubuntu2 failed to install/upgrade: Service mountkernfs has
to be enabled to start service udev
--
You received this bug
*** This bug is a duplicate of bug 1540568 ***
https://bugs.launchpad.net/bugs/1540568
** This bug has been marked a duplicate of bug 1540568
package udev 228-4ubuntu2 failed to install/upgrade: Service mountkernfs has
to be enabled to start service udev
--
You received this bug
*** This bug is a duplicate of bug 1540568 ***
https://bugs.launchpad.net/bugs/1540568
** This bug has been marked a duplicate of bug 1540568
package udev 228-4ubuntu2 failed to install/upgrade: Service mountkernfs has
to be enabled to start service udev
--
You received this bug
*** This bug is a duplicate of bug 1540568 ***
https://bugs.launchpad.net/bugs/1540568
** This bug has been marked a duplicate of bug 1540568
package udev 228-4ubuntu2 failed to install/upgrade: Service mountkernfs has
to be enabled to start service udev
--
You received this bug
The Debian bug was fixed yesterday in xenial's systemd, so closing.
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
*** This bug is a duplicate of bug 1540568 ***
https://bugs.launchpad.net/bugs/1540568
** This bug has been marked a duplicate of bug 1540568
package udev 228-4ubuntu2 failed to install/upgrade: Service mountkernfs has
to be enabled to start service udev
--
You received this bug
(Ubuntu)
Importance: Undecided
Assignee: Martin Pitt (pitti)
Status: Triaged
** Changed in: systemd (Ubuntu)
Milestone: None => ubuntu-16.02
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: systemd (Ubuntu)
Statu
*** This bug is a duplicate of bug 1540568 ***
https://bugs.launchpad.net/bugs/1540568
** This bug has been marked a duplicate of bug 1540568
package udev 228-4ubuntu2 failed to install/upgrade: Service mountkernfs has
to be enabled to start service udev
--
You received this bug
https://launchpad.net/ubuntu/+source/init-system-helpers/1.26ubuntu1
broke update-rc.d for about half a day in Ubuntu. If you
installed/upgraded during that time or with an image built in that time,
you'd get an effect like this. Can you please run
sudo update-rc.d mountkernfs.sh defaults
> addgroup: La grupo 'input' jam ekzistas kaj ne estas sistema grupo.
Elirado. dpkg: eraro dum procezado de la pako udev (--configure):
As the error says, please don't create group "input" as an user group,
it needs to be a system one. It's probably best to do "sudo delgroup
input" and then "sudo
Hey Bryan,
thanks for investigating and the patch! Indeed it seems the enabling in
debian/rules got reverted in some merge. The patch is good, except that
I changed postinst to
-if dpkg --compare-versions "$2" lt-nl "0.9.10.0-4ubuntu10"; then
+if dpkg --compare-versions "$2"
I grepped the whole archive and the only hook that explicitly attaches
/var/log/udev was libmtp (which got fixed in
https://launchpad.net/ubuntu/+source/libmtp/1.1.10-2ubuntu1).
** Also affects: apport (Ubuntu)
Importance: Undecided
Status: New
** Changed in: apport (Ubuntu Xenial)
I committed a cleanup of the file to udev.postinst (if running under
systemd).
** Changed in: systemd (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Bug watch added: Debian Bug tracker #812729
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812729
** Also affects: libmtp
nce: High => Undecided
** Changed in: debian-installer (Ubuntu)
Assignee: Martin Pitt (pitti) => (unassigned)
** Changed in: debian-installer (Ubuntu Trusty)
Status: New => Triaged
** Changed in: debian-installer (Ubuntu Trusty)
Assignee: (unassigned) => Martin Pit
** Bug watch added: Debian Bug tracker #789524
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789524
** Also affects: upstart (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789524
Importance: Unknown
Status: Unknown
--
You received this bug notification because
This has been dropped entirely after 14.04, but is still an issue in
14.04 LTS.
** Changed in: udev (Ubuntu)
Status: New => Fix Released
** Package changed: udev (Ubuntu) => systemd (Ubuntu)
** Also affects: systemd (Ubuntu Trusty)
Importance: Undecided
Status: New
** Summary
** Summary changed:
- package systemd 228-3ubuntu1 failed to install/upgrade: subprocess installed
post-installation script returned error exit status 1
+ package kernel-common 13.014+nmu3 failed to install/upgrade: unable to open
** No longer affects: systemd (Ubuntu Vivid)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1432265
Title:
does not ask for LUKS passphrases without plymouth
To manage
These units moved to ifupdown in the meantime, moving component. There
is now a fix for this, by adding Slice=system.slice to ifup@.service.
** Package changed: systemd (Ubuntu) => ifupdown (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
As I explained, the notion of "the last thing during boot" is not well-
defined with a partially ordered and parallel init system like systemd
or upstart (or even sysvinit+startpar).
So as long as cloud-init.service declares itself to run after rc-
local.service, then rc-local.service necessarily
** No longer affects: systemd (Ubuntu)
** No longer affects: dbus (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1530389
Title:
[upstream] some apps can't handle sftp://
Joe, please don't hijack bugs like this. You have a different laptop
model, please file a new bug with "ubuntu-bug udev". Thanks!
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Fix landed upstream, thanks Andreas!
** Package changed: udev (Ubuntu) => systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
** No longer affects: systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1529079
Title:
Can't start virtual machines after upgrade to Xenial
To manage notifications
dpkg: cycle found while processing triggers:
chain of packages whose triggers are or may be responsible:
ufw -> ufw
packages' pending triggers which are or may be unresolvable:
systemd: /etc/init.d
libc-bin: ldconfig
initramfs-tools: update-initramfs
libgdk-pixbuf2.0-0:amd64:
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: libseccomp (Ubuntu)
Status: Triaged => In Progress
** Changed in: systemd (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
I now isolated this seccomp failure into a tiny .c file which reproduces
this. On amd64 it works:
$ gcc -o /tmp/o ~/seccomp-socket-filter.c -lseccomp && /tmp/o
SCMP_SYS(socket) == 41 == 29
Success
and on i386 it reproduces the error:
$ gcc -o /tmp/o ~/seccomp-socket-filter.c -lseccomp && /tmp/o
Public bug reported:
Four days ago, on Dec 10,
http://autopkgtest.ubuntu.com/packages/s/systemd/xenial/i386/ started
failing:
==
FAIL: test_boot (__main__.NspawnTest)
Version comparison between the two builds:
- libseccomp-dev: Both versions built against 2.2.3-2ubuntu1
- libc6-dev: 2.21-0ubuntu4 → 2.21-0ubuntu5
- linux-libc-dev: 4.2.0-19.23 → 4.3.0-2.11
- binutils: 2.25.51.20151113-2ubuntu1 → 2.25.90.20151209-1ubuntu1
- gcc-5: 5.2.1-24ubuntu3 →
Xenial has this now, the MIR was approved at last:
systemd-journal-remote | 228-2ubuntu2 | xenial | amd64, arm64, armhf,
i386, powerpc, ppc64el, s390x
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of
Log excerpt:
Setting up libgtk-3-bin (3.18.6-1ubuntu1) ...
dpkg: cycle found while processing triggers:
chain of packages whose triggers are or may be responsible:
bamfdaemon -> bamfdaemon
packages' pending triggers which are or may be unresolvable:
software-center:
> UnreportableReason: The problem happened with the program /lib/systemd
/systemd-logind which changed since the crash occurred.
Apparrently you upgraded in the meantime. The journal output just says
that it segfaulted, but not why, so we need a proper retrace from a
current version. The .crash
This was fixed in Ubuntu 15.10 at least, and is not a severe error, so
I'm closing this now. Thanks for your report!
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Hello Bin, or anyone else affected,
Accepted gnome-desktop3 into trusty-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
desktop3/3.8.4-0ubuntu3.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
I reassign that to binutils for now, which provides the linker. Looks
like the alignment of the ELF sections need to be adjusted for 64k
pages?
** Summary changed:
- Systemd init failure on arm64 64k pages
+ compiled binaries don't work on arm64 64k pages kernel
** Summary changed:
- compiled
➜ ~ cat /etc/modules
> # at boot time, one per line. Lines beginning with "#" are ignored.
> “synaptics_i2c”
I hope the quotes are not literally in your /etc/modules :-)
This is saying that a module in your /etc/modules could not be loaded.
I. e. either the synaptics_i2c module does not exist,
When using the old-style /etc/udev/rules.d/70-persistent-net.rules
schema this is an unavoidable race condition. Our udev package has a
patch to try and make the best of it
(http://anonscm.debian.org/gitweb/?p=pkg-
systemd/systemd.git;a=blob;f=debian/patches/Revert-udev-network-device-
Uploaded and source-NEWed, thanks!
** Package changed: gdm (Ubuntu) => gdm3 (Ubuntu)
** Changed in: gdm3 (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
Uploaded, thanks!
** Changed in: gimp (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gimp in Ubuntu.
https://bugs.launchpad.net/bugs/1515763
Title:
Merge from debian 2.8.14-1.2
To
The verification of the Stable Release Update for nautilus has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
This is applied in the xenial version now.
** Changed in: systemd (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1450009
This bug only affected utopic, which is EOL now, so closing.
** Changed in: systemd (Ubuntu Utopic)
Status: Triaged => Won't Fix
** Changed in: null-and-void
Status: New => Invalid
** Changed in: systemd-shim (Ubuntu)
Assignee: Martin Pitt (pitti) => (unassigned)
*
So obviously one of the quirks in /usr/lib/pm-utils/sleep.d works around
this kernel bug. We need to find out which. Can you please move the
files in that directory to some other place one by one and do a "sudo
pm-suspend" / resume cycle until it starts failing? That's the "magic"
hook then. Which
** No longer affects: systemd (Ubuntu)
** No longer affects: systemd (Ubuntu Trusty)
** No longer affects: systemd (Ubuntu Vivid)
** No longer affects: systemd (Ubuntu Wily)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd
Thanks. Reassigning to the kernel then.
** Package changed: systemd (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
This is another instance of a libdevmapper upgrade problem:
Preparing to unpack .../libdevmapper1.02.1_2%3a1.02.90-2ubuntu1_amd64.deb ...
Unpacking libdevmapper1.02.1:amd64 (2:1.02.90-2ubuntu1) over
(2:1.02.77-6ubuntu2) ...
Preparing to unpack .../libudev1_219-7ubuntu6_amd64.deb ...
Unpacking
> I'm surprised the root filesystem is read-only at the point where
systemd starts. Isn't it remounted rw by the initramfs? (It is in
Debian.)
No, it shouldn't; Usually grub passes the "ro" option in which case
initramfs should leave it as readonly (see /usr/share/initramfs-
tools/init). rw
hanged in: rsyslog (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1484027
Title:
systemd-tmpfiles-clean warns about duplicate
I tried that user-data (minus the extra packages: and
ssh_authorized_keys: as they are irrelevant) on the current wily cloud
image with QEMU, and I get:
[ 13.799851] cloud-init[1010]: Cloud-init v. 0.7.7 running 'modules:config'
at Wed, 28 Oct 2015 08:11:33 +. Up 13.12 seconds.
[
Wrt. suspend there is no structural change between 15.04 and 15.10, in
both cases you were already using a direct kernel sleep without pm-utils
when you use the "K" menu.
This sounds like some kernel/driver bug which one of the pm-utils quirks
is working around. Can you please "cd
The "Failed to reset devices.list" is known and mostly harmless
(prohibited by LXC's apparmor profile).
** Package changed: systemd (Ubuntu) => lxc (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
Do you have a chance to replace this in /lib/systemd/system/systemd-
update-utmp-runlevel.service:
ExecStart=/usr/bin/strace -fvvs1024 -o /run/update-utmp.trace
/lib/systemd/systemd-update-utmp runlevel
and add this line
Environment=SYSTEMD_LOG_LEVEL=debug
? Then please boot and attach the
** Bug watch added: Debian Bug tracker #794723
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794723
** Also affects: policykit-1 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794723
Importance: Unknown
Status: Unknown
--
You received this bug notification
I think I know what's going on:
Unpacking apport (2.19.1-0ubuntu2) ...
Selecting previously unselected package policykit-1.
Preparing to unpack .../policykit-1_0.105-11ubuntu1_amd64.deb ...
Unpacking policykit-1 (0.105-11ubuntu1) ...
Processing triggers for shared-mime-info (1.3-1) ...
Processing
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Triaged
** Changed in: systemd (Ubuntu Vivid)
Status: New => Triaged
** Changed in: policykit-1 (Ubuntu)
Status: Confirmed => Triaged
** Changed in:
401 - 500 of 7748 matches
Mail list logo
