segfault / error 4 in libc-2.8.90.so

[Marc Cheng]

i can't start amarok-kde4 or digikam in Intrepid Ibex beta
dmesg give me following output:

[ 4586.282315] amarok[14575]: segfault at 1 ip 00007f67946c1690 sp 00007fff9eb8f3a8 error 4 in libc-2.8.90.so[7f679463f000+169000]
[ 4804.265751] digikam[14773]: segfault at 1 ip 00007f6e69915690 sp 00007fff773eabc8 error 4 in libc-2.8.90.so[7f6e69893000+169000]

amarok-kde4 in konsole:
~$ amarok
<unknown program name>(15154)/: Communication problem with "amarok" , it probably crashed.
Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" "

digikam in konsole:
~$ digikam
digikam(15158): Root Album Path: "/media/files/bilder"
digikam(15158): Database Path: "/media/files/bilder"
digikam(15158): SchemaUpdater update
digikam(15158): Have a database structure version "5"
digikam(15158): makeUpdates 5 to 5
digikam(15158): listFromType
digikam(15158): got listFromType
digikam(15158): Creating new Location "/bilder" uuid "volumeid:?uuid=5da0f3b4-3310-4b29-b571-0bf337a0165a"
digikam(15158): location for "/media/files/bilder" is available true
Segmentation fault (core dumped)

[Marc Cheng (bdgraue)]

same with juk:

dmesg:
[ 6002.690402] juk[15542]: segfault at 1 ip 00007fb4bd9b6690 sp 00007fffc98f9928 error 4 in libc-2.8.90.so[7fb4bd934000+169000]

konsole:
~$ juk
juk(15541): Communication problem with "juk" , it probably crashed.
Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" "

[Lou (lou-dayspringpublisher)]

I seem to have a related problem since updating to 8.10. Browsers can't open my /home/lat directory. They display the directory for a moment, then the window immediately closes, but the browser shows up at the bottom of the screem for a few more moments.

Dec 18 16:04:54 lat-ws kernel: [ 369.100461] nautilus[14520]: segfault at 746178 ip b7238d31 sp b5a24e48 error 4 in libc-2.8.90.so[b71c9000+158000]
Dec 18 16:06:25 lat-ws kernel: [ 460.789403] gnome-commander[14534]: segfault at 71 ip b6fe3b1e sp bfb36138 error 6 in libc-2.8.90.so[b6f72000+158000]

[Wei Li (lwcn)]

I have a similar fault in my ubuntu 8.10 within the libc-2.8.90.so using compiz.real
Do anyone know what that library is and how to do with it?

[Luke Whitmore (lwhitmore)]

I have another similar fault - if I try to execute gksudo gedit I end up with the following error message:

kernel: [10952.685832] gedit[24874]: segfault at 0 ip b74012c3 sp bfce8a2c error 4 in libc-2.8.90.so[b738a000+158000]

[Carlos Gacimartin (cgacimartin)]

I get the same problem than Lou while trying to access to a vnc http server with a web browser:

Jan 8 18:06:19 shirley kernel: [67278.368978] Xtightvnc[376]: segfault at 5fc7d070 ip 00007fca5f98f6b0 sp 00007fff68993f38 error 4 in libc-2.8.90.so[7fca5f90d000+169000]

[Carlos Gacimartin (cgacimartin)]

I'm using Ubuntu Intrepid 8.10, amd64 version updated (upgrade) daily.
Linux shirley 2.6.27-9-generic #1 SMP Thu Nov 20 22:15:32 UTC 2008 x86_64 GNU/Linux
-rwxr-xr-x 1 root root 1502520 2008-09-29 12:15 libc-2.8.90.so
libc-2.8.90.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), for GNU/Linux 2.6.8, dynamically linked (uses shared libs), stripped.

[Kevin Croissant (kevin-kevincroissant)]

I also had a segfault when running tlip2. It ran for about 10 seconds, closed, and in a terminal window, I found an error saying segmentation fault. I checked kern.log and found this:
Jan 11 18:05:36 Ubuntu-laptop kernel: [30493.560717] tilp[18899]: segfault at 0 ip b7488d28 sp bfb56f4c error 4 in libc-2.8.90.so[b7412000+158000]
running i386 ubuntu 8.10 with kernel 2.6 due to compat issues.

[Daniel Bair (danielbair)]

I am also getting a segfault message on my CrunchBang 8.10 system:
[14775.343595] php5[18939]: segfault at 0 ip b7a96591 sp bf8a1c6c error 4 in libc-2.8.90.so[b7a36000+158000]
[14835.930582] php5[19112]: segfault at 0 ip b7acb591 sp bf8d74ac error 4 in libc-2.8.90.so[b7a6b000+158000]
[14895.784451] php5[19301]: segfault at 0 ip b7907591 sp bfe139dc error 4 in libc-2.8.90.so[b78a7000+158000]
[14955.621659] php5[19627]: segfault at 0 ip b7a18591 sp bfc23fec error 4 in libc-2.8.90.so[b79b8000+158000]
[15015.498406] php5[19913]: segfault at 0 ip b7aee591 sp bfaf7ecc error 4 in libc-2.8.90.so[b7a8e000+158000]
[15075.006961] php5[20132]: segfault at 0 ip b7929591 sp bfc337fc error 4 in libc-2.8.90.so[b78c9000+158000]

[Hélio Nunes (dedalu-dedalu)]

Same (I think) here, with uvccapture.

Each shot prints on log/messages:

kernel [48639.690287] uvccapture[4421]: segfault at 0 ip 00007f81db679f72 sp 00007fffe3d84ea0 error 4 in libc-2.8.90.so[7f81db5d1000+169000]
kernel [48647.886920] uvccapture[4433]: segfault at 0 ip 00007f2606822f72 sp 00007fff0ef2c050 error 4 in libc-2.8.90.so[7f260677a000+169000]
kernel [48682.730732] uvccapture[4490]: segfault at 0 ip 00007fba1f12df72 sp 00007fff27838970 error 4 in libc-2.8.90.so[7fba1f085000+169000]

etc.

But uvccapture is running fine:
> gdb uvccapture
(gdb) set args -m
(gdb) run
Starting program: /usr/bin/uvccapture -m
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)

Program exited normally.

[zamrg (zamrg)]

getting this with dansguardian when I try a http request from a client, and the request is then past through dansguardian on the server

Apr 2 13:09:23 zephyr kernel: [ 585.708149] dansguardian[9900]: segfault at 1 ip b7cf22fb sp bfa7f50c error 4 in libc-2.8.90.so[b7c7b000+158000]
Apr 2 13:09:24 zephyr kernel: [ 586.898704] dansguardian[9894]: segfault at 98 ip b7cf2323 sp bfa7f50c error 4 in libc-2.8.90.so[b7c7b000+158000]
Apr 2 13:09:29 zephyr kernel: [ 591.144595] dansguardian[9897]: segfault at 5f ip b7cf22fb sp bfa7f50c error 4 in libc-2.8.90.so[b7c7b000+158000]
Apr 2 13:09:29 zephyr kernel: [ 591.148050] dansguardian[9898]: segfault at 5c ip b7cf2323 sp bfa7f50c error 4 in libc-2.8.90.so[b7c7b000+158000]
Apr 2 13:09:29 zephyr kernel: [ 591.188163] dansguardian[14751]: segfault at 60 ip b7cf2323 sp bfa7f50c error 4 in libc-2.8.90.so[b7c7b000+158000]
Apr 2 13:09:29 zephyr kernel: [ 591.384150] dansguardian[14753]: segfault at 68 ip b7cf2323 sp bfa7f50c error 4 in libc-2.8.90.so[b7c7b000+158000]
Apr 2 13:09:29 zephyr kernel: [ 591.500138] dansguardian[14749]: segfault at 5f ip b7cf22fb sp bfa7f50c error 4 in libc-2.8.90.so[b7c7b000+158000]
Apr 2 13:09:29 zephyr kernel: [ 591.640131] dansguardian[14754]: segfault at 4c ip b7cf2323 sp bfa7f50c error 4 in libc-2.8.90.so[b7c7b000+158000]
Apr 2 13:09:29 zephyr kernel: [ 591.643865] dansguardian[14757]: segfault at 4a ip b7cf22fb sp bfa7f50c error 4 in libc-2.8.90.so[b7c7b000+158000]
Apr 2 13:09:34 zephyr kernel: [ 596.576184] dansguardian[9896]: segfault at 2f5054 ip b7cf2323 sp bfa7f50c error 4 in libc-2.8.90.so[b7c7b000+158000]
Apr 2 13:09:34 zephyr kernel: [ 596.616150] dansguardian[14750]: segfault at 4b ip b7cf22fb sp bfa7f50c error 4 in libc-2.8.90.so[b7c7b000+158000]
Apr 2 13:09:34 zephyr kernel: [ 596.624179] dansguardian[9899]: segfault at 2f5054 ip b7cf2323 sp bfa7f50c error 4 in libc-2.8.90.so[b7c7b000+158000]

[elfstone (h-launchpad-elfstone-de)]

I have the same problem, when using pidgin and try to connect to the server. Pidgin does not crash, but says it cannot resolve the host of the authentication server, and i get an error like this in /var/log/messages:

Apr 6 16:56:47 etppc25 kernel: [ 3033.336981] pidgin[8752]: segfault at 9200000 ip b751948d sp bff14c84 error 4 in libc-2.8.90.so[b74a8000+158000]

[Lou (lou-dayspringpublisher)]

The causes of my problem were several empty files with graphics
characters for names. Once they were deleted from my home directory, no
more crashes!

[Fionn (fbe)]

I get the same error when I try to connect pidgin to the internal jabber server at work. This error turns up in the syslog and pidgin completely crashes with a segfault. For me this is a bit of a problem since I need to have acces to the jabber network at my company.

--
Jul 24 10:04:12 rtfm kernel: [119073.212576] pidgin[14215]: segfault at 0 ip b76e2613 sp bf8c08d8 error 4 in libc-2.9.so[b766b000+15c000]
--

This is a fresh jaunty install. Until last week I was on hardy and everything worked fine there.

[penalvch (penalvch)]

Marc Chang, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line:
sudo nano /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and try to file the crash report again via:
ubuntu-bug /var/crash/_my_crash_report.crash

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently.

Please do not attach your crash report manually to this report and reopen it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs