dring crashed with SIGSEGV in asn1_find_node()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ring (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
...
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: ring-daemon 20171129.
ProcVersionSign
Uname: Linux 4.13.0-19-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.8-0ubuntu5
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 2 06:19:38 2018
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/ring/dring
InstallationDate: Installed on 2017-09-13 (110 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170815)
ProcCmdline: /usr/lib/ring/dring
ProcEnviron:
XDG_RUNTIME_
SHELL=/bin/bash
PATH=(custom, no user)
LANG=sv_SE.UTF-8
SegvAnalysis:
Segfault happened at: 0x7fc8a66f67b5 <asn1_find_
PC (0x7fc8a66f67b5) ok
source "%ebp" ok
destination "0x44(%rbx)" (0x616666346339
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: ring
StacktraceTop:
asn1_find_node () from /usr/lib/
gnutls_
?? () from /usr/lib/
gnutls_
?? ()
Title: dring crashed with SIGSEGV in asn1_find_node()
UpgradeStatus: Upgraded to bionic on 2017-12-19 (14 days ago)
UserGroups: adm cdrom dip lpadmin 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 #1738915, 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.