Hello:

My Asus 1000HE had/has a similar issue which was never fixed by Debian.

Check the Ubuntu dmesg printout against the Devuan dmesg printout and see if there's any mention of that.
There's probably some driver or module you need loaded, present in the Ubuntu distribution and not in the Debian based ones.

Best,

A.

Hello:

Yes and the settings there should be properly reflected in about:config.
It is actively discouraged by FF to go there, soon we won't be able to tweak anything.

Independently of the fact that not eveyone fiddles around with about:config, dom.security.https_only_mode is set to false.

I have FF 91.9.1 esr installed on my 1000HE and it works properly. ie: with the option Don’t enable HTTPS-Only set as I have done for the longest while.

No.
Besides, I cannot recall this happening with the previous version. ie: 102.15.0esr-1~deb10u1

EDIT:

It seems that it is an issue with FF.

And from the looks of it, it won't be looked at by Mozilla or fixed any time soon.
At least, the thread seems to suggest that the solution is that you emply a work-around.

ie: with FF everything has to be via HTTPS and if you don't like that, file exceptions.

Yet another reason to ditch FF.

Thanks for your input.

Best,

A.

Hello:

Indeed ...
Makes me wonder why it would be worded in that rather confusing manner.
Wouldn't it have been much better (especially for idiots like mysef) to do it like this:

about:preferences#privacy
Enable HTTPS-Only Mode        -> false

ie: no double negatives

But that is in the about:preferences page.

The UI I does not have True or False (boolean) options.
It just has a circle, like box to tick but round.

Like this:

O   Don’t enable HTTPS-Only Mode  

So ...

If I don't tick the circle, it does/should not set the option Don’t enable HTTPS-Only Mode
If I do tick the circle, it does/should set the option Don’t enable HTTPS-Only Mode

Seems there's something amiss (?).

Thanks for your input.

Best,

A.

Hello:

Thanks for the prompt reply.

Yes, I had read something here about that some time ago.

Always do that to make sure any package is downloaded intact.
But as my installations/updates/upgrades all go through apt, I'd never seen this before.

I have inherent trust in Devuan repositories, what I do not trust is my sometimes flaky ADSL.  8^/

What called my attention is that this seems to be a FF thing as Pale Moon does not issue a warning.

Best,

A.

Hello:

For starters:
See here and here.

Best,

A.

Hello:

Some dependency issue (?)

Not necessarily.

If it is being installed from the correct Devuan repositories, apt install digikam (as sudo or root) should suffice.

I run Beowulf (not Daedalus) with a backported kernel and XFCE so if I try to install it a HUGE 176MB of files get drawn in.
I do not like KDE so it is definitely not for me.

But being Daedalus a recent release, you should check if all dependencies are being met, maybe something slipped through the packager's error detecting sieve, happens sometimes:

~$ apt show digikam
Package: digikam
Version: 4:5.9.0-1+b1
Priority: optional
Section: graphics
Source: digikam (4:5.9.0-1)
Maintainer: Debian KDE Extras Team <pkg-kde-extras@lists.alioth.debian.org>
Installed-Size: 3731 kB
Depends: digikam-private-libs (= 4:5.9.0-1+b1), libc6 (>= 2.14), libgcc1 (>= 1:3.0), libkf5configcore5 (>= 4.97.0), libkf5coreaddons5 (>= 4.100.0), libkf5filemetadata3 (>= 5.1.0.1), libkf5i18n5 (>= 4.97.0), libqt5core5a (>= 5.11.0~rc1), libqt5gui5 (>= 5.4.0), libqt5sql5 (>= 5.4.0), libqt5widgets5 (>= 5.4.0), libstdc++6 (>= 4.1.1), perl:any, libqt5sql5-sqlite, libqt5sql5-mysql, digikam-data (= 4:5.9.0-1), kipi-plugins (= 4:5.9.0-1+b1)
Recommends: www-browser, ffmpegthumbs
Suggests: digikam-doc, systemsettings
Homepage: http://www.digikam.org
Tag: field::arts, hardware::camera, implemented-in::c++,
 interface::graphical, interface::x11, role::program,
 scope::application, suite::kde, uitoolkit::qt, use::browsing,
 use::learning, use::organizing, use::searching, use::viewing,
 works-with::image, works-with::image:raster, x11::application
Download-Size: 3577 kB
APT-Sources: http://deb.devuan.org/merged beowulf/main amd64 Packages
Description: digital photo management application for KDE
~$

In my case (Beowulf), it boils down to this:

Depends:

digikam-private-libs (= 4:5.9.0-1+b1)
libc6 (>= 2.14)
libgcc1 (>= 1:3.0)
libkf5configcore5 (>= 4.97.0)
libkf5coreaddons5 (>= 4.100.0)
libkf5filemetadata3 (>= 5.1.0.1)
libkf5i18n5 (>= 4.97.0)
libqt5core5a (>= 5.11.0~rc1)
libqt5gui5 (>= 5.4.0)
libqt5sql5 (>= 5.4.0)
libqt5widgets5 (>= 5.4.0)
libstdc++6 (>= 4.1.1)
perl:any
libqt5sql5-sqlite
libqt5sql5-mysql
digikam-data (= 4:5.9.0-1)
kipi-plugins (= 4:5.9.0-1+b1)

Once you get your own (Daedalus) depends list, check to see if the right libraries/versions are present and let us know.

Someone who knows more than I about this will surely chip in.

Best,

A.

Hello:

First we need to know what your exact keyboard layout is.
I take it that it is an English language layout, yes?

Does it have an identifying sticker label somewhere?

---

---

Please post a photo of the sticker label.

Best,

A.

Hello:

As a system daemon?

I have been using timeshift for many years now.
But it is not set up as a daemon (at least not since I started using it).

It runs cron jobs which you set up when you configure it to do what you want.
ie: schedule the [hourly, daily, weekly, monthly] snapshots.

And if you need to take one manually, you just do it directly from the UI.

See here and here.

Bear in mind that the original developer/maintainer (teejee) closed shop and it is now maintained by the people at Linux Mint.

HTH.

Best,

A.

Hello:

In my opinion, it was just pour la galerie, so to speak. ie: an effort to, in the early stages of the systemd takeover, appease those who voiced their dissent.

But ...
Debian with another init?
Please ...

There was some more smoke and mirrors FUD from a self described Debian insider sometime ago but it was just that.

Sorry to be the one to break the news to you but that is definitely *not* in Debian's plans.
Deprecating SystemV support was the last step in that direction.

[1] the asterisks are not mine, they are in the original.

The inevitable result will be that in a very short time there will be no SystemV compatible packages in the Debian repositories as devs/maintainers will not include init scripts for a deprecated init in their packages, something that will inevitably extend to all Debian based distributions using systemd.

I've said it many times before: there is a lot of moolah behind making systemd the de-facto init for the Linux ecosystem.
systemd is nothing but a MS registry for Linux and the main purpose is to turn Linux into a MS type OS, with all that such a thing implies.

Like a poster at The Register once said with respect to systemd:

But there's nothing new at hand: it is the old MS embrace, extend, and extinguish that has been going on for decades, only that now there's active and quite visible participation from IBM/RH and last but not least Microsoft, corporation that that went from labelling Linux a cancer to wanting to become best friends with it while everyone smiled and said "how nice of them to do so".

Devuan (and derivatives) is still holding on but who knows for how long this will be so.

Best,

A.

Hello:

Seeing that System Rescue actuallu finds the keyboard, look at what its logs have to say about it:

~$ sudo dmesg | grep -i keyboard

As to the touchpad, see what x11 has to say:

xinput list   #if you don't have it you need to install it:

sudo apt install xinput

Please post your findings.

Best,

A.

Hello:

Yes, but it will have to wait till I have some time to do that.
For now, I seem to have solved the problem by installing 91.9.1esr.

I do not use the 1000HE much, just roast coffee with it one a fortnight and keep it updated.

As I have not had to do any local travel since a couple of years before the pandemic hit, browser usage has been limited to accessing the web to check on something while/if my box was off-line which is not frequent so I cannot really say at which point this started happening.

Although I suspect it is this last (available) version

But something is amiss: either a bug or FF code now does things it did not do in previous versions.
Would not be at all surprised.

Thanks in advance.

Best,

A.