Slim look and functionality

[black-clover]

Hello,

I started a new thread so whomever is interested in setting uo Slim will find the information more easily.
I've got everything pretty much working editing two files (besides /etc/rc.d/rc.x).

In ~/.Xinitrc I put just:

Code: [Select]

exec $1
In /etc/slim.conf the lines I've changed are:

Code: [Select]

# Available sessions (first one is the default).
sessiondir /usr/share/xsessions/
and:

Code: [Select]

login_cmd           exec /bin/bash -login ~/.xinitrc %session
That besides setting the theme of choice.

As Roarde pointed out, Slim is very smooth passing from the login screen to the WM desktop, with Jwm too.
However I was curious if someone was able to get the same smooth transition on logout, without a flash of the black screen before returning to the login screen.

[roarde]

That "flash" of text is rc.vlinit being run again, as the exit from X is treated like a change of runlevel. Early on, rc.vlinit detects an executable rc.sysvinit and uses that instead of itself. Following that and the remainder of the chain it restarts will show you where that text comes from.

I can only think of two choices:
    Run a daemon like plymouth to "eat" the screen with pretty pictures, not releasing it for text output.
    Or send all of the text from any involved script to a logfile, and write out anything that would clear the screen.

[black-clover]

I got  a strange thing.
I installed slim several times on VL Light using the same config files, without any problem.
But, when I installed it on VL-STD I got the following error, when attempting to open the USB memory with spacefm:

Code: [Select]

Error creating textual authentication agent: Error opening current controlling terminal for the process (`/dev/tty'): No such device or address (polkit-error-quark, 0)
Error mounting /dev/sdb1: GDBus.Error:org.freedesktop.UDisks2.Error.NotAuthorizedCanObtain: Not authorized to perform operation

However I do not get this error if I login as another user.
The only files I changed on the account with this problem were .xinitrc and .bashrc
I changed those to match the config of the user that works, but to no avail.

[roarde]

One thing to check:

Code: [Select]

su root -c 'diff -u /home/<user that fails>/.bashrc /home/<user that works>/.bashrc | less'

[roarde]

We talked about this in IRC last night (read "this morning"), and we hacked it into a working condition. Today, nightflier dropped into the channel and straightened me out on the xinitrc difference between STD and Light:

There are several ways to get from a terminal session to an X session. Two of those ways are fairly standard:

• Edit /etc/X11/xinit/xinitrc, or link it to an existing xinitrc.<DE> to select the system-default X session. Users wanting something else then write their own ~/.xinitrc. 7.2 Light does this.
• Place a .xinitrc in /etc/skel/, so newly created users have one. The version in skel starts the usual DE, of course. Users change that by editing. 7.2 Standard does this.

Slim's notes suggest providing a ~/.xinitrc somewhat like its own template. You did that, which overwrote the existing, working ~/.xinitrc. And now you know a lot more and had more fun than if everything had gone smoothly first time.

For someone looking in on this, what finally got the session to start with needed auths was to replace the end of Slim's "login_cmd" line with . /etc/X11/xinit/xinitrc.xfce. But that left no choice of session either at login time, or by a regular user's edit of ~/.xinitrc.

How 'bout this?:  Think of Slim as a startx substitute. Read startx(1) and write an /etc/X11/xinit/xinitrc.slim that works as that manpage describes, Allow for a "system-default" session to be started if no parameters are given, and for startup of the indicated session when one is. Hint: xinitrc.* are in the same directory. Don't get in startx's way, nor in gdm's.

Enjoy