Arch Linux

DelusionalLogic

Member

Registered: 2013-05-07

Posts: 40

dm-tool does nothing

I'm running (what i consider) a fairly standard setup:

- systemd
- lightdm
- bspwm
- openbox
- lightdm-gtk3-greeter

My main wm is bspwm, but sometimes i'd like to switch to openbox. For this i'm guessing dm-tool is the right way.

"dm-tool switch-to-greeter" is supposed to switch me back to the greeter, so i can log in to my openbox session. but when i try to do this nothing happens. "dm-tool lock" is supposed to lock the current seat and require my password to unlock, also this does nothing.

I looked in a D-Bus debugger, and lightdm is registered, the tool also shows up (very shortly) when i execute the command. Below is what is written to the log:

[+21257.82s] DEBUG: Seat seat0: Locking
[+21257.82s] DEBUG: Seat seat0: Creating greeter session
[+21257.82s] DEBUG: Seat seat0: Creating display server of type x
[+21257.82s] DEBUG: Using VT 2
[+21257.82s] DEBUG: Seat seat0: Starting local X display on VT 2
[+21257.82s] DEBUG: DisplayServer x-1: Logging to /var/log/lightdm/x-1.log
[+21257.82s] DEBUG: DisplayServer x-1: Writing X server authority to /run/lightdm/root/:1
[+21257.82s] DEBUG: DisplayServer x-1: Launching X Server
[+21257.82s] DEBUG: Launching process 26168: /usr/sbin/X :1 -seat seat0 -auth /run/lightdm/root/:1 -nolisten tcp vt2 -novtswitch
[+21257.82s] DEBUG: DisplayServer x-1: Waiting for ready signal from X server :1
[+21257.85s] DEBUG: Process 26168 exited with return value 1
[+21257.85s] DEBUG: DisplayServer x-1: X server stopped
[+21257.85s] DEBUG: Releasing VT 2
[+21257.85s] DEBUG: DisplayServer x-1: Removing X server authority /run/lightdm/root/:1
[+21257.85s] DEBUG: Seat seat0: Display server stopped
[+21257.85s] DEBUG: Seat seat0: Stopping session
[+21257.85s] DEBUG: Seat seat0: Session stopped
[+21257.85s] DEBUG: Seat seat0: Stopping display server, no sessions require it

It looks like it's doing what it's supposed to, it just never actually switches me to the new virtual terminal. why? (it's probably the novtswtich parameter, but why have that then)

Quick edit: I should probably mention that even though it says it's logging to x-1.log it deletes that right after it closes, so it's there for about 0.03 seconds, i can't catch that.

Last edited by DelusionalLogic (2015-01-09 21:44:58)

DelusionalLogic

Member

Registered: 2013-05-07

Posts: 40

Re: dm-tool does nothing

I'm in a situation now where i don't know what to do. I fixed the issue, but i guess this could be useful for someone at some point.

What i did was look in the Xorg log. Xorg was complaining that it couldn't find a driver, this was not a surprise as my system was running on pure magic at the time. Somehow the root x server knew how to set up my monitors, but no other x server did. I went through the wiki configuring nvidia with twinview, and now it works.

In short, the problem was that i forgot to configure x to use the nvidia driver.