Bug#905969: amdgpu: only one audio port shows up in pulseaudio
Source: linux Severity: normal Dear Maintainer, I have a Radeon RX580 card with two DisplayPort ports, in a dual-head monitor setup. When I look at the corresponding audio sink with pulseaudio, however, I find that there is only one output port listed, and so I cannot select which port I wish to send audio out on. Both ports work for audio; if the current-active monitor is disconnected, then the audio will automatically switch to the other one. It is just that they are not both exposed simultaneously to pulseaudio as being selectable. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-1-amd64 (SMP w/16 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system)
Bug#904967: linux-image-4.17.0-1-amd64: use-after-free in amdgpu
Package: src:linux Version: 4.17.8-1 Severity: important Dear Maintainer, I am encountering system instability on my machine, that I believe is related to the amdgpu driver. I am running a Sapphire Radeon RX 580 Nitro +. I am not sure the root cause of the instability, however, I have discovered the following use-after-free bug in the driver in my syslogs. It is clearly a bug of some import. Thank you, Alexis Hunt -- Package-specific info: ** Version: Linux version 4.17.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 7.3.0 (Debian 7.3.0-26)) #1 SMP Debian 4.17.8-1 (2018-07-20) ** Command line: BOOT_IMAGE=/vmlinuz-4.17.0-1-amd64 root=/dev/mapper/ala--main-ala--root ro amdgpu.dc=1 quiet ** Not tainted ** Relevant stack trace: Jul 24 11:27:04 ala kernel: [171212.829346] [ cut here ] Jul 24 11:27:04 ala kernel: [171212.829348] refcount_t: increment on 0; use-after-free. Jul 24 11:27:04 ala kernel: [171212.829362] WARNING: CPU: 12 PID: 17661 at /build/linux-9Vm0he/linux-4.17.6/lib/refcount.c:153 refcount_inc+0x27/0x30 Jul 24 11:27:04 ala kernel: [171212.829363] Modules linked in: fuse btrfs zstd_compress zstd_decompress xxhash xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c cpuid rfcomm ctr ccm cmac bnep nls_ascii amdkfd nls_cp437 vfat arc4 fat amdgpu btusb btrtl snd_hda_codec_realtek iwlmvm amd64_edac_mod snd_hda_codec_generic btbcm edac_mce_amd chash snd_hda_codec_hdmi mxm_wmi wmi_bmof btintel gpu_sched snd_hda_intel mac80211 bluetooth ttm snd_hda_codec kvm iwlwifi snd_hda_core drbg efi_pstore snd_hwdep irqbypass joydev evdev drm_kms_helper snd_pcm ansi_cprng efivars pcspkr cfg80211 snd_timer k10temp drm sp5100_tco ecdh_generic ccp snd rfkill rng_core soundcore shpchp wmi button acpi_cpufreq nct6775 hwmon_vid jc42 efivarfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb algif_skcipher af_alg Jul 24 11:27:04 ala kernel: [171212.829417] dm_crypt dm_mod hid_generic usbhid hid crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel ahci xhci_pci aes_x86_64 crypto_simd libahci xhci_hcd igb cryptd glue_helper libata i2c_piix4 i2c_algo_bit nvme dca usbcore scsi_mod usb_common nvme_core gpio_amdpt gpio_generic Jul 24 11:27:04 ala kernel: [171212.829437] CPU: 12 PID: 17661 Comm: Xorg Not tainted 4.17.0-1-amd64 #1 Debian 4.17.6-2 Jul 24 11:27:04 ala kernel: [171212.829438] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X370 Taichi, BIOS P3.20 09/08/2017 Jul 24 11:27:04 ala kernel: [171212.829441] RIP: 0010:refcount_inc+0x27/0x30 Jul 24 11:27:04 ala kernel: [171212.829442] RSP: 0018:bbd8c868b990 EFLAGS: 00010282 Jul 24 11:27:04 ala kernel: [171212.829444] RAX: RBX: 994f2f16e000 RCX: 0006 Jul 24 11:27:04 ala kernel: [171212.829445] RDX: 0007 RSI: 0096 RDI: 994ffe916730 Jul 24 11:27:04 ala kernel: [171212.829446] RBP: 994ff1317400 R08: 0482 R09: 0004 Jul 24 11:27:04 ala kernel: [171212.829447] R10: bbd8c868bb08 R11: 0001 R12: 994ff8921000 Jul 24 11:27:04 ala kernel: [171212.829448] R13: bbd8c868b9d0 R14: 994ecd35d080 R15: 994f2f16bc00 Jul 24 11:27:04 ala kernel: [171212.829450] FS: 7fc60b880a40() GS:994ffe90() knlGS: Jul 24 11:27:04 ala kernel: [171212.829451] CS: 0010 DS: ES: CR0: 80050033 Jul 24 11:27:04 ala kernel: [171212.829452] CR2: 185ca1569000 CR3: 0007ee75e000 CR4: 003406e0 Jul 24 11:27:04 ala kernel: [171212.829453] Call Trace: Jul 24 11:27:04 ala kernel: [171212.829505] dc_create_stream_for_sink+0x4e/0x190 [amdgpu] Jul 24 11:27:04 ala kernel: [171212.829557] create_stream_for_sink+0x6e/0x600 [amdgpu] Jul 24 11:27:04 ala kernel: [171212.829606] ? dm_update_crtcs_state+0x14d/0x4a0 [amdgpu] Jul 24 11:27:04 ala kernel: [171212.829649] dm_update_crtcs_state+0x14d/0x4a0 [amdgpu] Jul 24 11:27:04 ala kernel: [171212.829692] amdgpu_dm_atomic_check+0x191/0x3c0 [amdgpu] Jul 24 11:27:04 ala kernel: [171212.829707] drm_atomic_check_only+0x33a/0x4f0 [drm] Jul 24 11:27:04 ala kernel: [171212.829721] ? drm_property_blob_get+0xe/0x20 [drm] Jul 24 11:27:04 ala kernel: [171212.829733] drm_atomic_commit+0x13/0x50 [drm] Jul 24 11:27:04 ala kernel: [171212.829741] drm_atomic_helper_legacy_gamma_set+0x112/0x160 [drm_kms_helper] Jul 24 11:27:04 ala kernel: [171212.829753] drm_mode_gamma_set_ioctl+0x17b/0x1e0 [drm] Jul 24 11:27:04 ala kernel: [171212.829765] ? drm_mode_crtc_set_gamma_size+0xa0/0xa0 [drm] Jul 24 11:27:04 ala kernel: [171212.829775] drm_ioctl_kernel+0x5b/0xb0 [drm] Jul 24 11:27:04 ala kernel: [171212.829786] drm_ioctl+0x2c3/0x360 [drm] Jul 24 11:27:04 ala kernel: [171212.829797] ? drm_mode_crtc_set_gamma_size+0xa0/0xa0 [drm] Jul 24 11:27:04 ala kernel: [171212.829801] ? ep_scan_ready_list.constprop.18+0x242/0x250 Jul 24 11:27:04 ala kernel
Bug#892245: pkg-config: /usr/lib/x86_64-linux-gnu/pkgconfig is not searched on amd64
Control: tags -1 - moreinfo Upon further investigation, it appears I had pkg-config:i386 installed somehow. Please close this bug. On Wed, 7 Mar 2018 at 01:26 Helmut Grohne <hel...@subdivi.de> wrote: > Control: tags -1 + moreinfo unreproducible > > On Wed, Mar 07, 2018 at 12:42:28AM -0500, Alexis Hunt wrote: > > I'm running Debian testing and was trying to use a package reliant on > > libncursesw. The libncursesw5-dev package installs ncursesw.pc into > > /usr/lib/x86_64-linux-gnu/pkgconfig, alongside many other pkg-config > files. Upon > > configuring, however, an error was reported from pkg-config that it > could not > > find ncursesw.pc. Investigation shows that this is because it is no > loading from > > /usr/lib/x86_64-linux-gnu/pkgconfig, which means that any -dev package > which > > installs to that directory won't work correctly with pkg-config unless > the user > > explicitly specifies PKG_CONFIG_PATH (as I did to work around this). > > I cannot reproduce this at all. In a fresh sid debootstrap after > installing libncursesw5-dev and pkg-config, > > pkg-config --exists ncursesw > > gives a successful exit code. I conclude that the behaviour you are > reporting is not reproducible in general and that you need to provide > further information on how to reproduce it. Please remove the moreinfo > tag (by starting your reply with "Control: tags -1 - moreinfo") when > doing so. > > Helmut >
Bug#892245: pkg-config: /usr/lib/x86_64-linux-gnu/pkgconfig is not searched on amd64
Package: pkg-config Version: 0.29-4+b1 Severity: important Dear Maintainer, I'm running Debian testing and was trying to use a package reliant on libncursesw. The libncursesw5-dev package installs ncursesw.pc into /usr/lib/x86_64-linux-gnu/pkgconfig, alongside many other pkg-config files. Upon configuring, however, an error was reported from pkg-config that it could not find ncursesw.pc. Investigation shows that this is because it is no loading from /usr/lib/x86_64-linux-gnu/pkgconfig, which means that any -dev package which installs to that directory won't work correctly with pkg-config unless the user explicitly specifies PKG_CONFIG_PATH (as I did to work around this). I believe that pkg-config should look there by default, or else all -dev packages installing there need to be updated to install somewhere in the default path. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pkg-config depends on: ii libc6 2.26-6 ii libdpkg-perl 1.19.0.5 ii libglib2.0-0 2.54.3-2 pkg-config recommends no packages. pkg-config suggests no packages. -- no debconf information
Bug#882108: xmonad is almost entirely nonfunctional
Package: xmonad Version: 0.13-6 Severity: important Dear Maintainer, I have been using xmonad for a long while, and today upgraded to Buster. While xmonad worked at first, after making a change to my configuration file, it stopped working: 1. I can't run xmonad --recompile; it just says "Use Stack!" 2. Previously, I put xmonad in my .xsession and started it like that. Trying to do so causes it to fail, again saying "Use Stack!" in .xsession-errors, and kicks me back to the login screen. 3. Switching to select Xmonad in LightDM's WM list lets me log in properly, but then xmonad crashes after executing the startup scripts. 4. Trying to manually recover it with --replace also says "Use Stack!" 5. Removing my .xmonad directory lets me log in and xmonad does not crash, but none of the keybinds work so I cannot open programs, dmenu, etc. It is, as a result, completely unusable. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xmonad depends on: ii libc6 2.24-17 ii libffi6 3.2.1-6 ii libgmp10 2:6.1.2+dfsg-1.1 ii libx11-6 2:1.6.4-3 ii libxext6 2:1.3.3-1+b2 ii libxinerama1 2:1.1.3-1+b3 ii libxrandr22:1.5.1-1 ii x11-utils 7.7+3+b1 Versions of packages xmonad recommends: ii libghc-xmonad-dev 0.13-6 ii libghc-xmonad-doc 0.13-6 ii xfonts-base1:1.0.4+nmu1 Versions of packages xmonad suggests: pn gnome-session-flashback ii suckless-tools [dmenu] 43-1 -- no debconf information
Bug#750080: Still exists
This bug still exists on Buster. After deleting my .xmonad.hs by accident, xmonad is basically unusable to me.
Bug#860445: libvte9: U+1F3DB CLASSICAL BUILDING incorrectly rendered as a singlewidth character
Thanks. I will follow up there. On Mon, 24 Apr 2017 at 16:09 Jason Crain <ja...@inspiresomeone.us> wrote: > Control: reassign -1 libvte-2.91-0 0.46.1-1 > Control: forwarded -1 https://bugzilla.gnome.org/781676 > > On Sun, Apr 16, 2017 at 07:34:25PM -0400, Alexis Hunt wrote: > > I noticed recently that U+1F3DB CLASSICAL BUILDING is incorrectly being > rendered > > as a singlewidth character when it, like most (all?) emoji, is actually > > doublewidth. The result is that it overlaps with the subsequent > character. It > > should be rendered as doublewidth. > > > > I have reproduced this in Terminator and in rxvt-unicode. > > I assume that you meant to file this against vte2.91 Terminator uses > vte2.91. rxvt-unicode doesn't use any version of vte though so it won't > be affected by any possible vte bugs. > > The Unicode spec is ambiguous about some of those emoji characters. It > lists the range 1F3D4..1F3DF as neutral (N) rather than wide (W), but > elsewhere it says that emoji are considered to be wide. I've forwarded > this to the vte developers so they can comment on whether they consider > it a bug. >
Bug#860445: libvte9: U+1F3DB CLASSICAL BUILDING incorrectly rendered as a singlewidth character
Package: libvte9 Version: 1:0.28.2-5+b2 Severity: normal Dear Maintainer, I noticed recently that U+1F3DB CLASSICAL BUILDING is incorrectly being rendered as a singlewidth character when it, like most (all?) emoji, is actually doublewidth. The result is that it overlaps with the subsequent character. It should be rendered as doublewidth. I have reproduced this in Terminator and in rxvt-unicode. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libvte9 depends on: ii libatk1.0-0 2.22.0-1 ii libc62.24-9 ii libcairo21.14.8-1 ii libfontconfig1 2.11.0-6.7+b1 ii libfreetype6 2.6.3-3+b2 ii libgdk-pixbuf2.0-0 2.36.5-2 ii libglib2.0-0 2.50.3-2 ii libgtk2.0-0 2.24.31-2 ii libncurses5 6.0+20161126-1 ii libpango-1.0-0 1.40.4-1 ii libpangocairo-1.0-0 1.40.4-1 ii libpangoft2-1.0-01.40.4-1 ii libtinfo56.0+20161126-1 ii libvte-common1:0.28.2-5 ii libx11-6 2:1.6.4-3 ii libxext6 2:1.3.3-1+b2 libvte9 recommends no packages. libvte9 suggests no packages. -- no debconf information
