nautilus crashed with SIGSEGV in memset()

[Andy Loughran]

Binary package hint: nautilus

I'm using apport, so I think the information required is automagically supplied. If I'm not right, then I'll post the correct information later.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/nautilus
Package: nautilus 1:2.26.2-0ubuntu2
ProcCmdline: nautilus
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 memset () from /lib/tls/i686/cmov/libc.so.6
 g_slice_alloc0 () from /usr/lib/libglib-2.0.so.0
 gconf_value_new () from /usr/lib/libgconf-2.so.4
 gconf_value_copy () from /usr/lib/libgconf-2.so.4
 gconf_entry_new () from /usr/lib/libgconf-2.so.4
Tags: ubuntu-unr
Title: nautilus crashed with SIGSEGV in memset()
Uname: Linux 2.6.29-1-netbook i686
UserGroups: adm admin audio cdrom dialout dip fax fuse plugdev pulse pulse-access pulse-rt sambashare scanner tape video
SegvAnalysis:
 Segfault happened at: 0xb71ef377 <memset+55>: rep stos %eax,%es:(%edi)
 PC (0xb71ef377) ok
 source "%eax" ok
 destination "%es:(%edi)" (0xb773feeb) in non-writable VMA region: 0xb7734000-0xb7778000 r-xp /usr/lib/libgobject-2.0.so.0.2104.0
SegvReason: writing VMA /usr/lib/libgobject-2.0.so.0.2104.0

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

 * Is this reproducible?
 * If so, what specific steps should we take to recreate this bug?

 This will help us to find and resolve the problem.

[Sebastien Bacher (seb128)]

Could you try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report too?

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!