Bug 1545317 - User switching leads to failed session scopes
Summary: User switching leads to failed session scopes
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: lightdm-gtk
Version: 27
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Alternative GTK desktop environments
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-14 15:53 UTC by Mike Gerber
Modified: 2018-03-15 17:17 UTC (History)
5 users (show)

Fixed In Version: lightdm-gtk-2.0.4-1.fc27 lightdm-gtk-2.0.4-1.fc26
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-15 15:27:52 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Mike Gerber 2018-02-14 15:53:49 UTC
Description of problem:

User switching using "dm-tool switch-to-greeter" leads to failed session scopes:

# sudo journalctl -u session-c3.scope -b
-- Logs begin at Tue 2017-05-30 08:31:32 CEST, end at Wed 2018-02-14 16:48:16 CET. --
Feb 14 14:11:51 rowling.lan.rwsr-xr-x.de systemd[1]: Started Session c3 of user lightdm.
Feb 14 14:11:57 rowling.lan.rwsr-xr-x.de systemd[1]: session-c3.scope: Killing process 3961 (lightdm) wit
Feb 14 14:11:57 rowling.lan.rwsr-xr-x.de systemd[1]: session-c3.scope: Killing process 3972 (lightdm-gtk-
Feb 14 14:11:57 rowling.lan.rwsr-xr-x.de systemd[1]: Stopping Session c3 of user lightdm.
Feb 14 14:13:27 rowling.lan.rwsr-xr-x.de systemd[1]: session-c3.scope: Stopping timed out. Killing.
Feb 14 14:13:27 rowling.lan.rwsr-xr-x.de systemd[1]: session-c3.scope: Killing process 3961 (lightdm) wit
Feb 14 14:13:27 rowling.lan.rwsr-xr-x.de systemd[1]: session-c3.scope: Killing process 3972 (lightdm-gtk-
Feb 14 14:13:27 rowling.lan.rwsr-xr-x.de systemd[1]: Stopped Session c3 of user lightdm.
Feb 14 14:13:27 rowling.lan.rwsr-xr-x.de systemd[1]: session-c3.scope: Unit entered failed state.

Version-Release number of selected component (if applicable):
lightdm-gtk-2.0.3-4

How reproducible:
Steps to Reproduce:
1. Login with one user
2. /usr/bin/dm-tool switch-to-greeter
3. Login with another user
4. check systemctl --failed

Actual results:
Failed state of session-cX.scope

Expected results:
No failed state

Additional info:

Comment 1 Mike Gerber 2018-02-14 15:54:43 UTC
Configuring lightdm-gtk using --enable-kill-on-sigterm fixes this.

Comment 2 Fedora Update System 2018-03-06 15:15:30 UTC
lightdm-gtk-2.0.4-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2018-55ed35375d

Comment 3 Fedora Update System 2018-03-06 15:15:48 UTC
lightdm-gtk-2.0.4-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-78c76f6d86

Comment 4 Fedora Update System 2018-03-07 15:00:42 UTC
lightdm-gtk-2.0.4-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-55ed35375d

Comment 5 Fedora Update System 2018-03-07 15:35:12 UTC
lightdm-gtk-2.0.4-1.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-78c76f6d86

Comment 6 Mike Gerber 2018-03-13 14:05:52 UTC
lightdm-gtk-2.0.4-1.fc27 fixes this for me!

Comment 7 Fedora Update System 2018-03-15 15:27:52 UTC
lightdm-gtk-2.0.4-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2018-03-15 17:17:54 UTC
lightdm-gtk-2.0.4-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.