what does it mean "firefox developer edition is being updated by another instance"?

does the firefox develper auto-update?

$ uname -a
Linux hp845g8 6.1.0-49-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.174-1 (2026-05-26) x86_64 GNU/Linux

I can make scripts:

#!/usr/bin/env bash

shopt -s nullglob

for file in /etc/*version /etc/*release; do
    echo "$file:"
    cat "$file"
done

$ ./checkRelease 
/etc/debian_version:
12.6
/etc/devuan_version:
daedalus
/etc/os-release:

But, do we need to code-golf this? Or can we just put some data in the os-release file?

dont know why but the older image chimaera or similar older
got installed and proceeded to update from there,

posted sometime at pine forum , but thought this more devuan related, glad it could function, it is very minimal image.
(but have switched since to armbian pmce more)

libfdk-aac2t64

problem solved, thanks.

From the get-go, I was looking for a straightforward way to transfer files, preferably not involving Samba shares or complex server-client setups with encryption, compression etc. I researched several solutions, some of them seemed more feasible than others. To my surprise, finding a program capable of doing simple LAN transfers between different systems was not an easy task. Some of them could not be used because they were no longer supported on Windows 7 side, some worked but only one way (Win7 > Linux) because they detected wrong IP address due to a bug and had no manual way of setting up things. Some even required Internet access because they used a relay that could not be disabled!

Oh well. With patience and some trial and error, I eventually found a program called LanXchange, which works beautifully. It's not the prettiest or most featureful thing in existence, but it does its job very well.

To use it, you need to install Java Runtime Environment (JRE). You can get it via default-jre package in Excalibur repos, or from Eclipse Adoptium using this guide. I just got the repo version, while on Win7 I'm using the latter.

Unpack and launch LanXchange on both machines. On Windows, lxc.exe complained that I do not have Java installed, but the .jar file worked - so if you get the same error, just try that. On Linux side, use the provided lxc script. You can also run the .jar directly like this:

$ java -jar lanxchange.jar

but I noticed that it sometimes causes issues with incoming transfers not appearing until you unshare your previous files. Not a big problem, but I still recommend using the script.

Next, if you use a firewall like gufw, you will need to allow the following incoming ports: 27716, 27717, 27719. Create two separate 'Simple' rules both for TCP and UDP. On Windows, you probably don't need to do anything other than click 'Allow access' once.

So that's it! Now it should work - nothing beats sending files via a nice fat cable just like in the old days. Enjoy the speed and simplicity (and less wear for your USB Flash devices). Thanks to this wonderful program, I was able to forgo Samba entirely. I did not look into other solutions such as NFS, SFTP or a Python server - they do seem interesting though, so might experiment with them later as well.

HDA Codec Resampling in the Kernel

The Linux kernel's HDA subsystem does have hardware sample rate converter (SRC) capabilities managed by codec drivers. For example, the Creative CA0132 driver documentation shows that HDA codecs have dedicated SRC ports (0x80–0xbf) for sample rate conversion within the codec's internal routing.

Kernel-Level Format Handling

The kernel handles PCM format conversion through the snd_hdac_stream_format() function, which converts channel count, sample format, and sample rate into the HDA format value used by the hardware.

Hardware-Specific Workarounds

Some codecs have hardware-specific sample rate limitations that require kernel-level workarounds. For instance, the ALC269 driver has a fixup for the Lenovo Ideapad that forces analog I/O to 44.1kHz due to a hardware problem.

The fftrate project

The software resampling approach of the fftrate project bypasses these kernel-level hardware resamplers entirely by:
1.  Accepting audio at any rate from the application.
2.  Resampling to 192kHz 32-bit in userspace.
3.  Sending the already-resampled audio to ALSA at a fixed rate.

This avoids potential quality issues or bugs in the codec's hardware SRC implementation. The kernel ALSA driver simply sees a constant 192kHz 32-bit stream and passes it through without additional resampling.

Dialectical conclusion

There is a belief that fftrate may cure deafness, though it hasn't been verified by scientific methods. Give it a chance. It may (or may not) work.

Going through one of my daily rags, I came across a post with a reference to this link, which I am rather reluctantly posting here ie: the Off-topic page.

Not because it is not a truly delightful and inspiring read but because if it is so to a non-programmer like me, it will surely be of much higher significance to those who understand, make a living and/or dedicate time and effort to that very specific craft/art.

As such, it deserves to be in a much more important section of the forum or maybe become a sticky of sorts.

I think that there is a very important lesson to be had in those lines.

Best,

A.

$ sudo apt-get purge gnome-keyring
$ dpkg -l  | grep keyring
ii  debian-archive-keyring                              2025.1                               all          OpenPGP archive certificates of the Debian archive
ii  devuan-keyring                                      2025.08.09                           all          OpenPGP certificates used by the Devuan repository
ii  gnome-keyring-pkcs11:amd64                          48.0-1                               amd64        GNOME keyring module for the PKCS#11 module loading library
ii  libpam-gnome-keyring:amd64                          48.0-1                               amd64        PAM module to unlock the GNOME keyring upon login
ii  python3-keyring                                     25.6.0-2                             all          store and access your passwords safely

I'm not sure it's related to my issue. For example google-chrome presents the same message and gajim (if purged (and its .config dir)) and then if i started again after i try to enter my account for a server the same message will appear. If i hit cancel the dialogue dissapear but my xmpp acoount wont still login.
If i choose yes i get a dialogue window:

If i manage to login (without enabling kde waller -- yes that happened!) the next time i start gajim i get near my xfce notifacation area the message 'password not found authentication failed' and although i can see my contacts i am offline and trying to get online i get the same notification message.

Also shouldnt  $sudo apt-get purge gajim    delete the config files too. I purged it. I reninstalled it and my contacts were there.
Indeed:

~/.config/gajim$ ls
pluginsconfig  settings.sqlite  theme

ps: it not my writing that is messed up..  :-)

zk is not available in the official Debian repositories, which is the reason for it not being in the Devuan repositories.

If and when it gets included in the Debian repositories and has no 'unfixable' dependencies on systemd, you will find it after a few days in the Devuan repositories.

Until then, you (most probably) have the option of building it from source.

Best,

A.