deja-dup-monitor crashed with SIGSEGV

Bug #1753279 reported by nabin
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
deja-dup (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

ubuntu bionic beaver .
I get this error but don't know why because I don't use deja-dup.
I've got this a multiple times after logging in to my system

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: deja-dup 37.1-1fakesync1
Uname: Linux 4.15.7-041507-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Sun Mar 4 22:58:40 2018
ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
SegvAnalysis:
 Segfault happened at: 0x7fcdf71eb588: movl $0x0,(%rax)
 PC (0x7fcdf71eb588) 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=0x7fcdf745302c, init_routine=0x7fcdee2a8490 <__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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo

Revision history for this message
nabin (nabin6707-7) wrote :
information type: Private → Public Security
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in deja-dup (Ubuntu):
status: New → Confirmed
information type: Public Security → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.