Bug 327421 - akonaditray dont uses his plasma themes svg icon anymore
Summary: akonaditray dont uses his plasma themes svg icon anymore
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 4.11
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-10 16:59 UTC by FabiB
Modified: 2017-01-07 22:28 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description FabiB 2013-11-10 16:59:12 UTC 
unter 4.11 akonaditray dont uses his plasma themes icon anymore. if the plasma theme supports the akonadiicon in the svg icon theme akonaditray should load it as it was in the last releases

Reproducible: Always

Steps to Reproduce:
1. install a plasma theme with akonadi icon
2. anyble the theme

Actual Results:  
akonaditray still uses his normal blue icon

Expected Results:  
akonaditray should use the themes icon again
Comment 1 Daniel Vrátil 2013-11-11 16:08:54 UTC 
Could you please provide name of the specific theme that has it's own Akonadi icon?
Comment 2 FabiB 2013-11-11 16:46:23 UTC 
sure
for example caledonia -> http://caledonia.sourceforge.net/
Comment 3 Christoph Feck 2013-11-12 23:59:36 UTC 
Does process kded4 run?
Comment 4 FabiB 2013-11-13 00:06:04 UTC 
yes kded4 runs. its just for the akonadi icon since 4.11 (or maybe 4.10.. i dont remember anymore).
Comment 5 Daniel Vrátil 2013-11-13 09:29:34 UTC 
The problem is that it uses "akonaditray" icon that is shipped with the applet instead of "akonadi" icon shipped with oxygen-icons.
Comment 6 Denis Kurz 2016-09-24 20:45:47 UTC 
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 7 Denis Kurz 2017-01-07 22:28:50 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.