Arch Linux

Okay, it appears the only way to properly get my user to show up in who is to use a login manager that supports it. Even editing the proper sessreg commands into startx doesn't work.

This is a single-user machine, I'll just hard-code the proper locking command in. Sorry for the noise.

Doesn't seem to be consolekit's fault. I've found some people having similar problems with xdm and slim as login managers. Now I just need to figure out how to make startx deal with it.

Okay, I'm an idiot. I *do* have that directory, I just forgot to list hidden files. I stuck some debug points in the script and it appears it's not finding my user, on further examination because nothing for this display shows up in `who`. I think it might be consolekit's fault. I'll see if I can do some further debugging.

I just tested with startx, and, while the directory already existed, a socket was created for my session. I'm not sure what's actually creating the directory on my system.

I just use startx, with a couple arguments to wrap all of .xinitrc in a consolekit session.

@Celti - How do you start your X sessions? If it's with a login manager, which one?

This fails to work for me because I don't have a /tmp/.X11-unix/ directory. Anyone know what I can do to fix that?

@krisse7 - pm-utils-screen-lock-0.1.2-1 gets rid of the "return 0". It'll really only help if all sessions are using the same screen locker.

Just noticed one thing: is there a reason for the "return 0" in the script? Because now it locks only the first X session and leaves other possible sessions unlocked.

@krisse7 - pm-utils-screen-lock-0.1.1-1 now searches for gnome-screensav to deal with the 15 character limit.