Posts by Altoid

Altoid · Hardware & System Configuration

Hello:

Running 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:~$

My box has five different drives, /dev/sda through /dev/sde and I have a strange thing happening with gparted (v. 0.32.0).

fdisk

[root@devuan ~]# fdisk -l
Disk /dev/sda: 111.8 GiB, 120034123776 bytes, 234441648 sectors
Disk model: KINGSTON SV300S3
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0004a8f4

Device     Boot     Start       End   Sectors  Size Id Type
/dev/sda1            2048  40974335  40972288 19.6G 83 Linux
/dev/sda2        40974336 217677823 176703488 84.3G  5 Extended
/dev/sda3       217677824 234440703  16762880    8G 82 Linux swap / Solaris
/dev/sda5        40976384  45072383   4096000    2G 83 Linux
/dev/sda6        45074432 217677823 172603392 82.3G 83 Linux

Partition table entries are not in disk order.

Disk /dev/sdb: 68.4 GiB, 73407488000 bytes, 143374000 sectors
Disk model: VPBA073C3ETS11 N
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xbc66305b

Device     Boot Start       End   Sectors  Size Id Type
/dev/sdb1        2048 143372287 143370240 68.4G 83 Linux

Disk /dev/sdc: 279.4 GiB, 300000000000 bytes, 585937500 sectors
Disk model: ST3300555SS     
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x30830f4e

Device     Boot Start       End   Sectors   Size Id Type
/dev/sdc1        2048 585936895 585934848 279.4G  5 Extended
/dev/sdc5        4096 585936895 585932800 279.4G 83 Linux

Disk /dev/sdd: 68.4 GiB, 73407488000 bytes, 143374000 sectors
Disk model: GNA073C3ESTT0Z N
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xa88df1bd

Device     Boot     Start       End  Sectors  Size Id Type
/dev/sdd1  *         2048  39063551 39061504 18.6G 83 Linux
/dev/sdd2        39065598 127748095 88682498 42.3G  5 Extended
/dev/sdd3       127748096 143372287 15624192  7.5G 82 Linux swap / Solaris
/dev/sdd5        39065600  42969087  3903488  1.9G 83 Linux
/dev/sdd6        42971136 127748095 84776960 40.4G 83 Linux

Partition table entries are not in disk order.

Disk /dev/sde: 232.9 GiB, 250056000000 bytes, 488390625 sectors
Disk model: SEAGATE ST32500N
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x85188518

Device     Boot Start       End   Sectors   Size Id Type
/dev/sde1        2048 488388607 488386560 232.9G 83 Linux
[root@devuan ~]#

blkid:

[root@devuan ~]# blkid
/dev/sda1: LABEL="devuan" UUID="d6841f29-e39b-4c87-9c52-3a9c3bafe2d3" TYPE="ext4" PARTUUID="0004a8f4-01"
/dev/sda3: LABEL="swap" UUID="fb103b4c-e143-4432-a3a0-4883d288bddd" TYPE="swap" PARTUUID="0004a8f4-03"
/dev/sda5: LABEL="log" UUID="c22304ec-0b30-428a-a6ac-500785614702" TYPE="ext4" PARTUUID="0004a8f4-05"
/dev/sda6: LABEL="home" UUID="807e1ce7-72b4-48a3-8f34-65947ea9fd70" TYPE="ext4" PARTUUID="0004a8f4-06"

/dev/sdb1: LABEL="stuff" UUID="49d1369c-ed70-4543-b0ee-ef65327e101b" TYPE="ext4" PARTUUID="bc66305b-01"

/dev/sdc5: LABEL="storage" UUID="bdf33361-5929-433e-ac7f-1a626aa6e844" TYPE="ext4" PARTUUID="30830f4e-05"
/dev/sdd1: UUID="7a33fda5-abda-451b-b6ef-c17553c78810" TYPE="ext4" PARTUUID="a88df1bd-01"
/dev/sdd3: UUID="a806d014-08c4-4d12-87d2-0bd2a2bb60b4" TYPE="swap" PARTUUID="a88df1bd-03"
/dev/sdd5: UUID="f6b70140-07ab-4ff5-b5c5-d05ca2feb03b" TYPE="ext4" PARTUUID="a88df1bd-05"
/dev/sdd6: UUID="8a8a4242-b88a-45cb-b099-59138f895c16" TYPE="ext4" PARTUUID="a88df1bd-06"
/dev/sde1: LABEL="Backup" UUID="ca8dbded-819d-4e2b-b017-0981a75ea718" TYPE="ext4" PARTUUID="85188518-01"
[root@devuan ~]#

The problem is that gparted shows me /dev/sdb as a iso9660 file system labeled MAGIC_BOOT_DISK_v2_0 with a size of 68.37GiB.

Alternatively, gnome-disk-utility 3.30.2 reports it correctly:

Size: 73 GB (73405562880 bytes)
Device: /dev/sdb1
UUID: 49d1369c-ed70-4543-b0ee-ef65327e101b
Partition Type: Linux
Contents: Ext4

And running parted from a terminal also reports it correctly:

groucho@devuan:~$ sudo parted
GNU Parted 3.2
(parted) print list
--- snip ---
Model: IBM-ESXS VPBA073C3ETS11 N (scsi)
Disk /dev/sdb: 73.4GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  73.4GB  73.4GB  primary  ext4
--- snip ---

I have at some time mounted an *.iso file by the same name as the one reported by gparted using AcetoneISO but it was some time ago and it is not mounted now.
If I mount /dev/sdb, it shows up correctly:

groucho@devuan:~$ mount
--- snip ---
/dev/sda1 on / type ext4 (rw,noatime)
--- snip ---
/dev/sda6 on /home type ext4 (rw,noatime)
/dev/sda5 on /var/log type ext4 (rw,noatime)
/dev/sde1 on /media/backups type ext4 (rw,noatime)
--- snip ---
/dev/sdb1 on /media/stuff type ext4 (rw,relatime)
groucho@devuan:~$

Anyone knows what is going on with gparted?
Scared the daylights out of me when I saw it.

Thanks in advance,

A.

Altoid · Desktop and Multimedia

Hello:

Running 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:~$

I have come across a problem in thunar which consists of it crashing when I want to "drag and drop" a file from a folder into another folder.
thunar crashes the instant I move the mouse to "drag" the file I am "holding" by depressing the mouse's right button.

This happens independently of the location/destination of the file.
ie: within folders in the same drive or from/to to another mounted drive.

"Drag and Drop" is not something I do very often so I cannot say when this started to happen, but it may have started after upgrade to 3.1.0.

/var/log/kern.log, /var/log/syslog and dmesg have a line (obviously the same one) for each time this happens:

Mar 13 14:13:38 devuan kernel: [25529.814724] traps: Thunar[3927] trap int3 ip:7f5fcdb41c75 sp:7ffd5aa20300 error:0 in libglib-2.0.so.0.5800.3[7f5fcdb09000+7e000]

And ~/$ .xsession-errors has this:

(Thunar:3927): Gdk-ERROR **: 14:13:38.788: The program 'Thunar' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 8499 error_code 3 request_code 141 (Composite) minor_code 8)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Any ideas as to to fix this?

Thanks in advance,

A.

Altoid · Installation

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.

Altoid · Installation

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.

Altoid · Installation

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.

Altoid · Installation

Head_on_a_Stick wrote:

... 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.

Head_on_a_Stick wrote:

... should probably record both stdout and stderr:
/sbin/fstrim -a -v >> "$LOG" 2>&1

Done.
Thanks for the heads up.

Cheers,

A.

Altoid · Installation

Hello:

ralph.ronnquist wrote:

... PATH is a common cause of issues, see e.g. man 5 crontab.

--

Head_on_a_Stick wrote:

... 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 >> $LOG

Thank you both for your input.

Cheers,

A.

Altoid · Installation

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.

Altoid · Devuan Derivatives

Hello:

Ogis1975 wrote:

By no means.

+1

A.

Altoid · Devuan Derivatives

Hello:

jsalpha2 wrote:

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.

Altoid · Installation

Hello:

Altoid wrote:

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.

Altoid · Off-topic

Hello:

dice wrote:

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.

Altoid · Off-topic

Hello:

Altoid wrote:

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.

Ron wrote:

... 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.

Ron wrote:

... replace the cable ...

See if you can borrow a quality monitor OEM cable to test.

Cheers,

A.

Altoid · Off-topic

Hello:

Ron wrote:

Does anyone have any ideas what it is ...

I agree with these previous answers.

ralph.ronnquist wrote:

Have you tried replacing the monitor cable?

Head_on_a_Stick wrote:

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.

Altoid · Desktop and Multimedia

Hello:

alexkemp wrote:

Clue within Beowulf Release Notes

Don't forget these two, they come up with surprising frequency :

Release Notes wrote:

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.

Altoid · Desktop and Multimedia

Hello:

alexkemp wrote:

... 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.

Altoid · Desktop and Multimedia

Hello:

alexkemp wrote:

Thanks for such a fast reply ...

You're welcome.

alexkemp wrote:

... 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.

Altoid · Desktop and Multimedia

Hello:

alexkemp wrote:

... 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.

Altoid · Installation

Hello:

fsmithred wrote:

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:02

So 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.

Head_on_a_Stick wrote:

... 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.

Altoid · Desktop and Multimedia

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.

Altoid · Installation

Hello:

GlennW wrote:

... 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.

Altoid · Installation

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.

Altoid · Devuan

Hello:

Morty wrote:

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.

Altoid · Installation

Hello:

fsmithred wrote:

... 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.

Altoid · Installation

Hello:

Head_on_a_Stick wrote:

SLiM has been dead since 2013 ...

Still works ...
It's just the entry in slim.log.

Head_on_a_Stick wrote:

... so it doesn't support logind sessions correctly.

I see.

Head_on_a_Stick wrote:

... a different display manager.

I've always liked this one.

Head_on_a_Stick wrote:

... 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.

The officially official Devuan Forum!

#1376 Hardware & System Configuration » [SOLVED] Strange gparted situation » 2021-03-14 22:08:40

#1377 Desktop and Multimedia » Thunar crashes on "Drag and Drop" » 2021-03-13 17:48:10

#1378 Re: Installation » [Solved] Interpreting/debugging dbus-daemon failure in syslog » 2021-03-12 02:17:17

#1379 Re: Installation » [Solved] Interpreting/debugging dbus-daemon failure in syslog » 2021-03-11 01:16:25

#1380 Installation » [Solved] Interpreting/debugging dbus-daemon failure in syslog » 2021-03-10 20:44:54

#1381 Re: Installation » [SOLVED] Permissions for script in cron » 2021-03-09 20:26:54

#1382 Re: Installation » [SOLVED] Permissions for script in cron » 2021-03-08 21:08:01

#1383 Installation » [SOLVED] Permissions for script in cron » 2021-03-08 19:51:15

#1384 Re: Devuan Derivatives » Linux Mint Devuan Edition? » 2021-03-08 19:15:53

#1385 Re: Devuan Derivatives » Linux Mint Devuan Edition? » 2021-03-08 19:14:53

#1386 Re: Installation » kwalletd failure in syslog » 2021-03-07 21:44:39

#1387 Re: Off-topic » Operating System Backups » 2021-03-05 14:53:47

#1388 Re: Off-topic » A problem on my monitor » 2021-03-05 11:43:44

#1389 Re: Off-topic » A problem on my monitor » 2021-02-27 18:13:05

#1390 Re: Desktop and Multimedia » Packages in Synaptic that are 'Held Back' (how to fix that?) » 2021-02-27 12:47:40

#1391 Re: Desktop and Multimedia » Packages in Synaptic that are 'Held Back' (how to fix that?) » 2021-02-27 00:14:23

#1392 Re: Desktop and Multimedia » Packages in Synaptic that are 'Held Back' (how to fix that?) » 2021-02-26 19:45:59

#1393 Re: Desktop and Multimedia » Packages in Synaptic that are 'Held Back' (how to fix that?) » 2021-02-26 14:52:06

#1394 Re: Installation » [Solved] firefox-esr installed by Beowulf 3.1 dist-upgrade » 2021-02-25 16:02:12

#1395 Desktop and Multimedia » MS application on Wine will not open its files » 2021-02-25 15:12:36

#1396 Re: Installation » [Solved] firefox-esr installed by Beowulf 3.1 dist-upgrade » 2021-02-25 11:53:00

#1397 Installation » [Solved] firefox-esr installed by Beowulf 3.1 dist-upgrade » 2021-02-24 23:30:49

#1398 Re: Devuan » As Debian 11 moves closer to Devuan. Is there any reason to stay on De » 2021-02-24 18:28:38

#1399 Re: Installation » [Solved] libpolkit-qt-5-1-1 kept back after ASCII --> Beowulf upgrade » 2021-02-23 20:42:12

#1400 Re: Installation » [Solved] libpolkit-qt-5-1-1 kept back after ASCII --> Beowulf upgrade » 2021-02-23 17:01:14

Board footer