Bug 16960

Summary:	The drakconf command does not do anything when ~/.kde4/env contains "export QT_NO_GLIB=1"
Product:	Mageia	Reporter:	Herman Viaene <herman.viaene>
Component:	RPM Packages	Assignee:	Mageia tools maintainers <mageiatools>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11
Version:	5
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:
Attachments:	result of strace -o mcc.txt drakconf, closed of by Ctrl-C

Description Herman Viaene 2015-10-14 10:43:10 CEST

Description of problem:
Startung drakconf from the desktop shortcut works OK (this is the command kdesu drakconf), but otherwise it is not possible to start it as a normal user.
Giving the command drakconf as a normal user at the CLI just results in a hanging shell instead of opening the dialogue for the root password.
This only happens on one of my PC's, and this one is (as the others) fully updated, thus also with the latest polkit package.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:

Comment 1 Herman Viaene 2015-10-14 12:00:58 CEST

Created attachment 7125 [details]
result of strace -o mcc.txt drakconf, closed of by Ctrl-C

Comment 2 David Walser 2015-10-14 18:23:48 CEST

Have you also rebooted since installing the systemd update?

Comment 3 Herman Viaene 2015-10-15 08:38:14 CEST

Yes, more than once.

Comment 4 Herman Viaene 2015-10-22 15:22:08 CEST

Problem solved (more or less) in the way that I noticed that the symptoms did not occur for another user on the same machine.
So I made sure I had copy of the home of my main user (where I had the problem), deleted the user (and its home), added the user again and copied only the documents, pictures, mail and browser settings from the backup. Now the problem does not occur anymore.

I can understand that KDE problems can be overcome in this way, but why calling mcc at the CLI in konsole was affected and now works again, baffles me.

Comment 5 Herman Viaene 2015-10-27 09:23:18 CET

Five days later: the problem is back again for my main user and I have no clue why. Systemwise I just applied the new updates, did not install any new package.

Comment 6 Herman Viaene 2015-10-30 09:19:35 CET

Found the reason why this problem occurs: because of KDE bug 347206, I had a workaround in ~/.kde4/env which does "export QT_NO_GLIB=1".
When I remove that one, then drakconf behaves normally.

Comment 7 Herman Viaene 2015-10-31 11:23:39 CET

See Comment 32 in KDE bug 347206, the suggestion is above me to implement.

Comment 8 Marja Van Waes 2016-10-16 17:26:11 CEST

(In reply to Herman Viaene from comment #6)
> Found the reason why this problem occurs: because of KDE bug 347206, I had a
> workaround in ~/.kde4/env which does "export QT_NO_GLIB=1".
> When I remove that one, then drakconf behaves normally.

I doubt drakconf should be able to handle that setting.

However, I'll assign to the mageiatools maintainers to decide what to do with this report.

CC: (none) => marja11
Assignee: bugsquad => mageiatools
Summary: The drakconf command does not do anything => The drakconf command does not do anything when ~/.kde4/env contains "export QT_NO_GLIB=1"

Comment 9 Marja Van Waes 2018-05-03 07:32:54 CEST

Hi Herman,

Thank you for having taken the needed time to report this issue!

We regret if this issue didn't get fixed in Mageia 5.

Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, but non-security bugs have no chance of still getting fixed.

I assume this bug doesn't exist in Mageia 6 or later, because KDE and its tools are entirely different there.

Closing as OLD.

Please reopen this report and change its "Version:" at the top left to "6", if the same bug still exists in Mageia 6.

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