deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
deja-dup (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
during normal system operation
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: deja-dup 37.1-1fakesync1
ProcVersionSign
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Sun Feb 25 13:51:27 2018
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2017-04-01 (330 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170331)
ProcCmdline: /usr/lib/
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_
LANG=de_DE.UTF-8
LD_PRELOAD=<set>
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f437201c588: movl $0x0,(%rax)
PC (0x7f437201c588) 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: Upgraded to bionic on 2017-06-08 (262 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
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 #1751460, 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.