[Touch-packages] [Bug 1611745] Re: OpenGL not working through ssh -X
I have the same problem. If I force indirect rendering like below, it works, but it's not a good solution. 1. Create /etc/lightdm/lightdm.conf.d/50-xserver-command.conf : [SeatDefaults] # Dump core xserver-command=X -core +iglx 2. Restart LightDM # systemctl restart lightdm -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1611745 Title: OpenGL not working through ssh -X Status in xorg package in Ubuntu: Confirmed Bug description: I need to run several OpenGL-depending programs through ssh -x, like tecplot, mayavi or paraview. I connect to the remote machine with ssh -X (or ssh -Y, doesn't matter). Then I test opengl using e.g. glxinfo. The output of glxinfo on the remote machine says that it was unable to create the OpenGL context. In the other remote programs I receive the same error message. On the local machine, it works fine. See the logfiles attached (local_glxinfo.log, remote_glxinfo.log). I configured my Xorg according to the attached xorg.conf. The configuration was produced with nvidia-settings and two manual tweaks, lines 54 and 74. I added those lines because I could not (and still can't) enforce indirect rendering of my graphics card. Indirect rendering is still switched off, see lines 102 and 167 in Xorg.0.log. The issue does also occur when no manually generated xorg.conf is present. I'm using the latest drivers from the package nvidia-361. The issue occurs with and without my graphics card (Intel HD 4600, or GeForce 605). Before I switched to ubuntu-gnome 16.04 I had a xubuntu 14.04 LTS running. There some applications would work, other would not. Now nothing works at all. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook nvidia_uvm nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Wed Aug 10 13:32:00 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-34-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-34-generic, x86_64: installed virtualbox, 5.0.24, 4.4.0-34-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GF119 [GeForce 605] [10de:1048] (rev a1) (prog-if 00 [VGA controller]) Subsystem: LeadTek Research Inc. GF119 [GeForce 605] [107d:5afd] InstallationDate: Installed on 2016-08-09 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) MachineType: FUJITSU ESPRIMO P720 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic root=UUID=7b7bc513-0076-48db-a71b-28299a8a30e3 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2013 dmi.bios.vendor: FUJITSU // American Megatrends Inc. dmi.bios.version: V4.6.5.4 R1.3.0 for D3221-A1x dmi.board.name: D3221-A1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3221-A1 dmi.chassis.type: 6 dmi.chassis.vendor: FUJITSU dmi.chassis.version: C$WX02 dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV4.6.5.4R1.3.0forD3221-A1x:bd05/28/2013:svnFUJITSU:pnESPRIMOP720:pvr:rvnFUJITSU:rnD3221-A1:rvrS26361-D3221-A1:cvnFUJITSU:ct6:cvrC$WX02: dmi.product.name: ESPRIMO P720 dmi.sys.vendor: FUJITSU version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Aug 10 11:27:40 2016
[Touch-packages] [Bug 1342271] Re: lpq has long hang before completion.
Hello, I use remote printers over CUPS server and I have the same issue on my computers installed with Ubuntu 14.04 (no problem with Ubuntu 12.04) : $ time lpq printer printer is ready no entries real 1m0.082s user 0m0.010s sys 0m0.007s If you need information or if you want me to perform tests, don't hesitate to ask me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1342271 Title: lpq has long hang before completion. Status in cups package in Ubuntu: Confirmed Bug description: ubuntu 12.04 does not have this long hang issue. See attached straces - one from a machine with 12.04 and one to the same remote cups server using a 14.04 client. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups-client 1.7.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CupsErrorLog: CurrentDesktop: Unity Date: Tue Jul 15 14:26:40 2014 InstallationDate: Installed on 2014-06-18 (27 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: To be filled by O.E.M. To be filled by O.E.M. Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-30-generic root=UUID=a86d2294-0ef2-4c23-b951-ea3199bad7e7 ro rootflags=subvol=@ quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2202 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 LE R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2202:bd12/12/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1342271/+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 1342271] Re: lpq has long hang before completion.
This solution works for me : in /etc/cups/client.conf we added /version=1.1 to the server address : ServerName printhost.yourserveraddress.com/version=1.1 See http://askubuntu.com/questions/518723/ubuntu-14-04-cups-problem -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1342271 Title: lpq has long hang before completion. Status in cups package in Ubuntu: Confirmed Bug description: ubuntu 12.04 does not have this long hang issue. See attached straces - one from a machine with 12.04 and one to the same remote cups server using a 14.04 client. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups-client 1.7.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CupsErrorLog: CurrentDesktop: Unity Date: Tue Jul 15 14:26:40 2014 InstallationDate: Installed on 2014-06-18 (27 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: To be filled by O.E.M. To be filled by O.E.M. Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-30-generic root=UUID=a86d2294-0ef2-4c23-b951-ea3199bad7e7 ro rootflags=subvol=@ quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2202 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 LE R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2202:bd12/12/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1342271/+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 1414557] [NEW] Software Updater doesn't indicate all avalailable upgrades
Public bug reported: Hello everybody, 1) My release of Ubuntu : $ lsb_release -rd Description:Ubuntu 14.04.1 LTS Release:14.04 2) The version of package I'm using : update-manager 1:0.196.12 3) What you expected to happen ? I expect to install all available upgrades when I manually launch Software Updater (update-manager). 4) What happened instead ? aptitude (and apt-get) indicates avalaible upgrades while Software Updater (update-manager) indicates no available upgrades. My configuration of Software Updater (update-manager) : Automatically check for updates : Daily When there are security updates : Display immediatly When there are other updates : Display immediatly My configuration in dconf : path : /com/ubuntu/update-notifier/regular-auto-launch-interval key type : i key name : regular-auto-launch-interval key value : 0 summary : Interval (in days) when to auto launch for normal updates description : The interval (in days) when auto launching update-manager for normal updates. Please note that it will auto launch for security updates immediately. If you set it to 0 it will also launch as soon as updates become available. Tests : 2015-01-14 : $ aptitude safe-upgrade -s The following packages will be upgraded: compiz compiz-core compiz-gnome compiz-plugins-default libcgmanager0 libcgmanager0:i386 libclutter-gtk-1.0-0 libcompizconfig0 libdecoration0 9 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 1463 kB of archives. After unpacking 0 B will be used. $ update-manager = The software on this computer is up to date in a pop-up 2015-01-15 : update-manager suggests to upgrade libclutter-gtk-1.0-0 On 2015-01-14, this package was not suggested by update-manager but was suggested by aptitude . 2015-01-16 : update-manager suggests to upgrade libcgmanager0 On 2015-01-14, this package was not suggested by update-manager but was suggested by aptitude . 2015-01-23 : aptitude safe-upgrade -s The following packages will be upgraded: compiz compiz-core compiz-gnome compiz-plugins-default libcompizconfig0 libdecoration0 python-cupshelpers system-config-printer-common system-config-printer-gnome system-config-printer-udev The following packages are RECOMMENDED but will NOT be installed: avahi-utils 10 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 1 610 kB of archives. After unpacking 2 048 B will be used. Do you want to continue? [Y/n/?] Would download/install/remove packages. $ update-manager = The software on this computer is up to date in a pop-up 2015-01-26 : $ aptitude safe-upgrade -s The following packages will be upgraded: compiz compiz-core compiz-gnome compiz-plugins-default libcompizconfig0 libdecoration0 6 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 1 387 kB of archives. After unpacking 0 B will be used. Do you want to continue? [Y/n/?] Would download/install/remove packages. $ update-manager = The software on this computer is up to date in a pop-up Thanks. ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Package changed: unity (Ubuntu) = update-manager (Ubuntu) -- 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/1414557 Title: Software Updater doesn't indicate all avalailable upgrades Status in update-manager package in Ubuntu: New Bug description: Hello everybody, 1) My release of Ubuntu : $ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 2) The version of package I'm using : update-manager 1:0.196.12 3) What you expected to happen ? I expect to install all available upgrades when I manually launch Software Updater (update-manager). 4) What happened instead ? aptitude (and apt-get) indicates avalaible upgrades while Software Updater (update-manager) indicates no available upgrades. My configuration of Software Updater (update-manager) : Automatically check for updates : Daily When there are security updates : Display immediatly When there are other updates : Display immediatly My configuration in dconf : path : /com/ubuntu/update-notifier/regular-auto-launch-interval key type : i key name : regular-auto-launch-interval key value : 0 summary : Interval (in days) when to auto launch for normal updates description : The interval (in days) when auto launching update-manager for normal updates. Please note that it will auto launch for security updates immediately. If you set it to 0 it will also launch as soon as updates become available. Tests : 2015-01-14 : $ aptitude safe-upgrade -s The following packages will be upgraded: compiz compiz-core compiz-gnome compiz-plugins-default libcgmanager0 libcgmanager0:i386 libclutter-gtk-1.0-0 libcompizconfig0 libdecoration0 9 packages upgraded, 0 newly
[Touch-packages] [Bug 1414110] [NEW] Wireless powersave doesn't work (pm-utils)
Public bug reported: Hello, I notice a bug about wireless powersave (pm-utils 1.4.1-13ubuntu0.1 on Ubuntu 14.04.1 LTS using kernel 3.13.0-44-generic) : # PM_FUNCTIONS=/usr/lib/pm-utils/functions /usr/lib/pm-utils/power.d/wireless true cat: /sys/class/net/wlan0/device/enabled: No such file or directory If I replace '/sys/class/net/wlan0/device/enabled' by '/sys/class/net/wlan0/device/enable' in '/usr/lib/pm- utils/power.d/wireless', it seems to work fine : # PM_FUNCTIONS=/usr/lib/pm-utils/functions /usr/lib/pm-utils/power.d/wireless true Turning powersave for wlan0 on...Done. Is it possible to fix this bug ? Thanks :) ** Affects: pm-utils (Ubuntu) Importance: Undecided Status: New ** Package changed: gvfs (Ubuntu) = pm-utils (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1414110 Title: Wireless powersave doesn't work (pm-utils) Status in pm-utils package in Ubuntu: New Bug description: Hello, I notice a bug about wireless powersave (pm-utils 1.4.1-13ubuntu0.1 on Ubuntu 14.04.1 LTS using kernel 3.13.0-44-generic) : # PM_FUNCTIONS=/usr/lib/pm-utils/functions /usr/lib/pm-utils/power.d/wireless true cat: /sys/class/net/wlan0/device/enabled: No such file or directory If I replace '/sys/class/net/wlan0/device/enabled' by '/sys/class/net/wlan0/device/enable' in '/usr/lib/pm- utils/power.d/wireless', it seems to work fine : # PM_FUNCTIONS=/usr/lib/pm-utils/functions /usr/lib/pm-utils/power.d/wireless true Turning powersave for wlan0 on...Done. Is it possible to fix this bug ? Thanks :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1414110/+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 1311316] Re: After locking screen there is no input field to type password for unlock
For infomation : I used Marco Trevisan's unity package since 2014-09-11 without getting this issue. This morning I installed unity (up to date) from Ubuntu repository and I just get this issue. Like David, the first times I get this bug, I noticed some issues with window animations before it happened (windows were moving very slowly). -- 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/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Confirmed Status in Unity 7.2 series: Confirmed Status in unity package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+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 1311316] Re: After locking screen there is no input field to type password for unlock
For my part, reading explanations above, I understand it may be an LDAP configuration issue. However, I perform tests on 2 PC with the same configuration (LDAP Authentication, home areas served by NFS + automount, multimonitor) : - PC 1 using Marco Trevisan's unity package (https://launchpad.net/~3v1n0/+archive/ubuntu/unity-tests) works perfectly since installation of Marco's package (2014-09-11), before I get this issue every couple days, so I think Marco Trevisan's unity package probably fixed this bug. - PC 2 using Unity up to date from Ubuntu repository, I get this issue randomly (about once a week). So I think this is an issue related to Unity. Like there is a known and not solved Unity bug about this issue, for me, this is not logical to search the cause of this bug elsewhere (maybe I'm wrong). So msp3k and Philipp Wendler (and others using LDAP authentication), could you test Marco Trevisan's unity package and tell us if it solves this bug ? https://launchpad.net/~3v1n0/+archive/ubuntu/unity-tests -- 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/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Confirmed Status in Unity 7.2 series: Confirmed Status in unity package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+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 1311316] Re: After locking screen there is no input field to type password for unlock
For me, the bug status is not clear ? Someone know if the fix for Ubuntu 14.04 has been released or not ? Below what I understand : - The fix has not been yet released for Ubuntu 14.04 - The fix will be released on Ubuntu 14.04 with Unity 7.2.4 (The current release of Unity is 7.2.3) = https://launchpad.net/unity = https://launchpad.net/unity/+milestones = https://launchpad.net/unity/+milestone/7.2.4 Anyone can tell me if I'm right or not ? Thanks and have a good day ;) -- 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/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Confirmed Status in Unity 7.2 series: Confirmed Status in unity package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+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 1311316] Re: After locking screen there is no input field to type password for unlock
Thanks for your answer and also for your work Andrea ! Thanks to Marco Trevisan too. Sorry for my english but I don't understand if the fix works or not when you say We released a fix but it does not work then The one we released was text entry not showing randomly on multimonitor and seems to be fixed, for me it's contradictory. What I can say : - My PC using Marco Trevisan's unity package (https://launchpad.net/~3v1n0/+archive/ubuntu/unity-tests) works perfectly since 2014-09-11, - Another PC using Ubuntu's unity package, randomly, I have no input field to type password for unlock (normally this PC is up to date but I have to check). Both use multimonitor and LDAP authentication. -- 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/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Confirmed Status in Unity 7.2 series: Confirmed Status in unity package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+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 1311316] Re: After locking screen there is no input field to type password for unlock
Hello, I saw this bug seems to be fixed and released on September 17, anybody knows in which repository this fix has been released? Is this in trusty-proposed repository? How will we know if this fix has been released in the Trusty stable repository? Is this when Unity 7.2.4 will be released? Do you have any idea how long will it take? Have a good day and thanks for your help. -- 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/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+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 1311316] Re: After locking screen there is no input field to type password for unlock
I installed Marco Trevisan's unity package (https://launchpad.net/~3v1n0/+archive/ubuntu/unity-tests) on Monday, September 8 and I haven't had this issue since. Usually, I have this issue every couple of days so this package seems to correct it. For information, I have a very very very little display bug : after typing my password, when I press enter to unlock, some pixels of the arrow on the right of the password field appears to flicker (this is not a problem for me). This package will be released in official repositories ? Thanks. -- 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/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+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 1311316] Re: After locking screen there is no input field to type password for unlock
Hello tongr, For my part greeter-show-manual-login is enabled for several month and I have this issue every couple of days. I'm testing Marco Trevisan's unity package (https://launchpad.net/~3v1n0/+archive/ubuntu/unity-tests), I installed it last monday and I haven't had this issue since. I wait a little longer before validating. -- 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/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Triaged Status in “unity” package in Ubuntu: Confirmed Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+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 1311316] Re: After locking screen there is no input field to type password for unlock
This morning, I made a standard Ubuntu 14.04 installation on a dual-screen computer. I launched processes in order to use 100% of the CPUs, and I reprocuded this bug twice (I don't know if this bug is related to the CPUs usage). I also found this bug on other computers using local or LDAP accounts. I tryed to reproduce this bug on a single-screen computer but I didn't see any problem, so I think this bug is related to the dual-screen configuration. To ensure : Someone has this bug on a single-screen computer ? I know somebody who uses Ubuntu 14.04/Unity on a dual-screen computer and seems do not have this bug, do you need specific informations about the configuration of his system ? Is there a possibility to use another locker than the Unity locker ? If you need me for information or make tests/debugging, don't hesitate to contact me. Thanks. Attachement = sysinfo.txt : 1. system information about the computer impacted by this bug 2. system information about the computer which seems NOT impacted by this bug 3. additionnal packages installed on the computer which seems NOT impacted by this bug ** Attachment added: sysinfo.txt https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1311316/+attachment/4195367/+files/sysinfo.txt -- 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/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Triaged Status in “unity” package in Ubuntu: Confirmed Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+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
