You are not logged in.
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 directoryThis 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 directoryMy 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.
... would use either/or.
... want to use both methods then call the full path for date ...
Yes, makes sense.
Done, will use full path to the script.
... should probably record both stdout and stderr:
/sbin/fstrim -a -v >> "$LOG" 2>&1
Done.
Thanks for the heads up.
Cheers,
A.
Hello:
... PATH is a common cause of issues, see e.g. man 5 crontab.
--
... it's a PATH issue.
... set PATH in the script or call the full path to fstrim ...
Like this?
Belt and suspenders ...
#!/bin/sh
# trim all mounted file systems which support it
# added x 20200315
#
PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
LOG=/var/log/trim.log
echo "*** $(date -R) ***" >> $LOG
/sbin/fstrim -a -v >> $LOGThank you both for your input.
Cheers,
A.
Hello:
I have put a script to run fstrim in /etc/cron.weekly/:
groucho@devuan:/$ cat /etc/cron.weekly/dev-fstrim
#!/bin/sh
# trim all mounted file systems which support it
# added 20200315
#
LOG=/var/log/trim.log
echo "* $(date -R) *" >> $LOG
fstrim -a -v >> $LOG
groucho@devuan:/var/log$ But it is not running, probably because fstrim needs admin credentials to run.
I can run the script as root but that needs my intervention and the idea is that it runs automagically one a week.
What is the proper way to achieve this?
An entry in /etc/sudoers.d for fstrim?
Thanks in advance.
A.
Hello:
By no means.
+1
A.
Hello:
Hoping that someone is working on a Linux Mint Devuan Edition.
Why on earth bother?
We have Devuan which is very flexible and a host of options for the screen.
A.
Hello:
I have this line in my /var/log/syslog:
Feb 22 16:35:25 devuan dbus-daemon[2963]: [session uid=1000 pid=2961] Activated service 'org.kde.kwalletd' failed: Failed to execute program org.kde.kwalletd: No such file or directory
I'm bumping this because I have not been able to find any information elsewhere and as it is whateverd related, thought the answer could come from this forum.
Thanks in advance,
A.
Hello:
What do you use for backups?
I use two applications: Timeshift and BackInTime.
Timeshift takes system snapshots and BackInTime takes ~/ snapshots.
Have always worked quite well.
All the snapshots get stored on a separate 300Gb SAS drive living inside the box.
This is quite obviously not the ideal solution and I've been procrastinating for the longest while.
Cheers,
A.
Hello:
Are you using the OEM cable?
Does it have a ferrite filter?
How long has this specific cable been in use ie: terminals in its sockets?
Try unplugging/plugging them a number of times and see what happens, with the PC/monitor turned off.
... don't think it's something nearby that's causing the problem.
Check to see what happens by moving the monitor (if at all possible) to another location.
Does ot have to be more than a couple of feet.
... replace the cable ...
See if you can borrow a quality monitor OEM cable to test.
Cheers,
A.
Hello:
Does anyone have any ideas what it is ...
I agree with these previous answers.
Have you tried replacing the monitor cable?
If it's intermittent then the problem is with the hardware (the cable ...
The description fit this (probaby) being some sort of radio interference generated by something electrically powered running nearby and being picked up by the monitor cable.
Are you using the OEM cable?
Does it have a ferrite filter?
Have you tried using another cable?
When you do have these artifacts on the screen, is there something electrical running nearby?
Cheers,
A.
Hello:
Clue within Beowulf Release Notes
Don't forget these two, they come up with surprising frequency :
Changes in su
- The behavior of su has changed. Use 'su -' to get root's path or use
the full path to commands if you use only 'su'.---- snip ----
Pulseaudio
- If you install a desktop environment from the installer iso, you will
automatically get the debian-pulseaudio-config-override package,
which will ensure that pulseaudio is running. If you're running a
window manager, you may need to install the override package to get
sound. Alternatively, you may use the old method, described below.
- If you have no sound, make sure the following line in
/etc/pulse/client.conf.d/00-disable-autospawn.conf is commented as
shown here:#autospawn=no
---- snip ----
Regarding the importance of Release Notes, (believe it or not) someone once actually posted this bit of interesting IT wisdom here at Dev1:
Reading distro notes: Until Devuan, never wasted one minute reading them. Either an OS is transparent, and works effortlessly, or it needs criticism.
8^7 !!!
Cheers,
A.
Hello:
... discovering that ~/.xsession-errors was >3GB.
Diagnosing that is going to have to wait.
~/.xsession-errors can get out of control size-wise very quickly and not necessarily on a system with valid issues.
It's really only needed for debugging purposes.
One thing I did on a new installation long ago was to have a separate 2Gb /var partition.
There is a way to move an existing /var to a different partition but that exceeds the scope of this post which is an elegant way of saying I can't remember how it is done.
Obviously it involves repartitioning/creating a new partition but the rest is foggy (at least today).
Check this page: https://www.daniloaz.com/en/how-to-prev … huge-size/
Tells you how to deal with the ~/.xsession-errors file, from limiting its size via crontab to disabling writs to that file.
Cheers,
A.
Hello:
Thanks for such a fast reply ...
You're welcome.
... for such an excellent diagnosis ...
... best advice is given from those that have met the same/similar problem & fixed it.
Hmm ...
I'm just a humble messenger, an apprentice at best.
The heavy lifting (which is where the message actually originates) is done by others with much more knowledge and experience.
Glad you were able to get it working.
Do read up the (very often ignored) Release Notes.
Cheers,
A.
Hello:
... why did these packages get held back ...
Don't despair. 8^D
Read this post https://dev1galaxy.org/viewtopic.php?id=4130.
It is related to libpolkit-qt5-1-1 being held back, which in turn was related to SLiM and its dependencies.
groucho@devuan:~$ aptitude why consolekit
i slim Depends default-logind | logind | consolekit
groucho@devuan:~$ Installing libpam-elogind and removing consolekit gets rid of a few surplus/unused files and fixes everything.
Do read the post twice just in case.
Best,
A.
Hello:
Look for those packages in /var/log/apt/history* to see when they were installed ...
Done.
A huge print out, had to open it with pluma to get it decently formatted so as to search properly.
The first line of the log is dated 2017/05/01 and here's the first mention of webhttrack:
Start-Date: 2019-02-28 14:08:49
Commandline: /usr/sbin/synaptic
Requested-By: groucho (1000)
Install: libhttrack2:amd64 (3.48.24-1+b2, automatic), webhttrack:amd64 (3.48.24-1+b2), webhttrack-common:amd64 (3.48.24-1, automatic)
End-Date: 2019-02-28 14:09:02So it looks like I installed it.
But I cannot recall doing it nor can I think of any use I could have had for it.
I'm absolutely sure that I never used it.
Maybe I clicked on the synaptic box accidentally?
No idea.
But I don't use synaptic anymore save for looking up packages or data so I expect this will not happen again. 8^7
I'll eventually get rid of it.
... does aptitude do if you try to remove it?
I removed all (firefox-esr, webhttrack and httrack) with no issues whatsoever.
Culprit found, problem solved.
Thanks a lot for you input.
Cheers,
A.
Hello:
I run on an up to date Devuan Beowulf ...
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:~$ ... and have two MS based applications of which I am very fond of (Pegasus Mail and IrfanView), both running on Wine.
groucho@devuan:~$ wine --version
wine-4.0 (Debian 4.0-2)
groucho@devuan:~$ I'm having a problem loading the files I open with IrfanView as the files' Properties > Open With drop down menu does not list IrfanView (I have to look for it in Other Application but even then, once selected, it does not 'stick' and the drop down menu stays empty.
This causes that any IrfanView file (a huge list of graphic files) will not open like it should ie:on a mouse click and IrfanView will open but with no file loaded.
I have to open it via File > Open in the IrfanView menu.
Any idea on how to fix this?
Thanks in advance.
A.
Hello:
... program that saves/backs-up websites.
Yes, I looked it up after posting.
But the thing is, why was it installed during my ASCII - Beowulf 3.1 dist-upgrade?
And dragging in a browser I did not want in my rig?
If I Firefox-esr had been part of my ASCII, it would have expected to have it upgraded.
But it was not.
And I don't recall ever installing httrack or webhttrack.
It's not in my pre-Beowulf timeshift snapshots.
Thanks for your input.
Cheers,
A.
Hello:
One of the things I got when I went from ASCII to the latest Beowulf 3.1 was firefox-esr.
It was not installed in ASCII as I've been using Pale Moon for the longest while and this made me want to find out why it was there.
Maybe remnants of some meta-package?
An incomplete removal?
groucho@devuan:~$ aptitude why firefox
i webhttrack Depends iceape-browser | iceweasel | icecat | mozilla | firefox | mozilla-firefox | www-browser
groucho@devuan:~$ Never heard of webhttrack or know what it does, so I asked again:
groucho@devuan:~$ aptitude why webhttrack
i webhttrack Suggests httrack
p httrack Suggests webhttrack
groucho@devuan:~$ groucho@devuan:~$ aptitude why httrack
i webhttrack Suggests httrack
groucho@devuan:~$ Looks like a chicken/egg thing ...
Anyone know why webhttrack was installed in the first place, bringing in firefox-esr along with it?
TIA,
A.
Hello:
Is there any reason to stay on Devuan?
Yes, there are many reasons.
The first: trust
The second: basic common sense
All the other reasons follow these first two.
And like golinux wrote: It's about more than code.
But the question (if there has to be one at all) should be:
Is there any reason not to stay on Devuan?
And the answer is: none whatsoever.
As always, YMMV.
It's just my $0.02
A.
Hello:
... it's there to remind us all that we're not running systemd.
Hmm ...
Both the slim 1.3.6-5.1+devuan6 (merged beowulf/main) and 1.3.6-5.2+devuan1 (/merged beowulf /unstable) have default-logind | logind | consolekit as depends.
Depends slim 1.3.6-5.2+devuan1
libc6 (>= 2.14), libck-connector0, libdbus-1-3 (>= 1.9.14), libgcc1 (>= 1:3.0), libjpeg62-turbo (>= 1.3.1), libpam0g (>= 0.99.7.1), libpng16-16 (>= 1.6.2-1), libstdc++6 (>= 5.2), libx11-6, libxext6, libxft2 (>> 2.1.1), libxmu6, libxrandr2 (>= 2:1.2.99.3), debconf (>= 1.2.9) | debconf-2.0, dbus, default-logind | logind | consolekit, x11-xserver-utils, lsb-base
Depends slim 1.3.6-5.1+devuan6
libc6 (>= 2.17), libck-connector0, libdbus-1-3 (>= 1.9.14), libgcc-s1 (>= 3.0), libjpeg62-turbo (>= 1.3.1), libpam0g (>= 0.99.7.1), libpng16-16 (>= 1.6.2-1), libstdc++6 (>= 5.2), libx11-6, libxext6, libxft2 (>> 2.1.1), libxmu6, libxrandr2 (>= 2:1.2.99.3), debconf (>= 1.2.9) | debconf-2.0, dbus, default-logind | logind | consolekit, x11-xserver-utils, lsb-base
I looked to see if it was worth installing the unstable and check slim.log but I'd probably have an issue with libc6 (>= 2.17).
Cheers,
A.
Hello:
SLiM has been dead since 2013 ...
Still works ...
It's just the entry in slim.log.
... so it doesn't support logind sessions correctly.
I see.
... a different display manager.
I've always liked this one.
... no display manager at all ...
Tried that and had all sort of permission problems.
Si I installed slim and they all went away instantly.
So I'll keep it. 8^P!
Thanks for your input.
Cheers,
A.
Sorry, I don't know ...
No problem. 8^D
... see the "not provided by any .service files" a lot, and I just ignore it.
Right.
... remind us all that we're not running systemd.
Lol ...
Try this:
apt -s remove consolekit
[root@devuan ~]# apt -s remove consolekit
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package 'consolekit' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[root@devuan ~]# Nothing.
Thanks a lot for your input.
Cheers,
A.
Hello:
groucho@devuan:~$ aptitude why consolekit i slim Depends default-logind | logind | consolekit groucho@devuan:~$What does this mean in practical terms? eg: for slim which I am fond of.
It means slim needs something that provides default-logind or one of the others on that line.
I'm writing on this again as I have found this in /var/log/slim.log:
slim: waiting for X server to begin accepting connections.
slim: Consolekit::open_session: Unable to open session: The name org.freedesktop.ConsoleKit was not provided by any .service files
slim: falling back to PAM session
groucho@devuan:/var/log$It would seem that slim is still looking for consolekit in spite of it being replaced by elogind.
Why is that?
I am being able to log in without problems.
Thanks in advance,
A.
Hello:
I have this line in my /var/log/syslog:
Feb 22 16:35:25 devuan dbus-daemon[2963]: [session uid=1000 pid=2961] Activated service 'org.kde.kwalletd' failed: Failed to execute program org.kde.kwalletd: No such file or directoryI know uid=1000 is me but I cannot find pid=2961 which I guess is the program that syslog says failed to execute.
groucho@devuan:~$ ls /proc
1 121 129 1668 2058 25 2904 2992 3036 3131 37 4804 9591 driver kpagecgroup sched_debug version
10 122 130 1697 207 2514 2905 2996 3040 3155 38 5185 9592 execdomains kpagecount schedstat vmallocinfo
10097 1224 131 17 208 26 2906 3 3060 3161 39 6 acpi fb kpageflags self vmstat
10349 1225 132 1704 21 2602 2907 30 3063 3166 4 6091 asound filesystems loadavg slabinfo zoneinfo
10397 1226 14 1705 2102 2631 2908 3003 3072 3171 40 66 buddyinfo fs locks softirqs
10401 1227 142 1708 2135 2633 2916 3007 3074 3183 4094 67 bus interrupts meminfo stat
10483 1228 15 1719 2160 2658 2927 3008 3077 3186 41 6743 cgroups iomem misc swaps
11 1229 1555 19 2161 2667 2930 3009 3078 3195 413 7990 cmdline ioports modules sys
115 123 157 1968 2190 27 2962 3013 3079 3199 42 8 consoles irq mounts sysrq-trigger
116 124 16 1982 2192 2771 2963 3022 3081 32 43 8664 cpuinfo kallsyms mpt sysvipc
117 125 161 2 22 2804 2973 3023 3082 33 44 8760 crypto kcore mtrr thread-self
118 126 164 20 2223 2832 2983 3025 3086 34 4719 9 devices key-users net timer_list
119 127 165 2010 24 29 2985 3033 31 35 4745 9272 diskstats keys pagetypeinfo tty
12 128 166 205 2488 2903 2990 3034 3118 36 48 9273 dma kmsg partitions uptime
groucho@devuan:~$ Seems that org.kde.kwalletd is present in the system:
groucho@devuan:~$ locate kwalletd | grep org.kde.kwalletd
/usr/share/dbus-1/services/org.kde.kwalletd.service
/usr/share/dbus-1/services/org.kde.kwalletd5.service
groucho@devuan:~$ There is also a /.local/share/kwalletd sub-folder in my home folder but it is empty.
Could this be related to having replaced consolekit with elogind?
I have not seen or noticed any adverse symptoms.
Thanks in advance,
A.
Hello:
uninstalling apparmor also solves this issue.
Quite so ...
Something I'm considering as I'm not certain it is of any use to me.
ie: everything is apparently unconfined, so what does it actually do? Am I missing some configuration file/s?
groucho@devuan:~$ sudo dmesg | grep apparmor
[ 25.423650] audit: type=1400 --- snip --- apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-senddoc" pid=1409 comm="apparmor_parser"
[ 25.448662] audit: type=1400 --- snip --- apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-oopslash" pid=1412 comm="apparmor_parser"
[ 25.474000] audit: type=1400 --- snip --- apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=1411 comm="apparmor_parser"
[ 25.500604] audit: type=1400 --- snip --- apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=1411 comm="apparmor_parser"
[ 25.500605] audit: type=1400 --- snip --- apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=1410 comm="apparmor_parser"
[ 25.500607] audit: type=1400 --- snip --- apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=1410 comm="apparmor_parser"
[ 25.500608] audit: type=1400 --- snip --- apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=1410 comm="apparmor_parser"
[ 25.500609] audit: type=1400 --- snip --- apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-soffice" pid=1414 comm="apparmor_parser"
[ 25.500611] audit: type=1400 --- snip --- apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-soffice//gpg" pid=1414 comm="apparmor_parser"
[ 25.500612] audit: type=1400 --- snip --- apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-xpdfimport" pid=1416 comm="apparmor_parser"
groucho@devuan:~$ ... being obnoxious sorry...
Nah!
It's quite alright, been there/done that.
After all, it is monday.
Cheers,
A.