*** This bug is a duplicate of bug 1751460 ***
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
** Attachment removed: "CoreDump.gz"
** Attachment removed: "Disassembly.txt"
** Attachment removed: "ProcMaps.txt"
** Attachment removed: "ProcStatus.txt"
** Attachment removed: "Registers.txt"
** Attachment removed: "Stacktrace.txt"
** Attachment removed: "ThreadStacktrace.txt"
** This bug has been marked a duplicate of bug 1751460
deja-dup-monitor crashed with SIGSEGV in Gigacage::<lambda()>::operator()
** Information type changed from Private to Public
** Tags removed: need-amd64-retrace
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
deja-dup-monitor crashed with SIGSEGV
Status in deja-dup package in Ubuntu:
The system was subsequently upgraded by apt-get dist-upgrade during two or
three month from Ubuntu 17.04LTS to the last available Bionic Beaver
development branch. Had to upgrade due to some package I was unable to run
under LTS and it was OK under newer distributives.
At a beginning of February 2018 I've started to get different crashes.
Meanwhile, another operational system on the same laptop is OK, none crashes.
The current report is about new type of a crash I've never seen before.
DistroRelease: Ubuntu 18.04
Package: deja-dup 37.1-1fakesync1
ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
Uname: Linux 4.15.0-11-generic x86_64
Date: Sun Mar 4 11:09:32 2018
Segfault happened at: 0x7f38036c6588: movl $0x0,(%rax)
PC (0x7f38036c6588) ok
source "$0x0" ok
destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed
SegvReason: writing unknown VMA
init_routine=0x7f37fa783490 <__once_proxy>) at pthread_once.c:116
Gigacage::ensureGigacage() () at
std::lock_guard<bmalloc::StaticMutex>&) () at
bmalloc::PerProcess<bmalloc::PerHeapKind<bmalloc::Heap> >::getSlowCase() ()
Title: deja-dup-monitor crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin microchip plugdev sambashare sudo
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~desktop-packages
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp