Bug 299946 - kde root apps follow qtconfig instead systemsettings
Summary: kde root apps follow qtconfig instead systemsettings
Status: RESOLVED DUPLICATE of bug 194449
Alias: None
Product: systemsettings
Classification: Applications
Component: general (show other bugs)
Version: 1.0
Platform: unspecified Linux
: NOR major
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-13 15:41 UTC by
Modified: 2013-04-21 16:21 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description 2012-05-13 15:41:13 UTC
When running a kde application as root i see that for example is not using the style and fonts set in systemsettings (root), but instead is using the style and fonts configured in qtconfig.

Runing kde apps as a regular user is quite different and here it does in fact follows the definitions set in systemsettings.

Reproducible: Always

Steps to Reproduce:
Login as root as run a kde application, and will not use the definitions set in systemsettings (set as root).

To change for example the style of a kde app run as root, also as root run qtconfig and change the style.
Actual Results:  
Runing systemsettings as root and setting a style will not make any difference for the kde apps run as root.

Expected Results:  
The kde apps run as root should follow whats set in systemsettings as root.
Comment 1 Christoph Feck 2012-05-13 22:55:52 UTC
The general idea is to never let KDE applications run as root, but instead use the KAuth framework to let them execute certain actions that require root privileges.

If you know of KDE applications that currently require running as root instead of using KAuth, please report a bug for those applications. For example, see bug 259678 for partitionmanager.
Comment 2 2012-05-13 23:06:38 UTC
I also agree on that but isnt related with this bug.
Comment 3 Christoph Feck 2013-04-21 16:21:58 UTC

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