nautilus crashed with SIGSEGV in nautilus_list_view_dnd_drag_begin()

Bug #1847098 reported by Brinstar
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Low
Unassigned

Bug Description

ubuntu 19.10 beta
nautilus crashed while operating on several files in tree view

ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: nautilus 1:3.34.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 7 15:06:23 2019
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2019-08-03 (65 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcCmdline: /usr/bin/nautilus --gapplication-service
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, user)
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
SegvAnalysis:
 Segfault happened at: 0x56257fbf8bfc <nautilus_list_view_dnd_drag_begin+204>: movl $0x2e,0x58(%rdx)
 PC (0x56257fbf8bfc) ok
 source "$0x2e" ok
 destination "0x58(%rdx)" (0x00000058) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 nautilus_list_view_dnd_drag_begin ()
 () at /lib/x86_64-linux-gnu/libgtk-3.so.0
 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in nautilus_list_view_dnd_drag_begin()
UpgradeStatus: Upgraded to eoan on 2019-09-27 (9 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
separator:

usr_lib_nautilus:

Revision history for this message
Brinstar (brinstar) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 nautilus_list_view_dnd_drag_begin (list_view=0x562582e72350, offset_x=<optimized out>, offset_y=<optimized out>, event=0x7fcc10032f10) at ../src/nautilus-list-view-dnd.c:296
 _gtk_marshal_VOID__DOUBLE_DOUBLEv (closure=<optimized out>, return_value=<optimized out>, instance=<optimized out>, args=<optimized out>, marshal_data=<optimized out>, n_params=<optimized out>, param_types=0x5625828784c0) at gtkmarshalers.c:2982
 _g_closure_invoke_va () from /tmp/apport_sandbox_0lh3kzt0/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.6200.0
 g_signal_emit_valist () from /tmp/apport_sandbox_0lh3kzt0/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.6200.0
 g_signal_emit () from /tmp/apport_sandbox_0lh3kzt0/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.6200.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 nautilus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, could you also submit the issue upstream on https://gitlab.gnome.org/GNOME/nautilus/issues/ ?

information type: Private → Public
Changed in nautilus (Ubuntu):
importance: Medium → Low
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.