ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
RAOF has joined #wayland
iomari891 has joined #wayland
iomari891 has quit [Ping timeout: 480 seconds]
feaneron_ has quit [Ping timeout: 480 seconds]
glennk has quit [Ping timeout: 480 seconds]
feaneron has joined #wayland
karenw has joined #wayland
mceier has quit [Ping timeout: 480 seconds]
alarumbe has quit [Read error: Connection reset by peer]
alarumbe has joined #wayland
vincejv has quit [Remote host closed the connection]
karenw has quit [Ping timeout: 480 seconds]
vincejv has joined #wayland
iomari891 has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
feaneron has quit [Quit: feaneron]
rv1sr 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]
garnacho has quit [Ping timeout: 480 seconds]
WhizzWr has quit [Quit: Bye!]
WhizzWr has joined #wayland
mceier has joined #wayland
rasterman has joined #wayland
glennk has joined #wayland
JakeSays has joined #wayland
JakeSays1 has quit [Ping timeout: 480 seconds]
tzimmermann has joined #wayland
leon-anavi has joined #wayland
Fischmie- has joined #wayland
sima has joined #wayland
garnacho has joined #wayland
mvlad has joined #wayland
immibis has joined #wayland
immibis has quit [autokilled: Host violated network policy. - Contact support@oftc.net for help. (2024-11-28 08:49:50)]
<__monty__>
Do I understand correctly that a Qt application with the XCB platform plugin should automatically run under XWayland if launched on a Wayland system?
<ofourdan>
Yes. xcb means X11, and X11 means Xwayland on a Wayland session.
iomari891 has quit [Ping timeout: 480 seconds]
<__monty__>
Hmm, might Flatpak interfere with the program being allowed to use XWayland? Or does Fedora maybe prevent the use of XWayland by default?
<Ermine>
Before we get into XY problems, what's your original issue?
<psykose>
flatpak can hide the x/wayland sockets per application yes
<psykose>
you can use flatseal to see
<__monty__>
I'm trying to package a proprietary application that is distributed as a .deb as a flatpak to run it easily on Fedora. And the flatpak seems to work on X11 systems but under Wayland it crashes with "couldn't connect to display".
<kennylevinsen>
__monty__: "couldn't connect to display" sounds like it's trying to connect to X11 specifically and failing
<psykose>
check the flatpak permissions in flatseal and it probably doesn't have the x11 socket exposed https://img.ayaya.dev/IOyA0UptX8TW
<__monty__>
When specifying the permissions I included only fallback-x11 as that is apparently the modern recommendation.
<__monty__>
Oh, and wayland. (And pulseaudio but that shouldn't affect the display manager, I hope?)
<kennylevinsen>
fallback-x11 will only give access to x11 if you're on a legacy system *not* running Wayland
<kennylevinsen>
so it requires the app itself to support and be set up to use Wayland
<kennylevinsen>
you can try to mess with QT_QPA_PLATFORM, but if the app bundles its own version of Qt it will have to have been built with Wayland support
<kennylevinsen>
otherwise you'll need to do as some other distro packages do and substitute the Qt version through some hacks
<__monty__>
It does and it only comes with the XCB plugin. I looked into compiling the qwayland qpa but the sources for 6.5.1 don't build for me.
<kennylevinsen>
(if you *purely* want the app to operate in X11 mode even on Wayland, replace both wayland and fallback-x11 with x11)
<__monty__>
I've tried relying on the Qt that comes with the Flatpak KDE runtime but I think the API has changed too much.
<__monty__>
OK, will give that a try.
kts has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
feaneron has quit [Remote host closed the connection]
<__monty__>
kennylevinsen: That seems to have worked! Thanks a ton to everyone for entertaining my inexperience : )