top 6 comments

sorted by: hot top controversial new old

Gnome makes no sense anyway, this is just another example.

  • source
  • [–] 2 points 1 year ago
    [–] 2 points 1 year ago*

    I swear, if this was 50 years go, this thread would be people talking about keeping their typewriters, dagnabbit.

  • source
  • [–] -1 points 1 year ago (3 children)

    Time to switch then. I have no interest in wayland.

  • source
  • hideshow 3 child comments
  • load more comments (1 reply)
    23 comments in c/linux@lemmy.ml view that post
    [–] 8 points 1 year ago (13 children)

    Hopefully GDM can still run X11 Desktops that's what I care the most

  • source
  • hideshow 13 child comments
  • [–] 4 points 1 year ago (12 children)

    What's stopping you from using wayland, out of interest?

  • source
  • parent
  • hideshow 12 child comments
  • [–] 2 points 1 year ago (3 children)

    I sometimes install some windows programs in lutris. With some apps, the setup.exe wizard shows as a black window. Switching to xorg allows me to run the full setup without issues.

    I also remember having issues with Nvidia/gnome and Wayland, but I haven't tried in a while and the Nvidia driver got updated a few times in the mean time.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 1 point 1 year ago (2 children)

    Huh, interesting. I have seen the black window thing before but only with electron apps, and those can be told to use in-proc GPU to get around that issue. I assume that's not the issue you had.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 1 year ago (7 children)

    to run legacy x11 apps that dont work under xwayland??
    but ik i can use a lightweight wayland compositor like labwc

  • source
  • parent
  • hideshow 7 child comments
  • [–] 2 points 1 year ago (6 children)

    I was more wondering like what apps, since I've not had trouble myself.

    Hadn't heard of labwc, will have to check it out if I run into issues, thanks.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 1 point 1 year ago (5 children)

    Yw and the only app(Ik a game but whatever) i have issues with is BeamNG (Native and proton with Vulkan renderer)

  • source
  • parent
  • hideshow 5 child comments
  • [–] 1 point 1 year ago (4 children)

    Does it actually play better native than under proton/wine? Should be a dumb question but a lot of the games I've tried that are "native" work far better when I force them to use proton than let them be native.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 1 point 1 year ago* (3 children)

    It works better on Native wth?? i used to have issues with that(on kde) but thank you for telling me to try native
    but i remember i heard Native is worse due to the oudated OpenGL/Vulkan version and its wayy buggier

  • source
  • parent
  • hideshow 3 child comments
  • [–] 1 point 1 year ago (2 children)

    Glad that's working out for you. :)

    BTW wine vanilla and some custom proton builds are adding direct wayland support, just so you know. It's still experimental but works great for some games, just in case you have others tying you to X.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 1 year ago* (last edited 1 year ago) (1 child)

    BTW wine vanilla and some custom proton builds are adding direct wayland support, just so you know. It’s still experimental but works great for some games, just in case you have others tying you to X.

    if its a Native SDL game you can force it on Wayland aswell with a launch argument " SDL_VIDEODRIVEVER=wayland" works with Source Games and BeamNG from my testing
    edit: i couldnt get it work properly with Beamng cause it doesnt follow the setting

  • source
  • parent
  • hideshow 1 child comment
  • [–] 7 points 1 year ago (8 children)

    How will they reconcile this with Ubuntu that wants 26.04 LTS to still be able to launch X11 sessions from GDM?

  • source
  • hideshow 8 child comments
  • [–] 20 points 1 year ago

    The source code is freely available and GNOME isn't beholden to Canonicals decisions. If the Ubuntu devs want to keep X11 around nobody can stop them from maintaining it themselves, or pay somebody from the GNOME team to do it for them.

  • source
  • parent
  • [–] 12 points 1 year ago (6 children)

    We went ahead and disabled the X11 session by default and from now on it needs to be explicitly enabled when building the affected modules. (gnome-session, GDM, mutter/gnome-shell).

    Aside from a simple flag change and a recompile before Canonical adds the packages to their repo, it doesn't sound like this will affect Ubuntu at all. They probably already do this anyway to add their own little patches.

    The most likely scenario is that all the X11 session code stays disabled by default for 49 with a planned removal for GNOME 50.

    GNOME 50 is when Canonical will truly need to either move to Wayland or do something else.

    Seems fairly reasonable of a timeline from the GNOME team, IMO.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 3 points 1 year ago (5 children)

    Something tells me Canonical won't just kneel to THE ALMIGHTY GNOME TEAM

  • source
  • parent
  • hideshow 5 child comments
  • [+] 0 points 1 year ago* (last edited 1 year ago) (3 children)
  • [–] 1 point 1 year ago (1 child)

    GDM launches other environments too. I do not think it is about GNOME itself.

    A big thing missing from Wayland are all the other X11 window managers (hundreds of them) and desktop environments (like XFCE and Cinnamon) that people may want to use.

  • source
  • parent
  • hideshow 1 child comment
  • load more comments (-1 replies)