ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
<bleb>
in kde I changed my cursor theme from breeze to adwaita
Company has joined #wayland
<bleb>
after rebooting, the cursor looks correct, except when it is in the shadow of the firefox window it reverts to breeze
<bleb>
I read that under wayland each application is responsible for drawing the cursor including when it's over the shadow of the window
<bleb>
so it seems like maybe firefox has cached the old cursor somewhere and it comes back even after reboot
Brainium has quit [Quit: Konversation terminated!]
Brainium has joined #wayland
<bleb>
is there a way to tell firefox to forget the cursors it drew in the past, so that it loads them properly from my current settings?
<bleb>
I don't have the problem with other applications, but I did have firefox open at some point before I changed the cursor
<bleb>
hmm so I uninstalled firefox and nuked ~/.mozilla, then reinstalled
<bleb>
and I still have the same problem!!
caveman has quit [Remote host closed the connection]
caveman has joined #wayland
Moprius has joined #wayland
Moprius has quit []
caveman has quit [Remote host closed the connection]
caveman has joined #wayland
caveman has quit [Remote host closed the connection]
caveman has joined #wayland
feaneron has joined #wayland
Brainium has quit [Quit: Konversation terminated!]
kts has joined #wayland
mxz__ has joined #wayland
mxz___ has joined #wayland
mxz has quit [Ping timeout: 480 seconds]
mxz___ is now known as mxz
mxz_ has quit [Ping timeout: 480 seconds]
leon-anavi has quit [Remote host closed the connection]
blake has joined #wayland
feaneron has quit [Ping timeout: 480 seconds]
Net147 has quit [Read error: Connection reset by peer]
Net147_ has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
kts has quit [Quit: Konversation terminated!]
tzimmermann has joined #wayland
WhizzWr has quit [Quit: Bye!]
rv1sr has joined #wayland
glennk has joined #wayland
Guest2560 has quit [Remote host closed the connection]
cool110 has joined #wayland
cool110 is now known as Guest2675
MrCooper_ is now known as MrCooper
mripard has quit [Quit: mripard]
mripard has joined #wayland
<ifreund>
bleb: Firefox uses gtk3 which is responsible for drawing the cursor
<ifreund>
you probably need to tweak some GNOME setting or something
<ifreund>
hopefully GTK will support the cursor-shape-v1 protocol eventually, which would make this much smoother
Company has quit [Quit: Leaving]
<tkna>
Hi, The music creation software Renoise does not allow clipboard copy/paste to Wayland and I am going to make that request to the author. Is it advisable to have them read this page? Is there any other appropriate documentation? https://emersion.fr/blog/2020/wayland-clipboard-drag-and-drop/
psykose has joined #wayland
rasterman has joined #wayland
azerov has quit [Quit: Gateway shutdown]
<dottedmag>
tkna: Does Renoise use any toolkits? If it does, then this blog post is counterproductive.
Eighth_Doctor has quit []
deknos82[m] has quit [Quit: Bridge terminating on SIGTERM]
akallabeth[m] has quit [Quit: Bridge terminating on SIGTERM]
daissi has quit []
YaLTeR[m] has quit [Quit: Bridge terminating on SIGTERM]
swick[m] has quit []
DemiMarie has quit [Quit: Bridge terminating on SIGTERM]
zamundaaa[m] has quit [Quit: Bridge terminating on SIGTERM]
<WhyNotHugo>
I have a toplevel which I want to move around by click-dragging on any part of it. When the user clicks, I would call xdg_toplevel::move. But it's not clear to me how to _actually_ move the toplevel once the move is taking place, nor how to _end_ the move sequence when the mouse is released.
azerov has joined #wayland
<kennylevinsen>
WhyNotHugo: when you call move, if approved the server takes over - you lose pointer focus during, and only maybe get it back afterwards when the move is done
<kennylevinsen>
How the window is moved and stuff like stopping when the button is let go is implemented in the compositor
<tkna>
dottedmag: Renoise does not use GTK, QT, etc. It should be accessing something like SDL, just like the game. But the real problem is that Renoise does not yet support Wayland and Renoise running on my sway's Xwayland cannot access the clipboard. I may need to get the X11 clipboard to work in my environment. I will investigate this a bit.
<soreau>
kennylevinsen: should you only get an enter event after moving the mouse after the move grab is finished? or should it happen immediately on grab end, and who's in charge of this behavior?
<ifreund>
llyyr: mahkoh's comments seem pretty accurate to me
<ifreund>
as I understand it, the keys arg of the enter event exists to ensure that release events sent for keys held on enter make sense
<soreau>
but you can still know which modifiers are pressed at least..
<soreau>
(on enter)
<WhyNotHugo>
kennylevinsen: ah, so when the cursor is released the move is finished by the compositor (assuming the typical desktop compositor). My client doesn't need to do anything, right?
<soreau>
WhyNotHugo: right
<soreau>
you just call move and.. that's it
<WhyNotHugo>
thanks. Nice and simple.
<WhyNotHugo>
Now I wish layer-shell have a move request too
<dottedmag>
tkna: SDL has a Wayland backend, so if enabled it probably will work just fine
<dottedmag>
My guess will be that enabling it is going to require some changes to the software, it usually is.
akallabeth[m] has joined #wayland
<kennylevinsen>
soreau: From the perspective of the spec, you just lost focus when the move started and there's no guarantee you get it back
fmuellner has joined #wayland
<soreau>
kennylevinsen: oh no ;)
<soreau>
I think if the compositor is sane enough, you can at least expect enter on mouse move after grab end
<soreau>
but it seems like the better behavior would be to send enter on button released
bluetail has joined #wayland
<bluetail>
Hello. A lot of people who switch to Wayland made implementations complain about 'floaty' or 'laggy' mouse cursor. coming from x11. How can we make sense of that, is there any truth to it?
<soreau>
bluetail: I think the best way for you to find out is to try some wayland compositors (on real hw) and see for yourself
<bluetail>
soreau the only thing I can say for sure that the FPS for some x11 based games is frequently dipping. And just this week the OpenGL backend of dolphin-emulator broke suddenly, showing invisible textures. So I use Vulkan.
<soreau>
bluetail: what changed that broke dolphin?
<bluetail>
I do >not know<. I am sorry about that.
<bluetail>
But I got a good excuse.
<dottedmag>
bluetail: I saw laggy cursor somewhere once, I think it was an app that rolled everything itself instead of using a toolkit. This is most likely a bug.
<bluetail>
I reported https://bugs.winehq.org/show_bug.cgi?id=57120 which is super important to know when using any application running from wine. If you are not on coordinates 0,0, then you won't be able to interact with the x11 wine implementation of that application.
<bluetail>
and yep, from wayland
<bluetail>
dottedmag I see. Thanks for your insights!
<soreau>
if you're using mesa drivers, you might try vblank_mode=0 so clients render as fast as possible
<soreau>
for transparent textures, is there a screenshot or issue anywhere?
<bluetail>
Sure, I will provide one
<soreau>
but I'm a bit confused.. are you saying that dolphin only breaks when using it in wayland gl mode? and x11 gl mode works?
<bluetail>
I experience the exact same behavior using a old Dolphin build just for smash bros melee, called ishiruuka
<bluetail>
Let me check if on i3 it works properly.
<soreau>
so the problem is not that it's transparent to what is behind the application
<bluetail>
Probably, I am not good at articulating
<soreau>
it's most likely a bug in dolphin emulator but maybe less likely, a bug in mesa
<bluetail>
noo
<bluetail>
it cant be a dolphin bug
<bluetail>
it used to work, and it misbehaves both on most recent and really old build
<bluetail>
let me check from i3
<soreau>
presumably you're using sway to test wayland?
feaneron has joined #wayland
<bluetail>
yea, with minimum config
<bluetail>
same behavior in i3 (x11)
<soreau>
so if you didn't upgrade dolphin and it was working but now not, it might be that upgrading mesa broke it somehow but I still think it's more likely a bug in dolphin or some config option changed in settings
<bluetail>
or corruption. But for corruption snapraid should have told me. But then it wouldn't work with Vulkan backend
<soreau>
you can also try dolphin GL on zink
<soreau>
if that makes any difference, maybe it is a driver bug
<bluetail>
headache. I used to know how to enforce zink.
<soreau>
but idk if dolphin will even run on zink, never tried it
<bluetail>
u can even force java to do that. It's translation work
<bluetail>
maybe I should try building mesa-git from outside of AUR?
<soreau>
why outside?
<bluetail>
because I need to alter PKGBUILD because it is 9 subversions older than latest commit on gitlab
<bluetail>
and I don't know what to put into pkgver...
<bluetail>
otherwise I would just put latest commit 3886a3014d5ba132f9ceced00b44b3bf0daa1ca8 into it, but I doubt that'll do
<soreau>
well you can, but I would recommend installing to a nonstandard prefix and pointing LD_LIBRARY_PATH at the relevant directory to use it
<soreau>
then you can compare easily with system mesa and git
<soreau>
and this way if git's broken, you don't bork your system mesa
<bluetail>
soreau I think you overestimate me. I probably need to google quite a bit for that :D
<soreau>
not so much, it's just changing the --prefix, really :P
gryffus has quit []
gryffus has joined #wayland
<llyyr>
ifreund: would it make sense to add text to the protocol to convey these things more clearly? I understand that there's no guarantee the keys array in the enter event may not be in the order they were pressed, so I shouldn't rely on that assumption, but it doesn't prevent someone from reading it that way and I honestly don't feel like arguing about this with people
<llyyr>
but if someone wants to argue "Wayland doesn't tell me I can't make my client put itself on fire and abort, so I will do that" then what can I do?
<kennylevinsen>
well
<soreau>
tell them they're doing it wrong? *shrug*
<kennylevinsen>
Wayland doesn't tell you that your client can't put itself on fire and abort, that's juts bad UX
<kennylevinsen>
Wayland dictates some policies and mechanisms, but there are limits to what's within our "jurisdiction"
<kennylevinsen>
I left a comment
<soreau>
yea like requiring compositors to blacken behind fullscreen surfaces in the spec, I still think this part should be removed, since a compositor can disable scanout for transparent views and render behind it just fine if it wants
paulk has quit [Read error: Connection reset by peer]
<bluetail>
what is fire and abort? Is this holding space on a button, exiting the 'proposal' with escape so that it does NOT fire the button?
kts has quit [Quit: Konversation terminated!]
bindu_ has joined #wayland
bindu has quit [Ping timeout: 480 seconds]
nysach has joined #wayland
nysach has quit [Remote host closed the connection]
Moprius has joined #wayland
Moprius has quit [Quit: bye]
nerdopolis has quit [Ping timeout: 480 seconds]
Eighth_Doctor has joined #wayland
DemiMarieObenour[m] has joined #wayland
heftig has joined #wayland
swick[m] has joined #wayland
YaLTeR[m] has joined #wayland
zamundaaa[m] has joined #wayland
<MrCooper>
bluetail: 'floaty' or 'laggy' mouse cursor is an issue of the specific compositor, the Wayland protocol doesn't say anything about how the compositor should handle cursor movement
<bluetail>
MrCooper I blame xwayland tho
<bluetail>
like I don't believe sway or KDE is the cause
<MrCooper>
Xwayland isn't involved in cursor movement in any way
<bluetail>
MrCooper thats the point
<MrCooper>
it's all compositor internal
<bluetail>
people may feel mouse being floaty when fps isn't stable enough
<bluetail>
I know games where you get frequent 7 fps dips
<bluetail>
from my side, mouse never felt any floaty / laggy. Game did in some circumstances
<MrCooper>
hmm, are you talking about the actual cursor, or something drawn by the game as part of its window?
<bluetail>
I think they refer to the cursor as it is not asynchronous to the game drawing
<bluetail>
so the game feels stuttery sometimes
<bluetail>
at least thats what I think. I could be wrong
<MrCooper>
the cursor can move independently from game drawing though
<ofourdan>
most likely a game drawn cursor, I suspect…
nerdopolis has joined #wayland
Brainium has joined #wayland
tzimmermann has quit [Ping timeout: 480 seconds]
tent405 has quit [Ping timeout: 480 seconds]
paulk-bis has quit []
paulk has joined #wayland
mripard has quit [Quit: mripard]
tzimmermann has joined #wayland
DemiMarieObenour[m] is now known as DemiMarie
<bluetail>
Keep in mind, only assumptions. MrCooper in FPS, you move your weapon with the mouse most likely. So when they talk of the cursor, they mean that the movement is disrupted. As effect,there can be a delay in the action and it being delayed / feels like missing target consecutively.
<zamundaaa[m]>
That sounds more like being used to a different acceleration curve than anything else
<MrCooper>
if you were talking about FPS games, "mouse cursor" was a bit confusing terminology
Brainium has quit [Quit: Konversation terminated!]
Brainium has joined #wayland
feaneron has quit [Ping timeout: 480 seconds]
Company has joined #wayland
<bluetail>
Maybe we should get input from the users complaining and not talk through a filter. I don't feel comfortable doing that.
<bluetail>
Theres enough people complaining [...]
tzimmermann has quit [Quit: Leaving]
Brainium has quit [Quit: Konversation terminated!]
Brainium has joined #wayland
feaneron has joined #wayland
Company has quit [Remote host closed the connection]
nysach has joined #wayland
nysach has quit [Remote host closed the connection]
rasterman has quit [Quit: Gettin' stinky!]
nysach has joined #wayland
nysach has quit [Remote host closed the connection]
Brainium has quit [Quit: Konversation terminated!]
nurupo has quit [Quit: nurupo.ga]
nurupo has joined #wayland
cyrinux has quit []
cyrinux has joined #wayland
Moprius has joined #wayland
karolherbst_ has joined #wayland
balrog_ has quit []
balrog has joined #wayland
Calandracas has quit [Remote host closed the connection]
karolherbst has quit [Ping timeout: 480 seconds]
feaneron has quit [Ping timeout: 480 seconds]
coldfeet has joined #wayland
Calandracas has joined #wayland
Moprius_ has joined #wayland
Moprius has quit [Ping timeout: 480 seconds]
riteo has quit [Remote host closed the connection]
rv1sr has quit []
Brainium has joined #wayland
karolherbst_ is now known as karolherbst
coldfeet has quit [Remote host closed the connection]
glennk has quit [Ping timeout: 480 seconds]
Moprius_ has quit [Remote host closed the connection]