You are not logged in.
Hello.
My freshly installed system can poweroff and reboot perfectly *if* I initiate it from command line (both from within XFCE or GNOME and from a separate tty) using
# systemctl poweroffor
systemctl rebootbut it will 100% fail to poweroff or reboot properly if I initiate the procedure using any of the graphical commands of either XFCE, GNOME, GDM and LightDM. It is always the same issue, the PC *looks* like it is starting to poweroff but then it enters a weird mode from where it can only exit by unplugging the cable from the power.
System information:
CPU: Intel i7-2600K
MB: Gigabyte Z68MA-D2H-B3 [chipset: intel Z68 express]
GPU: ASUS STRIX-GTX970 [using proprietary nvidia drivers - package 352.30-2]
Additional information (may prove useful to someone).
1. I'm using 3 monitor setup (1 on DVI, 1 on HDMI and 1 on DP), in a proper reboot/poweroff all 3 monitors enter power saving mode and then come back up. In the borked one, the display connected to the DVI port stays on (showing nothing, of course). This is the same monitor that is used as a "primary" monitor for the console tty.
2. After "finishing" the poweroff/reboot procedure, the computer starts beeping every 10 or 15 seconds or so as if it were booting from the start. But no. It just beeps.
3. The environment initiating the poweroff/reboot doesn't matter. The same results with GNOME, XFCE and GDM and LightDM.
So, does anyone know what the difference of
#systemctl poweroffand clikcing the "Shut down" button of XFCE (or GNOME) is? I'm at a loss.
Thanks!
Offline
Anything interesting in the logs or systemd's journal?
Offline
So, does anyone know what the difference of
#systemctl poweroffand clikcing the "Shut down" button of XFCE (or GNOME) is? I'm at a loss.
your usage of this "#" sign suggests that you are excuting these commands with elevated privileges.
clicking the shutdown button on the other hand is a user action (no elevated privileges).
that could be an explanation.
i had a similar problem recently; another "# pacman -Syu" solved it.
i think it was systemd's update to 224.
edit:
erm, i missed the "freshly installed".
also, i thought, you might want to find out which commands these gui options execute. maybe they are different commands.
Last edited by ondoho (2015-08-07 14:58:16)
Offline
your usage of this "#" sign suggests that you are excuting these commands with elevated privileges.
clicking the shutdown button on the other hand is a user action (no elevated privileges).
Yes, you are 100% right. But since the poweroff/reboot procedure starts, and *does* something, I didn't consider this to be a viable option. Now that I think of it again, it could be. Are there any special groups or permissions my user needs to have in order to successfully execute such an action?
also, i thought, you might want to find out which commands these gui options execute. maybe they are different commands.
Yes, that was exactly my idea, find out what command get executed. But I've no idea on how to find them!
Offline
Anything interesting in the logs or systemd's journal?
If you mean
#journalctlI did not notice anything special or weird.... Is there any other log I could look into?
Offline
...by unplugging the cable from the power.
Holding down the power button is probably safer.
Offline
yourself wrote:...by unplugging the cable from the power.
Holding down the power button is probably safer.
Heh, yes it is. ;-)
Offline