nemo crashed when I clicked on the drive corresponding to my phone (connected via USB)
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: nemo 2.8.6-2
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Tue May 3 12:13:10 2016
ExecutablePath: /usr/bin/nemo
ProcCmdline: nemo
ProcEnviron:
PATH=(custom, user)
SHELL=/bin/bash
LANG=en_US.UTF-8
LANGUAGE=en_US
XDG_RUNTIME_DIR=<set>
SegvAnalysis:
Segfault happened at: 0x494654: movq $0x0,0x50(%rax)
PC (0x00494654) ok
source "$0x0" ok
destination "0x50(%rax)" (0x65745f656d696cb2) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: nemo
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
g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: nemo crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to xenial on 2016-04-25 (8 days ago)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers
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 #1545800, 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.