Zettlr: [BUG] Everything is frozen after a change of skin (Bordeaux)

Created on 3 Jul 2020 · 6Comments · Source: Zettlr/Zettlr

Description

At the first installation, everything was working. I changed the skin: Bordeaux. The software doesn't respond to commands anymore, despite uninstalling and reinstalling. I switch to 1.6 and changed the skin (the software was logically naked): Berlin and everything works again.

Reproducing

So sorry, I couldn't reproduce the bug: after repeated uninstallation and reboot, the software in 1.7 doesn't respond to any command.

Expected behaviour

When I restarted the software after the first skin change (in 1.7, to Bordeaux) :

X6D17_pO jpg large

Platform

OS and version: Windows 10.0.18363
Zettlr Version: 1.7.0
Screen Resolution: 1920x1080

Thank you very much for your great work for a great tool !

bug [critical] not confirmed

Source

Myllaume

All 6 comments

Thanks so much for opening up your first issue here on the repository! 🎉 We would like to warmly welcome you to the community behind the app! ☺️ We'll check in soon and have a look at your issue. In the meantime, you can check your issue and make sure it aligns with our contribution guidelines! Here's the comprehensive list:

Enhancements

An enhancement takes a feature and improves or alters its behaviour. Please make sure to argue how your proposition will aid non-technical text workers, and why it can't be emulated easily with other features or apps!

Feature requests

Feature requests introduce whole new features into the app. This requires a lot of work, so these might be turned down if the implementation costs supersede the benefits we expect to see from implementing it. Please do not be disappointed if that happens. It likely has nothing to do with your great request but simply with us and our missing resources!
You can of course always ask someone to implement this feature, because a PR with a working new feature has much higher chances of being merged! :)

Bug reports

Please note that one of the main reasons for why bug reports cannot be addressed is that there's not enough information for us to find and fix the bug you describe, so make sure you try to pinpoint the bug as close as possible.
The ideal bug report for us has two qualities:

The bug is always reproducible, at least within a certain context. 2. We know exactly what specifically goes wrong, and there is consensus on
what should happen instead.

Please note that if you encounter behaviour that does not align with your expectations of what would happen, this might as well be simply intended behaviour and we need to simply _clarify_ why the behaviour is the way it is. This is not to be considered a bug and such issues may be closed! Suggest an enhancement instead!
But now, have a great day and thank you again!

boring-cyborg[bot] on 3 Jul 2020

This almost looks as if the Bordeaux-theme file wasn't correctly loaded … mhh. I'll try to reproduce here locally! Curious that this has never happened during the betas …

nathanlesage on 3 Jul 2020

I have the same problem on MacOS. I was using the beta before and using Bordeaux and it wasn't a problem. Before this issue, I also had the problem mentioned elsewhere with editing links.

emarshphd on 3 Jul 2020

I've experienced the same exact problem in Kubuntu 20.04, after changing the theme to Bordeaux. In one of attempts to open Zettlr, after a few minutes it became responsive, so I went to preferences, changed the theme to the green one. It seemed ok, but soon it became not responsive again. After 3 or 4 minutes, it started working again normally. During the problems, laptop's fans were working noisily - zettlr was consuming 13% of CPU. I closed Zettlr and started it again, to replicate the problem: when opening Zettlr it freezed for a couple of minutes, 13%CPU, after that it seemed ok, then when moving through notes, it freezed again. Then after another couple of minutes, it changed to another note I clicked before (when feezed), then freezed again.