System menus corrupted after sleep on 21.3

Please post suggestions for improvement of Cinnamon on:
https://github.com/linuxmint/Cinnamon
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Post Reply
VancoD
Level 1
Level 1
Posts: 4
Joined: Wed Jan 17, 2024 10:37 pm

System menus corrupted after sleep on 21.3

Post by VancoD »

New install on an older Intel-based laptop. Updated to 21.3 and now when the system comes out of sleep/hibernate the system menus / taskbars are unintelligible.

I can see in both syslog and dmesg where the laptop goes into and out of hibernation - but there's no errors or messages indicating any sort of issue relating to the driver(s) or cinnamon.

Code: Select all

System:
  Kernel: 5.15.0-91-generic x86_64 bits: 64 compiler: gcc v: 11.4.0
    Desktop: Cinnamon 6.0.4 tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0
    Distro: Linux Mint 21.3 Virginia base: Ubuntu 22.04 jammy
Machine:
  Type: Laptop System: TOSHIBA product: Qosmio X505 v: PQX33U-052025
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: TOSHIBA model: Qosmio X505 serial: <superuser required>
    BIOS: TOSHIBA v: 2.90 date: 12/10/2010
Battery:
  ID-1: BAT1 charge: 80.0 Wh (100.0%) condition: 80.0/100.0 Wh (80.0%)
    volts: 12.5 min: 12.5 model: SANYO NS2P3SZNJ5WR type: Li-ion
    serial: <filter> status: Full
Memory:
  RAM: total: 7.74 GiB used: 3.1 GiB (40.1%)
  RAM Report:
    permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: quad core model: Intel Core i7 Q 740 bits: 64 type: MT MCP
    smt: enabled arch: Nehalem rev: 5 cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
  Speed (MHz): avg: 952 high: 1022 min/max: 933/1734 boost: enabled cores:
    1: 938 2: 931 3: 931 4: 931 5: 1007 6: 931 7: 1022 8: 931 bogomips: 27663
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: NVIDIA GF106M [GeForce GTX 460M] vendor: Toshiba driver: nvidia
    v: 390.157 pcie: speed: 5 GT/s lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:0dd1
    class-ID: 0300
  Device-2: Chicony USB2.0 UVC WebCam type: USB driver: uvcvideo
    bus-ID: 2-1.1:3 chip-ID: 04f2:b130 class-ID: 0e02 serial: <filter>
  Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 118 s-size: 413x231mm (16.3x9.1")
    s-diag: 473mm (18.6")
  Monitor-1: LVDS-0 res: 1920x1080 hz: 60 dpi: 119
    size: 409x230mm (16.1x9.1") diag: 469mm (18.5")
  OpenGL: renderer: GeForce GTX 460M/PCIe/SSE2 v: 4.6.0 NVIDIA 390.157
    direct render: Yes
Audio:
  Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Toshiba
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:3b56
    class-ID: 0403
  Device-2: NVIDIA GF106 High Definition Audio vendor: Toshiba
    driver: snd_hda_intel v: kernel pcie: speed: 5 GT/s lanes: 16
    bus-ID: 01:00.1 chip-ID: 10de:0be9 class-ID: 0403
  Sound Server-1: ALSA v: k5.15.0-91-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Realtek RTL8191SEvB Wireless LAN driver: rtl8192se v: kernel
    pcie: speed: 2.5 GT/s lanes: 1 port: 4000 bus-ID: 0a:00.0
    chip-ID: 10ec:8172 class-ID: 0280
  IF: wlp10s0 state: down mac: <filter>
  Device-2: Qualcomm Atheros AR8131 Gigabit Ethernet vendor: Toshiba
    driver: atl1c v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: 5000
    bus-ID: 0b:00.0 chip-ID: 1969:1063 class-ID: 0200
  IF: enp11s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 223.57 GiB used: 41.28 GiB (18.5%)
  ID-1: /dev/sda vendor: Seagate model: ST240HM000-1G5152 size: 223.57 GiB
    speed: 3.0 Gb/s type: SSD serial: <filter> rev: C675 scheme: GPT
Partition:
  ID-1: / size: 217.55 GiB used: 41.12 GiB (18.9%) fs: ext4 dev: /dev/dm-0
    mapped: vgmint-root
  ID-2: /boot/efi size: 512 MiB used: 6.1 MiB (1.2%) fs: vfat
    dev: /dev/sda2
  ID-3: /mnt/kodi size: 7.22 TiB used: 3.83 TiB (53.1%) fs: cifs
    dev: /dev/media
Swap:
  ID-1: swap-1 type: partition size: 976 MiB used: 157 MiB (16.1%)
    priority: -2 dev: /dev/dm-1 mapped: vgmint-swap_1
Sensors:
  System Temperatures: cpu: 57.0 C mobo: N/A gpu: nvidia temp: 48 C
  Fan Speeds (RPM): N/A
Repos:
  Packages: apt: 2371
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb http://packages.linuxmint.com virginia main upstream import backport
    2: deb http://archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
    3: deb http://archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse
    4: deb http://archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
    5: deb http://security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
  Active apt repos in: /etc/apt/sources.list.d/surfshark.list
    1: deb https://ocean.surfshark.com/debian stretch main
Info:
  Processes: 296 Uptime: 1d 1h 34m wakeups: 3 Init: systemd v: 249
  runlevel: 5 Compilers: gcc: 11.4.0 alt: 11/12 Shell: Bash v: 5.1.16
  running-in: gnome-terminal inxi: 3.3.13
Reboot seems my only option as I am not familiar enough with the system controls to guess my way around trying to find whatever tool might restart the window manager.

Image
Image
Last edited by SMG on Wed Jan 17, 2024 11:19 pm, edited 1 time in total.
Reason: Added direct link to image so it shows in the post.
Top
User avatar
SMG
Level 25
Level 25
Posts: 32007
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: System menus corrupted after sleep on 21.3

Post by SMG »

VancoD wrote: ⤴Wed Jan 17, 2024 11:13 pmI can see in both syslog and dmesg where the laptop goes into and out of hibernation - but there's no errors or messages indicating any sort of issue relating to the driver(s) or cinnamon.
Hibernation is different from sleep. Hibernation is saving to disk and the computer turns off. Sleep is saving to RAM and leaving the computer running. Which are you doing?
VancoD wrote: ⤴Wed Jan 17, 2024 11:13 pmReboot seems my only option as I am not familiar enough with the system controls to guess my way around trying to find whatever tool might restart the window manager.
You can restart Cinnamon with Ctl-Alt-Escape. However, I'm not sure that will help this situation.
VancoD wrote: ⤴Wed Jan 17, 2024 11:13 pm New install on an older Intel-based laptop. Updated to 21.3 and now when the system comes out of sleep/hibernate the system menus / taskbars are unintelligible.
A new install and an upgrade are two different things. If you upgraded to LM21.3 then did you take a Timeshift snapshot of your system before doing it? What version of Linux Mint were you using prior to this?

Also, please create a new user and see if the new user has the same problem.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
Top
VancoD
Level 1
Level 1
Posts: 4
Joined: Wed Jan 17, 2024 10:37 pm

Re: System menus corrupted after sleep on 21.3

Post by VancoD »

Thanks for the reply, SMG

> Hibernation is different from sleep. Which are you doing?

I am aware hibernation is different from sleep. :D The power button option, and the logs, say "suspend" - I assumed that to mean hibernation. I assume the lid close makes the same call as the results are the same. The power indicator "pulses" - so perhaps this is, in fact, "sleep" :?:

> If you upgraded to LM21.3 then did you take a Timeshift snapshot of your system before doing it?

I did not. As it was a minor version upgrade I thought it would be fine (and truth be told if I reloaded this system from scratch it would not be the end of the world as I've done very little customization other than a CIFS mount in fstab and installing my VPN client, both easily recoverable). In fact if a fresh install is in my best interest I can easily do so.

> What version of Linux Mint were you using prior to this?

This was a dist upgrade from 21.2 to 21.3

> You can restart Cinnamon with Ctl-Alt-Escape.

On this device that had no effect.

I did a lid close and open - here's the syslog from the event. I don't see anything of note, but then I'm not 100% what an issue may actually look like.

Code: Select all

Jan 19 23:07:12 Laptuggernaut ModemManager[889]: <info>  [sleep-monitor-systemd] system is about to suspend
Jan 19 23:07:12 Laptuggernaut NetworkManager[798]: <info>  [1705723632.9428] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Jan 19 23:07:12 Laptuggernaut NetworkManager[798]: <info>  [1705723632.9429] device (enp11s0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 19 23:07:12 Laptuggernaut NetworkManager[798]: <info>  [1705723632.9813] device (p2p-dev-wlp10s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 19 23:07:12 Laptuggernaut NetworkManager[798]: <info>  [1705723632.9820] manager: NetworkManager state is now ASLEEP
Jan 19 23:07:12 Laptuggernaut NetworkManager[798]: <info>  [1705723632.9824] device (wlp10s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Jan 19 23:07:12 Laptuggernaut dbus-daemon[797]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.9' (uid=0 pid=798 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Jan 19 23:07:12 Laptuggernaut systemd[1]: Starting Network Manager Script Dispatcher Service...
Jan 19 23:07:13 Laptuggernaut dbus-daemon[797]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jan 19 23:07:13 Laptuggernaut systemd[1]: Started Network Manager Script Dispatcher Service.
Jan 19 23:07:13 Laptuggernaut kernel: [  113.666418] wlp10s0: deauthenticating from c8:a7:0a:ac:06:f4 by local choice (Reason: 3=DEAUTH_LEAVING)
Jan 19 23:07:13 Laptuggernaut wpa_supplicant[832]: wlp10s0: CTRL-EVENT-DISCONNECTED bssid=c8:a7:0a:ac:06:f4 reason=3 locally_generated=1
Jan 19 23:07:13 Laptuggernaut wpa_supplicant[832]: wlp10s0: CTRL-EVENT-DSCP-POLICY clear_all
Jan 19 23:07:13 Laptuggernaut wpa_supplicant[832]: wlp10s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Jan 19 23:07:13 Laptuggernaut NetworkManager[798]: <info>  [1705723633.2121] device (wlp10s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Jan 19 23:07:13 Laptuggernaut avahi-daemon[794]: Withdrawing address record for fe80::6aca:c66a:7391:2fbd on wlp10s0.
Jan 19 23:07:13 Laptuggernaut avahi-daemon[794]: Leaving mDNS multicast group on interface wlp10s0.IPv6 with address fe80::6aca:c66a:7391:2fbd.
Jan 19 23:07:13 Laptuggernaut NetworkManager[798]: <info>  [1705723633.2127] dhcp4 (wlp10s0): canceled DHCP transaction
Jan 19 23:07:13 Laptuggernaut avahi-daemon[794]: Interface wlp10s0.IPv6 no longer relevant for mDNS.
Jan 19 23:07:13 Laptuggernaut NetworkManager[798]: <info>  [1705723633.2128] dhcp4 (wlp10s0): activation: beginning transaction (timeout in 45 seconds)
Jan 19 23:07:13 Laptuggernaut NetworkManager[798]: <info>  [1705723633.2128] dhcp4 (wlp10s0): state changed no lease
Jan 19 23:07:13 Laptuggernaut avahi-daemon[794]: Withdrawing address record for 192.168.1.236 on wlp10s0.
Jan 19 23:07:13 Laptuggernaut avahi-daemon[794]: Leaving mDNS multicast group on interface wlp10s0.IPv4 with address 192.168.1.236.
Jan 19 23:07:13 Laptuggernaut avahi-daemon[794]: Interface wlp10s0.IPv4 no longer relevant for mDNS.
Jan 19 23:07:13 Laptuggernaut systemd-resolved[734]: wlp10s0: Bus client reset search domain list.
Jan 19 23:07:13 Laptuggernaut systemd-resolved[734]: wlp10s0: Bus client set default route setting: no
Jan 19 23:07:13 Laptuggernaut systemd-resolved[734]: wlp10s0: Bus client reset DNS server list.
Jan 19 23:07:13 Laptuggernaut NetworkManager[798]: <info>  [1705723633.2403] device (wlp10s0): supplicant interface state: completed -> disconnected
Jan 19 23:07:13 Laptuggernaut NetworkManager[798]: <info>  [1705723633.2413] device (wlp10s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 19 23:07:13 Laptuggernaut wpa_supplicant[832]: wlp10s0: CTRL-EVENT-DSCP-POLICY clear_all
Jan 19 23:07:13 Laptuggernaut systemd[1]: Reached target Sleep.
Jan 19 23:07:13 Laptuggernaut systemd[1]: Starting Record successful boot for GRUB...
Jan 19 23:07:13 Laptuggernaut systemd[1]: Starting System Suspend...
Jan 19 23:07:13 Laptuggernaut systemd-sleep[3731]: Entering sleep state 'suspend'...
Jan 19 23:07:13 Laptuggernaut kernel: [  113.958362] PM: suspend entry (deep)
Jan 19 23:07:13 Laptuggernaut systemd[1]: grub-common.service: Deactivated successfully.
Jan 19 23:07:13 Laptuggernaut systemd[1]: Finished Record successful boot for GRUB.
Jan 19 23:07:13 Laptuggernaut wpa_supplicant[832]: wlp10s0: CTRL-EVENT-DSCP-POLICY clear_all
Jan 19 23:07:13 Laptuggernaut wpa_supplicant[832]: nl80211: deinit ifname=wlp10s0 disabled_11b_rates=0
Jan 19 23:07:13 Laptuggernaut systemd[1]: Starting GRUB failed boot detection...
Jan 19 23:07:13 Laptuggernaut kernel: [  114.012553] Filesystems sync: 0.054 seconds
Jan 19 23:07:13 Laptuggernaut systemd[1]: grub-initrd-fallback.service: Deactivated successfully.
Jan 19 23:07:13 Laptuggernaut systemd[1]: Finished GRUB failed boot detection.
Jan 19 23:07:35 Laptuggernaut kernel: [  115.958904] Freezing user space processes ... (elapsed 0.002 seconds) done.
Jan 19 23:07:35 Laptuggernaut kernel: [  115.961154] OOM killer disabled.
Jan 19 23:07:35 Laptuggernaut kernel: [  115.961155] Freezing remaining freezable tasks ... (elapsed 6.638 seconds) done.
Jan 19 23:07:35 Laptuggernaut kernel: [  122.600072] printk: Suspending console(s) (use no_console_suspend to debug)
Jan 19 23:07:35 Laptuggernaut kernel: [  122.631308] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jan 19 23:07:35 Laptuggernaut kernel: [  122.632123] sd 0:0:0:0: [sda] Stopping disk
Jan 19 23:07:35 Laptuggernaut kernel: [  124.102936] ACPI: EC: interrupt blocked
Jan 19 23:07:35 Laptuggernaut kernel: [  124.124290] ACPI: PM: Preparing to enter system sleep state S3
Jan 19 23:07:35 Laptuggernaut kernel: [  124.134026] ACPI: EC: event blocked
Jan 19 23:07:35 Laptuggernaut kernel: [  124.134029] ACPI: EC: EC stopped
Jan 19 23:07:35 Laptuggernaut kernel: [  124.134031] ACPI: PM: Saving platform NVS memory
Jan 19 23:07:35 Laptuggernaut kernel: [  124.134975] Disabling non-boot CPUs ...
Jan 19 23:07:35 Laptuggernaut kernel: [  124.137538] smpboot: CPU 1 is now offline
Jan 19 23:07:35 Laptuggernaut kernel: [  124.140769] smpboot: CPU 2 is now offline
Jan 19 23:07:35 Laptuggernaut kernel: [  124.143845] smpboot: CPU 3 is now offline
Jan 19 23:07:35 Laptuggernaut kernel: [  124.147038] smpboot: CPU 4 is now offline
Jan 19 23:07:35 Laptuggernaut kernel: [  124.149818] smpboot: CPU 5 is now offline
Jan 19 23:07:35 Laptuggernaut kernel: [  124.152213] smpboot: CPU 6 is now offline
Jan 19 23:07:35 Laptuggernaut kernel: [  124.154772] smpboot: CPU 7 is now offline
Jan 19 23:07:35 Laptuggernaut kernel: [  124.157554] ACPI: PM: Low-level resume complete
Jan 19 23:07:35 Laptuggernaut kernel: [  124.157584] ACPI: EC: EC started
Jan 19 23:07:35 Laptuggernaut kernel: [  124.157585] ACPI: PM: Restoring platform NVS memory
Jan 19 23:07:35 Laptuggernaut kernel: [  124.158478] Enabling non-boot CPUs ...
Jan 19 23:07:35 Laptuggernaut kernel: [  124.158528] x86: Booting SMP configuration:
Jan 19 23:07:35 Laptuggernaut kernel: [  124.158529] smpboot: Booting Node 0 Processor 1 APIC 0x2
Jan 19 23:07:35 Laptuggernaut kernel: [  124.162198] CPU1 is up
Jan 19 23:07:35 Laptuggernaut kernel: [  124.162238] smpboot: Booting Node 0 Processor 2 APIC 0x4
Jan 19 23:07:35 Laptuggernaut kernel: [  124.165936] CPU2 is up
Jan 19 23:07:35 Laptuggernaut kernel: [  124.165974] smpboot: Booting Node 0 Processor 3 APIC 0x6
Jan 19 23:07:35 Laptuggernaut kernel: [  124.169711] CPU3 is up
Jan 19 23:07:35 Laptuggernaut kernel: [  124.169756] smpboot: Booting Node 0 Processor 4 APIC 0x1
Jan 19 23:07:35 Laptuggernaut kernel: [  124.173076] CPU4 is up
Jan 19 23:07:35 Laptuggernaut kernel: [  124.173114] smpboot: Booting Node 0 Processor 5 APIC 0x3
Jan 19 23:07:35 Laptuggernaut kernel: [  124.176386] CPU5 is up
Jan 19 23:07:35 Laptuggernaut kernel: [  124.176425] smpboot: Booting Node 0 Processor 6 APIC 0x5
Jan 19 23:07:35 Laptuggernaut kernel: [  124.179782] CPU6 is up
Jan 19 23:07:35 Laptuggernaut kernel: [  124.179826] smpboot: Booting Node 0 Processor 7 APIC 0x7
Jan 19 23:07:35 Laptuggernaut kernel: [  124.183244] CPU7 is up
Jan 19 23:07:35 Laptuggernaut kernel: [  124.189864] ACPI: PM: Waking up from system sleep state S3
Jan 19 23:07:35 Laptuggernaut kernel: [  124.191392] ACPI: EC: interrupt unblocked
Jan 19 23:07:35 Laptuggernaut kernel: [  124.214218] ACPI: EC: event unblocked
Jan 19 23:07:35 Laptuggernaut kernel: [  124.215141] sd 0:0:0:0: [sda] Starting disk
Jan 19 23:07:35 Laptuggernaut kernel: [  124.509822] usb 2-1.3: reset full-speed USB device number 4 using ehci-pci
Jan 19 23:07:35 Laptuggernaut kernel: [  124.564926] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Jan 19 23:07:35 Laptuggernaut kernel: [  124.565349] ata4: SATA link down (SStatus 0 SControl 300)
Jan 19 23:07:35 Laptuggernaut kernel: [  124.565485] ata6: SATA link down (SStatus 0 SControl 300)
Jan 19 23:07:35 Laptuggernaut kernel: [  124.565978] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jan 19 23:07:35 Laptuggernaut kernel: [  124.567004] ata1.00: configured for UDMA/133
Jan 19 23:07:35 Laptuggernaut kernel: [  124.569821] ata5.00: configured for UDMA/100
Jan 19 23:07:35 Laptuggernaut kernel: [  124.701895] usb 2-1.1: reset high-speed USB device number 3 using ehci-pci
Jan 19 23:07:35 Laptuggernaut kernel: [  124.801908] firewire_core 0000:07:00.0: rediscovered device fw0
Jan 19 23:07:35 Laptuggernaut kernel: [  124.836384] OOM killer enabled.
Jan 19 23:07:35 Laptuggernaut kernel: [  124.836386] Restarting tasks ... 
Jan 19 23:07:35 Laptuggernaut kernel: [  124.840725] pci_bus 0000:02: Allocating resources
Jan 19 23:07:35 Laptuggernaut kernel: [  124.840758] pci_bus 0000:07: Allocating resources
Jan 19 23:07:35 Laptuggernaut kernel: [  124.840814] pci_bus 0000:0a: Allocating resources
Jan 19 23:07:35 Laptuggernaut kernel: [  124.840859] pci_bus 0000:0b: Allocating resources
Jan 19 23:07:35 Laptuggernaut kernel: [  124.840897] pci 0000:00:1e.0: PCI bridge to [bus 0c]
Jan 19 23:07:35 Laptuggernaut kernel: [  124.841089] pcieport 0000:00:1c.3: PCI bridge to [bus 07]
Jan 19 23:07:35 Laptuggernaut kernel: [  124.841105] pcieport 0000:00:1c.3:   bridge window [io  0x6000-0x6fff]
Jan 19 23:07:35 Laptuggernaut kernel: [  124.841124] pcieport 0000:00:1c.3:   bridge window [mem 0xf0500000-0xf05fffff]
Jan 19 23:07:35 Laptuggernaut kernel: [  124.841140] pcieport 0000:00:1c.3:   bridge window [mem 0xc0100000-0xc02fffff 64bit pref]
Jan 19 23:07:35 Laptuggernaut kernel: [  124.841246] pcieport 0000:00:1c.4: PCI bridge to [bus 0a]
Jan 19 23:07:35 Laptuggernaut kernel: [  124.841258] pcieport 0000:00:1c.4:   bridge window [io  0x4000-0x4fff]
Jan 19 23:07:35 Laptuggernaut kernel: [  124.841275] pcieport 0000:00:1c.4:   bridge window [mem 0xf0600000-0xf06fffff]
Jan 19 23:07:35 Laptuggernaut kernel: [  124.841290] pcieport 0000:00:1c.4:   bridge window [mem 0xc0300000-0xc04fffff 64bit pref]
Jan 19 23:07:35 Laptuggernaut kernel: [  124.844899] done.
Jan 19 23:07:35 Laptuggernaut systemd-resolved[734]: Clock change detected. Flushing caches.
Jan 19 23:07:35 Laptuggernaut zed[834]: Exiting
Jan 19 23:07:35 Laptuggernaut bluetoothd[796]: Endpoint unregistered: sender=:1.37 path=/MediaEndpoint/A2DPSource/ldac_hq
Jan 19 23:07:35 Laptuggernaut bluetoothd[796]: Endpoint unregistered: sender=:1.37 path=/MediaEndpoint/A2DPSource/ldac_sq
Jan 19 23:07:35 Laptuggernaut surfsharkd.js[1140]: JS LOG: Error: Parsing Error: Invalid arguments: 
Jan 19 23:07:35 Laptuggernaut rtkit-daemon[1148]: The canary thread is apparently starving. Taking action.
Jan 19 23:07:35 Laptuggernaut systemd[1]: zfs-zed.service: Deactivated successfully.
Jan 19 23:07:35 Laptuggernaut rtkit-daemon[1148]: Demoting known real-time threads.
Jan 19 23:07:35 Laptuggernaut systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Jan 19 23:07:35 Laptuggernaut bluetoothd[796]: Endpoint unregistered: sender=:1.37 path=/MediaEndpoint/A2DPSource/ldac_mq
Jan 19 23:07:35 Laptuggernaut systemd[1]: Starting Load/Save RF Kill Switch Status...
Jan 19 23:07:35 Laptuggernaut bluetoothd[796]: Endpoint unregistered: sender=:1.37 path=/MediaEndpoint/A2DPSink/aptx_hd
Jan 19 23:07:35 Laptuggernaut bluetoothd[796]: Endpoint unregistered: sender=:1.37 path=/MediaEndpoint/A2DPSource/aptx_hd
Jan 19 23:07:35 Laptuggernaut bluetoothd[796]: Endpoint unregistered: sender=:1.37 path=/MediaEndpoint/A2DPSink/aptx
Jan 19 23:07:35 Laptuggernaut rtkit-daemon[1148]: Successfully demoted thread 2125 of process 1962.
Jan 19 23:07:35 Laptuggernaut bluetoothd[796]: Endpoint unregistered: sender=:1.37 path=/MediaEndpoint/A2DPSource/aptx
Jan 19 23:07:35 Laptuggernaut bluetoothd[796]: Endpoint unregistered: sender=:1.37 path=/MediaEndpoint/A2DPSink/sbc
Jan 19 23:07:35 Laptuggernaut rtkit-daemon[1148]: Successfully demoted thread 1258 of process 1139.
Jan 19 23:07:35 Laptuggernaut bluetoothd[796]: Endpoint unregistered: sender=:1.37 path=/MediaEndpoint/A2DPSource/sbc
Jan 19 23:07:35 Laptuggernaut acpid: client 1105[0:0] has disconnected
Jan 19 23:07:35 Laptuggernaut bluetoothd[796]: Endpoint unregistered: sender=:1.37 path=/MediaEndpoint/A2DPSink/sbc_xq_453
Jan 19 23:07:35 Laptuggernaut bluetoothd[796]: Endpoint unregistered: sender=:1.37 path=/MediaEndpoint/A2DPSource/sbc_xq_453
Jan 19 23:07:35 Laptuggernaut rtkit-daemon[1148]: Successfully demoted thread 1257 of process 1139.
Jan 19 23:07:35 Laptuggernaut bluetoothd[796]: Endpoint unregistered: sender=:1.37 path=/MediaEndpoint/A2DPSink/sbc_xq_512
Jan 19 23:07:35 Laptuggernaut bluetoothd[796]: Endpoint unregistered: sender=:1.37 path=/MediaEndpoint/A2DPSource/sbc_xq_512
Jan 19 23:07:35 Laptuggernaut rtkit-daemon[1148]: Successfully demoted thread 1139 of process 1139.
Jan 19 23:07:35 Laptuggernaut bluetoothd[796]: Endpoint unregistered: sender=:1.37 path=/MediaEndpoint/A2DPSink/sbc_xq_552
Jan 19 23:07:35 Laptuggernaut bluetoothd[796]: Endpoint unregistered: sender=:1.37 path=/MediaEndpoint/A2DPSource/sbc_xq_552
Jan 19 23:07:35 Laptuggernaut rtkit-daemon[1148]: Successfully demoted thread 1167 of process 1138.
Jan 19 23:07:35 Laptuggernaut rtkit-daemon[1148]: Successfully demoted thread 1138 of process 1138.
Jan 19 23:07:35 Laptuggernaut rtkit-daemon[1148]: Demoted 6 threads.
Jan 19 23:07:35 Laptuggernaut systemd[1]: Started Load/Save RF Kill Switch Status.
Jan 19 23:07:35 Laptuggernaut systemd[1]: Stopped target Bluetooth Support.
Jan 19 23:07:35 Laptuggernaut kernel: [  125.084720] psmouse serio4: synaptics: queried max coordinates: x [..5556], y [..4718]
Jan 19 23:07:36 Laptuggernaut systemd[1]: Reached target Bluetooth Support.
Jan 19 23:07:36 Laptuggernaut systemd[1130]: Reached target Bluetooth.
Jan 19 23:07:36 Laptuggernaut systemd-sleep[3731]: System returned from sleep state.
Jan 19 23:07:36 Laptuggernaut kernel: [  125.661904] video LNXVIDEO:00: Restoring backlight state
Jan 19 23:07:36 Laptuggernaut kernel: [  125.662134] PM: suspend exit
Jan 19 23:07:36 Laptuggernaut pulseaudio[1139]: Could not find org.bluez.BatteryProviderManager1.RegisterBatteryProvider(), is bluetoothd started with experimental features enabled (-E flag)?
Jan 19 23:07:36 Laptuggernaut systemd[1]: systemd-suspend.service: Deactivated successfully.
Jan 19 23:07:36 Laptuggernaut systemd[1]: Finished System Suspend.
Jan 19 23:07:36 Laptuggernaut systemd[1]: Stopped target Sleep.
Jan 19 23:07:36 Laptuggernaut systemd[1]: Reached target Suspend.
Jan 19 23:07:36 Laptuggernaut systemd[1]: Stopped target Suspend.
Jan 19 23:07:36 Laptuggernaut dbus-daemon[1161]: [session uid=1000 pid=1161] Activating service name='org.cinnamon.ScreenSaver' requested by ':1.25' (uid=1000 pid=1407 comm="csd-power " label="unconfined")
Jan 19 23:07:36 Laptuggernaut ModemManager[889]: <info>  [sleep-monitor-systemd] system is resuming
Jan 19 23:07:36 Laptuggernaut NetworkManager[798]: <info>  [1705723656.5874] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Jan 19 23:07:36 Laptuggernaut NetworkManager[798]: <info>  [1705723656.5875] device (enp11s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jan 19 23:07:36 Laptuggernaut bluetoothd[796]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSource/ldac_hq
Jan 19 23:07:36 Laptuggernaut bluetoothd[796]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSource/ldac_sq
Jan 19 23:07:36 Laptuggernaut bluetoothd[796]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSource/ldac_mq
Jan 19 23:07:36 Laptuggernaut bluetoothd[796]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSink/aptx_hd
Jan 19 23:07:36 Laptuggernaut bluetoothd[796]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSource/aptx_hd
Jan 19 23:07:36 Laptuggernaut bluetoothd[796]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSink/aptx
Jan 19 23:07:36 Laptuggernaut bluetoothd[796]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSource/aptx
Jan 19 23:07:36 Laptuggernaut bluetoothd[796]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSink/sbc
Jan 19 23:07:36 Laptuggernaut bluetoothd[796]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSource/sbc
Jan 19 23:07:36 Laptuggernaut bluetoothd[796]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSink/sbc_xq_453
Jan 19 23:07:36 Laptuggernaut bluetoothd[796]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSource/sbc_xq_453
Jan 19 23:07:36 Laptuggernaut bluetoothd[796]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSink/sbc_xq_512
Jan 19 23:07:36 Laptuggernaut bluetoothd[796]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSource/sbc_xq_512
Jan 19 23:07:36 Laptuggernaut bluetoothd[796]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSink/sbc_xq_552
Jan 19 23:07:36 Laptuggernaut bluetoothd[796]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSource/sbc_xq_552
Jan 19 23:07:36 Laptuggernaut NetworkManager[798]: <info>  [1705723656.6103] device (wlp10s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jan 19 23:07:36 Laptuggernaut acpid: client connected from 1105[0:0]
Jan 19 23:07:36 Laptuggernaut acpid: 1 client rule loaded
Jan 19 23:07:36 Laptuggernaut NetworkManager[798]: <info>  [1705723656.7627] device (p2p-dev-wlp10s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jan 19 23:07:36 Laptuggernaut NetworkManager[798]: <info>  [1705723656.7643] manager: NetworkManager state is now DISCONNECTED
Jan 19 23:07:36 Laptuggernaut NetworkManager[798]: <info>  [1705723656.8007] device (wlp10s0): supplicant interface state: internal-starting -> disconnected
Jan 19 23:07:36 Laptuggernaut NetworkManager[798]: <info>  [1705723656.8008] device (p2p-dev-wlp10s0): state change: unavailable -> unmanaged (reason 'removed', sys-iface-state: 'removed')
Jan 19 23:07:36 Laptuggernaut NetworkManager[798]: <info>  [1705723656.8015] Wi-Fi P2P device controlled by interface wlp10s0 created
Jan 19 23:07:36 Laptuggernaut NetworkManager[798]: <info>  [1705723656.8019] manager: (p2p-dev-wlp10s0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/5)
Jan 19 23:07:36 Laptuggernaut NetworkManager[798]: <info>  [1705723656.8039] device (p2p-dev-wlp10s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jan 19 23:07:36 Laptuggernaut NetworkManager[798]: <info>  [1705723656.8048] device (wlp10s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Jan 19 23:07:36 Laptuggernaut NetworkManager[798]: <info>  [1705723656.8057] device (p2p-dev-wlp10s0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Jan 19 23:07:36 Laptuggernaut dbus-daemon[797]: [system] Activating via systemd: service name='org.blueman.Mechanism' unit='blueman-mechanism.service' requested by ':1.62' (uid=1000 pid=1591 comm="/usr/bin/python3 /usr/bin/blueman-applet " label="unconfined")
Jan 19 23:07:36 Laptuggernaut systemd[1]: Starting Bluetooth management mechanism...
Jan 19 23:07:37 Laptuggernaut org.cinnamon.ScreenSaver[3872]: Loading AccountsService
Jan 19 23:07:37 Laptuggernaut org.cinnamon.ScreenSaver[3872]: Fractional scaling active: False
Jan 19 23:07:37 Laptuggernaut org.cinnamon.ScreenSaver[3872]: Trying to connect to logind...
Jan 19 23:07:37 Laptuggernaut dbus-daemon[1161]: [session uid=1000 pid=1161] Successfully activated service 'org.cinnamon.ScreenSaver'
Jan 19 23:07:37 Laptuggernaut org.cinnamon.ScreenSaver[3872]: Starting screensaver...
Jan 19 23:07:37 Laptuggernaut org.cinnamon.ScreenSaver[3872]: Cinnamon Screensaver support not found in current theme - adding some...
Jan 19 23:07:37 Laptuggernaut cinnamon-session[1141]: WARNING: t+103.16380s: Detected that screensaver has appeared on the bus
Jan 19 23:07:37 Laptuggernaut dbus-daemon[797]: [system] Successfully activated service 'org.blueman.Mechanism'
Jan 19 23:07:37 Laptuggernaut systemd[1]: Started Bluetooth management mechanism.
Jan 19 23:07:37 Laptuggernaut org.cinnamon.ScreenSaver[3872]: AccountsService ready
Jan 19 23:07:37 Laptuggernaut org.cinnamon.ScreenSaver[3872]: Successfully using logind
Jan 19 23:07:37 Laptuggernaut NetworkManager[798]: <info>  [1705723657.8335] policy: auto-activating connection 'Auto FiOS-9RQ6B' (f6fa60a8-c239-465b-9a54-73ed7502a2e9)
Jan 19 23:07:37 Laptuggernaut NetworkManager[798]: <info>  [1705723657.8348] device (wlp10s0): Activation: starting connection 'Auto FiOS-9RQ6B' (f6fa60a8-c239-465b-9a54-73ed7502a2e9)
Jan 19 23:07:37 Laptuggernaut NetworkManager[798]: <info>  [1705723657.8350] device (wlp10s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 19 23:07:37 Laptuggernaut NetworkManager[798]: <info>  [1705723657.8356] manager: NetworkManager state is now CONNECTING
Jan 19 23:07:37 Laptuggernaut NetworkManager[798]: <info>  [1705723657.8362] device (wlp10s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 19 23:07:37 Laptuggernaut NetworkManager[798]: <info>  [1705723657.8370] device (wlp10s0): Activation: (wifi) access point 'Auto FiOS-9RQ6B' has security, but secrets are required.
Jan 19 23:07:37 Laptuggernaut NetworkManager[798]: <info>  [1705723657.8370] device (wlp10s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jan 19 23:07:37 Laptuggernaut NetworkManager[798]: <info>  [1705723657.8374] sup-iface[51084977cd3a288d,1,wlp10s0]: wps: type pbc start...
Jan 19 23:07:37 Laptuggernaut NetworkManager[798]: <info>  [1705723657.8397] device (wlp10s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 19 23:07:37 Laptuggernaut NetworkManager[798]: <info>  [1705723657.8403] device (wlp10s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 19 23:07:37 Laptuggernaut NetworkManager[798]: <info>  [1705723657.8409] device (wlp10s0): Activation: (wifi) connection 'Auto FiOS-9RQ6B' has security, and secrets exist.  No new secrets needed.
Jan 19 23:07:37 Laptuggernaut NetworkManager[798]: <info>  [1705723657.8410] Config: added 'ssid' value 'FiOS-9RQ6B'
Jan 19 23:07:37 Laptuggernaut NetworkManager[798]: <info>  [1705723657.8410] Config: added 'scan_ssid' value '1'
Jan 19 23:07:37 Laptuggernaut NetworkManager[798]: <info>  [1705723657.8410] Config: added 'bgscan' value 'simple:30:-70:86400'
Jan 19 23:07:37 Laptuggernaut NetworkManager[798]: <info>  [1705723657.8411] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
Jan 19 23:07:37 Laptuggernaut NetworkManager[798]: <info>  [1705723657.8411] Config: added 'auth_alg' value 'OPEN'
Jan 19 23:07:37 Laptuggernaut NetworkManager[798]: <info>  [1705723657.8411] Config: added 'psk' value '<hidden>'
Jan 19 23:07:37 Laptuggernaut wpa_supplicant[832]: wlp10s0: WPS-CANCEL 
Jan 19 23:07:37 Laptuggernaut wpa_supplicant[832]: wlp10s0: SME: Trying to authenticate with c8:a7:0a:ac:06:f4 (SSID='FiOS-9RQ6B' freq=2462 MHz)
Jan 19 23:07:37 Laptuggernaut kernel: [  127.037822] wlp10s0: authenticate with c8:a7:0a:ac:06:f4
Jan 19 23:07:37 Laptuggernaut NetworkManager[798]: <info>  [1705723657.8905] device (wlp10s0): supplicant interface state: disconnected -> authenticating
Jan 19 23:07:37 Laptuggernaut NetworkManager[798]: <info>  [1705723657.8906] device (p2p-dev-wlp10s0): supplicant management interface state: disconnected -> authenticating
Jan 19 23:07:37 Laptuggernaut wpa_supplicant[832]: wlp10s0: Trying to associate with c8:a7:0a:ac:06:f4 (SSID='FiOS-9RQ6B' freq=2462 MHz)
Jan 19 23:07:37 Laptuggernaut kernel: [  127.047856] wlp10s0: send auth to c8:a7:0a:ac:06:f4 (try 1/3)
Jan 19 23:07:37 Laptuggernaut kernel: [  127.049409] wlp10s0: authenticated
Jan 19 23:07:37 Laptuggernaut NetworkManager[798]: <info>  [1705723657.8922] device (wlp10s0): supplicant interface state: authenticating -> associating
Jan 19 23:07:37 Laptuggernaut NetworkManager[798]: <info>  [1705723657.8923] device (p2p-dev-wlp10s0): supplicant management interface state: authenticating -> associating
Jan 19 23:07:37 Laptuggernaut kernel: [  127.053802] wlp10s0: associate with c8:a7:0a:ac:06:f4 (try 1/3)
Jan 19 23:07:37 Laptuggernaut kernel: [  127.061565] wlp10s0: RX AssocResp from c8:a7:0a:ac:06:f4 (capab=0x431 status=0 aid=5)
Jan 19 23:07:37 Laptuggernaut wpa_supplicant[832]: wlp10s0: Associated with c8:a7:0a:ac:06:f4
Jan 19 23:07:37 Laptuggernaut wpa_supplicant[832]: wlp10s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jan 19 23:07:37 Laptuggernaut wpa_supplicant[832]: wlp10s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=US
Jan 19 23:07:37 Laptuggernaut kernel: [  127.063188] rtl8192se: switch case 0x5e not processed
Jan 19 23:07:37 Laptuggernaut kernel: [  127.063211] wlp10s0: associated
Jan 19 23:07:37 Laptuggernaut NetworkManager[798]: <info>  [1705723657.9117] device (wlp10s0): supplicant interface state: associating -> associated
Jan 19 23:07:37 Laptuggernaut NetworkManager[798]: <info>  [1705723657.9117] device (p2p-dev-wlp10s0): supplicant management interface state: associating -> associated
Jan 19 23:07:37 Laptuggernaut NetworkManager[798]: <info>  [1705723657.9193] device (wlp10s0): supplicant interface state: associated -> 4way_handshake
Jan 19 23:07:37 Laptuggernaut NetworkManager[798]: <info>  [1705723657.9193] device (p2p-dev-wlp10s0): supplicant management interface state: associated -> 4way_handshake
Jan 19 23:07:37 Laptuggernaut wpa_supplicant[832]: wlp10s0: WPA: Key negotiation completed with c8:a7:0a:ac:06:f4 [PTK=CCMP GTK=CCMP]
Jan 19 23:07:37 Laptuggernaut wpa_supplicant[832]: wlp10s0: CTRL-EVENT-CONNECTED - Connection to c8:a7:0a:ac:06:f4 completed [id=0 id_str=]
Jan 19 23:07:37 Laptuggernaut wpa_supplicant[832]: bgscan simple: Failed to enable signal strength monitoring
Jan 19 23:07:37 Laptuggernaut NetworkManager[798]: <info>  [1705723657.9932] device (wlp10s0): supplicant interface state: 4way_handshake -> completed
Jan 19 23:07:37 Laptuggernaut NetworkManager[798]: <info>  [1705723657.9933] device (wlp10s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "FiOS-9RQ6B"
Jan 19 23:07:37 Laptuggernaut NetworkManager[798]: <info>  [1705723657.9933] device (p2p-dev-wlp10s0): supplicant management interface state: 4way_handshake -> completed
Jan 19 23:07:37 Laptuggernaut NetworkManager[798]: <info>  [1705723657.9936] device (wlp10s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jan 19 23:07:37 Laptuggernaut kernel: [  127.149864] IPv6: ADDRCONF(NETDEV_CHANGE): wlp10s0: link becomes ready
Jan 19 23:07:37 Laptuggernaut NetworkManager[798]: <info>  [1705723657.9948] dhcp4 (wlp10s0): activation: beginning transaction (timeout in 45 seconds)
Jan 19 23:07:37 Laptuggernaut avahi-daemon[794]: Joining mDNS multicast group on interface wlp10s0.IPv6 with address fe80::6aca:c66a:7391:2fbd.
Jan 19 23:07:37 Laptuggernaut avahi-daemon[794]: New relevant interface wlp10s0.IPv6 for mDNS.
Jan 19 23:07:37 Laptuggernaut avahi-daemon[794]: Registering new address record for fe80::6aca:c66a:7391:2fbd on wlp10s0.*.
Jan 19 23:07:38 Laptuggernaut NetworkManager[798]: <info>  [1705723658.0559] dhcp4 (wlp10s0): state changed new lease, address=192.168.1.236
Jan 19 23:07:38 Laptuggernaut avahi-daemon[794]: Joining mDNS multicast group on interface wlp10s0.IPv4 with address 192.168.1.236.
Jan 19 23:07:38 Laptuggernaut avahi-daemon[794]: New relevant interface wlp10s0.IPv4 for mDNS.
Jan 19 23:07:38 Laptuggernaut avahi-daemon[794]: Registering new address record for 192.168.1.236 on wlp10s0.IPv4.
Jan 19 23:07:38 Laptuggernaut dbus-daemon[797]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.9' (uid=0 pid=798 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Jan 19 23:07:38 Laptuggernaut NetworkManager[798]: <info>  [1705723658.0587] device (wlp10s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jan 19 23:07:38 Laptuggernaut systemd[1]: Starting Network Manager Script Dispatcher Service...
Jan 19 23:07:38 Laptuggernaut dbus-daemon[797]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jan 19 23:07:38 Laptuggernaut systemd[1]: Started Network Manager Script Dispatcher Service.
Jan 19 23:07:38 Laptuggernaut NetworkManager[798]: <info>  [1705723658.0786] device (wlp10s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jan 19 23:07:38 Laptuggernaut NetworkManager[798]: <info>  [1705723658.0791] device (wlp10s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jan 19 23:07:38 Laptuggernaut NetworkManager[798]: <info>  [1705723658.0798] manager: NetworkManager state is now CONNECTED_LOCAL
Jan 19 23:07:38 Laptuggernaut NetworkManager[798]: <info>  [1705723658.0808] manager: NetworkManager state is now CONNECTED_SITE
Jan 19 23:07:38 Laptuggernaut NetworkManager[798]: <info>  [1705723658.0811] policy: set 'Auto FiOS-9RQ6B' (wlp10s0) as default for IPv4 routing and DNS
Jan 19 23:07:38 Laptuggernaut NetworkManager[798]: <info>  [1705723658.0824] device (wlp10s0): Activation: successful, device activated.
Jan 19 23:07:38 Laptuggernaut systemd-resolved[734]: wlp10s0: Bus client set search domain list to: fios-router.home
Jan 19 23:07:38 Laptuggernaut systemd-resolved[734]: wlp10s0: Bus client set default route setting: yes
Jan 19 23:07:38 Laptuggernaut systemd-resolved[734]: wlp10s0: Bus client set DNS server list to: 192.168.1.1
Jan 19 23:07:38 Laptuggernaut NetworkManager[798]: <info>  [1705723658.2223] manager: NetworkManager state is now CONNECTED_GLOBAL
Jan 19 23:07:39 Laptuggernaut ModemManager[889]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.4/0000:0a:00.0': not supported by any plugin
Jan 19 23:07:39 Laptuggernaut ModemManager[889]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.6/0000:0b:00.0': not supported by any plugin
Jan 19 23:07:41 Laptuggernaut systemd[1]: systemd-rfkill.service: Deactivated successfully.
Jan 19 23:07:42 Laptuggernaut surfsharkd.js[1140]: JS LOG: [#012  "wlp10s0"#012]
Jan 19 23:07:42 Laptuggernaut surfsharkd.js[1140]: JS LOG: active physical connections
Jan 19 23:07:42 Laptuggernaut surfsharkd.js[1140]: JS LOG: [#012  {#012    "id": "Auto FiOS-9RQ6B",#012    "type": "802-11-wireless",#012    "uuid": "f6fa60a8-c239-465b-9a54-73ed7502a2e9",#012    "wireless_security": {#012      "key_mgmt": "wpa-psk"#012    },#012    "internal_networks": [#012      {#012        "gateway": "192.168.1.1",#012        "protocol": "ipv4",#012        "address": "192.168.1.236",#012        "family": 24,#012        "_noncompliant": false#012      }#012    ],#012    "interface_name": "wlp10s0",#012    "_noncompliant": false#012  }#012]
Jan 19 23:07:48 Laptuggernaut systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Jan 19 23:08:07 Laptuggernaut systemd[1]: blueman-mechanism.service: Deactivated successfully.
Jan 19 23:08:07 Laptuggernaut cinnamon-session[1141]: WARNING: t+133.17184s: Detected that screensaver has left the bus
Jan 19 23:08:09 Laptuggernaut kernel: [  158.865835] CE: hpet increased min_delta_ns to 20115 nsec
The graphics chipset is nVidea (GTX 460M) (and this laptop is from - yikes - 2010) should I be considering a driver from nVidea? Not sure if they have support for something this old in new unified drivers....
Top
User avatar
SMG
Level 25
Level 25
Posts: 32007
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: System menus corrupted after sleep on 21.3

Post by SMG »

VancoD wrote: ⤴Sat Jan 20, 2024 12:21 amI am aware hibernation is different from sleep. :D The power button option, and the logs, say "suspend" - I assumed that to mean hibernation.
It does not mean hibernation. It means suspend/sleep.
VancoD wrote: ⤴Sat Jan 20, 2024 12:21 am I assume the lid close makes the same call as the results are the same. The power indicator "pulses" - so perhaps this is, in fact, "sleep" :?:
Yes, it is sleep. Sleep and suspend are the same thing.
VancoD wrote: ⤴Sat Jan 20, 2024 12:21 amThis was a dist upgrade from 21.2 to 21.3
Does this mean you did not use the option in Update Manager to upgrade?

The only people I've heard term this as a dist upgrade are one which are using terminal commands instead of the program designed by the Linux Mint developers. However, you could be an exception to that observation.

In one sense, the image you posted reminds me of problems people have had in the past with the oibaf PPA. You don't have that installed, but that PPA relates to graphics driver related packages. That may be why restarting Cinnamon had no effect. That only restarts the desktop environment. You would need to restart X Server to reload graphics. However, doing that means you lose everything which is open which likely defeats the reason you are suspending the computer. (X Server can be restarted with Ctl-Alt-Backspace.)
VancoD wrote: ⤴Sat Jan 20, 2024 12:21 amThe graphics chipset is nVidea (GTX 460M) (and this laptop is from - yikes - 2010) should I be considering a driver from nVidea? Not sure if they have support for something this old in new unified drivers....
Your inxi output indicates you are already using an Nvidia driver.

Device-1: NVIDIA GF106M [GeForce GTX 460M] vendor: Toshiba driver: nvidia
v: 390.157 pcie: speed: 5 GT/s lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:0dd1

Nothing in the output gave me any ideas of what might be happening. You are not seeing any messages in the System Reports app (either in System Reports or Crash Reports) are you?
Image
A woman typing on a laptop with LM20.3 Cinnamon.
Top
VancoD
Level 1
Level 1
Posts: 4
Joined: Wed Jan 17, 2024 10:37 pm

Re: System menus corrupted after sleep on 21.3

Post by VancoD »

SMG wrote: ⤴Sat Jan 20, 2024 6:14 pm The only people I've heard term this as a dist upgrade are one which are using terminal commands instead of the program designed by the Linux Mint developers.
Yeah - Debian admin by day (or sorts). I did see the GUI tool (which is what told me there was an update to be had), but I was already on CLI doing things (the VPN install) and just did a dist upgrade by force of habit.
SMG wrote: ⤴Sat Jan 20, 2024 6:14 pm Nothing in the output gave me any ideas of what might be happening. You are not seeing any messages in the System Reports app (either in System Reports or Crash Reports) are you?
Hadn't seen this before but it looks like Cinnamon cored at least once - https://termbin.com/9r9t (I think that happened right after I made my initial post).
That's the only instance.

If it proves a point I can easily reimage this with 21.2 and use the upgrade tool to get to 21.3. If nothing else it would prove dist-upgrade isn't ready for prime time :)
Top
VancoD
Level 1
Level 1
Posts: 4
Joined: Wed Jan 17, 2024 10:37 pm

Re: System menus corrupted after sleep on 21.3

Post by VancoD »

> Also, please create a new user and see if the new user has the same problem.

ARGH - didn't see this bit until now. I did create a new user and it does NOT have the problem! So there must be some bits of cruft in my config from the update / using dist-upgrade.
Top
User avatar
SMG
Level 25
Level 25
Posts: 32007
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: System menus corrupted after sleep on 21.3

Post by SMG »

VancoD wrote: ⤴Sat Jan 20, 2024 8:51 pmYeah - Debian admin by day (or sorts). I did see the GUI tool (which is what told me there was an update to be had), but I was already on CLI doing things (the VPN install) and just did a dist upgrade by force of habit.
I could be wrong, but I thought there were other steps involved in the upgrade besides doing a dist upgrade. I know part of the upgrade process mentions, "If asked whether to keep or replace configuration files, choose to replace them." so I think I've always assumed it was better to run if from the GUI. That is the official way to Upgrade to LM21.3.
VancoD wrote: ⤴Sat Jan 20, 2024 8:51 pm Hadn't seen this before but it looks like Cinnamon cored at least once - https://termbin.com/9r9t (I think that happened right after I made my initial post).
That's the only instance.
Signal: 11 (SEGV) not good. I see mention of the Nvidia driver in the GDB Log.

Code: Select all

Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007f479e1f016b in ?? () from /lib/x86_64-linux-gnu/libnvidia-glcore.so.390.157
VancoD wrote: ⤴Sat Jan 20, 2024 9:00 pm > Also, please create a new user and see if the new user has the same problem.

ARGH - didn't see this bit until now. I did create a new user and it does NOT have the problem! So there must be some bits of cruft in my config from the update / using dist-upgrade.
I just erased the part saying re-imaging and doing the upgrade via Update Manager would help in filing a bug report because I saw this post. This result would indicate it is somehow a setting with your user if a new user does not have the problem. That new user would be using the same base LM21.3 as your current user. Now which setting it is which might be causing the problem I do not know.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
Top
Post Reply

Return to “Cinnamon”