[Touch-packages] [Bug 1867802] Re: With fractional scaling enabled and scaling set to 200%, when videos are viewed in fullscreen there is constant refreshing and resizing of the video
*** This bug is a duplicate of bug 1862081 *** https://bugs.launchpad.net/bugs/1862081 The issues you describe are already covered by bug 1862081, bug 1846398 and bug 1754284. So please be careful to separate each concern and comment on those bugs appropriately. ** Tags added: xrandr-scaling ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** This bug has been marked a duplicate of bug 1862081 Gnome resizes framebuffer when playing fullscreen video over and over again (when using X11 fractional scaling) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1867802 Title: With fractional scaling enabled and scaling set to 200%, when videos are viewed in fullscreen there is constant refreshing and resizing of the video Status in xorg-server package in Ubuntu: New Bug description: This is seen both in Youtube and also other web-based videos as well as when videos are viewed using the local video player application. When a video is set to be viewed in fullscreen, the video flickers and continually resizes itself. Hardware: Two displays, with one set to scale at 200% (4k display resolution), the other set to 100% scale at 1080p. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 17 11:53:46 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e1) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [148c:2391] InstallationDate: Installed on 2020-03-16 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=0570e7f8-f576-4df1-9bb0-ee1102dd0991 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2008 dmi.board.asset.tag: Default string dmi.board.name: PRIME B450-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2008:bd12/06/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: 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.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A 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/ubuntu/+source/xorg-server/+bug/1867802/+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 1867802] Re: With fractional scaling enabled and scaling set to 200%, when videos are viewed in fullscreen there is constant refreshing and resizing of the video
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1867802 Title: With fractional scaling enabled and scaling set to 200%, when videos are viewed in fullscreen there is constant refreshing and resizing of the video Status in xorg package in Ubuntu: New Bug description: This is seen both in Youtube and also other web-based videos as well as when videos are viewed using the local video player application. When a video is set to be viewed in fullscreen, the video flickers and continually resizes itself. Hardware: Two displays, with one set to scale at 200% (4k display resolution), the other set to 100% scale at 1080p. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 17 11:53:46 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e1) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [148c:2391] InstallationDate: Installed on 2020-03-16 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=0570e7f8-f576-4df1-9bb0-ee1102dd0991 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2008 dmi.board.asset.tag: Default string dmi.board.name: PRIME B450-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2008:bd12/06/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: 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.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A 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/ubuntu/+source/xorg/+bug/1867802/+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 1867802] [NEW] With fractional scaling enabled and scaling set to 200%, when videos are viewed in fullscreen there is constant refreshing and resizing of the video
You have been subscribed to a public bug: This is seen both in Youtube and also other web-based videos as well as when videos are viewed using the local video player application. When a video is set to be viewed in fullscreen, the video flickers and continually resizes itself. Hardware: Two displays, with one set to scale at 200% (4k display resolution), the other set to 100% scale at 1080p. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 17 11:53:46 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e1) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [148c:2391] InstallationDate: Installed on 2020-03-16 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=0570e7f8-f576-4df1-9bb0-ee1102dd0991 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2008 dmi.board.asset.tag: Default string dmi.board.name: PRIME B450-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2008:bd12/06/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: 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.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal reproducible ubuntu -- With fractional scaling enabled and scaling set to 200%, when videos are viewed in fullscreen there is constant refreshing and resizing of the video https://bugs.launchpad.net/bugs/1867802 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- 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 1867760] Re: zorg crashes on every time on boot
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Summary changed: - zorg crashes on every time on boot + Xorg crashes on every time on boot -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1867760 Title: Xorg crashes on every time on boot Status in xorg-server package in Ubuntu: Incomplete Bug description: This is more of an annoyance than anything. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CompositorRunning: None CurrentDesktop: XFCE Date: Tue Mar 17 07:29:19 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.3.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller [1028:024f] Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller [1028:024f] InstallationDate: Installed on 2020-03-16 (0 days ago) InstallationMedia: Xubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Dell Inc. Latitude E6500 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=93ad7557-b4ea-40bd-a8ac-3496ddeb2747 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A29 dmi.board.name: 0W612R dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA29:bd06/04/2013:svnDellInc.:pnLatitudeE6500:pvr:rvnDellInc.:rn0W612R:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude E6500 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1867760/+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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
Same issue on Dell G3-3590 i7 gtx1660, worked for 2 months and now simply stopped, started without audio that i solved with this: " I used to change /etc/default/grub to have this line GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet splash acpi_backlight=vendor acpi_osi='!Windows 2013' acpi_osi='!Windows 2012' snd_hda_intel.dmic_detect=0" Then run in terminal grub-mkconfig -o /boot/grub/grub.cfg " I get this solution from here: https://bbs.archlinux.org/viewtopic.php?id=251157 Now audio works fine, with and without headphone. But the problem now is that the internal microphone is not detected. And when the headphone (with dont have microphone) is connected he is detected in input devices list as if it was a microphone. and when I added this: options snd-hda-intel index=0 model=laptop-dmic on: /etc/modprobe.d/alsa-base.conf a internal mic appears in the input device list but still not detecting audio, and the headphone is not detected in the input list anymore, but audio still working... -- 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/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1766740] Re: apport autopkgtest regression due to kernel packaging changes
This bug was fixed in the package apport - 2.20.1-0ubuntu2.22 --- apport (2.20.1-0ubuntu2.22) xenial-security; urgency=medium [ Michael Hudson-Doyle ] * SECURITY REGRESSION: fix autopkgtest failures since recent security update (LP: #1854237) - Fix regression in creating report for crashing setuid process by getting kernel to tell us the executable path rather than reading /proc/[pid]/exe. - Fix deletion of partially written core files. - Fix test_get_logind_session to use new API. - Restore add_proc_info raising ValueError for a dead process. - Delete test_lock_symlink, no longer applicable now that the lock is created in a directory only root can write to. [ Tiago Stürmer Daitx ] * SECURITY REGRESSION: 'module' object has no attribute 'O_PATH' (LP: #1851806) - apport/report.py, apport/ui.py: use file descriptors for /proc/pid directory access only when running under python 3; prevent reading /proc maps under python 2 as it does not provide a secure way to do so; use io.open for better compatibility between python 2 and 3. * data/apport: fix number of arguments passed through socks into a container. * test/test_report.py: test login session with both pid and proc_pid_fd. * test/test_apport_valgrind.py: skip test_sandbox_cache_options if system has little memory. * test/test_ui.py: modify run_crash_kernel test to account for the fact that linux-image-$kvers-$flavor is now built from the linux-signed source package on amd64 and ppc64el. (LP: #1766740) -- Tiago Stürmer Daitx Thu, 27 Feb 2020 03:18:45 + ** Changed in: apport (Ubuntu Xenial) Status: Triaged => Fix Released -- 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/1766740 Title: apport autopkgtest regression due to kernel packaging changes Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: Fix Released Status in apport source package in Bionic: Fix Released Bug description: [SRU Justification] In bionic, linux-image-$kvers-$flavor is now built from the linux-signed source package on amd64, not from the linux source package. This now causes a test to fail in the apport test suite: [...] == FAIL: test_run_crash_kernel (__main__.T) run_crash() for a kernel error -- Traceback (most recent call last): File "./test_ui.py", line 1305, in test_run_crash_kernel self.assertEqual(self.ui.opened_url, 'http://linux.bugs.example.com/%i' % se lf.ui.crashdb.latest_id()) AssertionError: 'http://linux-signed.bugs.example.com/5' != 'http://linux.bugs.e xample.com/5' - http://linux-signed.bugs.example.com/5 ? --- + http://linux.bugs.example.com/5 -- Ran 70 tests in 79.815s FAILED (failures=1) [...] (https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest- bionic/bionic/amd64/a/apport/20180424_19_45dc8@/log.gz) This test needs to be fixed to know about the packaging change. Note that this packaging change is expected to soon be SRUed back to all Ubuntu releases, so apport's testsuite change should also be SRUed. [Test case] This passes if the autopkgtests pass. [Regression potential] The test could be changed to pass while leaving underlying issues in the code. This has probably not happened here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1766740/+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 1854237] Re: autopkgtests fail after security fixes
This bug was fixed in the package apport - 2.20.1-0ubuntu2.22 --- apport (2.20.1-0ubuntu2.22) xenial-security; urgency=medium [ Michael Hudson-Doyle ] * SECURITY REGRESSION: fix autopkgtest failures since recent security update (LP: #1854237) - Fix regression in creating report for crashing setuid process by getting kernel to tell us the executable path rather than reading /proc/[pid]/exe. - Fix deletion of partially written core files. - Fix test_get_logind_session to use new API. - Restore add_proc_info raising ValueError for a dead process. - Delete test_lock_symlink, no longer applicable now that the lock is created in a directory only root can write to. [ Tiago Stürmer Daitx ] * SECURITY REGRESSION: 'module' object has no attribute 'O_PATH' (LP: #1851806) - apport/report.py, apport/ui.py: use file descriptors for /proc/pid directory access only when running under python 3; prevent reading /proc maps under python 2 as it does not provide a secure way to do so; use io.open for better compatibility between python 2 and 3. * data/apport: fix number of arguments passed through socks into a container. * test/test_report.py: test login session with both pid and proc_pid_fd. * test/test_apport_valgrind.py: skip test_sandbox_cache_options if system has little memory. * test/test_ui.py: modify run_crash_kernel test to account for the fact that linux-image-$kvers-$flavor is now built from the linux-signed source package on amd64 and ppc64el. (LP: #1766740) -- Tiago Stürmer Daitx Thu, 27 Feb 2020 03:18:45 + -- 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/1854237 Title: autopkgtests fail after security fixes Status in Apport: New Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: Fix Released Status in apport source package in Bionic: Fix Released Status in apport source package in Disco: New Status in apport source package in Eoan: Fix Released Bug description: The following autopkgtests fail after the recent security fixes: log:FAIL: test_get_logind_session (__main__.T) log:FAIL: test_core_dump_packaged (__main__.T) log:FAIL: test_core_dump_unpackaged (__main__.T) log:FAIL: test_crash_setuid_drop (__main__.T) log:FAIL: test_crash_setuid_keep (__main__.T) log:FAIL: test_crash_setuid_nonwritable_cwd (__main__.T) log:FAIL: test_lock_symlink (__main__.T) test_get_logind_session is a test failing to keep up with an API change. test_core_dump_* is failures to remove partly written core files. Both of these are easy fixes, I'll have a MP for them soon. test_crash_setuid_* are caused by the dropping of privileges when accessing the crashing process's /proc. They seem to be testing behaviour now explicitly forbidden by the fix to be honest! test_lock_symlink fails because the lock file is now always in /var/lock/apport/ and not in $APPORT_REPORT_DIR. I guess we could update the test, but is it really worth it after the fix? To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1854237/+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 1854237] Re: autopkgtests fail after security fixes
This bug was fixed in the package apport - 2.20.9-0ubuntu7.12 --- apport (2.20.9-0ubuntu7.12) bionic-security; urgency=medium [ Michael Hudson-Doyle ] * SECURITY REGRESSION: fix autopkgtest failures since recent security update (LP: #1854237) - Fix regression in creating report for crashing setuid process by getting kernel to tell us the executable path rather than reading /proc/[pid]/exe. - Fix deletion of partially written core files. - Fix test_get_logind_session to use new API. - Restore add_proc_info raising ValueError for a dead process. - Delete test_lock_symlink, no longer applicable now that the lock is created in a directory only root can write to. [ Tiago Stürmer Daitx ] * SECURITY REGRESSION: 'module' object has no attribute 'O_PATH' (LP: #1851806) - apport/report.py, apport/ui.py: use file descriptors for /proc/pid directory access only when running under python 3; prevent reading /proc maps under python 2 as it does not provide a secure way to do so; use io.open for better compatibility between python 2 and 3. * data/apport: fix number of arguments passed through socks into a container. * test/test_apport_valgrind.py: skip test_sandbox_cache_options if system has little memory. * test/test_report.py: test login session with both pid and proc_pid_fd. -- Tiago Stürmer Daitx Thu, 27 Feb 2020 03:18:45 + ** Changed in: apport (Ubuntu Bionic) Status: New => Fix Released ** Changed in: apport (Ubuntu Xenial) Status: New => Fix Released -- 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/1854237 Title: autopkgtests fail after security fixes Status in Apport: New Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: Fix Released Status in apport source package in Bionic: Fix Released Status in apport source package in Disco: New Status in apport source package in Eoan: Fix Released Bug description: The following autopkgtests fail after the recent security fixes: log:FAIL: test_get_logind_session (__main__.T) log:FAIL: test_core_dump_packaged (__main__.T) log:FAIL: test_core_dump_unpackaged (__main__.T) log:FAIL: test_crash_setuid_drop (__main__.T) log:FAIL: test_crash_setuid_keep (__main__.T) log:FAIL: test_crash_setuid_nonwritable_cwd (__main__.T) log:FAIL: test_lock_symlink (__main__.T) test_get_logind_session is a test failing to keep up with an API change. test_core_dump_* is failures to remove partly written core files. Both of these are easy fixes, I'll have a MP for them soon. test_crash_setuid_* are caused by the dropping of privileges when accessing the crashing process's /proc. They seem to be testing behaviour now explicitly forbidden by the fix to be honest! test_lock_symlink fails because the lock file is now always in /var/lock/apport/ and not in $APPORT_REPORT_DIR. I guess we could update the test, but is it really worth it after the fix? To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1854237/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
@Devin and Michael, That is because the X1C7 has too many configs: like different cpu, different ramsize or different disk size, each config has a unique cardlongname. And For this SRU, we only covered the configs we need to certify in our OEM enablement project. LENOVO noticed this issue too, they told us the alsa-lib could find and load the ucm by the first 3 letters of BIOS_VERSION, so I am going to submit a new SRU with this solution soon. With that solution landed in the alsa-lib, all x1c7 could use one ucm. So could you please upload the output of cat /sys/devices/virtual/dmi/id/bios_version, let us see if the first 3 letters of bios_version are same or not among all x1c7 machines. @sil2100, Since the current SRU already covered all machines we enabled in the OEM project and they all worked well, please release it. Then I will cover the left machines in a new SRU. thx. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+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 1867774] Re: PCI/internal sound card not detected
@Jesko, -42 has a regression on sof audio driver, please wait for the coming -43 kernel. thx. -- 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/1867774 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: Two days ago the audio of my laptop was still working fine. Between then and now I did a kernel and gnome-shell update (those are the ones I remember). Now my sound settings do not show any devices beyond the dummy ones. I have Ubuntu 19.10 on my Thinkpad X1 Yoga and I've tried these https://itsfoss.com/fix-sound-ubuntu-1304-quick-tip/ and https://help.ubuntu.com/community/SoundTroubleshooting things Here are some maybe relevant packages apt-cache policy alsa-base pulseaudio alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu eoan/main i386 Packages 100 /var/lib/dpkg/status pulseaudio: Installed: 1:13.0-1ubuntu1.1 Candidate: 1:13.0-1ubuntu1.1 Version table: *** 1:13.0-1ubuntu1.1 500 500 http://de.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages Here my lspci, which as you can see includes a audio device 00:00.0 Host bridge: Intel Corporation Device 3e34 (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (Whiskey Lake) (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP Thermal Controller (rev 11) 00:13.0 Serial controller: Intel Corporation Cannon Point-LP Integrated Sensor Hub (rev 11) 00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI Controller (rev 11) 00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 11) 00:14.3 Network controller: Intel Corporation Cannon Point-LP CNVi [Wireless-AC] (rev 11) 00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #0 (rev 11) 00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #1 (rev 11) 00:16.0 Communication controller: Intel Corporation Cannon Point-LP MEI Controller #1 (rev 11) 00:1c.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #1 (rev f1) 00:1d.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #9 (rev f1) 00:1d.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #13 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 11) 00:1f.3 Audio device: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) 00:1f.4 SMBus: Intel Corporation Cannon Point-LP SMBus Controller (rev 11) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP SPI Controller (rev 11) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (6) I219-V (rev 11) 02:00.0 Wireless controller [0d40]: Intel Corporation XMM7360 LTE Advanced Modem (rev 01) 03:00.0 Non-Volatile memory controller: Sandisk Corp Device 5006 05:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 06:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 06:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 06:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 06:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 07:00.0 System peripheral: Intel Corporation JHL6540 Thunderbolt 3 NHI (C step) [Alpine Ridge 4C 2016] (rev 02) 2d:00.0 USB controller: Intel Corporation JHL6540 Thunderbolt 3 USB Controller (C step) [Alpine Ridge 4C 2016] (rev 02) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Mar 17 14:21:31 2020 InstallationDate: Installed on 2020-01-15 (61 days ago)
[Touch-packages] [Bug 1867774] Re: PCI/internal sound card not detected
** Description changed: Two days ago the audio of my laptop was still working fine. Between then and now I did a kernel and gnome-shell update (those are the ones I remember). Now my sound settings do not show any devices beyond the dummy ones. I have Ubuntu 19.10 on my Thinkpad X1 Yoga and I've tried these https://itsfoss.com/fix-sound-ubuntu-1304-quick-tip/ and https://help.ubuntu.com/community/SoundTroubleshooting things Here are some maybe relevant packages - ``` + apt-cache policy alsa-base pulseaudio alsa-base: - Installed: 1.0.25+dfsg-0ubuntu5 - Candidate: 1.0.25+dfsg-0ubuntu5 - Version table: - *** 1.0.25+dfsg-0ubuntu5 500 - 500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages - 500 http://de.archive.ubuntu.com/ubuntu eoan/main i386 Packages - 100 /var/lib/dpkg/status + Installed: 1.0.25+dfsg-0ubuntu5 + Candidate: 1.0.25+dfsg-0ubuntu5 + Version table: + *** 1.0.25+dfsg-0ubuntu5 500 + 500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages + 500 http://de.archive.ubuntu.com/ubuntu eoan/main i386 Packages + 100 /var/lib/dpkg/status pulseaudio: - Installed: 1:13.0-1ubuntu1.1 - Candidate: 1:13.0-1ubuntu1.1 - Version table: - *** 1:13.0-1ubuntu1.1 500 - 500 http://de.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages - 100 /var/lib/dpkg/status - 1:13.0-1ubuntu1 500 - 500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages - ``` + Installed: 1:13.0-1ubuntu1.1 + Candidate: 1:13.0-1ubuntu1.1 + Version table: + *** 1:13.0-1ubuntu1.1 500 + 500 http://de.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages + 100 /var/lib/dpkg/status + 1:13.0-1ubuntu1 500 + 500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages + Here my lspci, which as you can see includes a audio device - ``` + 00:00.0 Host bridge: Intel Corporation Device 3e34 (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (Whiskey Lake) (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP Thermal Controller (rev 11) 00:13.0 Serial controller: Intel Corporation Cannon Point-LP Integrated Sensor Hub (rev 11) 00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI Controller (rev 11) 00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 11) 00:14.3 Network controller: Intel Corporation Cannon Point-LP CNVi [Wireless-AC] (rev 11) 00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #0 (rev 11) 00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #1 (rev 11) 00:16.0 Communication controller: Intel Corporation Cannon Point-LP MEI Controller #1 (rev 11) 00:1c.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #1 (rev f1) 00:1d.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #9 (rev f1) 00:1d.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #13 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 11) 00:1f.3 Audio device: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) 00:1f.4 SMBus: Intel Corporation Cannon Point-LP SMBus Controller (rev 11) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP SPI Controller (rev 11) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (6) I219-V (rev 11) 02:00.0 Wireless controller [0d40]: Intel Corporation XMM7360 LTE Advanced Modem (rev 01) 03:00.0 Non-Volatile memory controller: Sandisk Corp Device 5006 05:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 06:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 06:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 06:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 06:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 07:00.0 System peripheral: Intel Corporation JHL6540 Thunderbolt 3 NHI (C step) [Alpine Ridge 4C 2016] (rev 02) 2d:00.0 USB controller: Intel Corporation JHL6540 Thunderbolt 3 USB Controller (C step) [Alpine Ridge 4C 2016] (rev 02) - ``` + ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux
[Touch-packages] [Bug 1864274] Re: [iris regression] gfx corruption
** Summary changed:
- crunchy pixels
+ [iris regression] gfx corruption
--
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/1864274
Title:
[iris regression] gfx corruption
Status in Mesa:
Unknown
Status in mesa package in Ubuntu:
Confirmed
Status in mesa source package in Focal:
Confirmed
Bug description:
Hello, after upgrading firefox (and many other packages) on focal
today, I've got some video artifacts in firefox.
When typing in text boxes and text fields, the new character is drawn
very slowly, pixel-by-pixel, and isn't complete until the cursor has
moved on. When larger portions of the screen are updated, it looks a
lot like the entire window is being run through a video codec or you
can see parts of the video memory from other processes. (But it looks
more deliberate and predictable than either of these descriptions.)
So far Firefox is the only application I've found that is affected.
urxvt, libreoffice, xfontsel, glxgears all seem to work as expected.
I did get cairo package update today, but the changelog is just:
pango1.0 (1.44.7-1ubuntu2) focal; urgency=medium
* No-change rebuild with fixed binutils on arm64.
-- Matthias Klose Sat, 08 Feb 2020 11:15:23 +
And an xorg update:
xorg (1:7.7+19ubuntu14) focal; urgency=medium
* No-change rebuild with fixed binutils on arm64.
-- Matthias Klose Sat, 08 Feb 2020 11:21:28 +
So I don't believe these are involved.
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620
(rev 07)
Thanks
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 73.0.1+build1-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k5.4.0-14-generic.
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sarnold3296 F pulseaudio
/dev/snd/controlC0: sarnold3296 F pulseaudio
BuildID: 20200217142647
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 144'
Mixer name : 'Realtek ALC285'
Components : 'HDA:10ec0285,17aa225c,0012
HDA:8086280b,80860101,0010'
Controls : 53
Simple ctrls : 15
Card1.Amixer.info:
Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at
usb-:00:14.0-4.2.4, high speed'
Mixer name : 'USB Mixer'
Components : 'USB17ef:306f'
Controls : 9
Simple ctrls : 4
Channel: Unavailable
Date: Sat Feb 22 05:41:10 2020
ForcedLayersAccel: False
IncompatibleExtensions:
Pentadactyl - pentadac...@dactyl.googlecode.com
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
IpRoute:
default via 192.168.0.1 dev enp0s31f6 proto dhcp metric 100
10.23.231.0/24 dev lxdbr0 proto kernel scope link src 10.23.231.1
192.168.0.0/24 dev enp0s31f6 proto kernel scope link src 192.168.0.34 metric
100
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
linkdown
MostRecentCrashID: bp-ea952d4d-f25a-4ced-893c-8cabb2160112
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:737
PrefSources: prefs.js
ProcEnviron:
TERM=rxvt-unicode-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=73.0.1/20200217142647 (In use)
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: Upgraded to focal on 2020-01-24 (28 days ago)
dmi.bios.date: 11/25/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N23ET69W (1.44 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20KHCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrN23ET69W(1.44):bd11/25/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 6th
dmi.product.name: 20KHCTO1WW
dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
dmi.product.version: ThinkPad X1 Carbon 6th
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1864274/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help :
[Touch-packages] [Bug 1867774] Re: PCI/internal sound card not detected
Ok, I've downgraded to kernel 5.3.0-40-generic and the audio works again. I've also noticed that in 5.3.0-42 I cannot wake my laptop after suspend. -- 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/1867774 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: Two days ago the audio of my laptop was still working fine. Between then and now I did a kernel and gnome-shell update (those are the ones I remember). Now my sound settings do not show any devices beyond the dummy ones. I have Ubuntu 19.10 on my Thinkpad X1 Yoga and I've tried these https://itsfoss.com/fix-sound-ubuntu-1304-quick-tip/ and https://help.ubuntu.com/community/SoundTroubleshooting things Here are some maybe relevant packages ``` apt-cache policy alsa-base pulseaudio alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu eoan/main i386 Packages 100 /var/lib/dpkg/status pulseaudio: Installed: 1:13.0-1ubuntu1.1 Candidate: 1:13.0-1ubuntu1.1 Version table: *** 1:13.0-1ubuntu1.1 500 500 http://de.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages ``` Here my lspci, which as you can see includes a audio device ``` 00:00.0 Host bridge: Intel Corporation Device 3e34 (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (Whiskey Lake) (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP Thermal Controller (rev 11) 00:13.0 Serial controller: Intel Corporation Cannon Point-LP Integrated Sensor Hub (rev 11) 00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI Controller (rev 11) 00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 11) 00:14.3 Network controller: Intel Corporation Cannon Point-LP CNVi [Wireless-AC] (rev 11) 00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #0 (rev 11) 00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #1 (rev 11) 00:16.0 Communication controller: Intel Corporation Cannon Point-LP MEI Controller #1 (rev 11) 00:1c.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #1 (rev f1) 00:1d.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #9 (rev f1) 00:1d.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #13 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 11) 00:1f.3 Audio device: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) 00:1f.4 SMBus: Intel Corporation Cannon Point-LP SMBus Controller (rev 11) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP SPI Controller (rev 11) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (6) I219-V (rev 11) 02:00.0 Wireless controller [0d40]: Intel Corporation XMM7360 LTE Advanced Modem (rev 01) 03:00.0 Non-Volatile memory controller: Sandisk Corp Device 5006 05:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 06:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 06:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 06:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 06:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 07:00.0 System peripheral: Intel Corporation JHL6540 Thunderbolt 3 NHI (C step) [Alpine Ridge 4C 2016] (rev 02) 2d:00.0 USB controller: Intel Corporation JHL6540 Thunderbolt 3 USB Controller (C step) [Alpine Ridge 4C 2016] (rev 02) ``` ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Mar 17
[Touch-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
@advadrako would you mind sharing that file? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+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 1867766] Re: Namespace prefix sodipodi on namedview is not defined
This bug was fixed in the package ubuntu-themes - 19.04-0ubuntu3 --- ubuntu-themes (19.04-0ubuntu3) focal; urgency=medium * Preserve namespace declarations in the script that combines multiple SVG files into one (LP: #1867766) -- Olivier Tilloy Tue, 17 Mar 2020 16:56:03 +0100 ** Changed in: ubuntu-themes (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1867766 Title: Namespace prefix sodipodi on namedview is not defined Status in librsvg package in Ubuntu: Invalid Status in ubuntu-themes package in Ubuntu: Fix Released Bug description: [Summary] Since the package "gir1.2-rsvg-2.0:amd64" been upgraded from 2.46.4-1ubuntu1 to 2.48.0-1 in Focal's daily build, ubiquity will crash as attached crash log. [Steps to reproduce] 1. Boot with OEM mode, 2. Finish the 1st stage 3. Reboot 4. Boot into OOBE(oem-config) [Expected result] Should start oobe without any error. [Actual result] The error message 『The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again.』shown on the screen. [Failure rate] 100% [Additional information] No idea why, but some "nm-signal-*-secure" images will fail in Gtk.IconTheme().lookup_icon(n, 22, 0).load_icon(), and below error message will show: " Gtk-WARNING **: 18:23:31.380: Could not load a pixbuf from icon theme. This may indicate that pixbuf loaders or the mime database could not be found. gi.repository.GLib.GError: rsvg-error-quark: XML parse error: error code=201 (3) in (null):40:466: Namespace prefix sodipodi on namedview is not defined " To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1867766/+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 1863239] Re: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group
Please provide the udevadm database dump about the device in question a) when it has correct group b) when it does not. ** Changed in: udev (Ubuntu) Status: New => Invalid -- 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/1863239 Title: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group Status in libmtp package in Ubuntu: New Status in pulseaudio package in Ubuntu: Invalid Status in systemd package in Ubuntu: Incomplete Status in udev package in Ubuntu: Invalid Bug description: When testing HPLIP I found out that CUPS backends can access my printer only when they are running as root, when they are running as the special user lp, as it is usually the case, they cannot access the printer. So I tried to find out why and saw that the /dev/bus/usb/*/* device file for the printer has group ownership "audio" and not "lp": till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ ll /dev/bus/usb/*/* crw-rw-r-- 1 root root189, 0 Feb 11 14:17 /dev/bus/usb/001/001 crw-rw-r-- 1 root root189, 2 Feb 11 14:17 /dev/bus/usb/001/003 crw-rw-r-- 1 root root189, 3 Feb 11 14:17 /dev/bus/usb/001/004 crw-rw-r-- 1 root plugdev 189, 4 Feb 14 12:23 /dev/bus/usb/001/005 crw-rw-r-- 1 root root189, 5 Feb 11 14:17 /dev/bus/usb/001/006 crw-rw+ 1 root audio 189, 62 Feb 14 12:37 /dev/bus/usb/001/063 crw-rw-r-- 1 root root189, 128 Feb 11 14:17 /dev/bus/usb/002/001 crw-rw-r-- 1 root root189, 130 Feb 13 09:38 /dev/bus/usb/002/003 till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ The printer is the device /dev/bus/usb/001/063: till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ lsusb Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch sensor Bus 001 Device 063: ID 03f0:7a12 HP, Inc HP OfficeJet Pro 8730 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ There must be a bug somewhere in the UDEV rules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1863239/+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 1863239] Re: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group
udev source package is obsolete and is not used since precise. ** Changed in: systemd (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/1863239 Title: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group Status in libmtp package in Ubuntu: New Status in pulseaudio package in Ubuntu: Invalid Status in systemd package in Ubuntu: Incomplete Status in udev package in Ubuntu: Invalid Bug description: When testing HPLIP I found out that CUPS backends can access my printer only when they are running as root, when they are running as the special user lp, as it is usually the case, they cannot access the printer. So I tried to find out why and saw that the /dev/bus/usb/*/* device file for the printer has group ownership "audio" and not "lp": till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ ll /dev/bus/usb/*/* crw-rw-r-- 1 root root189, 0 Feb 11 14:17 /dev/bus/usb/001/001 crw-rw-r-- 1 root root189, 2 Feb 11 14:17 /dev/bus/usb/001/003 crw-rw-r-- 1 root root189, 3 Feb 11 14:17 /dev/bus/usb/001/004 crw-rw-r-- 1 root plugdev 189, 4 Feb 14 12:23 /dev/bus/usb/001/005 crw-rw-r-- 1 root root189, 5 Feb 11 14:17 /dev/bus/usb/001/006 crw-rw+ 1 root audio 189, 62 Feb 14 12:37 /dev/bus/usb/001/063 crw-rw-r-- 1 root root189, 128 Feb 11 14:17 /dev/bus/usb/002/001 crw-rw-r-- 1 root root189, 130 Feb 13 09:38 /dev/bus/usb/002/003 till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ The printer is the device /dev/bus/usb/001/063: till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ lsusb Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch sensor Bus 001 Device 063: ID 03f0:7a12 HP, Inc HP OfficeJet Pro 8730 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ There must be a bug somewhere in the UDEV rules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1863239/+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 1865504] Re: hwclock reports incorrect status in audit message
** Tags added: verification-done-eoan
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1865504
Title:
hwclock reports incorrect status in audit message
Status in util-linux package in Ubuntu:
Fix Released
Status in util-linux source package in Bionic:
Fix Committed
Status in util-linux source package in Eoan:
Fix Committed
Status in util-linux package in Debian:
Unknown
Bug description:
[Impact]
hwclock reports incorrect status in audit message:
- hwclock calls audit_log_user_message(3) to create an audit entry.
- audit_log_user_message(3) result 1 is "success" and 0 is "failed".
- hwclock use standard EXIT_{SUCCESS,FAILURE} macros with reverse status.
- Thus reports its status incorrectly in audit message.
It is a requirement for Common Criteria Certification that hwclock
reports correct status in audit message.
This has been fixed upstream in https://github.com/karelzak/util-
linux/commit/189edf1fe501ea39b35911337eab1740888fae7a
[Test Steps]
Steps to test:
1. Install auditd
2. Run following testcase,
# hwclock
2020-03-02 15:03:03.280351+
# hwclock --set --date "1/1/2000 00:00:00"
# echo $?
0
# hwclock
2000-01-01 00:00:05.413924+
# hwclock --utc --systohc
# echo $?
0
# hwclock
2020-03-02 15:07:00.264331+
Following audit messages from /var/log/audit/audit.log,
Note that last field in each audit record produced when hardware clock
was modified has, "res=failed". Although, testcase shows no* failure
occurred.
type=USYS_CONFIG msg=audit(1583161562.884:105): pid=2084 uid=0
auid=1000 ses=1 msg='op=change-system-time exe="/sbin/hwclock"
hostname=bionic-fips addr=? terminal=pts/0 res=failed'
type=USYS_CONFIG msg=audit(1583161614.497:106): pid=2103 uid=0
auid=1000 ses=1 msg='op=change-system-time exe="/sbin/hwclock"
hostname=bionic-fips addr=? terminal=pts/0 res=failed'
[Regression Potential]
Changes limited to the result value passed to audit_log_user_message(3),
so the audit messages will change the 'res=' field (to correct result.)
There should not be any regression to fix the status given to auditd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1865504/+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 1863239] Re: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group
pulseaudio doesn't ship any udev rules that change group permissions of devices. Plus it doesn't run as root, but as an unprivileged user. ** Changed in: pulseaudio (Ubuntu) Status: New => Invalid -- 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/1863239 Title: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group Status in libmtp package in Ubuntu: New Status in pulseaudio package in Ubuntu: Invalid Status in systemd package in Ubuntu: Incomplete Status in udev package in Ubuntu: Invalid Bug description: When testing HPLIP I found out that CUPS backends can access my printer only when they are running as root, when they are running as the special user lp, as it is usually the case, they cannot access the printer. So I tried to find out why and saw that the /dev/bus/usb/*/* device file for the printer has group ownership "audio" and not "lp": till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ ll /dev/bus/usb/*/* crw-rw-r-- 1 root root189, 0 Feb 11 14:17 /dev/bus/usb/001/001 crw-rw-r-- 1 root root189, 2 Feb 11 14:17 /dev/bus/usb/001/003 crw-rw-r-- 1 root root189, 3 Feb 11 14:17 /dev/bus/usb/001/004 crw-rw-r-- 1 root plugdev 189, 4 Feb 14 12:23 /dev/bus/usb/001/005 crw-rw-r-- 1 root root189, 5 Feb 11 14:17 /dev/bus/usb/001/006 crw-rw+ 1 root audio 189, 62 Feb 14 12:37 /dev/bus/usb/001/063 crw-rw-r-- 1 root root189, 128 Feb 11 14:17 /dev/bus/usb/002/001 crw-rw-r-- 1 root root189, 130 Feb 13 09:38 /dev/bus/usb/002/003 till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ The printer is the device /dev/bus/usb/001/063: till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ lsusb Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch sensor Bus 001 Device 063: ID 03f0:7a12 HP, Inc HP OfficeJet Pro 8730 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ There must be a bug somewhere in the UDEV rules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1863239/+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 1865504] Re: hwclock reports incorrect status in audit message
Successful verification on amd64 for bionic
$ dpkg -l | grep util-linux
ii util-linux2.31.1-0.4ubuntu3.6
amd64miscellaneous system utilities
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.3 LTS"
type=USYS_CONFIG msg=audit(1584464596.658:106): pid=13437 uid=0
auid=1000 ses=1 msg='op=change-system-time exe="/sbin/hwclock" hostname
=bionic-fips addr=? terminal=pts/0 res=success'
type=USYS_CONFIG msg=audit(1584464615.494:117): pid=13441 uid=0
auid=1000 ses=1 msg='op=change-system-time exe="/sbin/hwclock" hostname
=bionic-fips addr=? terminal=pts/0 res=success'
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1865504
Title:
hwclock reports incorrect status in audit message
Status in util-linux package in Ubuntu:
Fix Released
Status in util-linux source package in Bionic:
Fix Committed
Status in util-linux source package in Eoan:
Fix Committed
Status in util-linux package in Debian:
Unknown
Bug description:
[Impact]
hwclock reports incorrect status in audit message:
- hwclock calls audit_log_user_message(3) to create an audit entry.
- audit_log_user_message(3) result 1 is "success" and 0 is "failed".
- hwclock use standard EXIT_{SUCCESS,FAILURE} macros with reverse status.
- Thus reports its status incorrectly in audit message.
It is a requirement for Common Criteria Certification that hwclock
reports correct status in audit message.
This has been fixed upstream in https://github.com/karelzak/util-
linux/commit/189edf1fe501ea39b35911337eab1740888fae7a
[Test Steps]
Steps to test:
1. Install auditd
2. Run following testcase,
# hwclock
2020-03-02 15:03:03.280351+
# hwclock --set --date "1/1/2000 00:00:00"
# echo $?
0
# hwclock
2000-01-01 00:00:05.413924+
# hwclock --utc --systohc
# echo $?
0
# hwclock
2020-03-02 15:07:00.264331+
Following audit messages from /var/log/audit/audit.log,
Note that last field in each audit record produced when hardware clock
was modified has, "res=failed". Although, testcase shows no* failure
occurred.
type=USYS_CONFIG msg=audit(1583161562.884:105): pid=2084 uid=0
auid=1000 ses=1 msg='op=change-system-time exe="/sbin/hwclock"
hostname=bionic-fips addr=? terminal=pts/0 res=failed'
type=USYS_CONFIG msg=audit(1583161614.497:106): pid=2103 uid=0
auid=1000 ses=1 msg='op=change-system-time exe="/sbin/hwclock"
hostname=bionic-fips addr=? terminal=pts/0 res=failed'
[Regression Potential]
Changes limited to the result value passed to audit_log_user_message(3),
so the audit messages will change the 'res=' field (to correct result.)
There should not be any regression to fix the status given to auditd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1865504/+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 1865504] Re: hwclock reports incorrect status in audit message
autopkgtests
---
All test failures (except mysql-5.7 on bionic) were transient, and
passed w/ one retry.
The test failure for mysql-5.7/bionic is unrelated to this upload.
Confirmed w/ a retry on -updates and -proposed.
Both fail in the same way:
mysql-5.7 [bionic/amd64]
Version TriggersDateDurationRequester Result
5.7.29-0ubuntu0.18.04.1 util-linux/2.31.1-0.4ubuntu3.5 2020-03-17
11:02:44 UTC 0h 43m 09s mfo faillog artifacts ♻
5.7.29-0ubuntu0.18.04.1 util-linux/2.31.1-0.4ubuntu3.6 2020-03-17
10:55:08 UTC 0h 35m 47s mfo faillog artifacts ♻
"""
Completed: Failed 1/780 tests, 99.87% were successful.
Failing test(s): main.events_1
"""
The pending-sru page [1] is already up-to-date and shows only the
msyql-5.7 (unrelated) failures.
cheers,
Mauricio
[1] https://people.canonical.com/~ubuntu-archive/pending-sru.html
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1865504
Title:
hwclock reports incorrect status in audit message
Status in util-linux package in Ubuntu:
Fix Released
Status in util-linux source package in Bionic:
Fix Committed
Status in util-linux source package in Eoan:
Fix Committed
Status in util-linux package in Debian:
Unknown
Bug description:
[Impact]
hwclock reports incorrect status in audit message:
- hwclock calls audit_log_user_message(3) to create an audit entry.
- audit_log_user_message(3) result 1 is "success" and 0 is "failed".
- hwclock use standard EXIT_{SUCCESS,FAILURE} macros with reverse status.
- Thus reports its status incorrectly in audit message.
It is a requirement for Common Criteria Certification that hwclock
reports correct status in audit message.
This has been fixed upstream in https://github.com/karelzak/util-
linux/commit/189edf1fe501ea39b35911337eab1740888fae7a
[Test Steps]
Steps to test:
1. Install auditd
2. Run following testcase,
# hwclock
2020-03-02 15:03:03.280351+
# hwclock --set --date "1/1/2000 00:00:00"
# echo $?
0
# hwclock
2000-01-01 00:00:05.413924+
# hwclock --utc --systohc
# echo $?
0
# hwclock
2020-03-02 15:07:00.264331+
Following audit messages from /var/log/audit/audit.log,
Note that last field in each audit record produced when hardware clock
was modified has, "res=failed". Although, testcase shows no* failure
occurred.
type=USYS_CONFIG msg=audit(1583161562.884:105): pid=2084 uid=0
auid=1000 ses=1 msg='op=change-system-time exe="/sbin/hwclock"
hostname=bionic-fips addr=? terminal=pts/0 res=failed'
type=USYS_CONFIG msg=audit(1583161614.497:106): pid=2103 uid=0
auid=1000 ses=1 msg='op=change-system-time exe="/sbin/hwclock"
hostname=bionic-fips addr=? terminal=pts/0 res=failed'
[Regression Potential]
Changes limited to the result value passed to audit_log_user_message(3),
so the audit messages will change the 'res=' field (to correct result.)
There should not be any regression to fix the status given to auditd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1865504/+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 1865504] Re: hwclock reports incorrect status in audit message
Successful verification on amd64 for eaon
$ dpkg -l | grep util-linux
ii util-linux 2.34-0.1ubuntu2.4
amd64miscellaneous system utilities
Audit records found in /var/log/audit/audit.log,
type=USYS_CONFIG msg=audit(1584463433.533:68): pid=4263 uid=0 auid=1000
ses=1 msg='op=change-system-time exe="/usr/sbin/hwclock" hostname=eaon-
server addr=? terminal=pts/0 res=success'
type=USYS_CONFIG msg=audit(1584463480.497:81): pid=4268 uid=0 auid=1000
ses=1 msg='op=change-system-time exe="/usr/sbin/hwclock" hostname=eaon-
server addr=? terminal=pts/0 res=success'
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1865504
Title:
hwclock reports incorrect status in audit message
Status in util-linux package in Ubuntu:
Fix Released
Status in util-linux source package in Bionic:
Fix Committed
Status in util-linux source package in Eoan:
Fix Committed
Status in util-linux package in Debian:
Unknown
Bug description:
[Impact]
hwclock reports incorrect status in audit message:
- hwclock calls audit_log_user_message(3) to create an audit entry.
- audit_log_user_message(3) result 1 is "success" and 0 is "failed".
- hwclock use standard EXIT_{SUCCESS,FAILURE} macros with reverse status.
- Thus reports its status incorrectly in audit message.
It is a requirement for Common Criteria Certification that hwclock
reports correct status in audit message.
This has been fixed upstream in https://github.com/karelzak/util-
linux/commit/189edf1fe501ea39b35911337eab1740888fae7a
[Test Steps]
Steps to test:
1. Install auditd
2. Run following testcase,
# hwclock
2020-03-02 15:03:03.280351+
# hwclock --set --date "1/1/2000 00:00:00"
# echo $?
0
# hwclock
2000-01-01 00:00:05.413924+
# hwclock --utc --systohc
# echo $?
0
# hwclock
2020-03-02 15:07:00.264331+
Following audit messages from /var/log/audit/audit.log,
Note that last field in each audit record produced when hardware clock
was modified has, "res=failed". Although, testcase shows no* failure
occurred.
type=USYS_CONFIG msg=audit(1583161562.884:105): pid=2084 uid=0
auid=1000 ses=1 msg='op=change-system-time exe="/sbin/hwclock"
hostname=bionic-fips addr=? terminal=pts/0 res=failed'
type=USYS_CONFIG msg=audit(1583161614.497:106): pid=2103 uid=0
auid=1000 ses=1 msg='op=change-system-time exe="/sbin/hwclock"
hostname=bionic-fips addr=? terminal=pts/0 res=failed'
[Regression Potential]
Changes limited to the result value passed to audit_log_user_message(3),
so the audit messages will change the 'res=' field (to correct result.)
There should not be any regression to fix the status given to auditd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1865504/+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 1848202] Re: Use after free in gdbus leads to eds segfaults
Bug #1844853 was explicitly verified (again, comment #31 this time). Didn't observe any unexpected behavior due to the glib2.0 upgrade. ** Tags removed: verification-needed verification-needed-eoan ** Tags added: verification-done verification-done-eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1848202 Title: Use after free in gdbus leads to eds segfaults Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Eoan: Fix Committed Bug description: [ Description ] The Ubuntu Error Tracker has been receiving reports about a problem regarding evolution-data-server. This problem was most recently seen with package version 3.34.1-1, the problem page at https://errors.ubuntu.com/problem/b1f62616406e36e521fd1fb1d2be4ac2fe9a2cda contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. [ Fix ] This bug was fixed upstream in 2.62.2 (see the links below). That update is being issues to eoan. [ QA ] Under https://wiki.ubuntu.com/StableReleaseUpdates/GNOME, we don't need to explicitly test that this bug is fixed. Nevertheless, to verify this bug please give the desktop a good workout. Ideally install the SRU and use your machine as you would normally for a variety of tasks. Make sure there are no regressions. [ Regression potential ] 1) The changes involve mutexes and stuff, which is error prone. 2) It's GLib, a core library, so any bad regressions will be really serious for the desktop as a whole. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1848202/+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 1850932] Re: [SRU] Backport 2.62.4-1
Bug #1844853 was explicitly verified (again, comment #31 this time). Didn't observe any unexpected behavior due to the glib2.0 upgrade. ** Tags removed: verification-needed verification-needed-eoan ** Tags added: verification-done verification-done-eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1850932 Title: [SRU] Backport 2.62.4-1 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Eoan: Fix Committed Bug description: [ Description ] I'm creating this bug report to have a place to describe the proposed backport of glib2.0 2.62.4-1 from focal. One purpose of this backport is to fix bug #1844853. But there are several other changes. Here's the diff of NEWS: +Overview of changes in GLib 2.62.4 +== + +* Apply recursion depth limits to variants in D-Bus messages (!1290) + +* Bugs fixed: + - #1938 GDateTime doesn't support leap seconds + - !1240 Backport !1233 “gdatetime: Handle leap seconds in ISO8601 dates” +to glib-2-62 + - !1257 Backport !1232 “kqueue: Do not return early from _kqsub_cancel” +to glib-2-62 + - !1266 Backport !1265 “build: don't check for protected visibility” to +glib-2-62 + - !1276 Backport !1274 “trash portal: Don't follow symlinks” to glib-2-62 + - !1290 Backport !1201 “gdbusmessage: Limit recursion of variants in +D-Bus messages” to glib-2-62 + +Overview of changes in GLib 2.62.3 +== + +* Use `poll()` in `g_spawn_sync()` rather than `select()`, which is subject to + FD limits (#954) + +* Fix undefined behaviour with `g_utf8_find_prev_char()` (#1917) + +* Bugs fixed: + - #954 The g_spawn_sync() function uses select() which has limitations + - #1318 rare failure in gdbus-peer test: invalid uninstantiatable type '(null)' in cast to 'GDBusServer' + - #1897 glib 2.62.0 fails test 'test_writev_no_vectors' wih gcc7 + - #1903 use-after-free in mimeapps test causes intermittent segfault during testing + - #1916 objcopy not used from cross-compilation file in GIO tests + - #1917 Test utf8-pointer fails with static build, LTO, optimisations, and new GCC + - !1174 Backport !1164 “use-after-free fix in mimeapps test” to glib-2-62 + - !1184 Backport !1173 “gvariant: Limit recursion in g_variant_parse()” to glib-2-62 + - !1194 Backport !1176, !1183, !1188, !1191 to `glib-2-62` + - !1203 Backport !1192, !1193, !1197 Fixes for gdbus-peer tests to glib-2-62 + - !1207 Backport !1206 “goption: Relax assertion to avoid being broken by kdeinit5” to glib-2-62 + - !1215 [2.62] gdbus-peer: Specifically listen on 127.0.0.1 + - !1219 Backport !1218 “gdb: Fix GHashTable pretty printer off-by-one error” + - !1222 Backport !1221 “Add NOTE_REVOKE to the list of the monitoring events” to glib-2-62 + - !1228 Backport !1199 “gunicode: Fix UB in gutf8.c and utf8-pointer test” to glib-2-62 + + +Overview of changes in GLib 2.62.2 +== + +* Bugs fixed: + - #1896 Use after free when calling g_dbus_connection_flush_sync() in a dedicated thread + - !1154 Backport !1152 “gwinhttpvfs: Handle g_get_prgname() returning NULL” to glib-2-62 + - !1156 Backport !1146 Solaris fixes to glib-2-62 This release can be considered to be tested under https://wiki.ubuntu.com/StableReleaseUpdates/GNOME There are patches from the upstream master branch rather than this stable release: + Add-a-test-for-GDBusServer-authentication.patch + gdbus-server-auth-test-Create-temporary-directory-for-Uni.patch + gdbus-server-auth-test-Include-gcredentialsprivate.h.patch + Make-ld-executable-configurable.patch They are sensible backports which I hope are appropriate for SRU. [ QA ] The testsuite fixes will verify themselves during the build and autopkgtest. For the rest of the fixes, please exercise the desktop thoroughly. Log in, log out, run many applications and make sure there are no regressions. [ Regression potential ] test fixes> Build failures or autopkgtest failures. GLib is a central desktop library. Regressions could break any part of the desktop - so QA is important, the SRU exception notwithstanding. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1850932/+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 1867766] Re: Namespace prefix sodipodi on namedview is not defined
** Changed in: ubuntu-themes (Ubuntu) Status: In Progress => Fix Committed ** Changed in: librsvg (Ubuntu) Assignee: Olivier Tilloy (osomon) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1867766 Title: Namespace prefix sodipodi on namedview is not defined Status in librsvg package in Ubuntu: Invalid Status in ubuntu-themes package in Ubuntu: Fix Committed Bug description: [Summary] Since the package "gir1.2-rsvg-2.0:amd64" been upgraded from 2.46.4-1ubuntu1 to 2.48.0-1 in Focal's daily build, ubiquity will crash as attached crash log. [Steps to reproduce] 1. Boot with OEM mode, 2. Finish the 1st stage 3. Reboot 4. Boot into OOBE(oem-config) [Expected result] Should start oobe without any error. [Actual result] The error message 『The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again.』shown on the screen. [Failure rate] 100% [Additional information] No idea why, but some "nm-signal-*-secure" images will fail in Gtk.IconTheme().lookup_icon(n, 22, 0).load_icon(), and below error message will show: " Gtk-WARNING **: 18:23:31.380: Could not load a pixbuf from icon theme. This may indicate that pixbuf loaders or the mime database could not be found. gi.repository.GLib.GError: rsvg-error-quark: XML parse error: error code=201 (3) in (null):40:466: Namespace prefix sodipodi on namedview is not defined " To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1867766/+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 1864274] Re: crunchy pixels
** Also affects: mesa (Ubuntu Focal)
Importance: Undecided
Status: Confirmed
** Changed in: mesa (Ubuntu Focal)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
** Tags removed: champagne
--
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/1864274
Title:
crunchy pixels
Status in Mesa:
Unknown
Status in mesa package in Ubuntu:
Confirmed
Status in mesa source package in Focal:
Confirmed
Bug description:
Hello, after upgrading firefox (and many other packages) on focal
today, I've got some video artifacts in firefox.
When typing in text boxes and text fields, the new character is drawn
very slowly, pixel-by-pixel, and isn't complete until the cursor has
moved on. When larger portions of the screen are updated, it looks a
lot like the entire window is being run through a video codec or you
can see parts of the video memory from other processes. (But it looks
more deliberate and predictable than either of these descriptions.)
So far Firefox is the only application I've found that is affected.
urxvt, libreoffice, xfontsel, glxgears all seem to work as expected.
I did get cairo package update today, but the changelog is just:
pango1.0 (1.44.7-1ubuntu2) focal; urgency=medium
* No-change rebuild with fixed binutils on arm64.
-- Matthias Klose Sat, 08 Feb 2020 11:15:23 +
And an xorg update:
xorg (1:7.7+19ubuntu14) focal; urgency=medium
* No-change rebuild with fixed binutils on arm64.
-- Matthias Klose Sat, 08 Feb 2020 11:21:28 +
So I don't believe these are involved.
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620
(rev 07)
Thanks
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 73.0.1+build1-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k5.4.0-14-generic.
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sarnold3296 F pulseaudio
/dev/snd/controlC0: sarnold3296 F pulseaudio
BuildID: 20200217142647
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 144'
Mixer name : 'Realtek ALC285'
Components : 'HDA:10ec0285,17aa225c,0012
HDA:8086280b,80860101,0010'
Controls : 53
Simple ctrls : 15
Card1.Amixer.info:
Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at
usb-:00:14.0-4.2.4, high speed'
Mixer name : 'USB Mixer'
Components : 'USB17ef:306f'
Controls : 9
Simple ctrls : 4
Channel: Unavailable
Date: Sat Feb 22 05:41:10 2020
ForcedLayersAccel: False
IncompatibleExtensions:
Pentadactyl - pentadac...@dactyl.googlecode.com
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
IpRoute:
default via 192.168.0.1 dev enp0s31f6 proto dhcp metric 100
10.23.231.0/24 dev lxdbr0 proto kernel scope link src 10.23.231.1
192.168.0.0/24 dev enp0s31f6 proto kernel scope link src 192.168.0.34 metric
100
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
linkdown
MostRecentCrashID: bp-ea952d4d-f25a-4ced-893c-8cabb2160112
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:737
PrefSources: prefs.js
ProcEnviron:
TERM=rxvt-unicode-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=73.0.1/20200217142647 (In use)
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: Upgraded to focal on 2020-01-24 (28 days ago)
dmi.bios.date: 11/25/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N23ET69W (1.44 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20KHCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrN23ET69W(1.44):bd11/25/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 6th
dmi.product.name: 20KHCTO1WW
dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
dmi.product.version: ThinkPad X1 Carbon 6th
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1864274/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to :
[Touch-packages] [Bug 1844853] Re: IBus no longer works in Qt applications after upgrade
I have verified the testcase on eoan using version
2.62.4-1~ubuntu19.10.1 of the libglib2.0-* packages from eoan-proposed
and version 1.5.21-1~exp2ubuntu2.1 of the ibus packages from ppa:ubuntu-
security-proposed/ppa.
As regards the autopkgtest failure, please see:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1850932/comments/12
** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1844853
Title:
IBus no longer works in Qt applications after upgrade
Status in GLib:
Fix Released
Status in ibus:
Fix Released
Status in glib2.0 package in Ubuntu:
Fix Released
Status in ibus package in Ubuntu:
Fix Released
Status in glib2.0 source package in Xenial:
Fix Committed
Status in glib2.0 source package in Bionic:
Fix Committed
Status in glib2.0 source package in Disco:
Won't Fix
Status in glib2.0 source package in Eoan:
Fix Committed
Status in glib2.0 source package in Focal:
Fix Released
Status in ibus source package in Focal:
Fix Released
Status in glib2.0 package in Debian:
Fix Released
Bug description:
[Impact]
IBus was broken for Qt applications as a regression due to the fix of
CVE-2019-14822. As a result the IBus patch was disabled temporarily,
which fixed IBus from a usability POV.
The real fix has been made in glib2.0, and the updates in -proposed
will allow the IBus patch to be re-enabled.
[Test Case]
* On a standard Ubuntu {eoan,disco,bionic,xenial} installation
- Upgrade the glib2.0 packages from
{eoan,disco,bionic,xenial}-proposed
- Upgrade the ibus packages from
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa
- Install some IBus input method, e.g. ibus-libpinyin
- Install some Qt application, e.g. Kate
* Relogin (maybe reboot)
* Add the input method to the input sources
* Open the Qt app and try to input something using the IBus IM
=> Find that the transliteration works as expected
[Regression Potential]
The applicable patches origin from glib upstream:
https://gitlab.gnome.org/GNOME/glib/merge_requests/1176
Consequently the changes have been reviewed by the glib maintainer, but also
tested by the IBus maintainer, by me (gunnarhj), and - of course - the author
Simon McVittie. The changes have been in Debian unstable since 2019-10-30.
[Original description]
Kubuntu Release 18.04.3 LTS
Expected behavior:
ibus continues working as before after applying security update
1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5.
Observed behavior:
ibus is not usable anymore in Qt applications.
After updating ibus and the related packages ibus-gtk, ibus-gtk3,
libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to
1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using
shift-space no longer changes the selected input method and even when i switch
to the mozc input method in a gtk application, i can not use it in any Qt
applications.
When starting qtconfig in a terminal, I also get the following message:
Bus::open: Connect ibus failed!
IBusInputContext::createInputContext: no connection to ibus-daemon
This bug was not present in version 1.5.17-3ubuntu5 and I also
confirmed that downgrading the packages to version 1.5.17-3ubuntu4
restores ibus functionality in Qt applications.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ibus 1.5.17-3ubuntu5.1
ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-30-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: KDE
Date: Sat Sep 21 07:58:56 2019
InstallationDate: Installed on 2019-06-28 (84 days ago)
InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
SourcePackage: ibus
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1844853/+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 1866194] Re: After connecting an external output device (USB audio interface, Bluetooth speaker...), it shows up in the sound output options but the sound keeps being emitted fro
** Tags removed: rls-ff-incoming -- 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/1866194 Title: After connecting an external output device (USB audio interface, Bluetooth speaker...), it shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu version: focal dev Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 Device CID: 201704-25503 Steps to reproduce: 1. Go to Bluetooth settings panel 2. Pair a BT device 3. Make sure it's marked as Connected, and go to the Sound settings 4. Make sure it's the one selected as "Output device" 5. Click "Test" -> the test sound outputs from the internal laptop speakers (NOK) 6. Select "Speakers - Built-in Audio" as Output device and click "Test" -> the test sound outputs from the internal laptop speakers (OK) 7. Try to switch back to the BT device and click Test -> same result as in step 5 Tested with 2 different BT devices (one headset and one speaker) Attached are btmon logs captured during the procedure described above, and pactl logs capture after step 7. Up to this morning, it was harder to connect the BT device, but once connected, the sound would output on it as expected. Now, the BT connection seems to work better, but I can't output the sound to the BT device... I tried to reboot the device, and also to suspend/resume, but in each case, the BT device can connect back, but the sound is still output from the internal laptop speakers, even when the BT device is selected in the Sound settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 1566 F pulseaudio /dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio /dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 22:15:50 2020 InstallationDate: Installed on 2020-01-17 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1866194/+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 1867766] Re: Namespace prefix sodipodi on namedview is not defined
** Changed in: ubuntu-themes (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: ubuntu-themes (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-themes (Ubuntu) Status: New => In Progress ** Changed in: librsvg (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1867766 Title: Namespace prefix sodipodi on namedview is not defined Status in librsvg package in Ubuntu: Invalid Status in ubuntu-themes package in Ubuntu: Fix Committed Bug description: [Summary] Since the package "gir1.2-rsvg-2.0:amd64" been upgraded from 2.46.4-1ubuntu1 to 2.48.0-1 in Focal's daily build, ubiquity will crash as attached crash log. [Steps to reproduce] 1. Boot with OEM mode, 2. Finish the 1st stage 3. Reboot 4. Boot into OOBE(oem-config) [Expected result] Should start oobe without any error. [Actual result] The error message 『The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again.』shown on the screen. [Failure rate] 100% [Additional information] No idea why, but some "nm-signal-*-secure" images will fail in Gtk.IconTheme().lookup_icon(n, 22, 0).load_icon(), and below error message will show: " Gtk-WARNING **: 18:23:31.380: Could not load a pixbuf from icon theme. This may indicate that pixbuf loaders or the mime database could not be found. gi.repository.GLib.GError: rsvg-error-quark: XML parse error: error code=201 (3) in (null):40:466: Namespace prefix sodipodi on namedview is not defined " To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1867766/+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 1867766] Re: Namespace prefix sodipodi on namedview is not defined
even in building ubiquity it will fail in : (run:75635): Gtk-WARNING **: 23:32:02.334: Could not load a pixbuf from icon theme. This may indicate that pixbuf loaders or the mime database could not be found. Exception in GTK frontend (invoking crash handler): Traceback (most recent call last): File "./ubiquity/frontend/gtk_components/nmwidgets.py", line 330, in __init__ self.view = NetworkManagerTreeView(self.state_changed) File "./ubiquity/frontend/gtk_components/nmwidgets.py", line 96, in __init__ self.configure_icons() File "./ubiquity/frontend/gtk_components/nmwidgets.py", line 196, in configure_icons ico = ico.load_icon() gi.repository.GLib.GError: rsvg-error-quark: XML parse error: error code=201 (3) in (null):40:466: Namespace prefix sodipodi on namedview is not defined (0) Traceback (most recent call last): File "./ubiquity/frontend/gtk_components/nmwidgets.py", line 330, in __init__ self.view = NetworkManagerTreeView(self.state_changed) File "./ubiquity/frontend/gtk_components/nmwidgets.py", line 96, in __init__ self.configure_icons() File "./ubiquity/frontend/gtk_components/nmwidgets.py", line 196, in configure_icons ico = ico.load_icon() gi.repository.GLib.Error: rsvg-error-quark: XML parse error: error code=201 (3) in (null):40:466: Namespace prefix sodipodi on namedview is not defined (0) xauth/Xrdb output: -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1867766 Title: Namespace prefix sodipodi on namedview is not defined Status in librsvg package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: New Bug description: [Summary] Since the package "gir1.2-rsvg-2.0:amd64" been upgraded from 2.46.4-1ubuntu1 to 2.48.0-1 in Focal's daily build, ubiquity will crash as attached crash log. [Steps to reproduce] 1. Boot with OEM mode, 2. Finish the 1st stage 3. Reboot 4. Boot into OOBE(oem-config) [Expected result] Should start oobe without any error. [Actual result] The error message 『The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again.』shown on the screen. [Failure rate] 100% [Additional information] No idea why, but some "nm-signal-*-secure" images will fail in Gtk.IconTheme().lookup_icon(n, 22, 0).load_icon(), and below error message will show: " Gtk-WARNING **: 18:23:31.380: Could not load a pixbuf from icon theme. This may indicate that pixbuf loaders or the mime database could not be found. gi.repository.GLib.GError: rsvg-error-quark: XML parse error: error code=201 (3) in (null):40:466: Namespace prefix sodipodi on namedview is not defined " To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1867766/+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 1867766] Re: Namespace prefix sodipodi on namedview is not defined
even in build ubiquity it will failed in : (run:75635): Gtk-WARNING **: 23:32:02.334: Could not load a pixbuf from icon theme. This may indicate that pixbuf loaders or the mime database could not be found. Exception in GTK frontend (invoking crash handler): Traceback (most recent call last): File "./ubiquity/frontend/gtk_components/nmwidgets.py", line 330, in __init__ self.view = NetworkManagerTreeView(self.state_changed) File "./ubiquity/frontend/gtk_components/nmwidgets.py", line 96, in __init__ self.configure_icons() File "./ubiquity/frontend/gtk_components/nmwidgets.py", line 196, in configure_icons ico = ico.load_icon() gi.repository.GLib.GError: rsvg-error-quark: XML parse error: error code=201 (3) in (null):40:466: Namespace prefix sodipodi on namedview is not defined (0) Traceback (most recent call last): File "./ubiquity/frontend/gtk_components/nmwidgets.py", line 330, in __init__ self.view = NetworkManagerTreeView(self.state_changed) File "./ubiquity/frontend/gtk_components/nmwidgets.py", line 96, in __init__ self.configure_icons() File "./ubiquity/frontend/gtk_components/nmwidgets.py", line 196, in configure_icons ico = ico.load_icon() gi.repository.GLib.Error: rsvg-error-quark: XML parse error: error code=201 (3) in (null):40:466: Namespace prefix sodipodi on namedview is not defined (0) xauth/Xrdb output: -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1867766 Title: Namespace prefix sodipodi on namedview is not defined Status in librsvg package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: New Bug description: [Summary] Since the package "gir1.2-rsvg-2.0:amd64" been upgraded from 2.46.4-1ubuntu1 to 2.48.0-1 in Focal's daily build, ubiquity will crash as attached crash log. [Steps to reproduce] 1. Boot with OEM mode, 2. Finish the 1st stage 3. Reboot 4. Boot into OOBE(oem-config) [Expected result] Should start oobe without any error. [Actual result] The error message 『The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again.』shown on the screen. [Failure rate] 100% [Additional information] No idea why, but some "nm-signal-*-secure" images will fail in Gtk.IconTheme().lookup_icon(n, 22, 0).load_icon(), and below error message will show: " Gtk-WARNING **: 18:23:31.380: Could not load a pixbuf from icon theme. This may indicate that pixbuf loaders or the mime database could not be found. gi.repository.GLib.GError: rsvg-error-quark: XML parse error: error code=201 (3) in (null):40:466: Namespace prefix sodipodi on namedview is not defined " To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1867766/+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 1809132] Re: Updated bionic to the current 1.10 stable version
SRUing the newer version failed since it changed behaviour in some configuration which created issue for existing users. There isn't anyone currently working on resolving those issues so it's more realistic to untarget from Bionic. If the problem really needs to be resolved in that serie best to go through the rls-bb-incoming nomination process again. ** Changed in: network-manager (Ubuntu Bionic) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1809132 Title: Updated bionic to the current 1.10 stable version Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Won't Fix Bug description: * Impact The updates in the stable serie include several fixes for misbehaviour, segfaults and security issues, those are the sort of improvements that should be in the LTS The detail of the changes can be seen in the NEWS entry https://gitlab.freedesktop.org/NetworkManager/NetworkManager/blob/nm-1-10/NEWS * Test case There is no specific test case for the update, the changelog includes some specific bugs which have their own test case, otherwise it's important to get testing/feedback from users on desktop & server, using IPv4, IPv6, VPN, wifi, eth connections, etc. * Regression potential The update is non trivial, there are several changes are IPv6 and DNS (especially in the context of VPNs) handling so it would be good to give those extra testing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1809132/+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 1796622] Re: NetworkManager IPv6 DAD lifetime behavior introduce security risk
SRUing the newer version failed since it changed behaviour in some configuration which created issue for existing users. There isn't anyone currently working on resolving those issues so it's more realistic to untarget from Bionic. If the problem really needs to be resolved in that serie best to go through the rls-bb-incoming nomination process again. ** Changed in: network-manager (Ubuntu Cosmic) Status: New => Won't Fix ** Changed in: network-manager (Ubuntu Cosmic) Assignee: Till Kamppeter (till-kamppeter) => (unassigned) ** Changed in: network-manager (Ubuntu Bionic) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1796622 Title: NetworkManager IPv6 DAD lifetime behavior introduce security risk Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Won't Fix Status in network-manager source package in Cosmic: Won't Fix Status in network-manager source package in Disco: Fix Released Bug description: Description: When performing IPv6 certification test, two DAD test cases (3.2.5c and d) check the remaining lifetime feature of the IPv6 packets. The Network trace shows that the remaining lifetime becomes infinite when running these test cases. Hence when running in IPv6 environment with Network Manager enabled, there is a risk of packets travelling in network which has valid lifetime always. If these packets are snooped by a hacker he can reply to these packets and they can send legitimate packets which are actually not. According to https://tools.ietf.org/search/rfc4862, page 19: "The above rules address a specific denial-of-service attack in which a bogus advertisement could contain prefixes with very small Valid Lifetimes. Without the above rules, a single unauthenticated advertisement containing bogus Prefix Information options with short Valid Lifetimes could cause all of a node's addresses to expire prematurely. The above rules ensure that legitimate advertisements (which are sent periodically) will "cancel" the short Valid Lifetimes before they actually take effect." Other notes: - 2 test cases pass without NetworkManager. - Tested with different Linux Desktop Distributions, as long as NetworkManager is running, those DAD test cases fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1796622/+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 942856] Re: NetworkManager does not support AES-encrypted private keys for WPA 802.1x authentication
Untargetting for Bionic, SRUing the current version failed since it
changed DNS behaviour in some configuration which created issue for
existing users. There isn't anyone currently working on resolving those
issues so it's more realistic to untarget from Bionic.
If the problem really needs to be resolved in that serie best to go
through the rls-bb-incoming nomination process again.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/942856
Title:
NetworkManager does not support AES-encrypted private keys for WPA
802.1x authentication
Status in NetworkManager:
Confirmed
Status in network-manager package in Ubuntu:
Fix Released
Bug description:
* Impact
Selecting AES-{192,256}-CBC keys to connect isn't working
* Test case
1. Start with a working (cleartext or DES-3) private key/cert for a network.
Set up a connection and verify that everything works.
2. Re-encrypt the key with AES-256 with this command: "openssl rsa -in
working-key.pem -out aes-key.pem -aes256" (the output should have a line
starting with "DEK-Info: AES-256-CBC,")
3. Delete the settings for the test network and attempt to reconnect using
the new key.
That should work
* Regression potential
That's new code for an extra type of keys, it shouldn't impact
existing options
--
NetworkManager does not appear to support private keys encrypted with
AES. At the very least, it will not validate such a key in nm-util
when setting up a WPA 802.1x TLS wifi connection.
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/942856/+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
Re: [Touch-packages] [Bug 1866681] Re: [HP Pavilion dv9000] Mute toggles on/off while plugged into the headphone/speaker jack (19.04+)
Alrighty, so, I installed Xubuntu 16.04. `uname -or` outputs: 4.4.0-21-generic GNU/Linux and `pulseaudio --version` outputs: pulseaudio 8.0 In AlsaMixer, "Auto-Mute Mode" is set to "Enabled", and the audio works perfectly exactly as expected. This is definitely something that started happening in the 19.04 versions. On 3/12/20, Kai-Heng Feng wrote: > Can you please test older kernels like 4.15? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1866681 > > Title: > [HP Pavilion dv9000] Mute toggles on/off while plugged into the > headphone/speaker jack (19.04+) > > Status in alsa-driver package in Ubuntu: > New > Status in linux package in Ubuntu: > Confirmed > Status in pulseaudio package in Ubuntu: > New > > Bug description: > I'm on an HP Pavilion dv9000 (https://www.cnet.com/products/hp- > pavilion-dv9000/specs/) built many years ago. > > > Whenever I'm using any distro that's based on Ubuntu which was published > from Version 19.04 onwards, I've been having a major issue with the mute > button toggling on and off whenever I have something plugged into the audio > out jack. I know that it's not the fault of XFCE, because I also use the > latest version of Manjaro with XFCE on this same computer, and it works > fine. I also know it's not any Red Hat-based distro, because I use Stella > (which is a remix of CentOS 6) also on this exact same computer, and it also > works fine. Qubes, Mageia, and Fedora 31 also work perfectly fine and don't > have this issue. > > My "lsb-release" is: > DISTRIB_ID=Ubuntu > DISTRIB_RELEASE=19.10 > DISTRIB_CODENAME=eoan > DISTRIB_DESCRIPTION="Ubuntu 19.10" > > and "apt-cache policy pulseaudio" outputs: > pulseaudio: > Installed: 1:13.0-1ubuntu1.1 > Candidate: 1:13.0-1ubuntu1.1 > Version table: >*** 1:13.0-1ubuntu1.1 500 > 500 http://us.archive.ubuntu.com/ubuntu eoan-updates/main amd64 > Packages > 100 /var/lib/dpkg/status >1:13.0-1ubuntu1 500 > 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages > > I've uploaded a short video of the problem that I recorded with my phone > here: > https://www.youtube.com/watch?v=GXaHXQA-5uQ > > > The problem appears with Kali 2019 and 2020, Peppermint 19.04, Lubuntu > 19.04, Xubuntu 19.04, and Sparky 5.10 and 2020.02. > > > I've checked pretty much everything I can think of. There's a log for my > ALSA help diagnostics results on my current computer (which works properly > with 18.04) at: > http://alsa-project.org/db/?f=4859b85cd7fc32e7f01f8df63591b5a43dbf6829 > > > the result output of lspci is: > [code]00:00.0 RAM memory: NVIDIA Corporation C51 Host Bridge (rev a2) > 00:00.1 RAM memory: NVIDIA Corporation C51 Memory Controller 0 (rev a2) > 00:00.2 RAM memory: NVIDIA Corporation C51 Memory Controller 1 (rev a2) > 00:00.3 RAM memory: NVIDIA Corporation C51 Memory Controller 5 (rev a2) > 00:00.4 RAM memory: NVIDIA Corporation C51 Memory Controller 4 (rev a2) > 00:00.5 RAM memory: NVIDIA Corporation C51 Host Bridge (rev a2) > 00:00.6 RAM memory: NVIDIA Corporation C51 Memory Controller 3 (rev a2) > 00:00.7 RAM memory: NVIDIA Corporation C51 Memory Controller 2 (rev a2) > 00:02.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1) > 00:03.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1) > 00:04.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1) > 00:09.0 RAM memory: NVIDIA Corporation MCP51 Host Bridge (rev a2) > 00:0a.0 ISA bridge: NVIDIA Corporation MCP51 LPC Bridge (rev a3) > 00:0a.1 SMBus: NVIDIA Corporation MCP51 SMBus (rev a3) > 00:0a.3 Co-processor: NVIDIA Corporation MCP51 PMU (rev a3) > 00:0b.0 USB controller: NVIDIA Corporation MCP51 USB Controller (rev a3) > 00:0b.1 USB controller: NVIDIA Corporation MCP51 USB Controller (rev a3) > 00:0d.0 IDE interface: NVIDIA Corporation MCP51 IDE (rev f1) > 00:0e.0 IDE interface: NVIDIA Corporation MCP51 Serial ATA Controller (rev > f1) > 00:0f.0 IDE interface: NVIDIA Corporation MCP51 Serial ATA Controller (rev > f1) > 00:10.0 PCI bridge: NVIDIA Corporation MCP51 PCI Bridge (rev a2) > 00:10.1 Audio device: NVIDIA Corporation MCP51 High Definition Audio (rev > a2) > 00:14.0 Bridge: NVIDIA Corporation MCP51 Ethernet Controller (rev a3) > 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 > [Athlon64/Opteron] HyperTransport Technology Configuration > 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 > [Athlon64/Opteron] Address Map > 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 > [Athlon64/Opteron] DRAM Controller > 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 > [Athlon64/Opteron] Miscellaneous Control > 03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4311 > 802.11b/g WLAN (rev 01) > 05:00.0 VGA compatible controller: NVIDIA Corporation G73M [GeForce Go > 7600]
[Touch-packages] [Bug 1850932] Re: [SRU] Backport 2.62.4-1
I ran glib2.0/eoan/i386 myself locally, and it passed: autopkgtest [14:37:57]: summary buildPASS (superficial) build-static PASS (superficial) installed-tests PASS flakyPASS qemu-system-x86_64: terminating on signal 15 from pid 2692138 (/usr/bin/python3) I'm not sure what happens on the production infrastructure, but given that this works in focal and that eoan is "only" an interim release, I'd say this SRU could probably be released ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1850932 Title: [SRU] Backport 2.62.4-1 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Eoan: Fix Committed Bug description: [ Description ] I'm creating this bug report to have a place to describe the proposed backport of glib2.0 2.62.4-1 from focal. One purpose of this backport is to fix bug #1844853. But there are several other changes. Here's the diff of NEWS: +Overview of changes in GLib 2.62.4 +== + +* Apply recursion depth limits to variants in D-Bus messages (!1290) + +* Bugs fixed: + - #1938 GDateTime doesn't support leap seconds + - !1240 Backport !1233 “gdatetime: Handle leap seconds in ISO8601 dates” +to glib-2-62 + - !1257 Backport !1232 “kqueue: Do not return early from _kqsub_cancel” +to glib-2-62 + - !1266 Backport !1265 “build: don't check for protected visibility” to +glib-2-62 + - !1276 Backport !1274 “trash portal: Don't follow symlinks” to glib-2-62 + - !1290 Backport !1201 “gdbusmessage: Limit recursion of variants in +D-Bus messages” to glib-2-62 + +Overview of changes in GLib 2.62.3 +== + +* Use `poll()` in `g_spawn_sync()` rather than `select()`, which is subject to + FD limits (#954) + +* Fix undefined behaviour with `g_utf8_find_prev_char()` (#1917) + +* Bugs fixed: + - #954 The g_spawn_sync() function uses select() which has limitations + - #1318 rare failure in gdbus-peer test: invalid uninstantiatable type '(null)' in cast to 'GDBusServer' + - #1897 glib 2.62.0 fails test 'test_writev_no_vectors' wih gcc7 + - #1903 use-after-free in mimeapps test causes intermittent segfault during testing + - #1916 objcopy not used from cross-compilation file in GIO tests + - #1917 Test utf8-pointer fails with static build, LTO, optimisations, and new GCC + - !1174 Backport !1164 “use-after-free fix in mimeapps test” to glib-2-62 + - !1184 Backport !1173 “gvariant: Limit recursion in g_variant_parse()” to glib-2-62 + - !1194 Backport !1176, !1183, !1188, !1191 to `glib-2-62` + - !1203 Backport !1192, !1193, !1197 Fixes for gdbus-peer tests to glib-2-62 + - !1207 Backport !1206 “goption: Relax assertion to avoid being broken by kdeinit5” to glib-2-62 + - !1215 [2.62] gdbus-peer: Specifically listen on 127.0.0.1 + - !1219 Backport !1218 “gdb: Fix GHashTable pretty printer off-by-one error” + - !1222 Backport !1221 “Add NOTE_REVOKE to the list of the monitoring events” to glib-2-62 + - !1228 Backport !1199 “gunicode: Fix UB in gutf8.c and utf8-pointer test” to glib-2-62 + + +Overview of changes in GLib 2.62.2 +== + +* Bugs fixed: + - #1896 Use after free when calling g_dbus_connection_flush_sync() in a dedicated thread + - !1154 Backport !1152 “gwinhttpvfs: Handle g_get_prgname() returning NULL” to glib-2-62 + - !1156 Backport !1146 Solaris fixes to glib-2-62 This release can be considered to be tested under https://wiki.ubuntu.com/StableReleaseUpdates/GNOME There are patches from the upstream master branch rather than this stable release: + Add-a-test-for-GDBusServer-authentication.patch + gdbus-server-auth-test-Create-temporary-directory-for-Uni.patch + gdbus-server-auth-test-Include-gcredentialsprivate.h.patch + Make-ld-executable-configurable.patch They are sensible backports which I hope are appropriate for SRU. [ QA ] The testsuite fixes will verify themselves during the build and autopkgtest. For the rest of the fixes, please exercise the desktop thoroughly. Log in, log out, run many applications and make sure there are no regressions. [ Regression potential ] test fixes> Build failures or autopkgtest failures. GLib is a central desktop library. Regressions could break any part of the desktop - so QA is important, the SRU exception notwithstanding. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1850932/+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 1866890] Re: audio card not detected after upgrade to 20.04 (Only Dummy Output appears)
*** This bug is a duplicate of bug 1860697 *** https://bugs.launchpad.net/bugs/1860697 ** This bug has been marked a duplicate of bug 1860697 Sound doesn't work on Lenovo X1 Carbon 7th with 20.04 -- 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/1866890 Title: audio card not detected after upgrade to 20.04 (Only Dummy Output appears) Status in alsa-driver package in Ubuntu: New Bug description: Since upgrading to 20.04 the sound card is no longer detected. This means that I can only see "Dummy Output" in the sound settings. The audio works if I use Bluetooth headphones but not if I try to use the speakers or the 3.5mm headphone jack. My machine is a Lenovo ThinkPad X1 Yoga (4th gen). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1866890/+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 1867766] Re: Namespace prefix sodipodi on namedview is not defined
** Branch linked: lp:~osomon/ubuntu-themes/scavenge-preserve-namespaces -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1867766 Title: Namespace prefix sodipodi on namedview is not defined Status in librsvg package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: New Bug description: [Summary] Since the package "gir1.2-rsvg-2.0:amd64" been upgraded from 2.46.4-1ubuntu1 to 2.48.0-1 in Focal's daily build, ubiquity will crash as attached crash log. [Steps to reproduce] 1. Boot with OEM mode, 2. Finish the 1st stage 3. Reboot 4. Boot into OOBE(oem-config) [Expected result] Should start oobe without any error. [Actual result] The error message 『The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again.』shown on the screen. [Failure rate] 100% [Additional information] No idea why, but some "nm-signal-*-secure" images will fail in Gtk.IconTheme().lookup_icon(n, 22, 0).load_icon(), and below error message will show: " Gtk-WARNING **: 18:23:31.380: Could not load a pixbuf from icon theme. This may indicate that pixbuf loaders or the mime database could not be found. gi.repository.GLib.GError: rsvg-error-quark: XML parse error: error code=201 (3) in (null):40:466: Namespace prefix sodipodi on namedview is not defined " To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1867766/+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 1867784] Re: "systemctl status ..." in Focal does not show any process output
Never mind. My fault. The journal was gone, so nothing could be shown. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1867784 Title: "systemctl status ..." in Focal does not show any process output Status in systemd package in Ubuntu: Invalid Bug description: Software versions: # lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 # apt-cache policy systemd systemd: Installed: 244.3-1ubuntu1 Candidate: 244.3-1ubuntu1 Version table: *** 244.3-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status When I issue "systemctl status apache2" (or for any other service for that matter) in Focal, the last few lines of output are not shown any more: # systemctl status apache2 ● apache2.service - The Apache HTTP Server Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor prese> Drop-In: /etc/systemd/system/apache2.service.d └─override.conf Active: active (running) since Tue 2020-03-17 13:34:42 CET; 1h 43min ago Docs: https://httpd.apache.org/docs/2.4/ Main PID: 283994 (apache2) Tasks: 55 (limit: 9451) Memory: 27.3M CGroup: /system.slice/apache2.service ├─283994 /usr/sbin/apache2 -k start ├─283997 /usr/sbin/apache2 -k start └─283998 /usr/sbin/apache2 -k start # With Bionic (18.04), the last few log lines were shown as described in the systemctl man page: #systemctl status apache2 ● apache2.service - The Apache HTTP Server Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enab Drop-In: /lib/systemd/system/apache2.service.d └─apache2-systemd.conf /etc/systemd/system/apache2.service.d └─override.conf Active: active (running) since Tue 2020-03-03 23:01:13 CET; 1 weeks 6 days ago Process: 1255 ExecReload=/usr/sbin/apachectl graceful (code=exited, status=0/SUCCE Main PID: 11522 (/usr/sbin/apach) Tasks: 15 (limit: 4915) CGroup: /system.slice/apache2.service ├─ 1280 /usr/sbin/apache2 -k start ├─ 6459 /usr/sbin/apache2 -k start └─11522 /usr/sbin/apache2 -k start Mar 13 06:25:27 fatty.xy.de systemd[1]: Reloading The Apache HTTP Server. Mar 13 06:25:27 fatty.xy.de systemd[1]: Reloaded The Apache HTTP Server. Mar 14 06:25:27 fatty.xy.de systemd[1]: Reloading The Apache HTTP Server. Mar 14 06:25:27 fatty.xy.de systemd[1]: Reloaded The Apache HTTP Server. Mar 15 06:25:27 fatty.xy.de systemd[1]: Reloading The Apache HTTP Server. Mar 15 06:25:27 fatty.xy.de systemd[1]: Reloaded The Apache HTTP Server. Mar 16 06:25:28 fatty.xy.de systemd[1]: Reloading The Apache HTTP Server. Mar 16 06:25:28 fatty.xy.de systemd[1]: Reloaded The Apache HTTP Server. Mar 17 06:25:27 fatty.xy.de systemd[1]: Reloading The Apache HTTP Server. Mar 17 06:25:27 fatty.xy.de systemd[1]: Reloaded The Apache HTTP Server. # I do not know if this was an upstream systemd change, however it seems wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1867784/+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 1866194] Re: After connecting an external output device (USB audio interface, Bluetooth speaker...), it shows up in the sound output options but the sound keeps being emitted fro
Daniel, could you have a look there to see if that's a known/new issue and if maybe you think is something we should rls target? ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => High ** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- 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/1866194 Title: After connecting an external output device (USB audio interface, Bluetooth speaker...), it shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu version: focal dev Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 Device CID: 201704-25503 Steps to reproduce: 1. Go to Bluetooth settings panel 2. Pair a BT device 3. Make sure it's marked as Connected, and go to the Sound settings 4. Make sure it's the one selected as "Output device" 5. Click "Test" -> the test sound outputs from the internal laptop speakers (NOK) 6. Select "Speakers - Built-in Audio" as Output device and click "Test" -> the test sound outputs from the internal laptop speakers (OK) 7. Try to switch back to the BT device and click Test -> same result as in step 5 Tested with 2 different BT devices (one headset and one speaker) Attached are btmon logs captured during the procedure described above, and pactl logs capture after step 7. Up to this morning, it was harder to connect the BT device, but once connected, the sound would output on it as expected. Now, the BT connection seems to work better, but I can't output the sound to the BT device... I tried to reboot the device, and also to suspend/resume, but in each case, the BT device can connect back, but the sound is still output from the internal laptop speakers, even when the BT device is selected in the Sound settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 1566 F pulseaudio /dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio /dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 22:15:50 2020 InstallationDate: Installed on 2020-01-17 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1866194/+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 430203] Re: bell.ogg is unresponsive (outside HIG response times) [regression]
** Changed in: metacity (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-sounds in Ubuntu. https://bugs.launchpad.net/bugs/430203 Title: bell.ogg is unresponsive (outside HIG response times) [regression] Status in Metacity: Fix Released Status in metacity package in Ubuntu: Fix Released Status in ubuntu-sounds package in Ubuntu: Fix Released Status in metacity package in Fedora: Fix Released Bug description: Binary package hint: ubuntu-sounds The instantaneous beep in the default Ubuntu 9.10 preview install has been switched to a slow firing, and slow to repeat sound: /usr/share/sounds/ubuntu/stereo/bell.ogg the easiest way to cause this sound to be played in anger is to open a Terminal (eg. gnome-terminal) and hit the backspace. There is an audible delay in the latency until the sound is played and approximately 1 second until the sound is replayed (despite the key repeat likely firing at over 25 Hz. Viewing the Vorbis file with ogginfo and mhWavedit shows that it is is approximately 900 milliseconds in length! $ ogginfo /usr/share/sounds/ubuntu/stereo/bell.ogg | grep Playback Playback length: 0m:00.882s The file consists of ~50 milliseconds of silence, ~200 milliseconds of actual sound and then a further ~650 milliseconds of silence. Ideally the white space should be trimmed to the *absolute maximum*. The sound needs to play *immediately* to meet the requirements set of the HIG for interactive feedback (100 millisecond upper bound). If further delays are being introduced by the Vorbis loading then this sound (which should be immediate and responsive) should probably be converted to an uncompressed format. Failing that, the sound could be reverted to the previous short and quick 'bip' sound used previously. To manage notifications about this bug go to: https://bugs.launchpad.net/metacity/+bug/430203/+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 486154] Re: System beep broken in Karmic despite heroic efforts to fix it
Wontfix. ** Changed in: metacity (Ubuntu) Status: Triaged => Invalid -- 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/486154 Title: System beep broken in Karmic despite heroic efforts to fix it Status in Metacity: New Status in libcanberra package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Confirmed Status in metacity package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Bug description: Between Jaunty and Karmic, a number of changes were made to keep the PC speaker from beeping. As part of this, system bell events are now captured by metacity, which uses libcanberra to play a sound. For users without speakers, this fails to be useful. The current setup makes restoring the old behavior extremely difficult. The absolute show stopper is that metacity traps audible system bell events. This behavior is, as best we can tell, not configurable. The attached patch keeps metacity from capturing system bell events. It also removes the sound playback capability. As Lucid will be using pulse audio's module-x11-bell to play sounds for system bell events, it is not necessary for this capability to be in metacity. Additionally, this removes the discrepancy between metacity's and compiz's handling of system bell events. There are several other difficulties in enabling the system bell: 1) Even if it is taken out of the blacklist, the pcspkr module may not load properly. Another modprobe may be necessary to get it loaded. See bug #398161. 2) Something in Gnome's startup does the equivalent of `xset b off`, so `xset b on` must be run on every login. (Note that bug #280767 keeps you from setting the bell volume with xset.) 3) A number of settings in gnome-terminal and gconf may keep the shell from sounding system bell events. Comments #28, #34, and #50 give more detailed summaries of the various problems. To manage notifications about this bug go to: https://bugs.launchpad.net/metacity/+bug/486154/+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 942856] Re: NetworkManager does not support AES-encrypted private keys for WPA 802.1x authentication
** No longer affects: network-manager (Ubuntu Bionic)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/942856
Title:
NetworkManager does not support AES-encrypted private keys for WPA
802.1x authentication
Status in NetworkManager:
Confirmed
Status in network-manager package in Ubuntu:
Fix Released
Bug description:
* Impact
Selecting AES-{192,256}-CBC keys to connect isn't working
* Test case
1. Start with a working (cleartext or DES-3) private key/cert for a network.
Set up a connection and verify that everything works.
2. Re-encrypt the key with AES-256 with this command: "openssl rsa -in
working-key.pem -out aes-key.pem -aes256" (the output should have a line
starting with "DEK-Info: AES-256-CBC,")
3. Delete the settings for the test network and attempt to reconnect using
the new key.
That should work
* Regression potential
That's new code for an extra type of keys, it shouldn't impact
existing options
--
NetworkManager does not appear to support private keys encrypted with
AES. At the very least, it will not validate such a key in nm-util
when setting up a WPA 802.1x TLS wifi connection.
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/942856/+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 1855893] Re: Properly let PCM leave suspended state when hardware doesn't support PCM resume
** Changed in: pulseaudio (Ubuntu Bionic) Status: In Progress => Won't Fix -- 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/1855893 Title: Properly let PCM leave suspended state when hardware doesn't support PCM resume Status in HWE Next: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Won't Fix Bug description: [Impact] Headset Mic plugged into Dell WD19TB dock stops working after suspend/resume. [Fix] According to alia-lib's document, to make PCM properly leave suspended state, we only use snd_pcm_resume() if hardware support PCM resume. For hardware that doesn't support PCM resume, like snd-usb-audio on WD19TB dock, we should use snd_pcm_prepare(), snd_pcm_drop() or snd_pcm_drain() to make device leave suspended state. This patch defaults to use snd_pcm_drop() to achieve the goal. [Test] 1. See if microphone on snd-usb-audio works in gnome-control-center/cheese. 2. Suspend/resume. 3. See if microphone still works in those apps. I can the issue is fixed after each suspend/resume cycle. [Regression Potential] Low. This fix makes PCM suspend/resume more reliable. No functional change intended. I also don't find any regression during some smoke test. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1855893/+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 1867766] Re: Namespace prefix sodipodi on namedview is not defined
The invalid SVGs appear to be generated by the scavenge.py script in ubuntu-themes. ** Also affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1867766 Title: Namespace prefix sodipodi on namedview is not defined Status in librsvg package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: New Bug description: [Summary] Since the package "gir1.2-rsvg-2.0:amd64" been upgraded from 2.46.4-1ubuntu1 to 2.48.0-1 in Focal's daily build, ubiquity will crash as attached crash log. [Steps to reproduce] 1. Boot with OEM mode, 2. Finish the 1st stage 3. Reboot 4. Boot into OOBE(oem-config) [Expected result] Should start oobe without any error. [Actual result] The error message 『The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again.』shown on the screen. [Failure rate] 100% [Additional information] No idea why, but some "nm-signal-*-secure" images will fail in Gtk.IconTheme().lookup_icon(n, 22, 0).load_icon(), and below error message will show: " Gtk-WARNING **: 18:23:31.380: Could not load a pixbuf from icon theme. This may indicate that pixbuf loaders or the mime database could not be found. gi.repository.GLib.GError: rsvg-error-quark: XML parse error: error code=201 (3) in (null):40:466: Namespace prefix sodipodi on namedview is not defined " To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1867766/+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 1867784] [NEW] "systemctl status ..." in Focal does not show any process output
Public bug reported: Software versions: # lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 # apt-cache policy systemd systemd: Installed: 244.3-1ubuntu1 Candidate: 244.3-1ubuntu1 Version table: *** 244.3-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status When I issue "systemctl status apache2" (or for any other service for that matter) in Focal, the last few lines of output are not shown any more: # systemctl status apache2 ● apache2.service - The Apache HTTP Server Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor prese> Drop-In: /etc/systemd/system/apache2.service.d └─override.conf Active: active (running) since Tue 2020-03-17 13:34:42 CET; 1h 43min ago Docs: https://httpd.apache.org/docs/2.4/ Main PID: 283994 (apache2) Tasks: 55 (limit: 9451) Memory: 27.3M CGroup: /system.slice/apache2.service ├─283994 /usr/sbin/apache2 -k start ├─283997 /usr/sbin/apache2 -k start └─283998 /usr/sbin/apache2 -k start # With Bionic (18.04), the last few log lines were shown as described in the systemctl man page: #systemctl status apache2 ● apache2.service - The Apache HTTP Server Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enab Drop-In: /lib/systemd/system/apache2.service.d └─apache2-systemd.conf /etc/systemd/system/apache2.service.d └─override.conf Active: active (running) since Tue 2020-03-03 23:01:13 CET; 1 weeks 6 days ago Process: 1255 ExecReload=/usr/sbin/apachectl graceful (code=exited, status=0/SUCCE Main PID: 11522 (/usr/sbin/apach) Tasks: 15 (limit: 4915) CGroup: /system.slice/apache2.service ├─ 1280 /usr/sbin/apache2 -k start ├─ 6459 /usr/sbin/apache2 -k start └─11522 /usr/sbin/apache2 -k start Mar 13 06:25:27 fatty.xy.de systemd[1]: Reloading The Apache HTTP Server. Mar 13 06:25:27 fatty.xy.de systemd[1]: Reloaded The Apache HTTP Server. Mar 14 06:25:27 fatty.xy.de systemd[1]: Reloading The Apache HTTP Server. Mar 14 06:25:27 fatty.xy.de systemd[1]: Reloaded The Apache HTTP Server. Mar 15 06:25:27 fatty.xy.de systemd[1]: Reloading The Apache HTTP Server. Mar 15 06:25:27 fatty.xy.de systemd[1]: Reloaded The Apache HTTP Server. Mar 16 06:25:28 fatty.xy.de systemd[1]: Reloading The Apache HTTP Server. Mar 16 06:25:28 fatty.xy.de systemd[1]: Reloaded The Apache HTTP Server. Mar 17 06:25:27 fatty.xy.de systemd[1]: Reloading The Apache HTTP Server. Mar 17 06:25:27 fatty.xy.de systemd[1]: Reloaded The Apache HTTP Server. # I do not know if this was an upstream systemd change, however it seems wrong. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: focal status systemd -- 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/1867784 Title: "systemctl status ..." in Focal does not show any process output Status in systemd package in Ubuntu: New Bug description: Software versions: # lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 # apt-cache policy systemd systemd: Installed: 244.3-1ubuntu1 Candidate: 244.3-1ubuntu1 Version table: *** 244.3-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status When I issue "systemctl status apache2" (or for any other service for that matter) in Focal, the last few lines of output are not shown any more: # systemctl status apache2 ● apache2.service - The Apache HTTP Server Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor prese> Drop-In: /etc/systemd/system/apache2.service.d └─override.conf Active: active (running) since Tue 2020-03-17 13:34:42 CET; 1h 43min ago Docs: https://httpd.apache.org/docs/2.4/ Main PID: 283994 (apache2) Tasks: 55 (limit: 9451) Memory: 27.3M CGroup: /system.slice/apache2.service ├─283994 /usr/sbin/apache2 -k start ├─283997 /usr/sbin/apache2 -k start └─283998 /usr/sbin/apache2 -k start # With Bionic (18.04), the last few log lines were shown as described in the systemctl man page: #systemctl status apache2 ● apache2.service - The Apache HTTP Server Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enab Drop-In: /lib/systemd/system/apache2.service.d └─apache2-systemd.conf /etc/systemd/system/apache2.service.d └─override.conf Active: active (running) since Tue 2020-03-03 23:01:13 CET; 1 weeks 6 days ago Process: 1255 ExecReload=/usr/sbin/apachectl graceful
[Touch-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
Hello. I am wondering why this only applies to certain models of the X1C7. I had to make an additional file to get my Mic working: LENOVO-20QDCTO1WW-ThinkPadX1Carbon7th-20QDCTO1WW.conf Is this something I should report upstream? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+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 1863239] Re: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group
An additional remark: If a Focal system is booted with the printer plugged in and turned on, the group ownership gets correctly set to "lp", but if the printer is only plugged in and/or turned on after boot, it gets "audio" group ownership. -- 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/1863239 Title: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group Status in libmtp package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Status in systemd package in Ubuntu: New Status in udev package in Ubuntu: New Bug description: When testing HPLIP I found out that CUPS backends can access my printer only when they are running as root, when they are running as the special user lp, as it is usually the case, they cannot access the printer. So I tried to find out why and saw that the /dev/bus/usb/*/* device file for the printer has group ownership "audio" and not "lp": till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ ll /dev/bus/usb/*/* crw-rw-r-- 1 root root189, 0 Feb 11 14:17 /dev/bus/usb/001/001 crw-rw-r-- 1 root root189, 2 Feb 11 14:17 /dev/bus/usb/001/003 crw-rw-r-- 1 root root189, 3 Feb 11 14:17 /dev/bus/usb/001/004 crw-rw-r-- 1 root plugdev 189, 4 Feb 14 12:23 /dev/bus/usb/001/005 crw-rw-r-- 1 root root189, 5 Feb 11 14:17 /dev/bus/usb/001/006 crw-rw+ 1 root audio 189, 62 Feb 14 12:37 /dev/bus/usb/001/063 crw-rw-r-- 1 root root189, 128 Feb 11 14:17 /dev/bus/usb/002/001 crw-rw-r-- 1 root root189, 130 Feb 13 09:38 /dev/bus/usb/002/003 till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ The printer is the device /dev/bus/usb/001/063: till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ lsusb Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch sensor Bus 001 Device 063: ID 03f0:7a12 HP, Inc HP OfficeJet Pro 8730 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ There must be a bug somewhere in the UDEV rules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1863239/+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 1867766] Re: Namespace prefix sodipodi on namedview is not defined
As suggested by seb128, the ubiquity autopkgtests fail with the same error. ** Changed in: librsvg (Ubuntu) Status: New => Confirmed ** Changed in: librsvg (Ubuntu) Importance: Undecided => Critical ** Changed in: librsvg (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1867766 Title: Namespace prefix sodipodi on namedview is not defined Status in librsvg package in Ubuntu: Confirmed Bug description: [Summary] Since the package "gir1.2-rsvg-2.0:amd64" been upgraded from 2.46.4-1ubuntu1 to 2.48.0-1 in Focal's daily build, ubiquity will crash as attached crash log. [Steps to reproduce] 1. Boot with OEM mode, 2. Finish the 1st stage 3. Reboot 4. Boot into OOBE(oem-config) [Expected result] Should start oobe without any error. [Actual result] The error message 『The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again.』shown on the screen. [Failure rate] 100% [Additional information] No idea why, but some "nm-signal-*-secure" images will fail in Gtk.IconTheme().lookup_icon(n, 22, 0).load_icon(), and below error message will show: " Gtk-WARNING **: 18:23:31.380: Could not load a pixbuf from icon theme. This may indicate that pixbuf loaders or the mime database could not be found. gi.repository.GLib.GError: rsvg-error-quark: XML parse error: error code=201 (3) in (null):40:466: Namespace prefix sodipodi on namedview is not defined " To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1867766/+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 1867766] Re: Namespace prefix sodipodi on namedview is not defined
I bet this is caused by this upstream change in librsvg: - Librsvg's XML parser now supports namespaces (xmlns), and is stricter than before about it. Files may fail to parse if there are attributes or elements with namespace prefixes (e.g. foo:bar instead of plain bar), but without a corresponding namespace declaration (e.g. xmlns:foo="http://example.com/foo;). This may happen especially with incorrectly-written SVGs that use xlink:href or xi:include attributes without the corresponding namespace declarations. If you run into this, just add the following to your toplevel SVG element: http://www.w3.org/2000/svg; xmlns:xlink="http://www.w3.org/1999/xlink; xmlns:xi="http://www.w3.org/2001/XInclude;> ^ these ones The nm-signal-*.svg icons in /usr/share/icons/ubuntu-mono-light/status/22 use sodipodi: prefixed attributes (exported by inkscape) without the corresponding namespace declaration (http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1867766 Title: Namespace prefix sodipodi on namedview is not defined Status in librsvg package in Ubuntu: Confirmed Bug description: [Summary] Since the package "gir1.2-rsvg-2.0:amd64" been upgraded from 2.46.4-1ubuntu1 to 2.48.0-1 in Focal's daily build, ubiquity will crash as attached crash log. [Steps to reproduce] 1. Boot with OEM mode, 2. Finish the 1st stage 3. Reboot 4. Boot into OOBE(oem-config) [Expected result] Should start oobe without any error. [Actual result] The error message 『The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again.』shown on the screen. [Failure rate] 100% [Additional information] No idea why, but some "nm-signal-*-secure" images will fail in Gtk.IconTheme().lookup_icon(n, 22, 0).load_icon(), and below error message will show: " Gtk-WARNING **: 18:23:31.380: Could not load a pixbuf from icon theme. This may indicate that pixbuf loaders or the mime database could not be found. gi.repository.GLib.GError: rsvg-error-quark: XML parse error: error code=201 (3) in (null):40:466: Namespace prefix sodipodi on namedview is not defined " To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1867766/+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 1352975] Re: GUI symbol for Wi-fi in 14.10 shows not connected even when connected
Closing this now due to: 1) Upstream bug closed "RESOLVED OBSOLETE" on 2014-04-26 as issue only seen on buggy version of network-manager 2) Last report of issue was in comment #12 over 5 years ago 3) No response to comment #14 after over 6 months 4) Issue reported only against Ubuntu 14.10, EOL since 2015-07-23 ** Changed in: network-manager (Ubuntu) Status: Incomplete => Fix Released ** Changed in: hundredpapercuts Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1352975 Title: GUI symbol for Wi-fi in 14.10 shows not connected even when connected Status in One Hundred Papercuts: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in wifi-radar package in Ubuntu: Invalid Bug description: Using Ubuntu 14.10 alpha 2 with all updates. Clean install. Network manager 0.9.8.8-0ubuntu23 Wifi-card: Intel Wireless 7260 (Rev 73) The Wi-fi symbol in the top right corner does not indicate that it is connected to Wi-fi even when it is connected. (It shows a question mark instead) Expected behavior is that it would show signal strength, or at the very least "make it grey" and remove the question mark. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: network-manager 0.9.8.8-0ubuntu23 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.5-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Aug 5 17:42:57 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-08-05 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140730) IpRoute: default via 192.168.0.1 dev wlan0 proto static 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.110 metric 9 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 18b6987c1-3f15-4b41-be88-ea9f5ae9eff6 802-3-ethernet1407252000 ti. 05. aug. 2014 kl. 17.20 +0200 yes no /org/freedesktop/NetworkManager/Settings/1 Diskokatt 5Ghz6a2433b7-9e20-4c4a-9c9d-455fee3505ef 802-11-wireless 1407253201 ti. 05. aug. 2014 kl. 17.40 +0200 yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1352975/+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 1867774] [NEW] PCI/internal sound card not detected
Public bug reported: Two days ago the audio of my laptop was still working fine. Between then and now I did a kernel and gnome-shell update (those are the ones I remember). Now my sound settings do not show any devices beyond the dummy ones. I have Ubuntu 19.10 on my Thinkpad X1 Yoga and I've tried these https://itsfoss.com/fix-sound-ubuntu-1304-quick-tip/ and https://help.ubuntu.com/community/SoundTroubleshooting things Here are some maybe relevant packages ``` apt-cache policy alsa-base pulseaudio alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu eoan/main i386 Packages 100 /var/lib/dpkg/status pulseaudio: Installed: 1:13.0-1ubuntu1.1 Candidate: 1:13.0-1ubuntu1.1 Version table: *** 1:13.0-1ubuntu1.1 500 500 http://de.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages ``` Here my lspci, which as you can see includes a audio device ``` 00:00.0 Host bridge: Intel Corporation Device 3e34 (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (Whiskey Lake) (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP Thermal Controller (rev 11) 00:13.0 Serial controller: Intel Corporation Cannon Point-LP Integrated Sensor Hub (rev 11) 00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI Controller (rev 11) 00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 11) 00:14.3 Network controller: Intel Corporation Cannon Point-LP CNVi [Wireless-AC] (rev 11) 00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #0 (rev 11) 00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #1 (rev 11) 00:16.0 Communication controller: Intel Corporation Cannon Point-LP MEI Controller #1 (rev 11) 00:1c.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #1 (rev f1) 00:1d.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #9 (rev f1) 00:1d.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #13 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 11) 00:1f.3 Audio device: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) 00:1f.4 SMBus: Intel Corporation Cannon Point-LP SMBus Controller (rev 11) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP SPI Controller (rev 11) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (6) I219-V (rev 11) 02:00.0 Wireless controller [0d40]: Intel Corporation XMM7360 LTE Advanced Modem (rev 01) 03:00.0 Non-Volatile memory controller: Sandisk Corp Device 5006 05:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 06:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 06:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 06:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 06:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 07:00.0 System peripheral: Intel Corporation JHL6540 Thunderbolt 3 NHI (C step) [Alpine Ridge 4C 2016] (rev 02) 2d:00.0 USB controller: Intel Corporation JHL6540 Thunderbolt 3 USB Controller (C step) [Alpine Ridge 4C 2016] (rev 02) ``` ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Mar 17 14:21:31 2020 InstallationDate: Installed on 2020-01-15 (61 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET46W (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QFS10B00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information
[Touch-packages] [Bug 1850293] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-03-17 09:02 EDT--- IBM bugzilla status-> closed, Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1850293 Title: libep11 depends on old libssl for disco/eoan/focal Status in Ubuntu on IBM z Systems: Fix Released Status in openssl package in Ubuntu: Invalid Bug description: If using the newest version of libep11_2.1.0-8_s390x.deb with Disco/Eoan/Focal downloaded from http://public.dhe.ibm.com/security/cryptocards/pciecc3/EP11/2.1.0/ Following problem occur.: libep11 : Depends: libssl1.0.0 but it is not installable rmadison --arch=s390x libssl1.0.0 libssl1.0.0 | 1.0.2g-1ubuntu4| xenial | s390x libssl1.0.0 | 1.0.2g-1ubuntu4.15 | xenial-security | s390x libssl1.0.0 | 1.0.2g-1ubuntu4.15 | xenial-updates | s390x libssl1.0.0 | 1.0.2n-1ubuntu5| bionic | s390x libssl1.0.0 | 1.0.2n-1ubuntu5.3 | bionic-security | s390x libssl1.0.0 | 1.0.2n-1ubuntu5.3 | bionic-updates | s390x $ rmadison --arch=s390x libssl1.1 libssl1.1 | 1.1.0g-2ubuntu4 | bionic | s390x libssl1.1 | 1.1.1-1ubuntu2.1~18.04.4 | bionic-security | s390x libssl1.1 | 1.1.1-1ubuntu2.1~18.04.4 | bionic-updates | s390x libssl1.1 | 1.1.1b-1ubuntu2 | disco | s390x libssl1.1 | 1.1.1b-1ubuntu2.4| disco-updates | s390x libssl1.1 | 1.1.1c-1ubuntu4 | eoan| s390x libssl1.1 | 1.1.1c-1ubuntu4 | focal | s390x $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 19.10 Release: 19.10 Codename: eoan 11:58:56 AM: $ sudo apt install ./libep11_2.1.0-8_s390x.deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'libep11' instead of './libep11_2.1.0-8_s390x.deb' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libep11 : Depends: libssl1.0.0 but it is not installable E: Unable to correct problems, you have held broken packages. ubuntu@s1lp15:~$ sudo apt install ./libep11-dev_2.1.0-8_s390x.deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'libep11-dev' instead of './libep11-dev_2.1.0-8_s390x.deb' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libep11-dev : Depends: libep11 (= 2.1.0-8) but it is not installable E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1850293/+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 1502480] Re: Sound Settings and Time & Date Settings did not launch during gnome-flashback session
** Changed in: ubuntu-gnome-flashback Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1502480 Title: Sound Settings and Time & Date Settings did not launch during gnome- flashback session Status in Ubuntu GNOME Flashback: Fix Released Status in indicator-datetime package in Ubuntu: Fix Released Status in indicator-sound package in Ubuntu: Fix Released Bug description: When I try to launch Sound Settings or Time & Date Settings during gnome-flashback sessions it is nothing happen. Unity does not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome-flashback/+bug/1502480/+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 1410558] Re: ps doesn't support "thcount" format specifier on Xenial
Given this is an extremely simple fix to the procps output flags, none of the
autopkgtest regressions seem to be a result of this patch.
More details on each reported regression:
* apport/2.20.1-0ubuntu2.21 (amd64/i386)
- has failed since 2.20.1-0ubuntu2.18 according to [0]
- test_sandbox_cache_options: fails due to "ERROR: Package download error, try
again later: Untrusted packages:"
- test_get_logind_session: fails due to a systemd-logind error
- test_core_dump_packaged, test_core_dump_unpackaged: fail with "leaves
unexpected core file behind"
- test_crash_setuid_drop, test_crash_setuid_keep,
test_crash_setuid_nonwritable_cwd, test_lock_symlink: fail to generate reports
- test_run_crash_kernel: fails due to an URL mismatch
(http://linux-signed.bugs.example.com/5 vs http://linux.bugs.example.com/5)
* cmake/3.5.1-1ubuntu3 (armhf)
- retest could fix the proxy error
- CTestTestUpload: fails due to resolve error ("squid.internal" proxy)
* livecd-rootfs/2.408.57 (amd64/i386)
- tests timed out, a re-test should clear this regression
* openssh/1:7.2p2-4ubuntu2.8 (amd64/arm64/i386)
- failed due to host key certification, re-test should also clear this one
[0] http://autopkgtest.ubuntu.com/packages/a/apport/xenial/amd64
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1410558
Title:
ps doesn't support "thcount" format specifier on Xenial
Status in procps package in Ubuntu:
Fix Released
Status in procps source package in Xenial:
Fix Committed
Bug description:
[Impact]
ps -o thcount prints out an error (error: unknown user-defined format
specifier "thcount")
[Description]
The Xenial version of procps has a bug in the thcount format specifier. ps
doesn't recognize it, and complains about an unknown user-defined format.
This is due to the format specifier table in ps/output.c, which is queried
with a binary search. Since the "thcount" entry appears out of order in Xenial,
it can't be looked up and the program fails with the "unknown user-defined
format specifier" error.
This has been fixed upstream by the commit below:
- Fix for Bug:1174313 (3a52dfa34027)
$ git describe --contains 3a52dfa34027
v3.3.12~58^2
$ rmadison procps
procps | 2:3.3.10-4ubuntu2 | xenial | source, ...
procps | 2:3.3.10-4ubuntu2.4 | xenial-security | source, ...
procps | 2:3.3.10-4ubuntu2.4 | xenial-updates | source, ... <
procps | 2:3.3.12-3ubuntu1 | bionic | source, ...
procps | 2:3.3.12-3ubuntu1.1 | bionic-security | source, ...
procps | 2:3.3.12-3ubuntu1.2 | bionic-updates | source, ...
Releases starting with Bionic already have this fix, so it's only
needed for Xenial.
[Test case]
1. Boot up a Xenial environment with e.g. an lxd container:
# lxc launch images:ubuntu/xenial xenial
2. Execute ps with the '-o thcount' options:
# lxc exec xenial -- ps -o thcount
error: unknown user-defined format specifier "thcount"
Usage:
ps [options]
Try 'ps --help '
or 'ps --help '
for additional help text.
For more details see ps(1).
[Regression Potential]
The fix just fixes the order of two entries in the format specifier array, so
the regression potential is very low. Furthermore, the patch has been present
and tested in up-to-date versions of procps since Bionic. Any new regressions
introduced in Xenial will be checked with autopkgtest.
[Original Description]
In Ubuntu 12.04.5 LTS (procps 1:3.2.8-11ubuntu6.3), the following worked fine:
$ export PS_FORMAT=thcount
$ ps
THCNT
1
1
In Ubuntu 14.04.1 LTS (procps 1:3.3.9-1ubuntu2), it does not work
anymore:
$ export PS_FORMAT=thcount
$ ps
warning: $PS_FORMAT ignored. (unknown user-defined format specifier "thcount")
PID TTY TIME CMD
6593 pts/100:00:00 ps
16633 pts/100:00:00 bash
Other PS_FORMAT specifiers still work fine (I have tried many, but not
all).
In real-life usage, a more complex PS_FORMAT would of course be used,
such as
PS_FORMAT=pid,s,thcount,nice,euser,egroup,etime,cputime,%mem,rssize:6,size:7,vsize:7,command
Workaround: use nlwp instead of thcount (they are alias to the same
data, and nlwp works fine in both versions).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1410558/+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 1867766] Re: Namespace prefix sodipodi on namedview is not defined
" lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 "apt-cache policy gir1.2-rsvg-2.0 gir1.2-rsvg-2.0: Installed: 2.48.0-1 Candidate: 2.48.0-1 Version table: *** 2.48.0-1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 file: Packages 500 file: Packages 500 file: Packages 500 file: Packages 500 file: Packages 500 file: Packages 500 file: Packages 100 /var/lib/dpkg/status 2.46.4-1ubuntu1 500 500 file: Packages 500 file: Packages 500 file: Packages 500 file: Packages 500 file: Packages 500 file: Packages 500 file: Packages ** Tags added: oem-priority -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1867766 Title: Namespace prefix sodipodi on namedview is not defined Status in librsvg package in Ubuntu: New Bug description: [Summary] Since the package "gir1.2-rsvg-2.0:amd64" been upgraded from 2.46.4-1ubuntu1 to 2.48.0-1 in Focal's daily build, ubiquity will crash as attached crash log. [Steps to reproduce] 1. Boot with OEM mode, 2. Finish the 1st stage 3. Reboot 4. Boot into OOBE(oem-config) [Expected result] Should start oobe without any error. [Actual result] The error message 『The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again.』shown on the screen. [Failure rate] 100% [Additional information] No idea why, but some "nm-signal-*-secure" images will fail in Gtk.IconTheme().lookup_icon(n, 22, 0).load_icon(), and below error message will show: " Gtk-WARNING **: 18:23:31.380: Could not load a pixbuf from icon theme. This may indicate that pixbuf loaders or the mime database could not be found. gi.repository.GLib.GError: rsvg-error-quark: XML parse error: error code=201 (3) in (null):40:466: Namespace prefix sodipodi on namedview is not defined " To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1867766/+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 1867766] [NEW] Namespace prefix sodipodi on namedview is not defined
Public bug reported: [Summary] Since the package "gir1.2-rsvg-2.0:amd64" been upgraded from 2.46.4-1ubuntu1 to 2.48.0-1 in Focal's daily build, ubiquity will crash as attached crash log. [Steps to reproduce] 1. Boot with OEM mode, 2. Finish the 1st stage 3. Reboot 4. Boot into OOBE(oem-config) [Expected result] Should start oobe without any error. [Actual result] The error message 『The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again.』shown on the screen. [Failure rate] 100% [Additional information] No idea why, but some "nm-signal-*-secure" images will fail in Gtk.IconTheme().lookup_icon(n, 22, 0).load_icon(), and below error message will show: " Gtk-WARNING **: 18:23:31.380: Could not load a pixbuf from icon theme. This may indicate that pixbuf loaders or the mime database could not be found. gi.repository.GLib.GError: rsvg-error-quark: XML parse error: error code=201 (3) in (null):40:466: Namespace prefix sodipodi on namedview is not defined " ** Affects: librsvg (Ubuntu) Importance: Undecided Status: New ** Attachment added: "_usr_lib_ubiquity_bin_ubiquity.0.crash" https://bugs.launchpad.net/bugs/1867766/+attachment/5337963/+files/_usr_lib_ubiquity_bin_ubiquity.0.crash ** Summary changed: - gi.repository.GLib.GError: rsvg-error-quark: XML parse error: error code=201 (3) in (null):40:466: Namespace prefix sodipodi on namedview is not defined + Namespace prefix sodipodi on namedview is not defined -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1867766 Title: Namespace prefix sodipodi on namedview is not defined Status in librsvg package in Ubuntu: New Bug description: [Summary] Since the package "gir1.2-rsvg-2.0:amd64" been upgraded from 2.46.4-1ubuntu1 to 2.48.0-1 in Focal's daily build, ubiquity will crash as attached crash log. [Steps to reproduce] 1. Boot with OEM mode, 2. Finish the 1st stage 3. Reboot 4. Boot into OOBE(oem-config) [Expected result] Should start oobe without any error. [Actual result] The error message 『The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again.』shown on the screen. [Failure rate] 100% [Additional information] No idea why, but some "nm-signal-*-secure" images will fail in Gtk.IconTheme().lookup_icon(n, 22, 0).load_icon(), and below error message will show: " Gtk-WARNING **: 18:23:31.380: Could not load a pixbuf from icon theme. This may indicate that pixbuf loaders or the mime database could not be found. gi.repository.GLib.GError: rsvg-error-quark: XML parse error: error code=201 (3) in (null):40:466: Namespace prefix sodipodi on namedview is not defined " To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1867766/+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 1867760] Re: zorg crashes on every time on boot
May be related to lightdm found this in the crashreport: ProblemType: Crash Architecture: amd64 CrashCounter: 1 Date: Tue Mar 17 07:14:50 2020 DistroRelease: Ubuntu 18.04 ExecutablePath: /usr/lib/xorg/Xorg ExecutableTimestamp: 1576656929 ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root /:0 -nolisten tcp vt7 -novtswitch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1867760 Title: zorg crashes on every time on boot Status in xorg package in Ubuntu: New Bug description: This is more of an annoyance than anything. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CompositorRunning: None CurrentDesktop: XFCE Date: Tue Mar 17 07:29:19 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.3.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller [1028:024f] Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller [1028:024f] InstallationDate: Installed on 2020-03-16 (0 days ago) InstallationMedia: Xubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Dell Inc. Latitude E6500 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=93ad7557-b4ea-40bd-a8ac-3496ddeb2747 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A29 dmi.board.name: 0W612R dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA29:bd06/04/2013:svnDellInc.:pnLatitudeE6500:pvr:rvnDellInc.:rn0W612R:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude E6500 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1867760/+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 1867760] [NEW] zorg crashes on every time on boot
Public bug reported: This is more of an annoyance than anything. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CompositorRunning: None CurrentDesktop: XFCE Date: Tue Mar 17 07:29:19 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.3.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller [1028:024f] Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller [1028:024f] InstallationDate: Installed on 2020-03-16 (0 days ago) InstallationMedia: Xubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Dell Inc. Latitude E6500 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=93ad7557-b4ea-40bd-a8ac-3496ddeb2747 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A29 dmi.board.name: 0W612R dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA29:bd06/04/2013:svnDellInc.:pnLatitudeE6500:pvr:rvnDellInc.:rn0W612R:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude E6500 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1867760 Title: zorg crashes on every time on boot Status in xorg package in Ubuntu: New Bug description: This is more of an annoyance than anything. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CompositorRunning: None CurrentDesktop: XFCE Date: Tue Mar 17 07:29:19 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.3.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller [1028:024f] Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller [1028:024f] InstallationDate: Installed on 2020-03-16 (0 days ago) InstallationMedia: Xubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Dell Inc. Latitude E6500 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=93ad7557-b4ea-40bd-a8ac-3496ddeb2747 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A29 dmi.board.name: 0W612R dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA29:bd06/04/2013:svnDellInc.:pnLatitudeE6500:pvr:rvnDellInc.:rn0W612R:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude E6500 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
[Touch-packages] [Bug 1850293] Re: libep11 depends on old libssl for disco/eoan/focal
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1850293 Title: libep11 depends on old libssl for disco/eoan/focal Status in Ubuntu on IBM z Systems: Fix Released Status in openssl package in Ubuntu: Invalid Bug description: If using the newest version of libep11_2.1.0-8_s390x.deb with Disco/Eoan/Focal downloaded from http://public.dhe.ibm.com/security/cryptocards/pciecc3/EP11/2.1.0/ Following problem occur.: libep11 : Depends: libssl1.0.0 but it is not installable rmadison --arch=s390x libssl1.0.0 libssl1.0.0 | 1.0.2g-1ubuntu4| xenial | s390x libssl1.0.0 | 1.0.2g-1ubuntu4.15 | xenial-security | s390x libssl1.0.0 | 1.0.2g-1ubuntu4.15 | xenial-updates | s390x libssl1.0.0 | 1.0.2n-1ubuntu5| bionic | s390x libssl1.0.0 | 1.0.2n-1ubuntu5.3 | bionic-security | s390x libssl1.0.0 | 1.0.2n-1ubuntu5.3 | bionic-updates | s390x $ rmadison --arch=s390x libssl1.1 libssl1.1 | 1.1.0g-2ubuntu4 | bionic | s390x libssl1.1 | 1.1.1-1ubuntu2.1~18.04.4 | bionic-security | s390x libssl1.1 | 1.1.1-1ubuntu2.1~18.04.4 | bionic-updates | s390x libssl1.1 | 1.1.1b-1ubuntu2 | disco | s390x libssl1.1 | 1.1.1b-1ubuntu2.4| disco-updates | s390x libssl1.1 | 1.1.1c-1ubuntu4 | eoan| s390x libssl1.1 | 1.1.1c-1ubuntu4 | focal | s390x $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 19.10 Release: 19.10 Codename: eoan 11:58:56 AM: $ sudo apt install ./libep11_2.1.0-8_s390x.deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'libep11' instead of './libep11_2.1.0-8_s390x.deb' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libep11 : Depends: libssl1.0.0 but it is not installable E: Unable to correct problems, you have held broken packages. ubuntu@s1lp15:~$ sudo apt install ./libep11-dev_2.1.0-8_s390x.deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'libep11-dev' instead of './libep11-dev_2.1.0-8_s390x.deb' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libep11-dev : Depends: libep11 (= 2.1.0-8) but it is not installable E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1850293/+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 1865504] Re: hwclock reports incorrect status in audit message
Hi Joy,
Thanks for looking at those, I'm back from PTO and will take a look at
clearing them out.
Do you plan to verify bionic/eoan-proposed? I can do it as it's quick,
but wanted to check w/ you first as you're the reporter.
Thanks,
Mauricio
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1865504
Title:
hwclock reports incorrect status in audit message
Status in util-linux package in Ubuntu:
Fix Released
Status in util-linux source package in Bionic:
Fix Committed
Status in util-linux source package in Eoan:
Fix Committed
Status in util-linux package in Debian:
Unknown
Bug description:
[Impact]
hwclock reports incorrect status in audit message:
- hwclock calls audit_log_user_message(3) to create an audit entry.
- audit_log_user_message(3) result 1 is "success" and 0 is "failed".
- hwclock use standard EXIT_{SUCCESS,FAILURE} macros with reverse status.
- Thus reports its status incorrectly in audit message.
It is a requirement for Common Criteria Certification that hwclock
reports correct status in audit message.
This has been fixed upstream in https://github.com/karelzak/util-
linux/commit/189edf1fe501ea39b35911337eab1740888fae7a
[Test Steps]
Steps to test:
1. Install auditd
2. Run following testcase,
# hwclock
2020-03-02 15:03:03.280351+
# hwclock --set --date "1/1/2000 00:00:00"
# echo $?
0
# hwclock
2000-01-01 00:00:05.413924+
# hwclock --utc --systohc
# echo $?
0
# hwclock
2020-03-02 15:07:00.264331+
Following audit messages from /var/log/audit/audit.log,
Note that last field in each audit record produced when hardware clock
was modified has, "res=failed". Although, testcase shows no* failure
occurred.
type=USYS_CONFIG msg=audit(1583161562.884:105): pid=2084 uid=0
auid=1000 ses=1 msg='op=change-system-time exe="/sbin/hwclock"
hostname=bionic-fips addr=? terminal=pts/0 res=failed'
type=USYS_CONFIG msg=audit(1583161614.497:106): pid=2103 uid=0
auid=1000 ses=1 msg='op=change-system-time exe="/sbin/hwclock"
hostname=bionic-fips addr=? terminal=pts/0 res=failed'
[Regression Potential]
Changes limited to the result value passed to audit_log_user_message(3),
so the audit messages will change the 'res=' field (to correct result.)
There should not be any regression to fix the status given to auditd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1865504/+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 1867735] Re: Can't login after computer locks on idle
gnome-shell is responsible for the lock screen so reassigning to that ** Package changed: shadow (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1867735 Title: Can't login after computer locks on idle Status in gnome-shell package in Ubuntu: New Bug description: After a leave my computer on idle and try to put my password to login the screen starts to blink whenever I click on the screen. The workaround I found is to click on the switch user button to log back in but some windows are closed on this process. Also when the screen is locked I'm able to see the windows running on the user profile without unlocking ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: login 1:4.8.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 17 09:49:09 2020 InstallationDate: Installed on 2019-12-24 (83 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: shadow UpgradeStatus: Upgraded to focal on 2020-03-15 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867735/+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 1867653] Re: apt --fix-broken-install thinks I have other options and fails
Papercut? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1867653 Title: apt --fix-broken-install thinks I have other options and fails Status in apt package in Ubuntu: New Bug description: If I run `sudo apt --fix-broken-install` I receive ``` E: Command line option --fix-broken-install is not understood in combination with the other options ``` even if I don't have any other option. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 1.9.10 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Mar 16 19:00:14 2020 InstallationDate: Installed on 2019-02-03 (406 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1867653/+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 1867653] Re: apt --fix-broken-install thinks I have other options and fails
Thanks, yes it works. I didn't realised of the typo. I agree then that's just a confusing error message -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1867653 Title: apt --fix-broken-install thinks I have other options and fails Status in apt package in Ubuntu: New Bug description: If I run `sudo apt --fix-broken-install` I receive ``` E: Command line option --fix-broken-install is not understood in combination with the other options ``` even if I don't have any other option. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 1.9.10 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Mar 16 19:00:14 2020 InstallationDate: Installed on 2019-02-03 (406 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1867653/+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 1706770] Re: Lock screen can be bypassed when auto-login is enabled.
** Changed in: lightdm (Ubuntu) Status: Confirmed => Fix Committed -- 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/1706770 Title: Lock screen can be bypassed when auto-login is enabled. Status in Ubuntu MATE: Confirmed Status in lightdm package in Ubuntu: Fix Committed Status in mate-session-manager package in Ubuntu: Confirmed Bug description: 16.04 LTS = Hi, My machine is set up with full-disk encryption, so it requires a password when I boot it up. Because of this I thought I would enable auto-login to avoid having to enter two passwords at boot. When I leave my computer for short periods of time, I lock it. I thought this was working fine for a long time, but I've discovered the lock screen is actually easily bypassable when auto-login is enabled. All one has to do is click "Switch User" on the lock screen, then press "Unlock" and the computer unlocks without prompting for a password. Perhaps this is just me being an idiot, but I thought this was secure until now. It seems like either unlocking should always require a password (otherwise what's the point of locking in the first place) or it should be made totally obvious that unlocking doesn't actually require a password (i.e. removing the password box from the lock screen when auto-login is enabled). Thanks, Chris To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1706770/+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 1867653] Re: apt --fix-broken-install thinks I have other options and fails
It really seems to be a confusing way of saying "unknown option". Please try without the final dash sudo apt --fix-broken install where there's a space between "--fix-broken" and "install". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1867653 Title: apt --fix-broken-install thinks I have other options and fails Status in apt package in Ubuntu: New Bug description: If I run `sudo apt --fix-broken-install` I receive ``` E: Command line option --fix-broken-install is not understood in combination with the other options ``` even if I don't have any other option. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 1.9.10 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Mar 16 19:00:14 2020 InstallationDate: Installed on 2019-02-03 (406 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1867653/+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 1867735] [NEW] Can't login after computer locks on idle
Public bug reported: After a leave my computer on idle and try to put my password to login the screen starts to blink whenever I click on the screen. The workaround I found is to click on the switch user button to log back in but some windows are closed on this process. Also when the screen is locked I'm able to see the windows running on the user profile without unlocking ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: login 1:4.8.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 17 09:49:09 2020 InstallationDate: Installed on 2019-12-24 (83 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: shadow UpgradeStatus: Upgraded to focal on 2020-03-15 (1 days ago) ** Affects: shadow (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1867735 Title: Can't login after computer locks on idle Status in shadow package in Ubuntu: New Bug description: After a leave my computer on idle and try to put my password to login the screen starts to blink whenever I click on the screen. The workaround I found is to click on the switch user button to log back in but some windows are closed on this process. Also when the screen is locked I'm able to see the windows running on the user profile without unlocking ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: login 1:4.8.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 17 09:49:09 2020 InstallationDate: Installed on 2019-12-24 (83 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: shadow UpgradeStatus: Upgraded to focal on 2020-03-15 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1867735/+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 1867733] [NEW] [GS43VR 6RE, Realtek ALC898, Black Mic, Rear] No autoswitch
Public bug reported: There is no autoswitch and the mic is not detected ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: victorio 3988 F pulseaudio /dev/snd/controlC0: victorio 3988 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Mar 17 08:34:24 2020 InstallationDate: Installed on 2020-02-19 (26 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Audio Interno - HDA Intel PCH Symptom_Jack: Black Mic, Rear Symptom_Type: No auto-switch between inputs Title: [GS43VR 6RE, Realtek ALC898, Black Mic, Rear] No autoswitch UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E14A3IMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-14A3 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.A dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE14A3IMS.105:bd09/14/2016:svnMicro-StarInternationalCo.,Ltd.:pnGS43VR6RE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14A3:rvrREV0.A:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring: dmi.product.family: G dmi.product.name: GS43VR 6RE dmi.product.sku: 14A3.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1867733 Title: [GS43VR 6RE, Realtek ALC898, Black Mic, Rear] No autoswitch Status in alsa-driver package in Ubuntu: New Bug description: There is no autoswitch and the mic is not detected ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: victorio 3988 F pulseaudio /dev/snd/controlC0: victorio 3988 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Mar 17 08:34:24 2020 InstallationDate: Installed on 2020-02-19 (26 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Audio Interno - HDA Intel PCH Symptom_Jack: Black Mic, Rear Symptom_Type: No auto-switch between inputs Title: [GS43VR 6RE, Realtek ALC898, Black Mic, Rear] No autoswitch UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E14A3IMS.105 dmi.board.asset.tag: Default string dmi.board.name: MS-14A3 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.A dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE14A3IMS.105:bd09/14/2016:svnMicro-StarInternationalCo.,Ltd.:pnGS43VR6RE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14A3:rvrREV0.A:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring: dmi.product.family: G dmi.product.name: GS43VR 6RE dmi.product.sku: 14A3.1 dmi.product.version: REV: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/1867733/+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 1355025] Re: After suspend/resume, no sound with pulseaudio
** Tags added: resume suspend-resume -- 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/1355025 Title: After suspend/resume, no sound with pulseaudio Status in pulseaudio package in Ubuntu: Confirmed Bug description: HI, I've remarked the following bug, at least under KDE : DO : open your KDE session DO : launch an app which has not been set compliant with pulseaudio (for example, Skype 4.2, but in that case you need to log into the service so that it plays a sound - issue no longer reproducible with 4.3. This also works with Steam games like Civ5) DO : quit the app DO : suspend DO : wait some time, for example 15 minutes DO : resume DO : try to trigger a sound, anything (the sound tester applet in KDE is enough) EXPECT : you hear sound ACTUAL : no sound at all. Note that if you run pulseaudio -k, sound is partially restored... only for KDE apps. The only way to restore sound completely is to logout/login Reproducibility : always Tested on Kubuntu Trusty AMD64 My hardware : AMD Phenom x4 9850 8 GB RAM Asus M2N-SLI Deluxe NVidia GeForce 660 Ti ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: julien 4967 F pulseaudio julien31643 F pulseaudio /dev/snd/controlC0: julien 4967 F pulseaudio julien31643 F pulseaudio CurrentDesktop: KDE Date: Mon Aug 11 08:42:19 2014 SourcePackage: pulseaudio UpgradeStatus: Upgraded to trusty on 2014-03-20 (143 days ago) dmi.bios.date: 10/02/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS M2N-SLI DELUXE ACPI BIOS Revision 1701 dmi.board.name: M2N-SLI DELUXE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2N-SLIDELUXEACPIBIOSRevision1701:bd10/02/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-SLIDELUXE:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1355025/+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 1189107] Re: USB Soundcard is not detected everytime, especially on resume from suspend
** Tags added: resume suspend-resume -- 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/1189107 Title: USB Soundcard is not detected everytime, especially on resume from suspend Status in pulseaudio package in Ubuntu: New Bug description: Creative X-Fi USB seems not to be detected correctly. First time there's no possiblity to change output type to 5.1 (no menu in control center). After detaching and hooking up again it was not there. The third time I was able to detect it. It might be something to do with kernel. I have such information in dmesg: [ 2553.238048] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88020eb3b440 ... [ 2594.659850] usb 3-3.1: USB disconnect, device number 4 [ 2600.480546] usb 3-3.1: new full-speed USB device number 9 using xhci_hcd [ 2600.499566] usb 3-3.1: New USB device found, idVendor=041e, idProduct=3042 [ 2600.499574] usb 3-3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2600.499578] usb 3-3.1: Product: SB X-Fi Surround 5.1 [ 2600.499582] usb 3-3.1: Manufacturer: Creative Technology [ 2600.499585] usb 3-3.1: SerialNumber: 01ZK [ 2600.499842] usb 3-3.1: ep 0x83 - rounding interval to 64 microframes, ep desc says 80 microframes [ 2601.150221] xhci_queue_isoc_tx_prepare: 18 callbacks suppressed [ 2636.820277] usb 3-3.1: USB disconnect, device number 9 [ 2640.852723] usb 3-3.1: new full-speed USB device number 10 using xhci_hcd [ 2640.871708] usb 3-3.1: New USB device found, idVendor=041e, idProduct=3042 [ 2640.871716] usb 3-3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2640.871720] usb 3-3.1: Product: SB X-Fi Surround 5.1 [ 2640.871723] usb 3-3.1: Manufacturer: Creative Technology [ 2640.871726] usb 3-3.1: SerialNumber: 01ZK [ 2640.871986] usb 3-3.1: ep 0x83 - rounding interval to 64 microframes, ep desc says 80 microframes [ 2641.512162] xhci_queue_isoc_tx_prepare: 14 callbacks suppressed [ 2654.451042] usb 3-3.1: USB disconnect, device number 10 [ 2656.183934] usb 3-3.1: new full-speed USB device number 11 using xhci_hcd [ 2656.202981] usb 3-3.1: New USB device found, idVendor=041e, idProduct=3042 [ 2656.202989] usb 3-3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2656.202993] usb 3-3.1: Product: SB X-Fi Surround 5.1 [ 2656.202997] usb 3-3.1: Manufacturer: Creative Technology [ 2656.203000] usb 3-3.1: SerialNumber: 01ZK [ 2656.203242] usb 3-3.1: ep 0x83 - rounding interval to 64 microframes, ep desc says 80 microframes [ 2656.843048] xhci_queue_isoc_tx_prepare: 10 callbacks suppressed [ 2663.443582] xhci_queue_isoc_tx_prepare: 18 callbacks suppressed ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: pulseaudio 1:3.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mastier5078 F pulseaudio /dev/snd/pcmC1D0p: mastier5078 F...m pulseaudio /dev/snd/controlC0: mastier4113 F pulseaudio mastier5078 F pulseaudio Date: Sun Jun 9 10:34:52 2013 InstallationDate: Installed on 2012-10-25 (227 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True ProcEnviron: TERM=rxvt PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to raring on 2013-04-09 (60 days ago) dmi.bios.date: 04/10/2013 dmi.bios.vendor: LENOVO dmi.bios.version: GCET93WW (2.53 ) dmi.board.asset.tag: Not Available dmi.board.name: 34352NG dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGCET93WW(2.53):bd04/10/2013:svnLENOVO:pn34352NG:pvrThinkPadX230Tablet:rvnLENOVO:rn34352NG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 34352NG dmi.product.version: ThinkPad X230 Tablet dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1189107/+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 1867726] Re: Main audio device missing after resume from suspend
*** This bug is a duplicate of bug 1860764 *** https://bugs.launchpad.net/bugs/1860764 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1860764, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Summary changed: - don't exit a proper device sound after resume + Main audio device missing after resume from suspend ** Tags added: resume suspend-resume ** This bug has been marked a duplicate of bug 1860764 Line out audio device is missing after resume-from-suspend -- 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/1867726 Title: Main audio device missing after resume from suspend Status in pulseaudio package in Ubuntu: New Bug description: i am from this issue https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884 i test on 2.1 sound system without earphones!!! after resume i can see only 2 sound device 1 - Hdmi/displayport -pg106 high definition audio controller 2- dummy output and my sound doesn't work i used to test rhythmbox. but if i execute this systemctl --user restart pulseaudio i can see third device line out -family 17h (models 00h-0fh)hd audio controller How can we fix it? today i got all updates apt update apt upgrade ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob2353 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Mar 17 09:35:37 2020 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: pulseaudio UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob7141 F pulseaudio /dev/snd/controlC1: rob7141 F pulseaudio /dev/snd/pcmC1D0p: rob7141 F...m pulseaudio /dev/snd/timer: rob7141 f pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND
[Touch-packages] [Bug 1718927] Re: No HDMI sound after suspend/resume
This bug should remain unique to the original reporter. Everyone else please open a new bug. ** Tags added: resume suspend-resume ** Tags removed: 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/1718927 Title: No HDMI sound after suspend/resume Status in pulseaudio package in Ubuntu: Confirmed Bug description: When plugging in a HDMI TV to Lenovo Carbon 3rd Edition, sound works perfectly, but when I suspend computer and resume it there is no sound via HDMI in TV. However sound via built in speakers works fine. The only thing I can do to restore sound is to reboot the machine. Similar problem was discussed in following thread https://ubuntuforums.org/showthread.php?t=2251651 with no solution. I tested it on several versions of kernel 4.4.0 and on 4.4.8. Still no solution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1718927/+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 1866066] Re: Sound defaults to DUMMY output on resume [System76 galp3-c]
** Tags added: resume suspend-resume -- 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/1866066 Title: Sound defaults to DUMMY output on resume [System76 galp3-c] Status in pulseaudio package in Ubuntu: New Bug description: Sounds works perfectly. Suspend the laptop and then upon resume sound is switched to DUMMY OUTPUT requires restart. Just started happening. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.5 ProcVersionSignature: Ubuntu 5.3.0-7629.31~1581628854~18.04~2db8a7a~dev-generic 5.3.13 Uname: Linux 5.3.0-7629-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Mar 4 07:43:54 2020 InstallationDate: Installed on 2020-02-06 (26 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03-1 dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago Pro dmi.board.vendor: System76 dmi.board.version: galp3-c dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: galp3-c dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03-1:bd12/05/2018:svnSystem76:pnGalagoPro:pvrgalp3-c:rvnSystem76:rnGalagoPro:rvrgalp3-c:cvnSystem76:ct10:cvrgalp3-c: dmi.product.family: Not Applicable dmi.product.name: Galago Pro dmi.product.sku: Not Applicable dmi.product.version: galp3-c dmi.sys.vendor: System76 modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-03-04T07:42:51.788265 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1866066/+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 1820743] Re: Pulseaudio is sometimes broken after resume from suspend
** Tags added: resume suspend-resume -- 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/1820743 Title: Pulseaudio is sometimes broken after resume from suspend Status in pulseaudio package in Ubuntu: Confirmed Bug description: Sometimes when resuming from suspend pulseaudio is broken and only the dummy output is available. After "pulseaudio -k" audio again works. Here's what I found in the logs: $ journalctl --since "1 day ago" | grep pulseaudio Mar 17 19:40:51 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Mar 17 21:29:49 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Mar 18 09:01:13 coulson pulseaudio[9869]: [alsa-sink-ALC293 Analog] alsa-sink.c: snd_pcm_mmap_begin: File descriptor in bad state Mar 18 09:06:25 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Mar 18 09:32:40 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Mar 18 09:47:36 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Mar 18 18:16:42 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. --- Here I ran pulseaudio -k --- Mar 18 19:08:13 coulson pulseaudio[26606]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Mar 18 19:08:13 coulson pulseaudio[26612]: [pulseaudio] pid.c: Daemon already running. Mar 18 19:08:13 coulson pulseaudio[26614]: [pulseaudio] pid.c: Daemon already running. Mar 18 19:08:13 coulson pulseaudio[26616]: [pulseaudio] pid.c: Daemon already running. The "Failed to create sink input" seems to happen on every resume but only some times does it actually break. Don't know if the ofono message is related or not. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pedrocr 26606 F pulseaudio CurrentDesktop: GNOME Date: Mon Mar 18 19:11:09 2019 InstallationDate: Installed on 2018-05-31 (291 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET66W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS5TS00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS5TS00 dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1820743/+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 1867726] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1867726/+attachment/5337823/+files/AlsaInfo.txt -- 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/1867726 Title: don't exit a proper device sound after resume Status in pulseaudio package in Ubuntu: New Bug description: i am from this issue https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884 i test on 2.1 sound system without earphones!!! after resume i can see only 2 sound device 1 - Hdmi/displayport -pg106 high definition audio controller 2- dummy output and my sound doesn't work i used to test rhythmbox. but if i execute this systemctl --user restart pulseaudio i can see third device line out -family 17h (models 00h-0fh)hd audio controller How can we fix it? today i got all updates apt update apt upgrade ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob2353 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Mar 17 09:35:37 2020 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: pulseaudio UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob7141 F pulseaudio /dev/snd/controlC1: rob7141 F pulseaudio /dev/snd/pcmC1D0p: rob7141 F...m pulseaudio /dev/snd/timer: rob7141 f pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob7141 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40
[Touch-packages] [Bug 1867726] Re: don't exit a proper device sound after resume
done. i sent with not working sound ** Description changed: i am from this issue https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884 - + i test on 2.1 sound system without earphones!!! + after resume i can see only 2 sound device 1 - Hdmi/displayport -pg106 high definition audio controller 2- dummy output and my sound doesn't work i used to test rhythmbox. but if i execute this systemctl --user restart pulseaudio i can see third device line out -family 17h (models 00h-0fh)hd audio controller How can we fix it? today i got all updates apt update apt upgrade ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob2353 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Mar 17 09:35:37 2020 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: pulseaudio UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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. - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: rob7141 F pulseaudio - /dev/snd/controlC1: rob7141 F pulseaudio - /dev/snd/pcmC1D0p: rob7141 F...m pulseaudio - /dev/snd/timer: rob7141 f pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: rob7141 F pulseaudio + /dev/snd/controlC1: rob7141 F pulseaudio + /dev/snd/pcmC1D0p: rob7141 F...m pulseaudio + /dev/snd/timer: rob7141 f pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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. - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: rob7141 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: rob7141 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350
[Touch-packages] [Bug 1867726] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1867726/+attachment/5337819/+files/PulseList.txt -- 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/1867726 Title: don't exit a proper device sound after resume Status in pulseaudio package in Ubuntu: New Bug description: i am from this issue https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884 i test on 2.1 sound system without earphones!!! after resume i can see only 2 sound device 1 - Hdmi/displayport -pg106 high definition audio controller 2- dummy output and my sound doesn't work i used to test rhythmbox. but if i execute this systemctl --user restart pulseaudio i can see third device line out -family 17h (models 00h-0fh)hd audio controller How can we fix it? today i got all updates apt update apt upgrade ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob2353 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Mar 17 09:35:37 2020 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: pulseaudio UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob7141 F pulseaudio /dev/snd/controlC1: rob7141 F pulseaudio /dev/snd/pcmC1D0p: rob7141 F...m pulseaudio /dev/snd/timer: rob7141 f pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob7141 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40
[Touch-packages] [Bug 1867726] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1867726/+attachment/5337828/+files/PulseList.txt -- 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/1867726 Title: don't exit a proper device sound after resume Status in pulseaudio package in Ubuntu: New Bug description: i am from this issue https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884 i test on 2.1 sound system without earphones!!! after resume i can see only 2 sound device 1 - Hdmi/displayport -pg106 high definition audio controller 2- dummy output and my sound doesn't work i used to test rhythmbox. but if i execute this systemctl --user restart pulseaudio i can see third device line out -family 17h (models 00h-0fh)hd audio controller How can we fix it? today i got all updates apt update apt upgrade ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob2353 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Mar 17 09:35:37 2020 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: pulseaudio UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob7141 F pulseaudio /dev/snd/controlC1: rob7141 F pulseaudio /dev/snd/pcmC1D0p: rob7141 F...m pulseaudio /dev/snd/timer: rob7141 f pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob7141 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40
[Touch-packages] [Bug 1867726] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1867726/+attachment/5337827/+files/ProcEnviron.txt -- 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/1867726 Title: don't exit a proper device sound after resume Status in pulseaudio package in Ubuntu: New Bug description: i am from this issue https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884 i test on 2.1 sound system without earphones!!! after resume i can see only 2 sound device 1 - Hdmi/displayport -pg106 high definition audio controller 2- dummy output and my sound doesn't work i used to test rhythmbox. but if i execute this systemctl --user restart pulseaudio i can see third device line out -family 17h (models 00h-0fh)hd audio controller How can we fix it? today i got all updates apt update apt upgrade ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob2353 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Mar 17 09:35:37 2020 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: pulseaudio UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob7141 F pulseaudio /dev/snd/controlC1: rob7141 F pulseaudio /dev/snd/pcmC1D0p: rob7141 F...m pulseaudio /dev/snd/timer: rob7141 f pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob7141 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40
[Touch-packages] [Bug 1867726] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1867726/+attachment/5337826/+files/ProcCpuinfoMinimal.txt -- 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/1867726 Title: don't exit a proper device sound after resume Status in pulseaudio package in Ubuntu: New Bug description: i am from this issue https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884 i test on 2.1 sound system without earphones!!! after resume i can see only 2 sound device 1 - Hdmi/displayport -pg106 high definition audio controller 2- dummy output and my sound doesn't work i used to test rhythmbox. but if i execute this systemctl --user restart pulseaudio i can see third device line out -family 17h (models 00h-0fh)hd audio controller How can we fix it? today i got all updates apt update apt upgrade ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob2353 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Mar 17 09:35:37 2020 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: pulseaudio UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob7141 F pulseaudio /dev/snd/controlC1: rob7141 F pulseaudio /dev/snd/pcmC1D0p: rob7141 F...m pulseaudio /dev/snd/timer: rob7141 f pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob7141 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version:
[Touch-packages] [Bug 1867726] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1867726/+attachment/5337825/+files/Dependencies.txt -- 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/1867726 Title: don't exit a proper device sound after resume Status in pulseaudio package in Ubuntu: New Bug description: i am from this issue https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884 i test on 2.1 sound system without earphones!!! after resume i can see only 2 sound device 1 - Hdmi/displayport -pg106 high definition audio controller 2- dummy output and my sound doesn't work i used to test rhythmbox. but if i execute this systemctl --user restart pulseaudio i can see third device line out -family 17h (models 00h-0fh)hd audio controller How can we fix it? today i got all updates apt update apt upgrade ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob2353 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Mar 17 09:35:37 2020 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: pulseaudio UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob7141 F pulseaudio /dev/snd/controlC1: rob7141 F pulseaudio /dev/snd/pcmC1D0p: rob7141 F...m pulseaudio /dev/snd/timer: rob7141 f pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob7141 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40
[Touch-packages] [Bug 1867726] Re: don't exit a proper device sound after resume
i resent with correct. now i'm going to sent signal for slepping. ** Description changed: i am from this issue https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884 after resume i can see only 2 sound device 1 - Hdmi/displayport -pg106 high definition audio controller 2- dummy output and my sound doesn't work i used to test rhythmbox. but if i execute this systemctl --user restart pulseaudio i can see third device line out -family 17h (models 00h-0fh)hd audio controller How can we fix it? today i got all updates apt update apt upgrade ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob2353 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Mar 17 09:35:37 2020 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: pulseaudio UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob7141 F pulseaudio /dev/snd/controlC1: rob7141 F pulseaudio /dev/snd/pcmC1D0p: rob7141 F...m pulseaudio /dev/snd/timer: rob7141 f pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu8.5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: rob7141 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 19.10 + InstallationDate: Installed on 2019-01-26 (415 days ago) + InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) + NonfreeKernelModules: nvidia_modeset nvidia + Package: pulseaudio 1:13.0-1ubuntu1.1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 + Tags: eoan + Uname: Linux 5.3.0-42-generic x86_64 + UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 12/19/2018 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: P5.40 + dmi.board.name: AB350 Pro4 + 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:
[Touch-packages] [Bug 1867726] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1867726/+attachment/5337824/+files/CurrentDmesg.txt -- 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/1867726 Title: don't exit a proper device sound after resume Status in pulseaudio package in Ubuntu: New Bug description: i am from this issue https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884 i test on 2.1 sound system without earphones!!! after resume i can see only 2 sound device 1 - Hdmi/displayport -pg106 high definition audio controller 2- dummy output and my sound doesn't work i used to test rhythmbox. but if i execute this systemctl --user restart pulseaudio i can see third device line out -family 17h (models 00h-0fh)hd audio controller How can we fix it? today i got all updates apt update apt upgrade ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob2353 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Mar 17 09:35:37 2020 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: pulseaudio UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob7141 F pulseaudio /dev/snd/controlC1: rob7141 F pulseaudio /dev/snd/pcmC1D0p: rob7141 F...m pulseaudio /dev/snd/timer: rob7141 f pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob7141 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40
[Touch-packages] [Bug 1867726] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1867726/+attachment/5337817/+files/ProcCpuinfoMinimal.txt -- 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/1867726 Title: don't exit a proper device sound after resume Status in pulseaudio package in Ubuntu: New Bug description: i am from this issue https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884 i test on 2.1 sound system without earphones!!! after resume i can see only 2 sound device 1 - Hdmi/displayport -pg106 high definition audio controller 2- dummy output and my sound doesn't work i used to test rhythmbox. but if i execute this systemctl --user restart pulseaudio i can see third device line out -family 17h (models 00h-0fh)hd audio controller How can we fix it? today i got all updates apt update apt upgrade ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob2353 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Mar 17 09:35:37 2020 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: pulseaudio UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob7141 F pulseaudio /dev/snd/controlC1: rob7141 F pulseaudio /dev/snd/pcmC1D0p: rob7141 F...m pulseaudio /dev/snd/timer: rob7141 f pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob7141 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version:
[Touch-packages] [Bug 1867726] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1867726/+attachment/5337814/+files/AlsaInfo.txt -- 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/1867726 Title: don't exit a proper device sound after resume Status in pulseaudio package in Ubuntu: New Bug description: i am from this issue https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884 i test on 2.1 sound system without earphones!!! after resume i can see only 2 sound device 1 - Hdmi/displayport -pg106 high definition audio controller 2- dummy output and my sound doesn't work i used to test rhythmbox. but if i execute this systemctl --user restart pulseaudio i can see third device line out -family 17h (models 00h-0fh)hd audio controller How can we fix it? today i got all updates apt update apt upgrade ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob2353 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Mar 17 09:35:37 2020 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: pulseaudio UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob7141 F pulseaudio /dev/snd/controlC1: rob7141 F pulseaudio /dev/snd/pcmC1D0p: rob7141 F...m pulseaudio /dev/snd/timer: rob7141 f pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob7141 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40
[Touch-packages] [Bug 1867726] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1867726/+attachment/5337818/+files/ProcEnviron.txt -- 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/1867726 Title: don't exit a proper device sound after resume Status in pulseaudio package in Ubuntu: New Bug description: i am from this issue https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884 i test on 2.1 sound system without earphones!!! after resume i can see only 2 sound device 1 - Hdmi/displayport -pg106 high definition audio controller 2- dummy output and my sound doesn't work i used to test rhythmbox. but if i execute this systemctl --user restart pulseaudio i can see third device line out -family 17h (models 00h-0fh)hd audio controller How can we fix it? today i got all updates apt update apt upgrade ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob2353 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Mar 17 09:35:37 2020 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: pulseaudio UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob7141 F pulseaudio /dev/snd/controlC1: rob7141 F pulseaudio /dev/snd/pcmC1D0p: rob7141 F...m pulseaudio /dev/snd/timer: rob7141 f pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob7141 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40
[Touch-packages] [Bug 1867726] [NEW] don't exit a proper device sound after resume
Public bug reported: i am from this issue https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884 i test on 2.1 sound system without earphones!!! after resume i can see only 2 sound device 1 - Hdmi/displayport -pg106 high definition audio controller 2- dummy output and my sound doesn't work i used to test rhythmbox. but if i execute this systemctl --user restart pulseaudio i can see third device line out -family 17h (models 00h-0fh)hd audio controller How can we fix it? today i got all updates apt update apt upgrade ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob2353 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Mar 17 09:35:37 2020 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: pulseaudio UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob7141 F pulseaudio /dev/snd/controlC1: rob7141 F pulseaudio /dev/snd/pcmC1D0p: rob7141 F...m pulseaudio /dev/snd/timer: rob7141 f pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob7141 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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. ** Affects: pulseaudio (Ubuntu)
[Touch-packages] [Bug 1867726] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1867726/+attachment/5337816/+files/Dependencies.txt -- 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/1867726 Title: don't exit a proper device sound after resume Status in pulseaudio package in Ubuntu: New Bug description: i am from this issue https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884 i test on 2.1 sound system without earphones!!! after resume i can see only 2 sound device 1 - Hdmi/displayport -pg106 high definition audio controller 2- dummy output and my sound doesn't work i used to test rhythmbox. but if i execute this systemctl --user restart pulseaudio i can see third device line out -family 17h (models 00h-0fh)hd audio controller How can we fix it? today i got all updates apt update apt upgrade ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob2353 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Mar 17 09:35:37 2020 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: pulseaudio UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob7141 F pulseaudio /dev/snd/controlC1: rob7141 F pulseaudio /dev/snd/pcmC1D0p: rob7141 F...m pulseaudio /dev/snd/timer: rob7141 f pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob7141 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40
[Touch-packages] [Bug 1867726] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1867726/+attachment/5337815/+files/CurrentDmesg.txt -- 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/1867726 Title: don't exit a proper device sound after resume Status in pulseaudio package in Ubuntu: New Bug description: i am from this issue https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884 i test on 2.1 sound system without earphones!!! after resume i can see only 2 sound device 1 - Hdmi/displayport -pg106 high definition audio controller 2- dummy output and my sound doesn't work i used to test rhythmbox. but if i execute this systemctl --user restart pulseaudio i can see third device line out -family 17h (models 00h-0fh)hd audio controller How can we fix it? today i got all updates apt update apt upgrade ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob2353 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Mar 17 09:35:37 2020 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: pulseaudio UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob7141 F pulseaudio /dev/snd/controlC1: rob7141 F pulseaudio /dev/snd/pcmC1D0p: rob7141 F...m pulseaudio /dev/snd/timer: rob7141 f pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 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.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4: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. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob7141 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (132 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40
