About that rule, the only way to prevent breaking testing would have been
marking this bug as release critical not for this package, but for the
linux kernel package.
Which in turn would mean holding off new kernel releases from debian until
a proprietary legacy driver is fixed, which might never
It was quite disappointing to see (or not see) the GUI/WM stop working
after a causal system update (not upGrade).
I was able to get the system somewhat back to normal by using the
NOUVEAU driver instead of NVIDIA. BTW, even that was kind of tricking
because the Nvidia driver blacklisted Nouveau
@jim_p Is it possible for you to avoid putting all system information
and Xorg logs in every message?
It makes the thread very difficult to follow on the online bug tracker.
I too rolled back to linux-image-5.9.0-3-amd64 which works, hope it
won't be my very last kernel version.
Processing control commands:
> severity -1 serious
Bug #976056 [nvidia-legacy-340xx-driver] nvidia-legacy-340xx-driver: Fails to
build with kernel 5.9.11 (package linux-image-5.9.0-4-amd64)
Ignoring request to change severity of Bug 976056 to the same value.
> retitle -1
Control: severity -1 serious
Control: retitle -1 nvidia-legacy-340xx-driver: requires DRM_LEGACY, disabled
from Linux 5.9.11 onwards
Control: tag -1 upstream wontfix
On 11/29/20 1:37 PM, Salvatore Bonaccorso wrote:
> Some background: In the 5.9.11-1 upload for src:linux we disabled
>
Package: nvidia-legacy-340xx-driver
Version: 340.108-8
Followup-For: Bug #976056
X-Debbugs-Cc: pitsior...@gmail.com
What does this mean for a simple user like me? Is it the end for nvidia 340xx
on debian? I do not want to move to nouveau at all!
-- Package-specific info:
uname -a:
Linux mitsos
Hi,
On Sun, Nov 29, 2020 at 07:17:06AM +0200, jim_p wrote:
> Package: nvidia-legacy-340xx-driver
> Version: 340.108-8
> Severity: normal
> X-Debbugs-Cc: pitsior...@gmail.com
>
> Dear Maintainer,
>
> That was unexpected! I noticed that kernel 5.4.11 reached unstable today, so I
> upgraded to it
7 matches
Mail list logo
