[Touch-packages] [Bug 1843869] [NEW] System crashes randomly each time with different application
You have been subscribed to a public bug: Description:Ubuntu 16.04.6 LTS Release:16.04 Package version: 7.7+13ubuntu3.1 Fresh system install with Ubuntu 16.04 crashes the system after some time. We are running high CPU intensive jobs, but CPU usage never crosses 80%. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-62-generic 4.15.0-62.69~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-62.69~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-62-generic x86_64 NonfreeKernelModules: snapapi26 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Fri Sep 13 11:46:12 2019 InstallationDate: Installed on 2019-09-11 (1 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- System crashes randomly each time with different application https://bugs.launchpad.net/bugs/1843869 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg 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 1843869] Re: System crashes randomly each time with different application
** Package changed: linux-signed-hwe (Ubuntu) => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1843869 Title: System crashes randomly each time with different application Status in xorg package in Ubuntu: New Bug description: Description: Ubuntu 16.04.6 LTS Release: 16.04 Package version: 7.7+13ubuntu3.1 Fresh system install with Ubuntu 16.04 crashes the system after some time. We are running high CPU intensive jobs, but CPU usage never crosses 80%. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-62-generic 4.15.0-62.69~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-62.69~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-62-generic x86_64 NonfreeKernelModules: snapapi26 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Fri Sep 13 11:46:12 2019 InstallationDate: Installed on 2019-09-11 (1 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1843869/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843755] Re: [FFe] Please accept systemd 242 to Eoan
@vorlon: I agree that upgrading to v242 comes with risks, but the risk fairly hard to assess exactly. One measure can be the number of upstream stable backports and this is as follows: rbalint@yogi:~/projects/deb/systemd.git$ git describe github-stable/v242-stable v242-108-gf875dced33 rbalint@yogi:~/projects/deb/systemd.git$ git describe github-stable/v241-stable v241-188-g1e19bcd55e This measure does not give a clear guidance, since lack of backports can mean lack of regressions or the lack of interest to backport as well. Fedora 30 is also on systemd 241 and Fedora rawhide already moved to 243: https://pkgs.org/download/systemd It is still a question of Ubuntu wanting to use Eoan to get feedback on v242 features and regressions in preparing for 20.04 LTS - or we want to have v241 in Eoan to have lower risk of regression and lower required effort to keep systemd in Eoan but having a bigger version bump at the Eoan -> 20.04 upgrade. If the decision is to keep v241 for Eaon then we can merge changes from Debian stable and upstream v241 stable when needed and I move on to land a good v243 at the beginning of the 20.04 cycle. If we decide to approve this FFe, I can upload 242 today, we can merge 242 changes from Debian but only in the next few weeks - maybe two months, until Debian moves on to v243 then we are on our own maintaining v243 debs with the help of upstream's v242-stable branch. I can decrease the unknown risk by merging everything from v242-stable and doing a test round _before_ uploading 242 to Eoan, but I did not want to do that if the decision is sticking to v241 no matter how this testing run goes. So the third option would be conditionally accepting the FFe, only accepting v242 to Eoan if it includes all patches from v242-stable and the autopktests all pass. Picking this I need ~one more day to update the package and run the tests so it could land early next week. -- 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/1843755 Title: [FFe] Please accept systemd 242 to Eoan Status in systemd package in Ubuntu: Incomplete Bug description: Eoan currently has 241-7ubuntu1, Debian stable has 241 and Debian testing moved to 242 last week. While version 241 is the safer choice for Eoan (from v241 and v242) since it is widely tested updating to v242 will allow us to carry fewer patches in Eoan and makes moving to the next release easier. The proposed package is tested in Bileto and all tests are passing (except for a few unrelated failures): https://bileto.ubuntu.com/#/ticket/3797 The final version will be 242-6ubuntu1 and I'm tidying up the changelog, too. I plan merging 242-7, too, going forward but this will not need an FFe. CHANGES WITH 242: * In .link files, MACAddressPolicy=persistent (the default) is changed to cover more devices. For devices like bridges, tun, tap, bond, and similar interfaces that do not have other identifying information, the interface name is used as the basis for persistent seed for MAC and IPv4LL addresses. The way that devices that were handled previously is not changed, and this change is about covering more devices then previously by the "persistent" policy. MACAddressPolicy=random may be used to force randomized MACs and IPv4LL addresses for a device if desired. Hint: the log output from udev (at debug level) was enhanced to clarify what policy is followed and which attributes are used. `SYSTEMD_LOG_LEVEL=debug udevadm test-builtin net_setup_link /sys/class/net/` may be used to view this. Hint: if a bridge interface is created without any slaves, and gains a slave later, then now the bridge does not inherit slave's MAC. To inherit slave's MAC, for example, create the following file: ``` # /etc/systemd/network/98-bridge-inherit-mac.link [Match] Type=bridge [Link] MACAddressPolicy=none ``` * The .device units generated by systemd-fstab-generator and other generators do not automatically pull in the corresponding .mount unit as a Wants= dependency. This means that simply plugging in the device will not cause the mount unit to be started automatically. But please note that the mount unit may be started for other reasons, in particular if it is part of local-fs.target, and any unit which (transitively) depends on local-fs.target is started. * networkctl list/status/lldp now accept globbing wildcards for network interface names to match against all existing interfaces. * The $PIDFILE environment variable is set to point
[Touch-packages] [Bug 1843880] [NEW] GtkSpinButton's context menu changes the width of '+'
Public bug reported: GtkSpinButton consists of a (typically numeric) input field, followed by a '-' and finally a '+' sign. The width of the '+' sign shrinks a little bit when you open the right-click context menu of the input field. It shouldn't, it should have a constant width. Happens with Ubuntu's old default Ambiance and Radiance themes. Does not happen with Ubuntu's new default Yaru, or with GTK's default Adwaita. Example: Open gnome-terminal, right click on its terminal canvas, choose Preferences. You're taken to the profile's Text tab which contains four such widgets. Right-click on one of these input fields, e.g. on "80" for the initial number of columns. In addition to the context menu appearing, the '+' button becomes narrower, and thus the label on its right (e.g. "columns") shifts to the left. For some of the spinbuttons (the ones that stretch the window) the entire window also shrinks. Dismiss the context menu and it goes back to its previous width. (This is similar to former bug 1740709.) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: light-themes 19.04-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Sep 13 11:48:51 2019 InstallationDate: Installed on 2016-11-09 (1037 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to eoan on 2019-09-08 (4 days ago) ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan visual-quality ** Tags added: visual-quality -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1843880 Title: GtkSpinButton's context menu changes the width of '+' Status in ubuntu-themes package in Ubuntu: New Bug description: GtkSpinButton consists of a (typically numeric) input field, followed by a '-' and finally a '+' sign. The width of the '+' sign shrinks a little bit when you open the right-click context menu of the input field. It shouldn't, it should have a constant width. Happens with Ubuntu's old default Ambiance and Radiance themes. Does not happen with Ubuntu's new default Yaru, or with GTK's default Adwaita. Example: Open gnome-terminal, right click on its terminal canvas, choose Preferences. You're taken to the profile's Text tab which contains four such widgets. Right-click on one of these input fields, e.g. on "80" for the initial number of columns. In addition to the context menu appearing, the '+' button becomes narrower, and thus the label on its right (e.g. "columns") shifts to the left. For some of the spinbuttons (the ones that stretch the window) the entire window also shrinks. Dismiss the context menu and it goes back to its previous width. (This is similar to former bug 1740709.) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: light-themes 19.04-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Sep 13 11:48:51 2019 InstallationDate: Installed on 2016-11-09 (1037 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to eoan on 2019-09-08 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1843880/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843886] [NEW] pam_env.so does not recursively read /etc/environment.d
Public bug reported: Ubuntu creates /etc/environment and directory /etc/environment.d. pam_env.so only reads /etc/environment, but not recursively /etc/environment.d/ You'll have to add any files created within /etc/environment.d/ as an additional line to your pam_env.so pam configuration. This is not stated anywhere and not documented accordingly. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libpam-modules 1.3.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Sep 13 12:55:41 2019 InstallationDate: Installed on 2019-09-09 (3 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pam UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pam (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1843886 Title: pam_env.so does not recursively read /etc/environment.d Status in pam package in Ubuntu: New Bug description: Ubuntu creates /etc/environment and directory /etc/environment.d. pam_env.so only reads /etc/environment, but not recursively /etc/environment.d/ You'll have to add any files created within /etc/environment.d/ as an additional line to your pam_env.so pam configuration. This is not stated anywhere and not documented accordingly. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libpam-modules 1.3.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Sep 13 12:55:41 2019 InstallationDate: Installed on 2019-09-09 (3 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pam UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1843886/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 721786] Re: (Non-overlay) scroll-bar lacks sufficient contrast to easily identify its position in the scroll-track
** Changed in: ubuntu-themes (Ubuntu) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/721786 Title: (Non-overlay) scroll-bar lacks sufficient contrast to easily identify its position in the scroll-track Status in Ayatana Design: Fix Committed Status in One Hundred Papercuts: Fix Released Status in Ubuntu MATE: Won't Fix Status in Ubuntu theme: Fix Released Status in ubuntu-themes package in Ubuntu: Won't Fix Bug description: Binary package hint: gnome-session The scroll-bars that appear on the right-side and bottom of gnome windows lack sufficient contrast to the scroll-track. I have difficulty identifying where in the scroll-track the bar is positioned. I often mistake the background of the scroll-track as the scroll-bar itself. I'm using Inverted Control theme. More contrast and better color separation is needed here. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: gnome-session-bin 2.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-28.55-generic 2.6.32.27+drm33.12 Uname: Linux 2.6.32-28-generic i686 Architecture: i386 Date: Sat Feb 19 09:19:22 2011 ExecutablePath: /usr/bin/gnome-session InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1) ProcEnviron: LC_TIME=en_GB.UTF-8 LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: gnome-session XsessionErrors: (polkit-gnome-authentication-agent-1:1387): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/721786/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1819074] Re: Keepalived < 2.0.x in Ubuntu 18.04 LTS not compatible with systemd-networkd
Looks like this has been fixed in keepalived 2.x (detection of missing vip) - https://github.com/acassen/keepalived/issues/836 - but the patch is embedded with a whole load others that were merged at once so might be hard to backport. ** Bug watch added: github.com/acassen/keepalived/issues #836 https://github.com/acassen/keepalived/issues/836 -- 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/1819074 Title: Keepalived < 2.0.x in Ubuntu 18.04 LTS not compatible with systemd- networkd Status in keepalived package in Ubuntu: Fix Released Status in netplan.io package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in keepalived source package in Bionic: Triaged Status in netplan.io source package in Bionic: New Status in systemd source package in Bionic: New Bug description: Systemd-networkd clobbers VIPs placed by other daemons on any reconfiguration triggering systemd-networkd restart (netplan apply for example). Keepalived < version 2.0.x will not restore a VIP lost in this fashion, breaking high availability on Ubuntu 18.04 LTS. A backport for keepalived >= 2.0.x should fix the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1819074/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843627] Re: evolution-calendar-factory crashed with SIGSEGV in tcache_get()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: evolution-data-server (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1843627 Title: evolution-calendar-factory crashed with SIGSEGV in tcache_get() Status in evolution-data-server: Fix Released Status in evolution-data-server package in Ubuntu: Confirmed Bug description: https://gitlab.gnome.org/GNOME/evolution/issues/616 --- I don't know what happened. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: evolution-data-server 3.33.91-3 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 11 13:41:26 2019 ExecutablePath: /usr/libexec/evolution-calendar-factory InstallationDate: Installed on 2018-12-02 (282 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/libexec/evolution-calendar-factory ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f36355653ae <__GI___libc_malloc+286>: mov (%r8),%rsi PC (0x7f36355653ae) ok source "(%r8)" (0x7f36) not located in a known VMA region (needed readable region)! destination "%rsi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: evolution-data-server StacktraceTop: tcache_get (tc_idx=) at malloc.c:2937 __GI___libc_malloc (bytes=32) at malloc.c:3051 g_malloc () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_datalist_id_set_data_full () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: evolution-calendar-factory crashed with SIGSEGV in tcache_get() UpgradeStatus: Upgraded to eoan on 2018-12-02 (282 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1843627/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843755] Re: [FFe] Please accept systemd 242 to Eoan
** Tags added: id-5d6fb9fb2ac215651795ec78 -- 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/1843755 Title: [FFe] Please accept systemd 242 to Eoan Status in systemd package in Ubuntu: Incomplete Bug description: Eoan currently has 241-7ubuntu1, Debian stable has 241 and Debian testing moved to 242 last week. While version 241 is the safer choice for Eoan (from v241 and v242) since it is widely tested updating to v242 will allow us to carry fewer patches in Eoan and makes moving to the next release easier. The proposed package is tested in Bileto and all tests are passing (except for a few unrelated failures): https://bileto.ubuntu.com/#/ticket/3797 The final version will be 242-6ubuntu1 and I'm tidying up the changelog, too. I plan merging 242-7, too, going forward but this will not need an FFe. CHANGES WITH 242: * In .link files, MACAddressPolicy=persistent (the default) is changed to cover more devices. For devices like bridges, tun, tap, bond, and similar interfaces that do not have other identifying information, the interface name is used as the basis for persistent seed for MAC and IPv4LL addresses. The way that devices that were handled previously is not changed, and this change is about covering more devices then previously by the "persistent" policy. MACAddressPolicy=random may be used to force randomized MACs and IPv4LL addresses for a device if desired. Hint: the log output from udev (at debug level) was enhanced to clarify what policy is followed and which attributes are used. `SYSTEMD_LOG_LEVEL=debug udevadm test-builtin net_setup_link /sys/class/net/` may be used to view this. Hint: if a bridge interface is created without any slaves, and gains a slave later, then now the bridge does not inherit slave's MAC. To inherit slave's MAC, for example, create the following file: ``` # /etc/systemd/network/98-bridge-inherit-mac.link [Match] Type=bridge [Link] MACAddressPolicy=none ``` * The .device units generated by systemd-fstab-generator and other generators do not automatically pull in the corresponding .mount unit as a Wants= dependency. This means that simply plugging in the device will not cause the mount unit to be started automatically. But please note that the mount unit may be started for other reasons, in particular if it is part of local-fs.target, and any unit which (transitively) depends on local-fs.target is started. * networkctl list/status/lldp now accept globbing wildcards for network interface names to match against all existing interfaces. * The $PIDFILE environment variable is set to point the absolute path configured with PIDFile= for processes of that service. * The fallback DNS server list was augmented with Cloudflare public DNS servers. Use `-Ddns-servers=` to set a different fallback. * A new special target usb-gadget.target will be started automatically when a USB Device Controller is detected (which means that the system is a USB peripheral). * A new unit setting CPUQuotaPeriodSec= assigns the time period relatively to which the CPU time quota specified by CPUQuota= is measured. * A new unit setting ProtectHostname= may be used to prevent services from modifying hostname information (even if they otherwise would have privileges to do so). * A new unit setting NetworkNamespacePath= may be used to specify a namespace for service or socket units through a path referring to a Linux network namespace pseudo-file. * The PrivateNetwork= setting and JoinsNamespaceOf= dependencies now have an effect on .socket units: when used the listening socket is created within the configured network namespace instead of the host namespace. * ExecStart= command lines in unit files may now be prefixed with ':' in which case environment variable substitution is disabled. (Supported for the other ExecXYZ= settings, too.) * .timer units gained two new boolean settings OnClockChange= and OnTimezoneChange= which may be used to also trigger a unit when the system clock is changed or the local timezone is modified. systemd-run has been updated to make these options easily accessible from the command line for transient timers. * Two n
[Touch-packages] [Bug 1843812] Re: apt info "please use the '-a' switch"
** Tags added: id-5d7aa5d50ab4905dcdc54c44 -- 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/1843812 Title: apt info "please use the '-a' switch" Status in apt package in Ubuntu: Triaged Bug description: When getting info about a package, I see a notice asking me to "Please use the '-a' switch", but the apt program does not accept an '-a' switch. Steps to reproduce: $ apt info docker.io ... N: There is 1 additional record. Please use the '-a' switch to see it $ apt -a info docker.io $ apt info -a docker.io $ apt info docker.io -a Expected outcome: same output as `apt info docker.io` but with the 1 additional record. Seen outcome: E: Command line option 'a' [from -a] is not understood in combination with the other options. Also seen: `apt info $pkg` gives the same output as `apt show $pkg` including the Notice message, but where `apt info -a $pkg` fails, `apt show -a $pkg` succeeds. Workaround: Use `apt show -a $pkg` instead. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: apt 1.8.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: KDE Date: Thu Sep 12 14:16:09 2019 InstallationDate: Installed on 2018-10-30 (316 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: apt UpgradeStatus: Upgraded to disco on 2019-04-18 (147 days ago) modified.conffile..etc.logrotate.d.apport: [modified] modified.conffile..etc.logrotate.d.apt: [modified] mtime.conffile..etc.logrotate.d.apport: 2018-12-13T12:13:33.355709 mtime.conffile..etc.logrotate.d.apt: 2018-12-13T12:13:41.355709 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1843812/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843895] Re: Unable to launch seahorse
This issue occurs only on Xorg session (ubuntu 19.04). No problem on Wayland session. ** Also affects: xorg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1843895 Title: Unable to launch seahorse Status in seahorse package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: When I try to run seahorse, I've these errors: (seahorse:11732): Gdk-ERROR **: 14:45:20.702: The program 'seahorse' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 1008 error_code 11 request_code 130 (MIT-SHM) minor_code 5) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Trappe pour point d'arrêt et de trace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1843895/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843895] Re: Unable to launch seahorse
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem. Before using gdb do '$ export GDK_SYNCHRONIZE=1' What version of Ubuntu are you using ** No longer affects: xorg (Ubuntu) ** Changed in: seahorse (Ubuntu) Importance: Undecided => Low ** Changed in: seahorse (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1843895 Title: Unable to launch seahorse Status in seahorse package in Ubuntu: Incomplete Bug description: When I try to run seahorse, I've these errors: (seahorse:11732): Gdk-ERROR **: 14:45:20.702: The program 'seahorse' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 1008 error_code 11 request_code 130 (MIT-SHM) minor_code 5) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Trappe pour point d'arrêt et de trace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1843895/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843750] Re: libsecret ftbfs in eoan
** Changed in: libsecret (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsecret in Ubuntu. https://bugs.launchpad.net/bugs/1843750 Title: libsecret ftbfs in eoan Status in libsecret package in Ubuntu: Fix Committed Bug description: https://launchpadlibrarian.net/441262252/buildlog_ubuntu-eoan- amd64.libsecret_0.18.8-1_BUILDING.txt.gz Testsuite summary for libsecret 0.18.8 # TOTAL: 198 # PASS: 13 # SKIP: 0 # XFAIL: 0 # FAIL: 0 # XPASS: 0 # ERROR: 185 == To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsecret/+bug/1843750/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843755] Re: [FFe] Please accept systemd 242 to Eoan
@vorlon Testing 243 goes better than expected, I may able to prepare it for FFe instead of 242 so Eoan would be in sync with Fedora. -- 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/1843755 Title: [FFe] Please accept systemd 242 to Eoan Status in systemd package in Ubuntu: Incomplete Bug description: Eoan currently has 241-7ubuntu1, Debian stable has 241 and Debian testing moved to 242 last week. While version 241 is the safer choice for Eoan (from v241 and v242) since it is widely tested updating to v242 will allow us to carry fewer patches in Eoan and makes moving to the next release easier. The proposed package is tested in Bileto and all tests are passing (except for a few unrelated failures): https://bileto.ubuntu.com/#/ticket/3797 The final version will be 242-6ubuntu1 and I'm tidying up the changelog, too. I plan merging 242-7, too, going forward but this will not need an FFe. CHANGES WITH 242: * In .link files, MACAddressPolicy=persistent (the default) is changed to cover more devices. For devices like bridges, tun, tap, bond, and similar interfaces that do not have other identifying information, the interface name is used as the basis for persistent seed for MAC and IPv4LL addresses. The way that devices that were handled previously is not changed, and this change is about covering more devices then previously by the "persistent" policy. MACAddressPolicy=random may be used to force randomized MACs and IPv4LL addresses for a device if desired. Hint: the log output from udev (at debug level) was enhanced to clarify what policy is followed and which attributes are used. `SYSTEMD_LOG_LEVEL=debug udevadm test-builtin net_setup_link /sys/class/net/` may be used to view this. Hint: if a bridge interface is created without any slaves, and gains a slave later, then now the bridge does not inherit slave's MAC. To inherit slave's MAC, for example, create the following file: ``` # /etc/systemd/network/98-bridge-inherit-mac.link [Match] Type=bridge [Link] MACAddressPolicy=none ``` * The .device units generated by systemd-fstab-generator and other generators do not automatically pull in the corresponding .mount unit as a Wants= dependency. This means that simply plugging in the device will not cause the mount unit to be started automatically. But please note that the mount unit may be started for other reasons, in particular if it is part of local-fs.target, and any unit which (transitively) depends on local-fs.target is started. * networkctl list/status/lldp now accept globbing wildcards for network interface names to match against all existing interfaces. * The $PIDFILE environment variable is set to point the absolute path configured with PIDFile= for processes of that service. * The fallback DNS server list was augmented with Cloudflare public DNS servers. Use `-Ddns-servers=` to set a different fallback. * A new special target usb-gadget.target will be started automatically when a USB Device Controller is detected (which means that the system is a USB peripheral). * A new unit setting CPUQuotaPeriodSec= assigns the time period relatively to which the CPU time quota specified by CPUQuota= is measured. * A new unit setting ProtectHostname= may be used to prevent services from modifying hostname information (even if they otherwise would have privileges to do so). * A new unit setting NetworkNamespacePath= may be used to specify a namespace for service or socket units through a path referring to a Linux network namespace pseudo-file. * The PrivateNetwork= setting and JoinsNamespaceOf= dependencies now have an effect on .socket units: when used the listening socket is created within the configured network namespace instead of the host namespace. * ExecStart= command lines in unit files may now be prefixed with ':' in which case environment variable substitution is disabled. (Supported for the other ExecXYZ= settings, too.) * .timer units gained two new boolean settings OnClockChange= and OnTimezoneChange= which may be used to also trigger a unit when the system clock is changed or the local timezone is modified. systemd-run has been updated to make these options ea
[Touch-packages] [Bug 1843750] Re: libsecret ftbfs in eoan
https://bugs.launchpad.net/ubuntu/+source/libsecret/0.18.8-2 ** Changed in: libsecret (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsecret in Ubuntu. https://bugs.launchpad.net/bugs/1843750 Title: libsecret ftbfs in eoan Status in libsecret package in Ubuntu: Fix Released Bug description: https://launchpadlibrarian.net/441262252/buildlog_ubuntu-eoan- amd64.libsecret_0.18.8-1_BUILDING.txt.gz Testsuite summary for libsecret 0.18.8 # TOTAL: 198 # PASS: 13 # SKIP: 0 # XFAIL: 0 # FAIL: 0 # XPASS: 0 # ERROR: 185 == To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsecret/+bug/1843750/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1840510] Re: Please enable PGO and LTO for arm64
> This is worth about 30% performance. can you share some performance tests used to measure this improvement? -- 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/1840510 Title: Please enable PGO and LTO for arm64 Status in python3-defaults package in Ubuntu: New Bug description: The rules file conditionally enables PGO and LTO in the python3 build and while it's enabled for many platforms it's not enabled for arm64. This is worth about 30% performance. Please enable it. A patch is available here with the original debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934812 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1840510/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1840510] Re: Please enable PGO and LTO for arm64
Some of the subcomponents of the pyperformance suite: https://github.com/python/pyperformance/tree/master/pyperformance/benchmarks -- 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/1840510 Title: Please enable PGO and LTO for arm64 Status in python3-defaults package in Ubuntu: New Bug description: The rules file conditionally enables PGO and LTO in the python3 build and while it's enabled for many platforms it's not enabled for arm64. This is worth about 30% performance. Please enable it. A patch is available here with the original debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934812 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1840510/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived clusters
The following 3 bugs:
https://bugs.launchpad.net/bugs/1815101
https://bugs.launchpad.net/bugs/1819074
https://bugs.launchpad.net/bugs/1810583
Have the same root cause: the fact that systemd-network messes with
secondary IP addresses in NICs managed by systemd.
I'm marking all other cases as a duplicate of LP: #1815101.
TODO here is the following:
- There are mainly 2 "fixes" for this issue:
1) keepalived is able to recognize systemd-networkd changes and change
cluster status in order to reconfigure managed NICs (keepalived (>
2.0.x)).
2) systemd-networkd implements a new stanza (KeepConfiguration=) to
systemd service unit files in order to fix not only this behavior but
all those HA related software that manages secondary IPs and/or aliases
to NICs being managed by systemd-networkd.
I think the most appropriate would make sure those 2 features work in
Eoan, both, together, and then make sure the SRUs are done to Disco and
Bionic. One problem w/ the item (2) is that netplan will also have to
support the new "KeepConfiguration=" systemd service file stanza, but,
the fix (2) is more appropriate for all other HA related softwares
controlling virtual IPs (CTDB, Pacemaker, and so ...).
--
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/1815101
Title:
[master] Restarting systemd-networkd breaks keepalived clusters
Status in netplan:
Confirmed
Status in keepalived package in Ubuntu:
Confirmed
Status in systemd package in Ubuntu:
Confirmed
Bug description:
Configure netplan for interfaces, for example (a working config with
IP addresses obfuscated)
network:
ethernets:
eth0:
addresses: [192.168.0.5/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth2:
addresses:
- 12.13.14.18/29
- 12.13.14.19/29
gateway4: 12.13.14.17
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth3:
addresses: [10.22.11.6/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth4:
addresses: [10.22.14.6/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth7:
addresses: [9.5.17.34/29]
dhcp4: false
optional: true
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
version: 2
Configure keepalived (again, a working config with IP addresses
obfuscated)
global_defs # Block id
{
notification_email {
sysadm...@blah.com
}
notification_email_from keepali...@system3.hq.blah.com
smtp_server 10.22.11.7 # IP
smtp_connect_timeout 30 # integer, seconds
router_id system3 # string identifying the machine,
# (doesn't have to be hostname).
vrrp_mcast_group4 224.0.0.18 # optional, default 224.0.0.18
vrrp_mcast_group6 ff02::12 # optional, default ff02::12
enable_traps # enable SNMP traps
}
vrrp_sync_group collection {
group {
wan
lan
phone
}
vrrp_instance wan {
state MASTER
interface eth2
virtual_router_id 77
priority 150
advert_int 1
smtp_alert
authentication {
auth_type PASS
auth_pass BlahBlah
}
virtual_ipaddress {
12.13.14.20
}
}
vrrp_instance lan {
state MASTER
interface eth3
virtual_router_id 78
priority 150
advert_int 1
smtp_alert
authentication {
auth_type PASS
auth_pass MoreBlah
}
virtual_ipaddress {
10.22.11.13/24
}
}
vrrp_instance phone {
state MASTER
interface eth4
virtual_router_id 79
priority 150
advert_int 1
smtp_alert
authentication {
auth_type PASS
auth_pass MostBlah
}
virtual_ipaddress {
10.22.14.3/24
}
}
At boot the affec
[Touch-packages] [Bug 1819074] Re: Keepalived < 2.0.x in Ubuntu 18.04 LTS not compatible with systemd-networkd
*** This bug is a duplicate of bug 1815101 *** https://bugs.launchpad.net/bugs/1815101 The following 3 bugs: https://bugs.launchpad.net/bugs/1815101 https://bugs.launchpad.net/bugs/1819074 https://bugs.launchpad.net/bugs/1810583 Have the same root cause: the fact that systemd-network messes with secondary IP addresses in NICs managed by systemd. I'm marking all other cases as a duplicate of LP: #1815101. TODO here is the following: - There are mainly 2 "fixes" for this issue: 1) keepalived is able to recognize systemd-networkd changes and change cluster status in order to reconfigure managed NICs (keepalived (> 2.0.x)). 2) systemd-networkd implements a new stanza (KeepConfiguration=) to systemd service unit files in order to fix not only this behavior but all those HA related software that manages secondary IPs and/or aliases to NICs being managed by systemd-networkd. I think the most appropriate would make sure those 2 features work in Eoan, both, together, and then make sure the SRUs are done to Disco and Bionic. One problem w/ the item (2) is that netplan will also have to support the new "KeepConfiguration=" systemd service file stanza, but, the fix (2) is more appropriate for all other HA related softwares controlling virtual IPs (CTDB, Pacemaker, and so ...). ** This bug has been marked a duplicate of bug 1815101 [master] Restarting systemd-networkd breaks keepalived clusters ** Tags removed: server-next -- 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/1819074 Title: Keepalived < 2.0.x in Ubuntu 18.04 LTS not compatible with systemd- networkd Status in keepalived package in Ubuntu: Fix Released Status in netplan.io package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in keepalived source package in Bionic: Triaged Status in netplan.io source package in Bionic: New Status in systemd source package in Bionic: New Bug description: Systemd-networkd clobbers VIPs placed by other daemons on any reconfiguration triggering systemd-networkd restart (netplan apply for example). Keepalived < version 2.0.x will not restore a VIP lost in this fashion, breaking high availability on Ubuntu 18.04 LTS. A backport for keepalived >= 2.0.x should fix the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1819074/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived clusters
Based on comment #12, and other comments from other duplicate cases, I'll summarize here in a better (and consolidated way) how to reproduce the issue, how to mitigate it using the dummy workaround, and how to fix it (with the backports/merge requests). At the end I might provide a PPA asking for feedback. ** Changed in: netplan Status: Invalid => Confirmed ** Changed in: keepalived (Ubuntu) Status: Triaged => Confirmed ** Changed in: systemd (Ubuntu) Status: Triaged => Confirmed ** Also affects: keepalived (Ubuntu Eoan) Importance: Undecided Status: Confirmed ** Also affects: systemd (Ubuntu Eoan) Importance: Undecided Status: Confirmed ** Also affects: keepalived (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: keepalived (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: keepalived (Ubuntu Bionic) Status: New => Confirmed ** Changed in: keepalived (Ubuntu Disco) Status: New => Confirmed ** Changed in: systemd (Ubuntu Bionic) Status: New => Confirmed ** Changed in: systemd (Ubuntu Disco) Status: New => Confirmed ** Changed in: keepalived (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: keepalived (Ubuntu Disco) Importance: Undecided => Medium ** Changed in: keepalived (Ubuntu Eoan) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Disco) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Eoan) Importance: Undecided => Medium ** Changed in: keepalived (Ubuntu Bionic) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) ** Changed in: keepalived (Ubuntu Disco) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) ** Changed in: keepalived (Ubuntu Eoan) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) ** Changed in: systemd (Ubuntu Disco) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) ** Changed in: systemd (Ubuntu Eoan) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) ** Changed in: netplan Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) ** Changed in: systemd (Ubuntu Eoan) Status: Confirmed => In Progress ** Changed in: keepalived (Ubuntu Eoan) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1815101 Title: [master] Restarting systemd-networkd breaks keepalived clusters Status in netplan: Confirmed Status in keepalived package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Status in keepalived source package in Bionic: Confirmed Status in systemd source package in Bionic: Confirmed Status in keepalived source package in Disco: Confirmed Status in systemd source package in Disco: Confirmed Status in keepalived source package in Eoan: In Progress Status in systemd source package in Eoan: In Progress Bug description: Configure netplan for interfaces, for example (a working config with IP addresses obfuscated) network: ethernets: eth0: addresses: [192.168.0.5/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth2: addresses: - 12.13.14.18/29 - 12.13.14.19/29 gateway4: 12.13.14.17 dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth3: addresses: [10.22.11.6/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth4: addresses: [10.22.14.6/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth7: addresses: [9.5.17.34/29] dhcp4: false optional: true nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] version: 2 Configure keepalived (again, a working config with IP addresses obfu
[Touch-packages] [Bug 1731467] Re: Cannot pair BLE remote devices when using combo BT SoC
** Changed in: bluez (Ubuntu) Assignee: Konrad Zapałowicz (kzapalowicz) => (unassigned) -- 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/1731467 Title: Cannot pair BLE remote devices when using combo BT SoC Status in bluez package in Ubuntu: In Progress Status in linux package in Ubuntu: Fix Released Status in bluez source package in Xenial: New Status in linux source package in Xenial: Fix Released Status in bluez source package in Zesty: New Status in linux source package in Zesty: Fix Released Status in bluez source package in Artful: New Status in linux source package in Artful: Fix Released Bug description: It has been observed that sometimes it is not possible to pair with BLE remote devices when the host system is using combo (WiFi + BT) chip. The root cause of the disconnection has been identified as coming from the internal to bluez timeout. If bluez does not hear any reply from for two seconds the link is automagically disconnected. The reason fro the silence is not however a failure of the remote device but quite often a delay in the WiFi/BT combo driver that causes the packages not to reach the bluez stack. [Impact] Not possible to pair BLE remote devices such as sensors and such with Ubuntu when the host system uses BT+WiFi combo SoC. The connection attempt is disturbed with a timeout. [Fix] It has been fixed by increasing the timeout value from 2 seconds to 4 seconds. It is enough for the events to reach the stack (measured that it takes between 3 and 3.5 seconds). [Testcase] Tested with the device that failed to connect to Ubuntu Core gateway. It fails w/o the patch, it connects just fine with the patch applied. [Regression Potential] Very small. The increased timeout is taken into consideration only for new and scan report triggered connections. It will not make any already working device to fail to pair. [Other Info] The bug has been discussed and fixed here: https://marc.info/?l=linux-bluetooth&m=150824844606937&w=2 [Patch] https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth- next.git/commit/?id=1f01d8be0e6a04bd682a55f6d50c14c1679e7571 The patch has been accepted by the upstream and will be a part of the next kernel release. Currently in the bluetooth-next tree. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1731467/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843730] Re: dee ftbfs in eoan (all architectures)
** Changed in: dee (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dee in Ubuntu. https://bugs.launchpad.net/bugs/1843730 Title: dee ftbfs in eoan (all architectures) Status in dee package in Ubuntu: In Progress Bug description: https://launchpadlibrarian.net/441262638/buildlog_ubuntu-eoan- amd64.dee_1.2.7+17.10.20170616-4ubuntu1_BUILDING.txt.gz deprecated glib/gtk symbols To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dee/+bug/1843730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1620636] Re: Fails to pair with Bose QC35 headphones
** Changed in: bluez (Ubuntu) Assignee: Konrad Zapałowicz (kzapalowicz) => (unassigned) -- 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/1620636 Title: Fails to pair with Bose QC35 headphones Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: In Progress Bug description: I am unable to pair the Bose QC35 BT headphones with Ubuntu, either Ubuntu desktop running 16.04 LTS with bluez 5.37 (also tried bluez 5.41 from installed from yakkety archive), nor using Ubuntu Touch rc- proposed build for Turbo #174. I'm trying to pair through the normal bluetooth control panel brought up through the bluetooth indicator. I've attached some logs that show it failing to pair. If I can provide anymore useful information about the headphones, please let me know. Syslog with bluetoothd debugging enabled: http://pastebin.ubuntu.com/23141394/ btmon output: http://pastebin.ubuntu.com/23141446/ bluetoothctl output: http://pastebin.ubuntu.com/23141510/ With Linux kernel 4.8.0 and bluez 4.52: --- bluetoothctl: http://pastebin.ubuntu.com/23256457/ btmon: http://pastebin.ubuntu.com/23256471/ To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620636/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1840510] Re: Please enable PGO and LTO for arm64
To clarify, that's the release schedule for python 3.7.5. The pgo/lto change for arm64 is already in the 19.10 Ubuntu release of python3 (3.7.4), so once the 3.7.5 version is released upstream, then Debian will update to it, then Ubuntu 19.10 (or 20.04) will update to it, then it will be backported to 18.04. -- 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/1840510 Title: Please enable PGO and LTO for arm64 Status in python3-defaults package in Ubuntu: New Bug description: The rules file conditionally enables PGO and LTO in the python3 build and while it's enabled for many platforms it's not enabled for arm64. This is worth about 30% performance. Please enable it. A patch is available here with the original debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934812 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1840510/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1840510] Re: Please enable PGO and LTO for arm64
I've been told that this is planned for the 3.7.5 release of python3.7 in 18.04. The release schedule for that is here: https://www.python.org/dev/peps/pep-0537/#id4 -- 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/1840510 Title: Please enable PGO and LTO for arm64 Status in python3-defaults package in Ubuntu: New Bug description: The rules file conditionally enables PGO and LTO in the python3 build and while it's enabled for many platforms it's not enabled for arm64. This is worth about 30% performance. Please enable it. A patch is available here with the original debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934812 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1840510/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843730] Re: dee ftbfs in eoan (all architectures)
Disabling the Werror use workarounds the glib depreciation but hits a vapigen error, ricotz shared that patch as a 'crude hack, just to have it built' https://paste.debian.net/plain/1100570 Unsure if we want to go this way or if there is a better/nicer way to fix it ... Robert you have more experience with vala issue, maybe you have an opinion there? ** Changed in: dee (Ubuntu) Status: In Progress => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dee in Ubuntu. https://bugs.launchpad.net/bugs/1843730 Title: dee ftbfs in eoan (all architectures) Status in dee package in Ubuntu: Confirmed Bug description: https://launchpadlibrarian.net/441262638/buildlog_ubuntu-eoan- amd64.dee_1.2.7+17.10.20170616-4ubuntu1_BUILDING.txt.gz deprecated glib/gtk symbols To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dee/+bug/1843730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843099] Re: Unattended upgrades does not work on shutdown
It went further but still failed to update - here it is via the dbus shutdown command you supplied: ### unattended-upgrades.log: 2019-09-13 14:09:43,981 INFO Initial blacklisted packages: 2019-09-13 14:09:43,982 INFO Initial whitelisted packages: 2019-09-13 14:09:43,982 INFO Starting unattended upgrades script 2019-09-13 14:09:43,983 INFO Allowed origins are: o=Ubuntu-aptly,a=xenial 2019-09-13 14:10:01,496 INFO Packages that will be upgraded: apport apt-transport-https base-files bash bind9-host bsdutils btrfs-tools busybox-initramfs busybox-static bzip2 ca-certificates cloud-guest-utils cloud-initramfs-copymods cloud-initramfs-dyn-netconf console-setup console-setup-linux curl dbus dh-python distro-info-data dns-root-data dnsmasq-base dnsutils dpkg file friendly-recovery gettext-base git git-man gnupg gpgv grub-common grub-legacy-ec2 grub-pc grub-pc-bin grub2-common hdparm ifupdown initramfs-tools initramfs-tools-bin initramfs-tools-core iproute2 isc-dhcp-client isc-dhcp-common keyboard-configuration kmod krb5-locales libapparmor-perl libapparmor1 libasprintf0v5 libbind9-140 libblkid1 libbz2-1.0 libc-bin libcurl3-gnutls libdb5.3 libdbus-1-3 libdns-export162 libdns162 libelf1 libexpat1 libfdisk1 libgcrypt20 libglib2.0-0 libglib2.0-data libgnutls-openssl27 libgnutls30 libicu55 libisc-export160 libisc160 libisccc140 libisccfg140 libk5crypto3 libkmod2 libldap-2.4-2 liblwres141 libmagic1 libmount1 libmspack0 libpam-modules libpam-modules-bin libpam-runtime libpam-systemd libpam0g libpci3 libperl5.22 libplymouth4 libpng12-0 libpolkit-agent-1-0 libpolkit-backend-1-0 libpolkit-gobject-1-0 libprocps4 libpython3.5 libpython3.5-minimal libpython3.5-stdlib libsasl2-2 libsasl2-modules libsasl2-modules-db libseccomp2 libslang2 libsmartcols1 libsqlite3-0 libssl1.0.0 libsystemd0 libudev1 libuuid1 libx11-6 libx11-data libxml2 libxslt1.1 linux-firmware linux-headers-generic locales login lshw mount multiarch-support ntfs-3g open-iscsi open-vm-tools openssh-client openssh-server openssh-sftp-server openssl overlayroot passwd patch pciutils perl perl-base perl-modules-5.22 plymouth plymouth-theme-ubuntu-text policykit-1 procps python-apt-common python-lxml python3-apport python3-apt python3-distupgrade python3-problem-report python3-requests python3-software-properties python3-update-manager python3-urllib3 python3.5 python3.5-minimal resolvconf rsyslog shared-mime-info software-properties-common sosreport squashfs-tools sudo systemd systemd-sysv tzdata ubuntu-minimal ubuntu-release-upgrader-core ubuntu-server ubuntu-standard udev uidmap update-manager-core update-notifier-common ureadahead util-linux uuid-runtime vim vim-common vim-runtime vim-tiny vlan wget wireless-regdb xdg-user-dirs 2019-09-13 14:10:01,497 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2019-09-13 14:10:13,935 WARNING SIGTERM received, will stop 2019-09-13 14:10:16,810 WARNING SIGTERM received, will stop 2019-09-13 14:10:19,803 WARNING SIGTERM received, will stop 2019-09-13 14:10:22,772 WARNING SIGTERM received, will stop 2019-09-13 14:10:22,779 WARNING SIGTERM received, will stop 2019-09-13 14:10:25,764 WARNING SIGTERM received, will stop 2019-09-13 14:10:25,820 WARNING SIGTERM received, will stop 2019-09-13 14:10:28,713 WARNING SIGTERM received, will stop 2019-09-13 14:10:28,873 WARNING SIGTERM received, will stop 2019-09-13 14:10:31,832 WARNING SIGTERM received, will stop 2019-09-13 14:10:34,086 WARNING SIGNAL received, stopping 2019-09-13 14:10:34,697 WARNING SIGTERM received, will stop 2019-09-13 14:10:34,779 WARNING SIGTERM received, will stop ### unattended-upgrades-shutdown.log 2019-09-13 14:09:17,147 DEBUG - Waiting for signal to start operation 2019-09-13 14:09:43,639 DEBUG - Starting countdown of 25.0 minutes 2019-09-13 14:09:43,639 DEBUG - Initializing apt_pkg configuration 2019-09-13 14:09:43,640 DEBUG - starting unattended-upgrades in shutdown mode 2019-09-13 14:09:43,645 WARNING - Running unattended-upgrades in shutdown mode 2019-09-13 14:09:43,645 DEBUG - Running plymouth --text 2019-09-13 14:09:43,657 WARNING - Unattended-upgrade in progress during shutdown, please don't turn off the computer 2019-09-13 14:09:43,657 DEBUG - Running plymouth --text 2019-09-13 14:09:46,643 WARNING - Unattended-upgrade in progress during shutdown, please don't turn off the computer 2019-09-13 14:09:46,644 DEBUG - Running plymouth --text 2019-09-13 14:09:49,647 WARNING - Unattended-upgrade in progress during shutdown, please don't turn off the computer 2019-09-13 14:09:49,648 DEBUG - Running plymouth --text 2019-09-13 14:09:52,650 WARNING - Unattended-upgrade in progress during shutdown, please don't turn off the computer 2019-09-13 14:09:52,651 DEBUG - Running plymouth --text 2019-09-13 14:09:55,654 WARNING - Unattended-upgrade in progress during shutdown, please don't turn off the computer 2019-09-13 14:09:55,654 DEBUG - Running plymouth --text 2019-09-13 14:09:58,656 WARNING - Una
[Touch-packages] [Bug 1843099] Re: Unattended upgrades does not work on shutdown
Using reboot did more of the same. At this point the Xenial version is 16.04.4 - we have a snapshot from 2019-05-28. unattended-upgrades was at 0.90ubuntu0.9 but salt config management upgrades to 1.1ubuntu1.18.04.7~16.04.3 once the machine has salt installed. We pretty much update a symlink which has two publish dates, 2019-05-28 (old) to 2019-09-04 (new). I'm not sure if that's playing a role but I do know 0.90ubuntu0.9 worked for me last time. # As root dbus-send --system --print-reply \ --dest=org.freedesktop.login1 /org/freedesktop/login1 \ org.freedesktop.login1.Manager.PowerOff boolean:false dbus-send --system --print-reply \ --dest=org.freedesktop.login1 /org/freedesktop/login1 \ org.freedesktop.login1.Manager.Reboot boolean:false -- 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/1843099 Title: Unattended upgrades does not work on shutdown Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu * Ubuntu Xenial 16.04.6 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center * 1.1ubuntu1.18.04.7~16.04.3 3) What you expected to happen * Packages to be upgraded on reboot / shutdown. 4) What happened instead * The host just rebooted. Didn't perform upgrades. No useful output either until I enabled debug logging in the systemd unit file. I'm reporting a new bug but this is very similar to #1806487 and I'm actually wondering if it resurfaced somehow. We're running Ubuntu Xenial 16.04.6 which has 1.1ubuntu1.18.04.7~16.04.3 installed. I see that #1806487 was resolved with 1.1ubuntu1.18.04.7~16.04.2. However I'm seeing similar behavior. So far I've modified systemd to see if anything stands out. I do have an strace and then just debug mode. Unless needed, simply put, this is what a reboot with debug logging looks like (i.e. unattended-upgrades-shutdown.log): 2019-09-06 09:20:04,871 DEBUG - Waiting for signal to start operation 2019-09-06 09:20:43,996 WARNING - SIGTERM or SIGHUP received, stopping unattended-upgradesonly if it is running 2019-09-06 09:20:43,996 DEBUG - Starting countdown of 25.0 minutes 2019-09-06 09:20:43,997 DEBUG - get_lock returned 7 2019-09-06 09:20:43,997 DEBUG - lock not taken I hope that helps, please let me know if you need anything else from me or if I can provide any more information. I've done this many times before, this is the first time it hasn't worked. When I patched around the end of May, all went well. My other variants worked, well mainly Trusty but that's EOL for public access. Bionic doesn't seem to have anything it needs to update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1843099/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1842349] Re: Reconsider conditions for setting language and formats
This bug was fixed in the package accountsservice - 0.6.55-0ubuntu9 --- accountsservice (0.6.55-0ubuntu9) eoan; urgency=medium * debian/patches/0010-set-language.patch: - Simplify logic when to set language and formats (LP: #1842349). * debian/control: - Change Maintainer to Ubuntu Developers. -- Gunnar Hjalmarsson Fri, 13 Sep 2019 22:05:00 +0200 ** Changed in: accountsservice (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1842349 Title: Reconsider conditions for setting language and formats Status in accountsservice package in Ubuntu: Fix Released Bug description: In connection with the upgrade to 0.6.50 (bug #1789502) the fallback values from /etc/default/locale were set on initialization. While that addresses some aspects of the upstream changes, a need remains to reconsider the conditions in user_change_language_authorized_cb() and user_change_formats_locale_authorized_cb(). Currently it does not take into account if variables were previously set in ~/.pam_environment or not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1842349/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 357732] Re: cups always prints with the default page size
10 years after the initial bug report and it looks like I'm experiencing the same bug. In my case, I'm trying to print some pages that are 11" x 17" but it is received at the printer as US Letter size. I did confirm that /etc/papersize contains "letter", and changing that to "A4" also changes what is received by the printer. The print dialog confirms that 11x17 has been selected, but that's overwritten behind the scenes somewhere. Since 11x17 is a custom size in the print dialog, I'm not sure what I should put in /etc/papersize to make it work correctly. -- 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/357732 Title: cups always prints with the default page size Status in GS-GPL: Invalid Status in cups package in Ubuntu: Fix Released Status in ghostscript package in Ubuntu: Invalid Status in cups source package in Intrepid: Invalid Status in ghostscript source package in Intrepid: Invalid Status in cups source package in Jaunty: Fix Released Status in ghostscript source package in Jaunty: Invalid Bug description: After the upgrade to Jaunty some users experience that a part of the page is cut when printing, or other kinds of misalignment. (A fix is available, see below) Details: Cups does not print in any other page size than the one set in /etc/papersize, if the requested page size is specified as a job option rather than within the PS file. Pages are passed through "gs -sDEVICE=pdfwrite ..." which sets the page size to the default page size. Yet, I don't know whether this is a bug in ghostscript or the intended behavior of ghostscript and a bug in cups. Since the upgrade to Jauny beta, I experienced that evince would shift a document up when printing. It is reproducible. I print in A4 on a Canon IR3170Ci. The printed output is translated up. The upper part of the contents in not visible. I also tried another printer driver (hpijs instead of post-script) and did not observe any improvement. Changing /etc/papersize from letter to a4 allows me to print in a4. Printing from evince also working fine in intrepid. To reproduce the bug: lpr -omedia=A3 testpage.ps There should not be a problem if the postscript file itself requests a page size. FIX: # (For simplicity, just paste this section to a terminal.) # Download the attached pstopdf and install it in /usr/lib/cups/filter/ cd /tmp wget http://launchpadlibrarian.net/25537150/pstopdf sudo cp pstopdf /usr/lib/cups/filter/ # Then change the permissions of the installed file: sudo chmod ugo+rx /usr/lib/cups/filter/pstopdf # that's all. To manage notifications about this bug go to: https://bugs.launchpad.net/gs-gpl/+bug/357732/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843975] [NEW] install not completing due to hardlink failure
Public bug reported: Processing triggers for initramfs-tools (0.133ubuntu10) ... ln: failed to create hard link '/boot/initrd.img-4.15.0-1045-raspi2.dpkg-bak' => '/boot/initrd.img-4.15.0-1045-raspi2': Operation not permitted update-initramfs: Generating /boot/initrd.img-4.15.0-1045-raspi2 Unsupported platform. run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 1 dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1) I am assuming that this is due to the /boot partition on the Raspberry Pi being Fat16 and not supporting hardlinks. Use a copy instead? Keeps trying to complete every time I run apt-get. You might find these helpful in seeing how they handled it. https://ubuntu-mate.org/raspberry-pi/ubuntu-mate-18.04.2-beta1-desktop-armhf+raspi-ext4.img.xz https://archive.raspbian.org/raspbian/dists/buster/ https://ubuntu-mate.org/raspberry-pi/ I used these instructions ( https://ubuntu-mate.community/t/how-to-get- ubuntu-mate-18-04-up-on-raspberry-pi-4/20049 ) and then upgraded some packages to eoan. lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 sudo apt-get update && sudo apt-get install --no-install-recommends e2fsprogs unar uget aria2 filezilla transmission smtube smplayer mplayer vlc bleachbit gparted openvpn gadmin-samba gpart gpaint curl thunderbird-gnome-support youtube-dl cifs-utils ntfs-3g ntp hardlink mesa-va-drivers mesa-vdpau-drivers mesa-vulkan-drivers Thanks in advance. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1843975 Title: install not completing due to hardlink failure Status in initramfs-tools package in Ubuntu: New Bug description: Processing triggers for initramfs-tools (0.133ubuntu10) ... ln: failed to create hard link '/boot/initrd.img-4.15.0-1045-raspi2.dpkg-bak' => '/boot/initrd.img-4.15.0-1045-raspi2': Operation not permitted update-initramfs: Generating /boot/initrd.img-4.15.0-1045-raspi2 Unsupported platform. run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 1 dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1) I am assuming that this is due to the /boot partition on the Raspberry Pi being Fat16 and not supporting hardlinks. Use a copy instead? Keeps trying to complete every time I run apt-get. You might find these helpful in seeing how they handled it. https://ubuntu-mate.org/raspberry-pi/ubuntu-mate-18.04.2-beta1-desktop-armhf+raspi-ext4.img.xz https://archive.raspbian.org/raspbian/dists/buster/ https://ubuntu-mate.org/raspberry-pi/ I used these instructions ( https://ubuntu-mate.community/t/how-to- get-ubuntu-mate-18-04-up-on-raspberry-pi-4/20049 ) and then upgraded some packages to eoan. lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 sudo apt-get update && sudo apt-get install --no-install-recommends e2fsprogs unar uget aria2 filezilla transmission smtube smplayer mplayer vlc bleachbit gparted openvpn gadmin-samba gpart gpaint curl thunderbird-gnome-support youtube-dl cifs-utils ntfs-3g ntp hardlink mesa-va-drivers mesa-vdpau-drivers mesa-vulkan-drivers Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1843975/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
