VBoxClient crashed with SIGSEGV in XQueryExtension()

Bug #1872129 reported by Tony Middleton
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
virtualbox (Ubuntu)
New
Undecided
Unassigned

Bug Description

Received error message shortly after booting into Xubuntu 20.04 guest. Guest continued to work OK.

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: virtualbox-guest-x11 6.1.4-dfsg-2
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Fri Apr 10 20:21:57 2020
ExecutablePath: /usr/bin/VBoxClient
InstallationDate: Installed on 2020-04-10 (0 days ago)
InstallationMedia: Xubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1)
ProcCmdline: /usr/bin/VBoxClient --vmsvga-x11
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x7f5c6f14cb21 <XQueryExtension+49>: mov 0x968(%rdi),%rax
 PC (0x7f5c6f14cb21) ok
 source "0x968(%rdi)" (0x00000968) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: virtualbox
StacktraceTop:
 XQueryExtension () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XInitExtension () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XextAddDisplay () from /usr/lib/x86_64-linux-gnu/libXext.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libXrandr.so.2
 XRRQueryExtension () from /usr/lib/x86_64-linux-gnu/libXrandr.so.2
Title: VBoxClient crashed with SIGSEGV in XQueryExtension()
UpgradeStatus: Upgraded to focal on 2020-04-10 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
separator:

Revision history for this message
Tony Middleton (ximera) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #1864519, 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  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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