wrong monospace font size since upgrade
Hey I upgraded my primary desktop machine to precise this weekend, and noticed that the monospace font with size 8 gives me a weird looking terminal. Next I ran a small test to see how precise compares with oneiric. Using a fullscreen terminator window on a oneiric & precise kvm instance (1024x768) give me these terminal geometries: Ubuntu monospace sizeoneiric precise 7 201x72 201x80 8 201x65 168x65 9 168x55 168x60 10 144x48 144x55 "Monospace" (DejaVu Sans Mono) sizeoneiric precise 7 168x60 201x72 8 168x55 144x55 9 144x48 144x51 10 126x42 126x48 Can anyone confirm, or better, knows why this is? Size 8 has been perfect for me, now the terminals are all weird :/ -- t -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: wrong monospace font size since upgrade
17.01.2012 13:18, Timo Aaltonen kirjoitti: > > Hey > > I upgraded my primary desktop machine to precise this weekend, and > noticed that the monospace font with size 8 gives me a weird looking > terminal. Next I ran a small test to see how precise compares with > oneiric. Using a fullscreen terminator window on a oneiric & precise kvm > instance (1024x768) give me these terminal geometries: > > Ubuntu monospace > size oneiricprecise > 7201x72201x80 > 8201x65168x65 > 9168x55168x60 > 10144x48144x55 > > "Monospace" (DejaVu Sans Mono) > sizeoneiricprecise > 7168x60201x72 > 8168x55144x55 > 9144x48144x51 > 10126x42126x48 > > > Can anyone confirm, or better, knows why this is? Size 8 has been > perfect for me, now the terminals are all weird :/ Anyone? I can't be the only one seeing this :) -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: Why don't we use Mozilla ESR in Precise?
On 04.02.2012 15:51, Jo-Erlend Schinstad wrote: In Precise we've upgraded to version 11 of both Firefox and Thunderbird. But the reason for starting to upgrade frequently was said to be that Mozillas support periods were limited for newer versions after 3.6. But now we have the 10ESR versions of both. Why are they not used instead of the short-term 11? Agreed, my ex-colleagues hate it when the version changes every few weeks on their environment. I'd think it's the same for every entreprise-y user out there.. Guess it's not possible to provide the ESR release as an option, so that the upgrade needs to be tested at such sites only once a year instead of nine times? -- t -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: Known issues with xorg upgrades from HWE stacks?
On 18.11.2013 18:25, Robie Basak wrote: > I had an issue upgrading a friend's laptop yesterday. Before I > investigate further and spend time trying to figure out steps to > reproduce, has anybody else seen this behaviour? > > It was installed on 12.04 with the quantal HWE stack. After upgrading to > 12.10, xorg did not update, and was still on HWE packages. This > caused X to fail to boot - black screen. > > Various xorg packages were on quantal hwe ~precise versions. I asked > apt-get to lose these (apt-get --purge ...- ...- etc); it suggested > installing the native quantal versions as a solution to that request, > and then everything worked. > > The laptop has an nvidia graphics card. Everything is on defaults. > > I've heard various user stories about graphic stack failure upon > upgrade. Is this a known thing, and could this be an underlying cause? > Is this already a known bug? Upgrading from a HWE backport stack to 12.10 is not supported. You need to remove the backports first by installing 'xserver-xorg-lts-precise' which will pull in the original packages and removes the HWE stack. Upgrades to the next LTS will be supported. too bad if stock precise fails to work on such hw.. -- t -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: Known issues with xorg upgrades from HWE stacks?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 19.11.2013 14:16, Robie Basak wrote: > On Tue, Nov 19, 2013 at 02:02:37PM +0200, Timo Aaltonen wrote: >>> I've heard various user stories about graphic stack failure >>> upon upgrade. Is this a known thing, and could this be an >>> underlying cause? Is this already a known bug? >> >> Upgrading from a HWE backport stack to 12.10 is not supported. > > OK, though in that case, how can we communicate this better? Have > I missed some obvious notice? I wonder how many others have hit the > same problem, unknowingly attempting an unsupported upgrade. > > And shouldn't update-manager refuse to attempt an upgrade in this > case? AIUI LTS releases don't offer upgrades to interim releases (by default), only when the new LTS is available? - -- t -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSi7ZbAAoJEMtwMWWoiYTc5bMP/Rq/DSTxw8hRfkxP92sPT+Hv uRrHbQ5pCXruqhU43rFPzknjWz39FSSB5nHC9TbHbY7L4Lm4F3TtwNxHNm+SQ7vg P9psi8sCHZvE3kHObRngJMP6n77O9veNiPYOoAbIcYV8gEiXRtDLoCwYwUdRQeEh GqUOjszhfalLFW2n4S6iW7mYc1tp+q3Z1wBSUTb3B+zVyhhaCUACEzBfmYEs963z Dy6U82meH3NWAYUuwFZ3fkAjrclsqdDUsvxzZzFtLg5u8YUqGG5acq9R6O0YvSie /tXpTYH9wqZvKQxxpR/bnOCTwqyNqNCecRhmZDDbVVktZFE50AOCB6Iptu3bG/B9 Ftx5m64Mtz7R95lnxqYux0wp3g1ptq4/71IWVq3IxQp3MFm4G+FOWAPnUkgXv+U9 TpXlnkT7Fk1if7KfitG3wXK4RVJFsT8PisSg6a86+TYlomBxoWcghOkYIiOViAiu KFYJLTyuGdCtP/DNKHCB9eJYIeZVhPZosLB6HKJKYbhP5RRmObeAt0uuYlxOLE0L CMRe8s6MZFbu2CYLTuoeLxvIgvltsI86l3bwnnFDxO7ux9L9m4KFPizjm9ZLz4BP xbFz0qi3L0HVNe1Cb7dltKSG7Ayr63F1d4dwJJB7pBvGFoQDPT2joB+h2Ok7UgNN junf7IRMxv+pP9IOm7Dn =/ND6 -END PGP SIGNATURE- -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: Known issues with xorg upgrades from HWE stacks?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 19.11.2013 21:18, Robie Basak wrote: > On Tue, Nov 19, 2013 at 09:04:59PM +0200, Timo Aaltonen wrote: >> AIUI LTS releases don't offer upgrades to interim releases (by >> default), only when the new LTS is available? > > Right. > > But imagine the situation without HWE. > > I'm on Precise. Quantal is released, and I want to upgrade to it. > It doesn't appear by default, and the standard answer is to > specifically request through the GUI that all release upgrades are > displayed rather than only LTS release upgrades. Then a release > upgrade to Quantal appears, and I select it. AIUI, this is the > supported way of doing it. > > Now consider the same upgrade situation with HWE (which you say is > not supported). In my ignorance, I do exactly the same thing. I > request it to show me all available upgrades, not just LTS ones. > The release upgrade to Quantal appears. I select it. My system > breaks. > > So I don't think that saying that you have to explictly select it > is a reasonable excuse. This is the recommended way of upgrading up > from an LTS to a standard release for non-HWE installations. I do > not necessarily know that an HWE upgrade to a standard release is > not supported. I may not even know that I have an HWE stack > installed. The GUI behaves exactly the same, provides no warning > with the identical process, and causes my system to break. > > Save for any other explanation, this sounds like a Critical bug in > update-manager to me, since it causes the system to become > unusable through a process that the user would otherwise expect to > work, but is actually not supported in a particular configuration > that the user ends up in by default. > > Does this make sense? Does you disagree, or should I go ahead and > file this bug? Makes perfect sense, don't disagree at all. This was one of the points of the discussion around "pockets vs renames", that upgrades to 12.10 were a big no-no. Apparently the upgrader wasn't updated to know about that fact. Not pointing any fingers.. a bug report even this late certainly won't hurt. - -- t -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIbBAEBAgAGBQJSi7sMAAoJEMtwMWWoiYTcNOAP+Lnvhc8pqWsSck2AFeN1U4V8 lh6DK49hbrJwn6sAy90JoRPlZK53chvYj2K7ruMXPFVKiZF2kJJ/oEmesVG3CrbA 3HILAETPHj1OYAzlCwG339uwS9fPF1bFWpWnmkBkMAhiXlApw1NFivps/y6Dsf0e pTfZUpHtdj9anQFRYkzxSn952vx3gMP8TrCKg1cTjoEAb3UWLLZJj7t/yGp4+5G0 mn10Pnds5xBsF6CEgoWPPoqir95aAHR+VnwuSVg54LbXAbR58/stm/FDBXJssLpX JXIOzSI2Ae2ZMuEByx/fAQQtlFVu1I6zsG/X2aU9mqP6Bt+SuhUqIrZksVMUgAKx pDedUrRVQKb1XpvKFA0lqDRI0QeJOe0idTA9UHHsWoT54KomY44vCQtMFFq2SJ2z plYbdmVM7g39jyJKMKpsKGBjHu9vm/SqMW7/6rsCnVaC7cw55ItgPe4mxwdqHCi1 dhN5OSBGy88WQa9UvNXG5Pesj0mEI7D4eLRPtO4tlG/KJGCr8/irudVbExDu1dlh yuh5x3nCJOQFG5I3GYHUporAuWd2jPkhjWqwv2GdMQ/KhmMw/NeY2bgv8hicpShD 4hcInIhKLpmpP+EFi6WT6uKU3smqwRm/SUGdrje0OOifm06IDFaF0ru8oXI74fu9 Q0upsCVuX9KJZMd3wHQ= =WamD -END PGP SIGNATURE- -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: Known issues with xorg upgrades from HWE stacks?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 19.11.2013 21:25, Timo Aaltonen wrote: > On 19.11.2013 21:18, Robie Basak wrote: >> On Tue, Nov 19, 2013 at 09:04:59PM +0200, Timo Aaltonen wrote: >>> AIUI LTS releases don't offer upgrades to interim releases (by >>> default), only when the new LTS is available? > >> Right. > >> But imagine the situation without HWE. > >> I'm on Precise. Quantal is released, and I want to upgrade to >> it. It doesn't appear by default, and the standard answer is to >> specifically request through the GUI that all release upgrades >> are displayed rather than only LTS release upgrades. Then a >> release upgrade to Quantal appears, and I select it. AIUI, this >> is the supported way of doing it. > >> Now consider the same upgrade situation with HWE (which you say >> is not supported). In my ignorance, I do exactly the same thing. >> I request it to show me all available upgrades, not just LTS >> ones. The release upgrade to Quantal appears. I select it. My >> system breaks. > >> So I don't think that saying that you have to explictly select >> it is a reasonable excuse. This is the recommended way of >> upgrading up from an LTS to a standard release for non-HWE >> installations. I do not necessarily know that an HWE upgrade to a >> standard release is not supported. I may not even know that I >> have an HWE stack installed. The GUI behaves exactly the same, >> provides no warning with the identical process, and causes my >> system to break. > >> Save for any other explanation, this sounds like a Critical bug >> in update-manager to me, since it causes the system to become >> unusable through a process that the user would otherwise expect >> to work, but is actually not supported in a particular >> configuration that the user ends up in by default. > >> Does this make sense? Does you disagree, or should I go ahead >> and file this bug? > > Makes perfect sense, don't disagree at all. This was one of the > points of the discussion around "pockets vs renames", that upgrades > to 12.10 were a big no-no. Apparently the upgrader wasn't updated > to know about that fact. Not pointing any fingers.. a bug report > even this late certainly won't hurt. Also! Don't forget the session tomorrow about planning the HWE stack updates for 14.04.x if you have something to share :) https://blueprints.launchpad.net/ubuntu/+spec/core-1311-hwe-plans - -- t -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSi7vtAAoJEMtwMWWoiYTcprgP/06W81WrVDyK0PkEtNKw6ffu 9cdudP0k/6qAAxb4L4Hz3tQa0BTb/oXpoqJzTuf7o3u2ci3yciK65jMmk/sQmLle cIvHW8cEQ/tHKxI9XnlnYNLCrJY8r8sCqALJLNbOHABQGAHQb7xto2/NrVgpdwf5 VnzBY3NZWcnNNX9xvV6LypniswfdPsfeXqq+XyfAXFLV4KuSVrbyqX1u6mpOXVO5 vmVAymgjL3de01zJr2ZJsntcLIV82ZEdNVPJFYX/P4R1qecEUqu+DcmeVd4tZCy/ qw5TD24h4eJ2TTggqdPJS4R9mPNM8+EeWnQ/Kxoqnrre9oJKOpEItAdZnNyh59KZ qjxXI61N4WZi/83VYsvYEYlV+pbfr44wilWGkaKg4/W/XoSiuN4dFhJAN8hWoxQy 33zkd3id99tuFhpLRPi8ULMQaAEpf3FgLnFHI/d2dL1eNmi6Qj0qbW+P4Ro64Wul izvhidpB1iPUMlaTyYBmUFTRM6pl2u3X5Fxo69suWdizoiWNK7ck8XsvjJ/ahYyd B7DUTmOyqRk45nBAHSkW8uNBptbPzPRKhMIjEnLl+vvXPp6Rtu8Ujx30zJn8OTKl bss6R57H1mFD0mJFheB55qYvTqOPaIODLVcDi+3/rKKz8PS7JHI6bN76HMeO+6gA Dm2kzEBJ62292n9PqrMd =aWe+ -END PGP SIGNATURE- -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: Default File Manager with Unity8 in future desktops
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 30.01.2014 19:21, Oliver Grawert wrote: > hi, > > with the planned switch to unity8 in 14.10 it is most likely that > we will also start using the converged QML apps that are developed > today. > > With all the complaints and unhappyness about Nautilus upstream > ripping out things like dual pane and other beloved and helpful > features I expect we can do better and I think this is the right > time to: > > a) collect requirements b) file whishlist bugs c) if *you* want to > contribute, get in contact with the developers (CCed) > > the new core apps are all 100% developed by the community under > guidance of the canonical design team. > > the code for the filemanager can be found at > https://launchpad.net/ubuntu-filemanager-app > > it is running on phone and tablets already and has a proper > convergence mode adapting to bigger screens. > > lets get the discussion rolling ;) - - rubberbanding in list view https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/49348 ! - - support for gvfs or similar with feature parity - -- t -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJS7eOsAAoJEMtwMWWoiYTcS7wP/1N078wQpSRi0OeP0uM8RbiN htyrYXKNFPdxTOU4ISXk0e4n+IzN6/isHSjlo64WnVyVHLKFz6m67G3K905FEVaC s95OjyMOcVHvecdP75Iqs6xtAzG/SEGt5SiHa6GIoyF3MyPI/TliAXy2m/0kYdgK 3+grL0SlS3/yy7WWXsDF4htEslSrg0pXnDt8e+I+HTch+/2WM7Scl6c84wwymuNG X8tmnPbmoVj29BKoAmtmd2ZMK3u7dqO7ADg6i8MVMzy2ihOqslXhS5R9jJZRrolX gXv8luVhkdGs2++vfYOerb5tF5WdrEDYMb7tVvGKaDuD3mSfD4FPqpdBn+7Xt4pN ZIUTOek7i8xASw6kRuZ+yi6k+Z4bxQ5lRUv4eFKRpR+JD2gYvtC5AhtA9XaQtB9r 6Qj2o+Utrq1gwdyLzVsN1KHz7mIN8tHGsEOU8OdhdRU9BEhyu7v2ZoatuS4UIbZ+ CjnnJwFKLGXjJOqgmKmNk7V7b2PL/2Eyx5SWdXL8U5Ph+9ppaYvyWm7JYI1LVmDo EhcsAJ9QwAUvNr1aQsdrlmoItTvsGt5dpdCxTRJuM25osBIiVQGqdJTcOACTq+5E hjXs8nJDUInyrfG7eAnXATxd4Zntn7DIRcwrPilTMpxX8S5uQM3E1b/3X7s1Hp6O vgdzqFknMiZPtWV8Z/If =MkV/ -END PGP SIGNATURE- -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: Default App: xdiagnose
On 09.06.2017 03:43, Jeremy Bicha wrote: > The GNOME Activities Overview makes default installed apps much more > prominent so any app installed by default should work and be generally > useful. > > xdiagnose does not work with GNOME on Wayland (LP: #1616742) because > of the pkexec issue I mentioned in a separate thread on this list. > > The only Ubuntu flavors that include xdiagnose in 17.04 are Ubuntu > (Unity), Ubuntu Budgie and Ubuntu Kylin. > > Maybe whatever useful parts of the app should be moved to another > package or app? The apport hook & links are useful, so maybe strip everything else but leave these and the python bits they need. -- t -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: Default App: xdiagnose
On 01.09.2017 00:35, Jeremy Bicha wrote: > On Fri, Jun 9, 2017 at 3:55 AM, Timo Aaltonen wrote: >> On 09.06.2017 03:43, Jeremy Bicha wrote: >>> The GNOME Activities Overview makes default installed apps much more >>> prominent so any app installed by default should work and be generally >>> useful. >>> >>> xdiagnose does not work with GNOME on Wayland (LP: #1616742) because >>> of the pkexec issue I mentioned in a separate thread on this list. >>> >>> The only Ubuntu flavors that include xdiagnose in 17.04 are Ubuntu >>> (Unity), Ubuntu Budgie and Ubuntu Kylin. >>> >>> Maybe whatever useful parts of the app should be moved to another >>> package or app? >> >> The apport hook & links are useful, so maybe strip everything else but >> leave these and the python bits they need. > > Timo, thanks for moving the apport hooks to X. > > Is there any good reason why we shouldn't drop xdiagnose from the > default install and let it be demoted to universe now? Once ubuntu-meta etc stop pulling it in, yes. It does ship failsafe-x -stuff, but with current gfx stack there already is a proper fallback session if the KMS driver fails (fb + swrast), and is less useful anyway since we're on wayland now. If there is something useful to ship then that can be moved to xorg as well. -- t -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1754671] Please test proposed package
Hello dwmw2, or anyone else affected, Accepted network-manager into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/network- manager/1.10.14-0ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Network- manager, which is subscribed to NetworkManager. https://bugs.launchpad.net/bugs/1754671 Title: Full-tunnel VPN DNS leakage regression To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 942856] Re: NetworkManager does not support AES-encrypted private keys for WPA 802.1x authentication
Hello Walter, or anyone else affected, Accepted network-manager into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/network- manager/1.10.14-0ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done verification-done-bionic ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Network- manager, which is subscribed to NetworkManager. https://bugs.launchpad.net/bugs/942856 Title: NetworkManager does not support AES-encrypted private keys for WPA 802.1x authentication To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/942856/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1754671] Re: Full-tunnel VPN DNS leakage regression
systemd accepted to bionic/cosmic-proposed, please test ** Tags removed: verification-failed verification-failed-bionic ** Tags added: verification-needed verification-needed-bionic verification-needed-cosmic ** Changed in: systemd (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Network- manager, which is subscribed to NetworkManager. https://bugs.launchpad.net/bugs/1754671 Title: Full-tunnel VPN DNS leakage regression To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1806269] Re: nm-connection-editor crashes when trying to modify connection without gnome-keyring installed
Hello TJ, or anyone else affected, Accepted network-manager-applet into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /network-manager-applet/1.8.10-2ubuntu3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: network-manager-applet (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Network- manager, which is subscribed to Network Manager Applet. https://bugs.launchpad.net/bugs/1806269 Title: nm-connection-editor crashes when trying to modify connection without gnome-keyring installed To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-applet/+bug/1806269/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1754671] Re: Full-tunnel VPN DNS leakage regression
Hello dwmw2, or anyone else affected, Accepted network-manager into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/network- manager/1.10.6-2ubuntu1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: network-manager (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags removed: verification-done verification-done-bionic ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Network- manager, which is subscribed to NetworkManager. https://bugs.launchpad.net/bugs/1754671 Title: Full-tunnel VPN DNS leakage regression To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
