Strange Chrome Profile loading error

BarkingGhostar

Diamond Member
Nov 20, 2009
8,410
1,617
136
First, do folks just use FF in Linux (e.g. LM18), or Chrome? I noticed there is Chrome and Chromium, but both seem to exhibit the same error when launching. I went through their respective uninstall, but still found junk from them in several places requiring rot level cleanup.
 

lxskllr

No Lifer
Nov 30, 2004
59,425
9,944
126
I use Firefox. If you want to completely remove a package, here's a web search...

https://duckduckgo.com/?q=completely+remove+package+ubuntu&t=fpas

You can pick the method you prefer. I use synaptic as a package manager, and selecting 'completely remove'(or something like that) sbould get rid of everything.

Dunno about your error, you didn't specify, and I'm not that familiar with chrome(ium), but I suspect they share a configuration directory.
 

Red Squirrel

No Lifer
May 24, 2003
70,166
13,573
126
www.anyf.ca
I use Firefox too, as I don't really trust chrome with privacy, and Chromium is basically just built off it. I think it's probably safe to use though. I still keep it handy as if a site refuses to work in FF because of adblock etc and I really need to get to it, I just use Chromium, which I have zero extensions installed in.

I've never had any issues launching it though so can't help with that. I presume you used the package manager? You should be able to uninstall and reinstall. I find LM18 has some weird quirks at times with certain programs though. The other day I was having issues with the calculator and a few other programs. The GUI would just not accept any kind of input. Ended up having to reboot the whole system.
 

lxskllr

No Lifer
Nov 30, 2004
59,425
9,944
126
I find LM18 has some weird quirks at times with certain programs though. The other day I was having issues with the calculator and a few other programs. The GUI would just not accept any kind of input. Ended up having to reboot the whole system.
Sometimes updates will change some bits around and give unusual behavior until you reboot. I can usually anticipate it by seeing what's updated, but not always. The best thing to do would probably be updating once a week, then reboot the machine just in case. That also helps keep track of updates, so you have a better idea of what broke instead of rebooting after a couple months of updates, and wondering why your stuff isn't working when it comes back up.