Bug 16597 - After login to LXQt there is shown error GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed
Summary: After login to LXQt there is shown error GDBus.Error:org.freedesktop.PolicyKi...
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: Florian Hubold
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-17 20:02 CEST by Piotr Mierzwinski
Modified: 2015-10-19 18:45 CEST (History)
3 users (show)

See Also:
Source RPM: lxsession-0.5.1-6.mga5
CVE:
Status comment:


Attachments
journal for black screen (133.33 KB, text/plain)
2015-10-16 22:42 CEST, Piotr Mierzwinski
Details
systemclt status for black screen (1.73 KB, text/plain)
2015-10-16 22:42 CEST, Piotr Mierzwinski
Details
journal for manually run sddm (138.90 KB, text/plain)
2015-10-16 22:43 CEST, Piotr Mierzwinski
Details
systemclt status for maually run sddm (1.43 KB, text/plain)
2015-10-16 22:43 CEST, Piotr Mierzwinski
Details

Description Piotr Mierzwinski 2015-08-17 20:02:57 CEST
Description of problem:
After login to LXQt appears window with following error message:
"Cannot register authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: User of caller and user of subject differs."

Due to this error I can't run any applications requiring root privileges.
For example I'm not able to start update when update pops up on task bar (the most likely this is mgaapplet). I can't start neither rpmdrake nor mcc being regular user.

Some workaround is running lxqt-policykit-agent being logged as root.


Version-Release number of selected component (if applicable):
lxqt-policykit-0.9.0-1.mga5.i586.rpm
Mageia Cauldron 

How reproducible:
everytime

Steps to Reproduce:
1. start Mageia in text mode
2. login as root
3. start sddm
4. login as reqular user to LXQt session



Reproducible: 

Steps to Reproduce:
Comment 1 Piotr Mierzwinski 2015-08-17 20:16:25 CEST
Update for running processes and services:

$ systemctl status polkit.service
â polkit.service - Authorization Manager
   Loaded: loaded (/usr/lib/systemd/system/polkit.service; static; vendor preset: enabled)
   Active: active (running) since pon 2015-08-17 20:08:47 CEST; 41s ago
     Docs: man:polkit(8)
 Main PID: 2545 (polkitd)
   CGroup: /system.slice/polkit.service
           ââ2545 /usr/lib/polkit-1/polkitd --no-debug

sie 17 20:08:45 localhost.localdomain systemd[1]: Starting Authorization Manager...
sie 17 20:08:46 localhost.localdomain polkitd[2545]: Started polkitd version 0.113
sie 17 20:08:47 localhost.localdomain polkitd[2545]: Loading rules from directory /etc/polkit-1/rules.d
sie 17 20:08:47 localhost.localdomain polkitd[2545]: Loading rules from directory /usr/share/polkit-1/rules.d
sie 17 20:08:47 localhost.localdomain polkitd[2545]: Finished loading, compiling and executing 3 rules
sie 17 20:08:47 localhost.localdomain polkitd[2545]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
sie 17 20:08:47 localhost.localdomain systemd[1]: Started Authorization Manager.
$ ps -ef | grep polkit | grep -v grep
piotr     2524     1  0 20:08 ?        00:00:00 /usr/bin/lxpolkit
polkitd   2545     1  0 20:08 ?        00:00:00 /usr/lib/polkit-1/polkitd --no-debug


And when I try to run the agent manually (as regular user) then I get:
$ lxqt-policykit-agent
iconTheme "oxygen"
Theme: Cannot open file for reading: "/usr/share/lxqt/themes/Mga-plasma/lxqt-policykit-agent.qss"
New PolkitAgentListener  0x9105430
Adding new listener  PolkitQt1::Agent::Listener(0xbfb8ac38) for  0x9105430

** (process:3219): WARNING **: Unable to register authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: User of caller and user of subject differs.
"Cannot register authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: User of caller and user of subject differs."
Comment 2 David Walser 2015-08-25 23:22:13 CEST
Looks like a problem with lxpolkit (the policykit agent).

Assignee: bugsquad => doktor5000

Comment 3 Florian Hubold 2015-08-26 20:12:57 CEST
FWIW, lxpolkit is the LXDE polkit agent, provided by lxsession, which is required by lxde-common. Even then, this works fine here with lxpolkit and lxqt. Adding the lxsession maintainer in CC as I cannot reproduce.


(In reply to Piotr Mierzwinski from comment #0)
> Steps to Reproduce:
> 1. start Mageia in text mode
> 2. login as root
> 3. start sddm
> 4. login as reqular user to LXQt session

Hi there, how exactly do you start sddm or the X session?

Cannot reproduce here with a fresh mga5 install. Added "3" to the kernel options to start in runlevel 3, and then run sddm with "systemctl start prefdm.service" after choosing it via drakdm. This is what it looks like in the X session:


[user@localhost ~]$ systemctl status polkit.service -a
â polkit.service - Authorization Manager
   Loaded: loaded (/usr/lib/systemd/system/polkit.service; static)
   Active: active (running) since Mi 2015-08-26 19:53:54 CEST; 24s ago
     Docs: man:polkit(8)
 Main PID: 2074 (polkitd)
   CGroup: /system.slice/polkit.service
           ââ2074 /usr/lib/polkit-1/polkitd --no-debug

[user@localhost ~]$ ps -ef | grep polkit
polkitd   2074     1  0 19:53 ?        00:00:00 /usr/lib/polkit-1/polkitd --no-debug
user      2161     1  0 19:53 ?        00:00:00 /bin/lxpolkit
user      2479  2406  0 19:54 pts/0    00:00:00 grep --color polkit
[user@localhost ~]$

[user@localhost ~]$ loginctl 
   SESSION        UID USER             SEAT            
        c1       1000 user             seat0           
        c3        983 sddm             seat0           
        c4       1000 user             seat0           

3 sessions listed.
[user@localhost ~]$ loginctl session-status c4
c4 - user (1000)
           Since: Mi 2015-08-26 19:53:54 CEST; 18min ago
          Leader: 1995 (sddm-helper)
            Seat: seat0; vc1
         Display: :0
         Service: sddm; type x11; class user
           State: active
            Unit: session-c4.scope
                  ââ1995 /usr/libexec/sddm-helper --socket /tmp/sddm-auth1f91e904-d256-4091-b6da-fe6fa6236705 --id 1 --start LXQT --user user
                  ââ1997 lxqt-session
                  ââ2064 /usr/bin/dbus-launch --exit-with-session --sh-syntax
                  ââ2065 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
                  ââ2101 /usr/bin/VBoxClient --clipboard
                  ââ2102 /usr/bin/VBoxClient --clipboard
                  ââ2119 /usr/bin/VBoxClient --display
                  ââ2120 /usr/bin/VBoxClient --display
                  ââ2124 /usr/bin/VBoxClient --seamless
                  ââ2125 /usr/bin/VBoxClient --seamless
                  ââ2128 /usr/bin/VBoxClient --draganddrop
                  ââ2129 /usr/bin/VBoxClient --draganddrop
                  ââ2147 s2u --daemon=yes
                  ââ2158 openbox
                  ââ2161 /bin/lxpolkit
                  ââ2162 pcmanfm-qt --desktop --profile=lxqt
                  ââ2163 lxqt-globalkeysd
                  ââ2164 lxqt-notificationd
                  ââ2165 lxqt-panel
                  ââ2166 lxqt-policykit-agent
                  ââ2168 /bin/qlipper
                  ââ2171 lxqt-runner
                  ââ2173 /bin/xscreensaver -no-splash
                  ââ2176 /usr/bin/perl /usr/bin/mgaapplet
                  ââ2184 /usr/bin/perl /usr/bin/net_applet
                  ââ2194 /usr/libexec/gvfs-udisks2-volume-monitor
                  ââ2206 /usr/libexec/gvfsd
                  ââ2213 /usr/libexec/menu-cache/menu-cached /tmp/.menu-cached-:0-user
                  ââ2215 /usr/libexec/menu-cache/menu-cached /tmp/.menu-cached-:0-user
                  ââ2232 /usr/libexec/gvfs-afc-volume-monitor
                  ââ2238 /usr/libexec/gvfs-goa-volume-monitor
                  ââ2241 /usr/libexec/goa-daemon
                  ââ2246 /usr/libexec/at-spi-bus-launcher
                  ââ2247 /usr/libexec/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes
                  ââ2265 /usr/bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork --print-address 3
                  ââ2268 /usr/libexec/at-spi2-registryd --use-gnome-session
                  ââ2280 /usr/libexec/mission-control-5
                  ââ2282 /usr/libexec/gvfs-gphoto2-volume-monitor
                  ââ2289 /usr/libexec/gvfs-mtp-volume-monitor
                  ââ2328 lxqt-powermanagement
                  ââ2403 /bin/qterminal
                  ââ2406 /bin/bash
                  ââ3198 loginctl session-status c4
                  ââ3199 /usr/bin/less -FR
[user@localhost ~]$



A simple polkit test works just fine, authorisation dialog shows up and works:

[user@localhost ~]$ pkexec whoami
root


Please also provide the output of "loginctl" in your user session, and from "loginctl session-status" for the sessions you see.

Status: NEW => UNCONFIRMED
CC: (none) => doktor5000, nicolas.salguero
Ever confirmed: 1 => 0

Florian Hubold 2015-08-26 20:13:52 CEST

Source RPM: lxqt-policykit-0.9.0-1.mga5.i586.rpm => lxsession-0.5.1-6.mga5

Comment 4 Florian Hubold 2015-08-26 20:16:41 CEST
Sorry, just saw that now:

(In reply to Piotr Mierzwinski from comment #1)
> $ ps -ef | grep polkit | grep -v grep
> piotr     2524     1  0 20:08 ?        00:00:00 /usr/bin/lxpolkit
                                                           ^^^^^^^^
There's already one polkit agent running, the one from lxde, and you try to start a different one. I don't think that's supported. And lxpolkit was installed for me by default, and works just fine in your described test case.


> And when I try to run the agent manually (as regular user) then I get:
> $ lxqt-policykit-agent
> iconTheme "oxygen"
> Theme: Cannot open file for reading:
> "/usr/share/lxqt/themes/Mga-plasma/lxqt-policykit-agent.qss"
> New PolkitAgentListener  0x9105430
> Adding new listener  PolkitQt1::Agent::Listener(0xbfb8ac38) for  0x9105430
> 
> ** (process:3219): WARNING **: Unable to register authentication agent:
> GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: User of caller and user
> of subject differs.
> "Cannot register authentication agent:
> GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: User of caller and user
> of subject differs."
Comment 5 Piotr Mierzwinski 2015-08-27 00:04:11 CEST
I've installed lxqt using task-lxqt-minimal and after that I installed additional packages from lxqt. Below you can find the list:
$ rpm -qa|grep lxqt | sort
liblxqt0-0.9.0-1.mga5
liblxqt-globalkeys0-0.9.0-1.mga5
liblxqt-globalkeys-ui0-0.9.0-1.mga5
liblxqt-mount0-0.9.0-1.mga5
lxqt-about-0.9.0-1.mga5
lxqt-common-0.9.1-3.mga5
lxqt-config-0.9.0-1.mga5
lxqt-globalkeys-0.9.0-1.mga5
lxqt-notificationd-0.9.0-2.mga5
lxqt-openssh-askpass-0.9.0-1.mga5
lxqt-panel-0.9.0-4.mga5
lxqt-policykit-0.9.0-1.mga5
lxqt-powermanagement-0.9.0-2.mga5
lxqt-qtplugin-0.9.0-1.mga5
lxqt-runner-0.9.0-1.mga5
lxqt-session-0.9.0-2.mga5
task-lxqt-minimal-0.9.0-1.mga5

sddm
I login to Mageia to text terminal (runlevel 3), login as root and just execute sddm from command line. As far as I remember I didn't set prefdm manually.

(In reply to Florian Hubold from comment #4)
> > $ ps -ef | grep polkit | grep -v grep
> > piotr     2524     1  0 20:08 ?        00:00:00 /usr/bin/lxpolkit
>                                                           ^^^^^^^^
> There's already one polkit agent running, the one from lxde, and you try to start a
> different one. I don't think that's supported. And lxpolkit was installed for me by
> default, and works just fine in your described test case.

Yes. It's running in moment of login to lxqt session. And probably it caused the error message. I was trying to start another one because (as I mentioned earlier) I wasn't able to run update and rpmdrake being logged as regular user (using Alt+F2). The issue is how to turn off this agent and start the correct one. Or maybe it's enough to disable and enable prefdm service. I didn't try. I next post I will tell about this.


[piotr@localhost ~]$ systemctl status polkit.service -a
â polkit.service - Authorization Manager
   Loaded: loaded (/usr/lib/systemd/system/polkit.service; static; vendor preset: enabled)
   Active: active (running) since Åro 2015-08-26 23:08:45 CEST; 6min ago
     Docs: man:polkit(8)
 Main PID: 2224 (polkitd)
   CGroup: /system.slice/polkit.service
           ââ2224 /usr/lib/polkit-1/polkitd --no-debug

[piotr@localhost ~]$ ps -ef|grep polk
piotr     2202     1  0 23:08 ?        00:00:00 /usr/bin/lxpolkit
polkitd   2224     1  0 23:08 ?        00:00:00 /usr/lib/polkit-1/polkitd --no-debug
piotr     2663  2535  0 23:12 pts/1    00:00:00 grep --color polk

[piotr@localhost ~]$ loginctl
   SESSION        UID USER             SEAT            
        c1          0 root             seat0  

[piotr@localhost ~]$ loginctl session-status c1
c1 - root (0)
           Since: Åro 2015-08-26 23:07:21 CEST; 11min ago
          Leader: 792 (login)
            Seat: seat0; vc1
             TTY: tty1
         Service: login; type tty; class user
           State: active
            Unit: session-c1.scope
                  ââ 792 login -- root     
                  ââ1955 -bash
                  ââ2006 gpg-agent --keep-display --daemon --write-env-file /root/.gnupg/gpg-agent-info
                  ââ2024 sddm
                  ââ2026 /etc/X11/X :0 -auth /var/run/sddm/:0 -nolisten tcp -background none -noreset vt1
                  ââ2043 /usr/bin/dbus-launch --autolaunch 79cd35449d76421dab98195223ba95b9 --binary-syntax --close-stderr
                  ââ2044 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
                  ââ2045 /usr/libexec/sddm-helper --socket /tmp/sddm-auth9a5aa524-2d47-439e-a9f7-db9aa373a469 --id 1 --sta
                  ââ2046 lxqt-session
                  ââ2082 gpg-agent --keep-display --daemon --write-env-file /home/piotr/.gnupg/gpg-agent-info
                  ââ2119 /usr/bin/dbus-launch --exit-with-session --sh-syntax
                  ââ2120 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 15 --session
                  ââ2134 /usr/bin/VBoxClient --clipboard
                  ââ2135 /usr/bin/VBoxClient --clipboard
                  ââ2144 /usr/bin/VBoxClient --display
                  ââ2145 /usr/bin/VBoxClient --display
                  ââ2149 /usr/bin/VBoxClient --seamless
                  ââ2150 /usr/bin/VBoxClient --seamless
                  ââ2156 /usr/bin/VBoxClient --draganddrop
                  ââ2157 /usr/bin/VBoxClient --draganddrop
                  ââ2189 s2u --daemon=yes
                  ââ2199 openbox
                  ââ2202 /usr/bin/lxpolkit
                  ââ2203 pcmanfm-qt --desktop --profile=lxqt
                  ââ2204 lxqt-globalkeysd
                  ââ2205 lxqt-notificationd
                  ââ2206 lxqt-panel
                  ââ2207 lxqt-policykit-agent
                  ââ2209 /usr/bin/qlipper
                  ââ2213 lxqt-runner
                  ââ2215 /usr/bin/xscreensaver -no-splash
                  ââ2217 /usr/bin/perl /usr/bin/mgaapplet
                  ââ2226 /usr/bin/perl /usr/bin/net_applet
                  ââ2238 /usr/libexec/gvfsd
                  ââ2244 /usr/libexec/menu-cache/menu-cached /tmp/.menu-cached-:0-piotr
                  ââ2254 /usr/libexec/gvfsd-fuse /home/piotr/.gvfs -f -o big_writes
                  ââ2271 /usr/libexec/gvfs-udisks2-volume-monitor
                  ââ2282 /usr/libexec/gvfs-gphoto2-volume-monitor
                  ââ2291 /usr/libexec/gvfs-goa-volume-monitor
                  ââ2293 /usr/libexec/at-spi-bus-launcher
                  ââ2314 /usr/bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork --print-address 3
                  ââ2316 /usr/libexec/at-spi2-registryd --use-gnome-session
                  ââ2325 /usr/libexec/gvfs-mtp-volume-monitor
                  ââ2332 /usr/libexec/gvfs-afc-volume-monitor
                  ââ2351 lxqt-powermanagement
                  ââ2367 /usr/bin/qterminal
                  ââ2370 /bin/bash
                  ââ2439 su -
                  ââ2442 -bash
                  ââ2497 /usr/bin/perl /usr/libexec/drakrpm
                  ââ2535 /bin/bash
                  ââ2928 loginctl session-status c1
                  ââ2929 /usr/bin/less -FR

And authorisation test doesn't work.

[piotr@localhost ~]$ pkexec whoami
==== AUTHENTICATING FOR org.freedesktop.policykit.exec ===
Authentication is needed to run `/usr/bin/whoami' as the super user                                                       
Authenticating as: root
Password: 
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                                                                   

This incident has been reported.
Comment 6 Piotr Mierzwinski 2015-08-27 00:27:55 CEST
Update. As I promised.
Being logged in text terminal I performed:
$ systemctl disable prefdm.service && systemctl enable sddm.service
$ reboot

Being in run-level-3 I logged in as root. I was tried run prefdm like you. So I called:
$ systemctl start prefdm.service
Result was black screen. I was waiting couple of minutes and rebooted system.

Next try was with:
$ systemctl start sddm.service
Result the same - black screen. I was waiting couple of minutes and rebooted system.
Finally after login as root I just run sddm from command line and I got login screen. Unfortunately after login to lxqt I met the same error message. :(
Comment 7 Florian Hubold 2015-10-04 17:22:26 CEST
(In reply to Piotr Mierzwinski from comment #6)
> Finally after login as root I just run sddm from command line and I got
> login screen. Unfortunately after login to lxqt I met the same error
> message. :(

That is your problem, the way you start your X session - then your root session will probably be considered active and in the foreground by logind/polkit, and your user session not. You should try to find out why neither prefdm nor sddm start for you.

journalctl -ab | tail -150

during the time when sddm or prefdm show only a black screen will most certainly help with that.
Comment 8 papoteur 2015-10-15 13:42:40 CEST
Hello,
I have the same problem with LXQt in cauldron.
I didn't configure anything as DM.

ps -ef | grep polkit | grep -v grep
polkitd   1998     1  0 10:01 ?        00:00:00 /usr/lib/polkit-1/polkitd --no-debug
yves      2083     1  0 10:01 ?        00:00:00 /bin/lxpolkit

loginctl
   SESSION        UID USER             SEAT            
        c1       1000 yves             seat0           

1 sessions listed.

systemctl status polkit.service -a
â polkit.service - Authorization Manager
   Loaded: loaded (/usr/lib/systemd/system/polkit.service; static; vendor preset: enabled)
   Active: active (running) since jeu. 2015-10-15 09:47:31 CEST; 3h 50min ago
     Docs: man:polkit(8)
 Main PID: 1998 (polkitd)
   CGroup: /system.slice/polkit.service
           ââ1998 /usr/lib/polkit-1/polkitd --no-debug
$ systemctl status polkit.service -a
â polkit.service - Authorization Manager
   Loaded: loaded (/usr/lib/systemd/system/polkit.service; static; vendor preset: enabled)
   Active: active (running) since jeu. 2015-10-15 09:47:31 CEST; 3h 50min ago
     Docs: man:polkit(8)
 Main PID: 1998 (polkitd)
   CGroup: /system.slice/polkit.service
           ââ1998 /usr/lib/polkit-1/polkitd --no-debug
[yves@localhost ~]$ loginctl session-status c1
c1 - yves (1000)
           Since: jeu. 2015-10-15 09:47:28 CEST; 3h 51min ago
          Leader: 1864 (lxdm-session)
            Seat: seat0; vc1
             TTY: tty1
         Service: lxdm; type x11; class user
           State: active
            Unit: session-c1.scope
                  ââ1864 /usr/libexec/lxdm-session
                  ââ1873 lxqt-session
                  ââ1934 ssh-agent
                  ââ1955 gpg-agent --keep-display --daemon --write-env-f
                  ââ1988 /usr/bin/dbus-launch --exit-with-session --sh-s
                  ââ1989 /usr/bin/dbus-daemon --fork --print-pid 5 --pri
                  ââ2016 /usr/bin/VBoxClient --clipboard
                  ââ2018 /usr/bin/VBoxClient --clipboard
                  ââ2026 /usr/bin/VBoxClient --display
                  ââ2028 /usr/bin/VBoxClient --display
                  ââ2031 /usr/bin/VBoxClient --seamless
                  ââ2033 /usr/bin/VBoxClient --seamless
                  ââ2036 /usr/bin/VBoxClient --draganddrop
                  ââ2037 /usr/bin/VBoxClient --draganddrop
                  ââ2065 s2u --daemon=yes
                  ââ2080 openbox
                  ââ2083 /bin/lxpolkit
                  ââ2084 pcmanfm-qt --desktop --profile=lxqt
                  ââ2085 lxqt-globalkeysd
                  ââ2086 lxqt-notificationd
                  ââ2087 lxqt-panel
                  ââ2088 lxqt-policykit-agent
                  ââ2090 /bin/qlipper
                  ââ2095 lxqt-runner
                  ââ2097 /usr/bin/perl /usr/bin/mgaapplet
                  ââ2099 /usr/bin/perl /usr/bin/net_applet
                  ââ2117 /usr/libexec/gvfsd
                  ââ2120 /usr/libexec/menu-cache/menu-cached /home/yves/
                  ââ2126 /usr/libexec/gvfs-udisks2-volume-monitor
                  ââ2169 /usr/libexec/at-spi-bus-launcher
                  ââ2175 /usr/bin/dbus-daemon --config-file=/etc/at-spi2
                  ââ2177 /usr/libexec/at-spi2-registryd --use-gnome-sess
                  ââ2190 lxqt-powermanagement
                  ââ8754 /bin/qterminal
                  ââ8756 /bin/bash
                  ââ8969 loginctl session-status c1
                  ââ8970 /usr/bin/less -FR

oct. 15 10:06:33 localhost pkexec[2371]: pam_systemd(polkit-1:session): 
oct. 15 10:06:33 localhost pkexec[2371]: pam_tcb(polkit-1:session): Sess
oct. 15 10:06:35 localhost mgaapplet[2097]: no update media configured
oct. 15 13:06:33 localhost mgaapplet[2097]: Computing new updates...
oct. 15 13:06:33 localhost mgaapplet[2097]: running: mgaapplet-update-ch
oct. 15 13:06:33 localhost mgaapplet-update-checker[7858]: ### Program i
oct. 15 13:06:33 localhost mgaapplet-update-checker[7858]: running: urpm
oct. 15 13:06:33 localhost pkexec[7865]: pam_systemd(polkit-1:session): 
oct. 15 13:06:33 localhost pkexec[7865]: pam_tcb(polkit-1:session): Sess
oct. 15 13:06:37 localhost mgaapplet[2097]: no update media configured

CC: (none) => yves.brungard_mageia

Comment 9 Florian Hubold 2015-10-15 21:43:28 CEST
(In reply to papoteur from comment #8)

> ps -ef | grep polkit | grep -v grep
> polkitd   1998     1  0 10:01 ?        00:00:00 /usr/lib/polkit-1/polkitd
> --no-debug
> yves      2083     1  0 10:01 ?        00:00:00 /bin/lxpolkit
> 

> [yves@localhost ~]$ loginctl session-status c1
[...]
>                   ââ2083 /bin/lxpolkit
[...]
>                   ââ2088 lxqt-policykit-agent


There are two polkit agents running in parallel.
I believe this might be a problem, didn't see this earlier in the vast output, but I've adjusted my grep instructions now. Can you try disabling autostart for either one of those so you end up with only one polkit agent? Should be sufficient moving away either /etc/xdg/autostart/lxpolkit.desktop or /etc/xdg/autostart/lxqt-policykit-agent.desktop and then rebooting.

We should probably turn the "NotShowIn=GNOME;KDE;MATE;XFCE;OPENBOX;Old;" to "OnlyShowIn=LXDE" to resolve this conflict. Will also have to check why you end up with lxpolkit on minimal installation with only LXQt.

Ever confirmed: 0 => 1
Status: UNCONFIRMED => ASSIGNED

Comment 10 Piotr Mierzwinski 2015-10-16 03:16:23 CEST
(In reply to Florian Hubold from comment #7)
> (In reply to Piotr Mierzwinski from comment #6)
> > Finally after login as root I just run sddm from command line and I got
> > login screen. Unfortunately after login to lxqt I met the same error
> > message. :(
> 
> That is your problem, the way you start your X session - then your root
> session will probably be considered active and in the foreground by
> logind/polkit, and your user session not. You should try to find out why
> neither prefdm nor sddm start for you.
> 
> journalctl -ab | tail -150
> 
> during the time when sddm or prefdm show only a black screen will most
> certainly help with that.

The way I start my X session (manually running sddm) is caused that in other (the valid one) it makes I get black screen :(, so this is the only way when I'm able to get X session.

When I set symlink "default.target" (/etc/systemd/system) to runlevel5.target then after restart sddm is run. The service polkit doesn't. And If now I stop sddm, start polkit and again start sddm then I get black screen again.

Now in moment when black screen is active the polkitd is runnnig.
$ loginctl
   SESSION        UID USER             SEAT            
        c4        982 sddm             seat0

$ loginctl session-status c4
shows me quite short output (comparing to this one in earlier post), as following:
         Display: :0
         Service: sddm-greeter; type X11; class greeter
           State: closing
Running units are following: dbus-launch, dbus-daemon
In logs below I can see some warning about "Unrecognized OpenGL session"
I'm not sure is this the root cause, because when I call sddm manually it starts and I'm able to get login screen.

In systemd logs I can see  that (please read starting from end of list)
       info (coming from sddm): "Greeter stopped".
before info (coming from sddm): "Auth: sddm-helper exited with 11"
before info (coming from sddm-greeter): "Unrecognized OpenGL session", 
before info (coming from sddm): "Message received from greeter: Connect",
before info (coming from sddm-greeter): "Reading from /usr/..." - couple of time
before info (coming from sddm): Greeter session started successfully

Reading earlier the logs I can find out that session c4 is started for user sddm. sddm-helper is telling me that session opened for user sddm by (uid=0)
and before sddm is telling me about running the Greeter.

I've filtered logs by sddm and I can see only one suspect and this is the message: "Auth: sddm-helper exited with 11".
So the most likely I'm gettng black screen as result of this message :/. Of course I'm not sure. This is only my suspicion.

Could you tell me on what messages should I pay my attention?
I'm not expert in systemd and starting DM :/. For kdm it worked, and here doesn't. Still black screen :(. Running sddm manually works, but this is not the point and then I get polkit problems :/. In advance thank you for any help.
Comment 11 Florian Hubold 2015-10-16 20:56:26 CEST
(In reply to Piotr Mierzwinski from comment #10)

> The way I start my X session (manually running sddm) is caused that in other
> (the valid one) it makes I get black screen :(, so this is the only way when
> I'm able to get X session.
> 
> When I set symlink "default.target" (/etc/systemd/system) to
> runlevel5.target then after restart sddm is run. The service polkit doesn't.
> And If now I stop sddm, start polkit and again start sddm then I get black
> screen again.

Well, I'm using sddm together with prefdm and polkit starts just fine. Please do as you mentioned above, and when sddm is running, try to login as your normal user, wait a minute or so, then please switch to another tty via Ctrl+Alt+F2, and as root run
journalctl -ab > journal.log
and attach the file journal.log here.
Comment 12 Piotr Mierzwinski 2015-10-16 22:42:16 CEST
Created attachment 7128 [details]
journal for black screen
Comment 13 Piotr Mierzwinski 2015-10-16 22:42:59 CEST
Created attachment 7129 [details]
systemclt status for black screen
Comment 14 Piotr Mierzwinski 2015-10-16 22:43:30 CEST
Created attachment 7130 [details]
journal for manually run sddm
Comment 15 Piotr Mierzwinski 2015-10-16 22:43:57 CEST
Created attachment 7131 [details]
systemclt status for maually run sddm
Comment 16 Piotr Mierzwinski 2015-10-16 22:45:08 CEST
OK. So I logged in as root on tty1. I've started sddm. I've logged in via sddm as 
"normal user" (piotr) to lxqt session. Switched to tty2 and prepared the logs.
I've prepared also logs and systemctl status for session with black screen (Mageia starts to runlevel5). Second pair is what you asked me additional systemctl status.

In this test I was used following packages:
- sddm-0.12.0-1
- polkit-0.113-2
- polkit-kde-agent-1-5.4.2-1
I have no installed neiter polkit-agent-none nor polkit-qt-1-devel
Comment 17 papoteur 2015-10-17 09:01:55 CEST
(In reply to Florian Hubold from comment #9)
> (In reply to papoteur from comment #8)
>> Will also have to check why you
> end up with lxpolkit on minimal installation with only LXQt.

I have also XFCE and LXDE installed.
Comment 18 Florian Hubold 2015-10-18 15:50:18 CEST
@Piotr: You're testing under virtualbox, you should have mentioned that in the beginning. It can cause issues with anything that tries to use OpenGL if you have hardware acceleration enabled or if the vboxvideo drivers or libGL are not working properly - which happens often.

Totally apart from that, can you please switch your system back to the default boot to graphical.target and then try another display manager like kdm? Simply install kdm and choose it via drakdm, then reboot. The following commands should do it:

systemctl set-default runlevel5.target
urpmi kdm
drakdm
reboot

Can't really help you with your current issue, as I cannot reproduce. I'm using sddm, and I have several virtualbox installations that also use sddm, and none of them shows the issues you describe, so this might be caused by some local modifications.
Comment 19 Florian Hubold 2015-10-18 15:53:25 CEST
(In reply to papoteur from comment #17)
> (In reply to Florian Hubold from comment #9)
> > (In reply to papoteur from comment #8)
> >> Will also have to check why you
> > end up with lxpolkit on minimal installation with only LXQt.
> 
> I have also XFCE and LXDE installed.

Doesn't matter. I need to find out why this happens on a minimal installation - if you have more then a minimal installation the chances are simply higher, and if you have LXDE installation the chances are near 100% that you will get the LXDE polkit agent installed.

You could try with fix your issue as root via:

sed -i 's|NotShowIn=.*|OnlyShowIn=LXDE;|g' /etc/xdg/autostart/lxpolkit.desktop
Comment 20 Piotr Mierzwinski 2015-10-19 00:07:25 CEST
@Florian
It was seen in this log: "[piotr@localhost ~]$ loginctl session-status c1". Sorry I didn't mention about VirtualBox at the very beginning :/.

OK. Sometimes there are appearing all these issues you mentioned above, but how  one can explain that sddm is starting and working if it is run manually by root user? This is a riddle for me :/.

Recently I've tested sddm with Cauldron on my ivy bridge based laptop and all were working. I mean, using sddm, I was able to login into lxqt and plasma5 as well. Thus maybe this is some issue with VirtualBox or maybe some modification. I don't remember if I did any. I can reinstall entire lxqt to try again if this will work.

kdm I was testing with Mageia 5 (installed on VirtualBox) and worked, so there is big chance it will work in Cauldron, I think. I was needed sddm on Cauldron installed on VirtualBox, because I wanted to run also plasma5. And actually I wanted to build and test KDevelop 5 on virtual machine. Of course I'm able to do it without automatically starting sddm.

Anyway, big thanks for help. I'm appreciate for it.
I can live with manually run sddm, and I can login as root to be able update distribution.
Comment 21 Florian Hubold 2015-10-19 18:45:19 CEST
(In reply to Piotr Mierzwinski from comment #20)
> Sometimes there are appearing all these issues you mentioned above, but
> how  one can explain that sddm is starting and working if it is run manually
> by root user? This is a riddle for me :/.

Why shouldn't it start if you run it manually? But that way you basically loose he loginctl session tracking and also break polkit. So best get your DM setup correct, sddm works fine here on mga5 and on cauldron and also for quite some other people, so the question is what you do differently.


The other part of the bug with two polkit agents in parallel under LXQt should be fixed with http://svnweb.mageia.org/packages?view=revision&revision=892752 for cauldron.

Closing this one as no reproducible.

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


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