Announcement

Collapse
No announcement yet.

GNOME Merge Requests Opened That Would Drop X.Org Session Support

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

  • kmansoft
    replied
    LOL I've been trying to use GNOME Wayland for a while now but there are two show stoppers for me:

    1 - Fractional scaling for XWayland is still not merged (there have been several PRs over the last 2 years or so, but...) I use a 4K monitor and run X11 apps daily, and without this feature those apps look blurry. I guess the GNOME team just doesn't consider this important.

    2 - I've got an NVIDIA GPU and Manjaro doesn't even let me enter a Wayland session. There is a Wiki for how to enable it, requires a lot of manual tweaking, which I mostly did but still missing one option somewhere (the one about preserving video memory on suspend / resume). Don't have much motivation because (1) is still a show stopper.

    Leave a comment:


  • lsatenstein
    replied
    Fedora 39 Wayland graphics support is still beta code. It is too soon to remove x11 support. Suggest a one year delay, following 3-6 months bug free Wayland use

    Leave a comment:


  • timofonic
    replied
    Originally posted by Weasel View Post
    Ok, I'm sold. The fact that it uses file permissions for this is absolutely amazing and exactly what I wanted. Finally a sanely designed display server.

    Thanks for the detailed explanation!
    You're very welcome!

    I don't get the Wayland hype, Arcan is miles better and even evolves CLI in a sane way.

    The main developer is also an old school (German?) developer with C64 and Amiga background, so he's not a newbie trying to be better than grey bearded geeks but a very experienced developer.

    But he's not a RedHat, Microsoft or Qt employee. That's "his fault"

    Their aim is make an evolved UNIX thing, dont follow thr stupid cutrent idiocracy trend of current desktop Linux.
    Last edited by timofonic; 11 October 2023, 10:33 AM.

    Leave a comment:


  • Weasel
    replied
    Originally posted by timofonic View Post
    arcan-cfgfs allows you to access and manipulate the internal state of Durden and its targets through a virtual file system. This means that you can use any file system tool or command to browse, read, write and execute files that represent Durden's configuration, menus, keybindings, targets and more.

    With arcan-cfgfs, you can also create control sockets for specific targets, which allow you to send commands and receive events from them. This can be useful for scripting, automation or remote control purposes. For example, you can create a control socket for a terminal target and send keystrokes or commands to it, or read its output. You can also create a control socket for a graphical target and send mouse or touch events to it, or capture its contents as an image file.

    To create a control socket for a target, you need to use the global/system/control/name path in the arcan-cfgfs file system, where name is the name of the socket you want to create. This will create a socket file in ARCAN_APPLTEMPBASE/durden/ipc/name, where ARCAN_APPLTEMPBASE is an environment variable that points to the temporary directory used by Arcan. The socket file can then be accessed by any tool or program that supports socket communication. The protocol used by the socket is a simple text-based format that resembles FTP commands.

    The control sockets are created with the same permissions as the user running Durden, so they are only accessible by the same user or processes with higher privileges. This means that targets from different users or contexts cannot access each other's control sockets by default, unless they have some way of elevating their permissions or bypassing the file system security. However, Durden also provides a way of sharing control sockets between different targets, by using the target/control/adopt/name path in the arcan-cfgfs file system. This will allow the current target to adopt the control socket of another target with the given name, if it exists and is allowed by Durden's configuration.

    By using arcan-cfgfs and control sockets, you can have full access to the GUI of any target running under Durden, as long as you have the appropriate permissions and know the name of the target. You can also share this access with other targets if you want to enable cross-application interaction or collaboration.​

    https://youtu.be/YWk-dmsw9Uw?si=tfsXjhsRJvKahffd&t=42
    Ok, I'm sold. The fact that it uses file permissions for this is absolutely amazing and exactly what I wanted. Finally a sanely designed display server.

    Thanks for the detailed explanation!

    Leave a comment:


  • rogerx
    replied
    Originally posted by timofonic View Post

    I agree.

    Despite what many trolls say against Wayland, they surprisingly have very valid points.

    The main reasoning behind switching from Xorg to Wayland are the massive buggy codebase with lots of legacy code.

    Those are very valid points, but feature parity and future proof should be taken seriously into consideration. Right now and after 15 years, Wayland is quite incomplete and struggling to get even feature complete implementations. Maybe others don't see it this way, but it's a total failure for me.

    Even PulseAudio finally managed to considerably improve a lot over time, despite massive design flaws it had. Now there's PipeWire and WirePlumber.

    That's why I see Arcan or it's concept the future. A common codebase, modern technologies, a proper network aware protocol and a proper evolution of CLI in the notty style. User Interface on Linux must evolve, both graphics and CLI. Despite the trend, I will always disagree and feel we are in a technological dystopia.

    Linux ecosystem needs to properly evolve, with powerful solutions and not design over thousands of obsolete layers.

    Graphics toolkits are a nightmare too, but that's another topic.
    Probably exactly what everybody else's opinion is too.

    In order for something to succeed, need/require a major or almost complete agreement within the community. The reason why all these recent projects have others revolting, due to either bugs or lack of proper coding, for one reason or another. And I'm glad too, else I would have been forced into running pulseaudio, pipewire, wayland, systemd, rust, etc... (Regardless, rust has been forcing itself in between the cracks.) None of this much upsets me... I just avoid the stuff and stick with what works, and always has just worked.

    Leave a comment:


  • jaypatelani
    replied
    Originally posted by qarium View Post

    closed source people deserve to suffer.
    Just like RHEL ones 😬

    Leave a comment:


  • oiaohm
    replied
    Originally posted by qarium View Post
    Nvidia is the most expensive brand name in the gpu world these people who can afford the punishment to buy a new AMD gpu.
    This is simple miss.

    Try to by a new system without a intel or AMD GPU you will notice you get to server/workstation CPU before that is the case. Like all AM5 cpus include APU. Same with all your current generation Intel CPUs containing igpu that are not workstation class. Yes AMD threadripper 7000.

    So the reality is most people will be able to use their computer even if the Nvidia GPU is 100 percent bricked if their system is relatively new.

    Its very important to get the AMD/Intel GPU drivers working because like it or not they have the biggest market share. With Nvidia mostly being a subset inside the AMD/Intel market share.

    Majority of distributions users not give distribution reason to bend knee to Nvidia because not having Nvidia support is not going to make users computer totally not usable. Same applies to Gnome/KDE and so on.

    Leave a comment:


  • horizonbrave
    replied
    Originally posted by Rallos Zek View Post
    Gnome and removing useful features, can one name a better iconic duo?
    You've being gifted a huge feature called "security", stop being asinine and crying

    Leave a comment:


  • horizonbrave
    replied
    Originally posted by avis View Post
    Wayland fans love to see NVIDIA users suffer.
    I don't, but I'd say fuck them, that's what they deserve.

    There was another crying not to be rich enough to afford an AMD card: they're way cheaper and it's so easy to sell the Nvidia one! We are consumer first than human being.. the only weapon left is your brain and wallet.

    Leave a comment:


  • qarium
    replied
    Originally posted by avis View Post
    This would be a great loss to Gnome, not the Luddites. Why? Wayland is mostly Linux only while Xorg is FreeBSD/OpenBSD/NetBSD/etc.
    Lastly, there's something solid behind Xorg and I tend to believe that one day people will get fed up with Wayland and introduce something saner, something more appropriate for the desktop. Xorg/X11 will most likely survive and outlive both Wayland and Gnome.
    And you don't get fans by dropping support for something with a proven track record.
    Nope, check the diff, they are dropping X11 support.
    Wayland fans love to see NVIDIA users suffer.
    closed source people deserve to suffer.

    Leave a comment:

Working...
X