[Touch-packages] [Bug 1605813] Re: lock screen freezes while trying to wake from suspend
I too was affected by this bug. I run a fully updated 16.04 installation (currently 16.04.2) of Ubuntu. I used nouveau. When I pressed the power button on my work desktop to wake it from suspend, *sometimes* (here I differ from the original reporter) the login screen would appear and freeze. The system would not completely lock up. I could use ctrl + alt + f2 to switch to TTY2 and then restart the computer, like the original reporter. If I tried restarting lightdm via sudo service lightdm restart, the computer would completely lock up and I had to perform a hard restart. I successfully worked around the issue by installing the proprietary nvidia driver (nvidia-340). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1605813 Title: lock screen freezes while trying to wake from suspend Status in lightdm package in Ubuntu: Confirmed Bug description: Background: I am running a fully updated 16.04.1 installation of Ubuntu using open source nVidia drivers. When I press the power button on my PC to wake the computer from suspend, the login screen appears and freezes. The box around my username becomes somewhat opaque and no text box that would allow me to enter my password appears. I have tried this many times, and it always locks up in the same way. Steps taken after issue occurs: I have found, however, that the system is not completely locked up. I can use CTL + ALT + F2 to switch to TTY2. From there I can login and restart the computer without issue. I also tried restarting lightdm via sudo service lightdm restart. When I tried this and switched back to the GUI, the login screen was loaded, and I could type my password. Once the login screen disappeared, one of my monitors (dual-monitor setup) switched to my user account's wallpaper, and then the system locked up. I had to perform a hard restart. Workaround: I have found that using the proprietary 361.42 drivers provides a work around for this issue. When using the proprietary drivers, the computer resumes from suspend without issue. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jul 22 20:53:10 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-08 (14 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1605813/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 801073] Re: [dash] Dash is shown when pressing and releasing quickly super+KEY
On Ubuntu 14.10 this still happens, and annoys me. It happens both on my laptop and my work desktop. Interestingly, Super+s and Super+w work fine even if I type them extremely quickly, but Super+a does not work and inputs 'a' to the focused application instead of opening the application lens. Analogous problems occur with Super+f, Super+m, Super+c and Super+v. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/801073 Title: [dash] Dash is shown when pressing and releasing quickly super+KEY Status in Unity: Confirmed Status in Unity 2D: Fix Released Status in unity package in Ubuntu: Confirmed Status in unity-2d package in Ubuntu: Fix Released Bug description: Steps to reproduce: 1. Press the Super key and the L key 2. Release both of these keys as soon as possible (duration between step 1 and 2 has to be under 250ms) Current Result: The dash shows up. Expected Result: Nothing happens. Note: if you choose a key that is supposed to show a particular lens, for example the A key, then it's even worse: the dash shows up and immediately disappears To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/801073/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1019347] Re: A message: mount: / is busy appears every time shutting down or rebooting.
I recently had this problem on a 14.10 notebook. This notebook was upgraded from 14.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1019347 Title: A message: mount: / is busy appears every time shutting down or rebooting. Status in plymouth package in Ubuntu: Incomplete Status in upstart package in Ubuntu: Invalid Bug description: I arrived here from bug 963106 [https://bugs.launchpad.net/bugs/963106]. I thought that it was a problem with network-manager, but it was not. I was suggested that it is probably a problem with upstart : that modemmanager simply hasn't had time to complete the shutdown process before umountroot is run. Since modemmanager is an upstart job, sendsigs doesn't kill it. lsb_release -rd: Description: Ubuntu 12.04 LTS Release: 12.04 apt-cache policy upstart: upstart: Installed: 1.5-0ubuntu7 Candidate: 1.5-0ubuntu7 Version table: *** 1.5-0ubuntu7 0 500 http://kambing.ui.ac.id/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.5-0ubuntu5 0 500 http://kambing.ui.ac.id/ubuntu/ precise/main amd64 Packages Hope this will be fixed. Thanks. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: upstart 1.5-0ubuntu7 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Sat Jun 30 00:08:18 2012 InstallationMedia: Custom Live CD - Release amd64 SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1019347/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410792] [NEW] Feature request: add --auto-remove to apt command or make it default behavior
Public bug reported: When one removes a package, one usually wants to auto-remove the dependencies which were automatically installed and are no longer needed by any package. This feature is default on aptitude, and in apt-get it is enable by --auto-remove. Because the apt command lacks this feature (neither by default nor via a flag) then I have to remove packages with aptitude. Adding the --auto-remove flag to apt (or making it the default behavior) would make it more useful and user-friendly; new users would have to learn only one command (apt) for all common tasks, leaving other commands for specialized tasks. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: apt 1.0.9.2ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jan 14 10:56:30 2015 InstallationDate: Installed on 2014-04-28 (260 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: apt UpgradeStatus: Upgraded to utopic on 2014-10-25 (80 days ago) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1410792 Title: Feature request: add --auto-remove to apt command or make it default behavior Status in apt package in Ubuntu: New Bug description: When one removes a package, one usually wants to auto-remove the dependencies which were automatically installed and are no longer needed by any package. This feature is default on aptitude, and in apt-get it is enable by --auto-remove. Because the apt command lacks this feature (neither by default nor via a flag) then I have to remove packages with aptitude. Adding the --auto-remove flag to apt (or making it the default behavior) would make it more useful and user- friendly; new users would have to learn only one command (apt) for all common tasks, leaving other commands for specialized tasks. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: apt 1.0.9.2ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jan 14 10:56:30 2015 InstallationDate: Installed on 2014-04-28 (260 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: apt UpgradeStatus: Upgraded to utopic on 2014-10-25 (80 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1410792/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1283775] Re: Launcher: icon pips are not always updated properly
Unity version from trusty-proposed fixes this issue. I have tested it for several days and did not notice and regression. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1283775 Title: Launcher: icon pips are not always updated properly Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Committed Bug description: [Impact] The number of pips next to the Launcher icon may not be accurate and lead the user to believe that the number of open windows for a particular app is not what is true in reality. [Test Case] 1. Open up 2 Firefox windows. 2. Close one of the windows. Pips (the little arrows) next to the Launcher icon should reflect the number of open windows. [Regression potential] None identified. Original Description: Only occurs when there is just 1 app's windows (unmaxed), assumes multiple workspaces is enabled Test case: Open nautilus (1 pip shows up R. click nautilus icon open another nautilus window (a 2nd pip does not show, likely due to Bug 1281816 Drag the 2nd naut window fully into current ws, 2nd pip still not shown Click on Desktop, 2nd pip shows up Close one of the naut windows, icon still shows 2 pips. Click again on Desktop, 2nd pip is then removed ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140220-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sun Feb 23 12:28:18 2014 InstallationDate: Installed on 2014-02-22 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140222) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1283775/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
