I’m pretty sure the most important thing you’re missing is xorg-wayland package. Add that and give it a go again.
I think you meant xorg-xwayland I have that package already installed as well, it’s a dependency of mutter so they should already have that package installed by default when installing Gnome.
That is the package I referenced from post 15, and they don’t have it installed as per post 16.
Hmm, not sure where they got qt6-wayland package from if they’re using Gnome DE, they must’ve installed that themselves and you’re right they are missing xorg-xwayland I only was pointing out it was spelled incorrectly in your last post, so if they tried to install it, they’d have gotten an error.
Qt probably comes from a Qt application (i think it might be ProtonUp-Qt).
As per Xorg-Wayland, i have it but the copypaste omitted it for some reason.
There are the actual pacman -Q results:
egl-wayland 2:1.1.10-1
lib32-wayland 1.21.0-1
qt6-wayland 6.3.1-1
wayland 1.21.0-1
xorg-xwayland 22.1.3-1
Hmmm, well there is one solution, but it is a bit unorthodox. There is a package (I have it installed myself if that’s any consolation) called yaru-session available in the AUR. I use this in tandem with the yaru-gtk-theme, but having yaru-session installed on your system should expose that Gear icon in the login screen. To install it:
yay -S yaru-session
If it builds and there are no errors, reboot and see if the Gear icon shows up and let us know what is exposed in the Gear icon. For myself, my Gear icon shows Yaru Session and Gnome (which is on X11). Like I said, this is a bit unorthodox and you can always remove yaru-session, this is more just a way to test if the Gear icon shows up. At the very least it should expose the Gear icon with Yaru Session installed.
My only warning is do NOT log in using Yaru Session as it can be a bit buggy. Yaru Session I believe only uses X11, I don’t think Wayland support has been added for it, fyi.
I did try to install Hyprland and no gear to be seen… i’ll try with yaru session and come back to you.
Again, from my end:
How about changing kernel parameters in /etc/default/grub by adding the following parameter to the line:
GRUB_CMDLINE_LINUX_DEFAULT="<other-params> nvidia-drm.modeset=0"
Then updating grub and rebooting?
Just for a one-time try, if it doesn’t work, delete the kernel-parameter again.
Both with 1 and 0, no change.
Tried Yaru Sessions. It appears as if the gear works… but only for X11 sessions (as shown by the single “gnome” menu option")
Think it must be a driver-issue, most certainly.
Did you try any other drivers yet, like nouveau?
I didn’t try nouveau, what difference is there between nvidia propietary and nvidia-drm?
Using Nouveau isn’t a choice i have, the machine is used for gaming and nouveau vulkan isn’t out.
This is what i get from pacman -Q for nvidia:
lib32-nvidia-utils 515.65.01-1
nvidia 515.65.01-12
nvidia-hook 1.0-1
nvidia-inst 1.2-1
nvidia-installer-common 1.3-1
nvidia-installer-db 2.5.8-1
nvidia-installer-dkms 3.5-1
nvidia-settings 515.65.01-1
nvidia-utils 515.65.01-2
Forget that part, it is kernel-modesetting, we’ve already tried.
At my wit’s end here. Sorry, might be hopeless…
Found this.
Isn’t this referring to the open implementation? I’m using proprietary, never had such a problem before.
The Arch Wiki is warning against the use of proprietary ones.
With the yaru-sessions installed, did you also have done this already? ^
Yes I did, although as i already mentioned no change before and Gnome Wayland is still nowhere to be seen.
@anon11595408 so my choice is either using alpha code (by nvidia’s own admission) with worse performance or being stuck on X11? Arch baffles me at times.
Did you ever try re-installing Gnome yet?