https://bugs.kde.org/show_bug.cgi?id=515206
--- Comment #30 from [email protected] --- NEW OBSERVATION - Different behavior depending on the trigger: I have noticed that the "Autonomous" behavior and UI locking vary depending on where the update is started: 1. Triggered via Tray Icon (Right-click > Start updates): The "Green Shield" appears and the update process runs in the background. In this scenario, I am still able to open the Discover app without any lock or issues. 2. Triggered via Discover GUI (Clicking "Update" inside the app): As reported previously, this causes a significant notification lag, and once the Green Shield appears, the Discover app becomes locked/inaccessible. 3. Automatic Trigger still failing: Despite the settings, the system never starts this process on its own. I still have to manually click "Start updates" to see the autonomous (green shield) mode in action. Conclusion: The background update mechanism itself seems to work correctly when invoked from the system tray menu. However, the "Automatic" scheduler is still not triggering independently, and there is a specific UI conflict/lock when the process is initiated from within the Discover application itself. -- You are receiving this mail because: You are watching all bug changes.
