Announcement

Collapse
No announcement yet.

PCSX2 Emulator Disables Wayland Support By Default

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • fitzie
    replied
    Originally posted by hf_139 View Post

    GNOME is so "polished" that they had a massive security vulnerability just recently and if you look into the Fedora 39 Discourse, you see a flood of reports of GNOME 45 permanently crashing.

    In a few months, it will be a good moment to kill GNOME off and to suggest people to switch. Gnomes Wayland implementation is years behind kwin or wlroots. Plasma 6 will be the first DE with full fractional scaling (both Compositor and Applications). And both Budgie and Cosmic look promising for the people who simply don't want KDE. Hyprland is also waiting to collect a specific subset of users.
    polished for me has nothing to do with security, but that it works relatively bug free most of the time. I had a crasher on gnome 45, but instead of complaining about it on discourse, I got a stack trace and found the bug in libst and the defect in that gnome extensions that triggered (fixes are on going).

    I agree that cosmic has a lot of potential. we'll see how kde does with plasma 6. gnome is still the big daddy, I'd guess 60-80% of the desktops just based on it being the default for fedora and ubuntu.

    Leave a comment:


  • mSparks
    replied
    Originally posted by ssokolow View Post

    That's the problem. They don't obey user customizations, they can't be trusted to indicate any kind of security context information, and they don't respond to attempts to manage the window if the application gets wedged in a way that prevents the compositor from detecting it and taking over direct processing of input events.
    who do you think is the user here?
    The person using the application via a display server like x11 or wayland
    or the application developer defining CSDs?

    Leave a comment:


  • piotrj3
    replied
    Originally posted by DooMMasteR View Post
    What? the GPL enforcements where taken because NVIDIA used APIs in their closed code they should not use.
    The authors had long discussions about it but decided enforcement would be the best since then using drivers would become transparent and you could at least start debugging API interfacing issues in a proper way.
    So far, whatever shenanigans NVIDIA does on the APIs is mostly a black box, which is the opposite of the idea of using GPL code to interface your own code.

    And now NVIDIA seems to, again, not do the right thing... so the issue persists...

    Also most of the issues are completely unrelated to the DRM-API changes :-)
    There are things that should be exclusivly GPL. DMA-BUF related stuff (literal buffer to be passed around, even user mode) should never be one of them.

    Leave a comment:


  • DooMMasteR
    replied
    What? the GPL enforcements where taken because NVIDIA used APIs in their closed code they should not use.
    The authors had long discussions about it but decided enforcement would be the best since then using drivers would become transparent and you could at least start debugging API interfacing issues in a proper way.
    So far, whatever shenanigans NVIDIA does on the APIs is mostly a black box, which is the opposite of the idea of using GPL code to interface your own code.

    And now NVIDIA seems to, again, not do the right thing... so the issue persists...

    Also most of the issues are completely unrelated to the DRM-API changes :-)

    Leave a comment:


  • piotrj3
    replied
    Originally posted by DooMMasteR View Post
    All the NVIDIA workarounds are really bad, the window decoration stuff can and will be fixed, but with NVIDIA there is little hope and while some people still ride the ship that Linux should try to improve compatibility with NVIDIA's proprietary approach it becomes more and more clear that it is just a bad thing.
    Wayland without NVIDIA would simply be better.
    Even Chrome, when rendering on Wayland+VK has issues, that are mostly related to NVIDIA workarounds, and while Google has the manpower to make their own workarounds I can totally see how a smaller OSS project cannot spend the manpower on such BS.
    When Nvidia holds some responsibility, a lot of responsibility are on opensource devs as well. For example we wait forever for some community developers to agree how explicit sync is done. Stuff like DMA-BUF being GPL only was pure malicious action done against typical linux user who simply got some machine and might think "let's try linux" to only get dissappointed and never try again.

    Leave a comment:


  • piotrj3
    replied
    Originally posted by patrick1946 View Post

    SSD can't be trusted too because you can always disable them. Client side decorations are a proofen concept and the only problem now is that some frameworks like Qt do not support them well.
    Disabling is not a problem in grand scheme of things. Only program that i am aware uses such things is WINE stuff that you can set in wine config. And that is quite special case.

    There are a lot of problems with CSDs like you can crash aplication in a way that window of it can't be moved away because responsibility of decorations is inside aplication. Another is providing sensible CSD for each possible DE with each possible colors and so on. When SSD might be not as polished here, at least i am fully aware that decoration will respect dark mode, and color scheme of my DE.

    CSD can work on apple when essentially every single program in the world uses one toolkit, one enviroment, and limited design options from users.

    CSD will not work when you have Qt, GTK (hundreds of possible smaller GUIs, some of them are legacy or written for just one project), Gnome, KDE and a lot more DEs, each with own design choices and so on. Heck even if you had just KDE, making CSD good with all possible ways to configure KDE (You can make KDE look like windows 7, 10, 11, Mac OS and waaaay more) is unlikely.

    Leave a comment:


  • DooMMasteR
    replied
    All the NVIDIA workarounds are really bad, the window decoration stuff can and will be fixed, but with NVIDIA there is little hope and while some people still ride the ship that Linux should try to improve compatibility with NVIDIA's proprietary approach it becomes more and more clear that it is just a bad thing.
    Wayland without NVIDIA would simply be better.
    Even Chrome, when rendering on Wayland+VK has issues, that are mostly related to NVIDIA workarounds, and while Google has the manpower to make their own workarounds I can totally see how a smaller OSS project cannot spend the manpower on such BS.

    Leave a comment:


  • patrick1946
    replied
    Originally posted by ssokolow View Post

    That's the problem. They don't obey user customizations, they can't be trusted to indicate any kind of security context information, and they don't respond to attempts to manage the window if the application gets wedged in a way that prevents the compositor from detecting it and taking over direct processing of input events.
    SSD can't be trusted too because you can always disable them. Client side decorations are a proofen concept and the only problem now is that some frameworks like Qt do not support them well.

    Leave a comment:


  • patrick1946
    replied
    Originally posted by ssokolow View Post

    Though it fizzled out, KDE proposed the sane idea which preserves user choice, as usual, while GNOME just tried to gaslight everyone into believing that the limitations imposed by bad architectural decisions in Mutter were actually universal truths.
    KDE has a really bad idea record. I looked into this and it is simply complicated. The decoration space shouldn't be spend on a few design elements like modern UIs shows.

    Leave a comment:


  • Sonadow
    replied
    Originally posted by RedEyed View Post
    After decades to be a Linux user, I came to conclusion, that Linux Desktop is broken by design, everyone blaming everything and no one taking responsibility to make their code compatible.

    Unix philosophy is to make programs to do one thing well, but when we use Linux Desktop, we are wrongly expecting that all things are done well.
    If you want to use a proper Linux that is successful and coherent, buy a Chromebook and use ChromeOS.

    Leave a comment:

Working...
X