Bug 496960

Summary:	Akregator does not re-open after closing when certain settings are configured
Product:	[Applications] akregator	Reporter:	brib <usual.flag1029>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	REPORTED ---
Severity:	normal	CC:	usual.flag1029
Priority:	NOR
Version:	6.2.3
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description brib 2024-12-02 21:45:36 UTC

SUMMARY

When the system tray icon is disabled, I cannot open Akregator after closing it without killing running `killall akregator`.

This appears to be because the `akregator` process is running in the background after I close it. However, because the process is running in the background, I cannot spin up a new process without killing the old one. Furthermore, because the system tray icon is disabled, I have no access to the original process.

STEPS TO REPRODUCE
1. Open Akregator via menu or command line
2. Turn off the "Show Tray Icon" option in Akregator
3. Close Akregator (via closing the window or ctrl-Q)
4. Try to run Akregator again, from a menu or command line

OBSERVED RESULT

If run from a menu, it appears to start loading akregator (e.g. there is a bouncing "akregator" icon by my cursor), but this disappears.

If run from a command line, the following message shows:

org.kde.pim.akregator: akregator is already running, exiting.

EXPECTED RESULT

I expect that when I close all of Akregator's windows, or quit the application, and there is no tray icon present, that this kills the akregator process.

Even if the akregator process is not killed, I expect I should be able to re-open Akregator's windows by clicking on the menu icon.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.0
Kernel Version: 6.12.1-arch1-1 (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION

Comment 1 brib 2024-12-02 21:54:00 UTC

When I deleted my Akregator configuration, the bug did not seem to appear until I re-added my feed list and fetched my (3000+) feeds. I wonder if the size of the feed list or the feeds is affecting things.

Comment 2 brib 2024-12-02 22:02:09 UTC

Actually, I think another thing needed to reproduce the bug is to enable the "Mark all feeds as read on startup" setting. When this setting is not enabled, the process doesn't quit but the window opens normally. When the setting is enabled, the bug occurs.