Bug 339849 - Can't set breeze dark color scheme
Summary: Can't set breeze dark color scheme
Status: RESOLVED FIXED
Alias: None
Product: Breeze
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Development Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-10 17:38 UTC by Antonio Rojas
Modified: 2014-10-15 08:44 UTC (History)
3 users (show)

See Also:
Latest Commit: http://commits.kde.org/breeze/f58e7d0523f1c93a74046d9ecac82c72f0068c89
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 Antonio Rojas 2014-10-10 17:38:25 UTC 
Choosing the Breeze Dark color scheme in the colors KCM doesn't work. It throws the error: "QFile::copy: Empty or null file name". Doesn't seem to happen with any other color scheme

Reproducible: Always
Comment 1 Andrew Lake 2014-10-10 17:54:56 UTC 
Hmm, the only thing I can think of is that maybe the "ColorScheme" key should have the same name as the .colors file? In this case "Breeze-Dark" instead of "Breeze Dark".  Would that cause this problem?
Comment 2 Antonio Rojas 2014-10-10 18:01:59 UTC 
Changing the file name from Breeze-Dark.colors to BreezeDark.colors fixes this.
Comment 3 Andrew Lake 2014-10-11 06:23:30 UTC 
I changed the filename as suggested and made the commit. I don't have permissions to close this bug.
Comment 4 Bhushan Shah 2014-10-11 06:25:12 UTC 
I think someone should give you rights for that..
Comment 5 Hugo Pereira Da Costa 2014-10-15 06:58:30 UTC 
Git commit f58e7d0523f1c93a74046d9ecac82c72f0068c89 by Hugo Pereira Da Costa, on behalf of Andrew Lake.
Committed on 11/10/2014 at 06:16.
Pushed by hpereiradacosta into branch 'hpereira/kwin-decoration'.

rename Breeze-Dark.colors to BreezeDark.colors

M  +1    -1    CMakeLists.txt
R  +0    -0    colors/BreezeDark.colors [from: colors/Breeze-Dark.colors - 100% similarity]

http://commits.kde.org/breeze/f58e7d0523f1c93a74046d9ecac82c72f0068c89
Comment 6 Jonathan Riddell 2014-10-15 08:44:08 UTC 
this was fixed in the final 5.1 packages (versioned 5.1.0.1)