Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#24870 - [chromium] segfaults on startup

Attached to Project: Arch Linux
Opened by alexander (tirrex) - Saturday, 25 June 2011, 02:22 GMT
Last edited by Evangelos Foutras (foutrelis) - Wednesday, 13 July 2011, 17:25 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Evangelos Foutras (foutrelis)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

chromium segfaults after a recent pacman -Syu
$ chromium --version
Chromium 12.0.742.100
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Wednesday, 13 July 2011, 17:25 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Issue seems to be caused by unsupported packages interacting badly with Chromium.
Comment by Ionut Biru (wonder) - Saturday, 25 June 2011, 06:23 GMT
i don't see any crash backtrace here.
Comment by Jelle van der Waa (jelly) - Saturday, 25 June 2011, 07:19 GMT
Please give some more info
Comment by Krzysiek (Krzychek) - Saturday, 25 June 2011, 16:50 GMT
I have a similar problem on Arch x86_64.
Application always crash after firts typed letter, with ONLY one error in console: "Segmentation fault".
It applies not only chromium (when typing in address bar) but in other apps too and so far i can confirm:
*gksu - when typing password and 'run' commend when started without argument.
*banshee - when typing in quick search box.
*chromium - typing in address bar.
Applications don't crash when pasting text into these text fields.
I didn't find any related erros in /var/log/errors.log.
Comment by Jelle van der Waa (jelly) - Saturday, 25 June 2011, 18:41 GMT
It works here:
a) are you up 2 date? (Check your mirrorstatus)
b) do you have some foreign glibc installed -> pacman -Qm
c) strace / gdb chromium
Comment by Evangelos Foutras (foutrelis) - Sunday, 26 June 2011, 09:35 GMT
I can't reproduce the crashes on either i686 or x86_64.

More information is certainly needed. (See jelly's questions.)
Comment by Krzysiek (Krzychek) - Sunday, 26 June 2011, 11:17 GMT
a) Yes, I'm fully updated :D
b) I have glibc from official repo
# pacman -Qm
gnome-shell-extension-autohide-topbar 1.0-1
laptop-init-script 1.1-1
libflashsupport-pulse 20110625-1
plymouth-git 20110625-1
telepathy-sunshine-git 20110625-1
c) Output in: attached file "strace.txt"


Comment by Evangelos Foutras (foutrelis) - Sunday, 26 June 2011, 12:03 GMT
strace and gdb are two different debugging tools. You should run them individually:

1) In the case of strace, run 'strace -o strace-output chromium' and upload the strace-output file.

2) In the case of gdb, run 'gdb /usr/lib/chromium/chromium' and then in the gdb prompt:

a) Issue the command 'run' to begin the execution of Chromium.
b) Wait until it freezes and go back to the terminal running gdb.
c) Enter the commands 'set logging file gdb-output' and 'set logging on'.
d) Get a backtrace with the command 'bt full' (hit the return key until there are no more lines).
e) Exit gdb by issuing 'quit' and upload the gdb-output file.

Debugging symbols are stripped from the chromium binary (and the libraries it uses), so we won't get very useful output from gdb, but we'll have a better idea of what/where it fails.
Comment by Krzysiek (Krzychek) - Sunday, 26 June 2011, 17:58 GMT
'strace' generated huge file so I uploaded it to speedyshare :)
http://www.speedyshare.com/files/29160936/strace-output-chromium
Comment by Jelle van der Waa (jelly) - Sunday, 26 June 2011, 20:46 GMT
I'd say you configure gtk2 config isn't right because there are numerours of lines with file not found.
Comment by Evangelos Foutras (foutrelis) - Monday, 27 June 2011, 06:38 GMT
Can you upload the output from gdb as well?
Comment by alexander (tirrex) - Monday, 27 June 2011, 07:36 GMT
strace and gdb output
Comment by Andre Goree (t0ken) - Sunday, 03 July 2011, 06:30 GMT
I'm having this exact same issue, hoping my strace & gdb outputs can be of some use. I'm on an x86_64 system. Thanks.
Comment by Hans-Peter Sarstrom (hps) - Sunday, 03 July 2011, 09:47 GMT
I had this exact problem, then I ran pacman -R an old google-talkplugin that I had previously installed from AUR (and forgotten all about).
Note that just disabling it from within chromium did not work. (Yes, I had to be quick)

Hope this helps you guys as well.
Comment by Andre Goree (t0ken) - Sunday, 03 July 2011, 09:56 GMT
That resolved it for me, completely forgot about that plugin (b/c it doesn't work). Thanks Hans-Peter!
Comment by Evangelos Foutras (foutrelis) - Sunday, 03 July 2011, 11:02 GMT
Thanks for pinpointing the issue Hans-Peter; I was pretty much lost. :)

tirrex and Krzychek, can you confirm that removing google-talkplugin solves the issue for you as well?
Comment by Krzysiek (Krzychek) - Sunday, 03 July 2011, 18:31 GMT
I haven't installed google-talkplugin even :D
My system looks like one big error(because I'm still studying and playing with Arch), so I'm going to reinstall everything.
EDIT:// After re-installing the system started to be super stable and this "bug" goes away too... So sorry for taking time, it was my fault :/
Comment by Evangelos Foutras (foutrelis) - Wednesday, 13 July 2011, 17:24 GMT
@Krzysiek: hadn't seen your edit there. :)

I'm closing this bug since it seems to be caused by the way unsupported packages interact with Chromium.

Loading...