[Touch-packages] [Bug 1701222] Re: [Hyper-V] LIS daemons fail to start after disable/re-enable VM integration services

2017-10-04 Thread Dimitri John Ledkov 
The unit entered a failed state, and thus would not automatically started until 
failed state clears.
Why does bouncing of the services result in the daemon exiting with an error 
condition? Should that particular exit code result in a graceful shutdown of 
the service, such that the unit can be restarted again?
What userspace events should be causing the start of this unit? a udev event / 
udev rule? a .path unit monitoring sysfs or some such?

Is it possible to reproduce this on e.g. azure for me to investigate?

I'm going to remove per-series tasks from systemd, until this issue is
trianged. per-series tasks on the src:systemd package are used to track
fixes/patches which have been developed and are ready for inclusion in
the distribution.

** No longer affects: systemd (Ubuntu Artful)

** No longer affects: systemd (Ubuntu Zesty)

** No longer affects: systemd (Ubuntu Xenial)

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

Title:
  [Hyper-V] LIS daemons fail to start after disable/re-enable VM
  integration services

Status in linux package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  New
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux source package in Artful:
  In Progress

Bug description:
  Issue description: Hyper-V daemons fail to start after disable/re-
  enable VM integration services.

  Platform: host independent
  Affected daemons - KVP, FCOPY and VSS.

  Distribution name and release: Ubuntu 16.04, Ubuntu 17.04
  Kernel version: 4.11.0-rc7-next-20170421 (for Ubuntu 16.04), 
4.10.0-19-generic (for Ubuntu 17.04)

  Repro rate: 100%

  Steps to reproduce:
  1.Start VM with Guest Services enabled (FCopy daemon starts automatically)
  2.Go to File > Settings > Integration Services, uncheck Guest Services 
and apply (FCopy daemon will stop at this point)
  3.Re-enable Guest Services from VM Settings (Fcopy daemon is not running).
  This is the issue. systemd monitors for the service and if we have the hook 
for the Guest Service, it tries to start the daemon again.
  systemd attempt to start any of the LIS daemons will fail, but manually 
executing the daemon binary, it will start the daemon.

  Additional Info:
  - the steps above can be repro'd with KVP / Data Exchange integration service 
as well.
  - Manually starting hv_fcopy_daemon works fine.
  - other distros (RHEL) does not have this behavior, the LIS daemons are 
started automatically by systemd once we re-enable the integration service.

  On the upstream kernel and the upstream hv daemons, these messages are 
recorded in syslog, once we re-enable the Guest service:
  HV_FCOPY: pread failed: Bad file descriptor
  systemd[1]: hv-fcopy-daemon.service: Main process exited, code=exited, 
status=1/FAILURE
  systemd[1]: hv-fcopy-daemon.service: Unit entered failed state.
  systemd[1]: hv-fcopy-daemon.service: Failed with result 'exit-code'.

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

-- 
Mailing list: https://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 1669564] Re: udevadm trigger subsystem-match=net doesn't always run rules because of reconfiguration rate-limiting

2017-10-04 Thread Dimitri John Ledkov 
@original reporter have you added `udevadm control --reload` in the
appropriate points in the test-harness and/or cloud-init? And does this
resolve the race you have previously observed?

Unassigning, Removing artful series target and marking incomplete, until
further information is provided.

** No longer affects: systemd (Ubuntu Artful)

** No longer affects: nplan (Ubuntu Artful)

** Changed in: systemd (Ubuntu)
 Assignee: Balint Reczey (rbalint) => (unassigned)

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

** Changed in: nplan (Ubuntu)
   Status: New => Incomplete

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

Title:
  udevadm trigger subsystem-match=net doesn't always run rules because
  of reconfiguration rate-limiting

Status in nplan package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  1. root@ubuntu:~# lsb_release -rd
  Description:Ubuntu Zesty Zapus (development branch)
  Release:17.04

  2. root@ubuntu:~# apt-cache policy udev
  udev:
    Installed: 232-18ubuntu1
    Candidate: 232-18ubuntu1
    Version table:
   *** 232-18ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

  3. udevadm trigger --verbose --subsystem-match=net --action=add will run and 
read .link files from /run/systemd/network/10-netplan-interface1.link
  and apply MTU settings

  4. during system boot running (3) does not set the MTU; running (3)
  after boot has completed MTU is set correctly.

  Here'a log during boot where cloud-init generates a netplan config,
  invokes `netplan generate` which writes the networkd config out 
  and then udevadm trigger (3).  Upon logging in interface1 has an MTU of 1500. 
 Re-running udevadm trigger now runs the rules/link files and updates the MTU.

  Note that, if you run udevadm test /sys/class/net/interface1; this also will
  apply the MTU (test probably shouldn't change the interface, I'll file a
  bug for that as well).

  # journalctl -o short-precise --no-pager -b | grep WARK
  Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['netplan', '--debug', 
'generate']:
  Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['stat', 
'/run/systemd/network/10-netplan-interface1.link']:
  Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['cat', 
'/run/systemd/network/10-netplan-interface1.link']:
  Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['systemctl', 'start', 
'--no-block', 'systemd-udev-trigger.service']:
  Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['udevadm', 'trigger', 
'--verbose', '--subsystem-match=net', '--action=add']:

  root@ubuntu:~# cat /run/systemd/network/10-netplan-interface1.link
  [Match]
  MACAddress=52:54:00:12:34:02

  [Link]
  Name=interface1
  WakeOnLan=off
  MTUBytes=1492

  root@ubuntu:~# ifconfig interface1
  interface1: flags=4163  mtu 1500
  inet 10.0.2.100  netmask 255.255.255.0  broadcast 10.0.2.255
  inet6 fe80::5054:ff:fe12:3402  prefixlen 64  scopeid 0x20
  inet6 fec0::5054:ff:fe12:3402  prefixlen 64  scopeid 0x40
  ether 52:54:00:12:34:02  txqueuelen 1000  (Ethernet)
  RX packets 16  bytes 5053 (5.0 KB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 35  bytes 3287 (3.2 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  root@ubuntu:~# udevadm trigger --verbose --subsystem-match=net --action=add
  /sys/devices/pci:00/:00:04.0/virtio1/net/interface1
  /sys/devices/pci:00/:00:05.0/virtio2/net/interface2
    ys/devices/pci:00/:00:06.0/virtio3/net/interface0
  /sys/devices/virtual/net/lo

  root@ubuntu:~# ifconfig interface1
  interface1: flags=4163  mtu 1492
  inet 10.0.2.100  netmask 255.255.255.0  broadcast 10.0.2.255
  inet6 fe80::5054:ff:fe12:3402  prefixlen 64  scopeid 0x20
  inet6 fec0::5054:ff:fe12:3402  prefixlen 64  scopeid 0x40
  ether 52:54:00:12:34:02  txqueuelen 1000  (Ethernet)
  RX packets 16  bytes 5053 (5.0 KB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 37  bytes 3504 (3.5 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: udev 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Thu Mar  2 19:22:14 2017
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine:

[Touch-packages] [Bug 1691096] Re: mysql in lxd fails to start with systemd 233, 234: failed at step KEYRING

2017-10-04 Thread Dimitri John Ledkov 
** Changed in: systemd (Ubuntu Artful)
   Status: Triaged => Fix Committed

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

Title:
  mysql in lxd fails to start with systemd 233, 234: failed at step
  KEYRING

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Artful:
  Fix Committed

Bug description:
  artful unprivileged container on a xenial host

  xnox hinted that
  
https://github.com/systemd/systemd/commit/b3415f5daef49642be3d5f417b8880c078420ff7
  might be related

  With systemd 233, mysql-server-5.7 in an artful lxd unprivileged
  container fails to start:

    Process: 6460 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre
  (code=exited, status=237/KEYRING)

  May 16 12:20:08 artful-mysql systemd[1]: mysql.service: Failed to set 
invocation ID on control group /system.slice/mysql.service, ignoring: Operation 
not permitted
  (...)
  May 16 12:20:08 artful-mysql systemd[6460]: mysql.service: Failed at step 
KEYRING spawning /usr/share/mysql/mysql-systemd-start: Permission denied

  Reproducing it on a fresh xenial kvm as host, fresh artful lxd image. We 
start with systemd-232 in the artful lxd:
  ubuntu@intense-sunbeam:~$ apt-cache policy systemd
  systemd:
    Installed: 232-21ubuntu3
    Candidate: 233-6ubuntu1
    Version table:
   233-6ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu artful/main amd64 Packages
   *** 232-21ubuntu3 100
  100 /var/lib/dpkg/status

  Then we install mysql-server-5.7:
  ubuntu@intense-sunbeam:~$ sudo apt install mysql-server-5.7
  ...
  Setting up mysql-server-5.7 (5.7.17-0ubuntu1) ...
  update-alternatives: using /etc/mysql/mysql.cnf to provide /etc/mysql/my.cnf 
(my.cnf) in auto mode
  Renaming removed key_buffer and myisam-recover options (if present)
  Created symlink /etc/systemd/system/multi-user.target.wants/mysql.service → 
/lib/systemd/system/mysql.service.
  Processing triggers for libc-bin (2.24-9ubuntu2) ...
  Processing triggers for systemd (232-21ubuntu3) ...

  Which starts just fine:
  ubuntu@intense-sunbeam:~$ mysql -uroot -psecret
  mysql: [Warning] Using a password on the command line interface can be 
insecure.
  Welcome to the MySQL monitor.  Commands end with ; or \g.
  ...

  We then upgrade systemd:
  ubuntu@intense-sunbeam:~$ sudo apt install systemd
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    libpam-systemd libsystemd0
  (...)
  Setting up libpam-systemd:amd64 (233-6ubuntu1) ...

  mysql is still running:
  ubuntu@intense-sunbeam:~$ mysql -uroot -psecret
  mysql: [Warning] Using a password on the command line interface can be 
insecure.
  Welcome to the MySQL monitor.  Commands end with ; or \g.
  (...)

  But restarting mysql fails:
  ubuntu@intense-sunbeam:~$ sudo service mysql restart
  Job for mysql.service failed because the control process exited with error 
code.
  See "systemctl  status mysql.service" and "journalctl  -xe" for details.
  ubuntu@intense-sunbeam:~$ mysql -uroot -psecret
  mysql: [Warning] Using a password on the command line interface can be 
insecure.
  ERROR 2002 (HY000): Can't connect to local MySQL server through socket 
'/var/run/mysqld/mysqld.sock' (2)

  More logs attached.

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

-- 
Mailing list: https://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 1721203] [NEW] systemd armhf autopkgtest test-copy fails in artful

2017-10-04 Thread Dimitri John Ledkov 
Public bug reported:

systemd armhf autopkgtest test-copy fails in artful

test-copy uses itself as the source to test copies. The test suite tries
to test cases where maximum requested copy is below and above the
internal buffer size. However, that fails when the maximum requested
copy bytes is more than the source binary... as started to be the case
with uber optimised artful toolchain on armhf, and after debug symbols
stripped. Specifically test-copy started to be less than 32000 bytes.

Awaiting improvement to the test suite upstream, simply keep test-copy
unstripped such that systemd-tests can be used in adt tests without
failures.

** Affects: systemd
 Importance: Unknown
 Status: Unknown

** Affects: systemd (Ubuntu)
 Importance: High
 Assignee: Dimitri John Ledkov (xnox)
 Status: Fix Committed

** Affects: systemd (Ubuntu Artful)
 Importance: High
 Assignee: Dimitri John Ledkov (xnox)
 Status: Fix Committed


** Tags: adt-fail armhf

** Also affects: systemd (Ubuntu Artful)
   Importance: Undecided
 Assignee: Dimitri John Ledkov (xnox)
   Status: New

** Bug watch added: github.com/systemd/systemd/issues #6981
   https://github.com/systemd/systemd/issues/6981

** Also affects: systemd via
   https://github.com/systemd/systemd/issues/6981
   Importance: Unknown
   Status: Unknown

** Changed in: systemd (Ubuntu Artful)
   Status: New => Fix Committed

** Changed in: systemd (Ubuntu Artful)
   Importance: Undecided => High

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

Title:
  systemd armhf autopkgtest test-copy fails in artful

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Artful:
  Fix Committed

Bug description:
  systemd armhf autopkgtest test-copy fails in artful

  test-copy uses itself as the source to test copies. The test suite
  tries to test cases where maximum requested copy is below and above
  the internal buffer size. However, that fails when the maximum
  requested copy bytes is more than the source binary... as started to
  be the case with uber optimised artful toolchain on armhf, and after
  debug symbols stripped. Specifically test-copy started to be less than
  32000 bytes.

  Awaiting improvement to the test suite upstream, simply keep test-copy
  unstripped such that systemd-tests can be used in adt tests without
  failures.

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

-- 
Mailing list: https://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 1721204] [NEW] timesyncd has redundant condition conflict with ntp and others

2017-10-04 Thread Dimitri John Ledkov 
Public bug reported:

Cherrypick

Drop systemd-timesyncd.service.d/disable-with-time-daemon.conf

All major NTP implementations ship a native service file nowadays with a
Conflicts=systemd-timesyncd.service so this drop-in is no longer
necessary.

Closes: #873185

This should resolve the current issue in Ubuntu, where when both ntpd
and timesyncd are installed, both are enabled yet neither run.

** Affects: systemd (Ubuntu)
 Importance: High
 Assignee: Dimitri John Ledkov (xnox)
 Status: Fix Committed

** Affects: systemd (Ubuntu Artful)
 Importance: High
 Assignee: Dimitri John Ledkov (xnox)
 Status: Fix Committed

** Also affects: systemd (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Changed in: systemd (Ubuntu Artful)
   Importance: Undecided => High

** Changed in: systemd (Ubuntu Artful)
   Status: New => Fix Committed

** Changed in: systemd (Ubuntu Artful)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

Title:
  timesyncd has redundant condition conflict with ntp and others

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Artful:
  Fix Committed

Bug description:
  Cherrypick

  Drop systemd-timesyncd.service.d/disable-with-time-daemon.conf
  
  All major NTP implementations ship a native service file nowadays with a
  Conflicts=systemd-timesyncd.service so this drop-in is no longer
  necessary.
  
  Closes: #873185

  This should resolve the current issue in Ubuntu, where when both ntpd
  and timesyncd are installed, both are enabled yet neither run.

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

-- 
Mailing list: https://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 1693992] Re: gdm-session-worker crashed with SIGABRT in g_assertion_message() from g_assertion_message_expr() from load_users() from load_idle()

2017-10-04 Thread Daniel van Vugt 
** Summary changed:

- 
/usr/lib/gdm3/gdm-session-worker:6:g_assertion_message:g_assertion_message_expr:load_users:load_idle:g_main_dispatch
+ gdm-session-worker crashed with SIGABRT in g_assertion_message() from 
g_assertion_message_expr() from load_users() from load_idle()

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

Title:
  gdm-session-worker crashed with SIGABRT in g_assertion_message() from
  g_assertion_message_expr() from load_users() from load_idle()

Status in Ubuntu GNOME:
  New
Status in accountsservice package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gdm3.  This problem was most recently seen with package version 
3.24.1-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/c0848264c9da4adaeb5da47a7aa34ce5bdd84909 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

-- 
Mailing list: https://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 1693992] Re: /usr/lib/gdm3/gdm-session-worker:6:g_assertion_message:g_assertion_message_expr:load_users:load_idle:g_main_dispatch

2017-10-04 Thread Launchpad Bug Tracker 
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  gdm-session-worker crashed with SIGABRT in g_assertion_message() from
  g_assertion_message_expr() from load_users() from load_idle()

Status in Ubuntu GNOME:
  New
Status in accountsservice package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gdm3.  This problem was most recently seen with package version 
3.24.1-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/c0848264c9da4adaeb5da47a7aa34ce5bdd84909 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

-- 
Mailing list: https://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 1717213] Re: lubuntu installation with fully encryped disk is broken

2017-10-04 Thread Alois Vitasek 
** Information type changed from Public to Public Security

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

Title:
  lubuntu installation with fully encryped disk is broken

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Hello,

  This issue is concerned to the installation procedure for the Lubuntu 
distribution.
  I am using Lubuntu 17.04.

  I was trying to install Lubuntu on new notebook with fully encrypted disk 
from the USB stick.
  It was not possible and had to do some workarounds (now it works).

  There was three issues.

  1) Before installation I had run

 sudo swapoff --all

  2) Before installation I had install missing packake

 lvm2

  3) When the installation finished successfully, computer was not able to
 to boot. When I entered disk password, the boot process failed on strange 
error.
 (I have not it)

 I have applied these steps

 https://feeding.cloud.geek.nz/posts/recovering-from-unbootable-
  ubuntu-encrypted-lvm-root-partition/

 ant it works.

 The problem was, that in the installed system was missing package

   lvm2

  So I believe, that the problem is just only with missing package lvm2 in the 
installation
  system and also with missing this lvm2 package in the installed system.
  (and also with swapoff --all)

  Best regards

  Alois Vitasek

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: lvm2 2.02.167-1ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Thu Sep 14 10:20:42 2017
  InstallationDate: Installed on 2017-09-05 (8 days ago)
  InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: lvm2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1707611] Re: Sound does not automatically switch to HDMI when connected

2017-10-04 Thread Daniel van Vugt 
** Summary changed:

- Sound does not automatically play on new audio device
+ Sound does not automatically switch to HDMI when connected

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

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

Title:
  Sound does not automatically switch to HDMI when connected

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When connecting a HDMI cable or other audio device, the user must
  manually click on the "sound volume" in the top-right and switch to
  the newly connected device.

  Example: you connect a HDMI cable to the television, but then you must
  manually choose the HDMI sound option; it does not get selected
  automatically.

  Often times e.g. when the HDMI cable is disconnected, the user must
  then manually click on the "speakers" or "line out" setting - EVEN IF
  IT'S ALREADY SELECTED, it must be clicked on again for the sound to
  work through the computer's speakers.

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

-- 
Mailing list: https://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 1707487] Re: Bluetooth speaker only plays as mono

2017-10-04 Thread Daniel van Vugt 
** Changed in: pulseaudio (Ubuntu)
   Status: Expired => New

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

Title:
  Bluetooth speaker only plays as mono

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I connect my Sony SRS-X1 Bluetooth speaker to Ubuntu, it only
  plays back as "mono" and refuses to use "hi fidelity".

  I have Windows 10 installed on the same laptop and when I've used the
  Bluetooth speaker in Ubuntu, Windows will "forget" the speaker on its
  Bluetooth list. I have to hold in the "reset" button on the speaker
  itself and re-add the speaker to Windows 10. This ONLY HAPPENS if I
  try using this speaker in Ubuntu, which suggests that Ubuntu is
  forcing the speaker into "mono" mode and Windows then sees it as a
  different device?

  Please help.
  I will post all needed outputs as instructed.

  Cheers!
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  3626 F...m pulseaudio
   /dev/snd/controlC0:  david  3626 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-28 (367 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: pulseaudio 1:8.0-0ubuntu3.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Tags:  xenial
  Uname: Linux 4.4.0-87-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/16/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Insyde Corp.
  dmi.chassis.version: V2.21
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.21:bd12/16/2013:svnAcer:pnAspireV3-571:pvrV2.21:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.21:
  dmi.product.name: Aspire V3-571
  dmi.product.version: V2.21
  dmi.sys.vendor: Acer
  modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 
2016-07-29T10:08:04.428983

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

-- 
Mailing list: https://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 1086736] Re: [quantal] [regression] compiz (opengl) - Fatal: GL_OES_EGL_image is missing

2017-10-04 Thread Daniel van Vugt 
Don't really care about this bug any more :)

** Changed in: mesa (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  [quantal] [regression] compiz (opengl) - Fatal: GL_OES_EGL_image is
  missing

Status in Compiz:
  Invalid
Status in mesa package in Ubuntu:
  Won't Fix

Bug description:
  In precise I could build compiz for GLES/EGL and it would run fine.
  Now on quantal it doesn't work. And the error makes no sense because I
  have the "missing" extensions...

  ./bin/compiz (opengl) - Fatal: GL_OES_EGL_image is missing
  libEGL warning: DRI2: failed to authenticate
  ./bin/compiz (opengl) - Fatal: GL_OES_EGL_image is missing
  libEGL warning: DRI2: failed to authenticate
  ./bin/compiz (opengl) - Fatal: GL_OES_EGL_image is missing
  libEGL warning: DRI2: failed to authenticate
  ./bin/compiz (opengl) - Fatal: GL_OES_EGL_image is missing
  libEGL warning: DRI2: failed to authenticate
  ./bin/compiz (opengl) - Fatal: GL_OES_EGL_image is missing
  libEGL warning: DRI2: failed to authenticate
  ./bin/compiz (opengl) - Fatal: GL_OES_EGL_image is missing

  but running: es2_info 
  libEGL warning: unsupported platform Windows
  EGL_VERSION = 1.4 (DRI2)
  EGL_VENDOR = Mesa Project
  EGL_EXTENSIONS = EGL_MESA_drm_image EGL_WL_bind_wayland_display 
EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_image 
EGL_KHR_gl_renderbuffer_image EGL_KHR_surfaceless_context 
EGL_KHR_create_context EGL_NOK_swap_region EGL_NOK_texture_from_pixmap 
EGL_NV_post_sub_buffer 
  EGL_CLIENT_APIS = OpenGL OpenGL_ES OpenGL_ES2 
  GL_VERSION: OpenGL ES 2.0 Mesa 9.0
  GL_RENDERER: Mesa DRI Intel(R) Sandybridge Desktop 
  GL_EXTENSIONS:
  GL_EXT_blend_minmax, GL_EXT_multi_draw_arrays, 
  GL_EXT_texture_filter_anisotropic, GL_EXT_texture_compression_dxt1, 
  GL_EXT_texture_format_BGRA, GL_OES_compressed_ETC1_RGB8_texture, 
  GL_OES_depth24, GL_OES_element_index_uint, GL_OES_fbo_render_mipmap, 
  GL_OES_mapbuffer, GL_OES_rgb8_rgba8, GL_OES_standard_derivatives, 
  GL_OES_stencil8, GL_OES_texture_3D, GL_OES_texture_npot, 
  GL_OES_EGL_image, GL_OES_depth_texture, GL_OES_packed_depth_stencil, 
  GL_EXT_texture_type_2_10_10_10_REV, GL_APPLE_texture_max_level, 
  GL_EXT_read_format_bgra, GL_NV_fbo_color_attachments, 
  GL_OES_vertex_array_object, GL_EXT_texture_rg, GL_EXT_unpack_subimage, 
  GL_NV_draw_buffers, GL_NV_read_buffer

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

-- 
Mailing list: https://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 1719355] Re: Switcher widget background goes outside its border

2017-10-04 Thread Daniel van Vugt 
** Changed in: ubuntu-themes
   Status: Triaged => In Progress

** Changed in: ubuntu-themes (Ubuntu)
 Assignee: (unassigned) => Carlo Lobrano (c-lobrano)

** Changed in: ubuntu-themes (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Switcher widget background goes outside its border

Status in Ubuntu theme:
  In Progress
Status in Ubuntu UX:
  New
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  In both Ambiance and Radiance themes, the switcher background is
  visible outside the widget border when inside a headerbar.

  
  See picture from Gnome Control Settings -> Search

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

-- 
Mailing list: https://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 1720300] Re: List items become invisible when selected in g-c-c

2017-10-04 Thread Daniel van Vugt 
I experience the same bug when switching colour profiles. Very annoying
that I can't see what's selected without selecting something else first.

** Changed in: gnome-control-center (Ubuntu)
   Importance: Low => Medium

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Undecided => Medium

** Also affects: ubuntu-themes
   Importance: Undecided
   Status: New

** Summary changed:

- List items become invisible when selected in g-c-c
+ List items become invisible when selected in gnome-control-center

** Changed in: ubuntu-themes
   Importance: Undecided => Medium

** Changed in: ubuntu-themes
   Status: New => Confirmed

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

Title:
  List items become invisible when selected in gnome-control-center

Status in Ubuntu theme:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Steps:

  1. Open gnome-control-center
  2. Select the Search panel
  3. Select any of the items in the list
  4. They become invisible when selected

  They should be visibly selected.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170925-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 29 08:17:05 2017
  InstallationDate: Installed on 2017-09-21 (7 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1720519] Re: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.

2017-10-04 Thread Daniel van Vugt 
pulseaudio 1:10.0-2ubuntu3 does only load that module once. So it sounds
like some other config file is getting loaded with it in your case.
Perhaps Kubuntu-specific? Can anyone with this bug search their /etc and
~/ and find out all the locations where switch-on-connect is loaded?

grep -r 'load-module module-switch-on-connect' /etc

** Changed in: pulseaudio (Ubuntu)
 Assignee: ben van 't ende (benvantende) => (unassigned)

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

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: pulseaudio (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => (unassigned)

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

Title:
  Module "module-switch-on-connect" should be loaded once at most.
  Refusing to load.

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Pulseaudio daemon does not start after the update to Kubuntu 17.10
  beta2, because the module fails to load although it is there.

  From 'pulseaudio -vv'

  E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded 
once at most. Refusing to load.
  E: [pulseaudio] main.c: Module load failed.
  E: [pulseaudio] main.c: Failed to initialize daemon.

  PS sorry I am not a seasoned bug reporter. Let me know if I can
  provide more info.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ben2809 F...m chrome
   /dev/snd/controlC0:  ben2809 F chrome
   /dev/snd/timer:  ben2809 f chrome
  CurrentDesktop: KDE
  Date: Sat Sep 30 11:20:55 2017
  InstallationDate: Installed on 2017-04-07 (175 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: B150M-ITX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

-- 
Mailing list: https://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 1721023] Re: select window is pop up on top left of display

2017-10-04 Thread Jean-Baptiste Lallement 
** Tags removed: wayland-session
** Tags added: wayland

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

** Changed in: ibus (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  select window is pop up on top left of display

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  On wayland session, ibus (or wayland or gtk) display selection window
  on top left of the display.

  No problem on xorg session.

  How to reproduce:
  1. Install artful
  2. Install ibus-mozc (or install artful as Japanese locale)
  3. Login to wayland session
  4. Startup gedit or gnome-terminal
  5. Press Hankaku/Zenkaku (or enable Japanese input method)
  6. Type any words and press space

  Expected result:
  The select window pop up on bottom of the cursor.

  Actual result:
  The select window pop up on top left of the display.

  Fireforx hasn't any problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ibus 1.5.14-2ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  3 21:46:09 2017
  InstallationDate: Installed on 2017-09-18 (14 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1720684] Re: Bluetooth speaker used the HSP/HFP profile by default rather than the higher-quality A2DP profile

2017-10-04 Thread Daniel van Vugt 
Bluetooth audio and profile selection is actually the job of pulseaudio,
not bluez (surprisingly).

Also, A2DP has always been preferred over HSP/HFP but the availability
and detection of A2DP has been historically buggy. So the selection
might not turn out as you hope. AFAIK fixes for this already exist in
17.10 and in 16.04:

https://launchpad.net/ubuntu/+source/pulseaudio

Unfortunately it seems 17.04 has been neglected in this area. Although
to be fair 17.04 is also end-of-life soon:

https://wiki.ubuntu.com/Releases

Please try live-booting the latest 17.10 image and tell us if that has
indeed resolved the problem for your hardware:

http://cdimages.ubuntu.com/daily-live/current/

** Changed in: bluez (Ubuntu)
   Status: New => Incomplete

** Package changed: bluez (Ubuntu) => pulseaudio (Ubuntu)

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

Title:
  Bluetooth speaker used the HSP/HFP profile by default rather than the
  higher-quality A2DP profile

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Kubuntu 17.04
  Bluetooth device: 
https://smile.amazon.com/VicTsing-Wireless-Waterproof-Hands-Free-Speakerphone/dp/B074DX13T1
 (itentifies itself as "C6")

  The above Bluetooth speaker paired and started streaming audio
  perfectly in Kubuntu 17.04. But the audio quality was poor, because
  the default audio profile was the low-quality HSP/HFP one. When I
  switched it to the A2DP profile, it sounded perfect again.

  Can we make A2DP the default playback profile for Bluetooth audio
  devices?

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

-- 
Mailing list: https://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 1721102] Re: Thin line at the left of Simple Scan's "Scan" headerbar button

2017-10-04 Thread Jean-Baptiste Lallement 
** Tags removed: wayland-session

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

Title:
  Thin line at the left of Simple Scan's "Scan" headerbar button

Status in Ubuntu theme:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  There is a thin colored line (green or red) at the left of rounded
  button, for example in simple-scan in the screenshot attached (I
  didn't find any other app affected ATM)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170930-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  3 20:16:32 2017
  InstallationDate: Installed on 2013-09-03 (1490 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1721160] Re: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all

2017-10-04 Thread Jean-Baptiste Lallement 
** Tags removed: wayland-session

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

Title:
  [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at
  all

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  If I unplug the green plug to my speakers after my computer finishes
  booting and then immediately plug it back in again, sound works
  correctly.

  Prior to the unplug / replug trick the Line-out is missing from Sound 
settings.
  After the unplug / replug trick the Line-out is correctly listed in Sound 
settings.

  I will attach screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1272 F pulseaudio
   /dev/snd/controlC1:  scott  1272 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  3 17:21:49 2017
  InstallationDate: Installed on 2017-10-03 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 926 F pulseaudio
scott  1272 F pulseaudio
   /dev/snd/controlC1:  gdm 926 F pulseaudio
scott  1272 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

<    1   2