[Touch-packages] [Bug 2072452] Re: AppArmor denies crun sending signals to containers

[Neil Wilson]

Upstream fault report:
https://github.com/containerd/containerd/issues/10542

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

Title:
  AppArmor denies crun sending signals to containers

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in runc package in Ubuntu:
  New

Bug description:
  Environment: k8s 1.30.2, containerd 1.7.12 (package in ubuntu repo)

  When I do a k8s deployment update, the old pods stay in 'Terminating'
  status. The /var/log/syslog has the following messages:

  2024-07-05T15:52:07.892132+08:00 km kernel: audit: type=1400
  audit(1720165927.890:2191): apparmor="DENIED" operation="signal"
  class="signal" profile="cri-containerd.apparmor.d" pid=134029
  comm="runc" requested_mask="receive" denied_mask="receive" signal=kill
  peer="runc"

  Workaround:
  currently I disable the apparmor.service and reboot the system.

  Info from github:
  
https://github.com/moby/moby/pull/47749/files#diff-4a7aa58be335398fb04f9f1634143e158146b57c6256a2d605f9eb3c3c53d840

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: alsa-base (not installed)
  ProcVersionSignature: Ubuntu 6.8.0-36.36-generic 6.8.4
  Uname: Linux 6.8.0-36-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Mon Jul  8 09:26:20 2024
  InstallationDate: Installed on 2024-07-03 (5 days ago)
  InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Release amd64 
(20240423)
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2072452/+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 2072452] Re: AppArmor denies crun sending signals to containers

[Neil Wilson]

unknown error after kill: runc did not terminate successfully: exit
status 1: unable to signal init: permission denied

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

** Bug watch added: github.com/containerd/containerd/issues #10542
   https://github.com/containerd/containerd/issues/10542

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

Title:
  AppArmor denies crun sending signals to containers

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in runc package in Ubuntu:
  New

Bug description:
  Environment: k8s 1.30.2, containerd 1.7.12 (package in ubuntu repo)

  When I do a k8s deployment update, the old pods stay in 'Terminating'
  status. The /var/log/syslog has the following messages:

  2024-07-05T15:52:07.892132+08:00 km kernel: audit: type=1400
  audit(1720165927.890:2191): apparmor="DENIED" operation="signal"
  class="signal" profile="cri-containerd.apparmor.d" pid=134029
  comm="runc" requested_mask="receive" denied_mask="receive" signal=kill
  peer="runc"

  Workaround:
  currently I disable the apparmor.service and reboot the system.

  Info from github:
  
https://github.com/moby/moby/pull/47749/files#diff-4a7aa58be335398fb04f9f1634143e158146b57c6256a2d605f9eb3c3c53d840

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: alsa-base (not installed)
  ProcVersionSignature: Ubuntu 6.8.0-36.36-generic 6.8.4
  Uname: Linux 6.8.0-36-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Mon Jul  8 09:26:20 2024
  InstallationDate: Installed on 2024-07-03 (5 days ago)
  InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Release amd64 
(20240423)
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2072452/+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 1981103] Re: System with DNS server in /etc/network/interfaces has bogus systemd-resolved config after upgrade to 22.04

[Neil]

+1, can I simply remove ifupdown (e.g. apt remove ifupdown), do I still
need it with 22.04.1?

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

Title:
  System with DNS server in /etc/network/interfaces has bogus systemd-
  resolved config after  upgrade to 22.04

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu 22.04 LTS
  Release:22.04

  ifupdown:
Installed: 0.8.36+nmu1ubuntu3
Candidate: 0.8.36+nmu1ubuntu3
Version table:
   *** 0.8.36+nmu1ubuntu3 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  100 /var/lib/dpkg/status

  After upgrading a server with classic ifupdown configuration after
  reboot the machine had no valid dns servers anymore.

  The problem is that the state file created by ifupdown using
  /etc/network/if-up.d/resolved looks like this:

  root@pangaea-pm:~# cat /run/network/ifupdown-inet-ens13
  "DNS"="134.102.20.20 134.102.200.14"
  "DOMAINS"="marum.de"

  The script later sources this file and causes the following errors,
  easy to see when you execute this:

  root@pangaea-pm:~# ifdown ens13; ifup ens13
  /etc/network/if-down.d/resolved: 12: mystatedir: not found
  /etc/network/if-up.d/resolved: 12: mystatedir: not found
  /etc/network/if-up.d/resolved: 71: DNS: not found
  /etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13: 
DNS=134.102.20.20 134.102.200.14: not found
  /etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13: 
DOMAINS=marum.de: not found
  Failed to parse DNS server address: DNS
  Failed to set DNS configuration: Invalid argument

  This happened to me on three different servers, so this is a serious
  bug and should be fixed before 22.04 upgrades are allowed for
  everybody. Most servers provided by data centers like Hetzner
  (Germany) are configure like that. After a do-release-upgrade you have
  no working DNS anymore, unless you disable systemd-resolved. I don't
  want to use netplan, so changing to this is no option.

  The fix is easy - remove the quotes in the script on the left side
  "$DNS" => $DNS; same for DOMAINS:

  if  [ -n "$NEW_DNS" ]; then
  cat <"$mystatedir/ifupdown-${ADDRFAM}-$interface"
  $DNS="$NEW_DNS"
  EOF
  if  [ -n "$NEW_DOMAINS" ]; then
  cat <>"$mystatedir/ifupdown-${ADDRFAM}-$interface"
  $DOMAINS="$NEW_DOMAINS"
  EOF
  fi
  fi

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1981103/+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 778627] Re: bash completion now quotes shell variable references rather than expanding them

[Neil]

It's now 2021 - I'm on Ubuntu 20.04.2 LTS  and I'm still being annoyed
by this bug!

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

Title:
  bash completion now quotes shell variable references rather than
  expanding them

Status in bash package in Ubuntu:
  Fix Released
Status in bash source package in Precise:
  Fix Released
Status in bash source package in Quantal:
  Fix Released
Status in bash source package in Raring:
  Fix Released
Status in bash package in Debian:
  Fix Released
Status in bash package in Fedora:
  New

Bug description:
  Binary package hint: bash

  NB! NB! NB!

  After applying the update to resolve this problem one _also_ must
  enable direxpand option by issuing:

  shopt -s direxpand

  If you do not do this, the variable expansion will not happen.

  NB! NB! NB!

  [Impact]
  Bash-4.2 tries to leave completed directory names as the user typed them,
  without expanding them to a full pathname.  One effect of this is that
  shell variables used in pathnames being completed (e.g., $HOME) are left
  unchanged, but the `$' is quoted by readline because it is a special
  character to the shell.

  [Test Case]
  - [Current test case showing expected behavior]

  Items to address so far:
    - that $ is escaped less
    - that direxpand does not expand as expected
    - that direxpand option is available and if enabled, expands directories 
with variable names.

  zef:~/Projects/precise-amd64$ mkdir -p /tmp/testd/finger/toe
  zef:~/Projects/precise-amd64$ cd /tmp/testd/
  zef:/tmp/testd$ td=`pwd`
  zef:/tmp/testd$ cd ../
  zef:/tmp$ ls \$td/finger

  zef:/tmp$ shopt -s direxpand
  zef:/tmp$ ls $td/fing
  zef:/tmp$ ls /tmp/testd/finger/
  toe

  - [Previous Test Case showing non-working bash installation]
  ~$ mkdir -p /tmp/testd/finger/toe
  /tmp$ cd /tmp/testd
  /tmp/testd$ td=`pwd`
  /tmp/testd$ cd ../
  /tmp$ ls $td/fing

  Type a TAB character at this point, and bash completion makes the line:
  /tmp$ ls \$td/finger

  Note that while 'fing' has been expanded to 'finger ' (with a space at the 
end), the $td variable reference has had the
  $ character quoted with a backslash.  This prevents further extension of the 
pathname, and in fact makes
  the command invalid; if I type a newline at this point, I get:
  ls: cannot access $td/finger: No such file or directory

  This is not useful behavior.  I believe that in Ubuntu 10.10, the $td 
variable would have been expanded
  to  '/tmp/testd', and subsequent completions starting from 
'/tmp/testd/finger' would have worked.

  [The version of /etc/bash_completion.d/acroread.sh that is installed
  starts with:

  # _filedir : to handle file and directories with spaces in their names.
  if ! type _filedir &> /dev/null ; then

  so I don't think that file is overriding /etc/bash_completion's
  _filedir ...]

  [Regression Potential]
  - (#32) low potential for regressions since this bug is related to the 
interactive command line and would not influence any scripts.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: bash 4.2-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  Architecture: amd64
  Date: Fri May  6 09:48:29 2011
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
   LANGUAGE=en_US:en
  SourcePackage: bash
  UpgradeStatus: Upgraded to natty on 2011-04-30 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/778627/+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 1895422] Re: Sound card not detected on Dell Latitude 9510 (Realtek ALC711)

[Neil Burcham]

Has anyone put together a step-by-step tutorial (written or video), to
give a little detailed direction to these steps?

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

Title:
  Sound card not detected on Dell Latitude 9510 (Realtek ALC711)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I am running Ubuntu 20.04.01 LTS, kernel version 5.6.0-1027-oem
  (checked via uname -r).

  
  I believe my sound card is not being detected by Ubuntu.  I checked the 
serial number and via BIOS (which I've upgraded to the latest version) 
according to the specs 
(https://topics-cdn.dell.com/pdf/latitude-15-9510-2-in-1-laptop_owners-manual5_en-us.pdf)
 the sound controller/speaker should be Realtek ALC711-CG / Realtek ALC1309D.

  However, when I run lspci only the following device appears:
  00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device 
[8086:02c8]

  In alsamixer, only the HDMI port appears.

  alsa-info output: http://alsa-
  project.org/db/?f=f2b70f6eb1a237378bf563cacb6f192ce0a677c3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1895422/+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 1899157] [NEW] package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status

[Neil Carstairs]

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

Public bug reported:

Upgrading 18.04 to 20.04 failed

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6.3
ProcVersionSignature: hostname 4.15.0-111.112-generic 4.15.18
Uname: Linux 4.15.0-111-generic x86_64
NonfreeKernelModules: lkp_Ubuntu_4_15_0_111_112_generic_71
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Oct  9 11:42:12 2020
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2015-12-11 (1763 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: Upgraded to focal on 2020-10-09 (0 days ago)

** Affects: initramfs-tools (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 initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1899157

Title:
  package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Upgrading 18.04 to 20.04 failed

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.3
  ProcVersionSignature: hostname 4.15.0-111.112-generic 4.15.18
  Uname: Linux 4.15.0-111-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_4_15_0_111_112_generic_71
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Oct  9 11:42:12 2020
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2015-12-11 (1763 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-10-09 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1899157/+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 1882867] [NEW] package lightdm 1.30.0-0ubuntu3.1 failed to install/upgrade: installed lightdm package pre-removal script subprocess returned error exit status 10

[neil cawse]

Public bug reported:

I also had a login loop. nothing unusual with my install - just
upgrading packages. Nothing custom.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: lightdm 1.30.0-0ubuntu3.1
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
AptOrdering:
 slick-greeter:amd64: Remove
 lightdm:amd64: Remove
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Jun  4 23:43:52 2020
ErrorMessage: installed lightdm package pre-removal script subprocess returned 
error exit status 10
InstallationDate: Installed on 2020-05-18 (22 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.3
SourcePackage: lightdm
Title: package lightdm 1.30.0-0ubuntu3.1 failed to install/upgrade: installed 
lightdm package pre-removal script subprocess returned error exit status 10
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: lightdm (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 lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1882867

Title:
  package lightdm 1.30.0-0ubuntu3.1 failed to install/upgrade: installed
  lightdm package pre-removal script subprocess returned error exit
  status 10

Status in lightdm package in Ubuntu:
  New

Bug description:
  I also had a login loop. nothing unusual with my install - just
  upgrading packages. Nothing custom.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: lightdm 1.30.0-0ubuntu3.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  AptOrdering:
   slick-greeter:amd64: Remove
   lightdm:amd64: Remove
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Jun  4 23:43:52 2020
  ErrorMessage: installed lightdm package pre-removal script subprocess 
returned error exit status 10
  InstallationDate: Installed on 2020-05-18 (22 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.3
  SourcePackage: lightdm
  Title: package lightdm 1.30.0-0ubuntu3.1 failed to install/upgrade: installed 
lightdm package pre-removal script subprocess returned error exit status 10
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1882867/+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 1866974] Re: The Diffie-Hellman prime sent by the server is not acceptable

[Neil Green]

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

Want to add my thanks as well Simon, I'm still getting a warning abut a
wildcard cert, but it's at least functional now!

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

Title:
  The Diffie-Hellman prime sent by the server is not acceptable

Status in evolution package in Ubuntu:
  Confirmed
Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  I can no longer connect to my ISP mail server.
  Works in previous version 19.10

  "The reported error was “Failed to get capabilities: Error performing
  TLS handshake: The Diffie-Hellman prime sent by the server is not
  acceptable (not long enough).”."

  I've tried finding a workaround but so far no luck.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: evolution 3.35.92-1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 11 11:07:01 2020
  InstallationDate: Installed on 2020-03-03 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303)
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1866974/+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 1873794] Re: Unattended upgrades fixes missing from security repo

[Neil Wilson]

If the fix is not in the security pocket, how does it get sorted if the
updates pocket is turned off?

I understood *-updates are only supposed to be recommended.


As I mentioned if you build an image with a tool like 'mkosi' which utilises 
debootstrap and then cleans the cache, the partial directory is missing in the 
resulting image.

Under the Debian file system layout /var is supposed to be volatile. You
can't rely on anything being there.

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

Title:
  Unattended upgrades fixes missing from security repo

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Fix Released
Status in unattended-upgrades source package in Eoan:
  Fix Released

Bug description:
  Critical unattended upgrades fixes are missing from the bionic
  security repo, which means that if you are using an installation of
  Ubuntu using only 'bionic' and 'bionic-security' you can stop
  unattended-upgrades from working just by doing a 'rmdir
  /var/cache/apt/archives/partial'.

  This is because the 'rootdir' parameter on the main function is set to
  "" rather than "/" - which disables the required directories and files
  check.

  I'm presuming here that the *-updates pocket is still 'recommended'
  rather than 'required'.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: unattended-upgrades 1.1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
  Uname: Linux 4.15.0-96-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 20 12:44:35 2020
  InstallationDate: Installed on 2016-04-28 (1452 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: Upgraded to bionic on 2018-08-19 (610 days ago)
  modified.conffile..etc.apt.apt.conf.d.10periodic: [modified]
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-09-17T10:50:46.904847

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1873794/+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 1866367] [NEW] NetworkManager can't disable IPv6 properly

[Neil Wilson]

Public bug reported:

Clicking 'disable' on the IPv6 tag doesn't appear to remove auto-
configured IPv6 addresses or turn off the IPv6 operations on the
specified interface.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: network-manager 1.22.8-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar  6 15:24:21 2020
InstallationDate: Installed on 2020-03-06 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200304)
IpRoute:
 default via 192.168.1.254 dev ens33 proto dhcp metric 100 
 169.254.0.0/16 dev ens33 scope link metric 1000 
 192.168.1.0/24 dev ens33 proto kernel scope link src 192.168.1.86 metric 100
IwConfig:
 lono wireless extensions.
 
 ens33 no wireless extensions.
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAMEUUID  TYPE  TIMESTAMP  
 TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 
  
 Wired connection 1  9f785e0c-8a0d-310a-8a14-c603fd38083c  ethernet  1583508227 
 Fri 06 Mar 2020 15:23:47 GMT  yes  -999  no
/org/freedesktop/NetworkManager/Settings/1  yes ens33   activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  -- 
/etc/NetworkManager/system-connections/Wired connection 1.nmconnection
nmcli-dev:
 DEVICE  TYPE  STATE  IP4-CONNECTIVITY  IP6-CONNECTIVITY  DBUS-PATH 
 CONNECTION  CON-UUID   
   CON-PATH   
 ens33   ethernet  connected  full  limited   
/org/freedesktop/NetworkManager/Devices/2  Wired connection 1  
9f785e0c-8a0d-310a-8a14-c603fd38083c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 lo  loopback  unmanaged  unknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.22.8   connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug focal

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

Title:
  NetworkManager can't disable IPv6 properly

Status in network-manager package in Ubuntu:
  New

Bug description:
  Clicking 'disable' on the IPv6 tag doesn't appear to remove auto-
  configured IPv6 addresses or turn off the IPv6 operations on the
  specified interface.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.8-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  6 15:24:21 2020
  InstallationDate: Installed on 2020-03-06 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200304)
  IpRoute:
   default via 192.168.1.254 dev ens33 proto dhcp metric 100 
   169.254.0.0/16 dev ens33 scope link metric 1000 
   192.168.1.0/24 dev ens33 proto kernel scope link src 192.168.1.86 metric 100
  IwConfig:
   lono wireless extensions.
   
   ens33 no wireless extensions.
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE  FILENAME
   
   Wired connection 1  9f785e0c-8a0d-310a-8a14-c603fd38083c  ethernet  
1583508227  Fri 06 Mar 2020 15:23:47 GMT  yes  -999  no 
   /org/freedesktop/NetworkManager/Settings/1  yes ens33   activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  -- 
/etc/NetworkManager/system-connections/Wired connection 1.nmconnection
  nmcli-dev:
   DEVICE  TYPE  STATE  IP4-CONNECTIVITY  IP6-CONNECTIVITY  DBUS-PATH   
   CONN

[Touch-packages] [Bug 1863532] Re: Invoking "python" brings inappropriate response from command-not-found when python3 installed

[Neil McPhail]

Indeed. It offers python3 version 3.7.5-1ubuntu1 as a solution which is
not appropriate as python3 version 3.8.0-3 is already installed and does
not provide a `python` command.

The python-is-python3 solution sounds like a sensible way forward. There
be dragons, I suspect.

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

Title:
  Invoking "python" brings inappropriate response from command-not-found
  when python3 installed

Status in command-not-found package in Ubuntu:
  Triaged
Status in python3-defaults package in Ubuntu:
  Triaged
Status in command-not-found source package in Focal:
  Triaged
Status in python3-defaults source package in Focal:
  Triaged

Bug description:
  Ubuntu Mate 20.04 development release, upgraded from 19.10. I don't
  have python 2.7 installed, but have python 3 installed as per default.

  Please see ascii-cast at
  https://asciinema.org/a/SZR20NHz2FN6N6O1hj2Mqmnv8 .

  Running `python` brings up text from command-not-found which suggests
  installing `python3` as a solution to the missing command. `python3`
  is already installed, is a later version than the one indicated by
  command-not-found and does not supply a binary or symlink named
  `python`.

  $ apt policy python
  python:
Installed: (none)
Candidate: (none)
Version table:
   2.7.17-1 -1
  100 /var/lib/dpkg/status
  $ apt policy python3
  python3:
Installed: 3.8.0-3
Candidate: 3.8.0-3
Version table:
   *** 3.8.0-3 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  $ apt policy command-not-found
  command-not-found:
Installed: 19.10.0
Candidate: 19.10.0
Version table:
   *** 19.10.0 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu focal/main i386 Packages
  100 /var/lib/dpkg/status

  I don't know whether this is a bug in python3 or command-not-found
  (the latter of which doesn't seem to have been updated for 20.04 yet).
  i don't know if it is intentional that `python3` will not provide a
  binary or symlink named `python`. if that is the case, the output of
  `command-not-found` should be updated to reflect that.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: python3 3.8.0-3
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Feb 17 01:35:16 2020
  InstallationDate: Installed on 2019-10-11 (128 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  SourcePackage: python3-defaults
  UpgradeStatus: Upgraded to focal on 2020-02-07 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1863532/+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 1863532] Re: Invoking "python" brings inappropriate response from command-not-found when python3 installed

[Neil McPhail]

Indeed. It offers python3 version 3.7.5-1ubuntu1 as a solution which is
not appropriate as python3 version 3.8.0-3 is already installed and does
not provide a `python` command.

The python-is-python3 solution sounds like a sensible way forward. There
be dragons, I suspect.

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

Title:
  Invoking "python" brings inappropriate response from command-not-found
  when python3 installed

Status in command-not-found package in Ubuntu:
  Triaged
Status in python3-defaults package in Ubuntu:
  Triaged
Status in command-not-found source package in Focal:
  Triaged
Status in python3-defaults source package in Focal:
  Triaged

Bug description:
  Ubuntu Mate 20.04 development release, upgraded from 19.10. I don't
  have python 2.7 installed, but have python 3 installed as per default.

  Please see ascii-cast at
  https://asciinema.org/a/SZR20NHz2FN6N6O1hj2Mqmnv8 .

  Running `python` brings up text from command-not-found which suggests
  installing `python3` as a solution to the missing command. `python3`
  is already installed, is a later version than the one indicated by
  command-not-found and does not supply a binary or symlink named
  `python`.

  $ apt policy python
  python:
Installed: (none)
Candidate: (none)
Version table:
   2.7.17-1 -1
  100 /var/lib/dpkg/status
  $ apt policy python3
  python3:
Installed: 3.8.0-3
Candidate: 3.8.0-3
Version table:
   *** 3.8.0-3 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  $ apt policy command-not-found
  command-not-found:
Installed: 19.10.0
Candidate: 19.10.0
Version table:
   *** 19.10.0 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu focal/main i386 Packages
  100 /var/lib/dpkg/status

  I don't know whether this is a bug in python3 or command-not-found
  (the latter of which doesn't seem to have been updated for 20.04 yet).
  i don't know if it is intentional that `python3` will not provide a
  binary or symlink named `python`. if that is the case, the output of
  `command-not-found` should be updated to reflect that.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: python3 3.8.0-3
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Feb 17 01:35:16 2020
  InstallationDate: Installed on 2019-10-11 (128 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  SourcePackage: python3-defaults
  UpgradeStatus: Upgraded to focal on 2020-02-07 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1863532/+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 1863532] [NEW] Invoking "python" brings inappropriate response from command-not-found when python3 installed

[Neil McPhail]

Public bug reported:

Ubuntu Mate 20.04 development release, upgraded from 19.10. I don't have
python 2.7 installed, but have python 3 installed as per default.

Please see ascii-cast at
https://asciinema.org/a/SZR20NHz2FN6N6O1hj2Mqmnv8 .

Running `python` brings up text from command-not-found which suggests
installing `python3` as a solution to the missing command. `python3` is
already installed, is a later version than the one indicated by command-
not-found and does not supply a binary or symlink named `python`.

$ apt policy python
python:
  Installed: (none)
  Candidate: (none)
  Version table:
 2.7.17-1 -1
100 /var/lib/dpkg/status
$ apt policy python3
python3:
  Installed: 3.8.0-3
  Candidate: 3.8.0-3
  Version table:
 *** 3.8.0-3 500
500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status
$ apt policy command-not-found
command-not-found:
  Installed: 19.10.0
  Candidate: 19.10.0
  Version table:
 *** 19.10.0 500
500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
500 http://gb.archive.ubuntu.com/ubuntu focal/main i386 Packages
100 /var/lib/dpkg/status

I don't know whether this is a bug in python3 or command-not-found (the
latter of which doesn't seem to have been updated for 20.04 yet). i
don't know if it is intentional that `python3` will not provide a binary
or symlink named `python`. if that is the case, the output of `command-
not-found` should be updated to reflect that.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: python3 3.8.0-3
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
CurrentDesktop: MATE
Date: Mon Feb 17 01:35:16 2020
InstallationDate: Installed on 2019-10-11 (128 days ago)
InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
SourcePackage: python3-defaults
UpgradeStatus: Upgraded to focal on 2020-02-07 (10 days ago)

** Affects: command-not-found (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Affects: python3-defaults (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug champagne focal

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

Title:
  Invoking "python" brings inappropriate response from command-not-found
  when python3 installed

Status in command-not-found package in Ubuntu:
  Confirmed
Status in python3-defaults package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Mate 20.04 development release, upgraded from 19.10. I don't
  have python 2.7 installed, but have python 3 installed as per default.

  Please see ascii-cast at
  https://asciinema.org/a/SZR20NHz2FN6N6O1hj2Mqmnv8 .

  Running `python` brings up text from command-not-found which suggests
  installing `python3` as a solution to the missing command. `python3`
  is already installed, is a later version than the one indicated by
  command-not-found and does not supply a binary or symlink named
  `python`.

  $ apt policy python
  python:
Installed: (none)
Candidate: (none)
Version table:
   2.7.17-1 -1
  100 /var/lib/dpkg/status
  $ apt policy python3
  python3:
Installed: 3.8.0-3
Candidate: 3.8.0-3
Version table:
   *** 3.8.0-3 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  $ apt policy command-not-found
  command-not-found:
Installed: 19.10.0
Candidate: 19.10.0
Version table:
   *** 19.10.0 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu focal/main i386 Packages
  100 /var/lib/dpkg/status

  I don't know whether this is a bug in python3 or command-not-found
  (the latter of which doesn't seem to have been updated for 20.04 yet).
  i don't know if it is intentional that `python3` will not provide a
  binary or symlink named `python`. if that is the case, the output of
  `command-not-found` should be updated to reflect that.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: python3 3.8.0-3
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Feb 17 01:35:16 2020
  InstallationDate: Installed on 2019-10-11 (128 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  SourcePackage: python3-defaults
  UpgradeStatus: Upgraded to focal on 2020-02-07 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1863532/+subscrip

[Touch-packages] [Bug 1863532] Re: Invoking "python" brings inappropriate response from command-not-found when python3 installed

[Neil McPhail]

$ apt policy python3-commandnotfound 
python3-commandnotfound:
  Installed: 19.10.0
  Candidate: 19.10.0
  Version table:
 *** 19.10.0 500
500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
500 http://gb.archive.ubuntu.com/ubuntu focal/main i386 Packages
100 /var/lib/dpkg/status

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

Title:
  Invoking "python" brings inappropriate response from command-not-found
  when python3 installed

Status in command-not-found package in Ubuntu:
  Confirmed
Status in python3-defaults package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Mate 20.04 development release, upgraded from 19.10. I don't
  have python 2.7 installed, but have python 3 installed as per default.

  Please see ascii-cast at
  https://asciinema.org/a/SZR20NHz2FN6N6O1hj2Mqmnv8 .

  Running `python` brings up text from command-not-found which suggests
  installing `python3` as a solution to the missing command. `python3`
  is already installed, is a later version than the one indicated by
  command-not-found and does not supply a binary or symlink named
  `python`.

  $ apt policy python
  python:
Installed: (none)
Candidate: (none)
Version table:
   2.7.17-1 -1
  100 /var/lib/dpkg/status
  $ apt policy python3
  python3:
Installed: 3.8.0-3
Candidate: 3.8.0-3
Version table:
   *** 3.8.0-3 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  $ apt policy command-not-found
  command-not-found:
Installed: 19.10.0
Candidate: 19.10.0
Version table:
   *** 19.10.0 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu focal/main i386 Packages
  100 /var/lib/dpkg/status

  I don't know whether this is a bug in python3 or command-not-found
  (the latter of which doesn't seem to have been updated for 20.04 yet).
  i don't know if it is intentional that `python3` will not provide a
  binary or symlink named `python`. if that is the case, the output of
  `command-not-found` should be updated to reflect that.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: python3 3.8.0-3
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Feb 17 01:35:16 2020
  InstallationDate: Installed on 2019-10-11 (128 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  SourcePackage: python3-defaults
  UpgradeStatus: Upgraded to focal on 2020-02-07 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1863532/+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 1805183] Re: systemd-resolved constantly restarts on Bionic upgraded from Xenial

[Neil Wilson]

"I think you're trying to start dhclient on an interface that's already
setup."

It just triggers a lease refresh on the existing interface, which has
the same issue.

Nov 15 14:17:10 srv-ywz63 systemd-logind[981]: New session 27 of user ubuntu.
Nov 15 14:17:10 srv-ywz63 systemd[1]: Started Session 27 of user ubuntu.
Nov 15 14:17:30 srv-ywz63 sudo[12484]:   ubuntu : TTY=pts/2 ; PWD=/home/ubuntu 
; USER=root ; COMMAND=/sbin/dhclient eth0
Nov 15 14:17:30 srv-ywz63 sudo[12484]: pam_unix(sudo:session): session opened 
for user root by ubuntu(uid=0)
Nov 15 14:17:30 srv-ywz63 dhclient[12485]: DHCPREQUEST of 10.241.196.178 on 
eth0 to 255.255.255.255 port 67 (xid=0x511efd40)
Nov 15 14:17:30 srv-ywz63 dhclient[12485]: DHCPACK of 10.241.196.178 from 
10.241.196.177
Nov 15 14:17:30 srv-ywz63 dhclient[12485]: bound to 10.241.196.178 -- renewal 
in 1421 seconds.
Nov 15 14:17:30 srv-ywz63 sudo[12484]: pam_unix(sudo:session): session closed 
for user root

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

Title:
  systemd-resolved constantly restarts on Bionic upgraded from Xenial

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Cosmic:
  Won't Fix
Status in systemd source package in Disco:
  Fix Committed
Status in systemd source package in Eoan:
  Fix Committed
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [Impact]
  Log noise due to needless restart of resolved on lease expiry, maybe loss of 
cached state?
  Application that require Name Resolution may fail while the service is being 
unnecessarily restarted

  [Test case]
  (1) Append make_resolv_conf to the end of the file, so it gets executed
  (2) Execute the file with bash -x and different settings and ensure there are 
no restarts if the settings are the same, and that there are if settings 
change; for example:

  sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash 
-x debian/extra/dhclient-enter-resolved-hook
  sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash 
-x debian/extra/dhclient-enter-resolved-hook
  => no restart
  sudo new_domain_name_servers=8.8.8.8 interface="wlp61s0" reason=REBIND bash 
-x debian/extra/dhclient-enter-resolved-hook
  => should restart
  sudo new_domain_name_servers=8.8.8.8 interface="wlp61s0" reason=REBIND bash 
-x debian/extra/dhclient-enter-resolved-hook
  => no restart
  sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash 
-x debian/extra/dhclient-enter-resolved-hook
  => should restart

  [Regression potential]
  The change only restarts resolved when the settings change. If there's a bug 
in the logic, resolved might not be restarted when it should be. Also, since 
there will be less restarts of resolved, it will run longer, so if there are 
memory leaks they will become more apparent.

  [other info]

  this fix was included in the initial release of systemd for eoan, but
  the fix required the additional change in bug 1849608.  Both the
  original patch plus that change (to avoid using bash-specific &>) are
  included in the b/d patch for this bug.

  [Original bug report]
  If a cloud server is upgraded from Xenial to Bionic, the dhclient system 
remains in place and any DHCP lease refreshes cause a needless restart of the 
system-resolved daemon

  Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPREQUEST of 10.226.209.106 on 
ens3 to 10.226.209.105 port 67 (xid=0x2bd41d7d)
  Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPACK of 10.226.209.106 from 
10.226.209.105
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopping Network Name Resolution...
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopped Network Name Resolution.
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting Network Name Resolution...
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Positive Trust Anchors:
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: . IN DS 19036 8 2 
49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: . IN DS 20326 8 2 
e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Negative trust anchors: 
10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 1
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Using system hostname 
'srv-qvjhx'.
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Started Network Name Resolution.
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting 
resolvconf-pull-resolved.service...
  Nov 26 16:59:41 srv-qvjhx dhclient[825]: bound to 10.226.209.106 -- renewal 
in 1466 seconds.
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Started 
resolvconf-pull-resolved.service.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.25
  Pro

[Touch-packages] [Bug 1805183] Re: systemd-resolved constantly restarts on Bionic upgraded from Xenial

[Neil Wilson]

LGTM on bionic

ubuntu@srv-ywz63:~$ dpkg -l systemd | grep ii
ii  systemd237-3ubuntu10.32 i386 system and service manager
ubuntu@srv-ywz63:~$ journalctl -b -u systemd-resolved | grep Started
Nov 14 17:05:43 srv-ywz63 systemd[1]: Started Network Name Resolution.
Nov 14 17:05:44 srv-ywz63 systemd[1]: Started Network Name Resolution.
ubuntu@srv-ywz63:~$ sudo dhclient eth0
RTNETLINK answers: File exists
ubuntu@srv-ywz63:~$ journalctl -b -u systemd-resolved | grep Started
Nov 14 17:05:43 srv-ywz63 systemd[1]: Started Network Name Resolution.
Nov 14 17:05:44 srv-ywz63 systemd[1]: Started Network Name Resolution.
ubuntu@srv-ywz63:~$


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

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

Title:
  systemd-resolved constantly restarts on Bionic upgraded from Xenial

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Cosmic:
  Won't Fix
Status in systemd source package in Disco:
  Fix Committed
Status in systemd source package in Eoan:
  Fix Committed
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [Impact]
  Log noise due to needless restart of resolved on lease expiry, maybe loss of 
cached state?
  Application that require Name Resolution may fail while the service is being 
unnecessarily restarted

  [Test case]
  (1) Append make_resolv_conf to the end of the file, so it gets executed
  (2) Execute the file with bash -x and different settings and ensure there are 
no restarts if the settings are the same, and that there are if settings 
change; for example:

  sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash 
-x debian/extra/dhclient-enter-resolved-hook
  sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash 
-x debian/extra/dhclient-enter-resolved-hook
  => no restart
  sudo new_domain_name_servers=8.8.8.8 interface="wlp61s0" reason=REBIND bash 
-x debian/extra/dhclient-enter-resolved-hook
  => should restart
  sudo new_domain_name_servers=8.8.8.8 interface="wlp61s0" reason=REBIND bash 
-x debian/extra/dhclient-enter-resolved-hook
  => no restart
  sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash 
-x debian/extra/dhclient-enter-resolved-hook
  => should restart

  [Regression potential]
  The change only restarts resolved when the settings change. If there's a bug 
in the logic, resolved might not be restarted when it should be. Also, since 
there will be less restarts of resolved, it will run longer, so if there are 
memory leaks they will become more apparent.

  [other info]

  this fix was included in the initial release of systemd for eoan, but
  the fix required the additional change in bug 1849608.  Both the
  original patch plus that change (to avoid using bash-specific &>) are
  included in the b/d patch for this bug.

  [Original bug report]
  If a cloud server is upgraded from Xenial to Bionic, the dhclient system 
remains in place and any DHCP lease refreshes cause a needless restart of the 
system-resolved daemon

  Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPREQUEST of 10.226.209.106 on 
ens3 to 10.226.209.105 port 67 (xid=0x2bd41d7d)
  Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPACK of 10.226.209.106 from 
10.226.209.105
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopping Network Name Resolution...
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopped Network Name Resolution.
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting Network Name Resolution...
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Positive Trust Anchors:
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: . IN DS 19036 8 2 
49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: . IN DS 20326 8 2 
e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Negative trust anchors: 
10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 1
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Using system hostname 
'srv-qvjhx'.
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Started Network Name Resolution.
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting 
resolvconf-pull-resolved.service...
  Nov 26 16:59:41 srv-qvjhx dhclient[825]: bound to 10.226.209.106 -- renewal 
in 1466 seconds.
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Started 
resolvconf-pull-resolved.service.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.25
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  Uname: Linux 4.4.0-139-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CrashDB: ubuntu
  Date: Mon Nov 26 16:17:52 2018
  PackageArchit

[Touch-packages] [Bug 1805183] Re: systemd-resolved constantly restarts on Bionic upgraded from Xenial

[Neil Wilson]

I think just a delta change process would be fine. It's restarting when
there is no change in lease details, and just clogging up the logs.

btw I am not suggesting leaving dhclient there is a bug - hence the
title of the bug.

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

Title:
  systemd-resolved constantly restarts on Bionic upgraded from Xenial

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  If a cloud server is upgraded from Xenial to Bionic, the dhclient
  system remains in place and any DHCP lease refreshes cause a needless
  restart of the system-resolved daemon

  
  Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPREQUEST of 10.226.209.106 on 
ens3 to 10.226.209.105 port 67 (xid=0x2bd41d7d)
  Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPACK of 10.226.209.106 from 
10.226.209.105
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopping Network Name Resolution...
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopped Network Name Resolution.
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting Network Name Resolution...
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Positive Trust Anchors:
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: . IN DS 19036 8 2 
49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: . IN DS 20326 8 2 
e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Negative trust anchors: 
10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 1
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Using system hostname 
'srv-qvjhx'.
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Started Network Name Resolution.
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting 
resolvconf-pull-resolved.service...
  Nov 26 16:59:41 srv-qvjhx dhclient[825]: bound to 10.226.209.106 -- renewal 
in 1466 seconds.
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Started 
resolvconf-pull-resolved.service.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.25
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  Uname: Linux 4.4.0-139-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CrashDB: ubuntu
  Date: Mon Nov 26 16:17:52 2018
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805183/+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 1724919] Re: Bluetooth headphones only use A2DP when connected manually

[Neil Aspinall]

Bug still present in Ubuntu 18.10.

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

Title:
  Bluetooth headphones only use A2DP when connected manually

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

Bug description:
  Issue with Sony MDR-1ABT Bluetooth headphones:
  Once paired, the headphones will be connected automatically whenever they are 
switched on. However when connected this way, only the HSP/HFP profile will 
work and trying to change to A2DP in sound settings does nothing.
  If the headphones are then manually disconnected and reconnected from 
Bluetooth settings, they will initially use HSP/HFP but then selecting A2DP in 
sound settings will successfully make them use A2DP.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  neil   1443 F pulseaudio
   /dev/snd/pcmC0D0c:   neil   1443 F...m pulseaudio
   /dev/snd/controlC0:  neil   1443 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 19:12:59 2017
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: MDR-1ABT
  Symptom_Type: None of the above
  Title: [MDR-1ABT, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: Z270N-WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd07/06/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ270N-WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ270N-WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z270N-WIFI
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1724919/+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 1724919] Re: Bluetooth headphones only use A2DP when connected manually

[Neil Aspinall]

It's not possible to "change the bug status to Confirmed" as suggested
in comment #14, the Status is "changeable only by a project maintainer
of bug supervisor".

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

Title:
  Bluetooth headphones only use A2DP when connected manually

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

Bug description:
  Issue with Sony MDR-1ABT Bluetooth headphones:
  Once paired, the headphones will be connected automatically whenever they are 
switched on. However when connected this way, only the HSP/HFP profile will 
work and trying to change to A2DP in sound settings does nothing.
  If the headphones are then manually disconnected and reconnected from 
Bluetooth settings, they will initially use HSP/HFP but then selecting A2DP in 
sound settings will successfully make them use A2DP.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  neil   1443 F pulseaudio
   /dev/snd/pcmC0D0c:   neil   1443 F...m pulseaudio
   /dev/snd/controlC0:  neil   1443 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 19:12:59 2017
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: MDR-1ABT
  Symptom_Type: None of the above
  Title: [MDR-1ABT, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: Z270N-WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd07/06/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ270N-WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ270N-WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z270N-WIFI
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1724919/+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 1232928] Re: The wifi regulatory domain is ignored

[Neil Bhisma]

Thanks for providing the proper coding process to resolve WiFi issue,
this bugs process really help me a lot to get my solution as i am unable
to access WiFi connection in my Apple iPhone Device. But still anyone
want some more information apart from coding then i suggest to read this
blog once for more help: https://www.applemacsupportnumbers.com/apple-
id-support/

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

Title:
  The wifi regulatory domain is ignored

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have edited the /etc/defaults/crda file to configure my system
  regulatory domain to AU.

  When network-manager attaches to the wireless network, this value is not 
sourced. The regulatory domain switches back to US.
  This repeats back and forth, from AU to World to US.

  System detail is:
  root@mythtv:/etc/sysctl.d# cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="13.04, Raring Ringtail"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 13.04"
  VERSION_ID="13.04"
  ...

  Here is the output from dmesg when this occurs.

  [   15.579701] cfg80211: Calling CRDA for country: AU
  [   15.583170] cfg80211: Regulatory domain changed to country: AU
  [   15.583173] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
  [   15.583174] cfg80211:   (2402000 KHz - 2482000 KHz @ 4 KHz), (N/A, 
2000 mBm)
  [   15.583175] cfg80211:   (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 
2300 mBm)
  [   15.583176] cfg80211:   (525 KHz - 533 KHz @ 4 KHz), (300 mBi, 
2300 mBm)
  [   15.583177] cfg80211:   (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 
3000 mBm)
  ...
  [   22.265820] wlan0: authenticate with 94:44:52:a7:ed:d3
  [   22.313771] wlan0: send auth to 94:44:52:a7:ed:d3 (try 1/3)
  [   22.315735] wlan0: authenticated
  [   22.319045] wlan0: associate with 94:44:52:a7:ed:d3 (try 1/3)
  [   22.320563] wlan0: RX AssocResp from 94:44:52:a7:ed:d3 (capab=0x11 
status=0 aid=4)
  [   22.323544] wlan0: associated
  [   22.323571] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [   22.323611] cfg80211: Calling CRDA for country: US
  [   22.325924] cfg80211: Regulatory domain changed to country: US
  [   22.325927] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
  [   22.325928] cfg80211:   (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 
2700 mBm)
  [   22.325930] cfg80211:   (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 
1700 mBm)
  [   22.325931] cfg80211:   (525 KHz - 533 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
  [   22.325932] cfg80211:   (549 KHz - 560 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
  [   22.325933] cfg80211:   (565 KHz - 571 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
  [   22.325934] cfg80211:   (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 
3000 mBm)
  ...
  [  216.856143] wlan0: deauthenticating from 94:44:52:a7:ed:d3 by local choice 
(reason=3)
  [  216.884265] cfg80211: Calling CRDA to update world regulatory domain
  [  216.890344] cfg80211: World regulatory domain updated:
  [  216.890350] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
  [  216.890355] cfg80211:   (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
  [  216.890359] cfg80211:   (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
  [  216.890362] cfg80211:   (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
  [  216.890365] cfg80211:   (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
  [  216.890368] cfg80211:   (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
  [  216.890390] cfg80211: Calling CRDA for country: AU
  [  216.895900] cfg80211: Regulatory domain changed to country: AU
  [  216.895904] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
  [  216.895907] cfg80211:   (2402000 KHz - 2482000 KHz @ 4 KHz), (N/A, 
2000 mBm)
  [  216.895910] cfg80211:   (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 
2300 mBm)
  [  216.895913] cfg80211:   (525 KHz - 533 KHz @ 4 KHz), (300 mBi, 
2300 mBm)
  [  216.895915] cfg80211:   (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 
3000 mBm)
  [  217.982078] wlan0: authenticate with 94:44:52:a7:ed:d3
  [  218.005788] wlan0: send auth to 94:44:52:a7:ed:d3 (try 1/3)
  [  218.006865] wlan0: authenticated
  [  218.010870] wlan0: associate with 94:44:52:a7:ed:d3 (try 1/3)
  [  218.012486] wlan0: RX AssocResp from 94:44:52:a7:ed:d3 (capab=0x11 
status=0 aid=4)
  [  218.015591] wlan0: associated
  [  218.015626] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  218.015680] cfg80211: Calling CRDA for country: US
  [  218.022206] cfg80211: Regulatory domain changed to country: US
  [  218.022210] cfg80211:   (start_freq - end_fre

[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.

[Neil Hoggarth]

I have the same problem as William Jojo (w-jojo) reported in #54.

The Shibboleth authentication package (libapache2-mod-shib2) in Bionic
Universe depends on libcurl3 (via libxmltooling7). I'm told in bug
#1776489 that this is because upstream Shibboleth hasn't yet released a
version that works with OpenSSL 1.1, so it genuinely needs
libcurl3/libssl1.0.0.

Even when Shibboleth 3 is released by upstream, presumably it will not
appear in Bionic, except perhaps as a backport?

So we need a solution for proper libcurl3 / libcurl4 co-existence in
Bionic, if the Shibboleth SSO stack is going to work in the current LTS
cycle.

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

Title:
  After last updated libcurl3 on libcurl4, some apps are removed.

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) 
deleted such applications as:
  virtualbox-5.2
  opera-stable
  slack-desktop

  I really need these applications, I installed them with broken
  dependencies, but they are deleted after each update. Is it possible
  to make the dependence of the libcurl3 in libcurl4, and not remove it
  altogether from system?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+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 1773229] [NEW] spooldir mtime=0 prevents database from being updated

[Neil Roza]

Public bug reported:

When the spooldir mtime=0, cron refuses to update its "database". This
happens because the "old database" mtime is initialized to 0.


```
61: /* if spooldir's mtime has not changed, we don't need to fiddle with
62-  * the database.
63-  *
64-  * Note that old_db->mtime is initialized to 0 in main(), and
65-  * so is guaranteed to be different than the stat() mtime the first
66-  * time this function is called.
67-  */
68- if (old_db->mtime == TMAX(statbuf.st_mtime, syscron_stat.st_mtime)) {
69- Debug(DLOAD, ("[%ld] spool dir mtime unch, no load needed.\n",
70-   (long)getpid()))
71- return;
72- }
```

from `database.c`, v4.1

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

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

Title:
  spooldir mtime=0 prevents database from being updated

Status in cron package in Ubuntu:
  New

Bug description:
  When the spooldir mtime=0, cron refuses to update its "database". This
  happens because the "old database" mtime is initialized to 0.

  
  ```
  61: /* if spooldir's mtime has not changed, we don't need to fiddle with
  62-  * the database.
  63-  *
  64-  * Note that old_db->mtime is initialized to 0 in main(), and
  65-  * so is guaranteed to be different than the stat() mtime the first
  66-  * time this function is called.
  67-  */
  68- if (old_db->mtime == TMAX(statbuf.st_mtime, syscron_stat.st_mtime)) {
  69- Debug(DLOAD, ("[%ld] spool dir mtime unch, no load needed.\n",
  70-   (long)getpid()))
  71- return;
  72- }
  ```

  from `database.c`, v4.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1773229/+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 1761114] Re: systemd build error on aarch64 with "Failed to parse personality, ignoring: x86"

[Neil]

verified, build failed with version 229-4ubuntu21.2.
I was built with the command:

# dpkg-buildpackage -j4

I have passed the build with the commit mentioned on my aarch64 machine,
if build command is right, it is fine for me.

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

Title:
  systemd build error on aarch64 with "Failed to parse personality,
  ignoring: x86"

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  download source code from 
https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21,
  build with `dpkg-buildpackage` on aarch64, and build break with the following 
messages:

  ```
  + test /tmp/test-exec_workingdirectory = /tmp/test-exec_workingdirectory
2 
[/root/neil/systemd/test/systemd-229.orig/test/test-execute/exec-personality-x86.service:7]
 Failed to parse personality, ignoring: x86
3 + uname -m
4 + c=aarch64
5 + test aarch64 = i686
6 exec-personality-x86.service: Main process exited, code=exited, 
status=1/FAILURE
7 exec-personality-x86.service: Unit entered failed state.
8 exec-personality-x86.service: Failed with result 'exit-code'.
9 Assertion 'service->main_exec_status.status == status_expected' failed at 
../src/test/test-execute.c:65, function check(). Aborting.
  ```

  it should run into x86 test case with:
  ```
  87  static void test_exec_personality(Manager *m) {
  88  #if defined(__x86_64__)
  89  test(m, "exec-personality-x86-64.service", 0, CLD_EXITED);
  90  
  91  #elif defined(__s390__)
  92  test(m, "exec-personality-s390.service", 0, CLD_EXITED);
  93  
  94  #else
  95  test(m, "exec-personality-x86.service", 0, CLD_EXITED);
  96  #endif
  97  }
  ```

  after checked upstream systemd source code,
  https://github.com/systemd/systemd/commit/12591863 will fix it.

  is this patch already applied? or I get invalid build steps on
  aarch64?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1761114/+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 1761114] Re: systemd build error on aarch64 with "Failed to parse personality, ignoring: x86"

[Neil]

I am taking some features off on systemd, so i have to rebuild systemd package. 
Yes, I am building as root, and after pull the latest release and checked the 
source code,
I think this issue still exists.

** 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/1761114

Title:
  systemd build error on aarch64 with "Failed to parse personality,
  ignoring: x86"

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  download source code from 
https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21,
  build with `dpkg-buildpackage` on aarch64, and build break with the following 
messages:

  ```
  + test /tmp/test-exec_workingdirectory = /tmp/test-exec_workingdirectory
    2 
[/root/neil/systemd/test/systemd-229.orig/test/test-execute/exec-personality-x86.service:7]
 Failed to parse personality, ignoring: x86
3 + uname -m
4 + c=aarch64
5 + test aarch64 = i686
6 exec-personality-x86.service: Main process exited, code=exited, 
status=1/FAILURE
7 exec-personality-x86.service: Unit entered failed state.
8 exec-personality-x86.service: Failed with result 'exit-code'.
9 Assertion 'service->main_exec_status.status == status_expected' failed at 
../src/test/test-execute.c:65, function check(). Aborting.
  ```

  it should run into x86 test case with:
  ```
  87  static void test_exec_personality(Manager *m) {
  88  #if defined(__x86_64__)
  89  test(m, "exec-personality-x86-64.service", 0, CLD_EXITED);
  90  
  91  #elif defined(__s390__)
  92  test(m, "exec-personality-s390.service", 0, CLD_EXITED);
  93  
  94  #else
  95  test(m, "exec-personality-x86.service", 0, CLD_EXITED);
  96  #endif
  97  }
  ```

  after checked upstream systemd source code,
  https://github.com/systemd/systemd/commit/12591863 will fix it.

  is this patch already applied? or I get invalid build steps on
  aarch64?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1761114/+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 1761114] Re: systemd build error on aarch64 with "Failed to parse personality, ignoring: x86"

[Neil]

besides, exec-personality-aarch64.service get format issue in commit
12591863.

-Unit]
+[Unit]

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

Title:
  systemd build error on aarch64 with "Failed to parse personality,
  ignoring: x86"

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  download source code from 
https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21,
  build with `dpkg-buildpackage` on aarch64, and build break with the following 
messages:

  ```
  + test /tmp/test-exec_workingdirectory = /tmp/test-exec_workingdirectory
2 
[/root/neil/systemd/test/systemd-229.orig/test/test-execute/exec-personality-x86.service:7]
 Failed to parse personality, ignoring: x86
3 + uname -m
4 + c=aarch64
5 + test aarch64 = i686
6 exec-personality-x86.service: Main process exited, code=exited, 
status=1/FAILURE
7 exec-personality-x86.service: Unit entered failed state.
8 exec-personality-x86.service: Failed with result 'exit-code'.
9 Assertion 'service->main_exec_status.status == status_expected' failed at 
../src/test/test-execute.c:65, function check(). Aborting.
  ```

  it should run into x86 test case with:
  ```
  87  static void test_exec_personality(Manager *m) {
  88  #if defined(__x86_64__)
  89  test(m, "exec-personality-x86-64.service", 0, CLD_EXITED);
  90  
  91  #elif defined(__s390__)
  92  test(m, "exec-personality-s390.service", 0, CLD_EXITED);
  93  
  94  #else
  95  test(m, "exec-personality-x86.service", 0, CLD_EXITED);
  96  #endif
  97  }
  ```

  after checked upstream systemd source code,
  https://github.com/systemd/systemd/commit/12591863 will fix it.

  is this patch already applied? or I get invalid build steps on
  aarch64?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1761114/+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 1761114] [NEW] systemd build error on aarch64 with "Failed to parse personality, ignoring: x86"

[Neil]

Public bug reported:

download source code from 
https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21,
build with `dpkg-buildpackage` on aarch64, and build break with the following 
messages:

```
+ test /tmp/test-exec_workingdirectory = /tmp/test-exec_workingdirectory
  2 
[/root/neil/systemd/test/systemd-229.orig/test/test-execute/exec-personality-x86.service:7]
 Failed to parse personality, ignoring: x86
  3 + uname -m
  4 + c=aarch64
  5 + test aarch64 = i686
  6 exec-personality-x86.service: Main process exited, code=exited, 
status=1/FAILURE
  7 exec-personality-x86.service: Unit entered failed state.
  8 exec-personality-x86.service: Failed with result 'exit-code'.
  9 Assertion 'service->main_exec_status.status == status_expected' failed at 
../src/test/test-execute.c:65, function check(). Aborting.
```

it should run into x86 test case with:
```
87  static void test_exec_personality(Manager *m) {
88  #if defined(__x86_64__)
89  test(m, "exec-personality-x86-64.service", 0, CLD_EXITED);
90  
91  #elif defined(__s390__)
92  test(m, "exec-personality-s390.service", 0, CLD_EXITED);
93  
94  #else
95  test(m, "exec-personality-x86.service", 0, CLD_EXITED);
96  #endif
97  }
```

after checked upstream systemd source code,
https://github.com/systemd/systemd/commit/12591863 will fix it.

is this patch already applied? or I get invalid build steps on aarch64?

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: systemd

** Attachment added: "test-execute.log"
   
https://bugs.launchpad.net/bugs/1761114/+attachment/5101077/+files/test-execute.log

** Changed in: systemd (Ubuntu)
   Status: New => 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/1761114

Title:
  systemd build error on aarch64 with "Failed to parse personality,
  ignoring: x86"

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  download source code from 
https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21,
  build with `dpkg-buildpackage` on aarch64, and build break with the following 
messages:

  ```
  + test /tmp/test-exec_workingdirectory = /tmp/test-exec_workingdirectory
2 
[/root/neil/systemd/test/systemd-229.orig/test/test-execute/exec-personality-x86.service:7]
 Failed to parse personality, ignoring: x86
3 + uname -m
4 + c=aarch64
5 + test aarch64 = i686
6 exec-personality-x86.service: Main process exited, code=exited, 
status=1/FAILURE
7 exec-personality-x86.service: Unit entered failed state.
8 exec-personality-x86.service: Failed with result 'exit-code'.
9 Assertion 'service->main_exec_status.status == status_expected' failed at 
../src/test/test-execute.c:65, function check(). Aborting.
  ```

  it should run into x86 test case with:
  ```
  87  static void test_exec_personality(Manager *m) {
  88  #if defined(__x86_64__)
  89  test(m, "exec-personality-x86-64.service", 0, CLD_EXITED);
  90  
  91  #elif defined(__s390__)
  92  test(m, "exec-personality-s390.service", 0, CLD_EXITED);
  93  
  94  #else
  95  test(m, "exec-personality-x86.service", 0, CLD_EXITED);
  96  #endif
  97  }
  ```

  after checked upstream systemd source code,
  https://github.com/systemd/systemd/commit/12591863 will fix it.

  is this patch already applied? or I get invalid build steps on
  aarch64?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1761114/+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 972077] Re: apt repository disk format has race conditions

[Neil Roza]

affects me too

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

Title:
  apt repository disk format has race conditions

Status in APT:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released

Bug description:
  Apt archives are accessed over HTTP; this has resulted in a cluster of
  bugs (reported here, and upstream) about problems behind intercepting
  caches, problems with squid etc.

  There are 3 interlocking issues:
  A - mirror networks may be out of sync with each other (e.g. a file named on 
one mirror may no longer exist, or may not yet exist, on another mirror)
  B - updating files on a single mirror is not atomic - and even small windows 
of inconsistency will, given enough clients, cause headaches.
  C - caches exacerbate race conditions - when one happens, until the cached 
data expires, all clients of the cache will suffer from the race

  Solving this requires one of several things:
   - file system transactions
   - an archive format that requires only weakly ordered updates to the files 
at particular urls with the assumption that only one file may be observed to 
change at a time (because a lookup of file A, then B, may get a cache miss on A 
and a cache hit on B, so even if all clients strictly go A, then B, updates may 
still see old files when paths are reused).
   - super robust clients that repeatedly retry with progressively less cache 
friendly headers until they have a consistent view. (This is very tricky to do).

  It may be possible to do a tweak to the apt repository format though,
  which would allow publishing a race-free format in parallel with the
  existing layout, while clients migrate. To be safe against issue (A)
  the mirror network would need some care around handling of dns round-
  robin mirrors [to minimise the situation where referenced data is not
  available], but this should be doable - or alternatively clients doing
  'apt-get update' may need to be willing to retry to accommodate round-
  robin skew.

  What would such an archive format look like?
  It would have only one well known file name (InRelease), which would be 
internally signed. Rather than signing e.g. Packages.gz, it would sign a 
uniquely named packages and sources file - e.g. Packages-$HASH.gz or 
Packages-$serialno.gz.

  Backwards compatibility is achieved by using the same filenames for
  deb's and the like. We need to keep writing Packages.gz though, and
  Releases, until we no longer worry about old apt clients. We can
  optimise disk space a little by making Packages.gz a symlink to a
  Packages-$HASH.gz (and so on for Sources..), but it may be simpler and
  less prone to unexpected behaviour to keep using regular files.

  tl;dr
   * Unique file names for all unique file content with one exception
   * InRelease, a self-signed file that provides hashes and names the index 
files (Packages, Sources, Translations etc)
   * Coexists with existing archive layout

  Related bugs:
   * bug 804252: Please support InRelease files
   * bug 1430011: support apt by-hash mirrors

To manage notifications about this bug go to:
https://bugs.launchpad.net/apt/+bug/972077/+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 1737190] [NEW] updates

[Neil Campbell]

Public bug reported:

unable to update software

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-40.44-generic 4.10.17
Uname: Linux 4.10.0-40-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4.8
Architecture: amd64
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Dec  8 09:53:19 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Dell HD Graphics 520 [1028:06de]
InstallationDate: Installed on 2017-11-07 (30 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 003: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications 
Processor
 Bus 001 Device 002: ID 1bcf:28b8 Sunplus Innovation Technology Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Latitude E5470
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic.efi.signed 
root=UUID=528d7500-ba4c-479b-91af-06f8e0bcad74 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/15/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.7.3
dmi.board.name: 0P88J9
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.3:bd06/15/2016:svnDellInc.:pnLatitudeE5470:pvr:rvnDellInc.:rn0P88J9:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E5470
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
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.14-0ubuntu1

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


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

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

Title:
  updates

Status in xorg package in Ubuntu:
  New

Bug description:
  unable to update software

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-40.44-generic 4.10.17
  Uname: Linux 4.10.0-40-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.8
  Architecture: amd64
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Dec  8 09:53:19 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 520 [1028:06de]
  InstallationDate: Installed on 2017-11-07 (30 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications 
Processor
   Bus 001 Device 002: ID 1bcf:28b8 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude E5470
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic.efi.signed 
root=UUID=528d7500-ba4c-479b-91af-06f8e0bcad74 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.3
  dmi.board.name: 0P88J9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.3:bd06/15/2016:svnDellInc.:pnLatitudeE5470:pvr:rvnDellInc.:rn0P88J9:rvrA00:cvnDellInc.:ct9:cvr:
  dm

[Touch-packages] [Bug 1728165] [NEW] [PC-2170, Realtek ALC255, No microphone at all

[Neil Simmonds]

Public bug reported:

cant get the microphone to work at all.  mic works fine in my phone and
other computers - not in here.  mic is on my headphones - 3 way mini
jack

Alsamixer reports no capture device

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
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
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  neil   1212 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 27 23:16:15 2017
InstallationDate: Installed on 2017-10-21 (6 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
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/controlC0:  gdm 855 F pulseaudio
  neil   1212 F pulseaudio
Symptom_Jack: Black Headphone Out, Rear
Symptom_Type: No microphone at all
Title: [PC-2170, Realtek ALC255, Black Headphone Out, Rear] No microphone at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/20/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F4
dmi.board.asset.tag: Default string
dmi.board.name: MFLP7AP-00
dmi.board.vendor: GIGABYTE
dmi.board.version: 1.x
dmi.chassis.asset.tag: 7430791-001
dmi.chassis.type: 9
dmi.chassis.vendor: NOVATECH LTD
dmi.chassis.version: V1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd02/20/2017:svnNOVATECHLTD:pnPC-2170:pvrV1.0:rvnGIGABYTE:rnMFLP7AP-00:rvr1.x:cvnNOVATECHLTD:ct9:cvrV1.0:
dmi.product.family: AMI PLATFORM
dmi.product.name: PC-2170
dmi.product.version: V1.0
dmi.sys.vendor: NOVATECH LTD

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


** Tags: amd64 apport-bug artful wayland-session

** Description changed:

  cant get the microphone to work at all.  mic works fine in my phone and
  other computers - not in here.  mic is on my headphones - 3 way mini
  jack
  
  Alsamixer reports no capture device
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  neil   1212 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  neil   1212 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 27 23:16:15 2017
  InstallationDate: Installed on 2017-10-21 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  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/controlC0:  gdm 855 F pulseaudio
-   neil   1212 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  gdm 855 F pulseaudio
+   neil   1212 F pulseaudio
  Symptom_Jack: Black Headphone Out, Rear
- Symptom_Type: No sound at all
- Title: [PC-2170, Realtek ALC255, Black Headphone Out, Rear] No sound at all
+ Symptom_Type: No microphone at all
+ Title: [PC-2170, Realtek ALC255, Black Headphone Out, Rear] No microphone at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: MFLP7AP-00
  dmi.board.vendor: GIGABYTE
  dmi.board.version: 1.x
  dmi.chassis.asset.tag: 7430791-001
  dmi.chassis.type: 9
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd02/20/2017:svnNOVATECHLTD:pnPC-2170:pvrV1.0:rvnGIGABYTE:rnMFLP7AP-00:rvr1.x:cvnNOVATECHLTD:ct9:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: PC-2170
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD

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

Title:
  [PC-2170, Realtek ALC255, No microphone at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  cant get the microphone to work at all.  mic works fine in my phone
  and other computers - not in here.  mic is on my headphones - 3 way
  mini jack

  Alsamixer reports no capture device

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature:

[Touch-packages] [Bug 1724933] Re: I can't adjust display brightness

[Neil Woolford]

This appears to be quite an old issue with Optimus graphics. For me the 
workaround was to pass specific kernel parameters at boot time to inhibit acpi 
control of the backlight but allow intel_backlight control
I followed the instructions at 
https://nisheetlall.wordpress.com/2016/07/12/solved-brightness-fix-in-linux-for-optimus-laptops/
 which worked first time for me. Your mileage may of course vary - it happens 
that I have exactly the same Lenovo Z570 laptop as the author of those 
instructions.

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

Title:
  I can't adjust display brightness

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I'm using HP Pavilion DV6. After upgrade to Ubuntu 17.10 from 17.04 I
  can't adjust display brightness. when I press F2|F3 keys icon
  brightness appears, the controller moves but the brightness doesn't
  change.

  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
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 22:14:51 2017
  DistUpgraded: 2017-10-19 21:15:33,861 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.10.0-37-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:3388]
   Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 6730M/6770M/7690M 
XT] [1002:6740] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2017-06-18 (123 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
  dmi.bios.date: 04/25/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3388
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 10.25
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.13:bd04/25/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058F1124471610100:rvnHewlett-Packard:rn3388:rvr10.25:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 058F1124471610100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1724933/+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 1724933] Re: I can't adjust display brightness

[Neil Woolford]

I found that the brightness controls (via function key or sliders in power 
management) were changing the values in 
/sys/class/backlight/acpi_videos0/brightness, but nothing changed in 
/sys/class/backlight/intel_backlight/brightness.
When I edited the value in /sys/class/backlight/intel_backlight/brightness the 
display backlight brightness did change.
I also found that the display brightness could be changed in a unity session, 
(although not by function key).

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

Title:
  I can't adjust display brightness

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I'm using HP Pavilion DV6. After upgrade to Ubuntu 17.10 from 17.04 I
  can't adjust display brightness. when I press F2|F3 keys icon
  brightness appears, the controller moves but the brightness doesn't
  change.

  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
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 22:14:51 2017
  DistUpgraded: 2017-10-19 21:15:33,861 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.10.0-37-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:3388]
   Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 6730M/6770M/7690M 
XT] [1002:6740] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2017-06-18 (123 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
  dmi.bios.date: 04/25/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3388
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 10.25
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.13:bd04/25/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058F1124471610100:rvnHewlett-Packard:rn3388:rvr10.25:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 058F1124471610100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1724933/+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 1724919] [NEW] Bluetooth headphones only use A2DP when connected manually

[Neil Aspinall]

Public bug reported:

Issue with Sony MDR-1ABT Bluetooth headphones:
Once paired, the headphones will be connected automatically whenever they are 
switched on. However when connected this way, only the HSP/HFP profile will 
work and trying to change to A2DP in sound settings does nothing.
If the headphones are then manually disconnected and reconnected from Bluetooth 
settings, they will initially use HSP/HFP but then selecting A2DP in sound 
settings will successfully make them use A2DP.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  neil   1443 F pulseaudio
 /dev/snd/pcmC0D0c:   neil   1443 F...m pulseaudio
 /dev/snd/controlC0:  neil   1443 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 19 19:12:59 2017
InstallationDate: Installed on 2017-10-19 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: MDR-1ABT
Symptom_Type: None of the above
Title: [MDR-1ABT, playback] Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/06/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F5
dmi.board.asset.tag: Default string
dmi.board.name: Z270N-WIFI-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd07/06/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ270N-WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ270N-WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: Z270N-WIFI
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug artful

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

Title:
  Bluetooth headphones only use A2DP when connected manually

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Issue with Sony MDR-1ABT Bluetooth headphones:
  Once paired, the headphones will be connected automatically whenever they are 
switched on. However when connected this way, only the HSP/HFP profile will 
work and trying to change to A2DP in sound settings does nothing.
  If the headphones are then manually disconnected and reconnected from 
Bluetooth settings, they will initially use HSP/HFP but then selecting A2DP in 
sound settings will successfully make them use A2DP.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  neil   1443 F pulseaudio
   /dev/snd/pcmC0D0c:   neil   1443 F...m pulseaudio
   /dev/snd/controlC0:  neil   1443 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 19:12:59 2017
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: MDR-1ABT
  Symptom_Type: None of the above
  Title: [MDR-1ABT, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: Z270N-WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd07/06/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ270N-WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ270N-WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z270N-WIFI
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: https://launchpad.net/~to

[Touch-packages] [Bug 1668108] [NEW] Pulseaudio no sound, pavucontrol keeps flickering

[Neil Simon]

Public bug reported:

When I run pavucontrol, I get a flickering window (displays the controls
for a fraction of a second, then attempts to reconnect to pulseaudio).

I get no sound from my speakers.

Additionally, my speakers make a poping/thump sound when system starts.

If I use alsamixer, the Master is muted. I unmute it and hear a
pop/thump from the speakers.

If I try to start pulseaudio from the commandline (after stopping it), I
get the following:

$ pulseaudio -v
I: [pulseaudio] main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not 
permitted
I: [pulseaudio] main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not 
permitted
I: [pulseaudio] core-util.c: Successfully gained nice level -11.
I: [pulseaudio] main.c: This is PulseAudio 8.0
I: [pulseaudio] main.c: Page size is 4096 bytes
I: [pulseaudio] main.c: Machine ID is 585a29057506019e47b58dd24b8026db.
I: [pulseaudio] main.c: Session ID is c2.
I: [pulseaudio] main.c: Using runtime directory /run/user/500/pulse.
I: [pulseaudio] main.c: Using state directory /home/neil/.config/pulse.
I: [pulseaudio] main.c: Using modules directory /usr/lib/pulse-8.0/modules.
I: [pulseaudio] main.c: Running in system mode: no
I: [pulseaudio] main.c: System supports high resolution timers
I: [pulseaudio] cpu-x86.c: CPU flags: CMOV MMX SSE SSE2 SSE3 SSSE3 SSE4_1 
SSE4_2 MMXEXT 
I: [pulseaudio] svolume_mmx.c: Initialising MMX optimized volume functions.
I: [pulseaudio] remap_mmx.c: Initialising MMX optimized remappers.
I: [pulseaudio] svolume_sse.c: Initialising SSE2 optimized volume functions.
I: [pulseaudio] remap_sse.c: Initialising SSE2 optimized remappers.
I: [pulseaudio] sconv_sse.c: Initialising SSE2 optimized conversions.
I: [pulseaudio] svolume_orc.c: Initialising ORC optimized volume functions.
I: [pulseaudio] module-device-restore.c: Successfully opened database file 
'/home/neil/.config/pulse/585a29057506019e47b58dd24b8026db-device-volumes'.
I: [pulseaudio] module.c: Loaded "module-device-restore" (index: #0; argument: 
"").
I: [pulseaudio] module-stream-restore.c: Successfully opened database file 
'/home/neil/.config/pulse/585a29057506019e47b58dd24b8026db-stream-volumes'.
I: [pulseaudio] module.c: Loaded "module-stream-restore" (index: #1; argument: 
"").
I: [pulseaudio] module-card-restore.c: Successfully opened database file 
'/home/neil/.config/pulse/585a29057506019e47b58dd24b8026db-card-database'.
I: [pulseaudio] module.c: Loaded "module-card-restore" (index: #2; argument: 
"").
I: [pulseaudio] module.c: Loaded "module-augment-properties" (index: #3; 
argument: "").
I: [pulseaudio] module.c: Loaded "module-switch-on-port-available" (index: #4; 
argument: "").
I: [pulseaudio] (alsa-lib)utils.c: could not open configuration file 
/usr/share/alsa/ucm/HDA NVidia/HDA NVidia.conf
I: [pulseaudio] (alsa-lib)parser.c: error: could not parse configuration for 
card HDA NVidia
I: [pulseaudio] (alsa-lib)main.c: error: failed to import HDA NVidia use case 
configuration -2
I: [pulseaudio] alsa-ucm.c: UCM not available for card HDA NVidia
I: [pulseaudio] (alsa-lib)pcm_hw.c: open '/dev/snd/pcmC1D0c' failed (-2)
I: [pulseaudio] alsa-util.c: Error opening PCM device hw:1: No such file or 
directory
I: [pulseaudio] (alsa-lib)pcm_hw.c: open '/dev/snd/pcmC1D0c' failed (-2)
I: [pulseaudio] alsa-util.c: Error opening PCM device front:1: No such file or 
directory
I: [pulseaudio] (alsa-lib)pcm_hw.c: open '/dev/snd/pcmC1D0c' failed (-2)
I: [pulseaudio] alsa-util.c: Error opening PCM device hw:1: No such file or 
directory
I: [pulseaudio] (alsa-lib)pcm_hw.c: open '/dev/snd/pcmC1D1c' failed (-2)
I: [pulseaudio] alsa-util.c: Error opening PCM device iec958:1: No such file or 
directory
I: [pulseaudio] (alsa-lib)pcm_hw.c: open '/dev/snd/pcmC1D0p' failed (-2)
I: [pulseaudio] alsa-util.c: Error opening PCM device hw:1: No such file or 
directory
I: [pulseaudio] (alsa-lib)pcm_hw.c: open '/dev/snd/pcmC1D0p' failed (-2)
I: [pulseaudio] alsa-util.c: Error opening PCM device front:1: No such file or 
directory
I: [pulseaudio] (alsa-lib)pcm_hw.c: open '/dev/snd/pcmC1D0p' failed (-2)
I: [pulseaudio] alsa-util.c: Error opening PCM device hw:1: No such file or 
directory
I: [pulseaudio] (alsa-lib)pcm_hw.c: open '/dev/snd/pcmC1D0p' failed (-2)
I: [pulseaudio] alsa-util.c: Error opening PCM device surround21:1: No such 
file or directory
I: [pulseaudio] (alsa-lib)pcm_hw.c: open '/dev/snd/pcmC1D0p' failed (-2)
I: [pulseaudio] alsa-util.c: Error opening PCM device surround40:1: No such 
file or directory
I: [pulseaudio] (alsa-lib)pcm_hw.c: open '/dev/snd/pcmC1D0p' failed (-2)
I: [pulseaudio] alsa-util.c: Error opening PCM device surround41:1: No such 
file or directory
I: [pulseaudio] (alsa-lib)pcm_hw.c: open '/dev/snd/pcmC1D0p' failed (-2

[Touch-packages] [Bug 1663647] [NEW] cannot add printer

[Neil Mercer]

Public bug reported:

Terminal log follows

neil@neil-Latitude-D630:~$ lsmod | grep usb
usbhid 49152  0
hid   118784  2 hid_generic,usbhid
neil@neil-Latitude-D630:~$ tail -f /var/log/syslog
Feb 10 15:02:17 neil-Latitude-D630 avahi-daemon[960]: Registering new address 
record for fe80::221:5cff:fe6f:bbe5 on wlp12s0.*.
Feb 10 15:03:08 neil-Latitude-D630 wpa_supplicant[1147]: wlp12s0: WPA: Group 
rekeying completed with 58:98:35:15:e9:b9 [GTK=TKIP]
Feb 10 15:03:16 neil-Latitude-D630 systemd-timesyncd[463]: Synchronized to time 
server 91.189.94.4:123 (ntp.ubuntu.com).
Feb 10 15:03:16 neil-Latitude-D630 systemd[1581]: Time has been changed
Feb 10 15:03:16 neil-Latitude-D630 systemd[1]: Time has been changed
Feb 10 15:03:16 neil-Latitude-D630 systemd[1]: snapd.refresh.timer: Adding 5h 
11min 5.412159s random time.
Feb 10 15:03:16 neil-Latitude-D630 systemd[1]: apt-daily.timer: Adding 50min 
41.219140s random time.
Feb 10 15:13:09 neil-Latitude-D630 wpa_supplicant[1147]: wlp12s0: WPA: Group 
rekeying completed with 58:98:35:15:e9:b9 [GTK=TKIP]
Feb 10 15:17:01 neil-Latitude-D630 CRON[15040]: (root) CMD (   cd / && 
run-parts --report /etc/cron.hourly)
Feb 10 15:23:09 neil-Latitude-D630 wpa_supplicant[1147]: wlp12s0: WPA: Group 
rekeying completed with 58:98:35:15:e9:b9 [GTK=TKIP]
Feb 10 15:41:10 neil-Latitude-D630 kernel: [17268.068213] usb 2-4: new 
high-speed USB device number 4 using ehci-pci
Feb 10 15:41:10 neil-Latitude-D630 kernel: [17268.202919] usb 2-4: New USB 
device found, idVendor=04a9, idProduct=10d3
Feb 10 15:41:10 neil-Latitude-D630 kernel: [17268.202928] usb 2-4: New USB 
device strings: Mfr=1, Product=2, SerialNumber=3
Feb 10 15:41:10 neil-Latitude-D630 kernel: [17268.202934] usb 2-4: Product: 
iP2700 series
Feb 10 15:41:10 neil-Latitude-D630 kernel: [17268.202938] usb 2-4: 
Manufacturer: Canon
Feb 10 15:41:10 neil-Latitude-D630 kernel: [17268.202943] usb 2-4: 
SerialNumber: 234517
Feb 10 15:33:09 neil-Latitude-D630 wpa_supplicant[1147]: wlp12s0: WPA: Group 
rekeying completed with 58:98:35:15:e9:b9 [GTK=TKIP]
Feb 10 15:41:10 neil-Latitude-D630 mtp-probe: checking bus 2, device 4: 
"/sys/devices/pci:00/:00:1d.7/usb2/2-4"
Feb 10 15:41:10 neil-Latitude-D630 mtp-probe: bus: 2, device: 4 was not an MTP 
device
Feb 10 15:41:11 neil-Latitude-D630 systemd[1]: Created slice 
system-udev\x2dconfigure\x2dprinter.slice.
Feb 10 15:41:11 neil-Latitude-D630 systemd[1]: Starting Automatic USB/Bluetooth 
printer setup (-devices-pci:00-:00:1d.7-usb2-2\x2d4)...
Feb 10 15:41:11 neil-Latitude-D630 systemd[1]: Started CUPS Scheduler.
Feb 10 15:41:11 neil-Latitude-D630 systemd[1]: Reached target Printer.
Feb 10 15:41:11 neil-Latitude-D630 kernel: [17269.076606] usblp 2-4:1.0: 
usblp0: USB Bidirectional printer dev 4 if 0 alt 0 proto 2 vid 0x04A9 pid 0x10D3
Feb 10 15:41:11 neil-Latitude-D630 kernel: [17269.076648] usbcore: registered 
new interface driver usblp
Feb 10 15:41:11 neil-Latitude-D630 udev-configure-printer[15223]: add 
/devices/pci:00/:00:1d.7/usb2/2-4
Feb 10 15:41:11 neil-Latitude-D630 udev-configure-printer[15223]: device 
devpath is /devices/pci:00/:00:1d.7/usb2/2-4
Feb 10 15:41:11 neil-Latitude-D630 udev-configure-printer[15223]: MFG:Canon 
MDL:iP2700 series SERN:- serial:234517
Feb 10 15:41:12 neil-Latitude-D630 kernel: [17269.577898] audit: type=1400 
audit(1486741272.103:36): apparmor="DENIED" operation="sendmsg" 
profile="/usr/sbin/cupsd" name="/run/systemd/journal/socket" pid=15225 
comm="cupsd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0
Feb 10 15:41:12 neil-Latitude-D630 systemd[1]: cups.service: Main process 
exited, code=exited, status=1/FAILURE
Feb 10 15:41:12 neil-Latitude-D630 systemd[1]: cups.service: Unit entered 
failed state.
Feb 10 15:41:12 neil-Latitude-D630 systemd[1]: cups.service: Failed with result 
'exit-code'.
Feb 10 15:41:17 neil-Latitude-D630 udev-configure-printer[15223]: failed to 
connect to CUPS server; giving up
Feb 10 15:41:17 neil-Latitude-D630 systemd[1]: 
udev-configure-printer@-devices-pci:00-0000:00:1d.7-usb2-2\x2d4.service: 
Control process exited, code=exited status=1
Feb 10 15:41:17 neil-Latitude-D630 systemd[1]: Failed to start Automatic 
USB/Bluetooth printer setup (-devices-pci:00-:00:1d.7-usb2-2\x2d4).
Feb 10 15:41:17 neil-Latitude-D630 systemd[1]: 
udev-configure-printer@-devices-pci:00-:00:1d.7-usb2-2\x2d4.service: 
Unit entered failed state.
Feb 10 15:41:17 neil-Latitude-D630 systemd[1]: 
udev-configure-printer@-devices-pci:00-:00:1d.7-usb2-2\x2d4.service: 
Failed with result 'exit-code'.
^C
neil@neil-Latitude-D630:~$ lsusb
Bus 002 Device 004: ID 04a9:10d3 Canon, Inc. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 003: ID 0b97:7772 O2 Micro, Inc. OZ776 CCID Smartcard Reader
Bus 007 Device 002: ID 0b97:7761 O2 Micro, Inc. O

[Touch-packages] [Bug 1590892] Re: package util-linux 2.27.1-6ubuntu3.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Neil Rotherham]

I eventually got the updates to install by removing the WICID and WIFI Radar 
network scanners one of which I *think* was employing the runmbbservice 
(because the "mmb" bit seems to stand for "mobile broadband") Then I ran "sudo 
apt update && sudo apt upgrade" which then gave the following errors:
insserv: warning: script 'K01unlockgcstartup' missing LSB tags and overrides
insserv: warning: script 'K01gcstartup' missing LSB tags and overrides
insserv: warning: script 'S02lockgcstartup' missing LSB tags and overrides
insserv: warning: script 'lockgcstartup' missing LSB tags and overrides
insserv: warning: script 'gcstartup' missing LSB tags and overrid es
insserv: warning: script 'unlockgcstartup' missing LSB tags and overrides

I then ran "sudo dpkg --audit"
Which tipped me off to add empty LSP tags (after #!/bin/sh) to the latter three 
(the first three were links in a different directory to the second three) like 
this:

### BEGIN INIT INFO
# Provides :
# Required-Start :
# Required-Stop :
# Default-Start :
# Default-Stop  :
# Short-Description : Some info
# Description :   Some more info
### END INIT INFO

Then I ran "sudo dpkg --configure -a" which still seemed to complain
they were missing, but this time the "sudo dpkg --audit" command
returned nothing. Repeating "sudo apt update && sudo apt upgrade"
succeeded this time. Since I'm still not entirely sure what I have
managed to do, I think I've been very lucky. The moral of the story, I
think, is to be careful downloading free software even if it's through
the System Tools->software menu item.

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

Title:
  package util-linux 2.27.1-6ubuntu3.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  Could not install

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Jun  9 18:23:58 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-05-21 (18 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1590892/+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 1590892] Re: package util-linux 2.27.1-6ubuntu3.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Neil Rotherham]

What is runmbbservice and should I get rid of it?

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

Title:
  package util-linux 2.27.1-6ubuntu3.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  Could not install

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Jun  9 18:23:58 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-05-21 (18 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1590892/+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 1649288] [NEW] Unified ping doesn't support IPv4-mapped IPv6 addresses

[Neil Wilson]

Public bug reported:

ping to a mapped address


ping :::216.58.213.68

sends an ICMPv6 packet out onto the Internet with the mapped address in
the destination packet and the IPv6 address as the source. Mapped
addresses shouldn't appear on the public internet according to the RFC.

I would have expected this to use the IPv6 API to send an ICMP packet
over the v4 Internet on a dual stack machine in accordance with RFC4038.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: iputils-ping 3:20150815-2ubuntu3
ProcVersionSignature: User Name 4.8.0-30.32-generic 4.8.6
Uname: Linux 4.8.0-30-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Mon Dec 12 14:27:34 2016
SourcePackage: iputils
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug uec-images zesty

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

Title:
  Unified ping doesn't support IPv4-mapped IPv6 addresses

Status in iputils package in Ubuntu:
  New

Bug description:
  ping to a mapped address

  
  ping :::216.58.213.68

  sends an ICMPv6 packet out onto the Internet with the mapped address
  in the destination packet and the IPv6 address as the source. Mapped
  addresses shouldn't appear on the public internet according to the
  RFC.

  I would have expected this to use the IPv6 API to send an ICMP packet
  over the v4 Internet on a dual stack machine in accordance with
  RFC4038.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: iputils-ping 3:20150815-2ubuntu3
  ProcVersionSignature: User Name 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Mon Dec 12 14:27:34 2016
  SourcePackage: iputils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1649288/+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 1590892] Re: package util-linux 2.27.1-6ubuntu3.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Neil Rotherham]

Has anyone had a chance to look into this yet? It's been affecting me
for months - ever since I upgraded to Xenial, in fact.

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

Title:
  package util-linux 2.27.1-6ubuntu3.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  Could not install

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Jun  9 18:23:58 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-05-21 (18 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1590892/+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 1576692] Re: fully support package installation in systemd

[Neil Wilson]

Added both cloud-ini t and init-system-helpers from proposed to the
standard Xenial cloud image
(com.ubuntu.cloud:released:download/com.ubuntu.cloud:server:16.04:amd64/20160907.1/disk1.img)
on a suitably sized server.

Reset the cloud init with rm -rf /var/lib/cloud/instances/*, shutdown
the server and snapshotted the image.

Rebuilt a new server from the snapshotted image using the previously
failing postgresql user data and all is well. The new packages correct
my problem - bug 1611973

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

Title:
  fully support package installation in systemd

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in init-system-helpers package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Committed
Status in init-system-helpers source package in Xenial:
  Fix Committed

Bug description:
  in cloud-init users can install packages via cloud-config:
  #cloud-config
  packages: [apache2]

  Due to some intricacies of systemd and service installation that doesn't work 
all that well.
  We fixed the issue for simple services that do not have any dependencies on 
other services, or at least don't check those dependencies well under bug 
1575572.

  We'd like to have a way to fully support this in cloud-init.

  Related bugs:
   * bug 1575572:  apache2 fails to start if installed via cloud config (on 
Xenial)
   * bug 1611973: postgresql@9.5-main service not started if postgres installed 
via cloud-init
   * bug 1621336: snapd.boot-ok.service hangs eternally on cloud image upgrades 
(snapd packaging bug, but this cloud-init fix will workaround it)
   * bug 1620780: dev-sda2.device job running and times out

  SRU INFORMATION
  ===
  FIX for init-system-helpers: 
https://anonscm.debian.org/cgit/collab-maint/init-system-helpers.git/commit/?id=1460d6a02

  REGRESSION POTENTIAL for init-system-helpers: This changes invoke-rc.d
  and service, two very central pieces of packaging infrastructure.
  Errors in it will break installation/upgrades of packages or
  /etc/network/if-up.d/ hooks and the like. This changes the condition
  when systemd units get started without their dependencies, and the
  condition gets weakened. This means that behaviour in a booted system
  is unchanged, but during boot this could change the behaviour of if-
  up.d/ hooks (although they have never been defined well during boot
  anyway). However, I tested this change extensively in cloud images and
  desktop installations (particularly I recreated
  https://bugs.debian.org/777113 and confirmed that this approach also
  fixes it) and could not find any regression.

  TEST CASE (for both packages):
  Run
 lxc launch ubuntu-daily:x --config=user.user-data="$(printf 
"#cloud-config\npackages: [postgresql, samba, postfix]")" x1

  This will install all three packages, but "systemctl status
  postgresql@9.5-main" will not be running.

  Now prepare a new image with the proposed cloud-init and init-system-
  helpers:

 lxc launch ubuntu-daily:x xprep
 lxc exec xprep bash
 # enable -proposed and dist-upgrade, then poweroff
 lxc publish xprep x-proposed

  Now run the initial lxc launch again, but against that new x-proposed
  image instead of the standard daily:

lxc launch x-proposed --config=user.user-data="$(printf "#cloud-
  config\npackages: [postgresql, samba, postfix]")" x1

  You should now have "systemctl status postgresql@9.5-main" running.
  Directly after rebooting the instance, check that there are no hanging
  jobs (systemctl list-jobs), particularly networking.service, to ensure
  that https://bugs.debian.org/777113 did not come back.

  Also test interactively installing a package that ships a service,
  like "apache2", and verify that it starts properly after installation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1576692/+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 1576692] Re: fully support package installation in systemd

[Neil Wilson]

Have we back ported the init-system-helpers changes to Xenial?

I'm only seeing 1.29ubuntu2 this morning.

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

Title:
  fully support package installation in systemd

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in init-system-helpers package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Committed
Status in init-system-helpers source package in Xenial:
  In Progress

Bug description:
  in cloud-init users can install packages via cloud-config:
  #cloud-config
  packages: [apache2]

  Due to some intricacies of systemd and service installation that doesn't work 
all that well.
  We fixed the issue for simple services that do not have any dependencies on 
other services, or at least don't check those dependencies well under bug 
1575572.

  We'd like to have a way to fully support this in cloud-init.

  Related bugs:
   * bug 1575572:  apache2 fails to start if installed via cloud config (on 
Xenial)
   * bug 1611973: postgresql@9.5-main service not started if postgres installed 
via cloud-init
   * bug 1621336: snapd.boot-ok.service hangs eternally on cloud image upgrades 
(snapd packaging bug, but this cloud-init fix will workaround it)
   * bug 1620780: dev-sda2.device job running and times out

  SRU INFORMATION
  ===
  FIX for init-system-helpers: 
https://anonscm.debian.org/cgit/collab-maint/init-system-helpers.git/commit/?id=1460d6a02

  REGRESSION POTENTIAL for init-system-helpers: This changes invoke-rc.d
  and service, two very central pieces of packaging infrastructure.
  Errors in it will break installation/upgrades of packages or
  /etc/network/if-up.d/ hooks and the like. This changes the condition
  when systemd units get started without their dependencies, and the
  condition gets weakened. This means that behaviour in a booted system
  is unchanged, but during boot this could change the behaviour of if-
  up.d/ hooks (although they have never been defined well during boot
  anyway). However, I tested this change extensively in cloud images and
  desktop installations (particularly I recreated
  https://bugs.debian.org/777113 and confirmed that this approach also
  fixes it) and could not find any regression.

  TEST CASE (for both packages):
  Run
 lxc launch ubuntu-daily:x --config=user.user-data="$(printf 
"#cloud-config\npackages: [postgresql, samba, postfix]")" x1

  This will install all three packages, but "systemctl status
  postgresql@9.5-main" will not be running.

  Now prepare a new image with the proposed cloud-init and init-system-
  helpers:

 lxc launch ubuntu-daily:x xprep
 lxc exec xprep bash
 # enable -proposed and dist-upgrade, then poweroff
 lxc publish xprep x-proposed

  Now run the initial lxc launch again, but against that new x-proposed
  image instead of the standard daily:

lxc launch x-proposed --config=user.user-data="$(printf "#cloud-
  config\npackages: [postgresql, samba, postfix]")" x1

  You should now have "systemctl status postgresql@9.5-main" running.
  Directly after rebooting the instance, check that there are no hanging
  jobs (systemctl list-jobs), particularly networking.service, to ensure
  that https://bugs.debian.org/777113 did not come back.

  Also test interactively installing a package that ships a service,
  like "apache2", and verify that it starts properly after installation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1576692/+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 1620139] Re: factor buffers output when run interactively

[Neil Turton]

That seems like a good approach.  Thanks for looking at this.

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

Title:
  factor buffers output when run interactively

Status in coreutils package in Ubuntu:
  New

Bug description:
  When the "factor" utility is run without any arguments, it reads
  numbers from stdin and writes the factors to stdout.  One use case for
  this mode is to run factor in a terminal window and enter numbers
  manually.  This worked well in coreutils 8.23 and earlier.  However,
  in coreutils 8.25, the output of factor is buffered, making this mode
  of operation less useful.

  Notice that in the logs for version 8.25, all of the output occurs
  after end-of-file has been reached on stdin.

  I entered the following input:
factor --version
factor
5
7
9
^D

  bash$ factor --version
  factor (GNU coreutils) 8.23
  Copyright (C) 2014 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later .
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.

  Written by Paul Rubin, Torbjörn Granlund, and Niels Möller.
  bash$ factor
  5
  5: 5
  7
  7: 7
  9
  9: 3 3
  bash$ 

  bash$ factor --version
  factor (GNU coreutils) 8.25
  Copyright (C) 2016 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later .
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.

  Written by Paul Rubin, Torbjörn Granlund and Niels Möller.
  bash$ factor
  5
  7
  9
  5: 5
  7: 7
  9: 3 3
  bash$

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: coreutils 8.25-2ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Sep  4 23:32:33 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-08-13 (1118 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1620139/+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 1620139] [NEW] factor buffers output when run interactively

[Neil Turton]

Public bug reported:

When the "factor" utility is run without any arguments, it reads numbers
from stdin and writes the factors to stdout.  One use case for this mode
is to run factor in a terminal window and enter numbers manually.  This
worked well in coreutils 8.23 and earlier.  However, in coreutils 8.25,
the output of factor is buffered, making this mode of operation less
useful.

Notice that in the logs for version 8.25, all of the output occurs after
end-of-file has been reached on stdin.

I entered the following input:
  factor --version
  factor
  5
  7
  9
  ^D

bash$ factor --version
factor (GNU coreutils) 8.23
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later .
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Paul Rubin, Torbjörn Granlund, and Niels Möller.
bash$ factor
5
5: 5
7
7: 7
9
9: 3 3
bash$ 

bash$ factor --version
factor (GNU coreutils) 8.25
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later .
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Paul Rubin, Torbjörn Granlund and Niels Möller.
bash$ factor
5
7
9
5: 5
7: 7
9: 3 3
bash$

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: coreutils 8.25-2ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: KDE
Date: Sun Sep  4 23:32:33 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-08-13 (1118 days ago)
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
SourcePackage: coreutils
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: coreutils (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 coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1620139

Title:
  factor buffers output when run interactively

Status in coreutils package in Ubuntu:
  New

Bug description:
  When the "factor" utility is run without any arguments, it reads
  numbers from stdin and writes the factors to stdout.  One use case for
  this mode is to run factor in a terminal window and enter numbers
  manually.  This worked well in coreutils 8.23 and earlier.  However,
  in coreutils 8.25, the output of factor is buffered, making this mode
  of operation less useful.

  Notice that in the logs for version 8.25, all of the output occurs
  after end-of-file has been reached on stdin.

  I entered the following input:
factor --version
factor
5
7
9
^D

  bash$ factor --version
  factor (GNU coreutils) 8.23
  Copyright (C) 2014 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later .
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.

  Written by Paul Rubin, Torbjörn Granlund, and Niels Möller.
  bash$ factor
  5
  5: 5
  7
  7: 7
  9
  9: 3 3
  bash$ 

  bash$ factor --version
  factor (GNU coreutils) 8.25
  Copyright (C) 2016 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later .
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.

  Written by Paul Rubin, Torbjörn Granlund and Niels Möller.
  bash$ factor
  5
  7
  9
  5: 5
  7: 7
  9: 3 3
  bash$

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: coreutils 8.25-2ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Sep  4 23:32:33 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-08-13 (1118 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1620139/+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 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

[Neil Woolford]

I can confirm that /sys/device/platform/dock.0 does not exist on my
system.

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

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+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 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

[Neil Woolford]

Behaviour is not correct, nor was anything in my post #52 intended to
suggest that it is.

See the next couple of posts by Sebastian Bacher and myself for a full
and accurate description of the problem.

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

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+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 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

[Neil Woolford]

@seb128

"You have a laptop not connected to an external display and configured
in settings to suspend on lid close (battery/ac) but it doesn't suspend
when you close the lid? Suspending through the menu works though and
settings HandleLidSwitchDocked=suspend makes it suspend on lid close"

Yes, that's an absolutely correct summary of the problem and the
conditions under which it occurs.

I've now also tested from a vt login (Ctrl-Alt-F1) and again the system
doesn't suspend on lid closed unless HandleLidSwitchDocked=suspend is
set

I note that I didn't have to log in when resuming the vt, whereas using
the gui I need to go through the normal graphical greeter/login. When I
closed the vt and returned to the Unity gui after this test, the Unity
gui presented me with the greeter/login. I expect to see this login page
and have to enter my password after a suspend, this is consistent with
my settings.

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

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+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 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

[Neil Woolford]

@seb128

Yes, the bug is present with the default configuration file, but lid
close to suspend (from unity) works fine if I change the configuration.

In both the bug and functioning conditions the backlight turns off when
the lid is closed.

I will test behaviour from a console log-in later today.


** Attachment added: "unity-settings-daemon.log"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+attachment/4661238/+files/unity-settings-daemon.log

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

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in systemd package in Ubuntu:
  New

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+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 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

[Neil Woolford]

@pitti

neilw@NWPS-LAP:~$ ls /sys/class/drm/
card0   card0-LVDS-1  controlD64  ttm
card0-HDMI-A-1  card0-VGA-1   renderD128  version


neilw@NWPS-LAP:~$ grep -r . /sys/class/drm/*/enabled
/sys/class/drm/card0-HDMI-A-1/enabled:disabled
/sys/class/drm/card0-LVDS-1/enabled:enabled
/sys/class/drm/card0-VGA-1/enabled:disabled
neilw@NWPS-LAP:~$

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

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in systemd package in Ubuntu:
  New

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+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 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

[Neil Woolford]

Ok, I tried;

journalctl |grep systemd > somekindoflog.log

The result is attached.

** Attachment added: "Result of "journalctl |grep systemd > somekindoflog.log""
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+attachment/4660832/+files/somekindoflog.log

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

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+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 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

[Neil Woolford]

System left in buggy state, debug enabled in system.conf, system
rebooted.

neilw@NWPS-LAP:~$ ls /sys/class/drm/
card0   card0-LVDS-1  controlD64  ttm
card0-HDMI-A-1  card0-VGA-1   renderD128  version
neilw@NWPS-LAP:~$ cat /sys/class/drm/*/enabled
disabled
enabled
disabled
neilw@NWPS-LAP:~$ 

Try to suspend by lid closure.

neilw@NWPS-LAP:~$ journalctl 
-- Logs begin at Wed 2016-05-11 17:13:59 BST, end at Wed 2016-05-11 17:20:13 BST
May 11 17:13:59 NWPS-LAP systemd-journald[227]: Runtime journal (/run/log/journa
May 11 17:14:00 NWPS-LAP kernel: Initializing cgroup subsys cpuset
May 11 17:14:00 NWPS-LAP kernel: Initializing cgroup subsys cpu
May 11 17:14:00 NWPS-LAP kernel: Initializing cgroup subsys cpuacct
May 11 17:14:00 NWPS-LAP kernel: Linux version 4.4.0-22-generic (buildd@lcy01-32
May 11 17:14:00 NWPS-LAP kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22
May 11 17:14:00 NWPS-LAP kernel: KERNEL supported cpus:
May 11 17:14:00 NWPS-LAP kernel:   Intel GenuineIntel
May 11 17:14:00 NWPS-LAP kernel:   AMD AuthenticAMD
May 11 17:14:00 NWPS-LAP kernel:   Centaur CentaurHauls
May 11 17:14:00 NWPS-LAP kernel: tseg: 00dfc0
May 11 17:14:00 NWPS-LAP kernel: x86/fpu: Legacy x87 FPU detected.
May 11 17:14:00 NWPS-LAP kernel: x86/fpu: Using 'lazy' FPU context switches.
May 11 17:14:00 NWPS-LAP kernel: e820: BIOS-provided physical RAM map:
May 11 17:14:00 NWPS-LAP kernel: BIOS-e820: [mem 0x-0x00
May 11 17:14:00 NWPS-LAP kernel: BIOS-e820: [mem 0x0009f400-0x00
May 11 17:14:00 NWPS-LAP kernel: BIOS-e820: [mem 0x000e-0x00
May 11 17:14:00 NWPS-LAP kernel: BIOS-e820: [mem 0x0010-0xdf
May 11 17:14:00 NWPS-LAP kernel: BIOS-e820: [mem 0xdf8bf000-0xdf
May 11 17:14:00 NWPS-LAP kernel: BIOS-e820: [mem 0xdfabf000-0xdf
May 11 17:14:00 NWPS-LAP kernel: BIOS-e820: [mem 0xdfbbf000-0xdf
May 11 17:14:00 NWPS-LAP kernel: BIOS-e820: [mem 0xdfbff000-0xdf
lines 1-23

I'm afraid journalctl is new to me; is that the output you need, or do
you want me to attach the runtime journal mentioned in the first line
after the header?

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

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+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 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

[Neil Woolford]

neilw@NWPS-LAP:/etc/systemd$ sleep 10; systemd-inhibit

//Lid closed, count to ten and open again to find...

 Who: Telepathy (UID 1000/neilw, PID 1729/mission-control)
What: shutdown:sleep
 Why: Disconnecting IM accounts before suspend/shutdown...
Mode: delay

 Who: neilw (UID 1000/neilw, PID 1448/unity-settings-)
What: handle-power-key:handle-suspend-key:handle-hibernate-key
 Why: GNOME handling keypresses
Mode: block

 Who: NetworkManager (UID 0/root, PID 2218/NetworkManager)
What: sleep
 Why: NetworkManager needs to turn off networks
Mode: delay

 Who: Unity (UID 1000/neilw, PID 1463/compiz)
What: sleep
 Why: Unity needs to lock the screen
Mode: delay

 Who: neilw (UID 1000/neilw, PID 1448/unity-settings-)
What: sleep
 Why: GNOME needs to lock the screen
Mode: delay

5 inhibitors listed.

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

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+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 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

[Neil Woolford]

I've reinstated the workaround and run the requested commands again.

As far as I can see, the output of all three is exactly the same as in
the bug condition, apart from the items in the inhibitors list being
shown in a different order.

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

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+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 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

[Neil Woolford]

Ok.

Commented out the  HandleLidSwitchDocked=suspend line and restarted
systemd-logind.

Closed lid, waited a minute, the bug showed itself, the system did not
suspend.

neilw@NWPS-LAP:/etc/systemd$ systemd-inhibit
 Who: Unity (UID 1000/neilw, PID 1463/compiz)
What: sleep
 Why: Unity needs to lock the screen
Mode: delay

 Who: neilw (UID 1000/neilw, PID 1448/unity-settings-)
What: handle-power-key:handle-suspend-key:handle-hibernate-key
 Why: GNOME handling keypresses
Mode: block

 Who: neilw (UID 1000/neilw, PID 1448/unity-settings-)
What: sleep
 Why: GNOME needs to lock the screen
Mode: delay

 Who: Telepathy (UID 1000/neilw, PID 1729/mission-control)
What: shutdown:sleep
 Why: Disconnecting IM accounts before suspend/shutdown...
Mode: delay

 Who: NetworkManager (UID 0/root, PID 2218/NetworkManager)
What: sleep
 Why: NetworkManager needs to turn off networks
Mode: delay

5 inhibitors listed.

neilw@NWPS-LAP:/etc/systemd$ xrandr
Screen 0: minimum 320 x 200, current 1366 x 768, maximum 8192 x 8192
LVDS connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 
344mm x 194mm
   1366x768  60.07*+  40.04  
   1280x720  59.86  
   1152x768  59.78  
   1024x768  59.92  
   800x600   59.86  
   848x480   59.66  
   720x480   59.71  
   640x480   59.38  
HDMI-0 disconnected (normal left inverted right x axis y axis)
VGA-0 disconnected (normal left inverted right x axis y axis)

neilw@NWPS-LAP:/etc/systemd$ loginctl
   SESSIONUID USER SEAT
c2   1000 neilwseat0   

1 sessions listed.

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

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+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 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

[Neil Woolford]

The problem persists after sorting the oddity with the unity-settings-
daemon, which appears to have been a one-off problem. (See bug #1577906
for more detail.)

Now I find that suspend only works if "HandleLidSwitchDocked=suspend" is
in logind.conf.

Without that I return to the bug condition.

In the bug condition suspend works fine from the session indicator.


neilw@NWPS-LAP:~$ systemd-inhibit
 Who: neilw (UID 1000/neilw, PID 1558/unity-settings-)
What: handle-power-key:handle-suspend-key:handle-hibernate-key
 Why: GNOME handling keypresses
Mode: block

 Who: NetworkManager (UID 0/root, PID 2267/NetworkManager)
What: sleep
 Why: NetworkManager needs to turn off networks
Mode: delay

 Who: Telepathy (UID 1000/neilw, PID 1797/mission-control)
What: shutdown:sleep
 Why: Disconnecting IM accounts before suspend/shutdown...
Mode: delay

 Who: neilw (UID 1000/neilw, PID 1558/unity-settings-)
What: sleep
 Why: GNOME needs to lock the screen
Mode: delay

 Who: Unity (UID 1000/neilw, PID 1566/compiz)
What: sleep
 Why: Unity needs to lock the screen
Mode: delay

5 inhibitors listed.



** Attachment added: "As requested in post #22"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+attachment/4655927/+files/journal.txt

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

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+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 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

[Neil Woolford]

On my HP255G1 I have six inhibitors listed, the two blocks being;

 Who: neilw (UID 1000/neilw, PID 1669/unity-settings-)
What: handle-power-key:handle-suspend-key:handle-hibernate-key
 Why: GNOME handling keypresses
Mode: block


 Who: neilw (UID 1000/neilw, PID 1669/unity-settings-)
What: handle-lid-switch
 Why: Multiple displays attached
Mode: block

However, I certainly don't have multiple displays attached.

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

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+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 1477130] Re: timedatectl fails inside container

[Neil Hooey]

I have the same issue, with dbus installed.

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

Title:
  timedatectl fails inside container

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  lxc-attach -n mycont -- timedatectl
  Failed to create bus connection: No such file or directory

  while on the host timedatectl works just fine.

  lxc Version: 1.1.2-0ubuntu3 on ubuntu 15.04 x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1477130/+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 1549783] Re: Indicator shows "Tomorrow" for an alarm happening today when checked after midnight

[Neil McPhail]

** Attachment added: "Clock app show the alarm correctly"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1549783/+attachment/4580806/+files/screenshot20160224_012320048.png

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

Title:
  Indicator shows "Tomorrow" for an alarm happening today when checked
  after midnight

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  BQ E4.5 (krillin) running OTA9.1

  I have 2 recurring alarms set for 0730 and 0800. If I pull down the
  clock indicator bar after midnight, the 0730 alarm is listed as
  "Tomorrow". The Clock app lists the alarm correctly (although, if I
  rememebr correctly, there was previously a bug where the clock app
  would get this wrong too). The alarm functions correctly, but the
  indicator is unsettling.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1549783/+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 1549783] [NEW] Indicator shows "Tomorrow" for an alarm happening today when checked after midnight

[Neil McPhail]

Public bug reported:

BQ E4.5 (krillin) running OTA9.1

I have 2 recurring alarms set for 0730 and 0800. If I pull down the
clock indicator bar after midnight, the 0730 alarm is listed as
"Tomorrow". The Clock app lists the alarm correctly (although, if I
rememebr correctly, there was previously a bug where the clock app would
get this wrong too). The alarm functions correctly, but the indicator is
unsettling.

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

** Attachment added: "Screenshot of indicator showing wrong day for alarm"
   
https://bugs.launchpad.net/bugs/1549783/+attachment/4580805/+files/screenshot20160224_012251931.png

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

Title:
  Indicator shows "Tomorrow" for an alarm happening today when checked
  after midnight

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  BQ E4.5 (krillin) running OTA9.1

  I have 2 recurring alarms set for 0730 and 0800. If I pull down the
  clock indicator bar after midnight, the 0730 alarm is listed as
  "Tomorrow". The Clock app lists the alarm correctly (although, if I
  rememebr correctly, there was previously a bug where the clock app
  would get this wrong too). The alarm functions correctly, but the
  indicator is unsettling.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1549783/+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 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth

[Neil McPhail]

And the syslog...

** Attachment added: "bluetooth_syslog"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1435040/+attachment/4527538/+files/bluetooth_syslog

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

Title:
  Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  With my FORD Focus Car, pairing does not work. The bluetooth system in
  the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition"
  and then prompts me to connect with a 4-digit pin code, but the Ubuntu
  phone doesn't react at all and after a while the car system says that
  it failed to connect.

  image: 20150310-3201c0a
  KRILIN01A-S15A_BQ_L100EN_2020_150312
  OS Build 20

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+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 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth

[Neil McPhail]

I cannot connect to the unit in my Hyundai i40, and switching to the
latest rc-proposed with bluez5 hasn't changed anything.

Symptoms:
(1) When car unit is asked to search for devices, the phone is not seen at all. 
My other bluetooth devices get picked up by this search. I have checked, and 
the Ubuntu phone should be advertising
(2) Putting my car into listening mode, my phone can see it as "i40". If I try 
to connect, I get the PIN input screen on my phone but nothing happens after I 
input my PIN. The phone says the i40 is "disconnected" and the car doesn't 
register anything at all.

I have attached debugging info as per
https://wiki.ubuntu.com/DebuggingBluetooth.

** Attachment added: "bluetoothctl_dump.txt"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1435040/+attachment/4527537/+files/bluetoothctl_dump.txt

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

Title:
  Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  With my FORD Focus Car, pairing does not work. The bluetooth system in
  the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition"
  and then prompts me to connect with a 4-digit pin code, but the Ubuntu
  phone doesn't react at all and after a while the car system says that
  it failed to connect.

  image: 20150310-3201c0a
  KRILIN01A-S15A_BQ_L100EN_2020_150312
  OS Build 20

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+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 1515995] Re: Screen

[Neil Widdowson]

Hi Christopher, there is no change in using the nouveau default driver.

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

Title:
  Screen

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I am trying out Kubuntu at the moment and I have noticed that when watching 
videos they flicker. I have tried the different options in the 'Compositor 
Settings for Desktop Effects' Tearing Prevention and none seem to make a 
difference other than that if I put it on automatic, the top half of the screen 
flickers, and with 'full screen repaints' the whole screen flickers. I have 
tried the official Nvidia driver (352), the one from software centre and the 
default one - all make the video flicker in full screen. I had the same problem 
while using Linux Mint Mate, but not while using the Cinnamon Desktop, I also 
don't remember the problem occurring while using Ubuntu Unity Desktop.
  I am fairly new to Linux  so I don't know too much about how to go about 
finding out the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  352.41  Fri Aug 21 23:09:52 
PDT 2015
   GCC version:  gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2)
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  BootLog:
   fsck from util-linux 2.26.2
   /dev/sdb2: clean, 266511/13574144 files, 7382798/54296320 blocks
  CurrentDesktop: KDE
  Date: Fri Nov 13 12:47:42 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: kubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.2.0-18-generic, x86_64: installed
   nvidia-352-updates, 352.41, 4.2.0-18-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation Device [10de:0984]
  InstallationDate: Installed on 2015-11-12 (0 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: MSI MS-7850
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic.efi.signed 
root=UUID=43b80561-2236-4234-9459-091517df6ac9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.8
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-G41 PC Mate(MS-7850)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.8:bd07/21/2014:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnZ87-G41PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7850
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Fri Nov 13 10:44:18 2015
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.17.2-1ubuntu9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1515995/+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 1515995] Re: Screen

[Neil Widdowson]

While I've been watching videos online, they haven't flickered, but they
have had tears in them.

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

Title:
  Screen

Status in xorg package in Ubuntu:
  New

Bug description:
  I am trying out Kubuntu at the moment and I have noticed that when watching 
videos they flicker. I have tried the different options in the 'Compositor 
Settings for Desktop Effects' Tearing Prevention and none seem to make a 
difference other than that if I put it on automatic, the top half of the screen 
flickers, and with 'full screen repaints' the whole screen flickers. I have 
tried the official Nvidia driver (352), the one from software centre and the 
default one - all make the video flicker in full screen. I had the same problem 
while using Linux Mint Mate, but not while using the Cinnamon Desktop, I also 
don't remember the problem occurring while using Ubuntu Unity Desktop.
  I am fairly new to Linux  so I don't know too much about how to go about 
finding out the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  352.41  Fri Aug 21 23:09:52 
PDT 2015
   GCC version:  gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2)
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  BootLog:
   fsck from util-linux 2.26.2
   /dev/sdb2: clean, 266511/13574144 files, 7382798/54296320 blocks
  CurrentDesktop: KDE
  Date: Fri Nov 13 12:47:42 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: kubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.2.0-18-generic, x86_64: installed
   nvidia-352-updates, 352.41, 4.2.0-18-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation Device [10de:0984]
  InstallationDate: Installed on 2015-11-12 (0 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: MSI MS-7850
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic.efi.signed 
root=UUID=43b80561-2236-4234-9459-091517df6ac9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.8
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-G41 PC Mate(MS-7850)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.8:bd07/21/2014:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnZ87-G41PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7850
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Fri Nov 13 10:44:18 2015
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.17.2-1ubuntu9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1515995/+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 1515995] [NEW] Screen

[Neil Widdowson]

Public bug reported:

I am trying out Kubuntu at the moment and I have noticed that when watching 
videos they flicker. I have tried the different options in the 'Compositor 
Settings for Desktop Effects' Tearing Prevention and none seem to make a 
difference other than that if I put it on automatic, the top half of the screen 
flickers, and with 'full screen repaints' the whole screen flickers. I have 
tried the official Nvidia driver (352), the one from software centre and the 
default one - all make the video flicker in full screen. I had the same problem 
while using Linux Mint Mate, but not while using the Cinnamon Desktop, I also 
don't remember the problem occurring while using Ubuntu Unity Desktop.
I am fairly new to Linux  so I don't know too much about how to go about 
finding out the problem.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
Uname: Linux 4.2.0-18-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  352.41  Fri Aug 21 23:09:52 
PDT 2015
 GCC version:  gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2)
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
BootLog:
 fsck from util-linux 2.26.2
 /dev/sdb2: clean, 266511/13574144 files, 7382798/54296320 blocks
CurrentDesktop: KDE
Date: Fri Nov 13 12:47:42 2015
DistUpgraded: Fresh install
DistroCodename: wily
DistroVariant: kubuntu
DkmsStatus:
 bbswitch, 0.7, 4.2.0-18-generic, x86_64: installed
 nvidia-352-updates, 352.41, 4.2.0-18-generic, x86_64: installed
GraphicsCard:
 NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: NVIDIA Corporation Device [10de:0984]
InstallationDate: Installed on 2015-11-12 (0 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: MSI MS-7850
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic.efi.signed 
root=UUID=43b80561-2236-4234-9459-091517df6ac9 ro quiet splash vt.handoff=7
SourcePackage: xorg
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/21/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.8
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z87-G41 PC Mate(MS-7850)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.8:bd07/21/2014:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnZ87-G41PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.name: MS-7850
dmi.product.version: 1.0
dmi.sys.vendor: MSI
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Fri Nov 13 10:44:18 2015
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.17.2-1ubuntu9

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


** Tags: amd64 apport-bug kubuntu possible-manual-nvidia-install wily

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

Title:
  Screen

Status in xorg package in Ubuntu:
  New

Bug description:
  I am trying out Kubuntu at the moment and I have noticed that when watching 
videos they flicker. I have tried the different options in the 'Compositor 
Settings for Desktop Effects' Tearing Prevention and none seem to make a 
difference other than that if I put it on automatic, the top half of the screen 
flickers, and with 'full screen repaints' the whole screen flickers. I have 
tried the official Nvidia driver (352), the one from software centre and the 
default one - all make the video flicker in full screen. I had the same problem 
while using Linux Mint Mate, but not while using the Cinnamon Desktop, I also 
don't remember the problem occurring while using Ubuntu Unity Desktop.
  I am fairly new to Linux  so I don't know too much about how to go about 
finding out the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Pack

[Touch-packages] [Bug 1501668] Re: ListItem leadingActions have odd behaviour

[Neil McPhail]

This seems to be fixed with OTA-7

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Fix Released

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

Title:
  ListItem leadingActions have odd behaviour

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released

Bug description:
  I _think_ this is a bug in the ListItem leadingActions implementation,
  but please move this if it is another component.

  Krillin running default channel (Ubuntu 15.04 r25 as per most recent
  OTA update).

  In the browser app "bookmarks" page and the clock app "alarms" page,
  the listed items can be dragged to the right to reveal a "trash" icon.
  Clicking on that icon will often just remove the icon, rather than the
  list item. The listed item will only be deleted if the initial right-
  drag was all the way to the middle of the screen.

  Example:
  - Open the Clock app and create a new alarm
  - drag the alarm far enough to the right for the "trash" item to be visible. 
Release and allow to settle. The item should be in the "ready to be deleted" 
state
  - Click the trash icon. *The icon will disappear but the item will not*.

  - drag the alarm much further to the right (at least to the middle of the 
screen), release and allow to settle. Once again, it will be in the "ready to 
be deleted" state and will be visually identical to the above
  - Click the trash icon. *The icon and the item will be deleted, which is 
correct behaviour*.

  
  As this affects more than one app, I think the bug is likely to be in the 
component rather than the app.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1501668/+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 1442035] Re: mediascanner-service constantly consumes 50-100% of CPU in Bq Aquarius 4.5

[Neil McPhail]

I wonder if this is related to
https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1398614
which affects me on the desktop?

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

Title:
  mediascanner-service constantly consumes 50-100% of CPU in Bq Aquarius
  4.5

Status in mediascanner2 package in Ubuntu:
  New

Bug description:
  This is a new bug based on my comments in #1398614. I tried to use
  "adb shell ubuntu-bug mediascanner2.0" as per the documentation on
  reporting bugs on Ubuntu Touch but the command just hanged.

  What happens:

  I have about 10 GB of music on the SD card (FAT32) and mediascanner-
  service still takes up to 100% CPU after _several_hours_. This ruins
  the battery life. It stops if I remove the SD card.

  This might be due to the fact that mediascanner-service is in a crash
  loop and thus never finishes the scanning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1442035/+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 1398614] Re: mediascanner-service-2.0 using large amounts of CPU

[Neil McPhail]

Since pulling in mediascanner2.0 on wily with the ubuntu-sdk package, I
have mediascanner-service consuming a minimum of 10% of CPU at all
times, with frequent spikes to nearly 200%. My CPU is cooking nicely.

To put things in perspective, firefox with 15 open tabs is currently
consuming 3.3% of CPU.

Something is badly broken here.

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

Title:
  mediascanner-service-2.0 using large amounts of CPU

Status in mediascanner2 package in Ubuntu:
  Confirmed

Bug description:
  Each time I plug my external USB hard disk the mediascanner-service process 
is activ and is using large amount of CPU for long minutes without interruption.
  I have the same problem in utopic and vivid

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: mediascanner2.0 0.105+15.04.20141030.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Dec  3 00:29:43 2014
  InstallationDate: Installed on 2011-05-26 (1286 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  SourcePackage: mediascanner2
  UpgradeStatus: Upgraded to vivid on 2013-11-26 (371 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1398614/+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 1501668] Re: ListItem leadingActions have odd behaviour

[Neil McPhail]

This may be a duplicate of https://bugs.launchpad.net/ubuntu/+source
/ubuntu-ui-toolkit/+bug/1486008 , but I am not sure if it is the same
problem.

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

Title:
  ListItem leadingActions have odd behaviour

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  I _think_ this is a bug in the ListItem leadingActions implementation,
  but please move this if it is another component.

  Krillin running default channel (Ubuntu 15.04 r25 as per most recent
  OTA update).

  In the browser app "bookmarks" page and the clock app "alarms" page,
  the listed items can be dragged to the right to reveal a "trash" icon.
  Clicking on that icon will often just remove the icon, rather than the
  list item. The listed item will only be deleted if the initial right-
  drag was all the way to the middle of the screen.

  Example:
  - Open the Clock app and create a new alarm
  - drag the alarm far enough to the right for the "trash" item to be visible. 
Release and allow to settle. The item should be in the "ready to be deleted" 
state
  - Click the trash icon. *The icon will disappear but the item will not*.

  - drag the alarm much further to the right (at least to the middle of the 
screen), release and allow to settle. Once again, it will be in the "ready to 
be deleted" state and will be visually identical to the above
  - Click the trash icon. *The icon and the item will be deleted, which is 
correct behaviour*.

  
  As this affects more than one app, I think the bug is likely to be in the 
component rather than the app.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1501668/+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 1501668] [NEW] ListItem leadingActions have odd behaviour

[Neil McPhail]

Public bug reported:

I _think_ this is a bug in the ListItem leadingActions implementation,
but please move this if it is another component.

Krillin running default channel (Ubuntu 15.04 r25 as per most recent OTA
update).

In the browser app "bookmarks" page and the clock app "alarms" page, the
listed items can be dragged to the right to reveal a "trash" icon.
Clicking on that icon will often just remove the icon, rather than the
list item. The listed item will only be deleted if the initial right-
drag was all the way to the middle of the screen.

Example:
- Open the Clock app and create a new alarm
- drag the alarm far enough to the right for the "trash" item to be visible. 
Release and allow to settle. The item should be in the "ready to be deleted" 
state
- Click the trash icon. *The icon will disappear but the item will not*.

- drag the alarm much further to the right (at least to the middle of the 
screen), release and allow to settle. Once again, it will be in the "ready to 
be deleted" state and will be visually identical to the above
- Click the trash icon. *The icon and the item will be deleted, which is 
correct behaviour*.


As this affects more than one app, I think the bug is likely to be in the 
component rather than the app.

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

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

Title:
  ListItem leadingActions have odd behaviour

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  I _think_ this is a bug in the ListItem leadingActions implementation,
  but please move this if it is another component.

  Krillin running default channel (Ubuntu 15.04 r25 as per most recent
  OTA update).

  In the browser app "bookmarks" page and the clock app "alarms" page,
  the listed items can be dragged to the right to reveal a "trash" icon.
  Clicking on that icon will often just remove the icon, rather than the
  list item. The listed item will only be deleted if the initial right-
  drag was all the way to the middle of the screen.

  Example:
  - Open the Clock app and create a new alarm
  - drag the alarm far enough to the right for the "trash" item to be visible. 
Release and allow to settle. The item should be in the "ready to be deleted" 
state
  - Click the trash icon. *The icon will disappear but the item will not*.

  - drag the alarm much further to the right (at least to the middle of the 
screen), release and allow to settle. Once again, it will be in the "ready to 
be deleted" state and will be visually identical to the above
  - Click the trash icon. *The icon and the item will be deleted, which is 
correct behaviour*.

  
  As this affects more than one app, I think the bug is likely to be in the 
component rather than the app.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1501668/+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 1494804] Re: evolution-source-registry crashed with SIGABRT in g_assertion_message()

[Neil Padgett]

Sorry, I'm unable to do this; 15.10 was too unstable for me keep it on
my laptop, so I've removed it now.

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

Title:
  evolution-source-registry crashed with SIGABRT in
  g_assertion_message()

Status in evolution-data-server:
  Confirmed
Status in evolution-data-server package in Ubuntu:
  Confirmed

Bug description:
  Random crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: evolution-data-server 3.16.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Sep 11 16:29:44 2015
  ExecutablePath: /usr/lib/evolution/evolution-source-registry
  InstallationDate: Installed on 2015-09-11 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150911)
  ProcCmdline: /usr/lib/evolution/evolution-source-registry
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
  Signal: 6
  SourcePackage: evolution-data-server
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   e_source_get_extension () from /usr/lib/libedataserver-1.2.so.20
   ?? () from /usr/lib/libebackend-1.2.so.10
  Title: evolution-source-registry crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1494804/+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 893210] Re: [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

[Neil]

cat /proc/asound/card0/intel8x0
Intel8x0

Global control: 0xc002
Global status : 0x00700100
SDM   : 0x0008
AC'97 codecs ready: primary
AC'97 codecs SDIN : 0 0 0

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

Title:
  [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

Status in ALSA driver:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  fresh install of ubuntu studio and updates but internal speakers do
  not play. dell optiplex gx620 love ya

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: alsa-base 1.0.24+dfsg-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Card0.Amixer.info:
   Card hw:0 'ICH7'/'Intel ICH7 with AD1981B at irq 23'
 Mixer name : 'Analog Devices AD1981B'
 Components : 'AC97a:41445374'
 Controls  : 28
 Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'Device'/'C-Media Electronics Inc. USB Multimedia Audio Device at 
usb-:00:1d.7-4.1.4,'
 Mixer name : 'USB Mixer'
 Components : 'USB0d8c:0105'
 Controls  : 13
 Simple ctrls  : 6
  Date: Mon Nov 21 11:51:25 2011
  InstallationMedia: Ubuntu-Studio 11.10 "Oneiric Ocelot" - Release i386 
(20111011.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:ICH7 failed
  Symptom_Card: CM108 Audio Controller - USB Multimedia Audio Device
  Symptom_Type: No sound at all
  Title: [ICH4 - Intel ICH7, playback] No sound at all
  UpgradeStatus: Upgraded to oneiric on 2011-11-12 (8 days ago)
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0F8101
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0F8101:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/893210/+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 1497210] Re: [browser] There is no way to block adverts, web bugs and trackers in the web browser

[Neil McPhail]

Alternatively, a mechanism to alter /etc/hosts without having to remount
'/' would be welcome. This would permit advert blocking in all network
apps.

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

Title:
  [browser] There is no way to block adverts, web bugs and trackers in
  the web browser

Status in Canonical System Image:
  New
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  I would like to block trackers from being loaded by the web browser,
  with functionality something like Ghostery and / or uBlock Origin
  Firefox add ons.

  As a work-around, for now, you can install Privoxy and use that, this
  works very well, for example see https://ubuntu-
  phone.host1.webarch.net/wiki/Proxy_Web_Traffic -- of course this is
  far from ideal for non-technical users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1497210/+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 893210] Re: [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

[Neil]

are these correct so far?

analog-output-headphones.conf.patch
http://pastebin.com/cSZEpc10

analog-output-speaker.conf.patch
http://pastebin.com/0fXR5gmZ 

ac97_codec.h.patch
http://pastebin.com/mkj5tmzN

I need your help with the following section, i'm guessing goes in ac97_codec.h
but i dont know if it does or where in the file to edit:

diff --git a/sound/pci/ac97/ac97_patch.c b/sound/pci/ac97/ac97_patch.c
index f4234ed..581000c 100644
--- a/sound/pci/ac97/ac97_patch.c
+++ b/sound/pci/ac97/ac97_patch.c
@@ -1886,6 +1886,23 @@ static int patch_ad1981a(struct snd_ac97 *ac97)
 static const struct snd_kcontrol_new snd_ac97_ad198x_2cmic =
 AC97_SINGLE("Stereo Mic", AC97_AD_MISC, 6, 1, 0);
 
+#define AD198X_JS1_ST  0x08
+#define AD198X_JS0_ST  0x04
+
+void ad198x_handle_hp_jack(struct snd_ac97 *ac97)
+{
+   bool hp_plugged = (snd_ac97_read(ac97, AC97_AD_JACK_SPDIF) &
+   AD198X_JS1_ST) == AD198X_JS1_ST; 
+   snd_jack_report(ac97->hp_jack, hp_plugged ? SND_JACK_HEADPHONE : 0);
+}
+
+void ad198x_handle_lo_jack(struct snd_ac97 *ac97)
+{
+   bool lo_plugged = (snd_ac97_read(ac97, AC97_AD_JACK_SPDIF) &
+   AD198X_JS0_ST) == AD198X_JS0_ST; 
+   snd_jack_report(ac97->lo_jack, lo_plugged ? SND_JACK_LINEOUT : 0);
+}
+
 static int patch_ad1981b_specific(struct snd_ac97 *ac97)
 {
int err;
@@ -1894,8 +1911,23 @@ static int patch_ad1981b_specific(struct snd_ac97 *ac97)
return err;
if (check_list(ac97, ad1981_jacks_blacklist))
return 0;
-   return patch_build_controls(ac97, snd_ac97_ad1981x_jack_sense,
+   err = patch_build_controls(ac97, snd_ac97_ad1981x_jack_sense,
ARRAY_SIZE(snd_ac97_ad1981x_jack_sense));
+   if (err < 0)
+   return err;
+   if (( err = snd_jack_new(ac97->bus->card, "Headphone", 
SND_JACK_HEADPHONE,
+  &ac97->hp_jack, true, false)) < 0)
+   return err;
+   ad198x_handle_hp_jack(ac97);
+   if (( err = snd_jack_new(ac97->bus->card, "Line Out", SND_JACK_LINEOUT,
+  &ac97->lo_jack, true, false)) < 0)
+   return err;
+   ad198x_handle_lo_jack(ac97);
+   if (( err = snd_jack_new(ac97->bus->card, "SPEAKER", SND_JACK_LINEOUT,
+  &ac97->sp_jack, true, true)) < 0)
+   return err; 
+   snd_jack_report(ac97->sp_jack, SND_JACK_LINEOUT);
+   return 0;
 }
 
 static const struct snd_ac97_build_ops patch_ad1981b_build_ops = {

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

Title:
  [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

Status in ALSA driver:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  fresh install of ubuntu studio and updates but internal speakers do
  not play. dell optiplex gx620 love ya

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: alsa-base 1.0.24+dfsg-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Card0.Amixer.info:
   Card hw:0 'ICH7'/'Intel ICH7 with AD1981B at irq 23'
 Mixer name : 'Analog Devices AD1981B'
 Components : 'AC97a:41445374'
 Controls  : 28
 Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'Device'/'C-Media Electronics Inc. USB Multimedia Audio Device at 
usb-:00:1d.7-4.1.4,'
 Mixer name : 'USB Mixer'
 Components : 'USB0d8c:0105'
 Controls  : 13
 Simple ctrls  : 6
  Date: Mon Nov 21 11:51:25 2011
  InstallationMedia: Ubuntu-Studio 11.10 "Oneiric Ocelot" - Release i386 
(20111011.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:ICH7 failed
  Symptom_Card: CM108 Audio Controller - USB Multimedia Audio Device
  Symptom_Type: No sound at all
  Title: [ICH4 - Intel ICH7, playback] No sound at all
  UpgradeStatus: Upgraded to oneiric on 2011-11-12 (8 days ago)
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0F8101
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0F8101:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 893210] Re: [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

[Neil]

no sorry, still trying to figure out what goes where!

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

Title:
  [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

Status in ALSA driver:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  fresh install of ubuntu studio and updates but internal speakers do
  not play. dell optiplex gx620 love ya

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: alsa-base 1.0.24+dfsg-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Card0.Amixer.info:
   Card hw:0 'ICH7'/'Intel ICH7 with AD1981B at irq 23'
 Mixer name : 'Analog Devices AD1981B'
 Components : 'AC97a:41445374'
 Controls  : 28
 Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'Device'/'C-Media Electronics Inc. USB Multimedia Audio Device at 
usb-:00:1d.7-4.1.4,'
 Mixer name : 'USB Mixer'
 Components : 'USB0d8c:0105'
 Controls  : 13
 Simple ctrls  : 6
  Date: Mon Nov 21 11:51:25 2011
  InstallationMedia: Ubuntu-Studio 11.10 "Oneiric Ocelot" - Release i386 
(20111011.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:ICH7 failed
  Symptom_Card: CM108 Audio Controller - USB Multimedia Audio Device
  Symptom_Type: No sound at all
  Title: [ICH4 - Intel ICH7, playback] No sound at all
  UpgradeStatus: Upgraded to oneiric on 2011-11-12 (8 days ago)
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0F8101
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0F8101:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/893210/+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 893210] Re: [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

[Neil]

pactl list sinks
Sink #0
State: SUSPENDED
Name: alsa_output.pci-_00_1e.2.analog-stereo
Description: Built-in Audio Analogue Stereo
Driver: module-alsa-card.c
Sample Specification: s16le 2ch 48000Hz
Channel Map: front-left,front-right
Owner Module: 6
Mute: no
Volume: 0:   0% 1:   0%
0: -inf dB 1: -inf dB
balance 0.00
Base Volume:  63%
 -12.00 dB
Monitor Source: alsa_output.pci-_00_1e.2.analog-stereo.monitor
Latency: 0 usec, configured 0 usec
Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY 
Properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = "Intel ICH7"
alsa.id = "Intel ICH"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "0"
alsa.card = "0"
alsa.card_name = "Intel ICH7"
alsa.long_card_name = "Intel ICH7 with AD1981B at irq 23"
alsa.driver_name = "snd_intel8x0"
device.bus_path = "pci-:00:1e.2"
sysfs.path = "/devices/pci:00/:00:1e.2/sound/card0"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "27de"
device.product.name = "OptiPlex GX620"
device.form_factor = "internal"
device.string = "front:0"
device.buffering.buffer_size = "65536"
device.buffering.fragment_size = "65536"
device.access_mode = "mmap+timer"
device.profile.name = "analog-stereo"
device.profile.description = "Analogue Stereo"
device.description = "Built-in Audio Analogue Stereo"
alsa.mixer_name = "Analog Devices AD1981B"
alsa.components = "AC97a:41445374"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
Ports:
analog-output;output-amplifier-on: Analogue Output / Amplifier 
(priority: 9910)
analog-output;output-amplifier-off: Analogue Output / No 
Amplifier (priority: 9900)
analog-output-headphones;output-amplifier-on: Headphones / 
Amplifier (priority: 9010)
analog-output-headphones;output-amplifier-off: Headphones / No 
Amplifier (priority: 9000)
Active Port: analog-output;output-amplifier-off
Formats:
pcm
ouput successful from line out and headphones, not from internal speaker

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

Title:
  [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

Status in ALSA driver:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  fresh install of ubuntu studio and updates but internal speakers do
  not play. dell optiplex gx620 love ya

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: alsa-base 1.0.24+dfsg-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Card0.Amixer.info:
   Card hw:0 'ICH7'/'Intel ICH7 with AD1981B at irq 23'
 Mixer name : 'Analog Devices AD1981B'
 Components : 'AC97a:41445374'
 Controls  : 28
 Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'Device'/'C-Media Electronics Inc. USB Multimedia Audio Device at 
usb-:00:1d.7-4.1.4,'
 Mixer name : 'USB Mixer'
 Components : 'USB0d8c:0105'
 Controls  : 13
 Simple ctrls  : 6
  Date: Mon Nov 21 11:51:25 2011
  InstallationMedia: Ubuntu-Studio 11.10 "Oneiric Ocelot" - Release i386 
(20111011.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:ICH7 failed
  Symptom_Card: CM108 Audio Controller - USB Multimedia Audio Device
  Symptom_Type: No sound at all
  Title: [ICH4 - Intel ICH7, playback] No sound at all
  UpgradeStatus: Upgraded to oneiric on 2011-11-12 (8 days ago)
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0F8101
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0F8101:rvr:cvnD

[Touch-packages] [Bug 893210] Re: [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

[Neil]

you have to add element master mono to speaker.conf

there appears not to be a speaker.conf
there is;
/usr/share/alsa/cards/PC-Speaker.conf
/usr/share/pulseaudio/alsa-mixer/paths/analog-output-desktop-speaker.conf
/usr/share/pulseaudio/alsa-mixer/paths/analog-output-speaker.conf
/usr/share/pulseaudio/alsa-mixer/profile-sets/force-speaker.conf

you also need to implement headphone jack and line out jack detection
kctl and internal speaker phantom jack using bit 2 and bit 3 of
AC97_AD_JACK_SPDIF register

Need your guidance, do not know how to implement

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

Title:
  [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

Status in ALSA driver:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  fresh install of ubuntu studio and updates but internal speakers do
  not play. dell optiplex gx620 love ya

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: alsa-base 1.0.24+dfsg-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Card0.Amixer.info:
   Card hw:0 'ICH7'/'Intel ICH7 with AD1981B at irq 23'
 Mixer name : 'Analog Devices AD1981B'
 Components : 'AC97a:41445374'
 Controls  : 28
 Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'Device'/'C-Media Electronics Inc. USB Multimedia Audio Device at 
usb-:00:1d.7-4.1.4,'
 Mixer name : 'USB Mixer'
 Components : 'USB0d8c:0105'
 Controls  : 13
 Simple ctrls  : 6
  Date: Mon Nov 21 11:51:25 2011
  InstallationMedia: Ubuntu-Studio 11.10 "Oneiric Ocelot" - Release i386 
(20111011.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:ICH7 failed
  Symptom_Card: CM108 Audio Controller - USB Multimedia Audio Device
  Symptom_Type: No sound at all
  Title: [ICH4 - Intel ICH7, playback] No sound at all
  UpgradeStatus: Upgraded to oneiric on 2011-11-12 (8 days ago)
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0F8101
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0F8101:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/893210/+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 893210] Re: [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

[Neil]

changed analog-output-headphones.conf 
[Element Master Mono]
switch = on
volume = on
No effect

turned off headphone jack sense and line jack sense control
no effect, and were re-enabled by rebooting

Do not know how to implement the details in your post #43

just as an experiment I temporarily replaced the 
/usr/share/pulseaudio/alsa-mixer/paths/ directory with the one from 12.04
and that made no difference either!

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

Title:
  [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

Status in ALSA driver:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  fresh install of ubuntu studio and updates but internal speakers do
  not play. dell optiplex gx620 love ya

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: alsa-base 1.0.24+dfsg-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Card0.Amixer.info:
   Card hw:0 'ICH7'/'Intel ICH7 with AD1981B at irq 23'
 Mixer name : 'Analog Devices AD1981B'
 Components : 'AC97a:41445374'
 Controls  : 28
 Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'Device'/'C-Media Electronics Inc. USB Multimedia Audio Device at 
usb-:00:1d.7-4.1.4,'
 Mixer name : 'USB Mixer'
 Components : 'USB0d8c:0105'
 Controls  : 13
 Simple ctrls  : 6
  Date: Mon Nov 21 11:51:25 2011
  InstallationMedia: Ubuntu-Studio 11.10 "Oneiric Ocelot" - Release i386 
(20111011.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:ICH7 failed
  Symptom_Card: CM108 Audio Controller - USB Multimedia Audio Device
  Symptom_Type: No sound at all
  Title: [ICH4 - Intel ICH7, playback] No sound at all
  UpgradeStatus: Upgraded to oneiric on 2011-11-12 (8 days ago)
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0F8101
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0F8101:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/893210/+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 893210] Re: [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

[Neil]

I don't know Raymond. I just booted from ubuntu-12.04.5-desktop-
amd64.iso,  played a music file, opened alsamixer, and discovered that;
changing Master M volume independently changed the internal speaker
volume. In 14.04 Master M is muted by default, unmuting and raising the
volume has no effect.

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

Title:
  [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

Status in ALSA driver:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  fresh install of ubuntu studio and updates but internal speakers do
  not play. dell optiplex gx620 love ya

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: alsa-base 1.0.24+dfsg-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Card0.Amixer.info:
   Card hw:0 'ICH7'/'Intel ICH7 with AD1981B at irq 23'
 Mixer name : 'Analog Devices AD1981B'
 Components : 'AC97a:41445374'
 Controls  : 28
 Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'Device'/'C-Media Electronics Inc. USB Multimedia Audio Device at 
usb-:00:1d.7-4.1.4,'
 Mixer name : 'USB Mixer'
 Components : 'USB0d8c:0105'
 Controls  : 13
 Simple ctrls  : 6
  Date: Mon Nov 21 11:51:25 2011
  InstallationMedia: Ubuntu-Studio 11.10 "Oneiric Ocelot" - Release i386 
(20111011.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:ICH7 failed
  Symptom_Card: CM108 Audio Controller - USB Multimedia Audio Device
  Symptom_Type: No sound at all
  Title: [ICH4 - Intel ICH7, playback] No sound at all
  UpgradeStatus: Upgraded to oneiric on 2011-11-12 (8 days ago)
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0F8101
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0F8101:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/893210/+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 893210] Re: [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

[Neil]

so how can I get pactl list sinks to include:

analog-output-lfe-on-mono;output-amplifier-on: LFE on Separate Mono Output / 
Amplifier (priority: 4010)
analog-output-lfe-on-mono;output-amplifier-off: LFE on Separate Mono Output / 
No Amplifier (priority: 4000)

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

Title:
  [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

Status in ALSA driver:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  fresh install of ubuntu studio and updates but internal speakers do
  not play. dell optiplex gx620 love ya

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: alsa-base 1.0.24+dfsg-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Card0.Amixer.info:
   Card hw:0 'ICH7'/'Intel ICH7 with AD1981B at irq 23'
 Mixer name : 'Analog Devices AD1981B'
 Components : 'AC97a:41445374'
 Controls  : 28
 Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'Device'/'C-Media Electronics Inc. USB Multimedia Audio Device at 
usb-:00:1d.7-4.1.4,'
 Mixer name : 'USB Mixer'
 Components : 'USB0d8c:0105'
 Controls  : 13
 Simple ctrls  : 6
  Date: Mon Nov 21 11:51:25 2011
  InstallationMedia: Ubuntu-Studio 11.10 "Oneiric Ocelot" - Release i386 
(20111011.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:ICH7 failed
  Symptom_Card: CM108 Audio Controller - USB Multimedia Audio Device
  Symptom_Type: No sound at all
  Title: [ICH4 - Intel ICH7, playback] No sound at all
  UpgradeStatus: Upgraded to oneiric on 2011-11-12 (8 days ago)
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0F8101
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0F8101:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/893210/+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 893210] Re: [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

[Neil]

post #35 relates to 14.04.3

This post relates to 12.04.05

--- /media/kingfisher/FLASH DRIVE/alsa-info1
+++ /media/kingfisher/FLASH DRIVE/alsa-info2
@@ -3,7 +3,7 @@
 !!ALSA Information Script v 0.4.64
 !!
 
-!!Script ran on: Sat Sep 12 20:38:39 UTC 2015
+!!Script ran on: Sat Sep 12 20:40:18 UTC 2015
 
 
 !!Linux Distribution
@@ -211,7 +211,7 @@
 0:6c = 
 0:6e = 
 0:70 = 
-0:72 = 0004
+0:72 = 000c
 0:74 = 1001
 0:76 = 2010
 0:78 = 

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

Title:
  [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

Status in ALSA driver:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  fresh install of ubuntu studio and updates but internal speakers do
  not play. dell optiplex gx620 love ya

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: alsa-base 1.0.24+dfsg-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Card0.Amixer.info:
   Card hw:0 'ICH7'/'Intel ICH7 with AD1981B at irq 23'
 Mixer name : 'Analog Devices AD1981B'
 Components : 'AC97a:41445374'
 Controls  : 28
 Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'Device'/'C-Media Electronics Inc. USB Multimedia Audio Device at 
usb-:00:1d.7-4.1.4,'
 Mixer name : 'USB Mixer'
 Components : 'USB0d8c:0105'
 Controls  : 13
 Simple ctrls  : 6
  Date: Mon Nov 21 11:51:25 2011
  InstallationMedia: Ubuntu-Studio 11.10 "Oneiric Ocelot" - Release i386 
(20111011.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:ICH7 failed
  Symptom_Card: CM108 Audio Controller - USB Multimedia Audio Device
  Symptom_Type: No sound at all
  Title: [ICH4 - Intel ICH7, playback] No sound at all
  UpgradeStatus: Upgraded to oneiric on 2011-11-12 (8 days ago)
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0F8101
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0F8101:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/893210/+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 893210] Re: [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

[Neil]

--- /home/kingfisher/alsa-info.txt.yCKDtvMxUL
+++ /home/kingfisher/alsa-info.txt.3NDI7H9Nbu
@@ -3,7 +3,7 @@
 !!ALSA Information Script v 0.4.64
 !!
 
-!!Script ran on: Sat Sep 12 20:05:02 UTC 2015
+!!Script ran on: Sat Sep 12 20:08:12 UTC 2015
 
 
 !!Linux Distribution
@@ -215,7 +215,7 @@
 0:6c = 
 0:6e = 
 0:70 = 
-0:72 = 1804
+0:72 = 180c
 0:74 = 1001
 0:76 = 2010
 0:78 = 

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

Title:
  [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

Status in ALSA driver:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  fresh install of ubuntu studio and updates but internal speakers do
  not play. dell optiplex gx620 love ya

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: alsa-base 1.0.24+dfsg-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Card0.Amixer.info:
   Card hw:0 'ICH7'/'Intel ICH7 with AD1981B at irq 23'
 Mixer name : 'Analog Devices AD1981B'
 Components : 'AC97a:41445374'
 Controls  : 28
 Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'Device'/'C-Media Electronics Inc. USB Multimedia Audio Device at 
usb-:00:1d.7-4.1.4,'
 Mixer name : 'USB Mixer'
 Components : 'USB0d8c:0105'
 Controls  : 13
 Simple ctrls  : 6
  Date: Mon Nov 21 11:51:25 2011
  InstallationMedia: Ubuntu-Studio 11.10 "Oneiric Ocelot" - Release i386 
(20111011.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:ICH7 failed
  Symptom_Card: CM108 Audio Controller - USB Multimedia Audio Device
  Symptom_Type: No sound at all
  Title: [ICH4 - Intel ICH7, playback] No sound at all
  UpgradeStatus: Upgraded to oneiric on 2011-11-12 (8 days ago)
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0F8101
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0F8101:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/893210/+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 893210] Re: [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

[Neil]

booted from ubuntu-12.04.5-desktop-amd64.iso

12.04.5 alsa-info.txt
http://pastebin.com/uUkhy9H5

12.04.5 pactl list sinks
http://pastebin.com/zatgyeE7

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

Title:
  [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

Status in ALSA driver:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  fresh install of ubuntu studio and updates but internal speakers do
  not play. dell optiplex gx620 love ya

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: alsa-base 1.0.24+dfsg-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Card0.Amixer.info:
   Card hw:0 'ICH7'/'Intel ICH7 with AD1981B at irq 23'
 Mixer name : 'Analog Devices AD1981B'
 Components : 'AC97a:41445374'
 Controls  : 28
 Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'Device'/'C-Media Electronics Inc. USB Multimedia Audio Device at 
usb-:00:1d.7-4.1.4,'
 Mixer name : 'USB Mixer'
 Components : 'USB0d8c:0105'
 Controls  : 13
 Simple ctrls  : 6
  Date: Mon Nov 21 11:51:25 2011
  InstallationMedia: Ubuntu-Studio 11.10 "Oneiric Ocelot" - Release i386 
(20111011.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:ICH7 failed
  Symptom_Card: CM108 Audio Controller - USB Multimedia Audio Device
  Symptom_Type: No sound at all
  Title: [ICH4 - Intel ICH7, playback] No sound at all
  UpgradeStatus: Upgraded to oneiric on 2011-11-12 (8 days ago)
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0F8101
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0F8101:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/893210/+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 893210] Re: [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

[Neil]

3rd time lucky
12.04
https://www.dropbox.com/s/0k376713gb0ptod/Screenshot%20from%202014-12-02%2013%3A34%3A05.png?dl=0

14.04
https://www.dropbox.com/s/h38d1w4n16etdyh/Screenshot%20from%202014-12-02%2013%3A40%3A50.png?dl=0

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

Title:
  [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

Status in ALSA driver:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  fresh install of ubuntu studio and updates but internal speakers do
  not play. dell optiplex gx620 love ya

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: alsa-base 1.0.24+dfsg-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Card0.Amixer.info:
   Card hw:0 'ICH7'/'Intel ICH7 with AD1981B at irq 23'
 Mixer name : 'Analog Devices AD1981B'
 Components : 'AC97a:41445374'
 Controls  : 28
 Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'Device'/'C-Media Electronics Inc. USB Multimedia Audio Device at 
usb-:00:1d.7-4.1.4,'
 Mixer name : 'USB Mixer'
 Components : 'USB0d8c:0105'
 Controls  : 13
 Simple ctrls  : 6
  Date: Mon Nov 21 11:51:25 2011
  InstallationMedia: Ubuntu-Studio 11.10 "Oneiric Ocelot" - Release i386 
(20111011.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:ICH7 failed
  Symptom_Card: CM108 Audio Controller - USB Multimedia Audio Device
  Symptom_Type: No sound at all
  Title: [ICH4 - Intel ICH7, playback] No sound at all
  UpgradeStatus: Upgraded to oneiric on 2011-11-12 (8 days ago)
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0F8101
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0F8101:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/893210/+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 893210] Re: [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

[Neil]

apologies:
12.04
https://www.dropbox.com/s/0k376713gb0ptod/Screenshot%20from%202014-12-02%2013%3A34%3A05.png?dl=0

14.04
https://www.dropbox.com/s/0k376713gb0ptod/Screenshot%20from%202014-12-02%2013%3A34%3A05.png?dl=0

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

Title:
  [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

Status in ALSA driver:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  fresh install of ubuntu studio and updates but internal speakers do
  not play. dell optiplex gx620 love ya

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: alsa-base 1.0.24+dfsg-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Card0.Amixer.info:
   Card hw:0 'ICH7'/'Intel ICH7 with AD1981B at irq 23'
 Mixer name : 'Analog Devices AD1981B'
 Components : 'AC97a:41445374'
 Controls  : 28
 Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'Device'/'C-Media Electronics Inc. USB Multimedia Audio Device at 
usb-:00:1d.7-4.1.4,'
 Mixer name : 'USB Mixer'
 Components : 'USB0d8c:0105'
 Controls  : 13
 Simple ctrls  : 6
  Date: Mon Nov 21 11:51:25 2011
  InstallationMedia: Ubuntu-Studio 11.10 "Oneiric Ocelot" - Release i386 
(20111011.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:ICH7 failed
  Symptom_Card: CM108 Audio Controller - USB Multimedia Audio Device
  Symptom_Type: No sound at all
  Title: [ICH4 - Intel ICH7, playback] No sound at all
  UpgradeStatus: Upgraded to oneiric on 2011-11-12 (8 days ago)
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0F8101
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0F8101:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/893210/+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 893210] Re: [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

[Neil]

Thank you for your reply Raymond, i am uncertain what you are asking me
do.

14.04, 14.10 and 15.04 sound settings output look like this:
https://www.dropbox.com/s/h38d1w4n16...%3A50.png?dl=0
and the associated alsa mixer controls e.g. speaker are missing

this is what 12.04 looked like and worked:
https://www.dropbox.com/s/0k376713gb...%3A05.png?dl=0

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

Title:
  [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

Status in ALSA driver:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  fresh install of ubuntu studio and updates but internal speakers do
  not play. dell optiplex gx620 love ya

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: alsa-base 1.0.24+dfsg-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Card0.Amixer.info:
   Card hw:0 'ICH7'/'Intel ICH7 with AD1981B at irq 23'
 Mixer name : 'Analog Devices AD1981B'
 Components : 'AC97a:41445374'
 Controls  : 28
 Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'Device'/'C-Media Electronics Inc. USB Multimedia Audio Device at 
usb-:00:1d.7-4.1.4,'
 Mixer name : 'USB Mixer'
 Components : 'USB0d8c:0105'
 Controls  : 13
 Simple ctrls  : 6
  Date: Mon Nov 21 11:51:25 2011
  InstallationMedia: Ubuntu-Studio 11.10 "Oneiric Ocelot" - Release i386 
(20111011.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:ICH7 failed
  Symptom_Card: CM108 Audio Controller - USB Multimedia Audio Device
  Symptom_Type: No sound at all
  Title: [ICH4 - Intel ICH7, playback] No sound at all
  UpgradeStatus: Upgraded to oneiric on 2011-11-12 (8 days ago)
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0F8101
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0F8101:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/893210/+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 893210] Re: [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

[Neil]

alsa-info.txt
http://pastebin.com/pefj0dfq

differences with and without headphone socket occupied
alsa-info.patch.txt
http://pastebin.com/jzJBNd8e

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

Title:
  [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

Status in ALSA driver:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  fresh install of ubuntu studio and updates but internal speakers do
  not play. dell optiplex gx620 love ya

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: alsa-base 1.0.24+dfsg-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Card0.Amixer.info:
   Card hw:0 'ICH7'/'Intel ICH7 with AD1981B at irq 23'
 Mixer name : 'Analog Devices AD1981B'
 Components : 'AC97a:41445374'
 Controls  : 28
 Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'Device'/'C-Media Electronics Inc. USB Multimedia Audio Device at 
usb-:00:1d.7-4.1.4,'
 Mixer name : 'USB Mixer'
 Components : 'USB0d8c:0105'
 Controls  : 13
 Simple ctrls  : 6
  Date: Mon Nov 21 11:51:25 2011
  InstallationMedia: Ubuntu-Studio 11.10 "Oneiric Ocelot" - Release i386 
(20111011.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:ICH7 failed
  Symptom_Card: CM108 Audio Controller - USB Multimedia Audio Device
  Symptom_Type: No sound at all
  Title: [ICH4 - Intel ICH7, playback] No sound at all
  UpgradeStatus: Upgraded to oneiric on 2011-11-12 (8 days ago)
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0F8101
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0F8101:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/893210/+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 893210] Re: [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

[Neil]

Thank you Raymond, please see the following:

pactl list sinks
http://pastebin.com/8ypDq0vr

pulseverbose.log
http://pastebin.com/ThJQ7372

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

Title:
  [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

Status in ALSA driver:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  fresh install of ubuntu studio and updates but internal speakers do
  not play. dell optiplex gx620 love ya

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: alsa-base 1.0.24+dfsg-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Card0.Amixer.info:
   Card hw:0 'ICH7'/'Intel ICH7 with AD1981B at irq 23'
 Mixer name : 'Analog Devices AD1981B'
 Components : 'AC97a:41445374'
 Controls  : 28
 Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'Device'/'C-Media Electronics Inc. USB Multimedia Audio Device at 
usb-:00:1d.7-4.1.4,'
 Mixer name : 'USB Mixer'
 Components : 'USB0d8c:0105'
 Controls  : 13
 Simple ctrls  : 6
  Date: Mon Nov 21 11:51:25 2011
  InstallationMedia: Ubuntu-Studio 11.10 "Oneiric Ocelot" - Release i386 
(20111011.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:ICH7 failed
  Symptom_Card: CM108 Audio Controller - USB Multimedia Audio Device
  Symptom_Type: No sound at all
  Title: [ICH4 - Intel ICH7, playback] No sound at all
  UpgradeStatus: Upgraded to oneiric on 2011-11-12 (8 days ago)
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0F8101
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0F8101:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/893210/+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 893210] Re: [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

[Neil]

Its the same with 14.04, 14.10 and 15.04, is support discontinued for
Dell GX600, It would be nice if someone with expert knowledge would
explain how the internal speaker can be correctly detected, after all it
all worked perfectly in 12.04

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

Title:
  [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

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

Bug description:
  fresh install of ubuntu studio and updates but internal speakers do
  not play. dell optiplex gx620 love ya

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: alsa-base 1.0.24+dfsg-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Card0.Amixer.info:
   Card hw:0 'ICH7'/'Intel ICH7 with AD1981B at irq 23'
 Mixer name : 'Analog Devices AD1981B'
 Components : 'AC97a:41445374'
 Controls  : 28
 Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'Device'/'C-Media Electronics Inc. USB Multimedia Audio Device at 
usb-:00:1d.7-4.1.4,'
 Mixer name : 'USB Mixer'
 Components : 'USB0d8c:0105'
 Controls  : 13
 Simple ctrls  : 6
  Date: Mon Nov 21 11:51:25 2011
  InstallationMedia: Ubuntu-Studio 11.10 "Oneiric Ocelot" - Release i386 
(20111011.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:ICH7 failed
  Symptom_Card: CM108 Audio Controller - USB Multimedia Audio Device
  Symptom_Type: No sound at all
  Title: [ICH4 - Intel ICH7, playback] No sound at all
  UpgradeStatus: Upgraded to oneiric on 2011-11-12 (8 days ago)
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0F8101
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0F8101:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/893210/+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 1484124] [NEW] Errors in Ubuntu Content API documentation

[Neil McPhail]

Public bug reported:

From
https://developer.ubuntu.com/api/apps/qml/sdk-15.04/Ubuntu.Content.index/
as accessed on 2015-08-12:

Under "Definitions", the definition of "Content types" is confusingly
recursive ("Content types: A set of well-known content types").

Under "Reporting Bugs", there is a typo in the text ("If you find any
problems with the [MISSING_WORD_OR_PHRASE] or this documentation, please
file a bug in Ubuntu Content API"), and the bug reporting link points to
the upstream content-hub package, which doesn't accept bug reports.

** Affects: content-hub (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Errors in Ubuntu Content API documentation

Status in content-hub package in Ubuntu:
  New

Bug description:
  From
  https://developer.ubuntu.com/api/apps/qml/sdk-15.04/Ubuntu.Content.index/
  as accessed on 2015-08-12:

  Under "Definitions", the definition of "Content types" is confusingly
  recursive ("Content types: A set of well-known content types").

  Under "Reporting Bugs", there is a typo in the text ("If you find any
  problems with the [MISSING_WORD_OR_PHRASE] or this documentation,
  please file a bug in Ubuntu Content API"), and the bug reporting link
  points to the upstream content-hub package, which doesn't accept bug
  reports.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1484124/+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 1482613] Re: Apps with forced landscape orientation display the "wrong" way on the phone

[Neil McPhail]

A quick drawing to illustrate...

** Attachment added: "rotate.png"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1482613/+attachment/4441037/+files/rotate.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/1482613

Title:
  Apps with forced landscape orientation display the "wrong" way on the
  phone

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  See also https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1478637
  which is probably the same issue, but for natively landscape
  orientated devices.

  When an app sets a forced-landscape mode, the phone must be rotated
  clockwise from portrait mode to display it properly. This is a more
  difficult movement than rotating anti-clockwise for people holding the
  phone in their left hand (e.g. most right-handed people).

  When an app forces landscape mode, the "top" of the landscape screen
  should be the right of the portait-orientated screen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1482613/+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 1482613] [NEW] Apps with forced landscape orientation display the "wrong" way on the phone

[Neil McPhail]

Public bug reported:

See also https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1478637
which is probably the same issue, but for natively landscape orientated
devices.

When an app sets a forced-landscape mode, the phone must be rotated
clockwise from portrait mode to display it properly. This is a more
difficult movement than rotating anti-clockwise for people holding the
phone in their left hand (e.g. most right-handed people).

When an app forces landscape mode, the "top" of the landscape screen
should be the right of the portait-orientated screen.

** 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/1482613

Title:
  Apps with forced landscape orientation display the "wrong" way on the
  phone

Status in unity8 package in Ubuntu:
  New

Bug description:
  See also https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1478637
  which is probably the same issue, but for natively landscape
  orientated devices.

  When an app sets a forced-landscape mode, the phone must be rotated
  clockwise from portrait mode to display it properly. This is a more
  difficult movement than rotating anti-clockwise for people holding the
  phone in their left hand (e.g. most right-handed people).

  When an app forces landscape mode, the "top" of the landscape screen
  should be the right of the portait-orientated screen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1482613/+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 1466656] Re: Rotated ubuntu shapes have poor anti-aliasing

[Neil McPhail]

I have found a similar rendering bug which may be the same problem,
running OTA5 on krillin:

- Open browser in portrait mode
- rotate to landscape then back to portrait
- The "location" text field outline will become corrupted as per the attached 
screenshot.

** Attachment added: "screenshot20150720_195754928.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1466656/+attachment/4431687/+files/screenshot20150720_195754928.png

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

Title:
  Rotated ubuntu shapes have poor anti-aliasing

Status in Canonical System Image:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  $ adb shell system-image-cli --info
  current build number: 23
  device name: krillin
  channel: ubuntu-touch/stable/bq-aquaris.en
  last update: 2015-06-15 19:22:22
  version version: 23
  version ubuntu: 20150611.3
  version device: 20150529-8e13c5f
  version custom: 20150528-722-29-15-vivid

  Steps to reproduce:-

  1. Swipe down indicators
  2. Rotation
  3. Switch rotation lock _off_, that is "X"
  4. Hold phone in portrait and navigate to the top of the apps scope

  Observe normal icons

  5. Rotate phone 90 degrees to landscape, pull the scope "down" (to the
  side) slightly to force a re-draw

  Observe poor anti-aliasing around the ubuntu shapes.

  Two screenshots attached.
  device-2015-06-18-220419.png - portait
  device-2015-06-18-220428.png - landscape

  The effect is most noticable if you open both of the attachments full-
  size and switch between them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1466656/+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 1460149] Re: Visible corruption in SDL apps (Neverball, Neverputt) on Nexus 4 / Nexus 7.

[Neil McPhail]

Begin a right->left swipe and the picture clears

** Attachment added: "screenshot20151325_201339233.png"
   
https://bugs.launchpad.net/mir/+bug/1460149/+attachment/4420170/+files/screenshot20151325_201339233.png

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

Title:
  Visible corruption in SDL apps (Neverball, Neverputt) on Nexus 4 /
  Nexus 7.

Status in Mir:
  New
Status in libsdl2 package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  https://github.com/pseuudonym404/neverball-touch/issues/2

  Install neverball or neverputt from the click store:-

  https://uappexplorer.com/app/neverputt.lb
  https://uappexplorer.com/app/neverball.lb

  Note they work fine on krillin and arale, however there's corruption
  making the games unusable on Nexus 4 and Nexus 7.

  Simpler test cases are provided at the above linked github issue.
  Attaching them to this bug for persistence.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1460149/+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 1460149] Re: Visible corruption in SDL apps (Neverball, Neverputt) on Nexus 4 / Nexus 7.

[Neil McPhail]

I get similar corruption running Baldur's Gate (via GemRB and SDL2) on
krillin. The intro videos play well, but when the main menu appears the
shell bleeds into it. The picture clears when you begin to swipe. I'll
attach some pics as it is hard to explain.

** Attachment added: "Corruption of menu"
   
https://bugs.launchpad.net/mir/+bug/1460149/+attachment/4420169/+files/screenshot20151325_201317031.png

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

Title:
  Visible corruption in SDL apps (Neverball, Neverputt) on Nexus 4 /
  Nexus 7.

Status in Mir:
  New
Status in libsdl2 package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  https://github.com/pseuudonym404/neverball-touch/issues/2

  Install neverball or neverputt from the click store:-

  https://uappexplorer.com/app/neverputt.lb
  https://uappexplorer.com/app/neverball.lb

  Note they work fine on krillin and arale, however there's corruption
  making the games unusable on Nexus 4 and Nexus 7.

  Simpler test cases are provided at the above linked github issue.
  Attaching them to this bug for persistence.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1460149/+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 1466741] Re: system slow to wake up/unlock screen sluggish since the update to vivid

[Neil McPhail]

I'm getting this behaviour. Running "top" shown dbus-daemon consuming
33% of CPU time. Is that normal?

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

Title:
  system slow to wake up/unlock screen sluggish since the update to
  vivid

Status in the base for Ubuntu mobile products:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  That's not happening all the time but has been reported by several
  users on the list and I also hit the issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1466741/+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 1459259] Re: Apps using OpenAL on the Ubuntu Phone appear to have direct hardware access despite apparmor constraints

[Neil McPhail]

Thanks for the log - if pulse is being used, there must be some reason
the volume control doesn't work.

I have realised the reason the sound continues playing in the background
is due to an unrelated bug: apps continue running in background (or
screen-off) when they do not spawn a gui. Thus, this bug is probably
assigned to the wrong package. Can anyone suggest or reassign to a more
appropriate package?

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

Title:
  Apps using OpenAL on the Ubuntu Phone appear to have direct hardware
  access despite apparmor constraints

Status in apparmor package in Ubuntu:
  Incomplete

Bug description:
  I have been building some apps for the phone which use OpenAL. They
  will play audio if running under the "audio" policy group. However,
  the volume of audio is not controlled by the volume slider or "Silent
  mode" switch and audio can continue to play if the app is backgrounded
  or phone screen is switched off. After discussion on #ubuntu-touch it
  was suggested this may imply the apps have direct hardware access,
  despite apparmor constraints.

  I do not know if this is a security vulnerability, so I will report it
  as such to be safe.

  Attached is a .click package build for Ubuntu phones (armhf). It
  contains a small OpenAL example app borrowed from a blog site (source
  code included in click) and bundles the current OpenAL lib from the
  14.10 distribution. It runs under apparmor constraints, and is only
  granted access to the "audio" group. The app would be automatically
  accepted to the Ubuntu Store.

  The audio will continue to play until the app is killed by the user.
  It will play in silent mode, when in the background or when the screen
  is off. The app has been tested on BQ and meizu devices running RTM
  and vivid.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1459259/+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 1459259] Re: Apps using OpenAL on the Ubuntu Phone appear to have direct hardware access despite apparmor constraints

[Neil McPhail]

As far as I know, it _can_ use pulseaudio but don't know if that is what
is happening here. I had been told on the IRC channel that the reason it
was not responding to the volume control was because it was not using
pulse, and suggested it was directly accessing the hardware. I have no
idea how to confirm that but am happy to do any suggested debugging.

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

Title:
  Apps using OpenAL on the Ubuntu Phone appear to have direct hardware
  access despite apparmor constraints

Status in apparmor package in Ubuntu:
  Incomplete

Bug description:
  I have been building some apps for the phone which use OpenAL. They
  will play audio if running under the "audio" policy group. However,
  the volume of audio is not controlled by the volume slider or "Silent
  mode" switch and audio can continue to play if the app is backgrounded
  or phone screen is switched off. After discussion on #ubuntu-touch it
  was suggested this may imply the apps have direct hardware access,
  despite apparmor constraints.

  I do not know if this is a security vulnerability, so I will report it
  as such to be safe.

  Attached is a .click package build for Ubuntu phones (armhf). It
  contains a small OpenAL example app borrowed from a blog site (source
  code included in click) and bundles the current OpenAL lib from the
  14.10 distribution. It runs under apparmor constraints, and is only
  granted access to the "audio" group. The app would be automatically
  accepted to the Ubuntu Store.

  The audio will continue to play until the app is killed by the user.
  It will play in silent mode, when in the background or when the screen
  is off. The app has been tested on BQ and meizu devices running RTM
  and vivid.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1459259/+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 1459259] [NEW] Apps using OpenAL on the Ubuntu Phone appear to have direct hardware access despite apparmor constraints

[Neil McPhail]

Public bug reported:

I have been building some apps for the phone which use OpenAL. They will
play audio if running under the "audio" policy group. However, the
volume of audio is not controlled by the volume slider or "Silent mode"
switch and audio can continue to play if the app is backgrounded or
phone screen is switched off. After discussion on #ubuntu-touch it was
suggested this may imply the apps have direct hardware access, despite
apparmor constraints.

I do not know if this is a security vulnerability, so I will report it
as such to be safe.

Attached is a .click package build for Ubuntu phones (armhf). It
contains a small OpenAL example app borrowed from a blog site (source
code included in click) and bundles the current OpenAL lib from the
14.10 distribution. It runs under apparmor constraints, and is only
granted access to the "audio" group. The app would be automatically
accepted to the Ubuntu Store.

The audio will continue to play until the app is killed by the user. It
will play in silent mode, when in the background or when the screen is
off. The app has been tested on BQ and meizu devices running RTM and
vivid.

** Affects: apparmor (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Attachment added: "Sample application to demonstrate problem"
   
https://bugs.launchpad.net/bugs/1459259/+attachment/4405479/+files/altest.njmcphail_0.1_armhf.click

** Information type changed from Private Security to Public

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

Title:
  Apps using OpenAL on the Ubuntu Phone appear to have direct hardware
  access despite apparmor constraints

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  I have been building some apps for the phone which use OpenAL. They
  will play audio if running under the "audio" policy group. However,
  the volume of audio is not controlled by the volume slider or "Silent
  mode" switch and audio can continue to play if the app is backgrounded
  or phone screen is switched off. After discussion on #ubuntu-touch it
  was suggested this may imply the apps have direct hardware access,
  despite apparmor constraints.

  I do not know if this is a security vulnerability, so I will report it
  as such to be safe.

  Attached is a .click package build for Ubuntu phones (armhf). It
  contains a small OpenAL example app borrowed from a blog site (source
  code included in click) and bundles the current OpenAL lib from the
  14.10 distribution. It runs under apparmor constraints, and is only
  granted access to the "audio" group. The app would be automatically
  accepted to the Ubuntu Store.

  The audio will continue to play until the app is killed by the user.
  It will play in silent mode, when in the background or when the screen
  is off. The app has been tested on BQ and meizu devices running RTM
  and vivid.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1459259/+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 1452219] [NEW] Wishlist: ring-ring ringtone

[Neil McPhail]

Public bug reported:

The supplied ringtones are pretty, but not suitable for use in a
professional environment. It is not possible to add ringtones without
remounting rw, so a "ring-ring" type ringtone should be supplied by
default. I have supplied a bland/loud office-style ringtone which may
serve the purpose. This is an original work created by the tone
generators and filters in Audacity and has not been copied or derived
from another source. If you wish to use it, I am happy to change the
licence from the Creative Commons Attribution-ShareAlike 4.0
International License, if required.

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

** Attachment added: "Office ringtone. This work is licensed under the Creative 
Commons Attribution-ShareAlike 4.0 International License but I would be happy 
to change this if required."
   https://bugs.launchpad.net/bugs/1452219/+attachment/4392100/+files/office.ogg

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

Title:
  Wishlist: ring-ring ringtone

Status in ubuntu-touch-sounds package in Ubuntu:
  New

Bug description:
  The supplied ringtones are pretty, but not suitable for use in a
  professional environment. It is not possible to add ringtones without
  remounting rw, so a "ring-ring" type ringtone should be supplied by
  default. I have supplied a bland/loud office-style ringtone which may
  serve the purpose. This is an original work created by the tone
  generators and filters in Audacity and has not been copied or derived
  from another source. If you wish to use it, I am happy to change the
  licence from the Creative Commons Attribution-ShareAlike 4.0
  International License, if required.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-sounds/+bug/1452219/+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 1364872] Re: The gdbserver is not available on the device image

[Neil McPhail]

I'm not sure I agree this should only be in developer versions. I need a
phone which works (hence stable channel), but also like to develop and
debug apps. The 2 use cases are not mutually exclusive.

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

Title:
  The gdbserver is not available on the device image

Status in the base for Ubuntu mobile products:
  New
Status in ubuntu-touch-meta package in Ubuntu:
  Confirmed

Bug description:
  To enable debugging of applications with C++ code the target device
  must have gdbserver package installed.

  Right now for that the app developers need to turn the device writable
  and manually install the gdbserver package.

  It would be much more convinient and secure to keep the device
  readonly and have the gdbserver pre-installed on the device.

  The disk space should not be a concern  as all installed files from
  the package use up 215KB (binary - 190KB + doc - 20KB   + manpage -
  5KB)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1364872/+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 1397918] Re: krillin #169 + cgroups fix, scopes hang / crash / unusable

[Neil McPhail]

I'm adding a comment to keep this alive. I have had this bug on occasion
on krillin rtm v20. I haven't had an episode since upgrading to v21 a
couple of days ago but can't see anything in the changelogs which
suggest it has been fixed. If it has been fixed in the meantime, sorry
for the spam but this bug should then be closed.

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

Title:
  krillin #169 + cgroups fix, scopes hang / crash / unusable

Status in unity-scopes-api package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  On a couple of occasions over the weekend my phone has become
  unusable. I can unlock it, swipe the launcher out, pull down
  indicators, launch applications (from the launcher) and switch
  applications from the side. I cannot use any scops. They don't respond
  to touch at all. I'm stuck on the "Today" scope.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: libunity-scopes3 0.6.7+15.04.20141107.1~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Mon Dec  1 09:55:21 2014
  InstallationDate: Installed on 2014-11-24 (6 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141124-203231)
  SourcePackage: unity-scopes-api
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1397918/+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 1439680] [NEW] DatePicker scrolls too quickly, making precision difficult

[Neil McPhail]

Public bug reported:

Using the DatePicker is more difficult than it needs to be.

OS: 14.09-RTM Ubuntu-Touch on bq aquaris

Example: When adding a new event in the Calendar app, I am presented
with 2 DatePicker widgets (one for date and one for time).

Expected behaviour: I expect to be able to scroll to my desired date and
time quickly and efficiently. I expect it to be particularly easy to
select values at the 0,15,30,45 minute times.

Current behaviour: A small movement on the DatePicker dial causes the
dial to spin quickly. It is far too easy to overshoot the desired value
(often by a long way), Making a precise selection is fiddly and takes
longer than desirable. "Common" time increments such as 0,15,30 and 45
are no easier to select than 1,16,31 or 46, and the latter are often
picked accidently.

I don't know if this sensitivity to gesture is due to the high dpi
screen, or whether it is resolution independent.

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

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

Title:
  DatePicker scrolls too quickly, making precision difficult

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  Using the DatePicker is more difficult than it needs to be.

  OS: 14.09-RTM Ubuntu-Touch on bq aquaris

  Example: When adding a new event in the Calendar app, I am presented
  with 2 DatePicker widgets (one for date and one for time).

  Expected behaviour: I expect to be able to scroll to my desired date
  and time quickly and efficiently. I expect it to be particularly easy
  to select values at the 0,15,30,45 minute times.

  Current behaviour: A small movement on the DatePicker dial causes the
  dial to spin quickly. It is far too easy to overshoot the desired
  value (often by a long way), Making a precise selection is fiddly and
  takes longer than desirable. "Common" time increments such as 0,15,30
  and 45 are no easier to select than 1,16,31 or 46, and the latter are
  often picked accidently.

  I don't know if this sensitivity to gesture is due to the high dpi
  screen, or whether it is resolution independent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1439680/+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