[Bug 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"
Split up unicode-data into its own bug; bug 1838323. ** No longer affects: unicode-data (Ubuntu) ** No longer affects: gnome-characters (Ubuntu Xenial) ** No longer affects: gnome-characters (Ubuntu Disco) ** No longer affects: gucharmap (Ubuntu Xenial) ** No longer affects: gucharmap (Ubuntu Bionic) ** No longer affects: gucharmap (Ubuntu Disco) ** No longer affects: icu (Ubuntu Xenial) ** No longer affects: icu (Ubuntu Bionic) ** No longer affects: icu (Ubuntu Disco) ** No longer affects: unicode-data (Ubuntu Xenial) ** No longer affects: unicode-data (Ubuntu Bionic) ** No longer affects: unicode-data (Ubuntu Disco) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to fonts-noto-cjk in Ubuntu. https://bugs.launchpad.net/bugs/1828884 Title: [META] Handling Japanese new era "令和 (Reiwa)" To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1828884/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"
icu split up into bug 1838322. ** Changed in: openjdk-8 (Ubuntu Xenial) Status: New => Fix Released ** Changed in: openjdk-8 (Ubuntu Bionic) Status: New => Fix Released ** Changed in: openjdk-8 (Ubuntu Disco) Status: New => Fix Released ** No longer affects: icu (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to fonts-noto-cjk in Ubuntu. https://bugs.launchpad.net/bugs/1828884 Title: [META] Handling Japanese new era "令和 (Reiwa)" To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1828884/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1838321] Re: Support Japanese new era "令和 (Reiwa)"
Fixed in eoan, just needs a rebuild in other releases with a newer unicode-data that has Reiwa in it. Still dependent on font having the actual glyphs included (not the case at this moment in eoan). ** Also affects: gucharmap (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: gucharmap (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gucharmap in Ubuntu. https://bugs.launchpad.net/bugs/1838321 Title: Support Japanese new era "令和 (Reiwa)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gucharmap/+bug/1838321/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"
gucharmap split up into bug 1838321 ** No longer affects: gucharmap (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gucharmap in Ubuntu. https://bugs.launchpad.net/bugs/1828884 Title: [META] Handling Japanese new era "令和 (Reiwa)" To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1828884/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1838321] [NEW] Support Japanese new era "令和 (Reiwa)"
Public bug reported: [Background] Many packages are affected by the requirement to support the new era "Reiwa" (令和） This is the meta bug to track packages that need fixes; which packages have already been SRUd to previous releases, how to prioritize the work needed, and general test cases for verifying that things are working as expected. [Impact] Users who run Ubuntu in Japanese. [Test cases] 1) Search for character "SQUARE ERA NAME" 2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and "SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and that the glyphs are readable: - SQUARE ERA NAME HEISEI: ㍻ - SQUARE ERA NAME REIWA: 令和 (in a single glyph) Display of the Reiwa square glyph is font-specific; it may show simply as a empty square or a square with hex characters. If that is the case, the unicode data supports the new character, but the selected font does not include the new glyph. [Regression potential] This is a potentially large change as it impacts font display, character sets as well as date conversions. As such, extreme care should be taken to ensure that regressions are avoided, such that dates previous to May 1, 2019 continue to display as before, and dates onward are displayed with the new era symbols. The included test cases account for verifying the continued behavior or previous dates. ** Affects: gucharmap (Ubuntu) Importance: Undecided Status: New ** Affects: gucharmap (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: gucharmap (Ubuntu Disco) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gucharmap in Ubuntu. https://bugs.launchpad.net/bugs/1838321 Title: Support Japanese new era "令和 (Reiwa)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gucharmap/+bug/1838321/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"
Looks like noto sources now have the right glyphs (since their April 9 release, actually). It will need an update both in Debian and Ubuntu. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gucharmap in Ubuntu. https://bugs.launchpad.net/bugs/1828884 Title: [META] Handling Japanese new era "令和 (Reiwa)" To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1828884/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"
mozc appears to be all done (LP: #1823444) ** Changed in: mozc (Ubuntu Xenial) Status: New => Fix Released ** Changed in: mozc (Ubuntu Bionic) Status: New => Fix Released ** Changed in: mozc (Ubuntu Cosmic) Status: New => Fix Released ** Changed in: mozc (Ubuntu Disco) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gucharmap in Ubuntu. https://bugs.launchpad.net/bugs/1828884 Title: [META] Handling Japanese new era "令和 (Reiwa)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/1828884/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"
unicode-data in eoan does include Reiwa. Reverse-depends probably still need to be rebuilt (I'm testing gucharmap which seemed easy enough to patch to work). ** Changed in: unicode-data (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gucharmap in Ubuntu. https://bugs.launchpad.net/bugs/1828884 Title: [META] Handling Japanese new era "令和 (Reiwa)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/1828884/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"
Oops; picked the wrong openjdk... FWIW; according to the email by Mitsuya Shibata, openjdk 8 and 11 at least are affected (so, everything prior to disco if updates are not applied. Openjdk-8 updates appear to already be at 8u212, which should include Reiwa support. Marking as Fix Released so we can see at a glance that it's already been covered. ** Also affects: openjdk-13 (Ubuntu) Importance: Undecided Status: New ** Also affects: icu (Ubuntu) Importance: Undecided Status: New ** Also affects: unicode-data (Ubuntu) Importance: Undecided Status: New ** Also affects: poppler-data (Ubuntu) Importance: Undecided Status: New ** Description changed: [Background] Many packages are affected by the requirement to support the new era "Reiwa" (令和） This is the meta bug to track packages that need fixes; which packages have already been SRUd to previous releases, how to prioritize the work needed, and general test cases for verifying that things are working as expected. [Impact] Users who run Ubuntu in Japanese. [Test cases] == Date conversion == On applications that support writing dates in long form, or with symbols to denote era (either in X00.00.00 format or in GG1G5G1G format (G- glyph; X- character): 1) Enable date formatting in each of the above formats that are supported (long form or symbols) 2) Type in '2019/05/01' to be formatted, verify that it shows as "令和1年5月1日" or "R1.05.01" 3) Type in '2019/04/30' to be formatted, verify that it shows as "平成31年4月30日" or "H31.4.30" == Date output == 1) Set date to 2019/05/01 2) Output date; verify that the year it is displayed as "令和元年" 3) Set date to 2019/04/30 4) Output date; verify that the year is diplayed as "平成31年" === Displaying formatted year for Japanese era with glibc === Run: LC_ALL=ja_JP.utf8 date +%EY -d 20190430 # previous era (should still work as before SRUs) or LC_ALL=ja_JP.utf8 date +%EY -d 20190501 # new era (should now correctly display the new era) == Character maps / font support == 1) Search for character "SQUARE ERA NAME" 2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and "SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and that the glyphs are readable: - SQUARE ERA NAME HEISEI: ㍻ - SQUARE ERA NAME REIWA: 令和 (in a single glyph) Display of the Reiwa square glyph is font-specific; it may show simply as a empty square or a square with hex characters. If that is the case, the unicode data supports the new character, but the selected font does not include the new glyph. == Typing / input methods == 1) Type in 'heisei' 2) Verify that the input method in use gives you an option "平成", and optionally also the square era glyph. 3) Type in 'reiwa' 4) Verify that the input method in use gives you an option that includes "令和", and possibly also the square era glyph (if supported for Heisei) 5) Type in the following strings, and verify that the options are provided in the input method: - * "れいわ"(reiwa) => "令和" - * "れいわ"(reiwa) => "㋿" - * "２０１８ねん"(2018nenn) => "平成三十年" - * "２０１８ねん"(2018nenn) => "平成三十年" - * "２０１９ねん"(2019nenn) => "平成三十一年" - * "２０１９ねん"(2019nenn) => "令和元年" - * "２０２０ねん"(2020nenn) => "令和二年" + * "れいわ"(reiwa) => "令和" + * "れいわ"(reiwa) => "㋿" + * "２０１８ねん"(2018nenn) => "平成三十年" + * "２０１９ねん"(2019nenn) => "平成三十一年" + * "２０１９ねん"(2019nenn) => "令和元年" + * "２０２０ねん"(2020nenn) => "令和二年" /!\ Some fonts, like fonts-noto-cjk, currently have no glyph for U+32FF. [Regression potential] This is a potentially large change as it impacts font display, character sets as well as date conversions. As such, extreme care should be taken to ensure that regressions are avoided, such that dates previous to May 1, 2019 continue to display as before, and dates onward are displayed with the new era symbols. The included test cases account for verifying the continued behavior or previous dates. ** No longer affects: openjdk-13 (Ubuntu) ** Also affects: openjdk-8 (Ubuntu) Importance: Undecided Status: New ** Changed in: openjdk-8 (Ubuntu) Status: New => Fix Released ** Also affects: gucharmap (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: icu (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: unicode-data (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: poppler-data (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: mozc (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: libreoffice (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: libreoffice-l10n (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: openjdk-8 (Ubuntu Disco) Importance: Undecided Status: New **
[Bug 1162475] Re: [hostnamed] Changing hostname doesn't update /etc/hosts
I don't think it's *-control-center. At the time, that was filed there by pitti, who correctly pointed out that something might need to depend on libnss-myhostname (from systemd) for a fallback to resolving hostname via just /etc/hostname (since /etc/hosts isn't changed). At this point though, it looks like this is no longer required. Now, AFAICT the desktop correctly calls to systemd via dbus to ask for the change. I'll leave to you to make sure this is indeed the case (since you had commented on the bug previously, and I can't see any issues changing hostname as it is now, but maybe I'm not quite doing the same tests you were). unity-control-center is an obvious Won't Fix for Eoan or Disco, but I'll let the Desktop Team decide whether this needs to be fixed in other releases. Finally, this is still assigned to systemd, low priority, because hostnamed *doesn't* change /etc/hosts, and probably should (at the very least for consistency, to avoid keeping a reference to an old name for the system); but I didn't notice ill effects from not changing that file. sudo certainly doesn't hang here trying to resolve the new or old hostname. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1162475 Title: [hostnamed] Changing hostname doesn't update /etc/hosts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1162475/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1162475] Re: [hostnamed] Changing hostname doesn't update /etc/hosts
** Tags removed: rls-x-incoming ** Tags added: rls-ee-incoming ** Also affects: gnome-control-center (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: unity-control-center (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Xenial) Status: New => Triaged ** Changed in: systemd (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: unity-control-center (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1162475 Title: [hostnamed] Changing hostname doesn't update /etc/hosts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1162475/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"
** Also affects: gucharmap (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntu -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gucharmap in Ubuntu. https://bugs.launchpad.net/bugs/1828884 Title: [META] Handling Japanese new era "令和 (Reiwa)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-characters/+bug/1828884/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828884] Re: Handling Japanese new era "令和 (Reiwa)"
mozc appears to already be Fix Released for most releases; this has been handled as bug 1823444. ** Description changed: [Background] Many packages are affected by the requirement to support the new era "Reiwa" (令和） This is the meta bug to track packages that need fixes; which packages have already been SRUd to previous releases, how to prioritize the work needed, and general test cases for verifying that things are working as expected. [Impact] Users who run Ubuntu in Japanese. [Test cases] == Date conversion == On applications that support writing dates in long form, or with symbols to denote era (either in X00.00.00 format or in GG1G5G1G format (G- glyph; X- character): 1) Enable date formatting in each of the above formats that are supported (long form or symbols) 2) Type in '2019/05/01' to be formatted, verify that it shows as "令和1年5月1日" or "R1.05.01" 3) Type in '2019/04/30' to be formatted, verify that it shows as "平成31年4月30日" or "H31.4.30" == Date output == 1) Set date to 2019/05/01 2) Output date; verify that the year it is displayed as "令和元年" 3) Set date to 2019/04/30 4) Output date; verify that the year is diplayed as "平成31年" === Displaying formatted year for Japanese era with glibc === Run: LC_ALL=ja_JP.utf8 date +%EY -d 20190430 # previous era (should still work as before SRUs) or LC_ALL=ja_JP.utf8 date +%EY -d 20190501 # new era (should now correctly display the new era) - == Character maps / font support == 1) Search for character "SQUARE ERA NAME" 2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and "SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and that the glyphs are readable: - - SQUARE ERA NAME HEISEI: ㍻ - - SQUARE ERA NAME REIWA: 令和 (in a single glyph) + - SQUARE ERA NAME HEISEI: ㍻ + - SQUARE ERA NAME REIWA: 令和 (in a single glyph) Display of the Reiwa square glyph is font-specific; it may show simply as a empty square or a square with hex characters. If that is the case, the unicode data supports the new character, but the selected font does not include the new glyph. - == Typing / input methods == 1) Type in 'heisei' 2) Verify that the input method in use gives you an option "平成", and optionally also the square era glyph. - 1) Type in 'reiwa' - 2) Verify that the input method in use gives you an option that includes "令和", and possibly also the square era glyph (if supported for Heisei) + 3) Type in 'reiwa' + 4) Verify that the input method in use gives you an option that includes "令和", and possibly also the square era glyph (if supported for Heisei) + 5) Type in the following strings, and verify that the options are provided in the input method: + * "れいわ"(reiwa) => "令和" + * "れいわ"(reiwa) => "㋿" + * "２０１８ねん"(2018nenn) => "平成三十年" + * "２０１８ねん"(2018nenn) => "平成三十年" + * "２０１９ねん"(2019nenn) => "平成三十一年" + * "２０１９ねん"(2019nenn) => "令和元年" + * "２０２０ねん"(2020nenn) => "令和二年" + + /!\ Some fonts, like fonts-noto-cjk, currently have no glyph for U+32FF. [Regression potential] This is a potentially large change as it impacts font display, character sets as well as date conversions. As such, extreme care should be taken to ensure that regressions are avoided, such that dates previous to May 1, 2019 continue to display as before, and dates onward are displayed with the new era symbols. The included test cases account for verifying the continued behavior or previous dates. ** Also affects: mozc (Ubuntu) Importance: Undecided Status: New ** Changed in: mozc (Ubuntu) Status: New => Fix Released ** Summary changed: - Handling Japanese new era "令和 (Reiwa)" + [META] Handling Japanese new era "令和 (Reiwa)" ** Also affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Also affects: libreoffice-l10n (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-characters (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-characters in Ubuntu. https://bugs.launchpad.net/bugs/1828884 Title: [META] Handling Japanese new era "令和 (Reiwa)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1828884/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1806379] Re: [MIR] gnome-shell-extension-desktop-icons
MIR approved. I see no particular issues with the package after reviewing the code; no binary deps in universe, and it's a small package that appears like it should be well maintained in Debian and Ubuntu. ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: New => Fix Committed ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Assignee: Mathieu Trudel-Lapierre (cyphermox) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1806379 Title: [MIR] gnome-shell-extension-desktop-icons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1806379/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1806379] Re: [MIR] gnome-shell-extension-desktop-icons
** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1806379 Title: [MIR] gnome-shell-extension-desktop-icons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1806379/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797236] [NEW] network-manager openvpn settings not being saved
Public bug reported: I'm seeing some weird issue with the new NM + openvpn; if I create a new VPN connection, and add certificate options (verify name exactly, plus TLS auth), these options are not saved, leading to the connection failing. The following versions lead to an invalid connection: ii network-manager 1.12.4-1ubuntu1 amd64 network management framework (daemon and userspace tools) ii network-manager-openvpn 1.8.6-1 amd64 network management framework (OpenVPN plugin core) Reverting to the following versions, things work again: ii network-manager 1.12.2-0ubuntu4 amd64 network management framework (daemon and userspace tools) ii network-manager-openvpn 1.8.4-1 amd64 network management framework (OpenVPN plugin core) If I use an existing connection saved with a prior version of NM, the connection will be successful. If I go open the settings, hit Apply, all advanced TLS settings are wiped. The connection then fails: Oct 10 16:58:52 demeter nm-openvpn[6538]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Oct 10 16:58:52 demeter nm-openvpn[6538]: TCP/UDP: Preserving recently used remote address: [AF_INET]91.189.91.19:443 Oct 10 16:58:52 demeter nm-openvpn[6538]: Attempting to establish TCP connection with [AF_INET]91.189.91.19:443 [nonblock] Oct 10 16:58:53 demeter nm-openvpn[6538]: TCP connection established with [AF_INET]91.189.91.19:443 Oct 10 16:58:53 demeter nm-openvpn[6538]: TCP_CLIENT link local: (not bound) Oct 10 16:58:53 demeter nm-openvpn[6538]: TCP_CLIENT link remote: [AF_INET]xx.xx.xx.xx:443 Oct 10 16:58:53 demeter nm-openvpn[6538]: Connection reset, restarting [0] Oct 10 16:58:53 demeter nm-openvpn[6538]: SIGUSR1[soft,connection-reset] received, process restarting Oct 10 16:58:58 demeter nm-openvpn[6538]: WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info. Oct 10 16:58:58 demeter nm-openvpn[6538]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Oct 10 16:58:58 demeter nm-openvpn[6538]: TCP/UDP: Preserving recently used remote address: [AF_INET6]2001:67c:1562:0:1::1:443 Oct 10 16:58:58 demeter nm-openvpn[6538]: Attempting to establish TCP connection with [AF_INET6]2001:67c:1562:0:1::1:443 [nonblock] Oct 10 16:58:59 demeter nm-openvpn[6538]: TCP: connect to [AF_INET6]:xxx:xx:xx::xx:443 failed: Network is unreachable Oct 10 16:58:59 demeter nm-openvpn[6538]: SIGUSR1[connection failed(soft),init_instance] received, process restarting Oct 10 16:59:04 demeter nm-openvpn[6538]: WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Affects: network-manager-openvpn (Ubuntu) Importance: Undecided Status: New ** Also affects: network-manager-openvpn (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1797236 Title: network-manager openvpn settings not being saved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1797236/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767918] Re: Login password from GDM is shown in plain text on the VT1 console
Bug was confirmed fix, although we don't have a formal version number for the pacakge that was tested, let's mark this verification-done. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1767918 Title: Login password from GDM is shown in plain text on the VT1 console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1767918/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767918] Re: Login password from GDM is shown in plain text on the VT1 console
@Alan, Can you confirm which version of plymouth you had installed? You can use the following command to do so: dpkg -l plymouth | cat -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1767918 Title: Login password from GDM is shown in plain text on the VT1 console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1767918/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767918] Re: Login password from GDM is shown in plain text on the VT1 console
That's not what I mean though. For SRU verification we should aim to have a positive identification of the exact version of the plymouth package that was used for the tests. For example, this can be achieved by looking at 'dpkg -l plymouth | cat': 要望=(U)不明/(I)インストール/(R)削除/(P)完全削除/(H)保持 | 状態=(N)無/(I)インストール済/(C)設定/(U)展開/(F)設定失敗/(H)半インストール/(W)トリガ待ち/(T)トリガ保留 |/ エラー?=(空欄)無/(R)要再インストール (状態,エラーの大文字=異常) ||/ 名前 バージョン アーキテクチ 説明 +++-==-==--== ii plymouth 0.9.3-1ubuntu8 amd64boot animation, logger and I/O multiplexer This is from my PC, on cosmic. The version number on bionic would be different. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1767918 Title: Login password from GDM is shown in plain text on the VT1 console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1767918/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767918] Re: Login password from GDM is shown in plain text on the VT1 console
@Alan, could you please confirm which version of plymouth you have installed for the tests you did? Thanks! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1767918 Title: Login password from GDM is shown in plain text on the VT1 console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1767918/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767918] Re: Login password from GDM is shown in plain text on the VT1 console
** Description changed: - https://gitlab.gnome.org/GNOME/gdm/issues/408 + [Impact] + Sessions in specific circumstances when switching to TTY while plymouth is being activated or deactivated. + + [Test cases] + Steps to reproduce: + 1) Log-in using X11 login via GDM. + 2) Use the desktop for a while. (For some reason I cannot reproduce if I login and then restart after a short while). + 3) In Gnome click System menu -> Power Button -> Restart + 4) Quickly press CTRL-ALT-F1 + + Validate whether your login password is visible on the TTY. + + [Regression Potential] + Possible regressions may include difficulty showing text-mode splash or boot messages given that this changes the state of tty based on plymouth's own activation state. --- - I don't which package this applies to, but I believe the best bet is - GDM. + https://gitlab.gnome.org/GNOME/gdm/issues/408 + + + I don't which package this applies to, but I believe the best bet is GDM. Steps to reproduce: 1) Log-in using X11 login via GDM. 2) Use the desktop for a while. (For some reason I cannot reproduce if I login and then restart after a short while). 3) In Gnome click System menu -> Power Button -> Restart 4) Quickly press CTRL-ALT-F1 5) I see my login password in plain text in the console. Once I saw the login password repeated twice. See attached photo with the login password blanked out. Below the password is the console cursor. ## lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 ## apt-cache policy gdm3 gdm3: Installed: 3.28.0-0ubuntu1 Candidate: 3.28.0-0ubuntu1 Version table: *** 3.28.0-0ubuntu1 500 500 http://nz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-18.19-generic 4.15.17 Uname: Linux 4.15.0-18-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 30 14:54:07 2018 InstallationDate: Installed on 2018-04-13 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Changed in: plymouth (Ubuntu) Assignee: Canonical Foundations Team (canonical-foundations) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1767918 Title: Login password from GDM is shown in plain text on the VT1 console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1767918/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1780996] Re: Convert triggers to noawait
** Changed in: fusiondirectory (Ubuntu Xenial) Status: New => In Progress ** Changed in: fusiondirectory (Ubuntu Xenial) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) ** Changed in: fusiondirectory (Ubuntu Bionic) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1780996/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1780996] Re: Convert triggers to noawait
** Changed in: fusiondirectory (Ubuntu) Status: New => In Progress ** Changed in: fusiondirectory (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1780996/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1780996] Re: Convert triggers to noawait
dovecot for cosmic and bionic already changed to noawait triggers by Debian maintainer. ** Changed in: dovecot (Ubuntu) Status: In Progress => Fix Released ** Changed in: dovecot (Ubuntu Bionic) Status: New => Fix Released ** Changed in: dovecot (Ubuntu Xenial) Status: New => In Progress ** Changed in: dovecot (Ubuntu Xenial) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1780996/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1780996] Re: Convert triggers to noawait
** Changed in: dovecot (Ubuntu) Status: New => In Progress ** Changed in: dovecot (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1780996/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1770082] Re: systemd-networkd not renaming devices on boot
** Also affects: nplan (Ubuntu) Importance: Undecided Status: New ** Changed in: nplan (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1770082 Title: systemd-networkd not renaming devices on boot To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1770082/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768088] Re: can't activate 2 independent reachable interface
Still a bug; if systemd-networkd requires a restart, then systemd- networkd has something that it gets confused about, that we'll need to figure out. ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1768088 Title: can't activate 2 independent reachable interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1768088/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1770082] Re: systemd-networkd not renaming devices on boot
** Also affects: netplan.io (Ubuntu) Importance: Undecided Status: New ** Changed in: netplan.io (Ubuntu) Status: New => In Progress ** Changed in: netplan.io (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1770082 Title: systemd-networkd not renaming devices on boot To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1770082/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1770082] Re: systemd-networkd not renaming devices on boot
** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Changed in: netplan Status: Incomplete => Confirmed ** Changed in: cloud-init (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1770082 Title: systemd-networkd not renaming devices on boot To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1770082/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1732002] Re: cloud images in lxc get ipv6 address
This got landed in netplan.io 0.35 in bionic. The changes still should be part of a SRU. ** Changed in: nplan (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1732002 Title: cloud images in lxc get ipv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1732002/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1756322] Re: 'netplan apply' fails when trying to activate another interface on another QETH device ...
** Description changed: + [Impact] + Server users on s390x configuring qeth devices. + + [Test case] + 1) Reconfigure an interface for a QETH device + 2) Verify that 'netplan apply' completes successfully, without error. + + [Regression potential] + This change has minimal potential for regression, and it only skip qeth-based devices from "replugging", which "disconnects" them by unbinding and rebinding the driver. Potential issues would be limited to failure to rename interfaces without a reboot, for configurations that depend on this (but it already would not have worked due to netplan apply failing to rebind the device). + + --- + When trying to add another interface for a QETH device on a s390x system netplan apply fails: sudo netplan apply Cannot replug encc003: [Errno 19] No such device Traceback (most recent call last): File "/usr/sbin/netplan", line 23, in netplan.main() File "/usr/share/netplan/netplan/cli/core.py", line 50, in main self.run_command() File "/usr/share/netplan/netplan/cli/utils.py", line 110, in run_command self.func() File "/usr/share/netplan/netplan/cli/commands/apply.py", line 40, in run self.run_command() File "/usr/share/netplan/netplan/cli/utils.py", line 110, in run_command self.func() File "/usr/share/netplan/netplan/cli/commands/apply.py", line 87, in command_apply stdout=fd, stderr=fd) File "/usr/lib/python3.6/subprocess.py", line 291, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['udevadm', 'test-builtin', 'net_setup_link', '/sys/class/net/encc003']' returned non-zero exit status 4. It seems like rebinding of qeth devices is not allowed. With qeth devices, I guess one needs to "offline & online" them... Or like unbind a whole group of them, as there are three of them per interface. ubuntu@s1lp14:/sys/class/net/encc006/device$ ls -latr total 0 drwxr-xr-x 5 root root0 Mar 16 02:06 .. -rw-r--r-- 1 root root 4096 Mar 16 13:44 uevent drwxr-xr-x 6 root root0 Mar 16 13:44 . -rw-r--r-- 1 root root 4096 Mar 16 13:44 online lrwxrwxrwx 1 root root0 Mar 16 13:44 subsystem -> ../../../bus/ccwgroup lrwxrwxrwx 1 root root0 Mar 16 13:44 driver -> ../../../bus/ccwgroup/drivers/qeth drwxr-xr-x 2 root root0 Mar 16 13:44 vnicc --w--- 1 root root 4096 Mar 16 13:44 recover -rw-r--r-- 1 root root 4096 Mar 16 13:44 priority_queueing -rw-r--r-- 1 root root 4096 Mar 16 13:44 portno -rw-r--r-- 1 root root 4096 Mar 16 13:44 portname -rw-r--r-- 1 root root 4096 Mar 16 13:44 performance_stats -rw-r--r-- 1 root root 4096 Mar 16 13:44 layer2 -rw-r--r-- 1 root root 4096 Mar 16 13:44 isolation -rw-r--r-- 1 root root 4096 Mar 16 13:44 hw_trap lrwxrwxrwx 1 root root0 Mar 16 13:44 cdev2 -> ../../css0/0.0.0bb4/0.0.c008 lrwxrwxrwx 1 root root0 Mar 16 13:44 cdev1 -> ../../css0/0.0.0bb3/0.0.c007 lrwxrwxrwx 1 root root0 Mar 16 13:44 cdev0 -> ../../css0/0.0.0bb2/0.0.c006 -rw-r--r-- 1 root root 4096 Mar 16 13:44 buffer_count -rw-r--r-- 1 root root 4096 Mar 16 13:44 bridge_role -rw-r--r-- 1 root root 4096 Mar 16 13:44 bridge_reflect_promisc -rw-r--r-- 1 root root 4096 Mar 16 13:44 bridge_hostnotify --w--- 1 root root 4096 Mar 16 13:50 ungroup -r--r--r-- 1 root root 4096 Mar 16 13:50 switch_attrs -r--r--r-- 1 root root 4096 Mar 16 13:50 state drwxr-xr-x 2 root root0 Mar 16 13:50 power -r--r--r-- 1 root root 4096 Mar 16 13:50 inbuf_size -r--r--r-- 1 root root 4096 Mar 16 13:50 if_name -r--r--r-- 1 root root 4096 Mar 16 13:50 chpid -r--r--r-- 1 root root 4096 Mar 16 13:50 card_type -r--r--r-- 1 root root 4096 Mar 16 13:50 bridge_state drwxr-xr-x 2 root root0 Mar 16 13:50 blkt drwxr-xr-x 3 root root0 Mar 16 13:50 net - $ echo 'encc006' | sudo tee driver/unbind + $ echo 'encc006' | sudo tee driver/unbind encc006 tee: driver/unbind: No such device - $ echo 'cdev0' | sudo tee driver/unbind + $ echo 'cdev0' | sudo tee driver/unbind cdev0 tee: driver/unbind: No such device - $ echo '0.0.c006' | sudo tee driver/unbind + $ echo '0.0.c006' | sudo tee driver/unbind 0.0.c006 ubuntu@s1lp14:/sys/class/net/encc006/device$ Mar 16 13:52:28 s1lp14 sudo[8046]: ubuntu : TTY=pts/1 ; PWD=/sys/devices/qeth/0.0.c006 ; USER=root ; COMMAND=/usr/bin/tee driver/unbind Mar 16 13:52:28 s1lp14 sudo[8046]: pam_unix(sudo:session): session opened for user root by ubuntu(uid=0) Mar 16 13:52:28 s1lp14 systemd-networkd[7772]: encc006: Lost carrier Mar 16 13:52:28 s1lp14 systemd-timesyncd[1078]: Network configuration changed, trying to establish connection. Mar 16 13:52:28 s1lp14 systemd-timesyncd[1078]: Synchronized to time server 91.189.89.198:123 (ntp.ubuntu.com). Mar 16 13:52:28 s1lp14 systemd-networkd[7772]: encc006.2653: Lost carrier Mar 16 13:52:28 s1lp14 systemd-timesyncd[1078]: Network configuration changed, trying to
[Bug 1758647] Re: ubiquity doesn't preselect the right default keyboard layout
There was a misunderstanding there: I never suggested we should use xkb- keymap instead (or at least, that's not the message I was trying to convey). The intent was to reduce delta by not removing so much code, when console-setup merges are already difficult. I didn't foresee that some of that code setting a default would impact ubiquity (because ubiquity does things specially with d-i components, sometimes running them multiple times). There's always a need to update ubiquity after changing d-i components; it's inevitable since some of them are embedded in ubiquity source. The removals of xkb-keymaps aren't ubiquity-specific: we don't use this code in d-i, and instead use multiple screens to change keyboards. That's a conscious decision. The point for supporting xkb-keymap "in ubiquity" is more about making sure that we either "rebuild" the value based on layoutcode/variantcode, or otherwise unset it before running the configuration script -- ie. leave it in, but just explicitly ignore its values. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1758647 Title: ubiquity doesn't preselect the right default keyboard layout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1758647/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753431] Re: bonding does not works
Your original config in comment #1 is correct: you must specify the underlying devices, because those names are matched later for "interfaces:" in the bond config. The issue with 802.3ad is likely a driver issue or a bug in systemd; the right mode needs to be set by networkd (which may require rebooting rather than just running 'netplan apply'). Reassigning to systemd for investigation, we do have unit / autopkg tests running for netplan which look like 802.3ad is correctly set, but they do not interact with other network devices (there are no other network devices in the test environment). Furthermore, is anything beyond the physical network adapters configured to used 802.3ad? This is important for the bonding to work. ** Package changed: nplan (Ubuntu) => systemd (Ubuntu) ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1753431 Title: bonding does not works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1753431/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1726912] Re: fails to keep dhcplease
This would be a systemd-networkd bug, which I suspect might have already been fixed too. Reassigning to systemd. ** Package changed: nplan (Ubuntu) => systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1726912 Title: fails to keep dhcplease To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1726912/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754422] Re: [MIR] volume-key
MIR approved. The new version synced from debian in bionic (UNAPPROVED) looks good now, and appears to have corrected test suite issues: 18057438 | X- | volume-key | 0.3.9-4 | 6 hours | * volume-key/0.3.9-4 Component: universe Section: misc ** Changed in: volume-key (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to volume-key in Ubuntu. https://bugs.launchpad.net/bugs/1754422 Title: [MIR] volume-key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/volume-key/+bug/1754422/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1713803] Re: replacement of resolvconf with systemd needs integration
unbound attempts to add itself as a local resolver (pointing to 127.0.0.1). I think this will require specific integration work so that unbound can properly update/ tell systemd-networkd that it wants to be able to serve as a resolver. ** Changed in: squid3 (Ubuntu) Status: New => Invalid ** Changed in: unbound (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1713803 Title: replacement of resolvconf with systemd needs integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-androresolvd/+bug/1713803/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1713803] Re: replacement of resolvconf with systemd needs integration
sendmail only uses an update-libc.d script to reload the daemon on changes to resolv.conf, which should be sufficient for DNS resolution to remain working as it did with resolvconf; seeing as the nameserver will generally not change from 127.0.0.53 ** Changed in: sendmail (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1713803 Title: replacement of resolvconf with systemd needs integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-androresolvd/+bug/1713803/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754422] Re: [MIR] volume-key
Have the tests been fixed? I really don't much like having things in main that run tests but don't use the result; is there any way to just ignore the test(s) that are really broken and otherwise keep the remaining tests failing the build if they fail, such that we can catch a possible regression? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to volume-key in Ubuntu. https://bugs.launchpad.net/bugs/1754422 Title: [MIR] volume-key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/volume-key/+bug/1754422/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1713803] Re: replacement of resolvconf with systemd needs integration
Looks like the current behavior should be sufficient for postfix to integrate as well as it did with resolvconf: marking this Invalid. ** Changed in: postfix (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1713803 Title: replacement of resolvconf with systemd needs integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-androresolvd/+bug/1713803/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1756322] Re: 'netplan apply' fails when trying to activate another interface on another QETH device ...
** Changed in: netplan Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1756322 Title: 'netplan apply' fails when trying to activate another interface on another QETH device ... To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1756322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754422] Re: [MIR] volume-key
Wild guess is this is a test that expects user input, and the input never shows up? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to volume-key in Ubuntu. https://bugs.launchpad.net/bugs/1754422 Title: [MIR] volume-key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/volume-key/+bug/1754422/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753441] Re: [MIR] lame
Go for libmp3lame0, on the condition that CVE-2017-15019 be looked into. ** Changed in: lame (Ubuntu) Status: Incomplete => Fix Committed ** Changed in: lame (Ubuntu) Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned) ** Changed in: lame (Ubuntu) Assignee: (unassigned) => Iain Lane (laney) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to lame in Ubuntu. https://bugs.launchpad.net/bugs/1753441 Title: [MIR] lame To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lame/+bug/1753441/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753458] Re: [MIR] twolame
libtwolame0 is approved. ** Changed in: twolame (Ubuntu) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to twolame in Ubuntu. https://bugs.launchpad.net/bugs/1753458 Title: [MIR] twolame To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/twolame/+bug/1753458/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753450] Re: [MIR] mpg123
libmpg123-0 's MIR is approved then. ** Changed in: mpg123 (Ubuntu) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mpg123 in Ubuntu. https://bugs.launchpad.net/bugs/1753450 Title: [MIR] mpg123 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpg123/+bug/1753450/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753441] Re: [MIR] lame
** Changed in: lame (Ubuntu) Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to lame in Ubuntu. https://bugs.launchpad.net/bugs/1753441 Title: [MIR] lame To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lame/+bug/1753441/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753458] Re: [MIR] twolame
** Changed in: twolame (Ubuntu) Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to twolame in Ubuntu. https://bugs.launchpad.net/bugs/1753458 Title: [MIR] twolame To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/twolame/+bug/1753458/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753450] Re: [MIR] mpg123
** Changed in: mpg123 (Ubuntu) Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mpg123 in Ubuntu. https://bugs.launchpad.net/bugs/1753450 Title: [MIR] mpg123 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpg123/+bug/1753450/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753450] Re: [MIR] mpg123
MIR ack for libmpg123-0 if the Security Team acknowledges they are aware of this requirement. ** Changed in: mpg123 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mpg123 in Ubuntu. https://bugs.launchpad.net/bugs/1753450 Title: [MIR] mpg123 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpg123/+bug/1753450/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753458] Re: [MIR] twolame
MIR ack for libtwolame0 if the Security Team acknowledges they are aware of this requirement. ** Changed in: twolame (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to twolame in Ubuntu. https://bugs.launchpad.net/bugs/1753458 Title: [MIR] twolame To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/twolame/+bug/1753458/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753441] Re: [MIR] lame
This package has a long security history, and a currently left-open CVE because the upload of 3.100 did not include closing the active CVE. If there's a go-ahead from the Security Team (I'm not looking for a code review, just an acknowledgement that they are aware of the requirement for this package, and are fine with its current general state); then I see no issues with this MIR. ** Changed in: lame (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to lame in Ubuntu. https://bugs.launchpad.net/bugs/1753441 Title: [MIR] lame To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lame/+bug/1753441/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
Ok, I'm opening the tasks for Xenial and Trusty, and we can decide exactly where it makes sense to do the SRU for these changes. Plus, I understand maybe it was still reproducible in some form on bionic, so it this should be revisited in general. ** Also affects: console-setup (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: gdm3 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: console-setup (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: gdm3 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Trusty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1713803] Re: replacement of resolvconf with systemd needs integration
dnsmasq Suggests: resolvconf only, and checks before using it. None of the steps involved would break with resolvconf not being present, integration just happens via /etc/resolv.conf normally. ** Changed in: dnsmasq (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1713803 Title: replacement of resolvconf with systemd needs integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-androresolvd/+bug/1713803/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1713803] Re: replacement of resolvconf with systemd needs integration
vpnc and vpnc-scripts check for existance of /sbin/resolvconf and only Suggests: resolvconf. DNS integration by modifying /etc/resolv.conf (and thus the systemd symlink) should work appropriately and let systemd- resolved know about the new nameservers. ** Changed in: vpnc-scripts (Ubuntu) Status: New => Invalid ** Changed in: vpnc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1713803 Title: replacement of resolvconf with systemd needs integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-androresolvd/+bug/1713803/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1731505] Re: boot into link down state
I'm working on this in systemd upstream; should get it working soon. ** Changed in: netplan Status: Triaged => In Progress ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => In Progress ** Changed in: systemd (Ubuntu) Importance: Undecided => Wishlist ** Changed in: netplan Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1731505 Title: boot into link down state To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1731505/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1746419] Re: bond parameters are not changed by 'netplan apply'
Sounds like this is a bug in systemd, since it's what will deal with the actual devices. ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1746419 Title: bond parameters are not changed by 'netplan apply' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1746419/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1619258] Re: netplan should allow NICs to be disconnected and not stall the boot
In progress; we got optional: true for that and systemd has a corresponding "RequiredForOnline=false". ** Changed in: nplan (Ubuntu) Status: Confirmed => In Progress ** Changed in: nplan (Ubuntu) Importance: Undecided => High ** Changed in: nplan (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) ** Changed in: systemd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1619258 Title: netplan should allow NICs to be disconnected and not stall the boot To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1619258/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1727237] Re: systemd-resolved is not finding a domain
Xenial is affected too (systemd v229 looks to be, in general), so when SRUing we might as well push the fix there too, even if resolved is not typically used on Xenial. ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Xenial) Status: New => Triaged ** Changed in: systemd (Ubuntu Xenial) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1727237 Title: systemd-resolved is not finding a domain To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1727237] Re: systemd-resolved is not finding a domain
Packages are in my ppa: https://launchpad.net/~cyphermox/+archive/ubuntu/sru/+packages For bionic and xenial. I'll do one further build for artful. >From the look of things though, this will only be built and ready for amd64/i386, not for other architectures just yet. ** Changed in: systemd (Ubuntu Bionic) Status: Fix Committed => Triaged ** Changed in: systemd (Ubuntu Artful) Status: Confirmed => Triaged ** Changed in: systemd (Ubuntu Zesty) Status: Confirmed => Won't Fix ** Changed in: systemd (Ubuntu Artful) Importance: Undecided => High ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) ** Changed in: systemd (Ubuntu Artful) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1727237 Title: systemd-resolved is not finding a domain To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1738058] [NEW] vlan usage requires an intermediate step
Public bug reported:
If I try to apply vlans directly:
network:
version: 2
renderer: networkd
ethernets:
eth0: {}
vlans:
vlan1:
id: 1
link: eth0
addresses: [ 192.168.0.10/23 ]
vlan10:
id: 10
link: eth0
addresses: [ 10.0.0.5/24 ]
The vlan devices never come up, they are left in degraded state by
networkd. If I define an address for eth0, then eth0 and all of the
vlans will have the same address. Needless to say, this doesn't work.
If I use an intermediary device instead, such as a bond:
network:
version: 2
renderer: networkd
ethernets:
eth0: {}
bonds:
vmaster:
interfaces: [ eth0 ]
vlans:
vlan1:
id: 1
link: vmaster
addresses: [ 192.168.0.10/23 ]
vlan10:
id: 10
link: vmaster
addresses: [ 10.0.0.5/24 ]
Then the vlans are correctly applied and brought up by systemd.
I think this is either a systemd bug or a netplan bug; it's possible we
don't generate the config quite in the way that systemd expects it (even
though it looks straightforward enough).
** Affects: nplan (Ubuntu)
Importance: Undecided
Status: New
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1738058
Title:
vlan usage requires an intermediate step
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1738058/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1712921] Re: enabling networkd appears to eat up entropy
** Also affects: openssh (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: nplan (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: openssh (Ubuntu Bionic) Importance: Critical Assignee: Dimitri John Ledkov (xnox) Status: Fix Released ** Also affects: systemd (Ubuntu Bionic) Importance: Critical Assignee: Dimitri John Ledkov (xnox) Status: Triaged ** Also affects: nplan (Ubuntu Bionic) Importance: Critical Assignee: Mathieu Trudel-Lapierre (cyphermox) Status: In Progress ** Also affects: openssh (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: nplan (Ubuntu Zesty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1712921 Title: enabling networkd appears to eat up entropy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1712921/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1728181] [NEW] systemd-networkd-wait-online waits when devices are unmanaged
Public bug reported: I started a system with cloud-init disabled, etc. and a single real network interface (ens3) that could be configured. That VM has no configuration whatsoever for systemd-networkd, as that would have to have been written by netplan, and cloud-init did not generate netplan config (because it was disabled). So: root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route d-networkd-wait-online --ignore=lo ignoring: lo Event loop failed: Connection timed out root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route root@ubuntu:/etc/systemd/system/network-online.target.wants# networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 ens3 ether off unmanaged 3 sit0 sitoff unmanaged 3 links listed. root@ubuntu:/etc/systemd/system/network-online.target.wants# The system took 120 seconds to complete boot, because wait-online had to finish; and running wait-online from the system afterwards also waits 120 seconds (its default timeout). If there is no configuration for an interface, it's unmanaged (as shown by networkctl), so wait-online should not wait, and simply report that all interfaces are unmanaged, possibly returning an error so we don't reach network-online. FWIW, having wait-online look up configuration might later be useful also to figure out if an interface was configured, but marked as optional (such that it is explicitly not required to be up at boot), or if we want to configure network devices but specify that networkd should *not* bring them online (like "administratively disabled" interfaces in Cisco world using the "shutdown" command). ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1728181 Title: systemd-networkd-wait-online waits when devices are unmanaged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728181/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1712921] Re: enabling networkd appears to eat up entropy
There's a bit of netplan in that too. ** Also affects: nplan (Ubuntu) Importance: Undecided Status: New ** Changed in: nplan (Ubuntu Artful) Status: New => In Progress ** Changed in: nplan (Ubuntu Artful) Importance: Undecided => Critical ** Changed in: nplan (Ubuntu Artful) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1712921 Title: enabling networkd appears to eat up entropy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1712921/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1717471] Re: networkd does not accept / set advertised mtu
** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: nplan (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1717471 Title: networkd does not accept / set advertised mtu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1717471/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
Indeed, it looks like systemd is handling this properly by itself. I'll do some more testing but it looks like removing that is probably the best thing to do. At least font/keymaps are set properly. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1713578] [NEW] Migrate /etc/resolv.conf from resolvconf to systemd-resolved
Public bug reported: Moving off of resolvconf and to systemd-resolved requires that resolv.conf is properly handled both in the case of new installs (done as per 234-2ubuntu9 at least), but also in the case of upgrades from previous releases or previous versions of systemd. There are various use cases to take into account: 1) upgrades where resolv.conf is more or less default and dynamic, uses DHCP via ifupdown (servers), or 127.0.1.1/DHCP settings from NetworkManager (desktops), etc. 2) upgrades from manual resolv.conf settings (the user has written their own, it's static) 3) upgrades from manual resolv.conf managed via resolvconf. 3) No resolv.conf? Lack of resolv.conf is simple, writing one is always sane. Upgrades from dynamic files is also straightforward, copying it to /run/systemd/resolve/resolv.conf will keep the current state; /etc/resolv.conf will be symlinked to that. In the case of a manually-configured resolv.conf; whether it comes from resolvconf or is manually configured is non-trivial if we want to maintain the current DNS configuration and also remove resolvconf. The removal of resolvconf can be forced, but what do we do about the existing /etc/resolv.conf file, knowing that /run is a tmpfs? ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1713578 Title: Migrate /etc/resolv.conf from resolvconf to systemd-resolved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1713578/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1703662] Re: [MIR] rhythmbox-plugin-alternative-toolbar
** Changed in: rhythmbox-plugin-alternative-toolbar (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1703662 Title: [MIR] rhythmbox-plugin-alternative-toolbar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1703662/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1709135] Re: add bond primary parameter
Sounds like we'd need to add a key under parameters: for the bond device, as per the original description (but the device needs to be listed in 'interfaces', and exist in the list of interfaces defined in netplan: ethernets: version: 2 ethernets: eth0: match: driver: virtio ens4: match: driver: e1000 bonds: bond0: interfaces: [ eth0, ens4 ] parameters: mode: active-backup mii-monitor-interval: 100 primary: ens4 dhcp4: true This will require backporting the feature from systemd to the releases where we need this (to xenial). ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: nplan (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: nplan (Ubuntu Artful) Importance: High Assignee: Mathieu Trudel-Lapierre (cyphermox) Status: Triaged ** Also affects: systemd (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: nplan (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Zesty) Status: New => Fix Released ** Changed in: systemd (Ubuntu Artful) Status: New => Fix Released ** Changed in: systemd (Ubuntu Xenial) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: nplan (Ubuntu Xenial) Status: New => Triaged ** Changed in: nplan (Ubuntu Zesty) Status: New => Triaged ** Changed in: nplan (Ubuntu Zesty) Importance: Undecided => High ** Changed in: nplan (Ubuntu Xenial) Importance: Undecided => High ** Changed in: nplan (Ubuntu Zesty) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) ** Changed in: nplan (Ubuntu Xenial) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1709135 Title: add bond primary parameter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1709135/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1689317] Re: [MIR] epiphany-browser-runtime
Marking incomplete / unassigning; the Security Team NAKed this MIR in a different bug already, so if it's still needed and deemed appropriate (including the previous comment about how it means we might ship multiple browsers), then please set this back to New. ** Changed in: epiphany-browser (Ubuntu) Status: New => Incomplete ** Changed in: epiphany-browser (Ubuntu) Assignee: Mathieu Trudel-Lapierre (cyphermox) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu. https://bugs.launchpad.net/bugs/1689317 Title: [MIR] epiphany-browser-runtime To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1689317/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1703640] Re: nplan and libnss-resolve should be in same dependency
I don't think it is; you should be able to use things just as well with /etc/resolv.conf, and having systemd-networkd (or systemd-resolved) update it, depending on whether this is automatic via DHCP or for a static IP. Regardless, in general I tend to agree libnss-resolve probably should be included at the same level as nplan; this will need some more testing. In any case, not a bug in nplan, possibly a bug for libnss-resolve (systemd); so reassigning. ** Package changed: nplan (Ubuntu) => systemd (Ubuntu) ** Changed in: systemd (Ubuntu) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu) Status: New => Triaged ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1703640 Title: nplan and libnss-resolve should be in same dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1703640/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1665088] Re: netplan bridge config doesn't support stp boolean
Verification done on xenial and yakkety with netplan 0.23~: The parameters are being accepted by netplan parsing network v2 yaml; and appropriately copied on to the resulting configuration for the renderer. STP is not yet supported by systemd however, so further testing could not be done. ** Tags removed: verification-needed ** Tags added: verification-done-xenial verification-done-yakkety ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Fix Released ** Changed in: systemd (Ubuntu Zesty) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1665088 Title: netplan bridge config doesn't support stp boolean To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1665088/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1689317] Re: [MIR] epiphany-browser-runtime
We should probably try to avoid shipping more than one browser by default. Currently we ship Firefox (and shipping a browser on live images is up to the Desktop team, AFAIK). The package split appears to make sense to provide just the webapp integration feature (but it's not done yet). I have not made a full review of epiphany yet; I think given it's a browser and has has security history (despite most issues would be caused by webkit2gtk if anything), it would benefit a proper Security team review. ** Changed in: epiphany-browser (Ubuntu) Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu. https://bugs.launchpad.net/bugs/1689317 Title: [MIR] epiphany-browser-runtime To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1689317/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1686726] Re: [MIR] gnome-getting-started-docs
Seems simple enough, given that it's a doc package; and it has a bug subscriber, etc. MIR approved. ** Changed in: gnome-getting-started-docs (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) ** Changed in: gnome-getting-started-docs (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-getting-started-docs in Ubuntu. https://bugs.launchpad.net/bugs/1686726 Title: [MIR] gnome-getting-started-docs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-getting-started-docs/+bug/1686726/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1675933] Re: gdm fails to start
*** This bug is a duplicate of bug 1686257 *** https://bugs.launchpad.net/bugs/1686257 Indeed sounds like the issue I was having -- marking as a duplicate. FTR, I no longer see an issue with gdm3; but I had reinstalled my system with Ubuntu-GNOME directly, and in that case it worked; so it was indeed due to some issue with what is different between Ubuntu and Ubuntu- GNOME. ** This bug has been marked a duplicate of bug 1686257 gdm3 fails to start when default session-name=ubuntu -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1675933 Title: gdm fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1675933/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1685870] Re: [MIR] gnome-shell
It looks like the issues mentioned above are appropriately taken care of; so I'm good with this MIR. ** Changed in: gnome-shell (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1685870 Title: [MIR] gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1685870/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1685870] Re: [MIR] gnome-shell
- Despite what is claimed in the bug description; iio-sensor-proxy is still a Recommend, would need a MIR. - There appears to be test that could run for gnome-shell, but they aren't obviously being run as part of the build -- make check does not appear to run run-tests.sh. - There are a few older bugs filed against gnome-shell (but perhaps belong elsewhere) that are confirmed/triaged, but do not appear to have been upstreamed. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1685870 Title: [MIR] gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1685870/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1685408] Re: [MIR] mutter
MIR approved. ** Changed in: mutter (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1685408 Title: [MIR] mutter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1685408/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1686393] Re: [MIR] gdm3
Since this was in main previously, I don't see any reason to really block it, but it still ought to have some review by the Security team given the obvious security history for gdm and being a login manager. ** Changed in: gdm3 (Ubuntu) Assignee: Mathieu Trudel-Lapierre (cyphermox) => Ubuntu Security Team (ubuntu-security) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1686393 Title: [MIR] gdm3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1686393/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1685867] Re: [MIR] caribou
MIR approved. ** Changed in: caribou (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to caribou in Ubuntu. https://bugs.launchpad.net/bugs/1685867 Title: [MIR] caribou To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caribou/+bug/1685867/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1685414] Re: [MIR] gnome-settings-daemon
MIR approved. The test fixes are committed to the packaging branch. ** Changed in: gnome-settings-daemon (Ubuntu) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1685414 Title: [MIR] gnome-settings-daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1685414/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1683989] Re: [MIR] gjs
MIR approved. ** Changed in: gjs (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1683989 Title: [MIR] gjs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1683989/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1683937] Re: [MIR] mozjs38
MIR approved. ** Changed in: mozjs38 (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mozjs38 in Ubuntu. https://bugs.launchpad.net/bugs/1683937 Title: [MIR] mozjs38 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozjs38/+bug/1683937/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1683937] Re: [MIR] mozjs38
** Changed in: mozjs38 (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mozjs38 in Ubuntu. https://bugs.launchpad.net/bugs/1683937 Title: [MIR] mozjs38 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozjs38/+bug/1683937/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1685415] Re: [MIR] gnome-control-center
I've re-reviewed gnome-control-center since I mixed it up with gnome- settings-daemon before, and since there had never been a MIR in the past (although it was in main before); MIR approved. ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1685415 Title: [MIR] gnome-control-center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1685415/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1685414] Re: [MIR] gnome-settings-daemon
Please re-enable unit tests and make sure they fail the build if they fail. The open bug as a rationale for disabling tests seems like something that should be quite easy to fix, even if the fix is to remove that test as a distro patch. ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Incomplete ** Changed in: gnome-settings-daemon (Ubuntu) Importance: Undecided => High ** Changed in: gnome-settings-daemon (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) ** Changed in: gnome-settings-daemon (Ubuntu) Milestone: None => ubuntu-17.05 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1685414 Title: [MIR] gnome-settings-daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1685414/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1636666] Re: [MIR] pcre2
"Other distros do it" isn't sufficient rationale, by itself, to support putting pcre2 in main. We already ship it, the question is whether it should be in main, meaning whether Canonical will be responsible for support, providing security updates, etc. To mirror what doko mentioned earlier, what is needed to demote pcre3? Can we start (even a long-running) transition? (So there should be a tracker setup for that). There seems to be new security issues too. I don't have a preference on what version of pcre to use, there should just be a reasonable analysis of how far we are to being able to just one pcre, what the steps needed to get there, possibly bugs open or a transition tracker to follow progress, and whether we can more easily port what seems to require pcre2 now back to pcre3 in order to facilitate maintenance. Should we / can we invest time and effort in porting things from pcre3 to pcre2? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/163 Title: [MIR] pcre2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/163/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1636666] Re: [MIR] pcre2
** Changed in: pcre2 (Ubuntu) Milestone: ubuntu-17.03 => ubuntu-17.05 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/163 Title: [MIR] pcre2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/163/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1617098] Re: Add support for option max-routes
** Also affects: network-manager-openvpn (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: network-manager-openvpn (Ubuntu Yakkety) Status: New => Triaged ** Changed in: network-manager-openvpn (Ubuntu Yakkety) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1617098 Title: Add support for option max-routes To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-openvpn/+bug/1617098/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1636666] Re: [MIR] pcre2
To be clear, I share doko's feeling against having two versions of the library in main if it can be avoided -- this is certainly not a permanent situation, but most things don't appear to have switched to pcre2 just yet (and I would expect they would in the near-ish term). In that sense, I'd be more in favor of not upgrading vte/gnome-terminal for the time being. To make it simpler: how do we value the benefits of a new pcre2 in main (meaning possibly some new features of gnome-terminal and vte) against the (probably small, but still) maintenance burden of having two PCRE libraries in main or the need to hold gnome-terminal and vte back for this cycle? To me wearing the MIR team hat, the benefits don't outweigh the increased maintenance work (ie. you can do nothing to vte and gnome- terminal, and we're good), especially when you consider that pcre is the kind of thing that does tend to have CVEs every once in a while[1]. On the other hand, new features are shiny, but they look to me like they might be cherry-pickable. I'm open to be convinced, and the security team probably should have a say in it too (hence my suggestion of bringing it up on the mailing list). [1] http://www.cvedetails.com/product/5715/Pcre-Pcre.html?vendor_id=3265 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/163 Title: [MIR] pcre2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/163/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1636666] Re: [MIR] pcre2
I understand the concerns, and I share them, but I don't think we should alone make the decision. Perhaps bring this up for wider discussion on the ubuntu-devel mailing list? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/163 Title: [MIR] pcre2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/163/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1617098] Re: Add support for option max-routes
Sponsored the SRU. This does not need a fix in zesty as the fix is already applied there (via newer upstream release). Adam Collard, please update the bug description to follow the SRU procedures (https://wiki.ubuntu.com/StableReleaseUpdates#Procedure). You will want to subscribe ~ubuntu-sru when the bug report description is ready. ** Also affects: network-manager-openvpn (Ubuntu Zesty) Importance: Wishlist Status: Triaged ** Also affects: network-manager-openvpn (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: network-manager-openvpn (Ubuntu Zesty) Status: Triaged => Fix Released ** Changed in: network-manager-openvpn (Ubuntu Xenial) Importance: Undecided => Wishlist ** Changed in: network-manager-openvpn (Ubuntu Xenial) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1617098 Title: Add support for option max-routes To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-openvpn/+bug/1617098/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1333140] Re: Fix udev rules to consider mmc rpmb partitions
This isn't caused by ubiquity if it's at startup, since ubiquity would only care about it w/r/t partitioning, and that hasn't been the case since somewhere during the development cycle of 16.04 -- when we updated partman-base to stop trying to partition rpmb devices. Closing the ubiquity task as Invalid. Clearly, there's something else that breaks there. ** Changed in: ubiquity (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1333140 Title: Fix udev rules to consider mmc rpmb partitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1333140/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1636666] Re: [MIR] pcre2
** Changed in: pcre2 (Ubuntu) Milestone: None => ubuntu-17.03 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/163 Title: [MIR] pcre2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/163/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1560162] Re: Xenial: scaling is horribly out on xps13 install session
Since it's been verified by Nara; marking verification-done. ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1560162 Title: Xenial: scaling is horribly out on xps13 install session To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1560162/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1560162] Re: Xenial: scaling is horribly out on xps13 install session
This still needs verification. You would want to use 'break=bottom' on the command-line when booting to stop before ubiquity starts, then chroot into the system and apt-get install the new ubiquity to test this. The bug that was automatically found isn't a regression of this fix but an issue with debconf-apt-progress unrelated to the problem at hand. ** Tags removed: verification-failed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1560162 Title: Xenial: scaling is horribly out on xps13 install session To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1560162/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1560162] Re: Xenial: scaling is horribly out on xps13 install session
** Changed in: ubiquity (Ubuntu Xenial) Status: New => In Progress ** Changed in: ubiquity (Ubuntu Xenial) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1560162 Title: Xenial: scaling is horribly out on xps13 install session To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1560162/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1571262] [NEW] my computer's name is not "Bastien's computer"
Public bug reported: See included screenshot. There is something that looks like a hardcoded string for "Bastien's computer" as a hostname as visible in bluetooth. That is not the case, and may confuse users. I've found the following string in gnome-bluetooth 3.18.2-1ubuntu2: gnome-bluetooth-3.18.2/lib/settings.ui:Visible as “Bastien's computer” and available for Bluetooth file transfers. Transferred files are placed in the a href="http://www.gnome.org"Downloads/a; folder. Furthermore, this string is not translated, as opposed to the rest of the UI for Bluetooth settings. ** Affects: gnome-bluetooth (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screenshot displaying the issue" https://bugs.launchpad.net/bugs/1571262/+attachment/4638490/+files/Capture%20d%27%C3%A9cran%20de%202016-04-16%2018-54-47.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1571262 Title: my computer's name is not "Bastien's computer" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1571262/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1555237] Re: Upgrade from 14.04.4→ 16.04 dies midway taking out the session.
** Also affects: dbus (Ubuntu) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => In Progress ** Changed in: dbus (Ubuntu) Status: New => In Progress ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) ** Changed in: dbus (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: In Progress => Invalid ** Changed in: ubuntu-release-upgrader (Ubuntu) Assignee: Mathieu Trudel-Lapierre (cyphermox) => (unassigned) ** Changed in: dbus (Ubuntu) Importance: Undecided => Critical ** Changed in: systemd (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1555237 Title: Upgrade from 14.04.4→ 16.04 dies midway taking out the session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1555237/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1538293] Re: [MIR] appstream
It doesn't especially matter to me which packages make it to main or not, but we shouldn't move packages around if they don't need to be. Knowing what is affected also shows that there has been some work put in preparing the MIR request. As for the lintian warnings, no, it's not a blocker but they should also be fixed if possible. MIR approved. ** Changed in: appstream (Ubuntu) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1538293 Title: [MIR] appstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1538293/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1318875] Re: Airplane mode cannot save the previous status after reboot
** Changed in: unity-control-center (Ubuntu) Status: Confirmed => In Progress ** Changed in: unity-control-center (Ubuntu) Assignee: anagha (anghakc) => Mathieu Trudel-Lapierre (mathieu-tl) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1318875 Title: Airplane mode cannot save the previous status after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1318875/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1485217] Re: Magic for text/x-tex broken
How are you reproducing this? How can I verify the fix? It seems to me as nautilus recognizes a dummy file correctly as plain text rather than TeX document; so does the file command. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1485217 Title: Magic for text/x-tex broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1485217/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
