Supply a link! I like many others offered to help. I'm suddenly getting
emails that I might have inadvertently signed up for, but lacks specificity
in how to respond. May I suggest you find a way to link these responses to
your "page" wherever that is? Or do I just block the incoming emails?

On Tue, Mar 13, 2018 at 10:31 PM, Jeremy Bicha <email address hidden> wrote:

> Please do not add comments here saying that you are affected by this
> bug.
>
> Instead, you can click the button at the top of this page that says
> "This bug affects ___ people".
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1753122).
> https://bugs.launchpad.net/bugs/1751460
>
> Title:
>   [regression] deja-dup-monitor crashed with SIGSEGV in
>   Gigacage::<lambda()>::operator()
>
> Status in Déjà Dup:
>   New
> Status in WebKit:
>   Confirmed
> Status in deja-dup package in Ubuntu:
>   Confirmed
> Status in webkit2gtk package in Ubuntu:
>   Confirmed
> Status in deja-dup source package in Bionic:
>   Confirmed
> Status in webkit2gtk source package in Bionic:
>   Confirmed
>
> Bug description:
>   https://errors.ubuntu.com/problem/27441b78823246dd5392ee29ac3054
> 6f6464289e
>
>   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
>   CrashCounter: 1
>   CurrentDesktop: GNOME
>   Date: Sat Feb 24 14:30:47 2018
>   ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
>   InstallationDate: Installed on 2017-12-27 (59 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64
> (20171018)
>   ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
>   ProcEnviron:
>    PATH=(custom, no user)
>    XDG_RUNTIME_DIR=<set>
>    LANG=de_DE.UTF-8
>    SHELL=/bin/bash
>   SegvAnalysis:
>    Segfault happened at: 0x7ff1c3dda588:        movl   $0x0,(%rax)
>    PC (0x7ff1c3dda588) 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/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
>    __pthread_once_slow (once_control=0x7ff1c404202c,
> init_routine=0x7ff1baec0490 <__once_proxy>) at pthread_once.c:116
>    Gigacage::ensureGigacage() () from /usr/lib/x86_64-linux-gnu/
> libjavascriptcoregtk-4.0.so.18
>    bmalloc::Heap::Heap(bmalloc::HeapKind, std::lock_guard<bmalloc::StaticMutex>&)
> () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
>    bmalloc::PerProcess<bmalloc::PerHeapKind<bmalloc::Heap>
> >::getSlowCase() () from /usr/lib/x86_64-linux-gnu/
> libjavascriptcoregtk-4.0.so.18
>   Title: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()
>   UpgradeStatus: Upgraded to bionic on 2018-02-24 (0 days ago)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/deja-dup/+bug/1751460/+subscriptions
>



-- 
stephen saines
cell  647 631 0711