[Group.of.nepali.translators] [Bug 1678537] Re: Induces login loop after updating.
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1678537 Title: Induces login loop after updating. Status in linux package in Ubuntu: Expired Status in linux source package in Xenial: Expired Bug description: The above the linux (4.4.0-71.92) kernel fails to login after the login screen, since the screen freezes and cannot proceed further. Mouse and keyboard freezes. No response even after trying to get into terminal Alt+Control+F3. The system works fine with the kernal 4.4.0-53(both low latency and ordinary). My system has xorg amd gpu drivers. I suppose there is something closely linked with the driver. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abdul 1830 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.1 HibernationDevice: RESUME=UUID=d5b46fe3-47fb-4203-a8dd-e3badc88825a InstallationDate: Installed on 2017-03-25 (7 days ago) InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213 MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-lowlatency root=/dev/mapper/mint--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-53.74-lowlatency 4.4.30 RelatedPackageVersions: linux-restricted-modules-4.4.0-53-lowlatency N/A linux-backports-modules-4.4.0-53-lowlatency N/A linux-firmware 1.157.8 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: serena Uname: Linux 4.4.0-53-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/10/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A68HM-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1503:bd03/10/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA68HM-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678537/+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 1678537] Re: Induces login loop after updating.
[Expired for linux (Ubuntu Xenial) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu Xenial) Status: Incomplete => Expired -- 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/1678537 Title: Induces login loop after updating. Status in linux package in Ubuntu: Expired Status in linux source package in Xenial: Expired Bug description: The above the linux (4.4.0-71.92) kernel fails to login after the login screen, since the screen freezes and cannot proceed further. Mouse and keyboard freezes. No response even after trying to get into terminal Alt+Control+F3. The system works fine with the kernal 4.4.0-53(both low latency and ordinary). My system has xorg amd gpu drivers. I suppose there is something closely linked with the driver. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abdul 1830 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.1 HibernationDevice: RESUME=UUID=d5b46fe3-47fb-4203-a8dd-e3badc88825a InstallationDate: Installed on 2017-03-25 (7 days ago) InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213 MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-lowlatency root=/dev/mapper/mint--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-53.74-lowlatency 4.4.30 RelatedPackageVersions: linux-restricted-modules-4.4.0-53-lowlatency N/A linux-backports-modules-4.4.0-53-lowlatency N/A linux-firmware 1.157.8 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: serena Uname: Linux 4.4.0-53-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/10/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A68HM-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1503:bd03/10/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA68HM-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678537/+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 1690380] Re: "Cannot open log file '/var/log/nagios3/nagios.log' for reading" error from nagios web UI when view alert history etc.
** Changed in: nagios3 (Ubuntu) Status: Confirmed => Triaged ** Also affects: nagios3 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: nagios3 (Ubuntu Yakkety) 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/1690380 Title: "Cannot open log file '/var/log/nagios3/nagios.log' for reading" error from nagios web UI when view alert history etc. Status in nagios3 package in Ubuntu: Triaged Status in nagios3 source package in Xenial: New Status in nagios3 source package in Yakkety: New Bug description: Ubuntu 16.04.2 LTS nagios3 and nagios3-cgi 3.5.1.dfsg-2.1ubuntu1.1 If install nagios3 package and then view Alert History, Notification History or Events pages (and maybe others), e.g.: http://localhost/cgi-bin/nagios3/history.cgi?host=localhost Then get the following error in place of the information that should be there: Error: Cannot open log file '/var/log/nagios3/nagios.log' for reading! This issue: https://github.com/NagiosEnterprises/nagioscore/issues/303 ...suggests that this is caused by the fix for CVE-2016-9566: https://github.com/NagiosEnterprises/nagioscore/commit/ff22fd0de4938781edcbd48512d2494ca3c9c41a ...which has been back ported to 3.5.1.dfsg-2.1ubuntu1.1 according to: https://launchpad.net/ubuntu/xenial/+source/nagios3/+changelog The permissions and ownership of nagios.log are: $ ls -l /var/log/nagios3/nagios.log -rw--- 1 nagios adm 189 May 12 13:45 /var/log/nagios3/nagios.log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios3/+bug/1690380/+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 1687019] Re: Cannot add a Google account using Online Accounts in Ubuntu Gnome
** Bug watch added: Debian Bug tracker #862156 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862156 ** Also affects: webkit2gtk (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862156 Importance: Unknown Status: Unknown -- 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/1687019 Title: Cannot add a Google account using Online Accounts in Ubuntu Gnome Status in gnome-online-accounts: Unknown Status in Ubuntu GNOME: Fix Released Status in WebKit: Fix Released Status in webkit2gtk package in Ubuntu: Fix Released Status in webkit2gtk source package in Xenial: Fix Released Status in webkit2gtk source package in Yakkety: Fix Released Status in webkit2gtk source package in Zesty: Fix Released Status in webkit2gtk package in Debian: Unknown Bug description: Impact - Users will be unable to log in to a Google account using GNOME Online Account which is used by default in Ubuntu GNOME and Ubuntu Budgie. Any other browser or service that uses webkit2gtk is similarly broken, such as the Epiphany browser. The second issue fixed here is that any user who opted in to the new YouTube will only get a white screen when they attempt to visit YouTube. The new YouTube is still opt-in now but will eventually become the default for everyone. Test Case - 1. Install the updated webkit2gtk on Ubuntu GNOME. 2. Restart your computer (this may be necessary because of LP: #1610944) 3. Log in. Open Settings>Online Accounts. Remove any Google accounts already configured. Add your Google account. 4. Install Evolution if it's not already installed and verify that your Gmail account loads. Optional, because the beta is closed to new entrants: 5. Install epiphany-browser 6. Open the Web app (epiphany-browser) and log in to your Google account. 7. Visit https://www.google.com/new to make sure that your browser is set to use the "new YouTube." 8. If the new YouTube only shows a white screen, this part of the bug is not fixed. Regression Potential The regression potential was limited by only cherry-picking the commits to fix these 2 high-profile issues. 2.16.2 is being rolled out to most distros now. Other Info -- Fixed in 17.10 Alpha "artful" by updating to 2.16.2 Original Bug Report --- With Ubuntu Gnome 17.04 (brand new 64bit install on a Dell XPS13 laptop), I cannot add a Google account using Online-Accounts. If I choose to add a new Google account in Online Accounts, a window appears where I can enter my Google email. After entering my email and pressing the Next button, a window appears where I can enter my Google password. After entering the password and pressing the Next button, an empty window appears and nothing else happens. I expected this to show something useful, and actually add the Google account to my Gnome environment. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1687019/+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 1694945] Re: setuptools v36.0.0 breaks the python plugin
** Changed in: snapcraft Status: Fix Committed => Invalid -- 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/1694945 Title: setuptools v36.0.0 breaks the python plugin Status in Snapcraft: Invalid Status in snapcraft package in Ubuntu: Invalid Status in snapcraft source package in Xenial: Invalid Status in snapcraft source package in Yakkety: Invalid Status in snapcraft source package in Zesty: Invalid Status in snapcraft source package in Artful: Invalid Bug description: [Impact] * setuptools v36.0.0 was released today, which no longer bundles six, thereby breaking the python plugin (both python2 and python3). * The fix is to simply install six before setuptools. [Test Case] * Simply run one of the many python-based integration tests. For example: ./runtests.sh plugins test_python_plugin.py Without this patch, the test will fail. With it, the test will pass. [Regression Potential] * Potential is low as we have a large test suite with a number of python-based snaps. * Pulling in six could potentially conflict with the dependencies of the snap being build, although six was already used previously (it was just bundled with setuptools). To manage notifications about this bug go to: https://bugs.launchpad.net/snapcraft/+bug/1694945/+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 1663354] Re: [Hyper-V] SR-IOV functionality regression in 16.04 HWE proposed
** Changed in: linux (Ubuntu) Status: Triaged => Fix Released ** Changed in: linux (Ubuntu Xenial) Status: Triaged => 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/1663354 Title: [Hyper-V] SR-IOV functionality regression in 16.04 HWE proposed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: Hello, In 1650059 we requested the rebase to the 4.9 kernel LIS commits. Also, from comments #7 and #8 we confirmed that the SR-IOV functionality was working as expected. This was in the test kernel build 4.8.0-33.35. Now, while testing the HWE proposed kernel for Xenial - version 4.8.0-35, we seem to have a regression for SR-IOV. Issues start from the point where the Intel driver is not loaded automatically, then even with manually inserting it, the SR-IOV VF interfaces are not detected. We need to determine if between the test kernel and the proposed one if there have been any other related LIS / SR-IOV commits, or what related ones could have caused this. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1663354/+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 1691180] Re: linux: 4.4.0-79.100 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/xenial/4.4.0-79.100 /xenial-proposed-published.html ** Tags added: certification-testing-passed ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => 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/1691180 Title: linux: 4.4.0-79.100 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1691181 derivatives: 1691182,1691183,1691184,1691186 -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1691180/+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 1685186] Re: [SRU] Mir needs to be updated to 0.26 in 16.04LTS
** Also affects: mir (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: mir (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/1685186 Title: [SRU] Mir needs to be updated to 0.26 in 16.04LTS Status in mir package in Ubuntu: In Progress Status in mir source package in Xenial: In Progress Status in mir source package in Yakkety: In Progress Status in mir source package in Zesty: In Progress Bug description: [Impact] Snap development using Mir has been using the "stable phone overlay" PPA which is both inconvenient and a legacy of the cancelled Unity8 project. It would greatly simplify things if Mir were updated in the Xenial archive. [Test Case] Build a Mir client snap (e.g. lp:~albaguirre/+snap/mir-client-demos) against "Primary Ubuntu Archive" and deploy as described in https://developer.ubuntu.com/en/snappy/guides/mir-snaps/ Expected: the client apps start and are visible on screen Actual: the client apps don't start and are not visible on screen [Regression Potential] Mir has two categories of dependent project: 1 Unity8 and unity-system-compositor "server" packages 2 toolkits and other "clients" of Mir "Server" packages from the archive will stop working in the LTS as they will continue using the earlier libmirserver.so.38 (from Mir 0.21) which doesn't work with the libmirclient.so.9 from Mir 0.26. This is unimportant as these packages were provided as an "early experience", not for serious use. "Client" packages are dependent only on libmirclient.so.9 which is ABI stable. The principle type of regression would be FTBFS where APIs have been deprecated in 0.26. The linked 0.26.3 release has these deprecations disabled for 16.04. The packages are available in silo: https://bileto.ubuntu.com/#/ticket/2736 notes: A recursive search or rdependencies identifies the following packages in category 1: camera-app-autopilot gallery-app-autopilot indicator-network-autopilot indicators-client qtdeclarative5-qtmir-plugin qtmir-android qtmir-desktop qtmir-tests ubuntu-desktop-mir ubuntu-experience-tests ubuntu-pocket-desktop ubuntu-push-autopilot ubuntu-touch ubuntu-touch-session unity8 unity8-autopilot unity8-desktop-session-mir unity-scope-click-autopilot unity-system-compositor unity-system-compositor-autopilot Anyone wanting these packages should switch to the "unity8-desktop- session" preview package in 17.04 where they are far more functional. [Alternatives] If we want to keep everything working in Xenial, we *could* bump the libmirclient SONAME to libmirclient.so.10. This would result in libmirclient9 being NBS, but continuing to work against the Mir servers available in 16.04[*] (until and unless they are rebuilt). However, this does not enable the desired result for IoT deployments of toolkits (GTK, Qt etc) and other clients working against servers (specifically miral-kiosk) built against the updated libraries. To work for IoT these would need to rebuilt from source - at which point they (and their dependencies) would stop working against the servers in category 1. [*] with the exception of the servers provided in mir-examples, these would only work with clients linking against libmirclient.so.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1685186/+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 1694945] Re: setuptools v36.0.0 breaks the python plugin
** Changed in: snapcraft (Ubuntu Zesty) Status: New => Invalid ** Changed in: snapcraft (Ubuntu Yakkety) Status: New => Invalid ** Changed in: snapcraft (Ubuntu Xenial) Status: New => Invalid ** Changed in: snapcraft (Ubuntu Artful) Status: New => Invalid -- 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/1694945 Title: setuptools v36.0.0 breaks the python plugin Status in Snapcraft: Fix Committed Status in snapcraft package in Ubuntu: Invalid Status in snapcraft source package in Xenial: Invalid Status in snapcraft source package in Yakkety: Invalid Status in snapcraft source package in Zesty: Invalid Status in snapcraft source package in Artful: Invalid Bug description: [Impact] * setuptools v36.0.0 was released today, which no longer bundles six, thereby breaking the python plugin (both python2 and python3). * The fix is to simply install six before setuptools. [Test Case] * Simply run one of the many python-based integration tests. For example: ./runtests.sh plugins test_python_plugin.py Without this patch, the test will fail. With it, the test will pass. [Regression Potential] * Potential is low as we have a large test suite with a number of python-based snaps. * Pulling in six could potentially conflict with the dependencies of the snap being build, although six was already used previously (it was just bundled with setuptools). To manage notifications about this bug go to: https://bugs.launchpad.net/snapcraft/+bug/1694945/+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
