| 1 |
Here are some hints for ~amd64 users who are about to have trouble with |
| 2 |
gnome3-session failing to start: |
| 3 |
|
| 4 |
After updating today to mesa-10.4.2 and xorg-server-1.16.3-r1, gnome3 |
| 5 |
failed to start, complaining that 3d acceleration was not available. |
| 6 |
|
| 7 |
This was true, unfortunately, and the reason is that xorg-server is |
| 8 |
looking for the nvidia glx module in the wrong directory, i.e. |
| 9 |
/usr/lib64/xorg/modules/extensions/libglx.so. |
| 10 |
|
| 11 |
The correct path is /usr/lib64/opengl/nvidia/extensions/libglx.so. |
| 12 |
|
| 13 |
Normally, 'eselect opengl' sets this path correctly, but not today, |
| 14 |
apparently. |
| 15 |
|
| 16 |
I finally worked around this problem by creating an appropriate |
| 17 |
symlink to the nvidia libglx.so file in the correct location. |
| 18 |
|
| 19 |
Another recent problem is that xorg-server is honoring *only* the |
| 20 |
first path listed in /etc/X11/xorg.conf.d/20opengl, and fails if |
| 21 |
the appropriate file isn't there: |
| 22 |
|
| 23 |
i.e. it looks in /usr/lib32/ as the first default path (even on a |
| 24 |
64-bit machine) and fails to look in /usr/lib64/ even though that |
| 25 |
path is correctly included in the list of places to look. |
| 26 |
|
| 27 |
I think the devs are already aware of these bugs and are working |
| 28 |
on the problem. (Obviously not fixed yet :) |
| 29 |
|
| 30 |
|
| 31 |
BTW, some good news: mesa-10.4.2 fixes a problem with running |
| 32 |
gnome3 as virtualbox guest: The software rasterizer in the new |
| 33 |
mesa is now fast enough to satisfy /usr/libexec/gnome-session- |
| 34 |
check-accelerated, so gnome-session no longer craps out when |
| 35 |
starting in virtualbox :) |
Archives