*** This bug is a duplicate of bug 1447654 ***
https://bugs.launchpad.net/bugs/1447654
** This bug is no longer a duplicate of bug 1436448
Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was
reached (g-io-error-quark, 24)
** This bug has been marked a duplicate of
** Package changed: systemd (Ubuntu) => privoxy (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/1507257
Title:
Failed to start Privacy enhancing HTTP Proxy.
To manage
*** This bug is a duplicate of bug 1433320 ***
https://bugs.launchpad.net/bugs/1433320
** This bug is no longer a duplicate of bug 1506801
systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()
** This bug has been marked a duplicate of bug 1433320
systemd-journald, udev, logind
*** 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
*** This bug is a duplicate of bug 1433320 ***
https://bugs.launchpad.net/bugs/1433320
Till, I know. As I wrote, there's pretty much nothing we can really do
about this :/ Please stop filing a gazillion duplicates about this, it's
just causing a lot of unnecessary paperwork and manual
*** This bug is a duplicate of bug 1433320 ***
https://bugs.launchpad.net/bugs/1433320
** This bug is no longer a duplicate of bug 1506801
systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()
** This bug has been marked a duplicate of bug 1433320
systemd-journald, udev, logind
*** This bug is a duplicate of bug 1433320 ***
https://bugs.launchpad.net/bugs/1433320
** This bug is no longer a duplicate of bug 1506800
systemd-timesyncd crashed with SIGABRT in epoll_wait()
** This bug has been marked a duplicate of bug 1433320
systemd-journald, udev, logind crashed
42-usb-hid.rules got removed in vivid (or so), thus marking the floating
task invalid.
** Changed in: udev (Ubuntu)
Status: Confirmed => Invalid
** Package changed: udev (Ubuntu) => systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Is there an apt repository for these mariadb packages somewhere, or at
least some debs?
** Bug watch added: Red Hat Bugzilla #1271832
https://bugzilla.redhat.com/show_bug.cgi?id=1271832
** Also affects: systemd (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=1271832
Importance:
** Summary changed:
- systemd 226-2 (debian sid) breaks lxc-attach
+ systemd 226 (moving pid 1 into /init.scope cgroup) breaks lxc-attach
** Package changed: systemd (Ubuntu) => lxcfs (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Not sure what to do with this then -- I don't think we want to silence
the warning. If you write tmpfiles.d snippets they are useful to know
when something accidentally overlaps. We just know that this particular
instance is expected if you install rsyslog. Closing it as "wontfix"
won't magically
It's just a warning: the rsyslog package ships
/usr/lib/tmpfiles.d/00rsyslog.conf which also ships a config for
/var/log, so the one in var.conf is ignored.
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
There are no logs here which would show what led to the bad state of
libpam-systemd, and after your dist-upgrade the package is now installed
fine, so we lost the evidence of what went wrong. You apparently used
"apt-get upgrade" before, which doesn't write any further logs (such as
the update
Apparently you uninstalled the apport package? That's what provides
ubuntu-bug, and it's installed by default in Xubuntu.
** Package changed: systemd (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: In Progress => Invalid
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1495178 ***
https://bugs.launchpad.net/bugs/1495178
** This bug is no longer a duplicate of private bug 1502626
** This bug has been marked a duplicate of bug 1495178
Failed to set wall message, ignoring: Message recipient disconnected from
message bus
Thank you. This needs to be fixed in the kernel driver then, as without
a scan code there is nothing we can do in userspace.
** Package changed: systemd (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Summary changed:
- Brightness HotKeys not
*** This bug is a duplicate of bug 1433320 ***
https://bugs.launchpad.net/bugs/1433320
Till, you reported this like 20 times already.. :-)
** 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
Please only file one report per issue, using that for the keyboard
problem. This has got nothing to do with systemd, it's most probably
some (mis)configuration or misbehaviour of unity-settings-dameon.
** Summary changed:
- Waking up changes keyboard layout and turns off wifi
+ Waking up changes
*** This bug is a duplicate of bug 1495178 ***
https://bugs.launchpad.net/bugs/1495178
** This bug is no longer a duplicate of bug 1499863
systemd-logind crashed with SIGSEGV in __strlen_ia32()
** This bug has been marked a duplicate of bug 1495178
Failed to set wall message, ignoring:
*** This bug is a duplicate of bug 1495178 ***
https://bugs.launchpad.net/bugs/1495178
** This bug has been marked a duplicate of bug 1495178
Failed to set wall message, ignoring: Message recipient disconnected from
message bus without replying
--
You received this bug notification
** Changed in: systemd (Ubuntu)
Status: Confirmed => Triaged
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
** Bug watch added: Debian Bug tracker #761909
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761909
** Also affects: systemd (Debian) via
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Committed
** No longer affects: xorg-server (Ubuntu)
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
> did restore a recent wily backup though, so these now obsolete udev
files in /etc/init & /etc/init.d files might stem from that
Ah, this would explain it then.
I just did a dist-upgrade from vivid to current wily, and it works as
intended:
Setting up udev (225-1ubuntu4) ...
Installing new
** No longer affects: upstart (Ubuntu)
** No longer affects: udev (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/1495116
Title:
There is a whole chain of failures:
dpkg: dependency problems prevent configuration of systemd:
systemd depends on libcryptsetup4 (>= 2:1.4.3); however:
Package libcryptsetup4 is not configured yet.
dpkg: dependency problems prevent configuration of libcryptsetup4:
libcryptsetup4 depends on
*** This bug is a duplicate of bug 1496038 ***
https://bugs.launchpad.net/bugs/1496038
Google translate of the error message:
dpkg: a loop is found while processing triggers:
packet chain whose triggers are or may be responsible:
lubuntu-software-center -> cups
packet pending triggers
dpkg: cycle found while processing triggers:
chain of packages whose triggers are or may be responsible:
lubuntu-software-center -> libc-bin
This looks similar to bug 1496119, where lubuntu-software-center is the
common factor.
** Summary changed:
- package systemd 225-1ubuntu4 failed to
*** This bug is a duplicate of bug 1447807 ***
https://bugs.launchpad.net/bugs/1447807
** This bug has been marked a duplicate of bug 1447807
systemctl enable shows error on enabling a SysV service
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
udev-finish.service is gone, together with /lib/udev/udev-finish. That's
quite deliberate, we don't need it any more.
Please give me the output of "sudo systemctl status -l udev-
finish.service". Thanks!
** Package changed: udev (Ubuntu) => systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
** Changed in: apport (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: systemd (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
Apparently this still happens a lot, reopening.
** Changed in: systemd (Ubuntu)
Status: Fix Released => Confirmed
** Changed in: systemd (Ubuntu)
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Thanks for checking again! So this was a bug in the updated third-party
graphics driver then.
** Package changed: systemd (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
*** This bug is a duplicate of bug 1433320 ***
https://bugs.launchpad.net/bugs/1433320
** This bug is no longer a duplicate of private bug 1494664
** This bug has been marked a duplicate of bug 1433320
systemd-journald, udev, logind crashed with SIGABRT -- get killed by 1 min
watchdog
*** This bug is a duplicate of bug 1433320 ***
https://bugs.launchpad.net/bugs/1433320
** This bug is no longer a duplicate of bug 1496596
systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()
** This bug has been marked a duplicate of bug 1433320
systemd-journald, udev, logind
*** This bug is a duplicate of bug 1433320 ***
https://bugs.launchpad.net/bugs/1433320
** This bug is no longer a duplicate of bug 1495589
systemd-logind crashed with SIGABRT in __epoll_wait_nocancel()
** This bug has been marked a duplicate of bug 1433320
systemd-journald, udev, logind
** Changed in: systemd (Ubuntu)
Status: Won't Fix => Triaged
--
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/1433320
Title:
systemd-journald, udev, logind crashed with
ort (Ubuntu)
Status: New => Triaged
** Changed in: apport (Ubuntu)
Importance: Undecided => High
** Changed in: apport (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Description changed:
Errors Bucket
-
https://errors.ubuntu.com/bucket/?id=
This also applies when booting systemd without an initramfs. NOSUID is
already set, but not NOEXEC. I proposed that in
https://github.com/systemd/systemd/pull/1265
** Changed in: systemd (Ubuntu)
Status: Invalid => In Progress
--
You received this bug notification because you are a
This was fixed in
https://launchpad.net/ubuntu/+source/systemd/225-1ubuntu4
* Fix shutdown with specifying a time.
** Information type changed from Private to Public
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a
Feedback from upstream at https://github.com/systemd/systemd/pull/1265 :
Apparently noexec on /dev breaks some drivers which expose memory-mapped
devices in /dev/. So retitling for "nosuid" only. systemd already does
that, initramfs-tools doesn't yet, but the attached patch needs to be
modified to
*** This bug is a duplicate of bug 1433320 ***
https://bugs.launchpad.net/bugs/1433320
** This bug is no longer a duplicate of bug 1494950
programs using libsystemd crashed with SIGABRT in __epoll_wait_nocancel()
** This bug has been marked a duplicate of bug 1433320
systemd-journald
*** This bug is a duplicate of bug 1433320 ***
https://bugs.launchpad.net/bugs/1433320
** This bug is no longer a duplicate of bug 1494950
programs using libsystemd crashed with SIGABRT in __epoll_wait_nocancel()
** This bug has been marked a duplicate of bug 1433320
systemd-journald
*** This bug is a duplicate of bug 1433320 ***
https://bugs.launchpad.net/bugs/1433320
** This bug is no longer a duplicate of bug 1494950
programs using libsystemd crashed with SIGABRT in __epoll_wait_nocancel()
** This bug has been marked a duplicate of bug 1433320
systemd-journald
*** This bug is a duplicate of bug 1433320 ***
https://bugs.launchpad.net/bugs/1433320
** This bug is no longer a duplicate of bug 1494950
programs using libsystemd crashed with SIGABRT in __epoll_wait_nocancel()
** This bug has been marked a duplicate of bug 1433320
systemd-journald
*** This bug is a duplicate of bug 1433320 ***
https://bugs.launchpad.net/bugs/1433320
** This bug is no longer a duplicate of bug 1494950
programs using libsystemd crashed with SIGABRT in __epoll_wait_nocancel()
** This bug has been marked a duplicate of bug 1433320
systemd-journald
*** This bug is a duplicate of bug 1433320 ***
https://bugs.launchpad.net/bugs/1433320
** This bug is no longer a duplicate of bug 1494950
programs using libsystemd crashed with SIGABRT in __epoll_wait_nocancel()
** This bug has been marked a duplicate of bug 1433320
systemd-journald
*** This bug is a duplicate of bug 1433320 ***
https://bugs.launchpad.net/bugs/1433320
** This bug is no longer a duplicate of bug 1494950
programs using libsystemd crashed with SIGABRT in __epoll_wait_nocancel()
** This bug has been marked a duplicate of bug 1433320
systemd-journald
*** This bug is a duplicate of bug 1433320 ***
https://bugs.launchpad.net/bugs/1433320
** This bug is no longer a duplicate of bug 1494950
programs using libsystemd crashed with SIGABRT in __epoll_wait_nocancel()
** This bug has been marked a duplicate of bug 1433320
systemd-journald
Applied the udev.init change in http://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?id=63dff1e2132b for Debian. But it is
totally irrelevant for Ubuntu, as we don't support SysV init. Under
upstart /etc/init/udev does not do any mounting, it relies on mountall
to do that, thus this
** 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/1494135
Title:
Microphone mute hotkey for Dell
This sounds related:
http://cgit.freedesktop.org/xorg/xserver/commit/?id=dc48bd653c7e1013e2d69e3f59ae3cbc0c893473
-- Seems current X.org does not like logind to be restarted, but that's
what we do right now in the systemd package (so that after a dist-
upgrade you actually run the current
Missing bug ref in the changelog, closing manually:
https://launchpad.net/ubuntu/+source/nuntium/1.4+15.10.20150902-0ubuntu1
Thanks Dimitri and Alfonso!
** Changed in: nuntium (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of
Public bug reported:
In https://blueprints.launchpad.net/ubuntu/+spec/foundations-w-networkd-
vs-ifupdown we want to provide networkd as a viable option for Ubuntu,
in particular server/cloud land. This requires some integration with
existing packages, in particular calling the
** Also affects: adduser (Ubuntu)
Importance: Undecided
Status: New
** Changed in: adduser (Ubuntu)
Status: New => Triaged
** Changed in: systemd (Ubuntu)
Assignee: Martin Pitt (pitti) => (unassigned)
** Changed in: adduser (Ubuntu)
Importance: Undecided =&g
Thanks for confirming.
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
--
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/1485095
Title:
package systemd
** Package changed: systemd (Ubuntu) => libmtp (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/1487471
Title:
Udev rule for MTP with nvidia Shield
To manage notifications
There's nothing to fix, it's just a harmless warning as rsyslog drops
in its own configuration file.
** Summary changed:
- systemd-tmpfiles-clean reports warning in logs
+ systemd-tmpfiles-clean warns about duplicate /var/log line
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
Reopened, but if anything this is more a problem with logcheck (or
perhaps just missing ignore patterns). systemd's journal keeps the
priority of a message, and logcheck should certainly only look at >=
warning?
** Changed in: systemd (Ubuntu)
Status: Won't Fix => Triaged
--
You received
Fixed in version 223 (in wily), thus closing.
** 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/1476256
Switching user with "su" does not count as opening a full new session
(see /etc/pam.d/su). This does not start a session bus and systemd
process in particular.
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
This got fixed in 219-6, and thus in 15.04.
** Package changed: udev (Ubuntu) => systemd (Ubuntu)
** Bug watch added: Debian Bug tracker #765577
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765577
** Also affects: systemd (Debian) via
** Package changed: udev (Ubuntu) => systemd (Ubuntu)
** No longer affects: systemd (Ubuntu)
** Project changed: systemd => systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Status: New => Triaged
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
** Summary changed:
-
There isn't anything to go with here. It seems independent of the init
system, and mostly related to the graphics driver, i. e. a kernel issue.
Can you please "e"dit the default boot entry in grub and drop the
"quiet"? Please make/attach a screenshot (with a camera) when it
freezes. Thanks!
**
Removing systemd (219-7ubuntu6) ...
systemd is the active init system, please switch to another before removing
systemd.
Err, yes. Don't do that then :-)
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
This sounds similar to bug 1270257, but that was closed due to getting
too much noise.
** Package changed: dbus (Ubuntu) => network-manager (Ubuntu)
** No longer affects: systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
This means that pam-auth-update crashed with signal 11 (i. e. SIGSEGV).
** Package changed: systemd (Ubuntu) => pam (Ubuntu)
** Summary changed:
- package libpam-systemd:amd64 204-5ubuntu20.12 failed to install/upgrade:
subprocess installed post-installation script returned error exit status
Can you please run
grep -r 'compare-version.*' /var/lib/dpkg/info/
and copypaste the output here? There is no hit on my current wily
system, but perhaps you have some weird initramfs-tools version?
** Package changed: systemd (Ubuntu) = initramfs-tools (Ubuntu)
** Summary changed:
-
Public bug reported:
systemd 225 was released upstream yesterday:
http://lists.freedesktop.org/archives/systemd-devel/2015-August/034036.html
This includes two small new features and the usual lot of bug fixes:
* machinectl gained a new verb 'shell' which opens a fresh shell on the
systemd-journal-remote is not built in the current wily package as it's
blocked by feature freeze and bug 1488341. Reopening.
** Changed in: systemd (Ubuntu)
Status: Fix Released = Triaged
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
--
You received
Ah, this indeed does not only affect the link command but others too.
I'm just confused -- why do you call link *and* enable with an
absolute path? You can just do the latter, that implies link. Or you
explicitly link and then usually call enable on a name only, not a
path.
Either way,
** Bug watch added: Debian Bug tracker #742802
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742802
** Also affects: systemd (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742802
Importance: Unknown
Status: Unknown
--
You received this bug notification because
/etc/udev/rules.d/ is not supposed to have any rules except 70
-persistent-net.rules. Distribution supplied rules are in
/lib/udev/rules.d/.
Please run ubuntu-bug storage to file a new report with debug data,
this will be easier for the both of us. Thank you!
** Changed in: systemd (Ubuntu)
Thanks Thaddaeus! Committed.
** Changed in: systemd (Ubuntu)
Status: Confirmed = Fix Committed
** Project changed: initramfs-tools = null-and-void
** Changed in: null-and-void
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop
** Package changed: systemd (Ubuntu) = apport (Ubuntu)
** Summary changed:
- using PathExistsGlob in apport-noui.path results in test failures
+ running whoopsie during tests causes test failures
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
/etc/hosts doesn't seem to update even after installing nss-myhostname
FTR, the purpose of nss-myhostname is *not* to update /etc/hosts, but to
add itself to /etc/nsswitch.conf and dynamically resolve its own
hostname (from /etc/hostname).
--
You received this bug notification because you are
This was fixed in 223-1 with http://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?id=c1f6db6f9a
** Changed in: systemd (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Summary changed:
- package systemd 224-1ubuntu1 failed to install/upgrade: triggers looping,
abandoned
+ package systemd 224-1ubuntu1 failed to install/upgrade: dpkg package triggers
looping, abandoned
** Package changed: systemd (Ubuntu) = dpkg (Ubuntu)
--
You received this bug
Reassigning to pam which ships the pam-auth-update script.
** Package changed: systemd (Ubuntu) = pam (Ubuntu)
** Summary changed:
- libpam-systemd ignores force-confdef and force-confold when configuring
+ pam-auth-update ignores force-confdef and force-confold when configuring
--
You
It recommends d-bus, and recommends are installed by default. See
https://www.debian.org/doc/debian-policy/ch-relationships.html .
systemd works fine without dbus, just some things (logind, nspawn,
calling CLI tools as non-root) won't work. But this does make sense on
small installations,
Public bug reported:
The current gtk+3.0 in -proposed breaks reverse dependencies on
powerpc/ppc64el, such as
https://launchpad.net/ubuntu/+source/packagekit/0.8.17-4ubuntu5.
I reproduced this on a ppc64el machine, and reduced it a bit:
$ pkg-config --print-errors gtk+-3.0
Package mirclient was
I reverted that patch, as it would again cause fatal errors to be
ignored. We should put back --quiet, and fix adduser to not hide errors
with --quiet (linked Debian bug).
** Bug watch added: Debian Bug tracker #763055
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763055
** Also affects:
The next upload will revert this, so reopening the bug right away.
** Changed in: systemd (Ubuntu)
Status: Fix Released = Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
** Package changed: ifupdown (Ubuntu) = systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Status: New = In Progress
** Changed in: systemd (Ubuntu)
Importance: Undecided = High
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
--
You received this bug
** No longer affects: udev (Ubuntu)
** Changed in: systemd (Ubuntu)
Status: New = Triaged
** Changed in: systemd (Ubuntu)
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
If /dev/bcacheN does not exist, it is either a kernel problem
(missing/broken driver?) or perhaps a bug in bcache-tools that is
missing to put some necessary kernel modules, sysctls, or other files
into initramfs. udev is not responsible for creating device nodes,
that's the kernel's job. It *is*
*** This bug is a duplicate of bug 1438301 ***
https://bugs.launchpad.net/bugs/1438301
This is the same as bug 1438301. Apparently you have a broken BIOS which
reports a wrong lid switch state.
Workaround for now: Set HandleLidSwitch=ignore in
/etc/systemd/logind.conf
** This bug has been
@Albert: trusty tasks added for ecryptfs and ubiquity. I'll upload
ecryptfs for trusty together with the fix for bug 1453738.
** Also affects: ubiquity (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: ecryptfs-utils (Ubuntu Trusty)
Importance: Undecided
** Bug watch added: Debian Bug tracker #774153
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774153
** Also affects: systemd (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774153
Importance: Unknown
Status: Unknown
** Changed in: systemd (Ubuntu)
Status:
Is this still a thing? This hasn't moved in two years, and this kind of
massive redesign work isn't somethign which we should discuss at the
distro level, but at upstream. I suggest discussing that on
http://lists.freedesktop.org/mailman/listinfo/systemd-devel or providing
issues/pull requests on
** Changed in: systemd (Ubuntu)
Status: Triaged = Won't Fix
--
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/1455683
Title:
Starts emergency mode for failed auto fstab mounts
lucid archive grep finally finished, too. It's basically
Documentation/cgroups/cgroups.txt from teh various kernel sources, plus
libvirt documentation/config file, and the ltp tests again.
** Attachment added: lucid archive grep for /dev/cgroup
OK, that should have repaired your system.
** Changed in: systemd (Ubuntu)
Status: Incomplete = Invalid
--
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/1471527
Title:
Thanks for verifying! As this only affected the PPA I'm closing this
now.
** Changed in: systemd (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
Thanks Michael. So I'll close this report for the time being. Please
yell here when you see it again and reopen (or I'll reopen it for you, I
remain subscribed).
** Changed in: systemd (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of
There is absolutely zero distro integration with the systemd EFI boot
loader, unlike GRUB and friends. Thus we don't build/ship systemd's boot
loader so far, and bootctl can merely show you boots, but its other
commands don't work.
If that's confusing, we could also stop installing bootctl
We don't build/ship the coredump bits, as we use Apport in Ubuntu.
** Changed in: systemd (Ubuntu)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
** Bug watch added: Debian Bug tracker #765586
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765586
** Also affects: systemd (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765586
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Package changed: systemd (Ubuntu) = hdparm (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/1470014
Title:
systemd-udevd: Process '/lib/udev/hdparm' failed with exit
:perf_event:/user.slice
3:blkio:/user.slice
2:net_cls,net_prio:/user.slice
1:name=systemd:/user.slice/user-1000.slice/session-c2.scope
** Affects: systemd (Ubuntu)
Importance: High
Assignee: Martin Pitt (pitti)
Status: In Progress
** Changed in: systemd (Ubuntu)
Importance: Undecided
Confirmed. Installing lsh-server in vivid and logging in via ssh
reproduces this easily. There is no $XDG_SESSION_ID and login session
for lsh, so pam_systemd doesn't run. lsh-server does not ship any PAM
config at all.
** Summary changed:
- unprivileged lxc containers don't work in remote
501 - 600 of 7748 matches
Mail list logo
