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
columbarius has joined #wayland
columbar1 has quit [Ping timeout: 480 seconds]
silver has quit [Ping timeout: 480 seconds]
Seirdy has quit [Ping timeout: 480 seconds]
hegstal has quit [Remote host closed the connection]
charafau[m] has joined #wayland
silver has joined #wayland
silver has quit [Quit: One for all, all for One (2 Corinthians 5)]
Seirdy has joined #wayland
silver has joined #wayland
silver has quit []
silver has joined #wayland
remanifest has quit [Remote host closed the connection]
nerdopolis has quit [Ping timeout: 482 seconds]
zebrag has quit [Remote host closed the connection]
wwalker_ has joined #wayland
wwalker has quit [Ping timeout: 480 seconds]
wwalker_ has quit [Remote host closed the connection]
SallyAhaj has joined #wayland
tzimmermann has joined #wayland
dcz_ has joined #wayland
danvet has joined #wayland
jgrulich has joined #wayland
leon-p has joined #wayland
pochu has joined #wayland
hardening has joined #wayland
audgirka has joined #wayland
hegstal has joined #wayland
mcepl has quit []
mcepl has joined #wayland
rasterman has joined #wayland
mcepl has quit []
mcepl has joined #wayland
jgrulich has quit [Remote host closed the connection]
jgrulich has joined #wayland
<pq>
jadahl, :-DDD Fo ikke övertackas. Or something. I barely remember anything I used to read as a child on the electric heater in the bathroom.
<pq>
LaserEyess, your VM viewer application needs to forward absolute pointer positions to the guest OS, not relative.
<pq>
or, not *only* relative
<jadahl>
pq: yea :P (same here, reading on electric radiator)
<MrCooper>
pq: hmm, for some reason from you I only see � instead of ä
<pq>
UTF in IRC is hard :-/
<pq>
the last time I poked at the character set config (a decade or two ago) there were still channels I was on that didn't get the memo about UTF yet.
<pq>
at least I see my and your scandinavic characters correctly
<jadahl>
i see both of yours scandinavian letters correctly
<pq>
I also have the stack urxvt -> ssh -> screen -> irssi; so many places for things to be misconfigured. If it even is on my side.
<pq>
almost as bad as endianess bugs
<MrCooper>
my ä is German though :P
<pq>
a with two dots?
<MrCooper>
yep, what do you see instead?
<pq>
I see a with two dots.
<pq>
but I wrote övertackas with o with two dots.
<MrCooper>
I see � for that as well
<pq>
aaanyway :-)
<MrCooper>
I guess my client uses UTF-8 and yours doesn't, and something is failing to convert
<pq>
does → look like a right-arrow?
<MrCooper>
it does
<pq>
so I get that sent and seen right
<MrCooper>
→ ‽
<pq>
right-arrow and a fat question mark
<pq>
oh what has #wayland become :-p
<MrCooper>
weird, anyway sorry for the digression
MrCooper has quit [Remote host closed the connection]
<plaes>
Using `systemctl start weston@tty7.service` to start it
<pq>
right, so are you already on tty7 when you do that?
<plaes>
nope, remotely from ssh
<pq>
Do you have VTs to begin with?
<plaes>
but.. after running manually as root: `weston-launch -t /dev/tty7 -u paf` it complains and exits with: `fatal: environment variable XDG_RUNTIME_DIR is not set.`
<plaes>
and then I can start the systemd service and everything works
<pq>
that running manually as root should actually change anything AFAIU
<pq>
*should not
<pq>
so is the difference in starting the service from ssh vs. local login?
<pq>
logind seems to be happy to grant session control, and give Weston a DRM fd, but for some reason KMS refuses...
<pq>
I'm afraid I can't guess why that could be.
<plaes>
how should I start the system from local login?
<plaes>
as root or "special" user?
<pq>
since you have logind running, the manual way to start weston is to log in as a normal user and run simply 'weston'
<plaes>
yeah, that works
<pq>
ok cool, so the basics work
<pq>
which means the problem is somewhere in the service unit or PAM configuration direction, probably
<plaes>
it even works when launching via getty
<plaes>
getty@tty1.service -> usr/bin/agetty --autologin username --noclear %I $TERM ; and then using the .profile
<pq>
the only thing I can think of is that when you start the service, it starts on an inactive VT, so logind does not actually give DRM master status to Weston. But I'm not sure.
<pq>
you could try the weston service on tty1 instead of tty7 maybe?
<plaes>
already tried :)
<pq>
same problem?
<plaes>
yeah, weird thing is that weston thinks that it's correctly working - I can even launch the applications but they are not displayed
<pq>
yes, KMS errors are not fatal in Weston, it tries to keep on going
<pq>
I guess you would need to drill down to why the kernel is giving EPERM on KMS atomic commit. Is it because Weston is not DRM master, or something else.
<plaes>
actually, when I try to start on tty1 it fails with: weston@tty1.service: Failed with result 'protocol
<pq>
when using logind, it's logind that controls the DRM master status
<plaes>
any idea how to track down on these EPERM issues?
<pq>
that... stops very short
<plaes>
when I removed `--debug` it went a bit further
<plaes>
but still not much relevant info
<pq>
that's odd, --debug shouldn't have any effect
<pq>
um, there is /sys/module/drm/parameters/debug where I think you could write a value to enable various kernel debug prints, but I'm not sure they tell the reason about EPERM. Might be good to try.
<daniels>
0x1f is the value
mcepl has quit []
<plaes>
thanks
<pq>
thanks, I wondered off to find the docs for it and failed