| 1 |
On 3/12/20 7:46 PM, Neil Bothwick wrote: |
| 2 |
> On Fri, 13 Mar 2020 00:31:23 +0100, hitachi303 wrote: |
| 3 |
> |
| 4 |
>>>> I do edit it every time X won't start. Then X does start. But |
| 5 |
>>>> after updating and rebooting it has the old wrong line again. |
| 6 |
>>> You need to find out which ebuild is modifying it. Run "qlop -m" and |
| 7 |
>>> look for the package whose install time most closely matches the |
| 8 |
>>> modification time of the file. Then read the ebuild to see what is |
| 9 |
>>> going on. If an ebuild is setting this incorrectly, you may need to |
| 10 |
>>> file a bug report. |
| 11 |
>> |
| 12 |
>> Since I did edit the file I cannot find a match. I will have to wait |
| 13 |
>> until the problem occurs again. |
| 14 |
> |
| 15 |
> It seems that file is created/modified by the mesa ebuild. |
| 16 |
> |
| 17 |
> I would try removing the file and re-emerging mesa to see if it is |
| 18 |
> created with the correct content. |
| 19 |
> |
| 20 |
> |
| 21 |
|
| 22 |
The file is created/modified by app-eselect/eselect-opengl. If you have |
| 23 |
USE=libglvnd enabled, eselect-opengl is no longer installed, but the |
| 24 |
files it generated may remain. In this case, it is safe to remove the |
| 25 |
file if USE=libglvnd is enabled, and to regenerate the file by running |
| 26 |
`eselect opengl set xorg` (or nvidia, ...) if USE=-libglvnd. |
| 27 |
|
| 28 |
Jonathan Callen |
Archives