Slack wm are not logging out completely blackscreen with hyphen in upper left corner

BW-userx · 03-07-2017, 05:33 PM

I thought it was just Fluxbox that was doing this. But now that I got BlackBox running with dockapps .. I will configure, log out, log back in check to see if that works etc.. then after a bit I stop logging in and out and in, then just sit and watch a movie etc.. then get back to it, then when I log out, it does not completely log out. as the header question states.

It goes into the black screen and hangs with the hyphen up in the left corner. I end up having to hard shut it down and turn it back on again.

Does anyone know why it is not "killing" the wm fully to get back to the login screen (runlv 4). ??

frankbell · 03-07-2017, 08:02 PM

I've not encountered this in years of using Fluxbox and Slackware.

Have you looked in the log files for some hints? I would start with /var/log/Xorg.0.log

Also, did the system work properly at one time, or has this been a constant behavior?

BW-userx · 03-07-2017, 08:14 PM

Quote:

Originally Posted by frankbell

I've not encountered this in years of using Fluxbox and Slackware.

Have you looked in the log files for some hints? I would start with /var/log/Xorg.0.log

Also, did the system work properly at one time, or has this been a constant behavior?

I've looked at xsession.errors - it has been a constant sporadic behavior. Just started looking to try and find out what login manager slack is using.

what should I look for in /var/log/Xorg.0.log, keywords?

frankbell · 03-07-2017, 08:53 PM

Quote:

what should I look for in /var/log/Xorg.0.log

I have no idea; I stay out of log files except when absolutely necessary

.

I'd look for some that looks odd or inconsistent or reports an error on closing.

By the way, tail is a very useful command for looking log files. I recommend using it with the -n switch, so you can tail the last n lines, rather than wade trough the whole thing.

BW-userx · 03-07-2017, 08:59 PM

Quote:

Originally Posted by frankbell

I have no idea; I stay out of log files except when absolutely necessary

.

me too.

Quote:

Originally Posted by frankbell

I'd look for some that looks odd or inconsistent or reports an error on closing.

By the way, tail is a very useful command for looking log files. I recommend using it with the -n switch, so you can tail the last n lines, rather than wade trough the whole thing.

Yep Tail know it, but it doesn't do much good if the errors are in the middle or top of the log file.

ran into that before too.

I installed lxdm and set it to kill=1 on the session during logout.. I'll wait and see if that changes the behavior or not.

frankbell · 03-07-2017, 09:02 PM

When I have an error such as this one and want to look at the log file, I try to recreate the error and look at the relevant log file(s) quick like a bunny while the error message, if any, is still near the end of the log(s).

BW-userx · 03-07-2017, 09:08 PM

Quote:

Originally Posted by frankbell

When I have an error such as this one and want to look at the log file, I try to recreate the error and look at the relevant log file(s) quick like a bunny while the error message, if any, is still near the end of the log(s).

yeaaahhhhh I See your point of view. but if it still does this then that will eliminate the login manager as the culprit. if not then it will point me in that direction of it is the login manager doing this.

"avoiding them log files"

same like swapping out cards to see if that fixes it or not methodology.

Qury · 03-08-2017, 03:10 AM

Try adding the following to /etc/lxdm/PostLogout

killall --user $USER -TERM

Didier Spaier · 03-08-2017, 04:32 AM

This is most probably the consequence of an oddity in one of your customized WM startup scripts (/usr/bin/start<wm>, /etc/X11/xinit/xinitrc.<wm> ~/.fluxbox/startup, whatever).

Please post them if you want us to help you find the culprit.

BW-userx · 03-08-2017, 07:35 AM

.xinit

Quote:

#!/bin/sh
#
# ~/.xinitrc
#
# executed by startx (run your window manager from here)

if [ -d /etc/x11/xinit/xinitrc.d ]; then
for f in /etc/x11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fi

# exec gnome-session
# exec startkde
# exec startxfce4
# ...or the window manager of your choice

it was doing this on and off for a while, it wasn't until I changed WM iceWM, then BlackBox just to see what that is is about because it is installed. It started doing it in them as well. That is when i decided to post on it.

BW-userx · 03-08-2017, 08:05 AM

Quote:

Originally Posted by Qury

Try adding the following to /etc/lxdm/PostLogout

killall --user $USER -TERM

I was using slacks default login manager, I just installed lxdm to see if that will fix it. if yes then it has to be something to do with the default login manager that slack uses. trial and error

got a wait and see.

Didier Spaier · 03-08-2017, 08:27 AM

Quote:

Originally Posted by BW-userx

.xinit

Code:

#!/bin/sh
#
# ~/.xinitrc
#
# executed by startx (run your window manager from here)

if [ -d /etc/x11/xinit/xinitrc.d ]; then
  for f in /etc/x11/xinit/xinitrc.d/*; do
    [ -x "$f" ] && . "$f"
  done
  unset f
fi

# exec gnome-session
# exec startkde
# exec startxfce4
# ...or the window manager of your choice

it was doing this on and off for a while, it wasn't until I changed WM iceWM, then BlackBox just to see what that is is about because it is installed. It started doing it in them as well. That is when i decided to post on it.

This script does nothing on Slackware if you use startx that does not source or exec ~/.xinit. Furthermore there is a typo as it is /etc/X11/xinit/ not /etc/x11/xinit.

BW-userx · 03-08-2017, 08:32 AM

Quote:

Originally Posted by Didier Spaier

This script does nothing on Slackware if you use startx that does not source or exec ~/.xinit. Furthermore there is a typo as it is /etc/X11/xinit/ not /etc/x11/xinit.

yeah I know on that first part, just showing what is in there due to whatever someone said in here about how one effects another, and I got nothing in there to effect anything.

typo???
oic it now. little x big X . that is a system written file not me written file.

BW-userx · 03-08-2017, 08:46 AM

Code:

userx@slackwhere⚡️~⚡️$locate kde
locate: fatal error: Could not find user database '/var/lib/slocate/slocate.db':  No such file or directory

am I doing something wrong here so I can find the kde stuff to give it a look over, cuz I think that is the login manager default in this slack.

BW-userx · 03-08-2017, 08:50 AM

belay that last post. Fixed it.

Code:

userx@slackwhere⚡️~⚡️$sudo updatedb

http://www.linuxquestions.org/questi...ate-db-482616/