Ubuntu
nemo package

nemo crashed with SIGSEGV in on_menu_destroyed()

Bug #1545800 reported by Lonnie Lee Best
92
This bug affects 18 people
Affects Status Importance Assigned to Milestone
nemo (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

When I received this crash notification, I had just gotten through cutting and pasting 2 files. One file was very small, and the other was around 17gigs. At around the same time I deleted 2 other file (around the same size for each) and emptied the trash using the trash icon on Ubuntu's launcher bar. This all I can say.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: nemo 2.8.6-2
ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1
Uname: Linux 4.4.0-4-generic x86_64
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Feb 15 11:11:48 2016
ExecutablePath: /usr/bin/nemo
InstallationDate: Installed on 2016-02-10 (4 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
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)" (0x7f4d1141d270) in non-writable VMA region: 0x7f4d11404000-0x7f4d11456000 r-xp /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.4705.0
SegvReason: writing VMA /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.4705.0
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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Lonnie Lee Best (launchpad-startport) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 on_menu_destroyed (widget=0x1554380, view=0x13bcc80) at nemo-view.c:6653
 g_closure_invoke () from /tmp/apport_sandbox_3vq7u5/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 signal_emit_unlocked_R () from /tmp/apport_sandbox_3vq7u5/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /tmp/apport_sandbox_3vq7u5/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /tmp/apport_sandbox_3vq7u5/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in nemo (Ubuntu):
importance: Undecided → Medium
summary: - nemo crashed with SIGSEGV in g_closure_invoke()
+ nemo crashed with SIGSEGV in on_menu_destroyed()
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nemo (Ubuntu):
status: New → Confirmed
Revision history for this message
Lonnie Lee Best (launchpad-startport) wrote :

I submitted this bug back in February.

I'm still seeing this crash almost every time I attempt to close nemo.

Andreas Moog (ampelbein)
information type: Private → Public
Revision history for this message
robin (robinp) wrote :

Is anyone investigating this bug?

If not, any suggestions where to start?

Revision history for this message
robin (robinp) wrote :

This will not be fixed upstream, authors are not interested and have moved to v3.4

https://github.com/linuxmint/nemo/issues/941

It is not supported by Canonical, so perhaps time to move to a later version.

Revision history for this message
Fantu (fantonifabio) wrote :

this seems solved in newer nemo, is there someone that still reproduce it in nemo version of bionic?

Revision history for this message
Lonnie Lee Best (launchpad-startport) wrote :

16.04.5 was recently released, but this bug still remains.

Revision history for this message
Fantu (fantonifabio) wrote :

this is solved in nemo 3.0 with:
https://github.com/linuxmint/nemo/commit/fb97b62aad23bb44820713c8084785bbc147bfd7

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.