Bug 504719

Summary: Plasma apps fail to launch cleanly due to persistent ffffffff-ffff-4fff-bfff-ffffffffffff activity UUID across archlinux and Kubuntu fresh installs
Product: [Plasma] plasmashell Reporter: shippudend <shippudend>
Component: Activities in generalAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DOWNSTREAM    
Severity: major CC: ivan.cukic, meven, natalie_clarius, nate, nimokater, xaver.hugl
Priority: NOR    
Version First Reported In: 6.3.4   
Target Milestone: 1.0   
Platform: Kubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description shippudend@hotmail.com 2025-05-24 03:56:41 UTC 
SUMMARY
On multiple clean installations of both Arch Linux and Kubuntu 24.04 (Plasma 6) on both wayland and X11, all apps launched under systemd appear with a corrupted service ID like:
´´´
app-org.kde.konsole@ffffffffffff4fffbfffffffffffffff.service
´´´
This results in errors like:
´´´
Unit app-org.kde.konsole@ffffffffffff4fffbfffffffffffffff.service was already loaded or has a fragment file. 
´´´
Session ID or activity UUID is consistently stuck at:
´´´
ffffffff-ffff-4fff-bfff-ffffffffffff
´´´
This causes:

    All launched apps to share the same corrupted systemd unit

    Failure to open second windows

    Broken D-Bus integration

    Incomplete user session under loginctl

STEPS TO REPRODUCE
1. Perform a clean install of Kubuntu 24.04 or Arch Linux with KDE/Plasma
2. Log in as a new user
3. Launch Konsole or any app
4. Running 
´´´
qdbus6 org.kde.ActivityManager /ActivityManager/ListActivities

´´´
Returns
´´´
Error: org.freedesktop.DBus.Error.UnknownObject
No such object path '/ActivityManager/ListActivities'

´´´

Attempting to manually start kactivitymanagerd via kquitapp6 or kactivitymanagerd --no-respawn does not fix it


EXPECTED RESULT
kactivitymanagerd should initialize a real UUID and register valid activities

App unit names should reflect per-window UUIDs

KDE session should be systemd-integrated without launching failures

WHAT I TRIED:


    Wiped ~/.local/share/kactivitymanagerd, ~/.config/kactivitymanagerdrc, etc.

    Ran kactivitymanagerd manually

    Created new activities manually in System Settings

    Tried on both Wayland and X11 sessions

    Verified machine ID (/etc/machine-id) is valid

    BIOS UUID is valid (/sys/class/dmi/id/product_uuid)

    Confirmed uuidgen works

    Verified systemd --user session exists and is running

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 25.04
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.3
Kernel Version: 6.14.0-15-generic (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD 4700S 8-Core Processor Desktop Kit
Memory: 15.6 GiB of RAM
Graphics Processor: AMD Radeon RX 550 / 550 Series

ADDITIONAL INFORMATION
I made a post on the kde forums with more info: https://discuss.kde.org/t/launcher-fails-to-open-new-windows-of-already-open-apps/34551/5?u=galen
Comment 1 Nate Graham 2025-05-27 20:03:41 UTC 
Activities are per-user, but on current git master, I can't reproduce this if I create a new user account on the same machine:

$ qdbus-qt6 org.kde.ActivityManager /ActivityManager/Activities org.kde.ActivityManager.Activities.ListActivities
ce4eee70-b7f3-43f8-8639-e734f2103ffa
Comment 2 nimokater 2025-07-14 20:53:37 UTC 
I have the same issue using an  AMD 4700S desktop kit cpu, which i assume you are using as well according to this: https://discuss.kde.org/t/launcher-fails-to-open-new-windows-of-already-open-apps/34551/7
I am using PikaOS with KDE
Comment 3 nimokater 2025-07-14 20:55:03 UTC 
(In reply to Nate Graham from comment #1)
> Activities are per-user, but on current git master, I can't reproduce this
> if I create a new user account on the same machine:
> 
> $ qdbus-qt6 org.kde.ActivityManager /ActivityManager/Activities
> org.kde.ActivityManager.Activities.ListActivities
> ce4eee70-b7f3-43f8-8639-e734f2103ffa

it seems to be a hardware related issue since its only been reproduced with the same cpu aka the AMD 4700S 8-Core Processor Desktop Kit.