[Group.of.nepali.translators] [Bug 1641889] Re: The network indicator shows the wrong status
** Changed in: oem-priority Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1641889 Title: The network indicator shows the wrong status Status in Network Manager Applet: Unknown Status in OEM Priority Project: Fix Released Status in OEM Priority Project xenial series: New Status in network-manager-applet package in Ubuntu: Fix Released Status in network-manager-applet source package in Xenial: Fix Committed Bug description: [Summary] The network indicator shows the wrong status [Reproduce Steps] 1.Boot into Ubuntu OS , disconnect wireless connection Note : the issue can't be reproduced with wifi connected 2.Enable/disable wifi function by pressing hotkey then check network manager status [Results] Expected: "Enable Wi-Fi" option should be OFF Actual:"Enable Wi-Fi" option is ON [Additional Information] Product Name:Inspiron-7460 BIOS Version:1.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-applet/+bug/1641889/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1684205] Re: Screen lock button missing when using LightDM
** Also affects: gnome-shell (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: Triaged => Fix Committed ** Changed in: gnome-shell (Ubuntu Trusty) Status: New => Triaged ** Changed in: gnome-shell (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu Xenial) Status: New => Triaged ** Changed in: gnome-shell (Ubuntu Yakkety) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu Yakkety) Status: New => Triaged ** Changed in: gnome-shell (Ubuntu Zesty) Status: New => Triaged ** Changed in: gnome-shell (Ubuntu Zesty) Importance: Undecided => Medium ** Description changed: + Impact + == + A user who installs gnome-shell in Ubuntu 17.04 and earlier is asked to choose between gdm and lightdm. If the user chooses lightdm, the GNOME session will not have a lock button in the system status menu in the top right corner. + + Workaround + == + The keyboard shortcut Super+L still works to lock your screen. + Test Case = 1. a. From Ubuntu GNOME 17.04, install unity-greeter. Choose lightdm as your default. b. Restart c. Log in to GNOME - d. Click the far right of the top bar. The lock icon is missing. + d. Click the far right of the top bar. Make sure that the lock button exists. Click it. Your screen should lock. Or - 2. a. From Ubuntu (Unity) 17.04, install ubuntu-gnome-desktop or gnome-shell. Choose lightdm as your default if asked. + 1. a. From Ubuntu (Unity) 17.04, install ubuntu-gnome-desktop or gnome-shell. Choose lightdm as your default if asked. b. Restart c. Log in to GNOME - d. Click the far right of the top bar. The lock icon is missing. + d. Click the far right of the top bar. Make sure that the lock button exists. Click it. Your screen should lock. - Workaround - == - The keyboard shortcut Super+L still works to lock your screen. + 2. Make sure that the screen lock also still works if you use GDM + instead. + + Regression Potential + + This patch update just allows LightDM to lock the screen if GDM is not running. Other Info == GNOME didn't accept our LightDM patches when we proposed them a few years ago, so this will just need to be fixed in Ubuntu for now. -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1684205 Title: Screen lock button missing when using LightDM Status in Ubuntu GNOME: Triaged Status in gnome-shell package in Ubuntu: Fix Committed Status in gnome-shell source package in Trusty: Triaged Status in gnome-shell source package in Xenial: Triaged Status in gnome-shell source package in Yakkety: Triaged Status in gnome-shell source package in Zesty: Triaged Bug description: Impact == A user who installs gnome-shell in Ubuntu 17.04 and earlier is asked to choose between gdm and lightdm. If the user chooses lightdm, the GNOME session will not have a lock button in the system status menu in the top right corner. Workaround == The keyboard shortcut Super+L still works to lock your screen. Test Case = 1. a. From Ubuntu GNOME 17.04, install unity-greeter. Choose lightdm as your default. b. Restart c. Log in to GNOME d. Click the far right of the top bar. Make sure that the lock button exists. Click it. Your screen should lock. Or 1. a. From Ubuntu (Unity) 17.04, install ubuntu-gnome-desktop or gnome-shell. Choose lightdm as your default if asked. b. Restart c. Log in to GNOME d. Click the far right of the top bar. Make sure that the lock button exists. Click it. Your screen should lock. 2. Make sure that the screen lock also still works if you use GDM instead. Regression Potential This patch update just allows LightDM to lock the screen if GDM is not running. Other Info == GNOME didn't accept our LightDM patches when we proposed them a few years ago, so this will just need to be fixed in Ubuntu for now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1684205/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help :
[Group.of.nepali.translators] [Bug 1673247] Re: package snapd 2.23.1 failed to install/upgrade: trying to overwrite '/etc/apparmor.d/usr.lib.snapd.snap-confine', which is also in package snap-confine
** Also affects: dpkg (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: snapd (Ubuntu Zesty) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1673247 Title: package snapd 2.23.1 failed to install/upgrade: trying to overwrite '/etc/apparmor.d/usr.lib.snapd.snap-confine', which is also in package snap-confine 2.23.1 Status in dpkg package in Ubuntu: In Progress Status in snapd package in Ubuntu: In Progress Status in dpkg source package in Trusty: Confirmed Status in snapd source package in Trusty: In Progress Status in dpkg source package in Xenial: Confirmed Status in snapd source package in Xenial: Confirmed Status in dpkg source package in Yakkety: Confirmed Status in snapd source package in Yakkety: Confirmed Status in dpkg source package in Zesty: New Status in snapd source package in Zesty: New Bug description: When the ubuntu installer runs it has an option to download updates during the install. When this happens snapd/snap-confine 2.22.6 are installed on /target. The upgrade brings in snapd/snap-confine 2.23.1 which has a conffile in /etc/apparmor.d/usr.lib.snapd.snap-confine. The snapd packages declares a breaks/replaces: snapd-confine (<< 2.23) which works correctly on regular upgrades. However it does fail on upgrades with the "--root=/target" that is used by ubiquity. After a bit of debugging it turns out the reason is that src/archives.c:tarobject() has a check for obsolete conffiles in the block around "Is the file an obsolete conffile ...". There is a stat() here that checks that the conff->name and the fnamevb are the same file. This check fails to take the instdir into account and therefore the loop does not continue but falls through to the "does_replace()" checks. Snap 2.23.1 fails to upgrade from 2.21. Known facts: - reporters (and apport) indicate it fails during the install via the live-cd - not reproducible so far on an already installed system - breaks/replaces of snapd are correct - When adding "xenial-proposed" to apt-setup in ubiquity and installing Cause: - when ubiquity runs it uses "dpkg --root=/target --unpack ..." - however when doing the conffile checking dpkg does not handle the "--root" parameter correctly and checks something against "/" instead of "/target". - I really don't know what else to add... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: snapd 2.23.1 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CasperVersion: 1.376.2 Date: Wed Mar 15 16:03:33 2017 DuplicateSignature: package:snapd:2.23.1 Unpacking snapd (2.23.1) over (2.21) ... dpkg: error processing archive /target/var/cache/apt/archives/snapd_2.23.1_amd64.deb (--unpack): trying to overwrite '/etc/apparmor.d/usr.lib.snapd.snap-confine', which is also in package snap-confine 2.23.1 ErrorMessage: trying to overwrite '/etc/apparmor.d/usr.lib.snapd.snap-confine', which is also in package snap-confine 2.23.1 LiveMediaBuild: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: snapd Title: package snapd 2.23.1 failed to install/upgrade: trying to overwrite '/etc/apparmor.d/usr.lib.snapd.snap-confine', which is also in package snap-confine 2.23.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1673247/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1690574] Re: Fix autopkgtest regression with webkit2gtk 2.16.2
This bug was fixed in the package sphinx - 1.5.5-1ubuntu1 --- sphinx (1.5.5-1ubuntu1) artful; urgency=medium * Update jstests for compatibility with WebKitGTK+ 2.16 (LP: #1690574). Now the title property can be no longer than 1000 characters, so we cannot fetch the whole page using it. Instead, we compute the needed numbers with JavaScript and then fetch them using the title property. -- Dmitry ShachnevSat, 13 May 2017 18:52:57 +0300 ** Changed in: sphinx (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1690574 Title: Fix autopkgtest regression with webkit2gtk 2.16.2 Status in sphinx package in Ubuntu: Fix Released Status in sphinx source package in Xenial: Triaged Status in sphinx source package in Yakkety: Triaged Status in sphinx source package in Zesty: Triaged Bug description: Impact -- sphinx's autopkgtests fail with webkit2gtk's 2.16.2 update (LP: #1690536). Since we need to update webkit2gtk for security updates, we need to update sphinx's autopkgtests too. Test Case - Check https://autopkgtest.ubuntu.com/packages/sphinx and make sure that the tests triggered by webkit2gtk 2.16.2 are passing Regression Potential This update only affects the "sphinxdoc" autopkgtest. Other Info --- The autopkgtests are maintained in Debian; this particular test is not from sphinx upstream. https://anonscm.debian.org/git/python- modules/packages/sphinx.git/commit/?id=75bf800 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sphinx/+bug/1690574/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1551599] Re: Remove button missing after package installation
I am unable to duplicate this bug with gnome-software 3.24.1 in Ubuntu 17.10 Alpha. The bug is still present in Ubuntu 17.04 although it feels to me like it's closer to working than it was with earlier versions. ** Also affects: gnome-software (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: gnome-software (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: gnome-software (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: gnome-software (Ubuntu Xenial) Status: New => Confirmed ** Changed in: gnome-software (Ubuntu Xenial) Importance: Undecided => High ** Changed in: gnome-software (Ubuntu Yakkety) Status: New => Confirmed ** Changed in: gnome-software (Ubuntu Yakkety) Importance: Undecided => High ** Changed in: gnome-software (Ubuntu Zesty) Importance: Undecided => High ** Changed in: gnome-software (Ubuntu Zesty) Status: New => Confirmed ** Changed in: gnome-software (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1551599 Title: Remove button missing after package installation Status in One Hundred Papercuts: Confirmed Status in Release Notes for Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Confirmed Status in gnome-software source package in Yakkety: Confirmed Status in gnome-software source package in Zesty: Confirmed Bug description: [What Happens] == Installing -- 1. Open the Software app (GNOME Software). Search for clocks. 2. Click Install next to Clocks. 3. The Install button becomes insensitive and changes to Installing... 4. The Install button becomes sensitive again and changes back to Install (it should have changed to Remove) 5. If you click the Clocks row (still in the All page), the Clocks info page opens with an Install button (it should have a Launch button and a Remove button). 6. If you switch to the Installed page, Clocks correctly shows up with a Remove button. 7. If you click the Clocks row in the Installed page, the Clocks info page correctly opens with a Launch button and a Remove button. 8. Close the Software app then reopen it. Same results as #4-7 above. 9. $ pkill gnome-software 10. Open the Software app. Now Clocks shows up correctly in the All page with a Remove button and the Clocks info page correctly includes the Launch and Remove buttons but not the Install button. Removing 11. Click the Remove button to uninstall Clocks. 12. The Remove button becomes insensitive again and changes to Removing... 12. We basically get the same broken results as before. In the All page, the Clocks row shows Remove still. Clicking the Clocks row shows the Info page with Launch and Remove. One change is that in the Installed page, Clocks shows up twice, once with an Install button, once with a Remove button. Completely stopping the gnome-software process (via logging out or the pkill trick mentioned in #9) is necessary for the Software app to correctly register Clocks as being removed. I was unable to reproduce this bug with Fedora 24. Other Info == See also bug 1582959 which is similar but a bit different. In bug 1679417, a user reported that the package disappears from the Installed list if Remove is selected but password authentication is cancelled or failed. [Original bug report] = Used gnome-software to install a package. Once it was installed I expected to see an option to remove it. As can be seen all I see is the option to Install the package. If you click Install you are then given the option to remove the package. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.19.91~git20160229.ceb6b9d-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Mar 1 08:05:06 2016 InstallationDate: Installed on 2015-10-29 (123 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029) SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1551599/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1568174] Re: Super key with Mate Menu blocks other key combinations
** No longer affects: ubuntu-mate -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1568174 Title: Super key with Mate Menu blocks other key combinations Status in mate-menu package in Ubuntu: Fix Released Status in mate-menu source package in Xenial: Confirmed Bug description: Ubuntu Mate 16.04 To launch the Advanced Mate Menu, you press the Super key, but if you assign the launch of an application with Super + [other key], it wont work and simply opens the Mate Menu. This bug has also been reported to the Linux Mint Mate. https://github.com/linuxmint/mintmenu/issues/98 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-menu/+bug/1568174/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1682686] Re: Mate Advanced Menu does not appear when using Mutiny
This was fixed in Ubuntu MATE 17.10 recently with the release of mate- menu 17.10.0. ** Summary changed: - Mate Advanced Menu or Brisk menu do not appear when using Mutiny + Mate Advanced Menu does not appear when using Mutiny ** Also affects: mate-menu (Ubuntu) Importance: Undecided Status: New ** Also affects: mate-menu (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: mate-menu (Ubuntu) Status: New => Fix Released ** Changed in: mate-menu (Ubuntu Xenial) Status: New => Triaged ** Changed in: mate-menu (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: mate-menu (Ubuntu) Importance: Undecided => Medium ** Changed in: mate-menu (Ubuntu) Assignee: (unassigned) => Martin Wimpress (flexiondotorg) ** Changed in: mate-menu (Ubuntu Xenial) Assignee: (unassigned) => Martin Wimpress (flexiondotorg) ** No longer affects: ubuntu-mate -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1682686 Title: Mate Advanced Menu does not appear when using Mutiny Status in mate-menu package in Ubuntu: Fix Released Status in mate-menu source package in Xenial: Triaged Bug description: On mate 16.10, and 17.04 (and i believe it happened before in 16.04, and it happens on another computer system as well) when i enable any menu besides the simple "Main Menu" the menu will not display in the sidebar, and mate starts acting strange (sometimes crashes entirely and nothing works, or adding and managing applets becomes very slow and stutters) By skipping the pre-defined mutiny theme and assembling a similar layout yourself, the advanced menu can be carried over from the Redmond layout, but if you remove it and try to add it again, it disappears and does not work. Also by logging out it will try to assign your previous layout partially (a duplicate notifications menu and "show the desktop" button) and the advanced menu will also be missing. Usually after a while Ubuntu will show a error message and ask to report it, which i have done in the past. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-menu/+bug/1682686/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp