[Touch-packages] [Bug 1894606] Re: [SRU] Add profile-set for HP Thunderbolt Dock

2021-01-14 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1908167] Re: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic

2021-01-13 Thread 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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time

2020-11-22 Thread 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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620

2020-08-31 Thread 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 Ubuntu
Touch seeded packages, which is subscribed to alsa-lib 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620

2020-08-18 Thread Anthony Wong
** Tags added: originate-from-1887127 originate-from-1887878 sutton

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1882248] Re: [SRU] plug headset won't proper reconfig ouput to it on machine with default output

2020-08-11 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


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

2020-08-05 Thread Anthony Wong
** Tags added: originate-from-1874593 sutton

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/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
  

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

2020-08-04 Thread 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:
  

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

2020-08-04 Thread 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 

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

2020-07-27 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1883846] Re: hwdb: Mask rfkill event from intel-hid on HP platforms

2020-07-24 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  hwdb: Mask rfkill event from intel-hid on HP platforms

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

Bug description:
  [Impact]
  Press wireless hotkey on HP's latest generation laptops generate two rfkill 
events, prevent airplane mode from turning off.

  One event is from intel-hid and the other one is from hp-wireless.

  [Fix]
  Commit "hwdb: Mask rfkill event from intel-hid on HP platforms", to only use 
rfkill from hp-wireless.

  [Test]
  With the one-liner fix, press wireless hotkey only generate one rfkill event, 
hence airplane mode works as expected.

  [Regression Potential]
  Low, use hp-wireless over intel-hid is anticipated.

  any regression would likely result in missed rfkill events.

  [scope]

  this is fixed upstream by commit
  d8a9dd0dc17df77229d079afe29c05ae4a9e2ae9 which is not included in any
  version yet, so this is needed for f and g.

  @kaihengfeng is this needed on b and/or x as well?

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

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


[Touch-packages] [Bug 1883027] Re: dump_acpi_tables.py: fix incorrect output and change format

2020-06-23 Thread Anthony Wong
** Tags added: rls-ff-incoming

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

Title:
  dump_acpi_tables.py: fix incorrect output and change format

Status in Apport:
  Confirmed
Status in apport package in Ubuntu:
  Confirmed
Status in apport source package in Focal:
  Confirmed
Status in apport source package in Groovy:
  Confirmed

Bug description:
  dump_acpi_tables.py generates log files that is similar as the output
  from "acpidump" in acpica-tools. The output can be passed to other
  utilities in acpica-tools and fwts.

  It, however, has some subtle differences and some errors.

  Summary:

  1. ACPI tables have 4-char signatures - meaning SSDT's are SSDT, not
  SSDT1, SSDT2 and so on. Each table is unique by its table ID.

  Original:
    SSDT1, SSDT2, SSDT3 ...

  Changed:
    SSDT, SSDT, SSDT ...

  2. (Minor) acpidump outputs are all in upper cases

  3. (Minor) acpidump offset are aligned by data, not address

  Original:
    FFF0: 53 41 56 43 52 44 43 41 4E 43 52 4E 72 4E 50 4D  SAVCRDCANCRNrNPM
    1: 56 0A 04 00 0C FC FF FF FF 0A 03 0A 03 52 44 43  VRDC

  Changed:
  FFF0: 53 41 56 43 52 44 43 41 4E 43 52 4E 72 4E 50 4D  SAVCRDCANCRNrNPM
     1: 56 0A 04 00 0C FC FF FF FF 0A 03 0A 03 52 44 43  VRDC

  4. (Bug) dump_acpi_tables.py generates an extra line when data sizes
  are multiple of 16 bytes

  Original:
  05F0: 30 30 0B 00 08 00 A4 48 50 53 44 A4 53 50 53 44  00.HPSD.SPSD
  05F0: 30 30 0B 00 08 00 A4 48 50 53 44 A4 53 50 53 44 
 00.HPSD.SPSD

  Corrected:
  05F0: 30 30 0B 00 08 00 A4 48 50 53 44 A4 53 50 53 44  00.HPSD.SPSD

  5. (Bug) dump_acpi_tables.py misses an line when data sizes are
  multiple of 15 bytes

  Original:
  07E0: 42 0A 87 5C 2F 03 5F 53 42 5F 55 42 54 43 43 43  B..\/._SB_UBTCCC

  Corrected:
  07E0: 42 0A 87 5C 2F 03 5F 53 42 5F 55 42 54 43 43 43  B..\/._SB_UBTCCC
  07F0: 49 33 86 5C 2E 5F 53 42 5F 55 42 54 43 0A 80 I3.\._SB_UBTC..

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

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


[Touch-packages] [Bug 1883027] Re: dump_acpi_tables.py: fix incorrect output and change format

2020-06-22 Thread Anthony Wong
** Also affects: apport (Ubuntu Groovy)
   Importance: Undecided
   Status: New

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

** Changed in: apport (Ubuntu Focal)
   Status: New => Triaged

** Changed in: apport (Ubuntu Focal)
   Status: Triaged => Confirmed

** Changed in: apport (Ubuntu Groovy)
   Status: New => Confirmed

** Changed in: apport
   Status: New => Confirmed

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

Title:
  dump_acpi_tables.py: fix incorrect output and change format

Status in Apport:
  Confirmed
Status in apport package in Ubuntu:
  Confirmed
Status in apport source package in Focal:
  Confirmed
Status in apport source package in Groovy:
  Confirmed

Bug description:
  dump_acpi_tables.py generates log files that is similar as the output
  from "acpidump" in acpica-tools. The output can be passed to other
  utilities in acpica-tools and fwts.

  It, however, has some subtle differences and some errors.

  Summary:

  1. ACPI tables have 4-char signatures - meaning SSDT's are SSDT, not
  SSDT1, SSDT2 and so on. Each table is unique by its table ID.

  Original:
    SSDT1, SSDT2, SSDT3 ...

  Changed:
    SSDT, SSDT, SSDT ...

  2. (Minor) acpidump outputs are all in upper cases

  3. (Minor) acpidump offset are aligned by data, not address

  Original:
    FFF0: 53 41 56 43 52 44 43 41 4E 43 52 4E 72 4E 50 4D  SAVCRDCANCRNrNPM
    1: 56 0A 04 00 0C FC FF FF FF 0A 03 0A 03 52 44 43  VRDC

  Changed:
  FFF0: 53 41 56 43 52 44 43 41 4E 43 52 4E 72 4E 50 4D  SAVCRDCANCRNrNPM
     1: 56 0A 04 00 0C FC FF FF FF 0A 03 0A 03 52 44 43  VRDC

  4. (Bug) dump_acpi_tables.py generates an extra line when data sizes
  are multiple of 16 bytes

  Original:
  05F0: 30 30 0B 00 08 00 A4 48 50 53 44 A4 53 50 53 44  00.HPSD.SPSD
  05F0: 30 30 0B 00 08 00 A4 48 50 53 44 A4 53 50 53 44 
 00.HPSD.SPSD

  Corrected:
  05F0: 30 30 0B 00 08 00 A4 48 50 53 44 A4 53 50 53 44  00.HPSD.SPSD

  5. (Bug) dump_acpi_tables.py misses an line when data sizes are
  multiple of 15 bytes

  Original:
  07E0: 42 0A 87 5C 2F 03 5F 53 42 5F 55 42 54 43 43 43  B..\/._SB_UBTCCC

  Corrected:
  07E0: 42 0A 87 5C 2F 03 5F 53 42 5F 55 42 54 43 43 43  B..\/._SB_UBTCCC
  07F0: 49 33 86 5C 2E 5F 53 42 5F 55 42 54 43 0A 80 I3.\._SB_UBTC..

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

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


[Touch-packages] [Bug 1881549] Re: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke

2020-06-19 Thread 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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1883027] Re: dump_acpi_tables.py: fix incorrect output and change format

2020-06-16 Thread Anthony Wong
** Description changed:

  dump_acpi_tables.py generates log files that is similar as the output
- from "acpidump" in acpica-tools. The output can be past to other
- utilities in acpica-tools and / or fwts.
+ from "acpidump" in acpica-tools. The output can be passed to other
+ utilities in acpica-tools and fwts.
  
  It, however, has some subtle differences and some errors.
  
  Summary:
  
  1. ACPI tables have 4-char signatures - meaning SSDT's are SSDT, not
  SSDT1, SSDT2 and so on. Each table is unique by its table ID.
  
  Original:
    SSDT1, SSDT2, SSDT3 ...
  
  Changed:
    SSDT, SSDT, SSDT ...
  
  2. (Minor) acpidump outputs are all in upper cases
  
  3. (Minor) acpidump offset are aligned by data, not address
  
  Original:
    FFF0: 53 41 56 43 52 44 43 41 4E 43 52 4E 72 4E 50 4D  SAVCRDCANCRNrNPM
    1: 56 0A 04 00 0C FC FF FF FF 0A 03 0A 03 52 44 43  VRDC
  
  Changed:
  FFF0: 53 41 56 43 52 44 43 41 4E 43 52 4E 72 4E 50 4D  SAVCRDCANCRNrNPM
     1: 56 0A 04 00 0C FC FF FF FF 0A 03 0A 03 52 44 43  VRDC
  
  4. (Bug) dump_acpi_tables.py generates an extra line when data sizes are
  multiple of 16 bytes
  
  Original:
  05F0: 30 30 0B 00 08 00 A4 48 50 53 44 A4 53 50 53 44  00.HPSD.SPSD
  05F0: 30 30 0B 00 08 00 A4 48 50 53 44 A4 53 50 53 44 
 00.HPSD.SPSD
  
  Corrected:
  05F0: 30 30 0B 00 08 00 A4 48 50 53 44 A4 53 50 53 44  00.HPSD.SPSD
  
  5. (Bug) dump_acpi_tables.py misses an line when data sizes are multiple
  of 15 bytes
  
  Original:
  07E0: 42 0A 87 5C 2F 03 5F 53 42 5F 55 42 54 43 43 43  B..\/._SB_UBTCCC
  
  Corrected:
  07E0: 42 0A 87 5C 2F 03 5F 53 42 5F 55 42 54 43 43 43  B..\/._SB_UBTCCC
  07F0: 49 33 86 5C 2E 5F 53 42 5F 55 42 54 43 0A 80 I3.\._SB_UBTC..

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

Title:
  dump_acpi_tables.py: fix incorrect output and change format

Status in Apport:
  New
Status in apport package in Ubuntu:
  New

Bug description:
  dump_acpi_tables.py generates log files that is similar as the output
  from "acpidump" in acpica-tools. The output can be passed to other
  utilities in acpica-tools and fwts.

  It, however, has some subtle differences and some errors.

  Summary:

  1. ACPI tables have 4-char signatures - meaning SSDT's are SSDT, not
  SSDT1, SSDT2 and so on. Each table is unique by its table ID.

  Original:
    SSDT1, SSDT2, SSDT3 ...

  Changed:
    SSDT, SSDT, SSDT ...

  2. (Minor) acpidump outputs are all in upper cases

  3. (Minor) acpidump offset are aligned by data, not address

  Original:
    FFF0: 53 41 56 43 52 44 43 41 4E 43 52 4E 72 4E 50 4D  SAVCRDCANCRNrNPM
    1: 56 0A 04 00 0C FC FF FF FF 0A 03 0A 03 52 44 43  VRDC

  Changed:
  FFF0: 53 41 56 43 52 44 43 41 4E 43 52 4E 72 4E 50 4D  SAVCRDCANCRNrNPM
     1: 56 0A 04 00 0C FC FF FF FF 0A 03 0A 03 52 44 43  VRDC

  4. (Bug) dump_acpi_tables.py generates an extra line when data sizes
  are multiple of 16 bytes

  Original:
  05F0: 30 30 0B 00 08 00 A4 48 50 53 44 A4 53 50 53 44  00.HPSD.SPSD
  05F0: 30 30 0B 00 08 00 A4 48 50 53 44 A4 53 50 53 44 
 00.HPSD.SPSD

  Corrected:
  05F0: 30 30 0B 00 08 00 A4 48 50 53 44 A4 53 50 53 44  00.HPSD.SPSD

  5. (Bug) dump_acpi_tables.py misses an line when data sizes are
  multiple of 15 bytes

  Original:
  07E0: 42 0A 87 5C 2F 03 5F 53 42 5F 55 42 54 43 43 43  B..\/._SB_UBTCCC

  Corrected:
  07E0: 42 0A 87 5C 2F 03 5F 53 42 5F 55 42 54 43 43 43  B..\/._SB_UBTCCC
  07F0: 49 33 86 5C 2E 5F 53 42 5F 55 42 54 43 0A 80 I3.\._SB_UBTC..

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

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


[Touch-packages] [Bug 1881549] Re: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke

2020-06-10 Thread 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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1881549] Re: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke

2020-06-09 Thread 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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1881549] Re: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke

2020-06-03 Thread 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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1868210] Re: [SRU] Load ucm on Lenovo notebooks based on bios version

2020-04-28 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  [SRU] Load ucm on Lenovo notebooks based on bios version

Status in HWE Next:
  Fix Released
Status in alsa-lib package in Ubuntu:
  Invalid
Status in alsa-lib source package in Bionic:
  Fix Released
Status in alsa-lib source package in Eoan:
  Fix Released
Status in alsa-lib source package in Focal:
  Invalid

Bug description:
  This SRU is not backported from upstream of alsa-lib and this SRU is
  not going to be submitted to upstream. That is because the latest
  alsa-lib already supports ucm2, and with ucm2 all machines could share
  one ucm, so latest alsa-lib does not have this problem. This problem
  is only specific to the alsa-lib in Bionic and Eoan.

  [Impact]
  On some Lenovo notebooks, UCM files are not loaded and mic can't be used.

  [Fix]
  UCM was loaded based on cardlongname, but that can't cover all configs of the 
same model. Lenovo suggested to load  ucm by the first 3 letters of 
/sys/devices/virtual/dmi/id/bios_version, so that all configs could use just 
one ucm.

  [Test Case]
  After applying this patch, install the testing alsa-lib on Lenovo X1C7 and 
Dell vostro 5390, which are all machines with the DMIC connected to PCH. After 
system bootup, check the /usr/share/alsa/ucm/ for the presence of 
LENOVO-BIOSID-xxx directories.

  Lenovo X1C7 should load the N2H/*.conf and verify the audio
  functionalities. The Dell machine should still load the ucm by
  cardname, and it should work as good as before.

  [Regression Potential]
  low, just add some new UCMs and let Lenovo machine find the UCM by 
bios_version if it fails by cardlongname. I've already tested the change on 
Lenovo and Dell machines.

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

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


[Touch-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

2020-03-31 Thread 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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1859754] Re: [SRU] add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)

2020-03-24 Thread Anthony Wong
** Summary changed:

- add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 
7th, Dell cnl and cml machines)
+ [SRU] add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 
Carbon 7th, Dell cnl and cml machines)

** Changed in: alsa-lib (Ubuntu)
   Status: Fix Committed => Invalid

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

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

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

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

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

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

Title:
  [SRU] add ucm to make alsa/sof driver work under PA (variants of
  Lenovo X1 Carbon 7th, Dell cnl and cml machines)

Status in HWE Next:
  Fix Released
Status in alsa-lib package in Ubuntu:
  Invalid
Status in alsa-lib source package in Bionic:
  Fix Released
Status in alsa-lib source package in Eoan:
  Fix Released

Bug description:
  This ucm is only for Eoan and Bionic, for focal and future versions,
  we plan to integrate the ucm2 instead of this ucm, and the ucm2
  depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under
  developing by the community, is not ready yet.

  [Impact]
  In the oem project, we have a couple of Lenovo and Dell machines which
  connect the digital mic to PCH directly, this design needs the new
  sound driver soc/sof, and this driver can't work under pulseaudio
  automatically, we need to integrate the ucm for the driver, then the
  sof dirver could work under pulseaudio and gnome.

  This ucm is maintained by intel audio team, and it is not upstreamed
  and will not be upstreamed, since the community is developing the ucm2
  which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still
  under developing), for bionic and eoan, we have to integrate this ucm
  since the alsa-lib version is too low. For focal and future version, we
  are going to integrate the ucm2 after the ucm2 is ready.

  This ucm is already verified in the oem project, now it is time to put it
  into the stock ubuntu. 

  [Fix]
  These ucm files are backported from sof_ucm1 branch of
  https://github.com/thesofproject/alsa-ucm-conf.git

  [Test Case]
  Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of
  pulseaudio, the ucm files are loaded successfully, then check the
  gnome-sound-setting, both output and input devices work well.

  [Regression Risk]
  Low, just add some new ucm files, and this will not affect other machines,
  and those new added ucm files are only used by specific machines which enable
  the sof driver.

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

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


[Touch-packages] [Bug 1868210] Re: [SRU] Load ucm on Lenovo notebooks based on bios version

2020-03-23 Thread Anthony Wong
** Description changed:

  This SRU is not backported from upstream of alsa-lib and this SRU is not
  going to be submitted to upstream. That is because the latest alsa-lib
- already supported the ucm2 and with ucm2 all machines could share one
- ucm, so there is no this problem for latest alsa-lib. This problem is
- only specific to the alsa-lib of Eoan and Bionic.
+ already supports ucm2, and with ucm2 all machines could share one ucm,
+ so latest alsa-lib does not have this problem. This problem is only
+ specific to the alsa-lib in Bionic and Eoan.
  
  [Impact]
- On some lenovo notebooks, ucm files are not loaded and mic can't be used
+ On some Lenovo notebooks, UCM files are not loaded and mic can't be used.
  
  [Fix]
  UCM was loaded based on cardlongname, but that can't cover all configs of the 
same model. Lenovo suggested to load  ucm by the first 3 letters of 
/sys/devices/virtual/dmi/id/bios_version, so that all configs could use just 
one ucm.
  
  [Test Case]
- after applying this patch, I installed the testing alsa-lib on lenovo X1C7 
and Dell vostro5390 which are all machines with the dmic connected to pch, 
after booing up, I checked the /usr/share/alsa/ucm/, the LENOVO-BIOSID-xxx 
folders are there, and the LENOVO machine loaded the N2H/*.conf, it worked 
well, the Dell machine still loaded the ucm by cardname, it worked as good as 
before.
+ After applying this patch, install the testing alsa-lib on Lenovo X1C7 and 
Dell vostro 5390, which are all machines with the DMIC connected to PCH. After 
system bootup, check the /usr/share/alsa/ucm/ for the presence of 
LENOVO-BIOSID-xxx directories.
+ 
+ Lenovo X1C7 should load the N2H/*.conf and verify the audio
+ functionalities. The Dell machine should still load the ucm by cardname,
+ and it should work as good as before.
  
  [Regression Potential]
- low, just add some new ucms and let LENOVO machine find the ucm by 
bios_version if it fails by cardlongname. And already tested the change on 
lenovo and dell machines.
+ low, just add some new UCMs and let Lenovo machine find the UCM by 
bios_version if it fails by cardlongname. I've already tested the change on 
Lenovo and Dell machines.

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

Title:
  [SRU] Load ucm on Lenovo notebooks based on bios version

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Invalid
Status in alsa-lib source package in Bionic:
  Confirmed
Status in alsa-lib source package in Eoan:
  Confirmed
Status in alsa-lib source package in Focal:
  Invalid

Bug description:
  This SRU is not backported from upstream of alsa-lib and this SRU is
  not going to be submitted to upstream. That is because the latest
  alsa-lib already supports ucm2, and with ucm2 all machines could share
  one ucm, so latest alsa-lib does not have this problem. This problem
  is only specific to the alsa-lib in Bionic and Eoan.

  [Impact]
  On some Lenovo notebooks, UCM files are not loaded and mic can't be used.

  [Fix]
  UCM was loaded based on cardlongname, but that can't cover all configs of the 
same model. Lenovo suggested to load  ucm by the first 3 letters of 
/sys/devices/virtual/dmi/id/bios_version, so that all configs could use just 
one ucm.

  [Test Case]
  After applying this patch, install the testing alsa-lib on Lenovo X1C7 and 
Dell vostro 5390, which are all machines with the DMIC connected to PCH. After 
system bootup, check the /usr/share/alsa/ucm/ for the presence of 
LENOVO-BIOSID-xxx directories.

  Lenovo X1C7 should load the N2H/*.conf and verify the audio
  functionalities. The Dell machine should still load the ucm by
  cardname, and it should work as good as before.

  [Regression Potential]
  low, just add some new UCMs and let Lenovo machine find the UCM by 
bios_version if it fails by cardlongname. I've already tested the change on 
Lenovo and Dell machines.

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

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


[Touch-packages] [Bug 1868210] Re: [SRU] Load ucm on Lenovo notebooks based on bios version

2020-03-20 Thread Anthony Wong
** Changed in: alsa-lib (Ubuntu Focal)
   Status: New => Invalid

** Changed in: alsa-lib (Ubuntu Bionic)
   Status: New => Confirmed

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

** Changed in: alsa-lib (Ubuntu Focal)
   Importance: Critical => Undecided

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

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

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

Title:
  [SRU] Load ucm on Lenovo notebooks based on bios version

Status in alsa-lib package in Ubuntu:
  Invalid
Status in alsa-lib source package in Bionic:
  Confirmed
Status in alsa-lib source package in Focal:
  Invalid

Bug description:
  [Impact]
  On some lenovo notebooks, ucm files are not loaded and mic can't be used

  [Fix]
  UCM was loaded based on cardlongname, but that can't cover all configs of the 
same model. Lenovo suggested to load  ucm by the first 3 letters of 
/sys/devices/virtual/dmi/id/bios_version, so that all configs could use just 
one ucm.

  [Test Case]

  [Regression Potential]

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

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


[Touch-packages] [Bug 1868210] Re: [SRU] Load ucm on Lenovo notebooks based on bios version

2020-03-20 Thread Anthony Wong
** Also affects: alsa-lib (Ubuntu Focal)
   Importance: Critical
 Assignee: Hui Wang (hui.wang)
   Status: New

** Also affects: alsa-lib (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  [SRU] Load ucm on Lenovo notebooks based on bios version

Status in alsa-lib package in Ubuntu:
  Invalid
Status in alsa-lib source package in Bionic:
  Confirmed
Status in alsa-lib source package in Focal:
  Invalid

Bug description:
  [Impact]
  On some lenovo notebooks, ucm files are not loaded and mic can't be used

  [Fix]
  UCM was loaded based on cardlongname, but that can't cover all configs of the 
same model. Lenovo suggested to load  ucm by the first 3 letters of 
/sys/devices/virtual/dmi/id/bios_version, so that all configs could use just 
one ucm.

  [Test Case]

  [Regression Potential]

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

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


[Touch-packages] [Bug 1868210] [NEW] [SRU] Load ucm on Lenovo notebooks based on bios version

2020-03-20 Thread Anthony Wong
Public bug reported:

[Impact]
On some lenovo notebooks, ucm files are not loaded and mic can't be used

[Fix]
UCM was loaded based on cardlongname, but that can't cover all configs of the 
same model. Lenovo suggested to load  ucm by the first 3 letters of 
/sys/devices/virtual/dmi/id/bios_version, so that all configs could use just 
one ucm.

[Test Case]

[Regression Potential]

** Affects: alsa-lib (Ubuntu)
 Importance: Critical
 Assignee: Hui Wang (hui.wang)
 Status: New

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

Title:
  [SRU] Load ucm on Lenovo notebooks based on bios version

Status in alsa-lib package in Ubuntu:
  New

Bug description:
  [Impact]
  On some lenovo notebooks, ucm files are not loaded and mic can't be used

  [Fix]
  UCM was loaded based on cardlongname, but that can't cover all configs of the 
same model. Lenovo suggested to load  ucm by the first 3 letters of 
/sys/devices/virtual/dmi/id/bios_version, so that all configs could use just 
one ucm.

  [Test Case]

  [Regression Potential]

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

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


[Touch-packages] [Bug 1834138] Re: PA: Don't restore the streams to sinks/sources with only unavailable ports

2020-01-02 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)

2019-10-20 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1786574] Re: remove i2c-i801 from blacklist

2019-10-09 Thread Anthony Wong
Julian, what exactly is the problem you see in 19.10?

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

Title:
  remove i2c-i801 from blacklist

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  In Progress
Status in kmod package in Ubuntu:
  Fix Released
Status in kmod source package in Xenial:
  In Progress
Status in kmod source package in Bionic:
  In Progress
Status in kmod source package in Cosmic:
  In Progress

Bug description:
  SRU justification
  

  [Impact]
  Many modern notebooks need i2c-i801 kernel module to function, but it is 
blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user 
experience.

  [Test case]
  1. Install Ubuntu
  2. Check touchpad works or not
  3. Install the fixed kmod package
  4. Confirm touchpad works

  [Regression Potential]
  i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq 
nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a 
way to workaround the suspend issue, the proper fix should be in linux kernel. 
Since nc6000 was a machine sold in 2004, it is too difficult to find someone to 
verify if it will regress due to this SRU. The rationale to blacklist it is: 
https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, 
however it is no longer valid nowadays on modern computers.

  Besides, there look like to be a quirk in linux kernel that fixes it:
  https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434

  [Other Info]
  rationale of i2c_i801 driver blacklist: 
https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329

  
---
  Original bug report:

  We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module
  to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu.
  To use the touchpad, users have to remove the i2c-i801 line manually.

  i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000
  (Bug #16602), this module should be removed from blacklist.

  There is also another bug (Bug #1475945) that needs this module for
  Acer trackpad to work.

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

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


[Touch-packages] [Bug 1837700] Re: Dell system takes a long time to connect network with external dock

2019-09-10 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  Dell system takes a long time to connect network with external dock

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

Bug description:
  update for SRU process:

  [Impact]
  1. On system featured mac passthrough, e.g., Dell/Lenovo laptop, or system 
occasionally install two USB ethernet with same MAC address, the system will 
suffer 90 seconds for network interface renaming mechanism before the last USB 
ethernet interface to activate.

  [Test Case]
  1. Install ubuntu on Dell laptop.
  2. Connect the Dell laptop with two Realtek 8153 USB ethernet dongle. Users 
can observe the last one will take 90 seconds for renaming to rename0.
  3. Users can also find that the two USB ethernet have the same MAC address.

  [Regression Potential] 
  To resolve the issue, drop a debian patch from systemd package. The debian 
patch is to revert an upstream commit to support 
75-persistent-net-generator.rules udev rule. Since the udev rule is deprecated, 
the regression potential should be relatively low.

  ---

  
  Dell has a feature called MAC addrss passthrough[1] that would force usb 
ethernet adapters to be assigned with a predefined MAC address stored in BIOS 
or so. This feature has been landed to mainline kernel in driver r8152[2]. So 
whenever a r8152 managed device is plugged into Dell devices with MAC addrss 
passthrough enabled, this driver will set NIC MAC to a predefined one.

  And some Dell devices have already one built-in r8152 NIC port. On
  these devices, when a second r8152 NIC is plugged in, a Debian
  originated udev rules file 73-usb-net-by-mac.rules[3] will invoke udev
  built-in command `net_id` to give a persistent name, and that will be
  based on MAC address. However, since the system has already
  initialized the built-in r8152 NIC with that name, renaming the second
  interface with this name will always fail.

  While Debian still carries a patch called "Revert-udev-network-device-
  renaming-immediately-give.patch"[4] that tries to keep support of
  already deprecated "75-persistent-net-generator.rules" based interface
  renaming mechanism, this patch also propagated into Ubuntu[5]. This
  patch will retry renaming with a 90 seconds timeout when the error
  code is -EEXIST, so the uevent processing will always be blocked in
  the last ifrename step in the victim system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: udev 237-3ubuntu10.24 [modified: lib/udev/rules.d/50-firmware.rules 
lib/udev/rules.d/50-udev-default.rules 
lib/udev/rules.d/73-special-net-names.rules 
lib/udev/rules.d/73-usb-net-by-mac.rules]
  ProcVersionSignature: Ubuntu 4.15.0-1043.48-oem 4.15.18
  Uname: Linux 4.15.0-1043-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.core.rules 95-oem-hotkey-osd.rules
  Date: Wed Jul 24 15:30:59 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-jorah+X90
  InstallationDate: Installed on 2019-07-03 (20 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 7424 Rugged Extreme
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1043-oem.efi.signed 
root=UUID=5da90c85-3500-49a2-b989-71a604f9eec4 ro mem_sleep_default=deep quiet 
splash systemd.log_level=debug udev.log-priority=debug log_buf_len=8M 
vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0Y7FK3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd05/27/2019:svnDellInc.:pnLatitude7424RuggedExtreme:pvr:rvnDellInc.:rn0Y7FK3:rvrX03:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7424 Rugged Extreme
  dmi.sys.vendor: Dell Inc.

  [1]: 
https://www.dell.com/support/article/tw/zh/twdhs1/sln301147/what-is-mac-address-pass-through?lang=en
  [2]: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/usb/r8152.c
  [3]: 
https://salsa.debian.org/systemd-team/systemd/blob/master/debian/extra/rules/73-usb-net-by-mac.rules
  [4]: 

[Touch-packages] [Bug 1837700] Re: Dell system takes a long time to connect network with external dock

2019-07-24 Thread Anthony Wong
** Also affects: systemd (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  Dell system takes a long time to connect network with external dock

Status in HWE Next:
  New
Status in systemd package in Ubuntu:
  New
Status in systemd source package in Bionic:
  New

Bug description:
  Dell has a feature called MAC addrss passthrough[1] that would force
  usb ethernet adapters to be assigned with a predefined MAC address
  stored in BIOS or so. This feature has been landed to mainline kernel
  in driver r8152[2]. So whenever a r8152 managed device is plugged into
  Dell devices with MAC addrss passthrough enabled, this driver will set
  NIC MAC to a predefined one.

  And some Dell devices have already one built-in r8152 NIC port. On
  these devices, when a second r8152 NIC is plugged in, a Debian
  originated udev rules file 73-usb-net-by-mac.rules[3] will invoke udev
  built-in command `net_id` to give a persistent name, and that will be
  based on MAC address. However, since the system has already
  initialized the built-in r8152 NIC with that name, renaming the second
  interface with this name will always fail.

  While Debian still carries a patch called "Revert-udev-network-device-
  renaming-immediately-give.patch"[4] that tries to keep support of
  already deprecated "75-persistent-net-generator.rules" based interface
  renaming mechanism, this patch also propagated into Ubuntu[5]. This
  patch will retry renaming with a 90 seconds timeout when the error
  code is -EEXIST, so the uevent processing will always be blocked in
  the last ifrename step in the victim system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: udev 237-3ubuntu10.24 [modified: lib/udev/rules.d/50-firmware.rules 
lib/udev/rules.d/50-udev-default.rules 
lib/udev/rules.d/73-special-net-names.rules 
lib/udev/rules.d/73-usb-net-by-mac.rules]
  ProcVersionSignature: Ubuntu 4.15.0-1043.48-oem 4.15.18
  Uname: Linux 4.15.0-1043-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.core.rules 95-oem-hotkey-osd.rules
  Date: Wed Jul 24 15:30:59 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-jorah+X90
  InstallationDate: Installed on 2019-07-03 (20 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 7424 Rugged Extreme
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1043-oem.efi.signed 
root=UUID=5da90c85-3500-49a2-b989-71a604f9eec4 ro mem_sleep_default=deep quiet 
splash systemd.log_level=debug udev.log-priority=debug log_buf_len=8M 
vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0Y7FK3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd05/27/2019:svnDellInc.:pnLatitude7424RuggedExtreme:pvr:rvnDellInc.:rn0Y7FK3:rvrX03:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7424 Rugged Extreme
  dmi.sys.vendor: Dell Inc.

  [1]: 
https://www.dell.com/support/article/tw/zh/twdhs1/sln301147/what-is-mac-address-pass-through?lang=en
  [2]: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/usb/r8152.c
  [3]: 
https://salsa.debian.org/systemd-team/systemd/blob/master/debian/extra/rules/73-usb-net-by-mac.rules
  [4]: 
https://salsa.debian.org/systemd-team/systemd/blob/master/debian/patches/debian/Revert-udev-network-device-renaming-immediately-give.patch
  [5]: 
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/tree/debian/patches/debian/Revert-udev-network-device-renaming-immediately-give.patch?h=ubuntu-bionic

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

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


[Touch-packages] [Bug 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)

2019-07-23 Thread Anthony Wong
** Tags added: originate-from-1837165 somerville

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1786574] Re: remove i2c-i801 from blacklist

2019-04-15 Thread Anthony Wong
@fenris
Adding back i2c_i801 to blacklist can make the touchpad work again? Is this 
what you mean?

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

Title:
  remove i2c-i801 from blacklist

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  New
Status in kmod package in Ubuntu:
  Fix Released
Status in kmod source package in Xenial:
  In Progress
Status in kmod source package in Bionic:
  In Progress
Status in kmod source package in Cosmic:
  In Progress

Bug description:
  SRU justification
  

  [Impact]
  Many modern notebooks need i2c-i801 kernel module to function, but it is 
blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user 
experience.

  [Test case]
  1. Install Ubuntu
  2. Check touchpad works or not
  3. Install the fixed kmod package
  4. Confirm touchpad works

  [Regression Potential]
  i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq 
nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a 
way to workaround the suspend issue, the proper fix should be in linux kernel. 
Since nc6000 was a machine sold in 2004, it is too difficult to find someone to 
verify if it will regress due to this SRU. The rationale to blacklist it is: 
https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, 
however it is no longer valid nowadays on modern computers.

  Besides, there look like to be a quirk in linux kernel that fixes it:
  https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434

  [Other Info]
  rationale of i2c_i801 driver blacklist: 
https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329

  
---
  Original bug report:

  We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module
  to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu.
  To use the touchpad, users have to remove the i2c-i801 line manually.

  i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000
  (Bug #16602), this module should be removed from blacklist.

  There is also another bug (Bug #1475945) that needs this module for
  Acer trackpad to work.

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

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


[Touch-packages] [Bug 1802689] Re: Upgrade to kmod (25-1ubuntu1.1) causes Lenovo x240 laptop to hang on boot

2019-02-28 Thread Anthony Wong
** No longer affects: linux (Ubuntu)

** No longer affects: linux (Ubuntu Xenial)

** No longer affects: linux (Ubuntu Bionic)

** No longer affects: linux (Ubuntu Cosmic)

** Description changed:

  After upgrading my Lenovo x240 laptop to kmod (25-1ubuntu1.1), it hangs
  on boot.
  
  After blacklisting i2c_i801 everything works great again.
  
  I realize that this was a fix for bug 1786574, and that helps some other
  folks out.  I'm not sure what the right fix is but there's got to be
  something that works for everyone.
+ 
+ ==
+ 
+ The fix for the root cause of the hang is tracked in bug 1804604.

** Description changed:

  After upgrading my Lenovo x240 laptop to kmod (25-1ubuntu1.1), it hangs
  on boot.
  
  After blacklisting i2c_i801 everything works great again.
  
  I realize that this was a fix for bug 1786574, and that helps some other
  folks out.  I'm not sure what the right fix is but there's got to be
  something that works for everyone.
  
  ==
  
- The fix for the root cause of the hang is tracked in bug 1804604.
+ The fix for the root cause of this hang issue is tracked in bug 1804604.

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

Title:
  Upgrade to kmod (25-1ubuntu1.1) causes Lenovo x240 laptop to hang on
  boot

Status in kmod package in Ubuntu:
  Fix Released
Status in kmod source package in Xenial:
  Fix Released
Status in kmod source package in Bionic:
  Fix Released
Status in kmod source package in Cosmic:
  Fix Released

Bug description:
  After upgrading my Lenovo x240 laptop to kmod (25-1ubuntu1.1), it
  hangs on boot.

  After blacklisting i2c_i801 everything works great again.

  I realize that this was a fix for bug 1786574, and that helps some
  other folks out.  I'm not sure what the right fix is but there's got
  to be something that works for everyone.

  ==

  The fix for the root cause of this hang issue is tracked in bug
  1804604.

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

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


[Touch-packages] [Bug 1786574] Re: remove i2c-i801 from blacklist

2019-02-28 Thread Anthony Wong
Confirmed with three users who had regressions (bug 1802689 and bug
1802135) through email, and confirmed that our latest kernels no longer
manifest the regressions even after i2c_i801 has been removed from
blacklist.

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

Title:
  remove i2c-i801 from blacklist

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  New
Status in kmod package in Ubuntu:
  In Progress
Status in kmod source package in Xenial:
  In Progress
Status in kmod source package in Bionic:
  In Progress
Status in kmod source package in Cosmic:
  In Progress

Bug description:
  SRU justification
  

  [Impact]
  Many modern notebooks need i2c-i801 kernel module to function, but it is 
blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user 
experience.

  [Test case]
  1. Install Ubuntu
  2. Check touchpad works or not
  3. Install the fixed kmod package
  4. Confirm touchpad works

  [Regression Potential]
  i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq 
nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a 
way to workaround the suspend issue, the proper fix should be in linux kernel. 
Since nc6000 was a machine sold in 2004, it is too difficult to find someone to 
verify if it will regress due to this SRU. The rationale to blacklist it is: 
https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, 
however it is no longer valid nowadays on modern computers.

  Besides, there look like to be a quirk in linux kernel that fixes it:
  https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434

  [Other Info]
  rationale of i2c_i801 driver blacklist: 
https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329

  
---
  Original bug report:

  We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module
  to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu.
  To use the touchpad, users have to remove the i2c-i801 line manually.

  i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000
  (Bug #16602), this module should be removed from blacklist.

  There is also another bug (Bug #1475945) that needs this module for
  Acer trackpad to work.

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

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


[Touch-packages] [Bug 1802689] Re: Upgrade to kmod (25-1ubuntu1.1) causes Lenovo x240 laptop to hang on boot

2019-02-28 Thread Anthony Wong
I have confirmed with Adam Jacobs on email that he runs latest 18.10
kernel, and his system no longer hangs after i2c_i801 is removed from
blacklist.

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

Title:
  Upgrade to kmod (25-1ubuntu1.1) causes Lenovo x240 laptop to hang on
  boot

Status in kmod package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in kmod source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Incomplete
Status in kmod source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Incomplete
Status in kmod source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Incomplete

Bug description:
  After upgrading my Lenovo x240 laptop to kmod (25-1ubuntu1.1), it
  hangs on boot.

  After blacklisting i2c_i801 everything works great again.

  I realize that this was a fix for bug 1786574, and that helps some
  other folks out.  I'm not sure what the right fix is but there's got
  to be something that works for everyone.

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

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


[Touch-packages] [Bug 1802135] Re: broken touchpad after i2c-i801 blacklist change

2019-02-28 Thread Anthony Wong
I have confirmed with both Chad billman (cabillman) and Earle Lyons
(earlev4) through email that when running 4.15.0-45 and i2c_i801 removed
from blacklist, their touchpads still work.

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

Title:
  broken touchpad after i2c-i801 blacklist change

Status in kmod package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in kmod source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in kmod source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in kmod source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  SRU:
  

  [Impact]
  ThinkPad 11e 2nd/3rd touchpad not working when load i2c-i801.
  PNP LEN0049 will use smbus by default in kernel, but i2c bus is in
  runtime suspend mode in old touchpad fw.
  Then touchpad will not work.
  LEN2040 on 11e 3rd can reproduce this issue by passing
  psmouse.synaptics_intertouch=1

  These 2 pnp device should be the same one Synaptics s3203_ver5.

  [Fix]
  i2c-i801 should auto suspend when not used, no need runtime pm.

  [Test Case]
  Tested on Thinkpad 11e 3rd.
  Touchpad works fine.

  [Regression Potential]
  Low, upstream fix cherry-picked.

  4.18 kernel patch, no need for cosmic.

  
  Original bug report:
  =
  After upgrading to kmod (24-1ubuntu3.1) the trackpads stop working on Lenovo 
11e 2nd gen machines.

  We have a fleet of approximetly 1000 of them in production running
  ubuntu 18.04. Prior to this update the trackpads worked out of box in
  18.04.

  We are currently working around the issue by deploying our own
  blacklist files.

  Here is a link to the SRU justification: https://bugs.launchpad.net
  /hwe-next/+bug/1786574

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

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


[Touch-packages] [Bug 1806532] Re: The line-out on the Dell Dock station can't work

2019-02-28 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  The line-out on the Dell Dock station can't work

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

Bug description:
  [Impact]
  On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback
  devices, one is headphone, the other is line-out, but there is no UCM for
  these docks yet, so the pluseaudio only can handle the 1st playback device,
  need us to add the UCM for them, before adding UCM, we need to set the
  longname of the sound card in the linux kernel.

  [Fix]
  For Linux kernel: Cherry-picked 3 upstream patches, these patches add the 
longname of the sound card for the dock station.

  For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will
  add ucm configuration files for Dell WD15&19, and change the SPDIF conf
  in the USB-AUDIO.conf.

  [Test Case]
  Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from
  UI, and play sound via these devices

  [Regression Potential]
  Very low, these patches come from upstream, and the change is only specific
  to WD15 and WD19 dock station.

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

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


[Touch-packages] [Bug 1786574] Re: remove i2c-i801 from blacklist

2019-02-27 Thread Anthony Wong
** Changed in: hwe-next
   Status: Fix Released => In Progress

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

Title:
  remove i2c-i801 from blacklist

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  New
Status in kmod package in Ubuntu:
  In Progress
Status in kmod source package in Xenial:
  In Progress
Status in kmod source package in Bionic:
  In Progress
Status in kmod source package in Cosmic:
  In Progress

Bug description:
  SRU justification
  

  [Impact]
  Many modern notebooks need i2c-i801 kernel module to function, but it is 
blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user 
experience.

  [Test case]
  1. Install Ubuntu
  2. Check touchpad works or not
  3. Install the fixed kmod package
  4. Confirm touchpad works

  [Regression Potential]
  i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq 
nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a 
way to workaround the suspend issue, the proper fix should be in linux kernel. 
Since nc6000 was a machine sold in 2004, it is too difficult to find someone to 
verify if it will regress due to this SRU. The rationale to blacklist it is: 
https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, 
however it is no longer valid nowadays on modern computers.

  Besides, there look like to be a quirk in linux kernel that fixes it:
  https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434

  [Other Info]
  rationale of i2c_i801 driver blacklist: 
https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329

  
---
  Original bug report:

  We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module
  to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu.
  To use the touchpad, users have to remove the i2c-i801 line manually.

  i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000
  (Bug #16602), this module should be removed from blacklist.

  There is also another bug (Bug #1475945) that needs this module for
  Acer trackpad to work.

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

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


[Touch-packages] [Bug 1802135] Re: broken touchpad after i2c-i801 blacklist change

2019-02-27 Thread Anthony Wong
linux/Cosmic  should be Fix Released as the fix is already in 4.18 from
upstream.

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => Fix Released

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

Title:
  broken touchpad after i2c-i801 blacklist change

Status in kmod package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in kmod source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in kmod source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in kmod source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  SRU:
  

  [Impact]
  ThinkPad 11e 2nd/3rd touchpad not working when load i2c-i801.
  PNP LEN0049 will use smbus by default in kernel, but i2c bus is in
  runtime suspend mode in old touchpad fw.
  Then touchpad will not work.
  LEN2040 on 11e 3rd can reproduce this issue by passing
  psmouse.synaptics_intertouch=1

  These 2 pnp device should be the same one Synaptics s3203_ver5.

  [Fix]
  i2c-i801 should auto suspend when not used, no need runtime pm.

  [Test Case]
  Tested on Thinkpad 11e 3rd.
  Touchpad works fine.

  [Regression Potential]
  Low, upstream fix cherry-picked.

  4.18 kernel patch, no need for cosmic.

  
  Original bug report:
  =
  After upgrading to kmod (24-1ubuntu3.1) the trackpads stop working on Lenovo 
11e 2nd gen machines.

  We have a fleet of approximetly 1000 of them in production running
  ubuntu 18.04. Prior to this update the trackpads worked out of box in
  18.04.

  We are currently working around the issue by deploying our own
  blacklist files.

  Here is a link to the SRU justification: https://bugs.launchpad.net
  /hwe-next/+bug/1786574

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

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


[Touch-packages] [Bug 1786574] Re: remove i2c-i801 from blacklist

2019-02-27 Thread Anthony Wong
@midnightflash
Please provide more details on the issues you see so that we can help you. As 
Aaron said, please upload the dmesg from both your X11e and X250.

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

Title:
  remove i2c-i801 from blacklist

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  New
Status in kmod package in Ubuntu:
  In Progress
Status in kmod source package in Xenial:
  In Progress
Status in kmod source package in Bionic:
  In Progress
Status in kmod source package in Cosmic:
  In Progress

Bug description:
  SRU justification
  

  [Impact]
  Many modern notebooks need i2c-i801 kernel module to function, but it is 
blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user 
experience.

  [Test case]
  1. Install Ubuntu
  2. Check touchpad works or not
  3. Install the fixed kmod package
  4. Confirm touchpad works

  [Regression Potential]
  i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq 
nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a 
way to workaround the suspend issue, the proper fix should be in linux kernel. 
Since nc6000 was a machine sold in 2004, it is too difficult to find someone to 
verify if it will regress due to this SRU. The rationale to blacklist it is: 
https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, 
however it is no longer valid nowadays on modern computers.

  Besides, there look like to be a quirk in linux kernel that fixes it:
  https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434

  [Other Info]
  rationale of i2c_i801 driver blacklist: 
https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329

  
---
  Original bug report:

  We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module
  to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu.
  To use the touchpad, users have to remove the i2c-i801 line manually.

  i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000
  (Bug #16602), this module should be removed from blacklist.

  There is also another bug (Bug #1475945) that needs this module for
  Acer trackpad to work.

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

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


[Touch-packages] [Bug 1802135] Re: broken touchpad after i2c-i801 blacklist change

2019-02-27 Thread Anthony Wong
Change linux to Fix Released for the same reason.

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

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

Title:
  broken touchpad after i2c-i801 blacklist change

Status in kmod package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in kmod source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in kmod source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in kmod source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  SRU:
  

  [Impact]
  ThinkPad 11e 2nd/3rd touchpad not working when load i2c-i801.
  PNP LEN0049 will use smbus by default in kernel, but i2c bus is in
  runtime suspend mode in old touchpad fw.
  Then touchpad will not work.
  LEN2040 on 11e 3rd can reproduce this issue by passing
  psmouse.synaptics_intertouch=1

  These 2 pnp device should be the same one Synaptics s3203_ver5.

  [Fix]
  i2c-i801 should auto suspend when not used, no need runtime pm.

  [Test Case]
  Tested on Thinkpad 11e 3rd.
  Touchpad works fine.

  [Regression Potential]
  Low, upstream fix cherry-picked.

  4.18 kernel patch, no need for cosmic.

  
  Original bug report:
  =
  After upgrading to kmod (24-1ubuntu3.1) the trackpads stop working on Lenovo 
11e 2nd gen machines.

  We have a fleet of approximetly 1000 of them in production running
  ubuntu 18.04. Prior to this update the trackpads worked out of box in
  18.04.

  We are currently working around the issue by deploying our own
  blacklist files.

  Here is a link to the SRU justification: https://bugs.launchpad.net
  /hwe-next/+bug/1786574

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

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


[Touch-packages] [Bug 1802135] Re: broken touchpad after i2c-i801 blacklist change

2018-11-28 Thread Anthony Wong
** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

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

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

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

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

Title:
  broken touchpad after i2c-i801 blacklist change

Status in kmod package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in kmod source package in Xenial:
  Fix Committed
Status in linux source package in Xenial:
  Confirmed
Status in kmod source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Confirmed
Status in kmod source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  SRU:
  

  [Impact]
  ThinkPad 11e 2nd/3rd touchpad not working when load i2c-i801.
  PNP LEN0049 will use smbus by default in kernel, but i2c bus is in
  runtime suspend mode in old touchpad fw.
  Then touchpad will not work.
  LEN2040 on 11e 3rd can reproduce this issue by passing
  psmouse.synaptics_intertouch=1

  These 2 pnp device should be the same one Synaptics s3203_ver5.

  [Fix]
  i2c-i801 should auto suspend when not used, no need runtime pm.

  [Test Case]
  Tested on Thinkpad 11e 3rd.
  Touchpad works fine.

  [Regression Potential]
  Low, upstream fix cherry-picked.

  4.18 kernel patch, no need for cosmic.

  
  Original bug report:
  =
  After upgrading to kmod (24-1ubuntu3.1) the trackpads stop working on Lenovo 
11e 2nd gen machines.

  We have a fleet of approximetly 1000 of them in production running
  ubuntu 18.04. Prior to this update the trackpads worked out of box in
  18.04.

  We are currently working around the issue by deploying our own
  blacklist files.

  Here is a link to the SRU justification: https://bugs.launchpad.net
  /hwe-next/+bug/1786574

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

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


[Touch-packages] [Bug 1802135] Re: broken touchpad after i2c-i801 blacklist change

2018-11-12 Thread Anthony Wong
Opened "linux" task for investigating the real root cause of this
regression.

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

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

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

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

Title:
  broken touchpad after i2c-i801 blacklist change

Status in kmod package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in kmod source package in Xenial:
  Fix Committed
Status in linux source package in Xenial:
  Incomplete
Status in kmod source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Incomplete
Status in kmod source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Incomplete

Bug description:
  After upgrading to kmod (24-1ubuntu3.1) the trackpads stop working on
  Lenovo 11e 2nd gen machines.

  We have a fleet of approximetly 1000 of them in production running
  ubuntu 18.04. Prior to this update the trackpads worked out of box in
  18.04.

  We are currently working around the issue by deploying our own
  blacklist files.

  Here is a link to the SRU justification: https://bugs.launchpad.net
  /hwe-next/+bug/1786574

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

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


[Touch-packages] [Bug 1802689] Re: Upgrade to kmod (25-1ubuntu1.1) causes Lenovo x240 laptop to hang on boot

2018-11-12 Thread Anthony Wong
I am opening a "linux" task for investigating the real root cause of
this in kernel.

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

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

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

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

Title:
  Upgrade to kmod (25-1ubuntu1.1) causes Lenovo x240 laptop to hang on
  boot

Status in kmod package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in kmod source package in Xenial:
  Fix Committed
Status in linux source package in Xenial:
  Incomplete
Status in kmod source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Incomplete
Status in kmod source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Incomplete

Bug description:
  After upgrading my Lenovo x240 laptop to kmod (25-1ubuntu1.1), it
  hangs on boot.

  After blacklisting i2c_i801 everything works great again.

  I realize that this was a fix for bug 1786574, and that helps some
  other folks out.  I'm not sure what the right fix is but there's got
  to be something that works for everyone.

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

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


[Touch-packages] [Bug 1802135] Re: broken touchpad after i2c-i801 blacklist change

2018-11-10 Thread Anthony Wong
** Changed in: kmod (Ubuntu)
 Assignee: (unassigned) => AaronMa (mapengyu)

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

Title:
  broken touchpad after i2c-i801 blacklist change

Status in kmod package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to kmod (24-1ubuntu3.1) the trackpads stop working on
  Lenovo 11e 2nd gen machines.

  We have a fleet of approximetly 1000 of them in production running
  ubuntu 18.04. Prior to this update the trackpads worked out of box in
  18.04.

  We are currently working around the issue by deploying our own
  blacklist files.

  Here is a link to the SRU justification: https://bugs.launchpad.net
  /hwe-next/+bug/1786574

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

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


[Touch-packages] [Bug 1802689] Re: Upgrade to kmod (25-1ubuntu1.1) causes Lenovo x240 laptop to hang on boot

2018-11-10 Thread Anthony Wong
** Changed in: kmod (Ubuntu)
 Assignee: (unassigned) => AaronMa (mapengyu)

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

Title:
  Upgrade to kmod (25-1ubuntu1.1) causes Lenovo x240 laptop to hang on
  boot

Status in kmod package in Ubuntu:
  New

Bug description:
  After upgrading my Lenovo x240 laptop to kmod (25-1ubuntu1.1), it
  hangs on boot.

  After blacklisting i2c_i801 everything works great again.

  I realize that this was a fix for bug 1786574, and that helps some
  other folks out.  I'm not sure what the right fix is but there's got
  to be something that works for everyone.

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

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


[Touch-packages] [Bug 1786574] Re: remove i2c-i801 from blacklist

2018-11-05 Thread Anthony Wong
** Changed in: hwe-next
   Status: Fix Committed => Fix Released

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

Title:
  remove i2c-i801 from blacklist

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  New
Status in kmod package in Ubuntu:
  Fix Committed
Status in kmod source package in Xenial:
  Fix Released
Status in kmod source package in Bionic:
  Fix Released
Status in kmod source package in Cosmic:
  Fix Released

Bug description:
  SRU justification
  

  [Impact]
  Many modern notebooks need i2c-i801 kernel module to function, but it is 
blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user 
experience.

  [Test case]
  1. Install Ubuntu
  2. Check touchpad works or not
  3. Install the fixed kmod package
  4. Confirm touchpad works

  [Regression Potential]
  i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq 
nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a 
way to workaround the suspend issue, the proper fix should be in linux kernel. 
Since nc6000 was a machine sold in 2004, it is too difficult to find someone to 
verify if it will regress due to this SRU. The rationale to blacklist it is: 
https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, 
however it is no longer valid nowadays on modern computers.

  Besides, there look like to be a quirk in linux kernel that fixes it:
  https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434

  [Other Info]
  rationale of i2c_i801 driver blacklist: 
https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329

  
---
  Original bug report:

  We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module
  to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu.
  To use the touchpad, users have to remove the i2c-i801 line manually.

  i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000
  (Bug #16602), this module should be removed from blacklist.

  There is also another bug (Bug #1475945) that needs this module for
  Acer trackpad to work.

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

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


[Touch-packages] [Bug 1786574] Re: remove i2c-i801 from blacklist

2018-10-03 Thread Anthony Wong
On Wed, 19 Sep 2018 at 22:01,  Christian Ehrhardt  <
1786...@bugs.launchpad.net> wrote:

> Hi,
> first of all this package seems to have quite some issues in the merges
> that are done - it doesn't list all remaining changes and the i2c blacklist
> is one of them.
> It comes from like back in 2005 and I agree, it might or is safe to be
> removed.
>
> Thanks to Stefan Bader for cleaning this up, as the MP linked here has
> e.g. on changelog entries.
> I'd ack to his branch at [1] for Cosmic, is it would be an MP to ack on.
>

Thanks!


>
> But for the actual sponsoring, as I never really touched kmod before I'd
> be happy if you'd ask one of the foundations Team that is here this week
> that touched it recently as they might have extra considerations. OTOH
> the change really looks right for cosmic IMHO, so if no one responds get
> back to me.
>
> SRUs of this are quite a different topic for the following reasons:
> - if the issues still exists, it might regress somebody due to the SRU
> then.
> - If you can prove that the old issue really does no more exist with e.g.
> the oldest kernel in Bionic, then it might be done. But you'd have to
> outline that in detail when completing the SRU template for this bug [2]
> Without the prove I'd be concerned and as a SRU member would reject it, so
> really make sure you
> get this documented right.
>

I have added the SRU justification, hope that helps.


** Description changed:

+ SRU justification
+ 
+ 
+ [Impact]
+ Many modern notebooks need i2c-i801 kernel module to function, but it is 
blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user 
experience.
+ 
+ [Test case]
+ 1. Install Ubuntu
+ 2. Check touchpad works or not
+ 3. Install the fixed kmod package
+ 4. Confirm touchpad works
+ 
+ [Regression Potential]
+ i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq 
nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a 
way to workaround the suspend issue, the proper fix should be in linux kernel. 
Since nc6000 was a machine sold in 2004, it is too difficult to find someone to 
verify if it will regress due to this SRU. The rationale to blacklist it is: 
https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, 
however it is no longer valid nowadays on modern computers.
+ 
+ Besides, there look like to be a quirk in linux kernel that fixes it:
+ https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434
+ 
+ [Other Info]
+ rationale of i2c_i801 driver blacklist: 
https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329
+ 
+ 
---
+ Original bug report:
+ 
  We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module
  to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu. To
  use the touchpad, users have to remove the i2c-i801 line manually.
  
  i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000
  (Bug #16602), this module should be removed from blacklist.
  
  There is also another bug (Bug #1475945) that needs this module for Acer
  trackpad to work.

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

Title:
  remove i2c-i801 from blacklist

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in kmod package in Ubuntu:
  Confirmed
Status in kmod source package in Xenial:
  Confirmed
Status in kmod source package in Bionic:
  Confirmed
Status in kmod source package in Cosmic:
  Confirmed

Bug description:
  SRU justification
  

  [Impact]
  Many modern notebooks need i2c-i801 kernel module to function, but it is 
blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user 
experience.

  [Test case]
  1. Install Ubuntu
  2. Check touchpad works or not
  3. Install the fixed kmod package
  4. Confirm touchpad works

  [Regression Potential]
  i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq 
nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a 
way to workaround the suspend issue, the proper fix should be in linux kernel. 
Since nc6000 was a machine sold in 2004, it is too difficult to find someone to 
verify if it will regress due to this SRU. The rationale to blacklist it is: 
https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, 
however it is no longer valid nowadays on modern computers.

  Besides, there look like to be a quirk in linux kernel that fixes it:
  https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434

  [Other Info]
  rationale of i2c_i801 driver blacklist: 
https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329

  
---
  

[Touch-packages] [Bug 1768830] Re: the audio can't work on Lenovo machines with dual analogue codecs under ubuntu 18.04

2018-08-29 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  the audio can't work on Lenovo machines with dual analogue codecs
  under ubuntu 18.04

Status in HWE Next:
  Fix Released
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Bionic:
  Fix Released

Bug description:
  Steps:
  1. Install the ubuntu 18.04 on the machine of Lenovo P520.
  2. Login system.
  3. Plug in an external headset to record and playback in front and rear panel.

  Expected result:
  Output and input audio should work in front and rear panel.

  Actual result:
  Front panel audio doesn't work at all.
  Just output audio working, input audio does't work in rear panel.

  SRU Document:

  [Impact]

  We have several Lenovo machines like Lenovo P520 which have 2 analogue
  audio codecs on them, the internal speaker and front headset are
  connected to the 1st codec, the Rear mic, Line in and Line out are
  connected to the 2nd codec. So far, under ubuntu 18.04 with the alsa-
  lib/libasound2 v1.1.3-5, only the audio devices (internal speaker and
  front headset) on the 1st codec can work. To make all audio devices
  work on this machine, upstream provided 3 patches for kernel audio
  driver and 5 patches for alsa-lib. The kernel patches are already in
  the linux-4.12, so this is not a problem anymore under 18.04 since we
  use linux-4.15 in 18.04. For the 5 patches of alsa-lib, we need to
  backport them to v1.1.3-5, the 5 patches are list as below:

  2b9b3f01 ucm: Assure the user input card name not to exceed max size of card 
long name (it is in the alsa-lib v1.1.4)
  4b9297e6 ucm: Load device-specific configuration file based on the card long 
name (it is in the alsa-lib v1.1.4)
  b7e56af8 conf/ucm: Add dual HD-audio codecs config for Lenovo (it is in the 
alsa-lib v1.1.6)
  181f8e25 ucm: adding the folder of card_long_name when finding verb conf file 
(it is in the alsa-lib v1.1.6+)
  81db276f conf/ucm: increase the input volume for LineIn (it is in the 
alsa-lib v1.1.6+)

  Some explanation for these 5 patches, to make the audio work, the
  alsa-lib needs to add an audio configuration file and verb conf file
  for lenovo machines with dual codecs, these two files are put in a
  folder named by card_long_name, and the name of configuration file
  itself is also named by card_long_name, this is implemented by the
  patches of NO. 3rd and 5th.

  But the alsa-lib v1.1.3-5 itself doesn't support to search conf file with 
card_long_name, it only support searching with card_name, So we need to 
backport 3 patches to let alsa-lib v1.1.3-5 support to search with 
card_long_name, these 3 patches are No. 1st, 2nd and 4th.
   
  [Test Case]

  On the Lenovo machines with dual codecs (p520), I insatlled the
  libasound2 v1.1.3-5ubuntu1 and libasound2-data v1.1.3-5ubuntu1, the
  alsa-lib can find the conf file and can parse the conf file
  successfully, and I tested the internal speaker, front headset, rear
  mic, line out and line in, all audio devices work well.

  On a HP and Dell machines without dual codecs, I insatlled the
  libasound2 v1.1.3-5ubuntu1 and libasound2-data v1.1.3-5ubuntu1, the
  alsa-lib can't find conf file by card_long_name and card_name, the
  pulseaudio will drive the sound card as before, so all audio functions
  worked well as before.

  [Regression Potential]

  After adding these 5 patches, there 2 two changes introduced into the
  alsa-lib v1.1.3-5ubuntu1:

  1) before: only have folder and conf files named by card_name; after: has one 
folder and conf file named by card_long_name, this folder and conf file will 
not affect others,
  2) before: the ucm parser will search the conf file/folder by card_name only; 
 after: the ucm parser will search the conf file/foler by card_long_name first, 
if it fails, it will fallback to use card_name to search again. So this change 
is compatible with old version.

  There is no regression since there is only one folder named by
  card_long_name in v1.1.3-5ubuntu1, if it runs on lenovo machine with
  dual codecs, it will find the conf file by card_long_name, if it runs
  on other machines, the search by card_long_name will definitely fail
  and fall back to search by card_name, then it will be same as before.
  So the objective of these 5 patches is to let lenovo machines with
  dual codecs find the conf file by card_long_name, let other machines
  fail to search by card_long_name, then fallback to original searching
  method - search by card_name.

  [Other Info]

  Since I could not find the alsa-lib repository in canonical, I just
  generated the debdiff with "apt-get source ...".

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

-- 
Mailing list: 

[Touch-packages] [Bug 1750947] Re: pulseaudio print lots of error when selecting unavailable profile

2018-08-29 Thread 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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1786574] Re: remove i2c-i801 from blacklist

2018-08-28 Thread Anthony Wong
Yes, probably, I actually have pinged apw about this bug, so shouldn't
hurt to add him as reviewer. I may also try to find someone to upload a
package later.

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

Title:
  remove i2c-i801 from blacklist

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in kmod package in Ubuntu:
  Confirmed
Status in kmod source package in Xenial:
  Confirmed
Status in kmod source package in Bionic:
  Confirmed
Status in kmod source package in Cosmic:
  Confirmed

Bug description:
  We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module
  to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu.
  To use the touchpad, users have to remove the i2c-i801 line manually.

  i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000
  (Bug #16602), this module should be removed from blacklist.

  There is also another bug (Bug #1475945) that needs this module for
  Acer trackpad to work.

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

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


[Touch-packages] [Bug 1786574] Re: remove i2c-i801 from blacklist

2018-08-26 Thread Anthony Wong
** Also affects: oem-priority
   Importance: Undecided
   Status: New

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

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

Title:
  remove i2c-i801 from blacklist

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in kmod package in Ubuntu:
  New
Status in kmod source package in Xenial:
  New
Status in kmod source package in Bionic:
  New
Status in kmod source package in Cosmic:
  New

Bug description:
  We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module
  to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu.
  To use the touchpad, users have to remove the i2c-i801 line manually.

  i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000
  (Bug #16602), this module should be removed from blacklist.

  There is also another bug (Bug #1475945) that needs this module for
  Acer trackpad to work.

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

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


[Touch-packages] [Bug 1786574] Re: remove i2c-i801 from blacklist

2018-08-21 Thread Anthony Wong
Is there anything I should do to move this bug forward? Thanks.

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

Title:
  remove i2c-i801 from blacklist

Status in HWE Next:
  New
Status in kmod package in Ubuntu:
  New
Status in kmod source package in Xenial:
  New
Status in kmod source package in Bionic:
  New
Status in kmod source package in Cosmic:
  New

Bug description:
  We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module
  to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu.
  To use the touchpad, users have to remove the i2c-i801 line manually.

  i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000
  (Bug #16602), this module should be removed from blacklist.

  There is also another bug (Bug #1475945) that needs this module for
  Acer trackpad to work.

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

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


[Touch-packages] [Bug 1786574] Re: remove i2c-i801 from blacklist

2018-08-15 Thread Anthony Wong
** Changed in: kmod (Ubuntu Cosmic)
   Importance: Critical => High

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

Title:
  remove i2c-i801 from blacklist

Status in HWE Next:
  New
Status in kmod package in Ubuntu:
  New
Status in kmod source package in Xenial:
  New
Status in kmod source package in Bionic:
  New
Status in kmod source package in Cosmic:
  New

Bug description:
  We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module
  to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu.
  To use the touchpad, users have to remove the i2c-i801 line manually.

  i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000
  (Bug #16602), this module should be removed from blacklist.

  There is also another bug (Bug #1475945) that needs this module for
  Acer trackpad to work.

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

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


[Touch-packages] [Bug 1786574] Re: remove i2c-i801 from blacklist

2018-08-13 Thread Anthony Wong
** Tags added: 1786573 sutton

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

Title:
  remove i2c-i801 from blacklist

Status in HWE Next:
  New
Status in kmod package in Ubuntu:
  New

Bug description:
  We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module
  to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu.
  To use the touchpad, users have to remove the i2c-i801 line manually.

  i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000
  (Bug #16602), this module should be removed from blacklist.

  There is also another bug (Bug #1475945) that needs this module for
  Acer trackpad to work.

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

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


[Touch-packages] [Bug 1786574] Re: remove i2c-i801 from blacklist

2018-08-13 Thread Anthony Wong
** Description changed:

- Touchpad of Yoda2 doesn't work well via PS/2 mode, most time the data is
- lost sync via PS/2.
+ We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module
+ to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu. To
+ use the touchpad, users have to remove the i2c-i801 line manually.
  
- I have made a patch in upstream/Ubuntu 4.15/4.13 kernels to force
- touchpad using SMBus mode.
- SMBus mode requires i2c-i801 kernel module which is in modprobe
- blacklist in Ubuntu 18.04/16.04. User has to remove i2c-i801 manually.
+ i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000
+ (Bug #16602), this module should be removed from blacklist.
  
- i2c-i801 in blacklist is a very old workaround to fix HP compaq nc6000
- (Bug #16602), this module should be removed from blacklist.
+ There is also another bug (Bug #1475945) that needs this module for Acer
+ trackpad to work.

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

Title:
  remove i2c-i801 from blacklist

Status in HWE Next:
  New
Status in kmod package in Ubuntu:
  New

Bug description:
  We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module
  to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu.
  To use the touchpad, users have to remove the i2c-i801 line manually.

  i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000
  (Bug #16602), this module should be removed from blacklist.

  There is also another bug (Bug #1475945) that needs this module for
  Acer trackpad to work.

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

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


[Touch-packages] [Bug 1786574] Re: remove i2c-i801 from blacklist

2018-08-13 Thread Anthony Wong
** Description changed:

  Touchpad of Yoda2 doesn't work well via PS/2 mode, most time the data is
  lost sync via PS/2.
  
  I have made a patch in upstream/Ubuntu 4.15/4.13 kernels to force
  touchpad using SMBus mode.
  SMBus mode requires i2c-i801 kernel module which is in modprobe
  blacklist in Ubuntu 18.04/16.04. User has to remove i2c-i801 manually.
  
  i2c-i801 in blacklist is a very old workaround to fix HP compaq nc6000
- (Bug #10306), this module should be removed from blacklist.
+ (Bug #16602), this module should be removed from blacklist.

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

Title:
  remove i2c-i801 from blacklist

Status in HWE Next:
  New
Status in kmod package in Ubuntu:
  New

Bug description:
  Touchpad of Yoda2 doesn't work well via PS/2 mode, most time the data is
  lost sync via PS/2.

  I have made a patch in upstream/Ubuntu 4.15/4.13 kernels to force
  touchpad using SMBus mode.
  SMBus mode requires i2c-i801 kernel module which is in modprobe
  blacklist in Ubuntu 18.04/16.04. User has to remove i2c-i801 manually.

  i2c-i801 in blacklist is a very old workaround to fix HP compaq nc6000
  (Bug #16602), this module should be removed from blacklist.

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

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


[Touch-packages] [Bug 1499665] Re: [SynPS/2 Synaptics TouchPad] TouchPad not working after installtion

2017-11-11 Thread Anthony Wong
** Changed in: hwe-next
   Status: Incomplete => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/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 

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

2017-11-11 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


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

2017-11-11 Thread Anthony Wong
** Changed in: hwe-next
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1414706] Re: [20ALCTO1WW, Realtek ALC292, Black Mic, Left][Lenovo ThinkPad X240] external mic has no sound at all

2017-11-11 Thread Anthony Wong
** Changed in: hwe-next
   Status: Incomplete => Won't Fix

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

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

Status in HWE Next:
  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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1549163] Re: Bluetooth headset HSP/HFP mode not working in Xenial

2017-03-05 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1647283] Re: WiFi being detected as ethernet when race condition on renaming for persistent name

2017-03-05 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1647283] Re: WiFi being detected as ethernet when race condition on renaming for persistent name

2016-12-14 Thread Anthony Wong
** Changed in: network-manager (Ubuntu)
 Assignee: (unassigned) => Aron Xu (happyaron)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1643812] Re: There is no entry in 'Play sound through' list when plug in headset jack [8086:9d70].

2016-12-14 Thread Anthony Wong
** Tags added: kittyhawk originate-from-1613190

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1643812] Re: There is no entry in 'Play sound through' list when plug in headset jack [8086:9d70].

2016-12-14 Thread Anthony Wong
** Changed in: pulseaudio (Ubuntu Trusty)
 Assignee: (unassigned) => Hui Wang (hui.wang)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1646537] Re: Backlight sometimes fails to resume from suspend & screen brightness sometimes will not dim below 100%

2016-12-04 Thread Anthony Wong
** Changed in: linux (Ubuntu Vivid)
 Assignee: (unassigned) => AceLan Kao (acelankao)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1639896] Re: Backport support for AMD Polaris

2016-11-10 Thread Anthony Wong
** Summary changed:

- Backport support for Polaris
+ Backport support for AMD Polaris

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1515728] Re: After receiving a call while playing music the sound volume is very low and can't be raised

2016-07-19 Thread Anthony Wong
** Changed in: pulseaudio (Ubuntu RTM)
 Assignee: (unassigned) => Hui Wang (hui.wang)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)

2016-06-20 Thread 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 Ubuntu
Touch seeded packages, which is subscribed to apparmor 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1586641] Re: PCI/internal sound card not detected

2016-06-16 Thread Anthony Wong
** Changed in: alsa-driver (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1586641] Re: PCI/internal sound card not detected

2016-06-16 Thread 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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1586641] Re: PCI/internal sound card not detected

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1586641] Re: PCI/internal sound card not detected

2016-06-15 Thread 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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)

2016-06-14 Thread 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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1589889] Re: Bluetooth search gets nothing on Dell XPS 15 9550

2016-06-09 Thread Anthony Wong
Firmware is missing:

[3.479417] bluetooth hci0: Direct firmware load for brcm/BCM-0a5c-6410.hcd 
failed with error -2
[3.479421] Bluetooth: hci0: BCM: Patch brcm/BCM-0a5c-6410.hcd not found

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

Title:
  Bluetooth search gets nothing on Dell XPS 15 9550

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Title: Bluetooth search gets nothing on Dell XPS 15 9550

  Summary:
  Bluetooth search gets nothing on Dell XPS 15 9550

  Steps:
  1. Open Bluetooth Setting
  2. Click "+" to search nearby bluetooth devices

  Expected results: BT search could get nearby BT devices

  Actual results: Nothing shows from BT search

  Additional information:
  BT device:
  Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp.
  Couldn't open device, some information will be missing
  Device Descriptor:
    bLength18
    bDescriptorType 1
    bcdUSB   2.00
    bDeviceClass  255 Vendor Specific Class
    bDeviceSubClass 1
    bDeviceProtocol 1
    bMaxPacketSize064
    idVendor   0x0a5c Broadcom Corp.
    idProduct  0x6410

  CPU: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (8x)

  GPU: 00:02.0 VGA compatible controller: Intel Corporation HD Graphics
  530 (rev 06)

  Manufacturer: Dell

  ProductName: XPS 15 9550

  BiosVersion: 01.02.00

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

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


[Touch-packages] [Bug 1586941] Re: Randomly segfault on BYT with 4.4 kernel

2016-05-30 Thread Anthony Wong
** Also affects: upstart (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Randomly segfault on BYT with 4.4 kernel

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

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

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

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

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

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

  I'll paste some images and logs after.

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

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


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

2016-05-26 Thread 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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1470080] Re: Broken icon in indicator when iphone attached

2016-05-16 Thread Anthony Wong
I am on 16.04.

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

Title:
  Broken icon in indicator when iphone attached

Status in indicator-power package in Ubuntu:
  Confirmed

Bug description:
  Running wily with an iPhone 4 (but I doubt it matters which rev of
  iphone) attached, I see a combined battery gauge for desktop and phone
  in the indicator. Unfortunately the icon is broken / missing when the
  phone is attached, like it's missing a small version of the icon you
  see in system settings -> power.

  See screenshot (next to 61%)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: indicator-power 12.10.6+15.10.20150522-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
  Uname: Linux 3.19.0-22-generic x86_64
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jun 30 12:10:40 2015
  InstallationDate: Installed on 2014-06-16 (379 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: indicator-power
  UpgradeStatus: Upgraded to wily on 2015-05-09 (51 days ago)

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

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


[Touch-packages] [Bug 1470080] Re: Broken icon in indicator when iphone attached

2016-05-16 Thread Anthony Wong
Happens to me as well with iPhone 5. Please see the screenshot. I am
surprised this bug does not have any activities, has this already been
resolved?

** Attachment added: "screenshot"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1470080/+attachment/4663762/+files/%E6%93%B7%E5%8F%96%E9%81%B8%E5%8F%96%E5%8D%80%E5%9F%9F_096.png

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

Title:
  Broken icon in indicator when iphone attached

Status in indicator-power package in Ubuntu:
  Confirmed

Bug description:
  Running wily with an iPhone 4 (but I doubt it matters which rev of
  iphone) attached, I see a combined battery gauge for desktop and phone
  in the indicator. Unfortunately the icon is broken / missing when the
  phone is attached, like it's missing a small version of the icon you
  see in system settings -> power.

  See screenshot (next to 61%)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: indicator-power 12.10.6+15.10.20150522-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
  Uname: Linux 3.19.0-22-generic x86_64
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jun 30 12:10:40 2015
  InstallationDate: Installed on 2014-06-16 (379 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: indicator-power
  UpgradeStatus: Upgraded to wily on 2015-05-09 (51 days ago)

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

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


[Touch-packages] [Bug 1578196] Re: External Display Port monitor not working

2016-05-10 Thread 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 Ubuntu
Touch seeded 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
  

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

2016-04-12 Thread 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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1569214] [NEW] [SRU] Patches needed for Telit modems used in IOT systems

2016-04-12 Thread 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
  

[Touch-packages] [Bug 1549163] Re: Bluetooth headset HSP/HFP mode not working in Xenial

2016-03-10 Thread 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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1434372] Re: [Lenovo E555] Screen of laptop will become black and never lighting after un-plug VGA cable

2016-03-03 Thread 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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net

[Touch-packages] [Bug 1409675] Re: [Dell Latitude E5450, Realtek ALC293] Microphone is being detected as headphone

2016-03-03 Thread 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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1410205] Re: [radeon] Support for AMD Radeon R2 Graphics or R5 M240

2016-03-03 Thread Anthony Wong
** Changed in: hwe-next
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


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

2016-03-03 Thread Anthony Wong
** Changed in: hwe-next
   Status: Incomplete => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1503168] Re: [Dell Inspiron 5551][8086:0f31] Unable to adjust brightness

2016-03-03 Thread Anthony Wong
** Changed in: hwe-next
   Status: Incomplete => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1499665] Re: [SynPS/2 Synaptics TouchPad] TouchPad not working after installtion

2016-03-03 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/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 

[Touch-packages] [Bug 1503168] Re: [Dell Inspiron 5551][8086:0f31] Unable to adjust brightness

2015-12-02 Thread 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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1503168] Re: [Dell Inspiron 5551][8086:0f31] Unable to adjust brightness

2015-11-13 Thread 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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


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

2015-11-13 Thread 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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1513384] Re: Missing "Front Headphone" in headset mic path

2015-11-13 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1414930] Re: [Lenovo ThinkPad 2015 models] Buttons of Synaptics trackpad doesn't work

2015-04-01 Thread Anthony Wong
** Changed in: hwe-next
 Assignee: Liming Wang (wangliming) = Timo Aaltonen (tjaalton)

** Changed in: linux (Ubuntu Trusty)
 Assignee: Liming Wang (wangliming) = Timo Aaltonen (tjaalton)

** Changed in: linux (Ubuntu Utopic)
 Assignee: (unassigned) = Timo Aaltonen (tjaalton)

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

Title:
  [Lenovo ThinkPad 2015 models] Buttons of Synaptics trackpad doesn't
  work

Status in HWE Next Project:
  In Progress
Status in The Linux Kernel:
  In Progress
Status in libinput package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Confirmed
Status in systemd source package in Trusty:
  Confirmed
Status in linux source package in Utopic:
  Confirmed
Status in systemd source package in Utopic:
  Confirmed

Bug description:
  Lenovo X1 3rd Carbon (201411-16196)

  Steps to reproduce the bug:
  1, Log in to system
  2, Click left/right/middle buttons of the touchpad

  Actual result:
  No response after clicking the buttons

  Expected results:
  Buttons work as expected behavirour

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-45-generic 3.13.0-45.74 [modified: 
boot/vmlinuz-3.13.0-45-generic]
  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:  u  1598 F pulseaudio
   /dev/snd/controlC0:  u  1598 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 27 02:48:23 2015
  HibernationDevice: RESUME=UUID=c553e9ba-b74b-43ad-8cf2-496531261e0f
  InstallationDate: Installed on 2015-01-27 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20150126)
  MachineType: LENOVO 20BTZ09ZUS
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic 
root=UUID=1d34e685-c98b-41f3-b649-87770517b194 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
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET24W (1.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BTZ09ZUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET24W(1.02):bd10/27/2014:svnLENOVO:pn20BTZ09ZUS:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTZ09ZUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BTZ09ZUS
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1414930] Re: [Lenovo ThinkPad X1 Carbon 20BT] Buttons of Synaptics trackpad doesn't work

2015-03-09 Thread Anthony Wong
** Changed in: linux (Ubuntu Trusty)
 Assignee: (unassigned) = walimis (walimis)

** Changed in: linux (Ubuntu Trusty)
 Assignee: walimis (walimis) = Liming Wang (wangliming)

** Changed in: xserver-xorg-input-synaptics (Ubuntu Trusty)
 Assignee: (unassigned) = Liming Wang (wangliming)

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

** Changed in: linux (Ubuntu Trusty)
   Status: New = Confirmed

** Changed in: xserver-xorg-input-synaptics (Ubuntu Trusty)
   Status: New = Confirmed

** Changed in: hwe-next
   Status: Confirmed = In Progress

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

Title:
  [Lenovo ThinkPad X1 Carbon 20BT] Buttons of Synaptics trackpad doesn't
  work

Status in HWE Next Project:
  In Progress
Status in The Linux Kernel:
  In Progress
Status in libinput package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in xserver-xorg-input-synaptics package in Ubuntu:
  New
Status in libinput source package in Trusty:
  New
Status in linux source package in Trusty:
  Confirmed
Status in systemd source package in Trusty:
  New
Status in xserver-xorg-input-synaptics source package in Trusty:
  Confirmed
Status in libinput source package in Utopic:
  New
Status in linux source package in Utopic:
  New
Status in systemd source package in Utopic:
  New
Status in xserver-xorg-input-synaptics source package in Utopic:
  New

Bug description:
  Lenovo X1 3rd Carbon (201411-16196)

  Steps to reproduce the bug:
  1, Log in to system
  2, Click left/right/middle buttons of the touchpad

  Actual result:
  No response after clicking the buttons

  Expected results:
  Buttons work as expected behavirour

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-45-generic 3.13.0-45.74 [modified: 
boot/vmlinuz-3.13.0-45-generic]
  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:  u  1598 F pulseaudio
   /dev/snd/controlC0:  u  1598 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 27 02:48:23 2015
  HibernationDevice: RESUME=UUID=c553e9ba-b74b-43ad-8cf2-496531261e0f
  InstallationDate: Installed on 2015-01-27 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20150126)
  MachineType: LENOVO 20BTZ09ZUS
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic 
root=UUID=1d34e685-c98b-41f3-b649-87770517b194 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
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET24W (1.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BTZ09ZUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET24W(1.02):bd10/27/2014:svnLENOVO:pn20BTZ09ZUS:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTZ09ZUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BTZ09ZUS
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1414706] Re: [20ALCTO1WW, Realtek ALC292, Black Mic, Left][Lenovo ThinkPad X240] external mic has no sound at all

2015-03-06 Thread Anthony Wong
** Changed in: hwe-next
   Status: Confirmed = Incomplete

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

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

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

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

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

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

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

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

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

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


[Touch-packages] [Bug 1414930] Re: [Lenovo ThinkPad X1 Carbon 20BT] Buttons of Synaptics trackpad doesn't work

2015-03-03 Thread Anthony Wong
** Changed in: hwe-next
   Importance: Undecided = Medium

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

Title:
  [Lenovo ThinkPad X1 Carbon 20BT] Buttons of Synaptics trackpad doesn't
  work

Status in HWE Next Project:
  Confirmed
Status in The Linux Kernel:
  In Progress
Status in libinput package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Fix Released
Status in xserver-xorg-input-synaptics package in Ubuntu:
  New
Status in libinput source package in Trusty:
  New
Status in linux source package in Trusty:
  New
Status in systemd source package in Trusty:
  New
Status in xserver-xorg-input-synaptics source package in Trusty:
  New
Status in libinput source package in Utopic:
  New
Status in linux source package in Utopic:
  New
Status in systemd source package in Utopic:
  New
Status in xserver-xorg-input-synaptics source package in Utopic:
  New

Bug description:
  Lenovo X1 3rd Carbon (201411-16196)

  Steps to reproduce the bug:
  1, Log in to system
  2, Click left/right/middle buttons of the touchpad

  Actual result:
  No response after clicking the buttons

  Expected results:
  Buttons work as expected behavirour

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-45-generic 3.13.0-45.74 [modified: 
boot/vmlinuz-3.13.0-45-generic]
  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:  u  1598 F pulseaudio
   /dev/snd/controlC0:  u  1598 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 27 02:48:23 2015
  HibernationDevice: RESUME=UUID=c553e9ba-b74b-43ad-8cf2-496531261e0f
  InstallationDate: Installed on 2015-01-27 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20150126)
  MachineType: LENOVO 20BTZ09ZUS
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic 
root=UUID=1d34e685-c98b-41f3-b649-87770517b194 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
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET24W (1.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BTZ09ZUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET24W(1.02):bd10/27/2014:svnLENOVO:pn20BTZ09ZUS:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTZ09ZUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BTZ09ZUS
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1413865] Re: No default setting for When power is critically low in Power settings

2015-03-01 Thread Anthony Wong
** Changed in: ubuntukylin
Milestone: vivid-beta1 = vivid-beta2

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

Title:
  No default setting for When power is critically low in Power
  settings

Status in Ubuntu Kylin:
  Confirmed
Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  No default setting for When power is critically low in Power
  settings.

  电源设置中”电量严重不足时“没有默认选项

  Steps:
  1. Install the latest Ubuntu kylin Vivid x64 OS
  2. Enter into System settings--Power
  3. Check the default value of When power is critically low
  --Failed. No default value for it

  Configuration:
  OS: Ubuntu Kylin vivid Daily build 20150122 x64

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

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


[Touch-packages] [Bug 1409721] Re: [HP EliteBook 725 G2 Notebook PC] mic mute key (Fn+F8) does not work

2015-02-25 Thread Anthony Wong
** Changed in: hwe-next
   Status: Fix Committed = Fix Released

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

Title:
  [HP EliteBook 725 G2 Notebook PC] mic mute key (Fn+F8) does not work

Status in HWE Next Project:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  HP EliteBook 725 G2 Notebook PC
  (CID 201405-15214)
  updated ubuntu 14.04.1
  3.13.0-43-generic #72

  Steps to reproduce this bug:
  1. install 14.04.1 and use the updater to update the system. Reboot.
  2. Get into the desktop and ready to use the system.
  3. sudo apt-get install sox
  4. apply command 'sox -t alsa default tmp.wav' to record the sound. Press Fn 
F8 at the same time.
  5. use 'ctrl+c' to stop recording. use 'play tmp.wav' to playback
  6. during the playback, press the mute fhunction key.

  Expected result:
  of step 5. : The recorded sound was muted. The LED indicate the mic was muted.
  of step 6. : The speaker was muted and the mute LED indicate it was muted.

  Actual result:
  of step 5. : nothing happened.
  of step 6 : the sound was muted but the LED did not change color.

  More information:
  sudo hda-verb /dev/snd/hwC1D0 0x18 SET_PIN_WIDGET_CONTROL 0x20
  could turn off the mic mute LED

  sudo hda-verb /dev/snd/hwC1D0 0x18 SET_PIN_WIDGET_CONTROL 0x24
  could turn on the mic mute LED

  --

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-43-generic 3.13.0-43.72
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1404 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1404 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jan 12 07:36:28 2015
  HibernationDevice: RESUME=UUID=e24b803a-e217-4d6d-a35c-dbe0c033966a
  InstallationDate: Installed on 2015-01-08 (4 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP Licrice
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic 
root=UUID=c1e0a265-8c75-4427-ad25-f0c76f003ce7 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-43-generic N/A
   linux-backports-modules-3.13.0-43-generic  N/A
   linux-firmware 1.127.11
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/03/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M84 Ver. 97.35
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 221D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 63.14
  dmi.chassis.asset.tag: 73612P10CU
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM84Ver.97.35:bd09/03/2014:svnHewlett-Packard:pnHPLicrice:pvrA3009CD10002:rvnHewlett-Packard:rn221D:rvrKBCVersion63.14:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Licrice
  dmi.product.version: A3009CD10002
  dmi.sys.vendor: Hewlett-Packard
  --- 
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1516 F pulseaudio
   /dev/snd/controlC1:  ubuntu 1516 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=9864838c-7ba0-41b5-bd85-fe728504b659
  InstallationDate: Installed on 2015-01-14 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Hewlett-Packard HP 430 G2
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic 
root=UUID=d4e5a7ff-0bd2-48a7-9d43-2defe1dcd58b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-44-generic N/A
   linux-backports-modules-3.13.0-44-generic  N/A
   linux-firmware 1.127.11
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  trusty
  Uname: Linux 3.13.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/07/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M74 Ver. 01.03
  dmi.board.name: 2246
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 67.22
  dmi.chassis.asset.tag: 73612P10CU
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  

  1   2   >