on reboot after upgrade crash occured
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: deja-dup 37.1-1fakesync1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 5 11:46:28 2018
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
InstallationDate: Installed on 2017-06-06 (272 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
ProcEnviron:
LANGUAGE=de_AT:de
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=de_AT.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f242b05b588: movl $0x0,(%rax)
PC (0x7f242b05b588) 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:
() at /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
__pthread_once_slow (once_control=0x7f242b2c302c, init_routine=0x7f2422118490 <__once_proxy>) at pthread_once.c:116
Gigacage::ensureGigacage() () at /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
bmalloc::Heap::Heap(bmalloc::HeapKind, std::lock_guard<bmalloc::StaticMutex>&) () at /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
bmalloc::PerProcess<bmalloc::PerHeapKind<bmalloc::Heap> >::getSlowCase() () at /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
Title: deja-dup-monitor crashed with SIGSEGV
UpgradeStatus: Upgraded to bionic on 2018-02-12 (20 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.