Bug#769072: gnome-shell: GNOME Shell crashing with "Oh no, something went wrong"

Janusz S. Bien jsbien at mimuw.edu.pl
Sun Nov 16 08:13:47 UTC 2014


Quote/Cytat - Andreas Beckmann <anbe at debian.org> (nie, 16 lis 2014, 01:26:53):

> On 2014-11-15 21:53, Janusz S. Bien wrote:
>> Quote/Cytat - Andreas Beckmann <anbe at debian.org> (sob, 15 lis 2014,
>>> /usr/share/bug/libgl1-nvidia-glx/script 3>nvidia.log
>>
>> Enclosed.
>
> Thanks. Does not look like something is broken (except for having the
> nvidia packages installed manually on a system that does not support
> them). Which nvidia packages do you have installed?
>
> dpkg -l | grep nvidia
>
> (I would guess neither nvidia-driver nor xserver-xorg-video-nvidia).
>
>

--8<---------------cut here---------------start------------->8---
jsbien at cauda:~$ dpkg -l | grep nvidia
ii  libegl1-nvidia 340.46-3     i386         NVIDIA binary EGL libraries
ii  libgl1-nvidia- 340.46-3     i386         NVIDIA binary OpenGL libraries
ii  libgl1-nvidia- 304.123-4    i386         NVIDIA binary OpenGL libraries (3
ii  libnvidia-comp 340.46-3     i386         NVIDIA runtime compiler library
ii  libnvidia-eglc 340.46-3     i386         NVIDIA binary EGL core libraries
ii  libnvidia-ml1: 340.46-3     i386         NVIDIA Management Library (NVML)
ii  nvidia-alterna 340.46-3     i386         allows the selection of NVIDIA as
ii  nvidia-install 20131102+2   i386         cleanup after driver installation
ii  nvidia-kernel- 20131102+2   i386         NVIDIA binary kernel module suppo
ii  nvidia-kernel- 340.46-3     i386         NVIDIA binary kernel module DKMS
ii  nvidia-legacy- 304.123-4    i386         allows the selection of NVIDIA as
ii  nvidia-legacy- 304.123-4    i386         NVIDIA binary kernel module DKMS
ii  nvidia-libopen 340.46-3     i386         NVIDIA OpenCL ICD Loader library
ii  nvidia-modprob 340.46-1     i386         utility to load NVIDIA kernel mod
ii  nvidia-opencl- 340.46-3     i386         NVIDIA OpenCL driver
ii  nvidia-opencl- 340.46-3     i386         NVIDIA OpenCL installable client
ii  nvidia-setting 340.46-2     i386         tool for configuring the NVIDIA g
ii  nvidia-setting 304.123-2    i386         tool for configuring the NVIDIA g
ii  nvidia-smi     340.46-3     i386         NVIDIA System Management Interfac
ii  nvidia-support 20131102+2   i386         NVIDIA binary graphics driver sup
ii  nvidia-vdpau-d 340.46-3     i386         Video Decode and Presentation API
--8<---------------cut here---------------end--------------->8---

Although some of them has been installed manually, for the first time  
the nvidia packages just appeared after one of (dist?) upgrades. The  
first trace of them is from August:

Mon, Aug  4 2014 16:15:15 +0200
[INSTALL, DEPENDENCIES] libnvidia-compiler:i386
...
[INSTALL, DEPENDENCIES] nvidia-libopencl1:i386
[INSTALL, DEPENDENCIES] nvidia-opencl-common:i386
[INSTALL, DEPENDENCIES] nvidia-opencl-icd:i386

> To "fix" your system, either uninstall the nvidia packages (they are not
> useful on your system anyway)

Can I remove all of the packages listed above?

> or switch back to mesa:
>  update-alternatives --config glx
> and select mesa

This worked - thank you very much!

To be more precise, it almost worked: the monitor is not recognized
although it used to be. This is definitely another topic but I would
appreciate very much your advice, especially as I have systematically
such a problem on another computer: to which package should I submit the
issue?

> I don't think I can express this with package relationships:
>
> libgl1-nvidia-glx needs to be installed
>  (1) together with xserver-xorg-video-nvidia (and xserver-xorg-core)
>      (regular installation on a host)
>  (2) OR without xserver-xorg-core (and xserver-xorg-video-nvidia)
>      (i.e. libraries from a foreign architecture only or in a chroot
>       without own xserver)
> i.e. only the combination
>  install libgl1-nvidia-glx:native
>  install xserver-xorg-core:native
>  no-install xserver-xorg-video-nvidia
> should be forbidden.

I'm still intrigued by the message which I definitely seen on the
console during an upgrade, which was definitely about a nvidia package
and which is not present in /var/apt/log. The problem appeared
immediately after this routine upgrade. Perhaps by my actions I made it
worst, but the primary reason was (is?) somewhere in the system.

Once again I thank you very much for your help.

Janusz


-- 
Prof. dr hab. Janusz S. Bień -  Uniwersytet Warszawski (Katedra  
Lingwistyki Formalnej)
Prof. Janusz S. Bień - University of Warsaw (Formal Linguistics Department)
jsbien at uw.edu.pl, jsbien at mimuw.edu.pl, http://fleksem.klf.uw.edu.pl/~jsbien/



More information about the pkg-nvidia-devel mailing list