[Dx-packages] [Bug 1319872] Re: Dash doesn't work when scim is selected as the Keyboard Input Method System

[Bug Watch Updater]

** Changed in: scim (Debian)
   Status: Unknown => 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/1319872

Title:
  Dash doesn't work when scim is selected as the Keyboard Input Method
  System

Status in “scim” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  New
Status in “scim” package in Debian:
  New

Bug description:
  This issue regards the packages for SCIM Input Method and DASH.*

  In Ubuntu 14.04, the Dash doesn't work when scim is selected as the
  Keyboard Input Method. "Doesn't work" means the Dash opens, but one
  cannot type in the search screen. It accepts one letter and then
  freezes. When one goes into language support and changes the Keyboard
  IM to another option such as ibus or Fcitx, the Dash problem resolves.
  I started a thread on the Ubuntu forums
   about this matter
  some weeks ago, and someone else on the thread (tuannb86) reported the
  same problem. So there are definitely multiple users facing this
  issue.

  *I could not follow the standard procedure to initiate the bug in
  Ubuntu, because that requires hitting Alt-F2 to open a run-command
  screening and typing "ubuntu-bug 15370". (15370 is the number of the
  running process for scim in system monitor). By that way the bug is
  initiated and all the relevant info comes directly into the bug. But
  when scim is the selected IM, due to the bug I can't type in the dash
  screen. That includes the run-command screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubuntu-release-upgrader-core 1:0.220.2
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Thu May 15 10:36:28 2014
  InstallationDate: Installed on 2014-04-24 (20 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/scim/+bug/1319872/+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 1307619] Re: Qt Creator Menu bar is missing at Gnome3 or KDE Desktop

[Scott Kostyshak]

** Also affects: lyx
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to appmenu-qt5 in Ubuntu.
https://bugs.launchpad.net/bugs/1307619

Title:
  Qt Creator Menu bar is missing at Gnome3 or KDE Desktop

Status in LyX - The Document Processor:
  New
Status in “appmenu-qt5” package in Ubuntu:
  Confirmed

Bug description:
  1. Open "Qt Creator" Version 3.0.1 at the Gnome3 Desktop
  2. Menu bar is missing.

   workaround --
  After Deinstall appmenu-qt5 is the Menu bar working again.
  Open Terminal:
  sudo apt-get remove appmenu-qt5

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: appmenu-qt5 0.3.0+14.04.20140314-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic i686
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Mon Apr 14 18:52:18 2014
  InstallationDate: Installed on 2014-02-14 (58 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140214)
  SourcePackage: appmenu-qt5
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/lyx/+bug/1307619/+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 1307619] Re: Qt Creator Menu bar is missing at Gnome3 or KDE Desktop

[Scott Kostyshak]

I see this in Qt Creator as well as in a self-compiled LyX on Ubuntu 14.04. It 
might be useful to note that in the LyX case, one can get the menu bar back by 
executing the following command (in LyX's internal language)
ui-toggle menubar
Removing appmenu-qt5 solved the problem in both cases for me.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to appmenu-qt5 in Ubuntu.
https://bugs.launchpad.net/bugs/1307619

Title:
  Qt Creator Menu bar is missing at Gnome3 or KDE Desktop

Status in LyX - The Document Processor:
  New
Status in “appmenu-qt5” package in Ubuntu:
  Confirmed

Bug description:
  1. Open "Qt Creator" Version 3.0.1 at the Gnome3 Desktop
  2. Menu bar is missing.

   workaround --
  After Deinstall appmenu-qt5 is the Menu bar working again.
  Open Terminal:
  sudo apt-get remove appmenu-qt5

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: appmenu-qt5 0.3.0+14.04.20140314-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic i686
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Mon Apr 14 18:52:18 2014
  InstallationDate: Installed on 2014-02-14 (58 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140214)
  SourcePackage: appmenu-qt5
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/lyx/+bug/1307619/+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 1318103] Re: Error importing Python module pocketsphinx

[Alex Rea]

I have the same bug on the same setup. Trying to import it a second time
works for me weirdly, though, so I'm just using try/except to work
around this for the moment.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to pocketsphinx in Ubuntu.
https://bugs.launchpad.net/bugs/1318103

Title:
  Error importing Python module pocketsphinx

Status in “pocketsphinx” package in Ubuntu:
  Confirmed

Bug description:
  Pretty much stock standard Ubuntu 14.04 AMD64 with no manually
  compiled software and no manually installed python modules.

  $ python
  Python 2.7.6 (default, Mar 22 2014, 22:59:56) 
  [GCC 4.8.2] on linux2
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import pocketsphinx
  Traceback (most recent call last):
File "", line 1, in 
File "sphinxbase.pxd", line 150, in init pocketsphinx (pocketsphinx.c:7935)
  ValueError: PyCapsule_GetPointer called with invalid PyCapsule object
  >>>

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pocketsphinx/+bug/1318103/+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 1320346] [NEW] unity-tweak-tool does not start

[Erlenmayr]

Public bug reported:

unity-tweak-tools does not start, if overlay-scrollbar is not installed.

How to eproduce bug:
1. uninstall overlay-scrollbar, overlay-scrollbar-gtk2 and overlay-scrollbar-gtk
2. install unity-tweak-tool
3. try to start unity-tweak-tool

Solution:
a) fix unity-tweak-tool
or
b) make overlay-scrollbar a dependency of unity-tweak-tool packages

** Affects: unity-tweak-tool (Ubuntu)
 Importance: Undecided
 Status: New

** Package changed: unity (Ubuntu) => unity-tweak-tool (Ubuntu)

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

Title:
  unity-tweak-tool does not start

Status in “unity-tweak-tool” package in Ubuntu:
  New

Bug description:
  unity-tweak-tools does not start, if overlay-scrollbar is not
  installed.

  How to eproduce bug:
  1. uninstall overlay-scrollbar, overlay-scrollbar-gtk2 and 
overlay-scrollbar-gtk
  2. install unity-tweak-tool
  3. try to start unity-tweak-tool

  Solution:
  a) fix unity-tweak-tool
  or
  b) make overlay-scrollbar a dependency of unity-tweak-tool packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-tweak-tool/+bug/1320346/+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 1241101] Re: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

[José Tomás Atria]

I've been using the Raleigh override, and I have experienced no crashes.

I also tried David's suggestions, though the libgtk-3-0 version in the
Trusty repos seems to be the same as the one in the gnome3 ppa (Package
libgtk3 is already the newest version etc.). I compiled oxygen-gtk
locally, but the problem persists.

All of the above on 14.04.

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

Title:
  Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

Status in Eclipse:
  Confirmed
Status in “gtk+2.0” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Invalid
Status in “gtk+2.0” package in Suse:
  New

Bug description:
  Running smartgit 4.6.4 on 13.10 64 bits. After registering the
  product, smartgit crash when trying to open a new repository. Java
  error log :

  # A fatal error has been detected by the Java Runtime Environment:
  #
  #  SIGSEGV (0xb) at pc=0x7fa59061f9c0, pid=12494, tid=140349308167936
  #
  # JRE version: 7.0_25-b30
  # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 
compressed oops)
  # Problematic frame:
  # C  [libglib-2.0.so.0+0x389c0]  g_str_hash+0x0

  I tried different version of Java (Oracle v7 and v6 jre) with same
  result. Also, Eclipse display blank menus so there's a general java
  problem with displays.

To manage notifications about this bug go to:
https://bugs.launchpad.net/eclipse/+bug/1241101/+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 1241101] Re: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

[José Tomás Atria]

This also occurs here, with Ubuntu 14.04 x64.

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

Title:
  Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

Status in Eclipse:
  Confirmed
Status in “gtk+2.0” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Invalid
Status in “gtk+2.0” package in Suse:
  New

Bug description:
  Running smartgit 4.6.4 on 13.10 64 bits. After registering the
  product, smartgit crash when trying to open a new repository. Java
  error log :

  # A fatal error has been detected by the Java Runtime Environment:
  #
  #  SIGSEGV (0xb) at pc=0x7fa59061f9c0, pid=12494, tid=140349308167936
  #
  # JRE version: 7.0_25-b30
  # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 
compressed oops)
  # Problematic frame:
  # C  [libglib-2.0.so.0+0x389c0]  g_str_hash+0x0

  I tried different version of Java (Oracle v7 and v6 jre) with same
  result. Also, Eclipse display blank menus so there's a general java
  problem with displays.

To manage notifications about this bug go to:
https://bugs.launchpad.net/eclipse/+bug/1241101/+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 1319872] Re: Dash doesn't work when scim is selected as the Keyboard Input Method System

[Gunnar Hjalmarsson]

** Bug watch added: Debian Bug tracker #748381
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748381

** Also affects: scim (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748381
   Importance: Unknown
   Status: Unknown

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

Title:
  Dash doesn't work when scim is selected as the Keyboard Input Method
  System

Status in “scim” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  New
Status in “scim” package in Debian:
  Unknown

Bug description:
  This issue regards the packages for SCIM Input Method and DASH.*

  In Ubuntu 14.04, the Dash doesn't work when scim is selected as the
  Keyboard Input Method. "Doesn't work" means the Dash opens, but one
  cannot type in the search screen. It accepts one letter and then
  freezes. When one goes into language support and changes the Keyboard
  IM to another option such as ibus or Fcitx, the Dash problem resolves.
  I started a thread on the Ubuntu forums
   about this matter
  some weeks ago, and someone else on the thread (tuannb86) reported the
  same problem. So there are definitely multiple users facing this
  issue.

  *I could not follow the standard procedure to initiate the bug in
  Ubuntu, because that requires hitting Alt-F2 to open a run-command
  screening and typing "ubuntu-bug 15370". (15370 is the number of the
  running process for scim in system monitor). By that way the bug is
  initiated and all the relevant info comes directly into the bug. But
  when scim is the selected IM, due to the bug I can't type in the dash
  screen. That includes the run-command screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubuntu-release-upgrader-core 1:0.220.2
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Thu May 15 10:36:28 2014
  InstallationDate: Installed on 2014-04-24 (20 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/scim/+bug/1319872/+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 1316320] Re: Screen Lock does not prompt for password

[Charlie Ott]

Hmm... I see, the Unity Panel allows the User to enable the gnome screen
lock, which is not using SSSD (even though I have it installed) so it
just hangs in a loop when trying to unlock the screen.

Also the keyring seems to have the same problem, generating hundreds of
thousands of keyring.temp files in /home/user/.local/share/keyring

Unfortunately Google chrome prompts users to enable the keyring every
time :(


Had to use the find . -type file -delete command to remove them all.

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

Title:
  Screen Lock does not prompt for password

Status in Linux Terminal Server Project:
  Triaged
Status in Unity:
  Invalid
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  I am using LTSP fat clients, created with:

  $ sudo ltsp-build-image --arch amd64 --fat-client-desktop ubuntu-
  desktop

  LTSP server has sssd authentication utilizing pam and ldap.  Users can
  log in without issue and the home folder is available.  Everything
  works as expected except for screen locking.

  When locking the screen, the displays first go blank and the monitor
  goes to sleep.

  Then if i move the mouse or press a keystroke, They go black but the
  mouse is visible.

  Once I move the mouse or strike a key the second time, everything
  comes back up without password prompt.  However, password prompt is
  enabled in "Brightness & Lock"

  The client hardware is an Intel NUC D34010WYK

  Also maybe related, there seems to be no system tray.  No clock or
  username/logout buttons.  I am using Ctrl + Alt + L to lock the
  screen. (See attached screenshot)

  This is a security vulnerability and I can not make the new 14.04
  image available as fat clients, since they users cannot lock their
  workstation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ltsp/+bug/1316320/+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 1311403] Re: Can't type password after resume.

[Andrea Azzarone]

Do you remember which program had the focus when you closed the laptop?
VirtualBox, Remina, or something like that?

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

Title:
  Can't type password after resume.

Status in Unity:
  Incomplete
Status in “unity” package in Ubuntu:
  Incomplete

Bug description:
  I couldn't type password after resume - no characters displayed this
  time.

  I had to Ctrl+alt+f2 and service lightdm restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  Date: Tue Apr 22 17:37:49 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-11-23 (150 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to trusty on 2014-04-19 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1311403/+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 1308911] Re: Clipboard contents are accessible within lockscreen

[Andrea Azzarone]

** Tags removed: clipboard unity-greeter

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

Title:
  Clipboard contents are accessible within lockscreen

Status in Unity:
  In Progress
Status in “unity” package in Ubuntu:
  In Progress

Bug description:
  - Copy e.g. my password to the clipboard (highlight and/or Ctrl+C)
  - Lock the screen (Ctrl+Alt+L)
  - Paste content from clipboard using middle mouse button or Ctrl+V into input 
field
  - Login possible (if copied text was the password)

  Expected behaviour:
  No content from clipboard available at all in lockscreen

  lsb_release -rd:
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1308911/+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 1295413] Re: new unity lock screen doesn't appear after resume

[Andrea Azzarone]

Marking as invalid per comment #10.

** Changed in: unity
   Status: Incomplete => Opinion

** Changed in: unity
   Status: Opinion => Invalid

** Changed in: unity (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  new unity lock screen doesn't appear after resume

Status in Unity:
  Invalid
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  New lock screen is awesome.  Unfortunately, for me, whenever I resume,
  I get a blank screen.  I can switch VTs but switching to a text VT and
  back to X doesn't help.  If I unplug and/or re-plug my external
  display, I'll sometimes get a black screen with a mouse, sometimes a
  lock screen that doesn't appear to be accepting keyboard input.

  This has happened twice now, running current trusty and I've ended up
  rebooting each time.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140318-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  ApportVersion: 2.13.3-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]
  CurrentDesktop: Unity
  Date: Thu Mar 20 23:26:52 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-10-20 (882 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-02-19 (29 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1295413/+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 1059374] Re: Using Adwaita, many widgets are drawn with a solid black background

[pabloferz]

I am also seeing this bug in Ubuntu 14.04.

** Tags removed: quantal
** Tags added: trusty

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

Title:
  Using Adwaita, many widgets are drawn with a solid black background

Status in GTK+ GUI Toolkit:
  Fix Released
Status in Overlay Scrollbar:
  Confirmed
Status in “gnome-themes-standard” package in Ubuntu:
  Confirmed
Status in “gtk+3.0” package in Ubuntu:
  Fix Released
Status in “overlay-scrollbar” package in Ubuntu:
  Triaged

Bug description:
  When I use the Adwaita theme, some widgets end up being drawn with a
  black background after particular interactions. Here are two examples:

  If I open gedit, by default I see a new black document. The notebook
  widget is visible, and rendered correctly. As soon as I open another
  document (no matter if I close the existing one first), the entire
  widget starts being drawn with a black background.

  If I open System Settings, then click the (Ubuntu) Online Accounts
  panel, the box with the "Remove account" button has a solid black
  background. If, instead, I open Online Accounts directly from its
  launcher (run gnome-control-center credentials), everything is
  rendered correctly: there are no solid black backgrounds until I click
  "All Settings" and select the Online Accounts panel again.

  This has been happening consistently on two very different machines,
  both updated to Quantal from 12.04 using the upgrade tool.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: libgtk-3-0 3.6.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic x86_64
  ApportVersion: 2.5.3-0ubuntu1
  Architecture: amd64
  Date: Sun Sep 30 21:18:23 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110906)
  SourcePackage: gtk+3.0
  UpgradeStatus: Upgraded to quantal on 2012-08-26 (35 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1059374/+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 1319983] Re: notify-osd loses pending bubble if append occurs when bubble is not yet visible

[Didier Roche]

** Also affects: notify-osd (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

Title:
  notify-osd loses pending bubble if append occurs when bubble is not
  yet visible

Status in “notify-osd” package in Ubuntu:
  In Progress
Status in “notify-osd” source package in Trusty:
  New

Bug description:
  [Impact]
  When a notification specifiying x-canonical-append:true is recieved and 
merges with a bubble the bubble will be lost if the bubble is not yet visible.  
We will also update times incorrectly on any synchronous bubble.

  [Test Case]
  Running the attached scripts (play.py and play2.py) show the issue: bubbles 
after the first one aren't shown, because they specify x-canonical-append. The 
attached branch fixes that.

  [Regression Potential]
  The patch only touches code that is concerned with updating an existing 
notification. This is currently broken anyway.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1319983/+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 1319983] Re: notify-osd loses pending bubble if append occurs when bubble is not yet visible

[Lars Uebernickel]

** Description changed:

- When a notification specifiying x-canonical-append:true is recieved and
- merges with a bubble the bubble will be lost if the bubble is not yet
- visible.  We will also update times incorrectly on any synchronous
- bubble.
+ [Impact]
+ When a notification specifiying x-canonical-append:true is recieved and 
merges with a bubble the bubble will be lost if the bubble is not yet visible.  
We will also update times incorrectly on any synchronous bubble.
+ 
+ [Test Case]
+ Running the attached scripts (play.py and play2.py) show the issue: bubbles 
after the first one aren't shown, because they specify x-canonical-append. The 
attached branch fixes that.
+ 
+ [Regression Potential]
+ The patch only touches code that is concerned with updating an existing 
notification. This is currently broken anyway.

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

Title:
  notify-osd loses pending bubble if append occurs when bubble is not
  yet visible

Status in “notify-osd” package in Ubuntu:
  In Progress
Status in “notify-osd” source package in Trusty:
  New

Bug description:
  [Impact]
  When a notification specifiying x-canonical-append:true is recieved and 
merges with a bubble the bubble will be lost if the bubble is not yet visible.  
We will also update times incorrectly on any synchronous bubble.

  [Test Case]
  Running the attached scripts (play.py and play2.py) show the issue: bubbles 
after the first one aren't shown, because they specify x-canonical-append. The 
attached branch fixes that.

  [Regression Potential]
  The patch only touches code that is concerned with updating an existing 
notification. This is currently broken anyway.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1319983/+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 1307619] Re: Qt Creator Menu bar is missing at Gnome3 or KDE Desktop

[Elisa de Castro Guerra]

I confirm this  and removing appmenu-qt5 solve this bug.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to appmenu-qt5 in Ubuntu.
https://bugs.launchpad.net/bugs/1307619

Title:
  Qt Creator Menu bar is missing at Gnome3 or KDE Desktop

Status in “appmenu-qt5” package in Ubuntu:
  Confirmed

Bug description:
  1. Open "Qt Creator" Version 3.0.1 at the Gnome3 Desktop
  2. Menu bar is missing.

   workaround --
  After Deinstall appmenu-qt5 is the Menu bar working again.
  Open Terminal:
  sudo apt-get remove appmenu-qt5

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: appmenu-qt5 0.3.0+14.04.20140314-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic i686
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Mon Apr 14 18:52:18 2014
  InstallationDate: Installed on 2014-02-14 (58 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140214)
  SourcePackage: appmenu-qt5
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1307619/+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 1319983] Re: notify-osd loses pending bubble if append occurs when bubble is not yet visible

[Lars Uebernickel]

** Changed in: notify-osd (Ubuntu)
   Status: New => In Progress

** Changed in: notify-osd (Ubuntu)
 Assignee: (unassigned) => Lars Uebernickel (larsu)

** Branch linked: lp:~larsu/notify-osd/lp1319983

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

Title:
  notify-osd loses pending bubble if append occurs when bubble is not
  yet visible

Status in “notify-osd” package in Ubuntu:
  In Progress
Status in “notify-osd” source package in Trusty:
  New

Bug description:
  [Impact]
  When a notification specifiying x-canonical-append:true is recieved and 
merges with a bubble the bubble will be lost if the bubble is not yet visible.  
We will also update times incorrectly on any synchronous bubble.

  [Test Case]
  Running the attached scripts (play.py and play2.py) show the issue: bubbles 
after the first one aren't shown, because they specify x-canonical-append. The 
attached branch fixes that.

  [Regression Potential]
  The patch only touches code that is concerned with updating an existing 
notification. This is currently broken anyway.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1319983/+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 1308911] Re: Clipboard contents are accessible within lockscreen

[Launchpad Bug Tracker]

** Branch linked: lp:~andyrock/unity/fix-lp-1308911

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

Title:
  Clipboard contents are accessible within lockscreen

Status in Unity:
  In Progress
Status in “unity” package in Ubuntu:
  In Progress

Bug description:
  - Copy e.g. my password to the clipboard (highlight and/or Ctrl+C)
  - Lock the screen (Ctrl+Alt+L)
  - Paste content from clipboard using middle mouse button or Ctrl+V into input 
field
  - Login possible (if copied text was the password)

  Expected behaviour:
  No content from clipboard available at all in lockscreen

  lsb_release -rd:
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1308911/+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 1320286] [NEW] On LTSP thick client gnome-settings-daemon gets loaded before unity-settings-daemon

[Charlie Ott]

Public bug reported:

On amd64 ltsp fat client,

gnome-settings-daemon gets loaded before unity-settings-daemon, and thus
unity-panel-service doesn't start at all.

manually running /usr/lib/unity/unity-panel-service after system is a
work around the problem.

** 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/1320286

Title:
  On LTSP thick client gnome-settings-daemon gets loaded before unity-
  settings-daemon

Status in “unity” package in Ubuntu:
  New

Bug description:
  On amd64 ltsp fat client,

  gnome-settings-daemon gets loaded before unity-settings-daemon, and
  thus unity-panel-service doesn't start at all.

  manually running /usr/lib/unity/unity-panel-service after system is a
  work around the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1320286/+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 1315717] Re: Global MenuBar hidden in Qt applications after any dialog opens

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: appmenu-qt5 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Global MenuBar hidden in Qt applications after any dialog opens

Status in “appmenu-qt” package in Ubuntu:
  Confirmed
Status in “appmenu-qt5” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  This appears to happen only if the main application window is NOT
  fullscreen.

  Confirmed in the following Qt applications:

  Wallch, VLC and Qt Creator

  Steps to reproduce:

  1. Open the application
  2. Exit fullscreen (unmaximize) if maximized
  3. Open any application dialog through the menu or through a shortcut (e.g. 
Ctrl+P for Preferences dialog)
  4. Close the dialog with any way.
  5. Hover your mouse where the menu should be. The menu is now gone

  Video demonstrating the problem:
  https://www.youtube.com/watch?v=QRpl1rM9gxM

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-services 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sat May  3 20:30:11 2014
  ExecutablePath: /usr/lib/unity/unity-panel-service
  InstallationDate: Installed on 2014-04-18 (15 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/ubuntu/+source/appmenu-qt/+bug/1315717/+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 1315717] Re: Global MenuBar hidden in Qt applications after any dialog opens

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: appmenu-qt (Ubuntu)
   Status: New => Confirmed

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

Title:
  Global MenuBar hidden in Qt applications after any dialog opens

Status in “appmenu-qt” package in Ubuntu:
  Confirmed
Status in “appmenu-qt5” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  This appears to happen only if the main application window is NOT
  fullscreen.

  Confirmed in the following Qt applications:

  Wallch, VLC and Qt Creator

  Steps to reproduce:

  1. Open the application
  2. Exit fullscreen (unmaximize) if maximized
  3. Open any application dialog through the menu or through a shortcut (e.g. 
Ctrl+P for Preferences dialog)
  4. Close the dialog with any way.
  5. Hover your mouse where the menu should be. The menu is now gone

  Video demonstrating the problem:
  https://www.youtube.com/watch?v=QRpl1rM9gxM

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-services 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sat May  3 20:30:11 2014
  ExecutablePath: /usr/lib/unity/unity-panel-service
  InstallationDate: Installed on 2014-04-18 (15 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/ubuntu/+source/appmenu-qt/+bug/1315717/+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 1316320] Re: Screen Lock does not prompt for password

[Charlie Ott]

Ah! Alkis you're the best.  That was exactly the issue!  Thanks!

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

Title:
  Screen Lock does not prompt for password

Status in Linux Terminal Server Project:
  Triaged
Status in Unity:
  Invalid
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  I am using LTSP fat clients, created with:

  $ sudo ltsp-build-image --arch amd64 --fat-client-desktop ubuntu-
  desktop

  LTSP server has sssd authentication utilizing pam and ldap.  Users can
  log in without issue and the home folder is available.  Everything
  works as expected except for screen locking.

  When locking the screen, the displays first go blank and the monitor
  goes to sleep.

  Then if i move the mouse or press a keystroke, They go black but the
  mouse is visible.

  Once I move the mouse or strike a key the second time, everything
  comes back up without password prompt.  However, password prompt is
  enabled in "Brightness & Lock"

  The client hardware is an Intel NUC D34010WYK

  Also maybe related, there seems to be no system tray.  No clock or
  username/logout buttons.  I am using Ctrl + Alt + L to lock the
  screen. (See attached screenshot)

  This is a security vulnerability and I can not make the new 14.04
  image available as fat clients, since they users cannot lock their
  workstation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ltsp/+bug/1316320/+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 1302084] Re: Menu in the global title bar is missing after a window child in Qt5 applications

[Huck-bernhard]

Duplicate to Bug: 1315717 ?

https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1315717

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to appmenu-qt5 in Ubuntu.
https://bugs.launchpad.net/bugs/1302084

Title:
  Menu in the global title bar is missing after a window child in Qt5
  applications

Status in Application menu for Qt5:
  In Progress
Status in The Application Menu:
  New
Status in Unity:
  Invalid
Status in “appmenu-qt5” package in Ubuntu:
  In Progress

Bug description:
  steps to get this behavior

  1. "Settings | Appearance | Behavior" set Show the menus for a window in the 
window's title bar
  2. Open qtcreator in Normal Window Size (not maximized) .
  3. Move Mouse to the Title Bar, Menu Bar is showing. Open Menu "Open Help | 
About QtCreator..."
  4. Close Window "About Qt Creator".
  5. Move Mouse to the Title Bar, no menu bar is showing.

  this behavior is also in different QT4 and QT5 Applicaion showing.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: appmenu-qt5 0.3.0+14.04.20140314-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic i686
  ApportVersion: 2.14-0ubuntu1
  Architecture: i386
  Date: Thu Apr  3 19:38:03 2014
  InstallationDate: Installed on 2014-02-14 (47 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140214)
  SourcePackage: appmenu-qt5
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1302084/+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 1308911] Re: Clipboard contents are accessible within lockscreen

[Andrea Azzarone]

** Changed in: unity
   Status: Triaged => In Progress

** Changed in: unity (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Clipboard contents are accessible within lockscreen

Status in Unity:
  In Progress
Status in “unity” package in Ubuntu:
  In Progress

Bug description:
  - Copy e.g. my password to the clipboard (highlight and/or Ctrl+C)
  - Lock the screen (Ctrl+Alt+L)
  - Paste content from clipboard using middle mouse button or Ctrl+V into input 
field
  - Login possible (if copied text was the password)

  Expected behaviour:
  No content from clipboard available at all in lockscreen

  lsb_release -rd:
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1308911/+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 1315717] Re: Global MenuBar hidden in Qt applications after any dialog opens

[Huck-bernhard]

Duplicate to Bug: 1302084  ?

https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1302084

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

Title:
  Global MenuBar hidden in Qt applications after any dialog opens

Status in “appmenu-qt” package in Ubuntu:
  New
Status in “appmenu-qt5” package in Ubuntu:
  New
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  This appears to happen only if the main application window is NOT
  fullscreen.

  Confirmed in the following Qt applications:

  Wallch, VLC and Qt Creator

  Steps to reproduce:

  1. Open the application
  2. Exit fullscreen (unmaximize) if maximized
  3. Open any application dialog through the menu or through a shortcut (e.g. 
Ctrl+P for Preferences dialog)
  4. Close the dialog with any way.
  5. Hover your mouse where the menu should be. The menu is now gone

  Video demonstrating the problem:
  https://www.youtube.com/watch?v=QRpl1rM9gxM

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-services 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sat May  3 20:30:11 2014
  ExecutablePath: /usr/lib/unity/unity-panel-service
  InstallationDate: Installed on 2014-04-18 (15 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/ubuntu/+source/appmenu-qt/+bug/1315717/+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 1302081] Re: Menu in title bar is missing after a modal window child

[Huck-bernhard]

*** This bug is a duplicate of bug 1315717 ***
https://bugs.launchpad.net/bugs/1315717

** This bug has been marked a duplicate of bug 1315717
   Global MenuBar hidden in Qt applications after any dialog opens

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

Title:
  Menu in title bar is missing after a modal window child

Status in Application menu for Qt4:
  New
Status in “appmenu-qt” package in Ubuntu:
  Confirmed

Bug description:
  steps to get this behavior

  1. "Settings | Appearance | Behavior" set Show the menus for a window in the 
window's title bar
  2. Open qtcreator in Normal Window Size (not maximized) .
  3. Move Mouse to the Title Bar, Menu Bar is showing. Open Menu "Open Help | 
About QtCreator..."
  4. Close Window "About Qt Creator".
  5. Move Mouse to the Title Bar, no menu bar is showing.

  this behavior is also in different QT4 and QT5 Applicaion showing.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: appmenu-qt (0.2.7+14.04.20140305-0ubuntu1)
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic i686
  ApportVersion: 2.14-0ubuntu1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Thu Apr  3 19:31:17 2014
  InstallationDate: Installed on 2014-02-14 (47 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140214)
  SourcePackage: appmenu-qt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt/+bug/1302081/+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 1315717] Re: Global MenuBar hidden in Qt applications after any dialog opens

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: unity (Ubuntu)
   Status: New => Confirmed

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

Title:
  Global MenuBar hidden in Qt applications after any dialog opens

Status in “appmenu-qt” package in Ubuntu:
  New
Status in “appmenu-qt5” package in Ubuntu:
  New
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  This appears to happen only if the main application window is NOT
  fullscreen.

  Confirmed in the following Qt applications:

  Wallch, VLC and Qt Creator

  Steps to reproduce:

  1. Open the application
  2. Exit fullscreen (unmaximize) if maximized
  3. Open any application dialog through the menu or through a shortcut (e.g. 
Ctrl+P for Preferences dialog)
  4. Close the dialog with any way.
  5. Hover your mouse where the menu should be. The menu is now gone

  Video demonstrating the problem:
  https://www.youtube.com/watch?v=QRpl1rM9gxM

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-services 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sat May  3 20:30:11 2014
  ExecutablePath: /usr/lib/unity/unity-panel-service
  InstallationDate: Installed on 2014-04-18 (15 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/ubuntu/+source/appmenu-qt/+bug/1315717/+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 1315717] Re: Global MenuBar hidden in Qt applications after any dialog opens

[Huck-bernhard]

** Also affects: appmenu-qt (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: appmenu-qt5 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Global MenuBar hidden in Qt applications after any dialog opens

Status in “appmenu-qt” package in Ubuntu:
  New
Status in “appmenu-qt5” package in Ubuntu:
  New
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  This appears to happen only if the main application window is NOT
  fullscreen.

  Confirmed in the following Qt applications:

  Wallch, VLC and Qt Creator

  Steps to reproduce:

  1. Open the application
  2. Exit fullscreen (unmaximize) if maximized
  3. Open any application dialog through the menu or through a shortcut (e.g. 
Ctrl+P for Preferences dialog)
  4. Close the dialog with any way.
  5. Hover your mouse where the menu should be. The menu is now gone

  Video demonstrating the problem:
  https://www.youtube.com/watch?v=QRpl1rM9gxM

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-services 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sat May  3 20:30:11 2014
  ExecutablePath: /usr/lib/unity/unity-panel-service
  InstallationDate: Installed on 2014-04-18 (15 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/ubuntu/+source/appmenu-qt/+bug/1315717/+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 1316320] Re: Screen Lock does not prompt for password

[Alkis Georgopoulos]

The panel part might be because gnome-settings-daemon gets loaded before 
unity-settings-daemon, and thus unity-panel-service doesn't start at all.
Try manually running /usr/lib/unity/unity-panel-service, if then the panel 
applets get loaded, yeah file a separate bug against Unity*.

I don't know details about that, I've never used Unity, I'm using gnome-
fallback/flashback.

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

Title:
  Screen Lock does not prompt for password

Status in Linux Terminal Server Project:
  Triaged
Status in Unity:
  Invalid
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  I am using LTSP fat clients, created with:

  $ sudo ltsp-build-image --arch amd64 --fat-client-desktop ubuntu-
  desktop

  LTSP server has sssd authentication utilizing pam and ldap.  Users can
  log in without issue and the home folder is available.  Everything
  works as expected except for screen locking.

  When locking the screen, the displays first go blank and the monitor
  goes to sleep.

  Then if i move the mouse or press a keystroke, They go black but the
  mouse is visible.

  Once I move the mouse or strike a key the second time, everything
  comes back up without password prompt.  However, password prompt is
  enabled in "Brightness & Lock"

  The client hardware is an Intel NUC D34010WYK

  Also maybe related, there seems to be no system tray.  No clock or
  username/logout buttons.  I am using Ctrl + Alt + L to lock the
  screen. (See attached screenshot)

  This is a security vulnerability and I can not make the new 14.04
  image available as fat clients, since they users cannot lock their
  workstation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ltsp/+bug/1316320/+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 1316320] Re: Screen Lock does not prompt for password

[Charlie Ott]

In my environment, I wanted users to authenticate with thick clients
using their LDAP binding credentials.

I was able to enable SSSD authentication and add my LDAP cn to the
sudoers file on the fat client image.  After doing an ltsp-update-image,
I am able to use the sudo command with the fat client and xscreensaver
is able to authenticate allowing unlock.  So I believe Alkis, you are
correct, copying the /etc/shadow part would work for users specifically
added to the LTSP server's /etc/passwd & shadow.

Should I open another bug in regard to the gnome applets not loading?
I'm also missing the Clock, Volume Control, Network information, etc.
(See screenshot with original request).  I would like my users to at
least know what time it is. ;p

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

Title:
  Screen Lock does not prompt for password

Status in Linux Terminal Server Project:
  Triaged
Status in Unity:
  Invalid
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  I am using LTSP fat clients, created with:

  $ sudo ltsp-build-image --arch amd64 --fat-client-desktop ubuntu-
  desktop

  LTSP server has sssd authentication utilizing pam and ldap.  Users can
  log in without issue and the home folder is available.  Everything
  works as expected except for screen locking.

  When locking the screen, the displays first go blank and the monitor
  goes to sleep.

  Then if i move the mouse or press a keystroke, They go black but the
  mouse is visible.

  Once I move the mouse or strike a key the second time, everything
  comes back up without password prompt.  However, password prompt is
  enabled in "Brightness & Lock"

  The client hardware is an Intel NUC D34010WYK

  Also maybe related, there seems to be no system tray.  No clock or
  username/logout buttons.  I am using Ctrl + Alt + L to lock the
  screen. (See attached screenshot)

  This is a security vulnerability and I can not make the new 14.04
  image available as fat clients, since they users cannot lock their
  workstation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ltsp/+bug/1316320/+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 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04

[William Hua]

Hi Saveliy, you can try the PPA above as long as you're not using Unity
with the shift key as your input switcher, it seems to be working in
most cases.

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

Title:
  Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04

Status in LibreOffice Productivity Suite:
  Confirmed
Status in IBus:
  New
Status in Indicator keyboard:
  Fix Released
Status in Inkscape: A Vector Drawing Tool:
  New
Status in Mutter:
  Fix Released
Status in The OpenOffice.org Suite:
  New
Status in Unity:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-terminal” package in Ubuntu:
  Triaged
Status in “indicator-keyboard” package in Ubuntu:
  Triaged
Status in “kingsoft-office” package in Ubuntu:
  Confirmed
Status in “openjdk-7” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Triaged
Status in “unity-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” package in Fedora:
  Unknown
Status in “gnome-shell” package in Fedora:
  Unknown

Bug description:
  New keyboard layout changer in Ubuntu 13.10 introduce  old-new bug. Any 
system or application hotkey witch use char (for example: ctrl+alt+t for 
terminal or ctrl+t for new tab in browser) become unfunctional when selected 
non-latin keyboard layout.
  Hotkeys with F1-12, numbers and other non-character buttons works perfectly.

  Window manager hotkeys not affected by this bug. All hotkeys in system
  parameters->keyboard->hotkeys->windows works perfect with any keyboard
  layout.

  Workaround for some system hotkeys and two layouts (english and non-
  latin): rebind all hotkeys in your local layout. For example instead
  of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with
  english layout.  If you use english and two different non-latin
  layouts this workaround helps only with one of them.


  Dear Ubuntu users and developers! 
  Please include the following information to your comment about non-latin 
shortcuts problems:
  1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 
14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean 
installed
  2. What keyboard layout do you have
  3. What shortcut for keyboard layout switching do you use 
  4. On which session you have problems - that is one from Unity, GNOME Shell, 
GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz)
  5. With which program and its version and origin (Ubuntu repositories, PPA, 
non-deb binary package from some website) you have problems.

  By providing this information you can make bug-fixing much simpler and
  may be faster.

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1226962/+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 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04

[William Hua]

Hi DEDan, I'm not sure why IBus affected it, or why removing IBus fixed
it in the first place. My intuition says that this is purely a problem
caused specifically by the takeover of keyboard layout duties by gnome-
settings-daemon. I tested this by moving the /usr/bin/ibus-daemon binary
and killing ibus-daemon to stop it, but non-latin keyboard shortcuts
were still not working for me in Inkscape. You can try to do this
yourself to see if it helps your UTM5 issues, but I can't imagine it
helping tbh...

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

Title:
  Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04

Status in LibreOffice Productivity Suite:
  Confirmed
Status in IBus:
  New
Status in Indicator keyboard:
  Fix Released
Status in Inkscape: A Vector Drawing Tool:
  New
Status in Mutter:
  Fix Released
Status in The OpenOffice.org Suite:
  New
Status in Unity:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-terminal” package in Ubuntu:
  Triaged
Status in “indicator-keyboard” package in Ubuntu:
  Triaged
Status in “kingsoft-office” package in Ubuntu:
  Confirmed
Status in “openjdk-7” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Triaged
Status in “unity-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” package in Fedora:
  Unknown
Status in “gnome-shell” package in Fedora:
  Unknown

Bug description:
  New keyboard layout changer in Ubuntu 13.10 introduce  old-new bug. Any 
system or application hotkey witch use char (for example: ctrl+alt+t for 
terminal or ctrl+t for new tab in browser) become unfunctional when selected 
non-latin keyboard layout.
  Hotkeys with F1-12, numbers and other non-character buttons works perfectly.

  Window manager hotkeys not affected by this bug. All hotkeys in system
  parameters->keyboard->hotkeys->windows works perfect with any keyboard
  layout.

  Workaround for some system hotkeys and two layouts (english and non-
  latin): rebind all hotkeys in your local layout. For example instead
  of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with
  english layout.  If you use english and two different non-latin
  layouts this workaround helps only with one of them.


  Dear Ubuntu users and developers! 
  Please include the following information to your comment about non-latin 
shortcuts problems:
  1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 
14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean 
installed
  2. What keyboard layout do you have
  3. What shortcut for keyboard layout switching do you use 
  4. On which session you have problems - that is one from Unity, GNOME Shell, 
GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz)
  5. With which program and its version and origin (Ubuntu repositories, PPA, 
non-deb binary package from some website) you have problems.

  By providing this information you can make bug-fixing much simpler and
  may be faster.

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1226962/+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 1306499] Re: Sound indicator is laggy #287 on mako

[Launchpad Bug Tracker]

This bug was fixed in the package indicator-sound -
12.10.2+14.10.20140509-0ubuntu1

---
indicator-sound (12.10.2+14.10.20140509-0ubuntu1) utopic; urgency=low

  [ Michael Terry ]
  * Added timers to volume changes to settle frequent updates from
account services. (LP: #1306499)

  [ Nick Dedekind ]
  * Added timers to volume changes to settle frequent updates from
account services. (LP: #1306499)
 -- Ubuntu daily releaseFri, 09 May 2014 
14:43:21 +

** Changed in: indicator-sound (Ubuntu)
   Status: Confirmed => Fix Released

** Branch linked: lp:ubuntu/utopic-proposed/indicator-sound

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

Title:
  Sound indicator is laggy #287 on mako

Status in Sound Menu:
  Confirmed
Status in “indicator-sound” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  Open sound indicator
  Try and swipe the volume up and down
  Try and increase/decrease volume with the hardware vol+ & vol- keys
  Note that the slider takes a long time to update, and sometimes leaps 
backwards and forwards despite you only holding one button down.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: armhf
  Date: Fri Apr 11 10:39:43 2014
  InstallationDate: Installed on 2014-04-11 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS - armhf (20140411)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-sound/+bug/1306499/+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 1308911] Re: Clipboard contents are accessible within lockscreen

[Andrea Azzarone]

** Changed in: unity
 Assignee: (unassigned) => Andrea Azzarone (andyrock)

** Changed in: unity (Ubuntu)
 Assignee: (unassigned) => Andrea Azzarone (andyrock)

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

Title:
  Clipboard contents are accessible within lockscreen

Status in Unity:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  - Copy e.g. my password to the clipboard (highlight and/or Ctrl+C)
  - Lock the screen (Ctrl+Alt+L)
  - Paste content from clipboard using middle mouse button or Ctrl+V into input 
field
  - Login possible (if copied text was the password)

  Expected behaviour:
  No content from clipboard available at all in lockscreen

  lsb_release -rd:
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1308911/+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 1316320] Re: Screen Lock does not prompt for password

[Alkis Georgopoulos]

** Changed in: ltsp
   Status: New => Triaged

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

Title:
  Screen Lock does not prompt for password

Status in Linux Terminal Server Project:
  Triaged
Status in Unity:
  Invalid
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  I am using LTSP fat clients, created with:

  $ sudo ltsp-build-image --arch amd64 --fat-client-desktop ubuntu-
  desktop

  LTSP server has sssd authentication utilizing pam and ldap.  Users can
  log in without issue and the home folder is available.  Everything
  works as expected except for screen locking.

  When locking the screen, the displays first go blank and the monitor
  goes to sleep.

  Then if i move the mouse or press a keystroke, They go black but the
  mouse is visible.

  Once I move the mouse or strike a key the second time, everything
  comes back up without password prompt.  However, password prompt is
  enabled in "Brightness & Lock"

  The client hardware is an Intel NUC D34010WYK

  Also maybe related, there seems to be no system tray.  No clock or
  username/logout buttons.  I am using Ctrl + Alt + L to lock the
  screen. (See attached screenshot)

  This is a security vulnerability and I can not make the new 14.04
  image available as fat clients, since they users cannot lock their
  workstation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ltsp/+bug/1316320/+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 1316320] Re: Screen Lock does not prompt for password

[Alkis Georgopoulos]

LDM uses `ssh user@server` to authenticate users.
It then copies the user /etc/passwd information from the server to the client,
but it doesn't copy the /etc/shadow part, i.e. the user password hash.

So fat client and localapps users do not have a password set, and thus
cannot use `sudo`, cannot unlock a screensaver etc.

The fix would be to let LDM/ssh.c write the hash of the password it gets from 
the user, locally to /etc/passwd.
Patches welcome for that.

In the future, for LTSP 6, the plan is to drop LDM completely and use
pam to authenticate users, so there won't be issues like that there. But
without contributors, LTSP 6 might take a long while to arrive... :)

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

Title:
  Screen Lock does not prompt for password

Status in Linux Terminal Server Project:
  New
Status in Unity:
  Invalid
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  I am using LTSP fat clients, created with:

  $ sudo ltsp-build-image --arch amd64 --fat-client-desktop ubuntu-
  desktop

  LTSP server has sssd authentication utilizing pam and ldap.  Users can
  log in without issue and the home folder is available.  Everything
  works as expected except for screen locking.

  When locking the screen, the displays first go blank and the monitor
  goes to sleep.

  Then if i move the mouse or press a keystroke, They go black but the
  mouse is visible.

  Once I move the mouse or strike a key the second time, everything
  comes back up without password prompt.  However, password prompt is
  enabled in "Brightness & Lock"

  The client hardware is an Intel NUC D34010WYK

  Also maybe related, there seems to be no system tray.  No clock or
  username/logout buttons.  I am using Ctrl + Alt + L to lock the
  screen. (See attached screenshot)

  This is a security vulnerability and I can not make the new 14.04
  image available as fat clients, since they users cannot lock their
  workstation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ltsp/+bug/1316320/+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 1320112] Re: With Multi-Screen mouse pointer sticks at the wrong side of the launcher

[Stephen M. Webb]

It's highly likely this problem is in the x.org barrier code, but needs
further investigation.

** Changed in: unity (Ubuntu)
   Importance: Undecided => Medium

** Changed in: unity (Ubuntu)
   Status: Confirmed => Triaged

** Also affects: unity
   Importance: Undecided
   Status: New

** Changed in: unity
   Importance: Undecided => Medium

** Changed in: unity
   Status: New => Triaged

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

Title:
  With Multi-Screen mouse pointer sticks at the wrong side of the
  launcher

Status in Unity:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  When using Unity with multiple Screens (2 in my case) the mousepointer
  is sticky at the edge between the two screens. The second screen is
  attached, to the right side of the first.

  While moving the mouse from the left screen, to the right, it is
  stopped on the edge. Thereby the mousepointer is shown on the right
  screen over the launcher, but still sticks to the left screen.

  This is very annoying, since haptic does not match optic in that case.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-26.48-generic 3.13.11
  Uname: Linux 3.13.0-26-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri May 16 09:14:29 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-10-25 (202 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-04-22 (23 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1320112/+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 1320112] Re: With Multi-Screen mouse pointer sticks at the wrong side of the launcher

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: unity (Ubuntu)
   Status: New => Confirmed

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

Title:
  With Multi-Screen mouse pointer sticks at the wrong side of the
  launcher

Status in Unity:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  When using Unity with multiple Screens (2 in my case) the mousepointer
  is sticky at the edge between the two screens. The second screen is
  attached, to the right side of the first.

  While moving the mouse from the left screen, to the right, it is
  stopped on the edge. Thereby the mousepointer is shown on the right
  screen over the launcher, but still sticks to the left screen.

  This is very annoying, since haptic does not match optic in that case.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-26.48-generic 3.13.11
  Uname: Linux 3.13.0-26-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri May 16 09:14:29 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-10-25 (202 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-04-22 (23 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1320112/+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 1298202] Re: compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout()

[Margarita Manterola]

Hi,

Still seeing this bug, also when unlocking the screen.  Unity version
7.2.0+14.04.20140423-0ubuntu1.2. Is the fix supposed to be released to
Trusty?

This is the stacktrace top from the apport crash report:
?? ()
nux::WindowThread::ComputeQueuedLayout() () from 
/usr/lib/x86_64-linux-gnu/libnux-4.0.so.0
nux::WindowThread::RenderInterfaceFromForeignCmd(nux::Rect const&) () from 
/usr/lib/x86_64-linux-gnu/libnux-4.0.so.0
unity::UnityScreen::paintDisplay() () from /usr/lib/compiz/libunityshell.so
unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const&, GLMatrix const&, 
CompRegion const&, CompOutput*, unsigned int) () from 
/usr/lib/compiz/libunityshell.so

And the full stack trace:

#1  0x7fd95322e75d in nux::WindowThread::ComputeQueuedLayout() () from 
/usr/lib/x86_64-linux-gnu/libnux-4.0.so.0
#2  0x7fd95322fb28 in 
nux::WindowThread::RenderInterfaceFromForeignCmd(nux::Rect const&) () from 
/usr/lib/x86_64-linux-gnu/libnux-4.0.so.0
#3  0x7fd95496e0a9 in unity::UnityScreen::paintDisplay() () from 
/usr/lib/compiz/libunityshell.so
#4  0x7fd95496e468 in unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib 
const&, GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) () from 
/usr/lib/compiz/libunityshell.so
#5  0x7fd9688b1272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const&, 
GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) () from 
/usr/lib/compiz/libopengl.so
#6  0x7fd9688b1ed4 in PrivateGLScreen::paintOutputs(std::list >&, unsigned int, CompRegion const&) () from 
/usr/lib/compiz/libopengl.so
#7  0x7fd968ce944f in CompositeScreen::paint(std::list >&, unsigned int) () from 
/usr/lib/compiz/libcomposite.so
#8  0x7fd968cecaf2 in CompositeScreen::handlePaintTimeout() () from 
/usr/lib/compiz/libcomposite.so
#9  0x7fd975d8d53d in CompTimer::triggerCallback() () from 
/usr/lib/libcompiz_core.so.ABI-20140123
#10 0x7fd975d8d5ef in CompTimeoutSource::callback() () from 
/usr/lib/libcompiz_core.so.ABI-20140123
#11 0x7fd975d8cb4d in CompTimeoutSource::dispatch(sigc::slot_base*) () from 
/usr/lib/libcompiz_core.so.ABI-20140123
#12 0x7fd97427935f in Glib::Source::dispatch_vfunc(_GSource*, int 
(*)(void*), void*) () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1
#13 0x7fd973d6bce5 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x7fd973d6c048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x7fd973d6c30a in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x7fd975d480eb in 
compiz::private_screen::EventManager::startEventLoop(_XDisplay*) () from 
/usr/lib/libcompiz_core.so.ABI-20140123
#17 0x00401971 in main ()

Please let me know if you want more information.

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

Title:
  compiz crashed with SIGSEGV in
  nux::WindowThread::ComputeQueuedLayout()

Status in Unity:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  no further informations

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1298202/+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 1284898] Re: compiz crashed with SIGSEGV in ScaleScreen::getSelectedWindow()

[Philippe]

No news on this ?

That shortcut is kinda handy.

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

Title:
  compiz crashed with SIGSEGV in ScaleScreen::getSelectedWindow()

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  crashed when pressing super + w and trying to select a window

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140220-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
  Uname: Linux 3.13.0-12-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Feb 25 18:17:20 2014
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2014-02-25 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140223)
  ProcCmdline: compiz
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f1d2b6410c0 
<_ZNK11ScaleScreen17getSelectedWindowEv>:   mov0x48(%rdi),%rax
   PC (0x7f1d2b6410c0) ok
   source "0x48(%rdi)" (0x0048) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   ScaleScreen::getSelectedWindow() const () from /usr/lib/compiz/libscale.so
   unity::UnityScreen::handleEvent(_XEvent*) () from 
/usr/lib/compiz/libunityshell.so
   CompScreen::handleEvent(_XEvent*) () from 
/usr/lib/libcompiz_core.so.ABI-20140123
   PrivateScaleScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libscale.so
   CompScreen::handleEvent(_XEvent*) () from 
/usr/lib/libcompiz_core.so.ABI-20140123
  Title: compiz crashed with SIGSEGV in ScaleScreen::getSelectedWindow()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1284898/+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 1316320] Re: Screen Lock does not prompt for password

[Andrea Azzarone]

Seems like it's something wanted:
ltsp-5.5.1/client/Debian/share/ltsp/init-ltsp.d/50-gsettings-overrides:disable-lock-screen=true

So marking unity as invalid.

** Also affects: ltsp
   Importance: Undecided
   Status: New

** Changed in: unity
   Status: Incomplete => Invalid

** Changed in: unity (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Screen Lock does not prompt for password

Status in Linux Terminal Server Project:
  New
Status in Unity:
  Invalid
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  I am using LTSP fat clients, created with:

  $ sudo ltsp-build-image --arch amd64 --fat-client-desktop ubuntu-
  desktop

  LTSP server has sssd authentication utilizing pam and ldap.  Users can
  log in without issue and the home folder is available.  Everything
  works as expected except for screen locking.

  When locking the screen, the displays first go blank and the monitor
  goes to sleep.

  Then if i move the mouse or press a keystroke, They go black but the
  mouse is visible.

  Once I move the mouse or strike a key the second time, everything
  comes back up without password prompt.  However, password prompt is
  enabled in "Brightness & Lock"

  The client hardware is an Intel NUC D34010WYK

  Also maybe related, there seems to be no system tray.  No clock or
  username/logout buttons.  I am using Ctrl + Alt + L to lock the
  screen. (See attached screenshot)

  This is a security vulnerability and I can not make the new 14.04
  image available as fat clients, since they users cannot lock their
  workstation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ltsp/+bug/1316320/+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 1320112] [NEW] With Multi-Screen mouse pointer sticks at the wrong side of the launcher

[BeowulfOF]

Public bug reported:

When using Unity with multiple Screens (2 in my case) the mousepointer
is sticky at the edge between the two screens. The second screen is
attached, to the right side of the first.

While moving the mouse from the left screen, to the right, it is stopped
on the edge. Thereby the mousepointer is shown on the right screen over
the launcher, but still sticks to the left screen.

This is very annoying, since haptic does not match optic in that case.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
ProcVersionSignature: Ubuntu 3.13.0-26.48-generic 3.13.11
Uname: Linux 3.13.0-26-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Fri May 16 09:14:29 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-10-25 (202 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2014-04-22 (23 days ago)

** Affects: unity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

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

Title:
  With Multi-Screen mouse pointer sticks at the wrong side of the
  launcher

Status in “unity” package in Ubuntu:
  New

Bug description:
  When using Unity with multiple Screens (2 in my case) the mousepointer
  is sticky at the edge between the two screens. The second screen is
  attached, to the right side of the first.

  While moving the mouse from the left screen, to the right, it is
  stopped on the edge. Thereby the mousepointer is shown on the right
  screen over the launcher, but still sticks to the left screen.

  This is very annoying, since haptic does not match optic in that case.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-26.48-generic 3.13.11
  Uname: Linux 3.13.0-26-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri May 16 09:14:29 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-10-25 (202 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-04-22 (23 days ago)

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