2.5.0 release. Please report any need to reconfigure login access mode
Logout Required
After installing this update it is required that you logout of
your current user session and log back in to ensure the changes
supplied by this update are applied properly.
This update has been submitted for testing by germano.
Hard to explain in more detail; as I pointed out it doesn't work and says: Connection timed out to server XY. I can access it via FF and WebUI from the same box.
Wow, I was hoping for these issues to get solved for more than a year now and today's the day, thanks! One minor note: the settings window is ignoring the global dark theme, but I'll report this separately on GitHub, if this wasn't already done.
BZ#1487701 Window isn't shown when the app is launched
BZ#1563520 dependency for nextcloud-client will switch to python3
BZ#1647091 Nautilus integration not working/shows nothing
I tested this on three machines all running Fedora 29. On two of them it works just fine but on the third I cannot open the GUI. If I run nextcloud I get this message and nothing happens:
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
So I tried QT_QPA_PLATFORM=wayland nextcloud and got:
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in ""
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
After this I installed qt5-qtwayland and tried it again leading to this:
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
QSocketNotifier: Can only be used with threads started with QThread
Any ideas what else to try? I have no clue what makes the behaviour here different from that on the other ones.
This update has been submitted for testing by germano.
LGTM
Works for me. There is a warning about synchronized folders not being tracked reliably.
This issue is listed in FAQ - https://docs.nextcloud.com/desktop/2.3/faq.html
hm, not connecting to NC server any more after upgrade here: FC29 on VBox.
@markec please read https://www.chiark.greenend.org.uk/~sgtatham/bugs.html
This update has been pushed to testing.
Hard to explain in more detail; as I pointed out it doesn't work and says: Connection timed out to server XY. I can access it via FF and WebUI from the same box.
Wow, I was hoping for these issues to get solved for more than a year now and today's the day, thanks! One minor note: the settings window is ignoring the global dark theme, but I'll report this separately on GitHub, if this wasn't already done.
Nevermind, the problem with the window decorations was homemade and is solved. Nothing to complain about over here.
Besides of known problems like https://github.com/nextcloud/desktop/issues/560 and https://github.com/nextcloud/desktop/issues/560 of the e2e encryption feature, it LGTM.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
@marek you should subscribe to https://github.com/nextcloud/desktop/issues/868
I meant @markec
Works
@germano You might be interested in this issue when making the decision whether to release or not: https://github.com/nextcloud/desktop/issues/279
@germano, there is a regression with this version. Client cannot sync large files. Sync fails with "connection refused".
I will file a detailed bug report once I can test it more.
Thanks @germano! Hope they solve it soon.
I tested this on three machines all running Fedora 29. On two of them it works just fine but on the third I cannot open the GUI. If I run
nextcloud
I get this message and nothing happens:So I tried
QT_QPA_PLATFORM=wayland nextcloud
and got:After this I installed
qt5-qtwayland
and tried it again leading to this:Any ideas what else to try? I have no clue what makes the behaviour here different from that on the other ones.
I think my problem is also related to not falling back to IPv4 if IPv6 connectivity is broken...
works for me
E2E encryption does not seem to work for me, see https://github.com/nextcloud/desktop/issues/890.
Works for me.
I realize I have not added the link to my upstream report. Here it is - https://github.com/nextcloud/desktop/issues/966
This update has been obsoleted by nextcloud-client-2.5.1-1.fc29.