Bug#903310: Please move this bug to bumblebee
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 your system) and primus to replace the gl-backend for optimus (to be able to use optirun). Please move this bug to bumblebee-nvidia package maintainers if possible. Thanks! Kind regards, Alex signature.asc Description: OpenPGP digital signature
Bug#903310: Please move this bug to bumblebee
... 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 bumblebee-nvidia?): > Start-Date: 2018-07-25 17:11:11 > Commandline: apt install nvidia-driver-libs-nonglvnd > Requested-By: user (1000) > Install: libgles-nvidia1:amd64 (390.67-3, automatic), libgles-nvidia1:i386 > (390.67-3, automatic), nvidia-nonglvnd-vulkan-icd:amd64 (390.67-3, > automatic), nvidia-nonglvnd-vulkan-icd:i386 (390.67-3, automatic), > nvidia-driver-libs-nonglvnd-i386:i386 (390.67-3, automatic), > libgl1-nvidia-glx:amd64 (390.67-3, automatic), libgl1-nvidia-glx:i386 > (390.67-3, automatic), nvidia-driver-libs-nonglvnd:amd64 (390.67-3), > nvidia-driver-libs-nonglvnd:i386 (390.67-3, automatic), libegl1-nvidia:amd64 > (390.67-3, automatic), libegl1-nvidia:i386 (390.67-3, automatic), > nvidia-nonglvnd-vulkan-common:amd64 (390.67-3, automatic) > Remove: nvidia-vulkan-icd:amd64 (390.67-3), nvidia-vulkan-icd:i386 > (390.67-3), nvidia-driver-libs-i386:i386 (390.67-3), > nvidia-vulkan-common:amd64 (390.67-3), libgl1-nvidia-glvnd-glx:amd64 > (390.67-3), libgl1-nvidia-glvnd-glx:i386 (390.67-3), nvidia-driver-libs:amd64 > (390.67-3), nvidia-driver-libs:i386 (390.67-3) > End-Date: 2018-07-25 17:11:29 > > Start-Date: 2018-07-25 17:18:18 > Commandline: apt install primus > Requested-By: user (1000) > Install: primus-libs:amd64 (0~20150328-6, automatic), primus-libs:i386 > (0~20150328-6, automatic), primus:amd64 (0~20150328-6), primus-libs-ia32:i386 > (0~20150328-6, automatic), libgl1-mesa-glx:i386 (18.1.4-1, automatic), > socat:amd64 (1.7.3.2-2, automatic) > End-Date: 2018-07-25 17:18:21 signature.asc Description: OpenPGP digital signature
Bug#903310: linux-image-4.16.0-2-amd64 doesn't boot: drm_vblank.c:1073 drm_wait_one_vblank+0x16e/0x180 [drm]
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 [drm:drm_atomic_helper_wait_for_dependencies [drm.kms.helper]] *ERROR* [CONNECTOR:48:LVDS-1]] flip_done timed out also for other connectors. What happens (what i see): * Kernel and initrd are getting loaded by grub * initrd (cryptsetup) asks me for the passphrase and seems to get access to lvm partitions (and mounts XFS root-fs) * The system continues booting (screen goes blank for a long time ~10s (KMS?)) * System gets stuck after printing a bunch of boot messages and those above With 4.14.0-3-amd64 still everything works smoothly. The blank screen phase (KMS?) is less than a second here. After some ddg'ing i've found several bugs, but assume that this is a different one. So what i found and tried: * https://bbs.archlinux.org/viewtopic.php?id=218581 * Unfortunately the CMDLINE with "video=SVIDEO-1:d" doesn't help * Simply adding "nomodeset" to CMDLINE * lets the system get stuck with even worse error messages (something about blockdevice.target could't be reached) * http://lists-archives.com/debian-users/3722180-kernel-upgrade-freeze-on-boot-linux-image-4-16-0-2-amd64.html * Adding "slab_common.usercopy_fallback=y" to CMDLINE * Doesn't help here, i assume nvidia isn't in place on boot, just Intel graphics * https://devtalk.nvidia.com/default/topic/1030082 * Replaced gdm3 with lightdm (and lightdm-gtk-greeter) * Same error Xorg-setup (just for reference): * bumblebee (NVIDIA Optimus NVS 4200) with nvidia 390.48 * /etc/X11/xorg.conf.d/20-intel.conf Section "Device" Identifier "intelgpu0" Driver "intel" Option "VirtualHeads" "" EndSection Thanks! Regards, Alex -- Package-specific info: ** Kernel log: boot messages should be attached Jul 7 15:41:35 hostname kernel: [0.00] Linux version 4.16.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 7.3.0 (Debian 7.3.0-23)) #1 SMP Debian 4.16.16-2 (2018-06-22) Jul 7 15:41:35 hostname kernel: [0.00] Command line: BOOT_IMAGE=/vmlinuz-4.16.0-2-amd64 root=/dev/mapper/[...] ro cryptdevice=UUID=[...]:cryptolvm quiet [...] Jul 7 15:41:35 hostname kernel: [0.143661] pci :00:02.0: Video device with shadowed ROM at [mem 0x000c-0x000d] Jul 7 15:41:35 hostname kernel: [0.144653] Unpacking initramfs... [...] Jul 7 15:41:35 hostname kernel: [9.889500] thinkpad_acpi: ThinkPad ACPI Extras v0.25 Jul 7 15:41:35 hostname kernel: [9.889501] thinkpad_acpi: http://ibm-acpi.sf.net/ Jul 7 15:41:35 hostname kernel: [9.889502] thinkpad_acpi: ThinkPad BIOS 8CET57WW (1.37 ), EC unknown Jul 7 15:41:35 hostname kernel: [9.889503] thinkpad_acpi: Lenovo ThinkPad T420s, model 4174P4G Jul 7 15:41:35 hostname kernel: [9.891586] thinkpad_acpi: radio switch found; radios are enabled Jul 7 15:41:35 hostname kernel: [9.891699] thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver Jul 7 15:41:35 hostname kernel: [9.891700] thinkpad_acpi: Disabling thinkpad-acpi brightness events by default... Jul 7 15:41:35 hostname kernel: [9.893111] ACPI Warning: SystemIO range 0x0428-0x042F conflicts with OpRegion 0x0400-0x047F (\_SB.PCI0.LPC.PMIO) (20180105/utaddress-247) Jul 7 15:41:35 hostname kernel: [9.893117] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver Jul 7 15:41:35 hostname kernel: [9.893120] ACPI Warning: SystemIO range 0x0540-0x054F conflicts with OpRegion 0x0500-0x057F (\_SB.PCI0.LPC.LPIO) (20180105/utaddress-247) Jul 7 15:41:35 hostname kernel: [9.893124] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver Jul 7 15:41:35 hostname kernel: [9.893125] ACPI Warning: SystemIO range 0x0530-0x053F conflicts with OpRegion 0x0500-0x057F (\_SB.PCI0.LPC.LPIO) (20180105/utaddress-247) Jul 7 15:41:35 hostname kernel: [9.893128] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver Jul 7 15:41:35 hostname kernel: [9.893129] ACPI Warning: SystemIO range 0x0500-0x052F conflicts with OpRegion 0x0500-0x057F (\_SB.PCI0.LPC.LPIO) (20180105/utaddress-247) Jul 7 15:41:35 hostname kernel: [9.893132] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver Jul 7 15:41:35 hostname kernel: [9.893133] lpc_ich: Resource conflict(s) found affecting gpio_ich Jul 7
Bug#954217: libpango1.0-0 depends on libpango-1.0-0 (= 1.44.7-1), but on bullseye current is 1.44.7-2
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). * What led up to the situation? * libpango-1.0-0 got a new package version * What exactly did you do (or not do) that was effective (or ineffective)? * apt-get install python-gtkglext1 * What was the outcome of this action? Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: python-gtkglext1 : Depends: libpango1.0-0 (>= 1.14.0) but it is not going to be installed E: Unable to correct problems, you have held broken packages. * What outcome did you expect instead? * Package "python-gtkglext1" being installed -- System Information: Debian Release: bullseye/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-3-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libpango1.0-0 depends on: ii libpango-1.0-0 1.44.7-1 ii libpangocairo-1.0-0 1.44.7-1 ii libpangoft2-1.0-01.44.7-1 pn libpangox-1.0-0 ii libpangoxft-1.0-01.42.4-8 libpango1.0-0 recommends no packages. libpango1.0-0 suggests no packages.
