nautilus crashed with SIGSEGV in brasero_task_ctx_stop_progress()

Bug #1727362 reported by Barry Loram
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
brasero (Ubuntu)
New
Medium
Unassigned

Bug Description

No more info. Message on screen when I entered room.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: nautilus 1:3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Oct 25 15:17:40 2017
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2017-10-05 (20 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
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: 0x7fd162c68a6e <brasero_task_ctx_stop_progress+46>: mov 0x50(%rbx),%rdi
 PC (0x7fd162c68a6e) ok
 source "0x50(%rbx)" (0x00000050) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 brasero_task_ctx_stop_progress () from /usr/lib/x86_64-linux-gnu/libbrasero-burn3.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/libbrasero-burn3.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/libbrasero-burn3.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/libbrasero-burn3.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/libbrasero-burn3.so.1
Title: nautilus crashed with SIGSEGV in brasero_task_ctx_stop_progress()
UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago)
UserGroups: adm cdrom dip lpadmin mythtv plugdev sambashare sudo

Revision history for this message
Barry Loram (dreghorn67) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 brasero_task_ctx_stop_progress (self=0x5643692e1fa0) at burn-task-ctx.c:1025
 brasero_task_run_loop (error=0x7ffe215150f0, self=0x5643692e1fa0) at burn-task.c:466
 brasero_task_start_items (self=self@entry=0x5643692e1fa0, error=error@entry=0x7ffe215150f0) at burn-task.c:582
 brasero_task_start (self=0x5643692e1fa0, fake=fake@entry=0, error=error@entry=0x7ffe215150f0) at burn-task.c:623
 brasero_task_run (self=<optimized out>, error=error@entry=0x7ffe215150f0) at burn-task.c:682

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
information type: Private → Public
affects: nautilus (Ubuntu) → brasero (Ubuntu)
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.