I solved it by removing ~/.pki
Thank you . I've been messing around for two days trying to figure out why everything is crashing around me... This solved the issue.
Now I just need to go back and clean the mess I made...
Maybe try deleting the $HOME/.config/chromium directory and try again.
]]>$ chromium
Segmentation fault (core dumped)
$ chromium --version
Segmentation fault (core dumped)
Any ideas as to how I can debug this problem better? How do I increase the verbosity? Where is the core dumped to? I really enjoyed Chromium (I'm running GNOME 3, the GNOME browser is unusably slow be comparison even on a beast of a machine - I think it's fundamentally broken) but now I am relegated to using a less performant browser.
]]>I'm on 64bit with GPT, although this shouldn't be a problem. What is interesting is that I use btrfs, could this be a problem?
]]>Who of you uses 64 bits? I do.
Me, too. But I've just re-partitioned my disk and reinstalled the system, because I needed to install a Windows, too and it can't be done on a disk with GPT. I don't have any problems now. Do you use a disk with GPT or MBR? Don't know if it could have an effect or not...
]]>update: I'm getting more and more crashes. All says just segmentation fault, but with gksu I got this:
(gksu:2443): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Error on line 1 char 57: Element 'b' was closed, but the currently open element is 'big'
I don't know what it means, so don't know that it's related or not.
]]>So i switched back to google-chrome-beta, which is working fine.
]]>% pacman -Rscn chromium
% sudo updatedb
% locate chromium (and removed every file found)
% pacman -S chromium
% chromium
[1] 9317 segmentation fault (core dumped) chromium
%
What is happening?
]]>