Desktop Client Ubuntu 22.04 compatibility

I upgraded my PC from Ubuntu 20.04 to 22.04 to get a first idea on how things look like and if/how everything works as expected.

Sadly, the desktop client does not start any more. I remove the software and dependencies completely, and reinstalled the package from the official ubuntu software repo, but its still not working.
I looked into the original ownCloud repo and saw that the latest version available there is for Ubuntu 21.10:
So am I too early with testing or is something wrong with my maching?

Thank you and best regards!

1 Like

22.04 support for 2.10 is in QA right now, should be available soon (read: next week).


The updated builds have been deployed. You can install ownCloud on 22.04 normally now.


Thank you!

In the official Ubuntu 22.04 repo, there is still version 2.6.3 – when will that be updated?

Probably never since it comes from upstream Debian. You’re better off to add the ownCloud client repo to stay up to date.

It worked for me using the link indicated > Ubuntu 22.04. I could not install the debs, but the command line installation did the job:
(just launch it or copy/paste the commands in it)
Nautilus integration ???
I could not install Nautilus integration (which stopped working a long time ago alread on Ubuntu 20.04
I would be interested to know a way to get it back

I have the same issue; Owncloud isn’t running on startup and doesn’t open when activating the application shortcut. Typing “owncloud” in a terminal gives me a memory error. Reinstalling either doesn’t help (via software center or apt-get) or doesn’t seem to work at all (with the commands on the instructions-page or the *.sh. Adding the trusted key gives the following errors:

Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
2022-05-18 13:40:57 URL: [1412/1412] -> "-" [1]
gpg: invalid key resource URL '/etc/apt/trusted.gpg.d/isv:ownCloud:desktop.gpg'
gpg: Schlüsselblockhilfsmittel`(null)': Allgemeiner Fehler
gpg: Schlüssel 4ABE1AC7557BEFF9: 1 Beglaubigung wegen fehlendem Schlüssel nicht geprüft
gpg: Schlüssel D94AA3F0EFE21092: 3 Beglaubigungen wegen fehlender Schlüssel nicht geprüft
gpg: Schlüssel 871920D1991BC93C: 1 Beglaubigung wegen fehlendem Schlüssel nicht geprüft
gpg: Anzahl insgesamt bearbeiteter Schlüssel: 10
gpg:       ignorierte neue Schlüssel: 10

Someone on gave the following advice, that didn’t fix my problem, though:

I had the same issue. Owncloud doesn’t like php8.1 (yet). I finally got Owncloud running by installing php7.4 on Ubuntu 22.04. (I also installed php7.3 just to make sure).

Instructions on installing a previous version of PHP are here (make sure you read to the end of the instructions to set the default PHP version)

You’ll need to also install PHP modules:

apt install -y libapache2-mod-php7.4 \
php7.4-apcu \
php7.4-mysql \
php7.4-intl \
php7.4-curl \
php7.4-json \
php7.4-gd \
php7.4-xml \
php7.4-mbstring \

Isn’t anybody able to help me, please?

Same problem here… After upgrading to 22.04 no more owncloud client… :frowning: not able to get it to work after it is installed…

Hi again. Finally managed. First installed PHP 7.4 and set to default, then followed this recipe on how to avoid the key signing issue ( then apt update and install owncloud-client.

now all good :slight_smile:

1 Like

Hi! Thanks for your help! I still don’t have it running, though. But I am not sure if I use those instructions correctly. This is what happens with the keys:

claudius@claudius-B450-AORUS-M:~$ sudo apt-key adv --keyserver --recv-keys 4ABE1AC7557BEFF9
[sudo] Passwort für claudius: 
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
Executing: /tmp/apt-key-gpghome.wrEBpIUG82/ --keyserver --recv-keys 4ABE1AC7557BEFF9
gpg: Schlüssel 0700205DFD41A71A: vom Import-Aufpasser zurückgewiesen
gpg: Anzahl insgesamt bearbeiteter Schlüssel: 1
claudius@claudius-B450-AORUS-M:~$ sudo apt-key adv --keyserver --recv-keys D94AA3F0EFE21092
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
Executing: /tmp/apt-key-gpghome.9ce5Ko5O5P/ --keyserver --recv-keys D94AA3F0EFE21092
gpg: Empfangen vom Schlüsselserver fehlgeschlagen: Verbindung im DNS geschlossen
claudius@claudius-B450-AORUS-M:~$ sudo apt-key adv --keyserver --recv-keys 871920D1991BC93C
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
Executing: /tmp/apt-key-gpghome.ezRRtlkaPF/ --keyserver --recv-keys 871920D1991BC93C
gpg: Schlüssel 0700205DFD41A71A: vom Import-Aufpasser zurückgewiesen
gpg: Anzahl insgesamt bearbeiteter Schlüssel: 1

I think this is the crux:

gpg: Schlüssel 0700205DFD41A71A: vom Import-Aufpasser zurückgewiesen

“Key … rejected by import watchdog”

That warning in your command’s output is relevant.

See the following article for better methods: apt-key Is Deprecated. How To Add OpenPGP Repository Signing Keys Without It On Debian, Ubuntu, Linux Mint, Pop!_OS, Etc.

1 Like

Thank you so much! Off to a new error message!

It now says that it can’t download the key file because there is no such file or directory:

sudo wget -O- <>  gpg --dearmor | sudo tee /usr/share/keyrings/owncloud_archive-keyring.key
bash: Datei oder Verzeichnis nicht gefunden

Which I find very weird because the url is the one I can open in my browser and successfully downloaded the keyfile from by hand. What do I do?

I want to add that I am barely understanding what I’m doing and following the instructions to my best ability.

Lose the ‘sudo’ at the beginning of your command. You shouldn’t need root privileges to download a file.

You are missing a space between the capital “O” and the dash that follows it. (I see that it was not used in the example from the article I shared, but those types of articles are just reference material for me rather than a literal guide, so I am not viewing it from the same perspective that you are., and wouldn’t likely notice such a detail since I would be typing the command, not using copy and paste.) That trailing space may or may not matter, but since the syntax in the man page uses “-O file” and that dash means to write to standard output instead of a file, I like to keep the space after the “O”.

The angle bracket sandwich <URL goes here> is only an illustrative device, and those brackets should not be part of your actual command. Those will definitely cause the command to fail.

You are also missing a critical pipe character (this character: | ) between the URL in the wget command and the gpg command.

Here is what that command line does:

  1. Download ASCII armored GPG public repo key using wget redirecting to standard out
  2. Use redirected output from the wget command to convert ASCII to binary using gpg
  3. Run the redirected output from the gpg command through tee running as root via sudo so that it can be written to a folder that is not writeable by a standard user

Heureka! Finally! Now this got it working. Thank you so much!

Yeah, so, I know enough to get the general gist of what should be happening. But I am not experienced in using the syntax like a trained programmer would be. This means that all the little things like dashes and spaces always will trip me up.

Generally I found that whoever writes a tutorial knows the syntax and I basically don’t understand what the role of “-O” or of the vertical lines in this three-part-process is you outlined. So copy and paste is generally my best bet. Also from my experience there sometimes is an “implied sudo” since “everybody” knows what to run with sudo and what not to. This leads to my experience that a lot of times I can get things to run by trying running them as root.

I know that this is not great, but when one of the three most important programs for my work breaks, there are not a lot of options. And I want to avoid going back to windows after five years of daily driving ubuntu, which was basically my plan b.

All that just to say again: Thank you so much for your time, patience and thoroughness!


@silvain not sure which packages you installed. Ubuntu calls the integration packages nautilus-owncloud, whereas in our repository, they are called owncloud-client-nautilus etc. The extension works fine here.

@Plastikschnitzer & @LinkP, the Debian team in charge is working on providing more recent packages. You can also use our repositories or the AppImages.

For the record, @eivindrkvandal, the desktop client does not use PHP anywhere. These packages you installed are not needed.

Regarding the apt key import issue, I think we have to update the documentation. Thanks for the hint.

1 Like

Hi! I’ve installed a new computer with Ubuntu 22.04 now, and then installed owncloud client again. And you are totally right @fmoc . PHP not needed.
But, as expected, I still needed to follow the “trusted key” recipe. However, I find the Ubuntu-community recipe that you’ve linked in the installation instructions to be slightly “non-informative”. So I would follow a recipe that I googled and linked in my previous post. However, just realized that I did link the “wrong” recipe in my previous post , so, below is the link tot the “how-to” which I used, to add the owncloud key to the trusted.gpg.d folder with great success, and then enabled me to easily install the oc client.

PS: I see that several sw providers (kdnelive, google etc) has a built in way to get their keys added to the trusted key folder, will it be possible for you to consider build this in future installable versions?