Arch Linux

done_with_fish

Member

Registered: 2014-12-15

Posts: 7

Chromium terminated by signal SIGSEGV (Addres boundary error)

I'm having trouble opening chromium after upgrading today with

pacman -Syyu

Issuing

$ chromium

produces the error

fish: "chromium" terminated by signal SIGSEGV (Address boundary error)

I'm not sure how to fix the issue. I found a similar problem from 2014 here

https://bbs.archlinux.org/viewtopic.php?id=182488

According to this thread, the issue might be with libxcursor. Issuing

pacman -Qs libxcursor

produces

local/libxcursor 1.1.15-1

It looks like this version of libxcursor is from 2017:

https://www.archlinux.org/packages/extr … ibxcursor/

I'm not sure why libxcursor would be causing an issue now...

After more research, I'm still not sure how to fix the problem. Does anyone have an idea what might be wrong or how I might go about fixing the issue?

seth

Member

Registered: 2012-09-03

Posts: 51,684

Re: Chromium terminated by signal SIGSEGV (Addres boundary error)

The error message you received is completely generic and means "some programmer fucked up and the process tried to access memory that does not belong to it".
For a first better idea of the cause, check whether chromium left a coredump, "man coredumpctl" and if not, run chromium in gdb to obtain a backtrace, https://wiki.archlinux.org/index.php/De … _the_trace

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

foutrelis

Developer

From: Athens, Greece

Registered: 2008-07-28

Posts: 705

Website

Re: Chromium terminated by signal SIGSEGV (Addres boundary error)

Maybe some silliness like this? https://forum.antergos.com/topic/9677/c … -broken/20

Edit: Most likely it's the above; also see FS#58269 and https://crbug.com/834298#c4.

Last edited by foutrelis (2018-04-19 18:48:34)

PixelSmack

Member

Registered: 2009-02-18

Posts: 9

Re: Chromium terminated by signal SIGSEGV (Addres boundary error)

The Antegros thread provided a solution for me.

I.E rm ~/.config/chromium-flags.conf

done_with_fish

Member

Registered: 2014-12-15

Posts: 7

Re: Chromium terminated by signal SIGSEGV (Addres boundary error)

Thanks for pointing this out--I should have checked the Antergos forums first.

Instead of rm ~/.config/chromium-flags.conf I edited the file and altered the line

--user-data-dir=/home/antergos/.config/chromium/Default --homepage=http://antergos.com

by replacing "andergos" with my username. Everything works fine now.

foutrelis

Developer

From: Athens, Greece

Registered: 2008-07-28

Posts: 705

Website

Re: Chromium terminated by signal SIGSEGV (Addres boundary error)

That shouldn't point to the Default directory but its parent. You'll probably notice that you now have a ".config/chromium/Default/Default" directory (along with a bunch of other new directories in .config/chromium/Default/).

It's best to delete chromium-flags.conf if you haven't specified any new flags yourself.

mrunion

Member

From: Jonesborough, TN

Registered: 2007-01-26

Posts: 1,938

Website

Re: Chromium terminated by signal SIGSEGV (Addres boundary error)

....I should have checked the Antergos forums first....

Why? Do you run Antegros?

---

Matt

"It is very difficult to educate the educated."