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!
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!
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
Opened by alexander (tirrex) - Saturday, 25 June 2011, 02:22 GMT
Last edited by Evangelos Foutras (foutrelis) - Wednesday, 13 July 2011, 17:25 GMT
|
Detailschromium 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.
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.
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.
a) are you up 2 date? (Check your mirrorstatus)
b) do you have some foreign glibc installed -> pacman -Qm
c) strace / gdb chromium
More information is certainly needed. (See jelly's questions.)
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"
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.
http://www.speedyshare.com/files/29160936/strace-output-chromium
Note that just disabling it from within chromium did not work. (Yes, I had to be quick)
Hope this helps you guys as well.
tirrex and Krzychek, can you confirm that removing google-talkplugin solves the issue for you as well?
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 :/
I'm closing this bug since it seems to be caused by the way unsupported packages interact with Chromium.