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
sav10 has quit [Remote host closed the connection]
flibitijibibo has joined #wayland
ybogdano has joined #wayland
dcz_ has quit [Ping timeout: 480 seconds]
columbarius has joined #wayland
co1umbarius has quit [Ping timeout: 480 seconds]
wb9688 has quit [Ping timeout: 480 seconds]
ybogdano has quit [Ping timeout: 480 seconds]
smallville7123 has quit [Ping timeout: 480 seconds]
fmuellner has quit [Ping timeout: 480 seconds]
Seirdy has joined #wayland
wb9688 has joined #wayland
Leopold_ has quit []
Leopold_ has joined #wayland
Brainium has quit [Quit: Konversation terminated!]
julio7359 has joined #wayland
julio7359 has quit [Remote host closed the connection]
AJC_Z0 has joined #wayland
AJ_Z0 has quit [Read error: Connection reset by peer]
AJC_Z0 is now known as AJ_Z0
julio7359 has joined #wayland
AJC_Z0 has joined #wayland
caveman has quit []
AJ_Z0 has quit [Ping timeout: 480 seconds]
AJC_Z0 is now known as AJ_Z0
uniqdom has joined #wayland
<uniqdom>
Hello, I'm new here, trying Wayland by using Weston in X11. Is there a way to share the clipbard between Weston and X11 apps?
julio7359 has quit [Ping timeout: 480 seconds]
julio7359 has joined #wayland
<soreau>
uniqdom: you can, if the x11 apps run through xwayland in the weston session
julio7359 has quit [Remote host closed the connection]
<soreau>
but to share as you're describing, that is something that isn't implemented AFAIK
<uniqdom>
soreau: I see.
<uniqdom>
can you also copy and paste with mouse?
<soreau>
highlight/middle-click to copy/paste?
<uniqdom>
yes
<uniqdom>
does that have a name? because it is different than the clipboard, I think
<soreau>
it works in wlroots compositors, not sure about weston, you'd have to try it yourself
<uniqdom>
ok. I'm really new here in wayland. I just wanted to test waydroid (and android vm). Wayland was a requierement, and I still had x11 in my system.
<uniqdom>
I will have to dig a bit what is wlroots
<uniqdom>
Thanks soreau, have a good day/night
uniqdom has quit [Quit: Leaving]
Lucretia has quit [Read error: Connection reset by peer]
Lucretia has joined #wayland
molinari has quit [Ping timeout: 480 seconds]
CodeSpelunker has joined #wayland
vano has joined #wayland
vano has quit []
smallville7123 has joined #wayland
smallville7123 is now known as Guest1222
smallville7123 has joined #wayland
Guest1222 has quit [Read error: Connection reset by peer]
i509VCB is now known as Guest1223
radu24284303951534727071489559 has joined #wayland
CodeSpelunker has quit [Ping timeout: 480 seconds]
CodeSpelunker has joined #wayland
radu24284303951534727071489559 has quit [Ping timeout: 480 seconds]
eroc1990 is now known as Guest1226
eroc1990 has joined #wayland
Guest1226 has quit [Ping timeout: 480 seconds]
caveman has joined #wayland
kts has joined #wayland
Seirdy has quit [Ping timeout: 480 seconds]
cvmn has joined #wayland
caveman has quit [Ping timeout: 480 seconds]
Fxzxmic has joined #wayland
Seirdy has joined #wayland
Fxzxmic has quit []
Fxzxmic has joined #wayland
tzimmermann has joined #wayland
smallville7123 has quit [Ping timeout: 480 seconds]
kts has quit [Quit: Leaving]
ppascher has quit [Ping timeout: 480 seconds]
smallville7123 has joined #wayland
hardening has joined #wayland
Fxzx_mic has joined #wayland
Fxzxmic has quit [Ping timeout: 480 seconds]
jgrulich has joined #wayland
CodeSpelunker has quit [Remote host closed the connection]
CodeSpelunker has joined #wayland
CodeSpelunker has quit []
Company has quit [Read error: Connection reset by peer]
Fxzxmic has joined #wayland
molinari has joined #wayland
Fxzx_mic has quit [Ping timeout: 480 seconds]
rasterman has joined #wayland
mvlad has joined #wayland
dcz_ has joined #wayland
bodiccea_ has joined #wayland
kts has joined #wayland
danvet has joined #wayland
ppascher has joined #wayland
smallville7123 has quit [Ping timeout: 480 seconds]
smallville7123 has joined #wayland
smallville7123 is now known as Guest1235
smallville7123 has joined #wayland
smallville7123 is now known as Guest1236
smallville7123 has joined #wayland
kts has quit [Quit: Leaving]
MajorBiscuit has joined #wayland
kts has joined #wayland
Guest1235 has quit [Ping timeout: 480 seconds]
Guest1236 has quit [Ping timeout: 480 seconds]
Leopold_ has quit [Ping timeout: 480 seconds]
kts has quit [Quit: Leaving]
Serus has quit [Ping timeout: 480 seconds]
Leopold_ has joined #wayland
Dami_Lu has quit [Remote host closed the connection]
Dami_Lu has joined #wayland
Fxzx_mic has joined #wayland
Fxzxmic has quit [Ping timeout: 480 seconds]
sav10 has joined #wayland
sav10 has quit []
sav10 has joined #wayland
sav10 has quit [Remote host closed the connection]
kts has joined #wayland
devilhorns has joined #wayland
junaid has joined #wayland
Fxzx_mic has quit []
Fxzxmic has joined #wayland
sav10 has joined #wayland
bodiccea_ has quit [Quit: Leaving]
<pq>
SardemFF7, I just noticed Gitlab telling me that a webhook in Weston was disabled after being retried multiple times. Does that mean anything to you?
<SardemFF7>
hum, is there a time for the fails?
<pq>
not really, I noticed the error banner just now
<pq>
no idea of any logs or anything
<daniels>
yeah, I've seen it periodically - connecting to the remote host times out
<SardemFF7>
in the webhook config, you can click on the webhook and see the history I think
<pq>
Doesn't seem to work that way. There are only buttons "test", "edit" and "delete".
<SardemFF7>
on the “edit” page?
ChengAnXu has joined #wayland
<pq>
ah, there is the log. I didn't dare "edit" at first. :-)
<pq>
1 day ago, Error: Net::ReadTimeout
<pq>
Jan 12, 2023 11:36am GMT+0200
junaid has quit [Ping timeout: 480 seconds]
Leopold___ has joined #wayland
Leopold_ has quit [Ping timeout: 480 seconds]
<SardemFF7>
thanks, checking
sav10 has quit [Ping timeout: 480 seconds]
<pq>
mjt, I'm curious, what does your keyboard manufacturer say about remapping on Linux (and not in the hardware)?
<pq>
mjt, I'm also curious about those Weston bugs, whether we know about those yet.
<mjt>
pq: I'm not sure I follow (re keyboard remapping). They suggest using standard tools to do that, either gui or setxkbmap or whatever. Most of the discussions seems to be about the layouts, which one is better and why
<pq>
mjt, setxkbmap is X11, IIRC. What other tools do they suggest? I'm not aware of any standard tools.
<mjt>
I'm not yet there. I do remember though that something quite similar to X11 keyboard definitions were used for linux console too
<pq>
I'm not sure about the console, but Wayland compositors use the exact same layout etc. files as Xorg.
<pq>
That's what xkbcommon implements, and pretty much all Wayland compositors use.
<pq>
none of those are relevant for Wayland compositors, I believe
<mjt>
I'll look at all this later. THere's one annoying thing on this kbd which I'll have to fix anyway. I just had no time for that
<mjt>
(the thing is that it doesn't have Ins key, instead it is Fn+Del, and it turned out I do use Shift+Ins quite a lot. On the other hand, right next to this Del they've PrtScrn which is useless but can be remapped to Ins. It even has the right label)
<mjt>
speaking of wayland issues, I don't know if these are due to freerdp or wayland. For one, Xfreerdp (yes it's X, ie, working with xwayland) can't run in fullscreen mode
<mjt>
s/wayland/weston/
sav10 has joined #wayland
<mjt>
this is with latest weston, it worked before
<pq>
oh, a regression, that would be really nice to report
<mjt>
with latest weston and current xfreerdp2, the fullscreen window is offset by the size of the waybar
<pq>
waybar on weston?
<mjt>
no
ChengAnXu has quit []
<mjt>
err. I tried them all in sequence, and each had their own issues, I'm confusing them now :)
<pq>
heh
<mjt>
weston, sway, cage, something else...
<pq>
anyway, the keyboard remapping works by writing a layout file, and then pointing your compositor to that instead of a standard layout, I believe.
<mjt>
there's the bar at the top of weston screen. xfreerdp /f does not cover that one, instead it is *moved* by that size down and *right*, keeping the same size
<mjt>
so bottom and right sides of the window are off the screen
<pq>
moved down because of the panel is what happens when maximized and it shouldn't happen for fullscreen, but moving also *right* make me thing it's not the panel's doing.
<pq>
*think
Fxzx_mic has joined #wayland
<mjt>
I haven't looked very closely because instead of 3..5 days this project took 3 months (with numerous combinations of software)
<pq>
since the app is running through Xwayland, this is probably an XWM bug in Weston.
<mjt>
so after trying new weston briefly, seeing this issue, I didn;'t dig in but moved on instead
<pq>
right, understandable
<mjt>
freerdp has wayland version. but due to previous bug in weston they changed quite some code in wlfreerdp
<mjt>
and it is not complete anyway
Fxzxmic has quit [Ping timeout: 480 seconds]
<mjt>
now when this thing *finally* works "somehow" (I ended up returning to ol'good Xorg entirely, and writing some glue in C - surprisingly there's no x idle program which actually works ;) - I had to write one), I now have some time to do debugging
<SardemFF7>
[about the webhook] that’s really weird, it seems that some buffer just fills itself and is not read anymore and when I restart it all gets read at once, I’ll have to do some load testing to figure it out I guess
<mjt>
(but I also have to catch the other stuff up too)
<pq>
SardemFF7, ok, thanks
<mjt>
pq: issue initially reported against freerdp which turned out to be weston issue: https://github.com/FreeRDP/FreeRDP/issues/6722 (I wrote about that at the end of that long page) - but while debugging it, we found various "fun" stuff in wlfreerdp who uses mouse coordinates in a wrong way..
<mjt>
I probably can bisect the fullscreen mode regression
genpaku has quit [Read error: Connection reset by peer]
<pq>
that would be nice :-)
genpaku has joined #wayland
sav10 has quit []
andyrtr_ has joined #wayland
MajorBiscuit has quit [Quit: WeeChat 3.6]
andyrtr has quit [Ping timeout: 480 seconds]
andyrtr_ is now known as andyrtr
fmuellner has joined #wayland
floof58 is now known as Guest1252
floof58 has joined #wayland
Guest1252 has quit [Ping timeout: 480 seconds]
kts has quit [Quit: Leaving]
Fxzxmic has joined #wayland
Fxzx_mic has quit [Ping timeout: 480 seconds]
rasterman has quit [Ping timeout: 480 seconds]
rasterman has joined #wayland
mjt has quit [Remote host closed the connection]
devilhorns has quit []
Leopold___ has quit [Remote host closed the connection]
Leopold_ has joined #wayland
mjt has joined #wayland
glisse is now known as Guest1257
glisse has joined #wayland
fmuellner has quit []
Guest1257 has quit [Ping timeout: 480 seconds]
dri-logger has quit [Ping timeout: 480 seconds]
fmuellner has joined #wayland
dri-logger has joined #wayland
Szadek has quit [Quit: WeeChat 3.8]
manuel1985 has joined #wayland
floof58 has quit [Quit: floof58]
fmuellner has quit []
fmuellner has joined #wayland
floof58 has joined #wayland
floof58 has quit []
Fxzxmic has quit []
kts has joined #wayland
dcz_ has quit [Ping timeout: 480 seconds]
smallville7123 has quit [Read error: Connection reset by peer]
jgrulich has quit [Ping timeout: 480 seconds]
rv1sr has joined #wayland
sav10 has joined #wayland
manuel1985 has quit [Ping timeout: 480 seconds]
manuel1985 has joined #wayland
<mjt>
pq: bisecting seems to be a bit difficult due to interdependencies..
<mjt>
how xwayland and weston relate to each other?
Company has joined #wayland
Leopold_ has quit [Ping timeout: 480 seconds]
rawoul has quit [Quit: leaving]
<ManMower>
mjt: hmm, that issue 6722 is hard to follow and messy, but at the end the quoted weston patch isn't what fixed that problem. freerdp commit 5b09cd57a7 probably did, as it does what gschwind suggested (stop setting the cursor hotspot wrong)
<mjt>
ManMower: yes it's messy as it hit multiple people and everyone tried to help :)
<mjt>
ManMower: the thing is: after 5b09cd57a7 it didnt work still
<ManMower>
what is "it"?
<mjt>
wlfreerdp. it still had that mouse pointer issue
<mjt>
jumpy mouse
<mjt>
but when switching weston from 10.0.2 to 10.0.3 (or is it 10.2=>10.3?) the problem disappears
<ManMower>
O.o
<mjt>
regardless of 5b09cd57a7
<ManMower>
but those patches are for weston's test clients
<ManMower>
not weston's cursor handling
<mjt>
I especially built two versions of weston when someone here said 10.0.3 has the fixes
<ManMower>
can you give me a quick way to reproduce this bug?
<ManMower>
I have windows machines on hand if that's necessary
Leopold has joined #wayland
<mjt>
heh. I'm tryin to setup a testbed with weston here currently
<mjt>
the prob was rather trivial to reproduce when run on weston directly (without additional compositor like gnome)
<mjt>
any mouse click in the remote freerdp window and the cursor goes off
<mjt>
with 5b09cd57a7, I *think* (I too am confused now by all that already), the cursor after click were *moving* to the edge of the remote desktop in diagonal direction
<mjt>
like animation
<mjt>
it stopped with weston 10.0.3
<ManMower>
do you build freerdp yourself?
<mjt>
I tried it too when debugging
<ManMower>
(because if you do, maybe you can save me time figuring out what cmake options I need to enable the right clients and what not...)
<mjt>
I built both freerdp and weston
<mjt>
it builds with everything by default iirc, but needs the right build-deps
<mjt>
if your distro have freerdp 2.8 or later it should be enough already
<mjt>
2.9 (current) had other issues with wlfreerdp (mentioned in my message at the end of 6722)
<mjt>
it'd be really great if you two (freerdp and wayland people) work together on this. They tried really hard to figure it out. I'm just a user (with strong programming expirence but not in these areas)
<mjt>
I'm trying to figure out what to do with the misplacement of xfreerdp window within current weston right now
Leopold has quit [Ping timeout: 480 seconds]
<mjt>
but it looks like i'll have difficult time with these :(
<ManMower>
looks like 2.8 is almost certain to have the cursor problem because the freerdp fix for it landed after 2.8.1 was released?
<mjt>
yes
<ManMower>
k
<ManMower>
I'll try newer.
<mjt>
I tried 2.9 (last) freerdp
<mjt>
with weston 10.0.1 and with weston 10.0.3 - for *sure*, but can't say with 100% certainity about 10.0.2
fmuellner has quit []
<mjt>
still have local build of 10.0.3
fmuellner has joined #wayland
<mjt>
the puzzling thing about this issue was that it (almost) never happened with other compositors (eg neither gnome/mutter nor sway). "Almost" because some reported it can be seen under gnome too
<mjt>
btw, why dialog(1) does not show box characters in weston terminal? does the term implement switching to box drawing?
<ManMower>
weston-terminal isn't something you should be using for anything beyond testing a copositor.
<ManMower>
stick to the "real" terminals. weston-terminal is a broken toy.
<mjt>
I see
<mjt>
I think it's good enough to run some simple command (like freerdp)
<ManMower>
to more directly answer your question, it's because weston-terminal isn't a very good terminal. :)
<ManMower>
yes
<ManMower>
but trying to use it as a daily driver will be painful :)
Leopold_ has joined #wayland
<mjt>
it could also be that I was tired when testing 10.0.3 + mouse in wlfreerdp, and haven't noticed something which made my test void. It's unlikely but possible.
<ManMower>
hmm, I just get a flash of display then the client disconnects.
<daniels>
at a guess, that'd be ack_configure mishandling
<ManMower>
"Closed from Wayland"
<ManMower>
looking at the log, yeah, probably ack_configure
tzimmermann has quit [Quit: Leaving]
<mjt>
with freerdp 2.9 and weston 10.0.1 the bug with mouse position is definitely there
<mjt>
just verified
<mjt>
there's also another issue with mouse cursor: it does not change - when hovering over window borders, over text input areas where it should become ][-bar, etc
<ManMower>
that's probably because the patch that fixes it (5b09cd57a7) is apparently not in a release yet
<ManMower>
yeah, I can't even get this to connect, so I'm not going to be much use debugging cursor problems. could be something in my local setup.
Seirdy has quit []
<mjt>
which freerdp version did you try?
<ManMower>
git master
<mjt>
oh.. they just switched to sdl2
<mjt>
2 days ago. it is bumpy :)
<ManMower>
2.8 actually connects
sav10 has quit [Ping timeout: 480 seconds]
<ManMower>
but doesn't bother to decorate the rdp window
<mjt>
it's barebones wrt decorations
Leopold_ has quit [Ping timeout: 480 seconds]
<ManMower>
well, I can reproduce the bug on 2.9 even with the patch that I thought should fix it cherry-picked.
<mjt>
heh
<mjt>
I was about to say the same thing :))
<mjt>
just built 2.9 with that patch and run a test :)
manuel1985 has quit [Ping timeout: 480 seconds]
<mjt>
< mvlad> weston 10.0.3 had some hot spot cursor fixes, if testing w/ latest should also be there.
<mjt>
that's where I got this info
<mjt>
on Dec-29
rawoul has joined #wayland
<ManMower>
oh, I wasn't running what I thought I was. heh.
<ManMower>
I'm not actually seeing that bug in windows paint
rawoul has quit []
<ManMower>
silly question... you're not running weston in a virtual machine, are you?
rawoul has joined #wayland
<mjt>
I tried in various
<mjt>
right now it is qemu with qxl
<mjt>
the same thing happens on bare metal
<ManMower>
are you certain? because in some virtual environments cursor hotspots aren't handled properly
<ManMower>
and gnome is probably more sensible at noticing this is the case than weston
akallabeth[m] has joined #wayland
<mjt>
Hi akallabeth[m]
<mjt>
this is the freerdp guy :)
<ManMower>
hopefully the matrix bridge is working today
<mjt>
well, lemme test on a baremetal just to be sure
<ManMower>
thanks
Leopold_ has joined #wayland
<mjt>
it'd be interesting to fix the hotspot position in qemu too, if you have some more info about that
<ManMower>
that's a bigger deal
<mjt>
(I had to switch from stdvga to qxl due to something else required by wlroots now but not supported in stdvga; myself, I come from qemu land, being one of its developers)
<mjt>
yes it definitely happens on bare hw
<mjt>
very well wisible in paint
<ManMower>
using which weston and freerdp versions?
<mjt>
it is 10.0.1 and 2.9 right now. trying with uwc patch now..
<mjt>
it looks *exactly* like in qemu
jgrulich has joined #wayland
<mjt>
on baremetal, the cursor changes properly within wlfreerdp window. While in qemu it does not
<mjt>
ok. 5b09cd57a7 definitely fixes some probs with the cursor
<mjt>
but some of them remains, and they're quite similar to this offset one
<ManMower>
what remains? I can't see anything wrong just moving the mouse around in windows paint
<ManMower>
(on weston 10.0.1 here)
<mjt>
like right now, after some clicking, the draw dot in paint which should be in the center of the mouse "cross" cursor, is off by a few pixels - diagonally to up-left. But the "vertical window resize" cursor (two arrows up-down) is off down to about 10 pixels
<mjt>
after moving it to top-left corner (trying to move below that) things cyncronises
<mjt>
(sp)
<mjt>
it's enough to drag paint window (clicking at the title bar and moving just a bit) to trigger that again
junaid has joined #wayland
<mjt>
s/below/beyong/ - something's wrong with my English today :)
<mjt>
actually the vertical resize arrow cursor is always off by about 10 pixels
<ManMower>
I get all sorts of spastic cursor behaviour without the uwc patch...
<ManMower>
oh, there's a wrong hotspot now
junaid_ has joined #wayland
fmuellner has quit []
fmuellner has joined #wayland
jgrulich has quit [Ping timeout: 480 seconds]
Serus has joined #wayland
Szadek has joined #wayland
Seirdy has joined #wayland
<mjt>
it definitely had become better with freerdp uwc patch
<mjt>
but it looks like I just didn't try hard enough with weston 10.0.3 to reproduce the remaining issues
<ManMower>
mjt: looks like a freerdp bug, they're using the wrong serial for pointer_set_cursor.
<mjt>
akallabeth[m]: ping? :)
<ManMower>
looks like they're updating it on mouse click instead of just on pointer enter events
<ManMower>
so as soon as you click anywhere in the rdp window you've set yourself up for broken cursor hotspots until you exit/enter the window
<ManMower>
at which point it'll work again
<ManMower>
could just try removing the seat->display->serial = serial; in pointer_handle_button() in uwac-input.c as a quick test...
<ManMower>
err, no, needs a deeper audit. they update that on keystrokes too
<ManMower>
so your cursor hotspot changes will break after a keystroke I guess.
<ManMower>
other compositors may handle this differently I guess, but weston's behaviour is correct
<mjt>
yes hotspot is off once I click any key on keyboard
<mjt>
I never tried that
<ManMower>
looks like display->serial is only used for hotspots though
<ManMower>
so just remove all setting of it that doesn't come from an enter event
<mjt>
(just had this combo - weston + wlfreerdp - freeze on me, had to kill weston logging over network - guess the weston's idle timer triggered)
<mjt>
the monitor went blank and no clicking or touching keyboard turned it back on until I pkill weston
<ManMower>
that's surprising. unless weird VM viewers are involved. vmware's removes the mouse device on display sleep, so you can never wake it with the mouse
<mjt>
it is baremetal with nothing but weston and wlfreerdp
<mjt>
run from linux tty
<ManMower>
interesting. not sure what's breaking there then.
<mjt>
and weston-terminal ;)
<ManMower>
k, freerdp hotspots seem to work for me now, with all the broken input->display->serial updates removed
<mjt>
heh. it just did it again, turning screen off :)
<ManMower>
what's your gpu?
<mjt>
Intel(R) Celeron(R) N5105 @ 2.00Ghz
<mjt>
i915
<mjt>
it's a small testing machine
eroux has quit [Remote host closed the connection]
<ManMower>
surprised to see trouble on that
<mjt>
the monitor isn't off, it is just all-black. when the idle timer triggers, it's usually turned off (dpms, whatever it is)
<mjt>
started weston with --debug, let's see..
<ManMower>
I'm not going to have time to chase that right now, but if you need a work around you can just turn off the blanker I guess. heh :(
<mjt>
I'll have to test with 11.0 first anyway
<mjt>
(hopefully debian bookworm will come with that one)
<mjt>
ManMower: thank you very much for the debugging session and finding the hotspot issue! it's been a long and bumpy ride :)
<ManMower>
np. hopefully the rest of your journey is smoother. :)
<mjt>
I'll have a bit more time once this project (which took 3 months instead of 3 days) is complete, so I'll do some debugging too, hopefully, for the rest of the issues I faced
<mjt>
lol. and the qemu machine I left running also switched to "idle state". With all the windows in BRIGHT RED COLOR (various shades of it). Once I moved mouse over it, it switched to the usual weston's [Unlock your display] dialog with green circle inside