[Touch-packages] [Bug 1963767] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1963767 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1963767 Title: Microphone not working after suspend Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Custom DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 PackageArchitecture: amd64 Tags: impish Uname: Linux 5.16.11-xanmod1 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963767/+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 1963767] Re: Microphone not working after suspend
** Tags removed: impish ** Tags added: jammy ** Changed in: linux (Ubuntu) Status: Won't Fix => New ** Changed in: pulseaudio (Ubuntu) Status: Won't Fix => New -- 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/1963767 Title: Microphone not working after suspend Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop. On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone stops working (device is still there, but audio level is at zero all the time). To make it work again I need to do 2 things (just one is not sufficient): 1) Disconnect and connect webcam again to the laptop 2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start` Not sure whose fault it is, likely kernel driver, but the fact that pulseaudio needs to be restarted is concerning as well. Reproducible 100% for me. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Custom DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 PackageArchitecture: amd64 Tags: impish Uname: Linux 5.16.11-xanmod1 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963767/+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 1981622] Re: mtd device must be supplied (device name is empty)
I Have the same issue but the diffrence is that my device wont boot after getting this eror message Ps:im using kubuntu on a 4460 core i5 cpu and nvidia proprietary drivers -- 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/1981622 Title: mtd device must be supplied (device name is empty) Status in systemd package in Ubuntu: Confirmed Bug description: After updating my 22.04 system (possibly caused by Systemd update). And now booting, dmesg has two errors: 'mtd device must be supplied (device name is empty)'. See line 8 and 134 in the included logfile. The system are booting as it should though, and the system are working like it should no errors at all. Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in systemd? I have an EFI mounted at boot but it isn't used because I have installed my system in legacy BIOS mode. Is this maybe the culprit? I could ignore the message but it isn't nice though. Regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981622/+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 1981932] [NEW] Loud squeaking noise which disappears when audio is played
Public bug reported: When I connect my headset, theres a loud radio like noise which disappears when I play some audio but comes back as soon as i stop. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: costa 1294 F pulseaudio costa 6980 F alsamixer /dev/snd/controlC1: costa 1294 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 17 22:35:58 2022 InstallationDate: Installed on 2022-07-17 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [Nitro AN515-55, Realtek ALC295, Black Headphone Out, Right] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/19/2020 dmi.bios.release: 1.0 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.00 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Stonic_CMS dmi.board.vendor: CML dmi.board.version: V1.00 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.00 dmi.ec.firmware.release: 1.0 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.00:bd03/19/2020:br1.0:efr1.0:svnAcer:pnNitroAN515-55:pvrV1.00:rvnCML:rnStonic_CMS:rvrV1.00:cvnAcer:ct10:cvrV1.00:sku: dmi.product.family: Nitro 5 dmi.product.name: Nitro AN515-55 dmi.product.sku: dmi.product.version: V1.00 dmi.sys.vendor: Acer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/1981932 Title: Loud squeaking noise which disappears when audio is played Status in alsa-driver package in Ubuntu: New Bug description: When I connect my headset, theres a loud radio like noise which disappears when I play some audio but comes back as soon as i stop. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: costa 1294 F pulseaudio costa 6980 F alsamixer /dev/snd/controlC1: costa 1294 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 17 22:35:58 2022 InstallationDate: Installed on 2022-07-17 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [Nitro AN515-55, Realtek ALC295, Black Headphone Out, Right] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/19/2020 dmi.bios.release: 1.0 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.00 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Stonic_CMS dmi.board.vendor: CML dmi.board.version: V1.00 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.00 dmi.ec.firmware.release: 1.0 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.00:bd03/19/2020:br1.0:efr1.0:svnAcer:pnNitroAN515-55:pvrV1.00:rvnCML:rnStonic_CMS:rvrV1.00:cvnAcer:ct10:cvrV1.00:sku: dmi.product.family: Nitro 5 dmi.product.name: Nitro AN515-55 dmi.product.sku: dmi.product.version: V1.00 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1981932/+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 1927337] Re: [USB-Audio - RODECaster Pro, playback] Sound is distorted (21.04)
I have the same issue. -- 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/1927337 Title: [USB-Audio - RODECaster Pro, playback] Sound is distorted (21.04) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I got a Rodecaster Pro USB device that has been causing trouble before and already lead to quirk handling in the kernel for the sample rate, see https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/sound/usb/format.c?h=v5.8#n412 The Rodecaster is running fine on my laptop, but on my desktop, only audio input is working. The audio output is distorted. It's played kind of very slowly. Interestingly, if the source is a video file, the video plays slower, e.g. YouTube in a browser. I have never seen anything like that before. I have tried to figure out what the cause might be and I think I have reached the end of where I can get to on my own. I have documented most things at https://ubuntuforums.org/showthread.php?t=2461568 Putting my last step it in a nutshell: I have booted both my computers with a plain Ubuntu 21.04 from a pen drive (it uses kernel version 5.11.0-16-generic) to make sure it's not some different configuration that I have set up over the years on my systems (both Ubuntu 20.04 with kernel 5.8.18). I attached the Rodecaster. It runs fine on my laptop, but not on my desktop (used the output test from). I then detected the card number with aplay -l I killed pulseaudio with pulseaudio -k I then played the same sample (encoded in 48000 Hz in PCM signed 32 bit little endian format) using aplay -f S32_LE -c 2 -r 48000 -D hw:x ~/sample.wav where x is the appropriate card number and the rest of the arguments meet the Rodecaster's narrow specification. It's playing fine on the laptop, but distorted on the desktop. As far as I understand using aplay this way without a plugin should send the file directly to the device, so I assume there's something on the way from aplay to the Rodecaster that's interfering (kernel or even some piece of hardware) - and that definitely is where my expertise ends (rather a little before :-)). I'll gladly contribute any information that could be useful and I will willingly help to debug this problem if it may be related to the kernel. If there's anything I can do, please let me know. Cheers, Oliver 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 CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Thu May 6 09:33:40 2021 LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Pro failed Symptom_Card: RODECaster Pro - RODECaster Pro Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [USB-Audio - RODECaster Pro, playback] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550-A PRO (MS-7C56) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C56 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1927337/+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 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual
@apinunt, pcscd is not started at boot but when an application is calling the WinSCard API. See https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html Where do you find that pcscd manpage indicates it is started at boot? Interesting to know that this bug was already present in Ubuntu 21.10. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd 1.9.5-3 do not start automatically, only manual Status in pcsc-lite package in Ubuntu: Confirmed Bug description: Ubuntu Mate 22.04 with the latest updates. Problem is present with internal smart-card reader and also external usb smart-card reader. eid-viewer sees no card reader,but When i do: sudo pcscd -f it is working, also following the tips of Ludovic: https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html sudo systemctl stop pcscd.socket sudo systemctl start pcscd.socket It is working until next restart. libacsccid1 version: 1.1.8-1 libccid version: 1.5.0-2 pcscd version: 1.9.5-3 eid-archive version: 2022.3 eid-mw version: 5.0.28v5.0.28-0u2204-1 eid-viewer version: 5.0.28v5.0.28-0u2204-1 In Firefox, my eid card is then also recognized, but only in the ESR version, but this is a know Mozilla bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+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 1970449] Re: GPG keys are not shown in Software and Updates
The version from Ubuntu 20.04 has a p.close() at the end to close the subprocess. I have it here in my download folder. Perhaps it would be better to include that. The problem is that I can't make a package. I could upload a AptAuth.py that works. I can't understand why the importance was set to low. Ubuntu is a bit like a commercial operating system where some people even pay for support. Then something like that should work, I would say. But that is my opinion. -- 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/1970449 Title: GPG keys are not shown in Software and Updates Status in software-properties package in Ubuntu: Confirmed Bug description: software-properties-gtk does not show the registered apt gpg keys in the "Authentication" tab on my Ubuntu 21.10 and 22.04 systems. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Apr 26 20:48:04 2022 InstallationDate: Installed on 2022-04-25 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1970449/+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 1970449] Re: GPG keys are not shown in Software and Updates
Now I change the AptAuth.py. I changed subprocess.run to subprocess.Popen. (In the passage where it reads the keys) I did not change anything else. (The version in Ubuntu 20.04 had a p.close() or something additionally.) Here it works. It shows the keys ** Attachment added: "Bildschirmfoto vom 2022-07-17 10-08-27.png" https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1970449/+attachment/5603562/+files/Bildschirmfoto%20vom%202022-07-17%2010-08-27.png -- 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/1970449 Title: GPG keys are not shown in Software and Updates Status in software-properties package in Ubuntu: Confirmed Bug description: software-properties-gtk does not show the registered apt gpg keys in the "Authentication" tab on my Ubuntu 21.10 and 22.04 systems. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Apr 26 20:48:04 2022 InstallationDate: Installed on 2022-04-25 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1970449/+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 1970449] Re: GPG keys are not shown in Software and Updates
I would say that the application window gets no value when you use subprocess.run. When you change subprocess.run to subprocess.Popen it works. I can try to post a screenshot. I do not know if that works. That is the actual version. ** Attachment added: "Bildschirmfoto vom 2022-07-17 10-03-16.png" https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1970449/+attachment/5603561/+files/Bildschirmfoto%20vom%202022-07-17%2010-03-16.png -- 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/1970449 Title: GPG keys are not shown in Software and Updates Status in software-properties package in Ubuntu: Confirmed Bug description: software-properties-gtk does not show the registered apt gpg keys in the "Authentication" tab on my Ubuntu 21.10 and 22.04 systems. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Apr 26 20:48:04 2022 InstallationDate: Installed on 2022-04-25 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1970449/+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 1970449] Re: GPG keys are not shown in Software and Updates
subprocess.Popen was substituted with subprocess.run in the AptAuth.py. That seems to be the reason. They behave differently here. The other operations seem to work, but it does not read the keys with subprocess.run. It only reads the keys with subprocess.Popen. I do not exactly know why. I wrote a small testfile and they seem to behave differently. It seems as if they had a different return value. I'm not sure. The behavior of these two seems to be different here. From the python documentation that should not be the case, I would say. In the python documentation they seem to be nearly equal, but that does not seem to be the case. -- 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/1970449 Title: GPG keys are not shown in Software and Updates Status in software-properties package in Ubuntu: Confirmed Bug description: software-properties-gtk does not show the registered apt gpg keys in the "Authentication" tab on my Ubuntu 21.10 and 22.04 systems. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Apr 26 20:48:04 2022 InstallationDate: Installed on 2022-04-25 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1970449/+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 1970449] Re: GPG keys are not shown in Software and Updates
apt-key list works. It also shows the keys in /etc/apt/trusted.gpg.d/ -- 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/1970449 Title: GPG keys are not shown in Software and Updates Status in software-properties package in Ubuntu: Confirmed Bug description: software-properties-gtk does not show the registered apt gpg keys in the "Authentication" tab on my Ubuntu 21.10 and 22.04 systems. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Apr 26 20:48:04 2022 InstallationDate: Installed on 2022-04-25 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1970449/+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 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual
Forgot to say, but the same problem exists on both a Dell G5, running Ubuntu Mate 21.10 and a Dell Latitude 3190 running Ubuntu Mate 22.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd 1.9.5-3 do not start automatically, only manual Status in pcsc-lite package in Ubuntu: Confirmed Bug description: Ubuntu Mate 22.04 with the latest updates. Problem is present with internal smart-card reader and also external usb smart-card reader. eid-viewer sees no card reader,but When i do: sudo pcscd -f it is working, also following the tips of Ludovic: https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html sudo systemctl stop pcscd.socket sudo systemctl start pcscd.socket It is working until next restart. libacsccid1 version: 1.1.8-1 libccid version: 1.5.0-2 pcscd version: 1.9.5-3 eid-archive version: 2022.3 eid-mw version: 5.0.28v5.0.28-0u2204-1 eid-viewer version: 5.0.28v5.0.28-0u2204-1 In Firefox, my eid card is then also recognized, but only in the ESR version, but this is a know Mozilla bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+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 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual
We've been having to run "service pcscd start" manually to use the ACS ACR39U card reader each time. Man pcscd seems to say the service is started at boot, which it is not, though ideally we would like it to start when the reader is plugged into the computer and stop when it is unplugged. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd 1.9.5-3 do not start automatically, only manual Status in pcsc-lite package in Ubuntu: Confirmed Bug description: Ubuntu Mate 22.04 with the latest updates. Problem is present with internal smart-card reader and also external usb smart-card reader. eid-viewer sees no card reader,but When i do: sudo pcscd -f it is working, also following the tips of Ludovic: https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html sudo systemctl stop pcscd.socket sudo systemctl start pcscd.socket It is working until next restart. libacsccid1 version: 1.1.8-1 libccid version: 1.5.0-2 pcscd version: 1.9.5-3 eid-archive version: 2022.3 eid-mw version: 5.0.28v5.0.28-0u2204-1 eid-viewer version: 5.0.28v5.0.28-0u2204-1 In Firefox, my eid card is then also recognized, but only in the ESR version, but this is a know Mozilla bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+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 1981622] Re: mtd device must be supplied (device name is empty)
Hi, I have same error now. I recently upgraded to 22.04. First I had kernal panic but I was able to get past that issue and now stuck at "mtd device must be supplied". My PC only boots into emergency mode and can't do anything. I am waiting if there is any fix for this. -- 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/1981622 Title: mtd device must be supplied (device name is empty) Status in systemd package in Ubuntu: Confirmed Bug description: After updating my 22.04 system (possibly caused by Systemd update). And now booting, dmesg has two errors: 'mtd device must be supplied (device name is empty)'. See line 8 and 134 in the included logfile. The system are booting as it should though, and the system are working like it should no errors at all. Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in systemd? I have an EFI mounted at boot but it isn't used because I have installed my system in legacy BIOS mode. Is this maybe the culprit? I could ignore the message but it isn't nice though. Regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981622/+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
