Bug 24198

Summary: Mageia7B2 IceWM : MCC (drakconf) launcher button does not work
Product: Mageia Reporter: magnux77 <magnux77>
Component: RPM PackagesAssignee: Martin Whitaker <mageia>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Normal CC: mageia
Version: Cauldron   
Target Milestone: ---   
Hardware: All   
OS: Linux   
See Also: https://bugs.mageia.org/show_bug.cgi?id=24263
Whiteboard:
Source RPM: dbus, xdg-compliance CVE:
Status comment:

Description magnux77 2019-01-17 16:02:14 CET 
Description of problem:
Drakconf can not be lauched by clicking on the icon. Only by command in a root console.

Version-Release number of selected component (if applicable):
Mageia 7 Beta 2

How reproducible:
Every time

Steps to Reproduce:
1.
2.
3.
magnux77 2019-01-17 16:03:05 CET

Component: RPM Packages => Installer

magnux77 2019-01-17 16:04:08 CET

Summary: Mageia7B2 IceWM : icon CCM is not active, on clic no run => Mageia7B2 IceWM : icon CCM is not active, on click : no run !

David Walser 2019-01-19 17:01:51 CET

Assignee: bugsquad => shlomif
Summary: Mageia7B2 IceWM : icon CCM is not active, on click : no run ! => Mageia7B2 IceWM : MCC (drakconf) launcher button does not work

Comment 1 Martin Whitaker 2019-01-29 23:03:39 CET 
This is an authentication problem. Running mcc from the terminal gives

[live@localhost ~]$ mcc
Too late to run INIT block at /usr/lib64/perl5/vendor_perl/Glib/Object/Introspection.pm line 257.

(mcc:3489): dbind-WARNING **: 21:56:16.182: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-T9HHaHEKBy: Connection refused
==== AUTHENTICATING FOR org.mageia.drakconf.pkexec.run ====
Authentication is required to run Mageia Control Center GUI
Authenticating as: root
polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
==== AUTHENTICATION FAILED ====
Error executing command as another user: Not authorized

Checking the environment, DBUS_SESSION_BUS_ADDRESS is not defined, and checking what's running shows

[live@localhost ~]$ ps x | grep dbus
 3443 ?        S      0:00 dbus-launch --autolaunch=6873c93bab2345c79017ef3bf2716859 --binary-syntax --close-stderr
 3444 ?        Ss     0:00 /usr/bin/dbus-daemon --syslog-only --fork --print-pid 5 --print-address 7 --session

Going back to a 6.1 Live ISO, I find

[live@localhost ~]$ env | grep dbus
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-gyAewFS0V6,guid=0bd8fb5e0207759b5120c3ae5c50c6cb
[live@localhost ~]$ ps x | grep dbus
 3417 ?        S      0:00 /usr/bin/dbus-launch --exit-with-session --sh-syntax
 3418 ?        Ss     0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
 3531 ?        S      0:00 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3

I suspect it's the dbus-launch that's at fault, but I don't know what's calling that.

CC: (none) => mageia
Component: Installer => RPM Packages

Comment 2 Martin Whitaker 2019-01-30 19:06:03 CET 
Turns out this is another case of the new redhat/brp-mangle-shebangs RPM helper quietly breaking things. Some of the scripts in /etc/X11/xinit.d did not have shebangs, so the helper removed the execute bits from the file permissions, thus stopping them from being executed by /etc/X11/Xsession.

Status: NEW => ASSIGNED
Source RPM: (none) => dbus, xdg-compliance
Assignee: shlomif => mageia

Martin Whitaker 2019-01-30 19:49:34 CET

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=24263

Comment 3 Martin Whitaker 2019-02-02 16:51:56 CET 
Fixed in the beta2 ISOs currently in QA.

Resolution: (none) => FIXED
Status: ASSIGNED => RESOLVED