Bug 964 - When using super user KDE applications (by using kdesu), those applications does not take the good widget style
Summary: When using super user KDE applications (by using kdesu), those applications d...
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: UPSTREAM
Depends on:
Blocks:
 
Reported: 2011-04-24 15:30 CEST by Lucien XU
Modified: 2011-12-25 15:32 CET (History)
2 users (show)

See Also:
Source RPM: kdebase4-runtime
CVE:
Status comment:


Attachments

Description Lucien XU 2011-04-24 15:30:06 CEST
Description of problem:
In order to have the oxygen theme everywhere, I used kdesu to tune my super user theme and selected oxygen widget style instead of iaora.
Strangely, the application does not takes the theme, and even if it is said in systemsettings that the widget style is oxygen, it is still displayed with iaora.

Version-Release number of selected component (if applicable):
KDE 4.6.2

How reproducible:
Always

Steps to Reproduce:
1. (Create the kdesu symlink if not created)
2. Use kdesu systemsettings to launch the system settings and set another widget style.
3. The application does not change and still takes the iaora theme.
Comment 1 Ahmad Samir 2011-04-25 02:27:11 CEST
The same issue is valid when using 'su -' from terminal to load kde apps as root.

It seems that the style settings aren't applied if you're not fully logged in. Test case:
- Create user a and user b
- Log into user a, then load an KDE app as user b:
$ su - b
password:
- Load systemsetting and try to change the widget style:
$ systemsetting

the changes don't have any effect.
Comment 2 Ahmad Samir 2011-04-25 07:48:02 CEST
This looks like https://bugs.kde.org/show_bug.cgi?id=267770
Comment 3 Lucien XU 2011-04-25 09:36:47 CEST
It seems that the bug has been corrected upstream but will only available in 4.7 :(
Comment 4 D Morgan 2011-04-25 10:48:05 CEST
doesn't seems fixed : https://bugs.kde.org/show_bug.cgi?id=267770#c10

CC: (none) => dmorganec

Comment 5 Ahmad Samir 2011-04-25 16:43:01 CEST
(In reply to comment #3)
> It seems that the bug has been corrected upstream but will only available in
> 4.7 :(

No, not fixed for all situations, IIUC. I've already filed https://bugs.kde.org/show_bug.cgi?id=271665
Manuel Hiebel 2011-07-27 19:32:07 CEST

Keywords: (none) => UPSTREAM
Source RPM: (none) => kdesu

Comment 6 Marja Van Waes 2011-10-10 07:09:59 CEST
Doesn't seem fixed, when looking at the upstream bug reports

CC: (none) => marja11

Manuel Hiebel 2011-10-30 01:40:39 CEST

See Also: (none) => https://bugs.kde.org/show_bug.cgi?id=267770
Source RPM: kdesu => kdebase4-runtime

Comment 7 Marja Van Waes 2011-12-23 23:20:56 CET
We have KDE version 4.7.95-1.mga2 now, and a different default theme.

Is this bug still valid?

Keywords: (none) => NEEDINFO

Comment 8 Lucien XU 2011-12-25 10:55:45 CET
The bug is still valid, but hidden. Now apps launched with kdesu will take the oxygen widget set, that is the default set, even if I change the theme to cleardots for example

It is less annoying since I'm using oxygen by default, but the bug is still not fixed
Comment 9 Marja Van Waes 2011-12-25 11:53:46 CET
(In reply to comment #8)
> The bug is still valid, but hidden. Now apps launched with kdesu will take the
> oxygen widget set, that is the default set, even if I change the theme to
> cleardots for example
> 
> It is less annoying since I'm using oxygen by default, but the bug is still not
> fixed


Thanks for replying :)

Do you agree on closing this bug as WORKSFORME or OLD (we should have the possibility to close a bug as UPSTREAM), and later reopening it, if it still annoys, after upstream comes with a patch?

Keywords: NEEDINFO => (none)

Comment 10 Lucien XU 2011-12-25 14:20:09 CET
I agree 
It is no closed as worksforme
Comment 11 Marja Van Waes 2011-12-25 15:32:11 CET
(In reply to comment #10)
> I agree 
> It is no closed as worksforme

Thx :)

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


Note You need to log in before you can comment on or make changes to this bug.