Bug#1053909: anbox: Failed to start as either binder or ashmem kernel drivers are not loaded
Additional info: after running modinfo binder_linux and modinfo ashmem_linux, it looks like I have binder but don't have ashmem. Further research also tells me that Anbox's development is inactive, so I might just give up on this. Just thought I'd let you know about the status of this package. -- Have a good night Alex OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1053909: anbox: Failed to start as either binder or ashmem kernel drivers are not loaded
Package: anbox Version: 0.0~git20210106-1 Severity: important Dear Maintainer, I'm looking to use Anbox to run some Android apps. Unfortunately, opening Anbox's application launcher results in a splash screen that says "Starting..." but then closes. Running `anbox session-manager` returns the following error message: [ 2023-10-14 03:35:16] [session_manager.cpp:146@operator()] Failed to start as either binder or ashmem kernel drivers are not loaded So from the looks of it, it seems that Anbox's required kernel modules, ashmem and binder, are not included with this package at all. This would render Anbox unusuable on Debian. Please package the required Anbox kernel modules so that Anbox can run without crashing. Thanks, Alex -- System Information: Debian Release: 12.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-12-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages anbox depends on: ii init-system-helpers 1.65.2 ii iptables1.8.9-2 ii libboost-filesystem1.74.0 1.74.0+ds1-21 ii libboost-iostreams1.74.01.74.0+ds1-21 ii libboost-log1.74.0 1.74.0+ds1-21 ii libboost-program-options1.74.0 1.74.0+ds1-21 ii libboost-thread1.74.0 1.74.0+ds1-21 ii libc6 2.36-9+deb12u3 ii libegl1 1.6.0-1 ii libgcc-s1 12.2.0-14 ii libgles21.6.0-1 ii liblxc1 1:5.0.2-1+deb12u1 ii libprotobuf-lite23 3.12.4-1 ii libsdbus-c++0 0.8.3-4 ii libsdl2-2.0-0 2.26.5+dfsg-1 ii libsdl2-image-2.0-0 2.6.3+dfsg-1 ii libstdc++6 12.2.0-14 ii libsystemd0 252.17-1~deb12u1 ii lxc 1:5.0.2-1+deb12u1 Versions of packages anbox recommends: ii dbus-user-session 1.14.10-1~deb12u1 anbox suggests no packages. -- no debconf information
Bug#1024852: nvidia-driver in bullseye (470.141.03-1~deb11u1) and bullseye-backports (470.103.01-1~bpo11+1) do not support Linux kernel 6.0 or later
So what is the proposal there? The proposal is to include an updated nvidia-driver in backports so that it works with the backported Linux 6.0 kernel. Just do not install 6.0 kernel from backports if you need nvidia driver? Well, what if there is a scenario where the user needed 6.0 and the newer nvidia-driver? But even still, the fact of the matter is that an unknowing user who has a backported kernel and nvidia-driver will update their packages and then lose their nvidia-driver. Luckily my friend had integrated graphics to fall back on, but if he had one of those AMD APUs without an iGPU he would be left with a system without graphics. Why are you a) filing a bug which is already fixed in Debian, and Has the bug been fixed? I believe there is a misunderstanding. From what I can tell by previous bug reports for this package, the bug hasn't been fixed, is reproducible, and still happening. The Phoronix article is talking about a newer version of nvidia-driver that has not been packaged in bullseye or bullseye-backports (although newer versions are in bookworm and sid). b) why are you filing it against the bpo version of the package? Because a) I don't know how to file the bug report for both versions other than submitting two bug reports, which seems redundant and b) because I'd imagine the backports team would have more leeway to update the package compared to the stable branch, and c) I'd imagine that if a user needs a newer kernel, they are also likely to have newer hardware as a whole which would necessitate a newer, backported nvidia-driver as well. It is a very questionable bug report, and for me as a maintainer (not of this package though) it discourages me from doing more backports (just a personal opinion/feeling). I hope my bug report didn't dissuade you from contributing to Debian. At the same time, I am not seeing what's the problem as there is a dependency conflict and I am simply reporting that conflict so that the maintainers are aware of it. There is nothing personal about this. Ultimately I was just trying to help. -- Alex Relis OpenPGP_signature Description: OpenPGP digital signature
Bug#1024852: nvidia-driver in bullseye (470.141.03-1~deb11u1) and bullseye-backports (470.103.01-1~bpo11+1) do not support Linux kernel 6.0 or later
Package: nvidia-driver Version: 470.103.01-1~bpo11+1 Severity: grave Justification: renders package unusable Dear Maintainer, About a week ago, linux-image-6.0.0-0.deb11.2-amd64 was introduced in bullseye-backports. The problem is that the nvidia-driver version in both bullseye (470.141.03-1~deb11u1) and bullseye-backports (470.103.01-1~bpo11+1) (for some reason, the version in bullseye is newer which is strange) DO NOT support Linux kernel 6.0. When a user who uses a backported linux kernel and nvidia-driver upgrades their system, they will get an error message that looks like this https://imgur.com/sEVx1vc (sorry if I couldn't give you the text output; I am reporting this on behalf of a friend) This issue is reproducable and happened on two of my friends' machines. We found a current workaround that involves booting to kernel 5.1x in the Grub menu, running sudo apt purge linux-image-6.0.0-0.deb11.2-amd64 && sudo apt install -t bullseye-backports nvidia-driver && sudo reboot now. According to this Phoronix article ( https://www.phoronix.com/news/NVIDIA-515.76-Linux-Driver ), nvidia-driver 515.76 or newer support Linux kernel 6.0. I believe the solution is to upgrade nvidia-driver to 515.76 or newer in bullseye-backports so that users can use their graphics card on kernel 6.0. Thank you for reading my bug report and I hope you guys have a great day! -- Alex Relis
Bug#1015972: k3b: CD fails to burn, even with correct permissions
Package: k3b Version: 20.12.2-1 Severity: important Dear Maintainer, I have an optical disc reader/burner and needed to burn an Audio CD, so I opened K3b, created a new Audio CD project, and hit "Burn". It took awhile to burn, and in the middle of it I get an error message: Solution: Check permissions via Settings -> Configure K3b... -> Programs -> Permissions. If K3b's default value is set make sure you are member of "operator" group. Insufficient permissions for cdrdao executable: /bin/cdrdao K3b uses cdrdao to actually write CDs. This actually made my CD-R a coaster, as it seems that some part of the disc was already written, but no audio is playable after testing it in VLC. I later installed xfburn, interted a new CD-R and it burned the CD without issue. Because I still wanted to use K3b, I ran the command usermod -aG operator alex as root and restarted K3b. I was greeted to another error: Insufficient permissions for cdrecord executable: /bin/wodim K3b uses cdrecord to actually write CDs. Solution: Check permissions via Settings -> Configure K3b... -> Programs -> Permissions. If K3b's default value is set make sure you are member of "operator" group. Insufficient permissions for cdrdao executable: /bin/cdrdao K3b uses cdrdao to actually write CDs. Solution: Check permissions via Settings -> Configure K3b... -> Programs -> Permissions. If K3b's default value is set make sure you are member of "operator" group. Insufficient permissions for growisofs executable: /bin/growisofs K3b uses growisofs to actually write DVDs. Without growisofs you will not be able to write DVDs. Make sure to install at least version 5.10. Solution: Check permissions via Settings -> Configure K3b... -> Programs -> Permissions. If K3b's default value is set make sure you are member of "operator" group. I logged out and logged back in, but still got the error. Then I ran the groups command. Here is the output: alex@galago-pro:~$ groups alex dialout cdrom floppy sudo audio dip operator video plugdev kvm netdev bluetooth lpadmin scanner libvirt wireshark It seems like I am a member of all the proper user groups (audio, video, cdrom, operator). After talking to some of the members of the #debian IRC channel, some helpful folks linked me to #983861 and https://salsa.debian.org/qt-kde-team/kde/k3b/-/blob/master/debian/README.Debian and I also found #401057. Looks like k3b is falsely requiring the operator group instead of cdrom, but even when you add your user to operator and cdrom, K3b still errors out, asking the user for operator permissions. And the README file says to run dpkg-statoverride --add root cdrom 04710 /usr/bin/wodim if I am still getting permission issues, so I ran that, and just to be safe, I rebooted my system and opened K3b. Upon opening, I didn't get an error message. Assuming that the command worked, I attempted to burn another CD-R and... it did the exact same thing as when I did it the first time... that makes two coasters. It seems like there is a problem with this package and the way it accepts permissions. Can anyone try it on their own system to confirm that the bug is reproducable? Thanks, Alex Relis -- Package-specific info: Device was not specified. Trying to find an appropriate drive... Detected CD-R drive: /dev/cdrw Using /dev/cdrom of unknown capabilities Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'HL-DT-ST' Identification : 'BD-RE BP60NB10 ' Revision : '1.02' Device seems to be: Generic mmc2 DVD-R/DVD-RW. Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R -- System Information: Debian Release: 11.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable'), (100, 'bullseye-fasttrack'), (100, 'bullseye-backports-staging') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-0.bpo.1-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages k3b depends on: ii cdparanoia 3.10.2+debian-13.1 ii cdrdao 1:1.2.4-2 ii genisoimage9:1.1.11-3.2 ii k3b-data 20.12.2-1 ii kio5.78.0-5 ii libc6 2.31-13+deb11u3 ii libk3b720.12.2-1 ii libkf5archive5 5.78.0-2 ii libkf5authcore55.78.0-2 ii libkf5bookmarks5 5.78.0-2 ii libkf5cddb54:20.12.0-1 ii libkf5completion5 5.78.0-3 ii libkf5configcore5 5.78.0-4 ii libkf5configwidgets5
Bug#1008604: RFP: grub-btrfs -- Improves grub by adding "btrfs snapshots" to the grub menu.
Package: wnpp Severity: wishlist * Package name: grub-btrfs Version : 4.11 Upstream Author : Antynea * URL : https://github.com/Antynea/grub-btrfs * License : GPL v3 Programming Lang: Not sure. It looks like a systemd/OpenRC service with a bash script Description : Improves grub by adding "btrfs snapshots" to the grub menu. Debian Testing/Sid is nice, package breakage is not. There are snapshot filesystems which allow users to rollback their apt upgrades, but actually rolling back involves booting from an external media, which is not very fun. grub-btrfs trivializes btrfs snapshots by adding them to the user's grub so they can rollback upon boot. This feature built into distros like OpenSUSE Tumbleweed. I don't think there are any packages currently in Debian that provide this functionality. Even I, a Debian Stable user would love to have this functionality for upgrades just in case. I could set my system to have unattended-upgrades and rollback if something goes wrong. This package also should be one of the easier ones to maintain, as it is just a small systemd service and a bash script. So, to any willing maintainers out there, please sponsor my package request! -- Alex :)
Bug#1001725: audiotools: dvda2track binary not found anywhere.
Package: audiotools Version: 3.1.1-1.1+b8 Severity: normal Tags: upstream Dear Maintainer, So I am trying to rip a DVD-Audio album to flac but I'm having a bit of trouble. Bear in mind that by DVD-Audio I don't mean rip a DVD movie's audio. I mean DVD Audio, the more obscure audiophile format: https://en.wikipedia.org/wiki/DVD-Audio On paper, audiotools should do the job nicely since it has dvda2track which does exactly what I need. It's even demonstrated on the website of the program: http://audiotools.sourceforge.net/screenshots.html#dvda2track However, when installing the package on Debian, the binary for dvda2track isn't found anywhere. I assumed that this was for legal reasons, so I decided to manually compile the program myself. Turns out, the upstream version of the program doesn't have dvda2track either. Do you know why this is the case? And do you know of any other way to rip DVD-A on Debian? Python Audio Tools was last updated 5 years ago, and I am unable to get ahold of the upstream developer. Thanks, Alex :) -- System Information: Debian Release: 11.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-9-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages audiotools depends on: ii libasound2 1.2.4-1.1 ii libc6 2.31-13+deb11u2 ii libcdio-cdda2 10.2+2.0.0-1+b2 ii libcdio-paranoia2 10.2+2.0.0-1+b2 ii libcdio19 2.1.0-2 ii libmp3lame03.100-3 ii libmpg123-01.26.4-1 ii libopus0 1.3.1-0.1 ii libopusfile0 0.9+20170913-1.1 ii libpulse0 14.2-2 ii libtwolame00.4.0-2 ii libvorbisenc2 1.3.7-1 ii libvorbisfile3 1.3.7-1 ii libwavpack15.4.0-1 ii python33.9.2-3 Versions of packages audiotools recommends: ii faad 2.10.0-1 ii python3-urwid 2.1.2-1 Versions of packages audiotools suggests: pn faac -- no debconf information
Bug#997660: calibre: Ah yes, I seem to be having this issue as well!
Package: calibre Version: 5.30.0+dfsg-1 Followup-For: Bug #997660 Dear Maintainer, I'm on version 5.30.0+dfsg-1 and I am still experiencing this bug. It hasn't been fixed quite yet. Here's the error I seem to be getting: alex@alex-pc:~$ calibre Traceback (most recent call last): File "/usr/bin/calibre", line 21, in sys.exit(calibre()) File "/usr/lib/calibre/calibre/gui_launch.py", line 64, in calibre main(args) File "/usr/lib/calibre/calibre/gui2/main.py", line 533, in main app, opts, args = init_qt(args) File "/usr/lib/calibre/calibre/gui2/main.py", line 124, in init_qt app = Application(args, override_program_name=override, windows_app_uid=MAIN_APP_UID) File "/usr/lib/calibre/calibre/gui2/__init__.py", line 894, in __init__ from calibre_extensions import progress_indicator RuntimeError: the sip module implements API v12.0 to v12.8 but the progress_indicator module requires API v12.9 -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.14.0-trunk-amd64 (SMP w/8 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages calibre depends on: ii calibre-bin 5.30.0+dfsg-1 ii dpkg 1.20.9 ii fonts-liberation22.1.5-1 ii imagemagick 8:6.9.11.60+dfsg-1.3 ii imagemagick-6.q16 [imagemagick] 8:6.9.11.60+dfsg-1.3 ii libjpeg-turbo-progs 1:2.0.6-4 ii libjxr-tools 1.1-6+b1 ii optipng 0.7.7-2 ii poppler-utils20.09.0-3.1 ii python3 3.9.2-3 ii python3-apsw 3.36.0-r1-2 ii python3-bs4 4.10.0-2 ii python3-chardet 4.0.0-1 ii python3-chm 0.8.6-3 ii python3-css-parser 1.0.6-1 ii python3-cssselect1.1.0+ds-2 ii python3-cssutils 1.0.2-3 ii python3-dateutil 2.8.1-6 ii python3-feedparser 5.2.1-3 ii python3-html2text2020.1.16-1 ii python3-html5-parser 0.4.10-1 ii python3-html5lib 1.1-3 ii python3-jeepney 0.6.0-1 ii python3-lxml 4.6.3+dfsg-1 ii python3-markdown 3.3.4-1 ii python3-mechanize1:0.4.5-2 ii python3-msgpack 1.0.2-2 ii python3-netifaces0.11.0-1 ii python3-pil 8.3.2-1 ii python3-pkg-resources58.2.0-1 ii python3-py7zr0.11.3+dfsg-1 ii python3-pygments 2.7.1+dfsg-2.1 ii python3-pyparsing2.4.7-1 ii python3-pyqt55.15.5+dfsg-1 ii python3-pyqt5.qtsvg 5.15.5+dfsg-1 ii python3-pyqt5.qtwebengine5.15.5-1 ii python3-pyqt5.sip12.9.0-3 ii python3-regex0.1.20211008-1 ii python3-routes 2.5.1-1 ii python3-speechd 0.10.2-3 ii python3-zeroconf 0.36.9-1 ii python3.93.9.7-4 ii xdg-utils1.1.3-4.1 Versions of packages calibre recommends: ii python3-dnspython 2.0.0-1 ii python3-ipython7.22.0-1 ii udisks22.9.4-1 Versions of packages calibre suggests: ii python3-openssl 21.0.0-1 pn python3-unrardll -- no debconf information
Bug#979521: openboard-common depends on libjs-jquery-i18n-properties that was removed from unstable
Package: openboard-common Version: 1.5.4+dfsg1-1 Followup-For: Bug #979521 Dear Maintainer, I am having the same problem. `openboard-common` needs `libjs-jquery-i18n-properties` but it doesn't currently exist in Sid. As a result, installing `openboard` yields the following output: root@alex-pc:~# apt install openboard-common 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: openboard-common : Depends: libjs-jquery-i18n-properties but it is not installable Recommends: fonts-linex but it is not going to be installed E: Unable to correct problems, you have held broken packages. Adding `libjs-jquery-i18n-properties` would fix the issue, and it looks like somebody is going to reintroduce the package: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980416 So in that case, I send my digital high-five to Mike Gabriel. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages openboard-common depends on: pn fonts-ecolier-court pn fonts-ecolier-lignes-court pn fonts-sil-andika ii libjs-jquery 3.5.1+dfsg+~3.5.5-7 pn libjs-jquery-i18n-properties pn libjs-jquery-ui pn libjs-modernizr pn libjs-mustache Versions of packages openboard-common recommends: pn fonts-linex openboard-common suggests no packages.
Bug#979729: Problem magically fixed itself...?
Interestingly enough, I had a (probably unrelated) issue where WPA_Supplicant, plasmashell, and kworker were using 100% CPU, forcing me to reboot. And now upon reboot my Bluetooth works perfectly fine. I swear I didn't do anything else. Issue fixed on my end.
Bug#979729: firmware-realtek: WiFi works fine with Realtek RTL8822CE but Bluetooth doesn't work at all.
Package: firmware-realtek Version: 20201118-1 Severity: important Dear Maintainer, Bluetooth doesn't work at all. It is not appearing as a device in bluetoothctl or bluedevil. >From what I can tell, `dmesg` even reports that the firmware loaded >successfully. [ 21.488979] bluetooth hci0: firmware: direct-loading firmware rtl_bt/rtl8822cu_fw.bin [ 21.489472] bluetooth hci0: firmware: direct-loading firmware rtl_bt/rtl8822cu_config.bin) Updating packages and using a kernel from unstable did not fix the issue. The expected outcome is for the Bluetooth device to be detected with the ability to pair with other devices. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled firmware-realtek depends on no packages. firmware-realtek recommends no packages. Versions of packages firmware-realtek suggests: ii initramfs-tools 0.139 -- no debconf information
Bug#931900: Program crashes with message "free(): double free detected in tcache 2"
Oh, my bad. Weird that I didn't see it. Looks like there is a fix in that other bug report. Good luck. On 7/12/19 1:52 AM, Bernhard Übelacker wrote: > Hello > the issue you observed might be already reported in: > https://bugs.debian.org/924925 > > Kind regards, > Bernhard > signature.asc Description: OpenPGP digital signature
Bug#931900: Program crashes with message "free(): double free detected in tcache 2"
Package: projectm-pulseaudio Version: 2.1.0+dfsg-4+b4 Severity: grave Dear Maintainer, First off, I'm new to the BTS so excuse me for not doing this right. projectm-pulseaudio crashes after a few seconds in Buster. Typing "N" to go to the next visualization effect crashes the program instantly. Here is a log: user@debian:~$ projectM-pulseaudio dir:/usr/share/projectM/config.inp reading ~/.projectM/config.inp [projectM] config file: /home/user/.projectM/config.inp No Textures Loaded from "/usr"/share/projectM/textures [projectM] Allocating idle preset... [PresetFactory] path is Geiss & Sperl - Feedback (projectM idle HDR mix).milk [PresetFactory] url is idle://Geiss & Sperl - Feedback (projectM idle HDR mix).milk unconnected: connecting... connectHelper: "alsa_output.pci-_00_1b.0.analog-stereo.monitor" CREATED READY [PresetFactory] path is r/share/projectM/presets/phat_CloseIncounetersV2.milk [PresetFactory] url is /usr/share/projectM/presets/phat_CloseIncounetersV2.milk free(): double free detected in tcache 2 Aborted Not a programmer so I really don't know what "free(): double free detected in tcache 2", but I can only assume that's where the problem lies. Thank you, and have a great day/night. -Alex Relis -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages projectm-pulseaudio depends on: ii libc6 2.28-10 ii libftgl2 2.4.0-2 ii libgcc11:8.3.0-6 ii libglew2.1 2.1.0-4 ii libprojectm-qt1v5 2.1.0+dfsg-4+b4 ii libprojectm2v5 2.1.0+dfsg-4+b4 ii libpulse0 12.2-4 ii libqt4-opengl 4:4.8.7+dfsg-18 ii libqtcore4 4:4.8.7+dfsg-18 ii libqtgui4 4:4.8.7+dfsg-18 ii libstdc++6 8.3.0-6 ii pulseaudio 12.2-4 projectm-pulseaudio recommends no packages. projectm-pulseaudio suggests no packages. -- no debconf information signature.asc Description: OpenPGP digital signature
Bug#931834: Menu icons appear as black boxes
Package: retroarch Version: 1.7.3+dfsg1-1 Severity: normal Dear Maintainer, This is my first bug report, so bear with me. Upon opening RetroArch after upgrading from stretch to buster, I was greeted with black boxes instead of icons in the xmb menu (the default layout). Thinking it was a problem with my specific icon theme (I was using Monochrome), I switched my icon theme to something else and there are still black boxes. In fact, with some themes, every icon is black. I asked a friend whether or not he was experiencing the same problem and he was. That is what prompted me to file this report. Hope there is an easy fix. Thank you for your time, Alex Relis -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages retroarch depends on: ii fonts-dejavu-core 2.37-1 ii libasound21.1.8-1 ii libavcodec58 7:4.1.3-1 ii libavformat58 7:4.1.3-1 ii libavutil56 7:4.1.3-1 ii libc6 2.28-10 ii libdrm2 2.4.97-1 ii libegl1 1.1.0-1 ii libfreetype6 2.9.1-3 ii libgbm1 18.3.6-2 ii libgcc1 1:8.3.0-6 ii libgl11.1.0-1 ii libjack-jackd2-0 [libjack-0.125] 1.9.12~dfsg-2 ii libminiupnpc172.1-1+b1 ii libopenal11:1.19.1-1 ii libpulse0 12.2-4 ii libqt5core5a 5.11.3+dfsg1-1 ii libqt5gui55.11.3+dfsg1-1 ii libqt5widgets55.11.3+dfsg1-1 ii libretro-core-info1.3.6+git20160816-1 ii libsdl2-2.0-0 2.0.9+dfsg1-1 ii libstdc++68.3.0-6 ii libswresample37:4.1.3-1 ii libswscale5 7:4.1.3-1 ii libudev1 241-5 ii libusb-1.0-0 2:1.0.22-2 ii libv4l-0 1.16.3-3 ii libwayland-client01.16.0-1 ii libwayland-cursor01.16.0-1 ii libwayland-egl1 1.16.0-1 ii libx11-6 2:1.6.7-1 ii libx11-xcb1 2:1.6.7-1 ii libxcb1 1.13.1-2 ii libxext6 2:1.3.3-1+b2 ii libxinerama1 2:1.1.4-2 ii libxkbcommon0 0.8.2-1 ii libxv12:1.0.11-1 ii libxxf86vm1 1:1.1.4-1+b2 ii retroarch-assets 1.3.6+git20160731+dfsg1-2 ii zlib1g1:1.2.11.dfsg-1 retroarch recommends no packages. retroarch suggests no packages. -- no debconf information signature.asc Description: OpenPGP digital signature
