nautilus crashed with SIGSEGV in g_type_check_instance()

[Rwatts]

Binary package hint: nautilus

nautilus crashed with SIGSEGV in g_type_check_instance()

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/nautilus
Package: nautilus 1:2.24.0-0ubuntu2
ProcAttrCurrent: unconfined
ProcCmdline: nautilus --no-hostname --browser
ProcEnviron:
 PATH=/home/User Namename/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_type_check_instance () from /usr/lib/libgobject-2.0.so.0
 g_signal_handlers_disconnect_matched ()
 ?? ()
 ?? ()
 ?? ()
Title: nautilus crashed with SIGSEGV in g_type_check_instance()
Uname: Linux 2.6.27-7-generic i686
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev root sambashare scanner tape video

[Apport retracing service (apport)]

StacktraceTop:g_type_check_instance () from /usr/lib/libgobject-2.0.so.0
g_signal_handlers_disconnect_matched () from /usr/lib/libgobject-2.0.so.0
remove_pending (startup_data=0x94421e8, cancel_call_when_ready=0, cancel_timed_wait=1,
is_directory_ready_callback (file=0x92cc640, data=0x94421e8) at fm-properties-window.c:5347
ready_callback_call (directory=0x8966508, callback=0x9440718)

[Pedro Villavicencio (pedro)]

thanks for the report, trace looks like http://bugzilla.gnome.org/show_bug.cgi?id=543451, may you tell us a few easy steps in order to reproduce the crash? thanks.

[Popolon (popolon)]

Just crashed on Jaunty 64 bits, with the same error msg, bug report get me here, don't know how to attach new debug informations.

[Mazen (mezen)]

crash after upgrade from intrepid to jaunty beta and reboot. get the crash message after first jaunty session opening.

[Sebastien Bacher (seb128)]

could anybody try if that's still an issue in jaunty?

[Tomaso Bulligan (tomaso-bulligan)]

I filed my bug report from Jaunty. I don't remember what I did for it
to happen so I can't test if it has been fixed lately.

2009/6/10 Sebastien Bacher <email address hidden>:
> could anybody try if that's still an issue in jaunty?
>
> --
> nautilus crashed with SIGSEGV in g_type_check_instance()
> https://bugs.launchpad.net/bugs/285428
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Nautilus: Invalid
> Status in “nautilus” source package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: nautilus
>
> nautilus crashed with SIGSEGV in g_type_check_instance()
>
> ProblemType: Crash
> Architecture: i386
> DistroRelease: Ubuntu 8.10
> ExecutablePath: /usr/bin/nautilus
> Package: nautilus 1:2.24.0-0ubuntu2
> ProcAttrCurrent: unconfined
> ProcCmdline: nautilus --no-hostname --browser
> ProcEnviron:
>  PATH=/home/User Namename/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
>  LANG=en_US.UTF-8
>  SHELL=/bin/bash
> Signal: 11
> SourcePackage: nautilus
> StacktraceTop:
>  g_type_check_instance () from /usr/lib/libgobject-2.0.so.0
>  g_signal_handlers_disconnect_matched ()
>  ?? ()
>  ?? ()
>  ?? ()
> Title: nautilus crashed with SIGSEGV in g_type_check_instance()
> Uname: Linux 2.6.27-7-generic i686
> UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev root sambashare scanner tape video
>

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

We still need some steps to reproduce this from someone who got this crash. Thanks.

[Mathieu Marquer (slasher-fun)]

See duplicate bug https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/408987 for the steps to reproduce the bug.

[Pedro Villavicencio (pedro)]

Mathieu with those steps is not reproducible here with Karmic, could somebody add some easy steps to reproduce the issue with latest version on Karmic or Jaunty?

[Aold (theantoftheweb)]

I couldn't reproduce this bug with nautilus 2.27.4-0ubuntu5 (Karmic) but it still remains with nautilus 2.22.2-0ubuntu4 (Hardy) and nautilus 2.26.2-0ubuntu2 (JAUNTY).
I follow the steps I described here: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/408987.

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

Thank you Aold. Since we don't know which code change is responsible for the fix, there is no way to fix this in Hardy or Jaunty. Also we can't take the version from Karmic, because the gap between the two versions is too huge. Therefore I am closing this bug as "fix released".

[Ристе Ристевски (risteristevski)]

I had the same bug on Karmic.

[hassan121 (k7rata121)]

i had this bug on lucid.

[Karl Sam (karolus.magnus)]

it happened to me on Maverick. I will try to see if it's reproducible.