You are not logged in.
Or use xorg or just don't use gnome
--
The behavior is extremely peculiar, you're running gnome/GDM on the intel chip anyway and it's beyond me why the presence of the nvida GPU/driver should preclude that even iffff there should be any issues prime-run'ning anything later on even iff the selected session ends up being gnome on wayland. But I've also given up on trying to understand gnome or its developers.
Offline
Or use xorg or just don't use gnome
--
The behavior is extremely peculiar, you're running gnome/GDM on the intel chip anyway and it's beyond me why the presence of the nvida GPU/driver should preclude that even iffff there should be any issues prime-run'ning anything later on even iff the selected session ends up being gnome on wayland. But I've also given up on trying to understand gnome or its developers.
Well, I mainly use kde, I just check up on gnome time to time just know how it doing.
Anyways thank you for your help. I'll mark this as solved.
Last edited by Ayu2805 (2024-09-01 16:18:58)
Offline
... sorry I should've checked the current rule myself... why are they doing that now? weird but yeah gnome devs and their decisions are strange to understand.
@YCDA While I think the sentiment is a good one, just copy pasting a chatgpt response isn't really a helpful way to do it in the vast majority of cases and it's (at least to me) extremely annoying to read a post of that length that just contains nothing of relevance to the actual issue with it's only selling point being that it's politely written. And if someone where to try and take these at face value, the chance is high someones time is wasted immensely (or worse they create a worse problem by following wrong advice) by trying out suggestions that have absolutely no bearing on the issue at hand.
Last edited by V1del (2024-09-01 18:03:27)
Offline
... sorry I should've checked the current rule myself... why are they doing that now? weird but yeah gnome devs and their decisions are strange to understand.
Yeah it's fine. Either way gnome have their own set of drama.
But thanks for helping me out.
Offline
The behavior is extremely peculiar, you're running gnome/GDM on the intel chip anyway and it's beyond me why the presence of the nvida GPU/driver should preclude that even iffff there should be any issues prime-run'ning anything later on even iff the selected session ends up being gnome on wayland. But I've also given up on trying to understand gnome or its developers.
why are they doing that now? weird but yeah gnome devs and their decisions are strange to understand.
Well upon further investigation I found out that they removed that part from the udev rule in this commit. So if hopefully they don't revert it back(or disable it again) then it'll be fixed by Gnome 47.
Last edited by Ayu2805 (2024-09-02 06:19:57)
Offline
I've experienced this behavior when I installed the proprietary NVIDIA drivers for on my secondary compute card (not a display adapter).
I wish that GDM didn't try to be "smart" in this respect because it ended up creating a lot of churn in troubleshooting.
Last edited by mumei (2024-10-15 22:55:57)
Offline
I've got a similar problem with GDM on my hybrid thinkpad. Even when I enable "discrete graphics only" from the BIOS, GDM still tries to be smart and only lets me use Xorg, even with all the settings in place...
I did find a strange workaround using an old version of nvx (Note, this is not what nvx's purpose actually is):
Before(!) logging in with GDM I open a new display with Ctrl+Alt+F2
I log in, run nvx on (filling in my password when prompted) and GDM shows up again
Wayland used to be available to me now, but since GDM v46 this is not the case anymore, so continuing...
I log into GDM, which opens Gnome on Xorg
I log out of Gnome, GDM shows up
Now finally Wayland is among the options and I log in!
Wayland on Gnome now runs completely fine, literally no idea why it's disabled
Offline