Ask your questions here.
Post a reply

slim is dead, and save yourself some pain...

Fri Jan 23, 2015 1:25 am

My iso works properly. The installed system has a similar bug to what i had with my iso's booting.

The system goes through the whole boot fine until it tries to load the desktop manager. It just brings me to a black screen with a non-blinking text cursor at the top left of the screen.

Checking var logs. I settled upon slim.log since slim is what is not working.
Code:


slim: waiting for X server to begin accepting connections.


slim: waiting for X server to begin accepting connections.
slim: pam_open_session(): User not known to the underlying authentication module


slim: waiting for X server to begin accepting connections.
slim: pam_open_session(): User not known to the underlying authentication module


slim: waiting for X server to begin accepting connections.
slim: pam_open_session(): User not known to the underlying authentication module
Last edited by shamil on Mon Jan 26, 2015 12:39 am, edited 2 times in total.

Re: CAn't get to login screen

Fri Jan 23, 2015 12:15 pm

There was something with the username before. You had to boot with username=guest. What's up with that? What username did you create with the initial debian installation, and did you change it at some point? Maybe there's some file where it didn't get changed.

Re: CAn't get to login screen

Fri Jan 23, 2015 4:18 pm

I switched over to user for the user account on the iso relieving me of needing to do username=guest as a boot up option.

Re: CAn't get to login screen

Fri Jan 23, 2015 6:03 pm

How did you change the user name? For reference, you can check the commands inside the change-username script that comes with refractainstaller. There are a couple of sed commands that go into the user's config files and change /home/$oldname to /home/newname. That's in addition to three usermod commands that change username, group and home directory.

It works with startx if you kill slim?

Edit: try this in your home directory
Code:
grep guest .* 2>/dev/null
grep -r guest .config 2>/dev/null
grep -r guest .local 2>/dev/null

That will check for "guest" in all the hidden files in your home directory (top level) and also in the .config and .local directories (all levels). If you wanted to check all the hidden directories, run the first grep command above with the -r option (recursive).

Re: CAn't get to login screen

Sat Jan 24, 2015 1:09 am

I didn't change the user name. I went back to create an installation with "user" just for systemd since that seems to work better with the new system, made an iso, upon installing when the installer lets you change the user account name, i gave it something different. Password changing works no problem.

Re: CAn't get to login screen

Sat Jan 24, 2015 2:20 pm

Code:
slim: pam_open_session(): User not known to the underlying authentication module


From the pam man page:
The pam_open_session(3) function sets up a user session for a previously successful authenticated user. The session should later be terminated with a call to pam_close_session(3).


From the antix forum:
http://antix.freeforums.org/viewtopic.p ... view=print

Don't know if either of these is helpful. Maybe a problem with slim.conf autologin settings, maybe a problem with slim and pam. Have you tried setting the user name in slim.conf before making the snapshot? You shouldn't have to do that, but trying it might help identify the problem.

Also, it says "previously successful authenticated user" and I'm not entirely sure what that means. Has your user logged into the desktop with slim at least once before making the snapshot? I don't know if that matters.

I'm mostly guessing. I tried to install slim this morning, but it requires consolekit and libsystemd0, and those are not on the test installation. I've got some other test installs (in vbox) and maybe I can try with one of those. Have to sort through them to see what's what.

Re: CAn't get to login screen

Sat Jan 24, 2015 11:08 pm

Yup, the information from the antix link was the solution to my problem. Slim.conf has been modified. I just made default_user blank. Going to a login screen now actually works!!! Thx

EDIT: Did some extra research on slim. Arch users love using it. However, it appears to be abandoned by the developer. Also, it needs tweaking to make work with systemd where as other dm's can just be installed, used, and then tweaked if desired. Just wanted a lightweight dm. Going with qingy.
Post a reply