Bug 844399 - perhaps systemd-logind kills sessions on logout
Summary: perhaps systemd-logind kills sessions on logout
Keywords:
Status: CLOSED DUPLICATE of bug 821254
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-30 13:40 UTC by udo
Modified: 2012-08-01 16:38 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-08-01 16:38:15 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description udo 2012-07-30 13:40:53 UTC
Description of problem:
I see ' ...killed.' when exiting a terminal shell window from user a back to user b. I see this on more than one system, all running fedora 17, current w.r.t. yum.


Version-Release number of selected component (if applicable):
systemd-44-17.fc17.i686

How reproducible:
log in as user
`su -` to root
press ctrl-D.
two out of my three running boxes do show this behaviour.
The most powerful one (this one) doesn't.

Steps to Reproduce:
1. See above.
2.
3.
  
Actual results:
See above.

Expected results:
No killed session. Normally ended sessions instead.

Additional info:
coinciding logging in messages file:
Jul 30 15:34:18 recorder systemd-logind[27360]: New session c831 of user mythtv.
Jul 30 15:34:20 recorder systemd-logind[27360]: Removed session c831.

Comment 1 Michal Sekletar 2012-07-30 13:56:29 UTC
Are you running any programs after logging as user a. Can you provide output of ps command?

Comment 2 udo 2012-07-30 15:05:28 UTC
[root@recorder ~]# su - mythtv
Authentic:
	Indubitably true, in somebody's opinion.
[mythtv@recorder ~]$ ps
  PID TTY          TIME CMD
 8055 pts/0    00:00:00 bash
 8088 pts/0    00:00:00 ps
[mythtv@recorder ~]$

Comment 3 Michal Schmidt 2012-07-30 15:34:46 UTC
(In reply to comment #0)
> two out of my three running boxes do show this behaviour.
> The most powerful one (this one) doesn't.

Just guessing... Does this box have a custom kernel? If so, is it possible to reproduce the bug with a Fedora kernel?

Comment 4 udo 2012-07-30 15:43:54 UTC
All of my PC's run a 'custom' kernel: plain kernel.org code with very little patching.
So what would you suggest that kills my sessions?
(I do not want to exclude this possibility but it sounds far fetched and the two boxes in question have work to do so I'd rather not reboot them)

Comment 5 Michal Schmidt 2012-07-30 15:51:44 UTC
If, for instance, you have disabled CONFIG_AUDIT, you are exercising certain less tested codepaths inside systemd-logind and PAM modules.

Comment 6 udo 2012-07-30 15:57:27 UTC
CONFIG_AUDIT is set on one box where the issue occurs, but is not set on the otehr box where the issue occurs.

Comment 7 udo 2012-07-31 13:07:57 UTC
See https://bugzilla.redhat.com/show_bug.cgi?id=821254
Same issue?

Comment 8 Michal Schmidt 2012-08-01 16:38:15 UTC
The problem has been identified as incorrect PAM configuration, in bug 821254.

*** This bug has been marked as a duplicate of bug 821254 ***


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