Bug 229452 - Amarok doesn't follow kde color settings in playlist and context
Summary: Amarok doesn't follow kde color settings in playlist and context
Status: RESOLVED WORKSFORME
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 2.4.1
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
: 227138 234170 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-03-04 22:03 UTC by Kilian Lackhove
Modified: 2013-01-11 13:20 UTC (History)
10 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
image illustrating the bug (94.85 KB, image/png)
2010-04-09 01:49 UTC, Andrew Gaydenko
Details
unusable colors, very dark scheme (57.60 KB, image/jpeg)
2010-06-01 18:19 UTC, Suttor Ben
Details
check color roles (color scheme): text of one hue should only appear on background with the same hue. (155.93 KB, image/png)
2010-10-04 14:16 UTC, Philipp A.
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kilian Lackhove 2010-03-04 22:03:40 UTC
Version:            (using KDE 4.4.1)
OS:                Linux
Installed from:    Archlinux Packages

Amaroks playlist and colloction browser do not follow the kde color settings correctly:

The playlists background is painted in "window | normal background" and "view | alternate background". The Text is in "view | Normal text". The alternative background uses the "view | alternate background" color.

expected behavior: Amarok should use "window | alternate background" and "window | text" instead.

This problem makes amaroks playlist unusable when you tune the color setting to a dark theme but with e.g. the foder list in dolphin or text input fields white like here: http://www.kde-look.org/content/show.php/DarkDefault?content=103455
Comment 1 Myriam Schweingruber 2010-03-05 09:42:25 UTC
And what exact Amarok version are you talking about?
Comment 2 Kilian Lackhove 2010-03-05 10:55:53 UTC
i am using amarok 2.2.2-4 from archlinux extra on kde 4.4.1 form kdemod
Comment 3 Myriam Schweingruber 2010-03-05 12:08:50 UTC
There has been some work on that since 2.2.2, you should try again with Amarok 2.3, due in about 10 days and report back.
Comment 4 Kilian Lackhove 2010-03-05 14:16:23 UTC
just just cecked out amarok from git, same problem here.
Comment 5 Myriam Schweingruber 2010-03-05 15:07:14 UTC
Thank you for the feedback.
Comment 6 Andrew Gaydenko 2010-03-16 07:59:16 UTC
To developers: please, rise the bug priority as far as it's a matter of *accessibility*.
Comment 7 Andrew Gaydenko 2010-04-09 01:49:41 UTC
Created attachment 42607 [details]
image illustrating the bug

I have noticed the bug still "isn't confirmed". It seems like votes do not matter. So I have decided to attach a picture to illustrate the bug. On the picture you see awful library tree and play list colors in contrast with "official" (in accordance with color scheme) KDE colors - the window below A2 is a KMail messages list.
Comment 8 Myriam Schweingruber 2010-04-09 09:54:28 UTC
Confirmation is not done by votes, but by a second person. If our reaction is not fast enough for you, you are welcome to give a hand in bug triaging.
Comment 9 Sven Krohlas 2010-04-12 18:10:17 UTC
*** Bug 234170 has been marked as a duplicate of this bug. ***
Comment 10 Sven Krohlas 2010-04-12 18:10:48 UTC
*** Bug 227138 has been marked as a duplicate of this bug. ***
Comment 11 Christian Lichtsinn 2010-04-14 17:22:20 UTC
I have the same bug here. KDE SC 4.4.2, Amarok 2.3-GIT with "Dark Default" as colour scheme.
Comment 12 Suttor Ben 2010-04-28 18:16:02 UTC
Same here. With a very dark scheme Amarok is nearly unusable.

Amarok 2.3
KDE 4.4.2
Comment 13 Sam 2010-04-28 19:34:25 UTC
Latest beta (Amarok 2.3.1 beta1 ) fixes the problem for me.
Comment 14 Christian Lichtsinn 2010-04-29 14:02:29 UTC
Bug still exists here on Amarok 2.3-GIT with "Dark Default".
Comment 15 Andrew Gaydenko 2010-04-29 14:09:31 UTC
Myriam,

Is it possible to set the bug confirmation? It was confirmed an age ago :-)
Comment 16 Myriam Schweingruber 2010-04-30 00:21:44 UTC
It is set to NEW = confirmed since quite some time :)
Comment 17 Suttor Ben 2010-06-01 18:10:45 UTC
still the same in 2.3.1
Comment 18 Suttor Ben 2010-06-01 18:19:16 UTC
Created attachment 47570 [details]
unusable colors, very dark scheme
Comment 19 Philipp A. 2010-10-04 14:16:46 UTC
Created attachment 52216 [details]
check color roles (color scheme): text of one hue should only appear on background with the same hue.

@amarok devs:
you may want to use the color scheme “check color roles”, which should be used by every kde dev while developing custom ui elements:
http://kde-look.org/content/show.php?action=content&content=90034
Comment 20 Christoph Feck 2010-10-31 15:58:37 UTC
Wow, my color scheme has a fan ;)
Comment 21 Philipp A. 2010-10-31 16:25:25 UTC
i wish i wasn’t the only one -.-
many application developers don’t seem to care about people wanting to customize the color schemes.
Comment 22 Jaxxed 2010-12-05 04:18:53 UTC
2.3.2 Still the same problem.

I've checked out the source, but my kde skills are weak so I can find what I'm looking for.
Comment 23 Philipp A. 2010-12-06 03:24:33 UTC
i hiope it will be fixed in 2.4:
http://forum.kde.org/viewtopic.php?f=117&t=91307
Comment 24 Andrew Gaydenko 2011-04-02 11:36:13 UTC
As far as 2.4.0 is still also affected by this outstanding bug, will it be correct to change Version field to 2.4.0?
Comment 25 Jaxxed 2011-04-03 16:44:52 UTC
flying-sheep: Your theme is awesome.  It's ugly as stink, but it serves a great purpose, and should be used more by developers so that they can see what might happen to their apps in different schemes.
I didn't realize that you'd never received any appreciation.  Just because of that I showed some fan love on your theme page.
Comment 26 Philipp A. 2011-04-05 14:35:53 UTC
(In reply to comment #25)
> flying-sheep: Your theme is awesome.

i’m sure it is, but i didn’t make it. i’m only a fan of it, as it is a very useful tool.

and it really should be part of every testing procedure.
Comment 27 Myriam Schweingruber 2011-06-04 12:10:22 UTC
This is an automated message from the triager:

Amarok 2.4.1 has been released on May 8 already. Could you please upgrade and test if you can still reproduce this bug?

Without feedback within a month we will close this bug as resolved.

Thank you for your understanding.
Comment 28 Andrew Gaydenko 2011-06-04 12:56:06 UTC
Myriam, sorry, I don't understand your message. It is sufficient just to open A2 (and any standard KDE application with trees, lists and so on) to be sure the problem still exists. Have you ever opened any KDE app rather than A2? ;)
Comment 29 Myriam Schweingruber 2011-06-04 14:01:39 UTC
Andrew: if I had to test all the reported bugs that are open myself this would take a lot of time, that's why I ask people who reported the issue to test with a newer version. I don't think this is too much to ask.
So if you say A2 this is simply not precise enough.
Comment 30 Andrew Gaydenko 2011-06-04 14:15:26 UTC
Myriam, yes, v.2.4.1 is also affected by the issue.

Of course, it is our (users') task to report and verfy. I just mean for this concrete issue you would save your time just by opening the app - it takes less time rather new message in bugzilla. Nothing more. Thanks for your efforts.
Comment 31 Myriam Schweingruber 2011-06-04 15:52:19 UTC
Thank you for the fast feedback :)
Comment 32 Myriam Schweingruber 2012-10-22 02:08:29 UTC
Please check with Amarok 2.6, there have been many improvements since 2.4.x
Comment 33 Myriam Schweingruber 2013-01-11 13:20:34 UTC
Closing correctly.