nautilus crashed with SIGSEGV in set_floating_bar_status()

Bug #929064 reported by Jendrik Seipp
118
This bug affects 14 people
Affects Status Importance Assigned to Milestone
Nautilus
Invalid
Critical
nautilus (Ubuntu)
Fix Released
High
Unassigned
Precise
Fix Released
High
Unassigned

Bug Description

Crashed ramdomly after no particular action.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.3.5-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-14.23-generic 3.2.3
Uname: Linux 3.2.0-14-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Wed Feb 8 20:31:59 2012
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
ProcCmdline: nautilus -n
SegvAnalysis:
 Segfault happened at: 0x7f6901a90d60 <g_type_check_instance_cast+16>: mov (%rdi),%rax
 PC (0x7f6901a90d60) ok
 source "(%rdi)" (0xaaaaaaaaaaaaaaaa) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? ()
 ?? ()
 ?? ()
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_type_check_instance_cast()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Jendrik Seipp (jendrikseipp) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_type_check_instance_cast (type_instance=0xaaaaaaaaaaaaaaaa, iface_type=25432272) at /build/buildd/glib2.0-2.31.16/./gobject/gtype.c:3993
 set_floating_bar_status (status=0x0, slot=0x2161380) at nautilus-window-slot.c:533
 nautilus_window_slot_set_status (slot=0x2161380, status=<optimized out>, short_status=0x0) at nautilus-window-slot.c:567
 nautilus_view_display_selection_info (view=0x1cd24f0) at nautilus-view.c:2948
 update_status_idle_callback (data=<optimized out>) at nautilus-view.c:8847

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in nautilus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, did that happen only once? What where you doing when it happened?

summary: - nautilus crashed with SIGSEGV in g_type_check_instance_cast()
+ nautilus crashed with SIGSEGV in set_floating_bar_status()
Changed in nautilus (Ubuntu):
importance: Medium → Low
status: New → Incomplete
Revision history for this message
Jendrik Seipp (jendrikseipp) wrote : Re: [Bug 929064] Re: nautilus crashed with SIGSEGV in set_floating_bar_status()

This happened only once. At the time I had two tabs open and was adding
and removing a USB Stick and an SD card, but I'm not sure what exactly
caused the error.

Changed in nautilus (Ubuntu):
status: Incomplete → New
importance: Low → High
status: New → Confirmed
Changed in nautilus (Ubuntu):
status: Confirmed → Triaged
Changed in nautilus:
importance: Unknown → Medium
status: Unknown → New
Revision history for this message
Christopher Kyle Horton (christhehorton) wrote :

Similar to #6, I got a dupe of this when I tried to Safely Remove my external USB HDD using the launcher quicklist. No Nautilus windows were open at the time of the crash.

Changed in nautilus:
importance: Medium → Critical
tags: added: bugpattern-needed
tags: added: rls-mgr-p-tracking
Revision history for this message
Sebastien Bacher (seb128) wrote :

upstream says it should be fixed with > 3.3.90 and indeed we didn't get duplicates since, closing the bug

Changed in nautilus (Ubuntu):
status: Triaged → Fix Released
Changed in nautilus (Ubuntu Precise):
status: Triaged → Fix Released
Changed in nautilus:
status: New → 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.