[Touch-packages] [Bug 1389008] Re: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control)

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/ubuntu-touch-session

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-sound in Ubuntu.
https://bugs.launchpad.net/bugs/1389008

Title:
  Often fails to connect to Pulseaudio and unity-notifications (results
  in missing volume notifications and improper volume control)

Status in “indicator-sound” package in Ubuntu:
  Invalid
Status in “ubuntu-touch-session” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Confirmed
Status in “indicator-sound” package in Ubuntu RTM:
  Invalid
Status in “ubuntu-touch-session” package in Ubuntu RTM:
  Confirmed
Status in “unity8” package in Ubuntu RTM:
  New

Bug description:
  Often after boot indicator-sound fails to connect to Pulseaudio and to
  unity-notifications using libnotify. Therefore, volume notifications
  aren't shown and changes to the volume role go unnoticed, which then
  results in improper volume control.

  As already mentioned in the original bug description, running "restart
  indicator-sound" resolves the issue.

  Original description:

  Happens often after phone boot where changing volume by touch or by
  phone buttons. Volume correctly changes, but the
  org.freedesktop.Notifications popup isn't displayed.

  The problem seems fixes itself if you run "restart indicator-sound",
  so maybe there's an issue with i-sound and unity-notifications
  starting at the same time, with the former querying the latter's
  capabilities before it's ready for business?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1389008/+subscriptions

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

[Touch-packages] [Bug 1277608] Re: hostnamed should not print warning about nss-myhostname

[Josh]

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

Problem continues to exist on 14.10.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1277608

Title:
  hostnamed should not print warning about nss-myhostname

Status in “systemd” package in Ubuntu:
  Confirmed

Bug description:
  Currently hostnamed prints the following error in syslog:

  systemd-hostnamed[24508]: Warning: nss-myhostname is not installed.
  Changing the local hostname might make it unresolveable. Please
  install nss-myhostname!

  Since nss-myhostname was rejected as being the right approach in
  https://bugs.launchpad.net/ubuntu/+source/libnss-
  myhostname/+bug/1162478/comments/6 , we should not print the warning
  message in the LTS release, even if hostnamed doesn't currently modify
  /etc/hosts (LP: #1162475).

  Can we please patch this warning out to prevent users from thinking
  something is wrong on their system and leading them to install libnss-
  myhostname?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: systemd-services 204-5ubuntu10
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb  7 12:12:20 2014
  InstallationDate: Installed on 2013-11-26 (72 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: systemd
  UpgradeStatus: Upgraded to trusty on 2014-01-17 (20 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1277608/+subscriptions

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

[Touch-packages] [Bug 1359332] Re: Need to allow for both Unity 8 desktop "bare metal" and LXC sessions

[Mathew Hodson]

https://launchpad.net/ubuntu/+source/lightdm/1.10.3-0ubuntu2 is
available in trusty-proposed.

---
lightdm (1.10.3-0ubuntu2) trusty; urgency=medium

  * Refresh patches

 -- Robert Ancell  Fri, 10 Oct 2014
21:24:51 +1300

lightdm (1.10.3-0ubuntu1) trusty; urgency=medium

  * New upstream release:
- Fix crash when having configuration keys defined in multiple places
  (LP: #1377373)
- Allow user switching in multi-seat until bug stopping greeter showing on
  logout is fixed
- Don't access .dmrc files until information from these files is required
  (LP: #1370852)
- Do timed autologin each time you are returned to the greeter
  (LP: #1302491)

 -- Robert Ancell  Thu, 09 Oct 2014
09:01:21 +1300

lightdm (1.10.2-0ubuntu1) trusty; urgency=medium

  * New upstream release:
- Use logind to provide the list of seats to use. This is disabled unless
  logind-load-seats (in [LightDM] section) is set to true. This is the
  default behaviour in lightdm 1.12. (LP: #1190581)
- Fix crash if running script hooks with non-X display servers.
  (LP: #1305006)
- Add a seat option 'allow-user-switching' that can disable all user
  switching for that seat. (LP: #1350357)
- Make PAM services configurable. (LP: #1348251)
- Add liblightdm method to get user UID. (LP: #1370327)
- Add a new session type 'mir-container' that allows the session to run
  inside a custom system compositor. (LP: #1359332)
- Add --show-config option that shows combined configuration.
- Use XDG_SESSION_ID from PAM instead of using the logind D-Bus API.
  (LP: #1364725)
- Make socket writing code used between greeter and daemon more robust to
  errors.
- Correct section name in default users.conf file.
- Fix tests failing with Qt 5.3 due to it checking getuid/geteuid which we
  are faking.
- Fix small memory leaks.
- Test improvements

 -- Robert Ancell  Wed, 17 Sep 2014
16:27:53 +1200

** Changed in: lightdm (Ubuntu Trusty)
   Status: New => Fix Committed

** Branch linked: lp:ubuntu/trusty-proposed/lightdm

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1359332

Title:
  Need to allow for both Unity 8 desktop "bare metal" and LXC sessions

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in Unity 8 Desktop Session:
  Fix Committed
Status in unity8-desktop-session trusty series:
  Fix Committed
Status in Unity8 Desktop Preview in LXC:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “unity8-desktop-session” package in Ubuntu:
  Fix Released
Status in “lightdm” source package in Trusty:
  Fix Committed
Status in “unity8-desktop-session” source package in Trusty:
  Fix Released
Status in “lightdm” source package in Utopic:
  Fix Released
Status in “unity8-desktop-session” source package in Utopic:
  Fix Released

Bug description:
  [Impact]
  Users trying to use the Unity8 desktop preview in a Linux Container cannot 
log in using LightDM.  They are presented a black screen with a cursor.

  [Test Case]
  1. Install the Unity8 desktop preview in LXC package (currently in a PPA 
here: 
https://code.launchpad.net/~unity8-desktop-session-team/+archive/ubuntu/unity8-preview-lxc)
 alongside the unity8-desktop-session-mir package in Universe.  Setup the 
Unity8 desktop preview in LXC as shown in 
https://wiki.ubuntu.com/Unity8inLXC#Setting_up_the_Unity_8_Desktop_Preview_LXC
  2. Log in to the "Unity8 Mir in LXC" session from LightDM.

  The Unity8 desktop preview will load.

  [Regression potential]
  Non observed.

  Original Description:

  It would be desirable to allow both the Unity 8 desktop preview
  session from the archive and the Unity 8 desktop preview in the LXC to
  be installed at the same time.

  Currently, the Unity 8 desktop preview in LXC conflicts the "bare
  metal" Unity 8 desktop preview session.

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

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

[Touch-packages] [Bug 1364725] Re: logind session ID not used due to race condition

[Mathew Hodson]

https://launchpad.net/ubuntu/+source/lightdm/1.10.3-0ubuntu2 is
available in trusty-proposed.

---
lightdm (1.10.3-0ubuntu2) trusty; urgency=medium

  * Refresh patches

 -- Robert Ancell  Fri, 10 Oct 2014
21:24:51 +1300

lightdm (1.10.3-0ubuntu1) trusty; urgency=medium

  * New upstream release:
- Fix crash when having configuration keys defined in multiple places
  (LP: #1377373)
- Allow user switching in multi-seat until bug stopping greeter showing on
  logout is fixed
- Don't access .dmrc files until information from these files is required
  (LP: #1370852)
- Do timed autologin each time you are returned to the greeter
  (LP: #1302491)

 -- Robert Ancell  Thu, 09 Oct 2014
09:01:21 +1300

lightdm (1.10.2-0ubuntu1) trusty; urgency=medium

  * New upstream release:
- Use logind to provide the list of seats to use. This is disabled unless
  logind-load-seats (in [LightDM] section) is set to true. This is the
  default behaviour in lightdm 1.12. (LP: #1190581)
- Fix crash if running script hooks with non-X display servers.
  (LP: #1305006)
- Add a seat option 'allow-user-switching' that can disable all user
  switching for that seat. (LP: #1350357)
- Make PAM services configurable. (LP: #1348251)
- Add liblightdm method to get user UID. (LP: #1370327)
- Add a new session type 'mir-container' that allows the session to run
  inside a custom system compositor. (LP: #1359332)
- Add --show-config option that shows combined configuration.
- Use XDG_SESSION_ID from PAM instead of using the logind D-Bus API.
  (LP: #1364725)
- Make socket writing code used between greeter and daemon more robust to
  errors.
- Correct section name in default users.conf file.
- Fix tests failing with Qt 5.3 due to it checking getuid/geteuid which we
  are faking.
- Fix small memory leaks.
- Test improvements

 -- Robert Ancell  Wed, 17 Sep 2014
16:27:53 +1200

** Changed in: lightdm (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

** Branch linked: lp:ubuntu/trusty-proposed/lightdm

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1364725

Title:
  logind session ID not used due to race condition

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “lightdm” source package in Trusty:
  Fix Committed
Status in “lightdm” source package in Utopic:
  Fix Released

Bug description:
  [Impact]
  Sometimes a session will fail to get the logind session ID to pass back to 
the LightDM daemon. This appears to be due to a race using the D-Bus method 
org.freedesktop.login1.Manager.GetSessionByPID instead of getting the 
environment variable XDG_SESSION_ID as set in PAM.

  This bug was detected by a bug in LightDM 1.11.7 where the daemon
  would attempt to read both a logind and ConsoleKit ID when this D-Bus
  call failed.

  The solution is to use the XDG_SESSION_ID environment variable and not
  GetSessionByPID() and to fix the passing of the session id(s) from the
  session to the daemon to be unambiguous.

  [Test Case]
  Check the LightDM log always contains lines like:
  [+0.78s] DEBUG: Activating login1 session c1
  for each session.

  [Regression Potential]
  Change is non-trivial and could cause other bugs. Regression tests confirm 
existing test cases work.

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

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

[Touch-packages] [Bug 1348251] Re: Not able to configure PAM services

[Mathew Hodson]

https://launchpad.net/ubuntu/+source/lightdm/1.10.3-0ubuntu2 is
available in trusty-proposed.

---
lightdm (1.10.3-0ubuntu2) trusty; urgency=medium

  * Refresh patches

 -- Robert Ancell  Fri, 10 Oct 2014
21:24:51 +1300

lightdm (1.10.3-0ubuntu1) trusty; urgency=medium

  * New upstream release:
- Fix crash when having configuration keys defined in multiple places
  (LP: #1377373)
- Allow user switching in multi-seat until bug stopping greeter showing on
  logout is fixed
- Don't access .dmrc files until information from these files is required
  (LP: #1370852)
- Do timed autologin each time you are returned to the greeter
  (LP: #1302491)

 -- Robert Ancell  Thu, 09 Oct 2014
09:01:21 +1300

lightdm (1.10.2-0ubuntu1) trusty; urgency=medium

  * New upstream release:
- Use logind to provide the list of seats to use. This is disabled unless
  logind-load-seats (in [LightDM] section) is set to true. This is the
  default behaviour in lightdm 1.12. (LP: #1190581)
- Fix crash if running script hooks with non-X display servers.
  (LP: #1305006)
- Add a seat option 'allow-user-switching' that can disable all user
  switching for that seat. (LP: #1350357)
- Make PAM services configurable. (LP: #1348251)
- Add liblightdm method to get user UID. (LP: #1370327)
- Add a new session type 'mir-container' that allows the session to run
  inside a custom system compositor. (LP: #1359332)
- Add --show-config option that shows combined configuration.
- Use XDG_SESSION_ID from PAM instead of using the logind D-Bus API.
  (LP: #1364725)
- Make socket writing code used between greeter and daemon more robust to
  errors.
- Correct section name in default users.conf file.
- Fix tests failing with Qt 5.3 due to it checking getuid/geteuid which we
  are faking.
- Fix small memory leaks.
- Test improvements

 -- Robert Ancell  Wed, 17 Sep 2014
16:27:53 +1200

** Changed in: lightdm (Ubuntu Trusty)
   Status: New => Fix Committed

** Branch linked: lp:ubuntu/trusty-proposed/lightdm

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1348251

Title:
  Not able to configure PAM services

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “ubuntu-touch-session” package in Ubuntu:
  Invalid
Status in “lightdm” source package in Trusty:
  Fix Committed
Status in “ubuntu-touch-session” source package in Trusty:
  New
Status in “lightdm” source package in Utopic:
  Fix Released
Status in “ubuntu-touch-session” source package in Utopic:
  Invalid

Bug description:
  [Impact]
  No method to configure PAM services used (hard-coded to "lightdm"). This is 
required in some cases, e.g. when running Ubuntu on the phone we want to use a 
different PAM stack. By making this configurable the phone can have a package 
that overrides the default.

  [Test Case]
  1. Set a different PAM stack in the LightDM configuration:
   [SeatDefaults]
   pam-service=custom-service
  2. Start LightDM
  3. Log in
  Expected result:
  PAM modules in "custom-service" are run, user is logged in.
  Observed result:
  PAM modules in "lightdm" are run, user is logged in. (feature not yet 
supported)

  [Regression Potential]
  Low, fix is just replacing hard-coded values with a configuration lookup. 
Tested with regression tests.

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

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

[Touch-packages] [Bug 1390490] Re: Race between connectivity-api and network-manager

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/location-service

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to location-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1390490

Title:
  Race between connectivity-api and network-manager

Status in Ubuntu Location Provider Here:
  In Progress
Status in “location-service” package in Ubuntu:
  Fix Released
Status in “ubuntu-location-provider-here” package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  https://bugs.launchpad.net/ubuntu/+source/location-
  service/+bug/1389874 was a symptom for an issue with connectivity API
  which doesn't work when it starts before network-manager is started or
  when leaving airplane mode.

  To reproduce, create an upstart job like connectivity.conf with:
  start on started dbus

  console log

  respawn
  respawn limit unlimited

  script
  GLOG_logtostderr=1
  GLOG_v=200
  export GLOG_logtostderr GLOG_v
  exec /home/phablet/connectivity
  end script

  with connectivity from http://people.canonical.com/~lool/connectivity

  Then boot with airplane mode enabled, and leave airplane mode: only
  cell data is logged, not wifi data.

  Cheers,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-location-provider-here/+bug/1390490/+subscriptions

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

[Touch-packages] [Bug 1370327] Re: Add API to get UID for users

[Mathew Hodson]

https://launchpad.net/ubuntu/+source/lightdm/1.10.3-0ubuntu2 is
available in trusty-proposed.

---
lightdm (1.10.3-0ubuntu2) trusty; urgency=medium

  * Refresh patches

 -- Robert Ancell  Fri, 10 Oct 2014
21:24:51 +1300

lightdm (1.10.3-0ubuntu1) trusty; urgency=medium

  * New upstream release:
- Fix crash when having configuration keys defined in multiple places
  (LP: #1377373)
- Allow user switching in multi-seat until bug stopping greeter showing on
  logout is fixed
- Don't access .dmrc files until information from these files is required
  (LP: #1370852)
- Do timed autologin each time you are returned to the greeter
  (LP: #1302491)

 -- Robert Ancell  Thu, 09 Oct 2014
09:01:21 +1300

lightdm (1.10.2-0ubuntu1) trusty; urgency=medium

  * New upstream release:
- Use logind to provide the list of seats to use. This is disabled unless
  logind-load-seats (in [LightDM] section) is set to true. This is the
  default behaviour in lightdm 1.12. (LP: #1190581)
- Fix crash if running script hooks with non-X display servers.
  (LP: #1305006)
- Add a seat option 'allow-user-switching' that can disable all user
  switching for that seat. (LP: #1350357)
- Make PAM services configurable. (LP: #1348251)
- Add liblightdm method to get user UID. (LP: #1370327)
- Add a new session type 'mir-container' that allows the session to run
  inside a custom system compositor. (LP: #1359332)
- Add --show-config option that shows combined configuration.
- Use XDG_SESSION_ID from PAM instead of using the logind D-Bus API.
  (LP: #1364725)
- Make socket writing code used between greeter and daemon more robust to
  errors.
- Correct section name in default users.conf file.
- Fix tests failing with Qt 5.3 due to it checking getuid/geteuid which we
  are faking.
- Fix small memory leaks.
- Test improvements

 -- Robert Ancell  Wed, 17 Sep 2014
16:27:53 +1200

** Changed in: lightdm (Ubuntu Trusty)
   Status: New => Fix Committed

** Branch linked: lp:ubuntu/trusty-proposed/lightdm

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1370327

Title:
  Add API to get UID for users

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “lightdm” source package in Trusty:
  Fix Committed
Status in “lightdm” source package in Utopic:
  Fix Released

Bug description:
  [Impact]
  The LightDM user list provided to greeters via liblightdm doesn't have a 
method to access the user ID. This requires a greeter that might need this 
information to do a second lookup to get it.

  [Test Case]
  1. Write a greeter that needs the user ID
  Expected result:
  Can do it.
  Observed result:
  Can't do it.

  [Regression Potential]
  Low, the information was already in liblightdm, we just now expose it. Tested 
with regression tests.

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

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

[Touch-packages] [Bug 1190581] Re: Support logind's automatic multiseat feature

[Mathew Hodson]

** Branch linked: lp:ubuntu/trusty-proposed/lightdm

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1190581

Title:
  Support logind's automatic multiseat feature

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “lightdm” source package in Trusty:
  Fix Committed
Status in “lightdm” source package in Utopic:
  Fix Released
Status in “lightdm” package in Fedora:
  Unknown

Bug description:
  [Impact]
  LightDM does not use the information provided by logind to support automatic 
multi-seat setups. We have backported this support from LightDM 1.12 so this 
functionality can be used in 14.04 LTS. It is disabled by default.

  [Test Case]
  1. Enable multiseat in the LightDM configuration:
   [LightDM]
   logind-load-seats=true
  2. Start LightDM
  Expected result:
  The greeter is shown on both monitors and two sessions can be logged in.
  Observed result:
  Currently only one monitor / seat works.

  [Regression Potential]
  There is some risk of unrelated code being changed. This has been reduced by 
the use of regression tests, manual testing and providing this in the Ubuntu 
Desktop PPA.

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

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

[Touch-packages] [Bug 1350357] Re: Support disabling of user switching per seat

[Mathew Hodson]

https://launchpad.net/ubuntu/+source/lightdm/1.10.3-0ubuntu2 is
available in trusty-proposed.

---
lightdm (1.10.3-0ubuntu2) trusty; urgency=medium

  * Refresh patches

 -- Robert Ancell  Fri, 10 Oct 2014
21:24:51 +1300

lightdm (1.10.3-0ubuntu1) trusty; urgency=medium

  * New upstream release:
- Fix crash when having configuration keys defined in multiple places
  (LP: #1377373)
- Allow user switching in multi-seat until bug stopping greeter showing on
  logout is fixed
- Don't access .dmrc files until information from these files is required
  (LP: #1370852)
- Do timed autologin each time you are returned to the greeter
  (LP: #1302491)

 -- Robert Ancell  Thu, 09 Oct 2014
09:01:21 +1300

lightdm (1.10.2-0ubuntu1) trusty; urgency=medium

  * New upstream release:
- Use logind to provide the list of seats to use. This is disabled unless
  logind-load-seats (in [LightDM] section) is set to true. This is the
  default behaviour in lightdm 1.12. (LP: #1190581)
- Fix crash if running script hooks with non-X display servers.
  (LP: #1305006)
- Add a seat option 'allow-user-switching' that can disable all user
  switching for that seat. (LP: #1350357)
- Make PAM services configurable. (LP: #1348251)
- Add liblightdm method to get user UID. (LP: #1370327)
- Add a new session type 'mir-container' that allows the session to run
  inside a custom system compositor. (LP: #1359332)
- Add --show-config option that shows combined configuration.
- Use XDG_SESSION_ID from PAM instead of using the logind D-Bus API.
  (LP: #1364725)
- Make socket writing code used between greeter and daemon more robust to
  errors.
- Correct section name in default users.conf file.
- Fix tests failing with Qt 5.3 due to it checking getuid/geteuid which we
  are faking.
- Fix small memory leaks.
- Test improvements

 -- Robert Ancell  Wed, 17 Sep 2014
16:27:53 +1200

** Changed in: lightdm (Ubuntu Trusty)
   Status: Confirmed => Fix Committed

** Branch linked: lp:ubuntu/trusty-proposed/lightdm

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1350357

Title:
  Support disabling of user switching per seat

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “lightdm” source package in Trusty:
  Fix Committed
Status in “lightdm” source package in Utopic:
  Fix Released

Bug description:
  [Impact]
  No method of disabling user switching for LightDM. Some system administrators 
require this. There are methods to disable this inside the session but it is 
preferrable for a single method of doing this.

  [Test Case]
  1. Disable user switching in the LightDM configuration:
   [SeatDefaults]
   allow-user-switching=false
  2. Start LightDM
  3. Log in
  4. Attempt to switch user
  Expected result:
  User is unable to switch
  Observed result:
  Currently not supported - switching is allowed

  [Regression Potential]
  There is some risk of unrelated code being changed. This has been reduced by 
the use of regression tests, manual testing and providing this in the Ubuntu 
Desktop PPA.

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

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

[Touch-packages] [Bug 1305006] Re: Crashes running display server scripts for non X servers

[Mathew Hodson]

https://launchpad.net/ubuntu/+source/lightdm/1.10.3-0ubuntu2 is
available in trusty-proposed.

---
lightdm (1.10.3-0ubuntu2) trusty; urgency=medium

  * Refresh patches

 -- Robert Ancell  Fri, 10 Oct 2014
21:24:51 +1300

lightdm (1.10.3-0ubuntu1) trusty; urgency=medium

  * New upstream release:
- Fix crash when having configuration keys defined in multiple places
  (LP: #1377373)
- Allow user switching in multi-seat until bug stopping greeter showing on
  logout is fixed
- Don't access .dmrc files until information from these files is required
  (LP: #1370852)
- Do timed autologin each time you are returned to the greeter
  (LP: #1302491)

 -- Robert Ancell  Thu, 09 Oct 2014
09:01:21 +1300

lightdm (1.10.2-0ubuntu1) trusty; urgency=medium

  * New upstream release:
- Use logind to provide the list of seats to use. This is disabled unless
  logind-load-seats (in [LightDM] section) is set to true. This is the
  default behaviour in lightdm 1.12. (LP: #1190581)
- Fix crash if running script hooks with non-X display servers.
  (LP: #1305006)
- Add a seat option 'allow-user-switching' that can disable all user
  switching for that seat. (LP: #1350357)
- Make PAM services configurable. (LP: #1348251)
- Add liblightdm method to get user UID. (LP: #1370327)
- Add a new session type 'mir-container' that allows the session to run
  inside a custom system compositor. (LP: #1359332)
- Add --show-config option that shows combined configuration.
- Use XDG_SESSION_ID from PAM instead of using the logind D-Bus API.
  (LP: #1364725)
- Make socket writing code used between greeter and daemon more robust to
  errors.
- Correct section name in default users.conf file.
- Fix tests failing with Qt 5.3 due to it checking getuid/geteuid which we
  are faking.
- Fix small memory leaks.
- Test improvements

 -- Robert Ancell  Wed, 17 Sep 2014
16:27:53 +1200

** Changed in: lightdm (Ubuntu Trusty)
   Status: Triaged => Fix Committed

** Tags added: verification-needed

** Branch linked: lp:ubuntu/trusty-proposed/lightdm

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1305006

Title:
  Crashes running display server scripts for non X servers

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “lightdm” source package in Trusty:
  Fix Committed
Status in “lightdm” source package in Utopic:
  Fix Released

Bug description:
  [Impact]
  Running non X server setups (e.g. Unity 8) and having display server scripts 
configured leads to LightDM crashing. This is due to a faulty assumption in 
LightDM assuming all display servers are X servers. Commonly caused by having 
nVidia prime support installed. Error reports in [1].

  [Test Case]
  1. Install the Unity 8 desktop preview
  2. Configure a display setup script in the LightDM configuration:
   [SeatDefaults]
   display-setup-script=...
  3. Start LightDM
  4. Log in Unity 8
  Expected result:
  Setup script is run and you are logged into Unity 8
  Observed result:
  LightDM crashes

  [Regression Potential]
  Low, fix is simple. Tested with regression tests.

  [1]
  
https://errors.ubuntu.com/bucket/?id=/usr/sbin/lightdm%3A11%3Ax_server_local_get_authority_file_path%3Aseat_xlocal_run_script%3Arun_script%3Adisplay_server_ready_cb%3A_g_closure_invoke_va

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

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

[Touch-packages] [Bug 1190581] Re: Support logind's automatic multiseat feature

[Mathew Hodson]

https://launchpad.net/ubuntu/+source/lightdm/1.10.3-0ubuntu2 is
available in trusty-proposed.

---
lightdm (1.10.3-0ubuntu2) trusty; urgency=medium

  * Refresh patches

 -- Robert Ancell   Fri, 10 Oct 2014
21:24:51 +1300

lightdm (1.10.3-0ubuntu1) trusty; urgency=medium

  * New upstream release:
- Fix crash when having configuration keys defined in multiple places
  (LP: #1377373)
- Allow user switching in multi-seat until bug stopping greeter showing on
  logout is fixed
- Don't access .dmrc files until information from these files is required
  (LP: #1370852)
- Do timed autologin each time you are returned to the greeter
  (LP: #1302491)

 -- Robert Ancell   Thu, 09 Oct 2014
09:01:21 +1300

lightdm (1.10.2-0ubuntu1) trusty; urgency=medium

  * New upstream release:
- Use logind to provide the list of seats to use. This is disabled unless
  logind-load-seats (in [LightDM] section) is set to true. This is the
  default behaviour in lightdm 1.12. (LP: #1190581)
- Fix crash if running script hooks with non-X display servers.
  (LP: #1305006)
- Add a seat option 'allow-user-switching' that can disable all user
  switching for that seat. (LP: #1350357)
- Make PAM services configurable. (LP: #1348251)
- Add liblightdm method to get user UID. (LP: #1370327)
- Add a new session type 'mir-container' that allows the session to run
  inside a custom system compositor. (LP: #1359332)
- Add --show-config option that shows combined configuration.
- Use XDG_SESSION_ID from PAM instead of using the logind D-Bus API.
  (LP: #1364725)
- Make socket writing code used between greeter and daemon more robust to
  errors.
- Correct section name in default users.conf file.
- Fix tests failing with Qt 5.3 due to it checking getuid/geteuid which we
  are faking.
- Fix small memory leaks.
- Test improvements

 -- Robert Ancell   Wed, 17 Sep 2014
16:27:53 +1200

** Changed in: lightdm (Ubuntu Trusty)
   Status: Triaged => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1190581

Title:
  Support logind's automatic multiseat feature

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “lightdm” source package in Trusty:
  Fix Committed
Status in “lightdm” source package in Utopic:
  Fix Released
Status in “lightdm” package in Fedora:
  Unknown

Bug description:
  [Impact]
  LightDM does not use the information provided by logind to support automatic 
multi-seat setups. We have backported this support from LightDM 1.12 so this 
functionality can be used in 14.04 LTS. It is disabled by default.

  [Test Case]
  1. Enable multiseat in the LightDM configuration:
   [LightDM]
   logind-load-seats=true
  2. Start LightDM
  Expected result:
  The greeter is shown on both monitors and two sessions can be logged in.
  Observed result:
  Currently only one monitor / seat works.

  [Regression Potential]
  There is some risk of unrelated code being changed. This has been reduced by 
the use of regression tests, manual testing and providing this in the Ubuntu 
Desktop PPA.

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

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

[Touch-packages] [Bug 1190581] Re: Support logind's automatic multiseat feature

[Mathew Hodson]

** Bug watch removed: Red Hat Bugzilla #962907
   https://bugzilla.redhat.com/show_bug.cgi?id=962907

** Bug watch removed: freedesktop.org Bugzilla #69478
   https://bugs.freedesktop.org/show_bug.cgi?id=69478

** Bug watch removed: freedesktop.org Bugzilla #69477
   https://bugs.freedesktop.org/show_bug.cgi?id=69477

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1190581

Title:
  Support logind's automatic multiseat feature

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “lightdm” source package in Trusty:
  Triaged
Status in “lightdm” source package in Utopic:
  Fix Released
Status in “lightdm” package in Fedora:
  Unknown

Bug description:
  [Impact]
  LightDM does not use the information provided by logind to support automatic 
multi-seat setups. We have backported this support from LightDM 1.12 so this 
functionality can be used in 14.04 LTS. It is disabled by default.

  [Test Case]
  1. Enable multiseat in the LightDM configuration:
   [LightDM]
   logind-load-seats=true
  2. Start LightDM
  Expected result:
  The greeter is shown on both monitors and two sessions can be logged in.
  Observed result:
  Currently only one monitor / seat works.

  [Regression Potential]
  There is some risk of unrelated code being changed. This has been reduced by 
the use of regression tests, manual testing and providing this in the Ubuntu 
Desktop PPA.

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

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

[Touch-packages] [Bug 1383321] Re: Support XDG DesktopNames field in session files

[Mathew Hodson]

** Branch linked: lp:ubuntu/utopic-proposed/lightdm

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1383321

Title:
  Support XDG DesktopNames field in session files

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in Light Display Manager 1.12 series:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “lightdm” source package in Trusty:
  Fix Committed
Status in “lightdm” source package in Utopic:
  Fix Committed
Status in “lightdm” source package in Vivid:
  Fix Released

Bug description:
  [Impact]
  LightDM doesn't support the XDG standard "DesktopNames" field in session 
.desktop files. Instead we only support X-LightDM-DesktopName which was used 
before the standard was set. Newer sessions might expect DesktopNames to work.

  [Test Case]
  1. Install a session which has DesktopNames set in 
/usr/share/xsessions/name.desktop. i.e. DesktopNames=GNOME;Unity;
  2. Start this session
  Expected result:
  XDG_CURRENT_DESKTOP is set to GNOME:Unity
  Observed result:
  XDG_CURRENT_DESKTOP is not set

  [Regression Potential]
  Low. This feature is only activated if the field is set.

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

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

[Touch-packages] [Bug 1190344] Re: lightdm is leaking FDs -fix

[Mathew Hodson]

** Tags removed: fd fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1190344

Title:
  lightdm is leaking FDs -fix

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in Light Display Manager 1.12 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “lightdm” source package in Precise:
  Triaged
Status in “lightdm” source package in Trusty:
  Triaged
Status in “lightdm” source package in Utopic:
  Fix Committed
Status in “lightdm” source package in Vivid:
  Fix Released
Status in Fedora:
  Unknown

Bug description:
  [Impact]
  LightDM doesn't close the server side end of the pipes used to communicate 
with session processes. This means each session that is created leaks two file 
descriptors eventually leading to the system stopping it from creating new 
pipes.

  [Test Case]
  1. Start LightDM
  2. Check how many pipes are open
  # lsof -p {lightdm_pid} | grep FIFO | wc -l
  3. Create sessions by either cycling between users in Unity Greeter or 
logging in and out
  4. Check how many pipes exist using step 2.
  Expected result:
  No more pipes should be open
  Observed result:
  Many pipes remain open

  [Regression Potential]
  Low. Fix is to close pipes when finished with them. Tested with regression 
tests.

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

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

[Touch-packages] [Bug 1302491] Re: when autlogin with a timeout is used, it should be reapplied when the user logs out.

[Mathew Hodson]

** Changed in: lightdm (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Branch linked: lp:ubuntu/trusty-proposed/lightdm

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1302491

Title:
  when autlogin with a timeout is used, it should be reapplied when the
  user logs out.

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “lightdm” source package in Trusty:
  Fix Committed
Status in “lightdm” source package in Utopic:
  Fix Released

Bug description:
  [Impact]
  If LightDM is set up for timed login this only occurs on first login, i..e 
after a session logout timed login is not reattempted. This doesn't match the 
traditional behaviour of GDM. A common use case for timed login is kiosk setups 
where the greeter should never be displayed for any significant amount of time; 
this is currently impossible to set up with LightDM.

  [Test Case]
  1. Setup LightDM to do a timed login
  2. Wait for timeout
  (session starts)
  3. Log out of session
  Expected result:
  The session is started again after the timeout.
  Observed result:
  The greeter is show forever.

  [Regression potential]
  There is some risk that someone might have been relying on the existing 
behaviour. The assumption is that most timed login users would prefer the new 
behaviour. There is a small risk that these changes may have broken something 
else, this has been reduced by using the regression tests.

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

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

[Touch-packages] [Bug 1370852] Re: Scans all user accounts when not required

[Mathew Hodson]

** Changed in: lightdm (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Branch linked: lp:ubuntu/trusty-proposed/lightdm

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1370852

Title:
  Scans all user accounts when not required

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “lightdm” source package in Trusty:
  Fix Committed
Status in “lightdm” source package in Utopic:
  Fix Released

Bug description:
  [Impact]
  When AccountsService is not present on startup LightDM scans all the user 
accounts and attempts to access the dmrc file for each user. It does not use 
any information from the dmrc files. If you have many users and/or the dmrc 
files are on a slow filesystem this creates a big startup delay.

  [Test Case]
  1. Start LightDM on a system that doesn't have AccountsService and has many 
users
  Expected result:
  LightDM starts quickly
  Observed result:
  LightDM takes a long time to start

  [Regression potential]
  Low. We now only access the dmrc files when information from them i s 
required (lazy load). Tested with regression tests.

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

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

[Touch-packages] [Bug 1377373] Re: Variables defined twice in config files lead to crash

[Mathew Hodson]

** Changed in: lightdm (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Branch linked: lp:ubuntu/trusty-proposed/lightdm

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1377373

Title:
  Variables defined twice in config files lead to crash

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in Light Display Manager 1.12 series:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “lightdm” source package in Trusty:
  Fix Committed
Status in “lightdm” source package in Utopic:
  Fix Released
Status in “lightdm” package in Debian:
  Fix Released

Bug description:
  [Impact]
  Having the same configuration variable defined in two places causes LightDM 
to a double free and potentially crash.

  [Test Case]
  1. Install two configuration files in /etc/lightdm/lightdm.conf.d which both 
define the same variable.
  2. Run LightDM
  Expected result:
  LightDM runs correctly.
  Observed result:
  LightDM double frees a variable (seen with valgrind) and can crash.

  [Regression Potential]
  Low. The fix is not to double free the variable.

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

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

[Touch-packages] [Bug 1390490] Re: Race between connectivity-api and network-manager

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/ubuntu-location-provider-here

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to location-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1390490

Title:
  Race between connectivity-api and network-manager

Status in Ubuntu Location Provider Here:
  In Progress
Status in “location-service” package in Ubuntu:
  Fix Released
Status in “ubuntu-location-provider-here” package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  https://bugs.launchpad.net/ubuntu/+source/location-
  service/+bug/1389874 was a symptom for an issue with connectivity API
  which doesn't work when it starts before network-manager is started or
  when leaving airplane mode.

  To reproduce, create an upstart job like connectivity.conf with:
  start on started dbus

  console log

  respawn
  respawn limit unlimited

  script
  GLOG_logtostderr=1
  GLOG_v=200
  export GLOG_logtostderr GLOG_v
  exec /home/phablet/connectivity
  end script

  with connectivity from http://people.canonical.com/~lool/connectivity

  Then boot with airplane mode enabled, and leave airplane mode: only
  cell data is logged, not wifi data.

  Cheers,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-location-provider-here/+bug/1390490/+subscriptions

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

[Touch-packages] [Bug 1365490] Re: ubuntu 12.04.5 broken on VMware

[Mathew Hodson]

Tagging verification-done based on comment #14.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1365490

Title:
  ubuntu 12.04.5 broken on VMware

Status in “mesa” package in Ubuntu:
  Fix Released
Status in “mesa-lts-trusty” package in Ubuntu:
  Invalid
Status in “mesa-lts-trusty” source package in Precise:
  Fix Committed
Status in “mesa” source package in Trusty:
  Fix Released

Bug description:
  [Impact]

  A user might find Ubuntu 12.04.5 unusable on vmware because he would
  face a black screen after logging in. Although there is a workaround
  (disabling 3D) a user may have given up at that point.

  Backporting will help the user run the distro after upgrading, so I
  believe it's highly justified.

  [Test Case]

  On VMware Workstation 10, Install Ubuntu 12.04.5, preferrably using "easy 
install".
  Boot the VM, log in. You'll see a black screen only.

  [Regression Potential]

  The bug affects a function that impots a shared buffer to the 3D
  driver. The function is completely broken by the bug. Even if the
  patch should introduce another type of breakage, the problem couldn't
  be much worse than it already is, and should be confined to the
  specific function in question.

  [Other info]

  Due to different stack ordering of automatic variables, the bug may or
  may not be visible depending on the C compiler and the level of
  optimization used. For example, if -O0 -g is used the bug is not
  visible on 12.04.5. I have not encountered any symptoms of the bug yet
  on 14.04.

  [ Original bug report ]
  Ubuntu 12.04.5 shows a black screen after login with 3D enabled on
  VMware. This is due to a bug in the svga gallium driver's winsys.

  It's recently fixed in mesa master commit 2d6206140a, "winsys/svga: Fix
  incorrect type usage in IOCTL v2", with a request to backport to mesa
  stable, but I'm not sure whether anyone's still maintaining the 10.1 branch.

  Due to the severity of the symptoms it would be greatly appreciated if
  this fix could be incorporated in the
  libgl1-mesa-dri-lts-trusty package as soon as possible.

  Unfortunately it's affecting the package on the installation iso. Is
  there anything that can be done about that?

  Thanks,
  Thomas

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1365490/+subscriptions

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

[Touch-packages] [Bug 279368] Re: graphic problem when two or more folders for example are open

[Christopher M. Penalver]

DonPatricio, thank you for reporting this bug to Ubuntu. Intrepid reached EOL 
on April 30, 2010.
See this document for currently supported Ubuntu releases: 
https://wiki.ubuntu.com/Releases

Is this an issue in a supported release? If so, could you please execute the 
following command, as it will automatically gather debugging information, in a 
terminal:
apport-collect 279368

Please ensure you have xdiagnose installed, and that you click the Yes
button for attaching additional debugging information.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

** Package changed: ubuntu => xorg (Ubuntu)

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/279368

Title:
  graphic problem when two or more folders for example are open

Status in “xorg” package in Ubuntu:
  Incomplete

Bug description:
  This happens with a Nvidia Geforce fx 5700ve graphics card.
  just thought that i'd report that, because it looks really ugly.

  I am using Ubuntu 8.10 Beta with all updates installed.
  A screenshot is attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/279368/+subscriptions

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

[Touch-packages] [Bug 1391200] Re: Not configured for translations

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/ubuntu-ui-extras

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-extras in
Ubuntu.
https://bugs.launchpad.net/bugs/1391200

Title:
  Not configured for translations

Status in Ubuntu UI Toolkit Extras:
  In Progress
Status in “ubuntu-ui-extras” package in Ubuntu:
  Fix Released

Bug description:
  Using rtm 153, sharing a photo on facebook has an unstranslated "Post"
  button, that string comes from ubuntu-ui-extras but the project is not
  correctly configured for translations

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ui-extras/+bug/1391200/+subscriptions

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

[Touch-packages] [Bug 279368] [NEW] graphic problem when two or more folders for example are open

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

This happens with a Nvidia Geforce fx 5700ve graphics card.
just thought that i'd report that, because it looks really ugly.

I am using Ubuntu 8.10 Beta with all updates installed.
A screenshot is attached.

** Affects: xorg (Ubuntu)
 Importance: Low
 Status: Incomplete

-- 
graphic problem when two or more folders for example are open
https://bugs.launchpad.net/bugs/279368
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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

[Touch-packages] [Bug 1386682] Re: Facebook share is broken

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/webbrowser-app

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1386682

Title:
  Facebook share is broken

Status in The Webapps-core project:
  Fix Released
Status in Web Browser App:
  Fix Released
Status in “webbrowser-app” package in Ubuntu:
  Fix Released
Status in “webbrowser-app” package in Ubuntu RTM:
  In Progress

Bug description:
  Facebook share is broken.

  Testing:
  - make sure that you have a facebook account in the system settings,
  - go to the gallery app,
  - select a photo,
  - go to the share menu at the top and click share,
  - select the facebook app,
  - the app should start, there should be a sharing dialog with the picture,
  - enter some text in the text field and click share,
  - the screen should refresh (after the post is done) and you should see the 
picture with the text in your wall,

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-core/+bug/1386682/+subscriptions

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

[Touch-packages] [Bug 1351559] Re: Apps in spread are not anti-aliased

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/qtmir

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1351559

Title:
  Apps in spread are not anti-aliased

Status in Qt integration with the Mir display server:
  Fix Released
Status in “qtmir” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Fix Released
Status in “qtmir” package in Ubuntu RTM:
  In Progress
Status in “unity8” package in Ubuntu RTM:
  In Progress

Bug description:
  With qtcomp enabled, smoothing in the spread was disabled. This is
  unfortunately very visible on lower density devices, causing sharp
  edges on all diagonal lines.

  We need to investigate how to enable anti-aliasing with as little
  performance hit as possible.

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

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

[Touch-packages] [Bug 1351200] Re: Use stroke buttons in the toolbars

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/webbrowser-app

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1351200

Title:
  Use stroke buttons in the toolbars

Status in Web Browser App:
  Fix Released
Status in “webbrowser-app” package in Ubuntu:
  Fix Released
Status in “webbrowser-app” package in Ubuntu RTM:
  Confirmed

Bug description:
  The visual spec requires stroke buttons to be used in toolbars (e.g. in the 
tabs view or the history view).
  Stroke buttons are not available yet in the UITK (but work is in progress), 
this bug exists to track their use in webbrowser-app once available in the 
toolkit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/webbrowser-app/+bug/1351200/+subscriptions

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

[Touch-packages] [Bug 1342031] Re: Rename QML modules to follow qml-module-foo naming

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/accounts-qml-module

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to content-hub in Ubuntu.
https://bugs.launchpad.net/bugs/1342031

Title:
  Rename QML modules to follow qml-module-foo naming

Status in “accounts-qml-module” package in Ubuntu:
  Fix Released
Status in “address-book-app” package in Ubuntu:
  New
Status in “bacon2d” package in Ubuntu:
  Triaged
Status in “clickmanager-plugin” package in Ubuntu:
  New
Status in “content-hub” package in Ubuntu:
  New
Status in “cordova-ubuntu” package in Ubuntu:
  New
Status in “dee-qt” package in Ubuntu:
  New
Status in “gsettings-qt” package in Ubuntu:
  New
Status in “history-service” package in Ubuntu:
  New
Status in “libhud-qt” package in Ubuntu:
  Won't Fix
Status in “libqofono” package in Ubuntu:
  New
Status in “libusermetrics” package in Ubuntu:
  New
Status in “mediascanner2” package in Ubuntu:
  New
Status in “poppler-qml-plugin” package in Ubuntu:
  New
Status in “qml-box2d” package in Ubuntu:
  New
Status in “qml-friends” package in Ubuntu:
  New
Status in “qt3d-opensource-src” package in Ubuntu:
  New
Status in “qtconnectivity-opensource-src” package in Ubuntu:
  Fix Released
Status in “qtdeclarative-opensource-src” package in Ubuntu:
  Fix Released
Status in “qtgrilo” package in Ubuntu:
  New
Status in “qtlocation-opensource-src” package in Ubuntu:
  New
Status in “qtmultimedia-opensource-src” package in Ubuntu:
  Fix Released
Status in “qtpim-opensource-src” package in Ubuntu:
  Fix Released
Status in “qtquickcontrols-opensource-src” package in Ubuntu:
  Fix Released
Status in “qtsensors-opensource-src” package in Ubuntu:
  Fix Released
Status in “qtsystems-opensource-src” package in Ubuntu:
  Fix Released
Status in “reminders-app” package in Ubuntu:
  New
Status in “solid” package in Ubuntu:
  New
Status in “sync-monitor” package in Ubuntu:
  New
Status in “telephony-service” package in Ubuntu:
  Triaged
Status in “thumbnailer” package in Ubuntu:
  New
Status in “u1db-qt” package in Ubuntu:
  New
Status in “ubuntu-download-manager” package in Ubuntu:
  New
Status in “ubuntu-keyboard” package in Ubuntu:
  New
Status in “ubuntu-settings-components” package in Ubuntu:
  New
Status in “ubuntu-system-settings-online-accounts” package in Ubuntu:
  Fix Released
Status in “ubuntu-ui-extras” package in Ubuntu:
  New
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  New
Status in “ubuntuone-credentials” package in Ubuntu:
  New
Status in “unity-action-api” package in Ubuntu:
  Triaged
Status in “unity-notifications” package in Ubuntu:
  New
Status in “webbrowser-app” package in Ubuntu:
  Confirmed

Bug description:
  The package names of QML modules should be of the format qml-
  module-{$modulename}[version], a transition that was started during Qt
  5.3 preparation in Ubuntu. For example this could be qml-module-
  qtquick-localstorage or qml-module-qtsysteminfo for non versioned
  modules, and qml-module-ubuntu-webthing0.3 for versioned/co-
  installable modules.

  Further details in Debian e-mail:
  http://lists.alioth.debian.org/pipermail/pkg-kde-
  talk/2014-March/001889.html

  For Ubuntu, transitional packages should be put in place for smooth 
distribution upgrades, since we're shipping with the old names in previous 
Ubuntus. An example of that is at 
http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging/qtsystems-opensource-src/revision/31
 - in other words:
  - Make the old package a transitional oldlibs package that depends on the new 
package
  - Add Breaks/Replaces to the new package for the old non-transitional 
packages (be careful about the version number specification)
  - Keep Multi-Arch: same and Architecture: any for the transitional package
  - Write "QML module" instead of "QML plugin"
  - Rename also the *.install files

  ---
  One more example on naming:

  For example, the "test" (qtdeclarative5-test-plugin) in the old
  qtdeclarative5-style package naming became "qttest" (qml-module-
  qttest) in the new naming since the path is actually under
  /usr/lib/*/qt5/qml/QtTest/

  qml-module-qtquick-xmllistmodel has path
  /usr/lib/*/qt5/qml/QtQuick/XmlListModel, as an example if you have
  more than one subdir. /usr/lib/*/qt5/qml/Ubuntu/Connectivity/ would be
  qml-module-ubuntu-connectivity.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accounts-qml-module/+bug/1342031/+subscriptions

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

[Touch-packages] [Bug 234292] Re: laptop video output garbage

[Christopher M. Penalver]

kimus, thank you for reporting this bug to Ubuntu. Maverick reached EOL on 
April 10, 2012.
See this document for currently supported Ubuntu releases: 
https://wiki.ubuntu.com/Releases

Is this an issue in a supported release? If so, could you please execute the 
following command, as it will automatically gather debugging information, in a 
terminal:
apport-collect 234292

Please ensure you have xdiagnose installed, and that you click the Yes
button for attaching additional debugging information.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

** Package changed: ubuntu => xorg (Ubuntu)

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/234292

Title:
  laptop video output garbage

Status in “xorg” package in Ubuntu:
  Incomplete

Bug description:
  In my DELL Laptop (Precision M90) for some months and in a randomly
  manner my video output (monitor) just sends me garbage (like an out of
  sync). Even if I go to the console (Ctrl+F1) the video is in 'garbage
  mode'. Some times this problem doesn't happens one day but the next
  day may occur 2 or 3 times :-S.

  My only workaround is to go to suspend (Stand by) mode (Fn+Esc in my
  laptop) and when I wake up my laptop all is fine.

  I have the latest BIOS and proprietary nvidia-glx-new drivers. I did
  not find any thing abnormal in the Xorg log files after wake up from
  the suspend state.

  Please Help me. I'm getting desperate...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/234292/+subscriptions

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

[Touch-packages] [Bug 234292] [NEW] laptop video output garbage

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

In my DELL Laptop (Precision M90) for some months and in a randomly
manner my video output (monitor) just sends me garbage (like an out of
sync). Even if I go to the console (Ctrl+F1) the video is in 'garbage
mode'. Some times this problem doesn't happens one day but the next day
may occur 2 or 3 times :-S.

My only workaround is to go to suspend (Stand by) mode (Fn+Esc in my
laptop) and when I wake up my laptop all is fine.

I have the latest BIOS and proprietary nvidia-glx-new drivers. I did not
find any thing abnormal in the Xorg log files after wake up from the
suspend state.

Please Help me. I'm getting desperate...

** Affects: xorg (Ubuntu)
 Importance: Low
 Status: Incomplete

-- 
laptop video output garbage
https://bugs.launchpad.net/bugs/234292
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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

[Touch-packages] [Bug 1003950] Re: launcher does not show minimized update manager while clicked

[Linda]

I haven't experienced this bug in a while, but the only similarity in my
set up to Justin's is the multiple monitors.  My setup was a laptop and
external monitor.  I might have had them configured to show the dock on
both screens, but I've changed it to show only on the left, external
monitor screen.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1003950

Title:
  launcher does not show minimized update manager while clicked

Status in Unity:
  Fix Released
Status in Unity 5.0 series:
  Fix Released
Status in Unity 6.0 series:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “update-manager” package in Ubuntu:
  Confirmed
Status in “unity” source package in Precise:
  Fix Released
Status in “update-manager” source package in Precise:
  Confirmed
Status in “unity” source package in Quantal:
  Fix Released
Status in “update-manager” source package in Quantal:
  Confirmed

Bug description:
  Update manager is showing up in the dock but I can click on the icon
  all day and nothing happens. Similarly if I do Super-S or Super-W it
  doesn't show up anywhere.

  Even if I alt-tab to the application nothing shows up. This happens
  only when update manager runs on its own. If I kill it and then launch
  it myself it comes to the foreground just fine.

  I'm not 100% sure whether this is a unity, compiz, or update-manager
  bug but so far my bet is on unity.

  =Original Report=
  Bug #877444 is showing again in latest updates, please re-open it. This is 
the exact same problem.

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

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

[Touch-packages] [Bug 1335002] Re: Chinese input method does not work after enable Chinese keyboard in Ubuntu Phone

[XiaoGuo, Liu]

This problem still exists. it is not a good experience :)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1335002

Title:
  Chinese input method does not work after enable Chinese keyboard in
  Ubuntu Phone

Status in Ubuntu Keyboard:
  Confirmed
Status in “ubuntu-keyboard” package in Ubuntu:
  New
Status in “ubuntu-keyboard” package in Ubuntu RTM:
  New

Bug description:
  Reproduce steps:

  1, enable Chinese keyboard in system settings
  2, launch an app can input text like notes
  3, long press global icon and switch Chinese

  Expecting:
  user can input Chinese like press 'n' and 'i' then 你 should show up on 
candidate bar

  Actual:
  no candidate bar, so still input English

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-keyboard/+bug/1335002/+subscriptions

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

[Touch-packages] [Bug 1392928] [NEW] Cannot find the installed scope after installing a scope into the emulator

[XiaoGuo, Liu]

Public bug reported:

Cannot find the installed scope after installing a scope into the
emulator. I installed the scope from the "publish" button in the SDK. I
cannot find it even after I have restarted my emulator.

** Affects: unity-scopes-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: univ-train

** Tags added: univ-train

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-shell in
Ubuntu.
https://bugs.launchpad.net/bugs/1392928

Title:
  Cannot find the installed scope after installing a scope into the
  emulator

Status in “unity-scopes-shell” package in Ubuntu:
  New

Bug description:
  Cannot find the installed scope after installing a scope into the
  emulator. I installed the scope from the "publish" button in the SDK.
  I cannot find it even after I have restarted my emulator.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1392928/+subscriptions

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

[Touch-packages] [Bug 575778] Re: broadband card option 3g datacard 0af0:5000 initialization - card needs a second pin

[Bug Watch Updater]

** Changed in: network-manager
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/575778

Title:
  broadband card option 3g datacard 0af0:5000 initialization - card
  needs a second pin

Status in ModemManager (with NetworkManager support):
  New
Status in NetworkManager:
  Expired
Status in “modemmanager” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: modemmanager

  The older broadband card: option 3g datacard, that identifies itself using 
lsusb with
  Bus 009 Device 002: ID 0af0:5000 Option UMTS Card

  Needs a second pin at initialization, e.g. if your PIN is 1234 the correct 
sequence for initialization is:
  at+cpin="1234"
  at+cpin=""

  The card will acknowledge both command with "OK". The current modem-
  manager implementation does the first at+cpin="1234" step only, which
  is sufficient for most cards, except this one.

  If you initialize this card using "minicom" or setup and use "wvdial"
  for initialization only, you can continue using the network-manager
  and modem-manager as usual.

  Appended logs:
  1 Failed attempts with the default lucid setup:
1.1 modem_failed.log.txt
1.2 nm_failed.log.txt
  2 Successful attempts after an external at+cpin="" initialization
2.1 modem_success.log.txt
2.2 nm_success.log.txt 
  3. Output of the Python script mm-test.py: mm-test.log  

  Kind regards,
  Thorsten

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: modemmanager 0.3-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.32-21.32-generic-pae 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-21-generic-pae i686
  Architecture: i386
  Date: Wed May  5 14:58:52 2010
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406.1)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: modemmanager

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

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

[Touch-packages] [Bug 1391498] Re: [TOPBLOCKER] [Dash] In the app scope, replace the Ubuntu icon in the header with the word "Apps"

[Launchpad Bug Tracker]

This bug was fixed in the package unity-scope-click -
0.1.1+15.04.20141113~rtm-0ubuntu1

---
unity-scope-click (0.1.1+15.04.20141113~rtm-0ubuntu1) 14.09; urgency=low

  [ Ubuntu daily release ]
  * New rebuild forced

  [ Alejandro J. Cura ]
  * Remove ubuntu logo from apps scope (LP: #1391498)
 -- Ubuntu daily releaseThu, 13 Nov 2014 
04:36:07 +

** Changed in: unity-scope-click (Ubuntu RTM)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scope-click in
Ubuntu.
https://bugs.launchpad.net/bugs/1391498

Title:
  [TOPBLOCKER] [Dash] In the app scope, replace the Ubuntu icon in the
  header with the word "Apps"

Status in Ubuntu UX bugs:
  Fix Committed
Status in “unity-scope-click” package in Ubuntu:
  In Progress
Status in “unity-scope-click” package in Ubuntu RTM:
  Fix Released

Bug description:
  [Dash] In the app scope, replace the Ubuntu icon in the header with
  the word "Apps"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1391498/+subscriptions

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

[Touch-packages] [Bug 1357321] Re: [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu

[Lorn Potter]

Updated upstream. https://codereview.qt-project.org/#/c/99818/

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1357321

Title:
  [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu

Status in Platform API:
  Invalid
Status in The Savilerow project:
  New
Status in “network-manager” package in Ubuntu:
  Invalid
Status in “ofono” package in Ubuntu:
  Invalid
Status in “qtbase-opensource-src” package in Ubuntu:
  In Progress

Bug description:
  scope images load fine in wifi, but not on hsdpa even when there is
  good connectivity and browsing works well. Results are return, but
  images do not load.

To manage notifications about this bug go to:
https://bugs.launchpad.net/platform-api/+bug/1357321/+subscriptions

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

[Touch-packages] [Bug 678421] Re: Error message for a faulty ~/.profile script

[Gunnar Hjalmarsson]

On 2014-11-15 00:49, Barry Warsaw wrote:
> On Nov 14, 2014, at 11:38 PM, Gunnar Hjalmarsson wrote:
>> Right now I don't know how to best deal with this issue. Any
>> advice appreciated.
> 
> Probably use tee(1) to get the output both into the temp file and 
> ~/.xsession-errors.

Yeah.. But I fear that would make the code much more complicated. Or do
you have an idea, given the current code as shown in comment #33?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/678421

Title:
  Error message for a faulty ~/.profile script

Status in GDM: The Gnome Display Manager:
  New
Status in “gdm” package in Ubuntu:
  In Progress
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “gdm” source package in Trusty:
  Triaged
Status in “lightdm” source package in Trusty:
  In Progress
Status in “gdm” source package in Utopic:
  Triaged
Status in “lightdm” source package in Utopic:
  Fix Committed

Bug description:
  trusty and utopic SRU requests
  ==

  [Impact]

  In case of a syntax error in either of ~/.profile or a few other
  similar files, the Xorg login is interrupted, and the user is taken
  back to the login screen without an explanation. Debugging this
  problem may be a time consuming exercise, especially for non-
  experienced users.

  With the proposed change, lightdm/gdm does not try to load such a
  file, but shows a warning dialog instead. (A warning dialog is also
  shown in case of some other type of error, which would not have caused
  the login to fail.)

  [Test Case]

  To reproduce:

  * Edit ~/.profile and add something bad, e.g. a non-closed parenthesis.
  * Log out and find that you can't log in to a graphical session.

  After installing the proposed lightdm/gdm version, you'll instead see
  the dialog and can log in.

  [Regression Potential]

  Since this is only about improved exception handling, it does not at
  all affect users with correct configuration files. The regression risk
  ought to be minimal.

  [Original description]

  Binary package hint: gdm

  After adding "function AddPath { PATH="$1:$PATH" }" to $HOME/.profile
  made the Xorg startup fail. (At that moment I had already forgotten
  the changes made to the .profile). As I had autologin that meant it
  kept trying to login and finally showed me the graphics
  reconfiguration screen. That sent me to a huge hunt for xorg conf and
  setup problems.

  Anyway finally tracked this down. I had used bash syntax in .profile
  file whereas it was run with sh.

  This is not a bug per se but I think a user mistake in ".profile"
  shouldn't bring the whole xorg startup to a halt as it does with
  autologin. I propose running user ".profile" and ".xprofile" scripts
  so that Xsession script continues running even if they have errors.
  I'm not sure whether this change would have some negative effects as
  well.

  1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct 
16 19:48:22 UTC 2010 i686 GNU/Linux
  2) gdm 2.30.2.is.2.30.0-0ubuntu4

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

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

[Touch-packages] [Bug 1392910] [NEW] Valid links placed on desktop reported as broken after logon

[f(fanta)]

Public bug reported:

Steps to reproduce:
- place on the Desktop some symbolic links to directories that are somewhere 
below /media (e.g. with drag-and-drop from "Files")
- restart ubuntu and log on again
- the links now appear in the desktop as broken links (with a padlock in the 
icon, see attached screenshot)
- clicking on the link icon and try to open it, you get an error message, and 
the linked directory does not open; the directory is expected to open in "Files"

Workaround: 
- navigate to the linked directory by mean of "Files" or with command "CD" in a 
shell
- click on the background of the desktop
- hit F5 on the keyboard
- now the links change icon, and by clicking on them they open as expected

The issue is systematic.

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
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Sat Nov 15 01:20:02 2014
InstallationDate: Installed on 2014-11-12 (2 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug utopic

** Attachment added: "Screenshot from 2014-11-15 01:05:49.png"
   
https://bugs.launchpad.net/bugs/1392910/+attachment/4260834/+files/Screenshot%20from%202014-11-15%2001%3A05%3A49.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1392910

Title:
  Valid links placed on desktop reported as broken after logon

Status in “unity” package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  - place on the Desktop some symbolic links to directories that are somewhere 
below /media (e.g. with drag-and-drop from "Files")
  - restart ubuntu and log on again
  - the links now appear in the desktop as broken links (with a padlock in the 
icon, see attached screenshot)
  - clicking on the link icon and try to open it, you get an error message, and 
the linked directory does not open; the directory is expected to open in "Files"

  Workaround: 
  - navigate to the linked directory by mean of "Files" or with command "CD" in 
a shell
  - click on the background of the desktop
  - hit F5 on the keyboard
  - now the links change icon, and by clicking on them they open as expected

  The issue is systematic.

  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
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sat Nov 15 01:20:02 2014
  InstallationDate: Installed on 2014-11-12 (2 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  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/1392910/+subscriptions

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

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

[david howell]

I am having same exact issue on brand-new install of 14.04 on homegrown
computer. I am new to Linux... Just got tired of Windows when WIN8 was
released. Learning about ctrl+alt+f1 will be helpful until a fix (?) Is
released.

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

Title:
  Lock screen after idle time freezes unity

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

Bug description:
  Hello,

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 678421] Re: Error message for a faulty ~/.profile script

[Gunnar Hjalmarsson]

I created the file /etc/profile.d/wrong.sh with a sh syntax error. With
lightdm 1.12.1-0ubuntu1 the reason for the login failure is logged in
~/.xsession-errors, but with the latest lightdm version it's not. So
there is a regression with the fix of this bug.

The reason is that stderr is temporarily redirected to /tmp/config-err-
XX. Actually, if you are thrown back to the login screen and log in
via a console to investigate the reason, you can find the error message
in that /tmp file. OTOH, that's not documented anywhere...

Right now I don't know how to best deal with this issue. Any advice
appreciated.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/678421

Title:
  Error message for a faulty ~/.profile script

Status in GDM: The Gnome Display Manager:
  New
Status in “gdm” package in Ubuntu:
  In Progress
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “gdm” source package in Trusty:
  Triaged
Status in “lightdm” source package in Trusty:
  In Progress
Status in “gdm” source package in Utopic:
  Triaged
Status in “lightdm” source package in Utopic:
  Fix Committed

Bug description:
  trusty and utopic SRU requests
  ==

  [Impact]

  In case of a syntax error in either of ~/.profile or a few other
  similar files, the Xorg login is interrupted, and the user is taken
  back to the login screen without an explanation. Debugging this
  problem may be a time consuming exercise, especially for non-
  experienced users.

  With the proposed change, lightdm/gdm does not try to load such a
  file, but shows a warning dialog instead. (A warning dialog is also
  shown in case of some other type of error, which would not have caused
  the login to fail.)

  [Test Case]

  To reproduce:

  * Edit ~/.profile and add something bad, e.g. a non-closed parenthesis.
  * Log out and find that you can't log in to a graphical session.

  After installing the proposed lightdm/gdm version, you'll instead see
  the dialog and can log in.

  [Regression Potential]

  Since this is only about improved exception handling, it does not at
  all affect users with correct configuration files. The regression risk
  ought to be minimal.

  [Original description]

  Binary package hint: gdm

  After adding "function AddPath { PATH="$1:$PATH" }" to $HOME/.profile
  made the Xorg startup fail. (At that moment I had already forgotten
  the changes made to the .profile). As I had autologin that meant it
  kept trying to login and finally showed me the graphics
  reconfiguration screen. That sent me to a huge hunt for xorg conf and
  setup problems.

  Anyway finally tracked this down. I had used bash syntax in .profile
  file whereas it was run with sh.

  This is not a bug per se but I think a user mistake in ".profile"
  shouldn't bring the whole xorg startup to a halt as it does with
  autologin. I propose running user ".profile" and ".xprofile" scripts
  so that Xsession script continues running even if they have errors.
  I'm not sure whether this change would have some negative effects as
  well.

  1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct 
16 19:48:22 UTC 2010 i686 GNU/Linux
  2) gdm 2.30.2.is.2.30.0-0ubuntu4

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

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

Re: [Touch-packages] [Bug 678421] Re: Error message for a faulty ~/.profile script

[Barry Warsaw]

On Nov 14, 2014, at 11:38 PM, Gunnar Hjalmarsson wrote:

>Right now I don't know how to best deal with this issue. Any advice
>appreciated.

Probably use tee(1) to get the output both into the temp file and
~/.xsession-errors.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/678421

Title:
  Error message for a faulty ~/.profile script

Status in GDM: The Gnome Display Manager:
  New
Status in “gdm” package in Ubuntu:
  In Progress
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “gdm” source package in Trusty:
  Triaged
Status in “lightdm” source package in Trusty:
  In Progress
Status in “gdm” source package in Utopic:
  Triaged
Status in “lightdm” source package in Utopic:
  Fix Committed

Bug description:
  trusty and utopic SRU requests
  ==

  [Impact]

  In case of a syntax error in either of ~/.profile or a few other
  similar files, the Xorg login is interrupted, and the user is taken
  back to the login screen without an explanation. Debugging this
  problem may be a time consuming exercise, especially for non-
  experienced users.

  With the proposed change, lightdm/gdm does not try to load such a
  file, but shows a warning dialog instead. (A warning dialog is also
  shown in case of some other type of error, which would not have caused
  the login to fail.)

  [Test Case]

  To reproduce:

  * Edit ~/.profile and add something bad, e.g. a non-closed parenthesis.
  * Log out and find that you can't log in to a graphical session.

  After installing the proposed lightdm/gdm version, you'll instead see
  the dialog and can log in.

  [Regression Potential]

  Since this is only about improved exception handling, it does not at
  all affect users with correct configuration files. The regression risk
  ought to be minimal.

  [Original description]

  Binary package hint: gdm

  After adding "function AddPath { PATH="$1:$PATH" }" to $HOME/.profile
  made the Xorg startup fail. (At that moment I had already forgotten
  the changes made to the .profile). As I had autologin that meant it
  kept trying to login and finally showed me the graphics
  reconfiguration screen. That sent me to a huge hunt for xorg conf and
  setup problems.

  Anyway finally tracked this down. I had used bash syntax in .profile
  file whereas it was run with sh.

  This is not a bug per se but I think a user mistake in ".profile"
  shouldn't bring the whole xorg startup to a halt as it does with
  autologin. I propose running user ".profile" and ".xprofile" scripts
  so that Xsession script continues running even if they have errors.
  I'm not sure whether this change would have some negative effects as
  well.

  1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct 
16 19:48:22 UTC 2010 i686 GNU/Linux
  2) gdm 2.30.2.is.2.30.0-0ubuntu4

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

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

[Touch-packages] [Bug 1392888] [NEW] Mixed optimization and pragma settings cause ‘__open_too_many_args’ compile error

[Alan Chen]

Public bug reported:

Sample program below compiles with gcc with no errors, but results with
a compile error with g++

g++ version: 4.8.2-19ubuntu1

gcc -O2 prog.c  # ok
g++ -O2 prog.c  # error

In file included from /usr/include/fcntl.h:279:0,
 from prog.c:5:
In function ‘int open(const char*, int, ...)’,
inlined from ‘int main()’ at prog.c:12:40:
/usr/include/x86_64-linux-gnu/bits/fcntl2.h:44:28: error: call to 
‘__open_too_many_args’ declared with attribute error: open can be called either 
with 2 or 3 arguments, not more
 __open_too_many_args ();

Sample program:

#pragma GCC optimize ("O0")

#include 
#include 

int main()
{
 int fd;

 fd = open( "filename", O_RDONLY, 0644);
 if (fd < 0) return 1;

 close(fd);

 return 0;
}

** Affects: gcc-4.8 (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  Sample program below compiles with gcc with no errors, but results with
  a compile error with g++
  
  g++ version: 4.8.2-19ubuntu1
  
  gcc -O2 prog.c  # ok
  g++ -O2 prog.c  # error
  
  In file included from /usr/include/fcntl.h:279:0,
-  from prog.c:6:
+  from prog.c:5:
  In function ‘int open(const char*, int, ...)’,
- inlined from ‘int main()’ at prog.c:12:40:
+ inlined from ‘int main()’ at prog.c:12:40:
  /usr/include/x86_64-linux-gnu/bits/fcntl2.h:44:28: error: call to 
‘__open_too_many_args’ declared with attribute error: open can be called either 
with 2 or 3 arguments, not more
-  __open_too_many_args ();
- 
+  __open_too_many_args ();
  
  Sample program:
  
  #pragma GCC optimize ("O0")
  
  #include 
  #include 
  
  int main()
  {
-   int fd;
+  int fd;
  
-   fd = open( "filename", O_RDONLY, 0644);
-   if (fd < 0) return 1;
+  fd = open( "filename", O_RDONLY, 0644);
+  if (fd < 0) return 1;
  
- close(fd);
+  close(fd);
  
-   return 0;
+  return 0;
  }

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1392888

Title:
  Mixed optimization and pragma settings cause ‘__open_too_many_args’
  compile error

Status in “gcc-4.8” package in Ubuntu:
  New

Bug description:
  Sample program below compiles with gcc with no errors, but results
  with a compile error with g++

  g++ version: 4.8.2-19ubuntu1

  gcc -O2 prog.c  # ok
  g++ -O2 prog.c  # error

  In file included from /usr/include/fcntl.h:279:0,
   from prog.c:5:
  In function ‘int open(const char*, int, ...)’,
  inlined from ‘int main()’ at prog.c:12:40:
  /usr/include/x86_64-linux-gnu/bits/fcntl2.h:44:28: error: call to 
‘__open_too_many_args’ declared with attribute error: open can be called either 
with 2 or 3 arguments, not more
   __open_too_many_args ();

  Sample program:

  #pragma GCC optimize ("O0")

  #include 
  #include 

  int main()
  {
   int fd;

   fd = open( "filename", O_RDONLY, 0644);
   if (fd < 0) return 1;

   close(fd);

   return 0;
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1392888/+subscriptions

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

[Touch-packages] [Bug 1271839] Re: ibus-ui-gtk3 big memory leak

[hrvooje]

Happend to me too on Ubuntu 14.04 64bit. ibus-ui-gtk3 has taken 1,6GB of
RAM

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1271839

Title:
  ibus-ui-gtk3 big memory leak

Status in “ibus” package in Ubuntu:
  Expired

Bug description:
  ubuntu 13.10 64bit
  2gb of memory leak

  Also seen on Ubuntu 14.04 64Bit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1271839/+subscriptions

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

Re: [Touch-packages] [Bug 678421] Re: Error message for a faulty ~/.profile script

[Barry Warsaw]

On Nov 14, 2014, at 09:59 PM, Gunnar Hjalmarsson wrote:

>I don't know. Syntax errors directly in e.g. ~/.profile or /etc/profile
>are logged in ~/.xsession-errors both with the latest lightdm version
>and with previous versions, but I don't know whether syntax errors in
>files which are sourced from those files are logged anywhere.

I guess they aren't because ~/.xsession-errors is empty when lightdm exits
back to the login screen. :(

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/678421

Title:
  Error message for a faulty ~/.profile script

Status in GDM: The Gnome Display Manager:
  New
Status in “gdm” package in Ubuntu:
  In Progress
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “gdm” source package in Trusty:
  Triaged
Status in “lightdm” source package in Trusty:
  In Progress
Status in “gdm” source package in Utopic:
  Triaged
Status in “lightdm” source package in Utopic:
  Fix Committed

Bug description:
  trusty and utopic SRU requests
  ==

  [Impact]

  In case of a syntax error in either of ~/.profile or a few other
  similar files, the Xorg login is interrupted, and the user is taken
  back to the login screen without an explanation. Debugging this
  problem may be a time consuming exercise, especially for non-
  experienced users.

  With the proposed change, lightdm/gdm does not try to load such a
  file, but shows a warning dialog instead. (A warning dialog is also
  shown in case of some other type of error, which would not have caused
  the login to fail.)

  [Test Case]

  To reproduce:

  * Edit ~/.profile and add something bad, e.g. a non-closed parenthesis.
  * Log out and find that you can't log in to a graphical session.

  After installing the proposed lightdm/gdm version, you'll instead see
  the dialog and can log in.

  [Regression Potential]

  Since this is only about improved exception handling, it does not at
  all affect users with correct configuration files. The regression risk
  ought to be minimal.

  [Original description]

  Binary package hint: gdm

  After adding "function AddPath { PATH="$1:$PATH" }" to $HOME/.profile
  made the Xorg startup fail. (At that moment I had already forgotten
  the changes made to the .profile). As I had autologin that meant it
  kept trying to login and finally showed me the graphics
  reconfiguration screen. That sent me to a huge hunt for xorg conf and
  setup problems.

  Anyway finally tracked this down. I had used bash syntax in .profile
  file whereas it was run with sh.

  This is not a bug per se but I think a user mistake in ".profile"
  shouldn't bring the whole xorg startup to a halt as it does with
  autologin. I propose running user ".profile" and ".xprofile" scripts
  so that Xsession script continues running even if they have errors.
  I'm not sure whether this change would have some negative effects as
  well.

  1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct 
16 19:48:22 UTC 2010 i686 GNU/Linux
  2) gdm 2.30.2.is.2.30.0-0ubuntu4

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

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

[Touch-packages] [Bug 1357321] Re: [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu

[Lorn Potter]

When I run that test on the phone, it does not crash and passes.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1357321

Title:
  [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu

Status in Platform API:
  Invalid
Status in The Savilerow project:
  New
Status in “network-manager” package in Ubuntu:
  Invalid
Status in “ofono” package in Ubuntu:
  Invalid
Status in “qtbase-opensource-src” package in Ubuntu:
  In Progress

Bug description:
  scope images load fine in wifi, but not on hsdpa even when there is
  good connectivity and browsing works well. Results are return, but
  images do not load.

To manage notifications about this bug go to:
https://bugs.launchpad.net/platform-api/+bug/1357321/+subscriptions

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

[Touch-packages] [Bug 1386721] Re: Graphics Slow After Upgrade 14.04 - 14.10

[Gann Bierner]

I see this too on my Thinkpad T410 (14.10 upgraded from 14.04).  Chrome
is particularly bad but, strangely, it's much worse when maximized.
When not maximized, refresh is still slow but not as unbearable.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1386721

Title:
  Graphics Slow After Upgrade 14.04 - 14.10

Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  Using Gnome Ubuntu 14.10, Dell XPS 13, intel 915 Graphics

  After upgrading from 14.04 to 14.10 there are a lot of places where
  the graphics are working much slower than they were before:

  - Gnome Shell Interface is very sluggish, visible "chops" (redrawing)
  when pressing the [Super] key.

  - Selecting text in Gedit takes a full second pr. line

  Experiences some subjective improvement when I booted kernel 3.13.0-37
  instead of 3.16.0-23, but that may be my imagination as the problem
  persists.

  I've searched google, forums, found a couple of relevant links that
  point to the issue being the Intel drivers.

  http://askubuntu.com/questions/53962...E2%86%92-14-10
  http://www.webupd8.org/2014/10/ubunt...ent-1652086424

  But the drivers currently in 14.10 should be newer than those supplied
  by Intel to 14.04 so that doesn't make sense to me. As one Intel
  developer wrote:

  "I would like to point out that since what we do is bring more ecent
  versions of the software to the target distributions than they ship
  with, a 14.04 targeted installer is unlikely to bring much to a 14.10
  installation, which most likely has the same or more recent versions
  already anyway."

  Source: https://01.org/linuxgraphics/node/375

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Oct 28 15:24:30 2014
  DistUpgraded: 2014-10-25 20:59:36,052 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus: i915-3.15-3.13, 0.01, 3.13.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:060a]
  InstallationDate: Installed on 2014-06-14 (135 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  MachineType: Dell Inc. XPS13 9333
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic 
root=UUID=105bbbd1-365e-4063-bdca-fc5431faf5dc ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to utopic on 2014-10-25 (2 days ago)
  dmi.bios.date: 12/11/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0GFTRT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  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: Tue Oct 28 13:44:57 2014
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4933
   vendor CMN
  xserver.version: 2:1.16.0-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1386721/+subscriptions

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

[Touch-packages] [Bug 1377624] Re: udev requires hotplug support, thus upgrades fail

[Andrzej Kłapeć]

I'm also experiencing this issue on my 14.04 OVH VPS. It's running
2.6.32-042stab093.5 kernel, btw.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1377624

Title:
  udev requires hotplug support, thus upgrades fail

Status in “systemd” package in Ubuntu:
  Confirmed

Bug description:
  I'm running 14.04 LTS in an OpenVZ container.

  Upgrades failed today, due to failure to configure udev:
  $ sudo apt-get dist-upgrade
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  3 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Setting up udev (204-5ubuntu20.7) ...
   * udev requires hotplug support, not started
 ...fail!
  invoke-rc.d: initscript udev, action "restart" failed.
  dpkg: error processing package udev (--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of systemd-services:
   systemd-services depends on udev (>= 175-0ubuntu23); however:
Package udev is not configured yet.

  dpkg: error processing package systemd-services (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of libpam-systemd:amd64:
   libpam-systemd:amd64 depends on systemd-services (= 204-5ubuntu20.7); 
however:
Package systemd-services is not configured yet.

  dpkg: error processing package libpam-systemd:amd64 (--configure):
   dependency problems - leaving unconfigured
  Errors were encountered while processing:
   udev
   systemd-services
   libpam-systemd:amd64
  E: Sub-process /usr/bin/dpkg returned an error code (1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1377624/+subscriptions

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

[Touch-packages] [Bug 678421] Re: Error message for a faulty ~/.profile script

[Gunnar Hjalmarsson]

On 2014-11-14 21:45, Barry Warsaw wrote:
> On Nov 14, 2014, at 08:15 PM, Gunnar Hjalmarsson wrote:
>> Being thrown back indicates a syntax error.
> 
> Are those errors logged anywhere permanently?

I don't know. Syntax errors directly in e.g. ~/.profile or /etc/profile
are logged in ~/.xsession-errors both with the latest lightdm version
and with previous versions, but I don't know whether syntax errors in
files which are sourced from those files are logged anywhere.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/678421

Title:
  Error message for a faulty ~/.profile script

Status in GDM: The Gnome Display Manager:
  New
Status in “gdm” package in Ubuntu:
  In Progress
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “gdm” source package in Trusty:
  Triaged
Status in “lightdm” source package in Trusty:
  In Progress
Status in “gdm” source package in Utopic:
  Triaged
Status in “lightdm” source package in Utopic:
  Fix Committed

Bug description:
  trusty and utopic SRU requests
  ==

  [Impact]

  In case of a syntax error in either of ~/.profile or a few other
  similar files, the Xorg login is interrupted, and the user is taken
  back to the login screen without an explanation. Debugging this
  problem may be a time consuming exercise, especially for non-
  experienced users.

  With the proposed change, lightdm/gdm does not try to load such a
  file, but shows a warning dialog instead. (A warning dialog is also
  shown in case of some other type of error, which would not have caused
  the login to fail.)

  [Test Case]

  To reproduce:

  * Edit ~/.profile and add something bad, e.g. a non-closed parenthesis.
  * Log out and find that you can't log in to a graphical session.

  After installing the proposed lightdm/gdm version, you'll instead see
  the dialog and can log in.

  [Regression Potential]

  Since this is only about improved exception handling, it does not at
  all affect users with correct configuration files. The regression risk
  ought to be minimal.

  [Original description]

  Binary package hint: gdm

  After adding "function AddPath { PATH="$1:$PATH" }" to $HOME/.profile
  made the Xorg startup fail. (At that moment I had already forgotten
  the changes made to the .profile). As I had autologin that meant it
  kept trying to login and finally showed me the graphics
  reconfiguration screen. That sent me to a huge hunt for xorg conf and
  setup problems.

  Anyway finally tracked this down. I had used bash syntax in .profile
  file whereas it was run with sh.

  This is not a bug per se but I think a user mistake in ".profile"
  shouldn't bring the whole xorg startup to a halt as it does with
  autologin. I propose running user ".profile" and ".xprofile" scripts
  so that Xsession script continues running even if they have errors.
  I'm not sure whether this change would have some negative effects as
  well.

  1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct 
16 19:48:22 UTC 2010 i686 GNU/Linux
  2) gdm 2.30.2.is.2.30.0-0ubuntu4

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

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

[Touch-packages] [Bug 1355984] Re: Built in speakers do not work on iMac 14, 2

[Christopher M. Penalver]

Paul, did this issue not occur in a release prior to Raring without any
WORKAROUNDs (ex. Precise 12.04.0 with kernel 3.2.x)?

As well, could you please test the latest mainline kernel 3.18-rc4 and
advise to the results?

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1355984

Title:
  Built in speakers do not work on iMac 14,2

Status in “alsa-driver” package in Ubuntu:
  New
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Xubuntu 14.04 on iMac 14,2 no sound from internal speakers. Loud and clear 
using OSX 10.9.4. Also tried installing Lubuntu (no sound at all) Linux Mint 16 
& 17 and Ubuntu 13.04, 13.10 (same problem as Xubuntu).
  Have all PulseAudio utils installed, all devices are listed but only analogue 
volume meter shows outputs when playing but as above nothing from speakers.
  AlsaMixer shows S/PDIF (highlighted), SPDIF 1 & S/PDIF 2 not MM, set at 00 
but cannot be adjusted.

  To get the headphones to work I upgraded to the daily ALSA snapshot
  found here: https://code.launchpad.net/~ubuntu-audio-
  dev/+archive/ubuntu/alsa-daily/+packages

  The output of alsa-info.sh is here: 
http://www.alsa-project.org/db/?f=08cf13552b70232c96fea9293fdd54066243d79a I 
have downloaded the HDA Analyzer tool but I can't seem to get the internal 
speakers to work correctly in any consistent way, although they do occasionally 
work correctly for a few seconds. I can consistently make sound come from the 
speakers if I chose VREF = 50 or 80 in Node[0x0d]pin but it sounds like I am 
using a much smaller lower quality speaker when I do that. Here is the text 
dump for that node configuration:
  Node 0x0d [Pin Complex] wcaps 0x41048b: Stereo Amp-In
    Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
    Amp-In vals: [0x00 0x00]
    Pincap 0x1764: IN Detect Balance
  Vref caps: HIZ 50 GRD 80
    Pin Default 0x40f0: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0xf, Sequence = 0x0
    Unsolicited: tag=0x00, enabled=0
    Power: setting=D0, actual=D0
    Delay: 1 samples

  WORKAROUND for the headphones only: # echo "options snd-hda-intel
  model=imac27_122" >> /etc/modprobe.d/imac_local.conf followed by a
  reboot.

  ---
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ladmin 1910 F pulseaudio
   /dev/snd/controlC0:  ladmin 1910 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-08-11 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Apple Inc. iMac14,2
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-33-generic.efi.signed 
root=UUID=2f77d057-5c9c-42d8-b2c0-18507f43420e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-33.58-generic 3.13.11.4
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-33-generic N/A
   linux-backports-modules-3.13.0-33-generic  N/A
   linux-firmware 1.127.5
  Tags:  trusty trusty
  Uname: Linux 3.13.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/14/2014
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: IM142.88Z.0118.B02.1403141302
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-27ADBB7B4CEE8E61
  dmi.board.vendor: Apple Inc.
  dmi.board.version: iMac14,2
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-27ADBB7B4CEE8E61
  dmi.modalias: 
dmi:bvnAppleInc.:bvrIM142.88Z.0118.B02.1403141302:bd03/14/2014:svnAppleInc.:pniMac14,2:pvr1.0:rvnAppleInc.:rnMac-27ADBB7B4CEE8E61:rvriMac14,2:cvnAppleInc.:ct13:cvrMac-27ADBB7B4CEE8E61:
  dmi.product.name: iMac14,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1355984/+subscriptions

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

[Touch-packages] [Bug 1355984] Re: Built in speakers do not work on iMac 14, 2

[Christopher M. Penalver]

** Tags added: raring saucy

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1355984

Title:
  Built in speakers do not work on iMac 14,2

Status in “alsa-driver” package in Ubuntu:
  New
Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu 14.04 on iMac 14,2 no sound from internal speakers. Loud and clear 
using OSX 10.9.4. Also tried installing Lubuntu (no sound at all) Linux Mint 16 
& 17 and Ubuntu 13.04, 13.10 (same problem as Xubuntu).
  Have all PulseAudio utils installed, all devices are listed but only analogue 
volume meter shows outputs when playing but as above nothing from speakers.
  AlsaMixer shows S/PDIF (highlighted), SPDIF 1 & S/PDIF 2 not MM, set at 00 
but cannot be adjusted.

  To get the headphones to work I upgraded to the daily ALSA snapshot
  found here: https://code.launchpad.net/~ubuntu-audio-
  dev/+archive/ubuntu/alsa-daily/+packages

  The output of alsa-info.sh is here: 
http://www.alsa-project.org/db/?f=08cf13552b70232c96fea9293fdd54066243d79a I 
have downloaded the HDA Analyzer tool but I can't seem to get the internal 
speakers to work correctly in any consistent way, although they do occasionally 
work correctly for a few seconds. I can consistently make sound come from the 
speakers if I chose VREF = 50 or 80 in Node[0x0d]pin but it sounds like I am 
using a much smaller lower quality speaker when I do that. Here is the text 
dump for that node configuration:
  Node 0x0d [Pin Complex] wcaps 0x41048b: Stereo Amp-In
    Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
    Amp-In vals: [0x00 0x00]
    Pincap 0x1764: IN Detect Balance
  Vref caps: HIZ 50 GRD 80
    Pin Default 0x40f0: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0xf, Sequence = 0x0
    Unsolicited: tag=0x00, enabled=0
    Power: setting=D0, actual=D0
    Delay: 1 samples

  WORKAROUND for the headphones only: # echo "options snd-hda-intel
  model=imac27_122" >> /etc/modprobe.d/imac_local.conf followed by a
  reboot.

  ---
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ladmin 1910 F pulseaudio
   /dev/snd/controlC0:  ladmin 1910 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-08-11 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Apple Inc. iMac14,2
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-33-generic.efi.signed 
root=UUID=2f77d057-5c9c-42d8-b2c0-18507f43420e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-33.58-generic 3.13.11.4
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-33-generic N/A
   linux-backports-modules-3.13.0-33-generic  N/A
   linux-firmware 1.127.5
  Tags:  trusty trusty
  Uname: Linux 3.13.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/14/2014
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: IM142.88Z.0118.B02.1403141302
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-27ADBB7B4CEE8E61
  dmi.board.vendor: Apple Inc.
  dmi.board.version: iMac14,2
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-27ADBB7B4CEE8E61
  dmi.modalias: 
dmi:bvnAppleInc.:bvrIM142.88Z.0118.B02.1403141302:bd03/14/2014:svnAppleInc.:pniMac14,2:pvr1.0:rvnAppleInc.:rnMac-27ADBB7B4CEE8E61:rvriMac14,2:cvnAppleInc.:ct13:cvrMac-27ADBB7B4CEE8E61:
  dmi.product.name: iMac14,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1355984/+subscriptions

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

[Touch-packages] [Bug 1372548] Re: Phone field doesn't accept symbols #*()

[Bill Filler]

** Also affects: address-book-app (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: address-book-app (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Changed in: address-book-app (Ubuntu)
   Importance: Undecided => High

** Changed in: address-book-app (Ubuntu RTM)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to address-book-app in
Ubuntu.
https://bugs.launchpad.net/bugs/1372548

Title:
  Phone field doesn't accept symbols #*()

Status in Address Book App:
  Confirmed
Status in “address-book-app” package in Ubuntu:
  New
Status in “address-book-app” package in Ubuntu RTM:
  New

Bug description:
  The phone field in address book doesn't accept symbols available in
  the keyboard for phone numbers: #*

  Test case:
  - Open Contacts app.
  - Add a new contact.
  - Go to Phone number field.
  - Press "+" key for 5 seconds and select these symbols: *#()

  Expected result:
  - Field accepts symbols as part of a telephone number.

  Actual result:
  - Only "+" symbol is accepted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/address-book-app/+bug/1372548/+subscriptions

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

[Touch-packages] [Bug 1359849] Re: call notifications show "unknown" briefly before showing contact name

[Bill Filler]

** Changed in: telephony-service (Ubuntu RTM)
   Status: New => In Progress

** Changed in: telephony-service (Ubuntu RTM)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1359849

Title:
  call notifications show "unknown" briefly before showing contact name

Status in Telephony Service:
  In Progress
Status in “telephony-service” package in Ubuntu:
  In Progress
Status in “unity-notifications” package in Ubuntu:
  Invalid
Status in “telephony-service” package in Ubuntu RTM:
  In Progress

Bug description:
  build 203 on krillin

  When receing a call from a contact in your address book that has an
  avatar, the notification is first shown with "Unknown caller" and
  default avatar before switching to the correct name and avatar.

  The name and avatar should be fetched before displaying the
  notification such that when it's shown it's correct right away.

To manage notifications about this bug go to:
https://bugs.launchpad.net/telephony-service/+bug/1359849/+subscriptions

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

[Touch-packages] [Bug 1324622] Re: Video does not return to the first frame after finishing

[Bill Filler]

** Changed in: gallery-app (Ubuntu)
   Importance: Undecided => High

** Changed in: gallery-app (Ubuntu RTM)
   Importance: Undecided => High

** Tags added: ota-future

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gallery-app in Ubuntu.
https://bugs.launchpad.net/bugs/1324622

Title:
  Video does not return to the first frame after finishing

Status in Gallery App:
  In Progress
Status in “gallery-app” package in Ubuntu:
  New
Status in “gallery-app” package in Ubuntu RTM:
  New

Bug description:
  when play back of video ends, we should show the preview (first
  framew) with the Play button overlayed (same as if you have just
  navigated to video from Photos view). Currently we show black screen
  after video ends.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gallery-app/+bug/1324622/+subscriptions

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

[Touch-packages] [Bug 1362781] Re: After date recurrence end is not functioning.

[Bill Filler]

** Tags removed: touch-2014-11-07
** Tags added: ota-1

** Changed in: qtorganizer5-eds (Ubuntu)
   Importance: Undecided => High

** Changed in: qtorganizer5-eds (Ubuntu RTM)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtorganizer5-eds in
Ubuntu.
https://bugs.launchpad.net/bugs/1362781

Title:
  After date recurrence  end is not functioning.

Status in Qt Organizer - EDS plugin:
  In Progress
Status in Calendar application for Ubuntu devices:
  In Progress
Status in “qtorganizer5-eds” package in Ubuntu:
  In Progress
Status in “qtorganizer5-eds” package in Ubuntu RTM:
  New

Bug description:
  Just noticed that,

  Creating an event , which ends after certain date, is creating an
  event with infinity , no end dates.

  Expected :

  It should stop event from that date.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qtorganizer5-eds/+bug/1362781/+subscriptions

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

[Touch-packages] [Bug 1359337] Re: dialer not remembering current view after lock/unlock

[Bill Filler]

** Changed in: dialer-app
   Importance: High => Medium

** Changed in: dialer-app (Ubuntu)
   Importance: High => Medium

** Also affects: dialer-app (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Changed in: dialer-app (Ubuntu RTM)
   Importance: Undecided => Medium

** Changed in: dialer-app (Ubuntu RTM)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dialer-app in Ubuntu.
https://bugs.launchpad.net/bugs/1359337

Title:
  dialer not remembering current view after lock/unlock

Status in Dialer app for Ubuntu Touch:
  Confirmed
Status in “dialer-app” package in Ubuntu:
  Confirmed
Status in “dialer-app” package in Ubuntu RTM:
  Confirmed

Bug description:
  build 199
  open dialer
  navigate to contacts page or recents page
  lock the phone
  unlock the phone

  Expected results:
  dialer should be on the page you left it on

  Actual results:
  keypad view is always shown

To manage notifications about this bug go to:
https://bugs.launchpad.net/dialer-app/+bug/1359337/+subscriptions

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

[Touch-packages] [Bug 1358343] Re: [TOPBLOCKER] too easy to answer a call by accident

[Bill Filler]

** Changed in: telephony-service
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-notifications in
Ubuntu.
https://bugs.launchpad.net/bugs/1358343

Title:
  [TOPBLOCKER] too easy to answer a call by accident

Status in Telephony Service:
  Fix Released
Status in Ubuntu UX bugs:
  Fix Committed
Status in “dialer-app” package in Ubuntu:
  Invalid
Status in “telephony-service” package in Ubuntu:
  Fix Released
Status in “unity-notifications” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Fix Released
Status in “telephony-service” package in Ubuntu RTM:
  Fix Released
Status in “unity-notifications” package in Ubuntu RTM:
  Fix Released
Status in “unity8” package in Ubuntu RTM:
  Fix Released

Bug description:
  If you put the phone in your pocket with locked screen and you receive
  a call is too easy to answer or reject that by mistake. Or pressing
  the screen while trying to get the phone or the call can be answered
  without you noticed by your pocket.

To manage notifications about this bug go to:
https://bugs.launchpad.net/telephony-service/+bug/1358343/+subscriptions

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

[Touch-packages] [Bug 1353453] Re: m.here.com doesn’t close authentication page after logging in

[Bill Filler]

** Also affects: webbrowser-app (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: webbrowser-app (Ubuntu)
   Importance: Undecided => High

** Changed in: webbrowser-app (Ubuntu)
 Assignee: (unassigned) => Alexandre Abreu (abreu-alexandre)

** Changed in: webbrowser-app
 Assignee: Olivier Tilloy (osomon) => Alexandre Abreu (abreu-alexandre)

** Tags removed: touch-2014-11-27
** Tags added: ota-future

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1353453

Title:
  m.here.com doesn’t close authentication page after logging in

Status in Web Browser App:
  In Progress
Status in “webbrowser-app” package in Ubuntu:
  New
Status in “webbrowser-app” package in Ubuntu RTM:
  Triaged

Bug description:
  STEPS:
  1. Open the browser
  2. Goto m.here.com
  3. Click on the grid top right of the page
  4. Click on sign in
  5. This now opens a new tab for the sso auth
  6. This tab isn't closed
  7. Click on the option menu show tabs
  8. Click on the here maps tab
  9. Note you are now logged in.

  Repeat the steps in the here maps app, now you can't select tabs so
  although you are now logged in you can't get to a point  where you
  can't get back to the maps.

To manage notifications about this bug go to:
https://bugs.launchpad.net/webbrowser-app/+bug/1353453/+subscriptions

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

[Touch-packages] [Bug 1350584] Re: keyboard not displayed after returning to app from shell

[Bill Filler]

** Changed in: messaging-app (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to messaging-app in Ubuntu.
https://bugs.launchpad.net/bugs/1350584

Title:
  keyboard not displayed after returning to app from shell

Status in The Unity 8 shell:
  Fix Released
Status in “messaging-app” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Fix Released

Bug description:
  seeing this in build rtm13

  - open messaging-app
  - open a message and click in send field to display keyboard
  - left edge swipe to return to shell
  - click on messaging-app in Apps scope

  Expected result:
  - messaging-app displayed with keyboard visible

  Actual result:
  - messaging-app shown without focus or keyboard

  The same steps work with notes app, see comment #2.

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

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

Re: [Touch-packages] [Bug 678421] Re: Error message for a faulty ~/.profile script

[Barry Warsaw]

On Nov 14, 2014, at 08:15 PM, Gunnar Hjalmarsson wrote:

>Being thrown back indicates a syntax error.

Are those errors logged anywhere permanently?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/678421

Title:
  Error message for a faulty ~/.profile script

Status in GDM: The Gnome Display Manager:
  New
Status in “gdm” package in Ubuntu:
  In Progress
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “gdm” source package in Trusty:
  Triaged
Status in “lightdm” source package in Trusty:
  In Progress
Status in “gdm” source package in Utopic:
  Triaged
Status in “lightdm” source package in Utopic:
  Fix Committed

Bug description:
  trusty and utopic SRU requests
  ==

  [Impact]

  In case of a syntax error in either of ~/.profile or a few other
  similar files, the Xorg login is interrupted, and the user is taken
  back to the login screen without an explanation. Debugging this
  problem may be a time consuming exercise, especially for non-
  experienced users.

  With the proposed change, lightdm/gdm does not try to load such a
  file, but shows a warning dialog instead. (A warning dialog is also
  shown in case of some other type of error, which would not have caused
  the login to fail.)

  [Test Case]

  To reproduce:

  * Edit ~/.profile and add something bad, e.g. a non-closed parenthesis.
  * Log out and find that you can't log in to a graphical session.

  After installing the proposed lightdm/gdm version, you'll instead see
  the dialog and can log in.

  [Regression Potential]

  Since this is only about improved exception handling, it does not at
  all affect users with correct configuration files. The regression risk
  ought to be minimal.

  [Original description]

  Binary package hint: gdm

  After adding "function AddPath { PATH="$1:$PATH" }" to $HOME/.profile
  made the Xorg startup fail. (At that moment I had already forgotten
  the changes made to the .profile). As I had autologin that meant it
  kept trying to login and finally showed me the graphics
  reconfiguration screen. That sent me to a huge hunt for xorg conf and
  setup problems.

  Anyway finally tracked this down. I had used bash syntax in .profile
  file whereas it was run with sh.

  This is not a bug per se but I think a user mistake in ".profile"
  shouldn't bring the whole xorg startup to a halt as it does with
  autologin. I propose running user ".profile" and ".xprofile" scripts
  so that Xsession script continues running even if they have errors.
  I'm not sure whether this change would have some negative effects as
  well.

  1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct 
16 19:48:22 UTC 2010 i686 GNU/Linux
  2) gdm 2.30.2.is.2.30.0-0ubuntu4

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

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

[Touch-packages] [Bug 1384810] Re: "Next" key is too big for keyboard and doesn't translate well

[Bill Filler]

Please implement suggestion 2 from olga, just use the standard return
key please, not the "Next" button

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

** Also affects: address-book-app (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-keyboard (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Changed in: address-book-app (Ubuntu)
   Importance: Undecided => High

** Changed in: address-book-app (Ubuntu RTM)
   Importance: Undecided => High

** Changed in: ubuntu-keyboard (Ubuntu)
   Importance: Undecided => High

** Changed in: ubuntu-keyboard (Ubuntu RTM)
   Importance: Undecided => High

** Tags added: ota-future

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to address-book-app in
Ubuntu.
https://bugs.launchpad.net/bugs/1384810

Title:
  "Next" key is too big for keyboard and doesn't translate well

Status in Address Book App:
  Fix Committed
Status in Ubuntu Keyboard:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in “address-book-app” package in Ubuntu:
  New
Status in “ubuntu-keyboard” package in Ubuntu:
  New
Status in “address-book-app” package in Ubuntu RTM:
  New
Status in “ubuntu-keyboard” package in Ubuntu RTM:
  New

Bug description:
  In the address book, we replace the enter button with the text "Next"
  as it automatically navigates you to the next field.

  A better solution would be to use an icon that represents Next (some
  kind of forward arrow).

To manage notifications about this bug go to:
https://bugs.launchpad.net/address-book-app/+bug/1384810/+subscriptions

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

[Touch-packages] [Bug 1369510] Re: dutch keyboard layout lacks a .com option

[Bill Filler]

** Also affects: ubuntu-keyboard (Ubuntu RTM)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1369510

Title:
  dutch keyboard layout lacks a .com option

Status in “ubuntu-keyboard” package in Ubuntu:
  Triaged
Status in “ubuntu-keyboard” package in Ubuntu RTM:
  New

Bug description:
  In terms of popularity I would think that when entering an email
  address .com is a popular option. A lot of people use services like
  hotmail.com or gmail.com, so the ubuntu-keyboard should have an option
  for entering .com quickly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1369510/+subscriptions

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

[Touch-packages] [Bug 1370609] Re: surface position/height is not calculated properly when the wordRibbon is enabled but not visible

[Bill Filler]

** Changed in: ubuntu-keyboard (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntu-keyboard (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-keyboard (Ubuntu RTM)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1370609

Title:
  surface position/height is not calculated properly when the wordRibbon
  is enabled but not visible

Status in Ubuntu Keyboard:
  Confirmed
Status in “ubuntu-keyboard” package in Ubuntu:
  In Progress
Status in “ubuntu-keyboard” package in Ubuntu RTM:
  New

Bug description:
  If you have the wordRibbon enabled in the options, but you are using some 
textField that disables it (or some properties), for example entering a wifi 
password from the indicators, when the keyboard hides the mir surface rectangle 
is not calculated properly, and you can see that when the osk disappears a 
white box starts moving from few pixels on top of the keyboard.
  It could be height, it could be y...

  To reproduce:

  - enable word suggestion/completion
  - open network indicator
  - tap on a wifi where you did not set the password

  [now pay attention to the box around the keyboard before you cancel
  the connection dialog]

  - cancel the connection dialog and see the keyboard disappearing

  Actual result:
  Blank rectangle disappearing from few pixels on top of the keyboard

  Expected result:
  No blank rectangle is visible, keyboard disappears beautifully

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-keyboard/+bug/1370609/+subscriptions

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

[Touch-packages] [Bug 1385382] Re: Clock set to past confuses AppArmor cache validation

[Chris Wayne]

Yes, I'd put the workaround in place.  I can try and get this landed in
customizatoon-hooks as well if it's desired, but if the workaround is
enough, we should be good for now

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-touch-
customization-hooks in Ubuntu.
https://bugs.launchpad.net/bugs/1385382

Title:
  Clock set to past confuses AppArmor cache validation

Status in AppArmor Linux application security framework:
  Won't Fix
Status in “ubuntu-touch-customization-hooks” package in Ubuntu:
  Triaged

Bug description:
  During initial boot sometimes clock could be set to past, which will confuse 
logic validating precompiled AppArmour cache, causing cache recreation.
  If time is not set correct(valid) value, even consequent boots will fail to 
validate cache, forcing cache recreation.

  This bug affects Initial out of the box experience, since device clock
  is set in the factory to default value, for example 0:0am 1st of
  January 2014

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

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

[Touch-packages] [Bug 1256265] Re: keys sometimes get stuck in selected state

[Bill Filler]

** Tags removed: touch-2014-10-23
** Tags added: ota-future

** Also affects: ubuntu-keyboard (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-keyboard (Ubuntu RTM)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1256265

Title:
  keys sometimes get stuck in selected state

Status in Ubuntu Keyboard:
  In Progress
Status in “ubuntu-keyboard” package in Ubuntu:
  In Progress
Status in “ubuntu-keyboard” package in Ubuntu RTM:
  New

Bug description:
  I was typing a phone number pretty quickly into the messaging app.
  Part way through one of the numbers (7) stuck down, it didn't repeat, but the 
pop up which shows the key you pressed stuck up. See screenshot.
  I carried on typing and other keys didn't stick, and that key didn't come 
down.

  It only went away when the keyboard was re-opened after the screen
  locked and was unlocked and I tapped another field.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubuntu-keyboard 0.99.trunk.phablet2+14.04.20131126-0ubuntu1
  Uname: Linux 3.4.0-3-mako armv7l
  ApportVersion: 2.12.7-0ubuntu1
  Architecture: armhf
  Date: Fri Nov 29 10:27:27 2013
  InstallationDate: Installed on 2013-11-29 (0 days ago)
  InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20131129)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
  SourcePackage: ubuntu-keyboard
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-keyboard/+bug/1256265/+subscriptions

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

[Touch-packages] [Bug 1385382] Re: Clock set to past confuses AppArmor cache validation

[Jamie Strandboge]

** Summary changed:

- Clock set to past confuses AppArmour cache validation
+ Clock set to past confuses AppArmor cache validation

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-touch-
customization-hooks in Ubuntu.
https://bugs.launchpad.net/bugs/1385382

Title:
  Clock set to past confuses AppArmor cache validation

Status in AppArmor Linux application security framework:
  Won't Fix
Status in “ubuntu-touch-customization-hooks” package in Ubuntu:
  Triaged

Bug description:
  During initial boot sometimes clock could be set to past, which will confuse 
logic validating precompiled AppArmour cache, causing cache recreation.
  If time is not set correct(valid) value, even consequent boots will fail to 
validate cache, forcing cache recreation.

  This bug affects Initial out of the box experience, since device clock
  is set in the factory to default value, for example 0:0am 1st of
  January 2014

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

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

[Touch-packages] [Bug 678421] Re: Error message for a faulty ~/.profile script

[Gunnar Hjalmarsson]

On 2014-11-14 20:43, Barry Warsaw wrote:
> Sure, it's entirely possibly that my login has been silently ignoring
> the non-sh syntax errors, so in that respect, getting notification of
> them now is a good thing.

The use of commands unknown to sh is one kind of error that was silently
ignored. However, that's not a syntax error. Syntax errors was not
ignored.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/678421

Title:
  Error message for a faulty ~/.profile script

Status in GDM: The Gnome Display Manager:
  New
Status in “gdm” package in Ubuntu:
  In Progress
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “gdm” source package in Trusty:
  Triaged
Status in “lightdm” source package in Trusty:
  In Progress
Status in “gdm” source package in Utopic:
  Triaged
Status in “lightdm” source package in Utopic:
  Fix Committed

Bug description:
  trusty and utopic SRU requests
  ==

  [Impact]

  In case of a syntax error in either of ~/.profile or a few other
  similar files, the Xorg login is interrupted, and the user is taken
  back to the login screen without an explanation. Debugging this
  problem may be a time consuming exercise, especially for non-
  experienced users.

  With the proposed change, lightdm/gdm does not try to load such a
  file, but shows a warning dialog instead. (A warning dialog is also
  shown in case of some other type of error, which would not have caused
  the login to fail.)

  [Test Case]

  To reproduce:

  * Edit ~/.profile and add something bad, e.g. a non-closed parenthesis.
  * Log out and find that you can't log in to a graphical session.

  After installing the proposed lightdm/gdm version, you'll instead see
  the dialog and can log in.

  [Regression Potential]

  Since this is only about improved exception handling, it does not at
  all affect users with correct configuration files. The regression risk
  ought to be minimal.

  [Original description]

  Binary package hint: gdm

  After adding "function AddPath { PATH="$1:$PATH" }" to $HOME/.profile
  made the Xorg startup fail. (At that moment I had already forgotten
  the changes made to the .profile). As I had autologin that meant it
  kept trying to login and finally showed me the graphics
  reconfiguration screen. That sent me to a huge hunt for xorg conf and
  setup problems.

  Anyway finally tracked this down. I had used bash syntax in .profile
  file whereas it was run with sh.

  This is not a bug per se but I think a user mistake in ".profile"
  shouldn't bring the whole xorg startup to a halt as it does with
  autologin. I propose running user ".profile" and ".xprofile" scripts
  so that Xsession script continues running even if they have errors.
  I'm not sure whether this change would have some negative effects as
  well.

  1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct 
16 19:48:22 UTC 2010 i686 GNU/Linux
  2) gdm 2.30.2.is.2.30.0-0ubuntu4

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

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

[Touch-packages] [Bug 1377624] Re: udev requires hotplug support, thus upgrades fail

[parvan]

I also have the same issue.

Brand new install. 
OVH VPS 
Ubuntu 14.04 LTS in an OpenVZ container.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1377624

Title:
  udev requires hotplug support, thus upgrades fail

Status in “systemd” package in Ubuntu:
  Confirmed

Bug description:
  I'm running 14.04 LTS in an OpenVZ container.

  Upgrades failed today, due to failure to configure udev:
  $ sudo apt-get dist-upgrade
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  3 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Setting up udev (204-5ubuntu20.7) ...
   * udev requires hotplug support, not started
 ...fail!
  invoke-rc.d: initscript udev, action "restart" failed.
  dpkg: error processing package udev (--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of systemd-services:
   systemd-services depends on udev (>= 175-0ubuntu23); however:
Package udev is not configured yet.

  dpkg: error processing package systemd-services (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of libpam-systemd:amd64:
   libpam-systemd:amd64 depends on systemd-services (= 204-5ubuntu20.7); 
however:
Package systemd-services is not configured yet.

  dpkg: error processing package libpam-systemd:amd64 (--configure):
   dependency problems - leaving unconfigured
  Errors were encountered while processing:
   udev
   systemd-services
   libpam-systemd:amd64
  E: Sub-process /usr/bin/dpkg returned an error code (1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1377624/+subscriptions

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

[Touch-packages] [Bug 1385382] Re: Clock set to past confuses AppArmour cache validation

[Jamie Strandboge]

Assigning to package that ships /etc/init/custom-apparmor-cache.conf.
I'm not the owner of ubuntu-touch-customization-hooks so someone else
needs to land it. That said, the approach seems reasonable and the
script fine (though the double assignment for TIME_ROOTFS is not as
clear as it could be). However, I question whether this should be a pre-
start of custom-apparmor-cache.conf. On the one hand, we shouldn't need
this at all but because we do for custom-apparmor-cache to work right so
it makes sense, but on the other, perhaps this would be better placed in
a more 'foundational/phondational' package. Can we get someone from
Phonedations/Foundations to review and comment?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-touch-
customization-hooks in Ubuntu.
https://bugs.launchpad.net/bugs/1385382

Title:
  Clock set to past confuses AppArmor cache validation

Status in AppArmor Linux application security framework:
  Won't Fix
Status in “ubuntu-touch-customization-hooks” package in Ubuntu:
  Triaged

Bug description:
  During initial boot sometimes clock could be set to past, which will confuse 
logic validating precompiled AppArmour cache, causing cache recreation.
  If time is not set correct(valid) value, even consequent boots will fail to 
validate cache, forcing cache recreation.

  This bug affects Initial out of the box experience, since device clock
  is set in the factory to default value, for example 0:0am 1st of
  January 2014

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

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

[Touch-packages] [Bug 1385382] Re: Clock set to past confuses AppArmour cache validation

[Jamie Strandboge]

** Also affects: ubuntu-touch-customization-hooks (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-touch-customization-hooks (Ubuntu)
   Status: New => Triaged

** Changed in: apparmor
 Assignee: Jamie Strandboge (jdstrand) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-touch-
customization-hooks in Ubuntu.
https://bugs.launchpad.net/bugs/1385382

Title:
  Clock set to past confuses AppArmour cache validation

Status in AppArmor Linux application security framework:
  Won't Fix
Status in “ubuntu-touch-customization-hooks” package in Ubuntu:
  Triaged

Bug description:
  During initial boot sometimes clock could be set to past, which will confuse 
logic validating precompiled AppArmour cache, causing cache recreation.
  If time is not set correct(valid) value, even consequent boots will fail to 
validate cache, forcing cache recreation.

  This bug affects Initial out of the box experience, since device clock
  is set in the factory to default value, for example 0:0am 1st of
  January 2014

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

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

[Touch-packages] [Bug 678421] Re: Error message for a faulty ~/.profile script

[Gunnar Hjalmarsson]

Being thrown back indicates a syntax error. One thing you could do is
testing each one of your sourced files like this:

sh -n 

The files must pass that test, or else you won't be able to log in.

This is what the new lightdm code does, but it does not work
recursively...

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/678421

Title:
  Error message for a faulty ~/.profile script

Status in GDM: The Gnome Display Manager:
  New
Status in “gdm” package in Ubuntu:
  In Progress
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “gdm” source package in Trusty:
  Triaged
Status in “lightdm” source package in Trusty:
  In Progress
Status in “gdm” source package in Utopic:
  Triaged
Status in “lightdm” source package in Utopic:
  Fix Committed

Bug description:
  trusty and utopic SRU requests
  ==

  [Impact]

  In case of a syntax error in either of ~/.profile or a few other
  similar files, the Xorg login is interrupted, and the user is taken
  back to the login screen without an explanation. Debugging this
  problem may be a time consuming exercise, especially for non-
  experienced users.

  With the proposed change, lightdm/gdm does not try to load such a
  file, but shows a warning dialog instead. (A warning dialog is also
  shown in case of some other type of error, which would not have caused
  the login to fail.)

  [Test Case]

  To reproduce:

  * Edit ~/.profile and add something bad, e.g. a non-closed parenthesis.
  * Log out and find that you can't log in to a graphical session.

  After installing the proposed lightdm/gdm version, you'll instead see
  the dialog and can log in.

  [Regression Potential]

  Since this is only about improved exception handling, it does not at
  all affect users with correct configuration files. The regression risk
  ought to be minimal.

  [Original description]

  Binary package hint: gdm

  After adding "function AddPath { PATH="$1:$PATH" }" to $HOME/.profile
  made the Xorg startup fail. (At that moment I had already forgotten
  the changes made to the .profile). As I had autologin that meant it
  kept trying to login and finally showed me the graphics
  reconfiguration screen. That sent me to a huge hunt for xorg conf and
  setup problems.

  Anyway finally tracked this down. I had used bash syntax in .profile
  file whereas it was run with sh.

  This is not a bug per se but I think a user mistake in ".profile"
  shouldn't bring the whole xorg startup to a halt as it does with
  autologin. I propose running user ".profile" and ".xprofile" scripts
  so that Xsession script continues running even if they have errors.
  I'm not sure whether this change would have some negative effects as
  well.

  1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct 
16 19:48:22 UTC 2010 i686 GNU/Linux
  2) gdm 2.30.2.is.2.30.0-0ubuntu4

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

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

[Touch-packages] [Bug 1384800] Re: words with apostrophes are not suggested by prediction

[Bill Filler]

** Also affects: ubuntu-keyboard (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to presage in Ubuntu.
https://bugs.launchpad.net/bugs/1384800

Title:
  words with apostrophes are not suggested by prediction

Status in Ubuntu Keyboard:
  In Progress
Status in “presage” package in Ubuntu:
  In Progress
Status in “ubuntu-keyboard” package in Ubuntu:
  New
Status in “presage” package in Ubuntu RTM:
  New
Status in “ubuntu-keyboard” package in Ubuntu RTM:
  New

Bug description:
  The current word prediction does not suggest or correct words like
  "we'll", "it's" "they're" etc.

  The expected behavior is if I typed "its" it should be autocorrected
  to "it's" and similar for other common words.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-keyboard/+bug/1384800/+subscriptions

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

[Touch-packages] [Bug 1377755] Re: keyboard layout flickers and hides on gmail

[Bill Filler]

** Also affects: ubuntu-keyboard (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-keyboard (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-keyboard (Ubuntu)
   Importance: Undecided => High

** Changed in: ubuntu-keyboard (Ubuntu RTM)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1377755

Title:
  keyboard layout flickers and hides on gmail

Status in Oxide Webview:
  Fix Released
Status in Oxide 1.2 series:
  Fix Committed
Status in Ubuntu Keyboard:
  Confirmed
Status in “ubuntu-keyboard” package in Ubuntu:
  New
Status in “ubuntu-keyboard” package in Ubuntu RTM:
  New

Bug description:
  build 83 rtm-proposed on krillin

  1) Run the gmail webapp and compose a new message
  2) The "To:" field has focus and the keyboard is showing (url layout with @ 
and .com key)
  3) Tap in "CC:" field

  Expected results:
  keyboard stays visible with same url layout

  Actual results:
  keyboard switches to normal layout, then switches to url layout, then 
disappears

  4) Tap in the "Bcc:" field and no keyboard is shown, Tap back in To: or CC: 
field and no keyboard is shown
  5) Tap in Subject field and keyboard shown in normal layout
  6) Now when switch to to, cc, or bc it works, but normal layout shown first 
then changes to url layout

  Expected Result:
  - if new layout is same as existing layout it shouldnt' first switch back to 
default layout
  - keyboard should not be disappearing

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

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

[Touch-packages] [Bug 1347488] Re: Backspace should accelerate for single letters as well as words

[Bill Filler]

** Also affects: ubuntu-keyboard (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-keyboard (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-keyboard (Ubuntu)
   Importance: Undecided => High

** Changed in: ubuntu-keyboard (Ubuntu RTM)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1347488

Title:
  Backspace should accelerate for single letters as well as words

Status in Ubuntu Keyboard:
  Confirmed
Status in “ubuntu-keyboard” package in Ubuntu:
  New
Status in “ubuntu-keyboard” package in Ubuntu RTM:
  New

Bug description:
  Currently the backspace only accelerates when it starts deleting
  words, so deleting a very long string of characters which are unbroken
  by spaces takes a long time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-keyboard/+bug/1347488/+subscriptions

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

[Touch-packages] [Bug 1347796] Re: Ignore predictions for auto-completion if they're too different from original input

[Bill Filler]

** Changed in: ubuntu-keyboard (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntu-keyboard (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1347796

Title:
  Ignore predictions for auto-completion if they're too different from
  original input

Status in Ubuntu Keyboard:
  In Progress
Status in “ubuntu-keyboard” package in Ubuntu:
  In Progress
Status in “ubuntu-keyboard” package in Ubuntu RTM:
  New

Bug description:
  We should measure the Levenshtein distance between the user's input
  and the primary prediction candidate. If this passes a certain
  threshold (meaning that the two are very different) we should disable
  auto-completion and enter the user's word instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-keyboard/+bug/1347796/+subscriptions

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

[Touch-packages] [Bug 1325626] Re: Inline translations from .desktop files are not loaded

[Bill Filler]

** Changed in: notes-app
   Importance: High => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to camera-app in Ubuntu.
https://bugs.launchpad.net/bugs/1325626

Title:
  Inline translations from .desktop files are not loaded

Status in Camera App:
  Fix Released
Status in Gallery App:
  Fix Released
Status in Music application for Ubuntu devices:
  Fix Released
Status in Notes App:
  In Progress
Status in Calculator application for Ubuntu devices:
  Fix Released
Status in Calendar application for Ubuntu devices:
  Fix Released
Status in Clock application for Ubuntu devices:
  Fix Released
Status in File Manager application for Ubuntu devices:
  Fix Released
Status in RSS Feed Reader application for Ubuntu devices:
  Invalid
Status in Terminal application for Ubuntu devices:
  Fix Released
Status in Weather application for Ubuntu devices:
  Fix Released
Status in “camera-app” package in Ubuntu:
  Fix Released
Status in “gallery-app” package in Ubuntu:
  Fix Released
Status in “unity-scope-click” package in Ubuntu:
  Invalid

Bug description:
  Using image #60, and the Calculator app as an example, the inline
  translations of its desktop files are not loaded.

  Steps to reproduce:

  1. Set the system locale (System Settings > Language & Text) to Spanish or 
Simplified Chinese
  2. Reboot the phone
  Go to My Apps on the click scope

  Actual:
  - "Calculator" appears untranslated beneath the Calculator icon

  Expected:
  - "Calculator" appears translated beneath the Calculator icon (if inline 
translations are available in its .desktop file)

To manage notifications about this bug go to:
https://bugs.launchpad.net/camera-app/+bug/1325626/+subscriptions

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

[Touch-packages] [Bug 1324622] Re: Video does not return to the first frame after finishing

[Bill Filler]

** Also affects: gallery-app (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gallery-app (Ubuntu RTM)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gallery-app in Ubuntu.
https://bugs.launchpad.net/bugs/1324622

Title:
  Video does not return to the first frame after finishing

Status in Gallery App:
  In Progress
Status in “gallery-app” package in Ubuntu:
  New
Status in “gallery-app” package in Ubuntu RTM:
  New

Bug description:
  when play back of video ends, we should show the preview (first
  framew) with the Play button overlayed (same as if you have just
  navigated to video from Photos view). Currently we show black screen
  after video ends.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gallery-app/+bug/1324622/+subscriptions

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

[Touch-packages] [Bug 1335007] Re: Can't use pinyin for Chinese in browser URL bar due to Qt.ImhUrlCharactersOnly

[Bill Filler]

** Also affects: ubuntu-keyboard (Ubuntu RTM)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1335007

Title:
  Can't use pinyin for Chinese in browser URL bar due to
  Qt.ImhUrlCharactersOnly

Status in Ubuntu Keyboard:
  Confirmed
Status in “ubuntu-keyboard” package in Ubuntu:
  Confirmed
Status in “ubuntu-keyboard” package in Ubuntu RTM:
  New

Bug description:
  With Chinese pinyin input method enabled, open the browser, tap the
  URL bar/ search bar, type "n" and "i". You should see "你" as a word
  prediction. In fact no words show up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-keyboard/+bug/1335007/+subscriptions

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

[Touch-packages] [Bug 1335002] Re: Chinese input method does not work after enable Chinese keyboard in Ubuntu Phone

[Bill Filler]

** Also affects: ubuntu-keyboard (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-keyboard (Ubuntu)
   Importance: Undecided => High

** Also affects: ubuntu-keyboard (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-keyboard (Ubuntu RTM)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1335002

Title:
  Chinese input method does not work after enable Chinese keyboard in
  Ubuntu Phone

Status in Ubuntu Keyboard:
  Confirmed
Status in “ubuntu-keyboard” package in Ubuntu:
  New
Status in “ubuntu-keyboard” package in Ubuntu RTM:
  New

Bug description:
  Reproduce steps:

  1, enable Chinese keyboard in system settings
  2, launch an app can input text like notes
  3, long press global icon and switch Chinese

  Expecting:
  user can input Chinese like press 'n' and 'i' then 你 should show up on 
candidate bar

  Actual:
  no candidate bar, so still input English

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-keyboard/+bug/1335002/+subscriptions

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

[Touch-packages] [Bug 1390128] Re: [address-book] is stuck on contacts sync dialog & becomes unusable

[Bill Filler]

** Also affects: address-book-app (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Changed in: address-book-app (Ubuntu RTM)
   Importance: Undecided => Critical

** Changed in: address-book-app (Ubuntu RTM)
 Assignee: (unassigned) => Renato Araujo Oliveira Filho (renatofilho)

** Tags removed: touch-2014-11-13
** Tags added: ota-1

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to address-book-app in
Ubuntu.
https://bugs.launchpad.net/bugs/1390128

Title:
  [address-book] is stuck on contacts sync dialog & becomes unusable

Status in Address Book App:
  Fix Committed
Status in Ubuntu UX bugs:
  Fix Committed
Status in “address-book-app” package in Ubuntu:
  Fix Released
Status in “address-book-app” package in Ubuntu RTM:
  New

Bug description:
  build 143
  To reproduce this bug the address book app has to be launched for the first 
time.

  Steps to reproduce

  1. wipe your device if necessary
  2. launch the address book app and wait until the "You have no contacts" 
dialog comes up
  3. do not interact with the dialog and navigate away from the app
  4. launch the dialer or/and the messaging app
  5. open the app spread from the right edge and force close the address book 
app
  6. navigate to dialer (or messaging) app and save a contact from the main view
  7. now open the address book again and try to interact with the "You have no 
contacts" dialog

  Expected behaviour: you will either be able to dismiss the dialog or
  sync contacts

  Actual behaviour: you won't be able to tap anything or interact with
  the address book because the dialog is not dismissible.

  The interesting thing here is that it is possible to access the
  address book and contacts from the dialer and messaging app but not
  directly.

  Marking as "Critical" because the address book becomes completely
  unusable even if you restart your device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/address-book-app/+bug/1390128/+subscriptions

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

Re: [Touch-packages] [Bug 678421] Re: Error message for a faulty ~/.profile script

[Barry Warsaw]

Hi Gunnar.

On Nov 14, 2014, at 07:07 PM, Gunnar Hjalmarsson wrote:

>It has always been using Bourne shell, so "source" is not understood.
>You have obliviously been running your system without the configuration
>in those other shell files.

Sure, it's entirely possibly that my login has been silently ignoring the
non-sh syntax errors, so in that respect, getting notification of them now is
a good thing.

I still wonder what in my shell code could be causing lightdm to exit back
to the login screen and where those errors would be logged so that I can view
them and debug them.

Cheers.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/678421

Title:
  Error message for a faulty ~/.profile script

Status in GDM: The Gnome Display Manager:
  New
Status in “gdm” package in Ubuntu:
  In Progress
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “gdm” source package in Trusty:
  Triaged
Status in “lightdm” source package in Trusty:
  In Progress
Status in “gdm” source package in Utopic:
  Triaged
Status in “lightdm” source package in Utopic:
  Fix Committed

Bug description:
  trusty and utopic SRU requests
  ==

  [Impact]

  In case of a syntax error in either of ~/.profile or a few other
  similar files, the Xorg login is interrupted, and the user is taken
  back to the login screen without an explanation. Debugging this
  problem may be a time consuming exercise, especially for non-
  experienced users.

  With the proposed change, lightdm/gdm does not try to load such a
  file, but shows a warning dialog instead. (A warning dialog is also
  shown in case of some other type of error, which would not have caused
  the login to fail.)

  [Test Case]

  To reproduce:

  * Edit ~/.profile and add something bad, e.g. a non-closed parenthesis.
  * Log out and find that you can't log in to a graphical session.

  After installing the proposed lightdm/gdm version, you'll instead see
  the dialog and can log in.

  [Regression Potential]

  Since this is only about improved exception handling, it does not at
  all affect users with correct configuration files. The regression risk
  ought to be minimal.

  [Original description]

  Binary package hint: gdm

  After adding "function AddPath { PATH="$1:$PATH" }" to $HOME/.profile
  made the Xorg startup fail. (At that moment I had already forgotten
  the changes made to the .profile). As I had autologin that meant it
  kept trying to login and finally showed me the graphics
  reconfiguration screen. That sent me to a huge hunt for xorg conf and
  setup problems.

  Anyway finally tracked this down. I had used bash syntax in .profile
  file whereas it was run with sh.

  This is not a bug per se but I think a user mistake in ".profile"
  shouldn't bring the whole xorg startup to a halt as it does with
  autologin. I propose running user ".profile" and ".xprofile" scripts
  so that Xsession script continues running even if they have errors.
  I'm not sure whether this change would have some negative effects as
  well.

  1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct 
16 19:48:22 UTC 2010 i686 GNU/Linux
  2) gdm 2.30.2.is.2.30.0-0ubuntu4

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

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

[Touch-packages] [Bug 1323089] Re: wpa_supplicant writes to syslog every 2 minutes

[Christian Kujau]

Same here, every 2 minutes with wpa_supplicant v2.3:

$ sudo grep wpa_supplicant /var/log/messages | grep -v WPA | tail -3
Nov 14 11:24:32 acorn wpa_supplicant[942]: nl80211: send_and_recv->nl_recvmsgs 
failed: -33
Nov 14 11:26:32 acorn wpa_supplicant[942]: nl80211: send_and_recv->nl_recvmsgs 
failed: -33
Nov 14 11:28:32 acorn wpa_supplicant[942]: nl80211: send_and_recv->nl_recvmsgs 
failed: -33

No connectivity issues though, rekeying happens just fine every 10min:

$ sudo grep wpa_supplicant /var/log/messages | grep WPA | tail -3
Nov 14 11:07:28 acorn wpa_supplicant[942]: wlan0: WPA: Group rekeying completed 
with  [GTK=CCMP]
Nov 14 11:17:28 acorn wpa_supplicant[942]: wlan0: WPA: Group rekeying completed 
with  [GTK=CCMP]
Nov 14 11:27:28 acorn wpa_supplicant[942]: wlan0: WPA: Group rekeying completed 
with  [GTK=CCMP]

Wifi chip:
04:00.0 Network controller: Intel Corporation Centrino Wireless-N 2230 (rev c4)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1323089

Title:
  wpa_supplicant writes to syslog every 2 minutes

Status in “wpa” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 14.04 LTS
  wpasupplicant 2.1-0ubuntu1

  wpa_supplicant is writing to syslog every couple of minutes. Example
  output:

  May 25 19:57:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 19:57:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 19:59:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 19:59:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 20:00:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:01:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:01:24 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 20:03:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:03:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 20:05:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:05:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 20:05:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:07:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:07:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 20:09:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:09:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33
  May 25 20:10:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED 
  May 25 20:13:18 ubuntu wpa_supplicant[1161]: message repeated 2 times: [ 
wlan0: CTRL-EVENT-SCAN-STARTED ]
  May 25 20:13:23 ubuntu wpa_supplicant[1161]: nl80211: 
send_and_recv->nl_recvmsgs failed: -33

  The message seems harmless as far as the network is concerned, meaning
  there is no problem with the wifi connection. But it's spamming the
  syslog, making it very difficult to find any other thing there, and
  it's generating constant writes to disk, and an unnecessarily large
  syslog file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1323089/+subscriptions

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

[Touch-packages] [Bug 1392844] [NEW] Unity crashes, doesn't restart and window borders are gone

[snapy]

Public bug reported:

1) 
Description:Ubuntu 14.04.1 LTS
Release:14.04

2) 
unity: 7.2.2+14.04.20140714-0ubuntu1.1

3)
Continue to run smoothly.

4)
It crashed. I may have pressed the key for Ubuntu Dash Search (Super). After 
the crash, Super, ALT + F2 and ALT + TAB had no effect. The window borders were 
gone.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
Uname: Linux 3.13.0-39-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Fri Nov 14 20:10:02 2014
InstallationDate: Installed on 2014-04-18 (209 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 Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1392844

Title:
  Unity crashes, doesn't restart and window borders are gone

Status in “unity” package in Ubuntu:
  New

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

  2) 
  unity: 7.2.2+14.04.20140714-0ubuntu1.1

  3)
  Continue to run smoothly.

  4)
  It crashed. I may have pressed the key for Ubuntu Dash Search (Super). After 
the crash, Super, ALT + F2 and ALT + TAB had no effect. The window borders were 
gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Nov 14 20:10:02 2014
  InstallationDate: Installed on 2014-04-18 (209 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/1392844/+subscriptions

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

[Touch-packages] [Bug 1392744] Re: mako/vivid does not show install progress

[Rodney Dawes]

Yes, this is a crash in the ubuntu-download-manager-client library.

** Changed in: ubuntu-download-manager (Ubuntu)
 Assignee: (unassigned) => Manuel de la Peña (mandel)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scope-click in
Ubuntu.
https://bugs.launchpad.net/bugs/1392744

Title:
  mako/vivid does not show install progress

Status in “ubuntu-download-manager” package in Ubuntu:
  New
Status in “unity-scope-click” package in Ubuntu:
  Triaged

Bug description:
  I use a n4 with the vivid channel and I'm on image #20. When I go to a
  app in the store and click on "Install" I see now change in the UI,
  i.e. no download progress, no change in the button etc. But I do see
  activity in the u-d-m download logs and eventually the screen will
  refresh (or at least turn blank) and the app is installed.

  The log also shows me some "download_db.cpp:285] Parameter count
  mismatch" errors.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-download-manager/+bug/1392744/+subscriptions

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

[Touch-packages] [Bug 1387908] Re: [udev] FIDO u2f security keys should be supported out of the box

[Botond Szász]

For Plug-Up Security Key (http://www.plug-up.com/), to make it work I
added the following to '/etc/udev/rules.d/45-u2f.rules':

SUBSYSTEM=="hidraw", MODE="0666", ATTRS{idVendor}=="2581",
ATTRS{idProduct}=="f1d0"

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1387908

Title:
  [udev] FIDO u2f security keys should be supported out of the box

Status in “systemd” package in Ubuntu:
  Incomplete
Status in “systemd” source package in Trusty:
  Confirmed
Status in “systemd” source package in Utopic:
  Confirmed
Status in “systemd” source package in Vivid:
  Incomplete

Bug description:
  FIDO u2f is an emerging standard for public-private cryptography based
  2nd factor authentication, which improves on OTP by mitigating
  phishing, man-in-the-middle attacks and reply attacks.

  Google Chrome supports u2f devices which are now widely available from
  Yubico (new premium neo Yubikeys and Security keys).

  However, udev rules are required to setup permissions to allow the
  web-browsers which are running as regular users to access the devices
  in question.

  E.g.:

  KERNEL=="hidraw*", SUBSYSTEM=="hidraw", MODE="0664", GROUP="plugdev",
  ATTRS{idVendor}=="1050", ATTRS{idProduct}=="0113|0114|0115|0116|0120"

  Something like that should be enabled by default, however probably not
  encode on the vendor/productid as other vendors will also make u2f
  devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1387908/+subscriptions

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

[Touch-packages] [Bug 678421] Re: Error message for a faulty ~/.profile script

[Gunnar Hjalmarsson]

Hi Barry!

On 2014-11-14 17:56, Barry Warsaw wrote:
> So, when I log in, I do get several warnings in a dialog.  Most are 
> because I use `source` instead of `.` to source other shell files.
> What shell is lightdm using these days?

It has always been using Bourne shell, so "source" is not understood.
You have obliviously been running your system without the configuration
in those other shell files.

> Anyway, when I change them all to `.` I still get one warning about
> my use of shopt,

Another bash command, not understood by dash.

> However, logins are now completely broken. I see the screen blank and
> then I'm thrown back to the login screen.  ~/.xsession-errors is
> empty and I can find no other log file either in $HOME or /var/log
> that contains any information about what's going wrong.

This is the code in /usr/sbin/lightdm-session which triggers those
warning dialogs:


# temporary storage of error messages
ERR=$(mktemp --tmpdir config-err-XX)

source_with_error_check () {
CONFIG_FILE="$1"
if sh -n "$CONFIG_FILE" 2>"$ERR"; then
echo "Loading $CONFIG_FILE";
. "$CONFIG_FILE" 2>"$ERR"
if [ -s "$ERR" ]; then
SYNTAX=false
. /usr/lib/lightdm/config-error-dialog.sh
fi
else
SYNTAX=true
. /usr/lib/lightdm/config-error-dialog.sh
fi
cat "$ERR" >>/dev/stderr
truncate -s 0 "$ERR"
}

# Load profile
for file in "/etc/profile" "$HOME/.profile" \
"/etc/xprofile" "$HOME/.xprofile"; do
if [ -f "$file" ]; then
source_with_error_check "$file"
fi
done


I find it hard to believe that that code itself is causing the problem
you describe. Considering that you could log in just fine before you
changed the occurrences of "source" to ".", I would look for the cause
in the code which unlike before is now sourced by lightdm.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/678421

Title:
  Error message for a faulty ~/.profile script

Status in GDM: The Gnome Display Manager:
  New
Status in “gdm” package in Ubuntu:
  In Progress
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “gdm” source package in Trusty:
  Triaged
Status in “lightdm” source package in Trusty:
  In Progress
Status in “gdm” source package in Utopic:
  Triaged
Status in “lightdm” source package in Utopic:
  Fix Committed

Bug description:
  trusty and utopic SRU requests
  ==

  [Impact]

  In case of a syntax error in either of ~/.profile or a few other
  similar files, the Xorg login is interrupted, and the user is taken
  back to the login screen without an explanation. Debugging this
  problem may be a time consuming exercise, especially for non-
  experienced users.

  With the proposed change, lightdm/gdm does not try to load such a
  file, but shows a warning dialog instead. (A warning dialog is also
  shown in case of some other type of error, which would not have caused
  the login to fail.)

  [Test Case]

  To reproduce:

  * Edit ~/.profile and add something bad, e.g. a non-closed parenthesis.
  * Log out and find that you can't log in to a graphical session.

  After installing the proposed lightdm/gdm version, you'll instead see
  the dialog and can log in.

  [Regression Potential]

  Since this is only about improved exception handling, it does not at
  all affect users with correct configuration files. The regression risk
  ought to be minimal.

  [Original description]

  Binary package hint: gdm

  After adding "function AddPath { PATH="$1:$PATH" }" to $HOME/.profile
  made the Xorg startup fail. (At that moment I had already forgotten
  the changes made to the .profile). As I had autologin that meant it
  kept trying to login and finally showed me the graphics
  reconfiguration screen. That sent me to a huge hunt for xorg conf and
  setup problems.

  Anyway finally tracked this down. I had used bash syntax in .profile
  file whereas it was run with sh.

  This is not a bug per se but I think a user mistake in ".profile"
  shouldn't bring the whole xorg startup to a halt as it does with
  autologin. I propose running user ".profile" and ".xprofile" scripts
  so that Xsession script continues running even if they have errors.
  I'm not sure whether this change would have some negative effects as
  well.

  1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct 
16 19:48:22 UTC 2010 i686 GNU/Linux
  2) gdm 2.30.2.is.2.30.0-0ubuntu4

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

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

[Touch-packages] [Bug 1392829] Re: bluez-test-discovery ERROR:dbus.connection:Exception

[Huck-bernhard]

this error is only at Ubuntu 14.10 at 14.04 is it working

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1392829

Title:
  bluez-test-discovery ERROR:dbus.connection:Exception

Status in “bluez” package in Ubuntu:
  New

Bug description:
  ~$ bluez-test-discovery 
  [ 50:85:69:EF:9B:23 ]
  Trusted = 0
  Class = 0x08043c
  ERROR:dbus.connection:Exception in handler for D-Bus signal:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/dbus/connection.py", line 230, in 
maybe_handle_message
  self._handler(*args, **kwargs)
File "/usr/bin/bluez-test-discovery", line 15, in device_found
  value = unicode(value).encode('ascii', 'replace')
  NameError: name 'unicode' is not defined

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bluez 4.101-0ubuntu20
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Nov 14 19:24:49 2014
  InstallationDate: Installed on 2014-11-14 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  InterestingModules: btusb rfcomm bnep bluetooth
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0b05:17cb ASUSTek Computer, Inc. 
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=22d86bc8-8f82-4594-8e4b-10cd3b3ed488 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 00:02:72:CD:03:2A  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN 
RX bytes:1318 acl:0 sco:0 events:55 errors:0
TX bytes:1016 acl:0 sco:0 commands:47 errors:0
  rfkill:
   1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1392829/+subscriptions

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

[Touch-packages] [Bug 1392829] [NEW] bluez-test-discovery ERROR:dbus.connection:Exception

[Huck-bernhard]

Public bug reported:

~$ bluez-test-discovery 
[ 50:85:69:EF:9B:23 ]
Trusted = 0
Class = 0x08043c
ERROR:dbus.connection:Exception in handler for D-Bus signal:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 230, in 
maybe_handle_message
self._handler(*args, **kwargs)
  File "/usr/bin/bluez-test-discovery", line 15, in device_found
value = unicode(value).encode('ascii', 'replace')
NameError: name 'unicode' is not defined

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: bluez 4.101-0ubuntu20
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Nov 14 19:24:49 2014
InstallationDate: Installed on 2014-11-14 (0 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
InterestingModules: btusb rfcomm bnep bluetooth
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 004: ID 0b05:17cb ASUSTek Computer, Inc. 
 Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=22d86bc8-8f82-4594-8e4b-10cd3b3ed488 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
hciconfig:
 hci0:  Type: BR/EDR  Bus: USB
BD Address: 00:02:72:CD:03:2A  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN 
RX bytes:1318 acl:0 sco:0 events:55 errors:0
TX bytes:1016 acl:0 sco:0 commands:47 errors:0
rfkill:
 1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

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


** Tags: amd64 apport-bug utopic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1392829

Title:
  bluez-test-discovery ERROR:dbus.connection:Exception

Status in “bluez” package in Ubuntu:
  New

Bug description:
  ~$ bluez-test-discovery 
  [ 50:85:69:EF:9B:23 ]
  Trusted = 0
  Class = 0x08043c
  ERROR:dbus.connection:Exception in handler for D-Bus signal:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/dbus/connection.py", line 230, in 
maybe_handle_message
  self._handler(*args, **kwargs)
File "/usr/bin/bluez-test-discovery", line 15, in device_found
  value = unicode(value).encode('ascii', 'replace')
  NameError: name 'unicode' is not defined

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bluez 4.101-0ubuntu20
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Nov 14 19:24:49 2014
  InstallationDate: Installed on 2014-11-14 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  InterestingModules: btusb rfcomm bnep bluetooth
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0b05:17cb ASUSTek Computer, Inc. 
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=22d86bc8-8f82-4594-8e4b-10cd3b3ed488 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 00:02:72:CD:03:2A  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN 
RX bytes:1318 acl:0 sco:0 events:55 errors:0
TX bytes:1016 acl:0 sco:0 commands:47 errors:0
  rfkill:
   1: hci0: Bluetooth
Soft blocked: no

[Touch-packages] [Bug 1392744] Re: mako/vivid does not show install progress

[Alejandro J. Cura]

Managed to reproduce on mako vivid #20.

The scope is crashing like this:

Stacktrace:
 #0  0xb39da33c in QDBusAbstractInterface::asyncCallWithArgumentList(QString 
const&, QList const&) () from 
/usr/lib/arm-linux-gnueabihf/libQt5DBus.so.5
 No symbol table info available.
 #1  0xb395b15a in ?? () from 
/usr/lib/arm-linux-gnueabihf/libubuntu-download-manager-client.so.0
 No symbol table info available.
 #2  0xb3afb74a in 
click::DownloadManager::handleDownloadCreated(Ubuntu::DownloadManager::Download*)
 () from 
/usr/lib/arm-linux-gnueabihf/unity-scopes/clickstore/com.canonical.scopes.clickstore.so
 No symbol table info available.
 #3  0xb3af89be in ?? () from 
/usr/lib/arm-linux-gnueabihf/unity-scopes/clickstore/com.canonical.scopes.clickstore.so
 No symbol table info available.
 #4  0xb668b0e4 in QMetaObject::activate(QObject*, int, int, void**) () from 
/usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
 No symbol table info available.
 #5  0xb3979e18 in 
Ubuntu::DownloadManager::Manager::downloadCreated(Ubuntu::DownloadManager::Download*)
 () from /usr/lib/arm-linux-gnueabihf/libubuntu-download-manager-client.so.0
 No symbol table info available.
 #6  0xb3976004 in ?? () from 
/usr/lib/arm-linux-gnueabihf/libubuntu-download-manager-client.so.0
 No symbol table info available.
 #7  0xb668adf6 in QMetaObject::activate(QObject*, int, int, void**) () from 
/usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
 No symbol table info available.
 #8  0xb39fc334 in QDBusPendingCallWatcher::finished(QDBusPendingCallWatcher*) 
() from /usr/lib/arm-linux-gnueabihf/libQt5DBus.so.5
 No symbol table info available.
 #9  0xb39fc374 in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5DBus.so.5
 No symbol table info available.
 Backtrace stopped: previous frame identical to this frame (corrupt stack?)
StacktraceAddressSignature: 
/usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner:11:/usr/lib/arm-linux-gnueabihf/libQt5DBus.so.5.3.2+2333c:/usr/lib/arm-linux-gnueabihf/libubuntu-download-manager-client.so.0.9.0+f15a:/usr/lib/arm-
linux-gnueabihf/unity-scopes/clickstore/com.canonical.scopes.clickstore.so+b574a:/usr/lib/arm-linux-gnueabihf/unity-scopes/clickstore/com.canonical.scopes.clickstore.so+b29be:/usr/lib/arm-linux-gnueabihf/libQt5Core.so.5.3.2+1f70e4
:/usr/lib/arm-linux-gnueabihf/libubuntu-download-manager-client.so.0.9.0+2de18:/usr/lib/arm-linux-gnueabihf/libubuntu-download-manager-client.so.0.9.0+2a004:/usr/lib/arm-linux-gnueabihf/libQt5Core.so.5.3.2+1f6df6:/usr/lib/arm-linu
x-gnueabihf/libQt5DBus.so.5.3.2+45334:/usr/lib/arm-linux-gnueabihf/libQt5DBus.so.5.3.2+45374


** Changed in: unity-scope-click (Ubuntu)
   Status: New => Triaged

** Also affects: ubuntu-download-manager (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scope-click in
Ubuntu.
https://bugs.launchpad.net/bugs/1392744

Title:
  mako/vivid does not show install progress

Status in “ubuntu-download-manager” package in Ubuntu:
  New
Status in “unity-scope-click” package in Ubuntu:
  Triaged

Bug description:
  I use a n4 with the vivid channel and I'm on image #20. When I go to a
  app in the store and click on "Install" I see now change in the UI,
  i.e. no download progress, no change in the button etc. But I do see
  activity in the u-d-m download logs and eventually the screen will
  refresh (or at least turn blank) and the app is installed.

  The log also shows me some "download_db.cpp:285] Parameter count
  mismatch" errors.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-download-manager/+bug/1392744/+subscriptions

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

[Touch-packages] [Bug 1376445] Re: Addition of signon-apparmor-extension causes token lookup problems

[Jamie Strandboge]

FYI, the fix for bug 1392380 should accompany when signon-apparmor-
extension hits rtm. Both bugs are currently identically tagged. This
must not slip past OTA-1 otherwise there is a gaping security hole for
shipping devices.

** Information type changed from Public to Public Security

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-system-settings-
online-accounts in Ubuntu.
https://bugs.launchpad.net/bugs/1376445

Title:
  Addition of signon-apparmor-extension causes token lookup problems

Status in go-onlineaccounts:
  Incomplete
Status in The Savilerow project:
  Invalid
Status in ACL for signond, AppArmor backend:
  Fix Released
Status in Online Accounts setup for Ubuntu Touch:
  In Progress
Status in “ubuntu-system-settings-online-accounts” package in Ubuntu:
  In Progress
Status in “ubuntuone-credentials” package in Ubuntu:
  Confirmed
Status in “signon-apparmor-extension” package in Ubuntu RTM:
  Triaged
Status in “ubuntuone-credentials” package in Ubuntu RTM:
  Confirmed

Bug description:
  As of image ~264 of ubuntu-touch, the signon-apparmor-extension
  package is included. As a result, apps like pay-ui cannot find the
  token any longer, and are not being notified that they are not allowed
  to access the token. The following error appears in the payui log
  file:

  2014-10-01 19:15:51,550 - DEBUG -
  ../../../../lib/SignOn/authsessionimpl.cpp 184 errorSlot
  QDBusError("com.google.code.AccountsSSO.SingleSignOn.Error.PermissionDenied",
  "Client has insuficient permissions to access the
  service.Method:getAuthSessionObjectPath")

To manage notifications about this bug go to:
https://bugs.launchpad.net/go-onlineaccounts/+bug/1376445/+subscriptions

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

[Touch-packages] [Bug 1376445] Re: Addition of signon-apparmor-extension causes token lookup problems

[Jamie Strandboge]

Since this bug is blocking the landing of signon-apparmor-extension, and
the lack of signon-apparmor-extension is a security issue for devices,
marking the bug as Public Security.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-system-settings-
online-accounts in Ubuntu.
https://bugs.launchpad.net/bugs/1376445

Title:
  Addition of signon-apparmor-extension causes token lookup problems

Status in go-onlineaccounts:
  Incomplete
Status in The Savilerow project:
  Invalid
Status in ACL for signond, AppArmor backend:
  Fix Released
Status in Online Accounts setup for Ubuntu Touch:
  In Progress
Status in “ubuntu-system-settings-online-accounts” package in Ubuntu:
  In Progress
Status in “ubuntuone-credentials” package in Ubuntu:
  Confirmed
Status in “signon-apparmor-extension” package in Ubuntu RTM:
  Triaged
Status in “ubuntuone-credentials” package in Ubuntu RTM:
  Confirmed

Bug description:
  As of image ~264 of ubuntu-touch, the signon-apparmor-extension
  package is included. As a result, apps like pay-ui cannot find the
  token any longer, and are not being notified that they are not allowed
  to access the token. The following error appears in the payui log
  file:

  2014-10-01 19:15:51,550 - DEBUG -
  ../../../../lib/SignOn/authsessionimpl.cpp 184 errorSlot
  QDBusError("com.google.code.AccountsSSO.SingleSignOn.Error.PermissionDenied",
  "Client has insuficient permissions to access the
  service.Method:getAuthSessionObjectPath")

To manage notifications about this bug go to:
https://bugs.launchpad.net/go-onlineaccounts/+bug/1376445/+subscriptions

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

[Touch-packages] [Bug 1387691] Re: Media Player should not be visible in the app scope and launcher

[Launchpad Bug Tracker]

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

** Changed in: mediaplayer-app (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mediaplayer-app in Ubuntu.
https://bugs.launchpad.net/bugs/1387691

Title:
  Media Player should not be visible in the app scope and launcher

Status in Media Player App:
  In Progress
Status in Ubuntu UX bugs:
  Fix Committed
Status in “mediaplayer-app” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  Incomplete
Status in “url-dispatcher” package in Ubuntu:
  Incomplete
Status in “mediaplayer-app” package in Ubuntu RTM:
  In Progress

Bug description:
  The mediaplayer is an 'auxiliary app' in the current design approach.
  That means that its purpouse it playback media launched by other apps
  (e.g Messaging) or scopes (e.g. Videos). It should not be launched
  from the App scopes.

  However, the 'Update' section System Settings should still display it
  when an update to mediaplayer is available.

  Current behaviour
  - Mediaplayer app displayed in App Scope, Launcher and Settings

  Desired behaviour
  - Mediaplayer app not displayed in App Scope or Launcher
  - Mediaplayer displayed in Settings > Update

To manage notifications about this bug go to:
https://bugs.launchpad.net/mediaplayer-app/+bug/1387691/+subscriptions

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

[Touch-packages] [Bug 1387691] Re: Media Player should not be visible in the app scope and launcher

[Jim Hodapp]

** Changed in: mediaplayer-app
   Status: New => In Progress

** Changed in: mediaplayer-app (Ubuntu)
   Status: Confirmed => In Progress

** Also affects: mediaplayer-app (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Changed in: mediaplayer-app (Ubuntu RTM)
   Status: New => In Progress

** Changed in: mediaplayer-app
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mediaplayer-app in Ubuntu.
https://bugs.launchpad.net/bugs/1387691

Title:
  Media Player should not be visible in the app scope and launcher

Status in Media Player App:
  In Progress
Status in Ubuntu UX bugs:
  Fix Committed
Status in “mediaplayer-app” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  Incomplete
Status in “url-dispatcher” package in Ubuntu:
  Incomplete
Status in “mediaplayer-app” package in Ubuntu RTM:
  In Progress

Bug description:
  The mediaplayer is an 'auxiliary app' in the current design approach.
  That means that its purpouse it playback media launched by other apps
  (e.g Messaging) or scopes (e.g. Videos). It should not be launched
  from the App scopes.

  However, the 'Update' section System Settings should still display it
  when an update to mediaplayer is available.

  Current behaviour
  - Mediaplayer app displayed in App Scope, Launcher and Settings

  Desired behaviour
  - Mediaplayer app not displayed in App Scope or Launcher
  - Mediaplayer displayed in Settings > Update

To manage notifications about this bug go to:
https://bugs.launchpad.net/mediaplayer-app/+bug/1387691/+subscriptions

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

[Touch-packages] [Bug 1392380] Re: OA gives out all tokens to any app

[Jamie Strandboge]

Adding rtm14 ota-1 touch-2014-11-27. This needs to be fixed for RTM
branch when bug #1376445 is fixed, but bug #1376445 is targeted for
ota-1.

** Also affects: signon (Ubuntu Utopic)
   Importance: Undecided
   Status: New

** Also affects: signon (Ubuntu Vivid)
   Importance: Critical
 Assignee: Alberto Mardegan (mardy)
   Status: Confirmed

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

** Changed in: signon (Ubuntu Utopic)
   Importance: Undecided => Critical

** Also affects: signon (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Tags added: ota-1 rtm14 touch-2014-11-27

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to signon in Ubuntu.
https://bugs.launchpad.net/bugs/1392380

Title:
  OA gives out all tokens to any app

Status in “signon” package in Ubuntu:
  Confirmed
Status in “signon” source package in Utopic:
  Confirmed
Status in “signon” source package in Vivid:
  Confirmed
Status in “signon” package in Ubuntu RTM:
  New

Bug description:
  The attached app will steal all your tokens. All it takes is the
  "accounts" permission in the apparmor file.

  Here's the code: https://pastebin.canonical.com/120398/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1392380/+subscriptions

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

[Touch-packages] [Bug 1337262] Re: kmod should permit use of compressed modules

[Andy Whitcroft]

** Changed in: kmod (Ubuntu)
   Status: New => Triaged

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

** Changed in: kmod (Ubuntu)
 Assignee: (unassigned) => Andy Whitcroft (apw)

** Changed in: kmod (Ubuntu)
Milestone: None => ubuntu-14.12

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kmod in Ubuntu.
https://bugs.launchpad.net/bugs/1337262

Title:
  kmod should permit use of compressed modules

Status in “kmod” package in Ubuntu:
  Triaged

Bug description:
  kmod should permit use of compressed modules. This enables images that
  boot from RAM to be much smaller. In essence this requires only
  changing a build option. Uncompressed modules are still supported.

  A patch is here:
  https://github.com/abligh/kmod/commit/31795c8078ba9ccb6f064d11d0c9e640f8e0fab1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1337262/+subscriptions

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

[Touch-packages] [Bug 1012081] Re: util-linux needs updating to 2.24.2

[Romano Giannetti]

If it's in utopic a not in Trusty, someone should start a SRU request. 
https://wiki.ubuntu.com/StableReleaseUpdates 
But I suspect that, given that this bug has been declined for Trusty, it will 
be quite difficult to get through.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1012081

Title:
  util-linux needs updating to 2.24.2

Status in “util-linux” package in Ubuntu:
  Fix Released
Status in “util-linux” source package in Raring:
  Won't Fix
Status in “util-linux” package in Debian:
  Fix Released

Bug description:
  Applications in the default desktop - specifically gnome-disk-utility
  - depend on behaviour only introduced in util-linux 2.21+.
  Specifically if you select "Show in user interface" in mount options,
  it adds the mount option "x-gvfs-show" to the mount options in
  /etc/fstab. Mounting of this mount point then fails because the option
  is unrecognised.

  Also reported bug from the other point of view in bug #1011257

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: util-linux 2.20.1-1ubuntu3
  ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0
  Uname: Linux 3.4.0-5-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.1.1-0ubuntu2
  Architecture: amd64
  Date: Tue Jun 12 12:38:02 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to quantal on 2012-06-09 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1012081/+subscriptions

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

[Touch-packages] [Bug 1357321] Re: [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu

[Mathieu Trudel-Lapierre]

As far as I know there is nothing left to do on platform-api or NM, and
the issues have already been closed in other bugs; let's just keep the
qtbase task so it's clear where we're at.

** Changed in: platform-api
   Status: In Progress => Invalid

** Changed in: platform-api
 Assignee: Ricardo Mendoza (ricmm) => (unassigned)

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: network-manager (Ubuntu)
 Assignee: Mathieu Trudel-Lapierre (mathieu-tl) => (unassigned)

** Changed in: ofono (Ubuntu)
 Assignee: Alfonso Sanchez-Beato (alfonsosanchezbeato) => Mathieu 
Trudel-Lapierre (mathieu-tl)

** Changed in: ofono (Ubuntu)
 Assignee: Mathieu Trudel-Lapierre (mathieu-tl) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1357321

Title:
  [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu

Status in Platform API:
  Invalid
Status in The Savilerow project:
  New
Status in “network-manager” package in Ubuntu:
  Invalid
Status in “ofono” package in Ubuntu:
  Invalid
Status in “qtbase-opensource-src” package in Ubuntu:
  In Progress

Bug description:
  scope images load fine in wifi, but not on hsdpa even when there is
  good connectivity and browsing works well. Results are return, but
  images do not load.

To manage notifications about this bug go to:
https://bugs.launchpad.net/platform-api/+bug/1357321/+subscriptions

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

[Touch-packages] [Bug 678421] Re: Error message for a faulty ~/.profile script

[Barry Warsaw]

For now I'll keep the hold on lightdm, but if Robert or someone else
wants to debug in real-time, ping me on irc.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/678421

Title:
  Error message for a faulty ~/.profile script

Status in GDM: The Gnome Display Manager:
  New
Status in “gdm” package in Ubuntu:
  In Progress
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “gdm” source package in Trusty:
  Triaged
Status in “lightdm” source package in Trusty:
  In Progress
Status in “gdm” source package in Utopic:
  Triaged
Status in “lightdm” source package in Utopic:
  Fix Committed

Bug description:
  trusty and utopic SRU requests
  ==

  [Impact]

  In case of a syntax error in either of ~/.profile or a few other
  similar files, the Xorg login is interrupted, and the user is taken
  back to the login screen without an explanation. Debugging this
  problem may be a time consuming exercise, especially for non-
  experienced users.

  With the proposed change, lightdm/gdm does not try to load such a
  file, but shows a warning dialog instead. (A warning dialog is also
  shown in case of some other type of error, which would not have caused
  the login to fail.)

  [Test Case]

  To reproduce:

  * Edit ~/.profile and add something bad, e.g. a non-closed parenthesis.
  * Log out and find that you can't log in to a graphical session.

  After installing the proposed lightdm/gdm version, you'll instead see
  the dialog and can log in.

  [Regression Potential]

  Since this is only about improved exception handling, it does not at
  all affect users with correct configuration files. The regression risk
  ought to be minimal.

  [Original description]

  Binary package hint: gdm

  After adding "function AddPath { PATH="$1:$PATH" }" to $HOME/.profile
  made the Xorg startup fail. (At that moment I had already forgotten
  the changes made to the .profile). As I had autologin that meant it
  kept trying to login and finally showed me the graphics
  reconfiguration screen. That sent me to a huge hunt for xorg conf and
  setup problems.

  Anyway finally tracked this down. I had used bash syntax in .profile
  file whereas it was run with sh.

  This is not a bug per se but I think a user mistake in ".profile"
  shouldn't bring the whole xorg startup to a halt as it does with
  autologin. I propose running user ".profile" and ".xprofile" scripts
  so that Xsession script continues running even if they have errors.
  I'm not sure whether this change would have some negative effects as
  well.

  1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct 
16 19:48:22 UTC 2010 i686 GNU/Linux
  2) gdm 2.30.2.is.2.30.0-0ubuntu4

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

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

[Touch-packages] [Bug 1392380] Re: OA gives out all tokens to any app

[Alberto Mardegan]

Just to add some more information in order to have a more clear idea of
the seriousness of this bug: accounts which are created when the signon-
apparmor-extension is installed will work fine: apps won't be able to
abuse them.

This bug only affects the accounts which were created when the extension
was not installed: even if the extension gets installed later on, the
ACL checks will be bypassed and any app can get access to any account.

Fixing this bug will make all accounts (regardless of when they were
created) be protected by the ACL once the signon-apparmor-extension is
installed.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to signon in Ubuntu.
https://bugs.launchpad.net/bugs/1392380

Title:
  OA gives out all tokens to any app

Status in “signon” package in Ubuntu:
  Confirmed

Bug description:
  The attached app will steal all your tokens. All it takes is the
  "accounts" permission in the apparmor file.

  Here's the code: https://pastebin.canonical.com/120398/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1392380/+subscriptions

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

[Touch-packages] [Bug 209256] Re: different hintstyle issue

[Bug Watch Updater]

** Bug watch added: GNOME Bug Tracker #657047
   https://bugzilla.gnome.org/show_bug.cgi?id=657047

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/209256

Title:
  different hintstyle issue

Status in libcairo  -  cairo vector graphics library:
  Confirmed
Status in “cairo” package in Ubuntu:
  Triaged

Bug description:
  I'd like to render my fonts in different hintstyles.

  To be precise, I have chinese font and western language fonts. For the
  chinese font, I'd like it to be rendered in hintfull, but for other
  fonts, I'd prefer hintslight.

  Ok, I configured in the fontconfig file, but it didn't make any
  change. All the fonts are in the same hintstyle, depending on the
  configuration in  gnome-appearance-properties.

  I googled for quite a long time and finally I got one solution.

  In the file cairo-ft-font.c, in function _cairo_ft_options_merge, just
  comment the following line:

  // if (options->base.hint_style == CAIRO_HINT_STYLE_DEFAULT)

  and recompile, now everything works fine. The fonts are rendered
  according to the hintstyles configured in fontconfig.

  I don't know if this is really a bug of libcairo. If I'm wrong, please
  accept my apology.

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

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

[Touch-packages] [Bug 678421] Re: Error message for a faulty ~/.profile script

[Barry Warsaw]

pay-service crashed, leaving a core file and the following in
.xsesssion.old.  Not sure if this is related.

upstart: pay-service main process (6149) killed by ABRT signal

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/678421

Title:
  Error message for a faulty ~/.profile script

Status in GDM: The Gnome Display Manager:
  New
Status in “gdm” package in Ubuntu:
  In Progress
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “gdm” source package in Trusty:
  Triaged
Status in “lightdm” source package in Trusty:
  In Progress
Status in “gdm” source package in Utopic:
  Triaged
Status in “lightdm” source package in Utopic:
  Fix Committed

Bug description:
  trusty and utopic SRU requests
  ==

  [Impact]

  In case of a syntax error in either of ~/.profile or a few other
  similar files, the Xorg login is interrupted, and the user is taken
  back to the login screen without an explanation. Debugging this
  problem may be a time consuming exercise, especially for non-
  experienced users.

  With the proposed change, lightdm/gdm does not try to load such a
  file, but shows a warning dialog instead. (A warning dialog is also
  shown in case of some other type of error, which would not have caused
  the login to fail.)

  [Test Case]

  To reproduce:

  * Edit ~/.profile and add something bad, e.g. a non-closed parenthesis.
  * Log out and find that you can't log in to a graphical session.

  After installing the proposed lightdm/gdm version, you'll instead see
  the dialog and can log in.

  [Regression Potential]

  Since this is only about improved exception handling, it does not at
  all affect users with correct configuration files. The regression risk
  ought to be minimal.

  [Original description]

  Binary package hint: gdm

  After adding "function AddPath { PATH="$1:$PATH" }" to $HOME/.profile
  made the Xorg startup fail. (At that moment I had already forgotten
  the changes made to the .profile). As I had autologin that meant it
  kept trying to login and finally showed me the graphics
  reconfiguration screen. That sent me to a huge hunt for xorg conf and
  setup problems.

  Anyway finally tracked this down. I had used bash syntax in .profile
  file whereas it was run with sh.

  This is not a bug per se but I think a user mistake in ".profile"
  shouldn't bring the whole xorg startup to a halt as it does with
  autologin. I propose running user ".profile" and ".xprofile" scripts
  so that Xsession script continues running even if they have errors.
  I'm not sure whether this change would have some negative effects as
  well.

  1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct 
16 19:48:22 UTC 2010 i686 GNU/Linux
  2) gdm 2.30.2.is.2.30.0-0ubuntu4

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

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

[Touch-packages] [Bug 209256]

[Lavir the Whiolet]

Created attachment 109191
GIMP font rendering

https://bugzilla.gnome.org/show_bug.cgi?id=657047 refers to this bug.
The referring bug is about black border around text rendered with Cairo
with non-black color, antialiasing turned on and hinting set to
"medium".

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/209256

Title:
  different hintstyle issue

Status in libcairo  -  cairo vector graphics library:
  Confirmed
Status in “cairo” package in Ubuntu:
  Triaged

Bug description:
  I'd like to render my fonts in different hintstyles.

  To be precise, I have chinese font and western language fonts. For the
  chinese font, I'd like it to be rendered in hintfull, but for other
  fonts, I'd prefer hintslight.

  Ok, I configured in the fontconfig file, but it didn't make any
  change. All the fonts are in the same hintstyle, depending on the
  configuration in  gnome-appearance-properties.

  I googled for quite a long time and finally I got one solution.

  In the file cairo-ft-font.c, in function _cairo_ft_options_merge, just
  comment the following line:

  // if (options->base.hint_style == CAIRO_HINT_STYLE_DEFAULT)

  and recompile, now everything works fine. The fonts are rendered
  according to the hintstyles configured in fontconfig.

  I don't know if this is really a bug of libcairo. If I'm wrong, please
  accept my apology.

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

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

[Touch-packages] [Bug 678421] Re: Error message for a faulty ~/.profile script

[Barry Warsaw]

Hmm, as 1.13.0-0ubuntu1 just showed up in vivid, it broke my login in
the follow way.  Note that I always try devel channel updates in a VM
with a snapshotted disk so I'm able to revert and do some further
investigating.  Looking at the dist-upgrade packages, I suspect the
lightdm changes are affecting me, but I'm going to continue to
investigate.

So, when I log in, I do get several warnings in a dialog.  Most are
because I use `source` instead of `.` to source other shell files.  What
shell is lightdm using these days?  Still, even with the warnings, I can
log in just fine.

Anyway, when I change them all to `.` I still get one warning about my
use of shopt, but I'll just ignore that for now.  However, logins are
now completely broken.  I see the screen blank and then I'm thrown back
to the login screen.  ~/.xsession-errors is empty and I can find no
other log file either in $HOME or /var/log that contains any information
about what's going wrong.

I'm going to pin lightdm and dist-upgrade everything else just to verify
that the lightdm update is causing my problems.  How can I debug the
login crash after I fix my login scripts?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/678421

Title:
  Error message for a faulty ~/.profile script

Status in GDM: The Gnome Display Manager:
  New
Status in “gdm” package in Ubuntu:
  In Progress
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “gdm” source package in Trusty:
  Triaged
Status in “lightdm” source package in Trusty:
  In Progress
Status in “gdm” source package in Utopic:
  Triaged
Status in “lightdm” source package in Utopic:
  Fix Committed

Bug description:
  trusty and utopic SRU requests
  ==

  [Impact]

  In case of a syntax error in either of ~/.profile or a few other
  similar files, the Xorg login is interrupted, and the user is taken
  back to the login screen without an explanation. Debugging this
  problem may be a time consuming exercise, especially for non-
  experienced users.

  With the proposed change, lightdm/gdm does not try to load such a
  file, but shows a warning dialog instead. (A warning dialog is also
  shown in case of some other type of error, which would not have caused
  the login to fail.)

  [Test Case]

  To reproduce:

  * Edit ~/.profile and add something bad, e.g. a non-closed parenthesis.
  * Log out and find that you can't log in to a graphical session.

  After installing the proposed lightdm/gdm version, you'll instead see
  the dialog and can log in.

  [Regression Potential]

  Since this is only about improved exception handling, it does not at
  all affect users with correct configuration files. The regression risk
  ought to be minimal.

  [Original description]

  Binary package hint: gdm

  After adding "function AddPath { PATH="$1:$PATH" }" to $HOME/.profile
  made the Xorg startup fail. (At that moment I had already forgotten
  the changes made to the .profile). As I had autologin that meant it
  kept trying to login and finally showed me the graphics
  reconfiguration screen. That sent me to a huge hunt for xorg conf and
  setup problems.

  Anyway finally tracked this down. I had used bash syntax in .profile
  file whereas it was run with sh.

  This is not a bug per se but I think a user mistake in ".profile"
  shouldn't bring the whole xorg startup to a halt as it does with
  autologin. I propose running user ".profile" and ".xprofile" scripts
  so that Xsession script continues running even if they have errors.
  I'm not sure whether this change would have some negative effects as
  well.

  1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct 
16 19:48:22 UTC 2010 i686 GNU/Linux
  2) gdm 2.30.2.is.2.30.0-0ubuntu4

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

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