This bug was fixed in the package systemd - 204-5ubuntu20.19
---
systemd (204-5ubuntu20.19) trusty-proposed; urgency=medium
* Add upstream-uaccess-Add-new-DRM-render-nodes.patch: Add uaccess tag for
"renderD*" devices for AMD GPUs. (LP: #1536438)
* libpam-systemd: Don't restar
** Tags removed: verification-done-trusty verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1473800
Title:
restarting logind during systemd update ca
** Changed in: systemd (Ubuntu Trusty)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1473800
Title:
restarting logind during systemd update causes screen to lock
Worked for me on trusty.
I had trouble with sudo apt-get install systemd-services/trusty-proposed
-- it wanted to uninstall too many things. Probably it would have worked
fine with sudo apt-get install systemd-services/trusty-proposed libpamd-
systemd/trusty-proposed. Oops.
I instead asked apt to
Hello Michael, or anyone else affected,
Accepted systemd into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/204-5ubuntu20.19 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:
** Description changed:
When systemd is updated (through the update manager), the screen/session
locks when processing the update.
I've had this happen twice I think, and the only suspicious packages are
the systemd ones.
+
+
+ SRU INFORMATION:
+
+ - Fix from wily/xen
** Changed in: systemd (Ubuntu Trusty)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1473800
Title:
restarting logind during systemd update causes
** Also affects: systemd (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1473800
Title:
restarting logind during systemd update causes scree
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu Trusty)
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/1473800
Titl
Adding trusty task, as trusty is apparently also affected (see duplicate
bug 1543883).
** Changed in: systemd (Ubuntu Trusty)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
This bug was fixed in the package systemd - 225-1ubuntu7
---
systemd (225-1ubuntu7) wily; urgency=medium
* Don't restart logind on upgrades any more. This kills X.org (#798097)
while logind doesn't save/restore its open fds (issue #1163), and also
gets confused about being i
** 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
Bugs, which is subscribe
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 version).
When doing "systemctl daemon-reexec; [optional sleep]; systemctl try-
restart systemd-logind", loginctl show-session reveals that the current
session gets IdleHint=yes for a second or two, which causes the screen
lock. This does not seem to happen when *only* restarting logind without
a previous da
14 matches
Mail list logo