Ubuntu
nautilus package

nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__POINTER()

Bug #284610 reported by PAceyIV on 2008-10-16

This bug affects 3 people

Affects		Status	Importance	Assigned to	Milestone
	Nautilus	Expired	Critical	gnome-bugs #556775
	nautilus (Ubuntu)	Invalid	Medium	Unassigned

Bug Description

Binary package hint: nautilus

Description: Ubuntu intrepid (development branch)
Release: 8.10

nautilus:
  Installato: 1:2.24.0-0ubuntu2
  Candidato: 1:2.24.0-0ubuntu2
  Tabella versione:
*** 1:2.24.0-0ubuntu2 0
        500 http://it.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

I try to open a new windows on a bookmark to a FTP server (with login) in nautilus and all my nautilus windows are crashed!

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/nautilus
Package: nautilus 1:2.24.0-0ubuntu2
ProcAttrCurrent: unconfined
ProcCmdline: nautilus --no-desktop --browser
ProcEnviron:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=it_IT.UTF-8
SHELL=/bin/bash
Signal: 11
SourcePackage: nautilus
StacktraceTop:
?? ()
?? ()
?? ()
g_cclosure_marshal_VOID__POINTER ()
g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__POINTER()
Uname: Linux 2.6.27-7-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

PAceyIV (paceynet) wrote on 2008-10-16:

Dependencies.txt Edit (6.3 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (583 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (41.9 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (777 bytes, text/plain; charset="utf-8")
Registers.txt Edit (455 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (3.0 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2008-10-16: Symbolic stack trace

Stacktrace.txt (retraced) Edit (8.1 KiB, text/plain)

StacktraceTop:destroy_node_without_reporting (model=0xa18e810, node=0xa27d478) at fm-tree-model.c:755
destroy_node (model=0xa18e810, node=0xa27d478) at fm-tree-model.c:775
files_changed_callback (directory=0xb5e1ff30, changed_files=0xbf841e74,
IA__g_cclosure_marshal_VOID__POINTER (closure=0xa19a3c8, return_value=0x0,
IA__g_closure_invoke (closure=0xa19a3c8, return_value=0x0, n_param_values=2,

Revision history for this message

Apport retracing service (apport) wrote on 2008-10-16: Symbolic threaded stack trace

ThreadStacktrace.txt (retraced) Edit (14.7 KiB, text/plain)

Changed in nautilus:
importance:	Undecided → Medium

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2008-10-17:

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=556775

Changed in nautilus:
assignee:	nobody → desktop-bugs
status:	New → Triaged

Bug Watch Updater (bug-watch-updater) on 2008-10-17

Changed in nautilus:
status:	Unknown → New

Bug Watch Updater (bug-watch-updater) on 2010-09-16

Changed in nautilus:
importance:	Unknown → Critical

Bug Watch Updater (bug-watch-updater) on 2011-04-07

Changed in nautilus:
status:	New → Expired

Revision history for this message

Barry Drake (b-drake) wrote on 2011-12-23:

Occurred consequent to crash of gnome settings daemon in Precise.

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2018-03-13:

Thank you for reporting this bug to Ubuntu.
Ubuntu 8.10 (intrepid) reached end-of-life on April 30, 2010.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.