[Desktop-packages] [Bug 1898483] Re: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all despite the sound bars moving fine and device detected

[Anthony Wong]

** Changed in: alsa-driver (Ubuntu)
 Assignee: (unassigned) => Chris Chiu (mschiu77)

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

Title:
  [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all
  despite the sound bars moving fine and device detected

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The volume bars in sound settings react to what sound is played
  correctly but I can't hear any sounds

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65
  Uname: Linux 5.4.0-49-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  paramvir   1924 F pulseaudio
   /dev/snd/pcmC0D0p:   paramvir   1924 F...m pulseaudio
   /dev/snd/pcmC0D6c:   paramvir   1924 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  5 02:22:25 2020
  InstallationDate: Installed on 2020-04-26 (161 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: Cannon Lake PCH cAVS - sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  paramvir   1924 F pulseaudio
   /dev/snd/pcmC0D0p:   paramvir   1924 F...m pulseaudio
   /dev/snd/pcmC0D6c:   paramvir   1924 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0K1VDX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd07/22/2019:svnDellInc.:pnInspiron7591:pvr:rvnDellInc.:rn0K1VDX:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7591
  dmi.product.sku: 0923
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-04T03:10:08.906233

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1898483/+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 2061254] Re: No mic detected - Ubuntu 24.04 Beta

[Anthony Wong]

** Changed in: alsa-driver (Ubuntu)
 Assignee: (unassigned) => Hui Wang (hui.wang)

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

Title:
  No mic detected - Ubuntu 24.04 Beta

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  On Ubuntu 23.10, my laptop microphone is detected/working fine, but can't be 
detected on Ubuntu 24.04. 
  Tried direct direct install of 24.04 and upgrade fromo 23.10, same problem

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:burnarz   43101 F pipewire
   /dev/snd/controlC0:  burnarz   43106 F wireplumber
   /dev/snd/controlC1:  burnarz   43106 F wireplumber
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 14 01:04:10 2024
  InstallationDate: Installed on 2024-04-13 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240412)
  MachineType: LENOVO 83AR
  PackageArchitecture: all
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/24/2024
  dmi.bios.release: 1.33
  dmi.bios.vendor: LENOVO
  dmi.bios.version: MDCN33WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76461 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad Pro 5 16APH8
  dmi.ec.firmware.release: 1.33
  dmi.modalias: 
dmi:bvnLENOVO:bvrMDCN33WW:bd01/24/2024:br1.33:efr1.33:svnLENOVO:pn83AR:pvrIdeaPadPro516APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrIdeaPadPro516APH8:skuLENOVO_MT_83AR_BU_idea_FM_IdeaPadPro516APH8:
  dmi.product.family: IdeaPad Pro 5 16APH8
  dmi.product.name: 83AR
  dmi.product.sku: LENOVO_MT_83AR_BU_idea_FM_IdeaPad Pro 5 16APH8
  dmi.product.version: IdeaPad Pro 5 16APH8
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2061254/+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 2044191] Re: the sound of my pc crashes when i install a background changer

[Anthony Wong]

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

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

Title:
  the sound of my pc crashes when i install a background changer

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  every thing is ok and the no problem about the package pulseaudio is occured 
just the problem is in my hardware of my device and not from the system 
(software) 
  "left side in my speaker is not working on my hardware"
  sorry about that
  you can delete this report

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2044191/+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 1962349] Re: Bolt doesn't work with native USB4 hosts

[Anthony Wong]

** Also affects: linux (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Also affects: bolt (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-5.14 (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-5.17 (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

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

** Changed in: linux-oem-5.17 (Ubuntu Kinetic)
   Status: New => Invalid

** Changed in: linux-oem-5.14 (Ubuntu Kinetic)
   Status: New => Invalid

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

Title:
  Bolt doesn't work with native USB4 hosts

Status in OEM Priority Project:
  Fix Released
Status in bolt package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in bolt source package in Focal:
  Fix Released
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in bolt source package in Impish:
  Fix Released
Status in linux source package in Impish:
  Won't Fix
Status in linux-oem-5.14 source package in Impish:
  Invalid
Status in linux-oem-5.17 source package in Impish:
  Invalid
Status in bolt source package in Jammy:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in bolt source package in Kinetic:
  New
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-5.14 source package in Kinetic:
  Invalid
Status in linux-oem-5.17 source package in Kinetic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

   * AMD Yellow Carp provides integrated USB4 host controllers
   * When plugging in a Thunderbolt3 or USB4 device, users are unable to 
authorize it using the GUI due to an error message: "parent not authorized, 
deferring"

  [Test Plan]

  AMD Yellow Carp Host (issue this bug is about)
  --
   * Plug in USB4 device or TBT3 to AMD Yellow Carp host
   * Ensure that PCI topology has populated
   * Observe that /sys/bus/thunderbolt/devices/DEVICE/authorized is "0"
   * Try to run `boltctl enroll $UUID`

  Alpine Ridge / Titan Ridge host (discrete controller)
  --
  Start out on a host with discrete controller (Alpine Ridge or Titan Ridge)
  1. sudo boltctl forget -a
  2. Plug in dock
  3. Make sure 'boltctl list' enumerates dock.
  4. Check /sys/bus/thunderbolt/devices/domain0/iommu_dma_protection (value 
dependent upon host)
     - If 0; try to manually enroll using 'boltctl enroll $UUID'
     - If 1; ensure that device automatically enrolled with bolt.

  GUI Check
  -
  Ensure that devices show up in the Settings GUI and are now able to authorize.
  Note: for AMD platforms enumerating PCIe devices is a separate problem from 
BOLT handled by kernel tasks.  GUI check is only about "authorization".

  [Where problems could occur]

   * Intel USB4 or TBT3 hosts also use bolt.  They could have a problem with 
the new version of bolt.
   * This is very unlikely however since there is a through test suite, and up 
until now the entire industry has been using bolt on Intel controllers for a 
long time.
   * There haven't been any significant bugs reported upstream or in Ubuntu 
since 0.9.1 release.

  [Other Info]
   * This bug also occurs on Intel controllers from ICL, TGL or ALD, but in 
many cases they are automatically authorized to an iommu DMA policy.
   * It is fixed in bolt 0.9.1 or later release.
   * To solve the SRU, will backport 0.9.1 release from Impish.
   * I did look into backporting just the commit(s) for fixing this, but it's 
not a trivial backport.  Quoting the changelog 
(https://gitlab.freedesktop.org/bolt/bolt/-/blob/master/CHANGELOG.md): 
"Additionally the unique_id of said host controller changes with every boot, 
which breaks one of the fundamental assumptions in boltd".

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1962349/+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 1940377] Re: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute.

[Anthony Wong]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => AaronMa (mapengyu)

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

Title:
  The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work
  after install Ubuntu Hirsute.

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

Bug description:
  u@u-ThinkPad-L460:~$ uname -a
  Linux u-ThinkPad-L460 Kernel 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 
20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

  u@u-ThinkPad-L460:~$ cat /etc/issue
  Ubuntu 21.04 \n \l

  CPU : Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz
  WWAN : 12d1:15c1 Huawei Technologies Co., Ltd. ME906s LTE M.2 Module

  [Steps]
  1. Make a Live CD for Ubuntu Hirsute
  2. Plug in the Live CD
  3. Boot ThinkPad L460
  4. Install Ubuntu Hirsute and completed all configurations
  5. Make sure the installation done
  6. Boot the system and log in
  7. Enable the proposed channel
  8. Do the update and upgrade
  9. Reboot the system and check mmcli is upgraded to 1.16.6
  7. Verify the WWAN working or not.

  [Actual result]
  The WWAN can not be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubuntu-release-upgrader-core 1:21.04.16
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  Date: Wed Aug 18 01:32:17 2021
  InstallationDate: Installed on 2021-08-18 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2021-08-18 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  IpRoute:
   default via 10.1.1.1 dev wlp3s0 proto dhcp metric 600 
   10.1.1.0/24 dev wlp3s0 proto kernel scope link src 10.1.1.106 metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.30.0-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Tags:  hirsute
  Uname: Linux 5.11.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.30.0   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940377/+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 1940377] Re: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute.

[Anthony Wong]

** Also affects: linux (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/1940377

Title:
  The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work
  after install Ubuntu Hirsute.

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

Bug description:
  u@u-ThinkPad-L460:~$ uname -a
  Linux u-ThinkPad-L460 Kernel 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 
20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

  u@u-ThinkPad-L460:~$ cat /etc/issue
  Ubuntu 21.04 \n \l

  CPU : Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz
  WWAN : 12d1:15c1 Huawei Technologies Co., Ltd. ME906s LTE M.2 Module

  [Steps]
  1. Make a Live CD for Ubuntu Hirsute
  2. Plug in the Live CD
  3. Boot ThinkPad L460
  4. Install Ubuntu Hirsute and completed all configurations
  5. Make sure the installation done
  6. Boot the system and log in
  7. Enable the proposed channel
  8. Do the update and upgrade
  9. Reboot the system and check mmcli is upgraded to 1.16.6
  7. Verify the WWAN working or not.

  [Actual result]
  The WWAN can not be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubuntu-release-upgrader-core 1:21.04.16
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  Date: Wed Aug 18 01:32:17 2021
  InstallationDate: Installed on 2021-08-18 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2021-08-18 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  IpRoute:
   default via 10.1.1.1 dev wlp3s0 proto dhcp metric 600 
   10.1.1.0/24 dev wlp3s0 proto kernel scope link src 10.1.1.106 metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.30.0-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Tags:  hirsute
  Uname: Linux 5.11.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.30.0   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940377/+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 1894606] Re: [SRU] Add profile-set for HP Thunderbolt Dock

[Anthony Wong]

** 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 pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1894606

Title:
  [SRU] Add profile-set for HP Thunderbolt Dock

Status in HWE Next:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  HP Thunderbolt Dock has a USB audio device provides headset connector 
functionality. The Dock can also attach an optional USB audio module. Since 
they are both USB audio device, the input/output names are the same and it 
confuses user.

  [Fix]
  Add PulseAudio profile-sets for each USB device with different monikers.

  The merge request is already approved by maintainer, will be merged after 
14.0 release:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/353

  [Test]
  With profile-set applied, two different USB audio device on HP TBT Dock have 
distinctive names.

  [Regression Potential]
  Currently I can't think of any regression risk, as this SRU only adds new 
profile-sets and description translation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1894606/+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 1908167] Re: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic

[Anthony Wong]

** Description changed:

  [Impact]
  On the Dell AIO machines, there is no internal mic, after plugging a
  headset, users expect the headset-mic or headphone-mic could be selected
  automatically. But with the current rule, the headset-mic/headphone-mic will 
not be selected automatically and even users manually select them, they will 
not show up in the gnome sound setting, and users could not record sound by 
headset-mic/headphone-mic.
  
  [Fix]
  backport a patch from pulseaudio mergerequest, the patch is going to be
  merged to pulseaudio 14.1. This patch could be backported to hirsute without 
any change, but need to be changed if backport it to groovy and focal.
  
  [Test]
- On those Dell AIO, plug a headset, open the gnome sound setting, the 
headset-mic is selected automatically, use the headset-mic to record the sound, 
the sound could be recorded and the sound quality is good.
+ With the old pulseaudio (prior to 1:13.99.1-1ubuntu3.10), plugging in a 
headset to the problematic Dell AIO machine will not automatically select 
headset-mic/headphone-mic, and they also do not show up in Gnome sound 
settings, leading to failure to record any sound.
+ 
+ With the new proposed package, on those Dell AIO, plug a headset, open
+ the gnome sound setting, the headset-mic is selected automatically, use
+ the headset-mic to record the sound, the sound could be recorded and the
+ sound quality is good.
  
  [Where problems could occur]
  This patch could change the policy of audio device switching, it will not
  affect all audio devices, but only the devices which has AVAIL_UNKNOWN 
available status, that means it has possibility to introduce the regression on 
headphone-mic ,headset-mic, internal mic and internal speaker's switching since 
they all has AVAIL_UNKNOWN status. For example, after unpluging the headset, 
the input device will not switch to internal mic automatically or after unplug 
the headphone, the output device will not switch to internal speaker 
automatically. But this possibility is very low, we have tested the patch on 
many Dell and Lenovo machines, all worked well.

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

Title:
  [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be
  selected automatically if there is no internal mic

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Committed
Status in pulseaudio source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  On the Dell AIO machines, there is no internal mic, after plugging a
  headset, users expect the headset-mic or headphone-mic could be selected
  automatically. But with the current rule, the headset-mic/headphone-mic will 
not be selected automatically and even users manually select them, they will 
not show up in the gnome sound setting, and users could not record sound by 
headset-mic/headphone-mic.

  [Fix]
  backport a patch from pulseaudio mergerequest, the patch is going to be
  merged to pulseaudio 14.1. This patch could be backported to hirsute without 
any change, but need to be changed if backport it to groovy and focal.

  [Test]
  With the old pulseaudio (prior to 1:13.99.1-1ubuntu3.10), plugging in a 
headset to the problematic Dell AIO machine will not automatically select 
headset-mic/headphone-mic, and they also do not show up in Gnome sound 
settings, leading to failure to record any sound.

  With the new proposed package, on those Dell AIO, plug a headset, open
  the gnome sound setting, the headset-mic is selected automatically,
  use the headset-mic to record the sound, the sound could be recorded
  and the sound quality is good.

  [Where problems could occur]
  This patch could change the policy of audio device switching, it will not
  affect all audio devices, but only the devices which has AVAIL_UNKNOWN 
available status, that means it has possibility to introduce the regression on 
headphone-mic ,headset-mic, internal mic and internal speaker's switching since 
they all has AVAIL_UNKNOWN status. For example, after unpluging the headset, 
the input device will not switch to internal mic automatically or after unplug 
the headphone, the output device will not switch to internal speaker 
automatically. But this possibility is very low, we have tested the patch on 
many Dell and Lenovo machines, all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1908167/+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 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time

[Anthony Wong]

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

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => Hui Wang (hui.wang)

** Changed in: alsa-ucm-conf (Ubuntu)
 Assignee: (unassigned) => Hui Wang (hui.wang)

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

Title:
  The rear panel of Lenovo P620 doesn't support more than one audio
  device at the same time

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in alsa-ucm-conf package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After backporting following patches from PA and alsa-ucm-conf and then
  it works.

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355

  https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB-
  Audio

  Here is the test PPA:
  https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test

  Since the upstream not yet accepted those patches, the regression
  potential may quite high.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1902464/+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 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620

[Anthony Wong]

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

** 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 pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1891461

Title:
  Add proper USB audio support for Lenovo ThinkStation P620

Status in HWE Next:
  Fix Released
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Released
Status in alsa-lib source package in Groovy:
  Fix Released
Status in alsa-ucm-conf source package in Groovy:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its 
chipset. Instead, it's equipped with two USB audio devices, "Main", which is 
for internal speaker and front headset, and "Rear", which is for rear panel 
I/Os.

  However, both USB audio don't really work out of the box. Issues and
  fixes will be described together below.

  [Fix for alsa-lib]
  1) Both USB audio devices don't have S/PDIF port, so we need to disable them:
  
https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb

  [Fix for alsa-ucm-conf]
  2) PulseAudio doesn't assign the correct stream for "Main" device, audio 
output stays at "Speaker" after "Headset" is selected. So we need UCM to let 
PulseAudio understand correct stream assignment.
  In addition to that, in order to not let headset port availability invalidate 
speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" 
logically:
  https://github.com/alsa-project/alsa-ucm-conf/pull/42

  [Fix for PulseAudio]
  3) USB audio devices, UAC v2 and v3, support jack detection (insertion 
control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack 
detection doesn't work at userspace level. We need to let PulseAudio be aware 
those jacks:
  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b

  4) When a headset gets plugged, PulseAudio switches the profile from 
"Speaker" to "Headset" automatically. However, when headset gets unplugged, 
PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" 
profile. We need to fix priorities for profiles that are created from UCM to 
avoid the problem:
  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f

  [Test]
  Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are 
all selectable. Sound comes out from speaker even if "Headphone" is chosen. 
Microphone is already selected though there's no microphone plugged.

  With the above fix all applied, open Gnome Control Center -> Sound tab.
  Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down 
menu.
  Plug a headset to front port, "Headphone" and "Microphone" appears and 
automatically becomes default. Unplug the headset, sink switches back to 
"Speaker", and source switches to none.
  Plug line-in, line-out and microphone to the rear panel, jack detection works 
for all three ports, and they all work correctly. Unplug rear line-in, line-out 
or microphone makes the option in dropdown menu disappears.

  On other systems, nothing changed.

  [Regression Potential]
  For fix 1) and 2), The UCM in alsa-lib and alsa-ucm-conf strictly match 
kernel provided profile name, so no other device will be affected.

  For fix 3), if there are UAC v2/v3 devices claim to support jack detection 
but don't really support it, this will make the PulseAudio consider its 
availability to "no".
  AFAIK, the USB audios that have jack ports are mostly docking stations, which 
already have their own UCM profiles or PulseAudio profile-sets, so they are 
unaffected by this change.
  If we ever see this kind of regression, the proper fix is to disable jack 
detection from kernel side.

  For fix 4), if user depends on the old behavior (i.e. switch to
  another card while other profiles are still available), this will
  bring a behavioral change. However, all available profiles will still
  be available after the fix, so users can still be chose the preferred
  profile from the g-c-c dropdown menu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1891461/+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 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620

[Anthony Wong]

** Tags added: originate-from-1887127 originate-from-1887878 sutton

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

Title:
  Add proper USB audio support for Lenovo ThinkStation P620

Status in alsa-lib package in Ubuntu:
  New
Status in alsa-ucm-conf package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  In Progress
Status in alsa-lib source package in Focal:
  New
Status in alsa-ucm-conf source package in Focal:
  New
Status in pulseaudio source package in Focal:
  In Progress
Status in alsa-lib source package in Groovy:
  New
Status in alsa-ucm-conf source package in Groovy:
  New
Status in pulseaudio source package in Groovy:
  In Progress

Bug description:
  [Impact]
  Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its 
chipset. Instead, it's equipped with two USB audio devices, "Main", which is 
for internal speaker and front headset, and "Rear", which is for rear panel 
I/Os.

  However, both USB audio don't really work out of the box. Issues and
  fixes will be described together below.

  [Fix for alsa-lib]
  1) Both USB audio devices don't have S/PDIF port, so we need to disable them:
  
https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb

  [Fix for alsa-ucm-conf]
  2) PulseAudio doesn't assign the correct stream for "Main" device, audio 
output stays at "Speaker" after "Headset" is selected. So we need UCM to let 
PulseAudio understand correct stream assignment.
  In addition to that, in order to not let headset port availability invalidate 
speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" 
logically:
  https://github.com/alsa-project/alsa-ucm-conf/pull/42

  [Fix for PulseAudio]
  3) USB audio devices, UAC v2 and v3, support jack detection (insertion 
control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack 
detection doesn't work at userspace level. We need to let PulseAudio be aware 
those jacks:
  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b

  4) When a headset gets plugged, PulseAudio switches the profile from 
"Speaker" to "Headset" automatically. However, when headset gets unplugged, 
PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" 
profile. We need to fix priorities for profiles that are created from UCM to 
avoid the problem:
  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f

  [Test]
  Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are 
all selectable. Sound comes out from speaker even if "Headphone" is chosen. 
Microphone is already selected though there's no microphone plugged.

  With the above fix all applied, open Gnome Control Center -> Sound tab.
  Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down 
menu.
  Plug a headset to front port, "Headphone" and "Microphone" appears and 
automatically becomes default. Unplug the headset, sink switches back to 
"Speaker", and source switches to none.
  Plug line-in, line-out and microphone to the rear panel, jack detection works 
for all three ports, and they all work correctly. Unplug rear line-in, line-out 
or microphone makes the option in dropdown menu disappears.

  On other systems, nothing changed.

  [Regression Potential]
  For fix 1) and 2), The UCM in alsa-lib and alsa-ucm-conf strictly match 
kernel provided profile name, so no other device will be affected.

  For fix 3), if there are UAC v2/v3 devices claim to support jack detection 
but don't really support it, this will make the PulseAudio consider its 
availability to "no".
  AFAIK, the USB audios that have jack ports are mostly docking stations, which 
already have their own UCM profiles or PulseAudio profile-sets, so they are 
unaffected by this change.
  If we ever see this kind of regression, the proper fix is to disable jack 
detection from kernel side.

  For fix 4), if user depends on the old behavior (i.e. switch to
  another card while other profiles are still available), this will
  bring a behavioral change. However, all available profiles will still
  be available after the fix, so users can still be chose the preferred
  profile from the g-c-c dropdown menu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1891461/+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 1882248] Re: [SRU] plug headset won't proper reconfig ouput to it on machine with default output

[Anthony Wong]

** 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 pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1882248

Title:
  [SRU] plug headset won't proper reconfig ouput to it on machine with
  default output

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Released

Bug description:
  This is for pulseaudio bionic:

  [Impact]
  On a Dell machine without internal spk and internal mic, after freshly
  install the bionic on it, the active profile is Off, after users plug a
  headset to it and users select the headset from the pop-up dialogue,
  users expect the profile changes to analog-stereo (headset is on it),
  but the active_profile is still Off.

  [Fix]
  Upstream already has a patch to fix it, cherrypiack that patch to bionic.
  And that patch is already in the eoan, focal, ...

  [Test Case]
  freshly install the bionic with this patch on that dell machine,
  plug headset and select the headset from UI, the profile changes to
  analog-stereo, and play some sound, we could hear it from the headset

  [Regression Risk]
  Low, this patch is already in the upstream for a long time, and it is
  already in the eoan and focal.


  
  For linux kernel (oem-b):

  [Impact]
  On a Dell machine without internal spk and internal mic, after freshly
  install the bionic on it, and users plug a headset, the sound couldn't
  output from headset.

  [Fix]
  reverse the order of headset mic and headphone mic

  [Test Case]
  freshly install the bionic with this patch on that dell machine,
  plug headset and play sound, we could hear the sound from headset.

  [Regression Risk]
  Low, this patch only affects the machine without internal mic and
  internal spk, and I already tested this patch on the machine without
  internal mic and internal spk, it worked well.

  target machine does not have built-in speaker, and the monitor does
  not have an audio output (like d-sub VGA)

  As first boot, there will be a "dummy output" in g-c-c.

  After plug-in headset, there will be a headset appear in g-c-c, but it
  won't be automatically selected even it's chosen in the pop-up window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1882248/+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 1889217] Re: Make digital mic on the AMD Renoir machines work under gnome desktop

[Anthony Wong]

** Tags added: originate-from-1874593 sutton

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

Title:
  Make digital mic on the AMD Renoir machines work under gnome desktop

Status in alsa-lib package in Ubuntu:
  New
Status in alsa-ucm-conf package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New
Status in alsa-lib source package in Focal:
  New
Status in alsa-ucm-conf source package in Focal:
  New
Status in pulseaudio source package in Focal:
  New
Status in alsa-lib source package in Groovy:
  New
Status in alsa-ucm-conf source package in Groovy:
  New
Status in pulseaudio source package in Groovy:
  New

Bug description:
  [Impact]
  On the LENOVO AMD Renoir machines, there is a digital mic directly
  connected to the APU instead of the codec, so there are two separate
  sound cards in the system, one is for analogue codec driven by hda
  driver, the other is for the dmic driven by ASoC acp driver.

  The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't
  support this design yet, it could support all audio devices on the codec
  well, but it doesn't support that dmic well. In the gnome-control-center,
  the dmic becomes two input devices: analog input and multichannel input,
  and users can only record sound from analog input, the multichannel input
  can't function at all. Besides this issue, there is another issue, after
  users plug an external mic, the external mic can't replace the dmic
  automatically, this gives users a bad experience since this behaviour is
  different from the other audio designs.

  [Fix for pulseaudio]
  backport 3 patches:
  2 of them from upstream
  device-port: queue CARD CHANGE event before update default sink
  alsa: adjust ucm sink/source priority according to ports priority
  1 of them from a merge request:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305

  [Fix for alsa-ucm-conf]
  backport 14 patches:
  11 of them from upstream:
  ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch
  ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch
  sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch
  ucm.conf-add-support-for-the-kernel-module-name-tree.patch
  sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch
  sof-soundwire-initial-UCM2-version.patch
  sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch
  sof-soundwire-rewrite-for-syntax-3.patch
  HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch
  Fix-invalid-Regex-Type-in-various-Condition-blocks.patch
  hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch
  3 of them from a merge request:
  https://github.com/alsa-project/alsa-ucm-conf/pull/41

  [Fix for alsa-lib]
  backport 47 patches from upstream:
  Enabled-extended-namehints-in-alsa.conf.patch
  conf-add-snd_config_is_array-function.patch
  topology-use-snd_config_is_array-function.patch
  ucm-merge-the-array-items-from-the-condition-blocks.patch
  ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch
  ucm-execute-SectionDefaults-lately-when-the-first-ve.patch
  ucm-handle-set-_once-command.patch
  ucm-handle-set-_defaults-command.patch
  ucm-initialize-mgr-once_list.patch
  ucm-fix-SectionOnce-comment.patch
  ucm-fix-compilation-error-in-set_defaults_user.patch
  ucm-rename-SectionOnce-to-BootSequence.patch
  ucm-rename-_once-command-to-_boot-command.patch
  ucm-configuration-implement-in-place-Include.patch
  ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch
  ucm-config-substitute-File-string-to-allow-variables.patch
  ucm-configuration-allow-to-define-the-configuration-.patch
  ucm-configuration-add-DefineRegex.patch
  ucm-substitute-arguments-in-sequences.patch
  ucm-allow-syntax-version-3.patch
  ucm-config-change-the-in-place-include-evaluation-or.patch
  ucm-allow-to-specify-the-toplevel-directory-using-as.patch
  ucm-substitute-also-value-strings.patch
  ucm-handle-strict-prefix-correctly-for-the-UCM-card-.patch
  ucm-String-condition-implement-Empty.patch
  ucm-Define-DefineRegex-is-supported-in-Syntax-3.patch
  ucm-substitute-OpenName.patch
  ucm-substitute-CardNumber.patch
  ucm-implement-the-toplevel-ucm-configuration-file-pa.patch
  ucm-substitute-device-modifier-names-too.patch
  ucm-substitute-device-strings-in-the-device-lists.patch
  ucm-substitute-component-sequence-string.patch
  ucm-substitute-verb-name-and-file-field.patch
  ucm-substitute-Comment-in-Transition-and-Device.patch
  ucm-substitute-RenameDevice-and-DeleteDevice-lists.patch
  ucm-substitute-arguments-in-sequences-only-for-synta.patch
  ucm-shuffle-code-in-compound_merge.patch
  ucm-implement-CardIdByName-substitution.patch
  ucm-allow-to-ignore-errors-for-the-value-substitutio.patch
  ucm-allow-to-use-the-defined-variables-in-the-substi.patch
  ucm-implement-CardNumberByName-substitution.patch
  ucm-fix-the-possible-buffer-overflow-substitution.patch
  

[Desktop-packages] [Bug 1889217] Re: Make digital mic on the AMD Renoir machines work under gnome desktop

[Anthony Wong]

** Summary changed:

- Make digital mic on the AMD renoir machines work under gnome desktop
+ Make digital mic on the AMD Renoir machines work under gnome desktop

** Description changed:

  [Impact]
- On the LENOVO AMD renoir machines, there is a digital mic directly
+ On the LENOVO AMD Renoir machines, there is a digital mic directly
  connected to the APU instead of the codec, so there are two separate
  sound cards in the system, one is for analogue codec driven by hda
  driver, the other is for the dmic driven by ASoC acp driver.
  
  The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't
  support this design yet, it could support all audio devices on the codec
  well, but it doesn't support that dmic well. In the gnome-control-center,
  the dmic becomes two input devices: analog input and multichannel input,
  and users can only record sound from analog input, the multichannel input
  can't function at all. Besides this issue, there is another issue, after
  users plug an external mic, the external mic can't replace the dmic
  automatically, this gives users a bad experience since this behaviour is
  different from the other audio designs.
  
  [Fix for pulseaudio]
  backport 3 patches:
  2 of them from upstream
  device-port: queue CARD CHANGE event before update default sink
  alsa: adjust ucm sink/source priority according to ports priority
  1 of them from a merge request:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305
  
  [Fix for alsa-ucm-conf]
  backport 14 patches:
  11 of them from upstream:
  ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch
  ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch
  sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch
  ucm.conf-add-support-for-the-kernel-module-name-tree.patch
  sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch
  sof-soundwire-initial-UCM2-version.patch
  sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch
  sof-soundwire-rewrite-for-syntax-3.patch
  HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch
  Fix-invalid-Regex-Type-in-various-Condition-blocks.patch
  hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch
  3 of them from a merge request:
  https://github.com/alsa-project/alsa-ucm-conf/pull/41
  
  [Fix for alsa-lib]
  backport 47 patches from upstream:
  Enabled-extended-namehints-in-alsa.conf.patch
  conf-add-snd_config_is_array-function.patch
  topology-use-snd_config_is_array-function.patch
  ucm-merge-the-array-items-from-the-condition-blocks.patch
  ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch
  ucm-execute-SectionDefaults-lately-when-the-first-ve.patch
  ucm-handle-set-_once-command.patch
  ucm-handle-set-_defaults-command.patch
  ucm-initialize-mgr-once_list.patch
  ucm-fix-SectionOnce-comment.patch
  ucm-fix-compilation-error-in-set_defaults_user.patch
  ucm-rename-SectionOnce-to-BootSequence.patch
  ucm-rename-_once-command-to-_boot-command.patch
  ucm-configuration-implement-in-place-Include.patch
  ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch
  ucm-config-substitute-File-string-to-allow-variables.patch
  ucm-configuration-allow-to-define-the-configuration-.patch
  ucm-configuration-add-DefineRegex.patch
  ucm-substitute-arguments-in-sequences.patch
  ucm-allow-syntax-version-3.patch
  ucm-config-change-the-in-place-include-evaluation-or.patch
  ucm-allow-to-specify-the-toplevel-directory-using-as.patch
  ucm-substitute-also-value-strings.patch
  ucm-handle-strict-prefix-correctly-for-the-UCM-card-.patch
  ucm-String-condition-implement-Empty.patch
  ucm-Define-DefineRegex-is-supported-in-Syntax-3.patch
  ucm-substitute-OpenName.patch
  ucm-substitute-CardNumber.patch
  ucm-implement-the-toplevel-ucm-configuration-file-pa.patch
  ucm-substitute-device-modifier-names-too.patch
  ucm-substitute-device-strings-in-the-device-lists.patch
  ucm-substitute-component-sequence-string.patch
  ucm-substitute-verb-name-and-file-field.patch
  ucm-substitute-Comment-in-Transition-and-Device.patch
  ucm-substitute-RenameDevice-and-DeleteDevice-lists.patch
  ucm-substitute-arguments-in-sequences-only-for-synta.patch
  ucm-shuffle-code-in-compound_merge.patch
  ucm-implement-CardIdByName-substitution.patch
  ucm-allow-to-ignore-errors-for-the-value-substitutio.patch
  ucm-allow-to-use-the-defined-variables-in-the-substi.patch
  ucm-implement-CardNumberByName-substitution.patch
  ucm-fix-the-possible-buffer-overflow-substitution.patch
  ucm-simplify-get_by_card-in-parser.c.patch
  ucm-implement-AlwaysTrue-Condition.Type.patch
  ucm-Allow-empty-strings-in-var-.-substitutions.patch
  ucm-substitution-remove-duplicate-allow_empty-assign.patch
  ucm-fix-parse_get_safe_name-safe-name-must-be-checke.patch
  ucm-substitute-the-merged-tree-completely.patch
  add Breaks alsa-ucm-conf (<= 1.2.2-1ubuntu0.1) in the d/control
  add snd_config_is_array@ALSA_0.9 1.2.2-2.1ubuntu1 in the d/libasound2.symbols
  
  [Test Case]
  On the AMD Renoir machines:
  

[Desktop-packages] [Bug 1889217] Re: Make digital mic on the AMD renoir machines work under gnome desktop

[Anthony Wong]

** Description changed:

  [Impact]
  On the LENOVO AMD renoir machines, there is a digital mic directly
  connected to the APU instead of the codec, so there are two separate
  sound cards in the system, one is for analogue codec driven by hda
  driver, the other is for the dmic driven by ASoC acp driver.
  
  The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't
  support this design yet, it could support all audio devices on the codec
  well, but it doesn't support that dmic well. In the gnome-control-center,
  the dmic becomes two input devices: analog input and multichannel input,
  and users can only record sound from analog input, the multichannel input
  can't function at all. Besides this issue, there is another issue, after
  users plug an external mic, the external mic can't replace the dmic
  automatically, this gives users a bad experience since this behaviour is
  different from the other audio designs.
  
  [Fix for pulseaudio]
  backport 3 patches:
  2 of them from upstream
  device-port: queue CARD CHANGE event before update default sink
  alsa: adjust ucm sink/source priority according to ports priority
  1 of them from a merge request:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305
  
  [Fix for alsa-ucm-conf]
  backport 14 patches:
  11 of them from upstream:
  ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch
  ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch
  sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch
  ucm.conf-add-support-for-the-kernel-module-name-tree.patch
  sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch
  sof-soundwire-initial-UCM2-version.patch
  sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch
  sof-soundwire-rewrite-for-syntax-3.patch
  HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch
  Fix-invalid-Regex-Type-in-various-Condition-blocks.patch
  hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch
  3 of them from a merge request:
  https://github.com/alsa-project/alsa-ucm-conf/pull/41
  
  [Fix for alsa-lib]
  backport 47 patches from upstream:
  Enabled-extended-namehints-in-alsa.conf.patch
  conf-add-snd_config_is_array-function.patch
  topology-use-snd_config_is_array-function.patch
  ucm-merge-the-array-items-from-the-condition-blocks.patch
  ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch
  ucm-execute-SectionDefaults-lately-when-the-first-ve.patch
  ucm-handle-set-_once-command.patch
  ucm-handle-set-_defaults-command.patch
  ucm-initialize-mgr-once_list.patch
  ucm-fix-SectionOnce-comment.patch
  ucm-fix-compilation-error-in-set_defaults_user.patch
  ucm-rename-SectionOnce-to-BootSequence.patch
  ucm-rename-_once-command-to-_boot-command.patch
  ucm-configuration-implement-in-place-Include.patch
  ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch
  ucm-config-substitute-File-string-to-allow-variables.patch
  ucm-configuration-allow-to-define-the-configuration-.patch
  ucm-configuration-add-DefineRegex.patch
  ucm-substitute-arguments-in-sequences.patch
  ucm-allow-syntax-version-3.patch
  ucm-config-change-the-in-place-include-evaluation-or.patch
  ucm-allow-to-specify-the-toplevel-directory-using-as.patch
  ucm-substitute-also-value-strings.patch
  ucm-handle-strict-prefix-correctly-for-the-UCM-card-.patch
  ucm-String-condition-implement-Empty.patch
  ucm-Define-DefineRegex-is-supported-in-Syntax-3.patch
  ucm-substitute-OpenName.patch
  ucm-substitute-CardNumber.patch
  ucm-implement-the-toplevel-ucm-configuration-file-pa.patch
  ucm-substitute-device-modifier-names-too.patch
  ucm-substitute-device-strings-in-the-device-lists.patch
  ucm-substitute-component-sequence-string.patch
  ucm-substitute-verb-name-and-file-field.patch
  ucm-substitute-Comment-in-Transition-and-Device.patch
  ucm-substitute-RenameDevice-and-DeleteDevice-lists.patch
  ucm-substitute-arguments-in-sequences-only-for-synta.patch
  ucm-shuffle-code-in-compound_merge.patch
  ucm-implement-CardIdByName-substitution.patch
  ucm-allow-to-ignore-errors-for-the-value-substitutio.patch
  ucm-allow-to-use-the-defined-variables-in-the-substi.patch
  ucm-implement-CardNumberByName-substitution.patch
  ucm-fix-the-possible-buffer-overflow-substitution.patch
  ucm-simplify-get_by_card-in-parser.c.patch
  ucm-implement-AlwaysTrue-Condition.Type.patch
  ucm-Allow-empty-strings-in-var-.-substitutions.patch
  ucm-substitution-remove-duplicate-allow_empty-assign.patch
  ucm-fix-parse_get_safe_name-safe-name-must-be-checke.patch
  ucm-substitute-the-merged-tree-completely.patch
  add Breaks alsa-ucm-conf (<= 1.2.2-1ubuntu0.1) in the d/control
  add snd_config_is_array@ALSA_0.9 1.2.2-2.1ubuntu1 in the d/libasound2.symbols
  
  [Test Case]
- On the AMD renoir machines:
- Boot the system with these updated packages (already backported kernel
- drivers to focal and oem-5.6 kernels), open the gnome-control-center,
- we could see the digital mic in the input device tab, and only one
- input device. we 

[Desktop-packages] [Bug 1882161] Re: module-switch-on-port-avaiable: switch the port on ucm devices based on the priority

[Anthony Wong]

** 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 pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1882161

Title:
  module-switch-on-port-avaiable: switch the port on ucm devices based
  on the priority

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * On the Dell machines with multi function audio jack, the
     headphone/headset can't output sound automatically, which is different
     from ubuntu 18.04. The headphone/headset should be able to  output
     sound automatically after plugging in the audio jack.

  [Test Case]

   * On Tiger Lake platform
     Reproduce step:
     1. plug headphone/headset
     2. open g-c-c sound to check

     Expect result: The output device should switch to headphone or headset,
    since headphone's priority is higher in ucm2 config.
     Actual result: The output device is still internal speaker.

  [Regression Potential]

   * The change insert the ucm device by its priority, the potential
 regression is low, since if the change is not working properly, the 
 side effect is that the order of ucm devices are wrong, and it won't 
 switch to the correct output device as expect, but user can still
 config it manually.

  [Other]

   * This bug originates from an OEM private bug #1875597, then ubuntu users
     reported 2 public bugs #1871329 and #1881659. The 2nd issue of #1871329
     and the 1st issue of #1881659 have the same root cause as #1875597

   * The root cause is the ucm2 conf defines 2 input devices: the Mic2 and
     Headset MIC, and the pulseaudio parse the input device Headset MIC
     first then Mic2, finally the audio jack is set to Mic2 mode, this make
     the audio jack can't output sound anymore. To fix it, let the audio
     jack set to Headset MIC mode by default (Headset MIC has higher
     priority than Mic2 in the ucm2 conf), to do so, let pulseaudio send the
     device event to module-switch-on-port-available by the order of
     priority in the umc2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1882161/+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 1883497] Re: Only timing mode list in EDID supported on continuous freq monitors

[Anthony Wong]

** Also affects: xorg-server (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  Only timing mode list in EDID supported on continuous freq monitors

Status in HWE Next:
  New
Status in X.Org X server:
  New
Status in xf86-video-intel:
  Unknown
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Bionic:
  New
Status in xorg-server source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  Some new laptop display set EDID continuous freq bit 1.
  Then Xorg only uses the timing modes defined in EDID, no other modes are 
shown on Xorg.

  Upstream Bug:
  https://gitlab.freedesktop.org/drm/intel/-/issues/313

  Fix of Xorg in merge request:
  https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/421

  
https://cgit.freedesktop.org/xorg/xserver/commit/?id=6a79a737e2c0bc730ee693b4ea4a1530c108be4e

  this is required to support new laptop models which use such panels

  [Test case]
  Test that a proper list of modes is shown with a panel that uses the new EDID.

  [Regression potential]
  The patch retains the previous code path for setting modes on GTF-able 
monitors, and only adds support for non-GTF monitors. So in that sense there 
shouldn't be any regression potential, this has been reviewed by an upstream 
expert.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1883497/+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 1881549] Re: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke

[Anthony Wong]

Also verified on Claire's laptop and the propose package works fine.

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

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

Title:
  BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi
  broke

Status in wpa package in Ubuntu:
  Fix Released
Status in wpa source package in Focal:
  Fix Committed
Status in wpa source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * A driver supports FT (IEEE 802.11r-2008 or fast BSS transition (FT),
 also called fast roaming) if it either supports SME or the
 NL80211_CMD_UPDATE_FT_IES command. When selecting AKM suites,
 wpa_supplicant currently doesn't take into account whether or not either
 of those conditions are met. This can cause association failures, e.g.,
 when an AP supports both WPA-EAP and FT-EAP but the driver doesn't
 support FT (wpa_supplicant will decide to do FT-EAP since it is unaware
 the driver doesn't support it).

   * This is known to affect users at least users with popular chip-sets,
 such as BCM20703A1 or BCM4350 (notably present in the popular XPS 13/15
 laptops).

   * The upload fixes the bug by allowing an FT suite to be selected only
 when the driver also supports FT.

  [Test Case]

   * requires affected hardware and wpa_supplicant built with CONFIG_IEEE80211R
 and connecting to an AP supporting WPA-EAP and FT-EAP

  [Regression Potential]

   * a driver not advertising correctly its support for SME or the
 NL80211_CMD_UPDATE_FT_IES command via the drv_flags would be prevented from
 using FT but would still be able to connect to APs

  [Other Info]

   * Upstream fix: 
https://w1.fi/cgit/hostap/commit/?id=23dc196fde951b3d508f367a603cddffbd053490
   * Initial report: https://bugs.archlinux.org/task/63397
  ---

  Upgraded to 20.04 and the wifi broke.  It was working fine on 18.04.  Tried a 
variety of things with apw but nada.  /var/log attached
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1438 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-07-09 (329 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. XPS 15 9550
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=f73bcd37-31c3-4314-81cf-102bfd94a03e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-33-generic N/A
   linux-backports-modules-5.4.0-33-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-21 (12 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.1
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9550
  dmi.product.sku: 06E4
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1881549/+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 1881549] Re: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke

[Anthony Wong]

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

** Changed in: wpa (Ubuntu Focal)
   Status: New => Confirmed

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

Title:
  BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi
  broke

Status in linux package in Ubuntu:
  Invalid
Status in wpa package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Invalid
Status in wpa source package in Focal:
  Confirmed
Status in linux source package in Groovy:
  Invalid
Status in wpa source package in Groovy:
  Confirmed

Bug description:
  Upgraded to 20.04 and the wifi broke.  It was working fine on 18.04.  Tried a 
variety of things with apw but nada.  /var/log attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1438 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-07-09 (329 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. XPS 15 9550
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=f73bcd37-31c3-4314-81cf-102bfd94a03e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-33-generic N/A
   linux-backports-modules-5.4.0-33-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-21 (12 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.1
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9550
  dmi.product.sku: 06E4
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881549/+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 1881549] Re: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke

[Anthony Wong]

I worked with Claire and the wpasupplicant in the above PPA (#31) can
fix the issue.

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

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

Title:
  BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi
  broke

Status in linux package in Ubuntu:
  Invalid
Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  Upgraded to 20.04 and the wifi broke.  It was working fine on 18.04.  Tried a 
variety of things with apw but nada.  /var/log attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1438 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-07-09 (329 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. XPS 15 9550
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=f73bcd37-31c3-4314-81cf-102bfd94a03e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-33-generic N/A
   linux-backports-modules-5.4.0-33-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-21 (12 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.1
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9550
  dmi.product.sku: 06E4
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881549/+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 1881549] Re: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke

[Anthony Wong]

Not conclusive this's a kernel driver issue yet, also affects to "wpa"
as wpasupplicant could be related.

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

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

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

Title:
  BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi
  broke

Status in linux package in Ubuntu:
  Incomplete
Status in wpa package in Ubuntu:
  New

Bug description:
  Upgraded to 20.04 and the wifi broke.  It was working fine on 18.04.  Tried a 
variety of things with apw but nada.  /var/log attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1438 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-07-09 (329 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. XPS 15 9550
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=f73bcd37-31c3-4314-81cf-102bfd94a03e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-33-generic N/A
   linux-backports-modules-5.4.0-33-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-21 (12 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.1
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9550
  dmi.product.sku: 06E4
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881549/+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 1878670] Re: Gnome crash frequently

[Anthony Wong]

Hi Kurt,

I see you have a Ubuntu preload machine, we will try to see if we can reproduce 
your problem.
Meanwhile, please upload more details by apport-collect as Daniel said.

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

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

Title:
  Gnome crash frequently

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Triaged

Bug description:
  The system freezes frequently then logs out.
  If happens at apparently random times, and using no particular app.

  Extract of syslog is attached.

  Requested info is below:

  1) release
  Ubuntu 18.04.2 LTS (beaver-osp1-melisa X30)

  2) package version
  gnome-session:
Installeret: (ingen)
Kandidat:3.28.1-0ubuntu3
Versionstabel:
   3.28.1-0ubuntu3 500
  500 http://dk.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
   3.28.1-0ubuntu2 500
  500 http://dk.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  3) Gnome shouldn't crash

  4) Gnome crashed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878670/+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 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

[Anthony Wong]

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

** Also affects: pulseaudio (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: pulseaudio (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  New
Status in pulseaudio source package in Bionic:
  New
Status in pulseaudio source package in Focal:
  New

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 3-ring headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+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 1834138] Re: PA: Don't restore the streams to sinks/sources with only unavailable ports

[Anthony Wong]

** 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 pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1834138

Title:
  PA: Don't restore the streams to sinks/sources with only unavailable
  ports

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Released
Status in pulseaudio source package in Disco:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Released

Bug description:
  SRU Document:

  [Impact]

  The Lenovo P520 machine has dual analogue codecs, so there are two
  sinks and two sources in the PA, one has the front headphone and front
  microphone, the other has the rear lineout, linein and rear
  microphone, and the rear microphone always shows up in the gnome-
  sound-setting, When we plug a microphone to front audio jack, there
  are two input devices: rear mic and front mic in the gnome-sound-
  setting, and suppose users select the the front mic to record sound
  via audio app like arecord, the front mic will be bond the arecord,
  after the front mic is unplugged, there is only one rear mic left in
  the gnome-sound-setting, but the binding will not be changed, the
  arecrod still bind to front mic, under this situation if users record
  sound via arecord, they will find they can't record any sound from any
  other input devices even they are listed in the gnome-sound-setting.
  This problem also happens to output devices too.

  [Test Case]

  After applying this patch, I did the same test: unplug the front mic,
  then use the arecord to record sound, the app can record sound from
  rear mic now. After I plug the front mic back, the arecord still
  record from front mic. Also did the similar test for output devices,
  it worked as expected too.

  [Regression Potential]

  Low, Just make a simple check when creating new streams
  (sink_input/source_output), If the restored device (sink/source) has
  ports and all ports are unavialble, it will not restore the binding,
  otherwise it will work as before.

  For the Bionic, This SRU also includes the fix of LP: #1556439, this
  fix is safe and is very low possible to introduce any regression too,
  because it just adds a sink-input/source-output state checking, if the
  sink-input/source-output is unlinking or unlinked, it is useless to
  move it to a new sink/source, furthermore it will trigger an assertion
  that make the pulseaudio crash, adding this check can fix this problem
  (LP: #1556439).

  [Other Info]

  No more info here

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1834138/+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 1836630] Re: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend

[Anthony Wong]

** Also affects: linux (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-430 (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
   Status: Invalid

** Also affects: nvidia-graphics-drivers-430 (Ubuntu Focal)
   Importance: Undecided
 Assignee: Alberto Milone (albertomilone)
   Status: Confirmed

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-430 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

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

** Changed in: nvidia-graphics-drivers-430 (Ubuntu Eoan)
   Status: New => Fix Released

** Changed in: nvidia-graphics-drivers-430 (Ubuntu Focal)
   Status: Confirmed => New

** Changed in: nvidia-graphics-drivers-430 (Ubuntu Bionic)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

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

Title:
  System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Invalid
Status in nvidia-graphics-drivers-430 source package in Bionic:
  New
Status in linux source package in Eoan:
  Invalid
Status in nvidia-graphics-drivers-430 source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Invalid
Status in nvidia-graphics-drivers-430 source package in Focal:
  New

Bug description:
  After upgrading the Ubuntu kernel to version 5.0.0-21, the System76
  Oryx Pro (oryp5) fails to resume from suspend when using discrete
  NVIDIA graphics

  The issue can be created on this hardware by following these steps:
  - Install Ubuntu 18.04.2
  - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed
  - Upgrade:
sudo apt-get updatesudo apt-get dist-upgrade
  - Install 5.0 HWE kernel:
sudo apt-get install linux-generic-hwe-18.04-edge
  - Install NVIDIA driver:
sudo apt-get install nvidia-driver-430
  - Reboot:
sudo reboot
  - Attempt suspend/resume cycle

  This occurred after upgrading the kernel from version 5.0.0-20.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  system76   1721 F pulseaudio
   /dev/snd/controlC0:  system76   1721 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  MachineType: System76 Oryx Pro
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux-hwe-edge
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic 
root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro
  ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-21-generic N/A
   linux-backports-modules-5.0.0-21-generic  N/A
   linux-firmware1.173.9
  Tags:  bionic
  Uname: Linux 5.0.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm sudo
  _MarkForUpload: True
  dmi.bios.date: 05/07/2019
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.08
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76
  dmi.board.version: oryp5
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: oryp5
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5:
  dmi.product.family: Not Applicable
  dmi.product.name: Oryx Pro
  dmi.product.sku: Not Applicable
  dmi.product.version: oryp5
  dmi.sys.vendor: System76

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1836630/+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 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)

[Anthony Wong]

** 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 mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1714178

Title:
  Triple 4K monitor display failed (modesetting driver limited to
  8192x8192)

Status in DRI:
  Fix Released
Status in HWE Next:
  Fix Released
Status in X.Org X server:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-osp1 package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server source package in Bionic:
  Invalid

Bug description:
  Title: Triple monitor display failed with Dell Dock (HiDPI)
  (modesetting)

  Summary: Triple monitor display failed with Dell Dock (HiDPI)
  (modesetting)

  Steps:
  1. a laptop with Built-in 4K LCD
  2. Cold boot system with Dell Dock connected
  3. Connect a 4K monitor to Dock
  4. Connect 2nd 4K monitor to Dock
  5. Go to [All Settings]=>[Displays] to have the following configuration.
  Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors)
  Mirror displays: disable

  Expected results: Triple monitor display should works without issues
  Actual results: Triple monitor display failed with Dell Dock

  Additional information:
  1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04
  2. Laptop: Dell Precision 5520
  3. Dell Business Thunderbolt Dock - TB16
  https://goo.gl/vFDjpi

  WORKAROUND (UBUNTU 18.04+):
  Log in to "Ubuntu on Wayland" instead of "Ubuntu".

  ---
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.10
  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
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:07bf]
     Subsystem: Dell Device [1028:07bf]
  InstallationDate: Installed on 2017-08-29 (2 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Precision 5520
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed 
root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.11.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/dri/+bug/1714178/+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 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)

[Anthony Wong]

** Tags added: originate-from-1837165 somerville

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

Title:
  Triple 4K monitor display failed (modesetting driver limited to
  8192x8192)

Status in DRI:
  Fix Released
Status in HWE Next:
  New
Status in X.Org X server:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Confirmed
Status in linux-oem-osp1 source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server source package in Bionic:
  Confirmed

Bug description:
  Title: Triple monitor display failed with Dell Dock (HiDPI)
  (modesetting)

  Summary: Triple monitor display failed with Dell Dock (HiDPI)
  (modesetting)

  Steps:
  1. a laptop with Built-in 4K LCD
  2. Cold boot system with Dell Dock connected
  3. Connect a 4K monitor to Dock
  4. Connect 2nd 4K monitor to Dock
  5. Go to [All Settings]=>[Displays] to have the following configuration.
  Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors)
  Mirror displays: disable

  Expected results: Triple monitor display should works without issues
  Actual results: Triple monitor display failed with Dell Dock

  Additional information:
  1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04
  2. Laptop: Dell Precision 5520
  3. Dell Business Thunderbolt Dock - TB16
  https://goo.gl/vFDjpi

  WORKAROUND (UBUNTU 18.04+):
  Log in to "Ubuntu on Wayland" instead of "Ubuntu".

  ---
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.10
  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
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:07bf]
     Subsystem: Dell Device [1028:07bf]
  InstallationDate: Installed on 2017-08-29 (2 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Precision 5520
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed 
root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.11.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/dri/+bug/1714178/+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 1834406] Re: Upgrade Noto Sans CJK fonts to version 2.001

[Anthony Wong]

I've always have proposed turned on on my 19.04 box and haven't
experienced any Chinese input/output issues with the new font.

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

Title:
  Upgrade Noto Sans CJK fonts to version 2.001

Status in fonts-noto-cjk package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  Fix Released
Status in fonts-noto-cjk source package in Bionic:
  Fix Committed
Status in language-selector source package in Bionic:
  Fix Committed
Status in fonts-noto-cjk source package in Disco:
  Fix Committed
Status in language-selector source package in Disco:
  Fix Committed
Status in fonts-noto-cjk package in Debian:
  New

Bug description:
  [Impact]

  Due to Japan's new era, a Unicode character has been introduced which
  represents the era name (Reiwa) as one single character. The version
  of fonts-noto-cjk in the stable releases does not support the new
  character, which is what motivates a backport of the eoan fonts-noto-
  cjk version. The proposed SRU is in line with the meta bug #1828884.

  This means an upgrade of Noto Sans CJK from version 1.004 to 2.001,
  and it will bring a few other changes in the bargain. Most notably a
  new set of Hong Kong fonts has been added to the previous ones
  (simplified and traditional Chinese, Japanese, and Korean). Attached
  to this bug report please see the file noto-sans-cjk-news.txt with
  upstream's detailing of the changes.

  [Test Case]

  Install from {bionic,disco}-proposed:

  - fonts-noto-cjk
  - fonts-noto-cjk-extra
  - language-selector-common
  - language-selector-gnome

  1. The Reiwa glyph
  --
  Visit http://people.ubuntu.com/~gunnarhj/square-era-name-reiwa.html
  and find that a proper Japanese character, and not a tofu, is shown.

  2. Presence and configuration of HK fonts
  -
  (This also bears on the language-selector changes.)

  * Install the Hong Kong locale:

    sudo locale-gen zh_HK.UTF-8

  * Run this command:

    LC_CTYPE=zh_HK.UTF-8 fc-match

    and find that it returns:

    NotoSansCJK-Regular.ttc: "Noto Sans CJK HK" "Regular"

  3. General use
  --
  Browse some web sites with Chinese, Japanese or Korean contents and
  confirm that the upgrade does not cause any font rendering issues.

  [Regression Potential]

  This somewhat aggressive SRU proposal is based on trust in Google and
  Adobe as solid upstream providers of these fonts. Version 2.000 (which
  includes most of the changes) was released in November 2018, while
  version 2.001 (with the Reiwa glyph) was released in April 2019.
  Serious problems should have been known by now. The upstream bug
  tracker gives no cause for concern:

  https://github.com/googlefonts/noto-cjk/issues

  It may be worth mentioning that the fonts are provided as OTC files,
  and we don't compile those files ourselves. Hence just patching the
  new glyph would not be a practicable option.

  It would be easy to reverse this upgrade, if regressions would be
  reported. Basically we are talking about 7 files on the file system.

  [Other Info re. eoan]

  Since Debian hasn't packaged this yet, we have created a modified
  .orig.tar.xz file where 7 .ttc files (plus NEWS and HISTORY) differ
  from version 1:20181130+repack1-1~exp1, i.e. the latest Debian upload.

  There is no other Ubuntu/Debian delta, so as soon as Debian has
  catched up, it will be fine to start syncing again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/1834406/+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 1778011] Re: SRU: PRIME Power Saving mode draws too much power

[Anthony Wong]

** 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 nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1778011

Title:
  SRU: PRIME Power Saving mode draws too much power

Status in HWE Next:
  Fix Released
Status in gdm3 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in sddm package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released
Status in nvidia-prime source package in Bionic:
  Fix Released
Status in nvidia-settings source package in Bionic:
  Fix Released
Status in sddm source package in Bionic:
  Confirmed
Status in ubuntu-drivers-common source package in Bionic:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Relying on the nouveau driver and on the vga switcheroo (to get around a 
change in systemd LP: #1777099) caused increased power consumption, and slowed 
down the switching process.

  Furthermore, if the main X/Xwayland session was started by Gdm when
  the nvidia driver was loaded, the session will keep the nvidia module
  loaded, and prevent the system from switching off the dGPU. Also, the
  nouveau driver will be loaded, if nvidia is not, and this can cause
  problems to unsupported NVIDIA GPUs.

  The solution involves the following changes:

  1) Solving the problem in systemd (LP: #1777099)

  2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia
  modules, and to allow the PCI device to sleep.

  3) Making a slight change to the current patch in Gdm, used to call
  the PRIME scripts before and after a Gdm session (so that gpu-manager
  gets actually called on log out)

  4) Adding code in gpu-manager to kill the main X/Xwayland session on
  log out, if the session is preventing us from unloading the nvidia
  driver. A new X/Xwayland session will be created after unload the
  module.

  5) Removing the systemd service that loads nouveau from the nvidia
  packages.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 *

  2) Make sure the nvidia packages are installed, and enable performance mode 
(if it is already enabled, call "sudo prime-select intel" first):
  sudo prime-select nvidia

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Select power saving mode:
  sudo prime-select intel

  5) Log out and log back in

  6) Check if the nvidia driver is still loaded:
  lsmod | grep nvidia

  [Regression Potential]
  Low, as hybrid graphics support does not work correctly, and the changes only 
affect this use case.

  _
  * Steps to test the updates:

  1) Enable the bionic-proposed repositories

  2) Create /etc/apt/preferences.d/proposed-updates with the following
  content:

  Package: *
  Pin: release a=bionic-proposed
  Pin-Priority: 400

  3) Update the list of packages:

  sudo apt-get update

  4) Install the packages from -proposed using the following command:

  sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-
  proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-
  proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic-
  proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390
  /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia-
  ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1778011/+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 1789201] Re: prime-select doesn't work in phase 2

[Anthony Wong]

** 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 ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1789201

Title:
  prime-select doesn't work in phase 2

Status in HWE Next:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Bionic:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  We need to be able to disable the discrete GPU in phase 2 of the oem 
installer*, and this requires running gpu-manager.service before 
oem-config.service.

  [Test Case]
  Add the new ubuntu-drivers-common in -proposed repository, and see if 
gpu-manager.service is called in phase 2.

  [Regression Potential]
  Low, as no action will be taken unless custom settings for hybrid graphics 
are available.

  *What is "phase 2" (Booting from the recovery partition, and installing 
Ubuntu):
  
https://docs.google.com/presentation/d/18q2VtQt3OJzh12--2Llzwz36DlF3Lca6iLPCnhIbQds/edit?usp=sharing

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1789201/+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 1818152] Re: Nvidia 340

[Anthony Wong]

** Also affects: nvidia-graphics-drivers-340 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Nvidia 340

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  After installing NVIDIA driver, the screen brightness is freezed by
  100%

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   senne  2237 F...m pulseaudio
   /dev/snd/controlC0:  senne  2237 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Feb 28 23:00:25 2019
  InstallationDate: Installed on 2018-12-24 (66 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Apple Inc. MacBook5,1
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=8980397b-61c8-4011-a75c-9777552c623c ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/27/09
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB51.88Z.007D.B03.0904271443
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F42D89C8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: Proto
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F42D89C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB51.88Z.007D.B03.0904271443:bd04/27/09:svnAppleInc.:pnMacBook5,1:pvr1.0:rvnAppleInc.:rnMac-F42D89C8:rvrProto:cvnAppleInc.:ct10:cvrMac-F42D89C8:
  dmi.product.family: MacBook
  dmi.product.name: MacBook5,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818152/+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 1802168] Re: Unable to get right-click working on ThinkPad T480s

[Anthony Wong]

So there is a temporary fix in libinput (https://bit.ly/2ExTtIm) before
Benjamin's kernel fix is accepted as discussed in
https://gitlab.freedesktop.org/libinput/libinput/issues/177. That fix is
already in Disco so only need to fix Cosmic.


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

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

Title:
  Unable to get right-click working on ThinkPad T480s

Status in Linux:
  Unknown
Status in libinput package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Updated to Ubuntu 18.10, I've been fighting some weird behavior of the
  touchpad. Now, right-click does not work, whatever solution I try
  within gnome-tweaks, whether relying on multi-finger tapping or not.

  Found a very very close report from RedHat, on the same model of laptop, 
around kernel 4.18, with a fix: 
https://bugzilla.redhat.com/show_bug.cgi?id=1628715
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alex   2871 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  HibernationDevice: RESUME=LABEL="Swap"
  InstallationDate: Installed on 2012-11-03 (2195 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: LENOVO 20L7CTO1WW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-10-22 (16 days ago)
  UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin 
plugdev sambashare sudo vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 09/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET49W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L7CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L7CTO1WW
  dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1802168/+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 1813738] Re: laptop doesnt wake up

[Anthony Wong]

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

** This bug has been marked a duplicate of bug 1813663
   External monitors does not work anymore 4.15.0-44

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

Title:
  laptop doesnt wake up

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  after the latest update my laptop does not wake up if the external
  monitor was plugged in when it went to sleep.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
  Uname: Linux 4.15.0-44-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 29 10:53:33 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 5500 [1028:062c]
  InstallationDate: Installed on 2018-12-03 (56 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Latitude E5550
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0THWR2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/18/2015:svnDellInc.:pnLatitudeE5550:pvr:rvnDellInc.:rn0THWR2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5550
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1813738/+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 1811807] Re: fingerprint scanner not working

[Anthony Wong]

We do not enable fingerprint reader for OEM projects. From what I see
this is more a lack of support in libfprint. There is someone who is
working on reverse engineering the protocol so that it works in
libfprint:

github project: https://github.com/nmikhailov/Validity90
github bug for 06cb:009a: https://github.com/nmikhailov/Validity90/issues/34

** Bug watch added: github.com/nmikhailov/Validity90/issues #34
   https://github.com/nmikhailov/Validity90/issues/34

** Package changed: linux (Ubuntu) => libfprint (Ubuntu)

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

Title:
  fingerprint scanner not working

Status in libfprint package in Ubuntu:
  Confirmed

Bug description:
  I have a new Thinkpad Carbon X1 Extreme and the fingerprint scanner
  does not appear to be supported.

  $ fprintd-enroll $USER
  list_devices failed: No devices available

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-13-generic 4.18.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ian6133 F pulseaudio
   /dev/snd/controlC0:  ian6133 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue Jan 15 21:29:38 2019
  MachineType: LENOVO 20MF000BUS
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=f198f923-1cae-439c-aab1-aa886fdddf29 ro quiet splash 
psmouse.synaptics_intertouch=1 vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET35W (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MF000BUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET35W(1.17):bd12/21/2018:svnLENOVO:pn20MF000BUS:pvrThinkPadX1Extreme:rvnLENOVO:rn20MF000BUS:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MF000BUS
  dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1811807/+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 1778011] Re: SRU: PRIME Power Saving mode draws too much power

[Anthony Wong]

** Tags added: originate-from-1788575 somerville

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

Title:
  SRU: PRIME Power Saving mode draws too much power

Status in HWE Next:
  New
Status in gdm3 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Committed
Status in nvidia-prime source package in Bionic:
  Fix Committed
Status in nvidia-settings source package in Bionic:
  Fix Committed
Status in ubuntu-drivers-common source package in Bionic:
  Fix Committed

Bug description:
  SRU Request:

  [Impact]
  Relying on the nouveau driver and on the vga switcheroo (to get around a 
change in systemd LP: #1777099) caused increased power consumption, and slowed 
down the switching process.

  Furthermore, if the main X/Xwayland session was started by Gdm when
  the nvidia driver was loaded, the session will keep the nvidia module
  loaded, and prevent the system from switching off the dGPU. Also, the
  nouveau driver will be loaded, if nvidia is not, and this can cause
  problems to unsupported NVIDIA GPUs.

  The solution involves the following changes:

  1) Solving the problem in systemd (LP: #1777099)

  2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia
  modules, and to allow the PCI device to sleep.

  3) Making a slight change to the current patch in Gdm, used to call
  the PRIME scripts before and after a Gdm session (so that gpu-manager
  gets actually called on log out)

  4) Adding code in gpu-manager to kill the main X/Xwayland session on
  log out, if the session is preventing us from unloading the nvidia
  driver. A new X/Xwayland session will be created after unload the
  module.

  5) Removing the systemd service that loads nouveau from the nvidia
  packages.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 *

  2) Make sure the nvidia packages are installed, and enable performance mode 
(if it is already enabled, call "sudo prime-select intel" first):
  sudo prime-select nvidia

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Select power saving mode:
  sudo prime-select intel

  5) Log out and log back in

  6) Check if the nvidia driver is still loaded:
  lsmod | grep nvidia

  [Regression Potential]
  Low, as hybrid graphics support does not work correctly, and the changes only 
affect this use case.

  _
  * Steps to test the updates:

  1) Enable the bionic-proposed repositories

  2) Create /etc/apt/preferences.d/proposed-updates with the following
  content:

  Package: *
  Pin: release a=bionic-proposed
  Pin-Priority: 400

  3) Update the list of packages:

  sudo apt-get update

  4) Install the packages from -proposed using the following command:

  sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-
  proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-
  proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic-
  proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390
  /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia-
  ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1778011/+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 1728547] Re: SRU: Add support for keeping the dGPU on in power saving mode

[Anthony Wong]

** 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 ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1728547

Title:
  SRU: Add support for keeping the dGPU on in power saving mode

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Fix Committed
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Xenial:
  Fix Released
Status in ubuntu-drivers-common source package in Zesty:
  Fix Committed
Status in ubuntu-drivers-common source package in Artful:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Some systems don't play well when the dGPU is disabled. It should still be 
possible to use the Intel iGPU without disabling the dGPU.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common"

  2) Make sure the nvidia packages are installed, and enable power saving mode:
  sudo prime-select intel

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Install the mesa-utils package:
  sudo apt install mesa-utils

  5) Check the output of the following command (which should mention Intel):
  glxinfo | grep OpenGL

  
  [Regression Potential]
  Low, as the feature is disabled by default. This is only for hardware 
specific workarounds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1728547/+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 1750947] Re: pulseaudio print lots of error when selecting unavailable profile

[Anthony Wong]

** Changed in: pulseaudio (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

** 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 pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1750947

Title:
  pulseaudio print lots of error when selecting unavailable profile

Status in HWE Next:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Released

Bug description:
  SRU Document:

  [Impact]

  A HDMI audio device usually has several output ports, each port
  represents a profile in pulseaudio, without this patch, the puseaudio
  always choose the first profile no matter it is active or not.

  [Test Case]

  connect each port of HDMI device, and check if the profile of that
  port is active or not.

  [Regression Potential]

  The patch will check all ports under each profile, if a profile only
  contains unavailable ports, this profile will be set to unavailable as
  well. Without this patch, all profiles are always available, then if a
  profile includes a unusable hdmi-output, and pulseaudio select this
  profile to be active (since its priority is the highest), the kernel
  audio driver will crash.

  I think this patch will not introduce regression:
  1) It is a correct logic to set a profile to be unavailable if it only 
contains unavailable ports.
  2) pulseaudio-artful and pulseaudio-bionic already include this patch, they 
work very well
  3) I tested this patch on 1 lenovo laptop, 1 lenovo desktop, 1 dell laptop 
and 1 dell desktop, all worked well as before
  4) tested this patch on two dell machines (LOAD5-DVT2-A2 and Dawson-JC-C 
without analogue audio) which have unusable hdmi-output profile on them, the 
kernel driver did not crash anymore and audio function worked very well.

  [Other Info]

  Only pulseaudio-xenial has this problem.

  we need to backport this commit to pulseaudio-xenial.

  
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4

  After printing out the error logs, the kernel crashes and system
  hangs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1750947/+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 1728547] Re: SRU: Add support for keeping the dGPU on in power saving mode

[Anthony Wong]

Bug 1731873 is also awaiting verification, that is another bug for
ubuntu-drivers-common SRU.

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

Title:
  SRU: Add support for keeping the dGPU on in power saving mode

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Xenial:
  Fix Committed
Status in ubuntu-drivers-common source package in Zesty:
  Fix Committed
Status in ubuntu-drivers-common source package in Artful:
  Fix Committed

Bug description:
  SRU Request:

  [Impact]
  Some systems don't play well when the dGPU is disabled. It should still be 
possible to use the Intel iGPU without disabling the dGPU.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common"

  2) Make sure the nvidia packages are installed, and enable power saving mode:
  sudo prime-select intel

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Install the mesa-utils package:
  sudo apt install mesa-utils

  5) Check the output of the following command (which should mention Intel):
  glxinfo | grep OpenGL

  
  [Regression Potential]
  Low, as the feature is disabled by default. This is only for hardware 
specific workarounds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1728547/+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 1365926] Re: The “Enable this account” item in the new account settings page doesn’t work.

[Anthony Wong]

** Changed in: ubuntukylin
 Assignee: Anthony Wong (anthonywong) => (unassigned)

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

Title:
  The “Enable this account” item in the new account settings page
  doesn’t work.

Status in Ubuntu Kylin:
  Confirmed
Status in unity-control-center package in Ubuntu:
  New

Bug description:
  The “Enable this account” item in the new account settings page
  doesn’t work.

  Steps:
  1. Enter into System settings-->User Accounts
  2. Click Unlock in this page
  3. Add a new account
  4. Enter into the new account setting page, click the drop list at the right 
of "Password" item
  5. Chose Enable this account from Action list
  -->Failed. This item doesn't work

  Configuration:
  PC: Dell Vostro
  OS: Ubuntu Kylin 14.10 x32 Daily 20140905

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntukylin/+bug/1365926/+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 1652876] Re: No proprietary driver available for NVIDIA [10de:13b4]

[Anthony Wong]

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

** Changed in: ubuntu-drivers-common (Ubuntu)
   Status: New => Fix Released

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

Title:
  No proprietary driver available for NVIDIA [10de:13b4]

Status in HWE Next:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released

Bug description:
  This is a hybrid graphic system, but there is no proprietary driver
  available for the NVIDIA graphic card on this system.

  01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:13b4] (rev a2)
Subsystem: Dell Device [1028:07a9]
Kernel driver in use: nouveau
Kernel modules: nvidiafb, nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1652876/+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 1499665] Re: [SynPS/2 Synaptics TouchPad] TouchPad not working after installtion

[Anthony Wong]

** Changed in: hwe-next
   Status: Incomplete => Won't Fix

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

Title:
  [SynPS/2 Synaptics TouchPad] TouchPad not working after installtion

Status in HWE Next:
  Won't Fix
Status in linux package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  During installation touchpad works perfectly, but after trusty(3.19)
  installed, and restarted, touchpad unable to use anymore.

  Steps to reproduce:

  1. Boot system with 14.04.3 live usb
  2. Install the system

  Expected result:
  Touchpad works normally as in live environment 

  Actual results:
  Touchpad no response

  
  Additional Info.:
  $ xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech USB-PS/2 Optical Mouse id=9[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ DLLC6D7:00 06CB:796Aid=12   [slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=14   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Sleep Buttonid=8[slave  
keyboard (3)]
  ↳ Integrated_Webcam_HDid=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=15   [slave  
keyboard (3)]

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-28.30~14.04.1-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  .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: Fri Sep 25 17:48:59 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation ValleyView Gen7 [8086:0f31] (rev 0e) (prog-if 00 [VGA 
controller])
     Subsystem: Dell Device [1028:06d7]
  InstallationDate: Installed on 2015-09-22 (2 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Dell Inc. Inspiron 5551
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic.efi.signed 
root=UUID=3bf855c2-39fe-4325-a1cc-960930d96a9e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: X16
  dmi.board.asset.tag: AFTPASS
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: AFTPASS
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: X16
  dmi.modalias: 
dmi:bvnDellInc.:bvrX16:bd01/28/2015:svnDellInc.:pnInspiron5551:pvrX16:rvnDellInc.:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnDellInc.:ct8:cvrX16:
  dmi.product.name: Inspiron 5551
  dmi.product.version: X16
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Sep 25 17:06:43 2015
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5100
   vendor AUO
  xserver.version: 2:1.17.1-0ubuntu3.1~trusty1
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CasperVersion: 1.340.2
  CompizPlugins: No value set for 

[Desktop-packages] [Bug 1509921] Re: [HDA-Intel - HD-Audio Generic, recording] No sound at all

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Won't Fix

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

Title:
  [HDA-Intel - HD-Audio Generic, recording] No sound at all

Status in HWE Next:
  Won't Fix
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  This is a desktop box, with following ports:
  front jack: a single headset combo jack
  rear jacks: mic, speaker, line-in

  An "Analog Input" consistently show up even there is nothing plugged,
  but I'm not able to record using headset via front combo jack or rear mic 
jack, they all recorded with noises.

  00:01.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device 
[1002:9840]
  00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] FCH Azalia 
Controller [1022:780d] (rev 02)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
  Uname: Linux 3.13.0-66-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  1824 F pulseaudio
   /dev/snd/controlC0:  u  1824 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Oct 26 11:46:46 2015
  InstallationDate: Installed on 2015-10-23 (2 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic_1 failed
  Symptom_Card: Built-in Audio - HD-Audio Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  1824 F pulseaudio
   /dev/snd/controlC0:  u  1824 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HD-Audio Generic, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.0:bd05/21/2015:svnDellInc.:pnInspiron3655:pvr1.0.0:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.name: Inspiron 3655
  dmi.product.version: 1.0.0
  dmi.sys.vendor: Dell Inc.

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

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Won't Fix

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

-- 
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:
  Won't Fix
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-installer
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0CYT5F
  

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

[Anthony Wong]

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

-- 
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 gnome-control-center:
  Confirmed
Status in HWE Next:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
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/gnome-control-center/+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 1309550] Re: Exec should be "amdxdg-su -c /usr/bin/amdcccle" in ubuntu-amdccclesu.desktop

[Anthony Wong]

** Changed in: hwe-next
   Status: Triaged => Won't Fix

-- 
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:
  Won't Fix
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:
  In Progress
Status in fglrx-installer-updates source package in Trusty:
  In Progress

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-0ubuntu1
  

[Desktop-packages] [Bug 1417952] Re: [HP Pavilion 23 AIO] Stuck on the ubuntu loading splashscreen with fglrx installed

[Anthony Wong]

** Changed in: hwe-next
   Status: Confirmed => Won't Fix

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

Title:
  [HP Pavilion 23 AIO] Stuck on the ubuntu loading splashscreen with
  fglrx installed

Status in HWE Next:
  Won't Fix
Status in fglrx-installer package in Ubuntu:
  Confirmed

Bug description:
  CID: 201212-12386 HP Pavilion 23 AIO

  This AIO has two AMD graphic controller:
  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Trinity [Radeon HD 7540D] [1002:9991]
  01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M] [1002:6600]

  On 14.04.1, it could boot to desktop normally with the open-source driver, 
but not with fglrx / fglrx-updates.
  It will stuck on the purple screen with "Ubuntu" and running dots, but at 
this moment, you could switch to console without any problem.

  Error message could be found in the Xorg log:
  [17.652] (EE) AIGLX error: failed to open 
/usr/X11R6/lib64/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object 
file: No such file or directory]
  [17.652] (EE) AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, 
error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file 
or directory]
  [17.652] (EE) AIGLX error: failed to open 
/usr/X11R6/lib/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: 
No such file or directory]

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-45-generic 3.13.0-45.74
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1682 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 Feb  4 03:15:35 2015
  HibernationDevice: RESUME=UUID=8d360796-c015-4ef1-bc7c-96d698d008bc
  InstallationDate: Installed on 2015-02-03 (1 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard DVT-ys002
  ProcFB:
   0 radeondrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic 
root=UUID=13f3b16a-e799-4e06-babb-bffc9d86cd88 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-45-generic N/A
   linux-backports-modules-3.13.0-45-generic  N/A
   linux-firmware 1.127.11
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2013
  dmi.bios.vendor: AMI
  dmi.bios.version: 3.13H
  dmi.board.asset.tag: 4CS247000Z
  dmi.board.name: 2AF6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 011
  dmi.chassis.asset.tag: 4CS247000Z
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvr3.13H:bd01/07/2013:svnHewlett-Packard:pnDVT-ys002:pvr:rvnHewlett-Packard:rn2AF6:rvr011:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: DVT-ys002
  dmi.sys.vendor: Hewlett-Packard

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

[Anthony Wong]

** Changed in: hwe-next
   Status: Incomplete => Won't Fix

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

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

Status in HWE Next:
  Won't Fix
Status in alsa-driver package in Ubuntu:
  Confirmed

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

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

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

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

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

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

-- 
Mailing list: https://launchpad.net/~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 1435246] Re: No available driver was found in the "Additional Driver" tool for an I+N system on 14.04.2

[Anthony Wong]

** Changed in: hwe-next
   Status: Confirmed => Won't Fix

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

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

Title:
  No available driver was found in the "Additional Driver" tool for an
  I+N system on 14.04.2

Status in HWE Next:
  Won't Fix
Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  CID: 201408-15447 Dell Vostro 3449

  This is an I+N hybrid graphci system, but the proprietary nVidia video
  driver is not available in the "Additional driver" tool even with
  system upgraded to 3.16.0-31.

  00:02.0 VGA compatible controller [0300]: Intel Corporation Broadwell-U 
Integrated Graphics [8086:1616] (rev 08)
  08:00.0 3D controller [0302]: NVIDIA Corporation GF117M [GeForce 
610M/710M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.16.0-31-generic 3.16.0-31.43~14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 23 04:05:26 2015
  InstallationDate: Installed on 2015-03-23 (0 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: linux-lts-utopic
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1542 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1542 F pulseaudio
  CRDA:
   country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=6684dd24-230b-439d-b472-e64c6a9d0032
  InstallationDate: Installed on 2015-12-21 (0 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Dell Inc. Vostro 3449
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-57-generic.efi.signed 
root=UUID=d597d53e-d9fa-4631-b79c-d1b3472c8e80 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-57.77~14.04.1-generic 3.16.7-ckt20
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-57-generic N/A
   linux-backports-modules-3.16.0-57-generic  N/A
   linux-firmware 1.127.19
  Tags:  trusty
  Uname: Linux 3.16.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/25/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd10/25/2014:svnDellInc.:pnVostro3449:pvrA00:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Vostro 3449
  dmi.product.version: A00
  dmi.sys.vendor: Dell Inc.

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

[Anthony Wong]

** Changed in: hwe-next
   Status: Confirmed => Won't Fix

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

Title:
  [Dell Inspiron 5447] failed to suspend-resume when using AMD Radeon R7
  M260 graphic card [1002:6900]

Status in HWE Next:
  Won't Fix
Status in fglrx-installer package in Ubuntu:
  New

Bug description:
  Dell Inspiron 5447 (CID 201401-14529) on 14.04

  Steps to reproduce this bug:
  1. install proprietary driver by clicking 'Ubuntu Software Center'-->Software 
sources--> the tab 'Additional Drivers'
  2. select the suggested proprietary drivers fglrx or fglrx-updates
  3. reboot the system
  4. suspend the system by 'sudo rtcwake -s 60 -m mem' or the indicator in the 
top right of the desktop
  5. press power to resume the system if you suspended the system by the 
indicator

  Expected result:
  the system will resume back to work.

  Actul result:
  When resuming from suspend, the system will resume back to the stage which 
shows you the desktop screen, and then freeze.
  The resume screen looks fine but the system is freezed.

  Both of fglrx and fglrx-updates have the same issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: fglrx (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-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: Mon Jun  9 04:15:09 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx-updates, 13.350.1, 3.13.0-24-generic, x86_64: installed
   fwts-efi-runtime-dkms, 14.03.01, 3.13.0-24-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0640]
  InstallationDate: Installed on 2014-06-04 (5 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Inspiron 5447
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=0b1afcfd-68b0-40fa-b708-243e4be4209b ro rootdelay=60 quiet splash 
initcall_debug vt.handoff=7
  SourcePackage: fglrx-installer
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: X18
  dmi.board.name: 0NGDM1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X01
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: X18
  dmi.modalias: 
dmi:bvnDellInc.:bvrX18:bd02/12/2014:svnDellInc.:pnInspiron5447:pvrX18:rvnDellInc.:rn0NGDM1:rvrX01:cvnDellInc.:ct8:cvrX18:
  dmi.product.name: Inspiron 5447
  dmi.product.version: X18
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  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
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Jun  9 02:26:45 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors: Screen 1 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2
  xserver.video_driver: fglrx

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1327990/+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 1371372] Re: Support for Lenovo new TrackPad (ClickPad)

[Anthony Wong]

** Changed in: hwe-next
   Status: Confirmed => Won't Fix

-- 
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:
  Won't Fix
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 1390338] Re: No recommanded driver for [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] [1002:6840]

[Anthony Wong]

** Changed in: hwe-next
   Status: Triaged => Won't Fix

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

Title:
  No recommanded driver for [AMD/ATI] Thames [Radeon HD 7500M/7600M
  Series] [1002:6840]

Status in HWE Next:
  Won't Fix
Status in jockey package in Ubuntu:
  Triaged

Bug description:
  
  This is a system with APU and ATI graphic chip, APU works fine without extra 
driver.

  But Jockey does show any drivers for ATI graphic chip, so users are
  not able to use jockey install driver for this graphic chip.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: jockey-common 0.9.7-0ubuntu7.15
  ProcVersionSignature: Ubuntu 3.13.0-40.68~precise1-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: amd64
  Date: Thu Nov  6 07:55:40 2014
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MachineType: Hewlett-Packard HP Pavilion g7 Notebook PC
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic 
root=UUID=2b2e3844-604a-4074-9bbb-9a9e76412c6e ro quiet splash initcall_debug 
vt.handoff=7
  SourcePackage: jockey
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2012
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 184C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 57.34
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd10/17/2012:svnHewlett-Packard:pnHPPaviliong7NotebookPC:pvr089D1100501020100:rvnHewlett-Packard:rn184C:rvr57.34:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion g7 Notebook PC
  dmi.product.version: 089D1100501020100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1390338/+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 1133684] Re: Xorg segfaults with the fglrx driver on some Shark Bay systems

[Anthony Wong]

** Changed in: hwe-next
   Status: Triaged => Won't Fix

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

Title:
  Xorg segfaults with the fglrx driver on some Shark Bay systems

Status in amd:
  Fix Committed
Status in HWE Next:
  Won't Fix
Status in fglrx-installer package in Ubuntu:
  Triaged

Bug description:
  After getting GreenScreen, we restart system and enter into OOBE.
  Sometimes, system will restart suddenly and pop the message likes
  attached picture up. In this case, system cannot enter into OS desktop
  smoothly.

  Steps to Reproduce:
  1. Install 12.04.2 64-bit on shark bay platform.
  2. Boot
  3. Xorg segfaults and the console message like attached picture appears.

  Segfault backtrace:

  [ 18.746] (==) fglrx(0): hotplug detection: "enabled"
  [ 18.772] (EE)
  [ 18.772] (EE) Backtrace:
  [ 18.772] (EE) 0: /usr/bin/X (xorg_backtrace+0x34) [0x7ffd3b89a634]
  [ 18.772] (EE) 1: /usr/bin/X (0x7ffd3b6e5000+0x1b9589) [0x7ffd3b89e589]
  [ 18.772] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7ffd3aa0b000+0xfcb0) [0x7ffd3aa1acb0]
  [ 18.772] (EE) 3: 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/drivers/fglrx_drv.so 
(xclIn32+0x0) [0x7ffd37c828c0]
  [ 18.772] (EE) 4: 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/drivers/fglrx_drv.so 
(xilReadReg32_R600+0xe) [0x7ffd37e2f36e]
  [ 18.772] (EE) 5: 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/drivers/fglrx_drv.so 
(xdl_xs113_atiddxPxScreenInit+0xa4) [0x7ffd37df5614]
  [ 18.772] (EE) 6: 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/drivers/fglrx_drv.so 
(xdl_xs113_atiddxScreenInit+0xdb9) [0x7ffd37dd29e9]
  [ 18.772] (EE) 7: /usr/bin/X (AddScreen+0x8a) [0x7ffd3b73a9fa]
  [ 18.772] (EE) 8: /usr/bin/X (InitOutput+0x3f8) [0x7ffd3b77dd88]
  [ 18.772] (EE) 9: /usr/bin/X (0x7ffd3b6e5000+0x43f5d) [0x7ffd3b728f5d]
  [ 18.772] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xed) 
[0x7ffd3969176d]
  [ 18.773] (EE) 11: /usr/bin/X (0x7ffd3b6e5000+0x444b1) [0x7ffd3b7294b1]
  [ 18.773] (EE)
  [ 18.773] (EE) Segmentation fault at address 0x70180
  [ 18.773]
  Fatal server error:
  [ 18.773] Caught signal 11 (Segmentation fault). Server aborting
  [ 18.773]
  [ 18.773] (EE)
  Please consult the The X.Org Foundation support
   at http://wiki.x.org
   for help.
  [ 18.773] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
  [ 18.773] (EE)

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1133684/+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 1308954] Re: AMDRadeon HD 8670A/8670M/8690M [1002:6660] System freezes after resume from suspend with fglrx-updates

[Anthony Wong]

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

** Changed in: hwe-next/trusty
   Status: In Progress => Won't Fix

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

Title:
  AMDRadeon HD 8670A/8670M/8690M [1002:6660] System freezes after resume
  from suspend with fglrx-updates

Status in HWE Next:
  Fix Released
Status in HWE Next trusty series:
  Won't Fix
Status in fglrx-installer-updates package in Ubuntu:
  Fix Released
Status in fglrx-installer-updates source package in Trusty:
  In Progress

Bug description:
  SRU Justification

  [impact]
  this bug is blocking us to pass certification on OEM hardware.

  [test case]
  1. Install 14.04 and fglrx-updates driver
  2. Suspend the machine
  3. Wake it up

  Expected result:
  * Everything should work fine before and after S3

  [regression potential]

  
  -

  CID: 201305-13624

  This system would freeze after resume from suspend with fglrx-updates
  on Trusty.

  Steps:
  1. Install 14.04, and fglrx-updates driver
  2. Suspend
  3. Wake it up

  Expected results:
  * Everything works fine before / after S3

  Actual results:
  * After S3, I can see the login screen, caps lock LED and touchpad still 
responsive, but I can't login. Few seconds later, system froze, error message 
could be found in syslog
  kernel: [  599.576267] <3>[fglrx:firegl_pplib_notify_event] *ERROR* PPLIB: 
PPLib Notify Event failed!
  kernel: [  599.576268] <3>[fglrx:firegl_pplib_notify_event] *ERROR*
ulEventType = 0002, ulEventData = 

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: fglrx-updates 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
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-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: Thu Apr 17 16:42:48 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx-updates, 13.350.1, 3.13.0-23-generic, x86_64: installed
   fglrx-updates, 13.350.1, 3.13.0-24-generic, x86_64: installed
   fwts-efi-runtime-dkms, 14.03.01, 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: Hewlett-Packard Company Device [103c:2162]
     Subsystem: Hewlett-Packard Company Device [103c:2162]
  InstallationDate: Installed on 2014-04-10 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140406)
  MachineType: Hewlett-Packard HP Pavilion TS 14 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed 
root=UUID=ef6ba3b5-e12b-4029-9d6b-cb1753a88ce5 ro quiet splash vt.handoff=7
  SourcePackage: fglrx-installer-updates
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: B.09
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2162
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 29.0A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrB.09:bd05/27/2013:svnHewlett-Packard:pnHPPavilionTS14NotebookPC:pvr089C101630100:rvnHewlett-Packard:rn2162:rvr29.0A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion TS 14 Notebook PC
  dmi.product.version: 089C101630100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  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
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Apr 17 16:31:44 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   Screen 1 deleted because of no matching config section.
   AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object 
file: No such file 

[Desktop-packages] [Bug 1331347] Re: [Dell Inspiron 3542] 'ubuntu-driver list' does not suggest to use nvidia-graphics-drivers-331

[Anthony Wong]

** Changed in: hwe-next
   Status: Incomplete => Won't Fix

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

Title:
  [Dell Inspiron 3542] 'ubuntu-driver list' does not suggest to use
  nvidia-graphics-drivers-331

Status in HWE Next:
  Won't Fix
Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed

Bug description:
  tested by Dell Inspiron 3542 (CID 201402-14684) on 14.04 and 14.10
  daily build

  Steps to reproduce the bugs:
  1. install the system
  2. click 'Software center'-->Preference-->Additional drivers,
  or, use the command 'ubuntu-driver list'

  Expected result:
  the system should suggest nvidia-graphics-drivers-331 driver package because
  there is a nvidia graphic card
  NVIDIA Corporation GF117M [GeForce 610M/710M/820M / GT 620M/625M/630M/720M] 
[10de:1140]

  Actual result:
  It didn't suggest any graphic driver to be used.


  -- lspci -nnvv -d 10de:1140 --

  08:00.0 3D controller [0302]: NVIDIA Corporation GF117M [GeForce 
610M/710M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1)
Subsystem: Dell Device [1028:0652]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvidia

  
  -- more information --

  * apt-cache show nvidia-331 | grep 0625
  doesn't give you the expected modalias of the graphic card under sysfs

  * manual installation of nvidia-331 could enable the graphic card and
  works fine.

  $ dpkg -l | grep nvidia
  ii  nvidia-331331.79-0ubuntu1 

 amd64NVIDIA binary driver - version 331.79
  ii  nvidia-libopencl1-331 331.79-0ubuntu1 

 amd64NVIDIA OpenCL Driver and ICD Loader library
  ii  nvidia-opencl-icd-331 331.79-0ubuntu1 

 amd64NVIDIA OpenCL ICD
  ii  nvidia-prime  0.6.5   

 amd64Tools to enable NVIDIA's Prime
  ii  nvidia-settings   331.20-0ubuntu8 

 amd64Tool for configuring the NVIDIA graphics 
driver

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1331347/+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 1667198] Re: gpu-manager should also support using custom xorg.conf files for Nvidia

[Anthony Wong]

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

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

Title:
  gpu-manager should also support using custom xorg.conf files for
  Nvidia

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Xenial:
  Fix Released
Status in ubuntu-drivers-common source package in Zesty:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Different GPUs may require different options in the xorg.conf file. Currently 
this is not possible, since the options have been hardcoded in gpu-manager to 
configure the system automatically.

  This new (backported) feature allows users to tell gpu-manager to use
  their own custom xorg.confs for their NVIDIA GPUs.

  [Test Case]
  1) Enable the xenial-proposed repository, and install the 
ubuntu-drivers-common and the nvidia-prime packages.

  2) Install the nvidia driver.

  3) Place your configuration file(s) in the /usr/share/gpu-manager.d
  directory.

  If you are using a non-hybrid system, you can create the /usr/share
  /gpu-manager.d/non-hybrid file. In case of a hybrid system, you can
  specify /usr/share/gpu-manager.d/hybrid-performance and/or /usr/share
  /gpu-manager.d/hybrid-power-saving, depending on the power profile you
  intend to apply your settings to.

  4) Restart the system and see if it boots correctly. If unsure, please
  attach your /var/log/gpu-manager.log and /var/log/Xorg.0.log

  5) Make sure that the /etc/X11/xorg.conf matches the file you
  specified in 3)

  [Regression Potential]
  Low, the above mentioned changes are already in Artful, and will not affect 
the system's behaviour unless new configuration files are put in the 
/usr/share/gpu-manager.d/ directory.

  __
  This feature has been implemented for Intel (ex. gpumanager_uxa), which is 
parsing kernel parameter to add option in xorg.conf (commit ff3a4e54).

  And now Nvidia also need this feature to add Option
  "nvidiaXineramaInfo" "off" to fix some issues.

  Btw, I'm thinking it might be a more flexible to have a config file
  which user could add all options as they want so that we could prevent
  keeping change gpu-manager when some more options are needed in the
  future.

  Needed by LP: #1653592

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1667198/+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 1649763] Re: Dell XPS 15 2016 with Ubuntu 16 Sound HDMI issues

[Anthony Wong]

>From what I learnt from Hui Wang, it is not easy to backport these 3
commits to 16.04, or even it is not possible at all. These commits make
a great change for pulseaudio core as well as some other modules, it
will affect a lot of existing functions in the pulesaudio. The 1st
commit looks like below. I will leave the decision to desktop team if we
want to fix this in 16.04 or not.

hwang4@hwang4-Inspiron-7520:~/source/pulseaudio$ git show 
6b348961304903483aa78d4ddc1fd036ef75a7cb |diffstat
modules/dbus/iface-core.c | 114 ++---
modules/dbus/iface-sample.c | 10 +
modules/module-default-device-restore.c | 14 +-
modules/module-intended-roles.c | 37 +++---
modules/module-rescue-streams.c | 20 +--
modules/module-switch-on-connect.c | 30 +++--
pulsecore/cli-command.c | 20 +--
pulsecore/cli-text.c | 12 --
pulsecore/core.c | 170 
pulsecore/core.h | 28 -
pulsecore/namereg.c | 115 +
pulsecore/namereg.h | 6 -
pulsecore/protocol-native.c | 19 +--
pulsecore/sink.c | 7 +
pulsecore/source.c | 7 +
15 files changed, 370 insertions(+), 239 deletions(-)

** Changed in: unity-control-center (Ubuntu)
 Assignee: Hui Wang (hui.wang) => (unassigned)

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

Title:
  Dell XPS 15 2016 with Ubuntu 16 Sound HDMI issues

Status in OEM Priority Project:
  Confirmed
Status in Unity Control Center:
  New
Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  This issue is related to sound not working properly on Ubuntu when
  switching between an external display using HDMI with 4K resolution
  and the standard laptop display.

  Issue 1 - Sound only works on laptop when plugged into 4k HDMI display
  Issue 2 - Sound doesn't work when plugged removed from 4k HDMI display

  When you plug in a 4k Display that supports sound to the Dell XPS 15
  2016 model the sound only works on the laptop. Only when you go to
  Sound Settings and manually select the HDMI output for sound does the
  sound start to work on the display itself instead of the laptop.

  When you unplug the HDMI 4k display the sound doesn't work on the
  laptop. When you go to the Sound Settings dialog it only shows one
  output that is selected - if you select the same output thats already
  selected the sound starts to work again on the laptop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1649763/+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 1667198] Re: gpu-manager should also support using custom xorg.conf files for Nvidia

[Anthony Wong]

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

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

Title:
  gpu-manager should also support using custom xorg.conf files for
  Nvidia

Status in HWE Next:
  Incomplete
Status in OEM Priority Project:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Xenial:
  Fix Committed

Bug description:
  SRU Request:

  [Impact]
  Different GPUs may require different options in the xorg.conf file. Currently 
this is not possible, since the options have been hardcoded in gpu-manager to 
configure the system automatically.

  This new (backported) feature allows users to tell gpu-manager to use
  their own custom xorg.confs for their NVIDIA GPUs.

  [Test Case]
  1) Enable the xenial-proposed repository, and install the 
ubuntu-drivers-common and the nvidia-prime packages.

  2) Install the nvidia driver.

  3) Place your configuration file(s) in the /usr/share/gpu-manager.d
  directory.

  If you are using a non-hybrid system, you can create the /usr/share
  /gpu-manager.d/non-hybrid file. In case of a hybrid system, you can
  specify /usr/share/gpu-manager.d/hybrid-performance and/or /usr/share
  /gpu-manager.d/hybrid-power-saving, depending on the power profile you
  intend to apply your settings to.

  4) Restart the system and see if it boots correctly. If unsure, please
  attach your /var/log/gpu-manager.log and /var/log/Xorg.0.log

  5) Make sure that the /etc/X11/xorg.conf matches the file you
  specified in 3)

  [Regression Potential]
  Low, the above mentioned changes are already in Artful, and will not affect 
the system's behaviour unless new configuration files are put in the 
/usr/share/gpu-manager.d/ directory.

  __
  This feature has been implemented for Intel (ex. gpumanager_uxa), which is 
parsing kernel parameter to add option in xorg.conf (commit ff3a4e54).

  And now Nvidia also need this feature to add Option
  "nvidiaXineramaInfo" "off" to fix some issues.

  Btw, I'm thinking it might be a more flexible to have a config file
  which user could add all options as they want so that we could prevent
  keeping change gpu-manager when some more options are needed in the
  future.

  Needed by LP: #1653592

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1667198/+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 1672619] Re: "disable touchpad while typing" doesn't work on xps 13 and some other laptop

[Anthony Wong]

YC, can you post the output from xinput?

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

Title:
  "disable touchpad while typing" doesn't work on xps 13 and some other
  laptop

Status in OEM Priority Project:
  Triaged
Status in Xserver Xorg Input Synaptics:
  Confirmed
Status in xserver-xorg-input-synaptics package in Ubuntu:
  New

Bug description:
  It's reported that there are lots of false action of touch pad as using 
keyboard on xps 13
  with the factory image.

  The factory image is based on xenial.

  One propose that install xserver-xorg-input-libinput with modification
  90-libinput.conf in /usr/share/X11/xorg.conf.d from

  ...
  Section "InputClass"
  Identifier "libinput touchpad catchall"
  MatchIsTouchpad "on"
  MatchDevicePath "/dev/input/event*"
  Driver "libinput"
  EndSection
  ...

  to

  ...
  Section "InputClass"
  Identifier "libinput touchpad catchall"
  MatchIsTouchpad "on"
  MatchDevicePath "/dev/input/event*"
  Driver "libinput"
  Option "Tapping" "on"
  Option "PalmDetection" "on"
  EndSection
  ...

  helps a lot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1672619/+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 1672619] Re: "disable touchpad while typing" doesn't work on xps 13 and some other laptop

[Anthony Wong]

** Also affects: xserver-xorg-input-synaptics
   Importance: Undecided
   Status: New

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

Title:
  "disable touchpad while typing" doesn't work on xps 13 and some other
  laptop

Status in OEM Priority Project:
  Triaged
Status in Xserver Xorg Input Synaptics:
  New
Status in xserver-xorg-input-synaptics package in Ubuntu:
  New

Bug description:
  It's reported that there are lots of false action of touch pad as using 
keyboard on xps 13
  with the factory image.

  The factory image is based on xenial.

  One propose that install xserver-xorg-input-libinput with modification
  90-libinput.conf in /usr/share/X11/xorg.conf.d from

  ...
  Section "InputClass"
  Identifier "libinput touchpad catchall"
  MatchIsTouchpad "on"
  MatchDevicePath "/dev/input/event*"
  Driver "libinput"
  EndSection
  ...

  to

  ...
  Section "InputClass"
  Identifier "libinput touchpad catchall"
  MatchIsTouchpad "on"
  MatchDevicePath "/dev/input/event*"
  Driver "libinput"
  Option "Tapping" "on"
  Option "PalmDetection" "on"
  EndSection
  ...

  helps a lot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1672619/+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 1549163] Re: Bluetooth headset HSP/HFP mode not working in Xenial

[Anthony Wong]

** 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 pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1549163

Title:
  Bluetooth headset HSP/HFP mode not working in Xenial

Status in HWE Next:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Using the 2/14 Xenial daily build, paired bluetooth headsets' do not
  work in HSP/HFP mode.

  [Steps to reproduce]
  1. Pair a bluetooth headset with laptop installed with Xenial 2/14 daily build
  2. In the laptop, go to sound settings > output tab > try switching mode to 
HSP/HFP mode
  3. Press the "test sound" button and try playing sound
  4. Go to the input tab and check if bluetooth headset mic is listed

  [Expected result]
  After step 3, a window for mono audio test should pop up
  After step 4, the input tab should list a bluetooth headset mic device

  [Actual result]
  After step 3, the window that pops up is for stereo (A2DP) audio test
  After step 4, the input tab does not list any bluetooth headset mic

  [Details]
  BT wireless module:
   * Intel 3160
  BT headset:
   * Jabra CLI
  Xenial: 2/14 daily build:
   * Kernel: 4.4.0-6
   * bluez: 5.36-0ubuntu1
   * gstreamer1.0-pulseaudio:amd64: 1.7.2-1ubuntu1
   * pulseaudio: 1:8.0-0ubuntu2
   * pulseaudio-module-bluetooth: 1:8.0-0ubuntu2

  [Note]
  Also double checked with same set of hardware, but with 15.10 installed.
  Bluetooth headset HSP/HFP mode worked correctly in 15.10.

  15.10 details:
   * kernel: 4.2.0-19
   * bluez: 5.35-0ubuntu2
   * gstreamer1.0-pulseaudio:amd64: 1.6.0-1ubuntu1
   * pulseaudio: 1:6.0-0ubuntu13
   * pulseaudio-module-bluetooth: 1:6.0-0ubuntu13

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1549163/+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 1119820] Re: quirk some platforms to remove psmouse before suspend

[Anthony Wong]

** Changed in: jockey (Ubuntu)
   Status: New => Won't Fix

** Changed in: hwe-next
   Status: Triaged => Won't Fix

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

Title:
  quirk some platforms to remove psmouse before suspend

Status in HWE Next:
  Won't Fix
Status in jockey package in Ubuntu:
  Won't Fix

Bug description:
  The Lenovo E435 was quirked during hardware enablement so that the
  psmouse driver would be unloaded when going to Hibernate and reloaded
  when coming back from hibernate. We should include this quirk in 12.10
  so that we don't have a feature regression.

  Summary: After s4 hibernate, on logging back into the desktop the
  touchpad does not control the mouse cursor.

  Steps:
  1) Log into desktop.
  2) Click on the power button in the upper right corner of the desktop.
  3) Select Hibernate and close the lid.
  4) Once the system is in the hibernate state, open the lid.
  5) Log in the user.
  6) use the touchpad to move the mouse cursor.

  Expected results: The cursor moves as expected.

  Actual results: The cursor remains where it was before S4

  WORKAROUND: Closing the lid to initiate s3, then opening the lid will
  bring back the touchpad functionality.

  
  CPU: AMD A8-4500M APU with Radeon(tm) HD Graphics (4x)

  GPU:
  00:01.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI 
Device 9903
  01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI 
Seymour [Radeon HD 6400M Series]

  Manufacturer: LENOVO

  Model: ThinkPad Edge E435

  SKU: 3256S06

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1119820/+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 1647283] Re: WiFi being detected as ethernet when race condition on renaming for persistent name

[Anthony Wong]

** 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 network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1647283

Title:
  WiFi being detected as ethernet when race condition on renaming for
  persistent name

Status in HWE Next:
  Fix Released
Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project xenial series:
  New
Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  Forwarded https://bugzilla.gnome.org/show_bug.cgi?id=775613

  Version: NetworkManager 1.4.2

  This bug happens after power-on with probability about 1/50.
  That means we need to reboot about 50 times to get into the buggy situation.
  "nmcli d" shows the device type is ethernet:

  DEVICE   TYPE  STATECONNECTION
  wlp1s0   ethernet  unavailable  --
  lo   loopback  unmanaged--

  The bug starts from a race condition. But it is not the root cause.
  I've also attach 2 logs. One is in good situation. Another is in bad 
situation.
  This log is generated by applying a "log patch" to network-manager 1.4.2 so 
we can see more stuff.

  In the bad situation. The bug starts with race condition. But the race 
condition is not the root cause. The race condition is:
   * During the renaming from "wlan0" to "wlp1s0". "wlan0" disappeared.
   * Inside the NM, it is still using "wlan0" in "_linktype_get_type()".
   * Since /sys/class/net/wlan0/uevent is disappeared. so the type matching 
failed in _linktype_get_type().
   * Also wifi_utils_is_wifi() failed to because /sys/class/net/wlan0 
disappeared.
   * And finally, devtype and kind are both NULL, so it returns 
NM_LINK_TYPE_ETHERNET for wlan0.

  Later, wlan0 is renamed to wlp1s0, and it seems to me that the Object inherit 
the type so it is still type ethernet.
  But from the log, I saw _linktype_get_type() is called several times later 
and return the correct type (wifi). But just, "nmcli d" still shows type 
ethernet.

  I'm wondering if we are missing to update the type in the Object
  created after renaming and re-detecting the type.

  fix need landing LP: #1645698

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1647283/+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 1652876] Re: No proprietary driver available for NVIDIA [10de:13b4]

[Anthony Wong]

** Changed in: ubuntu-drivers-common (Ubuntu)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

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

Title:
  No proprietary driver available for NVIDIA [10de:13b4]

Status in HWE Next:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  This is a hybrid graphic system, but there is no proprietary driver
  available for the NVIDIA graphic card on this system.

  01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:13b4] (rev a2)
Subsystem: Dell Device [1028:07a9]
Kernel driver in use: nouveau
Kernel modules: nvidiafb, nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1652876/+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 1649763] Re: Dell XPS 15 2016 with Ubuntu 16 Sound HDMI issues

[Anthony Wong]

** Package changed: unity (Ubuntu) => unity-control-center (Ubuntu)

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

Title:
  Dell XPS 15 2016 with Ubuntu 16 Sound HDMI issues

Status in unity-control-center package in Ubuntu:
  New

Bug description:
  This issue is related to sound not working properly on Ubuntu when
  switching between an external display using HDMI with 4K resolution
  and the standard laptop display.

  Issue 1 - Sound only works on laptop when plugged into 4k HDMI display
  Issue 2 - Sound doesn't work when plugged removed from 4k HDMI display

  When you plug in a 4k Display that supports sound to the Dell XPS 15
  2016 model the sound only works on the laptop. Only when you go to
  Sound Settings and manually select the HDMI output for sound does the
  sound start to work on the display itself instead of the laptop.

  When you unplug the HDMI 4k display the sound doesn't work on the
  laptop. When you go to the Sound Settings dialog it only shows one
  output that is selected - if you select the same output thats already
  selected the sound starts to work again on the laptop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1649763/+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 1647283] Re: WiFi being detected as ethernet when race condition on renaming for persistent name

[Anthony Wong]

** Changed in: network-manager (Ubuntu)
 Assignee: (unassigned) => Aron Xu (happyaron)

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

Title:
  WiFi being detected as ethernet when race condition on renaming for
  persistent name

Status in HWE Next:
  New
Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  
  Forwarded https://bugzilla.gnome.org/show_bug.cgi?id=775613

  Version: NetworkManager 1.4.2

  This bug happens after power-on with probability about 1/50.
  That means we need to reboot about 50 times to get into the buggy situation.
  "nmcli d" shows the device type is ethernet:

  DEVICE   TYPE  STATECONNECTION 
  wlp1s0   ethernet  unavailable  --
  lo   loopback  unmanaged-- 

  The bug starts from a race condition. But it is not the root cause.
  I've also attach 2 logs. One is in good situation. Another is in bad 
situation.
  This log is generated by applying a "log patch" to network-manager 1.4.2 so 
we can see more stuff.

  In the bad situation. The bug starts with race condition. But the race 
condition is not the root cause. The race condition is:
   * During the renaming from "wlan0" to "wlp1s0". "wlan0" disappeared.
   * Inside the NM, it is still using "wlan0" in "_linktype_get_type()".
   * Since /sys/class/net/wlan0/uevent is disappeared. so the type matching 
failed in _linktype_get_type().
   * Also wifi_utils_is_wifi() failed to because /sys/class/net/wlan0 
disappeared.
   * And finally, devtype and kind are both NULL, so it returns 
NM_LINK_TYPE_ETHERNET for wlan0.

  Later, wlan0 is renamed to wlp1s0, and it seems to me that the Object inherit 
the type so it is still type ethernet.
  But from the log, I saw _linktype_get_type() is called several times later 
and return the correct type (wifi). But just, "nmcli d" still shows type 
ethernet.

  I'm wondering if we are missing to update the type in the Object
  created after renaming and re-detecting the type.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1647283/+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 1643812] Re: There is no entry in 'Play sound through' list when plug in headset jack [8086:9d70].

[Anthony Wong]

** Tags added: kittyhawk originate-from-1613190

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

Title:
  There is no entry in 'Play sound through' list when plug in headset
  jack [8086:9d70].

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  New
Status in pulseaudio source package in Trusty:
  New

Bug description:
  1. Install 14.04.5 image on P50s
  2. Login system
  3. $ sudo apt-get update
  4. $ apt-get dist-upgrade
  sudo apt-get install --install-recommends linux-generic-lts-xenial 
xserver-xorg-core-lts-xenial xserver-xorg-lts-xenial 
xserver-xorg-video-all-lts-xenial xserver-xorg-input-all-lts-xenial 
libwayland-egl1-mesa-lts-xenial
  5. Reboot the system
  6. Login system
  7. Open Sound setting window
  8. Plug headset jack, unplug headset jack.

  The kernel is 4.4.0-47, and the pulseaudio is 1:4.0-0ubuntu1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1643812/+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 1643812] Re: There is no entry in 'Play sound through' list when plug in headset jack [8086:9d70].

[Anthony Wong]

** Changed in: pulseaudio (Ubuntu Trusty)
 Assignee: (unassigned) => Hui Wang (hui.wang)

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

Title:
  There is no entry in 'Play sound through' list when plug in headset
  jack [8086:9d70].

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

Bug description:
  1. Install 14.04.5 image on P50s
  2. Login system
  3. $ sudo apt-get update
  4. $ apt-get dist-upgrade
  sudo apt-get install --install-recommends linux-generic-lts-xenial 
xserver-xorg-core-lts-xenial xserver-xorg-lts-xenial 
xserver-xorg-video-all-lts-xenial xserver-xorg-input-all-lts-xenial 
libwayland-egl1-mesa-lts-xenial
  5. Reboot the system
  6. Login system
  7. Open Sound setting window
  8. Plug headset jack, unplug headset jack.

  The kernel is 4.4.0-47, and the pulseaudio is 1:4.0-0ubuntu1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1643812/+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 1646537] Re: Backlight sometimes fails to resume from suspend & screen brightness sometimes will not dim below 100%

[Anthony Wong]

** Changed in: linux (Ubuntu Vivid)
 Assignee: (unassigned) => AceLan Kao (acelankao)

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

Title:
  Backlight sometimes fails to resume from suspend & screen brightness
  sometimes will not dim below 100%

Status in linux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  New
Status in xorg source package in Vivid:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in xorg source package in Xenial:
  Invalid

Bug description:
  Back-light sometimes fails to resume from suspend & screen brightness
  sometimes will not dim below 100%

  Issue is interment in occurrence. Will be reproducible with the
  command "sudo pm-suspend" & or close/reopen laptop lid for a period of
  time days or hours, then go a period of time, days or hours without
  being able to trigger it again.

  This is irrespective of running "apt-get update && apt-get upgrade -y"
  and has continued to be intermittent on last 3 versions of 3.19
  kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-74.82~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-74-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.21
  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 Dec  1 10:06:43 2016
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150721-1
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:191b] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:06e5]
  InstallationDate: Installed on 2016-11-22 (8 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150721-23:28
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d4 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 5510
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-74-generic.efi.signed 
root=UUID=8eaa6744-6718-456a-bda0-762475144d35 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.14
  dmi.board.name: 0W7V82
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.14:bd08/31/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0W7V82:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 5510
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Dec  1 09:14:43 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5182 
   vendor SHP
  xserver.version: 2:1.17.1-0ubuntu3.1~trusty1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1646537/+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 1642662] Re: SRU request: handle EGL alternatives and use different drivers for the LTS stacks

[Anthony Wong]

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

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

Title:
  SRU request: handle EGL alternatives and use different drivers for the
  LTS stacks

Status in HWE Next:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in nvidia-prime source package in Trusty:
  Fix Released
Status in ubuntu-drivers-common source package in Trusty:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  A recent security update of the nvidia driver provided new EGL libraries and 
new kernel modules (such as nvidia-modeset and nvidia-drm), which are not 
handled by the current gpu-manager (ubuntu-drivers-common) and nvidia-prime in 
14.04. This problem is fixed in Xenial or newer.

  ubuntu-drivers-common also does not distinguish between the different
  LTS stacks, and this is a major problem on Intel+Nvidia hybrid
  systems, as anything running stacks older than 14.04.5 will require
  using the intel driver with SNA acceleration, whereas the rest should
  use the modesetting driver. Boot parameters can also be passed to use
  other driver combinations (for unsupported use cases).

  [Test Case]
  1) Enable the trusty-proposed repository, and install the 
ubuntu-drivers-common and the nvidia-prime packages.

  2) Install the nvidia driver.

  3) Restart the system and see if it boots correctly. If unsure, please
  attach your /var/log/gpu-manager.log and /var/log/Xorg.0.log

  [Regression Potential]
  Low, the above mentioned changes are already in Yakkety (and most of them 
have been in Xenial since its release).

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1642662/+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 1642662] Re: Handle EGL alternatives and use different drivers for the LTS stacks

[Anthony Wong]

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

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

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

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

Title:
  Handle EGL alternatives and use different drivers for the LTS stacks

Status in HWE Next:
  In Progress
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in nvidia-prime source package in Trusty:
  In Progress
Status in ubuntu-drivers-common source package in Trusty:
  In Progress

Bug description:
  A recent security update of the nvidia driver provided new EGL
  libraries, which are not handled by the current gpu-manager (ubuntu-
  drivers-common) and nvidia-prime in 14.04. This problem is fixed in
  Xenial or newer.

  ubuntu-drivers-common also does not distinguish between the different
  LTS stacks, and this is a major problem on Intel+Nvidia hybrid
  systems, as anything running stacks older than 14.04.5 will require
  using the intel driver with SNA acceleration, whereas the rest should
  use the modesetting driver. Boot parameters can also be passed to use
  other driver combinations (for unsupported use cases).

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1642662/+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 1639896] Re: Backport support for AMD Polaris

[Anthony Wong]

** Summary changed:

- Backport support for Polaris
+ Backport support for AMD Polaris

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

Title:
  Backport support for AMD Polaris

Status in mesa package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Invalid
Status in mesa source package in Xenial:
  New
Status in xserver-xorg-video-amdgpu source package in Xenial:
  New

Bug description:
  Xenial has x-x-v-amdgpu 1.1.0 but 1.1.2 adds more PCI-ID's and fixes
  bugs.

  Mesa needs a bunch of commits backported from 12.0.x.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1639896/+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 1636397] Re: Fix modesetting slave output names

[Anthony Wong]

** Tags added: originate-from-1626412 somerville

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

Title:
  Fix modesetting slave output names

Status in HWE Next:
  New
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Xenial:
  New
Status in xorg-server source package in Yakkety:
  New

Bug description:
  From a private bug:
  "Currently, NVIDIA and modesetting drivers are using same output names, that 
creates confusion for xrandr clients like gnome-setting-daemon or xrandr 
utility.

  When modesetting outputs act as slave for other x-screen (like NVIDIA
  X-screen here), modesetting driver uses different scheme of output
  names to avoid kind of confusion we are seeing here. There is a bug in
  modesetting X-driver gets shipped with X-server, which disables slave
  output's name scheme."

  From a reviewed upstream patch:

  "Commit c7e8d4a6ee9542f56cd241cf7a960fb8223a6b22 had already
  unifdef MODESETTING_OUTPUT_SLAVE_SUPPORT but commit
  9257b1252da9092ddc676fec9aabe2b33dfad272 didn't notice that."

  so we need to backport that to zesty/yakkety/xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1636397/+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 1515728] Re: After receiving a call while playing music the sound volume is very low and can't be raised

[Anthony Wong]

** Changed in: pulseaudio (Ubuntu RTM)
 Assignee: (unassigned) => Hui Wang (hui.wang)

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

Title:
  After receiving a call while playing music the sound volume is very
  low and can't be raised

Status in Canonical System Image:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu RTM:
  Confirmed

Bug description:
  Sound volume very low after a received call ends.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1515728/+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 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)

[Anthony Wong]

** Summary changed:

- Snap blocks access to system input methods (ibus, fctix, ...)
+ Snap blocks access to system input methods (ibus, fcitx, ...)

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

Title:
  Snap blocks access to system input methods (ibus, fcitx, ...)

Status in apparmor package in Ubuntu:
  In Progress
Status in im-config package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Fix Committed
Status in apparmor source package in Xenial:
  Triaged
Status in im-config source package in Xenial:
  In Progress
Status in snapd source package in Xenial:
  Fix Released
Status in apparmor source package in Yakkety:
  In Progress
Status in im-config source package in Yakkety:
  Fix Released
Status in snapd source package in Yakkety:
  Fix Committed

Bug description:
  = SRU im-config =
  [Impact]
  ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is 
indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has 
AppArmor mediation, ibus-daemon does not so it is important that its abstract 
socket not be confused with dbus-daemon's. By modifying ibus-daemon's start 
arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue 
mediating DBus abstract sockets like normal and also mediate access to the 
ibus-daemon-specific abstract socket via unix rules. This also tidies up the 
abstract socket paths so that it is clear which are for ibus-daemon, which for 
dbus-daemon, etc.

  The upload simply adjusts 21_ibus.rc to start ibus-daemon with "--
  address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code
  changes are required.

  [Test Case]
  1. start a unity session before updating to the package in -proposed

  2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 
  
IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76

  3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 2973 jamie8u unix 0x  0t0   29606 
@/tmp/dbus-oxKYpN30 type=STREAM

  4. update the package in -proposed and perform '2' and '3'. The
  IBUS_ADDRESSES should be the same as before

  5. logout of unity, then log back in

  6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 
  
IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e

  (notice '/tmp/ibus/' in the path)

  7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 3471 jamie8u unix 0x  0t0  26107 
@/tmp/ibus/dbus-SpxOl8Fc type=STREAM
  ...

  (notice '@/tmp/ibus/' in the path)

  In addition to the above, you can test for regressions by opening
  'System Settings' under the 'gear' icon in the panel and selecting
  'Text Entry'. From there, add an input source on the right, make sure
  'Show current input source in the menu bar' is checked, then use the
  input source panel indicator to change input sources.

  [Regression Potential]

  The regression potential is considered low because there are no
  compiled code changes and because the changes only occur after ibus-
  daemon is restarted, which is upon session start, not package upgrade.
  When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are
  updated accordingly for other applications to pick up.

  This change intentionally requires a change to the unity7 snapd
  interface, which is in progress. Currently the change should not
  regress snapdsbehavior due to other issues surrounding using ibus
  unrelated to security policy.

  = Original description =
  Currently snaps can't access ibus/fcitx from the system, do we need a 
interface for input methods there?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1580463/+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 1586641] Re: PCI/internal sound card not detected

[Anthony Wong]

** Changed in: alsa-driver (Ubuntu)
   Status: New => Triaged

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  Triaged

Bug description:
  My sound card is not even detected and alsamixer do nothing.

  I tried oem-audio-hda-daily-lts-xenial-dkms -
  0.201605271732~ubuntu16.04.1 https://code.launchpad.net/~ubuntu-audio-
  dev/+archive/ubuntu/alsa-daily/+packages like it was described here
  https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS but it didn't worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat May 28 15:20:10 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-27 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0T6HHJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd02/14/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7470
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1586641/+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 1586641] Re: PCI/internal sound card not detected

[Anthony Wong]

** Changed in: alsa-driver (Ubuntu)
 Assignee: Anthony Wong (anthonywong) => AceLan Kao (acelankao)

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  My sound card is not even detected and alsamixer do nothing.

  I tried oem-audio-hda-daily-lts-xenial-dkms -
  0.201605271732~ubuntu16.04.1 https://code.launchpad.net/~ubuntu-audio-
  dev/+archive/ubuntu/alsa-daily/+packages like it was described here
  https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS but it didn't worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat May 28 15:20:10 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-27 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0T6HHJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd02/14/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7470
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1586641/+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 1586641] Re: PCI/internal sound card not detected

[Anthony Wong]

** Changed in: alsa-driver (Ubuntu)
 Assignee: (unassigned) => Anthony Wong (anthonywong)

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  My sound card is not even detected and alsamixer do nothing.

  I tried oem-audio-hda-daily-lts-xenial-dkms -
  0.201605271732~ubuntu16.04.1 https://code.launchpad.net/~ubuntu-audio-
  dev/+archive/ubuntu/alsa-daily/+packages like it was described here
  https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS but it didn't worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat May 28 15:20:10 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-27 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0T6HHJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd02/14/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7470
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1586641/+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 1586641] Re: PCI/internal sound card not detected

[Anthony Wong]

I can't see there is any PCI device from the alsainfo.txt log, if the kernel 
can't see the device it could be related to something that is below the kernel 
level. You can also upload the output of 'lspci -vvnn' for us to check.
Could you also check if there are settings in the BIOS about audio? Perhaps you 
can try to reset the BIOS to the default and see what happens.

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  My sound card is not even detected and alsamixer do nothing.

  I tried oem-audio-hda-daily-lts-xenial-dkms -
  0.201605271732~ubuntu16.04.1 https://code.launchpad.net/~ubuntu-audio-
  dev/+archive/ubuntu/alsa-daily/+packages like it was described here
  https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS but it didn't worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat May 28 15:20:10 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-27 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0T6HHJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd02/14/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7470
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1586641/+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 1544477] Re: No sound notification for new SMS (Ubuntu Touch)

[Anthony Wong]

** Changed in: pulseaudio (Ubuntu)
 Assignee: Anthony Wong (anthonywong) => Hui Wang (hui.wang)

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

Title:
  No sound notification for new SMS (Ubuntu Touch)

Status in Canonical System Image:
  Confirmed
Status in media-hub package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I noticed for last 2-3 days there is no sound notification for a new
  SMS, but there's a blinking green LED notification. Also in the
  indicator menu the envelope icon turns green and the new SMS is listed
  as usual. Things are working alright for Telegram, Gmail etc.
  (sound+LED+indicator menu).

  Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+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 1569214] Re: [SRU] Patches needed for Telit modems used in IOT systems

[Anthony Wong]

** Changed in: modemmanager (Ubuntu)
   Status: New => Won't Fix

** Changed in: hwe-next
   Status: In Progress => Won't Fix

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

Title:
  [SRU] Patches needed for Telit modems used in IOT systems

Status in HWE Next:
  Won't Fix
Status in modemmanager package in Ubuntu:
  Won't Fix

Bug description:
  We have been informed by Telit that additional patches are required to
  enable their WWAN modems. Those patches are already upstreamed in
  modemmanager but not yet in Xenial.

  [Impact]
  Since this device is needed for 16.04 project, we need SRU for modemmanager.

  The patches are:

  * telit: add modem_power_down to telit plugin
  commit: 14e47710561b2021b79814afa5ecd6b2abc4fad0
  This patch implements ModemManager feature set-power-state-low that is the 
common approach to put
  the modem in +CFUN=4 state

  * telit: add modem_reset to telit plugin
  commit: 7978225934dc87bc74fac4d79a1080bc0501e581
  This commit solves the following issue:
    The reset command (mmcli –m 0 –r) needs to tie up with the AT command 
(AT#REBOOT)

  * telit: SIM unlock retries field
  Main commit: c4ffe572aeeefac240f16822ca1d2d258f78ad8d
  Related coding style commits: 740e1b5461bda9ff28f3ad2210ecf7238c38e785
  a74edab57f53ee8c920e681145070b252f5e656e
  46f601edf6046c6d6459f7aee45fca68bc93cee3
  0a88ae2d6d87967c0d951cc95de0c1917c78b0ed
  aae96778c54a59dcf3955c2d81bee393c0348077
  This patch is necessary to fill the field “Unlock retries”, visible when 
mmcli -m 0 is run.

  * telit: add load supported bands interface
  Main commit: 70b8ec1a88477eea3a2f569a83fc270ccaff9504
  Related coding style commits: 3911ea5a0f6b26e12a3586c75d72bb2c5820e3c1
  This patch adds supported bands information.

  * dell: fixed cgmi_retries in dell_custom_init
  commit: 8a386218690aeff7e2c923a14f91da7bbc046ed2
  This patch solves a random never-ending loop during port probing.

  [Test Case]
  We have the hardware to verify.

  [Regression Potential]
  By looking at those commits, they are self-contained to the telit plugin. 
These patches were asked by Telit to backport (we have the specification 
document from Telit but that's not public)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1569214/+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 1578196] Re: External Display Port monitor not working

[Anthony Wong]

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

** Also affects: xorg-server via
   https://bugs.freedesktop.org/show_bug.cgi?id=95269
   Importance: Unknown
   Status: Unknown

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

Title:
  External Display Port monitor not working

Status in X.Org X server:
  Unknown
Status in xorg package in Ubuntu:
  New

Bug description:
  I have three monitors on my Lenovo X250, one built-in and two
  connected via a Lenovo docking station :

  built-in: 1920x1080
  HP 2335: 1920x1200
  BenQ GW2765: 2560x1440

  The HP is connected via DVI and the BenQ via Display Port.

  In this configuration, I get my HP and built-in ok, but the BenQ
  doesn't show up at all (using xrandr --query).

  If I connect the BenQ via HDMI, then it shows up in xrandr --query,
  but the display is still blank (bandwidth issue?).

  Here's the output with the DVI + DP config :

  $ xrandr --query
  Screen 0: minimum 8 x 8, current 3840 x 1200, maximum 32767 x 32767
  eDP1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 
276mm x 156mm
 1920x1080 60.04*+  59.93  
 1680x1050 59.9559.88  
 1600x1024 60.17  
 1400x1050 59.98  
 1600x900  60.00  
 1280x1024 60.02  
 1440x900  59.89  
 1280x960  60.00  
 1368x768  60.00  
 1360x768  59.8059.96  
 1152x864  60.00  
 1280x720  60.00  
 1024x768  60.00  
 1024x576  60.00  
 960x540   60.00  
 800x600   60.3256.25  
 864x486   60.00  
 640x480   59.94  
 720x405   60.00  
 640x360   60.00  
  DP1 disconnected (normal left inverted right x axis y axis)
  DP2 disconnected (normal left inverted right x axis y axis)
  DP2-1 disconnected (normal left inverted right x axis y axis)
  DP2-2 connected primary 1920x1200+0+0 (normal left inverted right x axis y 
axis) 495mm x 310mm
 1920x1200 59.95*+
 1600x1200 60.00  
 1280x1024 85.0275.0260.02  
 1280x960  60.00  
 1152x864  75.00  
 1024x768  85.0075.0370.0760.00  
 832x624   74.55  
 800x600   75.0060.32  
 640x480   75.0059.94  
 720x400   70.08  
  DP2-3 disconnected (normal left inverted right x axis y axis)
  HDMI1 disconnected (normal left inverted right x axis y axis)
  HDMI2 disconnected (normal left inverted right x axis y axis)
  VIRTUAL1 disconnected (normal left inverted right x axis y axis)

  and with built-in and BenQ only :

  $ xrandr --query
  Screen 0: minimum 8 x 8, current 4480 x 1440, maximum 32767 x 32767
  eDP1 connected primary 1920x1080+0+360 (normal left inverted right x axis y 
axis) 276mm x 156mm
 1920x1080 60.04*+  59.93  
 1680x1050 59.9559.88  
 1600x1024 60.17  
 1400x1050 59.98  
 1600x900  60.00  
 1280x1024 60.02  
 1440x900  59.89  
 1280x960  60.00  
 1368x768  60.00  
 1360x768  59.8059.96  
 1152x864  60.00  
 1280x720  60.00  
 1024x768  60.00  
 1024x576  60.00  
 960x540   60.00  
 800x600   60.3256.25  
 864x486   60.00  
 640x480   59.94  
 720x405   60.00  
 640x360   60.00  
  DP1 disconnected (normal left inverted right x axis y axis)
  DP2 disconnected (normal left inverted right x axis y axis)
  DP2-1 connected 2560x1440+1920+0 (normal left inverted right x axis y axis) 
597mm x 336mm
 2560x1440 59.95*+
 1920x1080 60.0050.0059.94  
 1680x1050 59.88  
 1600x900  59.98  
 1280x1024 75.0260.02  
 1280x800  59.91  
 1152x864  75.00  
 1280x720  60.0050.0059.94  
 1024x768  75.0860.00  
 832x624   74.55  
 800x600   75.0060.32  
 720x576   50.00  
 720x480   60.0059.94  
 640x480   75.0060.0059.94  
 720x400   70.08  
  DP2-2 disconnected (normal left inverted right x axis y axis)
  DP2-3 disconnected (normal left inverted right x axis y axis)
  HDMI1 disconnected (normal left inverted right x axis y axis)
  HDMI2 disconnected (normal left inverted right x axis y axis)
  VIRTUAL1 disconnected (normal left inverted right x axis y axis)

  This looks relevant :

  

  I'm running kernel 4.6.0-040600rc6-generic (installed as part of the
  debugging process).

  (This bug is the 'next step' from
  )

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.6.0-040600rc6-generic x86_64
  

[Desktop-packages] [Bug 1569214] Re: [SRU] Patches needed for Telit modems used in IOT systems

[Anthony Wong]

debdiff attached.

** Attachment added: "debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1569214/+attachment/4633976/+files/debdiff

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

** Changed in: hwe-next
 Assignee: (unassigned) => Anthony Wong (anthonywong)

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

Title:
  [SRU] Patches needed for Telit modems used in IOT systems

Status in HWE Next:
  In Progress
Status in modemmanager package in Ubuntu:
  New

Bug description:
  We have been informed by Telit that additional patches are required to
  enable their WWAN modems. Those patches are already upstreamed in
  modemmanager but not yet in Xenial.

  [Impact]
  Since this device is needed for 16.04 project, we need SRU for modemmanager.

  The patches are:

  * telit: add modem_power_down to telit plugin
  commit: 14e47710561b2021b79814afa5ecd6b2abc4fad0
  This patch implements ModemManager feature set-power-state-low that is the 
common approach to put
  the modem in +CFUN=4 state

  * telit: add modem_reset to telit plugin
  commit: 7978225934dc87bc74fac4d79a1080bc0501e581
  This commit solves the following issue:
    The reset command (mmcli –m 0 –r) needs to tie up with the AT command 
(AT#REBOOT)

  * telit: SIM unlock retries field
  Main commit: c4ffe572aeeefac240f16822ca1d2d258f78ad8d
  Related coding style commits: 740e1b5461bda9ff28f3ad2210ecf7238c38e785
  a74edab57f53ee8c920e681145070b252f5e656e
  46f601edf6046c6d6459f7aee45fca68bc93cee3
  0a88ae2d6d87967c0d951cc95de0c1917c78b0ed
  aae96778c54a59dcf3955c2d81bee393c0348077
  This patch is necessary to fill the field “Unlock retries”, visible when 
mmcli -m 0 is run.

  * telit: add load supported bands interface
  Main commit: 70b8ec1a88477eea3a2f569a83fc270ccaff9504
  Related coding style commits: 3911ea5a0f6b26e12a3586c75d72bb2c5820e3c1
  This patch adds supported bands information.

  * dell: fixed cgmi_retries in dell_custom_init
  commit: 8a386218690aeff7e2c923a14f91da7bbc046ed2
  This patch solves a random never-ending loop during port probing.

  [Test Case]
  We have the hardware to verify.

  [Regression Potential]
  By looking at those commits, they are self-contained to the telit plugin. 
These patches were asked by Telit to backport (we have the specification 
document from Telit but that's not public)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1569214/+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 1569214] [NEW] [SRU] Patches needed for Telit modems used in IOT systems

[Anthony Wong]

Public bug reported:

We have been informed by Telit that additional patches are required to
enable their WWAN modems. Those patches are already upstreamed in
modemmanager but not yet in Xenial.

[Impact]
Since this device is needed for 16.04 project, we need SRU for modemmanager.

The patches are:

* telit: add modem_power_down to telit plugin
commit: 14e47710561b2021b79814afa5ecd6b2abc4fad0
This patch implements ModemManager feature set-power-state-low that is the 
common approach to put
the modem in +CFUN=4 state

* telit: add modem_reset to telit plugin
commit: 7978225934dc87bc74fac4d79a1080bc0501e581
This commit solves the following issue:
  The reset command (mmcli –m 0 –r) needs to tie up with the AT command 
(AT#REBOOT)

* telit: SIM unlock retries field
Main commit: c4ffe572aeeefac240f16822ca1d2d258f78ad8d
Related coding style commits: 740e1b5461bda9ff28f3ad2210ecf7238c38e785
a74edab57f53ee8c920e681145070b252f5e656e
46f601edf6046c6d6459f7aee45fca68bc93cee3
0a88ae2d6d87967c0d951cc95de0c1917c78b0ed
aae96778c54a59dcf3955c2d81bee393c0348077
This patch is necessary to fill the field “Unlock retries”, visible when mmcli 
-m 0 is run.

* telit: add load supported bands interface
Main commit: 70b8ec1a88477eea3a2f569a83fc270ccaff9504
Related coding style commits: 3911ea5a0f6b26e12a3586c75d72bb2c5820e3c1
This patch adds supported bands information.

* dell: fixed cgmi_retries in dell_custom_init
commit: 8a386218690aeff7e2c923a14f91da7bbc046ed2
This patch solves a random never-ending loop during port probing.

[Test Case]
We have the hardware to verify.

[Regression Potential]
By looking at those commits, they are self-contained to the telit plugin. These 
patches were asked by Telit to backport (we have the specification document 
from Telit but that's not public)

** Affects: hwe-next
 Importance: Undecided
 Status: New

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


** Tags: originate-from-1568216 somerville

** Summary changed:

- Patches needed for Telit modems used in IOT systems
+ [SRU] Patches needed for Telit modems used in IOT systems

** Description changed:

  We have been informed by Telit that additional patches are required to
  enable their WWAN modems. Those patches are already upstreamed in
  modemmanager but not yet in Xenial.
+ 
+ Since this device is needed for 16.04 project, we need SRU for
+ modemmanager.
  
  The patches are:
  
  * telit: add modem_power_down to telit plugin
  commit: 14e47710561b2021b79814afa5ecd6b2abc4fad0
  This patch implements ModemManager feature set-power-state-low that is the 
common approach to put
  the modem in +CFUN=4 state
  
  * telit: add modem_reset to telit plugin
  commit: 7978225934dc87bc74fac4d79a1080bc0501e581
  This commit solves the following issue:
-   The reset command (mmcli –m 0 –r) needs to tie up with the AT command 
(AT#REBOOT)
+   The reset command (mmcli –m 0 –r) needs to tie up with the AT command 
(AT#REBOOT)
  
  * telit: SIM unlock retries field
  Main commit: c4ffe572aeeefac240f16822ca1d2d258f78ad8d
  Related coding style commits: 740e1b5461bda9ff28f3ad2210ecf7238c38e785
  a74edab57f53ee8c920e681145070b252f5e656e
  46f601edf6046c6d6459f7aee45fca68bc93cee3
  0a88ae2d6d87967c0d951cc95de0c1917c78b0ed
  aae96778c54a59dcf3955c2d81bee393c0348077
  This patch is necessary to fill the field “Unlock retries”, visible when 
mmcli -m 0 is run.
  
  * telit: add load supported bands interface
  Main commit: 70b8ec1a88477eea3a2f569a83fc270ccaff9504
  Related coding style commits: 3911ea5a0f6b26e12a3586c75d72bb2c5820e3c1
  This patch adds supported bands information.
  
  * dell: fixed cgmi_retries in dell_custom_init
  commit: 8a386218690aeff7e2c923a14f91da7bbc046ed2
  This patch solves a random never-ending loop during port probing.

** Description changed:

  We have been informed by Telit that additional patches are required to
  enable their WWAN modems. Those patches are already upstreamed in
  modemmanager but not yet in Xenial.
  
- Since this device is needed for 16.04 project, we need SRU for
- modemmanager.
+ [Impact]
+ Since this device is needed for 16.04 project, we need SRU for modemmanager.
  
  The patches are:
  
  * telit: add modem_power_down to telit plugin
  commit: 14e47710561b2021b79814afa5ecd6b2abc4fad0
  This patch implements ModemManager feature set-power-state-low that is the 
common approach to put
  the modem in +CFUN=4 state
  
  * telit: add modem_reset to telit plugin
  commit: 7978225934dc87bc74fac4d79a1080bc0501e581
  This commit solves the following issue:
    The reset command (mmcli –m 0 –r) needs to tie up with the AT command 
(AT#REBOOT)
  
  * telit: SIM unlock retries field
  Main commit: c4ffe572aeeefac240f16822ca1d2d258f78ad8d
  Related coding style commits: 740e1b5461bda9ff28f3ad2210ecf7238c38e785
  a74edab57f53ee8c920e681145070b252f5e656e
  46f601edf6046c6d6459f7aee45fca68bc93cee3
  0a88ae2d6d87967c0d951cc95de0c1917c78b0ed
  

[Desktop-packages] [Bug 1549163] Re: Bluetooth headset HSP/HFP mode not working in Xenial

[Anthony Wong]

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => David Henningsson (diwic)

** Tags added: originate-from-1549165 somerville

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

Title:
  Bluetooth headset HSP/HFP mode not working in Xenial

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Using the 2/14 Xenial daily build, paired bluetooth headsets' do not
  work in HSP/HFP mode.

  [Steps to reproduce]
  1. Pair a bluetooth headset with laptop installed with Xenial 2/14 daily build
  2. In the laptop, go to sound settings > output tab > try switching mode to 
HSP/HFP mode
  3. Press the "test sound" button and try playing sound
  4. Go to the input tab and check if bluetooth headset mic is listed

  [Expected result]
  After step 3, a window for mono audio test should pop up
  After step 4, the input tab should list a bluetooth headset mic device

  [Actual result]
  After step 3, the window that pops up is for stereo (A2DP) audio test
  After step 4, the input tab does not list any bluetooth headset mic

  [Details]
  BT wireless module:
   * Intel 3160
  BT headset:
   * Jabra CLI
  Xenial: 2/14 daily build:
   * Kernel: 4.4.0-6
   * bluez: 5.36-0ubuntu1
   * gstreamer1.0-pulseaudio:amd64: 1.7.2-1ubuntu1
   * pulseaudio: 1:8.0-0ubuntu2
   * pulseaudio-module-bluetooth: 1:8.0-0ubuntu2

  [Note]
  Also double checked with same set of hardware, but with 15.10 installed.
  Bluetooth headset HSP/HFP mode worked correctly in 15.10.

  15.10 details:
   * kernel: 4.2.0-19
   * bluez: 5.35-0ubuntu2
   * gstreamer1.0-pulseaudio:amd64: 1.6.0-1ubuntu1
   * pulseaudio: 1:6.0-0ubuntu13
   * pulseaudio-module-bluetooth: 1:6.0-0ubuntu13

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

[Anthony Wong]

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

-- 
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:
  Fix Released
Status in xorg package in Ubuntu:
  Fix Released

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 1409675] Re: [Dell Latitude E5450, Realtek ALC293] Microphone is being detected as headphone

[Anthony Wong]

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

** Changed in: hwe-next
   Status: Triaged => Won't Fix

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

Title:
  [Dell Latitude E5450, Realtek ALC293] Microphone is being detected as
  headphone

Status in HWE Next:
  Won't Fix
Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  
  External microphone is not working when plugged into the headset(combo) jack, 
even plugging headset(four rings) into the jack the headset micrphone will not 
working. 
  However built-in (next to webcam) micrphone works perfectly, with above 
situation.

  Step to reproduce:

  1. plug the headset or microphone connector into the headset jack on
  the side of laptop

  Expected result:

  Recording voice with plugged/exertnal microphone

  Actual result:

  Recording only went throug the buil-in microphone.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1385 F pulseaudio
   /dev/snd/controlC1:  ubuntu 1385 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jan 12 05:38:33 2015
  InstallationDate: Installed on 2015-01-12 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: None of the above
  Title: [Latitude E5450, Realtek ALC293, Mic, Internal] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 013BI5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X03
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd08/06/2014:svnDellInc.:pnLatitudeE5450:pvr01:rvnDellInc.:rn013BI5:rvrX03:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5450
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1409675/+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 1434372] Re: [Lenovo E555] Screen of laptop will become black and never lighting after un-plug VGA cable

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Won't Fix

** Changed in: xorg (Ubuntu)
 Assignee: Liming Wang (wangliming) => (unassigned)

** Changed in: hwe-next
 Assignee: Liming Wang (wangliming) => (unassigned)

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

Title:
  [Lenovo E555] Screen of laptop will become black and never lighting
  after un-plug VGA cable

Status in HWE Next:
  Won't Fix
Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  CID: 201408-15472 Lenovo E555 (A+A) with 14.04.2 (utopic)

  Steps:
  1. Install 14.04.2 on E555
  2. Install fglrx
  3. Reboot system and log in 
  4. Plug in a VGA cable and switch 4 modes by display key. (external, 
internal, extand and mirror)
  5. Un-plug VGA cable, observe screen result.

  Expected results:
  Labtop screen display normally.

  Actual result:
  Labtop screen became black and never lighting. Only press power button off/on 
machine, that could make screen light again.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1 [modified: 
boot/vmlinuz-3.16.0-30-generic]
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 19 23:58:26 2015
  InstallationDate: Installed on 2015-03-18 (1 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: linux-lts-utopic
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.7
  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
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 15.03.00, 3.16.0-30-generic, x86_64: installed
   tp-smapi, 0.41, 3.16.0-30-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R6 Graphics] 
[1002:130a] (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:130a]
  InstallationDate: Installed on 2015-05-26 (0 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: LENOVO 20DHZ092US
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic 
root=UUID=16647c0b-7fa4-4597-8b86-38225335cfcc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Tags:  trusty ubuntu compiz-0.9
  Uname: Linux 3.16.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/17/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: HTET37WW (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20DHZ092US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrHTET37WW(1.09):bd10/17/2014:svnLENOVO:pn20DHZ092US:pvrThinkPadE555:rvnLENOVO:rn20DHZ092US:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20DHZ092US
  dmi.product.version: ThinkPad E555
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue May 26 00:31:42 2015
  xserver.configfile: default
  xserver.errors:
   RADEON(G0): [drm] Failed to open DRM device for pci::01:00.0: No such 
file or directory
   RADEON(G0): Kernel modesetting setup failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.16.0-1ubuntu1.2~trusty2
  xserver.video_driver: radeon

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

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

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

[Anthony Wong]

** Changed in: hwe-next
   Status: Incomplete => Won't Fix

-- 
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:
  Won't Fix
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 1499665] Re: [SynPS/2 Synaptics TouchPad] TouchPad not working after installtion

[Anthony Wong]

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

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

Title:
  [SynPS/2 Synaptics TouchPad] TouchPad not working after installtion

Status in HWE Next:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  During installation touchpad works perfectly, but after trusty(3.19)
  installed, and restarted, touchpad unable to use anymore.

  Steps to reproduce:

  1. Boot system with 14.04.3 live usb
  2. Install the system

  Expected result:
  Touchpad works normally as in live environment 

  Actual results:
  Touchpad no response

  
  Additional Info.:
  $ xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech USB-PS/2 Optical Mouse id=9[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ DLLC6D7:00 06CB:796Aid=12   [slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=14   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Sleep Buttonid=8[slave  
keyboard (3)]
  ↳ Integrated_Webcam_HDid=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=15   [slave  
keyboard (3)]

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-28.30~14.04.1-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  .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: Fri Sep 25 17:48:59 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation ValleyView Gen7 [8086:0f31] (rev 0e) (prog-if 00 [VGA 
controller])
     Subsystem: Dell Device [1028:06d7]
  InstallationDate: Installed on 2015-09-22 (2 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Dell Inc. Inspiron 5551
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic.efi.signed 
root=UUID=3bf855c2-39fe-4325-a1cc-960930d96a9e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: X16
  dmi.board.asset.tag: AFTPASS
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: AFTPASS
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: X16
  dmi.modalias: 
dmi:bvnDellInc.:bvrX16:bd01/28/2015:svnDellInc.:pnInspiron5551:pvrX16:rvnDellInc.:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnDellInc.:ct8:cvrX16:
  dmi.product.name: Inspiron 5551
  dmi.product.version: X16
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Sep 25 17:06:43 2015
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5100
   vendor AUO
  xserver.version: 2:1.17.1-0ubuntu3.1~trusty1
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CasperVersion: 1.340.2
  CompizPlugins: No value set for 

[Desktop-packages] [Bug 1503168] Re: [Dell Inspiron 5551][8086:0f31] Unable to adjust brightness

[Anthony Wong]

** Changed in: hwe-next
   Status: Incomplete => Won't Fix

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

Title:
  [Dell Inspiron 5551][8086:0f31] Unable to adjust brightness

Status in HWE Next:
  Won't Fix
Status in xorg package in Ubuntu:
  New

Bug description:
  Failed to adjust brightness.

  Unable to change brightness with hotkeys or even system settings.

  Additional information:
  There are two backlight interfaces and the system seems to use the wrong one.
  /sys/class/backlight$ ls
  acpi_video0  intel_backlight

  Following commands proof that intel interfaces can controll the backlight:
  sudo sh -c "echo 2500 >> /sys/class/backlight/intel_backlight/brightness"


  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26
  Uname: Linux 3.13.0-65-generic x86_64
  .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
  Date: Tue Oct  6 15:25:21 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation ValleyView Gen7 [8086:0f31] (rev 0e) (prog-if 00 [VGA 
controller])
     Subsystem: Dell Device [1028:06d7]
  InstallationDate: Installed on 2015-10-05 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Inspiron 5551
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic.efi.signed 
root=UUID=2e69c3f8-b60b-4e26-beed-33717212e1e9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: X16
  dmi.board.asset.tag: AFTPASS
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: AFTPASS
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: X16
  dmi.modalias: 
dmi:bvnDellInc.:bvrX16:bd01/28/2015:svnDellInc.:pnInspiron5551:pvrX16:rvnDellInc.:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnDellInc.:ct8:cvrX16:
  dmi.product.name: Inspiron 5551
  dmi.product.version: X16
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  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.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Oct  6 14:20:56 2015
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5100
   vendor AUO
  xserver.version: 2:1.15.1-0ubuntu2.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1503168/+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 1535652] [NEW] Bluetooth headset is chosen in unity-control-center when plugging in a normal headphone

[Anthony Wong]

Public bug reported:

This bug is better explained by the reproduction steps:

1. pair a bluetooth headset and make sure it works
2. open sounds settings (unity-control-center sound)
3. select the bluetooth headset device
4. then select the internal speaker
5. plug in a common 3.5mm headphone to the computer

Notice that the bluetooth headset is automatically chosen, which I think
is a surprise to users, as user expects to use the headphone when he's
plugging that in.

** Affects: unity-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: wily

** Tags added: wily

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

Title:
  Bluetooth headset is chosen in unity-control-center when plugging in a
  normal headphone

Status in unity-control-center package in Ubuntu:
  New

Bug description:
  This bug is better explained by the reproduction steps:

  1. pair a bluetooth headset and make sure it works
  2. open sounds settings (unity-control-center sound)
  3. select the bluetooth headset device
  4. then select the internal speaker
  5. plug in a common 3.5mm headphone to the computer

  Notice that the bluetooth headset is automatically chosen, which I
  think is a surprise to users, as user expects to use the headphone
  when he's plugging that in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1535652/+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 1503168] Re: [Dell Inspiron 5551][8086:0f31] Unable to adjust brightness

[Anthony Wong]

I am confused, this bug is about brightness, but you mentioned wireless
hotkey in the last comments.

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

Title:
  [Dell Inspiron 5551][8086:0f31] Unable to adjust brightness

Status in HWE Next:
  Incomplete
Status in xorg package in Ubuntu:
  New

Bug description:
  Failed to adjust brightness.

  Unable to change brightness with hotkeys or even system settings.

  Additional information:
  There are two backlight interfaces and the system seems to use the wrong one.
  /sys/class/backlight$ ls
  acpi_video0  intel_backlight

  Following commands proof that intel interfaces can controll the backlight:
  sudo sh -c "echo 2500 >> /sys/class/backlight/intel_backlight/brightness"


  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26
  Uname: Linux 3.13.0-65-generic x86_64
  .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
  Date: Tue Oct  6 15:25:21 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation ValleyView Gen7 [8086:0f31] (rev 0e) (prog-if 00 [VGA 
controller])
     Subsystem: Dell Device [1028:06d7]
  InstallationDate: Installed on 2015-10-05 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Inspiron 5551
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic.efi.signed 
root=UUID=2e69c3f8-b60b-4e26-beed-33717212e1e9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: X16
  dmi.board.asset.tag: AFTPASS
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: AFTPASS
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: X16
  dmi.modalias: 
dmi:bvnDellInc.:bvrX16:bd01/28/2015:svnDellInc.:pnInspiron5551:pvrX16:rvnDellInc.:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnDellInc.:ct8:cvrX16:
  dmi.product.name: Inspiron 5551
  dmi.product.version: X16
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  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.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Oct  6 14:20:56 2015
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5100
   vendor AUO
  xserver.version: 2:1.15.1-0ubuntu2.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1503168/+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 1410801] Re: [AMD Richland + Topaz XT ] gpu-manager generated xorg.conf is not compatible with switchable graphics

[Anthony Wong]

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

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

Title:
  [AMD Richland + Topaz XT ] gpu-manager generated xorg.conf is not
  compatible with switchable graphics

Status in HWE Next:
  Fix Released
Status in fglrx-installer package in Ubuntu:
  Invalid
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in fglrx-installer source package in Trusty:
  Invalid
Status in ubuntu-drivers-common source package in Trusty:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Hybrid graphics systems with the AMD+AMD combination will not have an option 
to switch between power saving mode and performance mode.

  [Test case]
  1. Install 14.04 and the fglrx driver on a hybrid (laptop) system with two 
AMD GPUs
  2. Reboot the system
  3. Launch amdcccle and see if there is an option to switch between power 
profiles

  Expected result:
  * There should be an option to switch between power profiles

  [Regression potential]
  Low, as the change in gpu-manager only affects the codepath that deals with 
the above mentioned hardware combination.


  --

  This is a trusty system with two GPUs:
  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Richland [Radeon HD 8610G] [1002:990f]
  01:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] 
Topaz XT [Radeon R7 M260] [1002:6900]

  After installing fglrx driver, still not able to swtich in between
  graphics.

  Steps to reproduce:

  1. install system with trusty
  2. install fglrx
  3. sudo amdcccle

  Expected result:

  Able to see the optoin of switchable graphics

  Actual result:

  There is no such option.

  Verification:

  1. Adding "nogpumanager" to kernel parameter
  2. Recreate the xorg.conf with "amdconfig --initial".
  3. Reboot
  4. Open amdcccle
  You will able to see the option of switchable graphics

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubuntu-drivers-common 1:0.2.91.5
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jan 14 21:11:29 2015
  InstallationDate: Installed on 2015-01-14 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: ubuntu-drivers-common
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1410801/+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 1509921] Re: [HDA-Intel - HD-Audio Generic, recording] No sound at all

[Anthony Wong]

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

** Changed in: alsa-driver (Ubuntu)
 Assignee: (unassigned) => 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/1509921

Title:
  [HDA-Intel - HD-Audio Generic, recording] No sound at all

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

Bug description:
  This is a desktop box, with following ports:
  front jack: a single headset combo jack
  rear jacks: mic, speaker, line-in

  An "Analog Input" consistently show up even there is nothing plugged,
  but I'm not able to record via headset jack or rear mic jack, they all 
recorded with noises.

  00:01.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device 
[1002:9840]
  00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] FCH Azalia 
Controller [1022:780d] (rev 02)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
  Uname: Linux 3.13.0-66-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  1824 F pulseaudio
   /dev/snd/controlC0:  u  1824 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Oct 26 11:46:46 2015
  InstallationDate: Installed on 2015-10-23 (2 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic_1 failed
  Symptom_Card: Built-in Audio - HD-Audio Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  1824 F pulseaudio
   /dev/snd/controlC0:  u  1824 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HD-Audio Generic, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.0:bd05/21/2015:svnDellInc.:pnInspiron3655:pvr1.0.0:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.name: Inspiron 3655
  dmi.product.version: 1.0.0
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1509921/+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 1513384] Re: Missing "Front Headphone" in headset mic path

[Anthony Wong]

** 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 pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1513384

Title:
  Missing "Front Headphone" in headset mic path

Status in HWE Next:
  Fix Committed
Status in pulseaudio package in Ubuntu:
  Fix Committed

Bug description:
  Found in the wild on one of the machines we enable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1513384/+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 1503168] Re: [Dell Inspiron 5551][8086:0f31] Unable to adjust brightness

[Anthony Wong]

I see you test with 3.13. Does any later kernel or release can fix this?

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

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

Title:
  [Dell Inspiron 5551][8086:0f31] Unable to adjust brightness

Status in HWE Next:
  Incomplete
Status in xorg package in Ubuntu:
  New

Bug description:
  Failed to adjust brightness.

  Unable to change brightness with hotkeys or even system settings.

  Additional information:
  There are two backlight interfaces and the system seems to use the wrong one.
  /sys/class/backlight$ ls
  acpi_video0  intel_backlight

  Following commands proof that intel interfaces can controll the backlight:
  sudo sh -c "echo 2500 >> /sys/class/backlight/intel_backlight/brightness"


  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26
  Uname: Linux 3.13.0-65-generic x86_64
  .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
  Date: Tue Oct  6 15:25:21 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation ValleyView Gen7 [8086:0f31] (rev 0e) (prog-if 00 [VGA 
controller])
     Subsystem: Dell Device [1028:06d7]
  InstallationDate: Installed on 2015-10-05 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Inspiron 5551
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic.efi.signed 
root=UUID=2e69c3f8-b60b-4e26-beed-33717212e1e9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: X16
  dmi.board.asset.tag: AFTPASS
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: AFTPASS
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: X16
  dmi.modalias: 
dmi:bvnDellInc.:bvrX16:bd01/28/2015:svnDellInc.:pnInspiron5551:pvrX16:rvnDellInc.:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnDellInc.:ct8:cvrX16:
  dmi.product.name: Inspiron 5551
  dmi.product.version: X16
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  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.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Oct  6 14:20:56 2015
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5100
   vendor AUO
  xserver.version: 2:1.15.1-0ubuntu2.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1503168/+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 1479913] Re: SRU request: fglrx.ko fails because of backported GPL-only 'pci_ignore_hotplug' symbol

[Anthony Wong]

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

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

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

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

Title:
  SRU request: fglrx.ko fails because of backported GPL-only
  'pci_ignore_hotplug' symbol

Status in HWE Next:
  Fix Released
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:
  Fix Released
Status in fglrx-installer-updates source package in Trusty:
  Fix Released
Status in fglrx-installer source package in Vivid:
  Fix Released
Status in fglrx-installer-updates source package in Vivid:
  Fix Released

Bug description:
  [Impact]
  An update to the lts-vivid backported kernel (3.19.0-26) in Trusty and to the 
default kernel in Vivid, pulled in a commit that made pci_ignore_hotplug() GPL 
only. As a result, the DKMS module fails.

  [Test Case]
  Install the new packages and check that DKMS doesn't fail.

  [Regression Potential]
  Low, the patches are already included wily.

  __

  Have no idea what happened. Contact me if you need additional details.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: fglrx-core 2:15.200-0ubuntu4.1
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:

  ApportVersion: 2.17.2-0ubuntu1.2
  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: 3.19.0-26-generic
  Date: Thu Jul 30 12:05:59 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx-core, 15.200, 3.19.0-25-generic, x86_64: installed
   vboxhost, 4.3.30, 3.19.0-25-generic, x86_64: installed
   vboxhost, 4.3.30, 3.19.0-26-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Barts XT [Radeon HD 6870] [1002:6738] 
(prog-if 00 [VGA controller])
     Subsystem: Hightech Information System Ltd. Device [1787:2010]
  InstallationDate: Installed on 2012-09-16 (1046 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120905.2)
  MachineType: BIOSTAR Group A770E3
  PackageVersion: 2:15.200-0ubuntu4.1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic 
root=/dev/mapper/ubuntu-root ro radeon.nomodeset=1 radeon.dpm=1 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4.1
  SourcePackage: fglrx-installer
  Title: fglrx-core 2:15.200-0ubuntu4.1: fglrx-core kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080014
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: A770E3
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080014:bd04/21/2010:svnBIOSTARGroup:pnA770E3:pvr:rvnBIOSTARGroup:rnA770E3:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.name: A770E3
  dmi.sys.vendor: BIOSTAR Group
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.62+git1507210630.293f8f~gd~u
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.7~git1507230730.2ca1f7~gd~u
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.7~git1507230730.2ca1f7~gd~u
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Jul 30 09:44:01 2015
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.1-0ubuntu3
  xserver.video_driver: fglrx

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1479913/+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 1432976] Re: Battery hot key does not bring up the power management dialog in Trusty

[Anthony Wong]

** 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-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1432976

Title:
  Battery hot key does not bring up the power management dialog in
  Trusty

Status in HWE Next Project:
  Invalid
Status in unity-settings-daemon package in Ubuntu:
  In Progress

Bug description:
  * Impact
  the battery hotkey doesn't do anything

  * Test case:
  On a laptop with a special key for battery info press fn+f3
  - the power info dialog should be displayed

  * Regression potential
  the action used before was buggy, having a valid one shouldn't create any 
issue

  --

  CID: 201209-11840 Dell L322X

  The battery hotkey on this system (fn+f3) cannot bring up the power 
management dialog.
  Also verified with 14.04.2 on LiveUSB, it's not working as well.
  But it works with 12.04.5 on LiveUSB. (Maybe it's user-space related?)

  It seems that the key event could be detected properly, it could pass
  our checkbox test (which will check the '0xe071,0xef1:Battery Info'
  signal)

  ubuntu@201209-11840:~$ sudo showkey -k
  kb mode was ?UNKNOWN?
  [ if you are trying this under X, it might not work
  since the X server is also reading /dev/console ]

  press any key (program terminates 10s after last keypress)...
  keycode  28 release
  keycode 240 press
  keycode 240 release
  keycode 238 press
  keycode 238 release
  keycode  29 press
  ^Ccaught signal 2, cleaning up...
  ubuntu@201209-11840:~$

  ubuntu@201209-11840:~$ sudo showkey -s
  kb mode was ?UNKNOWN?
  [ if you are trying this under X, it might not work
  since the X server is also reading /dev/console ]

  press any key (program terminates 10s after last keypress)...
  0x9c
  0xe0 0x71 0xe0 0xf1
  ^Ccaught signal 2, cleaning up...
  ubuntu@201209-11840:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57 [modified: 
boot/vmlinuz-3.13.0-32-generic]
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1568 F pulseaudio
  CRDA:
   country TW:
    (2402 - 2472 @ 40), (3, 27)
    (5270 - 5330 @ 40), (3, 17), DFS
    (5735 - 5815 @ 40), (3, 30)
  CurrentDesktop: Unity
  Date: Tue Mar 17 03:29:53 2015
  HibernationDevice: RESUME=UUID=de4c68b6-83dc-477e-98f1-1696b3233a48
  InstallationDate: Installed on 2015-03-13 (3 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Dell Inc. XPS L322X
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed 
root=UUID=4039eaa6-fdf4-423a-ace9-930a8911122e ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-32-generic N/A
   linux-backports-modules-3.13.0-32-generic  N/A
   linux-firmware 1.127.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS L322X
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1432976/+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 1408510] Re: wallpaper settings becomes valid only after restart

[Anthony Wong]

** Changed in: ubuntukylin
   Status: Confirmed = Fix Released

** Changed in: unity-control-center (Ubuntu)
   Status: New = Fix Released

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

Title:
  wallpaper settings becomes valid only after  restart

Status in Ubuntu Kylin:
  Fix Released
Status in unity-control-center package in Ubuntu:
  Fix Released

Bug description:
  壁纸设置需要重启生效

  1. system settings - appearance  - Change Desktop Backgroud
  2. Failed
  3. Restart
  4. desktop backgroud changed

   Configuration:lenovo
OS: Vivid i386 Daily Build 20150106

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

[Anthony Wong]

** Changed in: hwe-next
   Status: Invalid = Confirmed

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