Linux Mint goes to the user login screen after opening my laptop lid, but only sometimes

[FlyingSaturn]

I used Mint with Cinnamon DE for a few months, but I had one problem or another. I fixed some of them by git-cloning the Qualcomm Atheros directories, checking the logs, or simply trying some makeshift fix from the internet (yes, turning off btrfs is a makeshift fix after one sees that "scanning btrfs systems" suddenly loads for a long time after changing the partition stuff).

It's just frustrating, and the new problem on the radar seems to be the way my hardware is triggering sudden redirects to user login screen for no reason (like, I am getting kicked out of my session). I restarted systemd-logind, checked the /var/logs/syslog file and even got something... that my laptop successfully initiated suspend the last time it threw me to the user login screen after opening the lid...

One thing to note: I haven't kept a login screen after screen lock, so idk...

Keep in mind that this happens seldom. Most of the times, I close the lid of my laptop for two days, and on the third day, I find that everything's the same as before. Better than windows, but when I close the lid, at least I trust the fact that I won't be thrown back to the login screen (something which I know from windows)...

When it does happen, it might happen even when I open the lid after a while or just after 10 seconds...

I'm simply frustrated. help me.

[FlyingSaturn]

Here's the inxi info:

System:
  Kernel: 6.11.0-19-generic arch: x86_64 bits: 64
  Desktop: Cinnamon v: 6.4.8 Distro: Linux Mint 22.1 Xia
Machine:
  Type: Laptop System: Dell product: Inspiron 5567 v: N/A
    serial: <superuser required>
  Mobo: Dell model: 06316V v: A00 serial: <superuser required> UEFI: Dell
    v: 1.5.0 date: 06/11/2021
Battery:
  ID-1: BAT0 charge: 20.3 Wh (88.3%) condition: 23.0/42.0 Wh (54.9%)
CPU:
  Info: dual core model: Intel Core i3-6006U bits: 64 type: MT MCP cache:
    L2: 512 KiB
  Speed (MHz): avg: 1700 min/max: 400/2000 cores: 1: 1700 2: 1700 3: 1700
    4: 1700
Graphics:
  Device-1: Intel Skylake GT2 [HD Graphics 520] driver: i915 v: kernel
  Device-2: Realtek Integrated Webcam driver: uvcvideo type: USB
  Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.6 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915
    resolution: 1920x1080~60Hz
  API: EGL v: 1.5 drivers: iris,swrast platforms: gbm,x11,surfaceless,device
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa
    v: 24.2.8-1ubuntu1~24.04.1 renderer: Mesa Intel HD Graphics 520 (SKL GT2)
  API: Vulkan v: 1.3.275 drivers: N/A surfaces: xcb,xlib
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio driver: snd_hda_intel
  API: ALSA v: k6.11.0-19-generic status: kernel-api
  Server-1: PipeWire v: 1.0.5 status: active
Network:
  Device-1: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter
    driver: ath10k_pci
  IF: wlp1s0 state: up mac: <filter>
  Device-2: Realtek RTL810xE PCI Express Fast Ethernet driver: r8169
  IF: enp2s0 state: down mac: <filter>
Bluetooth:
  Device-1: Qualcomm Atheros driver: btusb type: USB
  Report: hciconfig ID: hci0 rfk-id: 6 state: down
    bt-service: enabled,running rfk-block: hardware: no software: yes
    address: <filter>
Drives:
  Local Storage: total: 223.57 GiB used: 113.35 GiB (50.7%)
  ID-1: /dev/sda vendor: Western Digital model: WD Green 2.5 240GB
    size: 223.57 GiB
Partition:
  ID-1: / size: 72.2 GiB used: 36.03 GiB (49.9%) fs: ext4 dev: /dev/sda3
  ID-2: /boot/efi size: 96 MiB used: 42.9 MiB (44.7%) fs: vfat
    dev: /dev/sda1
  ID-3: /home size: 79.01 GiB used: 48.57 GiB (61.5%) fs: ext4
    dev: /dev/sda7
Swap:
  ID-1: swap-1 type: partition size: 16.36 GiB used: 108 KiB (0.0%)
    dev: /dev/sda6
Sensors:
  System Temperatures: cpu: 56.0 C pch: 52.5 C mobo: 41.0 C sodimm: SODIMM C
  Fan Speeds (rpm): cpu: 0
Info:
  Memory: total: 12 GiB available: 11.58 GiB used: 4.52 GiB (39.0%)
  Processes: 315 Uptime: 4h 54m Shell: Bash inxi: 3.3.34

[FlyingSaturn]

I just realized that it's my hardware/BIOS issue, they have issues with suspend a lot. I just checked the "Lock Screen" option in the Power Management settings under "When the lid is closed" instead of Suspend, because Windows technically did the same thing. Also, kept the "Suspend when inactive for" option to 15 minutes, because that's quite sensible.

The error is NOT from the side of Mint. Rather, Mint devs have made the "Suspend" operation so well that the laptop could be untouched for two days and it'd have the same charge. I love it guys. You guys rock.