The officially official Devuan Forum!

You are not logged in.

#1 2021-03-10 20:44:54

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

[Solved] Interpreting/debugging dbus-daemon failure in syslog

Hello:

As I explain in this other post https://dev1galaxy.org/viewtopic.php?id=4142, I am attempting to find out the cause of a failure reported in syslog by the dbus-daemon.
What syslog shows me (I've split it so it can be easier to read) is this:

Mar  9 06:57:35
devuan dbus-daemon[2961]:
[session uid=1000 pid=2959]
Activating service name='org.kde.kwalletd' requested by ':1.42' (uid=1000 pid=3124 comm="/usr/bin/kwalletd5 ")

Mar  9 06:57:35
devuan dbus-daemon[2961]:
[session uid=1000 pid=2959]
Activated service 'org.kde.kwalletd' failed: Failed to execute program org.kde.kwalletd: No such file or directory

This repeats itself with the same syntax and in the same manner ie: at the same time and one after the other, save for the different pid IDs which will be different each time.
It happens when I log in ie: session uid=1000.

Mar 10 14:43:03
devuan dbus-daemon[3015]:
[session uid=1000 pid=3013]
Activating service name='org.kde.kwalletd' requested by ':1.37' (uid=1000 pid=3174 comm="/usr/bin/kwalletd5 ")

Mar 10 14:43:03 devuan dbus-daemon[3015]:
[session uid=1000 pid=3013]
Activated service 'org.kde.kwalletd' failed: Failed to execute program org.kde.kwalletd: No such file or directory

My Devuan Beowulf installation (upgrade from ASCII) has libkwalletbackend5-5 installed:

groucho@devuan:~$ uname -a
Linux devuan 4.19.0-14-amd64 #1 SMP Debian 4.19.171-2 (2021-01-30) x86_64 GNU/Linux
groucho@devuan:~$ 
groucho@devuan:~$ apt list | grep kwallet | grep installed
--- snip ---
libkwalletbackend5-5/stable,now 5.54.0-1 amd64 [installed,automatic]
groucho@devuan:~$ 

libkwalletbackend5-5 is needed by backintime-qt4, the backintime-common GUI.

groucho@devuan:~$ aptitude why libkwalletbackend5-5
i   backintime-qt4    Depends  backintime-common (= 1.1.24-0.1)
i A backintime-common Depends  python3-keyring                 
i A python3-keyring   Suggests libkf5wallet-bin                
i A libkf5wallet-bin  Depends  libkwalletbackend5-5 (>= 5.13.0)
groucho@devuan:~$ 

Starting backintime-qt4 from a terminal to see if I could find anything got me this:

groucho@devuan:~$ backintime-qt4 --debug
DEBUG: [common/backintime.py:518 arg_parse] Arguments: {'debug': True} | unknownArgs: []

Back In Time
Version: 1.1.24

Back In Time comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; type `backintime --license' for details.

DEBUG: [common/backintime.py:585 getConfig] config file: /home/groucho/.config/backintime/config
DEBUG: [common/backintime.py:586 getConfig] profiles: ['1']
DEBUG: [common/applicationinstance.py:73 GUIApplicationInstance.check] No PID file
DEBUG: [common/pluginmanager.py:88 PluginManager.load_plugins] Register plugin path /usr/share/backintime/plugins
DEBUG: [common/pluginmanager.py:104 PluginManager.load_plugins] Add plugin notifyplugin.py
DEBUG: [common/pluginmanager.py:104 PluginManager.load_plugins] Add plugin qt4plugin.py
DEBUG: [common/pluginmanager.py:104 PluginManager.load_plugins] Add plugin userscriptsplugin.py
DEBUG: [common/snapshots.py:953 Snapshots.has_old_snapshots] Found old snapshots: False
DEBUG: [common/tools.py:618 keyring_supported] No appropriate keyring found. 'keyring.backends.chainer' can't be used with BackInTime
DEBUG: [common/applicationinstance.py:73 ApplicationInstance.check] No PID file
DEBUG: [common/mount.py:50 Mount.__init__] pw-cache is not running
DEBUG: [common/mount.py:59 Mount.__init__] Call command: /usr/bin/backintime pw-cache start
DEBUG: [common/applicationinstance.py:73 ApplicationInstance.check] No PID file
--- snip ---
The previous line repeats continuously till I exit the GUI.
--- snip ---
DEBUG: [common/applicationinstance.py:73 ApplicationInstance.check] No PID file
DEBUG: [common/tools.py:618 keyring_supported] No appropriate keyring found. 'keyring.backends.chainer' can't be used with BackInTime
DEBUG: [common/applicationinstance.py:73 ApplicationInstance.check] No PID file
DEBUG: [common/mount.py:50 Mount.__init__] pw-cache is not running
DEBUG: [common/mount.py:59 Mount.__init__] Call command: /usr/bin/backintime pw-cache start
groucho@devuan:~$ 

The available keyring.backends are these:

groucho@devuan:~$ keyring --list-backends
keyrings.alt.file.EncryptedKeyring (priority: 0.6)
keyring.backends.kwallet.DBusKeyringKWallet4 (priority: 3.9)
keyring.backends.chainer.ChainerBackend (priority: 10)
keyring.backends.kwallet.DBusKeyring (priority: 4.9)
keyrings.alt.Gnome.Keyring (priority: 1)
keyring.backends.fail.Keyring (priority: 0)
keyring.backends.SecretService.Keyring (priority: 5)
keyrings.alt.file.PlaintextKeyring (priority: 0.5)
groucho@devuan:~$ 

And the one with priority: 10 cannot be used by backintime-qt4.

But this is all way over my head.
Even though it seems that backintime is working properly, the printout of backintime-qt4 --debug plus the syslog errors could mean there's something amiss somewhere.

Any ideas/suggestions?

Thanks in advance,

A.

Last edited by Altoid (2021-03-12 02:18:11)

Offline

#2 2021-03-11 00:27:52

F_Sauce
Member
From: Noreg
Registered: 2017-07-07
Posts: 68  

Re: [Solved] Interpreting/debugging dbus-daemon failure in syslog

Hei Altoid.

Could this be related to having replaced consolekit with elogind?
I have not seen or noticed any adverse symptoms.

I went through the same procedure as you did, upgraded from ASCII to Beowulf; so, I don't think it has to do with that.
KWallet is working but, if I remember correctly, I had some issues initially; think I started from scratch and deleted every (user) kwallet associated files and repopulated the walletDB.

Not a good answer, and no proper solution, but that's how I believe I did manage to get the KWallet back working.
If you investigate further, which I didn't, you'll probably find a better way; the meaning of this reply was to state that it definitely may work!

Best of luck,
Olav

Offline

#3 2021-03-11 01:16:25

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

Re: [Solved] Interpreting/debugging dbus-daemon failure in syslog

Hello:

F_Sauce wrote:

Not a good answer ...

But it's an answer ...  8^D

F_Sauce wrote:

... probably find a better way ...

I have kept investigating but my knowledge in this area is very limited.

I did find this post that has some elements in common: https://github.com/bit-team/backintime/issues/990
The element in common would be the 'keyring.backends.chainer' can't be used with BackInTime along with the fact that this specific backend has priority: 10.

But I really cannot make heads / tails out of it.

Thanks for your input.

Cheers,

A.

Offline

#4 2021-03-12 02:17:17

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

Re: [Solved] Interpreting/debugging dbus-daemon failure in syslog

Hello:

F_Sauce wrote:

...probably find a better way ...

I'm not sure if it ended up being a better way but I think (at least) I solved the issues in the syslog and backintime-qt --debug outputs, which I think (?) were linked.

I just sort of followed what was done in this link https://github.com/jaraco/keyring/issues/391, a post by the same person who posted what I linked previously.

Apparently it all comes down to some problem in how backintime interacts with python-keyring.

I did this, not because I understood it well enough but out of faith in the solution posted by the chap who worked it out.
Hopefully I have not broken anything in the process:

1. created ~/.local/share/python_keyring/keyringrc.cfg which, as in the post linked, did not exist.

groucho@devuan:~$ cat /home/groucho/.local/share/python_keyring/keyringrc.cfg
# added 20210311
# see https://github.com/jaraco/keyring/issues/391
#
[backend]
default-keyring=keyring.backends.SecretService.Keyring
groucho@devuan:~$ 

By doing this, when I enter keyring get system username in a terminal I no longer receive a UI prompt to create a new kwallet keystore.
Because, why would I want to do that?
I don't use kwallet, I did not install it and do not I want to use it.
It probably came with a meta-package, can't really say.

Now it's clean, no kwallet prompt:

groucho@devuan:/$ keyring get system username
groucho@devuan:/$ 

After doing that and checking/double checking that I was not going to break anything, I decided to remove kwallet and all related files.
It was a huge hoard of kwhatever files...

Then I checked to see what was going on with backintime:

groucho@devuan:/$ backintime-qt4 --debug

Back In Time
Version: 1.1.24

Back In Time comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; type `backintime --license' for details.

DEBUG: [common/backintime.py:585 getConfig] config file: /home/groucho/.config/backintime/config
DEBUG: [common/backintime.py:586 getConfig] profiles: ['1']
DEBUG: [common/applicationinstance.py:73 GUIApplicationInstance.check] No PID file
DEBUG: [common/pluginmanager.py:88 PluginManager.load_plugins] Register plugin path /usr/share/backintime/plugins
DEBUG: [common/pluginmanager.py:104 PluginManager.load_plugins] Add plugin notifyplugin.py
DEBUG: [common/pluginmanager.py:104 PluginManager.load_plugins] Add plugin qt4plugin.py
DEBUG: [common/pluginmanager.py:104 PluginManager.load_plugins] Add plugin userscriptsplugin.py
DEBUG: [common/snapshots.py:953 Snapshots.has_old_snapshots] Found old snapshots: False
DEBUG: [common/tools.py:616 keyring_supported] Found appropriate keyring 'keyring.backends.SecretService'
DEBUG: [common/applicationinstance.py:73 ApplicationInstance.check] No PID file
DEBUG: [common/mount.py:50 Mount.__init__] pw-cache is not running
DEBUG: [common/mount.py:59 Mount.__init__] Call command: /usr/bin/backintime pw-cache start
DEBUG: [common/applicationinstance.py:73 ApplicationInstance.check] No PID file
--- snip ---
DEBUG: [common/applicationinstance.py:73 ApplicationInstance.check] No PID file
DEBUG: [common/tools.py:616 keyring_supported] Found appropriate keyring 'keyring.backends.SecretService'
DEBUG: [common/applicationinstance.py:73 ApplicationInstance.check] No PID file
DEBUG: [common/mount.py:50 Mount.__init__] pw-cache is not running
DEBUG: [common/mount.py:59 Mount.__init__] Call command: /usr/bin/backintime pw-cache start
DEBUG: [common/applicationinstance.py:73 ApplicationInstance.check] No PID file
groucho@devuan:/$ 

And lastly I checked syslog to see if I was getting any kwallet related failures:

groucho@devuan:/var/log$ tail -2500 syslog | grep kwallet| grep failed
Mar 11 11:45:40 devuan dbus-daemon[2968]: [session uid=1000 pid=2966] Activated service 'org.kde.kwalletd' failed: Failed to execute program org.kde.kwalletd: No such file or directory
groucho@devuan:/var/log$ 

That was the last one today at 11:45.
Nothing after six or seven reboots since mid-day today.

backintime seems to be working properly and I have not (yet) seen any problems arise.

Cheers,

A.

Last edited by Altoid (2021-03-12 02:24:06)

Offline

Board footer