Description of problem: Time to update, plus our current version crash sometimes. We usually update this package at x.x.1 or x.x.2 release, plus if needed for security or interoperability with server updates. Currently we ship 3.13.4 It crashes sometimes when user remove a configured folder sync or server. Christian Barranco used to package regularly and kindly did 3.13.4 too. He tried to package 3.14 but reported: "moving to 3.14.x will need quite some works on MGA9 to update the Qt6 stack. Hopefully, I am not too far to get through for Cauldron." ( Bug 33458 comment 16 ) So should we open a bug for updating Qt6 on mga9? Or what to do about this?
Setting high because our 3.13.4 crashes sometimes.
Priority: Normal => High
Another issue our 3.13 have is it stop syncing after suspend-resume on some installations, like on my wife's laptop, (weird, no problem on my desktop) and that is presumably fixed in 3.14+. https://github.com/nextcloud/desktop/issues/6487#issuecomment-2354082666 3.13 seem no longer maintained upstreams last 3.14, 3.14.3 released three weeks ago. 3.15.0 two days ago. Maybe too fresh, being a .0 release. But a related(?) login fix https://github.com/nextcloud/desktop/pull/7455 is in 3.15.0 but not in 3.14.3. messy, as always... Anyway, to compile 3.14+ we need update of Qt6, Christian Barranco said. Will that come or must we abandon nextcloud-client on mga9? -And instead recommend Appimage or Flatpak? -- in that case file manager integration is not possible, I guess? cc Qt6 last packager daviddavid
URL: (none) => https://github.com/nextcloud/desktop/releases/CC: (none) => geiger.david68210
(In reply to Morgan Leijström from comment #0) > Christian Barranco > "I am not too far to get through for Cauldron." And I see from that time 3.14.2 in /cauldron/x86_64/media/core/release/
I have switched to official Nextcloud client 3.15.0 AppImage. Good: both problems are gone on two systems. (no crash when removing a sync, and syncs resumes after system suspend-resume) Prominent downsides: no integration in file browser, and only x86_64. I ponder writing a detailed instruction on switching in a wiki page. Very easy: 1. Close nextcloud client 2. Uninstall lib64ocsync0 and deps 3. Go to https://nextcloud.com/install/, Click "DOWNLOAD FOR DESKTOP" -> get "Linux Appimage" Move it where you want it to live. Make it executable, i.e execute chmod +x *.AppImage 4. Launch that file. (it finds and use earlier sync settings) For next session autostart works, if enabled in its settings. Works, incl system tray icon, dialogues... Advantage: Updated, both bugs that annoyed me are fixed. Downsides: There is no i686 implementation. (?) There is no file browser integration. No language translation. (at least not Swedish) You need to update it manually. (or by Appimage updater) If no one can step in and package this, we need to drop it for mga10. CC earlier testers for sharing information
CC: (none) => Joselp, brtians1, mageiaSeverity: normal => majorStatus comment: (none) => Keep updated or drop.
I have tried to find a 32 bit alternative to ours, but failed; no AppImage nor Flatpak, and using packages from another distro I think is not to recommend even if we find one updated... - Ideas welcome. Could this package be some joint effort together with a similar distro? Personally, for some devices I use serverless syncing by syncthing which support 32 bit and several other OS, and then one computer can sync that to nextcloud server. The upside of syncthing is it do not depend on server, works for more OS, is fast - especially locally - and can keep file revisions. Problem is no sync to standard cloud. Workaround: use one own device all other of your devices sync with, and that device syncs to a cloud service.
(In reply to Morgan Leijström from comment #4) > I have switched to official Nextcloud client 3.15.0 AppImage. > Good: both problems are gone on two systems. > (no crash when removing a sync, and syncs resumes after system > suspend-resume) > > Prominent downsides: no integration in file browser, and only x86_64. > > I ponder writing a detailed instruction on switching in a wiki page. > > Very easy: > 1. Close nextcloud client > 2. Uninstall lib64ocsync0 and deps > 3. Go to https://nextcloud.com/install/, > Click "DOWNLOAD FOR DESKTOP" -> get "Linux Appimage" > Move it where you want it to live. > Make it executable, i.e execute chmod +x *.AppImage > 4. Launch that file. > (it finds and use earlier sync settings) > For next session autostart works, if enabled in its settings. > > Works, incl system tray icon, dialogues... > > Advantage: Updated, both bugs that annoyed me are fixed. > Downsides: > There is no i686 implementation. (?) > There is no file browser integration. > No language translation. (at least not Swedish) > You need to update it manually. (or by Appimage updater) > > > If no one can step in and package this, we need to drop it for mga10. > > CC earlier testers for sharing information Morgan - I'd heard why we didn't go to 3.14 before was an issue with library conflicts. I gather this version is self-contained then. Is that correct?
IIUC for mga9, the Qt6 stack need be updated, but I doubt it will be. It seem to compile on mga10 but we still need a maintainer. Yes, this AppImage seem to be complete. I only performed the four steps I noted, and it just works :) (Except not available for my 32 bit systems...) Sidenote: please do not cite large chink when not needed, to keep bug shorter.
(In reply to Morgan Leijström from comment #7) > It seem to compile on mga10 It = nextcloud-client
Created a wiki page on the client, both for our packages and the AppImage: https://wiki.mageia.org/en/Nextcloud-client Linked to it at bottom of https://wiki.mageia.org/en/Mageia_9_Errata#Various_software --- NOTE: keep this bug open until decided for mga10 § The errata 9 entry can be removed if we push a current update - and then also update the Nextcloud-client wiki page. § For mga10 we need to either make sure we keep it updated (have a maintainer) or we should drop it, and note that in release notes.
Status comment: Keep updated or drop. => Keep updated or drop, see c#9Keywords: (none) => FOR_RELEASENOTES10, IN_ERRATA9
Any timelines yet for MGA10? Also, any plans to upgrade QT6 in 9?