[nouveau] Xorg crashes with assertion failure "key->initialized" in dixGetPrivateAddr() from dixLookupPrivate() from DRI2Authenticate()

Bug #1796437 reported by David F Muller
42
This bug affects 8 people
Affects Status Importance Assigned to Milestone
gstreamer-vaapi (Ubuntu)
Confirmed
Undecided
Unassigned
xorg-server (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Went to the menu button in upper left corner. Attempted to open Budgie Welcome and the X11 session crashed. About 4 lines of error code were displayed for a few seconds then the login screen appeared.

Description: Ubuntu Cosmic Cuttlefish (development branch)
Release: 18.10
budgie-welcome:
  Installed: (none)
  Candidate: 0.6.1
  Version table:
     0.6.1 500
        500 http://us.archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages
        500 http://us.archive.ubuntu.com/ubuntu cosmic/universe i386 Packages

Seems to not be installed on a fresh install. So solved but needs fixing?

ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: xserver-xorg-core 2:1.20.1-3ubuntu2
ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
Uname: Linux 4.18.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
AssertionMessage: Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed.
BootLog:
 [ OK ] Stopped Snappy daemon.
          Starting Snappy daemon...
CompositorRunning: None
CrashCounter: 1
Date: Fri Oct 5 20:36:30 2018
DistUpgraded: Fresh install
DistroCodename: cosmic
DistroVariant: ubuntu
ExecutablePath: /usr/lib/xorg/Xorg
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
InstallationDate: Installed on 2018-10-06 (0 days ago)
InstallationMedia: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181005)
MachineType: System manufacturer System Product Name
ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
ProcEnviron: PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=21545d40-8bcb-45b5-b710-8521590b95a5 ro quiet splash vt.handoff=1
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
 __GI_abort () at abort.c:79
 __assert_fail_base (fmt=0x7f29afb85858 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, function=<optimized out>) at assert.c:92
 __GI___assert_fail (assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, function=0x55c50dccc0c0 "dixGetPrivateAddr") at assert.c:101
 ?? ()
Title: Xorg assert failure: Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 03/14/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1301
dmi.board.asset.tag: Default string
dmi.board.name: MAXIMUS IX FORMULA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSIXFORMULA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.94-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.1-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

Revision history for this message
David F Muller (dreamingwolf) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
 __GI_abort () at abort.c:79
 __assert_fail_base (fmt=0x7f29afb85858 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, function=<optimized out>) at assert.c:92
 __GI___assert_fail (assertion=assertion@entry=0x55c50dca64bb "key->initialized", file=file@entry=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=line@entry=121, function=function@entry=0x55c50dccc0c0 <__PRETTY_FUNCTION__.13800> "dixGetPrivateAddr") at assert.c:101
 dixGetPrivateAddr (key=<optimized out>, key=<optimized out>, privates=0x55c50f7ba1d0) at ../../../../../../include/privates.h:121

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in xorg-server (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Steve Beattie (sbeattie)
information type: Private → Public
Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: X11 crashed when attempting to open Budgie Welcome

Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.

Changed in xorg-server (Ubuntu):
status: New → Won't Fix
Revision history for this message
Norbert (nrbrtx) wrote :

Got this bug on clean installation of Ubuntu MATE 20.04 LTS (http://cdimage.ubuntu.com/ubuntu-mate/daily-live/current/ , SHA256 = db76f02f944bad2b713f49bc5d8f15f1e4a4da819e11053de99175d849c4b6a6 ) inside Oracle VM VirtualBox 5.1.38 (Ubuntu 16.04.6 LTS MATE as host).

tags: added: focal
Revision history for this message
Norbert (nrbrtx) wrote :
no longer affects: ubuntu-mate-meta (Ubuntu)
Revision history for this message
Norbert (nrbrtx) wrote :

The Xorg crash is fixable by preventing the start of Ubuntu MATE Welcome (I did it by removing whole Snap functionality with `sudo apt purge snapd`).

summary: - X11 crashed when attempting to open Budgie Welcome
+ X11 crashed when attempting to open Budgie and MATE Welcome
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote : Re: X11 crashed when attempting to open Budgie and MATE Welcome

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/1796437

tags: added: iso-testing
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Norbert,

I can't tell for sure if that crash is the same as this one because it's missing line number debug info. Please turn your crash file (and future ones) into a new bug by running:

  ubuntu-bug YOURFILE.crash

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in ubuntu-mate-meta (Ubuntu):
status: New → Confirmed
Changed in ubuntu-mate-welcome (Ubuntu):
status: New → Confirmed
Revision history for this message
Norbert (nrbrtx) wrote :

@Daniel van Vugt (vanvugt)

`apport-bug /var/crash/_usr_lib_xorg_Xorg.0.crash` says that the problem is already known and redirects me here, to this bug report. So I can't report the problem as new bug. If you are interested, please parse/unpack crash file above in comment 8.

Installing proposed updates does not change the situation.

Revision history for this message
Bill (franksmcb) (franksmcb) wrote :

@Norbert I am not seeing this with the 20200114 build. I'm running this in VirtualBox 5.2.34

Revision history for this message
Norbert (nrbrtx) wrote :

Still reproducible on 20200115 and 20200116 builds.

---

Reproducible method 1:

1. boot installation media
2. select [o] Normal installation, [x] Download updates, [x] Install third-party software
3. Wait installation to finish
4. Boot the installed system, wait for Snappy unpacking/initialization/seeding (check from tty1 with `snap list`)
5. Login to desktop session
6. Get crash of whole Xorg after login when of Ubuntu MATE Welcome window is starting to appear.

Reproducible method 2:

1. boot installation media
2. select [o] Normal installation, [ ] Download updates, [ ] Install third-party software
3. Wait installation to finish
4. Boot the installed system, wait for Snappy unpacking/initialization/seeding (check from tty1 with `snap list`)
5. Install Ubuntu restricted extras with `sudo apt-get install ubuntu-restricted-extras` and reboot
6. Login to desktop session
7. Get crash of whole Xorg after login when of Ubuntu MATE Welcome window is starting to appear.

Guest settings: choosing video acceleration disabled or 3d video acceleration does not change behavior. Increasing VRAM from default 16 Mb to 128 Mb (max for my machine) does not help either.
VirtualBox versions tested:

* 5.1.38-dfsg-0ubuntu1.16.04.3 (from multiverse) - crash,
* 5.0.40 (from Oracle) - crash,
* 5.1.38 (from Oracle) - crash,
* 5.2.36 (from Oracle) - crash,
* 6.0.16 (from Oracle) - crash,
* 6.1.2 (from Oracle) - crash.

---

Removing `ubuntu-mate-welcome` from autostart with `sudo rm /etc/xdg/autostart/ubuntu-mate-welcome-autostart.desktop` fixes the login issue. But direct launch of it with `ubuntu-mate-welcome` ends with another crash.

Revision history for this message
Norbert (nrbrtx) wrote :

With virt-manager the crashes occur with Cirrus, QXL, VGA video drivers.
But does not occur with VMVGA video driver.
Possibly kernel (drm) issue.

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Norbert (nrbrtx)
Changed in ubuntu-mate-meta (Ubuntu):
status: Confirmed → Invalid
Changed in ubuntu-mate-welcome (Ubuntu):
status: Confirmed → Invalid
Changed in linux (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Norbert (nrbrtx) wrote : Re: X11 crashed when attempting to open Budgie and MATE Welcome

I found the real reason for the crashes. The problematic package is the `gstreamer1.0-vaapi` (see https://packages.ubuntu.com/focal/gstreamer1.0-vaapi).
It is a dependency of `ubuntu-restricted-addons` (see https://packages.ubuntu.com/focal/ubuntu-restricted-addons).

So ubuntu-mate-welcome and for example Cheese may be fixed by removing this package with

```
sudo apt-get purge gstreamer1.0-vaapi
sudo apt-get autoremove --purge # to remove libgstreamer-plugins-bad1.0-0 (is not a problem)
```

So please carefully analyze the crash dumps for errors in `gstreamer1.0-vaapi` and fix this package.

Norbert (nrbrtx)
summary: - X11 crashed when attempting to open Budgie and MATE Welcome
+ X11 crashed when attempting to open GtkWebKit- and gstreamer-based
+ applications (as Yelp, Cheese, Budgie and MATE Welcome)
Revision history for this message
Norbert (nrbrtx) wrote : Re: X11 crashed when attempting to open GtkWebKit- and gstreamer-based applications (as Yelp, Cheese, Budgie and MATE Welcome)

The issue is more generic - Yelp and Cheese crash in the VirtualBox on MATE, Xfce, Budgie and GNOME FlashBack (metacity) sessions.

tags: added: nouveau
summary: - X11 crashed when attempting to open GtkWebKit- and gstreamer-based
- applications (as Yelp, Cheese, Budgie and MATE Welcome)
+ [nouveau] X11 crashed when attempting to open GtkWebKit- and gstreamer-
+ based applications (as Yelp, Cheese, Budgie and MATE Welcome)
summary: - [nouveau] X11 crashed when attempting to open GtkWebKit- and gstreamer-
- based applications (as Yelp, Cheese, Budgie and MATE Welcome)
+ [nouveau] Xorg crashes with assertion failure "key->initialized" in
+ dixGetPrivateAddr() from dixLookupPrivate() from DRI2Authenticate()
tags: removed: cosmic
Changed in xorg-server (Ubuntu):
status: Won't Fix → Confirmed
no longer affects: gstreamer-vaapi (Ubuntu)
no longer affects: linux (Ubuntu)
no longer affects: ubuntu-mate-meta (Ubuntu)
no longer affects: ubuntu-mate-welcome (Ubuntu)
Revision history for this message
Eric Adams (esa1975) wrote :

I run into this on Ubuntu Budgie 20.04 when trying to open GNOME Settings. It dumps me to to the login screen. I just tried to use About and it did the same thing. This is in a VirtualBox virtual machine if that is relevant. Happy to provide additional detail if needed. Thanks for looking into this.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gstreamer-vaapi (Ubuntu):
status: New → Confirmed
Revision history for this message
Briggs (jba1978) wrote :

Unable to log in to Xorg session. I got dumped back to the login screen.
I was able to log in using Wayland.
I did a full update in CLI but was still unable to successfully log in to Xorg.
Running on KVM/virt-manager

Revision history for this message
Norbert (nrbrtx) wrote :

Still happens with Ubuntu MATE 20.04 LTS (20200313) using VirtualBox 5.1.

Revision history for this message
Luis Felipe Lemos Forman (lipe66) wrote :

This is still happening in Ubuntu Budgie 20.04 on virt-maneger VM on latest daily.

Revision history for this message
Norbert (nrbrtx) wrote :

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.

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.