Shutdown option missing after logging out and back in  [SOLVED]

Help with issues concerning notebooks, laptops and netbooks.
Post Reply
kraileth
Posts: 312
Joined: Sun Sep 04, 2016 12:30 pm
Has thanked: 0
Been thanked: 0

Shutdown option missing after logging out and back in

Post by kraileth » Tue Nov 15, 2016 6:38 am

Not sure if this has anything to do with the machine being a laptop or not... I'll post it here, anyways:

I'm using GhostBSD 10.3 MATE. If I log in the first time after a fresh boot using Slim, everything is fine. There's the option to power down the machine in the MATE menu. However if I log out and log in again, that option is missing from the menu and I have to shutdown -p now in my terminal emulator (or press the power button to trigger shutdown).

It doesn't make a difference if I log in as another user or as the same user again. The latter however can lead to the system hanging for a couple of seconds before I get the desktop back.

Here is an example of what /var/log/messages says around the time of logging back in:

Code: Select all

Nov 15 11:28:10 klappi1 kernel: error: [drm:pid0:intel_lvds_enable] *ERROR* timed out waiting for panel to power off
Nov 15 11:28:11 klappi1 kernel: error: [drm:pid0:intel_lvds_enable] *ERROR* timed out waiting for panel to power off
Nov 15 11:28:13 klappi1 kernel: error: [drm:pid5607:intel_lvds_enable] *ERROR* timed out waiting for panel to power off
Nov 15 11:28:13 klappi1 devd: check_clients:  dropping disconnected client
Nov 15 11:28:13 klappi1 kernel: error: [drm:pid5607:gen6_sanitize_pm] *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 16070000, was 16000000
Nov 15 11:28:20 klappi1 mate-session[5610]: WARNING: Unable to find provider '' of required component 'dock'
Nov 15 11:28:23 klappi1 kernel: error: [drm:pid5607:gen6_sanitize_pm] *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 16070000, was 16000000
Nov 15 11:28:46 klappi1 gnome-keyring-daemon[5632]: The PKCS#11 component was already initialized
Nov 15 11:28:47 klappi1 gnome-keyring-daemon[5632]: The Secret Service was already initialized
Nov 15 11:28:47 klappi1 gnome-keyring-daemon[5632]: The SSH agent was already initialized
Nov 15 11:29:09 klappi1 mate-session[5610]: GLib-GObject-WARNING: g_object_get_valist: object class 'UpClient' has no property named 'can-suspend'
Nov 15 11:29:09 klappi1 dbus[1049]: [system] Activating service name='org.mate.SettingsDaemon.DateTimeMechanism' (using servicehelper)
Nov 15 11:29:09 klappi1 dbus[1049]: [system] Successfully activated service 'org.mate.SettingsDaemon.DateTimeMechanism'
I guess that the GLib-GObject-WARNING line is probably hinting what's going on here. Does anybody have any idea what's happening and how to solve it (or what to try)?

ASX
Posts: 988
Joined: Wed May 06, 2015 12:46 pm
Has thanked: 0
Been thanked: 0