Bug 6361 - QT applications look different than KDE ones when running outside of KDE
Summary: QT applications look different than KDE ones when running outside of KDE
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Nicolas Lécureuil
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2012-06-06 23:20 CEST by Ilyés Zoltán
Modified: 2013-11-23 16:13 CET (History)
4 users (show)

See Also:
Source RPM: qt4
CVE:
Status comment:


Attachments

Description Ilyés Zoltán 2012-06-06 23:20:05 CEST
Description of problem:
When I run QT applications outside of KDE (I tried with razorqt), they don't have the theme I set in KDE. I fired up qtconfig and observed that the oxygen theme is not between the selectable themes.

Because I also use Arch, and read about this on their wiki, I knew than the problem is that QT does not finds KDE's styles and a quick

export QT_PLUGIN_PATH=$HOME/.kde4/lib/kde4/plugins/:/usr/lib/kde4/plugins/

fixed the problem. I think this should be included by default in Mageia.

https://wiki.archlinux.org/index.php/Kde#KDE_and_Qt_programs_look_bad_when_in_a_different_window_manager is where I got the fix from.

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


How reproducible:
Always

Steps to Reproduce:
1.Log in to razorqt
2.Start SMplayer
3.Observe that the theme SMplayer uses is not the one Dolphin uses, for example.
Manuel Hiebel 2012-10-07 11:58:17 CEST

CC: (none) => balcaen.john, nicolas.lecureuil

Comment 1 Dainius Masiliūnas 2012-10-11 18:20:25 CEST
Confirmed both the issue and the workaround, with a note: "/usr/lib/kde4/plugins/" needs to be "/usr/lib64/kde4/plugins/" in x86_64 installations.

Additional workaround specific to Razor-qt is to go to Razor-qt's session configurator, Environment tab, and add this, if on x86_64:
Variable Name: QT_PLUGIN_PATH
Value: ${QT_PLUGIN_PATH}:/usr/lib64/kde4/plugins

CC: (none) => pastas4

Samuel Verschelde 2013-09-06 18:54:10 CEST

Keywords: (none) => Triaged
CC: (none) => stormi
Assignee: bugsquad => nicolas.lecureuil
Source RPM: (none) => qt4

Comment 2 Manuel Hiebel 2013-10-22 12:10:32 CEST
This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad
Comment 3 Manuel Hiebel 2013-11-23 16:13:58 CET
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

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


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