update-manager crashed with SIGSEGV

[radek]

update-manager[3484]: segfault at 3 ip 00007f2255cacbfb sp 00007f2241c52830 error 6 in libssl.so.1.1[7f2255c90000+60000]

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: update-manager 1:18.04.10
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 30 17:53:08 2018
ExecutablePath: /usr/bin/update-manager
GsettingsChanges:
 b'com.ubuntu.update-manager' b'show-details' b'true'
 b'com.ubuntu.update-manager' b'window-height' b'664'
 b'com.ubuntu.update-manager' b'first-run' b'false'
 b'com.ubuntu.update-manager' b'window-width' b'645'
 b'com.ubuntu.update-manager' b'launch-time' b'int64 1522425300'
InstallationDate: Installed on 2018-03-28 (1 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
InterpreterPath: /usr/bin/python3.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/bin/update-manager
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=cs_CZ.UTF-8
 SHELL=/bin/bash
Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
SegvAnalysis:
 Segfault happened at: 0x7f2255cacbfb: mov %al,(%rbx)
 PC (0x7f2255cacbfb) ok
 source "%al" ok
 destination "(%rbx)" (0x00000003) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: update-manager
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libssl.so.1.1
 ?? () from /usr/lib/x86_64-linux-gnu/libssl.so.1.1
 ?? () from /usr/lib/x86_64-linux-gnu/libssl.so.1.1
 ?? () from /usr/lib/x86_64-linux-gnu/libssl.so.1.1
 ?? () from /usr/lib/x86_64-linux-gnu/libssl.so.1.1
Title: update-manager crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 do_ssl3_write (s=s@entry=0x7f223c100700, type=type@entry=21, buf=0x7f223c0eb998 "\002\026", pipelens=pipelens@entry=0x7f2241c533f4, numpipes=numpipes@entry=1, create_empty_fragment=create_empty_fragment@entry=0) at ../ssl/record/rec_layer_s3.c:763
 ssl3_dispatch_alert (s=0x7f223c100700) at ../ssl/s3_msg.c:98
 ssl3_get_record (s=s@entry=0x7f223c100700) at ../ssl/record/ssl3_record.c:521
 ssl3_read_bytes (s=0x7f223c100700, type=23, recvd_type=0x0, buf=0x7f223c1137e0 "`\a", len=8192, peek=0) at ../ssl/record/rec_layer_s3.c:1055
 ssl3_read_internal (s=0x7f223c100700, buf=0x7f223c1137e0, len=8192, peek=0) at ../ssl/s3_lib.c:3840

[Launchpad Janitor (janitor)]

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