Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

3.14.0 bugs overview #7191

Open
9 of 15 tasks
camilasan opened this issue Sep 23, 2024 · 9 comments
Open
9 of 15 tasks

3.14.0 bugs overview #7191

camilasan opened this issue Sep 23, 2024 · 9 comments
Labels

Comments

@camilasan
Copy link
Member

camilasan commented Sep 23, 2024

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

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

❓Unsure about the status, urgent/approved?

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

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

✅ Done:

😑 Temporary workaround for now - see #7270:

@gvoigtlaender
Copy link

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

@ThaDaVos
Copy link

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
Copy link

le-patenteux commented Sep 28, 2024

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

❓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
Copy link

Webbeh commented Sep 29, 2024

#7171 (comment)

3.14.1 (windows 11) still broken.

@camilasan
Copy link
Member Author

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
Copy link

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
Copy link

Webbeh commented Sep 30, 2024

Compiling yourself also gets the code right from the vendor.

@cluck
Copy link

cluck commented Oct 30, 2024

What is the progress on #7166?

@kubrickfr
Copy link

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

8 participants