Nextcloud-Client: How to get latest 4.x release into the repos?

Ask Fedora
, , ,
41

This seems to work! Still the build could just be added to the F42 test repo

42

You have to test and give thumbs up. Otherwise it will not enter into stable. That is how testing works.

1 Like
43

@ankursinha, thanks. Shall try it, when I ascertain how to:

44

It is very helpful using in a pre release. There is testing still active.
It looks like this:

Login successful!
Getting list of installed packages...
Waiting for oraculum instance to return list of packages in updates-testing...
found 338 testing updates
===================================================================================================================================================================================================================================
     curl-8.18.0-5.fc44
===================================================================================================================================================================================================================================
  Update ID: FEDORA-2026-f3e5776cdf
    Release: Fedora 44
     Status: testing
       Type: critpath unspecified
      Karma: 2/3
       Bugs: https://bugzilla.redhat.com/2438170 - OBJ_find_sigid_algs() returns NID_undef for ML-DSA certificate
 Test Cases: https://fedoraproject.org/wiki/QA%3ATestcase_curl
      Notes: -  Fix `Could not find digest algorithm UNDEF (NID 0)`
  Submitter: jamacku
  Submitted: 2026-03-30 12:26:22
   Comments: geraldosimiao - 2026-03-31 16:03:07 (karma 1)
             filiperosset - 2026-04-01 18:47:01 (karma 1)
               no regressions noted

  https://bodhi.fedoraproject.org/updates/FEDORA-2026-f3e5776cdf

 inst. RPMS: curl-8.18.0-5.fc44.x86_64
               A utility for getting files from remote servers (FTP, HTTP, and others) (Installed 0 days ago)
             libcurl-8.18.0-5.fc44.x86_64
               A library for getting files from web servers (Installed 0 days ago)
Comment? -1/0/1 -> karma, 'i' -> ignore, other -> skip> 

     distribution-gpg-keys-1.119-1.fc44
===================================================================================================================================================================================================================================
  Update ID: FEDORA-2026-57a496c82a
    Release: Fedora 44
     Status: testing
       Type: critpath enhancement
      Karma: 2/2
    Request: stable
      Notes: - update copr keys
           :  - add: ultramarine repository keys
           : - add: terra repository keys
           : - update Google key block
  Submitter: msuchy
  Submitted: 2026-03-29 10:27:37
   Comments: geraldosimiao - 2026-03-31 16:05:38 (karma 1)
             filiperosset - 2026-04-01 18:47:03 (karma 1)
               no regressions noted

  https://bodhi.fedoraproject.org/updates/FEDORA-2026-57a496c82a

 inst. RPMS: distribution-gpg-keys-1.119-1.fc44.noarch
               GPG keys of various Linux distributions (Installed 0 days ago)
Comment? -1/0/1 -> karma, 'i' -> ignore, other -> skip> 0
Comment> aborted
45

@ilikelinux, so does it not activate for me, because it believes that I’ve no unstable packages installed?

46

Yes, no packages from updates-testing installed:

sudo dnf repolist 
repo id                                                repo name                                                           

fedora                                                 Fedora 44 - x86_64                                                  
fedora-cisco-openh264                                  Fedora 44 openh264 (From Cisco) - x86_64                            
updates                                                Fedora 44 - x86_64 - Updates                                        
updates-testing                                        Fedora 44 - x86_64 - Test Updates
1 Like
47

Is there somewhere where I can give thumbs up for f42? I only see it for f43 and f44

48

It looks like the older version is still in testing for F42?!

I guess the priority for F42 is low.

49

For me it looks like there is no version in testing currently:
https://bodhi.fedoraproject.org/updates/?packages=nextcloud-client
That’s what I’m asking: Can someone push the 4.x version to f42 testing?

50

please read the details:

This update can be pushed to stable now if the maintainer wishes  a week ago

User Icon nonamedotc commented a week ago

I intend to leave it this in testing for at least two weeks

sorry that’s for 43

51

i can share my experience from the last weeks with f43 and nextcloud-client 3.17 and 4.07 and current AppImage 33.0.2 from nextcloud.com .

my environment:

Fedora 43 with KDE6 on btrfs

without VFS i had no issues with any of the mentioned versions.

i focused my testing on “use with VFS”

Prodecure:

  • delete ~/Nextcloud/
  • delete ~/.config/Nextcloud/
  • install client
  • connect to nextcloud
  • close client
  • modify .config/Nextcloud/nextcloud.cfg
[General]
showExperimentalOptions=true
isVfsEnabled=true
  • start client
  • add a sync folder without subfolders (VFS does not show when adding sync folder)
  • close client
  • modify .config/Nextcloud/nextcloud.cfg
[Accounts]
0\FoldersWithPlaceholders\1\virtualFilesMode=suffix
  • enable VFS using three dots on the sync folder in the settings dialog
  • here it usally crashed
  • if not crashed: wait for full sync

Problems with RPM 4.0.7

after creating the syncfolder I enabled VFS (using the three dots on the sync folder in the settings dialog)
result: instant appcrash
cause: nullptr when creating the “do you really want to enable this experimental feature”
i asked Gemini and Claude for their opinion and they agreed: parameter error against the QT6 framework - possible cause: use of mismatching QT headers when compiling nextcloud

2026-04-06 22:50:18:751 [ warning qt.core.qobject.connect unknown:0 ]: QObject::connect(QDialog, OCC::AccountSettings): invalid nullptr parameter - segmentation fault

Problems with Appimage and rpm for 3.17

could not get VFS to show in the “three dots menu”
but i did not invest a lot of time into that

i remember that i had the same “appcrash” but when i had time to dig deeper the 4.0.7 was already in testing repositories - so i continued there

AppImage 33.0.2

this is what i use now.
works fine

manual steps needed with AppImage (similar things needed for flatpack)

tell KDE that any file ending in .nextcloud should be “opened” by your AppImage.

  1. Open System Settings.
  2. Go to Applications → File Associations.
  3. Click + Add (bottom left).
    • Group: application
    • Type name: nextcloud-virtual-file
  4. In the Filename Patterns section, click Add and type: *.nextcloud
  5. In the Application Preference Order section, click Add:
    • Browse to the location of your Nextcloud AppImage.
    • Select it and click OK.
  6. Click Apply.

add File Parameter to AppImage - for auto-download after double click on a *.nextcloud file

In the same File Associations menu:

  1. Select your AppImage in the list.
  2. Click Edit.
  3. In the Application tab, the “Command” field should look like this: /path/to/Nextcloud.AppImage
  4. add %f to “Parameters”

Procedure to update the AppImage

  1. download new appimage
  2. rename the old one
  3. modify the program path in KDE file associations

hope this helps someone :slight_smile: