Re: [Dx-packages] [Bug 1331873] Re: the "Ubuntu Help" should be "Ubuntu Kylin Help"

[handsome_feng]

I tested it in ubuntukylin 14.10 a short while ago ,it works well ,thank
you !

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

Title:
  the "Ubuntu Help" should be "Ubuntu Kylin Help"

Status in The Session Menu:
  Fix Released
Status in Ubuntu Kylin:
  Fix Committed
Status in “indicator-session” package in Ubuntu:
  Fix Released

Bug description:
  the "Ubuntu Help"should be "Ubuntu Kuliy Help" in the indicator ,since
  this is ubuntuKylin system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-session/+bug/1331873/+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 1344990] Re: Volume control jumps back and forth

[Jussi Lind]

Actually, this has nothing to do with Audacious, it's just that the
volume control is not stable.

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

Title:
  Volume control jumps back and forth

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

Bug description:
  Steps to reproduce:

  1) Listen to music via Audacious
  2) Open volume control from Unity's panel
  3) Try to change the volume

  What happens:

  - The volume control doesn't follow mouse properly and jumps back and
  forth

  What should happen:

  - The obvious thing

  I believe this is regression as didn't notice anything weird in 13.10
  with exactly same setup.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sat Jul 19 19:51:32 2014
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1344990/+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 1334998] Re: When using Super+L keys autohide not working properly

[pabouk]

Another workaround is to use the alternative shortcut without Super:
Ctrl+Alt+L

Probably the shortcuts with Super should cancel showing of the Launcher
when the other key of the shortcut (like L in Super+L) is pressed.

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

Title:
  When using Super+L keys autohide not working properly

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

Bug description:
  When using the super+l keys to lock the screen, the unity panel gets
  stuck. This happens whenever the user first clicks on the super key
  and then the L key.  Clicking simutaniously works as expected.

  The issue was also reported on Ask Ubuntu:
  http://askubuntu.com/questions/459585/launcher-auto-hide-not-working-
  ubuntu-14-04/469732?noredirect=1#comment652314_469732

  There is a workaround (the user has to double tap the super key)
  however, this is one of those papercuts that gets rather annoying over
  time.

  I would expect the system to be a little more tolerant in terms of the
  sequnce of keys pressed. If I first click on the super key and then
  the L key, the panel will not be locked when I log back in.

  ===
  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://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://archive.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
   7.2.0+14.04.20140416-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  ===
  Screenshot: http://i.imgur.com/e3AePQ8.png

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.1+14.04.20140513-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
  Uname: Linux 3.13.0-30-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: Fri Jun 27 09:23:52 2014
  InstallationDate: Installed on 2014-03-16 (103 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140313)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1334998/+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 1349128] Re: Ubuntu 14.04 login screen doesn't accept keyboard input (until using indicators)

[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/1349128

Title:
  Ubuntu 14.04 login screen doesn't accept keyboard input (until using
  indicators)

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

Bug description:
  Ubuntu 14.04 login screen doesn't accept keyboard input in the
  password box after my system has resumed from a sleep (=lid opening),
  so I can't relogin anymore

  Excpected behaviour: the login screen should accept keyboard input and
  show them as stars in the password box.

  Workaround: click on "switch user" in the upper right corner, after
  which keyboard input is accepted again.

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

  System is fully updated. Problem started to happen one or two weeks
  ago, so around mid July 2014.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1349128/+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 1349128] Re: Ubuntu 14.04 login screen doesn't accept keyboard input (until using indicators)

[Francis Potter]

This happens on my Dell XPS13 laptop. Here are the steps:

- Close the lid
- Wait a minute
- Open it back up

The login screen appears. The cursor is in the password area and is
flashing. Nothing I type on the keyboard does anything.

- Click on anything in the top bar -- the battery indicator, or the gear icon, 
or the clock
- Hit escape or click on the password box again

Now it works.

- Type my password and log in

This part is interesting: the things I was typing when attempting to log
in have been entered into the OS. In other words, if I had a browser
window up, my password attempts are there in the address bar. So the
things that I type on the login screen, when not accepted by the login
screen, are actually being accepted by the underlying operating system.

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

Title:
  Ubuntu 14.04 login screen doesn't accept keyboard input (until using
  indicators)

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

Bug description:
  Ubuntu 14.04 login screen doesn't accept keyboard input in the
  password box after my system has resumed from a sleep (=lid opening),
  so I can't relogin anymore

  Excpected behaviour: the login screen should accept keyboard input and
  show them as stars in the password box.

  Workaround: click on "switch user" in the upper right corner, after
  which keyboard input is accepted again.

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

  System is fully updated. Problem started to happen one or two weeks
  ago, so around mid July 2014.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1349128/+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 1301125] Re: Lock screen after idle time freezes unity

[bguiz]

Not sure if my problem is due to the same reasons, as the lock screen is
completely frozen - cannot even `Ctrl+Alt+F1` to go to tty, and mouse
will not move. Otherwise exactly the same: Screen when going to locking
manually using `Ctrl+Alt+L`works fine and responds to mouse/ keyboard.
Screen when locked from a timeout is completely unresponsive. The only
thing that responds is `Alt+SysRq+REISUB`.

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

Title:
  Lock screen after idle time freezes unity

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

Bug description:
  Hello,

  I recently upgrade to 14.04. My system uses fglrx provided by 14.04.

  When I lock manually the screen, I get no problem. I can even sleep the 
system without problem. However,
  when the screen is locked by idle time, I cannot unlock it.

  At this point, I can see the screen but with some kind of translucent
  panel over it. Mouse also works. I tried to type blink the password
  but I had no luck. I only get a working system by going text mode
  (ctrl+alt+f1) and restarting lightdm. No dmesg or Xorg logs seems to
  indicate any error. The only strange log was in .xsession-errors.old:

  init: processos unity-settings-daemon main (2495) terminados com status 1
  init: processos gnome-session (Unity) main (2539) terminados com status 1
  init: processos unity-panel-service main (2572) terminados com status 1
  init: processos hud main (2536) terminados com status 1
  init: processo indicator-powermain (2740) morto pelo sinal TERM
  init: processo indicator-datetimemain (2741) morto pelo sinal TERM
  init: processo indicator-soundmain (2747) morto pelo sinal TERM
  init: processo indicator-printersmain (2748) morto pelo sinal TERM
  init: processo indicator-sessionmain (2768) morto pelo sinal TERM
  init: processo indicator-syncmain (2795) morto pelo sinal TERM
  init: processo update-notifier-crash 
(/var/crash/_usr_bin_istanbul.1000.crash)main (4987) morto pelo sinal TERM
  init: processos unity-panel-service-lockscreen main (7447) terminados com 
status 1
  init: Disconnected from notified D-Bus bus
  init: processos at-spi2-registryd main (2538) terminados com status 1

  But as it has no time info, I cannot tell when they happened.

  At least another user faces the same problem:
  http://ubuntuforums.org/showthread.php?t=2214421

  And this seems to be different from bug 1283938 as pm sleep/wake works
  as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140328.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Apr  2 00:01:05 2014
  DistUpgraded: 2014-03-31 21:24:46,145 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx-updates, 13.350.1, 3.11.0-18-generic, x86_64: installed
   fglrx-updates, 13.350.1, 3.13.0-20-generic, x86_64: installed
   vboxhost, 4.3.10, 3.11.0-18-generic, x86_64: installed
   vboxhost, 4.3.10, 3.13.0-20-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0012]
  InstallationDate: Installed on 2012-10-19 (529 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  JockeyStatus:
   kmod:wl - Broadcom STA wireless driver (Proprietário, Desativado, Não está 
em uso) [auto-install]
   kmod:fglrx - Video driver for the AMD graphics accelerators (Proprietário, 
Desativado, Não está em uso)
   kmod:fglrx_updates - ATI Fire GL (Proprietário, Habilitado, Não está em uso)
  MachineType: Dell Inc. XPS 8300
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic 
root=UUID=6633d579-d782-47ec-ad5a-22abac1412a0 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-04-01 (1 days ago)
  dmi.bios.date: 10/17/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0Y2MRG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd10/17/2011:svnDellInc.:pnXPS8300:pvr:rvnDellInc.:rn0Y2MRG:rvrA01:cvnDellInc.:ct3:cvr:
  dmi.product.name: XPS 8300
  dmi.sys.vendor: Dell Inc.
  version.compiz

[Dx-packages] [Bug 1301125] Re: Lock screen after idle time freezes unity

[bguiz]

I'll just add that I have posted some questions about this (with a more
complete description) on askubuntu.com:

- http://askubuntu.com/q/503184/7593
- http://askubuntu.com/q/503238/7593

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

Title:
  Lock screen after idle time freezes unity

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

Bug description:
  Hello,

  I recently upgrade to 14.04. My system uses fglrx provided by 14.04.

  When I lock manually the screen, I get no problem. I can even sleep the 
system without problem. However,
  when the screen is locked by idle time, I cannot unlock it.

  At this point, I can see the screen but with some kind of translucent
  panel over it. Mouse also works. I tried to type blink the password
  but I had no luck. I only get a working system by going text mode
  (ctrl+alt+f1) and restarting lightdm. No dmesg or Xorg logs seems to
  indicate any error. The only strange log was in .xsession-errors.old:

  init: processos unity-settings-daemon main (2495) terminados com status 1
  init: processos gnome-session (Unity) main (2539) terminados com status 1
  init: processos unity-panel-service main (2572) terminados com status 1
  init: processos hud main (2536) terminados com status 1
  init: processo indicator-powermain (2740) morto pelo sinal TERM
  init: processo indicator-datetimemain (2741) morto pelo sinal TERM
  init: processo indicator-soundmain (2747) morto pelo sinal TERM
  init: processo indicator-printersmain (2748) morto pelo sinal TERM
  init: processo indicator-sessionmain (2768) morto pelo sinal TERM
  init: processo indicator-syncmain (2795) morto pelo sinal TERM
  init: processo update-notifier-crash 
(/var/crash/_usr_bin_istanbul.1000.crash)main (4987) morto pelo sinal TERM
  init: processos unity-panel-service-lockscreen main (7447) terminados com 
status 1
  init: Disconnected from notified D-Bus bus
  init: processos at-spi2-registryd main (2538) terminados com status 1

  But as it has no time info, I cannot tell when they happened.

  At least another user faces the same problem:
  http://ubuntuforums.org/showthread.php?t=2214421

  And this seems to be different from bug 1283938 as pm sleep/wake works
  as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140328.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Apr  2 00:01:05 2014
  DistUpgraded: 2014-03-31 21:24:46,145 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx-updates, 13.350.1, 3.11.0-18-generic, x86_64: installed
   fglrx-updates, 13.350.1, 3.13.0-20-generic, x86_64: installed
   vboxhost, 4.3.10, 3.11.0-18-generic, x86_64: installed
   vboxhost, 4.3.10, 3.13.0-20-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0012]
  InstallationDate: Installed on 2012-10-19 (529 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  JockeyStatus:
   kmod:wl - Broadcom STA wireless driver (Proprietário, Desativado, Não está 
em uso) [auto-install]
   kmod:fglrx - Video driver for the AMD graphics accelerators (Proprietário, 
Desativado, Não está em uso)
   kmod:fglrx_updates - ATI Fire GL (Proprietário, Habilitado, Não está em uso)
  MachineType: Dell Inc. XPS 8300
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic 
root=UUID=6633d579-d782-47ec-ad5a-22abac1412a0 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-04-01 (1 days ago)
  dmi.bios.date: 10/17/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0Y2MRG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd10/17/2011:svnDellInc.:pnXPS8300:pvr:rvnDellInc.:rn0Y2MRG:rvrA01:cvnDellInc.:ct3:cvr:
  dmi.product.name: XPS 8300
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ub

[Dx-packages] [Bug 1078512] Re: Regression -- Some applications icons in Unity Dash are displayed too large

[Launchpad Bug Tracker]

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

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

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

Title:
  Regression -- Some applications icons in Unity Dash are displayed too
  large

Status in Unity Applications Lens:
  New
Status in “unity-lens-applications” package in Ubuntu:
  Confirmed

Bug description:
  I am on unity-lens-applications 6.10.0-0ubuntu1, with Quantal Proposed
  enabled in Software Sources. I see large application icons for some
  applications. This is a regression, as this wasn't the case until
  recently.

  This issue might coincide with bug #1052513.

  In my case, these icons are enlarged within the application lens:

  Unison
  Weather Indicator
  Guake
  Xmind
  XDiagnose
  XML Copy Editor

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unity-lens-applications 6.10.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Tue Nov 13 18:09:00 2012
  EcryptfsInUse: Yes
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity-lens-applications
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-lens-applications/+bug/1078512/+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 1292218] Re: Lockscreen prompt missing hi dpi

[Treviño]

** No longer affects: unity/7.2

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

** Changed in: unity/7.2
   Status: New => In Progress

** Changed in: unity/7.2
Milestone: None => 7.2.3

** Changed in: unity/7.2
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: unity
Milestone: None => 7.3.1

** Branch unlinked: lp:~brandontschaefer/unity/fix-lockscreen-hidpi-
support

** Branch linked: lp:~3v1n0/unity/scaling-lockscreen

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

Title:
  Lockscreen prompt missing hi dpi

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

Bug description:
  The lockscreen has correct Panel HiDPI support, but the prompt doesn't
  scale right now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1292218/+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 1292218] Re: Lockscreen prompt missing hi dpi

[Treviño]

** Changed in: unity
 Assignee: Brandon Schaefer (brandontschaefer) => Marco Trevisan (Treviño) 
(3v1n0)

** Changed in: unity (Ubuntu)
 Assignee: Brandon Schaefer (brandontschaefer) => Marco Trevisan (Treviño) 
(3v1n0)

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

Title:
  Lockscreen prompt missing hi dpi

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

Bug description:
  The lockscreen has correct Panel HiDPI support, but the prompt doesn't
  scale right now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1292218/+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 1292218] Re: Lockscreen prompt missing hi dpi

[Treviño]

** Tags added: hidpi

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

Title:
  Lockscreen prompt missing hi dpi

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

Bug description:
  The lockscreen has correct Panel HiDPI support, but the prompt doesn't
  scale right now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1292218/+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 1305586] Re: Lock screen is unusable when some windows have a keyboard/mouse grab

[David Overcash]

And my Unity version:

$ apt-cache policy unity
unity:
  Installed: 7.2.2+14.04.20140714-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/1305586

Title:
  Lock screen is unusable when some windows have a keyboard/mouse grab

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  Fix Released
Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Released
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Released
Status in “unity” source package in Trusty:
  Fix Released

Bug description:
  [Impact]
  Some windows will grab the keyboard/mouse and when the lockscreen kicks in, 
this window will still have the grab and thusly, you can't enter your password 
in the lockscreen.

  [Test case]
  This will work only in the case that your lockscreen is set (from unity 
control center, lock pane) to lock immediately (when screen turns off).

  1. Open a window that will hold the grab, such as the ssh password dialog or 
a virtual
 machine (such as virtualbox in fullscreen).
  2. Wait for the lock screen to activate [1].
  3. The screen won't be locked, since it's not possible to steal drag to 
another window.

  [Regression potential]
  For the same reason of lp:49579, we can't lock the screen (yet) if something 
takes the grab in X, or we won't able to get input back. This is not a 
regression because it has never been possible in Ubuntu before, while when we 
tried that, it caused this bug.

  A possible source of regression might be that we now try to
  grab/ungrab the screen (the only X reliable way for grab checking),
  when showing the dash/hud or the lockscreen itself, and this might
  slow things down a little, but from measurements done this slow down
  is generally about 2ms, so nothing to worry about.

  
  * Compiz Debdiff is found at 
https://launchpadlibrarian.net/178439518/compiz-trusty-sru-2.debdiff *

  [1] You can use this to reduce the locking delay:
gsettings set org.gnome.desktop.session idle-delay 5
  and resetting it with:
gsettings reset org.gnome.desktop.session idle-delay

  ---

  Original Description:

  My screen just timed out and locked when a password prompt which had a
  grab was displaying.

  I couldn't type my password or interact with the indicators.

  gnome-screensaver just refuses to lock in this situation, perhaps
  unity could do the same unless it's possible to remove and readd the
  grabs yourself, but I don't think XLib lets you do that (you can only
  remove your own grabs AFAIK).

  TEMPORARY WORKAROUND TO LOGIN AGAIN:
  Click on the guest session
  Once the guest session is started log out
  This takes you back to the lightdm session screen you can then login to your 
user session and it be in the same state

  ProblemType: BugDistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140409-0ubuntu1 [origin: unknown]
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CrashDB: unity
  CurrentDesktop: Unity
  Date: Thu Apr 10 09:39:45 2014
  InstallationDate: Installed on 2012-10-07 (549 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 
(20121007)SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-05-07 (338 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1305586/+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 1071738] Re: Indicator scroll event says direction UP on 12.10 even when scrolling down

[Peter Levi]

This comment from a pygobject developer casts more insight and claims
the problem is in libappindicator:

https://bugzilla.gnome.org/show_bug.cgi?id=732470#c5

Citing:
"The issue seems to be related to libappindicator using a GI annotation for the
scroll-events direction with (type  Gdk.ScrollDirection), whereas the signal is
created using G_TYPE_UINT as the GValue argument type [1]. Emitting
'scroll-event' either with dbus or Python as Christoph has shown passes a
GValue holding an integer. When pygobject receives the signal, it tries to
marshal this GValue as an enum based on the introspection information (using
g_value_get_enum) which is what causes the assertion shown above. Beyond the
assertion warning, g_value_get_enum() also returns 0 which ends up being
GTK_SCROLL_UP (very similar to bug 693664).

We could hack around this in pygobject by also accepting integer types as valid
enum values, but I believe the root of the problem lies in libappindicator
using an annotation which differs in fundamental type than what the signal
describes for its GValue marshaller (G_TYPE_ENUM vs. G_TYPE_UINT).

[1]
http://bazaar.launchpad.net/~indicator-applet-developers/libappindicator/trunk.14.10/view/head:/src/app-indicator.c#L526
"

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

Title:
  Indicator scroll event says direction UP on 12.10 even when scrolling
  down

Status in “libappindicator” package in Ubuntu:
  Confirmed

Bug description:
  I am using AppIndicator via Python. On Ubuntu 12.10 (stock install,
  python-appindicator: Installed: 12.10.0-0ubuntu1) when I listen for
  scroll event signals, the direction is always reported as UP, never as
  DOWN - even when scrolling down. This was working on 12.04.

  My application variety depends on this functionality, here is the
  relevant bug report for it:
  https://bugs.launchpad.net/variety/+bug/1071598

  Here is sample code to demonstrate the problem (OK on 12.04, buggy on
  12.10):

  from gi.repository import Gtk, Gdk, AppIndicator3

  if __name__ == "__main__":
  menu = Gtk.Menu()
  quit = Gtk.MenuItem("Quit")
  quit.connect("activate", Gtk.main_quit)
  menu.append(quit)
  menu.show_all()

  def scroll(ind, steps, direction):
  print steps, direction
  if direction != Gdk.ScrollDirection.UP:
  print "Things seem ok"

  indicator = AppIndicator3.Indicator.new('testscroll', '', 
AppIndicator3.IndicatorCategory.APPLICATION_STATUS)
  indicator.set_status(AppIndicator3.IndicatorStatus.ACTIVE)
  indicator.set_icon("/usr/share/pixmaps/firefox.png")
  indicator.connect("scroll-event", scroll)
  indicator.set_menu(menu)
  Gtk.main()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1071738/+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 1305586] Re: Lock screen is unusable when some windows have a keyboard/mouse grab

[David Overcash]

This also happens in Chromium.

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

Title:
  Lock screen is unusable when some windows have a keyboard/mouse grab

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  Fix Released
Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Released
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Released
Status in “unity” source package in Trusty:
  Fix Released

Bug description:
  [Impact]
  Some windows will grab the keyboard/mouse and when the lockscreen kicks in, 
this window will still have the grab and thusly, you can't enter your password 
in the lockscreen.

  [Test case]
  This will work only in the case that your lockscreen is set (from unity 
control center, lock pane) to lock immediately (when screen turns off).

  1. Open a window that will hold the grab, such as the ssh password dialog or 
a virtual
 machine (such as virtualbox in fullscreen).
  2. Wait for the lock screen to activate [1].
  3. The screen won't be locked, since it's not possible to steal drag to 
another window.

  [Regression potential]
  For the same reason of lp:49579, we can't lock the screen (yet) if something 
takes the grab in X, or we won't able to get input back. This is not a 
regression because it has never been possible in Ubuntu before, while when we 
tried that, it caused this bug.

  A possible source of regression might be that we now try to
  grab/ungrab the screen (the only X reliable way for grab checking),
  when showing the dash/hud or the lockscreen itself, and this might
  slow things down a little, but from measurements done this slow down
  is generally about 2ms, so nothing to worry about.

  
  * Compiz Debdiff is found at 
https://launchpadlibrarian.net/178439518/compiz-trusty-sru-2.debdiff *

  [1] You can use this to reduce the locking delay:
gsettings set org.gnome.desktop.session idle-delay 5
  and resetting it with:
gsettings reset org.gnome.desktop.session idle-delay

  ---

  Original Description:

  My screen just timed out and locked when a password prompt which had a
  grab was displaying.

  I couldn't type my password or interact with the indicators.

  gnome-screensaver just refuses to lock in this situation, perhaps
  unity could do the same unless it's possible to remove and readd the
  grabs yourself, but I don't think XLib lets you do that (you can only
  remove your own grabs AFAIK).

  TEMPORARY WORKAROUND TO LOGIN AGAIN:
  Click on the guest session
  Once the guest session is started log out
  This takes you back to the lightdm session screen you can then login to your 
user session and it be in the same state

  ProblemType: BugDistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140409-0ubuntu1 [origin: unknown]
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CrashDB: unity
  CurrentDesktop: Unity
  Date: Thu Apr 10 09:39:45 2014
  InstallationDate: Installed on 2012-10-07 (549 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 
(20121007)SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-05-07 (338 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1305586/+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 1305586] Re: Lock screen is unusable when some windows have a keyboard/mouse grab

[David Overcash]

I'm still seeing this issue when Google Chrome is the last open ( and
focused ) application upon suspend.  When I typed my password in it
didn't work - so I did the "switch account" hack and logged in - and
found my password sitting in the Chrome address bar.

I've installed the latest proposed updates and have the following compiz 
version:
$ apt-cache policy compiz
compiz:
  Installed: 1:0.9.11.2+14.04.20140714-0ubuntu1

Let me know if I'm missing anything.

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

Title:
  Lock screen is unusable when some windows have a keyboard/mouse grab

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  Fix Released
Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Released
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Released
Status in “unity” source package in Trusty:
  Fix Released

Bug description:
  [Impact]
  Some windows will grab the keyboard/mouse and when the lockscreen kicks in, 
this window will still have the grab and thusly, you can't enter your password 
in the lockscreen.

  [Test case]
  This will work only in the case that your lockscreen is set (from unity 
control center, lock pane) to lock immediately (when screen turns off).

  1. Open a window that will hold the grab, such as the ssh password dialog or 
a virtual
 machine (such as virtualbox in fullscreen).
  2. Wait for the lock screen to activate [1].
  3. The screen won't be locked, since it's not possible to steal drag to 
another window.

  [Regression potential]
  For the same reason of lp:49579, we can't lock the screen (yet) if something 
takes the grab in X, or we won't able to get input back. This is not a 
regression because it has never been possible in Ubuntu before, while when we 
tried that, it caused this bug.

  A possible source of regression might be that we now try to
  grab/ungrab the screen (the only X reliable way for grab checking),
  when showing the dash/hud or the lockscreen itself, and this might
  slow things down a little, but from measurements done this slow down
  is generally about 2ms, so nothing to worry about.

  
  * Compiz Debdiff is found at 
https://launchpadlibrarian.net/178439518/compiz-trusty-sru-2.debdiff *

  [1] You can use this to reduce the locking delay:
gsettings set org.gnome.desktop.session idle-delay 5
  and resetting it with:
gsettings reset org.gnome.desktop.session idle-delay

  ---

  Original Description:

  My screen just timed out and locked when a password prompt which had a
  grab was displaying.

  I couldn't type my password or interact with the indicators.

  gnome-screensaver just refuses to lock in this situation, perhaps
  unity could do the same unless it's possible to remove and readd the
  grabs yourself, but I don't think XLib lets you do that (you can only
  remove your own grabs AFAIK).

  TEMPORARY WORKAROUND TO LOGIN AGAIN:
  Click on the guest session
  Once the guest session is started log out
  This takes you back to the lightdm session screen you can then login to your 
user session and it be in the same state

  ProblemType: BugDistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140409-0ubuntu1 [origin: unknown]
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CrashDB: unity
  CurrentDesktop: Unity
  Date: Thu Apr 10 09:39:45 2014
  InstallationDate: Installed on 2012-10-07 (549 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 
(20121007)SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-05-07 (338 days ago)

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

[Shvets Jan]

Fix doesn't fix anything. If app was started with russian layout -
hotkeys doesn't work, even change layout to english. I use 14.04 with
newest updates, and problem still exist now (2014/07/28). Only solution
for now is to start all apps with english layout or keep different
layouts for every app with english as default.

-- 
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 Aptana Studio Installer:
  New
Status in Default settings for the Baltix GNU/Linux OS and desktop:
  New
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 MonoDevelop:
  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 “openjdk-7” package in Ubuntu:
  Triaged
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/aptana-studio-installer/+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 1284767] Re: Unity fails to start with a 4K monitor attached

[Zan Lynx]

Here is xrandr --verbose from a running and working session

Screen 0: minimum 320 x 200, current 5760 x 2160, maximum 8192 x 8192
eDP1 connected 1920x1080+0+0 (0x46) normal (normal left inverted right x axis y 
axis) 294mm x 165mm
Identifier: 0x42
Timestamp:  2779103
Subpixel:   unknown
Gamma:  1.0:1.0:1.0
Brightness: 1.0
Clones:
CRTC:   0
CRTCs:  0 1 2
Transform:  1.00 0.00 0.00
0.00 1.00 0.00
0.00 0.00 1.00
   filter: 
EDID:
00000dae4513
15160104a51d117802a705a656549b26
0c50540001010101010101010101
010101010101363680a0703820402e1e
240026a5101a242480a070382040
2e1e240026a5101a00fe0056
4b574a4380314853450a
000a4131a300100a010a20200023
BACKLIGHT: 15 (0x000f)  range:  (0,15)
Backlight: 15 (0x000f)  range:  (0,15)
Broadcast RGB:  Full
supported: Full Limited 16:2
audio:  auto
supported: off  auto on  
  1920x1080 (0x46)  138.8MHz +HSync -VSync *current +preferred
h: width  1920 start 1966 end 1996 total 2080 skew0 clock   66.7KHz
v: height 1080 start 1082 end 1086 total 1112   clock   60.0Hz
  1920x1080 (0x47)  138.5MHz +HSync -VSync
h: width  1920 start 1968 end 2000 total 2080 skew0 clock   66.6KHz
v: height 1080 start 1083 end 1088 total    clock   59.9Hz
  1920x1080 (0x48)   92.5MHz +HSync -VSync
h: width  1920 start 1966 end 1996 total 2080 skew0 clock   44.5KHz
v: height 1080 start 1082 end 1086 total 1112   clock   40.0Hz
  1680x1050 (0x49)  146.2MHz -HSync +VSync
h: width  1680 start 1784 end 1960 total 2240 skew0 clock   65.3KHz
v: height 1050 start 1053 end 1059 total 1089   clock   60.0Hz
  1680x1050 (0x4a)  119.0MHz +HSync -VSync
h: width  1680 start 1728 end 1760 total 1840 skew0 clock   64.7KHz
v: height 1050 start 1053 end 1059 total 1080   clock   59.9Hz
  1600x1024 (0x4b)  103.1MHz +HSync +VSync
h: width  1600 start 1600 end 1656 total 1664 skew0 clock   62.0KHz
v: height 1024 start 1024 end 1029 total 1030   clock   60.2Hz
  1400x1050 (0x4c)  122.0MHz +HSync +VSync
h: width  1400 start 1488 end 1640 total 1880 skew0 clock   64.9KHz
v: height 1050 start 1052 end 1064 total 1082   clock   60.0Hz
  1280x1024 (0x4d)  108.0MHz +HSync +VSync
h: width  1280 start 1328 end 1440 total 1688 skew0 clock   64.0KHz
v: height 1024 start 1025 end 1028 total 1066   clock   60.0Hz
  1440x900 (0x4e)  106.5MHz -HSync +VSync
h: width  1440 start 1520 end 1672 total 1904 skew0 clock   55.9KHz
v: height  900 start  903 end  909 total  934   clock   59.9Hz
  1280x960 (0x4f)  108.0MHz +HSync +VSync
h: width  1280 start 1376 end 1488 total 1800 skew0 clock   60.0KHz
v: height  960 start  961 end  964 total 1000   clock   60.0Hz
  1360x768 (0x50)   84.8MHz -HSync +VSync
h: width  1360 start 1432 end 1568 total 1776 skew0 clock   47.7KHz
v: height  768 start  771 end  781 total  798   clock   59.8Hz
  1360x768 (0x51)   72.0MHz +HSync -VSync
h: width  1360 start 1408 end 1440 total 1520 skew0 clock   47.4KHz
v: height  768 start  771 end  781 total  790   clock   60.0Hz
  1152x864 (0x52)   81.6MHz -HSync +VSync
h: width  1152 start 1216 end 1336 total 1520 skew0 clock   53.7KHz
v: height  864 start  865 end  868 total  895   clock   60.0Hz
  1024x768 (0x53)   65.0MHz -HSync -VSync
h: width  1024 start 1048 end 1184 total 1344 skew0 clock   48.4KHz
v: height  768 start  771 end  777 total  806   clock   60.0Hz
  800x600 (0x54)   40.0MHz +HSync +VSync
h: width   800 start  840 end  968 total 1056 skew0 clock   37.9KHz
v: height  600 start  601 end  605 total  628   clock   60.3Hz
  800x600 (0x55)   36.0MHz +HSync +VSync
h: width   800 start  824 end  896 total 1024 skew0 clock   35.2KHz
v: height  600 start  601 end  603 total  625   clock   56.2Hz
  640x480 (0x56)   25.2MHz -HSync -VSync
h: width   640 start  656 end  752 total  800 skew0 clock   31.5KHz
v: height  480 start  490 end  492 total  525   clock   59.9Hz
VGA1 disconnected (normal left inverted right x axis y axis)
Identifier: 0x43
Timestamp:  2779103
Subpixel:   unknown
Clones:
CRTCs:  0 1
Transform:  1.00 0.00 0.00
0.00 1.00

[Dx-packages] [Bug 1284767] Re: Unity fails to start with a 4K monitor attached

[Zan Lynx]

I do not remember when this changed, but at some point it started
working again. The problem now is getting occasional compiz lockups and
the driver reporting continuous page flip failed no space on device
errors.

So I cannot give you xrandr info with the monitor not working.

But here is the current uname and lspci

Linux 3.2.0-67-generic x86_64

00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor DRAM 
Controller [8086:0154] (rev 09)
Subsystem: Dell Device [1028:058b]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: agpgart-intel

00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core 
processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Dell Device [1028:058b]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-  [disabled]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee0c00c  Data: 4169
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [a4] PCI Advanced Features
AFCap: TP+ FLR+
AFCtrl: FLR-
AFStatus: TP-
Kernel driver in use: i915
Kernel modules: i915

00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset 
Family USB xHCI Host Controller [8086:1e31] (rev 04) (prog-if 30 [XHCI])
Subsystem: Dell Device [1028:058b]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, 
L1 <1us
ExtTag- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq- AuxPwr+ 
TransPend-
LnkCap: Port #1, Speed 5GT/s, Width x1, ASPM L0s L1, Latency L0 
<512ns, L1 <16us
ClockPM- Surprise- LLActRep+ BwNot-
LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- Retrain- 
CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ 
DLActive+ BWMgmt+ ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- 
Surprise-
Slot #0, PowerLimit 10.000W; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- 
LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- 
Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ 
Interlock-
Changed: MRL- PresDet- LinkState+
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- 
CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
DevCap2: Completion Timeout: Range BC, TimeoutDis+ ARIFwd-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- ARIFwd-
LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-, 
Selectable De-emphasis: -6dB
 Transmit Margin: Normal Operating Range, 
EnterModifiedCompliance- ComplianceSOS-
 Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -3.5dB
Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
Address:   Data: 
Capabilities: [90] Subsystem: Dell Device [1028:058b]
Capabilities: [a0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset 
Family USB Enhanced Host Controller #1 [8086:1e26] (rev 04) (prog-if 20 [EHCI])
Subsystem: Dell Device [1028:058b]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-

[Dx-packages] [Bug 1186181] Re: [Indicator] battery icon unreliable at low battery levels

[Daniela Ferrai]

I potential solution we've been discussing with Nick Dedekind (deadnick)
is to dynamically draw the icon so it always represents an accurate
power status without having to rely on assets. I'll provide more updates
in the next couple of days.

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

Title:
  [Indicator] battery icon unreliable at low battery levels

Status in The Power Indicator:
  Triaged
Status in Ubuntu UX bugs:
  Triaged
Status in “indicator-power” package in Ubuntu:
  Triaged

Bug description:
  Battery icon does not reliably display correct values at low battery
  levels.

  The icon works fine until you get below 30%. At 10-30% a small red
  icon should be displayed, and another icon should be displayed at
  <10%. Currently, the icon doesn't seem to change to anything smaller
  than the 40% icon.

  I have sometimes seen the red 20% icon, but it's very unreliable, and
  typically switches back to the 40% icon moments after resuming the
  phone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-power/+bug/1186181/+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 1284767] Re: Unity fails to start with a 4K monitor attached

[madbiologist]

We are going to need some more info.

Can you please copy and paste the output of uname -srm

Can you also please attach the output of lspci -vvnn

Finally, please attach the output of xrandr --verbose when the monitor
does not work after booting with it connected and also when it does work
after hotplugging it.

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

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

Title:
  Unity fails to start with a 4K monitor attached

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

Bug description:
  I am running Ubuntu 12.04 LTS on a Dell XPS 13. This is an Intel
  i7-3537U integrated graphics setup.

  When I boot and log in and THEN attach a 4K monitor via DisplayPort
  everything works well.

  But when I attach the monitor and then boot, after logging in, Unity
  fails to start. It seems to be unable to allocate a OpenGL surface.

  Why the difference between startup and hotplug?

  [zlynx@slicer 11:29:36 (0) ~]
  $ unity -v --debug
  unity-panel-service: no process found
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  /usr/bin/compiz (core) - Debug: Could not stat() file 
/home/zlynx/.compiz-1/plugins/libcore.so : No such file or directory
  /usr/bin/compiz (core) - Debug: Could not stat() file 
/usr/lib/compiz/libcore.so : No such file or directory
  [New Thread 0x73b77700 (LWP 5114)]
  /usr/bin/compiz (core) - Debug: pending request:d
  /usr/bin/compiz (core) - Debug: - event serial: 1286
  /usr/bin/compiz (core) - Debug: - event window 0x3400090
  /usr/bin/compiz (core) - Debug: - x: 0 y: 0 width: 0 height: 0 border: 0, 
sibling: 0x0
  /usr/bin/compiz (core) - Debug: pending request:
  /usr/bin/compiz (core) - Debug: - event serial: 1354
  /usr/bin/compiz (core) - Debug: - event window 0x3400093
  /usr/bin/compiz (core) - Debug: - x: 1920 y: 0 width: 2160 height: 3840 
border: 0, sibling: 0x3400090
  /usr/bin/compiz (core) - Debug: pending request:
  /usr/bin/compiz (core) - Debug: - event serial: 1431
  /usr/bin/compiz (core) - Debug: - event window 0x3400096
  /usr/bin/compiz (core) - Debug: - x: 0 y: 0 width: 722 height: 457 border: 0, 
sibling: 0x3400093
  /usr/bin/compiz (core) - Debug: Could not stat() file 
/home/zlynx/.compiz-1/plugins/libccp.so : No such file or directory
  Checking if settings need to be migrated ...no
  Checking if internal files need to be migrated ...no
  Backend : gconf
  Integration : true
  Profile : unity
  Adding plugins
  Initializing core options...done
  /usr/bin/compiz (core) - Debug: Could not stat() file 
/home/zlynx/.compiz-1/plugins/libcomposite.so : No such file or directory
  Initializing composite options...done
  /usr/bin/compiz (core) - Debug: Could not stat() file 
/home/zlynx/.compiz-1/plugins/libopengl.so : No such file or directory
  Initializing opengl options...done
  /usr/bin/compiz (core) - Debug: Could not stat() file 
/home/zlynx/.compiz-1/plugins/libcompiztoolbox.so : No such file or directory
  /usr/bin/compiz (core) - Debug: Could not stat() file 
/home/zlynx/.compiz-1/plugins/libdecor.so : No such file or directory
  Initializing decor options...done
  /usr/bin/compiz (core) - Debug: Could not stat() file 
/home/zlynx/.compiz-1/plugins/libvpswitch.so : No such file or directory
  Initializing vpswitch options...done
  /usr/bin/compiz (core) - Debug: Could not stat() file 
/home/zlynx/.compiz-1/plugins/libsnap.so : No such file or directory
  Initializing snap options...done
  /usr/bin/compiz (core) - Debug: Could not stat() file 
/home/zlynx/.compiz-1/plugins/libmousepoll.so : No such file or directory
  Initializing mousepoll options...done
  /usr/bin/compiz (core) - Debug: Could not stat() file 
/home/zlynx/.compiz-1/plugins/libresize.so : No such file or directory
  Initializing resize options...done
  /usr/bin/compiz (core) - Debug: Could not stat() file 
/home/zlynx/.compiz-1/plugins/libplace.so : No such file or directory
  Initializing place options...done
  /usr/bin/compiz (core) - Debug: Could not stat() file 
/home/zlynx/.compiz-1/plugins/libmove.so : No such file or directory
  Initializing move options...done
  /usr/bin/compiz (core) - Debug: Could not stat() file 
/home/zlynx/.compiz-1/plugins/libwall.so : No such file or directory
  Initializing wall options...done
  /usr/bin/compiz (core) - Debug: Could not stat() file 
/home/zlynx/.compiz-1/plugins/libgrid.so : No such file or directory
  Initializing grid options...done
  /usr/bin/compiz (core) - Debug: Could not stat() file 
/home/zlynx/.compiz-1/plugins/libregex.so : No such file or directory
  /usr/bin/compiz (core) - Debug: Could not stat() file 
/home/zlynx/.compiz-1/plugins/libimgpng.so : No such file or directory
  /usr/bin/compiz (core) - Debug: Could not 

[Dx-packages] [Bug 1284767] Re: Unity fails to start with a 4K monitor attached

[madbiologist]

** Tags added: precise

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

Title:
  Unity fails to start with a 4K monitor attached

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

Bug description:
  I am running Ubuntu 12.04 LTS on a Dell XPS 13. This is an Intel
  i7-3537U integrated graphics setup.

  When I boot and log in and THEN attach a 4K monitor via DisplayPort
  everything works well.

  But when I attach the monitor and then boot, after logging in, Unity
  fails to start. It seems to be unable to allocate a OpenGL surface.

  Why the difference between startup and hotplug?

  [zlynx@slicer 11:29:36 (0) ~]
  $ unity -v --debug
  unity-panel-service: no process found
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  /usr/bin/compiz (core) - Debug: Could not stat() file 
/home/zlynx/.compiz-1/plugins/libcore.so : No such file or directory
  /usr/bin/compiz (core) - Debug: Could not stat() file 
/usr/lib/compiz/libcore.so : No such file or directory
  [New Thread 0x73b77700 (LWP 5114)]
  /usr/bin/compiz (core) - Debug: pending request:d
  /usr/bin/compiz (core) - Debug: - event serial: 1286
  /usr/bin/compiz (core) - Debug: - event window 0x3400090
  /usr/bin/compiz (core) - Debug: - x: 0 y: 0 width: 0 height: 0 border: 0, 
sibling: 0x0
  /usr/bin/compiz (core) - Debug: pending request:
  /usr/bin/compiz (core) - Debug: - event serial: 1354
  /usr/bin/compiz (core) - Debug: - event window 0x3400093
  /usr/bin/compiz (core) - Debug: - x: 1920 y: 0 width: 2160 height: 3840 
border: 0, sibling: 0x3400090
  /usr/bin/compiz (core) - Debug: pending request:
  /usr/bin/compiz (core) - Debug: - event serial: 1431
  /usr/bin/compiz (core) - Debug: - event window 0x3400096
  /usr/bin/compiz (core) - Debug: - x: 0 y: 0 width: 722 height: 457 border: 0, 
sibling: 0x3400093
  /usr/bin/compiz (core) - Debug: Could not stat() file 
/home/zlynx/.compiz-1/plugins/libccp.so : No such file or directory
  Checking if settings need to be migrated ...no
  Checking if internal files need to be migrated ...no
  Backend : gconf
  Integration : true
  Profile : unity
  Adding plugins
  Initializing core options...done
  /usr/bin/compiz (core) - Debug: Could not stat() file 
/home/zlynx/.compiz-1/plugins/libcomposite.so : No such file or directory
  Initializing composite options...done
  /usr/bin/compiz (core) - Debug: Could not stat() file 
/home/zlynx/.compiz-1/plugins/libopengl.so : No such file or directory
  Initializing opengl options...done
  /usr/bin/compiz (core) - Debug: Could not stat() file 
/home/zlynx/.compiz-1/plugins/libcompiztoolbox.so : No such file or directory
  /usr/bin/compiz (core) - Debug: Could not stat() file 
/home/zlynx/.compiz-1/plugins/libdecor.so : No such file or directory
  Initializing decor options...done
  /usr/bin/compiz (core) - Debug: Could not stat() file 
/home/zlynx/.compiz-1/plugins/libvpswitch.so : No such file or directory
  Initializing vpswitch options...done
  /usr/bin/compiz (core) - Debug: Could not stat() file 
/home/zlynx/.compiz-1/plugins/libsnap.so : No such file or directory
  Initializing snap options...done
  /usr/bin/compiz (core) - Debug: Could not stat() file 
/home/zlynx/.compiz-1/plugins/libmousepoll.so : No such file or directory
  Initializing mousepoll options...done
  /usr/bin/compiz (core) - Debug: Could not stat() file 
/home/zlynx/.compiz-1/plugins/libresize.so : No such file or directory
  Initializing resize options...done
  /usr/bin/compiz (core) - Debug: Could not stat() file 
/home/zlynx/.compiz-1/plugins/libplace.so : No such file or directory
  Initializing place options...done
  /usr/bin/compiz (core) - Debug: Could not stat() file 
/home/zlynx/.compiz-1/plugins/libmove.so : No such file or directory
  Initializing move options...done
  /usr/bin/compiz (core) - Debug: Could not stat() file 
/home/zlynx/.compiz-1/plugins/libwall.so : No such file or directory
  Initializing wall options...done
  /usr/bin/compiz (core) - Debug: Could not stat() file 
/home/zlynx/.compiz-1/plugins/libgrid.so : No such file or directory
  Initializing grid options...done
  /usr/bin/compiz (core) - Debug: Could not stat() file 
/home/zlynx/.compiz-1/plugins/libregex.so : No such file or directory
  /usr/bin/compiz (core) - Debug: Could not stat() file 
/home/zlynx/.compiz-1/plugins/libimgpng.so : No such file or directory
  /usr/bin/compiz (core) - Debug: Could not stat() file 
/home/zlynx/.compiz-1/plugins/libsession.so : No such file or directory
  Initializing session options...done
  /usr/bin/compiz (core) - Debug: Could not stat() file 
/home/zlynx/.compiz-1/plugins/libgnomecompat.so : No such file or directory
  Initializing gnomecompat options...done
  /usr/bin/compiz (core) - Debug: Could not stat() file 
/home/z

[Dx-packages] [Bug 1186181] Re: [Indicator] battery icon unreliable at low battery levels

[Daniela Ferrai]

I would agree with Matthew, it seems this is not a UX bug, rather a
implementation issue. Assets and specifications have been provided
(please view https://wiki.ubuntu.com/Power#Icons).

** Changed in: ubuntu-ux
 Assignee: Daniela Ferrai (dferrai) => Matthew Paul Thomas (mpt)

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

Title:
  [Indicator] battery icon unreliable at low battery levels

Status in The Power Indicator:
  Triaged
Status in Ubuntu UX bugs:
  Triaged
Status in “indicator-power” package in Ubuntu:
  Triaged

Bug description:
  Battery icon does not reliably display correct values at low battery
  levels.

  The icon works fine until you get below 30%. At 10-30% a small red
  icon should be displayed, and another icon should be displayed at
  <10%. Currently, the icon doesn't seem to change to anything smaller
  than the 40% icon.

  I have sometimes seen the red 20% icon, but it's very unreliable, and
  typically switches back to the 40% icon moments after resuming the
  phone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-power/+bug/1186181/+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 1186181] Re: [Indicator] battery icon unreliable at low battery levels

[Charles Kerr]

** Changed in: indicator-power
 Assignee: John Lea (johnlea) => Charles Kerr (charlesk)

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

Title:
  [Indicator] battery icon unreliable at low battery levels

Status in The Power Indicator:
  Triaged
Status in Ubuntu UX bugs:
  Fix Committed
Status in “indicator-power” package in Ubuntu:
  Triaged

Bug description:
  Battery icon does not reliably display correct values at low battery
  levels.

  The icon works fine until you get below 30%. At 10-30% a small red
  icon should be displayed, and another icon should be displayed at
  <10%. Currently, the icon doesn't seem to change to anything smaller
  than the 40% icon.

  I have sometimes seen the red 20% icon, but it's very unreliable, and
  typically switches back to the 40% icon moments after resuming the
  phone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-power/+bug/1186181/+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 1186181] Re: battery icon unreliable at low battery levels

[John Lea]

** Also affects: ubuntu-ux
   Importance: Undecided
   Status: New

** Summary changed:

- battery icon unreliable at low battery levels
+ [Indicator] battery icon unreliable at low battery levels

** Changed in: ubuntu-ux
 Assignee: (unassigned) => Daniela Ferrai (dferrai)

** Changed in: ubuntu-ux
   Importance: Undecided => High

** Changed in: ubuntu-ux
   Status: New => Triaged

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

Title:
  [Indicator] battery icon unreliable at low battery levels

Status in The Power Indicator:
  Triaged
Status in Ubuntu UX bugs:
  Triaged
Status in “indicator-power” package in Ubuntu:
  Triaged

Bug description:
  Battery icon does not reliably display correct values at low battery
  levels.

  The icon works fine until you get below 30%. At 10-30% a small red
  icon should be displayed, and another icon should be displayed at
  <10%. Currently, the icon doesn't seem to change to anything smaller
  than the 40% icon.

  I have sometimes seen the red 20% icon, but it's very unreliable, and
  typically switches back to the 40% icon moments after resuming the
  phone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-power/+bug/1186181/+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 1186181] Re: battery icon unreliable at low battery levels

[Charles Kerr]

** Changed in: indicator-power
 Assignee: Matthew Paul Thomas (mpt) => John Lea (johnlea)

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

Title:
  battery icon unreliable at low battery levels

Status in The Power Indicator:
  Triaged
Status in “indicator-power” package in Ubuntu:
  Triaged

Bug description:
  Battery icon does not reliably display correct values at low battery
  levels.

  The icon works fine until you get below 30%. At 10-30% a small red
  icon should be displayed, and another icon should be displayed at
  <10%. Currently, the icon doesn't seem to change to anything smaller
  than the 40% icon.

  I have sometimes seen the red 20% icon, but it's very unreliable, and
  typically switches back to the 40% icon moments after resuming the
  phone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-power/+bug/1186181/+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 1349128] Re: Ubuntu 14.04 login screen doesn't accept keyboard input (until using indicators)

[Sander Jonkers]

When not accepting/showing input from the keyboard, there is the usual
vertical blinking line in the password box (so: 'showing' it is
accepting input there), with the word "password" in the background of
that password box.

Would it help if I post a picture of video of what goes (or: doesn't go)
on?

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

Title:
  Ubuntu 14.04 login screen doesn't accept keyboard input (until using
  indicators)

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

Bug description:
  Ubuntu 14.04 login screen doesn't accept keyboard input in the
  password box after my system has resumed from a sleep (=lid opening),
  so I can't relogin anymore

  Excpected behaviour: the login screen should accept keyboard input and
  show them as stars in the password box.

  Workaround: click on "switch user" in the upper right corner, after
  which keyboard input is accepted again.

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

  System is fully updated. Problem started to happen one or two weeks
  ago, so around mid July 2014.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1349128/+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 1338604] Re: indicator shows 25% charge but phone runs out of battery

[Charles Kerr]

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

** This bug has been marked a duplicate of bug 1186181
   battery icon unreliable at low battery levels

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

Title:
  indicator shows 25% charge but phone runs out of battery

Status in “indicator-power” package in Ubuntu:
  Confirmed
Status in “powerd” package in Ubuntu:
  Incomplete

Bug description:
  build 116 on Nexus 4

  - Use the phone for a while when not plugged in
  - After extended use or being suspended, indicator shows about 25% charge 
(still white)
  - Then phone completely dies, battery is empty as you can't turn it back on 
unless plugged in

  Expected results:
  indicator should turn red when battery level critical
  user should be prompted that battery level critical

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1338604/+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 1186181] Re: battery icon unreliable at low battery levels

[Charles Kerr]

Promoting ticket to high based on bug #1338604. I'm not sure how long
mpt is out; maybe another designer should look at this.

** Changed in: indicator-power
   Importance: Medium => High

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

Title:
  battery icon unreliable at low battery levels

Status in The Power Indicator:
  Triaged
Status in “indicator-power” package in Ubuntu:
  Triaged

Bug description:
  Battery icon does not reliably display correct values at low battery
  levels.

  The icon works fine until you get below 30%. At 10-30% a small red
  icon should be displayed, and another icon should be displayed at
  <10%. Currently, the icon doesn't seem to change to anything smaller
  than the 40% icon.

  I have sometimes seen the red 20% icon, but it's very unreliable, and
  typically switches back to the 40% icon moments after resuming the
  phone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-power/+bug/1186181/+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 1338604] Re: indicator shows 25% charge but phone runs out of battery

[Charles Kerr]

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

The icon issue is described in
 which is currently blocked by design.

The notifications are covered in bug #1296431,  which has an approved
fix waiting to land.

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

Title:
  indicator shows 25% charge but phone runs out of battery

Status in “indicator-power” package in Ubuntu:
  Confirmed
Status in “powerd” package in Ubuntu:
  Incomplete

Bug description:
  build 116 on Nexus 4

  - Use the phone for a while when not plugged in
  - After extended use or being suspended, indicator shows about 25% charge 
(still white)
  - Then phone completely dies, battery is empty as you can't turn it back on 
unless plugged in

  Expected results:
  indicator should turn red when battery level critical
  user should be prompted that battery level critical

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1338604/+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 1340550] Re: time spend on screen is way to much

[Matthew Paul Thomas]

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

** This bug has been marked a duplicate of bug 462642
   Notifications should disappear sooner

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

Title:
  time spend on screen is way to much

Status in “notify-osd” package in Ubuntu:
  New

Bug description:
  We need to reduce time, that notification spends on screen, to like 3 
seconds, because current time (10 seconds or so) is wa to much...
  Also this notify-osd feels broken, it needs configuration tools to change 
various parameters like time, also it needs a way to know, if it is a system 
notification or a notification from third party program, and a way to disable 
notifications at all or part of them(system / third party).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1340550/+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 1331873] Re: the "Ubuntu Help" should be "Ubuntu Kylin Help"

[Aron Xu]

ubuntukylin-default-settings/1.2.0 is updated in utopic to set NAME to
Ubuntu Kylin in /etc/os-release, please verify if this works in an up-
to-date system and close the UbuntuKylin task if appropriate.

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

Title:
  the "Ubuntu Help" should be "Ubuntu Kylin Help"

Status in The Session Menu:
  Fix Released
Status in Ubuntu Kylin:
  Fix Committed
Status in “indicator-session” package in Ubuntu:
  Fix Released

Bug description:
  the "Ubuntu Help"should be "Ubuntu Kuliy Help" in the indicator ,since
  this is ubuntuKylin system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-session/+bug/1331873/+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 1208019] Re: Eclipse menus doesn't show up in Trusty

[William Hua]

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Fix Released

** Changed in: gtk+3.0 (Ubuntu Trusty)
   Status: New => Confirmed

** Changed in: unity-gtk-module (Ubuntu Trusty)
   Status: New => Confirmed

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

Title:
  Eclipse menus doesn't show up in Trusty

Status in Eclipse:
  Unknown
Status in GTK+ GUI Toolkit:
  Fix Released
Status in Unity GTK+ module:
  Fix Released
Status in “gtk+3.0” package in Ubuntu:
  Fix Released
Status in “unity-gtk-module” package in Ubuntu:
  Fix Released
Status in “gtk+3.0” source package in Trusty:
  Confirmed
Status in “unity-gtk-module” source package in Trusty:
  Confirmed

Bug description:
  [Impact]

  Switching tabs between open source files with different file types in
  Eclipse causes the Source and Refactor menus to be empty in the global
  menu bar under Unity.

  This is a severe usability problem for many Eclipse users. The fix
  proposed has been available in a PPA and is well-tested.

  [Test Case]

  1. Open a new project in Eclipse.
  2. Open two files: one with a .java extension, another with a .txt extension.
  3. Switch between the .java file and the .txt file and back again.
  4. Open the Source or Refactor menu in the Unity global menu bar.

  Expected result: menus with menu items
  Actual result: empty menus for both

  [Regression Potential]

  The fix involves changes to both gtk and unity-gtk-module.

  The changes to gtk are minimal and only involve the reversal of a pair
  of signal emissions, in a part of the code (GtkMenuTracker) which is
  normally used by desktop environments, not typical user applications.
  Therefore regression potential for the gtk update is unlikely.

  The changes to unity-gtk-module involve emitting show and hide signals
  where they were none before has some regression potential for
  applications that are explicitly watching for when their menus are
  opening and closing. But this is rare for applications to do, and we
  likely would have already received bug reports for those that do.
  Being completely sure would require extensive testing across all gtk
  apps though.

  Both changes together have been available as a PPA, thoroughly tested
  for quite some time now.

  [Other Info]

  The changes to unity-gtk-module depend on the changes to gtk, so both
  must be tested in simultaneity. Suggested to upload both to trusty-
  proposed at the same time.

  Original bug report follows:

  === %< ===

  
  HOW TO REPRODUCE
  

  1. Run Eclipse, Gimp or Inkscape.
  2. Move the cursor to the top of the screen.
  3. Click on any of the menu items (File, Edit, Navigate, ...)

  **
  EXPECTED BEHAVIOUR
  **

  - The content of the submenus show up.

  **
  REAL BEHAVIOUR
  **

  - Only the top-level headers are available.
  - Nothing happens when clicking on them
  - They don't show up in the HUD either.

  ***
  WORK-AROUND
  ***

  To modify "/usr/share/applications/eclipse.desktop" to look like this:

  [Desktop Entry]
  Type=Application
  Name=Eclipse
  Comment=Eclipse Integrated Development Environment
  Icon=eclipse
  Exec=env UBUNTU_MENUPROXY= eclipse
  Terminal=false
  Categories=Development;IDE;Java;

  
  RELEVANT DETAILS
  

  - Doesn't affect Ubuntu releases prior to 13.10.

  **
  TECHNICAL INFO
  **

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: eclipse 3.8.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
  Uname: Linux 3.10.0-6-generic i686
  ApportVersion: 2.11-0ubuntu1
  Architecture: i386
  Date: Sat Aug  3 17:03:55 2013
  InstallationDate: Installed on 2013-07-08 (25 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130708)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: eclipse
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/eclipse/+bug/1208019/+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 1208019] Re: Eclipse menus doesn't show up in Trusty

[Iain Lane]

** Also affects: gtk+3.0 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: unity-gtk-module (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

Title:
  Eclipse menus doesn't show up in Trusty

Status in Eclipse:
  Unknown
Status in GTK+ GUI Toolkit:
  Fix Released
Status in Unity GTK+ module:
  Fix Released
Status in “gtk+3.0” package in Ubuntu:
  Fix Released
Status in “unity-gtk-module” package in Ubuntu:
  Fix Released
Status in “gtk+3.0” source package in Trusty:
  Confirmed
Status in “unity-gtk-module” source package in Trusty:
  Confirmed

Bug description:
  [Impact]

  Switching tabs between open source files with different file types in
  Eclipse causes the Source and Refactor menus to be empty in the global
  menu bar under Unity.

  This is a severe usability problem for many Eclipse users. The fix
  proposed has been available in a PPA and is well-tested.

  [Test Case]

  1. Open a new project in Eclipse.
  2. Open two files: one with a .java extension, another with a .txt extension.
  3. Switch between the .java file and the .txt file and back again.
  4. Open the Source or Refactor menu in the Unity global menu bar.

  Expected result: menus with menu items
  Actual result: empty menus for both

  [Regression Potential]

  The fix involves changes to both gtk and unity-gtk-module.

  The changes to gtk are minimal and only involve the reversal of a pair
  of signal emissions, in a part of the code (GtkMenuTracker) which is
  normally used by desktop environments, not typical user applications.
  Therefore regression potential for the gtk update is unlikely.

  The changes to unity-gtk-module involve emitting show and hide signals
  where they were none before has some regression potential for
  applications that are explicitly watching for when their menus are
  opening and closing. But this is rare for applications to do, and we
  likely would have already received bug reports for those that do.
  Being completely sure would require extensive testing across all gtk
  apps though.

  Both changes together have been available as a PPA, thoroughly tested
  for quite some time now.

  [Other Info]

  The changes to unity-gtk-module depend on the changes to gtk, so both
  must be tested in simultaneity. Suggested to upload both to trusty-
  proposed at the same time.

  Original bug report follows:

  === %< ===

  
  HOW TO REPRODUCE
  

  1. Run Eclipse, Gimp or Inkscape.
  2. Move the cursor to the top of the screen.
  3. Click on any of the menu items (File, Edit, Navigate, ...)

  **
  EXPECTED BEHAVIOUR
  **

  - The content of the submenus show up.

  **
  REAL BEHAVIOUR
  **

  - Only the top-level headers are available.
  - Nothing happens when clicking on them
  - They don't show up in the HUD either.

  ***
  WORK-AROUND
  ***

  To modify "/usr/share/applications/eclipse.desktop" to look like this:

  [Desktop Entry]
  Type=Application
  Name=Eclipse
  Comment=Eclipse Integrated Development Environment
  Icon=eclipse
  Exec=env UBUNTU_MENUPROXY= eclipse
  Terminal=false
  Categories=Development;IDE;Java;

  
  RELEVANT DETAILS
  

  - Doesn't affect Ubuntu releases prior to 13.10.

  **
  TECHNICAL INFO
  **

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: eclipse 3.8.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
  Uname: Linux 3.10.0-6-generic i686
  ApportVersion: 2.11-0ubuntu1
  Architecture: i386
  Date: Sat Aug  3 17:03:55 2013
  InstallationDate: Installed on 2013-07-08 (25 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130708)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: eclipse
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/eclipse/+bug/1208019/+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 1208019] Re: Eclipse menus doesn't show up in Saucy

[William Hua]

** Branch linked: lp:~attente/gtk/1208019

** Summary changed:

- Eclipse menus doesn't show up in Saucy
+ Eclipse menus doesn't show up in Trusty

** Changed in: unity-gtk-module
   Status: In Progress => Fix Released

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

Title:
  Eclipse menus doesn't show up in Trusty

Status in Eclipse:
  Unknown
Status in GTK+ GUI Toolkit:
  Fix Released
Status in Unity GTK+ module:
  Fix Released
Status in “gtk+3.0” package in Ubuntu:
  Fix Released
Status in “unity-gtk-module” package in Ubuntu:
  Fix Released
Status in “gtk+3.0” source package in Trusty:
  Confirmed
Status in “unity-gtk-module” source package in Trusty:
  Confirmed

Bug description:
  [Impact]

  Switching tabs between open source files with different file types in
  Eclipse causes the Source and Refactor menus to be empty in the global
  menu bar under Unity.

  This is a severe usability problem for many Eclipse users. The fix
  proposed has been available in a PPA and is well-tested.

  [Test Case]

  1. Open a new project in Eclipse.
  2. Open two files: one with a .java extension, another with a .txt extension.
  3. Switch between the .java file and the .txt file and back again.
  4. Open the Source or Refactor menu in the Unity global menu bar.

  Expected result: menus with menu items
  Actual result: empty menus for both

  [Regression Potential]

  The fix involves changes to both gtk and unity-gtk-module.

  The changes to gtk are minimal and only involve the reversal of a pair
  of signal emissions, in a part of the code (GtkMenuTracker) which is
  normally used by desktop environments, not typical user applications.
  Therefore regression potential for the gtk update is unlikely.

  The changes to unity-gtk-module involve emitting show and hide signals
  where they were none before has some regression potential for
  applications that are explicitly watching for when their menus are
  opening and closing. But this is rare for applications to do, and we
  likely would have already received bug reports for those that do.
  Being completely sure would require extensive testing across all gtk
  apps though.

  Both changes together have been available as a PPA, thoroughly tested
  for quite some time now.

  [Other Info]

  The changes to unity-gtk-module depend on the changes to gtk, so both
  must be tested in simultaneity. Suggested to upload both to trusty-
  proposed at the same time.

  Original bug report follows:

  === %< ===

  
  HOW TO REPRODUCE
  

  1. Run Eclipse, Gimp or Inkscape.
  2. Move the cursor to the top of the screen.
  3. Click on any of the menu items (File, Edit, Navigate, ...)

  **
  EXPECTED BEHAVIOUR
  **

  - The content of the submenus show up.

  **
  REAL BEHAVIOUR
  **

  - Only the top-level headers are available.
  - Nothing happens when clicking on them
  - They don't show up in the HUD either.

  ***
  WORK-AROUND
  ***

  To modify "/usr/share/applications/eclipse.desktop" to look like this:

  [Desktop Entry]
  Type=Application
  Name=Eclipse
  Comment=Eclipse Integrated Development Environment
  Icon=eclipse
  Exec=env UBUNTU_MENUPROXY= eclipse
  Terminal=false
  Categories=Development;IDE;Java;

  
  RELEVANT DETAILS
  

  - Doesn't affect Ubuntu releases prior to 13.10.

  **
  TECHNICAL INFO
  **

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: eclipse 3.8.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
  Uname: Linux 3.10.0-6-generic i686
  ApportVersion: 2.11-0ubuntu1
  Architecture: i386
  Date: Sat Aug  3 17:03:55 2013
  InstallationDate: Installed on 2013-07-08 (25 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130708)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: eclipse
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/eclipse/+bug/1208019/+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 1301776] Re: Update manager is really small and not resizeable

[Launchpad Bug Tracker]

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

** Changed in: unity (Ubuntu Trusty)
   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/1301776

Title:
  Update manager is really small and not resizeable

Status in Unity:
  In Progress
Status in Unity 7.2 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  In Progress
Status in “update-manager” package in Ubuntu:
  Invalid
Status in “compiz” source package in Trusty:
  Triaged
Status in “unity” source package in Trusty:
  Confirmed
Status in “update-manager” source package in Trusty:
  Invalid

Bug description:
  update-manager 1:0.196.9, Ubuntu Trusty

  Update manager's window, and especially its fields inside the window, are way 
too small and also it's not resizeable, making it almost useless at least on my 
HiDPI screen (3200 x 1800).
  https://launchpadlibrarian.net/171657786/update-manager-is-small.png

  : "The Updates
  Available window should be manually resizable only when it is in this
  expanded state."

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1301776/+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 1349128] Re: Ubuntu 14.04 login screen doesn't accept keyboard input (until using indicators)

[Treviño]

When this happen, is any input field shown in the lockscreen or only the
username and a darker rounded rectangle is?

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

Title:
  Ubuntu 14.04 login screen doesn't accept keyboard input (until using
  indicators)

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

Bug description:
  Ubuntu 14.04 login screen doesn't accept keyboard input in the
  password box after my system has resumed from a sleep (=lid opening),
  so I can't relogin anymore

  Excpected behaviour: the login screen should accept keyboard input and
  show them as stars in the password box.

  Workaround: click on "switch user" in the upper right corner, after
  which keyboard input is accepted again.

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

  System is fully updated. Problem started to happen one or two weeks
  ago, so around mid July 2014.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1349128/+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 1349128] Re: Ubuntu 14.04 login screen doesn't accept keyboard input

[Sebastien Bacher]

seems like the issue is rather unity/the lockscreen, reassigning there
(setting the bug as confirmed, Didier had that issue as well on trusty)

** Package changed: lightdm (Ubuntu) => unity (Ubuntu)

** Tags added: lockscreen

** Summary changed:

- Ubuntu 14.04 login screen doesn't accept keyboard input
+ Ubuntu 14.04 login screen doesn't accept keyboard input (until using 
indicators=

** Summary changed:

- Ubuntu 14.04 login screen doesn't accept keyboard input (until using 
indicators=
+ Ubuntu 14.04 login screen doesn't accept keyboard input (until using 
indicators)

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

** Also affects: unity
   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/1349128

Title:
  Ubuntu 14.04 login screen doesn't accept keyboard input (until using
  indicators)

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

Bug description:
  Ubuntu 14.04 login screen doesn't accept keyboard input in the
  password box after my system has resumed from a sleep (=lid opening),
  so I can't relogin anymore

  Excpected behaviour: the login screen should accept keyboard input and
  show them as stars in the password box.

  Workaround: click on "switch user" in the upper right corner, after
  which keyboard input is accepted again.

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

  System is fully updated. Problem started to happen one or two weeks
  ago, so around mid July 2014.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1349128/+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 1349128] [NEW] Ubuntu 14.04 login screen doesn't accept keyboard input

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Ubuntu 14.04 login screen doesn't accept keyboard input in the password
box after my system has resumed from a sleep (=lid opening), so I can't
relogin anymore

Excpected behaviour: the login screen should accept keyboard input and
show them as stars in the password box.

Workaround: click on "switch user" in the upper right corner, after
which keyboard input is accepted again.

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

System is fully updated. Problem started to happen one or two weeks ago,
so around mid July 2014.

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


** Tags: bot-comment trusty
-- 
Ubuntu 14.04 login screen doesn't accept keyboard input
https://bugs.launchpad.net/bugs/1349128
You received this bug notification because you are a member of DX Packages, 
which is subscribed to unity in Ubuntu.

-- 
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 1281806] Re: Alt-Tab switcher regularly goes into "flicker loop of death" or just hangs

[Nathaniel W. Turner]

Marco, sorry for not following up. I reluctantly stopped using Unity
awhile back because it was too buggy (and I couldn't get any work done).
Hopefully you've been able to reproduce this.

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

Title:
  Alt-Tab switcher regularly goes into "flicker loop of death" or just
  hangs

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

Bug description:
  Recently when doing Alt-Tab (and Alt-`) to switch between windows, the
  rectangle display showing the icons for all the applications and
  windows will suddenly start flickering rapidly and the whole X
  sessions will become unresponsive to keypresses and mouse actions.
  Sometimes instead of flickering, the Alt-Tab display will simply fail
  to appear and the same unresponsive X session results.

  This seems to happen very frequently during the course of a day. When
  it happens, my only recourse is to press Ctrl-Alt-F2 to get a text
  console, log in, and run "killall compiz" and then "DISPLAY=:0
  metacity" to kill the hung window manager and start a new one. (I
  tried running "DISPLAY=:0 compiz" from VT2, but that doesn't seem to
  start compiz in a fully functional manner.)

  I'm reporting this from a system with an NVidia card, but I experience
  the same thing on another system using an ATI "Radeon HD 7970/R9 280X"
  card, so I don't think it's video-driver specific.

  Needless to say, this makes Unity pretty hard to use effectively.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140217-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.117  Tue Nov 26 21:25:36 
PST 2013
   GCC version:  gcc version 4.8.2 (Ubuntu/Linaro 4.8.2-14ubuntu4)
  .tmp.unity.support.test.0:

  ApportVersion: 2.13.2-0ubuntu4
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Feb 18 15:24:16 2014
  DistUpgraded: 2014-01-22 19:30:50,196 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-304-updates, 304.117, 3.11.0-15-generic, x86_64: installed
   nvidia-304-updates, 304.117, 3.13.0-7-generic, x86_64: installed
   nvidia-304-updates, 304.117, 3.13.0-8-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   NVIDIA Corporation G73 [GeForce 7600 GT] [10de:0391] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: BFG Tech Device [19f1:201f]
  JockeyStatus:
   kmod:nvidia_173 - NVIDIA legacy binary driver - version 173.14.39 
(Proprietary, Disabled, Not in use)
   kmod:nvidia_304_updates - nvidia_304_updates (Proprietary, Enabled, Not in 
use)
   kmod:nvidia_304 - NVIDIA legacy binary driver - version 304.117 
(Proprietary, Disabled, Not in use)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-8-generic 
root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-01-23 (26 days ago)
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: WBIBX10J.86A.0336.2012.0626.0141
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DP55WB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE64798-207
  dmi.chassis.type: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrWBIBX10J.86A.0336.2012.0626.0141:bd06/26/2012:svn:pn:pvr:rvnIntelCorporation:rnDP55WB:rvrAAE64798-207:cvn:ct2:cvr:
  drirc:
   
   
  version.compiz: compiz 1:0.9.11+14.04.20140217-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6
  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-1ubuntu2
  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

[Dx-packages] [Bug 1349412] Re: Sound indicator missing

[Jason Hobbs]

blah - the "show volume in menu bar" checkbox was unchecked.

** Changed in: unity (Ubuntu)
   Status: New => 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/1349412

Title:
  Sound indicator missing

Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  The sound indicator icon is missing from the bar on the top of my
  screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-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 Jul 28 14:09:52 2014
  InstallationDate: Installed on 2014-06-29 (28 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/unity/+bug/1349412/+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 1349412] [NEW] Sound indicator missing

[Jason Hobbs]

Public bug reported:

The sound indicator icon is missing from the bar on the top of my
screen.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.2+14.04.20140714-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-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 Jul 28 14:09:52 2014
InstallationDate: Installed on 2014-06-29 (28 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Sound indicator missing

Status in “unity” package in Ubuntu:
  New

Bug description:
  The sound indicator icon is missing from the bar on the top of my
  screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-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 Jul 28 14:09:52 2014
  InstallationDate: Installed on 2014-06-29 (28 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/unity/+bug/1349412/+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 1177713] Re: Unity: Name of Guest account not internationalized

[Gunnar Hjalmarsson]

** Changed in: ubuntu-translations
   Status: Triaged => Fix Released

** Changed in: unity
   Status: Confirmed => Fix Released

** No longer affects: unity (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/1177713

Title:
  Unity: Name of Guest account not internationalized

Status in Ubuntu Translations:
  Fix Released
Status in Unity:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:

  Login on a guest session
  Click on logout from guest session

  Result:

  There is a dialog, asking whether you're sure to log out. "Auf
  Wiedersehen, Guest. Sind Sie sicher, dass sie alle Programme schließen
  und sich von Ihrem Konto abmelden möchten?"

  In this string "Guest" is not translated to "Gast".

  Using Ubuntu 13.04
  Locale: German, Germany

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1177713/+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 1326909] Re: un-installable dependency for i386 version on 64-bit pc

[Fabio Porcedda]

As a temporary workaround i used this commands

  apt-get download overlay-scrollbar-gtk2:i386
  sudo dpkg -i --force-depends  overlay-scrollbar-gtk2*.deb

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

Title:
  un-installable dependency for i386 version on 64-bit pc

Status in “overlay-scrollbar” package in Ubuntu:
  Confirmed

Bug description:
  Synaptic does not let me install  overlay-scrollbar-gtk2:i386

  
  below is the error i get on usin aptitude:

  The following packages have unmet dependencies:
   overlay-scrollbar-gtk2:i386 : Depends: overlay-scrollbar:i386 which is a 
virtual package.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: overlay-scrollbar 0.2.16+r359+14.04.20131129-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Thu Jun  5 23:24:28 2014
  InstallationDate: Installed on 2013-11-09 (208 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageArchitecture: all
  SourcePackage: overlay-scrollbar
  UpgradeStatus: Upgraded to trusty on 2014-05-14 (21 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/overlay-scrollbar/+bug/1326909/+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 1326909] Re: un-installable dependency for i386 version on 64-bit pc

[Fabio Porcedda]

Any news on this bug?
What is the simplest way to fix it?

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

Title:
  un-installable dependency for i386 version on 64-bit pc

Status in “overlay-scrollbar” package in Ubuntu:
  Confirmed

Bug description:
  Synaptic does not let me install  overlay-scrollbar-gtk2:i386

  
  below is the error i get on usin aptitude:

  The following packages have unmet dependencies:
   overlay-scrollbar-gtk2:i386 : Depends: overlay-scrollbar:i386 which is a 
virtual package.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: overlay-scrollbar 0.2.16+r359+14.04.20131129-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Thu Jun  5 23:24:28 2014
  InstallationDate: Installed on 2013-11-09 (208 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageArchitecture: all
  SourcePackage: overlay-scrollbar
  UpgradeStatus: Upgraded to trusty on 2014-05-14 (21 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/overlay-scrollbar/+bug/1326909/+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 1349376] [NEW] vector graphic thumbnails blurry in dash on high-dpi screen

[Andreas E.]

Public bug reported:

Thumbnails used in the dash are blurry for small svg images. In contrast
to that the previews in the dash are specifically rendered for the dash
and show in correct resolution.

Nautilus is setup to display icons in 100% zoom level (default). In
Nautilus or on the desktop, svg thumbnails of 24×24px svg images are
smaller than the maximum available thumbnail area and are displayed in
screen pixels (which is very tiny, could also be a bug).

It appears the Unity dash looks up if a thumbnail exists for a specific file in 
~/.cache/thumbnails/normal, chooses that thumbnail and stretches it to the 
maximum available thumbnail area in the dash.
This makes vector graphics appear like they where raster graphics and look very 
blurry.

Ubuntu: 14.04
unity:  7.2.2+14.04. amd64

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

** Attachment added: "screenshot of the thumbnail as shown in the dash (behind: 
the desktop with the same file)"
   
https://bugs.launchpad.net/bugs/1349376/+attachment/4164278/+files/unity-hidpi-thumbnail-dash.png

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

Title:
  vector graphic thumbnails blurry in dash on high-dpi screen

Status in “unity” package in Ubuntu:
  New

Bug description:
  Thumbnails used in the dash are blurry for small svg images. In
  contrast to that the previews in the dash are specifically rendered
  for the dash and show in correct resolution.

  Nautilus is setup to display icons in 100% zoom level (default). In
  Nautilus or on the desktop, svg thumbnails of 24×24px svg images are
  smaller than the maximum available thumbnail area and are displayed in
  screen pixels (which is very tiny, could also be a bug).

  It appears the Unity dash looks up if a thumbnail exists for a specific file 
in ~/.cache/thumbnails/normal, chooses that thumbnail and stretches it to the 
maximum available thumbnail area in the dash.
  This makes vector graphics appear like they where raster graphics and look 
very blurry.

  Ubuntu: 14.04
  unity:  7.2.2+14.04. amd64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1349376/+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 1349376] Re: vector graphic thumbnails blurry in dash on high-dpi screen

[Andreas E.]

** Attachment added: "same file as shown in Nautilus and on the desktop"
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1349376/+attachment/4164279/+files/unity-hidpi-thumbnail-desktop.png

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

Title:
  vector graphic thumbnails blurry in dash on high-dpi screen

Status in “unity” package in Ubuntu:
  New

Bug description:
  Thumbnails used in the dash are blurry for small svg images. In
  contrast to that the previews in the dash are specifically rendered
  for the dash and show in correct resolution.

  Nautilus is setup to display icons in 100% zoom level (default). In
  Nautilus or on the desktop, svg thumbnails of 24×24px svg images are
  smaller than the maximum available thumbnail area and are displayed in
  screen pixels (which is very tiny, could also be a bug).

  It appears the Unity dash looks up if a thumbnail exists for a specific file 
in ~/.cache/thumbnails/normal, chooses that thumbnail and stretches it to the 
maximum available thumbnail area in the dash.
  This makes vector graphics appear like they where raster graphics and look 
very blurry.

  Ubuntu: 14.04
  unity:  7.2.2+14.04. amd64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1349376/+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 1315320] Re: Keyboard layout changes on restart

[Sony]

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

In my situation croatian keyboard layout is not working at all at any
time and i tnever did. Tried to delet and put a new one but nothing
happen. There are non croatian letters in Libre office writer and in
mozzila. Ubuntu 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/1315320

Title:
  Keyboard layout changes on restart

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I am using Ubuntu 14.04 LTS and I am having a problem with my keyboard layout.
  My default keyboard layout is Croatian, but every time I restart/turn on my 
laptop keyboard layout changes to English, but on the top panel the icon shows 
that I am on Croatian.

  So I need first to click on English keyboard layout, and then click again to 
Croatian to change it.
  When I installed Ubuntu this happend just one time, but then after a while 
this is happening very time I turn my laptop on.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 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
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri May  2 11:57:06 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-04-17 (14 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/unity/+bug/1315320/+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 741869] Re: Unity/compiz intercepts Super and Alt keypresses from grabbed windows like VMs.

[Oibaf]

It still doesn't work with the 0ad game. For example ALT+F should show
framerate. I still have to redefine keys I need. I am on an updated
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/741869

Title:
  Unity/compiz intercepts Super and Alt keypresses from grabbed windows
  like VMs.

Status in Ayatana Design:
  Fix Committed
Status in Compiz:
  Triaged
Status in Compiz Core:
  Triaged
Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project precise series:
  Won't Fix
Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Released
Status in “compiz” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  New
Status in “unity” source package in Trusty:
  Fix Released

Bug description:
  [Impact]
  After upgrading from Maverick to Natty, I can no longer use the Super 
(windows) key in Virtual Machine Manager. Previously, as long as I had the 
Virtual Machine Manager console window in the foreground, I could press the 
Super key and the start menu would pop up. Since upgrading to Natty, this no 
longer works, and the search box appears in the upper left.

  Also see bug #934921

  [Test Case]
  (1) Install virtualbox or virt-manager and qemu-system, create and boot a 
virtual machine
  (2) while in the virtual machine (and it should grab the keyboard), press the 
Super key
  Expected Result: the super key acts inside the VM (check by install unity on 
it or using xev)
  Buggy Result: the super key acts in the host and the Unity Dash is displayed

  [regression Potential]This patch plays with key grabs and ungrabs:
  the most likely potential for regression is (a) the existing grabs
  continue and no fix obtains or (2) the grab is not resumed when
  returning control from the VM and the Super key does not invoke the
  Unity Dash.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/741869/+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 1348668] Re: Unity lockscreen lets applications capture keyboard input

[Eddie Dunn]

Good to know. From the back of my mind, I can confirm that running
Firefox, vim, Terminator, or Gedit in the foreground does not affect the
lock screen. In other words the bug lies with the interaction between
Unity Lockscreen and Google Chrome.

Also, related to my previous comment, forget what I wrote there. I think
`workaround-screen-lock-malfunction_1_all.deb` is meant to fix something
else, and so is totally unrelated to this bug. I have had the issue
after installing it.

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

Title:
  Unity lockscreen lets applications capture keyboard input

Status in “unity” package in Ubuntu:
  New

Bug description:
  I noticed that with the Vimium extension activated in Google Chrome, I
  cannot unlock Unity's lockscreen because keyboard input is hijacked by
  Vimium. The lockscreen really should not let this happen, and it can
  even be considered a potential security vulnerability as it might
  allow applications to capture a user's password.

  I have noticed this before as well when using another application,
  though I can't remember which one it was at the moment.

  The workaround is to use the mouse to choose the Switch user-option,
  but this is really not obvious to anyone who might encounter this bug.

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

[Kanter]

apport information

** Attachment added: "GconfCompiz.txt"
   
https://bugs.launchpad.net/bugs/1348883/+attachment/4164167/+files/GconfCompiz.txt

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

Title:
  Password field on login does not respond to keyboard

Status in “unity” package in Ubuntu:
  Incomplete

Bug description:
  After closing my laptop and reopening it again, Ubuntu asks for my
  password. The input field is selected, but when I type nothing
  happens. Clicking around and back on the input also has no effect.

  I could solve it so far in 2 ways; restart, and select 'switch user'.

  On the second approach I found that the text I had entered now appeared in 
the text editor that was open, when I closed the laptop. 
  Further info: this was an online text editor ( Just checked, also occurs when 
closing with this specific inout field (in which I'm currently entering this 
text) selected). 
  Problem doesn't occur in Sublime Text, haven't checked other text editors.

  Reason I select this as a safety threat; I am inputting my Password 
unknowingly on an online form...
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-06-05 (52 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Package: unity 7.2.2+14.04.20140714-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Tags:  trusty
  Uname: Linux 3.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

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

[Kanter]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1348883/+attachment/4164168/+files/ProcEnviron.txt

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

Title:
  Password field on login does not respond to keyboard

Status in “unity” package in Ubuntu:
  Incomplete

Bug description:
  After closing my laptop and reopening it again, Ubuntu asks for my
  password. The input field is selected, but when I type nothing
  happens. Clicking around and back on the input also has no effect.

  I could solve it so far in 2 ways; restart, and select 'switch user'.

  On the second approach I found that the text I had entered now appeared in 
the text editor that was open, when I closed the laptop. 
  Further info: this was an online text editor ( Just checked, also occurs when 
closing with this specific inout field (in which I'm currently entering this 
text) selected). 
  Problem doesn't occur in Sublime Text, haven't checked other text editors.

  Reason I select this as a safety threat; I am inputting my Password 
unknowingly on an online form...
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-06-05 (52 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Package: unity 7.2.2+14.04.20140714-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Tags:  trusty
  Uname: Linux 3.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1348883/+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 1348883] Re: Password field on login does not respond to keyboard

[Kanter]

apport information

** Tags added: apport-collected trusty

** Description changed:

  After closing my laptop and reopening it again, Ubuntu asks for my
  password. The input field is selected, but when I type nothing happens.
  Clicking around and back on the input also has no effect.
  
  I could solve it so far in 2 ways; restart, and select 'switch user'.
  
  On the second approach I found that the text I had entered now appeared in 
the text editor that was open, when I closed the laptop. 
  Further info: this was an online text editor ( Just checked, also occurs when 
closing with this specific inout field (in which I'm currently entering this 
text) selected). 
  Problem doesn't occur in Sublime Text, haven't checked other text editors.
  
- Reason I select this as a safety threat; I am inputting my Password
- unknowingly on an online form...
+ Reason I select this as a safety threat; I am inputting my Password 
unknowingly on an online form...
+ --- 
+ ApportVersion: 2.14.1-0ubuntu3.2
+ Architecture: amd64
+ CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 14.04
+ InstallationDate: Installed on 2014-06-05 (52 days ago)
+ InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
+ Package: unity 7.2.2+14.04.20140714-0ubuntu1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
+ Tags:  trusty
+ Uname: Linux 3.13.0-32-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1348883/+attachment/4164166/+files/Dependencies.txt

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

Title:
  Password field on login does not respond to keyboard

Status in “unity” package in Ubuntu:
  Incomplete

Bug description:
  After closing my laptop and reopening it again, Ubuntu asks for my
  password. The input field is selected, but when I type nothing
  happens. Clicking around and back on the input also has no effect.

  I could solve it so far in 2 ways; restart, and select 'switch user'.

  On the second approach I found that the text I had entered now appeared in 
the text editor that was open, when I closed the laptop. 
  Further info: this was an online text editor ( Just checked, also occurs when 
closing with this specific inout field (in which I'm currently entering this 
text) selected). 
  Problem doesn't occur in Sublime Text, haven't checked other text editors.

  Reason I select this as a safety threat; I am inputting my Password 
unknowingly on an online form...
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-06-05 (52 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Package: unity 7.2.2+14.04.20140714-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Tags:  trusty
  Uname: Linux 3.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

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