Description of problem: Time to update. 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 have: 3.12.5 Upstream is at 3.12.7, but 3.13 is already at .2 so we deem it tested enough and that 3.13.2 or later is preferred over 3.12 series to longer avoid need for another update. Christian Barranco used to package regularly but have now left.
CC testers who use to test this package
CC: (none) => brtians1, mageia
Thank You. Hmm - who is packaging this now then?
I looked in core testing but am not seeing nothing new for nextcloud-client. The mirror I'm using is reported are being up-to-date. What are the packages to test?
Just CC you so you are getting updated whenever it is packaged. New packager may not ping you and I may forget or be away. Packager should the assign it to QA for testing, then it is yours. Hoping someone can take the ball.
The version 3.12.5 in Cauldron is only 2 months old! Upstream has already advanced to 3.12.7 and now 3.13.2, so it is moving rapidly. Changing assignment to squidf who routinely maintains this package.
Assignee: pkg-bugs => chb0
Yes it is moving rapidly but we do not update every version. As said, Christian is not working here anymore :( https://ml.mageia.org/l/msg/dev/2024-06/OVnnBXxrUEe0hCdvN7vidQ
Assignee: chb0 => pkg-bugs
Sorry, was unaware. Gloom...
Now we can skip 3.13.x 3.14.1 released three weeks ago. 100+ fixes/improvements since our version. We should keep this updated for best operation with especially newer server releases, and also due to security. We are getting behind, thus upping priority.
Priority: Normal => High
I tried to find a compatibility chart client/server but there is none. However, admin of a nextcloud server can set it to refuse old clients [1] and ours are getting old (in nextcloud universe) so our users risk getting locked out. Several places say it is recommended to always use latest client. But I think we can generally keep skipping some .x versions, and especially .0 like before. I also fond nothing against skipping a major version of the client. [1] https://help.nextcloud.com/t/which-nextcloud-desktop-client-version-is-working-with-which-server-version-server-version-newer-than-client-version/198994/8
How hard is this one to package? If not a huge learning curve maybe I can take ownership. Anyone on packaging team who good give me guidance on this?
Christian, if you still read this mail, maybe you as former packager of this application can help Brian to continue in your footsteps?
CC: (none) => chb0
(In reply to Brian Rockwell from comment #10) > How hard is this one to package? If not a huge learning curve maybe I can > take ownership. > > Anyone on packaging team who good give me guidance on this? This package should be rather straightforward. Download the source tarball and change the version, as a start. If issues, post here. That being said, neoclust used to be the official package, and might still be so.
Thank you for chiming in, Christian :-)
(In reply to christian barranco from comment #12) > (In reply to Brian Rockwell from comment #10) > > How hard is this one to package? If not a huge learning curve maybe I can > > take ownership. > > > > Anyone on packaging team who good give me guidance on this? > > This package should be rather straightforward. > Download the source tarball and change the version, as a start. > If issues, post here. > That being said, neoclust used to be the official package, and might still > be so. I have to take that back. With the arrival of qt6, there is much more work for this update. I take it. However, I had proposed change of way of working to overcome the packager uniqueness, but nobody had really care. It is one the reason why I stopped my involvement.
Warm tank you for stepping in Christian. I need this app. For your proposal, please add to https://wiki.mageia.org/en/Brainstorming_about_how_to_get_more_active_contributors
So, status: 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. I decided then to update to 3.13.4 instead. It is ready for testing by QA. ADVISORY NOTICE PROPOSAL ======================== Updated nextcloud-client to 3.13.4 branch Description Refer to upstream release notes References https://bugs.mageia.org/show_bug.cgi?id=33458 https://github.com/nextcloud/desktop/releases/tag/v3.12.6 https://github.com/nextcloud/desktop/releases/tag/v3.12.7 https://github.com/nextcloud/desktop/releases/tag/v3.13.0 https://github.com/nextcloud/desktop/releases/tag/v3.13.1 https://github.com/nextcloud/desktop/releases/tag/v3.13.2 https://github.com/nextcloud/desktop/releases/tag/v3.13.3 https://github.com/nextcloud/desktop/releases/tag/v3.13.4 SRPMS 9/core nextcloud-client-3.13.4-1.mga9.src.rpm PACKAGES FOR QA TESTING ======================= x86_64: lib64nextcloudsync0-3.13.4-1.mga9.x86_64.rpm lib64ocsync0-3.13.4-1.mga9.x86_64.rpm nextcloud-client-3.13.4-1.mga9.x86_64.rpm nextcloud-client-caja-3.13.4-1.mga9.x86_64.rpm nextcloud-client-dolphin-3.13.4-1.mga9.x86_64.rpm nextcloud-client-nautilus-3.13.4-1.mga9.x86_64.rpm nextcloud-client-nemo-3.13.4-1.mga9.x86_64.rpm i586: lib64nextcloudsync0-3.13.4-1.mga9.i586.rpm lib64ocsync0-3.13.4-1.mga9.i586.rpm nextcloud-client-3.13.4-1.mga9.i586.rpm nextcloud-client-caja-3.13.4-1.mga9.i586.rpm nextcloud-client-dolphin-3.13.4-1.mga9.i586.rpm nextcloud-client-nautilus-3.13.4-1.mga9.i586.rpm nextcloud-client-nemo-3.13.4-1.mga9.i586.rpm
Summary: nextcloud-client update request => nextcloud-client update to 3.13.4Assignee: chb0 => qa-bugs
Good decision. I am on testing it... soon. Both my servers (Murena (account) and Librecloud (hosted)) are down at the moment... Sigh. Now in the works of getting one at Hetzner. Do we have a bug pushing Qt6 update to mga9?
Keywords: (none) => advisory
Installed and tested without issues. Tested: - connect to two nextcloud servers; - directory sync; - open nextcloud pages in browser; - dolphin integration; - set status. All OK. No issues. System: Mageia 9, x86_64, Plasma DE, LXQt DE, AMD Ryzen 5 5600G with Radeon Graphics using amdgpu driver. $ uname -a Linux jupiter 6.6.52-desktop-1.mga9 #1 SMP PREEMPT_DYNAMIC Thu Sep 19 20:27:15 UTC 2024 x86_64 GNU/Linux $ rpm -qa | grep '3.13.4-1' lib64ocsync0-3.13.4-1.mga9 lib64nextcloudsync0-3.13.4-1.mga9 nextcloud-client-3.13.4-1.mga9 nextcloud-client-dolphin-3.13.4-1.mga9
Why am I not that lucky :( Plasma, 64 bit, my workstation. Both servers it synced with have gone offline. Updated to - lib64nextcloudsync0-3.13.4-1.mga9.x86_64 - lib64ocsync0-3.13.4-1.mga9.x86_64 - nextcloud-client-3.13.4-1.mga9.x86_64 - nextcloud-client-dolphin-3.13.4-1.mga9.x86_64 - nextcloud-client-nemo-3.13.4-1.mga9.x86_64 Rebooted Problem one main dialogue opens behind plasma panel. And mine was wide as I have big screen. Workaround: set panel narrow. I have had this problem before but was OK last week. I do not know why that comes and goes. Problem two I selected to remove one of the servers -> segfault! okt 22 13:37:47 svarten.tribun kernel: nextcloud[8671]: segfault at 0 ip 00007f145d7005e1 sp 00007ffcad77b510 error 4 in libgio-2.0.so.0.7600.3[7f145d65b000+10a000] likely on CPU 1 (core 1, socket 0) okt 22 13:37:47 svarten.tribun kernel: Code: e8 94 df f5 ff 58 5a 48 8b 05 6b e3 0f 00 48 83 c4 08 5b 5d c3 0f 1f 40 00 55 48 89 f5 53 48 89 fb 48 83 ec 08 e8 4f ff ff ff <48> 8b 3b 48 89 c6 e8 f4 aa f5 ff 48 89 ee 48 89 df 48 8b 40 10 48 okt 22 13:37:48 svarten.tribun systemd[1]: Started systemd-coredump@1-403264-0.service. okt 22 13:37:50 svarten.tribun systemd-coredump[403266]: [🡕] Process 8671 (nextcloud) of user 10702 dumped core. Stack trace of thread 8671: #0 0x00007f145d7005e1 g_action_map_lookup_action (libgio-2.0.so.0 + 0xdf5e1) #1 0x0000561ea3a29ab2 _ZN20CloudProviderWrapper21slotSyncPausedChangedEPN3OCC6FolderEb (nextcloud + 0x1e4ab2) #2 0x00007f145d2d3d12 _Z10doActivateILb0EEvP7QObjectiPPv (libQt5Core.so.5 + 0x2d3d12) etc... can grab more if wanted. Iĺl try removing configs.
Without doing anything else, I rebooted. nextcloud client showed up in system tray as usual. The server I clicked to remove was gone, OK. I added my new server, and cofigured sync shares - all OK. Weird: When opening the main dialogue (clicng the system tray icon), it opens on desktop 2 only, regardless of which is displayed. (I use four virtual Plasma desktops) And like in previous comment, the plasma tray covers it partly. Sync indication icons are OK on files in Dolphin. Working, useable. Why did i get the crash then? Maybe nextcloud client should optimally bes topped before upgrading, then started. I use to, when i am catious... but normal users should be able to just answr yes to that update popup... Can stopping/starting be scripted into the rpm? Or other ideas?
For the future: Is it possible to make this little sync thingy need less deps? (Syncthing (not packaged) is much smaller and does much more...) This is an up-to-date i586 LXDE installation: $ LC_ALL=C sudo urpmi --test --no-recommends nextcloud-client To satisfy dependencies, the following packages are going to be installed: (test only, installation will not be actually done) Package Version Release Arch (medium "Core Release") libass9 0.17.1 1.mga9 i586 libdc1394_25 2.2.6 3.mga9 i586 libqt5keychain1 0.13.2 1.mga9 i586 libqt5pdf5 5.15.10 8.mga9 i586 libqt5positioning5 5.15.7 2.mga9 i586 libqt5printsupport5 5.15.7 6.mga9 i586 libqt5quickcontrols2_5 5.15.7 1.mga9 i586 libqt5quicktemplates2_5 5.15.7 1.mga9 i586 libqt5quickwidgets5 5.15.7 1.mga9 i586 libqt5svg5 5.15.7 2.mga9 i586 libqt5webchannel5 5.15.7 1.mga9 i586 libqt5webengine5 5.15.10 8.mga9 i586 libqt5webenginecore5 5.15.10 8.mga9 i586 libqt5webenginewidgets5 5.15.10 8.mga9 i586 libqt5websockets5 5.15.7 1.mga9 i586 libqt5xml5 5.15.7 6.mga9 i586 libre2_9 20220601 1.mga9 i586 librtmp1 2.4 0.git2016010> i586 libsnappy1 1.1.9 3.mga9 i586 libsndio7 1.9.0 2.mga9 i586 libvidstab1.1 1.1.0 2.git2019021> i586 qtquickcontrols25 5.15.7 1.mga9 i586 qtsvg5 5.15.7 2.mga9 i586 qtwebengine5 5.15.10 8.mga9 i586 (medium "Core Updates") karchive 5.114.0 1.mga9 i586 libavfilter8 5.1.6 1.mga9 i586 libavformat59 5.1.6 1.mga9 i586 libkf5archive5 5.114.0 1.mga9 i586 libkf5guiaddons5 5.114.0 1.mga9 i586 libminizip1 1.2.13 1.2.mga9 i586 libopenmpt0 0.7.8 1.mga9 i586 libpostproc56 5.1.6 1.mga9 i586 libswscaler6 5.1.6 1.mga9 i586 libwebpmux3 1.3.0 2.1.mga9 i586 (medium "Core Updates Testing") libnextcloudsync0 3.13.4 1.mga9 i586 libocsync0 3.13.4 1.mga9 i586 nextcloud-client 3.13.4 1.mga9 i586 197MB of additional disk space will be used. 70MB of packages will be retrieved. Proceed with the installation of the 37 packages? (Y/n) n
mga9-i586 OK here (Bit the bullet anyway) Fresh install on updated LXDE, previous post. configured server the supposed way OK Set up syncing of a folder in my home, and a folder in my Win XP partition, found under /media/windows.... (This Mageia instance is mostly for safe file transfer for that old XP which I refuse internet connection; usage is configuring old automation equipment via old programs and serial port.)
I do not see the dialog positioning issues described in comment 19 but can confirm the crash/segfault when removing accounts. I had not tested it before so I do not know if it is a regression. See backtrace in attachment.
Created attachment 14714 [details] Backtrace of crash/segfault.
Did you leave it running during update, or did you restart it? I remember crashes when I tested long ago, and I *think* it was also then when changing account. I wonder what procedure it use when updating itself, on systems where it does. I should have grabbed the log... $ cat $HOME/.config/Nextcloud/nextcloud.cfg | grep LogDir logToTemporaryLogDir=true Which is /tmp/Nextcloud-logdir/ Do you still have yours? I guess it is cleared on reboot.
If you have time to experiment, you can launch the client telling it where to log. https://docs.nextcloud.com/desktop/latest/advancedusage.html
For the placement of main dialogue, on LXDE it is OK - in the middle of the screen is better than half hidden.
(In reply to Morgan Leijström from comment #25) > Did you leave it running during update, or did you restart it? It was running during the update but the crash did not happen in the same session as the update and the nextcloud app had been restarted after the update for testing. > I wonder what procedure it use when updating itself, on systems where it > does. > > I should have grabbed the log... > $ cat $HOME/.config/Nextcloud/nextcloud.cfg | grep LogDir > logToTemporaryLogDir=true > > Which is /tmp/Nextcloud-logdir/ > > Do you still have yours? No. /tmp in a tmpfs mount. Also, I don't have logToTemporaryLogDir=true in the config file.
On Plasma, for the placement of main dialogue, it seem to come when there are virtual desktop. And the workaround is to hoover the mouse over the nextcloud-client tray icon until it shows a status popup, then click, and it opens main dialogue in front of panel. (not always but most often) And it now works often to click without waiting until you shift to another desktop. Some bolt is loose. Not being on latest Plasma nor application, I refrain from reporting upstream.
MGA8-64, Plasma The following 4 packages are going to be installed: - lib64nextcloudsync0-3.13.4-1.mga9.x86_64 - lib64ocsync0-3.13.4-1.mga9.x86_64 - nextcloud-client-3.13.4-1.mga9.x86_64 - nextcloud-client-dolphin-3.13.4-1.mga9.x86_64 upgrade. -- rebooted both accounts are synchronizing
(In reply to Morgan Leijström from comment #29) > On Plasma, for the placement of main dialogue, it seem to come when there > are virtual desktop. I'm using Plasma DE and have 9 virtual desktops setup. I don't see the dialog placement issue.
MGA9-32, Mate The following 30 packages are going to be installed: - karchive-5.114.0-1.mga9.i586 - kguiaddons-5.114.0-1.mga9.i586 - libcaja-gir2.0-1.26.1-1.mga9.i586 - libkf5archive5-5.114.0-1.mga9.i586 - libkf5guiaddons5-5.114.0-1.mga9.i586 - libminizip1-1.2.13-1.2.mga9.i586 - libnextcloudsync0-3.13.4-1.mga9.i586 - libocsync0-3.13.4-1.mga9.i586 - libqt5keychain1-0.13.2-1.mga9.i586 - libqt5pdf5-5.15.10-8.mga9.i586 - libqt5positioning5-5.15.7-2.mga9.i586 - libqt5printsupport5-5.15.7-6.mga9.i586 - libqt5quickcontrols2_5-5.15.7-1.mga9.i586 - libqt5quicktemplates2_5-5.15.7-1.mga9.i586 - libqt5quickwidgets5-5.15.7-1.mga9.i586 - libqt5svg5-5.15.7-2.mga9.i586 - libqt5webchannel5-5.15.7-1.mga9.i586 - libqt5webengine5-5.15.10-8.mga9.i586 - libqt5webenginecore5-5.15.10-8.mga9.i586 - libqt5webenginewidgets5-5.15.10-8.mga9.i586 - libqt5websockets5-5.15.7-1.mga9.i586 - libqt5xml5-5.15.7-6.mga9.i586 - libre2_9-20220601-1.mga9.i586 - libsnappy1-1.1.9-3.mga9.i586 - nextcloud-client-3.13.4-1.mga9.i586 - nextcloud-client-caja-3.13.4-1.mga9.i586 - python3-caja-1.26.0-3.mga9.i586 - qtquickcontrols25-5.15.7-1.mga9.i586 - qtsvg5-5.15.7-2.mga9.i586 - qtwebengine5-5.15.10-8.mga9.i586 187MB of additional disk space will be used. 66MB of packages will be retrieved. Is it ok to continue? --nextcloud new build - connected to account and performed a full sync - worked as expected - rebooted and confirmed caja is reflecting sync status properly - dashboard and calendar links are working working for me.
Created attachment 14715 [details] Backtrace of crash when pausing a sync Segfault again - this time clearly not because of upgrade procedure. Kept using it on on my workstation, synced down a couple gigabytes, OK. Removed the one folder sync in one of two accounts: OK Removed that account: OK Connected to that server again, same account: OK Created three sync folders on that one: OK.. Or??? - strangely on one of them synced another folder than I thought I set, or I had just had too little coffee... Removed that sync: OK It was busy syncing, or rather server (or client?) got almost stale. So i paused the sync: => segfault ! This time I have client log, but seem not to contain the crash. I have the coredump. Will now attach both.
Created attachment 14716 [details] Last part of nextcloud client log crashing from pausing sync
Assignee: qa-bugs => pkg-bugsStatus comment: (none) => proposed 3.13.4-1.mga9 crashes sometimes
Starting from command line I now noticed some problems. They also appear in journal, I realise now: [morgan@svarten ~]$ nextcloud nextcloud.gui.application: Migrating old config from "/home/morgan/.local/share/Nextcloud" to "/home/morgan/.config/Nextcloud" nextcloud.gui.application: Failed to move the old config directory to its new location ( "/home/morgan/.local/share/Nextcloud" to "/home/morgan/.config/Nextcloud" ) Yes. probably because it do not exist in the old place. Stupid formulated message. Well... looking at it: There is no config in ~/.local/share/Nextcloud. But the new Somefolder_sync.log files are getting written there. ~/.config/Nextcloud/ contain nextcloud.cfg, cookies0.db, cookies1.db, sync-exclude.lst and lots of old logs from no longer used servers nextcloud.gui.application: Will move the individual files ("Connie_sync.log", "DokPerProg_sync.log", "Dokument_sync.log", "Familjebilder Morgans_sync.log", "Kunder_sync.log", "Murena_sync.log", "Program_sync.log", "Tribun_sync.log", "VBoxDelning_sync.log") nextcloud.gui.application: Fallback move of "Connie_sync.log" also failed nextcloud.gui.application: Fallback move of "DokPerProg_sync.log" also failed nextcloud.gui.application: Fallback move of "Dokument_sync.log" also failed nextcloud.gui.application: Fallback move of "Familjebilder Morgans_sync.log" also failed nextcloud.gui.application: Fallback move of "Kunder_sync.log" also failed nextcloud.gui.application: Fallback move of "Murena_sync.log" also failed nextcloud.gui.application: Fallback move of "Program_sync.log" also failed nextcloud.gui.application: Fallback move of "Tribun_sync.log" also failed nextcloud.gui.application: Fallback move of "VBoxDelning_sync.log" also failed Three of these are running syncs, the other are removed. Why can´t it move it own files? (all set to my UID an GID) Now one interesting thing, the log of the sync that crashed when i stopped it *is* in "/home/morgan/.config/Nextcloud/" like logs of syncs a year ago. Despite i did set this up fresh, like the other that gets logged in the other folder. Confusing. Anyhow, i believe /home/morgan/.local/share/Nextcloud/ is supposed to be empty. I now: 1. stopped the client 2. Moved away (renamed) that folder 3. Removed everything except nextcloud.cfg, cookies0.db, cookies1.db from ~/.config/Nextcloud/ 4. Again launched nextcloud in console: now *no* output and it just works :) (-and it also created sync-exclude.lst, good to have that one fresh) nextcloud.gui.application: Already running, exiting... I already know running nextcloud is "exiting"... someties in both meanings... ;-) I do no believe this cleanup helps with the crashes. Will see... Anyhow it seems this app need a bit of user care.
I forgo to write it created a new ~/.local/share/Nextcloud/ containing new logs per folder sync.
MGA9-64, Gnome, upgrade The following 6 packages are going to be installed: - kguiaddons-5.114.0-1.mga9.x86_64 - lib64kf5guiaddons5-5.114.0-1.mga9.x86_64 - lib64nextcloudsync0-3.13.4-1.mga9.x86_64 - lib64ocsync0-3.13.4-1.mga9.x86_64 - nextcloud-client-3.13.4-1.mga9.x86_64 - nextcloud-client-nautilus-3.13.4-1.mga9.x86_64 723KB of additional disk space will be used. -- rebooted - Nextcloud sync working - nautilus working
(In reply to Morgan Leijström from comment #35) > I do no believe this cleanup helps with the crashes. Will see... Unfortunately my feeling was correct. This one is soo weird. Had it running, and stress tested by loggin in to the server and moved the folder it was syncing with. (Yes it is a bad design it do not hinder it nor even indicate there is a client connected...) Client then realised target gone with read message at the configured folder sync. I then clicked the three dots in that list and selected to remove the sync. BAM! segfault. Firstline of that in journal: okt 23 23:51:59 svarten.tribun kernel: traps: nextcloud[309624] general protection fault ip:7f476dae6efd sp:7fffce5a04f8 error:0 in libgobject-2.0.so.0.7600.3[7f476dabd000+32000] I can grab all and attach if someone want, but i think time is better spend on getting 3.14+ soonish. The icing on the cake is that it have now misplaced its own files per its own saying. Here is the terminal from where i started it in end of Comment 35, no wit crashed with no output, then i restarted it and it complain: [morgan@svarten ~]$ nextcloud Segmenteringsfel (minnesutskrift skapad) [morgan@svarten ~]$ nextcloud nextcloud.gui.application: Migrating old config from "/home/morgan/.local/share/Nextcloud" to "/home/morgan/.config/Nextcloud" nextcloud.gui.application: Failed to move the old config directory to its new location ( "/home/morgan/.local/share/Nextcloud" to "/home/morgan/.config/Nextcloud" ) nextcloud.gui.application: Will move the individual files ("Connie_sync.log", "Kunder_sync.log", "Tribun_sync.log") Probably not a packaging issue, so I suggest we just roll it out. It works as long as there is no problem. It is probably working as well as the source is designed... But an update with fixed bugs would be good, later. I have no time to search their bug center to tell.
On i586 I can replicate both the crash and complaints on its own files, per procedures in comment 38. --- Additionally - I guess because it runs on LXDE instead of Plasma: 1) It do not remember login, I have to grant it using web browser each desktop start. 2) Popup it complains it cannot sense when file changes so replication is not immediate. I believe both are normal for the circumstance - I guess LXDE lack a compatible password storage and filetrigger. --- On my wifes laptop, Plasma, I see the same issue with main menu placement as described in comment 29. --- Frankly, server provide WebDAV. Isnt there a more mature sync client we can use?
Chewing along on three machines, total more than hundred thousand files, 400GB. It only ever crash, sometimes, if user try to remove a configured sync or server. I believe no data loss. And user need just to restart it, the item user wanted to remove is gone, and user can configure new server and sync folders. Good enough i think, but it is on the edge in my opinion. Input from more testers/systems would be good.
...So I suggest more testing, then validate in a couple of days anyway - if no severe problem is noted.
Status comment: proposed 3.13.4-1.mga9 crashes sometimes => proposed 3.13.4-1.mga9 crashes sometimes when user remove sync or server from configuration.Assignee: pkg-bugs => qa-bugs
MGA9-64, Xfce Upgrade upgraded files and rebooted System is synching as expected.
I have installed this version without issues, but I can't test it well because my nextcloud server Murena.io is fallen... The app run and I can put my account, but I can't connect with server fallen.
CC: (none) => joselpddj
@José I too run Murena.... Using it on Fairphone.) If you want i can give you a login to my Nextcloud instance, hosted at Hetzner. Mail me privately if you want.
OK... ship this. Next round up: Bug 33697 - nextcloud-client update to 3.14+
CC: (none) => sysadmin-bugsWhiteboard: (none) => MGA9-64-OK, MGA9-32-OKKeywords: (none) => validated_update
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2024-0219.html
Status: NEW => RESOLVEDResolution: (none) => FIXED
I note at segfault: the last command line output line before segfault: "There's already a global menu bar..." after having started it from terminal, and later removed a folder sync using its settings dialogue. --- Another thing I note is that the option --logwindow do not open a window with log, which i remember it have some time in the past. It instead logs to file. Same on MS Windows, I tested there now on my fathers system... But both the help output from "nextcloud --help" and the online documentation https://docs.nextcloud.com/desktop/3.13/advancedusage.html still say it should work. Meh.