Bug 144410

Summary:	settings: initial state of the window -- opened vs. hidden with icon in systray
Product:	[Applications] akregator	Reporter:	Maciej Pilichowski <bluedzins>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	REPORTED ---
Severity:	wishlist	CC:	cfeck, lucazanna89, mte90net
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:

Description Maciej Pilichowski 2007-04-19 08:15:32 UTC

Version:            (using KDE KDE 3.5.6)
Installed from:    SuSE RPMs

There is a similar (but not duplicate) wish-report about integrating KDE session mechanism and akregator restoration, here:
https://bugs.kde.org/show_bug.cgi?id=88692

This report however is about providing new explicit option in settings to control initial state of akregator, something like
[ ] hide in systray on start

I read only slow changing feeds and showing main window does not make any sense for me (there is nothing to read at most of the time). It is also useful when akregator is in Autostart. As a useful side-effect it would also mean, than after checking it on, KDE session manager would "restore" opened window in hidden state.

Comment 1 Christophe Marin 2009-07-04 14:03:45 UTC

*** Bug 187205 has been marked as a duplicate of this bug. ***

Comment 2 Maciej Pilichowski 2009-09-18 18:48:55 UTC

In regard to Autostart it is actually a bug -- I run several systray apps which launches (via Autostart) to systray. The only exception is Akregator which (auto)starts with window. Each time I start KDE I have to manually close the window. It also happens regardless of the previous state (i.e. when closing KDE).

No such effect with KDE3 version.

Please change the status to bug (since it is now a regression), thank you.

Comment 3 Daniele Scasciafratte 2012-08-27 12:55:13 UTC

Any news for this old bug?

Comment 4 Christoph Feck 2012-08-27 13:28:46 UTC

Since akregator is basically unmaintained, you would need to find someone providing a patch (or trying one yourself).

Comment 5 Justin Zobel 2021-03-09 04:11:52 UTC

Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.