Locking session makes Dolphin unusable (huge delay for every click)

asormanni · 16 October 2022 17:49

Hello,
i’m experiencing this problem with Dolphin: big delay even for closing the app

System: Manjaro KDE fully updated with stable branch, Wayland, Intel GPU with open source drivers, no network shared mounted, 1 USB drive always mounted, no system suspension or hybernation configured.

Behaviour:

when session starts, after system boot and SDDM login → Dolphin runs normally until the session is locked (manually or if timeout expires)
after session locking → Dolphin becomes completely unusable, with a 30 secs delay for every operation performed, until logout.
logout → Dolphin normal behaviour immediatly restored, until next session locking

Only Dolphin has the problem, every other KDE app or Plasma behaves normally even after session locking.

As a workaround, i’ve disabled completely session locking (home PC, security is not a problem (maybe… ), but would like to fix the root cause.

Any idea ? Some info here:

hostnamectl                                                                      Static hostname: fujitsu
       Icon name: computer-server
         Chassis: server 🖳
      Machine ID: 6d58c8d784a543e48de48cc977584765
         Boot ID: 7fe4e9e89f914f87adf208afad7b062f
Operating System: Manjaro Linux                                     
          Kernel: Linux 5.19.0-3-rt10-MANJARO
    Architecture: x86-64
 Hardware Vendor: FUJITSU
  Hardware Model: PRIMERGY TX1310 M3
Firmware Version: V5.0.0.11 R1.29.0 for D3521-A1x

System:
  Kernel: 5.19.0-3-rt10-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: root="UUID=91e2b4dc-f17a-4f58-9199-180c75043a93" rw reboot=efi
    vt.global_cursor_default=0 loglevel=3 udev.log-priority=3 splash
    usbcore.autosuspend=5 audit=0 preempt=full
  Console: pty pts/2 DM: SDDM Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Server System: FUJITSU product: PRIMERGY TX1310 M3 v: N/A
    serial: <filter> Chassis: type: 17 v: TX1310M3 serial: <filter>
  Mobo: FUJITSU model: D3521-A1 v: S26361-D3521-A13 serial: <filter>
    UEFI: FUJITSU // American Megatrends v: 5.0.0.11 R1.29.0 for D3521-A1x
    date: 12/22/2021
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard K360
    serial: <filter> charge: 55% (should be ignored) rechargeable: yes
    status: discharging
  Device-2: hidpp_battery_1 model: Logitech Wireless Mouse MX Master 3
    serial: <filter> charge: 55% (should be ignored) rechargeable: yes
    status: discharging
Memory:
  RAM: total: 39.01 GiB used: 2.53 GiB (6.5%)
  Array-1: capacity: 64 GiB slots: 4 EC: Single-bit ECC
    max-module-size: 16 GiB note: est.
  Device-1: DIMM CHA3 type: DDR4 detail: synchronous size: 8 GiB
    speed: 2400 MT/s volts: curr: 1.2 min: 1.2 max: 1.2 width (bits): data: 64
    total: 72 manufacturer: SK Hynix part-no: HMA81GU7AFR8N-UH
    serial: <filter>
  Device-2: DIMM CHA1 type: no module installed
  Device-3: DIMM CHB4 type: DDR4 detail: synchronous size: 16 GiB
    speed: 2400 MT/s volts: curr: 1.2 min: 1.2 max: 1.2 width (bits): data: 64
    total: 72 manufacturer: 0000 part-no: N/A serial: <filter>
  Device-4: DIMM CHB2 type: DDR4 detail: synchronous size: 16 GiB
    speed: 2400 MT/s volts: curr: 1.2 min: 1.2 max: 1.2 width (bits): data: 64
    total: 72 manufacturer: 0000 part-no: N/A serial: <filter>
CPU:
  Info: model: Intel Xeon E3-1225 v6 bits: 64 type: MCP arch: Kaby Lake
    level: v3 note: check built: 2018 process: Intel 14nm family: 6
    model-id: 0x9E (158) stepping: 9 microcode: 0xF0
  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: 8 MiB
    desc: 1x8 MiB
  Speed (MHz): avg: 1569 high: 3300 min/max: 800/3700 base/boost: 3300/3700
    scaling: driver: intel_pstate governor: powersave volts: 1.0 V
    ext-clock: 100 MHz cores: 1: 1000 2: 978 3: 3300 4: 1000 bogomips: 26399
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_perfmon art avx avx2 bmi1 bmi2 bts clflush
    clflushopt cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64
    dtherm dts epb ept ept_ad erms est f16c flexpriority flush_l1d fma fpu
    fsgsbase fxsr ht hwp hwp_act_window hwp_epp hwp_notify ibpb ibrs ida
    intel_pt invpcid invpcid_single lahf_lm lm mca mce md_clear mmx monitor
    movbe mpx msr mtrr nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm
    pdpe1gb pebs pge pln pni popcnt pse pse36 pti pts rdrand rdseed rdtscp
    rep_good sdbg sep smap smep smx ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp
    syscall tm tm2 tpr_shadow tsc tsc_adjust tsc_deadline_timer vme vmx vnmi
    vpid x2apic xgetbv1 xsave xsavec xsaveopt xsaves xtopology xtpr
  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: mmio_stale_data mitigation: Clear CPU buffers; SMT disabled
  Type: retbleed mitigation: IBRS
  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: IBRS, IBPB: conditional, RSB filling
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort mitigation: TSX disabled
Graphics:
  Device-1: Intel HD Graphics P630 vendor: Fujitsu Solutions driver: i915
    v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports:
    active: HDMI-A-2 empty: DP-1, DP-2, DP-3, HDMI-A-1, HDMI-A-3
    bus-ID: 00:02.0 chip-ID: 8086:591d class-ID: 0300
  Display: server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.3
    compositor: kwin_wayland driver: X: loaded: modesetting
    alternate: fbdev,vesa dri: iris gpu: i915 tty: 111x32
  Monitor-1: HDMI-A-2 model: LG (GoldStar) 2D FHD TV serial: <filter>
    built: 2017 res: 1920x1080 dpi: 96 gamma: 1.2 size: 509x286mm (20.04x11.26")
    diag: 584mm (23") ratio: 16:9 modes: max: 1920x1080 min: 720x400
  Message: GL data unavailable in console for root.
Audio:
  Device-1: Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series]
    driver: snd_hda_intel v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
    bus-ID: 01:00.0 chip-ID: 1102:0012 class-ID: 0403
  Sound API: ALSA v: k5.19.0-3-rt10-MANJARO running: yes
  Sound Interface: sndio v: N/A running: no
  Sound Server-1: PulseAudio v: 16.1 running: no
  Sound Server-2: PipeWire v: 0.3.58 running: yes
Network:
  Device-1: Intel Ethernet I219-LM vendor: Fujitsu Solutions driver: e1000e
    v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b7 class-ID: 0200
  IF: eno2 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: docker0 state: down mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IF-ID-2: host132 state: down mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IF-ID-3: nat122 state: down mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IF-ID-4: phys0 state: up speed: 1000 Mbps duplex: unknown mac: <filter>
  IP v4: <filter> type: noprefixroute scope: global broadcast: <filter>
  IF-ID-5: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A
  Message: Output throttled. IPs: 2; Limit: 10; Override: --limit [1-x;-1
    all]
  WAN IP: <filter>
Bluetooth:
  Message: No bluetooth data found.
Logical:
  Device-1: VG: os type: LVM2 size: 1.32 TiB free: 0 KiB
  LV-1: root maj-min: 253:1 type: linear dm: dm-1 size: 1.32 TiB
  Components:
  c-1: md126p6 maj-min: 259:5 size: 1.32 TiB
  LV-2: swap maj-min: 253:0 type: linear dm: dm-0 size: 512 MiB
  Components:
  c-1: md126p6 maj-min: 259:5 size: 1.32 TiB
RAID:
  Hardware-1: Intel Q170/H170/Z170/CM236 SATA Controller [RAID Mode]
    driver: ahci v: 3.0 port: f060 bus-ID: 00:17.0 chip-ID: 8086:a106 rev: N/A
    class-ID: 0104
  Supported mdraid levels: raid0
  Device-1: md126 maj-min: 9:126 type: mdraid level: raid-0 status: active
    state: clean size: 1.82 TiB
  Info: report: N/A blocks: 1949216768 chunk-size: 64k
  Components: Online:
  0: sdd maj-min: 8:48 size: 465.76 GiB state: active sync
  1: sdc maj-min: 8:32 size: 465.76 GiB state: active sync
  2: sdb maj-min: 8:16 size: 465.76 GiB state: active sync
  3: sda maj-min: 8:0 size: 465.76 GiB state: active sync
  Device-2: md127 maj-min: 9:127 type: mdraid level: N/A status: inactive
    size: N/A
  Info: report: N/A blocks: 4329568 chunk-size: N/A
  Components: Online: N/A Spare:
  0: sdd maj-min: 8:48 size: 465.76 GiB state: S
  1: sdc maj-min: 8:32 size: 465.76 GiB state: S
  2: sdb maj-min: 8:16 size: 465.76 GiB state: S
  3: sda maj-min: 8:0 size: 465.76 GiB state: S
Drives:
  Local Storage: total: raw: 2.73 TiB usable: 927.38 GiB used: 270.3 GiB
    (29.1%)
  ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 500GB
    family: based SSDs size: 465.76 GiB block-size: physical: 512 B
    logical: 512 B sata: 3.1 speed: 6.0 Gb/s type: SSD serial: <filter>
    rev: 1B6Q temp: 24 C
  SMART: yes state: enabled health: PASSED on: 324d 0h cycles: 1091
    written: 5.11 TiB
  ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 860 EVO 500GB
    family: based SSDs size: 465.76 GiB block-size: physical: 512 B
    logical: 512 B sata: 3.2 speed: 6.0 Gb/s type: SSD serial: <filter>
    rev: 3B6Q temp: 24 C
  SMART: yes state: enabled health: PASSED on: 322d 22h cycles: 1091
    written: 4.97 TiB Pre-Fail: reallocated sector: 98 threshold: 10
  ID-3: /dev/sdc maj-min: 8:32 vendor: Samsung model: SSD 860 EVO 500GB
    family: based SSDs size: 465.76 GiB block-size: physical: 512 B
    logical: 512 B sata: 3.2 speed: 6.0 Gb/s type: SSD serial: <filter>
    rev: 3B6Q temp: 26 C
  SMART: yes state: enabled health: PASSED on: 322d 22h cycles: 1091
    written: 5.05 TiB
  ID-4: /dev/sdd maj-min: 8:48 vendor: Samsung model: SSD 860 EVO 500GB
    family: based SSDs size: 465.76 GiB block-size: physical: 512 B
    logical: 512 B sata: 3.1 speed: 6.0 Gb/s type: SSD serial: <filter>
    rev: 1B6Q temp: 26 C
  SMART: yes state: enabled health: PASSED on: 324d 0h cycles: 1091
    written: 5.05 TiB
  ID-5: /dev/sde maj-min: 8:64 type: USB vendor: Seagate
    model: ST1000LM 014-1EJ164 drive model: ST1000LM014-1EJ164
    family: Laptop SSHD size: 931.51 GiB block-size: physical: 4096 B
    logical: 512 B sata: 3.1 speed: 6.0 Gb/s type: HDD rpm: 5400
    serial: <filter> drive serial: <filter> rev: SM36 temp: 28 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 3y 40d 19h cycles: 1311
    Pre-Fail: attribute: Spin_Retry_Count value: 100 worst: 100 threshold: 97
  Optical-1: /dev/sr0 vendor: HL-DT-ST model: DVDRAM GUD0N rev: PF02
    dev-links: cdrom
  Features: speed: 24 multisession: yes audio: yes dvd: yes
    rw: cd-r,cd-rw,dvd-r,dvd-ram state: running
Partition:
  ID-1: / raw-size: 1.32 TiB size: 1.3 TiB (98.35%) used: 270.23 GiB (20.3%)
    fs: ext4 block-size: 4096 B dev: /dev/dm-1 maj-min: 253:1 mapped: os-root
    label: N/A uuid: N/A
  ID-2: /boot/efi raw-size: 2 GiB size: 1.99 GiB (99.80%) used: 73.9 MiB
    (3.6%) fs: vfat block-size: 512 B dev: /dev/md126p1 maj-min: 259:0
    label: N/A uuid: C1D0-9D5C
Swap:
  Kernel: swappiness: 10 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 512 MiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/dm-0 maj-min: 253:0 mapped: os-swap label: swap
    uuid: 2f7555d0-ed5c-42e2-bf52-5a0b99820e6d
Unmounted:
  ID-1: /dev/md126p2 maj-min: 259:1 size: 16 MiB fs: N/A label: N/A uuid: N/A
  ID-2: /dev/md126p3 maj-min: 259:2 size: 501.11 GiB fs: ntfs label: N/A
    uuid: 1E1061A41061841D
  ID-3: /dev/md126p4 maj-min: 259:3 size: 630 MiB fs: ntfs label: N/A
    uuid: 04A03B41A03B390E
  ID-4: /dev/md126p5 maj-min: 259:4 size: 559 MiB fs: ntfs label: N/A
    uuid: EA8AD6F58AD6BCEF
  ID-5: /dev/sde1 maj-min: 8:65 size: 931.51 GiB fs: ext4 label: N/A
    uuid: 2b59b0d5-8153-4309-aa80-ced408f816a6
USB:
  Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 16 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 1-1:2 info: Logitech Unifying Receiver type: Keyboard,Mouse,HID
    driver: logitech-djreceiver,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s
    power: 98mA chip-ID: 046d:c52b class-ID: 0300
  Hub-2: 2-0:1 info: Super-speed hub ports: 10 rev: 3.0 speed: 5 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
  Device-1: 2-6:3 info: VIA Labs VL817 SATA Adaptor type: Mass Storage
    driver: uas interfaces: 1 rev: 3.1 speed: 5 Gb/s power: 8mA
    chip-ID: 2109:0715 class-ID: 0806 serial: <filter>
Sensors:
  System Temperatures: cpu: 33.0 C pch: 38.5 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 238 Uptime: 5h 15m wakeups: 28 Init: systemd v: 251
  default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 11
  clang: 14.0.6 Packages: pm: pacman pkgs: 2185 libs: 485 tools: yay
  pm: flatpak pkgs: 0 Shell: Zsh (su) v: 5.9 running-in: pty pts/2
  inxi: 3.3.22

fbt89 · 16 October 2022 22:26

I’m kind of confused, I thought if a session is locked then nothing would work until I logged back in. Yet you say all applications except Dolphin work?

winnie · 17 October 2022 03:36

RT Kernel?

Wayland?

Does this issue occur if you use X11? A standard kernel? Both?

asormanni · 17 October 2022 14:56

No, i mean that once logged in back from screen locking, every other app or KDE element works as expected, olny dolphin has problems. If you logout from system, at next login everything starts working as normal (dolphin included).

Regards,
A.

asormanni · 17 October 2022 16:51

This occurs only on this system and only with Wayland. With X11, same RT kernel, no problem at all.

A fresh copy of Manjaro KDE installed on a vm (uefi, with plasma-wayland-session and updates added) has dolphin working correctly even with Wayland, so definively there is something wrong in this system configuration, but what ?

winnie · 17 October 2022 16:55

I know it’s not a “solution” in the truest sense, but can you live without Wayland for now?

asormanni · 17 October 2022 17:43

i think i’ve found the problem: a side-by-side comparison between my system and the working vm shows that i’ve 2 env variables active in /etc/environment that are causing problems:

QT_AUTO_SCREEN_SCALE_FACTOR=1
QT_QPA_PLATFORM=xcb

Commenting them out (as they were in the vm) make the system work properly, after a reboot.

To answer your question… yes, i can live without Wayland, but it’s a challenge.

Problem is solved, many thanks to all for helping me.

Regards,
A.

freggel.doe · 17 October 2022 19:23

I’m curious: “a challenge” in what sense?

asormanni · 18 October 2022 09:46

I’d like to understand what is the root cause of this dolphin behaviour.

system · 20 October 2022 23:47

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