<polyrtm>
this is probably a noob question but why does river not take up the whole display when i start it even though the output is configured correctly? there's a gray bar on the right side of my screen
<polyrtm>
wow was that the first message in 2 days oops
polyrtm has quit [Quit: Lost terminal]
polyrtm has joined #river
<polyrtm>
okay i have figured out that it only happens when i start river from a display manager
polyrtm has quit [Client Quit]
plebbos has joined #river
plebbos has quit [Quit: Leaving]
snakedye has quit [Ping timeout: 260 seconds]
talismanick has quit [Ping timeout: 240 seconds]
lxsameer has joined #river
snakedye has joined #river
elshize has quit [Ping timeout: 240 seconds]
elshize has joined #river
pkap has joined #river
<leon-p>
huh, so apparently restarting the DBUS daemon kills river. The more you know...
<leon-p>
so polyrtm has unfortunately left, but if anyone else has this issue: This is caused by the display manager starting the X server because it thinks river is an X WM. So river will run as a window inside X.
<ifreund>
heh, I was wondering what was going wrong there :D
waleee has quit [Ping timeout: 260 seconds]
polyrtm has joined #river
<polyrtm>
hello i saw the discussion on the logs
<polyrtm>
i thought it might be something similar, how do I get the dm to run it as a wayland compositor then?
<leon-p>
The DM must have support for Wayland sessions, otherwise you are out of luck.
<leon-p>
which one are you using?
<polyrtm>
i tried both sddm and lightdm
<polyrtm>
I'm also on nixos which complicates things slightly
<leon-p>
lightdm definitely did not support Wayland up until recently (also can't remember if it does now, actually)
<leon-p>
gdm is known to work
<polyrtm>
i tried starting gdm with wayland enabled and it just hung
<leon-p>
(also you need to put the river session file into the wayland session directory)
<polyrtm>
yeah nixos complicates that slightly but i did the equivalent of that
<polyrtm>
although it might out it in the x session directory
<polyrtm>
lemme check
<leon-p>
I unfortunately can't help you debug your DM setup, however my recommendations are 1) check if your DM version supports Wayland, 2) check if your river session is correctly picked up as a Wayaldn session
<polyrtm>
okay thanks
snakedye_real has joined #river
elshize has quit [Quit: WeeChat 3.4]
<polyrtm>
okay apparently it just puts everything in the x sessions and for it to be put in the wayland sessions list the package has to provide a session file in /share/wayland-sessions
<polyrtm>
so to get this to work i may have to patch the nixos package
polyrtm has quit [Quit: Connection closed]
elshize has joined #river
snakedye_real has quit [Quit: snakedye_real]
elshize has quit [Quit: WeeChat 3.4]
elshize has joined #river
elshize has quit [Quit: WeeChat 3.4]
lxsameer has quit [Ping timeout: 248 seconds]
elshize has joined #river
lxsameer has joined #river
pkap has quit [Quit: Client closed]
waleee has joined #river
lxsameer has quit [Ping timeout: 240 seconds]
pkap has joined #river
lxsameer has joined #river
waleee has quit [Ping timeout: 248 seconds]
waleee has joined #river
pkap has quit [Ping timeout: 252 seconds]
talismanick has joined #river
talismanick has quit [Remote host closed the connection]