[Touch-packages] [Bug 1738676] Re: With natural scrolling, horizontal sliders behave backwards
** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Triaged -- 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/1738676 Title: With natural scrolling, horizontal sliders behave backwards Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: When natural-scrolling is enabled, controlling horizontal sliders is backwards and counter intuitive. The volume control in the top-bar "speaker" icon is backwards. You have to... - scroll DOWN, to INCREASE the volume - scroll UP, to DECREASE the volume Expected behavior: Enable natural-scrolling and - scroll UP, to INCREASE the volume - scroll DOWN, to DECREASE the volume - scroll UP, to INCREASE the screen brightness - scroll DOWN, to DECREASE the screen brightness Enable natural-scrolling, hover over a horizontal slider, and... - scroll UP, to move the slider to the RIGHT - scroll DOWN, to move the slider to the LEFT This happens for the OSD volume icon, and for the volume slider in the topbar menu. This also happens for screen brightness controls. This problem occurs for both mouse natural-scrolling and touchpad natural scrolling. Expected fix: When the pointer hovers over the speaker icon in the scroll actions on the speaker icon in the top bar should be reversed. When the user interacts with a horizontal slider, scrolling to the top should always move the slider to the right, and scrolling down should always move the slider to the left, even if natural-scrolling is enabled. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Dec 17 19:23:30 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' b"['r']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 'chrome-eppojlglocelodeimnohnlnionkobfln-Default.desktop', 'spotify.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop', 'org.gnome.gedit.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'org.gnome.Software.desktop', 'gnome-system-monitor.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-12-10 (7 days ago) InstallationMedia: Ubuntu 17.10.0 2017.12.10 amd64 "Custom Artful Aardvark" ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1738676/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824285] Re: Xorg crashed after login
*** This bug is a duplicate of bug 1792932 *** https://bugs.launchpad.net/bugs/1792932 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1792932, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1792932 Desktop fails to boot in vbox: Xorg assert failure: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. -- 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/1824285 Title: Xorg crashed after login Status in nvidia-graphics-drivers-418 package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: After login I see crash report. Description: Ubuntu 18.04.2 LTS Release: 18.04 xorg: Installed: 1:7.7+19ubuntu7.1 Candidate: 1:7.7+19ubuntu7.1 Version table: *** 1:7.7+19ubuntu7.1 500 500 http://kg.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.7+19ubuntu7 500 500 http://kg.archive.ubuntu.com/ubuntu bionic/main amd64 Packages nvidia-driver-418: Installed: (none) Candidate: 418.56-0ubuntu0~gpu18.04.1 Version table: 418.56-0ubuntu0~gpu18.04.1 500 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main amd64 Packages https://errors.ubuntu.com/oops/546067c2-5c1b-11e9-a404-fa163e102db1 /usr/lib/xorg/Xorg:Xorg: ../../dix/privates.c:385: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1824285/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818814] Re: systemd-tmpfiles-setup.services fails to create /var/run directories
For Dimitri: > In addition to debug output from systemd-tmpfiles-setup.service > as above, it is also interesting to know the permiissions > on / itself, ie. what's the output of: > $ ls -la / kalle@vspk:~$ ls -la / total 1272 drwxr-xr-x 24 root root4096 Apr 11 15:18 . drwxr-xr-x 24 root root4096 Apr 11 15:18 .. drwx-- 2 root root4096 Nov 27 2016 .cpt_hardlink_dir_a920e4ddc233afddc9fb53d26c392319 -rw-r--r-- 1 root root 0 Apr 11 15:20 .vzfifo drwxr-xr-x 2 root root4096 Apr 11 15:17 bin drwxr-xr-x 2 root root4096 May 14 2018 boot -rw--- 1 root root 1671168 Apr 11 15:19 core drwxr-xr-x 5 root root 640 Apr 11 15:19 dev drwxr-xr-x 154 root root 12288 Apr 11 15:18 etc drwxr-xr-x 5 root root4096 Apr 10 15:46 home drwxr-xr-x 16 root root4096 Jun 9 2018 lib drwxr-xr-x 2 root root4096 Mar 4 08:56 lib64 drwx-- 2 root root4096 Nov 27 2016 lost+found drwxr-xr-x 2 root root4096 Nov 27 2016 media drwxr-xr-x 2 root root4096 Nov 27 2016 mnt drwxr-xr-x 2 root root4096 Nov 27 2016 opt dr-xr-xr-x 139 root root 0 Apr 11 15:18 proc drwx-- 9 root root4096 Apr 11 08:29 root drwxr-xr-x 32 root root 980 Apr 12 08:25 run drwxr-xr-x 2 root root 12288 Apr 11 15:17 sbin drwxr-xr-x 2 root root4096 May 14 2018 snap drwxr-xr-x 2 root root4096 Nov 27 2016 srv drwxr-xr-x 7 root root 0 Apr 11 15:18 sys drwxrwxrwt 9 root root4096 Apr 12 08:25 tmp drwxr-xr-x 10 root root4096 Nov 27 2016 usr drwxr-xr-x 13 root root4096 Dec 17 13:37 var -- 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/1818814 Title: systemd-tmpfiles-setup.services fails to create /var/run directories Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: In Progress Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description:Ubuntu 16.04.6 LTS Release:16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center systemd: Installed: 229-4ubuntu21.16 Candidate: 229-4ubuntu21.16 Version table: *** 229-4ubuntu21.16 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3) What you expected to happen 4) What happened instead Ubuntu server (running in OpenVZ VPS farm, thus the old kernel version) has been up and running happily, until I performed apt-get upgrade and rebooted the server. After reboot, I could not establish SSH connection to server, port 22 connection was refused. I opened a HTML console to my server instance and checked logs. From the logs, it was shown, that SSH server could not start, as it did not have the /var/run/sshd directory. After scrolling back the /var/log/syslog, I noticed that there were lots of other /var/run subdirectories, which were not created. Here is cut from /var/log/syslog, related to systemd-tmpfiles: ---8<---8<--- Mar 6 12:32:54 vspk systemd-tmpfiles[81]: [/usr/lib/tmpfiles.d/00rsyslog.conf:6] Duplicate line for path "/v ar/log", ignoring. Mar 6 12:32:54 vspk systemd[1]: Starting Raise network interfaces... Mar 6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/named failed: Invalid argument Mar 6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path /var/run/fail2ban: Too many levels of symb olic links Mar 6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path
[Touch-packages] [Bug 1824285] Re: Xorg crashed after login
** Package changed: nvidia-graphics-drivers-319 (Ubuntu) => nvidia- graphics-drivers-418 (Ubuntu) ** Also affects: xorg (Ubuntu) Importance: Undecided Status: New -- 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/1824285 Title: Xorg crashed after login Status in nvidia-graphics-drivers-418 package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: After login I see crash report. Description: Ubuntu 18.04.2 LTS Release: 18.04 xorg: Installed: 1:7.7+19ubuntu7.1 Candidate: 1:7.7+19ubuntu7.1 Version table: *** 1:7.7+19ubuntu7.1 500 500 http://kg.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.7+19ubuntu7 500 500 http://kg.archive.ubuntu.com/ubuntu bionic/main amd64 Packages nvidia-driver-418: Installed: (none) Candidate: 418.56-0ubuntu0~gpu18.04.1 Version table: 418.56-0ubuntu0~gpu18.04.1 500 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main amd64 Packages https://errors.ubuntu.com/oops/546067c2-5c1b-11e9-a404-fa163e102db1 /usr/lib/xorg/Xorg:Xorg: ../../dix/privates.c:385: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1824285/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824415] Re: Vertical line screen flickers randomly appears on built-in laptop display only
Sorry, but this looks to me like a broken (or just poorly connected) LCD panel in the laptop. Not a software problem. I've had similar problems myself before, and the fix each time was to either replace the LCD panel, or to just reconnect its wires (sometimes the problem is just a bad connection). As a first point of call you should return the laptop to where you bought it, or contact HP Support about a warranty claim. ** Summary changed: - Screen flickers randomly appears on built-in laptop display only + Vertical line screen flickers randomly appears on built-in laptop display only ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid -- 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/1824415 Title: Vertical line screen flickers randomly appears on built-in laptop display only Status in Ubuntu: Invalid Bug description: The issue is similar to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785912 the short video with the problem https://photos.app.goo.gl/i5dHrQUDV1T2gp8o9 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 11 22:42:06 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83b2] InstallationDate: Installed on 2018-12-03 (129 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: HP HP EliteBook 840 G5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=4b3ca7ee-f7ef-4f10-ae37-d86fdeb64942 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/12/2018 dmi.bios.vendor: HP dmi.bios.version: Q78 Ver. 01.04.00 dmi.board.name: 83B2 dmi.board.vendor: HP dmi.board.version: KBC Version 04.53.00 dmi.chassis.asset.tag: F51020 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ78Ver.01.04.00:bd09/12/2018:svnHP:pnHPEliteBook840G5:pvr:rvnHP:rn83B2:rvrKBCVersion04.53.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 G5 dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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/1824415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824402] Re: [HDA-Intel - HD-Audio Generic, recording] No sound at all
*** This bug is a duplicate of bug 1820314 *** https://bugs.launchpad.net/bugs/1820314 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1820314, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1820314 [ASRock FM2A75M-DGS] No sound at all -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1824402 Title: [HDA-Intel - HD-Audio Generic, recording] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: with latest alsa daily situation did not get better ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hp 1692 F pulseaudio /dev/snd/controlC0: hp 1692 F pulseaudio CurrentDesktop: XFCE Date: Thu Apr 11 19:59:35 2019 InstallationDate: Installed on 2016-09-07 (945 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hp 1692 F pulseaudio /dev/snd/controlC0: hp 1692 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HD-Audio Generic, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.70 dmi.board.name: FM2A75M-DGS dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-04-08T16:46:31.160212 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1824402/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824405] Re: [HDA-Intel - HD-Audio Generic, playback] Playback problem
*** This bug is a duplicate of bug 1820314 *** https://bugs.launchpad.net/bugs/1820314 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1820314, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1820314 [ASRock FM2A75M-DGS] No sound at all -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1824405 Title: [HDA-Intel - HD-Audio Generic, playback] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: with latest alsa daily situation did not get better ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hp 1692 F pulseaudio /dev/snd/controlC0: hp 1692 F pulseaudio CurrentDesktop: XFCE Date: Thu Apr 11 20:05:47 2019 InstallationDate: Installed on 2016-09-07 (945 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia Symptom_Type: Only some of outputs are working Title: [HDA-Intel - HD-Audio Generic, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.70 dmi.board.name: FM2A75M-DGS dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-04-08T16:46:31.160212 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1824405/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738676] Re: With natural scrolling, horizontal sliders behave backwards
** Changed in: gnome-shell Status: Unknown => New -- 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/1738676 Title: With natural scrolling, horizontal sliders behave backwards Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: When natural-scrolling is enabled, controlling horizontal sliders is backwards and counter intuitive. The volume control in the top-bar "speaker" icon is backwards. You have to... - scroll DOWN, to INCREASE the volume - scroll UP, to DECREASE the volume Expected behavior: Enable natural-scrolling and - scroll UP, to INCREASE the volume - scroll DOWN, to DECREASE the volume - scroll UP, to INCREASE the screen brightness - scroll DOWN, to DECREASE the screen brightness Enable natural-scrolling, hover over a horizontal slider, and... - scroll UP, to move the slider to the RIGHT - scroll DOWN, to move the slider to the LEFT This happens for the OSD volume icon, and for the volume slider in the topbar menu. This also happens for screen brightness controls. This problem occurs for both mouse natural-scrolling and touchpad natural scrolling. Expected fix: When the pointer hovers over the speaker icon in the scroll actions on the speaker icon in the top bar should be reversed. When the user interacts with a horizontal slider, scrolling to the top should always move the slider to the right, and scrolling down should always move the slider to the left, even if natural-scrolling is enabled. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Dec 17 19:23:30 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' b"['r']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 'chrome-eppojlglocelodeimnohnlnionkobfln-Default.desktop', 'spotify.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop', 'org.gnome.gedit.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'org.gnome.Software.desktop', 'gnome-system-monitor.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-12-10 (7 days ago) InstallationMedia: Ubuntu 17.10.0 2017.12.10 amd64 "Custom Artful Aardvark" ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1738676/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801338] Re: apt fails to properly handle server-side connection closure
This can be reproduced by hosting a mirror on S3. S3 has built in functionality that closes a connection after 100 requests. We were able to add comments to apt source that output every time a new connection was made and we confirmed every 100 requests that S3 did close the connection. Intermittently, we would get the Undetermined Error during one of the connection close events. Debug output confirmed there is a connection: close header. We also confirmed apt identified a 102 connection reset by peer event by printing the error. So this isn't apache specific, I believe apache is just more prone to sending connection: close. Because of S3's behavior of closing connections every 100 requests, it became very noticeable to us. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1801338 Title: apt fails to properly handle server-side connection closure Status in apt package in Ubuntu: Triaged Status in apt source package in Xenial: New Status in apt source package in Bionic: Triaged Status in apt source package in Cosmic: Triaged Bug description: [Impact] In some cases, apt does not correctly handle server-side connection closure after a pipeline, and aborts the file being downloaded with an "Undetermined Error" when the connection has been closed. [Test case] This could be seen by running apt build-dep evince on cosmic with a recent apt with the pipelining fix (such as 1.6.6) against a local mirror running apache from trusty. It remains to be seen whether this is easily reproducible for anyone. [Regression potential] N/A yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1801338/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815987] Re: Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS
Bump. Still up to date on all patches, still have this issue. kris@mythserver2018:/$ uname -a Linux mythserver2018 4.15.0-47-generic #50-Ubuntu SMP Wed Mar 13 10:44:52 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux kris@mythserver2018:/$ sudo mount sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,nosuid,relatime,size=8109040k,nr_inodes=2027260,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=1627864k,mode=755) /dev/sda1 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids) cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=19533) mqueue on /dev/mqueue type mqueue (rw,relatime) debugfs on /sys/kernel/debug type debugfs (rw,relatime) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M) configfs on /sys/kernel/config type configfs (rw,relatime) fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime) tracefs on /sys/kernel/debug/tracing type tracefs (rw,relatime) /dev/sdc1 on /mnt/backup_storage type xfs (rw,relatime,attr2,inode64,noquota) /dev/sdb1 on /mnt/storage type xfs (rw,relatime,attr2,inode64,noquota) /dev/sda6 on /home type ext4 (rw,relatime,data=ordered) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime) vmware-vmblock on /run/vmblock-fuse type fuse.vmware-vmblock (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other) tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=1627860k,mode=700,uid=1000,gid=1000) kris@mythserver2018:/$ ls -l total 112 drwxr-xr-x 2 root root 4096 Apr 7 16:16 bin drwxr-xr-x 3 root root 4096 Apr 8 06:06 boot drwxrwxr-x 2 root root 4096 Jul 8 2018 cdrom drwxr-xr-x 21 root root 4500 Apr 11 07:35 dev drwxr-xr-x 157 root root 12288 Apr 11 18:50 etc drwxr-xr-x 5 root root 4096 Feb 1 21:37 home lrwxrwxrwx 1 root root33 Apr 7 16:19 initrd.img -> boot/initrd.img-4.15.0-47-generic lrwxrwxrwx 1 root root33 Apr 7 16:19 initrd.img.old -> boot/initrd.img-4.15.0-46-generic drwxr-xr-x 21 root root 4096 Sep 6 2018 lib drwxr-xr-x 2 root root 4096 Jul 29 2018 lib32 drwxr-xr-x 2 root root 4096 Apr 26 2018 lib64 drwx-- 2 root root 16384 Jul 8 2018 lost+found drwxr-xr-x 3 root root 4096 Jul 8 2018 media drwxr-xr-x 4 root root 4096 Jul 11 2018 mnt drwxr-xr-x 5 root root 4096 Mar 5 19:57 opt dr-xr-xr-x 291 root root 0 Apr 7 16:26 proc drwx-- 6 root root 4096 Nov 23 17:51 root drwxr-xr-x 34 root root 1040 Apr 11 18:47 run drwxr-xr-x 2 root root 12288 Apr 7 16:16 sbin drwxr-xr-x 2 root root 4096 Jul 8 2018 snap drwxr-xr-x 2 root root 4096 Apr 26 2018 srv dr-xr-xr-x 13 root root 0 Apr 11 18:48 sys drwxrwxrwt 7 root root 12288 Apr 11 18:51 tmp drwxr-xr-x 12 root root 4096 Jun 11 2010 usr drwxr-xr-x 15 root root 4096 May 23 2010 var lrwxrwxrwx 1 root root30 Apr 7 16:19 vmlinuz -> boot/vmlinuz-4.15.0-47-generic lrwxrwxrwx 1 root root30 Apr 7 16:19 vmlinuz.old -> boot/vmlinuz-4.15.0-46-generic -- 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/1815987 Title: Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS
[Touch-packages] [Bug 1824433] [NEW] dhcpd ignores $CONFIG_FILE in /etc/default/isc-dhcp-server
Public bug reported:
Package isc-dhcp-server 4.3.3 on Ubuntu 16.04 LTS.
On earlier (pre-systemd) systems, one could point dhcpd at a
configuration file in any location by setting
CONFIG_FILE=/new/path/dhcpd.conf in /etc/default/isc-dhcp-server. In
this version such setting is ignored; dhcpd always uses the default
/etc/dhcp/dhcpd.conf.
In more formulaeic terms:
Put CONFIG_FILE=/var/dhcpconf/mydhcp.conf in /etc/default/isc-dhcp-server.
I expect that when service isc-dhcp-server is next started, it will use that
configuration file.
In fact it still uses /etc/dhcp/dhcpd.conf.
The problem can be worked around by making /etc/dhcp/dhcpd.conf a
symlink to the desired config file, but why have /etc/default/isc-dhcp-
server at all if it doesn't work?
The offending code is in /lib/systemd/system/isc-dhcp-server.service.
Here is a relevant extract:
[Service]
EnvironmentFile=/etc/default/isc-dhcp-server
RuntimeDirectory=dhcp-server
# The leases files need to be root:dhcpd even when dropping privileges
ExecStart=/bin/sh -ec '\
CONFIG_FILE=/etc/dhcp/dhcpd.conf; \
if [ -f /etc/ltsp/dhcpd.conf ]; then CONFIG_FILE=/etc/ltsp/dhcpd.conf; fi; \
[ -e /var/lib/dhcp/dhcpd.leases ] || touch /var/lib/dhcp/dhcpd.leases; \
chown root:dhcpd /var/lib/dhcp /var/lib/dhcp/dhcpd.leases; \
chmod 775 /var/lib/dhcp ; chmod 664 /var/lib/dhcp/dhcpd.leases; \
exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid
-cf $CONFIG_FILE $INTERFACES'
/etc/default/isc-dhcp-server is correctly read as an EnvironmentFile,
but the ExecStart command unconditionally sets CONFIG_FILE, discarding
any value from the /etc/default file.
One fix might be to change the first few lines of the ExecStart to check
whether $CONFIG_FILE has been set, and perhaps whether it is still the
default value:
ExecStart=/bin/sh -ec '\
case $CONFIG_FILE in \
""|/etc/dhcp/dhcpd.conf) \
CONFIG_FILE=/etc/dhcp/dhcpd.conf; \
if [ -f /etc/ltsp/dhcpd.conf ]; then CONFIG_FILE=/etc/ltsp/dhcpd.conf;
fi; \
;; \
esac
Or it might make more sense to let whatever package is in charge of ltsp
configuration append CONFIG_FILE=/etc/ltsp/dhcpd.conf to /etc/defaults
/isc-dhcp-server, and replace the lines above with a simple
ExecStart=/bin/sh -ec '\
CONFIG_FILE=${CONFIG_FILE:-/etc/dhcp/dhcpd.conf}; \
Either way, a fix would be appreciated.
** Affects: isc-dhcp (Ubuntu)
Importance: Undecided
Status: New
--
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/1824433
Title:
dhcpd ignores $CONFIG_FILE in /etc/default/isc-dhcp-server
Status in isc-dhcp package in Ubuntu:
New
Bug description:
Package isc-dhcp-server 4.3.3 on Ubuntu 16.04 LTS.
On earlier (pre-systemd) systems, one could point dhcpd at a
configuration file in any location by setting
CONFIG_FILE=/new/path/dhcpd.conf in /etc/default/isc-dhcp-server. In
this version such setting is ignored; dhcpd always uses the default
/etc/dhcp/dhcpd.conf.
In more formulaeic terms:
Put CONFIG_FILE=/var/dhcpconf/mydhcp.conf in /etc/default/isc-dhcp-server.
I expect that when service isc-dhcp-server is next started, it will use that
configuration file.
In fact it still uses /etc/dhcp/dhcpd.conf.
The problem can be worked around by making /etc/dhcp/dhcpd.conf a
symlink to the desired config file, but why have /etc/default/isc-
dhcp-server at all if it doesn't work?
The offending code is in /lib/systemd/system/isc-dhcp-server.service.
Here is a relevant extract:
[Service]
EnvironmentFile=/etc/default/isc-dhcp-server
RuntimeDirectory=dhcp-server
# The leases files need to be root:dhcpd even when dropping privileges
ExecStart=/bin/sh -ec '\
CONFIG_FILE=/etc/dhcp/dhcpd.conf; \
if [ -f /etc/ltsp/dhcpd.conf ]; then CONFIG_FILE=/etc/ltsp/dhcpd.conf;
fi; \
[ -e /var/lib/dhcp/dhcpd.leases ] || touch /var/lib/dhcp/dhcpd.leases; \
chown root:dhcpd /var/lib/dhcp /var/lib/dhcp/dhcpd.leases; \
chmod 775 /var/lib/dhcp ; chmod 664 /var/lib/dhcp/dhcpd.leases; \
exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid
-cf $CONFIG_FILE $INTERFACES'
/etc/default/isc-dhcp-server is correctly read as an EnvironmentFile,
but the ExecStart command unconditionally sets CONFIG_FILE, discarding
any value from the /etc/default file.
One fix might be to change the first few lines of the ExecStart to
check whether $CONFIG_FILE has been set, and perhaps whether it is
still the default value:
ExecStart=/bin/sh -ec '\
case $CONFIG_FILE in \
""|/etc/dhcp/dhcpd.conf) \
CONFIG_FILE=/etc/dhcp/dhcpd.conf; \
if [ -f /etc/ltsp/dhcpd.conf ]; then
CONFIG_FILE=/etc/ltsp/dhcpd.conf; fi; \
;; \
esac
Or it might make more sense to let whatever package is in charge of
ltsp configuration append
[Touch-packages] [Bug 1823872] Re: Fixing fsfreeze-hook can break unattended upgrades
** Changed in: unattended-upgrades (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1823872 Title: Fixing fsfreeze-hook can break unattended upgrades Status in qemu package in Ubuntu: Invalid Status in unattended-upgrades package in Ubuntu: Fix Committed Bug description: [Impact] * If an update has a new conffile at a path that in a former version was a directory like old: /a/b/c new: a/b Here b is the new file name and was a directory in the old version. Then unattended upgrades breaks on installing such a package. * a recent qemu update has such a case and due to that triggered the issue in >=Bionic * The fix is to harden unattended upgrades to be able to handle the case without aborting. [Test Case] Get a qemu guest e.g. of Bionic before the update to 1:2.11+dfsg-1ubuntu7.12 That can be done with: $ time uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=bionic $ uvt-kvm create --password ubuntu bionic-testuu arch=amd64 release=bionic label=daily Log in and apt update & upgrade all packages, then Install the release level qemu in there. $ uvt-kvm ssh bionic-testuu $ sudo apt update $ sudo apt dist-upgrade $ sudo apt install unattended-upgrades $ sudo apt install qemu-guest-agent=1:2.11+dfsg-1ubuntu7 All before was preparation, now force the unattended upgrade to trigger the bug. $ sudo unattended-upgrade -d With the bug you'll find some error like: found pkg: qemu-guest-agent conffile line: /etc/init.d/qemu-guest-agent f61a64ac1e48993023018fd1cff85191 current md5: f61a64ac1e48993023018fd1cff85191 conffile line: /etc/qemu/fsfreeze-hook/fsfreeze-hook 15f6ff42cbc5550a07ee21c2a471d905 /etc/qemu/fsfreeze-hook/fsfreeze-hook not in package conffiles /etc/init.d/qemu-guest-agent /etc/qemu/fsfreeze-hook found conffile /etc/qemu/fsfreeze-hook in new pkg but on dpkg status Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 2057, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1773, in main if conffile_prompt(item.destfile): File "/usr/bin/unattended-upgrade", line 988, in conffile_prompt with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook' [Regression Potential] TODO: rbalint who writes the fix * discussion of how regressions are most likely to manifest as a result of this change. * It is assumed that any SRU candidate patch is well-tested before upload and has a low overall risk of regression, but it's important to make the effort to think about what ''could'' happen in the event of a regression. * This both shows the SRU team that the risks have been considered, and provides guidance to testers in regression-testing the SRU. [Other Info] * n/a --- As reported on https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1820291/comments/20 We fixed an issue and we added workrounds since basic mv_conffile coudn't handle it and did all sort of upgrade tests. That all worked fine and moved the conffile. It was now reported that due to some pre-checks that unattended upgrades might do this might do some checks on its own. Next step: - check unattended upgrades through this change - check if it only affects cases were the former config was modified (minority) or the default file layout (majority) --- original report copied --- just wanted to add: This bug also crashes unattended-upgrade and thus prevents security updates on 18.04: root@mailin1:~# unattended-upgrade Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1998, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1714, in main if conffile_prompt(item.destfile): File "/usr/bin/unattended-upgrade", line 929, in conffile_prompt with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook' Basically, unattended-upgrade wants to compare old/new conffiles and doesn't like it when the old conffile turns out to be a directory... This prevents security updates to be installed. The unattended-upgrade logs do not contain the trace, only the messages: 2019-04-05 13:24:24,851 INFO Initial blacklisted packages: 2019-04-05 13:24:24,853 INFO Initial whitelisted packages: 2019-04-05 13:24:24,853 INFO Starting unattended upgrades script 2019-04-05 13:24:24,854 INFO Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic' And that's it. You can't really get out of this without manually running
[Touch-packages] [Bug 1824152] Re: /usr/share/apport/whoopsie-upload-all:AttributeError:process_report:add_gdb_info:gdb_command:write:read:readinto:read:/usr/share/apport/whoopsie-upload-all@166:colle
This bug was fixed in the package apport - 2.20.10-0ubuntu27 --- apport (2.20.10-0ubuntu27) disco; urgency=medium * data/whoopsie-upload-all: confirm the exception has an errno before using it in a comparison. (LP: #1824152) -- Brian Murray Thu, 11 Apr 2019 09:52:07 -0700 ** Changed in: apport (Ubuntu Disco) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1824152 Title: /usr/share/apport/whoopsie-upload- all:AttributeError:process_report:add_gdb_info:gdb_command:write:read:readinto:read:/usr/share/apport /whoopsie-upload-all@166:collect_info:process_report Status in apport package in Ubuntu: Fix Released Status in apport source package in Disco: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.10-0ubuntu26, the problem page at https://errors.ubuntu.com/problem/069eb695cd341ac71e40453596403139bc245c08 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1824152/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813464] Re: package sasl2-bin 2.1.27+dfsg-1 failed to install/upgrade: installed sasl2-bin package post-installation script subprocess returned error exit status 1
not a bug in init-system-helpers or cyrus2-sasl, but in ubuntu-release- upgrader, which has a local version of invoke-rc.d (DistUpgrade/imported /invoke-rc.d) that it puts on its path. I don't know why it does that, but it's clearly not up to date with disco. ** Changed in: ubuntu-release-upgrader (Ubuntu Disco) Status: New => Triaged ** Changed in: ubuntu-release-upgrader (Ubuntu Disco) Importance: High => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1813464 Title: package sasl2-bin 2.1.27+dfsg-1 failed to install/upgrade: installed sasl2-bin package post-installation script subprocess returned error exit status 1 Status in cyrus-sasl2 package in Ubuntu: Triaged Status in ubuntu-release-upgrader package in Ubuntu: Triaged Status in cyrus-sasl2 source package in Disco: Triaged Status in ubuntu-release-upgrader source package in Disco: Triaged Bug description: I know that's not a good thing, but i try to upgrade versions by sSh ProblemType: Package DistroRelease: Ubuntu 19.04 Package: sasl2-bin 2.1.27+dfsg-1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 Date: Sun Jan 27 09:34:34 2019 ErrorMessage: installed sasl2-bin package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.7, Python 3.7.2rc1, python3-minimal, 3.7.1-1ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.2ubuntu2 apt 1.8.0~beta1 SourcePackage: cyrus-sasl2 Title: package sasl2-bin 2.1.27+dfsg-1 failed to install/upgrade: installed sasl2-bin package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to disco on 2019-01-27 (0 days ago) mtime.conffile..etc.default.saslauthd: 2019-01-14T05:57:07.197338 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1813464/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813464] Re: package sasl2-bin 2.1.27+dfsg-1 failed to install/upgrade: installed sasl2-bin package post-installation script subprocess returned error exit status 1
But also, init-system-helpers was already upgraded to the disco version when this happened (both for me, and for the original reporter) so I don't know why invoke-rc.d doesn't recognize this option given that it appears to be present in /usr/sbin/invoke-rc.d in disco. ** Also affects: init-system-helpers (Ubuntu) Importance: Undecided Status: New ** Changed in: init-system-helpers (Ubuntu Disco) Importance: Undecided => High ** Package changed: init-system-helpers (Ubuntu Disco) => ubuntu- release-upgrader (Ubuntu Disco) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1813464 Title: package sasl2-bin 2.1.27+dfsg-1 failed to install/upgrade: installed sasl2-bin package post-installation script subprocess returned error exit status 1 Status in cyrus-sasl2 package in Ubuntu: Triaged Status in ubuntu-release-upgrader package in Ubuntu: Triaged Status in cyrus-sasl2 source package in Disco: Triaged Status in ubuntu-release-upgrader source package in Disco: Triaged Bug description: I know that's not a good thing, but i try to upgrade versions by sSh ProblemType: Package DistroRelease: Ubuntu 19.04 Package: sasl2-bin 2.1.27+dfsg-1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 Date: Sun Jan 27 09:34:34 2019 ErrorMessage: installed sasl2-bin package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.7, Python 3.7.2rc1, python3-minimal, 3.7.1-1ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.2ubuntu2 apt 1.8.0~beta1 SourcePackage: cyrus-sasl2 Title: package sasl2-bin 2.1.27+dfsg-1 failed to install/upgrade: installed sasl2-bin package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to disco on 2019-01-27 (0 days ago) mtime.conffile..etc.default.saslauthd: 2019-01-14T05:57:07.197338 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1813464/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813464] Re: package sasl2-bin 2.1.27+dfsg-1 failed to install/upgrade: installed sasl2-bin package post-installation script subprocess returned error exit status 1
I just reproduced this bug on an upgrade from cosmic to disco. Apparently sasl2-bin is using a new option to invoke-rc.d which is not supported in the cosmic version of init-system-helpers, but does not have an appropriate versioned dependency on whichever version introduces this new flag. This is reproducible with the stock Ubuntu packages and the original report of 'third-party-packages' is a false positive. ** Changed in: cyrus-sasl2 (Ubuntu) Importance: Undecided => High ** Changed in: cyrus-sasl2 (Ubuntu) Status: Expired => Triaged ** Also affects: cyrus-sasl2 (Ubuntu Disco) Importance: High Status: Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1813464 Title: package sasl2-bin 2.1.27+dfsg-1 failed to install/upgrade: installed sasl2-bin package post-installation script subprocess returned error exit status 1 Status in cyrus-sasl2 package in Ubuntu: Triaged Status in ubuntu-release-upgrader package in Ubuntu: Triaged Status in cyrus-sasl2 source package in Disco: Triaged Status in ubuntu-release-upgrader source package in Disco: Triaged Bug description: I know that's not a good thing, but i try to upgrade versions by sSh ProblemType: Package DistroRelease: Ubuntu 19.04 Package: sasl2-bin 2.1.27+dfsg-1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 Date: Sun Jan 27 09:34:34 2019 ErrorMessage: installed sasl2-bin package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.7, Python 3.7.2rc1, python3-minimal, 3.7.1-1ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.2ubuntu2 apt 1.8.0~beta1 SourcePackage: cyrus-sasl2 Title: package sasl2-bin 2.1.27+dfsg-1 failed to install/upgrade: installed sasl2-bin package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to disco on 2019-01-27 (0 days ago) mtime.conffile..etc.default.saslauthd: 2019-01-14T05:57:07.197338 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1813464/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824425] [NEW] network-manager dies in package postinst on cosmic->disco upgrade
Public bug reported: I just did a cosmic->disco upgrade and as soon as the network-manager package was configured, my network dropped. Setting up network-manager (1.12.4-1ubuntu1) ... As soon as this package was configured, the NetworkManager service died, the NM applet disappeared from my desktop, and my network dropped. The NetworkManager service eventually succeeded in restarting, but it took 12 minutes. journalctl output looks like: Apr 11 13:30:43 virgil systemd[1]: Stopping Network Manager... Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.2262] caught SIGTERM, shutting down normally. Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.2277] device (wlan2): state change: activated -> deactivating (reason 'unmanaged', sys-iface-state: 'managed') Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.2392] device (wlan2): state change: deactivating -> unmanaged (reason 'removed', sys-iface-state: 'managed') Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.3055] dhcp4 (wlan2): canceled DHCP transaction, DHCP client pid 2596 Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.3056] dhcp4 (wlan2): state changed bound -> done Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.4210] device (virbr0-nic): released from master device virbr0 Apr 11 13:30:43 virgil NetworkManager[2684]: [1555014643.4430] exiting (success) Apr 11 13:30:43 virgil systemd[1]: NetworkManager.service: Succeeded. Apr 11 13:30:43 virgil systemd[1]: Stopped Network Manager. Apr 11 13:30:43 virgil systemd[1]: Starting Network Manager... Apr 11 13:32:13 virgil systemd[1]: NetworkManager.service: Start operation timed out. Terminating. Apr 11 13:32:13 virgil systemd[1]: NetworkManager.service: Main process exited, code=killed, status=15/TERM Apr 11 13:32:13 virgil systemd[1]: NetworkManager.service: Failed with result 'timeout'. Apr 11 13:32:13 virgil systemd[1]: Failed to start Network Manager. Apr 11 13:32:14 virgil systemd[1]: NetworkManager.service: Service RestartSec=100ms expired, scheduling restart. Apr 11 13:32:14 virgil systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 1. Apr 11 13:32:14 virgil systemd[1]: Stopped Network Manager. Apr 11 13:32:14 virgil systemd[1]: Starting Network Manager... Apr 11 13:33:50 virgil systemd[1]: NetworkManager.service: Start operation timed out. Terminating. Apr 11 13:33:50 virgil systemd[1]: NetworkManager.service: Main process exited, code=killed, status=15/TERM Apr 11 13:33:50 virgil systemd[1]: NetworkManager.service: Failed with result 'timeout'. Apr 11 13:33:50 virgil systemd[1]: Failed to start Network Manager. Apr 11 13:33:50 virgil systemd[1]: NetworkManager.service: Service RestartSec=100ms expired, scheduling restart. Apr 11 13:33:50 virgil systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 2. Apr 11 13:33:50 virgil systemd[1]: Stopped Network Manager. Apr 11 13:33:50 virgil systemd[1]: Starting Network Manager... Apr 11 13:35:21 virgil systemd[1]: NetworkManager.service: Start operation timed out. Terminating. Apr 11 13:35:21 virgil systemd[1]: NetworkManager.service: Main process exited, code=killed, status=15/TERM Apr 11 13:35:21 virgil systemd[1]: NetworkManager.service: Failed with result 'timeout'. Apr 11 13:35:21 virgil systemd[1]: Failed to start Network Manager. Apr 11 13:36:52 virgil systemd[1]: NetworkManager.service: Service RestartSec=100ms expired, scheduling restart. Apr 11 13:36:52 virgil systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 3. Apr 11 13:36:52 virgil systemd[1]: Stopped Network Manager. Apr 11 13:36:52 virgil systemd[1]: Starting Network Manager... Apr 11 13:38:28 virgil systemd[1]: NetworkManager.service: Start operation timed out. Terminating. Apr 11 13:38:28 virgil systemd[1]: NetworkManager.service: Main process exited, code=killed, status=15/TERM Apr 11 13:38:28 virgil systemd[1]: NetworkManager.service: Failed with result 'timeout'. Apr 11 13:38:28 virgil systemd[1]: Failed to start Network Manager. Apr 11 13:38:29 virgil systemd[1]: NetworkManager.service: Service RestartSec=100ms expired, scheduling restart. Apr 11 13:38:29 virgil systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 4. Apr 11 13:38:29 virgil systemd[1]: Stopped Network Manager. Apr 11 13:38:29 virgil systemd[1]: Starting Network Manager... Apr 11 13:40:00 virgil systemd[1]: NetworkManager.service: Start operation timed out. Terminating. Apr 11 13:40:01 virgil systemd[1]: NetworkManager.service: Main process exited, code=killed, status=15/TERM Apr 11 13:40:01 virgil systemd[1]: NetworkManager.service: Failed with result 'timeout'. Apr 11 13:40:01 virgil systemd[1]: Failed to start Network Manager. Apr 11 13:40:01 virgil systemd[1]: NetworkManager.service: Service RestartSec=100ms expired, scheduling restart. Apr 11 13:40:01 virgil systemd[1]: NetworkManager.service: Scheduled
[Touch-packages] [Bug 1822993] Please test proposed package
Hello Matthias, or anyone else affected, Accepted python3-stdlib-extensions into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python3-stdlib- extensions/3.6.8-1~18.10 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1822993 Title: SRU: update Python 2.7 to 2.7.16, Python 3.7 to 3.7.3 and 3.6 to 3.6.8 Status in python-stdlib-extensions package in Ubuntu: New Status in python2.7 package in Ubuntu: New Status in python3-stdlib-extensions package in Ubuntu: New Status in python3.6 package in Ubuntu: New Status in python3.7 package in Ubuntu: New Status in python-stdlib-extensions source package in Cosmic: Fix Committed Status in python2.7 source package in Cosmic: Fix Committed Status in python3-stdlib-extensions source package in Cosmic: Fix Committed Status in python3.6 source package in Cosmic: Fix Committed Status in python3.7 source package in Cosmic: Fix Committed Bug description: SRU: update Python 3.7 to the 3.7.3 release, update Python 3.6 to the 3.6.8 release. python3-stdlib-extensions also updates the modules to the 3.6.8 release for Python 3.6. Acceptance Criteria: The package builds, and the test suite doesn't show regressions. The test suite passes in the autopkg tests. The new packages don't cause regressions in a test rebuild of the main component. http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-cosmic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-gcc8-cosmic.html The test rebuilds are finished, and don't show any regressions for the main component. Regression Potential: Python 3.7 isn't used by default, so we don't have many default users. Regression Potential: Python 3.6 could see some regressions, although we are trying to minimize the risk by doing the test rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-stdlib-extensions/+bug/1822993/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1822993] Re: SRU: update Python 2.7 to 2.7.16, Python 3.7 to 3.7.3 and 3.6 to 3.6.8
Hello Matthias, or anyone else affected, Accepted python-stdlib-extensions into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /python-stdlib-extensions/2.7.16-2~18.10 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: python-stdlib-extensions (Ubuntu Cosmic) Status: New => Fix Committed ** Changed in: python3.7 (Ubuntu Cosmic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1822993 Title: SRU: update Python 2.7 to 2.7.16, Python 3.7 to 3.7.3 and 3.6 to 3.6.8 Status in python-stdlib-extensions package in Ubuntu: New Status in python2.7 package in Ubuntu: New Status in python3-stdlib-extensions package in Ubuntu: New Status in python3.6 package in Ubuntu: New Status in python3.7 package in Ubuntu: New Status in python-stdlib-extensions source package in Cosmic: Fix Committed Status in python2.7 source package in Cosmic: Fix Committed Status in python3-stdlib-extensions source package in Cosmic: Fix Committed Status in python3.6 source package in Cosmic: Fix Committed Status in python3.7 source package in Cosmic: Fix Committed Bug description: SRU: update Python 3.7 to the 3.7.3 release, update Python 3.6 to the 3.6.8 release. python3-stdlib-extensions also updates the modules to the 3.6.8 release for Python 3.6. Acceptance Criteria: The package builds, and the test suite doesn't show regressions. The test suite passes in the autopkg tests. The new packages don't cause regressions in a test rebuild of the main component. http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-cosmic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-gcc8-cosmic.html The test rebuilds are finished, and don't show any regressions for the main component. Regression Potential: Python 3.7 isn't used by default, so we don't have many default users. Regression Potential: Python 3.6 could see some regressions, although we are trying to minimize the risk by doing the test rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-stdlib-extensions/+bug/1822993/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1822993] Please test proposed package
Hello Matthias, or anyone else affected, Accepted python3.6 into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python3.6/3.6.8-1~18.10 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: python3-stdlib-extensions (Ubuntu Cosmic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1822993 Title: SRU: update Python 2.7 to 2.7.16, Python 3.7 to 3.7.3 and 3.6 to 3.6.8 Status in python-stdlib-extensions package in Ubuntu: New Status in python2.7 package in Ubuntu: New Status in python3-stdlib-extensions package in Ubuntu: New Status in python3.6 package in Ubuntu: New Status in python3.7 package in Ubuntu: New Status in python-stdlib-extensions source package in Cosmic: Fix Committed Status in python2.7 source package in Cosmic: Fix Committed Status in python3-stdlib-extensions source package in Cosmic: Fix Committed Status in python3.6 source package in Cosmic: Fix Committed Status in python3.7 source package in Cosmic: Fix Committed Bug description: SRU: update Python 3.7 to the 3.7.3 release, update Python 3.6 to the 3.6.8 release. python3-stdlib-extensions also updates the modules to the 3.6.8 release for Python 3.6. Acceptance Criteria: The package builds, and the test suite doesn't show regressions. The test suite passes in the autopkg tests. The new packages don't cause regressions in a test rebuild of the main component. http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-cosmic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-gcc8-cosmic.html The test rebuilds are finished, and don't show any regressions for the main component. Regression Potential: Python 3.7 isn't used by default, so we don't have many default users. Regression Potential: Python 3.6 could see some regressions, although we are trying to minimize the risk by doing the test rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-stdlib-extensions/+bug/1822993/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1822993] Please test proposed package
Hello Matthias, or anyone else affected, Accepted python3.7 into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python3.7/3.7.3-2~18.10 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: python3.6 (Ubuntu Cosmic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1822993 Title: SRU: update Python 2.7 to 2.7.16, Python 3.7 to 3.7.3 and 3.6 to 3.6.8 Status in python-stdlib-extensions package in Ubuntu: New Status in python2.7 package in Ubuntu: New Status in python3-stdlib-extensions package in Ubuntu: New Status in python3.6 package in Ubuntu: New Status in python3.7 package in Ubuntu: New Status in python-stdlib-extensions source package in Cosmic: Fix Committed Status in python2.7 source package in Cosmic: Fix Committed Status in python3-stdlib-extensions source package in Cosmic: Fix Committed Status in python3.6 source package in Cosmic: Fix Committed Status in python3.7 source package in Cosmic: Fix Committed Bug description: SRU: update Python 3.7 to the 3.7.3 release, update Python 3.6 to the 3.6.8 release. python3-stdlib-extensions also updates the modules to the 3.6.8 release for Python 3.6. Acceptance Criteria: The package builds, and the test suite doesn't show regressions. The test suite passes in the autopkg tests. The new packages don't cause regressions in a test rebuild of the main component. http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-cosmic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-gcc8-cosmic.html The test rebuilds are finished, and don't show any regressions for the main component. Regression Potential: Python 3.7 isn't used by default, so we don't have many default users. Regression Potential: Python 3.6 could see some regressions, although we are trying to minimize the risk by doing the test rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-stdlib-extensions/+bug/1822993/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1808476] Re: Please bump libssl1.1 dependency to at least >= 1.1.1, as headers leak constants
Hello Dimitri, or anyone else affected, Accepted python2.7 into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python2.7/2.7.16-2~18.10 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Description changed: + [Impact] + $ python -c 'import ssl; print(ssl.OP_NO_TLSv1_3)' Prints 0, for python2.7 built against 1.1.0 headers, yet prints 536870912 when built against 1.1.1 irrespective of the runtime libssl1.1 library version. This may yield confusion, especially since ssl.OPENSSL_VERSION reports runtime libssl version, not the version of the libssl headers. Such that, e.g. it looks like ssl module is running against 1.1.1, has OP_NO_TLSv1_3 option, yet cannot actually use it to disable TLSv1.3. Also vice versa, python2.7 build against 1.1.1 can be installed with 1.1.0 runtime library, and thus OP_NO_TLSv1_3 might be set, which is not understood by the runtime library. In libpython2.7-stdlib, please bump libssl1.1 version dep to "libssl1.1 (>= 1.1.1)" when building against libssl-dev >= 1.1.1. python3.x are not affected, as they started to exploit 1.1.1-only symbols/features, and thus already have an automatic dep on >= 1.1.1. + + [Test Case] + + Make sure the libssl1.1 build-dependency of python2.7 is at least 1.1.1. + + [Regression Potential] + + Potentially none, besides the usual regression potential of new + rebuilds. ** Changed in: python2.7 (Ubuntu Cosmic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1808476 Title: Please bump libssl1.1 dependency to at least >= 1.1.1, as headers leak constants Status in python2.7 package in Ubuntu: Fix Released Status in python2.7 source package in Bionic: New Status in python2.7 source package in Cosmic: Fix Committed Status in python2.7 source package in Disco: Fix Released Bug description: [Impact] $ python -c 'import ssl; print(ssl.OP_NO_TLSv1_3)' Prints 0, for python2.7 built against 1.1.0 headers, yet prints 536870912 when built against 1.1.1 irrespective of the runtime libssl1.1 library version. This may yield confusion, especially since ssl.OPENSSL_VERSION reports runtime libssl version, not the version of the libssl headers. Such that, e.g. it looks like ssl module is running against 1.1.1, has OP_NO_TLSv1_3 option, yet cannot actually use it to disable TLSv1.3. Also vice versa, python2.7 build against 1.1.1 can be installed with 1.1.0 runtime library, and thus OP_NO_TLSv1_3 might be set, which is not understood by the runtime library. In libpython2.7-stdlib, please bump libssl1.1 version dep to "libssl1.1 (>= 1.1.1)" when building against libssl-dev >= 1.1.1. python3.x are not affected, as they started to exploit 1.1.1-only symbols/features, and thus already have an automatic dep on >= 1.1.1. [Test Case] Make sure the libssl1.1 build-dependency of python2.7 is at least 1.1.1. [Regression Potential] Potentially none, besides the usual regression potential of new rebuilds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1808476/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1822993] Re: SRU: update Python 2.7 to 2.7.16, Python 3.7 to 3.7.3 and 3.6 to 3.6.8
Hello Matthias, or anyone else affected, Accepted python2.7 into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python2.7/2.7.16-2~18.10 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: python2.7 (Ubuntu Cosmic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1822993 Title: SRU: update Python 2.7 to 2.7.16, Python 3.7 to 3.7.3 and 3.6 to 3.6.8 Status in python-stdlib-extensions package in Ubuntu: New Status in python2.7 package in Ubuntu: New Status in python3-stdlib-extensions package in Ubuntu: New Status in python3.6 package in Ubuntu: New Status in python3.7 package in Ubuntu: New Status in python2.7 source package in Cosmic: Fix Committed Bug description: SRU: update Python 3.7 to the 3.7.3 release, update Python 3.6 to the 3.6.8 release. python3-stdlib-extensions also updates the modules to the 3.6.8 release for Python 3.6. Acceptance Criteria: The package builds, and the test suite doesn't show regressions. The test suite passes in the autopkg tests. The new packages don't cause regressions in a test rebuild of the main component. http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-cosmic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-gcc8-cosmic.html The test rebuilds are finished, and don't show any regressions for the main component. Regression Potential: Python 3.7 isn't used by default, so we don't have many default users. Regression Potential: Python 3.6 could see some regressions, although we are trying to minimize the risk by doing the test rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-stdlib-extensions/+bug/1822993/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824415] [NEW] Screen flickers randomly appears on built-in laptop display only
Public bug reported: The issue is similar to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785912 the short video with the problem https://photos.app.goo.gl/i5dHrQUDV1T2gp8o9 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 11 22:42:06 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83b2] InstallationDate: Installed on 2018-12-03 (129 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: HP HP EliteBook 840 G5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=4b3ca7ee-f7ef-4f10-ae37-d86fdeb64942 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/12/2018 dmi.bios.vendor: HP dmi.bios.version: Q78 Ver. 01.04.00 dmi.board.name: 83B2 dmi.board.vendor: HP dmi.board.version: KBC Version 04.53.00 dmi.chassis.asset.tag: F51020 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ78Ver.01.04.00:bd09/12/2018:svnHP:pnHPEliteBook840G5:pvr:rvnHP:rn83B2:rvrKBCVersion04.53.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 G5 dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic corruption ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1824415 Title: Screen flickers randomly appears on built-in laptop display only Status in xorg package in Ubuntu: New Bug description: The issue is similar to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785912 the short video with the problem https://photos.app.goo.gl/i5dHrQUDV1T2gp8o9 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 11 22:42:06 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83b2] InstallationDate: Installed on 2018-12-03 (129 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: HP HP EliteBook 840 G5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=4b3ca7ee-f7ef-4f10-ae37-d86fdeb64942 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/12/2018 dmi.bios.vendor: HP dmi.bios.version: Q78 Ver. 01.04.00 dmi.board.name: 83B2 dmi.board.vendor: HP dmi.board.version: KBC Version 04.53.00 dmi.chassis.asset.tag: F51020 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ78Ver.01.04.00:bd09/12/2018:svnHP:pnHPEliteBook840G5:pvr:rvnHP:rn83B2:rvrKBCVersion04.53.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 G5 dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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
[Touch-packages] [Bug 1798657] Re: gtk3 frontend 'help' window is huge and not resizeable
saw this again on upgrade from cosmic to disco. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1798657 Title: gtk3 frontend 'help' window is huge and not resizeable Status in debconf package in Ubuntu: New Bug description: If I click on 'help' on a debconf question when using the gtk3 frontend, I get a huge window with a 'close' button in the bottom right corner and a small amount of text in the middle of the screen. The window can be resized horizontally, but not vertically. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1798657/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824411] [NEW] ca-certificates pops a bad debconf prompt on upgrade to disco
Public bug reported: On upgrade from cosmic to disco, I get a debconf prompt from ca- certificates: New certificates to activate: mozilla/GlobalSign_Root_CA_-_R6.crt mozilla/OISTE_WISeKey_Global_Root_GC_CA.crt Neither of these two new certificates are selected by default. Looking at the config script, I see that this question is being asked at critical priority. It also appears that this is only being asked because ca- certificates/trust_new_crts is set to 'ask'. This is not a default setting and I have no memory of setting this, but the debconf database says this question has been seen. It's possible I did choose this option at some point despite not having memory of it; though I worry that since this is a continuously-upgraded system, something picked this for me at some point in the past due to a bug. But having decided for 'ask', the UX here is still pretty bad. - If the package's recommendation (and default behavior) is to enable these new certs on upgrade, then the debconf prompt should also have them preselected. Otherwise, this prompt looks like something the package maintainer is NOT recommending that you do, so then why prompt for it at all. - Presenting only the certificate filenames is not a great basis for anyone making a decision about whether or not to enable these certs. If I actually wanted to manage which certs are enabled, in order to make an informed decision I would expect to see things like the CN of the cert and possibly some EKU information, not a filename. ** Affects: ca-certificates (Ubuntu) Importance: Medium Status: New ** Changed in: ca-certificates (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1824411 Title: ca-certificates pops a bad debconf prompt on upgrade to disco Status in ca-certificates package in Ubuntu: New Bug description: On upgrade from cosmic to disco, I get a debconf prompt from ca- certificates: New certificates to activate: mozilla/GlobalSign_Root_CA_-_R6.crt mozilla/OISTE_WISeKey_Global_Root_GC_CA.crt Neither of these two new certificates are selected by default. Looking at the config script, I see that this question is being asked at critical priority. It also appears that this is only being asked because ca- certificates/trust_new_crts is set to 'ask'. This is not a default setting and I have no memory of setting this, but the debconf database says this question has been seen. It's possible I did choose this option at some point despite not having memory of it; though I worry that since this is a continuously-upgraded system, something picked this for me at some point in the past due to a bug. But having decided for 'ask', the UX here is still pretty bad. - If the package's recommendation (and default behavior) is to enable these new certs on upgrade, then the debconf prompt should also have them preselected. Otherwise, this prompt looks like something the package maintainer is NOT recommending that you do, so then why prompt for it at all. - Presenting only the certificate filenames is not a great basis for anyone making a decision about whether or not to enable these certs. If I actually wanted to manage which certs are enabled, in order to make an informed decision I would expect to see things like the CN of the cert and possibly some EKU information, not a filename. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1824411/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1822269] Re: mktemp does not handle -p option when --tmpdir option goes after -p option
This is not a bug, it is expected & reasonable behaviour.
The `-p DIR' and `--tmpdir[=DIR]' mktemp(1) options
are the same, excepting that the argument is
mandatory for -p and optional for --tmpdir. (See
the manpage (`man mktemp') or try `mktemp --help'.)
That is, the following are equivalent:
mktemp -u -p / --tmpdir
mktemp -u -p/--tmpdir
mktemp -u --tmpdir=/ --tmpdir
mktemp -u -p / -p "${TMPDIR:-/tmp}"
All print "FOO/tmp." where is the
value of TMPDIR (/tmp if not set (the usual case)).
Clearly, the LAST (right→most) -p or --tmpdir option
is being used, with all the preceding ones ignored.
--
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/1822269
Title:
mktemp does not handle -p option when --tmpdir option goes after -p
option
Status in coreutils package in Ubuntu:
New
Bug description:
# This is correct. The printed temp file name is in folder /
$ mktemp -u --tmpdir -p /
/tmp.aFd4MwfGDU
# after swapping the options, mktemp do not handle the -p option correctly.
# swapping options should not affect the output.
$ mktemp -u -p / --tmpdir
/tmp/tmp.FkTPrEsTMs
This should be a software bug, not relevant to any hardware.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1822269/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot
This does not need re-testing, already in bionic/cosmic, just closed
again due to changelog for this big backport.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1770082
Title:
systemd-networkd not renaming devices on boot
Status in netplan:
Fix Released
Status in cloud-init package in Ubuntu:
Confirmed
Status in netplan.io package in Ubuntu:
Fix Released
Status in nplan package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Confirmed
Status in nplan source package in Xenial:
Fix Released
Status in netplan.io source package in Bionic:
Fix Committed
Status in netplan.io source package in Cosmic:
Fix Committed
Bug description:
[Impact]
Systems relying on renaming network interfaces at boot and when 'netplan
apply' is run.
[Test case]
- Write a new netplan YAML (adjusting for current system as necessary):
network:
version: 2
ethernets:
ens3:
dhcp4: true
match:
macaddress: 52:54:00:de:bd:f6
set-name: myif0
- Bring down interface : 'ip link set dev ens3 down'
- Run 'netplan apply'
- Verify that the device is correctly renamed to 'myif0'.
- Reboot.
- Make sure the device is correctly renamed to 'myif0'.
[Regression potential]
Changes in rename logic to add udev rules may otherwise impact applying
different settings to the network interfaces. Changes in settings on network
interfaces, missing parameters (especially on bonds, bridges) should be
investigated as potential regressions. Other failures to apply network settings
might also happen if there's a race between applying renames via the udev
rules, and using the new names to apply configuration changes to the interfaces.
=== systemd issue ===
Renaming devices doesn't seem to work.
If I disable all other network configuration and create
/etc/systemd/network/10-network.link with:
[Match]
MACAddress=52:54:00:c1:c9:bb
[Link]
Name=myiface3
I expect this to cause the device with that MAC address to be renamed
to myiface3. However, when I reboot, I instead see:
$ ip l
1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: ens3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff
The device is not renamed.
This link file is pretty much identical to Example 2 in
https://www.freedesktop.org/software/systemd/man/systemd.link.html.
The renaming does work if I boot with net.ifnames=0, and oddly, it
also works if I unbind the device and rebind it as netplan apply does.
No setting of NamePolicy seems to help.
=== Original Bug ==
'set-name:' doesn't change the name of a network interface on boot, it
only works when you do netplan apply.
Say I take this 50-cloud-init.yaml file:
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
ethernets:
ens3:
dhcp4: true
match:
macaddress: 52:54:00:de:bd:f6
set-name: ens3
Say I change set-name to 'myiface3' and reboot. I expect that the
device will be called myiface3 and brought up fine with dhcp. However,
instead I see:
$ ip a
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens3: mtu 1500 qdisc noop state DOWN group default
qlen 1000
link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
The name has not been changed, and the device has not been brought up.
If I run netplan apply however, I see the following:
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
3: myiface3: mtu 1500 qdisc fq_codel state
UP group default qlen 1000
link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
valid_lft 3575sec preferred_lft 3575sec
inet6 fe80::5054:ff:fede:bdf6/64 scope link
[Touch-packages] [Bug 1823761] Re: [SRU] Move Livepatch in a different tab as in Disco
** Description changed: + * Impact + The livepatch graphical interfaces are currently limited in bionic, there is no easy way to know the current status and the details of the changes applied. The new design improves the user experience and we want that to benefit the LTS users + + * Test case + Open software-properties-gtk, you should see a livepatch new tab which has the detail of the status (including the CVEs fixes with the applied livepatch where there is one) + + * Regression potential + The changes are mostly new code so check that the livepatch tab works correctly. + There is some UI refactoring so it's best to check that the other tabs still look the same. + Note that the changes include some new strings. Those are translated in disco and have been announced to the translators in march as coming to bionic for a SRU + (https://lists.ubuntu.com/archives/ubuntu-translators/2019-March/007530.html). + Launchpad shares translations between series so we should get those translations included in the next bionic langpacks export. + + --- + Backport the new Livepatch tab from Disco. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1823761 Title: [SRU] Move Livepatch in a different tab as in Disco Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Bug description: * Impact The livepatch graphical interfaces are currently limited in bionic, there is no easy way to know the current status and the details of the changes applied. The new design improves the user experience and we want that to benefit the LTS users * Test case Open software-properties-gtk, you should see a livepatch new tab which has the detail of the status (including the CVEs fixes with the applied livepatch where there is one) * Regression potential The changes are mostly new code so check that the livepatch tab works correctly. There is some UI refactoring so it's best to check that the other tabs still look the same. Note that the changes include some new strings. Those are translated in disco and have been announced to the translators in march as coming to bionic for a SRU (https://lists.ubuntu.com/archives/ubuntu-translators/2019-March/007530.html). Launchpad shares translations between series so we should get those translations included in the next bionic langpacks export. --- Backport the new Livepatch tab from Disco. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1823761/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823761] Re: [SRU] Move Livepatch in a different tab as in Disco
** Changed in: software-properties (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: software-properties (Ubuntu Bionic) Importance: Undecided => High ** Changed in: software-properties (Ubuntu Bionic) Assignee: (unassigned) => Andrea Azzarone (azzar1) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1823761 Title: [SRU] Move Livepatch in a different tab as in Disco Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Bug description: Backport the new Livepatch tab from Disco. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1823761/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798313] Re: traceoute6 gives error sendto: Invalid argument
Yes I also ran into this same problem. $ traceroute6 -n 2001:4860:4860:: traceroute to 2001:4860:4860:: (2001:4860:4860::) from 2003:XX, 30 hops max, 24 byte packets sendto: Invalid argument 1 traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1 *sendto: Invalid argument traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1 *sendto: Invalid argument $ traceroute6 -V traceroute6 utility, iputils-s20161105 $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic $ dpkg-query -s iputils-tracepath Package: iputils-tracepath Status: install ok installed Priority: optional Section: net Installed-Size: 76 Maintainer: Ubuntu Developers Architecture: amd64 Source: iputils Version: 3:20161105-1ubuntu2 Depends: libc6 (>= 2.15), libcap2 (>= 1:2.10), libidn11 (>= 1.13) Suggests: traceroute Description: Tools to trace the network path to a remote host The tracepath utility is similar to the traceroute utility, but also attempts to discover the MTU of the path. Supports IPv4 and IPv6. Original-Maintainer: Noah Meyerhans -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1798313 Title: traceoute6 gives error sendto: Invalid argument Status in Iputils: Fix Released Status in iputils package in Ubuntu: Confirmed Status in iputils package in Debian: Fix Released Bug description: When running the following command all get is an error. (traceroute6.db works) # traceroute6.iputils 2001:4860:4860:: traceroute to 2001:4860:4860:: (2001:4860:4860::) from 2a00:8780:3:42:b92a:b222:8bed:4a9b, 30 hops max, 24 byte packets sendto: Invalid argument 1 traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1 *sendto: Invalid argument traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1 *sendto: Invalid argument traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1 * This seems like a regression of Debian bug https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=843264 Package version installed: iputils-tracepath 3:20161105-1ubuntu2 amd64 # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic To manage notifications about this bug go to: https://bugs.launchpad.net/iputils/+bug/1798313/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818814] Re: systemd-tmpfiles-setup.services fails to create /var/run directories
In addition to debug output from systemd-tmpfiles-setup.service as above, it is also interesting to know the permiissions on / itself, ie. what's the output of: $ ls -la / -- 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/1818814 Title: systemd-tmpfiles-setup.services fails to create /var/run directories Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: In Progress Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description:Ubuntu 16.04.6 LTS Release:16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center systemd: Installed: 229-4ubuntu21.16 Candidate: 229-4ubuntu21.16 Version table: *** 229-4ubuntu21.16 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3) What you expected to happen 4) What happened instead Ubuntu server (running in OpenVZ VPS farm, thus the old kernel version) has been up and running happily, until I performed apt-get upgrade and rebooted the server. After reboot, I could not establish SSH connection to server, port 22 connection was refused. I opened a HTML console to my server instance and checked logs. From the logs, it was shown, that SSH server could not start, as it did not have the /var/run/sshd directory. After scrolling back the /var/log/syslog, I noticed that there were lots of other /var/run subdirectories, which were not created. Here is cut from /var/log/syslog, related to systemd-tmpfiles: ---8<---8<--- Mar 6 12:32:54 vspk systemd-tmpfiles[81]: [/usr/lib/tmpfiles.d/00rsyslog.conf:6] Duplicate line for path "/v ar/log", ignoring. Mar 6 12:32:54 vspk systemd[1]: Starting Raise network interfaces... Mar 6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/named failed: Invalid argument Mar 6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path /var/run/fail2ban: Too many levels of symb olic links Mar 6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path /var/run/screen: Too many levels of symbol ic links Mar 6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path /var/run/sshd: Too many levels of symbolic links Mar 6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path /var/run/sudo: Too many levels of symbolic links Mar 6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path /var/run/sudo/ts: Too many levels of symbo lic links Mar 6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/utmp failed: Invalid argument Mar 6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/systemd/netif failed: Invalid argument Mar 6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/systemd/netif/links failed: Invalid argument Mar 6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/systemd/netif/leases failed: Invalid argument Mar 6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path /var/run/zabbix: Too many levels of symbol ic links
[Touch-packages] [Bug 1824405] [NEW] [HDA-Intel - HD-Audio Generic, playback] Playback problem
Public bug reported: with latest alsa daily situation did not get better ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hp 1692 F pulseaudio /dev/snd/controlC0: hp 1692 F pulseaudio CurrentDesktop: XFCE Date: Thu Apr 11 20:05:47 2019 InstallationDate: Installed on 2016-09-07 (945 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia Symptom_Type: Only some of outputs are working Title: [HDA-Intel - HD-Audio Generic, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.70 dmi.board.name: FM2A75M-DGS dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-04-08T16:46:31.160212 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1824405 Title: [HDA-Intel - HD-Audio Generic, playback] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: with latest alsa daily situation did not get better ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hp 1692 F pulseaudio /dev/snd/controlC0: hp 1692 F pulseaudio CurrentDesktop: XFCE Date: Thu Apr 11 20:05:47 2019 InstallationDate: Installed on 2016-09-07 (945 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia Symptom_Type: Only some of outputs are working Title: [HDA-Intel - HD-Audio Generic, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.70 dmi.board.name: FM2A75M-DGS dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-04-08T16:46:31.160212 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1824405/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824402] [NEW] [HDA-Intel - HD-Audio Generic, recording] No sound at all
Public bug reported: with latest alsa daily situation did not get better ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hp 1692 F pulseaudio /dev/snd/controlC0: hp 1692 F pulseaudio CurrentDesktop: XFCE Date: Thu Apr 11 19:59:35 2019 InstallationDate: Installed on 2016-09-07 (945 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hp 1692 F pulseaudio /dev/snd/controlC0: hp 1692 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HD-Audio Generic, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.70 dmi.board.name: FM2A75M-DGS dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-04-08T16:46:31.160212 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1824402 Title: [HDA-Intel - HD-Audio Generic, recording] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: with latest alsa daily situation did not get better ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hp 1692 F pulseaudio /dev/snd/controlC0: hp 1692 F pulseaudio CurrentDesktop: XFCE Date: Thu Apr 11 19:59:35 2019 InstallationDate: Installed on 2016-09-07 (945 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hp 1692 F pulseaudio /dev/snd/controlC0: hp 1692 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HD-Audio Generic, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.70 dmi.board.name: FM2A75M-DGS dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-04-08T16:46:31.160212 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1824402/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
Re: [Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail
I ended up uninstalling everything and installing the 18.04 from sctratch.Thanks for your help On Thursday, April 11, 2019, 12:26:08 PM GMT-3, José Enrique <1773...@bugs.launchpad.net> wrote: Hola creo recordar que utilicé estos comandos: sudo mv / usr / share / dbus-1 / system- servicios / org.freedesktop .systemd1. servicio / usr / share / dbus-1 / system- servicios / org.freedesktop .systemd1. Servicio. bak sudo apt-get install -f sudo apt dist-upgrade sudo apt autoremove A mi me funcionó correctamente, pero no lo almacené. Puede ser otro problema con el mismo resultado. Otra solución, que apliqué en un laptop fue sacar un back-up de los archivos de usuario, documentos, descargas... Y reinstalar la nueva versión desde 0 Sañudos El jue., 11 abr. 2019 0:45, loluchayjose <1773...@bugs.launchpad.net> escribió: > Bueno, ninguna de las soluciones aquí está muy clara. Una de ellas es > "sudo apt purge gdm etc."... "etc." que? > > Varios dicen "borrar"... borrar como? > > Tu dijiste: "I solved problem sttoping services and erasing systemd-shim > upon console. > After I could updating my pc, also, from console"... Qué servicios > paraste, y como? Tengo que hacerlo en Safe Mode? > > Uno de los últimos dice: "The upload of systemd that was purported to > fix this bug report was superseded by a security update of systemd so > the fix is no longer available." Así que por lo que se ve, esa solucion > ya no sirve. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1792241). > https://bugs.launchpad.net/bugs/1773859 > > Title: > upgrades to 18.04 fail > > Status in systemd package in Ubuntu: > Fix Released > Status in systemd-shim package in Ubuntu: > Won't Fix > Status in systemd source package in Bionic: > Triaged > Status in systemd-shim source package in Bionic: > Won't Fix > Status in systemd source package in Cosmic: > Fix Released > Status in systemd-shim source package in Cosmic: > Won't Fix > > Bug description: > [Impact] > > * Some systems fail to upgrade due to conflicts between systemd and > the (now removed from the archive) systemd-shim / upstart. > > * Instead of trying to work out what's the problem in ordering / > removal of diverts, ensure that systemd is never unpacked whilst > systemd-shim/upstart are still on disk. Thus declare conflicts against > systemd-shim/upstart packages in systemd package. > > [Test Case] > > * monitor drop-off of upgrades with below reported problem > > * Check that it is possible to upgrade to bionic's libpam-systemd > from xenial with systemd-shim installed on xenial, ie. > > lxc launch ubuntu-daily:xenial test-shim-upgrade > lxc exec test-shim-upgrade > apt update > apt install systemd-shim > wget > https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb > apt install ./systemd-shim_10-3_amd64.deb > sed 's/xenial/bionic/' -i /etc/apt/sources.list > apt update > apt install systemd > > this currently passes, however, systemd-shim remains installed. It > should be removed instead. Apt install systemd should have lines like > this: > > The following packages will be REMOVED: > systemd-shim > ... > Removing 'diversion of > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd > by systemd-shim' > ... > > > [Regression Potential] > > * systemd-shim/upstart are both removed and not supported in bionic, > thus forcing their removal via conflicts should bring the system into > an expected state. > > [Other Info] > > * original bug report > > $ sudo apt upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Done > The following packages will be REMOVED: > systemd-shim > 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. > 1 not fully installed or removed. > After this operation, 71.7 kB disk space will be freed. > Do you want to continue? [Y/n] y > (Reading database ... 63 files and directories currently installed.) > Removing systemd-shim (9-1bzr4ubuntu1) ... > Removing 'diversion of > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd > by systemd-shim' > dpkg-divert: error: rename involves overwriting > '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with > different file > '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', > not allowed > dpkg: error processing package systemd-shim (--remove): > subprocess installed post-removal script returned error exit status 2 > Errors were encountered while processing: > systemd-shim > E: Sub-process /usr/bin/dpkg returned an error code (1) > > Commenting out the dpkg-divert in systemd-shim's postrm solved this > for me and I was about to
[Touch-packages] [Bug 1818282] Re: systemd-networkd - RoutingPolicyRule does not apply correctly
autopkgtest regressions: bionic: dovecot (armhf) re-run passed, hurray! this leaves only test failures that i think we can ignore: systemd (ppc64el): bug 1821625 linux (various): very flaky tests snapd (various) might be bug 1824237, in any case they are all very flaky mariadb-10.1 (various): bug 1824335 linux-aws-edge (amd64): bug 1723223 cosmic: also only ignorable test failures: linux (various): very flaky tests docker.io (various): bug 1824237 systemd (various): bug 1824237 snapd (various): definitely bug 1824237 so i believe all remaining autopkgtest regressions are ignorable for this upload. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1818282 Title: systemd-networkd - RoutingPolicyRule does not apply correctly Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Committed Status in systemd source package in Disco: Fix Released Status in systemd package in Debian: Fix Released Bug description: [Impact] When attaching multiple IPs on secondary interface the routing policy rules do not apply for all IPs. The rules that are applied after restarting networkd are random. The issue has been reported and addressed upstream. [Test Case] Attach multiple IPs to secondary interface, config file: $ cat /etc/systemd/network/ens8.network [Match] Name=ens8 [Network] Address=172.31.28.195/20 Address=172.31.24.151/20 Address=172.31.24.152/20 Address=172.31.24.153/20 [Route] Destination=0.0.0.0/0 Gateway=172.31.16.1 Table=1000 [Route] Destination=172.31.24.153 Gateway=0.0.0.0 Scope=link Table=1000 [Route] Destination=172.31.28.195 Gateway=0.0.0.0 Scope=link Table=1000 [Route] Destination=172.31.24.151 Gateway=0.0.0.0 Scope=link Table=1000 [Route] Destination=172.31.24.152 Gateway=0.0.0.0 Scope=link Table=1000 [RoutingPolicyRule] From=172.31.24.153 Table=1000 [RoutingPolicyRule] From=172.31.28.195 Table=1000 [RoutingPolicyRule] From=172.31.24.152 Table=1000 [RoutingPolicyRule] From=172.31.24.151 Table=1000 $ ip rule show 0:from all lookup local 0:from 172.31.24.151 lookup 1000 32766:from all lookup main 32767:from all lookup default - restart networkd $ sudo systemctl restart systemd-networkd $ ip rule show 0:from all lookup local 0:from 172.31.24.151 lookup 1000 0:from 172.31.24.153 lookup 1000 0:from 172.31.28.195 lookup 1000 32766:from all lookup main 32767:from all lookup default - restart again $ sudo systemctl restart systemd-networkd $ ip rule show 0:from all lookup local 0:from 172.31.24.151 lookup 1000 0:from 172.31.24.152 lookup 1000 32766:from all lookup main 32767:from all lookup default The behaviour is random [Regression Potential] May impact the systemd-networkd service functionality. [Other] Affects Disco Bionic and Cosmic. Upstream bug : https://github.com/systemd/systemd/issues/11280 Upstream fix : https://github.com/systemd/systemd/pull/11795/commits $ lsb_release -rd Description: Ubuntu Disco Dingo (development branch) Release: 19.04 Systemd version : systemd: Installed: 240-6ubuntu1 Candidate: 240-6ubuntu1 Version table: *** 240-6ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818282/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820132] Re: /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport/whoopsie-upload-all@162:collect_info:process_report:add_gdb_info:gdb_command
To test this with whoopsie-upload-all one could do something like the following: 1) xeyes & 2) pkill -11 xeyes 3) sudo mv /usr/bin/xeyes /tmp/ 4) /usr/share/apport/whoopsie-upload-all Don't forget to move xeyes back if you care about it. -- 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/1820132 Title: /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport /whoopsie-upload- all@162:collect_info:process_report:add_gdb_info:gdb_command Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: Triaged Status in apport source package in Disco: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.10-0ubuntu23, the problem page at https://errors.ubuntu.com/problem/4a48673e60f08b7d2b9067d1b47766a57f7e693e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1820132/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (crash in xorg before using "foreign grub") netplan mis-configuration ma
okay a previous "fresh install that was crashing plymouth screen/lightdm/xorg was fixed by copying a known working set of netplan conf files into /etc/netplan .. the 01-netcfg.yaml from the "network install" uses networkd as the renderer .. with a working network device config.. plus the 01-network- manager-all.yaml file as well proof enough? of some weird interactions between services now the minimal 01-network-manager-all.yaml on the new installs seems to be lacking something .. although the documentation says it should work .. which it does if your graphics start properly .. Wayland (ubuntu install) or amd/ati cards probably nvidia too I have not tested but if using the current default netplan and i915 as module NOT listed in /etc/modules .. it does not work it crashes and locks up and only a powerswitch shutdown works .. no reset button on laptop .. no console access is available either .. so it has taken a bit of time to determine all this .. Anybody know how to fix the netplan config in a "generic way" to cure this issue? the only problem is no control over switching networks .. NetworkManager does not seem to have control over the interface started by networkd .. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1821609 Title: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (crash in xorg before using "foreign grub") netplan mis-configuration maybe underlying cause. Status in lightdm package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Invalid Bug description: Okay the has happened recently at least since march 18, 2019 iso and march 22, 2019 iso are both effected very similar to one of my previously reported bugs .. which was related to xorg not being installed .. back ground .. PC is lenovo sl 500 with evo860 SSD drive 3 partions contain installs of disco sda1 -- main working system -- I usually install grub from here as master .. sda6 and sda7 are test installs of disco daily iso's 03-18-2019, 03-22-2019 repectively on the test installs as long as the iso is using the grub boot loader installed from that install the system will boot normally .. the display manger tends to flicker on and off but does final start and login can proceed. but if another install re-installs grub as master the display manager fails to stay active or even come-up for sda6 or sda7 only if their own grubs are reinstalled will they work normally sda1 display manager/xorg login works always no matter which "grub- source" is in control. if I use rescue boot from any grub as master I can get the displays to work by running dpkg fix which does nothing .. and then resuming the boot .. then things work normally.. if the "non-rescue" boots are used the screen/computer locks and only a power down and reboot gives access. (sometime requiring radical depowering .. unpluging and removing battery) now the is a message that appears that RCs??? level is missing. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu11 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Mar 25 11:25:58 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2019-03-23 (1 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322) MachineType: LENOVO 2746CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6AET64WW dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 2746CTO dmi.board.vendor: LENOVO dmi.board.version: LENOVO 6AET64WW dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LENOVO 6AET64WW dmi.modalias:
[Touch-packages] [Bug 1824152] Re: /usr/share/apport/whoopsie-upload-all:AttributeError:process_report:add_gdb_info:gdb_command:write:read:readinto:read:/usr/share/apport/whoopsie-upload-all@166:colle
** Branch linked: lp:~ubuntu-core-dev/ubuntu/disco/apport/ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1824152 Title: /usr/share/apport/whoopsie-upload- all:AttributeError:process_report:add_gdb_info:gdb_command:write:read:readinto:read:/usr/share/apport /whoopsie-upload-all@166:collect_info:process_report Status in apport package in Ubuntu: In Progress Status in apport source package in Disco: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.10-0ubuntu26, the problem page at https://errors.ubuntu.com/problem/069eb695cd341ac71e40453596403139bc245c08 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1824152/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798313] Re: traceoute6 gives error sendto: Invalid argument
and no, using the traceroute package does not fix the issue dudek@test-box:~$ sudo apt-get install traceroute [sudo] password for adudek: Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: traceroute 0 upgraded, 1 newly installed, 0 to remove and 3 not upgraded. Need to get 45.4 kB of archives. After this operation, 152 kB of additional disk space will be used. Get:1 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 traceroute amd64 1:2.1.0-2 [45.4 kB] Fetched 45.4 kB in 3s (14.3 kB/s) Selecting previously unselected package traceroute. (Reading database ... 103312 files and directories currently installed.) Preparing to unpack .../traceroute_1%3a2.1.0-2_amd64.deb ... Unpacking traceroute (1:2.1.0-2) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... Setting up traceroute (1:2.1.0-2) ... update-alternatives: using /usr/bin/traceroute.db to provide /usr/bin/traceroute (traceroute) in auto mode update-alternatives: using /usr/bin/lft.db to provide /usr/bin/lft (lft) in auto mode update-alternatives: using /usr/bin/traceproto.db to provide /usr/bin/traceproto (traceproto) in auto mode update-alternatives: using /usr/sbin/tcptraceroute.db to provide /usr/sbin/tcptraceroute (tcptraceroute) in auto mode adudek@test-box:~$ traceroute6 -V traceroute6 utility, iputils-s20161105 adudek@test-box:~$ traceroute -V Modern traceroute for Linux, version 2.1.0 Copyright (c) 2016 Dmitry Butskoy, License: GPL v2 or any later adudek@test-box:~$ traceroute6 2001:4860:4860:: traceroute to 2001:4860:4860:: (2001:4860:4860::) from 2003:8:8:4:20c:29ff:fe59:583c, 30 hops max, 24 byte packets sendto: Invalid argument 1 traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1 adudek@test-box:~$ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1798313 Title: traceoute6 gives error sendto: Invalid argument Status in Iputils: Fix Released Status in iputils package in Ubuntu: Confirmed Status in iputils package in Debian: Fix Released Bug description: When running the following command all get is an error. (traceroute6.db works) # traceroute6.iputils 2001:4860:4860:: traceroute to 2001:4860:4860:: (2001:4860:4860::) from 2a00:8780:3:42:b92a:b222:8bed:4a9b, 30 hops max, 24 byte packets sendto: Invalid argument 1 traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1 *sendto: Invalid argument traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1 *sendto: Invalid argument traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1 * This seems like a regression of Debian bug https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=843264 Package version installed: iputils-tracepath 3:20161105-1ubuntu2 amd64 # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic To manage notifications about this bug go to: https://bugs.launchpad.net/iputils/+bug/1798313/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798313] Re: traceoute6 gives error sendto: Invalid argument
I have hit this issue too. via iputils-tracepath under ubuntu 18.04. There are actually 2 issues with this, one with ipv6 address and the other to an ipv6 hostname. https://github.com/iputils/iputils/issues/68 https://github.com/iputils/iputils/issues/81 I also do not see how this is fixed in the version when the issue wasn't fixed by the iputils maintainer until after 10 Nov 2016. This is a new issue that is not fixed in the released version of 18.04 iputils-tracepath or any iptuils utility based on the s20161105 build of iptuils. ** Bug watch added: github.com/iputils/iputils/issues #81 https://github.com/iputils/iputils/issues/81 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1798313 Title: traceoute6 gives error sendto: Invalid argument Status in Iputils: Fix Released Status in iputils package in Ubuntu: Confirmed Status in iputils package in Debian: Fix Released Bug description: When running the following command all get is an error. (traceroute6.db works) # traceroute6.iputils 2001:4860:4860:: traceroute to 2001:4860:4860:: (2001:4860:4860::) from 2a00:8780:3:42:b92a:b222:8bed:4a9b, 30 hops max, 24 byte packets sendto: Invalid argument 1 traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1 *sendto: Invalid argument traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1 *sendto: Invalid argument traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1 * This seems like a regression of Debian bug https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=843264 Package version installed: iputils-tracepath 3:20161105-1ubuntu2 amd64 # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic To manage notifications about this bug go to: https://bugs.launchpad.net/iputils/+bug/1798313/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1796251] Re: gnome-shell crashed with SIGSEGV when taking a screenshot, in __strlen_avx2() from real_save_png() from gdk_pixbuf__png_image_save_to_callback() from gdk_pixbuf_real
This bug was fixed in the package gnome-shell - 3.32.0+git20190410-1ubuntu1 --- gnome-shell (3.32.0+git20190410-1ubuntu1) disco; urgency=medium * Merging with debian git snapshot (LP: #1820775, LP: #1818790), remaining changes: + Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests gnome-themes-standard-data, gnome-backgrounds + Add some Recommends: - ubuntu-session (| gnome-session) to have the ubuntu session available - xserver-xorg-legacy - yaru-theme-gnome-shell for the default ubuntu theming + Update debian/gbp.conf with Ubuntu settings + gnome-shell-common.install: Install Ubuntu mode + gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative + ubuntu/desktop_detect.patch: - add caching for desktop detection to avoid querying the current desktop env variable as iterate through the list each time. For the time of the Shell process, we can expect this env variable to stay stable. + ubuntu/smarter_alt_tab.patch: - quick alt-tab (without showing up the switcher) switch only between the last window of the last 2 applications to be focused instead of raising all windows of those apps. + ubuntu/lightdm-user-switching.patch: - Allow user switching when using LightDM. + ubuntu/lock_on_suspend.patch - Respect Ubuntu's lock-on-suspend setting. + ubuntu/gdm.patch - as gdm is system-wide and not session-wide, ensure gdm has an ubuntu styling by default, not impacting the gnome user session though. + ubuntu/background_login.patch - Change default background color as we modified the default GDM color for our ubuntu session. Change it as well here, still applying the background noise loading. + ubuntu/gdm_alternatives.patch - Add support for GDM3 theme alternatives + ubuntu/block_mode_extension_update.patch - Don't allow ubuntu mode extension to update + optional-hot-corner.patch - enable patch proposed by upstream developer already in package (but not in series) to add a settings for optional hot corner activation. + volume-Add-back-sound-feedback-on-scroll.patch - Fix regression causing missing feedback on volume slider scroll + main-show-an-error-message-on-gnome-shell-crash.patch, global-make-possible-to-set-debug-flags-dynamically.patch, main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch, main-add-backtrace-crashes-all-and-backtrace-all.patch, sessionMode-add-support-for-debugFlags-parameter.patch: - Improve debug JS tracing for crash reports + st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch, st-scroll-view-Remove-scrollbars-references-on-dispose.patch: - Fix crash on theme changes + ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch: - stop searches when requested from UI + magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch: - Show monitor scaled cursor when magnifier is enabled * d/p/magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch: - Dropped the merged part, kept the fix for cursor scaling. * d/p/optional-hot-corner.patch, d/p/sessionMode-add-support-for-debugFlags-parameter.patch, d/p/ubuntu/lock_on_suspend.patch, d/p/ubuntu/resolve_alternate_theme_path.patch: - Refreshed. -- Marco Trevisan (Treviño) Wed, 10 Apr 2019 20:15:39 -0500 ** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1796251 Title: gnome-shell crashed with SIGSEGV when taking a screenshot, in __strlen_avx2() from real_save_png() from gdk_pixbuf__png_image_save_to_callback() from gdk_pixbuf_real_save_to_callback() from gdk_pixbuf_save_to_callbackv() Status in GNOME Shell: Fix Released Status in gdk-pixbuf package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.0-3ubuntu1, the problem page at https://errors.ubuntu.com/problem/1473c291c70d181ad72605561ac28f3b860445d5 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/gnome-shell/+bug/1796251/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More
[Touch-packages] [Bug 1659534] Re: userdel doesn't supports extrausers
** Tags removed: verification-done verification-needed-done ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1659534 Title: userdel doesn't supports extrausers Status in Snappy: In Progress Status in shadow package in Ubuntu: Fix Released Status in shadow source package in Xenial: Fix Committed Status in shadow source package in Bionic: Fix Committed Bug description: TEST CASE: - run userdel --extrausers foo on a ubuntu core system REGRESSION POTENTIAL: - low, this option will only take effect when "userdel --extrauser" is used. On an Ubuntu Core system is impossible to delete an user from the extrausers db: root@localhost:/# userdel --extrausers alice userdel: unrecognized option '--extrausers' To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1659534/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818814] Re: systemd-tmpfiles-setup.services fails to create /var/run directories
ok, let's try this; please create a file with the contents and location shown below: ubuntu@lp1818814:~$ cat /etc/systemd/system/systemd-tmpfiles-setup.service.d/debug.conf [Service] Environment="SYSTEMD_LOG_LEVEL=debug" PassEnvironment=SYSTEMD_LOG_LEVEL then, reboot (so the problem is reproduced) and get the output of $ journalctl -b -- 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/1818814 Title: systemd-tmpfiles-setup.services fails to create /var/run directories Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: In Progress Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description:Ubuntu 16.04.6 LTS Release:16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center systemd: Installed: 229-4ubuntu21.16 Candidate: 229-4ubuntu21.16 Version table: *** 229-4ubuntu21.16 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3) What you expected to happen 4) What happened instead Ubuntu server (running in OpenVZ VPS farm, thus the old kernel version) has been up and running happily, until I performed apt-get upgrade and rebooted the server. After reboot, I could not establish SSH connection to server, port 22 connection was refused. I opened a HTML console to my server instance and checked logs. From the logs, it was shown, that SSH server could not start, as it did not have the /var/run/sshd directory. After scrolling back the /var/log/syslog, I noticed that there were lots of other /var/run subdirectories, which were not created. Here is cut from /var/log/syslog, related to systemd-tmpfiles: ---8<---8<--- Mar 6 12:32:54 vspk systemd-tmpfiles[81]: [/usr/lib/tmpfiles.d/00rsyslog.conf:6] Duplicate line for path "/v ar/log", ignoring. Mar 6 12:32:54 vspk systemd[1]: Starting Raise network interfaces... Mar 6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/named failed: Invalid argument Mar 6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path /var/run/fail2ban: Too many levels of symb olic links Mar 6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path /var/run/screen: Too many levels of symbol ic links Mar 6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path /var/run/sshd: Too many levels of symbolic links Mar 6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path /var/run/sudo: Too many levels of symbolic links Mar 6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path /var/run/sudo/ts: Too many levels of symbo lic links Mar 6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/utmp failed: Invalid argument Mar 6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/systemd/netif failed: Invalid argument Mar 6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/systemd/netif/links failed: Invalid argument Mar 6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/systemd/netif/leases
[Touch-packages] [Bug 1822984] Re: revert tls security level back to 1
generated new weak key, cert and try to use it with current cosmic's openssl and succeed: # openssl genrsa -des3 -out myCA.key 600 # openssl req -x509 -new -nodes -key myCA.key -sha256 -days 1825 -out myCA.pem # openssl s_server -cert myCA.pem -key myCA.key -WWW # wget --ca-certificate myCA.pem https://localhost:4433 --2019-04-11 16:18:41-- https://localhost:4433/ Resolving localhost (localhost)... ::1, 127.0.0.1 Connecting to localhost (localhost)|::1|:4433... connected. HTTP request sent, awaiting response... 200 ok Length: unspecified [text/plain] Saving to: 'index.html.2' index.html.2 [ <=> ] 237 --.-KB/sin 0s 2019-04-11 16:18:41 (15.6 MB/s) - 'index.html.2' saved [237] # dpkg -l | grep libssl ii libssl1.1:amd641.1.1-1ubuntu2 Upgraded to: # dpkg -l | grep libssl ii libssl1.1:amd641.1.1-1ubuntu2.2 And now wget fails with too small key error, whilst the s_server is still running: # wget --ca-certificate myCA.pem https://localhost:4433 --2019-04-11 16:20:09-- https://localhost:4433/ Resolving localhost (localhost)... ::1, 127.0.0.1 Connecting to localhost (localhost)|::1|:4433... connected. ERROR: cannot verify localhost's certificate, issued by 'CN=localhost,O=Internet Widgits Pty Ltd,ST=Some-State,C=AU': EE certificate key too weak To connect to localhost insecurely, use `--no-check-certificate'. ** Tags removed: verification-needed verification-needed-cosmic ** Tags added: verification-done verification-done-cosmic -- 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/1822984 Title: revert tls security level back to 1 Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Cosmic: Fix Committed Status in openssl source package in Disco: Fix Released Bug description: [Impact] * increase minimum default tls security level from 0 to 1, as is the default upstream [Test Case] * generate 80bits TLS certificate and attempt to use it * with prior openssl it should work, but with this update it should fail [Regression Potential] * This increases the minimum required certificate/keys sizes and algorithms, back to what Bionic GA openssl 1.1.0 shipped as. It also now will match upstream default. It is still lower than Debian's default that raises it to 2 by default. * Cosmic GA shipped with TLS_SECURITY_LEVEL 0, meaning pretty much any weak keys were accepted. With this change keys lower than 112 will be rejected, which are considered to be too weak to be useful by most CAs out there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1822984/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1822898] Re: wget https://geoip.ubuntu.com/lookup fails in mini.iso d-i
booted cosmic mini-iso with proposed enabled, manually injected the 2.2 udeb, and wget geoip.ubuntu.com/lookup still works. ** Tags removed: verification-needed verification-needed-cosmic ** Tags added: verification-done verification-done-cosmic -- 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/1822898 Title: wget https://geoip.ubuntu.com/lookup fails in mini.iso d-i Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Cosmic: Fix Committed Status in openssl source package in Disco: Fix Released Status in openssl package in Debian: New Bug description: [Impact] * fetch-url cannot use https protocol (no https preseeds) [Test case] * in d-i, mini.iso, tty try wget https://geoip.ubuntu.com/lookup it should succeed. [Solution] The required openssl.cnf configuration file is missing, needs to simply exists, even if it is empty. [Regression Potential] well, if one cannot download over https / init ssl library in d-i, it's hard to get openssl busted more than that. No code changes on the .deb side of things To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1822898/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1724152] Re: ISST-LTE: pVM: aureport couldn't get the right auid from the audit log on ubuntu16.04
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin16043 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to audit in Ubuntu. https://bugs.launchpad.net/bugs/1724152 Title: ISST-LTE: pVM: aureport couldn't get the right auid from the audit log on ubuntu16.04 Status in The Ubuntu-power-systems project: Fix Released Status in audit package in Ubuntu: Invalid Status in audit source package in Xenial: Fix Released Status in audit source package in Zesty: Won't Fix Bug description: [Impact] The aureport command, part of the audit userspace utilities, incorrectly reports the user id of successful logins. "-1" is printed instead of the expected user id. [Test Case] As root, run `login`. Proceed as follows: 1. Login with a blank username and any password 2. Login with an invalid username and any password 3. Login with a valid username and an invalid password 4. Login with a valid username and a valid password 5. Exit from the login shell 6. Run `aureport -l` and examine the last for login records An unpatched aureport will print the following: # date time auid host term exe success event ... 2. 10/17/2017 23:45:32 UNKNOWN ? /dev/pts/8 /bin/login no 97 3. 10/17/2017 23:45:39 UNKNOWN ? /dev/pts/8 /bin/login no 99 4. 10/17/2017 23:45:45 tyhicks ? /dev/pts/8 /bin/login no 101 5. 10/17/2017 23:45:49 -1 ? /dev/pts/8 /bin/login yes 107 A patch aureport will print the correct output: Login Report # date time auid host term exe success event ... 2. 10/17/2017 23:52:44 UNKNOWN ? /dev/pts/8 /bin/login no 165 3. 10/17/2017 23:52:52 UNKNOWN ? /dev/pts/8 /bin/login no 167 4. 10/17/2017 23:52:58 tyhicks ? /dev/pts/8 /bin/login no 169 5. 10/17/2017 23:53:02 1000 ? /dev/pts/8 /bin/login yes 175 Note the "1000" in the auid column on the #5 row. It should *not* be "-1". [Regression Potential] The regression potential is limited due to the change only affecting a single line of code, the fix comes from upstream, and that the aureport utility is not critical. [Original Report] == Comment: #0 - Miao Tao Feng - 2016-11-23 02:46:25 == When we develop new testcase for audit, we found that command "aureport -l" print out wrong auid "-1" on ubuntu16.04 and it should be 1000 according to the audit.log. The following are details: root@roselp2:~# aureport -l Login Report # date time auid host term exe success event 1. 11/23/2016 02:20:12 -1 10.33.24.118 /dev/pts/0 /usr/sbin/sshd yes 18 The auid "-1" on the above line should be "1000? according to the audit.log. root@roselp2:~# grep ":18" /var/log/audit/audit.log type=USER_LOGIN msg=audit(1479889212.292:18): pid=4177 uid=0 auid=1000 ses=4 msg='op=login id=1000 exe="/usr/sbin/sshd" hostname=10.33.24.118 addr=10.33.24.118 terminal=/dev/pts/0 res=success' root@roselp2:~# dpkg -s auditd Package: auditd Status: install ok installed Priority: extra Section: admin Installed-Size: 1051 Maintainer: Ubuntu Developers Architecture: ppc64el Source: audit Version: 1:2.4.5-1ubuntu2 Depends: lsb-base (>= 3.0-6), mawk | gawk, init-system-helpers (>= 1.18~), libaudit1 (>= 1:2.4.2), libauparse0 (>= 1:2.3.1), libc6 (>= 2.17) Suggests: audispd-plugins root@roselp2:~# uname -a Linux roselp2 4.4.0-47-generic #68-Ubuntu SMP Wed Oct 26 19:38:24 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux root@roselp2:~# service auditd status ? auditd.service - Security Auditing Service Loaded: loaded (/lib/systemd/system/auditd.service; enabled; vendor preset: e Active: active (running) since Wed 2016-11-23 02:19:21 CST; 19s ago Main PID: 4085 (auditd) CGroup: /system.slice/auditd.service ??4085 /sbin/auditd -n Nov 23 02:19:21 roselp2 auditctl[4086]: enabled 0 Nov 23 02:19:21 roselp2 auditctl[4086]: failure 1 Nov 23 02:19:21 roselp2 auditctl[4086]: pid 0 Nov 23 02:19:21 roselp2 auditctl[4086]: rate_limit 0 Nov 23 02:19:21 roselp2 auditctl[4086]: backlog_limit 320 Nov 23 02:19:21 roselp2 auditctl[4086]: lost 0 Nov 23 02:19:21 roselp2 auditctl[4086]: backlog 0 Nov 23 02:19:21 roselp2 auditctl[4086]: backlog_wait_time 15000 Nov 23 02:19:21 roselp2 systemd[1]: Started Security Auditing Service. Nov 23 02:19:21 roselp2 auditd[4085]: Init complete, auditd 2.4.5 listening for Please cherry pick https://github.com/linux-audit/audit- userspace/commit/25097d64344828a80acf681da5c1dacc4ea3c069 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1724152/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1820172] Re: [regression] Python async test fails with OpenSSL 1.1.1b
** No longer affects: openssl (Ubuntu Disco) ** No longer affects: python3.7 (Ubuntu Disco) -- 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/1820172 Title: [regression] Python async test fails with OpenSSL 1.1.1b Status in Python: New Status in openssl package in Ubuntu: New Status in python3.7 package in Ubuntu: New Bug description: Python async test fails with OpenSSL 1.1.1b, after upgrading from 1.1.1. Reported also in the Python tracker. To manage notifications about this bug go to: https://bugs.launchpad.net/python/+bug/1820172/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1642514] Re: sched: Match-all classifier is missing in xenial
** Merge proposal linked:
https://code.launchpad.net/~smb/ubuntu/+source/iproute2/+git/iproute2/+merge/365865
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1642514
Title:
sched: Match-all classifier is missing in xenial
Status in iproute2 package in Ubuntu:
Invalid
Status in linux package in Ubuntu:
Fix Released
Status in iproute2 source package in Xenial:
In Progress
Status in linux source package in Xenial:
Fix Released
Bug description:
This is implemented in linux v4.8 by the following upstream patch:
bf3994d2ed31 ("net/sched: introduce Match-all classifier")
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=bf3994d2ed31
The backport is straightforward. It's useful in combination with
clsact qdisc (see bug #1642510).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1642514/+subscriptions
--
Mailing list: https://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 1773859] Re: upgrades to 18.04 fail
Hola creo recordar que utilicé estos comandos: sudo mv / usr / share / dbus-1 / system- servicios / org.freedesktop .systemd1. servicio / usr / share / dbus-1 / system- servicios / org.freedesktop .systemd1. Servicio. bak sudo apt-get install -f sudo apt dist-upgrade sudo apt autoremove A mi me funcionó correctamente, pero no lo almacené. Puede ser otro problema con el mismo resultado. Otra solución, que apliqué en un laptop fue sacar un back-up de los archivos de usuario, documentos, descargas... Y reinstalar la nueva versión desde 0 Sañudos El jue., 11 abr. 2019 0:45, loluchayjose <1773...@bugs.launchpad.net> escribió: > Bueno, ninguna de las soluciones aquí está muy clara. Una de ellas es > "sudo apt purge gdm etc."... "etc." que? > > Varios dicen "borrar"... borrar como? > > Tu dijiste: "I solved problem sttoping services and erasing systemd-shim > upon console. > After I could updating my pc, also, from console"... Qué servicios > paraste, y como? Tengo que hacerlo en Safe Mode? > > Uno de los últimos dice: "The upload of systemd that was purported to > fix this bug report was superseded by a security update of systemd so > the fix is no longer available." Así que por lo que se ve, esa solucion > ya no sirve. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1792241). > https://bugs.launchpad.net/bugs/1773859 > > Title: > upgrades to 18.04 fail > > Status in systemd package in Ubuntu: > Fix Released > Status in systemd-shim package in Ubuntu: > Won't Fix > Status in systemd source package in Bionic: > Triaged > Status in systemd-shim source package in Bionic: > Won't Fix > Status in systemd source package in Cosmic: > Fix Released > Status in systemd-shim source package in Cosmic: > Won't Fix > > Bug description: > [Impact] > >* Some systems fail to upgrade due to conflicts between systemd and > the (now removed from the archive) systemd-shim / upstart. > >* Instead of trying to work out what's the problem in ordering / > removal of diverts, ensure that systemd is never unpacked whilst > systemd-shim/upstart are still on disk. Thus declare conflicts against > systemd-shim/upstart packages in systemd package. > > [Test Case] > >* monitor drop-off of upgrades with below reported problem > >* Check that it is possible to upgrade to bionic's libpam-systemd > from xenial with systemd-shim installed on xenial, ie. > > lxc launch ubuntu-daily:xenial test-shim-upgrade > lxc exec test-shim-upgrade > apt update > apt install systemd-shim > wget > https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb > apt install ./systemd-shim_10-3_amd64.deb > sed 's/xenial/bionic/' -i /etc/apt/sources.list > apt update > apt install systemd > > this currently passes, however, systemd-shim remains installed. It > should be removed instead. Apt install systemd should have lines like > this: > > The following packages will be REMOVED: > systemd-shim > ... > Removing 'diversion of > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd > by systemd-shim' > ... > > > [Regression Potential] > >* systemd-shim/upstart are both removed and not supported in bionic, > thus forcing their removal via conflicts should bring the system into > an expected state. > > [Other Info] > >* original bug report > > $ sudo apt upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Done > The following packages will be REMOVED: > systemd-shim > 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. > 1 not fully installed or removed. > After this operation, 71.7 kB disk space will be freed. > Do you want to continue? [Y/n] y > (Reading database ... 63 files and directories currently installed.) > Removing systemd-shim (9-1bzr4ubuntu1) ... > Removing 'diversion of > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd > by systemd-shim' > dpkg-divert: error: rename involves overwriting > '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with > different file > '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', > not allowed > dpkg: error processing package systemd-shim (--remove): >subprocess installed post-removal script returned error exit status 2 > Errors were encountered while processing: >systemd-shim > E: Sub-process /usr/bin/dpkg returned an error code (1) > > Commenting out the dpkg-divert in systemd-shim's postrm solved this > for me and I was about to continue the upgrade. > > To manage notifications about this bug go to: > >
[Touch-packages] [Bug 1824342] Re: in 19.04, default user cannot access system journal
** Also affects: systemd (Ubuntu Disco) Importance: High Status: In Progress ** Tags removed: rls-dd-incoming ** Tags added: disco -- 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/1824342 Title: in 19.04, default user cannot access system journal Status in systemd package in Ubuntu: In Progress Status in systemd source package in Disco: In Progress Bug description: in a fresh install of 19.04 from http://cdimage.ubuntu.com/daily- live/20190410/disco-desktop-amd64.iso, journalctl -u snapd, or -u gdm, or -u udisks, results in 'no entries'. journalctl --system -u snapd etc, warns about permissions. $ sudo getfacl /var/log/journal/ getfacl: Removing leading '/' from absolute path names # file: var/log/journal/ # owner: root # group: systemd-journal # flags: -s- user::rwx group::r-x other::r-x default:user::rwx default:group::r-x default:group:adm:r-x default:mask::r-x default:other::r-x this is fixed via sudo setfacl -R -nm g:adm:rx,d:g:adm:rx /var/log/journal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824342/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824384] [NEW] libapparmor not built with -fPIC
Public bug reported: Attempted to build snap-confine with DEB_BUILD_MAINT_OPTIONS = hardening=+pie. The build fails with: mv -f snap-confine/.deps/snap_confine_snap_confine-user-support.Tpo snap-confine/.deps/snap_confine_snap_confine-user-support.Po gcc -Wall -Wextra -Wmissing-prototypes -Wstrict-prototypes -Wno-missing-field-initializers -Wno-unused-parameter -Werror -DLIBEXECDIR=\"/usr/lib/snapd\" -DNATIVE_LIBDIR=\"/usr/lib\" -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z,relro -o snap-confine/snap-confine snap-confine/snap_confine_snap_confine-cookie-support.o snap-confine/snap_confine_snap_confine-mount-support-nvidia.o snap-confine/snap_confine_snap_confine-mount-support.o snap-confine/snap_confine_snap_confine-ns-support.o snap-confine/snap_confine_snap_confine-seccomp-support-ext.o snap-confine/snap_confine_snap_confine-seccomp-support.o snap-confine/snap_confine_snap_confine-snap-confine-args.o snap-confine/snap_confine_snap_confine-snap-confine-invocation.o snap-confine/snap_confine_snap_confine-snap-confine.o snap-confine/snap_confine_snap_confine-udev-support.o snap-confine/snap_confine_snap_confine-user-support.o libsnap-confine-private.a -ludev-Wl,-Bstatic -lcap -lapparmor -Wl,-Bdynamic -pthread /usr/bin/ld: /lib/x86_64-linux-gnu/libapparmor.a(kernel.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC /lib/x86_64-linux-gnu/libapparmor.a: error adding symbols: Bad value collect2: error: ld returned 1 exit status By default, because of snapd reexec support on Ubuntu (and some other distros), snap-confine will try to link a static version libapparmor. It appears that libapparmor object files are built without -fPIC though. ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1824384 Title: libapparmor not built with -fPIC Status in apparmor package in Ubuntu: New Bug description: Attempted to build snap-confine with DEB_BUILD_MAINT_OPTIONS = hardening=+pie. The build fails with: mv -f snap-confine/.deps/snap_confine_snap_confine-user-support.Tpo snap-confine/.deps/snap_confine_snap_confine-user-support.Po gcc -Wall -Wextra -Wmissing-prototypes -Wstrict-prototypes -Wno-missing-field-initializers -Wno-unused-parameter -Werror -DLIBEXECDIR=\"/usr/lib/snapd\" -DNATIVE_LIBDIR=\"/usr/lib\" -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z,relro -o snap-confine/snap-confine snap-confine/snap_confine_snap_confine-cookie-support.o snap-confine/snap_confine_snap_confine-mount-support-nvidia.o snap-confine/snap_confine_snap_confine-mount-support.o snap-confine/snap_confine_snap_confine-ns-support.o snap-confine/snap_confine_snap_confine-seccomp-support-ext.o snap-confine/snap_confine_snap_confine-seccomp-support.o snap-confine/snap_confine_snap_confine-snap-confine-args.o snap-confine/snap_confine_snap_confine-snap-confine-invocation.o snap-confine/snap_confine_snap_confine-snap-confine.o snap-confine/snap_confine_snap_confine-udev-support.o snap-confine/snap_confine_snap_confine-user-support.o libsnap-confine-private.a -ludev-Wl,-Bstatic -lcap -lapparmor -Wl,-Bdynamic -pthread /usr/bin/ld: /lib/x86_64-linux-gnu/libapparmor.a(kernel.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC /lib/x86_64-linux-gnu/libapparmor.a: error adding symbols: Bad value collect2: error: ld returned 1 exit status By default, because of snapd reexec support on Ubuntu (and some other distros), snap-confine will try to link a static version libapparmor. It appears that libapparmor object files are built without -fPIC though. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1824384/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823862] Re: disco: unable to use iptables/enable ufw under -virtual kernel
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1823862 Title: disco: unable to use iptables/enable ufw under -virtual kernel Status in linux package in Ubuntu: Fix Committed Status in ufw package in Ubuntu: Invalid Bug description: SRU Justification Impact: iptables does not work in disco with linux-virtual. Fix: Add bpfilter to the generic inclusion list. Regression Potential: There are no code changes and thus minimal potential for regressions. Test Case: Verify that bpffilter.ko is shipped in linux-modues instead of linux-module-extra and that iptables commands work in disco with the linux-virtual kernel installed. --- Fresh install of disco: $ sudo ufw enable Command may disrupt existing ssh connections. Proceed with operation (y|n)? y ERROR: problem running ufw-init iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad built-in chain name iptables-restore: line 22 failed iptables-restore: line 2 failed iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file or directory Error occurred at line: 30 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No such file or directory Error occurred at line: 19 Try `iptables-restore -h' or 'iptables-restore --help' for more information. iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file or directory Error occurred at line: 2 Try `iptables-restore -h' or 'iptables-restore --help' for more information. Problem running '/etc/ufw/before.rules' Problem running '/etc/ufw/after.rules' ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ufw 0.36-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu26 Architecture: amd64 Date: Tue Apr 9 08:49:59 2019 Ec2AMI: ami-04cf Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.blue Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ufw UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823862/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (crash in xorg before using "foreign grub")
okay I stumbled across something .. the network install .. used netplan to set-up my wifi connection to start on boot .. so as soon as systemd networkd starts wifi is started NetworkManager thus has no access or anyway to try for other networks.. so I tried to change this.. If I edit the config files to give exclusive control to NetworkManager ..run netplan apply as long as I don't reboot I can use NetworkManager as per normal As soon as I try to reboot back into the install (via and foreign grub as defined above) I get exactly the same crash pattern as before .. so the deduction is that netplan configuration problems are causing the plymouth/xorg issues when you use only NetworkManager as a renderer .. so I am altering the title here again ** Summary changed: - lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (crash in xorg before using "foreign grub") + lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (crash in xorg before using "foreign grub") netplan mis-configuration maybe underlying cause. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1821609 Title: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (crash in xorg before using "foreign grub") netplan mis-configuration maybe underlying cause. Status in lightdm package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Invalid Bug description: Okay the has happened recently at least since march 18, 2019 iso and march 22, 2019 iso are both effected very similar to one of my previously reported bugs .. which was related to xorg not being installed .. back ground .. PC is lenovo sl 500 with evo860 SSD drive 3 partions contain installs of disco sda1 -- main working system -- I usually install grub from here as master .. sda6 and sda7 are test installs of disco daily iso's 03-18-2019, 03-22-2019 repectively on the test installs as long as the iso is using the grub boot loader installed from that install the system will boot normally .. the display manger tends to flicker on and off but does final start and login can proceed. but if another install re-installs grub as master the display manager fails to stay active or even come-up for sda6 or sda7 only if their own grubs are reinstalled will they work normally sda1 display manager/xorg login works always no matter which "grub- source" is in control. if I use rescue boot from any grub as master I can get the displays to work by running dpkg fix which does nothing .. and then resuming the boot .. then things work normally.. if the "non-rescue" boots are used the screen/computer locks and only a power down and reboot gives access. (sometime requiring radical depowering .. unpluging and removing battery) now the is a message that appears that RCs??? level is missing. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu11 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Mar 25 11:25:58 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2019-03-23 (1 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322) MachineType: LENOVO 2746CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6AET64WW dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 2746CTO dmi.board.vendor: LENOVO dmi.board.version: LENOVO 6AET64WW dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LENOVO 6AET64WW dmi.modalias: dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
[Touch-packages] [Bug 1824342] Re: in 19.04, default user cannot access system journal
** Changed in: systemd (Ubuntu) Status: New => In Progress -- 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/1824342 Title: in 19.04, default user cannot access system journal Status in systemd package in Ubuntu: In Progress Bug description: in a fresh install of 19.04 from http://cdimage.ubuntu.com/daily- live/20190410/disco-desktop-amd64.iso, journalctl -u snapd, or -u gdm, or -u udisks, results in 'no entries'. journalctl --system -u snapd etc, warns about permissions. $ sudo getfacl /var/log/journal/ getfacl: Removing leading '/' from absolute path names # file: var/log/journal/ # owner: root # group: systemd-journal # flags: -s- user::rwx group::r-x other::r-x default:user::rwx default:group::r-x default:group:adm:r-x default:mask::r-x default:other::r-x this is fixed via sudo setfacl -R -nm g:adm:rx,d:g:adm:rx /var/log/journal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824342/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783298] Re: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work
The slowness might have caused by some apparmor probs: pr 11 15:16:58 zander kernel: [13422.621558] audit: type=1400 audit(1554988618.771:27): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=13888 comm="ipp" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Apr 11 15:20:43 zander kernel: [13647.282091] audit: type=1400 audit(1554988843.431:28): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=20908 comm="ipp" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Apr 11 15:25:43 zander kernel: [13947.374877] audit: type=1400 audit(1554989143.520:29): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=27940 comm="ipp" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Apr 11 15:28:24 zander kernel: [14108.309867] audit: type=1400 audit(1554989304.459:30): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=424 comm="ipp" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Apr 11 15:28:46 zander kernel: [14130.333125] audit: type=1400 audit(1554989326.483:31): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=1116 comm="ipp" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Apr 11 15:43:00 zander kernel: [14984.432581] audit: type=1400 audit(1554990180.581:32): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=26456 comm="ipp" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Apr 11 15:43:03 zander kernel: [14987.725323] audit: type=1400 audit(1554990183.873:33): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=26546 comm="ipp" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Apr 11 15:43:05 zander kernel: [14989.287668] audit: type=1400 audit(1554990185.433:34): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=26584 comm="ipp" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Apr 11 15:43:06 zander kernel: [14990.386287] audit: type=1400 audit(1554990186.533:35): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=26610 comm="ipp" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Apr 11 15:54:37 zander dbus-daemon[859]: [system] Activating service name='org.opensuse.CupsPkHelper.Mechanism' requested by ':1.167' (uid=1000 pid=14054 comm="/usr/bin/python3 /usr/share/system-config-printer/" label="unconfined") (using servicehelper) Apr 11 15:54:37 zander dbus-daemon[859]: [system] Successfully activated service 'org.opensuse.CupsPkHelper.Mechanism' Apr 11 15:55:43 zander kernel: [15747.355081] audit: type=1400 audit(1554990943.501:36): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=15434 comm="ipp" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Apr 11 15:58:20 zander kernel: [15904.185434] audit: type=1400 audit(1554991100.336:37): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=21257 comm="apparmor_parser" Apr 11 15:58:20 zander kernel: [15904.185716] audit: type=1400 audit(1554991100.336:38): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="/usr/sbin/cupsd" pid=21257 comm="apparmor_parser" Did aa-disable cupsd and it seems faster. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1783298 Title: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work Status in CUPS: Fix Released Status in cups package in Ubuntu: Fix Released Status in cups source package in Bionic: Fix Released Status in cups source package in Cosmic: Fix Released Status in cups source package in Disco: Fix Released Bug description: [Impact] If a print queue is set up with "auth-info-required=negotiate" because the server requires authentication (for example Kerberos) the user is asked for user name and password on every join, instead of the authentication working automatically. This worked correctly in 14.04 and 16.04. Also setting "AuthType Default" for "/" in cupsd.conf leads to be prompted for a password on commands like "lpatat -a", even for root. Works correctly in Xenial and Cosmic. [Test Case] Set up a queue pointing to a Kerberos-authenticated Windows server with "lpadmin ... -o auth-info-required=negotiate ..." OR set "AuthType Default" for "/" in cupsd.conf. When printing or running other commands accessing your print queue you will get prompted for credentials. With the fix the authentication will get automatic again. [Regression Potential] Low, as the fix are simple one-line corrections taken from upstream. [Original report] Hi, We have our printers configured to print to a Windows print server. In
[Touch-packages] [Bug 1823306] Re: lxqt-sudo added to Exec line of software-properties-qt.desktop breaks use in KDE Plasma Discover
This bug was fixed in the package software-properties - 0.97.10 --- software-properties (0.97.10) disco; urgency=medium * Remove lxqt-sudo from exec line in software-properties-qt.desktop (LP: #1823306) * Make invisible software-properties-qt.desktop * Create software-properties-lxqt.desktop with lxqt-sudo and shown only in LXQt * Rename software-properties-drivers-qt.desktop to software-properties-drivers-lxqt.desktop -- Hans P Möller Wed, 10 Apr 2019 16:38:53 -0400 ** Changed in: software-properties (Ubuntu Disco) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1823306 Title: lxqt-sudo added to Exec line of software-properties-qt.desktop breaks use in KDE Plasma Discover Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Disco: Fix Released Bug description: In the upload: https://launchpad.net/ubuntu/+source/software- properties/0.97.8 there is a change in the software-properties-qt.desktop files which is (a) not documented in the changelog, and (b) not communicated to other flavour users of this application (Kubuntu in this case). -Exec=software-properties-qt +Exec=lxqt-sudo software-properties-qt This results in Plasma Discover not being able to launch software- properties-qt, as it uses privilege elevation via kdesu of whatever is in the Exec line, and lxqt-sudo added there makes this fail. Context to this is: For Cosmic release Lubuntu developers requested agreement from Kubuntu to the porting of the software-properties-kde package to pure Qt, so that it could be used in both Kubuntu and Lubuntu (lxqt) without pulling a lot of KDE dependencies into Lubuntu's lqxt images/installs. This was on the condition that despite being renamed to -qt, it remained completely as a tool for joint usage between the two flavours. The original sofware-properties-kde was meant to be launched by applications and was set not to show in DE menus by default. It seems that Lubuntu wishes to now have it useable directly from a 'start'/'search' menu, hence making it visible and adding the lxqt- sudo in the Exec line to facilitate launch with privilege escalation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1823306/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823432] Re: openexr ftbfs in disco (i386 only)
This bug was fixed in the package openexr - 2.2.1-4.1
---
openexr (2.2.1-4.1) unstable; urgency=medium
* Non-maintainer upload.
* bug909865.patch: Add -ffloat-store when compiling tests, to fix test
failures on i386. Patch backported from experimental. (Closes: #909865)
-- Steinar H. Gunderson Wed, 20 Mar 2019 22:40:43
+0100
** Changed in: openexr (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openexr in Ubuntu.
https://bugs.launchpad.net/bugs/1823432
Title:
openexr ftbfs in disco (i386 only)
Status in openexr package in Ubuntu:
Fix Released
Status in openexr source package in Disco:
Fix Released
Bug description:
https://launchpadlibrarian.net/417924506/buildlog_ubuntu-
disco-i386.openexr_2.2.1-4build1_BUILDING.txt.gz
compression 7, x sampling 2, y sampling 2: writing reading comparing
compression 8, x sampling 2, y sampling 2: writing reading comparing
compression 9, x sampling 2, y sampling 2: writing reading comparing
random bits
compression 0, x sampling 1, y sampling 1: writing reading
comparingIlmImfTest: testCompression.cpp:330: void {anonymous}::writeRead(const
Imf_2_2::Array2D&, const Imf_2_2::Array2D&, const
Imf_2_2::Array2D&, const char*, int, int, int, int,
Imf_2_2::Compression, int, int): Assertion `equivalent (pf1[y][x], pf2[y][x],
comp)' failed.
FAIL IlmImfTest (exit status: 134)
Testsuite summary for OpenEXR 2.2.1
# TOTAL: 1
# PASS: 0
# SKIP: 0
# XFAIL: 0
# FAIL: 1
# XPASS: 0
# ERROR: 0
See IlmImfTest/test-suite.log
make[5]: *** [Makefile:966: test-suite.log] Error 1
make[5]: Leaving directory '/<>/IlmImfTest'
make[4]: *** [Makefile:1074: check-TESTS] Error 2
make[4]: Leaving directory '/<>/IlmImfTest'
make[3]: *** [Makefile:1148: check-am] Error 2
make[3]: Leaving directory '/<>/IlmImfTest'
make[2]: *** [Makefile:498: check-recursive] Error 1
make[2]: Leaving directory '/<>'
dh_auto_test: make -j4 check VERBOSE=1 returned exit code 2
make[1]: *** [debian/rules:16: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:25: build-arch] Error 2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openexr/+bug/1823432/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783298] Re: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work
I have a situation that is similar but not with a windows server. I have an experimental server which is installed with Ubuntu Disco. Queues are authenticated with kerberos. This is IPP-Everywhere queues. I have a client with Ubuntu 18.04.2 LTS. Printing did not work with cups-2.2.7-1ubuntu2.4 on the client. Same symptoms as described here, cannot print, authentication prompt despite valid kerberos tickets. I compiled upstream cups 2.2.7 with Eskos fix-password-prompt.patch AND the kerberos truncate patch from #13 and installed it on the client. It works, but printing is very slow, at least from firefox. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1783298 Title: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work Status in CUPS: Fix Released Status in cups package in Ubuntu: Fix Released Status in cups source package in Bionic: Fix Released Status in cups source package in Cosmic: Fix Released Status in cups source package in Disco: Fix Released Bug description: [Impact] If a print queue is set up with "auth-info-required=negotiate" because the server requires authentication (for example Kerberos) the user is asked for user name and password on every join, instead of the authentication working automatically. This worked correctly in 14.04 and 16.04. Also setting "AuthType Default" for "/" in cupsd.conf leads to be prompted for a password on commands like "lpatat -a", even for root. Works correctly in Xenial and Cosmic. [Test Case] Set up a queue pointing to a Kerberos-authenticated Windows server with "lpadmin ... -o auth-info-required=negotiate ..." OR set "AuthType Default" for "/" in cupsd.conf. When printing or running other commands accessing your print queue you will get prompted for credentials. With the fix the authentication will get automatic again. [Regression Potential] Low, as the fix are simple one-line corrections taken from upstream. [Original report] Hi, We have our printers configured to print to a Windows print server. In Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup seems to be acting more like AuthInfoRequired username,password i.e. it prompts for a password when printing rather than using the available Kerberos credentials. We are using an unaltered cupsd.conf file and are adding printers with the following command: lpadmin -p "printer" -D "Printer" -L "room" -v "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4 -o printer-error-policy=abort-job -o auth-info-required=negotiate -m "CIS/hp-officejet_pro_476_576_series-ps.ppd" the smb backend has been linked to /usr/lib/x86_64-linux- gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile as it's blocked by default) and the permissions on this file changed to 700 (owner root) as per manpage instructions. When using lp -d printer /tmp/test.txt I get the following response: Password for myuid on localhost? Typing my password gets the job accepted to the queue but it does spool to the Windows Print Server and in the error_log file I can see D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_INFO_REQUIRED=negotiate D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0 D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set As I said earlier this all works perfectly on Xenial and Trusty. (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 10.13) Any ideas how to fix this? Thanks, Ian. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 24 10:03:57 2018 InstallationDate: Installed on 2018-06-22 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 790 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0HY9JP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Touch-packages] [Bug 1824342] Re: in 19.04, default user cannot access system journal
Ok, this is fixed in v240-stable branch by https://github.com/systemd /systemd-stable/commit/5b3437338286fde71f66952726840ba7dbdd86b4 But v240-stable branch has many other useful fixes let me try to land them all. -- 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/1824342 Title: in 19.04, default user cannot access system journal Status in systemd package in Ubuntu: New Bug description: in a fresh install of 19.04 from http://cdimage.ubuntu.com/daily- live/20190410/disco-desktop-amd64.iso, journalctl -u snapd, or -u gdm, or -u udisks, results in 'no entries'. journalctl --system -u snapd etc, warns about permissions. $ sudo getfacl /var/log/journal/ getfacl: Removing leading '/' from absolute path names # file: var/log/journal/ # owner: root # group: systemd-journal # flags: -s- user::rwx group::r-x other::r-x default:user::rwx default:group::r-x default:group:adm:r-x default:mask::r-x default:other::r-x this is fixed via sudo setfacl -R -nm g:adm:rx,d:g:adm:rx /var/log/journal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824342/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824097] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2019-04-11 09:02 EDT--- IBM bugzilla status -< closed, patches are already in 2.32 package. Many thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1824097 Title: [Ubuntu] Patches on top of binutils 2.32 Status in Ubuntu on IBM z Systems: Fix Released Status in binutils package in Ubuntu: Fix Released Bug description: [Impact] * Instructions change in z13 abi [Test Case] * Testsuite adjusted, and should pass. [Regression Potential] * Without these patches assembly/dissambly of code that uses renamed instructions will fail (z13+ abi) [Other Info] * Original request. Following patches have to be applied to binutils 2.32 - S/390: arch13: Adjust to recent changes commit e49edb49713e435b8441bb5a9bd0c10d9df84e2f - S/390: arch13: Add instruction descriptions commit d98eed0923af29043ce18da43d2a242191d44ceb - Revert "Add support to GNU ld to separate got related plt entries" commit 9db2b33d363e2047df53f89ad34e7d1104299d12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1824097/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824227] Re: console-setup failure due to race with systemd-tmpfiles
** Tags added: id-5cae47869ef68677a65c1e71 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1824227 Title: console-setup failure due to race with systemd-tmpfiles Status in console-setup package in Ubuntu: Fix Released Status in console-setup source package in Xenial: Fix Committed Status in console-setup source package in Bionic: Fix Committed Status in console-setup source package in Cosmic: Fix Committed Status in console-setup source package in Disco: Fix Released Bug description: [SRU Justification] I'm seeing a console-setup.service failure quite regularly in testing where the temp file that should have been created can't be found. This is a regular xenial cloud image. 19:51:13 systemd-tmpfiles[485]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. ... 19:51:13 systemd[1]: Starting Set console font and keymap... 19:51:15 setupcon[455]: /bin/setupcon: 809: /bin/setupcon: cannot open /tmp/tmpkbd.a8FGSs: No such file 19:51:15 systemd[1]: console-setup.service: Main process exited, code=exited, status=1/FAILURE 19:51:15 systemd[1]: Failed to start Set console font and keymap. 19:51:15 systemd[1]: console-setup.service: Unit entered failed state. 19:51:15 systemd[1]: console-setup.service: Failed with result 'exit-code'. ... /bin/setupcon has a lovely tempfile function that looks like: if \ TMPFILE=`mktemp /tmp/tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp /run/tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp /dev/.tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp /lib/init/rw/tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp 2>/dev/null` Here's our edited IRC conversation on the bug: <@vorlon> so I do think you're being hit by the tmp cleaner <@vorlon> also this seems like bad pathological default behavior for the tmp cleaner, to delete files that have just been created <@vorlon> but we should fix console-setup to not rely on /tmp <@vorlon> and I prefer that we do that instead of trying to fiddle with the ordering of the systemd units on startup <@vorlon> i.e. console-setup has an undeclared dependency on systemd-tmpfiles-clean; let's remove the dependency instead of declaring it <@vorlon> are you failing the race more often now than in the past? <@rcj>vorlon: it feels like it's failing more often but I don't have data to answer that. <@vorlon> are we shipping an image with a dirty rootfs? <@vorlon> dirty in the sense that e2fsck doesn't take one look at it, say "yep, nothing to do here" and exit <@vorlon> in the sense that this is what would make dev-sda1.device slow to complete AIUI <@rcj>would filesystem resize on first boot mark it dirty? Because that will happen <@vorlon> huh good question <@vorlon> it might rcj, unclean shutdown? <@rcj>xnox: first boot [Test case] 1. Install console-setup from -proposed 2. Reboot 3. Verify that `systemctl status console-setup` shows that the service has completed successfully. Since this is a race, additional fuzz testing may be warranted for the cloud images to confirm that the issue experienced in GCE is really fixed. However, that should not block promotion of this SRU fix since there definitely is a race here that should be fixed per se even if there are other issues still causing a failure in GCE. [Regression potential] None known. /run is guaranteed to be mounted rw very early in boot - generally before /tmp is mounted, due to /tmp being on the rootfs that needs to be fscked before remount. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: console-setup 1.108ubuntu15.4 ProcVersionSignature: User Name 4.15.0-1029.31~16.04.1-gcp 4.15.18 Uname: Linux 4.15.0-1029-gcp x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Apr 10 19:24:12 2019 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: console-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1824227/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824341] Re: NoAllowedOrigin cause package removal
full log that removed packages that shouldn't ** Description changed: unattended-upgrades remove packages that shouldn't when there is a NoAllowedOrigin exception. Version: unattended-upgrades=1.1ubuntu1.18.04.10 Ubuntu 18.04.2 LTS Description of problem: We have a internal package cliente-ldap that depends on samba, when u-u check for upgrade samba-common it raise a NoAllowedOrigin exception, then it doesn't clear apt.cache and it removes packages that shouldn't. - Log of dry-run with the problem: - $ sudo unattended-upgrade -d --dry-run + Log that happens package removal: + $ sudo unattended-upgrade -d [...] - Option --dry-run given, *not* performing real actions Packages that will be upgraded: libsmbclient libwbclient0 python-samba samba samba-common samba-common-bin samba-dsdb-modules samba-libs samba-vfs-modules smbclient Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log debug: call_adjusted samba-common debug: marked_pkg: samba: install=False, upgrade=False, delete=True debug: marked_pkg: cliente-ldap: install=False, upgrade=False, delete=True Traceback (most recent call last): - File "/usr/bin/unattended-upgrade", line 257, in call_adjusted - self.allowed_origins) - File "/usr/bin/unattended-upgrade", line 764, in ver_in_allowed_origin - raise NoAllowedOriginError() + File "/usr/bin/unattended-upgrade", line 257, in call_adjusted + self.allowed_origins) + File "/usr/bin/unattended-upgrade", line 764, in ver_in_allowed_origin + raise NoAllowedOriginError() NoAllowedOriginError debug: marked_pkg: samba-common: install=False, upgrade=True, delete=False debug: marked_pkg: smbclient: install=False, upgrade=False, delete=True debug: marked_pkg: samba-common-bin: install=False, upgrade=False, delete=True - Exception: + Exception: marking samba-common-bin for removal Keeping auto-removable samba-common-bin package(s) because it would also remove the following packages which should be kept in this step: samba-common + marking cliente-ldap for removal + (Reading database ... 213413 files and directories currently installed.) + Removing cliente-ldap (1:2.17.15) ... + marking libcephfs2 for removal + (Reading database ... 213392 files and directories currently installed.) + Removing libcephfs2 (12.2.11-0ubuntu0.18.04.1) ... + Processing triggers for libc-bin (2.27-3ubuntu1) ... + marking ldap-auth-config for removal + (Reading database ... 213386 files and directories currently installed.) + Removing libpam-ldap:amd64 (186-4ubuntu1) ... + Removing ldap-auth-config (0.5.3) ... + Removing ldap-auth-client (0.5.3) ... + Processing triggers for man-db (2.8.3-2ubuntu0.1) ... + marking python-samba for removal + (Reading database ... 213332 files and directories currently installed.) + Removing samba (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ... + Removing samba-common-bin (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ... + Removing python-samba (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ... + Processing triggers for libc-bin (2.27-3ubuntu1) ... + Processing triggers for man-db (2.8.3-2ubuntu0.1) ... + marking nss-updatedb for removal + (Reading database ... 212865 files and directories currently installed.) + Removing nss-updatedb (10-3build1) ... + Processing triggers for man-db (2.8.3-2ubuntu0.1) ... + marking samba-vfs-modules for removal + (Reading database ... 212859 files and directories currently installed.) + Removing samba-vfs-modules (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ... + Processing triggers for libc-bin (2.27-3ubuntu1) ... + Processing triggers for man-db (2.8.3-2ubuntu0.1) ... + marking librados2 for removal + (Reading database ... 212770 files and directories currently installed.) + Removing librados2 (12.2.11-0ubuntu0.18.04.1) ... + Processing triggers for libc-bin (2.27-3ubuntu1) ... + marking libibverbs1 for removal + (Reading database ... 212761 files and directories currently installed.) + Removing ibverbs-providers:amd64 (17.1-1ubuntu0.1) ... + Removing libibverbs1:amd64 (17.1-1ubuntu0.1) ... + Processing triggers for libc-bin (2.27-3ubuntu1) ... + marking libpam-mount for removal + (Reading database ... 212731 files and directories currently installed.) + Removing libpam-mount (2.16-3ubuntu0.1) ... + Processing triggers for sgml-base (1.29) ... + Processing triggers for libc-bin (2.27-3ubuntu1) ... + Processing triggers for man-db (2.8.3-2ubuntu0.1) ... + marking ibverbs-providers for removal marking tdb-tools for removal - Keeping auto-removable tdb-tools package(s) because it would also remove the following packages which should be kept in this step: samba-common - marking ibverbs-providers for removal + (Reading database ... 212691 files and directories currently installed.) + Removing tdb-tools (1.3.15-2) ... + Processing triggers for man-db (2.8.3-2ubuntu0.1) ... + marking samba-dsdb-modules for removal + (Reading database ... 212680 files and directories currently installed.) + Removing samba-dsdb-modules
[Touch-packages] [Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability
Uploaded as https://launchpad.net/ubuntu/+source/gtk+3.0/3.24.8-1ubuntu1 ** Changed in: gtk+3.0 (Ubuntu) Status: In Progress => Fix Committed -- 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/1763520 Title: after upgrade to bionic, printing fails without explanation / logs / debuggability Status in gtk+3.0 package in Ubuntu: Fix Committed Status in gtk+3.0 source package in Bionic: In Progress Status in gtk+3.0 source package in Cosmic: In Progress Bug description: [Impact] The problem occurs when the printer's driver package is updated and with this the PPD is replaced and one of the default settings of the queue is not available any more in the new PPD file. Then the setting is prefixed with "Custom." and with this the jobs fail. See comment #15 for more info. [Test Case] - Create a print queue with a PPD. - evince an arbitrary PDF file - Click the print icon - In the print dialog choose the newly created queue and choose some uncommon paper size (not custom). Click "Print". - Check /var/log/cups/error_log, the page size gets correctly received. - Close evince. - Stop CUPS, edit the PPD file removing the paper size you have selected for your job in the PageSize, PageRegion, PaperDimension, and ImageableArea lines. - Start CUPS. - Open the same PDF file again with evince, click Print and then select "Print" in the print dialog without changing anything. - The job fails, in /var/log/cups/error_log you see that the page size is prefixed with "Custom.". With the fixed package installed the job will print. [Regression Potential] The change applies only to saved settings of the print dialog not matching with any of the settings available in the PPD file. In rare cases the fix could fail by mis-understanding the setting and this way not being effective. For options which do not support setting custom values (the vast majority) the patch should always prevent a job failure though. [Other Info] Complete info about the bug and the fix in comment #15, Original bug description: I am unable to print to my network-attached printer after upgrade to bionic. ps shows: lp 26047 0.0 0.0 91668 5756 ?S15:06 0:00 \_ HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 lp 26050 0.1 0.0 0 0 ?Z15:06 0:00 | \_ [gs] lp 26048 0.0 0.0 79908 3836 ?S15:06 0:00 \_ HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 root 26049 0.0 0.0 84388 6192 ?S15:06 0:00 \_ ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 Note the un-reaped gs process. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2 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-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 12 15:07:49 2018 InstallationDate: Installed on 2010-09-24 (2757 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) MachineType: LENOVO 2306CTO Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-03-21 (21 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO
[Touch-packages] [Bug 1824341] Re: NoAllowedOrigin cause package removal
** Description changed: unattended-upgrades remove packages that shouldn't when there is a NoAllowedOrigin exception. Version: unattended-upgrades=1.1ubuntu1.18.04.10 Ubuntu 18.04.2 LTS Description of problem: We have a internal package cliente-ldap that depends on samba, when u-u check for upgrade samba-common it raise a NoAllowedOrigin exception, then it doesn't clear apt.cache and it removes packages that shouldn't. Log of dry-run with the problem: $ sudo unattended-upgrade -d --dry-run [...] Option --dry-run given, *not* performing real actions Packages that will be upgraded: libsmbclient libwbclient0 python-samba samba samba-common samba-common-bin samba-dsdb-modules samba-libs samba-vfs-modules smbclient Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log debug: call_adjusted samba-common debug: marked_pkg: samba: install=False, upgrade=False, delete=True debug: marked_pkg: cliente-ldap: install=False, upgrade=False, delete=True Traceback (most recent call last): - File "/usr/bin/unattended-upgrade", line 259, in call_adjusted - self.allowed_origins) - File "/usr/bin/unattended-upgrade", line 777, in ver_in_allowed_origin - raise NoAllowedOriginError() + File "/usr/bin/unattended-upgrade", line 257, in call_adjusted + self.allowed_origins) + File "/usr/bin/unattended-upgrade", line 764, in ver_in_allowed_origin + raise NoAllowedOriginError() NoAllowedOriginError debug: marked_pkg: samba-common: install=False, upgrade=True, delete=False debug: marked_pkg: smbclient: install=False, upgrade=False, delete=True debug: marked_pkg: samba-common-bin: install=False, upgrade=False, delete=True - Exception: + Exception: marking samba-common-bin for removal Keeping auto-removable samba-common-bin package(s) because it would also remove the following packages which should be kept in this step: samba-common marking tdb-tools for removal Keeping auto-removable tdb-tools package(s) because it would also remove the following packages which should be kept in this step: samba-common marking ibverbs-providers for removal marking python-dnspython for removal marking librados2 for removal marking ldap-auth-client for removal marking ldap-auth-config for removal marking python-tdb for removal marking libhx28 for removal marking libcephfs2 for removal marking nscd for removal marking smbclient for removal marking cliente-ldap for removal marking libnss-db for removal marking samba-vfs-modules for removal marking samba-dsdb-modules for removal marking libpam-mount for removal marking libpam-ldap for removal marking nss-updatedb for removal marking python-samba for removal marking auth-client-config for removal marking python-ldb for removal marking libnss-ldap for removal marking python-crypto for removal marking samba for removal marking libibverbs1 for removal marking attr for removal marking libpam-ccreds for removal - Packages that were successfully auto-removed: + Packages that were successfully auto-removed: Packages that are kept back: samba-common-bin tdb-tools InstCount=0 DelCount=0 BrokenCount=0 Log of what should happen: $ sudo unattended-upgrade -d --dry-run [...] Option --dry-run given, *not* performing real actions Packages that will be upgraded: libsmbclient libwbclient0 python-samba samba samba-common samba-common-bin samba-dsdb-modules samba-libs samba-vfs-modules smbclient Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log debug: call_adjusted samba-common debug: marked_pkg: samba: install=False, upgrade=False, delete=True - debug: marked_pkg: cliente-ldap: install=False, upgrade=True, delete=False + debug: marked_pkg: cliente-ldap: install=False, upgrade=False, delete=False Traceback (most recent call last): - File "/usr/bin/unattended-upgrade", line 259, in call_adjusted + File "/usr/bin/unattended-upgrade", line 257, in call_adjusted self.allowed_origins) - File "/usr/bin/unattended-upgrade", line 775, in ver_in_allowed_origin + File "/usr/bin/unattended-upgrade", line 764, in ver_in_allowed_origin raise NoAllowedOriginError() NoAllowedOriginError debug: marked_pkg: samba-common: install=False, upgrade=True, delete=False debug: marked_pkg: smbclient: install=False, upgrade=False, delete=True debug: marked_pkg: samba-common-bin: install=False, upgrade=False, delete=True debug: call_adjusted libsmbclient debug: marked_pkg: python-samba: install=False, upgrade=True, delete=False debug: marked_pkg: libwbclient0: install=False, upgrade=True, delete=False debug: marked_pkg: samba: install=False, upgrade=True, delete=False debug: marked_pkg: samba-dsdb-modules: install=False, upgrade=True, delete=False debug: marked_pkg: samba-libs: install=False, upgrade=True, delete=False debug: marked_pkg: samba-common: install=False, upgrade=True, delete=False
[Touch-packages] [Bug 1824341] Re: NoAllowedOrigin cause package removal
The attachment "fix clear cache on exception" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1824341 Title: NoAllowedOrigin cause package removal Status in unattended-upgrades package in Ubuntu: New Bug description: unattended-upgrades remove packages that shouldn't when there is a NoAllowedOrigin exception. Version: unattended-upgrades=1.1ubuntu1.18.04.10 Ubuntu 18.04.2 LTS Description of problem: We have a internal package cliente-ldap that depends on samba, when u-u check for upgrade samba-common it raise a NoAllowedOrigin exception, then it doesn't clear apt.cache and it removes packages that shouldn't. Log that happens package removal: $ sudo unattended-upgrade -d [...] Packages that will be upgraded: libsmbclient libwbclient0 python-samba samba samba-common samba-common-bin samba-dsdb-modules samba-libs samba-vfs-modules smbclient Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log debug: call_adjusted samba-common debug: marked_pkg: samba: install=False, upgrade=False, delete=True debug: marked_pkg: cliente-ldap: install=False, upgrade=False, delete=True Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 257, in call_adjusted self.allowed_origins) File "/usr/bin/unattended-upgrade", line 764, in ver_in_allowed_origin raise NoAllowedOriginError() NoAllowedOriginError debug: marked_pkg: samba-common: install=False, upgrade=True, delete=False debug: marked_pkg: smbclient: install=False, upgrade=False, delete=True debug: marked_pkg: samba-common-bin: install=False, upgrade=False, delete=True Exception: marking samba-common-bin for removal Keeping auto-removable samba-common-bin package(s) because it would also remove the following packages which should be kept in this step: samba-common marking cliente-ldap for removal (Reading database ... 213413 files and directories currently installed.) Removing cliente-ldap (1:2.17.15) ... marking libcephfs2 for removal (Reading database ... 213392 files and directories currently installed.) Removing libcephfs2 (12.2.11-0ubuntu0.18.04.1) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... marking ldap-auth-config for removal (Reading database ... 213386 files and directories currently installed.) Removing libpam-ldap:amd64 (186-4ubuntu1) ... Removing ldap-auth-config (0.5.3) ... Removing ldap-auth-client (0.5.3) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... marking python-samba for removal (Reading database ... 213332 files and directories currently installed.) Removing samba (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ... Removing samba-common-bin (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ... Removing python-samba (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... marking nss-updatedb for removal (Reading database ... 212865 files and directories currently installed.) Removing nss-updatedb (10-3build1) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... marking samba-vfs-modules for removal (Reading database ... 212859 files and directories currently installed.) Removing samba-vfs-modules (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... marking librados2 for removal (Reading database ... 212770 files and directories currently installed.) Removing librados2 (12.2.11-0ubuntu0.18.04.1) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... marking libibverbs1 for removal (Reading database ... 212761 files and directories currently installed.) Removing ibverbs-providers:amd64 (17.1-1ubuntu0.1) ... Removing libibverbs1:amd64 (17.1-1ubuntu0.1) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... marking libpam-mount for removal (Reading database ... 212731 files and directories currently installed.) Removing libpam-mount (2.16-3ubuntu0.1) ... Processing triggers for sgml-base (1.29) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... marking ibverbs-providers for removal marking tdb-tools for removal (Reading database ... 212691 files and directories currently installed.) Removing tdb-tools (1.3.15-2) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... marking samba-dsdb-modules for removal (Reading database ... 212680 files
[Touch-packages] [Bug 1824342] Re: in 19.04, default user cannot access system journal
fixed in v241 shame I did not upgrade systemd to v241 in disco. -- 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/1824342 Title: in 19.04, default user cannot access system journal Status in systemd package in Ubuntu: New Bug description: in a fresh install of 19.04 from http://cdimage.ubuntu.com/daily- live/20190410/disco-desktop-amd64.iso, journalctl -u snapd, or -u gdm, or -u udisks, results in 'no entries'. journalctl --system -u snapd etc, warns about permissions. $ sudo getfacl /var/log/journal/ getfacl: Removing leading '/' from absolute path names # file: var/log/journal/ # owner: root # group: systemd-journal # flags: -s- user::rwx group::r-x other::r-x default:user::rwx default:group::r-x default:group:adm:r-x default:mask::r-x default:other::r-x this is fixed via sudo setfacl -R -nm g:adm:rx,d:g:adm:rx /var/log/journal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824342/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824227] Re: console-setup failure due to race with systemd-tmpfiles
** Tags added: id-5caba54405de185b64adc2db -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1824227 Title: console-setup failure due to race with systemd-tmpfiles Status in console-setup package in Ubuntu: Fix Released Status in console-setup source package in Xenial: Fix Committed Status in console-setup source package in Bionic: Fix Committed Status in console-setup source package in Cosmic: Fix Committed Status in console-setup source package in Disco: Fix Released Bug description: [SRU Justification] I'm seeing a console-setup.service failure quite regularly in testing where the temp file that should have been created can't be found. This is a regular xenial cloud image. 19:51:13 systemd-tmpfiles[485]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. ... 19:51:13 systemd[1]: Starting Set console font and keymap... 19:51:15 setupcon[455]: /bin/setupcon: 809: /bin/setupcon: cannot open /tmp/tmpkbd.a8FGSs: No such file 19:51:15 systemd[1]: console-setup.service: Main process exited, code=exited, status=1/FAILURE 19:51:15 systemd[1]: Failed to start Set console font and keymap. 19:51:15 systemd[1]: console-setup.service: Unit entered failed state. 19:51:15 systemd[1]: console-setup.service: Failed with result 'exit-code'. ... /bin/setupcon has a lovely tempfile function that looks like: if \ TMPFILE=`mktemp /tmp/tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp /run/tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp /dev/.tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp /lib/init/rw/tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp 2>/dev/null` Here's our edited IRC conversation on the bug: <@vorlon> so I do think you're being hit by the tmp cleaner <@vorlon> also this seems like bad pathological default behavior for the tmp cleaner, to delete files that have just been created <@vorlon> but we should fix console-setup to not rely on /tmp <@vorlon> and I prefer that we do that instead of trying to fiddle with the ordering of the systemd units on startup <@vorlon> i.e. console-setup has an undeclared dependency on systemd-tmpfiles-clean; let's remove the dependency instead of declaring it <@vorlon> are you failing the race more often now than in the past? <@rcj>vorlon: it feels like it's failing more often but I don't have data to answer that. <@vorlon> are we shipping an image with a dirty rootfs? <@vorlon> dirty in the sense that e2fsck doesn't take one look at it, say "yep, nothing to do here" and exit <@vorlon> in the sense that this is what would make dev-sda1.device slow to complete AIUI <@rcj>would filesystem resize on first boot mark it dirty? Because that will happen <@vorlon> huh good question <@vorlon> it might rcj, unclean shutdown? <@rcj>xnox: first boot [Test case] 1. Install console-setup from -proposed 2. Reboot 3. Verify that `systemctl status console-setup` shows that the service has completed successfully. Since this is a race, additional fuzz testing may be warranted for the cloud images to confirm that the issue experienced in GCE is really fixed. However, that should not block promotion of this SRU fix since there definitely is a race here that should be fixed per se even if there are other issues still causing a failure in GCE. [Regression potential] None known. /run is guaranteed to be mounted rw very early in boot - generally before /tmp is mounted, due to /tmp being on the rootfs that needs to be fscked before remount. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: console-setup 1.108ubuntu15.4 ProcVersionSignature: User Name 4.15.0-1029.31~16.04.1-gcp 4.15.18 Uname: Linux 4.15.0-1029-gcp x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Apr 10 19:24:12 2019 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: console-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1824227/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818814] Re: systemd-tmpfiles-setup.services fails to create /var/run directories
Yes, tested, and sorry, it did not help. There are still the same errors in syslog, and /var/run don't have proper directories for sshd etc. The systemd (etc) version is now as follows: kalle@vspk:~$ apt-cache policy systemd systemd: Installed: 229-4ubuntu21.21+bug1818814v20190411b1 Candidate: 229-4ubuntu21.21+bug1818814v20190411b1 Version table: *** 229-4ubuntu21.21+bug1818814v20190411b1 500 500 http://ppa.launchpad.net/ddstreet/lp1818814/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu21.21 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 229-4ubuntu4 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages -- 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/1818814 Title: systemd-tmpfiles-setup.services fails to create /var/run directories Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: In Progress Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description:Ubuntu 16.04.6 LTS Release:16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center systemd: Installed: 229-4ubuntu21.16 Candidate: 229-4ubuntu21.16 Version table: *** 229-4ubuntu21.16 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3) What you expected to happen 4) What happened instead Ubuntu server (running in OpenVZ VPS farm, thus the old kernel version) has been up and running happily, until I performed apt-get upgrade and rebooted the server. After reboot, I could not establish SSH connection to server, port 22 connection was refused. I opened a HTML console to my server instance and checked logs. From the logs, it was shown, that SSH server could not start, as it did not have the /var/run/sshd directory. After scrolling back the /var/log/syslog, I noticed that there were lots of other /var/run subdirectories, which were not created. Here is cut from /var/log/syslog, related to systemd-tmpfiles: ---8<---8<--- Mar 6 12:32:54 vspk systemd-tmpfiles[81]: [/usr/lib/tmpfiles.d/00rsyslog.conf:6] Duplicate line for path "/v ar/log", ignoring. Mar 6 12:32:54 vspk systemd[1]: Starting Raise network interfaces... Mar 6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/named failed: Invalid argument Mar 6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path /var/run/fail2ban: Too many levels of symb olic links Mar 6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path /var/run/screen: Too many levels of symbol ic links Mar 6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path /var/run/sshd: Too many levels of symbolic links Mar 6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path /var/run/sudo: Too many levels of symbolic links Mar 6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path /var/run/sudo/ts: Too many levels of symbo lic links
[Touch-packages] [Bug 1824341] Re: NoAllowedOrigin cause package removal
The proposed fix is clear cache on NoAllowedOriginError exception. ** Patch added: "fix clear cache on exception" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1824341/+attachment/5254915/+files/uu_origin.patch ** Description changed: unattended-upgrades remove packages that shouldn't when there is a NoAllowedOrigin exception. Version: unattended-upgrades=1.1ubuntu1.18.04.10 Ubuntu 18.04.2 LTS Description of problem: We have a internal package cliente-ldap that depends on samba, when u-u check for upgrade samba-common it raise a NoAllowedOrigin exception, then it doesn't clear apt.cache and it removes packages that shouldn't. Log of dry-run with the problem: $ sudo unattended-upgrade -d --dry-run [...] Option --dry-run given, *not* performing real actions Packages that will be upgraded: libsmbclient libwbclient0 python-samba samba samba-common samba-common-bin samba-dsdb-modules samba-libs samba-vfs-modules smbclient Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log debug: call_adjusted samba-common debug: marked_pkg: samba: install=False, upgrade=False, delete=True - debug: marked_pkg: cliente-ldap: install=False, upgrade=True, delete=False + debug: marked_pkg: cliente-ldap: install=False, upgrade=False, delete=True Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 259, in call_adjusted self.allowed_origins) - File "/usr/bin/unattended-upgrade", line 775, in ver_in_allowed_origin + File "/usr/bin/unattended-upgrade", line 777, in ver_in_allowed_origin raise NoAllowedOriginError() NoAllowedOriginError debug: marked_pkg: samba-common: install=False, upgrade=True, delete=False debug: marked_pkg: smbclient: install=False, upgrade=False, delete=True debug: marked_pkg: samba-common-bin: install=False, upgrade=False, delete=True Exception: + marking samba-common-bin for removal + Keeping auto-removable samba-common-bin package(s) because it would also remove the following packages which should be kept in this step: samba-common + marking tdb-tools for removal + Keeping auto-removable tdb-tools package(s) because it would also remove the following packages which should be kept in this step: samba-common marking ibverbs-providers for removal - Keeping auto-removable ibverbs-providers package(s) because it would also remove the following packages which should be kept in this step: cliente-ldap samba-common - marking samba-common-bin for removal - Keeping auto-removable samba-common-bin package(s) because it would also remove the following packages which should be kept in this step: cliente-ldap samba-common + marking python-dnspython for removal + marking librados2 for removal + marking ldap-auth-client for removal + marking ldap-auth-config for removal + marking python-tdb for removal + marking libhx28 for removal + marking libcephfs2 for removal + marking nscd for removal + marking smbclient for removal + marking cliente-ldap for removal + marking libnss-db for removal marking samba-vfs-modules for removal + marking samba-dsdb-modules for removal + marking libpam-mount for removal + marking libpam-ldap for removal + marking nss-updatedb for removal + marking python-samba for removal + marking auth-client-config for removal + marking python-ldb for removal + marking libnss-ldap for removal marking python-crypto for removal - Keeping auto-removable python-crypto package(s) because it would also remove the following packages which should be kept in this step: cliente-ldap + marking samba for removal + marking libibverbs1 for removal marking attr for removal - marking smbclient for removal - Keeping auto-removable smbclient package(s) because it would also remove the following packages which should be kept in this step: cliente-ldap - marking python-ldb for removal - Keeping auto-removable python-ldb package(s) because it would also remove the following packages which should be kept in this step: cliente-ldap - marking python-tdb for removal - Keeping auto-removable python-tdb package(s) because it would also remove the following packages which should be kept in this step: cliente-ldap - marking samba-dsdb-modules for removal - marking librados2 for removal - marking libibverbs1 for removal - marking samba for removal - Keeping auto-removable samba package(s) because it would also remove the following packages which should be kept in this step: cliente-ldap - marking python-samba for removal - Keeping auto-removable python-samba package(s) because it would also remove the following packages which should be kept in this step: cliente-ldap - marking libcephfs2 for removal - marking tdb-tools for removal - Keeping auto-removable tdb-tools package(s) because it would also remove the following packages which should be kept in this step: cliente-ldap samba-common - marking python-dnspython for removal - Keeping auto-removable python-dnspython
[Touch-packages] [Bug 1823761] Re: [SRU] Move Livepatch in a different tab as in Disco
Could you make the bug SRU compliant (having the impact/test case/regression potential) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1823761 Title: [SRU] Move Livepatch in a different tab as in Disco Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: New Bug description: Backport the new Livepatch tab from Disco. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1823761/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823761] Re: [SRU] Move Livepatch in a different tab as in Disco
That's a software-properties change right? (assuming the component was just wrongly selected and changing that) ** Package changed: update-notifier (Ubuntu) => software-properties (Ubuntu) ** Changed in: software-properties (Ubuntu) Importance: Undecided => High ** Changed in: software-properties (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1823761 Title: [SRU] Move Livepatch in a different tab as in Disco Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: New Bug description: Backport the new Livepatch tab from Disco. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1823761/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824342] Re: in 19.04, default user cannot access system journal
build config, tmpfiles config have not changed. Probably a regression in v240 vs v239 of the systemd-tmpfiles utility implementation. -- 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/1824342 Title: in 19.04, default user cannot access system journal Status in systemd package in Ubuntu: New Bug description: in a fresh install of 19.04 from http://cdimage.ubuntu.com/daily- live/20190410/disco-desktop-amd64.iso, journalctl -u snapd, or -u gdm, or -u udisks, results in 'no entries'. journalctl --system -u snapd etc, warns about permissions. $ sudo getfacl /var/log/journal/ getfacl: Removing leading '/' from absolute path names # file: var/log/journal/ # owner: root # group: systemd-journal # flags: -s- user::rwx group::r-x other::r-x default:user::rwx default:group::r-x default:group:adm:r-x default:mask::r-x default:other::r-x this is fixed via sudo setfacl -R -nm g:adm:rx,d:g:adm:rx /var/log/journal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824342/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1666432] Re: Internet drops every few minutes on wired and wireless connection
I'm on ubuntu 18.10 and I get random drops but if I disconnect and reconnect from the UI, it works. This isn't happening on my laptop which runs 18.04 also on cable connection. -network description: Ethernet interface product: I211 Gigabit Network Connection vendor: Intel Corporation physical id: 0 bus info: pci@:07:00.0 logical name: enp7s0 version: 03 serial: e0:d5:5e:a0:55:0f size: 1Gbit/s capacity: 1Gbit/s width: 32 bits clock: 33MHz capabilities: pm msi msix pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=igb driverversion=5.4.0-k duplex=full firmware=0. 6-1 ip=192.168.0.108 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s resources: irq:38 memory:f760-f761 ioport:f000(size=32) memory:f762-f7623fff -- 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/1666432 Title: Internet drops every few minutes on wired and wireless connection Status in network-manager package in Ubuntu: Confirmed Bug description: Internet drops every 1-30 minutes when connected via wired or wireless (i.e., this is a problem on both wired and wireless) even though connection icon indicates the computer is still connected. Disconnecting and reconnecting via the connection icon resets internet temporarily until the next time. Dropped internet is discovered with "The site can't be reached" screens in Chromium, or error messages when downloading/updating in Terminal, or missing connection in Ubuntu Software app, or stalled syncing in Insync application (occurred even without Insync). Internet drops more frequently on wireless than on wired. It seems to disconnect more frequently with heavier internet use (e.g., downloading multiple files, opening several webpages in quick succession). This is a fresh install (yesterday) of Ubuntu 16.04 on a Dell Inspiron 15 5567 (dual boot). It occurs when running Live CD as well though. Ethernet and wifi both work without randomly disconnecting in Windows 10 on the same machine, and ethernet and wifi work on other machines running Ubuntu and Windows with the same router, so it is not a hardware or router issue. Output from sudo lshw -class network *-network description: Wireless interface product: Wireless 3165 vendor: Intel Corporation physical id: 0 bus info: pci@:02:00.0 logical name: wlp2s0 version: 79 serial: 58:fb:84:55:21:52 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.4.0-62-generic firmware=17.352738.0 ip=192.168.1.15 latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn resources: irq:283 memory:df10-df101fff *-network description: Ethernet interface product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 logical name: enp3s0 version: 07 serial: 18:db:f2:3c:d5:37 size: 10Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half firmware=rtl8106e-1_0.0.1 06/29/12 latency=0 link=no multicast=yes port=MII speed=10Mbit/s resources: irq:279 ioport:d000(size=256) memory:df00-df000fff memory:d030-d0303fff ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 21 16:36:55 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-02-20 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.1.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.15 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present
[Touch-packages] [Bug 1823761] [NEW] [SRU] Move Livepatch in a different tab as in Disco
You have been subscribed to a public bug: Backport the new Livepatch tab from Disco. ** Affects: software-properties (Ubuntu) Importance: High Status: Fix Released ** Affects: software-properties (Ubuntu Bionic) Importance: Undecided Status: New ** Tags: rls-bb-incoming -- [SRU] Move Livepatch in a different tab as in Disco https://bugs.launchpad.net/bugs/1823761 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824341] [NEW] NoAllowedOrigin cause package removal
Public bug reported: unattended-upgrades remove packages that shouldn't when there is a NoAllowedOrigin exception. Version: unattended-upgrades=1.1ubuntu1.18.04.10 Ubuntu 18.04.2 LTS Description of problem: We have a internal package cliente-ldap that depends on samba, when u-u check for upgrade samba-common it raise a NoAllowedOrigin exception, then it doesn't clear apt.cache and it removes packages that shouldn't. Log of dry-run with the problem: $ sudo unattended-upgrade -d --dry-run [...] Option --dry-run given, *not* performing real actions Packages that will be upgraded: libsmbclient libwbclient0 python-samba samba samba-common samba-common-bin samba-dsdb-modules samba-libs samba-vfs-modules smbclient Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log debug: call_adjusted samba-common debug: marked_pkg: samba: install=False, upgrade=False, delete=True debug: marked_pkg: cliente-ldap: install=False, upgrade=True, delete=False Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 259, in call_adjusted self.allowed_origins) File "/usr/bin/unattended-upgrade", line 775, in ver_in_allowed_origin raise NoAllowedOriginError() NoAllowedOriginError debug: marked_pkg: samba-common: install=False, upgrade=True, delete=False debug: marked_pkg: smbclient: install=False, upgrade=False, delete=True debug: marked_pkg: samba-common-bin: install=False, upgrade=False, delete=True Exception: marking ibverbs-providers for removal Keeping auto-removable ibverbs-providers package(s) because it would also remove the following packages which should be kept in this step: cliente-ldap samba-common marking samba-common-bin for removal Keeping auto-removable samba-common-bin package(s) because it would also remove the following packages which should be kept in this step: cliente-ldap samba-common marking samba-vfs-modules for removal marking python-crypto for removal Keeping auto-removable python-crypto package(s) because it would also remove the following packages which should be kept in this step: cliente-ldap marking attr for removal marking smbclient for removal Keeping auto-removable smbclient package(s) because it would also remove the following packages which should be kept in this step: cliente-ldap marking python-ldb for removal Keeping auto-removable python-ldb package(s) because it would also remove the following packages which should be kept in this step: cliente-ldap marking python-tdb for removal Keeping auto-removable python-tdb package(s) because it would also remove the following packages which should be kept in this step: cliente-ldap marking samba-dsdb-modules for removal marking librados2 for removal marking libibverbs1 for removal marking samba for removal Keeping auto-removable samba package(s) because it would also remove the following packages which should be kept in this step: cliente-ldap marking python-samba for removal Keeping auto-removable python-samba package(s) because it would also remove the following packages which should be kept in this step: cliente-ldap marking libcephfs2 for removal marking tdb-tools for removal Keeping auto-removable tdb-tools package(s) because it would also remove the following packages which should be kept in this step: cliente-ldap samba-common marking python-dnspython for removal Keeping auto-removable python-dnspython package(s) because it would also remove the following packages which should be kept in this step: cliente-ldap Packages that were successfully auto-removed: Packages that are kept back: ibverbs-providers python-crypto python-dnspython python-ldb python-samba python-tdb samba samba-common-bin smbclient tdb-tools InstCount=0 DelCount=0 BrokenCount=0 Log of what should happen: $ sudo unattended-upgrade -d --dry-run [...] Option --dry-run given, *not* performing real actions Packages that will be upgraded: libsmbclient libwbclient0 python-samba samba samba-common samba-common-bin samba-dsdb-modules samba-libs samba-vfs-modules smbclient Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log debug: call_adjusted samba-common debug: marked_pkg: samba: install=False, upgrade=False, delete=True debug: marked_pkg: cliente-ldap: install=False, upgrade=True, delete=False Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 259, in call_adjusted self.allowed_origins) File "/usr/bin/unattended-upgrade", line 775, in ver_in_allowed_origin raise NoAllowedOriginError() NoAllowedOriginError debug: marked_pkg: samba-common: install=False, upgrade=True, delete=False debug: marked_pkg: smbclient: install=False, upgrade=False, delete=True debug: marked_pkg: samba-common-bin: install=False, upgrade=False, delete=True debug: call_adjusted libsmbclient debug: marked_pkg: python-samba: install=False, upgrade=True, delete=False debug: marked_pkg: libwbclient0: install=False, upgrade=True, delete=False debug: marked_pkg: samba:
[Touch-packages] [Bug 1824342] Re: in 19.04, default user cannot access system journal
** Changed in: systemd (Ubuntu) Importance: Undecided => High ** Tags added: rls-dd-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1824342 Title: in 19.04, default user cannot access system journal Status in systemd package in Ubuntu: New Bug description: in a fresh install of 19.04 from http://cdimage.ubuntu.com/daily- live/20190410/disco-desktop-amd64.iso, journalctl -u snapd, or -u gdm, or -u udisks, results in 'no entries'. journalctl --system -u snapd etc, warns about permissions. $ sudo getfacl /var/log/journal/ getfacl: Removing leading '/' from absolute path names # file: var/log/journal/ # owner: root # group: systemd-journal # flags: -s- user::rwx group::r-x other::r-x default:user::rwx default:group::r-x default:group:adm:r-x default:mask::r-x default:other::r-x this is fixed via sudo setfacl -R -nm g:adm:rx,d:g:adm:rx /var/log/journal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824342/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818814] Re: systemd-tmpfiles-setup.services fails to create /var/run directories
ok, maybe there is a tmpfiles problem :) can you test with the systemd pkg from this ppa? https://launchpad.net/~ddstreet/+archive/ubuntu/lp1818814 ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Fix Released ** Changed in: systemd (Ubuntu Xenial) Status: New => In Progress ** Changed in: systemd (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Xenial) Assignee: (unassigned) => Dan Streetman (ddstreet) -- 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/1818814 Title: systemd-tmpfiles-setup.services fails to create /var/run directories Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: In Progress Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description:Ubuntu 16.04.6 LTS Release:16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center systemd: Installed: 229-4ubuntu21.16 Candidate: 229-4ubuntu21.16 Version table: *** 229-4ubuntu21.16 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3) What you expected to happen 4) What happened instead Ubuntu server (running in OpenVZ VPS farm, thus the old kernel version) has been up and running happily, until I performed apt-get upgrade and rebooted the server. After reboot, I could not establish SSH connection to server, port 22 connection was refused. I opened a HTML console to my server instance and checked logs. From the logs, it was shown, that SSH server could not start, as it did not have the /var/run/sshd directory. After scrolling back the /var/log/syslog, I noticed that there were lots of other /var/run subdirectories, which were not created. Here is cut from /var/log/syslog, related to systemd-tmpfiles: ---8<---8<--- Mar 6 12:32:54 vspk systemd-tmpfiles[81]: [/usr/lib/tmpfiles.d/00rsyslog.conf:6] Duplicate line for path "/v ar/log", ignoring. Mar 6 12:32:54 vspk systemd[1]: Starting Raise network interfaces... Mar 6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/named failed: Invalid argument Mar 6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path /var/run/fail2ban: Too many levels of symb olic links Mar 6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path /var/run/screen: Too many levels of symbol ic links Mar 6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path /var/run/sshd: Too many levels of symbolic links Mar 6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path /var/run/sudo: Too many levels of symbolic links Mar 6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path /var/run/sudo/ts: Too many levels of symbo lic links Mar 6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/utmp failed: Invalid argument Mar 6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/systemd/netif failed: Invalid argument
[Touch-packages] [Bug 1824340] [NEW] DHCPv4 can't set route
Public bug reported: Dear colleagues, I'm facing the problem in systemd-networkd with processing classless routes (in fact, I'm using netplan, but netplan use networkd). Environment is below. The problem: DHCP server sends the following classless routes in Opt.121 (in the following sequence): 3.3.3.0/24 -> 10.0.3.14 10.0.3.0/24 -> 0.0.0.0 and systemd-networkd fails with the message: Apr 11 11:11:40 mother systemd-networkd[8357]: eth1: DHCPv4 address 10.0.2.15/24 Apr 11 11:11:40 mother systemd-networkd[8357]: eth1: DHCP: No routes received from DHCP server: No data available Apr 11 11:11:40 mother systemd-networkd[8357]: eth1: Could not set DHCPv4 route: Network is unreachable Apr 11 11:11:40 mother systemd-networkd[8357]: eth1: Failed The cause is clear - at the moment when 3.3.3.0/24 appears, there is no route to it's nexthop (10.0.3.14). Default behavior of ISC DHCP client is the same but can be fixed in two ways: 1) second run of dhclient installs 3.3.3.0/24 since 10.0.3.14 is accessible since first run 2) OR changing /etc/dhcp/dhclient-exit-hooks.d/rfc3442-classless-routes in order to process connected routes (i.e. gateway is 0.0.0.0) first, while other routes - next. Is it possible to modify systemd-networkd behavior in some way? - 1) sort routes and install connected first and other - next? 2) OR use kind of max_retries after which systemd-networkd's dhcp client will fail finally 3) OR add ability to use own scripts like mentioned above ISC's hook? Any recommendation on how to work around this issue are highly appreciated. Thank you. Environment: OS: Ubuntu 18.04.2 systemd: 237 DNS server: dnsmasq (Openstack) Netplan: 0.40.1~18.04.4 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1824340 Title: DHCPv4 can't set route Status in systemd package in Ubuntu: New Bug description: Dear colleagues, I'm facing the problem in systemd-networkd with processing classless routes (in fact, I'm using netplan, but netplan use networkd). Environment is below. The problem: DHCP server sends the following classless routes in Opt.121 (in the following sequence): 3.3.3.0/24 -> 10.0.3.14 10.0.3.0/24 -> 0.0.0.0 and systemd-networkd fails with the message: Apr 11 11:11:40 mother systemd-networkd[8357]: eth1: DHCPv4 address 10.0.2.15/24 Apr 11 11:11:40 mother systemd-networkd[8357]: eth1: DHCP: No routes received from DHCP server: No data available Apr 11 11:11:40 mother systemd-networkd[8357]: eth1: Could not set DHCPv4 route: Network is unreachable Apr 11 11:11:40 mother systemd-networkd[8357]: eth1: Failed The cause is clear - at the moment when 3.3.3.0/24 appears, there is no route to it's nexthop (10.0.3.14). Default behavior of ISC DHCP client is the same but can be fixed in two ways: 1) second run of dhclient installs 3.3.3.0/24 since 10.0.3.14 is accessible since first run 2) OR changing /etc/dhcp/dhclient-exit-hooks.d/rfc3442-classless-routes in order to process connected routes (i.e. gateway is 0.0.0.0) first, while other routes - next. Is it possible to modify systemd-networkd behavior in some way? - 1) sort routes and install connected first and other - next? 2) OR use kind of max_retries after which systemd-networkd's dhcp client will fail finally 3) OR add ability to use own scripts like mentioned above ISC's hook? Any recommendation on how to work around this issue are highly appreciated. Thank you. Environment: OS: Ubuntu 18.04.2 systemd: 237 DNS server: dnsmasq (Openstack) Netplan: 0.40.1~18.04.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824340/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824342] [NEW] in 19.04, default user cannot access system journal
Public bug reported: in a fresh install of 19.04 from http://cdimage.ubuntu.com/daily- live/20190410/disco-desktop-amd64.iso, journalctl -u snapd, or -u gdm, or -u udisks, results in 'no entries'. journalctl --system -u snapd etc, warns about permissions. $ sudo getfacl /var/log/journal/ getfacl: Removing leading '/' from absolute path names # file: var/log/journal/ # owner: root # group: systemd-journal # flags: -s- user::rwx group::r-x other::r-x default:user::rwx default:group::r-x default:group:adm:r-x default:mask::r-x default:other::r-x this is fixed via sudo setfacl -R -nm g:adm:rx,d:g:adm:rx /var/log/journal ** Affects: systemd (Ubuntu) Importance: High Status: New ** Tags: rls-dd-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1824342 Title: in 19.04, default user cannot access system journal Status in systemd package in Ubuntu: New Bug description: in a fresh install of 19.04 from http://cdimage.ubuntu.com/daily- live/20190410/disco-desktop-amd64.iso, journalctl -u snapd, or -u gdm, or -u udisks, results in 'no entries'. journalctl --system -u snapd etc, warns about permissions. $ sudo getfacl /var/log/journal/ getfacl: Removing leading '/' from absolute path names # file: var/log/journal/ # owner: root # group: systemd-journal # flags: -s- user::rwx group::r-x other::r-x default:user::rwx default:group::r-x default:group:adm:r-x default:mask::r-x default:other::r-x this is fixed via sudo setfacl -R -nm g:adm:rx,d:g:adm:rx /var/log/journal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824342/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778219] Re: unattended-upgrades hangs on shutdown, leaves system in a broken state
Verified 1.1ubuntu1.18.04.7~16.04.2 on Xenial:
root@x-uu:~# dbus-send --system --print-reply --dest=org.freedesktop.login1
/org/freedesktop/login1 "org.freedesktop.login1.Manager.Reboot" boolean:false
method return time=1554982311.759518 sender=:1.1 -> destination=:1.7 serial=19
reply_serial=2
root@x-uu:~#
$
$ lxc shell x-uu
root@x-uu:~# dpkg -l unattended-upgrades | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersionArchitecture Description
+++-===-==--===
ii unattended-upgrades 1.1ubuntu1.18.04.7~16.04.2 all automatic
installation of security upgrades
root@x-uu:~# cat /var/log/unattended-upgrades/unattended-upgrades.log
2019-04-11 11:31:44,714 INFO Initial blacklisted packages:
2019-04-11 11:31:44,715 INFO Initial whitelisted packages:
2019-04-11 11:31:44,715 INFO Starting unattended upgrades script
2019-04-11 11:31:44,715 INFO Allowed origins are: o=Ubuntu,a=xenial,
o=Ubuntu,a=xenial-security, o=UbuntuESM,a=xenial, o=Ubuntu,a=xenial-updates
2019-04-11 11:31:52,034 INFO Initial blacklisted packages:
2019-04-11 11:31:52,034 INFO Initial whitelisted packages:
2019-04-11 11:31:52,035 INFO Starting unattended upgrades script
2019-04-11 11:31:52,035 INFO Allowed origins are: o=Ubuntu,a=xenial,
o=Ubuntu,a=xenial-security, o=UbuntuESM,a=xenial, o=Ubuntu,a=xenial-updates
2019-04-11 11:31:59,193 INFO Packages that will be upgraded: snapd
ubuntu-core-launcher
2019-04-11 11:31:59,194 INFO Writing dpkg log to
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
2019-04-11 11:32:06,043 INFO All upgrades installed
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1778219
Title:
unattended-upgrades hangs on shutdown, leaves system in a broken state
Status in snapd package in Ubuntu:
Confirmed
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in snapd source package in Xenial:
Confirmed
Status in unattended-upgrades source package in Xenial:
Fix Committed
Status in snapd source package in Bionic:
Confirmed
Status in unattended-upgrades source package in Bionic:
Fix Released
Status in unattended-upgrades source package in Cosmic:
Fix Released
Bug description:
[Impact]
* Unattended-upgrades hangs and gets killed when installing upgrades
that stat/stop services on shutdown, leaving the system in a broken
state
[Test Case]
* Install an updated bionic system:
$ lxc launch ubuntu:18.04 uu-shutdown-test
# apt update
...
* When testing the fixed version, install upgrade u-u at this point checking
that u-u.service is set up before and is wanted by shutdown.target:
# systemd-analyze dot | grep unatt
"unattended-upgrades.service"->"-.mount" [color="green"];
"unattended-upgrades.service"->"system.slice" [color="green"];
"unattended-upgrades.service"->"network.target" [color="green"];
"unattended-upgrades.service"->"systemd-journald.socket" [color="green"];
"unattended-upgrades.service"->"local-fs.target" [color="green"];
"unattended-upgrades.service"->"-.mount" [color="black"];
"unattended-upgrades.service"->"system.slice" [color="black"];
"shutdown.target"->"unattended-upgrades.service" [color="green"];
"shutdown.target"->"unattended-upgrades.service" [color="grey66"];
Color legend: black = Requires
dark blue = Requisite
dark grey = Wants
red = Conflicts
green = After
* Configure u-u to run on shutdown and install -updates:
# echo 'Unattended-Upgrade::InstallOnShutdown "true";' >
/etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown
# echo 'Unattended-Upgrade::Allowed-Origins::
"${distro_id}:${distro_codename}-updates";' >
/etc/apt/apt.conf.d/51unattended-upgrades-updates-too
* Downgrade snapd:
# apt install snapd=2.32.5+18.04
* Dowload packages for u-u:
# unattended-upgrade --download-only
* Reboot using logind to let inhibitors hold up shutdown:
# dbus-send --system --print-reply --dest=org.freedesktop.login1
/org/freedesktop/login1 "org.freedesktop.login1.Manager.Reboot" boolean:false
* With not fixed u-u observe the upgrade process being stuck:
# pstree| grep unatt
`-unattended-upgr---unattended-upgr-+-unattended-upgr---dpkg---snapd.prerm---systemctl
`-{unattended-upgr}
* With fixed u-u observe snapd update taking place and system
rebooting after a few seconds with
[Touch-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (crash in xorg before using "foreign grub")
An additional data point for reference .. did a netboot install of xubuntu using "daily" amd64 netboot mini.iso .. base install followed by taskselect install of xubuntu .. boots normally plymouth and lightdm screens appear as expected .. also switching to foreign grub .. it still boots normally .. normal expected behaviour .. note: regular ubuntu daily also behaves this way .. but uses wayland no xorg .. rhetorical question: so what makes the full graphics install so fragile for intel i915 graphics? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1821609 Title: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (crash in xorg before using "foreign grub") Status in lightdm package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Invalid Bug description: Okay the has happened recently at least since march 18, 2019 iso and march 22, 2019 iso are both effected very similar to one of my previously reported bugs .. which was related to xorg not being installed .. back ground .. PC is lenovo sl 500 with evo860 SSD drive 3 partions contain installs of disco sda1 -- main working system -- I usually install grub from here as master .. sda6 and sda7 are test installs of disco daily iso's 03-18-2019, 03-22-2019 repectively on the test installs as long as the iso is using the grub boot loader installed from that install the system will boot normally .. the display manger tends to flicker on and off but does final start and login can proceed. but if another install re-installs grub as master the display manager fails to stay active or even come-up for sda6 or sda7 only if their own grubs are reinstalled will they work normally sda1 display manager/xorg login works always no matter which "grub- source" is in control. if I use rescue boot from any grub as master I can get the displays to work by running dpkg fix which does nothing .. and then resuming the boot .. then things work normally.. if the "non-rescue" boots are used the screen/computer locks and only a power down and reboot gives access. (sometime requiring radical depowering .. unpluging and removing battery) now the is a message that appears that RCs??? level is missing. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu11 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Mar 25 11:25:58 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2019-03-23 (1 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322) MachineType: LENOVO 2746CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6AET64WW dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 2746CTO dmi.board.vendor: LENOVO dmi.board.version: LENOVO 6AET64WW dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LENOVO 6AET64WW dmi.modalias: dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW: dmi.product.name: 2746CTO dmi.product.version: ThinkPad SL500 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Touch-packages] [Bug 1757375] Re: Desktop unable to Suspend when Inactive
Your workaround worked for me too. I'm running Xubuntu 18.04. Now I can suspend the machine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-desktop- privileges in Ubuntu. https://bugs.launchpad.net/bugs/1757375 Title: Desktop unable to Suspend when Inactive Status in policykit-desktop-privileges package in Ubuntu: Confirmed Bug description: On 16.04 (XFCE session and others) and possibly later the power- manager is unable to suspend the system when the user is inactive. A PK user-agent dialog is presented for the user to authenticate first - and as this action occurs specifically when the user is idle and away the PC can end up having an unplanned loss of power when the battery is exhausted. /var/log/auth.log shows: polkitd(authority=local): Operator of unix-session:c2 FAILED to authenticate to gain authorization for action org.freedesktop.login1.suspend for system-bus-name::1.47 [xfce4-power- manager --restart --sm-client-id 2992705d4-6fa2-4fba-966c- f7631ecd0b46] (owned by unix-user:tj) The problem seems to be "com.ubuntu.desktop.pkla" is missing an entry to allow Suspend. Currently it only has an entry for hibernate. Adding the following stanza solves the issue: [Enable suspend by default in logind] Identity=unix-user:* Action=org.freedesktop.login1.suspend;org.freedesktop.login1.inhibit-handle-suspend-key;org.freedesktop.login1;org.freedesktop.login1.suspend-multiple-sessions;org.freedesktop.login1.suspend-ignore-inhibit ResultActive=yes ResultInactive=yes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1757375/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823426] Re: librsvg ftbfs in disco (i386 only)
This bug was fixed in the package librsvg - 2.44.10-1ubuntu1 --- librsvg (2.44.10-1ubuntu1) disco; urgency=medium * debian/patches/typenum-i386-ftbfs.patch: backport an upstream fix for a build failure in the vendored typenum crate on i386 (LP: #1823426) * debian/patches/i386-rounding-errors.patch: fix a rounding error on i386 that would result in a unit test failure -- Olivier Tilloy Wed, 10 Apr 2019 17:14:57 +0200 ** Changed in: librsvg (Ubuntu Disco) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1823426 Title: librsvg ftbfs in disco (i386 only) Status in librsvg: New Status in librsvg package in Ubuntu: Fix Released Status in librsvg source package in Disco: Fix Released Status in librsvg package in Debian: Fix Released Bug description: https://launchpadlibrarian.net/417925231/buildlog_ubuntu- disco-i386.librsvg_2.44.10-1_BUILDING.txt.gz Compiling phf_generator v0.7.23 Running `rustc --crate-name phf_generator /<>/vendor/phf_generator/src/lib.rs --color never --crate-type lib --emit=dep-info,link -C opt-level=3 -C debuginfo=2 -C metadata=454a5a2ede7d0e81 -C extra-filename=-454a5a2ede7d0e81 --out-dir /<>/target/release/deps -L dependency=/<>/target/release/deps --extern phf_shared=/<>/target/release/deps/libphf_shared-3211ae4bedecc506.rlib --extern rand=/<>/target/release/deps/librand-bc26f371fdd8f508.rlib --cap-lints allow` error[E0428]: the name `U1024` is defined multiple times --> /<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2112:5 | 2110 | pub type U1024 = UInt, B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>; | - previous definition of the type `U1024` here 2111 | pub type P1024 = PInt; pub type N1024 = NInt; 2112 | pub type U1024 = UInt, B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>; | ^ `U1024` redefined here | = note: `U1024` must be defined only once in the type namespace of this module error[E0428]: the name `P1024` is defined multiple times --> /<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2113:5 | 2111 | pub type P1024 = PInt; pub type N1024 = NInt; | - previous definition of the type `P1024` here 2112 | pub type U1024 = UInt, B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>; 2113 | pub type P1024 = PInt; pub type N1024 = NInt; | ^ `P1024` redefined here | = note: `P1024` must be defined only once in the type namespace of this module error[E0428]: the name `N1024` is defined multiple times --> /<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2113:35 | 2111 | pub type P1024 = PInt; pub type N1024 = NInt; | - previous definition of the type `N1024` here 2112 | pub type U1024 = UInt, B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>; 2113 | pub type P1024 = PInt; pub type N1024 = NInt; | ^ `N1024` redefined here | = note: `N1024` must be defined only once in the type namespace of this module Compiling quote v0.6.8 Running `rustc --crate-name quote /<>/vendor/quote/src/lib.rs --color never --crate-type lib --emit=dep-info,link -C opt-level=3 -C debuginfo=2 --cfg 'feature="default"' --cfg 'feature="proc-macro"' --cfg 'feature="proc-macro2"' -C metadata=7bcb03a3954c3d99 -C extra-filename=-7bcb03a3954c3d99 --out-dir /<>/target/release/deps -L dependency=/<>/target/release/deps --extern proc_macro2=/<>/target/release/deps/libproc_macro2-f0d4dedaba1fcdae.rlib --cap-lints allow` error: aborting due to 3 previous errors For more information about this error, try `rustc --explain E0428`. error: Could not compile `typenum`. Caused by: process didn't exit successfully: `rustc --crate-name typenum /<>/vendor/typenum/src/lib.rs --color never --crate-type lib --emit=dep-info,link -C opt-level=3 -C debuginfo=2 -C metadata=373290d68c8bc9c3 -C extra-filename=-373290d68c8bc9c3 --out-dir /<>/target/release/deps -L dependency=/<>/target/release/deps --cap-lints allow` (exit code: 1) warning: build failed, waiting for other jobs to finish... error: build failed make[3]: *** [Makefile:1955: /<>/target/release/librsvg_internals.a] Error 101 make[3]: Leaving directory '/<>' make[2]: *** [Makefile:1457: all-recursive] Error 1
[Touch-packages] [Bug 1823306] Re: lxqt-sudo added to Exec line of software-properties-qt.desktop breaks use in KDE Plasma Discover
** Changed in: software-properties (Ubuntu Disco) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1823306 Title: lxqt-sudo added to Exec line of software-properties-qt.desktop breaks use in KDE Plasma Discover Status in software-properties package in Ubuntu: Fix Committed Status in software-properties source package in Disco: Fix Committed Bug description: In the upload: https://launchpad.net/ubuntu/+source/software- properties/0.97.8 there is a change in the software-properties-qt.desktop files which is (a) not documented in the changelog, and (b) not communicated to other flavour users of this application (Kubuntu in this case). -Exec=software-properties-qt +Exec=lxqt-sudo software-properties-qt This results in Plasma Discover not being able to launch software- properties-qt, as it uses privilege elevation via kdesu of whatever is in the Exec line, and lxqt-sudo added there makes this fail. Context to this is: For Cosmic release Lubuntu developers requested agreement from Kubuntu to the porting of the software-properties-kde package to pure Qt, so that it could be used in both Kubuntu and Lubuntu (lxqt) without pulling a lot of KDE dependencies into Lubuntu's lqxt images/installs. This was on the condition that despite being renamed to -qt, it remained completely as a tool for joint usage between the two flavours. The original sofware-properties-kde was meant to be launched by applications and was set not to show in DE menus by default. It seems that Lubuntu wishes to now have it useable directly from a 'start'/'search' menu, hence making it visible and adding the lxqt- sudo in the Exec line to facilitate launch with privilege escalation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1823306/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777367] Re: Output device doesn't always switch back from HDMI
*** This bug is a duplicate of bug 1711101 *** https://bugs.launchpad.net/bugs/1711101 Facing the same issue with 18.04.2 LTS Had the same issue with previous versions as well Will there be a fix anytime soon? Thank you. -- 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/1777367 Title: Output device doesn't always switch back from HDMI Status in pulseaudio package in Ubuntu: Confirmed Bug description: When I disconnect to an HDMI output sometimes the configuration is left in an inconsistent state. It still shows as being connected to HDMI in volume up/down but there is no longer an HDMI option in the sound settings. After clicking the "Speakers - Built-in Audio" line in the Output tab of the settings (the only line available) everything is now correct. The same issue was also present in 16.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pedrocr 32004 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 17 22:54:14 2018 InstallationDate: Installed on 2018-05-31 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET66W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS5TS00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS5TS00 dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1777367/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1711101] Re: Audio doesn't auto switch away from HDMI after unplugging HDMI
Facing the same issue with 18.04.2 LTS Had the same issue with previous versions as well Will there be a fix anytime soon? Thank you. -- 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/1711101 Title: Audio doesn't auto switch away from HDMI after unplugging HDMI Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Triaged Bug description: Steps to reproduce * Attach an external HDMI/DP monitor to watch videos on an external display (TV) * In sound settings, send audio to HDMI out, rather than internal laptop audio * Play a video, to show audio is going over HDMI * Unplug HDMI/DP cable - Video switches to internal panel only as expected. Expected behaviour * Audio switches to internal sound card Actual behaviour * Audio does not auto switch Workaround * Go to sound settings panel every time, and click the internal sound card Video showing it: https://www.youtube.com/watch?v=UR3LP0INMeI ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu2 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alan 1568 F pulseaudio /dev/snd/controlC1: alan 1568 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Aug 16 11:11:45 2017 InstallationDate: Installed on 2017-08-02 (13 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/27/2016 dmi.bios.vendor: LENOVO dmi.bios.version: JBET56WW (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BV001BUK dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET56WW(1.21):bd01/27/2016:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BV001BUK dmi.product.version: ThinkPad T450 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1711101/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability
Thanks, but there's no need. We'll get it via 3.24.8 which I'm uploading now. -- 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/1763520 Title: after upgrade to bionic, printing fails without explanation / logs / debuggability Status in gtk+3.0 package in Ubuntu: In Progress Status in gtk+3.0 source package in Bionic: In Progress Status in gtk+3.0 source package in Cosmic: In Progress Bug description: [Impact] The problem occurs when the printer's driver package is updated and with this the PPD is replaced and one of the default settings of the queue is not available any more in the new PPD file. Then the setting is prefixed with "Custom." and with this the jobs fail. See comment #15 for more info. [Test Case] - Create a print queue with a PPD. - evince an arbitrary PDF file - Click the print icon - In the print dialog choose the newly created queue and choose some uncommon paper size (not custom). Click "Print". - Check /var/log/cups/error_log, the page size gets correctly received. - Close evince. - Stop CUPS, edit the PPD file removing the paper size you have selected for your job in the PageSize, PageRegion, PaperDimension, and ImageableArea lines. - Start CUPS. - Open the same PDF file again with evince, click Print and then select "Print" in the print dialog without changing anything. - The job fails, in /var/log/cups/error_log you see that the page size is prefixed with "Custom.". With the fixed package installed the job will print. [Regression Potential] The change applies only to saved settings of the print dialog not matching with any of the settings available in the PPD file. In rare cases the fix could fail by mis-understanding the setting and this way not being effective. For options which do not support setting custom values (the vast majority) the patch should always prevent a job failure though. [Other Info] Complete info about the bug and the fix in comment #15, Original bug description: I am unable to print to my network-attached printer after upgrade to bionic. ps shows: lp 26047 0.0 0.0 91668 5756 ?S15:06 0:00 \_ HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 lp 26050 0.1 0.0 0 0 ?Z15:06 0:00 | \_ [gs] lp 26048 0.0 0.0 79908 3836 ?S15:06 0:00 \_ HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 root 26049 0.0 0.0 84388 6192 ?S15:06 0:00 \_ ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 Note the un-reaped gs process. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2 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-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 12 15:07:49 2018 InstallationDate: Installed on 2010-09-24 (2757 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) MachineType: LENOVO 2306CTO Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-03-21 (21 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No
[Touch-packages] [Bug 1823426] Re: librsvg ftbfs in disco (i386 only)
** Changed in: librsvg (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1823426 Title: librsvg ftbfs in disco (i386 only) Status in librsvg: New Status in librsvg package in Ubuntu: In Progress Status in librsvg source package in Disco: In Progress Status in librsvg package in Debian: Fix Released Bug description: https://launchpadlibrarian.net/417925231/buildlog_ubuntu- disco-i386.librsvg_2.44.10-1_BUILDING.txt.gz Compiling phf_generator v0.7.23 Running `rustc --crate-name phf_generator /<>/vendor/phf_generator/src/lib.rs --color never --crate-type lib --emit=dep-info,link -C opt-level=3 -C debuginfo=2 -C metadata=454a5a2ede7d0e81 -C extra-filename=-454a5a2ede7d0e81 --out-dir /<>/target/release/deps -L dependency=/<>/target/release/deps --extern phf_shared=/<>/target/release/deps/libphf_shared-3211ae4bedecc506.rlib --extern rand=/<>/target/release/deps/librand-bc26f371fdd8f508.rlib --cap-lints allow` error[E0428]: the name `U1024` is defined multiple times --> /<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2112:5 | 2110 | pub type U1024 = UInt, B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>; | - previous definition of the type `U1024` here 2111 | pub type P1024 = PInt; pub type N1024 = NInt; 2112 | pub type U1024 = UInt, B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>; | ^ `U1024` redefined here | = note: `U1024` must be defined only once in the type namespace of this module error[E0428]: the name `P1024` is defined multiple times --> /<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2113:5 | 2111 | pub type P1024 = PInt; pub type N1024 = NInt; | - previous definition of the type `P1024` here 2112 | pub type U1024 = UInt, B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>; 2113 | pub type P1024 = PInt; pub type N1024 = NInt; | ^ `P1024` redefined here | = note: `P1024` must be defined only once in the type namespace of this module error[E0428]: the name `N1024` is defined multiple times --> /<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2113:35 | 2111 | pub type P1024 = PInt; pub type N1024 = NInt; | - previous definition of the type `N1024` here 2112 | pub type U1024 = UInt, B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>; 2113 | pub type P1024 = PInt; pub type N1024 = NInt; | ^ `N1024` redefined here | = note: `N1024` must be defined only once in the type namespace of this module Compiling quote v0.6.8 Running `rustc --crate-name quote /<>/vendor/quote/src/lib.rs --color never --crate-type lib --emit=dep-info,link -C opt-level=3 -C debuginfo=2 --cfg 'feature="default"' --cfg 'feature="proc-macro"' --cfg 'feature="proc-macro2"' -C metadata=7bcb03a3954c3d99 -C extra-filename=-7bcb03a3954c3d99 --out-dir /<>/target/release/deps -L dependency=/<>/target/release/deps --extern proc_macro2=/<>/target/release/deps/libproc_macro2-f0d4dedaba1fcdae.rlib --cap-lints allow` error: aborting due to 3 previous errors For more information about this error, try `rustc --explain E0428`. error: Could not compile `typenum`. Caused by: process didn't exit successfully: `rustc --crate-name typenum /<>/vendor/typenum/src/lib.rs --color never --crate-type lib --emit=dep-info,link -C opt-level=3 -C debuginfo=2 -C metadata=373290d68c8bc9c3 -C extra-filename=-373290d68c8bc9c3 --out-dir /<>/target/release/deps -L dependency=/<>/target/release/deps --cap-lints allow` (exit code: 1) warning: build failed, waiting for other jobs to finish... error: build failed make[3]: *** [Makefile:1955: /<>/target/release/librsvg_internals.a] Error 101 make[3]: Leaving directory '/<>' make[2]: *** [Makefile:1457: all-recursive] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [Makefile:940: all] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/librsvg/+bug/1823426/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail
This worked for me in quite a few upgrades. Before starting the upgrade
to 18.04, still on 16.04:
mv /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service{,.bak}
apt purge systemd-shim
It does not work in the opposite order! If you try that way, apt purge
will complain about the service file.
--
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/1773859
Title:
upgrades to 18.04 fail
Status in systemd package in Ubuntu:
Fix Released
Status in systemd-shim package in Ubuntu:
Won't Fix
Status in systemd source package in Bionic:
Triaged
Status in systemd-shim source package in Bionic:
Won't Fix
Status in systemd source package in Cosmic:
Fix Released
Status in systemd-shim source package in Cosmic:
Won't Fix
Bug description:
[Impact]
* Some systems fail to upgrade due to conflicts between systemd and
the (now removed from the archive) systemd-shim / upstart.
* Instead of trying to work out what's the problem in ordering /
removal of diverts, ensure that systemd is never unpacked whilst
systemd-shim/upstart are still on disk. Thus declare conflicts against
systemd-shim/upstart packages in systemd package.
[Test Case]
* monitor drop-off of upgrades with below reported problem
* Check that it is possible to upgrade to bionic's libpam-systemd
from xenial with systemd-shim installed on xenial, ie.
lxc launch ubuntu-daily:xenial test-shim-upgrade
lxc exec test-shim-upgrade
apt update
apt install systemd-shim
wget
https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb
apt install ./systemd-shim_10-3_amd64.deb
sed 's/xenial/bionic/' -i /etc/apt/sources.list
apt update
apt install systemd
this currently passes, however, systemd-shim remains installed. It
should be removed instead. Apt install systemd should have lines like
this:
The following packages will be REMOVED:
systemd-shim
...
Removing 'diversion of
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by
systemd-shim'
...
[Regression Potential]
* systemd-shim/upstart are both removed and not supported in bionic,
thus forcing their removal via conflicts should bring the system into
an expected state.
[Other Info]
* original bug report
$ sudo apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be REMOVED:
systemd-shim
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 71.7 kB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 63 files and directories currently installed.)
Removing systemd-shim (9-1bzr4ubuntu1) ...
Removing 'diversion of
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by
systemd-shim'
dpkg-divert: error: rename involves overwriting
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
different file
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd',
not allowed
dpkg: error processing package systemd-shim (--remove):
subprocess installed post-removal script returned error exit status 2
Errors were encountered while processing:
systemd-shim
E: Sub-process /usr/bin/dpkg returned an error code (1)
Commenting out the dpkg-divert in systemd-shim's postrm solved this
for me and I was about to continue the upgrade.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824227] Re: console-setup failure due to race with systemd-tmpfiles
This bug was fixed in the package console-setup - 1.178ubuntu12 --- console-setup (1.178ubuntu12) disco; urgency=medium * setupcon: use /run for tempfiles (and dump the various unnecessary fallback paths), since /run is always mountable rw at least as early as /tmp is and is guaranteed to be safe from tmpcleaners at boot. Only keep /tmp as a fallback in case we have access to write to /tmp and to a console, but not to /run. LP: #1824227. -- Steve Langasek Wed, 10 Apr 2019 12:51:56 -0700 ** Changed in: console-setup (Ubuntu Disco) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1824227 Title: console-setup failure due to race with systemd-tmpfiles Status in console-setup package in Ubuntu: Fix Released Status in console-setup source package in Xenial: Fix Committed Status in console-setup source package in Bionic: Fix Committed Status in console-setup source package in Cosmic: Fix Committed Status in console-setup source package in Disco: Fix Released Bug description: [SRU Justification] I'm seeing a console-setup.service failure quite regularly in testing where the temp file that should have been created can't be found. This is a regular xenial cloud image. 19:51:13 systemd-tmpfiles[485]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. ... 19:51:13 systemd[1]: Starting Set console font and keymap... 19:51:15 setupcon[455]: /bin/setupcon: 809: /bin/setupcon: cannot open /tmp/tmpkbd.a8FGSs: No such file 19:51:15 systemd[1]: console-setup.service: Main process exited, code=exited, status=1/FAILURE 19:51:15 systemd[1]: Failed to start Set console font and keymap. 19:51:15 systemd[1]: console-setup.service: Unit entered failed state. 19:51:15 systemd[1]: console-setup.service: Failed with result 'exit-code'. ... /bin/setupcon has a lovely tempfile function that looks like: if \ TMPFILE=`mktemp /tmp/tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp /run/tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp /dev/.tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp /lib/init/rw/tmpkbd.XX 2>/dev/null` \ || TMPFILE=`mktemp 2>/dev/null` Here's our edited IRC conversation on the bug: <@vorlon> so I do think you're being hit by the tmp cleaner <@vorlon> also this seems like bad pathological default behavior for the tmp cleaner, to delete files that have just been created <@vorlon> but we should fix console-setup to not rely on /tmp <@vorlon> and I prefer that we do that instead of trying to fiddle with the ordering of the systemd units on startup <@vorlon> i.e. console-setup has an undeclared dependency on systemd-tmpfiles-clean; let's remove the dependency instead of declaring it <@vorlon> are you failing the race more often now than in the past? <@rcj>vorlon: it feels like it's failing more often but I don't have data to answer that. <@vorlon> are we shipping an image with a dirty rootfs? <@vorlon> dirty in the sense that e2fsck doesn't take one look at it, say "yep, nothing to do here" and exit <@vorlon> in the sense that this is what would make dev-sda1.device slow to complete AIUI <@rcj>would filesystem resize on first boot mark it dirty? Because that will happen <@vorlon> huh good question <@vorlon> it might rcj, unclean shutdown? <@rcj>xnox: first boot [Test case] 1. Install console-setup from -proposed 2. Reboot 3. Verify that `systemctl status console-setup` shows that the service has completed successfully. Since this is a race, additional fuzz testing may be warranted for the cloud images to confirm that the issue experienced in GCE is really fixed. However, that should not block promotion of this SRU fix since there definitely is a race here that should be fixed per se even if there are other issues still causing a failure in GCE. [Regression potential] None known. /run is guaranteed to be mounted rw very early in boot - generally before /tmp is mounted, due to /tmp being on the rootfs that needs to be fscked before remount. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: console-setup 1.108ubuntu15.4 ProcVersionSignature: User Name 4.15.0-1029.31~16.04.1-gcp 4.15.18 Uname: Linux 4.15.0-1029-gcp x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Apr 10 19:24:12 2019 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: console-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this
[Touch-packages] [Bug 1823426] Re: librsvg ftbfs in disco (i386 only)
** Bug watch added: Debian Bug tracker #926840 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926840 ** Also affects: librsvg (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926840 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1823426 Title: librsvg ftbfs in disco (i386 only) Status in librsvg: New Status in librsvg package in Ubuntu: In Progress Status in librsvg source package in Disco: In Progress Status in librsvg package in Debian: Unknown Bug description: https://launchpadlibrarian.net/417925231/buildlog_ubuntu- disco-i386.librsvg_2.44.10-1_BUILDING.txt.gz Compiling phf_generator v0.7.23 Running `rustc --crate-name phf_generator /<>/vendor/phf_generator/src/lib.rs --color never --crate-type lib --emit=dep-info,link -C opt-level=3 -C debuginfo=2 -C metadata=454a5a2ede7d0e81 -C extra-filename=-454a5a2ede7d0e81 --out-dir /<>/target/release/deps -L dependency=/<>/target/release/deps --extern phf_shared=/<>/target/release/deps/libphf_shared-3211ae4bedecc506.rlib --extern rand=/<>/target/release/deps/librand-bc26f371fdd8f508.rlib --cap-lints allow` error[E0428]: the name `U1024` is defined multiple times --> /<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2112:5 | 2110 | pub type U1024 = UInt, B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>; | - previous definition of the type `U1024` here 2111 | pub type P1024 = PInt; pub type N1024 = NInt; 2112 | pub type U1024 = UInt, B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>; | ^ `U1024` redefined here | = note: `U1024` must be defined only once in the type namespace of this module error[E0428]: the name `P1024` is defined multiple times --> /<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2113:5 | 2111 | pub type P1024 = PInt; pub type N1024 = NInt; | - previous definition of the type `P1024` here 2112 | pub type U1024 = UInt, B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>; 2113 | pub type P1024 = PInt; pub type N1024 = NInt; | ^ `P1024` redefined here | = note: `P1024` must be defined only once in the type namespace of this module error[E0428]: the name `N1024` is defined multiple times --> /<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2113:35 | 2111 | pub type P1024 = PInt; pub type N1024 = NInt; | - previous definition of the type `N1024` here 2112 | pub type U1024 = UInt, B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>; 2113 | pub type P1024 = PInt; pub type N1024 = NInt; | ^ `N1024` redefined here | = note: `N1024` must be defined only once in the type namespace of this module Compiling quote v0.6.8 Running `rustc --crate-name quote /<>/vendor/quote/src/lib.rs --color never --crate-type lib --emit=dep-info,link -C opt-level=3 -C debuginfo=2 --cfg 'feature="default"' --cfg 'feature="proc-macro"' --cfg 'feature="proc-macro2"' -C metadata=7bcb03a3954c3d99 -C extra-filename=-7bcb03a3954c3d99 --out-dir /<>/target/release/deps -L dependency=/<>/target/release/deps --extern proc_macro2=/<>/target/release/deps/libproc_macro2-f0d4dedaba1fcdae.rlib --cap-lints allow` error: aborting due to 3 previous errors For more information about this error, try `rustc --explain E0428`. error: Could not compile `typenum`. Caused by: process didn't exit successfully: `rustc --crate-name typenum /<>/vendor/typenum/src/lib.rs --color never --crate-type lib --emit=dep-info,link -C opt-level=3 -C debuginfo=2 -C metadata=373290d68c8bc9c3 -C extra-filename=-373290d68c8bc9c3 --out-dir /<>/target/release/deps -L dependency=/<>/target/release/deps --cap-lints allow` (exit code: 1) warning: build failed, waiting for other jobs to finish... error: build failed make[3]: *** [Makefile:1955: /<>/target/release/librsvg_internals.a] Error 101 make[3]: Leaving directory '/<>' make[2]: *** [Makefile:1457: all-recursive] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [Makefile:940: all] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/librsvg/+bug/1823426/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1808233] Re: Update gtk to 3.24.4
** Changed in: gtk+3.0 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1808233 Title: Update gtk to 3.24.4 Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Cosmic: Fix Released Bug description: Impact == There is a new release in the stable 3.24 series. This also bundles the emoji fixes from LP: #1807719 and LP: #1807721 and the Xfce flickering fix from LP: #1798861. https://gitlab.gnome.org/GNOME/gtk/blob/gtk-3-24/NEWS https://gitlab.gnome.org/GNOME/gtk/compare/3.24.1...3.24.4 Test Case = Run several apps in the default Ubuntu install and make sure that there are no visible regressions. Make sure that GTK switches look OK. We will also be checking Xfce to validate the fix for LP: #1798861. Regression Potential There is a standing microrelease exception for GNOME point releases. I believe this is the second time in recent history that we've pushed a gtk point release as an SRU. The other example was 3.22.25 for Ubuntu 17.10 (LP: #1728421). We never ended up doing one for Ubuntu 18.04 LTS since it already included 3.22.30, the final 3.22 release. It hasn't been practical to update 18.04's gtk to the 3.24 series (bumped dependencies are one problem). https://wiki.ubuntu.com/StableReleaseUpdates#GNOME By the way, pre-release gtk3 is actually getting a bit more testing than a year ago since more developers and users are using development Flatpak releases of popular GNOME apps. (On the other hand, there were a few regressions in the 3.24.2 and 3.24.3 releases.) This update changes the ON/OFF switches for GNOME's default Adwaita theme to use ❙/○ for all languages (or ⏽/⭘ if they are supported in a font you have installed: currently, that's fonts-symbola which we no longer install by default). Previously, it was ❙/○ for most languages but ON/OFF for English (because English has short words that could fit on a switch). This doesn't affect default Ubuntu 18.10 which uses Yaru which doesn't use labels on its switches. This is technically a UI change, but it is useful for compatibility with Flatpak apps that are being built with the new GTK. This change is small enough that it could be reverted for Ubuntu 18.10 if necessary. Other Info == The commit history shows themeing changes to the GNOME default themes (Adwaita and Adwaita Dark which are bundled inside gtk3). But those changes were reverted for this release to make it easier for distros like us to push the update to our stable release. The next scheduled gtk3 release (3.24.5 ? in March?) will include those changes. See https://blog.gtk.org/2019/01/14/theme-changes-in- gtk-3/ for more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1808233/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813587] Re: libunistring and libidn ftbfs on 18.04 LTS
This bug was fixed in the package libidn - 1.33-2.2ubuntu1.1 --- libidn (1.33-2.2ubuntu1.1) cosmic; urgency=medium * Fix build failure in the proper way, with upstream gnulib patch LP: #1813587 -- Gianfranco Costamagna Wed, 27 Mar 2019 12:39:19 +0100 ** Changed in: libidn (Ubuntu Cosmic) Status: Fix Committed => Fix Released ** Changed in: libidn (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libidn in Ubuntu. https://bugs.launchpad.net/bugs/1813587 Title: libunistring and libidn ftbfs on 18.04 LTS Status in libidn package in Ubuntu: Fix Released Status in libunistring package in Ubuntu: Fix Released Status in libidn source package in Bionic: Fix Released Status in libunistring source package in Bionic: Fix Released Status in libidn source package in Cosmic: Fix Released Status in libunistring source package in Cosmic: Fix Released Status in libunistring package in Debian: New Bug description: Impact -- libunistring doesn't build from source which means someone would need to fix that problem before fixing any bugs in the libunistring package for Ubuntu 18.04 LTS. Test Case - Does libunistring build successfully? Regression Potential We are simply backporting the workaround we applied in Ubuntu 19.04. Original Bug Report --- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libunistring ftbfs. FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1813587/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813587] Re: libunistring and libidn ftbfs on 18.04 LTS
This bug was fixed in the package libidn - 1.33-2.1ubuntu1.2 --- libidn (1.33-2.1ubuntu1.2) bionic; urgency=medium * Fix build failure in the proper way, with upstream gnulib patch LP: #1813587 -- Gianfranco Costamagna Thu, 21 Mar 2019 10:33:11 +0100 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libidn in Ubuntu. https://bugs.launchpad.net/bugs/1813587 Title: libunistring and libidn ftbfs on 18.04 LTS Status in libidn package in Ubuntu: Fix Released Status in libunistring package in Ubuntu: Fix Released Status in libidn source package in Bionic: Fix Released Status in libunistring source package in Bionic: Fix Released Status in libidn source package in Cosmic: Fix Released Status in libunistring source package in Cosmic: Fix Released Status in libunistring package in Debian: New Bug description: Impact -- libunistring doesn't build from source which means someone would need to fix that problem before fixing any bugs in the libunistring package for Ubuntu 18.04 LTS. Test Case - Does libunistring build successfully? Regression Potential We are simply backporting the workaround we applied in Ubuntu 19.04. Original Bug Report --- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libunistring ftbfs. FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1813587/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell
Confirmed the same problem, ubuntu 18.04.2 LTS AMD64, when trying to connect to "eduroam" in several sites in several countries. I have to say this is pretty annoying. Same message as mentioned before: 124171.865640] wlan0: Limiting TX power to 20 (20 - 0) dBm as advertised by ac:a3:1e:c5:84:a0 [124189.157396] wlan0: deauthenticating from ac:a3:1e:c5:84:a0 by local choice (Reason: 3=DEAUTH_LEAVING) [124204.151294] wlan0: authenticate with ac:a3:1e:c5:d2:b0 [124204.167379] wlan0: send auth to ac:a3:1e:c5:d2:b0 (try 1/3) [124204.168385] wlan0: authenticated [124204.169459] wlan0: associate with ac:a3:1e:c5:d2:b0 (try 1/3) [124204.170668] wlan0: RX AssocResp from ac:a3:1e:c5:d2:b0 (capab=0x11 status=0 aid=2) [124204.170857] wlan0: associated then 124204.246197] wlan0: Limiting TX power to 30 (30 - 0) dBm as advertised by ac:a3:1e:c5:d2:b0 [124207.414305] wlan0: deauthenticating from ac:a3:1e:c5:d2:b0 by local choice (Reason: 3=DEAUTH_LEAVING) [124225.872935] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready -- 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/1748839 Title: Problem to connect to WPA2/PEAP WIFI - gnome-shell Status in network-manager package in Ubuntu: Confirmed Bug description: This problem is also happened on my desktop. After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC could not connect and authenticate on WiFi with WPA2/PEAP/MSCHAPv2/no CA certificate/true username and password. I tried to solve the problem following URL link; however, it could not help me also. https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c My PC is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, OS: Ubuntu 18.04.1 (64-bit). root@joe-UBTPC:/root # lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5) 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5) 00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05) 03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748839/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823516] Re: Nvidia driver installed but X apps are using software rendering (LLVMpipe/Mesa) in Wayland sessions
** Summary changed: - Nvidia driver installed but apps are using LLVMpipe/Mesa in Wayland sessions + Nvidia driver installed but X apps are using software rendering (LLVMpipe/Mesa) in Wayland sessions ** Changed in: xorg-server (Ubuntu) Importance: Undecided => High ** Changed in: xorg-server (Ubuntu) Status: Confirmed => Triaged ** Tags added: performance ** Summary changed: - Nvidia driver installed but X apps are using software rendering (LLVMpipe/Mesa) in Wayland sessions + Nvidia driver installed but X apps are using software rendering (LLVMpipe) in Wayland sessions ** Description changed: - Nvidia-418 installed but apps are using LLVMpipe/Mesa in Wayland - sessions. + Nvidia driver installed but X apps are using software rendering + (LLVMpipe) in Wayland sessions. I am using kernel parameter nvidia-drm.modeset=1, which is required to get the "Ubuntu on Wayland" option. But after logging in I see: $ glxinfo | grep OpenGL OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 8.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 19.0.1 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.1 Mesa 19.0.1 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.0.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: $ es2_info | grep ^GL GL_VERSION: OpenGL ES 3.0 Mesa 19.0.1 GL_RENDERER: llvmpipe (LLVM 8.0, 256 bits) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nvidia-driver-418 418.56-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 Date: Sun Apr 7 17:26:07 2019 InstallationDate: Installed on 2018-12-04 (124 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: nvidia-graphics-drivers-418 UpgradeStatus: No upgrade log present (probably fresh install) ** Tags added: nvidia -- 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/1823516 Title: Nvidia driver installed but X apps are using software rendering (LLVMpipe) in Wayland sessions Status in mesa package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in nvidia-graphics-drivers-418 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Triaged Bug description: Nvidia driver installed but X apps are using software rendering (LLVMpipe) in Wayland sessions. I am using kernel parameter nvidia-drm.modeset=1, which is required to get the "Ubuntu on Wayland" option. But after logging in I see: $ glxinfo | grep OpenGL OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 8.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 19.0.1 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.1 Mesa 19.0.1 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.0.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: $ es2_info | grep ^GL GL_VERSION: OpenGL ES 3.0 Mesa 19.0.1 GL_RENDERER: llvmpipe (LLVM 8.0, 256 bits) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nvidia-driver-418 418.56-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 Date: Sun Apr 7 17:26:07 2019 InstallationDate: Installed on 2018-12-04 (124 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: nvidia-graphics-drivers-418 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1823516/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1759014] Re: Netplan has no way to control DHCP client
netplan.io 0.96-0ubuntu0.18.04.3 with systemd 237-3ubuntu10.19:
network:
version: 2
ethernets:
ens3:
dhcp4: true
dhcp4-overrides:
use-dns: false
nameservers:
search: [lab, kitchen]
addresses: [8.8.8.8]
match:
macaddress: fa:16:3e:28:d1:28
set-name: ens3
ens4:
dhcp4: true
dhcp4-overrides:
use-routes: false
use-dns: false
route-metric:
match:
macaddress: fa:16:3e:d7:41:1b
set-name: ens4
Works fine, except the known issue with systemd addressed with
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823730.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1759014
Title:
Netplan has no way to control DHCP client
Status in netplan:
Fix Released
Status in netplan.io package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Confirmed
Status in netplan.io source package in Bionic:
Fix Committed
Status in systemd source package in Bionic:
Confirmed
Status in netplan.io source package in Cosmic:
Fix Committed
Status in systemd source package in Cosmic:
Confirmed
Status in netplan.io source package in Disco:
Fix Released
Status in systemd source package in Disco:
Confirmed
Bug description:
[Impact]
DHCP configurations where custom settings (routes, nameservers, etc.) need to
be applied.
[Test case]
1) Configure netplan for the particulars of the network by configuring an
appropriate dhcp{4,6}-override stanza:
network:
version: 2
ethernets:
engreen:
dhcp4: true
dhcp4-overrides:
use-dns: false
use-routes: false
route-metric:
Additionally, if so required, add a custom DNS / routes to the
configuration. e.g.
nameservers:
search: [lab, kitchen]
addresses: [8.8.8.8]
(See https://netplan.io/reference#dhcp-overrides for the available
options)
2) Run 'netplan apply' or reboot to have the configuration applied.
3) Validate that the routes / DNS are properly ignored and/or replaced by the
defined values.
[Regression potential]
Minimal; this adds new values to the configuration generated for networkd or
NetworkManager. Existing configurations will remain unchanged, but new
configurations using the dhcp{4,6}-overrides fields will benefit from
additional flexibility.
---
Currently DHCP appears to be an all or nothing boolean, which is insufficient
for many network configurations.
Ideally all of the DHCP configuration options supported by systemd would also
be supported in netplan:
https://www.freedesktop.org/software/systemd/man/systemd.network.html#%5BDHCP%5D%20Section%20Options
As an example, consider the following netplan configuration:
network:
version: 2
renderer: networkd
ethernets:
enp0s3:
dhcp4: yes
nameservers: [8.8.8.8,8.8.4.4]
After running netplan apply I check the nameservers with systemd-
resolve --status and it shows:
DNS Servers: 8.8.8.8
8.8.4.4
192.168.1.1
Here, "192.168.1.1" was provided by my DHCP server. On this
particular node, I only want the manually configured DNS servers, but
netplan has no way to indicate this.
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1759014/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1733435] Re: systemd-resolved does not work with unicast .local subdomains
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/1733435 Title: systemd-resolved does not work with unicast .local subdomains Status in systemd package in Ubuntu: Confirmed Bug description: My local network uses (it's being phased out slowly) XXX.cmu.local DNS names for systems on non-routable networks. After upgrading from zesty to artful, my system is not able to resolve those names anymore, even after removing libnss-mdns again. dig reports that systemd-resolved is returning SERVFAIL This seems to be the same as this upstream report, which was allegedly fixed. https://github.com/systemd/systemd/issues/5048 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12.1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.7-0ubuntu3.4 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Nov 20 17:30:30 2017 InstallationDate: Installed on 2016-12-06 (349 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. OptiPlex 9020 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/sys-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-11-17 (2 days ago) dmi.bios.date: 12/05/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0PC5F7 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd12/05/2013:svnDellInc.:pnOptiPlex9020:pvr01:rvnDellInc.:rn0PC5F7:rvrA03:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 9020 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1733435/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818814] Re: systemd-tmpfiles-setup.services fails to create /var/run directories
** Attachment added: "find_run_ls_after_reboot.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818814/+attachment/5254877/+files/find_run_ls_after_reboot.txt ** Changed in: systemd (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1818814 Title: systemd-tmpfiles-setup.services fails to create /var/run directories Status in systemd package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description:Ubuntu 16.04.6 LTS Release:16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center systemd: Installed: 229-4ubuntu21.16 Candidate: 229-4ubuntu21.16 Version table: *** 229-4ubuntu21.16 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3) What you expected to happen 4) What happened instead Ubuntu server (running in OpenVZ VPS farm, thus the old kernel version) has been up and running happily, until I performed apt-get upgrade and rebooted the server. After reboot, I could not establish SSH connection to server, port 22 connection was refused. I opened a HTML console to my server instance and checked logs. From the logs, it was shown, that SSH server could not start, as it did not have the /var/run/sshd directory. After scrolling back the /var/log/syslog, I noticed that there were lots of other /var/run subdirectories, which were not created. Here is cut from /var/log/syslog, related to systemd-tmpfiles: ---8<---8<--- Mar 6 12:32:54 vspk systemd-tmpfiles[81]: [/usr/lib/tmpfiles.d/00rsyslog.conf:6] Duplicate line for path "/v ar/log", ignoring. Mar 6 12:32:54 vspk systemd[1]: Starting Raise network interfaces... Mar 6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/named failed: Invalid argument Mar 6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path /var/run/fail2ban: Too many levels of symb olic links Mar 6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path /var/run/screen: Too many levels of symbol ic links Mar 6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path /var/run/sshd: Too many levels of symbolic links Mar 6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path /var/run/sudo: Too many levels of symbolic links Mar 6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path /var/run/sudo/ts: Too many levels of symbo lic links Mar 6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/utmp failed: Invalid argument Mar 6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/systemd/netif failed: Invalid argument Mar 6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/systemd/netif/links failed: Invalid argument Mar 6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/systemd/netif/leases failed: Invalid argument Mar 6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path /var/run/zabbix: Too many levels of symbol ic links
