Arch Linux

ducamps

Member

Registered: 2016-12-18

Posts: 35

Website

shutdown when lid close

hello all,
I have since a short time a problem with my laptop ass UX410U, when I close the lid this shutdown laptop instead suspend,
I have check the log and it's write suspend

juil. 14 15:43:47 zen-pc systemd-logind[479]: Lid closed.
juil. 14 15:43:47 zen-pc systemd-logind[479]: Suspending...
juil. 14 15:43:47 zen-pc root[18209]: LID closed
juil. 14 15:43:47 zen-pc org.gnome.Shell.desktop[719]: Window manager warning: Failed to set power save mode for output eDP-1: Permission non accordée
juil. 14 15:43:47 zen-pc gnome-shell[719]: Failed to read EDID from 'eDP-1': Aucun fichier ou dossier de ce type
juil. 14 15:43:47 zen-pc gnome-shell[719]: Screen lock is locked down, not locking
juil. 14 15:43:47 zen-pc gnome-shell[951]: Attempting to remove actor of type 'StLabel' from group of class 'ShellGenericContainer', but the container is not the actor's parent.
juil. 14 15:43:47 zen-pc gnome-shell[951]: gsignal.c:2641: instance '0x6df5570' has no handler with id '10954'
juil. 14 15:43:47 zen-pc gnome-shell[951]: gsignal.c:2641: instance '0x6df5570' has no handler with id '11197'
juil. 14 15:43:47 zen-pc gnome-shell[951]: gsignal.c:2641: instance '0x6df5570' has no handler with id '11401'
juil. 14 15:43:47 zen-pc gnome-shell[951]: gsignal.c:2641: instance '0x6df5570' has no handler with id '11737'
juil. 14 15:43:47 zen-pc gnome-shell[951]: gsignal.c:2641: instance '0x6df5570' has no handler with id '11980'
juil. 14 15:43:47 zen-pc gnome-shell[951]: gsignal.c:2641: instance '0x6df5570' has no handler with id '12184'
juil. 14 15:43:47 zen-pc gnome-shell[951]: gsignal.c:2641: instance '0x6df5570' has no handler with id '12185'
juil. 14 15:43:47 zen-pc gnome-shell[951]: gsignal.c:2641: instance '0x6df5570' has no handler with id '12186'
juil. 14 15:43:47 zen-pc gnome-shell[951]: gsignal.c:2641: instance '0x6df5570' has no handler with id '60120'
juil. 14 15:43:47 zen-pc gnome-shell[951]: gsignal.c:2641: instance '0x6df5570' has no handler with id '60363'
juil. 14 15:43:47 zen-pc gnome-shell[951]: gsignal.c:2641: instance '0x6df5570' has no handler with id '60567'
juil. 14 15:43:47 zen-pc gnome-shell[951]: gsignal.c:2641: instance '0x6df5570' has no handler with id '60903'
juil. 14 15:43:47 zen-pc gnome-shell[951]: gsignal.c:2641: instance '0x6df5570' has no handler with id '61146'
juil. 14 15:43:47 zen-pc gnome-shell[951]: gsignal.c:2641: instance '0x6df5570' has no handler with id '61350'
juil. 14 15:43:47 zen-pc gnome-shell[951]: gsignal.c:2641: instance '0x6df5570' has no handler with id '61351'
juil. 14 15:43:47 zen-pc gnome-shell[951]: gsignal.c:2641: instance '0x6df5570' has no handler with id '61352'
juil. 14 15:43:49 zen-pc systemd[1]: Reached target Sleep.
-- Subject: L'unité (unit) sleep.target a terminé son démarrage
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/l … temd-devel
--
-- L'unité (unit) sleep.target a terminé son démarrage, avec le résultat done.
juil. 14 15:43:49 zen-pc systemd[1]: Starting Suspend...
-- Subject: L'unité (unit) systemd-suspend.service a commencé à démarrer
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/l … temd-devel
--
-- L'unité (unit) systemd-suspend.service a commencé à démarrer.
juil. 14 15:43:49 zen-pc systemd-sleep[18210]: Suspending system...
-- Subject: Le système entre dans l'état de repos (sleep state) suspend
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/l … temd-devel
--
-- Le système est maintenant à l'état de repos (sleep state) suspend.

I have try to modify the login.d file and put ignore to lid switch option and it's the same thing the computer shutdown when lid close

juil. 14 18:19:40 zen-pc dbus-daemon[702]: Activating service name='ca.desrt.dconf'
juil. 14 18:19:40 zen-pc dbus-daemon[702]: Successfully activated service 'ca.desrt.dconf'
juil. 14 18:19:42 zen-pc systemd-logind[356]: Lid closed.
juil. 14 18:19:42 zen-pc root[895]: LID closed

when I push the sleep button the computer gone in sleep without problem

someone already have meet this issue or have a fix for this issue ?

thank you

ducamps

Member

Registered: 2016-12-18

Posts: 35

Website

Re: shutdown when lid close

for information when I put the laptop in sleep with the button it's work but when I close the lid the computer shutdown it's really weird

x33a

Forum Fellow

Registered: 2009-08-15

Posts: 4,587

Re: shutdown when lid close

Sounds like an issue with waking up. What happens if you manually use `systemctl suspend`?

ducamps

Member

Registered: 2016-12-18

Posts: 35

Website

Re: shutdown when lid close

systemctl suspend work correctly until I close the lid

x33a

Forum Fellow

Registered: 2009-08-15

Posts: 4,587

Re: shutdown when lid close

Alright, post your journal from the point you use the sleep button and wake it up. Also, post the journal from when you close the lid and open the lid (presumably it restarts at this point).

ducamps

Member

Registered: 2016-12-18

Posts: 35

Website

Re: shutdown when lid close

press sleep and wake up

juil. 16 09:27:09 zen-pc systemd-logind[461]: Suspend key pressed.
juil. 16 09:27:09 zen-pc root[6651]: SleepButton pressed
juil. 16 09:27:09 zen-pc root[6653]: ACPI action undefined: PNP0C0E:00
juil. 16 09:27:09 zen-pc gnome-shell[729]: Screen lock is locked down, not locking
juil. 16 09:27:09 zen-pc org.gnome.Shell.desktop[729]: Window manager warning: Failed to set power save mode for output eDP-1: Permission non accordée
juil. 16 09:27:09 zen-pc gnome-shell[970]: Attempting to remove actor of type 'StLabel' from group of class 'ShellGenericContainer', but the container is not the actor's parent.
juil. 16 09:27:09 zen-pc gnome-shell[970]: JS WARNING: [resource:///org/gnome/shell/ui/popupMenu.js 703]: reference to undefined property actor._delegate
juil. 16 09:27:12 zen-pc systemd[1]: Reached target Sleep.
juil. 16 09:27:12 zen-pc systemd[1]: Starting Suspend...
juil. 16 09:27:12 zen-pc systemd-sleep[6657]: Suspending system...
juil. 16 09:27:12 zen-pc kernel: PM: Syncing filesystems ... done.
juil. 16 09:27:12 zen-pc kernel: PM: Preparing system for sleep (mem)
juil. 16 09:27:12 zen-pc kernel: bbswitch: enabling discrete graphics
juil. 16 09:27:20 zen-pc kernel: Freezing user space processes ... (elapsed 0.003 seconds) done.
juil. 16 09:27:20 zen-pc kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
juil. 16 09:27:20 zen-pc kernel: PM: Suspending system (mem)
juil. 16 09:27:20 zen-pc kernel: Suspending console(s) (use no_console_suspend to debug)
juil. 16 09:27:20 zen-pc kernel: wlp2s0: deauthenticating from 00:19:70:34:b1:c4 by local choice (Reason: 3=DEAUTH_LEAVING)
juil. 16 09:27:20 zen-pc kernel: sd 2:0:0:0: [sdb] Synchronizing SCSI cache
juil. 16 09:27:20 zen-pc kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
juil. 16 09:27:20 zen-pc kernel: ACPI : EC: event blocked
juil. 16 09:27:20 zen-pc kernel: sd 2:0:0:0: [sdb] Stopping disk
juil. 16 09:27:20 zen-pc kernel: sd 0:0:0:0: [sda] Stopping disk
juil. 16 09:27:20 zen-pc kernel: iwlwifi 0000:02:00.0: Failed to find station
juil. 16 09:27:20 zen-pc kernel: wlp2s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)
juil. 16 09:27:20 zen-pc kernel: iwlwifi 0000:02:00.0: Failed to find station
juil. 16 09:27:20 zen-pc kernel: wlp2s0: failed to remove key (2, ff:ff:ff:ff:ff:ff) from hardware (-22)
juil. 16 09:27:20 zen-pc kernel: PM: suspend of devices complete after 929.728 msecs
juil. 16 09:27:20 zen-pc kernel: PM: late suspend of devices complete after 20.376 msecs
juil. 16 09:27:20 zen-pc kernel: ACPI : EC: interrupt blocked
juil. 16 09:27:20 zen-pc kernel: xhci_hcd 0000:00:14.0: System wakeup enabled by ACPI
juil. 16 09:27:20 zen-pc kernel: PM: noirq suspend of devices complete after 36.444 msecs
juil. 16 09:27:20 zen-pc kernel: ACPI: Preparing to enter system sleep state S3
juil. 16 09:27:20 zen-pc kernel: ACPI : EC: EC stopped
juil. 16 09:27:20 zen-pc kernel: PM: Saving platform NVS memory
juil. 16 09:27:20 zen-pc kernel: Disabling non-boot CPUs ...
juil. 16 09:27:20 zen-pc kernel: smpboot: CPU 1 is now offline
juil. 16 09:27:20 zen-pc kernel: smpboot: CPU 2 is now offline
juil. 16 09:27:20 zen-pc kernel: smpboot: CPU 3 is now offline
juil. 16 09:27:20 zen-pc kernel: ACPI: Low-level resume complete
juil. 16 09:27:20 zen-pc kernel: ACPI : EC: EC started
juil. 16 09:27:20 zen-pc kernel: PM: Restoring platform NVS memory
juil. 16 09:27:20 zen-pc kernel: Suspended for 5.256 seconds
juil. 16 09:27:20 zen-pc kernel: Enabling non-boot CPUs ...
juil. 16 09:27:20 zen-pc kernel: x86: Booting SMP configuration:
juil. 16 09:27:20 zen-pc kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
juil. 16 09:27:20 zen-pc kernel:  cache: parent cpu1 should not be sleeping
juil. 16 09:27:20 zen-pc kernel: CPU1 is up
juil. 16 09:27:20 zen-pc kernel: smpboot: Booting Node 0 Processor 2 APIC 0x1
juil. 16 09:27:20 zen-pc kernel:  cache: parent cpu2 should not be sleeping
juil. 16 09:27:20 zen-pc kernel: CPU2 is up
juil. 16 09:27:20 zen-pc kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
juil. 16 09:27:20 zen-pc kernel:  cache: parent cpu3 should not be sleeping
juil. 16 09:27:20 zen-pc kernel: CPU3 is up
juil. 16 09:27:20 zen-pc kernel: ACPI: Waking up from system sleep state S3
juil. 16 09:27:20 zen-pc kernel: acpi LNXPOWER:13: Turning OFF
juil. 16 09:27:20 zen-pc kernel: acpi LNXPOWER:12: Turning OFF
juil. 16 09:27:20 zen-pc kernel: acpi LNXPOWER:11: Turning OFF
juil. 16 09:27:20 zen-pc kernel: acpi LNXPOWER:10: Turning OFF
juil. 16 09:27:20 zen-pc kernel: acpi LNXPOWER:0f: Turning OFF
juil. 16 09:27:20 zen-pc kernel: acpi LNXPOWER:0e: Turning OFF
juil. 16 09:27:20 zen-pc kernel: acpi LNXPOWER:0d: Turning OFF
juil. 16 09:27:20 zen-pc kernel: acpi LNXPOWER:0c: Turning OFF
juil. 16 09:27:20 zen-pc kernel: acpi LNXPOWER:0b: Turning OFF
juil. 16 09:27:20 zen-pc kernel: acpi LNXPOWER:0a: Turning OFF
juil. 16 09:27:20 zen-pc kernel: acpi LNXPOWER:09: Turning OFF
juil. 16 09:27:20 zen-pc kernel: acpi LNXPOWER:08: Turning OFF
juil. 16 09:27:20 zen-pc kernel: acpi LNXPOWER:07: Turning OFF
juil. 16 09:27:20 zen-pc kernel: acpi LNXPOWER:06: Turning OFF
juil. 16 09:27:20 zen-pc kernel: acpi LNXPOWER:04: Turning OFF
juil. 16 09:27:20 zen-pc kernel: acpi LNXPOWER:03: Turning OFF
juil. 16 09:27:20 zen-pc kernel: acpi LNXPOWER:02: Turning OFF
juil. 16 09:27:20 zen-pc kernel: acpi LNXPOWER:01: Turning OFF
juil. 16 09:27:20 zen-pc kernel: acpi LNXPOWER:00: Turning OFF
juil. 16 09:27:20 zen-pc kernel: ACPI : EC: interrupt unblocked
juil. 16 09:27:20 zen-pc kernel: xhci_hcd 0000:00:14.0: System wakeup disabled by ACPI
juil. 16 09:27:20 zen-pc kernel: PM: noirq resume of devices complete after 33.938 msecs
juil. 16 09:27:20 zen-pc kernel: PM: early resume of devices complete after 16.034 msecs
juil. 16 09:27:20 zen-pc kernel: ACPI : EC: event unblocked
juil. 16 09:27:20 zen-pc kernel: usb usb1: root hub lost power or was reset
juil. 16 09:27:20 zen-pc kernel: usb usb2: root hub lost power or was reset
juil. 16 09:27:20 zen-pc kernel: sd 0:0:0:0: [sda] Starting disk
juil. 16 09:27:20 zen-pc kernel: sd 2:0:0:0: [sdb] Starting disk
juil. 16 09:27:20 zen-pc kernel: ACPI : button: The lid device is not compliant to SW_LID.
juil. 16 09:27:20 zen-pc kernel: iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
juil. 16 09:27:20 zen-pc kernel: rtc_cmos 00:01: System wakeup disabled by ACPI
juil. 16 09:27:20 zen-pc kernel: iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
juil. 16 09:27:20 zen-pc kernel: rtc_cmos 00:01: Alarms can be up to one month in the future
juil. 16 09:27:20 zen-pc kernel: [drm] GuC firmware load skipped
juil. 16 09:27:20 zen-pc kernel: iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
juil. 16 09:27:20 zen-pc kernel: iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
juil. 16 09:27:20 zen-pc kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
juil. 16 09:27:20 zen-pc kernel: ata3.00: configured for UDMA/133
juil. 16 09:27:20 zen-pc kernel: ahci 0000:00:17.0: port does not support device sleep
juil. 16 09:27:20 zen-pc kernel: usb 1-6: reset high-speed USB device number 2 using xhci_hcd
juil. 16 09:27:20 zen-pc kernel: usb 1-8: reset full-speed USB device number 3 using xhci_hcd
juil. 16 09:27:20 zen-pc kernel: PM: resume of devices complete after 940.113 msecs
juil. 16 09:27:20 zen-pc kernel: usb 1-8:1.0: rebind failed: -517
juil. 16 09:27:20 zen-pc kernel: usb 1-8:1.1: rebind failed: -517
juil. 16 09:27:20 zen-pc kernel: PM: Finishing wakeup.
juil. 16 09:27:20 zen-pc kernel: Restarting tasks ...
juil. 16 09:27:20 zen-pc kernel: [drm] RC6 on
juil. 16 09:27:20 zen-pc kernel: done.
juil. 16 09:27:20 zen-pc dhcpcd[671]: wlp2s0: carrier lost
juil. 16 09:27:20 zen-pc systemd[1]: Starting Load/Save RF Kill Switch Status...
juil. 16 09:27:20 zen-pc bluetoothd[459]: Endpoint unregistered: sender=:1.84 path=/MediaEndpoint/A2DPSource
juil. 16 09:27:20 zen-pc systemd[1]: Started Load/Save RF Kill Switch Status.
juil. 16 09:27:20 zen-pc bluetoothd[459]: Endpoint unregistered: sender=:1.84 path=/MediaEndpoint/A2DPSink
juil. 16 09:27:20 zen-pc dbus[462]: [system] Rejected send message, 1 matched rules; type="error", sender=":1.84" (uid=1000 pid=995 comm="/usr/bin/pulseaudio --daemonize=no ") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.2" (uid=0 pid=459 comm="/usr/lib/bluetooth/bluetoothd ")
juil. 16 09:27:20 zen-pc dbus[462]: [system] Rejected send message, 1 matched rules; type="error", sender=":1.84" (uid=1000 pid=995 comm="/usr/bin/pulseaudio --daemonize=no ") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.2" (uid=0 pid=459 comm="/usr/lib/bluetooth/bluetoothd ")
juil. 16 09:27:20 zen-pc dbus[462]: [system] Rejected send message, 1 matched rules; type="error", sender=":1.84" (uid=1000 pid=995 comm="/usr/bin/pulseaudio --daemonize=no ") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.2" (uid=0 pid=459 comm="/usr/lib/bluetooth/bluetoothd ")
juil. 16 09:27:20 zen-pc dbus[462]: [system] Rejected send message, 1 matched rules; type="error", sender=":1.84" (uid=1000 pid=995 comm="/usr/bin/pulseaudio --daemonize=no ") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.2" (uid=0 pid=459 comm="/usr/lib/bluetooth/bluetoothd ")
juil. 16 09:27:20 zen-pc root[6737]: ACPI action undefined: PNP0C0A:03
juil. 16 09:27:20 zen-pc systemd[1]: bluetooth.target: Unit not needed anymore. Stopping.
juil. 16 09:27:20 zen-pc systemd[1]: Stopped target Bluetooth.
juil. 16 09:27:20 zen-pc kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
juil. 16 09:27:20 zen-pc systemd[1]: Reached target Bluetooth.
juil. 16 09:27:20 zen-pc root[6744]: ACPI action undefined: ACPI0003:00
juil. 16 09:27:20 zen-pc kernel: bbswitch: disabling discrete graphics
juil. 16 09:27:20 zen-pc kernel: ACPI Warning: \_SB.PCI0.RP01.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20170119/nsarguments-95)
juil. 16 09:27:20 zen-pc kernel: Bluetooth: hci0: Device revision is 5
juil. 16 09:27:20 zen-pc kernel: Bluetooth: hci0: Secure boot is enabled
juil. 16 09:27:20 zen-pc kernel: Bluetooth: hci0: OTP lock is enabled
juil. 16 09:27:20 zen-pc kernel: Bluetooth: hci0: API lock is enabled
juil. 16 09:27:20 zen-pc kernel: Bluetooth: hci0: Debug lock is disabled
juil. 16 09:27:20 zen-pc kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014
juil. 16 09:27:20 zen-pc kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
juil. 16 09:27:20 zen-pc systemd-sleep[6657]: System resumed.
juil. 16 09:27:20 zen-pc systemd[1]: Started Suspend.
juil. 16 09:27:20 zen-pc systemd[1]: sleep.target: Unit not needed anymore. Stopping.
juil. 16 09:27:20 zen-pc systemd[1]: Stopped target Sleep.
juil. 16 09:27:20 zen-pc systemd[1]: suspend.target: Bound to unit systemd-suspend.service, but unit isn't active.
juil. 16 09:27:20 zen-pc systemd[1]: Dependency failed for Suspend.
juil. 16 09:27:20 zen-pc systemd-logind[461]: Operation 'sleep' finished.
juil. 16 09:27:20 zen-pc systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'.
juil. 16 09:27:20 zen-pc org.gnome.Shell.desktop[729]: Window manager warning: Failed to set power save mode for output eDP-1: Permission non accordée
juil. 16 09:27:20 zen-pc dhcpcd[671]: wlp2s0: deleting default route via 192.168.1.1
juil. 16 09:27:20 zen-pc dhcpcd[671]: wlp2s0: deleting route to 192.168.1.0/24
juil. 16 09:27:20 zen-pc avahi-daemon[479]: Withdrawing address record for 192.168.1.14 on wlp2s0.
juil. 16 09:27:20 zen-pc avahi-daemon[479]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.1.14.
juil. 16 09:27:20 zen-pc avahi-daemon[479]: Interface wlp2s0.IPv4 no longer relevant for mDNS.
juil. 16 09:27:21 zen-pc kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
juil. 16 09:27:21 zen-pc kernel: Bluetooth: hci0: Waiting for firmware download to complete
juil. 16 09:27:21 zen-pc kernel: Bluetooth: hci0: Firmware loaded in 1419830 usecs
juil. 16 09:27:21 zen-pc kernel: Bluetooth: hci0: Waiting for device to boot
juil. 16 09:27:21 zen-pc kernel: Bluetooth: hci0: Device booted in 10764 usecs
juil. 16 09:27:21 zen-pc kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
juil. 16 09:27:21 zen-pc kernel: Bluetooth: hci0: Applying Intel DDC parameters completed
juil. 16 09:27:21 zen-pc bluetoothd[459]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource
juil. 16 09:27:21 zen-pc bluetoothd[459]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink
juil. 16 09:27:21 zen-pc gnome-shell[970]: JS WARNING: [resource:///org/gnome/shell/gdm/util.js 331]: reference to undefined property this._preemptingService
juil. 16 09:27:21 zen-pc kernel: ata1.00: configured for UDMA/133
juil. 16 09:27:22 zen-pc ntpd[678]: Deleting interface #3 wlp2s0, 192.168.1.14#123, interface stats: received=60, sent=62, dropped=0, active_time=982 secs
juil. 16 09:27:22 zen-pc ntpd[678]: 92.222.82.98 local addr 192.168.1.14 -> <null>
juil. 16 09:27:22 zen-pc ntpd[678]: 163.172.12.49 local addr 192.168.1.14 -> <null>
juil. 16 09:27:22 zen-pc ntpd[678]: 163.172.61.210 local addr 192.168.1.14 -> <null>
juil. 16 09:27:22 zen-pc ntpd[678]: 62.210.244.146 local addr 192.168.1.14 -> <null>
juil. 16 09:27:22 zen-pc ntpd[678]: Deleting interface #5 wlp2s0, fe80::f2d5:bfff:fef4:ced7%2#123, interface stats: received=0, sent=0, dropped=0, active_time=982 secs
juil. 16 09:27:23 zen-pc kernel: wlp2s0: authenticate with 00:19:70:34:b1:c4
juil. 16 09:27:23 zen-pc kernel: wlp2s0: send auth to 00:19:70:34:b1:c4 (try 1/3)
juil. 16 09:27:23 zen-pc kernel: wlp2s0: send auth to 00:19:70:34:b1:c4 (try 2/3)
juil. 16 09:27:23 zen-pc kernel: wlp2s0: authenticated
juil. 16 09:27:23 zen-pc kernel: wlp2s0: associate with 00:19:70:34:b1:c4 (try 1/3)
juil. 16 09:27:23 zen-pc kernel: wlp2s0: RX AssocResp from 00:19:70:34:b1:c4 (capab=0x431 status=0 aid=1)
juil. 16 09:27:23 zen-pc kernel: wlp2s0: associated
juil. 16 09:27:23 zen-pc dhcpcd[671]: wlp2s0: carrier acquired
juil. 16 09:27:23 zen-pc dhcpcd[671]: wlp2s0: IAID bf:f4:ce:d7
juil. 16 09:27:24 zen-pc dhcpcd[671]: wlp2s0: rebinding lease of 192.168.1.14
juil. 16 09:27:24 zen-pc dhcpcd[671]: wlp2s0: probing address 192.168.1.14/24
juil. 16 09:27:24 zen-pc gnome-shell[970]: Could not find NVIDIA GPU model name, using general fallback.
juil. 16 09:27:24 zen-pc gnome-shell[970]: loading default theme (Adwaita)
juil. 16 09:27:24 zen-pc gnome-shell[970]: [pixel-saver]: 'appmenu' is not a valid button.
juil. 16 09:27:25 zen-pc ntpd[678]: Listen normally on 6 wlp2s0 [fe80::f2d5:bfff:fef4:ced7%2]:123
juil. 16 09:27:25 zen-pc ntpd[678]: new interface(s) found: waking up resolver
juil. 16 09:27:29 zen-pc dhcpcd[671]: wlp2s0: leased 192.168.1.14 for 86400 seconds
juil. 16 09:27:29 zen-pc avahi-daemon[479]: Joining mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.1.14.
juil. 16 09:27:29 zen-pc dhcpcd[671]: wlp2s0: adding route to 192.168.1.0/24
juil. 16 09:27:29 zen-pc dhcpcd[671]: wlp2s0: adding default route via 192.168.1.1
juil. 16 09:27:29 zen-pc avahi-daemon[479]: New relevant interface wlp2s0.IPv4 for mDNS.
juil. 16 09:27:29 zen-pc avahi-daemon[479]: Registering new address record for 192.168.1.14 on wlp2s0.IPv4.
juil. 16 09:27:29 zen-pc geoclue[791]: Failed to query location: Error resolving “location.services.mozilla.com”: Nom ou service inconnu
juil. 16 09:27:31 zen-pc ntpd[678]: Listen normally on 7 wlp2s0 192.168.1.14:123
juil. 16 09:27:31 zen-pc ntpd[678]: new interface(s) found: waking up resolver

adesh

Member

Registered: 2016-10-05

Posts: 167

Re: shutdown when lid close

Off-Topic: please use pastebin service for posting detailed logs.

ducamps

Member

Registered: 2016-12-18

Posts: 35

Website

Re: shutdown when lid close

and now when I close lid and open lid the power led stop after close lid so I think the laptop shutdown is after close lid

juil. 16 09:35:02 zen-pc systemd-logind[461]: Lid closed.
juil. 16 09:35:02 zen-pc systemd-logind[461]: Suspending...
juil. 16 09:35:02 zen-pc gnome-shell[729]: Screen lock is locked down, not locking
juil. 16 09:35:02 zen-pc root[9246]: LID closed
juil. 16 09:35:02 zen-pc gnome-shell[729]: Failed to read EDID from 'eDP-1': Aucun fichier ou dossier de ce type
juil. 16 09:35:02 zen-pc org.gnome.Shell.desktop[729]: Window manager warning: Failed to set power save mode for output eDP-1: Permission non accordée
juil. 16 09:35:02 zen-pc gnome-shell[970]: Attempting to remove actor of type 'StLabel' from group of class 'ShellGenericContainer', but the container is not the actor's parent.
juil. 16 09:35:02 zen-pc gnome-shell[970]: gsignal.c:2641: instance '0x7062170' has no handler with id '10806'
juil. 16 09:35:02 zen-pc gnome-shell[970]: gsignal.c:2641: instance '0x7062170' has no handler with id '11049'
juil. 16 09:35:02 zen-pc gnome-shell[970]: gsignal.c:2641: instance '0x7062170' has no handler with id '11253'
juil. 16 09:35:02 zen-pc gnome-shell[970]: gsignal.c:2641: instance '0x7062170' has no handler with id '11589'
juil. 16 09:35:02 zen-pc gnome-shell[970]: gsignal.c:2641: instance '0x7062170' has no handler with id '11832'
juil. 16 09:35:02 zen-pc gnome-shell[970]: gsignal.c:2641: instance '0x7062170' has no handler with id '12036'
juil. 16 09:35:02 zen-pc gnome-shell[970]: gsignal.c:2641: instance '0x7062170' has no handler with id '12037'
juil. 16 09:35:02 zen-pc gnome-shell[970]: gsignal.c:2641: instance '0x7062170' has no handler with id '12038'
juil. 16 09:35:03 zen-pc systemd[1]: Reached target Sleep.
juil. 16 09:35:03 zen-pc systemd[1]: Starting Suspend...
juil. 16 09:35:03 zen-pc systemd-sleep[9247]: Suspending system...
-- Reboot --
juil. 16 09:35:42 zen-pc kernel: Linux version 4.11.9-1-ARCH (builduser@tobias) (gcc version 7.1.1 20170621 (GCC) ) #1 SMP PREEMPT Wed Jul 5 18:23:08 CEST 2017
juil. 16 09:35:42 zen-pc kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=e7202733-4caf-4fda-adf3-bee2e80107ef rw quiet rcutree.rcu_idle_gp_delay=1
juil. 16 09:35:42 zen-pc kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
juil. 16 09:35:42 zen-pc kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
juil. 16 09:35:42 zen-pc kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
juil. 16 09:35:42 zen-pc kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
juil. 16 09:35:42 zen-pc kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
juil. 16 09:35:42 zen-pc kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
juil. 16 09:35:42 zen-pc kernel: x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
juil. 16 09:35:42 zen-pc kernel: x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
juil. 16 09:35:42 zen-pc kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format.
juil. 16 09:35:42 zen-pc kernel: e820: BIOS-provided physical RAM map:
juil. 16 09:35:42 zen-pc kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
juil. 16 09:35:42 zen-pc kernel: BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
juil. 16 09:35:42 zen-pc kernel: BIOS-e820: [mem 0x0000000000059000-0x000000000009dfff] usable
juil. 16 09:35:42 zen-pc kernel: BIOS-e820: [mem 0x000000000009e000-0x00000000000fffff] reserved
juil. 16 09:35:42 zen-pc kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000087585fff] usable
juil. 16 09:35:42 zen-pc kernel: BIOS-e820: [mem 0x0000000087586000-0x0000000087586fff] ACPI NVS
juil. 16 09:35:42 zen-pc kernel: BIOS-e820: [mem 0x0000000087587000-0x0000000087587fff] reserved
juil. 16 09:35:42 zen-pc kernel: BIOS-e820: [mem 0x0000000087588000-0x0000000089c05fff] usable
juil. 16 09:35:42 zen-pc kernel: BIOS-e820: [mem 0x0000000089c06000-0x000000008a930fff] reserved
juil. 16 09:35:42 zen-pc kernel: BIOS-e820: [mem 0x000000008a931000-0x000000008a977fff] ACPI data
juil. 16 09:35:42 zen-pc kernel: BIOS-e820: [mem 0x000000008a978000-0x000000008adb0fff] ACPI NVS
juil. 16 09:35:42 zen-pc kernel: BIOS-e820: [mem 0x000000008adb1000-0x000000008b1fffff] reserved
juil. 16 09:35:42 zen-pc kernel: BIOS-e820: [mem 0x000000008b200000-0x000000008b27efff] type 20
juil. 16 09:35:42 zen-pc kernel: BIOS-e820: [mem 0x000000008b27f000-0x000000008b2fefff] usable
juil. 16 09:35:42 zen-pc kernel: BIOS-e820: [mem 0x000000008b2ff000-0x000000008fffffff] reserved
juil. 16 09:35:42 zen-pc kernel: BIOS-e820: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved
juil. 16 09:35:42 zen-pc kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
juil. 16 09:35:42 zen-pc kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
juil. 16 09:35:42 zen-pc kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
juil. 16 09:35:42 zen-pc kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
juil. 16 09:35:42 zen-pc kernel: BIOS-e820: [mem 0x0000000100000000-0x000000026effffff] usable
juil. 16 09:35:42 zen-pc kernel: NX (Execute Disable) protection: active
juil. 16 09:35:42 zen-pc kernel: efi: EFI v2.50 by American Megatrends
juil. 16 09:35:42 zen-pc kernel: efi:  ACPI=0x8a93f000  ACPI 2.0=0x8a93f000  SMBIOS=0x8b170000  SMBIOS 3.0=0x8b16f000  ESRT=0x88930918

x33a

Forum Fellow

Registered: 2009-08-15

Posts: 4,587

Re: shutdown when lid close

Looks like when you close the lid, the steps after "systemd-sleep[pid]: Suspending system..." are not being performed. Take this as a starting point and see why it's not happening.

Also, as adesh mentioned, please use a paste site or at the very least, use code tags instead of quote tags, when posting output.

https://wiki.archlinux.org/index.php/Co … s_and_code