FS#12456 - [slim] "console" command no longer working
Attached to Project:
Arch Linux
Opened by David Rosenstrauch (darose) - Monday, 15 December 2008, 06:12 GMT
Last edited by Andrea Scarpino (BaSh) - Friday, 23 October 2009, 05:28 GMT
Opened by David Rosenstrauch (darose) - Monday, 15 December 2008, 06:12 GMT
Last edited by Andrea Scarpino (BaSh) - Friday, 23 October 2009, 05:28 GMT
|
Details
Description:
Not sure when this broke (or how) but the "console" command is no longer working in the slim login manager. For some reason the xterm command that it's trying to execute dies, and slim dies along with it (leaving an orphaned X session). Additional info: * package version(s) 1.3.1-1 * config and/or log files etc. slim.conf containing the following (default) console command: console_cmd /usr/bin/xterm -C -fg white -bg black +sb -T "Console login" -e /bin/sh -c "/bin/cat /etc/issue; exec /bin/login" Steps to reproduce: 1) start slim 2) type the "console" command in the username box 3) watch slim die! |
This task depends upon
Closed by Andrea Scarpino (BaSh)
Friday, 23 October 2009, 05:28 GMT
Reason for closing: Upstream
Additional comments about closing: see comments
Friday, 23 October 2009, 05:28 GMT
Reason for closing: Upstream
Additional comments about closing: see comments
2) I'm not sure that any are needed. You can watch the xterm command die just by executing it from a console. (e.g., in konsole, paste in: /usr/bin/xterm -C -fg white -bg black +sb -T "Console login" -e /bin/sh -c "/bin/cat /etc/issue; exec /bin/login".) Only problem is that the xterm disappears too quickly to see why it's dying.
I don't know how slim works, but with the command you specified, it will launch an xterm that dies as soon as the login process terminates. If "login" is a disabled or non-existent user, xterm will die because you're returning whatever /bin/login returns.
As far as the "/usr/bin/xterm ... exec /bin/login command", that's been part of slim.conf for quite a while now, and used to work fine. (It would open up a teeny little xterm on the slim login screen.)
It's only been sometime in the last couple of weeks that it's failed to work. *Some*thing changed recently to make this stop working, but I have no idea what. (Any I would be surprised if my "console user" somehow got deleted in that time.)
Can anyone else even recreate this? Or is this just a problem on my machine?
/var/log/slim.log:
-------------------
/usr/bin/xauth: creating new authority file /var/run/slim.auth
[ here it restarts ]
Fatal server error: Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again.
I don't know when it stopped working. My monthly backup snapshot shows there were neither user or group "console" 30 days ago. Executing the same console_cmd from an already running X session works ok.
Another problem is the default session, config file says it should prepend the first listed under "sessions" as default, but the log file shows it didn't prepend anything to the "login_cmd", not until you press F1 at least once. I guess this should be directed upstream.
BTW, since there hasn't really been any progress made on the bug here, I filed an upstream bug as well: http://developer.berlios.de/bugs/?func=detailbug&bug_id=15142&group_id=2663
I'm not really sure whether the bug is upstream or Arch-specific, though.
Feb 2 11:34:21 daroselin2 slim: pam_unix(slim:auth): conversation failed
Feb 2 11:34:21 daroselin2 slim: pam_unix(slim:auth): auth could not identify password for [exit]
Feb 2 11:40:14 daroselin2 slim: pam_unix(slim:auth): conversation failed
Feb 2 11:40:14 daroselin2 slim: pam_unix(slim:auth): auth could not identify password for [console]
Anyone know enough about slim and/or pam to debug this?
So I'm guessing the problem must be in Arch's /etc/pam.d/slim file:
#%PAM-1.0
auth requisite pam_nologin.so
auth required pam_env.so
auth required pam_unix.so
account required pam_unix.so
session required pam_limits.so
session required pam_unix.so
password required pam_unix.so
The console and exit commands are apparently getting routed to pam_unix when they shouldn't be.
Anyone grok this file well enough to know where the bug is? Where did we even get the contents for this file? It doesn't ship with slim, so I'm wondering what the source is.
I also have hope that the community could fix it as they did with a few bugs by now, take a look at this topic: http://bbs.archlinux.org/viewtopic.php?id=65869