Bug 7771

Summary: KDM Theme selection screen (systemsettings--->Login Screen-->Theme) not showing downloaded themes in the list
Product: Mageia Reporter: Tim Dickerson <n9nu>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: Normal    
Version: Cauldron   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: kdm-4.9.1-1.mga3 and earlier versions CVE:
Status comment:

Description Tim Dickerson 2012-10-11 22:03:05 CEST
Description of problem:

When a user goes to download new KDM themes via the systemsettings--->login-->Theme 'Get new themes' applet, none of them show up in the theme listing as being installed. 

This has been an on-going problem for a few years now and has been reported more than once on 'bugs.kde.org', however, I was told that it has not been addressed since it was initially reported 3 years ago. 

There is a very simple solution to this issue which everyone can manually apply to resolve the problem until the next release. 

The folder listed below needs a simple permissions change to allow for themes to be displayed. As SU/root user, do the following to fix it:


$ chmod x+o /usr/apps/kdm/themes  

It should look like this:  drwxr-xrwx 13 root root 4096 Oct  5 16:07 themes/


That's it. When you go to download new themes, they will show up in the listing and can be enabled at this point. 

This has been an issue for myself for the last two (2) years while using the 64 Bit ISO/DVD Classic Installer. I was told the i586 release encountered the same issue, but have not personally verified it. 

I don't off hand know what RPM file would need to be modified to reflect the correct permissions of that folder upon install, however, one would assume the file:  kdm-4.9.1-1.mga3  would be responsible.

This bug has been reported to kde.org several times and was addressed just today at the 'mga-qa' IRC discussion. 


Tim Dickerson
N9NU
Comment 1 Manuel Hiebel 2013-03-08 02:31:27 CET
a

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

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE