*** This bug is a duplicate of bug 1861609 ***
https://bugs.launchpad.net/bugs/1861609
** This bug has been marked a duplicate of bug 1861609
Xorg crashed with assertion failure (usually in a VM) at
[privates.h:121/122: dixGetPrivateAddr: Assertion `key->initialized' failed]
and call
** Tags removed: eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745345
Title:
Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122:
dixGetPrivateAddr: Assertion `key->initialized'
** Changed in: xorg-server (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745345
Title:
Xorg assert failure: Xorg:
** Changed in: xorg-server (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745345
Title:
Xorg assert failure: Xorg:
Mikko,
Re comment #49, we already have that fix (see comment #46).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745345
Title:
Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122:
The (new??) problem with focal has moved to bug 1861609. So just about
everyone should probably use bug 1861609 now.
** Tags removed: champagne
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745345
What we should actually do is to distinguish the bugs by call stack, as
that will be a little different for each flavour of this crash.
Unfortunately several of the most recent reports (focal) have no call
stack at all. So separating them is not an option yet.
--
You received this bug
It's not clear what issue are still remaining on focal, might we worth
having a new report for that serie to not confuse with past problems
that got resolved. Tagging as rls-ff-notfixing meanwhile because it's
not clear how much that's still a problem on focal
** Tags removed: rls-ff-incoming
**
Norbert,
VAAPI may trigger this crash because it involves calling low-level
driver functions within Xorg. That does not make it a problem with any
VAAPI packages, but is still a bug in Xorg. Or multiple bugs in Xorg.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
It seems to me that fix
https://gitlab.freedesktop.org/xorg/xserver/-/commit/cfc5e5040c934 is
the correct one. Is it possible to reproduce the crash with that one
patch applied even without all the other proposed fixes?
--
You received this bug notification because you are a member of Ubuntu
For me the main question is - how installation of `gstreamer1.0-vaapi` leads to
crash?
And why purging of `gstreamer1.0-vaapi` helps to avoid the crash.
@Daniel van Vugt (vanvugt) did you tried to reproduce this crash?
--
You received this bug notification because you are a member of Ubuntu
Looks like we might need to split this into multiple bugs somehow,
because the same assertion has kept failing over the years and multiple
fixes have already been applied:
Fixed in 1.20.7:
https://gitlab.freedesktop.org/xorg/xserver/-/commit/cfc5e5040c934
Fixed in 1.20.1:
And more fixes are proposed in:
https://gitlab.freedesktop.org/xorg/xserver/-/issues/615
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745345
Title:
Xorg assert failure: Xorg:
It looks like there are two possible upstreams for this bug:
https://gitlab.freedesktop.org/xorg/xserver/-/issues/615
https://gitlab.freedesktop.org/xorg/xserver/-/issues/781
** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #615
** Changed in: gstreamer-vaapi (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745345
Title:
Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122:
Seeing this on Ubuntu MATE 20.04 LTS beta 20200402:
> fresh install using `[x] Install third-party software for graphics and
Wi-Fi hardware and additional media formats` on VirtualBox 5.1 leads to
crashes on VirtualBox 5.1.
** Changed in: gstreamer-vaapi (Ubuntu)
Status: Invalid =>
I would like to also mention that Ubuntu 20.04 Daily (not MATE) crashes
on Virtualbox and KVM and that, as mentioned previously, running `sudo
apt-get purge gstreamer1.0-vaapi` fixes the crash to login issue.
Another workaround is to use Ubuntu on Wayland but in Virtualbox no
mouse pointer is
Ubuntu MATE 20.04 2020315
QEMU: crash
VirtualBox VBoxVGA crash
VirtualBox VMSVGA: no crash
In this case VirtualBox 6.1.4 (version shipping in 20.04)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Still happens with Ubuntu MATE 20.04 LTS (20200313) using VirtualBox
5.1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745345
Title:
Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122:
Still happens with Ubuntu MATE 20.04 LTS (20200413) using VirtualBox
5.1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745345
Title:
Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122:
This continues to be an issue with Virt-Manager/QEMU with the 20200306
ISO of Ubuntu MATE and the 20200305 ISO of Ubuntu Budgie.
With VirtualBox 6.1.4 the following results occur:
1. Using VMSVGA there is no crash
2. Using VBoxSVGA the crash occurs.
--
You received this bug notification
@Bill (franksmcb) (franksmcb)
This is a bit broader. VirtualBox is still affected. I use 5.1 because
of 25 VMs inside it.
As I already wrote - see https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1796437/comments/16 :
> Norbert (nrbrtx) wrote on 2020-01-16
>
>Still reproducible on
This does occur with 20200216 ISO with Ubuntu MATE using Virt-
manager/QEMU, however this issue does not occur using VirtualBox.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745345
Title:
Xorg
** Changed in: xorg-server
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745345
Title:
Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122:
Also tracking (sounds closely related) in:
https://gitlab.freedesktop.org/xorg/xserver/issues/781
** Bug watch added: gitlab.freedesktop.org/xorg/xserver/issues #781
https://gitlab.freedesktop.org/xorg/xserver/issues/781
** Also affects: xorg-server via
This also happened on a 20.04 Xubuntu 64-bit VM in Qemu/KVM: Xorg
crashing at login, next login works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745345
Title:
Xorg assert failure: Xorg:
It is not appropriate to have a gstreamer-vaapi task here because
there's nothing you can do in that package that is an acceptable fix for
Xorg crashing. It's not a fix, it is a workaround.
If you remove "gstreamer1.0-vaapi", then that might be a good workaround
for some people. But no possible
Removing the package "gstreamer1.0-vaapi" solved the issue for me, too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745345
Title:
Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122:
@vanvugt, could you please elaborate why do you think that `gstreamer-
vaapi` is not related to this bug (or really bug 1796437).
I see that installation of the single `gstreamer1.0-vaapi` package make
system crash. While its uninstallation removes the crash. Just tested
20200203 MATE ISO.
Do
** No longer affects: gstreamer-vaapi (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745345
Title:
Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122:
dixGetPrivateAddr:
Please don't run apport-collect on bugs you don't own. Please also avoid
attaching crash files to bugs as we can't process them that way. You
should run this command to create a new bug for each crash file:
ubuntu-bug YOURFILE.crash
--
You received this bug notification because you are a
Crash on VirtualBox with `gstreamer1.0-vaapi` installed also is caused by:
`gnome-books`, `gnome-contacts`, `gnome-control-center`, `gnome-documents`,
`gnome-help`, `gnome-music`, `gnome-photo`, `gnome-sound-recorder`,
`gnome-subtitles`.
--
You received this bug notification because you are a
** Attachment added: "crash file from Ubuntu MATE 20.04 LTS with all updates on
start of Yelp"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1745345/+attachment/5321764/+files/_usr_lib_xorg_Xorg.0.crash
--
You received this bug notification because you are a member of Ubuntu
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: MATE
DistUpgraded: Fresh install
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gstreamer-vaapi (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745345
For original problem with Ubuntu MATE Welcome one can use crash file
from this link - https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1796437/+attachment/5319138/+files/_usr_lib_xorg_Xorg.0.crash
.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I need to recall that on QEMU/KVM (while using virt-manager the crashes
occur with Cirrus, QXL, VGA video drivers, but does not occur with VMVGA
video driver) and VirtualBox (tested all versions with default
`vboxvideo` driver) the crash is caused by `gstreamer-vaapi` package
(see
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1745345
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745345
Title:
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745345
Title:
Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122:
dixGetPrivateAddr:
This is actually the top Xorg crash in 20.04 but a glitch on our the
tracking site "errors.ubuntu.com" makes it unclickable and unusable :(
https://errors.ubuntu.com/?release=Ubuntu%2020.04=xorg-
server=year
** Tags added: focal
--
You received this bug notification because you are a member of
41 matches
Mail list logo
