>GNOMEkeks have to mess with dbus just to have screensaver inhibitor on Wayland
the absolute state
/mpv/
Jaxson Green
Other urls found in this thread:
gitlab.gnome.org
twitter.com
Jayden Turner
Gnome was a mistake
Tyler Adams
GNOME is the nigger of the GNU/Linux user space
Sebastian Stewart
MATE is GNOME but actually good
Nathaniel Jones
>MATE is GNOME but I don't care
fify
Grayson Kelly
It's a Wayland problem, not a GNOME problem.
idle-inhibit is an optional Wayland protocol extension. A conforming compositor is not required to implement it.
Since mpv relies on such protocol for basic functionality, it's a nonstandard Wayland application and hence it shouldn't complain about compositors following the spec.
You might argue that Wayland itself is underspecified and underengineered, and you'd have a point. But it's not a problem with GNOME specifically.
Xavier Jones
How's it a Wayland problem when every compositor that claims to support Wayland supports that protocol with the exception of Mutter?
You can cry about not wanting to support Wayland protocols all you want, but then you don't get to claim that Mutter supports Wayland. As it stands, if you want to use Wayland on GNOME, you should just accept that you'll have a bunch of unsupported Wayland protocols.
mpv aren't obligated and shouldn't use fd portals for things that Wayland already has protocols for. GNOME users can just go use another video player.
Gavin Watson
Using the portal is the more idiomatic solution. I don't see the problem with this. Dbus is very useful like that.
Evan Harris
if only wm4 were alive, he would have slapped this the fuck down
Wyatt Rogers
>gnome users can send a simple IPC message to inhibit the screensaver
>non-gnome fags need thousands of complex hacks to do the same thing
GNOMEchads won this one.
Parker Smith
Gabriel Morgan
>muh portals
org.gnome.SessionManager.Inhibit. Let me guess. You "need" more.
Jaxson Flores
Why should I have to use that portal when idle_inhibitor works on *literally* every other wayland compositor?
Christopher Allen
That's not a portal, fucking retard.
Charles Phillips
yeah that's a gnome specific protocol, even worse
idle inhibitor works on wlroots-based compositors and KDE supports it as well, which covers just about every wayland compositor. GNOME can continue using their proprietary protocols
Luke Hall
>How's it a Wayland problem when every compositor that claims to support Wayland supports that protocol with the exception of Mutter?
The fact that some other compositors implement an optional feature does not change anything I said in the slightest.
>You can cry about not wanting to support Wayland protocols all you want, but then you don't get to claim that Mutter supports Wayland.
Retarded logic. Mutter supports all of the mandatory Wayland functionality, which is what is necessary and sufficient to be considered a compliant compositor.
>mpv aren't obligated and shouldn't use fd portals for things that Wayland already has protocols for.
mpv developers aren't forced to do anything, but they have no right to bitch about conforming Wayland compositors not implementing features that are not required to be a conforming compositor. They should just admit that they are a nonstandard Wayland application instead of crying about Wayland compositors implementing Wayland according to the spec and not however they want.
Daniel Adams
He can go and write Windows software for all I care. But he doesn't actually believe that.
Dylan Phillips
idle-inhibit is wlroots-specific (read: Sway-specific) and KDE-specific protocol, pick your poison.
None of this stuff is mandated by Wayland. If you want a standardized way to do that in Wayland, at least bark up the right tree.
Christian Evans
>mpv developers aren't forced to do anything, but they have no right to bitch about conforming Wayland compositors not implementing features that are not required to be a conforming compositor. They should just admit that they are a nonstandard Wayland application instead of crying about Wayland compositors implementing Wayland according to the spec and not however they want.
Nearly everything is a nonstandard Wayland application because virtually everyone at a minimum uses xdg-shell which is an extension and not part of the core protocol. This is part of the reason why the Wayland ecosystem is a joke.
Liam Bennett
This whole thread is proof why Wayland is a total piece of garbage and should be replaced by something new that also finally hopefully can copy with HiDPI, HDR and other modern stuff.
Really, how did such an awful protocol like Wayland even found traction? Just because it's a tiny bit less worse than X11?
Daniel Wright
*gnigger
>idle-inhibit is an optional Wayland protocol extension
every basic fucking feature is optional in wayland, because that gives wayland an excuse for nothing working correctly.