You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem
Upgrading from 124.X to 126.X causes a crash on boot if the Preferences file in the profile contains the string "theme":{"id":"","system_theme":1}, inside the extensions object. I'm guessing this is the setting that controls the experimental Thorium theme, which I had enabled in 124. Removing the string from the Preferences file causes the upgrade to succeed without further problems.
Additional Notes
Mostly putting this here so it can hopefully be automatically fixed in future releases, or at least so that others running into the same problem can find it and know how to solve it without needing to debug for a few hours like I ended up doing. 🙃
The text was updated successfully, but these errors were encountered:
@Thulinma This is not the reason for the crash, but you're close. Thanks for letting me know, as I was wondering if the code change would cause crashes on other systems.
Also, what experimental thorium theme in M124 are you talking about.
Ah yes, it was just a guess. Glad that you know what it is, at least! 👍
I.... don't recall what exact release had this, but some releases ago there was a theme of some sort mentioned in the "Thorium Experiments". I only noticed it was gone in the latest version but that may have actually disappeared much longer ago. I don't check the experiments list all that often. Sorry for any confusion! 😅
System Details
Problem
Upgrading from 124.X to 126.X causes a crash on boot if the
Preferences
file in the profile contains the string"theme":{"id":"","system_theme":1},
inside theextensions
object. I'm guessing this is the setting that controls the experimental Thorium theme, which I had enabled in 124. Removing the string from thePreferences
file causes the upgrade to succeed without further problems.Additional Notes
Mostly putting this here so it can hopefully be automatically fixed in future releases, or at least so that others running into the same problem can find it and know how to solve it without needing to debug for a few hours like I ended up doing. 🙃
The text was updated successfully, but these errors were encountered: