GNOME Bugzilla – Bug 712340
GDM, GNOME Shell and Totem don't start with Catalyst 13.11 beta 6
Last modified: 2021-06-10 11:20:39 UTC
I'm trying Fedora "20 Beta" release and Catalyst "13.11 beta 6" and gdm is giving me a black screen at startup. I searched on internet about this issue and found bug 701445, but I failed miserably trying to compile all packages mentioned there with those parameters. GDM does no seem to crash, instead is like is waiting there with a black screen, and I do not know about the internals of GDM, but maybe is GNOME Shell failing to start that does not allow GDM to load completely. Starting GNOME Shell from terminal it gives this error: [dyskette@prism ~]$ gnome-shell (gnome-shell:4856): GLib-CRITICAL **: g_strsplit: assertion 'string != NULL' failed (gnome-shell:4856): Clutter-CRITICAL **: Unable to initialize Clutter: The OpenGL version could not be determined Window manager error: Unable to initialize Clutter. But, trying to get a trace from that it just tell me "No stack.". Then I installed LXDE and lxdm to find out if it was a problem of Catalyst, and apparently all games and other software are working fine, except for Totem. Totem gives this error in terminal. [dyskette@prism ~]$ totem (totem:4836): GLib-CRITICAL **: g_strsplit: assertion 'string != NULL' failed (totem:4836): Clutter-CRITICAL **: Unable to initialize Clutter: The OpenGL version could not be determined (totem:4836): Totem-WARNING **: gtk-clutter failed to initialise, expect problems from here on. (totem:4836): GLib-CRITICAL **: g_strsplit: assertion 'string != NULL' failed (totem:4836): Clutter-CRITICAL **: Unable to initialize Clutter: The OpenGL version could not be determined Segmentation fault (core dumped) And gives me these traces.
+ Trace 232774
Is this a regression to the bug mentioned earlier or is it another one? And, is there a workaround in the meantime? I really like GNOME Shell and I don't feel comfortable with other DE's. P.S. I'm filling this bug in cogl following the same pattern as bug 701445. I'm sorry if this does not belong here.
I met exactly the same issue with Fedora 20 Beta with: gnome-shell-3.10.1-2.fc20.x86_64 gdm-3.10.0-1.fc20.x86_64 cogl-1.16.0-2.fc20.x86_64 clutter-1.16.0-2.fc20.x86_64
OK, I have GNOME Shell and Totem working with Catalyst 13.11 beta 6 finally, rebuilding rpms. In cogl spec file, %build section Added: --enable-cogl-gles2=no \ --enable-wayland-backend=no \ --enable-wayland-compositor=no Commented: # --enable-kms-egl-platform \ # --enable-wayland-egl-platform \ # --enable-wayland-egl-server \ # --enable-xlib-egl-platform In clutter spec file, %build section Added: --enable-wayland-backend=no \ --enable-wayland-compositor=no \ Commented: #%if %{with_wayland} # --enable-egl-backend \ # --enable-evdev-input \ # --enable-wayland-backend \ # --enable-wayland-compositor \ #%endif In gnome-shell spec file, %prep section, commented: # %patch10 -p1 -b .fix-wayland-build %install section, commented: # desktop-file-validate %{buildroot}%{_datadir}/applications/gnome-shell-wayland.desktop # %{_bindir}/gnome-shell-wayland # %{_datadir}/applications/gnome-shell-wayland.desktop Totem spec file did not need any modification, just rebuilding again is enough. Source rpm files are: cogl-1.16.0-2.fc20.src.rpm clutter-1.16.0-2.fc20.src.rpm gnome-shell-3.10.2-1.fc20.src.rpm totem-3.10.1-1.fc20.src.rpm
Informative result you have find. Thanks! I just filed an issue against Catalyst Driver on AMD Bugzilla: http://ati.cchtml.com/show_bug.cgi?id=949 It should be able to deal with EGL.
Bijiben and Cheese are also not starting. Rebuilding (with custom cogl and clutter from previous comment) fix them.
Unfortunately the fix in Comment 2 no longer works with the Fedora 20. The gnome-shell package no longer compiles. The reason I think is because the wayland patch has been included in gnome-shell. I have tried to disable in the spec file for gnome-shell everything concerning wayland but it does not compile. Any suggestion?
Well actually not ... the compilation still works. I had just to remove mutter-wayland-devel-3.10.1-1.fc20.x86_64 since otherwise configure detected it and tried to call the inexistent wayland libraries when rebuilding gnome-shell
Can you attach your glxinfo output?
This might be relevant: https://bugzilla.rpmfusion.org/show_bug.cgi?id=2914
The bug has now also reached Debian (unstable and testing) [1]. It seems like the correct explanation is given in [2]: glGetString(GL_VERSION) finds a string in another library than the fglrx libGL. The workaround mentioned in [2] to preload fglrx-libGL.so works on Debian. [1] https://bugs.debian.org/722161 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1054435#c4
any news? but still reproducible with libcogl20 1.18.2, fglrx 14.12 (debian)
I can confirm 1.18.2 is affected too. This bug is open for more than a year, now. Any chance to get this fixed in a coming release of cogl ? Does any developer need some logs, trace or anything else helping ?
It seems that there's something wrong with the AMD drivers on Linux. Using dlopen/dlsym on libGL.so.1 is not weird: it's pretty much how people have been using libGL since forever. Maybe fglrx expects people to link directly to libGL? That would be weird, and it would not allow things like shipping Cogl with support for desktop GL and GLES in the same shared library. It could also be an artefact of the linking done when building the shared library. Obviously, without knowing how these libraries are being built, there's not much we, as free software developers, can do. It would be helpful to notify AMD and see what are the requirements in order to use their libraries via libdl.
Created attachment 300709 [details] backtrace
Created attachment 300713 [details] glxinfo
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version of cogl, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a ticket at https://gitlab.gnome.org/GNOME/cogl/-/issues/ Thank you for your understanding and your help.