You are not logged in.
Pages: 1
Topic closed
Hello community.
New computer, new issues. I got an HP Zbook Studio G3 and I installed Arch as far as I could. I read the wiki article about this laptop, and also how to setup the Nvidia Optimus technology with the Nvidia driver, I followed carefully the steps. My system was working perfectly, I loved!
Yesterday two things happened: update of xorg and Gnome (y use GDM and Gnome with Xorg because is recommended to use optimus) and a manual stop of pulseaudio that I performed (pulseaudio -k). Now my system is completely unresponsive, extremely slow, the mause freeze on the screen and it takes ages to enter to Gnome, which behaves in the same way. What can be happening here? I appreciate any kind of help.
python -c 'import this' | awk 'NR == 5'
Offline
Have you tried disabling Wayland? It could skip to default after updating to 3.26.
Got the same problem and that's what solved it.
Go to
/etc/gdm/custom.confand uncomment this line
WaylandEnable=falseLast edited by edskeye (2017-10-09 07:38:59)
Offline
Hey there ^_^
I ran into what sounds like the same issue after upgrading Gnome. I'm also running Arch on a laptop with Nvidia Optimus and use the Nvidia driver. I was able to get Gnome functional again by disabling the PRIME synchronization (https://wiki.archlinux.org/index.php/NV … oken_VSync). I don't know if there's a way to work around that issue. Hope that helps!
Offline
I have the exact same issue with PRIME enabled on an Optimus laptop, and like eyefox I've just switched back to Nvidia only for now.
I'd suggest, Panadestein, either going with just the Nvidia card or if you can on your laptop (I don't seem to be able to on mine), go pure Intel if battery life is a concern.
Last edited by hrkristian (2017-10-10 20:43:42)
Offline
Similar issue for me with NVIDIA Optimus and i3wm.
After the Oct 7th's GTK+ update, lightdm gtk greeter and xfce4-terminal GUI were almost unresponsive, react super slowly to mouse or keyboard input. (I didn't test other apps)
Removing nvidia-drm.modeset=1 from kernel parameters solves the problem.
I don't know if this is the same bug that causes Gnome crashing.
Offline
Have you tried disabling Wayland? It could skip to default after updating to 3.26.
Got the same problem and that's what solved it.Go to
/etc/gdm/custom.confand uncomment this line
WaylandEnable=false
This works for me, Thanks!
Offline
Offline
Pages: 1
Topic closed