[Solved] User Login Loop after OpenBox Installation

[Mich-C]

Hello there.
I installed the Openbox window manager from the Package manager tool. (it also installed its 2-3 dependencies)
I was able to use openbox, but after I restarted lightdm to switch back to the default Xfce Desktop I get this problem:
I can login just in root-mode, if login in user mode lightdm restarts in loop every time I try to login.

I faced this problem in the past with my previous MX installation (https://mxlinux.org/forum/viewtopic.php ... b56f198c5a) that time I accidentally messed up file permissions using a file manager in root mode, while this time I avoided that. (Probably that time this loop was caused by the openbox installation too)

If I press ctrl+fn+f1 and I give commands I always get strange outputs.
For example with "startx" I get:

Code: Select all

xinit: server error
xauth: timout in locking authority file /home/michele/.Xauthority

Can you help me guys?

[Head_on_a_Stick]

I can login just in root-mode

^ Never do this.

if login in user mode lightdm restarts in loop every time I try to login.

Have you checked the LightDM log?

Post it here if you can't make any sense of it.

For example with "startx" I get:

Code: Select all

xinit: server error
xauth: timout in locking authority file /home/michele/.Xauthority

~/.Xauthority is probably root-owned now.

Try deleting that file, the X server will re-create it automatically when you log in again.

The plain startx command will run whichever alternative is set as x-session-manager (or x-window-manager if there is no session manager), unless you have a file at ~/.xsessionrc, ~/.xinitrc or ~/.xsession instructing otherwise.

To change that use

Code: Select all

# update-alternatives --config x-session-manager

Reference: https://wiki.debian.org/Xsession

Have you tried following the advice that fixed the problem last time?

[Mich-C]

Have you checked the LightDM log?

lightdm --test-mode

Code: Select all

Failed to use bus name org.freedesktop.DisplayManager, do you have appropriate permissions?

I thoght the problem was the "--test-mode flag" so I tryed also "sudo lightdm" and the ouptup given was the same

~/.Xauthority is probably root-owned now.
Try deleting that file

I applied he solution to my last problem was
I deleted it using "sudo rm ~/.Xauthority" and I also tryed renaming it "mv .Xauthority .Xauthority.bak"

Have you tried following the advice that fixed the problem last time?

Last time the owner of my whole user folder was the root user instead of the normal user. I checked but this time it's not the case.

The plain startx command will run whichever alternative is set
To change that use

Code: Select all

# update-alternatives --config x-session-manager

Ops... I rogot about this command. I'll try it anyway
Apart this I don't know what to do at this point... (I've reinstalled a month ago)

[Head_on_a_Stick]

Last time the owner of my whole user folder was the root user instead of the normal user. I checked but this time it's not the case.

OK, so are any files in $HOME owned by root?

Code: Select all

find ~ -user root

^ Run that command as your normal user.

I don't know what to do at this point

Check the LightDM log or post it here if you can't make sense of it.

If you don't know where the LightDM log is then ask your favourite search engine.

[richb]

I have had this happen when my Home partition was full.

[Mich-C]

Thank you richb, I'll check that also!

Code: Select all

find ~ -user root

Code: Select all

/home/michele/xonfig/xfce4/xfconf/xfce-perchannel-xml/xfce4-notifyd.xml
/home/michele/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-panel.xml
/home/michele/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-power-manager.xml
/home/michele/.config/xfce4/panel/xfce4-orageclock-plugin-l.rc /home/michele/.config/dconf/user
/home/michele/ACEauthority
/home/michele/.cache/gstreamer-1.0/registry.x86_64.bin
/home/miche1e/.cache/sessions/thumbs-mx:1
find: ■/home/michele/xache/sessions/thumbs-mx:1■: Permesso negato
/home/michele/.cache/dconf
find: ■/home/michele/.cache/dconf■: Permission negated
/home/michele/.xfce4-session.uerbose-log 
/home/michele/droidcam-64bit/u412loopback/u412loopback-dc.ko
/home/michele/droidcam-64bit/u412loopback/Amp_uersions
/home/michele/droidcam-64bit/u412loopback/Amp_uersions/u412loopback-dc.mod
/home/michele/droidcam-64bit/u412loopback/M12loopback-dc.mod.o.cmd
/home/michele/droidcam-64bit/u412loopback/.u412loopback-dc.ko.cmd
/home/michele/droidcam-64bit/u412loopback/u412loopback-dc.o
/home/michele/droidcam-64bit/u412loopback/u412loopback-dc.mod.c
/home/michele/droidcam-64bit/u412loopback/u412loopback-dc.mod.o
/home/michele/droidcam-64bit/u412loopback/modules.order
/home/michele/droidcam-64bit/u412loopback/Module.symuers
/home/michele/droidcam-64bit/u412loopback/.u412loopback-dc.o.cmd
/home/michele/.1ocal/share/nomacs/settings.ini
/home/michele/droidcam.tar.ba
/home/michele/.dbus/session-bus/06f79b20aea4a4ea6b653aa15c92bd2d-1

Check the LightDM log or post it here if you can't make sense of it.

Here's the log!

Code: Select all

[,6.00s] DEBUG: Logging to /war/log/lightdm/lightdm.log
[46.00s] DEBUG: Starting Light Display Manager 1.16.3, UID=O PID.4009
[v6.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[.0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/Ol_debian.conf 
[.0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/62_MX-17.conf
[.0.00s] DEBUG:	[SeatDefaults] is now called [Seat:.], please update this configuration 
[.0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d 
[00.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[.0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[.0.005] DEBUG:	[SeatDefaults] is now called [Seat:.l, please update this configuration
[.0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.005] DEBUG: Registered seat module xlocal
[.0.00s] DEBUG: Registered seat module xremote
[.0.00s] DEBUG: Registered seat module unity
[.0.025] DEBUG: Monitoring logind for seats
[.0.02s] DEBUG: Mew seat added from logind: seatO
[+0.02s] DEBUG: Seat seatO: Loading properties from config section Seat:.
[,0.02s] DEBUG: Seat seatO: Starting
[.0.02s] DEBUG: Seat setae: Creating user session
[.0.0Zs] DEBUG: Loading users from org.freedesktop.Accounts
[.0.0Zs] DEBUG: User /org/freedesktop/Accounts/User1000 added
[.0.02s] DEBUG: Seat seatO: Creating display seruer of type x
[+0.03s] DEBUG: Using VT 7
[+0.03s] DEBUG: Seat seatO: Starting local X display on VT 7
[.9.03s] DEBUG: DisplaySeruer x-1: Logging to /uar/log/lightdmix-1.1og
[.0.03s] DEBUG: DisplaySeruer x-1: Writing X server authority to /uar/run/lightdm/root/:1 
[,0.03s] DEBUG: DisplaySeruer x-1: Launching X Server
[+0.03s] DEBUG: Launching process 4014: /usr/bin/X -dpi $DPI :1 -seat seatO -auth /uar/run/lightdm/root/:1 -nolisten tcp ut7 -noutswitch
[+0.03s] DEBUG: DisplaySeruer x-1: Waiting for ready signal from X server :1
[.0.03sl DEBUG: Acquired bus name org.freedesktop.DisplayManager
[.0.03s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat8

[Head_on_a_Stick]

Try this command as your normal user:

Code: Select all

sudo chown -R "${USER}:${USER}" ~

Then check for root-owned files in $HOME again, repeat the command if there are some left.

[Mich-C]

Try this command as your normal user:

Code: Select all

sudo chown -R "${USER}:${USER}" ~

Then check for root-owned files in $HOME again, repeat the command if there are some left.

Many thanks! Everything seems ok now!
First time I inserted the command this way

Code: Select all

sudo chown -R "${michele}:${michele}" ~

but it actually was

Code: Select all

sudo chown -R "${USER}:${USER}" ~

. (forgive my ignorance )
Now When I use the command to display files owned by root in my home folder I get nothing from terminal, great!

At this point can I ask you which is the right command to exit from an openbox session without corrupting the login??
Consider that I installed a clean openbox from the package manager, I haven't customized it yet, so the only feature I can use now is launching apps right clicking on the desktop

[gosia]

Hello Mich-C,

At this point can I ask you which is the right command to exit from an openbox session without corrupting the login??

I'm using the exit-antix package. Also works well under Openbox.

many greetings gosia

[Head_on_a_Stick]

which is the right command to exit from an openbox session

Code: Select all

openbox --exit

Or

Code: Select all

pkill openbox

EDIT: please mark the thread [SOLVED].