[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
** Changed in: ubuntu-cdimage Assignee: (unassigned) => GEO (geo218) -- 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/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Released Status in apt source package in Focal: Fix Released Status in apt source package in Groovy: Fix Released Status in apt package in Debian: Fix Released Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. We have two changes that help address this: * The first one stops immediately configuring multi-arch siblings (e.g. libc6:i386 when it's configuring libc6:amd64). This was not necessary, and caused all the libc6:i386 failures here. * The second change sort of also supersedes the first one: It just ignores any errors from immediate configuration, relying on the fact that it's checked and rectified at a later point if there are unconfigured packages (which is what made all those failures happen spuriously after having successfully installed everything). [Test case] We have one test case in EIPP format in the Debian bug 973305 which was only helped by the second change, not the first one. Run /usr/lib/apt/planners < eipp.log and check there are no errors. TODO: It's unclear if the APT from proposed installed in the live session will fix the installer, needs investigation, but would make a useful test case. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes
[Touch-packages] [Bug 1647174] Re: opening menu for certain types of GtkComboBox causes Gdk-CRITICAL assertion 'GDK_IS_WINDOW (window)' failed
** Bug watch added: Debian Bug tracker #839122 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839122 ** Also affects: gtk+3.0 (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839122 Importance: Unknown Status: Unknown ** Bug watch added: GNOME Bug Tracker #771242 https://bugzilla.gnome.org/show_bug.cgi?id=771242 ** Also affects: gtk via https://bugzilla.gnome.org/show_bug.cgi?id=771242 Importance: Unknown Status: Unknown -- 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/1647174 Title: opening menu for certain types of GtkComboBox causes Gdk-CRITICAL assertion 'GDK_IS_WINDOW (window)' failed Status in GTK+: Unknown Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk+3.0 package in Debian: Unknown Bug description: It happens when try to open any ComboBox or a CellRendererCombo: Gdk-CRITICAL **: gdk_window_get_window_type: assertion 'GDK_IS_WINDOW (window)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1647174/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1507858] [NEW] Network Manager + dnsmasq are not correctly assigning upstream DNS servers
Public bug reported: I'm guessing that the problem is in network-manager, but could be network-manager-openvpn, or network-manager-openvpn-grnome, or dnsmasq?) I have a fresh install of xubuntu 14.04.3 amd64. network-manager 0.9.8.8-0ubuntu7.1 It has one eth port connected, plus 2 OpenVPN connections to remote gateways defined but not normally enabled. The 2 VPN connections are mutually exclusive. There is no selective routing defined, so if either is enabled its gateway becomes the default route. This all seems to be working as expected. Obviously I can only ever have one or the other VPN active, never both. However, the dns nameserver assignment is not working correctly. All of the config has been specified via the NM panel applet, but for clarity I will show you extracts from the NM connrction configs in /etc/NetworkManager/system-connections/ Ignoring the [connection],[vpn],[vpn-secrets] sections here are the 3 [ipv4] and [ipv6] sections: - FOR ETH1: [ipv6] method=ignore [ipv4] method=manual dns=192.168.88.1; address1=192.168.88.104/24,192.168.88.1 FOR VPN-A: [ipv6] method=ignore [ipv4] method=auto dns=111.111.111.111;222.222.222.222; (edited for this report) - and FOR VPN-B: [ipv6] method=ignore [ipv4] method=auto dns=333.333.333.333; (edited for this report) -- Starting with networking disabled and using the NM panel applet to activate the various connections I can monitor in syslog which DNS servers dnsmasq is choosing for its upstream lookups. Step-1, enable eth1 (with both VPN connections disabled) syslog shows: dnsmasq[2124]: setting upstream servers from DBus dnsmasq[2124]: using nameserver 192.168.88.1#53 (this is good, 192.168.88.1 is a local gateway and dns server combined) Step-2, enable VPN-A syslog-shows: dnsmasq[2124]: setting upstream servers from DBus dnsmasq[2124]: using nameserver 111.111.111.111#53 dnsmasq[2124]: using nameserver 222.222.222.222#53 (this is good, 192.168.88.1 has been dropped and the 2 servers defined for VPN-A have been selected) Step-3, disable VPN-A syslog shows: dnsmasq[2124]: setting upstream servers from DBus dnsmasq[2124]: using nameserver 192.168.88.1#53 (this is good, exactly as we were before enabling VPN-A) Step-4, enable VPN-B syslog shows: dnsmasq[2124]: setting upstream servers from DBus dnsmasq[2124]: using nameserver 333.333.333.333#53 dnsmasq[2124]: using nameserver 111.111.111.111#53 dnsmasq[2124]: using nameserver 222.222.222.222#53 (NO!, this is BAD, nameservers 111 and 222 have nothing to do with VPN-B) Step-5, disable VPN-B syslog shows: dnsmasq[2124]: setting upstream servers from DBus dnsmasq[2124]: using nameserver 192.168.88.1#53 (this is good, ) Step-6, lets try enabling VPN-A again syslog-shows: dnsmasq[2124]: setting upstream servers from DBus dnsmasq[2124]: using nameserver 111.111.111.111#53 dnsmasq[2124]: using nameserver 222.222.222.222#53 (this is good, ) I have experimented with this in multiple ways, as far as I can see any DNS servers applicable to the FIRST VPN to be activated are somehow "sticky". If I restart network-manager and then activate VPN-B I still get the wrong nameservers. If I want to activate VPN-B with its correct nameserver as defined then I have to re-boot and activate VPN-B before VPN-A. Then of course I end up with the opposite problem that VPN-A's nameservers are messed up. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1507858 Title: Network Manager + dnsmasq are not correctly assigning upstream DNS servers Status in network-manager package in Ubuntu: New Bug description: I'm guessing that the problem is in network-manager, but could be network-manager-openvpn, or network-manager-openvpn-grnome, or dnsmasq?) I have a fresh install of xubuntu 14.04.3 amd64. network-manager 0.9.8.8-0ubuntu7.1 It has one eth port connected, plus 2 OpenVPN connections to remote gateways defined but not normally enabled. The 2 VPN connections are mutually exclusive. There is no selective routing defined, so if either is enabled its gateway becomes the default route. This all seems to be working as expected. Obviously I can only ever have one or the other VPN active, never both. However, the dns nameserver assignment is not working correctly. All of the config has been specified via the NM panel applet, but for clarity I will show you extracts from the NM connrction configs in /etc/NetworkManager/system-connections/ Ignoring the [connection],[vpn],[vpn-secrets] sections here are the 3 [ipv4] and [ipv6] sections: - FOR ETH1:
[Touch-packages] [Bug 1414686] Re: package rsyslog 7.4.4-1ubuntu2.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Summary changed: - ackage rsyslog 7.4.4-1ubuntu2.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 + package rsyslog 7.4.4-1ubuntu2.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1414686 Title: package rsyslog 7.4.4-1ubuntu2.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in rsyslog package in Ubuntu: New Bug description: started creating problem after last install closed abruptly ProblemType: Package DistroRelease: Ubuntu 14.04 Package: rsyslog 7.4.4-1ubuntu2.5 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Mon Jan 26 19:43:36 2015 DpkgHistoryLog: Start-Date: 2015-01-26 19:43:20 Commandline: apt-get install alien Install: rpm2cpio:amd64 (4.11.1-3ubuntu0.1, automatic), rpm-common:amd64 (4.11.1-3ubuntu0.1, automatic), rpm:amd64 (4.11.1-3ubuntu0.1, automatic), librpm3:amd64 (4.11.1-3ubuntu0.1, automatic), debugedit:amd64 (4.11.1-3ubuntu0.1, automatic), librpmsign1:amd64 (4.11.1-3ubuntu0.1, automatic), alien:amd64 (8.90), librpmbuild3:amd64 (4.11.1-3ubuntu0.1, automatic), librpmio3:amd64 (4.11.1-3ubuntu0.1, automatic) DuplicateSignature: package:rsyslog:7.4.4-1ubuntu2.5:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 SourcePackage: rsyslog Title: package rsyslog 7.4.4-1ubuntu2.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1414686/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1341073] Re: GtkStack doesn't render a background
This bug is fixed here: https://git.gnome.org/browse/gtk+/commit/?id=02ccfb5d62430590b11b2d3e34b6100e4a6ddcda -- 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/1341073 Title: GtkStack doesn't render a background Status in GTK+ GUI Toolkit: Fix Released Status in “gtk+3.0” package in Ubuntu: New Bug description: GtkStack currently doesn't render a background, so theming it isn't possible. Also, this causes issues with native X11 windows under Ubuntu where the GtkStack will appear black or transparent, i.e. the background colour of the top-level X11 window. This breaks the stack transitions. Compare before/after on page 2 of widget-factory. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1341073/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
