You are not logged in.
Hi,
Staying on the 10th January repository gets rid of the problem.
I noticed the problem since xorg-1.19.
I use the proprietary Nvidia executable to install drivers.
My computer:
ASUS G750jw
No graphic chipset just GTX 765M card.
lspci :
user@arch_host:~ $ lspci | grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation GK106M [GeForce GTX 765M] (rev a1)
When i use the up to date repositories Slice works but not Gnome.
I use Slice insteed of gdm.
Coredumpctl :
PID: 564 (gnome-session-b)
UID: 1000 (titusiii)
GID: 1000 (titusiii)
Signal: 11 (SEGV)
Timestamp: Sat 2017-02-04 13:07:56 CET (37min ago)
Command Line: /usr/lib/gnome-session/gnome-session-binary
Executable: /usr/lib/gnome-session/gnome-session-binary
Control Group: /user.slice/user-1000.slice/session-c1.scope
Unit: session-c1.scope
Slice: user-1000.slice
Session: c1
Owner UID: 1000 (titusiii)
Boot ID: 5c1eb812b3de4a57838d4f0d261940b7
Machine ID: 26492d5cefc74c1c9a46897496fd253b
Hostname: arch_host
Storage: /var/lib/systemd/coredump/core.gnome-session-b.1000.5c1eb812b3de4a57838d4f0d261940b7.564.1486210076000000000000.lz4
Message: Process 564 (gnome-session-b) of user 1000 dumped core.
Stack trace of thread 564:
#0 0x00007f44db56f680 __egl_Main (libEGL_nvidia.so.0)
#1 0x00007f44ddf80cba __eglLookupVendorByName (libEGL.so.1)
#2 0x00007f44ddf80034 _init (libEGL.so.1)
#3 0x00007f44e61104ba n/a (n/a)
What would be the next steps to try and troubleshoot this problem ?
Cheers,
Titus
Offline
Solved by removing :
rm /usr/lib/libEGL.so.1
And copying :
cp /usr/lib/nvidia/libEGL.so.1.0.0 /usr/lib/libEGL.so.1
Offline
a) please mark the topic as solved
b) did you install the nvidia blob bypassing the package manager? /usr/lib/libEGL.so.1 should be provided by nvidia-libgl and symlink /usr/lib/nvidia/libEGL.so.1
Just saying, because your "solution" likely won't sustain.
Offline
@seth
I use the proprietary Nvidia executable to install drivers.
Offline
tsss... missed. Thanks.
@titusIII if you want to use the beta drivers, there's an AUR package.
The way it is, you likely resolved libGL with the mesa variant and can expect trouble on each and every future upgrade.
Offline
Package manager symlinks /usr/lib/nvidia/libEGL.so.1 on /usr/lib/libEGL.so.1
But in nvidia folder libEGL.so.1 and libEGL.so.1.0.0 are not same.
libEGL.so.1.0.0 is heavier.
The 1.0.0 file works but the .1 not.
Last edited by titusIII (2017-02-07 22:24:34)
Offline
$ ls -la /usr/lib/nvidia/libEGL.so.1
lrwxrwxrwx 1 root root 15 Oct 28 07:15 /usr/lib/nvidia/libEGL.so.1 -> libEGL.so.1.0.0
$ ls -la /usr/lib/nvidia/libEGL.so.1.0.0
-rwxr-xr-x 1 root root 76384 Oct 28 07:15 /usr/lib/nvidia/libEGL.so.1.0.0
Offline
$ ls -la /usr/lib/nvidia
lrwxrwxrwx 1 root root 11 Feb 5 15:56 libEGL.so -> libEGL.so.1
-rwxr-xr-x 1 root root 17528 Jun 13 2016 libEGL.so.1
-rwxr-xr-x 1 root root 76384 Oct 28 08:15 libEGL.so.1.0.0
Offline
If that output was after you installed the nvidia packages from the official repositories please post the output of
$ pacman -Qkk nvidia nvidia-libgl nvidia-utils libglvnd
Offline
$ pacman -Qkk nvidia nvidia-libgl nvidia-utils libglvnd
nvidia: 11 total files, 0 altered files
warning: nvidia-libgl: /usr/lib/libEGL.so.1 (File type mismatch)
nvidia-libgl: 19 total files, 1 altered file
nvidia-utils: 161 total files, 0 altered files
warning: libglvnd: /usr/lib/nvidia/libEGL.so (Symlink path mismatch)
warning: libglvnd: /usr/lib/nvidia/libEGL.so (Modification time mismatch)
warning: libglvnd: /usr/lib/nvidia/libEGL.so.1 (File type mismatch)
warning: libglvnd: /usr/lib/nvidia/libGL.so (Modification time mismatch)
warning: libglvnd: /usr/lib/nvidia/libGL.so.1 (Modification time mismatch)
warning: libglvnd: /usr/lib/nvidia/libGLESv1_CM.so (Modification time mismatch)
warning: libglvnd: /usr/lib/nvidia/libGLESv1_CM.so.1 (Modification time mismatch)
warning: libglvnd: /usr/lib/nvidia/libGLESv2.so (Modification time mismatch)
warning: libglvnd: /usr/lib/nvidia/libGLESv2.so.2 (Modification time mismatch)
libglvnd: 35 total files, 8 altered files
Offline
If you resintall nvidia-libgl and libglvnd then check again for modifications assuming there are none the issue should still not occur but without you having to alter files tracked by pacman.
Offline