3.14.0 bugs overview

[camilasan]

ℹ️ Status: WIP, need to change to make it more flexible to use http2 - #7182

• [Bug]: Regression issue: sync errors with latest desktop client #7171

❓Need to be confirmed, related to the new feature of enforcing Windows file/folder name rules?

• [Bug]: Synchronization fails if there are special characters in file names in Nextcloud Desktop Client 3.14 #7188

❓Unsure about the status, urgent/approved?

• [Bug]: 3.14.0 UI elements not working and claims sync issues (which are not existent) #7143
• [Bug]: Sync Connection Timeout #7184
• [Bug]: TLS MITM-compromise UX-response needs URGENT fix #7166

ℹ️ UI issues, related to the native UI feature - assigned to @camilasan :

• Font color on Desktop Client Linux in Dark mode  #6554
• [Bug]: Settings panel not respecting system theme (no Dark mode) #7125
• Fix native UI on 3.14 #7121

❓Couldn't find a way to reproduce it, update channel feature - assigned to @camilasan :

• [Bug]: Upgrade to 3.14.0 changes update channel from Stable to Daily #7178

✅ Done:

• [Bug]: Desktop client fails to start (error message included) #7146
• [Bug]: Client AppImage does no start on Linux Mint 22, CE - path override failed for key base #7128
• [Bug]: Can't start Nextcloud desktop Appimage 3.14 #7135
• [Bug]: Main window will not open on Windows #7156
• [Bug]: Edit locally fails always at the validation step #7174

😑 Temporary workaround for now - see #7270:

• [Bug]: Button and scrollbar not dark themed for activity feed / actions #7170

[gvoigtlaender]

There needs to be a regression, #5831 seems to be open again

[ThaDaVos]

Can also add that it stops opening the UI completely (except the Settings UI) after some time and you need to restart the application to get it opening again...

[le-patenteux]

ℹ️ Status: WIP, need to change to make it more flexible to use http2 - #7182

• [Bug]: Regression issue: sync errors with latest desktop client #7171

❓Need to be confirmed, related to the new feature of enforcing Windows file/folder name rules?

If you imply that #7171 is related only to Windows, it is not... 3.14.0 has sync issues on all platforms (Linux, Mac and Windows)

I am repeating myself as in issue 7171, sorry for that, but there is an urgent need for someone to release 3.14.1 as a copy of the latest stable 3.13.x because many customers and users are getting auto-updates of a sync client that can't sync anymore! This will give the team some time to fix the underlying issue.

I have been getting calls for almost a week from users, and been seeing tons of issues and posts being created on multiple discussion groups on that exact problem... The client is spitting misleading errors that makes people believe that the server is at fault, but it is the client.

EDIT:
I have just spotted the 3.14.1 release, but the flatpak version is not up to date yet... Is that something that can be discussed here or is the flatpak version maintained elsewhere?

[Webbeh]

#7171 (comment)

3.14.1 (windows 11) still broken.

[camilasan]

I have just spotted the 3.14.1 release, but the flatpak version is not up to date yet... Is that something that can be discussed here or is the flatpak version maintained elsewhere?

We do not maintain the flatpack.

[DanScharon]

I have just spotted the 3.14.1 release, but the flatpak version is not up to date yet... Is that something that can be discussed here or is the flatpak version maintained elsewhere?

We do not maintain the flatpack.

that's a pity because flatpaks actually provide an update mechanism with code directly from the vendor (i.e. you) and a way to integrate into the file managers (unlike AppImage)

[Webbeh]

Compiling yourself also gets the code right from the vendor.

[cluck]

What is the progress on #7166?

[kubrickfr]

What is the progress on #7166?

I came here to check on the status on that one too. I'm not complaining that it's not done yet, it's an open source project after all, I just don't understand the lack of interest, what does "Unsure about the status, urgent/approved?" mean? It's currently the biggest known security hole in the system and we're just relying on people clicking the right button a million times?