[Touch-packages] [Bug 1744544] Re: I don't know
Please describe the kind of problem you are, or were, experiencing. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1744544 Title: I don't know Status in Ubuntu: Incomplete Bug description: I don't know ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Jan 21 11:06:23 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3977] NVIDIA Corporation GK107M [GeForce GTX 660M] [10de:0fd4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GK107M [GeForce GTX 660M] [17aa:3977] InstallationDate: Installed on 2017-08-05 (168 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 2099 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic root=UUID=13938ffd-9af8-467d-bb58-79084d5812e4 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 5DCN40WW(V2.07) dmi.board.asset.tag: No Asset Tag dmi.board.name: Product Name dmi.board.vendor: LENOVO dmi.board.version: Mainboard version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y580 dmi.modalias: dmi:bvnLENOVO:bvr5DCN40WW(V2.07):bd10/10/2012:svnLENOVO:pn2099:pvrLenovoIdeaPadY580:rvnLENOVO:rnProductName:rvrMainboardversion:cvnLENOVO:ct10:cvrLenovoIdeaPadY580: dmi.product.family: IDEAPAD dmi.product.name: 2099 dmi.product.version: Lenovo IdeaPad Y580 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4 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 xserver.bootTime: Sun Jan 21 10:54:21 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1744544/+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 1868131] Re: Integrated speakers always muted
** This bug is no longer a duplicate of bug 1310121 headphones working while speakers not working ** Summary changed: - Integrated speakers always muted + [Toshiba NB250] Integrated speakers always muted -- 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/1868131 Title: [Toshiba NB250] Integrated speakers always muted Status in pulseaudio package in Ubuntu: New Bug description: Speakers are muted at boot and remains muted after plug and unplug headphones. Only can be activated from alsamixer, unmuting the headphones while the headphones are unplugged. Both speakers and headphones muting seems to be controlled in the Headphones area using alsamixer. Same problem in pulseaudio 1:11.1-1ubuntu7.4 on Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic. I've "solved" it Linux Mint 19.3 Tricia in a not very good way, keeping automute activated in alsamixer, modifiyng /usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf and executing a bash script at boot (sonido.sh) with the command "amixer set -c 0 Headphone unmute 100%" in order to prevent the speakers being muted. There are some issues reported to pulseaudio manteiners. Not the same but related: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/256 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/540 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu1881 F pulseaudio CasperVersion: 1.427 CurrentDesktop: XFCE Date: Thu Mar 19 15:58:26 2020 LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.60 dmi.board.name: PAV10 DDR2 dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.60:bd07/30/2010:svnTOSHIBA:pnTOSHIBANB250:pvrPLL2XE-005003AS:rvnTOSHIBA:rnPAV10DDR2:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ dmi.product.name: TOSHIBA NB250 dmi.product.sku: 012345678912345678912345678 dmi.product.version: PLL2XE-005003AS dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1868131/+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 1868128] Re: (Error ID: OOPS-f9a25a1047f367bba335ebdf6c9c0a24)
Firstly, not related to this bug but I notice your system will be running very slow because it's logging every single screen refresh to the kernel log. To stop that you should remove the kernel parameter: drm.debug=0xe -- 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/1868128 Title: (Error ID: OOPS-f9a25a1047f367bba335ebdf6c9c0a24) Status in Ubuntu: Incomplete Bug description: trying to reinstall my Ubuntu 18.04 on my Toshiba Satelite 64 bus laptop. I have a loaded flash drive but I keep getting an error message as follows, (Error ID: OOPS-f9a25a1047f367bba335ebdf6c9c0a24) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Mar 19 08:43:35 2020 DistUpgraded: 2018-09-05 15:50:48,221 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems 4th Gen Core Processor Integrated Graphics Controller [1179:fa22] InstallationDate: Installed on 2017-04-18 (1065 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: TOSHIBA Satellite C55t-A ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic root=UUID=1be49583-6218-4da2-9204-c5ae2ac5cebd ro drm.debug=0xe plymouth:debug Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-05 (560 days ago) dmi.bios.date: 01/24/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.70 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.70:bd01/24/2014:svnTOSHIBA:pnSatelliteC55t-A:pvrPSCFJU-00T00J:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Durban-Curiosity 10S/10SG dmi.product.name: Satellite C55t-A dmi.product.version: PSCFJU-00T00J dmi.sys.vendor: TOSHIBA 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 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Jun 27 12:22:02 2017 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1868128/+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 1868128] Re: (Error ID: OOPS-f9a25a1047f367bba335ebdf6c9c0a24)
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) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1868128 Title: (Error ID: OOPS-f9a25a1047f367bba335ebdf6c9c0a24) Status in Ubuntu: Incomplete Bug description: trying to reinstall my Ubuntu 18.04 on my Toshiba Satelite 64 bus laptop. I have a loaded flash drive but I keep getting an error message as follows, (Error ID: OOPS-f9a25a1047f367bba335ebdf6c9c0a24) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Mar 19 08:43:35 2020 DistUpgraded: 2018-09-05 15:50:48,221 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems 4th Gen Core Processor Integrated Graphics Controller [1179:fa22] InstallationDate: Installed on 2017-04-18 (1065 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: TOSHIBA Satellite C55t-A ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic root=UUID=1be49583-6218-4da2-9204-c5ae2ac5cebd ro drm.debug=0xe plymouth:debug Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-05 (560 days ago) dmi.bios.date: 01/24/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.70 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.70:bd01/24/2014:svnTOSHIBA:pnSatelliteC55t-A:pvrPSCFJU-00T00J:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Durban-Curiosity 10S/10SG dmi.product.name: Satellite C55t-A dmi.product.version: PSCFJU-00T00J dmi.sys.vendor: TOSHIBA 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 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Jun 27 12:22:02 2017 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1868128/+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)
@eddie, If your usb audio doesn't work, please file a new bug against the linux kernel. Let's track your issue in that bug. 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 1867474] Re: [Dell Vostro 5590] PCI/internal sound card not detected
The kernel 5.3.0-43 is in the -proposed, please use this kernel instead of -42 kernel. -- 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/1867474 Title: [Dell Vostro 5590] PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: Problem with detecting audio input/output device. Device: Dell Vostro 5590 Tested earlier also on Ubuntu 18.04 and 19.10. On older systems with some configurations output device was working, but I never succeeded making build-in microphone to work (be properly detected). On current Ubuntu 20.04 (14.03.2020) both input and output audio devices are not visible at all. Devices are work without any issues on Windows 10 originally installed on the device. Let me know if I can provide any additional information that will help solving the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 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 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 23:45:55 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) 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: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 051P23 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn051P23:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5590 dmi.product.sku: 095A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867474/+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 1865536] Re: OBS consumes all memory, fixed in upstream Mesa
** Tags added: bionic -- 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/1865536 Title: OBS consumes all memory, fixed in upstream Mesa Status in Mesa: Unknown Status in mesa package in Ubuntu: Confirmed Bug description: There is an issue where due to a Mesa bug OBS consumes all memory eventually. See https://gitlab.freedesktop.org/mesa/mesa/issues/1426. Unfortunately, this issue is in all recent Ubuntu versions. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1865536/+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 1865536] Re: OBS consumes all memory, fixed in upstream Mesa
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- 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/1865536 Title: OBS consumes all memory, fixed in upstream Mesa Status in Mesa: Unknown Status in mesa package in Ubuntu: Confirmed Bug description: There is an issue where due to a Mesa bug OBS consumes all memory eventually. See https://gitlab.freedesktop.org/mesa/mesa/issues/1426. Unfortunately, this issue is in all recent Ubuntu versions. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1865536/+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)
@hui.wang My USB headset no longer works. I installed kernel 5.3.0-43 from proposed and libasound2 from your ppa. $ uname -a Linux eddie-minut 5.3.0-43-generic #36-Ubuntu SMP Mon Mar 16 13:29:01 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ cat /sys/devices/virtual/dmi/id/bios_version N2HET46W (1.29 ) $ dpkg -l libasound2 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++--=-- ii libasound2:amd64 1.1.9-0ubuntu1.2++testucm amd64shared library for ALSA applications $ dmesg ... [ 464.139786] usb 1-3: Manufacturer: Kingston [ 464.378226] input: Kingston HyperX Cloud Flight Wireless Headset Consumer Control as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.3/0003:0951:16C4.0005/input/input33 [ 464.437214] input: Kingston HyperX Cloud Flight Wireless Headset as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.3/0003:0951:16C4.0005/input/input34 [ 464.437594] input: Kingston HyperX Cloud Flight Wireless Headset as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.3/0003:0951:16C4.0005/input/input35 [ 464.437943] input: Kingston HyperX Cloud Flight Wireless Headset as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.3/0003:0951:16C4.0005/input/input36 [ 464.438711] hid-generic 0003:0951:16C4.0005: input,hiddev0,hidraw1: USB HID v1.11 Device [Kingston HyperX Cloud Flight Wireless Headset] on usb-:00:14.0-3/input3 [ 465.169150] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 465.264582] sof-audio-pci :00:1f.3: firmware boot complete [ 465.578000] debugfs: File 'Analog Playback and Capture' in directory 'HDA Analog' already present! [ 465.703404] debugfs: File 'Analog Playback and Capture' in directory 'HDA Analog' already present! [ 532.954965] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 533.052406] sof-audio-pci :00:1f.3: firmware boot complete [ 543.902184] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 When I plug in a headset with a mic in the 3.5mm port, it still seems to use the internal mic instead of that of the headset. I also get a lot of popping sounds in the 3.5mm headset when playing audio, but that might not be related to this issue as I had that on kernel 5.3.0-41 as well. -- 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 :
[Touch-packages] [Bug 1868179] [NEW] Typing in virtualbox during installation does not work
Public bug reported: I tried to install Ubuntu 19.10, 20.04 and 18.04.4LTS in virtualbox 6.1 on MacOS Catalina. The installating packages starts, the mouse works, so I can navigate all the way through to the user account creation screen. However, I cannot input anything using the keyboard. I can drag the dialogue text into the text fields but not delete/add by typing into the field. All keyboard input is ignored. I use the standards laptop keyboard of the mac which otherwise works fine. Since it fails in all versions specified above it is likely to be related to the combination of VirtualBox, MacOS and the ubuntu installe package. ** Affects: virtualbox Importance: Undecided Status: New ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Also affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Changed in: alsa-driver (Ubuntu) Status: New => Invalid ** No longer affects: alsa-driver (Ubuntu) ** Package changed: ubiquity (Ubuntu) => virtualbox ** Also affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- 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/1868179 Title: Typing in virtualbox during installation does not work Status in Virtualbox: New Status in ubiquity package in Ubuntu: New Bug description: I tried to install Ubuntu 19.10, 20.04 and 18.04.4LTS in virtualbox 6.1 on MacOS Catalina. The installating packages starts, the mouse works, so I can navigate all the way through to the user account creation screen. However, I cannot input anything using the keyboard. I can drag the dialogue text into the text fields but not delete/add by typing into the field. All keyboard input is ignored. I use the standards laptop keyboard of the mac which otherwise works fine. Since it fails in all versions specified above it is likely to be related to the combination of VirtualBox, MacOS and the ubuntu installe package. To manage notifications about this bug go to: https://bugs.launchpad.net/virtualbox/+bug/1868179/+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 1163155] Re: keep the 3 or 5 youngest linux-image-*-generic and autoremove the rest
We only keep a certain number of installed kernels, across all flavours. Older ones are autoremoved, even automatically with unattended-upgrades. ** Changed in: apt (Ubuntu) Status: New => Won't Fix ** Changed in: apt (Ubuntu) Status: Won't Fix => Invalid -- 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/1163155 Title: keep the 3 or 5 youngest linux-image-*-generic and autoremove the rest Status in apt package in Ubuntu: Invalid Bug description: Keep a configurable number (per default maybe 3) of the youngest installed generic kernel images. Onlye the generic ones! Selfbuild kernels are not affected of that. Ubuntu-Systems running very long without reinstallation. After some years of updating there are a lot of old kernel-images installed but never used. It is a lot of space for mobile devices like netbooks, laptops or smaller. It can be realize (like feudora does) with a meta-package like "kernel-lates" which is assoziated with the last/youngest 3 kernels. All older one would be autoremoved. Of course there could be selected another solution to make it easier to configure if someone need to keep all old kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1163155/+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 1694367] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1694367 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: yakkety -- 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/1694367 Title: Screen tearing in 16.10 onwards Status in Mesa: Unknown Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: New Bug description: In 16.10 onwards my laptop has always shown screen tearing globally, additionally GL applications will not v-sync despite attempting to, they appear to sync slightly off from the [integrated] display. This occurs with kernels 4.8 to 4.11 and mesa 12 to 17, so not entirely sure if it's a bug with either or a default miss- configuration in ubuntu... ubuntu-bug also appears to be broken... To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1694367/+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 1163155] Re: keep the 3 or 5 youngest linux-image-*-generic and autoremove the rest
** Package changed: kernel-package (Ubuntu) => apt (Ubuntu) -- 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/1163155 Title: keep the 3 or 5 youngest linux-image-*-generic and autoremove the rest Status in apt package in Ubuntu: New Bug description: Keep a configurable number (per default maybe 3) of the youngest installed generic kernel images. Onlye the generic ones! Selfbuild kernels are not affected of that. Ubuntu-Systems running very long without reinstallation. After some years of updating there are a lot of old kernel-images installed but never used. It is a lot of space for mobile devices like netbooks, laptops or smaller. It can be realize (like feudora does) with a meta-package like "kernel-lates" which is assoziated with the last/youngest 3 kernels. All older one would be autoremoved. Of course there could be selected another solution to make it easier to configure if someone need to keep all old kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1163155/+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
Correction for the patch, please use this one. ** Patch added: "69-libmtp.rules.patch" https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1863239/+attachment/5339060/+files/69-libmtp.rules.patch -- 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: Confirmed Status in pulseaudio package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid 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 1163155] [NEW] keep the 3 or 5 youngest linux-image-*-generic and autoremove the rest
You have been subscribed to a public bug: Keep a configurable number (per default maybe 3) of the youngest installed generic kernel images. Onlye the generic ones! Selfbuild kernels are not affected of that. Ubuntu-Systems running very long without reinstallation. After some years of updating there are a lot of old kernel-images installed but never used. It is a lot of space for mobile devices like netbooks, laptops or smaller. It can be realize (like feudora does) with a meta-package like "kernel-lates" which is assoziated with the last/youngest 3 kernels. All older one would be autoremoved. Of course there could be selected another solution to make it easier to configure if someone need to keep all old kernels. ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: apt-get aptitude kernel packaging -- keep the 3 or 5 youngest linux-image-*-generic and autoremove the rest https://bugs.launchpad.net/bugs/1163155 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt 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 1694367] Re: Screen tearing in 16.10 onwards
** Package changed: kernel-package (Ubuntu) => linux (Ubuntu) -- 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/1694367 Title: Screen tearing in 16.10 onwards Status in Mesa: Unknown Status in linux package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: In 16.10 onwards my laptop has always shown screen tearing globally, additionally GL applications will not v-sync despite attempting to, they appear to sync slightly off from the [integrated] display. This occurs with kernels 4.8 to 4.11 and mesa 12 to 17, so not entirely sure if it's a bug with either or a default miss- configuration in ubuntu... ubuntu-bug also appears to be broken... To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1694367/+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 1867972] Re: [FFe] Please accept systemd 245.2-1ubuntu1 to Focal
** Changed in: systemd (Ubuntu) Status: Incomplete => New ** Patch added: "245.2-1ubuntu1~rbalint1.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1867972/+attachment/5339057/+files/245.2-1ubuntu1~rbalint1.debdiff -- 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/1867972 Title: [FFe] Please accept systemd 245.2-1ubuntu1 to Focal Status in systemd package in Ubuntu: New Bug description: Focal currently has 244.3-1ubuntu1. Upstream released 245 after the Focal Feature Freeze date, but updating to v245 will allow us to carry fewer patches in Focal and have the latest upstream fixes without cherry-picking the important ones. The proposed package is tested in Bileto and there are no unfixed regressions compared to the results of the latest tests. https://bileto.ubuntu.com/#/ticket/3801 The fixed gpsd upload invalidated the default excuses page, but it is still available at: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-3801-excuses/2020-03-18_14:40:01/3801_focal_excuses.html The changelog is not final in the Bileto PPA, the final one is at: https://code.launchpad.net/~rbalint/ubuntu/+source/systemd/+git/systemd/+ref/ubuntu-focal New notable upstream features, such as systemd-homed and systemd- repart are _not_ enabled in this upload. Please find the full NEWS file at: https://github.com/systemd/systemd/blob/v245/NEWS There is one notable failing test, netplan.io's which is failing in the release pocket, too. I'd like to have this passing, too, with systemd 245 before in migrates to the release pocket. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1867972/+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
The attached patch would fix this bug. It adds two rules to skip printers. The second skips all kinds of printers by checking whether the standard interface of a printer is present in the USB device. The first skips HP printers, it is the same rule as HPLIP uses. I have added it because it covers a second interface, which is probably of some weird proprietary HP printer devices. For my printer the bug goes away with this patch, also with any one of the two rules commented out. I think one can assume that there is no printer available which doubles as a media player. ** Patch added: "69-libmtp.rules.patch" https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1863239/+attachment/5339056/+files/69-libmtp.rules.patch ** Tags added: patch -- 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: Confirmed Status in pulseaudio package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid 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
There was already a measure against wrongly identifying HP printers as media players, but it is a rather dirty workaround which does not work any more (therefore this bug). The rule in the end of 69-libmtp.rules checks the absence of the env variable libsane_matched and this variable is set for all HP printers by HPLIP. First, this rule fails miserably if HPLIP is not installed, and I cannot imagine that the libmtp package depends on HPLIP only to identify unsupported devices. Also the libmtp rules are applied for both "add" and "bind" actions, whereas the rules of HPLIP (56-hpmud.rules) are only applied for "add" and so the bug happens on a "bind" action, here the HPLIP rules do not set said env variable and so the libmtp rules probe the HP printers. One can theoretically work around this problem by mucking with the UDEV rules of HPLIP, but this is a REALLY DIRTY workaround, so please DO NOT add an hplip task to this bug report. In addition, HPLIP will not be installed by default any more in the not too far future, as prnting and scanning will get snapped. Also we want printer driver Snaps (Printer Applications) not to run as root if possible, so we need to be sure that USB printer device files always belong to the group "lp" for all printer manufacturers and without HPLIP. -- 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: Confirmed Status in pulseaudio package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid 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 1867204] Re: /usr/share/apport/whoopsie-upload-all:FileNotFoundError:/usr/share/apport/whoopsie-upload-all@170:collect_info:process_report
** Also affects: apport (Ubuntu Focal) Importance: Undecided Status: New ** Tags removed: rls-ff-incoming -- 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/1867204 Title: /usr/share/apport/whoopsie-upload- all:FileNotFoundError:/usr/share/apport/whoopsie-upload- all@170:collect_info:process_report Status in apport package in Ubuntu: New Status in apport source package in Focal: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu19, the problem page at https://errors.ubuntu.com/problem/7a3912ff155870bdb23500abfa48a21a6cb07171 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/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1867204/+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 1868164] Re: Create a general hook for subiquity
** Description changed:
Users should be able to use "ubuntu-bug subiquity" on a system which was
installed with subiquity. The hook should include code like the
following which will send the bug to the subiquity project.
- report['CrashDB'] = '''{
-"impl": "launchpad",
-"project": "cloud-archive",
-"bug_pattern_url":
"http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml;,
- }'''
+ report['CrashDB'] = '''{
+ "impl": "launchpad",
+ "project": "subiquity",
+ "bug_pattern_url":
"http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml;,
+ }'''
--
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/1868164
Title:
Create a general hook for subiquity
Status in apport package in Ubuntu:
New
Status in apport source package in Focal:
New
Bug description:
Users should be able to use "ubuntu-bug subiquity" on a system which
was installed with subiquity. The hook should include code like the
following which will send the bug to the subiquity project.
report['CrashDB'] = '''{
"impl": "launchpad",
"project": "subiquity",
"bug_pattern_url":
"http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml;,
}'''
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1868164/+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 1868131] Re: Integrated speakers always muted
*** This bug is a duplicate of bug 1310121 *** https://bugs.launchpad.net/bugs/1310121 Increasing the headphones volume in alsamixer, speakers start to sound. If I plug the headphones, it works. When unplug the headphones, alsamixer Headphones volume goes to zero and it affects speaker, because headphones volume in alsamixer control both speaker and headphones. ** Attachment added: "With volume un Headphone section in alsamixer thre're sound" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1868131/+attachment/5339031/+files/sound.png -- 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/1868131 Title: Integrated speakers always muted Status in pulseaudio package in Ubuntu: New Bug description: Speakers are muted at boot and remains muted after plug and unplug headphones. Only can be activated from alsamixer, unmuting the headphones while the headphones are unplugged. Both speakers and headphones muting seems to be controlled in the Headphones area using alsamixer. Same problem in pulseaudio 1:11.1-1ubuntu7.4 on Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic. I've "solved" it Linux Mint 19.3 Tricia in a not very good way, keeping automute activated in alsamixer, modifiyng /usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf and executing a bash script at boot (sonido.sh) with the command "amixer set -c 0 Headphone unmute 100%" in order to prevent the speakers being muted. There are some issues reported to pulseaudio manteiners. Not the same but related: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/256 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/540 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu1881 F pulseaudio CasperVersion: 1.427 CurrentDesktop: XFCE Date: Thu Mar 19 15:58:26 2020 LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.60 dmi.board.name: PAV10 DDR2 dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.60:bd07/30/2010:svnTOSHIBA:pnTOSHIBANB250:pvrPLL2XE-005003AS:rvnTOSHIBA:rnPAV10DDR2:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ dmi.product.name: TOSHIBA NB250 dmi.product.sku: 012345678912345678912345678 dmi.product.version: PLL2XE-005003AS dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1868131/+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 1868166] [NEW] Install a CMake Package configuration file for sqlite3
Public bug reported: This is a feature request for the package. It would be good if either the "sqlite3" or "sqlite3-dev" package included a CMake package config file. This would allow sqlite3 to be included in the transitive dependencies when linking with CMake. Based on a quick search the proper location would probably be /usr/lib/x86_64-linux-gnu/cmake/sqlite3 as /usr/lib/x86_64-linux-gnu/cmake has other packages (for example PulseAudio). The name of the configurationfile would have to be either sqlite3Config.cmake or sqlite3-config.cmake (the latter one looks more appropriate in this case). ** Affects: sqlite3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/1868166 Title: Install a CMake Package configuration file for sqlite3 Status in sqlite3 package in Ubuntu: New Bug description: This is a feature request for the package. It would be good if either the "sqlite3" or "sqlite3-dev" package included a CMake package config file. This would allow sqlite3 to be included in the transitive dependencies when linking with CMake. Based on a quick search the proper location would probably be /usr/lib/x86_64-linux-gnu/cmake/sqlite3 as /usr/lib/x86_64-linux-gnu/cmake has other packages (for example PulseAudio). The name of the configurationfile would have to be either sqlite3Config.cmake or sqlite3-config.cmake (the latter one looks more appropriate in this case). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/1868166/+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 1867972] Re: [FFe] Please accept systemd 245.2-1ubuntu1 to Focal
The armhf failure should probably be fixed in LXD: https://github.com/lxc/lxd/issues/7059 ** Bug watch added: LXD bug tracker #7059 https://github.com/lxc/lxd/issues/7059 -- 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/1867972 Title: [FFe] Please accept systemd 245.2-1ubuntu1 to Focal Status in systemd package in Ubuntu: Incomplete Bug description: Focal currently has 244.3-1ubuntu1. Upstream released 245 after the Focal Feature Freeze date, but updating to v245 will allow us to carry fewer patches in Focal and have the latest upstream fixes without cherry-picking the important ones. The proposed package is tested in Bileto and there are no unfixed regressions compared to the results of the latest tests. https://bileto.ubuntu.com/#/ticket/3801 The fixed gpsd upload invalidated the default excuses page, but it is still available at: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-3801-excuses/2020-03-18_14:40:01/3801_focal_excuses.html The changelog is not final in the Bileto PPA, the final one is at: https://code.launchpad.net/~rbalint/ubuntu/+source/systemd/+git/systemd/+ref/ubuntu-focal New notable upstream features, such as systemd-homed and systemd- repart are _not_ enabled in this upload. Please find the full NEWS file at: https://github.com/systemd/systemd/blob/v245/NEWS There is one notable failing test, netplan.io's which is failing in the release pocket, too. I'd like to have this passing, too, with systemd 245 before in migrates to the release pocket. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1867972/+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 1868131] Re: Integrated speakers always muted
*** This bug is a duplicate of bug 1310121 *** https://bugs.launchpad.net/bugs/1310121 Just after boot, no sound. It can't be activated using pavucontrol. Only with alsamixer. ** Attachment added: "State of alsamixer and pavucontrol on boot" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1868131/+attachment/5339029/+files/boot.png -- 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/1868131 Title: Integrated speakers always muted Status in pulseaudio package in Ubuntu: New Bug description: Speakers are muted at boot and remains muted after plug and unplug headphones. Only can be activated from alsamixer, unmuting the headphones while the headphones are unplugged. Both speakers and headphones muting seems to be controlled in the Headphones area using alsamixer. Same problem in pulseaudio 1:11.1-1ubuntu7.4 on Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic. I've "solved" it Linux Mint 19.3 Tricia in a not very good way, keeping automute activated in alsamixer, modifiyng /usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf and executing a bash script at boot (sonido.sh) with the command "amixer set -c 0 Headphone unmute 100%" in order to prevent the speakers being muted. There are some issues reported to pulseaudio manteiners. Not the same but related: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/256 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/540 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu1881 F pulseaudio CasperVersion: 1.427 CurrentDesktop: XFCE Date: Thu Mar 19 15:58:26 2020 LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.60 dmi.board.name: PAV10 DDR2 dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.60:bd07/30/2010:svnTOSHIBA:pnTOSHIBANB250:pvrPLL2XE-005003AS:rvnTOSHIBA:rnPAV10DDR2:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ dmi.product.name: TOSHIBA NB250 dmi.product.sku: 012345678912345678912345678 dmi.product.version: PLL2XE-005003AS dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1868131/+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 1868164] [NEW] Create a general hook for subiquity
Public bug reported:
Users should be able to use "ubuntu-bug subiquity" on a system which was
installed with subiquity. The hook should include code like the
following which will send the bug to the subiquity project.
report['CrashDB'] = '''{
"impl": "launchpad",
"project": "cloud-archive",
"bug_pattern_url":
"http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml;,
}'''
** Affects: apport (Ubuntu)
Importance: Undecided
Status: New
** Affects: apport (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: apport (Ubuntu Focal)
Importance: Undecided
Status: New
--
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/1868164
Title:
Create a general hook for subiquity
Status in apport package in Ubuntu:
New
Status in apport source package in Focal:
New
Bug description:
Users should be able to use "ubuntu-bug subiquity" on a system which
was installed with subiquity. The hook should include code like the
following which will send the bug to the subiquity project.
report['CrashDB'] = '''{
"impl": "launchpad",
"project": "cloud-archive",
"bug_pattern_url":
"http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml;,
}'''
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1868164/+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
** Tags added: 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/1863239 Title: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group Status in libmtp package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid 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 1814611] Autopkgtest regression report (apport/2.20.9-0ubuntu7.13)
All autopkgtests for the newly accepted apport (2.20.9-0ubuntu7.13) for bionic have finished running. The following regressions have been reported in tests triggered by the package: apport/2.20.9-0ubuntu7.13 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#apport [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1814611 Title: turning off "Send error reports to Canonical" prevents using ubuntu- bug Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: Fix Committed Status in apport source package in Disco: Won't Fix Status in apport source package in Eoan: Fix Committed Bug description: Impact -- apport was modified (bug 1778497) to reduce the number of times people have to respond to crash reports, however the changes introduced a check to see if whoopsie is enabled. That check is done for any type of report, not just crashes, and subsequently people can not use ubuntu-bug to report bugs if whoopsie is disabled which is wrong as whoopsie is only for uploading crashes to the Error Tracker. Test Case - 1) On a system with Gnome installed use the Privacy control panel and set "Send error reports to Canonical" to Off 2) In a terminal run 'ubuntu-bug gnome-terminal' 3) Click "Send" and observe nothing happening (if something does happen confirm that whoopsie is disabled via 'systemctl is-enabled whoopsie' - there may be a bug in the control panel) Regression Potential The fix is just setting the value of a variable to True instead of checking to see if whoopsie is enabled so there really isn't any. However, it could cause a regression if there's a typo in the line being changed. Original Description Ubuntu 18.04.1 LTS, X11 gnome session. For some reason ubuntu-bug no longer opens a browser window, so it is not possible to enter useful bug detauls, or even know the bug number. After prompting whether or not to Send the report, clicking "Send" just closes appport and nothing else ever happens. The exit status of "ubuntu-bug" is zero. This worked fine before, but it has been many months since I tried to submit a bug. strace shows many stat calls on plausible browser paths, including the one that is correct (/usr/bin/firefox, which returned a successful stat call). I'll attach the trace output from strace -f -o /tmp/strace.log ubuntu-bug apport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814611/+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
Now I tried to investigate from which UDEV rule the wrong setting comes
from. First I searched all UDEV rules for the word "audio":
till@till-x1yoga:~$ grep -l '\baudio\b' /*/udev/rules.d/*.rules
/lib/udev/rules.d/50-udev-default.rules
/lib/udev/rules.d/60-persistent-v4l.rules
/lib/udev/rules.d/69-libmtp.rules
/lib/udev/rules.d/70-uaccess.rules
/lib/udev/rules.d/90-pulseaudio.rules
till@till-x1yoga:~$
So I expect only one of these can be the culprit. Actually a 'GROUP="audio"'
setting exists only in
/lib/udev/rules.d/50-udev-default.rules
and
/lib/udev/rules.d/69-libmtp.rules
The former is probably no problem as it assigns this group only to
devices of 'SUBSYSTEM=="sound"" where the latter seems to be actually
the culprit.
First it includes some devices explicitly and then it lists thousands of
supported devices. In the end there is some rule for passing a wide
range of devices through an auto-probing:
-
# Autoprobe vendor-specific, communication and PTP devices
ENV{ID_MTP_DEVICE}!="1", ENV{MTP_NO_PROBE}!="1",
ENV{COLOR_MEASUREMENT_DEVICE}!="1", ENV{ID_GPHOTO}!="1",
ENV{libsane_matched}!="yes", ATTR{bDeviceClass}=="00|02|06|ef|ff",
PROGRAM="mtp-probe /sys$env{DEVPATH} $attr{busnum} $attr{devnum}", RESULT=="1",
SYMLINK+="libmtp-%k", MODE="660", GROUP="audio", ENV{ID_MTP_DEVICE}="1",
ENV{ID_MEDIA_PLAYER}="1"
-
And this auto-probing tests positive on my printer:
till@till-x1yoga:~$ /lib/udev/mtp-probe
/sys/devices/pci:00/:00:14.0/usb1/1-1 001 012
1
till@till-x1yoga:~$
The device path of the printer I have taken from the blob in the udevadm
output (attached to previous comment) which also contains
"ID_MEDIA_PLAYER=1". So mtp-probe identifies my printer as a media
player and assigns the device file to the "audio" group.
I assume that this happens to most or even all HP printers, so an
exclusion of only my device via Vendor and Product ID would not be the
correct solution.
Either mtp-probe needs to get fixed or before said rule in the end of
the 69-libmtp.rules file and after the lines explicitly identifying
media players from HP, there should be placed a line to exclude further
HP devices, like
--
...
# Exclude any further, not explicitly specified HP devices
ATTR{idVendor}=="03f0", GOTO="libmtp_rules_end"
# Autoprobe vendor-specific, communication and PTP devices
ENV{ID_MTP_DEVICE}!="1", ENV{MTP_NO_PROBE}!="1",
ENV{COLOR_MEASUREMENT_DEVICE}!="1", ENV{ID_GPHOTO}!="1",
ENV{libsane_matched}!="yes", ATTR{bDeviceClass}=="00|02|06|ef|ff",
PROGRAM="mtp-probe /sys$env{DEVPATH} $attr{busnum} $attr{devnum}", RESULT=="1",
SYMLINK+="libmtp-%k", MODE="660", GROUP="audio", ENV{ID_MTP_DEVICE}="1",
ENV{ID_MEDIA_PLAYER}="1"
LABEL="libmtp_rules_end"
--
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
** Changed in: libmtp (Ubuntu)
Status: New => Confirmed
--
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:
Confirmed
Status in pulseaudio package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Invalid
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
[Touch-packages] [Bug 1814611] Re: turning off "Send error reports to Canonical" prevents using ubuntu-bug
On an Ubuntu 19.10 system I installed the version of apport from eoan- proposed and I was able to report a bug to Launchpad about gnome- terminal, as such I'm setting this to verification-done for eoan. bdmurray@clean-eoan-amd64:~$ apt-cache policy python3-apport python3-apport: Installed: 2.20.11-0ubuntu8.7 Candidate: 2.20.11-0ubuntu8.7 Version table: *** 2.20.11-0ubuntu8.7 500 500 http://archive.ubuntu.com/ubuntu eoan-proposed/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu eoan-proposed/main i386 Packages ** 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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1814611 Title: turning off "Send error reports to Canonical" prevents using ubuntu- bug Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: Fix Committed Status in apport source package in Disco: Won't Fix Status in apport source package in Eoan: Fix Committed Bug description: Impact -- apport was modified (bug 1778497) to reduce the number of times people have to respond to crash reports, however the changes introduced a check to see if whoopsie is enabled. That check is done for any type of report, not just crashes, and subsequently people can not use ubuntu-bug to report bugs if whoopsie is disabled which is wrong as whoopsie is only for uploading crashes to the Error Tracker. Test Case - 1) On a system with Gnome installed use the Privacy control panel and set "Send error reports to Canonical" to Off 2) In a terminal run 'ubuntu-bug gnome-terminal' 3) Click "Send" and observe nothing happening (if something does happen confirm that whoopsie is disabled via 'systemctl is-enabled whoopsie' - there may be a bug in the control panel) Regression Potential The fix is just setting the value of a variable to True instead of checking to see if whoopsie is enabled so there really isn't any. However, it could cause a regression if there's a typo in the line being changed. Original Description Ubuntu 18.04.1 LTS, X11 gnome session. For some reason ubuntu-bug no longer opens a browser window, so it is not possible to enter useful bug detauls, or even know the bug number. After prompting whether or not to Send the report, clicking "Send" just closes appport and nothing else ever happens. The exit status of "ubuntu-bug" is zero. This worked fine before, but it has been many months since I tried to submit a bug. strace shows many stat calls on plausible browser paths, including the one that is correct (/usr/bin/firefox, which returned a successful stat call). I'll attach the trace output from strace -f -o /tmp/strace.log ubuntu-bug apport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814611/+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
Attached is the output of sudo udevadm monitor -e Output of lsusb: till@till-x1yoga:~$ 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 012: 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:~$ Device is on Bus 001, Device 012, the HP OfficeJet Pro 8730 Here one sees that it is assigned to the "audio" group: till@till-x1yoga:~$ ls -l /dev/bus/usb/*/* crw-rw-r-- 1 root root189, 0 Mar 17 11:45 /dev/bus/usb/001/001 crw-rw-r-- 1 root root189, 2 Mar 17 11:45 /dev/bus/usb/001/003 crw-rw-r-- 1 root root189, 3 Mar 17 11:45 /dev/bus/usb/001/004 crw-rw 1 root plugdev 189, 4 Mar 18 14:04 /dev/bus/usb/001/005 crw-rw-r-- 1 root root189, 5 Mar 17 11:45 /dev/bus/usb/001/006 crw-rw+ 1 root audio 189, 11 Mar 19 18:55 /dev/bus/usb/001/012 crw-rw-r-- 1 root root189, 128 Mar 17 11:45 /dev/bus/usb/002/001 crw-rw-r-- 1 root root189, 130 Mar 17 11:45 /dev/bus/usb/002/003 till@till-x1yoga:~$ ** Attachment added: "udevadm-monitor-e-plug-hp-officejet-pro-8730-20200319-log.txt" https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1863239/+attachment/5338953/+files/udevadm-monitor-e-plug-hp-officejet-pro-8730-20200319-log.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/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 1867972] Re: [FFe] Please accept systemd 245.2-1ubuntu1 to Focal
@vorlon the armhf autopkgtest was failing due to being in a container, will fix that soon, too. -- 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/1867972 Title: [FFe] Please accept systemd 245.2-1ubuntu1 to Focal Status in systemd package in Ubuntu: Incomplete Bug description: Focal currently has 244.3-1ubuntu1. Upstream released 245 after the Focal Feature Freeze date, but updating to v245 will allow us to carry fewer patches in Focal and have the latest upstream fixes without cherry-picking the important ones. The proposed package is tested in Bileto and there are no unfixed regressions compared to the results of the latest tests. https://bileto.ubuntu.com/#/ticket/3801 The fixed gpsd upload invalidated the default excuses page, but it is still available at: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-3801-excuses/2020-03-18_14:40:01/3801_focal_excuses.html The changelog is not final in the Bileto PPA, the final one is at: https://code.launchpad.net/~rbalint/ubuntu/+source/systemd/+git/systemd/+ref/ubuntu-focal New notable upstream features, such as systemd-homed and systemd- repart are _not_ enabled in this upload. Please find the full NEWS file at: https://github.com/systemd/systemd/blob/v245/NEWS There is one notable failing test, netplan.io's which is failing in the release pocket, too. I'd like to have this passing, too, with systemd 245 before in migrates to the release pocket. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1867972/+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 1814611] Re: turning off "Send error reports to Canonical" prevents using ubuntu-bug
I installed the version of apport from bionic-proposed and was able to report a bug to Launchpad about gnome-terminal, so I'm setting this to verification-done for bionic. bdmurray@clean-bionic-amd64:~$ apt-cache policy apport apport: Installed: 2.20.9-0ubuntu7.12 Candidate: 2.20.9-0ubuntu7.13 Version table: 2.20.9-0ubuntu7.13 500 500 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic-proposed/main i386 Packages ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1814611 Title: turning off "Send error reports to Canonical" prevents using ubuntu- bug Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: Fix Committed Status in apport source package in Disco: Won't Fix Status in apport source package in Eoan: Fix Committed Bug description: Impact -- apport was modified (bug 1778497) to reduce the number of times people have to respond to crash reports, however the changes introduced a check to see if whoopsie is enabled. That check is done for any type of report, not just crashes, and subsequently people can not use ubuntu-bug to report bugs if whoopsie is disabled which is wrong as whoopsie is only for uploading crashes to the Error Tracker. Test Case - 1) On a system with Gnome installed use the Privacy control panel and set "Send error reports to Canonical" to Off 2) In a terminal run 'ubuntu-bug gnome-terminal' 3) Click "Send" and observe nothing happening (if something does happen confirm that whoopsie is disabled via 'systemctl is-enabled whoopsie' - there may be a bug in the control panel) Regression Potential The fix is just setting the value of a variable to True instead of checking to see if whoopsie is enabled so there really isn't any. However, it could cause a regression if there's a typo in the line being changed. Original Description Ubuntu 18.04.1 LTS, X11 gnome session. For some reason ubuntu-bug no longer opens a browser window, so it is not possible to enter useful bug detauls, or even know the bug number. After prompting whether or not to Send the report, clicking "Send" just closes appport and nothing else ever happens. The exit status of "ubuntu-bug" is zero. This worked fine before, but it has been many months since I tried to submit a bug. strace shows many stat calls on plausible browser paths, including the one that is correct (/usr/bin/firefox, which returned a successful stat call). I'll attach the trace output from strace -f -o /tmp/strace.log ubuntu-bug apport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814611/+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 1867972] Re: [FFe] Please accept systemd 245.2-1ubuntu1 to Focal
@vorlon I've also merged 245.2 and it is building and will be autopkgtested in Bileto soon. ** Summary changed: - [FFe] Please accept systemd 245-2ubuntu1 to Focal + [FFe] Please accept systemd 245.2-1ubuntu1 to Focal -- 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/1867972 Title: [FFe] Please accept systemd 245.2-1ubuntu1 to Focal Status in systemd package in Ubuntu: Incomplete Bug description: Focal currently has 244.3-1ubuntu1. Upstream released 245 after the Focal Feature Freeze date, but updating to v245 will allow us to carry fewer patches in Focal and have the latest upstream fixes without cherry-picking the important ones. The proposed package is tested in Bileto and there are no unfixed regressions compared to the results of the latest tests. https://bileto.ubuntu.com/#/ticket/3801 The fixed gpsd upload invalidated the default excuses page, but it is still available at: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-3801-excuses/2020-03-18_14:40:01/3801_focal_excuses.html The changelog is not final in the Bileto PPA, the final one is at: https://code.launchpad.net/~rbalint/ubuntu/+source/systemd/+git/systemd/+ref/ubuntu-focal New notable upstream features, such as systemd-homed and systemd- repart are _not_ enabled in this upload. Please find the full NEWS file at: https://github.com/systemd/systemd/blob/v245/NEWS There is one notable failing test, netplan.io's which is failing in the release pocket, too. I'd like to have this passing, too, with systemd 245 before in migrates to the release pocket. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1867972/+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 1867972] Re: [FFe] Please accept systemd 245-2ubuntu1 to Focal
@vorlon I have installed focal with ZFS as root in a VM and it rebooted fine to 245-2ubuntu1~rbalint1, thus this regression does affect us (with the default config). I'll propose a fix for the usernames starting with a digit regression and IMO this could go in a further upload. -- 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/1867972 Title: [FFe] Please accept systemd 245.2-1ubuntu1 to Focal Status in systemd package in Ubuntu: Incomplete Bug description: Focal currently has 244.3-1ubuntu1. Upstream released 245 after the Focal Feature Freeze date, but updating to v245 will allow us to carry fewer patches in Focal and have the latest upstream fixes without cherry-picking the important ones. The proposed package is tested in Bileto and there are no unfixed regressions compared to the results of the latest tests. https://bileto.ubuntu.com/#/ticket/3801 The fixed gpsd upload invalidated the default excuses page, but it is still available at: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-3801-excuses/2020-03-18_14:40:01/3801_focal_excuses.html The changelog is not final in the Bileto PPA, the final one is at: https://code.launchpad.net/~rbalint/ubuntu/+source/systemd/+git/systemd/+ref/ubuntu-focal New notable upstream features, such as systemd-homed and systemd- repart are _not_ enabled in this upload. Please find the full NEWS file at: https://github.com/systemd/systemd/blob/v245/NEWS There is one notable failing test, netplan.io's which is failing in the release pocket, too. I'd like to have this passing, too, with systemd 245 before in migrates to the release pocket. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1867972/+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 1867943] Re: Nautilus “Open Other Application” problem
** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu) ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1867943 Title: Nautilus “Open Other Application” problem Status in gtk+3.0 package in Ubuntu: New Bug description: When using Nautilus and I right click on an image file I get a drop down menu, the first two items are “Open With *Default application*” and “Open With Other Application”. I use Mirage as my default application for image files. On one account when I right click on an image file and choose “Open With Other Application”, Mirage is the preselected application not “Image Viewer” which is my usual second choice. On another account Mirage isn’t preselected, “Image Viewer” is. This is the expected behavior. I used the "Properties"->"Open With" to select “Image Viewer” and set it as the default. But that didn't work, it went back to Mirage as the default. I tried setting other programs as the default the same way and none stuck, it always returned to Mirage. I went to Settings->Details->Default Applications and changed the “Photos” from Mirage to “Image Viewer”. That worked and when right clicking and selecting “Other Application” Mirage is preselected. As expected. When I changed Settings->Details->Default Applications->“Photos” back to Mirage the problem returned. Mirage is the default and the preselected “Other Application”. “Right click on an image file and select : 'Open With Other Application' Then right click on the application that you do not want to be on that menu. Click on 'Forget association'”. Worked on other programs but not on Mirage. Description: Ubuntu 18.04 LTS (beaver-osha X84) Release: 18.04 Nautilus 1:3.26.4-0~ubuntu18.04.5 (from Software center) I expected Image Viewer to be the preselected Other Application. I got Mirage as the default application and the preselected “Other Application” I expected Mirage to be removed from the list when I clicked on “Forget association” What I got was Mirage would not go gently into the night I expected Mirage to accept not being the default application when using "Properties"->"Open With" to chose another application as the default. What I got was Mirage remaining the default. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.5 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 Uname: Linux 4.15.0-1073-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 18 11:21:53 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-osha+X84 InstallationDate: Installed on 2019-11-28 (111 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1867943/+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 1867943] [NEW] Nautilus “Open Other Application” problem
You have been subscribed to a public bug: When using Nautilus and I right click on an image file I get a drop down menu, the first two items are “Open With *Default application*” and “Open With Other Application”. I use Mirage as my default application for image files. On one account when I right click on an image file and choose “Open With Other Application”, Mirage is the preselected application not “Image Viewer” which is my usual second choice. On another account Mirage isn’t preselected, “Image Viewer” is. This is the expected behavior. I used the "Properties"->"Open With" to select “Image Viewer” and set it as the default. But that didn't work, it went back to Mirage as the default. I tried setting other programs as the default the same way and none stuck, it always returned to Mirage. I went to Settings->Details->Default Applications and changed the “Photos” from Mirage to “Image Viewer”. That worked and when right clicking and selecting “Other Application” Mirage is preselected. As expected. When I changed Settings->Details->Default Applications->“Photos” back to Mirage the problem returned. Mirage is the default and the preselected “Other Application”. “Right click on an image file and select : 'Open With Other Application' Then right click on the application that you do not want to be on that menu. Click on 'Forget association'”. Worked on other programs but not on Mirage. Description:Ubuntu 18.04 LTS (beaver-osha X84) Release:18.04 Nautilus 1:3.26.4-0~ubuntu18.04.5 (from Software center) I expected Image Viewer to be the preselected Other Application. I got Mirage as the default application and the preselected “Other Application” I expected Mirage to be removed from the list when I clicked on “Forget association” What I got was Mirage would not go gently into the night I expected Mirage to accept not being the default application when using "Properties"->"Open With" to chose another application as the default. What I got was Mirage remaining the default. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.5 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 Uname: Linux 4.15.0-1073-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 18 11:21:53 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-osha+X84 InstallationDate: Installed on 2019-11-28 (111 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: gtk+3.0 (Ubuntu) Importance: Low Status: New ** Tags: amd64 apport-bug bionic -- Nautilus “Open Other Application” problem https://bugs.launchpad.net/bugs/1867943 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 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 1868131] Re: Integrated speakers always muted
*** This bug is a duplicate of bug 1310121 *** https://bugs.launchpad.net/bugs/1310121 It is a duplicate of bug #1310121, unsolved from 2014, but administrators closed it. Daniel van Vugt (vanvugt) wrote 10 hours ago: #9 Everyone please report your own new bugs by running: ubuntu-bug pulseaudio This bug is closed. -- 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/1868131 Title: Integrated speakers always muted Status in pulseaudio package in Ubuntu: New Bug description: Speakers are muted at boot and remains muted after plug and unplug headphones. Only can be activated from alsamixer, unmuting the headphones while the headphones are unplugged. Both speakers and headphones muting seems to be controlled in the Headphones area using alsamixer. Same problem in pulseaudio 1:11.1-1ubuntu7.4 on Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic. I've "solved" it Linux Mint 19.3 Tricia in a not very good way, keeping automute activated in alsamixer, modifiyng /usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf and executing a bash script at boot (sonido.sh) with the command "amixer set -c 0 Headphone unmute 100%" in order to prevent the speakers being muted. There are some issues reported to pulseaudio manteiners. Not the same but related: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/256 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/540 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu1881 F pulseaudio CasperVersion: 1.427 CurrentDesktop: XFCE Date: Thu Mar 19 15:58:26 2020 LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.60 dmi.board.name: PAV10 DDR2 dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.60:bd07/30/2010:svnTOSHIBA:pnTOSHIBANB250:pvrPLL2XE-005003AS:rvnTOSHIBA:rnPAV10DDR2:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ dmi.product.name: TOSHIBA NB250 dmi.product.sku: 012345678912345678912345678 dmi.product.version: PLL2XE-005003AS dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1868131/+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 1868131] [NEW] Integrated speakers always muted
*** This bug is a duplicate of bug 1310121 *** https://bugs.launchpad.net/bugs/1310121 Public bug reported: Speakers are muted at boot and remains muted after plug and unplug headphones. Only can be activated from alsamixer, unmuting the headphones while the headphones are unplugged. Both speakers and headphones muting seems to be controlled in the Headphones area using alsamixer. Same problem in pulseaudio 1:11.1-1ubuntu7.4 on Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic. I've "solved" it Linux Mint 19.3 Tricia in a not very good way, keeping automute activated in alsamixer, modifiyng /usr/share/pulseaudio/alsa- mixer/paths/analog-output-headphones.conf and executing a bash script at boot (sonido.sh) with the command "amixer set -c 0 Headphone unmute 100%" in order to prevent the speakers being muted. There are some issues reported to pulseaudio manteiners. Not the same but related: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/256 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/540 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu1881 F pulseaudio CasperVersion: 1.427 CurrentDesktop: XFCE Date: Thu Mar 19 15:58:26 2020 LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.60 dmi.board.name: PAV10 DDR2 dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.60:bd07/30/2010:svnTOSHIBA:pnTOSHIBANB250:pvrPLL2XE-005003AS:rvnTOSHIBA:rnPAV10DDR2:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ dmi.product.name: TOSHIBA NB250 dmi.product.sku: 012345678912345678912345678 dmi.product.version: PLL2XE-005003AS dmi.sys.vendor: TOSHIBA ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "analog-output-headphones.conf" https://bugs.launchpad.net/bugs/1868131/+attachment/5338919/+files/analog-output-headphones.conf ** This bug has been marked a duplicate of bug 1310121 headphones working while speakers not working -- 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/1868131 Title: Integrated speakers always muted Status in pulseaudio package in Ubuntu: New Bug description: Speakers are muted at boot and remains muted after plug and unplug headphones. Only can be activated from alsamixer, unmuting the headphones while the headphones are unplugged. Both speakers and headphones muting seems to be controlled in the Headphones area using alsamixer. Same problem in pulseaudio 1:11.1-1ubuntu7.4 on Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic. I've "solved" it Linux Mint 19.3 Tricia in a not very good way, keeping automute activated in alsamixer, modifiyng /usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf and executing a bash script at boot (sonido.sh) with the command "amixer set -c 0 Headphone unmute 100%" in order to prevent the speakers being muted. There are some issues reported to pulseaudio manteiners. Not the same but related: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/256 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/540 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu1881 F pulseaudio CasperVersion: 1.427 CurrentDesktop: XFCE Date: Thu Mar 19 15:58:26 2020 LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.60 dmi.board.name: PAV10 DDR2 dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.60:bd07/30/2010:svnTOSHIBA:pnTOSHIBANB250:pvrPLL2XE-005003AS:rvnTOSHIBA:rnPAV10DDR2:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.family:
[Touch-packages] [Bug 1868128] [NEW] (Error ID: OOPS-f9a25a1047f367bba335ebdf6c9c0a24)
Public bug reported: trying to reinstall my Ubuntu 18.04 on my Toshiba Satelite 64 bus laptop. I have a loaded flash drive but I keep getting an error message as follows, (Error ID: OOPS-f9a25a1047f367bba335ebdf6c9c0a24) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Mar 19 08:43:35 2020 DistUpgraded: 2018-09-05 15:50:48,221 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems 4th Gen Core Processor Integrated Graphics Controller [1179:fa22] InstallationDate: Installed on 2017-04-18 (1065 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: TOSHIBA Satellite C55t-A ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic root=UUID=1be49583-6218-4da2-9204-c5ae2ac5cebd ro drm.debug=0xe plymouth:debug Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-05 (560 days ago) dmi.bios.date: 01/24/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.70 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.70:bd01/24/2014:svnTOSHIBA:pnSatelliteC55t-A:pvrPSCFJU-00T00J:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Durban-Curiosity 10S/10SG dmi.product.name: Satellite C55t-A dmi.product.version: PSCFJU-00T00J dmi.sys.vendor: TOSHIBA 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 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Jun 27 12:22:02 2017 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages 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/1868128 Title: (Error ID: OOPS-f9a25a1047f367bba335ebdf6c9c0a24) Status in xorg package in Ubuntu: New Bug description: trying to reinstall my Ubuntu 18.04 on my Toshiba Satelite 64 bus laptop. I have a loaded flash drive but I keep getting an error message as follows, (Error ID: OOPS-f9a25a1047f367bba335ebdf6c9c0a24) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Mar 19 08:43:35 2020 DistUpgraded: 2018-09-05 15:50:48,221 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems 4th Gen Core Processor Integrated Graphics Controller [1179:fa22] InstallationDate: Installed on 2017-04-18 (1065 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: TOSHIBA Satellite C55t-A ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic root=UUID=1be49583-6218-4da2-9204-c5ae2ac5cebd ro drm.debug=0xe plymouth:debug Renderer: Software SourcePackage:
[Touch-packages] [Bug 1868129] [NEW] I can't attach a writecache to LV
Public bug reported:
#lvconvert --type writecache --cachesettings 'low_watermark=0 high_watermark=10
writeback_jobs=2048' --cachevol cache ssd/data
WARNING: Unrecognised segment type writecache
Invalid argument for --type: writecache
Error during parsing of command line.
I see that lvm2 package was build without key --with-writecache=internal
#lvm version
LVM version: 2.03.07(2) (2019-11-30)
Library version: 1.02.167 (2019-11-30)
Driver version: 4.41.0
Configuration: ./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=${prefix}/include --mandir=${prefix}/share/man
--infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-silent-rules --libdir=${prefix}/lib/x86_64-linux-gnu
--libexecdir=${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking --exec-prefix=
--bindir=/bin --libdir=/lib/x86_64-linux-gnu --sbindir=/sbin
--with-usrlibdir=/usr/lib/x86_64-linux-gnu --with-optimisation=-O2
--with-cache=internal --with-device-uid=0 --with-device-gid=6
--with-device-mode=0660 --with-default-pid-dir=/run
--with-default-run-dir=/run/lvm --with-default-locking-dir=/run/lock/lvm
--with-thin=internal --with-thin-check=/usr/sbin/thin_check
--with-thin-dump=/usr/sbin/thin_dump --with-thin-repair=/usr/sbin/thin_repair
--enable-applib --enable-blkid_wiping --enable-cmdlib --enable-dmeventd
--enable-dbus-service --enable-lvmlockd-dlm --enable-lvmlockd-sanlock
--enable-lvmpolld --enable-notify-dbus --enable-pkgconfig --enable-readline
--enable-udev_rules --enable-udev_sync
# lsmod | grep dm_writecache
dm_writecache 36864 0
#cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu Focal Fossa (development branch)"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
#uname -a
Linux sw-sed-ubuntu 5.4.0-18-generic #22-Ubuntu SMP Sat Mar 7 18:13:06 UTC 2020
x86_64 x86_64 x86_64 GNU/Linux
#apt info lvm2
Package: lvm2
Version: 2.03.07-1ubuntu1
Priority: optional
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: lvm2 2.03.07-1ubuntu1
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
Date: Thu Mar 19 16:06:17 2020
InstallationDate: Installed on 2020-03-19 (0 days ago)
InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64
(20200317)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: lvm2
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: lvm2 (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal uec-images
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1868129
Title:
I can't attach a writecache to LV
Status in lvm2 package in Ubuntu:
New
Bug description:
#lvconvert --type writecache --cachesettings 'low_watermark=0
high_watermark=10 writeback_jobs=2048' --cachevol cache ssd/data
WARNING: Unrecognised segment type writecache
Invalid argument for --type: writecache
Error during parsing of command line.
I see that lvm2 package was build without key --with-
writecache=internal
#lvm version
LVM version: 2.03.07(2) (2019-11-30)
Library version: 1.02.167 (2019-11-30)
Driver version: 4.41.0
Configuration: ./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=${prefix}/include --mandir=${prefix}/share/man
--infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-silent-rules --libdir=${prefix}/lib/x86_64-linux-gnu
--libexecdir=${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking --exec-prefix=
--bindir=/bin --libdir=/lib/x86_64-linux-gnu --sbindir=/sbin
--with-usrlibdir=/usr/lib/x86_64-linux-gnu --with-optimisation=-O2
--with-cache=internal --with-device-uid=0 --with-device-gid=6
--with-device-mode=0660 --with-default-pid-dir=/run
--with-default-run-dir=/run/lvm --with-default-locking-dir=/run/lock/lvm
--with-thin=internal --with-thin-check=/usr/sbin/thin_check
--with-thin-dump=/usr/sbin/thin_dump --with-thin-repair=/usr/sbin/thin_repair
--enable-applib --enable-blkid_wiping --enable-cmdlib --enable-dmeventd
--enable-dbus-service --enable-lvmlockd-dlm --enable-lvmlockd-sanlock
--enable-lvmpolld --enable-notify-dbus --enable-pkgconfig --enable-readline
--enable-udev_rules --enable-udev_sync
# lsmod | grep dm_writecache
dm_writecache 36864 0
#cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
[Touch-packages] [Bug 1814611] Re: turning off "Send error reports to Canonical" prevents using ubuntu-bug
Hello jimav, or anyone else affected, Accepted apport into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apport/2.20.9-0ubuntu7.13 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apport (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- 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/1814611 Title: turning off "Send error reports to Canonical" prevents using ubuntu- bug Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: Fix Committed Status in apport source package in Disco: Won't Fix Status in apport source package in Eoan: Fix Committed Bug description: Impact -- apport was modified (bug 1778497) to reduce the number of times people have to respond to crash reports, however the changes introduced a check to see if whoopsie is enabled. That check is done for any type of report, not just crashes, and subsequently people can not use ubuntu-bug to report bugs if whoopsie is disabled which is wrong as whoopsie is only for uploading crashes to the Error Tracker. Test Case - 1) On a system with Gnome installed use the Privacy control panel and set "Send error reports to Canonical" to Off 2) In a terminal run 'ubuntu-bug gnome-terminal' 3) Click "Send" and observe nothing happening (if something does happen confirm that whoopsie is disabled via 'systemctl is-enabled whoopsie' - there may be a bug in the control panel) Regression Potential The fix is just setting the value of a variable to True instead of checking to see if whoopsie is enabled so there really isn't any. However, it could cause a regression if there's a typo in the line being changed. Original Description Ubuntu 18.04.1 LTS, X11 gnome session. For some reason ubuntu-bug no longer opens a browser window, so it is not possible to enter useful bug detauls, or even know the bug number. After prompting whether or not to Send the report, clicking "Send" just closes appport and nothing else ever happens. The exit status of "ubuntu-bug" is zero. This worked fine before, but it has been many months since I tried to submit a bug. strace shows many stat calls on plausible browser paths, including the one that is correct (/usr/bin/firefox, which returned a successful stat call). I'll attach the trace output from strace -f -o /tmp/strace.log ubuntu-bug apport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814611/+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 1867474] Re: [Dell Vostro 5590] PCI/internal sound card not detected
I installed kernel 5.3.0-050300 and sound and microphone works fine: Linux G3-3590 5.3.0-050300-generic #201909152230 SMP Sun Sep 15 22:32:54 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I'm using Ubuntu 18.04.04 on Dell G3 3590-A20P. -- 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/1867474 Title: [Dell Vostro 5590] PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: Problem with detecting audio input/output device. Device: Dell Vostro 5590 Tested earlier also on Ubuntu 18.04 and 19.10. On older systems with some configurations output device was working, but I never succeeded making build-in microphone to work (be properly detected). On current Ubuntu 20.04 (14.03.2020) both input and output audio devices are not visible at all. Devices are work without any issues on Windows 10 originally installed on the device. Let me know if I can provide any additional information that will help solving the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 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 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 23:45:55 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) 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: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 051P23 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn051P23:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5590 dmi.product.sku: 095A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867474/+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 1861082] Re: ubuntu-bug doesn't know how to file bugs against snaps
So, in addition to the contact: field on all seeded snaps / canonical snaps. Re: installers We generally do have special cases in ubuntu-bug for "debian-installer", "ubiquity", and "subiquity", as anybody should be able file bug reports against "installation". Whether or not, they are installing or completed the install. That needs more special cases in apport. For snaps that don't declare contact Maybe we should direct people at the snapstore URL to try to find who published the package there? Or like direct them at "snaps-on-ubuntu" project that has lots of bugs against any snap out there? I wonder how other distributions handle the "where to file bugs against snaps on $DISTRO". -- 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/1861082 Title: ubuntu-bug doesn't know how to file bugs against snaps Status in Snapcraft: New Status in snapd: Triaged Status in Snap Store: New Status in apport package in Ubuntu: Incomplete Bug description: Hello, I had problems with subiquity in the focal live server install image. I tried to use 'ubuntu-bug subiquity' to report the bug, but ubuntu-bug apparently cannot file bug reports against snaps. This is frustrating that users need to know which portions of Ubuntu are delivered via debs, which portions are delivered by snaps, and try to find a way to report bugs correctly. ubuntu-bug should know how to report bugs for Canonical software. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/snapcraft/+bug/1861082/+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 1814611] Re: turning off "Send error reports to Canonical" prevents using ubuntu-bug
Hello jimav, or anyone else affected, Accepted apport into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apport/2.20.11-0ubuntu8.7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apport (Ubuntu Eoan) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-eoan -- 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/1814611 Title: turning off "Send error reports to Canonical" prevents using ubuntu- bug Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: In Progress Status in apport source package in Disco: Won't Fix Status in apport source package in Eoan: Fix Committed Bug description: Impact -- apport was modified (bug 1778497) to reduce the number of times people have to respond to crash reports, however the changes introduced a check to see if whoopsie is enabled. That check is done for any type of report, not just crashes, and subsequently people can not use ubuntu-bug to report bugs if whoopsie is disabled which is wrong as whoopsie is only for uploading crashes to the Error Tracker. Test Case - 1) On a system with Gnome installed use the Privacy control panel and set "Send error reports to Canonical" to Off 2) In a terminal run 'ubuntu-bug gnome-terminal' 3) Click "Send" and observe nothing happening (if something does happen confirm that whoopsie is disabled via 'systemctl is-enabled whoopsie' - there may be a bug in the control panel) Regression Potential The fix is just setting the value of a variable to True instead of checking to see if whoopsie is enabled so there really isn't any. However, it could cause a regression if there's a typo in the line being changed. Original Description Ubuntu 18.04.1 LTS, X11 gnome session. For some reason ubuntu-bug no longer opens a browser window, so it is not possible to enter useful bug detauls, or even know the bug number. After prompting whether or not to Send the report, clicking "Send" just closes appport and nothing else ever happens. The exit status of "ubuntu-bug" is zero. This worked fine before, but it has been many months since I tried to submit a bug. strace shows many stat calls on plausible browser paths, including the one that is correct (/usr/bin/firefox, which returned a successful stat call). I'll attach the trace output from strace -f -o /tmp/strace.log ubuntu-bug apport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814611/+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 1867474] Re: [Dell Vostro 5590] PCI/internal sound card not detected
I have the same problem with Dell G3-3590-A20P after upgraded kernel to 5.3.0-42. Does anyone have updates about this? -- 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/1867474 Title: [Dell Vostro 5590] PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: Problem with detecting audio input/output device. Device: Dell Vostro 5590 Tested earlier also on Ubuntu 18.04 and 19.10. On older systems with some configurations output device was working, but I never succeeded making build-in microphone to work (be properly detected). On current Ubuntu 20.04 (14.03.2020) both input and output audio devices are not visible at all. Devices are work without any issues on Windows 10 originally installed on the device. Let me know if I can provide any additional information that will help solving the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 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 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 23:45:55 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) 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: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 051P23 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn051P23:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5590 dmi.product.sku: 095A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867474/+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 1867972] Re: [FFe] Please accept systemd 245-2ubuntu1 to Focal
@vorlon Thanks, please see the debdiff attached. Debian moved to the latest point release, 245.2, I'd like to give a round of testing to that one and upload this one to Focal. ** Patch added: "debdiff for 245-2ubuntu1~rbalint1" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1867972/+attachment/5338808/+files/245-2ubuntu1~rbalint1.debdiff -- 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/1867972 Title: [FFe] Please accept systemd 245-2ubuntu1 to Focal Status in systemd package in Ubuntu: Incomplete Bug description: Focal currently has 244.3-1ubuntu1. Upstream released 245 after the Focal Feature Freeze date, but updating to v245 will allow us to carry fewer patches in Focal and have the latest upstream fixes without cherry-picking the important ones. The proposed package is tested in Bileto and there are no unfixed regressions compared to the results of the latest tests. https://bileto.ubuntu.com/#/ticket/3801 The fixed gpsd upload invalidated the default excuses page, but it is still available at: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-3801-excuses/2020-03-18_14:40:01/3801_focal_excuses.html The changelog is not final in the Bileto PPA, the final one is at: https://code.launchpad.net/~rbalint/ubuntu/+source/systemd/+git/systemd/+ref/ubuntu-focal New notable upstream features, such as systemd-homed and systemd- repart are _not_ enabled in this upload. Please find the full NEWS file at: https://github.com/systemd/systemd/blob/v245/NEWS There is one notable failing test, netplan.io's which is failing in the release pocket, too. I'd like to have this passing, too, with systemd 245 before in migrates to the release pocket. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1867972/+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 1868089] Re: CUPS Fails to connect to printer
~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.4 LTS Release:18.04 Codename: bionic ~$ uname -a Linux Fueno 5.3.0-7629-generic #31~1581628854~18.04~2db8a7a~dev-Ubuntu SMP Fri Feb 14 19:57:43 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1868089 Title: CUPS Fails to connect to printer Status in cups package in Ubuntu: New Bug description: Printing is OK for a week, or, so. Then, with no changes, CUPS reports an error HP Office Jet Pro 9620 series "connect-to-printer" This lasts for 20 minutes, or so. I can ping the printer and connect to it with a browser. After pausing the printer and resume the printer, and connect with a browser, it starts to print. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.7 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.12 Architecture: amd64 CupsErrorLog: Date: Thu Mar 19 06:02:42 2020 Lpstat: device for HP_OfficeJet_Pro_9020_series: dnssd://HP%20OfficeJet%20Pro%209020%20series%20%5BCFE4C8%5D._ipp._tcp.local/?uuid=a58de112-16bc-5ad1-8887-1d919817cb03 device for HP_OfficeJet_Pro_9020_series_CFE4C8_: ipps://HPC46516CFE4C8.local:631/ipp/print Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 24f0:0105 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC7i7BNH Papersize: letter PpdFiles: HP_OfficeJet_Pro_9020_series_CFE4C8_: OfficeJet Pro 9020 series HP_OfficeJet_Pro_9020_series: HP OfficeJet Pro 9020 series, driverless, cups-filters 1.20.2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-7629-generic root=UUID=e495b330-7204-41f9-bfb7-a2a47e56fffd ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BNKBL357.86A.0080.2019.0725.1139 dmi.board.name: NUC7i7BNB dmi.board.vendor: Intel Corporation dmi.board.version: J31145-313 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBNKBL357.86A.0080.2019.0725.1139:bd07/25/2019:svnIntel(R)ClientSystems:pnNUC7i7BNH:pvrJ31153-314:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-313:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: BN dmi.product.name: NUC7i7BNH dmi.product.version: J31153-314 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1868089/+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 1868089] [NEW] CUPS Fails to connect to printer
Public bug reported: Printing is OK for a week, or, so. Then, with no changes, CUPS reports an error HP Office Jet Pro 9620 series "connect-to-printer" This lasts for 20 minutes, or so. I can ping the printer and connect to it with a browser. After pausing the printer and resume the printer, and connect with a browser, it starts to print. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.7 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.12 Architecture: amd64 CupsErrorLog: Date: Thu Mar 19 06:02:42 2020 Lpstat: device for HP_OfficeJet_Pro_9020_series: dnssd://HP%20OfficeJet%20Pro%209020%20series%20%5BCFE4C8%5D._ipp._tcp.local/?uuid=a58de112-16bc-5ad1-8887-1d919817cb03 device for HP_OfficeJet_Pro_9020_series_CFE4C8_: ipps://HPC46516CFE4C8.local:631/ipp/print Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 24f0:0105 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC7i7BNH Papersize: letter PpdFiles: HP_OfficeJet_Pro_9020_series_CFE4C8_: OfficeJet Pro 9020 series HP_OfficeJet_Pro_9020_series: HP OfficeJet Pro 9020 series, driverless, cups-filters 1.20.2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-7629-generic root=UUID=e495b330-7204-41f9-bfb7-a2a47e56fffd ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BNKBL357.86A.0080.2019.0725.1139 dmi.board.name: NUC7i7BNB dmi.board.vendor: Intel Corporation dmi.board.version: J31145-313 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBNKBL357.86A.0080.2019.0725.1139:bd07/25/2019:svnIntel(R)ClientSystems:pnNUC7i7BNH:pvrJ31153-314:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-313:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: BN dmi.product.name: NUC7i7BNH dmi.product.version: J31153-314 dmi.sys.vendor: Intel(R) Client Systems ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1868089 Title: CUPS Fails to connect to printer Status in cups package in Ubuntu: New Bug description: Printing is OK for a week, or, so. Then, with no changes, CUPS reports an error HP Office Jet Pro 9620 series "connect-to-printer" This lasts for 20 minutes, or so. I can ping the printer and connect to it with a browser. After pausing the printer and resume the printer, and connect with a browser, it starts to print. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.7 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.12 Architecture: amd64 CupsErrorLog: Date: Thu Mar 19 06:02:42 2020 Lpstat: device for HP_OfficeJet_Pro_9020_series: dnssd://HP%20OfficeJet%20Pro%209020%20series%20%5BCFE4C8%5D._ipp._tcp.local/?uuid=a58de112-16bc-5ad1-8887-1d919817cb03 device for HP_OfficeJet_Pro_9020_series_CFE4C8_: ipps://HPC46516CFE4C8.local:631/ipp/print Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 24f0:0105 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC7i7BNH Papersize: letter PpdFiles: HP_OfficeJet_Pro_9020_series_CFE4C8_: OfficeJet Pro 9020 series HP_OfficeJet_Pro_9020_series: HP OfficeJet Pro 9020 series, driverless, cups-filters 1.20.2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-7629-generic root=UUID=e495b330-7204-41f9-bfb7-a2a47e56fffd ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BNKBL357.86A.0080.2019.0725.1139 dmi.board.name: NUC7i7BNB dmi.board.vendor: Intel Corporation dmi.board.version: J31145-313 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBNKBL357.86A.0080.2019.0725.1139:bd07/25/2019:svnIntel(R)ClientSystems:pnNUC7i7BNH:pvrJ31153-314:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-313:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: BN dmi.product.name:
[Touch-packages] [Bug 1868085] Re: Bug related to the new kernel version 5.3.0-42-generic
5.3.0-43 is in -proposed now, please test -43 kernel. -- 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/1868085 Title: Bug related to the new kernel version 5.3.0-42-generic Status in alsa-driver package in Ubuntu: New Bug description: Hi all, After an update of Ubuntu kernel (version 5.3.0-42-generic) I can't have sound any more. No soundcards are detected any I have a "dummy output" in the sound pannel in settings. Furthermore I can't resume from sleep anymore. Output of ALSA Information script: !! !!ALSA Information Script v 0.4.64 !! !!Script ran on: Wed Mar 18 14:46:19 UTC 2020 !!Linux Distribution !!-- Ubuntu 18.04.4 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 18.04.4 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.4 LTS" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies /privacy-policy" UBUNTU_CODENAME=bionic !!DMI Information !!--- Manufacturer: HP Product Name: HP ZBook 15u G6 Product Version: Firmware Version: R70 Ver. 01.03.04 Board Vendor: HP Board Name:8549 !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ACPI000C:00/status 15 /sys/bus/acpi/devices/HPIC000C:00/status 15 /sys/bus/acpi/devices/HPQ6001:00/status15 /sys/bus/acpi/devices/IFX0785:00/status15 /sys/bus/acpi/devices/INT3400:00/status15 /sys/bus/acpi/devices/INT3403:00/status15 /sys/bus/acpi/devices/INT3403:01/status15 /sys/bus/acpi/devices/INT340E:00/status15 /sys/bus/acpi/devices/INT34BB:00/status15 /sys/bus/acpi/devices/INT3F0D:00/status15 /sys/bus/acpi/devices/LNXPOWER:00/status 15 /sys/bus/acpi/devices/LNXPOWER:02/status 1 /sys/bus/acpi/devices/LNXPOWER:03/status 1 /sys/bus/acpi/devices/LNXPOWER:05/status 1 /sys/bus/acpi/devices/LNXPOWER:06/status 1 /sys/bus/acpi/devices/LNXPOWER:07/status 1 /sys/bus/acpi/devices/LNXPOWER:08/status 1 /sys/bus/acpi/devices/PNP0103:00/status15 /sys/bus/acpi/devices/PNP0B00:00/status15 /sys/bus/acpi/devices/PNP0C02:00/status3 /sys/bus/acpi/devices/PNP0C02:01/status3 /sys/bus/acpi/devices/PNP0C02:05/status3 /sys/bus/acpi/devices/PNP0C09:00/status15 /sys/bus/acpi/devices/PNP0C0A:00/status31 /sys/bus/acpi/devices/PNP0C0C:00/status11 /sys/bus/acpi/devices/PRP1:00/status 11 /sys/bus/acpi/devices/SYNA3092:00/status 15 /sys/bus/acpi/devices/USBC000:00/status15 /sys/bus/acpi/devices/device:04/status 15 /sys/bus/acpi/devices/device:27/status 15 /sys/bus/acpi/devices/device:28/status 15 /sys/bus/acpi/devices/device:4c/status 15 !!Kernel Information !!-- Kernel release:5.3.0-42-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-42-generic Library version:1.1.3 Utilities version: 1.1.3 !!Loaded ALSA modules !!--- !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- --- no soundcards --- !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:9dc8] (rev 11) Subsystem: Hewlett-Packard Company Device [103c:8549] !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2 !!Loaded sound module options !!--- !!ALSA Device nodes !!- crw-rw 1 root audio 116, 1 Mar 18 14:45 /dev/snd/seq crw-rw 1 root audio 116, 33 Mar 18 14:44 /dev/snd/timer !!Aplay/Arecord output !! APLAY aplay: device_list:270: no soundcards found... ARECORD arecord: device_list:270: no
[Touch-packages] [Bug 1865504] Re: hwclock reports incorrect status in audit message
This bug was fixed in the package util-linux - 2.34-0.1ubuntu2.4
---
util-linux (2.34-0.1ubuntu2.4) eoan; urgency=medium
* d/p/hwclock_fix_audit_status.patch: reverse hwclock exit status
so to match audit_log_user_message(3) semantics. (LP: #1865504)
-- Joy Latten Thu, 05 Mar 2020 11:23:23
-0600
** Changed in: util-linux (Ubuntu Eoan)
Status: Fix Committed => Fix Released
--
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 Released
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] Update Released
The verification of the Stable Release Update for util-linux has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
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 Released
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 1868085] [NEW] Bug related to the new kernel version 5.3.0-42-generic
Public bug reported: Hi all, After an update of Ubuntu kernel (version 5.3.0-42-generic) I can't have sound any more. No soundcards are detected any I have a "dummy output" in the sound pannel in settings. Furthermore I can't resume from sleep anymore. Output of ALSA Information script: !! !!ALSA Information Script v 0.4.64 !! !!Script ran on: Wed Mar 18 14:46:19 UTC 2020 !!Linux Distribution !!-- Ubuntu 18.04.4 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 18.04.4 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.4 LTS" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies /privacy-policy" UBUNTU_CODENAME=bionic !!DMI Information !!--- Manufacturer: HP Product Name: HP ZBook 15u G6 Product Version: Firmware Version: R70 Ver. 01.03.04 Board Vendor: HP Board Name:8549 !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ACPI000C:00/status 15 /sys/bus/acpi/devices/HPIC000C:00/status 15 /sys/bus/acpi/devices/HPQ6001:00/status 15 /sys/bus/acpi/devices/IFX0785:00/status 15 /sys/bus/acpi/devices/INT3400:00/status 15 /sys/bus/acpi/devices/INT3403:00/status 15 /sys/bus/acpi/devices/INT3403:01/status 15 /sys/bus/acpi/devices/INT340E:00/status 15 /sys/bus/acpi/devices/INT34BB:00/status 15 /sys/bus/acpi/devices/INT3F0D:00/status 15 /sys/bus/acpi/devices/LNXPOWER:00/status 15 /sys/bus/acpi/devices/LNXPOWER:02/status 1 /sys/bus/acpi/devices/LNXPOWER:03/status 1 /sys/bus/acpi/devices/LNXPOWER:05/status 1 /sys/bus/acpi/devices/LNXPOWER:06/status 1 /sys/bus/acpi/devices/LNXPOWER:07/status 1 /sys/bus/acpi/devices/LNXPOWER:08/status 1 /sys/bus/acpi/devices/PNP0103:00/status 15 /sys/bus/acpi/devices/PNP0B00:00/status 15 /sys/bus/acpi/devices/PNP0C02:00/status 3 /sys/bus/acpi/devices/PNP0C02:01/status 3 /sys/bus/acpi/devices/PNP0C02:05/status 3 /sys/bus/acpi/devices/PNP0C09:00/status 15 /sys/bus/acpi/devices/PNP0C0A:00/status 31 /sys/bus/acpi/devices/PNP0C0C:00/status 11 /sys/bus/acpi/devices/PRP1:00/status 11 /sys/bus/acpi/devices/SYNA3092:00/status 15 /sys/bus/acpi/devices/USBC000:00/status 15 /sys/bus/acpi/devices/device:04/status 15 /sys/bus/acpi/devices/device:27/status 15 /sys/bus/acpi/devices/device:28/status 15 /sys/bus/acpi/devices/device:4c/status 15 !!Kernel Information !!-- Kernel release:5.3.0-42-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-42-generic Library version:1.1.3 Utilities version: 1.1.3 !!Loaded ALSA modules !!--- !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- --- no soundcards --- !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:9dc8] (rev 11) Subsystem: Hewlett-Packard Company Device [103c:8549] !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2 !!Loaded sound module options !!--- !!ALSA Device nodes !!- crw-rw 1 root audio 116, 1 Mar 18 14:45 /dev/snd/seq crw-rw 1 root audio 116, 33 Mar 18 14:44 /dev/snd/timer !!Aplay/Arecord output !! APLAY aplay: device_list:270: no soundcards found... ARECORD arecord: device_list:270: no soundcards found... !!Amixer output !!- !!Alsactl output !!-- --startcollapse-- --endcollapse-- !!All Loaded Modules !!-- ac97_bus acpi_pad acpi_thermal_rel aes_x86_64 aesni_intel amd_iommu_v2 amdgpu autofs4 bluetooth bnep btbcm btintel btrtl btusb ccm cfg80211 cmac coretemp crc32_pclmul crct10dif_pclmul cros_ec_core cros_ec_ishtp cryptd crypto_simd drm drm_kms_helper e1000e ecc ecdh_generic fb_sys_fops ghash_clmulni_intel glue_helper gpu_sched hid hid_generic hid_multitouch hid_sensor_als hid_sensor_hub
Re: [Touch-packages] [Bug 1647285] Re: SSL trust not system-wide
On Thu, 2020-03-19 at 09:44 +, Olivier Tilloy wrote: > It looks like symlinking firefox and thunderbird's own copies of > libnssckbi.so to the system-wide p11-kit-trust.so is the proper way to > fix this bug, as far as Mozilla's products are concerned. > > Before I proceed to doing this, I'd welcome comments from the security > team on this approach though, as I suspect I don't understand all the > implications. > > (an alternative would be building firefox/thunderbird against the > system-wide nss, but firefox currently requires 3.50, which isn't yet in > focal, and I suspect that requirement is being bumped often, so that > wouldn't really work with our distribution model) Right, don't bother trying to replace NSS just for this (although really, having a single version of NSS on the system *would* be nice). The interface to libnssckbi.so is a standard PKCS#11 library, and it's perfectly reasonable to replace that in each of firefox/thunderbird/chromium individually. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1647285 Title: SSL trust not system-wide Status in ca-certificates package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in nss package in Ubuntu: Confirmed Status in p11-kit package in Ubuntu: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: When I install a corporate CA trust root with update-ca-certificates, it doesn't seem to work everywhere. Various things like Firefox, Evolution, Chrome, etc. all fail to trust the newly-installed trusted CA. This ought to work, and does on other distributions. In p11-kit there is a module p11-kit-trust.so which can be used as a drop-in replacement for NSS's own libnssckbi.so trust root module, but which reads from the system's configured trust setup instead of the hard- coded version. This allows us to install the corporate CAs just once, and then file a bug against any package that *doesn't* then trust them. See https://fedoraproject.org/wiki/Features/SharedSystemCertificates for some of the historical details from when this feature was first implemented, but this is all now supported upstream and not at all distribution-specific. There shouldn't be any significant work required; it's mostly just a case of configuring and building it to make use of this functionality. (With 'alternatives' to let you substitute p11-kit-trust.so for the original NSS libnssckbi.so, etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1647285/+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 1647285] Re: SSL trust not system-wide
Before we switch any software to using p11-kit-trust.so, we need to fix our ca-certificates package to properly handle untrusted or blacklisted certificates. At the moment, I believe they are simply skipped when generating the contents of /usr/share/ca-certificates. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1647285 Title: SSL trust not system-wide Status in ca-certificates package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in nss package in Ubuntu: Confirmed Status in p11-kit package in Ubuntu: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: When I install a corporate CA trust root with update-ca-certificates, it doesn't seem to work everywhere. Various things like Firefox, Evolution, Chrome, etc. all fail to trust the newly-installed trusted CA. This ought to work, and does on other distributions. In p11-kit there is a module p11-kit-trust.so which can be used as a drop-in replacement for NSS's own libnssckbi.so trust root module, but which reads from the system's configured trust setup instead of the hard- coded version. This allows us to install the corporate CAs just once, and then file a bug against any package that *doesn't* then trust them. See https://fedoraproject.org/wiki/Features/SharedSystemCertificates for some of the historical details from when this feature was first implemented, but this is all now supported upstream and not at all distribution-specific. There shouldn't be any significant work required; it's mostly just a case of configuring and building it to make use of this functionality. (With 'alternatives' to let you substitute p11-kit-trust.so for the original NSS libnssckbi.so, etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1647285/+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 1647285] Re: SSL trust not system-wide
It looks like symlinking firefox and thunderbird's own copies of libnssckbi.so to the system-wide p11-kit-trust.so is the proper way to fix this bug, as far as Mozilla's products are concerned. Before I proceed to doing this, I'd welcome comments from the security team on this approach though, as I suspect I don't understand all the implications. (an alternative would be building firefox/thunderbird against the system-wide nss, but firefox currently requires 3.50, which isn't yet in focal, and I suspect that requirement is being bumped often, so that wouldn't really work with our distribution model) ** Changed in: firefox (Ubuntu) Status: New => Confirmed ** Changed in: firefox (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: thunderbird (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 ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1647285 Title: SSL trust not system-wide Status in ca-certificates package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in nss package in Ubuntu: Confirmed Status in p11-kit package in Ubuntu: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: When I install a corporate CA trust root with update-ca-certificates, it doesn't seem to work everywhere. Various things like Firefox, Evolution, Chrome, etc. all fail to trust the newly-installed trusted CA. This ought to work, and does on other distributions. In p11-kit there is a module p11-kit-trust.so which can be used as a drop-in replacement for NSS's own libnssckbi.so trust root module, but which reads from the system's configured trust setup instead of the hard- coded version. This allows us to install the corporate CAs just once, and then file a bug against any package that *doesn't* then trust them. See https://fedoraproject.org/wiki/Features/SharedSystemCertificates for some of the historical details from when this feature was first implemented, but this is all now supported upstream and not at all distribution-specific. There shouldn't be any significant work required; it's mostly just a case of configuring and building it to make use of this functionality. (With 'alternatives' to let you substitute p11-kit-trust.so for the original NSS libnssckbi.so, etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1647285/+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 1839290] Re: systemd doesn't restart a service after crashes
Dan, is there any chance of this fix landing to xenial-proposed and bionic-proposed? Thanks. -- 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/1839290 Title: systemd doesn't restart a service after crashes Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Disco: Fix Released Bug description: [impact] when a service configured to restart crashes, under certain configurations, that service is not correctly restarted. [test case] see comment 8 [regression potential] this changes the job mode of manager-triggered restarts to 'replace' any existing queued job(s), instead of failing if there are queued job(s). thus any regressions would occur when a service fails, that is configured to restart on failure. [scope] This is needed only for Xenial and Bionic. this is fixed with commit 03ff2dc71ecb09272d728d458498b44f7f132f51 which is included already in Eoan. [other info] original description: --- Affected versions of OS and systemd: $ cat /etc/issue Ubuntu 16.04.6 LTS \n \l $ systemd --version systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN Affected packages: systemd 229-4ubuntu21.22 and previous versions. Expected behaviour you didn't see: Scheduling restart of failed service. A process crashed by sigabrt and didn't restart. Description: The bug was reported to a systemd upstream repository: https://github.com/systemd/systemd/issues/11456 The bug was fixed and accepted to the master branch: https://github.com/systemd/systemd/pull/11467/files Action: Include this patch to Ubuntu 16.04 and other version of Ubuntu which are supported. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1839290/+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 1647285] Re: SSL trust not system-wide
according to #4 nss should still symlink libnssckbi.so to p11-kit- trust.so ** Changed in: nss (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1647285 Title: SSL trust not system-wide Status in ca-certificates package in Ubuntu: Confirmed Status in firefox package in Ubuntu: New Status in nss package in Ubuntu: Confirmed Status in p11-kit package in Ubuntu: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: When I install a corporate CA trust root with update-ca-certificates, it doesn't seem to work everywhere. Various things like Firefox, Evolution, Chrome, etc. all fail to trust the newly-installed trusted CA. This ought to work, and does on other distributions. In p11-kit there is a module p11-kit-trust.so which can be used as a drop-in replacement for NSS's own libnssckbi.so trust root module, but which reads from the system's configured trust setup instead of the hard- coded version. This allows us to install the corporate CAs just once, and then file a bug against any package that *doesn't* then trust them. See https://fedoraproject.org/wiki/Features/SharedSystemCertificates for some of the historical details from when this feature was first implemented, but this is all now supported upstream and not at all distribution-specific. There shouldn't be any significant work required; it's mostly just a case of configuring and building it to make use of this functionality. (With 'alternatives' to let you substitute p11-kit-trust.so for the original NSS libnssckbi.so, etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1647285/+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: [Zoom USB audio on Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker
** Description changed: 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. + + I was previously using 19.04 and 19.10 on this device and never + experienced this kind of issue. 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. -- 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: [Zoom USB audio on Dell Inspiron 7370] 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. I was previously using 19.04 and 19.10 on this device and never experienced this kind of issue. 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
[Touch-packages] [Bug 1791405] Re: bluetooth always in discoverable mode (security issue)
** Tags removed: fixed-upstream -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1791405 Title: bluetooth always in discoverable mode (security issue) Status in bluez package in Ubuntu: Triaged Status in gnome-bluetooth package in Ubuntu: Fix Released Status in gnome-bluetooth source package in Bionic: Fix Released Status in gnome-bluetooth source package in Cosmic: Fix Released Status in gnome-bluetooth source package in Disco: Fix Released Status in bluez source package in Focal: Triaged Status in gnome-bluetooth source package in Focal: Fix Released Status in gnome-bluetooth package in Fedora: Won't Fix Bug description: Excerpt from a similar report (https://bugzilla.redhat.com/show_bug.cgi?id=1602985) : Opening the Bluetooth settings will make the device discoverable again, but does not make the device undiscoverable after the settings are closed (this is not intended behavior; devices should only be discoverable when the bluetooth settings UI is open). There seem to be a merge request : https://gitlab.gnome.org/GNOME/gnome-bluetooth/merge_requests/1 Could you please merge it asap, it should be treated as a security issue IMHO. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1791405/+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 1857708] Re: Uses GNU awk specific option in bash completions, but gawk is not a dependency
** Changed in: pulseaudio (Ubuntu) Status: Triaged => Fix Released -- 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/1857708 Title: Uses GNU awk specific option in bash completions, but gawk is not a dependency Status in pulseaudio package in Ubuntu: Fix Released Bug description: The following command tells the files: grep awk $(dpkg-query -L pulseaudio | grep /usr/share/bash-completion/completions/) /usr/share/bash-completion/completions/pulseaudio:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pulseaudio:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacat:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacat:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacmd:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pacmd:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pactl:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pactl:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/padsp:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/padsp:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/paplay:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/paplay:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parec:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parec:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parecord:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/parecord:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pasuspender:pactl list cards 2> /dev/null | awk -e \ /usr/share/bash-completion/completions/pasuspender:pactl list cards 2> /dev/null | awk -e \ Only pulseaudio is a regular file; other ones are symbolic links, so it is enough to modify the first one. gawk has -e option, but it is not installed by default at least in Xubuntu, so (very) old mawk may be used. Solution: Either use "awk --" instead of "awk -e" or use "gawk -e" and put gawk as dependency. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarnos 1200 F pulseaudio /dev/snd/pcmC1D0p: jarnos 1200 F...m pulseaudio /dev/snd/controlC0: jarnos 1200 F pulseaudio /dev/snd/pcmC0D0p: jarnos 1200 F...m pulseaudio CurrentDesktop: XFCE Date: Fri Dec 27 18:44:55 2019 InstallationDate: Installed on 2019-12-05 (21 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1857708/+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: [Zoom USB audio on Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker
I'll unassign myself since I have no way to reproduce this right now. We may yet group similar bugs with this one in future but generally it's more helpful to deter people from doing that too soon. Otherwise when a bug is declared fixed someone will pipe up and say it's not, when really they've just subscribed to the wrong bug. ** Changed in: pulseaudio (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => (unassigned) -- 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: [Zoom USB audio on Dell Inspiron 7370] 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 1152137] Re: Pulseaudio won't start when home directory not owned by user
the fix is in the current pulseaudio version in focal now
** Changed in: pulseaudio (Ubuntu)
Status: Triaged => Fix Released
--
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/1152137
Title:
Pulseaudio won't start when home directory not owned by user
Status in pulseaudio package in Ubuntu:
Fix Released
Bug description:
I have an NFS mounted home directory on a dedicated fileserver which is
shared with Windows PCs via SMB.
The home directory is not owned by me. ACLs are set on it to allow me
full control of the contents but prevent me from changing its permissions.
This means any files or directories created in the home directory are owned
by me even though the top level is not.
Pulseaudio checks the home directory is owned by the user at startup and
exits if it isn't. This stops it running on my system.
I have recompiled pulseaudio without this check and it works fine.
Please either remove or modify the following startup check:
pulseaudio-1.1/src/pulsecore/src/pulsecore/core-util.c line 1415:
if (st.st_uid != getuid()) {
pa_log_error("Home directory %s not ours.", h);
errno = EACCES;
goto finish;
}
A better check would be for pulseaudio to try and create the files/folders it
needs and fail if it cannot.
I am using Ubuntu 12.04 and pulseaudio 1:1.1-0ubuntu15.2.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1152137/+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
I recommend making this bug unique to the machine model, and to the peripheral model. Most likely it's only triggered by one of them but while we don't know which it will help to avoid multiple people jumping on board the wrong bug. I can't seem to reproduce this bug in focal right now, but I do see other bugs sometimes which some people could confuse for this one. ** Summary changed: - 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 + [Zoom USB audio on Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker -- 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: [Zoom USB audio on Dell Inspiron 7370] 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 1868057] Re: screen flickering some small parts in user interface not right
Thanks for the bug report. I can't see anything in the attached files that would explain any flickering. Can you please take a video of the problem and attach it? Please also run this command: apport-collect 1868057 since I have moved the bug to gnome-shell. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1868057 Title: screen flickering some small parts in user interface not right Status in gnome-shell package in Ubuntu: Incomplete Bug description: just flickering but rare and little bits of colour problems in text. Don't really know what I'm doing now but it's an error report. Hopefully for graphics issues. lol 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 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 19 09:52:59 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 4th Gen Core Processor Integrated Graphics Controller [103c:1944] InstallationDate: Installed on 2020-03-18 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Hewlett-Packard HP ProBook 440 G1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=f6a4f0fe-5dac-4579-a54d-22600c546092 ro recovery nomodeset SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2019 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L74 Ver. 01.49 dmi.board.name: 1944 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 12.F4 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL74Ver.01.49:bd08/29/2019:svnHewlett-Packard:pnHPProBook440G1:pvrA3008DD10B03:rvnHewlett-Packard:rn1944:rvrKBCVersion12.F4:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP ProBook 440 G1 dmi.product.sku: C7N87AV#AB5 dmi.product.version: A3008DD10B03 dmi.sys.vendor: Hewlett-Packard 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/gnome-shell/+bug/1868057/+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 1868059] Re: Boot Flickering Issue
Is this different to bug 1868057? If so then please follow the same instructions as in that bug. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1868059 Title: Boot Flickering Issue Status in gnome-shell package in Ubuntu: Incomplete Bug description: On boot after I selected Ubuntu to load, it flickers while loading and I have to boot in "safe mode" then after that it loads normally. Quite frustrating not knowing how long it's going to take to load if at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868059/+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 1868059] [NEW] Boot Flickering Issue
Public bug reported: On boot after I selected Ubuntu to load, it flickers while loading and I have to boot in "safe mode" then after that it loads normally. Quite frustrating not knowing how long it's going to take to load if at all. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: Incomplete -- 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/1868059 Title: Boot Flickering Issue Status in gnome-shell package in Ubuntu: Incomplete Bug description: On boot after I selected Ubuntu to load, it flickers while loading and I have to boot in "safe mode" then after that it loads normally. Quite frustrating not knowing how long it's going to take to load if at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868059/+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 1868057] [NEW] screen flickering some small parts in user interface not right
Public bug reported: just flickering but rare and little bits of colour problems in text. Don't really know what I'm doing now but it's an error report. Hopefully for graphics issues. lol 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 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 19 09:52:59 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 4th Gen Core Processor Integrated Graphics Controller [103c:1944] InstallationDate: Installed on 2020-03-18 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Hewlett-Packard HP ProBook 440 G1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=f6a4f0fe-5dac-4579-a54d-22600c546092 ro recovery nomodeset SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2019 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L74 Ver. 01.49 dmi.board.name: 1944 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 12.F4 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL74Ver.01.49:bd08/29/2019:svnHewlett-Packard:pnHPProBook440G1:pvrA3008DD10B03:rvnHewlett-Packard:rn1944:rvrKBCVersion12.F4:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP ProBook 440 G1 dmi.product.sku: C7N87AV#AB5 dmi.product.version: A3008DD10B03 dmi.sys.vendor: Hewlett-Packard 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 third-party-packages 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/1868057 Title: screen flickering some small parts in user interface not right Status in xorg package in Ubuntu: New Bug description: just flickering but rare and little bits of colour problems in text. Don't really know what I'm doing now but it's an error report. Hopefully for graphics issues. lol 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 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 19 09:52:59 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 4th Gen Core Processor Integrated Graphics Controller [103c:1944] InstallationDate: Installed on 2020-03-18 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Hewlett-Packard HP ProBook 440 G1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=f6a4f0fe-5dac-4579-a54d-22600c546092 ro recovery nomodeset SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2019 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L74 Ver. 01.49 dmi.board.name: 1944 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 12.F4 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL74Ver.01.49:bd08/29/2019:svnHewlett-Packard:pnHPProBook440G1:pvrA3008DD10B03:rvnHewlett-Packard:rn1944:rvrKBCVersion12.F4:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP ProBook 440 G1 dmi.product.sku: C7N87AV#AB5 dmi.product.version: A3008DD10B03 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A
[Touch-packages] [Bug 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px
Actually the proper solution to comment #28 would be to change to overlay scrollbars, which is already covered by bug 1451924. It's still a different bug to this one, but if implemented it would close this bug nicely. If we just wanted to work on this bug without doing bug 1451924 then that would involve replacing the white background with the actual terminal background colour. Kind of similar to scrollbar-background- theming.patch but in a way that would actually be upstreamable... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1691678 Title: Scrollbars escape the bottom and right side of the Terminal window by 1px Status in GNOME Terminal: Fix Released Status in gnome-terminal package in Ubuntu: Triaged Status in gtk+3.0 package in Ubuntu: New Status in yaru-theme package in Ubuntu: Fix Released Bug description: Ubuntu's orange overlay scrollbars escape the bottom of the window during resizing. To reproduce try gnome-shell on artful using the Ambiance theme. Open a Terminal window and resize it vertically, quickly. Notice the bottom of the overlay scrollbar overruns the bottom of the window. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu3 Architecture: amd64 Date: Thu May 18 15:28:33 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2017-05-03 (15 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1691678/+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
