Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: On SUSE Linux, Virtual File support only works with AppImage, not the repo install #6737

Closed
5 of 8 tasks
woiwoiwoiwoi opened this issue May 7, 2024 · 2 comments
Closed
5 of 8 tasks

Comments

@woiwoiwoiwoi
Copy link

woiwoiwoiwoi commented May 7, 2024

⚠️ Before submitting, please verify the following: ⚠️

Bug description

I recently had to switch from Debian Unstable to OpenSUSE Tumbleweed. Virtual File support worked perfectly for the past year or so on Debian, but on SUSE the Nextcloud client crashes if it is turned on.

This applies to the version installed from the OpenSUSE Tumbleweed repository (on Debian, I also used the repository version). When using the AppImage of the Nextcloud Desktop client, virtual file support seems to be working fine.

However, I prefer the repo version since it comes with file explorer integration (and looks slightly better). To get file explorer integration with the AppImage, nautilus-extension-nextcloud needs to be installed, which then installs nextcloud-desktop anyway. So the client ends up being installed twice on the same system and the repo version needs to be removed from startup applications. This all feels a little hacky.

Steps to reproduce

  1. install Nextcloud Desktop client on SUSE: sudo zypper install nextcloud-desktop
  2. launch client
  3. quit client
  4. add showExperimentalOptions=true to $HOME/.config/Nextcloud/nextcloud.cfg
  5. launch client
  6. add a regular sync connection, since there is no option to enable virtual file support in this window (it used to be there on Debian)
  7. in client settings, click on three dots next to the just created sync connection and click on Enable virtual file support
  8. client crashes
  9. after client relaunch, virtual file support is still not enabled

Expected behavior

Client should not crash and virtual file support should stay enabled.

Which files are affected by this bug

virtual files

Operating system

Linux

Which version of the operating system you are running.

OpenSUSE Tumbleweed

Package

Distro package manager

Nextcloud Server version

28.0.5

Nextcloud Desktop Client version

3.13.0

Is this bug present after an update or on a fresh install?

Fresh desktop client install

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

Are you using an external user-backend?

  • Default internal user-backend
  • LDAP/ Active Directory
  • SSO - SAML
  • Other

Nextcloud Server logs

No response

Additional info

No response

@claucambra
Copy link
Collaborator

Hi @woiwoiwoiwoi, we do not package the SUSE package -- we officially recommend using the AppImage. I would recommend you open an issue with the SUSE packagers

@woiwoiwoiwoi
Copy link
Author

woiwoiwoiwoi commented May 16, 2024

Hi @claucambra and thank you for responding. I am using the AppImage at the moment, so that's fine. But am I correct in understanding that file explorer integration does not come with the AppImage? Because that is my only real issue with the AppImage: that I have to still install nextcloud-desktop anyway (for file explorer integration) and then the application is installed twice AND the repo version needs to be manually removed from startup applications.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants