Bug 1192127 - gdm failure: swrast_dri.so: undefined symbol: _glapi_tls_Dispatch
Summary: gdm failure: swrast_dri.so: undefined symbol: _glapi_tls_Dispatch
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: gdm
Version: 21
Hardware: i686
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-12 16:29 UTC by Jeff Hardy
Modified: 2015-02-22 04:33 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-02-22 04:33:02 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
journaltctl -b output from boot to gray gdm error screen (144.53 KB, text/plain)
2015-02-15 23:28 UTC, Jeff Hardy
no flags Details

Description Jeff Hardy 2015-02-12 16:29:43 UTC
Description of problem:

Fedup virtual machine (VirtualBox) from Fedora 20 to Fedora 21, gdm crashes with "Oh no, something has gone wrong."  Logs reveal the following error:

gdm-Xorg-:0: (==) VBoxVideo(0): DPMS enabled
gdm-Xorg-:0: (--) RandR disabled
gdm-Xorg-:0: (II) SELinux: Disabled on system
gdm-Xorg-:0: (II) Next line is added to allow vboxvideo_drv.so to appear as whitelisted driver
gdm-Xorg-:0: (II) The file referenced, is *NOT* loaded
gdm-Xorg-:0: (II) Loading /usr/lib/xorg/modules/drivers//ati_drv.so
gdm-Xorg-:0: (EE) AIGLX error: vboxvideo does not export required DRI extension
gdm-Xorg-:0: (EE) AIGLX: reverting to software rendering
gdm-Xorg-:0: (EE) AIGLX error: dlopen of /usr/lib/dri/swrast_dri.so failed (/usr/lib/dri/swrast_dri.so: undefined symbol: _glapi_tls_Dispatch)
gdm-Xorg-:0: (EE) GLX: could not load software renderer
gdm-Xorg-:0: (II) GLX: no usable GL providers found for screen 0

The very same image was similarly fedup upgraded on a physical laptop with similar results:

gdm-Xorg-:0: (II) intel(0): hardware support for Present enabled
gdm-Xorg-:0: (--) RandR disabled
gdm-Xorg-:0: (II) SELinux: Disabled on system
gdm-Xorg-:0: (EE) AIGLX error: dlopen of /usr/lib/dri/i915_dri.so failed (/usr/lib/dri/i915_dri.so: undefined symbol: _glapi_tls_Dispatch)
gdm-Xorg-:0: (EE) AIGLX: reverting to software rendering
gdm-Xorg-:0: (EE) AIGLX error: dlopen of /usr/lib/dri/swrast_dri.so failed (/usr/lib/dri/swrast_dri.so: undefined symbol: _glapi_tls_Dispatch)
gdm-Xorg-:0: (EE) GLX: could not load software renderer
gdm-Xorg-:0: (II) GLX: no usable GL providers found for screen 0

Starting gnome with startx from multi-user.target produces the same in Xorg.0.log.

KDM and XFCE both work without issue.


Version-Release number of selected component (if applicable):

rpm -qa | grep gdm
pulseaudio-gdm-hooks-5.0-25.fc21.i686
gdm-3.14.1-2.fc21.i686

How reproducible:

Always.

Steps to Reproduce:
1. fedup fedora 20 system to fedora 21
2. launch gdm

Actual results:

Grey screen "Oh no, something has gone wrong"

Expected results:

GDM user select screen, working Gnome.

Additional info:

Image has been upgraded through several Fedora releases.

Comment 1 Jeff Hardy 2015-02-12 16:31:47 UTC
Fresh Fedora 21 install in this particular VirtualBox environment works as expected.

Comment 2 Jeff Hardy 2015-02-15 23:28:01 UTC
Created attachment 992005 [details]
journaltctl -b output from boot to gray gdm error screen

Comment 3 Jeff Hardy 2015-02-15 23:30:01 UTC
# rpm -qa kernel* dracut* systemd* gdm* xorg* | sort
dracut-038-32.git20141216.fc21.i686
dracut-config-rescue-038-32.git20141216.fc21.i686
dracut-network-038-32.git20141216.fc21.i686
gdm-3.14.1-2.fc21.i686
kernel-3.12.6-200.fc19.i686
kernel-3.12.8-300.fc20.i686
kernel-3.17.7-200.fc20.i686
kernel-3.17.8-300.fc21.i686
kernel-core-3.17.8-300.fc21.i686
kernel-devel-3.12.6-200.fc19.i686
kernel-devel-3.12.8-300.fc20.i686
kernel-devel-3.17.7-200.fc20.i686
kernel-devel-3.17.8-300.fc21.i686
kernel-headers-3.17.8-300.fc21.i686
kernel-modules-3.17.8-300.fc21.i686
kernel-tools-3.17.8-300.fc21.i686
kernel-tools-libs-3.17.8-300.fc21.i686
systemd-216-14.fc21.i686
systemd-compat-libs-216-14.fc21.i686
systemd-devel-216-14.fc21.i686
systemd-libs-216-14.fc21.i686
systemd-python-216-14.fc21.i686
systemd-python3-216-14.fc21.i686
xorg-x11-apps-7.7-12.fc21.i686
xorg-x11-drv-evdev-2.9.0-3.fc21.i686
xorg-x11-drv-fbdev-0.4.3-19.fc21.i686
xorg-x11-drv-geode-2.11.15-4.fc21.i686
xorg-x11-drv-intel-2.99.916-3.20141117.fc21.i686
xorg-x11-drv-modesetting-0.9.0-2.fc21.i686
xorg-x11-drv-nouveau-1.0.11-1.fc21.i686
xorg-x11-drv-openchrome-0.3.3-12.fc21.i686
xorg-x11-drv-qxl-0.1.2-1.fc21.i686
xorg-x11-drv-synaptics-1.8.0-9.fc21.i686
xorg-x11-drv-vesa-2.3.2-19.fc21.i686
xorg-x11-drv-vmmouse-13.0.0-13.fc21.i686
xorg-x11-drv-vmware-13.0.2-5.20140613git82c9b0c.fc21.i686
xorg-x11-drv-wacom-0.25.0-2.fc21.i686
xorg-x11-fonts-100dpi-7.5-14.fc21.noarch
xorg-x11-fonts-75dpi-7.5-14.fc21.noarch
xorg-x11-fonts-ISO8859-1-100dpi-7.5-14.fc21.noarch
xorg-x11-fonts-ISO8859-1-75dpi-7.5-14.fc21.noarch
xorg-x11-fonts-misc-7.5-14.fc21.noarch
xorg-x11-fonts-Type1-7.5-14.fc21.noarch
xorg-x11-font-utils-7.5-25.fc21.i686
xorg-x11-proto-devel-7.7-12.fc21.noarch
xorg-x11-resutils-7.5-11.fc21.i686
xorg-x11-server-common-1.16.2.901-1.fc21.i686
xorg-x11-server-utils-7.7-10.fc21.i686
xorg-x11-server-Xorg-1.16.2.901-1.fc21.i686
xorg-x11-server-Xvfb-1.16.2.901-1.fc21.i686
xorg-x11-server-Xwayland-1.16.2.901-1.fc21.i686
xorg-x11-twm-1.0.8-2.fc21.i686
xorg-x11-util-macros-1.19.0-3.fc21.noarch
xorg-x11-utils-7.5-16.fc21.i686
xorg-x11-xauth-1.0.9-2.fc21.i686
xorg-x11-xbitmaps-1.1.1-7.fc21.noarch
xorg-x11-xdm-1.1.11-8.fc21.i686
xorg-x11-xfs-1.1.4-2.fc21.i686
xorg-x11-xfwp-1.0.2-7.fc21.i686
xorg-x11-xinit-1.3.4-2.fc21.i686
xorg-x11-xkb-utils-7.7-12.fc21.i686
xorg-x11-xsm-1.0.2-24.fc21.i686

Comment 4 Jeff Hardy 2015-02-18 04:49:08 UTC
Debian bug reporting same symptoms:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756407

I tracked my own problem down similarly:

ls -l /usr/lib/libGL.so*
lrwxrwxrwx  1 root root     14 Jan 24 09:00 /usr/lib/libGL.so -> libGL.so.1.2.0
lrwxrwxrwx  1 root root     18 Feb 12 11:01 /usr/lib/libGL.so.1 -> libGL.so.173.14.27
-rwxr-xr-x  1 root root 776588 Jan 24 09:01 /usr/lib/libGL.so.1.2.0
-rwxr-xr-x. 1 root root 667528 Aug 19  2010 /usr/lib/libGL.so.173.14.27

rpm -q --whatprovides /usr/lib/libGL.so
mesa-libGL-devel-10.4.3-1.20150124.fc21.i686

rpm -q --whatprovides /usr/lib/libGL.so.1
mesa-libGL-10.4.3-1.20150124.fc21.i686

rpm -q --whatprovides /usr/lib/libGL.so.1.2.0 
mesa-libGL-10.4.3-1.20150124.fc21.i686

rpm -q --whatprovides /usr/lib/libGL.so.173.14.27 
file /usr/lib/libGL.so.173.14.27 is not owned by any package

That library is ultimately left over from an nvidia proprietary driver install from some time ago.  Removing libGL.so.173.14.27 and running ldconfig fixed the symlinks and got everything operational again.

ls -l /usr/lib/libGL.so*
lrwxrwxrwx 1 root root     14 Jan 24 09:00 /usr/lib/libGL.so -> libGL.so.1.2.0
lrwxrwxrwx 1 root root     14 Feb 17 23:28 /usr/lib/libGL.so.1 -> libGL.so.1.2.0
-rwxr-xr-x 1 root root 776588 Jan 24 09:01 /usr/lib/libGL.so.1.2.0


Note You need to log in before you can comment on or make changes to this bug.