SUMMARY Akregator cannot be used from system tray (Wayland). STEPS TO REPRODUCE 1. Settings > General > select Show Tray Icon > Ok 2. Close the main window 3. Open Akregator from tray (Show hidden icons list) OBSERVED RESULT Akregator shows active in panel, but no window is opened. Need to quit the program from tray (right click) and open Akregator from start menu. When started, it always shows error that the session was not closed properly and asks what to do (restore/new). EXPECTED RESULT Start Akregator from the system tray with the current session active. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian 13 Trixie with Wayland KDE Plasma Version: 6.3.6 KDE Frameworks Version: 6.13.0 Qt Version: 6.8.2 ADDITIONAL INFORMATION I am unable to generate a back trace because the app does not crash. It only hangs. The only line shown in gdb that seems relevant is: qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x555555ed2e00 In /var/log/syslog: /var/log/syslog:15124:2025-09-08T12:12:43.881652+02:00 solydxk-main systemd[2046]: Started app-org.kde.akregator@0e62444243994d0588a1c6243ba6a4da.service - Akregator - Feed Reader. /var/log/syslog:15125:2025-09-08T12:12:44.349603+02:00 solydxk-main akregator[12775]: org.kde.pim.pimcommonactivities: Plasma activities is not running: 1 Plasma Activities in KDE PIM version: ****@solydxk-main:~$ apt-cache policy libkpim6pimcommonactivities6 libkpim6pimcommonactivities6: Installed: 4:24.12.3-1 Candidate: 4:24.12.3-1 Version table: *** 4:24.12.3-1 500 500 https://deb.debian.org/debian trixie/main amd64 Packages 100 /var/lib/dpkg/status Akregator version output: ****@solydxk-main:~$ akregator --version akregator 6.3.3 (24.12.3) QThreadStorage: Thread 0x563f051992e0 exited after QThreadStorage 10 destroyed QThreadStorage: Thread 0x563f051992e0 exited after QThreadStorage 3 destroyed QThreadStorage: Thread 0x563f051992e0 exited after QThreadStorage 2 destroyed
When Akregator is in the state as reported where a click will not open the main window, does the tray icon contain a "Restore" action? if it does not, then this is a bug which should have been fixed by https://invent.kde.org/pim/akregator/-/commit/37472c0e