[Touch-packages] [Bug 1890858] Re: AppArmor profile causes QEMU/KVM - Not Connected
The apparmor section of this is now properly covered in bug 1932537, therefore I'm dropping the apparmor task from this one. ** No longer affects: apparmor (Ubuntu) ** No longer affects: apparmor (Ubuntu Focal) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1890858 Title: AppArmor profile causes QEMU/KVM - Not Connected Status in libvirt package in Ubuntu: Invalid Status in libvirt source package in Focal: Fix Committed Bug description: [Impact] * libvirt in Focal in some cases e.g. with non local users needs to resolve those users. When trying to do so it fails due to apparmor isolation and breaks badly. * In later and former releases this issue isn't triggered, but it is unknown which (potentially complex) set of changes did that. A simple apparmor rule would help to allow libvirt to better function in environments with non known user IDs. [Test Plan] * Following these steps in an unfixed release triggers the issue sudo apt update; sudo apt dist-upgrade -y sudo apt install -y sssd sssd-ldap slapd ldap-utils openssl expect lsb-release libvirt-clients libvirt-daemon-system ubuntu-dev-tools pull-lp-source sssd cd sssd-2.4.1 echo "*;*;*;Al-2400;libvirt" | sudo tee -a /etc/security/group.conf head -n -5 debian/tests/ldap-user-group-ldap-auth > debian/tests/lp1890858-test chmod +x debian/tests/lp1890858-test sudo ./debian/tests/lp1890858-test sudo systemctl restart libvirtd # ensure it works in a normal login virsh list journalctl -u libvirtd # try the sssd login sudo login # use testuser1 / testuser1secret to log in virsh list If affected this will not work reporting an error like: $ virsh list error: failed to connect to the hypervisor error: End of file while reading data: Input/output error And in dmesg/journal an apparmor denial like: Jun 14 11:25:26 ldap.example.com audit[48330]: AVC apparmor="DENIED" operation="bind" profile="libvirtd" pid=48330 comm="rpc-worker" family="unix" sock_type="dgram" protocol=0 requested_mask="bind" denied_mask="bind" addr="@userdb-f283d575d74df972f9e10bd14d0befe3" [Where problems could occur] * Allowing a little bit more to a daemon that already is rather powerful and open in regard to it's profile usually isn't changing behavior. If anything it would be considered a potential risk, but this rule should be ok to be added and ubuntu-security confirmed this. [Other Info] * Comment 38 confirms that this should be ok - from the security Teams POV. https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1890858/comments/38 --- On some focal 20.04 systems, users are seeing "QEMU/KVM - Not Connected" when they attempt to use virt-manager to manage virtual machines. AppArmor denials like the following are seen in the logs: sudo grep libvirt /var/log/syslog | grep -i apparmor | grep -i denied Jun 28 14:53:27 koromicha kernel: [ 334.660844] audit: type=1400 audit(1593345207.778:951): apparmor="DENIED" operation="bind" profile="libvirtd" pid=12254 comm="libvirtd" family="unix" sock_type="dgram" protocol=0 requested_mask="bind" denied_mask="bind" addr="@userdb-6228daaaf66b14dfd14d93ef46d962c3" Jun 28 14:54:19 koromicha kernel: [ 386.034970] audit: type=1400 audit(1593345259.145:952): apparmor="DENIED" operation="bind" profile="libvirtd" pid=14311 comm="libvirtd" family="unix" sock_type="dgram" protocol=0 requested_mask="bind" denied_mask="bind" addr="@userdb-c861507740da1fa0c3356ad3b78bffe9" Jun 28 15:02:30 koromicha kernel: [ 877.339057] audit: type=1400 audit(1593345750.437:968): apparmor="DENIED" operation="bind" profile="libvirtd" pid=16175 comm="libvirtd" family="unix" sock_type="dgram" protocol=0 requested_mask="bind" denied_mask="bind" addr="@userdb-7d70643a9f8da0342f6359907817b664" Users have reported that the "solution" is to disable the AppArmor profile. More details, screenshots, etc. can be found here: https://kifarunix.com/how-to-fix-qemu-kvm-not-connected-error-on- ubuntu-20-04/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1890858/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1932537] Re: CUPS + SSSD: cannot access local CUPS web interface with domain user (apparmor problem)
Cups rightfully includes nameservices like: #include After our analysis in bug 1890858 I think it is fair to request an SRU update apparmor in Focal (only needed there, see bug 1890858 for details). As it would fix this element in Cups and actually in many other potential places as well. Adding "unix (bind) type=dgram addr=@userdb-*," in abstractions/nameservice in Focal seems right to me. --- Furthermore abstractions/nameservice already wants to allow sssd: 37 # When using sssd, the passwd and group files are stored in an alternate path 38 # and the nss plugin also needs to talk to a pipe 39 /var/lib/sss/mc/group r, 40 /var/lib/sss/mc/initgroups r, 41 /var/lib/sss/mc/passwd r, 42 /var/lib/sss/pipes/nss rw, I don't know if /var/lib/sss/pipes/private/pam rw, is a default configuration nor if it would be a safe path to allow. But it could pretty much be. If ok this one would likely be needed/wanted in >=Bionic into abstractions/nameservice --- Both changes IMHO would have to be done by the security Team in regard to the apparmor package, therefore I'll add a bug task for this and assign them to have a look. ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Changed in: apparmor (Ubuntu) Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1932537 Title: CUPS + SSSD: cannot access local CUPS web interface with domain user (apparmor problem) Status in apparmor package in Ubuntu: New Status in cups package in Ubuntu: New Bug description: [Summary] My domain user can not access the local CUPS web interface due to apparmor denials. Adding the following two lines to /etc/apparmor.d/local/usr.sbin.cupsd fixes it: /var/lib/sss/pipes/private/pam rw, unix (bind) type=dgram addr=@userdb-*, [Details] I have a (relatively) clean install of Ubuntu 20.04 (no upgrade), which is joined to a Windows AD-domain via sssd, but currently used off site with cached credentials. When I try to log in with my domain user (who is in the lpadmingroup) at the local cups web interface (localhost:631 ...> Add Printer) with the default apparmor config for cupsd I get a: AVC apparmor="DENIED" operation="connect" profile="/usr/sbin/cupsd" name="/var/lib/sss/pipes/private/pam" pid=189759 comm="cupsd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 This already existed in Bionic and my workaround was to add '/var/lib/sss/pipes/private/pam rw,' to /etc/apparmor.d/local/usr.sbin.cupsd and reload the profile: # echo '/var/lib/sss/pipes/private/pam rw,' > /etc/apparmor.d/local/usr.sbin.cupsd # apparmor_parser -r -W -T /etc/apparmor.d/usr.sbin.cupsd This worked in Bionic, but leads to a crash of cupsd in Focal when I try to log in as domain user with a the following log message nearby: AVC apparmor="DENIED" operation="bind" profile="/usr/sbin/cupsd" pid=189759 comm="cupsd" family="unix" sock_type="dgram" protocol=0 requested_mask="bind" denied_mask="bind" addr="@userdb-7625b1ef65396344ef05f0a8aeda870e" This looks very similar to https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1890858 , so I applied the same fix and added 'unix (bind) type=dgram addr=@userdb-*,' to /etc/apparmor.d/local/usr.sbin.cupsd: # echo 'unix (bind) type=dgram addr=@userdb-*,' >> /etc/apparmor.d/local/usr.sbin.cupsd # apparmor_parser -r -W -T /etc/apparmor.d/usr.sbin.cupsd Which fixed my problem. I am not an expert on apparmor, so I have no idea, if the first line gives too broad permissions. I think that there are two unrelated issues: 1) Cupsd cannot access sssd at all. This already existed in Bionic (but I failed to report the issue -- sorry for that). 2) Once the login succeeds, cups tries to resolve a uid/gid as it isn't known locally. To resolve it it needs to bind a unix socket. See: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1890858/comments/37 I will attach a full log with added comments on what I did. [Infos] 1) lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 2) apt-cache policy cups-daemon cups-daemon: Installiert: 2.3.1-9ubuntu1.1 Installationskandidat: 2.3.1-9ubuntu1.1 Versionstabelle: *** 2.3.1-9ubuntu1.1 500 500 http://ftp.uni-hannover.de/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://ftp.uni-hannover.de/ubuntu focal/main amd64
[Touch-packages] [Bug 1890858] Re: AppArmor profile causes QEMU/KVM - Not Connected
Thanks for the quick test, works for me as well. The global verification-done tag might be needed as well for the tools to work, adding that back. ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1890858 Title: AppArmor profile causes QEMU/KVM - Not Connected Status in apparmor package in Ubuntu: Invalid Status in libvirt package in Ubuntu: Invalid Status in apparmor source package in Focal: New Status in libvirt source package in Focal: Fix Committed Bug description: [Impact] * libvirt in Focal in some cases e.g. with non local users needs to resolve those users. When trying to do so it fails due to apparmor isolation and breaks badly. * In later and former releases this issue isn't triggered, but it is unknown which (potentially complex) set of changes did that. A simple apparmor rule would help to allow libvirt to better function in environments with non known user IDs. [Test Plan] * Following these steps in an unfixed release triggers the issue sudo apt update; sudo apt dist-upgrade -y sudo apt install -y sssd sssd-ldap slapd ldap-utils openssl expect lsb-release libvirt-clients libvirt-daemon-system ubuntu-dev-tools pull-lp-source sssd cd sssd-2.4.1 echo "*;*;*;Al-2400;libvirt" | sudo tee -a /etc/security/group.conf head -n -5 debian/tests/ldap-user-group-ldap-auth > debian/tests/lp1890858-test chmod +x debian/tests/lp1890858-test sudo ./debian/tests/lp1890858-test sudo systemctl restart libvirtd # ensure it works in a normal login virsh list journalctl -u libvirtd # try the sssd login sudo login # use testuser1 / testuser1secret to log in virsh list If affected this will not work reporting an error like: $ virsh list error: failed to connect to the hypervisor error: End of file while reading data: Input/output error And in dmesg/journal an apparmor denial like: Jun 14 11:25:26 ldap.example.com audit[48330]: AVC apparmor="DENIED" operation="bind" profile="libvirtd" pid=48330 comm="rpc-worker" family="unix" sock_type="dgram" protocol=0 requested_mask="bind" denied_mask="bind" addr="@userdb-f283d575d74df972f9e10bd14d0befe3" [Where problems could occur] * Allowing a little bit more to a daemon that already is rather powerful and open in regard to it's profile usually isn't changing behavior. If anything it would be considered a potential risk, but this rule should be ok to be added and ubuntu-security confirmed this. [Other Info] * Comment 38 confirms that this should be ok - from the security Teams POV. https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1890858/comments/38 --- On some focal 20.04 systems, users are seeing "QEMU/KVM - Not Connected" when they attempt to use virt-manager to manage virtual machines. AppArmor denials like the following are seen in the logs: sudo grep libvirt /var/log/syslog | grep -i apparmor | grep -i denied Jun 28 14:53:27 koromicha kernel: [ 334.660844] audit: type=1400 audit(1593345207.778:951): apparmor="DENIED" operation="bind" profile="libvirtd" pid=12254 comm="libvirtd" family="unix" sock_type="dgram" protocol=0 requested_mask="bind" denied_mask="bind" addr="@userdb-6228daaaf66b14dfd14d93ef46d962c3" Jun 28 14:54:19 koromicha kernel: [ 386.034970] audit: type=1400 audit(1593345259.145:952): apparmor="DENIED" operation="bind" profile="libvirtd" pid=14311 comm="libvirtd" family="unix" sock_type="dgram" protocol=0 requested_mask="bind" denied_mask="bind" addr="@userdb-c861507740da1fa0c3356ad3b78bffe9" Jun 28 15:02:30 koromicha kernel: [ 877.339057] audit: type=1400 audit(1593345750.437:968): apparmor="DENIED" operation="bind" profile="libvirtd" pid=16175 comm="libvirtd" family="unix" sock_type="dgram" protocol=0 requested_mask="bind" denied_mask="bind" addr="@userdb-7d70643a9f8da0342f6359907817b664" Users have reported that the "solution" is to disable the AppArmor profile. More details, screenshots, etc. can be found here: https://kifarunix.com/how-to-fix-qemu-kvm-not-connected-error-on- ubuntu-20-04/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1890858/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1930279] Re: [Ivy Bridge] flashing triangles on screen
** Changed in: linux (Ubuntu) Assignee: Amirhossein (bokensmile8) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1930279 Title: [Ivy Bridge] flashing triangles on screen Status in linux package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: when i did upgrade my ubuntu from 20.04 to 20.10 i have small winking triangles on my screen, they sometimes will appear when i watching a youtube video they will appear on the video's seek bar or when i typing they will appear on selected texts,but the main and most annoying state of it happens when I am playing minecraft,my entire game screen has these little triangles ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 31 18:05:33 2021 DistUpgraded: 2021-05-27 14:18:07,483 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [1043:844d] InstallationDate: Installed on 2020-01-10 (507 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=a5a5279f-cdf5-4129-94fa-8f17f7401833 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2021-05-27 (4 days ago) dmi.bios.date: 03/19/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1204 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1204:bd03/19/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLXR2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930279/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876056] Re: No automatic switch to headset microphone on connect
Suggestions for PulseAudio developers should be made as new issues at: https://gitlab.freedesktop.org/groups/pulseaudio/-/issues -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1876056 Title: No automatic switch to headset microphone on connect Status in pulseaudio package in Ubuntu: Invalid Bug description: On my Dell XPS 7590, when I plugin a headset with a 4-pin-connector, the audio OUTPUT automatically switches from the speakers in the laptop to the headset. However, the audio INPUT does not switch from the microphone in the laptop to the microphone in the headset. Using for example pavucontrol, I can switch to the microphone manually on the tab 'input devices' - on that tab Port will be on 'Internal Microphone' and I can set it to 'Headset Microphone'. What's even more confusing is that when I unplug the headset, both input AND output switch back to internal automatically and the port on the 'Input Devices'. This is on Ubuntu 19.10 with kernel 5.4.28-050428-generic (but I also see the same issue on kernel 5.3.0-48) and pulseaudio 1:13.0-1ubuntu1.1. If any more information is needed, let me know. inxi -F: System:Host: idefixpsie Kernel: 5.4.28-050428-generic x86_64 bits: 64 Desktop: KDE Plasma 5.16.5 Distro: Ubuntu 19.10 (Eoan Ermine) Machine: Type: Laptop System: Dell product: XPS 15 7590 v: N/A serial: Mobo: Dell model: 0VYV0G v: A00 serial: UEFI: Dell v: 1.5.0 date: 12/25/2019 Battery: ID-1: BAT0 charge: 77.7 Wh condition: 87.4/97.0 Wh (90%) CPU: Topology: 6-Core model: Intel Core i7-9750H bits: 64 type: MT MCP L2 cache: 12.0 MiB Speed: 4029 MHz max: 4500 MHz Core speeds (MHz): 1: 4213 2: 4160 3: 4229 4: 4210 5: 4224 6: 4163 7: 4280 8: 4189 9: 4291 10: 4198 11: 4149 12: 4188 Graphics: Device-1: Intel UHD Graphics 630 driver: i915 v: kernel Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 3840x2160~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics 630 (Coffeelake 3x8 GT2) v: 4.5 Mesa 19.2.8 Audio: Device-1: Intel Cannon Lake PCH cAVS driver: snd_hda_intel Sound Server: ALSA v: k5.4.28-050428-generic Network: Device-1: Intel driver: iwlwifi IF: wlan0 state: up mac: 5c:80:b6:7a:2c:45 IF-ID-1: docker0 state: down mac: 02:42:90:4c:31:a2 Drives:Local Storage: total: 953.87 GiB used: 67.58 GiB (7.1%) ID-1: /dev/nvme0n1 model: SSDPEMKF010T8 NVMe INTEL 1024GB size: 953.87 GiB Partition: ID-1: / size: 496.44 GiB used: 67.27 GiB (13.6%) fs: ext4 dev: /dev/dm-1 ID-2: /boot size: 704.5 MiB used: 288.4 MiB (40.9%) fs: ext4 dev: /dev/nvme0n1p2 ID-3: swap-1 size: 6.61 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/dm-2 Sensors: System Temperatures: cpu: 47.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 346 Uptime: 2d 17h 51m Memory: 31.12 GiB used: 9.08 GiB (29.2%) Shell: bash inxi: 3.0.36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876056/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925055] Re: Boot stuck in UEFI after enrolling keys for drivers
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Expired Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925215] Re: System completely freezes and requires reboot
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925215 Title: System completely freezes and requires reboot Status in systemd package in Ubuntu: Expired Bug description: The OS spontaneously froze whilst doing some work (firefox, VMs). I can't find anything suspect in the logs at this stage. I will keep an eye out for this issue but would like advise on what to check for, any tools I should install and commands to run when it crashes again. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Apr 20 14:28:46 2021 ExecutablePath: /usr/lib/systemd/systemd InstallationDate: Installed on 2021-04-16 (3 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=linux PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=739968f7-1aa4-47f1-8d68-55af0ffb428d ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/systemd-localed.service → /usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.30 dmi.board.name: Z77 OC Formula dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.30:bd07/11/2013:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77OCFormula:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1925215/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()
The Mesa developers won't be monitoring this bug. For more current information please subscribe to https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859 instead. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1871959 Title: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush() Status in Mesa: Unknown Status in mesa package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f --- nothing particular done to trigger this, just opening the lid apparently crashed the x server (ubuntu 20.04); then after reboot apport prompted me to report a crash ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 00:50:52 2020 DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56 DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] InstallationDate: Installed on 2019-11-27 (134 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5500 ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so Title: Xorg crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago) UserGroups: dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1871959/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1930910] Re: Fix micmute hotkeys on HP ProBooks
** Also affects: systemd (Ubuntu Impish)
Importance: Undecided
Status: Fix Committed
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Groovy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1930910
Title:
Fix micmute hotkeys on HP ProBooks
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in systemd package in Ubuntu:
Fix Committed
Status in systemd source package in Focal:
New
Status in systemd source package in Groovy:
New
Status in systemd source package in Hirsute:
New
Status in systemd source package in Impish:
Fix Committed
Bug description:
[Impact]
Micmute hotkey on many HP ProBooks don't work.
[Fix]
Commit a7161e0288d1 ("hwdb: Add ProBook to use micmute hotkey"), to map AT
keyboard's scancode to micmute hotkey.
[Test]
With the one-liner fix, micmute hotkey works on all the ProBooks I tested.
[Where problems could occur]
The hwdb originally only matches a few ProBooks, the fix changes that to
match all ProBook models. So if there's any ProBook that uses the scancode for
another purpose, there will be a regression.
However, the risk is rather slim because HP explicitly states that all
ProBooks use the same scancode for mic mute hotkey.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1930910/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1370953] Re: layout switch is delayed
Fixed in Ubuntu 21.04 for me -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1370953 Title: layout switch is delayed Status in console-setup package in Ubuntu: Confirmed Status in gconf package in Ubuntu: Confirmed Bug description: I have two layouts configured En and Ru with Ctrl-Shift as layout switch combo. When I start typing in wrong layout I notice it, hit Ctrl-Shift and type again, but more often than not it is wrong layout again. I repeat the action, but there is no luck. On the third attemt it usually either works OR the first letter is still in wrong layout, but the second is in correct one - i.e. layout switches as I type. The explanation for this is that layout switch takes very unreasonable time - much longer than it is needed to move your fingers from one key to the other. Each time I encounter the error I retry slower so on the third attempt it is slow enough to actually recognize that layout switch is happening, but with a delay. This is extremely annoying and unacceptable. If someone knows how to work around it - please post your suggestions here. It would be nice to have a solution for 3+ layouts setup as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1370953/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1669654] Re: package pulseaudio failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
** Tags removed: artful ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1669654 Title: package pulseaudio failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in pulseaudio package in Ubuntu: Confirmed Bug description: Pulse audio has crashed completely , not able to delete as well as reinstall ProblemType: Package DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.2 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aayush 1608 F pulseaudio Date: Fri Mar 3 06:24:50 2017 DuplicateSignature: package:pulseaudio:1:8.0-0ubuntu3.2 Processing triggers for gconf2 (3.2.6-3ubuntu6) ... dpkg: error processing package linux-image-4.4.0-36-generic (--configure): package linux-image-4.4.0-36-generic is not ready for configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-01-16 (411 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: pulseaudio Title: package pulseaudio 1:8.0-0ubuntu3.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R0220DA dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR0220DA:bd11/18/2013:svnSonyCorporation:pnSVF15213SNW:pvrC10K0BT6:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVF15213SNW dmi.product.version: C10K0BT6 dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1669654/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780693] Re: package pulseaudio 1:11.1-1ubuntu7.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
*** This bug is a duplicate of bug 1669654 *** https://bugs.launchpad.net/bugs/1669654 ** This bug has been marked a duplicate of bug 1669654 package pulseaudio failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1780693 Title: package pulseaudio 1:11.1-1ubuntu7.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in pulseaudio package in Ubuntu: New Bug description: na ProblemType: Package DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_40 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: libpulse-mainloop-glib0:amd64: Install libpulse0:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1013 F pulseaudio wilber 1365 F pulseaudio Date: Sun Jul 8 22:55:37 2018 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-07-09 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.2 SourcePackage: pulseaudio Title: package pulseaudio 1:11.1-1ubuntu7.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1780693/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1931765] Re: VAAPI broken on Wayland Kubuntu 21.04 (Plasma 5.22.0 + Weston)
** Package changed: wayland (Ubuntu) => libva (Ubuntu) ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags added: hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1931765 Title: VAAPI broken on Wayland Kubuntu 21.04 (Plasma 5.22.0 + Weston) Status in libva package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: SUMMARY VAAPI is broken on KDE Plasma Wayland and Weston Session STEPS TO REPRODUCE 1. Open a terminal 2. Type in vainfo OBSERVED RESULT Error Message: heiko@Tuxedobook:~$ vainfo wl_drm@6: error 0: authenticate failed VA error: wayland: Wayland roundtrip error: Protocol error (errno 71) libva info: VA-API version 1.10.0 libva error: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null) vaInitialize failed with error code 3 (invalid VADisplay),exit EXPECTED RESULT Should show VAAPI information without errors like on X11 session This bug was reproduced multiple times on two systems one with an intel igpu and one with a dedicated AMD GPU. Both systems are using the MESA drivers from this ppa: https://launchpad.net/~kisak/+archive/ubuntu/kisak-mesa This bug was discovered because KODI Mediacenter was crashing on startup on wayland while it is working flawless on X11/X.org. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 21.04 (available in About System) KDE Plasma Version: 5.22.0 ADDITIONAL INFORMATION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libva/+bug/1931765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i
@ivandrs, only RtHDDump.txt is not enough, Please refer to: https://github.com/ryanprescott/realtek-verb-tools/wiki/How-to-sniff- verbs-from-a-Windows-sound-driver and https://github.com/thesofproject/linux/issues/2748, If could find a workable verb sequence to initialize the I2S amplifier, it will be more helpful. ** Bug watch added: github.com/thesofproject/linux/issues #2748 https://github.com/thesofproject/linux/issues/2748 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1926165 Title: Bass speakers not enabled on Lenovo Yoga 9i Status in alsa-driver package in Ubuntu: Confirmed Bug description: The Lenovo Yoga 9i has two sets of speakers: regular ones and bass speakers. The former work but while latter are detected and show up in alsamixer, they play no sound. Plugging headphones in and out or toggling any of the volume options does not fix the issue. A possibly related issue for a different Yoga version: https://bugzilla.kernel.org/show_bug.cgi?id=205755 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4466 F pulseaudio ubuntu 6219 F alsamixer /dev/snd/pcmC0D0p: ubuntu 4466 F...m pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 15:10:05 2021 LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2021 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: EHCN40WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 9 14ITL5 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5: dmi.product.family: Yoga 9 14ITL5 dmi.product.name: 82BG dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5 dmi.product.version: Yoga 9 14ITL5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1930550] Re: usb sound devices crackling
Tested mpd today all day long about 10hours - no crackling at all, even with dsd 256 (11mbit). pulse and pipewire - stable crackling (1-5 in 5 minute about 0.2-0.3s). So buses, alsa, kernel, etc cannot affect this. I can make other tests, change config settings, please suggest how to investigate further. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1930550 Title: usb sound devices crackling Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrade from 20.04 to 21.04 all 3 my usb sound devices start crackling, i have xduoo05plus, audeze mobius, audient id4. I also tried to modify default-fragments = 5 default-fragment-size-msec = 2 to different sugested on stackoverflow articles setting Also this is in my config: high-priority = yes nice-level = -11 realtime-scheduling = yes realtime-priority = 5 I even tried to switch to pipewire, but it still the same. Possible issue in alsa kernel drivers for usb interface, submitting bug to pulse as it default in ubuntu. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: pulseaudio 1:14.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Jun 2 11:11:55 2021 InstallationDate: Installed on 2019-08-13 (658 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to hirsute on 2021-05-16 (16 days ago) dmi.bios.date: 08/12/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd08/12/2015:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnB85-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85-HD3:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: B85-HD3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.system.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2021-05-18T13:33:15.787174 mtime.conffile..etc.pulse.system.pa: 2021-05-18T11:20:40.860787 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1930550/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920836] Re: Show Extended Security Maintenence status
The warnings about the status.json file are due to the ubuntu-advantage client on these older systems not yet having the feature to write this file. When updated, this should work - that's correct, right @chad.smith? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1920836 Title: Show Extended Security Maintenence status Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Committed Status in software-properties source package in Hirsute: Fix Committed Bug description: [Impact] There is not currently a graphical method of determining if a system is subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) updates. This is resolved by adding some [new UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to the software properties application. [Test Case] 1. Install latest version of Ubuntu advantage: $ sudo add-apt-repository ppa:ua-client/stable $ sudo apt update $ sudo apt upgrade 2. Open Software Properties 3. Go to Updates tab. Expected result: Information is shown that indicates if this system is using Extended Security Maintenance updates, when updates will supported until, and a link to upgrade to ESM. Observed result: No ESM information currently shown. [Where problems could occur] - Software properties could hit a bug getting a response from the ua app. The current code carefully checks if and what is returned, falling back to a safe default behavior. - Launching software properties could trigger a bug in the ua app. - Software properties could show incorrect information, causing confusion for the user. The solution uses information from distro-info and the ua app which means software-properties contains no data about ESM, and instead relies on these apps that can be updated if things change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1932583] Re: apport-cli requires a terminal to submit
Of course, it would be even better if apport provided an option to skip this dialogue altogether. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1932583 Title: apport-cli requires a terminal to submit Status in apport package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' Description: Ubuntu Impish Indri (development branch) Release: 21.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Centerapport-noui: Installed: 2.20.11-0ubuntu67 Candidate: 2.20.11-0ubuntu67 Version table: *** 2.20.11-0ubuntu67 500 500 http://archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen Let apport-cli read S from standard input. 4) What happened instead What would you like to do? Your options are: S: Send report (8.4 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): Traceback (most recent call last): File "/usr/bin/apport-cli", line 387, in if not app.run_argv(): File "/usr/lib/python3/dist-packages/apport/ui.py", line 717, in run_argv return self.run_report_bug() File "/usr/lib/python3/dist-packages/apport/ui.py", line 556, in run_report_bug response = self.ui_present_report_details(allowed_to_report) File "/usr/bin/apport-cli", line 213, in ui_present_report_details response = dialog.run() File "/usr/bin/apport-cli", line 99, in run response = self.raw_input_char( File "/usr/bin/apport-cli", line 49, in raw_input_char saved_attributes = termios.tcgetattr(file) termios.error: (25, 'Inappropriate ioctl for device') The command '/bin/sh -c ubuntu-bug libkf5i18n-dev' returned a non-zero code: 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1932583/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i
@Hui Wang Any chance to get working verbs for Yoga C930? ) I have managed to run Win10 into QEMU with working bass speakers and got the RtHDDump.txt Maybe it will be useful.. ** Attachment added: "RtHDDump.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+attachment/5505829/+files/RtHDDump.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1926165 Title: Bass speakers not enabled on Lenovo Yoga 9i Status in alsa-driver package in Ubuntu: Confirmed Bug description: The Lenovo Yoga 9i has two sets of speakers: regular ones and bass speakers. The former work but while latter are detected and show up in alsamixer, they play no sound. Plugging headphones in and out or toggling any of the volume options does not fix the issue. A possibly related issue for a different Yoga version: https://bugzilla.kernel.org/show_bug.cgi?id=205755 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4466 F pulseaudio ubuntu 6219 F alsamixer /dev/snd/pcmC0D0p: ubuntu 4466 F...m pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 15:10:05 2021 LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2021 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: EHCN40WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 9 14ITL5 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5: dmi.product.family: Yoga 9 14ITL5 dmi.product.name: 82BG dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5 dmi.product.version: Yoga 9 14ITL5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830079] Re: PAM errors logged when pam_kwallet is not installed
*** This bug is a duplicate of bug 1768488 *** https://bugs.launchpad.net/bugs/1768488 ** This bug has been marked a duplicate of bug 1768488 dependency problem lightdm -> pam -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1830079 Title: PAM errors logged when pam_kwallet is not installed Status in lightdm package in Ubuntu: New Bug description: ii lightdm1.18.3-0ubuntu amd64 Display Manager VERSION="16.04.6 LTS (Xenial Xerus)" Running with XFCE installed, I see the following in /var/log/auth.log: May 21 15:52:09 lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory May 21 15:52:09 lightdm: PAM adding faulty module: pam_kwallet.so May 21 15:52:09 lightdm: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory May 21 15:52:09 lightdm: PAM adding faulty module: pam_kwallet5.so These can be avoided by prefixing the optional components in /etc/pam.d/lightdm (and lightdm-greeter) by a "-" as follows: #%PAM-1.0 authrequisite pam_nologin.so authsufficient pam_succeed_if.so user ingroup nopasswdlogin @include common-auth -authoptionalpam_gnome_keyring.so @include common-account session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so close #session requiredpam_loginuid.so session requiredpam_limits.so @include common-session session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so open -session optionalpam_gnome_keyring.so auto_start -session optionalpam_kwallet.so auto_start -session optionalpam_kwallet5.so auto_start session requiredpam_env.so readenv=1 session requiredpam_env.so readenv=1 user_readenv=1 envfile=/etc/default/locale @include common-password From man pam.conf: If the type value from the list above is prepended with a - character the PAM library will not log to the system log if it is not possible to load the module because it is missing in the system. This can be useful especially for modules which are not always installed on the system and are not required for correct authentication and authorization of the login session. Also, isn't it required to have: -auth optional pam_kwallet.so for pam_kallet to work, as it needs access to the password? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1830079/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1861598] Re: lightdm assumes pam-kwallet to be always installed
*** This bug is a duplicate of bug 1768488 *** https://bugs.launchpad.net/bugs/1768488 ** This bug has been marked a duplicate of bug 1768488 dependency problem lightdm -> pam -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1861598 Title: lightdm assumes pam-kwallet to be always installed Status in lightdm package in Ubuntu: New Bug description: During boot, I see this error: > Feb 02 10:50:05 myhost lightdm[3224]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory > Feb 02 10:50:05 myhost lightdm[3224]: PAM adding faulty module: pam_kwallet.so > Feb 02 10:50:05 myhost lightdm[3224]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory > Feb 02 10:50:05 myhost lightdm[3224]: PAM adding faulty module: pam_kwallet5.so which I guess it's caused by this: > # grep kwallet /etc/pam.d/lightd* > /etc/pam.d/lightdm:authoptionalpam_kwallet.so > /etc/pam.d/lightdm:authoptionalpam_kwallet5.so > /etc/pam.d/lightdm:session optionalpam_kwallet.so auto_start > /etc/pam.d/lightdm:session optionalpam_kwallet5.so auto_start > /etc/pam.d/lightdm-greeter:authoptionalpam_kwallet.so > /etc/pam.d/lightdm-greeter:authoptionalpam_kwallet5.so > /etc/pam.d/lightdm-greeter:session optionalpam_kwallet.so auto_start > /etc/pam.d/lightdm-greeter:session optionalpam_kwallet5.so auto_start kwallet is a KDE program, which is not installed on MATE (and I think it shouldn't be), so I guess that such modules should not be [attempted to be] loaded. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Sun Feb 2 11:03:53 2020 InstallationDate: Installed on 2020-01-20 (12 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1861598/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768488] Re: dependency problem lightdm -> pam
The following other bugs reports say the same thing: #1861598 and #1830079 I also find the same bug in Xubuntu 20.04 and in my own custom 20.04 Ubuntu. As the bug number here is the smallest, I'll assume it is the first one that has reported it. I stumbled upon this bug while trying to find why some good computer would crash suddenly with Xubuntu 20.04. Another issue related to ACPI is probably what was happening, however looking out for other bugs while I am at it is something to be done. I also experience some crashes in my own computer at home where no ACPI issue is mentioned in the logs, but this “pam_kwallet*” related message is in my logs. (Not anymore next session because I commented out the lines in the /etc/pam.d/lightdm and lightdm-greeter files, but I know this might be a temporary turn-around if it is not fixed upstream, right?) Now my first question is : what package does this bug belong to? Is is lightdm as it seems from this present bug report? I might say "yes", because wajig gives information about the packages pam_kwallet belong to, in particular, this part of the error message is interesting: “ PAM adding faulty module: pam_kwallet.so ” Well, there is no such file in the kwallet packages. In details: *** wajig whichpackage pam_kwallet UNINSTALLED MATCHES (x3) libpam-kwallet5: /lib/x86_64-linux-gnu/security/pam_kwallet5.so libpam-kwallet-common: /etc/xdg/autostart/pam_kwallet_init.desktop libpam-kwallet-common: /usr/share/libpam-kwallet-common/pam_kwallet_init *** what files do libpam-kwallet5 and libpam-kwallet-common bring in? The wajig command will also answer this question: *** wajig listfiles libpam-kwallet5 libpam-kwallet5: /lib/x86_64-linux-gnu/security/pam_kwallet5.so libpam-kwallet5: /usr/share/doc/libpam-kwallet5/changelog.Debian.gz libpam-kwallet5: /usr/share/doc/libpam-kwallet5/copyright *** So first thing first, the lines relating to "pam_kwallet.so" should just be removed from the files lightdm and lightdm-greeter, because it simply does not exist, so I guess this is why the message states it is a "faulty module". As for the rest of the error message from the system, "PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory" I have no idea what can be done, but surely we need to do something about it. Does PAM provide other types of conditions when it comes to try to load modules? Or might there be another way to tell it not to try loading it if we are not in a KDE environment? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1768488 Title: dependency problem lightdm -> pam Status in lightdm package in Ubuntu: Confirmed Bug description: Hi, I've installed Lubuntu 18.04 and found that problem: the display-manager service complains: ● lightdm.service - Light Display Manager Loaded: loaded (/lib/systemd/system/lightdm.service; indirect; vendor preset: enabled) Active: active (running) since Wed 2018-05-02 11:36:27 CEST; 1min 22s ago Docs: man:lightdm(1) Process: 1717 ExecStartPre=/bin/sh -c [ "$(basename $(cat /etc/X11/default-display-manager 2>/dev/null))" = "lightdm" ] (code=exited, status=0/SUCCESS) Main PID: 1720 (lightdm) Tasks: 6 (limit: 4915) CGroup: /system.slice/lightdm.service ├─1720 /usr/sbin/lightdm ├─1726 /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch └─1786 lightdm --session-child 12 19 Mai 02 11:36:29 pcdanisch lightdm[1735]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory Mai 02 11:36:29 pcdanisch lightdm[1735]: PAM adding faulty module: pam_kwallet5.so Mai 02 11:36:29 pcdanisch lightdm[1735]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0) Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or directory Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM adding faulty module: pam_gnome_keyring.so Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM adding faulty module: pam_kwallet.so Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM adding faulty module: pam_kwallet5.so Mai 02 11:36:30 pcdanisch lightdm[1786]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "danisch" It's
[Touch-packages] [Bug 1861408] Re: firefox apparmor messages
Linux Mint 20.1 Ulyssa Firefox 89.0 after update, i got ff 89, i have messages like this in syslog, on every start of firefox: Jun 20 15:24:23 dinar-Lenovo-G580 wpa_supplicant[680]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-80 noise=-95 txrate=43300 Jun 20 15:25:21 dinar-Lenovo-G580 kernel: [22164.956789] audit: type=1400 audit(1624191921.071:165): apparmor="DENIED" operation="open" profile="firefox" name="/sys/devices/pci:00/:00:1f.2/resource" pid=15814 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Jun 20 15:25:21 dinar-Lenovo-G580 kernel: [22164.956816] firefox[15814]: segfault at 0 ip 7ff585b5ad94 sp 7ffceca77710 error 6 in libxul.so[7ff582318000+5392000] Jun 20 15:25:21 dinar-Lenovo-G580 kernel: [22164.956822] Code: 00 e8 28 69 7c fc 50 80 3d f8 0b 4e 04 00 74 02 58 c3 c6 05 ed 0b 4e 04 01 48 8d 05 29 15 fc 02 48 8b 0d 47 36 3c 04 48 89 01 04 25 00 00 00 00 8b 01 00 00 e8 f4 68 7c fc 66 2e 0f 1f 84 00 Jun 20 15:25:21 dinar-Lenovo-G580 systemd[1]: Started Process Core Dump (PID 15815/UID 0). Jun 20 15:25:21 dinar-Lenovo-G580 kernel: [22164.998424] audit: type=1400 audit(1624191921.111:166): apparmor="DENIED" operation="open" profile="firefox" name="/run/user/1000/ICEauthority" pid=15809 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Jun 20 15:25:21 dinar-Lenovo-G580 systemd-coredump[15816]: Process 15814 (firefox) of user 1000 dumped core.#012#012Stack trace of thread 15814:#012#0 0x7ff585b5ad94 n/a (libxul.so + 0x4185d94)#012#1 0x7ff58ca19a27 __run_exit_handlers (libc.so.6 + 0x49a27)#012#2 0x7ff58ca19be0 __GI_exit (libc.so.6 + 0x49be0)#012#3 0x7ff5816f6c45 n/a (libpci.so.3 + 0x3c45)#012#4 0x7ff5816fc308 n/a (libpci.so.3 + 0x9308)#012#5 0x7ff585b64054 n/a (libxul.so + 0x418f054)#012#6 0x7ff585b649db n/a (libxul.so + 0x418f9db)#012#7 0x7ff585b5a13e n/a (libxul.so + 0x418513e)#012#8 0x7ff585b60ae3 n/a (libxul.so + 0x418bae3)#012#9 0x7ff585b60ee0 n/a (libxul.so + 0x418bee0)#012#10 0x556820bc9113 n/a (firefox + 0xc113)#012#11 0x7ff58c9f70b3 __libc_start_main (libc.so.6 + 0x270b3)#012#12 0x556820bc8b6e _start (firefox + 0xbb6e) Jun 20 15:25:21 dinar-Lenovo-G580 systemd[1]: systemd-coredump@8-15815-0.service: Succeeded. Jun 20 15:25:21 dinar-Lenovo-G580 kernel: [22165.724715] audit: type=1400 audit(1624191921.839:167): apparmor="DENIED" operation="open" profile="firefox" name="/proc/15809/cgroup" pid=15809 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Jun 20 15:25:21 dinar-Lenovo-G580 kernel: [22165.862576] audit: type=1107 audit(1624191921.975:168): pid=657 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/RealtimeKit1" interface="org.freedesktop.DBus.Properties" member="Get" mask="send" name="org.freedesktop.RealtimeKit1" pid=15895 label="firefox" peer_pid=978 peer_label="unconfined" Jun 20 15:25:21 dinar-Lenovo-G580 kernel: [22165.862576] exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?' Jun 20 15:25:22 dinar-Lenovo-G580 kernel: [22166.090862] audit: type=1107 audit(1624191922.207:169): pid=657 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/RealtimeKit1" interface="org.freedesktop.DBus.Properties" member="Get" mask="send" name="org.freedesktop.RealtimeKit1" pid=15809 label="firefox" peer_pid=978 peer_label="unconfined" Jun 20 15:25:22 dinar-Lenovo-G580 kernel: [22166.090862] exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?' Jun 20 15:25:22 dinar-Lenovo-G580 kernel: [22166.676720] audit: type=1107 audit(1624191922.791:170): pid=657 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/RealtimeKit1" interface="org.freedesktop.DBus.Properties" member="Get" mask="send" name="org.freedesktop.RealtimeKit1" pid=15973 label="firefox" peer_pid=978 peer_label="unconfined" Jun 20 15:25:22 dinar-Lenovo-G580 kernel: [22166.676720] exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?' Jun 20 15:25:23 dinar-Lenovo-G580 kernel: [22167.484270] audit: type=1107 audit(1624191923.599:171): pid=657 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/RealtimeKit1" interface="org.freedesktop.DBus.Properties" member="Get" mask="send" name="org.freedesktop.RealtimeKit1" pid=16038 label="firefox" peer_pid=978 peer_label="unconfined" Jun 20 15:25:23 dinar-Lenovo-G580 kernel: [22167.484270] exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?' Jun 20 15:25:25 dinar-Lenovo-G580 kernel: [22169.310779] audit: type=1107 audit(1624191925.427:172): pid=657 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system"
[Touch-packages] [Bug 1861598] Re: lightdm assumes pam-kwallet to be always installed
The following other bugs reports say the same thing: #1768488 and #1830079 I also find the same bug in Xubuntu 20.04 and in my own custom 20.04 Ubuntu. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1861598 Title: lightdm assumes pam-kwallet to be always installed Status in lightdm package in Ubuntu: New Bug description: During boot, I see this error: > Feb 02 10:50:05 myhost lightdm[3224]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory > Feb 02 10:50:05 myhost lightdm[3224]: PAM adding faulty module: pam_kwallet.so > Feb 02 10:50:05 myhost lightdm[3224]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory > Feb 02 10:50:05 myhost lightdm[3224]: PAM adding faulty module: pam_kwallet5.so which I guess it's caused by this: > # grep kwallet /etc/pam.d/lightd* > /etc/pam.d/lightdm:authoptionalpam_kwallet.so > /etc/pam.d/lightdm:authoptionalpam_kwallet5.so > /etc/pam.d/lightdm:session optionalpam_kwallet.so auto_start > /etc/pam.d/lightdm:session optionalpam_kwallet5.so auto_start > /etc/pam.d/lightdm-greeter:authoptionalpam_kwallet.so > /etc/pam.d/lightdm-greeter:authoptionalpam_kwallet5.so > /etc/pam.d/lightdm-greeter:session optionalpam_kwallet.so auto_start > /etc/pam.d/lightdm-greeter:session optionalpam_kwallet5.so auto_start kwallet is a KDE program, which is not installed on MATE (and I think it shouldn't be), so I guess that such modules should not be [attempted to be] loaded. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Sun Feb 2 11:03:53 2020 InstallationDate: Installed on 2020-01-20 (12 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1861598/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1933023] Re: tc lacks Cake qdisc in 18.04 + HWE 5.4 kernel
** Tags added: upgrade-software-version ** Tags added: iproute2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1933023 Title: tc lacks Cake qdisc in 18.04 + HWE 5.4 kernel Status in iproute2 package in Ubuntu: New Bug description: I am using the 5.4 HWE kernel in 18.04, and even though this kernel has the CAKE qdisc, I am unable to use it as the version of tc, which is used to configure it, is too old. Even the backported tc is too old. Can we get the 20.04 iproute2 package, which does support the CAKE qdisc, backported to 18.04 to fix this? P.S. I did try pulling iproute2 directly from 20.04 repos using apt pinning, but then had glibc version incomptibility problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1933023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1933023] Re: tc lacks Cake qdisc in 18.04 + HWE 5.4 kernel
** Description changed: I am using the 5.4 HWE kernel in 18.04, and even though this kernel has the CAKE qdisc, I am unable to use it as the version of tc, which is used to configure it, is too old. Even the backported tc is too old. Can we get the 20.04 iproute2 package, which does support the CAKE qdisc, backported to 18.04 to fix this? + + P.S. I did try pulling iproute2 directly from 20.04 repos using apt + pinning, but then had glibc version incomptibility problems. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1933023 Title: tc lacks Cake qdisc in 18.04 + HWE 5.4 kernel Status in iproute2 package in Ubuntu: New Bug description: I am using the 5.4 HWE kernel in 18.04, and even though this kernel has the CAKE qdisc, I am unable to use it as the version of tc, which is used to configure it, is too old. Even the backported tc is too old. Can we get the 20.04 iproute2 package, which does support the CAKE qdisc, backported to 18.04 to fix this? P.S. I did try pulling iproute2 directly from 20.04 repos using apt pinning, but then had glibc version incomptibility problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1933023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1933023] [NEW] tc lacks Cake qdisc in 18.04 + HWE 5.4 kernel
Public bug reported: I am using the 5.4 HWE kernel in 18.04, and even though this kernel has the CAKE qdisc, I am unable to use it as the version of tc, which is used to configure it, is too old. Even the backported tc is too old. Can we get the 20.04 iproute2 package, which does support the CAKE qdisc, backported to 18.04 to fix this? ** Affects: iproute2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1933023 Title: tc lacks Cake qdisc in 18.04 + HWE 5.4 kernel Status in iproute2 package in Ubuntu: New Bug description: I am using the 5.4 HWE kernel in 18.04, and even though this kernel has the CAKE qdisc, I am unable to use it as the version of tc, which is used to configure it, is too old. Even the backported tc is too old. Can we get the 20.04 iproute2 package, which does support the CAKE qdisc, backported to 18.04 to fix this? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1933023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1644038] Re: df does not show btrfs filesystem
Also affects Ubuntu 20.04 LTS (and other distributions like Debian 10). Indirectly reported upstream on https://debbugs.gnu.org/cgi/bugreport.cgi?bug=17676 "btrfs subvolumes and bind-mounts make df report incorrect and/or extra results" (the reported bug is a consequence of the issue on btrfs subvolumes). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1644038 Title: df does not show btrfs filesystem Status in coreutils package in Ubuntu: Confirmed Bug description: "df -T ." (from Ubuntu 16.04 coreutils 8.25-2ubuntu2) does not show btrfs filesystem (subvolume): root@diaspora:/local/home# df -T . Filesystem Type 1K-blocks Used Available Use% Mounted on - -926429912 398092364 527962324 43% /local/home root@diaspora:/local# df -T . Filesystem Type 1K-blocks Used Available Use% Mounted on /dev/sda4 btrfs 926429912 398092540 527962164 43% /local root@diaspora:/local# df -T | grep ^/dev /dev/sda2ext4 163828888614260 6913384 56% / /dev/sda3ext4 16382888 18501615342628 2% /tmp /dev/sda4btrfs926429912 398092360 527962328 43% /local root@diaspora:/local# mount | grep btrfs /dev/sda4 on /local type btrfs (rw,relatime,ssd,space_cache,subvolid=5,subvol=/) root@diaspora:/local# blkid | grep sda4 /dev/sda4: LABEL="local" UUID="11faaa39-5805-4e92-a891-e8ceb4afa9f7" UUID_SUB="787a362f-ba60-44ca-a49f-6ff37eb691d4" TYPE="btrfs" PARTUUID="c93790e9-04" root@diaspora:/local# btrfs filesystem show /local Label: 'local' uuid: 11faaa39-5805-4e92-a891-e8ceb4afa9f7 Total devices 1 FS bytes used 379.48GiB devid1 size 883.51GiB used 414.02GiB path /dev/sda4 root@diaspora:/local# btrfs subvolume list /local ID 270 gen 42626 top level 5 path data ID 271 gen 1046 top level 5 path tmp ID 622 gen 43690 top level 5 path home To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1644038/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1644038] Re: df does not show btrfs filesystem
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: coreutils (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1644038 Title: df does not show btrfs filesystem Status in coreutils package in Ubuntu: Confirmed Bug description: "df -T ." (from Ubuntu 16.04 coreutils 8.25-2ubuntu2) does not show btrfs filesystem (subvolume): root@diaspora:/local/home# df -T . Filesystem Type 1K-blocks Used Available Use% Mounted on - -926429912 398092364 527962324 43% /local/home root@diaspora:/local# df -T . Filesystem Type 1K-blocks Used Available Use% Mounted on /dev/sda4 btrfs 926429912 398092540 527962164 43% /local root@diaspora:/local# df -T | grep ^/dev /dev/sda2ext4 163828888614260 6913384 56% / /dev/sda3ext4 16382888 18501615342628 2% /tmp /dev/sda4btrfs926429912 398092360 527962328 43% /local root@diaspora:/local# mount | grep btrfs /dev/sda4 on /local type btrfs (rw,relatime,ssd,space_cache,subvolid=5,subvol=/) root@diaspora:/local# blkid | grep sda4 /dev/sda4: LABEL="local" UUID="11faaa39-5805-4e92-a891-e8ceb4afa9f7" UUID_SUB="787a362f-ba60-44ca-a49f-6ff37eb691d4" TYPE="btrfs" PARTUUID="c93790e9-04" root@diaspora:/local# btrfs filesystem show /local Label: 'local' uuid: 11faaa39-5805-4e92-a891-e8ceb4afa9f7 Total devices 1 FS bytes used 379.48GiB devid1 size 883.51GiB used 414.02GiB path /dev/sda4 root@diaspora:/local# btrfs subvolume list /local ID 270 gen 42626 top level 5 path data ID 271 gen 1046 top level 5 path tmp ID 622 gen 43690 top level 5 path home To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1644038/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
