nautilus crashed with SIGSEGV in g_closure_invoke()

Bug #475943 reported by abg
48
This bug affects 9 people
Affects Status Importance Assigned to Milestone
Nautilus
Expired
Critical
nautilus (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: nautilus

-

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Fri Nov 6 01:37:19 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
Package: nautilus 1:2.28.1-0ubuntu1
ProcCmdline: nautilus --no-desktop computer:
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x813bca0: mov 0x1c(%eax),%eax
 PC (0x0813bca0) ok
 source "0x1c(%eax)" (0x0000001c) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 ?? ()
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_closure_invoke()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin audio cdrom fuse lpadmin netdev plugdev sambashare ssh users

Revision history for this message
abg (abghome) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:nautilus_icon_container_receive_dropped_icons (
drag_data_received_callback (widget=0x9c87000,
_gtk_marshal_VOID__OBJECT_INT_INT_BOXED_UINT_UINT (
g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
?? () from /usr/lib/libgobject-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in nautilus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at:
https://bugzilla.gnome.org/show_bug.cgi?id=600964

Changed in nautilus (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
status: New → Triaged
Revision history for this message
David Nielsen (davidnielsen-deactivatedaccount) wrote :

I found that you can reproduce this by using file-roller to unpack something. This will create a new folder into which the files will go during uncompressing. Attempting to open the folder at a time when it is still visible in nautilus but has been deleted by file-roller will trigger the crash. It is tricky to time but happens from time to time.

tags: added: lucid
Changed in nautilus:
status: Unknown → New
Changed in nautilus:
importance: Unknown → Critical
Changed in nautilus:
status: New → Expired
Revision history for this message
Sebastien Bacher (seb128) wrote :

there has been no such issue reported in years, assuming it doesn't exist in the current version of the code and closing

Changed in nautilus (Ubuntu):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.