Plasma-plasmashell.service apparently not starting

Hi Guys,

I’ve been, and am still sort of struggling with:

I though it was fixed, but then reality decided to throw a spanner in the works.

It would seem that plasma-plasmashell.service isn’t starting, or not starting correctly or something of the sort, because when I execute:

$ systemctl --user restart plasma-plasmashell.service

…it starts working. Yet, directly after booting it looks to be running:

$ systemctl --user status plasma-plasmashell.service
● plasma-plasmashell.service - KDE Plasma Workspace
     Loaded: loaded (/usr/lib/systemd/user/plasma-plasmashell.service; enabled; preset: enabled)
     Active: active (running) since Tue 2024-10-15 15:12:54 SAST; 3min 46s ago
 Invocation: 0fc53050460746fa8a482ba332666555
   Main PID: 989 (plasmashell)
      Tasks: 24 (limit: 18951)
     Memory: 470.6M (peak: 487.7M)
        CPU: 12.577s
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service
             └─989 /usr/bin/plasmashell --no-respawn

Oct 15 15:13:07 Mirdarthos-PC plasmashell[989]: file:///home/mirdarthos/.local/share/plasma/plasmoids/com.github.k-donn.plasmoid-wunderground/contents/ui/DetailsItem.qml:139:17: Unable to assign [undefined] to QString
Oct 15 15:13:07 Mirdarthos-PC plasmashell[989]: Loading Calendar plugin HolidaysEventsPlugin(0x55c1eb54d4c0)
Oct 15 15:13:07 Mirdarthos-PC plasmashell[989]: Loading Calendar plugin PimEventsPlugin(0x55c1eb558250)
Oct 15 15:13:07 Mirdarthos-PC kioworker[1696]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairRequested(QString)
Oct 15 15:13:07 Mirdarthos-PC kioworker[1696]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairDone(Solid::ErrorType, QVariant, QString)
Oct 15 15:13:07 Mirdarthos-PC plasmashell[989]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.iec958-stereo.monitor"
Oct 15 15:13:08 Mirdarthos-PC plasmashell[989]: qml: [debug] [main.qml] Weather data changed
Oct 15 15:13:08 Mirdarthos-PC plasmashell[989]: qml: [debug] [main.qml] [pws-api.js] https://api.weather.com/v1/geocode/-25.724156/28.253234/forecast/daily/7day.json?apiKey=e1f10a1e78da46f5b10a1e78da96f525&language=en-ZA&units=m
Oct 15 15:13:08 Mirdarthos-PC plasmashell[989]: org.kde.plasma.containmentlayoutmanager: Trying to take space not available BasicAppletContainer_QMLTYPE_35_QML_78(0x55c1e4022d10, id="appletContainer", parent=0x55c1e3c69640, geometry=2537,1020 76x54)
Oct 15 15:13:08 Mirdarthos-PC plasmashell[989]: qml: [debug] [main.qml] [pws-api.js] Got new forecast data


$ ps -aux | grep plasmashell
mirdart+     964  4.6  4.4 4685448 728324 ?      Ssl  12:54   0:44 /usr/bin/plasmashell --no-respawn
mirdart+    3838  0.0  0.0   6400  2104 pts/0    S+   13:10   0:00 grep --color=auto --exclude-dir=.bzr --exclude-dir=CVS --exclude-dir=.git --exclude-dir=.hg --exclude-dir=.svn --exclude-dir=.idea --exclude-dir=.tox --exclude-dir=.venv --exclude-dir=venv plasmashell

Which is correct command, it seems:

$ systemctl --user cat plasma-plasmashell.service
# /usr/lib/systemd/user/plasma-plasmashell.service
[Unit]
Description=KDE Plasma Workspace
After=plasma-ksmserver.service plasma-kcminit.service
PartOf=graphical-session.target
StartLimitIntervalSec=60s
StartLimitBurst=3

[Service]
ExecStart=/usr/bin/plasmashell --no-respawn
Restart=on-failure
Type=dbus
BusName=org.kde.plasmashell
Slice=session.slice
TimeoutSec=40sec

[Install]
WantedBy=plasma-core.target

I previously did have a lot of customisations, but as far as I can tell, disabling them makes no difference.

After restarting the service, when everything’s working again:

$ systemctl --user status plasma-plasmashell.service
● plasma-plasmashell.service - KDE Plasma Workspace
     Loaded: loaded (/usr/lib/systemd/user/plasma-plasmashell.service; enabled; preset: enabled)
     Active: active (running) since Tue 2024-10-15 13:20:47 SAST; 2min 26s ago
 Invocation: 2f7fbd674e8e4926a8ed6d0fd21573d2
   Main PID: 4741 (plasmashell)
      Tasks: 32 (limit: 18951)
     Memory: 382.3M (peak: 383.8M)
        CPU: 9.394s
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service
             ├─4741 /usr/bin/plasmashell --no-respawn
             ├─4792 /usr/lib/kf6/kioworker /usr/lib/qt6/plugins/kf6/kio/desktop.so desktop "" local:/run/user/1000/plasmashelltnLamY.1.kioworker.socket
             ├─4831 /usr/lib/kf6/kioworker /usr/lib/qt6/plugins/kf6/kio/kio_trash.so trash "" local:/run/user/1000/plasmashellXgjtGW.2.kioworker.socket
             └─4833 /usr/lib/kf6/kioworker /usr/lib/qt6/plugins/kf6/kio/tags.so tags "" local:/run/user/1000/plasmashellsAGJEw.3.kioworker.socket

Oct 15 13:20:55 Mirdarthos-PC plasmashell[4741]: kameleon enabled true
Oct 15 13:20:55 Mirdarthos-PC plasmashell[4741]: file:///usr/share/plasma/plasmoids/org.kde.plasma.brightness/contents/ui/PopupDialog.qml:21:18: QML ScrollView: ScrollView only supports Flickable types as its contentItem
Oct 15 13:20:55 Mirdarthos-PC plasmashell[4741]: QQmlExpression: Expression file:///usr/share/plasma/plasmoids/org.kde.plasma.brightness/contents/ui/KeyboardColorItem.qml:26:5 depends on non-NOTIFYable properties:
Oct 15 13:20:55 Mirdarthos-PC plasmashell[4741]:     KeyboardColorControl::supported
Oct 15 13:20:55 Mirdarthos-PC plasmashell[4741]: QQmlExpression: Expression file:///usr/share/plasma/plasmoids/org.kde.plasma.brightness/contents/ui/KeyboardColorItem.qml:77:21 depends on non-NOTIFYable properties:
Oct 15 13:20:55 Mirdarthos-PC plasmashell[4741]:     KeyboardColorControl::enabled
Oct 15 13:20:55 Mirdarthos-PC plasmashell[4741]: QQmlExpression: Expression file:///usr/share/plasma/plasmoids/org.kde.plasma.brightness/contents/ui/KeyboardColorItem.qml:64:21 depends on non-NOTIFYable properties:
Oct 15 13:20:55 Mirdarthos-PC plasmashell[4741]:     KeyboardColorControl::enabled
Oct 15 13:20:55 Mirdarthos-PC plasmashell[4741]: qrc:/qt/qml/org/kde/plasma/components/ScrollView.qml:31:9: QML WheelHandler: target must be a QQuickFlickable
Oct 15 13:20:55 Mirdarthos-PC plasmashell[4741]: file:///usr/share/plasma/plasmoids/org.kde.plasma.brightness/contents/ui/KeyboardColorItem.qml:67:21: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }

I’ve tested a new user, and it works, so it’s obviously just me missing something.

Obligatory inxi -Farz:

System:
  Kernel: 6.6.54-2-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.6.54-2-MANJARO
    root=UUID=4b0b1c3e-837f-4ef5-bf96-6c630c24619b rw quiet
    udev.log_priority=3 modprobe.blacklist=iTCO_wdt ipv6.disable_ipv6=1
    nvidia.NVreg_UsePageAttributeTable=1
    nvidia.NVreg_PreserveVideoMemoryAllocations=1
    nvidia.NVreg_TemporaryFilePath=/var/tmp nvidia_drm.modeset=1
    nvidia_drm.fbdev=1
  Desktop: KDE Plasma v: 6.1.5 tk: Qt v: N/A wm: kwin_x11 with: cairo-dock
    dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop System: Gigabyte product: Z370 HD3 v: N/A serial: N/A
  Mobo: Gigabyte model: Z370 HD3-CF serial: N/A
    uuid: 03d502e0-045e-056a-9b06-650700080009 UEFI: American Megatrends v: F14
    date: 11/13/2021
CPU:
  Info: model: Intel Core i7-8700 socket: LGA1151 (U3E1) note: check bits: 64
    type: MT MCP arch: Coffee Lake gen: core 8 level: v3 note: check built: 2018
    process: Intel 14nm family: 6 model-id: 0x9E (158) stepping: 0xA (10)
    microcode: 0xF8
  Topology: cpus: 1x dies: 1 clusters: 6 cores: 6 threads: 12 tpc: 2
    smt: enabled cache: L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB
    desc: 6x256 KiB L3: 12 MiB desc: 1x12 MiB
  Speed (MHz): avg: 800 min/max: 800/4600 base/boost: 4300/8300 scaling:
    driver: intel_pstate governor: powersave volts: 1.1 V ext-clock: 100 MHz
    cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 9: 800
    10: 800 11: 800 12: 800 bogomips: 76831
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling mitigation: Microcode
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
    vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: IBRS
  Type: spec_rstack_overflow status: Not affected
  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; STIBP: conditional;
    RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort mitigation: TSX disabled
Graphics:
  Device-1: NVIDIA GM206 [GeForce GTX 960] vendor: Gigabyte driver: nvidia
    v: 550.120 alternate: nouveau,nvidia_drm non-free: 550.xx+ status: current
    (as of 2024-09; EOL~2026-12-xx) arch: Maxwell code: GMxxx
    process: TSMC 28nm built: 2014-2019 pcie: gen: 3 speed: 8 GT/s lanes: 16
    ports: active: none off: DVI-I-1,HDMI-A-1 empty: DP-1,DVI-D-1
    bus-ID: 01:00.0 chip-ID: 10de:1401 class-ID: 0300
  Display: unspecified server: X.Org v: 21.1.13 with: Xwayland v: 24.1.2
    compositor: kwin_x11 driver: X: loaded: nvidia gpu: nvidia,nvidia-nvswitch
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 5120x1080 s-dpi: 97 s-size: 1341x283mm (52.80x11.14")
    s-diag: 1371mm (53.96") monitors: <missing: xrandr>
  Monitor-1: DVI-I-1 model: LG (GoldStar) ULTRAWIDE serial: <filter>
    built: 2016 res: 2560x1080 dpi: 97 gamma: 1.2 size: 673x284mm (26.5x11.18")
    diag: 730mm (28.8") modes: max: 2560x1080 min: 640x480
  Monitor-2: HDMI-A-1 model: LG (GoldStar) ULTRAWIDE serial: <filter>
    built: 2016 res: 2560x1080 dpi: 97 gamma: 1.2 size: 673x284mm (26.5x11.18")
    diag: 730mm (28.8") modes: max: 2560x1080 min: 640x480
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
    drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia
    inactive: wayland,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.120
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GTX 960/PCIe/SSE2
    memory: 1.95 GiB
  API: Vulkan v: 1.3.295 layers: 1 device: 0 type: discrete-gpu
    name: NVIDIA GeForce GTX 960 driver: nvidia v: 550.120 device-ID: 10de:1401
    surfaces: xcb,xlib
Audio:
  Device-1: Intel 200 Series PCH HD Audio vendor: Gigabyte
    driver: snd_hda_intel v: kernel alternate: snd_soc_avs bus-ID: 00:1f.3
    chip-ID: 8086:a2f0 class-ID: 0403
  Device-2: NVIDIA GM206 High Definition Audio vendor: Gigabyte
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 01:00.1 chip-ID: 10de:0fba class-ID: 0403
  API: ALSA v: k6.6.54-2-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.2.5 status: n/a (root, process) with: wireplumber
    status: active tools: pw-cli,wpctl
  Server-3: PulseAudio v: 17.0 status: active (root, process)
    with: pulseaudio-alsa type: plugin tools: pacat,pactl
Network:
  Device-1: Intel Ethernet I219-V vendor: Gigabyte driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b8 class-ID: 0200
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Info: services: NetworkManager, sshd, systemd-timesyncd
Drives:
  Local Storage: total: 8.41 TiB used: 3.31 TiB (39.3%)
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 960 EVO 250GB
    size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 3B7QCXE7 temp: 30.9 C
    scheme: GPT
  SMART: yes health: PASSED on: 212d 2h cycles: 4,015
    read-units: 60,117,953 [30.7 TB] written-units: 49,703,378 [25.4 TB]
  ID-2: /dev/sda maj-min: 8:0 vendor: Seagate model: ST4000DM000-1F2168
    family: Desktop HDD.15 size: 3.64 TiB block-size: physical: 4096 B
    logical: 512 B sata: 3.1 speed: 6.0 Gb/s tech: HDD rpm: 5900
    serial: <filter> fw-rev: CC54 temp: 35 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 3y 245d 1h cycles: 4324
    read: 124.31 TiB written: 64.34 TiB Old-Age: UDMA CRC errors: 13567
    alert: Bad cable/connection? Pre-Fail: end-to-end: 99 threshold: 99
    alert: FAILING_NOW attribute: Spin_Retry_Count value: 100 worst: 100
    threshold: 97
  ID-3: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST5000VX0011-1T317X
    family: Surveillance size: 4.55 TiB block-size: physical: 4096 B
    logical: 512 B sata: 3.1 speed: 6.0 Gb/s tech: HDD rpm: 7200
    serial: <filter> fw-rev: VN02 temp: 40 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 1y 333d 7h cycles: 3391
    read: 80.12 TiB written: 19.49 TiB Pre-Fail: attribute: Spin_Retry_Count
    value: 100 worst: 100 threshold: 97
Partition:
  ID-1: / raw-size: 224.09 GiB size: 219.52 GiB (97.96%)
    used: 55.13 GiB (25.1%) fs: ext4 block-size: 4096 B dev: /dev/nvme0n1p2
    maj-min: 259:2
  ID-2: /boot/efi raw-size: 1000 MiB size: 998 MiB (99.80%)
    used: 288 KiB (0.0%) fs: vfat block-size: 512 B dev: /dev/nvme0n1p3
    maj-min: 259:3
Swap:
  Kernel: swappiness: 10 (default 60) cache-pressure: 75 (default 100)
    zswap: yes compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 7.81 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/nvme0n1p1 maj-min: 259:1
Sensors:
  System Temperatures: cpu: 34.0 C mobo: 29.0 C gpu: nvidia temp: 32 C
  Fan Speeds (rpm): N/A gpu: nvidia fan: 64%
Repos:
  Packages: pm: pacman pkgs: 1677 libs: 410 tools: pamac pm: appimage pkgs: 0
    pm: flatpak pkgs: 0
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: http://mirror.is.co.za/mirrors/manjaro.org/stable/$repo/$arch
    2: http://manjaro.mirror.ac.za/stable/$repo/$arch
    3: https://mirror.easyname.at/manjaro/stable/$repo/$arch
    4: https://ftp.psnc.pl/linux/manjaro/stable/$repo/$arch
    5: https://mirror.alwyzon.net/manjaro/stable/$repo/$arch
Info:
  Memory: total: 16 GiB available: 15.55 GiB used: 5.67 GiB (36.5%)
  Processes: 361 Power: uptime: 33m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 6.17 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
    tool: systemctl
  Compilers: clang: 18.1.8 gcc: 14.2.1 Shell: Sudo (sudo) v: 1.9.16
    default: Zsh v: 5.9 running-in: yakuake inxi: 3.3.36

(For what it’s worth)

I’d appreciate if someone could shine some light on my F’up…

Edit:

The same is apparently true for plasma-kglobalaccel.service. After startup:

$ systemctl --user status plasma-kglobalaccel.service
● plasma-kglobalaccel.service - KDE Global Shortcuts Server
Loaded: loaded (/usr/lib/systemd/user/plasma-kglobalaccel.service; static)
Active: active (running) since Tue 2024-10-15 12:54:28 SAST; 38min ago
Invocation: 723067ab9cb74c589eeec3d9d2e9a4a2
Main PID: 977 (kglobalacceld)
Tasks: 3 (limit: 18951)
Memory: 18.4M (peak: 20.2M)
CPU: 2.985s
CGroup: /user.slice/user-1000.slice/user@1000.service/background.slice/plasma-kglobalaccel.service
└─977 /usr/lib/kglobalacceld

Oct 15 12:54:28 Mirdarthos-PC systemd[825]: plasma-kglobalaccel.service: Main process exited, code=dumped, status=6/ABRT
Oct 15 12:54:28 Mirdarthos-PC systemd[825]: plasma-kglobalaccel.service: Failed with result 'core-dump'.
Oct 15 12:54:28 Mirdarthos-PC systemd[825]: Failed to start KDE Global Shortcuts Server.
Oct 15 12:54:28 Mirdarthos-PC systemd[825]: plasma-kglobalaccel.service: Scheduled restart job, restart counter is at 1.
Oct 15 12:54:28 Mirdarthos-PC systemd[825]: Starting KDE Global Shortcuts Server...
Oct 15 12:54:28 Mirdarthos-PC systemd[825]: Started KDE Global Shortcuts Server.
Oct 15 12:54:28 Mirdarthos-PC kglobalacceld[977]: could not create a component for  "bash-2.desktop"
Oct 15 12:54:29 Mirdarthos-PC kglobalacceld[977]: "applications.menu"  not found in  QList("/home/mirdarthos/.config/menus", "/etc/xdg/menus")

And my shortcut for running a script doesn’t work. Then

$ systemctl --user restart plasma-kglobalaccel.service
$ systemctl --user status plasma-kglobalaccel.service
● plasma-kglobalaccel.service - KDE Global Shortcuts Server
Loaded: loaded (/usr/lib/systemd/user/plasma-kglobalaccel.service; static)
Active: active (running) since Tue 2024-10-15 13:34:04 SAST; 27s ago
Invocation: c12dd3cd770a4cf2b6bb4b754591443a
Main PID: 6126 (kglobalacceld)
Tasks: 3 (limit: 18951)
Memory: 16.5M (peak: 17M)
CPU: 236ms
CGroup: /user.slice/user-1000.slice/user@1000.service/background.slice/plasma-kglobalaccel.service
└─6126 /usr/lib/kglobalacceld

Oct 15 13:34:03 Mirdarthos-PC systemd[825]: Starting KDE Global Shortcuts Server...
Oct 15 13:34:04 Mirdarthos-PC systemd[825]: Started KDE Global Shortcuts Server.

And the shortcut starts working.

Edit #2:

Just did some more troubleshooting and just as I though, disablling my themes and extensions made no difference.

1 Like

A bit of a guess after reading the output, it suggests to me that something in a panel’s widgets is causing the problem (perhaps the weather one?)

Try logging off, then going on a TTY and renaming ~/.config/plasma-org.kde.plasma.desktop-appletsrc then log back into Plasma. If this doesn’t help, log out again and rename the file back.

I just checked my service units, for some reason or the other that escaped me, with:

$ systemctl --user list-units

And this caught my attention:

[...]
● app-baloo_file@9298e7cacf8e4d579ea0e070d4830d3e.service                                    loaded failed failed    Baloo File Daemon
[...]
● app-pulseaudio@d6225bdee98e4c28ad2346560da7b39e.service                                    loaded failed failed    PulseAudio Sound System
[...]
● app-xembedsniproxy@439c183458ba4285b36cb27390f6b3a5.service                                loaded failed failed    XembedSniProxy
● app-zeitgeist\x2ddatahub@15be968a8f6b4e26b61e5c97d9d031ee.service                          loaded failed failed    Zeitgeist Datahub
[...]
● plasma-kcminit-phase1.service                                                              loaded failed failed    KDE Configuration Module Initialization (Phase 1)
[...]

The baloo indexer seems to be worrking fine:

$ balooctl6 status
Baloo File Indexer is running
Indexer state: Idle
Total files indexed: 255,386
Files waiting for content indexing: 0
Files failed to index: 0
Current size of index is 174.66 MiB

I have a hearing difficulty, so nothing audio-related, such as the pulseaudio service matters, and I don’t know what the next two are although as far as I know, zeitgeist is a notification daemon, so that’s not it that I know of.

No, what caught my attention was the failed plasma-kcminit-phase1.service. So I investigated further.

$ systemctl --user status plasma-kcminit-phase1.service
○ plasma-kcminit-phase1.service - KDE Configuration Module Initialization (Phase 1)
     Loaded: loaded (/usr/lib/systemd/user/plasma-kcminit-phase1.service; static)
     Active: inactive (dead) since Tue 2024-10-15 16:12:36 SAST; 9min ago
 Invocation: eaf5bc4dedea4f0480ddc94769413467
   Main PID: 986 (code=exited, status=2)
   Mem peak: 3.5M
        CPU: 10ms

Oct 15 16:12:36 Mirdarthos-PC systemd[833]: Starting KDE Configuration Module Initialization (Phase 1)...
Oct 15 16:12:36 Mirdarthos-PC qdbus[986]: Service 'org.kde.kcminit' does not exist.
Oct 15 16:12:36 Mirdarthos-PC systemd[833]: plasma-kcminit-phase1.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Oct 15 16:12:36 Mirdarthos-PC systemd[833]: plasma-kcminit-phase1.service: Failed with result 'exit-code'.
Oct 15 16:12:36 Mirdarthos-PC systemd[833]: Failed to start KDE Configuration Module Initialization (Phase 1).

I have a sneaky suspicion it has to do with that, because I tried the suggestion by @beermad to no change in behavior.

I was so certain it would work, I just deleted it. Didn’t work, so I got it back from a previous backup. (That’s what they’re there for after all.)

WOOOOOOOOOOOOOOOOOOOOHOOOOOOOOOOOOOOOOOOOOOOOO!!!

Seems I found it.

I’m trying to convert all my xdg-autostarts to systemd units, and for some reason as of yet unknown to me, this didn’t work for my Dock, cairo-dock. It works for everything else, except that.

:partying_face: :partying_face: :partying_face: :partying_face: :partying_face: :partying_face: :partying_face: :partying_face: :partying_face: :partying_face: :partying_face: :partying_face: :partying_face: :partying_face: :partying_face: :partying_face: :partying_face: :partying_face:

Now I wonder if I should retry restoring my backup and removing that before booting again… :thinking:

I’ve been down that rabbit-hole (though without quite the bad results you suffered). I’ve found that although processes that run purely in the background work OK that way, but those which need to do anything on-screen caused problems.

I found the most reliable way to do things was to have a single wrapper script which is called as an autostart and triggers everything I need on my desktop, with backgrounded processes as systemd units which are started by that wrapper rather than trying to make them auto-start. (Another advantage of this is that I find it useful to delay these a little bit to reduce the CPU load at login so my desktop becomes active a bit quicker - especially after auto-login from a reboot).

1 Like