https://bugs.kde.org/show_bug.cgi?id=510433

            Bug ID: 510433
           Summary: Conflict between autostart applications and session
                    restore
    Classification: Plasma
           Product: plasmashell
      Version First 6.4.5
       Reported In:
          Platform: Arch Linux
                OS: Linux
            Status: REPORTED
          Severity: minor
          Priority: NOR
         Component: Session Management
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]
  Target Milestone: 1.0

SUMMARY
Some autostart applications have issues when using session restore. I've seen
this with two applications, each with different behavior:
1. StreamController (flatpack installed via Discover)
2. DesktopVideoUpdater (part of the decklink package from Blackmagic Design)

STEPS TO REPRODUCE
1. Set Session Restore to "On last login"
2. Have affected application(s) installed and configured to autostart
3. Logout and log back into KDE

OBSERVED RESULT
The different applications had different behavior.
1. StreamController: the application crashes on startup and appears not to
start
2. DesktopVideoUpdater: "prior" instances of the application tagged with a
--session argument are started and a new instance of the application (not
tagged with --session) is also started creating duplicate processes.

EXPECTED RESULT
1. StreamController: the application starts as expected (works this way without
Session Restore)
2. DesktopVideoUpdater: prior instances of the application are not restored,
i.e. only one instance is running regardless of restarts.

SOFTWARE/OS VERSIONS
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.18.0
Qt Version: 6.9.2

ADDITIONAL INFORMATION
DesktopVideoUpdater is autostarted via a .desktop file in /etc/xdg/autostart
placed there by the package. This autostart entry doesn't appear in the System
Settings/Autostart section, but I presume that's by design.

StreamController is autostarted via a .desktop file in ~/.config/autostart. I
presume this is placed there by the application when its own autostart setting
is enabled. This autostart entry does appear in the System Settings/Autostart
section.

I suspect DesktopVideoUpdater is intended to be a GUI application based on its
man page, but no window ever appears and the application remains running until
logout. This may be intended as a "background task" or "system tray"
application that simply isn't properly implemented.

Both these packages may require additional hardware. The decklink package
(containing DesktopVideoUpdater) probably requires a Blackmagic Design
Decklink, Intensity, or Multibridge video editing card. StreamController may
function without a Stream Deck appliance, but I'm not sure.

My current workaround is to set Session Restore to "Start with an empty
session."

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to