Bug#903310: Please move this bug to bumblebee

2018-07-25 Thread Alexander Berg
Dear all, sorry for this. After some break'n'fix-ing it's clear that it's not the kernel's fault, but wrong specified package dependencies of bumblebee-nvidia. The fix for this situation is to install nvidia-driver-libs-nonglvnd replacing some of the nvidia-libgl-stuff (to be able to boot

Bug#903310: Please move this bug to bumblebee

2018-07-25 Thread Alexander Berg
... actually an another bug delivered the workaround: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888020 So this may be not a duplicate, as primus wasn't installed on my system before (and the above bug is about the primus package). To document (conflicting packages with

Bug#903310: linux-image-4.16.0-2-amd64 doesn't boot: drm_vblank.c:1073 drm_wait_one_vblank+0x16e/0x180 [drm]

2018-07-08 Thread Alexander Berg
Package: src:linux Version: 4.16.16-2 Severity: important Dear Maintainer, after some weeks of update-lazyness, i've upgraded to linux-image-4.16.0-1 (and later on to -2). Unfortunately the system (Lenovo T420s) got stuck on boot, displaying messages like

Bug#954217: libpango1.0-0 depends on libpango-1.0-0 (= 1.44.7-1), but on bullseye current is 1.44.7-2

2020-03-18 Thread Alexander Berg
Package: libpango1.0-0 Version: 1.44.7-1 Severity: important Tags: a11y Dear Maintainer, unfortunately there are still many packages depending on the transitional package libpango1.0-0, e.g. python-gtkglext1 Please update libpango1.0-0 on bullseye to depend on libpango-1.0-0 (= 1.44.7-2).