Nemo stops responding

Desktop Environments Cinnamon
1

Hi - I’ve been running EOS with Cinnamon on my laptop for about 6 months. Lately, it’s developed an annoying random issue where Nemo stops responding. When I try to start it from the terminal, I get
$ nemo
Could not register nemo as a remote: Timeout was reached
I check the log with journalctl --since “XX minutes ago”, but don’t see anything out of the ordinary.
However, about 5 min. later, a Nemo window pops up on my screen and works normally.

I’ve tried:
logging out of my session and back in with
$sudo systemctl restart lightdm
but Nemo is still unresponsive
restarting x with
$ sudo pkill x
but Nemo is still unresponsive

If I change to being the super user, Nemo works fine.

System:
$ inxi -Fxxc0z
System:
Kernel: 6.15.2-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 15.1.1
Desktop: Cinnamon v: 6.4.10 tk: GTK v: 3.24.49 wm: Muffin dm: LightDM
Distro: EndeavourOS base: Arch Linux
Machine:
Type: Convertible System: LENOVO product: 83DJ v: Yoga 7 2-in-1 14IML9
serial: Chassis: type: 31 v: Yoga 7 2-in-1 14IML9
serial:
Mobo: LENOVO model: LNVNB161216 v: SDK0T76463 WIN
serial: part-nu: LENOVO_MT_83DJ_BU_idea_FM_Yoga 7
2-in-1 14IML9 UEFI: LENOVO v: NWCN15WW date: 03/13/2024
Battery:
ID-1: BAT0 charge: 57.6 Wh (79.4%) condition: 72.5/71.0 Wh (102.1%)
volts: 16.3 min: 15.4 model: SMP L22M4PA1 serial:
status: not charging
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M325
serial: charge: 55% (should be ignored) status: discharging
CPU:
Info: 12-core (2-mt/10-st) model: Intel Core Ultra 5 125U bits: 64
type: MST AMCP arch: Meteor Lake rev: 4 cache: L1: 992 KiB L2: 10 MiB
L3: 12 MiB
Speed (MHz): avg: 400 min/max: 400/4300:3600:2100 cores: 1: 400 2: 400
3: 400 4: 400 5: 400 6: 400 7: 400 8: 400 9: 400 10: 400 11: 400 12: 400
13: 400 14: 400 bogomips: 75264
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
Device-1: Intel Meteor Lake-P [Intel Graphics] vendor: Lenovo driver: i915
v: kernel arch: Xe-LPG ports: active: HDMI-A-1,eDP-1
empty: DP-1, DP-2, DP-3, DP-4 bus-ID: 00:02.0 chip-ID: 8086:7d45
Device-2: Chicony Integrated Camera driver: uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 bus-ID: 3-9:4 chip-ID: 04f2:b7e8
Display: x11 server: X.Org v: 21.1.17 with: Xwayland v: 24.1.7 driver: X:
loaded: modesetting alternate: fbdev,intel,vesa dri: iris gpu: i915
display-ID: :0 screens: 1
Screen-1: 0 s-res: 3840x3360 s-dpi: 96
Monitor-1: HDMI-A-1 mapped: HDMI-1 pos: top-left
model: Philips PHL 272P7VU res: N/A dpi: 163 diag: 685mm (27")
Monitor-2: eDP-1 pos: primary,bottom-r model: ChiMei InnoLux 0x143f
res: 1920x1200 hz: 60 dpi: 162 diag: 355mm (14")
API: EGL v: 1.5 platforms: device: 0 drv: iris device: 1 drv: swrast gbm:
drv: iris surfaceless: drv: iris x11: drv: iris inactive: wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.1.3-arch1.3
glx-v: 1.4 direct-render: yes renderer: Mesa Intel Graphics (MTL)
device-ID: 8086:7d45
API: Vulkan Message: No Vulkan data available.
Info: Tools: api: eglinfo, glxinfo, vulkaninfo
x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Intel Meteor Lake-P HD Audio vendor: Lenovo
driver: sof-audio-pci-intel-mtl bus-ID: 00:1f.3 chip-ID: 8086:7e28
API: ALSA v: k6.15.2-arch1-1 status: kernel-api
Server-1: PipeWire v: 1.4.5 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin
Network:
Device-1: Intel Meteor Lake PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:7e40
IF: wlan0 state: up mac:
Bluetooth:
Device-1: Intel AX211 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 bus-ID: 3-10:5 chip-ID: 8087:0033
Report: btmgmt ID: hci0 rfk-id: 2 state: up address: N/A
Drives:
Local Storage: total: 953.87 GiB used: 97.88 GiB (10.3%)
ID-1: /dev/nvme0n1 model: P41PL NVMe SOLIDIGM 1024GB size: 953.87 GiB
speed: 63.2 Gb/s lanes: 4 serial: temp: 36.9 C
Partition:
ID-1: / size: 58.96 GiB used: 21.76 GiB (36.9%) fs: ext4 dev: /dev/nvme0n1p5
ID-2: /home size: 865.7 GiB used: 13.45 GiB (1.6%) fs: ext4
dev: /dev/nvme0n1p1
Swap:
ID-1: swap-1 type: partition size: 9.77 GiB used: 1.66 GiB (17.0%)
priority: -2 dev: /dev/nvme0n1p4
Sensors:
Src: /sys System Temperatures: cpu: 45.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 16 GiB note: est. available: 15.23 GiB used: 5.16 GiB (33.9%)
Processes: 348 Power: uptime: 2d 22h 33m wakeups: 0 Init: systemd v: 257
default: graphical
Packages: pm: pacman pkgs: 1353 Compilers: gcc: 15.1.1 Shell: Bash
v: 5.2.37 running-in: gnome-terminal inxi: 3.3.38

Any thoughts on what I can try to prevent Nemo from going unresponsive, or get it to restart faster?
Thanks!

2

I’ve only ever seen that with (auto-)mounted remote NAS volumes

  • when an already mounted volume “went away” (disconnected for whatever reason)
  • when the NAS connection was on a slow/flakey connection (WiFi, low speed, VPN with wrong MTU, etc.)
  • when the NAS volumes holds many folders & files (Nemo takes forever, apparently recursively checking all to find the total size)
  • on badly configured NFS shares (NFS defaults to 10000 retries, multiplied by however many retries the file manager uses internally; I typically set retry=1)
3

are there any hints in the ‘looking glass’?

4

A quick search reveals that Linux Mint and Manjaro users have had problems like this with

  • megasync
  • dropbox
  • keybase
5

It’s been over a year since I used Nemo on Arch Cinamon, and I had MegaSync working fine on that install. Do you have nemo-megasync installed?

6

I do not have nemo-megasync installed. I do use PCloud and Koofr for cloud storage and backup. Backup software is Duplicati.

It just occurred again and this is the log:

$ journalctl --since “10 minutes ago”
Jun 28 14:26:32 lenovo-y rtkit-daemon[1141]: Supervising 0 threads of 0 processes of 0 users.
Jun 28 14:26:32 lenovo-y rtkit-daemon[1141]: Supervising 0 threads of 0 processes of 0 users.
Jun 28 14:26:37 lenovo-y rtkit-daemon[1141]: Supervising 0 threads of 0 processes of 0 users.
Jun 28 14:26:37 lenovo-y rtkit-daemon[1141]: Supervising 0 threads of 0 processes of 0 users.
Jun 28 14:27:34 lenovo-y rtkit-daemon[1141]: Supervising 0 threads of 0 processes of 0 users.
Jun 28 14:27:34 lenovo-y rtkit-daemon[1141]: Supervising 0 threads of 0 processes of 0 users.
Jun 28 14:29:34 lenovo-y rtkit-daemon[1141]: Supervising 0 threads of 0 processes of 0 users.
Jun 28 14:29:34 lenovo-y rtkit-daemon[1141]: Supervising 0 threads of 0 processes of 0 users.
Jun 28 14:29:58 lenovo-y wpa_supplicant[809]: wlan0: RSN: Group rekeying completed with a0:36:bc:e4:67:84 [GTK=CCMP]
Jun 28 14:30:38 lenovo-y rtkit-daemon[1141]: Supervising 0 threads of 0 processes of 0 users.
Jun 28 14:30:38 lenovo-y rtkit-daemon[1141]: Supervising 0 threads of 0 processes of 0 users.
Jun 28 14:31:42 lenovo-y rtkit-daemon[1141]: Supervising 0 threads of 0 processes of 0 users.
Jun 28 14:31:42 lenovo-y rtkit-daemon[1141]: Supervising 0 threads of 0 processes of 0 users.
Jun 28 14:31:46 lenovo-y gvfsd[149493]: Error 2: PTP Layer error 02ff: Error getting friendlyname.
Jun 28 14:31:46 lenovo-y gvfsd[149493]: Error 2: Error 02ff: PTP I/O Error
Jun 28 14:31:46 lenovo-y gvfsd[149493]: Error 2: PTP Layer error 02ff: Error getting friendlyname.
Jun 28 14:31:46 lenovo-y gvfsd[149493]: Error 2: Error 02ff: PTP I/O Error
Jun 28 14:31:46 lenovo-y gvfsd[149493]: Error 2: PTP Layer error 02ff: Error getting friendlyname.
Jun 28 14:31:46 lenovo-y gvfsd[149493]: Error 2: Error 02ff: PTP I/O Error
Jun 28 14:31:46 lenovo-y gvfsd[149493]: Error 2: PTP Layer error 02ff: Error getting friendlyname.
Jun 28 14:31:46 lenovo-y gvfsd[149493]: Error 2: Error 02ff: PTP I/O Error
Jun 28 14:31:46 lenovo-y gvfsd[149493]: Error 2: PTP Layer error 02ff: Error getting friendlyname.
Jun 28 14:31:46 lenovo-y gvfsd[149493]: Error 2: Error 02ff: PTP I/O Error
Jun 28 14:31:46 lenovo-y gvfsd[149493]: Error 2: PTP Layer error 02ff: Error getting friendlyname.
Jun 28 14:31:46 lenovo-y gvfsd[149493]: Error 2: Error 02ff: PTP I/O Error
Jun 28 14:31:46 lenovo-y gvfsd[149493]: Error 2: PTP Layer error 02ff: Error getting friendlyname.
Jun 28 14:31:46 lenovo-y gvfsd[149493]: Error 2: Error 02ff: PTP I/O Error
Jun 28 14:31:46 lenovo-y gvfsd[149493]: Error 2: PTP Layer error 02ff: Error getting friendlyname.
Jun 28 14:31:46 lenovo-y gvfsd[149493]: Error 2: Error 02ff: PTP I/O Error
Jun 28 14:31:46 lenovo-y gvfsd[149493]: Error 2: PTP Layer error 02ff: Error getting friendlyname.
Jun 28 14:31:46 lenovo-y gvfsd[149493]: Error 2: Error 02ff: PTP I/O Error
Jun 28 14:31:46 lenovo-y gvfsd[149493]: Error 2: PTP Layer error 02ff: Error getting friendlyname.
Jun 28 14:31:46 lenovo-y gvfsd[149493]: Error 2: Error 02ff: PTP I/O Error
Jun 28 14:33:23 lenovo-y rtkit-daemon[1141]: Supervising 0 threads of 0 processes of 0 users.
Jun 28 14:33:23 lenovo-y rtkit-daemon[1141]: Supervising 0 threads of 0 processes of 0 users.
Jun 28 14:33:46 lenovo-y gvfsd[149493]: Error 2: PTP Layer error 02ff: Error getting friendlyname.
Jun 28 14:33:46 lenovo-y gvfsd[149493]: Error 2: Error 02ff: PTP I/O Error
Jun 28 14:34:34 lenovo-y rtkit-daemon[1141]: Supervising 0 threads of 0 processes of 0 users.
Jun 28 14:34:34 lenovo-y rtkit-daemon[1141]: Supervising 0 threads of 0 processes of 0 users.

7

I can only guess (not using all of these, only Nextcloud and TrueNAS over NFS) but it looks like the GNOME Virtual File System Daemon gvfsd reports connection problems. This may (or may not) be caused by the wlan0 CCPM rekeying (IPv6 sometimes change addresses), or just be some bug in Pcloud or Koofr.

I’d suggest disabling both, then check if it still happens, then turn on only one of them (testing both, of course), and check again.

If you find anything reproducible, you could report it to their issue trackers.

8

It will probably take some time, few days?, but it gives me a path to follow. Thanks!!

9

I’ve deactivated pCloud and Koofr cloud storage, and paused my backup service Duplicati. However, I just had another incident of Nemo not responding. The logs are as follows:

$ journalctl --since “40 minutes ago”
Jun 29 10:45:44 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:45:44 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:46:36 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:46:36 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:47:27 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:47:27 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:47:42 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:47:42 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:47:46 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:47:46 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:50:03 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:50:03 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:52:20 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:52:20 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:53:00 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:53:00 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:53:59 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:53:59 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:54:58 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:54:58 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:55:25 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:55:25 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:55:27 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:55:27 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:55:44 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:55:44 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:56:39 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:56:39 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:57:28 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:57:28 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:59:04 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:59:04 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:59:06 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:59:06 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:59:06 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:59:06 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:59:06 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:59:06 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:59:08 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:59:08 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:59:19 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:59:19 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:59:21 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:59:21 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:59:21 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 10:59:21 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 11:00:23 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 11:00:23 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 11:01:32 lenovo-y systemd-timesyncd[481]: Contacted time server 172.235.32.243:123 (0.arch.pool.ntp.org).
Jun 29 11:01:42 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 11:01:42 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 11:01:42 lenovo-y rtkit-daemon[1141]: Successfully made thread 249279 of process 248215 owned by ‘1000’ RT at priority 10.
Jun 29 11:01:42 lenovo-y rtkit-daemon[1141]: Supervising 2 threads of 2 processes of 1 users.
Jun 29 11:02:25 lenovo-y rtkit-daemon[1141]: Supervising 2 threads of 2 processes of 1 users.
Jun 29 11:02:25 lenovo-y rtkit-daemon[1141]: Supervising 2 threads of 2 processes of 1 users.
Jun 29 11:02:27 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 11:02:27 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 11:03:19 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 11:03:19 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 11:03:43 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 11:03:43 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 11:04:14 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 11:04:14 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 11:04:17 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 11:04:17 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 11:04:25 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 11:04:25 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 11:05:47 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 11:05:47 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 11:05:49 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 11:05:49 lenovo-y rtkit-daemon[1141]: Supervising 1 threads of 1 processes of 1 users.
Jun 29 11:05:49 lenovo-y rtkit-daemon[1141]: Successfully made thread 250588 of process 4949 owned by ‘1000’ RT at priority 10.
Jun 29 11:05:49 lenovo-y rtkit-daemon[1141]: Supervising 2 threads of 2 processes of 1 users.
Jun 29 11:07:28 lenovo-y rtkit-daemon[1141]: Supervising 2 threads of 2 processes of 1 users.
Jun 29 11:07:28 lenovo-y rtkit-daemon[1141]: Supervising 2 threads of 2 processes of 1 users.
Jun 29 11:07:57 lenovo-y rtkit-daemon[1141]: Supervising 2 threads of 2 processes of 1 users.
Jun 29 11:07:57 lenovo-y rtkit-daemon[1141]: Supervising 2 threads of 2 processes of 1 users.
Jun 29 11:10:27 lenovo-y rtkit-daemon[1141]: Supervising 2 threads of 2 processes of 1 users.
Jun 29 11:10:27 lenovo-y rtkit-daemon[1141]: Supervising 2 threads of 2 processes of 1 users.
Jun 29 11:11:57 lenovo-y rtkit-daemon[1141]: Supervising 2 threads of 2 processes of 1 users.
Jun 29 11:11:57 lenovo-y rtkit-daemon[1141]: Supervising 2 threads of 2 processes of 1 users.
Jun 29 11:12:28 lenovo-y rtkit-daemon[1141]: Supervising 2 threads of 2 processes of 1 users.
Jun 29 11:12:28 lenovo-y rtkit-daemon[1141]: Supervising 2 threads of 2 processes of 1 users.
Jun 29 11:13:36 lenovo-y rtkit-daemon[1141]: Supervising 2 threads of 2 processes of 1 users.
Jun 29 11:13:36 lenovo-y rtkit-daemon[1141]: Supervising 2 threads of 2 processes of 1 users.
Jun 29 11:14:29 lenovo-y rtkit-daemon[1141]: Supervising 2 threads of 2 processes of 1 users.
Jun 29 11:14:29 lenovo-y rtkit-daemon[1141]: Supervising 2 threads of 2 processes of 1 users.
Jun 29 11:15:48 lenovo-y rtkit-daemon[1141]: Supervising 2 threads of 2 processes of 1 users.
Jun 29 11:15:48 lenovo-y rtkit-daemon[1141]: Supervising 2 threads of 2 processes of 1 users.
Jun 29 11:16:29 lenovo-y rtkit-daemon[1141]: Supervising 2 threads of 2 processes of 1 users.
Jun 29 11:16:29 lenovo-y rtkit-daemon[1141]: Supervising 2 threads of 2 processes of 1 users.
Jun 29 11:18:08 lenovo-y rtkit-daemon[1141]: Supervising 2 threads of 2 processes of 1 users.
Jun 29 11:18:08 lenovo-y rtkit-daemon[1141]: Supervising 2 threads of 2 processes of 1 users.
Jun 29 11:18:08 lenovo-y rtkit-daemon[1141]: Supervising 2 threads of 2 processes of 1 users.
Jun 29 11:18:08 lenovo-y rtkit-daemon[1141]: Supervising 2 threads of 2 processes of 1 users.
Jun 29 11:18:16 lenovo-y rtkit-daemon[1141]: Supervising 2 threads of 2 processes of 1 users.
Jun 29 11:18:16 lenovo-y rtkit-daemon[1141]: Supervising 2 threads of 2 processes of 1 users.
Jun 29 11:19:24 lenovo-y rtkit-daemon[1141]: Supervising 2 threads of 2 processes of 1 users.
Jun 29 11:19:24 lenovo-y rtkit-daemon[1141]: Supervising 2 threads of 2 processes of 1 users.

an other thoughts?

10

I still don’t know the reason why this happens, but I’ve discovered the cause. The issue randomly occurs when I have my cell phone mounted by it being plugged into the USB C port. When the issue happens, unplugging the phone resolves the issue immediately.

11

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.