I am running Fedora 38 with Cinnamon and having an annoying issue where the laptop keeps waking itself up when I don’t want it to. Typically what happens is I close the lid, put the laptop in my bag, then it wakes up shortly afterwards - anything from a few seconds to a few minutes later. (I can usually tell this has happened because Cinnamon plays a chime sound when it wakes up)
Fairly often I need to carry the laptop in the bag for a 25-30 min walk, so I have made a habit of shutting it down completely when I do this - I don’t want it to wake up and then overheat itself by running in a bag with nowhere near enough airflow. This works but is inconvenient so I’d like to solve the underlying issue if possible.
A few theories I’ve had about why it might be:
- Closing the lid isn’t actually suspending for some reason - but this still happens if I select “suspend” from the Cinnamon menu beforehand
- The laptop is being shaken around excessively in the bag and something is somehow hitting the power button. It always goes in a padded laptop compartment, and in any case the issue has now occurred a few times immediately after putting it in the bag or even almost instantly while still sat on the desk, so while I’m not completely ruling this out it seems unlikely
- When I go in range of a known wireless network, it is waking in order to automatically connect to it - but I didn’t think the system was capable of this and in any case the issue still occurs if I turn off wi-fi so I don’t think that can be it
Thanks in advance for any advice on finding out what’s causing this, as I’m out of ideas for now!
Check the wall wort. Laptops will wake when you plug them in. This is triggered by external power, not the act of plugging in the cable.
This can’t be the issue - the laptop is not connected to an external power supply while in my bag, and in any case the Framework doesn’t actually appear to wake on receiving power (I’ve just checked)
I think I didn’t make this clear in my original post, but the issue is rather intermittent. It’s not like the laptop won’t stay asleep at all, it’s just that it will sometimes randomly wake itself up shortly after sleeping. As often happens with this sort of thing, as soon as I come to write a forum post about it, I can’t seem to get the issue to occur.
I’ll wait for it to happen again and then look in the systemd journal to see if I can find anything that might shed more light. At the very least that will tell me whether closing the lid is actually suspending or not.
Sleep can be tricky to diagnose. Be sure it’s not some vibration of the desk in conjunction with a sensitive touch pad waking the computer. Stranger things have happened! Another note is that some programs can interfere with sleep states. I think bittorrent clients do this quite often.
Hi @miscellanea32, welcome to the community. 
Could it be with cinnamon? have you tried switching back to gnome just to check it happens there too? And are you on latest firmware?
can we also get current journal to see if it suspends/sleeps properly?
journalctl -b 0
I’ve never had Gnome on this laptop - Fedora has an image which comes with Cinnamon out of the box so I installed that. Could try booting a live image with Gnome or something to try it, but not sure that would be representative of an actual installation?
This is what I get in the journal if I close the lid, wait for it to sleep, then wake it up again. I did this with nothing plugged in (except expansion cards, three USB-C and one USB-A) and no network connected in the hope that this would reduce the amount of unnecessary/irrelevant lines - the issue with unwanted wakes still occurs in this
Jan 12 11:29:04 framework-1 systemd-logind[1520]: Lid closed.
Jan 12 11:29:05 framework-1 systemd[2090]: Started dbus-:1.2-org.cinnamon.ScreenSaver@3.service.
Jan 12 11:29:05 framework-1 cinnamon-screensaver[13619]: CsNotificationWatcher: Could not add match rule to bus - GDBus.Error:org.freedesktop.DBus.Error.MatchRuleInvalid: Invalid match rule
Jan 12 11:29:05 framework-1 cinnamon-screensaver[13619]: Fractional scaling active: False
Jan 12 11:29:05 framework-1 cinnamon-screensaver[13619]: Trying to connect to logind...
Jan 12 11:29:05 framework-1 cinnamon-screensaver[13619]: Starting screensaver...
Jan 12 11:29:05 framework-1 cinnamon-screensaver[13619]: Cinnamon Screensaver support not found in current theme - adding some...
Jan 12 11:29:05 framework-1 cinnamon-session[2108]: WARNING: t+2309.15773s: Detected that screensaver has appeared on the bus
Jan 12 11:29:06 framework-1 cinnamon-screensaver[13619]: Successfully using logind
Jan 12 11:29:06 framework-1 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Jan 12 11:29:06 framework-1 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Jan 12 11:29:06 framework-1 systemd-logind[1520]: The system will suspend now!
Jan 12 11:29:06 framework-1 ModemManager[1632]: <info> [sleep-monitor-systemd] system is about to suspend
Jan 12 11:29:06 framework-1 NetworkManager[1687]: <info> [1705058946.2598] manager: sleep: sleep requested (sleeping: no enabled: yes)
Jan 12 11:29:06 framework-1 NetworkManager[1687]: <info> [1705058946.2604] device (wlp170s0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 12 11:29:06 framework-1 NetworkManager[1687]: <info> [1705058946.2613] device (wlp170s0): set-hw-addr: reset MAC address to [MAC address] (unmanage)
Jan 12 11:29:06 framework-1 NetworkManager[1687]: <info> [1705058946.2625] device ([MAC address]): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 12 11:29:06 framework-1 NetworkManager[1687]: <info> [1705058946.2630] device (p2p-dev-wlp170s0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 12 11:29:06 framework-1 NetworkManager[1687]: <info> [1705058946.2635] manager: NetworkManager state is now ASLEEP
Jan 12 11:29:06 framework-1 systemd[1]: Reached target sleep.target - Sleep.
Jan 12 11:29:06 framework-1 systemd[1]: Starting systemd-suspend.service - System Suspend...
Jan 12 11:29:06 framework-1 kernel: PM: suspend entry (s2idle)
Jan 12 11:29:06 framework-1 systemd-sleep[13662]: Entering sleep state 'suspend'...
Jan 12 11:29:06 framework-1 kernel: Filesystems sync: 0.018 seconds
Jan 12 11:29:27 framework-1 kernel: Freezing user space processes
Jan 12 11:29:27 framework-1 kernel: Freezing user space processes completed (elapsed 0.003 seconds)
Jan 12 11:29:27 framework-1 kernel: OOM killer disabled.
Jan 12 11:29:27 framework-1 kernel: Freezing remaining freezable tasks
Jan 12 11:29:27 framework-1 kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Jan 12 11:29:27 framework-1 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Jan 12 11:29:27 framework-1 kernel: PM: suspend devices took 0.271 seconds
Jan 12 11:29:27 framework-1 kernel: ACPI: EC: interrupt blocked
Jan 12 11:29:27 framework-1 kernel: ACPI: EC: interrupt unblocked
Jan 12 11:29:27 framework-1 kernel: i915 0000:00:02.0: [drm] GuC firmware i915/adlp_guc_70.bin version 70.5.1
Jan 12 11:29:27 framework-1 kernel: i915 0000:00:02.0: [drm] HuC firmware i915/tgl_huc.bin version 7.9.3
Jan 12 11:29:27 framework-1 kernel: i915 0000:00:02.0: [drm] HuC authenticated
Jan 12 11:29:27 framework-1 kernel: i915 0000:00:02.0: [drm] GuC submission enabled
Jan 12 11:29:27 framework-1 kernel: i915 0000:00:02.0: [drm] GuC SLPC enabled
Jan 12 11:29:27 framework-1 kernel: i915 0000:00:02.0: [drm] GuC RC: enabled
Jan 12 11:29:27 framework-1 kernel: nvme nvme0: 16/0/0 default/read/poll queues
Jan 12 11:29:27 framework-1 kernel: PM: resume devices took 0.291 seconds
Jan 12 11:29:27 framework-1 kernel: OOM killer enabled.
Jan 12 11:29:27 framework-1 kernel: Restarting tasks ...
Jan 12 11:29:27 framework-1 systemd-resolved[1454]: Clock change detected. Flushing caches.
Jan 12 11:29:27 framework-1 kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
Jan 12 11:29:27 framework-1 systemd-logind[1520]: Lid opened.
Jan 12 11:29:27 framework-1 kernel: mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915])
Jan 12 11:29:27 framework-1 kernel: done.
Jan 12 11:29:27 framework-1 kernel: random: crng reseeded on system resumption
Jan 12 11:29:27 framework-1 kernel: thermal thermal_zone13: failed to read out thermal zone (-61)
Jan 12 11:29:27 framework-1 systemd-sleep[13662]: System returned from sleep state.
Jan 12 11:29:27 framework-1 bluetoothd[1776]: Controller resume with wake event 0x0
Jan 12 11:29:27 framework-1 kernel: PM: suspend exit
Jan 12 11:29:27 framework-1 systemd[1]: systemd-suspend.service: Deactivated successfully.
Jan 12 11:29:27 framework-1 systemd[1]: Finished systemd-suspend.service - System Suspend.
Jan 12 11:29:27 framework-1 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 12 11:29:27 framework-1 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 12 11:29:27 framework-1 systemd[1]: Stopped target sleep.target - Sleep.
Jan 12 11:29:27 framework-1 systemd[1]: Reached target suspend.target - Suspend.
Jan 12 11:29:27 framework-1 systemd-logind[1520]: Operation 'sleep' finished.
Jan 12 11:29:27 framework-1 systemd[1]: Stopped target suspend.target - Suspend.
Jan 12 11:29:27 framework-1 ModemManager[1632]: <info> [sleep-monitor-systemd] system is resuming
Jan 12 11:29:27 framework-1 NetworkManager[1687]: <info> [1705058967.7161] manager: sleep: wake requested (sleeping: yes enabled: yes)
Jan 12 11:29:27 framework-1 NetworkManager[1687]: <info> [1705058967.7167] device (wlp170s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jan 12 11:29:27 framework-1 NetworkManager[1687]: <info> [1705058967.7177] device ([MAC address]): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jan 12 11:29:27 framework-1 kdeconnectd[2708]: Error sending UDP packet: QAbstractSocket::NetworkError
Jan 12 11:29:27 framework-1 NetworkManager[1687]: <info> [1705058967.7179] device (p2p-dev-wlp170s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jan 12 11:29:27 framework-1 NetworkManager[1687]: <info> [1705058967.7182] manager: NetworkManager state is now DISCONNECTED
Jan 12 11:29:27 framework-1 NetworkManager[1687]: <info> [1705058967.7184] device ([MAC address]): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Jan 12 11:29:27 framework-1 cinnamon-screensaver[13619]: Fractional scaling active: False
Jan 12 11:29:27 framework-1 audit: BPF prog-id=83 op=LOAD
Jan 12 11:29:27 framework-1 systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon...
Jan 12 11:29:27 framework-1 kernel: usb 3-9: reset full-speed USB device number 3 using xhci_hcd
Jan 12 11:29:28 framework-1 systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.
Jan 12 11:29:28 framework-1 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=fprintd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 12 11:29:28 framework-1 fprintd[13903]: libusb: error [udev_hotplug_event] ignoring udev action change
Jan 12 11:29:28 framework-1 fprintd[13903]: libusb: error [udev_hotplug_event] ignoring udev action change
Jan 12 11:29:30 framework-1 ModemManager[1632]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1d.0/0000:aa:00.0': not supported by any plugin
Do you mean the BIOS firmware? According to Framework Laptop BIOS and Driver Releases (13th Gen Intel® Core™) the factory-installed version is the latest.