[Touch-packages] [Bug 754275] Re: Time zones map is wrong

[Dennis Loose]

I'm realizing this is a decade old issue, but this package is still
being used today. Are there any plans to continue maintaining this?

The Flutter-based Ubuntu desktop installer
https://github.com/canonical/ubuntu-desktop-provision/ uses the SVGs
from this package (via https://github.com/canonical/ubuntu-flutter-
plugins/tree/main/packages/timezone_map) for the timezone selection
page.

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

Title:
  Time zones map is wrong

Status in Indicator Date and Time:
  Fix Released
Status in Ubuntu Geonames:
  Invalid
Status in libtimezonemap package in Ubuntu:
  Confirmed

Bug description:
  The time zones map is outdated, for example my city is shown in UTC+3
  time zone though it moved to UTC+4, Kemerovo is shown in UTC+8, though
  it moved to UTC+7 and so on.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/754275/+subscriptions


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

Re: [Touch-packages] [Bug 2012008] Re: package python3-problem-report 2.20.11-0ubuntu27.24 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attemp

[Dennis Ruffer]

The problem was not solved with this suggestion.

DaR


On Fri, Mar 17, 2023 at 3:25 AM Benjamin Drung <2012...@bugs.launchpad.net>
wrote:

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better.
>
> Can you try to re-install python3-problem-report with the following
> command:
>
> sudo apt-get install --reinstall python3-problem-report
>
> If it fails, please paste the full output.
>
> ** Changed in: apport (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2012008
>
> Title:
>   package python3-problem-report 2.20.11-0ubuntu27.24 failed to
>   install/upgrade: package is in a very bad inconsistent state; you
>   should  reinstall it before attempting configuration
>
> Status in apport package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Getting an error on every boot now.
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 20.04
>   Package: python3-problem-report 2.20.11-0ubuntu27.24
>   ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74
>   Uname: Linux 5.15.0-58-generic x86_64
>   ApportLog:
>ERROR: apport (pid 2603509) Thu Mar 16 15:38:45 2023: called for pid
> 3674, signal 11, core limit 0, dump mode 1
>ERROR: apport (pid 2603509) Thu Mar 16 15:38:45 2023: executable:
> /usr/bin/nautilus (command line "/usr/bin/nautilus --gapplication-service")
>ERROR: apport (pid 2603509) Thu Mar 16 15:38:45 2023:
> is_closing_session(): Could not determine DBUS socket.
>ERROR: apport (pid 2603509) Thu Mar 16 15:38:53 2023: wrote report
> /var/crash/_usr_bin_nautilus.1000.crash
>   ApportVersion: 2.20.11-0ubuntu27.24
>   AptOrdering: NULL: ConfigurePending
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CrashReports:
>640:1000:125:351112706:2023-03-08 09:27:20.347548007 -0800:2023-03-08
> 09:27:21.347548007 -0800:/var/crash/_usr_libexec_gvfsd-google.1000.crash
>640:1000:125:19914318:2023-03-16 15:39:57.163937568 -0700:2023-03-16
> 15:39:58.163937568 -0700:/var/crash/_usr_bin_nautilus.1000.crash
>600:0:125:79228:2023-03-16 15:39:33.322134256 -0700:2023-03-16
> 15:39:34.322134256 -0700:/var/crash/python3-problem-report.0.crash
>   Date: Thu Mar 16 15:39:34 2023
>   Dependencies:
>
>   DpkgHistoryLog:
>Start-Date: 2023-03-16  15:39:33
>Commandline: /usr/bin/apt-get -fy install
>Requested-By: druffer (1000)
>   DuplicateSignature:
>package:python3-problem-report:2.20.11-0ubuntu27.24
>Setting up python3-setuptools (45.2.0-1ubuntu0.1) ...
>dpkg: error processing package python3-problem-report (--configure):
> package is in a very bad inconsistent state; you should
>   ErrorMessage: package is in a very bad inconsistent state; you should
> reinstall it before attempting configuration
>   InstallationDate: Installed on 2022-10-20 (147 days ago)
>   InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64
> (20220223)
>   PackageArchitecture: all
>   Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal,
> 3.8.2-0ubuntu2
>   PythonDetails: N/A
>   RelatedPackageVersions:
>dpkg 1.19.7ubuntu3.2
>apt  2.0.9
>   SourcePackage: apport
>   Title: package python3-problem-report 2.20.11-0ubuntu27.24 failed to
> install/upgrade: package is in a very bad inconsistent state; you should
> reinstall it before attempting configuration
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2012008/+subscriptions
>
>

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

Title:
  package python3-problem-report 2.20.11-0ubuntu27.24 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  Getting an error on every boot now.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: python3-problem-report 2.20.11-0ubuntu27.24
  ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  ApportLog:
   ERROR: apport (pid 2603509) Thu Mar 16 15:38:45 2023: called for pid 3674, 
signal 11, core limit 0, dump mode 1
   ERROR: apport (pid 2603509) Thu Mar 16 15:38:45 2023: executable: 
/usr/bin/nautilus (command line "/usr/bin/nautilus --gapplication-service")
   ERROR: apport (pid 2603509) Thu Mar 16 15:38:45 2023: is_closing_session(): 
Could not determine DBUS socket.
   ERROR: apport (pid 2603509) Thu Mar 16 15:38:53 2023: wrote report 
/var/crash/_usr_bin_nautilus.1000.crash
  ApportVersion: 2.20.11-0ubuntu27.24
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashReports:
   

[Touch-packages] [Bug 2012008] [NEW] package python3-problem-report 2.20.11-0ubuntu27.24 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempt

[Dennis Ruffer]

Public bug reported:

Getting an error on every boot now.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: python3-problem-report 2.20.11-0ubuntu27.24
ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74
Uname: Linux 5.15.0-58-generic x86_64
ApportLog:
 ERROR: apport (pid 2603509) Thu Mar 16 15:38:45 2023: called for pid 3674, 
signal 11, core limit 0, dump mode 1
 ERROR: apport (pid 2603509) Thu Mar 16 15:38:45 2023: executable: 
/usr/bin/nautilus (command line "/usr/bin/nautilus --gapplication-service")
 ERROR: apport (pid 2603509) Thu Mar 16 15:38:45 2023: is_closing_session(): 
Could not determine DBUS socket.
 ERROR: apport (pid 2603509) Thu Mar 16 15:38:53 2023: wrote report 
/var/crash/_usr_bin_nautilus.1000.crash
ApportVersion: 2.20.11-0ubuntu27.24
AptOrdering: NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
CrashReports:
 640:1000:125:351112706:2023-03-08 09:27:20.347548007 -0800:2023-03-08 
09:27:21.347548007 -0800:/var/crash/_usr_libexec_gvfsd-google.1000.crash
 640:1000:125:19914318:2023-03-16 15:39:57.163937568 -0700:2023-03-16 
15:39:58.163937568 -0700:/var/crash/_usr_bin_nautilus.1000.crash
 600:0:125:79228:2023-03-16 15:39:33.322134256 -0700:2023-03-16 
15:39:34.322134256 -0700:/var/crash/python3-problem-report.0.crash
Date: Thu Mar 16 15:39:34 2023
Dependencies:
 
DpkgHistoryLog:
 Start-Date: 2023-03-16  15:39:33
 Commandline: /usr/bin/apt-get -fy install
 Requested-By: druffer (1000)
DuplicateSignature:
 package:python3-problem-report:2.20.11-0ubuntu27.24
 Setting up python3-setuptools (45.2.0-1ubuntu0.1) ...
 dpkg: error processing package python3-problem-report (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2022-10-20 (147 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt  2.0.9
SourcePackage: apport
Title: package python3-problem-report 2.20.11-0ubuntu27.24 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

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

Title:
  package python3-problem-report 2.20.11-0ubuntu27.24 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in apport package in Ubuntu:
  New

Bug description:
  Getting an error on every boot now.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: python3-problem-report 2.20.11-0ubuntu27.24
  ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  ApportLog:
   ERROR: apport (pid 2603509) Thu Mar 16 15:38:45 2023: called for pid 3674, 
signal 11, core limit 0, dump mode 1
   ERROR: apport (pid 2603509) Thu Mar 16 15:38:45 2023: executable: 
/usr/bin/nautilus (command line "/usr/bin/nautilus --gapplication-service")
   ERROR: apport (pid 2603509) Thu Mar 16 15:38:45 2023: is_closing_session(): 
Could not determine DBUS socket.
   ERROR: apport (pid 2603509) Thu Mar 16 15:38:53 2023: wrote report 
/var/crash/_usr_bin_nautilus.1000.crash
  ApportVersion: 2.20.11-0ubuntu27.24
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashReports:
   640:1000:125:351112706:2023-03-08 09:27:20.347548007 -0800:2023-03-08 
09:27:21.347548007 -0800:/var/crash/_usr_libexec_gvfsd-google.1000.crash
   640:1000:125:19914318:2023-03-16 15:39:57.163937568 -0700:2023-03-16 
15:39:58.163937568 -0700:/var/crash/_usr_bin_nautilus.1000.crash
   600:0:125:79228:2023-03-16 15:39:33.322134256 -0700:2023-03-16 
15:39:34.322134256 -0700:/var/crash/python3-problem-report.0.crash
  Date: Thu Mar 16 15:39:34 2023
  Dependencies:
   
  DpkgHistoryLog:
   Start-Date: 2023-03-16  15:39:33
   Commandline: /usr/bin/apt-get -fy install
   Requested-By: druffer (1000)
  DuplicateSignature:
   package:python3-problem-report:2.20.11-0ubuntu27.24
   Setting up python3-setuptools (45.2.0-1ubuntu0.1) ...
   dpkg: error processing package python3-problem-report (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2022-10-20 (147 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release 

[Touch-packages] [Bug 2007684] [NEW] package linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Dennis Layne]

Public bug reported:

bug window popped up.  I clicked submit

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1
ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
Uname: Linux 5.15.0-60-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Fri Feb 17 06:49:25 2023
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2022-09-11 (158 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.8
SourcePackage: initramfs-tools
Title: package linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package jammy

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

Title:
  package linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  bug window popped up.  I clicked submit

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
  Uname: Linux 5.15.0-60-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Fri Feb 17 06:49:25 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2022-09-11 (158 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: initramfs-tools
  Title: package linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2007684/+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 1932155] Re: *Fixed upstream* Crashes on Ubuntu 20.04.2 involving amdgpu/radeonsi and various AMD GPUs (e.g. RX 5500 XT), please merge/backport if possible!

[Dennis Gnad]

I saw in another bug that it already got backported in a PPA by Mario
Limonciello: https://launchpad.net/~superm1/+archive/ubuntu/lp1928393

However the bug manifestation looks different in that bug:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1928393

I attach a dmesg output from my PC, in which you see it differently.

This might also be a related bug:
https://gitlab.freedesktop.org/drm/amd/-/issues/934


** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #934
   https://gitlab.freedesktop.org/drm/amd/-/issues/934

** Attachment added: "amdgpu-errors-rx5500-complete-dmesg.txt"
   
https://bugs.launchpad.net/mesa/+bug/1932155/+attachment/5505043/+files/amdgpu-errors-rx5500-complete-dmesg.txt

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

Title:
  *Fixed upstream* Crashes on Ubuntu 20.04.2 involving amdgpu/radeonsi
  and various AMD GPUs (e.g. RX 5500 XT), please merge/backport if
  possible!

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  New

Bug description:
  In Ubuntu focal, 20.04.2, amdgpu/Xorg kernel driver crashes/resets
  occur with various previous-generation AMD Radeon GPUs, for instance
  Radeon RX 5500 XT. There is a recent fix in the mesa library.

  Please see upstream mesa bug including available patch:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866

  Patch is available for mesa-stable, 21.1.3 and 21.1.4. It looks like
  it could apply to 21.0 (which is in focal-proposed) too, with minor
  effort.

  Thanks if you can backport this!

  amdgpu kernel bug: https://bugzilla.kernel.org/show_bug.cgi?id=213145

  I can confirm it with linux-generic-hwe-20.04=5.8.0-55.62~20.04.1 from
  focal-updates/focal-security

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1932155/+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 1932155] Re: *Fixed upstream* Crashes on Ubuntu 20.04.2 involving amdgpu/radeonsi and various AMD GPUs (e.g. RX 5500 XT), please merge/backport if possible!

[Dennis Gnad]

** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #4866
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866

** Also affects: mesa via
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866
   Importance: Unknown
   Status: Unknown

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

Title:
  *Fixed upstream* Crashes on Ubuntu 20.04.2 involving amdgpu/radeonsi
  and various AMD GPUs (e.g. RX 5500 XT), please merge/backport if
  possible!

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  New

Bug description:
  In Ubuntu focal, 20.04.2, amdgpu/Xorg kernel driver crashes/resets
  occur with various previous-generation AMD Radeon GPUs, for instance
  Radeon RX 5500 XT. There is a recent fix in the mesa library.

  Please see upstream mesa bug including available patch:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866

  Patch is available for mesa-stable, 21.1.3 and 21.1.4. It looks like
  it could apply to 21.0 (which is in focal-proposed) too, with minor
  effort.

  Thanks if you can backport this!

  amdgpu kernel bug: https://bugzilla.kernel.org/show_bug.cgi?id=213145

  I can confirm it with linux-generic-hwe-20.04=5.8.0-55.62~20.04.1 from
  focal-updates/focal-security

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1932155/+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 1932155] [NEW] *Fixed upstream* Crashes on Ubuntu 20.04.2 involving amdgpu/radeonsi and various AMD GPUs (e.g. RX 5500 XT), please merge/backport if possible!

[Dennis Gnad]

Public bug reported:

In Ubuntu focal, 20.04.2, amdgpu/Xorg kernel driver crashes/resets occur
with various previous-generation AMD Radeon GPUs, for instance Radeon RX
5500 XT. There is a recent fix in the mesa library.

Please see upstream mesa bug including available patch:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866

Patch is available for mesa-stable, 21.1.3 and 21.1.4. It looks like it
could apply to 21.0 (which is in focal-proposed) too, with minor effort.

Thanks if you can backport this!

amdgpu kernel bug: https://bugzilla.kernel.org/show_bug.cgi?id=213145

I can confirm it with linux-generic-hwe-20.04=5.8.0-55.62~20.04.1 from
focal-updates/focal-security

** Affects: mesa
 Importance: Unknown
 Status: Unknown

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


** Tags: focal patch-accepted-upstream

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

Title:
  *Fixed upstream* Crashes on Ubuntu 20.04.2 involving amdgpu/radeonsi
  and various AMD GPUs (e.g. RX 5500 XT), please merge/backport if
  possible!

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  New

Bug description:
  In Ubuntu focal, 20.04.2, amdgpu/Xorg kernel driver crashes/resets
  occur with various previous-generation AMD Radeon GPUs, for instance
  Radeon RX 5500 XT. There is a recent fix in the mesa library.

  Please see upstream mesa bug including available patch:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866

  Patch is available for mesa-stable, 21.1.3 and 21.1.4. It looks like
  it could apply to 21.0 (which is in focal-proposed) too, with minor
  effort.

  Thanks if you can backport this!

  amdgpu kernel bug: https://bugzilla.kernel.org/show_bug.cgi?id=213145

  I can confirm it with linux-generic-hwe-20.04=5.8.0-55.62~20.04.1 from
  focal-updates/focal-security

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1932155/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).

[Dennis]

@vanvugt

Thank you for your quick response!
Does that mean I would have to wait for Pulseaudio to fix this in one of their 
future releases (maybe v.15) or will it be possible to use an alternative 
soundmanager, where the kernel fixes would be sufficient to use A2DP for 
bidirectional bluetooth sound?

Homeoffice without cableless headset is just not that comfortable :s


Best Regards
Dennis

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support (Bluetooth A2DP codecs).

Status in PulseAudio:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  In Progress
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).

[Dennis]

Hey there,

according to the above statements there has been a fix released for
bluez bluetooth stack as well for ubuntu system?

Am I able to get this fix installed for now?


Best Regards
Dennis

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support (Bluetooth A2DP codecs).

Status in PulseAudio:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  In Progress
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1847896] Re: Unable to shutdown or restart from log-in screen

[Scott Dennis]

Thanks for the fix. I tested it on my end and I confirmed this bug as
being fixed. I can now restart and shutdown via gdm.

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

Title:
  Unable to shutdown or restart from log-in screen

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Eoan:
  Fix Committed
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * Shutdown and restart options don't work from the login screen, when
  the user is not logged in.

  [Test Case]

   * Start the system and don't log in, or log out in case the system is set up 
with autologin.
   * Restart, then shut down the system using the option in the upper right 
corner of the login screen.
   * Observe both operations working.

  [Regression Potential]

   * The fix is treating treating the greeter as user display sessions
  by cherry-picking upstream's change released in v243. The fix itself
  is very small, but there may be non-obvious security implications.

  [Original Bug Text]

  When selecting the shutdown icon from the log-in screen you are
  prompted with a dialog that allows you to either cancel, restart or
  shutdown.

  It has been noted that the restart and shutdown options no longer
  work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 13 09:08:23 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-05-17 (148 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1847896/+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 1847896] Re: Unable to shutdown or restart from log-in screen

[Scott Dennis]

i got an email about released. I also notice on here that a fix has been
released. I don't see it as an update via software updates. How to I get
the fix.

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

Title:
  Unable to shutdown or restart from log-in screen

Status in gnome-shell package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Eoan:
  Confirmed
Status in systemd source package in Eoan:
  Confirmed

Bug description:
  [Impact]

   * Shutdown and restart options don't work from the login screen, when
  the user is not logged in.

  [Test Case]

   * Start the system and don't log in, or log out in case the system is set up 
with autologin.
   * Restart, then shut down the system using the option in the upper right 
corner of the login screen.
   * Observe both operations working.

  [Regression Potential]

   * The fix is treating treating the greeter as user display sessions
  by cherry-picking upstream's change released in v243. The fix itself
  is very small, but there may be non-obvious security implications.

  [Original Bug Text]

  When selecting the shutdown icon from the log-in screen you are
  prompted with a dialog that allows you to either cancel, restart or
  shutdown.

  It has been noted that the restart and shutdown options no longer
  work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 13 09:08:23 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-05-17 (148 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847896/+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 1801538] Re: no sound after upgrading to ubuntu 18.10 from 18.04

[Dennis Shimer]

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

Same thing for me with a Lenovo L520 and Intel chipset.  Some relevant
information just in case

sudo lshw -c sound
  *-multimedia  
   description: Audio device
   product: 6 Series/C200 Series Chipset Family High Definition Audio 
Controller
   vendor: Intel Corporation
   physical id: 1b
   bus info: pci@:00:1b.0
   version: 04
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress bus_master cap_list
   configuration: driver=snd_hda_intel latency=0
   resources: irq:28 memory:f090-f0903fff
  *-usb:1
   description: Video
   product: Integrated Camera
   vendor: Chicony Electronics Co., Ltd.
   physical id: 4
   bus info: usb@2:1.4
   version: 2.22
   capabilities: usb-2.00
   configuration: driver=uvcvideo maxpower=200mA speed=480Mbit/s
---
lspci -nnk | grep -A2 Audio
00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series Chipset 
Family High Definition Audio Controller [8086:1c20] (rev 04)
Subsystem: Lenovo 6 Series/C200 Series Chipset Family High Definition 
Audio Controller [17aa:21dd]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
---
lsmod | grep snd_hda_intel
snd_hda_intel  40960  3
snd_hda_codec 126976  4 
snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek
snd_hda_core   81920  5 
snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek
snd_pcm98304  5 
snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core
snd81920  17 
snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,thinkpad_acpi,snd_pcm,snd_rawmidi
d

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

Title:
  no sound after upgrading to ubuntu 18.10 from 18.04

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.10 does not recognize sound devices. After upgrading there
  is only a dummy device known. All others are gone. In tune there is no
  sound output to nowhere.

  It does not mater it headphones are plugged or not while booting. It
  does not matter if any usb-sound device is plugged or not. The only
  device show for output in mixer is "Dummy device".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: pulseaudio 1:12.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timidity   8931 F timidity
   /dev/snd/pcmC0D0p:   timidity   8931 F...m timidity
   /dev/snd/seq:timidity   8931 F timidity
   /dev/snd/timer:  timidity   8931 f timidity
  Date: Sat Nov  3 17:25:55 2018
  InstallationDate: Installed on 2011-10-19 (2571 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago)
  dmi.bios.date: 10/21/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.15
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: TravelMate P643-M
  dmi.board.vendor: Acer
  dmi.board.version: V2.15
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.15
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15:
  dmi.product.family: TravelMate P643-M
  dmi.product.name: TravelMate P643-M
  dmi.product.sku: TravelMate P643-M_0681_2.15
  dmi.product.version: V2.15
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1801538/+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 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.

[Dennis Gray]

my /etc/initramfs-tools/conf.d/resume file contains one line

RESUME=UUID=99a2d3b2-0f29-4080-977c-35a5744279a8

I have tried several suggestions in this thread but I haven't found
anything that works. I tried

RESUME=/dev/vg_system/lv_swap

then I ran the update-initramfs -u, as suggested. I got this:

update-initramfs: Generating /boot/initrd.img-4.15.0-43-generic
W: initramfs-tools configuration sets RESUME=/dev/vg_system/lv_swap
W: but no matching swap device is available.
I: The initramfs will attempt to resume from /dev/dm-1
I: (UUID=99a2d3b2-0f29-4080-977c-35a5744279a8)
I: Set the RESUME variable to override this.

I'm not what to do from here.

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

Title:
  Long time booting : Failed to connect to lvmetad. Falling back to
  device scanning.

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Confirmed

Bug description:
  [SRU Justification]
  A regression in initramfs-tools causes it to autogenerate config in the 
initramfs saying to resume from any available swap devices, but references the 
swap device by UUID, which is not a canonical form for referring to LVM volumes 
(because of snapshotting, they are not unique).  Ubiquity also generates a file 
in /etc at install time which references the swap partition in the same way.  
Since the lvm2 initramfs hooks also only activate precisely those LVs that are 
detected as needed at boot, this adds an inappropriate 30-second boot delay to 
any system with swap on LVM, which includes any desktop system that was 
configured with LVM (but not full-disk encryption) at install time.

  [Test case]
  1. Install using the "Use LVM" option in the desktop installer.
  4. Reboot.
  5. Verify that dmesg shows a 30-second delay before mounting the root 
filesystem.
  6. Install initramfs-tools from bionic-proposed.
  7. Reboot.
  8. Verify that dmesg no longer shows a 30-second delay before mounting the 
root filesystem.
  9. Install using the bionic daily image that contains the ubiquity from 
bionic-proposed.
  10. Reboot.
  11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that 
there is no delay before mounting the root filesystem.

  [Regression potential]
  This makes changes to shell scripts, and shell is a perilous language. An 
unnoticed bug could cause all initramfs generation, and thus all kernel 
installation, to fail for some users. A regression could also cause a user to 
lose hiberation support that they currently have.

  [Original description]
  After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu 
installation", the
  system is very slow to reboot.

  It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to 
device scanning.",
  then waits 32 seconds, then continues as it should.

  I think this is a ubiquity bug, since the d-i based installer is not affected.
   - ubuntu-18.04-desktop-amd64.iso 
(a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected
   - xubuntu-18.04-desktop-amd64.iso 
(7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected
   - ubuntu-18.04-server-amd64.iso 
(a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not 
affected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+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 1731940] Re: [P7xxDM2(-G), Realtek ALC898, Headphone Jack, External] No sound at all

[Dennis Mungai Lin.Jr.]

A possible work-around: Update the jack's description to PulseAudio, as
shown:

Create the file `/usr/share/pulseaudio/alsa-mixer/paths/iec958-stereo-
output.conf` and populate it with:

```
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as
# published by the Free Software Foundation; either version 2.1 of the
# License, or (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .


[General]
description = Headphones + Digital Output (S/PDIF)

[Element IEC958]
switch = mute
```

Then set the model definition at `/etc/modprobe.d/sound.conf` with the
following entries:

`options snd-hda-intel model=no-primary-hp enable=1 index=0`

When done, issue a reboot.

For current HDA model lists, see http://git.alsa-project.org/?p=alsa-
kernel.git;a=blob;f=Documentation/sound/alsa/HD-Audio-
Models.txt;hb=HEAD.

Will test and report back.

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

Title:
  [P7xxDM2(-G), Realtek ALC898, Headphone Jack, External] No sound at
  all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Hello there,

  I have Ubuntu 16.04LTS installed on the Clevo P751DM2-G, also marketed
  as the Schenker XMG U507, the System76's Serval WS (2017 model), the
  Eurocom Sky X4E2, among others.

  The sound card is the Realtek ALC898 with the following output
  configuration:

  1. One SPDIF/headphone combo jack (to the right)
  2. One Line Out.
  3. One Line-In.
  4. One Mic-In.

  Background information:

  On Windows, one can use the Realtek HD Audio control panel pop-up menu
  on jack detection to set the output type when an audio device is
  plugged in to an appropriate jack, combined with Sound Blaster X-Fi
  MB5 software to enable post-processing effects such as Bass, noise
  cancellation, etc.

  What I have tried so far:

  1. Setting the model definition at /etc/modprobe.d/sound.conf with the
  following entries:

  options snd-hda-intel model=no-primary-hp enable=1 index=0

  Using such a line worked before on an MSI GS43VR 6RE Phantom Pro that
  also has the same (or a similar) ESS Sabre Audio DAC component.

  Expected behavior:

  When plugged into the microphone jack, the ESS Sabre DAC should be
  activated and sound should be routed to the headset.

  Observed anomaly:

  Sound comes out through the speakers instead.

  However, the line-out output works. In that case, when plugged into
  the line out, Audio works as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.14.0 x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lin2199 F pulseaudio
   /dev/snd/controlC0:  lin2199 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Nov 13 17:34:53 2017
  InstallationDate: Installed on 2017-07-25 (111 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1812 F pulseaudio
lin2199 F pulseaudio
   /dev/snd/controlC0:  gdm1812 F pulseaudio
lin2199 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [P7xxDM2(-G), Realtek ALC898, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.06.04
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P7xxDM2(-G)
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.06.04:bd12/21/2016:svnNotebook:pnP7xxDM2(-G):pvrNotApplicable:rvnNotebook:rnP7xxDM2(-G):rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P7xxDM2(-G)
  dmi.product.version: Not Applicable
  dmi.sys.vendor: 

[Touch-packages] [Bug 1759300] Re: Gnome Shell: Touchpad right click (bottom right) area does not work

[Dennis Mungai Lin.Jr.]

Once again, Gnome pushing down "features" tuned for Mac users that
people with normal touchpads don't want and didn't ask for.

I came here from this article: https://medium.com/@pck/ubuntu-18-04-fix-
for-right-click-not-working-touchpad-issues-40037ff249e1

Thank God it can still be disabled and reverted to the old behavior:
https://itsfoss.com/fix-right-click-touchpad-ubuntu/

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

Title:
  Gnome Shell: Touchpad right click (bottom right) area does not work

Status in gsettings-desktop-schemas package in Ubuntu:
  Invalid

Bug description:
  The right (second) touchpad click does not work.
  It ceased to work about three months ago.
  ubuntu 18,04 aser ex2519

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1759300/+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 1797714] Re: [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta

[Dennis L.]

Update: Probably related to this report:
https://bugs.launchpad.net/ubuntu/+source/timidity/+bug/1798466

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

Title:
  [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I upgraded from Kubuntu 18.04 to 18.10 beta today, and I noticed I don't have 
sounds. The UI only shows a 'Dummy Device'. After doing a 'sudo alsa 
force-reload', KDE shows the audio device.
  When I execute alsamixer in a shell before executing the force-reload, the 
audio card is shown.

  My hardware: (from lspci)
  00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High 
Definition Audio (rev 05)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: pulseaudio 1:12.2-0ubuntu4
  Uname: Linux 4.19.0-041900rc6-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  juergen8924 F pulseaudio
   /dev/snd/controlC1:  juergen8924 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Oct 13 21:07:53 2018
  InstallationDate: Installed on 2015-02-16 (1334 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to cosmic on 2018-10-13 (0 days ago)
  dmi.bios.date: 10/06/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0KM426
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A02
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd10/06/2009:svnDellInc.:pnStudio1557:pvrA02:rvnDellInc.:rn0KM426:rvrA02:cvnDellInc.:ct8:cvrA02:
  dmi.product.name: Studio 1557
  dmi.product.version: A02
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714/+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 1797714] Re: [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta

[Dennis L.]

Removing the timidity package resolved this for me.

But the symptoms are strange: 
Symptoms after upgrading from 18.04 to 18:10:
- aplay -l shows all audio devices as expected, including internal on-board 
sound device
- pavucontrol only shows hdmi3 output, analog sound is missing from options

Removing timidity (just out of frustration because I couldn't find any
other suggestions on this) and rebooting once brought back the analog
sound devices

Thanks to JR for mentioning this.

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

Title:
  [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I upgraded from Kubuntu 18.04 to 18.10 beta today, and I noticed I don't have 
sounds. The UI only shows a 'Dummy Device'. After doing a 'sudo alsa 
force-reload', KDE shows the audio device.
  When I execute alsamixer in a shell before executing the force-reload, the 
audio card is shown.

  My hardware: (from lspci)
  00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High 
Definition Audio (rev 05)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: pulseaudio 1:12.2-0ubuntu4
  Uname: Linux 4.19.0-041900rc6-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  juergen8924 F pulseaudio
   /dev/snd/controlC1:  juergen8924 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Oct 13 21:07:53 2018
  InstallationDate: Installed on 2015-02-16 (1334 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to cosmic on 2018-10-13 (0 days ago)
  dmi.bios.date: 10/06/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0KM426
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A02
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd10/06/2009:svnDellInc.:pnStudio1557:pvrA02:rvnDellInc.:rn0KM426:rvrA02:cvnDellInc.:ct8:cvrA02:
  dmi.product.name: Studio 1557
  dmi.product.version: A02
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714/+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 1716654] Re: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns, dropouts or crackling sound

[Dennis Mungai Lin.Jr.]

Use this workaround which disables timer-based scheduling, which is the
root cause of the glitchy audio:

PulseAudio uses timer-based audio scheduling instead of the traditional,
interrupt-driven approach by default. This tends to expose issues in
some ALSA drivers, such as this glitch (observed on a Clevo P751DM2-G
under heavy load, for instance).

To turn timer-based scheduling off add tsched=0 in
/etc/pulse/default.pa:

Edit /etc/pulse/default.pa:

```

load-module module-udev-detect tsched=0

```

Then restart the PulseAudio server:

 pulseaudio -k
 pulseaudio --start


Note that if you are using Intel's IOMMU and experience glitches and/or
skips, add intel_iommu=igfx_off to your kernel command line and
regenerate the grub configuration as shown:

sudo update-grub

And reboot to test your changes.

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

Title:
  [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns,
  dropouts or crackling sound

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Have checked under windows (same computer in dual-boot & same
  headset), and the sound is crystal clear, so 99% sure this is not a
  hardware problem.

  Motherboard is ASUS Crosshair Hero 6.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  paul   2587 F pulseaudio
   /dev/snd/controlC0:  paul   2587 F pulseaudio
   /dev/snd/controlC1:  paul   2587 F pulseaudio
   /dev/snd/controlC2:  paul   2587 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 12 11:48:05 2017
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic 
successful
  Symptom_Card: HD-Audio Generic - HD-Audio Generic
  Symptom_Jack: Pink Mic, Rear
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through 
plughw:Generic successful
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns, 
dropouts or crackling sound
  UpgradeStatus: Upgraded to artful on 2017-08-31 (11 days ago)
  dmi.bios.date: 07/28/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1501
  dmi.board.asset.tag: Default string
  dmi.board.name: CROSSHAIR VI HERO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1501:bd07/28/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCROSSHAIRVIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-09-12T11:37:48.670242

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1716654/+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 1721074] Re: [P95_HR, Realtek Generic, Speaker, Internal] No sound at all

[Dennis Mungai Lin.Jr.]

Hello there,

Try this workaround:


In the file /usr/share/pulseaudio/alsa-mixer/paths/iec958-stereo-output.conf, 
ensure that its' populated as such:

```

# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as
# published by the Free Software Foundation; either version 2.1 of the
# License, or (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .


[General]
description = Headphones + Digital Output (S/PDIF)

[Element IEC958]
switch = mute

```

When done, issue a reboot.

See the new tags:

```

[General]
description = Headphones + Digital Output (S/PDIF)

```

That makes it possible for userland tools such as pavucontrol (a
pulseaudio program for configuring sound device properties) and the
sound panel to pick up the settings for the headphone and SPDIF audio
jack by adding a proper description for it as shown above.

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

Title:
  [P95_HR, Realtek Generic, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  no sound at all. used to work a few weeks ago.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-36.40~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC1:  cc16   2656 F pulseaudio
   /dev/snd/pcmC0D0c:   cc16   2656 F...m pulseaudio
   /dev/snd/controlC0:  cc16   2656 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Oct  3 17:23:32 2017
  InstallationDate: Installed on 2017-08-22 (42 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC1:  cc16   2656 F pulseaudio
   /dev/snd/controlC0:  cc16   2656 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [P95_HR, Realtek Generic, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/29/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.02
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P95_HR
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.02:bd06/29/2017:svnPCSpecialistLimited:pnP95_HR:pvrNotApplicable:rvnCLEVO:rnP95_HR:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: P95_HR
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist Limited

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1721074/+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 1747023] Re: [P95_HR, Realtek ALC1220, Black Headphone Out, Right] No sound at all

[Dennis Mungai Lin.Jr.]

Hello there,

Try this workaround:


In the file /usr/share/pulseaudio/alsa-mixer/paths/iec958-stereo-output.conf, 
ensure that its' populated as such:

```

# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as
# published by the Free Software Foundation; either version 2.1 of the
# License, or (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .


[General]
description = Headphones + Digital Output (S/PDIF)

[Element IEC958]
switch = mute

```

When done, issue a reboot.

See the new tags:

```

[General]
description = Headphones + Digital Output (S/PDIF)

```

That makes it possible for userland tools such as pavucontrol (a
pulseaudio program for configuring sound device properties) and the
sound panel to pick up the settings for the headphone and SPDIF audio
jack by adding a proper description for it as shown above.

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

Title:
  [P95_HR, Realtek ALC1220, Black Headphone Out, Right] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  External headphones don't work any more. Not sure if realted to the
  internal speakers problem: https://bugs.launchpad.net/ubuntu/+source
  /alsa-driver/+bug/1721074

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC0:  cc16   2550 F pulseaudio
   /dev/snd/controlC1:  cc16   2550 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Feb  2 14:51:06 2018
  InstallationDate: Installed on 2017-08-22 (164 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC0:  cc16   2550 F pulseaudio
   /dev/snd/controlC1:  cc16   2550 F pulseaudio
  Symptom_Jack: Black Headphone Out, Right
  Symptom_Type: No sound at all
  Title: [P95_HR, Realtek ALC1220, Black Headphone Out, Right] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/29/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.02
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P95_HR
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.02:bd06/29/2017:svnPCSpecialistLimited:pnP95_HR:pvrNotApplicable:rvnCLEVO:rnP95_HR:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P95_HR
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist Limited

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1747023/+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 1774982] [NEW] X.Org upgrade resulted in screen, graphics card & input device not detected

[Dennis]

Public bug reported:

Ever since an X.Org upgrade, both my Ubuntu and Mint machines fail to
detect my screen, graphics card, and input device correctly.This
happened to both machines at the same time after an upgrade. Running my
Ubuntu machine in low-graphics mode works, but I have yet to even
resolve the issue on my Mint machine. I assume this report contains log
files, but I include info. from the xserver log file, below, which
contains the following info. on module ABI versions, and the following
errors, and warnings:

Module ABI versions:
X.Org ANSI C Emulation:0.4
X.Org Video Driver: 20.0
X.Org XInput drive:22.1
X.Org Server Extension:9.0
(++) using VT number 7

(EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission
denied

(WW) Falling back to old probe method for modesetting
(WW) Falling back to old probe method for fbdev
(WW) Falling back to old probe method for vesa

(EE) intel(0):[drm] failed to set drm interface version Permission denied [13]
(EE) intel(0): Failed to claim DRM device
(ii) UnloadModule: "intel"
(EE) Screen(s)found, but none have a usable configuration
(EE) Fatal server error
(EE) Please consult the X.Org Foundation support at http://wiki.x.org for help
(EE) Please also check the log file "/var/log/Xorg.0.log" for additional info.
(EE) Server terminated w/error(1). Closing log file

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
Uname: Linux 4.4.0-127-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Jun  4 06:52:55 2018
DistUpgraded: 2016-08-21 11:26:30,537 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory))
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] 
(rev 03) (prog-if 00 [VGA controller])
   Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:0420]
   Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:0420]
InstallationDate: Installed on 2015-03-24 (1168 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Dell Inc. OptiPlex 780
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic 
root=UUID=82224d43-e3b0-4b70-b588-ea0bfdceb405 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-08-21 (651 days ago)
dmi.bios.date: 11/03/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 03NVJ6
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 15
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd11/03/2010:svnDellInc.:pnOptiPlex780:pvr:rvnDellInc.:rn03NVJ6:rvrA02:cvnDellInc.:ct15:cvr:
dmi.product.name: OptiPlex 780
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
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
xserver.bootTime: Tue May 22 07:18:58 2018
xserver.configfile: default
xserver.devices:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.7

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


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

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

Title:
  X.Org upgrade resulted in screen, graphics card & input device not
  detected

Status in xorg package in Ubuntu:
  New

Bug description:
  Ever since an X.Org upgrade, both my Ubuntu and Mint machines fail to
  detect my screen, graphics card, and input device correctly.This
  happened to both machines at the same time after an upgrade. Running
  my Ubuntu machine in low-graphics mode works, but I have yet to even
  resolve the issue on my Mint machine. I assume this report 

[Touch-packages] [Bug 861642] Re: upowerd uses 100% cpu till killed

[Dennis]

This bug was posted in 2011 and is still present in 2018. My version:

Linux thinkpad 4.4.0-119-generic #143-Ubuntu SMP Mon Apr 2 16:08:24 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  upowerd uses 100% cpu till killed

Status in Upower:
  New
Status in upower package in Ubuntu:
  Confirmed

Bug description:
  top - 12:57:54 up  2:56,  3 users,  load average: 1.06, 1.12, 1.35
  Tasks: 219 total,   2 running, 216 sleeping,   0 stopped,   1 zombie
  Cpu0  : 70.2%us, 29.8%sy,  0.0%ni,  0.0%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
  Cpu1  :  2.3%us,  1.3%sy,  0.0%ni, 96.4%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
  Cpu2  :  1.0%us,  0.3%sy,  0.0%ni, 98.7%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
  Cpu3  :  0.7%us,  1.6%sy,  0.0%ni, 97.7%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
  Cpu4  :  0.0%us,  0.3%sy,  0.0%ni, 99.7%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
  Cpu5  :  0.0%us,  0.3%sy,  0.0%ni, 98.3%id,  1.4%wa,  0.0%hi,  0.0%si,  0.0%st
  Mem:   5994176k total,  4198260k used,  1795916k free,63308k buffers
  Swap:  8193144k total,   355188k used,  7837956k free,   334316k cached

PID USER  PR  NI  VIRT  RES  SHR S %CPU %MEMTIME+  COMMAND  
  
   2268 root  20   0  148m 1572  680 R  100  0.0 111:08.37 upowerd

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: upower 0.9.9-4
  ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Wed Sep 28 12:53:23 2011
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  ProcEnviron:
   
  SourcePackage: upower
  UpgradeStatus: Upgraded to natty on 2011-04-06 (175 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/upower/+bug/861642/+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 1766077] [NEW] Power Save Blank Screen Resoration Ubuntu 18.04

[Dennis McLeod]

Public bug reported:

After Blank Screen has time operated, Display screens can be re-energized but 
only to a display of colored noise all over them.
To recover the machine must be turned of and restarted from scratch.

The problem can be bypassed by deactivating the Screen Blank feature and
only using the suspend mode to avoid having to use a forced power off
and loosing data.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 22 08:16:38 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] 
[1002:6611] (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Oland [Radeon HD 8570 / R7 240/340 OEM] 
[1043:869e]
InstallationDate: Installed on 2018-03-27 (26 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325)
MachineType: ASUSTeK COMPUTER INC. M52BC_M32BC
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic.efi.signed 
root=UUID=ea31804e-9cf0-469c-803d-f52d3c3797a3 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/12/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0401
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M52BC_M32BC
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0401:bd08/12/2015:svnASUSTeKCOMPUTERINC.:pnM52BC_M32BC:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM52BC_M32BC:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: Desktop
dmi.product.name: M52BC_M32BC
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  Power Save Blank Screen Resoration Ubuntu 18.04

Status in xorg package in Ubuntu:
  New

Bug description:
  After Blank Screen has time operated, Display screens can be re-energized but 
only to a display of colored noise all over them.
  To recover the machine must be turned of and restarted from scratch.

  The problem can be bypassed by deactivating the Screen Blank feature
  and only using the suspend mode to avoid having to use a forced power
  off and loosing data.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 22 08:16:38 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 
OEM] [1002:6611] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Oland [Radeon HD 8570 / R7 240/340 OEM] 
[1043:869e]
  InstallationDate: Installed on 2018-03-27 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325)
  MachineType: ASUSTeK COMPUTER INC. M52BC_M32BC
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic.efi.signed 
root=UUID=ea31804e-9cf0-469c-803d-f52d3c3797a3 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  

[Touch-packages] [Bug 1492180] Re: iwconfig reports wrong bitrate (6 Mb/s)

[Dennis Mungai Lin.Jr.]

Still present in 2018.

iw dev wlp112s0 link
Connected to e4:f4:c6:11:db:df (on wlp112s0)
SSID: War
freq: 5500
RX: 3408930932 bytes (2317180 packets)
TX: 117918998 bytes (1283736 packets)
signal: -41 dBm
tx bitrate: 6.0 MBit/s

bss flags:  short-slot-time
dtim period:1
beacon int: 100

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

Title:
  iwconfig reports wrong bitrate (6 Mb/s)

Status in One Hundred Papercuts:
  Confirmed
Status in wireless-tools package in Ubuntu:
  Confirmed

Bug description:
  Upgraded to Wily. iwconfig now says the Bitrate is 6 Mb/s when 'iw dev
  wlan0 link' seems to report the correct bitrate.

  Firmware iwlwifi-7260-13.ucode

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: wireless-tools 30~pre9-8ubuntu1
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Sep  4 12:43:52 2015
  Dependencies:
   gcc-5-base 5.2.1-15ubuntu5
   libc6 2.21-0ubuntu4
   libgcc1 1:5.2.1-15ubuntu5
   libiw30 30~pre9-8ubuntu1
   multiarch-support 2.21-0ubuntu4
  InstallationDate: Installed on 2011-11-11 (1393 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: wireless-tools
  UpgradeStatus: Upgraded to wily on 2015-09-04 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1492180/+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 1385292] Re: can't rename files in nautilus

[Dennis Baudys]

The problem still exists here (e.g. using nemo and trying to rename
files does not work in any way). I'm living with this very annoying bug
since years. Frustrating.

DistroRelease: Linux Mint 17.3 Rosa
Uname: Linux 4.4.0-109-generic #132~14.04.1-Ubuntu SMP
NonfreeKernelModules: nvidia
Architecture: amd64
CurrentDesktop: Cinnamon

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

Title:
  can't rename files in nautilus

Status in ibus:
  Unknown
Status in ibus package in Ubuntu:
  Triaged

Bug description:
  sometimes can't rename files with F2 button. It is higlight changing,
  but nothing gonna happen, it is not responding

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: nautilus 1:3.10.1-0ubuntu15
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 24 17:48:33 2014
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 
'permissions', 'mime_type', 'where']"
  InstallationDate: Installed on 2014-10-24 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1385292/+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 1731940] [NEW] [P7xxDM2(-G), Realtek ALC898, Headphone Jack, External] No sound at all

[Dennis Mungai Lin.Jr.]

Public bug reported:

Hello there,

I have Ubuntu 16.04LTS installed on the Clevo P751DM2-G, also marketed
as the Schenker XMG U507, the System76's Serval WS (2017 model), the
Eurocom Sky X4E2, among others.

The sound card is the Realtek ALC898 with the following output
configuration:

1. One SPDIF/headphone combo jack (to the right)
2. One Line Out.
3. One Line-In.
4. One Mic-In.

Background information:

On Windows, one can use the Realtek HD Audio control panel pop-up menu
on jack detection to set the output type when an audio device is plugged
in to an appropriate jack, combined with Sound Blaster X-Fi MB5 software
to enable post-processing effects such as Bass, noise cancellation, etc.

What I have tried so far:

1. Setting the model definition at /etc/modprobe.d/sound.conf with the
following entries:

options snd-hda-intel model=no-primary-hp enable=1 index=0

Using such a line worked before on an MSI GS43VR 6RE Phantom Pro that
also has the same (or a similar) ESS Sabre Audio DAC component.

Expected behavior:

When plugged into the microphone jack, the ESS Sabre DAC should be
activated and sound should be routed to the headset.

Observed anomaly:

Sound comes out through the speakers instead.

However, the line-out output works. In that case, when plugged into the
line out, Audio works as expected.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
Uname: Linux 4.14.0 x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  lin2199 F pulseaudio
 /dev/snd/controlC0:  lin2199 F pulseaudio
CurrentDesktop: GNOME
Date: Mon Nov 13 17:34:53 2017
InstallationDate: Installed on 2017-07-25 (111 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  gdm1812 F pulseaudio
  lin2199 F pulseaudio
 /dev/snd/controlC0:  gdm1812 F pulseaudio
  lin2199 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [P7xxDM2(-G), Realtek ALC898, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/21/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.06.04
dmi.board.asset.tag: Tag 12345
dmi.board.name: P7xxDM2(-G)
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.06.04:bd12/21/2016:svnNotebook:pnP7xxDM2(-G):pvrNotApplicable:rvnNotebook:rnP7xxDM2(-G):rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: P7xxDM2(-G)
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook

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


** Tags: amd64 apport-bug xenial

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

Title:
  [P7xxDM2(-G), Realtek ALC898, Headphone Jack, External] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hello there,

  I have Ubuntu 16.04LTS installed on the Clevo P751DM2-G, also marketed
  as the Schenker XMG U507, the System76's Serval WS (2017 model), the
  Eurocom Sky X4E2, among others.

  The sound card is the Realtek ALC898 with the following output
  configuration:

  1. One SPDIF/headphone combo jack (to the right)
  2. One Line Out.
  3. One Line-In.
  4. One Mic-In.

  Background information:

  On Windows, one can use the Realtek HD Audio control panel pop-up menu
  on jack detection to set the output type when an audio device is
  plugged in to an appropriate jack, combined with Sound Blaster X-Fi
  MB5 software to enable post-processing effects such as Bass, noise
  cancellation, etc.

  What I have tried so far:

  1. Setting the model definition at /etc/modprobe.d/sound.conf with the
  following entries:

  options snd-hda-intel model=no-primary-hp enable=1 index=0

  Using such a line worked before on an MSI GS43VR 6RE Phantom Pro that
  also has the same (or a similar) ESS Sabre Audio DAC component.

  Expected behavior:

  When plugged into the microphone jack, the ESS Sabre DAC should be
  activated and sound should be routed to the headset.

  Observed anomaly:

  Sound comes out through the speakers instead.

  However, the line-out output works. In that case, when plugged into
  the line out, 

[Touch-packages] [Bug 1730074] [NEW] games and menu

[Dennis Huffman]

Public bug reported:

After adding games from Synaptic I couldn't go to Administration or
Preferences. They were cut off. S I had to delete some games and then
fix broken packages.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sat Nov  4 08:08:35 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
   Subsystem: Dell Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [1028:06ac]
InstallationDate: Installed on 2017-11-03 (0 days ago)
InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
MachineType: Dell Inc. Inspiron 15-3552
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=343298a5-bb4e-4b6b-9a51-cbcf6e910c75 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/15/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 4.1.0
dmi.board.name: 0787MR
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvr4.1.0:bd06/15/2017:svnDellInc.:pnInspiron15-3552:pvr4.1.0:rvnDellInc.:rn0787MR:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 15-3552
dmi.product.version: 4.1.0
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug artful ubuntu

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

Title:
  games and menu

Status in xorg package in Ubuntu:
  New

Bug description:
  After adding games from Synaptic I couldn't go to Administration or
  Preferences. They were cut off. S I had to delete some games and then
  fix broken packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Nov  4 08:08:35 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Dell Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [1028:06ac]
  InstallationDate: Installed on 2017-11-03 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  MachineType: Dell Inc. Inspiron 15-3552
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=343298a5-bb4e-4b6b-9a51-cbcf6e910c75 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 4.1.0
  dmi.board.name: 0787MR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr4.1.0:bd06/15/2017:svnDellInc.:pnInspiron15-3552:pvr4.1.0:rvnDellInc.:rn0787MR:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3552
  dmi.product.version: 4.1.0
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  

[Touch-packages] [Bug 1727301] Re: 229-4ubuntu20 added ARP option breaks existing bonding interfaces

[Dennis Kuhn]

I could solve this issue by rebuilding the debian packages without two
patches:

- networkd-add-support-to-configure-NOARP-ARP-for-interface.patch
- networkd-bond-support-primary-slave-and-active-slave-4873.patch

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

Title:
  229-4ubuntu20 added ARP option breaks existing bonding interfaces

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  this breaks existing configurations with bonding on upgrading from
  229-4ubuntu19 to 229-4ubuntu20 on xenial

  as bond interfaces are now by default configured without ARP. Hence
  you suddenly lose network connectivity on upgrade. Very bad for a SRU.

  Plus adding "ARP=yes" to the Link section of a .network file does not
  work.

  Before this update, bond interfaces (specifically 802.3ad) were
  defaulting to ARP enabled. After the upgrade, they are created with
  NOARP set on the link.

  pre-upgrade:

  eth0: 
  eth1: 
  bond0: 

  post-upgrade:
  eth0: 
  eth1: 
  bond0: 

  Linux cnode11 4.4.0-97-generic #120-Ubuntu SMP Tue Sep 19 17:28:18 UTC
  2017 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727301/+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 1727301] Re: 229-4ubuntu20 added ARP option breaks existing bonding interfaces

[Dennis Kuhn]

We have the same problem without bond configured. After upgrading to
systemd 229-4ubuntu20 NOARP is set to our network interfaces. The
machine has two network interfaces and the configuration is very simple:

# 50-ens5f0.network

[Match]
MACAddress=24:8a:7:11:50:a8

[Link]
MTUBytes=9000

[Network]
Address=10.32.34.34/30
DHCP=no
LinkLocalAddressing=no
IPv6AcceptRA=no


# 50-ens5f1.network
[Match]
MACAddress=24:8a:7:11:50:a9

[Link]
MTUBytes=9000

[Network]
Address=10.32.33.126/30
DHCP=no
LinkLocalAddressing=no
IPv6AcceptRA=no


# ip link
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: ens5f0:  mtu 1500 qdisc mq state UP 
mode DEFAULT group default qlen 1000
link/ether 24:8a:07:11:50:a8 brd ff:ff:ff:ff:ff:ff
3: ens5f1:  mtu 1500 qdisc mq state UP 
mode DEFAULT group default qlen 1000
link/ether 24:8a:07:11:50:a9 brd ff:ff:ff:ff:ff:ff

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

Title:
  229-4ubuntu20 added ARP option breaks existing bonding interfaces

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  this breaks existing configurations with bonding on upgrading from
  229-4ubuntu19 to 229-4ubuntu20 on xenial

  as bond interfaces are now by default configured without ARP. Hence
  you suddenly lose network connectivity on upgrade. Very bad for a SRU.

  Plus adding "ARP=yes" to the Link section of a .network file does not
  work.

  Before this update, bond interfaces (specifically 802.3ad) were
  defaulting to ARP enabled. After the upgrade, they are created with
  NOARP set on the link.

  pre-upgrade:

  eth0: 
  eth1: 
  bond0: 

  post-upgrade:
  eth0: 
  eth1: 
  bond0: 

  Linux cnode11 4.4.0-97-generic #120-Ubuntu SMP Tue Sep 19 17:28:18 UTC
  2017 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727301/+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 1642123] Re: Dual Monitor, one monitor (random?) doesn't power up after lock.

[Dennis Fehr]

Does nobody else have this issue? When I open the laptop lid after lock,
I still get it, 90% of the time. It's either monitor, it's not always
just one.

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

Title:
  Dual Monitor, one monitor (random?) doesn't power up after lock.

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  If I switch to a different virtual terminal, and then back to F7, it
  powers back up. I have a laptop, and an Acer Monitor connected via
  HDMI. Randomly (not always), one (never both) of the displays powers
  back up.. Note: The monitor does attempt to search for connected
  devices it seems (cycles through it's sources), but seems to find
  none? But I guess does get poked when powering on? Looking at
  Xorg.0.log and dmesg don't really seem to give any hint about it.. and
  it's only ever happened when I upgraded to Ubuntu 16.10, from 16.04
  (64bit)..

  Any help would be greatly appreciated!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ubuntu-desktop 1.373
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov 15 21:41:43 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-10-14 (1493 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120926)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: ubuntu-meta
  UpgradeStatus: Upgraded to yakkety on 2016-10-27 (20 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1642123/+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 1099766] Re: modem-manager crashed with SIGABRT in g_assertion_message()

[Dennis]

Still happens on Ubuntu 17.04.

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

Title:
  modem-manager crashed with SIGABRT in g_assertion_message()

Status in modemmanager package in Ubuntu:
  Confirmed

Bug description:
  ran dist-upgrade and rebooted, noticed this crash after login

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: modemmanager 0.6.0.0.really-0ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-0.3-generic 3.8.0-rc3
  Uname: Linux 3.8.0-0-generic x86_64
  ApportVersion: 2.8-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Jan 15 14:33:29 2013
  ExecutablePath: /usr/sbin/modem-manager
  MarkForUpload: True
  ProcCmdline: /usr/sbin/modem-manager
  ProcEnviron:
   PATH=(custom, no user)
   TERM=linux
  Signal: 6
  SourcePackage: modemmanager
  StacktraceTop:
   raise () from /lib/x86_64-linux-gnu/libc.so.6
   abort () from /lib/x86_64-linux-gnu/libc.so.6
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   mm_plugin_base_supports_task_complete ()
  Title: modem-manager crashed with SIGABRT in raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1099766/+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 1377653] Re: HDMI sound output not detected / NVIDIA optimus laptop

[Dennis Mungai Lin.Jr.]

Also affected on an MSI GS43VR 6RE Phantom Pro with an i7 6700HQ, Intel
GT 530 iGP + GTX 1060.

On this laptop model, the external monitors' outputs are wired directly
to the GTX 1060, including the HDMI audio.

In this case, "lspci -H1" doesn't even list the NVIDIA Audio device
either, similar to the one above with the Asus GL502VM.

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

Title:
  HDMI sound output not detected / NVIDIA optimus laptop

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  not sure if this is an alsa or nvidia/nouveau bug.
  HDMI audio output doesn't appear in sound settings output panel.
  Audio works well on internal speakers, but it seems there is no way to make 
it output to hdmi...

  The laptop has optimus NVIDIA+Intel.
  The behaviour is the same with nouveau or nvidia proprietary driver.

  Please let me know if further testing is required

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sam2295 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Sun Oct  5 17:05:35 2014
  InstallationDate: Installed on 2014-04-21 (166 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N56VZ.215
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N56VZ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.215:bd11/02/2012:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N56VZ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

[Dennis]

I can confirm that this bug ist still present in Ubuntu Ubuntu 16.04.2 LTS. 
ibus-daemon and ibus-ui-gtk3 allocated together at least 2GB of ram. They also 
caused together approximately 40% CPU load.

** Changed in: ibus (Ubuntu)
   Status: Expired => Confirmed

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

Title:
  ibus-ui-gtk3 big memory leak

Status in ibus package in Ubuntu:
  Confirmed

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

  Also seen on Ubuntu 14.04 64Bit

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

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

Re: [Touch-packages] [Bug 1684233] Re: package ntp 1:4.2.8p4+dfsg-3ubuntu5.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[dennis]

i suspect it was malicious, pretty sure it was my teacher in my IT program.
thank you for looking into it and getting back to me. i was having quite a
hard time removing the issue but as i need my system for school i wiped and
re installed losing my data in the process. is there any tips you might be
able to give me in securing my system a little better? currently i use
arpalert,arpwatch,chrootkit,and lynis. any pointers or help would be
greatly appreciated. again thank you for your time.

On Wed, Apr 19, 2017 at 3:40 PM, Apport retracing service <
1684...@bugs.launchpad.net> wrote:

> ** Tags removed: need-duplicate-check
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1684233
>
> Title:
>   package ntp 1:4.2.8p4+dfsg-3ubuntu5.4 failed to install/upgrade:
>   subprocess installed post-installation script returned error exit
>   status 2
>
> Status in ntp package in Ubuntu:
>   New
>
> Bug description:
>   no idea how to explain or fix the issue, but it is causing me to not
>   be able to access the school network or internet from the school
>   network ethernet switch.
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 16.04
>   Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.4
>   ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
>   Uname: Linux 4.4.0-72-generic x86_64
>   ApportVersion: 2.20.1-0ubuntu2.5
>   Architecture: amd64
>   Date: Wed Apr 19 11:02:59 2017
>   ErrorMessage: subprocess installed post-installation script returned
> error exit status 2
>   InstallationDate: Installed on 2017-02-14 (63 days ago)
>   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
> (20160420.1)
>   NtpStatus: ntpq: read: Connection refused
>   ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic
> root=UUID=28cffc81-a318-4788-996b-6ba760b5a61d ro priority=low quiet
> splash vt.handoff=7
>   RelatedPackageVersions:
>dpkg 1.18.4ubuntu1.1
>apt  1.2.19
>   SourcePackage: ntp
>   Title: package ntp 1:4.2.8p4+dfsg-3ubuntu5.4 failed to install/upgrade:
> subprocess installed post-installation script returned error exit status 2
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1684233/+subscriptions
>

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

Title:
  package ntp 1:4.2.8p4+dfsg-3ubuntu5.4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 2

Status in ntp package in Ubuntu:
  New

Bug description:
  no idea how to explain or fix the issue, but it is causing me to not
  be able to access the school network or internet from the school
  network ethernet switch.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.4
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Wed Apr 19 11:02:59 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2017-02-14 (63 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  NtpStatus: ntpq: read: Connection refused
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=28cffc81-a318-4788-996b-6ba760b5a61d ro priority=low quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: ntp
  Title: package ntp 1:4.2.8p4+dfsg-3ubuntu5.4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Re: [Touch-packages] [Bug 1684233] Re: package ntp 1:4.2.8p4+dfsg-3ubuntu5.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[dennis]

i also noticed it was extremely sloppy as well, it kind of made me laugh to
be honest

On Mon, Apr 24, 2017 at 3:51 PM, DENNIS TOVA <
dtova13190.stud...@intellitec.edu> wrote:

> i suspect it was malicious, pretty sure it was my teacher in my IT
> program. thank you for looking into it and getting back to me. i was having
> quite a hard time removing the issue but as i need my system for school i
> wiped and re installed losing my data in the process. is there any tips you
> might be able to give me in securing my system a little better? currently i
> use arpalert,arpwatch,chrootkit,and lynis. any pointers or help would be
> greatly appreciated. again thank you for your time.
>
> On Wed, Apr 19, 2017 at 3:40 PM, Apport retracing service <
> 1684...@bugs.launchpad.net> wrote:
>
>> ** Tags removed: need-duplicate-check
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1684233
>>
>> Title:
>>   package ntp 1:4.2.8p4+dfsg-3ubuntu5.4 failed to install/upgrade:
>>   subprocess installed post-installation script returned error exit
>>   status 2
>>
>> Status in ntp package in Ubuntu:
>>   New
>>
>> Bug description:
>>   no idea how to explain or fix the issue, but it is causing me to not
>>   be able to access the school network or internet from the school
>>   network ethernet switch.
>>
>>   ProblemType: Package
>>   DistroRelease: Ubuntu 16.04
>>   Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.4
>>   ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
>>   Uname: Linux 4.4.0-72-generic x86_64
>>   ApportVersion: 2.20.1-0ubuntu2.5
>>   Architecture: amd64
>>   Date: Wed Apr 19 11:02:59 2017
>>   ErrorMessage: subprocess installed post-installation script returned
>> error exit status 2
>>   InstallationDate: Installed on 2017-02-14 (63 days ago)
>>   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
>> (20160420.1)
>>   NtpStatus: ntpq: read: Connection refused
>>   ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic
>> root=UUID=28cffc81-a318-4788-996b-6ba760b5a61d ro priority=low quiet
>> splash vt.handoff=7
>>   RelatedPackageVersions:
>>dpkg 1.18.4ubuntu1.1
>>apt  1.2.19
>>   SourcePackage: ntp
>>   Title: package ntp 1:4.2.8p4+dfsg-3ubuntu5.4 failed to install/upgrade:
>> subprocess installed post-installation script returned error exit status 2
>>   UpgradeStatus: No upgrade log present (probably fresh install)
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1684233/+subscriptions
>>
>
>

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

Title:
  package ntp 1:4.2.8p4+dfsg-3ubuntu5.4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 2

Status in ntp package in Ubuntu:
  New

Bug description:
  no idea how to explain or fix the issue, but it is causing me to not
  be able to access the school network or internet from the school
  network ethernet switch.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.4
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Wed Apr 19 11:02:59 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2017-02-14 (63 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  NtpStatus: ntpq: read: Connection refused
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=28cffc81-a318-4788-996b-6ba760b5a61d ro priority=low quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: ntp
  Title: package ntp 1:4.2.8p4+dfsg-3ubuntu5.4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1684233/+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 1547109] Re: [Skylake Client platform, Realtek ALC898, Green Line Out, Rear] Underruns, dropouts or crackling sound

[Dennis Mungai Lin.Jr.]

Also observed on the MSI GS43VR 6RE Phantom Pro Gaming notebook.

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

Title:
  [Skylake Client platform, Realtek ALC898, Green Line Out, Rear]
  Underruns, dropouts or crackling sound

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  To reproduce play Audio CD using Rhythmbox.
  I noticed that the audio is crackling (not overdriven, nor skipping.)
  However I can play the audio tracks fine with Totem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   arges  1968 F...m pulseaudio
   /dev/snd/controlC0:  arges  1968 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Feb 18 11:01:16 2016
  InstallationDate: Installed on 2015-09-04 (167 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150903)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [Skylake Client platform, Realtek ALC898, Green Line Out, Rear] 
Underruns, dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/16/2015
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: SKLSE2R1.R00.B089.B00.1506160228
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Skylake DT DDR4 RVP8
  dmi.board.vendor: Intel Corp.
  dmi.board.version: 1
  dmi.chassis.asset.tag: Un-Supported
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrSKLSE2R1.R00.B089.B00.1506160228:bd06/16/2015:svnIntelCorporation:pnSkylakeClientplatform:pvr0.1:rvnIntelCorp.:rnSkylakeDTDDR4RVP8:rvr1:cvnIntelCorporation:ct3:cvr0.1:
  dmi.product.name: Skylake Client platform
  dmi.product.version: 0.1
  dmi.sys.vendor: Intel Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1547109/+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 1639744] Re: lsblk does not use extended WWNs and may return the same ID for two different disks

[Dennis Kuhn]

Any news on this issue?

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

Title:
  lsblk does not use extended WWNs and may return the same ID for two
  different disks

Status in util-linux package in Ubuntu:
  New

Bug description:
  lsblk from util-linux in xenial is affected by this bug:
  https://github.com/karelzak/util-linux/issues/321

  This means that lsblk may return the same identifier for different
  devices, because it always uses the short WWN, while some devices are
  only identified uniquely by the full (extended) WWN.

  This has been fixed in upstream util-linux for a while, but the
  version in xenial is just a tick too old. Since the patch is less than
  10 lines, maybe you would consider a backport?

  To my knowledge, this affects mainly "Enterprise" hardware - logical
  volumes on fully hardware-driven RAID controllers like HP, Dell,
  LSI/Avago, and logical volumes on external storage arrays addressed
  over iSCSI or FC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1639744/+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 1633319] Re: memory leak in indicator-datetime

[Dennis Shimer]

I completely removed my google account and it still didn't help. Is
there any way to set this service to not start at all?

At this point the only thing I have found to even make my laptop usable
is 'killall unity-panel-service'

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

Title:
  memory leak in indicator-datetime

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 16.04 to 16.10 on the System76 Serval WS
  indicator-datetime-service is consuming all the system memory from
  3.7GB up to 32 GB in 30 seconds. The system kills the indicator-
  datetime-service process and indicator-datetime-service restarts and
  memory consumption repeats until killed again. All swap memory is
  consumed in this pattern.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 00:12:00 2016
  EcryptfsInUse: Yes
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1633319/+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 1652789] Re: indicator-datetime-service using high volumes of ram/memory

[Dennis Shimer]

I completely removed my google account and it still didn't help.  Is
there any way to set this service to not start at all?  At this point
the only thing I have found to even make my laptop usable is 'killall
unity-panel-service'

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

Title:
  indicator-datetime-service using high volumes of ram/memory

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  I have noticed every time my computer boots into Ubuntu, it freezes up
  with the mouse lagging and then unfreezes. I notice the SSD making
  huge amounts of read/writes (which I imagine is into virtual
  memory/swap space). I have to leave the computer for 15 mins or so
  before coming back to it.

  I noticed `indicator-datetime-service` was using a lot of RAM in
  `System Monitor`. So I killed it, and it comes back again each time I
  kill the process. So I clicked 'Stop' with has seemed to have
  temporary fixed the problem. Obviously now the correct time is not
  displayed on the task bar.

  indicator-datetime:
    Installed: 15.10+16.10.20160820.1-0ubuntu1
    Candidate: 15.10+16.10.20160820.1-0ubuntu1
    Version table:
   *** 15.10+16.10.20160820.1-0ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
  100 /var/lib/dpkg/status

  Description:Ubuntu 16.10
  Release:16.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1652789/+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 1642123] [NEW] Dual Monitor, one monitor (random?) doesn't power up after lock.

[Dennis Fehr]

Public bug reported:

If I switch to a different virtual terminal, and then back to F7, it
powers back up. I have a laptop, and an Acer Monitor connected via HDMI.
Randomly (not always), one (never both) of the displays powers back up..
Note: The monitor does attempt to search for connected devices it seems
(cycles through it's sources), but seems to find none? But I guess does
get poked when powering on? Looking at Xorg.0.log and dmesg don't really
seem to give any hint about it.. and it's only ever happened when I
upgraded to Ubuntu 16.10, from 16.04 (64bit)..

Any help would be greatly appreciated!

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: ubuntu-desktop 1.373
ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
Uname: Linux 4.8.0-27-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Nov 15 21:41:43 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-10-14 (1493 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120926)
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
   Users in the 'systemd-journal' group can see all messages. Pass -q to
   turn off this notice.
 No journal files were opened due to insufficient permissions.
SourcePackage: ubuntu-meta
UpgradeStatus: Upgraded to yakkety on 2016-10-27 (20 days ago)

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug yakkety

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

Title:
  Dual Monitor, one monitor (random?) doesn't power up after lock.

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  If I switch to a different virtual terminal, and then back to F7, it
  powers back up. I have a laptop, and an Acer Monitor connected via
  HDMI. Randomly (not always), one (never both) of the displays powers
  back up.. Note: The monitor does attempt to search for connected
  devices it seems (cycles through it's sources), but seems to find
  none? But I guess does get poked when powering on? Looking at
  Xorg.0.log and dmesg don't really seem to give any hint about it.. and
  it's only ever happened when I upgraded to Ubuntu 16.10, from 16.04
  (64bit)..

  Any help would be greatly appreciated!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ubuntu-desktop 1.373
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov 15 21:41:43 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-10-14 (1493 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120926)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: ubuntu-meta
  UpgradeStatus: Upgraded to yakkety on 2016-10-27 (20 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1642123/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Dennis]

Same issue here after upgrade to 16.10.

Here is the log after connecting to VPN:
Switching to system DNS server 10.1.96.48.
Cache miss for daisy.ubuntu.com IN A
Transaction 29603 for  scope dns on */*.
Using feature level UDP+EDNS0+DO+LARGE for transaction 29603.
Using DNS server 10.1.96.48 for transaction 29603.
Sending query packet with id 29603.
Timeout reached on transaction 29603.
Retrying transaction 29603.
Switching to system DNS server 10.1.96.49.
Cache miss for daisy.ubuntu.com IN A
Transaction 29603 for  scope dns on */*.
Using feature level UDP+EDNS0+DO+LARGE for transaction 29603.
Using DNS server 10.1.96.49 for transaction 29603.
Sending query packet with id 29603.
Timeout reached on transaction 29603.
Retrying transaction 29603.
Switching to system DNS server 10.1.96.48.
Cache miss for daisy.ubuntu.com IN A
Transaction 29603 for  scope dns on */*.
Using feature level UDP+EDNS0+DO+LARGE for transaction 29603.
Using DNS server 10.1.96.48 for transaction 29603.
Sending query packet with id 29603.

Later on:
Lost too many UDP packets, downgrading feature level...
Using degraded feature set (UDP+EDNS0+DO) for DNS server 10.1.96.48.
Using feature level UDP+EDNS0+DO for transaction 35344.
Sending query packet with id 35344.
Timeout reached on transaction 29603.

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

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1624317/+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 1550740] Re: networkmanager segfault on startup

[Dennis]

also happens to me randomly. any ideas?
NetworkManager[837]: segfault at 4e8 ip 0046c7d0 sp 7ffec3967e20 
error 4 in NetworkManager[40+2b9000]

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

Title:
  networkmanager segfault on startup

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  NetworkManager[677]: segfault at 168 ip 004c39cd sp
  7ffe4ff2c1c0 error 4 in NetworkManager[40+1bf000]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1550740/+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 1445630] Re: Can't connect to Wifi network secured with long PSK

[Dennis Shimer]

I had the exact same problem with a much less complex password that was
comprised of 8 mixed case characters followed by and underscore which
was followed by 4 numbers

Cccc_ (just the format, not the password)

Copying and pasting worked great and it connected first try.
Nexus 4 15.04 OTA-12

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

Title:
  Can't connect to Wifi network secured with long PSK

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Confirmed

Bug description:
  Device: BQ Aquaris E5.4 Ubuntu Edition

  I just got this device and wanted to connect to my WPA2 WiFi network
  which happens to have a 54 characters-long PSK. However, after
  entering my password (which naturally takes a little while) and
  clicking on "connect", it just simply returns me to the overview of
  WiFi networks near me. No error message.

  The following askubuntu.com questions appear to be related to this problem:
  http://askubuntu.com/questions/597333/get-wifi-password-into-ubuntu-touch
  
http://askubuntu.com/questions/306734/unable-to-connect-to-secured-wi-fi-from-nexus-7-running-ubuntu-touch-13-04

  I have enabled developer mode and edited the network manager file in
  /etc/NetworkManager/system-connections/ using adb shell. After that, I
  was able to connect to my network.

  Steps to reproduce:
  1. Set up a WPA2 network and give it a long password
  2. Click on your SSID on the list
  3. Enter your password
  4. Click "Connect".

  Expected result:
  Connected to the WiFi network

  Actual result:
  You see the list again and no indications that you are connected to the 
network. You aren't connected to the network.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445630/+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 1513272] Re: Root lvm lv mounted with wrong name

[James Dennis]

Seeing this change of behavior on Ubuntu 14.04.4

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

Title:
  Root lvm lv mounted with wrong name

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Debian:
  Fix Released

Bug description:
  In 15.04 and before, my root showed up in mound/findmnt/etc as
  /dev/vg/root, but now it shows up as /dev/dm-11.  This appears to be
  due to the following new code in scripts/local:

  ROOT=$(resolve_device "$ROOT")

  This resolves the symbolic link /dev/vg/lv to /dev/dm-xx and mounts
  that instead.  It should not be doing this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1513272/+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 1556134] Re: obex-check-device crashed with SIGSEGV in __GI_____strtoul_l_internal()

[Dennis]

I agree. There should be one public bug with a status for everyone.

** This bug is no longer a duplicate of private bug 1553358

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

Title:
  obex-check-device crashed with SIGSEGV in
  __GI_strtoul_l_internal()

Status in libopenobex package in Ubuntu:
  Confirmed

Bug description:
  on launch this crash occurs

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: libopenobex2 1.7.1-4
  ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
  Uname: Linux 4.4.0-11-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Wed Mar  9 16:14:37 2016
  Dependencies:
   gcc-6-base 6-20160227-0ubuntu1
   libc6 2.21-0ubuntu6
   libgcc1 1:6-20160227-0ubuntu1
   libudev1 229-2ubuntu1
   libusb-1.0-0 2:1.0.20-1
  ExecutablePath: /usr/sbin/obex-check-device
  InstallationDate: Installed on 2016-02-11 (28 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  ProcCmdline: /usr/sbin/obex-check-device 01da
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0x7f8783a75674 <__GI_strtoul_l_internal+68>:   
movsbq (%r14),%rax
   PC (0x7f8783a75674) ok
   source "(%r14)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: libopenobex
  StacktraceTop:
   __GI_strtoul_l_internal (nptr=0x0, endptr=0x0, base=16, group=, loc=0x7f8783dff500 <_nl_global_locale>) at ../stdlib/strtol_l.c:297
   main ()
  Title: obex-check-device crashed with SIGSEGV in __GI_strtoul_l_internal()
  UpgradeStatus: Upgraded to xenial on 2016-03-02 (9 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libopenobex/+bug/1556134/+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 1573039] [NEW] package tzdata 2016d-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Dennis Olivetti]

Public bug reported:

I was just installing updates

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tzdata 2016d-0ubuntu0.16.04
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv wl
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Thu Apr 21 15:24:40 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2014-11-09 (528 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.10ubuntu1
SourcePackage: tzdata
Title: package tzdata 2016d-0ubuntu0.16.04 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: Upgraded to xenial on 2016-04-18 (3 days ago)

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


** Tags: amd64 apport-package xenial

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

Title:
  package tzdata 2016d-0ubuntu0.16.04 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in tzdata package in Ubuntu:
  New

Bug description:
  I was just installing updates

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tzdata 2016d-0ubuntu0.16.04
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu Apr 21 15:24:40 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2014-11-09 (528 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: tzdata
  Title: package tzdata 2016d-0ubuntu0.16.04 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: Upgraded to xenial on 2016-04-18 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1573039/+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 1445630] Re: Can't connect to Wifi network secured with long PSK

[dennis]

I have the Problem with a 63 charter long password
with OTA10.1

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

Title:
  Can't connect to Wifi network secured with long PSK

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Confirmed

Bug description:
  Device: BQ Aquaris E5.4 Ubuntu Edition

  I just got this device and wanted to connect to my WPA2 WiFi network
  which happens to have a 54 characters-long PSK. However, after
  entering my password (which naturally takes a little while) and
  clicking on "connect", it just simply returns me to the overview of
  WiFi networks near me. No error message.

  The following askubuntu.com questions appear to be related to this problem:
  http://askubuntu.com/questions/597333/get-wifi-password-into-ubuntu-touch
  
http://askubuntu.com/questions/306734/unable-to-connect-to-secured-wi-fi-from-nexus-7-running-ubuntu-touch-13-04

  I have enabled developer mode and edited the network manager file in
  /etc/NetworkManager/system-connections/ using adb shell. After that, I
  was able to connect to my network.

  Steps to reproduce:
  1. Set up a WPA2 network and give it a long password
  2. Click on your SSID on the list
  3. Enter your password
  4. Click "Connect".

  Expected result:
  Connected to the WiFi network

  Actual result:
  You see the list again and no indications that you are connected to the 
network. You aren't connected to the network.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445630/+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 1571640] [NEW] lightdm changing resolution

[Dennis Olivetti]

Public bug reported:

Just after the upgrade to ubuntu 16.04, when lightdm starts the
resolution is 2560x1600. Then, after about half a second it is
automatically changed to 1280x800. This happens systematically at each
boot. No external monitor is connected.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.1-0ubuntu1
Uname: Linux 4.5.0-040500-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Apr 18 14:39:03 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-11-09 (525 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
SourcePackage: lightdm
UpgradeStatus: Upgraded to xenial on 2016-04-18 (0 days ago)

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


** Tags: amd64 apport-bug xenial

** Attachment added: "x-0-greeter.log"
   
https://bugs.launchpad.net/bugs/1571640/+attachment/4639214/+files/x-0-greeter.log

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

Title:
  lightdm changing resolution

Status in lightdm package in Ubuntu:
  New

Bug description:
  Just after the upgrade to ubuntu 16.04, when lightdm starts the
  resolution is 2560x1600. Then, after about half a second it is
  automatically changed to 1280x800. This happens systematically at each
  boot. No external monitor is connected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  Uname: Linux 4.5.0-040500-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr 18 14:39:03 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-09 (525 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-04-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1571640/+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 1568010] [NEW] package keyboard-configuration 1.108ubuntu13 failed to install/upgrade: subproces post-installation script geïnstalleerd gaf een foutwaarde 10 terug

[Dennis Coomans]

Public bug reported:

i have no idea, it happend during apt-get upgrade

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: keyboard-configuration 1.108ubuntu13
ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
Uname: Linux 4.4.0-15-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
Date: Fri Apr  8 17:30:17 2016
ErrorMessage: subproces post-installation script geïnstalleerd gaf een 
foutwaarde 10 terug
InstallationDate: Installed on 2016-04-08 (0 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160323.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.10
SourcePackage: console-setup
Title: package keyboard-configuration 1.108ubuntu13 failed to install/upgrade: 
subproces post-installation script geïnstalleerd gaf een foutwaarde 10 terug
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: console-setup (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package keyboard-configuration 1.108ubuntu13 failed to
  install/upgrade: subproces post-installation script geïnstalleerd gaf
  een foutwaarde 10 terug

Status in console-setup package in Ubuntu:
  New

Bug description:
  i have no idea, it happend during apt-get upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: keyboard-configuration 1.108ubuntu13
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  Date: Fri Apr  8 17:30:17 2016
  ErrorMessage: subproces post-installation script geïnstalleerd gaf een 
foutwaarde 10 terug
  InstallationDate: Installed on 2016-04-08 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160323.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10
  SourcePackage: console-setup
  Title: package keyboard-configuration 1.108ubuntu13 failed to 
install/upgrade: subproces post-installation script geïnstalleerd gaf een 
foutwaarde 10 terug
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1568010/+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 1301015] Re: Networking does not restart

[Dennis DeMarco]

Why hasn't this been fixed yet. It's a total automation fail.

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

Title:
  Networking does not restart

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu Server 14.04 it appears it is not possible to restart
  networking. This is fresh install from ISO.

  wirehive@ubuntu:~$ sudo /etc/init.d/networking restart
  wirehive@ubuntu:~$ echo $?
  1
  wirehive@ubuntu:~$ sudo service networking restart
  stop: Job failed while stopping
  start: Job is already running: networking
  wirehive@ubuntu:~$ sudo bash -x /etc/init.d/networking restart
  + PATH=/sbin:/bin
  + RUN_DIR=/run/network
  + IFSTATE=/run/network/ifstate
  + STATEDIR=/run/network/state
  + '[' -x /sbin/ifup ']'
  + '[' -x /sbin/ifdown ']'
  + . /lib/lsb/init-functions
  +++ run-parts --lsbsysinit --list /lib/lsb/init-functions.d
  ++ for hook in '$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d 
2>/dev/null)'
  ++ '[' -r /lib/lsb/init-functions.d/20-left-info-blocks ']'
  ++ . /lib/lsb/init-functions.d/20-left-info-blocks
  ++ for hook in '$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d 
2>/dev/null)'
  ++ '[' -r /lib/lsb/init-functions.d/50-ubuntu-logging ']'
  ++ . /lib/lsb/init-functions.d/50-ubuntu-logging
  +++ LOG_DAEMON_MSG=
  ++ FANCYTTY=
  ++ '[' -e /etc/lsb-base-logging.sh ']'
  ++ true
  + CONFIGURE_INTERFACES=yes
  + EXCLUDE_INTERFACES=
  + VERBOSE=no
  + '[' -f /etc/default/networking ']'
  + verbose=
  + '[' no = yes ']'
  + case "$1" in
  + init_is_upstart
  + '[' -x /sbin/initctl ']'
  + /bin/grep -q upstart
  + /sbin/initctl version
  + return 0
  + exit 1
  wirehive@ubuntu:~$ sudo bash -x service networking restart
  ++ basename service
  + VERSION='service ver. 0.91-ubuntu1'
  ++ basename service
  + USAGE='Usage: service < option > | --status-all | [ service_name [ command 
| --full-restart ] ]'
  + SERVICE=
  + ACTION=
  + SERVICEDIR=/etc/init.d
  + OPTIONS=
  + '[' 2 -eq 0 ']'
  + cd /
  + '[' 2 -gt 0 ']'
  + case "${1}" in
  + '[' -z '' -a 2 -eq 1 -a networking = --status-all ']'
  + '[' 2 -eq 2 -a restart = --full-restart ']'
  + '[' -z '' ']'
  + SERVICE=networking
  + shift
  + '[' 1 -gt 0 ']'
  + case "${1}" in
  + '[' -z networking -a 1 -eq 1 -a restart = --status-all ']'
  + '[' 1 -eq 2 -a '' = --full-restart ']'
  + '[' -z networking ']'
  + '[' -z '' ']'
  + ACTION=restart
  + shift
  + '[' 0 -gt 0 ']'
  + '[' -r /etc/init/networking.conf ']'
  + which initctl
  + grep -q upstart
  + initctl version
  + case "${ACTION}" in
  + stop networking
  stop: Job failed while stopping
  + :
  + exec start networking
  start: Job is already running: networking
  wirehive@ubuntu:~$

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1301015/+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 1555935] [NEW] Audio button records silence

[Dennis O'Flaherty]

Public bug reported:

Pressing and holding the microphone button seems to let me record audio,
but the generated audio file is completely silent.  This hasn't worked
since the microphone button showed up in the messaging app.

Nexus 4,  r258

** Affects: messaging-app (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Audio button records silence

Status in messaging-app package in Ubuntu:
  New

Bug description:
  Pressing and holding the microphone button seems to let me record
  audio, but the generated audio file is completely silent.  This hasn't
  worked since the microphone button showed up in the messaging app.

  Nexus 4,  r258

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1555935/+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 1507957] Re: Huawei E3372 LTE modem on 15.10 works only when connecting via wvdial and not network-manager

[dennis]

** Attachment added: "systemctl status ModemManager.service"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1507957/+attachment/4580833/+files/ModemManager.txt

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

Title:
  Huawei E3372 LTE modem on 15.10 works only when connecting via wvdial
  and not network-manager

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  If you plug the modem first time after booting, it cannot connect.
  Hovewer, after you unplug it and plug it again, it works like a charm.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-30-generic 3.19.0-30.34
  ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cysioland   2089 F pulseaudio
   /dev/snd/controlC0:  cysioland   2089 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Oct 20 11:28:10 2015
  HibernationDevice: RESUME=UUID=ed44c356-6a11-447b-94bc-88d54b0ead64
  InstallationDate: Installed on 2014-10-14 (370 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Acer Extensa 5635G
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic 
root=UUID=31750940-1f18-4f57-8933-4f779556f31b ro quiet splash 
libata.allow_tpm=1
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-30-generic N/A
   linux-backports-modules-3.19.0-30-generic  N/A
   linux-firmware 1.143.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-05-23 (149 days ago)
  dmi.bios.date: 12/21/2009
  dmi.bios.vendor: Phoenix
  dmi.bios.version: V1.3311
  dmi.board.name: BA50-MV
  dmi.board.vendor: Acer
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvrV1.3311:bd12/21/2009:svnAcer:pnExtensa5635G:pvrNotApplicable:rvnAcer:rnBA50-MV:rvrNotApplicable:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5635G
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1507957/+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 1507957] Re: Huawei E3372 LTE modem on 15.10 works only when connecting via wvdial and not network-manager

[dennis]

** Attachment added: "verbose lsusb"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1507957/+attachment/4580832/+files/lsub_verbose.txt

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

Title:
  Huawei E3372 LTE modem on 15.10 works only when connecting via wvdial
  and not network-manager

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  If you plug the modem first time after booting, it cannot connect.
  Hovewer, after you unplug it and plug it again, it works like a charm.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-30-generic 3.19.0-30.34
  ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cysioland   2089 F pulseaudio
   /dev/snd/controlC0:  cysioland   2089 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Oct 20 11:28:10 2015
  HibernationDevice: RESUME=UUID=ed44c356-6a11-447b-94bc-88d54b0ead64
  InstallationDate: Installed on 2014-10-14 (370 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Acer Extensa 5635G
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic 
root=UUID=31750940-1f18-4f57-8933-4f779556f31b ro quiet splash 
libata.allow_tpm=1
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-30-generic N/A
   linux-backports-modules-3.19.0-30-generic  N/A
   linux-firmware 1.143.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-05-23 (149 days ago)
  dmi.bios.date: 12/21/2009
  dmi.bios.vendor: Phoenix
  dmi.bios.version: V1.3311
  dmi.board.name: BA50-MV
  dmi.board.vendor: Acer
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvrV1.3311:bd12/21/2009:svnAcer:pnExtensa5635G:pvrNotApplicable:rvnAcer:rnBA50-MV:rvrNotApplicable:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5635G
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1507957/+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 1507957] Re: Huawei E3372 LTE modem on 15.10 works only when connecting via wvdial and not network-manager

[dennis]

** Attachment added: "lsusb"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1507957/+attachment/4580831/+files/lsub.txt

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

Title:
  Huawei E3372 LTE modem on 15.10 works only when connecting via wvdial
  and not network-manager

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  If you plug the modem first time after booting, it cannot connect.
  Hovewer, after you unplug it and plug it again, it works like a charm.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-30-generic 3.19.0-30.34
  ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cysioland   2089 F pulseaudio
   /dev/snd/controlC0:  cysioland   2089 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Oct 20 11:28:10 2015
  HibernationDevice: RESUME=UUID=ed44c356-6a11-447b-94bc-88d54b0ead64
  InstallationDate: Installed on 2014-10-14 (370 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Acer Extensa 5635G
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic 
root=UUID=31750940-1f18-4f57-8933-4f779556f31b ro quiet splash 
libata.allow_tpm=1
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-30-generic N/A
   linux-backports-modules-3.19.0-30-generic  N/A
   linux-firmware 1.143.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-05-23 (149 days ago)
  dmi.bios.date: 12/21/2009
  dmi.bios.vendor: Phoenix
  dmi.bios.version: V1.3311
  dmi.board.name: BA50-MV
  dmi.board.vendor: Acer
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvrV1.3311:bd12/21/2009:svnAcer:pnExtensa5635G:pvrNotApplicable:rvnAcer:rnBA50-MV:rvrNotApplicable:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5635G
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1507957/+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 1507957] Re: Huawei E3372 LTE modem on 15.10 works only when connecting via wvdial and not network-manager

[dennis]

Hi,
using HUAWEI E3372 (Telekom Speedstick V).
Have the same Problem, that the Networkmanager do not work with the Stick.
Did not detect it.

see attach, some information about the system.


** Attachment added: "Verbose Mode lsusb"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1507957/+attachment/4580830/+files/lsub_verbose.txt

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

Title:
  Huawei E3372 LTE modem on 15.10 works only when connecting via wvdial
  and not network-manager

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  If you plug the modem first time after booting, it cannot connect.
  Hovewer, after you unplug it and plug it again, it works like a charm.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-30-generic 3.19.0-30.34
  ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cysioland   2089 F pulseaudio
   /dev/snd/controlC0:  cysioland   2089 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Oct 20 11:28:10 2015
  HibernationDevice: RESUME=UUID=ed44c356-6a11-447b-94bc-88d54b0ead64
  InstallationDate: Installed on 2014-10-14 (370 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Acer Extensa 5635G
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic 
root=UUID=31750940-1f18-4f57-8933-4f779556f31b ro quiet splash 
libata.allow_tpm=1
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-30-generic N/A
   linux-backports-modules-3.19.0-30-generic  N/A
   linux-firmware 1.143.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-05-23 (149 days ago)
  dmi.bios.date: 12/21/2009
  dmi.bios.vendor: Phoenix
  dmi.bios.version: V1.3311
  dmi.board.name: BA50-MV
  dmi.board.vendor: Acer
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvrV1.3311:bd12/21/2009:svnAcer:pnExtensa5635G:pvrNotApplicable:rvnAcer:rnBA50-MV:rvrNotApplicable:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5635G
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1507957/+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 1507957] Re: Huawei E3372 LTE modem on 15.10 works only when connecting via wvdial and not network-manager

[dennis]

** Attachment added: "Kernel Version"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1507957/+attachment/4580834/+files/kernel.txt

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

Title:
  Huawei E3372 LTE modem on 15.10 works only when connecting via wvdial
  and not network-manager

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  If you plug the modem first time after booting, it cannot connect.
  Hovewer, after you unplug it and plug it again, it works like a charm.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-30-generic 3.19.0-30.34
  ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cysioland   2089 F pulseaudio
   /dev/snd/controlC0:  cysioland   2089 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Oct 20 11:28:10 2015
  HibernationDevice: RESUME=UUID=ed44c356-6a11-447b-94bc-88d54b0ead64
  InstallationDate: Installed on 2014-10-14 (370 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Acer Extensa 5635G
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic 
root=UUID=31750940-1f18-4f57-8933-4f779556f31b ro quiet splash 
libata.allow_tpm=1
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-30-generic N/A
   linux-backports-modules-3.19.0-30-generic  N/A
   linux-firmware 1.143.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-05-23 (149 days ago)
  dmi.bios.date: 12/21/2009
  dmi.bios.vendor: Phoenix
  dmi.bios.version: V1.3311
  dmi.board.name: BA50-MV
  dmi.board.vendor: Acer
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvrV1.3311:bd12/21/2009:svnAcer:pnExtensa5635G:pvrNotApplicable:rvnAcer:rnBA50-MV:rvrNotApplicable:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5635G
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1507957/+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 1507957] Re: Huawei E3372 LTE modem on 15.10 works only when connecting via wvdial and not network-manager

[dennis]

** Attachment added: "lsmod"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1507957/+attachment/4580835/+files/lsmod.txt

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

Title:
  Huawei E3372 LTE modem on 15.10 works only when connecting via wvdial
  and not network-manager

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  If you plug the modem first time after booting, it cannot connect.
  Hovewer, after you unplug it and plug it again, it works like a charm.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-30-generic 3.19.0-30.34
  ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cysioland   2089 F pulseaudio
   /dev/snd/controlC0:  cysioland   2089 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Oct 20 11:28:10 2015
  HibernationDevice: RESUME=UUID=ed44c356-6a11-447b-94bc-88d54b0ead64
  InstallationDate: Installed on 2014-10-14 (370 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Acer Extensa 5635G
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic 
root=UUID=31750940-1f18-4f57-8933-4f779556f31b ro quiet splash 
libata.allow_tpm=1
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-30-generic N/A
   linux-backports-modules-3.19.0-30-generic  N/A
   linux-firmware 1.143.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-05-23 (149 days ago)
  dmi.bios.date: 12/21/2009
  dmi.bios.vendor: Phoenix
  dmi.bios.version: V1.3311
  dmi.board.name: BA50-MV
  dmi.board.vendor: Acer
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvrV1.3311:bd12/21/2009:svnAcer:pnExtensa5635G:pvrNotApplicable:rvnAcer:rnBA50-MV:rvrNotApplicable:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5635G
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1507957/+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 1544435] [NEW] messaging app - iMessage only text

[dennis]

Public bug reported:

Hello,
a fried of mine is Apple User, he send me a Message with a picture and text.
But only recive the text.

** Affects: messaging-app (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  messaging app - iMessage only text

Status in messaging-app package in Ubuntu:
  New

Bug description:
  Hello,
  a fried of mine is Apple User, he send me a Message with a picture and text.
  But only recive the text.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1544435/+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 1523100] Re: Alsa not detecting internal microphone [ALC255]Acer Aspire VN7-792G

[Dennis Marttinen]

This bug does at least affect all the Acer Aspire V Nitro series
laptops. Basically it affects every system, which has a Realtek ALC255
sound card and the internal microphone not directly connected to it
hardware wise. Once more, I have the Acer Aspire VN7-792G and the
suggestion in post #26 can't get the internal microphone working.

** Summary changed:

- Alsa not detecting internal microphone [ALC255]Acer Aspire VN7-792G
+ Alsa not detecting internal microphone [ALC255]

** Summary changed:

- Alsa not detecting internal microphone [ALC255]
+ Alsa not detecting internal microphone [ALC255] (Realtek)

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

Title:
  Alsa not detecting internal microphone [ALC255] (Realtek)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
  Aspire VN7-792G and noticed, that the internal microphone doesn't
  work. The computer has been released a couple of months ago and it's
  Intel Skylake -based with a Sunrise Point -based motherboard.

  INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
  detected. Currently using Ubuntu 16.04 for proper hardware support.

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

  The speakers are working fine, but both alsamixer and pavucontrol
  (Pulseaudio Volume Control) raport the unplugged external microphone
  connector as the only sound input.

  I have tried many of the alsa model configurations (options snd-hda-
  intel model=something) without success, alsa finds only the microphone
  jack, which works fine when I plug an external microphone in it.

  Here's some info:

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
  HD Audio (rev 31)

  cat /proc/asound/cards:

  0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 128

  And a clip from dmesg | grep snd:

  [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [3.047514] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a

  One problem is that I can't find any model options (options snd-hda-
  intel model=something) or other parameters for the card's model
  (ALC255), I suppose this issue is relatively new.

  /Dennis
  --- 
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1180 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-11-11 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151110)
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  xenial
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-792G
  dmi.board.vendor: Acer
  dmi.board.version: V1.02
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02:
  dmi.product.name: Aspire VN7-792G
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+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 1523100] Re: Alsa not detecting internal microphone [ALC255]

[Dennis Marttinen]

The suggested fix in Raymond's post #26 doesn't work. This computer has
no combined audio port (now tested), and enabling dell-headset-multi
disables the separate external microphone port as well. Internal
microphone still not recognized.

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

Title:
  Alsa not detecting internal microphone [ALC255]

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
  Aspire VN7-792G and noticed, that the internal microphone doesn't
  work. The computer has been released a couple of months ago and it's
  Intel Skylake -based with a Sunrise Point -based motherboard.

  INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
  detected. Currently using Ubuntu 16.04 for proper hardware support.

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

  The speakers are working fine, but both alsamixer and pavucontrol
  (Pulseaudio Volume Control) raport the unplugged external microphone
  connector as the only sound input.

  I have tried many of the alsa model configurations (options snd-hda-
  intel model=something) without success, alsa finds only the microphone
  jack, which works fine when I plug an external microphone in it.

  Here's some info:

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
  HD Audio (rev 31)

  cat /proc/asound/cards:

  0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 128

  And a clip from dmesg | grep snd:

  [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [3.047514] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a

  One problem is that I can't find any model options (options snd-hda-
  intel model=something) or other parameters for the card's model
  (ALC255), I suppose this issue is relatively new.

  /Dennis
  --- 
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1180 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-11-11 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151110)
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  xenial
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-792G
  dmi.board.vendor: Acer
  dmi.board.version: V1.02
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02:
  dmi.product.name: Aspire VN7-792G
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+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 1523100] Re: Alsa not detecting internal microphone [ALC255]

[Dennis Marttinen]

I see, if support has been added, can I enable/try it somehow?

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

Title:
  Alsa not detecting internal microphone [ALC255]

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
  Aspire VN7-792G and noticed, that the internal microphone doesn't
  work. The computer has been released a couple of months ago and it's
  Intel Skylake -based with a Sunrise Point -based motherboard.

  INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
  detected. Currently using Ubuntu 16.04 for proper hardware support.

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

  The speakers are working fine, but both alsamixer and pavucontrol
  (Pulseaudio Volume Control) raport the unplugged external microphone
  connector as the only sound input.

  I have tried many of the alsa model configurations (options snd-hda-
  intel model=something) without success, alsa finds only the microphone
  jack, which works fine when I plug an external microphone in it.

  Here's some info:

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
  HD Audio (rev 31)

  cat /proc/asound/cards:

  0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 128

  And a clip from dmesg | grep snd:

  [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [3.047514] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a

  One problem is that I can't find any model options (options snd-hda-
  intel model=something) or other parameters for the card's model
  (ALC255), I suppose this issue is relatively new.

  /Dennis
  --- 
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1180 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-11-11 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151110)
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  xenial
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-792G
  dmi.board.vendor: Acer
  dmi.board.version: V1.02
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02:
  dmi.product.name: Aspire VN7-792G
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+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 1523100] Re: Alsa not detecting internal microphone [ALC255]

[Dennis Marttinen]

Barry,

1. There is no real benefit of 16.04, as it now has an older kernel
(4.3) than is available for wily (4.4). It once had better Intel HD
graphics support, but now the support has landed in 15.10. I'm now
running Ubuntu 15.10 too.

2. I've already tried node 0x19 for the internal microphone, but it
doesn't work (either I hear nothing or just plain white noise).

3. I'm not sure about the combined mic/headset jack. If they would have
integrated one in this PC, why would there then be a separate microphone
jack?

Raymond, I tested the internal mic using both sound recorder and cheese
and tried the stereo channels separately and together (using
pavucontrol) while going through the nodes in hdajackretask. You have a
point with the phasing, I might go through the nodes again just to make
sure, as I might have forgotten to try the channels separately on some
nodes :)

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

Title:
  Alsa not detecting internal microphone [ALC255]

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
  Aspire VN7-792G and noticed, that the internal microphone doesn't
  work. The computer has been released a couple of months ago and it's
  Intel Skylake -based with a Sunrise Point -based motherboard.

  INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
  detected. Currently using Ubuntu 16.04 for proper hardware support.

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

  The speakers are working fine, but both alsamixer and pavucontrol
  (Pulseaudio Volume Control) raport the unplugged external microphone
  connector as the only sound input.

  I have tried many of the alsa model configurations (options snd-hda-
  intel model=something) without success, alsa finds only the microphone
  jack, which works fine when I plug an external microphone in it.

  Here's some info:

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
  HD Audio (rev 31)

  cat /proc/asound/cards:

  0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 128

  And a clip from dmesg | grep snd:

  [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [3.047514] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a

  One problem is that I can't find any model options (options snd-hda-
  intel model=something) or other parameters for the card's model
  (ALC255), I suppose this issue is relatively new.

  /Dennis
  --- 
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1180 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-11-11 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151110)
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  xenial
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-792G
  dmi.board.vendor: Acer
  dmi.board.version: V1.02
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02:
  dmi.product.name: Aspire VN7-792G
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+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 1523100] Re: Alsa not detecting internal microphone [ALC255]

[Dennis Marttinen]

I've gone through the nodes, now making sure to test each channel
separately, but still nothing. Anything else we could try? I'm pretty
sure the microphone is not in the Realtec ALC255 protocol, but still
connected to the Intel sound card.

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

Title:
  Alsa not detecting internal microphone [ALC255]

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
  Aspire VN7-792G and noticed, that the internal microphone doesn't
  work. The computer has been released a couple of months ago and it's
  Intel Skylake -based with a Sunrise Point -based motherboard.

  INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
  detected. Currently using Ubuntu 16.04 for proper hardware support.

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

  The speakers are working fine, but both alsamixer and pavucontrol
  (Pulseaudio Volume Control) raport the unplugged external microphone
  connector as the only sound input.

  I have tried many of the alsa model configurations (options snd-hda-
  intel model=something) without success, alsa finds only the microphone
  jack, which works fine when I plug an external microphone in it.

  Here's some info:

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
  HD Audio (rev 31)

  cat /proc/asound/cards:

  0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 128

  And a clip from dmesg | grep snd:

  [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [3.047514] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a

  One problem is that I can't find any model options (options snd-hda-
  intel model=something) or other parameters for the card's model
  (ALC255), I suppose this issue is relatively new.

  /Dennis
  --- 
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1180 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-11-11 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151110)
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  xenial
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-792G
  dmi.board.vendor: Acer
  dmi.board.version: V1.02
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02:
  dmi.product.name: Aspire VN7-792G
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+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 1523100] Re: Alsa not detecting internal microphone [ALC255]

[Dennis Marttinen]

I've now gone through all the nodes (even unconnected ones) where any
kind of input source was possible and set them to internal mic one after
another, put on a boot override and rebooted every time. Some pins have
white noise, others nothing at all.

If this helps, on the side of Windows, device manager reports there to
be an "Intel Smart Sound Technology" device on which the "Realtek High
Definition Audio" device and the "Microphone Array" are located.

I think this means, that the microphone isn't connected to the Realtek
codec at all, but directly to the mysterious "Intel Smart Sound
Technology" device. Even the Realtek HD Audio Manager sees only the
external microphone jack and doesn't know about the internal one.

/Dennis

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

Title:
  Alsa not detecting internal microphone [ALC255]

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
  Aspire VN7-792G and noticed, that the internal microphone doesn't
  work. The computer has been released a couple of months ago and it's
  Intel Skylake -based with a Sunrise Point -based motherboard.

  INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
  detected. Currently using Ubuntu 16.04 for proper hardware support.

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

  The speakers are working fine, but both alsamixer and pavucontrol
  (Pulseaudio Volume Control) raport the unplugged external microphone
  connector as the only sound input.

  I have tried many of the alsa model configurations (options snd-hda-
  intel model=something) without success, alsa finds only the microphone
  jack, which works fine when I plug an external microphone in it.

  Here's some info:

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
  HD Audio (rev 31)

  cat /proc/asound/cards:

  0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 128

  And a clip from dmesg | grep snd:

  [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [3.047514] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a

  One problem is that I can't find any model options (options snd-hda-
  intel model=something) or other parameters for the card's model
  (ALC255), I suppose this issue is relatively new.

  /Dennis
  --- 
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1180 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-11-11 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151110)
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  xenial
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-792G
  dmi.board.vendor: Acer
  dmi.board.version: V1.02
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02:
  dmi.product.name: Aspire VN7-792G
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+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 1523100] Re: Alsa not detecting internal microphone [ALC255]

[Dennis Marttinen]

Hi Raymond,

switching to internal mic on node 0x12 doesn't work, the channel only
has white noise (the sound you hear from an untuned radio). I'm now
going to go through all the unconnected pins in hdajackretask to see if
one of them works.

/Dennis

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

Title:
  Alsa not detecting internal microphone [ALC255]

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
  Aspire VN7-792G and noticed, that the internal microphone doesn't
  work. The computer has been released a couple of months ago and it's
  Intel Skylake -based with a Sunrise Point -based motherboard.

  INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
  detected. Currently using Ubuntu 16.04 for proper hardware support.

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

  The speakers are working fine, but both alsamixer and pavucontrol
  (Pulseaudio Volume Control) raport the unplugged external microphone
  connector as the only sound input.

  I have tried many of the alsa model configurations (options snd-hda-
  intel model=something) without success, alsa finds only the microphone
  jack, which works fine when I plug an external microphone in it.

  Here's some info:

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
  HD Audio (rev 31)

  cat /proc/asound/cards:

  0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 128

  And a clip from dmesg | grep snd:

  [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [3.047514] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a

  One problem is that I can't find any model options (options snd-hda-
  intel model=something) or other parameters for the card's model
  (ALC255), I suppose this issue is relatively new.

  /Dennis
  --- 
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1180 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-11-11 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151110)
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  xenial
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-792G
  dmi.board.vendor: Acer
  dmi.board.version: V1.02
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02:
  dmi.product.name: Aspire VN7-792G
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+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 1523100] Re: Alsa not detecting internal microphone [ALC255]

[Dennis Marttinen]

@Raymond (superquad-vortex2)

I don't think the jack is a multifuntion one, but even if it is,
plugging the external microphone in or out doesn't change anything. The
computer has a separate headphone/SPDIF jack next to the microphone
input.

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

Title:
  Alsa not detecting internal microphone [ALC255]

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
  Aspire VN7-792G and noticed, that the internal microphone doesn't
  work. The computer has been released a couple of months ago and it's
  Intel Skylake -based with a Sunrise Point -based motherboard.

  INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
  detected. Currently using Ubuntu 16.04 for proper hardware support.

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

  The speakers are working fine, but both alsamixer and pavucontrol
  (Pulseaudio Volume Control) raport the unplugged external microphone
  connector as the only sound input.

  I have tried many of the alsa model configurations (options snd-hda-
  intel model=something) without success, alsa finds only the microphone
  jack, which works fine when I plug an external microphone in it.

  Here's some info:

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
  HD Audio (rev 31)

  cat /proc/asound/cards:

  0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 128

  And a clip from dmesg | grep snd:

  [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [3.047514] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a

  One problem is that I can't find any model options (options snd-hda-
  intel model=something) or other parameters for the card's model
  (ALC255), I suppose this issue is relatively new.

  /Dennis
  --- 
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1180 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-11-11 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151110)
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  xenial
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-792G
  dmi.board.vendor: Acer
  dmi.board.version: V1.02
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02:
  dmi.product.name: Aspire VN7-792G
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+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 1523100] [NEW] Alsa not detecting internal microphone [ALC255]

[Dennis Marttinen]

Public bug reported:

I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
Aspire VN7-792G and noticed, that the internal microphone doesn't work.
The computer has been released a couple of months ago and it's Intel
Skylake -based with a Sunrise Point -based motherboard.

INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
detected. Currently using Ubuntu 16.04 for proper hardware support.

Alsa reports the audio device to be:

Card: HDA Intel PCH
Chip: Intel Skylake HDMI

The speakers are working fine, but both alsamixer and pavucontrol
(Pulseaudio Volume Control) raport the unplugged external microphone
connector as the only sound input.

I have tried many of the alsa model configurations (options snd-hda-
intel model=something) without success, alsa finds only the microphone
jack, which works fine when I plug an external microphone in it.

Here's some info:

lspci | grep -I audio:

00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
HD Audio (rev 31)

cat /proc/asound/cards:

0 [PCH]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0x8432 irq 128

And a clip from dmesg | grep snd:

[3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
[3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
[3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs:
[3.047514] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a

One problem is that I can't find any model options (options snd-hda-
intel model=something) or other parameters for the card's model
(ALC255), I suppose this issue is relatively new.

/Dennis
--- 
ApportVersion: 2.19.2-0ubuntu6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dennis 1180 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 16.04
InstallationDate: Installed on 2015-11-11 (23 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151110)
Package: alsa-driver (not installed)
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
Tags:  xenial
Uname: Linux 4.2.0-19-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 09/25/2015
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.02
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Aspire VN7-792G
dmi.board.vendor: Acer
dmi.board.version: V1.02
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.02
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02:
dmi.product.name: Aspire VN7-792G
dmi.product.version: V1.02
dmi.sys.vendor: Acer

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


** Tags: apport-collected wily xenial

** Tags added: apport-collected xenial

** Description changed:

  I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
  Aspire VN7-792G and noticed, that the internal microphone doesn't work.
  The computer has been released a couple of months ago and it's Intel
  Skylake -based with a Sunrise Point -based motherboard.
  
  INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
  detected. Currently using Ubuntu 16.04 for proper hardware support.
  
  Alsa reports the audio device to be:
  
  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI
  
  The speakers are working fine, but both alsamixer and pavucontrol
  (Pulseaudio Volume Control) raport the unplugged external microphone
  connector as the only sound input.
  
  I have tried many of the alsa model configurations (options snd-hda-
  intel model=something) without success, alsa finds only the microphone
  jack, which works fine when I plug an external microphone in it.
  
  Here's some info:
  
  lspci | grep -I audio:
  
  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
  HD Audio (rev 31)
  
  cat /proc/asound/cards:
  
  0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 128
  
  And a clip from dmesg | grep snd:
  
  [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0

[Touch-packages] [Bug 1523100] AlsaInfo.txt

[Dennis Marttinen]

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1523100/+attachment/4530128/+files/AlsaInfo.txt

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

Title:
  Alsa not detecting internal microphone [ALC255]

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
  Aspire VN7-792G and noticed, that the internal microphone doesn't
  work. The computer has been released a couple of months ago and it's
  Intel Skylake -based with a Sunrise Point -based motherboard.

  INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
  detected. Currently using Ubuntu 16.04 for proper hardware support.

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

  The speakers are working fine, but both alsamixer and pavucontrol
  (Pulseaudio Volume Control) raport the unplugged external microphone
  connector as the only sound input.

  I have tried many of the alsa model configurations (options snd-hda-
  intel model=something) without success, alsa finds only the microphone
  jack, which works fine when I plug an external microphone in it.

  Here's some info:

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
  HD Audio (rev 31)

  cat /proc/asound/cards:

  0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 128

  And a clip from dmesg | grep snd:

  [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [3.047514] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a

  One problem is that I can't find any model options (options snd-hda-
  intel model=something) or other parameters for the card's model
  (ALC255), I suppose this issue is relatively new.

  /Dennis
  --- 
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1180 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-11-11 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151110)
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  xenial
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-792G
  dmi.board.vendor: Acer
  dmi.board.version: V1.02
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02:
  dmi.product.name: Aspire VN7-792G
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+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 1523100] Re: Alsa not detecting internal microphone [ALC255]

[Dennis Marttinen]

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

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

Title:
  Alsa not detecting internal microphone [ALC255]

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
  Aspire VN7-792G and noticed, that the internal microphone doesn't
  work. The computer has been released a couple of months ago and it's
  Intel Skylake -based with a Sunrise Point -based motherboard.

  INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
  detected. Currently using Ubuntu 16.04 for proper hardware support.

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

  The speakers are working fine, but both alsamixer and pavucontrol
  (Pulseaudio Volume Control) raport the unplugged external microphone
  connector as the only sound input.

  I have tried many of the alsa model configurations (options snd-hda-
  intel model=something) without success, alsa finds only the microphone
  jack, which works fine when I plug an external microphone in it.

  Here's some info:

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
  HD Audio (rev 31)

  cat /proc/asound/cards:

  0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 128

  And a clip from dmesg | grep snd:

  [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [3.047514] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a

  One problem is that I can't find any model options (options snd-hda-
  intel model=something) or other parameters for the card's model
  (ALC255), I suppose this issue is relatively new.

  /Dennis
  --- 
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1180 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-11-11 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151110)
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  xenial
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-792G
  dmi.board.vendor: Acer
  dmi.board.version: V1.02
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02:
  dmi.product.name: Aspire VN7-792G
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+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 1523100] CurrentDmesg.txt

[Dennis Marttinen]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1523100/+attachment/4530129/+files/CurrentDmesg.txt

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

Title:
  Alsa not detecting internal microphone [ALC255]

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
  Aspire VN7-792G and noticed, that the internal microphone doesn't
  work. The computer has been released a couple of months ago and it's
  Intel Skylake -based with a Sunrise Point -based motherboard.

  INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
  detected. Currently using Ubuntu 16.04 for proper hardware support.

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

  The speakers are working fine, but both alsamixer and pavucontrol
  (Pulseaudio Volume Control) raport the unplugged external microphone
  connector as the only sound input.

  I have tried many of the alsa model configurations (options snd-hda-
  intel model=something) without success, alsa finds only the microphone
  jack, which works fine when I plug an external microphone in it.

  Here's some info:

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
  HD Audio (rev 31)

  cat /proc/asound/cards:

  0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 128

  And a clip from dmesg | grep snd:

  [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [3.047514] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a

  One problem is that I can't find any model options (options snd-hda-
  intel model=something) or other parameters for the card's model
  (ALC255), I suppose this issue is relatively new.

  /Dennis
  --- 
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1180 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-11-11 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151110)
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  xenial
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-792G
  dmi.board.vendor: Acer
  dmi.board.version: V1.02
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02:
  dmi.product.name: Aspire VN7-792G
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+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 1523100] ProcEnviron.txt

[Dennis Marttinen]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1523100/+attachment/4530131/+files/ProcEnviron.txt

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

Title:
  Alsa not detecting internal microphone [ALC255]

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
  Aspire VN7-792G and noticed, that the internal microphone doesn't
  work. The computer has been released a couple of months ago and it's
  Intel Skylake -based with a Sunrise Point -based motherboard.

  INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
  detected. Currently using Ubuntu 16.04 for proper hardware support.

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

  The speakers are working fine, but both alsamixer and pavucontrol
  (Pulseaudio Volume Control) raport the unplugged external microphone
  connector as the only sound input.

  I have tried many of the alsa model configurations (options snd-hda-
  intel model=something) without success, alsa finds only the microphone
  jack, which works fine when I plug an external microphone in it.

  Here's some info:

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
  HD Audio (rev 31)

  cat /proc/asound/cards:

  0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 128

  And a clip from dmesg | grep snd:

  [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [3.047514] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a

  One problem is that I can't find any model options (options snd-hda-
  intel model=something) or other parameters for the card's model
  (ALC255), I suppose this issue is relatively new.

  /Dennis
  --- 
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1180 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-11-11 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151110)
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  xenial
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-792G
  dmi.board.vendor: Acer
  dmi.board.version: V1.02
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02:
  dmi.product.name: Aspire VN7-792G
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+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 1523100] JournalErrors.txt

[Dennis Marttinen]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1523100/+attachment/4530130/+files/JournalErrors.txt

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

Title:
  Alsa not detecting internal microphone [ALC255]

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
  Aspire VN7-792G and noticed, that the internal microphone doesn't
  work. The computer has been released a couple of months ago and it's
  Intel Skylake -based with a Sunrise Point -based motherboard.

  INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
  detected. Currently using Ubuntu 16.04 for proper hardware support.

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

  The speakers are working fine, but both alsamixer and pavucontrol
  (Pulseaudio Volume Control) raport the unplugged external microphone
  connector as the only sound input.

  I have tried many of the alsa model configurations (options snd-hda-
  intel model=something) without success, alsa finds only the microphone
  jack, which works fine when I plug an external microphone in it.

  Here's some info:

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
  HD Audio (rev 31)

  cat /proc/asound/cards:

  0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 128

  And a clip from dmesg | grep snd:

  [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [3.047514] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a

  One problem is that I can't find any model options (options snd-hda-
  intel model=something) or other parameters for the card's model
  (ALC255), I suppose this issue is relatively new.

  /Dennis
  --- 
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1180 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-11-11 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151110)
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  xenial
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-792G
  dmi.board.vendor: Acer
  dmi.board.version: V1.02
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02:
  dmi.product.name: Aspire VN7-792G
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+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 1523100] PulseList.txt

[Dennis Marttinen]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1523100/+attachment/4530132/+files/PulseList.txt

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

Title:
  Alsa not detecting internal microphone [ALC255]

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
  Aspire VN7-792G and noticed, that the internal microphone doesn't
  work. The computer has been released a couple of months ago and it's
  Intel Skylake -based with a Sunrise Point -based motherboard.

  INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
  detected. Currently using Ubuntu 16.04 for proper hardware support.

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

  The speakers are working fine, but both alsamixer and pavucontrol
  (Pulseaudio Volume Control) raport the unplugged external microphone
  connector as the only sound input.

  I have tried many of the alsa model configurations (options snd-hda-
  intel model=something) without success, alsa finds only the microphone
  jack, which works fine when I plug an external microphone in it.

  Here's some info:

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
  HD Audio (rev 31)

  cat /proc/asound/cards:

  0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 128

  And a clip from dmesg | grep snd:

  [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [3.047514] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a

  One problem is that I can't find any model options (options snd-hda-
  intel model=something) or other parameters for the card's model
  (ALC255), I suppose this issue is relatively new.

  /Dennis
  --- 
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1180 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-11-11 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151110)
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  xenial
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-792G
  dmi.board.vendor: Acer
  dmi.board.version: V1.02
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02:
  dmi.product.name: Aspire VN7-792G
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+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 1509916] [NEW] Duplicate key error when archiving

[Dennis O'Flaherty]

Public bug reported:

media scanner daemon crashes when I log into my machine (desktop, wily)

Mediascanner service starting at 2015-10-25 11:22:08.

terminate called after throwing an instance of 'std::runtime_error'
  what():  UNIQUE constraint failed: media_attic.id
Aborted (core dumped)


The service is trying to run this query in archiveItems:

const char *templ = R"(BEGIN TRANSACTION;
INSERT INTO media_attic SELECT * FROM media WHERE filename LIKE %s;
DELETE FROM media WHERE filename LIKE %s;
COMMIT;
)";

If I move/remove mediastore.db, the service runs again and catalogs
music I've added since my last run.

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

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

Title:
  Duplicate key error when archiving

Status in mediascanner2 package in Ubuntu:
  New

Bug description:
  media scanner daemon crashes when I log into my machine (desktop,
  wily)

  Mediascanner service starting at 2015-10-25 11:22:08.

  terminate called after throwing an instance of 'std::runtime_error'
what():  UNIQUE constraint failed: media_attic.id
  Aborted (core dumped)

  
  The service is trying to run this query in archiveItems:

  const char *templ = R"(BEGIN TRANSACTION;
  INSERT INTO media_attic SELECT * FROM media WHERE filename LIKE %s;
  DELETE FROM media WHERE filename LIKE %s;
  COMMIT;
  )";

  If I move/remove mediastore.db, the service runs again and catalogs
  music I've added since my last run.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1509916/+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 1505461] [NEW] Expose LED color setting

[Dennis O'Flaherty]

Public bug reported:

It would be nice you could change the color the LED blinks when you have
notifications.  If not through a GUI, at least through gsettings.

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

** Branch linked: lp:~doflah/unity8/led_color

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

Title:
  Expose LED color setting

Status in unity8 package in Ubuntu:
  New

Bug description:
  It would be nice you could change the color the LED blinks when you
  have notifications.  If not through a GUI, at least through gsettings.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1505461/+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 1504387]

[Dennis Schridde]

The KDE problem is indeed fixed in Mesa 11.0.3. Thanks!

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

Title:
  [regression] Software client windows appear all-black on wily desktop

Status in Mesa:
  Confirmed
Status in Mir:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  [regression] Software client windows appear all-black, as of today on
  wily desktop.

  Although Mir has not changed. It seems like some other part of the OS
  is broken.

  $ sudo mir_proving_server &
  $ sudo mir_demo_client_progressbar

  The bug appeared in:
  mesa (11.0.2-1ubuntu3) wily; urgency=medium

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1504387/+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 1502681] [NEW] Tables in scopes are restricted to two columns

[Dennis O'Flaherty]

Public bug reported:

The column count of PreviewWidget.gridLayout is hard coded to two.  I'd
expect that providing it an n by m matrix (VariantArray of
VariantArrays) it would render an n by m table.

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

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

Title:
  Tables in scopes are restricted to two columns

Status in unity8 package in Ubuntu:
  New

Bug description:
  The column count of PreviewWidget.gridLayout is hard coded to two.
  I'd expect that providing it an n by m matrix (VariantArray of
  VariantArrays) it would render an n by m table.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1502681/+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 1496713] [NEW] package slapd 2.4.31-1+nmu2ubuntu8.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Dennis Leeuw]

Public bug reported:

The only thing that seems to fail is the start:

Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
Setting up slapd (2.4.31-1+nmu2ubuntu8.2) ...
  Backing up /etc/ldap/slapd.conf in 
/var/backups/slapd-2.4.31-1+nmu2ubuntu8.1... done.
 * Starting OpenLDAP slapd  

 [fail] 
invoke-rc.d: initscript slapd, action "start" failed.

This seems to be the problem:
/usr/sbin/slapd -h ldap:/// ldapi:/// -g openldap -u openldap -f 
/etc/ldap/slapd.conf

If I change it to:
/usr/sbin/slapd -h ldap:/// -g openldap -u openldap -f /etc/ldap/slapd.conf

All works fine.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: slapd 2.4.31-1+nmu2ubuntu8.2
ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
Uname: Linux 3.13.0-63-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.13
Architecture: amd64
Date: Thu Sep 17 09:12:10 2015
DuplicateSignature: package:slapd:2.4.31-1+nmu2ubuntu8.2:subprocess installed 
post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2014-10-28 (323 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.4
 apt  1.0.1ubuntu2.10
SourcePackage: openldap
Title: package slapd 2.4.31-1+nmu2ubuntu8.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apparmor.d.usr.sbin.slapd: [modified]
modified.conffile..etc.ldap.schema.README: [deleted]
modified.conffile..etc.ldap.schema.collective.ldif: [deleted]
modified.conffile..etc.ldap.schema.collective.schema: [deleted]
modified.conffile..etc.ldap.schema.corba.ldif: [deleted]
modified.conffile..etc.ldap.schema.corba.schema: [modified]
modified.conffile..etc.ldap.schema.core.ldif: [deleted]
modified.conffile..etc.ldap.schema.core.schema: [modified]
modified.conffile..etc.ldap.schema.cosine.ldif: [deleted]
modified.conffile..etc.ldap.schema.cosine.schema: [modified]
modified.conffile..etc.ldap.schema.duaconf.ldif: [deleted]
modified.conffile..etc.ldap.schema.duaconf.schema: [deleted]
modified.conffile..etc.ldap.schema.dyngroup.ldif: [deleted]
modified.conffile..etc.ldap.schema.dyngroup.schema: [modified]
modified.conffile..etc.ldap.schema.inetorgperson.ldif: [deleted]
modified.conffile..etc.ldap.schema.inetorgperson.schema: [modified]
modified.conffile..etc.ldap.schema.java.ldif: [deleted]
modified.conffile..etc.ldap.schema.java.schema: [modified]
modified.conffile..etc.ldap.schema.ldapns.schema: [deleted]
modified.conffile..etc.ldap.schema.misc.ldif: [deleted]
modified.conffile..etc.ldap.schema.misc.schema: [modified]
modified.conffile..etc.ldap.schema.nis.ldif: [deleted]
modified.conffile..etc.ldap.schema.nis.schema: [modified]
modified.conffile..etc.ldap.schema.openldap.ldif: [deleted]
modified.conffile..etc.ldap.schema.openldap.schema: [modified]
modified.conffile..etc.ldap.schema.pmi.ldif: [deleted]
modified.conffile..etc.ldap.schema.pmi.schema: [deleted]
modified.conffile..etc.ldap.schema.ppolicy.ldif: [deleted]
modified.conffile..etc.ldap.schema.ppolicy.schema: [modified]
mtime.conffile..etc.apparmor.d.usr.sbin.slapd: 2015-07-01T13:37:11.436564
mtime.conffile..etc.ldap.schema.corba.schema: 2015-07-01T13:12:33.356559
mtime.conffile..etc.ldap.schema.core.schema: 2015-07-01T13:12:33.360559
mtime.conffile..etc.ldap.schema.cosine.schema: 2015-07-01T13:12:33.360559
mtime.conffile..etc.ldap.schema.dyngroup.schema: 2015-07-01T13:12:33.364559
mtime.conffile..etc.ldap.schema.inetorgperson.schema: 2015-07-01T13:12:33.364559
mtime.conffile..etc.ldap.schema.java.schema: 2015-07-01T13:12:33.368559
mtime.conffile..etc.ldap.schema.misc.schema: 2015-07-01T13:12:33.412559
mtime.conffile..etc.ldap.schema.nis.schema: 2015-07-01T13:12:33.412559
mtime.conffile..etc.ldap.schema.openldap.schema: 2015-07-01T13:12:33.416559
mtime.conffile..etc.ldap.schema.ppolicy.schema: 2015-07-01T13:12:33.420559

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


** Tags: amd64 apport-package trusty

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

Title:
  package slapd 2.4.31-1+nmu2ubuntu8.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openldap package in Ubuntu:
  New

Bug description:
  The only thing that seems to fail is the start:

  Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
  Setting up slapd (2.4.31-1+nmu2ubuntu8.2) ...
Backing up /etc/ldap/slapd.conf in 
/var/backups/slapd-2.4.31-1+nmu2ubuntu8.1... done.
   * Starting OpenLDAP slapd 

[Touch-packages] [Bug 1478403] Re: Messages appear from the wrong sender

[Dennis O'Flaherty]

** Also affects: dialer-app
   Importance: Undecided
   Status: New

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

Title:
  Messages appear from the wrong sender

Status in dialer-app:
  New
Status in history-service:
  New
Status in telepathy-ofono:
  New
Status in messaging-app package in Ubuntu:
  New

Bug description:
  After updating to OTA5 on mako (#21), I have been seeing text messages
  that are from one person, but appear as sent from someone else.  The
  first one was obvious, since it came from the T-Mobile voicemail
  number, but the next time was more subtle, since it came from a
  different friend's number.  I sent myself a message while running
  dbus-monitor to see where it went wrong:

  signal sender=:1.13 - dest=(null destination) serial=665 
path=/org/freedesktop/Telepathy/Connection/ofono/ofono/_14bb200/_1515120; 
interface=org.freedesktop.Telepathy.Channel.Interface.Messages; 
member=MessageReceived
 array [
array [
   dict entry(
  string message-received
  variantuint32 1437926656
   )
   dict entry(
  string message-sender
  variantuint32 2
   )
   dict entry(
  string message-sender-id
  variantstring correct number
   )
   dict entry(
  string message-token
  variantstring 2015-07-26T12:04:14-0400-1
   )
   dict entry(
  string message-type
  variantuint32 0
   )
   dict entry(
  string pending-message-id
  variantuint32 0
   )
]
array [
   dict entry(
  string content
  variantstring sample message
   )
   dict entry(
  string content-type
  variantstring text/plain
   )
]
 ]

  
  The telepathy-ofono message looks okay, but the message emitted by 
history-daemon is wrong:

  signal sender=:1.92 - dest=(null destination) serial=560 
path=/com/canonical/HistoryService; interface=com.canonical.HistoryService; 
member=EventsAdded
 array [
array [
   dict entry(
  string accountId
  variantstring ofono/ofono/account0
   )
   dict entry(
  string attachments
  variantarray [
 ]
   )
   dict entry(
  string eventId
  variantstring 2015-07-26T12:04:14-0400-1
   )
   dict entry(
  string message
  variantstring sample message
   )
   dict entry(
  string messageStatus
  variantint32 0
   )
   dict entry(
  string messageType
  variantint32 0
   )
   dict entry(
  string newEvent
  variantboolean true
   )
   dict entry(
  string participants
  variantarray [
string wrong number!
 ]
   )
   dict entry(
  string readTimestamp
  variantstring 
   )
   dict entry(
  string senderId
  variantstring same wrong number!
   )
   dict entry(
  string subject
  variantstring 
   )
   dict entry(
  string threadId
  variantstring same wrong number!
   )
   dict entry(
  string timestamp
  variantstring 2015-07-26T12:04:16.000
   )
   dict entry(
  string type
  variantint32 0
   )
]
 ]

To manage notifications about this bug go to:
https://bugs.launchpad.net/dialer-app/+bug/1478403/+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 1478403] Re: Messages appear from the wrong sender

[Dennis O'Flaherty]

I thought since I had gotten a text message from the voicemail number, I
might be able to cause false voicemail history as well, but I opened the
dialer-app and it froze, then crashed.  I opened it several more times
and it crashed each time.  Attached is the log with phone numbers
scrubbed.  It contains a number of errors regarding contact handles, so
I suspect the crash is related to the text message sender error.

** Attachment added: application-legacy-dialer-app-.log
   
https://bugs.launchpad.net/telepathy-ofono/+bug/1478403/+attachment/4434401/+files/application-legacy-dialer-app-.log

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

Title:
  Messages appear from the wrong sender

Status in history-service:
  New
Status in telepathy-ofono:
  New
Status in messaging-app package in Ubuntu:
  New

Bug description:
  After updating to OTA5 on mako (#21), I have been seeing text messages
  that are from one person, but appear as sent from someone else.  The
  first one was obvious, since it came from the T-Mobile voicemail
  number, but the next time was more subtle, since it came from a
  different friend's number.  I sent myself a message while running
  dbus-monitor to see where it went wrong:

  signal sender=:1.13 - dest=(null destination) serial=665 
path=/org/freedesktop/Telepathy/Connection/ofono/ofono/_14bb200/_1515120; 
interface=org.freedesktop.Telepathy.Channel.Interface.Messages; 
member=MessageReceived
 array [
array [
   dict entry(
  string message-received
  variantuint32 1437926656
   )
   dict entry(
  string message-sender
  variantuint32 2
   )
   dict entry(
  string message-sender-id
  variantstring correct number
   )
   dict entry(
  string message-token
  variantstring 2015-07-26T12:04:14-0400-1
   )
   dict entry(
  string message-type
  variantuint32 0
   )
   dict entry(
  string pending-message-id
  variantuint32 0
   )
]
array [
   dict entry(
  string content
  variantstring sample message
   )
   dict entry(
  string content-type
  variantstring text/plain
   )
]
 ]

  
  The telepathy-ofono message looks okay, but the message emitted by 
history-daemon is wrong:

  signal sender=:1.92 - dest=(null destination) serial=560 
path=/com/canonical/HistoryService; interface=com.canonical.HistoryService; 
member=EventsAdded
 array [
array [
   dict entry(
  string accountId
  variantstring ofono/ofono/account0
   )
   dict entry(
  string attachments
  variantarray [
 ]
   )
   dict entry(
  string eventId
  variantstring 2015-07-26T12:04:14-0400-1
   )
   dict entry(
  string message
  variantstring sample message
   )
   dict entry(
  string messageStatus
  variantint32 0
   )
   dict entry(
  string messageType
  variantint32 0
   )
   dict entry(
  string newEvent
  variantboolean true
   )
   dict entry(
  string participants
  variantarray [
string wrong number!
 ]
   )
   dict entry(
  string readTimestamp
  variantstring 
   )
   dict entry(
  string senderId
  variantstring same wrong number!
   )
   dict entry(
  string subject
  variantstring 
   )
   dict entry(
  string threadId
  variantstring same wrong number!
   )
   dict entry(
  string timestamp
  variantstring 2015-07-26T12:04:16.000
   )
   dict entry(
  string type
  variantint32 0
   )
]
 ]

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

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

[Touch-packages] [Bug 1478403] [NEW] Messages appear from the wrong sender

[Dennis O'Flaherty]

Public bug reported:

After updating to OTA5 on mako (#21), I have been seeing text messages
that are from one person, but appear as sent from someone else.  The
first one was obvious, since it came from the T-Mobile voicemail number,
but the next time was more subtle, since it came from a different
friend's number.  I sent myself a message while running dbus-monitor to
see where it went wrong:

signal sender=:1.13 - dest=(null destination) serial=665 
path=/org/freedesktop/Telepathy/Connection/ofono/ofono/_14bb200/_1515120; 
interface=org.freedesktop.Telepathy.Channel.Interface.Messages; 
member=MessageReceived
   array [
  array [
 dict entry(
string message-received
variantuint32 1437926656
 )
 dict entry(
string message-sender
variantuint32 2
 )
 dict entry(
string message-sender-id
variantstring correct number
 )
 dict entry(
string message-token
variantstring 2015-07-26T12:04:14-0400-1
 )
 dict entry(
string message-type
variantuint32 0
 )
 dict entry(
string pending-message-id
variantuint32 0
 )
  ]
  array [
 dict entry(
string content
variantstring sample message
 )
 dict entry(
string content-type
variantstring text/plain
 )
  ]
   ]


The telepathy-ofono message looks okay, but the message emitted by 
history-daemon is wrong:

signal sender=:1.92 - dest=(null destination) serial=560 
path=/com/canonical/HistoryService; interface=com.canonical.HistoryService; 
member=EventsAdded
   array [
  array [
 dict entry(
string accountId
variantstring ofono/ofono/account0
 )
 dict entry(
string attachments
variantarray [
   ]
 )
 dict entry(
string eventId
variantstring 2015-07-26T12:04:14-0400-1
 )
 dict entry(
string message
variantstring sample message
 )
 dict entry(
string messageStatus
variantint32 0
 )
 dict entry(
string messageType
variantint32 0
 )
 dict entry(
string newEvent
variantboolean true
 )
 dict entry(
string participants
variantarray [
  string wrong number!
   ]
 )
 dict entry(
string readTimestamp
variantstring 
 )
 dict entry(
string senderId
variantstring same wrong number!
 )
 dict entry(
string subject
variantstring 
 )
 dict entry(
string threadId
variantstring same wrong number!
 )
 dict entry(
string timestamp
variantstring 2015-07-26T12:04:16.000
 )
 dict entry(
string type
variantint32 0
 )
  ]
   ]

** Affects: history-service
 Importance: Undecided
 Status: New

** Affects: telepathy-ofono
 Importance: Undecided
 Status: New

** Affects: messaging-app (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: history-service
   Importance: Undecided
   Status: New

** Also affects: telepathy-ofono
   Importance: Undecided
   Status: New

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

Title:
  Messages appear from the wrong sender

Status in history-service:
  New
Status in telepathy-ofono:
  New
Status in messaging-app package in Ubuntu:
  New

Bug description:
  After updating to OTA5 on mako (#21), I have been seeing text messages
  that are from one person, but appear as sent from someone else.  The
  first one was obvious, since it came from the T-Mobile voicemail
  number, but the next time was more subtle, since it came from a
  different friend's number.  I sent myself a message while running
  dbus-monitor to see where it went wrong:

  signal sender=:1.13 - dest=(null destination) serial=665 
path=/org/freedesktop/Telepathy/Connection/ofono/ofono/_14bb200/_1515120; 
interface=org.freedesktop.Telepathy.Channel.Interface.Messages; 
member=MessageReceived
 array [
array [
   dict entry(
 

[Touch-packages] [Bug 1446007] Re: unity launcher fonts became extremely small after update

[Dennis Baudys]

I can confirm this. After upgrading from Ubuntu 12.04 to 14.04 the font
size (for the number of new emails) on the thunderbird icon in the unity
launcher became extremely small.

$ uname -a
Linux Dennis-PC 3.13.0-58-generic # 97-Ubuntu SMP Wed Jul 8 02:56:15 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux

Dennis

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

Title:
  unity launcher fonts became extremely small after update

Status in Unity:
  New
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Some applications such thunderbird and unity-mail have a counter at
  their icon in unity launcher.  In two computers with Ubuntu 14.04 the
  fonts of the counter became extremely small after a restart for no
  apparent reason.

  This has happened in two computers with completely different hardware
  and with a distance of about 1 month.

  Operating system: Ubuntu 14.04.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1446007/+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 1360403] Re: MMS does not work with T-Mobile US

[Dennis O'Flaherty]

It was a little bit of both but I made the changes to be able to
receive.  The only change I think I needed to make to send was to set
the context url, which I think is consistent with Sergio's comment #11.
It's a change i needed to make but it's a little bit of a hack in that
I'm not sure it's the correct fix.  I just know it works.

I just tried building from the github version and it seems the changes
in push.go are no longer necessary.  I still need to patch it to let
non-SMIL messages in, but I'm not sure if that's a normal event (MMS
from another phone) or if it's just because I'm using the smtp gateway
(MMS from e-mail) to test it.  I'm not an MMS expert, so it's mostly
just trial and error at this point.

I wasn't able to send or receive over wifi, I needed to switch the data
connection.  It also doesn't seem to try to receive again if you switch
after a failure which means you lose the message.

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

Title:
  MMS does not work with T-Mobile US

Status in the base for Ubuntu mobile products:
  Confirmed
Status in lxc-android-config package in Ubuntu:
  Triaged
Status in nuntium package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Confirmed
Status in ubuntu-download-manager package in Ubuntu:
  Confirmed

Bug description:
  My /var/lib/ofono/*/gprs file contains:

  [Settings]
  Powered=1
  RoamingAllowed=0

  [context1]
  Name=T-Mobile GPRS
  AccessPointName=fast.t-mobile.com
  Username=
  Password=
  Type=internet
  Protocol=ipv6
  MessageProxy=
  MessageCenter=http://mms.msg.eng.t-mobile.com/mms/wapenc

  I guess bug #1331813 is getting in the way of IPv6 working, so I was
  told to try 'Protocol=ip', but it doesn't work either.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1360403/+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 1360403] Re: MMS does not work with T-Mobile US

[Dennis O'Flaherty]

Jamie, I was able to get this working recently on my N4 using the dev
channel.  I patched nuntium (trunk, see attachment) to be able to
receive picture messages then I had to change some of my APN settings
with /usr/share/ofono/scripts to be able to send.  I don't use group
messages, but when I send an image to my phone through tmomail, it
receives it as a group message from my e-mail address and a blank
recipient.

** Attachment added: tmobile_mms
   
https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1360403/+attachment/4414101/+files/tmobile_mms

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

Title:
  MMS does not work with T-Mobile US

Status in the base for Ubuntu mobile products:
  Confirmed
Status in lxc-android-config package in Ubuntu:
  Triaged
Status in nuntium package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Confirmed
Status in ubuntu-download-manager package in Ubuntu:
  Confirmed

Bug description:
  My /var/lib/ofono/*/gprs file contains:

  [Settings]
  Powered=1
  RoamingAllowed=0

  [context1]
  Name=T-Mobile GPRS
  AccessPointName=fast.t-mobile.com
  Username=
  Password=
  Type=internet
  Protocol=ipv6
  MessageProxy=
  MessageCenter=http://mms.msg.eng.t-mobile.com/mms/wapenc

  I guess bug #1331813 is getting in the way of IPv6 working, so I was
  told to try 'Protocol=ip', but it doesn't work either.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1360403/+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 553533] Re: ubuntu-bug asks questions then exits

[Dennis Schridde]

 status: New → Invalid
 Outdated version

We believe this issue has been fixed in current versions of apport.
Please create a new report, should you still be experiencing it. would
have been more polite.

Adding Sorry for ignoring this report for five years. would have been
even better.

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

Title:
  ubuntu-bug asks questions then exits

Status in apport package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: apport

  When executing ubuntu-bug or apport-bug on the console, it starts to ask 
questions.
  1) I select other problem.
  2) Apports opens another window collecting problem information
  3) In the next question window I select other display-related problem
  4) Apport exits

  Additionaly it logs
  
  /usr/lib/pymodules/python2.6/lazr/restfulclient/__init__.py:19: UserWarning: 
Module launchpadlib was already imported from 
/usr/lib/pymodules/python2.6/launchpadlib/__init__.py, but 
/usr/lib/pymodules/python2.6 is being added to sys.path
import pkg_resources
  
  *before* asking the questions.

  I'd expect something useful to happen instead of step 4 above. E.g.
  asking which package is affected, opening bugs.launchpad.net with the
  already given information filled into a bugreporting for, something
  like that.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: apport 1.13.2-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.32-18.27-generic 2.6.32.10+drm33.1
  Uname: Linux 2.6.32-18-generic i686
  ApportLog:
   
  Architecture: i386
  Date: Thu Apr  1 21:46:05 2010
  InstallationMedia: Kubuntu-Netbook 10.04 Lucid Lynx - Beta i386 (20100318)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/553533/+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 1440294] Re: syncevolution - no export of tasks / memos Aquaris E4.5

[dennis]

no evenote account, save note local only

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

Title:
   syncevolution - no export of tasks / memos Aquaris E4.5

Status in syncevolution package in Ubuntu:
  New

Bug description:
  Phone: bq Aquaris E4.5 Ubuntu Edtion
  OS: Ubuntu 14.10(r20)
  SyncEvolution 1.5

  Can not export my Tasks and memos.
  Calendar and contacts export works!

  phablet@ubuntu-phablet:~$ syncevolution --print-databases
  CalDAV:
     select database via absolute URL, set username/password to scan, set 
syncURL to base URL if server does not support auto-discovery (path)

  CalDAVTodo:
     select database via absolute URL, set username/password to scan, set 
syncURL to base URL if server does not support auto-discovery (path)

  CalDAVJournal:
     select database via absolute URL, set username/password to scan, set 
syncURL to base URL if server does not support auto-discovery (path)

  CardDAV:
     select database via absolute URL, set username/password to scan, set 
syncURL to base URL if server does not support auto-discovery (path)

  Evolution Address Book = Evolution Contacts = evolution-contacts:
     Persönlich (system-address-book) default

  Evolution Calendar = evolution-calendar:
     Geburts-  Jahrestage (birthdays)
     Persönlich (system-calendar) default

  Evolution Task List = Evolution Tasks = evolution-tasks:
     Alarms (1427538744.24638.0@ubuntu-phablet)
     Persönlich (system-task-list) default
     Reminders (1427534898.18825.0@ubuntu-phablet)

  Evolution Memos = evolution-memos:
     Persönlich (system-memo-list) default

  phablet@ubuntu-phablet:~$ syncevolution --export tasks backend=evolution-tasks
  phablet@ubuntu-phablet:~$ file tasks
  tasks: empty

  phablet@ubuntu-phablet:~$ syncevolution --print-items backend
  =evolution-tasks

  no output

  phablet@ubuntu-phablet:~$ syncevolution --print-items backend
  =evolution-memos

  no output

  phablet@ubuntu-phablet:~$ click list
  com.canonical.payui   15.01.120
  com.canonical.scopes.bbc-sport1.03
  com.canonical.scopes.etsy 1.0.29
  com.canonical.scopes.euronews 0.5
  com.canonical.scopes.fitbit   1.0.40
  com.mikeasoft.podbird 0.5
  com.ubuntu.calendar   0.4.600
  com.ubuntu.camera 3.0.0.544
  com.ubuntu.developer.bobo1993324.qvbam0.1.3.1
  com.ubuntu.developer.liberavia.ardmediathek   0.1
  com.ubuntu.developer.majster-pl.utorch1.6
  com.ubuntu.developer.mzanetti.leo 0.2
  com.ubuntu.developer.ogra.rtv-de  0.3
  com.ubuntu.developer.tyrelparker0.metalhammer 0.2
  com.ubuntu.docviewer  0.3.109
  com.ubuntu.filemanager0.4.386
  com.ubuntu.gallery2.9.1.1183
  com.ubuntu.music  2.0.846
  com.ubuntu.reminders  0.5.380
  com.ubuntu.scopes.soundcloud  1.0.1-39
  com.ubuntu.scopes.vimeo   1.0.2-84
  com.ubuntu.telegram   1.1.2.95
  com.ubuntu.terminal   0.7.70
  dekko.dekkoproject0.5.1
  help.ubuntucoredev0.2
  noobslabscope.noobslab0.1.1
  omgubuntu-scope.mreese1.4
  com.canonical.scopes.bbc  1.7
  com.canonical.scopes.calls1.1
  com.canonical.scopes.cnet 0.6
  com.canonical.scopes.contacts 0.7
  com.canonical.scopes.dashboard1.6
  com.canonical.scopes.engadget 0.5
  com.canonical.scopes.events   1.0.11
  com.canonical.scopes.fbphotos 1.23
  com.canonical.scopes.flickr   1.0.24
  com.canonical.scopes.hints0.20
  com.canonical.scopes.holidays 1.1
  com.canonical.scopes.inrix1.0.28
  com.canonical.scopes.instagram1.0.15
  com.canonical.scopes.news 2.13
  com.canonical.scopes.photos   1.31
  com.canonical.scopes.photos-local 1.23
  com.canonical.scopes.poi  1.0.11
  com.canonical.scopes.shopping 1.9
  com.canonical.scopes.songkick 1.0.11
  com.canonical.scopes.tasks1.3
  com.canonical.scopes.texts1.0
  com.canonical.scopes.timeout  0.4.12
  com.canonical.scopes.transport-alerts 1.10
  com.canonical.scopes.twittertrending  1.0.9
  com.canonical.scopes.wikinear 1.0.9
  com.canonical.scopes.yelp 1.0.34
  com.canonical.unity-scope-nearby  0.8.8
  com.nokia.heremaps1.0.4
  com.ubuntu.developer.ken-vandine.pathwind 0.2.9
  com.ubuntu.developer.mzanetti.tagger  0.9.0.0
  com.ubuntu.developer.webapps.webapp-twitter   1.0.21
  com.zeptolab.cuttherope.free  0.5.1
  com.ubuntu.calculator 1.3.339
  com.ubuntu.clock  3.3.192
  com.ubuntu.scopes.youtube 1.0.18-134
  com.ubuntu.weather1.1.403

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/syncevolution/+bug/1440294/+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 1440294] [NEW] syncevolution - no export of tasks / memos Aquaris E4.5

[dennis]

Public bug reported:

Phone: bq Aquaris E4.5 Ubuntu Edtion
OS: Ubuntu 14.10(r20)
SyncEvolution 1.5

Can not export my Tasks and memos.
Calendar and contacts export works!

phablet@ubuntu-phablet:~$ syncevolution --print-databases
CalDAV:
   select database via absolute URL, set username/password to scan, set syncURL 
to base URL if server does not support auto-discovery (path)

CalDAVTodo:
   select database via absolute URL, set username/password to scan, set syncURL 
to base URL if server does not support auto-discovery (path)

CalDAVJournal:
   select database via absolute URL, set username/password to scan, set syncURL 
to base URL if server does not support auto-discovery (path)

CardDAV:
   select database via absolute URL, set username/password to scan, set syncURL 
to base URL if server does not support auto-discovery (path)

Evolution Address Book = Evolution Contacts = evolution-contacts:
   Persönlich (system-address-book) default

Evolution Calendar = evolution-calendar:
   Geburts-  Jahrestage (birthdays)
   Persönlich (system-calendar) default

Evolution Task List = Evolution Tasks = evolution-tasks:
   Alarms (1427538744.24638.0@ubuntu-phablet)
   Persönlich (system-task-list) default
   Reminders (1427534898.18825.0@ubuntu-phablet)

Evolution Memos = evolution-memos:
   Persönlich (system-memo-list) default

phablet@ubuntu-phablet:~$ syncevolution --export tasks backend=evolution-tasks
phablet@ubuntu-phablet:~$ file tasks
tasks: empty

phablet@ubuntu-phablet:~$ syncevolution --print-items backend=evolution-
tasks

no output

phablet@ubuntu-phablet:~$ syncevolution --print-items backend=evolution-
memos

no output

phablet@ubuntu-phablet:~$ click list
com.canonical.payui 15.01.120
com.canonical.scopes.bbc-sport  1.03
com.canonical.scopes.etsy   1.0.29
com.canonical.scopes.euronews   0.5
com.canonical.scopes.fitbit 1.0.40
com.mikeasoft.podbird   0.5
com.ubuntu.calendar 0.4.600
com.ubuntu.camera   3.0.0.544
com.ubuntu.developer.bobo1993324.qvbam  0.1.3.1
com.ubuntu.developer.liberavia.ardmediathek 0.1
com.ubuntu.developer.majster-pl.utorch  1.6
com.ubuntu.developer.mzanetti.leo   0.2
com.ubuntu.developer.ogra.rtv-de0.3
com.ubuntu.developer.tyrelparker0.metalhammer   0.2
com.ubuntu.docviewer0.3.109
com.ubuntu.filemanager  0.4.386
com.ubuntu.gallery  2.9.1.1183
com.ubuntu.music2.0.846
com.ubuntu.reminders0.5.380
com.ubuntu.scopes.soundcloud1.0.1-39
com.ubuntu.scopes.vimeo 1.0.2-84
com.ubuntu.telegram 1.1.2.95
com.ubuntu.terminal 0.7.70
dekko.dekkoproject  0.5.1
help.ubuntucoredev  0.2
noobslabscope.noobslab  0.1.1
omgubuntu-scope.mreese  1.4
com.canonical.scopes.bbc1.7
com.canonical.scopes.calls  1.1
com.canonical.scopes.cnet   0.6
com.canonical.scopes.contacts   0.7
com.canonical.scopes.dashboard  1.6
com.canonical.scopes.engadget   0.5
com.canonical.scopes.events 1.0.11
com.canonical.scopes.fbphotos   1.23
com.canonical.scopes.flickr 1.0.24
com.canonical.scopes.hints  0.20
com.canonical.scopes.holidays   1.1
com.canonical.scopes.inrix  1.0.28
com.canonical.scopes.instagram  1.0.15
com.canonical.scopes.news   2.13
com.canonical.scopes.photos 1.31
com.canonical.scopes.photos-local   1.23
com.canonical.scopes.poi1.0.11
com.canonical.scopes.shopping   1.9
com.canonical.scopes.songkick   1.0.11
com.canonical.scopes.tasks  1.3
com.canonical.scopes.texts  1.0
com.canonical.scopes.timeout0.4.12
com.canonical.scopes.transport-alerts   1.10
com.canonical.scopes.twittertrending1.0.9
com.canonical.scopes.wikinear   1.0.9
com.canonical.scopes.yelp   1.0.34
com.canonical.unity-scope-nearby0.8.8
com.nokia.heremaps  1.0.4
com.ubuntu.developer.ken-vandine.pathwind   0.2.9
com.ubuntu.developer.mzanetti.tagger0.9.0.0
com.ubuntu.developer.webapps.webapp-twitter 1.0.21
com.zeptolab.cuttherope.free0.5.1
com.ubuntu.calculator   1.3.339
com.ubuntu.clock3.3.192
com.ubuntu.scopes.youtube   1.0.18-134
com.ubuntu.weather  1.1.403

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

** Description changed:

  Phone: bq Aquaris E4.5 Ubuntu Edtion
  OS: Ubuntu 14.10(r20)
  SyncEvolution 1.5
  
- 
  Can not export my Tasks an memos.
- 
+ Calendar and contacts export works!
  
  phablet@ubuntu-phablet:~$ syncevolution --print-databases
  CalDAV:
-select database via absolute URL, set username/password to scan, set 
syncURL to base URL if server does not support auto-discovery (path)
+    select database via absolute URL, set username/password to scan, set 
syncURL to base URL if server does not support auto-discovery (path)
  
  CalDAVTodo:
-select database via absolute URL, set username/password to scan, set 
syncURL to base URL if server does not support auto-discovery (path)
+    select database via absolute URL, set username/password to scan, set 
syncURL to base URL if server does not support 

[Touch-packages] [Bug 1132736] Re: Xorg fails to start after installing the hardware enablement stack on precise due to missing symlink after purging old xserver-xorg

[Dennis Schridde]

Affects trusty with utopic hwe, too. Solution from comment #2 works.

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

Title:
  Xorg fails to start after installing the hardware enablement stack on
  precise due to missing symlink after purging old xserver-xorg

Status in xorg package in Ubuntu:
  Triaged
Status in xorg-lts-quantal package in Ubuntu:
  Confirmed
Status in xorg-lts-raring package in Ubuntu:
  Confirmed
Status in xorg-lts-saucy package in Ubuntu:
  Confirmed
Status in xorg-lts-trusty package in Ubuntu:
  Confirmed
Status in xorg-lts-utopic package in Ubuntu:
  Confirmed

Bug description:
  After installing the hardware enablement stack on precise by running:
  sudo apt-get install linux-generic-lts-quantal xserver-xorg-lts-quantal 

  Xorg fail to start. There is no error message or anything, just a black 
screen. Switching to a vt i possible and lightdm/x-0.log shows that a symlink 
is missing:
  X: cannot stat /etc/X11/X (No such file or directory), aborting.

  I updates two computers running precise x86_64 and both had the
  problem.

  Just recreating the symlink fixes the problem and then precise runs
  perfectly fine with the new stack (in fact, it's more stable so far).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1132736/+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 1360403] Re: MMS does not work with T-Mobile US

[Dennis O'Flaherty]

There is a branch tied to this bug with an apparent fix - could I get a
guide to trying to test it?  I'm not very familiar with Go, especially
cross-compiling for armhf

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

Title:
  MMS does not work with T-Mobile US

Status in lxc-android-config package in Ubuntu:
  Triaged
Status in nuntium package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Confirmed
Status in ubuntu-download-manager package in Ubuntu:
  Confirmed

Bug description:
  My /var/lib/ofono/*/gprs file contains:

  [Settings]
  Powered=1
  RoamingAllowed=0

  [context1]
  Name=T-Mobile GPRS
  AccessPointName=fast.t-mobile.com
  Username=
  Password=
  Type=internet
  Protocol=ipv6
  MessageProxy=
  MessageCenter=http://mms.msg.eng.t-mobile.com/mms/wapenc

  I guess bug #1331813 is getting in the way of IPv6 working, so I was
  told to try 'Protocol=ip', but it doesn't work either.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1360403/+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 1420466] [NEW] pulseaudio crashed, sound not coming out of built in speakers. only headphones give sounds, but cant be controlled through settings at all.

[Dennis Williams]

Public bug reported:

Description:Ubuntu 13.10
Release:13.10
unable to locate
pulseaudio crashed, sound not coming out of built in speakers. only headphones 
give sounds, but cant be controlled through settings at all.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: pulseaudio 1:4.0-0ubuntu6
ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12
Uname: Linux 3.11.0-26-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Date: Tue Feb 10 15:02:37 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-03-25 (687 days ago)
InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
MarkForUpload: True
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: Upgraded to saucy on 2014-12-01 (70 days ago)
dmi.bios.date: 09/21/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.15
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 143F
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 67.23
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.15:bd09/21/2010:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr059A1124321020100:rvnHewlett-Packard:rn143F:rvr67.23:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: HP Pavilion dv6 Notebook PC
dmi.product.version: 059A1124321020100
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug saucy

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

Title:
  pulseaudio crashed, sound not coming out of built in speakers. only
  headphones give sounds, but cant be controlled through settings at
  all.

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 13.10
  Release:  13.10
  unable to locate
  pulseaudio crashed, sound not coming out of built in speakers. only 
headphones give sounds, but cant be controlled through settings at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: pulseaudio 1:4.0-0ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12
  Uname: Linux 3.11.0-26-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Date: Tue Feb 10 15:02:37 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-03-25 (687 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  MarkForUpload: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to saucy on 2014-12-01 (70 days ago)
  dmi.bios.date: 09/21/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 143F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 67.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.15:bd09/21/2010:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr059A1124321020100:rvnHewlett-Packard:rn143F:rvr67.23:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 059A1124321020100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1420466/+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 1369067] Re: symbolic link to libturbojpeg.so missing

[Dennis Schridde]

On my system (Ubuntu 14.04) there is not even a shared object
libturbojpeg.so.0.

Version: libjpeg-turbo8 1.3.0-0ubuntu2

$ dpkg -L libjpeg-turbo8 | grep /usr/lib
/usr/lib
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libjpeg.so.8.0.2
/usr/lib/x86_64-linux-gnu/libjpeg.so.8

$ dpkg -L libjpeg-turbo8-dev | grep /usr/lib
/usr/lib
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libjpeg.a
/usr/lib/x86_64-linux-gnu/libturbojpeg.a
/usr/lib/x86_64-linux-gnu/libjpeg.so

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

Title:
  symbolic link to libturbojpeg.so missing

Status in libjpeg-turbo package in Ubuntu:
  Confirmed

Bug description:
  On amd64, the missing symlink (libturbojpeg.so - libturbojpeg.so.0)
  can lead to the following link error:

  /usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libturbojpeg.a(libturbojpeg_la-turbojpeg.o):
 relocation R_X86_64_32 against `.data' can not be used when making a shared 
object; recompile with -fPIC
  
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libturbojpeg.a: 
error adding symbols: Bad value

  Manually adding the missing symlink in /usr/lib/x86_64-linux-gnu/
  fixes the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1369067/+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 1286552] Re: No wifi after suspend

[Dennis-martin-herbers]

I tracked down the issue where WiFi would fail after suspend in that it
doesn't associate anymore (tries to connect but fails), and it's a bug
in wpa-supplicant that was fixed in the current version (Ubuntu uses
2.1, newest is 2.3). Replacing Ubuntu's wpa-supplicant 2.1 with Debian's
wpa-supplicant 2.3 and rebooting immediately fixed the issue. I know
that at least some people here had this issue...

https://packages.debian.org/sid/wpasupplicant

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

Title:
  No wifi after suspend

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After suspending ubuntu the wifi doesn't work. The solution given here
  (http://askubuntu.com/questions/368671/ubuntu-13-10-wifi-not-re-
  connecting-after-suspend) worked for me but when I have updated my
  Ubuntu now it won't work. I have tried to test mainline kernel but it
  won't to boot with it.

  To reproduce the bug : just suspend the computer and then power it.
  There's no wifi network until you restart the computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: ubuntu-release-upgrader-core 1:0.205.4
  ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
  Uname: Linux 3.11.0-15-generic i686
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: i386
  CrashDB: ubuntu
  Date: Sat Mar  1 15:20:39 2014
  InstallationDate: Installed on 2013-12-30 (61 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release i386 
(20131017)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  meradi 1503 F pulseaudio
  DistroRelease: Ubuntu 13.10
  HibernationDevice: RESUME=UUID=e71568e2-e875-4053-b3b7-2046540e78bf
  InstallationDate: Installed on 2013-12-30 (61 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release i386 
(20131017)
  MachineType: Hewlett-Packard HP Compaq 6830s
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic 
root=UUID=3eaae47b-7485-4723-8b3e-9f6dac7a01e4 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-15-generic N/A
   linux-backports-modules-3.11.0-15-generic  N/A
   linux-firmware 1.116.2
  Tags:  saucy
  Uname: Linux 3.11.0-15-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  WifiSyslog: Mar  1 15:34:33 meradi-HP-Compaq-6830s kernel: [ 4581.474196] 
perf samples too long (5002  5000), lowering kernel.perf_event_max_sample_rate 
to 25000
  dmi.bios.date: 03/12/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PZD Ver. F.0C
  dmi.board.name: 30E9
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 95.1C
  dmi.chassis.asset.tag: CNU91609Y2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PZDVer.F.0C:bd03/12/2009:svnHewlett-Packard:pnHPCompaq6830s:pvrF.0C:rvnHewlett-Packard:rn30E9:rvrKBCVersion95.1C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq 6830s
  dmi.product.version: F.0C
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1286552/+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 1411768] [NEW] clippath in svg doesn't have any effect

[Dennis O'Flaherty]

Public bug reported:

I used an svg as the source for scope art which has a clippath.  This is
rendered correctly in eog and firefox, but isn't rendered correctly in a
unity8 scope.

Source for the scope is here:
https://github.com/doswdev/haca/tree/combined_logos

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

** Attachment added: devils_ducks_bad.png
   
https://bugs.launchpad.net/bugs/1411768/+attachment/4300132/+files/devils_ducks_bad.png

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

Title:
  clippath in svg doesn't have any effect

Status in unity8 package in Ubuntu:
  New

Bug description:
  I used an svg as the source for scope art which has a clippath.  This
  is rendered correctly in eog and firefox, but isn't rendered correctly
  in a unity8 scope.

  Source for the scope is here:
  https://github.com/doswdev/haca/tree/combined_logos

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1411768/+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 1411768] Re: clippath in svg doesn't have any effect

[Dennis O'Flaherty]

This is what the image should look like

** Attachment added: devils_ducks_good.png
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1411768/+attachment/4300133/+files/devils_ducks_good.png

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

Title:
  clippath in svg doesn't have any effect

Status in unity8 package in Ubuntu:
  New

Bug description:
  I used an svg as the source for scope art which has a clippath.  This
  is rendered correctly in eog and firefox, but isn't rendered correctly
  in a unity8 scope.

  Source for the scope is here:
  https://github.com/doswdev/haca/tree/combined_logos

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1411768/+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 1410513] [NEW] package libtbb2 4.2~20130725-1.1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configur

[Dennis Ferguson]

Public bug reported:

Installed updates and it returned a failure to install/remove. Has been
doing this for a while but I never addressed it. My bad

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libtbb2 4.2~20130725-1.1ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
Date: Tue Jan 13 14:31:03 2015
DuplicateSignature: package:libtbb2:4.2~20130725-1.1ubuntu1:package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
SourcePackage: tbb
Title: package libtbb2 4.2~20130725-1.1ubuntu1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: Upgraded to trusty on 2014-05-20 (238 days ago)

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


** Tags: amd64 apport-package trusty

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

Title:
  package libtbb2 4.2~20130725-1.1ubuntu1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in tbb package in Ubuntu:
  New

Bug description:
  Installed updates and it returned a failure to install/remove. Has
  been doing this for a while but I never addressed it. My bad

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libtbb2 4.2~20130725-1.1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Tue Jan 13 14:31:03 2015
  DuplicateSignature: package:libtbb2:4.2~20130725-1.1ubuntu1:package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  SourcePackage: tbb
  Title: package libtbb2 4.2~20130725-1.1ubuntu1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: Upgraded to trusty on 2014-05-20 (238 days ago)

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

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

Re: [Touch-packages] [Bug 1405207] Re: [Inspiron N5110, IDT 92HD87B1/3, Black Headphone Out, Right] No sound at all

[dennis]

thanks for your help, but i don't belong here.
i recognize c but will not be getting that deep into code.

dutch

On 12/24/2014 09:56 PM, Raymond wrote:
 http://git.alsa-project.org/?p=alsa-
 tools.git;a=blob_plain;f=hdajacksensetest/hdajacksensetest.c;hb=HEAD

 try

 hdajacksensetest -a

 when you plugged and unpluggec headphone and mic jack


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

Title:
  [Inspiron N5110, IDT 92HD87B1/3, Black Headphone Out, Right] No sound
  at all

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  speakers on dell inspiron are working, but headphone jack does not ,
  at all, ever.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic i686
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dutch  1387 F pulseaudio
   /dev/snd/pcmC0D0p:   dutch  1387 F...m pulseaudio
  CurrentDesktop: Unity
  Date: Tue Dec 23 10:25:18 2014
  InstallationDate: Installed on 2014-12-22 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 
(20140722.2)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dutch  1387 F pulseaudio
   /dev/snd/pcmC0D0p:   dutch  1387 F...m pulseaudio
  Symptom_Jack: Black Headphone Out, Right
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [Inspiron N5110, IDT 92HD87B1/3, Black Headphone Out, Right] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd08/03/2012:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn:rvrA11:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron N5110
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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

Re: [Touch-packages] [Bug 1405207] Re: [Inspiron N5110, IDT 92HD87B1/3, Black Headphone Out, Right] No sound at all

[dennis]

Thanks for your support.  You will have to hold my hand a bit, I don't 
know linux as a first or second language.

here's what I can add to the troubleshooting...
1) just to be clear, there is no sound from headphones when plugged into 
the headphone jack.  Sound continues to come out of built-in speakers.
2) I opened system Setting , then Sound.  The only sound output 
device listed is built-in speakers, this does not change when I plug 
headphones in.
3) When I plug headphones into the MIC jack, it shows up as an output 
device Headphones, but headphones do not work either.  At the same 
time, the headphones plugged into MIC show up as Microphone in the 
Input tab.

So it looks like the sensing is screwed up, and I had trouble with this 
even in Windows7 before installing Ubuntu 14


On 12/24/2014 11:01 AM, Raymond wrote:
 headphone is not plugged,

 try hda  jack sense test


 Default Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x02, mute=1

 Node 0x13 [Audio Output] wcaps 0xd0c05: Stereo Amp-Out R/L
Control: name=Headphone Playback Volume, index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Control: name=Headphone Playback Switch, index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Device: name=92HD87B1/3 Analog, type=Audio, device=0
Amp-Out caps: N/A
Amp-Out vals:  [0x6f 0x6f]
Converter: stream=8, channel=0
Power states:
Power: setting=D0, actual=D0
Delay: 13 samples


 control.19 {
   iface CARD
   name 'Headphone Jack'
   value false
   comment {
   access read
   type BOOLEAN
   count 1
   }
   }


   active profile: output:analog-stereo+input:analog-stereo
   sinks:
   alsa_output.pci-_00_1b.0.analog-stereo/#0: Built-in Audio 
 Analog Stereo
   sources:
   alsa_output.pci-_00_1b.0.analog-stereo.monitor/#0: Monitor 
 of Built-in Audio Analog Stereo
   alsa_input.pci-_00_1b.0.analog-stereo/#1: Built-in Audio 
 Analog Stereo
   ports:
   analog-input-microphone-internal: Internal Microphone (priority 
 8900, latency offset 0 usec, available: unknown)
   properties:
   device.icon_name = audio-input-microphone
   analog-input-microphone: Microphone (priority 8700, latency 
 offset 0 usec, available: no)
   properties:
   device.icon_name = audio-input-microphone
   analog-output-speaker: Speakers (priority 1, latency offset 
 0 usec, available: unknown)
   properties:
   device.icon_name = audio-speakers
   analog-output-headphones: Headphones (priority 9000, latency 
 offset 0 usec, available: no)
   properties:
   device.icon_name = audio-headphones
   hdmi-output-0: HDMI / DisplayPort (priority 5900, latency 
 offset 0 usec, available: no)
   properties:
   device.icon_name = video-display


 ** Changed in: alsa-driver (Ubuntu)
 Status: New = 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/1405207

Title:
  [Inspiron N5110, IDT 92HD87B1/3, Black Headphone Out, Right] No sound
  at all

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  speakers on dell inspiron are working, but headphone jack does not ,
  at all, ever.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic i686
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dutch  1387 F pulseaudio
   /dev/snd/pcmC0D0p:   dutch  1387 F...m pulseaudio
  CurrentDesktop: Unity
  Date: Tue Dec 23 10:25:18 2014
  InstallationDate: Installed on 2014-12-22 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 
(20140722.2)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dutch  1387 F pulseaudio
   /dev/snd/pcmC0D0p:   dutch  1387 F...m pulseaudio
  Symptom_Jack: Black Headphone Out, Right
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [Inspiron N5110, IDT 92HD87B1/3, Black 

[Touch-packages] [Bug 1405207] [NEW] [Inspiron N5110, IDT 92HD87B1/3, Black Headphone Out, Right] No sound at all

[dennis]

Public bug reported:

speakers on dell inspiron are working, but headphone jack does not , at
all, ever.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic i686
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dutch  1387 F pulseaudio
 /dev/snd/pcmC0D0p:   dutch  1387 F...m pulseaudio
CurrentDesktop: Unity
Date: Tue Dec 23 10:25:18 2014
InstallationDate: Installed on 2014-12-22 (0 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dutch  1387 F pulseaudio
 /dev/snd/pcmC0D0p:   dutch  1387 F...m pulseaudio
Symptom_Jack: Black Headphone Out, Right
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [Inspiron N5110, IDT 92HD87B1/3, Black Headphone Out, Right] No sound at 
all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/03/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.vendor: Dell Inc.
dmi.board.version: A11
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd08/03/2012:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn:rvrA11:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron N5110
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.

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


** Tags: apport-bug i386 trusty

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

Title:
  [Inspiron N5110, IDT 92HD87B1/3, Black Headphone Out, Right] No sound
  at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  speakers on dell inspiron are working, but headphone jack does not ,
  at all, ever.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic i686
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dutch  1387 F pulseaudio
   /dev/snd/pcmC0D0p:   dutch  1387 F...m pulseaudio
  CurrentDesktop: Unity
  Date: Tue Dec 23 10:25:18 2014
  InstallationDate: Installed on 2014-12-22 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 
(20140722.2)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dutch  1387 F pulseaudio
   /dev/snd/pcmC0D0p:   dutch  1387 F...m pulseaudio
  Symptom_Jack: Black Headphone Out, Right
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [Inspiron N5110, IDT 92HD87B1/3, Black Headphone Out, Right] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd08/03/2012:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn:rvrA11:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron N5110
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1405207/+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 1360403] Re: MMS does not work with T-Mobile US

[Dennis O'Flaherty]

I'm able to receive picture messages through a complicated workaround.
This gets dumped in the nuntium log (I obscured the incoming phone
number):

  c1 06 28 1f 22 61 70 70  6c 69 63 61 74 69 6f 6e  |..(.application|
0010  2f 76 6e 64 2e 77 61 70  2e 6d 6d 73 2d 6d 65 73  |/vnd.wap.mms-mes|
0020  73 61 67 65 00 81 84 8d  80 af 84 8c 82 98 6d 61  |sage..ma|
0030  76 6f 64 69 2d 37 2d 38  39 2d 63 31 2d 33 2d 63  |vodi-7-89-c1-3-c|
0040  61 2d 37 2d 31 62 66 2d  34 2d 63 61 2d 34 61 32  |a-7-1bf-4-ca-4a2|
0050  31 63 32 38 00 8d 92 89  1a 80 18 83 2b 00 00 00  |1c28+---|
0060  00 00 00 00 00 00 00 00  2f 54 59 50 45 3d 50 4c  |/TYPE=PL|
0070  4d 4e 00 8a 80 8e 03 11  4a cb 88 05 81 03 03 f4  |MN..J...|
0080  80 83 68 74 74 70 3a 2f  2f 61 74 6c 32 6d 6f 73  |..http://atl2mos|
0090  67 65 74 2e 6d 73 67 2e  65 6e 67 2e 74 2d 6d 6f  |get.msg.eng.t-mo|
00a0  62 69 6c 65 2e 63 6f 6d  2f 6d 6d 73 2f 77 61 70  |bile.com/mms/wap|
00b0  65 6e 63 3f 54 3d 6d 61  76 6f 64 69 2d 37 2d 31  |enc?T=mavodi-7-1|
00c0  33 62 2d 31 62 66 2d 34  2d 63 61 2d 34 61 32 31  |3b-1bf-4-ca-4a21|
00d0  63 32 38 00   |c28.|

I can extract the URL from the dump and pull it down from the tmo server
as long as wifi is OFF

  wget http://atl2mosget.msg.eng.t-mobile.com/mms/wapenc?T=mavodi-7-13b-
1bf-4-ca-4a21c28

which gives me a SMIL message with a jpg attachment.  If I truncate the
file up until the FF D8 FF magic number for jpeg, I'm left with a file I
can open in an image viewer.

The nuntium log also contains this line - maybe it's encountering an unexpected 
message type which prevents the MMS from propagating through the rest of the 
pipeline:
  2014/12/20 12:21:46 Error cannot decode media type for field beginning with 
0x28@2

Hopefully this is useful to someone...

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

Title:
  MMS does not work with T-Mobile US

Status in lxc-android-config package in Ubuntu:
  Triaged
Status in nuntium package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Confirmed
Status in ubuntu-download-manager package in Ubuntu:
  Confirmed

Bug description:
  My /var/lib/ofono/*/gprs file contains:

  [Settings]
  Powered=1
  RoamingAllowed=0

  [context1]
  Name=T-Mobile GPRS
  AccessPointName=fast.t-mobile.com
  Username=
  Password=
  Type=internet
  Protocol=ipv6
  MessageProxy=
  MessageCenter=http://mms.msg.eng.t-mobile.com/mms/wapenc

  I guess bug #1331813 is getting in the way of IPv6 working, so I was
  told to try 'Protocol=ip', but it doesn't work either.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1360403/+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 52321] Re: Displayed Image on TFT is 2 pixels off, of what it normally should be

[dennis]

I am sorry, I don't have this notebook anymore since about 7-8 years
now. Consider that my last comment was from 2006 -- you might want to
put someone from the newer commenters from 2008-2009 on subscription.
But I don't know if this bug is worth looking into, as there are no
complaints since 2009 here...?

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

Title:
  Displayed Image on TFT is 2 pixels off, of what it normally should be

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xserver-xorg-driver-trident

  I have an older Laptop, Gericom Supersonic A440 1Ghz.
  It has a 1024x768 TFT Display and a Trident Cyberblade i1 Graphics Adapter.

  When I use the trident driver in xorg.conf, the displayed image is 2 pixels 
off to the right. That means, I have 2 lines of pixels missing at the right 
side of the display and 2 black/blank lines at the left.
  I bootet Knoppix, and there I didn't have this problem (though it was using 
the trident driver!)

  The only way I can have it working in kubuntu, is to use the vesa driver, 
but then X needs more of RAM, than with the trident driver.
  So this should be fixed, maybe just by updating the trident driver to the 
most recent version?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/52321/+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