[Oneiric] gsd-segfault error 14 in libvorbisenc.so.2.0.8

[Sam_]

On shutdown gsd segfaults, messages can be found next day in logfiles (attached). But system shut down ok.
In /var/crash is an apport crash file _usr_lib_gnome-settings-daemon_gnome-settings-daemon.1000.crash, but it's locked, when trying to upload via terminal it says permission denied. There is a .lock file in /var/crash.

Still segfaulting after recent updates and reboot.
Jul 2 00:58:29 kernel: [10289.035211] gnome-settings-[1375]: segfault at 7f35538d7b10 ip 00007f35538d7b10 sp 00007fffa9bdf2f8 error 14 in libvorbisenc.so.2.0.8[7f3555d9c000+2b3000]
Jul 2 00:58:29 kernel: Kernel logging (proc) stopped.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: gnome-settings-daemon 3.1.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.0-2.3-generic 3.0.0-rc4
Uname: Linux 3.0-2-generic x86_64
NonfreeKernelModules: wl
Architecture: amd64
Date: Fri Jul 1 23:10:33 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110423)
ProcEnviron:
 PATH=(custom, no user)
 LANG=C
 SHELL=/bin/bash
SourcePackage: gnome-settings-daemon
UpgradeStatus: No upgrade log present (probably fresh install)

[Jean-Baptiste Lallement (jibel)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

You might need to enable apport in /etc/default/apport and restart.

Now 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'.

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. Thanks in advance for your cooperation and understanding.

[Sam_ (and-sam)]

After reboot today it showed again segfault from shutdown yesterday. Apport says the report is damaged. Maybe it tries to overwrite it, so I've removed it and maybe have a new one on next reboot.

[Sam_ (and-sam)]

Segfault again. No luck with sudo, apport still says file is damaged. It's owned by user and I made it r+w to upload manually.

[Sam_ (and-sam)]

After recent updates and reboot today no gsd-segfault in log files.
The last one was on logout this morning, the time from above crash file.
Jul 5 00:41:27 kernel: [ 2656.312282] gnome-settings-[3324]: segfault at 7fe3a8679b10 ip 00007fe3a8679b10 sp 00007fff8fa43278 error 14 in libvorbisenc.so.2.0.8[7fe3aab3e000+2b3000]
Jul 5 00:41:28 kernel: Kernel logging (proc) stopped.

[Sam_ (and-sam)]

Revoke statement #8 segfault still present on shutdown, but no new crash report in /var.
Jul 5 23:32:49 kernel: [ 4399.742726] gnome-settings-[1505]: segfault at 7f2fc0b5db10 ip 00007f2fc0b5db10 sp 00007fff38afa0a8 error 14 in libvorbisenc.so.2.0.8[7f2fc3022000+2b3000]
Jul 5 23:32:49 kernel: Kernel logging (proc) stopped.

[Pedro Villavicencio (pedro)]

please do use apport as described above an file a new bug, one without a backtrace and only comments is useless for us, thanks.

[Sam_ (and-sam)]

Pedro, please read #5. I did exactly this right now again
$ sudo ubuntu-bug /var/crash/_usr_lib_gnome-settings-daemon_gnome-settings-daemon.1000.crash
and apport says file is damaged.

I've also tried:
$ sudo ubuntu-bug -c _usr_lib_gnome-settings-daemon_gnome-settings-daemon.1000.crash -u 804545
and got to LP authorization page and passed (Use your browser to authorize
this program to access Launchpad on your behalf), but crash report wasn't uploaded here (yet?).

The segfault occurs on shutdowns and next day on reboot there is the crash file, which apport claims is damaged.

What is your solution on that?

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[Sam_ (and-sam)]

Thanks Sebastien, again, the crash happens on computer shutdown, so this
"Perform any actions necessary to reproduce the crash" means I would run gdb, then shutdown the computer and after reboot retrieve a backtrace from a gdb which isn't of course running anymore after reboot.
Never mind, g-s-d segfault doesn't interfere with Oneiric stability, if it wasn't noticed in log file I wouldn't even know it happened.

[Sebastien Bacher (seb128)]

is the apport report corrupted every time? it could be that the box stops before apport write its report, does it happen on session closing as well?

[Sam_ (and-sam)]

Yep, it's corrupted every time, tried uploading the crash from yesterdays shutdown which displays the 'padding' error from #5.
Last lines from yesterdays syslog.
Jul 6 23:34:56 kernel: [ 5422.183400] gnome-settings-[1558]: segfault at 7fe135f5fb10 ip 00007fe135f5fb10 sp 00007fff562c5c88 error 14
Jul 6 23:34:57 kernel: Kernel logging (proc) stopped.
Jul 6 23:34:57 rsyslogd: [origin software="rsyslogd" swVersion="5.8.1" x-pid="869" x-info="http://www.rsyslog.com"] exiting on signal 15.

Segfault messages toggle between above one or refer to libvorbisenc.so.

Regarding session logout there is another issue, which I haven't reported yet.
Logout via session menu logs out but lightdm isn't displayed, only desktop wallpaper.
Since unable to log back in on lightdm, switched to tty and rebooted.
After reboot via tty no segfault of g-s-d in syslog or new crash file in /var/crash. The crash file from yesterday is still there.

[Sam_ (and-sam)]

Just found Bug #791875 which may refer to logout-in issue.

[Sam_ (and-sam)]

Sorry for the noise, this Bug #800904 matches exactly logout-in issue.

[Sam_ (and-sam)]

After reboot due to recent updates via update manager again segfaults, but no new crash file generated, the one from July 6th remains unchanged.
Jul 7 19:15:01 AptDaemon.Worker: INFO: Finished transaction /org/debian/apt/transaction/23585575236b48328e3a75ed409a1f10
Jul 7 19:16:59 kernel: [ 4487.071746] gnome-settings-[1330]: segfault at 7f3e5dc9ab10 ip 00007f3e5dc9ab10 sp 00007ffffcd74248 error 14 in libvorbisenc.so.2.0.8[7f3e5fb31000+2b3000]
Jul 7 19:16:59 gnome-session[1267]: WARNING: Application 'gnome-settings-daemon.desktop' killed by signal
Jul 7 19:17:00 kernel: Kernel logging (proc) stopped.

[Sam_ (and-sam)]

No segfaults and crash reports anymore since yesterday updates. Thanks.