deep g

Hello, > Also, is it possible to somehow keep the current configuration? Your current configuration should stay except any changes from the new features that do not exist in the...

Hello, > I've installed the version from the openbar2.0 branch, but the problem persists. Well, we need to find the root cause then. What exactly is causing the crash. I...

Hello @StanSvec and @alq3f , I have good news and better news. I have been using Candybar for the past couple days and finally faced the Crash issue today, so...

One more thing, even with the workaround, the issue seems to happen more with the 'Accessibility' indicator in the panel and not really when the indicator is not there. Not...

> I updated the code from the branch (last commit yesterday 16th), but the issue is not fixed by that even after I removed the Accessibility icon. I'll wait for...

Quick Update: - I have merged OpenBar 2.0 into 'main' branch so all new updates will be there. - The main issue for Candy crash saga will only be fixed...

@StanSvec Thank you for the update. In my test it wouldn't crash on

> There is another update coming soon where the loading and unloading of stylesheet is altered to accommodate NixOS like immutable distros. That might help here too but would need...

Hello @coyotle , With latest update (v37), the released version is up to date with `main` branch. As discussed in the thread, the core issue seems to be upstream in...

Thanks! However, can you please turn off Dash-to-dock. Reboot and reproduce the Open Bar crash. Then collect the journalctl log for the previous/crashed session. This is since there is a...