vino-server crashed with SIGSEGV in _XSend()

Bug #1764149 reported by Tom Lorenzen
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
vino (Ubuntu)
New
Undecided
Unassigned

Bug Description

Ubuntu 18.04 relogged to switch from wayland back to Xorg then all of the sudden the bug report came up, i don't know what happened exactly

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: vino 3.22.0-3ubuntu1
Uname: Linux 4.16.2-041602-generic x86_64
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 15 17:41:09 2018
ExecutablePath: /usr/lib/vino/vino-server
InstallationDate: Installed on 2018-04-06 (9 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
ProcCmdline: /usr/lib/vino/vino-server
ProcEnviron:
 LANG=de_DE.UTF-8
 PATH=(custom, user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x7f2f2ea233ce <_XSend+126>: mov (%rax),%rdx
 PC (0x7f2f2ea233ce) ok
 source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: vino
StacktraceTop:
 _XSend () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XQueryExtension () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libXtst.so.6
 XTestQueryExtension () from /usr/lib/x86_64-linux-gnu/libXtst.so.6
 ?? ()
Title: vino-server crashed with SIGSEGV in _XSend()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

Revision history for this message
Tom Lorenzen (to-lorenzen) 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 #1724572, 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.