nautilus crashed with SIGSEGV in g_closure_invoke()

Bug #1427843 reported by Alexander Vinbæk Strand
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu GNOME
New
Undecided
Unassigned

Bug Description

nautilus crashed with SIGSEGV in g_closure_invoke()

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: nautilus 1:3.14.1-0ubuntu1~utopic1 [origin: LP-PPA-gnome3-team-gnome3-staging]
ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
Uname: Linux 3.16.0-31-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Tue Mar 3 20:38:34 2015
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:

InstallationDate: Installed on 2015-02-23 (8 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
ProcCmdline: nautilus -n
ProcEnviron:
 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=nb_NO.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x47a7a9: cmp %rax,(%rdx)
 PC (0x0047a7a9) ok
 source "%rax" ok
 destination "(%rdx)" (0x747265632d377363) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 ?? ()
 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_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

Revision history for this message
Alexander Vinbæk Strand (alexstrand7-o) wrote :
Revision history for this message
Ubuntu GNOME (ug-bot) 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 #1406775, 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.

information type: Private → Public
tags: removed: need-amd64-retrace
Revision history for this message
Alexander Vinbæk Strand (alexstrand7-o) wrote :

I can't open the other bug report.

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.