running the stuff in the title, tried a buncha switches for chromium/electron stuff but still the load mesured with e.g. amdgpu_top doesn’t show “Media” usage. playing other stuff (VLC, Dragon, mpv) shows “Media” usage, which means those are using hardware acceleration.
edit: in the meantime tried the portable version as well, same results so it isn’t a flatpak issue.
edit 2: as @thingsiplay@lemmy.ml found, running portable and flatpak with --enable-features=AcceleratedVideoDecodeLinuxZeroCopyGL,AcceleratedVideoDecodeLinuxGL,VaapiIgnoreDriverChecks under X11/Xwayland produces hardware accelerated video. that doesn’t seem to be the case with wayland, the media graph stays at 0% and there’s a buncha dropped frames with e.g. 4K video.
Stop using flatpack for open source stuff people, i will get tagged as the anti-flatpack guy but there is 3 threads a week for stuff like this.
Flatpack solves the wrong problem for the wrong people. Stop recommending it, stop using it and spread the word.
I agree. I always try to use software from my distros repository before anything else.
Flatpaks/appimages are good for when there is no other option.
if you’d read the thread you’d see it’s not a flatpak issue. also if you spell it correctly maybe people would take you seriously.
the thread had no solution when I wrote, I assumed it was flatpak
You seem to have found a reason now, and it indeed seems to be flatpak again
And the reason is always the same, flatpak runs as intended and breaks stuff by default, people find issues, write a thread here to ask for proper flags and settings for stuff that works natively out of the box 90% of the time when installed from the native repos in serious distros.
Which brings us back to my point: it solves the wrong problem for the wrong people. Provides sandboxing and isolation for people that use it as a covenient software source unaware of its quirks.
For those aware of them it is useless because they will know enough to do the isolation and sanboxing were it matters themselves.
To be fair you did some good work understanding what was happening, so I ask you: why do you use flatpak?
brah, it is not a flatpak issue, the same happens with the portable version i.e. the one you’d get via deb/rpm/whatevers. it doesn’t accelerate video under wayland but does with xwayland; If you got a commensurate rant towards wayland, ixnay please.
as to why flatpak at all, I like my system stuff and my application stuff separate. thus my apps are all flatpak and autoupdated via systemd timer (another rant?) whereas my system stuff get updated like once a month or so as I hate rebooting.
I’m sure you found by now that your use case doesn’t match everybody else’s, so chill with the absolutes a bit.
I ain’t your brah mate.
Look, I am not that antagonistic man, no need to be this riled up. My main issue is that I lurk these threads to help people with their linux issues to help adoption, but we really have a lot of threads were flatpak is the issue, you can check the history.
I am sorry you did check to see if the native one works and reproduced the issue, I somehow understood the exact contrary, I apologize.
The next time I will ask the user to reproduce te issue with the native version before I start my rant.
My usecase is to turn on my machine in the morning, edit some text files and run a browser and some command line tools. Then i turn it off in the evening, nothing special. I got no beef with wayland and especially nothing against systemd btw.
Is there any chanche that your reboot aversion is due to wayland’s issues with session restoration?