[Touch-packages] [Bug 1779045] Re: hangs on boot from suspend, does not transition to login
That doesn't look like the right link... Please provide a new image of the problem and/or a more detailed description. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1779045 Title: hangs on boot from suspend, does not transition to login Status in Ubuntu: Incomplete Bug description: rebooted desktop from suspend ~24 hrs. Screens (2 monitors) looked like the image here: https://www.google.com/url?sa=i=j==s=images==rja=8=2ahUKEwjr84KuufXbAhUFY6wKHaUAD_UQjRx6BAgBEAU=http%3A%2F%2Fchortle.ccsu.edu%2FimagePuzzles%2FSection10%2Fsection10puzzles.html=AOvVaw07RS3vqIKnwkN3sD39H0Dg=1530243986234703 with subtle movment occationally. This did not return to the log in screen after 10 minutes. officialkw...@gmail.com if you need any additional information, happy to help. PS. Thank you for all of your hard work, 18.04 is wonderful! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 27 23:51:56 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Cedar [Radeon HD 5000/6000/7350/8350 Series] [1682:304a] InstallationDate: Installed on 2018-05-22 (36 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard p6703w ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=a1a58597-5728-46a4-a46d-2677eaf3db97 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6.05 dmi.board.name: 2AB1 dmi.board.vendor: FOXCONN dmi.board.version: 1.00 dmi.chassis.asset.tag: 4CE10607BB dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6.05:bd01/18/2011:svnHewlett-Packard:pnp6703w:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: p6703w dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1779045/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779045] [NEW] hangs on boot from suspend, does not transition to login
Public bug reported: rebooted desktop from suspend ~24 hrs. Screens (2 monitors) looked like the image here: https://www.google.com/url?sa=i=j==s=images==rja=8=2ahUKEwjr84KuufXbAhUFY6wKHaUAD_UQjRx6BAgBEAU=http%3A%2F%2Fchortle.ccsu.edu%2FimagePuzzles%2FSection10%2Fsection10puzzles.html=AOvVaw07RS3vqIKnwkN3sD39H0Dg=1530243986234703 with subtle movment occationally. This did not return to the log in screen after 10 minutes. officialkw...@gmail.com if you need any additional information, happy to help. PS. Thank you for all of your hard work, 18.04 is wonderful! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 27 23:51:56 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Cedar [Radeon HD 5000/6000/7350/8350 Series] [1682:304a] InstallationDate: Installed on 2018-05-22 (36 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard p6703w ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=a1a58597-5728-46a4-a46d-2677eaf3db97 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6.05 dmi.board.name: 2AB1 dmi.board.vendor: FOXCONN dmi.board.version: 1.00 dmi.chassis.asset.tag: 4CE10607BB dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6.05:bd01/18/2011:svnHewlett-Packard:pnp6703w:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: p6703w dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** 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/1779045 Title: hangs on boot from suspend, does not transition to login Status in xorg package in Ubuntu: New Bug description: rebooted desktop from suspend ~24 hrs. Screens (2 monitors) looked like the image here: https://www.google.com/url?sa=i=j==s=images==rja=8=2ahUKEwjr84KuufXbAhUFY6wKHaUAD_UQjRx6BAgBEAU=http%3A%2F%2Fchortle.ccsu.edu%2FimagePuzzles%2FSection10%2Fsection10puzzles.html=AOvVaw07RS3vqIKnwkN3sD39H0Dg=1530243986234703 with subtle movment occationally. This did not return to the log in screen after 10 minutes. officialkw...@gmail.com if you need any additional information, happy to help. PS. Thank you for all of your hard work, 18.04 is wonderful! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 27 23:51:56 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Cedar [Radeon HD 5000/6000/7350/8350 Series] [1682:304a] InstallationDate: Installed on 2018-05-22 (36 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard p6703w ProcEnviron:
[Touch-packages] [Bug 1749199] Re: purge conf files on removal of upstart (was session fails to start after an upgrade from xenial to bionic)
This bug was fixed in the package ubuntu-release-upgrader - 1:18.10.3 --- ubuntu-release-upgrader (1:18.10.3) cosmic; urgency=medium [ Dimitri John Ledkov ] * Purge obsolete packages, if user agrees to remove obsolete packages. LP: #1749199 * Make dist-upgrade.py work when PWD != datadir, by fixing the logic for finding and loading .release config files with datadir prepended first. [ Brian Murray ] * DistUpgrade/DistUpgradeCache.py: clarify why a package is not removed. -- Brian Murray Wed, 27 Jun 2018 16:34:25 -0700 ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Invalid => Fix Released -- 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/1749199 Title: purge conf files on removal of upstart (was session fails to start after an upgrade from xenial to bionic) Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Fix Released Status in ubuntu-release-upgrader source package in Bionic: Invalid Status in xorg source package in Bionic: Fix Released Bug description: [Testcase] 1. Launch xenial lxd container 2. install x11-common upstart 3. do-release-upgrade to bionic 4. Upgrade to bionic removes upstart 5. upgrade to new x11-common, make sure the upstart snippets are gone from disk: /etc/X11/Xsession.d/00upstart /etc/X11/Xsession.d/99upstart 6. for the new release-upgrader, check that upstart is purged, if user selects to remove packages at the end of the do-release-upgrade. After an upgrade from Xenial to Bionic the session fails to start and returns immediately to the login screen. There is this line in the journal [...] /usr/lib/gdm3/gdm-x-session[3584]: /etc/X11/Xsession.d/99x11-common_start: ligne 5: /sbin/upstart: Aucun fichier ou dossier de ce type (full journal from a failed attempt attached) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.26.1-0ubuntu9 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 Date: Tue Feb 13 15:11:12 2018 InstallationDate: Installed on 2018-02-07 (6 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-02-13 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1749199/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778962] Re: when entering the line of text "if network manager is crashing you can restart it with sudo systemctl restart network-manager; " the editers saves the file as a Amig
I can confirm the bug on 16.04, but it's only nautilus/GTK reporting the file type is "Amiga SoundTracker audio (audio/x-mod)". In a shell it is correctly identified as text: $ file Untitled\ Document\ 1 Untitled Document 1: ASCII text Furthermore, the bug does not seem to exist any more in Ubuntu 18.10. ** Package changed: gedit (Ubuntu) => gtk+3.0 (Ubuntu) ** Changed in: gtk+3.0 (Ubuntu) Status: New => Fix Released ** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: glib2.0 (Ubuntu) Status: New => 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/1778962 Title: when entering the line of text "if network manager is crashing you can restart it with sudo systemctl restart network-manager;" the editers saves the file as a Amiga SoundTracker audio (audio/x-mod) file. Status in glib2.0 package in Ubuntu: Fix Released Status in gtk+3.0 package in Ubuntu: Fix Released Bug description: when entering the line of text "if network manager is crashing you can restart it with sudo systemctl restart network-manager;" the editers saves the file as a Amiga SoundTracker audio (audio/x-mod) file. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gedit 3.18.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jun 27 13:32:25 2018 InstallationDate: Installed on 2018-02-20 (126 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1778962/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1745664] Re: [regression] systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_cln
** No longer affects: systemd -- 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/1745664 Title: [regression] systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_clnttcp_create() Status in systemd package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/54968dedd418de647365aa3f0127906ca9adbfe3 --- configured system to use nis. seems to be crashing when I attempt to use a NIS user account ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 Date: Fri Jan 26 13:45:06 2018 ExecutablePath: /lib/systemd/systemd-logind InstallationDate: Installed on 2018-01-26 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180126) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. Z370 HD3 ProcCmdline: /lib/systemd/systemd-logind ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __libc_connect (fd=39, addr=addr@entry=..., len=len@entry=16) at ../sysdeps/unix/sysv/linux/connect.c:26 __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, prog=prog@entry=10, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27301efc, sendsz=sendsz@entry=400, recvsz=recvsz@entry=400) at clnt_tcp.c:153 __GI___libc_rpc_getport (tottimeout_sec=60, timeout_sec=5, protocol=6, version=2, program=17, address=0x7ffc27302060) at pm_getport.c:106 __GI_pmap_getport (address=address@entry=0x7ffc27302060, program=program@entry=17, version=version@entry=2, protocol=protocol@entry=6) at pm_getport.c:154 __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, prog=prog@entry=17, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27302050, sendsz=sendsz@entry=0, recvsz=recvsz@entry=0) at clnt_tcp.c:136 SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Title: systemd-logind crashed with SIGABRT in __libc_connect() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: Software adm bin daemon lp mail nuucp root scswebadmin sys sysdesign tty uucp dmi.bios.date: 09/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: Z370 HD3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd09/22/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370HD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z370 HD3 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1745664/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778962] [NEW] when entering the line of text "if network manager is crashing you can restart it with sudo systemctl restart network-manager; " the editers saves the file as a Am
You have been subscribed to a public bug: when entering the line of text "if network manager is crashing you can restart it with sudo systemctl restart network-manager;" the editers saves the file as a Amiga SoundTracker audio (audio/x-mod) file. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gedit 3.18.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jun 27 13:32:25 2018 InstallationDate: Installed on 2018-02-20 (126 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- when entering the line of text "if network manager is crashing you can restart it with sudo systemctl restart network-manager;" the editers saves the file as a Amiga SoundTracker audio (audio/x-mod) file. https://bugs.launchpad.net/bugs/1778962 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777099] Re: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1
This bug is missing an SRU test case, which needs to be there before we accept this into bionic-proposed. ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => Incomplete -- 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/1777099 Title: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1 Status in OEM Priority Project: New Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Bionic: Incomplete Bug description: refer to https://github.com/systemd/systemd/issues/6908 we need that solution to make NVIDIA dGPU switching works. impacted issue: https://bugs.launchpad.net/somerville/+bug/1774326 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1777099/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778984] Re: Parse error of /etc/apparmor.d/tunables/home.d/ubuntu after unattended-upgrades
Hi Serge, can you please attach your /etc/apparmor.d/tunables/home.d/ubuntu file? Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1778984 Title: Parse error of /etc/apparmor.d/tunables/home.d/ubuntu after unattended-upgrades Status in apparmor package in Ubuntu: New Bug description: Environment: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.2 LTS" NAME="Ubuntu" VERSION="16.04.2 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.2 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/; SUPPORT_URL="http://help.ubuntu.com/; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial Docker Details: Client: Version: 17.06.2-ce API version: 1.30 Go version: go1.8.3 Git commit: cec0b72 Built:Tue Sep 5 20:00:17 2017 OS/Arch: linux/amd64 Server: Version: 17.06.2-ce API version: 1.30 (minimum version 1.12) Go version: go1.8.3 Git commit: cec0b72 Built:Tue Sep 5 19:59:11 2017 OS/Arch: linux/amd64 Experimental: false Problem: Docker containers will not restart due error /etc/apparmor.d/tunables/home.d/ubuntu at line 7: Found unexpected character: '' How to recreate problem: 1. initiate unattended upgrades: sudo unattened-upgrades -d 2. Wait until Apparmor is installing... Installing new version of config file /etc/init.d/apparmor ... Installing new version of config file /etc/init/apparmor.conf ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd 3. Pull the power from the computer to simulate a complete power failure. 4. Plug the system back in and try to restart a docker container using "sudo docker restart Error upon attempting to restart docker container: Error response from daemon: Cannot restart container updater-nodejs: AppArmor enabled on system but the docker-default profile could not be loaded: running /sbin/apparmor_parser apparmor_parser -Kr /var/lib/docker/tmp/docker-default480199246 failed with output: AppArmor parser error for /var/lib/docker/tmp/docker-default480199246 in /etc/apparmor.d/tunables/home.d/ubuntu at line 7: Found unexpected character: '' error: exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1778984/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1770176] Re: Ubuntu 18.04 - NetworkManager menu items in top right menu behaves very strange.
I am also seeing very similar effects. The menu doesn't show the wifi connection points at all and sometimes the network icon in the top panel disappears completely. As others have found control via Settings works fine. Ubuntu 18.04 on a Lenovo Lifebook. -- 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/1770176 Title: Ubuntu 18.04 - NetworkManager menu items in top right menu behaves very strange. Status in network-manager package in Ubuntu: Confirmed Bug description: In a fresh Ubuntu 18.04 desktop install, I've found a very strange behaviour on my Dell XPS 15. This laptop doesn't have an integrated Ethernet port, so I've to use external USB 3.0 Ethernet adapters. When I boot Ubuntu with the adapter plugged in, the wired connection section in the top right menu doesn't show the "Via cavo collegato" section (in Italian, sorry... maybe in English it is "Through connected cable") in the correct way, often but not every time... The menu section title is sometimes " collegato" and expanding the section it doesn't list all the defined Ethernet connection profiles I've on my machine. To access all profiles and to change it I've to select the "Wired network settings" item in the section and so the system settings window appears and all defined profiles are there (so I can change connection by clicking here). Another strange behaviour occours with the "VPN" section in the same topright menu. I have two VPN profiles defined (one of Cisco type, the other is of OpenVPN type). If I select one of this two profiles, VPN connection is established but the switch button in the menu doesn't reflect the state of the connection. To see the correct state of the VPN connection I've to open the "system settings" window, again. It seems there is some trouble in the topright menu communication with the NetworkManager subsystem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1770176/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778981] Re: package openssh-server 1:7.6p1-4 failed to install/upgrade: instalado openssh-server paquete post-installation guión el subproceso devolvió un error con estado de sa
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: openssh (Ubuntu) Importance: Undecided => Low ** Changed in: openssh (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1778981 Title: package openssh-server 1:7.6p1-4 failed to install/upgrade: instalado openssh-server paquete post-installation guión el subproceso devolvió un error con estado de salida 1 Status in openssh package in Ubuntu: Invalid Bug description: fail to make a directory ProblemType: Package DistroRelease: Ubuntu 18.04 Package: openssh-server 1:7.6p1-4 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: ncurses-term:i386: Install openssh-sftp-server:i386: Install openssh-server:i386: Install ssh-import-id:i386: Install NULL: ConfigurePending Architecture: i386 Date: Wed Jun 27 14:09:07 2018 ErrorMessage: instalado openssh-server paquete post-installation guión el subproceso devolvió un error con estado de salida 1 InstallationDate: Installed on 2018-06-09 (18 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: /etc/ssh/sshd_config: No such file or directory SourcePackage: openssh Title: package openssh-server 1:7.6p1-4 failed to install/upgrade: instalado openssh-server paquete post-installation guión el subproceso devolvió un error con estado de salida 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1778981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1719612] Re: non-us keyboard layout not setup in initramfs
Are we sure that this is fixed? It seems to still be happening. -- 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/1719612 Title: non-us keyboard layout not setup in initramfs Status in console-setup package in Ubuntu: Fix Released Status in console-setup source package in Artful: Triaged Bug description: Description:Ubuntu Artful Aardvark (development branch) Release:17.10 In Artful the /etc/console/cached.kmap.gz file does not exists, in its place, it uses some files with more precise names susch as cached_UTF-8_del.kmap.gz. However the initramfs scripts still uses cached.kmap.gz . The consequence is that the keyboard layout remains US in the initramfs which is a problem for full encrypted installation when entering passphrase. Proposed solution is to make a symbolic link from cached_UTF-8_del.kmap.gz to cached.kmap.gz. Then the initramfs tools will find the /etc/console/cached.kmap.gz file and includes it in the initramfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1719612/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778800] Re: package unattended-upgrades 1.1ubuntu1.18.04.1 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error ex
Fix is pending: https://github.com/mvo5/unattended-upgrades/pull/130 -- 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/1778800 Title: package unattended-upgrades 1.1ubuntu1.18.04.1 failed to install/upgrade: installed unattended-upgrades package post- installation script subprocess returned error exit status 1 Status in unattended-upgrades package in Ubuntu: In Progress Bug description: update did not install. a similar thing has happened with several apps have tried to download and the OS wont install them for some reason. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 26 22:26:14 2018 ErrorMessage: installed unattended-upgrades package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-06-08 (18 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: unattended-upgrades Title: package unattended-upgrades 1.1ubuntu1.18.04.1 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "0"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "1"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-06-09T09:48:10.967920 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1778800/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778981] [NEW] package openssh-server 1:7.6p1-4 failed to install/upgrade: instalado openssh-server paquete post-installation guión el subproceso devolvió un error con estado de
Public bug reported: fail to make a directory ProblemType: Package DistroRelease: Ubuntu 18.04 Package: openssh-server 1:7.6p1-4 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: ncurses-term:i386: Install openssh-sftp-server:i386: Install openssh-server:i386: Install ssh-import-id:i386: Install NULL: ConfigurePending Architecture: i386 Date: Wed Jun 27 14:09:07 2018 ErrorMessage: instalado openssh-server paquete post-installation guión el subproceso devolvió un error con estado de salida 1 InstallationDate: Installed on 2018-06-09 (18 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: /etc/ssh/sshd_config: No such file or directory SourcePackage: openssh Title: package openssh-server 1:7.6p1-4 failed to install/upgrade: instalado openssh-server paquete post-installation guión el subproceso devolvió un error con estado de salida 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package bionic i386 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1778981 Title: package openssh-server 1:7.6p1-4 failed to install/upgrade: instalado openssh-server paquete post-installation guión el subproceso devolvió un error con estado de salida 1 Status in openssh package in Ubuntu: New Bug description: fail to make a directory ProblemType: Package DistroRelease: Ubuntu 18.04 Package: openssh-server 1:7.6p1-4 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: ncurses-term:i386: Install openssh-sftp-server:i386: Install openssh-server:i386: Install ssh-import-id:i386: Install NULL: ConfigurePending Architecture: i386 Date: Wed Jun 27 14:09:07 2018 ErrorMessage: instalado openssh-server paquete post-installation guión el subproceso devolvió un error con estado de salida 1 InstallationDate: Installed on 2018-06-09 (18 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: /etc/ssh/sshd_config: No such file or directory SourcePackage: openssh Title: package openssh-server 1:7.6p1-4 failed to install/upgrade: instalado openssh-server paquete post-installation guión el subproceso devolvió un error con estado de salida 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1778981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778984] [NEW] Parse error of /etc/apparmor.d/tunables/home.d/ubuntu after unattended-upgrades
Public bug reported: Environment: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.2 LTS" NAME="Ubuntu" VERSION="16.04.2 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.2 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/; SUPPORT_URL="http://help.ubuntu.com/; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial Docker Details: Client: Version: 17.06.2-ce API version: 1.30 Go version: go1.8.3 Git commit: cec0b72 Built:Tue Sep 5 20:00:17 2017 OS/Arch: linux/amd64 Server: Version: 17.06.2-ce API version: 1.30 (minimum version 1.12) Go version: go1.8.3 Git commit: cec0b72 Built:Tue Sep 5 19:59:11 2017 OS/Arch: linux/amd64 Experimental: false Problem: Docker containers will not restart due error /etc/apparmor.d/tunables/home.d/ubuntu at line 7: Found unexpected character: '' How to recreate problem: 1. initiate unattended upgrades: sudo unattened-upgrades -d 2. Wait until Apparmor is installing... Installing new version of config file /etc/init.d/apparmor ... Installing new version of config file /etc/init/apparmor.conf ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd 3. Pull the power from the computer to simulate a complete power failure. 4. Plug the system back in and try to restart a docker container using "sudo docker restart Error upon attempting to restart docker container: Error response from daemon: Cannot restart container updater-nodejs: AppArmor enabled on system but the docker-default profile could not be loaded: running /sbin/apparmor_parser apparmor_parser -Kr /var/lib/docker/tmp/docker-default480199246 failed with output: AppArmor parser error for /var/lib/docker/tmp/docker-default480199246 in /etc/apparmor.d/tunables/home.d/ubuntu at line 7: Found unexpected character: '' error: exit status 1 ** 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/1778984 Title: Parse error of /etc/apparmor.d/tunables/home.d/ubuntu after unattended-upgrades Status in apparmor package in Ubuntu: New Bug description: Environment: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.2 LTS" NAME="Ubuntu" VERSION="16.04.2 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.2 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/; SUPPORT_URL="http://help.ubuntu.com/; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial Docker Details: Client: Version: 17.06.2-ce API version: 1.30 Go version: go1.8.3 Git commit: cec0b72 Built:Tue Sep 5 20:00:17 2017 OS/Arch: linux/amd64 Server: Version: 17.06.2-ce API version: 1.30 (minimum version 1.12) Go version: go1.8.3 Git commit: cec0b72 Built:Tue Sep 5 19:59:11 2017 OS/Arch: linux/amd64 Experimental: false Problem: Docker containers will not restart due error /etc/apparmor.d/tunables/home.d/ubuntu at line 7: Found unexpected character: '' How to recreate problem: 1. initiate unattended upgrades: sudo unattened-upgrades -d 2. Wait until Apparmor is installing... Installing new version of config file /etc/init.d/apparmor ... Installing new version of config file /etc/init/apparmor.conf ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd 3. Pull the power from the computer to simulate a complete power failure. 4. Plug the system back in and try to restart a docker container using "sudo docker restart Error upon attempting to restart docker container: Error response from daemon: Cannot restart container updater-nodejs: AppArmor enabled on system but the docker-default profile could not be loaded: running /sbin/apparmor_parser apparmor_parser -Kr /var/lib/docker/tmp/docker-default480199246 failed with output: AppArmor parser error for /var/lib/docker/tmp/docker-default480199246 in /etc/apparmor.d/tunables/home.d/ubuntu at line 7: Found unexpected character: '' error: exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1778984/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778800] Re: package unattended-upgrades 1.1ubuntu1.18.04.1 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error ex
Could you please confirm that the installation failure happened during shutdown? In that case this is a duplicate of LP: #1778219. DpkgTerminalLog.txt: Setting up unattended-upgrades (1.1ubuntu1.18.04.1) ... Failed to start unattended-upgrades.service: Connection timed out See system logs and 'systemctl status unattended-upgrades.service' for details. invoke-rc.d: initscript unattended-upgrades, action "start" failed. [0;1;32m●[0m unattended-upgrades.service - Unattended Upgrades Shutdown Loaded: loaded (/lib/systemd/system/unattended-upgrades.service; enabled; vendor preset: enabled) Active: [0;1;32mactive (running)[0m since Mon 2018-06-25 07:02:10 BST; 1 day 15h ago Docs: man:unattended-upgrade(8) CGroup: /system.slice/unattended-upgrades.service Failed to dump process list, ignoring: No such file or directory dpkg: error processing package unattended-upgrades (--configure): installed unattended-upgrades package post-installation script subprocess returned error exit status 1 ... however there is a little twist, since in u-u's case the debhelper- added service start is not needed and I'm fixing that. ** Changed in: unattended-upgrades (Ubuntu) Status: New => In Progress -- 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/1778800 Title: package unattended-upgrades 1.1ubuntu1.18.04.1 failed to install/upgrade: installed unattended-upgrades package post- installation script subprocess returned error exit status 1 Status in unattended-upgrades package in Ubuntu: In Progress Bug description: update did not install. a similar thing has happened with several apps have tried to download and the OS wont install them for some reason. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 26 22:26:14 2018 ErrorMessage: installed unattended-upgrades package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-06-08 (18 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: unattended-upgrades Title: package unattended-upgrades 1.1ubuntu1.18.04.1 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "0"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "1"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-06-09T09:48:10.967920 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1778800/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778969] Re: package gir1.2-gstreamer-1.0 1.14.0-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuratio
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1778969 Title: package gir1.2-gstreamer-1.0 1.14.0-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in gstreamer1.0 package in Ubuntu: New Bug description: when trying to uninstall a software "krita" I encounter this problem. It said "the package is in a very bad inconsistent state, you should try to reinstall it." ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gir1.2-gstreamer-1.0 1.14.0-1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: krita:amd64: Purge NULL: ConfigurePending NULL: PurgePending NULL: ConfigurePending Architecture: amd64 Date: Thu Jun 28 00:52:40 2018 DuplicateSignature: package:gir1.2-gstreamer-1.0:1.14.0-1 Processing triggers for gnome-menus (3.13.3-11ubuntu1) ... dpkg: error processing package gir1.2-gstreamer-1.0 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: gstreamer1.0 Title: package gir1.2-gstreamer-1.0 1.14.0-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1778969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778969] [NEW] package gir1.2-gstreamer-1.0 1.14.0-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurat
Public bug reported: when trying to uninstall a software "krita" I encounter this problem. It said "the package is in a very bad inconsistent state, you should try to reinstall it." ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gir1.2-gstreamer-1.0 1.14.0-1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: krita:amd64: Purge NULL: ConfigurePending NULL: PurgePending NULL: ConfigurePending Architecture: amd64 Date: Thu Jun 28 00:52:40 2018 DuplicateSignature: package:gir1.2-gstreamer-1.0:1.14.0-1 Processing triggers for gnome-menus (3.13.3-11ubuntu1) ... dpkg: error processing package gir1.2-gstreamer-1.0 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: gstreamer1.0 Title: package gir1.2-gstreamer-1.0 1.14.0-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1778969 Title: package gir1.2-gstreamer-1.0 1.14.0-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in gstreamer1.0 package in Ubuntu: New Bug description: when trying to uninstall a software "krita" I encounter this problem. It said "the package is in a very bad inconsistent state, you should try to reinstall it." ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gir1.2-gstreamer-1.0 1.14.0-1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: krita:amd64: Purge NULL: ConfigurePending NULL: PurgePending NULL: ConfigurePending Architecture: amd64 Date: Thu Jun 28 00:52:40 2018 DuplicateSignature: package:gir1.2-gstreamer-1.0:1.14.0-1 Processing triggers for gnome-menus (3.13.3-11ubuntu1) ... dpkg: error processing package gir1.2-gstreamer-1.0 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: gstreamer1.0 Title: package gir1.2-gstreamer-1.0 1.14.0-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1778969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 795900] Re: [CA0106 - CA0106, playback] No sound at all
computer suddenly lost audio while playing youtube video, unmute does not work. it was working this morning. OS is Bionic Beaver -- 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/795900 Title: [CA0106 - CA0106, playback] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Hi, I have a system that has lost sound twice. First I upgraded från 10.? to 11.04. Everything was fine. Then suddenly my sound stops working. After some time and changing settings I decide to do a clean 11.04 install. Great! My sound is back. A week later : same problem again. What can I do to reset the sound system without having to reinstall? Yes I have tried alsamixer and other tips from the sound wiki. One thing that might have triggered the problem: I muted my sound yesterday (it was working) and turned the computer off for the night with that setting. Then when I rebooted today and the volume icon was showing muted. So I unmuted but still nothing. When my system boots I here a click from the speakers when the sound card is detected. When the drumroll is supposed to be played at login I get a short bzzt when the system can't play sound. I login and get another bzzt. Otherwise the speakers are silent. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: alsa-base 1.0.24+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-10.44-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: johanf 3224 F pulseaudio Card0.Amixer.info: Card hw:0 'CA0106'/'Audigy SE [SB0570] at 0xec00 irq 17' Mixer name : 'CA0106' Components : '' Controls : 35 Simple ctrls : 18 CurrentDmesg: [ 72.266824] EXT4-fs (sdc1): re-mounted. Opts: commit=0 [ 75.680814] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro,commit=0 [ 75.682797] EXT4-fs (sdc1): re-mounted. Opts: commit=0 Date: Sat Jun 11 13:07:08 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427) PackageArchitecture: all ProcEnviron: LANGUAGE=sv_SE:en PATH=(custom, user) LANG=sv_SE.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:CA0106 failed Symptom_Card: CA0106 Soundblaster - CA0106 Symptom_DevicesInUse: 3224 Symptom_Type: No sound at all Title: [CA0106 - CA0106, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1104 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q-PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1104:bd07/31/2008:svnSystemmanufacturer:pnP5Q-PRO:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5Q-PRO dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/795900/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778960] [NEW] SRU: Update python 2.7 to the final 2.7.15 release
Public bug reported: Ubuntu 18.04 LTS shipped with the python 2.7.15 release candidate. Please let's update to the final release. Upstream changes are: - bpo-33374: Tweak the definition of PyGC_Head, so compilers do not believe it is always 16-byte aligned on x86. This prevents crashes with more aggressive optimizations present in GCC 8. - Identify as 2.7.15 instead of 2.7.15rc1 Acceptance criteria: The package builds, and the testsuite doesn't show regressions. ** Affects: python2.7 (Ubuntu) Importance: Undecided Status: New -- 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/1778960 Title: SRU: Update python 2.7 to the final 2.7.15 release Status in python2.7 package in Ubuntu: New Bug description: Ubuntu 18.04 LTS shipped with the python 2.7.15 release candidate. Please let's update to the final release. Upstream changes are: - bpo-33374: Tweak the definition of PyGC_Head, so compilers do not believe it is always 16-byte aligned on x86. This prevents crashes with more aggressive optimizations present in GCC 8. - Identify as 2.7.15 instead of 2.7.15rc1 Acceptance criteria: The package builds, and the testsuite doesn't show regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1778960/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778908] Re: 16.04 libtag dependancy issues
Why does Launchpad not recognise Launchpad's bug tracker when you try and associate another package as being affected? I wanted to correctly link this bug on the Mixxx tracker but it throws up an error of unrecognise bug tracker!! https://bugs.launchpad.net/mixxx/+bug/1778950 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to taglib in Ubuntu. https://bugs.launchpad.net/bugs/1778908 Title: 16.04 libtag dependancy issues Status in taglib package in Ubuntu: New Bug description: This issue has come up from trying to install Mixxx from their official LaunchPad host ppa and it appears to reference libtag1-vanilla, which does appear to exist in 16.04 but I believe should be superseded by libtag1v5-vanilla, yet it doesn't seem to recognise as such. As it then can't be manually installed or the other removed I think there is a deeper issue with this package than just Mixxx having the wrong one down as a dependency. This has been reported to the Mixxx developers on their forum about a week ago but no official response as yet... I've run this in a virtual box but there are multiple users who have reported this on their main systems (at least four I've seen.) osboxes@osboxes:~$ sudo apt-get update [sudo] password for osboxes: Hit:1 http://security.ubuntu.com/ubuntu xenial-security InRelease Hit:2 http://ppa.launchpad.net/mixxx/mixxx/ubuntu xenial InRelease Hit:3 http://us.archive.ubuntu.com/ubuntu xenial InRelease Hit:4 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease Hit:5 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease Reading package lists... Done osboxes@osboxes:~$ sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. osboxes@osboxes:~$ sudo apt-get install mixxx Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: mixxx : Depends: libtag1-vanilla (>= 1.10-0ubuntu1~xenial0) but it is not going to be installed E: Unable to correct problems, you have held broken packages. osboxes@osboxes:~$ sudo apt-get install libtag1-vanilla Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libcheese8 : Depends: gstreamer1.0-plugins-good (>= 0.11.0) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. osboxes@osboxes:~$ sudo apt-get install gstreamer1.0-plugins-good Reading package lists... Done Building dependency tree Reading state information... Done gstreamer1.0-plugins-good is already the newest version (1.8.3-1ubuntu0.4). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. osboxes@osboxes:~$ sudo apt-get remove libtag1v5-vanilla Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: indicator-bluetooth : Depends: unity-control-center but it is not going to be installed or gnome-control-center but it is not going to be installed or ubuntu-system-settings but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. osboxes@osboxes:~$ sudo apt-get remove libtag1v5 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages
[Touch-packages] [Bug 1778936] Re: please re-add Support-system-image-read-only-etc.patch
** Tags added: patch -- 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/1778936 Title: please re-add Support-system-image-read-only-etc.patch Status in systemd package in Ubuntu: New Status in systemd source package in Bionic: New Status in systemd source package in Cosmic: New Bug description: The 16.04 version of systemd had a patch to support the read-only etc. For core18 we will also need this change because core18 is still not on a fully writable etc. I will attach a debdiff against the current bionic version of systemd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778936/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710750] Re: session hangs on logout
Forgot to mention that I am running Ubuntu 18.04 using the Gnome X session, but I also tested the Ubuntu X session and Ubuntu Wayland sessions. -- 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/1710750 Title: session hangs on logout Status in systemd package in Ubuntu: Confirmed Bug description: Every session I've tried, in 17.10 (gnome, gnome classic, gnome wayland, budgie, cinnamon, cinnamon software rending) Hangs the system when I go to log out or shutdown. sometimes it completes sometimes I have to restart lightdm from a tty. but gnome locks the session bus then and a restart is required to fix it. system is ryzen 1600x rx580 on amdgpu. I can't even find to logs, the log file viewer only holds logs since boot no previous boots. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1710750/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710750] Re: session hangs on logout
With only one user, if I logout, X hangs -- can't even get a console with ctrl-alt-f3. Also, if I need to restart X with ctrl-alt-backspace, it hangs. I am able to ssh into the machine and restart gdm3, and that allows me to log back in. I added another user to see if I had a problem with a config related to my user. Just adding another user to the system has halted the hangs. I can now logout and restart X without issue. I am not sure what logs to attach, because I haven't been able to find any indication of a problem other than X hanging. -- 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/1710750 Title: session hangs on logout Status in systemd package in Ubuntu: Confirmed Bug description: Every session I've tried, in 17.10 (gnome, gnome classic, gnome wayland, budgie, cinnamon, cinnamon software rending) Hangs the system when I go to log out or shutdown. sometimes it completes sometimes I have to restart lightdm from a tty. but gnome locks the session bus then and a restart is required to fix it. system is ryzen 1600x rx580 on amdgpu. I can't even find to logs, the log file viewer only holds logs since boot no previous boots. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1710750/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778946] [NEW] No dns resolution after closing a vpn/pptp connection
Public bug reported: step to reproduce set a VPN connection configured to connect a Microsoft vpn server (pptp) internet acces is ok enable the vpn connection using the applet on the top right corner of the desktop internet still ok ping works disable the vpn connection ping doesn't works with a host but works if i specify an ip address ping: xx.net: Nom ou service inconnu As a workaround, i disable the ethernet link and re-enable it name resolution is now ok ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 27 18:09:30 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-06-03 (1484 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IpRoute: default via 192.168.0.254 dev eth0 proto dhcp metric 20100 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100 IwConfig: lono wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Connexion filaire 1 94806bba-1c68-46b6-87f4-a3aff6dd /org/freedesktop/NetworkManager/ActiveConnection/6 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected (site only) started limited enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1778946 Title: No dns resolution after closing a vpn/pptp connection Status in network-manager package in Ubuntu: New Bug description: step to reproduce set a VPN connection configured to connect a Microsoft vpn server (pptp) internet acces is ok enable the vpn connection using the applet on the top right corner of the desktop internet still ok ping works disable the vpn connection ping doesn't works with a host but works if i specify an ip address ping: xx.net: Nom ou service inconnu As a workaround, i disable the ethernet link and re-enable it name resolution is now ok ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 27 18:09:30 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-06-03 (1484 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IpRoute: default via 192.168.0.254 dev eth0 proto dhcp metric 20100 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100 IwConfig: lono wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Connexion filaire 1 94806bba-1c68-46b6-87f4-a3aff6dd /org/freedesktop/NetworkManager/ActiveConnection/6 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6
[Touch-packages] [Bug 1778944] Re: package libssl-doc 1.1.0g-2ubuntu4 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal: sudo apt-get clean Then try performing the update again. This will likely resolve your issue, but the failure could be caused by filesystem or memory corruption. So please also run a fsck on your filesystem(s) and a memory test. Thanks in advance! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: fsys-tarfile-error ** Changed in: openssl (Ubuntu) Status: New => Invalid -- 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/1778944 Title: package libssl-doc 1.1.0g-2ubuntu4 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 Status in openssl package in Ubuntu: Invalid Bug description: Package fails ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libssl-doc 1.1.0g-2ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jun 27 17:59:50 2018 Dependencies: DpkgHistoryLog: Start-Date: 2018-06-27 17:59:48 Requested-By: pj (1000) Upgrade: openssl:amd64 (1.1.0g-2ubuntu4, 1.1.0g-2ubuntu4.1), libssl-dev:amd64 (1.1.0g-2ubuntu4, 1.1.0g-2ubuntu4.1), libssl-doc:amd64 (1.1.0g-2ubuntu4, 1.1.0g-2ubuntu4.1), bsdutils:amd64 (1:2.31.1-0.4ubuntu3.1, 1:2.31.1-0.4ubuntu3.1), libssl1.1:amd64 (1.1.0g-2ubuntu4, 1.1.0g-2ubuntu4.1), libssl1.0.0:amd64 (1.0.2n-1ubuntu5, 1.0.2n-1ubuntu5.1) Remove: shutter:amd64 (0.94-1) ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 InstallationDate: Installed on 2018-01-14 (163 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: openssl Title: package libssl-doc 1.1.0g-2ubuntu4 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1778944/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778908] Re: 16.04 libtag dependancy issues
Ahhh obviously fully Mixxx's fault, just realised the libtag version it fails to downgrade to is in their ppa and not the Ubuntu repo looking at the apt-cache policy output. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to taglib in Ubuntu. https://bugs.launchpad.net/bugs/1778908 Title: 16.04 libtag dependancy issues Status in taglib package in Ubuntu: New Bug description: This issue has come up from trying to install Mixxx from their official LaunchPad host ppa and it appears to reference libtag1-vanilla, which does appear to exist in 16.04 but I believe should be superseded by libtag1v5-vanilla, yet it doesn't seem to recognise as such. As it then can't be manually installed or the other removed I think there is a deeper issue with this package than just Mixxx having the wrong one down as a dependency. This has been reported to the Mixxx developers on their forum about a week ago but no official response as yet... I've run this in a virtual box but there are multiple users who have reported this on their main systems (at least four I've seen.) osboxes@osboxes:~$ sudo apt-get update [sudo] password for osboxes: Hit:1 http://security.ubuntu.com/ubuntu xenial-security InRelease Hit:2 http://ppa.launchpad.net/mixxx/mixxx/ubuntu xenial InRelease Hit:3 http://us.archive.ubuntu.com/ubuntu xenial InRelease Hit:4 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease Hit:5 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease Reading package lists... Done osboxes@osboxes:~$ sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. osboxes@osboxes:~$ sudo apt-get install mixxx Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: mixxx : Depends: libtag1-vanilla (>= 1.10-0ubuntu1~xenial0) but it is not going to be installed E: Unable to correct problems, you have held broken packages. osboxes@osboxes:~$ sudo apt-get install libtag1-vanilla Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libcheese8 : Depends: gstreamer1.0-plugins-good (>= 0.11.0) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. osboxes@osboxes:~$ sudo apt-get install gstreamer1.0-plugins-good Reading package lists... Done Building dependency tree Reading state information... Done gstreamer1.0-plugins-good is already the newest version (1.8.3-1ubuntu0.4). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. osboxes@osboxes:~$ sudo apt-get remove libtag1v5-vanilla Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: indicator-bluetooth : Depends: unity-control-center but it is not going to be installed or gnome-control-center but it is not going to be installed or ubuntu-system-settings but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. osboxes@osboxes:~$ sudo apt-get remove libtag1v5 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to
[Touch-packages] [Bug 1710750] Re: session hangs on logout
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/1710750 Title: session hangs on logout Status in systemd package in Ubuntu: Confirmed Bug description: Every session I've tried, in 17.10 (gnome, gnome classic, gnome wayland, budgie, cinnamon, cinnamon software rending) Hangs the system when I go to log out or shutdown. sometimes it completes sometimes I have to restart lightdm from a tty. but gnome locks the session bus then and a restart is required to fix it. system is ryzen 1600x rx580 on amdgpu. I can't even find to logs, the log file viewer only holds logs since boot no previous boots. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1710750/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778944] Re: package libssl-doc 1.1.0g-2ubuntu4 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
** Tags removed: need-duplicate-check -- 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/1778944 Title: package libssl-doc 1.1.0g-2ubuntu4 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 Status in openssl package in Ubuntu: Invalid Bug description: Package fails ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libssl-doc 1.1.0g-2ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jun 27 17:59:50 2018 Dependencies: DpkgHistoryLog: Start-Date: 2018-06-27 17:59:48 Requested-By: pj (1000) Upgrade: openssl:amd64 (1.1.0g-2ubuntu4, 1.1.0g-2ubuntu4.1), libssl-dev:amd64 (1.1.0g-2ubuntu4, 1.1.0g-2ubuntu4.1), libssl-doc:amd64 (1.1.0g-2ubuntu4, 1.1.0g-2ubuntu4.1), bsdutils:amd64 (1:2.31.1-0.4ubuntu3.1, 1:2.31.1-0.4ubuntu3.1), libssl1.1:amd64 (1.1.0g-2ubuntu4, 1.1.0g-2ubuntu4.1), libssl1.0.0:amd64 (1.0.2n-1ubuntu5, 1.0.2n-1ubuntu5.1) Remove: shutter:amd64 (0.94-1) ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 InstallationDate: Installed on 2018-01-14 (163 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: openssl Title: package libssl-doc 1.1.0g-2ubuntu4 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1778944/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1745664] Re: [regression] systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_cln
** Changed in: systemd Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1745664 Title: [regression] systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_clnttcp_create() Status in systemd: Fix Released Status in systemd package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/54968dedd418de647365aa3f0127906ca9adbfe3 --- configured system to use nis. seems to be crashing when I attempt to use a NIS user account ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 Date: Fri Jan 26 13:45:06 2018 ExecutablePath: /lib/systemd/systemd-logind InstallationDate: Installed on 2018-01-26 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180126) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. Z370 HD3 ProcCmdline: /lib/systemd/systemd-logind ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __libc_connect (fd=39, addr=addr@entry=..., len=len@entry=16) at ../sysdeps/unix/sysv/linux/connect.c:26 __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, prog=prog@entry=10, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27301efc, sendsz=sendsz@entry=400, recvsz=recvsz@entry=400) at clnt_tcp.c:153 __GI___libc_rpc_getport (tottimeout_sec=60, timeout_sec=5, protocol=6, version=2, program=17, address=0x7ffc27302060) at pm_getport.c:106 __GI_pmap_getport (address=address@entry=0x7ffc27302060, program=program@entry=17, version=version@entry=2, protocol=protocol@entry=6) at pm_getport.c:154 __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, prog=prog@entry=17, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27302050, sendsz=sendsz@entry=0, recvsz=recvsz@entry=0) at clnt_tcp.c:136 SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Title: systemd-logind crashed with SIGABRT in __libc_connect() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: Software adm bin daemon lp mail nuucp root scswebadmin sys sysdesign tty uucp dmi.bios.date: 09/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: Z370 HD3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd09/22/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370HD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z370 HD3 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1745664/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778944] [NEW] package libssl-doc 1.1.0g-2ubuntu4 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
Public bug reported: Package fails ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libssl-doc 1.1.0g-2ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jun 27 17:59:50 2018 Dependencies: DpkgHistoryLog: Start-Date: 2018-06-27 17:59:48 Requested-By: pj (1000) Upgrade: openssl:amd64 (1.1.0g-2ubuntu4, 1.1.0g-2ubuntu4.1), libssl-dev:amd64 (1.1.0g-2ubuntu4, 1.1.0g-2ubuntu4.1), libssl-doc:amd64 (1.1.0g-2ubuntu4, 1.1.0g-2ubuntu4.1), bsdutils:amd64 (1:2.31.1-0.4ubuntu3.1, 1:2.31.1-0.4ubuntu3.1), libssl1.1:amd64 (1.1.0g-2ubuntu4, 1.1.0g-2ubuntu4.1), libssl1.0.0:amd64 (1.0.2n-1ubuntu5, 1.0.2n-1ubuntu5.1) Remove: shutter:amd64 (0.94-1) ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 InstallationDate: Installed on 2018-01-14 (163 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: openssl Title: package libssl-doc 1.1.0g-2ubuntu4 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- 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/1778944 Title: package libssl-doc 1.1.0g-2ubuntu4 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 Status in openssl package in Ubuntu: New Bug description: Package fails ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libssl-doc 1.1.0g-2ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jun 27 17:59:50 2018 Dependencies: DpkgHistoryLog: Start-Date: 2018-06-27 17:59:48 Requested-By: pj (1000) Upgrade: openssl:amd64 (1.1.0g-2ubuntu4, 1.1.0g-2ubuntu4.1), libssl-dev:amd64 (1.1.0g-2ubuntu4, 1.1.0g-2ubuntu4.1), libssl-doc:amd64 (1.1.0g-2ubuntu4, 1.1.0g-2ubuntu4.1), bsdutils:amd64 (1:2.31.1-0.4ubuntu3.1, 1:2.31.1-0.4ubuntu3.1), libssl1.1:amd64 (1.1.0g-2ubuntu4, 1.1.0g-2ubuntu4.1), libssl1.0.0:amd64 (1.0.2n-1ubuntu5, 1.0.2n-1ubuntu5.1) Remove: shutter:amd64 (0.94-1) ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 InstallationDate: Installed on 2018-01-14 (163 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: openssl Title: package libssl-doc 1.1.0g-2ubuntu4 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1778944/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386257] Re: intel-microcode should be installed by default, when the CPU is GenuineIntel
@lahtis deb packaging doesn't provide us the granularity to have the kernel packages specifically depend on intel-microcode packages on Intel x86 systems and amd64-microcde on AMD x86 systems. Instead, we have to depend on both packages. If you have an Intel processor, the AMD microcode is not used. If you have an AMD processor, the Intel microcode is not used. The downside here is slightly increased storage requirements to store the unnecessary package on your device (and the bandwidth to download the updates). We apologize for the inconvenience but felt it was warranted in order to get updated microcode deployed to all users in order to address known vulnerabilities in processors. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1386257 Title: intel-microcode should be installed by default, when the CPU is GenuineIntel Status in intel: Fix Released Status in Ubuntu Kylin: Fix Released Status in amd64-microcode package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntukylin-meta package in Ubuntu: Fix Released Bug description: intel-microcode should be installed by default on the bare-metal systems which are running on GenuineIntel CPUs, by the installers. Similarly other microcode packages for other CPUs brands should be considered for inclusion (e.g. amd64-microcode). I hope that ubuntu-drivers-common can gain ability to detect cpu series and/or vendors, packages that provide microcodes similarly declare support for cpu series and/or vendors, the microcode packages are shipped on the CDs in the pool directory, and installed on to the target machines as part of the installation. This should help with rapid correction of bugs and behaviour of the CPUs in the field. 2017 update, amd64-microcode should also be seeded, as it is useful to have it autoinstallable. In the recent years there have been critical CPU security vulnerabilities which got fixed with microcode updates. To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1386257/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386257] Re: intel-microcode should be installed by default, when the CPU is GenuineIntel
@amribrahim1987 you've probably noticed but we have released an amd64-microcode update recently: https://usn.ubuntu.com/3690-1/ Updates for AMD microcode will be provided in the amd64-microcode package and not in linux-firmware. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1386257 Title: intel-microcode should be installed by default, when the CPU is GenuineIntel Status in intel: Fix Released Status in Ubuntu Kylin: Fix Released Status in amd64-microcode package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntukylin-meta package in Ubuntu: Fix Released Bug description: intel-microcode should be installed by default on the bare-metal systems which are running on GenuineIntel CPUs, by the installers. Similarly other microcode packages for other CPUs brands should be considered for inclusion (e.g. amd64-microcode). I hope that ubuntu-drivers-common can gain ability to detect cpu series and/or vendors, packages that provide microcodes similarly declare support for cpu series and/or vendors, the microcode packages are shipped on the CDs in the pool directory, and installed on to the target machines as part of the installation. This should help with rapid correction of bugs and behaviour of the CPUs in the field. 2017 update, amd64-microcode should also be seeded, as it is useful to have it autoinstallable. In the recent years there have been critical CPU security vulnerabilities which got fixed with microcode updates. To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1386257/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1762766] Re: apt-get update hangs when apt-transport-https is not installed
Hello Graham, or anyone else affected, Accepted apt into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.2.27 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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! ** Changed in: apt (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- 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/1762766 Title: apt-get update hangs when apt-transport-https is not installed Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Triaged Status in apt source package in Xenial: Fix Committed Status in apt package in Debian: Fix Released Bug description: When "apt-get update" is run on a docker container running Ubuntu v16.04 and containing an additional apt source repository hosted on an https webserver, the "apt-get update" command hangs. The hang happens after connections to http ubuntu hosts are complete, and apt-get remains stuck on "Working" at 0%. Removing the sources file for the https repo causes apt-get to complete normally. The source file contains 4 separate entries to 4 different repos on the same https server. When the source file is modified so that just *one* entry exists to one repo on the https server, we suddenly get a sensible error message that tells us that apt-transport-https needs to be installed. Installing apt-transport-https into the docker container before adding the sources list to the https servers works around the problem and sanity returns. Key notes: - The use of docker isn't related to the bug, except that the docker image doesn't contain the apt-transport-https package whereas our cloud images do contain this package by default. This can give the impression that this is a docker bug when it's not. - The hang in "apt-get update" seems to occur when the sources file contains more than one entry in the file. When just one entry exists in the file (and all other entries are commented out) a sensible error messages appears. - We encountered this on a host that didn't support cut and paste, sorry :( To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1762766/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778547] Re: Broken system lock counting
Hello Julian, or anyone else affected,
Accepted apt into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.2.27 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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. 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!
** Changed in: apt (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-xenial
** Changed in: apt (Ubuntu Artful)
Status: In Progress => Fix Committed
** Tags added: verification-needed-artful
--
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/1778547
Title:
Broken system lock counting
Status in apt package in Ubuntu:
Fix Committed
Status in apt source package in Xenial:
Fix Committed
Status in apt source package in Artful:
Fix Committed
Status in apt source package in Bionic:
Fix Committed
Bug description:
[Impact]
System lock unrefing is broken, off-by-one error. Locking twice opens a
second fd for the lock file, and the old fd gets lost and remains open for the
remaining duration of the program
[Test case]
Executing the following script should show one lock file in the first
line, and none in the last line.
def maybe_readlink(path):
try:
return os.readlink("/proc/self/fd/" + p)
except:
return ""
import os, apt_pkg
apt_pkg.init()
apt_pkg.pkgsystem_lock()
apt_pkg.pkgsystem_lock()
apt_pkg.pkgsystem_unlock()
apt_pkg.pkgsystem_unlock()
print([(p, maybe_readlink("/proc/self/fd/" + p)) for p in
os.listdir("/proc/self/fd")])
[Test output]
good, cosmic:
[('0', '/dev/pts/2'), ('1', '/dev/pts/2'), ('2', '/dev/pts/2'), ('3',
'/var/lib/dpkg/lock'), ('4', '')]
[('0', '/dev/pts/2'), ('1', '/dev/pts/2'), ('2', '/dev/pts/2'), ('3',
'')]
bad, bionic:
[('0', '/dev/pts/0'), ('1', '/dev/pts/0'), ('2', '/dev/pts/0'), ('3',
'pipe:[40889331]'), ('4', '/var/lib/dpkg/lock'), ('5', '/var/lib/dpkg/lock'),
('6', ''), ('17', 'socket:[53931]')]
[('0', '/dev/pts/0'), ('1', '/dev/pts/0'), ('2', '/dev/pts/0'), ('3',
'pipe:[40889331]'), ('4', '/var/lib/dpkg/lock'), ('5', ''), ('17',
'socket:[53931]')]
[Regression potential]
A locking change can potentially break locking, but this one seems like an
obvious off-by-one error.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1778547/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778547] Please test proposed package
Hello Julian, or anyone else affected,
Accepted apt into artful-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.5.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. 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!
** Changed in: apt (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Tags added: verification-needed-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1778547
Title:
Broken system lock counting
Status in apt package in Ubuntu:
Fix Committed
Status in apt source package in Xenial:
Fix Committed
Status in apt source package in Artful:
Fix Committed
Status in apt source package in Bionic:
Fix Committed
Bug description:
[Impact]
System lock unrefing is broken, off-by-one error. Locking twice opens a
second fd for the lock file, and the old fd gets lost and remains open for the
remaining duration of the program
[Test case]
Executing the following script should show one lock file in the first
line, and none in the last line.
def maybe_readlink(path):
try:
return os.readlink("/proc/self/fd/" + p)
except:
return ""
import os, apt_pkg
apt_pkg.init()
apt_pkg.pkgsystem_lock()
apt_pkg.pkgsystem_lock()
apt_pkg.pkgsystem_unlock()
apt_pkg.pkgsystem_unlock()
print([(p, maybe_readlink("/proc/self/fd/" + p)) for p in
os.listdir("/proc/self/fd")])
[Test output]
good, cosmic:
[('0', '/dev/pts/2'), ('1', '/dev/pts/2'), ('2', '/dev/pts/2'), ('3',
'/var/lib/dpkg/lock'), ('4', '')]
[('0', '/dev/pts/2'), ('1', '/dev/pts/2'), ('2', '/dev/pts/2'), ('3',
'')]
bad, bionic:
[('0', '/dev/pts/0'), ('1', '/dev/pts/0'), ('2', '/dev/pts/0'), ('3',
'pipe:[40889331]'), ('4', '/var/lib/dpkg/lock'), ('5', '/var/lib/dpkg/lock'),
('6', ''), ('17', 'socket:[53931]')]
[('0', '/dev/pts/0'), ('1', '/dev/pts/0'), ('2', '/dev/pts/0'), ('3',
'pipe:[40889331]'), ('4', '/var/lib/dpkg/lock'), ('5', ''), ('17',
'socket:[53931]')]
[Regression potential]
A locking change can potentially break locking, but this one seems like an
obvious off-by-one error.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1778547/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766542] Re: Installation blocks when the machine is behind a proxy server
Hello Robert, or anyone else affected, Accepted apt into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.6.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: apt (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- 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/1766542 Title: Installation blocks when the machine is behind a proxy server Status in OEM Priority Project: Confirmed Status in apt package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Incomplete Status in apt source package in Bionic: Fix Committed Status in ubiquity source package in Bionic: New Bug description: [Impact] APT takes a long time to notice when certain connections time out [Test case] * Change the default route to not route stuff successfully (wrong gateway, for example) * Make your sources.list look like this: deb http://archive.ubuntu.com/ubuntu bionic main restricted deb http://archive.ubuntu.com/ubuntu bionic-updates main restricted * Run apt update You should see that it fails with a long verbose error message for the first entry, with all possible IP addresses listed in it; while for the second one it fails with just "Unable to connect to archive.ubuntu.com:http:" as it recognizes it has been blacklisted. [Regression potential] APT will not attempt to retry the host given that it could not connect to it for previous entries. If your network recovered in the meantime, it might update less than previously. [Original bug report] When the machine is behind a proxy server, the installation will block for a while (several minutes) to retrieve the package lists. The timeouts are too long and makes user feels the machine may have some problems. The symptom is similar with bug #14599, but it seems the apt-setup module was rewritten. Another method to trigger this issue is to make the machine cannot access to the Internet, for instance: a wrong gateway. Image: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1766542/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773992] Re: apt-key adv should gpgconf --kill all the things after execution
Hello Dimitri, or anyone else affected, Accepted apt into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.6.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: apt (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- 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/1773992 Title: apt-key adv should gpgconf --kill all the things after execution Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Committed Bug description: [Impact] dirmngr processes are left hanging around after doing key server stuff with apt-key adv. [Test case] apt-key adv --recv-keys "8439 38DF 228D 22F7 B374 2BC0 D94A A3F0 EFE2 1092" < /dev/null ; sleep 2; ps aux should not show a dirmngr process (except for any that was there before running it, obviously). [Regression potential] This just kills more processes using the temporary gpg home directory. It's hard to imagine what could go wrong there. Maybe gpgconf could go mad and kill the wrong process, who knows? [Original bug report] apt-key adv should gpgconf --kill all the things after execution to ensure that e.g. dirmngr processes are not left hanging around To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1773992/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778551] Please test proposed package
Hello Seth, or anyone else affected, Accepted apt into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.5.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-artful to verification-done-artful. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-artful. 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! -- 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/1778551 Title: Add linux-modules* packages to VersionedKernelPackages Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Committed Status in apt source package in Artful: Fix Committed Bug description: == SRU Justification == Impact: The 4.15 hwe kernel includes some package shuffling, so the VersionedKernelPackages list in /etc/apt/apt.conf.d/01autoremove needs to be updated to include linux-modules* packages. Fix: Backport the conf file changes from bionic. Test Case: Confirm that linux-modules* packages are autoremoved according to the same rules used for linux-image* packages. Regression Potential: Minimal. Probably the worst case is that some packages that should be autoremoved are not, but since these changes have been in use in bionic for a while now no regressions are expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1778551/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778547] Please test proposed package
Hello Julian, or anyone else affected,
Accepted apt into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.6.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!
--
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/1778547
Title:
Broken system lock counting
Status in apt package in Ubuntu:
Fix Committed
Status in apt source package in Xenial:
Fix Committed
Status in apt source package in Artful:
Fix Committed
Status in apt source package in Bionic:
Fix Committed
Bug description:
[Impact]
System lock unrefing is broken, off-by-one error. Locking twice opens a
second fd for the lock file, and the old fd gets lost and remains open for the
remaining duration of the program
[Test case]
Executing the following script should show one lock file in the first
line, and none in the last line.
def maybe_readlink(path):
try:
return os.readlink("/proc/self/fd/" + p)
except:
return ""
import os, apt_pkg
apt_pkg.init()
apt_pkg.pkgsystem_lock()
apt_pkg.pkgsystem_lock()
apt_pkg.pkgsystem_unlock()
apt_pkg.pkgsystem_unlock()
print([(p, maybe_readlink("/proc/self/fd/" + p)) for p in
os.listdir("/proc/self/fd")])
[Test output]
good, cosmic:
[('0', '/dev/pts/2'), ('1', '/dev/pts/2'), ('2', '/dev/pts/2'), ('3',
'/var/lib/dpkg/lock'), ('4', '')]
[('0', '/dev/pts/2'), ('1', '/dev/pts/2'), ('2', '/dev/pts/2'), ('3',
'')]
bad, bionic:
[('0', '/dev/pts/0'), ('1', '/dev/pts/0'), ('2', '/dev/pts/0'), ('3',
'pipe:[40889331]'), ('4', '/var/lib/dpkg/lock'), ('5', '/var/lib/dpkg/lock'),
('6', ''), ('17', 'socket:[53931]')]
[('0', '/dev/pts/0'), ('1', '/dev/pts/0'), ('2', '/dev/pts/0'), ('3',
'pipe:[40889331]'), ('4', '/var/lib/dpkg/lock'), ('5', ''), ('17',
'socket:[53931]')]
[Regression potential]
A locking change can potentially break locking, but this one seems like an
obvious off-by-one error.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1778547/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778551] Re: Add linux-modules* packages to VersionedKernelPackages
Hello Seth, or anyone else affected, Accepted apt into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.2.27 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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! ** Changed in: apt (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial ** Changed in: apt (Ubuntu Artful) Status: In Progress => Fix Committed ** Tags added: verification-needed-artful -- 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/1778551 Title: Add linux-modules* packages to VersionedKernelPackages Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Committed Status in apt source package in Artful: Fix Committed Bug description: == SRU Justification == Impact: The 4.15 hwe kernel includes some package shuffling, so the VersionedKernelPackages list in /etc/apt/apt.conf.d/01autoremove needs to be updated to include linux-modules* packages. Fix: Backport the conf file changes from bionic. Test Case: Confirm that linux-modules* packages are autoremoved according to the same rules used for linux-image* packages. Regression Potential: Minimal. Probably the worst case is that some packages that should be autoremoved are not, but since these changes have been in use in bionic for a while now no regressions are expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1778551/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386257] Re: intel-microcode should be installed by default, when the CPU is GenuineIntel
Same happened also me. Updating system and intel-microcode is installed in AMD machine. Updating intel laptop and also AMD-microcode is installed in intel-laptop. Is there no amendment here? What processor is used. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1386257 Title: intel-microcode should be installed by default, when the CPU is GenuineIntel Status in intel: Fix Released Status in Ubuntu Kylin: Fix Released Status in amd64-microcode package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntukylin-meta package in Ubuntu: Fix Released Bug description: intel-microcode should be installed by default on the bare-metal systems which are running on GenuineIntel CPUs, by the installers. Similarly other microcode packages for other CPUs brands should be considered for inclusion (e.g. amd64-microcode). I hope that ubuntu-drivers-common can gain ability to detect cpu series and/or vendors, packages that provide microcodes similarly declare support for cpu series and/or vendors, the microcode packages are shipped on the CDs in the pool directory, and installed on to the target machines as part of the installation. This should help with rapid correction of bugs and behaviour of the CPUs in the field. 2017 update, amd64-microcode should also be seeded, as it is useful to have it autoinstallable. In the recent years there have been critical CPU security vulnerabilities which got fixed with microcode updates. To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1386257/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700826] Re: please include numactl on the ubuntu-server iso
Yeah - I verified it on the arm64 ISOs, and it was good. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1700826 Title: please include numactl on the ubuntu-server iso Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Xenial: Fix Released Status in ubuntu-meta source package in Zesty: Fix Released Bug description: I've submitted an MIR for the numactl binary package at: LP: #1700824. Assuming that is approved, please also include this on the server seed, which I believe is necessary for it to appear on the ubuntu-server ISOs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1700826/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386257] Re: intel-microcode should be installed by default, when the CPU is GenuineIntel
im updating latest intel-microcode (sudo apt-get update && sudo apt-get upgrade -y) and it is also automatically install also amd-microcode in my laptop. Why? my laptop not use amd-microcode. it is use only intel. Why it install it when updating my laptop. Is this a bug or what? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1386257 Title: intel-microcode should be installed by default, when the CPU is GenuineIntel Status in intel: Fix Released Status in Ubuntu Kylin: Fix Released Status in amd64-microcode package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntukylin-meta package in Ubuntu: Fix Released Bug description: intel-microcode should be installed by default on the bare-metal systems which are running on GenuineIntel CPUs, by the installers. Similarly other microcode packages for other CPUs brands should be considered for inclusion (e.g. amd64-microcode). I hope that ubuntu-drivers-common can gain ability to detect cpu series and/or vendors, packages that provide microcodes similarly declare support for cpu series and/or vendors, the microcode packages are shipped on the CDs in the pool directory, and installed on to the target machines as part of the installation. This should help with rapid correction of bugs and behaviour of the CPUs in the field. 2017 update, amd64-microcode should also be seeded, as it is useful to have it autoinstallable. In the recent years there have been critical CPU security vulnerabilities which got fixed with microcode updates. To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1386257/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778936] Re: please re-add Support-system-image-read-only-etc.patch
** Also affects: systemd (Ubuntu Cosmic) 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/1778936 Title: please re-add Support-system-image-read-only-etc.patch Status in systemd package in Ubuntu: New Status in systemd source package in Bionic: New Status in systemd source package in Cosmic: New Bug description: The 16.04 version of systemd had a patch to support the read-only etc. For core18 we will also need this change because core18 is still not on a fully writable etc. I will attach a debdiff against the current bionic version of systemd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778936/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710634] Re: Incorrect directory for (lib)krb5 plugins
This was fixed in debian's 1.15.2-1, and bionic already has 1.16-2, so
marking as fix released.
** Changed in: krb5 (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1710634
Title:
Incorrect directory for (lib)krb5 plugins
Status in krb5 package in Ubuntu:
Fix Released
Status in krb5 package in Debian:
Fix Released
Bug description:
The libkrb5-3 package built from the krb5 source hints at a (lib)krb5
plugin directory like this:
debian/libkrb5-3.dirs.in:usr/lib/${DEB_HOST_MULTIARCH}/krb5/plugins/krb5
debian/libkrb5-3.lintian-overrides:libkrb5-3:
package-contains-empty-directory */plugins/krb5/
The correct (lib)krb5 plugins directory, however, is:
/usr/lib/${DEB_HOST_MULTIARCH}/krb5/plugins/libkrb5
This can be verified in the krb5 source:
$ grep plugins/libkrb5 -r src
src/lib/krb5/os/locate_kdc.c: LIBDIR
"/krb5/plugins/libkrb5",
src/lib/krb5/os/locate_kdc.c:static const char *objdirs[] = { LIBDIR
"/krb5/plugins/libkrb5", NULL };
As well as in the built library:
$ strings /usr/lib/x86_64-linux-gnu/libkrb5.so.3|grep plugins
/usr/lib/x86_64-linux-gnu/krb5/plugins/authdata
/usr/lib/x86_64-linux-gnu/krb5/plugins
plugins
/usr/lib/x86_64-linux-gnu/krb5/plugins/libkrb5
This also briefly introduced a bug in the ubuntu and debian sssd packages,
which assumed .../plugins/krb5 was the correct path:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1664566
In debian it was fixed in commit e6c4e91473e75f0ddc917a24f4d561fab9900939:
commit e6c4e91473e75f0ddc917a24f4d561fab9900939
Author: Timo Aaltonen
Date: Fri Feb 17 11:22:12 2017 +0200
rules, common.install: Fix sssd_krb5_locator_plugin install path. (LP:
#1664566)
There is no immediate impact to the libkrb5-3 package itself, since MIT
kerberos does not ship any libkrb5 plugin at the moment and it is an empty
directory. It should be fixed, though, to avoid inducing similar bugs in
the future.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1710634/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778936] Re: please re-add Support-system-image-read-only-etc.patch
** Patch added: "systemd_237-3ubuntu10.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778936/+attachment/5157097/+files/systemd_237-3ubuntu10.2.debdiff ** Also affects: systemd (Ubuntu Bionic) 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/1778936 Title: please re-add Support-system-image-read-only-etc.patch Status in systemd package in Ubuntu: New Status in systemd source package in Bionic: New Bug description: The 16.04 version of systemd had a patch to support the read-only etc. For core18 we will also need this change because core18 is still not on a fully writable etc. I will attach a debdiff against the current bionic version of systemd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778936/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778936] [NEW] please re-add Support-system-image-read-only-etc.patch
Public bug reported: The 16.04 version of systemd had a patch to support the read-only etc. For core18 we will also need this change because core18 is still not on a fully writable etc. I will attach a debdiff against the current bionic version of systemd. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu Bionic) 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/1778936 Title: please re-add Support-system-image-read-only-etc.patch Status in systemd package in Ubuntu: New Status in systemd source package in Bionic: New Bug description: The 16.04 version of systemd had a patch to support the read-only etc. For core18 we will also need this change because core18 is still not on a fully writable etc. I will attach a debdiff against the current bionic version of systemd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778936/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1751489] Re: rsync dies with "inflate returned -3 (0 bytes)"
** Changed in: rsync (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1751489 Title: rsync dies with "inflate returned -3 (0 bytes)" Status in rsync package in Ubuntu: New Status in rsync package in Debian: New Bug description: On Ubuntu 16.04, when rsyncing big KVM VM image (17,055,219,712 bytes), sync error happens each time I try to use command rsync -vaz -e ssh host:/path/to/file ./ The full text printed: inflate returned -3 (0 bytes) rsync error: error in rsync protocol data stream (code 12) at token.c(557) [receiver=3.1.1] rsync: connection unexpectedly closed (72 bytes received so far) [generator] rsync error: error in rsync protocol data stream (code 12) at io.c(226) [generator=3.1.1] On receiving side: Ubuntu 16.04.3 64bit, rsync 3.1.1-3ubuntu1.2 On remote side: Ubuntu 14.04.5 64bit, rsync 3.1.0-2ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1751489/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778932] Re: rsync can trigger system crash
And I blacklisted a module that might have been contributing. (hid_uclogic) but the problem persists. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1778932 Title: rsync can trigger system crash Status in rsync package in Ubuntu: New Bug description: I'm not sure how much of this is rsync or something else in my system. I can reliably trigger this using rsync to transfer files from one drive to another drive on my computer. the source is ssd and destination is mdadm raid 1 partition. will attach syslog messages. after it is triggered, the the system becomes unresponsive and requires a hard reboot. running rysnc as user, no special privileges. root@music:~# lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 apt-cache policy rsync rsync: Installed: 3.1.2-2.1ubuntu1 Candidate: 3.1.2-2.1ubuntu1 Version table: *** 3.1.2-2.1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status uname -a Linux music 4.15.0-23-lowlatency #25-Ubuntu SMP PREEMPT Wed May 23 20:39:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rsync 3.1.2-2.1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-lowlatency 4.15.18 Uname: Linux 4.15.0-23-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jun 27 10:08:36 2018 InstallationDate: Installed on 2018-03-31 (87 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color LANGUAGE=en_US PATH=(custom, no user) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1778932/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778932] Re: rsync can trigger system crash
attaching syslog which shows the crash appearing. ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1778932/+attachment/5157089/+files/syslog -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1778932 Title: rsync can trigger system crash Status in rsync package in Ubuntu: New Bug description: I'm not sure how much of this is rsync or something else in my system. I can reliably trigger this using rsync to transfer files from one drive to another drive on my computer. the source is ssd and destination is mdadm raid 1 partition. will attach syslog messages. after it is triggered, the the system becomes unresponsive and requires a hard reboot. running rysnc as user, no special privileges. root@music:~# lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 apt-cache policy rsync rsync: Installed: 3.1.2-2.1ubuntu1 Candidate: 3.1.2-2.1ubuntu1 Version table: *** 3.1.2-2.1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status uname -a Linux music 4.15.0-23-lowlatency #25-Ubuntu SMP PREEMPT Wed May 23 20:39:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rsync 3.1.2-2.1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-lowlatency 4.15.18 Uname: Linux 4.15.0-23-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jun 27 10:08:36 2018 InstallationDate: Installed on 2018-03-31 (87 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color LANGUAGE=en_US PATH=(custom, no user) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1778932/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778932] [NEW] rsync can trigger system crash
Public bug reported: I'm not sure how much of this is rsync or something else in my system. I can reliably trigger this using rsync to transfer files from one drive to another drive on my computer. the source is ssd and destination is mdadm raid 1 partition. will attach syslog messages. after it is triggered, the the system becomes unresponsive and requires a hard reboot. running rysnc as user, no special privileges. root@music:~# lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 apt-cache policy rsync rsync: Installed: 3.1.2-2.1ubuntu1 Candidate: 3.1.2-2.1ubuntu1 Version table: *** 3.1.2-2.1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status uname -a Linux music 4.15.0-23-lowlatency #25-Ubuntu SMP PREEMPT Wed May 23 20:39:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rsync 3.1.2-2.1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-lowlatency 4.15.18 Uname: Linux 4.15.0-23-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jun 27 10:08:36 2018 InstallationDate: Installed on 2018-03-31 (87 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color LANGUAGE=en_US PATH=(custom, no user) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rsync (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 rsync in Ubuntu. https://bugs.launchpad.net/bugs/1778932 Title: rsync can trigger system crash Status in rsync package in Ubuntu: New Bug description: I'm not sure how much of this is rsync or something else in my system. I can reliably trigger this using rsync to transfer files from one drive to another drive on my computer. the source is ssd and destination is mdadm raid 1 partition. will attach syslog messages. after it is triggered, the the system becomes unresponsive and requires a hard reboot. running rysnc as user, no special privileges. root@music:~# lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 apt-cache policy rsync rsync: Installed: 3.1.2-2.1ubuntu1 Candidate: 3.1.2-2.1ubuntu1 Version table: *** 3.1.2-2.1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status uname -a Linux music 4.15.0-23-lowlatency #25-Ubuntu SMP PREEMPT Wed May 23 20:39:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rsync 3.1.2-2.1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-lowlatency 4.15.18 Uname: Linux 4.15.0-23-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jun 27 10:08:36 2018 InstallationDate: Installed on 2018-03-31 (87 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color LANGUAGE=en_US PATH=(custom, no user) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1778932/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1771011] Re: Doesn't accept environment variable with underscore in its name in AuthorizedKeysFile
** Also affects: openssh via https://bugzilla.mindrot.org/show_bug.cgi?id=2851 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1771011 Title: Doesn't accept environment variable with underscore in its name in AuthorizedKeysFile Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Triaged Bug description: If environment variable name defined in AuthorizedKeysFile contains underscore character (environment="FOO_BAR=1" ...), sshd refuses connection and throws following error: authorized_keys:1: bad key options: invalid environment string To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1771011/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1651818] Re: busybox-initramfs needs different compile options to work with cryptroot-unlock
Thanks Dimitri! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1651818 Title: busybox-initramfs needs different compile options to work with cryptroot-unlock Status in busybox package in Ubuntu: Won't Fix Status in cryptsetup package in Ubuntu: Fix Released Status in cryptsetup source package in Bionic: Confirmed Bug description: The cryptroot-unlock script in the cryptsetup package does not work in initramfs. It fails because "ps -e" is not available in busybox for initramfs. When building the package with CONFIG_DESKTOP=y CONFIG_EXTRA_COMPAT=y the needed commands (ps, grep) with parameter are there and it works. Tetsted on Ubuntu GNOME 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1651818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1677881] Re: Missing dep8 tests
Since this package is currently a sync from Debian, and I want their opinion on these tests first, I submitted an MP for Debian here: https://salsa.debian.org/debian/krb5/merge_requests/2 ** Changed in: krb5 (Ubuntu) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: krb5 (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1677881 Title: Missing dep8 tests Status in krb5 package in Ubuntu: In Progress Bug description: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 As of March 29, 2017, this source package did not contain dep8 tests in the current development release of Ubuntu, named Zesty. This was determined by running `pull-lp-source krb5 zesty` and then checking for the existence of 'debian/tests/' and 'debian/tests/control'. Test automation is essential to higher levels of quality and confidence in updates to packages. dep8 tests [1] specify how automatic testing can be integrated into packages and then run by package maintainers before new uploads. This defect is to report the absence of these tests and to report the opportunity as a potential item for development by both new and experienced contributors. [1] http://packaging.ubuntu.com/html/auto-pkg-test.html affects ubuntu/krb5 status new importance wishlist tag needs-dep8 - --- Joshua Powers Ubuntu Server Canonical Ltd -BEGIN PGP SIGNATURE- iQIcBAEBCAAGBQJY3YGVAAoJEIP8BxPaZgwlCIEP/36uotG3iLNIh5/fPc2FDzwV hqK5CLKbCLqlX7RmzkSzO303hJ051Q6uWIb1ZcnvZShO4h2mrQfyXXmWBXO3So/2 imYe6Pg3j9v1aNYCxpvWKL6VIpN5beADCoWlAS9P89qSIdyEYTiaL6HFHzbA5hck 7rtMhHnzw16mkT+ttZ39f4kqZ9jqqV1je0lPyCI3L+UicswkdeymHeZAZSkG13lW uSi5SVLFDpDeWq/23Ohj0tacLZbpBKG4vScRQ7+Me3ieGnC0gii8C1luXGPWpS9v CvW1JLPbuo3yHooBzJw6YAYI2TiWyNjtO2/9ESPxcmn+tPn7iXoeTBIstlQC2iY0 fvoUrmxUjSJafgCyZE1NNy8gTlFLObpMP/qZPtw7YLKaD9t64+JZUK4vzSNr1tY5 ltCXFf0mneUrUjTOS1Io+vigiBbMEIFuUjEXT3DxGEybf8rrl6fJdCD++1L0NTXR ImfhCBgSEYBrluRLHu1tGftin7wKgarl7uWLzZxGeJ/MiXkX0eWIgOVoXaQq6gnR HR7XF1x9x1VJYi2CGMrDDWSHWDHgXC5UOcBz/KLMSPMcyQakXyRrw1Hqplj3G3PM OkqR8uLWUYfTZvrVvnSj4jJPNRSiBOz95FFbfMZ43yxoE5F6QBhztwgcJC8/g+bn zu94s0Hiyv+yxmptMwgX =ibX0 -END PGP SIGNATURE- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1677881/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1751489] Re: rsync dies with "inflate returned -3 (0 bytes)"
Can be avoided not using -z AFAIK it is an issue with compression on very huge files. Theree are similar discussions on e.g. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741628 ** Bug watch added: Debian Bug tracker #741628 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741628 ** Also affects: rsync (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741628 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1751489 Title: rsync dies with "inflate returned -3 (0 bytes)" Status in rsync package in Ubuntu: New Status in rsync package in Debian: Unknown Bug description: On Ubuntu 16.04, when rsyncing big KVM VM image (17,055,219,712 bytes), sync error happens each time I try to use command rsync -vaz -e ssh host:/path/to/file ./ The full text printed: inflate returned -3 (0 bytes) rsync error: error in rsync protocol data stream (code 12) at token.c(557) [receiver=3.1.1] rsync: connection unexpectedly closed (72 bytes received so far) [generator] rsync error: error in rsync protocol data stream (code 12) at io.c(226) [generator=3.1.1] On receiving side: Ubuntu 16.04.3 64bit, rsync 3.1.1-3ubuntu1.2 On remote side: Ubuntu 14.04.5 64bit, rsync 3.1.0-2ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1751489/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1597415] Re: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument
Confirming the same issue on Ubuntu Server 18.04 LTS: Error calling EVIOCSKEYCODE on device node '/dev/input/event2' (scan code 0x9004c, key code 162): Invalid argument CODE_FILE ../src/udev/udev-builtin-keyboard.c CODE_FUNC map_keycode CODE_LINE 103 ERRNO 22 PRIORITY3 SYSLOG_FACILITY 3 SYSLOG_IDENTIFIER systemd-udevd _BOOT_ID8561955e61444adea66c6983c7972f60 _CAP_EFFECTIVE 3f _CMDLINE/lib/systemd/systemd-udevd _COMM systemd-udevd _EXE/lib/systemd/systemd-udevd _GID0 _HOSTNAME blueeyebrows _MACHINE_ID 3c83a050931347c59c2d930c491afdc7 _PID340 _SELINUX_CONTEXTunconfined _SOURCE_REALTIME_TIMESTAMP 1530104311822252 _SYSTEMD_CGROUP /system.slice/systemd-udevd.service _SYSTEMD_INVOCATION_ID da5926014fa944509d5e10a8d9a6adf2 _SYSTEMD_SLICE system.slice _SYSTEMD_UNIT systemd-udevd.service _TRANSPORT journal _UID0 __CURSOR s=b7551ec2b2f942ae94a42e8501582e71;i=1784;b=8561955e61444adea66c6983c7972f60;m=868e2f;t=56f9f2bf9bcec;x=626cfce2d4ede039 __MONOTONIC_TIMESTAMP 8818223 __REALTIME_TIMESTAMP1530104311823596 Kernel: 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1597415 Title: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Hi, the symptom is this error message in my system's logs: juin 29 16:56:39 vougeot systemd-udevd[522]: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument According to /proc/bus/input/devices the corresponding input device is: I: Bus=0019 Vendor= Product= Version= N: Name="Dell WMI hotkeys" P: Phys=wmi/input0 S: Sysfs=/devices/virtual/input/input10 U: Uniq= H: Handlers=kbd event9 B: PROP=0 B: EV=13 B: KEY=1000b0400 0 e 0 B: MSC=10 This laptop is a Dell Latitude E6520. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu6 Uname: Linux 4.6.3-040603-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: KDE CustomUdevRuleFiles: 60-ssd-scheduler.rules Date: Wed Jun 29 17:43:01 2016 EcryptfsInUse: Yes MachineType: Dell Inc. Latitude E6520 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to xenial on 2016-04-09 (80 days ago) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0NVF5K dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1748063] Re: package clamav-base 0.99.3+addedllvm-0ubuntu0.14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
** Changed in: debconf (Ubuntu) Status: New => Incomplete -- 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/1748063 Title: package clamav-base 0.99.3+addedllvm-0ubuntu0.14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in clamav package in Ubuntu: Incomplete Status in debconf package in Ubuntu: Incomplete Bug description: My computer used to continually freeze after about thirty (30) seconds or so such that neither my mouse nor my keyboard worked because they froze, which required me to repeatedly restart my computer, but not first without disconnecting my computer from its internet connection, given that my understanding is and/or was that there are or were security problems in permitting the grub loader to be seen and, therefore, its key to be read by eavesdropper(s) on the other end of the internet cable. Nevertheless, it also appears, after having reviewed my computer's files and folder that criminal hacker(s) have and continue to attempt to infiltrate my computer by means of two (2) known files, Namely, .pki and .esd_auth . Given that my computer was hacked a day or two ago, thereby rendering it useless to the point of my computer being unable to boot, I assert and maintain that these vulnerabilities ought to be addressed to prevent further security breaches in an otherwise excellent operating system. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: clamav-base 0.99.3+addedllvm-0ubuntu0.14.04.1 ProcVersionSignature: Ubuntu 3.2.0-121.164-generic-pae 3.2.79 Uname: Linux 3.2.0-121-generic-pae i686 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: i386 Date: Wed Feb 7 20:46:24 2018 DuplicateSignature: package:clamav-base:0.99.3+addedllvm-0ubuntu0.14.04.1:subprocess installed post-installation script returned error exit status 128 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-02-16 (356 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) PackageArchitecture: all ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.2.0-121-generic-pae root=UUID=120b07c7-e971-4a45-bc46-a15f8eefc5e1 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: clamav Title: package clamav-base 0.99.3+addedllvm-0ubuntu0.14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: Upgraded to trusty on 2017-07-29 (194 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1748063/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700826] Re: please include numactl on the ubuntu-server iso
16.04.4 iso /media/iso/pool/main/n/numactl/libnuma1_2.0.11-1ubuntu1.1_amd64.deb /media/iso/pool/main/n/numactl/numactl_2.0.11-1ubuntu1.1_amd64.deb I guess with that you are good now. ** Changed in: ubuntu-meta (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: ubuntu-meta (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: ubuntu-meta (Ubuntu Zesty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1700826 Title: please include numactl on the ubuntu-server iso Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Xenial: Fix Released Status in ubuntu-meta source package in Zesty: Fix Released Bug description: I've submitted an MIR for the numactl binary package at: LP: #1700824. Assuming that is approved, please also include this on the server seed, which I believe is necessary for it to appear on the ubuntu-server ISOs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1700826/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641272] Re: Debug symbols package doesnt exist
** Tags added: bot-stop-nagging -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1641272 Title: Debug symbols package doesnt exist Status in dnsmasq package in Ubuntu: New Bug description: On Yakkety with ddebs repos enabled there is no debug packages for dnsmasq To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1641272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700826] Re: please include numactl on the ubuntu-server iso
This is resolved I'd think. @Dannf did you check older ISOs like the last 16.04 respin in regard to your case? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1700826 Title: please include numactl on the ubuntu-server iso Status in ubuntu-meta package in Ubuntu: Fix Committed Status in ubuntu-meta source package in Xenial: Fix Committed Status in ubuntu-meta source package in Zesty: Fix Committed Bug description: I've submitted an MIR for the numactl binary package at: LP: #1700824. Assuming that is approved, please also include this on the server seed, which I believe is necessary for it to appear on the ubuntu-server ISOs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1700826/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776218] Re: New style hook support not robust on removal
** Tags added: id-5b333ce4c9e5f90176d2242c
--
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/1776218
Title:
New style hook support not robust on removal
Status in apt package in Ubuntu:
In Progress
Bug description:
The new style (json-rpc) hooks are great. However when using them in snapd we
noticed the following problem. When shipping a hook in
/etc/apt/apt.conf.d/20snapd.conf like:
```
AptCli::Hooks::Install { "[ ! -f /usr/bin/snap ] || /usr/bin/snap advise-snap
--from-apt || true"; };
```
this works fine.
However when the snapd package is removed apt fails with:
```
...
Purging configuration files for snapd (1337.2.32.8) ...
Final directory cleanup
Discarding preserved snap namespaces
Removing extra snap-confine apparmor rules
Removing snapd cache
Removing snapd state
E: Could not read response to hello message from hook [ ! -f /usr/bin/snap ]
|| /usr/bin/snap advise-snap --from-apt || true: Connection reset by peer
E: Could not read message separator line after handshake from [ ! -f
/usr/bin/snap ] || /usr/bin/snap advise-snap --from-apt || true: Connection
reset by peer
quiet: end of output.
```
I.e. if the hook is not there apt still expectes a handshake.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1776218/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738085] Re: Bridge gets created while the network interfaces are still being renamed
Hi, first of all I beg your pardon - while I'm just the one cleaning old bugs - it is bad that you had to wait so long. Now lets get to your case... This is a mix of systemd and ifup based network ocnfiguration, and in Artful a lot of this was still in flight. In Bionic there is a simplified frontend to networkd (or networkmanager) [1] netplan. I wanted to check your case with this new way to do it. I have 4 devices, using one as "wan" and 3 for the bridge in netplan looks like: network: version: 2 ethernets: wan: dhcp4: true match: macaddress: 52:54:00:75:f5:3e set-name: wan lan1: match: macaddress: 52:54:00:84:a1:87 set-name: lan1 lan2: match: macaddress: 52:54:00:f3:4f:cc set-name: lan2 lan3: match: macaddress: 52:54:00:ff:11:1a set-name: lan3 bridges: br0: addresses: [ 10.0.0.1/24 ] interfaces: - lan1 - lan2 - lan3 That will create link files like yours for renaming: $ cat /run/systemd/network/10-netplan-wan.link [Match] MACAddress=52:54:00:75:f5:3e [Link] Name=wan WakeOnLan=off But also for network configuration: $ cat /run/systemd/network/10-netplan-wan.network [Match] MACAddress=52:54:00:75:f5:3e Name=wan [Network] DHCP=ipv4 [DHCP] UseMTU=true RouteMetric=100 Especially also the bridge: $ cat /run/systemd/network/10-netplan-br0.network [Match] Name=br0 [Network] Address=10.0.0.1/24 $ cat /run/systemd/network/10-netplan-br0.netdev [NetDev] Name=br0 Kind=bridge And the device association to the bridge: $ cat /run/systemd/network/10-netplan-lan2.network [Match] MACAddress=52:54:00:f3:4f:cc Name=lan2 [Network] Bridge=br0 LinkLocalAddressing=no That looks good to me now: $ networkctl list IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 6 br0 ether routableconfigured 7 lan3 ether carrier configured 8 lan1 ether carrier configured 9 wan ether routableconfigured 10 lan2 ether carrier configured $ networkctl status ●State: routable Address: 10.0.0.1 on br0 192.168.122.229 on wan fe80::e831:94ff:fe76:95f9 on br0 fe80::5054:ff:fe75:f53e on wan Gateway: 192.168.122.1 on wan DNS: 192.168.122.1 $ brctl show bridge name bridge id STP enabled interfaces br0 8000.ea31947695f9 no lan1 lan2 lan3 Please see [1] and man netplan for more, or feel free to write the same in networkd rules as you already started on your own. But mixing the systems to control devices is not really recommended as you'd run in issues just as the one you have reported. Therefore I'd consider this a broken config more than a bug in Ubuntu and would mark the bug incomplete for now until further discussion/info was provided. [1]: https://netplan.io/ ** Also affects: netplan.io (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Incomplete ** Changed in: netplan.io (Ubuntu) Status: New => Incomplete ** Changed in: bridge-utils (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bridge-utils in Ubuntu. https://bugs.launchpad.net/bugs/1738085 Title: Bridge gets created while the network interfaces are still being renamed Status in bridge-utils package in Ubuntu: Incomplete Status in netplan.io package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: I have a problem with bridge configuration for the interfaces on my system that I also happen to rename explicitly. Specifically, I have following network configuration: # WAN interface auto wan iface wan inet dhcp # LAN interfaces iface wlan inet manual iface lan1 inet manual iface lan2 inet manual iface lan3 inet manual # LAN bridge auto lan iface lan inet static address 10.0.0.1 netmask 255.255.255.0 bridge_ports wlan lan1 lan2 lan3 I use systemd .link files for renaming each of the 5 bridged interfaces, e.g. cat /etc/systemd/network/10-lan1.link [Match] MACAddress=90:e2:ba:ae:e8:21 [Link] Name=lan1 (BTW, I previously used udev rules to handle the renaming, before I migrated to systemd .link files hoping for improvement) Upon system boot, I see following messages: Dec 13 16:03:38 trout kernel: [
[Touch-packages] [Bug 1778908] [NEW] 16.04 libtag dependancy issues
Public bug reported: This issue has come up from trying to install Mixxx from their official LaunchPad host ppa and it appears to reference libtag1-vanilla, which does appear to exist in 16.04 but I believe should be superseded by libtag1v5-vanilla, yet it doesn't seem to recognise as such. As it then can't be manually installed or the other removed I think there is a deeper issue with this package than just Mixxx having the wrong one down as a dependency. This has been reported to the Mixxx developers on their forum about a week ago but no official response as yet... I've run this in a virtual box but there are multiple users who have reported this on their main systems (at least four I've seen.) osboxes@osboxes:~$ sudo apt-get update [sudo] password for osboxes: Hit:1 http://security.ubuntu.com/ubuntu xenial-security InRelease Hit:2 http://ppa.launchpad.net/mixxx/mixxx/ubuntu xenial InRelease Hit:3 http://us.archive.ubuntu.com/ubuntu xenial InRelease Hit:4 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease Hit:5 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease Reading package lists... Done osboxes@osboxes:~$ sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. osboxes@osboxes:~$ sudo apt-get install mixxx Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: mixxx : Depends: libtag1-vanilla (>= 1.10-0ubuntu1~xenial0) but it is not going to be installed E: Unable to correct problems, you have held broken packages. osboxes@osboxes:~$ sudo apt-get install libtag1-vanilla Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libcheese8 : Depends: gstreamer1.0-plugins-good (>= 0.11.0) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. osboxes@osboxes:~$ sudo apt-get install gstreamer1.0-plugins-good Reading package lists... Done Building dependency tree Reading state information... Done gstreamer1.0-plugins-good is already the newest version (1.8.3-1ubuntu0.4). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. osboxes@osboxes:~$ sudo apt-get remove libtag1v5-vanilla Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: indicator-bluetooth : Depends: unity-control-center but it is not going to be installed or gnome-control-center but it is not going to be installed or ubuntu-system-settings but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. osboxes@osboxes:~$ sudo apt-get remove libtag1v5 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libcheese8 : Depends: gstreamer1.0-plugins-good (>= 0.11.0) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. osboxes@osboxes:~$ sudo apt-cache policy libtag1-vanilla libtag1-vanilla: Installed: (none) Candidate: 1.10-0ubuntu1~xenial0 Version table: 1.10-0ubuntu1~xenial0 500 500 http://ppa.launchpad.net/mixxx/mixxx/ubuntu xenial/main amd64 Packages ** Affects: taglib (Ubuntu) Importance: Undecided
[Touch-packages] [Bug 1690836] Re: libnl-genl-3.0 memory leak
X: 3.2.27-1ubuntu0.16.04.1 A: 3.2.29-0ubuntu3 https://github.com/thom311/libnl looks more up to date than the repo suggested before. Checking the log in between it is not ovbious what it is, also the leak seemed to have changed between trusty and xenial (maybe old fixed and new added). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1690836 Title: libnl-genl-3.0 memory leak Status in libnl3 package in Ubuntu: Fix Released Status in libnl3 source package in Trusty: Confirmed Status in libnl3 source package in Xenial: Confirmed Bug description: It seems that there is a memory leak in the libnl-genl-3.0 library. The memory-leak can be seen when the function genl_ctrl_resolve() fails. It seems that this function copy a buffer and forget to deallocate it properly: 258 cb = nl_cb_clone(orig); // buffer copied not freed - The following attached source-code can help you to reproduce this behavior on Ubuntu 14.04. It forces an issue on the genl_ctrl_resolve by asking an unknown netlink-family. To compile program: g++ -std=c++11 main.cpp $(pkg-config --cflags --libs libnl-3.0 libnl-genl-3.0) -o main To detect memory-leak using Valgrind: valgrind --leak-check=full ./main - Executing it on Debian 8.0 shows "no memory leak": sylvain@debian:~/test$ lsb_release -rd Description: Debian GNU/Linux 8.8 (jessie) Release: 8.8 sylvain@debian:~/test$ g++ -std=c++11 main.cpp $(pkg-config --cflags --libs libnl-3.0 libnl-genl-3.0) -o main sylvain@debian:~/test$ valgrind --leak-check=full ./main ==26390== Memcheck, a memory error detector ==26390== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==26390== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info ==26390== Command: ./main ==26390== start test error: can't retrieve the netlink-family id end test ==26390== ==26390== HEAP SUMMARY: ==26390== in use at exit: 0 bytes in 0 blocks ==26390== total heap usage: 13 allocs, 13 frees, 22,142 bytes allocated ==26390== ==26390== All heap blocks were freed -- no leaks are possible ==26390== ==26390== For counts of detected and suppressed errors, rerun with: -v ==26390== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) - Executing it on Ubuntu 14.04 shows a memory leak: ubuntu@ubuntu:~$ lsb_release -rd Description: Ubuntu 14.04.5 LTS Release: 14.04 ubuntu@ubuntu:~$ g++ -std=c++11 main.cpp $(pkg-config --cflags --libs libnl-3.0 libnl-genl-3.0) -o main ubuntu@ubuntu:~$ valgrind --leak-check=full ./main ==37377== Memcheck, a memory error detector ==37377== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==37377== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info ==37377== Command: ./main ==37377== start test error: can't retrieve the netlink-family id end test ==37377== ==37377== HEAP SUMMARY: ==37377== in use at exit: 224 bytes in 1 blocks ==37377== total heap usage: 13 allocs, 12 frees, 22,142 bytes allocated ==37377== ==37377== 224 bytes in 1 blocks are definitely lost in loss record 1 of 1 ==37377==at 0x4C2CC70: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==37377==by 0x5048FAA: nl_cb_alloc (in /lib/x86_64-linux-gnu/libnl-3.so.200.16.1) ==37377==by 0x504CB1E: nl_socket_alloc (in /lib/x86_64-linux-gnu/libnl-3.so.200.16.1) ==37377==by 0x4012E3: A::Init() (in /home/ubuntu/main) ==37377==by 0x401189: main (in /home/ubuntu/main) ==37377== ==37377== LEAK SUMMARY: ==37377==definitely lost: 224 bytes in 1 blocks ==37377==indirectly lost: 0 bytes in 0 blocks ==37377== possibly lost: 0 bytes in 0 blocks ==37377==still reachable: 0 bytes in 0 blocks ==37377== suppressed: 0 bytes in 0 blocks ==37377== ==37377== For counts of detected and suppressed errors, rerun with: -v ==37377== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) Thanks, Sylvain Trinquet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1690836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1763099] Re: Stack-Overflow in nm-new (binuitils-2.30-15ubuntu1)
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-12641 -- 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/1763099 Title: Stack-Overflow in nm-new (binuitils-2.30-15ubuntu1) Status in binutils package in Ubuntu: Confirmed Bug description: Dear all, The following binutils nm-new Stack-Overflow was found by a modified version of the kAFL fuzzer (https://github.com/RUB-SysSec/kAFL). I have attached the crashing input and an ASAN report. Steps to reproduce: Build current verison of binutils: ``` pull-lp-source binutils cd binutils-2.30 CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address -ggdb" CXXFLAGS="-fsanitize=address -fsanitize-recover=address -ggdb" LDFLAGS="-fsanitize=address" ./configure CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address -ggdb" CXXFLAGS="-fsanitize=address -fsanitize-recover=address -ggdb" LDFLAGS="-fsanitize=address" make ``` Run inputs under ASAN: ``` ASAN_OPTIONS=halt_on_error=true:allow_addr2line=true ./nm-new a -C -l --synthetic $file ``` We can verify this issue for nm-new binuitils-2.30-15ubuntu1 (Ubuntu 16.04.4 LTS / sources from "pull-lp-source bintuils"). Credits: Sergej Schumilo, Cornelius Aschermann (both of Ruhr- Universität Bochum) Best regards, Sergej Schumilo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1763099/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690836] Re: libnl-genl-3.0 memory leak
Needs debugging what the actual change is that could be considered for backporting. ** Changed in: libnl3 (Ubuntu Trusty) Status: Triaged => Confirmed ** Changed in: libnl3 (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1690836 Title: libnl-genl-3.0 memory leak Status in libnl3 package in Ubuntu: Fix Released Status in libnl3 source package in Trusty: Confirmed Status in libnl3 source package in Xenial: Confirmed Bug description: It seems that there is a memory leak in the libnl-genl-3.0 library. The memory-leak can be seen when the function genl_ctrl_resolve() fails. It seems that this function copy a buffer and forget to deallocate it properly: 258 cb = nl_cb_clone(orig); // buffer copied not freed - The following attached source-code can help you to reproduce this behavior on Ubuntu 14.04. It forces an issue on the genl_ctrl_resolve by asking an unknown netlink-family. To compile program: g++ -std=c++11 main.cpp $(pkg-config --cflags --libs libnl-3.0 libnl-genl-3.0) -o main To detect memory-leak using Valgrind: valgrind --leak-check=full ./main - Executing it on Debian 8.0 shows "no memory leak": sylvain@debian:~/test$ lsb_release -rd Description: Debian GNU/Linux 8.8 (jessie) Release: 8.8 sylvain@debian:~/test$ g++ -std=c++11 main.cpp $(pkg-config --cflags --libs libnl-3.0 libnl-genl-3.0) -o main sylvain@debian:~/test$ valgrind --leak-check=full ./main ==26390== Memcheck, a memory error detector ==26390== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==26390== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info ==26390== Command: ./main ==26390== start test error: can't retrieve the netlink-family id end test ==26390== ==26390== HEAP SUMMARY: ==26390== in use at exit: 0 bytes in 0 blocks ==26390== total heap usage: 13 allocs, 13 frees, 22,142 bytes allocated ==26390== ==26390== All heap blocks were freed -- no leaks are possible ==26390== ==26390== For counts of detected and suppressed errors, rerun with: -v ==26390== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) - Executing it on Ubuntu 14.04 shows a memory leak: ubuntu@ubuntu:~$ lsb_release -rd Description: Ubuntu 14.04.5 LTS Release: 14.04 ubuntu@ubuntu:~$ g++ -std=c++11 main.cpp $(pkg-config --cflags --libs libnl-3.0 libnl-genl-3.0) -o main ubuntu@ubuntu:~$ valgrind --leak-check=full ./main ==37377== Memcheck, a memory error detector ==37377== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==37377== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info ==37377== Command: ./main ==37377== start test error: can't retrieve the netlink-family id end test ==37377== ==37377== HEAP SUMMARY: ==37377== in use at exit: 224 bytes in 1 blocks ==37377== total heap usage: 13 allocs, 12 frees, 22,142 bytes allocated ==37377== ==37377== 224 bytes in 1 blocks are definitely lost in loss record 1 of 1 ==37377==at 0x4C2CC70: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==37377==by 0x5048FAA: nl_cb_alloc (in /lib/x86_64-linux-gnu/libnl-3.so.200.16.1) ==37377==by 0x504CB1E: nl_socket_alloc (in /lib/x86_64-linux-gnu/libnl-3.so.200.16.1) ==37377==by 0x4012E3: A::Init() (in /home/ubuntu/main) ==37377==by 0x401189: main (in /home/ubuntu/main) ==37377== ==37377== LEAK SUMMARY: ==37377==definitely lost: 224 bytes in 1 blocks ==37377==indirectly lost: 0 bytes in 0 blocks ==37377== possibly lost: 0 bytes in 0 blocks ==37377==still reachable: 0 bytes in 0 blocks ==37377== suppressed: 0 bytes in 0 blocks ==37377== ==37377== For counts of detected and suppressed errors, rerun with: -v ==37377== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) Thanks, Sylvain Trinquet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1690836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1763102] Re: Multiple memory corruptions in objdump (binuitils-2.30-15ubuntu1)
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-12697 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-12698 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-12699 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-12700 -- 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/1763102 Title: Multiple memory corruptions in objdump (binuitils-2.30-15ubuntu1) Status in binutils package in Ubuntu: Confirmed Bug description: Dear all, The following binutils objdump memory corruptions were found by a modified version of the kAFL fuzzer (https://github.com/RUB-SysSec/kAFL). I have attached the crashing inputs and each ASAN report. Steps to reproduce: Build current verison of binutils: ``` pull-lp-source binutils cd binutils-2.30 CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address -ggdb" CXXFLAGS="-fsanitize=address -fsanitize-recover=address -ggdb" LDFLAGS="-fsanitize=address" ./configure CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address -ggdb" CXXFLAGS="-fsanitize=address -fsanitize-recover=address -ggdb" LDFLAGS="-fsanitize=address" make ``` Run inputs under ASAN: ``` ASAN_OPTIONS=halt_on_error=false:allow_addr2line=true ./objdump --dwarf-check -C -g -f -dwarf -x $file ``` We can verify those issues for objdump binuitils-2.30-15ubuntu1 (Ubuntu 16.04.4 LTS / sources from "pull-lp-source bintuils"). Credits: Sergej Schumilo, Cornelius Aschermann (both of Ruhr- Universität Bochum) Best regards, Sergej Schumilo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1763102/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690836] Re: libnl-genl-3.0 memory leak
Xenial seems affected # valgrind --leak-check=full ./main ==1859== Memcheck, a memory error detector ==1859== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==1859== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info ==1859== Command: ./main ==1859== start test error: can't retrieve the netlink-family id end test ==1859== ==1859== HEAP SUMMARY: ==1859== in use at exit: 72,704 bytes in 1 blocks ==1859== total heap usage: 17 allocs, 16 frees, 96,875 bytes allocated ==1859== ==1859== LEAK SUMMARY: ==1859==definitely lost: 0 bytes in 0 blocks ==1859==indirectly lost: 0 bytes in 0 blocks ==1859== possibly lost: 0 bytes in 0 blocks ==1859==still reachable: 72,704 bytes in 1 blocks ==1859== suppressed: 0 bytes in 0 blocks ==1859== Reachable blocks (those to which a pointer was found) are not shown. ==1859== To see them, rerun with: --leak-check=full --show-leak-kinds=all ==1859== ==1859== For counts of detected and suppressed errors, rerun with: -v ==1859== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) ** Also affects: libnl3 (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1690836 Title: libnl-genl-3.0 memory leak Status in libnl3 package in Ubuntu: Fix Released Status in libnl3 source package in Trusty: Triaged Status in libnl3 source package in Xenial: New Bug description: It seems that there is a memory leak in the libnl-genl-3.0 library. The memory-leak can be seen when the function genl_ctrl_resolve() fails. It seems that this function copy a buffer and forget to deallocate it properly: 258 cb = nl_cb_clone(orig); // buffer copied not freed - The following attached source-code can help you to reproduce this behavior on Ubuntu 14.04. It forces an issue on the genl_ctrl_resolve by asking an unknown netlink-family. To compile program: g++ -std=c++11 main.cpp $(pkg-config --cflags --libs libnl-3.0 libnl-genl-3.0) -o main To detect memory-leak using Valgrind: valgrind --leak-check=full ./main - Executing it on Debian 8.0 shows "no memory leak": sylvain@debian:~/test$ lsb_release -rd Description: Debian GNU/Linux 8.8 (jessie) Release: 8.8 sylvain@debian:~/test$ g++ -std=c++11 main.cpp $(pkg-config --cflags --libs libnl-3.0 libnl-genl-3.0) -o main sylvain@debian:~/test$ valgrind --leak-check=full ./main ==26390== Memcheck, a memory error detector ==26390== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==26390== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info ==26390== Command: ./main ==26390== start test error: can't retrieve the netlink-family id end test ==26390== ==26390== HEAP SUMMARY: ==26390== in use at exit: 0 bytes in 0 blocks ==26390== total heap usage: 13 allocs, 13 frees, 22,142 bytes allocated ==26390== ==26390== All heap blocks were freed -- no leaks are possible ==26390== ==26390== For counts of detected and suppressed errors, rerun with: -v ==26390== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) - Executing it on Ubuntu 14.04 shows a memory leak: ubuntu@ubuntu:~$ lsb_release -rd Description: Ubuntu 14.04.5 LTS Release: 14.04 ubuntu@ubuntu:~$ g++ -std=c++11 main.cpp $(pkg-config --cflags --libs libnl-3.0 libnl-genl-3.0) -o main ubuntu@ubuntu:~$ valgrind --leak-check=full ./main ==37377== Memcheck, a memory error detector ==37377== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==37377== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info ==37377== Command: ./main ==37377== start test error: can't retrieve the netlink-family id end test ==37377== ==37377== HEAP SUMMARY: ==37377== in use at exit: 224 bytes in 1 blocks ==37377== total heap usage: 13 allocs, 12 frees, 22,142 bytes allocated ==37377== ==37377== 224 bytes in 1 blocks are definitely lost in loss record 1 of 1 ==37377==at 0x4C2CC70: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==37377==by 0x5048FAA: nl_cb_alloc (in /lib/x86_64-linux-gnu/libnl-3.so.200.16.1) ==37377==by 0x504CB1E: nl_socket_alloc (in /lib/x86_64-linux-gnu/libnl-3.so.200.16.1) ==37377==by 0x4012E3: A::Init() (in /home/ubuntu/main) ==37377==by 0x401189: main (in /home/ubuntu/main) ==37377== ==37377== LEAK SUMMARY: ==37377==definitely lost: 224 bytes in 1 blocks ==37377==indirectly lost: 0 bytes in 0 blocks ==37377== possibly lost: 0 bytes in 0 blocks ==37377==
[Touch-packages] [Bug 1690836] Re: libnl-genl-3.0 memory leak
Artful # valgrind --leak-check=full ./main ==1839== Memcheck, a memory error detector ==1839== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==1839== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info ==1839== Command: ./main ==1839== start test error: can't retrieve the netlink-family id end test ==1839== ==1839== HEAP SUMMARY: ==1839== in use at exit: 0 bytes in 0 blocks ==1839== total heap usage: 17 allocs, 17 frees, 96,875 bytes allocated ==1839== ==1839== All heap blocks were freed -- no leaks are possible ==1839== ==1839== For counts of detected and suppressed errors, rerun with: -v ==1839== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) ** Changed in: libnl3 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1690836 Title: libnl-genl-3.0 memory leak Status in libnl3 package in Ubuntu: Fix Released Status in libnl3 source package in Trusty: Triaged Status in libnl3 source package in Xenial: New Bug description: It seems that there is a memory leak in the libnl-genl-3.0 library. The memory-leak can be seen when the function genl_ctrl_resolve() fails. It seems that this function copy a buffer and forget to deallocate it properly: 258 cb = nl_cb_clone(orig); // buffer copied not freed - The following attached source-code can help you to reproduce this behavior on Ubuntu 14.04. It forces an issue on the genl_ctrl_resolve by asking an unknown netlink-family. To compile program: g++ -std=c++11 main.cpp $(pkg-config --cflags --libs libnl-3.0 libnl-genl-3.0) -o main To detect memory-leak using Valgrind: valgrind --leak-check=full ./main - Executing it on Debian 8.0 shows "no memory leak": sylvain@debian:~/test$ lsb_release -rd Description: Debian GNU/Linux 8.8 (jessie) Release: 8.8 sylvain@debian:~/test$ g++ -std=c++11 main.cpp $(pkg-config --cflags --libs libnl-3.0 libnl-genl-3.0) -o main sylvain@debian:~/test$ valgrind --leak-check=full ./main ==26390== Memcheck, a memory error detector ==26390== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==26390== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info ==26390== Command: ./main ==26390== start test error: can't retrieve the netlink-family id end test ==26390== ==26390== HEAP SUMMARY: ==26390== in use at exit: 0 bytes in 0 blocks ==26390== total heap usage: 13 allocs, 13 frees, 22,142 bytes allocated ==26390== ==26390== All heap blocks were freed -- no leaks are possible ==26390== ==26390== For counts of detected and suppressed errors, rerun with: -v ==26390== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) - Executing it on Ubuntu 14.04 shows a memory leak: ubuntu@ubuntu:~$ lsb_release -rd Description: Ubuntu 14.04.5 LTS Release: 14.04 ubuntu@ubuntu:~$ g++ -std=c++11 main.cpp $(pkg-config --cflags --libs libnl-3.0 libnl-genl-3.0) -o main ubuntu@ubuntu:~$ valgrind --leak-check=full ./main ==37377== Memcheck, a memory error detector ==37377== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==37377== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info ==37377== Command: ./main ==37377== start test error: can't retrieve the netlink-family id end test ==37377== ==37377== HEAP SUMMARY: ==37377== in use at exit: 224 bytes in 1 blocks ==37377== total heap usage: 13 allocs, 12 frees, 22,142 bytes allocated ==37377== ==37377== 224 bytes in 1 blocks are definitely lost in loss record 1 of 1 ==37377==at 0x4C2CC70: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==37377==by 0x5048FAA: nl_cb_alloc (in /lib/x86_64-linux-gnu/libnl-3.so.200.16.1) ==37377==by 0x504CB1E: nl_socket_alloc (in /lib/x86_64-linux-gnu/libnl-3.so.200.16.1) ==37377==by 0x4012E3: A::Init() (in /home/ubuntu/main) ==37377==by 0x401189: main (in /home/ubuntu/main) ==37377== ==37377== LEAK SUMMARY: ==37377==definitely lost: 224 bytes in 1 blocks ==37377==indirectly lost: 0 bytes in 0 blocks ==37377== possibly lost: 0 bytes in 0 blocks ==37377==still reachable: 0 bytes in 0 blocks ==37377== suppressed: 0 bytes in 0 blocks ==37377== ==37377== For counts of detected and suppressed errors, rerun with: -v ==37377== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) Thanks, Sylvain Trinquet To manage notifications about this bug go to:
[Touch-packages] [Bug 119294] Re: OpenSSL should support VIA PadLock
** Changed in: ssl-cert Status: Unknown => Fix Released -- 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/119294 Title: OpenSSL should support VIA PadLock Status in ssl-cert: Fix Released Status in openssh package in Ubuntu: Invalid Status in openssl package in Ubuntu: Incomplete Status in openssl package in Debian: Fix Released Bug description: VIA PadLock is a hardware cryptography engine for AES and SHA1/256. OpenSSL now supports PadLock, but a cache logic bug prevents the use of the PadLock engine. A fairly trivial patch exists and has been merged in OpenSSL 0.9.8g upstream. See bug #119295 for the patch and more details. Initial work on PadLock support was done some time ago : http://www.logix.cz/michal/devel/padlock/ To manage notifications about this bug go to: https://bugs.launchpad.net/ssl-cert/+bug/119294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 590639] Re: Segfault on OpenSSL engine initialisation when AES-NI is enabled
** Changed in: openssl Status: Confirmed => Fix Released -- 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/590639 Title: Segfault on OpenSSL engine initialisation when AES-NI is enabled Status in OpenSSL: Fix Released Status in php: Invalid Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Lucid: Fix Released Status in openssl source package in Maverick: Fix Released Bug description: Binary package hint: apache2 Installed software: apache2-mpm-prefork 2.2.14-5ubuntu8 php5 5.3.2-1ubuntu4.2 libapache2-mod-php5 5.3.2-1ubuntu4.2 php5-curl 5.3.2-1ubuntu4.2 Ubuntu version: Ubuntu 10.04 LTS If php5-curl module enabled in the apache2 and access any page on this server with https:// regardless of URL and handler of this URL (php5 or simple static file), apache reset connection logging following in the error.log: [Mon Jun 07 08:48:58 2010] [notice] Apache/2.2.14 (Ubuntu) DAV/2 SVN/1.6.6 PHP/5.3.2-1ubuntu4.2 with Suhosin-Patch mod_python/3.3.1 Python/2.6.5 mod_ssl/2.2.14 OpenSSL/0.9.8k configured -- resuming normal operations [Mon Jun 07 08:49:10 2010] [notice] child pid 24120 exit signal Segmentation fault (11) [Mon Jun 07 08:49:10 2010] [notice] child pid 24121 exit signal Segmentation fault (11) This bug was appeared after upgrade from 9.10 to 10.04, nothing was changed in the configs, previous version of ubuntu working ok. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: apache2.2-bin 2.2.14-5ubuntu8 ProcVersionSignature: Ubuntu 2.6.32-22.35-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic x86_64 Architecture: amd64 Date: Mon Jun 7 08:49:30 2010 ExecutablePath: /usr/lib/apache2/mpm-prefork/apache2 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) ProcEnviron: PATH=(custom, no user) LANG=C SourcePackage: apache2 To manage notifications about this bug go to: https://bugs.launchpad.net/openssl/+bug/590639/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 654493] Re: infinit loop with "openssl s_client -connect xmpp-gmx.gmx.net:5222 -starttls xmpp"
** Changed in: openssl Status: New => Invalid -- 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/654493 Title: infinit loop with "openssl s_client -connect xmpp-gmx.gmx.net:5222 -starttls xmpp" Status in OpenSSL: Invalid Status in openssl package in Ubuntu: Confirmed Bug description: Binary package hint: openssl i try to check sertifikat of jabber server i use, with fallowing result: openssl s_client -connect xmpp-gmx.gmx.net:5222 -starttls xmpp -debug CONNECTED(0003) write to 0x258bf60 [0x7fff56396990] (121 bytes => 121 (0x79)) - 3c 73 74 72 65 61 6d 3a-73 74 72 65 61 6d 20 78 read from 0x258bf60 [0x2582e70] (8192 bytes => 238 (0xEE)) - 3c 3f 78 6d 6c 20 76 65-72 73 69 6f 6e 3d 27 31 < 00e0 - 2f 73 74 72 65 61 6d 3a-65 72 72 6f 72 3e /stream:error> read from 0x258bf60 [0x2582e70] (8192 bytes => 16 (0x10)) - 3c 2f 73 74 72 65 61 6d-3a 73 74 72 65 61 6d 3e read from 0x258bf60 [0x2582e70] (8192 bytes => 0 (0x0)) read from 0x258bf60 [0x2582e70] (8192 bytes => 0 (0x0)) read from 0x258bf60 [0x2582e70] (8192 bytes => 0 (0x0)) read from 0x258bf60 [0x2582e70] (8192 bytes => 0 (0x0)) read from 0x258bf60 [0x2582e70] (8192 bytes => 0 (0x0)) read from 0x258bf60 [0x2582e70] (8192 bytes => 0 (0x0)) read from 0x258bf60 [0x2582e70] (8192 bytes => 0 (0x0)) read from 0x258bf60 [0x2582e70] (8192 bytes => 0 (0x0)) read from 0x258bf60 [0x2582e70] (8192 bytes => 0 (0x0)) read from 0x258bf60 [0x2582e70] (8192 bytes => 0 (0x0)) read from 0x258bf60 [0x2582e70] (8192 bytes => 0 (0x0)) read from 0x258bf60 [0x2582e70] (8192 bytes => 0 (0x0)) read from 0x258bf60 [0x2582e70] (8192 bytes => 0 (0x0)) ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: openssl 0.9.8o-1ubuntu4 Uname: Linux 2.6.36-rc4-00134-g03a7ab0 x86_64 Architecture: amd64 Date: Mon Oct 4 12:39:43 2010 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100803.1) ProcEnviron: LANG=de_DE.utf8 SHELL=/bin/bash SourcePackage: openssl To manage notifications about this bug go to: https://bugs.launchpad.net/openssl/+bug/654493/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 579081] Re: Segfault in HMAC_Init_ex () from /lib/i686/cmov/libcrypto.so.0.9.8
** Changed in: openssl Status: Unknown => Fix Released -- 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/579081 Title: Segfault in HMAC_Init_ex () from /lib/i686/cmov/libcrypto.so.0.9.8 Status in OpenSSL: Fix Released Status in openssl package in Ubuntu: Fix Released Bug description: Both gm-notify.py and gm-notify-config.py crash on startup with a segfault in HMAC_Init_ex () from /lib/i686/cmov/libcrypto.so.0.9.8. To manage notifications about this bug go to: https://bugs.launchpad.net/openssl/+bug/579081/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 965371] Re: HTTPS requests fail on sites which immediately close the connection if TLS 1.1 negotiation is attempted, on Ubuntu 12.04
** Changed in: openssl Status: Confirmed => Fix Released -- 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/965371 Title: HTTPS requests fail on sites which immediately close the connection if TLS 1.1 negotiation is attempted, on Ubuntu 12.04 Status in OpenSSL: Fix Released Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Precise: Triaged Status in openssl package in Debian: Fix Released Bug description: This week, HTTPS connections from a Python script I wrote started giving me this error: urllib2.URLError: This used to work up until some three days ago and still works on other Ubuntu versions, but not in other Python versions on Precise. I was suspecting this was a bug in Python, but a guy on AskUbuntu ( http://askubuntu.com/questions/116020/python-https-requests-urllib2 -to-some-sites-fail-on-ubuntu-12-04-without-proxy/116059#116059 ) found out this happens using the openssl command line tool too: $ openssl s_client -connect www.mediafire.com:443 But succeeds if forcing TLS 1 with the -tls1 argument. To manage notifications about this bug go to: https://bugs.launchpad.net/openssl/+bug/965371/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 624361] Re: service ssh restart does not test the configuration file
Fixed by Colin in 1:6.7p1-5+deb8u4 1:7.4p1-10+deb9u2 1:7.5p1-6 by hat
only Xenial still is affected.
But by now Xenial configs should work already since thre is already the
next LTS released.
** Also affects: openssh (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: openssh (Ubuntu)
Status: Triaged => Fix Released
** Changed in: openssh (Ubuntu Xenial)
Status: New => Triaged
** Changed in: openssh (Ubuntu Xenial)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/624361
Title:
service ssh restart does not test the configuration file
Status in openssh package in Ubuntu:
Fix Released
Status in openssh source package in Xenial:
Triaged
Status in openssh package in Debian:
Fix Released
Bug description:
I would have expect "service ssh restart" to run the configuration
test as "/etc/init.d/ssh restart" do. Or at least, I would have expect
to have a meaningful exit status in case of failure.
I modified "/etc/ssh/sshd_config" and mistakenly inserted an error. I
tried to apply my modification by restarting SSH :
# service ssh restart
ssh start/running
# echo $?
0
Because no error were reported I assumed that SSH was running with the
new configuration. I was wrong because SSH never restarted because of
a the syntax error in /etc/ssh/sshd_config.
After some digging I found the error :
# service ssh try-restart
/etc/ssh/sshd_config line 100: Directive 'AllowUsers' is not allowed within a
Match block
Am I wrong to expecting that the new starting method provided in Lucid
("service ") is equivalent to the old technique
involving an init script ?
# lsb_release -rd
Description: Ubuntu 10.04.1 LTS
Release: 10.04
# apt-cache policy openssh-server
openssh-server:
Installed: 1:5.3p1-3ubuntu4
Candidate: 1:5.3p1-3ubuntu4
Version table:
*** 1:5.3p1-3ubuntu4 0
500 http://ca.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages
100 /var/lib/dpkg/status
1:5.3p1-3ubuntu3 0
500 http://ca.archive.ubuntu.com/ubuntu/ lucid/main Packages
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: openssh-server 1:5.3p1-3ubuntu4
ProcVersionSignature: Ubuntu 2.6.32-24.41-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic x86_64
Architecture: amd64
Date: Wed Aug 25 20:56:54 2010
ProcEnviron:
LANG=en_US.UTF8
SHELL=/bin/bash
SourcePackage: openssh
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/624361/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1018998] Re: SSL_OP_ALL incorrectly disables TLS 1.1
** Changed in: openssl Status: Unknown => Fix Released -- 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/1018998 Title: SSL_OP_ALL incorrectly disables TLS 1.1 Status in OpenSSL: Fix Released Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Precise: Fix Released Status in openssl source package in Quantal: Fix Released Bug description: From the openssl 1.0.1b changelog: *) OpenSSL 1.0.0 sets SSL_OP_ALL to 0x8FFFL and OpenSSL 1.0.1 and 1.0.1a set SSL_OP_NO_TLSv1_1 to 0x0400L which would unfortunately mean any application compiled against OpenSSL 1.0.0 headers setting SSL_OP_ALL would also set SSL_OP_NO_TLSv1_1, unintentionally disablng TLS 1.1 also. Fix this by changing the value of SSL_OP_NO_TLSv1_1 to 0x1000L Any application which was previously compiled against OpenSSL 1.0.1 or 1.0.1a headers and which cares about SSL_OP_NO_TLSv1_1 will need to be recompiled as a result. Letting be results in inability to disable specifically TLS 1.1 and in client context, in unlike event, limit maximum offered version to TLS 1.0 Any package in the repo that got compiled on oneiric, or on precise before 2012-03-24 02:03:49 EDT got compiled with SSL_OP_ALL set to 0x8FFFL, and is telling openssl on precise to disable tls v1.1. openssl 1.0.1 had SSL_OP_ALL set to 0x8BFFL. We have two choices: 1- We rebuild all packages that are in the archive that were built before 2012-03-24 02:03:49 EDT so they set SSL_OP_ALL to 0x8BFFL. Unfortunately, that means when we push 1.0.1b to quantal, they will no longer be able to use SSL_OP_NO_TLSv1_1 to disable tlsv1.1 during runtime. 2- We issue an openssl security update for precise and quantal that switches SSL_OP_NO_TLSv1_1 to 0x1000L, as in 1.0.1b. This means old applications will not disable tls v1.1 by accident, but will no longer be able to use SSL_OP_NO_TLSv1_1 to disable tlsv1.1 during runtime. If some applications are known to rely on runtime disabling of tls v1.1, we can simply rebuild them once the openssl security update has been pushed out. To manage notifications about this bug go to: https://bugs.launchpad.net/openssl/+bug/1018998/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 969343] Re: Unable to connect to WPA enterprise wireless
** Changed in: openssl Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/969343 Title: Unable to connect to WPA enterprise wireless Status in OEM Priority Project: Fix Released Status in OEM Priority Project precise series: Fix Released Status in OpenSSL: Invalid Status in wpa_supplicant: In Progress Status in openssl package in Ubuntu: Invalid Status in wpa package in Ubuntu: Fix Released Status in wpasupplicant package in Ubuntu: Invalid Status in openssl source package in Precise: Invalid Status in wpa source package in Precise: Invalid Status in wpasupplicant source package in Precise: Fix Released Status in wpa package in Debian: Fix Released Status in openssl package in Fedora: New Status in wpasupplicant package in Fedora: Invalid Bug description: [Impact] Breaks 802.1x (PEAP) authentication for wireless networks using specific authentication servers and/or AP hardware. Aruba network devices specifically are known to be affected; and is a popular device type used in enterprises to secure wireless networks. [Test Case] This issue is hardware specific and may or may not be limited to Aruba authentication servers. 1) Attempt to connect / authenticate to a wireless, 802.1x network requiring Protected EAP (or possibly other auth mechanisms). 2) (optionally) Watch SSL traffic between the station and authentication server using wireshark/tcpdump, looking for auth failures and the extensions passed. [Regression Potential] Since this changes the SSL extensions and options used to connect to 802.1x wireless networks; some networks specifically configured to request or make use of the session ticket extension could be made impossible to successfully authenticate to; up to the point where multiple connection failures could lock the accounts used in highly-restricted networks. Also, there is a potential (again, due to the change in SSL options) for other networks (using specific AP hardware) that don't support the extensions used to fail authentication. --- Using identical settings as in 11.10, I am unable to make a wpa enterprise connection using xubuntu precise beta 2. This is a Lenovo X220 with a Centrino Advanced-N 6205 wireless interface. During the attempted logon, I am not presented with a certificate to approve, although wireless instructions for OSX suggest that I should be. However, I never had to approve a certificate when connecting with 11.10 -- I just ignored the certificate screen and everything worked. This seems like the relevant excerpt from syslog: Mar 30 10:39:01 fin8344m2 wpa_supplicant[1116]: Trying to associate with 00:11:92:3e:79:80 (SSID='Northwestern' freq=2462 MHz) Mar 30 10:39:01 fin8344m2 NetworkManager[848]: (wlan0): supplicant interface state: scanning -> associating Mar 30 10:39:01 fin8344m2 kernel: [ 2201.940422] wlan0: authenticated Mar 30 10:39:01 fin8344m2 kernel: [ 2201.940974] wlan0: associate with 00:11:92:3e:79:80 (try 1) Mar 30 10:39:01 fin8344m2 kernel: [ 2201.943165] wlan0: RX ReassocResp from 00:11:92:3e:79:80 (capab=0x431 status=0 aid=222) Mar 30 10:39:01 fin8344m2 kernel: [ 2201.943174] wlan0: associated Mar 30 10:39:01 fin8344m2 wpa_supplicant[1116]: Associated with 00:11:92:3e:79:80 Mar 30 10:39:01 fin8344m2 wpa_supplicant[1116]: CTRL-EVENT-EAP-STARTED EAP authentication started Mar 30 10:39:01 fin8344m2 NetworkManager[848]: (wlan0): supplicant interface state: associating -> associated Mar 30 10:39:01 fin8344m2 wpa_supplicant[1116]: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=25 Mar 30 10:39:01 fin8344m2 wpa_supplicant[1116]: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected Mar 30 10:39:01 fin8344m2 wpa_supplicant[1116]: SSL: SSL3 alert: read (remote end reported an error):fatal:bad certificate Mar 30 10:39:01 fin8344m2 wpa_supplicant[1116]: OpenSSL: openssl_handshake - SSL_connect error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate Mar 30 10:39:01 fin8344m2 wpa_supplicant[1116]: CTRL-EVENT-EAP-FAILURE EAP authentication failed Mar 30 10:39:01 fin8344m2 kernel: [ 2201.969742] wlan0: deauthenticated from 00:11:92:3e:79:80 (Reason: 23) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 2.0-0ubuntu1 Architecture: amd64 Date: Fri Mar 30 10:34:13 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=en_US:en TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash
[Touch-packages] [Bug 1051892] Re: [Quantal] Regression in TLS 1.2 workarounds
** Changed in: openssl Status: Unknown => Fix Released -- 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/1051892 Title: [Quantal] Regression in TLS 1.2 workarounds Status in OpenSSL: Fix Released Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Quantal: Fix Released Bug description: openssl 1.0.1c-3ubuntu1 dropped almost all of debian/patches/tls12_workarounds.patch because the upstream 1.0.1c release contained the changes. However, the dropped pieces of tls12_workarounds.patch had a subtle difference from upstream. In the Ubuntu patch, ssl23_client_hello() checked the *client* TLS version when deciding if the cipher list should be truncated or not for TLS 1.2. The upstream code (http://cvs.openssl.org/chngview?cn=22408) checks the *negotiated* TLS version, which I believe is incorrect since the ServerHello hasn't even occurred yet in order to negotiate the TLS version. The change from TLS1_get_versions() to TLS1_get_client_versions() was discussed here: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/986147/comments/4 This bug can be reproduced with the following command: $ openssl s_client -connect d2chzxaqi4y7f8.cloudfront.net:443 -CApath /etc/ssl/certs/ It will fail unless -tls1 is specified like so: $ openssl s_client -connect d2chzxaqi4y7f8.cloudfront.net:443 -CApath /etc/ssl/certs/ -tls1 Making this change fixes the problem (ssl3_client_hello() will probably need the same change): --- openssl-1.0.1c.orig/ssl/s23_clnt.c 2012-09-17 01:06:06.584617683 -0700 +++ openssl-1.0.1c/ssl/s23_clnt.c 2012-09-17 02:09:01.140540223 -0700 @@ -491,7 +491,7 @@ * as hack workaround chop number of supported ciphers * to keep it well below this if we use TLS v1.2 */ - if (TLS1_get_version(s) >= TLS1_2_VERSION + if (TLS1_get_client_version(s) >= TLS1_2_VERSION && i > OPENSSL_MAX_TLS1_2_CIPHER_LENGTH) i = OPENSSL_MAX_TLS1_2_CIPHER_LENGTH & ~1; #endif To manage notifications about this bug go to: https://bugs.launchpad.net/openssl/+bug/1051892/+subscriptions -- Mailing list: https://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 1547927] Re: LDAP_OPT_X_TLS_REQUIRE_CERT handling differences between ldaps:// and STARTTLS
I can check again, but the last time I looked this was still broken ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1547927 Title: LDAP_OPT_X_TLS_REQUIRE_CERT handling differences between ldaps:// and STARTTLS Status in openldap package in Ubuntu: Incomplete Bug description: Tested with vivid and wily... also logged with openldap as http://www.openldap.org/its/index.cgi/Incoming?id=8374 The handling of the LDAP_OPT_X_TLS_REQUIRE_CERT option appears to be different between servers accessed via ldaps:// and ldap:// (plus STARTTLS) URIs. When accessing server with a self-signed certificate, the results are: ldaps:// neverOK hard Error: can't contact LDAP server demand Error: can't contact LDAP server allowOK try Error: can't contact LDAP server ldap:// plus explicit ldap_start_tls_s() neverOK hard OK demand OK allowOK try OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1547927/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1134873] Re: regression in 1.0.1-4ubuntu5.6 causes connection errors
** Changed in: openssl Status: New => Fix Released -- 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/1134873 Title: regression in 1.0.1-4ubuntu5.6 causes connection errors Status in OpenSSL: Fix Released Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Precise: Fix Released Status in openssl source package in Quantal: Fix Released Status in openssl source package in Raring: Fix Released Bug description: In our workplace we have a subversion repository that is accessed via an apache proxy. The proxy runs mod_proxy and uses SSL between the SVN client and the proxy (does not use SSL between the proxy and the actual SVN server) on ubuntu 12.04 LTS 64-bit. Yesterday some of our developers started getting strange error messages when using SVN, here is an example: svn: PROPFIND of '/svn/mike/test-django-tools/trunk/dev-packages': Could not read status line: SSL alert received: Bad record MAC This error did not occur on every request, but if a particular request failed then it was generally reproducible. Since nothing in our environment had changed, I checked our unnattended-upgrades logfiles and saw that openssl and libssl had been updated to 1.0.1-4ubuntu5.6 on Feb 22. After building previous version (1.0.1-4ubuntu5.5) and installing, the problem went away. To manage notifications about this bug go to: https://bugs.launchpad.net/openssl/+bug/1134873/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1420608] Re: s_client doesn't recognise XMPP STARTTLS messages with double quotes
** Changed in: openssl
Status: New => Fix Released
--
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/1420608
Title:
s_client doesn't recognise XMPP STARTTLS messages with double quotes
Status in OpenSSL:
Fix Released
Status in openssl package in Ubuntu:
Confirmed
Bug description:
OpenSSL s_client does not recognise the XML produced by some Jabber
servers (eg. OpenFire). The parameter values use double (") instead of
single quotes (') and s_client is too conservative in its string-
parsing routine.
To demonstrate the problem I used one of the public XMPP servers
running OpenFire 3.9.3:
openssl s_client -connect jabber.rootbash.com:5222 -starttls xmpp -debug
CONNECTED(0003)
write to 0x1124c10 [0x7fffdf2d49c0] (124 bytes => 124 (0x7C))
- 3c 73 74 72 65 61 6d 3a-73 74 72 65 61 6d 20 78
read from 0x1124c10 [0x1118800] (8192 bytes => 192 (0xC0))
- 3c 3f 78 6d 6c 20 76 65-72 73 69 6f 6e 3d 27 31 http://etherx
0050 - 2e 6a 61 62 62 65 72 2e-6f 72 67 2f 73 74 72 65 .jabber.org/stre
0060 - 61 6d 73 22 20 78 6d 6c-6e 73 3d 22 6a 61 62 62 ams" xmlns="jabb
0070 - 65 72 3a 63 6c 69 65 6e-74 22 20 66 72 6f 6d 3d er:client" from=
0080 - 22 6a 61 62 62 65 72 2e-72 6f 6f 74 62 61 73 68 "jabber.rootbash
0090 - 2e 63 6f 6d 22 20 69 64-3d 22 61 39 64 33 30 61 .com" id="a9d30a
00a0 - 34 32 22 20 78 6d 6c 3a-6c 61 6e 67 3d 22 65 6e 42" xml:lang="en
00b0 - 22 20 76 65 72 73 69 6f-6e 3d 22 31 2e 30 22 3e " version="1.0">
read from 0x1124c10 [0x1118800] (8192 bytes => 428 (0x1AC))
- 3c 73 74 72 65 61 6d 3a-66 65 61 74 75 72 65 73 DI
0090 - 47 45 53 54 2d 4d 44 35-3c 2f 6d 65 63 68 61 6e GEST-MD5P
00b0 - 4c 41 49 4e 3c 2f 6d 65-63 68 61 6e 69 73 6d 3e LAIN
00c0 - 3c 6d 65 63 68 61 6e 69-73 6d 3e 41 4e 4f 4e 59 ANONY
00d0 - 4d 4f 55 53 3c 2f 6d 65-63 68 61 6e 69 73 6d 3e MOUS
00e0 - 3c 6d 65 63 68 61 6e 69-73 6d 3e 43 52 41 4d 2d CRAM-
00f0 - 4d 44 35 3c 2f 6d 65 63-68 61 6e 69 73 6d 3e 3c MD5<
0100 - 2f 6d 65 63 68 61 6e 69-73 6d 73 3e 3c 63 6f 6d /mechanisms>http://jabber.or
0130 - 67 2f 66 65 61 74 75 72-65 73 2f 63 6f 6d 70 72 g/features/compr
0140 - 65 73 73 22 3e 3c 6d 65-74 68 6f 64 3e 7a 6c 69 ess">zli
0150 - 62 3c 2f 6d 65 74 68 6f-64 3e 3c 2f 63 6f 6d 70 bhttp://jabb
0180 - 65 72 2e 6f 72 67 2f 66-65 61 74 75 72 65 73 2f er.org/features/
0190 - 69 71 2d 61 75 74 68 22-2f 3e 3c 2f 73 74 72 65 iq-auth"/>
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 620 bytes and written 124 bytes
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
---
The "no peer certificate available" is incorrect, it appears because
s_client doesn't correctly recognise the response from the remote
server.
The problem comes from the hard-coded string that s_client is looking for
during communication with the remote server here:
https://github.com/openssl/openssl/blob/OpenSSL_1_0_1-stable/apps/s_client.c#L1461
- the utility expects only a single-quoted string, while the standard also
allows the use of double quotes.
There is a bug report and a series of patches for various XMPP-related
bugs submitted in OpenSSL RT bugtracker
https://rt.openssl.org/Ticket/Display.html?id=2860=guest=guest
(and more specifically for this problem -
https://rt.openssl.org/Ticket/Display.html?id=2860#txn-34620). This
issue has been fixed in the upstream Git repository in the master
branch
(https://github.com/openssl/openssl/blob/fbf08b79ff33110c242849e836aeb494bc03a132/apps/s_client.c#L1620).
Please consider including these patches.
Also please update the man page for s_client, it is for a previous
version of the utility and doesn't mention STARTTLS XMPP support at
all.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: openssl 1.0.1f-1ubuntu2.8
ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
Uname: Linux 3.13.0-45-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Feb 10 21:59:30 2015
InstallationDate: Installed on 2014-07-07 (218 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: openssl
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/openssl/+bug/1420608/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1133333] Re: SSL read error: decryption failed or bad record mac
** Changed in: openssl Status: New => Fix Released -- 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/113 Title: SSL read error: decryption failed or bad record mac Status in OpenSSL: Fix Released Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Precise: Fix Released Status in openssl source package in Quantal: Fix Released Status in openssl source package in Raring: Fix Released Status in openssl package in Debian: Fix Released Bug description: I have Ubuntu-12.10/irssi 0.8.15/libssl 1.0.1c-3. After connecting successfully to an SSL IRC server and joining some channel on it, I get the error read error: decryption failed or bad record mac after which the connection terminates. I didn't have any problem with this before, the error started to occur only yesterday after an Ubuntu security update from libssl 1.0.1c-3ubuntu2 to 1.0.1c-3ubuntu2.1. Using the version 1.0.1c-3ubuntu2 of libssl and libcrypto gets rid of the problem. --- ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 DistroRelease: Ubuntu 12.10 InstallationDate: Installed on 2013-02-15 (10 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True Package: openssl 1.0.1c-3ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.5.0-25.38-generic 3.5.7.4 Tags: quantal running-unity Uname: Linux 3.5.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/openssl/+bug/113/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1594748] Re: CRYPTO_set_mem_functions() is broken
** Changed in: openssl
Status: Unknown => Invalid
--
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/1594748
Title:
CRYPTO_set_mem_functions() is broken
Status in OpenSSL:
Invalid
Status in openssl package in Ubuntu:
Fix Released
Status in openssl source package in Xenial:
Fix Released
Bug description:
Description: Ubuntu 16.04 LTS
Release: 16.04
openssl:
Installed: 1.0.2g-1ubuntu4.1
Candidate: 1.0.2g-1ubuntu4.1
Version table:
*** 1.0.2g-1ubuntu4.1 500
500 http://fi.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
1.0.2g-1ubuntu4 500
500 http://fi.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
CRYPTO_set_mem_functions() always returns 0 because library
initialization already calls CRYPTO_malloc() and disables it:
#0 CRYPTO_malloc (num=num@entry=1168, file=file@entry=0x770ae02c
"fips_drbg_lib.c",
line=line@entry=106) at mem.c:329
#1 0x770596df in FIPS_drbg_new (type=type@entry=0,
flags=flags@entry=0)
at fips_drbg_lib.c:106
#2 0x7705aeb9 in FIPS_drbg_health_check (
dctx=dctx@entry=0x7731c960 ) at fips_drbg_selftest.c:760
#3 0x770595f0 in FIPS_drbg_init (dctx=dctx@entry=0x7731c960
,
type=, flags=) at fips_drbg_lib.c:94
#4 0x76fe38f3 in RAND_init_fips () at rand_lib.c:287
#5 0x76f26f7a in OPENSSL_init_library () at o_init.c:119
#6 0x77de74ea in call_init (l=, argc=argc@entry=1,
argv=argv@entry=0x7fffe5e8, env=env@entry=0x7fffe5f8) at
dl-init.c:72
#7 0x77de75fb in call_init (env=0x7fffe5f8, argv=0x7fffe5e8,
argc=1,
l=) at dl-init.c:30
#8 _dl_init (main_map=main_map@entry=0x640380, argc=1, argv=0x7fffe5e8,
env=0x7fffe5f8) at dl-init.c:120
This doesn't happen in upstream OpenSSL or in Debian's OpenSSL.
Looking at the patches, this is caused by FIPS_drbg_init() in
openssl-1.0.2g-fips.patch:
+if (!(dctx->xflags & DRBG_FLAG_TEST)) {
+if (!FIPS_drbg_health_check(dctx)) {
+FIPSerr(FIPS_F_FIPS_DRBG_INIT, FIPS_R_SELFTEST_FAILURE);
+return 0;
+}
+}
I don't want any FIPS mode enabled though, so does it really even need
to call RAND_init_fips() then?
To manage notifications about this bug go to:
https://bugs.launchpad.net/openssl/+bug/1594748/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1651818] Re: busybox-initramfs needs different compile options to work with cryptroot-unlock
This bug was fixed in the package cryptsetup - 2:2.0.2-1ubuntu2 --- cryptsetup (2:2.0.2-1ubuntu2) cosmic; urgency=medium * Apply patch from Trent Nelson to fix cryptroot-unlock for busybox compatibility. LP: #1651818 -- Dimitri John Ledkov Thu, 21 Jun 2018 16:38:31 +0100 ** Changed in: cryptsetup (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 busybox in Ubuntu. https://bugs.launchpad.net/bugs/1651818 Title: busybox-initramfs needs different compile options to work with cryptroot-unlock Status in busybox package in Ubuntu: Won't Fix Status in cryptsetup package in Ubuntu: Fix Released Status in cryptsetup source package in Bionic: Confirmed Bug description: The cryptroot-unlock script in the cryptsetup package does not work in initramfs. It fails because "ps -e" is not available in busybox for initramfs. When building the package with CONFIG_DESKTOP=y CONFIG_EXTRA_COMPAT=y the needed commands (ps, grep) with parameter are there and it works. Tetsted on Ubuntu GNOME 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1651818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1712496] Re: package ssh 1:7.2p2-4ubuntu2.2 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd
Hi, from your log: aug 23 09:45:31 hostname sshd[1051]: error: Bind to port 22 on 192.168.2.4 failed: Cannot assign requested address. aug 23 09:45:31 hostname sshd[1051]: fatal: Cannot bind any address. aug 23 09:45:31 hostname systemd[1]: Failed to start OpenBSD Secure Shell server. It seems you have configured a listen address that does not exist. This makes the server (re-)start fail. And that in turn will break updates/installs. Please fix your configuration of sshd and things will resolve. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1712496 Title: package ssh 1:7.2p2-4ubuntu2.2 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd Status in openssh package in Ubuntu: Incomplete Bug description: openssh-server is installed, but cannot be reinstalled ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ssh 1:7.2p2-4ubuntu2.2 ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76 Uname: Linux 4.4.0-92-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 AptOrdering: libgraphite2-3: Install openssh-server: Configure ssh: Configure libgraphite2-3: Configure NULL: ConfigurePending Architecture: amd64 Date: Tue Aug 22 10:13:58 2017 ErrorMessage: vereistenproblemen - blijft ongeconfigureerd InstallationDate: Installed on 2014-04-20 (1221 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: openssh Title: package ssh 1:7.2p2-4ubuntu2.2 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1712496/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1712496] Re: package ssh 1:7.2p2-4ubuntu2.2 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd
Thank you for taking the time to report this bug and helping to make Ubuntu better. On upgrading a service this service has to be restarted to pick up the fixes. Rather rarely a real issue occurs that the newer version does e.g. fail with the formerly working configuration. But most of the time what happens is, that a service was installed, but stays unconfigured or experimented with but left in a broken state. Now on any update of the related packages that service has to be restarted, but since its config is incomplete/faulty it fails to restart. Therefore the update of that package has to consider itself incomplete. Depending on your particular case there are two solutions: - either remove the offending package if you don't want to continue using it. - Or if you do want to keep it please fix the configuration so that re-starting the service will work. Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete. If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New. ** Changed in: openssh (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1712496 Title: package ssh 1:7.2p2-4ubuntu2.2 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd Status in openssh package in Ubuntu: Incomplete Bug description: openssh-server is installed, but cannot be reinstalled ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ssh 1:7.2p2-4ubuntu2.2 ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76 Uname: Linux 4.4.0-92-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 AptOrdering: libgraphite2-3: Install openssh-server: Configure ssh: Configure libgraphite2-3: Configure NULL: ConfigurePending Architecture: amd64 Date: Tue Aug 22 10:13:58 2017 ErrorMessage: vereistenproblemen - blijft ongeconfigureerd InstallationDate: Installed on 2014-04-20 (1221 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: openssh Title: package ssh 1:7.2p2-4ubuntu2.2 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1712496/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1770617] Re: Dia-normal, GIMP crash when attempting to print using network printer
** Also affects: gtk+2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1770617 Title: Dia-normal, GIMP crash when attempting to print using network printer Status in dia package in Ubuntu: New Status in gimp package in Ubuntu: New Status in gtk+2.0 package in Ubuntu: New Bug description: When I attempt to print a diagram from dia-normal using one of the network printers offered by cups, the program crashes in the process of selecting a printer from the list of available printers. Steps to reproduce: 1) Start dia, open a diagram 2) Select File->Print 3) Click on a (network) printer in the list of printers -> Crash Expected result: The ability to click the print button and have my diagram roll off the printer. Actual result: Dia graphical interface disappears, the following assertion shows up in a terminal: *** Error in `dia-normal': double free or corruption (!prev): 0x0285db10 *** Additional information: - Disabling the avahi daemon makes this problem disappear without loss of network printing ability, presumably because our network configuration does not rely on printer auto-discovery. - Problems do not occur when printing from e.g. evince. - But similar problems do exist with the Gimp. Perhaps this is a bug in one of the libraries used by dia and Gimp (GTK2 print dialogue/back-end problems solved in GTK3?) - This bug may be related to bug #1701128, but without access to the logs I am unable to verify. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: dia 0.97.3-1 ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 Uname: Linux 4.4.0-124-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CurrentDesktop: GNOME Date: Fri May 11 11:09:10 2018 InstallationDate: Installed on 2016-05-04 (736 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: dia UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dia/+bug/1770617/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1547927] Re: LDAP_OPT_X_TLS_REQUIRE_CERT handling differences between ldaps:// and STARTTLS
Hi, I'm clearing old dormant bugs atm. Here are no good next step to take action. Also the referred upstream discussion seems to have fallen to slumber. Did you have luck trying newer versions of this or any other update that helps to get this bug moving again? Also we are waiting for answers to comment #5 as for others the issue seems not to trigger, and clear steps to reproduce would help. ** Changed in: openldap (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1547927 Title: LDAP_OPT_X_TLS_REQUIRE_CERT handling differences between ldaps:// and STARTTLS Status in openldap package in Ubuntu: Incomplete Bug description: Tested with vivid and wily... also logged with openldap as http://www.openldap.org/its/index.cgi/Incoming?id=8374 The handling of the LDAP_OPT_X_TLS_REQUIRE_CERT option appears to be different between servers accessed via ldaps:// and ldap:// (plus STARTTLS) URIs. When accessing server with a self-signed certificate, the results are: ldaps:// neverOK hard Error: can't contact LDAP server demand Error: can't contact LDAP server allowOK try Error: can't contact LDAP server ldap:// plus explicit ldap_start_tls_s() neverOK hard OK demand OK allowOK try OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1547927/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1723761] Re: unattended-upgrade hangs on shutdown when network is required for updates
This bug was fixed in the package apt - 1.7.0~alpha1 --- apt (1.7.0~alpha1) experimental; urgency=medium [ Julian Andres Klode ] * CMake: Fix builds without zstd * apt.conf.autoremove: Catch some new Ubuntu module packages * Fix build with new gtest (Closes: #897149) * tests: Do not expect requested-by if sudo was invoked by root * Run tests on GitLab CI * Handle a missed case of timed out ip addresses (LP: #1766542) * Lower default timeout from 120s to 30s * apt-key: Pass all instead of gpg-agent to gpgconf --kill (LP: #1773992) * Fix lock counting in debSystem * CI: Export DEBIAN_FRONTEND=noninteractive in all CI environments * Ensure that we are online in apt-daily-upgrade.service (LP: #1723761) * gitlab-ci: chmod 755 /root [ David Kalnischkies ] * move special READMEs into doc/ and format as md * Add boilerplate plural form to po/apt-all.pot * don't try SRV requests based on IP addresses * use 127.0.0.1 instead of localhost as default Tor proxy * Extend apt build-dep pkg/release to switch dep as needed * Support release selector for volatile files as well * Start pkg records for deb files with dpkg output * Deprectate buggy/incorrect Rls/PkgFile::IsOk methods * Support --with-source in show & search commands * Support local files as arguments in show command (Closes: 883206) * Drop alternative URIs we got a hash-based fail from * Handle by-hash URI construction more centrally * Don't force the same mirror for by-hash URIs * Reword error for timed out read/write on SOCKS proxy (Closes: #898886) * Don't show acquire warning for "hidden" components (Closes: #879591) * Use a steady clock source for progress reporting * Use steady clock source for bandwidth limitation [ Guillem Jover ] * Remove obsolete RCS keywords * Normalize authors through a mailmap file * po: Fill Project-Id-Version with correct project id and version * po: Fix translated string not matching format string arguments * po: Fix Language field to match actual locale * po: Remove spurious text in Plural-Forms field * po: Add missing Plural-Forms fields [ Filipe Brandenburger ] * Update .gitignore * Increase debug verbosity in `apt-get autoremove` * Extend test-apt-get-autoremove to check debug output [ annadane ] * Add verb 'be' to NEWS entry for 1.5~beta1 (Closes: 892792) [ Алексей Шилин ] * Russian program translation update (Closes: 898797) [ Frans Spiesschaert ] * Dutch program translation update (Closes: #900589) * Dutch manpage translation update (Closes: #900602) -- Julian Andres Klode Mon, 25 Jun 2018 17:12:30 +0200 ** Changed in: apt (Ubuntu) Status: In Progress => Fix Released -- 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/1723761 Title: unattended-upgrade hangs on shutdown when network is required for updates Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Bug description: Recently an update for flashplugin-installer on xenial was available in the ubuntu repositories. During the installation of this package a blob is downloaded from Adobe servers, which requires network connectivity/internet access. Because the network interface(s) have already stopped when this package is installed, the server cannot be reached, thus blocking the shutdown process until a timeout kills the unattended-upgrades process. On my machines the shutdown takes about 30 minutes in this case. The systemd configuration is standard here, except for a few additional services. A possible fix could be adding After=network-online.target NetworkManager-wait-online.service to After= in the systemd unit file. As a workaround I pinned the flashplugin-installer to -1: #echo >/etc/apt/preferences.d/forbid_flashplugin "\ Package: flashplugin-installer Pin: release * Pin-Priority: -1"; To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1723761/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1702290] Re: slapd fails to stop if /etc/ldap/slapd.d/cn=config.ldif is deleted but /etc/ldap/slapd.d still exists
Thank you for taking the time to report this bug and helping to make Ubuntu better. On upgrading a service this service has to be restarted to pick up the fixes. Rather rarely a real issue occurs that the newer version does e.g. fail with the formerly working configuration. But most of the time what happens is, that a service was installed, but stays unconfigured or experimented with but left in a broken state. Now on any update of the related packages that service has to be restarted, but since its config is incomplete/faulty it fails to restart. Therefore the update of that package has to consider itself incomplete. Depending on your particular case there are two solutions: - either remove the offending package if you don't want to continue using it. - Or if you do want to keep it please fix the configuration so that re-starting the service will work. Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete. If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New. ** Changed in: openldap (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1702290 Title: slapd fails to stop if /etc/ldap/slapd.d/cn=config.ldif is deleted but /etc/ldap/slapd.d still exists Status in openldap package in Ubuntu: Incomplete Status in openldap package in Debian: New Bug description: after i install slapd and remove it's one of folders, couldnt do apt- get ugrade. It said problem about header ProblemType: Package DistroRelease: Ubuntu 14.04 Package: slapd 2.4.31-1+nmu2ubuntu8.4 ProcVersionSignature: Ubuntu 3.13.0-95.142-generic 3.13.11-ckt39 Uname: Linux 3.13.0-95-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.1-0ubuntu3.23 AptOrdering: ldap-utils: Remove slapd: Remove Architecture: amd64 Date: Tue Jul 4 15:22:00 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DpkgHistoryLog: Start-Date: 2017-07-04 15:21:46 Commandline: apt-get remove slapd ldap-utils Remove: ldap-utils:amd64 (2.4.31-1+nmu2ubuntu8.4), slapd:amd64 (2.4.31-1+nmu2ubuntu8.4) DuplicateSignature: package:slapd:2.4.31-1+nmu2ubuntu8.4:subprocess installed pre-removal script returned error exit status 2 ErrorMessage: subprocess installed pre-removal script returned error exit status 2 InstallationDate: Installed on 2015-06-03 (761 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: openldap Title: package slapd 2.4.31-1+nmu2ubuntu8.4 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2 UpgradeStatus: Upgraded to trusty on 2016-05-30 (400 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1702290/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1702290] Re: slapd fails to stop if /etc/ldap/slapd.d/cn=config.ldif is deleted but /etc/ldap/slapd.d still exists
This is essentially a config change breaking the service (re)start. and due to that upgrades. While the init could be more resilient it is not really a bug but a misconfiguration as identified by Ryan already. Also the error message (these days) is not misleading at all (tried on cosmic): slapd[26348]: sed: can't read /etc/ldap/slapd.d/cn=config.ldif: No such file or directory Which after deleting the file makes sense :-) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1702290 Title: slapd fails to stop if /etc/ldap/slapd.d/cn=config.ldif is deleted but /etc/ldap/slapd.d still exists Status in openldap package in Ubuntu: Incomplete Status in openldap package in Debian: New Bug description: after i install slapd and remove it's one of folders, couldnt do apt- get ugrade. It said problem about header ProblemType: Package DistroRelease: Ubuntu 14.04 Package: slapd 2.4.31-1+nmu2ubuntu8.4 ProcVersionSignature: Ubuntu 3.13.0-95.142-generic 3.13.11-ckt39 Uname: Linux 3.13.0-95-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.1-0ubuntu3.23 AptOrdering: ldap-utils: Remove slapd: Remove Architecture: amd64 Date: Tue Jul 4 15:22:00 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DpkgHistoryLog: Start-Date: 2017-07-04 15:21:46 Commandline: apt-get remove slapd ldap-utils Remove: ldap-utils:amd64 (2.4.31-1+nmu2ubuntu8.4), slapd:amd64 (2.4.31-1+nmu2ubuntu8.4) DuplicateSignature: package:slapd:2.4.31-1+nmu2ubuntu8.4:subprocess installed pre-removal script returned error exit status 2 ErrorMessage: subprocess installed pre-removal script returned error exit status 2 InstallationDate: Installed on 2015-06-03 (761 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: openldap Title: package slapd 2.4.31-1+nmu2ubuntu8.4 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2 UpgradeStatus: Upgraded to trusty on 2016-05-30 (400 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1702290/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
A potential fix has been proposed in my askubuntu quesion: https://askubuntu.com/questions/1046810/cannot-downgrade-wpa-supplicant-to-fix-wifi-connection-to-a-corporate-network-w However, I have not been able to test if this works yet. (as I got some deadlines and cannot afford a potentially unstable machine at the moment). Feel free to try this, otherwise I will in a few weeks time. -- 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: Connection to open or WPA secured wifi works without any issues. Connection to WPA2/PEAP fails. Repeatedly asks for username/password. Possible gnome-shell integration issue. The system was updated from Xenial to Bionic in mid-January. At that time this WPA2/PEAP setup worked without any issues. With the updates coming in the last week of January / First February week - the bug was experienced. 1) ➜ syncthing git:(master) lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2) - up to date packages [code] ➜ cat /etc/apt/sources.list |egrep -v '^#' deb http://cz.archive.ubuntu.com/ubuntu/ bionic main restricted deb http://cz.archive.ubuntu.com/ubuntu/ bionic-updates main restricted deb http://cz.archive.ubuntu.com/ubuntu/ bionic universe deb http://cz.archive.ubuntu.com/ubuntu/ bionic-updates universe deb http://cz.archive.ubuntu.com/ubuntu/ bionic multiverse deb http://cz.archive.ubuntu.com/ubuntu/ bionic-updates multiverse deb http://security.ubuntu.com/ubuntu/ bionic-security multiverse main universe restricted [/code] Note: # some pkg version related to problem might be from proposed-updates repo 2b) [code] dpkg -l |egrep -i 'network manager|networkm|libnm' ii gir1.2-networkmanager-1.0:amd641.8.4-1ubuntu4 amd64GObject introspection data for the libnm-glib/libnm-util library ii gir1.2-nm-1.0:amd641.8.4-1ubuntu4 amd64GObject introspection data for the libnm library ii gir1.2-nmgtk-1.0:amd64 1.8.10-2ubuntu1 amd64GObject introspection data for libnm-gtk ii libnm-glib-vpn1:amd64 1.8.4-1ubuntu4 amd64network management framework (GLib VPN shared library) ii libnm-glib4:amd64 1.8.4-1ubuntu4 amd64network management framework (GLib shared library) ii libnm-gtk0:amd64 1.8.10-2ubuntu1 amd64library for wireless and mobile dialogs (libnm-glib version) ii libnm-util2:amd64 1.8.4-1ubuntu4 amd64network management framework (shared library) ii libnm0:amd64 1.8.4-1ubuntu4 amd64GObject-based client library for NetworkManager ii libnma0:amd64 1.8.10-2ubuntu1 amd64library for wireless and mobile dialogs (libnm version) ii libproxy1-plugin-networkmanager:amd64 0.4.15-0ubuntu1 amd64automatic proxy configuration management library (Network Manager plugin) ii network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu4 all NetworkManager configuration to enable connectivity checking ii strongswan-nm 5.6.1-2ubuntu1 amd64strongSwan plugin to interact with NetworkManager ii wpasupplicant 2:2.6-15ubuntu2 amd64client support for WPA and WPA2 (IEEE 802.11i) [/code] 3,4) Connection to open or WPA secured wifi works withou any issues. Connection to WPA2/PLEAP (without cert, just with username/password fails). Although wifi layer get's is associated the client (network-manager) possibly due to bug deauthenticate itself without establishing an IP connection. Connect to network. 5) Logs (syslog/kernel) Core moments: [code] Feb 12 09:19:02 dontpanic NetworkManager[1125]: [1518423542.9125] keyfile: update /etc/NetworkManager/system-connections/WiFi (82c55e94-907a-458a-ae31-8cbd75db0fa5,"WiFi") Feb 12 09:19:02 dontpanic gnome-shell[4284]: g_value_get_string:
[Touch-packages] [Bug 1741128] Re: libmagic1 in 16.04 reports XLS files as application/CDFV2-unknown
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: file (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to file in Ubuntu. https://bugs.launchpad.net/bugs/1741128 Title: libmagic1 in 16.04 reports XLS files as application/CDFV2-unknown Status in file package in Ubuntu: Confirmed Bug description: The libmagic1 package repots XLS files as application/CDFV2-unknown This is a bug in the libmagic code and has been fixed in version 5.31 and up. see: https://github.com/mscdex/mmmagic/issues/107 We have a file transfer app running on LTS 16.04 and it's constantly rejecting files of .xls Deleted /companies/5412/FROM/RDMS_History.XLS Mime Type:application/CDFV2-unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file/+bug/1741128/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776218] Re: New style hook support not robust on removal
** Changed in: apt (Ubuntu)
Status: New => In Progress
** Changed in: apt (Ubuntu)
Importance: Undecided => High
** Changed in: apt (Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
--
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/1776218
Title:
New style hook support not robust on removal
Status in apt package in Ubuntu:
In Progress
Bug description:
The new style (json-rpc) hooks are great. However when using them in snapd we
noticed the following problem. When shipping a hook in
/etc/apt/apt.conf.d/20snapd.conf like:
```
AptCli::Hooks::Install { "[ ! -f /usr/bin/snap ] || /usr/bin/snap advise-snap
--from-apt || true"; };
```
this works fine.
However when the snapd package is removed apt fails with:
```
...
Purging configuration files for snapd (1337.2.32.8) ...
Final directory cleanup
Discarding preserved snap namespaces
Removing extra snap-confine apparmor rules
Removing snapd cache
Removing snapd state
E: Could not read response to hello message from hook [ ! -f /usr/bin/snap ]
|| /usr/bin/snap advise-snap --from-apt || true: Connection reset by peer
E: Could not read message separator line after handshake from [ ! -f
/usr/bin/snap ] || /usr/bin/snap advise-snap --from-apt || true: Connection
reset by peer
quiet: end of output.
```
I.e. if the hook is not there apt still expectes a handshake.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1776218/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776218] Re: New style hook support not robust on removal
Any chance this can be fixed for 18.04.1 ?
--
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/1776218
Title:
New style hook support not robust on removal
Status in apt package in Ubuntu:
New
Bug description:
The new style (json-rpc) hooks are great. However when using them in snapd we
noticed the following problem. When shipping a hook in
/etc/apt/apt.conf.d/20snapd.conf like:
```
AptCli::Hooks::Install { "[ ! -f /usr/bin/snap ] || /usr/bin/snap advise-snap
--from-apt || true"; };
```
this works fine.
However when the snapd package is removed apt fails with:
```
...
Purging configuration files for snapd (1337.2.32.8) ...
Final directory cleanup
Discarding preserved snap namespaces
Removing extra snap-confine apparmor rules
Removing snapd cache
Removing snapd state
E: Could not read response to hello message from hook [ ! -f /usr/bin/snap ]
|| /usr/bin/snap advise-snap --from-apt || true: Connection reset by peer
E: Could not read message separator line after handshake from [ ! -f
/usr/bin/snap ] || /usr/bin/snap advise-snap --from-apt || true: Connection
reset by peer
quiet: end of output.
```
I.e. if the hook is not there apt still expectes a handshake.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1776218/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778566] Re: [radeon] Screen does not refresh till the mouse moves (ATI ES1000 GPU)
I will report it there. But are you sure that is not a Wayland issue? That something on the graphics loop can block the whole execution of the program and be woken up by mouse movement sounds like a deep architectural problem to me. The graphics card is rare, it is integrated in a HP ProLiant DL380 G6, a server system with dual Xeon processors. -- 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/1778566 Title: [radeon] Screen does not refresh till the mouse moves (ATI ES1000 GPU) Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: When Wayland is activated in GDM, nothing happens when selecting an account with the keyboard or typing in the password. I have to type, then wait, then move the mouse around for the characters to appears. Because I wouldn't believe this report, I made a video of the problem: https://peertube.mastodon.host/videos/watch/a4d02b33-d71e-4b0e-82cf- f2a74f952ca5 Moving from Wayland to X makes the issue disappear. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.2-0ubuntu1.2 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 25 18:39:19 2018 InstallationDate: Installed on 2018-06-17 (8 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.gdm3.custom.conf: [modified] mtime.conffile..etc.gdm3.custom.conf: 2018-06-24T23:13:52.497184 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1778566/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
