Summary: | x11-misc/slim isn't starting - ? | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Justin Lecher (RETIRED) <jlec> |
Component: | Current packages | Assignee: | Ian Stakenvicius (RETIRED) <axs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | Adrian.Bassett, desktop-misc |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
slim.log
Xorg.0.log slim.conf |
Description
Justin Lecher (RETIRED)
![]() Created attachment 377746 [details]
slim.log
slim.log
Created attachment 377748 [details]
Xorg.0.log
Xorg log
Created attachment 377750 [details]
slim.conf
slim.conf
(In reply to Justin Lecher from comment #0) > What works: > > * Starting with "strace slim -nodaemon" And of course startx works as well The PAM errors in slim.log concern me.. If I had to guess, I think that slim cannot authenticate the primary root session and therefore is forced to exit. Do you know what (if anything) is non-standard in /etc/pam.d/ ? the files system{,-local}-{login,auth}, slim, and slimlock would be of particular interest here. Perhaps I should at that more description. It seems that X starts, e.g. the focus moves to vt7 but no slim comes up. If I do startx then the login prompt appears on VT7 which works for logins as long as the second X is running. I rebuilt quite some packages yesterday and now it works. I will reopen if it comes back. (In reply to Justin Lecher from comment #8) > I rebuilt quite some packages yesterday and now it works. I will reopen if > it comes back. What comes back? You didn't identify a specific issue so any future bug where "slim doesn't work" looks like this one. What is still missing here is what PAM might say about what slim is doing, probably in the syslog. it maybe correlated with #501330. It still comes from time to time, but no clue how to solve it or to debug it. Why did you put the crappiest Summary ever back? It doesn't explain anything. (In reply to Jeroen Roovers from comment #12) > Why did you put the crappiest Summary ever back? It doesn't explain anything. And why did you out something wrong into the Summary? Let's place a "?" because nobody knows the root cause |