Client 4 provides lots of fixes and improvements since 3-series we have As usual we dont package .0 version (which is not even available now) and wait for the bugfix release which is released since 18 days, seem OK. https://github.com/nextcloud/desktop/releases Lots of fixes and new checks. Most important feature IMO is "This release introduces a bulk upload feature which lets the desktop client upload large numbers of small files much faster. The difference can be huge – 10x or more!"
neoclust is still the maintainer according to madb CC christian as he helped package previous versions
CC: (none) => chb0Assignee: bugsquad => mageiaSummary: nextcloud-client update to 4.1.1 => nextcloud-client update to 3.4.1
Hi I was actually wondering last week what to do. 3.3 series is no more supported. I guess we should go for the 3.4 one then. If you give your agreement to switch version, I can build it right away. Just let me know.
cauldron is now with 3.4.1 version. I think we need to update mga8 to 3.4.1 too
Hi The MGA8 package for 3.4.1 is now ready and under testing on my machine. Another option would be to wait for 3.4.2 which should not be far away, based on experience. 3.4.0 had a hectic start. Might not be a bad idea to wait for another bug fix release. Otherwise, Nicolas, I can place the src.rpm at the usual location for your review. Let me know what your choice is.
Good. Yes I am happy we have as principle for NC client not jump on .0 versions, as I see 3.4.0 screwed up filedates and thus syncing in some cases. That is probably the reason 3.4.0 got removed and 3.4.1 quickly out, it even have some antidotes baked in to help recover from that 3.4.0 screw-up.
Trying to understand the milestones status https://github.com/nextcloud/desktop/milestones No release dates - i guess it mean release when "ready", IMO that is good. Both 3.4.1 and 3.5.0 are "100% ready" - only meaning all bugs set to that milestone are fixed. 3.5.0 share some fixed issues with 3.4.1 - i guess it was cloned before 3.4.1. Interesting: *No* issue is set for 3.4.2 milestone yet!? Combining no issue is set to 3.4.2 and that 3.4.1 have been out 18 days, One would guess there is no 3.4.2 in a realtively long while. BUT there are however some bugs that seem they _should_ fix rather quickly. https://github.com/nextcloud/desktop/issues I read several users are going back to 3.3.6 (both after trying 3.4.0 and 3.4.1, but most are on late NC server 23, and most clients not on Linux, but that may be beacause most testers use late NS servers, and MSWindows clients) So yes I too now land in that we should wait for 3.4.2
Hi I'll keep testing 3.4.1 on my machine. First thing: language pack is messed up or there is something new to consider during the packaging. I confirm I think it is wise to wait for 3.4.2
Summary: nextcloud-client update to 3.4.1 => nextcloud-client update to 3.4.2, when releasedStatus comment: (none) => We think 3.4.1 have too severe bugs, some users went back to 3.3.6
Hi 3.4.2 is out. I will package and test it tomorrow.
Hi Nicolas the src.rpm is ready for your review at the usual location. I have started to test it and I have not encountered any issue. Advisory proposal ================= Updated nextcloud-client packages to leave the end of life 3.3. branch Description Update to version 3.4.2 to move to the new supported branch. 3.4.2 is assessed as enough matured to do so. It includes various bug fixes; more details in the references. It comes with some new improvements and features as well: * Main dialog will be a regular window if tray icons are not available on the system. * Network traffic performance improvements. * Improvements to the sync engine. References https://github.com/nextcloud/desktop/releases/tag/v3.4.2 https://github.com/nextcloud/desktop/releases/tag/v3.4.1 https://github.com/nextcloud/desktop/releases/tag/v3.4.0-rc2 https://github.com/nextcloud/desktop/releases/tag/v3.4.0-rc1 https://bugs.mageia.org/show_bug.cgi?id=29855 SRPMS 8/core nextcloud-client-3.4.2-1.mga8 PROVIDED PACKAGES: lib64nextcloudsync0-3.4.2-1.mga8 lib64ocsync0-3.4.2-1.mga8 nextcloud-client-3.4.2-1.mga8 Optional depending on Desktop Environment: nextcloud-client-caja-3.4.2-1.mga8 nextcloud-client-dolphin-3.4.2-1.mga8 nextcloud-client-nautilus-3.4.2-1.mga8 nextcloud-client-nemo-3.4.2-1.mga8
available for QA :-)
Assignee: mageia => qa-bugs
Packages for QA =============== x86_64: lib64nextcloudsync0-3.4.2-1.mga8.x86_64.rpm lib64ocsync0-3.4.2-1.mga8.x86_64.rpm nextcloud-client-3.4.2-1.mga8.x86_64.rpm nextcloud-client-caja-3.4.2-1.mga8.x86_64.rpm nextcloud-client-dolphin-3.4.2-1.mga8.x86_64.rpm nextcloud-client-nautilus-3.4.2-1.mga8.x86_64.rpm nextcloud-client-nemo-3.4.2-1.mga8.x86_64.rpm i586: lib64nextcloudsync0-3.4.2-1.mga8.i586.rpm lib64ocsync0-3.4.2-1.mga8.i586.rpm nextcloud-client-3.4.2-1.mga8.i586.rpm nextcloud-client-caja-3.4.2-1.mga8.i586.rpm nextcloud-client-dolphin-3.4.2-1.mga8.i586.rpm nextcloud-client-nautilus-3.4.2-1.mga8.i586.rpm nextcloud-client-nemo-3.4.2-1.mga8.i586.rpm aarch64: lib64nextcloudsync0-3.4.2-1.mga8.aarch64.rpm lib64ocsync0-3.4.2-1.mga8.aarch64.rpm nextcloud-client-3.4.2-1.mga8.aarch64.rpm nextcloud-client-caja-3.4.2-1.mga8.aarch64.rpm nextcloud-client-dolphin-3.4.2-1.mga8.aarch64.rpm nextcloud-client-nautilus-3.4.2-1.mga8.aarch64.rpm nextcloud-client-nemo-3.4.2-1.mga8.aarch64.rpm armv7hl: lib64nextcloudsync0-3.4.2-1.mga8.armv7hl.rpm lib64ocsync0-3.4.2-1.mga8.armv7hl.rpm nextcloud-client-3.4.2-1.mga8.armv7hl.rpm nextcloud-client-caja-3.4.2-1.mga8.armv7hl.rpm nextcloud-client-dolphin-3.4.2-1.mga8.armv7hl.rpm nextcloud-client-nautilus-3.4.2-1.mga8.armv7hl.rpm nextcloud-client-nemo-3.4.2-1.mga8.armv7hl.rpm
Thanks __OK Testing on x86_64, Dolphin, seem to work perfectly. § Updated two clients § System tray, main dialogue, settings window § Resumes syncs, Conveys new changes both ways § Dolphin integration § New synk with same server. § nextcloud --logwindow : brings up dialogue to activate massive logging to files. I enabled it, closed dialogue. Quirk: need restart to really log. __Segfault exiting! Close nextcloud-client by tray icon popup menu -> segfault, memory dump. /!\ My worries here is what if it do not reliably save synchronisation state etc in database before crashing? I searched https://github.com/nextcloud/desktop/issues but could not find a bug entered for crash at shutting down. Can others here replicate? __To be verified by someone § fresh install § connecting to new server § Integration with caja, nautilus, nemo We do not use to check aarch64 or armv7hl
Summary: nextcloud-client update to 3.4.2, when released => nextcloud-client update to 3.4.2Status comment: We think 3.4.1 have too severe bugs, some users went back to 3.3.6 => Segfault shutting down. Is sync status reliably saved?
Hi Plasma x86_64 *Update from 3.3.6: OK *Dolphin integration: OK *Crash reported by Morgan while closing NC-client via the systray: Reproduced with journalctl -f in parallel. No other symptom. I will file a bug. @Morgan: have you had more symptoms during this crash, rather than a message in the journal?
No other symptom.
hi guys do you want me to test this or wait for a fix?
CC: (none) => brtians1
I forgot to report localisation is OK at least for Swedish @ christian, yes please report upstream and post here the bug link I let christian decide if we should do more testing or wait for fix. Myself leave it in operation as is for now. IMO, if the crash do not risk the data base or files it is OK for now. To test are the caja, nautilus, nemo plugins, a 32 bit install, a fresh install (not update), and connecting to a not before configured server.
Hi I did more testing yesterday. VM x86 Cinnamon *fresh install *connection and sync: ok *right click on systray icon to close down: no error! *reboot *auto restart: ok *right click on systray icon to close down: no error! VM x86 Gnome *fresh install *connection and sync: ok *right click on systray icon to close down: no error! *reboot *auto restart: ok *right click on systray icon to close down: no error! VM x86 Plasma *fresh install *connection and sync: ok *right click on systray icon to close down: no error! *reboot *auto restart: ok *right click on systray icon to close down: no error! VM x86 Plasma *fresh install 3.3.6 *connection and sync: ok *right click on systray icon to close down: no error. *reboot *auto restart: ok *right click on systray icon to close down: no error. *upgrade 3.4.2 *connection and sync: ok *right click on systray icon to close down: no error. *reboot *auto restart: ok *right click on systray icon to close down: no error. On my machine, I confirm the consistent behavior leading to crash after shutdown by clicking on the systray applet. I will test an uninstall and remove of configuration folder, to confirm whether I keep getting the crash. Would it be possible to get more testing including right click on applet systray to check the crash (journalctl -f in a console)? I am not sure where the bug should be filed. Beside this, it works flawlessly.
Good testing. Wonder what is the culprit then... Reading journals of segfaulting shutdown: __In journal: feb 01 12:43:39 svarten.tribun kernel: nextcloud[367040]: segfault at ffffffffffffffff ip 00007f68ad6eca6d sp 00007ffc5feb5ff8 error 5 in libgobject-2.0.so.0.6600.8[7f68ad6c7000+2e000] feb 01 12:43:39 svarten.tribun kernel: Code: 02 48 8d 05 75 3c 02 00 48 8b 34 d8 eb b6 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 85 ff 74 4b 48 8b 07 48 85 c0 74 43 <48> 8b 00 48 3d fc 03 00 00 76 18 48 83 e0 fc 0f b6 50 14 45 31 c0 __Last lines in last nextcloud clientlogfile: OCC::SocketListener::sendMessage ]: Sending SocketAPI message --> "UNREGISTER_PATH:/home/morgan/Synkning/GamlaDropbox" to QLocalSocket(0x562322deae20) 2022-02-01 12:43:39:431 [ debug nextcloud.gui.socketapi /home/iurt/rpmbuild/BUILD/desktop-3.4.2/src/gui/socketapi/socketapi.cpp:205 ] [ OCC::SocketListener::sendMessage ]: Sending SocketAPI message --> "UNREGISTER_PATH:/home/morgan/Synkning/GamlaDropbox" to QLocalSocket(0x562322e78dd0) 2022-02-01 12:43:39:431 [ info nextcloud.sync.database /home/iurt/rpmbuild/BUILD/desktop-3.4.2/src/common/syncjournaldb.cpp:631 ]: Closing DB "/home/morgan/Synkning/GamlaDropbox/.sync_dc3bf265c34a.db" 2022-02-01 12:43:39:431 [ debug nextcloud.sync.database /home/iurt/rpmbuild/BUILD/desktop-3.4.2/src/common/syncjournaldb.cpp:246 ] [ OCC::SyncJournalDb::commitTransaction ]: No database Transaction to commit To me it seems to close database. I would have loved to see a clear message it is finished shutting down. What do last lines in logfile say when it shuts down cleanly?
Hi When it closes fine with 3.4.2, Plasma: __journal systemd[1533]: app-\x2fusr\x2fbin\x2fnextcloud-e59248c76f6a4a44b53d23d49facb630.scope: Succeeded. __log 2022-02-03 10:57:02:892 [ debug nextcloud.gui.account.manager /home/iurt/rpmbuild/BUILD/desktop-3.4.2/src/gui/accountmanager.cpp:198 ] [ OCC::AccountManager::saveAccount ]: Saving account "https://mycloud" 2022-02-03 10:57:02:895 [ info nextcloud.gui.account.manager /home/iurt/rpmbuild/BUILD/desktop-3.4.2/src/gui/accountmanager.cpp:246 ]: Saving 0 unknown certs. 2022-02-03 10:57:02:895 [ info nextcloud.gui.account.manager /home/iurt/rpmbuild/BUILD/desktop-3.4.2/src/gui/accountmanager.cpp:260 ]: Saving cookies. "/home/toto/.config/Nextcloud/cookies0.db" 2022-02-03 10:57:02:895 [ debug nextcloud.sync.cookiejar /home/iurt/rpmbuild/BUILD/desktop-3.4.2/src/libsync/cookiejar.cpp:107 ] [ OCC::CookieJar::save ]: "/home/toto/.config/Nextcloud/cookies0.db" 2022-02-03 10:57:02:896 [ debug nextcloud.gui.account.manager /home/iurt/rpmbuild/BUILD/desktop-3.4.2/src/gui/accountmanager.cpp:205 ] [ OCC::AccountManager::saveAccount ]: Saved account settings, status: QSettings::NoError 2022-02-03 10:57:02:896 [ info nextcloud.gui.account.manager /home/iurt/rpmbuild/BUILD/desktop-3.4.2/src/gui/accountmanager.cpp:246 ]: Saving 0 unknown certs. 2022-02-03 10:57:02:896 [ info nextcloud.gui.account.manager /home/iurt/rpmbuild/BUILD/desktop-3.4.2/src/gui/accountmanager.cpp:260 ]: Saving cookies. "/home/toto/.config/Nextcloud/cookies0.db" 2022-02-03 10:57:02:896 [ debug nextcloud.sync.cookiejar /home/iurt/rpmbuild/BUILD/desktop-3.4.2/src/libsync/cookiejar.cpp:107 ] [ OCC::CookieJar::save ]: "/home/toto/.config/Nextcloud/cookies0.db" 2022-02-03 10:57:02:897 [ info nextcloud.gui.account.manager /home/iurt/rpmbuild/BUILD/desktop-3.4.2/src/gui/accountmanager.cpp:193 ]: Saved all account settings, status: QSettings::NoError 2022-02-03 10:57:02:897 [ debug nextcloud.gui.socketapi /home/iurt/rpmbuild/BUILD/desktop-3.4.2/src/gui/socketapi/socketapi.cpp:205 ] [ OCC::SocketListener::sendMessage ]: Sending SocketAPI message --> "UNREGISTER_PATH:/home/toto/Musique" to QLocalSocket(0x563deefc8e30) 2022-02-03 10:57:02:898 [ info nextcloud.sync.database /home/iurt/rpmbuild/BUILD/desktop-3.4.2/src/common/syncjournaldb.cpp:631 ]: Closing DB "/home/toto/Musique/.sync_c3f2e524e2be.db" 2022-02-03 10:57:02:911 [ debug nextcloud.gui.socketapi /home/iurt/rpmbuild/BUILD/desktop-3.4.2/src/gui/socketapi/socketapi.cpp:296 ] [ OCC::SocketApi::~SocketApi ]: dtor 2022-02-03 10:57:02:911 [ info nextcloud.gui.socketapi /home/iurt/rpmbuild/BUILD/desktop-3.4.2/src/gui/socketapi/socketapi.cpp:331 ]: Lost connection QLocalSocket(0x563deefc8e30) I will file a bug report against nextcloud-client
Breaking news... While writing the bug report, I downgraded to 3.3.6 on my machine to post the log of the expected behavior, using a case on a production machine. Guess what... I got exactly the same type of segfault in the terminal, with the same type of "No database Transaction to commit" in the log file. This issue is not specific to 3.4.2 then. My view is then to keep testing this release and to validate it; if nothing is highlighted in normal use, of course. I will still write a bug report against nextcloud-client, but I will not make it specific to 3.4.2
Good finding. Post back here a link to the the bug __OK, so left to test are: § Integration with caja, nautilus, nemo § 32 bit
Hi Integrations with nautilus and nemo have been tested by me on VM x86_64, fresh installation; comment #17 Is it an update from 3.3.6 you are after?
I tested update from 3.3.6 on two 64 bit plasma systems OK. So only caja left (one arch i think will be enough) And 32 bit install or update (i think either will do, and that we do not need to check integration there, if it works for 64 bit, so...)
Here is the link to the bug report: https://github.com/nextcloud/desktop/issues/4248
MG8-64, Gnome, Nautilus The following 4 packages are going to be installed: - lib64nextcloudsync0-3.4.2-1.mga8.x86_64 - lib64ocsync0-3.4.2-1.mga8.x86_64 - nextcloud-client-3.4.2-1.mga8.x86_64 - nextcloud-client-nautilus-3.4.2-1.mga8.x86_64 --- upgrade performed some large updates and synching is working as expected. works on gnome/nautilus
(In reply to Brian Rockwell from comment #25) > MG8-64, Gnome, Nautilus > > The following 4 packages are going to be installed: > > - lib64nextcloudsync0-3.4.2-1.mga8.x86_64 > - lib64ocsync0-3.4.2-1.mga8.x86_64 > - nextcloud-client-3.4.2-1.mga8.x86_64 > - nextcloud-client-nautilus-3.4.2-1.mga8.x86_64 > > > --- upgrade > > performed some large updates and synching is working as expected. > > works on gnome/nautilus Thanks Brian. Do you get the segfault message if you quit through the systray applet?
MGA8-64, Mate The following 26 packages are going to be installed: - lib64caja-gir2.0-1.24.1-1.1.mga8.x86_64 - lib64cloudproviders0-0.3.1-1.mga8.x86_64 - lib64event7-2.1.12-1.mga8.x86_64 - lib64minizip1-1.2.11-9.mga8.x86_64 - lib64nextcloudsync0-3.4.2-1.mga8.x86_64 - lib64ocsync0-3.4.2-1.mga8.x86_64 - lib64qt5keychain1-0.11.1-2.mga8.x86_64 - lib64qt5pdf5-5.15.6-1.mga8.x86_64 - lib64qt5positioning5-5.15.2-1.mga8.x86_64 - lib64qt5quickcontrols2_5-5.15.2-1.mga8.x86_64 - lib64qt5quicktemplates2_5-5.15.2-1.mga8.x86_64 - lib64qt5quickwidgets5-5.15.2-1.mga8.x86_64 - lib64qt5svg5-5.15.2-1.1.mga8.x86_64 - lib64qt5webchannel5-5.15.2-1.mga8.x86_64 - lib64qt5webengine5-5.15.6-1.mga8.x86_64 - lib64qt5webenginecore5-5.15.6-1.mga8.x86_64 - lib64qt5webenginewidgets5-5.15.6-1.mga8.x86_64 - lib64qt5websockets5-5.15.2-1.mga8.x86_64 - lib64re2_9-20201101-2.mga8.x86_64 - lib64snappy1-1.1.8-2.mga8.x86_64 - nextcloud-client-3.4.2-1.mga8.x86_64 - nextcloud-client-caja-3.4.2-1.mga8.x86_64 - python3-caja-1.24.0-2.mga8.x86_64 - qtquickcontrols25-5.15.2-1.mga8.x86_64 - qtsvg5-5.15.2-1.1.mga8.x86_64 - qtwebengine5-5.15.6-1.mga8.x86_64 -- Started nextcloud-client and attached to a local test server - synched 566 files - no issues - closed nextclound-client via <right-click> <exit> - nothing in journal logs -- rebooted - caja reflecting sync state in folders This working for mate
Whiteboard: (none) => MGA8-64-OK
(In reply to Morgan Leijström from comment #23) > > And 32 bit install or update (i think either will do, and that we do not > need to check integration there, if it works for 64 bit, so...) Waiting for a 32-bit OK before validating, then.
CC: (none) => andrewsfarm
The following 25 packages are going to be installed: - libcaja-gir2.0-1.24.1-1.1.mga8.i586 - libcloudproviders0-0.3.1-1.mga8.i586 - libminizip1-1.2.11-9.mga8.i586 - libnextcloudsync0-3.4.2-1.mga8.i586 - libocsync0-3.4.2-1.mga8.i586 - libqt5keychain1-0.11.1-2.mga8.i586 - libqt5pdf5-5.15.8-1.mga8.i586 - libqt5positioning5-5.15.2-1.mga8.i586 - libqt5quickcontrols2_5-5.15.2-1.mga8.i586 - libqt5quicktemplates2_5-5.15.2-1.mga8.i586 - libqt5quickwidgets5-5.15.2-1.mga8.i586 - libqt5svg5-5.15.2-1.1.mga8.i586 - libqt5webchannel5-5.15.2-1.mga8.i586 - libqt5webengine5-5.15.8-1.mga8.i586 - libqt5webenginecore5-5.15.8-1.mga8.i586 - libqt5webenginewidgets5-5.15.8-1.mga8.i586 - libqt5websockets5-5.15.2-1.mga8.i586 - libre2_9-20201101-2.mga8.i586 - libsnappy1-1.1.8-2.mga8.i586 - nextcloud-client-3.4.2-1.mga8.i586 - nextcloud-client-caja-3.4.2-1.mga8.i586 - python3-caja-1.24.0-2.mga8.i586 - qtquickcontrols25-5.15.2-1.mga8.i586 - qtsvg5-5.15.2-1.1.mga8.i586 - qtwebengine5-5.15.8-1.mga8.i586 -- rebooted system synch'd fine caja reflecting sync status properly no shutdown startup issues to speak of
Whiteboard: MGA8-64-OK => MGA8-64-OK MGA8-32-OK
Thanks for all your efforts, guys. Validating. Suggested advisory in Comment 9.
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugs
Keywords: (none) => advisoryCC: (none) => davidwhodgins
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2022-0023.html
Status: NEW => RESOLVEDResolution: (none) => FIXED