So, I have some problems with X.Org and its related components. Everything is fine starting up, but it's the exiting or shutting down that issues kind of crop up.

Once I'm in Fluxbox, if I right-click -> fluxbox menu -> exit, it kicks me back to the command line instead of back to SLiM. Secondly, xlockmore only happens when invoke it from the menu. Then, when it is running, I have to use my root password to unlock the screen instead of my user password.

I'd like SLiM to startup again when I exit Fluxbox, xlockmore to start automatically after a certain amount of time of inactivity and password protect a certain amount of time after that, and I'd like the user password to unlock the screen. Let me know which files I need to post.

Right now, I can think of these files being useful:/usr/share/fluxbox/menu

# We always try and start X on a static VT. The various DMs normally default# to using VT7. If you wish to use the xdm init script, then you should ensure# that the VT checked is the same VT your DM wants to use. We do this check to# ensure that you have't accidently configured something to run on the VT# in your /etc/inittab file so that you don't get a dead keyboard.CHECKVT=7

# What display manager do you use ? [ xdm | gdm | kdm | kdm-3.5 | kdm-4.0 | entrance ]# NOTE: If this is set in /etc/rc.conf, that setting will override this one.# KDE-specific note: kdm-3.5 and kdm-4.0 are just examples. You will find all # possible versions by looking at the directories in /usr/kde/.DISPLAYMANAGER="slim

# Hide the mouse cursor (note: does not work with some WMs).# Valid values: true|false# hidecursor false

# This command is executed after a succesful login.# you can place the %session and %theme variables# to handle launching of specific commands in .xinitrc# depending of chosen session and slim theme## NOTE: if your system does not have bash you need# to adjust the command according to your preferred shell,# i.e. for freebsd use:# login_cmd exec /bin/sh - ~/.xinitrc %sessionlogin_cmd exec /bin/bash -login /etc/X11/xinit/xinitrc

# Commands executed when starting and exiting a session.# They can be used for registering a X11 session with# sessreg. You can use the %user variable## sessionstart_cmd some command# sessionstop_cmd some command

# Available sessions (first one is the default).# The current chosen session name is replaced in the login_cmd# above, so your login command can handle different sessions.# see the xinitrc.sample file shipped with slim sourcessessions xfce4,icewm,wmaker,blackbox

nightmorph wrote:Hmm, this is interesting. Just last night I was helping out another Gentoo user who has the same issue, only with SLiM and Xfce. There seems to be something going around.

You do have xdm in your default runlevel, right? Also, it may turn out to not matter, but did you emerge pambase with the "consolekit" USE flag? Your slim.conf looks okay, so . . . are you using baselayout-2/openrc?...

Yes, xdm is in the default runlevel. I do not have PAM installed, and pam and consolekit are not in my USE flags. Here's my /etc/make.conf:

# These settings were set by the catalyst build script that automatically# built this stage.# Please consult /etc/make.conf.example for a more detailed example.CFLAGS="-march=athlon-xp -O2 -pipe -fomit-frame-pointer"CXXFLAGS="-march=athlon-xp -O2 -pipe -fomit-frame-pointer"# WARNING: Changing your CHOST is not something that should be done lightly.# Please consult http://www.gentoo.org/doc/en/change-chost.xml before changing.CHOST="i686-pc-linux-gnu"MAKEOPTS="-j2"

I've disabled all USE Flags to begin with, and added the flags that I wanted. Going for a minimalist setup here, which is why I'm using SLiM and Fluxbox. I may have disabled something necessary deeper in the system. I have sys-apps/baselayout-1.12.11.1 installed on my system, and openrc is masked.

The best things in life are free.http://www.gentoo.orgGuy 1: Surely, you will fold with me.Guy 2: Alright, but don't call me Shirley.

Now, on to xlockmore. Fluxbox has placed it in my menu as "Lock Screen". That's all fine and dandy, but the problem here is that it no longer locks the screen. However, if I run xlock through Eterm, it wants to know what passphrase I want to unlock the screen, like so:

$xlockKey:Again:

And then the screen saver comes up and then I can press whatever key and enter to unlock it.

The best things in life are free.http://www.gentoo.orgGuy 1: Surely, you will fold with me.Guy 2: Alright, but don't call me Shirley.