Skip to main content ↑ ↓
Topic: ungoogled-chromium 138 segfault with old config (Read 481 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

ungoogled-chromium 138 segfault with old config

Did a fairly sizeable system update including ungoogled-chromium (137.0.7151.119-1 -> 138.0.7204.49-1), and now it hit a segmentation fault soon after starting. This was fixed by removing the old configuration ~/.config/chromium/. I did not dissect further to identify the culprit (there's a lot of junk in that directory). Before the segfault there were just a bunch of dbus-related errors printed, but it seems those appear even now that it's working.
 

Re: ungoogled-chromium 138 segfault with old config

Reply #1 –
Quote from: lotuskip – on
Did a fairly sizeable system update including ungoogled-chromium (137.0.7151.119-1 -> 138.0.7204.49-1), and now it hit a segmentation fault soon after starting. This was fixed by removing the old configuration ~/.config/chromium/. I did not dissect further to identify the culprit (there's a lot of junk in that directory). Before the segfault there were just a bunch of dbus-related errors printed, but it seems those appear even now that it's working.



This has happened to me once or twice over the years with firefox.  It is a problem.  I ended up abandoning only configs for the new firefox.  The guys here might be able to help, but if not, you might end up having to ask on chromium developers themselves.  They might well know what they changed.  You can read the readmes in the source code as well which often list the differences between versions.