Bug 219399

Summary:	sometimes doesn't show tray icon
Product:	[Applications] akregator	Reporter:	Marc Haber <mh+kde-bugs>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	fe.thomm
Priority:	NOR
Version:	1.5.3
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Marc Haber 2009-12-20 10:13:13 UTC

Version:           1.5.3 (using 4.3.4 (KDE 4.3.4), Debian packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.32-zgws1

Hi,

akregator sometimes stops showing its tray icon despite the option being ticket in the akregator configuration. To get the icon back, I need to untick the option, click apply, tick the option again, and click apply again.

Greetings
Marc

Comment 1 Ferdinand Thommes 2010-05-07 14:46:46 UTC

confirmed with KDE 4.4.3 in Debian Sid
I use akregator within kontact.
upon starting kontact there is no tray icon even though its ticked in akregator settings. opening akregator within kontact  and klicking on a feed to open, the icon appears _and_ akregator starts fetching news.
on another box with the same kde 4.4.3 and debian sid it all works as it should. icon sits in tray after start and news get fetched in auto mode.

regards
Ferdinand

Comment 2 Christophe Marin 2010-12-26 18:11:46 UTC

When starting kontact, akregator is not automatically loaded (unless you set kontact to start on the akregator component).

That's why the systray icon is not there. Nothing is misbehaving there.

I don't think the original report was about kontact.

Comment 3 Denis Kurz 2016-09-24 19:44:50 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of akregator (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.

Comment 4 Denis Kurz 2017-01-07 21:48:53 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.