https://bugs.kde.org/show_bug.cgi?id=509691
--- Comment #9 from Jörg Habenicht <[email protected]> --- Hello guys, hi Nate, TL;DR: Could it be a fault of plasma-fallback-session-restore? The error still persists, so I did a bit more research on this topic. AI and me found more stuff to look at. A) I logged the start of xosview with this shell script. It logs the environment. I renamed xosview to xosview.real (see below). #!/bin/sh { date +%T.%N echo "PID=$$ PPID=$PPID ARGS=$*" tr '\0' ' ' < /proc/$PPID/cmdline; echo cat /proc/$$/cgroup env | grep -E 'DESKTOP_STARTUP_ID|XDG_ACTIVATION|SESSION_MANAGER' echo ---- } >> /tmp/xosview-start.log ps fax >> /tmp/xosview-ps.$$.log exec /usr/bin/xosview.real "$@" Session closed with one instance of xosview, session starts with two instances. result in /tmp/xosview-start.log is: 18:57:01.747993181 PID=31091 PPID=30912 ARGS= /usr/bin/ksmserver 0::/4 SESSION_MANAGER=local/karli:@/tmp/.ICE-unix/30912,unix/karli:/tmp/.ICE-unix/30912 DESKTOP_STARTUP_ID=karli;1790873821;739247;30912_TIME32962054 ---- 18:57:01.843824954 PID=31207 PPID=31103 ARGS= /usr/libexec/plasma-fallback-session-restore 0::/4 SESSION_MANAGER=local/karli:@/tmp/.ICE-unix/30912,unix/karli:/tmp/.ICE-unix/30912 DESKTOP_STARTUP_ID=karli;1790873821;842529;31103_TIME32962095 ---- B) Now I renamed /usr/share/applications/xosview.desktop . Close and restart the session. Only one instance of xosview started. /tmp/xosview-start.log shows no new content. Instead the renamed xosview.real was started (see A). # pgrep -a xosview 34198 /usr/bin/xosview.real plasma-fallback-session-restore got an entry as well: $ cat ~/.local/state/plasmasessionrestorestaterc [0] appId=xosview.desktop So it seems plasma-fallback-session-restore remembered xosview as well as ksmserver. There could be a fault in plasma-workspace/startkde/session-restore/{save,restore}.cpp I'll investigate further. -- You are receiving this mail because: You are watching all bug changes.
