ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput | register your nick to speak
xst9948 has quit [Ping timeout: 480 seconds]
dcz_ has quit [Ping timeout: 480 seconds]
c7s has quit [Ping timeout: 480 seconds]
caveman has quit [Remote host closed the connection]
<kennylevinsen>
dman_lfc: your compositor should start xwayland itself
<dman_lfc>
weston is the compositor
<dman_lfc>
the instructions say to run with the --xwayland flag to start the xserver listening for appropriate apps
<kennylevinsen>
Did you manage to start Weston before this?
<kennylevinsen>
dman_lfc: after all you say "question about xwayland", but the error you get is Weston failing to start for reasons unrelated to Xwayland.
<dman_lfc>
yes weston starts & is running, so is the xwayland server
<dman_lfc>
xserver listening on display :0
<kennylevinsen>
Then what's the problem?
<dman_lfc>
the issues are - [01:00:16.369] atomic: couldn't commit new state: Permission denied
<kennylevinsen>
It's possible to have sporadic permission denied errors from drm (e.g. during vt switches) - what's the symptom? Weston never managing to put anything on screen?
<kennylevinsen>
dman_lfc: you may still lack proper permission. The "correct" way to start Weston on a non-systemd platform would be either to use seatd (daemon or seatd-launch, if Weston is built with libseat support) or weston-launch.
<kennylevinsen>
these all run a tiny daemon as root that acts as intermediate for opening drm and evdev devices
<dman_lfc>
currently everything runs as root
___nick___ has joined #wayland
<dman_lfc>
we provide root access out of the box - hence init.d scripts run as root too
___nick___ has quit []
___nick___ has joined #wayland
dcz_ has joined #wayland
rasterman has joined #wayland
ecloud has quit [Ping timeout: 480 seconds]
ecloud has joined #wayland
flacks has quit [Quit: Quitter]
flacks has joined #wayland
bittin has joined #wayland
fmuellner has joined #wayland
bittin_ has joined #wayland
bittin_ has quit [Remote host closed the connection]
<kennylevinsen>
dman_lfc: so Weston is running as root but you still get permission denied and nothing shows up on screen?
<dman_lfc>
correct
<dman_lfc>
bear in mind i'm just using weston to facilitate xwayland
<dman_lfc>
let me explain a bit more & you can tell me if I'm mad :-)
<kennylevinsen>
Sure :)
<dman_lfc>
I'm working on a linux project - 'batocera linux' which facilitates emulators - provide front-end (emulation station) & pre-packaged emulators ready to go
<dman_lfc>
one of the emulators I want to run on the raspberry pi is supermodel (emulates sega model3)
<dman_lfc>
this is an older emulator written for X11 & openGL
<dman_lfc>
to run it (using OpenGL for the Pi4) I need to run against Xwayland
<dman_lfc>
thefore the gui (emulation station) launched a python script to start the associated emulator
<dman_lfc>
currently it's not detecting the running background xwayland server
<dman_lfc>
we use buildroot to build the linux os, it has weston available, hence using that at the wayland compositor
<dman_lfc>
does that help?
<kennylevinsen>
How does the emulation station GUI work? X, fbdev, direct drm, ...?
<dman_lfc>
wayland
<dman_lfc>
weston is using drm backend
<kennylevinsen>
Okay, good. Sounded like you were trying to start Weston + Xwayland for just that single emulator while something else was drm master
<kennylevinsen>
Xwayland is right now an unimportant detail - that should just work once Weston starts correctly. Try to share a link to your Weston start script.
<soreau>
well if running as root.. why use weston-launch at all?
<soreau>
does it work if you just run weston as root?
<dman_lfc>
for drm backend i believe
<kennylevinsen>
soreau: I don't remember if weston has a direct fallback
<dman_lfc>
weston doesn't start with it removed
<dman_lfc>
let me try without the $WESTON_ARGS
<dman_lfc>
nope :-(
<dman_lfc>
i understood you had to run weston in it's own VT
<dman_lfc>
hence using openvt
<kennylevinsen>
The VT it runs on need to not be occupied but it could have been confused by the VT switch
<kennylevinsen>
Can you try to manually run weston-laumch from a tty?
<dman_lfc>
yeah i can - i'm sure it will bring up the desktop aok
<kennylevinsen>
If that works we know your setup is sane and all your problems revolve around the init script
<dman_lfc>
have desktop
<kennylevinsen>
And you just called weston-launch as root?
<dman_lfc>
yes
Akra has joined #wayland
<soreau>
maybe that XDG_RUNTIME_DIR needs to fall back to an absolute path?
<kennylevinsen>
dman_lfc: immediate hunch: might be a controlling tty thing and you need to use the --tty flag for weston-launch, which in turn require the -u flag (could be "root" I guess?)
<kennylevinsen>
soreau: I assume XDG_RUNTIME_DIR wouldn't matter until at least a Weston shell is shown...
<kennylevinsen>
dman_lfc: the only real difference to being called from init script vs. you doing stuff from try would be some environment variables, controlling tty and what VT is active. Note that any VT not currently running a drm session is fine. A kernel console doesn't matter.
<dman_lfc>
i will try i didn't think --tty was valid for weston-launch
<kennylevinsen>
Please do not paste logs into IRC. Use a pastebin for anything over a few lines.
<dman_lfc>
will do
<kennylevinsen>
Have you tried manually changing to VT 6? Don't remember if the tty flag does VT activation
<dman_lfc>
those aren't in the log output but in the terminal
<dman_lfc>
will go up & switch to tty6
Akra has quit []
<dman_lfc>
i assume you want me to alt f6 - correct?
<kennylevinsen>
Yeah
<dman_lfc>
brb - it's upstairs (getting my step count up)
<kennylevinsen>
I'm pretty confident this would all Just Work(tm) with libseat and either seatd-launch or seatd deamonized. I can't wait for weston-launch to be retired :(
<dman_lfc>
yeah showed the desktop
<kennylevinsen>
Okay, try to add your openvt on top
<kennylevinsen>
Or just pick tty1
<kennylevinsen>
You don't need to pick another tty if nothing graphical is going to run on tty1...
<dman_lfc>
the xkbcommon: ERROR: is alarming or is that normal?
GoGi has quit [Quit: GoGi]
GoGi has joined #wayland
<kennylevinsen>
Not alarming unless something is broken
<kennylevinsen>
It's just complaining that your locale is "C" instead of, say, en_US.UTF-8
<kennylevinsen>
So it can't make any localized decisions
<dman_lfc>
ah ok
<dman_lfc>
so when you say add openvt on top what are you suggesting?
<kennylevinsen>
We concluded that weston-launch worked but did not activate (I.e. switch to) the VT you started it on. Either pick tty1/VT1 to not need a switch, call chvt before starting weston-launch, or wrap weston-launch in openvt -s just like before.
<kennylevinsen>
otherwise Weston just sits forever idle on vt6, waiting for someone to find it
<dman_lfc>
so if I do some like this - weston-launch -u root --tty=/dev/tty1 -- --log=/userdata/system/logs/weston.log
<dman_lfc>
no openvt ^
<kennylevinsen>
sure should work. At least after reboot if you just left the device on vt6.
<kennylevinsen>
It worked with manual VT switching just a moment ago no?
<dman_lfc>
yes when i manually switched to tty6 earlier
<kennylevinsen>
Did you check if something comes up on screen or are you only looking at the log?
<kennylevinsen>
If nothing comes up still, add "chvt 1" (or 6 if you change back to tty6) before weston-launch. That's identical to you alt+fN'ing around.
<dman_lfc>
ok
<dman_lfc>
doesn't start
<dman_lfc>
soreau: card0 doesn't do KMS, hence why it uses card1 - just a fyi
<dman_lfc>
thanks for trying kennylevinsen - i'm off to bed here it's after midnight. i have built an image with sway added - i will look into it tomorrow
moa has quit [Ping timeout: 480 seconds]
bluebugs has joined #wayland
GoGi has quit [Quit: GoGi]
GoGi has joined #wayland
wrl_ has quit []
wrl has joined #wayland
GoGi has quit []
GoGi has joined #wayland
GoGi has quit []
GoGi has joined #wayland
luc4 has joined #wayland
GoGi has quit [Quit: GoGi]
GoGi has joined #wayland
GoGi has quit []
GoGi has joined #wayland
GoGi has quit []
GoGi has joined #wayland
GoGi has quit []
GoGi has joined #wayland
GoGi has quit []
GoGi has joined #wayland
GoGi has quit []
GoGi has joined #wayland
GoGi has quit []
GoGi has joined #wayland
GoGi has left #wayland [#wayland]
tkilian has joined #wayland
tkilian has quit [Ping timeout: 480 seconds]
___nick___ has quit []
___nick___ has joined #wayland
___nick___ has quit []
c7s has joined #wayland
___nick___ has joined #wayland
bittin has quit [Read error: Connection reset by peer]