nautilus crashed with SIGSEGV in g_type_check_instance()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu GNOME |
New
|
Undecided
|
Unassigned |
Bug Description
I use Ubuntu Gnome 15.10 64 bit, updated to Gnome 3.18 with the Gnome Staging PPA.
For some reason Nautilus crashed when I tried to open a file called Text.clu. There was no recommended application for it so I choose "View all applications" and selected one of two instances of gedit on the list (no idea why gedit was listed twice) and clicked Select. Gedit did not open, nothing seemed to happen until Nautilus crashed. Afterwards I got an error about Gedit not responding and later I got the crash report for Nautilus.
When I try to reproduce this Nautilus does not crash, but now Gedit is already selected as a recommended application, so I can't replicate everything I did the first time.
ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: nautilus 1:3.18.
ProcVersionSign
Uname: Linux 4.2.0-30-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Feb 28 23:18:55 2016
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
InstallationDate: Installed on 2015-12-30 (60 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcCmdline: /usr/bin/nautilus --gapplication-
SegvAnalysis:
Segfault happened at: 0x7f34ec65fe5c <g_type_
PC (0x7f34ec65fe5c) ok
source "$0x4" ok
destination "0x16(%rdx)" (0x6d75696d6f72
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
g_type_
g_signal_
g_signal_emit () from /usr/lib/
?? () from /usr/lib/
g_main_
Title: nautilus crashed with SIGSEGV in g_type_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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 #1542667, 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.