[Touch-packages] [Bug 1787537] Re: package ubuntu-web-launchers 18.04.6 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-settings (Ubuntu) Status: New => Confirmed -- 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/1787537 Title: package ubuntu-web-launchers 18.04.6 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: I was loading Thunderbird ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ubuntu-web-launchers 18.04.6 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 AptOrdering: linux-modules-4.15.0-30-generic:amd64: Remove NULL: ConfigurePending Architecture: amd64 Date: Fri Aug 17 09:21:08 2018 ErrorMessage: problemi con le dipendenze - lasciato non configurato InstallationDate: Installed on 2018-05-07 (102 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: ubuntu-settings Title: package ubuntu-web-launchers 18.04.6 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1787537/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735784] Re: package uuid-runtime 2.27.1-6ubuntu3.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati
[Expired for dpkg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: dpkg (Ubuntu) Status: Incomplete => Expired -- 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/1735784 Title: package uuid-runtime 2.27.1-6ubuntu3.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in dpkg package in Ubuntu: Expired Status in util-linux package in Ubuntu: Expired Bug description: it always shows a massage that is : "Package operation failed - this installation or removal of a software package failed" ProblemType: Package DistroRelease: Ubuntu 16.04 Package: uuid-runtime 2.27.1-6ubuntu3.3 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 Date: Fri Dec 1 21:14:54 2017 DpkgHistoryLog: Start-Date: 2017-12-01 21:13:48 Commandline: aptdaemon role='role-commit-packages' sender=':1.94' Upgrade: thunderbird-gnome-support:amd64 (1:52.4.0+build1-0ubuntu0.16.04.2, 1:52.5.0+build1-0ubuntu0.16.04.1), dpkg:amd64 (1.18.4ubuntu1.2, 1.18.4ubuntu1.3), thunderbird-locale-en-us:amd64 (1:52.4.0+build1-0ubuntu0.16.04.2, 1:52.5.0+build1-0ubuntu0.16.04.1), firefox-locale-en:amd64 (57.0+build4-0ubuntu0.16.04.6, 57.0.1+build2-0ubuntu0.16.04.1), thunderbird:amd64 (1:52.4.0+build1-0ubuntu0.16.04.2, 1:52.5.0+build1-0ubuntu0.16.04.1), firefox:amd64 (57.0+build4-0ubuntu0.16.04.6, 57.0.1+build2-0ubuntu0.16.04.1), libdpkg-perl:amd64 (1.18.4ubuntu1.2, 1.18.4ubuntu1.3), thunderbird-locale-en:amd64 (1:52.4.0+build1-0ubuntu0.16.04.2, 1:52.5.0+build1-0ubuntu0.16.04.1), dpkg-dev:amd64 (1.18.4ubuntu1.2, 1.18.4ubuntu1.3) DuplicateSignature: package:uuid-runtime:2.27.1-6ubuntu3.3 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... dpkg: error processing package uuid-runtime (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-08-26 (96 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: util-linux Title: package uuid-runtime 2.27.1-6ubuntu3.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1735784/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735784] Re: package uuid-runtime 2.27.1-6ubuntu3.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati
[Expired for util-linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: util-linux (Ubuntu) Status: Incomplete => Expired -- 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/1735784 Title: package uuid-runtime 2.27.1-6ubuntu3.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in dpkg package in Ubuntu: Expired Status in util-linux package in Ubuntu: Expired Bug description: it always shows a massage that is : "Package operation failed - this installation or removal of a software package failed" ProblemType: Package DistroRelease: Ubuntu 16.04 Package: uuid-runtime 2.27.1-6ubuntu3.3 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 Date: Fri Dec 1 21:14:54 2017 DpkgHistoryLog: Start-Date: 2017-12-01 21:13:48 Commandline: aptdaemon role='role-commit-packages' sender=':1.94' Upgrade: thunderbird-gnome-support:amd64 (1:52.4.0+build1-0ubuntu0.16.04.2, 1:52.5.0+build1-0ubuntu0.16.04.1), dpkg:amd64 (1.18.4ubuntu1.2, 1.18.4ubuntu1.3), thunderbird-locale-en-us:amd64 (1:52.4.0+build1-0ubuntu0.16.04.2, 1:52.5.0+build1-0ubuntu0.16.04.1), firefox-locale-en:amd64 (57.0+build4-0ubuntu0.16.04.6, 57.0.1+build2-0ubuntu0.16.04.1), thunderbird:amd64 (1:52.4.0+build1-0ubuntu0.16.04.2, 1:52.5.0+build1-0ubuntu0.16.04.1), firefox:amd64 (57.0+build4-0ubuntu0.16.04.6, 57.0.1+build2-0ubuntu0.16.04.1), libdpkg-perl:amd64 (1.18.4ubuntu1.2, 1.18.4ubuntu1.3), thunderbird-locale-en:amd64 (1:52.4.0+build1-0ubuntu0.16.04.2, 1:52.5.0+build1-0ubuntu0.16.04.1), dpkg-dev:amd64 (1.18.4ubuntu1.2, 1.18.4ubuntu1.3) DuplicateSignature: package:uuid-runtime:2.27.1-6ubuntu3.3 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... dpkg: error processing package uuid-runtime (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-08-26 (96 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: util-linux Title: package uuid-runtime 2.27.1-6ubuntu3.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1735784/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1736381] Re: package apport 2.14.1-0ubuntu3.27 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
[Expired for apport (Ubuntu) because there has been no activity for 60 days.] ** Changed in: apport (Ubuntu) Status: Incomplete => Expired -- 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/1736381 Title: package apport 2.14.1-0ubuntu3.27 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in apport package in Ubuntu: Expired Bug description: Hi, We are working on Ubuntu 14.04LTS. We are trying to "sudo apt-get upgrade". In that, we are getting error similar as below: Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: linux-image-4.4.0-98-generic linux-image-extra-4.4.0-98-generic Use 'apt-get autoremove' to remove them. The following packages have been kept back: libvlc-dev libvlc5 vlc vlc-data vlc-nox vlc-plugin-notify The following packages will be upgraded: curl evince evince-common firefox firefox-locale-en idle-python2.7 libcairo-gobject2 libcairo2 libcurl3 libcurl3-gnutls libdvdnav-dev libdvdnav4 libdvdread-dev libdvdread4 libevdocument3-4 libevview3-3 libpython2.7 libpython2.7-minimal libpython2.7-stdlib libpython3.4 libpython3.4-minimal libpython3.4-stdlib libshine3 libssh-4 libxcursor1 libxfont1 python2.7 python2.7-minimal python3.4 python3.4-minimal resolvconf thunderbird thunderbird-gnome-support 33 upgraded, 0 newly installed, 0 to remove and 6 not upgraded. 19 not fully installed or removed. Need to get 98.7 MB of archives. After this operation, 322 kB disk space will be freed. Do you want to continue? [Y/n] y Get:1 http://ppa.launchpad.net/jonathonf/vlc/ubuntu/ trusty/main libcairo2 amd64 1.14.6-1~14.04.york0 [556 kB] Get:2 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main libpython3.4 amd64 3.4.3-1ubuntu1~14.04.6 [1,305 kB] Get:3 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main python3.4 amd64 3.4.3-1ubuntu1~14.04.6 [178 kB] Get:4 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main libpython3.4-stdlib amd64 3.4.3-1ubuntu1~14.04.6 [1,987 kB] Get:5 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main python3.4-minimal amd64 3.4.3-1ubuntu1~14.04.6 [1,224 kB] Get:6 http://ppa.launchpad.net/jonathonf/vlc/ubuntu/ trusty/main libcairo-gobject2 amd64 1.14.6-1~14.04.york0 [132 kB] Get:7 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main libpython3.4-minimal amd64 3.4.3-1ubuntu1~14.04.6 [460 kB] Get:8 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main resolvconf all 1.69ubuntu1.3 [55.3 kB] Get:9 http://ppa.launchpad.net/jonathonf/vlc/ubuntu/ trusty/main libdvdread-dev amd64 5.0.3-1~14.04.york0 [68.4 kB] Get:10 http://ppa.launchpad.net/jonathonf/vlc/ubuntu/ trusty/main libdvdread4 amd64 5.0.3-1~14.04.york0 [54.8 kB] Get:11 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main libcurl3-gnutls amd64 7.35.0-1ubuntu2.13 [166 kB] Get:12 http://ppa.launchpad.net/jonathonf/vlc/ubuntu/ trusty/main libdvdnav-dev amd64 5.0.3-1~14.04.york0 [54.2 kB] Get:13 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main curl amd64 7.35.0-1ubuntu2.13 [123 kB] Get:14 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main libcurl3 amd64 7.35.0-1ubuntu2.13 [173 kB] Get:15 http://ppa.launchpad.net/jonathonf/vlc/ubuntu/ trusty/main libdvdnav4 amd64 5.0.3-1~14.04.york0 [41.1 kB] Get:16 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main python2.7 amd64 2.7.6-8ubuntu0.4 [196 kB] Get:17 http://ppa.launchpad.net/jonathonf/vlc/ubuntu/ trusty/main libshine3 amd64 3.1.0-4~14.04.york0 [25.3 kB] Get:18 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main libpython2.7 amd64 2.7.6-8ubuntu0.4 [1,040 kB] Get:19 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main libpython2.7-stdlib amd64 2.7.6-8ubuntu0.4 [1,869 kB] Get:20 http://ppa.launchpad.net/jonathonf/vlc/ubuntu/ trusty/main libssh-4 amd64 0.6.3-4.3~14.04.york0 [120 kB] Get:21 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main python2.7-minimal amd64 2.7.6-8ubuntu0.4 [1,188 kB] Get:22 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main libpython2.7-minimal amd64 2.7.6-8ubuntu0.4 [307 kB] Get:23 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main libxcursor1 amd64 1:1.1.14-1ubuntu0.14.04.1 [20.0 kB] Get:24 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main libxfont1 amd64 1:1.4.7-1ubuntu0.4 [95.1 kB] Get:25 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main evince amd64 3.10.3-0ubuntu10.4 [159 kB] Get:26 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main libevdocument3-4 amd64 3.10.3-0ubuntu10.4 [218 kB] Get:27 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main libevview3-3 amd64
[Touch-packages] [Bug 1779438] Re: Cannot resolve names using systemd-resolved stub resolver
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1779438 Title: Cannot resolve names using systemd-resolved stub resolver Status in systemd package in Ubuntu: Expired Bug description: Description: Ubuntu 18.04 LTS Release: 18.04 I am running a clean install of Ubuntu 18.04. This bug was also present for me on a clean install of Ubuntu 17.10 and I had a solution, but it appears to no longer work. What I expect to happen: Ping other hosts on network by name What happened instead: I can't ping other machines on network via name. From my Ubuntu 18.04 machine, I `ping ubuntu-test-1` and `ping ubuntu-test-1.localdomain` but neither work. I can ping by IP address though. The other machines on the network are Ubuntu Server 16.04.3 machines and can ping each other by name also. All machines on network including problem one receive DHCP leases from same server (192.168.20.1) I believe the problem is systemd-resolved stub resolver. `cat /etc/resolv.conf` # This file is managed by man:systemd-resolved(8). Do not edit. # # This is a dynamic resolv.conf file for connecting local clients to the # internal DNS stub resolver of systemd-resolved. This file lists all # configured search domains. # # Run "systemd-resolve --status" to see details about the uplink DNS servers # currently in use. # # Third party programs must not access this file directly, but only through the # symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way, # replace this symlink by a static file or a different symlink. # # See man:systemd-resolved.service(8) for details about the supported modes of # operation for /etc/resolv.conf. nameserver 127.0.0.53 search localdomain If I change the nameserver line to the IP of my nameserver, not the stub, resolution works. nameserver 192.168.20.1 search localdomain Now I can ping hosts by name. I used to solve this problem like this... `sudo systemctl disable systemd-resolved.service` `echo "nameserver 192.168.20.1" | sudo tee -a /etc/resolvconf/resolv.conf.d/tail` `sudo reboot` But /etc/resolvconf/resolv.conf.d no longer exists, and it's about time this problem was fixed :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1779438/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1793060] Re: configure_networking uses features not available in initramfs.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1793060 Title: configure_networking uses features not available in initramfs. Status in initramfs-tools package in Ubuntu: Confirmed Bug description: initramfs-tools 0.131ubuntu10 modified configure_networking to use run_dhclient instead of ipconfig. configure_networking now fails to configure networking in the initramfs because it now uses features not available in the initramfs. https://git.launchpad.net/ubuntu/+source/initramfs- tools/commit/?id=a77729e9a69ff7af4911285c771d80e01b7addfe run_dhclient calls dhclient which calls /sbin/dhclient-script. /sbin/dhclient-script calls 'chown --reference=$resolv_conf $new_resolv_conf', but chown isn't available in initramfs /boot/initrd.img-4.18.0-7-generic. /sbin/dhclient-script also calls 'chmod --reference=$resolv_conf $new_resolv_conf' but busybox chmod in the initramfs does not support the option --reference. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1793060/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792552] Re: Qt doesn't cope with EPERM returned from statx(2)
Unsubscribing ~ubuntu-sponsors for now because upstream has rejected the patch. If this was done in error, please resubscribe us. Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1792552 Title: Qt doesn't cope with EPERM returned from statx(2) Status in qtbase-opensource-src package in Ubuntu: New Bug description: The statx(2) system call is a relatively new addition and has not seen widespread use. As such the seccomp filer used by snapd to confine application processes does not currently permit it. While addressing the bug in snapd is in progress we wanted to contribute a fix to the package so that all snaps built with Qt from the Ubuntu archive will automatically benefit and behave correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1792552/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1793229] [NEW] [VYBE, Realtek ALC892, Green Line Out, Rear] skipping/underruns
Public bug reported: Audio (from many sources) skips/hiccups pretty often (I'd say at least once every 30 seconds.) Iv'e tried all three workarounds here without success: https://wiki.ubuntu.com/Audio/PositionReporting Happy to debug as needed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ahh2147 F pulseaudio /dev/snd/controlC0: ahh2147 F pulseaudio Date: Tue Sep 18 18:41:45 2018 InstallationDate: Installed on 2018-09-08 (10 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Line Out, Rear Symptom_PulseAudioLog: Sep 18 18:40:10 timberwolf dbus-daemon[787]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.34' (uid=121 pid=1133 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Sep 18 18:40:16 timberwolf dbus-daemon[787]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.65' (uid=121 pid=1133 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [VYBE, Realtek ALC892, Green Line Out, Rear] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: DBZ6810H.86A.0014.2011.0413.1049 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DZ68DB dmi.board.vendor: Intel Corporation dmi.board.version: AAG27985-100 dmi.chassis.type: 3 dmi.chassis.vendor: MAINGEAR dmi.modalias: dmi:bvnIntelCorp.:bvrDBZ6810H.86A.0014.2011.0413.1049:bd04/13/2011:svnMAINGEAR:pnVYBE:pvr:rvnIntelCorporation:rnDZ68DB:rvrAAG27985-100:cvnMAINGEAR:ct3:cvr: dmi.product.name: VYBE dmi.sys.vendor: MAINGEAR ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1793229 Title: [VYBE, Realtek ALC892, Green Line Out, Rear] skipping/underruns Status in pulseaudio package in Ubuntu: New Bug description: Audio (from many sources) skips/hiccups pretty often (I'd say at least once every 30 seconds.) Iv'e tried all three workarounds here without success: https://wiki.ubuntu.com/Audio/PositionReporting Happy to debug as needed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ahh2147 F pulseaudio /dev/snd/controlC0: ahh2147 F pulseaudio Date: Tue Sep 18 18:41:45 2018 InstallationDate: Installed on 2018-09-08 (10 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Line Out, Rear Symptom_PulseAudioLog: Sep 18 18:40:10 timberwolf dbus-daemon[787]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.34' (uid=121 pid=1133 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Sep 18 18:40:16 timberwolf dbus-daemon[787]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.65' (uid=121 pid=1133 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [VYBE, Realtek ALC892, Green Line Out, Rear] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version:
[Touch-packages] [Bug 1793186] Re: /usr/bin/mixxx:11:soundtouch::TDStretch::overlapStereo:soundtouch::TDStretch::overlap:soundtouch::TDStretch::processSamples:soundtouch::FIFOSamplePipe::moveSamples:s
*** This bug is a duplicate of bug 1577042 *** https://bugs.launchpad.net/bugs/1577042 ** This bug has been marked a duplicate of bug 1577042 SIGSEGV in SoundTouch 1.9.2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to soundtouch in Ubuntu. https://bugs.launchpad.net/bugs/1793186 Title: /usr/bin/mixxx:11:soundtouch::TDStretch::overlapStereo:soundtouch::TDStretch::overlap:soundtouch::TDStretch::processSamples:soundtouch::FIFOSamplePipe::moveSamples:soundtouch::SoundTouch::putSamples Status in Mixxx: Fix Released Status in mixxx package in Ubuntu: Confirmed Status in soundtouch package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding mixxx. This problem was most recently seen with package version 2.0.0~dfsg-9, the problem page at https://errors.ubuntu.com/problem/b0fe240bbf4fabd30cff44df2813af2822eb29a1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mixxx/+bug/1793186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1793186] Re: /usr/bin/mixxx:11:soundtouch::TDStretch::overlapStereo:soundtouch::TDStretch::overlap:soundtouch::TDStretch::processSamples:soundtouch::FIFOSamplePipe::moveSamples:s
** Changed in: mixxx Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to soundtouch in Ubuntu. https://bugs.launchpad.net/bugs/1793186 Title: /usr/bin/mixxx:11:soundtouch::TDStretch::overlapStereo:soundtouch::TDStretch::overlap:soundtouch::TDStretch::processSamples:soundtouch::FIFOSamplePipe::moveSamples:soundtouch::SoundTouch::putSamples Status in Mixxx: Fix Released Status in mixxx package in Ubuntu: Confirmed Status in soundtouch package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding mixxx. This problem was most recently seen with package version 2.0.0~dfsg-9, the problem page at https://errors.ubuntu.com/problem/b0fe240bbf4fabd30cff44df2813af2822eb29a1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mixxx/+bug/1793186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1793186] Re: /usr/bin/mixxx:11:soundtouch::TDStretch::overlapStereo:soundtouch::TDStretch::overlap:soundtouch::TDStretch::processSamples:soundtouch::FIFOSamplePipe::moveSamples:s
Here is the Upstream bug: https://sourceforge.net/p/soundtouch/bugs/4/ fixed in sounddouch 2.0. ** Also affects: soundtouch (Ubuntu) Importance: Undecided Status: New ** Changed in: mixxx Status: New => Confirmed ** Changed in: mixxx (Ubuntu) Status: New => Confirmed ** Changed in: soundtouch (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to soundtouch in Ubuntu. https://bugs.launchpad.net/bugs/1793186 Title: /usr/bin/mixxx:11:soundtouch::TDStretch::overlapStereo:soundtouch::TDStretch::overlap:soundtouch::TDStretch::processSamples:soundtouch::FIFOSamplePipe::moveSamples:soundtouch::SoundTouch::putSamples Status in Mixxx: Confirmed Status in mixxx package in Ubuntu: Confirmed Status in soundtouch package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding mixxx. This problem was most recently seen with package version 2.0.0~dfsg-9, the problem page at https://errors.ubuntu.com/problem/b0fe240bbf4fabd30cff44df2813af2822eb29a1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mixxx/+bug/1793186/+subscriptions -- Mailing list: https://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 1784887] Re: Python3
Dear Sirs, thanks for your replying. Unfortunately, in the meantime, I had a failure on my motherboard, and the technician installed Fedora 28 on my pc. So I am unable to fullfll your request. By the way, how can I stop or enter "Solved" on my post? I welcome the occasion to confirm that Fedora 28 is working perfectly. Regards and thank you. Giovanni Bravin Italy Il 18/09/18 22:17, Juhani Numminen ha scritto: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. Unfortunately, we cannot work on this bug because your > description didn't include enough information. You may find it helpful > to read "How to report bugs effectively" > http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful > if you would then provide a more complete description of the problem. > > Please include the full output of the commands that you mentioned in the bug > report, including the error messages. > Please attach the files /var/log/dpkg.log and /var/log/apt/history.log. > > Please also attach term.log from your home directory after running this > command from terminal: > sudo cp /var/log/apt/term.log $HOME/ > > Thanks! > > ** Changed in: python3-defaults (Ubuntu) > Status: New => Incomplete > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1784887 Title: Python3 Status in python3-defaults package in Ubuntu: Incomplete Bug description: I am trying to install a smart card reader on USB, and it requires the following commands fro terminal: sudo apt-get update sudo apt-get install libacr38u sudo apt-get install libccid sudo apt-get libpcsclite1 sudo apt-get install pcscd Most of them reported a failure on Python3. I have tried an upgrade of Python3 thru Syynaptic but I received a similar answer. I am a newbie on Linux/Ubuntu so I apologize, but I need help. I use: Ubuntu 18.04.1 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1784887/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1784887] Re: Python3
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. Please include the full output of the commands that you mentioned in the bug report, including the error messages. Please attach the files /var/log/dpkg.log and /var/log/apt/history.log. Please also attach term.log from your home directory after running this command from terminal: sudo cp /var/log/apt/term.log $HOME/ Thanks! ** Changed in: python3-defaults (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1784887 Title: Python3 Status in python3-defaults package in Ubuntu: Incomplete Bug description: I am trying to install a smart card reader on USB, and it requires the following commands fro terminal: sudo apt-get update sudo apt-get install libacr38u sudo apt-get install libccid sudo apt-get libpcsclite1 sudo apt-get install pcscd Most of them reported a failure on Python3. I have tried an upgrade of Python3 thru Syynaptic but I received a similar answer. I am a newbie on Linux/Ubuntu so I apologize, but I need help. I use: Ubuntu 18.04.1 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1784887/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780846] Re: After update 2018-07-08 menus and buttons are behaving badly
(Another workaround for this bug would be to use the proprietary driver for Nvidia instead of nouveau. I am not planning to do this (yet?) ) -- 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/1780846 Title: After update 2018-07-08 menus and buttons are behaving badly Status in mesa package in Ubuntu: Confirmed Bug description: After an update to Description: Ubuntu 16.04.4 LTS Release: 16.04 Menus and buttons are behaving badly. This is a general issue, affecting most programs. Text in buttons is not always being displayed. When you mouse over an entry in a menu list the previous entry disappears e.g. the logout menu (power button icon at top right of panel) Menu items are getting red backgrounds where they were not before. Introduced by update done by update-manager on Last update Start-Date: 2018-07-08 21:25:10 Modified packages: libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-nouveau2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-nouveau2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libapt-inst2.0:amd64 (1.2.26, 1.2.27) libegl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apt:amd64 (1.2.26, 1.2.27) libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) mesa-common-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libapt-pkg5.0:amd64 (1.2.26, 1.2.27) apache2-data:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-amdgpu1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-amdgpu1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) firefox-locale-en:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 61.0+build3-0ubuntu0.16.04.2) libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libgl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apt-utils:amd64 (1.2.26, 1.2.27) libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-intel1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-intel1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) apache2-bin:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) firefox:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 61.0+build3-0ubuntu0.16.04.2) apt-transport-https:amd64 (1.2.26, 1.2.27) libdrm-radeon1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-radeon1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apache2:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) apache2-utils:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) libdrm-dev:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-common:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1780846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1715319] Re: [IPV6] DHCP client gets 128 subnet mask instead of any other that defined
Seems that AdvManagedFlag & AdvOtherConfigFlag on radvd.conf should do
the trick.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1715319
Title:
[IPV6] DHCP client gets 128 subnet mask instead of any other that
defined
Status in isc-dhcp package in Ubuntu:
Confirmed
Bug description:
After configuring DHCP server (with and without RADVD), the client
gets ipv6 address in range that was defined, or preserved. But the
subnetmask of the address is 128 no matter what was the definition.
Steps to reproduce
1.Install packages:
#apt-get install -y *dhcp*
#apt-get install radvd
2.Define DHCP and RADVD files:
#vim /etc/dhcp/dhcpd6.conf
authoritative;
default-lease-time 600;
max-lease-time 7200;
log-facility local7;
subnet6 ::/64 {
option dhcp6.name-servers ::;
range6 ::1 ::100;
}
#vim /etc/radvd.conf
interface enp5s0f0
{
AdvSendAdvert on;
MinRtrAdvInterval 3;
MaxRtrAdvInterval 10;
prefix ::/64 {
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr on;
};
};
3.
# sysctl net.ipv6.conf.ens3.forwarding
net.ipv6.conf.ens3.forwarding = 1
4.Create empty server data base file and bring up DHCP server:
#echo "" > /tmp/dhcp6.lease
# dhcpd -6 -cf /etc/dhcp/dhcpd6.conf -lf /tmp/dhcpd6.leases enp5s0f0
5.Define client interface in /etc/network/interfaces file:
#vim /etc/network/interfaces
auto enp6s0f0
iface enp6s0f0 inet6 dhcp
6.Start client and check the ip:
#ifdown
#ifup
#ifconfig enp6s0f0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1715319/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1784347] Comment bridged from LTC Bugzilla
--- Comment From kyle.mahlk...@ibm.com 2018-09-18 14:39 EDT--- Are there any updates from Canonical on including this patch? -- 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/1784347 Title: ISST-LTE: KVM:UBUNTU1804: BostonLC: fdisk -l shows the conflicting partitions name for the mpath Status in The Ubuntu-power-systems project: Triaged Status in util-linux package in Ubuntu: New Bug description: == Comment: #0 - Chanh H. Nguyen - 2018-01-09 11:14:07 == We have the Ubuntu1804 installed on our BostonLC system. Create a SAN via the Emulex adapter to have the mpath disk. Running the fdisk -l and ls -l showing the conflict name for the mpath. :~# uname -a Linux boslcp4 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux root@boslcp4:~# cat /etc/os-release NAME="Ubuntu" VERSION="18.04 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu Bionic Beaver (development branch)" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic :~# fdisk -l /dev/mapper/mpatha Disk /dev/mapper/mpatha: 600 GiB, 644245094400 bytes, 1258291200 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 32768 bytes / 32768 bytes Disklabel type: dos Disk identifier: 0xa5be904b Device Boot StartEnd Sectors Size Id Type /dev/mapper/mpatha-part1 2048 419432447 419430400 200G 83 Linux /dev/mapper/mpatha-part2 419432448 838862847 419430400 200G 83 Linux /dev/mapper/mpatha-part3 838862848 1258291199 419428352 200G 83 Linux :~# ls -l /dev/mapper/mpatha* lrwxrwxrwx 1 root root 7 Jan 9 04:04 /dev/mapper/mpatha -> ../dm-0 lrwxrwxrwx 1 root root 7 Jan 9 04:03 /dev/mapper/mpatha1 -> ../dm-1 lrwxrwxrwx 1 root root 7 Jan 9 04:03 /dev/mapper/mpatha2 -> ../dm-2 lrwxrwxrwx 1 root root 7 Jan 9 04:03 /dev/mapper/mpatha3 -> ../dm-3 == Comment: #2 - Chanh H. Nguyen - 2018-01-09 11:35:04 == I just modify the partitions and it is still showing the conflicting name on partitions. :~# ls -l /dev/mapper/mpatha* lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha -> ../dm-0 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha1 -> ../dm-1 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha2 -> ../dm-2 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha3 -> ../dm-3 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha4 -> ../dm-4 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha5 -> ../dm-5 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha6 -> ../dm-6 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha7 -> ../dm-7 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha8 -> ../dm-8 :~# fdisk -l /dev/mapper/mpatha Disk /dev/mapper/mpatha: 600 GiB, 644245094400 bytes, 1258291200 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 32768 bytes / 32768 bytes Disklabel type: dos Disk identifier: 0xa5be904b Device Boot StartEnd Sectors Size Id Type /dev/mapper/mpatha-part12048 419432447 419430400 200G 83 Linux /dev/mapper/mpatha-part2 419432448 838862847 419430400 200G 83 Linux /dev/mapper/mpatha-part3 838862848 964691967 125829120 60G 83 Linux /dev/mapper/mpatha-part4 964691968 1258291199 293599232 140G 5 Extended /dev/mapper/mpatha-part5 964694016 1006637055 41943040 20G 83 Linux /dev/mapper/mpatha-part6 1006639104 1048582143 41943040 20G 83 Linux /dev/mapper/mpatha-part7 1048584192 1090527231 41943040 20G 83 Linux /dev/mapper/mpatha-part8 1090529280 1132472319 41943040 20G 83 Linux == Comment: #5 - Kyle Mahlkuch - 2018-06-26 13:50:12 == I have created and submitted a patch that should help with this bug. I will update when/if the patch is accepted. == Comment: #9 - Kyle Mahlkuch - 2018-07-27 09:10:44 == Here is the patch: https://github.com/karelzak/util-linux/commit/73775189767195f1d9f5b6b6f6a54e51f61c4356 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1784347/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1793092] Re: [FFe] openssl 1.1.1
** Tags added: needs-debian-merge upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1793092 Title: [FFe] openssl 1.1.1 Status in openssl package in Ubuntu: New Bug description: Merge openssl 1.1.1 from debian unstable. OpenSSL 1.1.1 is now out, with TLS1.3 support, and is the new upstream LTS release. Preserving existing delta: - Replace duplicate files in the doc directory with symlinks. - debian/libssl1.1.postinst: + Display a system restart required notification on libssl1.1 upgrade on servers. + Use a different priority for libssl1.1/restart-services depending on whether a desktop, or server dist-upgrade is being performed. With further changes to diverge from Debian to: - Revert "Enable system default config to enforce TLS1.2 as a minimum" & "Increase default security level from 1 to 2". - Further decrease security level from 1 to 0, for compatibility with openssl 1.0.2. These mitigate most of the runtime incompatibilities, and ensure client<->server compatibility between 1.1.1, 1.1.0, and 1.0.2 series and thus one can continue to mix & match xenial/bionic/cosmic releases. Proposed package is in https://launchpad.net/~xnox/+archive/ubuntu/openssl with a rebuild of all the reverse dependencies. It demonstrates that openssl compiled as above is more compatible and has less issues than debian config, and has only a small fallout which is being analyzed right now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1793092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2
NGINX has technically said this is won't fix: >From a response to my inquiry: http://mailman.nginx.org/pipermail/nginx- devel/2018-September/011448.html -- Hello! On Tue, Sep 18, 2018 at 08:12:20AM -0400, Thomas Ward wrote: > Downstream in Ubuntu, it has been proposed to demote pcre3 and > use pcre2 instead as it is newer. > https://trac.nginx.org/nginx/ticket/720 shows it was marked 4 > years ago that NGINX does not support pcre2. Are there any > plans to use pcre2 instead of pcre3? There are no immediate plans. When we last checked, there were no problems with PCRE, but PCRE2 wasn't available in most distributions we support, making the switch mostly meaningless. Also, it looks like PCRE2 is still not supported even by Exim, which is the parent project of PCRE and PCRE2: https://bugs.exim.org/show_bug.cgi?id=1878 As such, adding PCRE2 support to nginx looks premature. -- Maxim Dounin http://mdounin.ru/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 Status in aide package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: Fix Released Status in clamav package in Ubuntu: Triaged Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Triaged Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: Triaged Status in libpam-mount package in Ubuntu: Incomplete Status in libselinux package in Ubuntu: Triaged Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php7.2 package in Ubuntu: Triaged Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Incomplete Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in wget package in Ubuntu: Incomplete Status in zsh package in Ubuntu: Incomplete Bug description: demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. aide apache2 apr-util clamav exim4 freeradius git glib2.0 grep haproxy libpam-mount libselinux nginx nmap php7.2 postfix python-pyscss quagga rasqal slang2 sssd wget zsh -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named (according to jbicha). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1786574] Re: remove i2c-i801 from blacklist
I did prepare some slightly modified proposal for this and will try to get things progressing tomorrow. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1786574 Title: remove i2c-i801 from blacklist Status in HWE Next: New Status in OEM Priority Project: New Status in kmod package in Ubuntu: Confirmed Status in kmod source package in Xenial: Confirmed Status in kmod source package in Bionic: Confirmed Status in kmod source package in Cosmic: Confirmed Bug description: We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu. To use the touchpad, users have to remove the i2c-i801 line manually. i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000 (Bug #16602), this module should be removed from blacklist. There is also another bug (Bug #1475945) that needs this module for Acer trackpad to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1786574/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1785311] Re: VLAN in GUI's network setting is under Bluetooth section
I do confirm the issue Ubuntu 18.04 NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1785311 Title: VLAN in GUI's network setting is under Bluetooth section Status in network-manager package in Ubuntu: New Bug description: I install vlan package and setup VLAN successfully. But when I check the Network settings in GUI, the created VLAN interface is under Bluetooth section. For reference, here is the screen shot of the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1785311/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787843] Re: tengo un problema de arranque de equipo, despues de instalar la ultima version de ubuntu
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1787843 Title: tengo un problema de arranque de equipo, despues de instalar la ultima version de ubuntu Status in systemd package in Ubuntu: Confirmed Bug description: Instale la nueva version de Ubuntu, pero al reiniciarse se me quedaba ploqueado, lo intente a traves del BIOS pidiendole que me reparase lo que podia haber mal y en apariencias fue bien (eso fue ayer), hoy lo vuelvo a encender y me vuelve a pasar lo mismo le pido que me identifique el problema y me dice que es un problema al instalar el software y que esta en el paquete : systemd-shim 9-1bzr4ubuntu1 y hasta ahi se, me podrian ayudar? Agracias ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd-sysv 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic i686 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: i386 Date: Fri Aug 17 02:50:45 2018 ErrorMessage: installed systemd-shim package post-removal script subprocess returned error exit status 2 InstallationDate: Installed on 2015-09-11 (1073 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release i386 (20131017) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: systemd Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1787843/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2
This bug was fixed in the package apr-util - 1.6.1-2ubuntu1 --- apr-util (1.6.1-2ubuntu1) cosmic; urgency=medium * Drop build dependency on libpcre3-dev. Closes: #909077. LP: #1792544. -- Matthias Klose Tue, 18 Sep 2018 13:05:27 +0200 ** Changed in: apr-util (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 Status in aide package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: Fix Released Status in clamav package in Ubuntu: Triaged Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Triaged Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: Triaged Status in libpam-mount package in Ubuntu: Incomplete Status in libselinux package in Ubuntu: Triaged Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php7.2 package in Ubuntu: Triaged Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Incomplete Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in wget package in Ubuntu: Incomplete Status in zsh package in Ubuntu: Incomplete Bug description: demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. aide apache2 apr-util clamav exim4 freeradius git glib2.0 grep haproxy libpam-mount libselinux nginx nmap php7.2 postfix python-pyscss quagga rasqal slang2 sssd wget zsh -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named (according to jbicha). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1760818] Re: gedit and gnome-calculator transparency/graphics corruption issue when GTK_IM_MODULE=xim is set
Having the issue over here on 18.04.1 and as mentioned it seems to be focused on what input method system you choose. For me I can't switch over to ibus (without downgrading) without summoning the wrath of bug #1765304. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1760818 Title: gedit and gnome-calculator transparency/graphics corruption issue when GTK_IM_MODULE=xim is set Status in gtk+3.0 package in Ubuntu: Confirmed Status in im-config package in Ubuntu: Confirmed Bug description: In a "Ubuntu" (Xorg) session on 18.04 gedit and gnome-calculator suffer from a graphics issue where parts of their windows hold parts of wallpaper or other windows' contents as background. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20180328-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 3 09:12:31 2018 PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to bionic on 2018-02-07 (54 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1760818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1764946] Re: package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sysvinit (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1764946 Title: package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: sub- processo script post-installation instalado retornou estado de saída de erro 1 Status in sysvinit package in Ubuntu: Confirmed Bug description: Upgrade from 14.04 to 16.04. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: sysv-rc 2.88dsf-59.3ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Tue Apr 17 21:22:39 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 1 InstallationDate: Installed on 2015-10-05 (925 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: sysvinit Title: package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 UpgradeStatus: Upgraded to xenial on 2018-04-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1764946/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776622] Re: snapd on cosmic never finishes installing/updating. Can't install any other updates.
** Tags added: rls-cc-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/1776622 Title: snapd on cosmic never finishes installing/updating. Can't install any other updates. Status in snapd: Confirmed Status in snapd package in Ubuntu: In Progress Status in systemd package in Ubuntu: Confirmed Bug description: snapd (2.33+18.10ubuntu3) cosmic never finishes installing. Can't install any other updates. The first time I gave up waiting and killed it. Then... $ sudo apt full-upgrade E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. $ sudo dpkg --configure -a Setting up snapd (2.33+18.10ubuntu3) ... snapd.snap-repair.service is a disabled or a static unit, not starting it. << never ends >> All the while the snap and snapd process use about 0.3% CPU (which is more than usual). WORKAROUND: sudo killall apt dpkg sudo dpkg -r snapd gnome-software-plugin-snap sudo apt update sudo apt full-upgrade --- ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: snapd 2.33+18.10ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.10-0ubuntu3 Architecture: amd64 Date: Wed Jun 13 16:49:20 2018 InstallationDate: Installed on 2018-05-26 (17 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776622/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2
glib is filed upstream as https://gitlab.gnome.org/GNOME/glib/issues/1085 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 Status in aide package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: New Status in clamav package in Ubuntu: Triaged Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Triaged Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: Triaged Status in libpam-mount package in Ubuntu: Incomplete Status in libselinux package in Ubuntu: Triaged Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php7.2 package in Ubuntu: Triaged Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Incomplete Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in wget package in Ubuntu: Incomplete Status in zsh package in Ubuntu: Incomplete Bug description: demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. aide apache2 apr-util clamav exim4 freeradius git glib2.0 grep haproxy libpam-mount libselinux nginx nmap php7.2 postfix python-pyscss quagga rasqal slang2 sssd wget zsh -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named (according to jbicha). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- Mailing list: https://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 1792544] Re: demotion of pcre3 in favor of pcre2
Nice find, I looked in trac but must have missed that... Sent from my Sprint Samsung Galaxy S9+. Original message From: Anders Kaseorg Date: 9/18/18 06:22 (GMT-05:00) To: tew...@thomas-ward.net Subject: [Bug 1792544] Re: demotion of pcre3 in favor of pcre2 Likewise, nginx does not support PCRE2: https://trac.nginx.org/nginx/ticket/720 ** Bug watch added: trac.nginx.org/nginx/ #720 http://trac.nginx.org/nginx/ticket/720 ** Changed in: nginx (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are subscribed to nginx in Ubuntu. Matching subscriptions: nginx https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 Status in aide package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: New Status in clamav package in Ubuntu: Triaged Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Triaged Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: New Status in libpam-mount package in Ubuntu: Incomplete Status in libselinux package in Ubuntu: New Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php7.2 package in Ubuntu: Triaged Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Incomplete Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in wget package in Ubuntu: Incomplete Status in zsh package in Ubuntu: Incomplete Bug description: demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. aide apache2 apr-util clamav exim4 freeradius git glib2.0 grep haproxy libpam-mount libselinux nginx nmap php7.2 postfix python-pyscss quagga rasqal slang2 sssd wget zsh -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named (according to jbicha). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 Status in aide package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: New Status in clamav package in Ubuntu: Triaged Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Triaged Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: Triaged Status in libpam-mount package in Ubuntu: Incomplete Status in libselinux package in Ubuntu: Triaged Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php7.2 package in Ubuntu: Triaged Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Incomplete Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in wget package in Ubuntu: Incomplete Status in zsh package in Ubuntu: Incomplete Bug description: demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. aide apache2 apr-util clamav exim4 freeradius git glib2.0 grep haproxy libpam-mount libselinux nginx nmap php7.2 postfix python-pyscss quagga rasqal slang2 sssd wget zsh -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named (according to jbicha). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2
** Changed in: libselinux (Ubuntu) Status: New => Triaged ** Changed in: haproxy (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 Status in aide package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: New Status in clamav package in Ubuntu: Triaged Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Triaged Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: Triaged Status in libpam-mount package in Ubuntu: Incomplete Status in libselinux package in Ubuntu: Triaged Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php7.2 package in Ubuntu: Triaged Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Incomplete Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in wget package in Ubuntu: Incomplete Status in zsh package in Ubuntu: Incomplete Bug description: demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. aide apache2 apr-util clamav exim4 freeradius git glib2.0 grep haproxy libpam-mount libselinux nginx nmap php7.2 postfix python-pyscss quagga rasqal slang2 sssd wget zsh -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named (according to jbicha). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1793120] [NEW] Ubuntu 18.04.1 Desktop install fails to show try or install choice
Public bug reported: When I try to install Ubuntu 18.04 (replacing rather than updating 16.04) on my HP Pavilion dv7 6080eo laptop, which currently runs Windows in dual boot with Ubuntu 16.04 LTS for amd64, I never get the screen with the Try Ubuntu or Install Ubuntu choice. Instead the GUI drops into "terminal mode" showing some errors, and after some time I can log into "Try Ubuntu" mode. I have verified the DVD with two methods: Compared the MD5 sum of the ubuntu-18.04.1-desktop-amd64.iso file using md5sum with the value on the web, f430da8fa59d2f5f4262518e3c177246, and checked the DVD using the command: dd if=/dev/sr0 | head -c $(wc -c .../ubuntu-18.04.1-desktop- amd64.iso) | md5sum | cut -d' ' -f1 which also returned f430da8fa59d2f5f4262518e3c177246. Verified the DVD integrity, booting the HP with ubuntu-18.04.1 -desktop-amd64 DVD and used the Check CD for defects menu option, which was successful. The "terminal output" I get before the "installation" on the HP drops into try mode includes (at least) one suspicious line in the beginning (I have attached a picture): [ OK ] Created slice system-lvm2\x2dpvscan.slice Starting LVM2 PV scan on device 8:6... [ OK ] Started Snappy daemon. Starting Wait until snapd is fully seeded.. Starting Holds Snappy daemon refresh... [ FAILED ] Failed to start Dispatcher daemon for systemd-networkd. : : When I boot on an old Asus laptop (K70IO) from that DVD, everything behaves normally. When I boot the HP laptop with a DVD with ubuntu-16.04.1-amd.iso, everything behaves normally. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Attachment added: "2018-08-31 005.jpg" https://bugs.launchpad.net/bugs/1793120/+attachment/5190136/+files/2018-08-31%20005.jpg -- 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/1793120 Title: Ubuntu 18.04.1 Desktop install fails to show try or install choice Status in systemd package in Ubuntu: New Bug description: When I try to install Ubuntu 18.04 (replacing rather than updating 16.04) on my HP Pavilion dv7 6080eo laptop, which currently runs Windows in dual boot with Ubuntu 16.04 LTS for amd64, I never get the screen with the Try Ubuntu or Install Ubuntu choice. Instead the GUI drops into "terminal mode" showing some errors, and after some time I can log into "Try Ubuntu" mode. I have verified the DVD with two methods: Compared the MD5 sum of the ubuntu-18.04.1-desktop-amd64.iso file using md5sum with the value on the web, f430da8fa59d2f5f4262518e3c177246, and checked the DVD using the command: dd if=/dev/sr0 | head -c $(wc -c .../ubuntu-18.04.1-desktop- amd64.iso) | md5sum | cut -d' ' -f1 which also returned f430da8fa59d2f5f4262518e3c177246. Verified the DVD integrity, booting the HP with ubuntu-18.04.1 -desktop-amd64 DVD and used the Check CD for defects menu option, which was successful. The "terminal output" I get before the "installation" on the HP drops into try mode includes (at least) one suspicious line in the beginning (I have attached a picture): [ OK ] Created slice system-lvm2\x2dpvscan.slice Starting LVM2 PV scan on device 8:6... [ OK ] Started Snappy daemon. Starting Wait until snapd is fully seeded.. Starting Holds Snappy daemon refresh... [ FAILED ] Failed to start Dispatcher daemon for systemd-networkd. : : When I boot on an old Asus laptop (K70IO) from that DVD, everything behaves normally. When I boot the HP laptop with a DVD with ubuntu-16.04.1-amd.iso, everything behaves normally. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1793120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1153488] Re: Treats bluetooth input device batteries as batteries
https://www.applemacsupportnumbers.com/apple-customer-support/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1153488 Title: Treats bluetooth input device batteries as batteries Status in gnome-power-manager package in Ubuntu: Invalid Status in upower package in Ubuntu: Fix Released Status in gnome-power-manager source package in Precise: Invalid Status in upower source package in Precise: Fix Released Status in gnome-power-manager source package in Quantal: Invalid Status in upower source package in Quantal: Won't Fix Status in gnome-power-manager source package in Raring: Invalid Status in upower source package in Raring: Fix Released Status in gnome-power-manager source package in Saucy: Invalid Status in upower source package in Saucy: Fix Released Bug description: [Impact] * There are many Bluetooth devices with battery information inside. When they are treated as system battery, it will make the system poweroff/suspend/hibernate when some Bluetooth device has critical low battery. It is a very annoying behavior for the users. Originally, there is no such Bluetooth battery information until Ubuntu 12.04 brings linux-quantal-lts and linux-raring-lts, so those linux kernels also bring this issue. [Test Case] * Pair some Bluetooth devices, such as Apple Wireless Mouse or Apple Wireless Keyboard. * Click the power indicator and you can find Apple Wireless Mouse is listed as system battery, and there is no Apple Wireless Keyboard. If you open gnome-power-statistics, you can find the 'Supply' field of Apple Wireless Mouse is 'Yes' but it should not be. [Regression Potential] * There is no obvious regression as I know. [Other Info] * Most patches are from upstream, modified to fix the conflicts, and made by the same developer (i.e. fourdollars). * We need another patch from https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d0a934b764c67b4bf626f5b7cf725a6e3066afd2 to make Apple Wireless Keyboard showing. [Original Bug Description] This is a weird one... the system is an HP Pavilion 23 All In One and is powered by a large power supply brick. I currently have an Apple Magic Mouse connected via Bluetooth. As soon as the mouse is connected, the Battery indicator shows up and clicking on that shows that the system is reading my mouse as a battery! See the attached screen shot for what I see in the Power status. Looking at hcitool: ubuntu@201206-11396:~$ hcitool dev Devices: hci0 9C:B7:0D:80:71:DB To make matters even more weird, I actually observed the battery indicator go from full to "Critically Low" and the system suspended itself. Keep in mind, again, that this system has NO battery, it's reading my bluetooth mouse as a battery device. I disconnected the magic mouse and the battery indicator went to Empty Red outline and status showed Battery Disconnected. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.5.0-23-generic 3.5.0-23.35~precise1 ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 NonfreeKernelModules: wl fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. AplayDevices: List of PLAYBACK Hardware Devices card 0: Generic [HD-Audio Generic], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Generic [HD-Audio Generic], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1726 F pulseaudio Card0.Amixer.info: Card hw:0 'Generic'/'HD-Audio Generic at 0xfeb4 irq 16' Mixer name : 'Realtek ALC269VC' Components : 'HDA:10ec0269,103c2aee,00100202' Controls : 21 Simple ctrls : 10 Date: Mon Mar 11 03:54:36 2013 HibernationDevice: RESUME=UUID=ccd7a21f-7a71-4fa5-b95d-e2898c3dae24 InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) MachineType: Hewlett-Packard a654 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic root=UUID=e2a5f4ae-dfa2-40be-a6c5-3ddb85dcf68e ro quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-23-generic N/A linux-backports-modules-3.5.0-23-generic N/A linux-firmware1.79.1 SourcePackage: linux StagingDrivers: rts_pstor UpgradeStatus: No upgrade log present (probably fresh install)
[Touch-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2
Likewise, nginx does not support PCRE2: https://trac.nginx.org/nginx/ticket/720 ** Bug watch added: trac.nginx.org/nginx/ #720 http://trac.nginx.org/nginx/ticket/720 ** Changed in: nginx (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 Status in aide package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: New Status in clamav package in Ubuntu: Triaged Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Triaged Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: New Status in libpam-mount package in Ubuntu: Incomplete Status in libselinux package in Ubuntu: New Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php7.2 package in Ubuntu: Triaged Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Incomplete Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in wget package in Ubuntu: Incomplete Status in zsh package in Ubuntu: Incomplete Bug description: demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. aide apache2 apr-util clamav exim4 freeradius git glib2.0 grep haproxy libpam-mount libselinux nginx nmap php7.2 postfix python-pyscss quagga rasqal slang2 sssd wget zsh -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named (according to jbicha). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1791959] Re: [SRU] remove orphaned initrd old-dkms files in /boot
** Merge proposal unlinked: https://code.launchpad.net/~tdaitx/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/355188 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1791959 Title: [SRU] remove orphaned initrd old-dkms files in /boot Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: New Status in initramfs-tools source package in Bionic: New Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing old-dkms initrd files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory and being carried forward with every upgrade. Note: Filling up the /boot partition causes updates and upgrades to fail. [Test Case] As the fix for bug 1515513 is available on Xenial and Bionic it is no longer possible to reproduce this by simply installing and updating kernels - dkms 2.2.0.3-2ubuntu11.3/xenial or 2.3-3ubuntu1/bionic would be required for that. In order to replicate it an old dkms file will be created by hand. This assumes a new Xenial/Bionic schroot. 1) create files to work as a placeholders for old dkms files (there are 4 possible namings for these files) touch /boot/initrd-4.0.0-0-generic.img.old-dkms /boot/initramfs-4.0.0-0-generic.img.old-dkms /boot/initrd.img-4.0.0-0-generic.old-dkms /boot/initrd-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools * xenial: apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 * bionic: apt-get install -y linux-image-4.15.0-32-generic linux-image-4.15.0-33-generic linux-image-4.15.0-34-generic r8168-dkms initramfs-tools=0.130ubuntu3.3 3) install the headers for the old kernels (forces dkms to run) * xenial: apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic * bionic: apt-get install -y linux-headers-4.15.0-32-generic linux-headers-4.15.0-33-generic linux-headers-4.15.0-34-generic 4) verify that there are 7 old-dkms, the 4 manually created ones and one for each installed kernel ls -1 /boot/*.old-dkms 5) install the initramfs-tools from proposed that contains this fix apt-get install -y initramfs-tools 6) verify that the manually created old-dkms files were removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms 7) mark kernel images and headers as automatically installed apt-mark auto linux-image-4*-generic linux-headers-4*-generic 8) autoremove the older kernel apt-get autoremove -y 9) verify that there are now only 2 old-dkms, one for each installed kernel ls -1 /boot/*.old-dkms These steps guarantees that: - orphaned old-dkms are correctly removed from /boot - non-orphaned old-dkms are kept - when kernel is removed the related old-dkms are also deleted [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1791959/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1791959] Re: [SRU] remove orphaned initrd old-dkms files in /boot
SRU as a merge proposal for both this and bug 1667512 available at Bionic: https://code.launchpad.net/~tdaitx/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/355189 Xenial: https://code.launchpad.net/~tdaitx/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/355190 ** No longer affects: dkms (Ubuntu) ** No longer affects: dkms (Ubuntu Xenial) ** No longer affects: dkms (Ubuntu Bionic) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1791959 Title: [SRU] remove orphaned initrd old-dkms files in /boot Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: New Status in initramfs-tools source package in Bionic: New Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing old-dkms initrd files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory and being carried forward with every upgrade. Note: Filling up the /boot partition causes updates and upgrades to fail. [Test Case] As the fix for bug 1515513 is available on Xenial and Bionic it is no longer possible to reproduce this by simply installing and updating kernels - dkms 2.2.0.3-2ubuntu11.3/xenial or 2.3-3ubuntu1/bionic would be required for that. In order to replicate it an old dkms file will be created by hand. This assumes a new Xenial/Bionic schroot. 1) create files to work as a placeholders for old dkms files (there are 4 possible namings for these files) touch /boot/initrd-4.0.0-0-generic.img.old-dkms /boot/initramfs-4.0.0-0-generic.img.old-dkms /boot/initrd.img-4.0.0-0-generic.old-dkms /boot/initrd-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools * xenial: apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 * bionic: apt-get install -y linux-image-4.15.0-32-generic linux-image-4.15.0-33-generic linux-image-4.15.0-34-generic r8168-dkms initramfs-tools=0.130ubuntu3.3 3) install the headers for the old kernels (forces dkms to run) * xenial: apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic * bionic: apt-get install -y linux-headers-4.15.0-32-generic linux-headers-4.15.0-33-generic linux-headers-4.15.0-34-generic 4) verify that there are 7 old-dkms, the 4 manually created ones and one for each installed kernel ls -1 /boot/*.old-dkms 5) install the initramfs-tools from proposed that contains this fix apt-get install -y initramfs-tools 6) verify that the manually created old-dkms files were removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms 7) mark kernel images and headers as automatically installed apt-mark auto linux-image-4*-generic linux-headers-4*-generic 8) autoremove the older kernel apt-get autoremove -y 9) verify that there are now only 2 old-dkms, one for each installed kernel ls -1 /boot/*.old-dkms These steps guarantees that: - orphaned old-dkms are correctly removed from /boot - non-orphaned old-dkms are kept - when kernel is removed the related old-dkms are also deleted [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1791959/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1667512] Re: [SRU] update-initramfs should sync only the filesystem containing the initramfs image
SRU as a merge proposal for both this and bug 1791959 available at Bionic: https://code.launchpad.net/~tdaitx/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/355189 Xenial: https://code.launchpad.net/~tdaitx/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/355190 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1667512 Title: [SRU] update-initramfs should sync only the filesystem containing the initramfs image Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools package in Debian: Fix Released Bug description: [Impact] If there is lots of activity on a different filesystem, high io/cache pressure, or a stale mount updating initramfs might hang because the update-initramfs script calls sync. This leaves the system unresponsive and will require the user to forcefully kill dpkg. [Test Case] One easy way to simulate this is by copying a huge file over nfs. Note: do not use localhost, it is too fast for this purpose, a network bridge over qemu is good enough. 1. Setup a nfs server and export a directory with write permissions for the client 2. Copy a big file over NFS (assumes it is mounted at /mnt in the client) $ dd if=/dev/zero of=/mnt/big_zeros bs=512 count=1M status=progress Note: adjust the "count" accordingly to how fast/slow your system is. 3. Call sync and verify that it only finished after "dd" is done. 4. Repeat step #2 and now call "sync -f /boot/". Verify that it finished immediatly. [Regression Potential] Although syncfs(2) man page [2] states that it works just the same as sync - except being limited to a filesystem -, any actual differences in the implementation can affect how the initrd image file is synced to the disk, leading to unexpected behavior. [Other] If syncfs is unsupported then the 'sync' binary will ensure that a normal system-wide sync is called [1]. The proposed patch won't help in scenarios where the initrd file is located in a busy filesystem (eg. no separated /boot partition). The 'sync' and 'syncfs' specifications are pretty much similar and syncfs is expected to work the same as a normal sync regarding data integrity. Also altought the patch introduces the initrd file as an extra argument which would cause 'sync -f' to fail if the file does not exist, the update-initramfs script would fail earlier than that because that file is created by the 'mv' call a few lines above. Thus no regressions are expected. [References] [1] http://git.savannah.gnu.org/cgit/coreutils.git/commit/src/sync.c?id=8b2bf5295f353016d4f5e6a2317d55b6a8e7fd00 [2] http://manpages.ubuntu.com/manpages/xenial/man2/syncfs.2.html [Original bug report] At least four users, including myself, are having an issue with update-initramfs hanging while updating ubuntu 16.04. The bug has been documented while attempting an update to multiple kernel versions ( 4.4.0-24, 4.4.0-62, 4.4.0-63). The bug causes any apt-get update or install to fail, and may also lead to an unbootable system. User #1 (me): $ uname -a Linux 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ sudo apt-get upgrade Fetched 1,571 MB in 2min 9s (12.2 MB/s) Extracting templates from packages: 100% Preconfiguring packages ... (Reading database ... 344634 files and directories currently installed.) Preparing to unpack .../base-files_9.4ubuntu4.4_amd64.deb ... Unpacking base-files (9.4ubuntu4.4) over (9.4ubuntu4.3) ... Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.1) ... update-initramfs: deferring update (trigger activated) Processing triggers for man-db (2.7.5-1) ... Processing triggers for cracklib-runtime (2.9.2-1build2) ... Processing triggers for install-info (6.1.0.dfsg.1-5) ... Processing triggers for initramfs-tools (0.122ubuntu8.8) ... update-initramfs: Generating /boot/initrd.img-4.4.0-63-generic Uh oh! Let's try to troubleshoot. $ sudo killall dpkg $ sudo dpkg --configure -a Setting up initramfs-tools (0.122ubuntu8.8) ... update-initramfs: deferring update (trigger activated) Setting up base-files (9.4ubuntu4.4) ... Installing new version of config file /etc/issue ... Installing new version of config file /etc/issue.net ... Installing new version of config file /etc/lsb-release ... Setting up linux-image-4.4.0-63-generic (4.4.0-63.84) ... Running depmod. update-initramfs: deferring update (hook will be called later) initrd.img(/boot/initrd.img-4.4.0-63-generic ) points to /boot/initrd.img-4.4.0-63-generic (/boot/initrd.img-4.4.0-63-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 491. vmlinuz(/boot/vmlinuz-4.4.0-63-generic ) points to /boot/vmlinuz-4.4.0-63-generic
[Touch-packages] [Bug 1791959] Re: [SRU] remove orphaned initrd old-dkms files in /boot
** Merge proposal linked: https://code.launchpad.net/~tdaitx/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/355188 ** Merge proposal linked: https://code.launchpad.net/~tdaitx/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/355189 ** Merge proposal linked: https://code.launchpad.net/~tdaitx/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/355190 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1791959 Title: [SRU] remove orphaned initrd old-dkms files in /boot Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: New Status in initramfs-tools source package in Bionic: New Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing old-dkms initrd files using the kernel's prerm hook, but that is only executed for the kernel version being removed: any other old-dkms file generated prior to that would not be removed by the hook, taking space in the /boot directory and being carried forward with every upgrade. Note: Filling up the /boot partition causes updates and upgrades to fail. [Test Case] As the fix for bug 1515513 is available on Xenial and Bionic it is no longer possible to reproduce this by simply installing and updating kernels - dkms 2.2.0.3-2ubuntu11.3/xenial or 2.3-3ubuntu1/bionic would be required for that. In order to replicate it an old dkms file will be created by hand. This assumes a new Xenial/Bionic schroot. 1) create files to work as a placeholders for old dkms files (there are 4 possible namings for these files) touch /boot/initrd-4.0.0-0-generic.img.old-dkms /boot/initramfs-4.0.0-0-generic.img.old-dkms /boot/initrd.img-4.0.0-0-generic.old-dkms /boot/initrd-4.0.0-0-generic.old-dkms 2) install 3 old kernels, r8168-dkms, and the current initramfs-tools * xenial: apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12 * bionic: apt-get install -y linux-image-4.15.0-32-generic linux-image-4.15.0-33-generic linux-image-4.15.0-34-generic r8168-dkms initramfs-tools=0.130ubuntu3.3 3) install the headers for the old kernels (forces dkms to run) * xenial: apt-get install -y linux-headers-4.4.0-21-generic linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic * bionic: apt-get install -y linux-headers-4.15.0-32-generic linux-headers-4.15.0-33-generic linux-headers-4.15.0-34-generic 4) verify that there are 7 old-dkms, the 4 manually created ones and one for each installed kernel ls -1 /boot/*.old-dkms 5) install the initramfs-tools from proposed that contains this fix apt-get install -y initramfs-tools 6) verify that the manually created old-dkms files were removed and that there are only 3 files now, one for each installed kernel ls /boot/*.old-dkms 7) mark kernel images and headers as automatically installed apt-mark auto linux-image-4*-generic linux-headers-4*-generic 8) autoremove the older kernel apt-get autoremove -y 9) verify that there are now only 2 old-dkms, one for each installed kernel ls -1 /boot/*.old-dkms These steps guarantees that: - orphaned old-dkms are correctly removed from /boot - non-orphaned old-dkms are kept - when kernel is removed the related old-dkms are also deleted [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1791959/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792358] Re: Update to 2.0.0 (next cycle or ffe)
The package was updated (but without ffe?), https://launchpad.net/ubuntu/+source/libjpeg-turbo/2.0.0-0ubuntu1 ** Changed in: libjpeg-turbo (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1792358 Title: Update to 2.0.0 (next cycle or ffe) Status in libjpeg-turbo package in Ubuntu: Fix Released Bug description: The new version would be nice to get but it's not in Debian yet and it has quite some non trivial changes, it would require a ffe if we wanted to update this cycle. Tagging as blocked by ff for now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1792358/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2
Hi, Andreas Hasenack wrote: > I've seen the wget debian change, but just switching builddeps from pcre3-dev > to pcre2-dev and rebuilding isn't enough. The package ends up not finding > pcre and doesn't enable it: > checking for PCRE... no > checking pcre.h usability... no > checking pcre.h presence... no > checking for pcre.h... no > ... > Libs: -luuid -lidn2 -lnettle -lgnutls -lz -lpsl > > So while the package builds, it's not using pcre. > > I tried to switch apache, and while I could make it find pcre2-config and use > it, pcre2 has different libraries than pcre3: > pcre3-config --libs: -lpcre > pcre2-config --libs: no such parameter > > In pcre2, we have --libs8, --libs-posix, --libs32 and --libs16, but no > --libs. Is this a bug in pcre2-config? Indeed, same for zsh: checking for pcre-config... no checking pcre.h usability... no checking pcre.h presence... no checking for pcre.h... no checking for pcre_compile... no checking for pcre_study... no checking for pcre_exec... no [...] ../../Test/V07pcre.ztst: starting. ../../Test/V07pcre.ztst: skipped (the zsh/pcre module is not available) → Back to Incomplete. I'll revert that commit from the recent 5.6.2-2 upload. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE ** Changed in: zsh (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 Status in aide package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: New Status in clamav package in Ubuntu: Triaged Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Triaged Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: New Status in libpam-mount package in Ubuntu: Incomplete Status in libselinux package in Ubuntu: New Status in nginx package in Ubuntu: Triaged Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php7.2 package in Ubuntu: Triaged Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Incomplete Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in wget package in Ubuntu: Incomplete Status in zsh package in Ubuntu: Incomplete Bug description: demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. aide apache2 apr-util clamav exim4 freeradius git glib2.0 grep haproxy libpam-mount libselinux nginx nmap php7.2 postfix python-pyscss quagga rasqal slang2 sssd wget zsh -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named (according to jbicha). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2
sssd: https://pagure.io/SSSD/sssd/issue/3833 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 Status in aide package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: New Status in clamav package in Ubuntu: Triaged Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Triaged Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: New Status in libpam-mount package in Ubuntu: Incomplete Status in libselinux package in Ubuntu: New Status in nginx package in Ubuntu: Triaged Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php7.2 package in Ubuntu: Triaged Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Incomplete Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in wget package in Ubuntu: Incomplete Status in zsh package in Ubuntu: Triaged Bug description: demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. aide apache2 apr-util clamav exim4 freeradius git glib2.0 grep haproxy libpam-mount libselinux nginx nmap php7.2 postfix python-pyscss quagga rasqal slang2 sssd wget zsh -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named (according to jbicha). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2
Note to those filing upstream bugs: probably don’t call the old library “pcre3” since that’s not a thing outside Debian/Ubuntu. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 Status in aide package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: New Status in clamav package in Ubuntu: Triaged Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Triaged Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: New Status in libpam-mount package in Ubuntu: Incomplete Status in libselinux package in Ubuntu: New Status in nginx package in Ubuntu: Triaged Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php7.2 package in Ubuntu: Triaged Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Incomplete Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in wget package in Ubuntu: Incomplete Status in zsh package in Ubuntu: Triaged Bug description: demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. aide apache2 apr-util clamav exim4 freeradius git glib2.0 grep haproxy libpam-mount libselinux nginx nmap php7.2 postfix python-pyscss quagga rasqal slang2 sssd wget zsh -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named (according to jbicha). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2
I think that completes the analysis of the current state of things. Although it seems infeasible to demote PCRE at this time, there’s no reason that should block the promotion of PCRE2, especially seeing as a bundled copy of PCRE2 is already in main (18.04 and 18.10) via libqt5core5a. ** Changed in: sssd (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 Status in aide package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: New Status in clamav package in Ubuntu: Triaged Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Triaged Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: New Status in libpam-mount package in Ubuntu: Incomplete Status in libselinux package in Ubuntu: New Status in nginx package in Ubuntu: Triaged Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php7.2 package in Ubuntu: Triaged Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Incomplete Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in wget package in Ubuntu: Incomplete Status in zsh package in Ubuntu: Triaged Bug description: demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. aide apache2 apr-util clamav exim4 freeradius git glib2.0 grep haproxy libpam-mount libselinux nginx nmap php7.2 postfix python-pyscss quagga rasqal slang2 sssd wget zsh -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named (according to jbicha). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2
Actually, sssd build would still pull libpcre3-dev because of some dependency, and then use that... and upstream config phase doesn't support pcre2. I've filed a bug upstream. ** Changed in: sssd (Ubuntu) Status: Triaged => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 Status in aide package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: New Status in clamav package in Ubuntu: Triaged Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Triaged Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: New Status in libpam-mount package in Ubuntu: Incomplete Status in libselinux package in Ubuntu: New Status in nginx package in Ubuntu: Triaged Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php7.2 package in Ubuntu: Triaged Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Incomplete Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in wget package in Ubuntu: Incomplete Status in zsh package in Ubuntu: Triaged Bug description: demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. aide apache2 apr-util clamav exim4 freeradius git glib2.0 grep haproxy libpam-mount libselinux nginx nmap php7.2 postfix python-pyscss quagga rasqal slang2 sssd wget zsh -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named (according to jbicha). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2
reported upstream: https://savannah.gnu.org/bugs/index.php?54677 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 Status in aide package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: New Status in clamav package in Ubuntu: Triaged Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Triaged Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: New Status in libpam-mount package in Ubuntu: Incomplete Status in libselinux package in Ubuntu: New Status in nginx package in Ubuntu: Triaged Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php7.2 package in Ubuntu: Triaged Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Incomplete Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Confirmed Status in wget package in Ubuntu: Incomplete Status in zsh package in Ubuntu: Triaged Bug description: demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. aide apache2 apr-util clamav exim4 freeradius git glib2.0 grep haproxy libpam-mount libselinux nginx nmap php7.2 postfix python-pyscss quagga rasqal slang2 sssd wget zsh -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named (according to jbicha). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2
• Quagga: no PCRE2 support • Rasqal: no PCRE2 support • S-Lang: no PCRE2 support ** Changed in: quagga (Ubuntu) Status: New => Incomplete ** Changed in: rasqal (Ubuntu) Status: New => Incomplete ** Changed in: slang2 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 Status in aide package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: New Status in clamav package in Ubuntu: Triaged Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Triaged Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: New Status in libpam-mount package in Ubuntu: Incomplete Status in libselinux package in Ubuntu: New Status in nginx package in Ubuntu: Triaged Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php7.2 package in Ubuntu: Triaged Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Incomplete Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Confirmed Status in wget package in Ubuntu: Incomplete Status in zsh package in Ubuntu: Triaged Bug description: demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. aide apache2 apr-util clamav exim4 freeradius git glib2.0 grep haproxy libpam-mount libselinux nginx nmap php7.2 postfix python-pyscss quagga rasqal slang2 sssd wget zsh -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named (according to jbicha). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2
• pam_mount: no PCRE2 support • nmap: no PCRE2 support • postfix: no PCRE2 support, http://postfix.1071664.n5.nabble.com/Plans-for-using-PCRE-v2-in-Postfix-td83200.html • pyScss: no PCRE2 support ** Changed in: libpam-mount (Ubuntu) Status: New => Incomplete ** Changed in: nmap (Ubuntu) Status: New => Incomplete ** Changed in: postfix (Ubuntu) Status: New => Incomplete ** Changed in: python-pyscss (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 Status in aide package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: New Status in clamav package in Ubuntu: Triaged Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Triaged Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: New Status in libpam-mount package in Ubuntu: Incomplete Status in libselinux package in Ubuntu: New Status in nginx package in Ubuntu: Triaged Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php7.2 package in Ubuntu: Triaged Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Incomplete Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Confirmed Status in wget package in Ubuntu: Incomplete Status in zsh package in Ubuntu: Triaged Bug description: demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. aide apache2 apr-util clamav exim4 freeradius git glib2.0 grep haproxy libpam-mount libselinux nginx nmap php7.2 postfix python-pyscss quagga rasqal slang2 sssd wget zsh -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named (according to jbicha). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1793092] [NEW] [FFe] openssl 1.1.1
Public bug reported: Merge openssl 1.1.1 from debian unstable. OpenSSL 1.1.1 is now out, with TLS1.3 support, and is the new upstream LTS release. Preserving existing delta: - Replace duplicate files in the doc directory with symlinks. - debian/libssl1.1.postinst: + Display a system restart required notification on libssl1.1 upgrade on servers. + Use a different priority for libssl1.1/restart-services depending on whether a desktop, or server dist-upgrade is being performed. With further changes to diverge from Debian to: - Revert "Enable system default config to enforce TLS1.2 as a minimum" & "Increase default security level from 1 to 2". - Further decrease security level from 1 to 0, for compatibility with openssl 1.0.2. These mitigate most of the runtime incompatibilities, and ensure client<->server compatibility between 1.1.1, 1.1.0, and 1.0.2 series and thus one can continue to mix & match xenial/bionic/cosmic releases. Proposed package is in https://launchpad.net/~xnox/+archive/ubuntu/openssl with a rebuild of all the reverse dependencies. It demonstrates that openssl compiled as above is more compatible and has less issues than debian config, and has only a small fallout which is being analyzed right now. ** Affects: openssl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1793092 Title: [FFe] openssl 1.1.1 Status in openssl package in Ubuntu: New Bug description: Merge openssl 1.1.1 from debian unstable. OpenSSL 1.1.1 is now out, with TLS1.3 support, and is the new upstream LTS release. Preserving existing delta: - Replace duplicate files in the doc directory with symlinks. - debian/libssl1.1.postinst: + Display a system restart required notification on libssl1.1 upgrade on servers. + Use a different priority for libssl1.1/restart-services depending on whether a desktop, or server dist-upgrade is being performed. With further changes to diverge from Debian to: - Revert "Enable system default config to enforce TLS1.2 as a minimum" & "Increase default security level from 1 to 2". - Further decrease security level from 1 to 0, for compatibility with openssl 1.0.2. These mitigate most of the runtime incompatibilities, and ensure client<->server compatibility between 1.1.1, 1.1.0, and 1.0.2 series and thus one can continue to mix & match xenial/bionic/cosmic releases. Proposed package is in https://launchpad.net/~xnox/+archive/ubuntu/openssl with a rebuild of all the reverse dependencies. It demonstrates that openssl compiled as above is more compatible and has less issues than debian config, and has only a small fallout which is being analyzed right now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1793092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792930] Re: split does not break on error when reading from standard input
Ok, now I use the bash option set -o pipefail and let split fail with the error code of tar. ** Changed in: coreutils (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1792930 Title: split does not break on error when reading from standard input Status in coreutils package in Ubuntu: Invalid Bug description: Hi all, I found a bug in "split". I want to tar some files but some of them have wrong permissions. tar puts out an exit code 2 "Cannot open: Permission denied". That is good because in my script I can catch this error and react to this. $ tar -c -f /tmp/test.tar -C /media/testpath testfile ; echo $? tar: testfile: Cannot open: Permission denied tar: Exiting with failure status due to previous errors 2 Unfortunately my tar directory is too big to save it in one file on my filesystem that I have to split the archive. But doing this "split" does not get the error code 2 from standard input (tar) and does not break as it should: $ tar -c -f - -C /media/testpath testfile | split - ; echo $? tar: testfile: Cannot open: Permission denied tar: Exiting with failure status due to previous errors 0 In the end I got a tar file without files that have no permissions and my script does not break because of error code 0. Ubuntu 18.04.1 tar 1.29b coreutils 8.28 Best regards, Alexander To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1792930/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2
• Aide: no PCRE2 support • Exim: no PCRE2 support, upstream bug: https://bugs.exim.org/show_bug.cgi?id=1878 • FreeRADIUS: no PCRE2 support, mentioned in passing: https://github.com/FreeRADIUS/freeradius-server/issues/1865 • GLib: no PCRE2 support • grep: no PCRE2 support ** Bug watch added: bugs.exim.org/ #1878 http://bugs.exim.org/show_bug.cgi?id=1878 ** Bug watch added: github.com/FreeRADIUS/freeradius-server/issues #1865 https://github.com/FreeRADIUS/freeradius-server/issues/1865 ** Changed in: aide (Ubuntu) Status: New => Incomplete ** Changed in: exim4 (Ubuntu) Status: New => Incomplete ** Changed in: freeradius (Ubuntu) Status: New => Incomplete ** Changed in: glib2.0 (Ubuntu) Status: New => Incomplete ** Changed in: grep (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 Status in aide package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: New Status in clamav package in Ubuntu: Triaged Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Triaged Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: New Status in libpam-mount package in Ubuntu: Incomplete Status in libselinux package in Ubuntu: New Status in nginx package in Ubuntu: Triaged Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php7.2 package in Ubuntu: Triaged Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: New Status in rasqal package in Ubuntu: New Status in slang2 package in Ubuntu: New Status in sssd package in Ubuntu: Triaged Status in wget package in Ubuntu: Incomplete Status in zsh package in Ubuntu: Triaged Bug description: demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. aide apache2 apr-util clamav exim4 freeradius git glib2.0 grep haproxy libpam-mount libselinux nginx nmap php7.2 postfix python-pyscss quagga rasqal slang2 sssd wget zsh -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named (according to jbicha). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2
apr-util: filed a Debian bug. ** Changed in: wget (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 Status in aide package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: New Status in clamav package in Ubuntu: Triaged Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Triaged Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: New Status in libpam-mount package in Ubuntu: New Status in libselinux package in Ubuntu: New Status in nginx package in Ubuntu: Triaged Status in nmap package in Ubuntu: New Status in pcre3 package in Ubuntu: Confirmed Status in php7.2 package in Ubuntu: Triaged Status in postfix package in Ubuntu: New Status in python-pyscss package in Ubuntu: New Status in quagga package in Ubuntu: New Status in rasqal package in Ubuntu: New Status in slang2 package in Ubuntu: New Status in sssd package in Ubuntu: Triaged Status in wget package in Ubuntu: Incomplete Status in zsh package in Ubuntu: Triaged Bug description: demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. aide apache2 apr-util clamav exim4 freeradius git glib2.0 grep haproxy libpam-mount libselinux nginx nmap php7.2 postfix python-pyscss quagga rasqal slang2 sssd wget zsh -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named (according to jbicha). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2
Copying from https://bugs.launchpad.net/ubuntu/+source/pcre2/+bug/163/comments/20, HAProxy and SELinux upstream support PCRE2. https://git.haproxy.org/?p=haproxy.git;a=commitdiff;h=f2592b29f13907ddf2bba42d00bc41cb8ee5b69b https://github.com/SELinuxProject/selinux/commit/50f0910cf05bdc1d10710c7c3fb748a178473387 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 Status in aide package in Ubuntu: New Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: New Status in clamav package in Ubuntu: Triaged Status in exim4 package in Ubuntu: New Status in freeradius package in Ubuntu: New Status in git package in Ubuntu: Triaged Status in glib2.0 package in Ubuntu: New Status in grep package in Ubuntu: New Status in haproxy package in Ubuntu: New Status in libpam-mount package in Ubuntu: New Status in libselinux package in Ubuntu: New Status in nginx package in Ubuntu: Triaged Status in nmap package in Ubuntu: New Status in pcre3 package in Ubuntu: Confirmed Status in php7.2 package in Ubuntu: Triaged Status in postfix package in Ubuntu: New Status in python-pyscss package in Ubuntu: New Status in quagga package in Ubuntu: New Status in rasqal package in Ubuntu: New Status in slang2 package in Ubuntu: New Status in sssd package in Ubuntu: Triaged Status in wget package in Ubuntu: Incomplete Status in zsh package in Ubuntu: Triaged Bug description: demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. aide apache2 apr-util clamav exim4 freeradius git glib2.0 grep haproxy libpam-mount libselinux nginx nmap php7.2 postfix python-pyscss quagga rasqal slang2 sssd wget zsh -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named (according to jbicha). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2
Andreas: No, it’s not a bug. PCRE2 is a new project that’s not intended to be compatible with the older PCRE (i.e. what Debian misnamed “pcre3”). The API is completely different and this is expected. See bug 163 for context, and specifically the PCRE2 release announcement linked in the bug description: https://lists.exim.org/lurker/message/20150105.162835.0666407a.en.html That’s why getting rid of PCRE “in favor of” PCRE2 is a pointless way to frame the issue. PCRE2 neither replaces nor conflicts with PCRE, as was pointed out many times in bug 163. But since we’re apparently gathering information here: although Apache 2.4.x does not support PCRE2, Apache trunk does support PCRE2 as of r1773454. (As you can see, this support was added by creating separate conditionally compiled code paths for PCRE and PCRE2.) https://github.com/apache/httpd/commit/b1a3338e011a17ad190fb7f66cf5ca9acf353570 ** Bug watch added: Debian Bug tracker #757140 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757140 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 Status in aide package in Ubuntu: New Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: New Status in clamav package in Ubuntu: Triaged Status in exim4 package in Ubuntu: New Status in freeradius package in Ubuntu: New Status in git package in Ubuntu: Triaged Status in glib2.0 package in Ubuntu: New Status in grep package in Ubuntu: New Status in haproxy package in Ubuntu: New Status in libpam-mount package in Ubuntu: New Status in libselinux package in Ubuntu: New Status in nginx package in Ubuntu: Triaged Status in nmap package in Ubuntu: New Status in pcre3 package in Ubuntu: Confirmed Status in php7.2 package in Ubuntu: Triaged Status in postfix package in Ubuntu: New Status in python-pyscss package in Ubuntu: New Status in quagga package in Ubuntu: New Status in rasqal package in Ubuntu: New Status in slang2 package in Ubuntu: New Status in sssd package in Ubuntu: Triaged Status in wget package in Ubuntu: Triaged Status in zsh package in Ubuntu: Triaged Bug description: demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. aide apache2 apr-util clamav exim4 freeradius git glib2.0 grep haproxy libpam-mount libselinux nginx nmap php7.2 postfix python-pyscss quagga rasqal slang2 sssd wget zsh -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named (according to jbicha). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2
apr-util has a false Build-Depends on libpcre3-dev; it should simply be dropped. A corresponding Depends was already dropped in https://bugs.debian.org/757140. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 Status in aide package in Ubuntu: New Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: New Status in clamav package in Ubuntu: Triaged Status in exim4 package in Ubuntu: New Status in freeradius package in Ubuntu: New Status in git package in Ubuntu: Triaged Status in glib2.0 package in Ubuntu: New Status in grep package in Ubuntu: New Status in haproxy package in Ubuntu: New Status in libpam-mount package in Ubuntu: New Status in libselinux package in Ubuntu: New Status in nginx package in Ubuntu: Triaged Status in nmap package in Ubuntu: New Status in pcre3 package in Ubuntu: Confirmed Status in php7.2 package in Ubuntu: Triaged Status in postfix package in Ubuntu: New Status in python-pyscss package in Ubuntu: New Status in quagga package in Ubuntu: New Status in rasqal package in Ubuntu: New Status in slang2 package in Ubuntu: New Status in sssd package in Ubuntu: Triaged Status in wget package in Ubuntu: Triaged Status in zsh package in Ubuntu: Triaged Bug description: demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. aide apache2 apr-util clamav exim4 freeradius git glib2.0 grep haproxy libpam-mount libselinux nginx nmap php7.2 postfix python-pyscss quagga rasqal slang2 sssd wget zsh -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named (according to jbicha). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2
I've seen the wget debian change, but just switching builddeps from pcre3-dev to pcre2-dev and rebuilding isn't enough. The package ends up not finding pcre and doesn't enable it: checking for PCRE... no checking pcre.h usability... no checking pcre.h presence... no checking for pcre.h... no ... Libs: -luuid -lidn2 -lnettle -lgnutls -lz -lpsl So while the package builds, it's not using pcre. I tried to switch apache, and while I could make it find pcre2-config and use it, pcre2 has different libraries than pcre3: pcre3-config --libs: -lpcre pcre2-config --libs: no such parameter In pcre2, we have --libs8, --libs-posix, --libs32 and --libs16, but no --libs. Is this a bug in pcre2-config? Any quick tips about this before I dig in further? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 Status in aide package in Ubuntu: New Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: New Status in clamav package in Ubuntu: Triaged Status in exim4 package in Ubuntu: New Status in freeradius package in Ubuntu: New Status in git package in Ubuntu: Triaged Status in glib2.0 package in Ubuntu: New Status in grep package in Ubuntu: New Status in haproxy package in Ubuntu: New Status in libpam-mount package in Ubuntu: New Status in libselinux package in Ubuntu: New Status in nginx package in Ubuntu: Triaged Status in nmap package in Ubuntu: New Status in pcre3 package in Ubuntu: Confirmed Status in php7.2 package in Ubuntu: Triaged Status in postfix package in Ubuntu: New Status in python-pyscss package in Ubuntu: New Status in quagga package in Ubuntu: New Status in rasqal package in Ubuntu: New Status in slang2 package in Ubuntu: New Status in sssd package in Ubuntu: Triaged Status in wget package in Ubuntu: Triaged Status in zsh package in Ubuntu: Triaged Bug description: demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. aide apache2 apr-util clamav exim4 freeradius git glib2.0 grep haproxy libpam-mount libselinux nginx nmap php7.2 postfix python-pyscss quagga rasqal slang2 sssd wget zsh -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named (according to jbicha). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792984] Re: graphic lag
Can you please explain what is not very smooth? What were you doing at the time? And can you provide a video (like from a phone) of the problem? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1792984 Title: graphic lag Status in Ubuntu: Incomplete Bug description: the graphic not very smooth ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Tue Sep 18 00:38:19 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:0767] Subsystem: Dell Radeon R7 M445 [1028:0767] InstallationDate: Installed on 2018-09-16 (0 days ago) InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725.1) MachineType: Dell Inc. Inspiron 5567 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.4 dmi.board.name: 02YHJP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.4:bd04/02/2018:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn02YHJP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5567 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1792984/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1760106] Re: FFe: Enable configuring resume offset via sysfs
** Changed in: oem-priority Status: Triaged => 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/1760106 Title: FFe: Enable configuring resume offset via sysfs Status in OEM Priority Project: Fix Released Status in klibc package in Ubuntu: New Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in klibc source package in Bionic: New Status in linux source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in klibc source package in Cosmic: New Status in linux source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * Cannot hibernate & resume from a swapfile [Test Case] * Create or enlarge swapfile to be big enough for hibernation * Attempt to hibernate and resume [Regression Potential] * Hibernation is not reliable technology in itself, and multiple things may cause failure to resume. Thus it is sufficient to validate this bug after swapfile is attempted for hibernation and the disk offset kernel parameter is modified. Irrespective if actual suspending or resume were successful or not. [Other Info] * Original bug report In 4.17 a new attribute is introduced to configure the hibernation resume offset. Since Ubuntu enables a swapfile by default this attribute is important to be able to make hibernation work "out of the box". The patch in the kernel is here: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next=355064675f1c997cea017ea64c8f2c216e5425d9 Systemd support for adopting this change is available here: https://github.com/systemd/systemd/pull/8406 As of 3/30/18 it's not yet been merged however. Klibc support for adopting this change is available here: https://www.zytor.com/pipermail/klibc/2018-March/003986.html To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1760106/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1793060] Re: configure_networking uses features not available in initramfs.
Thanks for the report. I'm a bit confused though, because although you're right that the call to chown will probably fail, I can't see how that failure will result in networking not being configured. Can you post the console log of networking failing to be configured? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1793060 Title: configure_networking uses features not available in initramfs. Status in initramfs-tools package in Ubuntu: New Bug description: initramfs-tools 0.131ubuntu10 modified configure_networking to use run_dhclient instead of ipconfig. configure_networking now fails to configure networking in the initramfs because it now uses features not available in the initramfs. https://git.launchpad.net/ubuntu/+source/initramfs- tools/commit/?id=a77729e9a69ff7af4911285c771d80e01b7addfe run_dhclient calls dhclient which calls /sbin/dhclient-script. /sbin/dhclient-script calls 'chown --reference=$resolv_conf $new_resolv_conf', but chown isn't available in initramfs /boot/initrd.img-4.18.0-7-generic. /sbin/dhclient-script also calls 'chmod --reference=$resolv_conf $new_resolv_conf' but busybox chmod in the initramfs does not support the option --reference. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1793060/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
