[Touch-packages] [Bug 1788807] Re: Bluetooth device not detected after resume from suspend [Qualcomm Atheros QCA9565]
[Expired for gnome-bluetooth (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-bluetooth (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1788807 Title: Bluetooth device not detected after resume from suspend [Qualcomm Atheros QCA9565] Status in bluez package in Ubuntu: Expired Status in gnome-bluetooth package in Ubuntu: Expired Bug description: When I suspend my laptop, it often happens that the bluetooth stops working. From gnome settings it is shown like if I had no bluetooth device at all. $ lspci -nnk | grep -iA3 net; lsusb; rfkill list; uname -r; dmesg | egrep -i 'blue|firm' 03:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01) Subsystem: AzureWave QCA9565 / AR9565 Wireless Network Adapter [1a3b:2130] Kernel driver in use: ath9k Kernel modules: ath9k 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI Express Card Reader [10ec:5287] (rev 01) -- 04:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12) Subsystem: ASUSTeK Computer Inc. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1043:200f] Kernel driver in use: r8169 Kernel modules: r8169 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 006: ID 13d3:3408 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 4.15.0-32-generic [0.024000] Spectre V2 : Enabling Restricted Speculation for firmware calls [0.048030] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [2.758768] [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS [ 35.407491] Bluetooth: Core ver 2.22 [ 35.407504] Bluetooth: HCI device and connection manager initialized [ 35.407506] Bluetooth: HCI socket layer initialized [ 35.407507] Bluetooth: L2CAP socket layer initialized [ 35.407510] Bluetooth: SCO socket layer initialized [ 53.501780] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 53.501780] Bluetooth: BNEP filters: protocol multicast [ 53.501783] Bluetooth: BNEP socket layer initialized [ 87.220137] Bluetooth: RFCOMM TTY layer initialized [ 87.220143] Bluetooth: RFCOMM socket layer initialized [ 87.220149] Bluetooth: RFCOMM ver 1.11 [ 1675.503865] usb 1-5: device firmware changed [ 1681.095543] Bluetooth: Can't get version to change to load ram patch err [ 1681.095546] Bluetooth: Loading patch file failed [ 4105.994687] audit: type=1107 audit(1534926184.213:339): pid=1258 uid=105 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=10248 label="snap.signal-desktop.signal-desktop" peer_pid=1314 peer_label="unconfined" Trying to use bluetooth from bluetoothctl $ bluetoothctl Agent registered [bluetooth]# scan on No default controller available Trying to restart the bluetooth service doesn't produce any effect: $ sudo service bluetooth restart Getting bluetooth service status: $ sudo service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset Active: active (running) since Fri 2018-08-24 11:23:17 EEST; 1min 35s ago Docs: man:bluetoothd(8) Main PID: 24999 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4915) CGroup: /system.slice/bluetooth.service └─24999 /usr/lib/bluetooth/bluetoothd elo 24 11:23:17 fabio-X550JK systemd[1]: Stopping Bluetooth service... elo 24 11:23:17 fabio-X550JK systemd[1]: Stopped Bluetooth service. elo 24 11:23:17 fabio-X550JK systemd[1]: Starting Bluetooth service... elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Bluetooth daemon 5.48 elo 24 11:23:17 fabio-X550JK systemd[1]: Started Bluetooth service. elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Starting SDP server elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Bluetooth management interface 1 lines 1-17/17 (END) Reloading the driver: $ sudo modprobe -r btusb; sudo modprobe btusb; $ sudo service bluetooth restart None of these attempts could solve the issue. What happens? Bluetooth is working, I suspend my laptop, I resume my laptop -> Bluetooth controller is no longer recognised and bluetooth service cannot be used anymore. What would you expect? Bluetooth controller to be recognised and working also after resume. P
[Touch-packages] [Bug 1788807] Re: Bluetooth device not detected after resume from suspend [Qualcomm Atheros QCA9565]
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1788807 Title: Bluetooth device not detected after resume from suspend [Qualcomm Atheros QCA9565] Status in bluez package in Ubuntu: Expired Status in gnome-bluetooth package in Ubuntu: Expired Bug description: When I suspend my laptop, it often happens that the bluetooth stops working. From gnome settings it is shown like if I had no bluetooth device at all. $ lspci -nnk | grep -iA3 net; lsusb; rfkill list; uname -r; dmesg | egrep -i 'blue|firm' 03:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01) Subsystem: AzureWave QCA9565 / AR9565 Wireless Network Adapter [1a3b:2130] Kernel driver in use: ath9k Kernel modules: ath9k 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI Express Card Reader [10ec:5287] (rev 01) -- 04:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12) Subsystem: ASUSTeK Computer Inc. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1043:200f] Kernel driver in use: r8169 Kernel modules: r8169 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 006: ID 13d3:3408 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 4.15.0-32-generic [0.024000] Spectre V2 : Enabling Restricted Speculation for firmware calls [0.048030] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [2.758768] [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS [ 35.407491] Bluetooth: Core ver 2.22 [ 35.407504] Bluetooth: HCI device and connection manager initialized [ 35.407506] Bluetooth: HCI socket layer initialized [ 35.407507] Bluetooth: L2CAP socket layer initialized [ 35.407510] Bluetooth: SCO socket layer initialized [ 53.501780] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 53.501780] Bluetooth: BNEP filters: protocol multicast [ 53.501783] Bluetooth: BNEP socket layer initialized [ 87.220137] Bluetooth: RFCOMM TTY layer initialized [ 87.220143] Bluetooth: RFCOMM socket layer initialized [ 87.220149] Bluetooth: RFCOMM ver 1.11 [ 1675.503865] usb 1-5: device firmware changed [ 1681.095543] Bluetooth: Can't get version to change to load ram patch err [ 1681.095546] Bluetooth: Loading patch file failed [ 4105.994687] audit: type=1107 audit(1534926184.213:339): pid=1258 uid=105 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=10248 label="snap.signal-desktop.signal-desktop" peer_pid=1314 peer_label="unconfined" Trying to use bluetooth from bluetoothctl $ bluetoothctl Agent registered [bluetooth]# scan on No default controller available Trying to restart the bluetooth service doesn't produce any effect: $ sudo service bluetooth restart Getting bluetooth service status: $ sudo service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset Active: active (running) since Fri 2018-08-24 11:23:17 EEST; 1min 35s ago Docs: man:bluetoothd(8) Main PID: 24999 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4915) CGroup: /system.slice/bluetooth.service └─24999 /usr/lib/bluetooth/bluetoothd elo 24 11:23:17 fabio-X550JK systemd[1]: Stopping Bluetooth service... elo 24 11:23:17 fabio-X550JK systemd[1]: Stopped Bluetooth service. elo 24 11:23:17 fabio-X550JK systemd[1]: Starting Bluetooth service... elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Bluetooth daemon 5.48 elo 24 11:23:17 fabio-X550JK systemd[1]: Started Bluetooth service. elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Starting SDP server elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Bluetooth management interface 1 lines 1-17/17 (END) Reloading the driver: $ sudo modprobe -r btusb; sudo modprobe btusb; $ sudo service bluetooth restart None of these attempts could solve the issue. What happens? Bluetooth is working, I suspend my laptop, I resume my laptop -> Bluetooth controller is no longer recognised and bluetooth service cannot be used anymore. What would you expect? Bluetooth controller to be recognised and working also after resume. ProblemType: Bug Di
[Touch-packages] [Bug 1807481] [NEW] Unable to enable/disable a repository in Software and Updates GUI
Public bug reported: When I click the checkbox to enable/disable a repository nothing happens. On 16.04 I was able to enable/disable repository in GUI, now I can't. Release Ubuntu 18.04.1 LTS package software-properties-gtk 0.96.24.32.5 I expect to enable/disable repository in GUI Nothing happens when I click the check box. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: software-properties-gtk 0.96.24.32.5 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Dec 8 02:55:00 2018 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2016-03-31 (981 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 SourcePackage: software-properties UpgradeStatus: Upgraded to bionic on 2018-09-18 (80 days ago) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Summary changed: - Unable to check not uncheck enabled/disabled repository in Software and Updates GUI. In 16.04 I was able to enable/disable repositories in the GUI, not I can't + Unable to enable/disable a repository in Software and Updates GUI -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1807481 Title: Unable to enable/disable a repository in Software and Updates GUI Status in software-properties package in Ubuntu: New Bug description: When I click the checkbox to enable/disable a repository nothing happens. On 16.04 I was able to enable/disable repository in GUI, now I can't. Release Ubuntu 18.04.1 LTS package software-properties-gtk 0.96.24.32.5 I expect to enable/disable repository in GUI Nothing happens when I click the check box. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: software-properties-gtk 0.96.24.32.5 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Dec 8 02:55:00 2018 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2016-03-31 (981 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 SourcePackage: software-properties UpgradeStatus: Upgraded to bionic on 2018-09-18 (80 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1807481/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807480] [NEW] [HP Pavilion Laptop 15-cd0xx, Realtek ALC295, Mic, Internal] Underruns, dropouts or crackling sound
Public bug reported: Whether I record with aux earbuds(with mics) or the internal mic I hear crackling with each sound. I tried using this https://wiki.ubuntu.com/Audio/PositionReporting but with no success. What should I do? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rgundlach2 2214 F pulseaudio /dev/snd/controlC0: rgundlach2 2214 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Dec 7 20:37:12 2018 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed Symptom_Card: Built-in Audio - HD-Audio Generic Symptom_Jack: Mic, Internal Symptom_PulseAudioLog: Dec 07 20:31:09 hp-pavillion dbus-daemon[1336]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.36' (uid=121 pid=1788 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Dec 07 20:33:56 hp-pavillion pulseaudio[1788]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [HP Pavilion Laptop 15-cd0xx, Realtek ALC295, Mic, Internal] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2018 dmi.bios.vendor: AMI dmi.bios.version: F.26 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8353 dmi.board.vendor: HP dmi.board.version: 37.34 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.26:bd07/25/2018:svnHP:pnHPPavilionLaptop15-cd0xx:pvr:rvnHP:rn8353:rvr37.34:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cd0xx dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-12-07T20:19:52.343950 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1807480 Title: [HP Pavilion Laptop 15-cd0xx, Realtek ALC295, Mic, Internal] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: New Bug description: Whether I record with aux earbuds(with mics) or the internal mic I hear crackling with each sound. I tried using this https://wiki.ubuntu.com/Audio/PositionReporting but with no success. What should I do? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rgundlach2 2214 F pulseaudio /dev/snd/controlC0: rgundlach2 2214 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Dec 7 20:37:12 2018 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed Symptom_Card: Built-in Audio - HD-Audio Generic Symptom_Jack: Mic, Internal Symptom_PulseAudioLog: Dec 07 20:31:09 hp-pavillion dbus-daemon[1336]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.36' (uid=121 pid=1788 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Dec 07 20:33:56 hp-pavillion pulseaudio[1788]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [HP Pavilion Laptop 15-cd0xx, Realtek ALC295, Mic, Internal] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2018 dmi.bios.vendor: AMI dmi.bios.version: F.26 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8353 dmi.board.vendor: HP dmi.board.version: 37.34 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.26:bd07/25/2018:svnHP:pnHPPavilionLaptop15-cd0xx:pvr:rvnHP:rn8353:rvr37.34:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cd0xx dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 201
[Touch-packages] [Bug 1713749] Re: Gtk-WARNING **: Theme parsing error: gtk.css
** Also affects: apport Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1713749 Title: Gtk-WARNING **: Theme parsing error: gtk.css Status in Apport: New Status in OpenShot Video Editor: New Status in apport package in Ubuntu: Invalid Bug description: I don't know where to report this bug. Pretty much every GUI application throws these warnings. $ ubuntu-bug apport-gtk (apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:597:14: not a number (apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:597:14: Expected a string. (apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:600:17: Expected a string. (apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:784:14: not a number (apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:784:14: Expected a string. (apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:787:17: Expected a string. (apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:1096:14: not a number (apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:1096:14: Expected a string. (apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:1099:17: Expected a string. (apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:2286:8: not a number (apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:2286:18: Using Pango syntax for the font: style property is deprecated; please use CSS syntax (apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:2291:8: not a number (apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:2291:18: Using Pango syntax for the font: style property is deprecated; please use CSS syntax (apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:4357:14: not a number (apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:4357:14: Expected a string. (apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:4419:12: not a number (apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:4419:12: Expected a string. (apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:4428:16: not a number (apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:4428:16: Expected a string. (apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:4443:22: not a number (apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:4443:22: Expected a string. (apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:4499:12: Expected a string. (apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:4501:16: not a number (apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:4501:16: Expected a string. (apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:4549:12: not a number (apport-gtk:3007): Gtk-WARNING **: Theme parsing error: gtk.css:4549:12: Expected a string. This happened after one of Ubuntu Studio upgrades. Studio uses Xfce. Is there a way to fix this? Maybe there is a better package to report? ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: apport-gtk 2.20.4-0ubuntu4.5 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportLog: ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CrashReports: 640:1000:118:2325445:2017-08-28 12:29:40.645797729 +0300:2017-08-28 12:29:41.645797729 +0300:/var/crash/_usr_bin_thunar.1000.crash CurrentDesktop: XFCE Date: Tue Aug 29 17:59:02 2017 PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to zesty on 2017-04-15 (135 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1713749/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 881137] Re: UFW does not clean iptables setting from /etc/ufw/before.rules
Please note that the various rules files are there for admins to adjust as needed. However, to work with other programs on the system, I reiterate that by default ufw will not flush anything it doesn't manage itself (MANAGE_BUILTINS, as mentioned, controls this behavior). If someone adds rules to these files then care is needed to add rules to remove them. You could add flush rules to do this like has been posted above, but as posted this is not much different from setting MANAGE_BUILTINS=yes. Perhaps you would like to instead add to the nat table your own chain, adding your rules to the chain, and then flush that chain (this is what ufw does internally for its chains). Maciej mentioned after_up, after_down, before_up and before_down. Please note that these days ufw supports something similar with its /etc/ufw/after.init and /etc/ufw/before.init scripts. See 'BOOT INITIALIZATION' in 'man ufw-framework' for details. Progress has been made on nat and other routing rules, so ufw will start to manage some of these others tables in a similar fashion as the filter table (thought it's been slow going). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/881137 Title: UFW does not clean iptables setting from /etc/ufw/before.rules Status in ufw package in Ubuntu: Won't Fix Bug description: Adding some additional settings to /etc/ufw/before.rules is not deleted when ufw is stopped. I added these lines at top of file /etc/ufw/before.rules *nat :POSTROUTING ACCEPT [0:0] -A POSTROUTING -o eth0 -j MASQUERADE COMMIT Then I reloaded ufw firewall with command: ufw reload. Output from iptables-save $ iptables-save -t nat *nat :PREROUTING ACCEPT [4:478] :INPUT ACCEPT [4:478] :OUTPUT ACCEPT [0:0] :POSTROUTING ACCEPT [0:0] -A POSTROUTING -o eth0 -j MASQUERADE COMMIT Then I reloaded ufw firewall again: $ iptables-save -t nat *nat :PREROUTING ACCEPT [4:478] :INPUT ACCEPT [4:478] :OUTPUT ACCEPT [0:0] :POSTROUTING ACCEPT [0:0] -A POSTROUTING -o eth0 -j MASQUERADE -A POSTROUTING -o eth0 -j MASQUERADE COMMIT And ufw reload again $ iptables-save -t nat *nat :PREROUTING ACCEPT [4:478] :INPUT ACCEPT [4:478] :OUTPUT ACCEPT [0:0] :POSTROUTING ACCEPT [0:0] -A POSTROUTING -o eth0 -j MASQUERADE -A POSTROUTING -o eth0 -j MASQUERADE -A POSTROUTING -o eth0 -j MASQUERADE COMMIT And again and postrouting is never deleted when ufw is stopped and added again when stared. Same happen if I stop ufw firewall with: $ stop ufw. nat lines are not cleaned. UFW should remove all iptables settings specified in config files after ufw is stopped! This can be dangerous if apt-get is updating some ufw files and scripts needs to reload ufw (some lines will be more times). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/881137/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability
** Changed in: gtk+3.0 (Ubuntu) Status: Triaged => In Progress ** Changed in: gtk+3.0 (Ubuntu Bionic) Status: New => In Progress ** Changed in: gtk+3.0 (Ubuntu Cosmic) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1763520 Title: after upgrade to bionic, printing fails without explanation / logs / debuggability Status in cups-filters package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: In Progress Status in cups-filters source package in Bionic: Invalid Status in gtk+3.0 source package in Bionic: In Progress Status in cups-filters source package in Cosmic: Invalid Status in gtk+3.0 source package in Cosmic: In Progress Bug description: [Impact] The problem occurs when the printer's driver package is updated and with this the PPD is replaced and one of the default settings of the queue is not available any more in the new PPD file. Then the setting is prefixed with "Custom." and with this the jobs fail. See comment #15 for more info. [Test Case] - Create a print queue with a PPD. - evince an arbitrary PDF file - Click the print icon - In the print dialog choose the newly created queue and choose some uncommon paper size (not custom). Click "Print". - Check /var/log/cups/error_log, the page size gets correctly received. - Close evince. - Stop CUPS, edit the PPD file removing the paper size you have selected for your job in the PageSize, PageRegion, PaperDimension, and ImageableArea lines. - Start CUPS. - Open the same PDF file again with evince, click Print and then select "Print" in the print dialog without changing anything. - The job fails, in /var/log/cups/error_log you see that the page size is prefixed with "Custom.". With the fixed package installed the job will print. [Regression Potential] The change applies only to saved settings of the print dialog not matching with any of the settings available in the PPD file. In rare cases the fix could fail by mis-understanding the setting and this way not being effective. For options which do not support setting custom values (the vast majority) the patch should always prevent a job failure though. [Other Info] Complete info about the bug and the fix in comment #15, Original bug description: I am unable to print to my network-attached printer after upgrade to bionic. ps shows: lp 26047 0.0 0.0 91668 5756 ?S15:06 0:00 \_ HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 lp 26050 0.1 0.0 0 0 ?Z15:06 0:00 | \_ [gs] lp 26048 0.0 0.0 79908 3836 ?S15:06 0:00 \_ HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 root 26049 0.0 0.0 84388 6192 ?S15:06 0:00 \_ ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 Note the un-reaped gs process. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 12 15:07:49 2018 InstallationDate: Installed on 2010-09-24 (2757 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) MachineType: LENOVO 2306CTO Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1 SourcePackage: c
[Touch-packages] [Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability
** Description changed: + [Impact] + + The problem occurs when the printer's driver package is updated and with + this the PPD is replaced and one of the default settings of the queue is + not available any more in the new PPD file. Then the setting is prefixed + with "Custom." and with this the jobs fail. + + See comment #15 for more info. + + [Test Case] + + - Create a print queue with a PPD. + - evince an arbitrary PDF file + - Click the print icon + - In the print dialog choose the newly created queue and choose some uncommon paper size (not custom). Click "Print". + - Check /var/log/cups/error_log, the page size gets correctly received. + - Close evince. + - Stop CUPS, edit the PPD file removing the paper size you have selected for your job in the PageSize, PageRegion, PaperDimension, and ImageableArea lines. + - Start CUPS. + - Open the same PDF file again with evince, click Print and then select "Print" in the print dialog without changing anything. + - The job fails, in /var/log/cups/error_log you see that the page size is prefixed with "Custom.". + + With the fixed package installed the job will print. + + [Regression Potential] + + The change applies only to saved settings of the print dialog not + matching with any of the settings available in the PPD file. In rare + cases the fix could fail by mis-understanding the setting and this way + not being effective. For options which do not support setting custom + values (the vast majority) the patch should always prevent a job failure + though. + + [Other Info] + + Complete info about the bug and the fix in comment #15, + + Original bug description: + I am unable to print to my network-attached printer after upgrade to bionic. ps shows: lp 26047 0.0 0.0 91668 5756 ?S15:06 0:00 \_ HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 lp 26050 0.1 0.0 0 0 ?Z15:06 0:00 | \_ [gs] lp 26048 0.0 0.0 79908 3836 ?S15:06 0:00 \_ HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 root 26049 0.0 0.0 84388 6192 ?S15:06 0:00 \_ ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 Note the un-reaped gs process. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 12 15:07:49 2018 InstallationDate: Installed on 2010-09-24 (2757 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) MachineType: LENOVO 2306CTO Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-03-21 (21 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO modified.conffile..etc.cups.cupsd.conf: [inaccessible: [Errno 13] Permission denied: '
[Touch-packages] [Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability
debdiff for bionic. ** Patch added: "gtk+3.0_3.22.30-1ubuntu1_3.22.30-1ubuntu1.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1763520/+attachment/5220194/+files/gtk+3.0_3.22.30-1ubuntu1_3.22.30-1ubuntu1.1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1763520 Title: after upgrade to bionic, printing fails without explanation / logs / debuggability Status in cups-filters package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Triaged Status in cups-filters source package in Bionic: Invalid Status in gtk+3.0 source package in Bionic: New Status in cups-filters source package in Cosmic: Invalid Status in gtk+3.0 source package in Cosmic: New Bug description: I am unable to print to my network-attached printer after upgrade to bionic. ps shows: lp 26047 0.0 0.0 91668 5756 ?S15:06 0:00 \_ HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 lp 26050 0.1 0.0 0 0 ?Z15:06 0:00 | \_ [gs] lp 26048 0.0 0.0 79908 3836 ?S15:06 0:00 \_ HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 root 26049 0.0 0.0 84388 6192 ?S15:06 0:00 \_ ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 Note the un-reaped gs process. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 12 15:07:49 2018 InstallationDate: Installed on 2010-09-24 (2757 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) MachineType: LENOVO 2306CTO Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-03-21 (21 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO modified.conffile..etc.cups.cupsd.conf: [inaccessible: [Errno 13] Permission denied: '/etc/cups/cupsd.conf'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1763520/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability
I have now added debdiffs for disco and for the SRUs. Please can someone with appropriate rights upload them? Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1763520 Title: after upgrade to bionic, printing fails without explanation / logs / debuggability Status in cups-filters package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Triaged Status in cups-filters source package in Bionic: Invalid Status in gtk+3.0 source package in Bionic: New Status in cups-filters source package in Cosmic: Invalid Status in gtk+3.0 source package in Cosmic: New Bug description: I am unable to print to my network-attached printer after upgrade to bionic. ps shows: lp 26047 0.0 0.0 91668 5756 ?S15:06 0:00 \_ HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 lp 26050 0.1 0.0 0 0 ?Z15:06 0:00 | \_ [gs] lp 26048 0.0 0.0 79908 3836 ?S15:06 0:00 \_ HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 root 26049 0.0 0.0 84388 6192 ?S15:06 0:00 \_ ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 Note the un-reaped gs process. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 12 15:07:49 2018 InstallationDate: Installed on 2010-09-24 (2757 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) MachineType: LENOVO 2306CTO Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-03-21 (21 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO modified.conffile..etc.cups.cupsd.conf: [inaccessible: [Errno 13] Permission denied: '/etc/cups/cupsd.conf'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1763520/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability
debdiff for cosmic. ** Patch added: "gtk+3.0_3.24.1-1ubuntu2_3.24.1-1ubuntu2.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1763520/+attachment/5220193/+files/gtk+3.0_3.24.1-1ubuntu2_3.24.1-1ubuntu2.1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1763520 Title: after upgrade to bionic, printing fails without explanation / logs / debuggability Status in cups-filters package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Triaged Status in cups-filters source package in Bionic: Invalid Status in gtk+3.0 source package in Bionic: New Status in cups-filters source package in Cosmic: Invalid Status in gtk+3.0 source package in Cosmic: New Bug description: I am unable to print to my network-attached printer after upgrade to bionic. ps shows: lp 26047 0.0 0.0 91668 5756 ?S15:06 0:00 \_ HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 lp 26050 0.1 0.0 0 0 ?Z15:06 0:00 | \_ [gs] lp 26048 0.0 0.0 79908 3836 ?S15:06 0:00 \_ HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 root 26049 0.0 0.0 84388 6192 ?S15:06 0:00 \_ ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 Note the un-reaped gs process. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 12 15:07:49 2018 InstallationDate: Installed on 2010-09-24 (2757 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) MachineType: LENOVO 2306CTO Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-03-21 (21 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO modified.conffile..etc.cups.cupsd.conf: [inaccessible: [Errno 13] Permission denied: '/etc/cups/cupsd.conf'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1763520/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability
debdiff for disco. ** Patch added: "gtk+3.0_3.24.1-1ubuntu2_3.24.1-1ubuntu3.debdiff" https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1763520/+attachment/5220192/+files/gtk+3.0_3.24.1-1ubuntu2_3.24.1-1ubuntu3.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1763520 Title: after upgrade to bionic, printing fails without explanation / logs / debuggability Status in cups-filters package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Triaged Status in cups-filters source package in Bionic: Invalid Status in gtk+3.0 source package in Bionic: New Status in cups-filters source package in Cosmic: Invalid Status in gtk+3.0 source package in Cosmic: New Bug description: I am unable to print to my network-attached printer after upgrade to bionic. ps shows: lp 26047 0.0 0.0 91668 5756 ?S15:06 0:00 \_ HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 lp 26050 0.1 0.0 0 0 ?Z15:06 0:00 | \_ [gs] lp 26048 0.0 0.0 79908 3836 ?S15:06 0:00 \_ HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 root 26049 0.0 0.0 84388 6192 ?S15:06 0:00 \_ ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 Note the un-reaped gs process. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 12 15:07:49 2018 InstallationDate: Installed on 2010-09-24 (2757 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) MachineType: LENOVO 2306CTO Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-03-21 (21 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO modified.conffile..etc.cups.cupsd.conf: [inaccessible: [Errno 13] Permission denied: '/etc/cups/cupsd.conf'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1763520/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never
** Changed in: cups Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1804576 Title: MaxJobTime=0 results in jobs being cancelled immediately instead of never Status in CUPS: Fix Released Status in cups package in Ubuntu: In Progress Status in cups source package in Trusty: Invalid Status in cups source package in Xenial: In Progress Status in cups source package in Bionic: In Progress Status in cups source package in Cosmic: In Progress Status in cups source package in Disco: In Progress Status in cups package in Debian: Fix Released Bug description: [Impact] Setting the cupsd option MaxJobTime to 0 should make the server wait indefinitely for the job to be ready for print. Instead, after updating job-cancel-after option with MaxJobTime=0 value it results in immediate cancelling. This leads to problems with using filters that take some time to process - the user needs to set MaxJobTime to a ridiculously high value to ensure the job is not going to get cancelled instead of just disabling the cancelling timeout. [Test Case] 1. Add MaxJobTime 0 option to /etc/cups/cupsd.conf. 2. Setup a filter that takes at least several seconds to process. (please find a sample imagetopdf wrapper introducing 5s delay) 3. Submit a print job matching the filter, e.g. lp -d my-printer someimage.jpg # jpg uses the imagetopdf wrapper Expected result: The job is printed after the 5s delay. Actual result: The job is cancelled. [Regression Potential] The scope of the change is limited to fixing the MaxJobTime handling in scheduler/job.c and scheduler/printers.c. There should be no difference in behavior except for the special value of MaxJobTime=0. [Other Info] Original bug description: When using CUPS filters, these filters can take a few seconds to complete. In this case no documents are allowed to be lost on printing failures, so we used to set "MaxJobTime 0" in cupsd.conf which worked on Ubuntu 14.04. With cups on 18.04, you get the following message in /var/log/cups/error_log whenever the filter takes a little longer: I [12/Nov/2018:14:43:26 +0100] [Job 18] Canceling stuck job after 0 seconds. Then, the job is deleted and lost. "MaxJobTime 0" is documented as "indefinite wait", but apparently cups treats is as "wait almost not at all". This issue appears to have also been filed upstream: https://github.com/apple/cups/issues/5438 Temporary workaround is to set the MaxJobTime to a very large value instead (e.g. 3 years) Trusty is not affected by this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1804576/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)
Verification :: disco-proposed
---
Okay, not strictly required as not yet a Stable Release, but doing anyway.
Successful.
$ wget http://archive.ubuntu.com/ubuntu/dists/disco-proposed/main
/installer-amd64/20101020ubuntu560/images/netboot/ubuntu-
installer/amd64/{linux,initrd.gz}
$ virt-install \
--name disco \
--vcpus 2 \
--memory 512 \
--disk size=4,bus=virtio,format=qcow2 \
--network user,model=virtio \
--graphics none \
--import \
--boot kernel=linux,initrd=initrd.gz,kernel_args='console=ttyS0
ipv6.disable=1 auto=true hostname=ubuntu'
Wait until dialog.
Exit to shell.
~ # cat /etc/default-release
disco
~ # sed -n '/^Package: debian-installer/,/^Version:/p' /var/lib/dpkg/status
Package: debian-installer
Status: install ok installed
Version: netboot-20101020ubuntu560
~ # ls -d /usr/lib/ssl/certs/
/usr/lib/ssl/certs/
~ # wget http://github.com
...
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://github.com/ [following]
--2018-12-07 20:42:20-- https://github.com/
...
Saving to: 'index.html'
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done verification-done-bionic
verification-done-cosmic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1807023
Title:
installer stock images fail to validate any HTTPS certificates (ca-
certificates missing)
Status in debian-installer:
Unknown
Status in ca-certificates package in Ubuntu:
Invalid
Status in debian-installer package in Ubuntu:
Fix Released
Status in ca-certificates source package in Trusty:
In Progress
Status in debian-installer source package in Trusty:
In Progress
Status in ca-certificates source package in Xenial:
In Progress
Status in debian-installer source package in Xenial:
In Progress
Status in ca-certificates source package in Bionic:
Invalid
Status in debian-installer source package in Bionic:
Fix Committed
Status in ca-certificates source package in Cosmic:
Invalid
Status in debian-installer source package in Cosmic:
Fix Committed
Status in ca-certificates source package in Disco:
Invalid
Status in debian-installer source package in Disco:
Fix Released
Status in debian-installer package in Debian:
Fix Released
Bug description:
[Impact]
* The installer stock images fail to validate any HTTPS
certificates because ca-certificates is not available
in the installer environment.
* This causes wget/download errors for preseed files on
HTTPS servers (or HTTP servers that redirect to HTTPS,
which are increasingly common nowadays - e.g., GitHub)
and theoretically any other files that are downloaded
with d-i-utils/fetch-url/wget.
* The fix is to ship ca-certificates-udeb in installer
stock images.
* Debian already ships ca-certificate-udeb in the stock
installer images; the fix is applied since Jan 2017.
(reference: Debian Bug #842040 / d-i commit 2f00c51a [1])
[Test Case]
* In the installer shell:
~ # wget http://github.com # or https://github.com
- FAIL if ca-certificates-udeb is missing:
"ERROR: cannot verify github.com's certificate, <...>'
- PASS if ca-certificates-udeb is available
"Saving to: 'index.html'"
* Test steps with virt-install and netboot images
are provided in the comments, for each release.
[Regression Potential]
* Low. This just adds the ca-certificates files in
/etc/ssl/certs and symlink in /usr/lib/ssl/certs,
so only tools looking for that would be affected.
* Apparently only wget checks for/uses those files,
and the difference in behavior is download errors
no longer occur.
[Notes]
* The ca-certificates-udeb is not currently present
in the Ubuntu 'main' component, but in 'universe',
despite the normal deb being in 'main'.
However, when rebuilding in a PPA it goes into
'main' accordingly, and can be used by default
by debian-installer (otherwise, UDEB_COMPONENTS
has to be modified to include universe/d-i).
* So this fix includes a no-change-rebuild for the
ca-certificates package, in order to publish the
udeb in the archive (at least in PPA for testing).
Hopefully that can be sorted out for this fix
to work out.
* The ca-certificates and debian-installer builds
have been done in a PPA using all architectures,
and testing has been done with the amd64 images.
* This fix is requested for Bionic, Cosmic, Disco
at least.
* The fix for Trusty and Xenial needed a little
bit more work to build/ship the (new) udeb.
(reference: Debian Bug #845456 / ca-certificates commit 3acb3a90 [2])
It would be good to have them too if at all possible.
[1]
https://salsa.debian.org/installer-t
[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)
Verification :: cosmic-proposed
---
Successful.
$ wget
http://archive.ubuntu.com/ubuntu/dists/cosmic-proposed/main/installer-amd64/20101020ubuntu557.1/images/netboot/ubuntu-installer/amd64/{linux,initrd.gz}
$ virt-install \
--name cosmic \
--vcpus 2 \
--memory 512 \
--disk size=4,bus=virtio,format=qcow2 \
--network user,model=virtio \
--graphics none \
--import \
--boot kernel=linux,initrd=initrd.gz,kernel_args='console=ttyS0
ipv6.disable=1 auto=true hostname=ubuntu'
Wait until dialog.
Exit to shell.
~ # cat /etc/default-release
cosmic
~ # sed -n '/^Package: debian-installer/,/^Version:/p' /var/lib/dpkg/status
Package: debian-installer
Status: install ok installed
Version: netboot-20101020ubuntu557.1
~ # ls -d /usr/lib/ssl/certs/
/usr/lib/ssl/certs/
~ # wget http://github.com
...
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://github.com/ [following]
--2018-12-07 20:39:52-- https://github.com/
...
Saving to: 'index.html'
...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1807023
Title:
installer stock images fail to validate any HTTPS certificates (ca-
certificates missing)
Status in debian-installer:
Unknown
Status in ca-certificates package in Ubuntu:
Invalid
Status in debian-installer package in Ubuntu:
Fix Released
Status in ca-certificates source package in Trusty:
In Progress
Status in debian-installer source package in Trusty:
In Progress
Status in ca-certificates source package in Xenial:
In Progress
Status in debian-installer source package in Xenial:
In Progress
Status in ca-certificates source package in Bionic:
Invalid
Status in debian-installer source package in Bionic:
Fix Committed
Status in ca-certificates source package in Cosmic:
Invalid
Status in debian-installer source package in Cosmic:
Fix Committed
Status in ca-certificates source package in Disco:
Invalid
Status in debian-installer source package in Disco:
Fix Released
Status in debian-installer package in Debian:
Fix Released
Bug description:
[Impact]
* The installer stock images fail to validate any HTTPS
certificates because ca-certificates is not available
in the installer environment.
* This causes wget/download errors for preseed files on
HTTPS servers (or HTTP servers that redirect to HTTPS,
which are increasingly common nowadays - e.g., GitHub)
and theoretically any other files that are downloaded
with d-i-utils/fetch-url/wget.
* The fix is to ship ca-certificates-udeb in installer
stock images.
* Debian already ships ca-certificate-udeb in the stock
installer images; the fix is applied since Jan 2017.
(reference: Debian Bug #842040 / d-i commit 2f00c51a [1])
[Test Case]
* In the installer shell:
~ # wget http://github.com # or https://github.com
- FAIL if ca-certificates-udeb is missing:
"ERROR: cannot verify github.com's certificate, <...>'
- PASS if ca-certificates-udeb is available
"Saving to: 'index.html'"
* Test steps with virt-install and netboot images
are provided in the comments, for each release.
[Regression Potential]
* Low. This just adds the ca-certificates files in
/etc/ssl/certs and symlink in /usr/lib/ssl/certs,
so only tools looking for that would be affected.
* Apparently only wget checks for/uses those files,
and the difference in behavior is download errors
no longer occur.
[Notes]
* The ca-certificates-udeb is not currently present
in the Ubuntu 'main' component, but in 'universe',
despite the normal deb being in 'main'.
However, when rebuilding in a PPA it goes into
'main' accordingly, and can be used by default
by debian-installer (otherwise, UDEB_COMPONENTS
has to be modified to include universe/d-i).
* So this fix includes a no-change-rebuild for the
ca-certificates package, in order to publish the
udeb in the archive (at least in PPA for testing).
Hopefully that can be sorted out for this fix
to work out.
* The ca-certificates and debian-installer builds
have been done in a PPA using all architectures,
and testing has been done with the amd64 images.
* This fix is requested for Bionic, Cosmic, Disco
at least.
* The fix for Trusty and Xenial needed a little
bit more work to build/ship the (new) udeb.
(reference: Debian Bug #845456 / ca-certificates commit 3acb3a90 [2])
It would be good to have them too if at all possible.
[1]
https://salsa.debian.org/installer-team/debian-installer/commit/2f00c51a7ead982ae1cd71bee06c8416890196b6
[2]
https://salsa.debian.org/debian/ca-certificates/commit/3acb3a9042a00307ba35d10052d81cdc206c34a4
[Debugging]
For debugging purposes, one can install strace-ude
[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)
Verification :: bionic-proposed
---
Successful.
$ wget http://archive.ubuntu.com/ubuntu/dists/bionic-proposed/main
/installer-amd64/20101020ubuntu543.4/images/netboot/ubuntu-
installer/amd64/{linux,initrd.gz}
$ virt-install \
--name bionic \
--vcpus 2 \
--memory 512 \
--disk size=4,bus=virtio,format=qcow2 \
--network user,model=virtio \
--graphics none \
--import \
--boot kernel=linux,initrd=initrd.gz,kernel_args='console=ttyS0
ipv6.disable=1 auto=true hostname=ubuntu'
Wait until dialog.
Exit to shell.
~ # cat /etc/default-release
bionic
~ # sed -n '/^Package: debian-installer/,/^Version:/p' /var/lib/dpkg/status
Package: debian-installer
Status: install ok installed
Version: netboot-20101020ubuntu543.4
~ # ls -d /usr/lib/ssl/certs/
/usr/lib/ssl/certs/
~ # wget http://github.com
...
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://github.com/ [following]
--2018-12-07 20:33:24-- https://github.com/
...
Saving to: 'index.html'
...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1807023
Title:
installer stock images fail to validate any HTTPS certificates (ca-
certificates missing)
Status in debian-installer:
Unknown
Status in ca-certificates package in Ubuntu:
Invalid
Status in debian-installer package in Ubuntu:
Fix Released
Status in ca-certificates source package in Trusty:
In Progress
Status in debian-installer source package in Trusty:
In Progress
Status in ca-certificates source package in Xenial:
In Progress
Status in debian-installer source package in Xenial:
In Progress
Status in ca-certificates source package in Bionic:
Invalid
Status in debian-installer source package in Bionic:
Fix Committed
Status in ca-certificates source package in Cosmic:
Invalid
Status in debian-installer source package in Cosmic:
Fix Committed
Status in ca-certificates source package in Disco:
Invalid
Status in debian-installer source package in Disco:
Fix Released
Status in debian-installer package in Debian:
Fix Released
Bug description:
[Impact]
* The installer stock images fail to validate any HTTPS
certificates because ca-certificates is not available
in the installer environment.
* This causes wget/download errors for preseed files on
HTTPS servers (or HTTP servers that redirect to HTTPS,
which are increasingly common nowadays - e.g., GitHub)
and theoretically any other files that are downloaded
with d-i-utils/fetch-url/wget.
* The fix is to ship ca-certificates-udeb in installer
stock images.
* Debian already ships ca-certificate-udeb in the stock
installer images; the fix is applied since Jan 2017.
(reference: Debian Bug #842040 / d-i commit 2f00c51a [1])
[Test Case]
* In the installer shell:
~ # wget http://github.com # or https://github.com
- FAIL if ca-certificates-udeb is missing:
"ERROR: cannot verify github.com's certificate, <...>'
- PASS if ca-certificates-udeb is available
"Saving to: 'index.html'"
* Test steps with virt-install and netboot images
are provided in the comments, for each release.
[Regression Potential]
* Low. This just adds the ca-certificates files in
/etc/ssl/certs and symlink in /usr/lib/ssl/certs,
so only tools looking for that would be affected.
* Apparently only wget checks for/uses those files,
and the difference in behavior is download errors
no longer occur.
[Notes]
* The ca-certificates-udeb is not currently present
in the Ubuntu 'main' component, but in 'universe',
despite the normal deb being in 'main'.
However, when rebuilding in a PPA it goes into
'main' accordingly, and can be used by default
by debian-installer (otherwise, UDEB_COMPONENTS
has to be modified to include universe/d-i).
* So this fix includes a no-change-rebuild for the
ca-certificates package, in order to publish the
udeb in the archive (at least in PPA for testing).
Hopefully that can be sorted out for this fix
to work out.
* The ca-certificates and debian-installer builds
have been done in a PPA using all architectures,
and testing has been done with the amd64 images.
* This fix is requested for Bionic, Cosmic, Disco
at least.
* The fix for Trusty and Xenial needed a little
bit more work to build/ship the (new) udeb.
(reference: Debian Bug #845456 / ca-certificates commit 3acb3a90 [2])
It would be good to have them too if at all possible.
[1]
https://salsa.debian.org/installer-team/debian-installer/commit/2f00c51a7ead982ae1cd71bee06c8416890196b6
[2]
https://salsa.debian.org/debian/ca-certificates/commit/3acb3a9042a00307ba35d10052d81cdc206c34a4
[Debugging]
For debugging purposes, one can install strace-udeb
[Touch-packages] [Bug 1561278] Re: internal sound card not detected HP X2
Got the commands to run without error, but even after a reset, no sound. -- 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/1561278 Title: internal sound card not detected HP X2 Status in alsa-driver package in Ubuntu: Confirmed Bug description: HP Pavilion X2 - No sound card detected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Wed Mar 23 18:18:32 2016 InstallationDate: Installed on 2016-03-18 (5 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 813E dmi.board.vendor: HP dmi.board.version: 34.10 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.04:bd09/11/2015:svnHP:pnHPPavilionx2Detachable:pvrType1ProductConfigId:rvnHP:rn813E:rvr34.10:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion x2 Detachable dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1561278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)
This bug was fixed in the package debian-installer - 20101020ubuntu560
---
debian-installer (20101020ubuntu560) disco; urgency=medium
[ Mauricio Faria de Oliveira ]
* build/pkg-lists/base: add ca-certificates-udeb to enable HTTPS
without d-i/allow_unauthenticated_ssl in stock initramfs image
as in Debian. (LP: #1807023) (closes: #842040)
-- Dan Streetman Mon, 26 Nov 2018 16:49:46
-0200
** Changed in: debian-installer (Ubuntu Disco)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1807023
Title:
installer stock images fail to validate any HTTPS certificates (ca-
certificates missing)
Status in debian-installer:
Unknown
Status in ca-certificates package in Ubuntu:
Invalid
Status in debian-installer package in Ubuntu:
Fix Released
Status in ca-certificates source package in Trusty:
In Progress
Status in debian-installer source package in Trusty:
In Progress
Status in ca-certificates source package in Xenial:
In Progress
Status in debian-installer source package in Xenial:
In Progress
Status in ca-certificates source package in Bionic:
Invalid
Status in debian-installer source package in Bionic:
Fix Committed
Status in ca-certificates source package in Cosmic:
Invalid
Status in debian-installer source package in Cosmic:
Fix Committed
Status in ca-certificates source package in Disco:
Invalid
Status in debian-installer source package in Disco:
Fix Released
Status in debian-installer package in Debian:
Fix Released
Bug description:
[Impact]
* The installer stock images fail to validate any HTTPS
certificates because ca-certificates is not available
in the installer environment.
* This causes wget/download errors for preseed files on
HTTPS servers (or HTTP servers that redirect to HTTPS,
which are increasingly common nowadays - e.g., GitHub)
and theoretically any other files that are downloaded
with d-i-utils/fetch-url/wget.
* The fix is to ship ca-certificates-udeb in installer
stock images.
* Debian already ships ca-certificate-udeb in the stock
installer images; the fix is applied since Jan 2017.
(reference: Debian Bug #842040 / d-i commit 2f00c51a [1])
[Test Case]
* In the installer shell:
~ # wget http://github.com # or https://github.com
- FAIL if ca-certificates-udeb is missing:
"ERROR: cannot verify github.com's certificate, <...>'
- PASS if ca-certificates-udeb is available
"Saving to: 'index.html'"
* Test steps with virt-install and netboot images
are provided in the comments, for each release.
[Regression Potential]
* Low. This just adds the ca-certificates files in
/etc/ssl/certs and symlink in /usr/lib/ssl/certs,
so only tools looking for that would be affected.
* Apparently only wget checks for/uses those files,
and the difference in behavior is download errors
no longer occur.
[Notes]
* The ca-certificates-udeb is not currently present
in the Ubuntu 'main' component, but in 'universe',
despite the normal deb being in 'main'.
However, when rebuilding in a PPA it goes into
'main' accordingly, and can be used by default
by debian-installer (otherwise, UDEB_COMPONENTS
has to be modified to include universe/d-i).
* So this fix includes a no-change-rebuild for the
ca-certificates package, in order to publish the
udeb in the archive (at least in PPA for testing).
Hopefully that can be sorted out for this fix
to work out.
* The ca-certificates and debian-installer builds
have been done in a PPA using all architectures,
and testing has been done with the amd64 images.
* This fix is requested for Bionic, Cosmic, Disco
at least.
* The fix for Trusty and Xenial needed a little
bit more work to build/ship the (new) udeb.
(reference: Debian Bug #845456 / ca-certificates commit 3acb3a90 [2])
It would be good to have them too if at all possible.
[1]
https://salsa.debian.org/installer-team/debian-installer/commit/2f00c51a7ead982ae1cd71bee06c8416890196b6
[2]
https://salsa.debian.org/debian/ca-certificates/commit/3acb3a9042a00307ba35d10052d81cdc206c34a4
[Debugging]
For debugging purposes, one can install strace-udeb in the installer
to verify wget's stat() calls to /usr/lib/ssl/certs.
~ # anna-install strace-udeb
~ # strace -e stat wget -O- https://github.com >/dev/null
...
Resolving github.com... stat("/etc/resolv.conf", {st_mode=S_IFREG|0644,
st_size=20, ...}) = 0
140.82.118.3, 140.82.118.4
Connecting to github.com|140.82.118.3|:443... connected.
stat("/usr/lib/ssl/certs/45bfefc3.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 EN
[Touch-packages] [Bug 1807448] [NEW] [SRU] Patch power9-001.diff breaks IFUNC on ELFv1
Public bug reported: [ SRU Justification ] As per comment #4 in https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1655181 the undefined weak fix should not have been backported because it breaks IFUNC on ELFv1, and can't be fixed without a much larger backport from 2.27. This patch breaks glibc builds on PPC64 ELFv1. See also https://sourceware.org/bugzilla/show_bug.cgi?id=20472 I will be pushing this upload via the ubuntu-security-proposed PPA, as this regression also exists in security and if we ever want to do a glibc security update, we need the fix there as well. [ Test Case ] See that glibc now builds on powerpc in xenial, when it didn't with the previous version. [ Regression Potential ] We lived fine without this patch before, and will do again in the future. Removing it fixes ELFv1 glibc builds (and presumably anything else that uses IFUNC), but should have no other obvious impact. ** Affects: binutils (Ubuntu) Importance: Undecided Status: Invalid ** Affects: binutils (Ubuntu Xenial) Importance: Undecided Assignee: Adam Conrad (adconrad) Status: In Progress ** Also affects: binutils (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: binutils (Ubuntu) Status: New => Invalid ** Changed in: binutils (Ubuntu Xenial) Assignee: (unassigned) => Adam Conrad (adconrad) ** Changed in: binutils (Ubuntu Xenial) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1807448 Title: [SRU] Patch power9-001.diff breaks IFUNC on ELFv1 Status in binutils package in Ubuntu: Invalid Status in binutils source package in Xenial: In Progress Bug description: [ SRU Justification ] As per comment #4 in https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1655181 the undefined weak fix should not have been backported because it breaks IFUNC on ELFv1, and can't be fixed without a much larger backport from 2.27. This patch breaks glibc builds on PPC64 ELFv1. See also https://sourceware.org/bugzilla/show_bug.cgi?id=20472 I will be pushing this upload via the ubuntu-security-proposed PPA, as this regression also exists in security and if we ever want to do a glibc security update, we need the fix there as well. [ Test Case ] See that glibc now builds on powerpc in xenial, when it didn't with the previous version. [ Regression Potential ] We lived fine without this patch before, and will do again in the future. Removing it fixes ELFv1 glibc builds (and presumably anything else that uses IFUNC), but should have no other obvious impact. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1807448/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 19353] Re: Tools relying on /etc/debian_version get confused
** Tags added: disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/19353 Title: Tools relying on /etc/debian_version get confused Status in base-files package in Ubuntu: Confirmed Bug description: /etc/debian_version appears to be carried unmodified from Debian on Ubuntu systems. This means that things like reportbug that use the information there to identify the version of Debian that they are running on will identify Unbuntu systems as a Debian version. Another approach would be to modify all the tools like reportbug to add their own information or read /etc/ubuntu_version and prefer that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/19353/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)
Hello Mauricio, or anyone else affected, Accepted debian-installer into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/debian- installer/20101020ubuntu543.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: debian-installer (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic ** Changed in: debian-installer (Ubuntu Disco) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1807023 Title: installer stock images fail to validate any HTTPS certificates (ca- certificates missing) Status in debian-installer: Unknown Status in ca-certificates package in Ubuntu: Invalid Status in debian-installer package in Ubuntu: Fix Committed Status in ca-certificates source package in Trusty: In Progress Status in debian-installer source package in Trusty: In Progress Status in ca-certificates source package in Xenial: In Progress Status in debian-installer source package in Xenial: In Progress Status in ca-certificates source package in Bionic: Invalid Status in debian-installer source package in Bionic: Fix Committed Status in ca-certificates source package in Cosmic: Invalid Status in debian-installer source package in Cosmic: Fix Committed Status in ca-certificates source package in Disco: Invalid Status in debian-installer source package in Disco: Fix Committed Status in debian-installer package in Debian: Fix Released Bug description: [Impact] * The installer stock images fail to validate any HTTPS certificates because ca-certificates is not available in the installer environment. * This causes wget/download errors for preseed files on HTTPS servers (or HTTP servers that redirect to HTTPS, which are increasingly common nowadays - e.g., GitHub) and theoretically any other files that are downloaded with d-i-utils/fetch-url/wget. * The fix is to ship ca-certificates-udeb in installer stock images. * Debian already ships ca-certificate-udeb in the stock installer images; the fix is applied since Jan 2017. (reference: Debian Bug #842040 / d-i commit 2f00c51a [1]) [Test Case] * In the installer shell: ~ # wget http://github.com # or https://github.com - FAIL if ca-certificates-udeb is missing: "ERROR: cannot verify github.com's certificate, <...>' - PASS if ca-certificates-udeb is available "Saving to: 'index.html'" * Test steps with virt-install and netboot images are provided in the comments, for each release. [Regression Potential] * Low. This just adds the ca-certificates files in /etc/ssl/certs and symlink in /usr/lib/ssl/certs, so only tools looking for that would be affected. * Apparently only wget checks for/uses those files, and the difference in behavior is download errors no longer occur. [Notes] * The ca-certificates-udeb is not currently present in the Ubuntu 'main' component, but in 'universe', despite the normal deb being in 'main'. However, when rebuilding in a PPA it goes into 'main' accordingly, and can be used by default by debian-installer (otherwise, UDEB_COMPONENTS has to be modified to include universe/d-i). * So this fix includes a no-change-rebuild for the ca-certificates package, in order to publish the udeb in the archive (at least in PPA for testing). Hopefully that can be sorted out for this fix to work out. * The ca-certificates and debian-installer builds have been done in a PPA using all architectures, and testing has been done with the amd64 images. * This fix is requested for Bionic, Cosmic, Disco at least. * The fix for Trusty and Xenial needed a little bit more work to build/shi
[Touch-packages] [Bug 1807262] Re: stein unit tests fail with sqlalchemy.exc.NoSuchTableError: migration_tmp
** Changed in: cinder (Ubuntu) Status: Invalid => Triaged ** Changed in: cinder (Ubuntu) Importance: Undecided => High ** Changed in: nova (Ubuntu) Status: Invalid => Triaged ** Changed in: nova (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/1807262 Title: stein unit tests fail with sqlalchemy.exc.NoSuchTableError: migration_tmp Status in sqlalchemy-migrate: New Status in cinder package in Ubuntu: Triaged Status in migrate package in Ubuntu: Triaged Status in nova package in Ubuntu: Triaged Status in sqlite3 package in Ubuntu: Invalid Bug description: Several tests that use sqlite fail with: "sqlalchemy.exc.NoSuchTableError: migration_tmp". I'm currently hitting this with nova and cinder packages in disco. Note this started sometime after 11/19 when nova 2:19.0.0~b1~git2018111953.3e756ff674-0ubuntu1 was uploaded (and built successfully at the time). After doing some digging this appears to occur with libsqlite3-0 3.26.0-1 but does not occur with libsqlite3-0 3.25.3-1. Here are some more details on that, shown by running a failing unit test from the cinder package: https://paste.ubuntu.com/p/hsnQFQD572/ Update: The test in the paste above also works successfully with libsqlite3-0 3.25.3-2. To manage notifications about this bug go to: https://bugs.launchpad.net/sqlalchemy-migrate/+bug/1807262/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807437] Re: package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status
** Tags removed: need-duplicate-check -- 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/1807437 Title: package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 Status in openssh package in Ubuntu: New Bug description: On startuo I got an error message,three consecutive times now, saying system failed to load package. Weirdly, another message appears saying my software is up to date. When I 'x' it. I'm left with the option of reporting the bug failure, which I'm doing now. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: openssh-server 1:7.6p1-4ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: usbmuxd:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri Dec 7 19:01:57 2018 ErrorMessage: installed openssh-server package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-07-29 (861 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: /etc/ssh/sshd_config line 13: Deprecated option UsePrivilegeSeparation /etc/ssh/sshd_config line 16: Deprecated option KeyRegenerationInterval /etc/ssh/sshd_config line 17: Deprecated option ServerKeyBits /etc/ssh/sshd_config line 30: Bad SSH2 mac spec 'hmac-sha2-512-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-ripemd160-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-512,hmac-sha2-256,hmac-ripemd160,umac-...@openssh.com'. SourcePackage: openssh Title: package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-05-15 (205 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1807437/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)
Hello Mauricio, or anyone else affected, Accepted debian-installer into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/debian- installer/20101020ubuntu557.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: debian-installer (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1807023 Title: installer stock images fail to validate any HTTPS certificates (ca- certificates missing) Status in debian-installer: Unknown Status in ca-certificates package in Ubuntu: Invalid Status in debian-installer package in Ubuntu: Fix Committed Status in ca-certificates source package in Trusty: In Progress Status in debian-installer source package in Trusty: In Progress Status in ca-certificates source package in Xenial: In Progress Status in debian-installer source package in Xenial: In Progress Status in ca-certificates source package in Bionic: Invalid Status in debian-installer source package in Bionic: Fix Committed Status in ca-certificates source package in Cosmic: Invalid Status in debian-installer source package in Cosmic: Fix Committed Status in ca-certificates source package in Disco: Invalid Status in debian-installer source package in Disco: Fix Committed Status in debian-installer package in Debian: Fix Released Bug description: [Impact] * The installer stock images fail to validate any HTTPS certificates because ca-certificates is not available in the installer environment. * This causes wget/download errors for preseed files on HTTPS servers (or HTTP servers that redirect to HTTPS, which are increasingly common nowadays - e.g., GitHub) and theoretically any other files that are downloaded with d-i-utils/fetch-url/wget. * The fix is to ship ca-certificates-udeb in installer stock images. * Debian already ships ca-certificate-udeb in the stock installer images; the fix is applied since Jan 2017. (reference: Debian Bug #842040 / d-i commit 2f00c51a [1]) [Test Case] * In the installer shell: ~ # wget http://github.com # or https://github.com - FAIL if ca-certificates-udeb is missing: "ERROR: cannot verify github.com's certificate, <...>' - PASS if ca-certificates-udeb is available "Saving to: 'index.html'" * Test steps with virt-install and netboot images are provided in the comments, for each release. [Regression Potential] * Low. This just adds the ca-certificates files in /etc/ssl/certs and symlink in /usr/lib/ssl/certs, so only tools looking for that would be affected. * Apparently only wget checks for/uses those files, and the difference in behavior is download errors no longer occur. [Notes] * The ca-certificates-udeb is not currently present in the Ubuntu 'main' component, but in 'universe', despite the normal deb being in 'main'. However, when rebuilding in a PPA it goes into 'main' accordingly, and can be used by default by debian-installer (otherwise, UDEB_COMPONENTS has to be modified to include universe/d-i). * So this fix includes a no-change-rebuild for the ca-certificates package, in order to publish the udeb in the archive (at least in PPA for testing). Hopefully that can be sorted out for this fix to work out. * The ca-certificates and debian-installer builds have been done in a PPA using all architectures, and testing has been done with the amd64 images. * This fix is requested for Bionic, Cosmic, Disco at least. * The fix for Trusty and Xenial needed a little bit more work to build/ship the (new) udeb. (reference: Debian Bug #845456 / ca-certificates
[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)
** Branch linked: lp:~ubuntu-core-dev/debian-installer/bionic-proposed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1807023
Title:
installer stock images fail to validate any HTTPS certificates (ca-
certificates missing)
Status in debian-installer:
Unknown
Status in ca-certificates package in Ubuntu:
Invalid
Status in debian-installer package in Ubuntu:
Fix Committed
Status in ca-certificates source package in Trusty:
In Progress
Status in debian-installer source package in Trusty:
In Progress
Status in ca-certificates source package in Xenial:
In Progress
Status in debian-installer source package in Xenial:
In Progress
Status in ca-certificates source package in Bionic:
Invalid
Status in debian-installer source package in Bionic:
Fix Committed
Status in ca-certificates source package in Cosmic:
Invalid
Status in debian-installer source package in Cosmic:
Fix Committed
Status in ca-certificates source package in Disco:
Invalid
Status in debian-installer source package in Disco:
Fix Committed
Status in debian-installer package in Debian:
Fix Released
Bug description:
[Impact]
* The installer stock images fail to validate any HTTPS
certificates because ca-certificates is not available
in the installer environment.
* This causes wget/download errors for preseed files on
HTTPS servers (or HTTP servers that redirect to HTTPS,
which are increasingly common nowadays - e.g., GitHub)
and theoretically any other files that are downloaded
with d-i-utils/fetch-url/wget.
* The fix is to ship ca-certificates-udeb in installer
stock images.
* Debian already ships ca-certificate-udeb in the stock
installer images; the fix is applied since Jan 2017.
(reference: Debian Bug #842040 / d-i commit 2f00c51a [1])
[Test Case]
* In the installer shell:
~ # wget http://github.com # or https://github.com
- FAIL if ca-certificates-udeb is missing:
"ERROR: cannot verify github.com's certificate, <...>'
- PASS if ca-certificates-udeb is available
"Saving to: 'index.html'"
* Test steps with virt-install and netboot images
are provided in the comments, for each release.
[Regression Potential]
* Low. This just adds the ca-certificates files in
/etc/ssl/certs and symlink in /usr/lib/ssl/certs,
so only tools looking for that would be affected.
* Apparently only wget checks for/uses those files,
and the difference in behavior is download errors
no longer occur.
[Notes]
* The ca-certificates-udeb is not currently present
in the Ubuntu 'main' component, but in 'universe',
despite the normal deb being in 'main'.
However, when rebuilding in a PPA it goes into
'main' accordingly, and can be used by default
by debian-installer (otherwise, UDEB_COMPONENTS
has to be modified to include universe/d-i).
* So this fix includes a no-change-rebuild for the
ca-certificates package, in order to publish the
udeb in the archive (at least in PPA for testing).
Hopefully that can be sorted out for this fix
to work out.
* The ca-certificates and debian-installer builds
have been done in a PPA using all architectures,
and testing has been done with the amd64 images.
* This fix is requested for Bionic, Cosmic, Disco
at least.
* The fix for Trusty and Xenial needed a little
bit more work to build/ship the (new) udeb.
(reference: Debian Bug #845456 / ca-certificates commit 3acb3a90 [2])
It would be good to have them too if at all possible.
[1]
https://salsa.debian.org/installer-team/debian-installer/commit/2f00c51a7ead982ae1cd71bee06c8416890196b6
[2]
https://salsa.debian.org/debian/ca-certificates/commit/3acb3a9042a00307ba35d10052d81cdc206c34a4
[Debugging]
For debugging purposes, one can install strace-udeb in the installer
to verify wget's stat() calls to /usr/lib/ssl/certs.
~ # anna-install strace-udeb
~ # strace -e stat wget -O- https://github.com >/dev/null
...
Resolving github.com... stat("/etc/resolv.conf", {st_mode=S_IFREG|0644,
st_size=20, ...}) = 0
140.82.118.3, 140.82.118.4
Connecting to github.com|140.82.118.3|:443... connected.
stat("/usr/lib/ssl/certs/45bfefc3.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
ERROR: cannot verify github.com's certificate, issued by 'CN=DigiCert SHA2
Extended Validation Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US':
Unable to locally verify the issuer's authority.
To connect to github.com insecurely, use `--no-check-certificate'.
+++ exited with 5 +++
~ #
~ #
[Touch-packages] [Bug 1807262] Re: stein unit tests fail with sqlalchemy.exc.NoSuchTableError: migration_tmp
Upstream PR: https://review.openstack.org/#/c/623564/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/1807262 Title: stein unit tests fail with sqlalchemy.exc.NoSuchTableError: migration_tmp Status in sqlalchemy-migrate: New Status in cinder package in Ubuntu: Invalid Status in migrate package in Ubuntu: Triaged Status in nova package in Ubuntu: Invalid Status in sqlite3 package in Ubuntu: Invalid Bug description: Several tests that use sqlite fail with: "sqlalchemy.exc.NoSuchTableError: migration_tmp". I'm currently hitting this with nova and cinder packages in disco. Note this started sometime after 11/19 when nova 2:19.0.0~b1~git2018111953.3e756ff674-0ubuntu1 was uploaded (and built successfully at the time). After doing some digging this appears to occur with libsqlite3-0 3.26.0-1 but does not occur with libsqlite3-0 3.25.3-1. Here are some more details on that, shown by running a failing unit test from the cinder package: https://paste.ubuntu.com/p/hsnQFQD572/ Update: The test in the paste above also works successfully with libsqlite3-0 3.25.3-2. To manage notifications about this bug go to: https://bugs.launchpad.net/sqlalchemy-migrate/+bug/1807262/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)
** Branch linked: lp:~ubuntu-core-dev/debian-installer/cosmic-proposed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1807023
Title:
installer stock images fail to validate any HTTPS certificates (ca-
certificates missing)
Status in debian-installer:
Unknown
Status in ca-certificates package in Ubuntu:
Invalid
Status in debian-installer package in Ubuntu:
Fix Committed
Status in ca-certificates source package in Trusty:
In Progress
Status in debian-installer source package in Trusty:
In Progress
Status in ca-certificates source package in Xenial:
In Progress
Status in debian-installer source package in Xenial:
In Progress
Status in ca-certificates source package in Bionic:
Invalid
Status in debian-installer source package in Bionic:
Fix Committed
Status in ca-certificates source package in Cosmic:
Invalid
Status in debian-installer source package in Cosmic:
Fix Committed
Status in ca-certificates source package in Disco:
Invalid
Status in debian-installer source package in Disco:
Fix Committed
Status in debian-installer package in Debian:
Fix Released
Bug description:
[Impact]
* The installer stock images fail to validate any HTTPS
certificates because ca-certificates is not available
in the installer environment.
* This causes wget/download errors for preseed files on
HTTPS servers (or HTTP servers that redirect to HTTPS,
which are increasingly common nowadays - e.g., GitHub)
and theoretically any other files that are downloaded
with d-i-utils/fetch-url/wget.
* The fix is to ship ca-certificates-udeb in installer
stock images.
* Debian already ships ca-certificate-udeb in the stock
installer images; the fix is applied since Jan 2017.
(reference: Debian Bug #842040 / d-i commit 2f00c51a [1])
[Test Case]
* In the installer shell:
~ # wget http://github.com # or https://github.com
- FAIL if ca-certificates-udeb is missing:
"ERROR: cannot verify github.com's certificate, <...>'
- PASS if ca-certificates-udeb is available
"Saving to: 'index.html'"
* Test steps with virt-install and netboot images
are provided in the comments, for each release.
[Regression Potential]
* Low. This just adds the ca-certificates files in
/etc/ssl/certs and symlink in /usr/lib/ssl/certs,
so only tools looking for that would be affected.
* Apparently only wget checks for/uses those files,
and the difference in behavior is download errors
no longer occur.
[Notes]
* The ca-certificates-udeb is not currently present
in the Ubuntu 'main' component, but in 'universe',
despite the normal deb being in 'main'.
However, when rebuilding in a PPA it goes into
'main' accordingly, and can be used by default
by debian-installer (otherwise, UDEB_COMPONENTS
has to be modified to include universe/d-i).
* So this fix includes a no-change-rebuild for the
ca-certificates package, in order to publish the
udeb in the archive (at least in PPA for testing).
Hopefully that can be sorted out for this fix
to work out.
* The ca-certificates and debian-installer builds
have been done in a PPA using all architectures,
and testing has been done with the amd64 images.
* This fix is requested for Bionic, Cosmic, Disco
at least.
* The fix for Trusty and Xenial needed a little
bit more work to build/ship the (new) udeb.
(reference: Debian Bug #845456 / ca-certificates commit 3acb3a90 [2])
It would be good to have them too if at all possible.
[1]
https://salsa.debian.org/installer-team/debian-installer/commit/2f00c51a7ead982ae1cd71bee06c8416890196b6
[2]
https://salsa.debian.org/debian/ca-certificates/commit/3acb3a9042a00307ba35d10052d81cdc206c34a4
[Debugging]
For debugging purposes, one can install strace-udeb in the installer
to verify wget's stat() calls to /usr/lib/ssl/certs.
~ # anna-install strace-udeb
~ # strace -e stat wget -O- https://github.com >/dev/null
...
Resolving github.com... stat("/etc/resolv.conf", {st_mode=S_IFREG|0644,
st_size=20, ...}) = 0
140.82.118.3, 140.82.118.4
Connecting to github.com|140.82.118.3|:443... connected.
stat("/usr/lib/ssl/certs/45bfefc3.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
ERROR: cannot verify github.com's certificate, issued by 'CN=DigiCert SHA2
Extended Validation Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US':
Unable to locally verify the issuer's authority.
To connect to github.com insecurely, use `--no-check-certificate'.
+++ exited with 5 +++
~ #
~ #
[Touch-packages] [Bug 1807262] Re: stein unit tests fail with sqlalchemy.exc.NoSuchTableError: migration_tmp
I've moved ahead with an upstream PR and will be uploading to Ubuntu shortly with a patch/bug to Debian. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/1807262 Title: stein unit tests fail with sqlalchemy.exc.NoSuchTableError: migration_tmp Status in sqlalchemy-migrate: New Status in cinder package in Ubuntu: Invalid Status in migrate package in Ubuntu: Triaged Status in nova package in Ubuntu: Invalid Status in sqlite3 package in Ubuntu: Invalid Bug description: Several tests that use sqlite fail with: "sqlalchemy.exc.NoSuchTableError: migration_tmp". I'm currently hitting this with nova and cinder packages in disco. Note this started sometime after 11/19 when nova 2:19.0.0~b1~git2018111953.3e756ff674-0ubuntu1 was uploaded (and built successfully at the time). After doing some digging this appears to occur with libsqlite3-0 3.26.0-1 but does not occur with libsqlite3-0 3.25.3-1. Here are some more details on that, shown by running a failing unit test from the cinder package: https://paste.ubuntu.com/p/hsnQFQD572/ Update: The test in the paste above also works successfully with libsqlite3-0 3.25.3-2. To manage notifications about this bug go to: https://bugs.launchpad.net/sqlalchemy-migrate/+bug/1807262/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807440] [NEW] sensible-browser cannot process $BROWSER variable when it contains a whitespace character
Public bug reported:
If path to a browser defined via the $BROWSER environment variable
contains a whitespace character, running sensible-browser should launch
browser defined by $BROWSER.
If path to a browser defined via the $BROWSER environment variable
contains a whitespace character, running sensible-browser will not parse
the whitespace characters and therefore not load the browser defined by
$BROWSER.
Bug can be fixed by updating line 8 in /usr/bin/sensible-browser:
${BROWSER} "$@" > "${BROWSER}" "$@"
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: sensible-utils 0.0.12
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec 7 11:05:17 2018
Dependencies:
InstallationDate: Installed on 2018-12-06 (1 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: sensible-utils
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: sensible-utils (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic
** Description changed:
- Release: Ubuntu 18.04.1
- Package: sensible-utils 0.0.12
-
If path to a browser defined via the $BROWSER environment variable
contains a whitespace character, running sensible-browser should launch
browser defined by $BROWSER.
If path to a browser defined via the $BROWSER environment variable
contains a whitespace character, running sensible-browser will not parse
the whitespace characters and therefore not load the browser defined by
$BROWSER.
Bug can be fixed by updating line 8 in /usr/bin/sensible-browser:
${BROWSER} "$@" > "${BROWSER}" "$@"
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: sensible-utils 0.0.12
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec 7 11:05:17 2018
Dependencies:
-
+
InstallationDate: Installed on 2018-12-06 (1 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
PackageArchitecture: all
ProcEnviron:
- PATH=(custom, no user)
- XDG_RUNTIME_DIR=
- LANG=en_US.UTF-8
- SHELL=/bin/bash
+ PATH=(custom, no user)
+ XDG_RUNTIME_DIR=
+ LANG=en_US.UTF-8
+ SHELL=/bin/bash
SourcePackage: sensible-utils
UpgradeStatus: No upgrade log present (probably fresh install)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sensible-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1807440
Title:
sensible-browser cannot process $BROWSER variable when it contains a
whitespace character
Status in sensible-utils package in Ubuntu:
New
Bug description:
If path to a browser defined via the $BROWSER environment variable
contains a whitespace character, running sensible-browser should
launch browser defined by $BROWSER.
If path to a browser defined via the $BROWSER environment variable
contains a whitespace character, running sensible-browser will not
parse the whitespace characters and therefore not load the browser
defined by $BROWSER.
Bug can be fixed by updating line 8 in /usr/bin/sensible-browser:
${BROWSER} "$@" > "${BROWSER}" "$@"
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: sensible-utils 0.0.12
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec 7 11:05:17 2018
Dependencies:
InstallationDate: Installed on 2018-12-06 (1 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
PackageArchitecture: all
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: sensible-utils
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sensible-utils/+bug/1807440/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)
** Patch added: "lp1807023-ca-certificates-xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1807023/+attachment/5220173/+files/lp1807023-ca-certificates-xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1807023
Title:
installer stock images fail to validate any HTTPS certificates (ca-
certificates missing)
Status in debian-installer:
Unknown
Status in ca-certificates package in Ubuntu:
Invalid
Status in debian-installer package in Ubuntu:
In Progress
Status in ca-certificates source package in Trusty:
In Progress
Status in debian-installer source package in Trusty:
In Progress
Status in ca-certificates source package in Xenial:
In Progress
Status in debian-installer source package in Xenial:
In Progress
Status in ca-certificates source package in Bionic:
Invalid
Status in debian-installer source package in Bionic:
In Progress
Status in ca-certificates source package in Cosmic:
Invalid
Status in debian-installer source package in Cosmic:
In Progress
Status in ca-certificates source package in Disco:
Invalid
Status in debian-installer source package in Disco:
In Progress
Status in debian-installer package in Debian:
Fix Released
Bug description:
[Impact]
* The installer stock images fail to validate any HTTPS
certificates because ca-certificates is not available
in the installer environment.
* This causes wget/download errors for preseed files on
HTTPS servers (or HTTP servers that redirect to HTTPS,
which are increasingly common nowadays - e.g., GitHub)
and theoretically any other files that are downloaded
with d-i-utils/fetch-url/wget.
* The fix is to ship ca-certificates-udeb in installer
stock images.
* Debian already ships ca-certificate-udeb in the stock
installer images; the fix is applied since Jan 2017.
(reference: Debian Bug #842040 / d-i commit 2f00c51a [1])
[Test Case]
* In the installer shell:
~ # wget http://github.com # or https://github.com
- FAIL if ca-certificates-udeb is missing:
"ERROR: cannot verify github.com's certificate, <...>'
- PASS if ca-certificates-udeb is available
"Saving to: 'index.html'"
* Test steps with virt-install and netboot images
are provided in the comments, for each release.
[Regression Potential]
* Low. This just adds the ca-certificates files in
/etc/ssl/certs and symlink in /usr/lib/ssl/certs,
so only tools looking for that would be affected.
* Apparently only wget checks for/uses those files,
and the difference in behavior is download errors
no longer occur.
[Notes]
* The ca-certificates-udeb is not currently present
in the Ubuntu 'main' component, but in 'universe',
despite the normal deb being in 'main'.
However, when rebuilding in a PPA it goes into
'main' accordingly, and can be used by default
by debian-installer (otherwise, UDEB_COMPONENTS
has to be modified to include universe/d-i).
* So this fix includes a no-change-rebuild for the
ca-certificates package, in order to publish the
udeb in the archive (at least in PPA for testing).
Hopefully that can be sorted out for this fix
to work out.
* The ca-certificates and debian-installer builds
have been done in a PPA using all architectures,
and testing has been done with the amd64 images.
* This fix is requested for Bionic, Cosmic, Disco
at least.
* The fix for Trusty and Xenial needed a little
bit more work to build/ship the (new) udeb.
(reference: Debian Bug #845456 / ca-certificates commit 3acb3a90 [2])
It would be good to have them too if at all possible.
[1]
https://salsa.debian.org/installer-team/debian-installer/commit/2f00c51a7ead982ae1cd71bee06c8416890196b6
[2]
https://salsa.debian.org/debian/ca-certificates/commit/3acb3a9042a00307ba35d10052d81cdc206c34a4
[Debugging]
For debugging purposes, one can install strace-udeb in the installer
to verify wget's stat() calls to /usr/lib/ssl/certs.
~ # anna-install strace-udeb
~ # strace -e stat wget -O- https://github.com >/dev/null
...
Resolving github.com... stat("/etc/resolv.conf", {st_mode=S_IFREG|0644,
st_size=20, ...}) = 0
140.82.118.3, 140.82.118.4
Connecting to github.com|140.82.118.3|:443... connected.
stat("/usr/lib/ssl/certs/45bfefc3.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
ERROR: cannot verify github.com's certificate, issued by 'CN=DigiCert SHA2
Extended Validation Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US':
Unable to locally verify the i
[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)
** Patch added: "lp1807023-ca-certificates-trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1807023/+attachment/5220172/+files/lp1807023-ca-certificates-trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1807023
Title:
installer stock images fail to validate any HTTPS certificates (ca-
certificates missing)
Status in debian-installer:
Unknown
Status in ca-certificates package in Ubuntu:
Invalid
Status in debian-installer package in Ubuntu:
In Progress
Status in ca-certificates source package in Trusty:
In Progress
Status in debian-installer source package in Trusty:
In Progress
Status in ca-certificates source package in Xenial:
In Progress
Status in debian-installer source package in Xenial:
In Progress
Status in ca-certificates source package in Bionic:
Invalid
Status in debian-installer source package in Bionic:
In Progress
Status in ca-certificates source package in Cosmic:
Invalid
Status in debian-installer source package in Cosmic:
In Progress
Status in ca-certificates source package in Disco:
Invalid
Status in debian-installer source package in Disco:
In Progress
Status in debian-installer package in Debian:
Fix Released
Bug description:
[Impact]
* The installer stock images fail to validate any HTTPS
certificates because ca-certificates is not available
in the installer environment.
* This causes wget/download errors for preseed files on
HTTPS servers (or HTTP servers that redirect to HTTPS,
which are increasingly common nowadays - e.g., GitHub)
and theoretically any other files that are downloaded
with d-i-utils/fetch-url/wget.
* The fix is to ship ca-certificates-udeb in installer
stock images.
* Debian already ships ca-certificate-udeb in the stock
installer images; the fix is applied since Jan 2017.
(reference: Debian Bug #842040 / d-i commit 2f00c51a [1])
[Test Case]
* In the installer shell:
~ # wget http://github.com # or https://github.com
- FAIL if ca-certificates-udeb is missing:
"ERROR: cannot verify github.com's certificate, <...>'
- PASS if ca-certificates-udeb is available
"Saving to: 'index.html'"
* Test steps with virt-install and netboot images
are provided in the comments, for each release.
[Regression Potential]
* Low. This just adds the ca-certificates files in
/etc/ssl/certs and symlink in /usr/lib/ssl/certs,
so only tools looking for that would be affected.
* Apparently only wget checks for/uses those files,
and the difference in behavior is download errors
no longer occur.
[Notes]
* The ca-certificates-udeb is not currently present
in the Ubuntu 'main' component, but in 'universe',
despite the normal deb being in 'main'.
However, when rebuilding in a PPA it goes into
'main' accordingly, and can be used by default
by debian-installer (otherwise, UDEB_COMPONENTS
has to be modified to include universe/d-i).
* So this fix includes a no-change-rebuild for the
ca-certificates package, in order to publish the
udeb in the archive (at least in PPA for testing).
Hopefully that can be sorted out for this fix
to work out.
* The ca-certificates and debian-installer builds
have been done in a PPA using all architectures,
and testing has been done with the amd64 images.
* This fix is requested for Bionic, Cosmic, Disco
at least.
* The fix for Trusty and Xenial needed a little
bit more work to build/ship the (new) udeb.
(reference: Debian Bug #845456 / ca-certificates commit 3acb3a90 [2])
It would be good to have them too if at all possible.
[1]
https://salsa.debian.org/installer-team/debian-installer/commit/2f00c51a7ead982ae1cd71bee06c8416890196b6
[2]
https://salsa.debian.org/debian/ca-certificates/commit/3acb3a9042a00307ba35d10052d81cdc206c34a4
[Debugging]
For debugging purposes, one can install strace-udeb in the installer
to verify wget's stat() calls to /usr/lib/ssl/certs.
~ # anna-install strace-udeb
~ # strace -e stat wget -O- https://github.com >/dev/null
...
Resolving github.com... stat("/etc/resolv.conf", {st_mode=S_IFREG|0644,
st_size=20, ...}) = 0
140.82.118.3, 140.82.118.4
Connecting to github.com|140.82.118.3|:443... connected.
stat("/usr/lib/ssl/certs/45bfefc3.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
ERROR: cannot verify github.com's certificate, issued by 'CN=DigiCert SHA2
Extended Validation Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US':
Unable to locally verify the i
[Touch-packages] [Bug 1807437] [NEW] package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit statu
Public bug reported: On startuo I got an error message,three consecutive times now, saying system failed to load package. Weirdly, another message appears saying my software is up to date. When I 'x' it. I'm left with the option of reporting the bug failure, which I'm doing now. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: openssh-server 1:7.6p1-4ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: usbmuxd:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri Dec 7 19:01:57 2018 ErrorMessage: installed openssh-server package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-07-29 (861 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: /etc/ssh/sshd_config line 13: Deprecated option UsePrivilegeSeparation /etc/ssh/sshd_config line 16: Deprecated option KeyRegenerationInterval /etc/ssh/sshd_config line 17: Deprecated option ServerKeyBits /etc/ssh/sshd_config line 30: Bad SSH2 mac spec 'hmac-sha2-512-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-ripemd160-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-512,hmac-sha2-256,hmac-ripemd160,umac-...@openssh.com'. SourcePackage: openssh Title: package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-05-15 (205 days ago) ** Affects: openssh (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 openssh in Ubuntu. https://bugs.launchpad.net/bugs/1807437 Title: package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 Status in openssh package in Ubuntu: New Bug description: On startuo I got an error message,three consecutive times now, saying system failed to load package. Weirdly, another message appears saying my software is up to date. When I 'x' it. I'm left with the option of reporting the bug failure, which I'm doing now. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: openssh-server 1:7.6p1-4ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: usbmuxd:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri Dec 7 19:01:57 2018 ErrorMessage: installed openssh-server package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-07-29 (861 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: /etc/ssh/sshd_config line 13: Deprecated option UsePrivilegeSeparation /etc/ssh/sshd_config line 16: Deprecated option KeyRegenerationInterval /etc/ssh/sshd_config line 17: Deprecated option ServerKeyBits /etc/ssh/sshd_config line 30: Bad SSH2 mac spec 'hmac-sha2-512-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-ripemd160-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-512,hmac-sha2-256,hmac-ripemd160,umac-...@openssh.com'. SourcePackage: openssh Title: package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-05-15 (205 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1807437/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)
** Patch removed: "lp1807023-ca-certificates-xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1807023/+attachment/5220101/+files/lp1807023-ca-certificates-xenial.debdiff
** Patch removed: "lp1807023-ca-certificates-trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1807023/+attachment/5220103/+files/lp1807023-ca-certificates-trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1807023
Title:
installer stock images fail to validate any HTTPS certificates (ca-
certificates missing)
Status in debian-installer:
Unknown
Status in ca-certificates package in Ubuntu:
Invalid
Status in debian-installer package in Ubuntu:
In Progress
Status in ca-certificates source package in Trusty:
In Progress
Status in debian-installer source package in Trusty:
In Progress
Status in ca-certificates source package in Xenial:
In Progress
Status in debian-installer source package in Xenial:
In Progress
Status in ca-certificates source package in Bionic:
Invalid
Status in debian-installer source package in Bionic:
In Progress
Status in ca-certificates source package in Cosmic:
Invalid
Status in debian-installer source package in Cosmic:
In Progress
Status in ca-certificates source package in Disco:
Invalid
Status in debian-installer source package in Disco:
In Progress
Status in debian-installer package in Debian:
Fix Released
Bug description:
[Impact]
* The installer stock images fail to validate any HTTPS
certificates because ca-certificates is not available
in the installer environment.
* This causes wget/download errors for preseed files on
HTTPS servers (or HTTP servers that redirect to HTTPS,
which are increasingly common nowadays - e.g., GitHub)
and theoretically any other files that are downloaded
with d-i-utils/fetch-url/wget.
* The fix is to ship ca-certificates-udeb in installer
stock images.
* Debian already ships ca-certificate-udeb in the stock
installer images; the fix is applied since Jan 2017.
(reference: Debian Bug #842040 / d-i commit 2f00c51a [1])
[Test Case]
* In the installer shell:
~ # wget http://github.com # or https://github.com
- FAIL if ca-certificates-udeb is missing:
"ERROR: cannot verify github.com's certificate, <...>'
- PASS if ca-certificates-udeb is available
"Saving to: 'index.html'"
* Test steps with virt-install and netboot images
are provided in the comments, for each release.
[Regression Potential]
* Low. This just adds the ca-certificates files in
/etc/ssl/certs and symlink in /usr/lib/ssl/certs,
so only tools looking for that would be affected.
* Apparently only wget checks for/uses those files,
and the difference in behavior is download errors
no longer occur.
[Notes]
* The ca-certificates-udeb is not currently present
in the Ubuntu 'main' component, but in 'universe',
despite the normal deb being in 'main'.
However, when rebuilding in a PPA it goes into
'main' accordingly, and can be used by default
by debian-installer (otherwise, UDEB_COMPONENTS
has to be modified to include universe/d-i).
* So this fix includes a no-change-rebuild for the
ca-certificates package, in order to publish the
udeb in the archive (at least in PPA for testing).
Hopefully that can be sorted out for this fix
to work out.
* The ca-certificates and debian-installer builds
have been done in a PPA using all architectures,
and testing has been done with the amd64 images.
* This fix is requested for Bionic, Cosmic, Disco
at least.
* The fix for Trusty and Xenial needed a little
bit more work to build/ship the (new) udeb.
(reference: Debian Bug #845456 / ca-certificates commit 3acb3a90 [2])
It would be good to have them too if at all possible.
[1]
https://salsa.debian.org/installer-team/debian-installer/commit/2f00c51a7ead982ae1cd71bee06c8416890196b6
[2]
https://salsa.debian.org/debian/ca-certificates/commit/3acb3a9042a00307ba35d10052d81cdc206c34a4
[Debugging]
For debugging purposes, one can install strace-udeb in the installer
to verify wget's stat() calls to /usr/lib/ssl/certs.
~ # anna-install strace-udeb
~ # strace -e stat wget -O- https://github.com >/dev/null
...
Resolving github.com... stat("/etc/resolv.conf", {st_mode=S_IFREG|0644,
st_size=20, ...}) = 0
140.82.118.3, 140.82.118.4
Connecting to github.com|140.82.118.3|:443... connected.
stat("/usr/lib/ssl/certs/45bfefc3.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No s
[Touch-packages] [Bug 1807432] [NEW] /proc/diskstats does not rollup queue depth from partitions
Public bug reported: Tested in Ubuntu 18.04LTS and Ubuntu 18.10, with the same result. The queue size rollup works in Centos 7 though. root@vagrant:~# uname -a Linux vagrant 4.18.0-12-generic #13-Ubuntu SMP Wed Nov 14 15:17:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@vagrant:~# lsb_release -rd Description:Ubuntu 18.10 Release:18.10 root@vagrant:~# cat /proc/diskstats 7 0 loop0 5 0 16 0 0 0 0 0 0 0 0 7 1 loop1 0 0 0 0 0 0 0 0 0 0 0 7 2 loop2 0 0 0 0 0 0 0 0 0 0 0 7 3 loop3 0 0 0 0 0 0 0 0 0 0 0 7 4 loop4 0 0 0 0 0 0 0 0 0 0 0 7 5 loop5 0 0 0 0 0 0 0 0 0 0 0 7 6 loop6 0 0 0 0 0 0 0 0 0 0 0 7 7 loop7 0 0 0 0 0 0 0 0 0 0 0 259 0 nvme0n1 813340 0 10963704 274028 4075 44 1040576 46884 0 18012 908472 259 5 nvme0n1p1 203838 0 2749463 65696 986 0 252416 11696 13 14360 218028 259 6 nvme0n1p2 202672 0 2713358 67924 1015 0 259840 11696 20 14372 220388 259 7 nvme0n1p3 202961 0 2717301 70464 1034 0 264704 11652 19 14344 226248 259 8 nvme0n1p4 203216 0 2730974 69944 1028 0 263168 11840 16 14340 224992 8 0 sda 11622 783 612090 16416 6529 9730 607624 52912 0 7964 76940 8 1 sda1 11543 783 607954 16408 4731 9730 607624 52844 0 7380 76304 253 0 dm-0 12083 0 598666 25540 16198 0 613808 137252 0 7936 162808 253 1 dm-1 186 0 8696 104 0 0 0 0 0 80 104 We expect the queue depth of 'nvme0n1' to increase when the partitions it has increase, but this never happens. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: cosmic disk diskstats queue ** Package changed: apport (Ubuntu) => ubuntu ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1807432 Title: /proc/diskstats does not rollup queue depth from partitions Status in linux package in Ubuntu: Incomplete Bug description: Tested in Ubuntu 18.04LTS and Ubuntu 18.10, with the same result. The queue size rollup works in Centos 7 though. root@vagrant:~# uname -a Linux vagrant 4.18.0-12-generic #13-Ubuntu SMP Wed Nov 14 15:17:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@vagrant:~# lsb_release -rd Description:Ubuntu 18.10 Release:18.10 root@vagrant:~# cat /proc/diskstats 7 0 loop0 5 0 16 0 0 0 0 0 0 0 0 7 1 loop1 0 0 0 0 0 0 0 0 0 0 0 7 2 loop2 0 0 0 0 0 0 0 0 0 0 0 7 3 loop3 0 0 0 0 0 0 0 0 0 0 0 7 4 loop4 0 0 0 0 0 0 0 0 0 0 0 7 5 loop5 0 0 0 0 0 0 0 0 0 0 0 7 6 loop6 0 0 0 0 0 0 0 0 0 0 0 7 7 loop7 0 0 0 0 0 0 0 0 0 0 0 259 0 nvme0n1 813340 0 10963704 274028 4075 44 1040576 46884 0 18012 908472 259 5 nvme0n1p1 203838 0 2749463 65696 986 0 252416 11696 13 14360 218028 259 6 nvme0n1p2 202672 0 2713358 67924 1015 0 259840 11696 20 14372 220388 259 7 nvme0n1p3 202961 0 2717301 70464 1034 0 264704 11652 19 14344 226248 259 8 nvme0n1p4 203216 0 2730974 69944 1028 0 263168 11840 16 14340 224992 8 0 sda 11622 783 612090 16416 6529 9730 607624 52912 0 7964 76940 8 1 sda1 11543 783 607954 16408 4731 9730 607624 52844 0 7380 76304 253 0 dm-0 12083 0 598666 25540 16198 0 613808 137252 0 7936 162808 253 1 dm-1 186 0 8696 104 0 0 0 0 0 80 104 We expect the queue depth of 'nvme0n1' to increase when the partitions it has increase, but this never happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807432/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)
** Branch linked: lp:~ubuntu-core-dev/debian-installer/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1807023
Title:
installer stock images fail to validate any HTTPS certificates (ca-
certificates missing)
Status in debian-installer:
Unknown
Status in ca-certificates package in Ubuntu:
Invalid
Status in debian-installer package in Ubuntu:
In Progress
Status in ca-certificates source package in Trusty:
In Progress
Status in debian-installer source package in Trusty:
In Progress
Status in ca-certificates source package in Xenial:
In Progress
Status in debian-installer source package in Xenial:
In Progress
Status in ca-certificates source package in Bionic:
Invalid
Status in debian-installer source package in Bionic:
In Progress
Status in ca-certificates source package in Cosmic:
Invalid
Status in debian-installer source package in Cosmic:
In Progress
Status in ca-certificates source package in Disco:
Invalid
Status in debian-installer source package in Disco:
In Progress
Status in debian-installer package in Debian:
Fix Released
Bug description:
[Impact]
* The installer stock images fail to validate any HTTPS
certificates because ca-certificates is not available
in the installer environment.
* This causes wget/download errors for preseed files on
HTTPS servers (or HTTP servers that redirect to HTTPS,
which are increasingly common nowadays - e.g., GitHub)
and theoretically any other files that are downloaded
with d-i-utils/fetch-url/wget.
* The fix is to ship ca-certificates-udeb in installer
stock images.
* Debian already ships ca-certificate-udeb in the stock
installer images; the fix is applied since Jan 2017.
(reference: Debian Bug #842040 / d-i commit 2f00c51a [1])
[Test Case]
* In the installer shell:
~ # wget http://github.com # or https://github.com
- FAIL if ca-certificates-udeb is missing:
"ERROR: cannot verify github.com's certificate, <...>'
- PASS if ca-certificates-udeb is available
"Saving to: 'index.html'"
* Test steps with virt-install and netboot images
are provided in the comments, for each release.
[Regression Potential]
* Low. This just adds the ca-certificates files in
/etc/ssl/certs and symlink in /usr/lib/ssl/certs,
so only tools looking for that would be affected.
* Apparently only wget checks for/uses those files,
and the difference in behavior is download errors
no longer occur.
[Notes]
* The ca-certificates-udeb is not currently present
in the Ubuntu 'main' component, but in 'universe',
despite the normal deb being in 'main'.
However, when rebuilding in a PPA it goes into
'main' accordingly, and can be used by default
by debian-installer (otherwise, UDEB_COMPONENTS
has to be modified to include universe/d-i).
* So this fix includes a no-change-rebuild for the
ca-certificates package, in order to publish the
udeb in the archive (at least in PPA for testing).
Hopefully that can be sorted out for this fix
to work out.
* The ca-certificates and debian-installer builds
have been done in a PPA using all architectures,
and testing has been done with the amd64 images.
* This fix is requested for Bionic, Cosmic, Disco
at least.
* The fix for Trusty and Xenial needed a little
bit more work to build/ship the (new) udeb.
(reference: Debian Bug #845456 / ca-certificates commit 3acb3a90 [2])
It would be good to have them too if at all possible.
[1]
https://salsa.debian.org/installer-team/debian-installer/commit/2f00c51a7ead982ae1cd71bee06c8416890196b6
[2]
https://salsa.debian.org/debian/ca-certificates/commit/3acb3a9042a00307ba35d10052d81cdc206c34a4
[Debugging]
For debugging purposes, one can install strace-udeb in the installer
to verify wget's stat() calls to /usr/lib/ssl/certs.
~ # anna-install strace-udeb
~ # strace -e stat wget -O- https://github.com >/dev/null
...
Resolving github.com... stat("/etc/resolv.conf", {st_mode=S_IFREG|0644,
st_size=20, ...}) = 0
140.82.118.3, 140.82.118.4
Connecting to github.com|140.82.118.3|:443... connected.
stat("/usr/lib/ssl/certs/45bfefc3.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
ERROR: cannot verify github.com's certificate, issued by 'CN=DigiCert SHA2
Extended Validation Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US':
Unable to locally verify the issuer's authority.
To connect to github.com insecurely, use `--no-check-certificate'.
+++ exited with 5 +++
~ #
~ # anna-install ca-
[Touch-packages] [Bug 1807262] Re: stein unit tests fail with sqlalchemy.exc.NoSuchTableError: migration_tmp
** Also affects: sqlalchemy-migrate Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/1807262 Title: stein unit tests fail with sqlalchemy.exc.NoSuchTableError: migration_tmp Status in sqlalchemy-migrate: New Status in cinder package in Ubuntu: Invalid Status in migrate package in Ubuntu: Triaged Status in nova package in Ubuntu: Invalid Status in sqlite3 package in Ubuntu: Invalid Bug description: Several tests that use sqlite fail with: "sqlalchemy.exc.NoSuchTableError: migration_tmp". I'm currently hitting this with nova and cinder packages in disco. Note this started sometime after 11/19 when nova 2:19.0.0~b1~git2018111953.3e756ff674-0ubuntu1 was uploaded (and built successfully at the time). After doing some digging this appears to occur with libsqlite3-0 3.26.0-1 but does not occur with libsqlite3-0 3.25.3-1. Here are some more details on that, shown by running a failing unit test from the cinder package: https://paste.ubuntu.com/p/hsnQFQD572/ Update: The test in the paste above also works successfully with libsqlite3-0 3.25.3-2. To manage notifications about this bug go to: https://bugs.launchpad.net/sqlalchemy-migrate/+bug/1807262/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)
** Changed in: ca-certificates (Ubuntu Disco) Status: In Progress => Invalid ** Changed in: ca-certificates (Ubuntu Disco) Assignee: Mauricio Faria de Oliveira (mfo) => (unassigned) ** Changed in: ca-certificates (Ubuntu Cosmic) Status: In Progress => Invalid ** Changed in: ca-certificates (Ubuntu Cosmic) Assignee: Mauricio Faria de Oliveira (mfo) => (unassigned) ** Changed in: ca-certificates (Ubuntu Bionic) Status: In Progress => Invalid ** Changed in: ca-certificates (Ubuntu Bionic) Assignee: Mauricio Faria de Oliveira (mfo) => (unassigned) ** Changed in: ca-certificates (Ubuntu Xenial) Status: New => Invalid ** Changed in: ca-certificates (Ubuntu Xenial) Status: Invalid => In Progress ** Changed in: ca-certificates (Ubuntu Xenial) Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo) ** Changed in: ca-certificates (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: ca-certificates (Ubuntu Trusty) Status: New => In Progress ** Changed in: ca-certificates (Ubuntu Trusty) Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo) ** Changed in: ca-certificates (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: debian-installer (Ubuntu Xenial) Status: New => In Progress ** Changed in: debian-installer (Ubuntu Xenial) Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo) ** Changed in: debian-installer (Ubuntu Trusty) Status: New => In Progress ** Changed in: debian-installer (Ubuntu Trusty) Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1807023 Title: installer stock images fail to validate any HTTPS certificates (ca- certificates missing) Status in debian-installer: Unknown Status in ca-certificates package in Ubuntu: Invalid Status in debian-installer package in Ubuntu: In Progress Status in ca-certificates source package in Trusty: In Progress Status in debian-installer source package in Trusty: In Progress Status in ca-certificates source package in Xenial: In Progress Status in debian-installer source package in Xenial: In Progress Status in ca-certificates source package in Bionic: Invalid Status in debian-installer source package in Bionic: In Progress Status in ca-certificates source package in Cosmic: Invalid Status in debian-installer source package in Cosmic: In Progress Status in ca-certificates source package in Disco: Invalid Status in debian-installer source package in Disco: In Progress Status in debian-installer package in Debian: Fix Released Bug description: [Impact] * The installer stock images fail to validate any HTTPS certificates because ca-certificates is not available in the installer environment. * This causes wget/download errors for preseed files on HTTPS servers (or HTTP servers that redirect to HTTPS, which are increasingly common nowadays - e.g., GitHub) and theoretically any other files that are downloaded with d-i-utils/fetch-url/wget. * The fix is to ship ca-certificates-udeb in installer stock images. * Debian already ships ca-certificate-udeb in the stock installer images; the fix is applied since Jan 2017. (reference: Debian Bug #842040 / d-i commit 2f00c51a [1]) [Test Case] * In the installer shell: ~ # wget http://github.com # or https://github.com - FAIL if ca-certificates-udeb is missing: "ERROR: cannot verify github.com's certificate, <...>' - PASS if ca-certificates-udeb is available "Saving to: 'index.html'" * Test steps with virt-install and netboot images are provided in the comments, for each release. [Regression Potential] * Low. This just adds the ca-certificates files in /etc/ssl/certs and symlink in /usr/lib/ssl/certs, so only tools looking for that would be affected. * Apparently only wget checks for/uses those files, and the difference in behavior is download errors no longer occur. [Notes] * The ca-certificates-udeb is not currently present in the Ubuntu 'main' component, but in 'universe', despite the normal deb being in 'main'. However, when rebuilding in a PPA it goes into 'main' accordingly, and can be used by default by debian-installer (otherwise, UDEB_COMPONENTS has to be modified to include universe/d-i). * So this fix includes a no-change-rebuild for the ca-certificates package, in order to publish the udeb in the archive (at least in PPA for testing). Hopefully that can be sorted out for this fix to work out. * The ca-certificates and debian-installer builds have been done in a PPA using all architectures, and testing has been done with the amd64 images. *
[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)
Marked ca-certificates for b/c/d as Invalid - it does not need an upload, only archive twiddling to move its component. For t/x, ca-certificates does need the patches @mfo attached to actually generate the -udeb binary pkg. Please nobody sponsor this bug - @slashd or I will handle the sruing. ** Patch removed: "lp1807023-ca-certificates-disco.debdiff" https://bugs.launchpad.net/ubuntu/trusty/+source/debian-installer/+bug/1807023/+attachment/5219788/+files/lp1807023-ca-certificates-disco.debdiff ** Patch removed: "lp1807023-ca-certificates-cosmic.debdiff" https://bugs.launchpad.net/ubuntu/trusty/+source/debian-installer/+bug/1807023/+attachment/5219789/+files/lp1807023-ca-certificates-cosmic.debdiff ** Patch removed: "lp1807023-ca-certificates-bionic.debdiff" https://bugs.launchpad.net/ubuntu/trusty/+source/debian-installer/+bug/1807023/+attachment/5219790/+files/lp1807023-ca-certificates-bionic.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1807023 Title: installer stock images fail to validate any HTTPS certificates (ca- certificates missing) Status in debian-installer: Unknown Status in ca-certificates package in Ubuntu: Invalid Status in debian-installer package in Ubuntu: In Progress Status in ca-certificates source package in Trusty: In Progress Status in debian-installer source package in Trusty: In Progress Status in ca-certificates source package in Xenial: In Progress Status in debian-installer source package in Xenial: In Progress Status in ca-certificates source package in Bionic: Invalid Status in debian-installer source package in Bionic: In Progress Status in ca-certificates source package in Cosmic: Invalid Status in debian-installer source package in Cosmic: In Progress Status in ca-certificates source package in Disco: Invalid Status in debian-installer source package in Disco: In Progress Status in debian-installer package in Debian: Fix Released Bug description: [Impact] * The installer stock images fail to validate any HTTPS certificates because ca-certificates is not available in the installer environment. * This causes wget/download errors for preseed files on HTTPS servers (or HTTP servers that redirect to HTTPS, which are increasingly common nowadays - e.g., GitHub) and theoretically any other files that are downloaded with d-i-utils/fetch-url/wget. * The fix is to ship ca-certificates-udeb in installer stock images. * Debian already ships ca-certificate-udeb in the stock installer images; the fix is applied since Jan 2017. (reference: Debian Bug #842040 / d-i commit 2f00c51a [1]) [Test Case] * In the installer shell: ~ # wget http://github.com # or https://github.com - FAIL if ca-certificates-udeb is missing: "ERROR: cannot verify github.com's certificate, <...>' - PASS if ca-certificates-udeb is available "Saving to: 'index.html'" * Test steps with virt-install and netboot images are provided in the comments, for each release. [Regression Potential] * Low. This just adds the ca-certificates files in /etc/ssl/certs and symlink in /usr/lib/ssl/certs, so only tools looking for that would be affected. * Apparently only wget checks for/uses those files, and the difference in behavior is download errors no longer occur. [Notes] * The ca-certificates-udeb is not currently present in the Ubuntu 'main' component, but in 'universe', despite the normal deb being in 'main'. However, when rebuilding in a PPA it goes into 'main' accordingly, and can be used by default by debian-installer (otherwise, UDEB_COMPONENTS has to be modified to include universe/d-i). * So this fix includes a no-change-rebuild for the ca-certificates package, in order to publish the udeb in the archive (at least in PPA for testing). Hopefully that can be sorted out for this fix to work out. * The ca-certificates and debian-installer builds have been done in a PPA using all architectures, and testing has been done with the amd64 images. * This fix is requested for Bionic, Cosmic, Disco at least. * The fix for Trusty and Xenial needed a little bit more work to build/ship the (new) udeb. (reference: Debian Bug #845456 / ca-certificates commit 3acb3a90 [2]) It would be good to have them too if at all possible. [1] https://salsa.debian.org/installer-team/debian-installer/commit/2f00c51a7ead982ae1cd71bee06c8416890196b6 [2] https://salsa.debian.org/debian/ca-certificates/commit/3acb3a9042a00307ba35d10052d81cdc206c34a4 [Debugging] For debugging purposes, one can install strace-udeb in the installer to verify wget's stat() calls to /usr/lib/ssl/certs. ~ # anna-install strace-u
[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)
Please do the necessary to make sure we don't upload ca-certificates by
mistake again.
I would suggest we :
1) Remove the debdiff
2) Set the status for ca-certificates to "Won't Fix"
To avoid confusion.
The ca-certificates work need to be done by an archive admin, no rebuild
needed.
Regards,
Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1807023
Title:
installer stock images fail to validate any HTTPS certificates (ca-
certificates missing)
Status in debian-installer:
Unknown
Status in ca-certificates package in Ubuntu:
Invalid
Status in debian-installer package in Ubuntu:
In Progress
Status in ca-certificates source package in Trusty:
In Progress
Status in debian-installer source package in Trusty:
In Progress
Status in ca-certificates source package in Xenial:
In Progress
Status in debian-installer source package in Xenial:
In Progress
Status in ca-certificates source package in Bionic:
Invalid
Status in debian-installer source package in Bionic:
In Progress
Status in ca-certificates source package in Cosmic:
Invalid
Status in debian-installer source package in Cosmic:
In Progress
Status in ca-certificates source package in Disco:
Invalid
Status in debian-installer source package in Disco:
In Progress
Status in debian-installer package in Debian:
Fix Released
Bug description:
[Impact]
* The installer stock images fail to validate any HTTPS
certificates because ca-certificates is not available
in the installer environment.
* This causes wget/download errors for preseed files on
HTTPS servers (or HTTP servers that redirect to HTTPS,
which are increasingly common nowadays - e.g., GitHub)
and theoretically any other files that are downloaded
with d-i-utils/fetch-url/wget.
* The fix is to ship ca-certificates-udeb in installer
stock images.
* Debian already ships ca-certificate-udeb in the stock
installer images; the fix is applied since Jan 2017.
(reference: Debian Bug #842040 / d-i commit 2f00c51a [1])
[Test Case]
* In the installer shell:
~ # wget http://github.com # or https://github.com
- FAIL if ca-certificates-udeb is missing:
"ERROR: cannot verify github.com's certificate, <...>'
- PASS if ca-certificates-udeb is available
"Saving to: 'index.html'"
* Test steps with virt-install and netboot images
are provided in the comments, for each release.
[Regression Potential]
* Low. This just adds the ca-certificates files in
/etc/ssl/certs and symlink in /usr/lib/ssl/certs,
so only tools looking for that would be affected.
* Apparently only wget checks for/uses those files,
and the difference in behavior is download errors
no longer occur.
[Notes]
* The ca-certificates-udeb is not currently present
in the Ubuntu 'main' component, but in 'universe',
despite the normal deb being in 'main'.
However, when rebuilding in a PPA it goes into
'main' accordingly, and can be used by default
by debian-installer (otherwise, UDEB_COMPONENTS
has to be modified to include universe/d-i).
* So this fix includes a no-change-rebuild for the
ca-certificates package, in order to publish the
udeb in the archive (at least in PPA for testing).
Hopefully that can be sorted out for this fix
to work out.
* The ca-certificates and debian-installer builds
have been done in a PPA using all architectures,
and testing has been done with the amd64 images.
* This fix is requested for Bionic, Cosmic, Disco
at least.
* The fix for Trusty and Xenial needed a little
bit more work to build/ship the (new) udeb.
(reference: Debian Bug #845456 / ca-certificates commit 3acb3a90 [2])
It would be good to have them too if at all possible.
[1]
https://salsa.debian.org/installer-team/debian-installer/commit/2f00c51a7ead982ae1cd71bee06c8416890196b6
[2]
https://salsa.debian.org/debian/ca-certificates/commit/3acb3a9042a00307ba35d10052d81cdc206c34a4
[Debugging]
For debugging purposes, one can install strace-udeb in the installer
to verify wget's stat() calls to /usr/lib/ssl/certs.
~ # anna-install strace-udeb
~ # strace -e stat wget -O- https://github.com >/dev/null
...
Resolving github.com... stat("/etc/resolv.conf", {st_mode=S_IFREG|0644,
st_size=20, ...}) = 0
140.82.118.3, 140.82.118.4
Connecting to github.com|140.82.118.3|:443... connected.
stat("/usr/lib/ssl/certs/45bfefc3.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
ERROR: cannot verify github.com's certificate, issued by 'CN=DigiCert SHA2
Extende
[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)
removing the sponsors team - please nobody upload this! @slashd or i
will sru when ready.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1807023
Title:
installer stock images fail to validate any HTTPS certificates (ca-
certificates missing)
Status in debian-installer:
Unknown
Status in ca-certificates package in Ubuntu:
Invalid
Status in debian-installer package in Ubuntu:
In Progress
Status in ca-certificates source package in Trusty:
In Progress
Status in debian-installer source package in Trusty:
In Progress
Status in ca-certificates source package in Xenial:
In Progress
Status in debian-installer source package in Xenial:
In Progress
Status in ca-certificates source package in Bionic:
Invalid
Status in debian-installer source package in Bionic:
In Progress
Status in ca-certificates source package in Cosmic:
Invalid
Status in debian-installer source package in Cosmic:
In Progress
Status in ca-certificates source package in Disco:
Invalid
Status in debian-installer source package in Disco:
In Progress
Status in debian-installer package in Debian:
Fix Released
Bug description:
[Impact]
* The installer stock images fail to validate any HTTPS
certificates because ca-certificates is not available
in the installer environment.
* This causes wget/download errors for preseed files on
HTTPS servers (or HTTP servers that redirect to HTTPS,
which are increasingly common nowadays - e.g., GitHub)
and theoretically any other files that are downloaded
with d-i-utils/fetch-url/wget.
* The fix is to ship ca-certificates-udeb in installer
stock images.
* Debian already ships ca-certificate-udeb in the stock
installer images; the fix is applied since Jan 2017.
(reference: Debian Bug #842040 / d-i commit 2f00c51a [1])
[Test Case]
* In the installer shell:
~ # wget http://github.com # or https://github.com
- FAIL if ca-certificates-udeb is missing:
"ERROR: cannot verify github.com's certificate, <...>'
- PASS if ca-certificates-udeb is available
"Saving to: 'index.html'"
* Test steps with virt-install and netboot images
are provided in the comments, for each release.
[Regression Potential]
* Low. This just adds the ca-certificates files in
/etc/ssl/certs and symlink in /usr/lib/ssl/certs,
so only tools looking for that would be affected.
* Apparently only wget checks for/uses those files,
and the difference in behavior is download errors
no longer occur.
[Notes]
* The ca-certificates-udeb is not currently present
in the Ubuntu 'main' component, but in 'universe',
despite the normal deb being in 'main'.
However, when rebuilding in a PPA it goes into
'main' accordingly, and can be used by default
by debian-installer (otherwise, UDEB_COMPONENTS
has to be modified to include universe/d-i).
* So this fix includes a no-change-rebuild for the
ca-certificates package, in order to publish the
udeb in the archive (at least in PPA for testing).
Hopefully that can be sorted out for this fix
to work out.
* The ca-certificates and debian-installer builds
have been done in a PPA using all architectures,
and testing has been done with the amd64 images.
* This fix is requested for Bionic, Cosmic, Disco
at least.
* The fix for Trusty and Xenial needed a little
bit more work to build/ship the (new) udeb.
(reference: Debian Bug #845456 / ca-certificates commit 3acb3a90 [2])
It would be good to have them too if at all possible.
[1]
https://salsa.debian.org/installer-team/debian-installer/commit/2f00c51a7ead982ae1cd71bee06c8416890196b6
[2]
https://salsa.debian.org/debian/ca-certificates/commit/3acb3a9042a00307ba35d10052d81cdc206c34a4
[Debugging]
For debugging purposes, one can install strace-udeb in the installer
to verify wget's stat() calls to /usr/lib/ssl/certs.
~ # anna-install strace-udeb
~ # strace -e stat wget -O- https://github.com >/dev/null
...
Resolving github.com... stat("/etc/resolv.conf", {st_mode=S_IFREG|0644,
st_size=20, ...}) = 0
140.82.118.3, 140.82.118.4
Connecting to github.com|140.82.118.3|:443... connected.
stat("/usr/lib/ssl/certs/45bfefc3.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
ERROR: cannot verify github.com's certificate, issued by 'CN=DigiCert SHA2
Extended Validation Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US':
Unable to locally verify the issuer's authority.
To connect to github.com insecurely, use `--no-check-certificate'.
+++ exited with 5 +++
[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)
>From #ubuntu-release (freenode)
With regards to the FTBFS situation with ca-certificates-udeb:
slashd: Promoted. I'll retry the builds when the publisher's done
moving it around.
slashd: Just disco. For other releases, it'll require some fiddling.
I'll continue with the SRU as soon as disco is building fine and goes
into -releases.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1807023
Title:
installer stock images fail to validate any HTTPS certificates (ca-
certificates missing)
Status in debian-installer:
Unknown
Status in ca-certificates package in Ubuntu:
In Progress
Status in debian-installer package in Ubuntu:
In Progress
Status in ca-certificates source package in Trusty:
New
Status in debian-installer source package in Trusty:
New
Status in ca-certificates source package in Xenial:
New
Status in debian-installer source package in Xenial:
New
Status in ca-certificates source package in Bionic:
In Progress
Status in debian-installer source package in Bionic:
In Progress
Status in ca-certificates source package in Cosmic:
In Progress
Status in debian-installer source package in Cosmic:
In Progress
Status in ca-certificates source package in Disco:
In Progress
Status in debian-installer source package in Disco:
In Progress
Status in debian-installer package in Debian:
Fix Released
Bug description:
[Impact]
* The installer stock images fail to validate any HTTPS
certificates because ca-certificates is not available
in the installer environment.
* This causes wget/download errors for preseed files on
HTTPS servers (or HTTP servers that redirect to HTTPS,
which are increasingly common nowadays - e.g., GitHub)
and theoretically any other files that are downloaded
with d-i-utils/fetch-url/wget.
* The fix is to ship ca-certificates-udeb in installer
stock images.
* Debian already ships ca-certificate-udeb in the stock
installer images; the fix is applied since Jan 2017.
(reference: Debian Bug #842040 / d-i commit 2f00c51a [1])
[Test Case]
* In the installer shell:
~ # wget http://github.com # or https://github.com
- FAIL if ca-certificates-udeb is missing:
"ERROR: cannot verify github.com's certificate, <...>'
- PASS if ca-certificates-udeb is available
"Saving to: 'index.html'"
* Test steps with virt-install and netboot images
are provided in the comments, for each release.
[Regression Potential]
* Low. This just adds the ca-certificates files in
/etc/ssl/certs and symlink in /usr/lib/ssl/certs,
so only tools looking for that would be affected.
* Apparently only wget checks for/uses those files,
and the difference in behavior is download errors
no longer occur.
[Notes]
* The ca-certificates-udeb is not currently present
in the Ubuntu 'main' component, but in 'universe',
despite the normal deb being in 'main'.
However, when rebuilding in a PPA it goes into
'main' accordingly, and can be used by default
by debian-installer (otherwise, UDEB_COMPONENTS
has to be modified to include universe/d-i).
* So this fix includes a no-change-rebuild for the
ca-certificates package, in order to publish the
udeb in the archive (at least in PPA for testing).
Hopefully that can be sorted out for this fix
to work out.
* The ca-certificates and debian-installer builds
have been done in a PPA using all architectures,
and testing has been done with the amd64 images.
* This fix is requested for Bionic, Cosmic, Disco
at least.
* The fix for Trusty and Xenial needed a little
bit more work to build/ship the (new) udeb.
(reference: Debian Bug #845456 / ca-certificates commit 3acb3a90 [2])
It would be good to have them too if at all possible.
[1]
https://salsa.debian.org/installer-team/debian-installer/commit/2f00c51a7ead982ae1cd71bee06c8416890196b6
[2]
https://salsa.debian.org/debian/ca-certificates/commit/3acb3a9042a00307ba35d10052d81cdc206c34a4
[Debugging]
For debugging purposes, one can install strace-udeb in the installer
to verify wget's stat() calls to /usr/lib/ssl/certs.
~ # anna-install strace-udeb
~ # strace -e stat wget -O- https://github.com >/dev/null
...
Resolving github.com... stat("/etc/resolv.conf", {st_mode=S_IFREG|0644,
st_size=20, ...}) = 0
140.82.118.3, 140.82.118.4
Connecting to github.com|140.82.118.3|:443... connected.
stat("/usr/lib/ssl/certs/45bfefc3.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
ERROR: cannot verify github.com's certificate, issued by 'C
[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)
>From #ubuntu-release (freenode)
With regards to the FTBFS situation with ca-certificates-udeb:
slashd: Promoted. I'll retry the builds when the publisher's
done moving it around.
I'll continue with the SRU as soon as disco is building fine and goes
into -releases.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1807023
Title:
installer stock images fail to validate any HTTPS certificates (ca-
certificates missing)
Status in debian-installer:
Unknown
Status in ca-certificates package in Ubuntu:
In Progress
Status in debian-installer package in Ubuntu:
In Progress
Status in ca-certificates source package in Trusty:
New
Status in debian-installer source package in Trusty:
New
Status in ca-certificates source package in Xenial:
New
Status in debian-installer source package in Xenial:
New
Status in ca-certificates source package in Bionic:
In Progress
Status in debian-installer source package in Bionic:
In Progress
Status in ca-certificates source package in Cosmic:
In Progress
Status in debian-installer source package in Cosmic:
In Progress
Status in ca-certificates source package in Disco:
In Progress
Status in debian-installer source package in Disco:
In Progress
Status in debian-installer package in Debian:
Fix Released
Bug description:
[Impact]
* The installer stock images fail to validate any HTTPS
certificates because ca-certificates is not available
in the installer environment.
* This causes wget/download errors for preseed files on
HTTPS servers (or HTTP servers that redirect to HTTPS,
which are increasingly common nowadays - e.g., GitHub)
and theoretically any other files that are downloaded
with d-i-utils/fetch-url/wget.
* The fix is to ship ca-certificates-udeb in installer
stock images.
* Debian already ships ca-certificate-udeb in the stock
installer images; the fix is applied since Jan 2017.
(reference: Debian Bug #842040 / d-i commit 2f00c51a [1])
[Test Case]
* In the installer shell:
~ # wget http://github.com # or https://github.com
- FAIL if ca-certificates-udeb is missing:
"ERROR: cannot verify github.com's certificate, <...>'
- PASS if ca-certificates-udeb is available
"Saving to: 'index.html'"
* Test steps with virt-install and netboot images
are provided in the comments, for each release.
[Regression Potential]
* Low. This just adds the ca-certificates files in
/etc/ssl/certs and symlink in /usr/lib/ssl/certs,
so only tools looking for that would be affected.
* Apparently only wget checks for/uses those files,
and the difference in behavior is download errors
no longer occur.
[Notes]
* The ca-certificates-udeb is not currently present
in the Ubuntu 'main' component, but in 'universe',
despite the normal deb being in 'main'.
However, when rebuilding in a PPA it goes into
'main' accordingly, and can be used by default
by debian-installer (otherwise, UDEB_COMPONENTS
has to be modified to include universe/d-i).
* So this fix includes a no-change-rebuild for the
ca-certificates package, in order to publish the
udeb in the archive (at least in PPA for testing).
Hopefully that can be sorted out for this fix
to work out.
* The ca-certificates and debian-installer builds
have been done in a PPA using all architectures,
and testing has been done with the amd64 images.
* This fix is requested for Bionic, Cosmic, Disco
at least.
* The fix for Trusty and Xenial needed a little
bit more work to build/ship the (new) udeb.
(reference: Debian Bug #845456 / ca-certificates commit 3acb3a90 [2])
It would be good to have them too if at all possible.
[1]
https://salsa.debian.org/installer-team/debian-installer/commit/2f00c51a7ead982ae1cd71bee06c8416890196b6
[2]
https://salsa.debian.org/debian/ca-certificates/commit/3acb3a9042a00307ba35d10052d81cdc206c34a4
[Debugging]
For debugging purposes, one can install strace-udeb in the installer
to verify wget's stat() calls to /usr/lib/ssl/certs.
~ # anna-install strace-udeb
~ # strace -e stat wget -O- https://github.com >/dev/null
...
Resolving github.com... stat("/etc/resolv.conf", {st_mode=S_IFREG|0644,
st_size=20, ...}) = 0
140.82.118.3, 140.82.118.4
Connecting to github.com|140.82.118.3|:443... connected.
stat("/usr/lib/ssl/certs/45bfefc3.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
ERROR: cannot verify github.com's certificate, issued by 'CN=DigiCert SHA2
Extended Validation Server CA,OU=www.digicert.com,O=Dig
[Touch-packages] [Bug 1807262] Re: stein unit tests fail with sqlalchemy.exc.NoSuchTableError: migration_tmp
Laszlo, I just tested with the updates you posted in comment #8 and it works. \o/ ** Also affects: migrate (Ubuntu) Importance: Undecided Status: New ** Changed in: migrate (Ubuntu) Status: New => Triaged ** Changed in: migrate (Ubuntu) Importance: Undecided => High ** Changed in: nova (Ubuntu) Status: Triaged => Invalid ** Changed in: cinder (Ubuntu) Status: Triaged => Invalid ** Changed in: sqlite3 (Ubuntu) Status: New => Invalid ** Changed in: nova (Ubuntu) Importance: High => Undecided ** Changed in: cinder (Ubuntu) Importance: High => Undecided -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/1807262 Title: stein unit tests fail with sqlalchemy.exc.NoSuchTableError: migration_tmp Status in cinder package in Ubuntu: Invalid Status in migrate package in Ubuntu: Triaged Status in nova package in Ubuntu: Invalid Status in sqlite3 package in Ubuntu: Invalid Bug description: Several tests that use sqlite fail with: "sqlalchemy.exc.NoSuchTableError: migration_tmp". I'm currently hitting this with nova and cinder packages in disco. Note this started sometime after 11/19 when nova 2:19.0.0~b1~git2018111953.3e756ff674-0ubuntu1 was uploaded (and built successfully at the time). After doing some digging this appears to occur with libsqlite3-0 3.26.0-1 but does not occur with libsqlite3-0 3.25.3-1. Here are some more details on that, shown by running a failing unit test from the cinder package: https://paste.ubuntu.com/p/hsnQFQD572/ Update: The test in the paste above also works successfully with libsqlite3-0 3.25.3-2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1807262/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807262] Re: stein unit tests fail with sqlalchemy.exc.NoSuchTableError: migration_tmp
Laszlo, that fix seems reasonable. Do you want to push on getting that into migrate and uploaded to Debian or would you like one of us to handle it? Thanks again for the quick responses on this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/1807262 Title: stein unit tests fail with sqlalchemy.exc.NoSuchTableError: migration_tmp Status in cinder package in Ubuntu: Invalid Status in migrate package in Ubuntu: Triaged Status in nova package in Ubuntu: Invalid Status in sqlite3 package in Ubuntu: Invalid Bug description: Several tests that use sqlite fail with: "sqlalchemy.exc.NoSuchTableError: migration_tmp". I'm currently hitting this with nova and cinder packages in disco. Note this started sometime after 11/19 when nova 2:19.0.0~b1~git2018111953.3e756ff674-0ubuntu1 was uploaded (and built successfully at the time). After doing some digging this appears to occur with libsqlite3-0 3.26.0-1 but does not occur with libsqlite3-0 3.25.3-1. Here are some more details on that, shown by running a failing unit test from the cinder package: https://paste.ubuntu.com/p/hsnQFQD572/ Update: The test in the paste above also works successfully with libsqlite3-0 3.25.3-2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1807262/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806961] Re: Lock can be circumvented by switching tty when using lightdm
** Tags added: community-security ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1806961 Title: Lock can be circumvented by switching tty when using lightdm Status in lightdm package in Ubuntu: Confirmed Bug description: Steps to reproduce (only works on X11, not on wayland): 1) install lightdm a) run "sudo apt install lightdm" on a fresh 18.04 install of ubuntu b) switch to lightdm with "sudo dpkg-reconfigure gdm3" c) reboot to make the login manager switch take effect 2) log in to your account 3) click switch user (clicking lock should also work) in the dropdown in the top right corner 4) switch to a different tty (ctrl+alt+f2 for example) 5) switch back to your original tty (with lightdm usally tty 7) You are now logged back in your account without having to type your password. I have marked lightdm as the vulnerable package because all I had to do to reproduce the issue was install lightdm with "sudo apt install lightdm" and then switch to lightdm with "sudo dpkg-reconfigure gdm3" So I think something should either be changed in lightdm or in dpkg- reconfigure. I have been told that I should be using light-locker instead of dm-tool, but I have no idea what those things are, or how to switch between them, i'm just clicking switch user. The user does not know, and is never informed of the existence of these tools. Since neither apt, nor dpkg-reconfigure warns me that i should use lightlocker instead of dm-tool, I think this is still a security vulnerability, because a user that wants to use lightdm and installs it by quickly searching online for "how to switch login managers" will not be informed of this vulnerability. Extra info: ubuntu 18.04 (fully up to date) lightdm version 1.26.0-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1806961/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807262] Re: stein unit tests fail with sqlalchemy.exc.NoSuchTableError: migration_tmp
Indentation is messed up during the post, but easy to correct if you see the source of the migrate/changeset/databases/sqlite.py file. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/1807262 Title: stein unit tests fail with sqlalchemy.exc.NoSuchTableError: migration_tmp Status in cinder package in Ubuntu: Triaged Status in nova package in Ubuntu: Triaged Status in sqlite3 package in Ubuntu: New Bug description: Several tests that use sqlite fail with: "sqlalchemy.exc.NoSuchTableError: migration_tmp". I'm currently hitting this with nova and cinder packages in disco. Note this started sometime after 11/19 when nova 2:19.0.0~b1~git2018111953.3e756ff674-0ubuntu1 was uploaded (and built successfully at the time). After doing some digging this appears to occur with libsqlite3-0 3.26.0-1 but does not occur with libsqlite3-0 3.25.3-1. Here are some more details on that, shown by running a failing unit test from the cinder package: https://paste.ubuntu.com/p/hsnQFQD572/ Update: The test in the paste above also works successfully with libsqlite3-0 3.25.3-2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1807262/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807262] Re: stein unit tests fail with sqlalchemy.exc.NoSuchTableError: migration_tmp
It's 'PRAGMA legacy_alter_table = ON' and the following change in
src:migrate (0.11.0 version) might do the trick.
@@ -9,6 +9,7 @@ except ImportError: # Python 2
from UserDict import DictMixin
from copy import copy
import re
+import sqlite3
from sqlalchemy.databases import sqlite as sa_base
from sqlalchemy.schema import ForeignKeyConstraint
@@ -96,6 +97,10 @@ class SQLiteHelper(SQLiteCommon):
if omit_constraints is None or cons.name not in omit_constraints
])
+tup = sqlite3.sqlite_version_info
+if tup[0] > 3 or (tup[0] == 3 and tup[1] >= 26):
+self.append('PRAGMA legacy_alter_table = ON')
+self.execute()
self.append('ALTER TABLE %s RENAME TO migration_tmp' % table_name)
self.execute()
@@ -106,6 +111,9 @@ class SQLiteHelper(SQLiteCommon):
self.execute()
self.append('DROP TABLE migration_tmp')
self.execute()
+if tup[0] > 3 or (tup[0] == 3 and tup[1] >= 26):
+self.append('PRAGMA legacy_alter_table = OFF')
+self.execute()
def visit_column(self, delta):
if isinstance(delta, DictMixin):
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sqlite3 in Ubuntu.
https://bugs.launchpad.net/bugs/1807262
Title:
stein unit tests fail with sqlalchemy.exc.NoSuchTableError:
migration_tmp
Status in cinder package in Ubuntu:
Triaged
Status in nova package in Ubuntu:
Triaged
Status in sqlite3 package in Ubuntu:
New
Bug description:
Several tests that use sqlite fail with:
"sqlalchemy.exc.NoSuchTableError: migration_tmp". I'm currently
hitting this with nova and cinder packages in disco.
Note this started sometime after 11/19 when nova
2:19.0.0~b1~git2018111953.3e756ff674-0ubuntu1 was uploaded (and built
successfully at the time).
After doing some digging this appears to occur with libsqlite3-0
3.26.0-1 but does not occur with libsqlite3-0 3.25.3-1. Here are some
more details on that, shown by running a failing unit test from the
cinder package: https://paste.ubuntu.com/p/hsnQFQD572/
Update: The test in the paste above also works successfully with
libsqlite3-0 3.25.3-2.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1807262/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1805426] Re: Not able to log in into Google Account, aswell as Microsoft account
Thank you for the debugging. I don't think goa requires IPv6, could you give details on how you disabled IPv6? Maybe doing the same steps is enough for others to reproduce the issue. The issue connecting to ppas when IPv6 is enabling is a bug by itself, either in the software or in your local network configuration ** Changed in: gnome-initial-setup (Ubuntu) Status: Incomplete => Invalid ** Package changed: gnome-control-center (Ubuntu) => gnome-online- accounts (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1805426 Title: Not able to log in into Google Account, aswell as Microsoft account Status in gnome-initial-setup package in Ubuntu: Invalid Status in gnome-online-accounts package in Ubuntu: New Bug description: After the first boot up of Ubuntu 18.10, it invites me to log-in into several accounts, including Google and Microsoft accounts. After I log-in into Ubuntu One, my next step is to log in my Google Account, but the log-in page never loads, and when it does (after a couple of minutes), and I insert my log in credentials, it fails the log-in process, all of this happens with the Microsoft account too. The Ubuntu One account logs-in without a hitch, but the rest does not. 1) Description: Ubuntu 18.10 Release: 18.10 2) gnome-initial-setup: Instalado: 3.30.0-1ubuntu3 Candidato: 3.30.0-1ubuntu3.1 Tabela de versão: 3.30.0-1ubuntu3.1 500 500 http://br.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages *** 3.30.0-1ubuntu3 500 500 http://br.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-initial-setup 3.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 27 11:12:31 2018 ExecutablePath: /usr/lib/gnome-initial-setup/gnome-initial-setup InstallationDate: Installed on 2018-11-27 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-initial-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1805426/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
Can confirm that this is reproducible with the standard Ubuntu session in 18.04.01 and 18.10, tested both with the vanilla install with no updates and also fully updated. However, notice a few things: - If you repeatedly click the checkbox it will sometimes trigger the authentication window - The issue is *only* reproducible when the user do not have the permission to apply the changes (ie. before triggering the authentication window). It will also not be reproducible in a live session. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab Status in software-properties package in Ubuntu: Confirmed Bug description: On the "Other Software" tab, I am unable to select "Canonical Partners". Similarly, the other checkboxes on the "Other Software" can not be clicked. Clicking on a checkbox has no effect, and a dialog requesting the admin password is not presented. However, activating or deactivating checkboxes on other tabs causes an authorization dialog to be presented to the user. I experience this bug in an an Xorg session. sources.list and sources.list.d have the following permissions: -rw-r--r-- 1 root root 2897 Oct 26 22:35 sources.list drwxr-xr-x 2 root root 4096 Oct 26 21:29 sources.list.d All files in sources.list.d have the following permissions as this example: -rw-r--r-- 1 root root 189 Oct 25 21:50 google-chrome.list $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.96.24.17 Candidate: 0.96.24.17 Version table: *** 0.96.24.17 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 26 22:45:09 2017 InstallationDate: Installed on 2017-10-26 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark" PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1727908/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1805426] [NEW] Not able to log in into Google Account, aswell as Microsoft account
You have been subscribed to a public bug: After the first boot up of Ubuntu 18.10, it invites me to log-in into several accounts, including Google and Microsoft accounts. After I log- in into Ubuntu One, my next step is to log in my Google Account, but the log-in page never loads, and when it does (after a couple of minutes), and I insert my log in credentials, it fails the log-in process, all of this happens with the Microsoft account too. The Ubuntu One account logs-in without a hitch, but the rest does not. 1) Description: Ubuntu 18.10 Release:18.10 2) gnome-initial-setup: Instalado: 3.30.0-1ubuntu3 Candidato: 3.30.0-1ubuntu3.1 Tabela de versão: 3.30.0-1ubuntu3.1 500 500 http://br.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages *** 3.30.0-1ubuntu3 500 500 http://br.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-initial-setup 3.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 27 11:12:31 2018 ExecutablePath: /usr/lib/gnome-initial-setup/gnome-initial-setup InstallationDate: Installed on 2018-11-27 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-initial-setup UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-online-accounts (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-initial-setup (Ubuntu) Importance: Low Status: Invalid ** Tags: amd64 apport-bug cosmic -- Not able to log in into Google Account, aswell as Microsoft account https://bugs.launchpad.net/bugs/1805426 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts 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 1795844] Re: package libqt4-network:amd64 4:4.8.7+dfsg-7ubuntu1 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de inte
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qt4-x11 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1795844 Title: package libqt4-network:amd64 4:4.8.7+dfsg-7ubuntu1 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. Status in qt4-x11 package in Ubuntu: Confirmed Bug description: This error occured when i tried to install git using sudo apt-get install git ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libqt4-network:amd64 4:4.8.7+dfsg-7ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 AptOrdering: liberror-perl:amd64: Install git-man:amd64: Install git:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Wed Oct 3 04:42:26 2018 ErrorMessage: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. InstallationDate: Installed on 2018-09-30 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: qt4-x11 Title: package libqt4-network:amd64 4:4.8.7+dfsg-7ubuntu1 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1795844/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
Using GTK_THEME=Adwaita software-properties-gtk works fine as well... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab Status in software-properties package in Ubuntu: Confirmed Bug description: On the "Other Software" tab, I am unable to select "Canonical Partners". Similarly, the other checkboxes on the "Other Software" can not be clicked. Clicking on a checkbox has no effect, and a dialog requesting the admin password is not presented. However, activating or deactivating checkboxes on other tabs causes an authorization dialog to be presented to the user. I experience this bug in an an Xorg session. sources.list and sources.list.d have the following permissions: -rw-r--r-- 1 root root 2897 Oct 26 22:35 sources.list drwxr-xr-x 2 root root 4096 Oct 26 21:29 sources.list.d All files in sources.list.d have the following permissions as this example: -rw-r--r-- 1 root root 189 Oct 25 21:50 google-chrome.list $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.96.24.17 Candidate: 0.96.24.17 Version table: *** 0.96.24.17 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 26 22:45:09 2017 InstallationDate: Installed on 2017-10-26 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark" PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1727908/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807138] Re: [ALC256 - Razer Blade 15 2018] Headphones not automatically detected
** Summary changed: - [ALC256 - HDA-Intel - HDA Intel PCH, playback] Headphones not automatically detected + [ALC256 - Razer Blade 15 2018] Headphones not automatically detected -- 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/1807138 Title: [ALC256 - Razer Blade 15 2018] Headphones not automatically detected Status in alsa-driver package in Ubuntu: Incomplete Bug description: Running the command alsamixer allows me to manually increase the sound levels for the headset, and sound plays properly through them. This requires me to disable the auto-mute feature. I haven't rebooted my system yet to see if this is permanent. But the UI doesn't show the heaphones at all and only sends sound through the main speakers of the laptop. ➜ ~ lspci -nnk | grep -i -A7 audio 00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a348] (rev 10) Subsystem: Razer USA Ltd. Device [1a58:2001] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a323] (rev 10) Subsystem: Razer USA Ltd. Device [1a58:2001] Kernel driver in use: i801_smbus Kernel modules: i2c_i801 ➜ ~ cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC256 Codec: Intel Kabylake HDMI Using for example pavucontrol allows me to select the headphone, which are marked as unplugged, and I can play audio through them as long as I keep the application open. If I reboot or close pavucontrol, everything is back to the original state and only the speakers work. Additional Information: ➜ ~ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 What I expect to happen: When I plug in my headphones, Ubuntu and the UI should see them and automatically redirect all sound through them. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: olivar 8320 F...m pulseaudio /dev/snd/controlC0: olivar 8320 F pulseaudio CurrentDesktop: X-Cinnamon Date: Thu Dec 6 13:02:14 2018 InstallationDate: Installed on 2018-11-21 (15 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: Razer dmi.bios.version: 01.01 dmi.board.name: DANA_MB dmi.board.vendor: Razer dmi.chassis.type: 10 dmi.chassis.vendor: Razer dmi.modalias: dmi:bvnRazer:bvr01.01:bd08/31/2018:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr: dmi.product.family: 1A582001 Razer Blade dmi.product.name: Blade dmi.product.version: 1.04 dmi.sys.vendor: Razer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1807138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1803534] Re: Backport uuid based cache file naming scheme
The CPU regression looks similar to https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=909818#90 which has been fixed in https://gitlab.freedesktop.org/fontconfig/fontconfig/commit/5f12f564 , we should probably backport that one ** Bug watch added: Debian Bug tracker #909818 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909818 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1803534 Title: Backport uuid based cache file naming scheme Status in fontconfig package in Ubuntu: New Status in fontconfig source package in Bionic: Fix Committed Bug description: Fontconfig 2.13.0 changed the cache file naming scheme to be based on the contents of ".uuid" file in the directory rather than a hash of the directory name. On a pure debs system this doesn't really matter since everything is using the same libfontconfig.so. When snaps are involved, it can lead to some apps not seeing the cache files produced by a different fontconfig version. In particular, while libfontconfig 2.13 can reuse 2.12's cache files for read only directories, the reverse is not true. This will be a problem for apps built on top of the "core18" base snap when run on later Ubuntu releases (cosmic, disco, etc). By providing a backport of the UUID cache file feature to bionic for use by snap applications, we'd avoid this. Having it in bionic- updates would be ideal so that snapcraft picks it up automatically. [Impact] * This update changes how fontconfig cache files are named, instead of using md5($dir), it instead uses the contents of a $dir/.uuid file. No changes are made to the format of the cache file contents. * This change is primarily intended for use by snap applications built with core18: as the updated libfontconfig will fall back to the md5 cache file names for read-only directories without a .uuid file, they will be able to reuse cache files from any host system running fontconfig >= 2.11.95 [Test Case] * After installing the update, cache files should be generated in /var/cache/fontconfig/ with names like "07b67f7a-16ea-4440-9b6c- 21fc9153568c-le64.cache-7" (note the extra dashes not present in the MD5 based cache file names). [Regression Potential] * Applications using a non-default libfontconfig could end up not finding the new cache files and regenerating them in ~/.cache/fontconfig. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1803534/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1803534] Re: Backport uuid based cache file naming scheme
** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-failed verification-failed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1803534 Title: Backport uuid based cache file naming scheme Status in fontconfig package in Ubuntu: New Status in fontconfig source package in Bionic: Fix Committed Bug description: Fontconfig 2.13.0 changed the cache file naming scheme to be based on the contents of ".uuid" file in the directory rather than a hash of the directory name. On a pure debs system this doesn't really matter since everything is using the same libfontconfig.so. When snaps are involved, it can lead to some apps not seeing the cache files produced by a different fontconfig version. In particular, while libfontconfig 2.13 can reuse 2.12's cache files for read only directories, the reverse is not true. This will be a problem for apps built on top of the "core18" base snap when run on later Ubuntu releases (cosmic, disco, etc). By providing a backport of the UUID cache file feature to bionic for use by snap applications, we'd avoid this. Having it in bionic- updates would be ideal so that snapcraft picks it up automatically. [Impact] * This update changes how fontconfig cache files are named, instead of using md5($dir), it instead uses the contents of a $dir/.uuid file. No changes are made to the format of the cache file contents. * This change is primarily intended for use by snap applications built with core18: as the updated libfontconfig will fall back to the md5 cache file names for read-only directories without a .uuid file, they will be able to reuse cache files from any host system running fontconfig >= 2.11.95 [Test Case] * After installing the update, cache files should be generated in /var/cache/fontconfig/ with names like "07b67f7a-16ea-4440-9b6c- 21fc9153568c-le64.cache-7" (note the extra dashes not present in the MD5 based cache file names). [Regression Potential] * Applications using a non-default libfontconfig could end up not finding the new cache files and regenerating them in ~/.cache/fontconfig. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1803534/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1785778] Re: Hash Sum mismatch Ubuntu Server 18.04.1 LTS
Even by downloading the file and checking HASH and MD5sum. It's different than it should be. Can you please tell me how to what to ask for ISP if they are mangling the traffic. HASH file downloaded and check for SHA256 checksum. Get:15 http://archive.ubuntu.com/ubuntu bionic/multiverse amd64 Packages [151 kB] Get:16 http://archive.ubuntu.com/ubuntu bionic/multiverse Translation-en [108 kB] Get:17 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [454 kB] Get:18 http://archive.ubuntu.com/ubuntu bionic-updates/main Translation-en [169 kB] Get:19 http://archive.ubuntu.com/ubuntu bionic-updates/restricted amd64 Packages [6,992 B] Get:20 http://archive.ubuntu.com/ubuntu bionic-updates/restricted Translation-en [3,076 B] Get:21 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [592 kB] Err:21 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages Hash Sum mismatch Hashes of expected file: - Filesize:592272 [weak] - SHA256:4d0d8e9333b6ffbd2f40ad77155823f8bc231b7a363c5fc901172a53819248b8 - SHA1:e1db814ef58855914af89e6a64a29d14ee43b280 [weak] - MD5Sum:a6799ae06b4e4a977bc6ef98d1a64758 [weak] Hashes of received file: - SHA256:65b8bf8f415626588cd41c899159d8d3fff7a0b2d6deaf122f2066b9f5667f2d - SHA1:faade6528307e867d378a4faccc955627b6529d5 [weak] - MD5Sum:5dccc9ef9d9a1189787ace009a0ab8d0 [weak] - Filesize:592272 [weak] Last modification reported: Fri, 07 Dec 2018 12:40:08 + Release file created at: Fri, 07 Dec 2018 13:10:55 + Get:22 http://archive.ubuntu.com/ubuntu bionic-updates/universe Translation-en [165 kB] Get:23 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 Packages [6,372 B] Get:24 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse Translation-en [3,356 B] Get:25 http://archive.ubuntu.com/ubuntu bionic-backports/universe amd64 Packages [3,468 B] Get:26 http://archive.ubuntu.com/ubuntu bionic-backports/universe Translation-en [1,604 B] Get:27 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages [218 kB] Get:28 http://archive.ubuntu.com/ubuntu bionic-security/main Translation-en [84.0 kB] Get:29 http://archive.ubuntu.com/ubuntu bionic-security/universe amd64 Packages [106 kB] Get:30 http://archive.ubuntu.com/ubuntu bionic-security/universe Translation-en [60.3 kB] Get:31 http://archive.ubuntu.com/ubuntu bionic-security/multiverse amd64 Packages [1,440 B] Get:32 http://archive.ubuntu.com/ubuntu bionic-security/multiverse Translation-en [996 B] Fetched 17.7 MB in 15s (1,162 kB/s) Reading package lists... Done E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-updates/universe/binary-amd64/by-hash/SHA256/4d0d8e9333b6ffbd2f40ad77155823f8bc231b7a363c5fc901172a53819248b8 Hash Sum mismatch Hashes of expected file: - Filesize:592272 [weak] - SHA256:4d0d8e9333b6ffbd2f40ad77155823f8bc231b7a363c5fc901172a53819248b8 - SHA1:e1db814ef58855914af89e6a64a29d14ee43b280 [weak] - MD5Sum:a6799ae06b4e4a977bc6ef98d1a64758 [weak] Hashes of received file: - SHA256:65b8bf8f415626588cd41c899159d8d3fff7a0b2d6deaf122f2066b9f5667f2d - SHA1:faade6528307e867d378a4faccc955627b6529d5 [weak] - MD5Sum:5dccc9ef9d9a1189787ace009a0ab8d0 [weak] - Filesize:592272 [weak] Last modification reported: Fri, 07 Dec 2018 12:40:08 + Release file created at: Fri, 07 Dec 2018 13:10:55 + E: Some index files failed to download. They have been ignored, or old ones used instead. ** Attachment added: "Hash sum mismatch" https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1785778/+attachment/5220107/+files/manual%20hash%20check.jpg -- 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/1785778 Title: Hash Sum mismatch Ubuntu Server 18.04.1 LTS Status in apt package in Ubuntu: Invalid Bug description: Hi, I'm getting weird Hashes mismatch error while trying to update Ubuntu server 18.04.1 LTS server. The error I'm receiving is as follows. $ sudo apt-get update Get:1 http://security.ubuntu.com/ubuntu bionic-security InRelease [83.2 kB] Hit:2 http://archive.ubuntu.com/ubuntu bionic InRelease Hit:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease Get:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB] Get:5 http://archive.ubuntu.com/ubuntu bionic-updates/universe Sources [52.2 kB] Get:6 http://archive.ubuntu.com/ubuntu bionic-updates/main Sources [152 kB] Get:7 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse Sources [2,676 B] Get:8 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [277 kB] Get:9 http://archive.ubuntu.com/ubuntu bionic-updates/main Translation-en [105 kB] Get:10 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [157 kB] Err:10 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packag
[Touch-packages] [Bug 1803534] Re: Backport uuid based cache file naming scheme
I installed 'fontconfig' from proposed and the package installation failed on that error 'fc-cache: symbol lookup error: fc-cache: undefined symbol: FcDirCacheCreateUUID' It looks like the fontconfig binary should depends on the new version of the lib and doesn't? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1803534 Title: Backport uuid based cache file naming scheme Status in fontconfig package in Ubuntu: New Status in fontconfig source package in Bionic: Fix Committed Bug description: Fontconfig 2.13.0 changed the cache file naming scheme to be based on the contents of ".uuid" file in the directory rather than a hash of the directory name. On a pure debs system this doesn't really matter since everything is using the same libfontconfig.so. When snaps are involved, it can lead to some apps not seeing the cache files produced by a different fontconfig version. In particular, while libfontconfig 2.13 can reuse 2.12's cache files for read only directories, the reverse is not true. This will be a problem for apps built on top of the "core18" base snap when run on later Ubuntu releases (cosmic, disco, etc). By providing a backport of the UUID cache file feature to bionic for use by snap applications, we'd avoid this. Having it in bionic- updates would be ideal so that snapcraft picks it up automatically. [Impact] * This update changes how fontconfig cache files are named, instead of using md5($dir), it instead uses the contents of a $dir/.uuid file. No changes are made to the format of the cache file contents. * This change is primarily intended for use by snap applications built with core18: as the updated libfontconfig will fall back to the md5 cache file names for read-only directories without a .uuid file, they will be able to reuse cache files from any host system running fontconfig >= 2.11.95 [Test Case] * After installing the update, cache files should be generated in /var/cache/fontconfig/ with names like "07b67f7a-16ea-4440-9b6c- 21fc9153568c-le64.cache-7" (note the extra dashes not present in the MD5 based cache file names). [Regression Potential] * Applications using a non-default libfontconfig could end up not finding the new cache files and regenerating them in ~/.cache/fontconfig. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1803534/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)
The ca-certificates fix for Xenial and Trusty
include the changes to build the (new) udeb.
The normal deb package has been verified for
regressions (next comments) and it is correct,
with no functional changes whatsoever.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1807023
Title:
installer stock images fail to validate any HTTPS certificates (ca-
certificates missing)
Status in debian-installer:
Unknown
Status in ca-certificates package in Ubuntu:
In Progress
Status in debian-installer package in Ubuntu:
In Progress
Status in ca-certificates source package in Trusty:
New
Status in debian-installer source package in Trusty:
New
Status in ca-certificates source package in Xenial:
New
Status in debian-installer source package in Xenial:
New
Status in ca-certificates source package in Bionic:
In Progress
Status in debian-installer source package in Bionic:
In Progress
Status in ca-certificates source package in Cosmic:
In Progress
Status in debian-installer source package in Cosmic:
In Progress
Status in ca-certificates source package in Disco:
In Progress
Status in debian-installer source package in Disco:
In Progress
Status in debian-installer package in Debian:
Fix Released
Bug description:
[Impact]
* The installer stock images fail to validate any HTTPS
certificates because ca-certificates is not available
in the installer environment.
* This causes wget/download errors for preseed files on
HTTPS servers (or HTTP servers that redirect to HTTPS,
which are increasingly common nowadays - e.g., GitHub)
and theoretically any other files that are downloaded
with d-i-utils/fetch-url/wget.
* The fix is to ship ca-certificates-udeb in installer
stock images.
* Debian already ships ca-certificate-udeb in the stock
installer images; the fix is applied since Jan 2017.
(reference: Debian Bug #842040 / d-i commit 2f00c51a [1])
[Test Case]
* In the installer shell:
~ # wget http://github.com # or https://github.com
- FAIL if ca-certificates-udeb is missing:
"ERROR: cannot verify github.com's certificate, <...>'
- PASS if ca-certificates-udeb is available
"Saving to: 'index.html'"
* Test steps with virt-install and netboot images
are provided in the comments, for each release.
[Regression Potential]
* Low. This just adds the ca-certificates files in
/etc/ssl/certs and symlink in /usr/lib/ssl/certs,
so only tools looking for that would be affected.
* Apparently only wget checks for/uses those files,
and the difference in behavior is download errors
no longer occur.
[Notes]
* The ca-certificates-udeb is not currently present
in the Ubuntu 'main' component, but in 'universe',
despite the normal deb being in 'main'.
However, when rebuilding in a PPA it goes into
'main' accordingly, and can be used by default
by debian-installer (otherwise, UDEB_COMPONENTS
has to be modified to include universe/d-i).
* So this fix includes a no-change-rebuild for the
ca-certificates package, in order to publish the
udeb in the archive (at least in PPA for testing).
Hopefully that can be sorted out for this fix
to work out.
* The ca-certificates and debian-installer builds
have been done in a PPA using all architectures,
and testing has been done with the amd64 images.
* This fix is requested for Bionic, Cosmic, Disco
at least.
* The fix for Trusty and Xenial needed a little
bit more work to build/ship the (new) udeb.
(reference: Debian Bug #845456 / ca-certificates commit 3acb3a90 [2])
It would be good to have them too if at all possible.
[1]
https://salsa.debian.org/installer-team/debian-installer/commit/2f00c51a7ead982ae1cd71bee06c8416890196b6
[2]
https://salsa.debian.org/debian/ca-certificates/commit/3acb3a9042a00307ba35d10052d81cdc206c34a4
[Debugging]
For debugging purposes, one can install strace-udeb in the installer
to verify wget's stat() calls to /usr/lib/ssl/certs.
~ # anna-install strace-udeb
~ # strace -e stat wget -O- https://github.com >/dev/null
...
Resolving github.com... stat("/etc/resolv.conf", {st_mode=S_IFREG|0644,
st_size=20, ...}) = 0
140.82.118.3, 140.82.118.4
Connecting to github.com|140.82.118.3|:443... connected.
stat("/usr/lib/ssl/certs/45bfefc3.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
ERROR: cannot verify github.com's certificate, issued by 'CN=DigiCert SHA2
Extended Validation Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US':
Unable to locally verify t
[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)
Package Contents :: Xenial
==
No regressions in ca-certificate DEB file
after the changes to build the UDEB file.
The only difference is due to the changes
in changelog file and package version.
dpkg-deb -c (content listing)
---
$ dpkg-deb -c ca-certificates_20170717~16.04.2_all.deb | sed
's/[0-9][0-9]:[0-9][0-9]/HH:MM/' > dpkg-deb_-c.new
$ dpkg-deb -c ca-certificates_20170717~16.04.1_all.deb | sed
's/[0-9][0-9]:[0-9][0-9]/HH:MM/' > dpkg-deb_-c.old
$ diff dpkg-deb_-c.{old,new}
14c14
< -rw-r--r-- root/root 12885 2017-09-27 HH:MM
./usr/share/doc/ca-certificates/changelog.gz
---
> -rw-r--r-- root/root 12948 2018-12-06 HH:MM
> ./usr/share/doc/ca-certificates/changelog.gz
dpkg-deb -x (content files)
---
$ dpkg-deb -x ca-certificates_20170717~16.04.1_all.deb dpkg-deb_-x.old
$ dpkg-deb -x ca-certificates_20170717~16.04.2_all.deb dpkg-deb_-x.new
$ diff -r dpkg-deb_-x.{old,new}
Binary files dpkg-deb_-x.old/usr/share/doc/ca-certificates/changelog.gz and
dpkg-deb_-x.new/usr/share/doc/ca-certificates/changelog.gz differ
dpkg-deb -e (control files)
---
$ dpkg-deb -e ca-certificates_20170717~16.04.2_all.deb dpkg-deb_-e.new
$ dpkg-deb -e ca-certificates_20170717~16.04.1_all.deb dpkg-deb_-e.old
$ diff -r dpkg-deb_-e.{old,new}
diff -r dpkg-deb_-e.old/control dpkg-deb_-e.new/control
2c2
< Version: 20170717~16.04.1
---
> Version: 20170717~16.04.2
diff -r dpkg-deb_-e.old/md5sums dpkg-deb_-e.new/md5sums
151c151
< fc0ff87421a0735d09e88bdf444dc760 usr/share/doc/ca-certificates/changelog.gz
---
> 5596056c49179e32312e93f4c7296987 usr/share/doc/ca-certificates/changelog.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1807023
Title:
installer stock images fail to validate any HTTPS certificates (ca-
certificates missing)
Status in debian-installer:
Unknown
Status in ca-certificates package in Ubuntu:
In Progress
Status in debian-installer package in Ubuntu:
In Progress
Status in ca-certificates source package in Trusty:
New
Status in debian-installer source package in Trusty:
New
Status in ca-certificates source package in Xenial:
New
Status in debian-installer source package in Xenial:
New
Status in ca-certificates source package in Bionic:
In Progress
Status in debian-installer source package in Bionic:
In Progress
Status in ca-certificates source package in Cosmic:
In Progress
Status in debian-installer source package in Cosmic:
In Progress
Status in ca-certificates source package in Disco:
In Progress
Status in debian-installer source package in Disco:
In Progress
Status in debian-installer package in Debian:
Fix Released
Bug description:
[Impact]
* The installer stock images fail to validate any HTTPS
certificates because ca-certificates is not available
in the installer environment.
* This causes wget/download errors for preseed files on
HTTPS servers (or HTTP servers that redirect to HTTPS,
which are increasingly common nowadays - e.g., GitHub)
and theoretically any other files that are downloaded
with d-i-utils/fetch-url/wget.
* The fix is to ship ca-certificates-udeb in installer
stock images.
* Debian already ships ca-certificate-udeb in the stock
installer images; the fix is applied since Jan 2017.
(reference: Debian Bug #842040 / d-i commit 2f00c51a [1])
[Test Case]
* In the installer shell:
~ # wget http://github.com # or https://github.com
- FAIL if ca-certificates-udeb is missing:
"ERROR: cannot verify github.com's certificate, <...>'
- PASS if ca-certificates-udeb is available
"Saving to: 'index.html'"
* Test steps with virt-install and netboot images
are provided in the comments, for each release.
[Regression Potential]
* Low. This just adds the ca-certificates files in
/etc/ssl/certs and symlink in /usr/lib/ssl/certs,
so only tools looking for that would be affected.
* Apparently only wget checks for/uses those files,
and the difference in behavior is download errors
no longer occur.
[Notes]
* The ca-certificates-udeb is not currently present
in the Ubuntu 'main' component, but in 'universe',
despite the normal deb being in 'main'.
However, when rebuilding in a PPA it goes into
'main' accordingly, and can be used by default
by debian-installer (otherwise, UDEB_COMPONENTS
has to be modified to include universe/d-i).
* So this fix includes a no-change-rebuild for the
ca-certificates package, in order to publish the
udeb in the archive (at least in PPA for testing).
Hopefully that can be sorted out for this fix
to work out.
* The ca-certificates and debian-installer builds
have been done in a PPA using all architectures,
and testing has been done with the amd6
[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)
Package Contents :: Trusty
==
No regressions in ca-certificate DEB file
after the changes to build the UDEB file.
The only difference is due to the changes
in changelog file and package version.
dpkg-deb -c (content listing)
---
$ dpkg-deb -c ca-certificates_20170717~14.04.1_all.deb | sed
's/[0-9][0-9]:[0-9][0-9]/HH:MM/' > dpkg-deb_-c.old
$ dpkg-deb -c ca-certificates_20170717~14.04.2_all.deb | sed
's/[0-9][0-9]:[0-9][0-9]/HH:MM/' > dpkg-deb_-c.new
$ diff dpkg-deb_-c.{old,new}
14c14
< -rw-r--r-- root/root 11052 2018-12-06 HH:MM
./usr/share/doc/ca-certificates/changelog.gz
---
> -rw-r--r-- root/root 11108 2018-12-06 HH:MM
> ./usr/share/doc/ca-certificates/changelog.gz
dpkg-deb -x (content files)
---
$ dpkg-deb -x ca-certificates_20170717~14.04.1_all.deb dpkg-deb_-x.old
$ dpkg-deb -x ca-certificates_20170717~14.04.2_all.deb dpkg-deb_-x.new
$ diff -r dpkg-deb_-x.{old,new}
Binary files dpkg-deb_-x.old/usr/share/doc/ca-certificates/changelog.gz and
dpkg-deb_-x.new/usr/share/doc/ca-certificates/changelog.gz differ
dpkg-deb -e (control files)
---
$ dpkg-deb -e ca-certificates_20170717~14.04.1_all.deb dpkg-deb_-e.old
$ dpkg-deb -e ca-certificates_20170717~14.04.2_all.deb dpkg-deb_-e.new
$ diff -r dpkg-deb_-e.{old,new}
diff -r dpkg-deb_-e.old/control dpkg-deb_-e.new/control
2c2
< Version: 20170717~14.04.1
---
> Version: 20170717~14.04.2
diff -r dpkg-deb_-e.old/md5sums dpkg-deb_-e.new/md5sums
151c151
< c410ab88c14eab543d0c57f08b104895 usr/share/doc/ca-certificates/changelog.gz
---
> da9525233e9c26a1b101bd9be04280d0 usr/share/doc/ca-certificates/changelog.gz
** Description changed:
[Impact]
* The installer stock images fail to validate any HTTPS
certificates because ca-certificates is not available
in the installer environment.
* This causes wget/download errors for preseed files on
HTTPS servers (or HTTP servers that redirect to HTTPS,
which are increasingly common nowadays - e.g., GitHub)
and theoretically any other files that are downloaded
with d-i-utils/fetch-url/wget.
* The fix is to ship ca-certificates-udeb in installer
stock images.
* Debian already ships ca-certificate-udeb in the stock
installer images; the fix is applied since Jan 2017.
(reference: Debian Bug #842040 / d-i commit 2f00c51a [1])
[Test Case]
* In the installer shell:
~ # wget http://github.com # or https://github.com
- FAIL if ca-certificates-udeb is missing:
"ERROR: cannot verify github.com's certificate, <...>'
- PASS if ca-certificates-udeb is available
"Saving to: 'index.html'"
* Test steps with virt-install and netboot images
are provided in the comments, for each release.
[Regression Potential]
* Low. This just adds the ca-certificates files in
/etc/ssl/certs and symlink in /usr/lib/ssl/certs,
so only tools looking for that would be affected.
* Apparently only wget checks for/uses those files,
and the difference in behavior is download errors
no longer occur.
[Notes]
* The ca-certificates-udeb is not currently present
in the Ubuntu 'main' component, but in 'universe',
-despite the normal deb being in 'main'.
+ despite the normal deb being in 'main'.
-However, when rebuilding in a PPA it goes into
-'main' accordingly, and can be used by default
-by debian-installer (otherwise, UDEB_COMPONENTS
-has to be modified to include universe/d-i).
+ However, when rebuilding in a PPA it goes into
+ 'main' accordingly, and can be used by default
+ by debian-installer (otherwise, UDEB_COMPONENTS
+ has to be modified to include universe/d-i).
* So this fix includes a no-change-rebuild for the
ca-certificates package, in order to publish the
udeb in the archive (at least in PPA for testing).
-Hopefully that can be sorted out for this fix
-to work out.
+ Hopefully that can be sorted out for this fix
+ to work out.
* The ca-certificates and debian-installer builds
have been done in a PPA using all architectures,
and testing has been done with the amd64 images.
- * This fix is request for Bionic, Cosmic, Disco.
+ * This fix is requested for Bionic, Cosmic, Disco
+at least.
- The fix for Trusty and Xenial needed a little
-bit more work to build/ship the (new) udeb.
+ * The fix for Trusty and Xenial needed a little
+ bit more work to build/ship the (new) udeb.
+(reference: Debian Bug #845456 / ca-certificates commit 3acb3a90 [2])
It would be good to have them too if at all possible.
- [1] https://salsa.debian.org/installer-team/debian-
- installer/commit/2f00c51a7ead982ae1cd71bee06c8416890196b6
+ [1]
https://salsa.debian.org/installer-team/debian-installer/commit/2f00c51a7ead982ae1cd71bee06c8416890196b6
+ [2]
https://salsa.debian.org/debian/ca-certificates/commit/3acb3a90
[Touch-packages] [Bug 1807262] Re: stein unit tests fail with sqlalchemy.exc.NoSuchTableError: migration_tmp
Christian, thanks for all the digging! I just ran a successful test against sqlite 3.26.0-2 package rebuilt with 2defce45c5670e0258374eeb2e293fcf6f82bddd reverted. That's the only change I made and it seems to resolve the issue. Now to figure out if that patch is fine and we really need to update PRAGMAs to enable legacy usage or if there is a bug upstream. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/1807262 Title: stein unit tests fail with sqlalchemy.exc.NoSuchTableError: migration_tmp Status in cinder package in Ubuntu: Triaged Status in nova package in Ubuntu: Triaged Status in sqlite3 package in Ubuntu: New Bug description: Several tests that use sqlite fail with: "sqlalchemy.exc.NoSuchTableError: migration_tmp". I'm currently hitting this with nova and cinder packages in disco. Note this started sometime after 11/19 when nova 2:19.0.0~b1~git2018111953.3e756ff674-0ubuntu1 was uploaded (and built successfully at the time). After doing some digging this appears to occur with libsqlite3-0 3.26.0-1 but does not occur with libsqlite3-0 3.25.3-1. Here are some more details on that, shown by running a failing unit test from the cinder package: https://paste.ubuntu.com/p/hsnQFQD572/ Update: The test in the paste above also works successfully with libsqlite3-0 3.25.3-2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1807262/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)
** Description changed:
[Impact]
* The installer stock images fail to validate any HTTPS
certificates because ca-certificates is not available
in the installer environment.
* This causes wget/download errors for preseed files on
HTTPS servers (or HTTP servers that redirect to HTTPS,
which are increasingly common nowadays - e.g., GitHub)
and theoretically any other files that are downloaded
with d-i-utils/fetch-url/wget.
* The fix is to ship ca-certificates-udeb in installer
stock images.
* Debian already ships ca-certificate-udeb in the stock
installer images; the fix is applied since Jan 2017.
(reference: Debian Bug #842040 / d-i commit 2f00c51a [1])
[Test Case]
* In the installer shell:
~ # wget http://github.com # or https://github.com
- FAIL if ca-certificates-udeb is missing:
"ERROR: cannot verify github.com's certificate, <...>'
- PASS if ca-certificates-udeb is available
"Saving to: 'index.html'"
* Test steps with virt-install and netboot images
are provided in the comments, for each release.
[Regression Potential]
* Low. This just adds the ca-certificates files in
/etc/ssl/certs and symlink in /usr/lib/ssl/certs,
so only tools looking for that would be affected.
* Apparently only wget checks for/uses those files,
and the difference in behavior is download errors
no longer occur.
[Notes]
* The ca-certificates-udeb is not currently present
- in the Ubuntu archive despite being available for
- download in Launchpad with a link for some reason
- (perhaps a problem during import from Debian/sid?)
+ in the Ubuntu 'main' component, but in 'universe',
+despite the normal deb being in 'main'.
+
+However, when rebuilding in a PPA it goes into
+'main' accordingly, and can be used by default
+by debian-installer (otherwise, UDEB_COMPONENTS
+has to be modified to include universe/d-i).
* So this fix includes a no-change-rebuild for the
ca-certificates package, in order to publish the
- udeb in the archive.
+ udeb in the archive (at least in PPA for testing).
+
+Hopefully that can be sorted out for this fix
+to work out.
* The ca-certificates and debian-installer builds
have been done in a PPA using all architectures,
and testing has been done with the amd64 images.
* This fix is request for Bionic, Cosmic, Disco.
- The older releases (Trusty, Xenial) are affected,
- but not requested for, and would need more work,
- as the udeb is not yet in the packaging but that
- is doable if required for the process.
+ The fix for Trusty and Xenial needed a little
+bit more work to build/ship the (new) udeb.
+
+ It would be good to have them too if at all possible.
[1] https://salsa.debian.org/installer-team/debian-
installer/commit/2f00c51a7ead982ae1cd71bee06c8416890196b6
[Debugging]
For debugging purposes, one can install strace-udeb in the installer to
verify wget's stat() calls to /usr/lib/ssl/certs.
~ # anna-install strace-udeb
~ # strace -e stat wget -O- https://github.com >/dev/null
...
Resolving github.com... stat("/etc/resolv.conf", {st_mode=S_IFREG|0644,
st_size=20, ...}) = 0
140.82.118.3, 140.82.118.4
Connecting to github.com|140.82.118.3|:443... connected.
stat("/usr/lib/ssl/certs/45bfefc3.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
ERROR: cannot verify github.com's certificate, issued by 'CN=DigiCert SHA2
Extended Validation Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US':
Unable to locally verify the issuer's authority.
To connect to github.com insecurely, use `--no-check-certificate'.
+++ exited with 5 +++
~ #
~ # anna-install ca-certificates-udeb # not in archive yet.
unknown udeb ca-certificates-udeb
~ # wget --no-check-certificate
https://launchpad.net/ubuntu/+archive/primary/+files/ca-certificates-
udeb_20180409_all.udeb
~ # udpkg -i ca-certificates-udeb_20180409_all.udeb
~ # strace -e stat wget -O- https://github.com >/dev/null
...
Resolving github.com... stat("/etc/resolv.conf", {st_mode=S_IFREG|0644,
st_size=20, ...}) = 0
140.82.118.3, 140.82.118.4
Connecting to github.com|140.82.118.3|:443... connected.
stat("/usr/lib/ssl/certs/45bfefc3.0", 0x7fffbb9431c0) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", {st_mode=S_IFREG|0644, st_size=1367,
...}) = 0
stat("/usr/lib/ssl/certs/244b5494.1", 0x7fffbb9431c0) = -1 ENOENT (No such
file or directory)
HTTP request sent, awaiting response... 200 OK
stat("-", 0x7fffbb943558) = -1 ENOENT (No such file or
directory)
Length: un
[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)
** Patch added: "lp1807023-debian-installer-xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1807023/+attachment/5220102/+files/lp1807023-debian-installer-xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1807023
Title:
installer stock images fail to validate any HTTPS certificates (ca-
certificates missing)
Status in debian-installer:
Unknown
Status in ca-certificates package in Ubuntu:
In Progress
Status in debian-installer package in Ubuntu:
In Progress
Status in ca-certificates source package in Trusty:
New
Status in debian-installer source package in Trusty:
New
Status in ca-certificates source package in Xenial:
New
Status in debian-installer source package in Xenial:
New
Status in ca-certificates source package in Bionic:
In Progress
Status in debian-installer source package in Bionic:
In Progress
Status in ca-certificates source package in Cosmic:
In Progress
Status in debian-installer source package in Cosmic:
In Progress
Status in ca-certificates source package in Disco:
In Progress
Status in debian-installer source package in Disco:
In Progress
Status in debian-installer package in Debian:
Fix Released
Bug description:
[Impact]
* The installer stock images fail to validate any HTTPS
certificates because ca-certificates is not available
in the installer environment.
* This causes wget/download errors for preseed files on
HTTPS servers (or HTTP servers that redirect to HTTPS,
which are increasingly common nowadays - e.g., GitHub)
and theoretically any other files that are downloaded
with d-i-utils/fetch-url/wget.
* The fix is to ship ca-certificates-udeb in installer
stock images.
* Debian already ships ca-certificate-udeb in the stock
installer images; the fix is applied since Jan 2017.
(reference: Debian Bug #842040 / d-i commit 2f00c51a [1])
[Test Case]
* In the installer shell:
~ # wget http://github.com # or https://github.com
- FAIL if ca-certificates-udeb is missing:
"ERROR: cannot verify github.com's certificate, <...>'
- PASS if ca-certificates-udeb is available
"Saving to: 'index.html'"
* Test steps with virt-install and netboot images
are provided in the comments, for each release.
[Regression Potential]
* Low. This just adds the ca-certificates files in
/etc/ssl/certs and symlink in /usr/lib/ssl/certs,
so only tools looking for that would be affected.
* Apparently only wget checks for/uses those files,
and the difference in behavior is download errors
no longer occur.
[Notes]
* The ca-certificates-udeb is not currently present
in the Ubuntu archive despite being available for
download in Launchpad with a link for some reason
(perhaps a problem during import from Debian/sid?)
* So this fix includes a no-change-rebuild for the
ca-certificates package, in order to publish the
udeb in the archive.
* The ca-certificates and debian-installer builds
have been done in a PPA using all architectures,
and testing has been done with the amd64 images.
* This fix is request for Bionic, Cosmic, Disco.
The older releases (Trusty, Xenial) are affected,
but not requested for, and would need more work,
as the udeb is not yet in the packaging but that
is doable if required for the process.
[1] https://salsa.debian.org/installer-team/debian-
installer/commit/2f00c51a7ead982ae1cd71bee06c8416890196b6
[Debugging]
For debugging purposes, one can install strace-udeb in the installer
to verify wget's stat() calls to /usr/lib/ssl/certs.
~ # anna-install strace-udeb
~ # strace -e stat wget -O- https://github.com >/dev/null
...
Resolving github.com... stat("/etc/resolv.conf", {st_mode=S_IFREG|0644,
st_size=20, ...}) = 0
140.82.118.3, 140.82.118.4
Connecting to github.com|140.82.118.3|:443... connected.
stat("/usr/lib/ssl/certs/45bfefc3.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
ERROR: cannot verify github.com's certificate, issued by 'CN=DigiCert SHA2
Extended Validation Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US':
Unable to locally verify the issuer's authority.
To connect to github.com insecurely, use `--no-check-certificate'.
+++ exited with 5 +++
~ #
~ # anna-install ca-certificates-udeb # not in archive yet.
unknown udeb ca-certificates-udeb
~ # wget --no-check-certificate
https://launchpad.net/ubuntu/+archive/primary/+files/ca-certificates-
udeb_20180409_all.udeb
~ # udpkg -i ca-certificates-udeb_20180409_all.ud
[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)
** Patch added: "lp1807023-debian-installer-trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1807023/+attachment/5220104/+files/lp1807023-debian-installer-trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1807023
Title:
installer stock images fail to validate any HTTPS certificates (ca-
certificates missing)
Status in debian-installer:
Unknown
Status in ca-certificates package in Ubuntu:
In Progress
Status in debian-installer package in Ubuntu:
In Progress
Status in ca-certificates source package in Trusty:
New
Status in debian-installer source package in Trusty:
New
Status in ca-certificates source package in Xenial:
New
Status in debian-installer source package in Xenial:
New
Status in ca-certificates source package in Bionic:
In Progress
Status in debian-installer source package in Bionic:
In Progress
Status in ca-certificates source package in Cosmic:
In Progress
Status in debian-installer source package in Cosmic:
In Progress
Status in ca-certificates source package in Disco:
In Progress
Status in debian-installer source package in Disco:
In Progress
Status in debian-installer package in Debian:
Fix Released
Bug description:
[Impact]
* The installer stock images fail to validate any HTTPS
certificates because ca-certificates is not available
in the installer environment.
* This causes wget/download errors for preseed files on
HTTPS servers (or HTTP servers that redirect to HTTPS,
which are increasingly common nowadays - e.g., GitHub)
and theoretically any other files that are downloaded
with d-i-utils/fetch-url/wget.
* The fix is to ship ca-certificates-udeb in installer
stock images.
* Debian already ships ca-certificate-udeb in the stock
installer images; the fix is applied since Jan 2017.
(reference: Debian Bug #842040 / d-i commit 2f00c51a [1])
[Test Case]
* In the installer shell:
~ # wget http://github.com # or https://github.com
- FAIL if ca-certificates-udeb is missing:
"ERROR: cannot verify github.com's certificate, <...>'
- PASS if ca-certificates-udeb is available
"Saving to: 'index.html'"
* Test steps with virt-install and netboot images
are provided in the comments, for each release.
[Regression Potential]
* Low. This just adds the ca-certificates files in
/etc/ssl/certs and symlink in /usr/lib/ssl/certs,
so only tools looking for that would be affected.
* Apparently only wget checks for/uses those files,
and the difference in behavior is download errors
no longer occur.
[Notes]
* The ca-certificates-udeb is not currently present
in the Ubuntu archive despite being available for
download in Launchpad with a link for some reason
(perhaps a problem during import from Debian/sid?)
* So this fix includes a no-change-rebuild for the
ca-certificates package, in order to publish the
udeb in the archive.
* The ca-certificates and debian-installer builds
have been done in a PPA using all architectures,
and testing has been done with the amd64 images.
* This fix is request for Bionic, Cosmic, Disco.
The older releases (Trusty, Xenial) are affected,
but not requested for, and would need more work,
as the udeb is not yet in the packaging but that
is doable if required for the process.
[1] https://salsa.debian.org/installer-team/debian-
installer/commit/2f00c51a7ead982ae1cd71bee06c8416890196b6
[Debugging]
For debugging purposes, one can install strace-udeb in the installer
to verify wget's stat() calls to /usr/lib/ssl/certs.
~ # anna-install strace-udeb
~ # strace -e stat wget -O- https://github.com >/dev/null
...
Resolving github.com... stat("/etc/resolv.conf", {st_mode=S_IFREG|0644,
st_size=20, ...}) = 0
140.82.118.3, 140.82.118.4
Connecting to github.com|140.82.118.3|:443... connected.
stat("/usr/lib/ssl/certs/45bfefc3.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
ERROR: cannot verify github.com's certificate, issued by 'CN=DigiCert SHA2
Extended Validation Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US':
Unable to locally verify the issuer's authority.
To connect to github.com insecurely, use `--no-check-certificate'.
+++ exited with 5 +++
~ #
~ # anna-install ca-certificates-udeb # not in archive yet.
unknown udeb ca-certificates-udeb
~ # wget --no-check-certificate
https://launchpad.net/ubuntu/+archive/primary/+files/ca-certificates-
udeb_20180409_all.udeb
~ # udpkg -i ca-certificates-udeb_20180409_all.ud
[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)
Testing :: Trusty
=
original
wget http://archive.ubuntu.com/ubuntu/dists/trusty-updates/main
/installer-amd64/20101020ubuntu318.44/images/netboot/ubuntu-
installer/amd64/{linux,initrd.gz}
~ # cat /etc/default-release
trusty
~ # ls -d /usr/lib/ssl/certs
ls: /usr/lib/ssl/certs: No such file or directory
~ # wget http://github.com
...
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://github.com/ [following]
...
ERROR: cannot verify github.com's certificate, issued by '/C=US/O=DigiCert
Inc/OU=www.digicert.com/CN=DigiCert SHA2 Extended Validation Server CA':
Unable to locally verify the issuer's authority.
To connect to github.com insecurely, use `--no-check-certificate'.
modified
wget http://ppa.launchpad.net/mfo/sf205192/ubuntu/dists/trusty/main
/installer-amd64/20101020ubuntu318.45/images/netboot/ubuntu-
installer/amd64/{linux,initrd.gz}
~ # cat /etc/default-release
trusty
~ # ls -d /usr/lib/ssl/certs
/usr/lib/ssl/certs
~ # wget http://github.com
...
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://github.com/ [following]
...
Saving to: 'index.html'
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1807023
Title:
installer stock images fail to validate any HTTPS certificates (ca-
certificates missing)
Status in debian-installer:
Unknown
Status in ca-certificates package in Ubuntu:
In Progress
Status in debian-installer package in Ubuntu:
In Progress
Status in ca-certificates source package in Trusty:
New
Status in debian-installer source package in Trusty:
New
Status in ca-certificates source package in Xenial:
New
Status in debian-installer source package in Xenial:
New
Status in ca-certificates source package in Bionic:
In Progress
Status in debian-installer source package in Bionic:
In Progress
Status in ca-certificates source package in Cosmic:
In Progress
Status in debian-installer source package in Cosmic:
In Progress
Status in ca-certificates source package in Disco:
In Progress
Status in debian-installer source package in Disco:
In Progress
Status in debian-installer package in Debian:
Fix Released
Bug description:
[Impact]
* The installer stock images fail to validate any HTTPS
certificates because ca-certificates is not available
in the installer environment.
* This causes wget/download errors for preseed files on
HTTPS servers (or HTTP servers that redirect to HTTPS,
which are increasingly common nowadays - e.g., GitHub)
and theoretically any other files that are downloaded
with d-i-utils/fetch-url/wget.
* The fix is to ship ca-certificates-udeb in installer
stock images.
* Debian already ships ca-certificate-udeb in the stock
installer images; the fix is applied since Jan 2017.
(reference: Debian Bug #842040 / d-i commit 2f00c51a [1])
[Test Case]
* In the installer shell:
~ # wget http://github.com # or https://github.com
- FAIL if ca-certificates-udeb is missing:
"ERROR: cannot verify github.com's certificate, <...>'
- PASS if ca-certificates-udeb is available
"Saving to: 'index.html'"
* Test steps with virt-install and netboot images
are provided in the comments, for each release.
[Regression Potential]
* Low. This just adds the ca-certificates files in
/etc/ssl/certs and symlink in /usr/lib/ssl/certs,
so only tools looking for that would be affected.
* Apparently only wget checks for/uses those files,
and the difference in behavior is download errors
no longer occur.
[Notes]
* The ca-certificates-udeb is not currently present
in the Ubuntu 'main' component, but in 'universe',
despite the normal deb being in 'main'.
However, when rebuilding in a PPA it goes into
'main' accordingly, and can be used by default
by debian-installer (otherwise, UDEB_COMPONENTS
has to be modified to include universe/d-i).
* So this fix includes a no-change-rebuild for the
ca-certificates package, in order to publish the
udeb in the archive (at least in PPA for testing).
Hopefully that can be sorted out for this fix
to work out.
* The ca-certificates and debian-installer builds
have been done in a PPA using all architectures,
and testing has been done with the amd64 images.
* This fix is request for Bionic, Cosmic, Disco.
The fix for Trusty and Xenial needed a little
bit more work to build/ship the (new) udeb.
It would be good to have them too if at all possible.
[1] https://salsa.debian.org/installer-team/debian-
installer/commit/2f00c51a7ead982ae1cd71bee06c8416890196b6
[Debugging]
For debugging purposes, one can install strace-udeb in the installer
to verify wget's stat() calls to /usr/lib/ss
[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)
Testing :: Xenial
=
original
wget http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main
/installer-amd64/20101020ubuntu451.26/images/netboot/ubuntu-
installer/amd64/{linux,initrd.gz}
~ # cat /etc/default-release
xenial
~ # ls -d /usr/lib/ssl/certs
ls: /usr/lib/ssl/certs: No such file or directory
~ # wget http://github.com
...
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://github.com/ [following]
...
ERROR: cannot verify github.com's certificate, issued by 'CN=DigiCert SHA2
Extended Validation Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US':
Unable to locally verify the issuer's authority.
To connect to github.com insecurely, use `--no-check-certificate'.
~ #
modified
wget http://ppa.launchpad.net/mfo/sf205192/ubuntu/dists/xenial/main
/installer-amd64/20101020ubuntu451.27/images/netboot/ubuntu-
installer/amd64/{linux,initrd.gz}
~ # cat /etc/default-release
xenial
~ # ls -d /usr/lib/ssl/certs
/usr/lib/ssl/certs
~ # wget http://github.com
...
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://github.com/ [following]
...
Saving to: 'index.html'
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1807023
Title:
installer stock images fail to validate any HTTPS certificates (ca-
certificates missing)
Status in debian-installer:
Unknown
Status in ca-certificates package in Ubuntu:
In Progress
Status in debian-installer package in Ubuntu:
In Progress
Status in ca-certificates source package in Trusty:
New
Status in debian-installer source package in Trusty:
New
Status in ca-certificates source package in Xenial:
New
Status in debian-installer source package in Xenial:
New
Status in ca-certificates source package in Bionic:
In Progress
Status in debian-installer source package in Bionic:
In Progress
Status in ca-certificates source package in Cosmic:
In Progress
Status in debian-installer source package in Cosmic:
In Progress
Status in ca-certificates source package in Disco:
In Progress
Status in debian-installer source package in Disco:
In Progress
Status in debian-installer package in Debian:
Fix Released
Bug description:
[Impact]
* The installer stock images fail to validate any HTTPS
certificates because ca-certificates is not available
in the installer environment.
* This causes wget/download errors for preseed files on
HTTPS servers (or HTTP servers that redirect to HTTPS,
which are increasingly common nowadays - e.g., GitHub)
and theoretically any other files that are downloaded
with d-i-utils/fetch-url/wget.
* The fix is to ship ca-certificates-udeb in installer
stock images.
* Debian already ships ca-certificate-udeb in the stock
installer images; the fix is applied since Jan 2017.
(reference: Debian Bug #842040 / d-i commit 2f00c51a [1])
[Test Case]
* In the installer shell:
~ # wget http://github.com # or https://github.com
- FAIL if ca-certificates-udeb is missing:
"ERROR: cannot verify github.com's certificate, <...>'
- PASS if ca-certificates-udeb is available
"Saving to: 'index.html'"
* Test steps with virt-install and netboot images
are provided in the comments, for each release.
[Regression Potential]
* Low. This just adds the ca-certificates files in
/etc/ssl/certs and symlink in /usr/lib/ssl/certs,
so only tools looking for that would be affected.
* Apparently only wget checks for/uses those files,
and the difference in behavior is download errors
no longer occur.
[Notes]
* The ca-certificates-udeb is not currently present
in the Ubuntu archive despite being available for
download in Launchpad with a link for some reason
(perhaps a problem during import from Debian/sid?)
* So this fix includes a no-change-rebuild for the
ca-certificates package, in order to publish the
udeb in the archive.
* The ca-certificates and debian-installer builds
have been done in a PPA using all architectures,
and testing has been done with the amd64 images.
* This fix is request for Bionic, Cosmic, Disco.
The older releases (Trusty, Xenial) are affected,
but not requested for, and would need more work,
as the udeb is not yet in the packaging but that
is doable if required for the process.
[1] https://salsa.debian.org/installer-team/debian-
installer/commit/2f00c51a7ead982ae1cd71bee06c8416890196b6
[Debugging]
For debugging purposes, one can install strace-udeb in the installer
to verify wget's stat() calls to /usr/lib/ssl/certs.
~ # anna-install strace-udeb
~ # strace -e stat wget -O- https://github.com >/dev/null
...
Resolving github.com... stat("/etc/resolv.conf", {st_mode=S_IFREG|0644,
st_size=20, ..
[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)
** Patch added: "lp1807023-ca-certificates-xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1807023/+attachment/5220101/+files/lp1807023-ca-certificates-xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1807023
Title:
installer stock images fail to validate any HTTPS certificates (ca-
certificates missing)
Status in debian-installer:
Unknown
Status in ca-certificates package in Ubuntu:
In Progress
Status in debian-installer package in Ubuntu:
In Progress
Status in ca-certificates source package in Trusty:
New
Status in debian-installer source package in Trusty:
New
Status in ca-certificates source package in Xenial:
New
Status in debian-installer source package in Xenial:
New
Status in ca-certificates source package in Bionic:
In Progress
Status in debian-installer source package in Bionic:
In Progress
Status in ca-certificates source package in Cosmic:
In Progress
Status in debian-installer source package in Cosmic:
In Progress
Status in ca-certificates source package in Disco:
In Progress
Status in debian-installer source package in Disco:
In Progress
Status in debian-installer package in Debian:
Fix Released
Bug description:
[Impact]
* The installer stock images fail to validate any HTTPS
certificates because ca-certificates is not available
in the installer environment.
* This causes wget/download errors for preseed files on
HTTPS servers (or HTTP servers that redirect to HTTPS,
which are increasingly common nowadays - e.g., GitHub)
and theoretically any other files that are downloaded
with d-i-utils/fetch-url/wget.
* The fix is to ship ca-certificates-udeb in installer
stock images.
* Debian already ships ca-certificate-udeb in the stock
installer images; the fix is applied since Jan 2017.
(reference: Debian Bug #842040 / d-i commit 2f00c51a [1])
[Test Case]
* In the installer shell:
~ # wget http://github.com # or https://github.com
- FAIL if ca-certificates-udeb is missing:
"ERROR: cannot verify github.com's certificate, <...>'
- PASS if ca-certificates-udeb is available
"Saving to: 'index.html'"
* Test steps with virt-install and netboot images
are provided in the comments, for each release.
[Regression Potential]
* Low. This just adds the ca-certificates files in
/etc/ssl/certs and symlink in /usr/lib/ssl/certs,
so only tools looking for that would be affected.
* Apparently only wget checks for/uses those files,
and the difference in behavior is download errors
no longer occur.
[Notes]
* The ca-certificates-udeb is not currently present
in the Ubuntu archive despite being available for
download in Launchpad with a link for some reason
(perhaps a problem during import from Debian/sid?)
* So this fix includes a no-change-rebuild for the
ca-certificates package, in order to publish the
udeb in the archive.
* The ca-certificates and debian-installer builds
have been done in a PPA using all architectures,
and testing has been done with the amd64 images.
* This fix is request for Bionic, Cosmic, Disco.
The older releases (Trusty, Xenial) are affected,
but not requested for, and would need more work,
as the udeb is not yet in the packaging but that
is doable if required for the process.
[1] https://salsa.debian.org/installer-team/debian-
installer/commit/2f00c51a7ead982ae1cd71bee06c8416890196b6
[Debugging]
For debugging purposes, one can install strace-udeb in the installer
to verify wget's stat() calls to /usr/lib/ssl/certs.
~ # anna-install strace-udeb
~ # strace -e stat wget -O- https://github.com >/dev/null
...
Resolving github.com... stat("/etc/resolv.conf", {st_mode=S_IFREG|0644,
st_size=20, ...}) = 0
140.82.118.3, 140.82.118.4
Connecting to github.com|140.82.118.3|:443... connected.
stat("/usr/lib/ssl/certs/45bfefc3.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
ERROR: cannot verify github.com's certificate, issued by 'CN=DigiCert SHA2
Extended Validation Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US':
Unable to locally verify the issuer's authority.
To connect to github.com insecurely, use `--no-check-certificate'.
+++ exited with 5 +++
~ #
~ # anna-install ca-certificates-udeb # not in archive yet.
unknown udeb ca-certificates-udeb
~ # wget --no-check-certificate
https://launchpad.net/ubuntu/+archive/primary/+files/ca-certificates-
udeb_20180409_all.udeb
~ # udpkg -i ca-certificates-udeb_20180409_all.udeb
[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)
** Patch added: "lp1807023-ca-certificates-trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1807023/+attachment/5220103/+files/lp1807023-ca-certificates-trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1807023
Title:
installer stock images fail to validate any HTTPS certificates (ca-
certificates missing)
Status in debian-installer:
Unknown
Status in ca-certificates package in Ubuntu:
In Progress
Status in debian-installer package in Ubuntu:
In Progress
Status in ca-certificates source package in Trusty:
New
Status in debian-installer source package in Trusty:
New
Status in ca-certificates source package in Xenial:
New
Status in debian-installer source package in Xenial:
New
Status in ca-certificates source package in Bionic:
In Progress
Status in debian-installer source package in Bionic:
In Progress
Status in ca-certificates source package in Cosmic:
In Progress
Status in debian-installer source package in Cosmic:
In Progress
Status in ca-certificates source package in Disco:
In Progress
Status in debian-installer source package in Disco:
In Progress
Status in debian-installer package in Debian:
Fix Released
Bug description:
[Impact]
* The installer stock images fail to validate any HTTPS
certificates because ca-certificates is not available
in the installer environment.
* This causes wget/download errors for preseed files on
HTTPS servers (or HTTP servers that redirect to HTTPS,
which are increasingly common nowadays - e.g., GitHub)
and theoretically any other files that are downloaded
with d-i-utils/fetch-url/wget.
* The fix is to ship ca-certificates-udeb in installer
stock images.
* Debian already ships ca-certificate-udeb in the stock
installer images; the fix is applied since Jan 2017.
(reference: Debian Bug #842040 / d-i commit 2f00c51a [1])
[Test Case]
* In the installer shell:
~ # wget http://github.com # or https://github.com
- FAIL if ca-certificates-udeb is missing:
"ERROR: cannot verify github.com's certificate, <...>'
- PASS if ca-certificates-udeb is available
"Saving to: 'index.html'"
* Test steps with virt-install and netboot images
are provided in the comments, for each release.
[Regression Potential]
* Low. This just adds the ca-certificates files in
/etc/ssl/certs and symlink in /usr/lib/ssl/certs,
so only tools looking for that would be affected.
* Apparently only wget checks for/uses those files,
and the difference in behavior is download errors
no longer occur.
[Notes]
* The ca-certificates-udeb is not currently present
in the Ubuntu archive despite being available for
download in Launchpad with a link for some reason
(perhaps a problem during import from Debian/sid?)
* So this fix includes a no-change-rebuild for the
ca-certificates package, in order to publish the
udeb in the archive.
* The ca-certificates and debian-installer builds
have been done in a PPA using all architectures,
and testing has been done with the amd64 images.
* This fix is request for Bionic, Cosmic, Disco.
The older releases (Trusty, Xenial) are affected,
but not requested for, and would need more work,
as the udeb is not yet in the packaging but that
is doable if required for the process.
[1] https://salsa.debian.org/installer-team/debian-
installer/commit/2f00c51a7ead982ae1cd71bee06c8416890196b6
[Debugging]
For debugging purposes, one can install strace-udeb in the installer
to verify wget's stat() calls to /usr/lib/ssl/certs.
~ # anna-install strace-udeb
~ # strace -e stat wget -O- https://github.com >/dev/null
...
Resolving github.com... stat("/etc/resolv.conf", {st_mode=S_IFREG|0644,
st_size=20, ...}) = 0
140.82.118.3, 140.82.118.4
Connecting to github.com|140.82.118.3|:443... connected.
stat("/usr/lib/ssl/certs/45bfefc3.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
ERROR: cannot verify github.com's certificate, issued by 'CN=DigiCert SHA2
Extended Validation Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US':
Unable to locally verify the issuer's authority.
To connect to github.com insecurely, use `--no-check-certificate'.
+++ exited with 5 +++
~ #
~ # anna-install ca-certificates-udeb # not in archive yet.
unknown udeb ca-certificates-udeb
~ # wget --no-check-certificate
https://launchpad.net/ubuntu/+archive/primary/+files/ca-certificates-
udeb_20180409_all.udeb
~ # udpkg -i ca-certificates-udeb_20180409_all.udeb
[Touch-packages] [Bug 1785778] Re: Hash Sum mismatch Ubuntu Server 18.04.1 LTS
File list has changed. Error no longer exists. Let it be noted that this error may recur. Question: Does one just need to wait for refresh of files or report it here anyway? -- 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/1785778 Title: Hash Sum mismatch Ubuntu Server 18.04.1 LTS Status in apt package in Ubuntu: Invalid Bug description: Hi, I'm getting weird Hashes mismatch error while trying to update Ubuntu server 18.04.1 LTS server. The error I'm receiving is as follows. $ sudo apt-get update Get:1 http://security.ubuntu.com/ubuntu bionic-security InRelease [83.2 kB] Hit:2 http://archive.ubuntu.com/ubuntu bionic InRelease Hit:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease Get:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB] Get:5 http://archive.ubuntu.com/ubuntu bionic-updates/universe Sources [52.2 kB] Get:6 http://archive.ubuntu.com/ubuntu bionic-updates/main Sources [152 kB] Get:7 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse Sources [2,676 B] Get:8 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [277 kB] Get:9 http://archive.ubuntu.com/ubuntu bionic-updates/main Translation-en [105 kB] Get:10 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [157 kB] Err:10 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages Hash Sum mismatch Hashes of expected file: - Filesize:157408 [weak] - SHA256:95fae016beb34455d4601a44c76d1823479178cbcdc58365750d4c039eecfb18 - SHA1:ad29965fe436d84b62331a4662e5fc679103fa0d [weak] - MD5Sum:4375646a0495b45597e06fb3e21dbd10 [weak] Hashes of received file: - SHA256:cdb9774bad7ab6f191ce597e3139f105477428fdc2509c63fcac8e5b904e4f4a - SHA1:96a041a735ddb8be1b14cc214ce0f56b486b42db [weak] - MD5Sum:a33f0341357c0be32207618a14b500db [weak] - Filesize:157408 [weak] Last modification reported: Tue, 07 Aug 2018 07:15:09 + Release file created at: Tue, 07 Aug 2018 07:15:03 + Get:11 http://archive.ubuntu.com/ubuntu bionic-updates/universe Translation-en [71.0 kB] Get:12 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 Packages [3,772 B] Get:13 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse Translation-en [2,376 B] Err:14 http://download.webmin.com/download/repository sarge InRelease Could not connect to download.webmin.com:80 (108.60.199.109), connection timed out Fetched 329 kB in 30s (10.9 kB/s) Reading package lists... Done W: Failed to fetch http://download.webmin.com/download/repository/dists/sarge/InRelease Could not connect to download.webmin.com:80 (108.60.199.109), connection timed out E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-updates/universe/binary-amd64/by-hash/SHA256/95fae016beb34455d4601a44c76d1823479178cbcdc58365750d4c039eecfb18 Hash Sum mismatch Hashes of expected file: - Filesize:157408 [weak] - SHA256:95fae016beb34455d4601a44c76d1823479178cbcdc58365750d4c039eecfb18 - SHA1:ad29965fe436d84b62331a4662e5fc679103fa0d [weak] - MD5Sum:4375646a0495b45597e06fb3e21dbd10 [weak] Hashes of received file: - SHA256:cdb9774bad7ab6f191ce597e3139f105477428fdc2509c63fcac8e5b904e4f4a - SHA1:96a041a735ddb8be1b14cc214ce0f56b486b42db [weak] - MD5Sum:a33f0341357c0be32207618a14b500db [weak] - Filesize:157408 [weak] Last modification reported: Tue, 07 Aug 2018 07:15:09 + Release file created at: Tue, 07 Aug 2018 07:15:03 + W: Some index files failed to download. They have been ignored, or old ones used instead. I have tried solution provided in search as "removing all files in /var/lib/apt/lists and update again" but it doesn't work. Don't know how to resolve it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1785778/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1785778] Re: Hash Sum mismatch Ubuntu Server 18.04.1 LTS
@Elzix: You might want to talk to your ISP, or check your hardware, as something is broken. jak@jak-t480s:~:master$ curl -s http://gb.archive.ubuntu.com/ubuntu/dists/bionic-updates/main/binary-i386/by-hash/SHA256/54181e4ce10a58ed362cac0b1a98f48989710d6697291b81e0ad7a2c9320a462 | sha256sum 54181e4ce10a58ed362cac0b1a98f48989710d6697291b81e0ad7a2c9320a462 - jak@jak-t480s:~:master$ curl -s http://us.archive.ubuntu.com/ubuntu/dists/bionic-updates/main/binary-i386/by-hash/SHA256/54181e4ce10a58ed362cac0b1a98f48989710d6697291b81e0ad7a2c9320a462 | sha256sum 54181e4ce10a58ed362cac0b1a98f48989710d6697291b81e0ad7a2c9320a462 - jak@jak-t480s:~:master$ curl -s http://archive.ubuntu.com/ubuntu/dists/bionic-updates/main/binary-i386/by-hash/SHA256/54181e4ce10a58ed362cac0b1a98f48989710d6697291b81e0ad7a2c9320a462 | sha256sum 54181e4ce10a58ed362cac0b1a98f48989710d6697291b81e0ad7a2c9320a462 - -- 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/1785778 Title: Hash Sum mismatch Ubuntu Server 18.04.1 LTS Status in apt package in Ubuntu: Invalid Bug description: Hi, I'm getting weird Hashes mismatch error while trying to update Ubuntu server 18.04.1 LTS server. The error I'm receiving is as follows. $ sudo apt-get update Get:1 http://security.ubuntu.com/ubuntu bionic-security InRelease [83.2 kB] Hit:2 http://archive.ubuntu.com/ubuntu bionic InRelease Hit:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease Get:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB] Get:5 http://archive.ubuntu.com/ubuntu bionic-updates/universe Sources [52.2 kB] Get:6 http://archive.ubuntu.com/ubuntu bionic-updates/main Sources [152 kB] Get:7 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse Sources [2,676 B] Get:8 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [277 kB] Get:9 http://archive.ubuntu.com/ubuntu bionic-updates/main Translation-en [105 kB] Get:10 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [157 kB] Err:10 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages Hash Sum mismatch Hashes of expected file: - Filesize:157408 [weak] - SHA256:95fae016beb34455d4601a44c76d1823479178cbcdc58365750d4c039eecfb18 - SHA1:ad29965fe436d84b62331a4662e5fc679103fa0d [weak] - MD5Sum:4375646a0495b45597e06fb3e21dbd10 [weak] Hashes of received file: - SHA256:cdb9774bad7ab6f191ce597e3139f105477428fdc2509c63fcac8e5b904e4f4a - SHA1:96a041a735ddb8be1b14cc214ce0f56b486b42db [weak] - MD5Sum:a33f0341357c0be32207618a14b500db [weak] - Filesize:157408 [weak] Last modification reported: Tue, 07 Aug 2018 07:15:09 + Release file created at: Tue, 07 Aug 2018 07:15:03 + Get:11 http://archive.ubuntu.com/ubuntu bionic-updates/universe Translation-en [71.0 kB] Get:12 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 Packages [3,772 B] Get:13 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse Translation-en [2,376 B] Err:14 http://download.webmin.com/download/repository sarge InRelease Could not connect to download.webmin.com:80 (108.60.199.109), connection timed out Fetched 329 kB in 30s (10.9 kB/s) Reading package lists... Done W: Failed to fetch http://download.webmin.com/download/repository/dists/sarge/InRelease Could not connect to download.webmin.com:80 (108.60.199.109), connection timed out E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-updates/universe/binary-amd64/by-hash/SHA256/95fae016beb34455d4601a44c76d1823479178cbcdc58365750d4c039eecfb18 Hash Sum mismatch Hashes of expected file: - Filesize:157408 [weak] - SHA256:95fae016beb34455d4601a44c76d1823479178cbcdc58365750d4c039eecfb18 - SHA1:ad29965fe436d84b62331a4662e5fc679103fa0d [weak] - MD5Sum:4375646a0495b45597e06fb3e21dbd10 [weak] Hashes of received file: - SHA256:cdb9774bad7ab6f191ce597e3139f105477428fdc2509c63fcac8e5b904e4f4a - SHA1:96a041a735ddb8be1b14cc214ce0f56b486b42db [weak] - MD5Sum:a33f0341357c0be32207618a14b500db [weak] - Filesize:157408 [weak] Last modification reported: Tue, 07 Aug 2018 07:15:09 + Release file created at: Tue, 07 Aug 2018 07:15:03 + W: Some index files failed to download. They have been ignored, or old ones used instead. I have tried solution provided in search as "removing all files in /var/lib/apt/lists and update again" but it doesn't work. Don't know how to resolve it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1785778/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807138] Re: [ALC256 - HDA-Intel - HDA Intel PCH, playback] Headphones not automatically detected
I'm using a Razer Blade 15 2018 -- 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/1807138 Title: [ALC256 - HDA-Intel - HDA Intel PCH, playback] Headphones not automatically detected Status in alsa-driver package in Ubuntu: Incomplete Bug description: Running the command alsamixer allows me to manually increase the sound levels for the headset, and sound plays properly through them. This requires me to disable the auto-mute feature. I haven't rebooted my system yet to see if this is permanent. But the UI doesn't show the heaphones at all and only sends sound through the main speakers of the laptop. ➜ ~ lspci -nnk | grep -i -A7 audio 00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a348] (rev 10) Subsystem: Razer USA Ltd. Device [1a58:2001] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a323] (rev 10) Subsystem: Razer USA Ltd. Device [1a58:2001] Kernel driver in use: i801_smbus Kernel modules: i2c_i801 ➜ ~ cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC256 Codec: Intel Kabylake HDMI Using for example pavucontrol allows me to select the headphone, which are marked as unplugged, and I can play audio through them as long as I keep the application open. If I reboot or close pavucontrol, everything is back to the original state and only the speakers work. Additional Information: ➜ ~ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 What I expect to happen: When I plug in my headphones, Ubuntu and the UI should see them and automatically redirect all sound through them. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: olivar 8320 F...m pulseaudio /dev/snd/controlC0: olivar 8320 F pulseaudio CurrentDesktop: X-Cinnamon Date: Thu Dec 6 13:02:14 2018 InstallationDate: Installed on 2018-11-21 (15 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: Razer dmi.bios.version: 01.01 dmi.board.name: DANA_MB dmi.board.vendor: Razer dmi.chassis.type: 10 dmi.chassis.vendor: Razer dmi.modalias: dmi:bvnRazer:bvr01.01:bd08/31/2018:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr: dmi.product.family: 1A582001 Razer Blade dmi.product.name: Blade dmi.product.version: 1.04 dmi.sys.vendor: Razer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1807138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)
** Also affects: debian-installer via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842040
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1807023
Title:
installer stock images fail to validate any HTTPS certificates (ca-
certificates missing)
Status in debian-installer:
Unknown
Status in ca-certificates package in Ubuntu:
In Progress
Status in debian-installer package in Ubuntu:
In Progress
Status in ca-certificates source package in Trusty:
New
Status in debian-installer source package in Trusty:
New
Status in ca-certificates source package in Xenial:
New
Status in debian-installer source package in Xenial:
New
Status in ca-certificates source package in Bionic:
In Progress
Status in debian-installer source package in Bionic:
In Progress
Status in ca-certificates source package in Cosmic:
In Progress
Status in debian-installer source package in Cosmic:
In Progress
Status in ca-certificates source package in Disco:
In Progress
Status in debian-installer source package in Disco:
In Progress
Status in debian-installer package in Debian:
Fix Released
Bug description:
[Impact]
* The installer stock images fail to validate any HTTPS
certificates because ca-certificates is not available
in the installer environment.
* This causes wget/download errors for preseed files on
HTTPS servers (or HTTP servers that redirect to HTTPS,
which are increasingly common nowadays - e.g., GitHub)
and theoretically any other files that are downloaded
with d-i-utils/fetch-url/wget.
* The fix is to ship ca-certificates-udeb in installer
stock images.
* Debian already ships ca-certificate-udeb in the stock
installer images; the fix is applied since Jan 2017.
(reference: Debian Bug #842040 / d-i commit 2f00c51a [1])
[Test Case]
* In the installer shell:
~ # wget http://github.com # or https://github.com
- FAIL if ca-certificates-udeb is missing:
"ERROR: cannot verify github.com's certificate, <...>'
- PASS if ca-certificates-udeb is available
"Saving to: 'index.html'"
* Test steps with virt-install and netboot images
are provided in the comments, for each release.
[Regression Potential]
* Low. This just adds the ca-certificates files in
/etc/ssl/certs and symlink in /usr/lib/ssl/certs,
so only tools looking for that would be affected.
* Apparently only wget checks for/uses those files,
and the difference in behavior is download errors
no longer occur.
[Notes]
* The ca-certificates-udeb is not currently present
in the Ubuntu archive despite being available for
download in Launchpad with a link for some reason
(perhaps a problem during import from Debian/sid?)
* So this fix includes a no-change-rebuild for the
ca-certificates package, in order to publish the
udeb in the archive.
* The ca-certificates and debian-installer builds
have been done in a PPA using all architectures,
and testing has been done with the amd64 images.
* This fix is request for Bionic, Cosmic, Disco.
The older releases (Trusty, Xenial) are affected,
but not requested for, and would need more work,
as the udeb is not yet in the packaging but that
is doable if required for the process.
[1] https://salsa.debian.org/installer-team/debian-
installer/commit/2f00c51a7ead982ae1cd71bee06c8416890196b6
[Debugging]
For debugging purposes, one can install strace-udeb in the installer
to verify wget's stat() calls to /usr/lib/ssl/certs.
~ # anna-install strace-udeb
~ # strace -e stat wget -O- https://github.com >/dev/null
...
Resolving github.com... stat("/etc/resolv.conf", {st_mode=S_IFREG|0644,
st_size=20, ...}) = 0
140.82.118.3, 140.82.118.4
Connecting to github.com|140.82.118.3|:443... connected.
stat("/usr/lib/ssl/certs/45bfefc3.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
ERROR: cannot verify github.com's certificate, issued by 'CN=DigiCert SHA2
Extended Validation Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US':
Unable to locally verify the issuer's authority.
To connect to github.com insecurely, use `--no-check-certificate'.
+++ exited with 5 +++
~ #
~ # anna-install ca-certificates-udeb # not in archive yet.
unknown udeb ca-certificates-udeb
~ # wget --no-check-certificate
https://launchpad.net/ubuntu/+archive/primary/+files/ca-certificates-
udeb_20180409_all.udeb
~ # udpkg -i ca-certificates-udeb_20180409_all.udeb
~ # strace -e stat wget -O- https://github.com >/dev/nu
[Touch-packages] [Bug 1785778] Re: Hash Sum mismatch Ubuntu Server 18.04.1 LTS
E: Failed to fetch http://gb.archive.ubuntu.com/ubuntu/dists/bionic- updates/main/binary-i386/by- hash/SHA256/54181e4ce10a58ed362cac0b1a98f48989710d6697291b81e0ad7a2c9320a462 Hash Sum mismatch I went to http://gb.archive.ubuntu.com/ubuntu/dists/bionic- updates/universe/binary-amd64/by-hash/SHA256/ and downloaded 54181e4ce10a58ed362cac0b1a98f48989710d6697291b81e0ad7a2c9320a462 2018-12-07 12:40 388K $ sha256sum 54181e4ce10a58ed362cac0b1a98f48989710d6697291b81e0ad7a2c9320a462 50b11a2f079b77e21cf149c15f5bbc9d29fa3f32a9f4e886e51744738202a3fc 54181e4ce10a58ed362cac0b1a98f48989710d6697291b81e0ad7a2c9320a462 Tried switching server: http://us.archive.ubuntu.com/ubuntu/dists /bionic-updates/main/binary-i386/by- hash/SHA256/54181e4ce10a58ed362cac0b1a98f48989710d6697291b81e0ad7a2c9320a462 and got the same hash 50b11a2f079b77e21cf149c15f5bbc9d29fa3f32a9f4e886e51744738202a3fc in error. -- 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/1785778 Title: Hash Sum mismatch Ubuntu Server 18.04.1 LTS Status in apt package in Ubuntu: Invalid Bug description: Hi, I'm getting weird Hashes mismatch error while trying to update Ubuntu server 18.04.1 LTS server. The error I'm receiving is as follows. $ sudo apt-get update Get:1 http://security.ubuntu.com/ubuntu bionic-security InRelease [83.2 kB] Hit:2 http://archive.ubuntu.com/ubuntu bionic InRelease Hit:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease Get:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB] Get:5 http://archive.ubuntu.com/ubuntu bionic-updates/universe Sources [52.2 kB] Get:6 http://archive.ubuntu.com/ubuntu bionic-updates/main Sources [152 kB] Get:7 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse Sources [2,676 B] Get:8 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [277 kB] Get:9 http://archive.ubuntu.com/ubuntu bionic-updates/main Translation-en [105 kB] Get:10 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [157 kB] Err:10 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages Hash Sum mismatch Hashes of expected file: - Filesize:157408 [weak] - SHA256:95fae016beb34455d4601a44c76d1823479178cbcdc58365750d4c039eecfb18 - SHA1:ad29965fe436d84b62331a4662e5fc679103fa0d [weak] - MD5Sum:4375646a0495b45597e06fb3e21dbd10 [weak] Hashes of received file: - SHA256:cdb9774bad7ab6f191ce597e3139f105477428fdc2509c63fcac8e5b904e4f4a - SHA1:96a041a735ddb8be1b14cc214ce0f56b486b42db [weak] - MD5Sum:a33f0341357c0be32207618a14b500db [weak] - Filesize:157408 [weak] Last modification reported: Tue, 07 Aug 2018 07:15:09 + Release file created at: Tue, 07 Aug 2018 07:15:03 + Get:11 http://archive.ubuntu.com/ubuntu bionic-updates/universe Translation-en [71.0 kB] Get:12 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 Packages [3,772 B] Get:13 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse Translation-en [2,376 B] Err:14 http://download.webmin.com/download/repository sarge InRelease Could not connect to download.webmin.com:80 (108.60.199.109), connection timed out Fetched 329 kB in 30s (10.9 kB/s) Reading package lists... Done W: Failed to fetch http://download.webmin.com/download/repository/dists/sarge/InRelease Could not connect to download.webmin.com:80 (108.60.199.109), connection timed out E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-updates/universe/binary-amd64/by-hash/SHA256/95fae016beb34455d4601a44c76d1823479178cbcdc58365750d4c039eecfb18 Hash Sum mismatch Hashes of expected file: - Filesize:157408 [weak] - SHA256:95fae016beb34455d4601a44c76d1823479178cbcdc58365750d4c039eecfb18 - SHA1:ad29965fe436d84b62331a4662e5fc679103fa0d [weak] - MD5Sum:4375646a0495b45597e06fb3e21dbd10 [weak] Hashes of received file: - SHA256:cdb9774bad7ab6f191ce597e3139f105477428fdc2509c63fcac8e5b904e4f4a - SHA1:96a041a735ddb8be1b14cc214ce0f56b486b42db [weak] - MD5Sum:a33f0341357c0be32207618a14b500db [weak] - Filesize:157408 [weak] Last modification reported: Tue, 07 Aug 2018 07:15:09 + Release file created at: Tue, 07 Aug 2018 07:15:03 + W: Some index files failed to download. They have been ignored, or old ones used instead. I have tried solution provided in search as "removing all files in /var/lib/apt/lists and update again" but it doesn't work. Don't know how to resolve it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1785778/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)
d-i for disco uploaded but it now FTBFS because it cannot locate ca-
certificate-udeb.
For some reasons, I didn't notice before hand but ca-certificates
(deb)[1] is found in "main" but ca-certificates (udeb)[2] in 'Universe'
and I suspect the build failure is due to the fact that the builder
doesn't look in 'universe' for it, as it needs to be in 'main'
@archive-admin
Since ca-certificate is already in 'main' can we promote its udeb into 'main'
as well ?
Without the need of a MIR ?
Note: We tried to rebuild ca-certificates w/ no change and see if the
new udeb would be in 'main' but it remained in 'universe' so this will
definitely require an archive admin manipulation.
I already pinged them on #ubuntu-release (Freenode)
[1] - http://archive.ubuntu.com/ubuntu/pool/main/c/ca-certificates/
[2] - http://archive.ubuntu.com/ubuntu/pool/universe/c/ca-certificates/
- Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1807023
Title:
installer stock images fail to validate any HTTPS certificates (ca-
certificates missing)
Status in debian-installer:
Unknown
Status in ca-certificates package in Ubuntu:
In Progress
Status in debian-installer package in Ubuntu:
In Progress
Status in ca-certificates source package in Trusty:
New
Status in debian-installer source package in Trusty:
New
Status in ca-certificates source package in Xenial:
New
Status in debian-installer source package in Xenial:
New
Status in ca-certificates source package in Bionic:
In Progress
Status in debian-installer source package in Bionic:
In Progress
Status in ca-certificates source package in Cosmic:
In Progress
Status in debian-installer source package in Cosmic:
In Progress
Status in ca-certificates source package in Disco:
In Progress
Status in debian-installer source package in Disco:
In Progress
Status in debian-installer package in Debian:
Fix Released
Bug description:
[Impact]
* The installer stock images fail to validate any HTTPS
certificates because ca-certificates is not available
in the installer environment.
* This causes wget/download errors for preseed files on
HTTPS servers (or HTTP servers that redirect to HTTPS,
which are increasingly common nowadays - e.g., GitHub)
and theoretically any other files that are downloaded
with d-i-utils/fetch-url/wget.
* The fix is to ship ca-certificates-udeb in installer
stock images.
* Debian already ships ca-certificate-udeb in the stock
installer images; the fix is applied since Jan 2017.
(reference: Debian Bug #842040 / d-i commit 2f00c51a [1])
[Test Case]
* In the installer shell:
~ # wget http://github.com # or https://github.com
- FAIL if ca-certificates-udeb is missing:
"ERROR: cannot verify github.com's certificate, <...>'
- PASS if ca-certificates-udeb is available
"Saving to: 'index.html'"
* Test steps with virt-install and netboot images
are provided in the comments, for each release.
[Regression Potential]
* Low. This just adds the ca-certificates files in
/etc/ssl/certs and symlink in /usr/lib/ssl/certs,
so only tools looking for that would be affected.
* Apparently only wget checks for/uses those files,
and the difference in behavior is download errors
no longer occur.
[Notes]
* The ca-certificates-udeb is not currently present
in the Ubuntu archive despite being available for
download in Launchpad with a link for some reason
(perhaps a problem during import from Debian/sid?)
* So this fix includes a no-change-rebuild for the
ca-certificates package, in order to publish the
udeb in the archive.
* The ca-certificates and debian-installer builds
have been done in a PPA using all architectures,
and testing has been done with the amd64 images.
* This fix is request for Bionic, Cosmic, Disco.
The older releases (Trusty, Xenial) are affected,
but not requested for, and would need more work,
as the udeb is not yet in the packaging but that
is doable if required for the process.
[1] https://salsa.debian.org/installer-team/debian-
installer/commit/2f00c51a7ead982ae1cd71bee06c8416890196b6
[Debugging]
For debugging purposes, one can install strace-udeb in the installer
to verify wget's stat() calls to /usr/lib/ssl/certs.
~ # anna-install strace-udeb
~ # strace -e stat wget -O- https://github.com >/dev/null
...
Resolving github.com... stat("/etc/resolv.conf", {st_mode=S_IFREG|0644,
st_size=20, ...}) = 0
140.82.118.3, 140.82.118.4
Connecting to github.com|140.82.118.3|:443... connected.
stat("/usr/lib/ssl/certs/45bfefc3.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
st
[Touch-packages] [Bug 1639675] Re: [X555UB, Realtek ALC256, Speaker, Internal] No sound at all
The issue was fixed in the kernel https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/sound/pci/hda/patch_realtek.c?id=c1732ede5 ** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- 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/1639675 Title: [X555UB, Realtek ALC256, Speaker, Internal] No sound at all Status in linux package in Ubuntu: Fix Released Bug description: On ubuntu 16.04 only mic does not work but now 16.10 sounds don`t play too ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrey 2177 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 7 05:17:43 2016 InstallationDate: Installed on 2016-11-07 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrey 2177 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [X555UB, Realtek ALC256, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555UB.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555UB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555UB.300:bd07/06/2016:svnASUSTeKCOMPUTERINC.:pnX555UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X555UB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1639675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806860] Re: Pulseaudio module-jack-source unable to connect to jackd2
** Changed in: jackd2 (Ubuntu) Status: Incomplete => New ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1806860 Title: Pulseaudio module-jack-source unable to connect to jackd2 Status in jackd2 package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: When installing jackd2 in ubuntu 18.04, i am unable to load the module-jack-source. Syslog gives me: Dec 5 11:49:45 nvidion pulseaudio[7905]: JACK error >attempt to connect to server failed< Dec 5 11:49:45 nvidion pulseaudio[7905]: jack_client_open() failed. Dec 5 11:49:45 nvidion pulseaudio[7905]: Failed to load module "module-jack-source" (argument: ""): initialization failed. Dec 5 11:49:45 nvidion pulseaudio[7905]: JACK error >connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=Datei oder Verzeichnis nicht gefunden)< Dec 5 11:49:50 nvidion pulseaudio[7905]: message repeated 5 times: [ JACK error >connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=Datei oder Verzeichnis nicht gefunden)<] Dec 5 11:49:51 nvidio So the path to the shared memory location is not as expected. When jackd2 is running i have: hcw@nvidion:$ cd /dev/shm/ hcw@nvidion:/dev/shm$ ls jack-1000-0 jack_sem.1000_default_1000_0_system jack_sem.1000_default_jack_rack jack_sem.1000_jack_default_1000_0_system jack-1000-1 jack_sem.1000_default_freewheel jack_sem.1000_default_qjackctl jack-shm-registry jack_default_1000_0 jack_sem.1000_default_jack_mixer jack_sem.1000_default_system So it seems module-jack-source / sink are guessing the wrong shared memory paths to the jackd2 server.. Versions: jackd2 1.9.12~dfsg-2 pulseaudio-module-jack 1:11.1-1ubuntu7.1 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-39.42-lowlatency 4.15.18 Tags: bionic Uname: Linux 4.15.0-39-lowlatency x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-16 (111 days ago) UserGroups: adm audio dialout disk docker kvm libvirt mythtv tracing video wireshark _MarkForUpload: True dmi.bios.date: 12/05/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 042NDD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd12/05/2017:svnDellInc.:pnInspiron7566:pvr:rvnDellInc.:rn042NDD:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7566 dmi.sys.vendor: Dell Inc. modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2018-12-04T10:32:39.961952 mtime.conffile..etc.pulse.default.pa: 2018-12-03T11:18:37.948772 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1806860/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807399] Re: package libpam-systemd:amd64 229-4ubuntu21.10 [origin: Ubuntu] failed to install/upgrade: subprocess installed post-installation script returned error exit status 12
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1807399 Title: package libpam-systemd:amd64 229-4ubuntu21.10 [origin: Ubuntu] failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in systemd package in Ubuntu: New Bug description: ola ProblemType: Package DistroRelease: elementary 0.4.1 Package: libpam-systemd:amd64 229-4ubuntu21.10 [origin: Ubuntu] ProcVersionSignature: Ubuntu 4.15.0-42.45~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue Dec 4 22:59:18 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2018-11-25 (11 days ago) InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20170517) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29 SourcePackage: systemd Title: package libpam-systemd:amd64 229-4ubuntu21.10 [origin: Ubuntu] failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1807399/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604235] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all, mic does not record any sound tried almost all ways to fix it, but nothing worked.
** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Fix Released -- 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/1604235 Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all, mic does not record any sound tried almost all ways to fix it, but nothing worked. Status in alsa-driver package in Ubuntu: Fix Released Bug description: Even headphones does not automatically detect in this laptop. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yashwanth 3716 F pulseaudio CurrentDesktop: Unity Date: Tue Jul 19 10:04:49 2016 InstallationDate: Installed on 2016-07-19 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_AlsaRecordingTestStderr: a r e c o r d : p c m _ r e a d : 2 0 3 2 : r e a d e r r o r : I n p u t / o u t p u t e r r o r Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yashwanth 3716 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555UA.204:bd10/18/2015:svnASUSTeKCOMPUTERINC.:pnX555UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X555UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1604235/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807138] Re: [HDA-Intel - HDA Intel PCH, playback] Headphones not automatically detected
What laptop model do you use? Upstream kernel driver has regular fixes like https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/sound/pci/hda/patch_realtek.c?id=c1732ede5 (the one should be in the current kernel already though) ** Changed in: alsa-driver (Ubuntu) Importance: Undecided => Low ** Changed in: alsa-driver (Ubuntu) Status: New => Incomplete ** Summary changed: - [HDA-Intel - HDA Intel PCH, playback] Headphones not automatically detected + [ALC256 - HDA-Intel - HDA Intel PCH, playback] Headphones not automatically detected -- 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/1807138 Title: [ALC256 - HDA-Intel - HDA Intel PCH, playback] Headphones not automatically detected Status in alsa-driver package in Ubuntu: Incomplete Bug description: Running the command alsamixer allows me to manually increase the sound levels for the headset, and sound plays properly through them. This requires me to disable the auto-mute feature. I haven't rebooted my system yet to see if this is permanent. But the UI doesn't show the heaphones at all and only sends sound through the main speakers of the laptop. ➜ ~ lspci -nnk | grep -i -A7 audio 00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a348] (rev 10) Subsystem: Razer USA Ltd. Device [1a58:2001] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a323] (rev 10) Subsystem: Razer USA Ltd. Device [1a58:2001] Kernel driver in use: i801_smbus Kernel modules: i2c_i801 ➜ ~ cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC256 Codec: Intel Kabylake HDMI Using for example pavucontrol allows me to select the headphone, which are marked as unplugged, and I can play audio through them as long as I keep the application open. If I reboot or close pavucontrol, everything is back to the original state and only the speakers work. Additional Information: ➜ ~ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 What I expect to happen: When I plug in my headphones, Ubuntu and the UI should see them and automatically redirect all sound through them. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: olivar 8320 F...m pulseaudio /dev/snd/controlC0: olivar 8320 F pulseaudio CurrentDesktop: X-Cinnamon Date: Thu Dec 6 13:02:14 2018 InstallationDate: Installed on 2018-11-21 (15 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: Razer dmi.bios.version: 01.01 dmi.board.name: DANA_MB dmi.board.vendor: Razer dmi.chassis.type: 10 dmi.chassis.vendor: Razer dmi.modalias: dmi:bvnRazer:bvr01.01:bd08/31/2018:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr: dmi.product.family: 1A582001 Razer Blade dmi.product.name: Blade dmi.product.version: 1.04 dmi.sys.vendor: Razer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1807138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
Sebastien, at present I can't confirm this on Xubuntu 18.04 but I still see a problem with Ubuntu 18.04 for which I have vanilla-gnome-desktop installed so using the Adwaita theme· If I try to select or deselect anything on the "Other Software" tab I see the panel dim slightly as if the prompt for the admin password was going to appear but it doesn't. Just this tab is affected. But *sometimes* if I first select an item on another tab, cancel the password prompt and return to the "Other Software" tab then the password prompt does appear when selecting or deselecting an item. Unfortunately, the above is not reproducible every time and while testing before posting here (by repeatedly switching tabs and trying to select or deselect items) the application crashed and invited me to send a crash report. I see this problem when starting Software & Updates as a stand alone application and also through GNOME Software but not through synaptic as my password has already been entered. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab Status in software-properties package in Ubuntu: Confirmed Bug description: On the "Other Software" tab, I am unable to select "Canonical Partners". Similarly, the other checkboxes on the "Other Software" can not be clicked. Clicking on a checkbox has no effect, and a dialog requesting the admin password is not presented. However, activating or deactivating checkboxes on other tabs causes an authorization dialog to be presented to the user. I experience this bug in an an Xorg session. sources.list and sources.list.d have the following permissions: -rw-r--r-- 1 root root 2897 Oct 26 22:35 sources.list drwxr-xr-x 2 root root 4096 Oct 26 21:29 sources.list.d All files in sources.list.d have the following permissions as this example: -rw-r--r-- 1 root root 189 Oct 25 21:50 google-chrome.list $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.96.24.17 Candidate: 0.96.24.17 Version table: *** 0.96.24.17 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 26 22:45:09 2017 InstallationDate: Installed on 2017-10-26 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark" PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1727908/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1793410] Re: [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal microphone not working
Could be that it requires an hack similar to https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/sound/pci/hda/patch_realtek.c?id=b72f936f with your ids being 1025:1269 Do you feel like manually patching that in the driver you build to see if that fixes the issue? it would be adding a line SND_PCI_QUIRK(0x1025, 0x1269, "Acer Swift SF315-52", ALC286_FIXUP_ACER_AIO_MIC_NO_PRESENCE), -- 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/1793410 Title: [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal microphone not working Status in alsa-driver package in Ubuntu: Confirmed Bug description: Recently bought a new Acer Swift 3 laptop and installed Ubuntu 18.04 on it. Everything works except the internal microphone. I have also tested with an external microphone and this didn't work either. I have worked my way through all the suggested solutions I could find, including trying to reconfigure the pins using hdajacketask. In pavucontrol I have options for Internal Microphone and Microphone (unplugged) but the internal mic only captures static noise. The latest HD-Audio Codec-Specific Models has configurations for alc255-acer and alc256 for some other models, but setting options snd- hda-intel model=MODEL in /etc/modprobe.d/alsa-base.conf does not solve the issue with any of these. Some info - lspci | grep -I audio: 00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point- LP HD Audio (rev 21) cat /proc/asound/cards: 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xdf1a8000 irq 127 dmesg | grep snd: [3.944593] snd_hda_core: loading out-of-tree module taints kernel. [3.956337] snd_soc_skl: Unknown symbol snd_hdac_display_power (err 0) [3.956422] snd_soc_skl: Unknown symbol snd_hdac_i915_exit (err 0) [4.000880] snd_hda_intel :00:1f.3: Probing card using HDA DKMS, version 0.201808050301~ubuntu18.04.1 [4.000895] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [4.013061] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC256: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [4.013063] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [4.013065] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [4.013066] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [4.013066] snd_hda_codec_realtek hdaudioC0D0:inputs: [4.013068] snd_hda_codec_realtek hdaudioC0D0: Mic=0x18 [4.013069] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 info on node 12 from cat /proc/asound/card*/codec\#*: Node 0x12 [Pin Complex] wcaps 0x40040b: Stereo Amp-In Control: name="Internal Mic Boost Volume", index=0, device=0 ControlAmp: chs=3, dir=In, idx=0, ofs=0 Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0 Amp-In vals: [0x02 0x02] Pincap 0x0020: IN Pin Default 0x4000: [N/A] Line Out at Ext N/A Conn = Unknown, Color = Unknown DefAssociation = 0x0, Sequence = 0x0 Pin-ctls: 0x20: IN Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Let me know if you need any other information. James --- Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) _MarkForUpload: True dmi.bios.date: 06/22/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.04 dmi.board.asset.tag: Default string dmi.board.name: Erdinger_KL dmi.board.vendor: KBL dmi.board.version: V1.04 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.04 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.04:bd06/22/2018:svnAcer:pnSwiftSF315-52:pvrV1.04:rvnKBL:rnErdinger_KL:rvrV1.04:cvnAcer:ct10:cvrV1.04: dmi.product.family: Swift 3 dmi.product.name: Swift SF315-52 dmi.product.version: V1.04 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1793410/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807399] [NEW] package libpam-systemd:amd64 229-4ubuntu21.10 [origin: Ubuntu] failed to install/upgrade: subprocess installed post-installation script returned error exit status
Public bug reported: ola ProblemType: Package DistroRelease: elementary 0.4.1 Package: libpam-systemd:amd64 229-4ubuntu21.10 [origin: Ubuntu] ProcVersionSignature: Ubuntu 4.15.0-42.45~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue Dec 4 22:59:18 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2018-11-25 (11 days ago) InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20170517) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29 SourcePackage: systemd Title: package libpam-systemd:amd64 229-4ubuntu21.10 [origin: Ubuntu] failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package loki third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1807399 Title: package libpam-systemd:amd64 229-4ubuntu21.10 [origin: Ubuntu] failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in systemd package in Ubuntu: New Bug description: ola ProblemType: Package DistroRelease: elementary 0.4.1 Package: libpam-systemd:amd64 229-4ubuntu21.10 [origin: Ubuntu] ProcVersionSignature: Ubuntu 4.15.0-42.45~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue Dec 4 22:59:18 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2018-11-25 (11 days ago) InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20170517) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29 SourcePackage: systemd Title: package libpam-systemd:amd64 229-4ubuntu21.10 [origin: Ubuntu] failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1807399/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never
** Changed in: cups (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1804576 Title: MaxJobTime=0 results in jobs being cancelled immediately instead of never Status in CUPS: New Status in cups package in Ubuntu: In Progress Status in cups source package in Trusty: Invalid Status in cups source package in Xenial: In Progress Status in cups source package in Bionic: In Progress Status in cups source package in Cosmic: In Progress Status in cups source package in Disco: In Progress Status in cups package in Debian: Fix Released Bug description: [Impact] Setting the cupsd option MaxJobTime to 0 should make the server wait indefinitely for the job to be ready for print. Instead, after updating job-cancel-after option with MaxJobTime=0 value it results in immediate cancelling. This leads to problems with using filters that take some time to process - the user needs to set MaxJobTime to a ridiculously high value to ensure the job is not going to get cancelled instead of just disabling the cancelling timeout. [Test Case] 1. Add MaxJobTime 0 option to /etc/cups/cupsd.conf. 2. Setup a filter that takes at least several seconds to process. (please find a sample imagetopdf wrapper introducing 5s delay) 3. Submit a print job matching the filter, e.g. lp -d my-printer someimage.jpg # jpg uses the imagetopdf wrapper Expected result: The job is printed after the 5s delay. Actual result: The job is cancelled. [Regression Potential] The scope of the change is limited to fixing the MaxJobTime handling in scheduler/job.c and scheduler/printers.c. There should be no difference in behavior except for the special value of MaxJobTime=0. [Other Info] Original bug description: When using CUPS filters, these filters can take a few seconds to complete. In this case no documents are allowed to be lost on printing failures, so we used to set "MaxJobTime 0" in cupsd.conf which worked on Ubuntu 14.04. With cups on 18.04, you get the following message in /var/log/cups/error_log whenever the filter takes a little longer: I [12/Nov/2018:14:43:26 +0100] [Job 18] Canceling stuck job after 0 seconds. Then, the job is deleted and lost. "MaxJobTime 0" is documented as "indefinite wait", but apparently cups treats is as "wait almost not at all". This issue appears to have also been filed upstream: https://github.com/apple/cups/issues/5438 Temporary workaround is to set the MaxJobTime to a very large value instead (e.g. 3 years) Trusty is not affected by this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1804576/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1805027] Re: systemd-resolved can't resolve Comcast mail server addresses
** Tags added: id-5c094e11580a2f05d67fe6f3 -- 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/1805027 Title: systemd-resolved can't resolve Comcast mail server addresses Status in systemd package in Ubuntu: Triaged Bug description: 1) Ubuntu release: 18.10 2) systemd-resolved version: (Default latest version that comes with Ubuntu 18.10) 3) Expected behavior: Comcast's POP3 mail server addresses to be resolved to IP addresses 4) Actual behavior: Comcast's POP3 mail server addresses can't be resolved to IP addresses Starting on Monday, November 19, 2018, Comcast made a DNS change related to its POP3 mail servers (mail.comcast.net and pop3.comcast.net) that prevent resolved from being able to resolve those domains into IP addresses. When I try to ping either host (mail.comcast.net or pop2.comcast.net), I get this error: tom@deathstar:~$ ping mail.comcast.net ping: mail.comcast.net: Name or service not known tom@deathstar:~$ When I manually lookup up the domain, I get these results: tom@deathstar:~$ nslookup mail.comcast.net Server: 127.0.0.53 Address: 127.0.0.53#53 Non-authoritative answer: mail.comcast.net canonical name = imap.ge.xfinity.com. Name: imap.ge.xfinity.com Address: 96.118.242.209 Name: imap.ge.xfinity.com Address: 96.118.242.197 Name: imap.ge.xfinity.com Address: 96.118.242.233 Name: imap.ge.xfinity.com Address: 96.118.242.225 Name: imap.ge.xfinity.com Address: 96.118.242.226 Name: imap.ge.xfinity.com Address: 96.118.242.217 Name: imap.ge.xfinity.com Address: 96.118.242.208 Name: imap.ge.xfinity.com Address: 96.118.242.230 Name: imap.ge.xfinity.com Address: 96.118.242.232 Name: imap.ge.xfinity.com Address: 96.118.242.218 Name: imap.ge.xfinity.com Address: 96.118.242.211 Name: imap.ge.xfinity.com Address: 96.118.242.242 Name: imap.ge.xfinity.com Address: 96.118.242.221 Name: imap.ge.xfinity.com Address: 96.118.242.196 Name: imap.ge.xfinity.com Address: 96.118.208.40 Name: imap.ge.xfinity.com Address: 96.118.208.99 Name: imap.ge.xfinity.com Address: 2001:558:fc11:9:f816:3eff:fee8:4f07 Name: imap.ge.xfinity.com Address: 2001:558:fc11:9:f816:3eff:fe7d:1b0c Name: imap.ge.xfinity.com Address: 2001:558:fc11:9:f816:3eff:fe25:5ae5 Name: imap.ge.xfinity.com Address: 2001:558:fc11:9:f816:3eff:fef6:babc Name: imap.ge.xfinity.com Address: 2001:558:fc11:9:f816:3eff:fe87:c172 Name: imap.ge.xfinity.com Address: 2001:558:fc11:9:f816:3eff:fee6:7a57 Name: imap.ge.xfinity.com Address: 2001:558:fc11:9:f816:3eff:fe0f:a4a Name: imap.ge.xfinity.com Address: 2001:558:fc11:2:f816:3eff:fec7:cb93 Name: imap.ge.xfinity.com Address: 2001:558:fee2:1000:f816:3eff:fe42:4f14 Name: imap.ge.xfinity.com Address: 2001:558:fc18:0:f816:3eff:fe33:9aaa Name: imap.ge.xfinity.com Address: 2001:558:fc18:0:f816:3eff:feb2:8c0d Name: imap.ge.xfinity.com Address: 2001:558:fc18:0:f816:3eff:fef1:25a5 Name: imap.ge.xfinity.com Address: 2001:558:fc18:0:f816:3eff:febd:320a Name: imap.ge.xfinity.com Address: 2001:558:fc18:0:f816:3eff:fe36:aba3 Name: imap.ge.xfinity.com Address: 2001:558:fc18:0:f816:3eff:fe3f:76f2 Name: imap.ge.xfinity.com Address: 2001:558:fc18:0:f816:3eff:fe45:1d1e tom@deathstar:~$ dig mail.comcast.net ; <<>> DiG 9.11.4-3ubuntu5-Ubuntu <<>> mail.comcast.net ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15037 ;; flags: qr rd ra; QUERY: 1, ANSWER: 17, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;mail.comcast.net.IN A ;; ANSWER SECTION: mail.comcast.net. 15 IN CNAME imap.ge.xfinity.com. imap.ge.xfinity.com. 12 IN A 96.117.3.119 imap.ge.xfinity.com. 12 IN A 96.117.3.96 imap.ge.xfinity.com. 12 IN A 96.117.3.143 imap.ge.xfinity.com. 12 IN A 96.117.3.145 imap.ge.xfinity.com. 12 IN A 96.117.3.129 imap.ge.xfinity.com. 12 IN A 96.117.3.148 imap.ge.xfinity.com. 12 IN A 96.117.3.201 imap.ge.xfinity.com. 12 IN A 96.117.3.136 imap.ge.xfinity.com. 12 IN A 96.118.133.238 imap.ge.xfinity.com. 12 IN A 96.117.3.128 imap.ge.xfinity.com. 12 IN A 96.117.3.144 imap.ge.xfinity.com. 12 IN A 96.117.2.238 imap.ge.xfinity.com. 12 IN A 96.117.3.110 imap.ge.xfinity.com. 12 IN A 96.117.3.140 imap.ge.xfinity.com. 12 IN A 96.117.3.154 imap.ge.xfinity.com. 12 IN A 96.117.3.132 ;; Query time: 13 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Tue Nov 20 06:58:31 PST 2
[Touch-packages] [Bug 1807288] Re: mkfs.ext4 -d $directory_with_acls leads to EINVAL
** Tags added: id-5c09fa23626104848f94e45e -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1807288 Title: mkfs.ext4 -d $directory_with_acls leads to EINVAL Status in e2fsprogs package in Ubuntu: New Status in e2fsprogs source package in Bionic: New Status in e2fsprogs source package in Cosmic: New Status in e2fsprogs source package in Disco: New Bug description: [Justification] `mkfs.ext4 -d` can produce broken filesystems when there are acls in the tree used as input. [Test case] 1. dd if=/dev/zero count=0 bs=1M seek=100 of=./fake.img 2. mkdir -p stuff/journal 3. setfacl -m g:adm:rwx stuff/journal 4. mkfs.ext4 -L lala -O -metadata_csum -T default -O uninit_bg fake.img -d ./stuff/ 5. sudo mount ./fake.img /mnt 6. Verify that `getfacl /mnt/journal/` returns an error. 7. sudo umount /mnt 8. install libext2fs2 from -proposed. 9. mkfs.ext4 -L lala -O -metadata_csum -T default -O uninit_bg fake.img -d ./stuff/ 10. sudo mount ./fake.img /mnt 11. Verify that `getfacl /mnt/journal/` returns acl information, not an error. 12. sudo umount /mnt [Original description] This looks an awful lot like bug 1645232 but that is claimed to be fixed: mwhudson@ringil:~/tmp$ mkfs.ext4 -V mke2fs 1.44.1 (24-Mar-2018) Using EXT2FS Library version 1.44.1 mwhudson@ringil:~/tmp$ dd if=/dev/zero count=0 bs=1M seek=100 of=./fake.img 0+0 records in 0+0 records out 0 bytes copied, 0.0015871 s, 0.0 kB/s mwhudson@ringil:~/tmp$ mkdir -p stuff/journal mwhudson@ringil:~/tmp$ setfacl -m g:adm:rwx stuff/journal mwhudson@ringil:~/tmp$ mkfs.ext4 -L lala -O -metadata_csum -T default -O uninit_bg fake.img -d ./stuff/ mke2fs 1.44.1 (24-Mar-2018) Discarding device blocks: done Creating filesystem with 25600 4k blocks and 6400 inodes Allocating group tables: done Writing inode tables: done Creating journal (1024 blocks): done Copying files into the device: done Writing superblocks and filesystem accounting information: done mwhudson@ringil:~/tmp$ sudo mount ./fake.img /mnt mwhudson@ringil:~/tmp$ getfacl /mnt/journal/ getfacl: /mnt/journal/: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1807288/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
Thank you for your bug report, I can't confirm that problem neither on 18.04 nor 18.10 though, it might be specific to some configuration/theme/session. Do you use the standard ubuntu session? ** Changed in: software-properties (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab Status in software-properties package in Ubuntu: Confirmed Bug description: On the "Other Software" tab, I am unable to select "Canonical Partners". Similarly, the other checkboxes on the "Other Software" can not be clicked. Clicking on a checkbox has no effect, and a dialog requesting the admin password is not presented. However, activating or deactivating checkboxes on other tabs causes an authorization dialog to be presented to the user. I experience this bug in an an Xorg session. sources.list and sources.list.d have the following permissions: -rw-r--r-- 1 root root 2897 Oct 26 22:35 sources.list drwxr-xr-x 2 root root 4096 Oct 26 21:29 sources.list.d All files in sources.list.d have the following permissions as this example: -rw-r--r-- 1 root root 189 Oct 25 21:50 google-chrome.list $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.96.24.17 Candidate: 0.96.24.17 Version table: *** 0.96.24.17 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 26 22:45:09 2017 InstallationDate: Installed on 2017-10-26 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark" PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1727908/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807288] Re: mkfs.ext4 -d $directory_with_acls leads to EINVAL
This bug was fixed in the package e2fsprogs - 1.44.4-2ubuntu1 --- e2fsprogs (1.44.4-2ubuntu1) disco; urgency=medium * debian/patches/0001-libext2fs-fix-regression-so-we-are-correctly- transla.patch: cherry-pick upstream fix so we are correctly translating acls in mkfs.ext4. Closes LP: #1807288. -- Steve Langasek Fri, 07 Dec 2018 12:12:52 +0200 ** Changed in: e2fsprogs (Ubuntu Disco) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1807288 Title: mkfs.ext4 -d $directory_with_acls leads to EINVAL Status in e2fsprogs package in Ubuntu: Fix Released Status in e2fsprogs source package in Bionic: New Status in e2fsprogs source package in Cosmic: New Status in e2fsprogs source package in Disco: Fix Released Bug description: [Justification] `mkfs.ext4 -d` can produce broken filesystems when there are acls in the tree used as input. [Test case] 1. dd if=/dev/zero count=0 bs=1M seek=100 of=./fake.img 2. mkdir -p stuff/journal 3. setfacl -m g:adm:rwx stuff/journal 4. mkfs.ext4 -L lala -O -metadata_csum -T default -O uninit_bg fake.img -d ./stuff/ 5. sudo mount ./fake.img /mnt 6. Verify that `getfacl /mnt/journal/` returns an error. 7. sudo umount /mnt 8. install libext2fs2 from -proposed. 9. mkfs.ext4 -L lala -O -metadata_csum -T default -O uninit_bg fake.img -d ./stuff/ 10. sudo mount ./fake.img /mnt 11. Verify that `getfacl /mnt/journal/` returns acl information, not an error. 12. sudo umount /mnt [Original description] This looks an awful lot like bug 1645232 but that is claimed to be fixed: mwhudson@ringil:~/tmp$ mkfs.ext4 -V mke2fs 1.44.1 (24-Mar-2018) Using EXT2FS Library version 1.44.1 mwhudson@ringil:~/tmp$ dd if=/dev/zero count=0 bs=1M seek=100 of=./fake.img 0+0 records in 0+0 records out 0 bytes copied, 0.0015871 s, 0.0 kB/s mwhudson@ringil:~/tmp$ mkdir -p stuff/journal mwhudson@ringil:~/tmp$ setfacl -m g:adm:rwx stuff/journal mwhudson@ringil:~/tmp$ mkfs.ext4 -L lala -O -metadata_csum -T default -O uninit_bg fake.img -d ./stuff/ mke2fs 1.44.1 (24-Mar-2018) Discarding device blocks: done Creating filesystem with 25600 4k blocks and 6400 inodes Allocating group tables: done Writing inode tables: done Creating journal (1024 blocks): done Copying files into the device: done Writing superblocks and filesystem accounting information: done mwhudson@ringil:~/tmp$ sudo mount ./fake.img /mnt mwhudson@ringil:~/tmp$ getfacl /mnt/journal/ getfacl: /mnt/journal/: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1807288/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458204] Re: removing kernels should not require a restart afterward
Hello Daniel, or anyone else affected, Accepted update-notifier into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/update- notifier/3.168.10 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-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 for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: update-notifier (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1458204 Title: removing kernels should not require a restart afterward Status in unattended-upgrades: New Status in update notifier: New Status in linux package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: Fix Released Status in update-notifier package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in update-notifier source package in Xenial: Fix Committed Status in linux source package in Artful: Won't Fix Status in unattended-upgrades source package in Artful: Won't Fix Status in update-notifier source package in Artful: Won't Fix Bug description: [Impact] The rationale behind the SRU to Xenial is that with latest unattended- upgrades SRU it starts removing unused kernels, but all older kernels are not removed in a single run. With update-notifier and u-u not fixed they place /var/run/reboot-required asking for a reboot when it is not needed. [Test Case] 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. [ Regression Potential ] If the check for skipping placing the /var/run/reboot-required file is too broad it may make kernel upgrades fail to ask for reboot. The fix changes a hook called by maintainer scripts and a failure in the hook can make kernel package installations fail. The fix is simple and was tested in several releases thus regressing in these ways is unlikely. [ Original Bug Text ] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag
[Touch-packages] [Bug 1807262] Re: stein unit tests fail with sqlalchemy.exc.NoSuchTableError: migration_tmp
quoting; ... so that when "PRAGMA legacy_alter_table" is set behaviour is still compatible with versions 3.24 and earlier). WTH where would/should we set that PRAGMA? I think that would be in sqlalchemy's sqlite backend? Coreybc can you take over from here? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/1807262 Title: stein unit tests fail with sqlalchemy.exc.NoSuchTableError: migration_tmp Status in cinder package in Ubuntu: Triaged Status in nova package in Ubuntu: Triaged Status in sqlite3 package in Ubuntu: New Bug description: Several tests that use sqlite fail with: "sqlalchemy.exc.NoSuchTableError: migration_tmp". I'm currently hitting this with nova and cinder packages in disco. Note this started sometime after 11/19 when nova 2:19.0.0~b1~git2018111953.3e756ff674-0ubuntu1 was uploaded (and built successfully at the time). After doing some digging this appears to occur with libsqlite3-0 3.26.0-1 but does not occur with libsqlite3-0 3.25.3-1. Here are some more details on that, shown by running a failing unit test from the cinder package: https://paste.ubuntu.com/p/hsnQFQD572/ Update: The test in the paste above also works successfully with libsqlite3-0 3.25.3-2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1807262/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807262] Re: stein unit tests fail with sqlalchemy.exc.NoSuchTableError: migration_tmp
git bisect start # good: [cbb6e4f7de0115395269860fed18d56beb7ac2bb] Version 3.24.0 git bisect good cbb6e4f7de0115395269860fed18d56beb7ac2bb # bad: [d4f098763eb4fd12a99497340e2f589b37234676] Version 3.26.0 git bisect bad d4f098763eb4fd12a99497340e2f589b37234676 # good: [bf92c08976ad16818be09a6941995bfbf43858f0] Add the "atrc" test program to the Makefiles. Fix a typo in the instructions in the header comment of the atrc program. git bisect good bf92c08976ad16818be09a6941995bfbf43858f0 # good: [ab747c198137c2890b16c2e28afa0d447bcfe8a2] Minor simplification: In OP_ParseSchema, read the p1 register once. git bisect good ab747c198137c2890b16c2e28afa0d447bcfe8a2 # good: [43172f4b080b5f9f8563b8df351dc742afe21bb0] Eponymous virtual tables appear to exist in all schemas. This is an alternative and improved fix to the eponymous virtual table in trigger problem that was previously addressed by checkin [1fa74930ab56171e]. git bisect good 43172f4b080b5f9f8563b8df351dc742afe21bb0 # bad: [e504cfa1878e1d3253e6ff03b33156db2c99c931] Improvements to the CSV virtual table. git bisect bad e504cfa1878e1d3253e6ff03b33156db2c99c931 # bad: [910531f62a723fec548be99fa7dd71888d07d5e7] Merge fixes from trunk. git bisect bad 910531f62a723fec548be99fa7dd71888d07d5e7 # good: [fba76ed87c26c84fb14277efd80ac774533bc92a] Merge the permutations fix from trunk. git bisect good fba76ed87c26c84fb14277efd80ac774533bc92a # good: [6436da628906b028a2e15c273ff03f7984310111] Improved documentation for SQLITE_DBCONFIG_DEFENSIVE. Add a NEVER() macro on an unreachable branch. git bisect good 6436da628906b028a2e15c273ff03f7984310111 # good: [eb689e572223191847e3ed3140902d0d309d04d4] Fix for ticket [787fa716be3a7f650cac] git bisect good eb689e572223191847e3ed3140902d0d309d04d4 # bad: [3cab37c2f2261ccca632a1843b8baeccdecd110d] Fix invalid use of unprotected sqlite3_value objects in the sqldiff utility, when using the --changeset option. git bisect bad 3cab37c2f2261ccca632a1843b8baeccdecd110d # bad: [2defce45c5670e0258374eeb2e293fcf6f82bddd] When a table is renamed using "ALTER TABLE RENAME TO", update any REFERENCES clauses that refer to the table, unless "PRAGMA legacy_alter_table" is true and "PRAGMA foreign_keys" is set to false (i.e. so that when "PRAGMA legacy_alter_table" is set behaviour is still compatible with versions 3.24 and earlier). git bisect bad 2defce45c5670e0258374eeb2e293fcf6f82bddd # first bad commit: [2defce45c5670e0258374eeb2e293fcf6f82bddd] When a table is renamed using "ALTER TABLE RENAME TO", update any REFERENCES clauses that refer to the table, unless "PRAGMA legacy_alter_table" is true and "PRAGMA foreign_keys" is set to false (i.e. so that when "PRAGMA legacy_alter_table" is set behaviour is still compatible with versions 3.24 and earlier). => https://github.com/mackyle/sqlite/commit/2defce45c5670e0258374eeb2e293fcf6f82bddd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/1807262 Title: stein unit tests fail with sqlalchemy.exc.NoSuchTableError: migration_tmp Status in cinder package in Ubuntu: Triaged Status in nova package in Ubuntu: Triaged Status in sqlite3 package in Ubuntu: New Bug description: Several tests that use sqlite fail with: "sqlalchemy.exc.NoSuchTableError: migration_tmp". I'm currently hitting this with nova and cinder packages in disco. Note this started sometime after 11/19 when nova 2:19.0.0~b1~git2018111953.3e756ff674-0ubuntu1 was uploaded (and built successfully at the time). After doing some digging this appears to occur with libsqlite3-0 3.26.0-1 but does not occur with libsqlite3-0 3.25.3-1. Here are some more details on that, shown by running a failing unit test from the cinder package: https://paste.ubuntu.com/p/hsnQFQD572/ Update: The test in the paste above also works successfully with libsqlite3-0 3.25.3-2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1807262/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1561278] Re: internal sound card not detected HP X2
bah, sorry, you probably need the lib as well $ wget https://launchpad.net/ubuntu/+source/alsa-lib/1.1.7-2/+build/15743375/+files/libasound2-data_1.1.7-2_all.deb https://launchpad.net/ubuntu/+source/alsa-lib/1.1.7-2/+build/15743375/+files/libasound2_1.1.7-2_amd64.deb $ sudo dpkg -i libasound*.deb -- 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/1561278 Title: internal sound card not detected HP X2 Status in alsa-driver package in Ubuntu: Confirmed Bug description: HP Pavilion X2 - No sound card detected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Wed Mar 23 18:18:32 2016 InstallationDate: Installed on 2016-03-18 (5 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 813E dmi.board.vendor: HP dmi.board.version: 34.10 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.04:bd09/11/2015:svnHP:pnHPPavilionx2Detachable:pvrType1ProductConfigId:rvnHP:rn813E:rvr34.10:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion x2 Detachable dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1561278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1585084] Re: Volume notification keeps popping up constantly (the notify-OSD bubble on top-right corner)
I ~think~ I just fixed this issue on my PC (GA-B250M-DS3H with HDA Intel PCH, ALC887-VD). Symptoms just like described on this thread: - repeated "Jack 'Front Headphone Jack' is now plugged in" / plugged out messages in pulseaudio logs - acpi_listen showing plug/unplug events - once headphones are plugged into the front jack, issue stops - hdajackretask works as a workaround - side effects: audio stutters, graphics freezes for a split second (looks very much like video card lagging). OSD notifications turned off so I didn't have those. I had the front panel audio cable go behind the motherboard, attached to the other cables in the case. Once I re-connected the cable to go separately from everything else, the problem seems to have completely disappeared. Crosstalk with other cables / motherboard seems like a likely root cause. `pulseaudio - --log-time=1` had 'plugged in' followed by 'plugged out' at very close timestamps (~20ms). Debouncing could avoid the side effects and hide the problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1585084 Title: Volume notification keeps popping up constantly (the notify-OSD bubble on top-right corner) Status in pulseaudio package in Ubuntu: Confirmed Bug description: I upgraded to Ubuntu 16.04 yesterday, I did a clean install while preserving the home directory which is mounted in a separate partition. Even during the installation I had constant volume notification bubble appearing on the top-right corner of my screen, it would come and go about twice every minute. I just thought it was due to installing hardware drivers or something but the problem persisted even when I booted into the freshly installed system. I did some searching and two users reported the exact problem. And one more suggested this happens because constant disconnect and reconnect of the sound card which makes sense as the sound settings flashes briefly during every popup. Someone on IRC suggested to kill pulseaudio and thus restart it, that does not fix the issue. I also tried the Live environment thinking it might be due to some old config files in home partition (which was preserved during upgrade), but this problem happens in the live environment as well, which makes sense because it was present during installation as well. Users with the same issue: http://ubuntuforums.org/showthread.php?t=2323815 http://askubuntu.com/questions/773008/constant-volume-osd-in-16-04 http://askubuntu.com/questions/767466/sound-card-being-disconnected-reconnected-constantly Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: sidd 1651 F pulseaudio /dev/snd/controlC0: sidd 1651 F pulseaudio /dev/snd/controlC1: sidd 1651 F pulseaudio CurrentDesktop: Unity Date: Tue May 24 12:31:12 2016 InstallationDate: Installed on 2016-05-23 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0705 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A97EVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1585084/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1561278] Re: internal sound card not detected HP X2
After a reboot, I now get: dpkg: error processing archive libasound2-data_1.1.7-2_all.deb (--install): installing libasound2-data would break libasound2:amd64, and deconfiguration is not permitted (--auto-deconfigure might help) Errors were encountered while processing: libasound2-data_1.1.7-2_all.deb -- 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/1561278 Title: internal sound card not detected HP X2 Status in alsa-driver package in Ubuntu: Confirmed Bug description: HP Pavilion X2 - No sound card detected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Wed Mar 23 18:18:32 2016 InstallationDate: Installed on 2016-03-18 (5 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 813E dmi.board.vendor: HP dmi.board.version: 34.10 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.04:bd09/11/2015:svnHP:pnHPPavilionx2Detachable:pvrType1ProductConfigId:rvnHP:rn813E:rvr34.10:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion x2 Detachable dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1561278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1561278] Re: internal sound card not detected HP X2
I get 'dpkg frontend is locked by another process' after the dpkg command. No idea what process this is. -- 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/1561278 Title: internal sound card not detected HP X2 Status in alsa-driver package in Ubuntu: Confirmed Bug description: HP Pavilion X2 - No sound card detected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Wed Mar 23 18:18:32 2016 InstallationDate: Installed on 2016-03-18 (5 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 813E dmi.board.vendor: HP dmi.board.version: 34.10 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.04:bd09/11/2015:svnHP:pnHPPavilionx2Detachable:pvrType1ProductConfigId:rvnHP:rn813E:rvr34.10:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion x2 Detachable dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1561278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458204] Re: removing kernels should not require a restart afterward
It looks like Brian can't do it either, but I uploaded the fix for update-notifier in Xenial. ** Description changed: + [Impact] + + The rationale behind the SRU to Xenial is that with latest unattended- + upgrades SRU it starts removing unused kernels, but all older kernels + are not removed in a single run. With update-notifier and u-u not fixed + they place /var/run/reboot-required asking for a reboot when it is not + needed. + + + [Test Case] + 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. + + [ Regression Potential ] + + If the check for skipping placing the /var/run/reboot-required file is too broad it may make kernel upgrades fail to ask for reboot. The fix changes a hook called by maintainer scripts and a failure in the hook can make kernel package installations fail. + The fix is simple and was tested in several releases thus regressing in these ways is unlikely. + + [ Original Bug Text ] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) - --- + --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: - linux-restricted-modules-3.13.0-53-generic N/A - linux-backports-modules-3.13.0-53-generic N/A - linux-firmware 1.127.12 + linux-restricted-modules-3.13.0-53-generic N/A + linux-backports-modules-3.13.0-53-generic N/A + linux-firmware 1.127.12 RfKill: - + Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: - + _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 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.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer -- 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/1458204 Title: removing kernels should not require a restart afterward Status in unattended-upgrades: New Status in update notifier: New Status in linux package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: Fix Released Status in update-notifier package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in linux source package in Artful: Won't Fix Status in unattended-upgrades source package in Artful: Won't Fix Status in update-notifier source package in Artful: Won't Fix Bug description: [Impact] The rationale behind the SRU to Xenial is that with latest unattended- upgrades SRU it starts removing unused kernels, but all older kernels are not removed in a single run. With update-notifier and u-u not fixed they place /var/run/reboot-required asking for a reboot when it is not needed. [Test Case] 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel
[Touch-packages] [Bug 1727459] Re: software-properties-gtk crashed with AttributeError in on_driver_selection_changed(): 'NoneType' object has no attribute 'record'
*** This bug is a duplicate of bug 1807373 *** https://bugs.launchpad.net/bugs/1807373 ** This bug has been marked a duplicate of bug 1807373 /usr/bin/software-properties-gtk:AttributeError:on_driver_selection_changed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1727459 Title: software-properties-gtk crashed with AttributeError in on_driver_selection_changed(): 'NoneType' object has no attribute 'record' Status in software-properties package in Ubuntu: New Bug description: I was using synaptic to abilitate intel microcode driver ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Wed Oct 25 19:55:20 2017 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2017-10-19 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk -n -t 75497602 ProcEnviron: SHELL=/bin/bash LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonArgs: ['/usr/bin/software-properties-gtk', '-n', '-t', '75497602'] PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 SourcePackage: software-properties Title: software-properties-gtk crashed with AttributeError in on_driver_selection_changed(): 'NoneType' object has no attribute 'record' Traceback: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 1196, in on_driver_selection_changed if 'dkms' in pkg.candidate.record['Depends']: AttributeError: 'NoneType' object has no attribute 'record' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1727459/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807373] Re: /usr/bin/software-properties-gtk:AttributeError:on_driver_selection_changed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: software-properties (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1807373 Title: /usr/bin/software-properties- gtk:AttributeError:on_driver_selection_changed Status in software-properties package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 1.92.36bodhi1, the problem page at https://errors.ubuntu.com/problem/b13c9466e8741d31ba6c9934365589f383a60650 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1807373/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807373] [NEW] /usr/bin/software-properties-gtk:AttributeError:on_driver_selection_changed
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 1.92.36bodhi1, the problem page at https://errors.ubuntu.com/problem/b13c9466e8741d31ba6c9934365589f383a60650 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: artful bionic cosmic kylin-15.04 kylin-17.10 quantal raring saucy trusty utopic vivid wily xenial yakkety zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1807373 Title: /usr/bin/software-properties- gtk:AttributeError:on_driver_selection_changed Status in software-properties package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 1.92.36bodhi1, the problem page at https://errors.ubuntu.com/problem/b13c9466e8741d31ba6c9934365589f383a60650 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1807373/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807262] Re: stein unit tests fail with sqlalchemy.exc.NoSuchTableError: migration_tmp
Oh yeah sqlite uses special repository software - thanks :-/
But there is https://github.com/mackyle/sqlite/commits/master
I wrote a build and test script that worked against 3.24 and 3.26 from
git confirming the results.
Kicking that in git bisect to hopefully be able to pick up some insight
later on.
# git bisect start
# git bisect good version-3.24.0
# git bisect bad version-3.26.0
# git bisect run ~/bin/buildsqlite3.sh
The first commit built fine and tested as good, that seems ok'ish.
Walking away for now ...
$ cat #~/bin/buildsqlite3.sh
#!/bin/sh
set -ux
# See http://www.wtfpl.net/txt/copying for license details
# Creates a minimal manifest and manifest.uuid file so sqlite (and fossil) can
build
testdir="/root/cinder-14.0.0~b1~git2018111617.4529b193d"
basedir=$(pwd)
# special bullshit for Fossil versioning system compat
git rev-parse --git-dir >/dev/null || exit 1
echo $(git log -1 --format=format:%H) > manifest.uuid
echo C $(cat manifest.uuid) > manifest
git log -1 --format=format:%ci%n | sed 's/ [-+].*$//;s/ /T/;s/^/D /' >> manifest
# get temp build dir
bdir=$(mktemp -d)
cd "${bdir}"
"${basedir}/configure" || exit 125
make -j || exit 125
make -j sqlite3.c || exit 125
make install || exit 125
# something did not install correctly
ls -laF /usr/local/lib/libsqlite3* || exit 125
# Test
cd "${testdir}"
export LD_LIBRARY_PATH=/usr/local/lib
pkgos-dh_auto_test --no-py2
"cinder.tests.unit.api.contrib.test_volume_type_encryption.VolumeTypeEncryptionTest.test_create_volume_exists"
rc=$?
unset LD_LIBRARY_PATH
# cleanup
# do not by accident test against older libs
rm -f /usr/local/lib/libsqlite3*
cd "${basedir}"
rm -rf "${bdir}"
git clean -f -x
# deliver actual test RC
exit ${rc};
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sqlite3 in Ubuntu.
https://bugs.launchpad.net/bugs/1807262
Title:
stein unit tests fail with sqlalchemy.exc.NoSuchTableError:
migration_tmp
Status in cinder package in Ubuntu:
Triaged
Status in nova package in Ubuntu:
Triaged
Status in sqlite3 package in Ubuntu:
New
Bug description:
Several tests that use sqlite fail with:
"sqlalchemy.exc.NoSuchTableError: migration_tmp". I'm currently
hitting this with nova and cinder packages in disco.
Note this started sometime after 11/19 when nova
2:19.0.0~b1~git2018111953.3e756ff674-0ubuntu1 was uploaded (and built
successfully at the time).
After doing some digging this appears to occur with libsqlite3-0
3.26.0-1 but does not occur with libsqlite3-0 3.25.3-1. Here are some
more details on that, shown by running a failing unit test from the
cinder package: https://paste.ubuntu.com/p/hsnQFQD572/
Update: The test in the paste above also works successfully with
libsqlite3-0 3.25.3-2.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1807262/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1745879] Re: Icons in .desktop files are hardcoded
Hi, The desktop files come from Debian, so I suggest you report this against the Debian bug tracker, using the reportbug command or by sending email as instructed in https://www.debian.org/Bugs/Reporting. The bug should be reported against the python3.5 package. (Because that's the version you have. Some more python2.x and python3.y packages are actually also affected.) To verify which package owns a file, use the command "dpkg -S /usr/share/applications/python*.desktop". Regards, Juhani Numminen ** Package changed: python3-defaults (Ubuntu) => python3.5 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1745879 Title: Icons in .desktop files are hardcoded Status in python3.5 package in Ubuntu: New Bug description: There is already a bug report in the Python bug tracker, from 2014. It has only one response, saying the reporting person should open a bug on their distribution's bug tracker. I'm not sure if this ever happened, so I'm trying my luck here. If this belongs to Debian or Linux Mint please let me know. Problem: The icon paths in the .desktop files shipping with both Python 2.x and 3.x are hardcoded (e.g. "/usr/share/pixmaps/python3.5.xpm"). This is extremely annoying for theming. Solution: Instead of hardcoding the icon to "/usr/share/pixmaps/pythonx.x.xpm", it should just say "python2" and "python3", or even "python". Almost all icon themes will work for Python then. Also I wonder why there's the NoDisplay directive set to true. Like this, having a desktop file makes no sense at all IMO. After each Python update I have to edit the file again and again. So from this: [Desktop Entry] Name=Python (v3.5) Comment=Python Interpreter (v3.5) Exec=/usr/bin/python3.5 Icon=/usr/share/pixmaps/python3.5.xpm Terminal=true Type=Application Categories=Development; StartupNotify=true NoDisplay=true X-Desktop-File-Install-Version=0.22 to this: [Desktop Entry] Name=Python (v3.5) Comment=Python Interpreter (v3.5) Exec=/usr/bin/python3.5 Icon=python3 Terminal=true Type=Application Categories=Development; StartupNotify=true X-Desktop-File-Install-Version=0.22 Information: $ lsb_release -rd Description: Linux Mint 18.2 Sonya Release: 18.2 $ apt-cache policy python3 python3: Installiert: 3.5.1-3 Installationskandidat: 3.5.1-3 Versionstabelle: *** 3.5.1-3 500 500 http://ftp-stud.hs-esslingen.de/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status $ Thanks, - Linus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.5/+bug/1745879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
