nautilus crashed with SIGSEGV in g_type_check_instance_cast()

Bug #1056130 reported by Mike Williamson
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Undecided
Unassigned

Bug Description

Nautilus crashed just after login. Nothing else was happening at the time.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
Uname: Linux 3.5.0-15-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
Date: Tue Sep 25 07:18:28 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'geometry' b"'687x550+1912+298'"
 b'org.gnome.nautilus.window-state' b'maximized' b'true'
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
ProcCmdline: nautilus -n
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7ffa7d65ae8c <g_type_check_instance_cast+28>: mov (%rax),%rbp
 PC (0x7ffa7d65ae8c) ok
 source "(%rax)" (0x700000008) not located in a known VMA region (needed readable region)!
 destination "%rbp" 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
 ?? () from /usr/lib/x86_64-linux-gnu/libdbusmenu-gtk3.so.4
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_type_check_instance_cast()
UpgradeStatus: Upgraded to quantal on 2012-09-07 (18 days ago)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev postgres sambashare sudo wireshark

Revision history for this message
Mike Williamson (sleepycat) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Possible regression detected

This crash has the same stack trace characteristics as bug #1053670. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.

tags: added: regression-retracer
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1053670, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-amd64-retrace
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.