from:"Yu"

jammy: replace "Closes => LP"

** Patch added: "libmbim_1.28.0-1~ubuntu20.04.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/2014954/+attachment/5680885/+files/libmbim_1.28.0-1~ubuntu20.04.2.debdiff

** Patch removed: "libmbim_1.28.0-1~ubuntu20.04.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/2014954/+attachment/5676943/+files/libmbim_1.28.0-1~ubuntu20.04.2.debdiff

** Patch removed: "libmbim_1.28.2-1ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/2014954/+attachment/5680077/+files/libmbim_1.28.2-1ubuntu1.debdiff

** Patch removed: "libmbim_1.28.4-2ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/2014954/+attachment/5680078/+files/libmbim_1.28.4-2ubuntu1.debdiff

** Patch removed: "libmbim_1.28.0-1~ubuntu20.04.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/2014954/+attachment/5680079/+files/libmbim_1.28.0-1~ubuntu20.04.2.debdiff

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

Title:
  Backport Intel Mutual Authentications - FCC Lock

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  In Progress
Status in libmbim source package in Jammy:
  New
Status in libmbim source package in Lunar:
  New

Bug description:
  [ Impact ]

  There exist no formal API to do the FCC unlock procedure[1] in the
  latest version of the modemmanger.

  But there is a merged commit[2] that provide this functionality for
  intel WWAN cards in the upstream project.

  Lenovo have several laptops using the Intel WWAN cards, and Lenovo are
  struggling to give a decent way to run the FCC unlock service without
  this.

  [ Test Plan ]

  OEM enablement engineers and Lenovo engineers will help to test if the
  FCC unlock would work on certain laptops with the help of a custom
  package[1] provided by Lenovo which contains the FCC unlock script.

  [ Where problems could occur ]

  This is a completely new feature to support Intel WWAN cards mutal
  authentication, which does not affect other existing features.

  But the feature itself might have bugs and glitches since it is a
  brand new one and is not widely tested by the laptop vendors, still it
  is better than nothing.

  [ Other Info ]

  [1] FCC unlock procedure: 
https://modemmanager.org/docs/modemmanager/fcc-unlock/
  [2] intel-mutual-authentication: new service, fcc-lock: 
https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/merge_requests/157
- when the device is first shipped or comes out of the factory,
  it should be protected with a lock till the device reaches
  the end user. This FCC lock feature will ensure the device
  is secured till its unlocked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2014954/+subscriptions


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

[Desktop-packages] [Bug 2014954] Re: Backport Intel Mutual Authentications - FCC Lock

lunar: replace "Closes => LP"

** Patch added: "libmbim_1.28.2-1ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/2014954/+attachment/5680884/+files/libmbim_1.28.2-1ubuntu1.debdiff

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

Title:
  Backport Intel Mutual Authentications - FCC Lock

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  In Progress
Status in libmbim source package in Jammy:
  New
Status in libmbim source package in Lunar:
  New

Bug description:
  [ Impact ]

  There exist no formal API to do the FCC unlock procedure[1] in the
  latest version of the modemmanger.

  But there is a merged commit[2] that provide this functionality for
  intel WWAN cards in the upstream project.

  Lenovo have several laptops using the Intel WWAN cards, and Lenovo are
  struggling to give a decent way to run the FCC unlock service without
  this.

  [ Test Plan ]

  OEM enablement engineers and Lenovo engineers will help to test if the
  FCC unlock would work on certain laptops with the help of a custom
  package[1] provided by Lenovo which contains the FCC unlock script.

  [ Where problems could occur ]

  This is a completely new feature to support Intel WWAN cards mutal
  authentication, which does not affect other existing features.

  But the feature itself might have bugs and glitches since it is a
  brand new one and is not widely tested by the laptop vendors, still it
  is better than nothing.

  [ Other Info ]

  [1] FCC unlock procedure: 
https://modemmanager.org/docs/modemmanager/fcc-unlock/
  [2] intel-mutual-authentication: new service, fcc-lock: 
https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/merge_requests/157
- when the device is first shipped or comes out of the factory,
  it should be protected with a lock till the device reaches
  the end user. This FCC lock feature will ensure the device
  is secured till its unlocked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2014954/+subscriptions


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

[Desktop-packages] [Bug 2014954] Re: Backport Intel Mutual Authentications - FCC Lock

mantic: replace "Closes => LP"

** Patch added: "libmbim_1.28.4-2ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/2014954/+attachment/5680883/+files/libmbim_1.28.4-2ubuntu1.debdiff

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

Title:
  Backport Intel Mutual Authentications - FCC Lock

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  In Progress
Status in libmbim source package in Jammy:
  New
Status in libmbim source package in Lunar:
  New

Bug description:
  [ Impact ]

  There exist no formal API to do the FCC unlock procedure[1] in the
  latest version of the modemmanger.

  But there is a merged commit[2] that provide this functionality for
  intel WWAN cards in the upstream project.

  Lenovo have several laptops using the Intel WWAN cards, and Lenovo are
  struggling to give a decent way to run the FCC unlock service without
  this.

  [ Test Plan ]

  OEM enablement engineers and Lenovo engineers will help to test if the
  FCC unlock would work on certain laptops with the help of a custom
  package[1] provided by Lenovo which contains the FCC unlock script.

  [ Where problems could occur ]

  This is a completely new feature to support Intel WWAN cards mutal
  authentication, which does not affect other existing features.

  But the feature itself might have bugs and glitches since it is a
  brand new one and is not widely tested by the laptop vendors, still it
  is better than nothing.

  [ Other Info ]

  [1] FCC unlock procedure: 
https://modemmanager.org/docs/modemmanager/fcc-unlock/
  [2] intel-mutual-authentication: new service, fcc-lock: 
https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/merge_requests/157
- when the device is first shipped or comes out of the factory,
  it should be protected with a lock till the device reaches
  the end user. This FCC lock feature will ensure the device
  is secured till its unlocked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2014954/+subscriptions


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

[Desktop-packages] [Bug 2014954] Re: Backport Intel Mutual Authentications - FCC Lock

Hi @Christian, thanks for the comment, I thought "Closes" and "LP" are the same 
thing.
The Lenovo wants to ship their new laptop products with "Fibocom L860-GL" (uses 
MBIM protocol) and needs this patch to do the FCC unlock. Their aim is that the 
SIM card can work properly once end user receives the device.

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

Title:
  Backport Intel Mutual Authentications - FCC Lock

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  In Progress
Status in libmbim source package in Jammy:
  New
Status in libmbim source package in Lunar:
  New

Bug description:
  [ Impact ]

  There exist no formal API to do the FCC unlock procedure[1] in the
  latest version of the modemmanger.

  But there is a merged commit[2] that provide this functionality for
  intel WWAN cards in the upstream project.

  Lenovo have several laptops using the Intel WWAN cards, and Lenovo are
  struggling to give a decent way to run the FCC unlock service without
  this.

  [ Test Plan ]

  OEM enablement engineers and Lenovo engineers will help to test if the
  FCC unlock would work on certain laptops with the help of a custom
  package[1] provided by Lenovo which contains the FCC unlock script.

  [ Where problems could occur ]

  This is a completely new feature to support Intel WWAN cards mutal
  authentication, which does not affect other existing features.

  But the feature itself might have bugs and glitches since it is a
  brand new one and is not widely tested by the laptop vendors, still it
  is better than nothing.

  [ Other Info ]

  [1] FCC unlock procedure: 
https://modemmanager.org/docs/modemmanager/fcc-unlock/
  [2] intel-mutual-authentication: new service, fcc-lock: 
https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/merge_requests/157
- when the device is first shipped or comes out of the factory,
  it should be protected with a lock till the device reaches
  the end user. This FCC lock feature will ensure the device
  is secured till its unlocked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2014954/+subscriptions


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

[Desktop-packages] [Bug 2014954] Re: Backport Intel Mutual Authentications - FCC Lock

Thanks Lucas and Seb, I re-uploaded the debdiff patch file for theses 3
series.

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

Title:
  Backport Intel Mutual Authentications - FCC Lock

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  In Progress
Status in libmbim source package in Jammy:
  New
Status in libmbim source package in Lunar:
  New

Bug description:
  [ Impact ]

  There exist no formal API to do the FCC unlock procedure[1] in the
  latest version of the modemmanger.

  But there is a merged commit[2] that provide this functionality for
  intel WWAN cards in the upstream project.

  Lenovo have several laptops using the Intel WWAN cards, and Lenovo are
  struggling to give a decent way to run the FCC unlock service without
  this.

  [ Test Plan ]

  OEM enablement engineers and Lenovo engineers will help to test if the
  FCC unlock would work on certain laptops with the help of a custom
  package[1] provided by Lenovo which contains the FCC unlock script.

  [ Where problems could occur ]

  This is a completely new feature to support Intel WWAN cards mutal
  authentication, which does not affect other existing features.

  But the feature itself might have bugs and glitches since it is a
  brand new one and is not widely tested by the laptop vendors, still it
  is better than nothing.

  [ Other Info ]

  [1] FCC unlock procedure: 
https://modemmanager.org/docs/modemmanager/fcc-unlock/
  [2] intel-mutual-authentication: new service, fcc-lock: 
https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/merge_requests/157
- when the device is first shipped or comes out of the factory,
  it should be protected with a lock till the device reaches
  the end user. This FCC lock feature will ensure the device
  is secured till its unlocked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2014954/+subscriptions


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

[Desktop-packages] [Bug 2014954] Re: Backport Intel Mutual Authentications - FCC Lock

for jammy

** Patch added: "libmbim_1.28.0-1~ubuntu20.04.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/2014954/+attachment/5680079/+files/libmbim_1.28.0-1~ubuntu20.04.2.debdiff

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

Title:
  Backport Intel Mutual Authentications - FCC Lock

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  In Progress
Status in libmbim source package in Jammy:
  New
Status in libmbim source package in Lunar:
  New

Bug description:
  [ Impact ]

  There exist no formal API to do the FCC unlock procedure[1] in the
  latest version of the modemmanger.

  But there is a merged commit[2] that provide this functionality for
  intel WWAN cards in the upstream project.

  Lenovo have several laptops using the Intel WWAN cards, and Lenovo are
  struggling to give a decent way to run the FCC unlock service without
  this.

  [ Test Plan ]

  OEM enablement engineers and Lenovo engineers will help to test if the
  FCC unlock would work on certain laptops with the help of a custom
  package[1] provided by Lenovo which contains the FCC unlock script.

  [ Where problems could occur ]

  This is a completely new feature to support Intel WWAN cards mutal
  authentication, which does not affect other existing features.

  But the feature itself might have bugs and glitches since it is a
  brand new one and is not widely tested by the laptop vendors, still it
  is better than nothing.

  [ Other Info ]

  [1] FCC unlock procedure: 
https://modemmanager.org/docs/modemmanager/fcc-unlock/
  [2] intel-mutual-authentication: new service, fcc-lock: 
https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/merge_requests/157
- when the device is first shipped or comes out of the factory,
  it should be protected with a lock till the device reaches
  the end user. This FCC lock feature will ensure the device
  is secured till its unlocked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2014954/+subscriptions


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

[Desktop-packages] [Bug 2014954] Re: Backport Intel Mutual Authentications - FCC Lock

for mantic

** Patch added: "libmbim_1.28.4-2ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/2014954/+attachment/5680078/+files/libmbim_1.28.4-2ubuntu1.debdiff

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

Title:
  Backport Intel Mutual Authentications - FCC Lock

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  In Progress
Status in libmbim source package in Jammy:
  New
Status in libmbim source package in Lunar:
  New

Bug description:
  [ Impact ]

  There exist no formal API to do the FCC unlock procedure[1] in the
  latest version of the modemmanger.

  But there is a merged commit[2] that provide this functionality for
  intel WWAN cards in the upstream project.

  Lenovo have several laptops using the Intel WWAN cards, and Lenovo are
  struggling to give a decent way to run the FCC unlock service without
  this.

  [ Test Plan ]

  OEM enablement engineers and Lenovo engineers will help to test if the
  FCC unlock would work on certain laptops with the help of a custom
  package[1] provided by Lenovo which contains the FCC unlock script.

  [ Where problems could occur ]

  This is a completely new feature to support Intel WWAN cards mutal
  authentication, which does not affect other existing features.

  But the feature itself might have bugs and glitches since it is a
  brand new one and is not widely tested by the laptop vendors, still it
  is better than nothing.

  [ Other Info ]

  [1] FCC unlock procedure: 
https://modemmanager.org/docs/modemmanager/fcc-unlock/
  [2] intel-mutual-authentication: new service, fcc-lock: 
https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/merge_requests/157
- when the device is first shipped or comes out of the factory,
  it should be protected with a lock till the device reaches
  the end user. This FCC lock feature will ensure the device
  is secured till its unlocked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2014954/+subscriptions


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

[Desktop-packages] [Bug 2014954] Re: Backport Intel Mutual Authentications - FCC Lock

for lunar

** Patch added: "libmbim_1.28.2-1ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/2014954/+attachment/5680077/+files/libmbim_1.28.2-1ubuntu1.debdiff

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

Title:
  Backport Intel Mutual Authentications - FCC Lock

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  In Progress
Status in libmbim source package in Jammy:
  New
Status in libmbim source package in Lunar:
  New

Bug description:
  [ Impact ]

  There exist no formal API to do the FCC unlock procedure[1] in the
  latest version of the modemmanger.

  But there is a merged commit[2] that provide this functionality for
  intel WWAN cards in the upstream project.

  Lenovo have several laptops using the Intel WWAN cards, and Lenovo are
  struggling to give a decent way to run the FCC unlock service without
  this.

  [ Test Plan ]

  OEM enablement engineers and Lenovo engineers will help to test if the
  FCC unlock would work on certain laptops with the help of a custom
  package[1] provided by Lenovo which contains the FCC unlock script.

  [ Where problems could occur ]

  This is a completely new feature to support Intel WWAN cards mutal
  authentication, which does not affect other existing features.

  But the feature itself might have bugs and glitches since it is a
  brand new one and is not widely tested by the laptop vendors, still it
  is better than nothing.

  [ Other Info ]

  [1] FCC unlock procedure: 
https://modemmanager.org/docs/modemmanager/fcc-unlock/
  [2] intel-mutual-authentication: new service, fcc-lock: 
https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/merge_requests/157
- when the device is first shipped or comes out of the factory,
  it should be protected with a lock till the device reaches
  the end user. This FCC lock feature will ensure the device
  is secured till its unlocked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2014954/+subscriptions


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

[Desktop-packages] [Bug 2014954] Re: Backport Intel Mutual Authentications - FCC Lock

2023-06-13 Thread Atlas Yu

Hi @seb128, this is not the same as Bug #1950282, this is for Fibocom
L860-GL-16.

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

** Changed in: libmbim (Ubuntu)
 Assignee: Atlas Yu (pseudoc) => (unassigned)

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

Title:
  Backport Intel Mutual Authentications - FCC Lock

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

Bug description:
  [ Impact ]

  There exist no formal API to do the FCC unlock procedure[1] in the
  latest version of the modemmanger.

  But there is a merged commit[2] that provide this functionality for
  intel WWAN cards in the upstream project.

  Lenovo have several laptops using the Intel WWAN cards, and Lenovo are
  struggling to give a decent way to run the FCC unlock service without
  this.

  [ Test Plan ]

  OEM enablement engineers and Lenovo engineers will help to test if the
  FCC unlock would work on certain laptops with the help of a custom
  package[1] provided by Lenovo which contains the FCC unlock script.

  [ Where problems could occur ]

  This is a completely new feature to support Intel WWAN cards mutal
  authentication, which does not affect other existing features.

  But the feature itself might have bugs and glitches since it is a
  brand new one and is not widely tested by the laptop vendors, still it
  is better than nothing.

  [ Other Info ]

  [1] FCC unlock procedure: 
https://modemmanager.org/docs/modemmanager/fcc-unlock/
  [2] intel-mutual-authentication: new service, fcc-lock: 
https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/merge_requests/157
- when the device is first shipped or comes out of the factory,
  it should be protected with a lock till the device reaches
  the end user. This FCC lock feature will ensure the device
  is secured till its unlocked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2014954/+subscriptions


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

[Desktop-packages] [Bug 2014954] Re: Backport Intel Mutual Authentications - FCC Lock

2023-05-31 Thread Atlas Yu

refined debdiff

** Patch removed: "libmbim_1.28.0-1~ubuntu20.04.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/2014954/+attachment/5659790/+files/libmbim_1.28.0-1~ubuntu20.04.2.debdiff

** Patch added: "libmbim_1.28.0-1~ubuntu20.04.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/2014954/+attachment/5676943/+files/libmbim_1.28.0-1~ubuntu20.04.2.debdiff

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

Title:
  Backport Intel Mutual Authentications - FCC Lock

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

Bug description:
  [ Impact ]

  There exist no formal API to do the FCC unlock procedure[1] in the
  latest version of the modemmanger.

  But there is a merged commit[2] that provide this functionality for
  intel WWAN cards in the upstream project.

  Lenovo have several laptops using the Intel WWAN cards, and Lenovo are
  struggling to give a decent way to run the FCC unlock service without
  this.

  [ Test Plan ]

  OEM enablement engineers and Lenovo engineers will help to test if the
  FCC unlock would work on certain laptops with the help of a custom
  package[1] provided by Lenovo which contains the FCC unlock script.

  [ Where problems could occur ]

  This is a completely new feature to support Intel WWAN cards mutal
  authentication, which does not affect other existing features.

  But the feature itself might have bugs and glitches since it is a
  brand new one and is not widely tested by the laptop vendors, still it
  is better than nothing.

  [ Other Info ]

  [1] FCC unlock procedure: 
https://modemmanager.org/docs/modemmanager/fcc-unlock/
  [2] intel-mutual-authentication: new service, fcc-lock: 
https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/merge_requests/157
- when the device is first shipped or comes out of the factory,
  it should be protected with a lock till the device reaches
  the end user. This FCC lock feature will ensure the device
  is secured till its unlocked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2014954/+subscriptions


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

[Desktop-packages] [Bug 2014954] Re: Backport Intel Mutual Authentications - FCC Lock

2023-05-31 Thread Atlas Yu

I uploaded the modified version to my PPA:
https://launchpad.net/~pseudoc/+archive/ubuntu/ppa/+packages

You may install the libmbim from it:
sudo add-apt-repository ppa:pseudoc/ppa
sudo apt update
sudo apt install libmbim

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

Title:
  Backport Intel Mutual Authentications - FCC Lock

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

Bug description:
  [ Impact ]

  There exist no formal API to do the FCC unlock procedure[1] in the
  latest version of the modemmanger.

  But there is a merged commit[2] that provide this functionality for
  intel WWAN cards in the upstream project.

  Lenovo have several laptops using the Intel WWAN cards, and Lenovo are
  struggling to give a decent way to run the FCC unlock service without
  this.

  [ Test Plan ]

  OEM enablement engineers and Lenovo engineers will help to test if the
  FCC unlock would work on certain laptops with the help of a custom
  package[1] provided by Lenovo which contains the FCC unlock script.

  [ Where problems could occur ]

  This is a completely new feature to support Intel WWAN cards mutal
  authentication, which does not affect other existing features.

  But the feature itself might have bugs and glitches since it is a
  brand new one and is not widely tested by the laptop vendors, still it
  is better than nothing.

  [ Other Info ]

  [1] FCC unlock procedure: 
https://modemmanager.org/docs/modemmanager/fcc-unlock/
  [2] intel-mutual-authentication: new service, fcc-lock: 
https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/merge_requests/157
- when the device is first shipped or comes out of the factory,
  it should be protected with a lock till the device reaches
  the end user. This FCC lock feature will ensure the device
  is secured till its unlocked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2014954/+subscriptions


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

[Desktop-packages] [Bug 2011770] Re: [gsd-rfkill] WwanEnabled never get synced

2023-04-18 Thread Atlas Yu

Upstream project will include the fix for 44.1.

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/2011770

Title:
  [gsd-rfkill] WwanEnabled never get synced

Status in OEM Priority Project:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Jammy:
  Fix Released
Status in gnome-settings-daemon source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

   * Sometimes on devices with WWAN card, whenever user presses the
  wireless function key (Fn+F8) or turn on the airplane mode radio
  button in Settings, the airplane mode will not be enabled, and the
  airplane mode icon is not shown in the status bar.

   * There is a unmerged upstream merge request that delivers the fix:
  https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/-/merge_requests/310

  It works perfectly well on several Lenovo laptops with WWAN cards.
  The root causes is that the value of "WwanEnabled" under 
"org.freedesktop.NetworkManager" is not synced correctly, gsd-rfkill should 
listen to "g-properties-changed" instead of "g-signal" now.

  [ Test Plan ]

   1. Find a machine which has WWAN card.
   2. Boot the machine, and run rfkill list to see if WWAN is unblocked. if not 
use rfkill to unblock the WWAN, and reboot.
   3. Press the wireless media key (Fn+F8) or turn on the airplane mode radio 
button in Settings.
   4. The airplane mode should be enabled, but actually not.

  [ Where problems could occur ]

   * When user is using a very low version network-manager (< 1.20) that
  still broadcasting DBUS "PropertiesChanged" events on "g-signal"
  instead of the concurrent "g-properties-changed", the airplane mode
  will sometimes not be able to enable.

  [1]: 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/853
  [2]: 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/6fb917178aa19c61e909957f5146aa4565e0cb2f

  [ Other Info ]

  1. About Ubuntu
  Description:Ubuntu 22.04.2 LTS
  Release:22.04
  Kernel: 6.1.0-1007-oem

  2. The version of packages:
  gnome-settings-daemon:
    Installed: 42.1-1ubuntu2.1

  network-manager:
    Installed: 1.36.6-0ubuntu2

  3. Expect:
  The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is called, and 
manager->wwan_enabled is set to the correct value.

  4. Actual:
  The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is never called, 
so manager->wwan_enabled is not synced, If machine has WWAN device(s), and the 
initial value of manager->wwan_enabled is true, it will never be able to switch 
to airplane mode.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2011770/+subscriptions


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

[Desktop-packages] [Bug 2014954] Re: Backport Intel Mutual Authentications - FCC Lock

2023-04-01 Thread Atlas Yu

Here is the debdiff with the upstream patch.

** Patch added: "libmbim_1.28.0-1~ubuntu20.04.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/2014954/+attachment/5659790/+files/libmbim_1.28.0-1~ubuntu20.04.2.debdiff

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

Title:
  Backport Intel Mutual Authentications - FCC Lock

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

Bug description:
  [ Impact ]

  There exist no formal API to do the FCC unlock procedure[1] in the
  latest version of the modemmanger.

  But there is a merged commit[2] that provide this functionality for
  intel WWAN cards in the upstream project.

  Lenovo have several laptops using the Intel WWAN cards, and Lenovo are
  struggling to give a decent way to run the FCC unlock service without
  this.

  [ Test Plan ]

  OEM enablement engineers and Lenovo engineers will help to test if the
  FCC unlock would work on certain laptops with the help of a custom
  package[1] provided by Lenovo which contains the FCC unlock script.

  [ Where problems could occur ]

  This is a completely new feature to support Intel WWAN cards mutal
  authentication, which does not affect other existing features.

  But the feature itself might have bugs and glitches since it is a
  brand new one and is not widely tested by the laptop vendors, still it
  is better than nothing.

  [ Other Info ]

  [1] FCC unlock procedure: 
https://modemmanager.org/docs/modemmanager/fcc-unlock/
  [2] intel-mutual-authentication: new service, fcc-lock: 
https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/merge_requests/157
- when the device is first shipped or comes out of the factory,
  it should be protected with a lock till the device reaches
  the end user. This FCC lock feature will ensure the device
  is secured till its unlocked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2014954/+subscriptions


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

[Desktop-packages] [Bug 2014954] Re: Backport Intel Mutual Authentications - FCC Lock

2023-04-01 Thread Atlas Yu

** Tags added: oem-priority originate-from-1956804 sutton

** Tags added: originate-from-2007061

** Changed in: oem-priority
 Assignee: (unassigned) => Atlas Yu (pseudoc)

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

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

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

Title:
  Backport Intel Mutual Authentications - FCC Lock

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

Bug description:
  [ Impact ]

  There exist no formal API to do the FCC unlock procedure[1] in the
  latest version of the modemmanger.

  But there is a merged commit[2] that provide this functionality for
  intel WWAN cards in the upstream project.

  Lenovo have several laptops using the Intel WWAN cards, and Lenovo are
  struggling to give a decent way to run the FCC unlock service without
  this.

  [ Test Plan ]

  OEM enablement engineers and Lenovo engineers will help to test if the
  FCC unlock would work on certain laptops with the help of a custom
  package[1] provided by Lenovo which contains the FCC unlock script.

  [ Where problems could occur ]

  This is a completely new feature to support Intel WWAN cards mutal
  authentication, which does not affect other existing features.

  But the feature itself might have bugs and glitches since it is a
  brand new one and is not widely tested by the laptop vendors, still it
  is better than nothing.

  [ Other Info ]

  [1] FCC unlock procedure: 
https://modemmanager.org/docs/modemmanager/fcc-unlock/
  [2] intel-mutual-authentication: new service, fcc-lock: 
https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/merge_requests/157
- when the device is first shipped or comes out of the factory,
  it should be protected with a lock till the device reaches
  the end user. This FCC lock feature will ensure the device
  is secured till its unlocked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2014954/+subscriptions


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

[Desktop-packages] [Bug 2014954] [NEW] Backport Intel Mutual Authentications - FCC Lock

2023-04-01 Thread Atlas Yu

Public bug reported:

[ Impact ]

There exist no formal API to do the FCC unlock procedure[1] in the
latest version of the modemmanger.

But there is a merged commit[2] that provide this functionality for
intel WWAN cards in the upstream project.

Lenovo have several laptops using the Intel WWAN cards, and Lenovo are
struggling to give a decent way to run the FCC unlock service without
this.

[ Test Plan ]

OEM enablement engineers and Lenovo engineers will help to test if the
FCC unlock would work on certain laptops with the help of a custom
package[1] provided by Lenovo which contains the FCC unlock script.

[ Where problems could occur ]

This is a completely new feature to support Intel WWAN cards mutal
authentication, which does not affect other existing features.

But the feature itself might have bugs and glitches since it is a brand
new one and is not widely tested by the laptop vendors, still it is
better than nothing.

[ Other Info ]

[1] FCC unlock procedure: https://modemmanager.org/docs/modemmanager/fcc-unlock/
[2] intel-mutual-authentication: new service, fcc-lock: 
https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/merge_requests/157
  - when the device is first shipped or comes out of the factory,
it should be protected with a lock till the device reaches
the end user. This FCC lock feature will ensure the device
is secured till its unlocked.

** Affects: oem-priority
 Importance: High
 Assignee: Atlas Yu (pseudoc)
 Status: Confirmed

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


** Tags: oem-priority originate-from-1956804 originate-from-2007061 sutton

** Description changed:

  [ Impact ]
  
  There exist no formal API to do the FCC unlock procedure[1] in the
  latest version of the modemmanger.
  
  But there is a merged commit[2] that provide this functionality for
  intel WWAN cards in the upstream project.
  
  Lenovo have several laptops using the Intel WWAN cards, and Lenovo are
  struggling to give a decent way to run the FCC unlock service without
  this.
  
  [ Test Plan ]
  
  OEM enablement engineers and Lenovo engineers will help to test if the
  FCC unlock would work on certain laptops with the help of a custom
  package[1] provided by Lenovo which contains the FCC unlock script.
  
  [ Where problems could occur ]
  
  This is a completely new feature to support Intel WWAN cards mutal
  authentication, which does not affect other existing features.
  
  But the feature itself might have bugs and glitches since it is a brand
  new one and is not widely tested by the laptop vendors, still it is
  better than nothing.
  
  [ Other Info ]
  
  [1] FCC unlock procedure: 
https://modemmanager.org/docs/modemmanager/fcc-unlock/
- [2] 
- intel-mutual-authentication: new service, fcc-lock: 
https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/merge_requests/157
+ [2] intel-mutual-authentication: new service, fcc-lock: 
https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/merge_requests/157
  - when the device is first shipped or comes out of the factory,
  it should be protected with a lock till the device reaches
  the end user. This FCC lock feature will ensure the device
  is secured till its unlocked.

** Description changed:

  [ Impact ]
  
  There exist no formal API to do the FCC unlock procedure[1] in the
  latest version of the modemmanger.
  
  But there is a merged commit[2] that provide this functionality for
  intel WWAN cards in the upstream project.
  
  Lenovo have several laptops using the Intel WWAN cards, and Lenovo are
  struggling to give a decent way to run the FCC unlock service without
  this.
  
  [ Test Plan ]
  
  OEM enablement engineers and Lenovo engineers will help to test if the
  FCC unlock would work on certain laptops with the help of a custom
  package[1] provided by Lenovo which contains the FCC unlock script.
  
  [ Where problems could occur ]
  
  This is a completely new feature to support Intel WWAN cards mutal
  authentication, which does not affect other existing features.
  
  But the feature itself might have bugs and glitches since it is a brand
  new one and is not widely tested by the laptop vendors, still it is
  better than nothing.
  
  [ Other Info ]
  
  [1] FCC unlock procedure: 
https://modemmanager.org/docs/modemmanager/fcc-unlock/
  [2] intel-mutual-authentication: new service, fcc-lock: 
https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/merge_requests/157
- - when the device is first shipped or comes out of the factory,
- it should be protected with a lock till the device reaches
- the end user. This FCC lock feature will ensure the device
- is secured till its unlocked.
+   - when the device is first shipped or comes out of the factory,
+ it should be protected with a lock till the device reaches
+ the end user. This FCC lock feature will ensure the device
+ is secured till its unlocked.

-- 
You received this bug notification

[Desktop-packages] [Bug 2011770] Re: [gsd-rfkill] WwanEnabled never get synced

2023-03-26 Thread Atlas Yu

RE: #14/#15

The autopkgtest regressions seem not to be real regressions, this patch
only affect WWAN, in the regression report the failure is about display
issue in mutter.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/2011770

Title:
  [gsd-rfkill] WwanEnabled never get synced

Status in OEM Priority Project:
  Fix Committed
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Jammy:
  Fix Committed
Status in gnome-settings-daemon source package in Kinetic:
  Fix Committed

Bug description:
  [ Impact ]

   * Sometimes on devices with WWAN card, whenever user presses the
  wireless function key (Fn+F8) or turn on the airplane mode radio
  button in Settings, the airplane mode will not be enabled, and the
  airplane mode icon is not shown in the status bar.

   * There is a unmerged upstream merge request that delivers the fix:
  https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/-/merge_requests/310

  It works perfectly well on several Lenovo laptops with WWAN cards.
  The root causes is that the value of "WwanEnabled" under 
"org.freedesktop.NetworkManager" is not synced correctly, gsd-rfkill should 
listen to "g-properties-changed" instead of "g-signal" now.

  [ Test Plan ]

   1. Find a machine which has WWAN card.
   2. Boot the machine, and run rfkill list to see if WWAN is unblocked. if not 
use rfkill to unblock the WWAN, and reboot.
   3. Press the wireless media key (Fn+F8) or turn on the airplane mode radio 
button in Settings.
   4. The airplane mode should be enabled, but actually not.

  [ Where problems could occur ]

   * When user is using a very low version network-manager (< 1.20) that
  still broadcasting DBUS "PropertiesChanged" events on "g-signal"
  instead of the concurrent "g-properties-changed", the airplane mode
  will sometimes not be able to enable.

  [1]: 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/853
  [2]: 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/6fb917178aa19c61e909957f5146aa4565e0cb2f

  [ Other Info ]

  1. About Ubuntu
  Description:Ubuntu 22.04.2 LTS
  Release:22.04
  Kernel: 6.1.0-1007-oem

  2. The version of packages:
  gnome-settings-daemon:
    Installed: 42.1-1ubuntu2.1

  network-manager:
    Installed: 1.36.6-0ubuntu2

  3. Expect:
  The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is called, and 
manager->wwan_enabled is set to the correct value.

  4. Actual:
  The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is never called, 
so manager->wwan_enabled is not synced, If machine has WWAN device(s), and the 
initial value of manager->wwan_enabled is true, it will never be able to switch 
to airplane mode.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2011770/+subscriptions


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

[Desktop-packages] [Bug 2011770] Re: [gsd-rfkill] WwanEnabled never get synced

2023-03-26 Thread Atlas Yu

Verified the new version of gnome-settings-daemon (43.0-1ubuntu1.1) on
kinetic.

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/2011770

Title:
  [gsd-rfkill] WwanEnabled never get synced

Status in OEM Priority Project:
  Fix Committed
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Jammy:
  Fix Committed
Status in gnome-settings-daemon source package in Kinetic:
  Fix Committed

Bug description:
  [ Impact ]

   * Sometimes on devices with WWAN card, whenever user presses the
  wireless function key (Fn+F8) or turn on the airplane mode radio
  button in Settings, the airplane mode will not be enabled, and the
  airplane mode icon is not shown in the status bar.

   * There is a unmerged upstream merge request that delivers the fix:
  https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/-/merge_requests/310

  It works perfectly well on several Lenovo laptops with WWAN cards.
  The root causes is that the value of "WwanEnabled" under 
"org.freedesktop.NetworkManager" is not synced correctly, gsd-rfkill should 
listen to "g-properties-changed" instead of "g-signal" now.

  [ Test Plan ]

   1. Find a machine which has WWAN card.
   2. Boot the machine, and run rfkill list to see if WWAN is unblocked. if not 
use rfkill to unblock the WWAN, and reboot.
   3. Press the wireless media key (Fn+F8) or turn on the airplane mode radio 
button in Settings.
   4. The airplane mode should be enabled, but actually not.

  [ Where problems could occur ]

   * When user is using a very low version network-manager (< 1.20) that
  still broadcasting DBUS "PropertiesChanged" events on "g-signal"
  instead of the concurrent "g-properties-changed", the airplane mode
  will sometimes not be able to enable.

  [1]: 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/853
  [2]: 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/6fb917178aa19c61e909957f5146aa4565e0cb2f

  [ Other Info ]

  1. About Ubuntu
  Description:Ubuntu 22.04.2 LTS
  Release:22.04
  Kernel: 6.1.0-1007-oem

  2. The version of packages:
  gnome-settings-daemon:
    Installed: 42.1-1ubuntu2.1

  network-manager:
    Installed: 1.36.6-0ubuntu2

  3. Expect:
  The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is called, and 
manager->wwan_enabled is set to the correct value.

  4. Actual:
  The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is never called, 
so manager->wwan_enabled is not synced, If machine has WWAN device(s), and the 
initial value of manager->wwan_enabled is true, it will never be able to switch 
to airplane mode.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2011770/+subscriptions


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

[Desktop-packages] [Bug 2011770] Re: [gsd-rfkill] WwanEnabled never get synced

2023-03-26 Thread Atlas Yu

Verified the new version of gnome-settings-daemon (42.1-1ubuntu2.2) on
jammy.

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/2011770

Title:
  [gsd-rfkill] WwanEnabled never get synced

Status in OEM Priority Project:
  Fix Committed
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Jammy:
  Fix Committed
Status in gnome-settings-daemon source package in Kinetic:
  Fix Committed

Bug description:
  [ Impact ]

   * Sometimes on devices with WWAN card, whenever user presses the
  wireless function key (Fn+F8) or turn on the airplane mode radio
  button in Settings, the airplane mode will not be enabled, and the
  airplane mode icon is not shown in the status bar.

   * There is a unmerged upstream merge request that delivers the fix:
  https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/-/merge_requests/310

  It works perfectly well on several Lenovo laptops with WWAN cards.
  The root causes is that the value of "WwanEnabled" under 
"org.freedesktop.NetworkManager" is not synced correctly, gsd-rfkill should 
listen to "g-properties-changed" instead of "g-signal" now.

  [ Test Plan ]

   1. Find a machine which has WWAN card.
   2. Boot the machine, and run rfkill list to see if WWAN is unblocked. if not 
use rfkill to unblock the WWAN, and reboot.
   3. Press the wireless media key (Fn+F8) or turn on the airplane mode radio 
button in Settings.
   4. The airplane mode should be enabled, but actually not.

  [ Where problems could occur ]

   * When user is using a very low version network-manager (< 1.20) that
  still broadcasting DBUS "PropertiesChanged" events on "g-signal"
  instead of the concurrent "g-properties-changed", the airplane mode
  will sometimes not be able to enable.

  [1]: 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/853
  [2]: 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/6fb917178aa19c61e909957f5146aa4565e0cb2f

  [ Other Info ]

  1. About Ubuntu
  Description:Ubuntu 22.04.2 LTS
  Release:22.04
  Kernel: 6.1.0-1007-oem

  2. The version of packages:
  gnome-settings-daemon:
    Installed: 42.1-1ubuntu2.1

  network-manager:
    Installed: 1.36.6-0ubuntu2

  3. Expect:
  The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is called, and 
manager->wwan_enabled is set to the correct value.

  4. Actual:
  The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is never called, 
so manager->wwan_enabled is not synced, If machine has WWAN device(s), and the 
initial value of manager->wwan_enabled is true, it will never be able to switch 
to airplane mode.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2011770/+subscriptions


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

[Desktop-packages] [Bug 2011770] Re: [gsd-rfkill] WwanEnabled never get synced

2023-03-25 Thread Atlas Yu

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/2011770

Title:
  [gsd-rfkill] WwanEnabled never get synced

Status in OEM Priority Project:
  Fix Committed
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Jammy:
  Fix Committed
Status in gnome-settings-daemon source package in Kinetic:
  Fix Committed

Bug description:
  [ Impact ]

   * Sometimes on devices with WWAN card, whenever user presses the
  wireless function key (Fn+F8) or turn on the airplane mode radio
  button in Settings, the airplane mode will not be enabled, and the
  airplane mode icon is not shown in the status bar.

   * There is a unmerged upstream merge request that delivers the fix:
  https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/-/merge_requests/310

  It works perfectly well on several Lenovo laptops with WWAN cards.
  The root causes is that the value of "WwanEnabled" under 
"org.freedesktop.NetworkManager" is not synced correctly, gsd-rfkill should 
listen to "g-properties-changed" instead of "g-signal" now.

  [ Test Plan ]

   1. Find a machine which has WWAN card.
   2. Boot the machine, and run rfkill list to see if WWAN is unblocked. if not 
use rfkill to unblock the WWAN, and reboot.
   3. Press the wireless media key (Fn+F8) or turn on the airplane mode radio 
button in Settings.
   4. The airplane mode should be enabled, but actually not.

  [ Where problems could occur ]

   * When user is using a very low version network-manager (< 1.20) that
  still broadcasting DBUS "PropertiesChanged" events on "g-signal"
  instead of the concurrent "g-properties-changed", the airplane mode
  will sometimes not be able to enable.

  [1]: 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/853
  [2]: 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/6fb917178aa19c61e909957f5146aa4565e0cb2f

  [ Other Info ]

  1. About Ubuntu
  Description:Ubuntu 22.04.2 LTS
  Release:22.04
  Kernel: 6.1.0-1007-oem

  2. The version of packages:
  gnome-settings-daemon:
    Installed: 42.1-1ubuntu2.1

  network-manager:
    Installed: 1.36.6-0ubuntu2

  3. Expect:
  The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is called, and 
manager->wwan_enabled is set to the correct value.

  4. Actual:
  The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is never called, 
so manager->wwan_enabled is not synced, If machine has WWAN device(s), and the 
initial value of manager->wwan_enabled is true, it will never be able to switch 
to airplane mode.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2011770/+subscriptions


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

[Desktop-packages] [Bug 2011770] Re: [gsd-rfkill] WwanEnabled never get synced

2023-03-21 Thread Atlas Yu

Thank you, Seb!

** Description changed:

  [ Impact ]
  
-  * Sometimes on devices with WWAN card, whenever user presses the
+  * Sometimes on devices with WWAN card, whenever user presses the
  wireless function key (Fn+F8) or turn on the airplane mode radio button
  in Settings, the airplane mode will not be enabled, and the airplane
  mode icon is not shown in the status bar.
  
-  * There is a unmerged upstream merge request that delivers the fix:
+  * There is a unmerged upstream merge request that delivers the fix:
  https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/-/merge_requests/310
  
  It works perfectly well on several Lenovo laptops with WWAN cards.
  The root causes is that the value of "WwanEnabled" under 
"org.freedesktop.NetworkManager" is not synced correctly, gsd-rfkill should 
listen to "g-properties-changed" instead of "g-signal" now.
  
  [ Test Plan ]
  
-  1. Find a machine which has WWAN card.
-  2. Boot the machine, and run rfkill list to see if WWAN is unblocked. if not 
use rfkill to unblock the WWAN, and reboot.
-  3. Press the wireless media key (Fn+F8) or turn on the airplane mode radio 
button in Settings.
-  4. The airplane mode should be enabled, but actually not.
+  1. Find a machine which has WWAN card.
+  2. Boot the machine, and run rfkill list to see if WWAN is unblocked. if not 
use rfkill to unblock the WWAN, and reboot.
+  3. Press the wireless media key (Fn+F8) or turn on the airplane mode radio 
button in Settings.
+  4. The airplane mode should be enabled, but actually not.
  
  [ Where problems could occur ]
  
-  * When user is using a very low version network-manager that still
+  * When user is using a very low version network-manager that still
  broadcasting DBUS "PropertiesChanged" events on "g-signal" instead of
  the concurrent "g-properties-changed", the airplane mode will sometimes
  not be able to enable.
+ 
+ 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/853#75fe48a78c4af7f7fb18988e15e27dcba51d0d06
  
  [ Other Info ]
  
  1. About Ubuntu
  Description:Ubuntu 22.04.2 LTS
  Release:22.04
  Kernel: 6.1.0-1007-oem
  
  2. The version of packages:
  gnome-settings-daemon:
    Installed: 42.1-1ubuntu2.1
  
  network-manager:
    Installed: 1.36.6-0ubuntu2
  
  3. Expect:
  The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is called, and 
manager->wwan_enabled is set to the correct value.
  
  4. Actual:
  The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is never called, 
so manager->wwan_enabled is not synced, If machine has WWAN device(s), and the 
initial value of manager->wwan_enabled is true, it will never be able to switch 
to airplane mode.

** Description changed:

  [ Impact ]
  
   * Sometimes on devices with WWAN card, whenever user presses the
  wireless function key (Fn+F8) or turn on the airplane mode radio button
  in Settings, the airplane mode will not be enabled, and the airplane
  mode icon is not shown in the status bar.
  
   * There is a unmerged upstream merge request that delivers the fix:
  https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/-/merge_requests/310
  
  It works perfectly well on several Lenovo laptops with WWAN cards.
  The root causes is that the value of "WwanEnabled" under 
"org.freedesktop.NetworkManager" is not synced correctly, gsd-rfkill should 
listen to "g-properties-changed" instead of "g-signal" now.
  
  [ Test Plan ]
  
   1. Find a machine which has WWAN card.
   2. Boot the machine, and run rfkill list to see if WWAN is unblocked. if not 
use rfkill to unblock the WWAN, and reboot.
   3. Press the wireless media key (Fn+F8) or turn on the airplane mode radio 
button in Settings.
   4. The airplane mode should be enabled, but actually not.
  
  [ Where problems could occur ]
  
-  * When user is using a very low version network-manager that still
- broadcasting DBUS "PropertiesChanged" events on "g-signal" instead of
- the concurrent "g-properties-changed", the airplane mode will sometimes
- not be able to enable.
+  * When user is using a very low version network-manager (< 1.20) that
+ still broadcasting DBUS "PropertiesChanged" events on "g-signal" instead
+ of the concurrent "g-properties-changed", the airplane mode will
+ sometimes not be able to enable.
  
- 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/853#75fe48a78c4af7f7fb18988e15e27dcba51d0d06
+ [1]: 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/853
+ [2]: 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/6fb917178aa19c61e909957f5146aa4565e0cb2f
  
  [ Other Info ]
  
  1. About Ubuntu
  Description:Ubuntu 22.04.2 LTS
  Release:22.04
  Kernel: 6.1.0-1007-oem
  
  2. The version of packages:
  gnome-settings-daemon:
    Installed: 42.1-1ubuntu2.1
  
  network-manager:
    Installed: 1.36.6-0ubuntu2
  
  3. Expect:
  The function nm_signal(plugins/rfkill/

[Desktop-packages] [Bug 2011770] Re: [gsd-rfkill] WwanEnabled never get synced

2023-03-16 Thread Atlas Yu

Here is a screen cast recording for better illustration.

** Description changed:

- The value of "WwanEnabled" under "org.freedesktop.NetworkManager" is not
- synced correctly, which will lead to a airplane mode switching failure
- when host has WWAN device(s).
+ [ Impact ]
  
- There is a MR on the upstream project, which can solve this bug.
- https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/merge_requests/310
+  * Sometimes on devices with WWAN card, whenever user presses the
+ wireless function key (Fn+F8) or turn on the airplane mode radio button
+ in Settings, the airplane mode will not be enabled, and the airplane
+ mode icon is not shown in the status bar.
  
- The description copied from the MR:
+  * There is a unmerged upstream merge request that delivers the fix:
+ https://gitlab.gnome.org/GNOME/gnome-settings-
+ daemon/-/merge_requests/310
  
- g-signal is not fired on property changes, so nm_signal is never called,
- and all changes of NetworkManager's WwanEnabled property are missed.
- That leads to an inability to disable the airplane mode on laptops with
- WWAN after the airplane mode was once enabled by button.
+ It works perfectly well on several Lenovo laptops with WWAN cards.
+ The root causes is that the value of "WwanEnabled" under 
"org.freedesktop.NetworkManager" is not synced correctly, gsd-rfkill should 
listen to "g-properties-changed" instead of "g-signal" now.
  
- Fix this by subscribing to g-properties-changed to actually listen to
- the updates of WwanEnabled. It also makes the code simpler.
+ [ Test Plan ]
  
- ==
+  1. Find a machine which has WWAN card.
+  2. Boot the machine, and run rfkill list to see if WWAN is unblocked. if not 
use rfkill to unblock the WWAN, and reboot.
+  3. Press the wireless media key (Fn+F8) or turn on the airplane mode radio 
button in Settings.
+  4. The airplane mode should be enabled, but actually not.
+ 
+ [ Where problems could occur ]
+ 
+  * When user is using a very low version network-manager that still
+ broadcasting DBUS "PropertiesChanged" events on "g-signal" instead of
+ the concurrent "g-properties-changed", the airplane mode will sometimes
+ not be able to enable.
+ 
+ [ Other Info ]
  
  1. About Ubuntu
  Description:Ubuntu 22.04.2 LTS
  Release:22.04
+ Kernel: 6.1.0-1007-oem
  
  2. The version of packages:
- 
  gnome-settings-daemon:
-   Installed: 42.1-1ubuntu2.1
+   Installed: 42.1-1ubuntu2.1
  
  network-manager:
-   Installed: 1.36.6-0ubuntu2
+   Installed: 1.36.6-0ubuntu2
  
  3. Expect:
  The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is called, and 
manager->wwan_enabled is set to the correct value.
  
  4. Actual:
  The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is never called, 
so manager->wwan_enabled is not synced, If machine has WWAN device(s), and the 
initial value of manager->wwan_enabled is true, it will never be able to switch 
to airplane mode.

** Attachment added: "cannot-enable-ariplane-mode.webm"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2011770/+attachment/5654814/+files/cannot-enable-ariplane-mode.webm

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/2011770

Title:
  [gsd-rfkill] WwanEnabled never get synced

Status in OEM Priority Project:
  Triaged
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  [ Impact ]

   * Sometimes on devices with WWAN card, whenever user presses the
  wireless function key (Fn+F8) or turn on the airplane mode radio
  button in Settings, the airplane mode will not be enabled, and the
  airplane mode icon is not shown in the status bar.

   * There is a unmerged upstream merge request that delivers the fix:
  https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/-/merge_requests/310

  It works perfectly well on several Lenovo laptops with WWAN cards.
  The root causes is that the value of "WwanEnabled" under 
"org.freedesktop.NetworkManager" is not synced correctly, gsd-rfkill should 
listen to "g-properties-changed" instead of "g-signal" now.

  [ Test Plan ]

   1. Find a machine which has WWAN card.
   2. Boot the machine, and run rfkill list to see if WWAN is unblocked. if not 
use rfkill to unblock the WWAN, and reboot.
   3. Press the wireless media key (Fn+F8) or turn on the airplane mode radio 
button in Settings.
   4. The airplane mode should be enabled, but actually not.

  [ Where problems could occur ]

   * When user is using a very low version network-manager that still
  broadcasting DBUS "PropertiesChanged" events on "g-signal" instead of
  the concurrent "g-properties-changed", the airplane mode will
  sometimes not be able to enable.

  [ Other Info ]

  1. About Ubuntu
  Description:Ubuntu 22.04.2 LTS
  Release:22.04
  Kernel: 6.1.0-1007-oem

  2. The version of p

[Desktop-packages] [Bug 2011770] Re: [gsd-rfkill] WwanEnabled never get synced

2023-03-16 Thread Atlas Yu

** Patch added: "rfkill-sync-wwan-enabled.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2011770/+attachment/5654804/+files/rfkill-sync-wwan-enabled.debdiff

** Patch removed: "sync-wwan-enabled.patch"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2011770/+attachment/5654775/+files/sync-wwan-enabled.patch

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/2011770

Title:
  [gsd-rfkill] WwanEnabled never get synced

Status in OEM Priority Project:
  Triaged
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  The value of "WwanEnabled" under "org.freedesktop.NetworkManager" is
  not synced correctly, which will lead to a airplane mode switching
  failure when host has WWAN device(s).

  There is a MR on the upstream project, which can solve this bug.
  https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/merge_requests/310

  The description copied from the MR:

  g-signal is not fired on property changes, so nm_signal is never
  called, and all changes of NetworkManager's WwanEnabled property are
  missed. That leads to an inability to disable the airplane mode on
  laptops with WWAN after the airplane mode was once enabled by button.

  Fix this by subscribing to g-properties-changed to actually listen to
  the updates of WwanEnabled. It also makes the code simpler.

  ==

  1. About Ubuntu
  Description:Ubuntu 22.04.2 LTS
  Release:22.04

  2. The version of packages:

  gnome-settings-daemon:
Installed: 42.1-1ubuntu2.1

  network-manager:
Installed: 1.36.6-0ubuntu2

  3. Expect:
  The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is called, and 
manager->wwan_enabled is set to the correct value.

  4. Actual:
  The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is never called, 
so manager->wwan_enabled is not synced, If machine has WWAN device(s), and the 
initial value of manager->wwan_enabled is true, it will never be able to switch 
to airplane mode.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2011770/+subscriptions


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

[Desktop-packages] [Bug 2011770] Re: [gsd-rfkill] WwanEnabled never get synced

2023-03-15 Thread Atlas Yu

The patch that applies the upstream MR!310.

** Patch added: "sync-wwan-enabled.patch"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2011770/+attachment/5654775/+files/sync-wwan-enabled.patch

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/2011770

Title:
  [gsd-rfkill] WwanEnabled never get synced

Status in OEM Priority Project:
  Triaged
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  The value of "WwanEnabled" under "org.freedesktop.NetworkManager" is
  not synced correctly, which will lead to a airplane mode switching
  failure when host has WWAN device(s).

  There is a MR on the upstream project, which can solve this bug.
  https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/merge_requests/310

  The description copied from the MR:

  g-signal is not fired on property changes, so nm_signal is never
  called, and all changes of NetworkManager's WwanEnabled property are
  missed. That leads to an inability to disable the airplane mode on
  laptops with WWAN after the airplane mode was once enabled by button.

  Fix this by subscribing to g-properties-changed to actually listen to
  the updates of WwanEnabled. It also makes the code simpler.

  ==

  1. About Ubuntu
  Description:Ubuntu 22.04.2 LTS
  Release:22.04

  2. The version of packages:

  gnome-settings-daemon:
Installed: 42.1-1ubuntu2.1

  network-manager:
Installed: 1.36.6-0ubuntu2

  3. Expect:
  The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is called, and 
manager->wwan_enabled is set to the correct value.

  4. Actual:
  The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is never called, 
so manager->wwan_enabled is not synced, If machine has WWAN device(s), and the 
initial value of manager->wwan_enabled is true, it will never be able to switch 
to airplane mode.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2011770/+subscriptions


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

[Desktop-packages] [Bug 2011770] [NEW] [gsd-rfkill] WwanEnabled never get synced

2023-03-15 Thread Atlas Yu

Public bug reported:

The value of "WwanEnabled" under "org.freedesktop.NetworkManager" is not
synced correctly, which will lead to a airplane mode switching failure
when host has WWAN device(s).

There is a MR on the upstream project, which can solve this bug.
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/merge_requests/310

The description copied from the MR:

g-signal is not fired on property changes, so nm_signal is never called,
and all changes of NetworkManager's WwanEnabled property are missed.
That leads to an inability to disable the airplane mode on laptops with
WWAN after the airplane mode was once enabled by button.

Fix this by subscribing to g-properties-changed to actually listen to
the updates of WwanEnabled. It also makes the code simpler.

==

1. About Ubuntu
Description:Ubuntu 22.04.2 LTS
Release:22.04

2. The version of packages:

gnome-settings-daemon:
  Installed: 42.1-1ubuntu2.1

network-manager:
  Installed: 1.36.6-0ubuntu2

3. Expect:
The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is called, and 
manager->wwan_enabled is set to the correct value.

4. Actual:
The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is never called, so 
manager->wwan_enabled is not synced, If machine has WWAN device(s), and the 
initial value of manager->wwan_enabled is true, it will never be able to switch 
to airplane mode.

** Affects: oem-priority
 Importance: Critical
 Assignee: Atlas Yu (pseudoc)
 Status: Triaged

** Affects: gnome-settings-daemon (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: oem-priority originate-from-2007638 sutton

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

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

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

** Changed in: oem-priority
 Assignee: (unassigned) => Atlas Yu (pseudoc)

** Tags added: oem-priority originate-from-2007638 sutton

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/2011770

Title:
  [gsd-rfkill] WwanEnabled never get synced

Status in OEM Priority Project:
  Triaged
Status in gnome-settings-daemon package in Ubuntu:
  New

Bug description:
  The value of "WwanEnabled" under "org.freedesktop.NetworkManager" is
  not synced correctly, which will lead to a airplane mode switching
  failure when host has WWAN device(s).

  There is a MR on the upstream project, which can solve this bug.
  https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/merge_requests/310

  The description copied from the MR:

  g-signal is not fired on property changes, so nm_signal is never
  called, and all changes of NetworkManager's WwanEnabled property are
  missed. That leads to an inability to disable the airplane mode on
  laptops with WWAN after the airplane mode was once enabled by button.

  Fix this by subscribing to g-properties-changed to actually listen to
  the updates of WwanEnabled. It also makes the code simpler.

  ==

  1. About Ubuntu
  Description:Ubuntu 22.04.2 LTS
  Release:22.04

  2. The version of packages:

  gnome-settings-daemon:
Installed: 42.1-1ubuntu2.1

  network-manager:
Installed: 1.36.6-0ubuntu2

  3. Expect:
  The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is called, and 
manager->wwan_enabled is set to the correct value.

  4. Actual:
  The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is never called, 
so manager->wwan_enabled is not synced, If machine has WWAN device(s), and the 
initial value of manager->wwan_enabled is true, it will never be able to switch 
to airplane mode.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2011770/+subscriptions


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

[Desktop-packages] [Bug 1942366] [NEW] PrintScreen button unresponsive after trying to take a window screenshot of a notification

2021-09-01 Thread Yu Yang Lin Hou

Public bug reported:

Steps to reproduce:
1. trigger a notification pop-up (e.g. ``notify-send Date "`date`"``)
2. mouse over the notification to bring it into focus
3. press `Alt`+`PrintScreen` to attempt to take a screenshot of the window in 
focus
4. nothing happens and the `PrintScreen` button becomes unresponsive

Nothing is logged and no crash reports are generated. The button simply
becomes unresponsive. Restarting Gnome (`Alt`+`F2` and typing
`r`restores the functionality of the `PrintScreen` button).

I am running Ubuntu 18.04.5 LTS.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-screenshot 3.25.0-0ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-81.91~18.04.1-generic 5.4.128
Uname: Linux 5.4.0-81-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.24
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep  1 20:03:23 2021
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
InstallationDate: Installed on 2020-03-28 (521 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
SourcePackage: gnome-screenshot
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-screenshot (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screenshot in Ubuntu.
https://bugs.launchpad.net/bugs/1942366

Title:
  PrintScreen button unresponsive after trying to take a window
  screenshot of a notification

Status in gnome-screenshot package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. trigger a notification pop-up (e.g. ``notify-send Date "`date`"``)
  2. mouse over the notification to bring it into focus
  3. press `Alt`+`PrintScreen` to attempt to take a screenshot of the window in 
focus
  4. nothing happens and the `PrintScreen` button becomes unresponsive

  Nothing is logged and no crash reports are generated. The button
  simply becomes unresponsive. Restarting Gnome (`Alt`+`F2` and typing
  `r`restores the functionality of the `PrintScreen` button).

  I am running Ubuntu 18.04.5 LTS.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-screenshot 3.25.0-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-81.91~18.04.1-generic 5.4.128
  Uname: Linux 5.4.0-81-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.24
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  1 20:03:23 2021
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  InstallationDate: Installed on 2020-03-28 (521 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  SourcePackage: gnome-screenshot
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1747646] Re: Authentication error with google drive

2019-03-09 Thread Yu Lou

System information:

* Ubuntu 18.10
* Linux 4.18.0-16-generic #17-Ubuntu SMP Fri Feb 8 00:06:57 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux
* duplicity 0.7.17-0ubuntu2
* deja-dup 38.0-1

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1747646

Title:
  Authentication error with google drive

Status in Déjà Dup:
  Confirmed
Status in Duplicity:
  Confirmed
Status in deja-dup package in Ubuntu:
  Triaged

Bug description:
  Hi,

  I'm having an issue using deja-dup to back up my laptop to my google
  drive.

  When backing only a small folder (eg: ~/Documents) every thing works fine.
  However when trying to backup my whole home folder (/home/myusername) I get 
an "Invalid credentials" error after 5-10 min.

  The back up seems to start normally and my destination folder starts
  filling with "duplicity-full...difftar.gz" files, but eventually I get
  the Invalid Credentials error.

  
  lsb_release -d
  Fedora release 27 (Twenty Seven)

  rpm -q deja-dup duplicity
  deja-dup-37.1-1.fc27.x86_64
  duplicity-0.7.16-1.fc27.x86_64

  deja-dup.log attached.
  I cannot attach deja-dup.gsettings since i can only join 1 file. Will send if 
needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1747646/+subscriptions

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

[Desktop-packages] [Bug 1747646] Re: Authentication error with google drive

2019-03-09 Thread Yu Lou

The bug affects me even after I log out and log in again:

Giving up after 5 attempts. Error: gdata-service-error-quark:
Authentication required: Unauthorized (4)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1747646

Title:
  Authentication error with google drive

Status in Déjà Dup:
  Confirmed
Status in Duplicity:
  Confirmed
Status in deja-dup package in Ubuntu:
  Triaged

Bug description:
  Hi,

  I'm having an issue using deja-dup to back up my laptop to my google
  drive.

  When backing only a small folder (eg: ~/Documents) every thing works fine.
  However when trying to backup my whole home folder (/home/myusername) I get 
an "Invalid credentials" error after 5-10 min.

  The back up seems to start normally and my destination folder starts
  filling with "duplicity-full...difftar.gz" files, but eventually I get
  the Invalid Credentials error.

  
  lsb_release -d
  Fedora release 27 (Twenty Seven)

  rpm -q deja-dup duplicity
  deja-dup-37.1-1.fc27.x86_64
  duplicity-0.7.16-1.fc27.x86_64

  deja-dup.log attached.
  I cannot attach deja-dup.gsettings since i can only join 1 file. Will send if 
needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1747646/+subscriptions

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

[Desktop-packages] [Bug 1296270] Re: Have to login twice after suspending

2018-02-13 Thread Yu Lou

Same issue after upgrading from Ubuntu Gnone 17.04 to Ubuntu 17.10.

First I purged gnome-screensaver, but it didn't work.

Then I went to Setting -> Privacy -> Screen Lock -> Automatic Screen
Lock and turned it off. Now the original Gnome lock screen went away and
only one lock screen is left.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/1296270

Title:
  Have to login twice after suspending

Status in gnome-screensaver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [ The bug ]
  After resuming from suspend, the screen is locked. I enter my password 
correctly and takes me to the screen I was at before suspending. Within 10 
seconds the screen is automatically locked and I have to re-enter my password 
to get it unlocked.

  [ How to reproduce this bug ]
  Suspend your machine. Wake it from suspend.

  
  [ Environment ]
  lsb_release -a

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04
  Codename: trusty

   apt-cache policy linux-generic
  linux-generic:
Installed: 3.13.0.18.22
Candidate: 3.13.0.19.23
Version table:
   3.13.0.19.23 0
  500 http://in.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
   *** 3.13.0.18.22 0
  100 /var/lib/dpkg/status
  --- 
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jobin  2887 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=755cc019-dd1c-4b7d-a70c-bbaaa6aa03c9
  InstallationDate: Installed on 2014-03-17 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140316)
  MachineType: Hewlett-Packard HP 630 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-19-generic 
root=UUID=e65dde38-8db3-4375-af07-da5265597b0a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-19-generic N/A
   linux-backports-modules-3.13.0-19-generic  N/A
   linux-firmware 1.126
  Tags:  trusty
  Uname: Linux 3.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 07/22/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1A
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3672
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 23.24
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1A:bd07/22/2011:svnHewlett-Packard:pnHP630NotebookPC:pvr058A10004C1000260:rvnHewlett-Packard:rn3672:rvr23.24:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 630 Notebook PC
  dmi.product.version: 058A10004C1000260
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1502978] Re: fglrx-core 2:15.201-0ubuntu1: fglrx-core kernel module failed to build against kernel 4.3 [firegl_public.c:... error: void value not ignored as it ought to be ...

2017-08-12 Thread Yu

I got this bug while plugging in my HDMI cable, screen was hanging
(super lag, it seems like the GPU rendering error). It works fine with
VGA interface.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1502978

Title:
  fglrx-core 2:15.201-0ubuntu1: fglrx-core kernel module failed to build
  against kernel 4.3 [firegl_public.c:... error: void value not ignored
  as it ought to be ... seq_printf]

Status in fglrx-installer package in Ubuntu:
  Invalid
Status in fglrx-installer-updates package in Ubuntu:
  Invalid
Status in software-properties package in Ubuntu:
  Invalid
Status in fglrx-installer source package in Trusty:
  New
Status in fglrx-installer-updates source package in Trusty:
  New
Status in software-properties source package in Trusty:
  Triaged

Bug description:
  Probably fglrx-installer. 
  However I am not using fglrx , I am using xserver-xorg-video-ati and 
xserver-xorg-video-amdgpu.
  This happened when I installed kernel 4.3.0-040300rc4 in Ubuntu Wily Werewolf.
  Graphic card Radeon R9 380

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: fglrx-core 2:15.201-0ubuntu1
  Uname: Linux 4.3.0-040300rc4-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DKMSKernelVersion: 4.3.0-040300rc4-generic
  Date: Mon Oct  5 18:33:50 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: fglrx-core, 15.201, 4.2.0-14-generic, x86_64: installed
  DuplicateSignature: 
dkms:fglrx-core:2:15.201-0ubuntu1:/var/lib/dkms/fglrx-core/15.201/build/2.6.x/firegl_public.c:639:9:
 error: void value not ignored as it ought to be
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tonga PRO [Radeon R9 285/380] 
[1002:6939] (rev f1) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:2015]
  InstallationDate: Installed on 2015-02-01 (246 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150130)
  MachineType: Gigabyte Technology Co., Ltd. GA-MA770-UD3
  PackageVersion: 2:15.201-0ubuntu1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-040300rc4-generic 
root=UUID=494a814f-1825-4bfc-941f-1d7ee79111d1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu4
   apt  1.0.9.10ubuntu7
  SourcePackage: fglrx-installer
  Title: fglrx-core 2:15.201-0ubuntu1: fglrx-core kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FA
  dmi.board.name: GA-MA770-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/09/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA770-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA770-UD3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA770-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.2+15.10.20151002-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Mon Oct  5 18:37:05 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9
  xserver.video_driver: amdgpu

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

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

[Desktop-packages] [Bug 1692300] [NEW] [H61M-DS2 REV 1.2, Realtek ALC887-VD, Green Line Out, Rear] No sound at all

2017-05-21 Thread Nicholas Yu

Public bug reported:

Fresh install ubuntu but no sound.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-52-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  yuyy   1632 F pulseaudio
 /dev/snd/pcmC0D0p:   yuyy   1632 F...m pulseaudio
 /dev/snd/controlC0:  yuyy   1632 F pulseaudio
CurrentDesktop: Unity
Date: Sun May 21 16:55:34 2017
InstallationDate: Installed on 2017-05-20 (1 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=zh_CN:zh
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=zh_CN.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: 内置音频 - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  yuyy   1632 F pulseaudio
 /dev/snd/pcmC0D0p:   yuyy   1632 F...m pulseaudio
 /dev/snd/controlC0:  yuyy   1632 F pulseaudio
  yuyy  14846 F alsamixer
Symptom_Jack: Green Line Out, Rear
Symptom_Type: No sound at all
Title: [H61M-DS2 REV 1.2, Realtek ALC887-VD, Green Line Out, Rear] No sound at 
all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/12/2011
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: FB
dmi.board.name: H61M-DS2 REV 1.2
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd10/12/2011:svnGigabyteTechnologyCo.,Ltd.:pnH61M-DS2REV1.2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-DS2REV1.2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: H61M-DS2 REV 1.2
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  [H61M-DS2 REV 1.2, Realtek ALC887-VD, Green Line Out, Rear] No sound
  at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Fresh install ubuntu but no sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yuyy   1632 F pulseaudio
   /dev/snd/pcmC0D0p:   yuyy   1632 F...m pulseaudio
   /dev/snd/controlC0:  yuyy   1632 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun May 21 16:55:34 2017
  InstallationDate: Installed on 2017-05-20 (1 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=zh_CN:zh
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=zh_CN.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: 内置音频 - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yuyy   1632 F pulseaudio
   /dev/snd/pcmC0D0p:   yuyy   1632 F...m pulseaudio
   /dev/snd/controlC0:  yuyy   1632 F pulseaudio
yuyy  14846 F alsamixer
  Symptom_Jack: Green Line Out, Rear
  Symptom_Type: No sound at all
  Title: [H61M-DS2 REV 1.2, Realtek ALC887-VD, Green Line Out, Rear] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FB
  dmi.board.name: H61M-DS2 REV 1.2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd10/12/2011:svnGigabyteTechnologyCo.,Ltd.:pnH61M-DS2REV1.2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-DS2REV1.2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: H61M-DS2 REV 1.2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1639699] Re: network-manager Down after Laptop Suspend mode

2016-12-27 Thread Yowu Yu

before suspend
ps -ef | grep wpa_supplicant  
root  1054 1  0 15:29 ?00:00:00 /sbin/wpa_supplicant -u -s -O 
/run/wpa_supplicant
uyu423   13023 12933  0 16:41 pts/000:00:00 grep --color=auto 
--exclude-dir=.bzr --exclude-dir=CVS --exclude-dir=.git --exclude-dir=.hg 
--exclude-dir=.svn wpa_supplicant

after resume
ps -ef | grep wpa_supplicant  
root  1054 1  0 15:29 ?00:00:00 /sbin/wpa_supplicant -u -s -O 
/run/wpa_supplicant
uyu423   13884 12933  0 16:42 pts/000:00:00 grep --color=auto 
--exclude-dir=.bzr --exclude-dir=CVS --exclude-dir=.git --exclude-dir=.hg 
--exclude-dir=.svn wpa_supplicant

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

Title:
  network-manager Down after Laptop Suspend mode

Status in Ubuntu GNOME:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  I installed Ubuntu Gnome 16.10 in Dell XPS-13 (9350)

  network-manager does not function properly when latop re-opened.(can't
  use network. but IP address is still allocated.) After executing the
  following command, the network runs again. "sudo service network-
  manager restart"

  $ lspci
  00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers 
(rev 08)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07)
  00:04.0 Signal processing controller: Intel Corporation Skylake Processor 
Thermal Subsystem (rev 08)
  00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller (rev 21)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Thermal subsystem (rev 21)
  00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #0 (rev 21)
  00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #1 (rev 21)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME 
HECI #1 (rev 21)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller 
[AHCI mode] (rev 21)
  00:1c.0 PCI bridge: Intel Corporation Device 9d10 (rev f1)
  00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#5 (rev f1)
  00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#6 (rev f1)
  00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#9 (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
  00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
  3a:00.0 Network controller: Broadcom Limited BCM4350 802.11ac Wireless 
Network Adapter (rev 08)
  3b:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI 
Express Card Reader (rev 01)
  3c:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller (rev 01)

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

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

[Desktop-packages] [Bug 1639699] Re: network-manager Down after Laptop Suspend mode

2016-12-27 Thread Yowu Yu

It seems that this issue has been resolved a few days ago.

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

Title:
  network-manager Down after Laptop Suspend mode

Status in Ubuntu GNOME:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  I installed Ubuntu Gnome 16.10 in Dell XPS-13 (9350)

  network-manager does not function properly when latop re-opened.(can't
  use network. but IP address is still allocated.) After executing the
  following command, the network runs again. "sudo service network-
  manager restart"

  $ lspci
  00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers 
(rev 08)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07)
  00:04.0 Signal processing controller: Intel Corporation Skylake Processor 
Thermal Subsystem (rev 08)
  00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller (rev 21)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Thermal subsystem (rev 21)
  00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #0 (rev 21)
  00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #1 (rev 21)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME 
HECI #1 (rev 21)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller 
[AHCI mode] (rev 21)
  00:1c.0 PCI bridge: Intel Corporation Device 9d10 (rev f1)
  00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#5 (rev f1)
  00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#6 (rev f1)
  00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#9 (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
  00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
  3a:00.0 Network controller: Broadcom Limited BCM4350 802.11ac Wireless 
Network Adapter (rev 08)
  3b:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI 
Express Card Reader (rev 01)
  3c:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller (rev 01)

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

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

[Desktop-packages] [Bug 1645241] Re: Information bar hard to see when focus is lost

2016-11-28 Thread Yu Lou

** Project changed: ubuntu-gnome => nautilus (Ubuntu)

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

Title:
  Information bar hard to see when focus is lost

Status in nautilus package in Ubuntu:
  New

Bug description:
  Information bar in Nautilus will be transparent if the focus is lost.
  This will make texts on it hard to see if the information bar overlaps
  with a file icon.

  How to reproduce:

  Open Nautilus, select a file, scroll the window so that a file icon is
  overlapped by the information , then click another window.

  I've included a screenshot showing what will happen.

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

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

[Desktop-packages] [Bug 1639699] Re: network-manager Down after Laptop Suspend mode

2016-11-06 Thread Yowu Yu

$ dmesg (After executing 'sudo service network-manager restart')

[ 6123.662754] IPv6: ADDRCONF(NETDEV_CHANGE): wlp58s0: link becomes ready
[ 6171.294759] xhci_hcd :00:14.0: xHC is not running.
[ 6174.234416] brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 0x30)
[ 6174.604156] IPv6: ADDRCONF(NETDEV_UP): wlp58s0: link is not ready
[ 6174.779951] IPv6: ADDRCONF(NETDEV_UP): wlp58s0: link is not ready
[ 6183.668692] IPv6: ADDRCONF(NETDEV_CHANGE): wlp58s0: link becomes ready
[ 6192.098950] xhci_hcd :00:14.0: Port resume took longer than 2 msec, 
port status = 0x400603

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

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

Title:
  network-manager Down after Laptop Suspend mode

Status in Ubuntu GNOME:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  I installed Ubuntu Gnome 16.10 in Dell XPS-13 (9350)

  network-manager does not function properly when latop re-opened.(can't
  use network. but IP address is still allocated.) After executing the
  following command, the network runs again. "sudo service network-
  manager restart"

  $ lspci
  00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers 
(rev 08)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07)
  00:04.0 Signal processing controller: Intel Corporation Skylake Processor 
Thermal Subsystem (rev 08)
  00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller (rev 21)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Thermal subsystem (rev 21)
  00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #0 (rev 21)
  00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #1 (rev 21)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME 
HECI #1 (rev 21)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller 
[AHCI mode] (rev 21)
  00:1c.0 PCI bridge: Intel Corporation Device 9d10 (rev f1)
  00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#5 (rev f1)
  00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#6 (rev f1)
  00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#9 (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
  00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
  3a:00.0 Network controller: Broadcom Limited BCM4350 802.11ac Wireless 
Network Adapter (rev 08)
  3b:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI 
Express Card Reader (rev 01)
  3c:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller (rev 01)

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

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

[Desktop-packages] [Bug 1574347] Re: [SRU] Re-read the link type if the name changed

2016-09-20 Thread Yiyao Yu

More info:
network-manger version: 1.2.0-0ubuntu0.16.04.3
Caused by:
Disabling/Enabling Network via GUI (Blank icon)
Sleep/Hibernate (Ethernet icon)

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

Title:
  [SRU] Re-read the link type if the name changed

Status in NetworkManager:
  Fix Released
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

Bug description:
  [Impact]
  NM needs to re-read the DEVTYPE after the device name changed, an example is 
that WiFi network list disappears from network manager applet

  [Testcase]
  1. Boot the system. It should include a wireless device.
  2. In a terminal, run 'nmcli dev'.
  3. In the correct case, the line for the wireless device should read "wifi" 
under the TYPE column. In a failure case, it will read "ethernet".

  After upgrading to the new version, the repeating the above steps
  should give expected behavior.

  [Regression Potential]
  Potential of causing regression is relatively small for a one line change to 
re-read a value to be known.

  ---

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1574347/+subscriptions

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

[Desktop-packages] [Bug 1574347] Re: [SRU] Re-read the link type if the name changed

2016-09-20 Thread Yiyao Yu

Still happening on Dell XPS 14 l421x with Intel Corporation Centrino
Advanced-N 6235 (rev 24). Already running network-manager 1.2.0. It
seems that the network manager applet wifi icon changes back to the
ethernet icon every time the system wakes from sleep.

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

Title:
  [SRU] Re-read the link type if the name changed

Status in NetworkManager:
  Fix Released
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

Bug description:
  [Impact]
  NM needs to re-read the DEVTYPE after the device name changed, an example is 
that WiFi network list disappears from network manager applet

  [Testcase]
  1. Boot the system. It should include a wireless device.
  2. In a terminal, run 'nmcli dev'.
  3. In the correct case, the line for the wireless device should read "wifi" 
under the TYPE column. In a failure case, it will read "ethernet".

  After upgrading to the new version, the repeating the above steps
  should give expected behavior.

  [Regression Potential]
  Potential of causing regression is relatively small for a one line change to 
re-read a value to be known.

  ---

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1574347/+subscriptions

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

[Desktop-packages] [Bug 1554303] Re: xinit can't start

2016-03-07 Thread Qiang Yu

** Description changed:

  xinit can't start from command line while startx and lightdm is OK.
  
  Reproduce:
  1. setup to boot into command line by
  $ sudo systemctl set-default multi-user.target
  2. reboot into command line
  3. login and tart xinit by
  $ xinit
  
+ The error log is
+ [   237.119] (EE) xf86OpenConsole: Cannot open /dev/tty0 (No such file or 
directory)
+ 
+ But this way the xinit is OK
+ xinit -- /usr/bin/X :0 vt1 -nolisten
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xinit 1.3.4-3
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  .tmp.unity.support.test.0:
-  
+ 
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Mar  8 09:57:43 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
-  Advanced Micro Devices, Inc. [AMD/ATI] Hawaii XT [Radeon R9 290X] 
[1002:67b0] (prog-if 00 [VGA controller])
-Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii XT [Radeon R9 
290X] [1002:0b00]
+  Advanced Micro Devices, Inc. [AMD/ATI] Hawaii XT [Radeon R9 290X] 
[1002:67b0] (prog-if 00 [VGA controller])
+    Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii XT [Radeon R9 
290X] [1002:0b00]
  InstallationDate: Installed on 2016-03-01 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160228)
  MachineType: Gigabyte Technology Co., Ltd. X58A-UD3R
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic 
root=UUID=c137e0c1-ad99-47f4-acf5-e7f4792afa9e ro quiet splash vt.handoff=7
  SourcePackage: xinit
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FE
  dmi.board.name: X58A-UD3R
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFE:bd12/23/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD3R:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: X58A-UD3R
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.2+16.04.20160209-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build1
  xserver.bootTime: Tue Mar  8 09:46:59 2016
  xserver.configfile: default
  xserver.errors: systemd-logind: failed to get session: PID 893 does not 
belong to any known session
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.3-2ubuntu4
  xserver.video_driver: radeon

** Attachment removed: "XorgLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xinit/+bug/1554303/+attachment/4592137/+files/XorgLog.txt

** Attachment removed: "XorgLogOld.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xinit/+bug/1554303/+attachment/4592138/+files/XorgLogOld.txt

** Attachment added: "log when xinit fail"
   
https://bugs.launchpad.net/ubuntu/+source/xinit/+bug/1554303/+attachment/4592153/+files/Xorg.0.log

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

Title:
  xinit can't start

Status in xinit package in Ubuntu:
  New

Bug description:
  xinit can't start from command line while startx and lightdm is OK.

  Reproduce:
  1. setup to boot into command line by
  $ sudo systemctl set-default multi-user.target
  2. reboot into command line
  3. login and tart xinit by
  $ xinit

  The error log is
  [   237.119] (EE) xf86OpenConsole: Cannot open /dev/tty0 (No such file or 
directory)

  But this way the xinit is OK
  xinit -- /usr/bin/X :0 vt1 -nolisten

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xinit 1.3.4-3
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlack

[Desktop-packages] [Bug 1554303] [NEW] xinit can't start

2016-03-07 Thread Qiang Yu

Public bug reported:

xinit can't start from command line while startx and lightdm is OK.

Reproduce:
1. setup to boot into command line by
$ sudo systemctl set-default multi-user.target
2. reboot into command line
3. login and tart xinit by
$ xinit

The error log is
[   237.119] (EE) xf86OpenConsole: Cannot open /dev/tty0 (No such file or 
directory)

But this way the xinit is OK
xinit -- /usr/bin/X :0 vt1 -nolisten

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xinit 1.3.4-3
ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
Uname: Linux 4.4.0-8-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Tue Mar  8 09:57:43 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Hawaii XT [Radeon R9 290X] [1002:67b0] 
(prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii XT [Radeon R9 290X] 
[1002:0b00]
InstallationDate: Installed on 2016-03-01 (6 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160228)
MachineType: Gigabyte Technology Co., Ltd. X58A-UD3R
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic 
root=UUID=c137e0c1-ad99-47f4-acf5-e7f4792afa9e ro quiet splash vt.handoff=7
SourcePackage: xinit
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/23/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: FE
dmi.board.name: X58A-UD3R
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFE:bd12/23/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD3R:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: X58A-UD3R
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.12.2+16.04.20160209-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build1
xserver.bootTime: Tue Mar  8 09:46:59 2016
xserver.configfile: default
xserver.errors: systemd-logind: failed to get session: PID 893 does not belong 
to any known session
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.3-2ubuntu4
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  xinit can't start

Status in xinit package in Ubuntu:
  New

Bug description:
  xinit can't start from command line while startx and lightdm is OK.

  Reproduce:
  1. setup to boot into command line by
  $ sudo systemctl set-default multi-user.target
  2. reboot into command line
  3. login and tart xinit by
  $ xinit

  The error log is
  [   237.119] (EE) xf86OpenConsole: Cannot open /dev/tty0 (No such file or 
directory)

  But this way the xinit is OK
  xinit -- /usr/bin/X :0 vt1 -nolisten

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xinit 1.3.4-3
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Mar  8 09:57:43 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Hawaii XT [Radeon R9 290X] 
[1002:67b0] (prog-if 00 [VGA controller])
     Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii XT [Radeon R9 
290X] [1002:0b00]
  InstallationDate: Installed on 2016-03-01 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160228)
  MachineType: Gigabyte Technology Co., Ltd. X58A-UD3R
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.

[Desktop-packages] [Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported

2015-12-21 Thread Keng-Yu Lin

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

** Changed in: network-manager (Ubuntu)
   Importance: High => Undecided

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

Title:
  Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported

Status in HWE Next:
  Fix Released
Status in HWE Next wily series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in linux source package in Wily:
  Fix Released
Status in linux-firmware source package in Wily:
  Fix Released
Status in network-manager source package in Wily:
  Confirmed

Bug description:
  =

  CURRENT STATUS:

  Wily(15.10) could not work with and don't need Adam's dkms package 1.0
  or 1.1

  Wily(15.10) has already fixed the driver part, and the firmware part
  is in progress.

  For now, you guys could use 15.10(purge the ath10k-dkms if you tried
  installing it), and make a copy of
  https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-
  firmware.git/plain/ath10k/QCA6174 into /lib/firmware/ath10k/

  15.10 will work in a week by a simple `apt upgrade`

  Distros before 15.10(lower than 4.2 kernel) please keep using the
  dkms(which will be relocated soon)

  =

  Card detail: Qualcomm Atheros Device [168c:003e] (rev 20)
  Subsystem: Bigfoot Networks, Inc. Device [1a56:1525]

  This is on a fully updated Ubuntu Server 14.04 installation, with the 
ubuntu-desktop environment installed. This happened in order to get the md raid 
drivers for raid0 on my system, as the desktop version doesn't support them.
  ---
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  matanis2333 F pulseaudio
   /dev/snd/controlC0:  matanis2333 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6
  InstallationDate: Installed on 2014-10-16 (3 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
   p2p1  no wireless extensions.

   lono wireless extensions.
  MachineType: Micro-Star International Co., Ltd. GT72 2QE
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed 
root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:

  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1781IMS.10D
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1781
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.C
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: GT72 2QE
  dmi.product.version: REV:0.C
  dmi.sys.vendor: Micro-Star International Co., Ltd.

  Qualcomm Atheros Device [168c:003e] (rev 20)

  mainline commit d63955b33b3bee45d784ffdfafeb93076c765660

  [6.221281] ath10k_pci :02:00.0: pci irq msi interrupts 1 irq_mode 0 
reset_mode 0
  [6.417386] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/cal-pci-:02:00.0.bin failed with error -2
  [6.417404] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/QCA6174/hw2.1/board-pci-168c:003e:17aa:3044.bin failed with error -2
  [6.417407] ath10k_pci :02:00.0: failed to load spec board file, 
falling back to generic: -2
  [6.417416] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/QCA6174/hw2.1/board.bin failed with error -2
  [6.417418] ath10k_pci :02:00.0: failed to fetch generic board data: -2
  [6.417420] ath10k_pci :02:00.0: failed to fetch board file: -2
  [6.417421] ath10k_pci :02:00.0: could not fetch firmware files (-2)
  [6.417423] ath10k_pci 00

[Desktop-packages] [Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported

2015-12-21 Thread Keng-Yu Lin

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

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

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

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

Title:
  Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported

Status in HWE Next:
  Fix Released
Status in HWE Next wily series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in linux source package in Wily:
  Fix Released
Status in linux-firmware source package in Wily:
  Fix Released
Status in network-manager source package in Wily:
  Confirmed

Bug description:
  =

  CURRENT STATUS:

  Wily(15.10) could not work with and don't need Adam's dkms package 1.0
  or 1.1

  Wily(15.10) has already fixed the driver part, and the firmware part
  is in progress.

  For now, you guys could use 15.10(purge the ath10k-dkms if you tried
  installing it), and make a copy of
  https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-
  firmware.git/plain/ath10k/QCA6174 into /lib/firmware/ath10k/

  15.10 will work in a week by a simple `apt upgrade`

  Distros before 15.10(lower than 4.2 kernel) please keep using the
  dkms(which will be relocated soon)

  =

  Card detail: Qualcomm Atheros Device [168c:003e] (rev 20)
  Subsystem: Bigfoot Networks, Inc. Device [1a56:1525]

  This is on a fully updated Ubuntu Server 14.04 installation, with the 
ubuntu-desktop environment installed. This happened in order to get the md raid 
drivers for raid0 on my system, as the desktop version doesn't support them.
  ---
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  matanis2333 F pulseaudio
   /dev/snd/controlC0:  matanis2333 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6
  InstallationDate: Installed on 2014-10-16 (3 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
   p2p1  no wireless extensions.

   lono wireless extensions.
  MachineType: Micro-Star International Co., Ltd. GT72 2QE
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed 
root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:

  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1781IMS.10D
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1781
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.C
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: GT72 2QE
  dmi.product.version: REV:0.C
  dmi.sys.vendor: Micro-Star International Co., Ltd.

  Qualcomm Atheros Device [168c:003e] (rev 20)

  mainline commit d63955b33b3bee45d784ffdfafeb93076c765660

  [6.221281] ath10k_pci :02:00.0: pci irq msi interrupts 1 irq_mode 0 
reset_mode 0
  [6.417386] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/cal-pci-:02:00.0.bin failed with error -2
  [6.417404] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/QCA6174/hw2.1/board-pci-168c:003e:17aa:3044.bin failed with error -2
  [6.417407] ath10k_pci :02:00.0: failed to load spec board file, 
falling back to generic: -2
  [6.417416] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/QCA6174/hw2.1/board.bin failed with error -2
  [6.417418] ath10k_pci :02:00.0: failed to fetch generic board data: -2
  [6.417420] ath10k_pci :02:00.0: failed to fetch board file: -2
  [6.417421] ath10k_p

[Desktop-packages] [Bug 1505705] Re: [sound] Subwoofer slider works in mysterious ways

2015-11-09 Thread Keng-Yu Lin

** Changed in: hwe-next
   Importance: Undecided => Low

** Changed in: hwe-next
   Status: New => Triaged

** Changed in: hwe-next
 Assignee: (unassigned) => David Henningsson (diwic)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1505705

Title:
  [sound] Subwoofer slider works in mysterious ways

Status in HWE Next:
  Triaged
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in unity-control-center package in Ubuntu:
  Triaged

Bug description:
  Sometimes it follows master volume and sometimes it doesn't.

  Same as:
  https://bugzilla.gnome.org/show_bug.cgi?id=753847

  Also raised by OEM team.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1505705/+subscriptions

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

[Desktop-packages] [Bug 1506107] Re: Bad webcam video rendering when using XV acceleration on Skylake gpus.

2015-11-09 Thread Keng-Yu Lin

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1506107

Title:
  Bad webcam video rendering when using XV acceleration on Skylake gpus.

Status in HWE Next:
  Fix Released
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-intel-lts-vivid package in Ubuntu:
  New
Status in xserver-xorg-video-intel source package in Trusty:
  Invalid
Status in xserver-xorg-video-intel-lts-vivid source package in Trusty:
  In Progress
Status in xserver-xorg-video-intel source package in Vivid:
  In Progress
Status in xserver-xorg-video-intel-lts-vivid source package in Vivid:
  Invalid

Bug description:
  CPU: Intel(R) Core(TM) i3-6100U CPU @ 2.30GHz
  GPU: Intel Corporation Device [8086:1916] (rev 07)
  Webcam: 0bda:57e3 Realtek Semiconductor Corp.

  [Impact] 
  We noticed that webcam output on a wide range of skylake systems contained 
corruption during certification testing of OEM machines which uses a certain 
gstreamer pipeline. An example of the corruption is attached.

  [Test Case]
  1. Boot ubuntu 14.04.3 or 15.04 on a machine with a skylake intel GPU and a 
webcam
  2. Login system and open a terminal.
  4. Execute '$ gst-launch-0.10 v4l2src ! xvimagesink'

  Expect result:
  There should be no visual artifacts during video playing.  The artifacts will 
look like the attached video and be very obvious in the unfixed package.

  [Regression Potential] 
  Low, the fix is very minimal was included immediately after the 2.99.917 
release was made. It consists of 2 parts, a small patch 
(http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=cc9d7f603037d0d7eff346dd350f4d8b3f31)
 and a configure option change. The configure option change was in lieu of 
http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=986cb2335c30792e24a7e2b930ecaa3fa051809a
 which flipped it on unconditionally and only affects i915_bpo in both of these 
releases as it requires a 4.0 or newer kernel (i915_bpo is a backport of i915 
from 4.2 that is only used on skylake). Both of these changes are already in 
wily's xserver-xorg-video-intel.

  It has been tested on a large number of machines during certification,
  and also by me on sandybridge, ivybridge, broadwell and skylake
  machines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1506107/+subscriptions

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

[Desktop-packages] [Bug 1509182] Re: AMD [1002:6606][1002:6821] with fglrx 2:15.200-0ubuntu0.5 does not work well with GStreamer autovideosink plugin

2015-10-27 Thread Keng-Yu Lin

** Changed in: fglrx-installer (Ubuntu)
 Assignee: Keng-Yu Lin (lexical) => Alberto Milone (albertomilone)

** Changed in: hwe-next
   Importance: Undecided => Medium

** Changed in: hwe-next
 Assignee: (unassigned) => Alberto Milone (albertomilone)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1509182

Title:
  AMD [1002:6606][1002:6821] with fglrx 2:15.200-0ubuntu0.5 does not
  work well with GStreamer autovideosink plugin

Status in HWE Next:
  New
Status in fglrx-installer package in Ubuntu:
  New

Bug description:
  CID: 201404-14986 Dell Precision M2800

  On this I+A (AMD/ATI Mars XTX [Radeon HD 8790M] [1002:6606]) system,
  the GStreamer autovideosink plugin does not work well with the
  proprietary fglrx driver (version 2:15.200-0ubuntu0.5)

  Steps:
  1. Install 14.04.3 + upgrade (3.19.0-30) + fglrx + Checkbox test suite
  2. Run  "gst-launch-1.0 videotestsrc ! videoconvert ! autovideosink"
  3. Run "gst-launch-1.0 videotestsrc ! videoconvert ! ximagesink"

  Expected result:
  * A "Bar and static" video test screen will pop up.

  Actual result:
  * Only the command in step 3 will work, the command in step 2 does not, it 
will cause X to crash for sometimes, error log could be found:
  [  1494.011] (EE) 
  [  1494.011] (EE) Backtrace:
  [  1494.012] (EE) 0: /usr/bin/X (xorg_backtrace+0x48) [0x7f6b10f1af08]
  [  1494.012] (EE) 1: /usr/bin/X (0x7f6b10d7a000+0x1a4f39) [0x7f6b10f1ef39]
  [  1494.012] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f6b0eefa000+0x36d40) 
[0x7f6b0ef30d40]
  [  1494.012] (EE) 3: /usr/bin/X (0x7f6b10d7a000+0xa9921) [0x7f6b10e23921]
  [  1494.012] (EE) 4: /usr/bin/X (0x7f6b10d7a000+0xaa7db) [0x7f6b10e247db]
  [  1494.012] (EE) 5: /usr/bin/X (0x7f6b10d7a000+0xf0d30) [0x7f6b10e6ad30]
  [  1494.012] (EE) 6: /usr/bin/X (0x7f6b10d7a000+0x5414e) [0x7f6b10dce14e]
  [  1494.012] (EE) 7: /usr/bin/X (0x7f6b10d7a000+0x57f9b) [0x7f6b10dd1f9b]
  [  1494.012] (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) 
[0x7f6b0ef1bec5]
  [  1494.012] (EE) 9: /usr/bin/X (0x7f6b10d7a000+0x4352e) [0x7f6b10dbd52e]
  [  1494.012] (EE) 
  [  1494.013] (EE) Segmentation fault at address 0x1009c9cbc
  [  1494.013] (EE) 
  Fatal server error:
  [  1494.013] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [  1494.013] (EE) 
  [  1494.013] (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  [  1494.013] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
  [  1494.013] (EE) 
  [  1494.013] (II) AIGLX: Suspending AIGLX clients for VT switch
  [  1494.014] (II) fglrx(0): Backup framebuffer data.
  [  1494.077] (II) fglrx(0): Backup complete.
  [  1494.093] (EE) Server terminated with error (1). Closing log file.

  Verified with the latest AMD driver(15.9, fglrx version:
  15.201-0ubuntu1)[1], this issue does not exist with it.

  As this issue will cause the camera display test and video test to
  crash (whitelist test cases), I will mark this bug as a blocker.

  [1] http://support.amd.com/en-us/download/desktop?os=Linux+x86

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: fglrx 2:15.200-0ubuntu0.5
  ProcVersionSignature: Ubuntu 3.19.0-30.34~14.04.1-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Oct 22 23:54:16 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx-core, 15.200, 3.19.0-30-generic, x86_64: installed
   fwts-efi-runtime-dkms, 15.09.00, 3.19.0-25-generic, x86_64: installed
   fwts-efi-runtime-dkms, 15.09.00, 3.19.0-30-generic, x86_64: installed
   tp-smapi, 0.41, 3.19.0-25-generic, x86_64: installed
   tp-smapi, 0.41, 3.19.0-30-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0684]
   Advanced Micro Devices, Inc. [AMD/ATI] Mars XTX [Radeon HD 8790M] 
[1002:6606] (prog-if 00 [VGA controller])
 Subsystem: Dell FirePro W4170M [1028:0684]
  InstallationDate: Installed on 2015-10-12 (11 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Dell Inc. Precision M2800
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic 
root=UUID=25743653-47a5-417f-8dcb-abd5233bd68e ro quiet splash vt.handoff=7
  SourcePackage: fglrx

[Desktop-packages] [Bug 1497266] [NEW] package lirc 0.9.0-0ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2015-09-18 Thread Lin Yu Han

Public bug reported:

Setting up lirc (0.9.0-0ubuntu5) ...
initctl: Unknown job: udev
reload: Unknown job: udev
invoke-rc.d: initscript udev, action "reload" failed.
dpkg: error processing package lirc (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 lirc
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: lirc 0.9.0-0ubuntu5
ProcVersionSignature: Ubuntu 3.19.0-28.30~14.04.1-generic 3.19.8-ckt5
Uname: Linux 3.19.0-28-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.13
Architecture: amd64
Date: Fri Sep 18 09:44:17 2015
DuplicateSignature: package:lirc:0.9.0-0ubuntu5:subprocess installed 
post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2015-09-14 (3 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.4
 apt  1.0.1ubuntu2.10
SourcePackage: lirc
Title: package lirc 0.9.0-0ubuntu5 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package trusty

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

Title:
  package lirc 0.9.0-0ubuntu5 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in lirc package in Ubuntu:
  New

Bug description:
  Setting up lirc (0.9.0-0ubuntu5) ...
  initctl: Unknown job: udev
  reload: Unknown job: udev
  invoke-rc.d: initscript udev, action "reload" failed.
  dpkg: error processing package lirc (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   lirc
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: lirc 0.9.0-0ubuntu5
  ProcVersionSignature: Ubuntu 3.19.0-28.30~14.04.1-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: amd64
  Date: Fri Sep 18 09:44:17 2015
  DuplicateSignature: package:lirc:0.9.0-0ubuntu5:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-09-14 (3 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.4
   apt  1.0.1ubuntu2.10
  SourcePackage: lirc
  Title: package lirc 0.9.0-0ubuntu5 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1489696] Re: black screen when enabling rotation on a gpu screen

2015-08-31 Thread Keng-Yu Lin

** Changed in: hwe-next
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: hwe-next
   Importance: Undecided => Medium

** Changed in: hwe-next
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1489696

Title:
  black screen when enabling rotation on a gpu screen

Status in HWE Next:
  In Progress
Status in xorg-server package in Ubuntu:
  In Progress
Status in xorg-server-lts-vivid package in Ubuntu:
  Invalid
Status in xorg-server source package in Vivid:
  New
Status in xorg-server-lts-vivid source package in Vivid:
  New

Bug description:
  Running with the proprietary nvidia drivers in an optimus config
  works, but enabling reflection or rotation on the intel screen causes
  a black screen to appear.

  [Impact]
   * Causes a black screen if rotation or reflection is enabled.

  [Test Case]
   * Run xrandr --output SOMEOUTPUT --rotation left
  - Expected: Screen should rotate, or the call should fail.
  - Bad behavior: Succeeds, but causes a black screen.

  [Regression Potential]
   * The affected codepaths have reflection and rotation disabled for gpu 
screens. Another fix could be fixing reflection/rotation, but that will be more 
involved and likely require driver fixes.

  [Other Info]
   * This issue is copied from 
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1308515 for vivid 
and wily.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1489696/+subscriptions

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

[Desktop-packages] [Bug 1399096] Re: Touchpad lost function after switch from guest to user account

2015-08-16 Thread Keng-Yu Lin

** Changed in: hwe-next
   Importance: Undecided => Low

** Changed in: hwe-next
   Status: New => Invalid

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

Title:
  Touchpad lost function after switch from guest to user account

Status in HWE Next:
  Invalid
Status in unity-greeter package in Ubuntu:
  New

Bug description:
  Reproduce steps:
1) Change account to guest by click guest account on the menu.
2) Change account to user again
3) Touchpad lost its function.

  When the touchpad becomes malfunction, there are some messages in
  /var/log/Xorg.0.log

  [   282.908] (WW) synaptics: SynPS/2 Synaptics TouchPad: can't grab event 
device, errno=16
  [   282.940] [dix] couldn't enable device 11
  [   282.940] setversion 1.4 failed: Permission denied

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-input-synaptics 1.7.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-41.69stella1-generic 3.13.11.10
  Uname: Linux 3.13.0-41-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Dec  4 02:25:41 2014
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-neihu-trusty-amd64-20141125-0
  DistroCodename: trusty
  DistroVariant: ubuntu
  InstallationDate: Installed on 2014-12-04 (0 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20141125-01:45
  Lsusb:
   Bus 001 Device 003: ID 0bda:5776 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 8087:8000 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP 15 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-41-generic 
root=UUID=f7c1e040-6471-4e14-9e77-bb406b63fad3 ro quiet splash 
video.use_native_backlight=1 radeon.modeset=0 nouveau.modeset=0 vt.handoff=7
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/28/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.32
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2211
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 86.45
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.32:bd10/28/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr097F12005F1620100:rvnHewlett-Packard:rn2211:rvr86.45:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 097F12005F1620100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.1stella3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Dec  4 02:21:16 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17900 
   vendor AUO
  xserver.version: 2:1.15.1-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1399096/+subscriptions

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

[Desktop-packages] [Bug 1311257] Re: Wifi cannot connect or unstable after suspend 14.04

2015-08-16 Thread Terri Yu

A while back, my wifi connection kept dropping.  I had to keep re-
booting Ubuntu 14.04 to try and get my wifi connection back. I have a
Lenovo Thinkpad X220T laptop with Intel Centrino Advanced-N 6205 wifi
card. I'm using a WPA2 connection.

I tried disabling the N mode of the wifi card, as detailed in this link:
http://askubuntu.com/questions/457729/ubuntu-14-04-wireless-constantly-
disconnects

I also tried killing wpa_supplicant as detailed here in this bug report.

Eventually, I upgraded my Linux kernel from 3.13 to 3.16 (the v3.16
kernel is available on Ubuntu 14.04.2) and that mostly fixed my wifi
issues.  I've upgraded to the 3.19 kernel this week and my wifi seems to
be working on this kernel as well.

Reference: see my report on Ubuntu forums --
http://ubuntuforums.org/showthread.php?t=2275184

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-nettool in Ubuntu.
https://bugs.launchpad.net/bugs/1311257

Title:
  Wifi cannot connect or unstable after suspend 14.04

Status in gnome-nettool package in Ubuntu:
  Confirmed

Bug description:
  I've tried every solution, such as
  1. editing /etc/pm/config.d to add
   SUSPEND_MODULES="iwlwifi"
  2. editing /etc/modprobe/d/wilwifi.conf to add:
  options iwlwifi bt_coex_active=0
  options iwlwifi 11n_disable=1
  3. running: sudo rmmod iwlwifi && sudo modprobe iwlwifi
  4. stopping, starting, or restarting Network Manager

  Nothing seems to work.  When I had 13.10, my wifi worked without a
  problem, but once I erased it and installed 14.04, wifi will not
  connect after suspend.  Ethernet works fine.  The only way I've found
  to resolve this is to restart my computer.  I have a Lenovo T420.  If
  I try to connect after suspend, it shows the Wifi Networks, tries to
  connect, and  says "Disconnected..." every time.

  ~$ sudo apt-get update; sudo apt-get install hwinfo grep rfkill; sudo lshw -C 
network; rfkill list; sudo iwlist scan | egrep -i 'chan|ssid'; cat 
/etc/network/interfaces; cat /etc/lsb-release; lspci -nnk | grep -iA2 net; 
lsusb; nmcli nm status; sudo lshw -short; uname -a; dmesg | egrep 
'02:00|80211|acx|at76|ath|b43|bcm|brcm|CX|eth|ipw|ireless|irmware|isl|lbtf|orinoco|ndiswrapper|NPE|ound|p54|prism|rror|rtl|rt2|rt3|rt5|rt6|rt7|usb|witch|wl';sudo
 dmidecode|egrep 'anufact|roduct|erial|elease'; iwconfig; cat /etc/modprobe.d/* 
| egrep 
'80211|acx|at76|ath|b43|bcm|brcm|CX|eth|ipw|irmware|isl|lbtf|orinoco|ndiswrapper|NPE|p54|prism|rtl|rt2|rt3|rt6|rt7|wmi|witch|wl';
 cat /var/lib/NetworkManager/NetworkManager.state; sudo hwinfo --netcard ; ps 
-aux|egrep 'wpa|icd|etwork'; netstat -rn ; cat /etc/resolv.conf; ls -lia /boot; 
sudo lsmod
  Ign http://dl.google.com stable InRelease
  Hit http://dl.google.com stable Release.gpg
  Hit http://dl.google.com stable Release
  Hit http://repository.spotify.com stable InRelease
  Ign http://us.archive.ubuntu.com trusty InRelease
  Hit http://dl.google.com stable/main amd64 Packages
  Hit http://dl.google.com stable/main i386 Packages
  Ign http://extras.ubuntu.com trusty InRelease
  Hit http://repository.spotify.com stable/non-free amd64 Packages
  Ign http://security.ubuntu.com trusty-security InRelease
  Ign http://us.archive.ubuntu.com trusty-updates InRelease
  Hit http://repository.spotify.com stable/non-free i386 Packages
  Hit http://extras.ubuntu.com trusty Release.gpg
  Hit http://security.ubuntu.com trusty-security Release.gpg
  Ign http://us.archive.ubuntu.com trusty-backports InRelease
  Hit http://extras.ubuntu.com trusty Release
  Ign http://us.archive.ubuntu.com trusty-proposed InRelease
  Hit http://security.ubuntu.com trusty-security Release
  Hit http://extras.ubuntu.com trusty/main Sources
  Ign http://dl.google.com stable/main Translation-en_US
  Hit http://us.archive.ubuntu.com trusty Release.gpg
  Ign http://dl.google.com stable/main Translation-en
  Hit http://security.ubuntu.com trusty-security/main Sources
  Hit http://extras.ubuntu.com trusty/main amd64 Packages
  Hit http://us.archive.ubuntu.com trusty-updates Release.gpg
  Hit http://security.ubuntu.com trusty-security/restricted Sources
  Hit http://extras.ubuntu.com trusty/main i386 Packages
  Hit http://us.archive.ubuntu.com trusty-backports Release.gpg
  Hit http://security.ubuntu.com trusty-security/universe Sources
  Hit http://us.archive.ubuntu.com trusty-proposed Release.gpg
  Hit http://security.ubuntu.com trusty-security/multiverse Sources
  Hit http://us.archive.ubuntu.com trusty Release
  Ign http://ppa.launchpad.net trusty InRelease
  Hit http://security.ubuntu.com trusty-security/main amd64 Packages
  Hit http://us.archive.ubuntu.com trusty-updates Release
  Ign http://ppa.launchpad.net trusty InRelease
  Hit http://security.ubuntu.com trusty-security/restricted amd64 Packages
  Ign http://repository.spotify.com stable/non-free Translation-en_US
  Hit http://us.archive.ubuntu.com trusty-backports Release
  Ign http://ppa.launchpad.net trusty

[Desktop-packages] [Bug 1470862] Re: When using fglrx module, the virtual consoles are blank and useless

2015-08-14 Thread Stephen Yu

I have the same problem after upgraded from Ubuntu 14.10 to 15.04. My
graphic card is AMD R7 260X using fglrx-amdcccle-updates
2:15.200-0ubuntu4 driver. This driver seems working fine except I got
blank screen when I tried to switch to virtual consoles with ctl+alt+fx
keys.

The open source driver radeon is even worse, it randomly crashs X and
get to the login screen and you can't log back it from the login screen.
Instead, you need to "sudo killall Xorg".

Tried many suggestions so far from the web, it didn't help.

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1470862

Title:
When using fglrx module, the virtual consoles are blank and useless

Status in fglrx-installer-updates package in Ubuntu:
Confirmed

Bug description:
When the PC boots it shows the sddm login, but if I switch to the
first virtual console using Ctrl+Alt+F1, the console is blank. The
other consoles are in the same state. Only the virtual console with
the sddm login, is running fine.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: fglrx-updates 2:15.200-0ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
Uname: Linux 3.19.0-21-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CurrentDesktop: KDE
Date: Thu Jul 2 15:31:28 2015
SourcePackage: fglrx-installer-updates
UpgradeStatus: Upgraded to vivid on 2015-03-12 (112 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1470862/+subscriptions

[Desktop-packages] [Bug 1323594] Re: vpn auto-connect works, but doesn't connect automatically when network is available.

2015-07-14 Thread Vincent Yu

Looks like NetworkManager is having issues getting the user's VPN
password from gnome-key-daemon. I've posted a workaround at
http://askubuntu.com/a/332796/109757. Basically, change password-flags=1
to password-flags=0 in /etc/NetworkManager/system-connections/
(warning: this will store the VPN password in plaintext).

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

Title:
  vpn auto-connect works, but doesn't connect automatically when network
  is available.

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I'm having a bug in Ubuntu Trusty Tahr 14.04 LTS. The issue I'm having
  is that with a connection set to auto-connect to a PPTP-vpn, it does
  not auto-connect when (wireless)-network becomes available.

  Syslog returns this error:

   [1401130450.367538] [nm-vpn-connection.c:1374]
  get_secrets_cb(): Failed to request VPN secrets #2: (6) No agents were
  available for this request.

  However it does connect when when connecting to the particular
  connection manually. e.g. I select the wireless network in the
  network-manager.

  This bug seems related to bugs:
  #280571
  #1297849
  #1247682 
  #1298047

  The difference between my situation and the others is that vpn-
  autoconnect does work, it just doesn't work automatically.

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

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

[Desktop-packages] [Bug 556071] Re: Xelatex complains that lmodern fonts are not installed

2015-06-03 Thread yu sheng lin

Using 14.04 and lmodern is still not in the dependencies list.
I am using xeCJK and this it successfully compiled after installing lmodern.
\usepackage{xeCJK}
\usepackage{fontspec}
\setCJKmainfont{}

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to texlive-base in Ubuntu.
https://bugs.launchpad.net/bugs/556071

Title:
  Xelatex complains that lmodern fonts are not installed

Status in texlive-base package in Ubuntu:
  New

Bug description:
  Binary package hint: texlive-xetex

  There is exactly the same problem in Ubuntu 9.10 as described in this
  Debian bug report:

  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576599

  ProblemType: Bug
  Architecture: i386
  Date: Mon Apr  5 23:28:13 2010
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  NonfreeKernelModules: wl
  Package: texlive-xetex 2007.dfsg.2-7ubuntu1
  ProcEnviron:
   LANG=de_CH.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-20.58-generic
  SourcePackage: texlive-bin
  Uname: Linux 2.6.31-20-generic i686

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

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

[Desktop-packages] [Bug 1381856] Re: [Dell Latitude E5550] Microphone mute key does not work on this system

2015-06-01 Thread Keng-Yu Lin

@Hui, can you also SRU the U-S-D patch?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1381856

Title:
  [Dell Latitude E5550] Microphone mute key does not work on this system

Status in HWE Next Project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in linux source package in Utopic:
  Fix Released
Status in unity-settings-daemon source package in Utopic:
  New

Bug description:
  CID: 201406-15271 Dell Latitude E5550

  The microphone mute key does not work at all.

  Key event cannot be captured by "xev" or "sudo showkey -s"
  But keycode 248 would be returned when testing with sudo showkey -k

  Alsa info:
  http://www.alsa-project.org/db/?f=006099fcf08709c82a74dba986a907a602a868ab

  Also note that with file at /etc/udev/hwdb.d/60-dell-mic-mute-hotkey.hwdb 
generated with the following content:
  # Dell platform kernel driver 
  keyboard:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pn*
   KEYBOARD_KEY_150=f20 # Mic mute toggle

  And with udev database updated: sudo udevadm hwdb -u

  The microphone mute key works, but the mic mute led does not work.
  (Also the icon is not correct, which show a speaker instead of a mic)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-37-generic 3.13.0-37.64
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1530 F pulseaudio
   /dev/snd/controlC1:  ubuntu 1530 F pulseaudio
  CRDA:
   country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
  CurrentDesktop: Unity
  Date: Wed Oct 15 23:17:51 2014
  HibernationDevice: RESUME=UUID=02cbc1f1-a261-484c-8fc2-05b68f73446d
  InstallationDate: Installed on 2014-10-09 (6 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Latitude E5550
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic 
root=UUID=d3b20ae5-9ff8-49b3-b640-1c6a9f264710 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/25/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: T43
  dmi.board.name: 0141B2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X02
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrT43:bd07/25/2014:svnDellInc.:pnLatitudeE5550:pvr01:rvnDellInc.:rn0141B2:rvrX02:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5550
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1381856/+subscriptions

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

[Desktop-packages] [Bug 1441449] Re: [HP Z820] external microphone does not work, only records noises

2015-05-15 Thread Keng-Yu Lin

** Changed in: hwe-next
 Assignee: Keng-Yu Lin (lexical) => David Henningsson (diwic)

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

Title:
  [HP Z820] external microphone does not work, only records noises

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

Bug description:
  Records with a lot noises, barely can heard the sound.

  Step to reproduce:

  1. plug your microphone to the front/rear micrphone jack
  2. turn up the microphone volume in the system > sound settings
  3. open a terminal then type command: arecord test.wav, ctrl-c to inturrupt 
when you finish

  Expected result:

  when playing the recordings it should plays recognizable sound.

  Actual results:

  A lot noise in the recordings.

  
  Additional information:
  In the attached recording file, you should hear, "Testing, One, Two, Three, 
Four, Five ".

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-49.81-generic 3.13.11-ckt17
  Uname: Linux 3.13.0-49-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1696 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1696 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Apr  8 01:32:46 2015
  InstallationDate: Installed on 2015-04-02 (5 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J63 v03.69
  dmi.board.asset.tag: 2UA4242K12
  dmi.board.name: 158B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: 2UA4242K12
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ63v03.69:bd03/25/2014:svnHewlett-Packard:pnHPZ820Workstation:pvr:rvnHewlett-Packard:rn158B:rvr1.01:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Z820 Workstation
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1441449/+subscriptions

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

[Desktop-packages] [Bug 1445221] Re: [BSW] Backport fixes to solve promotion video playback issue

2015-04-21 Thread Keng-Yu Lin

** Changed in: hwe-next
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1445221

Title:
  [BSW] Backport fixes to solve promotion video playback issue

Status in HWE Next Project:
  Fix Committed
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-intel source package in Trusty:
  Fix Committed

Bug description:
  In Braswell platform, it needs the following commit to properly run
  Ubuntu promotion video

  commit 2afeef0c3ffeae768198fc08c9f365ccd28b7f5d
  Author: Chris Wilson 
  Date:   Thu May 15 11:28:48 2014 +0100

  sna: Mark the CHV vsync method as unknown

  Similar to the story with Baytrail, vsync is a lost art.

  Signed-off-by: Chris Wilson 

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1445221/+subscriptions

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

[Desktop-packages] [Bug 1445221] Re: [BSW] Backport fixes to solve promotion video playback issue

2015-04-21 Thread Keng-Yu Lin

** Changed in: hwe-next
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1445221

Title:
  [BSW] Backport fixes to solve promotion video playback issue

Status in HWE Next Project:
  Fix Committed
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-intel source package in Trusty:
  Fix Committed

Bug description:
  In Braswell platform, it needs the following commit to properly run
  Ubuntu promotion video

  commit 2afeef0c3ffeae768198fc08c9f365ccd28b7f5d
  Author: Chris Wilson 
  Date:   Thu May 15 11:28:48 2014 +0100

  sna: Mark the CHV vsync method as unknown

  Similar to the story with Baytrail, vsync is a lost art.

  Signed-off-by: Chris Wilson 

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1445221/+subscriptions

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

[Desktop-packages] [Bug 1381625] Re: Adjust brightness to lowest value caused screen whole black

2015-04-20 Thread Keng-Yu Lin

** Changed in: hwe-next
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1381625

Title:
  Adjust brightness to lowest value caused screen whole black

Status in HWE Next Project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  New

Bug description:
  [Impact]

  When adjusting screen brightness to lowest value, it turns screen
  backlight off.

  [Test Case]

  1. Install Image
  2. Press System's brightness hotkey to adjust the brightness level to the 
lowest or
  3. Go to System "Settings" -> "Brightness & Lock" to adjust brightness level 
to the lowest
  4. Check if the screen display still has backlight

  Expected results: There is still screen backlight

  Actual results: Sceen backlight is turned off

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1381625/+subscriptions

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

[Desktop-packages] [Bug 1445221] Re: [BSW] Backport fixes to solve promotion video playback issue

2015-04-20 Thread Keng-Yu Lin

** Changed in: hwe-next
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1445221

Title:
  [BSW] Backport fixes to solve promotion video playback issue

Status in HWE Next Project:
  Fix Committed
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-intel source package in Trusty:
  Fix Committed

Bug description:
  In Braswell platform, it needs the following commit to properly run
  Ubuntu promotion video

  commit 2afeef0c3ffeae768198fc08c9f365ccd28b7f5d
  Author: Chris Wilson 
  Date:   Thu May 15 11:28:48 2014 +0100

  sna: Mark the CHV vsync method as unknown

  Similar to the story with Baytrail, vsync is a lost art.

  Signed-off-by: Chris Wilson 

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1445221/+subscriptions

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

[Desktop-packages] [Bug 1441449] Re: [HP Z820] external microphone does not work, only records noises

2015-04-20 Thread Keng-Yu Lin

** Changed in: hwe-next
   Importance: Critical => High

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

Title:
  [HP Z820] external microphone does not work, only records noises

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

Bug description:
  Records with a lot noises, barely can heard the sound.

  Step to reproduce:

  1. plug your microphone to the front/rear micrphone jack
  2. turn up the microphone volume in the system > sound settings
  3. open a terminal then type command: arecord test.wav, ctrl-c to inturrupt 
when you finish

  Expected result:

  when playing the recordings it should plays recognizable sound.

  Actual results:

  A lot noise in the recordings.

  
  Additional information:
  In the attached recording file, you should hear, "Testing, One, Two, Three, 
Four, Five ".

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-49.81-generic 3.13.11-ckt17
  Uname: Linux 3.13.0-49-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1696 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1696 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Apr  8 01:32:46 2015
  InstallationDate: Installed on 2015-04-02 (5 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J63 v03.69
  dmi.board.asset.tag: 2UA4242K12
  dmi.board.name: 158B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: 2UA4242K12
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ63v03.69:bd03/25/2014:svnHewlett-Packard:pnHPZ820Workstation:pvr:rvnHewlett-Packard:rn158B:rvr1.01:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Z820 Workstation
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1441449/+subscriptions

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

[Desktop-packages] [Bug 1441449] Re: [HP Z820] external microphone does not work, only records noises

2015-04-16 Thread Keng-Yu Lin

** Changed in: hwe-next
 Assignee: (unassigned) => Keng-Yu Lin (lexical)

** Changed in: hwe-next
   Importance: Undecided => Critical

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

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

Title:
  [HP Z820] external microphone does not work, only records noises

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

Bug description:
  Records with a lot noises, barely can heard the sound.

  Step to reproduce:

  1. plug your microphone to the front/rear micrphone jack
  2. turn up the microphone volume in the system > sound settings
  3. open a terminal then type command: arecord test.wav, ctrl-c to inturrupt 
when you finish

  Expected result:

  when playing the recordings it should plays recognizable sound.

  Actual results:

  A lot noise in the recordings.

  
  Additional information:
  In the attached recording file, you should hear, "Testing, One, Two, Three, 
Four, Five ".

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-49.81-generic 3.13.11-ckt17
  Uname: Linux 3.13.0-49-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1696 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1696 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Apr  8 01:32:46 2015
  InstallationDate: Installed on 2015-04-02 (5 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J63 v03.69
  dmi.board.asset.tag: 2UA4242K12
  dmi.board.name: 158B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: 2UA4242K12
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ63v03.69:bd03/25/2014:svnHewlett-Packard:pnHPZ820Workstation:pvr:rvnHewlett-Packard:rn158B:rvr1.01:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Z820 Workstation
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1441449/+subscriptions

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

[Desktop-packages] [Bug 1248720] Re: Bluetooth ON/OFF button switches OFF automatically

2015-04-09 Thread Yu Ning

@Sebastien, I just made a quick check for the redesigned code, yes, it
does similar blocking&unblocking on power_callback(), that is also what
my patch does.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1248720

Title:
  Bluetooth ON/OFF button switches OFF automatically

Status in One Hundred Papercuts:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  I am on ThinkPad T61 with Ubuntu 13.10 installed. I disabled bluetooth
  on startup by adding:

  "echo disable > /proc/acpi/ibm/bluetooth"

  to /etc/rc.local. When I open gnome-control-center -> Bluetooth and
  click on the "ON/OFF" switch button, it switches on for a fraction of
  a second and then switches back to off. Below are dmesg lines
  corresponding to this event:

  [   94.028110] usb 3-1: new full-speed USB device number 5 using uhci_hcd
  [   94.194320] usb 3-1: New USB device found, idVendor=0a5c, idProduct=2110
  [   94.194325] usb 3-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [   94.194328] usb 3-1: Product: BCM2045B
  [   94.194330] usb 3-1: Manufacturer: Broadcom Corp
  [   94.388169] usb 3-1: USB disconnect, device number 5

  
  The workaround is to type "turn connectivity on/off" combination of my 
keyboard (FN+F5) -- then both wireless and bluetooth go off, and when I type it 
again, bluetooth comes back ON.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu45
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Wed Nov  6 20:41:45 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-10-18 (19 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20131023.2-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3+13.10.20131004-0ubuntu1

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

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

[Desktop-packages] [Bug 1441449] Re: [HP Z820] external microphone does not work, only records noises

2015-04-09 Thread Keng-Yu Lin

@yung, can you open `alsamixer` then try to lower the gain or volume.
see if with lower volume or gain, clear sound can be recorded.

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

Title:
  [HP Z820] external microphone does not work, only records noises

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

Bug description:
  Records with a lot noises, barely can heard the sound.

  Step to reproduce:

  1. plug your microphone to the front/rear micrphone jack
  2. turn up the microphone volume in the system > sound settings
  3. open a terminal then type command: arecord test.wav, ctrl-c to inturrupt 
when you finish

  Expected result:

  when playing the recordings it should plays recognizable sound.

  Actual results:

  A lot noise in the recordings.

  
  Additional information:
  In the attached recording file, you should hear, "Testing, One, Two, Three, 
Four, Five ".

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-49.81-generic 3.13.11-ckt17
  Uname: Linux 3.13.0-49-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1696 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1696 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Apr  8 01:32:46 2015
  InstallationDate: Installed on 2015-04-02 (5 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J63 v03.69
  dmi.board.asset.tag: 2UA4242K12
  dmi.board.name: 158B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: 2UA4242K12
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ63v03.69:bd03/25/2014:svnHewlett-Packard:pnHPZ820Workstation:pvr:rvnHewlett-Packard:rn158B:rvr1.01:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Z820 Workstation
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1441449/+subscriptions

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

[Desktop-packages] [Bug 1248720] Re: Bluetooth ON/OFF button switches OFF automatically

Tested with gnome live [1], the issue is not reproduced, the g-c-c
version is 3.16.0.

I also checked the source code [2], looks like the issue is already
fixed via a redesign [3]. The upstream tracker for the redesign is
https://bugzilla.gnome.org/show_bug.cgi?id=719565

[1]: https://download.gnome.org/misc/promo-usb/gnome-3.16.x86_64.iso
[2]: 
https://git.gnome.org/browse/gnome-control-center/tree/panels/bluetooth/cc-bluetooth-panel.c
[3]: 
https://git.gnome.org/browse/gnome-control-center/commit/?id=28fecc01c46a7b082f9746744c938e499a522e4f

** Bug watch added: GNOME Bug Tracker #719565
   https://bugzilla.gnome.org/show_bug.cgi?id=719565

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1248720

Title:
  Bluetooth ON/OFF button switches OFF automatically

Status in One Hundred Papercuts:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  I am on ThinkPad T61 with Ubuntu 13.10 installed. I disabled bluetooth
  on startup by adding:

  "echo disable > /proc/acpi/ibm/bluetooth"

  to /etc/rc.local. When I open gnome-control-center -> Bluetooth and
  click on the "ON/OFF" switch button, it switches on for a fraction of
  a second and then switches back to off. Below are dmesg lines
  corresponding to this event:

  [   94.028110] usb 3-1: new full-speed USB device number 5 using uhci_hcd
  [   94.194320] usb 3-1: New USB device found, idVendor=0a5c, idProduct=2110
  [   94.194325] usb 3-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [   94.194328] usb 3-1: Product: BCM2045B
  [   94.194330] usb 3-1: Manufacturer: Broadcom Corp
  [   94.388169] usb 3-1: USB disconnect, device number 5

  
  The workaround is to type "turn connectivity on/off" combination of my 
keyboard (FN+F5) -- then both wireless and bluetooth go off, and when I type it 
again, bluetooth comes back ON.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu45
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Wed Nov  6 20:41:45 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-10-18 (19 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20131023.2-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3+13.10.20131004-0ubuntu1

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

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

[Desktop-packages] [Bug 1248720] Re: Bluetooth ON/OFF button switches OFF automatically

The issue is also reproduced in ubuntu gnome daily image [1], the
package version is 1:3.14.2-2ubuntu3

[1]: http://cdimage.ubuntu.com/ubuntu-gnome/daily-live/20150407/

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1248720

Title:
  Bluetooth ON/OFF button switches OFF automatically

Status in One Hundred Papercuts:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  I am on ThinkPad T61 with Ubuntu 13.10 installed. I disabled bluetooth
  on startup by adding:

  "echo disable > /proc/acpi/ibm/bluetooth"

  to /etc/rc.local. When I open gnome-control-center -> Bluetooth and
  click on the "ON/OFF" switch button, it switches on for a fraction of
  a second and then switches back to off. Below are dmesg lines
  corresponding to this event:

  [   94.028110] usb 3-1: new full-speed USB device number 5 using uhci_hcd
  [   94.194320] usb 3-1: New USB device found, idVendor=0a5c, idProduct=2110
  [   94.194325] usb 3-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [   94.194328] usb 3-1: Product: BCM2045B
  [   94.194330] usb 3-1: Manufacturer: Broadcom Corp
  [   94.388169] usb 3-1: USB disconnect, device number 5

  
  The workaround is to type "turn connectivity on/off" combination of my 
keyboard (FN+F5) -- then both wireless and bluetooth go off, and when I type it 
again, bluetooth comes back ON.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu45
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Wed Nov  6 20:41:45 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-10-18 (19 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20131023.2-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3+13.10.20131004-0ubuntu1

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

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

[Desktop-packages] [Bug 1248720] Re: Bluetooth ON/OFF button switches OFF automatically

I'll also try with latest upstream version.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1248720

Title:
  Bluetooth ON/OFF button switches OFF automatically

Status in One Hundred Papercuts:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  I am on ThinkPad T61 with Ubuntu 13.10 installed. I disabled bluetooth
  on startup by adding:

  "echo disable > /proc/acpi/ibm/bluetooth"

  to /etc/rc.local. When I open gnome-control-center -> Bluetooth and
  click on the "ON/OFF" switch button, it switches on for a fraction of
  a second and then switches back to off. Below are dmesg lines
  corresponding to this event:

  [   94.028110] usb 3-1: new full-speed USB device number 5 using uhci_hcd
  [   94.194320] usb 3-1: New USB device found, idVendor=0a5c, idProduct=2110
  [   94.194325] usb 3-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [   94.194328] usb 3-1: Product: BCM2045B
  [   94.194330] usb 3-1: Manufacturer: Broadcom Corp
  [   94.388169] usb 3-1: USB disconnect, device number 5

  
  The workaround is to type "turn connectivity on/off" combination of my 
keyboard (FN+F5) -- then both wireless and bluetooth go off, and when I type it 
again, bluetooth comes back ON.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu45
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Wed Nov  6 20:41:45 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-10-18 (19 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20131023.2-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3+13.10.20131004-0ubuntu1

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

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

[Desktop-packages] [Bug 1248720] Re: Bluetooth ON/OFF button switches OFF automatically

I installed gnome desktop on ubuntu trusty, and can also reproduce the
issue in gnome-control-center.

The package version is:
gnome-control-center 1:3.6.3-0ubuntu56.1

$ gnome-control-center --version
gnome-control-center 3.6.3

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1248720

Title:
  Bluetooth ON/OFF button switches OFF automatically

Status in One Hundred Papercuts:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  I am on ThinkPad T61 with Ubuntu 13.10 installed. I disabled bluetooth
  on startup by adding:

  "echo disable > /proc/acpi/ibm/bluetooth"

  to /etc/rc.local. When I open gnome-control-center -> Bluetooth and
  click on the "ON/OFF" switch button, it switches on for a fraction of
  a second and then switches back to off. Below are dmesg lines
  corresponding to this event:

  [   94.028110] usb 3-1: new full-speed USB device number 5 using uhci_hcd
  [   94.194320] usb 3-1: New USB device found, idVendor=0a5c, idProduct=2110
  [   94.194325] usb 3-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [   94.194328] usb 3-1: Product: BCM2045B
  [   94.194330] usb 3-1: Manufacturer: Broadcom Corp
  [   94.388169] usb 3-1: USB disconnect, device number 5

  
  The workaround is to type "turn connectivity on/off" combination of my 
keyboard (FN+F5) -- then both wireless and bluetooth go off, and when I type it 
again, bluetooth comes back ON.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu45
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Wed Nov  6 20:41:45 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-10-18 (19 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20131023.2-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3+13.10.20131004-0ubuntu1

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

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

[Desktop-packages] [Bug 1248720] Re: Bluetooth ON/OFF button switches OFF automatically

Let me install a gnome desktop and have a try. Will update later.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1248720

Title:
  Bluetooth ON/OFF button switches OFF automatically

Status in One Hundred Papercuts:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  I am on ThinkPad T61 with Ubuntu 13.10 installed. I disabled bluetooth
  on startup by adding:

  "echo disable > /proc/acpi/ibm/bluetooth"

  to /etc/rc.local. When I open gnome-control-center -> Bluetooth and
  click on the "ON/OFF" switch button, it switches on for a fraction of
  a second and then switches back to off. Below are dmesg lines
  corresponding to this event:

  [   94.028110] usb 3-1: new full-speed USB device number 5 using uhci_hcd
  [   94.194320] usb 3-1: New USB device found, idVendor=0a5c, idProduct=2110
  [   94.194325] usb 3-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [   94.194328] usb 3-1: Product: BCM2045B
  [   94.194330] usb 3-1: Manufacturer: Broadcom Corp
  [   94.388169] usb 3-1: USB disconnect, device number 5

  
  The workaround is to type "turn connectivity on/off" combination of my 
keyboard (FN+F5) -- then both wireless and bluetooth go off, and when I type it 
again, bluetooth comes back ON.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu45
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Wed Nov  6 20:41:45 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-10-18 (19 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20131023.2-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3+13.10.20131004-0ubuntu1

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

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

[Desktop-packages] [Bug 1309550] Re: Exec should be "amdxdg-su -c /usr/bin/amdcccle" in ubuntu-amdccclesu.desktop

2015-04-06 Thread Keng-Yu Lin

** Changed in: hwe-next
 Assignee: (unassigned) => Alberto Milone (albertomilone)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1309550

Title:
  Exec should be "amdxdg-su -c /usr/bin/amdcccle" in ubuntu-
  amdccclesu.desktop

Status in HWE Next Project:
  Triaged
Status in fglrx-installer package in Ubuntu:
  Fix Released
Status in fglrx-installer-updates package in Ubuntu:
  Fix Released
Status in fglrx-installer source package in Trusty:
  Triaged
Status in fglrx-installer-updates source package in Trusty:
  Triaged

Bug description:
  When trying to open the AMD Catalyst Control Center in Administrative
  mode by using the launcher found in dash, you will be ask to enter
  password for it, but it always shows "su: authentication failure" and
  exit.

  Steps:
  1. Install 14.04 on a I+A system, boot to desktop
  2. Try to open the Control Center in administrative mode by searching AMD in 
dash
  3. Enter password

  Expected result:
  * AMD Catalyst Control Center opened

  Actual result:
  * The authentication windows closed with failure message

  This bug will be a blocker to 14.04 certificate for all I+A (or even
  A+A) GPU switchable systems, since user won't be able to switch
  between GPUs without using the command line commands.

  WORKAROUND:
  run "sudo amdcccle" in the terminal, you will be able to switch between GPUs.

  Exec should be "amdxdg-su -c /usr/bin/amdcccle" in ubuntu-amdccclesu.desktop.
  It must be full patch, otherwise it will fail to be launched.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: fglrx 2:13.350.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Apr 18 21:54:39 2014
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-kittyhawk-kylin-trusty-amd64-20140412-0
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx, 13.350.1, 3.13.0-24-generic, x86_64: installed
   oem-audio-mic-mute-led-1220709, 1.0kittyhawk1, 3.13.0-24-generic, x86_64: 
installed
   oem-touchpad-rmi4-1238726, 0001kittyhawk4, 3.13.0-24-generic, x86_64: 
installed
   tp-smapi, 0.41, 3.13.0-24-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:501d]
  InstallationDate: Installed on 2014-04-16 (1 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140412-08:01
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0011 Validity Sensors, Inc. VFS5011 Fingerprint 
Reader
   Bus 001 Device 003: ID 04f2:b39f Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 8087:07dc Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20AYZ01MCN
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=5a95717e-ff3f-46f7-a0ee-af0dc776f3ae ro quiet splash pcie_aspm=force 
radeon.modeset=0 nouveau.modeset=0 vt.handoff=7
  SourcePackage: fglrx-installer
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J3ET29WW (1.06 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AYZ01MCN
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD PRC DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ3ET29WW(1.06):bd06/25/2013:svnLENOVO:pn20AYZ01MCN:pvrThinkPadS3-S440:rvnLENOVO:rn20AYZ01MCN:rvrWin8STDPRCDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20AYZ01MCN
  dmi.product.version: ThinkPad S3-S440
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0

[Desktop-packages] [Bug 1248720] Re: Bluetooth ON/OFF button switches OFF automatically

2015-04-03 Thread Yu Ning

** Branch linked: lp:~yuningdodo/unity-control-center/unity-control-
center.lp1248720-block-power-callback-unless-its-triggered-by-user

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1248720

Title:
  Bluetooth ON/OFF button switches OFF automatically

Status in One Hundred Papercuts:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  I am on ThinkPad T61 with Ubuntu 13.10 installed. I disabled bluetooth
  on startup by adding:

  "echo disable > /proc/acpi/ibm/bluetooth"

  to /etc/rc.local. When I open gnome-control-center -> Bluetooth and
  click on the "ON/OFF" switch button, it switches on for a fraction of
  a second and then switches back to off. Below are dmesg lines
  corresponding to this event:

  [   94.028110] usb 3-1: new full-speed USB device number 5 using uhci_hcd
  [   94.194320] usb 3-1: New USB device found, idVendor=0a5c, idProduct=2110
  [   94.194325] usb 3-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [   94.194328] usb 3-1: Product: BCM2045B
  [   94.194330] usb 3-1: Manufacturer: Broadcom Corp
  [   94.388169] usb 3-1: USB disconnect, device number 5

  
  The workaround is to type "turn connectivity on/off" combination of my 
keyboard (FN+F5) -- then both wireless and bluetooth go off, and when I type it 
again, bluetooth comes back ON.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu45
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Wed Nov  6 20:41:45 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-10-18 (19 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20131023.2-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3+13.10.20131004-0ubuntu1

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

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

[Desktop-packages] [Bug 1248720] Re: Bluetooth ON/OFF button switches OFF automatically

2015-04-01 Thread Yu Ning

Hi guys, I have converted my patch (comment #8) to a merge proposal,
could anyone help review it? Thanks in advance.

https://code.launchpad.net/~yuningdodo/unity-control-center/unity-
control-center.lp1248720-block-power-callback-unless-its-triggered-by-
user/+merge/255041

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1248720

Title:
  Bluetooth ON/OFF button switches OFF automatically

Status in One Hundred Papercuts:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  I am on ThinkPad T61 with Ubuntu 13.10 installed. I disabled bluetooth
  on startup by adding:

  "echo disable > /proc/acpi/ibm/bluetooth"

  to /etc/rc.local. When I open gnome-control-center -> Bluetooth and
  click on the "ON/OFF" switch button, it switches on for a fraction of
  a second and then switches back to off. Below are dmesg lines
  corresponding to this event:

  [   94.028110] usb 3-1: new full-speed USB device number 5 using uhci_hcd
  [   94.194320] usb 3-1: New USB device found, idVendor=0a5c, idProduct=2110
  [   94.194325] usb 3-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [   94.194328] usb 3-1: Product: BCM2045B
  [   94.194330] usb 3-1: Manufacturer: Broadcom Corp
  [   94.388169] usb 3-1: USB disconnect, device number 5

  
  The workaround is to type "turn connectivity on/off" combination of my 
keyboard (FN+F5) -- then both wireless and bluetooth go off, and when I type it 
again, bluetooth comes back ON.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu45
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Wed Nov  6 20:41:45 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-10-18 (19 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20131023.2-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3+13.10.20131004-0ubuntu1

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

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

[Desktop-packages] [Bug 1309550] Re: Exec should be "amdxdg-su -c /usr/bin/amdcccle" in ubuntu-amdccclesu.desktop

** Changed in: hwe-next
   Status: New => Triaged

** Changed in: hwe-next
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1309550

Title:
  Exec should be "amdxdg-su -c /usr/bin/amdcccle" in ubuntu-
  amdccclesu.desktop

Status in HWE Next Project:
  Triaged
Status in fglrx-installer package in Ubuntu:
  Fix Released
Status in fglrx-installer-updates package in Ubuntu:
  Fix Released
Status in fglrx-installer source package in Trusty:
  Triaged
Status in fglrx-installer-updates source package in Trusty:
  Triaged

Bug description:
  When trying to open the AMD Catalyst Control Center in Administrative
  mode by using the launcher found in dash, you will be ask to enter
  password for it, but it always shows "su: authentication failure" and
  exit.

  Steps:
  1. Install 14.04 on a I+A system, boot to desktop
  2. Try to open the Control Center in administrative mode by searching AMD in 
dash
  3. Enter password

  Expected result:
  * AMD Catalyst Control Center opened

  Actual result:
  * The authentication windows closed with failure message

  This bug will be a blocker to 14.04 certificate for all I+A (or even
  A+A) GPU switchable systems, since user won't be able to switch
  between GPUs without using the command line commands.

  WORKAROUND:
  run "sudo amdcccle" in the terminal, you will be able to switch between GPUs.

  Exec should be "amdxdg-su -c /usr/bin/amdcccle" in ubuntu-amdccclesu.desktop.
  It must be full patch, otherwise it will fail to be launched.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: fglrx 2:13.350.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Apr 18 21:54:39 2014
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-kittyhawk-kylin-trusty-amd64-20140412-0
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx, 13.350.1, 3.13.0-24-generic, x86_64: installed
   oem-audio-mic-mute-led-1220709, 1.0kittyhawk1, 3.13.0-24-generic, x86_64: 
installed
   oem-touchpad-rmi4-1238726, 0001kittyhawk4, 3.13.0-24-generic, x86_64: 
installed
   tp-smapi, 0.41, 3.13.0-24-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:501d]
  InstallationDate: Installed on 2014-04-16 (1 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140412-08:01
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0011 Validity Sensors, Inc. VFS5011 Fingerprint 
Reader
   Bus 001 Device 003: ID 04f2:b39f Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 8087:07dc Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20AYZ01MCN
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=5a95717e-ff3f-46f7-a0ee-af0dc776f3ae ro quiet splash pcie_aspm=force 
radeon.modeset=0 nouveau.modeset=0 vt.handoff=7
  SourcePackage: fglrx-installer
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J3ET29WW (1.06 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AYZ01MCN
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD PRC DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ3ET29WW(1.06):bd06/25/2013:svnLENOVO:pn20AYZ01MCN:pvrThinkPadS3-S440:rvnLENOVO:rn20AYZ01MCN:rvrWin8STDPRCDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20AYZ01MCN
  dmi.product.version: ThinkPad S3-S440
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-x

[Desktop-packages] [Bug 1371372] Re: Support for Lenovo new TrackPad (ClickPad)

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/1371372

Title:
  Support for Lenovo new TrackPad (ClickPad)

Status in HWE Next Project:
  Confirmed
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  *This bug is under developing

  Affected model:

  L440 - with Ubuntu release: 12.04.5
  w540 - with Ubuntu release: 12.04.5
  X240
  T440p with Ubuntu release: 14.10(daily),  issue reported separately here with 
this bug #1383157

  Description:

  The Lenovo new TrackPad since 2014 starting to unify buttons into
  ClickPad, but in most case for now, upper middle scroll(selection) and
  upper left click, in generally it is not effecting normal use, however
  it is a trouble for user who use Trackpoint(Pointing Stick), which
  makes it useless since there is no wait to scroll with TrackPoint.

  Steps to reproduce:

  1. Open any webpage
  2. Trying to scroll page with TrackPoint

  1. Open any textfile with any editors
  2.  Trying to select and copy some text while using TrackPoint

  Actual result:

  Users need to move their hands off the keyboard and use the bottom of
  touchpad to perform actions all over again.

  Expected results:

  5 buttons on new TrackPad should works as expected.

  -
  Additional information:

  New Trackpad should be supported in Utopic according to this bug:
  https://bugs.launchpad.net/ubuntu/+source/libevdev/+bug/1294515

  -
  Reference information about the unified touchpad:

  ThinkPad TrackPad features promote page:
  http://shop.lenovo.com/us/en/laptops/thinkpad/trackpad/

  Synaptics ClickPad solution:
  http://www.synaptics.com/en/clickpad.php

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1371372/+subscriptions

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

[Desktop-packages] [Bug 1410205] Re: [radeon] Support for AMD Radeon R2 Graphics or R5 M240

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

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

Title:
  [radeon] Support for AMD Radeon R2 Graphics or R5 M240

Status in HWE Next Project:
  Confirmed
Status in xorg package in Ubuntu:
  New

Bug description:
  
  This is a system with APU and GPU, without fglrx driver is running very slow 
with trusty(14.04.1), both fresh install and after upgraded(2014.01.13). 

  Unity is also not fully supported:
  $ /usr/lib/nux/unity_support_test -p
  OpenGL vendor string:   VMware, Inc.
  OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.4, 128 bits)
  OpenGL version string:  2.1 Mesa 10.1.3

  Not software rendered:no
  Not blacklisted:  yes
  GLX fbconfig: yes
  GLX texture from pixmap:  yes
  GL npot or rect textures: yes
  GL vertex program:yes
  GL fragment program:  yes
  GL vertex buffer object:  yes
  GL framebuffer object:yes
  GL version is 1.4+:   yes

  Unity 3D supported:   no

  -
  Effected Devices:
  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Mullins [Radeon R2 Graphics] [1002:9852]
  01:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Jet 
XT [Radeon R5 M240] [1002:6664]

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Jan 13 18:55:27 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R2 Graphics] 
[1002:9852] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:22c2]
 Subsystem: Hewlett-Packard Company Device [103c:22c2]
  InstallationDate: Installed on 2015-01-13 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard Presario CQ45 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic.efi.signed 
root=UUID=74553f05-2b74-46cc-87d3-537a92c0439a ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/03/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: B.0A
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 22C2
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 86.08
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrB.0A:bd04/03/2014:svnHewlett-Packard:pnPresarioCQ45NotebookPC:pvr05A920200:rvnHewlett-Packard:rn22C2:rvrKBCVersion86.08:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: Presario CQ45 Notebook PC
  dmi.product.version: 05A920200
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Jan 13 18:51:53 2015
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1410205/+subscriptions

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

[Desktop-packages] [Bug 1327990] Re: [Dell Inspiron 5447] failed to suspend-resume when using AMD Radeon R7 M260 graphic card [1002:6900]