Bug 187205 - launch akregator minimized in system tray
Summary: launch akregator minimized in system tray
Status: RESOLVED DUPLICATE of bug 144410
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-15 11:08 UTC by Luca
Modified: 2009-07-04 14:03 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Luca 2009-03-15 11:08:57 UTC
Version:            (using KDE 4.2.1)
OS:                Linux
Installed from:    Unspecified Linux

Every time i log in in a KDE session, akregator starts and pops up the mainwindow, also if i log out from the previous session with akregator minimized in the sys tray. 
It would be nice if there was an option to force akregator to start minimized in the system tray.
Comment 1 Haakon Nilsen 2009-03-21 18:03:23 UTC
You can try to start akregator using 'akregator --hide-mainwindow'. This does not seem to work correctly for me (on trunk). The window is already there when the test for this option is run in main.cpp.

If akregator is minimized to the systray when it quits, it will start up in this state too.
Comment 2 Maciej Pilichowski 2009-06-15 07:21:58 UTC
> If akregator is minimized to the systray when it quits, it will start up in
> this state too.

KDE4.3b2. Does not work that way.

If it is technically possible, with systray enabled, it would be great to detect how akregator was launched:
* SM -- restore previous state
* by hand (like from KMenu) -- show window
* automatically (like autostart) -- does not show window

It if it is not possible, please provide an option for this -- for example when somebody uses autostart, he/she would expect akregator in systray state on launch _always_.
Comment 3 Christophe Marin 2009-07-04 14:03:45 UTC

*** This bug has been marked as a duplicate of bug 144410 ***