Dear Maintainer,

i recently upgrade my xserver to 1.16 and therefore switched from fglrx
to radeon (fgrlx doesn't support xserver 1.16 yet). When i'm trying to
start the xserver it sefaults (see logs). I'm not sure if it is a
side effect from switching from fgrlx to radeon. I think i uninstalled
fglrx properly.

best wishes,
Michael

I guess it's possible fglrx left the EGL stack messed up... If you start
Xorg with the environment variable EGL_LOG_LEVEL=debug, there should be
some more information about that in its stderr output.

It looks like it could be a bug in libepoxy0. It would be great if you
could get a backtrace with gdb, ideally with
/usr/lib/x86_64-linux-gnu/libepoxy.so.0 rebuilt to have debugging symbols.

Thanks for your quickly reply! It says:

libEGL debug: Native platform type: drm (autodetected)
libEGL debug: EGL search path is /usr/lib/x86_64-linux-gnu/egl
libEGL debug: added /usr/lib/x86_64-linux-gnu/egl/egl_gallium.so to
module array
libEGL debug: added egl_dri2 to module array
libEGL debug: dlopen(/usr/lib/x86_64-linux-gnu/egl/egl_gallium.so)
libEGL info: use DRM for display 0x7f308063cec0
libEGL debug: EGL user error 0x3001 (EGL_NOT_INITIALIZED) in
eglInitialize(no usable display)

i also add the output of startx and the xorg.log

Best,
Michael

Does the environment variable EGL_DRIVER=egl_dri2 work around the problem?

Unfortunately not:

libEGL debug: Native platform type: drm (autodetected)
libEGL debug: EGL search path is /usr/lib/x86_64-linux-gnu/egl
libEGL debug: added egl_dri2 to module array
libEGL debug: the best driver is DRI2
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0x7f82b4e72339]
(EE) 1: /usr/bin/X (0x7f82b4cc7000+0x1af3a9) [0x7f82b4e763a9]
(EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f82b2a1f000+0x35480)
[0x7f82b2a54480]
(EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (0x7f82b2a1f000+0x12530a)
[0x7f82b2b4430a]
(EE) 4: /usr/lib/x86_64-linux-gnu/libepoxy.so.0 (0x7f82af325000+0x5402f)
[0x7f82af37902f]
(EE) 5: /usr/lib/xorg/modules/libglamoregl.so (glamor_init+0x15c)
[0x7f82af81c84c]
(EE) 6: /usr/lib/xorg/modules/drivers/radeon_drv.so
(0x7f82b0489000+0x4be4c) [0x7f82b04d4e4c]
(EE) 7: /usr/lib/xorg/modules/drivers/radeon_drv.so
(0x7f82b0489000+0xc1c8) [0x7f82b04951c8]
(EE) 8: /usr/lib/xorg/modules/drivers/radeon_drv.so
(0x7f82b0489000+0x46549) [0x7f82b04cf549]
(EE) 9: /usr/bin/X (AddScreen+0x101) [0x7f82b4d1d281]
(EE) 10: /usr/bin/X (InitOutput+0x397) [0x7f82b4d5df27]
(EE) 11: /usr/bin/X (0x7f82b4cc7000+0x59d2a) [0x7f82b4d20d2a]
(EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5)
[0x7f82b2a40b45]
(EE) 13: /usr/bin/X (0x7f82b4cc7000+0x4549e) [0x7f82b4d0c49e]
(EE)
(EE) Segmentation fault at address 0x0

I tried apt-get install --reinstall libgl1-mesa-glx libgl1-mesa-dri
xserver-xorg-video-radeon xserver-xorg-core

which the ubuntu wiki suggested in case of a broken fglrx removal, it
didn't help.

Now i set Option "Accel" "False" in my xorg.conf as workaround which
gives me at least a working gui environment, yet a little slow of course.

Best
Michael

I had the exactly same bug and today I saw that I have some fglrx packages
with dpkg -l *fglrx*

So I purged all of them with aptitude purge ... and after reboot  it works
again with aceleration.

Hope it helps you.

My late client made you a beneficiary in his will. After several failed
attempts to reach you by post mail, I resulted reaching you by email, I
advise you contact me immediately for more information.