[Dx-packages] [Bug 1301589] Re: indicator-session-service crashed with SIGSEGV in strlen()

[Matt]

I have the same issue, but may have found the source & potential
workaround.

When I use a monolithic site-wide passwd file, indicator-session
crashes.  When I strip it down to just a local account, everything is
fine.  After I stop showing the users for quick user switching, it stops
crashing!

Possible workaround: Run the command below as the affected user.
dconf write /apps/indicator-session/user-show-menu false

I've actually applied this as a manditory setting on a system-wide
level.  Apply the attached tarball, then run 'sudo dconf update'


** Attachment added: "workaround for indicator-session crash"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1301589/+attachment/4480999/+files/indicator-session-fix.tgz

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-session in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1301589

Title:
  indicator-session-service crashed with SIGSEGV in strlen()

Status in indicator-session package in Ubuntu:
  Confirmed

Bug description:
  Happened after initial log on after power up.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: indicator-session 12.10.5+14.04.20140324-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  Date: Wed Apr  2 16:02:54 2014
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-session/indicator-session-service
  InstallationDate: Installed on 2014-03-28 (4 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  ProcCmdline: 
/usr/lib/x86_64-linux-gnu/indicator-session/indicator-session-service
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f729bc0392a :movdqu (%rax),%xmm12
   PC (0x7f729bc0392a) ok
   source "(%rax)" (0x0001) not located in a known VMA region (needed 
readable region)!
   destination "%xmm12" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-session
  StacktraceTop:
   strlen () at ../sysdeps/x86_64/strlen.S:106
   g_strdup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: indicator-session-service crashed with SIGSEGV in strlen()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1301589/+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 381416] Re: notify-osd should have a close button

[matt]

I agree. I know this bug is already closed as Won't Fix because it's working 
as designed, but I think it's a faulty design. Making the notifications 
light-weight by giving the user no way to interact with them, even to dismiss 
them, isn't really light-weight at all. It's more intrusive and difficult to 
work with. I have no way of getting the notifications out of my way once I've 
seen them, so they stay there taking up 
I don't think it helps things at all to simply hold notifications of different 
priorities or lengths for different lengths of time. A notification should stay 
visible until a user has had a chance to see it.  How long it takes the user to 
see it depends on else they're doing, and there's no way for either the system 
nor the application to know what else the user is doing -- are they currently 
reading something and waiting until they get to the end of a paragraph to 
glance at the notification, or did they look at it right away?  You don't know, 
and you can't, so err on the side of longer notifications and give them a 
dismiss button.  

To point: when I first installed Ubuntu 14.04, one of the first pieces
of advice I got was to install a patched version of NotifyOSD that would
let you customize notifications (including dismissing them).  When
that's the advice that people are giving to new users, I think you have
a design problem

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/381416

Title:
  notify-osd should have a close button

Status in notify-osd package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: notify-osd

  As simple as that. The new notification system works fine, but it really bugs 
me that I'm forced to wait for those little messages to fade away by 
themselves. Should I suggest this somewhere else?
  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/381416/+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 1170647] Re: After minimizing an external media, clicking on the Files icon on the Launcher doesn't restore the minimized window, but opens a new one

[Matt Anderson]

I have had this bug for as long as I can remember, first time I bothered
to look it up

-- 
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/1170647

Title:
  After minimizing an external media, clicking on the Files icon on
  the Launcher doesn't restore the minimized window, but opens a new one

Status in One Hundred Papercuts:
  Triaged
Status in Unity:
  Triaged
Status in unity package in Ubuntu:
  Triaged

Bug description:
  ***
   ISSUE
  ***

  HOW TO REPRODUCE

  1. Connect a removable media to the computer.
  2. On the launcher, click on the Files icon.
  3. On the left sidebar, click on the removable media icon or the trash.
  4. Minimize the window.
  5. Click on the Files icon.

  EXPECTED BEHAVIOUR

  - The Files window to be maximized.

  REAL BEHAVIOUR

  - A new window is opened.

  RELEVANT DETAILS

  - One way to navigate between windows at this moment is to use the
  control + tabulation key combination, or to click again on the
  Files icon so windows are exposed.

  Otherwise the minimized window Can be restored by clicking on the
  Volume's launcher icon or scrolling on the Files icon

  **
   SOLUTION
  **

  WORK-AROUND

  - On the launcher, left click on the Files icon and select the
  unlock from Launcher option.

  FIX

  - The launcher icon for Files to be treated the same way as if it
  was unlocked.

  REGRESSION POTENTIAL

  - Clicking on the Files icon won't send the user to its home folder,
  but to the latest opened Files window.

  
   TECHNICAL INFO
  

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6
  Uname: Linux 3.8.0-18-generic i686
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  Date: Fri Apr 19 11:33:13 2013
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b'814x493+136+38'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'182'
  InstallationDate: Installed on 2011-07-23 (635 days ago)
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110426)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to raring on 2013-04-14 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1170647/+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 815996] Re: Desktop occasionally freezes/locks up when switching workspaces

[Matt]

On 14.04 the same: when I switch workspace in windows oftentimes it get stuck 
on workspace mode (where I see the 4 workspaces). The moust pointer becomes a 
hand and there is no way to switch back to normal mode. This seems to happen 
more if there are windows refreshing (e.g. a tail in some terminal window). I 
typically get out of this by kill -HUP compiz from Ctrl+Alt+F1
I could not get out of it disabling snapping windows because it said unity 
plugin requires.
VGA driver is fglrx proprietary

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to compiz-plugins-main in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/815996

Title:
  Desktop occasionally freezes/locks up when switching workspaces

Status in Compiz:
  Confirmed
Status in Compiz Main Plugins:
  Confirmed
Status in Compiz Desktop Wall Plugin:
  Confirmed
Status in compiz package in Ubuntu:
  Confirmed
Status in compiz-plugins-main package in Ubuntu:
  Confirmed

Bug description:
  I'm assuming the issue is related to Compiz, but I'm not 100% sure.
  When I'm switching workspaces, it occasionally locks up (becoming more
  frequent). Most of the time, I'm going from the current one down
  (Ctrl+Alt+Down Arrow), and it freezes mid slide. Typically, I'm able
  to correct things by backing out to a terminal then returning
  (Ctrl+Alt+F1, pause, Alt+F7), but sometimes when I return the dual
  screen setup acts as one large screen (windows are stretched to the
  full width of both screens) and many of the windows collect on the
  first workspace.

  
  Ubuntu 11.04 (Classic)
  All packages up-to-date.

  If there are any logs/etc that would be helpful, let me know.
  --- 
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,grid,imgpng,snap,compiztoolbox,resize,place,regex,move,gnomecompat,animation,vpswitch,mousepoll,workarounds,session,expo,wall,ezoom,fade,switcher,scale]
  DistroCodename: natty
  DistroRelease: Ubuntu 11.04
  DistroVariant: ubuntu
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429)
  InstallationMedia_: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429)
  NonfreeKernelModules: nvidia
  Package: compiz 1:0.9.4+bzr20110606-0ubuntu1~natty2
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7
  ProcVersionSignature_: Ubuntu 2.6.38-10.46-generic 2.6.38.7
  Tags:  natty natty ubuntu
  Uname: Linux 2.6.38-10-generic x86_64
  UnreportableReason: Please work this issue through technical support channels 
first.
  UpgradeStatus: Upgraded to natty on 2011-05-02 (84 days ago)
  UserGroups: adm admin audio cdrom dialout dip fuse lpadmin netdev plugdev 
sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/815996/+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

[Matt Zuba]

@andyrock

mzuba@d000-mzuba1:~$ ls -l /sbin/unix_chkpwd
-rwxr-sr-x 1 root shadow 35536 Jan 31  2014 /sbin/unix_chkpwd


I am using LDAP via PBIS fwiw.

At home, I have a dual monitor setup (as opposed to tri-monitor at work)
and I do not use LDAP and do not have this issue.

-- 
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:
  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/~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

[Matt Zuba]

FWIW - I have Marco's PPA package installed and I continue to see this
issue.  Another issue that seems partly relevant is that my screensaver
never stays on for more than a few minutes before I see the lock screen
again.  I notice that when this happens, this issue is more prevelant.
Here is a snippet of my auth.log (note that I, nor anyone else is at the
office during this time frame) and 6:25 is when I first sat down at my
desk to log in.

212 Dec  2 04:40:14 d000-mzuba1 compiz: PAM adding faulty module: 
pam_kwallet.so
213 Dec  2 04:52:04 d000-mzuba1 compiz: PAM unable to 
dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object 
file: No such file or directory
214 Dec  2 04:52:04 d000-mzuba1 compiz: PAM adding faulty module: 
pam_kwallet.so
215 Dec  2 05:03:52 d000-mzuba1 compiz: PAM unable to 
dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object 
file: No such file or directory
216 Dec  2 05:03:52 d000-mzuba1 compiz: PAM adding faulty module: 
pam_kwallet.so
217 Dec  2 05:15:42 d000-mzuba1 compiz: PAM unable to 
dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object 
file: No such file or directory
218 Dec  2 05:15:42 d000-mzuba1 compiz: PAM adding faulty module: 
pam_kwallet.so
219 Dec  2 05:27:30 d000-mzuba1 compiz: PAM unable to 
dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object 
file: No such file or directory
220 Dec  2 05:27:30 d000-mzuba1 compiz: PAM adding faulty module: 
pam_kwallet.so
221 Dec  2 05:39:18 d000-mzuba1 compiz: PAM unable to 
dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object 
file: No such file or directory
222 Dec  2 05:39:18 d000-mzuba1 compiz: PAM adding faulty module: 
pam_kwallet.so
223 Dec  2 05:51:06 d000-mzuba1 compiz: PAM unable to 
dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object 
file: No such file or directory
224 Dec  2 05:51:06 d000-mzuba1 compiz: PAM adding faulty module: 
pam_kwallet.so
225 Dec  2 06:02:55 d000-mzuba1 compiz: PAM unable to 
dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object 
file: No such file or directory
226 Dec  2 06:02:55 d000-mzuba1 compiz: PAM adding faulty module: 
pam_kwallet.so
227 Dec  2 06:14:43 d000-mzuba1 compiz: PAM unable to 
dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object 
file: No such file or directory
228 Dec  2 06:14:43 d000-mzuba1 compiz: PAM adding faulty module: 
pam_kwallet.so
229 Dec  2 06:25:41 d000-mzuba1 unix_chkpwd[14694]: check pass; user unknown
230 Dec  2 06:25:41 d000-mzuba1 unix_chkpwd[14694]: password check failed 
for user (mzuba)
231 Dec  2 06:25:41 d000-mzuba1 compiz: pam_unix(lightdm:auth): 
authentication failure; logname= uid=1002442509 euid=1002442509 tty= ruser= 
rhost=  user=mzuba
232 Dec  2 06:25:41 d000-mzuba1 compiz: gkr-pam: unlocked login keyring
233 Dec  2 06:25:41 d000-mzuba1 unix_chkpwd[14703]: could not obtain user 
info (mzuba)
234 Dec  2 06:25:48 d000-mzuba1 compiz: PAM unable to 
dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object 
file: No such file or directory
235 Dec  2 06:25:48 d000-mzuba1 compiz: PAM adding faulty module: 
pam_kwallet.so
236 Dec  2 06:25:48 d000-mzuba1 compiz: pam_succeed_if(lightdm:auth): 
requirement user ingroup nopasswdlogin not met by user mzuba
237 Dec  2 06:25:52 d000-mzuba1 unix_chkpwd[15012]: check pass; user unknown
238 Dec  2 06:25:52 d000-mzuba1 unix_chkpwd[15012]: password check failed 
for user (mzuba)
239 Dec  2 06:25:52 d000-mzuba1 compiz: pam_unix(lightdm:auth): 
authentication failure; logname= uid=1002442509 euid=1002442509 tty= ruser= 
rhost=  user=mzuba
240 Dec  2 06:25:52 d000-mzuba1 compiz: gkr-pam: unlocked login keyring
241 Dec  2 06:25:52 d000-mzuba1 unix_chkpwd[15015]: could not obtain user 
info (mzuba)

-- 
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:
  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
  

[Dx-packages] [Bug 1333107] Re: After Lockscreen Textbox Behave Strangely

[Matt Franklin]

I have exactly the same error.  As stated above, keyboard letter P
upper or lower case can be typed without causing the attempted new
folder to disappear. The workaround I have been using for this is first
creating the folder in Nautilus, where there is no issue, and then
saving files into it from within other programs.

-- 
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/1333107

Title:
  After Lockscreen Textbox Behave Strangely

Status in Unity:
  New
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  1) System Description
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  unity:
    Installed: 7.2.1+14.04.20140513-0ubuntu2
    Candidate: 7.2.1+14.04.20140513-0ubuntu2
    Version table:
   *** 7.2.1+14.04.20140513-0ubuntu2 0
  500 http://id.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   7.2.0+14.04.20140423-0ubuntu1.2 0
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
   7.2.0+14.04.20140416-0ubuntu1 0
  500 http://id.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  2) Scenario (two case)
  - I lock ubuntu by closing laptop's lid or lock manually
  - I unlock it by giving password and it is unlocked
  - I try to open 'Saving or Open File Dialog' of an App, like firefox or geany

  (Create Folder)
  - I make a new folder by clicking on 'Create Folder' button
  - There appear new folder that ready to be renamed, has a 'Type name of new 
folder' text
  [ a ] I type in the name by pressing letter button on keyboard

  (Type Ahead)
  - I click on dialog's folder view (the big one) empty area to give it focus
  - I type directly one letter from keyboard so type-ahead textbox appeared
  [ b ] I type another letter to the type-ahead

  3) What you expected to happen
  [ a ] I can create a folder with a specified name
  [ b ] I can type more than one letter on type-ahead

  4) What happened instead
  [ a ] Once I press keyboard key, the new folder gone like when I press 
'Escape' key
  [ b ] Successfully type one letter, but when I type another letter, the type 
ahead gone

  5) Notes
  - Not only letter key, modifier key like 'Alt' and 'Shift' also affecting 
this (case [ a ] especially)
  - Onboard (On-screen keyboard) also affecting this
  - Textbox on facebook search behave like type-ahead
  - Textbox on firefox normal but cannot select suggested site by pressing 
'down arrow' button

  The bug happened after lock screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.1+14.04.20140513-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Mon Jun 23 13:10:06 2014
  InstallationDate: Installed on 2014-04-21 (62 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1333107/+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

[Matt Zuba]

Let me add a small twist to this...

I have a triple-screen setup on an ATI card.  I have the same issue
above, but I also have another...

Sometimes when I come to my computer in the morning for work, one screen
will not have the input field, but two others will.  If I mis-type my
password in one of the working screens, the input field then disappears.
If I type it incorrectly in the other window, the input field disappears
on that one as well.  Then I'm back to the issue in this bug.  But if I
do type it correctly on either of the working monitors, then sometimes
I'll get another lock screen, and sometimes I'll get my desktop.

Additionally, if I do end up in a spot where I have visible fields, if I
restart lightdm and then login, then I get the lock screen again after
logging in and have to enter my password again.

The Unity Lockscreen has been a huge nightmare for me...

-- 
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:
  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/~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 1308317] Re: applications in full-screen do not align properly after minimization

[Matt]

** Description changed:

  This is a problem with mouse-clicking sections of the firefox window
  that are unresponsive.
  
  I'll try to describe the problem. Firefox is open and set to
  fullscreen/maximize. You press the minimize button to send Firefox to
  the launcher. After opening firefox, by clicking on the launcher icon,
  firefox returns to fullscreen/maximize and appears normal. However, the
  tabs at the top are unclickable. The mouse button is an I-beam - or
  text-editing cursor - instead of a pointer when hovering over the tabs.
  Clicking changes the position of the I-beam in the text url below. This
  happens without regard to which programs are open, or whether or not
  anything else is open. This happens 100% of the time.
  
  It seems as though the firefox window is adjusting to maximize and leave
  room for the menubar at the top, but the GUI does not anticipate the
  menu bar. There is about a 10 pixel discrepancy between where the mouse
  points, and where it registers.
  
  This also occurs with browser, Chromium.
+ 
+ This problem does not occur when switching between windows with
+ maximized browsers, only when a browser opened from launcher after being
+ minimized.
  
  This video should help shed light on the problem:
  http://tinypic.com/r/2jfcepi/8
  
  I'm running Ubuntu 14.04 beta.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:
  
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  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: Tue Apr 15 22:01:26 2014
  DistUpgraded: 2014-04-04 13:01:59,967 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:100d]
  InstallationDate: Installed on 2014-03-02 (45 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: ASUSTeK COMPUTER INC. K46CA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed 
root=UUID=b5739d9f-9c22-4526-8ff5-d851de39247a ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to trusty on 2014-04-04 (11 days ago)
  dmi.bios.date: 10/16/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K46CA.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K46CA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK46CA.309:bd10/16/2012:svnASUSTeKCOMPUTERINC.:pnK46CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK46CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: K46CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Apr 15 11:10:07 2014
  xserver.configfile: default
  xserver.errors:
  
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12348
   vendor AUO
  xserver.version: 2:1.15.1-0ubuntu1

-- 
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/1308317

Title:
  applications in full-screen do not align properly after minimization

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  This is a problem with mouse-clicking sections of the firefox window
  that are unresponsive.

  I'll try to describe the problem. Firefox is open and set to
  fullscreen/maximize. You press the minimize button to send Firefox to
  the launcher. After opening firefox, by clicking on the launcher icon,
  firefox returns to 

[Dx-packages] [Bug 1308317] Re: applications in full-screen do not align properly after minimization

[Matt]

** Description changed:

  This is a problem with mouse-clicking sections of the firefox window
  that are unresponsive.
  
  I'll try to describe the problem. Firefox is open and set to
  fullscreen/maximize. You press the minimize button to send Firefox to
  the launcher. After opening firefox, by clicking on the launcher icon,
  firefox returns to fullscreen/maximize and appears normal. However, the
  tabs at the top are unclickable. The mouse button is an I-beam - or
  text-editing cursor - instead of a pointer when hovering over the tabs.
  Clicking changes the position of the I-beam in the text url below. This
  happens without regard to which programs are open, or whether or not
- anything else is open. There seems to be a 50/50 chance of clicking
- firefox from the launch pad, and having this happen.
+ anything else is open. This happens 100% of the time.
  
  It seems as though the firefox window is adjusting to maximize and leave
  room for the menubar at the top, but the GUI does not anticipate the
  menu bar. There is about a 10 pixel discrepancy between where the mouse
  points, and where it registers.
  
- This happens to ALL applications set to full-screen mode after
- minimization.
+ This also occurs with browser, Chromium.
  
  This video should help shed light on the problem:
  http://tinypic.com/r/2jfcepi/8
  
  I'm running Ubuntu 14.04 beta.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:
-  
+ 
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  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: Tue Apr 15 22:01:26 2014
  DistUpgraded: 2014-04-04 13:01:59,967 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
-Subsystem: ASUSTeK Computer Inc. Device [1043:100d]
+  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
+    Subsystem: ASUSTeK Computer Inc. Device [1043:100d]
  InstallationDate: Installed on 2014-03-02 (45 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: ASUSTeK COMPUTER INC. K46CA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed 
root=UUID=b5739d9f-9c22-4526-8ff5-d851de39247a ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to trusty on 2014-04-04 (11 days ago)
  dmi.bios.date: 10/16/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K46CA.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K46CA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK46CA.309:bd10/16/2012:svnASUSTeKCOMPUTERINC.:pnK46CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK46CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: K46CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Apr 15 11:10:07 2014
  xserver.configfile: default
  xserver.errors:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
-  product id   12348 
-  vendor AUO
+  product id   12348
+  vendor AUO
  xserver.version: 2:1.15.1-0ubuntu1

-- 
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/1308317

Title:
  applications in full-screen do not align properly after minimization

Status in “unity” package in Ubuntu:
  New

Bug description:
  This is 

[Dx-packages] [Bug 1125442] Re: Always Visible and On Top Windows Steal Focus on Workspace Switch

[Matt Goodall]

I believe another example of this is when using the Chromium Hangouts
extension[1]. The extension uses Chromium Panels - small windows
anchored to the edge of the screen that appear on all workspaces - and
those panels have the same effect. See  Panels window causes Workspace
switching focus to break[2] for more.

[1] 
https://chrome.google.com/webstore/detail/hangouts/nckgahadagoaajjgafhacjanaoiihapd.
[2] https://code.google.com/p/chromium/issues/detail?id=295856

** Bug watch added: code.google.com/p/chromium/issues #295856
   http://code.google.com/p/chromium/issues/detail?id=295856

-- 
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/1125442

Title:
  Always Visible and On Top Windows Steal Focus on Workspace Switch

Status in Ayatana Design:
  New
Status in “unity” package in Ubuntu:
  Confirmed
Status in “unity” source package in Precise:
  Confirmed
Status in “unity” source package in Quantal:
  Confirmed
Status in “unity” source package in Raring:
  Confirmed

Bug description:
  1. Open any application (e.g. TextEditor)
  2. Right click the title bar
   2a. Select Always on Visible Workspace
  3. Right click the title bar
   3a. Select Always on Top
  4. Open a different application (e.g. Terminal)
  5. Ensure that window has focus
  6. Switch workspaces (Notice: the first application now has focus)
  7. Return to first workspace (Notice: the second application does not regain 
focus)

  Expected:

  The initial application should not have ever regained focus, and
  certainly the second application should have it when returning to that
  workspace.

  antarus@mach ~ $ lsb_release -rd
  Description:Ubuntu 12.04.1 LTS
  Release:12.04

  antarus@mach ~ $ apt-cache policy unity
  unity:
Installed: 5.18.0-0ubuntu2
Candidate: 5.18.0-0ubuntu2
Version table:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/1125442/+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