Gui unreachable, errors when using cli on 2.1.0.5_stable_2025-03-04 in debian

[ts678]

@enae

followed the documentation.

Note the documentation footer says it’s “Last updated 5 months ago”, probably because

@kenkendk

Does this meant that you had to install the gnome-shell-extension-appindicator and otherwise there was no TrayIcon shown?

If so, I will update the docs to recommend that.

was not clearly retested, but now is a great time to test, with fresh install and no tray icon.

I’m still advocating for another docs change, unless someone can show why it’s incorrect:

@ts678

I wish documentation didn’t say that, as dpkg doesn’t install dependencies.

and there’s now proof that apt worked for you when dpkg didn’t, but reason is not clear.

I’d be a bit surprised if default Debian didn’t install those two binaries, but you could check.

whereis ldconfig hopefully will find it, maybe in /usr/sbin. You can then see how long:

ls -lc /usr/sbin/ldconfig for example. Does time look like apt run, or original install?

Another possibility (it seems unlikely) is that your su didn’t set up PATH to check /usr/sbin.

You can test this with your su again, then printenv PATH

@enae

please say that the command needs the full path of the .deb file

I don’t think that’s quite correct, but it needs to look like a path. A ./ prefix is enough.
I haven’t seen official docs on that, but page below covers that and dependency topic:

Does dpkg -i install dependencies?

For those with GUI, a file browser is another option, as many of them install packages.
The ones I’ve used seem to start gdebi, which officially says it installs dependencies.

Install Dependencies Using dpkg, apt and gdebi discusses their dependency handing.

[kenkendk]

@enae

As you can see on the screenshot, after a fresh install of a network install of Debian, by using dpkg -i duplicati_version.deb => some components are missing (ld-config, start-stop-daemon) in the PATH variable or non executable.

What Debian build is this? It is possible that the .deb package does not correctly list all dependencies.

As @ts678 points out, dpkg should fail if dependencies are missing, where apt will install dependencies.

@enae

here seems that it can be a permissions problem for install some components of Duplicati:

My french is not quite up there, but it seems that it complains that apt does not have access to the .deb package in the Download folder?

@enae

what did bring me again to the same errors before formatting my computer…
and uninstalling Duplicati, and reinstalling it don’t give me access to this automatic passphrase setting up window again.

The password is stored in Duplicati-server.sqlite, so to get the dialog again, you need to delete that database (or at least update some settings in there).

There are a few less destructive ways to (re-)set the passphrase.

What some have used is:

1. Edit the /etc/init.d/duplicati file and add --webservice-password=temp
2. Restart the Duplicati service
3. Login with the password temp
4. Change the password on the Settings page
5. Edit the /etc/init.d/duplicati file and remove --webservice-password=temp
6. Restart the Duplicati service

Remember step 5, because otherwise it will reset your password to temp on each service restart.

[enae]

Hello,
thanks for your answers
about the version of Debian, it’s the same than used last time. The only difference is that, as it’s network install, while the installation process, updates of potentially old softwares are searched, and installed in live.
About the ldconfig and the PATH env, i made this morning a screenshot you can see below

About the ./prefix, it’s ok too

About the error message after Duplicati installation, it tells that the download is made out of the apt sandbox as root because the duplicati2.1.0.5…deb is not accessible from the _apt user (13: permission denied)
I think it’s because i tried to install a .deb package that is not listed in the apt sources.list (/etc/apt/sources.list)
In this case, a good thing could be have an apt repository, so you can add it to a debian installation, and install it just by using apt install Duplicati (will install the last version in the repository)
Another good thing on that, other debian based distributions could use it as it is, just by adding the repository on the sources.list of their distributions.

I’m asking me about one thing:
Wouldn’t be more convenient for you if i make a copy of my debian installation through virtualisation, (like with virtualbox) and send you this, so you’ll can clone the virtual installation, and try as many times you want as many things you need to see for make it work correctly?
Thanks for your help

[kenkendk]

@enae

In this case, a good thing could be have an apt repository, so you can add it to a debian installation, and install it just by using apt install Duplicati (will install the last version in the repository)

Yes, that is planned. At least we can set up a PPA.

@enae

Wouldn’t be more convenient for you if i make a copy of my debian installation through virtualisation, (like with virtualbox) and send you this, so you’ll can clone the virtual installation, and try as many times you want as many things you need to see for make it work correctly?

Sure thing. I have a Virtualbox setup for x64 images. If you can share it, lets try that way.

[enae]

Hi,
well, i’m looking for can share you a virtual config, (config in english) through a google drive space.

[ts678]

@kenkendk

My french is not quite up there, but it seems that it complains that apt does not have access to the .deb package in the Download folder?

@enae

About the error message after Duplicati installation, it tells that the download is made out of the apt sandbox as root because the duplicati2.1.0.5…deb is not accessible from the _apt user (13: permission denied)

This error is easy to spot with web search, where you can maybe get better information, however the basic idea seems to be that apt, as a security measure, doesn’t use root to download, and apparently copying from the local file is affected by the downloading rule.

For example, if you download to somewhere in your home folder, this user can’t access:

_apt:x:105:65534::/nonexistent:/usr/sbin/nologin (showing an /etc/passwd entry)

if (as is usually true) ls -ld ~ shows your home directory isn’t accessible by everyone.

If as a test, I move the deb to /tmp (not very secure, but it’s a test), message vanishes.

For the path issues, seeing a recent ls -lc makes me think the package of Debian that you installed surprisingly (to me) didn’t have them. Was it some sort of minimal package?