Comment 27 for bug 630884

Revision history for this message
Dmitry Shachnev (mitya57) wrote : Re: [Bug 630884] Re: nautilus crashed with SIGSEGV in g_closure_invoke()

2010/11/18, steubens <email address hidden>:
> it wont let me change the status, this bug is _not_ fixed
>
> --
> nautilus crashed with SIGSEGV in g_closure_invoke()
> https://bugs.launchpad.net/bugs/630884
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Nautilus: Fix Released
> Status in “nautilus” package in Ubuntu: Fix Released
> Status in “nautilus” source package in Maverick: Fix Released
>
> Bug description:
> Binary package hint: nautilus
>
> The crash occurred when unmounting one of the two partitions of an external
> USB hard drive.
>
> ProblemType: Crash
> DistroRelease: Ubuntu 10.10
> Package: nautilus 1:2.31.90-0ubuntu3
> ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
> Uname: Linux 2.6.35-19-generic x86_64
> NonfreeKernelModules: nvidia
> Architecture: amd64
> Date: Sun Sep 5 15:21:26 2010
> ExecutablePath: /usr/bin/nautilus
> ProcCmdline: nautilus --sm-client-id
> 10928320c4a96d9667123966432354984000000032280024 --sm-client-state-file
> /home/username/.config/session-state/nautilus-1283608771.desktop
> ProcEnviron:
> LANG=en_GB.UTF-8
> SHELL=/bin/bash
> SegvAnalysis:
> Segfault happened at: 0x44c9af: mov (%r12),%rax
> PC (0x0044c9af) ok
> source "(%r12)" (0x00000020) not located in a known VMA region (needed
> readable region)!
> destination "%rax" ok
> SegvReason: reading NULL VMA
> Signal: 11
> SourcePackage: nautilus
> StacktraceTop:
> ?? ()
> g_closure_invoke ()
> ?? () from /usr/lib/libgobject-2.0.so.0
> g_signal_emit_valist ()
> g_signal_emit () from /usr/lib/libgobject-2.0.so.0
> Title: nautilus crashed with SIGSEGV in g_closure_invoke()
> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/nautilus/+bug/630884/+subscribe
>