The officially official Devuan Forum!

You are not logged in.

#1 2019-05-13 19:20:32

Altoid
Member
Registered: 2017-05-07
Posts: 233  

LXDE GDBus.Error woes

Hello:

While testing light desktops for my 1000HE, I installed a minimal Devuan ASCII, then X11 and LXDE.
Uninstalled LXDM and start X as user after the login.

All installations made as root after login (without the desktop) have worked perfectly.

But I'm having a problem for which I have not been able to find a solution and am at my wits end.

1. Once the desktop is up (takes a good 30/40s) , there's a pop-up with a notice:
GDBus.Error:org.freedesktop.ConsoleKit.Manager.GeneralError: Unable to lookup session information for process '1824'

This only happens if from a cold start, after a reboot.
Logging out and then logging in again, from the desktop or the system will not have this behaviour. ie: desktop comes up quickly and no pop-up.

But if I reboot it is there again.

2.
I can only start synaptic via gksu in a terminal, if I try to do it from the menu, anything I try to click with the mouse or even ctrl+alt+del is unresponsive.
ie: synaptic-pkexec (.desktop file command) is not working.
Hard shutdown required.

3. Attempting to shutdown or reboot from the menu shows an error at the bottom of the window:
GDBus.Error:org.freedesktop.DBus.Error.Interactive authentication required. 
Only logout is possible.

4. Maybe unrelated ...
Cannot get the new settings for the LXTerminal to stick.

Any ideas?

Thanks in advance.

A.

Offline

#2 2019-05-13 20:42:53

fsmithred
Administrator
Registered: 2016-11-25
Posts: 1,155  

Re: LXDE GDBus.Error woes

It probably has to do with policykit backends. We removed lxde from the desktop choices in the ascii installer isos because it wasn't quite right. You'll need to find the right combination of packages to get what you want. To start with, find out what's installed.

dpkg -l | egrep "consolekit|elogind|libpam|policykit|polkit"

Offline

#3 2019-05-13 20:54:29

Head_on_a_Stick
Member
From: London
Registered: 2019-03-24
Posts: 290  
Website

Re: LXDE GDBus.Error woes

Altoid wrote:

I can only start synaptic via gksu in a terminal, if I try to do it from the menu, anything I try to click with the mouse or even ctrl+alt+del is unresponsive.
ie: synaptic-pkexec (.desktop file command) is not working.

You need to install a graphical polkit authentication agent and (auto)start it.

Try this:

# apt install lxpolkit
lxpolkit &
synaptic-pkexec

It may be that lxpolkit will start automatically once it is installed, I don't use LXDE so I'm not sure.

If not then try adding lxpolkit & to ~/.xsessionrc


Fabricando fit faber

Offline

#4 2019-05-13 21:33:05

Altoid
Member
Registered: 2017-05-07
Posts: 233  

Re: LXDE GDBus.Error woes

Hello:

fsmithred wrote:

It probably has to do with policykit backends.

A permissions things, to be sure.

fsmithred wrote:

...removed lxde from the desktop choices in the ascii installer isos because it wasn't quite right.

I see ...

fsmithred wrote:

... need to find the right combination of packages ...

OK.

fsmithred wrote:

...find out what's installed.

dpkg -l | egrep "consolekit|elogind|libpam|policykit|polkit"

Here it is ...

groucho@devuan:~$ dpkg -l | egrep "consolekit|elogind|libpam|policykit|polkit"
ii  consolekit  0.4.6-6  i386  framework for defining and tracking users, sessions and seats
ii  elogind  234.4-2  i386  user, seat and session management daemon
ii  libelogind0:i386  234.4-2  i386  user, seat and session management library
ii  libpam-cap:i386  1:2.25-1  i386  POSIX 1003.1e capabilities (PAM module)
ii  libpam-elogind:i386  234.4-2  i386  elogind PAM module
ii  libpam-gnome-keyring:i386  3.20.0-3  i386  PAM module to unlock the GNOME keyring upon login
ii  libpam-modules:i386  1.1.8-3.6  i386  Pluggable Authentication Modules for PAM
ii  libpam-modules-bin  1.1.8-3.6  i386  Pluggable Authentication Modules for PAM - helper binaries
ii  libpam-runtime  1.1.8-3.6  all  Runtime support for the PAM library
ii  libpam0g:i386  1.1.8-3.6  i386  Pluggable Authentication Modules library
ii  libpolkit-agent-1-0:i386  0.105-25+devuan0~bpo2+1  i386  PolicyKit Authentication Agent API
ii  libpolkit-backend-1-0  0.105-25+devuan0~bpo2+1  all  PolicyKit Authorization API
ii  libpolkit-backend-consolekit-1-0:i386  0.105-25+devuan0~bpo2+1  i386  PolicyKit backend API
ii  libpolkit-gobject-1-0  0.105-25+devuan0~bpo2+1  all  PolicyKit Authorization API
ii  libpolkit-gobject-consolekit-1-0:i386  0.105-25+devuan0~bpo2+1  i386  PolicyKit Authorization API
ii  libpolkit-qt5-1-1:i386  0.112.0-5  i386  PolicyKit-qt5-1 library
ii  lxpolkit  0.5.3-2  i386  LXDE PolicyKit authentication agent
ii  lxqt-policykit  0.11.1-1  i386  LXQt authentication agent for PolicyKit
ii  lxqt-policykit-l10n  0.11.2-1  all  Language package for lxqt-policykit
ii  policykit-1  0.105-25+devuan0~bpo2+1  i386  framework for managing administrative policies and privileges
ii  policykit-1-gnome  0.105-6  i386  authentication agent for PolicyKit
groucho@devuan:~$ 

... but none in the list seem to be running:

groucho@devuan:~$ ps x | grep "consolekit|elogind|libpam|policykit|polkit"
5050 pts/0    S+     0:00 grep consolekit|elogind|libpam|policykit|polkit
groucho@devuan:~$ 

Thanks in advance,

A.

Offline

#5 2019-05-13 21:36:22

Altoid
Member
Registered: 2017-05-07
Posts: 233  

Re: LXDE GDBus.Error woes

Hello:

Head_on_a_Stick wrote:

... install a graphical polkit authentication agent ...

See the list of installed packages.
It is installed but not (?) running.

Thanks for your input.

A.

Offline

#6 2019-05-14 01:12:21

fsmithred
Administrator
Registered: 2016-11-25
Posts: 1,155  

Re: LXDE GDBus.Error woes

ps ax | grep polkit

to see if it's running.

Offline

#7 2019-05-14 01:55:08

Altoid
Member
Registered: 2017-05-07
Posts: 233  

Re: LXDE GDBus.Error woes

Hello:

fsmithred wrote:
ps ax | grep polkit

to see if it's running.

Ahh ...

groucho@devuan:~$ ps ax | grep polkit
 1677 ?        Sl     0:00 /usr/lib/policykit-1/polkitd --no-debug
 1820 tty1     Sl     0:00 lxpolkit
 1961 pts/0    S+     0:00 grep polkit
groucho@devuan:~$ 

It seems it's ?

I also had a look at /var/log/auth.log.

groucho@devuan:~$ cat /var/log/auth.log | grep -i failed
--- snip ...
May 13 17:02:40 devuan dbus[1518]: [system] Failed to activate service 'org.freedesktop.ConsoleKit': timed out
May 13 17:13:51 devuan polkitd(authority=local): Operator of unix-process:2448:231281 FAILED to authenticate to gain authorization for action com.ubuntu.pkexec.synaptic for unix-process:2448:231281 [/bin/sh /usr/bin/synaptic-pkexec] (owned by unix-user:groucho)
May 13 17:17:28 devuan polkitd(authority=local): Operator of unix-process:2524:253913 FAILED to authenticate to gain authorization for action com.ubuntu.pkexec.synaptic for unix-process:2524:253913 [/bin/sh /usr/bin/synaptic-pkexec] (owned by unix-user:groucho)
May 13 22:02:12 devuan dbus[1516]: [system] Failed to activate service 'org.freedesktop.ConsoleKit': timed out
May 13 22:48:28 devuan dbus[1513]: [system] Failed to activate service 'org.freedesktop.ConsoleKit': timed out
May 13 23:54:04 devuan dbus[1499]: [system] Failed to activate service 'org.freedesktop.ConsoleKit': timed out

I saw this on this info as relevant (?) in bugs.debian and thought it may help if you had it:
Not that I have a clue ...   =-/

groucho@devuan:~$ ls -al /usr/lib/dbus-1.0/dbus-daemon-launch-helper
-rwsr-xr-- 1 root messagebus 42892 Mar 16 03:22 /usr/lib/dbus-1.0/dbus-daemon-launch-helper
groucho@devuan:~$ 
groucho@devuan:~$ LANG=C apt-cache policy $(dpkg -S /usr/lib/dbus-1.0/dbus-daemon-launch-helper | cut -d":" -f1)
dbus:
  Installed: 1.10.22-1+devuan2
  Candidate: 1.10.22-1+devuan2
  Version table:
 *** 1.10.22-1+devuan2 500
        500 http://deb.devuan.org/merged ascii/main i386 Packages
        500 http://deb.devuan.org/merged ascii-updates/main i386 Packages
        500 http://packages.devuan.org/devuan ascii/main i386 Packages
        100 /var/lib/dpkg/status
groucho@devuan:~$ dbus

Thanks for your input.

A.

Last edited by Altoid (2019-05-14 13:15:39)

Offline

#8 2019-05-14 16:31:55

chris2be8
Member
Registered: 2018-08-11
Posts: 56  

Re: LXDE GDBus.Error woes

The ? means that polkitd isn't attached to a terminal. ps aux gives more information:

chris@rigel:~/bin$ ps aux | grep polkit
chris      360  0.0  0.0  12784   972 pts/2    S+   17:25   0:00 grep polkit
root      2787  0.0  0.1 297264  6992 ?        Sl    2018   0:00 /usr/lib/policykit-1/polkitd --no-debug

chris@rigel:~/bin$ ps aux | head -3
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         1  0.0  0.0  15812  1628 ?        Ss    2018   2:25 init [2]
root         2  0.0  0.0      0     0 ?        S     2018   0:05 [kthreadd]

The second command is just to show the column headings. The first column shows polkit runs as root which is why you need ps ax to show it.

Chris

Offline

#9 2019-05-14 16:58:28

Altoid
Member
Registered: 2017-05-07
Posts: 233  

Re: LXDE GDBus.Error woes

Hello:

chris2be8 wrote:

The ? means that polkitd isn't attached to a terminal. ps aux gives more ...

OK, here's ps aux:

groucho@devuan:~$ ps aux | grep polkit
root      1709  0.3  0.3  37032  6428 ?        Sl   13:49   0:00 /usr/lib/policykit-1/polkitd --no-debug
groucho   1852  0.2  0.8  45036 17144 tty1     Sl   13:50   0:00 lxpolkit
groucho   2052  0.0  0.0   4728   840 pts/0    S+   13:51   0:00 grep polkit
groucho@devuan:~$ 
chris@rigel:~/bin$ ps aux | head -3
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         1  0.0  0.0  15812  1628 ?        Ss    2018   2:25 init [2]
root         2  0.0  0.0      0     0 ?        S     2018   0:05 [kthreadd]

The second command is just to show the column headings.
The first column shows polkit runs as root which is why you need ps ax to show it.

I see ...
(have to read up on this)

Thanks for your input.

A.

Offline

#10 2019-05-14 17:24:16

Head_on_a_Stick
Member
From: London
Registered: 2019-03-24
Posts: 290  
Website

Re: LXDE GDBus.Error woes

Altoid wrote:

It is installed but not (?) running.

Then run it.

My earlier post suggests how.

I prefer this to find the process:

pgrep -a polkit

Fabricando fit faber

Offline

#11 2019-05-14 19:24:44

Altoid
Member
Registered: 2017-05-07
Posts: 233  

Re: LXDE GDBus.Error woes

Hello:

Head_on_a_Stick wrote:

Then run it.

My mistake, it seems it is running.

groucho@devuan:~$ pgrep -a polkit
1685 /usr/lib/policykit-1/polkitd --no-debug
1828 lxpolkit
groucho@devuan:~$ 
Head_on_a_Stick wrote:

My earlier post suggests how.

This:

Head_on_a_Stick wrote:

... install a graphical polkit authentication agent and (auto)start it.

If you mean slim, xdm and such, that's what I was not wanting to have, which is why I unisntalled lxdm.
Maybe that's where it went south?
So much for modularity ...

With respect to /.xsessionrc, it's not in /:

groucho@devuan:/$ locate xsessionrc
/etc/X11/Xsession.d/40x11-common_xsessionrc
groucho@devuan:/$ 

40x11-common_xsessionrc relates to Xsession:

groucho@devuan:/$ cat /etc/X11/Xsession.d/40x11-common_xsessionrc
# This file is sourced by Xsession(5), not executed.

#Source user defined xsessionrc (locales and other environment variables)
if [ -r "$USERXSESSIONRC" ]; then
  . "$USERXSESSIONRC"
fi
groucho@devuan:/$ 

Which in turn I can find elsewhere and gets complicated:

groucho@devuan:/$ locate Xsession
/etc/X11/Xsession
/etc/X11/Xsession.d
/etc/X11/Xsession.d/20vdpau-va-gl
/etc/X11/Xsession.d/20x11-common_process-args
/etc/X11/Xsession.d/30x11-common_xresources
/etc/X11/Xsession.d/35x11-common_xhost-local
/etc/X11/Xsession.d/40x11-common_xsessionrc
/etc/X11/Xsession.d/50x11-common_determine-startup
/etc/X11/Xsession.d/52gtk3-nooverlayscrollbar-nocsd
/etc/X11/Xsession.d/60xdg-user-dirs-update
/etc/X11/Xsession.d/75dbus_dbus-launch
/etc/X11/Xsession.d/90consolekit
/etc/X11/Xsession.d/90gpg-agent
/etc/X11/Xsession.d/90qt-a11y
/etc/X11/Xsession.d/90qt5-opengl
/etc/X11/Xsession.d/90x11-common_ssh-agent
/etc/X11/Xsession.d/95dbus_update-activation-env
/etc/X11/Xsession.d/99x11-common_start
/etc/X11/Xsession.options
/usr/share/man/man5/Xsession.5.gz
/usr/share/man/man5/Xsession.options.5.gz
groucho@devuan:/$ 

FWIW, my workstation which runs slim and XFCE4 has the same 40x11-common_xsessionrc and no /.xsessionrc.

If polkit and lxpolkit are running maybe it is some DBus issue?

I'll try a couple of things and check back.

Thanks a lot for your input.

A.

Last edited by Altoid (2019-05-14 19:25:31)

Offline

#12 2019-05-14 19:42:42

Head_on_a_Stick
Member
From: London
Registered: 2019-03-24
Posts: 290  
Website

Re: LXDE GDBus.Error woes

Altoid wrote:

/.xsessionrc

That's not what I typed, read my post again.

Reference: https://wiki.debian.org/Xsession#User_configuration


Fabricando fit faber

Offline

#13 2019-05-14 23:17:07

Altoid
Member
Registered: 2017-05-07
Posts: 233  

Re: LXDE GDBus.Error woes

Hello:

Altoid wrote:

I'll try a couple of things and check back.

Famous last words ...

I reinstalled slim and the result was a totally unresponsive keyboard and trackpad.
So I purged slim and went for lxde, with the same result.

Then I purged both lxde and xserver, reinstalled xserver and ...
... got the same result ie: was a totally unresponsive keyboard and trackpad.

So now I've purged lxde and xserver, pondering my next step.
Theoretically speaking, what I now have is a base system with a few added things (like sudo, etc.)

Cheers,

A.

Offline

#14 2019-05-15 04:27:08

ToxicExMachina
Member
Registered: 2019-03-11
Posts: 106  

Re: LXDE GDBus.Error woes

Altoid wrote:

totally unresponsive keyboard and trackpad.

I think input subsystem doesn't start properly. Check X.org logs: Xorg.0.log from /var/log or ~/.local/share/xorg

Offline

#15 2019-05-15 13:08:18

Altoid
Member
Registered: 2017-05-07
Posts: 233  

Re: LXDE GDBus.Error woes

Hello:

ToxicExMachina wrote:

I think input subsystem doesn't start properly. Check X.org logs: Xorg.0.log from /var/log or ~/.local/share/xorg

Yes, I've been looking into that.
The xserver relies on udev for the list of input devices and the log does not list keyboard or trackpad.
So that's a lead.

But there's something else, of a more serious nature, amiss here ...
To post here, I was wanting to put the output of Xorg.0.log (a txt file) on an SD card mounted by me as root in /media/SD and as root was denied access.
I was also denied chown. (!!!)

Something (what?) when/after I uninstalled slim knocked out some essentials. ie: udev whatevers and some permission configs.

fsmithred wrote:

We removed lxde from the desktop choices in the ascii installer isos because it wasn't quite right. You'll need to find the right combination of packages to get what you want.

I did not know that and went for it as it is what Knoppix chose in their rescue CDs.
They usually know what they are doing but then each CD is a custom compound of many sources, custom tailored and not really updateable.
ie: have to reinstall (if used 'on-disk') every time and have probably ironed out whatever ails lxde.

It's a dejavu feeling having to reinstall (years of suffering MS) to fix something but at this point I think it is the best thing to do.

It's all down to Linux experience and eventually I will know how to avoid this type of crap and if not, know enough to be able to fix it.

But now I'm reinstalling.  =-/

Thanks to all for your input.

A.

Last edited by Altoid (2019-05-15 19:32:03)

Offline

Board footer