deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
deja-dup (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Difficult to know what happened. It was after a reboot on a 18.04 test computer.
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: deja-dup 37.1-1fakesync1
ProcVersionSign
Uname: Linux 4.15.0-10-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 2 11:28:59 2018
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2017-11-17 (104 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
JournalErrors:
Hint: You are currently not seeing messages from other users and the system.
Users in groups 'adm', 'systemd-journal' can see all messages.
Pass -q to turn off this notice.
-- Logs begin at Thu 2018-03-01 20:20:46 CET, end at Fri 2018-03-02 11:31:09 CET. --
mars 02 11:26:58 hostname pulseaudio[1513]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop
ProcCmdline: /usr/lib/
ProcEnviron:
PATH=(custom, user)
XDG_RUNTIME_
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f2222ec7588: movl $0x0,(%rax)
PC (0x7f2222ec7588) 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 2018-03-01 (0 days ago)
UserGroups: 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.