[Touch-packages] [Bug 1645698] Re: [SRU] Upgrade network-manager to latest point release

[Ara Pulido]

** Changed in: oem-priority
   Status: Triaged => Fix Released

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

Title:
  [SRU] Upgrade network-manager to latest point release

Status in OEM Priority Project:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Released
Status in network-manager source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  This SRU would try to have the latest well-tested upstream point
  release (1.2.6) of 1.2.x land in Xenial, which is the successor of the
  current 1.2.2 version, fixing quite some bugs that's suitable to land
  in the stable branch.

  https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-2

  [Test Case]

  After installing the updated version, users should be able to avoid
  some mem leaks in some cases and have generally improved DNS related
  experiences.

  Also, as this is a general point release update, cases described in
  https://wiki.ubuntu.com/NetworkManager/DistroTesting should be used
  for smoke testing.

  [Regression Potential]

  This is a bug/regression fix for 1.2.2 and 1.2.4, which is quite
  complete.

  [Other Info]
  The first attempt at SRUing this to xenial was for 1.2.4 but it failed 
verification. This second attempt matches yakkety with 1.2.6.

  Parallel building was enabled in xenial to keep the diff between
  xenial and yakkety minimal since they are basically in sync now.
  Parallel building was enabled in the yakkety package in May 2016 so
  it's been working fine for a while.

  needed by:
  lp #1647283

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1645698/+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 1630156] Re: No password needed to Log in after cancel the password and then reset again

[Ara Pulido]

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

** Changed in: oem-priority/trusty
   Status: New => Confirmed

** Changed in: oem-priority
   Status: New => Confirmed

** Description changed:

  OS: 14.04 trusty
+ 
+ Tested with 16.10
+ lightdm version is 1.19.5
+ issue still exist
+ 
  
  1. Go to path "System Setting --> User Accounts--> Unlock" to unlock system 
setting.
  2. Click "Password --> Action --> Log in without password -->Change to clear 
Log in password.
  3. Reboot and log to desktop without password.
  4. Then do the similar action "Set a password now" as the same way to set Log 
in password.
  5. Reboot but still no password needed at Log in interface.

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

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

Title:
  No password needed to Log in after cancel the password and then reset
  again

Status in Light Display Manager:
  New
Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project trusty series:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  OS: 14.04 trusty

  Tested with 16.10
  lightdm version is 1.19.5
  issue still exist

  
  1. Go to path "System Setting --> User Accounts--> Unlock" to unlock system 
setting.
  2. Click "Password --> Action --> Log in without password -->Change to clear 
Log in password.
  3. Reboot and log to desktop without password.
  4. Then do the similar action "Set a password now" as the same way to set Log 
in password.
  5. Reboot but still no password needed at Log in interface.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1630156/+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 1630156] Re: No password needed to Log in after cancel the password and then reset again

[Ara Pulido]

What version of lightdm are you using?

Is this happening in Yakkety?

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

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

Title:
  No password needed to Log in after cancel the password and then reset
  again

Status in Light Display Manager:
  New
Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  New
Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  OS: 14.04 trusty

  1. Go to path "System Setting --> User Accounts--> Unlock" to unlock system 
setting.
  2. Click "Password --> Action --> Log in without password -->Change to clear 
Log in password.
  3. Reboot and log to desktop without password.
  4. Then do the similar action "Set a password now" as the same way to set Log 
in password.
  5. Reboot but still no password needed at Log in interface.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1630156/+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 1578127] Re: Sometimes WLAN detects no SSID after s3

[Ara Pulido]

Marking as Fix Released, based on Chih's comment

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Fix Released

** Changed in: oem-priority
   Status: Incomplete => Fix Released

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

Title:
  Sometimes WLAN detects no SSID after s3

Status in NetworkManager:
  New
Status in OEM Priority Project:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  [Steps to reproduce]
  1. Boot into OS
  2. Do s3 a few times
  3. Check if wifi is still working after s3

  [Expected results]
  wifi still working correctly after s3

  [Actual results]
  1. Wifi shows "disconnected" in network-manager (both in applet and from 
command "nmcli d status")
  2. Only one random SSID is displayed in network-manager applet, but wifi 
connection cannot be established at all with this SSID. Clicking on the SSID 
results in pop up window in the comment #2 below
  3. "nmcli d wifi rescan" does not resolve issue
  4.  "iwlist [interface] scan" returns nothing and does not reolve issue
  5. "nmcli d wifi connect [any SSID that you know should exist]" results in 
SSID not found and does not resolve issue
  6. "sudo service network-manager restart", warm boot, cold boot resolves issue

  [Details]
  OS: Xenial based OEM image
  WLAN module: Marvel [11ab:2b38]
  network-manager:
  - 1.2.0-0ubuntu0.16.04.1 (fail rate 1/20~ 1/15)
  - 1.1.93 (fail rate 1/15)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1578127/+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 1490937] Re: Unavailable port selected by default

[Ara Pulido]

Marking as Invalid for Xenial

** Changed in: oem-priority
   Status: Incomplete => Invalid

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

Title:
  Unavailable port selected by default

Status in OEM Priority Project:
  Invalid
Status in OEM Priority Project trusty series:
  Won't Fix
Status in PulseAudio:
  In Progress
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  In case one card has only unavailable ports, it might be still be
  selected as default, even though there are available ports on other
  cards.

  E g, on a HTPC which have only Headphone and HDMI outputs, and these
  two outputs are on separate cards, the headphone port might be
  selected even if the HDMI port is available and the headphone port is
  not.

  Probably PulseAudio's routing system needs to be rewritten to be more
  port based to fix this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1490937/+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 1562822] Re: Bluetooth Browse Files... not working

[Ara Pulido]

** Changed in: oem-priority
   Status: Fix Committed => Fix Released

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

Title:
  Bluetooth Browse Files... not working

Status in OEM Priority Project:
  Fix Released
Status in indicator-bluetooth package in Ubuntu:
  Fix Released
Status in unity-control-center package in Ubuntu:
  Fix Released
Status in indicator-bluetooth source package in Xenial:
  Fix Released
Status in unity-control-center source package in Xenial:
  Fix Released

Bug description:
  indicator

  * Impact
  The bluetooth indicator includes a non working "browse files..." items

  * Test case
  connect/pair a phone which does obex, open the bluetooth indicator and select 
the device, the only action listed should be "send"

  * Regression potential
  none, it's removing a widget which was doing nothing

  --
  ucc

  * Impact
  The bluetooth settings include a non working "browse files..." items

  * Test case
  connect/pair a phone which does obex, open settings->bluetooth, the only 
action listed should be "send"

  * Regression potential
  none, it's removing a widget which was doing nothing

  --

  Mobile phone: LG L40 Android 4.4.2

  1. Connecting to Phone is successful shown.
  2. Click on Button  "Browse Files... " nothing happen.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity-control-center 15.04.0+16.04.20160315-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 28 13:31:39 2016
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2016-02-04 (52 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160204)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1562822/+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 1586941] Re: Randomly segfault on BYT with 4.4 kernel

[Ara Pulido]

** Changed in: oem-priority
   Status: Incomplete => Confirmed

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

Title:
  Randomly segfault on BYT with 4.4 kernel

Status in OEM Priority Project:
  Confirmed
Status in upstart :
  New
Status in upstart package in Ubuntu:
  New

Bug description:
  
  We have a randomly crash bug when using 14.04 (trusty) upstart 
(1.12.1-0ubuntu4.2).

  We've tried the workarounds of LP:1447756 but it doesn't work.
  Also the test case doesn't crash. So we think this is a new bug.

  The bug is also happened on very early stages. And inside the
  installer, it crashes more often then the system. We see it core
  dumped in the installer, but not about to get the core file because
  the squashfs only keeps file in the memory.

  Also when run on system, the filesystem seems to be read-only then so
  there's also no logs.

  We are using 4.4 kernel (linux-image-4.4.0-22-generic
  4.4.0-22.40~14.04.1)

  I'll paste some images and logs after.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1586941/+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 1438587] Re: connect button is grey when connecting to Ad-hoc SSID

[Ara Pulido]

** Changed in: oem-priority
   Status: Incomplete => Invalid

** Changed in: oem-priority/trusty
   Status: New => Invalid

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

Title:
  connect button is grey when connecting to Ad-hoc SSID

Status in NetworkManager:
  New
Status in OEM Priority Project:
  Invalid
Status in OEM Priority Project trusty series:
  Invalid
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  First, I created an adhoc network through nm-applet->create new wifi
  network.

  Network Name: 111
  wi-fi security: WEP 128-bit Passphrase
  key: 222

  Then click create button and wait for its ready.

  using another machine to connect to this "111", enter password 222 and
  you can find that the connect button is grey, you can not click it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1438587/+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 1490937] Re: Unavailable port selected by default

[Ara Pulido]

Does this happen in Xenial?

** Changed in: oem-priority
   Status: New => Won't Fix

** Changed in: oem-priority
   Status: Won't Fix => New

** Changed in: oem-priority
   Status: New => Incomplete

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

Title:
  Unavailable port selected by default

Status in OEM Priority Project:
  Incomplete
Status in OEM Priority Project trusty series:
  Won't Fix
Status in PulseAudio:
  In Progress
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  In case one card has only unavailable ports, it might be still be
  selected as default, even though there are available ports on other
  cards.

  E g, on a HTPC which have only Headphone and HDMI outputs, and these
  two outputs are on separate cards, the headphone port might be
  selected even if the HDMI port is available and the headphone port is
  not.

  Probably PulseAudio's routing system needs to be rewritten to be more
  port based to fix this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1490937/+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 1562822] Re: Bluetooth Browse Files... not working

[Ara Pulido]

** Changed in: oem-priority
   Status: New => Fix Committed

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

Title:
  Bluetooth Browse Files... not working

Status in OEM Priority Project:
  Fix Committed
Status in indicator-bluetooth package in Ubuntu:
  Fix Released
Status in unity-control-center package in Ubuntu:
  Fix Released
Status in indicator-bluetooth source package in Xenial:
  Fix Committed
Status in unity-control-center source package in Xenial:
  Fix Released

Bug description:
  indicator

  * Impact
  The bluetooth indicator includes a non working "browse files..." items

  * Test case
  connect/pair a phone which does obex, open the bluetooth indicator and select 
the device, the only action listed should be "send"

  * Regression potential
  none, it's removing a widget which was doing nothing

  --
  ucc

  * Impact
  The bluetooth settings include a non working "browse files..." items

  * Test case
  connect/pair a phone which does obex, open settings->bluetooth, the only 
action listed should be "send"

  * Regression potential
  none, it's removing a widget which was doing nothing

  --

  Mobile phone: LG L40 Android 4.4.2

  1. Connecting to Phone is successful shown.
  2. Click on Button  "Browse Files... " nothing happen.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity-control-center 15.04.0+16.04.20160315-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 28 13:31:39 2016
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2016-02-04 (52 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160204)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1562822/+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 1301720] Re: [Text Entry] Missing English input in Simplified and Traditional Chinese default enviroment

[Ara Pulido]

** Changed in: oem-priority
   Status: Triaged => Won't Fix

** No longer affects: oem-priority/trusty

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

Title:
  [Text Entry] Missing English input in Simplified and Traditional
  Chinese default enviroment

Status in OEM Priority Project:
  Won't Fix
Status in ibus package in Ubuntu:
  Confirmed
Status in ibus source package in Trusty:
  Confirmed

Bug description:
  English input source is missing from Traditional Chinese and
  Simplified Chinese 14.04 default environment.

  This cause a problem that user have to add back English input source
  manually for each fresh installation.

  It's been verified in Japanese and Korean environment does not have
  this issue.

  
  Originally found this issue on 14.04 beta2 with Traditional Chinese:

  LANG=zh_TW.UTF-8
  LANGUAGE=
  LC_CTYPE="zh_TW.UTF-8"
  LC_NUMERIC="zh_TW.UTF-8"
  LC_TIME="zh_TW.UTF-8"
  LC_COLLATE="zh_TW.UTF-8"
  LC_MONETARY="zh_TW.UTF-8"
  LC_MESSAGES="zh_TW.UTF-8"
  LC_PAPER="zh_TW.UTF-8"
  LC_NAME="zh_TW.UTF-8"
  LC_ADDRESS="zh_TW.UTF-8"
  LC_TELEPHONE="zh_TW.UTF-8"
  LC_MEASUREMENT="zh_TW.UTF-8"
  LC_IDENTIFICATION="zh_TW.UTF-8"
  LC_ALL=

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140324-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.339
  CurrentDesktop: Unity
  Date: Thu Apr  3 03:50:26 2014
  ExecutablePath: /usr/bin/unity-control-center
  LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  ProcEnviron:
   TERM=xterm
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=zh_TW.UTF-8
   XDG_RUNTIME_DIR=
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu12
   deja-dup 29.5-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1301720/+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 1069964] Re: Two processes attempt to mount blank optical discs

[Ara Pulido]

** Changed in: oem-priority
   Status: Incomplete => Won't Fix

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

Title:
  Two processes attempt to mount blank optical discs

Status in OEM Priority Project:
  Won't Fix
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  This behavior can be reproduced using either a live USB or an
  installed version of the effected flavors. Simply insert a blank
  optical disc in the drive.

  The behavior differs slightly in Ubuntu GNOME as the notification to
  either Open with CD/DVD Creator or Eject is displayed twice - that is
  after simply clicking on the X to close that notification it closes
  but a new duplicate notification appaers immediately. The GNOME
  Classic session is not effected at all.

  In all other effected flavors and/or desktop environments a
  notification appears stating "Unable to mount Blank disc. Location is
  already mounted". Effected flavors and DE's include Ubuntu w/Unity,
  gnome-session-flashback, and Ubuntu MATE.

  Versions effected include Trusty, Utopic, and Vivid. I assume that two
  separate processes are actually attempting to mount the blank optical
  media, rather than just the file manager attemting to do so, because
  both Nautilus and Caja are effected (based on some of the comments
  below possibly also Nemo).

  While purely cosmetic in nature I'd certainly be willing to try and
  troubleshoot this if someone more tech savvy would provide some
  debugging instructions.

  Original content begins below:

  This error message comes up, while still able to burn, read/write etc. It 
occurs in quantal when inserting a CD/DVD into the drive, but it did not happen 
in precice.
  Screenshot:
  http://i47.tinypic.com/4v0aj6.png

  Burner: LG HL-DT-ST DVDRAM GH24NS90

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gnome-settings-daemon 3.4.2-0ubuntu14
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  Date: Mon Oct 22 19:50:35 2012
  ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-fallback-mount-helper
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1069964/+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 1059872] Re: Error formatting disk using disk utility

[Ara Pulido]

** No longer affects: oem-priority

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

Title:
  Error formatting disk using disk utility

Status in DarGUI:
  New
Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Trusty:
  Triaged
Status in util-linux package in Debian:
  Fix Released

Bug description:
  [Impact]

  Formatting a SD card using the disk utility fails with an error
  message

  "Error formatting disk - Error synchronizing after initial wipe: Timed
  out waiting for object (udisks-error-quark, 0)"

  The underlying problem is that the "wipefs" tool from util-linux does
  not work any more.

  You can work around this bug in gnome-disk-utility using these steps:

  * After selecting the SD card, instead of clicking the gear icon to format,
click the partition in the "Volumes" section.

  * Delete the partition ("minus" icon)

  * Create a new partition

  [Test Case]

  $ sudo modprobe scsi_debug dev_size_mb=200
  # this creates a new /dev/sdX, usually /dev/sdb; check dmesg!

  # now create a partition table
  $ cat 

[Touch-packages] [Bug 1069964] Re: Two processes attempt to mount blank optical discs

[Ara Pulido]

** Changed in: oem-priority
   Status: New => Incomplete

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

Title:
  Two processes attempt to mount blank optical discs

Status in OEM Priority Project:
  Incomplete
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  This behavior can be reproduced using either a live USB or an
  installed version of the effected flavors. Simply insert a blank
  optical disc in the drive.

  The behavior differs slightly in Ubuntu GNOME as the notification to
  either Open with CD/DVD Creator or Eject is displayed twice - that is
  after simply clicking on the X to close that notification it closes
  but a new duplicate notification appaers immediately. The GNOME
  Classic session is not effected at all.

  In all other effected flavors and/or desktop environments a
  notification appears stating "Unable to mount Blank disc. Location is
  already mounted". Effected flavors and DE's include Ubuntu w/Unity,
  gnome-session-flashback, and Ubuntu MATE.

  Versions effected include Trusty, Utopic, and Vivid. I assume that two
  separate processes are actually attempting to mount the blank optical
  media, rather than just the file manager attemting to do so, because
  both Nautilus and Caja are effected (based on some of the comments
  below possibly also Nemo).

  While purely cosmetic in nature I'd certainly be willing to try and
  troubleshoot this if someone more tech savvy would provide some
  debugging instructions.

  Original content begins below:

  This error message comes up, while still able to burn, read/write etc. It 
occurs in quantal when inserting a CD/DVD into the drive, but it did not happen 
in precice.
  Screenshot:
  http://i47.tinypic.com/4v0aj6.png

  Burner: LG HL-DT-ST DVDRAM GH24NS90

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gnome-settings-daemon 3.4.2-0ubuntu14
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  Date: Mon Oct 22 19:50:35 2012
  ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-fallback-mount-helper
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1069964/+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 1059872] Re: Error formatting disk using disk utility

[Ara Pulido]

** Changed in: oem-priority
   Status: New => Incomplete

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

Title:
  Error formatting disk using disk utility

Status in DarGUI:
  New
Status in OEM Priority Project:
  Incomplete
Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Trusty:
  Triaged
Status in util-linux package in Debian:
  Fix Released

Bug description:
  [Impact]

  Formatting a SD card using the disk utility fails with an error
  message

  "Error formatting disk - Error synchronizing after initial wipe: Timed
  out waiting for object (udisks-error-quark, 0)"

  The underlying problem is that the "wipefs" tool from util-linux does
  not work any more.

  You can work around this bug in gnome-disk-utility using these steps:

  * After selecting the SD card, instead of clicking the gear icon to format,
click the partition in the "Volumes" section.

  * Delete the partition ("minus" icon)

  * Create a new partition

  [Test Case]

  $ sudo modprobe scsi_debug dev_size_mb=200
  # this creates a new /dev/sdX, usually /dev/sdb; check dmesg!

  # now create a partition table
  $ cat 

[Touch-packages] [Bug 1032433] Re: Using WEP 128-bit Passphrase, Ad-hoc connection cannot be established

[Ara Pulido]

** Changed in: oem-priority
   Status: Confirmed => Won't Fix

** No longer affects: oem-priority/precise

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

Title:
  Using WEP 128-bit Passphrase, Ad-hoc connection cannot be established

Status in OEM Priority Project:
  Won't Fix
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When setting up an ad-hoc wifi connection, if choose "WEP 128-bit 
Passphrase", the connection cannot be established.
  If choose "None" or "WEP 40/128-bit Key", it can be established successfully.

  Steps to reproduce:
  1. Choose "Create new Wireless Network" in network applet
  2. Choose "WEP 128-bit Passphrase" and create an ad-hoc connection
  3. Use another computer to connect the same ad-hoc ESSID
  4. The connection cannot be established

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1032433/+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 1564156] Re: xenial: invalid opcode when using llvmpipe

[Ara Pulido]

** Changed in: oem-priority
   Status: Fix Committed => Fix Released

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

Title:
  xenial: invalid opcode when using llvmpipe

Status in OEM Priority Project:
  Fix Released
Status in System76:
  Fix Released
Status in Release Notes for Ubuntu:
  Fix Released
Status in llvm-toolchain-3.8 package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in llvm-toolchain-3.8 source package in Xenial:
  Fix Released
Status in mesa source package in Xenial:
  Confirmed

Bug description:
  [Description updated to reflect state of 16.04 release ISO]

  == In summary ==

  If you have an Intel Skylake (6th gen) CPU and an NVIDIA GPU (or
  possibly other GPUs that likewise require use of the llvmpipe opengl
  software fallback), a work-around is needed to install Ubuntu 16.04
  desktop.

  To work-around this, you'll need to:

  1) Choose "Install Ubuntu" in the pre-boot menu (rather than "Try
  Ubuntu without installing")

  2) Check "Download updates while installing Ubuntu"

  ** Note: "Download updates while installing Ubuntu" doesn't currently
  seem to be working. If after installing 16.04 on effected Skylake
  hardware you find that Unity/Compiz is broken, switch to a VT with
  Control+Alt+F1, login, and then run:

  sudo apt-get update
  sudo apt-get dist-upgrade

  You should see the `libllvm3.8` package get updated. After a reboot,
  Unity/Compiz should be working.

  == In detail ==

  The Ubuntu 16.04 desktop ISOs include libllvm3.8 1:3.8-2ubuntu1, which
  has a bug that results in invalid JIT code generation when using the
  mesa llvmpipe opengl software fallback on Skylake CPUs.

  When you encounter this bug, Unity/Compiz will fail to start, and
  you'll see something like this in dmesg:

  [ 2092.557913] traps: compiz[10155] trap invalid opcode
  ip:7efc940030d4 sp:7ffccd914ea0 error:0

  libllvm3.8 1:3.8-2ubuntu3 fixes this issue, but the fix did not make
  it onto the 16.04 release ISOs. It will be included on the 16.04.1
  ISOs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1564156/+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 1578127] Re: Sometimes WLAN detects no SSID after s3

[Ara Pulido]

Marking as Incomplete, as we are waiting on a retest

** Changed in: oem-priority
   Status: New => Incomplete

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

Title:
  Sometimes WLAN detects no SSID after s3

Status in NetworkManager:
  New
Status in OEM Priority Project:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  [Steps to reproduce]
  1. Boot into OS
  2. Do s3 a few times
  3. Check if wifi is still working after s3

  [Expected results]
  wifi still working correctly after s3

  [Actual results]
  1. Wifi shows "disconnected" in network-manager (both in applet and from 
command "nmcli d status")
  2. Only one random SSID is displayed in network-manager applet, but wifi 
connection cannot be established at all with this SSID. Clicking on the SSID 
results in pop up window in the comment #2 below
  3. "nmcli d wifi rescan" does not resolve issue
  4.  "iwlist [interface] scan" returns nothing and does not reolve issue
  5. "nmcli d wifi connect [any SSID that you know should exist]" results in 
SSID not found and does not resolve issue
  6. "sudo service network-manager restart", warm boot, cold boot resolves issue

  [Details]
  OS: Xenial based OEM image
  WLAN module: Marvel [11ab:2b38]
  network-manager:
  - 1.2.0-0ubuntu0.16.04.1 (fail rate 1/20~ 1/15)
  - 1.1.93 (fail rate 1/15)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1578127/+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 1490347] Re: [Regresision] 16:04 + 15:10 - Cannot pair with devices using (Legacy) PIN codes

[Ara Pulido]

** Also affects: bluez (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  [Regresision] 16:04 + 15:10 - Cannot pair with devices using (Legacy)
  PIN codes

Status in Bluez Utilities:
  New
Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in bluez package in Ubuntu:
  Triaged
Status in bluez source package in Wily:
  Triaged
Status in bluez source package in Xenial:
  New

Bug description:
  Bluez 5.3 does not have support for pairing with devices (such as
  keyboards) that use a PIN code for pairing.

  A mouse pairs correctly.

  From my research it seems as if the ChromeOS project developed patches
  to fix this and they are supposed to have been included in Bluez 5.4
  (that statement dated April 2013) but I've not yet identified them.

  "The agent's implementation in bt_console/bluetoothctl upstream is
  incomplete, missing some functions like DisplayPincode."

  https://code.google.com/p/chromium/issues/detail?id=222661

  Along with the loss of Headset profiles meaning VoIP applications can
  no longer use HSP/HFP profiles (requiring functionality yet to land in
  Ofono) this cripples the use of Bluetooth for much else than A2DP or
  mouse input.

  Attempting to pair with, for example, an Apple Wireless Keyboard that
  pairs and works correctly with 14.04 LTS, fails totally on 15.10.

  The mouse shown below is already paired, connected, and working.

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# agent on
  Agent registered
  [bluetooth]# default-agent
  Default agent request successful
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller 00:1F:3A:E0:0A:AF Discovering: yes
  [CHG] Device 00:0A:95:4B:BD:C2 LegacyPairing: yes
  [CHG] Device 00:0A:95:4B:BD:C2 RSSI: -48
  [bluetooth]# pair 00:0A:95:4B:BD:C2
  Attempting to pair with 00:0A:95:4B:BD:C2

  >>> at this point nothing is happening

  >>> so I press Enter on the keyboard and...
  [agent] PIN code: 791166
  >>> I type 791166 Enter and ...
  [agent] PIN code: 237744
  >>> I type 237744 Enter and...
  [agent] PIN code: 358866
  >>> I type 358866 Enter and...
  Request PIN code
  [agent] Enter PIN code: 1234
  >>> I type 1234 Enter on the keyboard and 1234 at the prompt...
  Failed to pair: org.bluez.Error.AuthenticationFailed

  This cycle repeats in various permuations. Sometimes the final
  "Request PIN code" does not appear.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1490347/+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 1574347] Re: WiFi network list disappears from network manager applet

[Ara Pulido]

** Also affects: network-manager (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  WiFi network list disappears from network manager applet

Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Xenial:
  New

Bug description:
  Issue is in Ubuntu 16.04 LTS amd64 version.

  Steps to reproduce: -

  1. Connect to a WiFi AP.
  2. Switch off the AP OR switch off the wifi in the computer.
  3. Switch point (2) back on.
  4. The network will get connected to the AP it was connected to in point (1).

  Problems:-

  1. The network manager applet does not show the list of WiFI APs it can find.
  2. The network manager applet does not the name of the AP to which it is 
connected
  3. The icon of the applet shows two vertical arrows in opposite direction - 
the wired connection symbol and NOT the wifi connected icon.

  
  Temporary Workaround:-
  Log out and again log back in.

  Please solve this issue asap.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr 24 23:15:34 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-04-23 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.1.1 dev wlp18s0  proto static  metric 600 
   169.254.0.0/16 dev wlp18s0  scope link  metric 1000 
   192.168.1.0/24 dev wlp18s0  proto kernel  scope link  src 192.168.1.99  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  
AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH   
ACTIVE  DEVICE   STATE  ACTIVE-PATH
   Airtel-201  d263b201-9281-427e-94e2-762fa620813c  802-11-wireless  
1461519922  Sunday 24 April 2016 11:15:22 PM IST  yes  0
 no/org/freedesktop/NetworkManager/Settings/0  yes wlp18s0  
activated  /org/freedesktop/NetworkManager/ActiveConnection/8 
   Wired connection 1  142942d4-d247-4880-9bab-1eeafc29ca86  802-3-ethernet   
1461508904  Sunday 24 April 2016 08:11:44 PM IST  yes  4294966297   
 no/org/freedesktop/NetworkManager/Settings/2  no  --   --  
   --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp18s0  wifi  connected/org/freedesktop/NetworkManager/Devices/1  
Airtel-201  d263b201-9281-427e-94e2-762fa620813c  
/org/freedesktop/NetworkManager/ActiveConnection/8 
   enp19s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1574347/+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 1564156] Re: xenial: invalid opcode when using llvmpipe

[Ara Pulido]

** Changed in: oem-priority
   Status: New => Fix Committed

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

Title:
  xenial: invalid opcode when using llvmpipe

Status in OEM Priority Project:
  Fix Committed
Status in System76:
  Fix Committed
Status in Release Notes for Ubuntu:
  Fix Released
Status in llvm-toolchain-3.8 package in Ubuntu:
  Fix Committed
Status in mesa package in Ubuntu:
  New
Status in llvm-toolchain-3.8 source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  New

Bug description:
  [Description updated to reflect state of 16.04 release ISO]

  == In summary ==

  If you have an Intel Skylake (6th gen) CPU and an NVIDIA GPU (or
  possibly other GPUs that likewise require use of the llvmpipe opengl
  software fallback), a work-around is needed to install Ubuntu 16.04
  desktop.

  To work-around this, you'll need to:

  1) Choose "Install Ubuntu" in the pre-boot menu (rather than "Try
  Ubuntu without installing")

  2) Check "Download updates while installing Ubuntu"

  ** Note the above work-around wont work till 
  llvm-toolchain-3.8 1:3.8-2ubuntu3 lands in xenial-updates (it's currently 
only in xenial-proposed). FIXME: update description once this happens.

  == In detail ==

  The Ubuntu 16.04 desktop ISOs includes libllvm3.8 1:3.8-2ubuntu1,
  which has a bug that results in invalid JIT code generation when using
  the mesa llvmpipe opengl software fallback on Skylake CPUs.

  When you encounter this bug, Unity/Compiz will fail to start, and
  you'll see something like this in dmesg:

  [ 2092.557913] traps: compiz[10155] trap invalid opcode
  ip:7efc940030d4 sp:7ffccd914ea0 error:0

  libllvm3.8 1:3.8-2ubuntu3 fixes this issue, but the fix did not make
  it onto the 16.04 release ISO. It will be included on the 16.04.1 ISO.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1564156/+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 1371625] Re: wifi don't work after suspend

[Ara Pulido]

Marking as Invalid, as we don't have clear reproduceable steps

** Changed in: oem-priority
   Status: Incomplete => Invalid

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

Title:
  wifi don't work after suspend

Status in OEM Priority Project:
  Invalid
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When i take my laptop, fujitsu-siemens AMILO-Li3710,  from a suspend state 
wifi don't work.
  I need to restart it to function properly.

  This is my laptop and i have ubuntu 14.04..
  http://wiki.ubuntu-it.org/Hardware/Notebook/FujitsuSiemensAMILOLi3710

  thx

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1371625/+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 254584] Re: Activating -proposed should need a confirmation with a proper warning

[Ara Pulido]

I think that a confirmation is needed, to make sure that the people
activating it know what they are doing.

Something like:

"Proposed is intended for people willing to test updates before the
reach a wider audience. Are you sure you want to activate -proposed?"


** Summary changed:

- Too easy to activate the proposed repository
+ Activating -proposed should need a confirmation with a proper warning

** Description changed:

  The GUI is mainly intended for use by normal users. Using the proposed
  repository may cause problems and is therefore not recommended for the
  broad mayority of users. The normal user should not be able to activate
  this repository by just a single click.
  
- Please remove that possibility or at least provide a warning/information
- about the consequences.
+ We need a proper warning, explaining what -proposed is, requiring
+ confirmation by the user.
  
  : "The “When checking
  for updates, check for:” menu should contain options for “All updates”
  (the default, -security + -updates + -backports), “Security and
  recommended updates” (-security + -updates), and “Security updates only”
  (-security) (fixing bug 887079). If your current update config does not
  match one of those three options (for example, if you have opted in to
  -proposed), there should be a fourth, checked, option: “Custom”, and
  this option should persist until you close System Settings. (UI for
  configuring -proposed should be provided by the Ubuntu Contributor
  Console.)"

** Changed in: software-properties (Ubuntu)
   Importance: Low => Wishlist

** Changed in: software-properties (Ubuntu)
 Assignee: (unassigned) => Will Cooke (willcooke)

** Also affects: software-properties (Ubuntu Xenial)
   Importance: Wishlist
 Assignee: Will Cooke (willcooke)
   Status: Triaged

** Also affects: software-center (Ubuntu Xenial)
   Importance: Undecided
   Status: Invalid

** No longer affects: software-center (Ubuntu)

** No longer affects: software-center (Ubuntu Xenial)

** Description changed:

  The GUI is mainly intended for use by normal users. Using the proposed
  repository may cause problems and is therefore not recommended for the
  broad mayority of users. The normal user should not be able to activate
  this repository by just a single click.
  
  We need a proper warning, explaining what -proposed is, requiring
  confirmation by the user.
+ 
+ For example:
+ 
+ "Proposed is intended for people willing to test updates before the
+ reach a wider audience. Are you sure you want to activate -proposed?"
  
  : "The “When checking
  for updates, check for:” menu should contain options for “All updates”
  (the default, -security + -updates + -backports), “Security and
  recommended updates” (-security + -updates), and “Security updates only”
  (-security) (fixing bug 887079). If your current update config does not
  match one of those three options (for example, if you have opted in to
  -proposed), there should be a fourth, checked, option: “Custom”, and
  this option should persist until you close System Settings. (UI for
  configuring -proposed should be provided by the Ubuntu Contributor
  Console.)"

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

Title:
  Activating -proposed should need a confirmation with a proper warning

Status in software-properties package in Ubuntu:
  Triaged
Status in software-properties source package in Xenial:
  Triaged

Bug description:
  The GUI is mainly intended for use by normal users. Using the proposed
  repository may cause problems and is therefore not recommended for the
  broad mayority of users. The normal user should not be able to
  activate this repository by just a single click.

  We need a proper warning, explaining what -proposed is, requiring
  confirmation by the user.

  For example:

  "Proposed is intended for people willing to test updates before the
  reach a wider audience. Are you sure you want to activate -proposed?"

  : "The “When
  checking for updates, check for:” menu should contain options for “All
  updates” (the default, -security + -updates + -backports), “Security
  and recommended updates” (-security + -updates), and “Security updates
  only” (-security) (fixing bug 887079). If your current update config
  does not match one of those three options (for example, if you have
  opted in to -proposed), there should be a fourth, checked, option:
  “Custom”, and this option should persist until you close System
  Settings. (UI for configuring -proposed should be provided by the
  Ubuntu Contributor Console.)"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/254584/+subs

[Touch-packages] [Bug 1368063] Re: [Nexus 4] The photo captured by Camera app show darkness.

[Ara Pulido]

** No longer affects: oem-priority

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

Title:
  [Nexus 4] The photo captured by Camera app show darkness.

Status in camera-app:
  Confirmed
Status in camera-app package in Ubuntu:
  Confirmed

Bug description:
  Install Ubuntu 14.04 and boot into OS.
  Opened Camera app from dash home.Clicked the roundness button to capture 
photos.
  View the photos in /home/pictures.Found the photos show darkness.

  Steps to Reproduce:
  1.Boot into OS.
  2.Open Camera app from dash home.
  3. Activate the camera flash
  4.Click the roundness button to capture photos.
  5.View the photos in /home/pictures.
  6.Found the photos show darkness.

  Pictures are OK only if you do not activate the flash camera.

To manage notifications about this bug go to:
https://bugs.launchpad.net/camera-app/+bug/1368063/+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 1431211] Re: [desktop] camera-app preview screen twisted after maximizing the preview screen

[Ara Pulido]

** Changed in: oem-priority
   Status: Incomplete => Won't Fix

** Changed in: oem-priority/trusty
   Status: New => Won't Fix

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

Title:
  [desktop] camera-app preview screen twisted after maximizing the
  preview screen

Status in camera-app:
  Won't Fix
Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project trusty series:
  Won't Fix
Status in camera-app package in Ubuntu:
  Won't Fix

Bug description:
  The preview screen of camera-app twisted after maximizing the preview screen.
  It has failure-rate, should be reproduced in 5 times of retries.
  version: 2.9.1+14.04.20130508-0ubuntu1

  ---
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-datong150206-trusty-amd64-20150214-1
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2015-02-17 (23 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150214-07:47
  NonfreeKernelModules: wl fglrx
  Package: camera-app 2.9.1+14.04.20140508-0ubuntu1 [origin: Canonical]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Tags: third-party-packages trusty
  Uname: Linux 3.13.0-45-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/camera-app/+bug/1431211/+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 1441095] Re: novatel: improve probing for Dell branded modems

[Ara Pulido]

** Changed in: oem-priority
   Status: Fix Committed => Fix Released

** Changed in: oem-priority/trusty
   Status: Fix Committed => Fix Released

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

Title:
  novatel: improve probing for Dell branded modems

Status in Libmbim:
  Fix Released
Status in ModemManager:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project trusty series:
  Fix Released
Status in libmbim package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in libmbim source package in Trusty:
  Fix Released
Status in modemmanager source package in Trusty:
  Fix Released
Status in network-manager source package in Trusty:
  Fix Released

Bug description:
  [Impact]

   * The users can not use the WWAN of Sierra DW5809e (EM7305) or Sierra
  DW5811e (EM7455) to connect to Internet.

  [Test Case]

   * Insert the WWAN of Sierra DW5809e (EM7305) or Sierra DW5811e
  (EM7455).

   * Insert the SIM, boot the Ubuntu system, and connect to Internet by
  NetworkManager.

  [Regression Potential]

   * No trivial regression so far.

  [Other Info]

   * There is no gateway information in Network Manager. (See the picture in 
comment #74)
* Some ISPs like TW Mobile in Taiwan don't need the gateway to connect to 
Internet.
* Some ISPs like Chunghwa Telecom in Taiwan do need the gateway to connect 
to Internet.
* We need to see the gateway information in Network Manager to cover all 
ISPs.

  Dell rebrands modems from different vendors, including Novatel, Sierra
  and Ericsson. Until now we defaulted to the Novatel plugin when a Dell
  device was found, but then we're breaking newer MBIM Sierra Dell-
  branded modems, as we don't have MBIM support in the Novatel plugin.

  So, we should try to improve the probing in the Novatel, Sierra and
  MBM plugins, so that they probe also Dell devices, and we'll then try
  to match via AT-probing which plugin should be handling the Dell
  device.

  https://bugs.freedesktop.org/show_bug.cgi?id=86713

  Could we backport this patch  into trusty? Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/libmbim/+bug/1441095/+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 1441095] Re: novatel: improve probing for Dell branded modems

[Ara Pulido]

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

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

Title:
  novatel: improve probing for Dell branded modems

Status in ModemManager:
  Fix Released
Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project trusty series:
  In Progress
Status in libmbim package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in libmbim source package in Trusty:
  Fix Committed
Status in modemmanager source package in Trusty:
  In Progress
Status in network-manager source package in Trusty:
  In Progress

Bug description:
  [Impact]

   * The users can not use the WWAN of Sierra DW5809e (EM7305) or Sierra
  DW5811e (EM7455) to connect to Internet.

  [Test Case]

   * Insert the WWAN of Sierra DW5809e (EM7305) or Sierra DW5811e
  (EM7455).

   * Insert the SIM, boot the Ubuntu system, and connect to Internet by
  NetworkManager.

  [Regression Potential]

   * No trivial regression so far.

  [Other Info]
   
   * None

  Dell rebrands modems from different vendors, including Novatel, Sierra
  and Ericsson. Until now we defaulted to the Novatel plugin when a Dell
  device was found, but then we're breaking newer MBIM Sierra Dell-
  branded modems, as we don't have MBIM support in the Novatel plugin.

  So, we should try to improve the probing in the Novatel, Sierra and
  MBM plugins, so that they probe also Dell devices, and we'll then try
  to match via AT-probing which plugin should be handling the Dell
  device.

  https://bugs.freedesktop.org/show_bug.cgi?id=86713

  Could we backport this patch  into trusty? Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/modemmanager/+bug/1441095/+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 1490937] Re: Unavailable port selected by default

[Ara Pulido]

** Changed in: oem-priority/trusty
   Status: New => Won't Fix

** Changed in: oem-priority
   Importance: Critical => High

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

Title:
  Unavailable port selected by default

Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  Won't Fix
Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  In case one card has only unavailable ports, it might be still be
  selected as default, even though there are available ports on other
  cards.

  E g, on a HTPC which have only Headphone and HDMI outputs, and these
  two outputs are on separate cards, the headphone port might be
  selected even if the HDMI port is available and the headphone port is
  not.

  Probably PulseAudio's routing system needs to be rewritten to be more
  port based to fix this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1490937/+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 1412937] Re: Config option to set UNITY_LOW_GFX_MODE=1

[Ara Pulido]

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

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

Title:
  Config option to set UNITY_LOW_GFX_MODE=1

Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  New
Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  Triaged
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  New

Bug description:
  Right now the procedure to turn on low_gfx_mode is
  https://bugs.launchpad.net/compiz/+bug/1293384/comments/15

  "sudo -H gedit /usr/share/gnome-session/sessions/ubuntu.session
  Remove "compiz" from the RequiredComponents list

  sudo -H gedit /usr/share/upstart/sessions/unity7.conf:

  Add these lines after "export COMPIZ_CONFIG_PROFILE":
  env UNITY_LOW_GFX_MODE="1"
  export UNITY_LOW_GFX_MODE"

  We should add a config option (preferably system wide) to tell
  Compiz/Unity to go to the LOW_GFX mode regardless of what the hardware
  says it can do.

  This will make it easier to setup items like terminal services using
  Unity.   This procedure has helped in at least one case for me, (a
  machine used by several users remotely using Unity).  I can imagine it
  would also help in multiseat scenarios, etc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1412937/+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 1420630] Re: indicator-sound menu icon disappeared after volume down to zero

[Ara Pulido]

** Changed in: oem-priority
   Status: New => Incomplete

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

Title:
  indicator-sound menu icon disappeared after volume down to zero

Status in OEM Priority Project:
  Incomplete
Status in OEM Priority Project trusty series:
  Incomplete
Status in indicator-sound package in Ubuntu:
  Fix Released
Status in indicator-sound source package in Trusty:
  New

Bug description:
  On the HP commercial notebooks, there're function keys to control volume.
  The menu volume icon will be disappeared if we volume down
  (with key combination: Fn+F6, you can also emulate the keys with "xdotool key 
XF86AudioLowerVolume") to zero then logout and back in.
  But if we just zero down volume(with the single volume on/off button), then 
logout and back in, the volume icon is still there.

  This issue is fixed with installing indicator-
  sound_12.10.2+14.10.20141010-0ubuntu1(Utopic)

  Package: indicator-sound_12.10.2+14.04.20140401-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-38.65stella1-generic 3.13.11.8
  Uname: Linux 3.13.0-38-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Wed Feb 11 14:18:50 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-datong140729-trusty-amd64-20150114-3
  InstallationDate: Installed on 2015-01-29 (13 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150114-08:50
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1420630/+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 1420630] Re: indicator-sound menu icon disappeared after volume down to zero

[Ara Pulido]

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

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

Title:
  indicator-sound menu icon disappeared after volume down to zero

Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  Incomplete
Status in indicator-sound package in Ubuntu:
  Fix Released
Status in indicator-sound source package in Trusty:
  New

Bug description:
  On the HP commercial notebooks, there're function keys to control volume.
  The menu volume icon will be disappeared if we volume down
  (with key combination: Fn+F6, you can also emulate the keys with "xdotool key 
XF86AudioLowerVolume") to zero then logout and back in.
  But if we just zero down volume(with the single volume on/off button), then 
logout and back in, the volume icon is still there.

  This issue is fixed with installing indicator-
  sound_12.10.2+14.10.20141010-0ubuntu1(Utopic)

  Package: indicator-sound_12.10.2+14.04.20140401-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-38.65stella1-generic 3.13.11.8
  Uname: Linux 3.13.0-38-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Wed Feb 11 14:18:50 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-datong140729-trusty-amd64-20150114-3
  InstallationDate: Installed on 2015-01-29 (13 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150114-08:50
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1420630/+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 1438587] Re: connect button is grey when connecting to Ad-hoc SSID

[Ara Pulido]

** Changed in: oem-priority
   Status: New => Incomplete

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

Title:
  connect button is grey when connecting to Ad-hoc SSID

Status in NetworkManager:
  New
Status in OEM Priority Project:
  Incomplete
Status in OEM Priority Project trusty series:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  First, I created an adhoc network through nm-applet->create new wifi
  network.

  Network Name: 111
  wi-fi security: WEP 128-bit Passphrase
  key: 222

  Then click create button and wait for its ready.

  using another machine to connect to this "111", enter password 222 and
  you can find that the connect button is grey, you can not click it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1438587/+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 1441095] Re: novatel: improve probing for Dell branded modems

[Ara Pulido]

We need some testing results on both Wily and Trusty.

Thanks,
Ara.

** Changed in: oem-priority
   Importance: Undecided => High

** Changed in: oem-priority
   Status: New => Incomplete

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

Title:
  novatel: improve probing for Dell branded modems

Status in ModemManager:
  New
Status in OEM Priority Project:
  Incomplete
Status in OEM Priority Project trusty series:
  New
Status in modemmanager package in Ubuntu:
  New
Status in modemmanager source package in Trusty:
  New

Bug description:
  Dell rebrands modems from different vendors, including Novatel, Sierra
  and Ericsson. Until now we defaulted to the Novatel plugin when a Dell
  device was found, but then we're breaking newer MBIM Sierra Dell-
  branded modems, as we don't have MBIM support in the Novatel plugin.

  So, we should try to improve the probing in the Novatel, Sierra and
  MBM plugins, so that they probe also Dell devices, and we'll then try
  to match via AT-probing which plugin should be handling the Dell
  device.

  
  https://bugs.freedesktop.org/show_bug.cgi?id=86713

  Could we backport this patch  into trusty? Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/modemmanager/+bug/1441095/+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 1310518] Re: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen

[Ara Pulido]

Tim, is this still happening? I cannot reproduce it in Trusty

** Changed in: oem-priority
   Status: Triaged => Incomplete

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

Title:
  Touch screen and touchpad lost click function after quickly tapped
  dash home repeatly by touch screen

Status in OEM Priority Project:
  Incomplete
Status in OEM Priority Project precise series:
  Won't Fix
Status in OEM Priority Project trusty series:
  New
Status in Unity:
  Triaged
Status in Unity 7.2 series:
  Triaged
Status in unity package in Ubuntu:
  Triaged

Bug description:

  Touch screen and touchpad lost click function after quickly tapped
  dash home repeatly by touch screen, Installed 14.04, still have same
  issue.

  Quickly tapped dash home more than three times by touch screen.Found
  touch screen and touchpad lost click function.

  Note:
  1.When this issue occured, cursor still can be moved by touch screen/touchpad.
  2.When this issue occured ,click/double click by touch screen/touchpad,left 
click/right click by touchpad all were not workable.

  Steps to Reproduce:
  1.install 12.04.4 image or 14.04 image, boot into Ubuntu OS.
  2.Quickly tapped dash home more than three times by touch screen.
  3.Found touch screen and touchpad lost click function.

  This bug is reported from private OEM project, also check
  https://launchpad.net/bugs/1297067

  ==

  using xinput --query-state can actually see the button press event

  ⎡ Virtual core pointer id=2   [master pointer (3)]
  ⎜ ↳ Virtual core XTEST pointer id=4   [slave pointer (2)]
  ⎜ ↳ syntp id=6[slave pointer (2)]
  ⎜ ↳ ELAN Touchscreen id=11[slave pointer (2)]

  #xinput --query-state 11
  2 classes :
  ButtonClass
   button[1]=up
   button[2]=up
   button[3]=up
   button[4]=up
   button[5]=up
  ValuatorClass Mode=Absolute Proximity=In
   valuator[0]=398
   valuator[1]=1652
   valuator[2]=5
   valuator[3]=3
   valuator[4]=0
   valuator[5]=399
   valuator[6]=1653

  #xinput --query-state 6
  2 classes :
  ButtonClass
   button[1]=down
   button[2]=up
   button[3]=up
   button[4]=up
   button[5]=up
   button[6]=up
   button[7]=up
   button[8]=up
  ValuatorClass Mode=Relative Proximity=In
   valuator[0]=1
   valuator[1]=394

  touchpad's button and touchpanel's
  valuator[2] and valuator[3] will changed after we press the button (or 
monitor)

  Also I found press "super" on keyboard will recover the
  touchscreen/touchpad loss.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.20.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  CompizPlugins: 
[core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Mon Apr 21 16:50:04 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-daan2-precise-amd64-20140416-1
  InstallationMedia: Ubuntu 12.04 "Precise" - Failed to find casper uuid.conf 
in 'binary/casper/initrd.img-3.11.0-18-generic.old-dkms' LIVE Binary 
20140416-06:52
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1310518/+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 1441095] Re: novatel: improve probing for Dell branded modems

[Ara Pulido]

** Changed in: oem-priority
   Status: New => Incomplete

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

Title:
  novatel: improve probing for Dell branded modems

Status in ModemManager:
  New
Status in OEM Priority Project:
  Incomplete
Status in OEM Priority Project trusty series:
  New
Status in modemmanager package in Ubuntu:
  New
Status in modemmanager source package in Trusty:
  New

Bug description:
  Dell rebrands modems from different vendors, including Novatel, Sierra
  and Ericsson. Until now we defaulted to the Novatel plugin when a Dell
  device was found, but then we're breaking newer MBIM Sierra Dell-
  branded modems, as we don't have MBIM support in the Novatel plugin.

  So, we should try to improve the probing in the Novatel, Sierra and
  MBM plugins, so that they probe also Dell devices, and we'll then try
  to match via AT-probing which plugin should be handling the Dell
  device.

  
  https://bugs.freedesktop.org/show_bug.cgi?id=86713

  Could we backport this patch  into trusty? Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/modemmanager/+bug/1441095/+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 1431211] Re: [desktop] camera-app preview screen twisted after maximizing the preview screen

[Ara Pulido]

** Changed in: oem-priority
   Status: New => Incomplete

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

Title:
  [desktop] camera-app preview screen twisted after maximizing the
  preview screen

Status in camera-app:
  Incomplete
Status in OEM Priority Project:
  Incomplete
Status in OEM Priority Project trusty series:
  New
Status in camera-app package in Ubuntu:
  Incomplete

Bug description:
  The preview screen of camera-app twisted after maximizing the preview screen.
  It has failure-rate, should be reproduced in 5 times of retries.
  version: 2.9.1+14.04.20130508-0ubuntu1

  ---
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-datong150206-trusty-amd64-20150214-1
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2015-02-17 (23 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150214-07:47
  NonfreeKernelModules: wl fglrx
  Package: camera-app 2.9.1+14.04.20140508-0ubuntu1 [origin: Canonical]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Tags: third-party-packages trusty
  Uname: Linux 3.13.0-45-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/camera-app/+bug/1431211/+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 1066157] Re: dash +orca does not speak the names of application icons

[Ara Pulido]

** Changed in: oem-priority
   Status: New => Fix 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/1066157

Title:
  dash +orca does not speak the names of application icons

Status in OEM Priority Project:
  Fix Released
Status in Unity:
  Fix Released
Status in Unity 5.0 series:
  New
Status in Unity 6.0 series:
  Won't Fix
Status in Unity 7.2 series:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Released

Bug description:
  [Impact]
  Screen reader support for dynamic content in the Dash is enabled.

  [Test Case]

  (1) Enable Screen Reader (System Settings > Universal Access > Screen Reader)
  (2) Press Super + A to bring up the Applications lens of the Dash
  (3) Navigate displayed content
  (4) Choose an application for preview
  (5) Press Esc until the Dash is closed, repeat steps 2 to 4

  You should hear the application description and preview description.

  [Regression Potential]

  Some new code deals with processing pointers:  the usual problem
  potential of dealing with pointers in C code applies.

  [Other Info]

  This patch for Ubuntu 14.04 LTS was cherry picked from the Ubuntu
  "Vivid Vervet" dev release where it has been in public use for some
  time without apparent regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1066157/+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 1310518] Re: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen

[Ara Pulido]

** Changed in: oem-priority/precise
   Status: New => Won't Fix

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

Title:
  Touch screen and touchpad lost click function after quickly tapped
  dash home repeatly by touch screen

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project precise series:
  Won't Fix
Status in OEM Priority Project trusty series:
  New
Status in Unity:
  Triaged
Status in Unity 7.2 series:
  Triaged
Status in unity package in Ubuntu:
  Triaged

Bug description:

  Touch screen and touchpad lost click function after quickly tapped
  dash home repeatly by touch screen, Installed 14.04, still have same
  issue.

  Quickly tapped dash home more than three times by touch screen.Found
  touch screen and touchpad lost click function.

  Note:
  1.When this issue occured, cursor still can be moved by touch screen/touchpad.
  2.When this issue occured ,click/double click by touch screen/touchpad,left 
click/right click by touchpad all were not workable.

  Steps to Reproduce:
  1.install 12.04.4 image or 14.04 image, boot into Ubuntu OS.
  2.Quickly tapped dash home more than three times by touch screen.
  3.Found touch screen and touchpad lost click function.

  This bug is reported from private OEM project, also check
  https://launchpad.net/bugs/1297067

  ==

  using xinput --query-state can actually see the button press event

  ⎡ Virtual core pointer id=2   [master pointer (3)]
  ⎜ ↳ Virtual core XTEST pointer id=4   [slave pointer (2)]
  ⎜ ↳ syntp id=6[slave pointer (2)]
  ⎜ ↳ ELAN Touchscreen id=11[slave pointer (2)]

  #xinput --query-state 11
  2 classes :
  ButtonClass
   button[1]=up
   button[2]=up
   button[3]=up
   button[4]=up
   button[5]=up
  ValuatorClass Mode=Absolute Proximity=In
   valuator[0]=398
   valuator[1]=1652
   valuator[2]=5
   valuator[3]=3
   valuator[4]=0
   valuator[5]=399
   valuator[6]=1653

  #xinput --query-state 6
  2 classes :
  ButtonClass
   button[1]=down
   button[2]=up
   button[3]=up
   button[4]=up
   button[5]=up
   button[6]=up
   button[7]=up
   button[8]=up
  ValuatorClass Mode=Relative Proximity=In
   valuator[0]=1
   valuator[1]=394

  touchpad's button and touchpanel's
  valuator[2] and valuator[3] will changed after we press the button (or 
monitor)

  Also I found press "super" on keyboard will recover the
  touchscreen/touchpad loss.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.20.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  CompizPlugins: 
[core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Mon Apr 21 16:50:04 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-daan2-precise-amd64-20140416-1
  InstallationMedia: Ubuntu 12.04 "Precise" - Failed to find casper uuid.conf 
in 'binary/casper/initrd.img-3.11.0-18-generic.old-dkms' LIVE Binary 
20140416-06:52
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1310518/+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 1441095] Re: novatel: improve probing for Dell branded modems

[Ara Pulido]

** Also affects: modemmanager (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

Title:
  novatel: improve probing for Dell branded modems

Status in ModemManager (with NetworkManager support):
  New
Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  New
Status in modemmanager package in Ubuntu:
  New
Status in modemmanager source package in Trusty:
  New

Bug description:
  Dell rebrands modems from different vendors, including Novatel, Sierra
  and Ericsson. Until now we defaulted to the Novatel plugin when a Dell
  device was found, but then we're breaking newer MBIM Sierra Dell-
  branded modems, as we don't have MBIM support in the Novatel plugin.

  So, we should try to improve the probing in the Novatel, Sierra and
  MBM plugins, so that they probe also Dell devices, and we'll then try
  to match via AT-probing which plugin should be handling the Dell
  device.

  
  https://bugs.freedesktop.org/show_bug.cgi?id=86713

  Could we backport this patch  into trusty? Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/modemmanager/+bug/1441095/+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 1431128] Re: screen remains blank after waking up from suspend

[Ara Pulido]

** No longer affects: oem-priority/trusty

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

Title:
  screen remains blank after waking up from suspend

Status in lightdm package in Ubuntu:
  New
Status in lightdm source package in Trusty:
  New

Bug description:
  Steps:
  1. Suspend the computer by pressing the Sleep key(Fn+F2 on the keyboard here)
  2. Press any key on the keyboard or the Power button to wake the device up

  Expected results:
  1. The system suspends and the Power button LED blinks
  2. The system wakes up and user can log in.

  Actual results:
  1. The system suspends and the Power button LED blinks (OK)
  2. The login screen appears and the screen is immediately turned off (NOK). 
User needs to move the mouse or enter a key to turn the screen on.

  Additional information:

  - In a few additional occasions, after performing this action several
  times (pressing the Sleep key to suspend the system, then wake it up),
  the system freezes at log in screen just before going to suspend mode.
  It has to be force-stopped and restarted.

  - Please note that this problem does NOT happen when suspending from
  the User Menu or using the Power button and selecting Suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.4-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  Date: Thu Mar 12 11:19:32 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-datong140729-kylin-trusty-amd64-20150205-2
  InstallationDate: Installed on 2015-02-10 (29 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150205-07:08
  LightdmConfig:
   [SeatDefaults]
   autologin-guest=false
   autologin-user-timeout=0
   autologin-session=lightdm-autologin
   #autologin-user=u
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1431128/+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 1420630] Re: indicator-sound menu icon disappeared after volume down to zero

[Ara Pulido]

I cannot reproduce this on stock Ubuntu

Have you tried reproducing this on stock Ubuntu?

** Changed in: oem-priority/trusty
   Status: New => Incomplete

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

Title:
  indicator-sound menu icon disappeared after volume down to zero

Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  Incomplete
Status in indicator-sound package in Ubuntu:
  Triaged
Status in indicator-sound source package in Trusty:
  New

Bug description:
  On the HP commercial notebooks, there're function keys to control volume.
  The menu volume icon will be disappeared if we volume down
  (with key combination: Fn+F6, you can also emulate the keys with "xdotool key 
XF86AudioLowerVolume") to zero then logout and back in.
  But if we just zero down volume(with the single volume on/off button), then 
logout and back in, the volume icon is still there.

  This issue is fixed with installing indicator-
  sound_12.10.2+14.10.20141010-0ubuntu1(Utopic)

  Package: indicator-sound_12.10.2+14.04.20140401-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-38.65stella1-generic 3.13.11.8
  Uname: Linux 3.13.0-38-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Wed Feb 11 14:18:50 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-datong140729-trusty-amd64-20150114-3
  InstallationDate: Installed on 2015-01-29 (13 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150114-08:50
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1420630/+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 1434447] Re: apport reports are not complete for filing bugs against linux-lts-utopic kernel

[Ara Pulido]

** Also affects: apport (Ubuntu Utopic)
   Importance: Undecided
   Status: New

** Also affects: apport (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

Title:
  apport reports are not complete for filing bugs against linux-lts-
  utopic kernel

Status in apport package in Ubuntu:
  New
Status in apport source package in Trusty:
  New
Status in apport source package in Utopic:
  New

Bug description:
  When filing a bug with ubuntu-bug linux command on 14.04.2, it won't collect 
extra reports for attachment.
  Only Dependencies.txt and ProcEnviron.txt will be attached to the report. 
(See bug 1434442)

  
  Similar bugs: bug 1352829, bug 1229611

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apport 2.14.1-0ubuntu3.7
  ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 20 04:36:34 2015
  InstallationDate: Installed on 2015-03-20 (0 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1434447/+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 1405349] Re: switching to activated guest session causes screen blank

[Ara Pulido]

** Also affects: lightdm (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

Title:
  switching to activated guest session causes screen blank

Status in Light Display Manager:
  Confirmed
Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project trusty series:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed
Status in lightdm source package in Trusty:
  New

Bug description:
  Hi,
  I switch to activated guest session, but the screen remains blank. I have to 
wake it up with keyboard/mouse action.

  How to reproduce:
  1. login with your account normally.
  2. switch to guest session from the panel menu "Switch Account... -> Guest 
Session", now it's under guest session and the display is normal.
  3. switch back to your user account, then switch to guest session again.
  4. The screen remains blank.

  P.S: I can't reproduce this issue under Precise.

  Package:
  lightdm 1.10.3-0ubuntu2
  unity-settings-daemon-14.04.0+14.10.20140606~0ubuntu1
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-datong140729-kylin-trusty-amd64-20150205-2
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2015-02-09 (1 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150205-07:08
  LightdmConfig:
   [SeatDefaults]
   autologin-guest=false
   autologin-user-timeout=0
   autologin-session=lightdm-autologin
  Package: lightdm 1.10.3-0ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-38.65stella1-generic 3.13.11.8
  Tags: trusty third-party-packages
  Uname: Linux 3.13.0-38-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1405349/+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 1431128] Re: screen remains blank after waking up from suspend

[Ara Pulido]

** Also affects: lightdm (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

Title:
  screen remains blank after waking up from suspend

Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  New
Status in lightdm package in Ubuntu:
  New
Status in lightdm source package in Trusty:
  New

Bug description:
  Steps:
  1. Suspend the computer by pressing the Sleep key(Fn+F2 on the keyboard here)
  2. Press any key on the keyboard or the Power button to wake the device up

  Expected results:
  1. The system suspends and the Power button LED blinks
  2. The system wakes up and user can log in.

  Actual results:
  1. The system suspends and the Power button LED blinks (OK)
  2. The login screen appears and the screen is immediately turned off (NOK). 
User needs to move the mouse or enter a key to turn the screen on.

  Additional information:

  - In a few additional occasions, after performing this action several
  times (pressing the Sleep key to suspend the system, then wake it up),
  the system freezes at log in screen just before going to suspend mode.
  It has to be force-stopped and restarted.

  - Please note that this problem does NOT happen when suspending from
  the User Menu or using the Power button and selecting Suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.4-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  Date: Thu Mar 12 11:19:32 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-datong140729-kylin-trusty-amd64-20150205-2
  InstallationDate: Installed on 2015-02-10 (29 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150205-07:08
  LightdmConfig:
   [SeatDefaults]
   autologin-guest=false
   autologin-user-timeout=0
   autologin-session=lightdm-autologin
   #autologin-user=u
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1431128/+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 1424466] Re: Devel package not installable in 14.04.2 (mesa-lts-utopic

[Ara Pulido]

** Also affects: mesa (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

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

Title:
  Devel package not installable in 14.04.2 (mesa-lts-utopic

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Trusty:
  Fix Committed

Bug description:
  [Impact] 
   * Some -dev packages like ubuntu-sdk and libglew-dev cannot be installed 
when the lts-utopic stack is used.

  [Test Case]
   * Install the lts-utopic stack.
   * apt-get install ubuntu-sdk
   * Good: you get a whole list of packages to install.
   * Bad: apt-get install fails like pasted in the original bug report.
   * Also test the same without the lts-utopic stack, to make sure there are no 
regressions.

  [Regression Potential] 
   * Low, this has been done for precise before, and mesa packaging has to be 
updated for every LTS release. Unfortunately there are no alternatives. :(

  [Other Info]
   * There's probably an apt bug in here too. Nudging the resolver by 
specifying libgl1-mesa-dev-lts-utopic and libgles2-mesa-dev-lts-utopic works, 
but I didn't find a good way to express this in the depends, and that would 
have to be done for every package.

  [Original bug report]
  Not the first, likely not the last devel to not be installable in 14.04.2 or 
any mesa-lts-utopic install
  Another one is libglew-dev

   sudo apt-get install freeglut3-dev
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (>= 0.91.8) but it is not 
going to be installed
     Depends: libcogl15 (>= 1.15.8) but it is not going to be 
installed
   libcheese7 : Depends: libclutter-gst-2.0-0 (>= 0.10.0) but it is not going 
to be installed
    Depends: gstreamer1.0-clutter but it is not going to be 
installed
   libclutter-1.0-0 : Depends: libcogl-pango15 (>= 1.15.8) but it is not going 
to be installed
  Depends: libcogl15 (>= 1.15.8) but it is not going to be 
installed

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: freeglut3-dev (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb 22 18:03:30 2015
  InstallationDate: Installed on 2015-02-08 (14 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150203.2)
  SourcePackage: freeglut
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1424466/+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 1318584] Re: qt crashed when switching video out mode to external or internal only mode

[Ara Pulido]

** Changed in: oem-priority
   Status: Confirmed => Won't Fix

** Changed in: oem-priority/trusty
   Status: New => Won't Fix

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

Title:
  qt crashed when switching video out mode to external or internal only
  mode

Status in Checkbox - Graphical Test Runner:
  Confirmed
Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project trusty series:
  Won't Fix
Status in Qt:
  New
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  checkbox-gui crashed with following console outputs:

  pure virtual method called
  terminate called without an active exception
  Aborted (core dumped)

  Steps to reproduce:

  1. open checkbox-gui

  2. connected external display

  3. switch video output mode, usually by using the common video output
  switch hotkey.

  Expected result:

  checkbox-gui still running when switching back to extended desktop
  video out mode.

  Actual result:

  checkbox-gui crashed

  ---
  https://bugreports.qt-project.org/browse/QTBUG-39663

To manage notifications about this bug go to:
https://bugs.launchpad.net/checkbox-gui/+bug/1318584/+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 1332947] Re: HDPI: unity randomly turns on large text in universal access

[Ara Pulido]

** Changed in: unity/7.2
   Status: Fix Committed => Fix Released

** Changed in: oem-priority
   Status: In Progress => Fix Released

** Changed in: oem-priority/trusty
   Status: New => Fix 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/1332947

Title:
  HDPI: unity randomly turns on large text in universal access

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project trusty series:
  Fix Released
Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Released

Bug description:
  [ Impact ]

  Using a display scaling factor of > 1.0 the 'large text' setting is
  sometimes enabled automatically on session start, doubling the scaling
  factor.

  [ Test Case ]

  (1) Using the System Settings > Displays > Scale for menu and title bars 
slider, set the scaling to a value > 1 (for example, 1.88).
  (2) Log out and in several times.

  Since this problem occurs as a result of a race condition somewhere,
  it is not reliably reproducable.

  [ Regression Potential ]

  Any code change to the Unity desktop shell could introduce a new crash
  or lockup.

  [ Other Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu
  14.10 where it has been in production use for some time without
  demonstrating regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1332947/+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 1035431] Re: bluetooth-wizard failed to connect to a keyboard(logitech)

[Ara Pulido]

** Changed in: oem-priority
   Status: In Progress => Fix Released

** Changed in: oem-priority/trusty
   Status: New => Fix Released

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

Title:
  bluetooth-wizard failed to connect to a keyboard(logitech)

Status in GNOME Bluetooth:
  New
Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project trusty series:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released
Status in gnome-bluetooth package in Ubuntu:
  Fix Released
Status in bluez source package in Precise:
  Triaged
Status in gnome-bluetooth source package in Precise:
  Triaged
Status in bluez source package in Trusty:
  Fix Released
Status in gnome-bluetooth source package in Trusty:
  Fix Released

Bug description:
  [Impact]

   * Fixes issues connecting bluetooth devices using SSP (Simple Secure
  Pairing); which does include many newer bluetooth devices, especially
  keyboards.

  [Test Case]

   * Try to connect a bluetooth keyboard using the wizard; especially
  one of the following models:

  Logitech Bluetooth Keyboard K760
  Logitech Bluetooth Keyboard K810
  HP Bluetooth Keyboard K4000

  [Regression Potential]

   * It must be ensured that keyboards that could already be paired
  successfully still work properly; specifically, especially for
  keyboards but for any other devices, that pairing still works despite
  changes to the SSP code.

  [Other Info]

  
  ---

  When I try to connect my bluetooth keyboard using bluetooth-wizard, it
  ever fails:

  ** (bluetooth-wizard:11367): WARNING **: Setting up 'Logitech K760'
  failed: Authentication Failed

  This keyboard works fine with another computer under ubuntu 11.04.
  This keyboard works fine with this computer and Windows 7 (arghhh).
  This computer ubuntu 12.04 works fine with my bluetooth mouse.

  I can attach manually this keyboard to this computer using :

  sudo hidd --search

  My computer is a Samsung 305U1A
  My bluetooth interface is :

  Bus 003 Device 002: ID 0a5c:219c Broadcom Corp.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1035431/+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 1319698] Re: Gallery app shows pictures abnormally if target directory or file name contained Chinese text .

[Ara Pulido]

** Changed in: oem-priority
   Status: New => Fix Released

** Changed in: oem-priority/trusty
   Status: New => Fix Released

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

Title:
  Gallery app shows pictures abnormally if target directory or file name
  contained Chinese text .

Status in Gallery App:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project trusty series:
  Fix Released
Status in Thumbnail generator for all kinds of files:
  Fix Released
Status in thumbnailer package in Ubuntu:
  Fix Released
Status in thumbnailer source package in Trusty:
  Fix Released

Bug description:
  Steps:
  1. Copy some pictures to ~/Pictures
  2. Launch Gallery app by entering "gallery" in Dash
  3. Observe what the Gallery shows.

  Actual results:
  There are some transparent frames in Gallery.

  Expected results:
  Gallery app should show pictures included in ~/Pictures directory in step 2.

  Platform:
  Lenovo S440s

  Note:
  Once Gallery's target directory or file name of the target directory contains 
Chinese text, the issue will be reproduced. Adverse, if Gallery's target 
directory or file name of the target directory in English, Gallery displays 
normally.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gallery-app/+bug/1319698/+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 1414706] Re: [20ALCTO1WW, Realtek ALC292, Black Mic, Left][Lenovo ThinkPad X240] external mic has no sound at all

[Ara Pulido]

** Changed in: hwe-next
   Status: Incomplete => Confirmed

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

Title:
  [20ALCTO1WW, Realtek ALC292, Black Mic, Left][Lenovo ThinkPad X240]
  external mic has no sound at all

Status in HWE Next Project:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  During this test, an error dialog was thrown, reading:

  The following mixer control(s) might be incorrectly set: 
  Mic is at 0.0%

  Mic is muted
  Please try to fix that (e g by running 
  "alsamixer -D hw:PCH" in a terminal) and see if that solves the problem.
  Would you like to continue troubleshooting anyway?

  However, the System Settings... -> Sound UI shows the mic as not
  muted. When I tried running the alsamixer command, I saw mic and mic-
  boost were both showing 0; I cranked them up to 100, but it made no
  difference. I also tried re-running this command with the mic/mic-
  boost still set to 100 and it threw the same error.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doctorow   2636 F pulseaudio
   /dev/snd/pcmC1D0c:   doctorow   2636 F...m pulseaudio
   /dev/snd/pcmC1D0p:   doctorow   2636 F...m pulseaudio
   /dev/snd/controlC0:  doctorow   2636 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jan 26 16:20:49 2015
  InstallationDate: Installed on 2014-09-10 (138 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 0 3 1 
:   r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doctorow   2636 F pulseaudio
   /dev/snd/pcmC1D0c:   doctorow   2636 F...m pulseaudio
   /dev/snd/pcmC1D0p:   doctorow   2636 F...m pulseaudio
   /dev/snd/controlC0:  doctorow   2636 F pulseaudio
  Symptom_Jack: Black Mic, Left
  Symptom_Type: No sound at all
  Title: [20ALCTO1WW, Realtek ALC292, Black Mic, Left] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/24/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GIET75WW (2.25 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ALCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGIET75WW(2.25):bd06/24/2014:svnLENOVO:pn20ALCTO1WW:pvrThinkPadX240:rvnLENOVO:rn20ALCTO1WW:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20ALCTO1WW
  dmi.product.version: ThinkPad X240
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2015-01-22T13:36:22.741441

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1414706/+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 1414706] Re: [20ALCTO1WW, Realtek ALC292, Black Mic, Left][Lenovo ThinkPad X240] external mic has no sound at all

[Ara Pulido]

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  [20ALCTO1WW, Realtek ALC292, Black Mic, Left][Lenovo ThinkPad X240]
  external mic has no sound at all

Status in HWE Next Project:
  Incomplete
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  During this test, an error dialog was thrown, reading:

  The following mixer control(s) might be incorrectly set: 
  Mic is at 0.0%

  Mic is muted
  Please try to fix that (e g by running 
  "alsamixer -D hw:PCH" in a terminal) and see if that solves the problem.
  Would you like to continue troubleshooting anyway?

  However, the System Settings... -> Sound UI shows the mic as not
  muted. When I tried running the alsamixer command, I saw mic and mic-
  boost were both showing 0; I cranked them up to 100, but it made no
  difference. I also tried re-running this command with the mic/mic-
  boost still set to 100 and it threw the same error.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doctorow   2636 F pulseaudio
   /dev/snd/pcmC1D0c:   doctorow   2636 F...m pulseaudio
   /dev/snd/pcmC1D0p:   doctorow   2636 F...m pulseaudio
   /dev/snd/controlC0:  doctorow   2636 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jan 26 16:20:49 2015
  InstallationDate: Installed on 2014-09-10 (138 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 0 3 1 
:   r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doctorow   2636 F pulseaudio
   /dev/snd/pcmC1D0c:   doctorow   2636 F...m pulseaudio
   /dev/snd/pcmC1D0p:   doctorow   2636 F...m pulseaudio
   /dev/snd/controlC0:  doctorow   2636 F pulseaudio
  Symptom_Jack: Black Mic, Left
  Symptom_Type: No sound at all
  Title: [20ALCTO1WW, Realtek ALC292, Black Mic, Left] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/24/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GIET75WW (2.25 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ALCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGIET75WW(2.25):bd06/24/2014:svnLENOVO:pn20ALCTO1WW:pvrThinkPadX240:rvnLENOVO:rn20ALCTO1WW:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20ALCTO1WW
  dmi.product.version: ThinkPad X240
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2015-01-22T13:36:22.741441

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1414706/+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 1319698] Re: Gallery app shows pictures abnormally if target directory or file name contained Chinese text .

[Ara Pulido]

** Also affects: thumbnailer (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: thumbnailer (Ubuntu Trusty)
 Assignee: (unassigned) => Jussi Pakkanen (jpakkane)

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

Title:
  Gallery app shows pictures abnormally if target directory or file name
  contained Chinese text .

Status in Gallery App:
  Fix Released
Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  New
Status in Thumbnail generator for all kinds of files:
  Fix Released
Status in thumbnailer package in Ubuntu:
  Fix Released
Status in thumbnailer source package in Trusty:
  New

Bug description:
  Steps:
  1. Copy some pictures to ~/Pictures
  2. Launch Gallery app by entering "gallery" in Dash
  3. Observe what the Gallery shows.

  Actual results:
  There are some transparent frames in Gallery.

  Expected results:
  Gallery app should show pictures included in ~/Pictures directory in step 2.

  Platform:
  Lenovo S440s

  Note:
  Once Gallery's target directory or file name of the target directory contains 
Chinese text, the issue will be reproduced. Adverse, if Gallery's target 
directory or file name of the target directory in English, Gallery displays 
normally.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gallery-app/+bug/1319698/+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 1414706] Re: [20ALCTO1WW, Realtek ALC292, Black Mic, Left][Lenovo ThinkPad X240] external mic has no sound at all

[Ara Pulido]

** Changed in: hwe-next
   Status: Incomplete => Confirmed

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

Title:
  [20ALCTO1WW, Realtek ALC292, Black Mic, Left][Lenovo ThinkPad X240]
  external mic has no sound at all

Status in HWE Next Project:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  During this test, an error dialog was thrown, reading:

  The following mixer control(s) might be incorrectly set: 
  Mic is at 0.0%

  Mic is muted
  Please try to fix that (e g by running 
  "alsamixer -D hw:PCH" in a terminal) and see if that solves the problem.
  Would you like to continue troubleshooting anyway?

  However, the System Settings... -> Sound UI shows the mic as not
  muted. When I tried running the alsamixer command, I saw mic and mic-
  boost were both showing 0; I cranked them up to 100, but it made no
  difference. I also tried re-running this command with the mic/mic-
  boost still set to 100 and it threw the same error.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doctorow   2636 F pulseaudio
   /dev/snd/pcmC1D0c:   doctorow   2636 F...m pulseaudio
   /dev/snd/pcmC1D0p:   doctorow   2636 F...m pulseaudio
   /dev/snd/controlC0:  doctorow   2636 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jan 26 16:20:49 2015
  InstallationDate: Installed on 2014-09-10 (138 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 0 3 1 
:   r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doctorow   2636 F pulseaudio
   /dev/snd/pcmC1D0c:   doctorow   2636 F...m pulseaudio
   /dev/snd/pcmC1D0p:   doctorow   2636 F...m pulseaudio
   /dev/snd/controlC0:  doctorow   2636 F pulseaudio
  Symptom_Jack: Black Mic, Left
  Symptom_Type: No sound at all
  Title: [20ALCTO1WW, Realtek ALC292, Black Mic, Left] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/24/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GIET75WW (2.25 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ALCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGIET75WW(2.25):bd06/24/2014:svnLENOVO:pn20ALCTO1WW:pvrThinkPadX240:rvnLENOVO:rn20ALCTO1WW:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20ALCTO1WW
  dmi.product.version: ThinkPad X240
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2015-01-22T13:36:22.741441

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1414706/+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 1414706] Re: [20ALCTO1WW, Realtek ALC292, Black Mic, Left][Lenovo ThinkPad X240] external mic has no sound at all

[Ara Pulido]

** Changed in: alsa-driver (Ubuntu)
   Importance: Undecided => High

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

Title:
  [20ALCTO1WW, Realtek ALC292, Black Mic, Left][Lenovo ThinkPad X240]
  external mic has no sound at all

Status in HWE Next Project:
  New
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  During this test, an error dialog was thrown, reading:

  The following mixer control(s) might be incorrectly set: 
  Mic is at 0.0%

  Mic is muted
  Please try to fix that (e g by running 
  "alsamixer -D hw:PCH" in a terminal) and see if that solves the problem.
  Would you like to continue troubleshooting anyway?

  However, the System Settings... -> Sound UI shows the mic as not
  muted. When I tried running the alsamixer command, I saw mic and mic-
  boost were both showing 0; I cranked them up to 100, but it made no
  difference. I also tried re-running this command with the mic/mic-
  boost still set to 100 and it threw the same error.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doctorow   2636 F pulseaudio
   /dev/snd/pcmC1D0c:   doctorow   2636 F...m pulseaudio
   /dev/snd/pcmC1D0p:   doctorow   2636 F...m pulseaudio
   /dev/snd/controlC0:  doctorow   2636 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jan 26 16:20:49 2015
  InstallationDate: Installed on 2014-09-10 (138 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 0 3 1 
:   r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doctorow   2636 F pulseaudio
   /dev/snd/pcmC1D0c:   doctorow   2636 F...m pulseaudio
   /dev/snd/pcmC1D0p:   doctorow   2636 F...m pulseaudio
   /dev/snd/controlC0:  doctorow   2636 F pulseaudio
  Symptom_Jack: Black Mic, Left
  Symptom_Type: No sound at all
  Title: [20ALCTO1WW, Realtek ALC292, Black Mic, Left] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/24/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GIET75WW (2.25 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ALCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGIET75WW(2.25):bd06/24/2014:svnLENOVO:pn20ALCTO1WW:pvrThinkPadX240:rvnLENOVO:rn20ALCTO1WW:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20ALCTO1WW
  dmi.product.version: ThinkPad X240
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2015-01-22T13:36:22.741441

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1414706/+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 1405349] Re: switching to activated guest session causes screen blank

[Ara Pulido]

TienFu, can you run "apport-collect 1405349"?

** Also affects: lightdm (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: oem-priority
   Status: New => Incomplete

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

Title:
  switching to activated guest session causes screen blank

Status in Light Display Manager:
  New
Status in OEM Priority Project:
  Incomplete
Status in OEM Priority Project trusty series:
  New
Status in lightdm package in Ubuntu:
  New

Bug description:
  Hi,
  I switch to activated guest session, but the screen remains blank. I have to 
wake it up with keyboard/mouse action.

  How to reproduce:
  1. login with your account normally.
  2. switch to guest session from the panel menu "Switch Account... -> Guest 
Session", now it's under guest session and the display is normal.
  3. switch back to your user account, then switch to guest session again.
  4. The screen remains blank.

  P.S: I can't reproduce this issue under Precise.

  
  Package:
  lightdm 1.10.1-0ubuntu1
  unity-settings-daemon-14.04.0+14.10.20140606~0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1405349/+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 1066157] Re: dash +orca does not speak the names of application icons

[Ara Pulido]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

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

Title:
  dash +orca does not speak the names of application icons

Status in OEM Priority Project:
  New
Status in Unity:
  Confirmed
Status in Unity 5.0 series:
  New
Status in Unity 6.0 series:
  New
Status in Unity 7.2 series:
  Confirmed
Status in unity package in Ubuntu:
  Triaged

Bug description:
  using orca and navigating around the dash with the keyboard I hear the
  names of videos, shopping results, files and folders, application
  suggestions from the software centre, but not the very most important
  thing in the dash - applications installed that I might want to run.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1066157/+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 1371625] Re: wifi don't work after suspend

[Ara Pulido]

** Changed in: oem-priority
   Status: New => Incomplete

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

Title:
  wifi don't work after suspend

Status in OEM Priority Project:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When i take my laptop, fujitsu-siemens AMILO-Li3710,  from a suspend state 
wifi don't work.
  I need to restart it to function properly.

  This is my laptop and i have ubuntu 14.04..
  http://wiki.ubuntu-it.org/Hardware/Notebook/FujitsuSiemensAMILOLi3710

  thx

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1371625/+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 1354498] Re: Switcher Icons emblem (count) is too small

[Ara Pulido]

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

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

Title:
  Switcher Icons emblem (count) is too small

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  New

Bug description:
  [ Impact]

  The emblem size does not change as the icon size is adjusted.

  [ Test Case ]

  (1) Use the System Settings > Displays > Scale for menus and title
  bars slider to adjust the Swicther icon size.

  (2) Observe the size of the badge.  It should scale with the icon
  size.

  [ Regression Potential

  Any code change to the Unity desktop shell has the potential to
  introduce new crashers or lockers.

  [ Other Info ]

  The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu
  14.10 where it has been in production use for some time with no
  apparent regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1354498/+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 1407865] Re: "Super+Alt+S" did not function at the login screen

[Ara Pulido]

** Also affects: orca (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: lightdm (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: orca (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: lightdm (Ubuntu Vivid)
   Importance: Undecided
   Status: New

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

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

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

Title:
   "Super+Alt+S" did not function at the login screen

Status in OEM Priority Project:
  Incomplete
Status in OEM Priority Project trusty series:
  New
Status in lightdm package in Ubuntu:
  Fix Released
Status in orca package in Ubuntu:
  Fix Released
Status in lightdm source package in Trusty:
  New
Status in orca source package in Trusty:
  New
Status in lightdm source package in Vivid:
  Fix Released
Status in orca source package in Vivid:
  Fix Released

Bug description:
  [Impact]
  Lenovo customer require to fix it.

  [Regression Potential]
  N/A

  [Other Info]
  N/A

  Summary:
  Some accessibility features of the Ubuntu operating system did not function. 
The command to toggle the Orca screen reader on and off (super+alt+S) did not 
function at the Login screen.

  Steps to reproduce:
  1. Boot into the system.
  2. Press "super+alt+s" to enable the orca screen reader.

  Expected result:
  The screen reader should be enabled.

  Actual result:
  It doesn't work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1407865/+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 1407865] Re: "Super+Alt+S" did not function at the login screen

[Ara Pulido]

What release of Ubuntu has this been tested? Does this happen in Vivid?

** Changed in: oem-priority
   Status: New => Incomplete

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

Title:
   "Super+Alt+S" did not function at the login screen

Status in OEM Priority Project:
  Incomplete
Status in OEM Priority Project trusty series:
  New
Status in lightdm package in Ubuntu:
  New
Status in orca package in Ubuntu:
  New

Bug description:
  Summary:Some accessibility features of the Ubuntu operating system did not 
function. The command to toggle the Orca screen reader on and off (super+alt+S) 
did not function at the Login screen.
  Steps to reproduce:
  1. Boot into the system.
  2. Press "super+alt+s" to enable the orca screen reader.
  Expected result:The screen reader should be enabled.
  Actual result:It doesn't work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1407865/+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 1395709] [NEW] Silence mode goes unchecked after 1 second

[Ara Pulido]

Public bug reported:

Using the phone in version 9, rtm English channel, but configured in
Spanish.

Steps to reproduce:

1) Go to system-settings/sound and enable silent mode
2) Reboot the phone
3) Unlock the SIM
4) Open the Sound Indicator and leave it open
5) Toggle Silence mode
6) Leave the indicator open and wait.

Expected results
* Silent mode is already checked on boot (bug 1391164)
* Silence mode stays checked

Actual results
* Silence mode goes back unchecked after 0.5 seconds.

** Affects: indicator-sound (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Silence mode goes unchecked after 1 second

Status in “indicator-sound” package in Ubuntu:
  New

Bug description:
  Using the phone in version 9, rtm English channel, but configured in
  Spanish.

  Steps to reproduce:

  1) Go to system-settings/sound and enable silent mode
  2) Reboot the phone
  3) Unlock the SIM
  4) Open the Sound Indicator and leave it open
  5) Toggle Silence mode
  6) Leave the indicator open and wait.

  Expected results
  * Silent mode is already checked on boot (bug 1391164)
  * Silence mode stays checked

  Actual results
  * Silence mode goes back unchecked after 0.5 seconds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1395709/+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 1332947] Re: HDPI: unity randomly turns on large text in universal access

[Ara Pulido]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Also affects: oem-priority/trusty
   Importance: Undecided
   Status: New

** Changed in: oem-priority
   Status: New => In Progress

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

Title:
  HDPI: unity randomly turns on large text in universal access

Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project trusty series:
  New
Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity” source package in Trusty:
  In Progress

Bug description:
  I have a macbook pro with retina display. In Ubuntu 14.04 64bit, every
  couple of reboots, the 'large text' option in Universal Access gets
  switched on upon login. It happens in roughly 1 out of 5 reboots for 1
  or more users on the computer.

  It appears to happen to people with small HighDPI screens. In my case, it's 
13 inch at 2560x1600.
  Another example is 13 inch at 1080p -  
http://askubuntu.com/questions/453785/large-text-button-in-universal-access-turns-itself-on-after-reboot-ubuntu-14-0

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

  unity-control-center:
Installed: 14.04.3+14.04.20140410-0ubuntu1
Candidate: 14.04.3+14.04.20140410-0ubuntu1
Version table:
   *** 14.04.3+14.04.20140410-0ubuntu1 0
  500 http://sk.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  
  intel iris pro graphics (lspci -vvv):

  00:02.0 VGA compatible controller: Intel Corporation Device 0a2e (rev 09) 
(prog-if 00 [VGA controller])
Subsystem: Apple Inc. Device 011a
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-  [disabled]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00018  Data: 
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [a4] PCI Advanced Features
AFCap: TP+ FLR+
AFCtrl: FLR-
AFStatus: TP-
Kernel driver in use: i915

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1332947/+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 1332947] Re: HDPI: unity randomly turns on large text in universal access

[Ara Pulido]

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

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

Title:
  HDPI: unity randomly turns on large text in universal access

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity” source package in Trusty:
  New

Bug description:
  I have a macbook pro with retina display. In Ubuntu 14.04 64bit, every
  couple of reboots, the 'large text' option in Universal Access gets
  switched on upon login. It happens in roughly 1 out of 5 reboots for 1
  or more users on the computer.

  It appears to happen to people with small HighDPI screens. In my case, it's 
13 inch at 2560x1600.
  Another example is 13 inch at 1080p -  
http://askubuntu.com/questions/453785/large-text-button-in-universal-access-turns-itself-on-after-reboot-ubuntu-14-0

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

  unity-control-center:
Installed: 14.04.3+14.04.20140410-0ubuntu1
Candidate: 14.04.3+14.04.20140410-0ubuntu1
Version table:
   *** 14.04.3+14.04.20140410-0ubuntu1 0
  500 http://sk.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  
  intel iris pro graphics (lspci -vvv):

  00:02.0 VGA compatible controller: Intel Corporation Device 0a2e (rev 09) 
(prog-if 00 [VGA controller])
Subsystem: Apple Inc. Device 011a
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-  [disabled]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00018  Data: 
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [a4] PCI Advanced Features
AFCap: TP+ FLR+
AFCtrl: FLR-
AFStatus: TP-
Kernel driver in use: i915

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1332947/+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 1316734] Re: Scaling factors for high DPI screens are sometimes applied twice

[Ara Pulido]

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

** Also affects: oem-priority/trusty
   Importance: Undecided
   Status: New

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

** Changed in: oem-priority
   Importance: Undecided => High

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

Title:
  Scaling factors for high DPI screens are sometimes applied twice

Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  New
Status in Unity:
  New
Status in “unity” package in Ubuntu:
  Confirmed
Status in “unity” source package in Trusty:
  New

Bug description:
  I have a high DPI screen, and thus configured Unity to scale
  everything by a factor of 1.62 (Under Settings -> Display). Sometimes
  after logging in the text is suddenly much larger than before, and
  this change persists even after reboot. I was able to get back normal
  font sizes by modifying text scaling in unity tweak.

  I'd have to look at this again the next time this happens, but if I
  understand this correctly then sometimes the scaling factor is re-
  applied to the text scaling in cases where it was already applied
  before, thus scaling the text by 1.62*1.62 instead of only 1.62 as it
  should be.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1316734/+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 1331037] Re: Touchscreens: The mouse cursor disappears when touching the screen

[Ara Pulido]

Marking as Invalid, as this is the intended behaviour.

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

** Changed in: oem-priority
   Status: Confirmed => Invalid

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

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

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

Title:
  Touchscreens: The mouse cursor disappears when touching the screen

Status in OEM Priority Project:
  Invalid
Status in OEM Priority Project trusty series:
  New
Status in Unity:
  Invalid
Status in “unity” package in Ubuntu:
  Invalid
Status in “unity” source package in Trusty:
  Invalid

Bug description:
  Single touch does cursor emulation, so I would expect that when I
  touch the touchscreen, the cursor jumps to the touch position.

  Instead of doing that, the cursor disappears until I use the mouse
  again.

  Touch events work correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.1+14.04.20140513-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Jun 17 17:03:39 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-04-29 (48 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/oem-priority/+bug/1331037/+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 1319698] Re: Gallery app shows pictures abnormally if target directory or file name contained Chinese text .

[Ara Pulido]

We are already shipping gallery-app in our pre-installed Ubuntu Desktop
systems, so we would need a fix for this sooner, rather than later.

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

Title:
  Gallery app shows pictures abnormally if target directory or file name
  contained Chinese text .

Status in Gallery App:
  In Progress
Status in OEM Priority Project:
  In Progress
Status in Thumbnail generator for all kinds of files:
  In Progress
Status in “thumbnailer” package in Ubuntu:
  In Progress

Bug description:
  Steps:
  1. Copy some pictures to ~/Pictures
  2. Launch Gallery app by entering "gallery" in Dash
  3. Observe what the Gallery shows.

  Actual results:
  There are some transparent frames in Gallery.

  Expected results:
  Gallery app should show pictures included in ~/Pictures directory in step 2.

  Platform:
  Lenovo S440s

  Note:
  Once Gallery's target directory or file name of the target directory contains 
Chinese text, the issue will be reproduced. Adverse, if Gallery's target 
directory or file name of the target directory in English, Gallery displays 
normally.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gallery-app/+bug/1319698/+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 1334546] Re: The search engine is hardcoded in webbrowser-app

[Ara Pulido]

** Changed in: oem-priority
   Status: Triaged => Fix Released

** Changed in: oem-priority/trusty
   Status: New => Fix Released

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

Title:
  The search engine is hardcoded in webbrowser-app

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project trusty series:
  Fix Released
Status in Web Browser App:
  Fix Released
Status in “unity8” package in Ubuntu:
  Invalid

Bug description:
  The search engine is hard coded into the webbroswer-app.

  http://bazaar.launchpad.net/~phablet-team/webbrowser-
  app/14.04/view/head:/src/app/AddressBar.qml

  function buildSearchUrl(query) {
  var searchUrl = 
"https://google.com/search?client=ubuntu&q=%1&ie=utf-8&oe=utf-8";
  var terms = query.split(/\s/).map(escapeHtmlEntities)
  return searchUrl.arg(terms.join("+"))
  }

  So can we add a way to easily change or customize the search engine?

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1334546/+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 1318584] Re: qt crashed when switching video out mode to external or internal only mode

[Ara Pulido]

Timo, Marteen, any updates on this bug?

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

Title:
  qt crashed when switching video out mode to external or internal only
  mode

Status in Checkbox - Graphical Test Runner:
  Confirmed
Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project trusty series:
  New
Status in Qt:
  New
Status in “qtbase-opensource-src” package in Ubuntu:
  Confirmed

Bug description:
  checkbox-gui crashed with following console outputs:

  pure virtual method called
  terminate called without an active exception
  Aborted (core dumped)

  Steps to reproduce:

  1. open checkbox-gui

  2. connected external display

  3. switch video output mode, usually by using the common video output
  switch hotkey.

  Expected result:

  checkbox-gui still running when switching back to extended desktop
  video out mode.

  Actual result:

  checkbox-gui crashed

  ---
  https://bugreports.qt-project.org/browse/QTBUG-39663

To manage notifications about this bug go to:
https://bugs.launchpad.net/checkbox-gui/+bug/1318584/+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 1076458] Re: [network]: gnome-control-center crashed with SIGSEGV in nm_device_get_udi()

[Ara Pulido]

This cannot be reproduced in Trusty.

** Also affects: network-manager (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: network-manager (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Changed in: network-manager (Ubuntu Trusty)
   Status: New => Invalid

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

Title:
  [network]: gnome-control-center crashed with SIGSEGV in
  nm_device_get_udi()

Status in “network-manager” package in Ubuntu:
  New
Status in “network-manager” source package in Precise:
  New
Status in “network-manager” source package in Trusty:
  Invalid

Bug description:
  Trying to setup open vpn

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: gnome-control-center 1:3.4.2-0ubuntu0.5
  ProcVersionSignature: Ubuntu 3.2.0-32.51-generic-pae 3.2.30
  Uname: Linux 3.2.0-32-generic-pae i686
  ApportVersion: 2.0.1-0ubuntu14
  Architecture: i386
  Date: Thu Nov  8 10:47:38 2012
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  ProcCmdline: gnome-control-center network
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xa66122c3 : cmp
%eax,(%edx)
   PC (0xa66122c3) ok
   source "%eax" ok
   destination "(%edx)" (0x046f) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   nm_device_get_udi () from /usr/lib/libnm-glib.so.4
   ?? () from /usr/lib/control-center-1/panels/libnetwork.so
   g_cclosure_marshal_VOID__PARAM () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: [network]: gnome-control-center crashed with SIGSEGV in 
nm_device_get_udi()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu3
   deja-dup22.0-0ubuntu2
   gnome-bluetooth 3.2.2-0ubuntu5
   gnome-control-center-signon 0.0.10-0precise1
   indicator-datetime  0.3.94-0ubuntu2

  [Impact]

   * gnome-control-center will crash when you get into network panel.

  [Test Case]

   * open gnome-control-center  
   * click network   --2
   * go back to main panel  --3
   * repeat step 2 and 3 

  [Regression Potential]

   * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696143  it has
  been accepted by upstream for a very long time. And our qe has
  verified it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1076458/+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 1035431] Re: bluetooh-wizard failed to connect to a keyboard(logitech)

[Ara Pulido]

** Also affects: gnome-bluetooth (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: bluez (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: gnome-bluetooth (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: bluez (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

Title:
  bluetooh-wizard failed to connect to a keyboard(logitech)

Status in GNOME Bluetooth:
  New
Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project trusty series:
  New
Status in “bluez” package in Ubuntu:
  Confirmed
Status in “gnome-bluetooth” package in Ubuntu:
  Confirmed
Status in “bluez” source package in Precise:
  New
Status in “gnome-bluetooth” source package in Precise:
  New
Status in “bluez” source package in Trusty:
  New
Status in “gnome-bluetooth” source package in Trusty:
  New

Bug description:
  When I try to connect my bluetooth keyboard using bluetooth-wizard, it
  ever fails:

  ** (bluetooth-wizard:11367): WARNING **: Setting up 'Logitech K760'
  failed: Authentication Failed

  This keyboard works fine with another computer under ubuntu 11.04.
  This keyboard works fine with this computer and Windows 7 (arghhh).
  This computer ubuntu 12.04 works fine with my bluetooth mouse.

  I can attach manually this keyboard to this computer using :

  sudo hidd --search

  My computer is a Samsung 305U1A
  My bluetooth interface is :

  Bus 003 Device 002: ID 0a5c:219c Broadcom Corp.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1035431/+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 1354313] Re: [Dell Inspiron 5721] Brightness control does not work with 12.04.5(with kernel 3.13)

[Ara Pulido]

** Also affects: hwe-next
   Importance: Undecided
   Status: New

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

Title:
  [Dell Inspiron 5721] Brightness control does not work with
  12.04.5(with kernel 3.13)

Status in HWE Next Project:
  New
Status in “linux-lts-trusty” package in Ubuntu:
  New
Status in “xorg” package in Ubuntu:
  New

Bug description:
  This is a system installed with latest stable 12.04.5 image.

  The Brightness key will invoke the osd-notify indicator but the
  display brightness won't change.

  Verifying the value changing in backlight interface, system are using
  acpi_video0 instead:

  Steps to monitor the backlight interfaces:

  Press the brightness key until maxium indicator shows:

  ubuntu@201210-11863:/sys/class/backlight$ cat intel_backlight/brightness ; 
cat acpi_video0/brightness
  3407
  99
  ubuntu@201210-11863:/sys/class/backlight$

  Press the brightness key until to minimum indicator shows:

  ubuntu@201210-11863:/sys/class/backlight$ cat intel_backlight/brightness ; 
cat acpi_video0/brightness
  3407
  0

  
  -

  The workaround found here could solve this issue:
  http://itsfoss.com/fix-brightness-ubuntu-1310/

  -

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.0.1-0ubuntu17.6
  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
  Date: Fri Aug  8 03:51:43 2014
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  DkmsStatus: fwts-efi-runtime-dkms, 14.07.00, 3.13.0-32-generic, x86_64: 
installed
  ExtraDebuggingInterest: Yes, even including gdb or git bisection work if 
needed
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:05ba]
   Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] 
(rev ff) (prog-if ff)
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MachineType: Dell Inc. Inspiron 5721
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=93a24f68-72a1-4335-938a-75f624f57e68 ro quiet splash initcall_debug 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0KNF68
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X01
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd10/25/2013:svnDellInc.:pnInspiron5721:pvrA12:rvnDellInc.:rn0KNF68:rvrX01:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron 5721
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.7.12-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1~precise1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1354313/+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 1308323] Re: Shutdown/reboot/login/logout dialogs not scaled after toggling UI scale Edit

[Ara Pulido]

** Changed in: oem-priority/trusty
   Status: New => Fix Released

** Changed in: oem-priority
   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 in Ubuntu.
https://bugs.launchpad.net/bugs/1308323

Title:
  Shutdown/reboot/login/logout dialogs not scaled after toggling UI
  scale Edit

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project trusty series:
  Fix Released
Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity” source package in Trusty:
  Fix Released

Bug description:
  1. Install Ubuntu-trusty image and boot into OS
  2. Go to System settings > Display
  3. Toggle UI scale up or down
  4. Press power button to launch poweroff notification prompt
  5. Check if the contents of the prompt is also scaled in accordance to the UI 
scale settings

  [Expected results]
  Contents of the poweroff notification prompt should be scaled in accordance 
to the UI scale settings

  [Actual results]
  Contents of the poweroff notification prompt is not scaled

  [Inpact]
  When Caps lock was active the icon did not render a tooltip if you moused 
over the icon. This can be consfusing if the user has no clue what the icon 
means.

  [Test case]
  1) Go to System Settings -> Display
  2) Change the DPI scale to a noticable size.
  3) Then select Shutdown to bring up the Dialog.

  Expected Result:
The shutdown dialog scaled correctly.

  [Regression potential]
  Low. Worse case we just dont scale, the changes are pretty isolated to the 
number changing game.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1308323/+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 1281058] Re: [UIFe] The system shutdowns when multiple accounts are open

[Ara Pulido]

** Changed in: oem-priority
   Status: In Progress => Fix Released

** Changed in: oem-priority/trusty
   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 in Ubuntu.
https://bugs.launchpad.net/bugs/1281058

Title:
  [UIFe] The system shutdowns when multiple accounts are open

Status in Ayatana Design:
  Fix Committed
Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project trusty series:
  Fix Released
Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Released
Status in “indicator-session” package in Ubuntu:
  Triaged
Status in “systemd” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity-greeter” package in Ubuntu:
  Fix Released
Status in “indicator-session” source package in Trusty:
  Confirmed
Status in “systemd” source package in Trusty:
  Confirmed
Status in “unity” source package in Trusty:
  Fix Released
Status in “unity-greeter” source package in Trusty:
  Fix Released

Bug description:
  [Impact]

  Other users logged into a system may loose work if another user shuts
  down/reboots a system.  Data loss is not a Good Thing.

  [Test Case]

  Steps to reproduce:

  1) Create a second account in the system
  2) While the first account is open, open a session with the second one
  3) Try to shutdown the system

  Expected results:
  The system logs out instead of shutting down (ideally with a warning on why 
it did that)

  Actual results:
  The system shutdowns and unsaved data on session1 is lost

  [ Regression Potential]

  None.

  --
  Desired resolution:

  - Add a warning message informing the user that other users are logged in and 
then shutting down will also close their sessions as proposed in the mockup 
attached to comment #12
  - The warning message should be "Other users are currently logged in to this 
computer, shutting down now will also close these other sessions"

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