Bug#804328: glx-alternative-nvidia: GDM3 exits with "Failed to initialize GLX extension (Compatible NVIDIA X driver not found)"

2015-11-11 Thread Alessio Gaeta
Il giorno sab, 07/11/2015 alle 18.50 +0100, Andreas Beckmann ha scritto: > For some reason your nvidia alternative (from nvidia-alternative) had > disappeared, cascading to glx-alternative-nvidia before it could be > reinstated, therefore cancelling the bumblebee setting. > > Essentially it's

Bug#804328: glx-alternative-nvidia: GDM3 exits with "Failed to initialize GLX extension (Compatible NVIDIA X driver not found)"

2015-11-11 Thread Andreas Beckmann
On 2015-11-11 19:32, Alessio Gaeta wrote: > I'm quite sure I did not fiddled with nvidia-alternative before the > system malfunction (I'm quite sure I did not at all ever). I could have > done it trying to recover the situation, reconfiguring related > packages. So, I cannot explain what rendered

Bug#804328: glx-alternative-nvidia: GDM3 exits with "Failed to initialize GLX extension (Compatible NVIDIA X driver not found)"

2015-11-07 Thread Andreas Beckmann
On 2015-11-07 13:38, Alessio Gaeta wrote: > after the last system upgrade GDM3 started to crash showing the infamous white > screen. > But I'm using Bumblebee, thus by default Intel card should be used. Looking at > the GLX alternatives I saw: > > # update-alternatives --config glx > Sono

Bug#804328: glx-alternative-nvidia: GDM3 exits with "Failed to initialize GLX extension (Compatible NVIDIA X driver not found)"

2015-11-07 Thread Alessio Gaeta
Package: glx-alternative-nvidia Version: 0.7.0 Severity: grave Justification: renders package unusable Hello, after the last system upgrade GDM3 started to crash showing the infamous white screen. In logs I found these relevant lines: [...] /usr/lib/gdm3/gdm-x-session[1730]: (II) NVIDIA GLX

Bug#804328: glx-alternative-nvidia: GDM3 exits with "Failed to initialize GLX extension (Compatible NVIDIA X driver not found)"

2015-11-07 Thread Andreas Beckmann
On 2015-11-07 17:18, Alessio Gaeta wrote: > In attach the log you requested. Relevant part is right at the file > head (2015-11-03). The log is in Italian, somehow I expected this :-) > but it should be quite simple > to guess what's happened... :) and that as well :-) > Reading the log I can