ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
columbarius has joined #wayland
co1umbarius has quit [Ping timeout: 480 seconds]
guru_ has joined #wayland
guru__ has quit [Ping timeout: 480 seconds]
cwegener1 has quit [Ping timeout: 480 seconds]
fmuellner has quit [Remote host closed the connection]
cwegener has joined #wayland
sally has quit [Remote host closed the connection]
privacy has quit [Quit: Leaving]
garnacho has quit [Ping timeout: 480 seconds]
mclasen has quit [Quit: mclasen]
karolherbst_ has joined #wayland
karolherbst has quit [Ping timeout: 480 seconds]
Arnavion has quit []
Arnavion has joined #wayland
Arnavion has quit []
Arnavion has joined #wayland
cwegener has quit [Ping timeout: 480 seconds]
glennk has joined #wayland
cwegener has joined #wayland
Brainium has quit [Quit: Konversation terminated!]
mxz_ has joined #wayland
sally has joined #wayland
mxz has quit [Ping timeout: 480 seconds]
mxz__ has quit [Ping timeout: 480 seconds]
mxz_ is now known as mxz
mxz_ has joined #wayland
sima has joined #wayland
kts has joined #wayland
kts has quit [Ping timeout: 480 seconds]
sally has quit [Remote host closed the connection]
kts has joined #wayland
ity has quit [Remote host closed the connection]
ity has joined #wayland
kts_ has joined #wayland
kts has quit [Ping timeout: 480 seconds]
Guest1317 has quit [Remote host closed the connection]
cool110 has joined #wayland
cool110 is now known as Guest1372
glennk has quit [Ping timeout: 480 seconds]
sally has joined #wayland
Dami_Lu has quit [Remote host closed the connection]
Dami_Lu has joined #wayland
leon-anavi has joined #wayland
kts_ has quit [Ping timeout: 480 seconds]
f_ has joined #wayland
tzimmermann has joined #wayland
f_ has quit [Ping timeout: 480 seconds]
Dami_Lu has quit [Remote host closed the connection]
<colinmarc>
Explicit sync on nvidia is coming soon, I read somewhere. Does anyone know if the implicit-explicit-interop-via-ioctls-thing is supposed to be working already? And in particular on Vulkan? I've been trying for weeks to get it working on a 3080 in my compositor and I just get all-black dmabufs (but only above a certain size). I posted on the nvidia developer forums but the response has been bagel.
ahartmetz has joined #wayland
<MrCooper>
colinmarc: the nvidia driver doesn't handle implicit sync at all, including those ioctls
radu24284303951534727071489559 has quit []
radu24284303951534727071489559 has joined #wayland
<colinmarc>
Ok, thank you for confirming that.
<colinmarc>
I was just now reflecting on whether my issue is actually a sync issue (I don't have any flickering or anything, just... nothing) or whether that's a red herring and it's some other WSI incompatibility.
<MrCooper>
if it was a synchronization issue, the expected contents should show up eventually (and before that I'd expect to see garbage instead of all black)
<colinmarc>
I don't think so. I'm just doing the import to a VkImage and the VkImage is all black.
<colinmarc>
But it's super weird, 800x640 works every time, but 800x642 and it's all black, every time. That's true for lots of different resolutions, but there's no pattern to the stride/size I can figure out.
<cwegener>
Ah. Ok. Yeah. Sounds different.
kts_ has joined #wayland
mvlad has joined #wayland
radu24284303951534727071489559 has quit [Ping timeout: 480 seconds]
rasterman- has joined #wayland
rasterman has quit [Ping timeout: 480 seconds]
iomari892 has joined #wayland
glennk has joined #wayland
iomari891 has quit [Ping timeout: 480 seconds]
iomari891 has joined #wayland
<cwegener>
colinmarc: I think I can also reproduce your issue in jay.
<cwegener>
Turns out that the initial issue I was testing and that Julian worked around by following Xaver's approach of not sending the fence fd when the driver is NVidia is specific to OpenGL as the backend.
<cwegener>
i.e. I believe that the workaround of not sending the fence fd only works for OpenGL
<cwegener>
I just tested now with the Vulkan backend in jay ... and the screen is all black
iomari892 has quit [Ping timeout: 480 seconds]
vincejv has quit [Ping timeout: 480 seconds]
fmuellner has joined #wayland
cmichael has joined #wayland
<colinmarc>
cwegener: huh that’s reassuring to hear at least! which card are you testing on? I had a friend unable to reproduce on a p1000
<colinmarc>
I wonder if this combination (vulkan + new card + nvidia) is actually just not very commonly tested and the bug reports are getting lost in the sea of sync issues
<colinmarc>
can you also try with very low resolutions?
<Company>
swick[m], zamundaaa[m], pq: as a followup from yesterday, what we've decided to do in GTK 4.16:
<Company>
* We've special-cased the GTK background drawing now, so we can do whatever we decide on later, apps just set a ::black-background property
<Company>
* I've decided that offloading will require black-pixel support because I don't want to deal with the extra feature dimension when delaing with things, so Kwin 6.0 will have to live without GTK graphics offloading
junaid has joined #wayland
<Company>
and everything else is still private to GTK, so we can change stuff as-needed
iomari892 has joined #wayland
iomari891 has quit [Ping timeout: 480 seconds]
iomari891 has joined #wayland
tzimmermann has quit [Quit: Leaving]
iomari892 has quit [Ping timeout: 480 seconds]
glennk has joined #wayland
rv1sr has quit []
i509vcb_ has joined #wayland
f_ has quit [Ping timeout: 480 seconds]
iomari892 has joined #wayland
iomari891 has quit [Ping timeout: 480 seconds]
naemi has quit [Quit: bye]
<mclasen>
Company: my current thinking is to do another 4.14 release next weekend, and then flip to vulkan in main and do a 4.15 snapshot
naemi has joined #wayland
iomari892 has quit [Ping timeout: 480 seconds]
kts has quit [Quit: Konversation terminated!]
Narrat has joined #wayland
<Company>
mclasen: wrong channel? But sounds good to me
rv1sr has quit [Remote host closed the connection]
rv1sr has joined #wayland
jlco_ has joined #wayland
mjt has joined #wayland
jlco has quit [Ping timeout: 480 seconds]
ghishadow has joined #wayland
<mjt>
Hi! I've a laptop with small (12" wide) FullHD monitor, - that's about 160ppi (1920/12). I used cinnamon before, and everything worked fine there, - both the built-in monitor and external monitor with smaller ppi had comfort font sizes. Decided to give gnome on wayland a try, and immediately faced an issue with font sizes
<mjt>
does wayland has a notion of ppi?
<mjt>
I don't see how to find which ppi it detects/uses. At least xdpyinfo shows 96 which is obviously wrong
sergio_ has joined #wayland
<colinmarc>
Hi @mjt, wayland supports whole and fractional UI scaling (the latter only on some compositors). I'm not sure how to configure it in gnome, but there should be an option somewhere. Note that you'll have trouble with old apps that still use X11 via Xwayland (a translation layer).
<mjt>
gnome has a way to change scaling factor. But it applies to *both* monitors
<mjt>
so it is either one normal one huge, or one tiny one normal
<mjt>
(I also often use my desktop monitor with smaller ppi value)
<colinmarc>
I'd take that up with the gnome folks, as this is really a channel for discussing the protocol itself.
<mjt>
I see
<mjt>
thank you for the info anyway, the key for the start is to find out where the problem is