dring crashed with SIGSEGV in asn1_find_node()

Bug #1740820 reported by Anders Pamdal on 2018-01-02
This bug report is a duplicate of:  Edit Remove
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ring (Ubuntu)

Bug Description


ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: ring-daemon 20171129.2.cf5bbff~ds1-2
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
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
 PATH=(custom, no user)
 Segfault happened at: 0x7fc8a66f67b5 <asn1_find_node+181>: cmp %ebp,0x44(%rbx)
 PC (0x7fc8a66f67b5) ok
 source "%ebp" ok
 destination "0x44(%rbx)" (0x61666634633965a5) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: ring
 asn1_find_node () from /usr/lib/x86_64-linux-gnu/libtasn1.so.6
 gnutls_x509_crl_iter_crt_serial () from /usr/lib/x86_64-linux-gnu/libgnutls.so.30
 ?? () from /usr/lib/x86_64-linux-gnu/libgnutls.so.30
 gnutls_x509_trust_list_verify_crt2 () from /usr/lib/x86_64-linux-gnu/libgnutls.so.30
 ?? ()
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

Anders Pamdal (anders-pamdal) wrote :

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.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers