Latte-Dock tends to freeze up whole system

Issues & Assistance Latte Dock
1

As the title says, sometimes when i open a program from my latte-dock dock, it tends to freeze up the whole pc, to the point where i have to force a hard reboot, this usually happens after the pc wakes up from sleep. It wouldnt be that much of a problem but stuff tends to break on hard reboots. Anyone else experiencing this?

System:
  Kernel: 5.16.2-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=3bf66fc0-89ba-4f98-b6f6-81b2ff1ff168 rw rootflags=subvol=@
    quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
    systemd.unified_cgroup_hierarchy=1
    resume=UUID=fd7e8027-710d-411d-82b6-505a4c2b5304 loglevel=3
    nvidia-drm.modeset=1
  Desktop: KDE Plasma 5.23.5 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11
    vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Laptop System: Micro-Star product: GL62M 7REX v: REV:1.0
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: Micro-Star model: MS-16J9 v: REV:1.0 serial: <superuser required>
    UEFI: American Megatrends v: E16J9IMS.31A date: 07/11/2017
Battery:
  ID-1: BAT1 charge: 33.0 Wh (90.9%) condition: 36.3/42.4 Wh (85.6%)
    volts: 11.9 min: 10.8 model: MSI BIF0_9 type: Li-ion serial: N/A
    status: N/A
CPU:
  Info: model: Intel Core i5-7300HQ bits: 64 type: MCP arch: Kaby Lake
    family: 6 model-id: 0x9E (158) stepping: 9 microcode: 0xEA
  Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 256 KiB
    desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 6 MiB
    desc: 1x6 MiB
  Speed (MHz): avg: 3178 high: 3191 min/max: 800/3500 scaling:
    driver: intel_pstate governor: performance cores: 1: 3182 2: 3187 3: 3191
    4: 3154 bogomips: 19999
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf
    mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled
  Type: mds mitigation: Clear CPU buffers; SMT disabled
  Type: meltdown mitigation: PTI
  Type: spec_store_bypass
    mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1
    mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional,
    IBRS_FW, STIBP: disabled, RSB filling
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel HD Graphics 630 vendor: Micro-Star MSI driver: i915
    v: kernel bus-ID: 00:02.0 chip-ID: 8086:591b class-ID: 0300
  Device-2: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile]
    vendor: Micro-Star MSI driver: nvidia v: 495.46
    alternate: nouveau,nvidia_drm bus-ID: 01:00.0 chip-ID: 10de:1c8c
    class-ID: 0302
  Display: x11 server: X.Org 1.21.1.3 compositor: kwin_x11 driver:
    loaded: modesetting,nvidia display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1013x285mm (39.9x11.2")
    s-diag: 1052mm (41.4")
  Monitor-1: eDP-1-1 res: 1920x1080 dpi: 142 size: 344x194mm (13.5x7.6")
    diag: 395mm (15.5")
  Monitor-2: HDMI-1-2 res: 1920x1080 hz: 60 dpi: 92
    size: 528x297mm (20.8x11.7") diag: 606mm (23.9")
  OpenGL: renderer: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2
    v: 4.6.0 NVIDIA 495.46 direct render: Yes
Audio:
  Device-1: Intel CM238 HD Audio vendor: Micro-Star MSI driver: snd_hda_intel
    v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a171 class-ID: 0403
  Sound Server-1: ALSA v: k5.16.2-zen1-1-zen running: yes
  Sound Server-2: PulseAudio v: 15.0 running: no
  Sound Server-3: PipeWire v: 0.3.43 running: yes
Network:
  Device-1: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi
    v: kernel bus-ID: 02:00.0 chip-ID: 8086:24fb class-ID: 0280
  IF: wlp2s0 state: down mac: <filter>
  Device-2: Qualcomm Atheros QCA8171 Gigabit Ethernet
    vendor: Micro-Star MSI driver: alx v: kernel port: d000 bus-ID: 03:00.0
    chip-ID: 1969:10a1 class-ID: 0200
  IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Intel Wireless-AC 3168 Bluetooth type: USB driver: btusb v: 0.8
    bus-ID: 1-10:6 chip-ID: 8087:0aa7 class-ID: e001
  Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
  Local Storage: total: 685.61 GiB used: 192.08 GiB (28.0%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Kingston model: RBU-SNS8152S3256GG5
    size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    type: SSD serial: <filter> rev: 01.R scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Crucial model: CT480M500SSD1
    size: 447.13 GiB block-size: physical: 4096 B logical: 512 B
    speed: 6.0 Gb/s type: SSD serial: <filter> rev: MU03 scheme: MBR
Partition:
  ID-1: / raw-size: 229.37 GiB size: 229.37 GiB (100.00%)
    used: 192.08 GiB (83.7%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 576 KiB (0.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1
  ID-3: /home raw-size: 229.37 GiB size: 229.37 GiB (100.00%)
    used: 192.08 GiB (83.7%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-4: /var/log raw-size: 229.37 GiB size: 229.37 GiB (100.00%)
    used: 192.08 GiB (83.7%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-5: /var/tmp raw-size: 229.37 GiB size: 229.37 GiB (100.00%)
    used: 192.08 GiB (83.7%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 8.8 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/sda3 maj-min: 8:3
  ID-2: swap-2 type: zram size: 15.55 GiB used: 2 MiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 58.0 C pch: 38.0 C mobo: 27.8 C gpu: nvidia
    temp: 38 C
  Fan Speeds (RPM): N/A
Info:
  Processes: 256 Uptime: 1m wakeups: 1 Memory: 15.55 GiB
  used: 4.93 GiB (31.7%) Init: systemd v: 250 tool: systemctl Compilers:
  gcc: 11.1.0 clang: 13.0.0 Packages: 1927 note: see --pkg apt: 0
  pacman: 1919 lib: 504 flatpak: 8 Shell: fish v: 3.3.1 running-in: konsole
  inxi: 3.3.12
Garuda:
  System install date:     2021-11-26
  Last full system update: 2022-02-03
  Is partially upgraded:   No
  Using TLP:               No
  Windows dual boot:       No/Undetected
1 Like
2

Do you mean that when you open an app from somewhere else, there is no problem?
Blaming latte requires some evidence from logs

journalctl -b -p3
journalctl -b -1 -p3
2 Likes
3

Yes, when i open it from latte,

journalctl -b -p3 ::

feb 07 23:07:54 MSIGARUDA kernel: x86/cpu: SGX disabled by BIOS.
feb 07 23:07:55 MSIGARUDA kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [m>
feb 07 23:07:55 MSIGARUDA kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [m>
feb 07 23:07:55 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 07 23:07:55 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 07 23:07:55 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 07 23:07:55 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 07 23:07:55 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 07 23:07:55 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 07 23:07:55 MSIGARUDA systemd-tmpfiles[471]: Failed to write file "/sys/module/pcie_aspm/parameters/policy": Operation not permitted
feb 07 23:07:56 MSIGARUDA libvirtd[519]: cannot open directory '/run/media/jurosic_park/2ndSSD/VMs': No such file or directory
feb 07 23:07:56 MSIGARUDA libvirtd[519]: internal error: Failed to autostart storage pool '2ndSSD': cannot open directory '/run/media/ju>
feb 07 23:07:56 MSIGARUDA libvirtd[519]: cannot open directory '/run/media/jurosic_park/DISK M-PC': No such file or directory
feb 07 23:07:56 MSIGARUDA libvirtd[519]: internal error: Failed to autostart storage pool 'DISK_M-PC': cannot open directory '/run/media>
feb 07 23:07:57 MSIGARUDA kernel: 
feb 07 23:07:57 MSIGARUDA kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  495.46  Wed Oct 27 16:31:33 UTC 2021
feb 07 23:07:58 MSIGARUDA nmbd[1900]: [2022/02/07 23:07:58.606532,  0] ../../source3/nmbd/nmbd.c:901(main)
feb 07 23:07:58 MSIGARUDA nmbd[1900]:   nmbd version 4.15.4 started.
feb 07 23:07:58 MSIGARUDA nmbd[1900]:   Copyright Andrew Tridgell and the Samba Team 1992-2021
feb 07 23:07:58 MSIGARUDA smbd[1932]: [2022/02/07 23:07:58.704586,  0] ../../source3/smbd/server.c:1734(main)
feb 07 23:07:58 MSIGARUDA smbd[1932]:   smbd version 4.15.4 started.
feb 08 07:53:50 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 08 07:53:50 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 08 07:53:50 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 08 07:53:50 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 08 07:53:50 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 08 07:53:50 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 08 07:54:31 MSIGARUDA kernel: NVRM: GPU at PCI:0000:01:00: GPU-63f4bd47-9605-c863-2296-278181802e42
feb 08 07:54:31 MSIGARUDA kernel: NVRM: Xid (PCI:0000:01:00): 31, pid=8254, Ch 00000060, intr 10000000. MMU Fault: ENGINE HOST0 HUBCLIENT_HOST_CPU faulted @ 0x1_041fc000. Fault is of type FAULT_PTE ACCESS_TYPE_WRITE
feb 08 07:54:31 MSIGARUDA kernel: NVRM: Xid (PCI:0000:01:00): 31, pid=8254, Ch 00000060, intr 10000000. MMU Fault: ENGINE HOST0 HUBCLIENT_HOST_CPU faulted @ 0x1_041fc000. Fault is of type FAULT_PTE ACCESS_TYPE_WRITE
feb 08 07:54:32 MSIGARUDA kernel: NVRM: Xid (PCI:0000:01:00): 31, pid=8254, Ch 00000060, intr 10000000. MMU Fault: ENGINE HOST0 HUBCLIENT_HOST_CPU faulted @ 0x1_041fc000. Fault is of type FAULT_PTE ACCESS_TYPE_WRITE
feb 08 07:54:32 MSIGARUDA kernel: NVRM: Xid (PCI:0000:01:00): 31, pid=8254, Ch 00000060, intr 10000000. MMU Fault: ENGINE HOST0 HUBCLIENT_HOST_CPU faulted @ 0x1_041fc000. Fault is of type FAULT_PTE ACCESS_TYPE_WRITE
feb 08 07:54:32 MSIGARUDA kernel: NVRM: Xid (PCI:0000:01:00): 31, pid=8254, Ch 00000060, intr 10000000. MMU Fault: ENGINE HOST0 HUBCLIENT_HOST_CPU faulted @ 0x1_041fc000. Fault is of type FAULT_PTE ACCESS_TYPE_WRITE
feb 08 07:54:32 MSIGARUDA kernel: NVRM: Xid (PCI:0000:01:00): 31, pid=8254, Ch 00000060, intr 10000000. MMU Fault: ENGINE HOST0 HUBCLIENT_HOST_CPU faulted @ 0x1_041fc000. Fault is of type FAULT_PTE ACCESS_TYPE_WRITE
feb 08 07:54:32 MSIGARUDA kernel: NVRM: Xid (PCI:0000:01:00): 31, pid=8254, Ch 00000060, intr 10000000. MMU Fault: ENGINE HOST0 HUBCLIENT_HOST_CPU faulted @ 0x1_041fc000. Fault is of type FAULT_PTE ACCESS_TYPE_WRITE
feb 08 07:54:32 MSIGARUDA kernel: NVRM: Xid (PCI:0000:01:00): 31, pid=8254, Ch 00000060, intr 10000000. MMU Fault: ENGINE HOST0 HUBCLIENT_HOST_CPU faulted @ 0x1_041fc000. Fault is of type FAULT_PTE ACCESS_TYPE_WRITE
feb 08 07:54:32 MSIGARUDA kernel: NVRM: Xid (PCI:0000:01:00): 31, pid=8254, Ch 00000060, intr 10000000. MMU Fault: ENGINE HOST0 HUBCLIENT_HOST_CPU faulted @ 0x1_041fc000. Fault is of type FAULT_PTE ACCESS_TYPE_WRITE
feb 08 07:54:32 MSIGARUDA kernel: NVRM: Xid (PCI:0000:01:00): 31, pid=8254, Ch 00000060, intr 10000000. MMU Fault: ENGINE HOST0 HUBCLIENT_HOST_CPU faulted @ 0x1_041fc000. Fault is of type FAULT_PTE ACCESS_TYPE_WRITE
feb 08 07:54:32 MSIGARUDA kernel: NVRM: Xid (PCI:0000:01:00): 31, pid=8254, Ch 00000060, intr 10000000. MMU Fault: ENGINE HOST0 HUBCLIENT_HOST_CPU faulted @ 0x1_041fc000. Fault is of type FAULT_PTE ACCESS_TYPE_WRITE
feb 08 07:54:32 MSIGARUDA kernel: NVRM: Xid (PCI:0000:01:00): 31, pid=8254, Ch 00000060, intr 10000000. MMU Fault: ENGINE HOST0 HUBCLIENT_HOST_CPU faulted @ 0x1_041fc000. Fault is of type FAULT_PTE ACCESS_TYPE_WRITE
feb 08 07:54:32 MSIGARUDA kernel: NVRM: Xid (PCI:0000:01:00): 31, pid=8254, Ch 00000060, intr 10000000. MMU Fault: ENGINE HOST0 HUBCLIENT_HOST_CPU faulted @ 0x1_041fc000. Fault is of type FAULT_PTE ACCESS_TYPE_WRITE
feb 08 07:54:32 MSIGARUDA kernel: NVRM: Xid (PCI:0000:01:00): 31, pid=8254, Ch 00000060, intr 10000000. MMU Fault: ENGINE HOST0 HUBCLIENT_HOST_CPU faulted @ 0x1_041fc000. Fault is of type FAULT_PTE ACCESS_TYPE_WRITE
feb 08 07:57:52 MSIGARUDA nmbd[1900]: [2022/02/08 07:57:52.128030,  0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2)
feb 08 07:57:52 MSIGARUDA nmbd[1900]:   *****
feb 08 07:57:52 MSIGARUDA nmbd[1900]: 
feb 08 07:57:52 MSIGARUDA nmbd[1900]:   Samba name server MSIGARUDA is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.72
feb 08 07:57:52 MSIGARUDA nmbd[1900]: 
feb 08 07:57:52 MSIGARUDA nmbd[1900]:   *****
feb 08 11:17:27 MSIGARUDA kernel: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers
feb 08 11:17:27 MSIGARUDA kernel: CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers
feb 08 11:17:33 MSIGARUDA kernel: CIFS: VFS: multichannel is not supported on this protocol version, use 3.0 or above
feb 08 11:17:35 MSIGARUDA kernel: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers
feb 08 11:17:35 MSIGARUDA kernel: CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers
feb 08 11:17:35 MSIGARUDA kernel: CIFS: VFS: multichannel is not supported on this protocol version, use 3.0 or above
feb 08 13:00:31 MSIGARUDA pipewire-pulse[5108]: mod.protocol-pulse: server 0x561888648210: client 0x56188947efc0 [Chromium] error -104 (Connection reset by peer)

journalctl -b -1 -p3 ::

feb 07 23:07:54 MSIGARUDA kernel: x86/cpu: SGX disabled by BIOS.
feb 07 23:07:55 MSIGARUDA kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [m>
feb 07 23:07:55 MSIGARUDA kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [m>
feb 07 23:07:55 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 07 23:07:55 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 07 23:07:55 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 07 23:07:55 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 07 23:07:55 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 07 23:07:55 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 07 23:07:55 MSIGARUDA systemd-tmpfiles[471]: Failed to write file "/sys/module/pcie_aspm/parameters/policy": Operation not permitted
feb 07 23:07:56 MSIGARUDA libvirtd[519]: cannot open directory '/run/media/jurosic_park/2ndSSD/VMs': No such file or directory
feb 07 23:07:56 MSIGARUDA libvirtd[519]: internal error: Failed to autostart storage pool '2ndSSD': cannot open directory '/run/media/ju>
feb 07 23:07:56 MSIGARUDA libvirtd[519]: cannot open directory '/run/media/jurosic_park/DISK M-PC': No such file or directory
feb 07 23:07:56 MSIGARUDA libvirtd[519]: internal error: Failed to autostart storage pool 'DISK_M-PC': cannot open directory '/run/media>
feb 07 23:07:57 MSIGARUDA kernel: 
feb 07 23:07:57 MSIGARUDA kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  495.46  Wed Oct 27 16:31:33 UTC 2021
feb 07 23:07:58 MSIGARUDA nmbd[1900]: [2022/02/07 23:07:58.606532,  0] ../../source3/nmbd/nmbd.c:901(main)
feb 07 23:07:58 MSIGARUDA nmbd[1900]:   nmbd version 4.15.4 started.
feb 07 23:07:58 MSIGARUDA nmbd[1900]:   Copyright Andrew Tridgell and the Samba Team 1992-2021
feb 07 23:07:58 MSIGARUDA smbd[1932]: [2022/02/07 23:07:58.704586,  0] ../../source3/smbd/server.c:1734(main)
feb 07 23:07:58 MSIGARUDA smbd[1932]:   smbd version 4.15.4 started.
feb 08 07:53:50 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 08 07:53:50 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 08 07:53:50 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 08 07:53:50 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 08 07:53:50 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 08 07:53:50 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 08 07:54:31 MSIGARUDA kernel: NVRM: GPU at PCI:0000:01:00: GPU-63f4bd47-9605-c863-2296-278181802e42
feb 08 07:54:31 MSIGARUDA kernel: NVRM: Xid (PCI:0000:01:00): 31, pid=8254, Ch 00000060, intr 10000000. MMU Fault: ENGINE HOST0 HUBCLIENT_HOST_CPU faulted @ 0x1_041fc000. Fault is of type FAULT_PTE ACCESS_TYPE_WRITE
feb 08 07:54:31 MSIGARUDA kernel: NVRM: Xid (PCI:0000:01:00): 31, pid=8254, Ch 00000060, intr 10000000. MMU Fault: ENGINE HOST0 HUBCLIENT_HOST_CPU faulted @ 0x1_041fc000. Fault is of type FAULT_PTE ACCESS_TYPE_WRITE
feb 08 07:54:32 MSIGARUDA kernel: NVRM: Xid (PCI:0000:01:00): 31, pid=8254, Ch 00000060, intr 10000000. MMU Fault: ENGINE HOST0 HUBCLIENT_HOST_CPU faulted @ 0x1_041fc000. Fault is of type FAULT_PTE ACCESS_TYPE_WRITE
feb 08 07:54:32 MSIGARUDA kernel: NVRM: Xid (PCI:0000:01:00): 31, pid=8254, Ch 00000060, intr 10000000. MMU Fault: ENGINE HOST0 HUBCLIENT_HOST_CPU faulted @ 0x1_041fc000. Fault is of type FAULT_PTE ACCESS_TYPE_WRITE
feb 08 07:54:32 MSIGARUDA kernel: NVRM: Xid (PCI:0000:01:00): 31, pid=8254, Ch 00000060, intr 10000000. MMU Fault: ENGINE HOST0 HUBCLIENT_HOST_CPU faulted @ 0x1_041fc000. Fault is of type FAULT_PTE ACCESS_TYPE_WRITE
feb 08 07:54:32 MSIGARUDA kernel: NVRM: Xid (PCI:0000:01:00): 31, pid=8254, Ch 00000060, intr 10000000. MMU Fault: ENGINE HOST0 HUBCLIENT_HOST_CPU faulted @ 0x1_041fc000. Fault is of type FAULT_PTE ACCESS_TYPE_WRITE
feb 08 07:54:32 MSIGARUDA kernel: NVRM: Xid (PCI:0000:01:00): 31, pid=8254, Ch 00000060, intr 10000000. MMU Fault: ENGINE HOST0 HUBCLIENT_HOST_CPU faulted @ 0x1_041fc000. Fault is of type FAULT_PTE ACCESS_TYPE_WRITE
feb 08 07:54:32 MSIGARUDA kernel: NVRM: Xid (PCI:0000:01:00): 31, pid=8254, Ch 00000060, intr 10000000. MMU Fault: ENGINE HOST0 HUBCLIENT_HOST_CPU faulted @ 0x1_041fc000. Fault is of type FAULT_PTE ACCESS_TYPE_WRITE
feb 08 07:54:32 MSIGARUDA kernel: NVRM: Xid (PCI:0000:01:00): 31, pid=8254, Ch 00000060, intr 10000000. MMU Fault: ENGINE HOST0 HUBCLIENT_HOST_CPU faulted @ 0x1_041fc000. Fault is of type FAULT_PTE ACCESS_TYPE_WRITE
feb 08 07:54:32 MSIGARUDA kernel: NVRM: Xid (PCI:0000:01:00): 31, pid=8254, Ch 00000060, intr 10000000. MMU Fault: ENGINE HOST0 HUBCLIENT_HOST_CPU faulted @ 0x1_041fc000. Fault is of type FAULT_PTE ACCESS_TYPE_WRITE
feb 08 07:54:32 MSIGARUDA kernel: NVRM: Xid (PCI:0000:01:00): 31, pid=8254, Ch 00000060, intr 10000000. MMU Fault: ENGINE HOST0 HUBCLIENT_HOST_CPU faulted @ 0x1_041fc000. Fault is of type FAULT_PTE ACCESS_TYPE_WRITE
feb 08 07:54:32 MSIGARUDA kernel: NVRM: Xid (PCI:0000:01:00): 31, pid=8254, Ch 00000060, intr 10000000. MMU Fault: ENGINE HOST0 HUBCLIENT_HOST_CPU faulted @ 0x1_041fc000. Fault is of type FAULT_PTE ACCESS_TYPE_WRITE
feb 08 07:54:32 MSIGARUDA kernel: NVRM: Xid (PCI:0000:01:00): 31, pid=8254, Ch 00000060, intr 10000000. MMU Fault: ENGINE HOST0 HUBCLIENT_HOST_CPU faulted @ 0x1_041fc000. Fault is of type FAULT_PTE ACCESS_TYPE_WRITE
feb 08 07:54:32 MSIGARUDA kernel: NVRM: Xid (PCI:0000:01:00): 31, pid=8254, Ch 00000060, intr 10000000. MMU Fault: ENGINE HOST0 HUBCLIENT_HOST_CPU faulted @ 0x1_041fc000. Fault is of type FAULT_PTE ACCESS_TYPE_WRITE
feb 08 07:57:52 MSIGARUDA nmbd[1900]: [2022/02/08 07:57:52.128030,  0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2)
feb 08 07:57:52 MSIGARUDA nmbd[1900]:   *****
feb 08 07:57:52 MSIGARUDA nmbd[1900]: 
feb 08 07:57:52 MSIGARUDA nmbd[1900]:   Samba name server MSIGARUDA is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.72
feb 08 07:57:52 MSIGARUDA nmbd[1900]: 
feb 08 07:57:52 MSIGARUDA nmbd[1900]:   *****
feb 08 11:17:27 MSIGARUDA kernel: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers
feb 08 11:17:27 MSIGARUDA kernel: CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers
feb 08 07:53:50 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 08 07:53:50 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 08 07:53:50 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 08 07:53:50 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 08 07:53:50 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 08 07:53:50 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 08 07:54:31 MSIGARUDA kernel: NVRM: GPU at PCI:0000:01:00: GPU-63f4bd47-9605-c863-2296-278181802e42
feb 08 07:54:31 MSIGARUDA kernel: NVRM: Xid (PCI:0000:01:00): 31, pid=8254, Ch 00000060, intr 10000000. MMU Fault: ENGINE HOST0 HUBCLIEN>
feb 08 07:54:31 MSIGARUDA kernel: NVRM: Xid (PCI:0000:01:00): 31, pid=8254, Ch 00000060, intr 10000000. MMU Fault: ENGINE HOST0 HUBCLIEN>
feb 08 07:54:32 MSIGARUDA kernel: NVRM: Xid (PCI:0000:01:00): 31, pid=8254, Ch 00000060, intr 10000000. MMU Fault: ENGINE HOST0 HUBCLIEN>
feb 08 07:54:32 MSIGARUDA kernel: NVRM: Xid (PCI:0000:01:00): 31, pid=8254, Ch 00000060, intr 10000000. MMU Fault: ENGINE HOST0 HUBCLIEN>
feb 08 07:54:32 MSIGARUDA kernel: NVRM: Xid (PCI:0000:01:00): 31, pid=8254, Ch 00000060, intr 10000000. MMU Fault: ENGINE HOST0 HUBCLIEN>
feb 07 22:04:17 MSIGARUDA kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
feb 07 22:04:17 MSIGARUDA kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
feb 07 22:04:17 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 07 22:04:17 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 07 22:04:17 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 07 22:04:17 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 07 22:04:17 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 07 22:04:17 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 07 22:04:18 MSIGARUDA systemd-tmpfiles[472]: Failed to write file "/sys/module/pcie_aspm/parameters/policy": Operation not permitted
feb 07 22:04:22 MSIGARUDA nmbd[595]: [2022/02/07 22:04:22.615880,  0] ../../source3/nmbd/nmbd.c:901(main)
feb 07 22:04:22 MSIGARUDA nmbd[595]:   nmbd version 4.15.4 started.
feb 07 22:04:22 MSIGARUDA nmbd[595]:   Copyright Andrew Tridgell and the Samba Team 1992-2021
feb 07 22:04:22 MSIGARUDA libvirtd[540]: cannot open directory '/run/media/jurosic_park/DISK M-PC': No such file or directory
feb 07 22:04:22 MSIGARUDA libvirtd[540]: internal error: Failed to autostart storage pool 'DISK_M-PC': cannot open directory '/run/media/jurosic_park/DISK M-PC': No such file or directory
feb 07 22:04:22 MSIGARUDA libvirtd[540]: cannot open directory '/run/media/jurosic_park/2ndSSD/VMs': No such file or directory
feb 07 22:04:22 MSIGARUDA libvirtd[540]: internal error: Failed to autostart storage pool '2ndSSD': cannot open directory '/run/media/jurosic_park/2ndSSD/VMs': No such file or directory
feb 07 22:04:22 MSIGARUDA smbd[601]: [2022/02/07 22:04:22.709276,  0] ../../source3/smbd/server.c:1734(main)
feb 07 22:04:22 MSIGARUDA smbd[601]:   smbd version 4.15.4 started.
feb 07 22:04:22 MSIGARUDA smbd[601]:   Copyright Andrew Tridgell and the Samba Team 1992-2021
feb 07 22:04:23 MSIGARUDA kernel: 
feb 07 22:04:23 MSIGARUDA kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  495.46  Wed Oct 27 16:31:33 UTC 2021
feb 07 22:04:33 MSIGARUDA sddm-helper[4024]: gkr-pam: unable to locate daemon control file
feb 07 22:04:38 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 07 22:04:38 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 07 22:04:38 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 07 22:04:38 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 07 22:04:38 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 07 22:04:38 MSIGARUDA kernel: Bluetooth: hci0: Failed to read codec capabilities (-56)
feb 07 22:04:45 MSIGARUDA nmbd[595]: [2022/02/07 22:04:45.531813,  0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2)
feb 07 22:04:45 MSIGARUDA nmbd[595]:   *****
feb 07 22:04:45 MSIGARUDA nmbd[595]: 
feb 07 22:04:45 MSIGARUDA nmbd[595]:   Samba name server MSIGARUDA is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.72
feb 07 22:04:45 MSIGARUDA nmbd[595]: 
feb 07 22:04:45 MSIGARUDA nmbd[595]:   *****
4

You should have said which program and that you mean opening from a task entry in the dock (if I understand well).
If so, delete the task/shortcut and try again.

I asked specifically if opening the same program with a non-latte method, because I wonder how can you do that. kRunner?
Kickof applications menu is still on latte…

A latte task icon keeps the path of the program/file from the moment you save it. If the file is on a removable media, that media maybe lost (temporarilly?) while suspending.

Is this related to your program?

4 Likes
5

Sorry, i wasn't thorough enough, it happens if i launch ANY program from the dock, and no it isn't, that's because my 2ndSSD doesn't automatically mount at boot, as you can see libvirtd is displaying that message because on launch it cannot find my second drive, as it is not mounted.

6

Edit your fstab and mount it at boot.

4 Likes
7 
man fstab

Or, simply search fstab on the forum for information.

You can also use systemd mount/automount units to do exactly the same thing.

The Archwiki contains tons of information on both methods.

2 Likes
8

The drive isnt causing the freeze, i know that for sure, it was happening even before i got it.

9

Still waiting for an answer on how do you start programs that don’t freeze your system?.

Did you try deleting task icons and recreate them?
What happens when you start programs from Applications menu (kickoff)?

3 Likes
10

Sorry for the late response, ive been busy with school and forgot about this thread.

I launch them from the terminal or from the application "start" menu.

11

I too have the same issue. While troubleshooting, I've made some finding if you find it useful.

  1. It never freezes if you load from Plasma Search (KRunner)
  2. Also this occurs only when launching GTK Apps.
  3. This can be reproduced if you try to load 3 consecutive GTK programs when there is relatively heavy system load, typically immediately after rebooting.
    It freezes immediately on clicking the 3rd Application.
  4. SysRq (magic keys) don't work when the system freezes with this issue.
  5. The freeze is almost absent if there is even a single QT based window open on screen.
  6. while trying to debug this the konsole terminal window was open (QT App) so it was impossible to get it to freeze. I've only ever got it to freeze once while having the debug window open, the last output on the debug console was "...indicatorlevel.qml: Unable to assign [undefined] to double." which doesn't seem relevant and looked like the system froze before the application could output any information.
4 Likes
12

Exactly what in encountering!

13

Really strange that this is not reproduced with plasma default panels and taskmanagers. Latte does not use any unique codepath to execute applications. It uses plasma default infrastructure for this through: plasma-workspace/libtaskmanager at master · KDE/plasma-workspace · GitHub

2 Likes
14

It is very weird, ive had this problem with default stuff too, i remember it would lock up my system even after a fresh install.

15

Meanwhile, I've tried some stuff to troubleshoot with no solution. I use a Radeon card BTW with a triple monitor setup.

  1. Tried the non-git version.
  2. Tried the default dock and panel layouts.
  3. Disabled all unnecessary mounts on fstab.
  4. Disabled compositor
  5. Tried both AMD & ATI drivers on Xorg conf
  6. Disabled all additional monitors

None of them seemed to affect it in any way.
Also by any chance is the most frequent lockup while launching firefox or thunderbird ?

16

Yeah, usually when launching apps that have a spike in cpu usage, like electron apps, browsers, but ive also noticed it just lock up by itself sometimes, less frequently, but it does happen, its very weird and kinda annoying..

EDIT: Forgot to add the fact that it seem to happen more commonly if you move your mouse sharply right after you launch something

17

You might want to Check to see if it does this on the live image to rule out hardware

3 Likes
18

I would like to add another potential aspect to check for possible effect.

Does this happen on systems with more than one desktop environment installed?

The reason is that DEs usually provide their own specific configuration daemons, that autostart by default and few of them act on the same context, like dbus, security/keyring, tracker etc., no matter if you just login into one DE, so it might some times conflict.

2 Likes
19

As far as i know i only have the Plasma desktop enviroment.

20

Forgot to add the fact that it seem to happen more commonly if you move your mouse sharply right after you launch something

Lol, I too have a mouse flick action after launch but surely that can’t be a cause.

You might want to Check to see if it does this on the live image to rule out hardware

Will be trying that out soon.

Does this happen on systems with more than one desktop environment installed?

I didn’t have any other DE. But now I just installed wayland and tried to see if using that solves this issue… but no dice.

Also another thing I noticed, if you crash it enough times consecutively, a lot of KWin settings get reset. Especially the KDE “Window Decorations” and the Keyboard Shortcuts as well as defaulting the dock panel layout.

Also if anyone knows of a more verbose debug option for latte-dock, it would be helpful. As it stands the system locks up before any usable output. Can’t even figure out which stage of the action cause the lockup. So its impossible to report this without sounding silly.