[Touch-packages] [Bug 1835957] Re: cupsd gobbles up resources
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1835957 Title: cupsd gobbles up resources Status in cups package in Ubuntu: Expired Bug description: My computer has got very slow since 4 or 5 weeks. Finally, I checked resource usage with and the culprit seems to be cupsd. Here is an output line from a few minutes after boot: 30900 root 20 0 305452 287396 5768 S 5,3 9,3 0:41.34 cupsd Then after an hour and a half (with nothing printed): 30900 root 20 0 2565692 2,125g 2240 R 79,0 71,9 93:01.45 cupsd So %CPU grows 5,3 -> 79,0 and %MEM, 9,3 -> 71,9. Not good. A user on a local forum asked whether printing anything helped, and, certainly, it did. After I did (print something), cupsd was happy with less than 1% of CPU and MEM. So if I print something after every boot, the problem does go away. But that is not really a solution, is it? Running Lubuntu 16.04.6 LTS (32-bit). cups version is 2.1.3-4ubuntu0.9. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1835957/+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 1797717] Re: fstrim -av tries to trim read only mounted ntfs-3g and fails
** Tags added: disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1797717 Title: fstrim -av tries to trim read only mounted ntfs-3g and fails Status in util-linux package in Ubuntu: Confirmed Bug description: If I run sudo fstrim -av I see: /media/SSD_Data: 2 GiB (2145820672 bytes) trimmed fstrim: /media/Win7: FITRIM ioctl failed: Bad file descriptor /: 26.9 GiB (28823887872 bytes) trimmed /media/SSD_Data is read-write mounted NTFS via ntfs-3g, and /media/Win7 is read-only mounted NTFS, also via ntfs-3g. Lines from fstab: UUID=censored /media/SSD_Data ntfs-3g rw,noatime,nofail,big_writes,windows_names,nosuid,nodev,allow_other,hide_hid_files,inherit,noexec 0 0 UUID=censored /media/Win7 ntfs-3g ro,nofail,big_writes,windows_names,nosuid,nodev,allow_other,noexec,hide_hid_files 0 0 If I do sudo umount /media/Win7 and then sudo mount -o rw /media/Win7 then sudo fstrim -av takes longer and succeeds for all filesystems. So, it seems the read only is the problem. This seems cosmetic, but it causes periodic runs of fstrim via systemd to report failures. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: util-linux 2.32-0.1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Oct 13 15:25:41 2018 SourcePackage: util-linux UpgradeStatus: Upgraded to cosmic on 2018-10-11 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1797717/+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 1845190] Re: binutils nm wrong output format breaks i386 nm work
** Changed in: binutils Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1845190 Title: binutils nm wrong output format breaks i386 nm work Status in binutils: Fix Released Status in binutils package in Ubuntu: Confirmed Bug description: discovered with diffoscope autopkgregression, looks like a real bug, based on https://salsa.debian.org/reproducible-builds/diffoscope/issues/69 To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1845190/+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 1845190]
Fixed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1845190 Title: binutils nm wrong output format breaks i386 nm work Status in binutils: Fix Released Status in binutils package in Ubuntu: Confirmed Bug description: discovered with diffoscope autopkgregression, looks like a real bug, based on https://salsa.debian.org/reproducible-builds/diffoscope/issues/69 To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1845190/+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 935681] Re: "Restart services during package upgrades without asking?" fails to honor --yes for apt-get
This issues show up again on Bionic now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/935681 Title: "Restart services during package upgrades without asking?" fails to honor --yes for apt-get Status in eglibc package in Ubuntu: Confirmed Bug description: I left an old netbook to do an "apt-get -y dist-upgrade" overnight, and when I returned to it the next morning, the upgrades were unfinished because libc upgrade was waiting for me to respond to "Restart services during package upgrades without asking?" It looks like the question is prioritized depending on whether the upgrade is done on desktop or not, and if it's not, the priority is set critical. According to documentation [1], critical is for "Items that will probably break the system without user intervention." I don't think restart-without-asking satisfies that condition. * [1] http://www.debian.org/doc/packaging- manuals/debconf_specification.html#AEN101 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libc6 2.15-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-17.26-generic-pae 3.2.6 Uname: Linux 3.2.0-17-generic-pae i686 ApportVersion: 1.91-0ubuntu1 Architecture: i386 Date: Sat Feb 18 21:07:37 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) ProcEnviron: LANGUAGE=fi:en_US:en PATH=(custom, user) LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: eglibc UpgradeStatus: Upgraded to precise on 2012-02-17 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/935681/+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 1845190] Re: binutils nm wrong output format breaks i386 nm work
** Changed in: binutils Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1845190 Title: binutils nm wrong output format breaks i386 nm work Status in binutils: In Progress Status in binutils package in Ubuntu: Confirmed Bug description: discovered with diffoscope autopkgregression, looks like a real bug, based on https://salsa.debian.org/reproducible-builds/diffoscope/issues/69 To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1845190/+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 1845190]
The binutils-2_33-branch branch has been updated by Alan Modra : https://sourceware.org/git/gitweb.cgi?p=binutils- gdb.git;h=895b6d98785ba89819820aa5f4abed17fbb28c37 commit 895b6d98785ba89819820aa5f4abed17fbb28c37 Author: Alan Modra Date: Tue Sep 24 22:47:13 2019 +0930 PR25031, nm reports wrong address on 32bit Using saved_format breaks when nm is presented with multiple object files, some 32-bit and some 64-bit. PR 25031 * nm.c (print_format_string): New. (get_print_format): Delete saved_format. Move earlier. (set_print_width): Call get_print_format. (print_value): Use print_format_string. (cherry picked from commit 352f6bc3e5b23e76d8e6f56fb7db4e57d8f5d5bd) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1845190 Title: binutils nm wrong output format breaks i386 nm work Status in binutils: In Progress Status in binutils package in Ubuntu: Confirmed Bug description: discovered with diffoscope autopkgregression, looks like a real bug, based on https://salsa.debian.org/reproducible-builds/diffoscope/issues/69 To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1845190/+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 1845190]
The master branch has been updated by Alan Modra : https://sourceware.org/git/gitweb.cgi?p=binutils- gdb.git;h=352f6bc3e5b23e76d8e6f56fb7db4e57d8f5d5bd commit 352f6bc3e5b23e76d8e6f56fb7db4e57d8f5d5bd Author: Alan Modra Date: Tue Sep 24 22:47:13 2019 +0930 PR25031, nm reports wrong address on 32bit Using saved_format breaks when nm is presented with multiple object files, some 32-bit and some 64-bit. PR 25031 * nm.c (print_format_string): New. (get_print_format): Delete saved_format. Move earlier. (set_print_width): Call get_print_format. (print_value): Use print_format_string. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1845190 Title: binutils nm wrong output format breaks i386 nm work Status in binutils: In Progress Status in binutils package in Ubuntu: Confirmed Bug description: discovered with diffoscope autopkgregression, looks like a real bug, based on https://salsa.debian.org/reproducible-builds/diffoscope/issues/69 To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1845190/+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 1845190] Re: binutils nm wrong output format breaks i386 nm work
> on amd64 it works correctly: > > nm elfmix1.not_a > return42_or_3_long_name.o: > T return42_or_3 > return42_or_3_long_name.obj: > T return42_or_3 No, on amd64 the bug is the same as on i386. The correct output on both i386 and amd64 must be: return42_or_3_long_name.o: T return42_or_3 return42_or_3_long_name.obj: T return42_or_3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1845190 Title: binutils nm wrong output format breaks i386 nm work Status in binutils: New Status in binutils package in Ubuntu: Confirmed Bug description: discovered with diffoscope autopkgregression, looks like a real bug, based on https://salsa.debian.org/reproducible-builds/diffoscope/issues/69 To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1845190/+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 1844853] Re: IBus no longer works in Qt applications after upgrade
** Changed in: ibus Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1844853 Title: IBus no longer works in Qt applications after upgrade Status in ibus: Fix Released Status in ibus package in Ubuntu: Fix Released Status in ibus package in Debian: Unknown Bug description: Kubuntu Release 18.04.3 LTS Expected behavior: ibus continues working as before after applying security update 1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5. Observed behavior: ibus is not usable anymore in Qt applications. After updating ibus and the related packages ibus-gtk, ibus-gtk3, libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using shift-space no longer changes the selected input method and even when i switch to the mozc input method in a gtk application, i can not use it in any Qt applications. When starting qtconfig in a terminal, I also get the following message: Bus::open: Connect ibus failed! IBusInputContext::createInputContext: no connection to ibus-daemon This bug was not present in version 1.5.17-3ubuntu5 and I also confirmed that downgrading the packages to version 1.5.17-3ubuntu4 restores ibus functionality in Qt applications. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu5.1 ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 21 07:58:56 2019 InstallationDate: Installed on 2019-06-28 (84 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1844853/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832651] Re: jackdbus fails to start: cannot allocate memory
I was unable to recreate this on an installation of Eoan, which will become Ubuntu 19.10, using systemd version 241-7ubuntu1 and jackd2 version 1.9.12~dfsg-2build1 subsequently I'm setting the Eoan task to Fix Released. ** Changed in: systemd (Ubuntu Eoan) Status: Confirmed => Fix Released -- 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/1832651 Title: jackdbus fails to start: cannot allocate memory Status in systemd: Fix Released Status in jackd2 package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in jackd2 source package in Eoan: Invalid Status in systemd source package in Eoan: Fix Released Bug description: The `.log/jack/jackdbus.log` shows the following after trying to start/restart jack using "Ubuntu Studio Controls" (also tried using `jack_control start`): ERROR: Cannot lock down 82280346 byte memory area (Cannot allocate memory) This is a fresh install of Ubuntu Studio 19.04, installed via USB. The first thing I did after installing was check to see if jack was running, but unfortunately it's not working. The error would seem to indicate that I'm not in the `audio` group, however checking `groups` shows that I am in the audio group. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: jackd2 1.9.12~dfsg-2build1 ProcVersionSignature: Ubuntu 5.0.0-13.14-lowlatency 5.0.6 Uname: Linux 5.0.0-13-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 12 18:13:25 2019 InstallationDate: Installed on 2019-06-12 (0 days ago) InstallationMedia: Ubuntu-Studio 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: jackd2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1832651/+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 1586528] Re: Avahi-daemon withdraws address record
I found a workaround this problem. Check my git https://github.com/WillyWeiss/-Avahi-daemon-withdraws-address-record-/blob/master/README.md I just a simple bash that check for a valid IP Address on a given card. If the IP is not found then 'dhclient' will be called on that given interface(card) It is working by default on eth0 but you can add more cards in the script. Just read the readme in the git above. Hope it helps. Prove of functionality: Sep 24 16:47:40 MyHostName rngd[395]: stats: Entropy starvations: 0 Sep 24 16:47:40 MyHostName rngd[395]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us Sep 24 16:47:46 MyHostName avahi-daemon[380]: Withdrawing address record for 192.168.0.13 on eth0. Sep 24 16:47:46 MyHostName avahi-daemon[380]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.0.13. Sep 24 16:47:46 MyHostName avahi-daemon[380]: Interface eth0.IPv4 no longer relevant for mDNS. Sep 24 16:47:47 MyHostName dhclient[4487]: DHCPREQUEST for 192.168.0.13 on eth0 to 255.255.255.255 port 67 Sep 24 16:47:47 MyHostName dhclient[4487]: DHCPACK of 192.168.0.13 from 192.168.0.1 Sep 24 16:47:47 MyHostName avahi-daemon[380]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.0.13. Sep 24 16:47:47 MyHostName avahi-daemon[380]: New relevant interface eth0.IPv4 for mDNS. Sep 24 16:47:47 MyHostName avahi-daemon[380]: Registering new address record for 192.168.0.13 on eth0.IPv4. Sep 24 16:47:47 MyHostName dhclient[4487]: bound to 192.168.0.13 -- renewal in 41664 seconds. -- 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/1586528 Title: Avahi-daemon withdraws address record Status in avahi package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Confirmed Bug description: For some reason, if I leave my Ubuntu VM up for a prolonged period of time the machine will lose connection to the network. ip addr shows that the nic port no longer has an address and an examination of the syslog shows this: May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record for 10.0.2.15 on enp0s3. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast group on interface enp0s3.IPv4 with address 10.0.2.15. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no longer relevant for mDNS. for no known reason. The only reliable way to get the network to come back (that I have found) is a full reboot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 27 15:11:34 2016 InstallationDate: Installed on 2015-10-22 (218 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: avahi UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+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 1759836] Re: systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez
Hello Vinícius, or anyone else affected, Accepted bluez into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/bluez/5.48-0ubuntu3.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: bluez (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1759836 Title: systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez Status in linux: Confirmed Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in bluez source package in Bionic: Fix Committed Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: Invalid Status in bluez source package in Disco: Fix Committed Status in linux source package in Disco: Invalid Status in systemd source package in Disco: Invalid Status in bluez source package in Eoan: Fix Released Status in linux source package in Eoan: Invalid Status in systemd source package in Eoan: Invalid Status in bluez package in Debian: New Bug description: [impact] on specific Dell systems, with a specific usb bluetooth device built- in, the udev rule 'hid2hci' provided by the 'bluez' package causes an endless loop of uevents resulting from 'bind' or 'unbind' kernel uevents. These new events were added to the kernel after the 'hid2hci' udev rule was written. [test case] the specific Dell system is required to be able to reproduce this, or at least the specific usb bluetooth hardware included in that system. Reproducing this is reportedly easy, for example comment 75 indicates it happens on every boot. When this happens, any process monitor (e.g. ps, top, etc) will show the 'udevd' process using 100% of a cpu, and 'udevadm monitor' should show repeated 'bind' and 'unbind' events as mentioned in comment 39. [regression potential] as this alters what kernel uevents the 'hid2hci' udev rule processes, regressions would involve the affected usb bluetooth device failing to be set up, or otherwise not processing the uevents correctly. [other info] this is not fixed yet upstream, as of my last check, but has been submitted upstream as mentioned in comment 95. original description: -- The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:p
[Touch-packages] [Bug 1402793] Re: [ABRA A7 V1, VIA VT1802, Green Headphone Out, Front] No sound at all
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1402793 Title: [ABRA A7 V1, VIA VT1802, Green Headphone Out, Front] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: I can get sound from speakers but I can't get my jack to work. I tried many things with no help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fma2341 F pulseaudio /dev/snd/controlC1: fma2341 F pulseaudio CurrentDesktop: Unity Date: Mon Dec 15 21:04:39 2014 InstallationDate: Installed on 2014-07-08 (159 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm1601 F pulseaudio fma2341 F pulseaudio /dev/snd/controlC1: lightdm1601 F pulseaudio fma2341 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_Type: No sound at all Title: [ABRA A7 V1, VIA VT1802, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2014 dmi.bios.vendor: MONSTER dmi.bios.version: ABRA A7 V1 dmi.board.asset.tag: Tag 12345 dmi.board.name: ABRA A7 V1 dmi.board.vendor: MONSTER dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: MONSTER dmi.chassis.version: N/A dmi.modalias: dmi:bvnMONSTER:bvrABRAA7V1:bd04/08/2014:svnMONSTER:pnABRAA7V1:pvrNotApplicable:rvnMONSTER:rnABRAA7V1:rvrNotApplicable:cvnMONSTER:ct9:cvrN/A: dmi.product.name: ABRA A7 V1 dmi.product.version: Not Applicable dmi.sys.vendor: MONSTER mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-12-04T18:12:09.578053 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1402793/+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 1845245] [NEW] Behaviour change in systemd 243 breaks netplan.io ethernets autopkgtest
Public bug reported: The commit introducing the regression is this one: commit bd08ce56156751d58584a44e766ef61340cdae2d Author: Yu Watanabe Date: Mon Apr 15 17:34:00 2019 +0900 network: prevent interfaces to be initialized multiple times When a uevent is received during the relevant interface is in LINK_STATE_PENDING, then the interface may be initialized twice. To prevent that, this introduces LINK_STATE_INITIALIZED. I'll triage further and possibly revert the change in the next 243-based upload. ** Affects: netplan.io (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Also affects: netplan.io (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1845245 Title: Behaviour change in systemd 243 breaks netplan.io ethernets autopkgtest Status in netplan.io package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: The commit introducing the regression is this one: commit bd08ce56156751d58584a44e766ef61340cdae2d Author: Yu Watanabe Date: Mon Apr 15 17:34:00 2019 +0900 network: prevent interfaces to be initialized multiple times When a uevent is received during the relevant interface is in LINK_STATE_PENDING, then the interface may be initialized twice. To prevent that, this introduces LINK_STATE_INITIALIZED. I'll triage further and possibly revert the change in the next 243-based upload. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1845245/+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 1831296] Re: __main__.SeccompTest is failing on Ubuntu CI
included in systemd: https://launchpad.net/ubuntu/+source/systemd/242-6ubuntu1 ** Changed in: systemd (Ubuntu Eoan) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1831296 Title: __main__.SeccompTest is failing on Ubuntu CI Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Eoan: Fix Released Bug description: Since https://github.com/systemd/systemd/pull/12430 was merged and libsecomp was updated the test has been failing on Ubuntu CI: https://github.com/systemd/systemd/issues/12709. By analogy with https://github.com/systemd/systemd/pull/12430/commits/c3ab2c389ee60d92fb8d7fe779ae9c4e3c092e4c, the test should look for either "killed" or "dumped". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1831296/+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 1759836] Re: systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez
Hello Vinícius, or anyone else affected, Accepted bluez into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/bluez/5.50-0ubuntu2.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: bluez (Ubuntu Disco) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-disco -- 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/1759836 Title: systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez Status in linux: Confirmed Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in bluez source package in Bionic: In Progress Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: Invalid Status in bluez source package in Disco: Fix Committed Status in linux source package in Disco: Invalid Status in systemd source package in Disco: Invalid Status in bluez source package in Eoan: Fix Released Status in linux source package in Eoan: Invalid Status in systemd source package in Eoan: Invalid Status in bluez package in Debian: New Bug description: [impact] on specific Dell systems, with a specific usb bluetooth device built- in, the udev rule 'hid2hci' provided by the 'bluez' package causes an endless loop of uevents resulting from 'bind' or 'unbind' kernel uevents. These new events were added to the kernel after the 'hid2hci' udev rule was written. [test case] the specific Dell system is required to be able to reproduce this, or at least the specific usb bluetooth hardware included in that system. Reproducing this is reportedly easy, for example comment 75 indicates it happens on every boot. When this happens, any process monitor (e.g. ps, top, etc) will show the 'udevd' process using 100% of a cpu, and 'udevadm monitor' should show repeated 'bind' and 'unbind' events as mentioned in comment 39. [regression potential] as this alters what kernel uevents the 'hid2hci' udev rule processes, regressions would involve the affected usb bluetooth device failing to be set up, or otherwise not processing the uevents correctly. [other info] this is not fixed yet upstream, as of my last check, but has been submitted upstream as mentioned in comment 95. original description: -- The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:s
[Touch-packages] [Bug 1843630] Re: ubuntu-bug not opening anything in the browser
** Attachment added: "crashdb.conf" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1843630/+attachment/5290988/+files/crashdb.conf ** Changed in: apport (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1843630 Title: ubuntu-bug not opening anything in the browser Status in apport package in Ubuntu: New Bug description: Ubuntu 19.04, "ubuntu-bug apport" pops up the "Send problem report to the developers?" with the "Don't send" and "Send" buttons, but when I click on "Send" nothing happens. I have the "problem_types" line commented out in /etc/apport/crashdb.conf, though I don't know if that's relevant when I'm trying to report a bug, not a crash. I have no idea how to troubleshoot this further. Please advise. The same problem occurs for "ubuntu-bug needrestart". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1843630/+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 1759836] Re: systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez
** Description changed: - The systemd-udevd proccess consumes 100% of a thread everytime, but i'm - not noticing any difference in my computer. + [impact] + + on specific Dell systems, with a specific usb bluetooth device built-in, + the udev rule 'hid2hci' provided by the 'bluez' package causes an + endless loop of uevents resulting from 'bind' or 'unbind' kernel + uevents. These new events were added to the kernel after the 'hid2hci' + udev rule was written. + + [test case] + + the specific Dell system is required to be able to reproduce this, or at + least the specific usb bluetooth hardware included in that system. + + Reproducing this is reportedly easy, for example comment 75 indicates it + happens on every boot. + + When this happens, any process monitor (e.g. ps, top, etc) will show the + 'udevd' process using 100% of a cpu, and 'udevadm monitor' should show + repeated 'bind' and 'unbind' events as mentioned in comment 39. + + [regression potential] + + as this alters what kernel uevents the 'hid2hci' udev rule processes, + regressions would involve the affected usb bluetooth device failing to + be set up, or otherwise not processing the uevents correctly. + + [other info] + + this is not fixed yet upstream, as of my last check, but has been + submitted upstream as mentioned in comment 95. + + + original description: + + -- + + + The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. -- 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/1759836 Title: systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez Status in linux: Confirmed Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in bluez source package in Bionic: In Progress Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: Invalid Status in bluez source package in Disco: Fix Committed Status in linux source package in Disco: Invalid Status in systemd source package in Disco: Invalid Status in bluez source package in Eoan: Fix Released Status in linux source package in Eoan: Invalid Status in systemd source package in Eoan: Invalid Status in bluez package in Debian: New Bug description: [impact] on specific Dell systems, with a specific usb bluetooth device built- in, the udev rule 'hid2hci' provided by the 'bluez' package causes an endless loop of uevents resulting from 'bind' or 'unbind' kernel uevents. These new events were added to the kernel after the 'hid2hci' udev rule was written. [test case] the specific Dell system is required to be able to reproduce this, or at least the specific usb bluetooth hardware included in that system. Reproducing this is reportedly easy, for example comment 75 indicates it happens on every boot. When this happens, any process monitor (e.g. ps, top, etc) will show the 'udevd' process using 100% of a cpu, and 'udevadm monitor' should show repeated 'bind' and 'unbind' events as mentioned in comment 39. [regression potential] as this alters what kernel uevents the 'hid2hci' udev rule processes, regressions would involve the affected usb bluetooth device failing to be set up, or otherwise not p
Re: [Touch-packages] [Bug 1531184] Re: [SRU] dnsmasq doesn't start on boot because its interface isn't up yet
On Tue, Sep 24, 2019 at 04:57:59PM -, Benjamin Bach wrote: > @Robie Basak > > > Will this delay boot for laptop users who are offline, for example? > > If someone has installed the dnsmasq package with the dnsmasq.service > file, they already intend to run this as a network-dependent service? > It's not part of a normal user's setup - I think they have dnsmasq-base, > which doesn't include the service. They already intend to run this as a service, yes. But why do you qualify that as "network-dependent"? dnsmasq is still useful on a laptop only occasionally connected to the Internet, is it not? What if a user wants it inward-facing, for example for VMs? -- 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/1531184 Title: [SRU] dnsmasq doesn't start on boot because its interface isn't up yet Status in One Hundred Papercuts: Confirmed Status in dnsmasq package in Ubuntu: Confirmed Status in dnsmasq package in Debian: New Bug description: [Impact] dnsmasq will fail to respond on network devices that weren't up when its service started, thus not binding as expected. [Test Case] TBD [Regression Potential] The fix is just configuring the order of service startup, so is unlikely to create any regressions. Things to watch would be service related misbehaviors and general availability of the dnsmasq functionality. [Fix] Straightforward packaging fix to the service to make it delay startup until after the network is online. https://bugs.debian.org/cgi- bin/bugreport.cgi?att=1;bug=774970;filename=774970-network- online.debdiff;msg=22 [Discussion] [Original Report] My dnsmasq instance uses "interface=br-vz0" and the interface br-vz0 is managed manually in /etc/network/interfaces. During boot, dnsmasq is started before br-vz0 is created and this causes dnsmasq to exit: Jan 5 08:56:16 simon-laptop dnsmasq[1008]: dnsmasq: unknown interface br-vz0 Jan 5 08:56:16 simon-laptop dnsmasq[1008]: unknown interface br-vz0 Jan 5 08:56:16 simon-laptop dnsmasq[1008]: FAILED to start up Jan 5 08:56:17 simon-laptop NetworkManager[937]: NetworkManager (version 1.0.4) is starting... ... Jan 5 08:56:18 simon-laptop NetworkManager[937]: interface-parser: parsing file /etc/network/interfaces ... Jan 5 08:56:18 simon-laptop NetworkManager[937]: found bridge ports none for br-vz0 Jan 5 08:56:18 simon-laptop NetworkManager[937]: adding bridge port none to eni_ifaces Jan 5 08:56:18 simon-laptop NetworkManager[937]: management mode: unmanaged ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: dnsmasq 2.75-1 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 Uname: Linux 4.3.0-5-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 5 09:53:30 2016 PackageArchitecture: all SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1531184/+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 1830746] Re: memlock setting in systemd (pid 1) too low for containers (bionic)
This has landed in Eoan in at least version 242 of systemd. ** Changed in: systemd (Ubuntu Eoan) Status: New => Fix Released ** Tags added: rls-dd-incoming -- 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/1830746 Title: memlock setting in systemd (pid 1) too low for containers (bionic) Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: New Status in systemd source package in Cosmic: New Status in systemd source package in Disco: New Status in systemd source package in Eoan: Fix Released Bug description: See also https://discuss.linuxcontainers.org/t/limits-kernel-memlock- cannot-exceed-16777216/4856/5 In containers, the limits.kernel.memlock cannot exceed 16777216 when the container is bionic. The memlock setting is set to 16M in systemd and cannot be bumped up in an unprivileged container. This is fixed in upstream systemd. Container ubuntu version: Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic systemd package version: 237-3ubuntu10.21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1830746/+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 1779767] Re: Default cron PATH does not include /snap/bin
** Tags added: rls-ee-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1779767 Title: Default cron PATH does not include /snap/bin Status in cron package in Ubuntu: Confirmed Bug description: I recently changed from a .deb install of LXD to a snap, and was surprised that one of my crontab scripts stopped working. I see that $PATH in a cron script only contains "/usr/bin:/bin", whereas my default shell also includes "/snap/bin". It seems to me that for the best user experience with snaps, "/snap/bin" should be part of the default $PATH in cron. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cron 3.0pl1-128.1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_40 kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 livepatch_livepatch_Ubuntu_4_15_0_20_21_generic_ zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jul 2 14:30:06 2018 InstallationDate: Installed on 2017-12-20 (194 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cron UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1779767/+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 645404] Re: Support Private PPAs
** Tags added: rls-ee-notfixing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/645404 Title: Support Private PPAs Status in software-properties package in Ubuntu: In Progress Status in software-properties source package in Bionic: In Progress Status in software-properties source package in Cosmic: In Progress Status in software-properties source package in Disco: In Progress Status in software-properties source package in Eoan: In Progress Bug description: Software properties add-apt-repository currently does not support adding private PPAs. software-properties should connect to the API and observe that it gets permission denied trying to read the ppa. Then it can reconnect to the API asking for authentication, which will open a browser window where you can do the openid ritual. Then using that token it ought to be possible for it to get the password etc. ProblemType: BugDistroRelease: Ubuntu 12.04 Package: python-software-properties 0.82.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/645404/+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 1531184] Re: [SRU] dnsmasq doesn't start on boot because its interface isn't up yet
Adding to my previous message: After=NetworkManager-wait-online.service will not work, as it doesn't respect for instance setups where networkd handles connections. @Robie Basak > Will this delay boot for laptop users who are offline, for example? If someone has installed the dnsmasq package with the dnsmasq.service file, they already intend to run this as a network-dependent service? It's not part of a normal user's setup - I think they have dnsmasq-base, which doesn't include the service. dnsmasq-base: > This package contains the dnsmasq executable and documentation, but not the infrastructure required to run it as a system daemon. For that, install the dnsmasq package. -- 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/1531184 Title: [SRU] dnsmasq doesn't start on boot because its interface isn't up yet Status in One Hundred Papercuts: Confirmed Status in dnsmasq package in Ubuntu: Confirmed Status in dnsmasq package in Debian: New Bug description: [Impact] dnsmasq will fail to respond on network devices that weren't up when its service started, thus not binding as expected. [Test Case] TBD [Regression Potential] The fix is just configuring the order of service startup, so is unlikely to create any regressions. Things to watch would be service related misbehaviors and general availability of the dnsmasq functionality. [Fix] Straightforward packaging fix to the service to make it delay startup until after the network is online. https://bugs.debian.org/cgi- bin/bugreport.cgi?att=1;bug=774970;filename=774970-network- online.debdiff;msg=22 [Discussion] [Original Report] My dnsmasq instance uses "interface=br-vz0" and the interface br-vz0 is managed manually in /etc/network/interfaces. During boot, dnsmasq is started before br-vz0 is created and this causes dnsmasq to exit: Jan 5 08:56:16 simon-laptop dnsmasq[1008]: dnsmasq: unknown interface br-vz0 Jan 5 08:56:16 simon-laptop dnsmasq[1008]: unknown interface br-vz0 Jan 5 08:56:16 simon-laptop dnsmasq[1008]: FAILED to start up Jan 5 08:56:17 simon-laptop NetworkManager[937]: NetworkManager (version 1.0.4) is starting... ... Jan 5 08:56:18 simon-laptop NetworkManager[937]: interface-parser: parsing file /etc/network/interfaces ... Jan 5 08:56:18 simon-laptop NetworkManager[937]: found bridge ports none for br-vz0 Jan 5 08:56:18 simon-laptop NetworkManager[937]: adding bridge port none to eni_ifaces Jan 5 08:56:18 simon-laptop NetworkManager[937]: management mode: unmanaged ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: dnsmasq 2.75-1 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 Uname: Linux 4.3.0-5-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 5 09:53:30 2016 PackageArchitecture: all SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1531184/+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 1845190] Re: binutils nm wrong output format breaks i386 nm work
** Tags added: rls-ee-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1845190 Title: binutils nm wrong output format breaks i386 nm work Status in binutils: New Status in binutils package in Ubuntu: Confirmed Bug description: discovered with diffoscope autopkgregression, looks like a real bug, based on https://salsa.debian.org/reproducible-builds/diffoscope/issues/69 To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1845190/+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 1807440] Re: sensible-browser cannot process $BROWSER variable when it contains a whitespace character
The sensible-utils package which provides the sensible-browser script is in sync with the version of the package in Debian. Would you mind forwarding this bug to Debian? Thanks in advance. ** Tags added: eoan ** Changed in: sensible-utils (Ubuntu) Importance: Undecided => Low ** Changed in: sensible-utils (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sensible-utils in Ubuntu. https://bugs.launchpad.net/bugs/1807440 Title: sensible-browser cannot process $BROWSER variable when it contains a whitespace character Status in sensible-utils package in Ubuntu: Triaged Bug description: If path to a browser defined via the $BROWSER environment variable contains a whitespace character, running sensible-browser should launch browser defined by $BROWSER. If path to a browser defined via the $BROWSER environment variable contains a whitespace character, running sensible-browser will not parse the whitespace characters and therefore not load the browser defined by $BROWSER. Bug can be fixed by updating line 8 in /usr/bin/sensible-browser: ${BROWSER} "$@" > "${BROWSER}" "$@" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: sensible-utils 0.0.12 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Dec 7 11:05:17 2018 Dependencies: InstallationDate: Installed on 2018-12-06 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: sensible-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sensible-utils/+bug/1807440/+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 1779156] Re: lxc 'delete' fails to destroy ZFS filesystem 'dataset is busy'
Been digging into this a bit further with lxc 3.17 on Eoan. lxc launch ubuntu:bionic zfs-bug-test Creating zfs-bug-test Starting zfs-bug-test lxc delete zfs-bug-test --force Error: Failed to destroy ZFS filesystem: Failed to run: zfs destroy -r default/containers/z1: cannot destroy 'default/containers/z1': dataset is busy However, re-running the delete works fine: lxd.lxc delete z1 --force Looking at system calls, it appears that the first failing delete --force command attempts to destroy the zfs file system multiple times and then gives up. In doing so, it umounts the zfs file system. Hence the second time the delete is issued it works fine because zfs is now umounted. So it appears that the ordering in the delete is not as it expected. It seems to do: zfs destroy x 10 (or so and then gives up because of errno 16 -EBUSY) zfs umount It should be doing: zfs umount zfs destroy This matches the observed reference counting. The ref count is only dropped once the umount is complete. Attempts to destroy it before that will cause an -EBUSY. -- 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/1779156 Title: lxc 'delete' fails to destroy ZFS filesystem 'dataset is busy' Status in linux package in Ubuntu: Triaged Status in lxc package in Ubuntu: Confirmed Status in linux source package in Cosmic: Triaged Status in lxc source package in Cosmic: Confirmed Status in linux source package in Disco: New Status in lxc source package in Disco: New Status in linux source package in Eoan: Triaged Status in lxc source package in Eoan: Confirmed Bug description: I'm not sure exactly what got me into this state, but I have several lxc containers that cannot be deleted. $ lxc info api_status: stable api_version: "1.0" auth: trusted public: false auth_methods: - tls environment: addresses: [] architectures: - x86_64 - i686 certificate: | -BEGIN CERTIFICATE- -END CERTIFICATE- certificate_fingerprint: 3af6f8b8233c5d9e898590a9486ded5c0bec045488384f30ea921afce51f75cb driver: lxc driver_version: 3.0.1 kernel: Linux kernel_architecture: x86_64 kernel_version: 4.15.0-23-generic server: lxd server_pid: 15123 server_version: "3.2" storage: zfs storage_version: 0.7.5-1ubuntu15 server_clustered: false server_name: milhouse $ lxc delete --force b1 Error: Failed to destroy ZFS filesystem: cannot destroy 'default/containers/b1': dataset is busy Talking in #lxc-dev, stgraber and sforeshee provided diagnosis: | short version is that something unshared a mount namespace causing | them to get a copy of the mount table at the time that dataset was | mounted, which then prevents zfs from being able to destroy it) The work around provided was | you can unstick this particular issue by doing: | grep default/containers/b1 /proc/*/mountinfo | then for any of the hits, do: | nsenter -t PID -m -- umount /var/snap/lxd/common/lxd/storage-pools/default/containers/b1 | then try the delete again ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: smoser31412 F pulseaudio /dev/snd/controlC2: smoser31412 F pulseaudio /dev/snd/controlC0: smoser31412 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jun 28 10:42:45 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2015-07-23 (1071 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1) MachineType: b'\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff' b'\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff' ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.174 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2015 dmi.bios.vendor: Intel Corporation dmi.bios.version: RYBDWi35.86A.0246.2015.0309.1355 dmi.board.asset.tag: ��
[Touch-packages] [Bug 1842324] Re: Port schemas from gnome-settings-daemon-common to com.canonical.unity.settings-daemon
This bug was fixed in the package unity - 7.5.0+19.10.20190924-0ubuntu1 --- unity (7.5.0+19.10.20190924-0ubuntu1) eoan; urgency=medium [ Khurshid Alam ] * Port media keys to use com.canonical.unity.settings-daemon. LP: #1842324 (LP: #1842324) [ Tasos Sahanidis ] * Fix gcc 7.2 build errors -- Marco Trevisan (Treviño) Tue, 24 Sep 2019 09:46:52 + ** Changed in: unity (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1842324 Title: Port schemas from gnome-settings-daemon-common to com.canonical.unity .settings-daemon Status in indicator-session package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Confirmed Status in unity-greeter package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Fix Released Bug description: Unity-settings-daemon still depends on gnome-settings-daemon schemas. It is undesired as it requires to modify code in all unity related components when upstream drops some gsettings schemas. gnome-settings-daemon > 3.33 drops/modify media-keys schemas in an undesired way that it can't easily be reverted. Keyboard & mouse schemas are modified and unity-settings-daemon is crashing. So it's better unity uses it's own schema as suggested by Laney. We will of- course keep using settings migration (org.gnome.settings-daemon-> org.gnome.desktop) wherever possible. https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/6dff93a0dfa80db3f481eed5d6ed689bf469aa1b https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/44f53c64c5a2514d2c022bcb1596a9e46f1df51c https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/121a6f89917898b8d05db2e1933dd0ad59c26768 Since this is a huge task it can be achieved gradually. 1) Ubuntu 19.10 - Port media keys to use com.canonical.unity.settings-daemon - u-s-d will still use org.gnome.settings-daemon name in dbus - u-s-d will still respects activation toggle in org.gnome.settings- daemon - everything else remains the same 2) Ubuntu 20.04 - Port rest of plugins to use com.canonical.unity.settings-daemon - u-s-d will still use org.gnome.settings-daemon name in dbus - Activation toggle key will now use com.canonical.unity.settings- daemon - Everything else will remain the same To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1842324/+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 1845201] [NEW] systemd root-unittests autopkgtest is failing on armhf
Public bug reported: This is a regression with 242, to be fixed soon. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse -- 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/1845201 Title: systemd root-unittests autopkgtest is failing on armhf Status in systemd package in Ubuntu: New Bug description: This is a regression with 242, to be fixed soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1845201/+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 1843630] Re: ubuntu-bug not opening anything in the browser
Could you please attach the contents of your /etc/apport/crashdb.conf file to this bug report? ** Changed in: apport (Ubuntu) Status: New => Incomplete -- 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/1843630 Title: ubuntu-bug not opening anything in the browser Status in apport package in Ubuntu: Incomplete Bug description: Ubuntu 19.04, "ubuntu-bug apport" pops up the "Send problem report to the developers?" with the "Don't send" and "Send" buttons, but when I click on "Send" nothing happens. I have the "problem_types" line commented out in /etc/apport/crashdb.conf, though I don't know if that's relevant when I'm trying to report a bug, not a crash. I have no idea how to troubleshoot this further. Please advise. The same problem occurs for "ubuntu-bug needrestart". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1843630/+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 1843755] Re: [FFe] Please accept systemd 242 to Eoan
Since the time before Eoan Beta is too short I reverted to ship 242, it is now in -proposed. ** Summary changed: - [FFe] Please accept systemd 243 to Eoan + [FFe] Please accept systemd 242 to Eoan -- 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/1843755 Title: [FFe] Please accept systemd 242 to Eoan Status in systemd package in Ubuntu: Confirmed Bug description: Eoan currently has 241-7ubuntu1, Debian stable has 241 and Debian testing moved to 242 last week. While version 241 is the safer choice for Eoan (from v241 and v242) since it is widely tested updating to v242 will allow us to carry fewer patches in Eoan and makes moving to the next release easier. The proposed package is tested in Bileto and all tests are passing (except for a few unrelated failures): https://bileto.ubuntu.com/#/ticket/3797 The final version will be 242-6ubuntu1 and I'm tidying up the changelog, too. I plan merging 242-7, too, going forward but this will not need an FFe. CHANGES WITH 242: * In .link files, MACAddressPolicy=persistent (the default) is changed to cover more devices. For devices like bridges, tun, tap, bond, and similar interfaces that do not have other identifying information, the interface name is used as the basis for persistent seed for MAC and IPv4LL addresses. The way that devices that were handled previously is not changed, and this change is about covering more devices then previously by the "persistent" policy. MACAddressPolicy=random may be used to force randomized MACs and IPv4LL addresses for a device if desired. Hint: the log output from udev (at debug level) was enhanced to clarify what policy is followed and which attributes are used. `SYSTEMD_LOG_LEVEL=debug udevadm test-builtin net_setup_link /sys/class/net/` may be used to view this. Hint: if a bridge interface is created without any slaves, and gains a slave later, then now the bridge does not inherit slave's MAC. To inherit slave's MAC, for example, create the following file: ``` # /etc/systemd/network/98-bridge-inherit-mac.link [Match] Type=bridge [Link] MACAddressPolicy=none ``` * The .device units generated by systemd-fstab-generator and other generators do not automatically pull in the corresponding .mount unit as a Wants= dependency. This means that simply plugging in the device will not cause the mount unit to be started automatically. But please note that the mount unit may be started for other reasons, in particular if it is part of local-fs.target, and any unit which (transitively) depends on local-fs.target is started. * networkctl list/status/lldp now accept globbing wildcards for network interface names to match against all existing interfaces. * The $PIDFILE environment variable is set to point the absolute path configured with PIDFile= for processes of that service. * The fallback DNS server list was augmented with Cloudflare public DNS servers. Use `-Ddns-servers=` to set a different fallback. * A new special target usb-gadget.target will be started automatically when a USB Device Controller is detected (which means that the system is a USB peripheral). * A new unit setting CPUQuotaPeriodSec= assigns the time period relatively to which the CPU time quota specified by CPUQuota= is measured. * A new unit setting ProtectHostname= may be used to prevent services from modifying hostname information (even if they otherwise would have privileges to do so). * A new unit setting NetworkNamespacePath= may be used to specify a namespace for service or socket units through a path referring to a Linux network namespace pseudo-file. * The PrivateNetwork= setting and JoinsNamespaceOf= dependencies now have an effect on .socket units: when used the listening socket is created within the configured network namespace instead of the host namespace. * ExecStart= command lines in unit files may now be prefixed with ':' in which case environment variable substitution is disabled. (Supported for the other ExecXYZ= settings, too.) * .timer units gained two new boolean settings OnClockChange= and OnTimezoneChange= which may be used to also trigger a unit when the system clock is changed or the local timezone is
[Touch-packages] [Bug 1845190] Re: binutils nm wrong output format breaks i386 nm work
Launchpad has imported 2 comments from the remote bug at https://sourceware.org/bugzilla/show_bug.cgi?id=25031. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2019-09-24T11:10:32+00:00 Gianfranco Costamagna wrote: Created attachment 12001 example This happens since binutils 2.32.51.20190611 (The Debian version mostly tracks svn) and it was working on 2.32-8 (updated to 20190424) to reproduce: nm elfmix1.not_a nm: 42-Mach-O.o: file format not recognized nm: 43-Mach-O.o: file format not recognized nm: Mach-O.o: file format not recognized return42_or_3_long_name.o: T return42_or_3 nm: return42_or_3_long_name.c: file format not recognized nm: regen_elfmix.sh: file format not recognized return42_or_3_long_name.obj: ffa49ce8 T return42_or_3 before, with old binutils it was printed correctly nm elfmix1.not_a nm: 42-Mach-O.o: file format not recognized nm: 43-Mach-O.o: file format not recognized nm: Mach-O.o: file format not recognized return42_or_3_long_name.o: T return42_or_3 nm: return42_or_3_long_name.c: file format not recognized nm: regen_elfmix.sh: file format not recognized return42_or_3_long_name.obj: T return42_or_3 Looks like the returned output is half full of uninitialized values on amd64 it works correctly nm elfmix1.not_a nm: 42-Mach-O.o: file format not recognized nm: 43-Mach-O.o: file format not recognized nm: Mach-O.o: file format not recognized return42_or_3_long_name.o: T return42_or_3 nm: return42_or_3_long_name.c: file format not recognized nm: regen_elfmix.sh: file format not recognized return42_or_3_long_name.obj: T return42_or_3 Reply at: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1845190/comments/0 On 2019-09-24T11:12:39+00:00 Gianfranco Costamagna wrote: Please see this Debian discussion for more information https://salsa.debian.org/reproducible-builds/diffoscope/issues/69 Reply at: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1845190/comments/1 ** Changed in: binutils Status: Unknown => New ** Changed in: binutils Importance: Unknown => Medium ** Bug watch added: salsa.debian.org/reproducible-builds/diffoscope/issues #69 https://salsa.debian.org/reproducible-builds/diffoscope/issues/69 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1845190 Title: binutils nm wrong output format breaks i386 nm work Status in binutils: New Status in binutils package in Ubuntu: Confirmed Bug description: discovered with diffoscope autopkgregression, looks like a real bug, based on https://salsa.debian.org/reproducible-builds/diffoscope/issues/69 To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1845190/+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 1842437] Re: Xenial: libblkid: fix false-positive/misdetection of nilfs2 filesystem with udev
LP: #1844504 ** Tags added: ftbfs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1842437 Title: Xenial: libblkid: fix false-positive/misdetection of nilfs2 filesystem with udev Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Xenial: In Progress Bug description: [Impact] * Users / systemd can fail to mount a filesystem by UUID (e.g., during boot, triggering emergency shell prompt) if the magic bytes for the nilfs filesystem are written to the right place in a partition of another filesystem, (for whatever reason or coincidence). * Note this can happen after the filesystem/mount is working correctly, so a change of behavior/problem can potentially be noticed when trying to mount the filesystem again, which can very well be the next time the system boots. * This happens because if udev blkid detects more than one filesystem, it does not print the UUID env vars required to create the /dev/disk/by-id symlinks and other things. * The fix enhances the check for valid nilfs superblock by specifically checking a value read from disk to be valid/ within a value range, which addresses this one occurrence and prevents a lot more. [Test Case] * Synthetic test case written for this problem on comment #6. [Regression Potential] * Low. The code is contained in the probe for the nilfs filesystem. * This just makes it be more restrictive about the possibly valid values for a few bytes read from disk (that now need to be within the acceptable range of valid values) so this only decreases false- positives, and cannot increase false-negatives of valid filesystems. [Original Description] The nilfs filesystem has a backup superblock at the end of the device. If the magic number is coincidentally found at the right position and the filesystem is on a partition/not-wholedisk device, the only check left is for checksum verification, which is explicitly ignored in 'udev built-in blkid'. This causes blkid to detect one actually valid filesystem with a superblock at the beginning of the device (e.g., ext4), and then an invalid nilfs2 filesystem due to a coincidental magic number at the end of the device. And this causes blkid to break out of the safeprobe routine (which expects a single filesystem to be detected), and not print the UUIDs, thus not creating /dev/disk/by-uuid/ links which prevent mounting the partition by-uuid at boot time, causing emergency shell/boot failures. This upstream fix resolved the problem by introducing a check for the 'bytes' paramenters in the superblock, which is read from disk, and turns out to have an out-of-range value. - 'liblkid: Add length check in probe_nilfs2 before crc32' https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=ac681a310c32319423297544833932f4d689a7a2 $ git describe --contains ac681a310c32319423297544833932f4d689a7a2 v2.29-rc1~172 Xenial, which is v2.27.1-based, is the only release that needs it. Bionic is v2.31.1, so all post-Xenial supported releases have it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1842437/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1842643] Re: [ffe] Update to 1.44.6
On Mon, Sep 23, 2019 at 10:12:14AM -, Sebastien Bacher wrote: > We failed to have consensus in Paris and I feel like it's getting late > now and we have enough other work to do to wrap the cycle so would > prefer to delay to next cycle now. Iain, what do you think? (you opened > the FFe but so you should be the one deciding if we withdraw the > request) Right, yes, I think so. Sorry about this - maybe I was being overly conservative here, not sure. Agreed we probably have enough work to do and don't want to have to deal with any (unknown) fallout from this. For the record, I saw mclasen saying on IRC somewhere (can't find it right now) that some commits from cairo git ara cairo snapshot needed to work properly with this new pango but there is no maintainer to release it - not sure of the details. We should bear this in mind next cycle. status wontfix Cheers, -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] ** Changed in: pango1.0 (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1842643 Title: [ffe] Update to 1.44.6 Status in pango1.0 package in Ubuntu: Won't Fix Bug description: There are a lot of changes in pango1.0 since the version we currently have in eoan. We held off updating because there was a test failure. This has been resolved in the latest release, so we'd like to go for the update now. Overview of changes in 1.44.6 = - docs: Fix symbol indices - Fix Thai line breaking - Re-add symbols needed by some bindings - Don't insert hyphens for some languages - Fix a crash with hyphenation Overview of changes in 1.44.5 = - Revert a broken change (causing crashes on OS X) Overview of changes in 1.44.4 = - Add an insert-hyphens attribute - Reinstate the return type of pango_fc_font_lock_face - Fix a problem with ellipses getting the wrong font - fc: Improve filtering by font format - Re-add PangoFcFont to public headers - Install PangoFc and PangoOT introspection files - Fix ink rectangles to have positive height - Fix mark positioning - Switch to using harfbuzz for metrics Overview of changes in 1.44.3 = - Install pango-ot headers - Make subpixel positioning optional - fc: Ignore fonts with unsupported formats Overview of changes in 1.44.2 = - Disable ligatures when letterspacing - Set design coords on hb_font_t - Expose more font options in pango-view - OS X: Make 'system-ui' font work - Keep deprecated pango-fc apis in headers - Make hex boxes work, always - introspection: Various build fixes - introspection: Add PangoPT, PangoFT2 namespaces - layout: Make the new line-spacing opt-in Overview of changes in 1.44.1 = - Fix a crash with allow_break attributes - Fix Emoji spacing - Fix up includes and pkg-config requires - Correct some cases for hyphen insertion Overview of changes in 1.44.0 = - Use harfbuzz for shaping on all platforms - Stop using freetype for font loading; this drops support for type1 and bitmap fonts - Add a getter for hb_font_t - Make PangoCoverage a GObject - Add a pango_tailor_break api - font metrics: Add line height - layout: Support line spacing - layout: Draw hyphens for line breaks - Add an attribute to suppress line breaking - cairo: Don't render hex boxes for space - Add an attribute to show invisible characters - Stop quantizing glyph positions - Add tests for itemization and line breaking - Remove language and shape engine remnants - Rename meson options: gtk_doc, introspection - Require GLib 2.59.2 - Require Harfbuzz 2.0 Overview of changes in 1.43.0 = - Drop autotools - Drop Visual Studio build - Build with meson everywhere - Update Emoji tables for Unicode 11 - Update test data for Unicode 11 - Fix a crash with Thai breaking - Fix a crash with font variations - Deprecate bidi apis in favor of fribidi - Add a variable font family api - Improve font fallback handling on win32 And see posts from upstream https://blogs.gnome.org/mclasen/2019/07/19/pango-updates/ https://blogs.gnome.org/mclasen/2019/07/27/more-text-rendering-updates/ https://blogs.gnome.org/mclasen/2019/08/07/pango-1-44-wrap-up/ for the new features. We'd like to update to it, if possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1842643/+subscriptions -- Mailing list: https://launchpad.net/~
[Touch-packages] [Bug 1845190] [NEW] binutils nm wrong output format breaks i386 nm work
Public bug reported: discovered with diffoscope autopkgregression, looks like a real bug, based on https://salsa.debian.org/reproducible-builds/diffoscope/issues/69 ** Affects: binutils Importance: Unknown Status: Unknown ** Affects: binutils (Ubuntu) Importance: High Assignee: Matthias Klose (doko) Status: Confirmed ** Bug watch added: Sourceware.org Bugzilla #25031 https://sourceware.org/bugzilla/show_bug.cgi?id=25031 ** Also affects: binutils via https://sourceware.org/bugzilla/show_bug.cgi?id=25031 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1845190 Title: binutils nm wrong output format breaks i386 nm work Status in binutils: Unknown Status in binutils package in Ubuntu: Confirmed Bug description: discovered with diffoscope autopkgregression, looks like a real bug, based on https://salsa.debian.org/reproducible-builds/diffoscope/issues/69 To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1845190/+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 1222602] Re: [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class hardware and 943/945 graphics controllers
** Changed in: mesa Importance: Medium => Unknown ** Changed in: mesa Remote watch: freedesktop.org Bugzilla #64202 => gitlab.freedesktop.org/mesa/mesa/issues #727 -- 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/1222602 Title: [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class hardware and 943/945 graphics controllers Status in Mesa: Unknown Status in Nux: Fix Released Status in Release Notes for Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in nux package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Bug description: After the upgrade to Mesa 9.2.0 unity is barely usable. Dash, Alt+Tab switcher and Alt+F2 command line shows in more than 1 minute, using 100% cpu. A downgrade to mesa 9.1.6-2ubuntu2 restores full performance. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgl1-mesa-glx 9.2-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.12.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Sep 9 01:51:45 2013 DistUpgraded: 2013-09-08 20:36:47,811 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:0110] Subsystem: Micro-Star International Co., Ltd. Device [1462:0110] InstallationDate: Installed on 2013-09-07 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: MICRO-STAR INTERNATIONAL CO., LTD U90/U100 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-5-generic root=UUID=674329c8-d0a6-4954-89c0-72821cfa0ba8 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to saucy on 2013-09-08 (0 days ago) dmi.bios.date: 12/01/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: U90/U100 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.board.version: Ver.001 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.chassis.version: Ver.001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd12/01/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnU90/U100:pvrVer.001:rvnMICRO-STARINTERNATIONALCO.,LTD:rnU90/U100:rvrVer.001:cvnMICRO-STARINTERNATIONALCO.,LTD:ct10:cvrVer.001: dmi.product.name: U90/U100 dmi.product.version: Ver.001 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1 version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Mon Sep 9 01:46:55 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1001 vendor HSD xserver.version: 2:1.14.2.901-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1222602/+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 1844132] Re: FFe: Mesa 19.2.0
** Changed in: libclc (Ubuntu Eoan) Status: New => Fix Released -- 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/1844132 Title: FFe: Mesa 19.2.0 Status in libclc package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Confirmed Status in libclc source package in Eoan: Fix Released Status in mesa source package in Eoan: Confirmed Bug description: It would be great to get 19.2.0 in eoan, though it's release cycle has slipped. It's working fine on a typical desktop use here on i915 (Kaby Lake). It would also migrate to llvm-9. It is currently at rc3, and final version is expected to arrive next week (week 39). New features: Full support for Intel Ice Lake Support for AMD Navi GL_ARB_post_depth_coverage on radeonsi (Navi) GL_ARB_seamless_cubemap_per_texture on etnaviv (if GPU supports SEAMLESS_CUBE_MAP) GL_EXT_shader_image_load_store on radeonsi (with LLVM >= 10) GL_EXT_shader_samples_identical on iris and radeonsi (if using NIR) GL_EXT_texture_shadow_lod on i965, iris EGL_EXT_platform_device VK_AMD_buffer_marker on radv VK_EXT_index_type_uint8 on radv VK_EXT_post_depth_coverage on radv VK_EXT_queue_family_foreign on radv VK_EXT_sample_locations on radv VK_EXT_shader_demote_to_helper_invocation on Intel. VK_KHR_depth_stencil_resolve on radv VK_KHR_imageless_framebuffer on radv VK_KHR_shader_atomic_int64 on radv VK_KHR_uniform_buffer_standard_layout on radv (note: iris is the new DRI driver for newer Intel, not enabled by default yet) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1844132/+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 1742997] Re: Newly installed applications are not showing in "Installed"
This bug was fixed in the package gnome-software - 3.28.1-0ubuntu4.18.04.12 --- gnome-software (3.28.1-0ubuntu4.18.04.12) bionic; urgency=medium * debian/patches/0001-Fix-apps-that-were-previously-uninstalled-from-not-s.patch: - Fix apps that are reinstalled from disappearing from installed page (LP: #1742997) gnome-software (3.28.1-0ubuntu4.18.04.11) bionic; urgency=medium * debian/patches/0031-shell-Don-t-progate-CTRL-F-key-pressed-event.patch: - Fix Ctrl-F not opening search bar (LP: #1735071) * debian/patches/0014-Add-a-basic-permissions-system.patch: - Fix interface connections not showing correct state (LP: #1806697) * debian/patches/0017-snap-Use-default-icon-if-none-provided.patch: - Update default snap icon (LP: #1818920) * debian/patches/0032-snap-Update-Snap-store-category-mapping.patch: - Update snap store categories (LP: #1836826) -- Robert Ancell Tue, 17 Sep 2019 09:49:03 +0200 ** Changed in: gnome-software (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1742997 Title: Newly installed applications are not showing in "Installed" Status in GNOME Software: Expired Status in gnome-software package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Invalid Status in gnome-software source package in Bionic: Fix Released Status in packagekit source package in Bionic: Invalid Bug description: [Impact] Removing and installing an app stops it showing in the installed apps page. [Test Case] 1. Open GNOME Software 2. Go to installed tab 3. Click on an installed app 4. Remove this app 5. Install this app 6. Click back button to return to installation page. Expected result: App shows on page. Observed result: App does not show on page. [Regression Potential] Change is small, and just fixes and ordering issue. Unlikely to trigger other major issues. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1742997/+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 1742997] Update Released
The verification of the Stable Release Update for gnome-software has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1742997 Title: Newly installed applications are not showing in "Installed" Status in GNOME Software: Expired Status in gnome-software package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Invalid Status in gnome-software source package in Bionic: Fix Committed Status in packagekit source package in Bionic: Invalid Bug description: [Impact] Removing and installing an app stops it showing in the installed apps page. [Test Case] 1. Open GNOME Software 2. Go to installed tab 3. Click on an installed app 4. Remove this app 5. Install this app 6. Click back button to return to installation page. Expected result: App shows on page. Observed result: App does not show on page. [Regression Potential] Change is small, and just fixes and ordering issue. Unlikely to trigger other major issues. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1742997/+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 1844132] Re: FFe: Mesa 19.2.0
** Also affects: libclc (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/1844132 Title: FFe: Mesa 19.2.0 Status in libclc package in Ubuntu: New Status in mesa package in Ubuntu: Confirmed Status in libclc source package in Eoan: New Status in mesa source package in Eoan: Confirmed Bug description: It would be great to get 19.2.0 in eoan, though it's release cycle has slipped. It's working fine on a typical desktop use here on i915 (Kaby Lake). It would also migrate to llvm-9. It is currently at rc3, and final version is expected to arrive next week (week 39). New features: Full support for Intel Ice Lake Support for AMD Navi GL_ARB_post_depth_coverage on radeonsi (Navi) GL_ARB_seamless_cubemap_per_texture on etnaviv (if GPU supports SEAMLESS_CUBE_MAP) GL_EXT_shader_image_load_store on radeonsi (with LLVM >= 10) GL_EXT_shader_samples_identical on iris and radeonsi (if using NIR) GL_EXT_texture_shadow_lod on i965, iris EGL_EXT_platform_device VK_AMD_buffer_marker on radv VK_EXT_index_type_uint8 on radv VK_EXT_post_depth_coverage on radv VK_EXT_queue_family_foreign on radv VK_EXT_sample_locations on radv VK_EXT_shader_demote_to_helper_invocation on Intel. VK_KHR_depth_stencil_resolve on radv VK_KHR_imageless_framebuffer on radv VK_KHR_shader_atomic_int64 on radv VK_KHR_uniform_buffer_standard_layout on radv (note: iris is the new DRI driver for newer Intel, not enabled by default yet) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1844132/+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 1837174] Re: auto compress if save filename ends with .gz
** Changed in: oem-priority Importance: High => Medium -- 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/1837174 Title: auto compress if save filename ends with .gz Status in Apport: Confirmed Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: Fix Released Bug description: email plain text file will be likely cause problem. gzip the save file could help lots of back and forth. Proposed to gzip the file if filename ends with ".gz". To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1837174/+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