nautilus crashed with SIGSEGV in g_type_check_instance()

Bug #447459 reported by LavianoTS386
222
This bug affects 33 people
Affects Status Importance Assigned to Milestone
Nautilus
Expired
Critical
nautilus (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: nautilus

I got some permissions problems for seemingly no reason.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Fri Oct 9 14:18:56 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: nvidia
Package: nautilus 1:2.28.0-0ubuntu5
ProcCmdline: nautilus
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-12.41-generic
SegvAnalysis:
 Segfault happened at: 0x7f0729ae2665 <g_type_check_instance+21>: mov (%rax),%rdi
 PC (0x7f0729ae2665) ok
 source "(%rax)" (0x00000074) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_type_check_instance ()
 g_signal_connect_data ()
 ?? ()
 ?? ()
 ?? ()
Title: nautilus crashed with SIGSEGV in g_type_check_instance()
Uname: Linux 2.6.31-12-generic x86_64
UserGroups: adm admin audio cdrom dialout fuse lpadmin netdev plugdev vboxusers video

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

StacktraceTop:g_type_check_instance ()
g_signal_connect_data ()
set_pending_icon_to_reveal (container=0x26e0020,
end_renaming_mode (container=0x26e0020, commit=1)
key_press_event (widget=0x26e0020, event=0x2854660)

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

Thanks for the report, it looks like bug https://bugzilla.gnome.org/show_bug.cgi?id=452894, commenting upstream now.

Changed in nautilus (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
status: New → Triaged
visibility: private → public
Changed in nautilus:
status: Unknown → New
Changed in nautilus:
importance: Unknown → Critical
tags: added: bugpattern-needed
tags: added: precise
tags: added: saucy
tags: added: trusty
Changed in nautilus:
status: New → Incomplete
tags: added: vivid
Changed in nautilus:
status: Incomplete → Expired
tags: added: wily
Revision history for this message
Cysioland (cysioland) wrote :

Happened to me when I created a new folder and typed in its name.

tags: added: xenial
Revision history for this message
Sebastien Bacher (seb128) wrote :

The bug is quite old and the code changed since, also there has been no new report of that specific problem nor activity for some years so assuming it has been resolved and closing the ticket. If you still get issues in newer versions feel free to open a new report though.

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.

Other bug subscribers

Remote bug watches

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