I installed the Nextcloud Office Desktop app the morning after Nextcloud shipped it, expecting a five-minute job. The first launch on Ubuntu died with libEGL.so.1: cannot open shared object file. The app is the signed build of Euro-Office, which its documentation describes as a fork of ONLYOFFICE Document Server maintained independently, and it comes from a proper signed APT and DNF repository. Per Nextcloud’s blog, the first production-ready version of Euro-Office was released on June 9, 2026, and the blog asks contributors to keep to the project’s AGPL v3 license. What the download page does not tell you is which libraries the package forgets, or that pointing it at your Nextcloud does almost nothing until the server has an editor of its own.
These notes cover the repository and .deb installs, the three missing-library errors, Wayland, the Nextcloud connection and a run against ONLYOFFICE Desktop Editors. After a false start on Proxmox, I ran it in November 2026 on Google Cloud VMs: version 9.3.8 on Ubuntu 26.04.1 LTS (box1, X11 under Xvfb plus one Weston run) and on Fedora 45, against Nextcloud 34.0.6.
Checking the CPU before anything else
My first attempt was on a Proxmox VM with the kvm64 CPU type (the backend default when none is set), and the binary refused to start at all. The Qt and Chromium libraries inside the package are built for the x86-64-v2 baseline (SSE4.2, POPCNT), and kvm64 only exposes the older baseline. So the dynamic loader stops before a window ever appears.
/opt/nextcloud-office/nextcloudoffice/DesktopEditors: CPU ISA level is lower than required
EXIT=127
Any physical machine from the last ten years passes this check. In a VM, set the CPU type to host or the migration-safe x86-64-v2-AES (Proxmox), or host-passthrough (libvirt), before you install anything, because no package fix gets around it. I moved to cloud VMs with a modern CPU model, and the same package started fine there. Beyond the CPU, the requirements are modest.
- An x86_64 machine (arm64 .debs and aarch64 RPMs exist, untested here)
- About 1.7 GB of free disk
- A graphical session, X11 or Wayland
Which of the two you run changes the dependency story, as the Wayland section below shows. The disk figure is the app plus the 230 to 290 dependencies a minimal image needs.
Installing from the APT repository on Ubuntu
Nextcloud publishes a signed repository at download.nextcloud.com/office/repo, and that’s the method I’d use on any machine you plan to keep. With the repository in place, apt upgrade picks up new builds and you never download a .deb by hand again. Start by fetching the signing key into its own keyring.
sudo install -d -m 0755 /etc/apt/keyrings
sudo curl -fsSL https://download.nextcloud.com/office/repo/nextcloud-office.asc -o /etc/apt/keyrings/nextcloud-office.asc
Check the fingerprint before you trust it. Nextcloud doesn’t publish it anywhere else that I found, so the best you can do is compare it with the value below and with the key ID on the signed RPMs.
gpg --show-keys /etc/apt/keyrings/nextcloud-office.asc
Look for a key ID ending in A287C3D0. Mine matched, and it is the same key that signs the RPMs further down.
pub rsa4096 2026-08-25 [SC]
C013F0BEF96800BBBC4D93DDE6E70E5FA287C3D0
uid Nextcloud Office Package Signing Key <[email protected]>
Add the repository and refresh the package lists. The signed-by option limits that key to this one repository instead of trusting it for everything.
echo "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/nextcloud-office.asc] https://download.nextcloud.com/office/repo/deb stable main" | sudo tee /etc/apt/sources.list.d/nextcloud-office.list
sudo apt-get update
Before installing, ask apt which builds the repository carries, so you know what you’re about to get and what you could roll back to.
apt-cache policy nextcloud-office-nextcloudoffice
Two versions were published when I ran it, and the newer one is the candidate. Because the older build stays in the repository, you can pin back with apt install nextcloud-office-nextcloudoffice=<version> if an update breaks something.
nextcloud-office-nextcloudoffice:
Installed: (none)
Candidate: 9.3.8-0
Version table:
9.3.8-0 500
500 https://download.nextcloud.com/office/repo/deb stable/main amd64 Packages
9.3.6-0 500
500 https://download.nextcloud.com/office/repo/deb stable/main amd64 Packages
The package recommends ttf-mscorefonts-installer, and apt installs recommended packages by default. That one stops a non-interactive install at a EULA prompt. Accept it up front through debconf, then install. Skip the first line and an unattended script either sits at the prompt or, under a noninteractive frontend, fails on the declined EULA.
echo ttf-mscorefonts-installer msttcorefonts/accepted-mscorefonts-eula select true | sudo debconf-set-selections
sudo apt-get install -y nextcloud-office-nextcloudoffice
On a minimal Ubuntu 26.04 cloud image that pulled in 278 packages. The app lands in /opt/nextcloud-office/nextcloudoffice with a launcher at /usr/bin/nextcloud-office-nextcloudoffice. Ask dpkg for the status and size.
Status: install ok installed
Installed-Size: 1403407
Version: 9.3.8-0
Installed-Size is in kilobytes, so that’s 1.4 GB on disk for the app alone, before the fonts and codecs it brings along. Keep that in mind for thin clients with small disks, because the 278 dependencies land on top of it and most of them are codecs and fonts you may never use in an office suite.
Installing the .deb directly with a checksum
If you would rather not add a repository (a kiosk image, a one-off test), the same signed package is attached to the GitHub releases. I ran this on a fresh Ubuntu 26.04.1 VM, and once more on Ubuntu 24.04.5. Look up the latest tag instead of hardcoding it, so the commands keep working after the next release.
NCO_VER=$(curl -s https://api.github.com/repos/nextcloud-releases/Office-DesktopEditors/releases/latest | grep -oP '"tag_name": "v\K[^"]+')
echo $NCO_VER
curl -sLO https://github.com/nextcloud-releases/Office-DesktopEditors/releases/download/v${NCO_VER}/nextcloud-office-nextcloudoffice_${NCO_VER}-0_amd64.deb
The download is 314 MB. Hash it and compare the result with the sha256 digest GitHub shows next to the asset on the release page.
sha256sum nextcloud-office-nextcloudoffice_${NCO_VER}-0_amd64.deb
For the 9.3.8 build the digest was this one, identical on both Ubuntu releases. A different value means a corrupted or substituted file, so delete it and download again.
4d24d9772260757a50266385d760deefe804a915a94b3a79987ae390fca37a51 nextcloud-office-nextcloudoffice_9.3.8-0_amd64.deb
Install it with apt instead of dpkg, because dpkg would leave the dependencies unresolved. The EULA preseed goes first again.
echo ttf-mscorefonts-installer msttcorefonts/accepted-mscorefonts-eula select true | sudo debconf-set-selections
sudo apt-get install -y ./nextcloud-office-nextcloudoffice_${NCO_VER}-0_amd64.deb
On 26.04 that was 278 newly installed packages, with libxcb-cursor0 coming from universe, and dpkg reported install ok installed with the same 1403407 KB Installed-Size as the repository build. On 24.04 it was 290 packages and the same clean status. A machine installed this way gets no updates, though. Either add the repository later or repeat the download when a new tag appears.
Fixing the libraries the package forgets
Here’s where the five-minute job ended. On a desktop install of Ubuntu you probably already have every library the app wants, because GNOME pulled them in. A minimal or server image with a desktop added later is different. The package’s dependency list is three libraries short, and you meet them one at a time.
Error: “libEGL.so.1: cannot open shared object file”
The launcher exits with code 127 straight away, and nothing appears on screen.
/opt/nextcloud-office/nextcloudoffice/DesktopEditors: error while loading shared libraries: libEGL.so.1: cannot open shared object file: No such file or directory
EXIT=127
The package’s Depends line does not mention libegl1 at all. I grepped dpkg -s for it and got 0, so apt had no reason to install it. Add it yourself.
sudo apt-get install -y libegl1
Two packages come in, the EGL loader and Mesa’s EGL driver. After that, ldd on the main binary stops reporting anything as not found.
Error: Could not load the Qt platform plugin “xcb” in “” even though it was found
The second launch got further, printed two harmless qt.multimedia warnings about pipewire, and then aborted with a core dump.
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: vkkhrdisplay, wayland-brcm, wayland-egl, wayland, xcb, minimal, vnc, eglfs, minimalegl, linuxfb, offscreen.
Reinstalling does not help, whatever the message says. The plugin file is there, but two of the libraries it links against are not, and ldd on the main binary cannot see that. Ask about the plugin itself.
ldd /opt/nextcloud-office/nextcloudoffice/platforms/libqxcb.so | grep "not found"
It names the two XCB helper libraries that the Qt plugin needs for window manager hints and keyboard symbols. My run printed each line twice; I show them once.
libxcb-icccm.so.4 => not found
libxcb-keysyms.so.1 => not found
Both come from small packages in Ubuntu’s universe component on 26.04, which is enabled by default, so there’s no extra repository and nothing to pin or watch for updates later.
sudo apt-get install -y libxcb-icccm4 libxcb-keysyms1
After that the window opened. The pipewire warnings stay, and you can ignore them unless you embed audio or video in slides. Building an image for several machines? Put all three packages on the same apt install line as the app and you’ll skip both errors.
Running it on Wayland, and where libxcb-cursor0 fits
The 9.3.8 release notes carry four Wayland fixes, among them “wayland: paste from system clipboard in login windows” (desktop-sdk#23) and “wayland: type the character the keyboard layout produces” (desktop-sdk#41). The only dependency line is “debian: add missing dependancies” (desktop-apps#86), which added libpulse0, libopengl0 and libnss3. The notes never mention libxcb-cursor. It doesn’t need a mention, because libxcb-cursor0 is already in the .deb’s Depends, so apt installs it with the app.
To see what a Wayland session changes, I started a headless Weston 14.0.2 compositor on the 26.04 box (no Xwayland) and launched the app with WAYLAND_DISPLAY set, DISPLAY unset and no QT_QPA_PLATFORM override. The launcher doesn’t force a platform, so Qt picked its Wayland plugin by itself. Eight processes came up, the home window drew with client-side decorations, and the main process had loaded this plugin:
P=$(pgrep -f -o 'nextcloudoffice/DesktopEditors')
grep -o 'libqwayland[^ ]*\|libqxcb[^ ]*' /proc/$P/maps | sort -u
It printed only libqwayland.so, with no libqxcb.so beside it. The terminal also showed a GDK seat assertion and some libEGL and ZINK warnings from the VM’s lack of a GPU, none of which stopped the window. Then I removed the cursor library on purpose to see which session depends on it.
sudo dpkg --remove --force-depends libxcb-cursor0
Under X11 the app now aborts with exit code 134, and Qt names the missing package in its first line, which is more helpful than the icccm and keysyms failure above:
qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin.
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
The same launch in the Weston session still opened the window, with seven processes and libqwayland.so mapped. The Wayland path doesn’t touch libxcb-cursor at all. Forcing QT_QPA_PLATFORM=xcb inside the Wayland session brought the X11 error straight back. If you ever see that cursor message on a GNOME or KDE Wayland desktop, something has set the platform to xcb (an environment file or a desktop launcher override), and either removing that or running sudo apt-get install -y libxcb-cursor0 fixes it. I put the package back the same way. I only removed libxcb-cursor0 for this test, so I can’t say whether a Wayland session also gets by without the icccm and keysyms libraries.
Installing on Fedora with DNF
The RPM side of the same repository has x86_64 and aarch64 directories, and the packages are signed with the key from earlier. Import the key, then create the repo file.
sudo rpm --import https://download.nextcloud.com/office/repo/nextcloud-office.asc
sudo vim /etc/yum.repos.d/nextcloud-office.repo
Paste this definition. With $basearch in the URL, the same file works on an ARM laptop, and repo_gpgcheck makes dnf verify the metadata as well as each package.
[nextcloud-office]
name=Nextcloud Office
baseurl=https://download.nextcloud.com/office/repo/rpm/stable/$basearch
enabled=1
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://download.nextcloud.com/office/repo/nextcloud-office.asc
Install the package. Fedora 45 ships dnf5, so the output format differs from older guides.
sudo dnf -y install nextcloud-office-nextcloudoffice
The transaction summary is bigger than you might expect for an office suite.
Transaction Summary:
Installing: 237 packages
Total size of inbound packages is 484 MiB. Need to download 484 MiB.
Confirm the signature on what landed. I do this on any third-party repository, since a misconfigured repo file can quietly disable checking.
rpm -q --qf '%{RSAHEADER:pgpsig}\n' nextcloud-office-nextcloudoffice
You should see the Nextcloud Office key ID. Mine was signed the night before I installed it.
RSA/SHA512, Sat 14 Nov 2026 12:33:59 AM UTC, Key ID e6e70e5fa287c3d0
The RPM does better than the .deb on dependencies, because the EGL and XCB helper libraries all came in with it. It misses a different one, though.
Error: “libOpenGL.so.0: cannot open shared object file” on Fedora
My first launch on Fedora failed exactly like the Ubuntu one, with another library this time.
/opt/nextcloud-office/nextcloudoffice/DesktopEditors: error while loading shared libraries: libOpenGL.so.0: cannot open shared object file: No such file or directory
EXIT=127
On Ubuntu that library comes from libopengl0, which the .deb does list. On Fedora, ask dnf which package provides it.
dnf provides 'libOpenGL.so.0()(64bit)'
It’s a small package from the base Fedora repository, about 145 KiB once installed, so there’s no good reason to leave it out of a kickstart file or an image build.
libglvnd-opengl-1:1.7.0-10.fc45.x86_64 : OpenGL support for libglvnd
Repo : fedora
Install it, and the next launch gets past the loader and opens the window.
sudo dnf -y install libglvnd-opengl
With that in place, eight processes came up under /opt/nextcloud-office and the home screen rendered. Fedora’s fontconfig printed a run of 48-guessfamily.conf warnings on the terminal in my session, and those come from the newer fontconfig rather than the app. A full desktop install may already have libglvnd-opengl, but my minimal box didn’t, so check with rpm -q before you assume.

On Fedora it unpacks to 1.6 GB in /opt/nextcloud-office, a little more than the .deb’s 1.4 GB. Plan disk space for the larger number if you package for both.
Connecting the app to your Nextcloud
Local editing works the moment the window opens. You click Open local file, pick a DOCX, and you’re editing. The cloud connection is the part that makes this a Nextcloud product, and it’s also where I lost the most time, even though the dialog itself is simple.
- Click Clouds + in the home sidebar.
- Leave the provider on Nextcloud.
- Type
https://cloud.example.comin Server URL. - Click Connect now and log in.
The numbers in the screenshot follow those steps, and the login page opens in a new tab inside the app.

- 1Clouds +
- 2Nextcloud
- 3Server URL
- 4Connect now
A one-entry dropdown surprised me. The Euro-Office DesktopEditors README lists “Moodle, Nextcloud, ownCloud, Seafile, Liferay, kDrive” as cloud connections, yet the signed build I installed offered only Nextcloud. Nextcloud’s announcement says you can connect more than one instance to the app, so several Nextcloud servers work, but nothing else.
Why a self-signed certificate fails with “Check the cloud office URL”
I tested a second hostname on the same server with a self-signed certificate, the way a lot of home labs run Nextcloud. The app rejects it inline, with no certificate prompt and nothing in the terminal.

“Check the cloud office URL” reads like a typo warning, but the URL was fine and the certificate was the problem. The primary hostname on the same server, which has a Let’s Encrypt certificate, connected on the first try. For a Nextcloud that’s internal only, a DNS-01 Let’s Encrypt certificate is easier than fighting the trust store, because it needs no inbound port and every client already trusts it. Since the error never mentions certificates, it’s worth trying the URL in a browser on the same machine before you chase typos. I didn’t test whether adding a private CA to the system store changes the outcome.
What happens when the server has no editor
My first successful login looked like a success and wasn’t. “Connect now” opened the ordinary Nextcloud web interface in an app tab, and the instance never appeared under Clouds on the home screen. Clicking lab-notes.docx popped up a GTK “Save As” dialog to download the file.

Why a download? The desktop app doesn’t edit cloud files by itself. It hands them to the Euro-Office integration on the server, and my stock Nextcloud 34 install had no such editor app enabled. So the server needs an editor before the desktop connection does anything useful.
Adding the Euro-Office editor to Nextcloud
Two pieces make up the server side, and both are needed. The app alone has nothing to send documents to, while the DocumentServer on its own is invisible to Nextcloud.
- The
euroofficeNextcloud app - A Euro-Office DocumentServer on HTTPS
My server ran Nextcloud in Docker Compose from /opt/nc, with a service named nextcloud and Caddy as a service on the same Compose network, so the commands below use docker compose exec. On a bare-metal install like the one in our Nextcloud on Ubuntu 26.04 guide, run the same occ lines as sudo -u www-data php occ from the Nextcloud directory. Anyone already running ONLYOFFICE Docs will recognise the shape from integrating ONLYOFFICE Docs with Nextcloud, with different image and app names.
Generate a shared secret first. The DocumentServer and Nextcloud sign every request with it, so both sides need the same value.
export JWT_SECRET=$(openssl rand -hex 24)
echo "$JWT_SECRET" | sudo tee /opt/nc/jwt.txt
sudo chmod 600 /opt/nc/jwt.txt
Keep the same shell open for the occ lines later, because they read $JWT_SECRET, and paste the same value into the Compose file by hand.
Add the DocumentServer to the Compose file next to Nextcloud.
sudo vim /opt/nc/compose.yaml
This is the service block I added under services:, with your secret in place of the placeholder.
docs:
image: ghcr.io/euro-office/documentserver:latest
environment: [JWT_ENABLED=true, JWT_SECRET=your-jwt-secret-here]
Give it its own HTTPS hostname in the reverse proxy. With Caddy that’s three lines in the Caddyfile.
sudo vim /opt/nc/Caddyfile
Caddy requests the certificate for the new name on its own, as long as the DNS record already points at the server.
docs.example.com {
reverse_proxy docs:80
}
Bring the stack up. The image is 1.04 GB, so the first pull takes a minute. Compose doesn’t recreate a running Caddy just because its bind-mounted Caddyfile changed, so restart that service (mine is named caddy) to load the new site.
cd /opt/nc
sudo docker compose up -d
sudo docker compose restart caddy
curl -s https://docs.example.com/healthcheck
Once the DocumentServer is ready, the healthcheck answers true; on a first start it can print nothing for a minute while the server boots and Caddy fetches the certificate, so repeat it. Then install the Nextcloud app and point it at the server.
sudo docker compose exec -u www-data nextcloud php occ app:install eurooffice
sudo docker compose exec -u www-data nextcloud php occ config:app:set eurooffice DocumentServerUrl --value=https://docs.example.com/
sudo docker compose exec -u www-data nextcloud php occ config:system:set eurooffice jwt_secret --value="$JWT_SECRET"
sudo docker compose exec -u www-data nextcloud php occ config:system:set eurooffice jwt_header --value=Authorization
sudo docker compose exec -u www-data nextcloud php occ config:system:set overwrite.cli.url --value=https://cloud.example.com
I set the secret and header in system config (the app’s README uses config:app:set, and the app falls back to the system eurooffice array when the app value is empty). The last line gives Nextcloud the public URL to use when it builds links outside a web request. I typed these lines one at a time, so add -T and --interactive=false per Docker’s exec reference if you put them in a script. Now run the app’s own connection test.
sudo docker compose exec -u www-data nextcloud php occ eurooffice:documentserver --check
A working setup prints the DocumentServer version. Anything else, usually the token error, means the two secrets differ.
Document server https://docs.example.com/ version 9.3.8.37 is successfully connected
Back on the desktop, I clicked Clouds + and connected to the same URL again. This time the Nextcloud tab opened in a stripped-down desktop mode without the web header, and the instance showed up under Clouds with my username beneath it.
Editing DOCX, XLSX and ODT files
With the editor in place, clicking lab-notes.docx in the cloud tab opened a native editor tab instead of a download. I typed one line and watched the status bar.

- 1lab-notes.docx tab
- 2Edited line
- 3All changes saved
The lab-notes.docx tab sits next to the cloud tab, the Edited line is the one I added, and All changes saved appeared shortly after I stopped typing. I don’t trust a status bar on its own, so I checked the file on the server.
sudo docker compose exec nextcloud sh -c 'ls -l data/philip/files/Lab/lab-notes.docx; ls data/philip/files_versions/Lab/'
The modification time matches the edit. Nextcloud also kept the previous copy as a version, so a bad save can be rolled back from the web interface.
-rw-r--r-- 1 www-data www-data 27572 Nov 14 10:48 data/philip/files/Lab/lab-notes.docx
lab-notes.docx.v1794651963
Unzipping the saved DOCX and searching word/document.xml found Edited from Nextcloud Office Desktop on box1 at 10:48 UTC., so the text really reached the stored file. A timestamp alone would only prove that something was written.
Spreadsheets got the same treatment. I built lab-budget.xlsx with Python’s openpyxl: four hardware rows, a line total of quantity times price in column D, and =SUM(D2:D5) in D6. openpyxl writes formulas without a cached result, so the stored D6 started out empty. I uploaded it to Nextcloud and opened it from the cloud tab.

- 1lab-budget.xlsx tab
- 2Edited quantity
- 3SUM formula
- 4Recalculated total
- 5All changes saved
The lab-budget.xlsx tab opened as a spreadsheet editor and showed a total of 1568. I changed the Mini PC quantity in B2 from 2 to 5 (the Edited quantity), and the Recalculated total in D6 jumped to 2555 at once, with the SUM formula intact in the formula bar. All changes saved appeared in the status bar, and I closed the editor tab before checking the server, where the file carried the minute I closed it. Don’t shut the laptop lid the moment the status bar goes quiet.
sudo docker compose exec nextcloud sh -c 'ls -l data/philip/files/Lab/lab-budget.xlsx; ls data/philip/files_versions/Lab/'
A new version file sits next to the updated spreadsheet, just as with the DOCX.
-rw-r--r-- 1 www-data www-data 8950 Nov 14 12:01 data/philip/files/Lab/lab-budget.xlsx
lab-budget.xlsx.v1794657487
To check the cells rather than the timestamp, I copied the file out and pulled the two cells from the sheet XML.
unzip -p lab-budget.xlsx xl/worksheets/sheet1.xml | grep -oE '<c r="(B2|D6)"[^>]*>(<f>[^<]*</f>)?<v>[^<]*</v></c>'
The new quantity is there, the formula survived as a formula, and the app filled in the cached result that openpyxl had left blank. file still called it Microsoft Excel 2007+, so nothing got converted along the way.
<c r="B2"><v>5</v></c>
<c r="D6"><f>SUM(D2:D5)</f><v>2555</v></c>
A local copy behaves the same without a server. I opened it with nextcloud-office-nextcloudoffice ~/local-budget.xlsx, changed the SSD price in C3 from 119 to 109 and pressed Ctrl+S. There was no format prompt, and the saved file held <c r="C3"><v>109</v></c> with D6 recalculated to 1528. That covers simple formulas; I didn’t try macros, pivot tables or charts.
ODT is the format people worry about with an ONLYOFFICE-based editor, since its native model is OOXML. I opened an ODT created elsewhere, added a line and saved it back.

Then I checked what was actually written to disk.
file ~/odf-test.odt; unzip -p ~/odf-test.odt mimetype
The mimetype entry confirms it stayed ODT and wasn’t silently converted to DOCX.
/home/philip/odf-test.odt: OpenDocument Text
application/vnd.oasis.opendocument.text
A three-line text document is a weak test of ODF fidelity, and I wouldn’t read more into it than “it round-trips plain text and keeps the format”. Styles, tracked changes and ODS spreadsheets stayed untested, so if your team lives in ODF, run your own documents through it before you switch.
Comparing Nextcloud Office Desktop with ONLYOFFICE
The question I actually wanted answered: is this anything more than ONLYOFFICE with a new logo? Click About at the bottom of the home sidebar, and the dialog is honest about where the code comes from.

- 1Version and build
- 2Euro-Office notice
Version and build reads “Community version 9.3.8.0 (x64 deb) · build 2026-11-13”. The Euro-Office notice says it’s a modified version of ONLYOFFICE, not affiliated with Ascensio System SIA, modified between March and November 2026 and licensed AGPL-3.0-only. The rebrand also stops at the window manager. Under X11, xprop on the home window reported these names:
WM_CLASS(STRING) = "DesktopEditors", "Euro-Office"
_NET_WM_NAME(UTF8_STRING) = "Euro-Office"
Neither says Nextcloud, so a window rule or a taskbar pin in your desktop has to match DesktopEditors or Euro-Office.
For the comparison I installed ONLYOFFICE Desktop Editors 10.0.0 from its GitHub release on the same Ubuntu box and opened the same DOCX in each. Then I summed resident (RSS) and proportional (PSS) memory over every process 45 seconds after launch, taking three samples each.
| Measured on box1 | Nextcloud Office Desktop 9.3.8 | ONLYOFFICE Desktop Editors 10.0.0 |
|---|---|---|
| Download | 314 MB .deb | 266 MB .deb (279357060 bytes) |
| dpkg Installed-Size | 1403407 KB | 1067031 KB |
| Directory under /opt | 1.4G | 1.1G |
| Processes, one DOCX open | 8 | 8 |
| PSS total | 567 to 586 MiB | 569 to 571 MiB |
| RSS total | 1066 to 1085 MiB | 1097 to 1100 MiB |
| Cloud connectors | Nextcloud only | 10 |
| AI Chat, AI Tools, Plugins tab | None | All three |
| Signed APT/DNF repository | Yes | Not checked (I used the GitHub .deb) |
Memory is a wash. Both run eight processes and sit at about 570 MiB of real (PSS) memory with a document open, so don’t pick either on footprint. The RSS totals look twice as large only because shared Chromium pages are counted once per process, which is why PSS is the number to quote. Nextcloud’s build takes about 330 MB more on disk, and I didn’t diff the two trees to find out which files account for it. On a laptop that’s noise; on a fleet of thin clients with 16 GB disks it might decide things.
What each one connects to and adds matters far more. ONLYOFFICE’s home screen has AI Chat and AI Tools in the sidebar and a Plugins tab in the editor ribbon, and Nextcloud’s build has none of them. Its Clouds page lists ten Available clouds, against the single Nextcloud entry in Nextcloud’s dropdown.

- 1Clouds
- 2Available clouds
My pick comes down to the server you edit against. Teams that live in Nextcloud and want a desktop editor with no AI features, no third-party cloud logins and a vendor who answers for the build should take Nextcloud Office Desktop. Anyone who also uses ownCloud, Seafile, Dropbox or Box, or wants the plugins and AI tools, is better off staying on ONLYOFFICE Desktop Editors, which reaches Nextcloud through its own connector anyway. For the servers themselves, our OpenCloud vs ownCloud vs Nextcloud test covers that side.
Euro-Office vs Collabora
These are different engines. Euro-Office comes from ONLYOFFICE and treats Microsoft formats as native, while Collabora is built on LibreOffice and treats ODF as native, so the choice follows your file formats more than any feature list. On the server, Collabora Online plugs into Nextcloud through the richdocuments app, and our Collabora Online deployment guide walks through it with Let’s Encrypt.
I didn’t run Collabora for this article, so I can’t compare the two on the same documents. If you only need a local ODF editor on Fedora, plain LibreOffice from the Fedora RPM or Flatpak is still the lighter option.
What I still don’t know
A few things I couldn’t settle on these boxes, and I’d want answers before rolling the app out to a team.
- How it behaves on GNOME or KDE Wayland on real hardware
- Whether a private CA in the trust store works
- Whether Ubuntu 24.04 needs the same three libraries
- How the aarch64 RPMs run
My Wayland run used a headless Weston compositor with software rendering, which proves Qt picks the Wayland plugin but says nothing about a full desktop’s portals, scaling or GPU drivers. Every other run was an X11 session under Xvfb. On 24.04 I installed the .deb but never launched the GUI. The missing dependencies (EGL and the two XCB helpers on Ubuntu, libglvnd-opengl on Fedora) look like packaging gaps the Euro-Office DesktopEditors project will probably close in a point release. On Fedora, ldd reported nothing missing and the launch still failed, so a real test launch is the check to trust before you bake them into an image. Nextcloud’s own launch post covers the Windows and macOS builds, which I didn’t touch.