nextcloud
[Bug]: Nextcloud UI (3.14.1) is broken on Windows 10 (21H2 19044.4894) using dark mode
⚠️ Before submitting, please verify the following: ⚠️
- [x] This is a bug, not a question or a configuration issue.
- [x] This issue is not already reported on Github (I've searched it).
- [x] Nextcloud Server and Desktop Client are up to date. See Server Maintenance and Release Schedule and Desktop Releases for supported versions.
- [x] I agree to follow Nextcloud's Code of Conduct
Bug description
Nextcloud UI (3.14.1) is completely broken in Windows 10 (21H2 19044.4894).
Steps to reproduce
Read above
Expected behavior
Not broke.
Which files are affected by this bug
Nextcloud Desktop
Operating system
Windows
Which version of the operating system you are running.
Read above
Package
Official Linux AppImage
Nextcloud Server version
Not sure
Nextcloud Desktop Client version
Read above
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
Client. No need for server logs.
Additional info
No response
For me: if the Windows dark mode is enabled, the font color changes to white, but the background remains also white.
Windows light mode: seems to fix this...
I tried downgrading and confirmed this bug also exists in 3.14.0. Downgrading further to 3.13.4 resolves it, so looks like the bug started in 3.14.0
can confirm this too (though completely broken is bit too harsh) .. the darkmode (Systemsetting in Windows10) shows a nearly unusuable Mainwindow . Letters and some icons and the content of the popup when selecting accounts/settings are light, so as the background, the background should be dark. In Windows lightmode we have a light background with dark letters and it looks ok.
this shouldn't be too hard to fix i guess.
As this seems to be broken since 3.14.0 I guess it is somewhere around this PR: https://github.com/nextcloud/desktop/pull/4584
a quick update from my side windows 11 light and dark mode are on their way to get a working release feel free to test this build from the stable branch: https://cloud.nextcloud.com/s/7rm65tyMDLN4CkF for windows 10, let's use this issue to track the bugs with dark mode (original report from @PeterTucker ) this is currently not working as Qt6 does not switch to dark palette when running on Windows 10 in dark mode for background, you can read https://www.qt.io/blog/dark-mode-on-windows-11-with-qt-6.5 and sorry for the problems, we are working on it
@mgallien thank you. If you need someone to test any working dark mode build for Windows 10, feel free to reach out.
I have exactly the same issue, since the GUI was reworked. Using the version 3.14.1
Windows 10 22H2 19045.4894
The decision to switch to Qt6 without checking the dependencies beforehand is annoying to say the least. Maybe it wasn't even widely known. Whatever the case, it's good that it's going to be fixed 👏 keep on doing the good stuff 😀
fixing this is now planned for the 3.14.2 milestone with release date planned for 17/10/2024
Same here . Why not just dropp the layovers and leave a "Normal" win UI window ? Or at least give the user a choice without forcing any "decorations" that can be desired by one, and hated / buggy for others ?
Any news on this?
It looks like the fix was moved to the next release 3.14.3. According to the issue history.
Have the same problem, Win10 (22H2) 64x dark theme. I have installed version 3.14.2.
Same issue here on Windows 10. Switching windows theme to light fixes the issue. Let's hope that NextCloud will fix this issue soon.
Since we don't really know the timeline on this (and I see this is now a bug for 3.15), does anyone know the last working version of Nextcloud client? I'd like to downgrade my client. It's okay if it's light themed.
@Rello @claucambra
Hello,
3.15 has mainly a technical reasons because there was an issue with the versioning in 3.14. Depending on your urgency, if you can wait another week, you can save yourself the downgrade. we are testing the next version including the fix already internally
Definitely can wait the week. Good to know the 3.15 fix is on the way. Thanks for updating everyone. 👍
This is really annoying, such a stupid bug. Is it really that hard to fix?
Hi, its a but in QT. we are currently testing an implemented workaround. stay tuned