On 2018-03-06 00:44, Vincent Lefevre wrote:
> It appears that while the bug was fixed in unstable
> (384.111-1 -> 384.111-4), a new buggy version has just been uploaded
> to unstable (387.34-4), as detected by apt-listbugs. Indeed, this bug
> is marked as found in 387.34-1, but there's no fixed ver
It appears that while the bug was fixed in unstable
(384.111-1 -> 384.111-4), a new buggy version has just been uploaded
to unstable (387.34-4), as detected by apt-listbugs. Indeed, this bug
is marked as found in 387.34-1, but there's no fixed version for 387.*:
Found in versions nvidia-graphics-d
On Sat, 2018-01-13 at 14:59 +0100, Andreas Beckmann wrote:
> On 2018-01-11 23:26, Luca Boccassi wrote:
> > The new meta packages for switching over are handy, unfortunately
> > apt
> > chokes on them - aptitude is able to figure it out though.
> >
> > I suspect it's again due to multiarch - seems
On 2018-01-11 23:26, Luca Boccassi wrote:
> The new meta packages for switching over are handy, unfortunately apt
> chokes on them - aptitude is able to figure it out though.
>
> I suspect it's again due to multiarch - seems to be a recurring problem
> with apt. So don't think there's anything we
Great, thanks!
Andreas, tested as well on my Stretch desktop, both glvnd and non-glvnd
look fine.
The new meta packages for switching over are handy, unfortunately apt
chokes on them - aptitude is able to figure it out though.
I suspect it's again due to multiarch - seems to be a recurring prob
Hi,
Tested w/ the following games :
Cities Skylines -> OK
F1 2017 (Vulkan Only) -> OK
Middle Earth Shadow of Mordor -> OK
Civilization V -> OK
All under KDE.
All is OK for me. :-)
2018-01-11 13:47 GMT+01:00 Luca Boccassi :
> On Thu, 2018-01-11 at 12:23 +0100, Julien Aubin wrote:
> > Le 11 janv
On Thu, 2018-01-11 at 12:23 +0100, Julien Aubin wrote:
> Le 11 janv. 2018 12:19, "Luca Boccassi" a écrit :
>
> On Wed, 2018-01-10 at 23:58 +0100, Andreas Beckmann wrote:
> > On 2018-01-10 15:25, Luca Boccassi wrote:
> > > I'm a little confused as what their blobs could possible have to
> > > do
>
On Wed, 2018-01-10 at 23:58 +0100, Andreas Beckmann wrote:
> On 2018-01-10 15:25, Luca Boccassi wrote:
> > I'm a little confused as what their blobs could possible have to do
> > with spectre/meltdown to be honest
>
> meltdown does not seem to be an issue, but for spectre it is not
> neccessarily
Le 11 janv. 2018 12:19, "Luca Boccassi" a écrit :
On Wed, 2018-01-10 at 23:58 +0100, Andreas Beckmann wrote:
> On 2018-01-10 15:25, Luca Boccassi wrote:
> > I'm a little confused as what their blobs could possible have to do
> > with spectre/meltdown to be honest
>
> meltdown does not seem to be
On Wed, 2018-01-10 at 23:58 +0100, Andreas Beckmann wrote:
> On 2018-01-10 15:25, Luca Boccassi wrote:
> > I'm a little confused as what their blobs could possible have to do
> > with spectre/meltdown to be honest
>
> meltdown does not seem to be an issue, but for spectre it is not
> neccessarily
On 2018-01-10 15:25, Luca Boccassi wrote:
> I'm a little confused as what their blobs could possible have to do
> with spectre/meltdown to be honest
meltdown does not seem to be an issue, but for spectre it is not
neccessarily the GPU bits being fixed, but the CPU side of the driver -
which can ru
Control: tag -1 - stretch
Nope, this is not stretch-only. The found/fixed versions are sufficient
to express the occurrences of this bug.
Andreas
Control: fixed -1 384.111-1
Control: tags -1 stretch
On Wed, 2018-01-10 at 15:11 +0100, Julien Aubin wrote:
> Package: nvidia-driver
> Version: 375.82-1~deb9u1
> Severity: critical
>
> Hi,
>
> NVidia upgraded their blob to version 384.111 in order to fix Spectre
> /
> Meltdown vulnerability. It
Package: nvidia-driver
Version: 375.82-1~deb9u1
Severity: critical
Hi,
NVidia upgraded their blob to version 384.111 in order to fix Spectre /
Meltdown vulnerability. It turns out that the 375.xx branch is no longer
supported, so we cannot expect getting driver patches for the current
stretch dri
14 matches
Mail list logo
