[Dx-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
>It's a dfferrent new bug. I think there is already a similar bug open. What languages are you using? Please try to unlock after changing the language in the keyboard indicator. I use Icelandic. It has extra letters, such as þæðöÞÆÐÖ (and accented), over English (as it is a superset I never change to English layout) but as I said I'm not using those in my password. And this bug had just happened for the first time while getting no password prompt has happened many times. I changed to gnome-shell, at least to try out, so I do not expect the bug to happen there.. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages 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: *** IMPORTANT ** *** The fix is not included in TRUSTY. Will be included with next SRU. *** If you can reproduce this bug please be sure to provide the following info: 1. Do you use a multi-head setup? If yes, using just one monitor fixes the issue? 2. Can you reproduce all the time? 3. Do you use ldap? If yes, using gnome-screensaver fix the issue (see comment #115) can you still reproduce that? 4. Please consider posting /var/log/auth.log (at least part of it, should not contain sensitive information) 5. Please specify the unity version *** END IMPORTANT ** 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1390625] Re: mouse cursor gets corrupted
A possible workaround in Ubuntu 14.10 Unity, until it gets fixed: (1) Open "Screen Display", (2) change selection in the drop-down list below "Scale all window contents to match:" and (3) Apply. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1390625 Title: mouse cursor gets corrupted Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: In Ubuntu 14.10, the mouse cursor graphic gets corrupted under certain occasions. It then looks flipped, sheared or shows fragments of a previous cursor. * when switching the cursor them forth and back in Gnome Tweak Tool * when drag&dropping a document icon Maybe related, the cursor does not always show the correct image scale on a high-dpi display (this was working right in 14.04). For example after login, or when hovering specific areas, or on mouse down to start a drag&drop, the cursor appears 1/4 the expected size. Attached is a photo of a corrupted cursor (whereas a screenshot with Gimp showed the uncorrupted cursor). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 BootLog: * Setting up X socket directories... [400G [394G[ OK ] CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Nov 7 22:12:52 2014 DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-02-02 (278 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash acpi_backlight=vendor SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Nov 7 14:54:59 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 1 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16970 vendor SDC xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1390625/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
I've just run into this with Ubuntu 14.04.1, updated today at about 15:45. I didn't happen immediately after the update, in fact it was fine for a few hours so I think it's unlikely to be related. Some info: * unity --version: unity 7.2.3 * uname -r -v -p -i -o: 3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 x86_64 x86_64 GNU/Linux * Dual-head?: yes, 2 monitors * modified pam?: no, and not using ldap * Running 2 VMware Workstation 10 VMs (both Windows 7 x86_64) I have too much work (in VMs) going to risk re-setting unity, so I'm going to have to wait for it to timeout and hope! Some redacted output from /var/log/auth.log: Jan 8 14:24:12 machinename compiz: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Jan 8 14:24:12 machinename compiz: PAM adding faulty module: pam_kwallet.so Jan 8 14:24:12 machinename compiz: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "my-username" Jan 8 14:39:43 machinename compiz: gkr-pam: unlocked login keyring Jan 8 14:41:59 machinename compiz: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Jan 8 14:41:59 machinename compiz: PAM adding faulty module: pam_kwallet.so Jan 8 14:41:59 machinename compiz: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "my-username" Jan 8 14:42:57 machinename compiz: gkr-pam: unlocked login keyring Jan 8 14:43:04 machinename compiz: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Jan 8 14:43:04 machinename compiz: PAM adding faulty module: pam_kwallet.so Jan 8 14:43:04 machinename compiz: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "my-username" Jan 8 14:47:37 machinename compiz: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Jan 8 14:47:37 machinename compiz: PAM adding faulty module: pam_kwallet.so Jan 8 14:47:37 machinename compiz: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "my-username" Jan 8 14:47:41 machinename compiz: gkr-pam: unlocked login keyring Jan 8 14:48:38 machinename compiz: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Jan 8 14:48:38 machinename compiz: PAM adding faulty module: pam_kwallet.so Jan 8 14:48:38 machinename compiz: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "my-username" Jan 8 14:49:01 machinename compiz: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Jan 8 14:49:01 machinename compiz: PAM adding faulty module: pam_kwallet.so Jan 8 14:49:10 machinename compiz: gkr-pam: unlocked login keyring Jan 8 14:49:10 machinename compiz: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "my-username" Jan 8 14:54:45 machinename compiz: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Jan 8 14:54:45 machinename compiz: PAM adding faulty module: pam_kwallet.so Robin -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages 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: *** IMPORTANT ** *** The fix is not included in TRUSTY. Will be included with next SRU. *** If you can reproduce this bug please be sure to provide the following info: 1. Do you use a multi-head setup? If yes, using just one monitor fixes the issue? 2. Can you reproduce all the time? 3. Do you use ldap? If yes, using gnome-screensaver fix the issue (see comment #115) can you still reproduce that? 4. Please consider posting /var/log/auth.log (at least part of it, should not contain sensitive information) 5. Please specify the unity version *** END IMPORTANT ** 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
[Dx-packages] [Bug 1301125] Re: Lock screen after idle time freezes unity
In a shell I am able to export DISPLAY variable and unity --replace to work around the problem. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1301125 Title: Lock screen after idle time freezes unity Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Hello, I recently upgrade to 14.04. My system uses fglrx provided by 14.04. When I lock manually the screen, I get no problem. I can even sleep the system without problem. However, when the screen is locked by idle time, I cannot unlock it. At this point, I can see the screen but with some kind of translucent panel over it. Mouse also works. I tried to type blink the password but I had no luck. I only get a working system by going text mode (ctrl+alt+f1) and restarting lightdm. No dmesg or Xorg logs seems to indicate any error. The only strange log was in .xsession-errors.old: init: processos unity-settings-daemon main (2495) terminados com status 1 init: processos gnome-session (Unity) main (2539) terminados com status 1 init: processos unity-panel-service main (2572) terminados com status 1 init: processos hud main (2536) terminados com status 1 init: processo indicator-powermain (2740) morto pelo sinal TERM init: processo indicator-datetimemain (2741) morto pelo sinal TERM init: processo indicator-soundmain (2747) morto pelo sinal TERM init: processo indicator-printersmain (2748) morto pelo sinal TERM init: processo indicator-sessionmain (2768) morto pelo sinal TERM init: processo indicator-syncmain (2795) morto pelo sinal TERM init: processo update-notifier-crash (/var/crash/_usr_bin_istanbul.1000.crash)main (4987) morto pelo sinal TERM init: processos unity-panel-service-lockscreen main (7447) terminados com status 1 init: Disconnected from notified D-Bus bus init: processos at-spi2-registryd main (2538) terminados com status 1 But as it has no time info, I cannot tell when they happened. At least another user faces the same problem: http://ubuntuforums.org/showthread.php?t=2214421 And this seems to be different from bug 1283938 as pm sleep/wake works as expected. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140328.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Apr 2 00:01:05 2014 DistUpgraded: 2014-03-31 21:24:46,145 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-updates, 13.350.1, 3.11.0-18-generic, x86_64: installed fglrx-updates, 13.350.1, 3.13.0-20-generic, x86_64: installed vboxhost, 4.3.10, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.10, 3.13.0-20-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] [1002:6758] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0012] InstallationDate: Installed on 2012-10-19 (529 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) JockeyStatus: kmod:wl - Broadcom STA wireless driver (Proprietário, Desativado, Não está em uso) [auto-install] kmod:fglrx - Video driver for the AMD graphics accelerators (Proprietário, Desativado, Não está em uso) kmod:fglrx_updates - ATI Fire GL (Proprietário, Habilitado, Não está em uso) MachineType: Dell Inc. XPS 8300 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=6633d579-d782-47ec-ad5a-22abac1412a0 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-01 (1 days ago) dmi.bios.date: 10/17/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0Y2MRG dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd10/17/2011:svnDellInc.:pnXPS8300:pvr:rvnDellInc.:rn0Y2MRG:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.name: XPS 8300 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.
Re: [Dx-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
Robin, a fix for this issue is scheduled for next SRU (almost ready!). Resetting unity from tt1 should be just fine. Or you can run metacity --replace. 2015-01-08 17:01 GMT+01:00 nybbler : > I've just run into this with Ubuntu 14.04.1, updated today at about > 15:45. I didn't happen immediately after the update, in fact it was fine > for a few hours so I think it's unlikely to be related. > > Some info: > * unity --version: unity 7.2.3 > * uname -r -v -p -i -o: 3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 > 19:35:06 UTC 2014 x86_64 x86_64 GNU/Linux > * Dual-head?: yes, 2 monitors > * modified pam?: no, and not using ldap > * Running 2 VMware Workstation 10 VMs (both Windows 7 x86_64) > > I have too much work (in VMs) going to risk re-setting unity, so I'm > going to have to wait for it to timeout and hope! > > Some redacted output from /var/log/auth.log: > > Jan 8 14:24:12 machinename compiz: PAM unable to dlopen(pam_kwallet.so): > /lib/security/pam_kwallet.so: cannot open shared object file: No such file > or directory > Jan 8 14:24:12 machinename compiz: PAM adding faulty module: > pam_kwallet.so > Jan 8 14:24:12 machinename compiz: pam_succeed_if(lightdm:auth): > requirement "user ingroup nopasswdlogin" not met by user "my-username" > Jan 8 14:39:43 machinename compiz: gkr-pam: unlocked login keyring > Jan 8 14:41:59 machinename compiz: PAM unable to dlopen(pam_kwallet.so): > /lib/security/pam_kwallet.so: cannot open shared object file: No such file > or directory > Jan 8 14:41:59 machinename compiz: PAM adding faulty module: > pam_kwallet.so > Jan 8 14:41:59 machinename compiz: pam_succeed_if(lightdm:auth): > requirement "user ingroup nopasswdlogin" not met by user "my-username" > Jan 8 14:42:57 machinename compiz: gkr-pam: unlocked login keyring > Jan 8 14:43:04 machinename compiz: PAM unable to dlopen(pam_kwallet.so): > /lib/security/pam_kwallet.so: cannot open shared object file: No such file > or directory > Jan 8 14:43:04 machinename compiz: PAM adding faulty module: > pam_kwallet.so > Jan 8 14:43:04 machinename compiz: pam_succeed_if(lightdm:auth): > requirement "user ingroup nopasswdlogin" not met by user "my-username" > Jan 8 14:47:37 machinename compiz: PAM unable to dlopen(pam_kwallet.so): > /lib/security/pam_kwallet.so: cannot open shared object file: No such file > or directory > Jan 8 14:47:37 machinename compiz: PAM adding faulty module: > pam_kwallet.so > Jan 8 14:47:37 machinename compiz: pam_succeed_if(lightdm:auth): > requirement "user ingroup nopasswdlogin" not met by user "my-username" > Jan 8 14:47:41 machinename compiz: gkr-pam: unlocked login keyring > Jan 8 14:48:38 machinename compiz: PAM unable to dlopen(pam_kwallet.so): > /lib/security/pam_kwallet.so: cannot open shared object file: No such file > or directory > Jan 8 14:48:38 machinename compiz: PAM adding faulty module: > pam_kwallet.so > Jan 8 14:48:38 machinename compiz: pam_succeed_if(lightdm:auth): > requirement "user ingroup nopasswdlogin" not met by user "my-username" > Jan 8 14:49:01 machinename compiz: PAM unable to dlopen(pam_kwallet.so): > /lib/security/pam_kwallet.so: cannot open shared object file: No such file > or directory > Jan 8 14:49:01 machinename compiz: PAM adding faulty module: > pam_kwallet.so > Jan 8 14:49:10 machinename compiz: gkr-pam: unlocked login keyring > Jan 8 14:49:10 machinename compiz: pam_succeed_if(lightdm:auth): > requirement "user ingroup nopasswdlogin" not met by user "my-username" > Jan 8 14:54:45 machinename compiz: PAM unable to dlopen(pam_kwallet.so): > /lib/security/pam_kwallet.so: cannot open shared object file: No such file > or directory > Jan 8 14:54:45 machinename compiz: PAM adding faulty module: > pam_kwallet.so > > Robin > > -- > You received this bug notification because you are a bug assignee. > 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: > *** IMPORTANT ** > > *** The fix is not included in TRUSTY. Will be included with next SRU. > *** > > If you can reproduce this bug please be sure to provide the following > info: > 1. Do you use a multi-head setup? If yes, using just one monitor fixes > the issue? > 2. Can you reproduce all the time? > 3. Do you use ldap? If yes, using gnome-screensaver fix the issue (see > comment #115) can you still reproduce that? > 4. Please consider posting /var/log/auth.log (at least part of it, > should not contain sensitive information) > 5. Please specify the unity version > *** END IMPORTANT ** > > 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 ha
Re: [Dx-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
Hi Andrea, Thanks for the reply. It wasn't until I posted that I noticed my unity version was still old. Goes to show I shouldn't make assumptions about what gets updated! Cheers, Robin Robin, a fix for this issue is scheduled for next SRU (almost ready!). Resetting unity from tt1 should be just fine. Or you can run metacity --replace. 2015-01-08 17:01 GMT+01:00 nybbler : > I've just run into this with Ubuntu 14.04.1, updated today at about > 15:45. I didn't happen immediately after the update, in fact it was fine > for a few hours so I think it's unlikely to be related. > > Some info: > * unity --version: unity 7.2.3 > * uname -r -v -p -i -o: 3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 > 19:35:06 UTC 2014 x86_64 x86_64 GNU/Linux > * Dual-head?: yes, 2 monitors > * modified pam?: no, and not using ldap > * Running 2 VMware Workstation 10 VMs (both Windows 7 x86_64) > > I have too much work (in VMs) going to risk re-setting unity, so I'm > going to have to wait for it to timeout and hope! > > Some redacted output from /var/log/auth.log: > > Jan 8 14:24:12 machinename compiz: PAM unable to dlopen(pam_kwallet.so): > /lib/security/pam_kwallet.so: cannot open shared object file: No such file > or directory > Jan 8 14:24:12 machinename compiz: PAM adding faulty module: > pam_kwallet.so > Jan 8 14:24:12 machinename compiz: pam_succeed_if(lightdm:auth): > requirement "user ingroup nopasswdlogin" not met by user "my-username" > Jan 8 14:39:43 machinename compiz: gkr-pam: unlocked login keyring > Jan 8 14:41:59 machinename compiz: PAM unable to dlopen(pam_kwallet.so): > /lib/security/pam_kwallet.so: cannot open shared object file: No such file > or directory > Jan 8 14:41:59 machinename compiz: PAM adding faulty module: > pam_kwallet.so > Jan 8 14:41:59 machinename compiz: pam_succeed_if(lightdm:auth): > requirement "user ingroup nopasswdlogin" not met by user "my-username" > Jan 8 14:42:57 machinename compiz: gkr-pam: unlocked login keyring > Jan 8 14:43:04 machinename compiz: PAM unable to dlopen(pam_kwallet.so): > /lib/security/pam_kwallet.so: cannot open shared object file: No such file > or directory > Jan 8 14:43:04 machinename compiz: PAM adding faulty module: > pam_kwallet.so > Jan 8 14:43:04 machinename compiz: pam_succeed_if(lightdm:auth): > requirement "user ingroup nopasswdlogin" not met by user "my-username" > Jan 8 14:47:37 machinename compiz: PAM unable to dlopen(pam_kwallet.so): > /lib/security/pam_kwallet.so: cannot open shared object file: No such file > or directory > Jan 8 14:47:37 machinename compiz: PAM adding faulty module: > pam_kwallet.so > Jan 8 14:47:37 machinename compiz: pam_succeed_if(lightdm:auth): > requirement "user ingroup nopasswdlogin" not met by user "my-username" > Jan 8 14:47:41 machinename compiz: gkr-pam: unlocked login keyring > Jan 8 14:48:38 machinename compiz: PAM unable to dlopen(pam_kwallet.so): > /lib/security/pam_kwallet.so: cannot open shared object file: No such file > or directory > Jan 8 14:48:38 machinename compiz: PAM adding faulty module: > pam_kwallet.so > Jan 8 14:48:38 machinename compiz: pam_succeed_if(lightdm:auth): > requirement "user ingroup nopasswdlogin" not met by user "my-username" > Jan 8 14:49:01 machinename compiz: PAM unable to dlopen(pam_kwallet.so): > /lib/security/pam_kwallet.so: cannot open shared object file: No such file > or directory > Jan 8 14:49:01 machinename compiz: PAM adding faulty module: > pam_kwallet.so > Jan 8 14:49:10 machinename compiz: gkr-pam: unlocked login keyring > Jan 8 14:49:10 machinename compiz: pam_succeed_if(lightdm:auth): > requirement "user ingroup nopasswdlogin" not met by user "my-username" > Jan 8 14:54:45 machinename compiz: PAM unable to dlopen(pam_kwallet.so): > /lib/security/pam_kwallet.so: cannot open shared object file: No such file > or directory > Jan 8 14:54:45 machinename compiz: PAM adding faulty module: > pam_kwallet.so > > Robin > > -- > You received this bug notification because you are a bug assignee. > 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: > *** IMPORTANT ** > > *** The fix is not included in TRUSTY. Will be included with next SRU. > *** > > If you can reproduce this bug please be sure to provide the following > info: > 1. Do you use a multi-head setup? If yes, using just one monitor fixes > the issue? > 2. Can you reproduce all the time? > 3. Do you use ldap? If yes, using gnome-screensaver fix the issue (see > comment #115) can you still reproduce that? > 4. Please consider posting /var/log/auth.log (at least part of it, > should not contain sensitive information) > 5. Please specify the unity version > *** END IMPORTANT ** > > Sometimes (but not always) after locking the screen there is the >
[Dx-packages] [Bug 1408759] [NEW] thunderbird icon shows up as question mark in unity
Public bug reported: Using the following versions: ii thunderbird 1:31.3.0+build1-0ubuntu1 amd64Email, RSS and newsgroup client with integrated spam filter ii unity 7.3.1+15.04.20141216-0ubuntu1 amd64Interface designed for efficiency of space and interaction. On Vivid when I launch thunderbird the icon in Unity shows up as a question mark. It would be super-duper if it had the pretty blue bird attacking the envelope icon instead. Let me know what log files / steps I should use to debug this. Thanks ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Also affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1408759 Title: thunderbird icon shows up as question mark in unity Status in thunderbird package in Ubuntu: New Status in unity package in Ubuntu: New Bug description: Using the following versions: ii thunderbird 1:31.3.0+build1-0ubuntu1 amd64Email, RSS and newsgroup client with integrated spam filter ii unity 7.3.1+15.04.20141216-0ubuntu1 amd64Interface designed for efficiency of space and interaction. On Vivid when I launch thunderbird the icon in Unity shows up as a question mark. It would be super-duper if it had the pretty blue bird attacking the envelope icon instead. Let me know what log files / steps I should use to debug this. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1408759/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 866752] Re: Sometimes configure events are missed and windows move slow as a result
** Changed in: unity (Ubuntu) Status: New => Fix Released ** No longer affects: ayatana-design -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/866752 Title: Sometimes configure events are missed and windows move slow as a result Status in Compiz: Fix Released Status in Compiz Core: Fix Released Status in Unity: Fix Released Status in compiz package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in compiz source package in Oneiric: Fix Released Status in unity source package in Oneiric: Won't Fix Bug description: Our current method of tracking configure events is error prone since it's liable to interference from other plugins. A better solution is to use X Request serials like metacity does, since this is not prone to be interfered with. TESTCASE Move windows around, maximize, unmaximize, semi-maximize, use alt-tab Windows shouldn't move slowly To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/866752/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 862339] Re: Grid placement is offset by 1px
** No longer affects: ayatana-design ** Changed in: unity (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/862339 Title: Grid placement is offset by 1px Status in Compiz: Fix Released Status in Compiz Grid Plugin: Fix Released Status in Compiz Main Plugins: Fix Released Status in Unity: Fix Released Status in compiz package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: Window placement is offset by 1px when the grid plugin maximizes a window TESTCASE Semi-maximize two terminals There should be no visible gap between them To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/862339/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 832150] Re: ubuntu desktop unity. Mouse at the left side doesn't reveal launcher
** No longer affects: ayatana-design -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/832150 Title: ubuntu desktop unity. Mouse at the left side doesn't reveal launcher Status in Unity: Fix Released Status in compiz package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in compiz source package in Oneiric: Fix Released Status in unity source package in Oneiric: Won't Fix Bug description: TEST CASE: 1. Start a session (restarting Unity didn't do the trick). 2. Start gnome-terminal or gedit and maximize it (doesn't matter how, also works with other applications). RESULT: * The launcher does not reveal (hide mode 2 - "Dodge Window"). I'm not sure how, but it will eventually start working again after some window dragging/maximizing. Using Nux r483 and Unity r1628. =Original Report= Hello i am testing Ubuntu 11.10 alpha3 and i have a problem with unity. When i open a window, firefox for example, i cannot see the launcher when i move my cursor on the left side as i used to. This problem is not happening when i use unity2d. I can see the launcher by pressing alt+f1. I didn't had a clean install, i mean i upgraded to Ubuntu 11.10. Unity's package version is 4.8.2-0ubuntu4. Thank you in advance Vassilis ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: unity 4.8.2-0ubuntu4 ProcVersionSignature: Ubuntu 3.0.0-9.13-generic 3.0.3 Uname: Linux 3.0.0-9-generic i686 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,resize,gnomecompat,imgpng,vpswitch,commands,grid,obs,compiztoolbox,place,mousepoll,move,regex,wall,session,unitymtgrabhandles,wobbly,animation,workarounds,expo,ezoom,staticswitcher,fade,scale,unityshell] Date: Tue Aug 23 19:14:50 2011 InstallationMedia: Ubuntu 10.04.2 LTS "Lucid Lynx" - Release i386 (20110211.1) SourcePackage: unity UpgradeStatus: Upgraded to oneiric on 2011-08-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/832150/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
