[Dx-packages] [Bug 1350393] Re: Recent accountsservice update causes login window to hang

[Gunnar Hjalmarsson]

Right, Derek. Actually, shouldn't the LDAP issue you described be
reported as a separate libnss-ldap bug?

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

Title:
  Recent accountsservice update causes login window to hang

Status in Light Display Manager:
  New
Status in accountsservice package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  The recent 0.6.35-0ubuntu7.1 update (see
  https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1290785)
  seems to have removed the UID_MAX check, which could be used to hide
  users from the login window. In a large organization where many
  thousands of users are present on our systems, we relied on the
  UID_MAX setting in /etc/login.defs to prevent accounts-daemon from
  trying to frob all our accounts. accounts-daemon's performance is so
  poor, that not having the UID_MAX check causes lightdm to hang for
  5-10mins while accounts-daemon tries to look for something in every
  users home folder.

  I've already done things like set the login window to require the user
  to enter their username and password rather than list all users, but
  the login window still hangs while accounts-daemon is doing its thing.

  The behavior I see, is:

  1) just after boot, there's a black screen, right after the plymouth splash 
disappears, for 2-3 minutes before lightdm appears
  2) You type a username into the username field and press 'Tab'
  3) lightdm appears to hang for 5-10mins before the cursor moves to the 
password field. During this time, I see an accounts-daemon spawn for each user 
on the system, sequentially (in alphabetical order). Once the last user's 
accounts-daemon process finishes, the cursor moves to the password field.

  This not only happens on first boot, but every time a user logs out
  and the system returns to the login window.

  Any chance we can have the UID_MAX check back? Or some equivalent?
  This is causing a serious problem for us!

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1350393/+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 1350393] Re: Recent accountsservice update causes login window to hang

[Derek Poon]

@Gunnar, 0.6.35-0ubuntu7.2 may be improve performance in some cases, but
it does nothing to avoid the infinite hang that I characterized in
comment #4.  The fact that it calls user_language_validate() just once
in the context of an LDAP user when the LDAP client isn't fully ready
will cause accounts-daemon to fail completely.  Therefore, your revised
patch should make no difference to the failure mode I described.

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

Title:
  Recent accountsservice update causes login window to hang

Status in Light Display Manager:
  New
Status in accountsservice package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  The recent 0.6.35-0ubuntu7.1 update (see
  https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1290785)
  seems to have removed the UID_MAX check, which could be used to hide
  users from the login window. In a large organization where many
  thousands of users are present on our systems, we relied on the
  UID_MAX setting in /etc/login.defs to prevent accounts-daemon from
  trying to frob all our accounts. accounts-daemon's performance is so
  poor, that not having the UID_MAX check causes lightdm to hang for
  5-10mins while accounts-daemon tries to look for something in every
  users home folder.

  I've already done things like set the login window to require the user
  to enter their username and password rather than list all users, but
  the login window still hangs while accounts-daemon is doing its thing.

  The behavior I see, is:

  1) just after boot, there's a black screen, right after the plymouth splash 
disappears, for 2-3 minutes before lightdm appears
  2) You type a username into the username field and press 'Tab'
  3) lightdm appears to hang for 5-10mins before the cursor moves to the 
password field. During this time, I see an accounts-daemon spawn for each user 
on the system, sequentially (in alphabetical order). Once the last user's 
accounts-daemon process finishes, the cursor moves to the password field.

  This not only happens on first boot, but every time a user logs out
  and the system returns to the login window.

  Any chance we can have the UID_MAX check back? Or some equivalent?
  This is causing a serious problem for us!

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1350393/+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 996791] Re: Xubuntu 12.04 extremely slow login

[Derek Poon]

I suspect that this bug is a duplicate of
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1350393

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

Title:
  Xubuntu 12.04 extremely slow login

Status in accountsservice package in Ubuntu:
  Confirmed

Bug description:
  The core issue is that /usr/lib/accountsservice/accounts-daemon
  doesn't accept dbus messages on boot.

  The symptom to this problem is that, after successfulling entering
  your login information, the system takes about 85 seconds to boot.
  The real issue occuring is that /usr/lib/accountsservice/accounts-
  daemon isn't being started correctly by ligthdm.  The accounts-daemon
  wont accept dbus requests, and so the dbus timeout is hit during boot.

  Before I start, here is a run down on my machine/setup:
  Intel I7.
  Xubuntu 12.04.
  Encrypted home drive.
  Running compiz.

  Enabling the log files on lightdm, the follow warnings are displayed (Notice 
the times):
  [+11.58s] DEBUG: Greeter quit
  [+36.60s] WARNING: Could not call SetXSession: Timeout was reached
  [+61.63s] WARNING: Could not call FindUserByName: Timeout was reached
  [+61.63s] DEBUG: Dropping privileges to uid 1000
  [+61.63s] DEBUG: Restoring privileges
  [+86.65s] WARNING: Could not call FindUserByName: Timeout was reached

  If the /usr/lib/accountsservices/accounts-daemon is restarted, after
  the lightdm login screen is displayed, but before a login, then xfce
  will start immediately.  Otherwise boot times take about 87 seconds.

  Also, it was found that the program d-feet, is unable to retrive valid
  methods from /usr/lib/accountsservices/accounts-daemon before it is
  restarted.  After the deamon is restarted, all dbus methods are
  visuable and communicate correctly.

  For descussion on the problem, and a temporary fix, see the following thread:
  http://ubuntuforums.org/showthread.php?t=1970326

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/996791/+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 1350393] Re: Recent accountsservice update causes login window to hang

[Derek Poon]

This may be a duplicate of bug 996791.
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/996791

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

Title:
  Recent accountsservice update causes login window to hang

Status in Light Display Manager:
  New
Status in accountsservice package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  The recent 0.6.35-0ubuntu7.1 update (see
  https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1290785)
  seems to have removed the UID_MAX check, which could be used to hide
  users from the login window. In a large organization where many
  thousands of users are present on our systems, we relied on the
  UID_MAX setting in /etc/login.defs to prevent accounts-daemon from
  trying to frob all our accounts. accounts-daemon's performance is so
  poor, that not having the UID_MAX check causes lightdm to hang for
  5-10mins while accounts-daemon tries to look for something in every
  users home folder.

  I've already done things like set the login window to require the user
  to enter their username and password rather than list all users, but
  the login window still hangs while accounts-daemon is doing its thing.

  The behavior I see, is:

  1) just after boot, there's a black screen, right after the plymouth splash 
disappears, for 2-3 minutes before lightdm appears
  2) You type a username into the username field and press 'Tab'
  3) lightdm appears to hang for 5-10mins before the cursor moves to the 
password field. During this time, I see an accounts-daemon spawn for each user 
on the system, sequentially (in alphabetical order). Once the last user's 
accounts-daemon process finishes, the cursor moves to the password field.

  This not only happens on first boot, but every time a user logs out
  and the system returns to the login window.

  Any chance we can have the UID_MAX check back? Or some equivalent?
  This is causing a serious problem for us!

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1350393/+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 1382861] Re: Auto brightness toggle sometimes doesn't appear in power indicator

[Charles Kerr]

** Branch linked: lp:~charlesk/indicator-power/lp-1382861-fix-menu-
creation-test

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

Title:
  Auto brightness toggle sometimes doesn't appear in power indicator

Status in the base for Ubuntu mobile products:
  Confirmed
Status in indicator-power package in Ubuntu:
  Confirmed

Bug description:
  On build #5 in the ubuntu-touch/ubuntu-rtm/devel channel, the auto
  brightness toggle is sometimes missing in the power indicator.
  Sometimes everything is fine and sometimes it's simply not there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1382861/+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 1451613] Re: Unity/compiz crashes when locking screen

[Vitor Lopes-dos-Santos]

I also have the same problem.

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

Title:
  Unity/compiz crashes when locking screen

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

Bug description:
  Since a recent update (around April 29th), sometimes (approximately once a 
day) when I lock my computer screen (CTRL+L or using system menu) the computer 
freeze for a while (2 to 30 seconds) before showing the login screen.
  Then when I try to unlock the screen I need to enter my password twice (with 
no error message after the first try).
  Once logged in, all applications are closed. Uptime is still running (since 
no reboot) and services too (with no interruption).

  Looking at the apport.log file (see attached) it seems that when I try
  to lock the screen, compiz crashes.

  I've attached the compiz crash file too (_usr_bin_compiz.1000.crash)
  but without the 100Mo data of base64 core dumb…

  
  I'm using Ubuntu 14.04 AMD64.
  Graphics drivers: nvidia-331.113 (tested)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1451613/+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 1382861] Re: Auto brightness toggle sometimes doesn't appear in power indicator

[Launchpad Bug Tracker]

** Branch linked: lp:~charlesk/indicator-datetime/lp-1382861-fix-menu-
creation-test

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

Title:
  Auto brightness toggle sometimes doesn't appear in power indicator

Status in the base for Ubuntu mobile products:
  Confirmed
Status in indicator-power package in Ubuntu:
  Confirmed

Bug description:
  On build #5 in the ubuntu-touch/ubuntu-rtm/devel channel, the auto
  brightness toggle is sometimes missing in the power indicator.
  Sometimes everything is fine and sometimes it's simply not there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1382861/+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 1437538] Re: Battery Applet appears in English with Gnome in Ubuntu 12.04

[Alfonso]

Help me please carry with it a month and you have not yet given any

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

Title:
  Battery Applet appears in English with Gnome in Ubuntu 12.04

Status in indicator-power package in Ubuntu:
  Incomplete

Bug description:
  Use Ubuntu 12.04 on a Toshiba NB500. I use the Gnome desktop environment, but 
I found a bug:
  The battery applet appears in English, but with Unity appears in Spanish, but 
I still use Gnome !. So I ask you traduzcais battery applet to Spanish. If you 
ask me I missing some information. a greeting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1437538/+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 1103064] Re: power indicator shows Logitech wireless keyboard and mouse batteries with 0%

[MasterCATZ]

it seems it looses connection somehow when the message pops up the
keyboard is listed as unknown if i turn keyboard / off / on again it
works  , but these messages still pop up if the keyboard is even
switched OFF

Done when error is up

 upower -d
Device: /org/freedesktop/UPower/devices/keyboard_0003o046DoC52Bx14F8
  native-path:  
/sys/devices/pci:00/:00:12.0/usb9/9-1/9-1:1.2/0003:046D:C52B.14F7/0003:046D:C52B.14F8
  vendor:   Logitech, Inc.
  model:K400
  serial:   9E5B1F54
  power supply: no
  updated:  Fri 15 May 2015 06:56:54 AEST (60 seconds ago)
  has history:  yes
  has statistics:   no
  keyboard
present: no
rechargeable:yes
state:   unknown
percentage:  0%
  History (charge):
1431637014  0.000   unknown
  History (rate):
1431637014  0.000   unknown

Daemon:
  daemon-version:  0.9.23
  can-suspend: yes
  can-hibernate:   no
  on-battery:  no
  on-low-battery:  no
  lid-is-closed:   no
  lid-is-present:  no
  is-docked:   yes

Done after keyboard Switched off and back on as you can see 70% power
still

 upower -d
Device: /org/freedesktop/UPower/devices/keyboard_0003o046DoC52Bx1500
  native-path:  
/sys/devices/pci:00/:00:12.0/usb9/9-1/9-1:1.2/0003:046D:C52B.14FF/0003:046D:C52B.1500
  vendor:   Logitech, Inc.
  model:K400
  serial:   9E5B1F54
  power supply: no
  updated:  Fri 15 May 2015 07:00:33 AEST (7 seconds ago)
  has history:  yes
  has statistics:   no
  keyboard
present: yes
rechargeable:yes
state:   discharging
percentage:  70%
  History (charge):
1431637233  70.000  discharging
1431637171  0.000   unknown
1431637166  0.000   unknown
  History (rate):
1431637171  0.000   unknown
1431637166  0.000   unknown

Daemon:
  daemon-version:  0.9.23
  can-suspend: yes
  can-hibernate:   no
  on-battery:  no
  on-low-battery:  no
  lid-is-closed:   no
  lid-is-present:  no
  is-docked:   yes

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

Title:
  power indicator shows Logitech wireless keyboard and mouse batteries
  with 0%

Status in The Power Indicator:
  Invalid
Status in Upower:
  Fix Released
Status in indicator-power package in Ubuntu:
  Invalid
Status in upower package in Ubuntu:
  Fix Released
Status in indicator-power source package in Raring:
  Invalid
Status in upower source package in Raring:
  Won't Fix

Bug description:
  I updated by raring installation and found that the power indicator
  now shows my wireless keyboard and mouse as (missing) and with
  extremely low power. Both the keyboard and mouse work (I'm using them
  to type this bug) and the low battery light on the respective devices
  do not show low power. Even switching to brand new batteries don't
  make the indicator change state.

  I've attached a screenshot of the indicator and a screen shot of the
  power setting dialog which seems to be in conflict with the indicator.

  I've reproduced this behavior with the 3.8.0-0-generic &
  vmlinuz-3.8.0-1-generic kernels.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: indicator-power 12.10.6daily13.01.18-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-0.4-generic 3.8.0-rc3
  Uname: Linux 3.8.0-0-generic x86_64
  ApportVersion: 2.8-0ubuntu2
  Architecture: amd64
  Date: Tue Jan 22 11:39:23 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-05-08 (259 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-power
  UpgradeStatus: Upgraded to raring on 2013-01-18 (3 days ago)
  --- 
  ApportVersion: 2.8-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 13.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-05-08 (259 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  Package: upower 0.9.19-1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4
  Tags:  raring running-unity
  Uname: Linux 3.8.0-1-generic x86_64
  UpgradeStatus: Upgraded to raring on 2013-01-18 (4 days ago)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-power/+bug/1103064/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https:

[Dx-packages] [Bug 1455231] Re: [a11y] accerciser cannot explore Unity's accessibility object hierarchy

[Christopher Townsend]

Well, this is not needed for the lp:unity/7.2 as it's already correct.
Just going to mark the tasks Fix Released then:)

** No longer affects: unity/7.2

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

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

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

Title:
  [a11y] accerciser cannot explore Unity's accessibility object
  hierarchy

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

Bug description:
  accerciser cannot explore Unity's accessibility object hierarchy

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1455231/+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 1455231] [NEW] [a11y] accerciser cannot explore Unity's accessibility object hierarchy

[Christopher Townsend]

Public bug reported:

accerciser cannot explore Unity's accessibility object hierarchy

** Affects: unity
 Importance: Undecided
 Status: New

** Affects: unity/7.2
 Importance: Undecided
 Status: New

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

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

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

Title:
  [a11y] accerciser cannot explore Unity's accessibility object
  hierarchy

Status in Unity:
  New
Status in Unity 7.2 series:
  New
Status in unity package in Ubuntu:
  New

Bug description:
  accerciser cannot explore Unity's accessibility object hierarchy

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1455231/+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 1448229] Re: Launcher Trash icon: Empty Trash option opens nautilus @ home

[Chris Moore]

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

Recorded a video of the issue in case there was any question what is
happening.

https://youtu.be/jpugIadlxz0

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

Title:
  Launcher Trash icon: Empty Trash option opens nautilus @ home

Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Test case:
  Add a file to trash if none already
  Right click on Unity launcher trash icon > click on Empty Trash option
  nautilus open a window @ home folder

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.2+15.04.20150420-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Apr 24 13:11:02 2015
  InstallationDate: Installed on 2015-04-24 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  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/1448229/+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 1448229] Re: Launcher Trash icon: Empty Trash option opens nautilus @ home

[Chris Moore]

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

I have the same bug on 2 systems, both fresh installations.

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

Title:
  Launcher Trash icon: Empty Trash option opens nautilus @ home

Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Test case:
  Add a file to trash if none already
  Right click on Unity launcher trash icon > click on Empty Trash option
  nautilus open a window @ home folder

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.2+15.04.20150420-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Apr 24 13:11:02 2015
  InstallationDate: Installed on 2015-04-24 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  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/1448229/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1390625] Re: mouse cursor gets corrupted

[david]

i read all comentaries and  all intel graphics=mouse bug(me too) and
installin xserver-xorg you can fix the problem but the touch pad wont
work(another time me too).

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

Title:
  mouse cursor gets corrupted

Status in elementary OS:
  Confirmed
Status in Mesa:
  New
Status in Unity:
  Invalid
Status in unity package in Ubuntu:
  Invalid
Status in xorg-lts-utopic package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 14.10, the mouse cursor graphic gets corrupted under certain
  occasions. It then looks flipped, sheared or shows fragments of a
  previous cursor.

  * when switching the cursor them forth and back in Gnome Tweak Tool
  * when drag&dropping a document icon

  Maybe related, the cursor does not always show the correct image scale
  on a high-dpi display (this was working right in 14.04). For example
  after login, or when hovering specific areas, or on mouse down to
  start a drag&drop, the cursor appears 1/4 the expected size.

  Attached is a photo of a corrupted cursor (whereas a screenshot with
  Gimp showed the uncorrupted cursor).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20141016-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  BootLog:
   * Setting up X socket directories...   
  [ OK ]
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Nov  7 22:12:52 2014
  DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:3978]
  InstallationDate: Installed on 2014-02-02 (278 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201)
  MachineType: LENOVO 20266
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash 
acpi_backlight=vendor
  SourcePackage: unity
  UpgradeStatus: Upgraded to utopic on 2014-11-04 (3 days ago)
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Fri Nov  7 14:54:59 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 1
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16970
   vendor SDC
  xserver.version: 2:1.16.0-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/elementaryos/+bug/1390625/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1370791] Re: [system-settings] When brightness is set to automatic, the slider doesn't show current value

[Matthew Paul Thomas]

That is bug 1314678, which has also been covered in the spec since April
2013: "If it is checked and you adjust the brightness manually, the
function that determines the automatic brightness should be adjusted
such that, in future, the current ambient light value would result in
your just-chosen brightness being chosen automatically." I even drew a
bunch of graphs to illustrate how it should work.

If graphs aren't your style, here's an example in text:

If the ambient brightness in your office is X, which results in an
automatic brightness of Y, then the brightness slider should show Y
(this bug).

If you then move the slider to Z, the brightness should change to Z (bug
1314678).

If you then go out into the street, the brightness should adjust
accordingly, because automatic brightness is still on, and the slider
should reflect that new brightness (this bug).

If you then go back into your office, the brightness should change to Z,
because that's the brightness you last chose for the office's level of
ambient light (bug 1314678).

** Changed in: ubuntu-ux
   Status: Confirmed => Fix Committed

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

Title:
  [system-settings] When brightness is set to automatic, the slider
  doesn't show current value

Status in the base for Ubuntu mobile products:
  Confirmed
Status in The Power Indicator:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in indicator-power package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  On the brightness page, there is a slider to set brightness and a
  checkbox to set it automatically.

  When I select the automatic brightness, I was expecting the slider to
  show the current brightness level. Instead, it just keeps the old
  value manually set. I find this a little confusing: I have a slider
  whose value I can change, but will do nothing while the checkbox is
  marked, and the value it shows is different from the current
  brightness of the screen.

  : "Because users
  have different preferences, the function should also be user-
  adjustable. This should be achieved by altering the display brightness
  manually while 'Adjust automatically' is checked."

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1370791/+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 1437765] Re: No desktop after upgrade to 14.10

[Jeroen T. Vermeulen]

Saw a bunch of at-spi2 errors in .xsession-errors.  Reinstalled at-
spi2-core, and those errors went away.  Still no desktop.  Deleting
.config/dconf/user did the trick.

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

Title:
  No desktop after upgrade to 14.10

Status in unity package in Ubuntu:
  New

Bug description:
  After upgrading my desktop machine from 14.04 to 14.10, I no longer
  have a desktop.  The login screen works, but after logging in, I get
  just the backdrop image and a mouse pointer.  Nothing else.

  The pointer responds to mouse movements, and I can switch to a text
  console using ctrl-alt-F, which is how I installed KDE in order to
  file this bug.  But I can no longer open a terminal with ctrl-alt-T,
  or switch workspaces with ctrl-alt-.

  My .xsession-errors after logging in showed:

  X Error of failed request:  BadRequest (invalid request code or no such 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  19 (X_GLXQueryServerString)
Serial number of failed request:  22
Current serial number in output stream:  22
  openConnection: connect: No such file or directory
  cannot connect to brltty at :0
  Script for ibus started at run_im.
  Script for auto started at run_im.
  Script for default started at run_im.
  upstart: hud main process (2389) terminated with status 1
  upstart: unity-settings-daemon main process (2393) terminated with status 1
  upstart: unity7 main process (2405) terminated with status 1
  upstart: gnome-session (Unity) main process (2411) terminated with status 1
  upstart: unity-panel-service main process (2422) terminated with status 1
  upstart: indicator-keyboard main process (2496) terminated with status 1
  upstart: indicator-printers main process (2502) terminated with status 1
  upstart: upstart-dbus-session-bridge main process (2366) terminated with 
status 1
  upstart: indicator-bluetooth main process (2485) killed by TERM signal
  upstart: indicator-power main process (2486) killed by TERM signal
  upstart: indicator-datetime main process (2494) killed by TERM signal
  upstart: indicator-sound main process (2501) killed by TERM signal
  upstart: indicator-session main process (2503) killed by TERM signal
  upstart: indicator-application main process (2536) killed by TERM signal
  upstart: Disconnected from notified D-Bus bus

  This is quite a slow machine, so normally it'd take a while to
  complete a graphical login.  But now, when I log in and immediately
  switch to a graphical console to run "top," it doesn't show much going
  on.  External filesystem volumes are not auto-mounted under /media the
  way they usually are.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20141016-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7
  Uname: Linux 3.16.0-33-generic i686
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: KDE
  Date: Sun Mar 29 09:23:52 2015
  InstallationDate: Installed on 2012-11-25 (853 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  SourcePackage: unity
  UpgradeStatus: Upgraded to utopic on 2015-03-28 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1437765/+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 1455149] [NEW] add function to test retrieval of WPAD file in proxy settings

[Karl-Philipp Richter]

Public bug reported:

I'd suggest to add a "test retrieval" and "test retrieval and display"
button. It's crucial to provide useful feedback in case of failure
including the HTTP error code or others error messages from Linux ("host
not reachable"), invalid URL, etc.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: unity 7.3.2+15.04.20150420-0ubuntu1
Uname: Linux 4.0.1-040001-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CompizPlugins: »/apps/compiz-1/general/screen0/options/active_plugins« wurde 
kein Wert zugewiesen
CurrentDesktop: Unity
Date: Thu May 14 18:44:59 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-04-02 (41 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: unity
SystemImageInfo:
 current build number: 0
 device name: 
 channel: daily
 last update: Unknown
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug third-party-packages vivid

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

Title:
  add function to test retrieval of WPAD file in proxy settings

Status in unity package in Ubuntu:
  New

Bug description:
  I'd suggest to add a "test retrieval" and "test retrieval and display"
  button. It's crucial to provide useful feedback in case of failure
  including the HTTP error code or others error messages from Linux
  ("host not reachable"), invalid URL, etc.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.2+15.04.20150420-0ubuntu1
  Uname: Linux 4.0.1-040001-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CompizPlugins: »/apps/compiz-1/general/screen0/options/active_plugins« wurde 
kein Wert zugewiesen
  CurrentDesktop: Unity
  Date: Thu May 14 18:44:59 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-04-02 (41 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1455149/+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 1434205] Re: accounts-daemon using up several gigabytes of RAM

[Gunnar Hjalmarsson]

** Changed in: accountsservice (Ubuntu)
   Status: New => Invalid

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

Title:
  accounts-daemon using up several gigabytes of RAM

Status in accountsservice package in Ubuntu:
  Invalid

Bug description:
  HP Z400 Workstation
  Intel Xeon W3520
  12GB RAM
  nVidia QuadroFX 580

  Kubuntu Trusty 14.04.2 LTS, apt-get says everything is up to date
  Kernel 3.13.0-46-generic x64
  KDE SC Version 4.13.2
  Accountsservice 0.6.35-0ubuntu7.1

  My system seems to boot just fine until it tries to bring up LightDM.
  At that point, accounts-daemon eats up 100% of a CPU core, starts
  allocating tons of memory and causes LightDM to hang for ~25 seconds.
  After I put in my username and password accounts-daemon continues
  eating up 100% of a CPU core, allocates more memory and hangs the
  login process some more. After being logged in for a few minutes it
  stops using CPU time but never frees any memory, eventually settling
  in at ~6GB used. At the time of this writing it is currently at
  5,754,280K.

  If I kill the process it frees all of the memory, but after locking
  the screen or similiar action something (dbus?) starts it back up
  again and the process repeats, although only using up ~3GB of RAM. I
  have tried running accounts-daemon --debug and it doesn't spit out
  anything indicating an error. The closest that I've found to a problem
  is in the lightdm.log file excerpted below:

  
  [+0.05s] DEBUG: Using VT 7
  [+0.05s] DEBUG: Seat: Starting local X display on VT 7
  [+0.05s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log
  [+0.05s] DEBUG: DisplayServer x-0: Writing X server authority to 
/var/run/lightdm/root/:0
  [+0.05s] DEBUG: DisplayServer x-0: Launching X Server
  [+0.05s] DEBUG: Launching process 1254: /usr/bin/X -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  [+0.05s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
  [+0.05s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
  [+0.05s] DEBUG: Registering seat with bus path 
/org/freedesktop/DisplayManager/Seat0
  [+25.08s] WARNING: Error getting user list from org.freedesktop.Accounts: 
Timeout was reached
  [+25.08s] DEBUG: Loading user config from /etc/lightdm/users.conf
  [+25.09s] DEBUG: User x added
  [+25.09s] DEBUG: Got signal 10 from process 1254
  [+25.09s] DEBUG: DisplayServer x-0: Got signal from X server :0
  [+25.09s] DEBUG: DisplayServer x-0: Connecting to XServer :0
  

  dbus does seem to start the service successfully as evidenced in
  syslog:

  
  Mar 19 10:32:32 the-cybercraft dbus[791]: [system] Activating service 
name='org.freedesktop.Accounts' (using servicehelper)
  Mar 19 10:32:32 the-cybercraft accounts-daemon[1259]: started daemon version 
0.6.35
  Mar 19 10:32:32 the-cybercraft dbus[791]: [system] Successfully activated 
service 'org.freedesktop.Accounts'
  

  I'll provide any help that I can, and thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1434205/+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 1370791] Re: [system-settings] When brightness is set to automatic, the slider doesn't show current value

[Pat McGowan]

With autobrigthness enabled we need to define the behavior for what
happens when the user tries to use the slider:

1 - it works but auto is still on and will reset it
2 - it signals user wants manual settings so disable auto
3 - the slider is disabled but reflects current brightness value

** Changed in: ubuntu-ux
   Status: Fix Committed => Confirmed

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

Title:
  [system-settings] When brightness is set to automatic, the slider
  doesn't show current value

Status in the base for Ubuntu mobile products:
  Confirmed
Status in The Power Indicator:
  Confirmed
Status in Ubuntu UX bugs:
  Confirmed
Status in indicator-power package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  On the brightness page, there is a slider to set brightness and a
  checkbox to set it automatically.

  When I select the automatic brightness, I was expecting the slider to
  show the current brightness level. Instead, it just keeps the old
  value manually set. I find this a little confusing: I have a slider
  whose value I can change, but will do nothing while the checkbox is
  marked, and the value it shows is different from the current
  brightness of the screen.

  : "Because users
  have different preferences, the function should also be user-
  adjustable. This should be achieved by altering the display brightness
  manually while 'Adjust automatically' is checked."

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1370791/+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 1370791] Re: [system-settings] When brightness is set to automatic, the slider doesn't show current value

[Pat McGowan]

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
   Importance: Undecided => Medium

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

** Changed in: canonical-devices-system-image
Milestone: None => ww22-2015

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Thomas Strehl (strehl-t)

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

Title:
  [system-settings] When brightness is set to automatic, the slider
  doesn't show current value

Status in the base for Ubuntu mobile products:
  Confirmed
Status in The Power Indicator:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in indicator-power package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  On the brightness page, there is a slider to set brightness and a
  checkbox to set it automatically.

  When I select the automatic brightness, I was expecting the slider to
  show the current brightness level. Instead, it just keeps the old
  value manually set. I find this a little confusing: I have a slider
  whose value I can change, but will do nothing while the checkbox is
  marked, and the value it shows is different from the current
  brightness of the screen.

  : "Because users
  have different preferences, the function should also be user-
  adjustable. This should be achieved by altering the display brightness
  manually while 'Adjust automatically' is checked."

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1370791/+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 1382861] Re: Auto brightness toggle sometimes doesn't appear in power indicator

[Pat McGowan]

This is being reported more often and on all hardware
The check  that the device supports autobrightness seems unreliable.

** Changed in: indicator-power (Ubuntu)
   Importance: Undecided => Critical

** Changed in: indicator-power (Ubuntu)
 Assignee: (unassigned) => Charles Kerr (charlesk)

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
   Importance: Undecided => Critical

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

** Changed in: canonical-devices-system-image
Milestone: None => ww22-2015

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Thomas Strehl (strehl-t)

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

Title:
  Auto brightness toggle sometimes doesn't appear in power indicator

Status in the base for Ubuntu mobile products:
  Confirmed
Status in indicator-power package in Ubuntu:
  Confirmed

Bug description:
  On build #5 in the ubuntu-touch/ubuntu-rtm/devel channel, the auto
  brightness toggle is sometimes missing in the power indicator.
  Sometimes everything is fine and sometimes it's simply not there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1382861/+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 1452405] Re: wmctrl cannot move windows into certain positions

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

Title:
  wmctrl cannot move windows into certain positions

Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu version 15.04, Unity version 7.3.2+15.04.20150420-0ubuntu1 and
  wmctrl version 1.07-7.

  If I try to place a window in the top left of the desktop, with the command 
"wmctrl -r :ACTIVE: -e 0,0,0,1240,1034", it'll instead place the window about 
10 pixels to the right of the edge of the Unity launcher.
  Similarly, trying to place a window on the top right corner with "wmctrl -r 
:ACTIVE: -e 1,1280,0,640,360", the window appears in the right X position, but 
it's also about 10 pixels below the Unity panel.
  However, "wmctrl -r :ACTIVE: -e 1,1280,720,640,335" will place the window at 
the expected position. It's like it's expecting the launcher and panel to be 
bigger than they actually are.
  I have my launcher set to 32 pixel icons, and I set up the scale for menu and 
titlebars as 0.875 in Settings>Displays, and my resolution is 1920x1080.

  Would love to know if there's any workaround or alternative way to
  place windows in specific spots via script. I tried xdotool but causes
  the same abnormal behavior. I confirmed xmctrl works in other desktops
  like KDE (both 4 and plasma 5)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1452405/+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 1451613] Re: Unity/compiz crashes when locking screen

[Joao Marinho]

I am also having the same problem here, it started to happen a lot after
I did regular updates last friday.

I am using nvidia drivers 331.113

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

Title:
  Unity/compiz crashes when locking screen

Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Since a recent update (around April 29th), sometimes (approximately once a 
day) when I lock my computer screen (CTRL+L or using system menu) the computer 
freeze for a while (2 to 30 seconds) before showing the login screen.
  Then when I try to unlock the screen I need to enter my password twice (with 
no error message after the first try).
  Once logged in, all applications are closed. Uptime is still running (since 
no reboot) and services too (with no interruption).

  Looking at the apport.log file (see attached) it seems that when I try
  to lock the screen, compiz crashes.

  I've attached the compiz crash file too (_usr_bin_compiz.1000.crash)
  but without the 100Mo data of base64 core dumb…

  
  I'm using Ubuntu 14.04 AMD64.
  Graphics drivers: nvidia-331.113 (tested)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1451613/+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 1445106] Re: [Notifications] turn the screen on

[Oliver Grawert]

do either of android, IOS or windows phone use the proximity sensor to
check if they are in a pocket to not trigger any button presses on the
notifications ? that is IMHO the only sane solution to this problem,
your pocket should not be able to generate any input, only turning on
the screen if the proximity sensor is not covered will help with that
(yes, i know it wouldn't turn on then if you have a sheet of paper on
top of it on your desk or some such, but isn't that a corner case
(beyond the fact that you still get acoustic (and perhaps haptic)
signals anyway ?)

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

Title:
  [Notifications] turn the screen on

Status in Ubuntu UX bugs:
  Triaged
Status in indicator-messages package in Ubuntu:
  Confirmed

Bug description:
  Built: r20

  When getting a notification, such as a text message, the screen will turn on.
  This becomes a problem when the device is kept in a pocket,
  where it may falsely register screen activity and thus stay on for hours.

  
  -UX comment-

  Please refer for the correct behaviour here:
  
https://docs.google.com/a/canonical.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit?pli=1#

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1445106/+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 1445106] Re: [Notifications] turn the screen on

[Sigurt Bladt Dinesen]

I think the led indicator plays a part as well.
For me, the perfect combination is no sound, vibrate, and turn start blinking 
the led until the next time I open the notification tray.

I believe this is the behaviour I used to get on android.

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

Title:
  [Notifications] turn the screen on

Status in Ubuntu UX bugs:
  Triaged
Status in indicator-messages package in Ubuntu:
  Confirmed

Bug description:
  Built: r20

  When getting a notification, such as a text message, the screen will turn on.
  This becomes a problem when the device is kept in a pocket,
  where it may falsely register screen activity and thus stay on for hours.

  
  -UX comment-

  Please refer for the correct behaviour here:
  
https://docs.google.com/a/canonical.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit?pli=1#

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1445106/+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 1350393] Re: Recent accountsservice update causes login window to hang

[Gunnar Hjalmarsson]

Version 0.6.35-0ubuntu7.2 of accountsservice is now available in trusty-
proposed, and the performance ought to have improved significantly due
to the change on a system with many users.

@Stephen, @Ioannis and @Derek: It would be great if you could install
the new version, and let us know about your observations as regards
performance.

** Changed in: accountsservice (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Recent accountsservice update causes login window to hang

Status in Light Display Manager:
  New
Status in accountsservice package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  The recent 0.6.35-0ubuntu7.1 update (see
  https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1290785)
  seems to have removed the UID_MAX check, which could be used to hide
  users from the login window. In a large organization where many
  thousands of users are present on our systems, we relied on the
  UID_MAX setting in /etc/login.defs to prevent accounts-daemon from
  trying to frob all our accounts. accounts-daemon's performance is so
  poor, that not having the UID_MAX check causes lightdm to hang for
  5-10mins while accounts-daemon tries to look for something in every
  users home folder.

  I've already done things like set the login window to require the user
  to enter their username and password rather than list all users, but
  the login window still hangs while accounts-daemon is doing its thing.

  The behavior I see, is:

  1) just after boot, there's a black screen, right after the plymouth splash 
disappears, for 2-3 minutes before lightdm appears
  2) You type a username into the username field and press 'Tab'
  3) lightdm appears to hang for 5-10mins before the cursor moves to the 
password field. During this time, I see an accounts-daemon spawn for each user 
on the system, sequentially (in alphabetical order). Once the last user's 
accounts-daemon process finishes, the cursor moves to the password field.

  This not only happens on first boot, but every time a user logs out
  and the system returns to the login window.

  Any chance we can have the UID_MAX check back? Or some equivalent?
  This is causing a serious problem for us!

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1350393/+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 1443178] Re: Accounts Service always relies on language fallback if never set by the user

[Gunnar Hjalmarsson]

I have successfully installed and run both accountsservice
0.6.35-0ubuntu7.2 from trusty-proposed and accountsservice
0.6.37-1ubuntu10.1 from vivid-proposed. Querying accountsservice for
language and regional formats seems to work as expected, and even if I
haven't measured it, the desired performance improvement requested by
the bug reporter has most likely been achieved.

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Accounts Service always relies on language fallback if never set by
  the user

Status in the base for Ubuntu mobile products:
  New
Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Trusty:
  Fix Committed
Status in accountsservice source package in Vivid:
  Fix Committed

Bug description:
  trusty and vivid SRU requests
  =

  [Impact]

  Until a user has set the language or regional formats explicitly,
  accountsservice makes the system default values available. The code
  for 'calculating' the system defaults is expensive, and it's triggered
  frequently. The case in the original description of this bug report is
  one example of bad performance for this reason. Another example is a
  system with many users (see e.g. bug #1350393).

  This upload adds a couple of static variables inside the function in
  question, to avoid that the expensive code is executed at each
  invocation. Under certain conditions this improves the performance
  significantly.

  [Test Case]

  Hmm.. There is no easy use case to reproduce the bug. The original
  description below gives a hint.

  [Regression Potential]

  On a multi-user system, if the system defaults in /etc/default/locale
  are changed, accountsservice will keep providing the old system
  default values until the system is rebooted. (Previously it took
  effect instantly.) I think the advantages with the proposed change
  outweigh this subtle change in behavior (which hardly anyone will
  notice anyway).

  Can't think of anything besides that.

  [Original description]

  current build number: 169
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-04-12 20:38:14
  version version: 169
  version ubuntu: 20150412
  version device: 20150210
  version custom: 20150412

  This causes a bad side effect when changing volume via indicator-
  sound, as that will cause a sync to accountsservice in order to sync
  the volume. Once that sync happens, it will request the user
  properties, and in case the user doesn't have a valid language at
  /var/lib/AccountsService/users/, it will always rely on the
  fallback, which would be fine if calculating the fallback wasn't 't so
  cpu or i/o intensive (and that happens multiple times).

  As a test, just flash latest vivid image on mako, don't set any
  language when the wizard shows up, run top and then change the volume
  by pressing volume up/down. This is what I see with mako:

   PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND
  2609 phablet   20   0  499660 121220  52688 S   7.6  6.5   0:41.69 unity8
  5600 phablet   20   03676   1760   1288 R   6.0  0.1   0:00.19 
language-option
  1312 root  20   0  211532  15572  11344 S   1.9  0.8   0:07.25 
unity-system-co
  1316 phablet   20   0   36532   3792   2928 S   1.3  0.2   0:01.66 
accounts-daemon

  And the reason why:
  src/user.c
  ...
  static void
  user_get_property (GObject*object,
     guint   param_id,
     GValue *value,
     GParamSpec *pspec)
  {
  User *user = USER (object);
  ...
  case PROP_LANGUAGE:
  if (user->language)
  g_value_set_string (value, user->language);
  else
  g_value_set_string (value, user_get_fallback_value 
(user, "Language"));
  break;
  case PROP_FORMATS_LOCALE:
  if (user->formats_locale)
  g_value_set_string (value, user->formats_locale);
  else
  g_value_set_string (value, user_get_fallback_value 
(user, "FormatsLocale"));
  break;

  user_set_property never gets called unless the user changes the system
  language from system-settings or wizard.

  Once you change the language, it will set a valid language at
  /var/lib/AccountsService/users/, causing this behavior to stop.

  Another bad side effect of this issue is that it takes quite a while
  for accountsservice to reply back to indicator-sound when the sync
  happens, possibly causing sync aborts (as indicator-sound only waits 1
  second before triggering another sync).

  Some

Re: [Dx-packages] [Bug 1241101]

[MiXiM]

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

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

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

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/eclipse/+bug/1241101/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1241101]

[Simone]

(In reply to Cristiano Gaviao from comment #45)
> (In reply to Simone Perriello from comment #43)
> > Do you mean creating a .desktop file? If so, where I have to put the
> > commands in the exec, right? Can you provide a template of a .desktop file?
> > I've always launched Eclipse from terminal.
> 
> Yep, its a .desktop file that I've put in /usr/share/applications.
> 
> [Desktop Entry]
> Version=4.5
> Comment=Integrated Development Environment
> Exec=env LIBOVERLAY_SCROLLBAR=0 SWT_GTK3=0 
> /opt/eclipse-ide/java-mars/eclipse/eclipse
> Type=Application
> Icon=eclipse-luna.xpm
> Terminal=false
> NoDisplay=false
> Categories=Development;IDE;Java
> StartupWMClass=Eclipse
> Name[en_US]=Eclipse Mars Java

More or less, it's the same .desktop file that I've used (see my comment
above). However, as said, it doesn't work at all.

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

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

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

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/eclipse/+bug/1241101/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 652978] Re: Notify-OSD should be suppressed when using the sound menu

[Matthew Paul Thomas]

Mirco, Lars:
(1) How is an app supposed to know whether a track change was triggered from 
the sound menu, or from any other software that sends MPRIS requests?
(2) Volume changes aren't triggered by apps. If indicator-sound isn't the 
appropriate home for the volume changes part of this bug, what is?

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

Title:
  Notify-OSD should be suppressed when using the sound menu

Status in Ayatana Design:
  Fix Committed
Status in Sound Menu:
  Invalid
Status in indicator-sound package in Ubuntu:
  Confirmed
Status in notify-osd package in Ubuntu:
  Invalid

Bug description:
  When using the sound menu, the user is immediately visually notified
  about switching of tracks by the menu itself.

  +

  When notifying using Notify-OSD, it covers some parts of sound menu
  itself. I think Notify-OSD should not be shown when switching tracks
  using the sound-menu and MAY BE whenever switching manually.

  Example video:
  http://dl.dropbox.com/u/275756/out.ogv

  
  PS:
  U1 was not working, so dropbox. :)
  and yes, I did spend like 10 minutes thinking which songs I should show in 
the video. :P

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/652978/+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 1445106] Re: [Notifications] turn the screen on

[Matthew Paul Thomas]

iOS and (reportedly) Windows Phone always wake the display for a few
seconds -- just as if you had tapped the home button or pressed the
sleep/wake button -- when a notification arrives of the sort that
appears on the lock screen.

Android used to do the same, but as of 5.0 apparently no longer does,
unless you (a) turn on the "Ambient display" setting, (b) use a Motorola
and leave on the "Active display" setting, or (c) install an app like
Glimpse Notifications. ("Using Android Lollipop's lock screen
notifications? Tired of having to press the power button to see them?
Then this app is for you!")

For Ubuntu, the relevant part of the spec says: "If the screen display
is off (black), the expected behaviour is to wake the phone by simply
tapping on the screen or by using the physical button on the side. Once
the display is active, user can interact with the notification bubbles."
 I think a couple of points need clearing up:

1. Should tapping the screen *normally* wake the phone, or is this
behavior specific to a certain period after a notification has arrived?
If the former, it would help to link to the relevant spec. If the
latter, how long is the period?

2. If a notification would play a sound, should this sound still play
even when the screen does not wake up?

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

Title:
  [Notifications] turn the screen on

Status in Ubuntu UX bugs:
  Triaged
Status in indicator-messages package in Ubuntu:
  Confirmed

Bug description:
  Built: r20

  When getting a notification, such as a text message, the screen will turn on.
  This becomes a problem when the device is kept in a pocket,
  where it may falsely register screen activity and thus stay on for hours.

  
  -UX comment-

  Please refer for the correct behaviour here:
  
https://docs.google.com/a/canonical.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit?pli=1#

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