Description of problem: InYesterday I used kde4 for a change, configuring lots of stuff and in the end find a file written to /.config/Trolltech.conf with following content: [Qt%20Plugin%20Cache%204.7.false] usr\lib64\kde4\plugins\kauth\backend\kauth_backend_plugin.so=40704, 0, x86_64 linux g++-4 full-config, 2011-09-07T11:52:42 usr\lib64\kde4\plugins\kauth\helper\kauth_helper_plugin.so=40704, 0, x86_64 linux g++-4 full-config, 2011-09-07T11:52:42 (Yes it was created 12/9 as per 'stat', not 7/9 as per content!) It shouldn't write such stuff to the root of the filesystem.
Assignee: bugsquad => balcaen.john
Trolltech.conf is a Qt file not a kde4 file.
CC: (none) => balcaen.john
I could only judge by the content of the conf file: obvously the file itself isn't included in any package. rpm -qf /usr/lib64/kde4/plugins/kauth/backend/kauth_backend_plugin.so kdelibs4-core-4.7.1-1.mga2 but feel free to reassign to proper package.
It's wrote in /root/.config/Trolltech.conf because a Qt related app (the kauth backend here) was run as root probably because you did auth yourself to change some root related settings (via polkit eventually). So if you want to prevent this behavior (write a conf file when there's no config file available) you should report it upstream but i guess it's going to be close as invalid because it's certainly a expected behavior from kdelibs or Qt.
I don't think I did anything as root in KDE, only as user. And it's not in /root but in the root of the filesystem, i.e. "/" ....
What did you use to get the auth plugin working ? Hum here it's quite strange to be @ / :/ If you can reproduce could provide us a way to reproduce ? (aka what did you do in systemsettings ? )
In fact it's more complicated then expected cf the upstream bug.
Keywords: (none) => UPSTREAMSee Also: (none) => https://bugs.kde.org/show_bug.cgi?id=249217
This is a duplicate of #1854 or vice versa.
*** Bug 1854 has been marked as a duplicate of this bug. ***
CC: (none) => jim
Setting version to 1 since Mageia 1 is also affected.
CC: (none) => stormiHardware: x86_64 => AllVersion: Cauldron => 1
Note https://bugs.mageia.org/show_bug.cgi?id=1854#c4 The file /.config/Trolltech.conf _may_ be created during the installation of kdebase4-workspace. It's inconsistent though, which will make tracking down the cause very difficult.
CC: (none) => davidwhodgins
The upstream bug report has 275 votes, but didn't get fixed
CC: (none) => marja11
still not fixed upstream
Version: 1 => 2Severity: normal => minor
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
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 => RESOLVEDResolution: (none) => OLD