[Touch-packages] [Bug 1869868] Re: bug
Please describe in more detail what kind of problem you are 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/1869868 Title: bug Status in Ubuntu: Incomplete Bug description: bug ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 31 13:22:32 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [8086:22b0] (rev 36) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [8086:7270] InstallationDate: Installed on 2020-03-31 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 040b:2011 Weltrend Semiconductor Bus 001 Device 003: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory Bus 001 Device 002: ID 048d:1345 Integrated Technology Express, Inc. Multi Cardreader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: AZW Z83 II ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=7843659a-587f-48ec-86b4-df2d315abde7 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: YB1007 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrYB1007:bd08/17/2017:svnAZW:pnZ83II:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnCherryTrailCR:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z83 II dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: AZW version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.1 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/+bug/1869868/+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 1870988] Re: [nouveau] Xorg crashed with SIGABRT in disk_cache_has_key() from can_skip_compile.part()
** Summary changed: - [nouveau] Xorg crashed with SIGABRT in disk_cache_has_key() + [nouveau] Xorg crashed with SIGABRT in disk_cache_has_key() from can_skip_compile.part() ** Summary changed: - [nouveau] Xorg crashed with SIGABRT in disk_cache_has_key() from can_skip_compile.part() + [nouveau] Xorg crashed with SIGABRT in disk_cache_has_key() from can_skip_compile.part() from _mesa_glsl_compile_shader() ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- 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/1870988 Title: [nouveau] Xorg crashed with SIGABRT in disk_cache_has_key() from can_skip_compile.part() from _mesa_glsl_compile_shader() Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: I'm not exactly sure what triggered this bug however, I was installing wire, session-desktop and a few minutes beforehand I uninstalled wire. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 5 15:29:29 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.4, 5.4.0-21-generic, x86_64: installed ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation GT216M [NVS 5100M] [10de:0a2c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GT216M [NVS 5100M] [103c:1521] InstallationDate: Installed on 2020-04-05 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Hewlett-Packard HP EliteBook 8540p PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=07ef73e3-6724-4de6-af31-bbb7c81944c9 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/xorg/modules/libglamoregl.so Title: Xorg crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 11/11/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CVD Ver. F.60 dmi.board.name: 1521 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 32.36 dmi.chassis.asset.tag: NG00162275 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CVDVer.F.60:bd11/11/2015:svnHewlett-Packard:pnHPEliteBook8540p:pvr:rvnHewlett-Packard:rn1521:rvrKBCVersion32.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8540p dmi.product.sku: NU486AV dmi.sys.vendor: Hewlett-Packard separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1870988/+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 1871275] Re: package ca-certificates 20170717~16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: ca-certificates (Ubuntu) Importance: Undecided => Low ** Changed in: ca-certificates (Ubuntu) Status: New => Invalid -- 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/1871275 Title: package ca-certificates 20170717~16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in ca-certificates package in Ubuntu: Invalid Bug description: packages failed to install ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ca-certificates 20170717~16.04.2 ProcVersionSignature: Ubuntu 4.4.0-176.206-generic 4.4.211 Uname: Linux 4.4.0-176-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 Date: Mon Apr 6 20:58:46 2020 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-04-08 (1825 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: ca-certificates Title: package ca-certificates 20170717~16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1871275/+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 1871282] Re: libpam fails to install during upgrade from 19.10 to 20.20 beta
Please attach the full logs from your upgrade. If you used do-release- upgrade or update-manager, these will be in /var/log/dist-upgrade. ** Changed in: pam (Ubuntu) Status: New => Opinion ** Changed in: pam (Ubuntu) Status: Opinion => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1871282 Title: libpam fails to install during upgrade from 19.10 to 20.20 beta Status in pam package in Ubuntu: Incomplete Bug description: Hello, I runned an upgrade from 19.10 to 20.20 beta and it gave me a bunch of errors related to pam: 6.3965:installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Segmentation fault), core dumped installed libpam-runtime package post-installation script subprocess was killed by signal (Segmentation fault), core dumped And some other errors probably because of the previous failures: Não foi possível instalar '/var/cache/apt/archives/libpam-modules_1.3.1-5ubuntu4_amd64.deb' (Could not install '/var...') Não foi possível instalar 'libpam-modules' Não foi possível instalar 'passwd' I had some extra repos added: google-chrome flacon-ubuntu-ppa-eoan kubuntu-ppa-ubuntu-backports-disco otto-kesselgulasch-ubuntu-gimp-bionic virtualbox.list skype-stable.list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1871282/+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 1861990] Re: journalctl unable to read logs
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1861990 Title: journalctl unable to read logs Status in systemd package in Ubuntu: Expired Bug description: Ubuntu release: 18.04.4 LTS Package version: systemd 237-3ubuntu10.33 A simple journalctl command is now giving me this error Journal file /var/log/journal/ad9213e031ec2a16399a4251594e/user-1001@ae426ac82df44a8489f745ad63e8c9ea-215f-0005848bb1ab0334.journal uses an unsupported feature, ignoring file. Use SYSTEMD_LOG_LEVEL=debug journalctl --file=/var/log/journal/ad9213e031ec2a16399a4251594e/user-1001@ae426ac82df44a8489f745ad63e8c9ea-215f-0005848bb1ab0334.journal to see the details. -- No entries -- When I invoke the recommended command SYSTEMD_LOG_LEVEL=debug journalctl --file=/var/log/journal/ad9213e031ec2a16399a4251594e/user-1001 @ae426ac82df44a8489f745ad63e8c9ea-215f- 0005848bb1ab0334.journal I get Journal effective settings seal=no compress=no compress_threshold_bytes=8B Journal file /var/log/journal/ad9213e031ec2a16399a4251594e/user-1001@ae426ac82df44a8489f745ad63e8c9ea-215f-0005848bb1ab0334.journal uses incompatible flag lz4-compressed disabled at compilation time. Failed to open journal file /var/log/journal/ad9213e031ec2a16399a4251594e/user-1001@ae426ac82df44a8489f745ad63e8c9ea-215f-0005848bb1ab0334.journal: Protocol not supported mmap cache statistics: 0 hit, 1 miss Failed to open files: Protocol not supported journalctl --version gives systemd 244 (244) -PAM -AUDIT -SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP -LIBCRYPTSETUP -GCRYPT -GNUTLS -ACL +XZ -LZ4 -SECCOMP +BLKID -ELFUTILS -KMOD -IDN2 -IDN -PCRE2 default-hierarchy=unified Looks like someone has reported the same thing to redhat (https://bugzilla.redhat.com/show_bug.cgi?id=1778809) with no answers yet. Were logs previously lz4-compressed and now are not? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1861990/+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 1862044] Re: packet loss, extra latency and lower bandwidth on bionic
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1862044 Title: packet loss, extra latency and lower bandwidth on bionic Status in systemd package in Ubuntu: Expired Bug description: We are investigating migrating our servers from Xenial to Bionic. We are seeing significant network differences between the 2 LTS versions. Using the same hardware an machines connected to a single swith on the same network, we see: 10% less packets throuput on bionic in comparision to Xenial when running uperf. Also "tc -s qdisc" report packets been dropped on Bionic but not Xenial. The command iperf -c -u -d -p 20 timeout on Bionic and not on Xenial, and if you reduce the value of p, you will see more packet drops on Bionic. We tryied to upgrade the xenial kernel to the same version than bionic. We did not see any improvement. All the tests are performed with 4 identical physical machines connected to the same physical switch. With one bionic machine, one Xenial machine and 2 extra Xenial machine that act as iperf/uperf clients. All 4 nodes are configured as ntp peers with each others. Under load, the bionic machine see siginificant jitter improvement with the 3 others machines. We don't see that with the Xenial hosts. I doesn't seems to be an hardware compatibility issue as we see significant network performance loss in our datacenter on fully different hardware. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: iperf 2.0.10+dfsg1-1ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-76.86-lowlatency 4.15.18 Uname: Linux 4.15.0-76-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Wed Feb 5 17:14:25 2020 Dependencies: gcc-8-base 8.3.0-6ubuntu1~18.04.1 libc6 2.27-3ubuntu1 libgcc1 1:8.3.0-6ubuntu1~18.04.1 libstdc++6 8.3.0-6ubuntu1~18.04.1 InstallationDate: Installed on 2020-01-29 (7 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: iperf UpgradeStatus: No upgrade log present (probably fresh install) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.29 ProcVersionSignature: Ubuntu 4.15.0-76.86-lowlatency 4.15.18 Uname: Linux 4.15.0-76-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Wed Feb 5 17:29:53 2020 ExecutablePath: /lib/systemd/systemd InstallationDate: Installed on 2020-01-29 (7 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Dell Inc. XPS 8700 ProcEnviron: TERM=linux PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-76-lowlatency root=UUID=400563c9-8749-47b7-8abb-1efdb57bc589 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/16/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA01:bd05/16/2013:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1862044/+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 1536353] Re: [Regression] Epson's printer driver packages cannot be installed as lsb package is not available anymore
Thank you so much for this information, I have been googling and searching the net for 2 weeks for an answer of my Epson L800, I couldn't installed it in Sparkylinux 5, I added the Debian 9 repository and charm. One thing that I don't get it to work is the HubiC cloud, it keeps says "Warning] Can not synchronise /home/qkeybil/Hubic/: Index was outside the bounds of the array.. Will retry later. If there is one out there to help, what is going on? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lsb in Ubuntu. https://bugs.launchpad.net/bugs/1536353 Title: [Regression] Epson's printer driver packages cannot be installed as lsb package is not available anymore Status in lsb: New Status in cups-filters package in Ubuntu: Fix Released Status in epson-inkjet-printer-escpr package in Ubuntu: Fix Released Status in lsb package in Ubuntu: Fix Released Status in cups-filters source package in Xenial: Fix Released Status in epson-inkjet-printer-escpr source package in Xenial: Fix Released Status in lsb source package in Xenial: Fix Released Bug description: [SRU justification] Previous releases were compatible with third-party printer drivers provided in LSB package format (and also as .deb packages depending on the lsb package). As of 16.04, because the LSB specifies ABIs for various libraries that are no longer supported in Ubuntu as obsolete, the packages for the lsb modules have been dropped in both Debian and Ubuntu. This includes dropping of lsb-core, which is the component which provides the LSB-mandated ELF loader path - without which no lsb executable will work. This SRU will restore the bare minimum of LSB compatibility necessary to support known third-party LSB printer driver packages on Ubuntu 16.04. [Regression potential] The reintroduced 'lsb' binary package is known to not fully satisfy the requirements for a complete LSB-compliant system. This is a regression vs. Ubuntu 14.04; so anyone using LSB packages on Ubuntu 14.04 who upgrades to Ubuntu 16.04 may have the upgrade succeed without any warning from the package manager. As there are very few lsb packages in use in the wild, this is considered an acceptable regression, especially as this will land before the first 16.04 point release. [Test case] 1. Download the epsion 201106w printer driver package from http://download.ebz.epson.net/dsc/op/stable/debian/dists/lsb3.2/main/binary-amd64/epson-inkjet-printer-201106w_1.0.1-1lsb3.2_amd64.deb 2. Install the package and confirm that its dependencies are not satisfiable. 3. Enable xenial-proposed. 4. Install the package again and confirm that the dependencies are satisfied. 5. Verify that /opt/epson-inkjet-printer-201106w/cups/lib/filter/epson_inkjet_printer_filter can be run without errors about missing lsb ld.so or missing libraries. Starting with Xenial, lsb compatibility packages were dropped (besides lsb-release and lsb-base): lsb (9.20150826) unstable; urgency=low * Drop all the LSB compatibility packages besides lsb-release and lsb-base - Drop packages-availability checking in lsb-release - Truncate README.Debian to a minimum - Document this in lsb-base.NEWS.Debian * Change the versioning number to avoid any ambiguity; use joeyh's version.date, with version being Debian next stable's -- Didier Raboud Wed, 26 Aug 2015 12:00:00 +0200 The problem is that downloadable printer drivers (like the ones from Openprinting, but also from other available providers) that are suggested when installing a printer on Ubuntu depends on lsb, which is not available anymore: epson-inkjet-printer-201106w: Dépend: lsb (>=3.2) but it is not installable This triggers a regression where it is not possible to setup a printer this way (downloading a driver where no local driver is available) anymore. I see two possible solutions: - Add a proper replaces field to one of the remaining lsb-* packages, to hopefully fix missing lsb package (maybe it would be useful to also replace other compability packages that are not built anymore). - Re-introduce LSB compatibility packages, but that might be an overkill. To manage notifications about this bug go to: https://bugs.launchpad.net/lsb/+bug/1536353/+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 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]
[+Subscribed Hans] Hans, I think the issue is caused by: [drm:intel_dsi_vbt_gpio_init [i915]] *ERROR* Failed to own gpio for panel control Would be appreciated if you can take a look. -- 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/1860754 Title: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error] Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't recognize graphic driver. - run udo apt-get install xserver-xorg-video-intel 0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 14:29:01 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd] InstallationDate: Installed on 2020-01-24 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T100HAN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T100HAN.221 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T100HAN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: T dmi.product.name: T100HAN dmi.product.sku: ASUS-TabletSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860754/+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 1871023] Re: json_gvariant_deserialize can fail due to unrelated code setting errno
** Changed in: json-glib (Ubuntu Bionic) Status: Fix Committed => In Progress ** Changed in: json-glib (Ubuntu Eoan) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-glib in Ubuntu. https://bugs.launchpad.net/bugs/1871023 Title: json_gvariant_deserialize can fail due to unrelated code setting errno Status in json-glib package in Ubuntu: Fix Committed Status in json-glib source package in Bionic: In Progress Status in json-glib source package in Eoan: In Progress Status in json-glib source package in Focal: Fix Committed Bug description: [Impact] json_gvariant_deserialize can fail due to unrelated code setting errno, this is causing snapd-glib to not be able to decode responses from snapd. Fixed in https://gitlab.gnome.org/GNOME/json-glib/-/merge_requests/22 [Test Case] 1. Run GNOME Software from the command line 2. Browse to postman Expected result: Errors are not shown on the command line Observed result: The following errors are shown on the command line: 05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed 05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed 05:17:29:0877 Gs not GsPlugin error g-io-error-quark:35: Invalid string value converting to GVariant 05:17:29:0877 Gs not handling error failed for action refine: Invalid string value converting to GVariant (These errors may not always occur, and is likely racy). [Regression Potential] Small risk of introducing other bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1871023/+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 1871282] Re: libpam fails to install during upgrade from 19.10 to 20.20 beta
** Description changed: Hello, I runned an upgrade from 19.10 to 20.20 beta and it gave me a bunch of errors related to pam: 6.3965:installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Segmentation fault), core dumped installed libpam-runtime package post-installation script subprocess was killed by signal (Segmentation fault), core dumped And some other errors probably because of the previous failures: Não foi possível instalar '/var/cache/apt/archives/libpam-modules_1.3.1-5ubuntu4_amd64.deb' (Could not install '/var...') Não foi possível instalar 'libpam-modules' Não foi possível instalar 'passwd' + + I had some extra repos added: + google-chrome + flacon-ubuntu-ppa-eoan + kubuntu-ppa-ubuntu-backports-disco + otto-kesselgulasch-ubuntu-gimp-bionic + virtualbox.list + skype-stable.list -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1871282 Title: libpam fails to install during upgrade from 19.10 to 20.20 beta Status in pam package in Ubuntu: New Bug description: Hello, I runned an upgrade from 19.10 to 20.20 beta and it gave me a bunch of errors related to pam: 6.3965:installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Segmentation fault), core dumped installed libpam-runtime package post-installation script subprocess was killed by signal (Segmentation fault), core dumped And some other errors probably because of the previous failures: Não foi possível instalar '/var/cache/apt/archives/libpam-modules_1.3.1-5ubuntu4_amd64.deb' (Could not install '/var...') Não foi possível instalar 'libpam-modules' Não foi possível instalar 'passwd' I had some extra repos added: google-chrome flacon-ubuntu-ppa-eoan kubuntu-ppa-ubuntu-backports-disco otto-kesselgulasch-ubuntu-gimp-bionic virtualbox.list skype-stable.list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1871282/+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 1871112] Re: [vboxvideo] VirtualBox not starting
Sounds like either bug 1870726 or bug 1849883. Do you think either of those describe the problem you are facing? ** Summary changed: - VirtualBox not starting + [vboxvideo] VirtualBox not starting ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (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/1871112 Title: [vboxvideo] VirtualBox not starting Status in xorg-server package in Ubuntu: Incomplete Bug description: Focal Fossa beta release does not booting correctly to the desktop. Machine: VirtualBox 6.0.18 r136238, Graphics Controller: VBoxSVGA or VBoxsVGA ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 Date: Mon Apr 6 13:07:07 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) Subsystem: VMware VirtualBox Graphics Adapter [15ad:0405] LiveMediaBuild: Lsusb: Bus 002 Device 002: ID 80ee:0031 VirtualBox USB CD-ROM Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz boot=casper noprompt splash -- locale=en_US SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1871112/+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 1857046] Re: lxc 3.0.4-0ubuntu2 ADT test failure with linux 5.5.0-2.3
Considering fixed as we now have 4.0.1 in the archive, if this still happens, let us know. ** Changed in: lxc (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1857046 Title: lxc 3.0.4-0ubuntu2 ADT test failure with linux 5.5.0-2.3 Status in lxc package in Ubuntu: Fix Released Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-canonical-kernel-team-bootstrap/focal/amd64/l/lxc/20191218_145013_76e0c@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-canonical-kernel-team-bootstrap/focal/arm64/l/lxc/20191218_165648_a3f34@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-canonical-kernel-team-bootstrap/focal/ppc64el/l/lxc/20191218_151902_0998c@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-canonical-kernel-team-bootstrap/focal/s390x/l/lxc/20191218_152251_9101b@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1857046/+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 1871282] [NEW] libpam fails to install during upgrade from 19.10 to 20.20 beta
Public bug reported: Hello, I runned an upgrade from 19.10 to 20.20 beta and it gave me a bunch of errors related to pam: 6.3965:installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Segmentation fault), core dumped installed libpam-runtime package post-installation script subprocess was killed by signal (Segmentation fault), core dumped And some other errors probably because of the previous failures: Não foi possível instalar '/var/cache/apt/archives/libpam-modules_1.3.1-5ubuntu4_amd64.deb' (Could not install '/var...') Não foi possível instalar 'libpam-modules' Não foi possível instalar 'passwd' ** Affects: pam (Ubuntu) Importance: Undecided Status: New ** Tags: dist-upgrade -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1871282 Title: libpam fails to install during upgrade from 19.10 to 20.20 beta Status in pam package in Ubuntu: New Bug description: Hello, I runned an upgrade from 19.10 to 20.20 beta and it gave me a bunch of errors related to pam: 6.3965:installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Segmentation fault), core dumped installed libpam-runtime package post-installation script subprocess was killed by signal (Segmentation fault), core dumped And some other errors probably because of the previous failures: Não foi possível instalar '/var/cache/apt/archives/libpam-modules_1.3.1-5ubuntu4_amd64.deb' (Could not install '/var...') Não foi possível instalar 'libpam-modules' Não foi possível instalar 'passwd' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1871282/+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 1870539] Re: package liblxc-common 3.0.4-0ubuntu2 failed to install/upgrade: a tentar sobre-escrever '/usr/share/man/ja/man1/lxc-user-nic.1.gz', que também está no pacote lxc-uti
This has already been fixed in 4.0.1-0ubuntu1 ** Changed in: lxc (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1870539 Title: package liblxc-common 3.0.4-0ubuntu2 failed to install/upgrade: a tentar sobre-escrever '/usr/share/man/ja/man1/lxc-user-nic.1.gz', que também está no pacote lxc-utils 3.0.4-0ubuntu2 Status in lxc package in Ubuntu: Fix Released Bug description: EU estava utilizando normalmente o Ubuntu e começou a dar este erro toda vez que inicializo o sistema. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: liblxc-common 3.0.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 AptOrdering: liblxc1:amd64: Install liblxc-common:amd64: Install lxc-utils:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri Apr 3 09:40:14 2020 ErrorMessage: a tentar sobre-escrever '/usr/share/man/ja/man1/lxc-user-nic.1.gz', que também está no pacote lxc-utils 3.0.4-0ubuntu2 InstallationDate: Installed on 2020-03-20 (14 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=a587e5d5-e952-4c03-8a86-2af704b07304 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu1 PythonDetails: N/A SourcePackage: lxc Title: package liblxc-common 3.0.4-0ubuntu2 failed to install/upgrade: a tentar sobre-escrever '/usr/share/man/ja/man1/lxc-user-nic.1.gz', que também está no pacote lxc-utils 3.0.4-0ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.net.0.type = veth lxc.net.0.link = lxcbr0 lxc.net.0.flags = up lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1870539/+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 1871137] Re: Recorded audio is super choppy with today's apt upgrade
** Changed in: pulseaudio (Ubuntu) Status: New => 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/1871137 Title: Recorded audio is super choppy with today's apt upgrade Status in pulseaudio package in Ubuntu: Fix Released Bug description: People reported choppy audio coming from me in my morning stand-up call. I thought it might be an issue with our chat system, so I tried recording a sound bite in Audacity both with and without my bluetooth headset. I got the same incredibly choppy sound in either case. I'll attach a clip to the bug if I can so you can see what I mean. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 Date: Mon Apr 6 11:07:37 2020 InstallationDate: Installed on 2020-01-09 (87 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-01-24 (73 days ago) dmi.bios.date: 04/18/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.7.0 dmi.board.name: Alienware 17 R5 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.7.0:bd04/18/2019:svnAlienware:pnAlienware17R5:pvr1.7.0:rvnAlienware:rnAlienware17R5:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware 17 R5 dmi.product.sku: 0877 dmi.product.version: 1.7.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871137/+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 1870803] Re: LightDM unlocks without Password
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1870803 Title: LightDM unlocks without Password Status in Ubuntu: New Status in lightdm package in Ubuntu: New Bug description: When doing `dm-tool lock` the screen locks. Then pressing CTRL+ALT+F7 immediately returns me to my Session without any need to type the password. When logging in mutliple users I can switch between the users with CTRL+ALT+F7 and CTRL+ALT+F8 without needing any of the users passwords. I tested this with both lightdm-gtk-greeter and slick-greeter and the behavior is the same for both. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screensaver (not installed) ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 Date: Sat Apr 4 17:05:51 2020 SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1870803/+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 1870397] Re: package grub-efi-amd64 2.02-2ubuntu8.15 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 12
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1870397 Title: package grub-efi-amd64 2.02-2ubuntu8.15 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 128 Status in debconf package in Ubuntu: New Status in grub2 package in Ubuntu: New Bug description: I really don't know what happened. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: grub-efi-amd64 2.02-2ubuntu8.15 ProcVersionSignature: Ubuntu 4.15.0-1024.29-oem 4.15.18 Uname: Linux 4.15.0-1024-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.13 Architecture: amd64 Date: Thu Apr 2 14:19:25 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+loki-n3-v3-whl+X32 ErrorMessage: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2020-01-22 (71 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1024-oem.efi.signed root=UUID=9f8587ef-fb04-4725-bf4f-01726b47221a ro mem_sleep_default=deep usbcore.quirks=2386:3119:k quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12 SourcePackage: grub2 Title: package grub-efi-amd64 2.02-2ubuntu8.15 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1870397/+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 1870539] Re: package liblxc-common 3.0.4-0ubuntu2 failed to install/upgrade: a tentar sobre-escrever '/usr/share/man/ja/man1/lxc-user-nic.1.gz', que também está no pacote lxc-uti
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public ** Package changed: ubuntu => lxc (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1870539 Title: package liblxc-common 3.0.4-0ubuntu2 failed to install/upgrade: a tentar sobre-escrever '/usr/share/man/ja/man1/lxc-user-nic.1.gz', que também está no pacote lxc-utils 3.0.4-0ubuntu2 Status in lxc package in Ubuntu: New Bug description: EU estava utilizando normalmente o Ubuntu e começou a dar este erro toda vez que inicializo o sistema. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: liblxc-common 3.0.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 AptOrdering: liblxc1:amd64: Install liblxc-common:amd64: Install lxc-utils:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri Apr 3 09:40:14 2020 ErrorMessage: a tentar sobre-escrever '/usr/share/man/ja/man1/lxc-user-nic.1.gz', que também está no pacote lxc-utils 3.0.4-0ubuntu2 InstallationDate: Installed on 2020-03-20 (14 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=a587e5d5-e952-4c03-8a86-2af704b07304 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu1 PythonDetails: N/A SourcePackage: lxc Title: package liblxc-common 3.0.4-0ubuntu2 failed to install/upgrade: a tentar sobre-escrever '/usr/share/man/ja/man1/lxc-user-nic.1.gz', que também está no pacote lxc-utils 3.0.4-0ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.net.0.type = veth lxc.net.0.link = lxcbr0 lxc.net.0.flags = up lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1870539/+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 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
Attached my realtek dump. ** Attachment added: "RealTek Dump" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1851518/+attachment/5348304/+files/RtHDDump.zip -- 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/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in alsa-driver package in Ubuntu: Confirmed Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1383 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 06:20:08 2019 InstallationDate: Installed on 2019-11-03 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8
[Touch-packages] [Bug 1870397] Re: package grub-efi-amd64 2.02-2ubuntu8.15 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 12
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public ** Package changed: ubuntu => grub2 (Ubuntu) ** Also affects: debconf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1870397 Title: package grub-efi-amd64 2.02-2ubuntu8.15 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 128 Status in debconf package in Ubuntu: New Status in grub2 package in Ubuntu: New Bug description: I really don't know what happened. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: grub-efi-amd64 2.02-2ubuntu8.15 ProcVersionSignature: Ubuntu 4.15.0-1024.29-oem 4.15.18 Uname: Linux 4.15.0-1024-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.13 Architecture: amd64 Date: Thu Apr 2 14:19:25 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+loki-n3-v3-whl+X32 ErrorMessage: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2020-01-22 (71 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1024-oem.efi.signed root=UUID=9f8587ef-fb04-4725-bf4f-01726b47221a ro mem_sleep_default=deep usbcore.quirks=2386:3119:k quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12 SourcePackage: grub2 Title: package grub-efi-amd64 2.02-2ubuntu8.15 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1870397/+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 1871019] Re: Nextcloud account added to Online Accounts does not populate Calendar apps (WebDAV file sharing does work)
Something I just noticed, if it means anything, is that I have a file in ~/.config/evolution/sources that seems to contain what would be my Nextcloud info, but it seems to be missing some information perhaps? I don't have a reference in front of me for what these normally look like. Contents pasted below [Data Source] DisplayName=leggett...@ambrose.leggett.dev Enabled=true Parent= [Authentication] Host= Method=none Port=0 ProxyUid=system-proxy RememberPassword=true User= CredentialName= IsExternal=true [Collection] BackendName=webdav CalendarEnabled=true ContactsEnabled=true Identity=leggettc18 MailEnabled=true AllowSourcesRename=false CalendarUrl= ContactsUrl= [GNOME Online Accounts] AccountId=account_1586225954_0 CalendarUrl=https://leggett...@ambrose.leggett.dev/remote.php/caldav/ ContactsUrl=https://leggett...@ambrose.leggett.dev/remote.php/carddav/ Name= Address= -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1871019 Title: Nextcloud account added to Online Accounts does not populate Calendar apps (WebDAV file sharing does work) Status in gnome-online-accounts package in Ubuntu: Incomplete Bug description: My Nextcloud server was working fine with previous versions of Ubuntu, but on the 20.04 daily when I add my Nextcloud account it does not populate my Calendars or todo lists. It does give me file access via WebDAV. Server is working fine as far as I'm aware. Going to Settings -> Administration - Overview shows me any configuration issues it can detect, currently the only error there is related to background job execution (which is only relevant to the News app if I'm not mistaken). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-online-accounts 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 5 23:59:55 2020 InstallationDate: Installed on 2020-04-03 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1871019/+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 1870539] [NEW] package liblxc-common 3.0.4-0ubuntu2 failed to install/upgrade: a tentar sobre-escrever '/usr/share/man/ja/man1/lxc-user-nic.1.gz', que também está no pacote lxc-u
You have been subscribed to a public bug: EU estava utilizando normalmente o Ubuntu e começou a dar este erro toda vez que inicializo o sistema. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: liblxc-common 3.0.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 AptOrdering: liblxc1:amd64: Install liblxc-common:amd64: Install lxc-utils:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri Apr 3 09:40:14 2020 ErrorMessage: a tentar sobre-escrever '/usr/share/man/ja/man1/lxc-user-nic.1.gz', que também está no pacote lxc-utils 3.0.4-0ubuntu2 InstallationDate: Installed on 2020-03-20 (14 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=a587e5d5-e952-4c03-8a86-2af704b07304 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu1 PythonDetails: N/A SourcePackage: lxc Title: package liblxc-common 3.0.4-0ubuntu2 failed to install/upgrade: a tentar sobre-escrever '/usr/share/man/ja/man1/lxc-user-nic.1.gz', que também está no pacote lxc-utils 3.0.4-0ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.net.0.type = veth lxc.net.0.link = lxcbr0 lxc.net.0.flags = up lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-package focal -- package liblxc-common 3.0.4-0ubuntu2 failed to install/upgrade: a tentar sobre-escrever '/usr/share/man/ja/man1/lxc-user-nic.1.gz', que também está no pacote lxc-utils 3.0.4-0ubuntu2 https://bugs.launchpad.net/bugs/1870539 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc 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 1869429] Re: package apparmor 2.12-4ubuntu5.1 failed to install/upgrade: installed apparmor package post-installation script subprocess returned error exit status 12
Hello Thomas, That's a very dirty upgrade log, quite a lot failed. Is this a small- memory system? Do you know what may make this system unique in showing these errors? I don't have a lot of ideas where things would have gone off the rails otherwise. Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1869429 Title: package apparmor 2.12-4ubuntu5.1 failed to install/upgrade: installed apparmor package post-installation script subprocess returned error exit status 12 Status in apparmor package in Ubuntu: New Bug description: I was running "do-release-upgrade". It prompted me that my /etc/ssh/sshd_config file was different from the maintainers; I went to look at the differences, and somehow I wasn't able to go back and say "keep my version", instead things errored out. I was able to recover at the end of the process. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: apparmor 2.12-4ubuntu5.1 ProcVersionSignature: Ubuntu 4.15.0-91.92~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 Date: Fri Mar 27 20:01:57 2020 Df: Dmesg: ErrorMessage: installed apparmor package post-installation script subprocess returned error exit status 12 InstallationDate: Installed on 2017-05-04 (1057 days ago) InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.8) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic root=UUID=9e033fda-4dfa-44ab-9f9d-2984aae489de ro quiet splash pcie_aspm=off vt.handoff=7 Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12 SourcePackage: apparmor Syslog: Mar 27 18:17:18 laptopsanytime dbus[861]: [system] AppArmor D-Bus mediation is enabled Mar 27 18:20:14 laptopsanytime dbus[955]: [system] AppArmor D-Bus mediation is enabled Mar 27 18:22:56 laptopsanytime dbus[963]: [system] AppArmor D-Bus mediation is enabled Mar 27 19:02:11 laptopsanytime dbus[865]: [system] AppArmor D-Bus mediation is enabled Title: package apparmor 2.12-4ubuntu5.1 failed to install/upgrade: installed apparmor package post-installation script subprocess returned error exit status 12 UpgradeStatus: Upgraded to bionic on 2020-03-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1869429/+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 1871019] Re: Nextcloud account added to Online Accounts does not populate Calendar apps (WebDAV file sharing does work)
Absolutely, I've attached a txt file with the contents of `journalctl -b 0`. For the record, my actions for these logs were: 1. Boot 2. Sign in 3. Launch Firefox and navigate to my Nextcloud instance 4. Generate an app specific password (I use two-factor) 5. Add the Nextcloud account in the Online Accounts settings page. 6. Open the calendar app to make sure it didn't miraculously work this time. Worth noting is that I have the exact same issue in two different installations of the same 20.04 daily iso, so its not an issue specific to this particular installation. Tomorrow I'll see if I can set up an Endeavor OS install in a VM to see if it happens on a different distro running Gnome 3.36. Also, just wanted to say this is a small bump in an otherwise stellar looking release. Appreciate all the work you guys do at Canonical. ** Attachment added: "results of `journalctl -b 0` after attempting to add nextcloud account and not having it show up in the calendar app." https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1871019/+attachment/5348302/+files/logs.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1871019 Title: Nextcloud account added to Online Accounts does not populate Calendar apps (WebDAV file sharing does work) Status in gnome-online-accounts package in Ubuntu: Incomplete Bug description: My Nextcloud server was working fine with previous versions of Ubuntu, but on the 20.04 daily when I add my Nextcloud account it does not populate my Calendars or todo lists. It does give me file access via WebDAV. Server is working fine as far as I'm aware. Going to Settings -> Administration - Overview shows me any configuration issues it can detect, currently the only error there is related to background job execution (which is only relevant to the News app if I'm not mistaken). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-online-accounts 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 5 23:59:55 2020 InstallationDate: Installed on 2020-04-03 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1871019/+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 1870837] Re: hcitool lescan says 'Set scan parameters failed: Input/output error'
Hmm, I think comment #21 got it right. hcitool has not been supported for years. Arguably we shouldn't be shipping it. But nobody is going to maintain it as far as I can tell. ** Changed in: bluez (Ubuntu) Status: New => Won't Fix -- 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/1870837 Title: hcitool lescan says 'Set scan parameters failed: Input/output error' Status in bluez package in Ubuntu: Won't Fix Bug description: Hi, after some testing with Ubuntu 20.04 beta I couldn't get hcitool lescan working. I get the following error: hcitool lescan Set scan parameters failed: Input/output error Bluetooth hardware: hci0: Type: Primary Bus: USB BD Address: 04:EA:56:21:xx:xx ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1605 acl:0 sco:0 events:123 errors:0 TX bytes:5801 acl:0 sco:0 commands:123 errors:0 Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'xx' Class: 0x200104 Service Classes: Audio Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x100 LMP Version: 5.1 (0xa) Subversion: 0x100 Manufacturer: Intel Corp. (2) It is not hardware related, since I get the same error with a USB bluetooth dongle: hcitool -i hci1 lescan Set scan parameters failed: Input/output error hcitool scan is working fine on both devices; bluetoothctl is also working and able to find ble devices. I would normally prefer bluetoothctl, but I got a software which is based on hcitool. dmesg shows this errors: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! Bluez version: bluez 5.53-0ubuntu2 amd64 System: Distributor ID: Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 Codename: focal --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root ro ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/23/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0075.2019.1023.1448 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0075.2019.1023.1448:bd10/23/2019:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 04:EA:56:21:1E:D3 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17030 acl:0 sco:0 events:2764 errors:0 TX bytes:677849 acl:0 sco:0 commands:2757 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1870837/+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 1871275] Re: package ca-certificates 20170717~16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- 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/1871275 Title: package ca-certificates 20170717~16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in ca-certificates package in Ubuntu: New Bug description: packages failed to install ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ca-certificates 20170717~16.04.2 ProcVersionSignature: Ubuntu 4.4.0-176.206-generic 4.4.211 Uname: Linux 4.4.0-176-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 Date: Mon Apr 6 20:58:46 2020 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-04-08 (1825 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: ca-certificates Title: package ca-certificates 20170717~16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1871275/+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 1871275] [NEW] package ca-certificates 20170717~16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: packages failed to install ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ca-certificates 20170717~16.04.2 ProcVersionSignature: Ubuntu 4.4.0-176.206-generic 4.4.211 Uname: Linux 4.4.0-176-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 Date: Mon Apr 6 20:58:46 2020 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-04-08 (1825 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: ca-certificates Title: package ca-certificates 20170717~16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ca-certificates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- 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/1871275 Title: package ca-certificates 20170717~16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in ca-certificates package in Ubuntu: New Bug description: packages failed to install ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ca-certificates 20170717~16.04.2 ProcVersionSignature: Ubuntu 4.4.0-176.206-generic 4.4.211 Uname: Linux 4.4.0-176-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 Date: Mon Apr 6 20:58:46 2020 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-04-08 (1825 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: ca-certificates Title: package ca-certificates 20170717~16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1871275/+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 1869036] Re: package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package
*** This bug is a duplicate of bug 1869035 *** https://bugs.launchpad.net/bugs/1869035 ** Information type changed from Private Security to Public Security -- 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/1869036 Title: package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 Status in pulseaudio package in Ubuntu: New Bug description: i wanted to install wine 5.0 and there is errors ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpulse0 (not installed) ProcVersionSignature: Ubuntu 4.15.0-91.92~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.22 Architecture: amd64 Date: Wed Mar 25 16:57:57 2020 DuplicateSignature: package:libpulse0:(not installed) Unpacking libpulse0:i386 (1:8.0-0ubuntu3.10) ... dpkg: error processing archive /var/cache/apt/archives/libpulse0_1%3a8.0-0ubuntu3.10_i386.deb (--unpack): trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 ErrorMessage: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 InstallationDate: Installed on 2017-09-28 (908 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: pulseaudio Title: package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1869036/+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 1871271] [NEW] Laptop disconnects from Wi-Fi despite being in range until I turn Airplane mode on and off again
Public bug reported: This happened when I opened Discord while loading CSPAN on my FireFox browser, suddenly the connection dropped! network-manager: Installed: 1.10.6-2ubuntu1.4 Candidate: 1.10.6-2ubuntu1.4 Version table: *** 1.10.6-2ubuntu1.4 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.10.6-2ubuntu1.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.10.6-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages This issue also occurs on ubuntu 19.10 and 20.04 current daily build. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.4 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Date: Mon Apr 6 21:36:04 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-04-04 (3 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 20600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE NETGEAR18 4c46a7b6-0545-43ef-b9bb-adcd9750847e wifi 1586223271 Mon 06 Apr 2020 09:34:31 PM EDT yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes wlp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- Wired connection 1 72505ff5-ec1c-36b6-b1f3-f3188add1bd5 ethernet 1586219071 Mon 06 Apr 2020 08:24:31 PM EDT yes 4294966297no /org/freedesktop/NetworkManager/Settings/2 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 NETGEAR18 4c46a7b6-0545-43ef-b9bb-adcd9750847e /org/freedesktop/NetworkManager/ActiveConnection/1 enp1s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected (site only) started limited enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Screenshot from 2020-04-06 21-37-17.png" https://bugs.launchpad.net/bugs/1871271/+attachment/5348270/+files/Screenshot%20from%202020-04-06%2021-37-17.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1871271 Title: Laptop disconnects from Wi-Fi despite being in range until I turn Airplane mode on and off again Status in network-manager package in Ubuntu: New Bug description: This happened when I opened Discord while loading CSPAN on my FireFox browser, suddenly the connection dropped! network-manager: Installed: 1.10.6-2ubuntu1.4 Candidate: 1.10.6-2ubuntu1.4 Version table: *** 1.10.6-2ubuntu1.4 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.10.6-2ubuntu1.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.10.6-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages This issue also occurs on ubuntu 19.10 and 20.04 current daily build. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.4 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion:
[Touch-packages] [Bug 1871260] Re: update-initramfs Error 24 (EMFILE? == Too many open files?)
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1871260 Title: update-initramfs Error 24 (EMFILE? == Too many open files?) Status in initramfs-tools package in Ubuntu: New Bug description: $ sudo apt-get dist-upgrade Fails with: Setting up linux-image-5.3.0-46-generic (5.3.0-46.38) ... Processing triggers for linux-image-5.3.0-46-generic (5.3.0-46.38) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 5.3.0-46-generic ...done. /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.3.0-46-generic I: The initramfs will attempt to resume from /dev/nvme1n1p3 I: (UUID=03bd380f-5d5c-433d-9047-0ca550fef461) I: Set the RESUME variable to override this. Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 If "Error 24" means errno==24 then it is EMFILE (Too many open files). Re-running produces an identical failure. There is nothing unusual going on in the machine. Just rebooted, actually. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-46-generic 5.3.0-46.38 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jima 6601 F pulseaudio tu2 10212 F pulseaudio Date: Mon Apr 6 16:48:05 2020 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2020-03-24 (13 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-45-generic root=UUID=7c21c040-30e8-456e-bcd9-5f4bcfc2fc92 ro toram priority=low quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 RelatedPackageVersions: grub-pc N/A SourcePackage: initramfs-tools Title: package linux-image-5.3.0-46-generic 5.3.0-46.38 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0605 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z370-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0605:bd12/01/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1871260/+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 1871261] Re: package ufw 0.36-6 failed to install/upgrade: end of file on stdin at conffile prompt
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1871261 Title: package ufw 0.36-6 failed to install/upgrade: end of file on stdin at conffile prompt Status in ufw package in Ubuntu: New Bug description: No action on my part resulted in a report problem dialog. I have never modified the ufw configuration through the life of this install, which has come from 18.04 thru 19.04 and 19.10 to arrive at 20.04. Guessing someone made a typo in packaging. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: ufw 0.36-6 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu24 AptOrdering: ufw:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Apr 7 06:45:08 2020 ErrorMessage: end of file on stdin at conffile prompt InstallationDate: Installed on 2017-04-14 (1088 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-is-python2, 2.7.17-3 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.1 SourcePackage: ufw Title: package ufw 0.36-6 failed to install/upgrade: end of file on stdin at conffile prompt UpgradeStatus: Upgraded to focal on 2020-04-06 (0 days ago) mtime.conffile..etc.default.ufw: 2019-07-28T20:35:23.745568 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1871261/+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 1871261] [NEW] package ufw 0.36-6 failed to install/upgrade: end of file on stdin at conffile prompt
Public bug reported: No action on my part resulted in a report problem dialog. I have never modified the ufw configuration through the life of this install, which has come from 18.04 thru 19.04 and 19.10 to arrive at 20.04. Guessing someone made a typo in packaging. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: ufw 0.36-6 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu24 AptOrdering: ufw:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Apr 7 06:45:08 2020 ErrorMessage: end of file on stdin at conffile prompt InstallationDate: Installed on 2017-04-14 (1088 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-is-python2, 2.7.17-3 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.1 SourcePackage: ufw Title: package ufw 0.36-6 failed to install/upgrade: end of file on stdin at conffile prompt UpgradeStatus: Upgraded to focal on 2020-04-06 (0 days ago) mtime.conffile..etc.default.ufw: 2019-07-28T20:35:23.745568 ** Affects: ufw (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1871261 Title: package ufw 0.36-6 failed to install/upgrade: end of file on stdin at conffile prompt Status in ufw package in Ubuntu: New Bug description: No action on my part resulted in a report problem dialog. I have never modified the ufw configuration through the life of this install, which has come from 18.04 thru 19.04 and 19.10 to arrive at 20.04. Guessing someone made a typo in packaging. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: ufw 0.36-6 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu24 AptOrdering: ufw:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Apr 7 06:45:08 2020 ErrorMessage: end of file on stdin at conffile prompt InstallationDate: Installed on 2017-04-14 (1088 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-is-python2, 2.7.17-3 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.1 SourcePackage: ufw Title: package ufw 0.36-6 failed to install/upgrade: end of file on stdin at conffile prompt UpgradeStatus: Upgraded to focal on 2020-04-06 (0 days ago) mtime.conffile..etc.default.ufw: 2019-07-28T20:35:23.745568 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1871261/+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 1871241] Re: Mi computador no reproduce ningun tipo de sonido ni con audifono y sin ellos tampoco
** Package changed: ubuntu => alsa-driver (Ubuntu) -- 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/1871241 Title: Mi computador no reproduce ningun tipo de sonido ni con audifono y sin ellos tampoco Status in alsa-driver package in Ubuntu: New Bug description: Tengo un computador hp con sistema operativo ubuntu 16.04 y de un momento a otro no reproduce ningun sonido, intento reiniciarlo y algunas veces si funciona y reproduce sonido, pero no reconoce los audifonos y tambien existen momentos como esta actualmente que no reproduce nada y tampoco reconoce los audifonos ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base (not installed) ProcVersionSignature: Ubuntu 4.4.0-176.206-generic 4.4.211 Uname: Linux 4.4.0-176-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 6 16:43:17 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-atami161222-xenial-amd64-20170321-0 InstallationDate: Installed on 2020-04-02 (4 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20170321-07:27 ProcEnviron: LANGUAGE=es_CO:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CO.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1871241/+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 1871260] [NEW] update-initramfs Error 24 (EMFILE? == Too many open files?)
Public bug reported: $ sudo apt-get dist-upgrade Fails with: Setting up linux-image-5.3.0-46-generic (5.3.0-46.38) ... Processing triggers for linux-image-5.3.0-46-generic (5.3.0-46.38) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 5.3.0-46-generic ...done. /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.3.0-46-generic I: The initramfs will attempt to resume from /dev/nvme1n1p3 I: (UUID=03bd380f-5d5c-433d-9047-0ca550fef461) I: Set the RESUME variable to override this. Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 If "Error 24" means errno==24 then it is EMFILE (Too many open files). Re-running produces an identical failure. There is nothing unusual going on in the machine. Just rebooted, actually. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-46-generic 5.3.0-46.38 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jima 6601 F pulseaudio tu2 10212 F pulseaudio Date: Mon Apr 6 16:48:05 2020 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2020-03-24 (13 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-45-generic root=UUID=7c21c040-30e8-456e-bcd9-5f4bcfc2fc92 ro toram priority=low quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 RelatedPackageVersions: grub-pc N/A SourcePackage: initramfs-tools Title: package linux-image-5.3.0-46-generic 5.3.0-46.38 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0605 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z370-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0605:bd12/01/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1871260 Title: update-initramfs Error 24 (EMFILE? == Too many open files?) Status in initramfs-tools package in Ubuntu: New Bug description: $ sudo apt-get dist-upgrade Fails with: Setting up linux-image-5.3.0-46-generic (5.3.0-46.38) ... Processing triggers for linux-image-5.3.0-46-generic (5.3.0-46.38) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 5.3.0-46-generic ...done. /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.3.0-46-generic I: The initramfs will attempt to resume from /dev/nvme1n1p3 I: (UUID=03bd380f-5d5c-433d-9047-0ca550fef461) I: Set the RESUME variable to override this. Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 If "Error 24" means errno==24 then it is EMFILE (Too many open files). Re-running produces an identical failure. There is nothing unusual going on in the machine. Just rebooted, actually. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-46-generic 5.3.0-46.38 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jima 6601 F pulseaudio tu2 10212 F pulseaudio Date: Mon Apr 6 16:48:05 2020 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2020-03-24 (13
[Touch-packages] [Bug 1871241] [NEW] Mi computador no reproduce ningun tipo de sonido ni con audifono y sin ellos tampoco
You have been subscribed to a public bug: Tengo un computador hp con sistema operativo ubuntu 16.04 y de un momento a otro no reproduce ningun sonido, intento reiniciarlo y algunas veces si funciona y reproduce sonido, pero no reconoce los audifonos y tambien existen momentos como esta actualmente que no reproduce nada y tampoco reconoce los audifonos ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base (not installed) ProcVersionSignature: Ubuntu 4.4.0-176.206-generic 4.4.211 Uname: Linux 4.4.0-176-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 6 16:43:17 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-atami161222-xenial-amd64-20170321-0 InstallationDate: Installed on 2020-04-02 (4 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20170321-07:27 ProcEnviron: LANGUAGE=es_CO:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CO.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- Mi computador no reproduce ningun tipo de sonido ni con audifono y sin ellos tampoco https://bugs.launchpad.net/bugs/1871241 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver 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 1869868] Re: bug
** Information type changed from Private Security to Public -- 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/1869868 Title: bug Status in xorg package in Ubuntu: New Bug description: bug ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 31 13:22:32 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [8086:22b0] (rev 36) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [8086:7270] InstallationDate: Installed on 2020-03-31 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 040b:2011 Weltrend Semiconductor Bus 001 Device 003: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory Bus 001 Device 002: ID 048d:1345 Integrated Technology Express, Inc. Multi Cardreader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: AZW Z83 II ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=7843659a-587f-48ec-86b4-df2d315abde7 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: YB1007 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrYB1007:bd08/17/2017:svnAZW:pnZ83II:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnCherryTrailCR:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z83 II dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: AZW version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1869868/+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 1869629] Re: please add /etc/mdns.allow to /etc/apparmor.d/abstractions/mdns
FYI, I submitted https://github.com/snapcore/snapd/pull/8443 for this. ** Changed in: snapd Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1869629 Title: please add /etc/mdns.allow to /etc/apparmor.d/abstractions/mdns Status in snapd: In Progress Status in apparmor package in Ubuntu: Fix Released Status in chrony package in Ubuntu: Invalid Bug description: In focal users of mdns get denials in apparmor confined applications. An exampel can be found in the original bug below. It seems it is a common pattern, see https://github.com/lathiat/nss-mdns#etcmdnsallow Therefore I'm asking to add /etc/mdns.allow r, to the file /etc/apparmor.d/abstractions/mdns" by default. --- original bug --- Many repetitions of audit: type=1400 audit(1585517168.705:63): apparmor="DENIED" operation="open" profile="/usr/sbin/chronyd" name="/etc/mdns.allow" pid=1983815 comm="chronyd" requested_mask="r" denied_mask="r" fsuid=123 ouid=0 in log. I use libnss-mdns for .local name resolution, so /etc/nsswitch.conf contains hosts: files mdns [NOTFOUND=return] myhostname dns and /etc/mnds.allow contains the domains to resolve with mDNS (in may case, "local." and "local"; see /usr/share/doc/libnss- mdns/README.html.) Presumably cronyd calls a gethostbyX() somewhere, thus eventually trickling down through the name service switch and opening /etc/mdns.allow, which the AppArmor profile in the chrony package does not allow. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: chrony 3.5-6ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 Date: Sun Mar 29 15:02:39 2020 InstallationDate: Installed on 2020-03-26 (3 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200326) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chrony UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1869629/+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 1869024] Re: add support for DynamicUser feature of systemd
FYI, I added these accesses in https://github.com/snapcore/snapd/pull/8443 ** Also affects: snapd Importance: Undecided Status: New ** Changed in: snapd Status: New => In Progress ** Changed in: snapd Assignee: (unassigned) => Jamie Strandboge (jdstrand) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1869024 Title: add support for DynamicUser feature of systemd Status in snapd: In Progress Status in apparmor package in Ubuntu: In Progress Bug description: systemd offers to create dynamic (and semi-stable) users for services. This causes many services using Apparmor profiles to trigger those denials (even when they don't use the DynamicUser feature): audit: type=1107 audit(1585076282.591:30): pid=621 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/systemd1" interface="org.freedesktop.systemd1.Manager" member="GetDynamicUsers" mask="send" name="org.freedesktop.systemd1" pid=709 label="/usr/sbin/squid" peer_pid=1 peer_label="unconfined" And more recently with systemd 245 this also get shown: audit: type=1400 audit(1585139000.628:39): apparmor="DENIED" operation="open" profile="/usr/sbin/squid" name="/run/systemd/userdb/" pid=769 comm="squid" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Additional information: # lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 # uname -a Linux foo.example.com 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-cache policy apparmor squid apparmor: Installed: 2.13.3-7ubuntu2 Candidate: 2.13.3-7ubuntu2 Version table: *** 2.13.3-7ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status squid: Installed: 4.10-1ubuntu1 Candidate: 4.10-1ubuntu1 Version table: *** 4.10-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1869024/+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 1870483] Re: package liblxc-common 1:4.0.0-0ubuntu2 failed to install/upgrade: trying to overwrite '/usr/share/man/ja/man1/lxc-user-nic.1.gz', which is also in package lxc-utils
This bug was fixed in the package lxc - 1:4.0.1-0ubuntu1 --- lxc (1:4.0.1-0ubuntu1) focal; urgency=medium * New upstream bugfix release (4.0.1): - Tweak systemd ordering (start after remote-fs.target) - Fix various issues around attach and cgroups - Fix shutdown timeout not working on pidfd systems - Fix cgroup issue on 4.9 kernel - Fix write issues in /dev/stdout * Fix upgrade ordering (LP: #1870483) * Update lintian overrides: - Drop epoch bump override (no longer detecting it) - Add /usr/libexec override (LXC only uses /usr/lib) -- Stéphane Graber Mon, 06 Apr 2020 16:24:28 -0400 ** Changed in: lxc (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1870483 Title: package liblxc-common 1:4.0.0-0ubuntu2 failed to install/upgrade: trying to overwrite '/usr/share/man/ja/man1/lxc-user-nic.1.gz', which is also in package lxc-utils 3.0.4-0ubuntu2 Status in lxc package in Ubuntu: Fix Released Bug description: . ProblemType: Package DistroRelease: Ubuntu 20.04 Package: liblxc-common 1:4.0.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 Date: Fri Apr 3 08:00:56 2020 ErrorMessage: trying to overwrite '/usr/share/man/ja/man1/lxc-user-nic.1.gz', which is also in package lxc-utils 3.0.4-0ubuntu2 InstallationDate: Installed on 2018-04-14 (719 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=0af0a12d-3b1e-4708-89c4-73f666ddc618 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu1 PythonDetails: N/A SourcePackage: lxc Title: package liblxc-common 1:4.0.0-0ubuntu2 failed to install/upgrade: trying to overwrite '/usr/share/man/ja/man1/lxc-user-nic.1.gz', which is also in package lxc-utils 3.0.4-0ubuntu2 UpgradeStatus: Upgraded to focal on 2020-03-08 (25 days ago) defaults.conf: lxc.net.0.type = veth lxc.net.0.link = lxcbr0 lxc.net.0.flags = up lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1870483/+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 1871023] Re: json_gvariant_deserialize can fail due to unrelated code setting errno
** Changed in: json-glib (Ubuntu Eoan) Status: New => Fix Committed ** Changed in: json-glib (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-glib in Ubuntu. https://bugs.launchpad.net/bugs/1871023 Title: json_gvariant_deserialize can fail due to unrelated code setting errno Status in json-glib package in Ubuntu: Fix Committed Status in json-glib source package in Bionic: Fix Committed Status in json-glib source package in Eoan: Fix Committed Status in json-glib source package in Focal: Fix Committed Bug description: [Impact] json_gvariant_deserialize can fail due to unrelated code setting errno, this is causing snapd-glib to not be able to decode responses from snapd. Fixed in https://gitlab.gnome.org/GNOME/json-glib/-/merge_requests/22 [Test Case] 1. Run GNOME Software from the command line 2. Browse to postman Expected result: Errors are not shown on the command line Observed result: The following errors are shown on the command line: 05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed 05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed 05:17:29:0877 Gs not GsPlugin error g-io-error-quark:35: Invalid string value converting to GVariant 05:17:29:0877 Gs not handling error failed for action refine: Invalid string value converting to GVariant (These errors may not always occur, and is likely racy). [Regression Potential] Small risk of introducing other bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1871023/+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 1871023] Re: json_gvariant_deserialize can fail due to unrelated code setting errno
** Description changed: [Impact] json_gvariant_deserialize can fail due to unrelated code setting errno, this is causing snapd-glib to not be able to decode responses from snapd. Fixed in https://gitlab.gnome.org/GNOME/json-glib/-/merge_requests/22 [Test Case] 1. Run GNOME Software from the command line 2. Browse to postman Expected result: - Postman is shown with correct data + Errors are not shown on the command line Observed result: - Not all channels shown, the following shown on the command line: + The following errors are shown on the command line: 05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed 05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed 05:17:29:0877 Gs not GsPlugin error g-io-error-quark:35: Invalid string value converting to GVariant 05:17:29:0877 Gs not handling error failed for action refine: Invalid string value converting to GVariant (These errors may not always occur, and is likely racy). [Regression Potential] Small risk of introducing other bugs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-glib in Ubuntu. https://bugs.launchpad.net/bugs/1871023 Title: json_gvariant_deserialize can fail due to unrelated code setting errno Status in json-glib package in Ubuntu: Fix Committed Status in json-glib source package in Bionic: New Status in json-glib source package in Eoan: New Status in json-glib source package in Focal: Fix Committed Bug description: [Impact] json_gvariant_deserialize can fail due to unrelated code setting errno, this is causing snapd-glib to not be able to decode responses from snapd. Fixed in https://gitlab.gnome.org/GNOME/json-glib/-/merge_requests/22 [Test Case] 1. Run GNOME Software from the command line 2. Browse to postman Expected result: Errors are not shown on the command line Observed result: The following errors are shown on the command line: 05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed 05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed 05:17:29:0877 Gs not GsPlugin error g-io-error-quark:35: Invalid string value converting to GVariant 05:17:29:0877 Gs not handling error failed for action refine: Invalid string value converting to GVariant (These errors may not always occur, and is likely racy). [Regression Potential] Small risk of introducing other bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1871023/+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 1870729] Re: DHCP Server regularly killed code=killed, status=6/ABRT
Does adjusting /etc/apparmor.d/usr.sbin.dhcpd to have:
owner @{PROC}/[0-9]*/comm r,
owner @{PROC}/[0-9]*/task/[0-9]*/comm r,
resolve the issue for you? Be sure to load the policy into the kernel
with: sudo apparmor_parser -r /etc/apparmor.d/usr.sbin.dhcpd before
performing your testing.
** Changed in: isc-dhcp (Ubuntu)
Importance: Undecided => High
** Changed in: isc-dhcp (Ubuntu)
Status: New => In Progress
** Changed in: isc-dhcp (Ubuntu)
Milestone: None => ubuntu-20.04
** Changed in: isc-dhcp (Ubuntu)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1870729
Title:
DHCP Server regularly killed code=killed, status=6/ABRT
Status in isc-dhcp package in Ubuntu:
In Progress
Bug description:
On Ubuntu 20.04 The idc-dhcp- server version is
isc-dhcp-server:
Installed: (none)
Candidate: 4.4.1-2.1ubuntu3
Version table:
4.4.1-2.1ubuntu3 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
The DHCP server is being regularly killed, when searching google the bug
looks very similar to an older bug regarding accessing a lease file, that was
fixed year ago. As a temporary fix in systemd I have enabled a restart every
time the main process fails. The error got worse when i start to run a pair of
dhcp servers syncing state between each other
I regularly see the following in the syslog
Apr 4 00:04:55 gw sh[1500]: ../../../../lib/isc/unix/socket.c:3361:
INSIST(!sock->pending_send) failed, back trace
Apr 4 00:04:55 gw sh[1500]: #0 0x7f36befeda4a in ??
Apr 4 00:04:55 gw sh[1500]: #1 0x7f36befed980 in ??
Apr 4 00:04:55 gw sh[1500]: #2 0x7f36bf0297e1 in ??
Apr 4 00:04:55 gw sh[1500]: #3 0x7f36bedd0609 in ??
Apr 4 00:04:55 gw sh[1500]: #4 0x7f36bef0c153 in ??
Apr 4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Main process exited,
code=killed, status=6/ABRT
Apr 4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Failed with result
'signal'.
Apr 4 00:05:00 gw systemd[1]: isc-dhcp-server.service: Scheduled restart
job, restart counter is at 3.
Apr 4 00:05:00 gw systemd[1]: Stopped ISC DHCP IPv4 server.
Apr 4 00:05:00 gw systemd[1]: Started ISC DHCP IPv4 server.
Apr 4 00:05:00 gw kernel: [ 3508.161248] audit: type=1400
audit(1585958700.678:46): apparmor="DENIED" operation="open"
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2068/comm" pid=2049
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
Apr 4 00:05:00 gw dhcpd[2049]: Internet Systems Consortium DHCP Server 4.4.1
Apr 4 00:05:00 gw sh[2049]: Internet Systems Consortium DHCP Server 4.4.1
Apr 4 00:05:00 gw sh[2049]: Copyright 2004-2018 Internet Systems Consortium.
Apr 4 00:05:00 gw sh[2049]: All rights reserved.
Apr 4 00:05:00 gw sh[2049]: For info, please visit
https://www.isc.org/software/dhcp/
Apr 4 00:05:00 gw dhcpd[2049]: Copyright 2004-2018 Internet Systems
Consortium.
Apr 4 00:05:00 gw dhcpd[2049]: All rights reserved.
Apr 4 00:05:00 gw dhcpd[2049]: For info, please visit
https://www.isc.org/software/dhcp/
Apr 4 00:05:00 gw kernel: [ 3508.161561] audit: type=1400
audit(1585958700.678:47): apparmor="DENIED" operation="open"
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2069/comm" pid=2049
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
Apr 4 00:05:00 gw kernel: [ 3508.161563] audit: type=1400
audit(1585958700.682:48): apparmor="DENIED" operation="open"
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2070/comm" pid=2049
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
Apr 4 00:05:00 gw dhcpd[2049]: Config file: /etc/dhcp/dhcpd.conf
Apr 4 00:05:00 gw sh[2049]: Config file: /etc/dhcp/dhcpd.conf
Apr 4 00:05:00 gw sh[2049]: Database file: /var/lib/dhcp/dhcpd.leases
Apr 4 00:05:00 gw sh[2049]: PID file: /run/dhcp-server/dhcpd.pid
Apr 4 00:05:00 gw dhcpd[2049]: Database file: /var/lib/dhcp/dhcpd.leases
Apr 4 00:05:00 gw dhcpd[2049]: PID file: /run/dhcp-server/dhcpd.pid
Apr 4 00:05:00 gw dhcpd[2049]: Wrote 0 deleted host decls to leases file.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1870729/+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 1871023] Re: json_gvariant_deserialize can fail due to unrelated code setting errno
** Changed in: json-glib (Ubuntu Focal) Status: New => Fix Committed ** Changed in: json-glib (Ubuntu Focal) Importance: Undecided => High ** Changed in: json-glib (Ubuntu Eoan) Importance: Undecided => High ** Changed in: json-glib (Ubuntu Bionic) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-glib in Ubuntu. https://bugs.launchpad.net/bugs/1871023 Title: json_gvariant_deserialize can fail due to unrelated code setting errno Status in json-glib package in Ubuntu: Fix Committed Status in json-glib source package in Bionic: New Status in json-glib source package in Eoan: New Status in json-glib source package in Focal: Fix Committed Bug description: [Impact] json_gvariant_deserialize can fail due to unrelated code setting errno, this is causing snapd-glib to not be able to decode responses from snapd. Fixed in https://gitlab.gnome.org/GNOME/json-glib/-/merge_requests/22 [Test Case] 1. Run GNOME Software from the command line 2. Browse to postman Expected result: Postman is shown with correct data Observed result: Not all channels shown, the following shown on the command line: 05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed 05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed 05:17:29:0877 Gs not GsPlugin error g-io-error-quark:35: Invalid string value converting to GVariant 05:17:29:0877 Gs not handling error failed for action refine: Invalid string value converting to GVariant (These errors may not always occur, and is likely racy). [Regression Potential] Small risk of introducing other bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1871023/+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 1285444] Re: Login Successful, Desktop Never Loads
This bug report is from 2014. I get this issue (return almost immediately to the login screen) in Ubuntu 20.04 Beta with the 5.4.0-21 kernel. But with the immediate previous kernel, 5.4.0-18 works and I get a desktop session. Anyone who found an existing report on such an issue? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1285444 Title: Login Successful, Desktop Never Loads Status in at-spi2-core package in Ubuntu: Triaged Bug description: Here is what I encounter 1. Boot computer, boot proceeds normally 2. Reach standard Ubuntu login screen, nothing seems to be amiss 3. Enter user name and password 4. Login disappears, just see the pink "Ubuntu 14.04" background The desktop never loads, not even after ~30 minutes. The launcher never appears, and the Desktop background never changes to the user- configured background. Other features: * Cursor works fine, it can be moved around the screen * No error messages pop up * ALT+F1 etc. can be used to switch to different TTYs; all files on the system appear to be intact * Print screen button works (I will upload a screen shot when I get a chance to copy it onto a USB drive) * Hitting power button pops up a window prompting the user to decide whether to shut down * CTRL+ALT+DELETE prompts the user to log out * Desktop does not load on any user accounts, including the guest account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1285444/+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 1871023] Re: json_gvariant_deserialize can fail due to unrelated code setting errno
** Changed in: json-glib (Ubuntu Bionic) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: json-glib (Ubuntu Eoan) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: json-glib (Ubuntu Focal) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-glib in Ubuntu. https://bugs.launchpad.net/bugs/1871023 Title: json_gvariant_deserialize can fail due to unrelated code setting errno Status in json-glib package in Ubuntu: New Status in json-glib source package in Bionic: New Status in json-glib source package in Eoan: New Status in json-glib source package in Focal: New Bug description: [Impact] json_gvariant_deserialize can fail due to unrelated code setting errno, this is causing snapd-glib to not be able to decode responses from snapd. Fixed in https://gitlab.gnome.org/GNOME/json-glib/-/merge_requests/22 [Test Case] 1. Run GNOME Software from the command line 2. Browse to postman Expected result: Postman is shown with correct data Observed result: Not all channels shown, the following shown on the command line: 05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed 05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed 05:17:29:0877 Gs not GsPlugin error g-io-error-quark:35: Invalid string value converting to GVariant 05:17:29:0877 Gs not handling error failed for action refine: Invalid string value converting to GVariant (These errors may not always occur, and is likely racy). [Regression Potential] Small risk of introducing other bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1871023/+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 1870408] Re: casper-md5check should leave a breadcrumb which apport, ubiquity, subiquity could use
I think the logic to parse the json file and write the report keys
should exist in hookutils.py that way it is usable by the general
"ubuntu.py" hook and the ubiquity and subiquity hooks.
It'd be good if this file existed on an installed system. Will it be
copied from the live system to the installed one?
--
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/1870408
Title:
casper-md5check should leave a breadcrumb which apport, ubiquity,
subiquity could use
Status in subiquity:
New
Status in apport package in Ubuntu:
Triaged
Status in casper package in Ubuntu:
In Progress
Status in ubiquity package in Ubuntu:
New
Bug description:
casper-md5check should leave a breadcrumb which apport & ubiquity can
pick up. (subiquity too)
There will be a file called:
/run/casper-md5check.json
If it does not exist, or is empty the check did not run enough to
validate anything. Treat as skip.
If it has content it will have:
{
"checksum_missmatch" : [
"./pics/red-upperleft.png",
"./pics/red-lowerleft.png"
],
"result" : "fail"
}
optional checksum_missmatch key, which will have a list of strings
that are files that failed md5sum.
result key, which can have string values "pass" "fail" "skip".
One can use python's json or yaml safe_load to parse the file into a
dictionary.
To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1870408/+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 1870059] Re: gtk+3.0 ftbfs in focal (all archs)
https://launchpad.net/ubuntu/+source/gtk+3.0/3.24.14-1ubuntu2 ** Changed in: ubuntu Status: Confirmed => Fix Released -- 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/1870059 Title: gtk+3.0 ftbfs in focal (all archs) Status in gtk+3.0 package in Ubuntu: Fix Released Bug description: https://launchpadlibrarian.net/47194/buildlog_ubuntu-focal- amd64.gtk+3.0_3.24.14-1ubuntu1_BUILDING.txt.gz seen in the second focal test rebuild make[2]: *** [Makefile:749: check-recursive] Error 1 make[2]: Target 'check' not remade because of errors. make[2]: Leaving directory '/build/gtk+3.0-ucFLVC/gtk+3.0-3.24.14/debian/build/deb' dh_auto_test: error: cd debian/build/deb && make -j4 check VERBOSE=1 -k check -j1 returned exit code 2 make[1]: *** [debian/rules:205: override_dh_auto_test] Error 25 make[1]: Leaving directory '/build/gtk+3.0-ucFLVC/gtk+3.0-3.24.14' make: *** [debian/rules:135: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1870059/+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 1870059] [NEW] gtk+3.0 ftbfs in focal (all archs)
You have been subscribed to a public bug: https://launchpadlibrarian.net/47194/buildlog_ubuntu-focal- amd64.gtk+3.0_3.24.14-1ubuntu1_BUILDING.txt.gz seen in the second focal test rebuild make[2]: *** [Makefile:749: check-recursive] Error 1 make[2]: Target 'check' not remade because of errors. make[2]: Leaving directory '/build/gtk+3.0-ucFLVC/gtk+3.0-3.24.14/debian/build/deb' dh_auto_test: error: cd debian/build/deb && make -j4 check VERBOSE=1 -k check -j1 returned exit code 2 make[1]: *** [debian/rules:205: override_dh_auto_test] Error 25 make[1]: Leaving directory '/build/gtk+3.0-ucFLVC/gtk+3.0-3.24.14' make: *** [debian/rules:135: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 ** Affects: gtk+3.0 (Ubuntu) Importance: High Status: Fix Released ** Tags: ftbfs rls-ff-incoming -- gtk+3.0 ftbfs in focal (all archs) https://bugs.launchpad.net/bugs/1870059 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 1871148] Re: services start before apparmor profiles are loaded
I uploaded 2.13.3-7ubuntu4 to address this: https://launchpad.net/ubuntu/+source/apparmor/2.13.3-7ubuntu4 There might be other fixes for zsys, but this should address the issue in snapd. It is currently in unapproved, but a member of the release team will hopefully approve it soon. ** Changed in: apparmor (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: apparmor (Ubuntu Focal) Milestone: None => ubuntu-20.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1871148 Title: services start before apparmor profiles are loaded Status in AppArmor: Invalid Status in apparmor package in Ubuntu: Fix Committed Status in zsys package in Ubuntu: Confirmed Status in apparmor source package in Focal: Fix Committed Status in zsys source package in Focal: Confirmed Bug description: Per discussion with Zyga in #snapd on Freenode, I have hit a race condition where services are being started by the system before apparmor has been started. I have a complete log of my system showing the effect somewhere within at https://paste.ubuntu.com/p/Jyx6gfFc3q/. Restarting apparmor using `sudo systemctl restart apparmor` is enough to bring installed snaps back to full functionality. Previously, when running any snap I would receive the following in the terminal: --- cannot change profile for the next exec call: No such file or directory snap-update-ns failed with code 1: File exists --- Updated to add for Jamie: $ snap version snap2.44.2+20.04 snapd 2.44.2+20.04 series 16 ubuntu 20.04 kernel 5.4.0-21-generic To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1871148/+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 1866611] Re: OpenVPN w. SHA1 signed CA broken after upgrade to 1.1.1d-2ubuntu6
Here is a solution https://forums.openvpn.net/viewtopic.php?t=23979#p79185 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1866611 Title: OpenVPN w. SHA1 signed CA broken after upgrade to 1.1.1d-2ubuntu6 Status in openssl package in Ubuntu: Confirmed Bug description: After upgrading openssl on my Focal-install this morning (upgrade openssl:amd64 1.1.1d-2ubuntu3 1.1.1d-2ubuntu6 per /var/log/dpkg.log), my OpenVPN tunnel refuses to connect to our corporate VPN (from /var/log/syslog): corp-laptop nm-openvpn[4688]: VERIFY ERROR: depth=0, error=CA signature digest algorithm too weak: C=DK, ST=None, L=Copenhagen, O=XX, OU=XX, CN=XX, emailAddress=XX corp-laptop nm-openvpn[4688]: OpenSSL: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed I'm told we're running a SHA1-signed CA, which we're guessing has been deprecated somewhere between -2ubuntu3 and -2ubuntu6. The changelog for -2ubuntu4 mentions importing some upstream changes, but isn't more specific than that: https://changelogs.ubuntu.com/changelogs/pool/main/o/openssl/openssl_1.1 .1d-2ubuntu4/changelog As a work-around, the internet suggests two work-arounds (neither of which has worked for me): 1) Adding the following to /etc/defaults/openssl: OPTARGS="--tls-cipher DEFAULT:@SECLEVEL=0" 2) Adding the following to /etc/ssl/openssl.conf: CipherString= :@SECLEVEL=1 I also tried rolling back the package, but the old version doesn't seem to be available: $ sudo apt install openssl=1.1.1d-2ubuntu3 ... E: Version '1.1.1d-2ubuntu3' for 'openssl' was not found I am no SSL-expert and would appreciate any pointers to get around this. (Our network-dept. does not have the bandwidth to roll over our CA on short notice, so I will need some other way to move ahead). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1866611/+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 1848919] Re: [snap] Permission denied on Private encrypted folder
** Changed in: snapd Status: In Progress => Fix Released ** Changed in: snapd (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1848919 Title: [snap] Permission denied on Private encrypted folder Status in AppArmor: Fix Released Status in snapd: Fix Released Status in apparmor package in Ubuntu: In Progress Status in chromium-browser package in Ubuntu: Invalid Status in snapd package in Ubuntu: Fix Released Bug description: When accessing the Private (/home/username/Private, Encrypted Directory) folder (e.g. via "Link save as...") it shows "Could not read contents of Private, Error opening directory ...: Permission denied" Package: chromium-browser Version: 77.0.3865.120-0ubuntu1~snap1 To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1848919/+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 1869996] Re: Hibernation can NOT work due to incorrect RESUME=
This bug was fixed in the package initramfs-tools - 0.136ubuntu4
---
initramfs-tools (0.136ubuntu4) focal; urgency=medium
* Skip setting mac-address, unless unsupported unpredictable netnames
are used.
-- Dimitri John Ledkov Sat, 04 Apr 2020 23:39:59
+0100
** Changed in: initramfs-tools (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1869996
Title:
Hibernation can NOT work due to incorrect RESUME=
Status in initramfs-tools package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
New
Bug description:
In Ubuntu 18.04 I have the below 4 lines, but in Ubuntu 20.04 (dev
build) these lines are missing:
--- /usr/share/initramfs-tools/init2020-04-01 01:15:20.533208700 +
+++ /usr/share/initramfs-tools/init 2020-04-01 00:59:43.931655200 +
@@ -163,6 +163,10 @@
;;
resume=*)
RESUME="${x#resume=}"
+ case $RESUME in
+ UUID=*)
+RESUME="/dev/disk/by-uuid/${RESUME#UUID=}"
+ esac
;;
resume_offset=*)
resume_offset="${x#resume_offset=}"
As a result, hibernation can not work: the saved state in the swap
partition is lost and no resume happens.
The issue is: when I use the "resume=UUID=533b2cd9-31ac-449b-82ff-
014f09ab0a9c" kernel parameter for hibernation, due to the missing
lines, the variable 'resume' in a later place in "/usr/share
/initramfs-tools/init" is set to "UUID=533b2cd9-31ac-449b-82ff-
014f09ab0a9c" rather than "/dev/disk/by-uuid/533b2cd9-31ac-449b-82ff-
014f09ab0a9c". Next, in /usr/share/initramfs-tools/scripts/local-
premount/resume:
DEV=$(readlink "$resume")
DEV=/sys/class/block/${DEV##*/}/dev
if [ -r "$DEV" ]; then
read -r MAJMIN < "$DEV"
fi
if [ -z "$MAJMIN" ]; then
exit 1
fi
Here the 'readlink' will fail, so $DEV is not pointing to a valid device, and
then $MAJMIN is empty and
we "exit 1", so no resume can happen!
Not sure why the 4 lines are removed in Ubuntu 20.04...
PS, this is my version info:
root@localhost:~# dpkg-query -s initramfs-tools-core
Package: initramfs-tools-core
Status: install ok installed
Priority: optional
Section: utils
Installed-Size: 271
Maintainer: Ubuntu Developers
Architecture: all
Multi-Arch: foreign
Source: initramfs-tools
Version: 0.136ubuntu1
Replaces: initramfs-tools (<< 0.121~)
Depends: busybox-initramfs (>= 1:1.30.1-4ubuntu5~), initramfs-tools-bin (=
0.136ubuntu1), klibc-utils (>= 2.0.4-8~), cpio (>= 2.12), lz4, kmod, udev,
coreutils (>= 8.24), logsave | e2fsprogs (<< 1.45.3-1~)
Suggests: bash-completion
Breaks: busybox-initramfs (<< 1:1.30.1-4ubuntu5~), initramfs-tools (<< 0.121~)
Conffiles:
/etc/initramfs-tools/initramfs.conf 4ec999d424d01b9ca685e65ba0f22a13
Description: generic modular initramfs generator (core tools)
This package contains the mkinitramfs program that can be used to
create a bootable initramfs for a Linux kernel. The initramfs should
be loaded along with the kernel and is then responsible for mounting
the root filesystem and starting the main init system.
Original-Maintainer: Debian kernel team
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1869996/+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 1848919] Re: [snap] Permission denied on Private encrypted folder
** Changed in: apparmor Status: In Progress => Fix Released ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Changed in: apparmor (Ubuntu) Importance: Undecided => Medium ** Changed in: apparmor (Ubuntu) Status: New => In Progress ** Changed in: apparmor (Ubuntu) Assignee: (unassigned) => Jamie Strandboge (jdstrand) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1848919 Title: [snap] Permission denied on Private encrypted folder Status in AppArmor: Fix Released Status in snapd: In Progress Status in apparmor package in Ubuntu: In Progress Status in chromium-browser package in Ubuntu: Invalid Status in snapd package in Ubuntu: Triaged Bug description: When accessing the Private (/home/username/Private, Encrypted Directory) folder (e.g. via "Link save as...") it shows "Could not read contents of Private, Error opening directory ...: Permission denied" Package: chromium-browser Version: 77.0.3865.120-0ubuntu1~snap1 To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1848919/+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 1866611] Re: OpenVPN w. SHA1 signed CA broken after upgrade to 1.1.1d-2ubuntu6
I have the same issue with SecurityKISS VPN. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1866611 Title: OpenVPN w. SHA1 signed CA broken after upgrade to 1.1.1d-2ubuntu6 Status in openssl package in Ubuntu: Confirmed Bug description: After upgrading openssl on my Focal-install this morning (upgrade openssl:amd64 1.1.1d-2ubuntu3 1.1.1d-2ubuntu6 per /var/log/dpkg.log), my OpenVPN tunnel refuses to connect to our corporate VPN (from /var/log/syslog): corp-laptop nm-openvpn[4688]: VERIFY ERROR: depth=0, error=CA signature digest algorithm too weak: C=DK, ST=None, L=Copenhagen, O=XX, OU=XX, CN=XX, emailAddress=XX corp-laptop nm-openvpn[4688]: OpenSSL: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed I'm told we're running a SHA1-signed CA, which we're guessing has been deprecated somewhere between -2ubuntu3 and -2ubuntu6. The changelog for -2ubuntu4 mentions importing some upstream changes, but isn't more specific than that: https://changelogs.ubuntu.com/changelogs/pool/main/o/openssl/openssl_1.1 .1d-2ubuntu4/changelog As a work-around, the internet suggests two work-arounds (neither of which has worked for me): 1) Adding the following to /etc/defaults/openssl: OPTARGS="--tls-cipher DEFAULT:@SECLEVEL=0" 2) Adding the following to /etc/ssl/openssl.conf: CipherString= :@SECLEVEL=1 I also tried rolling back the package, but the old version doesn't seem to be available: $ sudo apt install openssl=1.1.1d-2ubuntu3 ... E: Version '1.1.1d-2ubuntu3' for 'openssl' was not found I am no SSL-expert and would appreciate any pointers to get around this. (Our network-dept. does not have the bandwidth to roll over our CA on short notice, so I will need some other way to move ahead). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1866611/+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 1863532] Re: Invoking "python" brings inappropriate response from command-not-found when python3 installed
Current behavior on focal: $ python Command 'python' not found, did you mean: command 'python3' from deb python3 command 'python ' from deb python-is-python3 $ There's an extra space in the name 'python ', can we get this fixed? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1863532 Title: Invoking "python" brings inappropriate response from command-not-found when python3 installed Status in command-not-found package in Ubuntu: Triaged Status in python3-defaults package in Ubuntu: Triaged Status in command-not-found source package in Focal: Triaged Status in python3-defaults source package in Focal: Triaged Bug description: Ubuntu Mate 20.04 development release, upgraded from 19.10. I don't have python 2.7 installed, but have python 3 installed as per default. Please see ascii-cast at https://asciinema.org/a/SZR20NHz2FN6N6O1hj2Mqmnv8 . Running `python` brings up text from command-not-found which suggests installing `python3` as a solution to the missing command. `python3` is already installed, is a later version than the one indicated by command-not-found and does not supply a binary or symlink named `python`. $ apt policy python python: Installed: (none) Candidate: (none) Version table: 2.7.17-1 -1 100 /var/lib/dpkg/status $ apt policy python3 python3: Installed: 3.8.0-3 Candidate: 3.8.0-3 Version table: *** 3.8.0-3 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status $ apt policy command-not-found command-not-found: Installed: 19.10.0 Candidate: 19.10.0 Version table: *** 19.10.0 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status I don't know whether this is a bug in python3 or command-not-found (the latter of which doesn't seem to have been updated for 20.04 yet). i don't know if it is intentional that `python3` will not provide a binary or symlink named `python`. if that is the case, the output of `command-not-found` should be updated to reflect that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: python3 3.8.0-3 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: MATE Date: Mon Feb 17 01:35:16 2020 InstallationDate: Installed on 2019-10-11 (128 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2) SourcePackage: python3-defaults UpgradeStatus: Upgraded to focal on 2020-02-07 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1863532/+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 1796911] Re: libnss-systemd was denied talking to pid1
** Changed in: apparmor (Ubuntu) Status: Confirmed => In Progress ** Changed in: apparmor (Ubuntu) Assignee: (unassigned) => Jamie Strandboge (jdstrand) ** Changed in: apparmor (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1796911 Title: libnss-systemd was denied talking to pid1 Status in apparmor package in Ubuntu: In Progress Bug description: cosmic apparmor 2.12-4ubuntu8 kernel 4.18.0-8-generic #9-Ubuntu I'm getting these audit messages in dmesg showing apparmor denied errors: [ 68.649187] audit: type=1107 audit(1539094926.655:32): pid=605 uid=105 auid=4294967295 ses=4294967295 subj==unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/systemd1" interface="org.freedesktop.systemd1.Manager" member="GetDynamicUsers" mask="send" name="org.freedesktop.systemd1" pid=1091 label="/usr/sbin/named" peer_pid=1 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=105 hostname=? addr=? terminal=?' [ 161.059989] audit: type=1107 audit(1539095018.957:33): pid=605 uid=105 auid=4294967295 ses=4294967295 subj==unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/systemd1" interface="org.freedesktop.systemd1.Manager" member="GetDynamicUsers" mask="send" name="org.freedesktop.systemd1" pid=1191 label="/usr/sbin/named" peer_pid=1 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=105 hostname=? addr=? terminal=?' [ 437.582034] audit: type=1107 audit(1539095295.553:34): pid=605 uid=105 auid=4294967295 ses=4294967295 subj==unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/systemd1" interface="org.freedesktop.systemd1.Manager" member="GetDynamicUsers" mask="send" name="org.freedesktop.systemd1" pid=1534 label="/usr/sbin/named" peer_pid=1 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=105 hostname=? addr=? terminal=?' [ 468.184231] audit: type=1107 audit(1539095326.159:35): pid=605 uid=105 auid=4294967295 ses=4294967295 subj==unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/systemd1" interface="org.freedesktop.systemd1.Manager" member="GetDynamicUsers" mask="send" name="org.freedesktop.systemd1" pid=1577 label="/usr/sbin/named" peer_pid=1 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=105 hostname=? addr=? terminal=?' I pinged #ubuntu-hardened, and xnox had these comments: ha ahasenack, libnss-systemd was denied talking to pid1 to query dynamicusers i think so i think something somehwere need adjustemnt to allow libnss-systemd to talk to pid1 and call GetDynamicUsers LookupDynamicUserByName LookupDynamicUserByUID GetDynamicUsers as well To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1796911/+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 1869024] Re: add support for DynamicUser feature of systemd
** Changed in: apparmor (Ubuntu) Status: New => Fix Committed ** Changed in: apparmor (Ubuntu) Status: Fix Committed => In Progress ** Changed in: apparmor (Ubuntu) Importance: Undecided => High ** Changed in: apparmor (Ubuntu) Assignee: (unassigned) => Jamie Strandboge (jdstrand) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1869024 Title: add support for DynamicUser feature of systemd Status in apparmor package in Ubuntu: In Progress Bug description: systemd offers to create dynamic (and semi-stable) users for services. This causes many services using Apparmor profiles to trigger those denials (even when they don't use the DynamicUser feature): audit: type=1107 audit(1585076282.591:30): pid=621 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/systemd1" interface="org.freedesktop.systemd1.Manager" member="GetDynamicUsers" mask="send" name="org.freedesktop.systemd1" pid=709 label="/usr/sbin/squid" peer_pid=1 peer_label="unconfined" And more recently with systemd 245 this also get shown: audit: type=1400 audit(1585139000.628:39): apparmor="DENIED" operation="open" profile="/usr/sbin/squid" name="/run/systemd/userdb/" pid=769 comm="squid" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Additional information: # lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 # uname -a Linux foo.example.com 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-cache policy apparmor squid apparmor: Installed: 2.13.3-7ubuntu2 Candidate: 2.13.3-7ubuntu2 Version table: *** 2.13.3-7ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status squid: Installed: 4.10-1ubuntu1 Candidate: 4.10-1ubuntu1 Version table: *** 4.10-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1869024/+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 1871137] Re: Recorded audio is super choppy with today's apt upgrade
After running another apt update && apt upgrade this problem seems to have resolved itself. I hate mysteries :) ** Attachment added: "Non choppy sound. yay." https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871137/+attachment/5347952/+files/Non%20choppy%20sound.%20yay. -- 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/1871137 Title: Recorded audio is super choppy with today's apt upgrade Status in pulseaudio package in Ubuntu: New Bug description: People reported choppy audio coming from me in my morning stand-up call. I thought it might be an issue with our chat system, so I tried recording a sound bite in Audacity both with and without my bluetooth headset. I got the same incredibly choppy sound in either case. I'll attach a clip to the bug if I can so you can see what I mean. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 Date: Mon Apr 6 11:07:37 2020 InstallationDate: Installed on 2020-01-09 (87 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-01-24 (73 days ago) dmi.bios.date: 04/18/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.7.0 dmi.board.name: Alienware 17 R5 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.7.0:bd04/18/2019:svnAlienware:pnAlienware17R5:pvr1.7.0:rvnAlienware:rnAlienware17R5:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware 17 R5 dmi.product.sku: 0877 dmi.product.version: 1.7.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871137/+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 1859581] Re: land oem-getlogs in focal and enable apport-unpack to process apport.gz file
** Branch linked: lp:~ubuntu-core-dev/ubuntu/focal/apport/ubuntu -- 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/1859581 Title: land oem-getlogs in focal and enable apport-unpack to process apport.gz file Status in Apport: New Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: Fix Released Bug description: LP: #1841157 seems forgeting to include oem-getlogs in debian/apport.install. Also, add the attached patch so that apport-unpack can process apport.gz that oem-getlogs generate directly. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1859581/+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 1870893] Re: libdvdread 6.1.0 broke ABI without changing the SONAME
** Changed in: libdvdread (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdvdread in Ubuntu. https://bugs.launchpad.net/bugs/1870893 Title: libdvdread 6.1.0 broke ABI without changing the SONAME Status in libdvdread package in Ubuntu: Fix Released Status in libdvdread package in Debian: Fix Released Bug description: related to bug 1870858.. similar fault different program (parole) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: vlc 3.0.8-4 ProcVersionSignature: Ubuntu 5.4.0-22.26-generic 5.4.29 Uname: Linux 5.4.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Apr 5 05:19:53 2020 InstallationDate: Installed on 2019-12-02 (124 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191130) SourcePackage: vlc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdvdread/+bug/1870893/+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 1871185] [NEW] urls in ubuntu-bugs dialog not really clickable
Public bug reported: when ubuntu-bug report suggests filing a bug report directly in launchpad for snap packages, the displayed url is clickable but the url stops at the first + symbol. see attachment. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: apport 2.20.11-0ubuntu8.8 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CrashReports: 640:1000:124:8919925:2020-03-29 20:16:13.456640958 +0200:2020-03-29 20:16:14.456640958 +0200:/var/crash/_usr_bin_python3.7.1000.crash CurrentDesktop: XFCE Date: Mon Apr 6 19:50:16 2020 InstallationDate: Installed on 2020-03-18 (18 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "ubuntu-bug-dialog.png" https://bugs.launchpad.net/bugs/1871185/+attachment/5347929/+files/ubuntu-bug-dialog.png -- 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/1871185 Title: urls in ubuntu-bugs dialog not really clickable Status in apport package in Ubuntu: New Bug description: when ubuntu-bug report suggests filing a bug report directly in launchpad for snap packages, the displayed url is clickable but the url stops at the first + symbol. see attachment. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: apport 2.20.11-0ubuntu8.8 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CrashReports: 640:1000:124:8919925:2020-03-29 20:16:13.456640958 +0200:2020-03-29 20:16:14.456640958 +0200:/var/crash/_usr_bin_python3.7.1000.crash CurrentDesktop: XFCE Date: Mon Apr 6 19:50:16 2020 InstallationDate: Installed on 2020-03-18 (18 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1871185/+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 1871148] Re: services start before apparmor profiles are loaded
Reassigning the snapd task to apparmor in Ubuntu since it has a patch to rc.apparmor.functions to look for /var/lib/snapd/apparmor/profiles but does not add it to RequiresMountsFor. ** Project changed: snapd => apparmor ** Changed in: apparmor Status: Confirmed => In Progress ** Changed in: apparmor Importance: Critical => Undecided ** Changed in: apparmor Status: In Progress => Invalid ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Changed in: apparmor (Ubuntu Focal) Status: New => In Progress ** Changed in: apparmor (Ubuntu Focal) Importance: Undecided => Critical ** Changed in: apparmor (Ubuntu Focal) Assignee: (unassigned) => Jamie Strandboge (jdstrand) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1871148 Title: services start before apparmor profiles are loaded Status in AppArmor: Invalid Status in apparmor package in Ubuntu: In Progress Status in zsys package in Ubuntu: Confirmed Status in apparmor source package in Focal: In Progress Status in zsys source package in Focal: Confirmed Bug description: Per discussion with Zyga in #snapd on Freenode, I have hit a race condition where services are being started by the system before apparmor has been started. I have a complete log of my system showing the effect somewhere within at https://paste.ubuntu.com/p/Jyx6gfFc3q/. Restarting apparmor using `sudo systemctl restart apparmor` is enough to bring installed snaps back to full functionality. Previously, when running any snap I would receive the following in the terminal: --- cannot change profile for the next exec call: No such file or directory snap-update-ns failed with code 1: File exists --- Updated to add for Jamie: $ snap version snap2.44.2+20.04 snapd 2.44.2+20.04 series 16 ubuntu 20.04 kernel 5.4.0-21-generic To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1871148/+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 1870837] Re: hcitool lescan says 'Set scan parameters failed: Input/output error'
I also think it's not a kernel issue since bluetoothctl is working and able to find Bluetooth low energy devices. Bluez Ubuntu 18.04 version with latest focal kernel also results in: hcitool lescan Set scan parameters failed: Input/output error -- 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/1870837 Title: hcitool lescan says 'Set scan parameters failed: Input/output error' Status in bluez package in Ubuntu: New Bug description: Hi, after some testing with Ubuntu 20.04 beta I couldn't get hcitool lescan working. I get the following error: hcitool lescan Set scan parameters failed: Input/output error Bluetooth hardware: hci0: Type: Primary Bus: USB BD Address: 04:EA:56:21:xx:xx ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1605 acl:0 sco:0 events:123 errors:0 TX bytes:5801 acl:0 sco:0 commands:123 errors:0 Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'xx' Class: 0x200104 Service Classes: Audio Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x100 LMP Version: 5.1 (0xa) Subversion: 0x100 Manufacturer: Intel Corp. (2) It is not hardware related, since I get the same error with a USB bluetooth dongle: hcitool -i hci1 lescan Set scan parameters failed: Input/output error hcitool scan is working fine on both devices; bluetoothctl is also working and able to find ble devices. I would normally prefer bluetoothctl, but I got a software which is based on hcitool. dmesg shows this errors: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! Bluez version: bluez 5.53-0ubuntu2 amd64 System: Distributor ID: Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 Codename: focal --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root ro ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/23/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0075.2019.1023.1448 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0075.2019.1023.1448:bd10/23/2019:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 04:EA:56:21:1E:D3 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17030 acl:0 sco:0 events:2764 errors:0 TX bytes:677849 acl:0 sco:0 commands:2757 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1870837/+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 1835660] Re: initramfs unpacking failed
We currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Invalid ** Description changed: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. + + --- + + However, we currently believe that the decoding error reported in dmesg + is actually harmless and has no impact on usability on the system. + + Switching from lz4 to gzip compression, simply papers over the warning, + without any benefits, and slows down boot. + + Kernel should be fixed to correctly parse lz4 compressed initrds, or at + least lower the warning, to not be user visible as an error. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+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 1871176] [NEW] package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1
Public bug reported: hayden@t470s:~$ sudo apt-get install gnome-boxes [sudo] password for hayden: Reading package lists... Done Building dependency tree Reading state information... Done gnome-boxes is already the newest version (3.36.2-1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up lvm2 (2.03.07-1ubuntu1) ... update-initramfs: deferring update (trigger activated) Failed to restart lvm2-lvmpolld.service: Unit lvm2-lvmpolld.socket is masked. invoke-rc.d: initscript lvm2-lvmpolld, action "restart" failed. ● lvm2-lvmpolld.service - LVM2 poll daemon Loaded: loaded (/lib/systemd/system/lvm2-lvmpolld.service; static; vendor preset: enabled) Active: active (exited) since Mon 2020-04-06 09:33:50 EDT; 4h 10min ago Docs: man:lvmpolld(8) Tasks: 0 (limit: 23811) Memory: 0B CGroup: /system.slice/lvm2-lvmpolld.service Apr 06 09:33:50 t470s systemd[1]: Starting LSB: LVM2 poll daemon... Apr 06 09:33:50 t470s systemd[1]: Started LSB: LVM2 poll daemon. dpkg: error processing package lvm2 (--configure): installed lvm2 package post-installation script subprocess returned error exit status 1 Processing triggers for initramfs-tools (0.136ubuntu2) ... update-initramfs: Generating /boot/initrd.img-5.4.0-21-generic Errors were encountered while processing: lvm2 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 Date: Mon Apr 6 13:38:10 2020 ErrorMessage: installed lvm2 package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.1 SourcePackage: lvm2 Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/1871176 Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 Status in lvm2 package in Ubuntu: New Bug description: hayden@t470s:~$ sudo apt-get install gnome-boxes [sudo] password for hayden: Reading package lists... Done Building dependency tree Reading state information... Done gnome-boxes is already the newest version (3.36.2-1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up lvm2 (2.03.07-1ubuntu1) ... update-initramfs: deferring update (trigger activated) Failed to restart lvm2-lvmpolld.service: Unit lvm2-lvmpolld.socket is masked. invoke-rc.d: initscript lvm2-lvmpolld, action "restart" failed. ● lvm2-lvmpolld.service - LVM2 poll daemon Loaded: loaded (/lib/systemd/system/lvm2-lvmpolld.service; static; vendor preset: enabled) Active: active (exited) since Mon 2020-04-06 09:33:50 EDT; 4h 10min ago Docs: man:lvmpolld(8) Tasks: 0 (limit: 23811) Memory: 0B CGroup: /system.slice/lvm2-lvmpolld.service Apr 06 09:33:50 t470s systemd[1]: Starting LSB: LVM2 poll daemon... Apr 06 09:33:50 t470s systemd[1]: Started LSB: LVM2 poll daemon. dpkg: error processing package lvm2 (--configure): installed lvm2 package post-installation script subprocess returned error exit status 1 Processing triggers for initramfs-tools (0.136ubuntu2) ... update-initramfs: Generating /boot/initrd.img-5.4.0-21-generic Errors were encountered while processing: lvm2 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 Date: Mon Apr 6 13:38:10 2020 ErrorMessage: installed lvm2 package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.1 SourcePackage: lvm2 Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2
[Touch-packages] [Bug 1861082] Re: ubuntu-bug doesn't know how to file bugs against snaps
Based on the latest comments, "incomplete" is wrong, we have enough information here for apport to start using the contact field. ** Changed in: apport (Ubuntu) Status: Incomplete => Triaged -- 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: Triaged 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 1870837] Re: hcitool lescan says 'Set scan parameters failed: Input/output error'
On uname -a Linux xxx 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux even with up to date focal bluez version the bluetooth device isn't recognized: dmesg | grep Bluetooth = empty output The backup usb bluetooth dongle also doesn't work with this kernel: [ 417.427445] usb 1-2: new full-speed USB device number 5 using xhci_hcd [ 417.843295] usb 1-2: config 1 interface 1 altsetting 0 endpoint 0x3 has wMaxPacketSize 0, skipping [ 417.843303] usb 1-2: config 1 interface 1 altsetting 0 endpoint 0x83 has wMaxPacketSize 0, skipping [ 417.843323] usb 1-2: New USB device found, idVendor=0a12, idProduct=0001 [ 417.843329] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0 root@xxx:# hcitool scan Device is not available: Address family not supported by protocol root@cdsv2:# lsusb ... Bus 001 Device 005: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) ... -- 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/1870837 Title: hcitool lescan says 'Set scan parameters failed: Input/output error' Status in bluez package in Ubuntu: New Bug description: Hi, after some testing with Ubuntu 20.04 beta I couldn't get hcitool lescan working. I get the following error: hcitool lescan Set scan parameters failed: Input/output error Bluetooth hardware: hci0: Type: Primary Bus: USB BD Address: 04:EA:56:21:xx:xx ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1605 acl:0 sco:0 events:123 errors:0 TX bytes:5801 acl:0 sco:0 commands:123 errors:0 Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'xx' Class: 0x200104 Service Classes: Audio Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x100 LMP Version: 5.1 (0xa) Subversion: 0x100 Manufacturer: Intel Corp. (2) It is not hardware related, since I get the same error with a USB bluetooth dongle: hcitool -i hci1 lescan Set scan parameters failed: Input/output error hcitool scan is working fine on both devices; bluetoothctl is also working and able to find ble devices. I would normally prefer bluetoothctl, but I got a software which is based on hcitool. dmesg shows this errors: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! Bluez version: bluez 5.53-0ubuntu2 amd64 System: Distributor ID: Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 Codename: focal --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root ro ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/23/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0075.2019.1023.1448 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0075.2019.1023.1448:bd10/23/2019:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 04:EA:56:21:1E:D3 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17030 acl:0 sco:0 events:2764 errors:0 TX bytes:677849 acl:0 sco:0 commands:2757 errors:0 To manage notifications about this bug go to:
[Touch-packages] [Bug 1870837] Re: hcitool lescan says 'Set scan parameters failed: Input/output error'
https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=b1eb2c4cd057624312e0412f6c4be000f7fc3617 These legacy tools has been marked deprecated since 2017. You should try migrating to bluetoothctl instead. ** No longer affects: linux (Ubuntu) -- 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/1870837 Title: hcitool lescan says 'Set scan parameters failed: Input/output error' Status in bluez package in Ubuntu: New Bug description: Hi, after some testing with Ubuntu 20.04 beta I couldn't get hcitool lescan working. I get the following error: hcitool lescan Set scan parameters failed: Input/output error Bluetooth hardware: hci0: Type: Primary Bus: USB BD Address: 04:EA:56:21:xx:xx ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1605 acl:0 sco:0 events:123 errors:0 TX bytes:5801 acl:0 sco:0 commands:123 errors:0 Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'xx' Class: 0x200104 Service Classes: Audio Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x100 LMP Version: 5.1 (0xa) Subversion: 0x100 Manufacturer: Intel Corp. (2) It is not hardware related, since I get the same error with a USB bluetooth dongle: hcitool -i hci1 lescan Set scan parameters failed: Input/output error hcitool scan is working fine on both devices; bluetoothctl is also working and able to find ble devices. I would normally prefer bluetoothctl, but I got a software which is based on hcitool. dmesg shows this errors: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! Bluez version: bluez 5.53-0ubuntu2 amd64 System: Distributor ID: Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 Codename: focal --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root ro ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/23/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0075.2019.1023.1448 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0075.2019.1023.1448:bd10/23/2019:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 04:EA:56:21:1E:D3 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17030 acl:0 sco:0 events:2764 errors:0 TX bytes:677849 acl:0 sco:0 commands:2757 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1870837/+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 1870837] Re: hcitool lescan says 'Set scan parameters failed: Input/output error'
Not a kernel issue. -- 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/1870837 Title: hcitool lescan says 'Set scan parameters failed: Input/output error' Status in bluez package in Ubuntu: New Bug description: Hi, after some testing with Ubuntu 20.04 beta I couldn't get hcitool lescan working. I get the following error: hcitool lescan Set scan parameters failed: Input/output error Bluetooth hardware: hci0: Type: Primary Bus: USB BD Address: 04:EA:56:21:xx:xx ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1605 acl:0 sco:0 events:123 errors:0 TX bytes:5801 acl:0 sco:0 commands:123 errors:0 Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'xx' Class: 0x200104 Service Classes: Audio Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x100 LMP Version: 5.1 (0xa) Subversion: 0x100 Manufacturer: Intel Corp. (2) It is not hardware related, since I get the same error with a USB bluetooth dongle: hcitool -i hci1 lescan Set scan parameters failed: Input/output error hcitool scan is working fine on both devices; bluetoothctl is also working and able to find ble devices. I would normally prefer bluetoothctl, but I got a software which is based on hcitool. dmesg shows this errors: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! Bluez version: bluez 5.53-0ubuntu2 amd64 System: Distributor ID: Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 Codename: focal --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root ro ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/23/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0075.2019.1023.1448 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0075.2019.1023.1448:bd10/23/2019:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 04:EA:56:21:1E:D3 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17030 acl:0 sco:0 events:2764 errors:0 TX bytes:677849 acl:0 sco:0 commands:2757 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1870837/+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 1870837] Re: hcitool lescan says 'Set scan parameters failed: Input/output error'
With current Ubuntu 18.04 installed on focal and the current bluez v5.48 (current Ubuntu 18.04 version): I get the following error: root@xxx:~# uname -a Linux xxx 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux root@xxx:~# hcitool lescan Could not open device: No such device root@xxx:~# dpkg -l | grep bluez ii bluez 5.48-0ubuntu3.4 amd64Bluetooth tools and daemons -- 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/1870837 Title: hcitool lescan says 'Set scan parameters failed: Input/output error' Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Hi, after some testing with Ubuntu 20.04 beta I couldn't get hcitool lescan working. I get the following error: hcitool lescan Set scan parameters failed: Input/output error Bluetooth hardware: hci0: Type: Primary Bus: USB BD Address: 04:EA:56:21:xx:xx ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1605 acl:0 sco:0 events:123 errors:0 TX bytes:5801 acl:0 sco:0 commands:123 errors:0 Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'xx' Class: 0x200104 Service Classes: Audio Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x100 LMP Version: 5.1 (0xa) Subversion: 0x100 Manufacturer: Intel Corp. (2) It is not hardware related, since I get the same error with a USB bluetooth dongle: hcitool -i hci1 lescan Set scan parameters failed: Input/output error hcitool scan is working fine on both devices; bluetoothctl is also working and able to find ble devices. I would normally prefer bluetoothctl, but I got a software which is based on hcitool. dmesg shows this errors: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! Bluez version: bluez 5.53-0ubuntu2 amd64 System: Distributor ID: Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 Codename: focal --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root ro ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/23/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0075.2019.1023.1448 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0075.2019.1023.1448:bd10/23/2019:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 04:EA:56:21:1E:D3 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17030 acl:0 sco:0 events:2764 errors:0 TX bytes:677849 acl:0 sco:0 commands:2757 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1870837/+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 1866611] Re: OpenVPN w. SHA1 signed CA broken after upgrade to 1.1.1d-2ubuntu6
As a quick addition for the QVPN app on a Qnap NAS in our network I just installed a Raspberry 3 with PiVpn (pivpn.io) configured for OpenVPN, as I'm in doubt Qnap will release an updated QVpn just in Time ... Works like a charm and installation is super easy. With at least one connection it seems even faster than QVpn on a more powerful NAS. No test with multiple connections until now ... but there are more beefy Rasberry 4 if it shows to slow... With this additional VPN the transition to Ubuntu 20.04 can now be done in my company. When its finished i'll switch off QVpn (and remove the corresponding portforwarding). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1866611 Title: OpenVPN w. SHA1 signed CA broken after upgrade to 1.1.1d-2ubuntu6 Status in openssl package in Ubuntu: Confirmed Bug description: After upgrading openssl on my Focal-install this morning (upgrade openssl:amd64 1.1.1d-2ubuntu3 1.1.1d-2ubuntu6 per /var/log/dpkg.log), my OpenVPN tunnel refuses to connect to our corporate VPN (from /var/log/syslog): corp-laptop nm-openvpn[4688]: VERIFY ERROR: depth=0, error=CA signature digest algorithm too weak: C=DK, ST=None, L=Copenhagen, O=XX, OU=XX, CN=XX, emailAddress=XX corp-laptop nm-openvpn[4688]: OpenSSL: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed I'm told we're running a SHA1-signed CA, which we're guessing has been deprecated somewhere between -2ubuntu3 and -2ubuntu6. The changelog for -2ubuntu4 mentions importing some upstream changes, but isn't more specific than that: https://changelogs.ubuntu.com/changelogs/pool/main/o/openssl/openssl_1.1 .1d-2ubuntu4/changelog As a work-around, the internet suggests two work-arounds (neither of which has worked for me): 1) Adding the following to /etc/defaults/openssl: OPTARGS="--tls-cipher DEFAULT:@SECLEVEL=0" 2) Adding the following to /etc/ssl/openssl.conf: CipherString= :@SECLEVEL=1 I also tried rolling back the package, but the old version doesn't seem to be available: $ sudo apt install openssl=1.1.1d-2ubuntu3 ... E: Version '1.1.1d-2ubuntu3' for 'openssl' was not found I am no SSL-expert and would appreciate any pointers to get around this. (Our network-dept. does not have the bandwidth to roll over our CA on short notice, so I will need some other way to move ahead). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1866611/+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 1835660] Re: initramfs unpacking failed
I had also the same message in dmesg. (I don't remember when it started) Here : Ubuntu 19.10 booting a manually installed kernel (5.5.2-050502-generic) I followed previous advices : Adding COMPRESS=gzip to /etc/initramfs-tools/initramfs.conf (instead of lz4) then : $ sudo update-grub;sudo update-initramfs -c -k all;sudo update-grub Reboot. No more error message, and systemd-analyse says : Startup finished in 15.790s (firmware) + 3.112s (loader) + 9.986s (kernel) + 9.605s (userspace) = 38.495s graphical.target reached after 9.595s in userspace I restored COMPRESS=lz4 then $ sudo update-grub;sudo update-initramfs -c -k all;sudo update-grub Reboot : still no error message, and systemd-analyse says : Startup finished in 15.793s (firmware) + 3.188s (loader) + 8.962s (kernel) + 11.645s (userspace) = 39.589s graphical.target reached after 11.635s in userspace (Yes it's slower but it might be me : I have to choose in grub menu selection and type full disk encryption password) I rebooted a 3rd time : no change, still no more Decoding errors. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+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 1870837] Re: hcitool lescan says 'Set scan parameters failed: Input/output error'
I tested the following mainline kernels: Linux xxx 5.3.18-050318-generic #201912181133 SMP Wed Dec 18 16:36:09 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@xxx:~# hcitool lescan Set scan parameters failed: Input/output error root@xxx:~# uname -a Linux xxx 4.15.18-041518-generic #201804190330 SMP Thu Apr 19 07:34:21 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@xxx:~# hcitool lescan Set scan parameters failed: Input/output error 5.3. since it is Ubuntu 19.10's kernel; 4.15 since it is Ubuntu 18.04's kernel. With both of them it didn't work. Thats strange since hcitool lescan did work on the same machine with Ubuntu 18.04 and the 4.15 kernel. On another machine with Ubuntu 18.04 hcitool lescan works: uname -a Linux xxx 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux root@xxx:~# hcitool lescan LE Scan ... 6E:82:1E:5F:xx:xx (unknown) ... So I think it is not kernel related ... -- 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/1870837 Title: hcitool lescan says 'Set scan parameters failed: Input/output error' Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Hi, after some testing with Ubuntu 20.04 beta I couldn't get hcitool lescan working. I get the following error: hcitool lescan Set scan parameters failed: Input/output error Bluetooth hardware: hci0: Type: Primary Bus: USB BD Address: 04:EA:56:21:xx:xx ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1605 acl:0 sco:0 events:123 errors:0 TX bytes:5801 acl:0 sco:0 commands:123 errors:0 Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'xx' Class: 0x200104 Service Classes: Audio Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x100 LMP Version: 5.1 (0xa) Subversion: 0x100 Manufacturer: Intel Corp. (2) It is not hardware related, since I get the same error with a USB bluetooth dongle: hcitool -i hci1 lescan Set scan parameters failed: Input/output error hcitool scan is working fine on both devices; bluetoothctl is also working and able to find ble devices. I would normally prefer bluetoothctl, but I got a software which is based on hcitool. dmesg shows this errors: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! Bluez version: bluez 5.53-0ubuntu2 amd64 System: Distributor ID: Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 Codename: focal --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root ro ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/23/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0075.2019.1023.1448 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0075.2019.1023.1448:bd10/23/2019:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 04:EA:56:21:1E:D3 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17030 acl:0 sco:0 events:2764 errors:0 TX bytes:677849 acl:0 sco:0 commands:2757 errors:0 To manage notifications about this bug
[Touch-packages] [Bug 1871154] [NEW] Error message displayed during boot (mountroot hook, premount)
Public bug reported: Hi, my Ubuntu system uses LVM2 for its root file system. It boots correctly, but an ugly error message is displayed during boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 Uname: Linux 5.6.2-050602-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 6 17:59:03 2020 SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1871154 Title: Error message displayed during boot (mountroot hook, premount) Status in lvm2 package in Ubuntu: New Bug description: Hi, my Ubuntu system uses LVM2 for its root file system. It boots correctly, but an ugly error message is displayed during boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 Uname: Linux 5.6.2-050602-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 6 17:59:03 2020 SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1871154/+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 1871154] Re: Error message displayed during boot (mountroot hook, premount)
Here is a screenshot of the error message. ** Attachment added: "IMG_20200405_222107.jpg" https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1871154/+attachment/5347869/+files/IMG_20200405_222107.jpg -- 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/1871154 Title: Error message displayed during boot (mountroot hook, premount) Status in lvm2 package in Ubuntu: New Bug description: Hi, my Ubuntu system uses LVM2 for its root file system. It boots correctly, but an ugly error message is displayed during boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 Uname: Linux 5.6.2-050602-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 6 17:59:03 2020 SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1871154/+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 1871154] Re: Error message displayed during boot (mountroot hook, premount)
Here is my (very simple) LVM setup: # pvdisplay --- Physical volume --- PV Name /dev/nvme0n1p2 VG Name MonVolume2 PV Size <850.00 GiB / not usable 3.00 MiB Allocatable yes PE Size 4.00 MiB Total PE 217599 Free PE 89599 Allocated PE 128000 PV UUID oZhDcb-KQRJ-eFm9-sKDf-ZztS-1oiI-X3dV0V # vgdisplay --- Volume group --- VG Name MonVolume2 System ID Formatlvm2 Metadata Areas1 Metadata Sequence No 48 VG Access read/write VG Status resizable MAX LV0 Cur LV1 Open LV 1 Max PV0 Cur PV1 Act PV1 VG Size <850.00 GiB PE Size 4.00 MiB Total PE 217599 Alloc PE / Size 128000 / 500.00 GiB Free PE / Size 89599 / <350.00 GiB VG UUID R8BWf2-UExN-WPsG-0bxU-7Qzf-PtlT-fgf4hS # lvdisplay --- Logical volume --- LV Path/dev/MonVolume2/UbuntuRacine LV NameUbuntuRacine VG NameMonVolume2 LV UUIDnhjz7g-J0GH-uMqQ-3QQU-eoJH-tuc3-YTMtcd LV Write Accessread/write LV Creation host, time ubuntu, 2019-05-03 18:45:22 +0200 LV Status available # open 1 LV Size500.00 GiB Current LE 128000 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:0 -- 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/1871154 Title: Error message displayed during boot (mountroot hook, premount) Status in lvm2 package in Ubuntu: New Bug description: Hi, my Ubuntu system uses LVM2 for its root file system. It boots correctly, but an ugly error message is displayed during boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 Uname: Linux 5.6.2-050602-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 6 17:59:03 2020 SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1871154/+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 1871154] Re: Error message displayed during boot (mountroot hook, premount)
My system had the same LVM setup in Ubuntu 19.10 and no error message was displayed during boot. -- 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/1871154 Title: Error message displayed during boot (mountroot hook, premount) Status in lvm2 package in Ubuntu: New Bug description: Hi, my Ubuntu system uses LVM2 for its root file system. It boots correctly, but an ugly error message is displayed during boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 Uname: Linux 5.6.2-050602-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 6 17:59:03 2020 SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1871154/+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 1870837] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1870837/+attachment/5347853/+files/ProcCpuinfo.txt -- 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/1870837 Title: hcitool lescan says 'Set scan parameters failed: Input/output error' Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Hi, after some testing with Ubuntu 20.04 beta I couldn't get hcitool lescan working. I get the following error: hcitool lescan Set scan parameters failed: Input/output error Bluetooth hardware: hci0: Type: Primary Bus: USB BD Address: 04:EA:56:21:xx:xx ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1605 acl:0 sco:0 events:123 errors:0 TX bytes:5801 acl:0 sco:0 commands:123 errors:0 Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'xx' Class: 0x200104 Service Classes: Audio Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x100 LMP Version: 5.1 (0xa) Subversion: 0x100 Manufacturer: Intel Corp. (2) It is not hardware related, since I get the same error with a USB bluetooth dongle: hcitool -i hci1 lescan Set scan parameters failed: Input/output error hcitool scan is working fine on both devices; bluetoothctl is also working and able to find ble devices. I would normally prefer bluetoothctl, but I got a software which is based on hcitool. dmesg shows this errors: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! Bluez version: bluez 5.53-0ubuntu2 amd64 System: Distributor ID: Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 Codename: focal --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root ro ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/23/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0075.2019.1023.1448 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0075.2019.1023.1448:bd10/23/2019:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 04:EA:56:21:1E:D3 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17030 acl:0 sco:0 events:2764 errors:0 TX bytes:677849 acl:0 sco:0 commands:2757 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1870837/+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 1870837] Re: hcitool lescan says 'Set scan parameters failed: Input/output error'
** Attachment added: "syslog.txt" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1870837/+attachment/5347863/+files/syslog.txt -- 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/1870837 Title: hcitool lescan says 'Set scan parameters failed: Input/output error' Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Hi, after some testing with Ubuntu 20.04 beta I couldn't get hcitool lescan working. I get the following error: hcitool lescan Set scan parameters failed: Input/output error Bluetooth hardware: hci0: Type: Primary Bus: USB BD Address: 04:EA:56:21:xx:xx ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1605 acl:0 sco:0 events:123 errors:0 TX bytes:5801 acl:0 sco:0 commands:123 errors:0 Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'xx' Class: 0x200104 Service Classes: Audio Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x100 LMP Version: 5.1 (0xa) Subversion: 0x100 Manufacturer: Intel Corp. (2) It is not hardware related, since I get the same error with a USB bluetooth dongle: hcitool -i hci1 lescan Set scan parameters failed: Input/output error hcitool scan is working fine on both devices; bluetoothctl is also working and able to find ble devices. I would normally prefer bluetoothctl, but I got a software which is based on hcitool. dmesg shows this errors: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! Bluez version: bluez 5.53-0ubuntu2 amd64 System: Distributor ID: Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 Codename: focal --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root ro ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/23/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0075.2019.1023.1448 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0075.2019.1023.1448:bd10/23/2019:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 04:EA:56:21:1E:D3 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17030 acl:0 sco:0 events:2764 errors:0 TX bytes:677849 acl:0 sco:0 commands:2757 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1870837/+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 1870837] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1870837/+attachment/5347854/+files/ProcCpuinfoMinimal.txt -- 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/1870837 Title: hcitool lescan says 'Set scan parameters failed: Input/output error' Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Hi, after some testing with Ubuntu 20.04 beta I couldn't get hcitool lescan working. I get the following error: hcitool lescan Set scan parameters failed: Input/output error Bluetooth hardware: hci0: Type: Primary Bus: USB BD Address: 04:EA:56:21:xx:xx ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1605 acl:0 sco:0 events:123 errors:0 TX bytes:5801 acl:0 sco:0 commands:123 errors:0 Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'xx' Class: 0x200104 Service Classes: Audio Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x100 LMP Version: 5.1 (0xa) Subversion: 0x100 Manufacturer: Intel Corp. (2) It is not hardware related, since I get the same error with a USB bluetooth dongle: hcitool -i hci1 lescan Set scan parameters failed: Input/output error hcitool scan is working fine on both devices; bluetoothctl is also working and able to find ble devices. I would normally prefer bluetoothctl, but I got a software which is based on hcitool. dmesg shows this errors: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! Bluez version: bluez 5.53-0ubuntu2 amd64 System: Distributor ID: Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 Codename: focal --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root ro ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/23/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0075.2019.1023.1448 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0075.2019.1023.1448:bd10/23/2019:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 04:EA:56:21:1E:D3 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17030 acl:0 sco:0 events:2764 errors:0 TX bytes:677849 acl:0 sco:0 commands:2757 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1870837/+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 1870837] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1870837/+attachment/5347852/+files/Lsusb-v.txt -- 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/1870837 Title: hcitool lescan says 'Set scan parameters failed: Input/output error' Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Hi, after some testing with Ubuntu 20.04 beta I couldn't get hcitool lescan working. I get the following error: hcitool lescan Set scan parameters failed: Input/output error Bluetooth hardware: hci0: Type: Primary Bus: USB BD Address: 04:EA:56:21:xx:xx ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1605 acl:0 sco:0 events:123 errors:0 TX bytes:5801 acl:0 sco:0 commands:123 errors:0 Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'xx' Class: 0x200104 Service Classes: Audio Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x100 LMP Version: 5.1 (0xa) Subversion: 0x100 Manufacturer: Intel Corp. (2) It is not hardware related, since I get the same error with a USB bluetooth dongle: hcitool -i hci1 lescan Set scan parameters failed: Input/output error hcitool scan is working fine on both devices; bluetoothctl is also working and able to find ble devices. I would normally prefer bluetoothctl, but I got a software which is based on hcitool. dmesg shows this errors: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! Bluez version: bluez 5.53-0ubuntu2 amd64 System: Distributor ID: Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 Codename: focal --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root ro ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/23/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0075.2019.1023.1448 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0075.2019.1023.1448:bd10/23/2019:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 04:EA:56:21:1E:D3 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17030 acl:0 sco:0 events:2764 errors:0 TX bytes:677849 acl:0 sco:0 commands:2757 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1870837/+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 1870837] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1870837/+attachment/5347858/+files/UdevDb.txt -- 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/1870837 Title: hcitool lescan says 'Set scan parameters failed: Input/output error' Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Hi, after some testing with Ubuntu 20.04 beta I couldn't get hcitool lescan working. I get the following error: hcitool lescan Set scan parameters failed: Input/output error Bluetooth hardware: hci0: Type: Primary Bus: USB BD Address: 04:EA:56:21:xx:xx ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1605 acl:0 sco:0 events:123 errors:0 TX bytes:5801 acl:0 sco:0 commands:123 errors:0 Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'xx' Class: 0x200104 Service Classes: Audio Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x100 LMP Version: 5.1 (0xa) Subversion: 0x100 Manufacturer: Intel Corp. (2) It is not hardware related, since I get the same error with a USB bluetooth dongle: hcitool -i hci1 lescan Set scan parameters failed: Input/output error hcitool scan is working fine on both devices; bluetoothctl is also working and able to find ble devices. I would normally prefer bluetoothctl, but I got a software which is based on hcitool. dmesg shows this errors: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! Bluez version: bluez 5.53-0ubuntu2 amd64 System: Distributor ID: Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 Codename: focal --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root ro ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/23/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0075.2019.1023.1448 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0075.2019.1023.1448:bd10/23/2019:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 04:EA:56:21:1E:D3 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17030 acl:0 sco:0 events:2764 errors:0 TX bytes:677849 acl:0 sco:0 commands:2757 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1870837/+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 1870837] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1870837/+attachment/5347855/+files/ProcEnviron.txt -- 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/1870837 Title: hcitool lescan says 'Set scan parameters failed: Input/output error' Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Hi, after some testing with Ubuntu 20.04 beta I couldn't get hcitool lescan working. I get the following error: hcitool lescan Set scan parameters failed: Input/output error Bluetooth hardware: hci0: Type: Primary Bus: USB BD Address: 04:EA:56:21:xx:xx ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1605 acl:0 sco:0 events:123 errors:0 TX bytes:5801 acl:0 sco:0 commands:123 errors:0 Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'xx' Class: 0x200104 Service Classes: Audio Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x100 LMP Version: 5.1 (0xa) Subversion: 0x100 Manufacturer: Intel Corp. (2) It is not hardware related, since I get the same error with a USB bluetooth dongle: hcitool -i hci1 lescan Set scan parameters failed: Input/output error hcitool scan is working fine on both devices; bluetoothctl is also working and able to find ble devices. I would normally prefer bluetoothctl, but I got a software which is based on hcitool. dmesg shows this errors: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! Bluez version: bluez 5.53-0ubuntu2 amd64 System: Distributor ID: Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 Codename: focal --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root ro ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/23/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0075.2019.1023.1448 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0075.2019.1023.1448:bd10/23/2019:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 04:EA:56:21:1E:D3 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17030 acl:0 sco:0 events:2764 errors:0 TX bytes:677849 acl:0 sco:0 commands:2757 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1870837/+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 1870837] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1870837/+attachment/5347857/+files/ProcModules.txt -- 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/1870837 Title: hcitool lescan says 'Set scan parameters failed: Input/output error' Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Hi, after some testing with Ubuntu 20.04 beta I couldn't get hcitool lescan working. I get the following error: hcitool lescan Set scan parameters failed: Input/output error Bluetooth hardware: hci0: Type: Primary Bus: USB BD Address: 04:EA:56:21:xx:xx ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1605 acl:0 sco:0 events:123 errors:0 TX bytes:5801 acl:0 sco:0 commands:123 errors:0 Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'xx' Class: 0x200104 Service Classes: Audio Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x100 LMP Version: 5.1 (0xa) Subversion: 0x100 Manufacturer: Intel Corp. (2) It is not hardware related, since I get the same error with a USB bluetooth dongle: hcitool -i hci1 lescan Set scan parameters failed: Input/output error hcitool scan is working fine on both devices; bluetoothctl is also working and able to find ble devices. I would normally prefer bluetoothctl, but I got a software which is based on hcitool. dmesg shows this errors: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! Bluez version: bluez 5.53-0ubuntu2 amd64 System: Distributor ID: Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 Codename: focal --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root ro ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/23/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0075.2019.1023.1448 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0075.2019.1023.1448:bd10/23/2019:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 04:EA:56:21:1E:D3 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17030 acl:0 sco:0 events:2764 errors:0 TX bytes:677849 acl:0 sco:0 commands:2757 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1870837/+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 1870837] rfkill.txt
apport information ** Attachment added: "rfkill.txt" https://bugs.launchpad.net/bugs/1870837/+attachment/5347860/+files/rfkill.txt -- 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/1870837 Title: hcitool lescan says 'Set scan parameters failed: Input/output error' Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Hi, after some testing with Ubuntu 20.04 beta I couldn't get hcitool lescan working. I get the following error: hcitool lescan Set scan parameters failed: Input/output error Bluetooth hardware: hci0: Type: Primary Bus: USB BD Address: 04:EA:56:21:xx:xx ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1605 acl:0 sco:0 events:123 errors:0 TX bytes:5801 acl:0 sco:0 commands:123 errors:0 Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'xx' Class: 0x200104 Service Classes: Audio Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x100 LMP Version: 5.1 (0xa) Subversion: 0x100 Manufacturer: Intel Corp. (2) It is not hardware related, since I get the same error with a USB bluetooth dongle: hcitool -i hci1 lescan Set scan parameters failed: Input/output error hcitool scan is working fine on both devices; bluetoothctl is also working and able to find ble devices. I would normally prefer bluetoothctl, but I got a software which is based on hcitool. dmesg shows this errors: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! Bluez version: bluez 5.53-0ubuntu2 amd64 System: Distributor ID: Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 Codename: focal --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root ro ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/23/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0075.2019.1023.1448 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0075.2019.1023.1448:bd10/23/2019:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 04:EA:56:21:1E:D3 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17030 acl:0 sco:0 events:2764 errors:0 TX bytes:677849 acl:0 sco:0 commands:2757 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1870837/+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 1870837] syslog.txt
apport information ** Attachment added: "syslog.txt" https://bugs.launchpad.net/bugs/1870837/+attachment/5347861/+files/syslog.txt ** Attachment removed: "syslog.txt" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1870837/+attachment/5347861/+files/syslog.txt -- 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/1870837 Title: hcitool lescan says 'Set scan parameters failed: Input/output error' Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Hi, after some testing with Ubuntu 20.04 beta I couldn't get hcitool lescan working. I get the following error: hcitool lescan Set scan parameters failed: Input/output error Bluetooth hardware: hci0: Type: Primary Bus: USB BD Address: 04:EA:56:21:xx:xx ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1605 acl:0 sco:0 events:123 errors:0 TX bytes:5801 acl:0 sco:0 commands:123 errors:0 Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'xx' Class: 0x200104 Service Classes: Audio Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x100 LMP Version: 5.1 (0xa) Subversion: 0x100 Manufacturer: Intel Corp. (2) It is not hardware related, since I get the same error with a USB bluetooth dongle: hcitool -i hci1 lescan Set scan parameters failed: Input/output error hcitool scan is working fine on both devices; bluetoothctl is also working and able to find ble devices. I would normally prefer bluetoothctl, but I got a software which is based on hcitool. dmesg shows this errors: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! Bluez version: bluez 5.53-0ubuntu2 amd64 System: Distributor ID: Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 Codename: focal --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root ro ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/23/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0075.2019.1023.1448 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0075.2019.1023.1448:bd10/23/2019:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 04:EA:56:21:1E:D3 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17030 acl:0 sco:0 events:2764 errors:0 TX bytes:677849 acl:0 sco:0 commands:2757 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1870837/+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 1870837] getfacl.txt
apport information ** Attachment added: "getfacl.txt" https://bugs.launchpad.net/bugs/1870837/+attachment/5347859/+files/getfacl.txt -- 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/1870837 Title: hcitool lescan says 'Set scan parameters failed: Input/output error' Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Hi, after some testing with Ubuntu 20.04 beta I couldn't get hcitool lescan working. I get the following error: hcitool lescan Set scan parameters failed: Input/output error Bluetooth hardware: hci0: Type: Primary Bus: USB BD Address: 04:EA:56:21:xx:xx ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1605 acl:0 sco:0 events:123 errors:0 TX bytes:5801 acl:0 sco:0 commands:123 errors:0 Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'xx' Class: 0x200104 Service Classes: Audio Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x100 LMP Version: 5.1 (0xa) Subversion: 0x100 Manufacturer: Intel Corp. (2) It is not hardware related, since I get the same error with a USB bluetooth dongle: hcitool -i hci1 lescan Set scan parameters failed: Input/output error hcitool scan is working fine on both devices; bluetoothctl is also working and able to find ble devices. I would normally prefer bluetoothctl, but I got a software which is based on hcitool. dmesg shows this errors: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! Bluez version: bluez 5.53-0ubuntu2 amd64 System: Distributor ID: Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 Codename: focal --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root ro ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/23/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0075.2019.1023.1448 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0075.2019.1023.1448:bd10/23/2019:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 04:EA:56:21:1E:D3 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17030 acl:0 sco:0 events:2764 errors:0 TX bytes:677849 acl:0 sco:0 commands:2757 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1870837/+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 1870837] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1870837/+attachment/5347856/+files/ProcInterrupts.txt -- 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/1870837 Title: hcitool lescan says 'Set scan parameters failed: Input/output error' Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Hi, after some testing with Ubuntu 20.04 beta I couldn't get hcitool lescan working. I get the following error: hcitool lescan Set scan parameters failed: Input/output error Bluetooth hardware: hci0: Type: Primary Bus: USB BD Address: 04:EA:56:21:xx:xx ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1605 acl:0 sco:0 events:123 errors:0 TX bytes:5801 acl:0 sco:0 commands:123 errors:0 Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'xx' Class: 0x200104 Service Classes: Audio Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x100 LMP Version: 5.1 (0xa) Subversion: 0x100 Manufacturer: Intel Corp. (2) It is not hardware related, since I get the same error with a USB bluetooth dongle: hcitool -i hci1 lescan Set scan parameters failed: Input/output error hcitool scan is working fine on both devices; bluetoothctl is also working and able to find ble devices. I would normally prefer bluetoothctl, but I got a software which is based on hcitool. dmesg shows this errors: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! Bluez version: bluez 5.53-0ubuntu2 amd64 System: Distributor ID: Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 Codename: focal --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root ro ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/23/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0075.2019.1023.1448 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0075.2019.1023.1448:bd10/23/2019:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 04:EA:56:21:1E:D3 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17030 acl:0 sco:0 events:2764 errors:0 TX bytes:677849 acl:0 sco:0 commands:2757 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1870837/+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 1870837] Re: hcitool lescan says 'Set scan parameters failed: Input/output error'
** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1870837/+attachment/5347865/+files/CurrentDmesg.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1870837/+attachment/5347848/+files/CurrentDmesg.txt -- 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/1870837 Title: hcitool lescan says 'Set scan parameters failed: Input/output error' Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Hi, after some testing with Ubuntu 20.04 beta I couldn't get hcitool lescan working. I get the following error: hcitool lescan Set scan parameters failed: Input/output error Bluetooth hardware: hci0: Type: Primary Bus: USB BD Address: 04:EA:56:21:xx:xx ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1605 acl:0 sco:0 events:123 errors:0 TX bytes:5801 acl:0 sco:0 commands:123 errors:0 Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'xx' Class: 0x200104 Service Classes: Audio Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x100 LMP Version: 5.1 (0xa) Subversion: 0x100 Manufacturer: Intel Corp. (2) It is not hardware related, since I get the same error with a USB bluetooth dongle: hcitool -i hci1 lescan Set scan parameters failed: Input/output error hcitool scan is working fine on both devices; bluetoothctl is also working and able to find ble devices. I would normally prefer bluetoothctl, but I got a software which is based on hcitool. dmesg shows this errors: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! Bluez version: bluez 5.53-0ubuntu2 amd64 System: Distributor ID: Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 Codename: focal --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root ro ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/23/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0075.2019.1023.1448 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0075.2019.1023.1448:bd10/23/2019:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 04:EA:56:21:1E:D3 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17030 acl:0 sco:0 events:2764 errors:0 TX bytes:677849 acl:0 sco:0 commands:2757 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1870837/+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 1871137] Re: Recorded audio is super choppy with today's apt upgrade
** Attachment added: "Choppy sound with Gnome Sound Recorder" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871137/+attachment/5347862/+files/Choppy%20sound%20with%20Gnome%20Sound%20Recorder -- 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/1871137 Title: Recorded audio is super choppy with today's apt upgrade Status in pulseaudio package in Ubuntu: New Bug description: People reported choppy audio coming from me in my morning stand-up call. I thought it might be an issue with our chat system, so I tried recording a sound bite in Audacity both with and without my bluetooth headset. I got the same incredibly choppy sound in either case. I'll attach a clip to the bug if I can so you can see what I mean. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 Date: Mon Apr 6 11:07:37 2020 InstallationDate: Installed on 2020-01-09 (87 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-01-24 (73 days ago) dmi.bios.date: 04/18/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.7.0 dmi.board.name: Alienware 17 R5 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.7.0:bd04/18/2019:svnAlienware:pnAlienware17R5:pvr1.7.0:rvnAlienware:rnAlienware17R5:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware 17 R5 dmi.product.sku: 0877 dmi.product.version: 1.7.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871137/+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 1870837] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1870837/+attachment/5347849/+files/Dependencies.txt -- 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/1870837 Title: hcitool lescan says 'Set scan parameters failed: Input/output error' Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Hi, after some testing with Ubuntu 20.04 beta I couldn't get hcitool lescan working. I get the following error: hcitool lescan Set scan parameters failed: Input/output error Bluetooth hardware: hci0: Type: Primary Bus: USB BD Address: 04:EA:56:21:xx:xx ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1605 acl:0 sco:0 events:123 errors:0 TX bytes:5801 acl:0 sco:0 commands:123 errors:0 Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'xx' Class: 0x200104 Service Classes: Audio Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x100 LMP Version: 5.1 (0xa) Subversion: 0x100 Manufacturer: Intel Corp. (2) It is not hardware related, since I get the same error with a USB bluetooth dongle: hcitool -i hci1 lescan Set scan parameters failed: Input/output error hcitool scan is working fine on both devices; bluetoothctl is also working and able to find ble devices. I would normally prefer bluetoothctl, but I got a software which is based on hcitool. dmesg shows this errors: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! Bluez version: bluez 5.53-0ubuntu2 amd64 System: Distributor ID: Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 Codename: focal --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root ro ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/23/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0075.2019.1023.1448 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0075.2019.1023.1448:bd10/23/2019:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 04:EA:56:21:1E:D3 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17030 acl:0 sco:0 events:2764 errors:0 TX bytes:677849 acl:0 sco:0 commands:2757 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1870837/+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 1870837] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1870837/+attachment/5347851/+files/Lsusb-t.txt -- 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/1870837 Title: hcitool lescan says 'Set scan parameters failed: Input/output error' Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Hi, after some testing with Ubuntu 20.04 beta I couldn't get hcitool lescan working. I get the following error: hcitool lescan Set scan parameters failed: Input/output error Bluetooth hardware: hci0: Type: Primary Bus: USB BD Address: 04:EA:56:21:xx:xx ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1605 acl:0 sco:0 events:123 errors:0 TX bytes:5801 acl:0 sco:0 commands:123 errors:0 Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'xx' Class: 0x200104 Service Classes: Audio Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x100 LMP Version: 5.1 (0xa) Subversion: 0x100 Manufacturer: Intel Corp. (2) It is not hardware related, since I get the same error with a USB bluetooth dongle: hcitool -i hci1 lescan Set scan parameters failed: Input/output error hcitool scan is working fine on both devices; bluetoothctl is also working and able to find ble devices. I would normally prefer bluetoothctl, but I got a software which is based on hcitool. dmesg shows this errors: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! Bluez version: bluez 5.53-0ubuntu2 amd64 System: Distributor ID: Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 Codename: focal --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root ro ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/23/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0075.2019.1023.1448 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0075.2019.1023.1448:bd10/23/2019:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 04:EA:56:21:1E:D3 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17030 acl:0 sco:0 events:2764 errors:0 TX bytes:677849 acl:0 sco:0 commands:2757 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1870837/+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 1870837] Re: hcitool lescan says 'Set scan parameters failed: Input/output error'
apport information ** Tags added: apport-collected ** Description changed: Hi, after some testing with Ubuntu 20.04 beta I couldn't get hcitool lescan working. I get the following error: hcitool lescan Set scan parameters failed: Input/output error Bluetooth hardware: hci0: Type: Primary Bus: USB BD Address: 04:EA:56:21:xx:xx ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1605 acl:0 sco:0 events:123 errors:0 TX bytes:5801 acl:0 sco:0 commands:123 errors:0 Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'xx' Class: 0x200104 Service Classes: Audio Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x100 LMP Version: 5.1 (0xa) Subversion: 0x100 Manufacturer: Intel Corp. (2) It is not hardware related, since I get the same error with a USB bluetooth dongle: hcitool -i hci1 lescan Set scan parameters failed: Input/output error hcitool scan is working fine on both devices; bluetoothctl is also working and able to find ble devices. I would normally prefer bluetoothctl, but I got a software which is based on hcitool. dmesg shows this errors: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! Bluez version: bluez 5.53-0ubuntu2 amd64 System: Distributor ID: Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 Codename: focal + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu22 + Architecture: amd64 + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-04-01 (4 days ago) + InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) + InterestingModules: rfcomm bnep btusb bluetooth + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 0463: MGE UPS Systems UPS + Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB + Bus 001 Device 004: ID 8087:0aaa Intel Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: Intel(R) Client Systems NUC8i3BEH + Package: linux + PackageArchitecture: amd64 + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root ro + ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 + Tags: focal + Uname: Linux 5.4.0-21-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 10/23/2019 + dmi.bios.vendor: Intel Corp. + dmi.bios.version: BECFL357.86A.0075.2019.1023.1448 + dmi.board.name: NUC8BEB + dmi.board.vendor: Intel Corporation + dmi.board.version: J72693-306 + dmi.chassis.type: 35 + dmi.chassis.vendor: Intel Corporation + dmi.chassis.version: 2.0 + dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0075.2019.1023.1448:bd10/23/2019:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: + dmi.product.family: Intel NUC + dmi.product.name: NUC8i3BEH + dmi.product.sku: BOXNUC8i3BEH + dmi.product.version: J72753-305 + dmi.sys.vendor: Intel(R) Client Systems + hciconfig: + hci0:Type: Primary Bus: USB + BD Address: 04:EA:56:21:1E:D3 ACL MTU: 1021:4 SCO MTU: 96:6 + UP RUNNING + RX bytes:17030 acl:0 sco:0 events:2764 errors:0 + TX bytes:677849 acl:0 sco:0 commands:2757 errors:0 ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1870837/+attachment/5347848/+files/CurrentDmesg.txt -- 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/1870837 Title: hcitool lescan says 'Set scan parameters failed: Input/output error' Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Hi, after some testing with Ubuntu 20.04 beta I couldn't get hcitool lescan working. I get the following error: hcitool lescan Set scan parameters failed: Input/output error Bluetooth hardware: hci0: Type: Primary Bus: USB BD Address: 04:EA:56:21:xx:xx ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1605 acl:0 sco:0 events:123 errors:0 TX bytes:5801 acl:0 sco:0 commands:123 errors:0 Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'xx' Class: 0x200104 Service Classes: Audio Device Class:
[Touch-packages] [Bug 1870980] Re: dnsmasq conf file runtime group conflicts with initd
Well I am not sure what happened here . I recently made the jump from Fedora/KDESpin to kubuntu and am still struggling with some of the not so subtle differences (Used Fedora since its inception) . So now I want to close this . Thanks for your prompt response ** Changed in: dnsmasq (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1870980 Title: dnsmasq conf file runtime group conflicts with initd Status in dnsmasq package in Ubuntu: Invalid Bug description: In /etc/dnsmasq.conf a runtime group of 'dnsmasq' is specified The initd start script is creating a pid file and changing its ownership to dnsmasq:nogroup This causes the pid file to not be found (though I'm not sure why since the pid file is owned by user 'dnsmasq') ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: dnsmasq 2.79-1 [modified: etc/dnsmasq.conf] ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: KDE Date: Sun Apr 5 15:44:29 2020 InstallationDate: Installed on 2020-04-04 (1 days ago) InstallationMedia: Kubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.dnsmasq.conf: [modified] mtime.conffile..etc.dnsmasq.conf: 2020-04-05T11:13:49.503651 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1870980/+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 1870837] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1870837/+attachment/5347850/+files/Lspci.txt -- 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/1870837 Title: hcitool lescan says 'Set scan parameters failed: Input/output error' Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Hi, after some testing with Ubuntu 20.04 beta I couldn't get hcitool lescan working. I get the following error: hcitool lescan Set scan parameters failed: Input/output error Bluetooth hardware: hci0: Type: Primary Bus: USB BD Address: 04:EA:56:21:xx:xx ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1605 acl:0 sco:0 events:123 errors:0 TX bytes:5801 acl:0 sco:0 commands:123 errors:0 Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'xx' Class: 0x200104 Service Classes: Audio Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x100 LMP Version: 5.1 (0xa) Subversion: 0x100 Manufacturer: Intel Corp. (2) It is not hardware related, since I get the same error with a USB bluetooth dongle: hcitool -i hci1 lescan Set scan parameters failed: Input/output error hcitool scan is working fine on both devices; bluetoothctl is also working and able to find ble devices. I would normally prefer bluetoothctl, but I got a software which is based on hcitool. dmesg shows this errors: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! Bluez version: bluez 5.53-0ubuntu2 amd64 System: Distributor ID: Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 Codename: focal --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root ro ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/23/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0075.2019.1023.1448 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0075.2019.1023.1448:bd10/23/2019:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 04:EA:56:21:1E:D3 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17030 acl:0 sco:0 events:2764 errors:0 TX bytes:677849 acl:0 sco:0 commands:2757 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1870837/+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 1871149] Re: False apt_pkg.CacheMismatchError
** Summary changed:
-
/usr/bin/unattended-upgrade:apt_pkg.CacheMismatchError:/usr/bin/unattended-upgrade@2512:main:run:get_auto_removable::is_auto_removable
+ False apt_pkg.CacheMismatchError
** Description changed:
- The Ubuntu Error Tracker has been receiving reports about a problem regarding
unattended-upgrades. This problem was most recently seen with package version
2.1, the problem page at
https://errors.ubuntu.com/problem/ff08f6aa104f8e3233da3081835ecc2e9f0452f5
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
+ Python-apt throws CacheMismatchError which is almost certainly false:
+
+ Traceback (most recent call last):
+ File "/usr/bin/unattended-upgrade", line 2512, in
+ sys.exit(main(options))
+ File "/usr/bin/unattended-upgrade", line 1986, in main
+ res = run(options, rootdir, mem_log, logfile_dpkg,
+ File "/usr/bin/unattended-upgrade", line 2398, in run
+ new_pending_autoremovals = get_auto_removable(cache)
+ File "/usr/bin/unattended-upgrade", line 1789, in get_auto_removable
+ return {pkg.name for pkg in cache
+ File "/usr/bin/unattended-upgrade", line 1790, in
+ if pkg.is_auto_removable}
+ File "/usr/lib/python3/dist-packages/apt/package.py", line 1269, in
is_auto_removable
+ self._pcache._depcache.is_garbage(self._pkg))
+ apt_pkg.CacheMismatchError: Object of different cache passed as argument to
apt_pkg.DepCache method
+
+ The relevant code in u-u:
+
+ def get_auto_removable(cache):
+ # type: (apt.Cache) -> AbstractSet[str]
+ return {pkg.name for pkg in cache
+ if pkg.is_auto_removable}
+
+ ---
+
+ The Ubuntu Error Tracker has been receiving reports about a problem
+ regarding unattended-upgrades. This problem was most recently seen with
package version 2.1, the problem page at
https://errors.ubuntu.com/problem/ff08f6aa104f8e3233da3081835ecc2e9f0452f5
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/.
** Package changed: unattended-upgrades (Ubuntu) => python-apt (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1871149
Title:
False apt_pkg.CacheMismatchError
Status in python-apt package in Ubuntu:
New
Bug description:
Python-apt throws CacheMismatchError which is almost certainly false:
Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 2512, in
sys.exit(main(options))
File "/usr/bin/unattended-upgrade", line 1986, in main
res = run(options, rootdir, mem_log, logfile_dpkg,
File "/usr/bin/unattended-upgrade", line 2398, in run
new_pending_autoremovals = get_auto_removable(cache)
File "/usr/bin/unattended-upgrade", line 1789, in get_auto_removable
return {pkg.name for pkg in cache
File "/usr/bin/unattended-upgrade", line 1790, in
if pkg.is_auto_removable}
File "/usr/lib/python3/dist-packages/apt/package.py", line 1269, in
is_auto_removable
self._pcache._depcache.is_garbage(self._pkg))
apt_pkg.CacheMismatchError: Object of different cache passed as argument to
apt_pkg.DepCache method
The relevant code in u-u:
def get_auto_removable(cache):
# type: (apt.Cache) -> AbstractSet[str]
return {pkg.name for pkg in cache
if pkg.is_auto_removable}
---
The Ubuntu Error Tracker has been receiving reports about a problem
regarding unattended-upgrades. This problem was most recently seen with
package version 2.1, the problem page at
https://errors.ubuntu.com/problem/ff08f6aa104f8e3233da3081835ecc2e9f0452f5
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
[Touch-packages] [Bug 1871153] [NEW] /usr/bin/unattended-upgrade:apt.cache.CacheClosedException:/usr/bin/unattended-upgrade@2512:main:run:do_auto_remove:cache_commit:commit:_fetch_archives
Public bug reported: Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 2512, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1986, in main res = run(options, rootdir, mem_log, logfile_dpkg, File "/usr/bin/unattended-upgrade", line 2307, in run kernel_pkgs_kept_installed) = do_auto_remove( File "/usr/bin/unattended-upgrade", line 1876, in do_auto_remove res, error = cache_commit(cache, logfile_dpkg, verbose) File "/usr/bin/unattended-upgrade", line 861, in cache_commit res = cache.commit(install_progress=iprogress) File "/usr/lib/python3/dist-packages/apt/cache.py", line 678, in commit res = self._fetch_archives(fetcher, pm, File "/usr/lib/python3/dist-packages/apt/cache.py", line 466, in _fetch_archives raise CacheClosedException( apt.cache.CacheClosedException: Cache object used after close() called --- The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 2.1, the problem page at https://errors.ubuntu.com/problem/b923ed6f4c01a301c3d3910bdb0eed754b7214f7 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/. ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1871153 Title: /usr/bin/unattended-upgrade:apt.cache.CacheClosedException:/usr/bin /unattended- upgrade@2512:main:run:do_auto_remove:cache_commit:commit:_fetch_archives Status in unattended-upgrades package in Ubuntu: New Bug description: Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 2512, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1986, in main res = run(options, rootdir, mem_log, logfile_dpkg, File "/usr/bin/unattended-upgrade", line 2307, in run kernel_pkgs_kept_installed) = do_auto_remove( File "/usr/bin/unattended-upgrade", line 1876, in do_auto_remove res, error = cache_commit(cache, logfile_dpkg, verbose) File "/usr/bin/unattended-upgrade", line 861, in cache_commit res = cache.commit(install_progress=iprogress) File "/usr/lib/python3/dist-packages/apt/cache.py", line 678, in commit res = self._fetch_archives(fetcher, pm, File "/usr/lib/python3/dist-packages/apt/cache.py", line 466, in _fetch_archives raise CacheClosedException( apt.cache.CacheClosedException: Cache object used after close() called --- The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 2.1, the problem page at https://errors.ubuntu.com/problem/b923ed6f4c01a301c3d3910bdb0eed754b7214f7 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/unattended-upgrades/+bug/1871153/+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 1871153] Re: /usr/bin/unattended-upgrade:apt.cache.CacheClosedException:/usr/bin/unattended-upgrade@2512:main:run:do_auto_remove:cache_commit:commit:_fetch_archives
** Description changed: + Traceback (most recent call last): + File "/usr/bin/unattended-upgrade", line 2512, in + sys.exit(main(options)) + File "/usr/bin/unattended-upgrade", line 1986, in main + res = run(options, rootdir, mem_log, logfile_dpkg, + File "/usr/bin/unattended-upgrade", line 2307, in run + kernel_pkgs_kept_installed) = do_auto_remove( + File "/usr/bin/unattended-upgrade", line 1876, in do_auto_remove + res, error = cache_commit(cache, logfile_dpkg, verbose) + File "/usr/bin/unattended-upgrade", line 861, in cache_commit + res = cache.commit(install_progress=iprogress) + File "/usr/lib/python3/dist-packages/apt/cache.py", line 678, in commit + res = self._fetch_archives(fetcher, pm, + File "/usr/lib/python3/dist-packages/apt/cache.py", line 466, in _fetch_archives + raise CacheClosedException( + apt.cache.CacheClosedException: Cache object used after close() called + + --- + The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 2.1, the problem page at https://errors.ubuntu.com/problem/b923ed6f4c01a301c3d3910bdb0eed754b7214f7 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/. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1871153 Title: /usr/bin/unattended-upgrade:apt.cache.CacheClosedException:/usr/bin /unattended- upgrade@2512:main:run:do_auto_remove:cache_commit:commit:_fetch_archives Status in unattended-upgrades package in Ubuntu: New Bug description: Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 2512, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1986, in main res = run(options, rootdir, mem_log, logfile_dpkg, File "/usr/bin/unattended-upgrade", line 2307, in run kernel_pkgs_kept_installed) = do_auto_remove( File "/usr/bin/unattended-upgrade", line 1876, in do_auto_remove res, error = cache_commit(cache, logfile_dpkg, verbose) File "/usr/bin/unattended-upgrade", line 861, in cache_commit res = cache.commit(install_progress=iprogress) File "/usr/lib/python3/dist-packages/apt/cache.py", line 678, in commit res = self._fetch_archives(fetcher, pm, File "/usr/lib/python3/dist-packages/apt/cache.py", line 466, in _fetch_archives raise CacheClosedException( apt.cache.CacheClosedException: Cache object used after close() called --- The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 2.1, the problem page at https://errors.ubuntu.com/problem/b923ed6f4c01a301c3d3910bdb0eed754b7214f7 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/unattended-upgrades/+bug/1871153/+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 1871149] [NEW] False apt_pkg.CacheMismatchError
Public bug reported:
Python-apt throws CacheMismatchError which is almost certainly false:
Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 2512, in
sys.exit(main(options))
File "/usr/bin/unattended-upgrade", line 1986, in main
res = run(options, rootdir, mem_log, logfile_dpkg,
File "/usr/bin/unattended-upgrade", line 2398, in run
new_pending_autoremovals = get_auto_removable(cache)
File "/usr/bin/unattended-upgrade", line 1789, in get_auto_removable
return {pkg.name for pkg in cache
File "/usr/bin/unattended-upgrade", line 1790, in
if pkg.is_auto_removable}
File "/usr/lib/python3/dist-packages/apt/package.py", line 1269, in
is_auto_removable
self._pcache._depcache.is_garbage(self._pkg))
apt_pkg.CacheMismatchError: Object of different cache passed as argument to
apt_pkg.DepCache method
The relevant code in u-u:
def get_auto_removable(cache):
# type: (apt.Cache) -> AbstractSet[str]
return {pkg.name for pkg in cache
if pkg.is_auto_removable}
---
The Ubuntu Error Tracker has been receiving reports about a problem
regarding unattended-upgrades. This problem was most recently seen with
package version 2.1, the problem page at
https://errors.ubuntu.com/problem/ff08f6aa104f8e3233da3081835ecc2e9f0452f5
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/.
** Affects: python-apt (Ubuntu)
Importance: Undecided
Status: New
** Tags: focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1871149
Title:
False apt_pkg.CacheMismatchError
Status in python-apt package in Ubuntu:
New
Bug description:
Python-apt throws CacheMismatchError which is almost certainly false:
Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 2512, in
sys.exit(main(options))
File "/usr/bin/unattended-upgrade", line 1986, in main
res = run(options, rootdir, mem_log, logfile_dpkg,
File "/usr/bin/unattended-upgrade", line 2398, in run
new_pending_autoremovals = get_auto_removable(cache)
File "/usr/bin/unattended-upgrade", line 1789, in get_auto_removable
return {pkg.name for pkg in cache
File "/usr/bin/unattended-upgrade", line 1790, in
if pkg.is_auto_removable}
File "/usr/lib/python3/dist-packages/apt/package.py", line 1269, in
is_auto_removable
self._pcache._depcache.is_garbage(self._pkg))
apt_pkg.CacheMismatchError: Object of different cache passed as argument to
apt_pkg.DepCache method
The relevant code in u-u:
def get_auto_removable(cache):
# type: (apt.Cache) -> AbstractSet[str]
return {pkg.name for pkg in cache
if pkg.is_auto_removable}
---
The Ubuntu Error Tracker has been receiving reports about a problem
regarding unattended-upgrades. This problem was most recently seen with
package version 2.1, the problem page at
https://errors.ubuntu.com/problem/ff08f6aa104f8e3233da3081835ecc2e9f0452f5
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/python-apt/+bug/1871149/+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 1871006] Re: add-apt-repository crashed with AttributeError in _get_https_content_py3(): 'InvalidURL' object has no attribute 'reason'
Thanks, indeed that command triggers the error
** Changed in: software-properties (Ubuntu)
Status: Incomplete => Confirmed
** Description changed:
Release: 20.04 Ubuntu Focal Fossa (development branch)
Package/Program: add-apt-repository
- Command: add-apt-repository --remove
+ Command:
+ $ sudo add-apt-repository --remove ppa:"deb [arch=amd64]
https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"
Expected response:
- Either to get the ppa removed or the exception handled with a message
"unable to find the URL"
+ Either to get the ppa removed or the exception handled with a message
"unable to find the URL"
What happened instead:
- The traceback of an exception was printed in the terminal.
+ The traceback of an exception was printed in the terminal.
Traceback:
Traceback (most recent call last):
- File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 138,
in _get_https_content_py3
- lp_page = urllib.request.urlopen(request,
- File "/usr/lib/python3.8/urllib/request.py", line 222, in urlopen
- return opener.open(url, data, timeout)
- File "/usr/lib/python3.8/urllib/request.py", line 525, in open
- response = self._open(req, data)
- File "/usr/lib/python3.8/urllib/request.py", line 542, in _open
- result = self._call_chain(self.handle_open, protocol, protocol +
- File "/usr/lib/python3.8/urllib/request.py", line 502, in _call_chain
- result = func(*args)
- File "/usr/lib/python3.8/urllib/request.py", line 1362, in https_open
- return self.do_open(http.client.HTTPSConnection, req,
- File "/usr/lib/python3.8/urllib/request.py", line 1319, in do_open
- h.request(req.get_method(), req.selector, req.data, headers,
- File "/usr/lib/python3.8/http/client.py", line 1230, in request
- self._send_request(method, url, body, headers, encode_chunked)
- File "/usr/lib/python3.8/http/client.py", line 1241, in _send_request
- self.putrequest(method, url, **skips)
- File "/usr/lib/python3.8/http/client.py", line 1092, in putrequest
- self._validate_path(url)
- File "/usr/lib/python3.8/http/client.py", line 1183, in _validate_path
- raise InvalidURL(f"URL can't contain control characters. {url!r} "
+ File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 138,
in _get_https_content_py3
+ lp_page = urllib.request.urlopen(request,
+ File "/usr/lib/python3.8/urllib/request.py", line 222, in urlopen
+ return opener.open(url, data, timeout)
+ File "/usr/lib/python3.8/urllib/request.py", line 525, in open
+ response = self._open(req, data)
+ File "/usr/lib/python3.8/urllib/request.py", line 542, in _open
+ result = self._call_chain(self.handle_open, protocol, protocol +
+ File "/usr/lib/python3.8/urllib/request.py", line 502, in _call_chain
+ result = func(*args)
+ File "/usr/lib/python3.8/urllib/request.py", line 1362, in https_open
+ return self.do_open(http.client.HTTPSConnection, req,
+ File "/usr/lib/python3.8/urllib/request.py", line 1319, in do_open
+ h.request(req.get_method(), req.selector, req.data, headers,
+ File "/usr/lib/python3.8/http/client.py", line 1230, in request
+ self._send_request(method, url, body, headers, encode_chunked)
+ File "/usr/lib/python3.8/http/client.py", line 1241, in _send_request
+ self.putrequest(method, url, **skips)
+ File "/usr/lib/python3.8/http/client.py", line 1092, in putrequest
+ self._validate_path(url)
+ File "/usr/lib/python3.8/http/client.py", line 1183, in _validate_path
+ raise InvalidURL(f"URL can't contain control characters. {url!r} "
http.client.InvalidURL: URL can't contain control characters.
'/api/devel/~deb [arch=amd64] https/+archive/ubuntu/ppa' (found at least ' ')
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
- File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 380,
in get_ppa_info
- ret = get_ppa_info_from_lp(user, ppa)
- File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 110,
in get_ppa_info_from_lp
- return get_info_from_lp(lp_url)
- File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 104,
in get_info_from_lp
- return get_info_from_https(lp_url, True)
- File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 96,
in get_info_from_https
- data = func(lp_url=url, accept_json=accept_json,
retry_delays=retry_delays)
- File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 143,
in _get_https_content_py3
- "Error reading %s (%d tries): %s" % (lp_url, trynum, e.reason),
+ File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 380,
in get_ppa_info
+ ret = get_ppa_info_from_lp(user, ppa)
+ File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 110,
in get_ppa_info_from_lp
+ return get_info_from_lp(lp_url)
+ File
