nautilus crashed with SIGABRT in g_assertion_message()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
seems that a network share on a heavily IO bound ZFS-backed freenas share (it's either cifs or afp, nautilus doesn't tell me which, so I assume it's cifs) causes 100% cpu load followed by nautilus crashes if the share becomes unresponsive while mounted using gvfs.
if it is indeed accessing via cifs then the backend is samba4 acting as a Domain Controller.
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: nautilus 1:3.10.1-0ubuntu4
ProcVersionSign
Uname: Linux 3.13.0-11-generic x86_64
NonfreeKernelMo
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Feb 25 00:32:15 2014
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
InstallationDate: Installed on 2014-02-24 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
ProcCmdline: nautilus -n
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, user)
XDG_RUNTIME_
LANG=en_GB.UTF-8
SHELL=/bin/bash
Signal: 6
SourcePackage: nautilus
StacktraceTop:
g_assertion_
g_assertion_
?? ()
?? ()
?? () from /usr/lib/
Title: nautilus crashed with SIGABRT in g_assertion_
UpgradeStatus: Upgraded to trusty on 2014-02-24 (0 days ago)
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 #1202159, 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.