After log out freezes when I chose to shutdown!

[asinoro]

After log out no further respond when I chose to shutdown or restart the MX it stuck and I have to power off the laptop from its button!

[aus9]

what distro please?

can you do it manually?

Code: Select all

sudo su
shutdown -h now

as root ....anythinng in /var/log/messages?

[asinoro]

It does shutdown from terminal, the problem is that it stuck-freeze at log out screen when I choose to shutdown or restart.

I have auto login activate but when I log out brings me to log in.

When I chose from there suspend and hibernate work well. When I chose shutdown or restart then there is the symbol to restart and I can not do anything because already it freezes the system.

When I do ctrl + alt + backspace then black screen with white stripe flinching on uper left corner.

Or I have to press the button to close the laptop or I have to go to console terminal with ctrl + alt + f1 to log in as root and to run the command reboot.

Code: Select all

System:    Host: asinoro Kernel: 4.2.0-0.bpo.1-amd64 x86_64 (64 bit gcc: 4.9.2)
           Desktop: Xfce 4.12.2 (Gtk 2.24.25) Distro: MX-16 amd64 Migrated
Machine:   Device: laptop System: LENOVO product: 80G0 v: Lenovo G50-30
           Mobo: LENOVO model: Lancer 5A6 v: SDK0F82993WIN UEFI: LENOVO v: A7CN40WW date: 07/18/2014
Battery    BAT0: charge: 26.8 Wh 100.0% condition: 26.8/28.5 Wh (94%) model: Lenovo status: Full
CPU:       Dual core Intel Celeron N2840 (-MCP-) cache: 1024 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 8652
           clock speeds: max: 2582 MHz 1: 2582 MHz 2: 2582 MHz
Graphics:  Card: Intel Atom Processor Z36xxx/Z37xxx Series Graphics & Display bus-ID: 00:02.0
           Display Server: X.Org 1.16.4 drivers: intel (unloaded: modesetting,fbdev,vesa)
           Resolution: 1366x768@59.97hz
           GLX Renderer: Mesa DRI Intel Bay Trail GLX Version: 3.0 Mesa 12.0.3 Direct Rendering: Yes
Audio:     Card Intel Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0
           Sound: Advanced Linux Sound Architecture v: k4.2.0-0.bpo.1-amd64
Network:   Card-1: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter driver: ath9k bus-ID: 02:00.0
           IF: wlan0 state: down mac: <filter>
           Card-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8169 v: 2.3LK-NAPI port: 1000 bus-ID: 03:00.0
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
           Card-3: Atheros usb-ID: 001-008
           IF: null-if-id state: N/A speed: N/A duplex: N/A mac: N/A
Drives:    HDD Total Size: 500.1GB (53.5% used)
           ID-1: /dev/sda model: ST500LT012 size: 500.1GB
Partition: ID-1: / size: 29G used: 21G (76%) fs: ext4 dev: /dev/sda14
           ID-2: swap-1 size: 4.19GB used: 0.67GB (16%) fs: swap dev: /dev/sda8
Sensors:   System Temperatures: cpu: 40.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 192 Uptime: 1:03 Memory: 1137.9/1888.4MB Init: SysVinit runlevel: 5 Gcc sys: 4.9.2
           Client: Shell (bash 4.3.301) inxi: 2.3.8 

Now I have the mood to solve together this problem, but I understand the new users that they don't have any passion. This forum works well and I want to help! At the end this will be good for MX!

[asinoro]

Maybe is something because of the migration?

lightdm.png

[Jerry3904]

Could you please remind us of what repos you have enabled by posting the output of this command:

Code: Select all

inxi -r

I ask because I am having trouble understanding how so many problems could suddenly arise with you and no one else.

Perhaps also the system details:

Code: Select all

inxi -Fxx

[asinoro]

inxi -F I have done before is above.

Code: Select all

$ inxi -r
Repos:     Active apt sources in file: /etc/apt/sources.list.d/antix.list
           deb http://antix.daveserver.info/jessie/ jessie main
           Active apt sources in file: /etc/apt/sources.list.d/debian-stable-updates.list
           deb http://ftp.us.debian.org/debian/ jessie-updates main contrib non-free
           Active apt sources in file: /etc/apt/sources.list.d/debian.list
           deb http://ftp.us.debian.org/debian/ jessie main contrib non-free
           deb http://security.debian.org/ jessie/updates main contrib non-free
           Active apt sources in file: /etc/apt/sources.list.d/dropbox.list
           deb http://linux.dropbox.com/debian/ jessie main
           Active apt sources in file: /etc/apt/sources.list.d/google-chrome.list
           deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
           Active apt sources in file: /etc/apt/sources.list.d/mx.list
           deb http://mxrepo.com/mx/repo/ mx15 main non-free
           Active apt sources in file: /etc/apt/sources.list.d/mx16.list
           deb http://mxrepo.com/mx/repo/ mx16 non-free main
           Active apt sources in file: /etc/apt/sources.list.d/opera-stable.list
           deb https://deb.opera.com/opera-stable/ stable non-free
           Active apt sources in file: /etc/apt/sources.list.d/vivaldi.list
           deb http://repo.vivaldi.com/stable/deb/ stable main

[Jerry3904]

Thanks--that looks OK.

[Jerry3904]

When I chose from there suspend and hibernate work well. When I chose shutdown or restart then there is the symbol to restart and I can not do anything because already it freezes the system.

We don't ship with hibernate enabled, for good reason, and the button in the upper right corner of the login screen shows it greyed out by default.

How did you activate it exactly?

Also, is there any indication in /var/log/lightdm/lightdm.log (you have to be root) of critical errors or something like that?

[asinoro]

At the virtual box the button in the upper right corner it is activated and works everything fine!

This is how activated hibernation, though at MX-15 if I remember well I could shutdown and restart from log out screen with hibernation active.

viewtopic.php?f=97&t=39543&p=402423&hil ... on#p381181

Code: Select all

cat /var/log/lightdm/lightdm.log
[+0.02s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.02s] DEBUG: Starting Light Display Manager 1.10.3, UID=0 PID=2517
[+0.02s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.02s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf
[+0.02s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/02_MX-15.conf
[+0.02s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/02_MX-16.conf
[+0.02s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/60-lightdm-gtk-greeter.conf
[+0.02s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.02s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.02s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.02s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.06s] DEBUG: Registered seat module xlocal
[+0.06s] DEBUG: Registered seat module xremote
[+0.06s] DEBUG: Registered seat module unity
[+0.06s] DEBUG: Registered seat module surfaceflinger
[+0.96s] DEBUG: Adding default seat
[+0.96s] DEBUG: Seat: Starting
[+0.96s] DEBUG: Seat: Creating user session
[+0.96s] WARNING: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
[+0.96s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+1.20s] DEBUG: User panpan added
[+1.20s] DEBUG: User user11 added
[+1.20s] DEBUG: User user12 added
[+1.28s] DEBUG: Seat: Creating display server of type x
[+1.28s] DEBUG: Could not run plymouth --ping: Failed to execute child process "plymouth" (No such file or directory)
[+1.28s] DEBUG: Using VT 7
[+1.28s] DEBUG: Seat: Starting local X display on VT 7
[+1.28s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log
[+1.28s] DEBUG: DisplayServer x-0: Writing X server authority to /var/run/lightdm/root/:0
[+1.28s] DEBUG: DisplayServer x-0: Launching X Server
[+1.28s] DEBUG: Launching process 2804: /usr/bin/X -dpi $DPI :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+1.28s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
[+1.28s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+1.28s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+4.46s] DEBUG: Got signal 10 from process 2804
[+4.46s] DEBUG: DisplayServer x-0: Got signal from X server :0
[+4.46s] DEBUG: DisplayServer x-0: Connecting to XServer :0
[+4.47s] CRITICAL: user_get_uid: assertion 'user != NULL' failed
[+4.47s] DEBUG: Launching process 2928: /usr/local/bin/early-bg
[+4.66s] DEBUG: Process 2928 exited with return value 0
[+4.66s] DEBUG: Seat: Exit status of /usr/local/bin/early-bg: 0
[+4.66s] DEBUG: Seat: Display server ready, starting session authentication
[+4.66s] DEBUG: Session pid=2935: Started with service 'lightdm-autologin', username 'panpan'
[+5.17s] DEBUG: Session pid=2935: Authentication complete with return value 0: Success
[+5.17s] DEBUG: Seat: Session authenticated, running command
[+5.17s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session0
[+5.17s] DEBUG: Session pid=2935: Running command /etc/X11/Xsession default
[+5.17s] DEBUG: Creating shared data directory /var/lib/lightdm/data/panpan
[+5.17s] DEBUG: Session pid=2935: Logging to .xsession-errors
[+5.20s] DEBUG: Activating VT 7
[+5.20s] DEBUG: Activating login1 session 1

[richb]

From the MX-15 Manual.

Do I need to create a SWAP file?
The Installer will create a SWAP file for you (see Section 2.5.1). If you intend to hibernate (and not just suspend) the system, swap may need to be something on the order of 2GB or else the hibernation will fail when the current memory use is more than 1GB. In any case, hibernate routinely fails and is therefore not supported by MX Linux.
What do names like “sda” mean?

And the same applies to MX-16.