deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
deja-dup (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
On restart after update and upgrade .
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: deja-dup 37.1-2fakesync1
ProcVersionSign
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: MATE
Date: Tue Apr 3 12:31:18 2018
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2017-12-23 (100 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219)
ProcCmdline: /usr/lib/
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
XDG_RUNTIME_
LANG=pt_BR.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f8e190220a8: movl $0x0,(%rax)
PC (0x7f8e190220a8) ok
source "$0x0" ok
destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: deja-dup
StacktraceTop:
?? () from /usr/lib/
__pthread_
Gigacage:
bmalloc:
bmalloc:
Title: deja-dup-monitor crashed with SIGSEGV in __pthread_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip kvm lpadmin plugdev sambashare sudo vboxusers
This crash has the same stack trace characteristics as bug #1751460. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.