evince crashed with SIGSEGV in g_settings_backend_watch()

[Nicolas DERIVE]

Starting Evince I got this crash

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: evince 3.2.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic-pae 3.0.4
Uname: Linux 3.0.0-12-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu2
Architecture: i386
CheckboxSubmission: c4273c0f4f2b8d26cd6bf31cadfd2912
CheckboxSystem: a871981cb5bdf4d6ebd55be46becf77e
Date: Thu Oct 6 23:41:18 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/evince
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic-pae root=UUID=57815366-c975-4e08-a10e-208025672f51 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 LANGUAGE=fr_FR:fr:en_GB:en
SegvAnalysis:
 Segfault happened at: 0xb6e32450 <g_settings_backend_watch+112>: mov 0xc(%edi),%eax
 PC (0xb6e32450) ok
 source "0xc(%edi)" (0x0000000c) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evince
StacktraceTop:
 g_settings_backend_watch (backend=0x0, vtable=0xb6eded78, target=0xb818ab50, context=0x0) at /build/buildd/glib2.0-2.30.0/./gio/gsettingsbackend.c:249
 g_delayed_settings_backend_new (backend=0x0, owner=0xb826cef0, owner_context=0xb7fa1570) at /build/buildd/glib2.0-2.30.0/./gio/gdelayedsettingsbackend.c:489
 g_settings_delay (settings=0xb826cef0) at /build/buildd/glib2.0-2.30.0/./gio/gsettings.c:2100
 ?? ()
 g_type_create_instance (type=3042973256) at /build/buildd/glib2.0-2.30.0/./gobject/gtype.c:1885
Title: evince crashed with SIGSEGV in g_settings_backend_watch()
UpgradeStatus: Upgraded to oneiric on 2008-10-18 (1083 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev pulse pulse-access scanner tape users video

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #839876, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.