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

[Bug]: UI broken #7215

Open
4 of 8 tasks
Byter3 opened this issue Sep 26, 2024 · 11 comments
Open
4 of 8 tasks

[Bug]: UI broken #7215

Byter3 opened this issue Sep 26, 2024 · 11 comments

Comments

@Byter3
Copy link

Byter3 commented Sep 26, 2024

⚠️ Before submitting, please verify the following: ⚠️

Bug description

The pop-up window's UI is completlty broken.
kép

Steps to reproduce

Open up the pop-up window

Expected behavior

UI not broken

Which files are affected by this bug

a screenshot

Operating system

Windows

Which version of the operating system you are running.

Windows 11

Package

Official Windows MSI

Nextcloud Server version

29.0.4

Nextcloud Desktop Client version

3.14.0

Is this bug present after an update or on a fresh install?

Updated from a minor version (ex. 3.4.2 to 3.4.4)

Are you using the Nextcloud Server Encryption module?

Encryption is Enabled

Are you using an external user-backend?

  • Default internal user-backend
  • LDAP/ Active Directory
  • SSO - SAML
  • Other

Nextcloud Server logs

No response

Additional info

No response

@ostasevych
Copy link

ostasevych commented Sep 26, 2024

Three questions:

  1. is that possible to revert the UI back? The previous one looks much more attractive, while the newly represented ugly and not working
  2. if not, is that possible to keep two branches: the legacy and the with the new style?
  3. finally, if not, how to make the desktop client not to update itself? I would like to stay on the legacy version.

Thanks!

@ThaDaVos
Copy link

It's broken in multiple ways - it even stops opening after a while and one needs to exit the application and restart it to have the UI open again (Settings UI can still be opened, but one cannot resolve conflicts from there)

@LMRW
Copy link

LMRW commented Sep 26, 2024

It's broken in multiple ways - it even stops opening after a while and one needs to exit the application and restart it to have the UI open again (Settings UI can still be opened, but one cannot resolve conflicts from there)

Is this one tracked? This one is driving me and clients nuts

@lucidnx
Copy link

lucidnx commented Sep 26, 2024

I can confirm both issues mentioned here:

  1. UI broken
  2. unable to open UI
  • ocasional crash when trying to open UI.

How can somebody release so much broken build?

@LMRW
Copy link

LMRW commented Sep 27, 2024

I'll always be grateful for open source software but I do think nextcloud need to reflect on this and offer an explanation on what happened here as I agree this is totally ridiculous

@ThaDaVos
Copy link

The issue of not being able to open it is already tracked but also seems to be solved it latest daily (09-26)
#7156

@Gimzie
Copy link

Gimzie commented Sep 27, 2024

I'm having similar issues with the new UI on Linux (EndeavorOS) with Nextcloud 3.14.0. It appears to be trying to use the system theme or something, but is missing icons and in general looks very broken/unfinished. I'm not sure what theming it was using in previous versions, but I personally find it preferable because it was consistent across devices.

That's in addition to the multitude of syncing/connection closed errors that the application has been throwing with the new version.

image

@nmbgeek
Copy link

nmbgeek commented Sep 29, 2024

Same
image

@ostasevych
Copy link

3.14.1 is not helpful anyway on Win10.

My kind suggestion is to keep 3.13.x branch, and place 3.14.x to dev or unstable in order not to confuse users and stop that aggressive self-updating from 3.13 to 3.14.

@ThowZzy
Copy link

ThowZzy commented Sep 29, 2024

Can second that too !
image

@mgallien
Copy link
Collaborator

please people be patient
we are well aware of those issues but we had to prioritize other fixes to be included in 3.14.1 release
we would very much welcome wider testing of our release candidate during our release process as we cannot ensure issues are discovered without your help
some of the issues in 3.14.0 were never reproduced by the team even if many people were impacted (especially the issue with http2)

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

No branches or pull requests

9 participants