You are not logged in.
Pages: 1
Hi all. Straight-forward problem, hopefully with a straight-forward solution. I am running Arch with Gnome3 DE on Xorg. Whenever I go to shutdown my computer (going up to the top-right corner drop down menu, and clicking the on/off button) my system freezes for about 30-40 seconds before the menu asking me to select Cancel/Restart/Shutdown pops up. I recently did an update today on my system, including installing the newest Linux LTS. I'm not sure if that update was related to my problem. I also installed the Gnome Shell extension "caffeine" today, too.
Any ideas?
Edit: This problem doesn't seem to be present when attempting to shutdown from GDM
Edit #2: After attempting to shutdown from GDM, my problem disappeared all together... I will mark this solved if anybody has any ideas what was causing this problem.
Edit #3: The problem has returned.
Last edited by bmgxc9 (2017-02-28 21:10:38)
Arch Linux | Void Linux | Debian
GNU/Linux user since 2015.
Offline
have you tried running htop/iotop just before trying to shut down? looking in the journal?
Offline
have you tried running htop/iotop just before trying to shut down? looking in the journal?
Yes, I have used HTOP. I didn't see anything I think would cause a hang. And in any circumstance, rebooting after waiting for the panel to appear, or by holding the power button did not resolve the situation. For some reason, shutting down through GDM is what fixed the problem.
Arch Linux | Void Linux | Debian
GNU/Linux user since 2015.
Offline
is it resolved then?
if not, have you tried iotop? checked the journal?
Offline
is it resolved then?
if not, have you tried iotop? checked the journal?
-- Logs begin at Fri 2017-02-17 13:51:27 CST, end at Tue 2017-02-28 15:04:25
Feb 17 13:51:27 bmgxc9-arch systemd-journald[130]: Time spent on flushing to
Feb 17 13:51:27 bmgxc9-arch kernel: microcode: CPU0 microcode updated early
Feb 17 13:51:27 bmgxc9-arch kernel: Initializing cgroup subsys cpuset
Feb 17 13:51:27 bmgxc9-arch kernel: Initializing cgroup subsys cpu
Feb 17 13:51:27 bmgxc9-arch kernel: Initializing cgroup subsys cpuacct
Feb 17 13:51:27 bmgxc9-arch kernel: Linux version 4.4.49-1-lts (builduser@an
Feb 17 13:51:27 bmgxc9-arch kernel: Command line: BOOT_IMAGE=/vmlinuz-linux-
Feb 17 13:51:27 bmgxc9-arch kernel: x86/fpu: xstate_offset[2]: 576, xstate_
Feb 17 13:51:27 bmgxc9-arch kernel: x86/fpu: Supporting XSAVE feature 0x01:
Feb 17 13:51:27 bmgxc9-arch kernel: x86/fpu: Supporting XSAVE feature 0x02:
Feb 17 13:51:27 bmgxc9-arch kernel: x86/fpu: Supporting XSAVE feature 0x04:
Feb 17 13:51:27 bmgxc9-arch kernel: x86/fpu: Enabled xstate features 0x7, co
Feb 17 13:51:27 bmgxc9-arch kernel: x86/fpu: Using 'eager' FPU context switc
Feb 17 13:51:27 bmgxc9-arch kernel: e820: BIOS-provided physical RAM map:
That is my journalctl outpout. I thought the problem was resolved, but it has returned again.
What should be I looking for in IOTOP?
Arch Linux | Void Linux | Debian
GNU/Linux user since 2015.
Offline
I uninstalled the Caffeine gnome shell extension, and the problem went away. I am going to mark it solved, but I would really like to know if anybody has any ideas why caffeine was doing this so I can reinstall it and use it.
Arch Linux | Void Linux | Debian
GNU/Linux user since 2015.
Offline
I had this problem, too. Finally, disabling secondary graphic card fix my problem. I used
nouveau.modeset=0kernel parameter and the problem solved.
Offline
Pages: 1