[Touch-packages] [Bug 1870729] Re: DHCP Server regularly killed code=killed, status=6/ABRT

[Andrew Welham]

incorrect statement above, since i have been bouncing the dhcp servers
to try to find a pattern, the primary dhcp server logged a single error
but continues to work

Apr  8 06:32:36 dhcp-primary systemd[1]: isc-dhcp-server.service: Main
process exited, code=killed, status=6/ABRT

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

Title:
  DHCP Server regularly killed code=killed, status=6/ABRT

Status in isc-dhcp package in Ubuntu:
  Fix Released

Bug description:
  On Ubuntu 20.04 The idc-dhcp- server version is
  isc-dhcp-server:
Installed: (none)
Candidate: 4.4.1-2.1ubuntu3
Version table:
   4.4.1-2.1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  
  The DHCP server is being regularly killed, when searching google the  bug 
looks very similar to an older bug regarding accessing a lease file, that was 
fixed year ago. As a temporary fix in systemd I have enabled a restart every 
time the main process fails. The error got worse when i start to run a pair of 
dhcp servers syncing state between each other

  
  I regularly see the following in the syslog

  Apr  4 00:04:55 gw sh[1500]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
  Apr  4 00:04:55 gw sh[1500]: #0 0x7f36befeda4a in ??
  Apr  4 00:04:55 gw sh[1500]: #1 0x7f36befed980 in ??
  Apr  4 00:04:55 gw sh[1500]: #2 0x7f36bf0297e1 in ??
  Apr  4 00:04:55 gw sh[1500]: #3 0x7f36bedd0609 in ??
  Apr  4 00:04:55 gw sh[1500]: #4 0x7f36bef0c153 in ??
  Apr  4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Main process exited, 
code=killed, status=6/ABRT
  Apr  4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Failed with result 
'signal'.
  Apr  4 00:05:00 gw systemd[1]: isc-dhcp-server.service: Scheduled restart 
job, restart counter is at 3.
  Apr  4 00:05:00 gw systemd[1]: Stopped ISC DHCP IPv4 server.
  Apr  4 00:05:00 gw systemd[1]: Started ISC DHCP IPv4 server.
  Apr  4 00:05:00 gw kernel: [ 3508.161248] audit: type=1400 
audit(1585958700.678:46): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2068/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw dhcpd[2049]: Internet Systems Consortium DHCP Server 4.4.1
  Apr  4 00:05:00 gw sh[2049]: Internet Systems Consortium DHCP Server 4.4.1
  Apr  4 00:05:00 gw sh[2049]: Copyright 2004-2018 Internet Systems Consortium.
  Apr  4 00:05:00 gw sh[2049]: All rights reserved.
  Apr  4 00:05:00 gw sh[2049]: For info, please visit 
https://www.isc.org/software/dhcp/
  Apr  4 00:05:00 gw dhcpd[2049]: Copyright 2004-2018 Internet Systems 
Consortium.
  Apr  4 00:05:00 gw dhcpd[2049]: All rights reserved.
  Apr  4 00:05:00 gw dhcpd[2049]: For info, please visit 
https://www.isc.org/software/dhcp/
  Apr  4 00:05:00 gw kernel: [ 3508.161561] audit: type=1400 
audit(1585958700.678:47): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2069/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw kernel: [ 3508.161563] audit: type=1400 
audit(1585958700.682:48): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2070/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw dhcpd[2049]: Config file: /etc/dhcp/dhcpd.conf
  Apr  4 00:05:00 gw sh[2049]: Config file: /etc/dhcp/dhcpd.conf
  Apr  4 00:05:00 gw sh[2049]: Database file: /var/lib/dhcp/dhcpd.leases
  Apr  4 00:05:00 gw sh[2049]: PID file: /run/dhcp-server/dhcpd.pid
  Apr  4 00:05:00 gw dhcpd[2049]: Database file: /var/lib/dhcp/dhcpd.leases
  Apr  4 00:05:00 gw dhcpd[2049]: PID file: /run/dhcp-server/dhcpd.pid
  Apr  4 00:05:00 gw dhcpd[2049]: Wrote 0 deleted host decls to leases file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1870729/+subscriptions

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

[Touch-packages] [Bug 1870729] Re: DHCP Server regularly killed code=killed, status=6/ABRT

[Andrew Welham]

I tried this.
If you stop the primary dhcp server
Start the backup (This time it works)
Restart the primary dhcp server
Secondary dhcp server fails with the error 

Apr  8 06:26:00 dhcp-backupl dhcpd[1360]: failover peer failover-partner: peer 
moves from communications-interrupted to normal
Apr  8 06:26:00 dhcp-backupl dhcpd[1360]: failover peer failover-partner: Both 
servers normal
Apr  8 06:26:00 dhcp-backupl sh[1360]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
Apr  8 06:26:00 dhcp-backupl sh[1360]: #0 0x7fbe199fda4a in ??
Apr  8 06:26:00 dhcp-backupl sh[1360]: #1 0x7fbe199fd980 in ??
Apr  8 06:26:00 dhcp-backupl sh[1360]: #2 0x7fbe19a397e1 in ??
Apr  8 06:26:00 dhcp-backupl sh[1360]: #3 0x7fbe197e0609 in ??
Apr  8 06:26:00 dhcp-backupl sh[1360]: #4 0x7fbe1991c103 in ??
Apr  8 06:26:01 dhcp-backupl systemd[1]: isc-dhcp-server.service: Main process 
exited, code=killed, status=6/ABRT
Apr  8 06:26:01 dhcp-backupl systemd[1]: isc-dhcp-server.service: Failed with 
result 'signal'

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

Title:
  DHCP Server regularly killed code=killed, status=6/ABRT

Status in isc-dhcp package in Ubuntu:
  Fix Released

Bug description:
  On Ubuntu 20.04 The idc-dhcp- server version is
  isc-dhcp-server:
Installed: (none)
Candidate: 4.4.1-2.1ubuntu3
Version table:
   4.4.1-2.1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  
  The DHCP server is being regularly killed, when searching google the  bug 
looks very similar to an older bug regarding accessing a lease file, that was 
fixed year ago. As a temporary fix in systemd I have enabled a restart every 
time the main process fails. The error got worse when i start to run a pair of 
dhcp servers syncing state between each other

  
  I regularly see the following in the syslog

  Apr  4 00:04:55 gw sh[1500]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
  Apr  4 00:04:55 gw sh[1500]: #0 0x7f36befeda4a in ??
  Apr  4 00:04:55 gw sh[1500]: #1 0x7f36befed980 in ??
  Apr  4 00:04:55 gw sh[1500]: #2 0x7f36bf0297e1 in ??
  Apr  4 00:04:55 gw sh[1500]: #3 0x7f36bedd0609 in ??
  Apr  4 00:04:55 gw sh[1500]: #4 0x7f36bef0c153 in ??
  Apr  4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Main process exited, 
code=killed, status=6/ABRT
  Apr  4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Failed with result 
'signal'.
  Apr  4 00:05:00 gw systemd[1]: isc-dhcp-server.service: Scheduled restart 
job, restart counter is at 3.
  Apr  4 00:05:00 gw systemd[1]: Stopped ISC DHCP IPv4 server.
  Apr  4 00:05:00 gw systemd[1]: Started ISC DHCP IPv4 server.
  Apr  4 00:05:00 gw kernel: [ 3508.161248] audit: type=1400 
audit(1585958700.678:46): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2068/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw dhcpd[2049]: Internet Systems Consortium DHCP Server 4.4.1
  Apr  4 00:05:00 gw sh[2049]: Internet Systems Consortium DHCP Server 4.4.1
  Apr  4 00:05:00 gw sh[2049]: Copyright 2004-2018 Internet Systems Consortium.
  Apr  4 00:05:00 gw sh[2049]: All rights reserved.
  Apr  4 00:05:00 gw sh[2049]: For info, please visit 
https://www.isc.org/software/dhcp/
  Apr  4 00:05:00 gw dhcpd[2049]: Copyright 2004-2018 Internet Systems 
Consortium.
  Apr  4 00:05:00 gw dhcpd[2049]: All rights reserved.
  Apr  4 00:05:00 gw dhcpd[2049]: For info, please visit 
https://www.isc.org/software/dhcp/
  Apr  4 00:05:00 gw kernel: [ 3508.161561] audit: type=1400 
audit(1585958700.678:47): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2069/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw kernel: [ 3508.161563] audit: type=1400 
audit(1585958700.682:48): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2070/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw dhcpd[2049]: Config file: /etc/dhcp/dhcpd.conf
  Apr  4 00:05:00 gw sh[2049]: Config file: /etc/dhcp/dhcpd.conf
  Apr  4 00:05:00 gw sh[2049]: Database file: /var/lib/dhcp/dhcpd.leases
  Apr  4 00:05:00 gw sh[2049]: PID file: /run/dhcp-server/dhcpd.pid
  Apr  4 00:05:00 gw dhcpd[2049]: Database file: /var/lib/dhcp/dhcpd.leases
  Apr  4 00:05:00 gw dhcpd[2049]: PID file: /run/dhcp-server/dhcpd.pid
  Apr  4 00:05:00 gw dhcpd[2049]: Wrote 0 deleted host decls to leases file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1870729/+subscriptions

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

[Touch-packages] [Bug 1870729] Re: DHCP Server regularly killed code=killed, status=6/ABRT

[Andrew Welham]

The primary DHCP server is now fine, but the secondary won't start any more 
(although it did immediately after patching)
I now get the error
Apr  8 06:14:11 dhcp-backup dhcpd[1181]:
Apr  8 06:14:11 dhcp-backup dhcpd[1181]: Sending on   
Socket/fallback/fallback-net
Apr  8 06:14:11 dhcp-backup dhcpd[1181]: failover peer failover-partner: I move 
from normal to startup
Apr  8 06:14:11 dhcp-backup dhcpd[1181]: Server starting service.
Apr  8 06:14:11 dhcp-backup dhcpd[1181]: failover peer failover-partner: peer 
moves from normal to communications-interrupted
Apr  8 06:14:11 dhcp-backup dhcpd[1181]: failover peer failover-partner: I move 
from startup to normal
Apr  8 06:14:11 dhcp-backup dhcpd[1181]: balancing pool 5645d4679930 Internal  
total 250  free 125  backup 125  lts 0  max-own (+/-)25
Apr  8 06:14:11 dhcp-backup dhcpd[1181]: balanced pool 5645d4679930 Internal  
total 250  free 125  backup 125  lts 0  max-misbal 38
Apr  8 06:14:11 dhcp-backup dhcpd[1181]: balancing pool 5645d46e2cf0 Internal  
total 250  free 111  backup 139  lts 14  max-own (+/-)25
Apr  8 06:14:11 dhcp-backup dhcpd[1181]: balanced pool 5645d46e2cf0 Internal  
total 250  free 111  backup 139  lts 14  max-misbal 38
Apr  8 06:14:11 dhcp-backup dhcpd[1181]: failover peer failover-partner: peer 
moves from communications-interrupted to normal
Apr  8 06:14:11 dhcp-backup dhcpd[1181]: failover peer failover-partner: Both 
servers normal
Apr  8 06:14:11 dhcp-backup sh[1181]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
Apr  8 06:14:11 dhcp-backup sh[1181]: #0 0x7f0a52b25a4a in ??
Apr  8 06:14:11 dhcp-backup sh[1181]: #1 0x7f0a52b25980 in ??
Apr  8 06:14:11 dhcp-backup sh[1181]: #2 0x7f0a52b617e1 in ??
Apr  8 06:14:11 dhcp-backup sh[1181]: #3 0x7f0a52908609 in ??
Apr  8 06:14:11 dhcp-backup sh[1181]: #4 0x7f0a52a44103 in ??
Apr  8 06:14:12 dhcp-backup systemd[1]: isc-dhcp-server.service: Main process 
exited, code=killed, status=6/ABRT
Apr  8 06:14:12 dhcp-backup systemd[1]: isc-dhcp-server.service: Failed with 
result 'signal'.

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

Title:
  DHCP Server regularly killed code=killed, status=6/ABRT

Status in isc-dhcp package in Ubuntu:
  Fix Released

Bug description:
  On Ubuntu 20.04 The idc-dhcp- server version is
  isc-dhcp-server:
Installed: (none)
Candidate: 4.4.1-2.1ubuntu3
Version table:
   4.4.1-2.1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  
  The DHCP server is being regularly killed, when searching google the  bug 
looks very similar to an older bug regarding accessing a lease file, that was 
fixed year ago. As a temporary fix in systemd I have enabled a restart every 
time the main process fails. The error got worse when i start to run a pair of 
dhcp servers syncing state between each other

  
  I regularly see the following in the syslog

  Apr  4 00:04:55 gw sh[1500]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
  Apr  4 00:04:55 gw sh[1500]: #0 0x7f36befeda4a in ??
  Apr  4 00:04:55 gw sh[1500]: #1 0x7f36befed980 in ??
  Apr  4 00:04:55 gw sh[1500]: #2 0x7f36bf0297e1 in ??
  Apr  4 00:04:55 gw sh[1500]: #3 0x7f36bedd0609 in ??
  Apr  4 00:04:55 gw sh[1500]: #4 0x7f36bef0c153 in ??
  Apr  4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Main process exited, 
code=killed, status=6/ABRT
  Apr  4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Failed with result 
'signal'.
  Apr  4 00:05:00 gw systemd[1]: isc-dhcp-server.service: Scheduled restart 
job, restart counter is at 3.
  Apr  4 00:05:00 gw systemd[1]: Stopped ISC DHCP IPv4 server.
  Apr  4 00:05:00 gw systemd[1]: Started ISC DHCP IPv4 server.
  Apr  4 00:05:00 gw kernel: [ 3508.161248] audit: type=1400 
audit(1585958700.678:46): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2068/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw dhcpd[2049]: Internet Systems Consortium DHCP Server 4.4.1
  Apr  4 00:05:00 gw sh[2049]: Internet Systems Consortium DHCP Server 4.4.1
  Apr  4 00:05:00 gw sh[2049]: Copyright 2004-2018 Internet Systems Consortium.
  Apr  4 00:05:00 gw sh[2049]: All rights reserved.
  Apr  4 00:05:00 gw sh[2049]: For info, please visit 
https://www.isc.org/software/dhcp/
  Apr  4 00:05:00 gw dhcpd[2049]: Copyright 2004-2018 Internet Systems 
Consortium.
  Apr  4 00:05:00 gw dhcpd[2049]: All rights reserved.
  Apr  4 00:05:00 gw dhcpd[2049]: For info, please visit 
https://www.isc.org/software/dhcp/
  Apr  4 00:05:00 gw kernel: [ 3508.161561] audit: type=1400 
audit(1585958700.678:47): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2069/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 

[Touch-packages] [Bug 1870073] Re: python-debian ftbfs in focal

[Michael Hudson-Doyle]

Updated the description which was about python-glanceclient

** Description changed:

  seen in the second focal test rebuild
- 
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18963677/+files/buildlog_ubuntu-focal-amd64.python-glanceclient_1%3A2.17.0-0ubuntu2_BUILDING.txt.gz
+ 
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18963359
+ 
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18963359/+files/buildlog_ubuntu-focal-amd64.python-debian_0.1.36build1_BUILDING.txt.gz
  
- During handling of the above exception, another exception occurred:
+ the failure is this:
  
- 
- Traceback (most recent call last):
- 
-   File "/usr/lib/python3/dist-packages/requests/adapters.py", line 439, 
in send
- resp = conn.urlopen(
- 
-   File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 
719, in urlopen
- retries = retries.increment(
- 
-   File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 436, 
in increment
- raise MaxRetryError(_pool, url, error or ResponseError(cause))
- 
- urllib3.exceptions.MaxRetryError:
- HTTPSConnectionPool(host='0.0.0.0', port=45175): Max retries exceeded
- with url: /v2/images/image123 (Caused by SSLError(SSLError("bad
- handshake: SysCallError(-1, 'Unexpected EOF')")))
- 
- 
- During handling of the above exception, another exception occurred:
- 
- 
- Traceback (most recent call last):
- 
-   File "/<>/glanceclient/common/http.py", line 269, in 
_request
- resp = self.session.request(method,
- 
-   File "/usr/lib/python3/dist-packages/requests/sessions.py", line 533, 
in request
- resp = self.send(prep, **send_kwargs)
- 
-   File "/usr/lib/python3/dist-packages/requests/sessions.py", line 646, 
in send
- r = adapter.send(request, **kwargs)
- 
-   File "/usr/lib/python3/dist-packages/requests/adapters.py", line 514, 
in send
- raise SSLError(e, request=request)
- 
- requests.exceptions.SSLError: HTTPSConnectionPool(host='0.0.0.0',
- port=45175): Max retries exceeded with url: /v2/images/image123 (Caused
- by SSLError(SSLError("bad handshake: SysCallError(-1, 'Unexpected
- EOF')")))
- 
- 
- During handling of the above exception, another exception occurred:
- 
- 
- Traceback (most recent call last):
- 
-   File "/<>/glanceclient/tests/unit/test_ssl.py", line 124, 
in test_v2_requests_cert_verification
- gc.images.get('image123')
- 
-   File "/<>/glanceclient/v2/images.py", line 198, in get
- return self._get(image_id)
- 
-   File "/<>/glanceclient/common/utils.py", line 598, in inner
- return RequestIdProxy(wrapped(*args, **kwargs))
- 
-   File "/<>/glanceclient/v2/images.py", line 191, in _get
- resp, body = self.http_client.get(url, headers=header)
- 
-   File "/<>/glanceclient/common/http.py", line 315, in get
- return self._request('GET', url, **kwargs)
- 
-   File "/<>/glanceclient/common/http.py", line 282, in 
_request
- raise exc.CommunicationError(message=message)
- 
- glanceclient.exc.CommunicationError: Error finding address for
- https://0.0.0.0:45175/v2/images/image123:
- HTTPSConnectionPool(host='0.0.0.0', port=45175): Max retries exceeded
- with url: /v2/images/image123 (Caused by SSLError(SSLError("bad
- handshake: SysCallError(-1, 'Unexpected EOF')")))
- 
- 
- During handling of the above exception, another exception occurred:
- 
- 
- Traceback (most recent call last):
- 
-   File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in 
patched
- return func(*args, **keywargs)
- 
-   File "/<>/glanceclient/tests/unit/test_ssl.py", line 128, 
in test_v2_requests_cert_verification
- self.fail('No certificate failure message is received')
- 
-   File "/usr/lib/python3/dist-packages/unittest2/case.py", line 690, in 
fail
- raise self.failureException(msg)
- 
- AssertionError: No certificate failure message is received
- 
- 
- ==
- Totals
- ==
- Ran: 635 tests in 1.7474 sec.
-  - Passed: 623
-  - Skipped: 7
-  - Expected Fail: 0
-  - Unexpected Success: 0
-  - Failed: 5
- Sum of execute time for each test: 5.8393 sec.
- 
- ==
- Worker Balance
- ==
-  - Worker 0 (159 tests) => 0:00:01.182108
-  - Worker 1 (159 tests) => 0:00:01.607279
-  - Worker 2 (159 tests) => 0:00:01.570729
-  - Worker 3 (158 tests) => 0:00:01.650056
- make[1]: *** [debian/rules:24: override_dh_auto_test] Error 1
- make[1]: Leaving directory '/<>'
+ /bin/sh: 1: lib/debian/doc-debtags: not found

** Changed in: python-debian (Ubuntu)
 Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson)

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

Title:
  python-debian ftbfs in focal

Status in python-debian package in Ubuntu:
  Confirmed

Bug description:
  seen in the 

[Touch-packages] [Bug 1871023] Re: json_gvariant_deserialize can fail due to unrelated code setting errno

[Robert Ancell]

Confirmed fixed in Bionic with json-glib 1.4.2-3ubuntu0.18.04.1


** Tags removed: verification-needed 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 json-glib in Ubuntu.
https://bugs.launchpad.net/bugs/1871023

Title:
  json_gvariant_deserialize can fail due to unrelated code setting errno

Status in json-glib package in Ubuntu:
  Fix Released
Status in json-glib source package in Bionic:
  Fix Committed
Status in json-glib source package in Eoan:
  Fix Committed
Status in json-glib source package in Focal:
  Fix Released

Bug description:
  [Impact]
  json_gvariant_deserialize can fail due to unrelated code setting errno, this 
is causing snapd-glib to not be able to decode responses from snapd. Fixed in 
https://gitlab.gnome.org/GNOME/json-glib/-/merge_requests/22

  [Test Case]
  1. Run GNOME Software from the command line
  2. Browse to postman

  Expected result:
  Errors are not shown on the command line

  Observed result:
  The following errors are shown on the command line:
  05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed
  05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed
  05:17:29:0877 Gs  not GsPlugin error g-io-error-quark:35: Invalid string 
value converting to GVariant
  05:17:29:0877 Gs  not handling error failed for action refine: Invalid string 
value converting to GVariant

  (These errors may not always occur, and is likely racy).

  [Regression Potential]
  Small risk of introducing other bugs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1871023/+subscriptions

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

[Touch-packages] [Bug 1871023] Re: json_gvariant_deserialize can fail due to unrelated code setting errno

[Robert Ancell]

Confirmed fixed in Eoan with json-glib 1.4.4-2ubuntu0.19.10.1

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

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

Title:
  json_gvariant_deserialize can fail due to unrelated code setting errno

Status in json-glib package in Ubuntu:
  Fix Released
Status in json-glib source package in Bionic:
  Fix Committed
Status in json-glib source package in Eoan:
  Fix Committed
Status in json-glib source package in Focal:
  Fix Released

Bug description:
  [Impact]
  json_gvariant_deserialize can fail due to unrelated code setting errno, this 
is causing snapd-glib to not be able to decode responses from snapd. Fixed in 
https://gitlab.gnome.org/GNOME/json-glib/-/merge_requests/22

  [Test Case]
  1. Run GNOME Software from the command line
  2. Browse to postman

  Expected result:
  Errors are not shown on the command line

  Observed result:
  The following errors are shown on the command line:
  05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed
  05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed
  05:17:29:0877 Gs  not GsPlugin error g-io-error-quark:35: Invalid string 
value converting to GVariant
  05:17:29:0877 Gs  not handling error failed for action refine: Invalid string 
value converting to GVariant

  (These errors may not always occur, and is likely racy).

  [Regression Potential]
  Small risk of introducing other bugs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1871023/+subscriptions

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

[Touch-packages] [Bug 1871394] Re: modeset: Loss of VGA signal (ast2500) on login

[Daniel van Vugt]

The attached Xorg log files seem to show that it knows about both GPUs
and it claims to be using both...

1. Are you able to work around the problem by logging into "Ubuntu on
Wayland" instead?

2. Does the same problem also occur in Ubuntu 20.04 (to be released
soon)? http://cdimage.ubuntu.com/daily-live/current/ or in 19.10
(https://ubuntu.com/download/desktop)?

** Summary changed:

- no dual head video with 2 on board sources: ast2500 and i915
+ modeset: Loss of VGA signal (ast2500) on login

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

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

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

Title:
  modeset: Loss of VGA signal (ast2500) on login

Status in mutter package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I am creating a new computer platforms.  It provides two video
  sources: an Intel i915 DisplayPort and an AST2500 VGA.  The i915 also
  provides HDMI, but it is disconnected/disabled.

  EXPECTED BEHAVIOR: Video is presented through the AST2500 to VGA and
  the i915 to DisplayPort, mergine the displays to a unified layout when
  a layout is provided to xorg.

  ACTUAL BEHAVIOR: Both monitors present a purple background at login,
  but the VGA monitor is quickly disabled at login.

  When I had a problem with these video sources under Windows the Intel
  team provided me a "Switchable Graphics" BIOS module.  It resolved the
  issue there.  My BIOS settings define "Switchable Graphics" as the
  Primary Display.

  When I set the BIOS to use the ast2500 as the only display source the
  system works as intended.  I mention this to confirm the ast2500 and
  kernel can display video even if the ast2500 won't display video
  alongside the i915.

  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

  xorg:
Installed: 1:7.7+19ubuntu7.1
Candidate: 1:7.7+19ubuntu7.1
Version table:
   *** 1:7.7+19ubuntu7.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:7.7+19ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  test@test:~$ modinfo ast | grep -version
  filename:   
/lib/modules/5.3.0-46-generic/kernel/drivers/gpu/drm/ast/ast.ko
  license:GPL and additional rights
  description:AST
  author: Dave Airlie
  firmware:   ast_dp501_fw.bin
  alias:  pci:v1A03d2010sv*sd*bc03sc*i*
  alias:  pci:v1A03d2000sv*sd*bc03sc*i*
  depends:drm,drm_kms_helper,drm_vram_helper,i2c-algo-bit
  retpoline:  Y
  intree: Y
  name:   ast
  vermagic:   5.3.0-46-generic SMP mod_unload 
  signat: PKCS#7
  signer: 
  sig_key:
  sig_hashalgo:   md4
  parm:   modeset:Disable/Enable modesetting (int)

  test@test:~$ xrandr --listproviders
  Providers: number : 2
  Provider 0: id: 0x6e cap: 0x9, Source Output, Sink Offload crtcs: 3 outputs: 
2 associated providers: 0 name:modesetting
  Provider 1: id: 0x41 cap: 0x0 crtcs: 1 outputs: 1 associated providers: 0 
name:modesetting

  Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
  DP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 496mm x 292mm
 1920x1080 60.00*+
 1680x1050 59.95  
 1600x900  60.00  
 1280x1024 60.02  
 1440x900  59.89  
 1280x800  59.81  
 1280x720  60.00  
 1024x768  60.00  
 800x600   60.32  
 640x480   59.94  
 720x400   70.08  
  HDMI-1 disconnected (normal left inverted right x axis y axis)

  test@test:~$ sudo lshw -C video
  [sudo] password for test: 
*-display 
 description: VGA compatible controller
 product: Intel Corporation
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 02
 width: 64 bits
 clock: 33MHz
 capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 resources: irq:152 memory:9000-90ff memory:8000-8fff 
ioport:6000(size=64) memory:c-d
*-display
 description: VGA compatible controller
 product: ASPEED Graphics Family
 vendor: ASPEED Technology, Inc.
 physical id: 0
 bus info: pci@:04:00.0
 version: 41
 width: 32 bits
 clock: 33MHz
 capabilities: pm msi vga_controller cap_list
 configuration: driver=ast latency=0
 resources: irq:18 

[Touch-packages] [Bug 1871261] Re: package ufw 0.36-6 failed to install/upgrade: end of file on stdin at conffile prompt

[Edward Savage]

All good, thanks Jamie.

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

Title:
  package ufw 0.36-6 failed to install/upgrade: end of file on stdin at
  conffile prompt

Status in ufw package in Ubuntu:
  Invalid

Bug description:
  No action on my part resulted in a report problem dialog.  I have
  never modified the ufw configuration through the life of this install,
  which has come from 18.04 thru 19.04 and 19.10 to arrive at 20.04.
  Guessing someone made a typo in packaging.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: ufw 0.36-6
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu24
  AptOrdering:
   ufw:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Apr  7 06:45:08 2020
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2017-04-14 (1088 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-is-python2, 2.7.17-3
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.1
  SourcePackage: ufw
  Title: package ufw 0.36-6 failed to install/upgrade: end of file on stdin at 
conffile prompt
  UpgradeStatus: Upgraded to focal on 2020-04-06 (0 days ago)
  mtime.conffile..etc.default.ufw: 2019-07-28T20:35:23.745568

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

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

[Touch-packages] [Bug 1871414] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1871414

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  [Gigabyte GA-AB350M-D3H] Pulseaudio repeatedly detects a headphone
  being plugged in when nothing is plugged in

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

Bug description:
  Software details:
  Distro: Kubuntu 20.04 Beta
  Kernel: 5.4.0-21-generic
  alsa-base version 1.0.25+dfsg-0ubuntu5
  alsa-utils version 1.2.2-1ubuntu1
  pulseaudio version 1:13.99.1-1ubuntu1

  Hardware details:
  Motherboard: Gigabyte GA-AB350M-D3H
  Audio Codec: Realtek ALC887
  GPU: Nvidia RTX 2060 Super (with the audio output disabled in PulseAudio)

  Regarding the issue:
  Every time I start an audio stream (regardless of the application), I can 
hear interruptions in the sound and when opening alsamixer I can also see the 
interface kind of flickering for a few milliseconds.
  After running pulseaudio with logging enabled for a few seconds (while 
playing music), this pattern can be seen:

  [pulseaudio] sink.c: alsa_output.pci-_0a_00.3.analog-stereo: state: IDLE 
-> RUNNING
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] 

[Touch-packages] [Bug 1865499] Re: pulseaudio doesn't detect (new) USB headset

[Daniel van Vugt]

It looks like that fix is already released as an official update in
1.1.3-5ubuntu0.4 on 24 March 2020. If that didn't fix the problem here
then I might have linked to the wrong thing. Please update your system
and tell us if the problem still occurs.

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

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

Title:
  pulseaudio doesn't detect (new) USB headset

Status in alsa-lib package in Ubuntu:
  Incomplete

Bug description:
  When booting the system (Lenovo Thinkpad L480/L490), all connected USB
  headsets are recognized and can be used, and configured via
  pavucontrol.

  When hot-plugging the USB headset, either the speaker is recognized,
  or the microphone, rarely both. But when both are recognized, the
  microphone is always a "multichannel" device. When both the speaker
  and the "multichannel" microphone are recognized, only one can be used
  - either speaker or microphone. When selecting the speaker, the
  microphone is switched back to any other device available, them same
  goes for the microphone and the speaker - any other speaker is
  selected.

  A workaround is to plug in the USB headset and run "pkill -U $USER
  pulseaudio". Everything works fine until the next hot-plug (eg. a
  second headset).

  Running "lsb_release -a" gives   
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04
  Codename: bionic

  Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
  our users are affected by this bug, all running the same Ubuntu and
  package versions. I activated the proposed repository to check if any
  updates available fix the problem, but to no avail. I also switched
  kernels (from 4.15 to 5.5 mainline from
  https://wiki.ubuntu.com/Kernel/MainlineBuilds).

  I read bug #1325282
  (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
  and it sounds somewhat very familiar, but instead of "env={}" in
  /usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
  Removing "env=env" doesn't resolve the problem.

  Do you require additional information?

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

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

[Touch-packages] [Bug 1871458] Re: No display signal if NVIDIA driver and display scaling is active

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1870758, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1870758
   [nvidia] Display scaling results in monitor power save state

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

Title:
  No display signal if NVIDIA driver and display scaling is active

Status in xorg package in Ubuntu:
  New

Bug description:
  I recently installed Ubuntu 20.04 (20200402) with LVM encryption and 
automatic logon.
  So I enter my encryption password and after the motherboards boot logo it 
will login automatically to desktop. I also chose the additional drivers and so 
nvidia-driver-440.
  Everything seems to be OK until I select a scaling above 100% (e.g. 200%) in 
settings. Next reboot, I enter my encryption password. When the automatic logon 
process should happen, the monitor turns off and says that no display signal is 
available.

  Currently I was able to return to a working setup by pressing CTRL + ALT + 
F4, login and enter the following commands to remove nvidia-driver and use XORG 
instead:
  sudo apt purge nvidia-driver-440
  sudo apt autoremove
  sudo reboot

  I am pretty sure that the issue will occur again, if I choose NVIDIA
  driver again.

  Any thoughts?

  EDIT: On Ubuntu 19.04 I had a similar bug: If I started my PC and the
  monitor was not turned on, the monitor reported no signal available
  after turning it on. I was not able to see the boot-up field to enter
  my encryption password. Unfortunately I didn't test, if I were able to
  enter my password and logon anyway. Workaround was to turn the monitor
  on, before starting the PC.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 19:31:50 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd GP102 [GeForce GTX 1080 Ti] 
[1458:3762]
  InstallationDate: Installed on 2020-04-05 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Micro-Star International Co., Ltd. MS-7B45
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.80
  dmi.board.asset.tag: Default string
  dmi.board.name: Z370 GAMING PRO CARBON (MS-7B45)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.80:bd04/03/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B45:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ370GAMINGPROCARBON(MS-7B45):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7B45
  dmi.product.sku: Default string
  dmi.product.version: 2.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:

[Touch-packages] [Bug 1871451] Re: powerpc segfault on exponential of negative in python

[Jakub Kaczmarzyk]

Thank you. I have posted this as an issue on moby/qemu
https://github.com/moby/qemu/issues/10

** Bug watch added: github.com/moby/qemu/issues #10
   https://github.com/moby/qemu/issues/10

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

Title:
  powerpc segfault on exponential of negative in python

Status in cloud-images:
  New
Status in python3-defaults package in Ubuntu:
  New

Bug description:
  When calculating the exponential of a negative number in python 3.6
  with the Ubuntu 18.04 Docker image (ppcle64), I receive a segfault.

  ```
  python3 -c "import math; math.exp(-1)"
  qemu: uncaught target signal 11 (Segmentation fault) - core dumped
  Segmentation fault
  ```

  I am running this in Docker on macOS. Here are the steps to reproduce
  the error.

  ```
  docker run --rm -it --platform linux/ppc64le ubuntu:18.04
  apt-get update -qq && apt-get install -y -qq python3
  python3 -c "import math; print(math.exp(0))"  # 1.0
  python3 -c "import math; print(math.exp(-0))"  # 1.0
  python3 -c "import math; print(math.exp(1))"  # 2.718281828459045
  python3 -c "import math; print(math.exp(-1))"
  ```

  This error does not happen when using the debian:10 or alpine images.

  Here is the output of docker version on my machine:

  ```
  Client: Docker Engine - Community
   Version:   19.03.8
   API version:   1.40
   Go version:go1.12.17
   Git commit:afacb8b
   Built: Wed Mar 11 01:21:11 2020
   OS/Arch:   darwin/amd64
   Experimental:  true

  Server: Docker Engine - Community
   Engine:
    Version:  19.03.8
    API version:  1.40 (minimum version 1.12)
    Go version:   go1.12.17
    Git commit:   afacb8b
    Built:Wed Mar 11 01:29:16 2020
    OS/Arch:  linux/amd64
    Experimental: true
   containerd:
    Version:  v1.2.13
    GitCommit:7ad184331fa3e55e52b890ea95e65ba581ae3429
   runc:
    Version:  1.0.0-rc10
    GitCommit:dc9208a3303feef5b3839f4323d9beb36df0a9dd
   docker-init:
    Version:  0.18.0
    GitCommit:fec3683
  ```

  Cross-posted to StackOverflow:
  https://stackoverflow.com/questions/61084969/python-segfault-
  calculating-exponential-of-negative-ppc64le

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1871451/+subscriptions

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

[Touch-packages] [Bug 1871414] Re: Pulseaudio repeatedly detects a headphone being plugged in when nothing is plugged in

[Daniel van Vugt]

** Summary changed:

- Pulseaudio incorrectly detects a headphone being plugged in
+ Pulseaudio repeatedly detects a headphone being plugged in when nothing is 
plugged in

** Tags added: focal

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

** Summary changed:

- Pulseaudio repeatedly detects a headphone being plugged in when nothing is 
plugged in
+ [Gigabyte GA-AB350M-D3H] Pulseaudio repeatedly detects a headphone being 
plugged in when nothing is plugged in

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

Title:
  [Gigabyte GA-AB350M-D3H] Pulseaudio repeatedly detects a headphone
  being plugged in when nothing is plugged in

Status in linux package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Software details:
  Distro: Kubuntu 20.04 Beta
  Kernel: 5.4.0-21-generic
  alsa-base version 1.0.25+dfsg-0ubuntu5
  alsa-utils version 1.2.2-1ubuntu1
  pulseaudio version 1:13.99.1-1ubuntu1

  Hardware details:
  Motherboard: Gigabyte GA-AB350M-D3H
  Audio Codec: Realtek ALC887
  GPU: Nvidia RTX 2060 Super (with the audio output disabled in PulseAudio)

  Regarding the issue:
  Every time I start an audio stream (regardless of the application), I can 
hear interruptions in the sound and when opening alsamixer I can also see the 
interface kind of flickering for a few milliseconds.
  After running pulseaudio with logging enabled for a few seconds (while 
playing music), this pattern can be seen:

  [pulseaudio] sink.c: alsa_output.pci-_0a_00.3.analog-stereo: state: IDLE 
-> RUNNING
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone 

[Touch-packages] [Bug 1871475] Re: Black screen after screen lock

[Daniel van Vugt]

Please try logging into "Ubuntu on Wayland" from the login screen and
tell us if that avoids the problem.

** Tags added: amdgpu

** Package changed: xorg (Ubuntu) => mutter (Ubuntu)

** Summary changed:

- Black screen after screen lock
+ [amdgpu] Black screen after screen lock

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

Title:
  [amdgpu] Black screen after screen lock

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When I lock the screen with "Windows" + "L" key combination the screen
  gets locked, but I expect it to stay on and be locked. In Ubuntu
  20.04. when I do it the screen gets locked but get immediately black a
  sit would be in standby. The screen should stay on and show locked
  screen.

  This black screen happens often, but sometimes not.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 20:51:27 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Picasso [17aa:5125]
  InstallationDate: Installed on 2020-04-02 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  MachineType: LENOVO 20NKS01Y00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=024c6306-92b0-4cf4-88de-71e1f0671318 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/28/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R12ET46W(1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NKS01Y00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR12ET46W(1.16):bd10/28/2019:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T495
  dmi.product.name: 20NKS01Y00
  dmi.product.sku: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495
  dmi.product.version: ThinkPad T495
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1871403] Re: wifi won't connect, but kernel 5.6 fixes it

[Daniel van Vugt]

** Summary changed:

- wifi won't connect
+ wifi won't connect, but kernel 5.6 fixes it

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

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

Title:
  wifi won't connect, but kernel 5.6 fixes it

Status in linux package in Ubuntu:
  New

Bug description:
  My wifi adapter won't connect under Kubuntu.  It works fine when I
  boot the same laptop under Ubuntu 18.04, but when I boot under Kubuntu
  20.04, I get "Configuring Interface" followed by "Wireless interface
  (wlp1s0)  The wifi network could not be found."

  It worked fine up until today.  Ethernet connection works fine.

  I tried restarting NetworkManager.service in systemctl and I get this:

  NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Tue 2020-04-07 10:08:47 EDT; 1min 3s ago
 Docs: man:NetworkManager(8)
 Main PID: 4231 (NetworkManager)
Tasks: 3 (limit: 16627)
   Memory: 5.0M
   CGroup: /system.slice/NetworkManager.service
   └─4231 /usr/sbin/NetworkManager --no-daemon

  Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.1829] 
device (wlp1s0): supplicant interface state: scanning -> authenticating
  Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.1830] 
device (p2p-dev-wlp1s0): supplicant management interface state: scanning -> 
authenticating
  Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.2268] 
device (wlp1s0): supplicant interface state: authenticating -> disconnected
  Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.2269] 
device (p2p-dev-wlp1s0): supplicant management interface state: authenticating 
-> disconnected
  Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8910] 
device (wlp1s0): Activation: (wifi) association took too long, failing 
activation
  Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8911] 
device (wlp1s0): state change: config -> failed (reason 'ssid-not-found', 
sys-iface-state: 'managed')
  Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8933] 
device (wlp1s0): Activation: failed for connection 'BoulderNET'
  Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8939] 
device (wlp1s0): state change: failed -> disconnected (reason 'none', 
sys-iface-state: 'managed')
  Apr 07 10:09:34 ZenBook NetworkManager[4231]:   [1586268574.2285] 
device (wlp1s0): supplicant interface state: disconnected -> inactive
  Apr 07 10:09:34 ZenBook NetworkManager[4231]:   [1586268574.2287] 
device (p2p-dev-wlp1s0): supplicant management interface state: disconnected -> 
inactive
  dennis@ZenBook:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  Uname: Linux 5.6.1-050601-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Tue Apr  7 10:14:23 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Picasso [1043:1b71]
  InstallationDate: Installed on 2020-03-06 (31 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX434DA_UM433DA
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.1-050601-generic 
root=UUID=f2ef7f4c-875c-4861-a849-e5ebf6d646fd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX434DA_UM433DA.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX434DA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX434DA_UM433DA.302:bd09/05/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX434DA_UM433DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX434DA_UM433DA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  

[Touch-packages] [Bug 1871148] Re: services start before apparmor profiles are loaded

[Seth Arnold]

Jamie, what happens on systems without snap installed? Will systemd
start the apparmor service?

How much later does this push the already-too-late apparmor service?

Requiring a potentially new thing may push the apparmor unit further
behind, allowing even more services to start before profiles have been
loaded.

I have to think the better approach may have been to introduce something
like apparmor@.service and configure an apparmor@snapd.service that will
load profiles before snapd is started -- at least if snap is not itself
loading profiles before launching programs.

Thanks

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

Title:
  services start before apparmor profiles are loaded

Status in AppArmor:
  Invalid
Status in apparmor package in Ubuntu:
  Fix Released
Status in zsys package in Ubuntu:
  Invalid
Status in apparmor source package in Focal:
  Fix Released
Status in zsys source package in Focal:
  Invalid

Bug description:
  Per discussion with Zyga in #snapd on Freenode, I have hit a race
  condition where services are being started by the system before
  apparmor has been started. I have a complete log of my system showing
  the effect somewhere within at https://paste.ubuntu.com/p/Jyx6gfFc3q/.
  Restarting apparmor using `sudo systemctl restart apparmor` is enough
  to bring installed snaps back to full functionality.

  Previously, when running any snap I would receive the following in the
  terminal:

  ---
  cannot change profile for the next exec call: No such file or directory
  snap-update-ns failed with code 1: File exists
  ---

  Updated to add for Jamie:

  $ snap version
  snap2.44.2+20.04
  snapd   2.44.2+20.04
  series  16
  ubuntu  20.04
  kernel  5.4.0-21-generic

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

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

[Touch-packages] [Bug 1871422] Re: Unable to get 4K 60Hz on nvidia GT 1030 on AMD Ryzen 5 2600

[Daniel van Vugt]

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

Thanks for the bug report. This does indeed look like a duplicate of bug
1870637:

[10.855] (--) modeset(0): HDMI max TMDS frequency 30KHz
[10.855] (II) modeset(0): Not using default mode "3840x2160" (bad mode 
clock/interlace/doublescan)
[10.855] (II) modeset(0): Not using default mode "2560x1440" (bad mode 
clock/interlace/doublescan)
[10.855] (II) modeset(0): Printing probed modes for output HDMI-1

** This bug has been marked a duplicate of bug 1870637
   Nvidia+modeset: Can't set 4K@60Hz: HDMI max TMDS frequency 30KHz

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

Title:
  Unable to get 4K 60Hz on nvidia GT 1030 on AMD Ryzen 5 2600

Status in xorg package in Ubuntu:
  New

Bug description:
  This is a duplicate of https://bugs.launchpad.net/ubuntu/+source/xorg-
  server/+bug/1870637

  The only difference is that i switched from a Ryzen 2200G CPU to a Ryzen 5 
2600.
  Still running a zotac nvidia GT1030 graphics card.
  I was not sure how to get the system log files to the older thread, my 
apologies for the inconvenience.

  I was able to set 4K 60 @200%, but after reboot i got a crash notice and i'm 
back to fullHD.
  If this would have fixed the issue i would have ordered a 3700X for my 
windows system and would have kept the ryzen 5 2600 for my ubuntu system, but 
since this is not the case, i'll be putting the ryzen 2200G back into my ubuntu 
system.

  Before i do so; I'll try to enable wayland, as asked, but if i
  remember correctly i read on a post on omgunbuntu that wayland is
  currently disabled on the beta? Anyway, i'll have a look and report
  back

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..29.00.0: Error: [Errno 21] Is een map: 
'/proc/driver/nvidia/gpus/:29:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu1)
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 17:05:52 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.64, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] 
[19da:2476]
  InstallationDate: Installed on 2020-04-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Micro-Star International Co., Ltd. MS-7B84
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=44827b31-356c-437b-9865-80f973861754 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.D0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M PRO-M2 (MS-7B84)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.D0:bd12/03/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B84:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-M2(MS-7B84):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B84
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: 

[Touch-packages] [Bug 1871329] Re: No "Select Audio Device" panel when plugging headphones, and no sound output to headphones

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  No "Select Audio Device" panel when plugging headphones, and no sound
  output to headphones

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:

  
  Summary
  ===

  Internal speakers work as expected, but when plugging headphones
  through the 3.5mm jack, the "Select Audio Device" panel doesn't show
  up (it normally shows up to allow user to select what kind of device
  has been plugged in, be it headphones, microphone or headset). In the
  Sound Settings, the Output Device automatically switches to
  "Headphones - sof-hda-dsp", but no sound can be heard even though the
  vumeter in the Sound Settings moves!

  Steps to reproduce
  ==

  1. Install focal beta
  2. Make sure the sound works as expected using the internal speakers and an 
audio file or Youtube
  3. Plug headphones in jack 3.5mm interface

  Expected Results
  

  - In Sound Settings, the headphones are automatically selected as output 
device
  - In Sound Settings, the vumeter under the Output Device moves according to 
the sound
  - Sound can be heard through the headphones

  
  Actual results
  ==

  - In Sound Settings, the headphones are automatically selected as output 
device (OK)
  - In Sound Settings, the vumeter under the Output Device moves according to 
the sound (OK)
  - No sound can be heard (Not OK)

  Attached are output of `pactl info` and `pactl list` before and after
  plugging headphones, while playing a tune on Bandcamp in Firefox.

  
  Additional Info
  ===

  Ubuntu: 20.04 beta image
  Certified device: 
  system-manufacturer: Dell Inc.
  system-product-name: Vostro 5590
  bios-version: 1.1.0
  CPU: Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:9b41] (rev 02)
  01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:1d13] (rev a1)
  kernel-version: 5.4.0-21-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1768 F pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1768 F...m pulseaudio
   /dev/snd/pcmC0D6c:   pieq   1768 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 16:33:27 2020
  InstallationDate: Installed on 2020-04-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd07/18/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5590
  dmi.product.sku: 095A
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1871391] Re: sound output dont change

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1866194, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1866194
   External audio device shows up in the sound output options but the sound 
keeps being emitted from the internal laptop speaker, or none at all.

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

Title:
  sound output dont change

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Even with right output selected, the sound plays on the notebook
  output.

  I've tried restart the system, it dont change.  If i test the sound on
  the configs, i hear the sound right (on my phones).  But on spotify \
  chrome, the sound plays on notebook output.

  https://imgur.com/a/9SMeTYA

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  otavio154337 F pulseaudio
   /dev/snd/controlC0:  otavio154337 F pulseaudio
   /dev/snd/pcmC0D0c:   otavio154337 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 14:26:53 2020
  InstallationDate: Installed on 2020-02-27 (40 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-04-06 (0 days ago)
  dmi.bios.date: 11/08/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9VCN15WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R33126 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion Y530-15ICH-1060
  dmi.modalias: 
dmi:bvnLENOVO:bvr9VCN15WW:bd11/08/2018:svnLENOVO:pn81M7:pvrLenovoLegionY530-15ICH-1060:rvnLENOVO:rnLNVNB161216:rvrSDK0R33126WIN:cvnLENOVO:ct10:cvrLenovoLegionY530-15ICH-1060:
  dmi.product.family: Legion Y530-15ICH-1060
  dmi.product.name: 81M7
  dmi.product.sku: LENOVO_MT_81M7_BU_idea_FM_Legion Y530-15ICH-1060
  dmi.product.version: Lenovo Legion Y530-15ICH-1060
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1871497] Re: Ubuntu accepts headset without asking me what it was when I plugged my Microsoft headset into my PC.

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1871329, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1871329
   No "Select Audio Device" panel when plugging headphones, and no sound output 
to headphones

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

Title:
  Ubuntu accepts headset without asking me what it was when I plugged my
  Microsoft headset into my PC.

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu registers the USB Headset as a speaker too, as one an see when
  the volume button is pushed and the volume is modified.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.4
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  seija  3751 F pulseaudio
   /dev/snd/pcmC1D0p:   seija  3751 F...m pulseaudio
   /dev/snd/controlC0:  gdm1130 F pulseaudio
seija  3751 F pulseaudio
  Date: Tue Apr  7 17:53:12 2020
  InstallationDate: Installed on 2020-04-04 (3 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1843982] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user()

[Daniel van Vugt]

Tracking in:

https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781
https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f
https://errors.ubuntu.com/problem/3945cd9cdcec914cab9a3220d05e969696c7

** Description changed:

  https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f
+ https://errors.ubuntu.com/problem/3945cd9cdcec914cab9a3220d05e969696c7
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 10:29:16 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-05-24 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () 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
   ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

** Description changed:

+ https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781
  https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f
  https://errors.ubuntu.com/problem/3945cd9cdcec914cab9a3220d05e969696c7
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 10:29:16 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-05-24 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () 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
   ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

Title:
  Various programs crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from update_user()

Status in accountsservice:
  New
Status in accountsservice package in Ubuntu:
  Triaged
Status in accountsservice package in Debian:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781
  https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f
  https://errors.ubuntu.com/problem/3945cd9cdcec914cab9a3220d05e969696c7

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 10:29:16 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-05-24 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () 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
   ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0
   

[Touch-packages] [Bug 1871414] Re: Pulseaudio incorrectly detects a headphone being plugged in

[Yosep Perez]

The attachments in the comments (not in the bug itself) where taken
using the latest stable kernel 5.6.2, this is because I wanted to see if
the issue was fixed in the meantime. But the behavior is exactly the
same, sadly

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

Title:
  Pulseaudio incorrectly detects a headphone being plugged in

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Software details:
  Distro: Kubuntu 20.04 Beta
  Kernel: 5.4.0-21-generic
  alsa-base version 1.0.25+dfsg-0ubuntu5
  alsa-utils version 1.2.2-1ubuntu1
  pulseaudio version 1:13.99.1-1ubuntu1

  Hardware details:
  Motherboard: Gigabyte GA-AB350M-D3H
  Audio Codec: Realtek ALC887
  GPU: Nvidia RTX 2060 Super (with the audio output disabled in PulseAudio)

  Regarding the issue:
  Every time I start an audio stream (regardless of the application), I can 
hear interruptions in the sound and when opening alsamixer I can also see the 
interface kind of flickering for a few milliseconds.
  After running pulseaudio with logging enabled for a few seconds (while 
playing music), this pattern can be seen:

  [pulseaudio] sink.c: alsa_output.pci-_0a_00.3.analog-stereo: state: IDLE 
-> RUNNING
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes

  Note: I've no headphones attached ! Only the line out is connected to
  a 2.1 Speaker

[Touch-packages] [Bug 1871414] Re: Pulseaudio incorrectly detects a headphone being plugged in

[Yosep Perez]

After some debugging, I ended up doing strace on the pulseaudio server
to see if I could spot the issue and I think this is the closest I got
(in the attachment there's a bit more info):

write(5, "W", 1)= 1
read(16, "\0\0\0\0\1\0\0\0(\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0Front He"..., 72) = 72
ioctl(16, SNDRV_CTL_IOCTL_ELEM_READ, 0x7fff1d114f40) = 0
write(5, "W", 1)= 1
write(19, "\1\0\0\0\0\0\0\0", 8)= 8
futex(0x561a8db98540, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, NULL, 
FUTEX_BITSET_MATCH_ANY) = 0
write(19, "\1\0\0\0\0\0\0\0", 8)= 8
futex(0x561a8db98540, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, NULL, 
FUTEX_BITSET_MATCH_ANY) = -1 EAGAIN (Resource temporarily unavailable)
write(19, "\1\0\0\0\0\0\0\0", 8)= 8
futex(0x561a8db98540, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, NULL, 
FUTEX_BITSET_MATCH_ANY) = 0
read(16, "\0\0\0\0\1\0\0\0\v\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0Headphon"..., 72) = 72
ioctl(16, SNDRV_CTL_IOCTL_ELEM_READ, 0x7fff1d114880) = 0
ioctl(16, SNDRV_CTL_IOCTL_ELEM_READ, 0x7fff1d114890) = 0
read(16, "\0\0\0\0\1\0\0\0\n\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0Headphon"..., 72) = 72
ioctl(16, SNDRV_CTL_IOCTL_ELEM_READ, 0x7fff1d114880) = 0
ioctl(16, SNDRV_CTL_IOCTL_ELEM_READ, 0x7fff1d114890) = 0
read(16, "\0\0\0\0\1\0\0\0\5\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0Surround"..., 72) = 72
ioctl(16, SNDRV_CTL_IOCTL_ELEM_READ, 0x7fff1d114880) = 0
ioctl(16, SNDRV_CTL_IOCTL_ELEM_READ, 0x7fff1d114890) = 0
read(16, "\0\0\0\0\1\0\0\0\10\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0Center P"..., 72) = 
72
ioctl(16, SNDRV_CTL_IOCTL_ELEM_READ, 0x7fff1d114880) = 0
ioctl(16, SNDRV_CTL_IOCTL_ELEM_READ, 0x7fff1d114890) = 0
read(16, "\0\0\0\0\1\0\0\0\t\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0LFE Play"..., 72) = 72
ioctl(16, SNDRV_CTL_IOCTL_ELEM_READ, 0x7fff1d114880) = 0
ioctl(16, SNDRV_CTL_IOCTL_ELEM_READ, 0x7fff1d114890) = 0
read(16, "\0\0\0\0\1\0\0\0\4\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0Surround"..., 72) = 72
ioctl(16, SNDRV_CTL_IOCTL_ELEM_READ, 0x7fff1d114880) = 0
ioctl(16, SNDRV_CTL_IOCTL_ELEM_READ, 0x7fff1d114890) = 0
read(16, "\0\0\0\0\1\0\0\0\6\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0Center P"..., 72) = 72
ioctl(16, SNDRV_CTL_IOCTL_ELEM_READ, 0x7fff1d114880) = 0
ioctl(16, SNDRV_CTL_IOCTL_ELEM_READ, 0x7fff1d114890) = 0
read(16, "\0\0\0\0\1\0\0\0\7\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0LFE Play"..., 72) = 72
ioctl(16, SNDRV_CTL_IOCTL_ELEM_READ, 0x7fff1d114880) = 0
ioctl(16, SNDRV_CTL_IOCTL_ELEM_READ, 0x7fff1d114890) = 0
read(16, 0x7fff1d115520, 72)= -1 EAGAIN (Resource temporarily 
unavailable)
read(4, "WW", 10)   = 2
write(5, "W", 1)= 1
write(5, "W", 1)= 1
read(4, "WW", 10)   = 2
write(46, "\1\0\0\0\0\0\0\0", 8)= 8

Note that the FD 16 is "16u CHR 116,16 0t0 20030 /dev/snd/controlC1",
basically the control interface of the card I really want to be
listening to: card 1; the other card (0) is the one in the video card
which I don't really care

** Attachment added: "lsof+strace.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871414/+attachment/5349096/+files/lsof+strace.tar.gz

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

Title:
  Pulseaudio incorrectly detects a headphone being plugged in

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Software details:
  Distro: Kubuntu 20.04 Beta
  Kernel: 5.4.0-21-generic
  alsa-base version 1.0.25+dfsg-0ubuntu5
  alsa-utils version 1.2.2-1ubuntu1
  pulseaudio version 1:13.99.1-1ubuntu1

  Hardware details:
  Motherboard: Gigabyte GA-AB350M-D3H
  Audio Codec: Realtek ALC887
  GPU: Nvidia RTX 2060 Super (with the audio output disabled in PulseAudio)

  Regarding the issue:
  Every time I start an audio stream (regardless of the application), I can 
hear interruptions in the sound and when opening alsamixer I can also see the 
interface kind of flickering for a few milliseconds.
  After running pulseaudio with logging enabled for a few seconds (while 
playing music), this pattern can be seen:

  [pulseaudio] sink.c: alsa_output.pci-_0a_00.3.analog-stereo: state: IDLE 
-> RUNNING
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] 

[Touch-packages] [Bug 1871414] Re: Pulseaudio incorrectly detects a headphone being plugged in

[Yosep Perez]

** Attachment added: "alsa-info.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871414/+attachment/5349075/+files/alsa-info.txt

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

Title:
  Pulseaudio incorrectly detects a headphone being plugged in

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Software details:
  Distro: Kubuntu 20.04 Beta
  Kernel: 5.4.0-21-generic
  alsa-base version 1.0.25+dfsg-0ubuntu5
  alsa-utils version 1.2.2-1ubuntu1
  pulseaudio version 1:13.99.1-1ubuntu1

  Hardware details:
  Motherboard: Gigabyte GA-AB350M-D3H
  Audio Codec: Realtek ALC887
  GPU: Nvidia RTX 2060 Super (with the audio output disabled in PulseAudio)

  Regarding the issue:
  Every time I start an audio stream (regardless of the application), I can 
hear interruptions in the sound and when opening alsamixer I can also see the 
interface kind of flickering for a few milliseconds.
  After running pulseaudio with logging enabled for a few seconds (while 
playing music), this pattern can be seen:

  [pulseaudio] sink.c: alsa_output.pci-_0a_00.3.analog-stereo: state: IDLE 
-> RUNNING
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes

  Note: I've no headphones attached ! Only the line out is connected to
  a 2.1 Speaker

  It seems basically the same bug as this: 

[Touch-packages] [Bug 1871381] Re: GStreamer dvdreadsrc linked with wrong libdvdread in 20.04 beta

[Brian Murray]

The libdvdread package was actually reverted to 6.0.2 so this should be
a non-issue.

libdvdread (6.1.0+really6.0.2-1) unstable; urgency=medium

  * Team upload
  * Revert to 6.0.2 due to an ABI break in 6.1.0 (Closes: #955367)

 -- Sebastian Ramacher   Fri, 03 Apr 2020 22:10:47
+0200

** Package changed: lsdvd (Ubuntu) => libdvdread (Ubuntu)

** Changed in: libdvdread (Ubuntu)
   Status: Triaged => Invalid

** No longer affects: gst-plugins-ugly-multiverse0.10 (Ubuntu)

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

Title:
  GStreamer dvdreadsrc linked with wrong libdvdread in 20.04 beta

Status in libdvdread package in Ubuntu:
  Invalid

Bug description:
  dvdreadsrc as well as lsdvd were built with libdvdread version 6.0.2,
  while version 6.1.0 included in the 20.04 beta.

  The problem is related to the latest changes of the ifo_handle_t struct 
contained on the libdvdread source file
  src/dvdread/ifo_types.h
  where the first structure filed dvd_file_t *file was removed in the version 
6.1.0

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

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

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

[Hui Wang]

@David,

Please upload the dmesg of -46 kernel.

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Any time now, the sound card was deactivated, and it appears as a
  "Dummy device". I searched many forums about it, but nothing works.
  I'll be grateful if a program exists that I could install for sound
  card recognition.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 20 16:13:53 2020
  InstallationDate: Installed on 2020-03-19 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_CL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.name: 054J60
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd08/08/2019:svnDellInc.:pnG33590:pvr:rvnDellInc.:rn054J60:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: GSeries
  dmi.product.name: G3 3590
  dmi.product.sku: 0949
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1871381] [NEW] GStreamer dvdreadsrc linked with wrong libdvdread in 20.04 beta

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

dvdreadsrc as well as lsdvd were built with libdvdread version 6.0.2,
while version 6.1.0 included in the 20.04 beta.

The problem is related to the latest changes of the ifo_handle_t struct 
contained on the libdvdread source file
src/dvdread/ifo_types.h
where the first structure filed dvd_file_t *file was removed in the version 
6.1.0

** Affects: gst-plugins-ugly-multiverse0.10 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: libdvdread (Ubuntu)
 Importance: High
 Status: Triaged


** Tags: bot-comment
-- 
GStreamer dvdreadsrc linked with wrong libdvdread in 20.04 beta
https://bugs.launchpad.net/bugs/1871381
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to libdvdread in Ubuntu.

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

[Touch-packages] [Bug 1871023] Autopkgtest regression report (json-glib/1.4.4-2ubuntu0.19.10.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted json-glib (1.4.4-2ubuntu0.19.10.1) for 
eoan have finished running.
The following regressions have been reported in tests triggered by the package:

libgdata/0.17.11-3build1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/eoan/update_excuses.html#json-glib

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  json_gvariant_deserialize can fail due to unrelated code setting errno

Status in json-glib package in Ubuntu:
  Fix Released
Status in json-glib source package in Bionic:
  Fix Committed
Status in json-glib source package in Eoan:
  Fix Committed
Status in json-glib source package in Focal:
  Fix Released

Bug description:
  [Impact]
  json_gvariant_deserialize can fail due to unrelated code setting errno, this 
is causing snapd-glib to not be able to decode responses from snapd. Fixed in 
https://gitlab.gnome.org/GNOME/json-glib/-/merge_requests/22

  [Test Case]
  1. Run GNOME Software from the command line
  2. Browse to postman

  Expected result:
  Errors are not shown on the command line

  Observed result:
  The following errors are shown on the command line:
  05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed
  05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed
  05:17:29:0877 Gs  not GsPlugin error g-io-error-quark:35: Invalid string 
value converting to GVariant
  05:17:29:0877 Gs  not handling error failed for action refine: Invalid string 
value converting to GVariant

  (These errors may not always occur, and is likely racy).

  [Regression Potential]
  Small risk of introducing other bugs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1871023/+subscriptions

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

[Touch-packages] [Bug 1796911] Re: libnss-systemd was denied talking to pid1

[Launchpad Bug Tracker]

This bug was fixed in the package apparmor - 2.13.3-7ubuntu4

---
apparmor (2.13.3-7ubuntu4) focal; urgency=medium

  * debian/apparmor.service: add /var/lib/snapd/apparmor/profiles to
RequiresMountsFor since Ubuntu's rc.apparmor.functions looks for it
(LP: #1871148)
  * libnss-systemd.patch: allow accessing the libnss-systemd VarLink sockets
and DBus APIs. Patch partially based on work by Simon Deziel.
(LP: #1796911, LP: #1869024)
  * upstream-mr-424-kerberos-dot-dirs.patch: abstractions/kerberosclient:
allow reading /etc/krb5.conf.d/
  * upstream-mr-442-gnome-user-themes.patch: gnome abstraction: allow reading
per-user themes from $XDG_DATA_HOME (Closes: #930031)
  * upstream-mr-443-ecryptfs-dirs.patch: abstractions/base: allow read access
to top-level ecryptfs directories (LP: #1848919)
  * upstream-mr-445-uuidd-request.patch: abstractions/base: allow read access
to /run/uuidd/request
  * upstream-mr-464-Mesa_i915_perf_interface.patch: let Mesa check if the
kernel supports the i915 perf interface. Patch from Debian

 -- Jamie Strandboge   Mon, 06 Apr 2020 17:47:20 +

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

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

Title:
  libnss-systemd was denied talking to pid1

Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  cosmic
  apparmor 2.12-4ubuntu8
  kernel 4.18.0-8-generic #9-Ubuntu 

  I'm getting these audit messages in dmesg showing apparmor denied errors:
  [   68.649187] audit: type=1107 audit(1539094926.655:32): pid=605 uid=105 
auid=4294967295 ses=4294967295 subj==unconfined msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/systemd1" 
interface="org.freedesktop.systemd1.Manager" member="GetDynamicUsers" 
mask="send" name="org.freedesktop.systemd1" pid=1091 label="/usr/sbin/named" 
peer_pid=1 peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=105 hostname=? addr=? 
terminal=?'
  [  161.059989] audit: type=1107 audit(1539095018.957:33): pid=605 uid=105 
auid=4294967295 ses=4294967295 subj==unconfined msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/systemd1" 
interface="org.freedesktop.systemd1.Manager" member="GetDynamicUsers" 
mask="send" name="org.freedesktop.systemd1" pid=1191 label="/usr/sbin/named" 
peer_pid=1 peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=105 hostname=? addr=? 
terminal=?'
  [  437.582034] audit: type=1107 audit(1539095295.553:34): pid=605 uid=105 
auid=4294967295 ses=4294967295 subj==unconfined msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/systemd1" 
interface="org.freedesktop.systemd1.Manager" member="GetDynamicUsers" 
mask="send" name="org.freedesktop.systemd1" pid=1534 label="/usr/sbin/named" 
peer_pid=1 peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=105 hostname=? addr=? 
terminal=?'
  [  468.184231] audit: type=1107 audit(1539095326.159:35): pid=605 uid=105 
auid=4294967295 ses=4294967295 subj==unconfined msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/systemd1" 
interface="org.freedesktop.systemd1.Manager" member="GetDynamicUsers" 
mask="send" name="org.freedesktop.systemd1" pid=1577 label="/usr/sbin/named" 
peer_pid=1 peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=105 hostname=? addr=? 
terminal=?'

  I pinged #ubuntu-hardened, and xnox had these comments:
   ha
   ahasenack, libnss-systemd was denied talking to pid1
   to query dynamicusers i think
   so i think something somehwere need adjustemnt to allow libnss-systemd 
to talk to pid1 and call GetDynamicUsers
   LookupDynamicUserByName LookupDynamicUserByUID GetDynamicUsers
   as well

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

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

[Touch-packages] [Bug 1848919] Re: [snap] Permission denied on Private encrypted folder

[Launchpad Bug Tracker]

This bug was fixed in the package apparmor - 2.13.3-7ubuntu4

---
apparmor (2.13.3-7ubuntu4) focal; urgency=medium

  * debian/apparmor.service: add /var/lib/snapd/apparmor/profiles to
RequiresMountsFor since Ubuntu's rc.apparmor.functions looks for it
(LP: #1871148)
  * libnss-systemd.patch: allow accessing the libnss-systemd VarLink sockets
and DBus APIs. Patch partially based on work by Simon Deziel.
(LP: #1796911, LP: #1869024)
  * upstream-mr-424-kerberos-dot-dirs.patch: abstractions/kerberosclient:
allow reading /etc/krb5.conf.d/
  * upstream-mr-442-gnome-user-themes.patch: gnome abstraction: allow reading
per-user themes from $XDG_DATA_HOME (Closes: #930031)
  * upstream-mr-443-ecryptfs-dirs.patch: abstractions/base: allow read access
to top-level ecryptfs directories (LP: #1848919)
  * upstream-mr-445-uuidd-request.patch: abstractions/base: allow read access
to /run/uuidd/request
  * upstream-mr-464-Mesa_i915_perf_interface.patch: let Mesa check if the
kernel supports the i915 perf interface. Patch from Debian

 -- Jamie Strandboge   Mon, 06 Apr 2020 17:47:20 +

** Changed in: apparmor (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  [snap] Permission denied on Private encrypted folder

Status in AppArmor:
  Fix Released
Status in snapd:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in chromium-browser package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Fix Released

Bug description:
  When accessing the Private (/home/username/Private, Encrypted
  Directory) folder (e.g. via "Link save as...") it shows "Could not
  read contents of Private, Error opening directory ...: Permission
  denied"

  Package: chromium-browser
  Version: 77.0.3865.120-0ubuntu1~snap1

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

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

[Touch-packages] [Bug 1871148] Re: services start before apparmor profiles are loaded

[Launchpad Bug Tracker]

This bug was fixed in the package apparmor - 2.13.3-7ubuntu4

---
apparmor (2.13.3-7ubuntu4) focal; urgency=medium

  * debian/apparmor.service: add /var/lib/snapd/apparmor/profiles to
RequiresMountsFor since Ubuntu's rc.apparmor.functions looks for it
(LP: #1871148)
  * libnss-systemd.patch: allow accessing the libnss-systemd VarLink sockets
and DBus APIs. Patch partially based on work by Simon Deziel.
(LP: #1796911, LP: #1869024)
  * upstream-mr-424-kerberos-dot-dirs.patch: abstractions/kerberosclient:
allow reading /etc/krb5.conf.d/
  * upstream-mr-442-gnome-user-themes.patch: gnome abstraction: allow reading
per-user themes from $XDG_DATA_HOME (Closes: #930031)
  * upstream-mr-443-ecryptfs-dirs.patch: abstractions/base: allow read access
to top-level ecryptfs directories (LP: #1848919)
  * upstream-mr-445-uuidd-request.patch: abstractions/base: allow read access
to /run/uuidd/request
  * upstream-mr-464-Mesa_i915_perf_interface.patch: let Mesa check if the
kernel supports the i915 perf interface. Patch from Debian

 -- Jamie Strandboge   Mon, 06 Apr 2020 17:47:20 +

** Changed in: apparmor (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  services start before apparmor profiles are loaded

Status in AppArmor:
  Invalid
Status in apparmor package in Ubuntu:
  Fix Released
Status in zsys package in Ubuntu:
  Invalid
Status in apparmor source package in Focal:
  Fix Released
Status in zsys source package in Focal:
  Invalid

Bug description:
  Per discussion with Zyga in #snapd on Freenode, I have hit a race
  condition where services are being started by the system before
  apparmor has been started. I have a complete log of my system showing
  the effect somewhere within at https://paste.ubuntu.com/p/Jyx6gfFc3q/.
  Restarting apparmor using `sudo systemctl restart apparmor` is enough
  to bring installed snaps back to full functionality.

  Previously, when running any snap I would receive the following in the
  terminal:

  ---
  cannot change profile for the next exec call: No such file or directory
  snap-update-ns failed with code 1: File exists
  ---

  Updated to add for Jamie:

  $ snap version
  snap2.44.2+20.04
  snapd   2.44.2+20.04
  series  16
  ubuntu  20.04
  kernel  5.4.0-21-generic

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

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

[Touch-packages] [Bug 1869024] Re: add support for DynamicUser feature of systemd

[Launchpad Bug Tracker]

This bug was fixed in the package apparmor - 2.13.3-7ubuntu4

---
apparmor (2.13.3-7ubuntu4) focal; urgency=medium

  * debian/apparmor.service: add /var/lib/snapd/apparmor/profiles to
RequiresMountsFor since Ubuntu's rc.apparmor.functions looks for it
(LP: #1871148)
  * libnss-systemd.patch: allow accessing the libnss-systemd VarLink sockets
and DBus APIs. Patch partially based on work by Simon Deziel.
(LP: #1796911, LP: #1869024)
  * upstream-mr-424-kerberos-dot-dirs.patch: abstractions/kerberosclient:
allow reading /etc/krb5.conf.d/
  * upstream-mr-442-gnome-user-themes.patch: gnome abstraction: allow reading
per-user themes from $XDG_DATA_HOME (Closes: #930031)
  * upstream-mr-443-ecryptfs-dirs.patch: abstractions/base: allow read access
to top-level ecryptfs directories (LP: #1848919)
  * upstream-mr-445-uuidd-request.patch: abstractions/base: allow read access
to /run/uuidd/request
  * upstream-mr-464-Mesa_i915_perf_interface.patch: let Mesa check if the
kernel supports the i915 perf interface. Patch from Debian

 -- Jamie Strandboge   Mon, 06 Apr 2020 17:47:20 +

** Changed in: apparmor (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  add support for DynamicUser feature of systemd

Status in snapd:
  In Progress
Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  systemd offers to create dynamic (and semi-stable) users for services.
  This causes many services using Apparmor profiles to trigger those
  denials (even when they don't use the DynamicUser feature):

  audit: type=1107 audit(1585076282.591:30): pid=621 uid=103
  auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/systemd1"
  interface="org.freedesktop.systemd1.Manager" member="GetDynamicUsers"
  mask="send" name="org.freedesktop.systemd1" pid=709
  label="/usr/sbin/squid" peer_pid=1 peer_label="unconfined"

  And more recently with systemd 245 this also get shown:

  audit: type=1400 audit(1585139000.628:39): apparmor="DENIED"
  operation="open" profile="/usr/sbin/squid" name="/run/systemd/userdb/"
  pid=769 comm="squid" requested_mask="r" denied_mask="r" fsuid=0 ouid=0

  
  Additional information:
  # lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  # uname -a
  Linux foo.example.com 5.4.0-18-generic #22-Ubuntu SMP Sat Mar 7 18:13:06 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

  # apt-cache policy apparmor squid
  apparmor:
Installed: 2.13.3-7ubuntu2
Candidate: 2.13.3-7ubuntu2
Version table:
   *** 2.13.3-7ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  squid:
Installed: 4.10-1ubuntu1
Candidate: 4.10-1ubuntu1
Version table:
   *** 4.10-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1871451] Re: powerpc segfault on exponential of negative in python

[Daniel Axtens]

Hi,

I tested this on a real ppc64le machine:

root@1325f5985861:/#  python3 -c "import math; print(math.exp(-1))"
0.36787944117144233
root@1325f5985861:/# uname -a
Linux 1325f5985861 5.4.0-21-generic #25+lp1866909v202004031128-Ubuntu SMP Fri 
Apr 3 18:38:30 UTC 202 ppc64le ppc64le ppc64le GNU/Linux


It looks like it's a qemu bug.

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

Title:
  powerpc segfault on exponential of negative in python

Status in cloud-images:
  New
Status in python3-defaults package in Ubuntu:
  New

Bug description:
  When calculating the exponential of a negative number in python 3.6
  with the Ubuntu 18.04 Docker image (ppcle64), I receive a segfault.

  ```
  python3 -c "import math; math.exp(-1)"
  qemu: uncaught target signal 11 (Segmentation fault) - core dumped
  Segmentation fault
  ```

  I am running this in Docker on macOS. Here are the steps to reproduce
  the error.

  ```
  docker run --rm -it --platform linux/ppc64le ubuntu:18.04
  apt-get update -qq && apt-get install -y -qq python3
  python3 -c "import math; print(math.exp(0))"  # 1.0
  python3 -c "import math; print(math.exp(-0))"  # 1.0
  python3 -c "import math; print(math.exp(1))"  # 2.718281828459045
  python3 -c "import math; print(math.exp(-1))"
  ```

  This error does not happen when using the debian:10 or alpine images.

  Here is the output of docker version on my machine:

  ```
  Client: Docker Engine - Community
   Version:   19.03.8
   API version:   1.40
   Go version:go1.12.17
   Git commit:afacb8b
   Built: Wed Mar 11 01:21:11 2020
   OS/Arch:   darwin/amd64
   Experimental:  true

  Server: Docker Engine - Community
   Engine:
    Version:  19.03.8
    API version:  1.40 (minimum version 1.12)
    Go version:   go1.12.17
    Git commit:   afacb8b
    Built:Wed Mar 11 01:29:16 2020
    OS/Arch:  linux/amd64
    Experimental: true
   containerd:
    Version:  v1.2.13
    GitCommit:7ad184331fa3e55e52b890ea95e65ba581ae3429
   runc:
    Version:  1.0.0-rc10
    GitCommit:dc9208a3303feef5b3839f4323d9beb36df0a9dd
   docker-init:
    Version:  0.18.0
    GitCommit:fec3683
  ```

  Cross-posted to StackOverflow:
  https://stackoverflow.com/questions/61084969/python-segfault-
  calculating-exponential-of-negative-ppc64le

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1871451/+subscriptions

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

[Touch-packages] [Bug 1870747] Re: ibus-ui-gtk3 crashed with SIGABRT in raise()

[Gunnar Hjalmarsson]

@Sebastien: Takao Fujiwara provided some hints about this and other
similar crash reports at the upstream issue I submitted. I'm thinking
that this may be something to look into post-release.

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

Title:
  ibus-ui-gtk3 crashed with SIGABRT in raise()

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 13:27:38 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   ?? () 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
   ?? ()
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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

[Touch-packages] [Bug 1871497] Re: Ubuntu accepts headset without asking me what it was when I plugged my Microsoft headset into my PC.

[Seija Kijin]

** Attachment added: "Settings screenshot"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871497/+attachment/5349040/+files/Screenshot%20from%202020-04-07%2017-57-03.png

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

Title:
  Ubuntu accepts headset without asking me what it was when I plugged my
  Microsoft headset into my PC.

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu registers the USB Headset as a speaker too, as one an see when
  the volume button is pushed and the volume is modified.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.4
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  seija  3751 F pulseaudio
   /dev/snd/pcmC1D0p:   seija  3751 F...m pulseaudio
   /dev/snd/controlC0:  gdm1130 F pulseaudio
seija  3751 F pulseaudio
  Date: Tue Apr  7 17:53:12 2020
  InstallationDate: Installed on 2020-04-04 (3 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1871497] [NEW] Ubuntu accepts headset without asking me what it was when I plugged my Microsoft headset into my PC.

[Seija Kijin]

Public bug reported:

Ubuntu registers the USB Headset as a speaker too, as one an see when
the volume button is pushed and the volume is modified.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7.4
ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-46-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  seija  3751 F pulseaudio
 /dev/snd/pcmC1D0p:   seija  3751 F...m pulseaudio
 /dev/snd/controlC0:  gdm1130 F pulseaudio
  seija  3751 F pulseaudio
Date: Tue Apr  7 17:53:12 2020
InstallationDate: Installed on 2020-04-04 (3 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/15/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.3
dmi.board.name: 09YTN7
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5570
dmi.product.sku: 0810
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug bionic

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

Title:
  Ubuntu accepts headset without asking me what it was when I plugged my
  Microsoft headset into my PC.

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu registers the USB Headset as a speaker too, as one an see when
  the volume button is pushed and the volume is modified.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.4
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  seija  3751 F pulseaudio
   /dev/snd/pcmC1D0p:   seija  3751 F...m pulseaudio
   /dev/snd/controlC0:  gdm1130 F pulseaudio
seija  3751 F pulseaudio
  Date: Tue Apr  7 17:53:12 2020
  InstallationDate: Installed on 2020-04-04 (3 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1871023] Please test proposed package

[Brian Murray]

Hello Robert, or anyone else affected,

Accepted json-glib into bionic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/json-
glib/1.4.2-3ubuntu0.18.04.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  json_gvariant_deserialize can fail due to unrelated code setting errno

Status in json-glib package in Ubuntu:
  Fix Released
Status in json-glib source package in Bionic:
  Fix Committed
Status in json-glib source package in Eoan:
  Fix Committed
Status in json-glib source package in Focal:
  Fix Released

Bug description:
  [Impact]
  json_gvariant_deserialize can fail due to unrelated code setting errno, this 
is causing snapd-glib to not be able to decode responses from snapd. Fixed in 
https://gitlab.gnome.org/GNOME/json-glib/-/merge_requests/22

  [Test Case]
  1. Run GNOME Software from the command line
  2. Browse to postman

  Expected result:
  Errors are not shown on the command line

  Observed result:
  The following errors are shown on the command line:
  05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed
  05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed
  05:17:29:0877 Gs  not GsPlugin error g-io-error-quark:35: Invalid string 
value converting to GVariant
  05:17:29:0877 Gs  not handling error failed for action refine: Invalid string 
value converting to GVariant

  (These errors may not always occur, and is likely racy).

  [Regression Potential]
  Small risk of introducing other bugs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1871023/+subscriptions

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

[Touch-packages] [Bug 1871023] Re: json_gvariant_deserialize can fail due to unrelated code setting errno

[Brian Murray]

Hello Robert, or anyone else affected,

Accepted json-glib into eoan-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/json-
glib/1.4.4-2ubuntu0.19.10.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
eoan to verification-done-eoan. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-eoan. In either case, without details of your testing we will not
be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: json-glib (Ubuntu Eoan)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-eoan

** Changed in: json-glib (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  json_gvariant_deserialize can fail due to unrelated code setting errno

Status in json-glib package in Ubuntu:
  Fix Released
Status in json-glib source package in Bionic:
  Fix Committed
Status in json-glib source package in Eoan:
  Fix Committed
Status in json-glib source package in Focal:
  Fix Released

Bug description:
  [Impact]
  json_gvariant_deserialize can fail due to unrelated code setting errno, this 
is causing snapd-glib to not be able to decode responses from snapd. Fixed in 
https://gitlab.gnome.org/GNOME/json-glib/-/merge_requests/22

  [Test Case]
  1. Run GNOME Software from the command line
  2. Browse to postman

  Expected result:
  Errors are not shown on the command line

  Observed result:
  The following errors are shown on the command line:
  05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed
  05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed
  05:17:29:0877 Gs  not GsPlugin error g-io-error-quark:35: Invalid string 
value converting to GVariant
  05:17:29:0877 Gs  not handling error failed for action refine: Invalid string 
value converting to GVariant

  (These errors may not always occur, and is likely racy).

  [Regression Potential]
  Small risk of introducing other bugs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1871023/+subscriptions

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

[Touch-packages] [Bug 1869996] Re: Hibernation can NOT work due to incorrect RESUME=

[Francis Ginther]

Removing linux-azure as this appears to be unrelated.

** No longer affects: linux-azure (Ubuntu)

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

Title:
  Hibernation can NOT work due to incorrect RESUME=

Status in initramfs-tools package in Ubuntu:
  Fix Released

Bug description:
  In Ubuntu 18.04 I have the below 4 lines, but in Ubuntu 20.04 (dev
  build) these lines are missing:

  --- /usr/share/initramfs-tools/init2020-04-01 01:15:20.533208700 +
  +++ /usr/share/initramfs-tools/init 2020-04-01 00:59:43.931655200 +
  @@ -163,6 +163,10 @@
  ;;
  resume=*)
  RESUME="${x#resume=}"
  +   case $RESUME in
  +   UUID=*)
  +RESUME="/dev/disk/by-uuid/${RESUME#UUID=}"
  +   esac
  ;;
  resume_offset=*)
  resume_offset="${x#resume_offset=}"

  As a result, hibernation can not work: the saved state in the swap
  partition is lost and no resume happens.

  The issue is: when I use the "resume=UUID=533b2cd9-31ac-449b-82ff-
  014f09ab0a9c" kernel parameter for hibernation, due to the missing
  lines, the variable 'resume' in a later place in "/usr/share
  /initramfs-tools/init" is set to "UUID=533b2cd9-31ac-449b-82ff-
  014f09ab0a9c" rather than "/dev/disk/by-uuid/533b2cd9-31ac-449b-82ff-
  014f09ab0a9c". Next, in /usr/share/initramfs-tools/scripts/local-
  premount/resume:

  DEV=$(readlink "$resume")
  DEV=/sys/class/block/${DEV##*/}/dev
  if [ -r "$DEV" ]; then
  read -r MAJMIN < "$DEV"
  fi
  if [ -z "$MAJMIN" ]; then
  exit 1
  fi

  Here the 'readlink' will fail, so $DEV is not pointing to a valid device, and 
then $MAJMIN is empty and
  we "exit 1", so no resume can happen!

  
  Not sure why the 4 lines are removed in Ubuntu 20.04...

  
  PS, this is my version info:

  root@localhost:~# dpkg-query -s initramfs-tools-core
  Package: initramfs-tools-core
  Status: install ok installed
  Priority: optional
  Section: utils
  Installed-Size: 271
  Maintainer: Ubuntu Developers 
  Architecture: all
  Multi-Arch: foreign
  Source: initramfs-tools
  Version: 0.136ubuntu1
  Replaces: initramfs-tools (<< 0.121~)
  Depends: busybox-initramfs (>= 1:1.30.1-4ubuntu5~), initramfs-tools-bin (= 
0.136ubuntu1), klibc-utils (>= 2.0.4-8~), cpio (>= 2.12), lz4, kmod, udev, 
coreutils (>= 8.24), logsave | e2fsprogs (<< 1.45.3-1~)
  Suggests: bash-completion
  Breaks: busybox-initramfs (<< 1:1.30.1-4ubuntu5~), initramfs-tools (<< 0.121~)
  Conffiles:
   /etc/initramfs-tools/initramfs.conf 4ec999d424d01b9ca685e65ba0f22a13
  Description: generic modular initramfs generator (core tools)
   This package contains the mkinitramfs program that can be used to
   create a bootable initramfs for a Linux kernel.  The initramfs should
   be loaded along with the kernel and is then responsible for mounting
   the root filesystem and starting the main init system.
  Original-Maintainer: Debian kernel team 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1869996/+subscriptions

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

[Touch-packages] [Bug 1870729] Re: DHCP Server regularly killed code=killed, status=6/ABRT

[Jamie Strandboge]

Now that there are no apparmor denials, this sounds like something for
the server team to take a look at. Can you file a new bug since this one
was used to address the apparmor denials? Thanks!

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

Title:
  DHCP Server regularly killed code=killed, status=6/ABRT

Status in isc-dhcp package in Ubuntu:
  Fix Released

Bug description:
  On Ubuntu 20.04 The idc-dhcp- server version is
  isc-dhcp-server:
Installed: (none)
Candidate: 4.4.1-2.1ubuntu3
Version table:
   4.4.1-2.1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  
  The DHCP server is being regularly killed, when searching google the  bug 
looks very similar to an older bug regarding accessing a lease file, that was 
fixed year ago. As a temporary fix in systemd I have enabled a restart every 
time the main process fails. The error got worse when i start to run a pair of 
dhcp servers syncing state between each other

  
  I regularly see the following in the syslog

  Apr  4 00:04:55 gw sh[1500]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
  Apr  4 00:04:55 gw sh[1500]: #0 0x7f36befeda4a in ??
  Apr  4 00:04:55 gw sh[1500]: #1 0x7f36befed980 in ??
  Apr  4 00:04:55 gw sh[1500]: #2 0x7f36bf0297e1 in ??
  Apr  4 00:04:55 gw sh[1500]: #3 0x7f36bedd0609 in ??
  Apr  4 00:04:55 gw sh[1500]: #4 0x7f36bef0c153 in ??
  Apr  4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Main process exited, 
code=killed, status=6/ABRT
  Apr  4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Failed with result 
'signal'.
  Apr  4 00:05:00 gw systemd[1]: isc-dhcp-server.service: Scheduled restart 
job, restart counter is at 3.
  Apr  4 00:05:00 gw systemd[1]: Stopped ISC DHCP IPv4 server.
  Apr  4 00:05:00 gw systemd[1]: Started ISC DHCP IPv4 server.
  Apr  4 00:05:00 gw kernel: [ 3508.161248] audit: type=1400 
audit(1585958700.678:46): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2068/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw dhcpd[2049]: Internet Systems Consortium DHCP Server 4.4.1
  Apr  4 00:05:00 gw sh[2049]: Internet Systems Consortium DHCP Server 4.4.1
  Apr  4 00:05:00 gw sh[2049]: Copyright 2004-2018 Internet Systems Consortium.
  Apr  4 00:05:00 gw sh[2049]: All rights reserved.
  Apr  4 00:05:00 gw sh[2049]: For info, please visit 
https://www.isc.org/software/dhcp/
  Apr  4 00:05:00 gw dhcpd[2049]: Copyright 2004-2018 Internet Systems 
Consortium.
  Apr  4 00:05:00 gw dhcpd[2049]: All rights reserved.
  Apr  4 00:05:00 gw dhcpd[2049]: For info, please visit 
https://www.isc.org/software/dhcp/
  Apr  4 00:05:00 gw kernel: [ 3508.161561] audit: type=1400 
audit(1585958700.678:47): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2069/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw kernel: [ 3508.161563] audit: type=1400 
audit(1585958700.682:48): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2070/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw dhcpd[2049]: Config file: /etc/dhcp/dhcpd.conf
  Apr  4 00:05:00 gw sh[2049]: Config file: /etc/dhcp/dhcpd.conf
  Apr  4 00:05:00 gw sh[2049]: Database file: /var/lib/dhcp/dhcpd.leases
  Apr  4 00:05:00 gw sh[2049]: PID file: /run/dhcp-server/dhcpd.pid
  Apr  4 00:05:00 gw dhcpd[2049]: Database file: /var/lib/dhcp/dhcpd.leases
  Apr  4 00:05:00 gw dhcpd[2049]: PID file: /run/dhcp-server/dhcpd.pid
  Apr  4 00:05:00 gw dhcpd[2049]: Wrote 0 deleted host decls to leases file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1870729/+subscriptions

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

[Touch-packages] [Bug 1871488] [NEW] gnome-online-accounts doesn't sync nextcloud calendar

[Jeffrey Bouter]

Public bug reported:

gnome-online-accounts does not synchronise calendars into the evolution
data server. Therefore, calendars are not displayed in the gnome-
calendar application or the time/calendar of gnome shell (when the clock
in the centre of the top bar is clicked)

Manually adding all CalDAV calendars in Evolution resolves the issue,
which makes me think the issue lies between gnome-online-accounts and
the evolution data server.

This may be related to bug #1866999

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-online-accounts 3.36.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu24
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Apr  7 22:48:37 2020
InstallationDate: Installed on 2020-03-17 (21 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
SourcePackage: gnome-online-accounts
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-online-accounts (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

** Description changed:

- gnome-online-accounts does not synchronise accounts into the evolution
+ gnome-online-accounts does not synchronise calendars into the evolution
  data server. Therefore, calendars are not displayed in the gnome-
  calendar application or the time/calendar of gnome shell (when the clock
  in the centre of the top bar is clicked)
  
  Manually adding all CalDAV calendars in Evolution resolves the issue,
  which makes me think the issue lies between gnome-online-accounts and
  the evolution data server.
  
  This may be related to bug #1866999
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-online-accounts 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Apr  7 22:48:37 2020
  InstallationDate: Installed on 2020-03-17 (21 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  gnome-online-accounts doesn't sync nextcloud calendar

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

Bug description:
  gnome-online-accounts does not synchronise calendars into the
  evolution data server. Therefore, calendars are not displayed in the
  gnome-calendar application or the time/calendar of gnome shell (when
  the clock in the centre of the top bar is clicked)

  Manually adding all CalDAV calendars in Evolution resolves the issue,
  which makes me think the issue lies between gnome-online-accounts and
  the evolution data server.

  This may be related to bug #1866999

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-online-accounts 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Apr  7 22:48:37 2020
  InstallationDate: Installed on 2020-03-17 (21 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1871487] Re: anon_inode:[eventfd] leaked on vgs invocation inside lxd container

[Alasdair G. Kergon]

The message is warning you that whatever process launched 'vgs' leaked a
file descriptor i.e. it has granted 'vgs' access to a file that should
not be there.

So you'll want to move this bug to whichever component that is e.g.
something related to 'lxc'

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

Title:
  anon_inode:[eventfd] leaked on vgs invocation inside lxd container

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  $ lxc launch ubuntu-daily:f reproducer
  $ lxc shell reproducer
  $ vgs

  Expected behaviour:

No output (the behaviour on an EC2 instance with no VGs).

  Actual behaviour:

Outputs "File descriptor 25 (anon_inode:[eventfd]) leaked on vgs
  invocation. Parent PID 283: -bash"

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lvm2 2.03.07-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-1028.29~18.04.1-gcp 5.0.21
  Uname: Linux 5.0.0-1028-gcp x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_0_0_1028_29_gcp_65 
lkp_Ubuntu_5_0_0_1028_29_gcp_64 nf_tables lkp_Ubuntu_5_0_0_1028_29_gcp_63 
ebtable_filter ebtables ufs msdos xfs binfmt_misc veth ip6t_MASQUERADE 
ip6table_nat nf_nat_ipv6 ipt_MASQUERADE xt_CHECKSUM xt_comment xt_tcpudp 
iptable_nat nf_nat_ipv4 nf_nat iptable_mangle bridge stp llc zfs zunicode zavl 
icp zcommon znvpair spl ip6table_filter ip6_tables iptable_filter bpfilter 
nls_iso8859_1 input_leds serio_raw sch_fq_codel ib_iser rdma_cm iw_cm ib_cm 
ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables 
autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 
crypto_simd cryptd glue_helper virtio_net net_failover failover psmouse
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  Date: Tue Apr  7 20:19:14 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  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/1871487/+subscriptions

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

[Touch-packages] [Bug 1870837] Re: hcitool lescan says 'Set scan parameters failed: Input/output error'

[mm]

Bluetoothctl and blueman are both using LE Extended commands and are
therefor working I think.

(btw: I would edit my comments if I could ...)

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

Title:
  hcitool lescan says 'Set scan parameters failed: Input/output error'

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  Hi,

  after some testing with Ubuntu 20.04 beta I couldn't get hcitool
  lescan working. I get the following error:

  hcitool lescan
  Set scan parameters failed: Input/output error

  Bluetooth hardware: 
  hci0:   Type: Primary  Bus: USB
  BD Address: 04:EA:56:21:xx:xx  ACL MTU: 1021:4  SCO MTU: 96:6
  UP RUNNING
  RX bytes:1605 acl:0 sco:0 events:123 errors:0
  TX bytes:5801 acl:0 sco:0 commands:123 errors:0
  Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
  Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
  Link policy: RSWITCH SNIFF
  Link mode: SLAVE ACCEPT
  Name: 'xx'
  Class: 0x200104
  Service Classes: Audio
  Device Class: Computer, Desktop workstation
  HCI Version: 5.1 (0xa)  Revision: 0x100
  LMP Version: 5.1 (0xa)  Subversion: 0x100
  Manufacturer: Intel Corp. (2)

  It is not hardware related, since I get the same error with a USB
  bluetooth dongle:

  hcitool -i hci1 lescan
  Set scan parameters failed: Input/output error

  hcitool scan is working fine on both devices; bluetoothctl is also working 
and able to find ble devices.
  I would normally prefer bluetoothctl, but I got a software which is based on 
hcitool.

  dmesg shows this errors:
  [  138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already 
present!
  [  138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already 
present!

  Bluez version:
  bluez 5.53-0ubuntu2 amd64

  System:
  Distributor ID: Ubuntu
  Description:Ubuntu Focal Fossa (development branch)
  Release:20.04
  Codename:   focal
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-01 (4 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 
(20200331)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0463: MGE UPS Systems UPS
   Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 
(ZW090) - UZB
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Intel(R) Client Systems NUC8i3BEH
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/vgcs2ubct-root ro
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/23/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0075.2019.1023.1448
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-306
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0075.2019.1023.1448:bd10/23/2019:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.sku: BOXNUC8i3BEH
  dmi.product.version: J72753-305
  dmi.sys.vendor: Intel(R) Client Systems
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 04:EA:56:21:1E:D3  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:17030 acl:0 sco:0 events:2764 errors:0
TX bytes:677849 acl:0 sco:0 commands:2757 errors:0

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

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

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

[Ubuntu Foundations Team Bug Bot]

The attachment "dual-jacks.patch" seems to be a debdiff.  The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

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

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

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

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

  [Expected result]
  Can detect external headset

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

  [Regression Potential]
  Low.

  [Failure rate]
  100%

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

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

  Ubuntu-Focal-Source:
  
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

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

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

[Touch-packages] [Bug 1870837] Re: hcitool lescan says 'Set scan parameters failed: Input/output error'

[mm]

It seems to me that the "normal" LE commands are broken and only the LE
Extended commands are working?

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

Title:
  hcitool lescan says 'Set scan parameters failed: Input/output error'

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  Hi,

  after some testing with Ubuntu 20.04 beta I couldn't get hcitool
  lescan working. I get the following error:

  hcitool lescan
  Set scan parameters failed: Input/output error

  Bluetooth hardware: 
  hci0:   Type: Primary  Bus: USB
  BD Address: 04:EA:56:21:xx:xx  ACL MTU: 1021:4  SCO MTU: 96:6
  UP RUNNING
  RX bytes:1605 acl:0 sco:0 events:123 errors:0
  TX bytes:5801 acl:0 sco:0 commands:123 errors:0
  Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
  Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
  Link policy: RSWITCH SNIFF
  Link mode: SLAVE ACCEPT
  Name: 'xx'
  Class: 0x200104
  Service Classes: Audio
  Device Class: Computer, Desktop workstation
  HCI Version: 5.1 (0xa)  Revision: 0x100
  LMP Version: 5.1 (0xa)  Subversion: 0x100
  Manufacturer: Intel Corp. (2)

  It is not hardware related, since I get the same error with a USB
  bluetooth dongle:

  hcitool -i hci1 lescan
  Set scan parameters failed: Input/output error

  hcitool scan is working fine on both devices; bluetoothctl is also working 
and able to find ble devices.
  I would normally prefer bluetoothctl, but I got a software which is based on 
hcitool.

  dmesg shows this errors:
  [  138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already 
present!
  [  138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already 
present!

  Bluez version:
  bluez 5.53-0ubuntu2 amd64

  System:
  Distributor ID: Ubuntu
  Description:Ubuntu Focal Fossa (development branch)
  Release:20.04
  Codename:   focal
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-01 (4 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 
(20200331)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0463: MGE UPS Systems UPS
   Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 
(ZW090) - UZB
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Intel(R) Client Systems NUC8i3BEH
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/vgcs2ubct-root ro
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/23/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0075.2019.1023.1448
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-306
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0075.2019.1023.1448:bd10/23/2019:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.sku: BOXNUC8i3BEH
  dmi.product.version: J72753-305
  dmi.sys.vendor: Intel(R) Client Systems
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 04:EA:56:21:1E:D3  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:17030 acl:0 sco:0 events:2764 errors:0
TX bytes:677849 acl:0 sco:0 commands:2757 errors:0

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

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

[Touch-packages] [Bug 1871487] [NEW] anon_inode:[eventfd] leaked on vgs invocation inside lxd container

[Dan Watkins]

Public bug reported:

Steps to reproduce:

$ lxc launch ubuntu-daily:f reproducer
$ lxc shell reproducer
$ vgs

Expected behaviour:

  No output (the behaviour on an EC2 instance with no VGs).

Actual behaviour:

  Outputs "File descriptor 25 (anon_inode:[eventfd]) leaked on vgs
invocation. Parent PID 283: -bash"

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: lvm2 2.03.07-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-1028.29~18.04.1-gcp 5.0.21
Uname: Linux 5.0.0-1028-gcp x86_64
NonfreeKernelModules: lkp_Ubuntu_5_0_0_1028_29_gcp_65 
lkp_Ubuntu_5_0_0_1028_29_gcp_64 nf_tables lkp_Ubuntu_5_0_0_1028_29_gcp_63 
ebtable_filter ebtables ufs msdos xfs binfmt_misc veth ip6t_MASQUERADE 
ip6table_nat nf_nat_ipv6 ipt_MASQUERADE xt_CHECKSUM xt_comment xt_tcpudp 
iptable_nat nf_nat_ipv4 nf_nat iptable_mangle bridge stp llc zfs zunicode zavl 
icp zcommon znvpair spl ip6table_filter ip6_tables iptable_filter bpfilter 
nls_iso8859_1 input_leds serio_raw sch_fq_codel ib_iser rdma_cm iw_cm ib_cm 
ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables 
autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 
crypto_simd cryptd glue_helper virtio_net net_failover failover psmouse
ApportVersion: 2.20.11-0ubuntu24
Architecture: amd64
Date: Tue Apr  7 20:19:14 2020
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: lvm2
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  anon_inode:[eventfd] leaked on vgs invocation inside lxd container

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  $ lxc launch ubuntu-daily:f reproducer
  $ lxc shell reproducer
  $ vgs

  Expected behaviour:

No output (the behaviour on an EC2 instance with no VGs).

  Actual behaviour:

Outputs "File descriptor 25 (anon_inode:[eventfd]) leaked on vgs
  invocation. Parent PID 283: -bash"

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lvm2 2.03.07-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-1028.29~18.04.1-gcp 5.0.21
  Uname: Linux 5.0.0-1028-gcp x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_0_0_1028_29_gcp_65 
lkp_Ubuntu_5_0_0_1028_29_gcp_64 nf_tables lkp_Ubuntu_5_0_0_1028_29_gcp_63 
ebtable_filter ebtables ufs msdos xfs binfmt_misc veth ip6t_MASQUERADE 
ip6table_nat nf_nat_ipv6 ipt_MASQUERADE xt_CHECKSUM xt_comment xt_tcpudp 
iptable_nat nf_nat_ipv4 nf_nat iptable_mangle bridge stp llc zfs zunicode zavl 
icp zcommon znvpair spl ip6table_filter ip6_tables iptable_filter bpfilter 
nls_iso8859_1 input_leds serio_raw sch_fq_codel ib_iser rdma_cm iw_cm ib_cm 
ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables 
autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 
crypto_simd cryptd glue_helper virtio_net net_failover failover psmouse
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  Date: Tue Apr  7 20:19:14 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  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/1871487/+subscriptions

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

[Touch-packages] [Bug 1870837] Re: hcitool lescan says 'Set scan parameters failed: Input/output error'

[mm]

After some time I am back to:
hcitool lescan
Set scan parameters failed: Input/output error

Issuing
hcitool cmd 0x03 0x0003
< HCI Command: ogf 0x03, ocf 0x0003, plen 0
> HCI Event: 0x0e plen 4
  02 03 0C 00

helps again, but I still can't find any BLE devices with hcitool lescan. 
Nevertheless the i/o error is gone and btmon also doesn't report any error.
Sadly the result is still a non functional lescan ...

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

Title:
  hcitool lescan says 'Set scan parameters failed: Input/output error'

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  Hi,

  after some testing with Ubuntu 20.04 beta I couldn't get hcitool
  lescan working. I get the following error:

  hcitool lescan
  Set scan parameters failed: Input/output error

  Bluetooth hardware: 
  hci0:   Type: Primary  Bus: USB
  BD Address: 04:EA:56:21:xx:xx  ACL MTU: 1021:4  SCO MTU: 96:6
  UP RUNNING
  RX bytes:1605 acl:0 sco:0 events:123 errors:0
  TX bytes:5801 acl:0 sco:0 commands:123 errors:0
  Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
  Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
  Link policy: RSWITCH SNIFF
  Link mode: SLAVE ACCEPT
  Name: 'xx'
  Class: 0x200104
  Service Classes: Audio
  Device Class: Computer, Desktop workstation
  HCI Version: 5.1 (0xa)  Revision: 0x100
  LMP Version: 5.1 (0xa)  Subversion: 0x100
  Manufacturer: Intel Corp. (2)

  It is not hardware related, since I get the same error with a USB
  bluetooth dongle:

  hcitool -i hci1 lescan
  Set scan parameters failed: Input/output error

  hcitool scan is working fine on both devices; bluetoothctl is also working 
and able to find ble devices.
  I would normally prefer bluetoothctl, but I got a software which is based on 
hcitool.

  dmesg shows this errors:
  [  138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already 
present!
  [  138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already 
present!

  Bluez version:
  bluez 5.53-0ubuntu2 amd64

  System:
  Distributor ID: Ubuntu
  Description:Ubuntu Focal Fossa (development branch)
  Release:20.04
  Codename:   focal
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-01 (4 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 
(20200331)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0463: MGE UPS Systems UPS
   Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 
(ZW090) - UZB
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Intel(R) Client Systems NUC8i3BEH
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/vgcs2ubct-root ro
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/23/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0075.2019.1023.1448
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-306
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0075.2019.1023.1448:bd10/23/2019:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.sku: BOXNUC8i3BEH
  dmi.product.version: J72753-305
  dmi.sys.vendor: Intel(R) Client Systems
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 04:EA:56:21:1E:D3  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:17030 acl:0 sco:0 events:2764 errors:0
TX bytes:677849 acl:0 sco:0 commands:2757 errors:0

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

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

[Touch-packages] [Bug 1871403] Re: wifi won't connect

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => xorg (Ubuntu)

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

Title:
  wifi won't connect

Status in xorg package in Ubuntu:
  New

Bug description:
  My wifi adapter won't connect under Kubuntu.  It works fine when I
  boot the same laptop under Ubuntu 18.04, but when I boot under Kubuntu
  20.04, I get "Configuring Interface" followed by "Wireless interface
  (wlp1s0)  The wifi network could not be found."

  It worked fine up until today.  Ethernet connection works fine.

  I tried restarting NetworkManager.service in systemctl and I get this:

  NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Tue 2020-04-07 10:08:47 EDT; 1min 3s ago
 Docs: man:NetworkManager(8)
 Main PID: 4231 (NetworkManager)
Tasks: 3 (limit: 16627)
   Memory: 5.0M
   CGroup: /system.slice/NetworkManager.service
   └─4231 /usr/sbin/NetworkManager --no-daemon

  Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.1829] 
device (wlp1s0): supplicant interface state: scanning -> authenticating
  Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.1830] 
device (p2p-dev-wlp1s0): supplicant management interface state: scanning -> 
authenticating
  Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.2268] 
device (wlp1s0): supplicant interface state: authenticating -> disconnected
  Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.2269] 
device (p2p-dev-wlp1s0): supplicant management interface state: authenticating 
-> disconnected
  Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8910] 
device (wlp1s0): Activation: (wifi) association took too long, failing 
activation
  Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8911] 
device (wlp1s0): state change: config -> failed (reason 'ssid-not-found', 
sys-iface-state: 'managed')
  Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8933] 
device (wlp1s0): Activation: failed for connection 'BoulderNET'
  Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8939] 
device (wlp1s0): state change: failed -> disconnected (reason 'none', 
sys-iface-state: 'managed')
  Apr 07 10:09:34 ZenBook NetworkManager[4231]:   [1586268574.2285] 
device (wlp1s0): supplicant interface state: disconnected -> inactive
  Apr 07 10:09:34 ZenBook NetworkManager[4231]:   [1586268574.2287] 
device (p2p-dev-wlp1s0): supplicant management interface state: disconnected -> 
inactive
  dennis@ZenBook:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  Uname: Linux 5.6.1-050601-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Tue Apr  7 10:14:23 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Picasso [1043:1b71]
  InstallationDate: Installed on 2020-03-06 (31 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX434DA_UM433DA
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.1-050601-generic 
root=UUID=f2ef7f4c-875c-4861-a849-e5ebf6d646fd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX434DA_UM433DA.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX434DA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX434DA_UM433DA.302:bd09/05/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX434DA_UM433DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX434DA_UM433DA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  

[Touch-packages] [Bug 1871422] Re: Unable to get 4K 60Hz on nvidia GT 1030 on AMD Ryzen 5 2600

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => xorg (Ubuntu)

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

Title:
  Unable to get 4K 60Hz on nvidia GT 1030 on AMD Ryzen 5 2600

Status in xorg package in Ubuntu:
  New

Bug description:
  This is a duplicate of https://bugs.launchpad.net/ubuntu/+source/xorg-
  server/+bug/1870637

  The only difference is that i switched from a Ryzen 2200G CPU to a Ryzen 5 
2600.
  Still running a zotac nvidia GT1030 graphics card.
  I was not sure how to get the system log files to the older thread, my 
apologies for the inconvenience.

  I was able to set 4K 60 @200%, but after reboot i got a crash notice and i'm 
back to fullHD.
  If this would have fixed the issue i would have ordered a 3700X for my 
windows system and would have kept the ryzen 5 2600 for my ubuntu system, but 
since this is not the case, i'll be putting the ryzen 2200G back into my ubuntu 
system.

  Before i do so; I'll try to enable wayland, as asked, but if i
  remember correctly i read on a post on omgunbuntu that wayland is
  currently disabled on the beta? Anyway, i'll have a look and report
  back

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..29.00.0: Error: [Errno 21] Is een map: 
'/proc/driver/nvidia/gpus/:29:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu1)
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 17:05:52 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.64, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] 
[19da:2476]
  InstallationDate: Installed on 2020-04-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Micro-Star International Co., Ltd. MS-7B84
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=44827b31-356c-437b-9865-80f973861754 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.D0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M PRO-M2 (MS-7B84)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.D0:bd12/03/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B84:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-M2(MS-7B84):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B84
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1871475] Re: Black screen after screen lock

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => xorg (Ubuntu)

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

Title:
  Black screen after screen lock

Status in xorg package in Ubuntu:
  New

Bug description:
  When I lock the screen with "Windows" + "L" key combination the screen
  gets locked, but I expect it to stay on and be locked. In Ubuntu
  20.04. when I do it the screen gets locked but get immediately black a
  sit would be in standby. The screen should stay on and show locked
  screen.

  This black screen happens often, but sometimes not.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 20:51:27 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Picasso [17aa:5125]
  InstallationDate: Installed on 2020-04-02 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  MachineType: LENOVO 20NKS01Y00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=024c6306-92b0-4cf4-88de-71e1f0671318 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/28/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R12ET46W(1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NKS01Y00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR12ET46W(1.16):bd10/28/2019:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T495
  dmi.product.name: 20NKS01Y00
  dmi.product.sku: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495
  dmi.product.version: ThinkPad T495
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1871403] [NEW] wifi won't connect

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

My wifi adapter won't connect under Kubuntu.  It works fine when I boot
the same laptop under Ubuntu 18.04, but when I boot under Kubuntu 20.04,
I get "Configuring Interface" followed by "Wireless interface (wlp1s0)
The wifi network could not be found."

It worked fine up until today.  Ethernet connection works fine.

I tried restarting NetworkManager.service in systemctl and I get this:

NetworkManager.service - Network Manager
 Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
 Active: active (running) since Tue 2020-04-07 10:08:47 EDT; 1min 3s ago
   Docs: man:NetworkManager(8)
   Main PID: 4231 (NetworkManager)
  Tasks: 3 (limit: 16627)
 Memory: 5.0M
 CGroup: /system.slice/NetworkManager.service
 └─4231 /usr/sbin/NetworkManager --no-daemon

Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.1829] device 
(wlp1s0): supplicant interface state: scanning -> authenticating
Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.1830] device 
(p2p-dev-wlp1s0): supplicant management interface state: scanning -> 
authenticating
Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.2268] device 
(wlp1s0): supplicant interface state: authenticating -> disconnected
Apr 07 10:09:24 ZenBook NetworkManager[4231]:   [1586268564.2269] device 
(p2p-dev-wlp1s0): supplicant management interface state: authenticating -> 
disconnected
Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8910] device 
(wlp1s0): Activation: (wifi) association took too long, failing activation
Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8911] device 
(wlp1s0): state change: config -> failed (reason 'ssid-not-found', 
sys-iface-state: 'managed')
Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8933] device 
(wlp1s0): Activation: failed for connection 'BoulderNET'
Apr 07 10:09:27 ZenBook NetworkManager[4231]:   [1586268567.8939] device 
(wlp1s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 
'managed')
Apr 07 10:09:34 ZenBook NetworkManager[4231]:   [1586268574.2285] device 
(wlp1s0): supplicant interface state: disconnected -> inactive
Apr 07 10:09:34 ZenBook NetworkManager[4231]:   [1586268574.2287] device 
(p2p-dev-wlp1s0): supplicant management interface state: disconnected -> 
inactive
dennis@ZenBook:~$

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
Uname: Linux 5.6.1-050601-generic x86_64
ApportVersion: 2.20.11-0ubuntu24
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: KDE
Date: Tue Apr  7 10:14:23 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Picasso [1043:1b71]
InstallationDate: Installed on 2020-03-06 (31 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306)
MachineType: ASUSTeK COMPUTER INC. ZenBook UX434DA_UM433DA
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.1-050601-generic 
root=UUID=f2ef7f4c-875c-4861-a849-e5ebf6d646fd ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/05/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX434DA_UM433DA.302
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX434DA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX434DA_UM433DA.302:bd09/05/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX434DA_UM433DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ZenBook
dmi.product.name: ZenBook UX434DA_UM433DA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal kubuntu ubuntu
-- 
wifi won't connect
https://bugs.launchpad.net/bugs/1871403
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, 

[Touch-packages] [Bug 1871422] [NEW] Unable to get 4K 60Hz on nvidia GT 1030 on AMD Ryzen 5 2600

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

This is a duplicate of https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1870637

The only difference is that i switched from a Ryzen 2200G CPU to a Ryzen 5 2600.
Still running a zotac nvidia GT1030 graphics card.
I was not sure how to get the system log files to the older thread, my 
apologies for the inconvenience.

I was able to set 4K 60 @200%, but after reboot i got a crash notice and i'm 
back to fullHD.
If this would have fixed the issue i would have ordered a 3700X for my windows 
system and would have kept the ryzen 5 2600 for my ubuntu system, but since 
this is not the case, i'll be putting the ryzen 2200G back into my ubuntu 
system.

Before i do so; I'll try to enable wayland, as asked, but if i remember
correctly i read on a post on omgunbuntu that wayland is currently
disabled on the beta? Anyway, i'll have a look and report back

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..29.00.0: Error: [Errno 21] Is een map: 
'/proc/driver/nvidia/gpus/:29:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu1)
ApportVersion: 2.20.11-0ubuntu24
Architecture: amd64
BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr  7 17:05:52 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: nvidia, 440.64, 5.4.0-21-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] [19da:2476]
InstallationDate: Installed on 2020-04-07 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
MachineType: Micro-Star International Co., Ltd. MS-7B84
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=44827b31-356c-437b-9865-80f973861754 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/03/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.D0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B450M PRO-M2 (MS-7B84)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.D0:bd12/03/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B84:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-M2(MS-7B84):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7B84
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal resolution ubuntu
-- 
Unable to get 4K 60Hz on nvidia GT 1030 on AMD Ryzen 5 2600
https://bugs.launchpad.net/bugs/1871422
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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

[Touch-packages] [Bug 1871475] [NEW] Black screen after screen lock

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When I lock the screen with "Windows" + "L" key combination the screen
gets locked, but I expect it to stay on and be locked. In Ubuntu 20.04.
when I do it the screen gets locked but get immediately black a sit
would be in standby. The screen should stay on and show locked screen.

This black screen happens often, but sometimes not.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu24
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr  7 20:51:27 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 
00 [VGA controller])
   Subsystem: Lenovo Picasso [17aa:5125]
InstallationDate: Installed on 2020-04-02 (4 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
MachineType: LENOVO 20NKS01Y00
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=024c6306-92b0-4cf4-88de-71e1f0671318 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/28/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R12ET46W(1.16 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20NKS01Y00
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrR12ET46W(1.16):bd10/28/2019:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T495
dmi.product.name: 20NKS01Y00
dmi.product.sku: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495
dmi.product.version: ThinkPad T495
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal third-party-packages ubuntu
-- 
Black screen after screen lock
https://bugs.launchpad.net/bugs/1871475
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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

[Touch-packages] [Bug 1871148] Re: services start before apparmor profiles are loaded

[Zygmunt Krynicki]

@jibel, can you explain how the mount generator makes local-fs.target
satisfied *before* /var/lib is mounted?

I think this is worth investigating.

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

Title:
  services start before apparmor profiles are loaded

Status in AppArmor:
  Invalid
Status in apparmor package in Ubuntu:
  Fix Committed
Status in zsys package in Ubuntu:
  Invalid
Status in apparmor source package in Focal:
  Fix Committed
Status in zsys source package in Focal:
  Invalid

Bug description:
  Per discussion with Zyga in #snapd on Freenode, I have hit a race
  condition where services are being started by the system before
  apparmor has been started. I have a complete log of my system showing
  the effect somewhere within at https://paste.ubuntu.com/p/Jyx6gfFc3q/.
  Restarting apparmor using `sudo systemctl restart apparmor` is enough
  to bring installed snaps back to full functionality.

  Previously, when running any snap I would receive the following in the
  terminal:

  ---
  cannot change profile for the next exec call: No such file or directory
  snap-update-ns failed with code 1: File exists
  ---

  Updated to add for Jamie:

  $ snap version
  snap2.44.2+20.04
  snapd   2.44.2+20.04
  series  16
  ubuntu  20.04
  kernel  5.4.0-21-generic

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

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

[Touch-packages] [Bug 1871484] [NEW] manpage refers to non-existent "tags configuration setting description below"

[Dan Watkins]

Public bug reported:

And, AFAICT, it isn't present in any LVM manpage:

$ zgrep tags /usr/share/man/man*/*lvm*
/usr/share/man/man5/lvm.conf.5.gz:See \fBtags\fP configuration setting 
description below.
/usr/share/man/man7/lvmreport.7.gz:Let's display one one more field in addition 
("lv_tags" in this example)
/usr/share/man/man7/lvmreport.7.gz:# lvs \-o+lv_tags
/usr/share/man/man7/lvmreport.7.gz:# lvs \-o+tags
/usr/share/man/man7/lvmreport.7.gz:# lvs \-o 
name,size,origin,snap_percent,tags,time
/usr/share/man/man7/lvmreport.7.gz:# lvchange \-\-deltag test \-S 'tags = test'
/usr/share/man/man7/lvmreport.7.gz:whole list strictly, its subset or 
intersection. Let's take "lv_tags"
/usr/share/man/man7/lvmreport.7.gz:tags field. We're using { } to denote that 
we're interested in subset
/usr/share/man/man7/lvmreport.7.gz:# lvs \-o name,tags \-S 'tags={tagA}'
/usr/share/man/man7/lvmreport.7.gz:# lvs \-o name,tags \-S 'tags=tagA'
/usr/share/man/man7/lvmreport.7.gz:# lvs \-o name,tags \-S 
'tags={tagA,tagC,tagD}'
/usr/share/man/man7/lvmreport.7.gz:# lvs \-o name,tags \-S 'tags={tagA || tagC 
|| tagD}'
/usr/share/man/man7/lvmreport.7.gz:# lvs \-o name,tags \-S 'tags=[tagA]'

/usr/share/man/man7/lvmreport.7.gz:# lvs \-o name,tags \-S 'tags=[tagB,tagA]'
/usr/share/man/man7/lvmreport.7.gz:# lvs \-o name,tags \-S 'tags=[tagA || tagC 
|| tagD]'
/usr/share/man/man7/lvmreport.7.gz:# lvs \-o name,tags \-S 'tags=""'
/usr/share/man/man7/lvmreport.7.gz:# lvs \-o name,tags \-S 'tags!=""'
/usr/share/man/man8/lvm.8.gz:.B tags
/usr/share/man/man8/lvm.8.gz:Display any tags defined on this host.
/usr/share/man/man8/lvm.8.gz:Physical Volumes are considered to match if any of 
the listed tags is

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: lvm2 2.03.07-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
ApportVersion: 2.20.11-0ubuntu24
Architecture: amd64
CurrentDesktop: i3
Date: Tue Apr  7 15:54:40 2020
InstallationDate: Installed on 2019-05-07 (336 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
SourcePackage: lvm2
UpgradeStatus: Upgraded to focal on 2019-11-15 (144 days ago)

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

Title:
  manpage refers to non-existent "tags configuration setting description
  below"

Status in lvm2 package in Ubuntu:
  New

Bug description:
  And, AFAICT, it isn't present in any LVM manpage:

  $ zgrep tags /usr/share/man/man*/*lvm*
  /usr/share/man/man5/lvm.conf.5.gz:See \fBtags\fP configuration setting 
description below.
  /usr/share/man/man7/lvmreport.7.gz:Let's display one one more field in 
addition ("lv_tags" in this example)
  /usr/share/man/man7/lvmreport.7.gz:# lvs \-o+lv_tags
  /usr/share/man/man7/lvmreport.7.gz:# lvs \-o+tags
  /usr/share/man/man7/lvmreport.7.gz:# lvs \-o 
name,size,origin,snap_percent,tags,time
  /usr/share/man/man7/lvmreport.7.gz:# lvchange \-\-deltag test \-S 'tags = 
test'
  /usr/share/man/man7/lvmreport.7.gz:whole list strictly, its subset or 
intersection. Let's take "lv_tags"
  /usr/share/man/man7/lvmreport.7.gz:tags field. We're using { } to denote that 
we're interested in subset
  /usr/share/man/man7/lvmreport.7.gz:# lvs \-o name,tags \-S 'tags={tagA}'
  /usr/share/man/man7/lvmreport.7.gz:# lvs \-o name,tags \-S 'tags=tagA'
  /usr/share/man/man7/lvmreport.7.gz:# lvs \-o name,tags \-S 
'tags={tagA,tagC,tagD}'
  /usr/share/man/man7/lvmreport.7.gz:# lvs \-o name,tags \-S 'tags={tagA || 
tagC || tagD}'
  /usr/share/man/man7/lvmreport.7.gz:# lvs \-o name,tags \-S 'tags=[tagA]'  
  
  /usr/share/man/man7/lvmreport.7.gz:# lvs \-o name,tags \-S 'tags=[tagB,tagA]'
  /usr/share/man/man7/lvmreport.7.gz:# lvs \-o name,tags \-S 'tags=[tagA || 
tagC || tagD]'
  /usr/share/man/man7/lvmreport.7.gz:# lvs \-o name,tags \-S 'tags=""'
  /usr/share/man/man7/lvmreport.7.gz:# lvs \-o name,tags \-S 'tags!=""'
  /usr/share/man/man8/lvm.8.gz:.B tags
  /usr/share/man/man8/lvm.8.gz:Display any tags defined on this host.
  /usr/share/man/man8/lvm.8.gz:Physical Volumes are considered to match if any 
of the listed tags is

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lvm2 2.03.07-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  CurrentDesktop: i3
  Date: Tue Apr  7 15:54:40 2020
  InstallationDate: Installed on 2019-05-07 (336 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: 

[Touch-packages] [Bug 1870837] Re: hcitool lescan says 'Set scan parameters failed: Input/output error'

[mm]

Executing "hcitool cmd 0x03 0x0003" made the error with hcitool disappear:
hcitool lescan
LE Scan ...

But hcitool does not seem to work as I can't find any ble devices.
btmon output after executing "hcitool cmd 0x03 0x0003 and hcitool lescan:

> HCI Event: Command Complete (0x0e) plen 4 
>#51 [hci0] 21:45:08.127791
  LE Set Scan Enable (0x08|0x000c) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Scan Parameters (0x08|0x000b) plen 7  
   #52 [hci0] 21:45:08.127962
Type: Passive (0x00)
Interval: 10.000 msec (0x0010)
Window: 10.000 msec (0x0010)
Own address type: Public (0x00)
Filter policy: Accept all advertisement (0x00)
> HCI Event: Command Complete (0x0e) plen 4 
>#53 [hci0] 21:45:08.128699
  LE Set Scan Parameters (0x08|0x000b) ncmd 1
Status: Success (0x00)
< HCI Command: LE Set Scan Parameters (0x08|0x000b) plen 7  
   #54 [hci0] 21:45:08.128795
Type: Passive (0x00)
Interval: 10.000 msec (0x0010)
Window: 10.000 msec (0x0010)
Own address type: Public (0x00)
Filter policy: Accept all advertisement (0x00)
> HCI Event: Command Complete (0x0e) plen 4 
>#55 [hci0] 21:45:08.129744
  LE Set Scan Parameters (0x08|0x000b) ncmd 1
Status: Success (0x00)
< HCI Command: LE Set Scan Enable (0x08|0x000c) plen 2  
   #56 [hci0] 21:45:08.129821
Scanning: Enabled (0x01)
Filter duplicates: Disabled (0x00)
> HCI Event: Command Complete (0x0e) plen 4 
>#57 [hci0] 21:45:08.131737
  LE Set Scan Enable (0x08|0x000c) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Scan Enable (0x08|0x000c) plen 2  
   #58 [hci0] 21:45:08.190201
Scanning: Disabled (0x00)
Filter duplicates: Enabled (0x01)
> HCI Event: Command Complete (0x0e) plen 4 
>#59 [hci0] 21:45:08.200856
  LE Set Scan Enable (0x08|0x000c) ncmd 2
Status: Success (0x00)
@ RAW Close: hcitool

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

Title:
  hcitool lescan says 'Set scan parameters failed: Input/output error'

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  Hi,

  after some testing with Ubuntu 20.04 beta I couldn't get hcitool
  lescan working. I get the following error:

  hcitool lescan
  Set scan parameters failed: Input/output error

  Bluetooth hardware: 
  hci0:   Type: Primary  Bus: USB
  BD Address: 04:EA:56:21:xx:xx  ACL MTU: 1021:4  SCO MTU: 96:6
  UP RUNNING
  RX bytes:1605 acl:0 sco:0 events:123 errors:0
  TX bytes:5801 acl:0 sco:0 commands:123 errors:0
  Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
  Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
  Link policy: RSWITCH SNIFF
  Link mode: SLAVE ACCEPT
  Name: 'xx'
  Class: 0x200104
  Service Classes: Audio
  Device Class: Computer, Desktop workstation
  HCI Version: 5.1 (0xa)  Revision: 0x100
  LMP Version: 5.1 (0xa)  Subversion: 0x100
  Manufacturer: Intel Corp. (2)

  It is not hardware related, since I get the same error with a USB
  bluetooth dongle:

  hcitool -i hci1 lescan
  Set scan parameters failed: Input/output error

  hcitool scan is working fine on both devices; bluetoothctl is also working 
and able to find ble devices.
  I would normally prefer bluetoothctl, but I got a software which is based on 
hcitool.

  dmesg shows this errors:
  [  138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already 
present!
  [  138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already 
present!

  Bluez version:
  bluez 5.53-0ubuntu2 amd64

  System:
  Distributor ID: Ubuntu
  Description:Ubuntu Focal Fossa (development branch)
  Release:20.04
  Codename:   focal
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-01 (4 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 
(20200331)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux 

[Touch-packages] [Bug 1854314] Re: Legacy directory /var/run in /lib/systemd/system/dbus.socket

[mm]

Bug still present in current Ubuntu 20.04 beta:
 dmesg|grep accordingly
[   63.817919] systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= 
references a path below legacy directory /var/run/, updating 
/var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update 
the unit file accordingly.

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

Title:
  Legacy directory /var/run in /lib/systemd/system/dbus.socket

Status in D-Bus:
  New
Status in dbus package in Ubuntu:
  Fix Committed
Status in dbus package in Debian:
  Fix Committed

Bug description:
  dbus/focal-proposed,now 1.12.16-2ubuntu1 amd64

  Re(o)curring after each new upgrade of dbus, for quite some time and
  still...

  $ dmesg|grep accordingly
  systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a 
path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket 
→ /run/dbus/system_bus_socket; please update the unit file accordingly.

  Originally:
  $cat /lib/systemd/system/dbus.socket
  [Unit]
  Description=D-Bus System Message Bus Socket

  [Socket]
  ListenStream=/var/run/dbus/system_bus_socket

  After change:
  $cat /lib/systemd/system/dbus.socket
  [Unit]
  Description=D-Bus System Message Bus Socket

  [Socket]
  ListenStream=/run/dbus/system_bus_socket

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

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

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

[David]

I know that If I say that there is still no sound on kernel 5.3.0-46, you will 
ask me to try 5.3.0-47...and so on and so on...
But nonetheless, here we go

user@G3:~$ aplay -l
 List of PLAYBACK Hardware Devices 
card 0: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
user@G3:~$ uname -r
5.3.0-46-generic


Someone should really start working on it. Google suggests there is a handful 
of users affected by this bug with no obvious solution.


** Attachment added: "Screenshot from 2020-04-07 20-18-41.png"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1868319/+attachment/5348986/+files/Screenshot%20from%202020-04-07%2020-18-41.png

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Any time now, the sound card was deactivated, and it appears as a
  "Dummy device". I searched many forums about it, but nothing works.
  I'll be grateful if a program exists that I could install for sound
  card recognition.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 20 16:13:53 2020
  InstallationDate: Installed on 2020-03-19 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_CL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.name: 054J60
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd08/08/2019:svnDellInc.:pnG33590:pvr:rvnDellInc.:rn054J60:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: GSeries
  dmi.product.name: G3 3590
  dmi.product.sku: 0949
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1861558] Re: Snap 'ed applicaitons have garbage on top of the window Close [x] button

[Michael Weimann]

Present on current 20.04 dev release with vanilla GNOME.

While this bug doesn't affect any functionality is shows me every day a
broken UI. That reduces the fun using Ubuntu / snaps.

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

Title:
  Snap 'ed applicaitons have garbage on top of the window Close [x]
  button

Status in adwaita-icon-theme package in Ubuntu:
  Confirmed
Status in gnome-themes-extra package in Ubuntu:
  Confirmed
Status in humanity-icon-theme package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed
Status in ubuntu-mono package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 19.10 installed
  2. Install GNOME application as a Snap - for example with

  sudo snap install gedit gnome-calculator

  3. Open GNOME Tweaks -> Appearance tab, then switch Icon set to the
  one of the following:

  * Adwaita
  * DMZ-Black
  * DMZ-White
  * hicolor
  * HighContrast
  * Humanity
  * Humanity-Dark
  * LoginIcons

  For example - Adwaita theme with Adwaita icon set.

  4. Open GNOME Calculator as a Snap application:

 /snap/bin/gnome-calculator

  Expected result:

  * GNOME Calculator looks as any other GTK application

  Actual result:

  * GNOME Calculator has garbage on top of the window Close [x] button

  ---

  Notes: 
  1. Problem was first seen on AskUbuntu - https://askubuntu.com/q/1206868
  2. one can use the script below to check all possible Theme<->Icon 
combinations:

  ```
  #!/bin/bash

  DISPLAY=:0

  for t in $(ls -1 /usr/share/themes/)
  do 
for i in $(ls -1 /usr/share/icons/)
do

  echo -e "\nTheme: $t, Icons: $i\n"

gsettings set org.gnome.desktop.interface gtk-theme "$t"
gsettings set org.gnome.desktop.interface icon-theme "$i"

  /snap/bin/gnome-calculator

#read -r -s -p "Press  for next theme"   
done
  done

  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: snapd 2.41+19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb  1 17:55:09 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1861558/+subscriptions

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

[Touch-packages] [Bug 1870729] Re: DHCP Server regularly killed code=killed, status=6/ABRT

[mm]

The bug is still present for me with 
ii  isc-dhcp-server   4.4.1-2.1ubuntu4  
  amd64ISC DHCP server for automatic IP address assignment.

apparmor rules are up to date with:
owner @{PROC}/[0-9]*/comm r,
owner @{PROC}/[0-9]*/task/[0-9]*/comm r,

Error in syslog:
Apr  7 19:23:25 cdsv2 systemd[1]: isc-dhcp-server.service: Main process exited, 
code=killed, status=6/ABRT
Apr  7 19:23:25 cdsv2 systemd[1]: isc-dhcp-server.service: Failed with result 
'signal'.

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

Title:
  DHCP Server regularly killed code=killed, status=6/ABRT

Status in isc-dhcp package in Ubuntu:
  Fix Released

Bug description:
  On Ubuntu 20.04 The idc-dhcp- server version is
  isc-dhcp-server:
Installed: (none)
Candidate: 4.4.1-2.1ubuntu3
Version table:
   4.4.1-2.1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  
  The DHCP server is being regularly killed, when searching google the  bug 
looks very similar to an older bug regarding accessing a lease file, that was 
fixed year ago. As a temporary fix in systemd I have enabled a restart every 
time the main process fails. The error got worse when i start to run a pair of 
dhcp servers syncing state between each other

  
  I regularly see the following in the syslog

  Apr  4 00:04:55 gw sh[1500]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
  Apr  4 00:04:55 gw sh[1500]: #0 0x7f36befeda4a in ??
  Apr  4 00:04:55 gw sh[1500]: #1 0x7f36befed980 in ??
  Apr  4 00:04:55 gw sh[1500]: #2 0x7f36bf0297e1 in ??
  Apr  4 00:04:55 gw sh[1500]: #3 0x7f36bedd0609 in ??
  Apr  4 00:04:55 gw sh[1500]: #4 0x7f36bef0c153 in ??
  Apr  4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Main process exited, 
code=killed, status=6/ABRT
  Apr  4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Failed with result 
'signal'.
  Apr  4 00:05:00 gw systemd[1]: isc-dhcp-server.service: Scheduled restart 
job, restart counter is at 3.
  Apr  4 00:05:00 gw systemd[1]: Stopped ISC DHCP IPv4 server.
  Apr  4 00:05:00 gw systemd[1]: Started ISC DHCP IPv4 server.
  Apr  4 00:05:00 gw kernel: [ 3508.161248] audit: type=1400 
audit(1585958700.678:46): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2068/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw dhcpd[2049]: Internet Systems Consortium DHCP Server 4.4.1
  Apr  4 00:05:00 gw sh[2049]: Internet Systems Consortium DHCP Server 4.4.1
  Apr  4 00:05:00 gw sh[2049]: Copyright 2004-2018 Internet Systems Consortium.
  Apr  4 00:05:00 gw sh[2049]: All rights reserved.
  Apr  4 00:05:00 gw sh[2049]: For info, please visit 
https://www.isc.org/software/dhcp/
  Apr  4 00:05:00 gw dhcpd[2049]: Copyright 2004-2018 Internet Systems 
Consortium.
  Apr  4 00:05:00 gw dhcpd[2049]: All rights reserved.
  Apr  4 00:05:00 gw dhcpd[2049]: For info, please visit 
https://www.isc.org/software/dhcp/
  Apr  4 00:05:00 gw kernel: [ 3508.161561] audit: type=1400 
audit(1585958700.678:47): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2069/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw kernel: [ 3508.161563] audit: type=1400 
audit(1585958700.682:48): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2070/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw dhcpd[2049]: Config file: /etc/dhcp/dhcpd.conf
  Apr  4 00:05:00 gw sh[2049]: Config file: /etc/dhcp/dhcpd.conf
  Apr  4 00:05:00 gw sh[2049]: Database file: /var/lib/dhcp/dhcpd.leases
  Apr  4 00:05:00 gw sh[2049]: PID file: /run/dhcp-server/dhcpd.pid
  Apr  4 00:05:00 gw dhcpd[2049]: Database file: /var/lib/dhcp/dhcpd.leases
  Apr  4 00:05:00 gw dhcpd[2049]: PID file: /run/dhcp-server/dhcpd.pid
  Apr  4 00:05:00 gw dhcpd[2049]: Wrote 0 deleted host decls to leases file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1870729/+subscriptions

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

[Touch-packages] [Bug 1871261] Re: package ufw 0.36-6 failed to install/upgrade: end of file on stdin at conffile prompt

[Jamie Strandboge]

Thank you for reporting a bug and helping to make Ubuntu better.

Based on https://launchpadlibrarian.net/473334677/DpkgTerminalLog.txt:

Preparing to unpack .../archives/ufw_0.36-6_all.deb ...
Unpacking ufw (0.36-6) over (0.36-5) ...
Setting up ufw (0.36-6) ...

Configuration file '/etc/default/ufw'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
Y or I  : install the package maintainer's version
N or O  : keep your currently-installed version
  D : show the differences between the versions
  Z : start a shell to examine the situation
 The default action is to keep your current version.
*** ufw (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package ufw 
(--configure):
 end of file on stdin at conffile prompt

Looking at
https://launchpadlibrarian.net/473334680/modified.conffile..etc.default.ufw.txt
I can see that the file (/etc/default/ufw) is missing the trailing
newline from 0.36-5 (this file is not  manipulated by the ufw command).

I can't say why the file on your system was missing the trailing
newline, but since it was, unattended-upgrades (seen in
https://launchpadlibrarian.net/473334676/DpkgHistoryLog.txt) wasn't in a
position to answer the conffile question.

This is not a bug in ufw. To remedy the situation, you should be able to
perform: sudo apt-get -f install.

I also see that the system is running the current development release of
Ubuntu. Unlike stable releases of Ubuntu, it is sometimes easier to
disable unattended-upgrades when using the development release and
instead run apt manually. If you disable it, feel free to re-enable it
once Ubuntu 20.04 is released.

Thanks again!

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

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

Title:
  package ufw 0.36-6 failed to install/upgrade: end of file on stdin at
  conffile prompt

Status in ufw package in Ubuntu:
  Invalid

Bug description:
  No action on my part resulted in a report problem dialog.  I have
  never modified the ufw configuration through the life of this install,
  which has come from 18.04 thru 19.04 and 19.10 to arrive at 20.04.
  Guessing someone made a typo in packaging.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: ufw 0.36-6
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu24
  AptOrdering:
   ufw:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Apr  7 06:45:08 2020
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2017-04-14 (1088 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-is-python2, 2.7.17-3
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.1
  SourcePackage: ufw
  Title: package ufw 0.36-6 failed to install/upgrade: end of file on stdin at 
conffile prompt
  UpgradeStatus: Upgraded to focal on 2020-04-06 (0 days ago)
  mtime.conffile..etc.default.ufw: 2019-07-28T20:35:23.745568

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

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

[Touch-packages] [Bug 1796911] Re: libnss-systemd was denied talking to pid1

[Jamie Strandboge]

** Changed in: apparmor (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  libnss-systemd was denied talking to pid1

Status in apparmor package in Ubuntu:
  Fix Committed

Bug description:
  cosmic
  apparmor 2.12-4ubuntu8
  kernel 4.18.0-8-generic #9-Ubuntu 

  I'm getting these audit messages in dmesg showing apparmor denied errors:
  [   68.649187] audit: type=1107 audit(1539094926.655:32): pid=605 uid=105 
auid=4294967295 ses=4294967295 subj==unconfined msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/systemd1" 
interface="org.freedesktop.systemd1.Manager" member="GetDynamicUsers" 
mask="send" name="org.freedesktop.systemd1" pid=1091 label="/usr/sbin/named" 
peer_pid=1 peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=105 hostname=? addr=? 
terminal=?'
  [  161.059989] audit: type=1107 audit(1539095018.957:33): pid=605 uid=105 
auid=4294967295 ses=4294967295 subj==unconfined msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/systemd1" 
interface="org.freedesktop.systemd1.Manager" member="GetDynamicUsers" 
mask="send" name="org.freedesktop.systemd1" pid=1191 label="/usr/sbin/named" 
peer_pid=1 peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=105 hostname=? addr=? 
terminal=?'
  [  437.582034] audit: type=1107 audit(1539095295.553:34): pid=605 uid=105 
auid=4294967295 ses=4294967295 subj==unconfined msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/systemd1" 
interface="org.freedesktop.systemd1.Manager" member="GetDynamicUsers" 
mask="send" name="org.freedesktop.systemd1" pid=1534 label="/usr/sbin/named" 
peer_pid=1 peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=105 hostname=? addr=? 
terminal=?'
  [  468.184231] audit: type=1107 audit(1539095326.159:35): pid=605 uid=105 
auid=4294967295 ses=4294967295 subj==unconfined msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/systemd1" 
interface="org.freedesktop.systemd1.Manager" member="GetDynamicUsers" 
mask="send" name="org.freedesktop.systemd1" pid=1577 label="/usr/sbin/named" 
peer_pid=1 peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=105 hostname=? addr=? 
terminal=?'

  I pinged #ubuntu-hardened, and xnox had these comments:
   ha
   ahasenack, libnss-systemd was denied talking to pid1
   to query dynamicusers i think
   so i think something somehwere need adjustemnt to allow libnss-systemd 
to talk to pid1 and call GetDynamicUsers
   LookupDynamicUserByName LookupDynamicUserByUID GetDynamicUsers
   as well

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

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

[Touch-packages] [Bug 1870837] Re: hcitool lescan says 'Set scan parameters failed: Input/output error'

[mm]

Installed blueman for testing purpose (wasn't installed before): it is allowed 
to perform these commands:
@ RAW Open: blueman-manager (privileged) version 2.22   
   {0x0004} 
20:43:17.578682
@ RAW Close: blueman-manager
   {0x0004} 
20:43:17.578707
@ MGMT Command: Start Discovery (0x0023) plen 1 
{0x0001} [hci0] 
20:43:17.751082
Address type: 0x07
  BR/EDR
  LE Public
  LE Random
< HCI Command: LE Set Random Address (0x08|0x0005) plen 6   
#495 [hci0] 
20:43:17.751177
Address: 16:68:B8:85:83:60 (Non-Resolvable)
> HCI Event: Command Complete (0x0e) plen 4 
> #496 [hci0] 
> 20:43:17.866069
  LE Set Random Address (0x08|0x0005) ncmd 1
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8 
#497 [hci0] 
20:43:17.866147
Own address type: Random (0x01)
Filter policy: Accept all advertisement (0x00)
PHYs: 0x01
Entry 0: LE 1M
  Type: Active (0x01)
  Interval: 22.500 msec (0x0024)
  Window: 11.250 msec (0x0012)
> HCI Event: Command Complete (0x0e) plen 4 
> #498 [hci0] 
> 20:43:17.867046
  LE Set Extended Scan Parameters (0x08|0x0041) ncmd 1
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6 
#499 [hci0] 
20:43:17.867156
Extended scan: Enabled (0x01)
Filter duplicates: Enabled (0x01)
Duration: 0 msec (0x)
Period: 0.00 sec (0x)
...

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

Title:
  hcitool lescan says 'Set scan parameters failed: Input/output error'

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  Hi,

  after some testing with Ubuntu 20.04 beta I couldn't get hcitool
  lescan working. I get the following error:

  hcitool lescan
  Set scan parameters failed: Input/output error

  Bluetooth hardware: 
  hci0:   Type: Primary  Bus: USB
  BD Address: 04:EA:56:21:xx:xx  ACL MTU: 1021:4  SCO MTU: 96:6
  UP RUNNING
  RX bytes:1605 acl:0 sco:0 events:123 errors:0
  TX bytes:5801 acl:0 sco:0 commands:123 errors:0
  Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
  Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
  Link policy: RSWITCH SNIFF
  Link mode: SLAVE ACCEPT
  Name: 'xx'
  Class: 0x200104
  Service Classes: Audio
  Device Class: Computer, Desktop workstation
  HCI Version: 5.1 (0xa)  Revision: 0x100
  LMP Version: 5.1 (0xa)  Subversion: 0x100
  Manufacturer: Intel Corp. (2)

  It is not hardware related, since I get the same error with a USB
  bluetooth dongle:

  hcitool -i hci1 lescan
  Set scan parameters failed: Input/output error

  hcitool scan is working fine on both devices; bluetoothctl is also working 
and able to find ble devices.
  I would normally prefer bluetoothctl, but I got a software which is based on 
hcitool.

  dmesg shows this errors:
  [  138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already 
present!
  [  138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already 
present!

  Bluez version:
  bluez 5.53-0ubuntu2 amd64

  System:
  Distributor ID: Ubuntu
  Description:Ubuntu Focal Fossa (development branch)
  Release:20.04
  Codename:   focal
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-01 (4 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 
(20200331)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0463: MGE UPS Systems UPS
   Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 
(ZW090) - UZB
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Intel(R) Client Systems NUC8i3BEH
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/vgcs2ubct-root 

[Touch-packages] [Bug 1870837] Re: hcitool lescan says 'Set scan parameters failed: Input/output error'

[mm]

After some more investigation I found out that the software I am using
is NOT using hcitool. It really seems to be another problem since the
custom software and the hcitool lescan command are throwing the same
error observed with btmon:

@ RAW Close: hcitool
   {0x0004} 
20:16:29.633716
@ RAW Open: hcitool (privileged) version 2.22   
{0x0004} [hci0] 
20:16:29.633742
< HCI Command: LE Set Scan Parameters (0x08|0x000b) plen 7  
 #35 [hci0] 
20:16:29.633780
Type: Active (0x01)
Interval: 10.000 msec (0x0010)
Window: 10.000 msec (0x0010)
Own address type: Public (0x00)
Filter policy: Accept all advertisement (0x00)
> HCI Event: Command Complete (0x0e) plen 4 
>  #36 [hci0] 
> 20:16:29.750680
  LE Set Scan Parameters (0x08|0x000b) ncmd 1
Status: Command Disallowed (0x0c)
@ RAW Close: hcitool

Software (phython):
@ RAW Open: python (privileged) version 2.22
{0x0003} [hci0] 
20:14:38.006713
> HCI Event: Command Complete (0x0e) plen 4 
>  #28 [hci0] 
> 20:14:38.119126
  LE Set Scan Enable (0x08|0x000c) ncmd 1
Status: Command Disallowed (0x0c)
< HCI Command: LE Set Scan Parameters (0x08|0x000b) plen 7  
 #29 [hci0] 
20:14:38.119219
Type: Passive (0x00)
Interval: 10.000 msec (0x0010)
Window: 10.000 msec (0x0010)
Own address type: Public (0x00)
Filter policy: Accept all advertisement (0x00)
> HCI Event: Command Complete (0x0e) plen 4 
>  #30 [hci0] 
> 20:14:38.119989
  LE Set Scan Parameters (0x08|0x000b) ncmd 1
Status: Command Disallowed (0x0c)
< HCI Command: LE Set Scan Parameters (0x08|0x000b) plen 7  
 #31 [hci0] 
20:14:38.120063
Type: Passive (0x00)
Interval: 10.000 msec (0x0010)
Window: 10.000 msec (0x0010)
Own address type: Public (0x00)
Filter policy: Accept all advertisement (0x00)
> HCI Event: Command Complete (0x0e) plen 4 
>  #32 [hci0] 
> 20:14:38.120946
  LE Set Scan Parameters (0x08|0x000b) ncmd 1
Status: Command Disallowed (0x0c)
< HCI Command: LE Set Scan Enable (0x08|0x000c) plen 2  
 #33 [hci0] 
20:14:38.120988
Scanning: Enabled (0x01)
Filter duplicates: Disabled (0x00)
> HCI Event: Command Complete (0x0e) plen 4 
>  #34 [hci0] 
> 20:14:38.121945
  LE Set Scan Enable (0x08|0x000c) ncmd 1
Status: Command Disallowed (0x0c)

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

Title:
  hcitool lescan says 'Set scan parameters failed: Input/output error'

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  Hi,

  after some testing with Ubuntu 20.04 beta I couldn't get hcitool
  lescan working. I get the following error:

  hcitool lescan
  Set scan parameters failed: Input/output error

  Bluetooth hardware: 
  hci0:   Type: Primary  Bus: USB
  BD Address: 04:EA:56:21:xx:xx  ACL MTU: 1021:4  SCO MTU: 96:6
  UP RUNNING
  RX bytes:1605 acl:0 sco:0 events:123 errors:0
  TX bytes:5801 acl:0 sco:0 commands:123 errors:0
  Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
  Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
  Link policy: RSWITCH SNIFF
  Link mode: SLAVE ACCEPT
  Name: 'xx'
  Class: 0x200104
  Service Classes: Audio
  Device Class: Computer, Desktop workstation
  HCI Version: 5.1 (0xa)  Revision: 0x100
  LMP Version: 5.1 (0xa)  Subversion: 0x100
  Manufacturer: Intel Corp. (2)

  It is not hardware related, since I get the same error with a USB
  bluetooth dongle:

  hcitool -i hci1 lescan
  Set scan parameters failed: Input/output error

  hcitool scan is working fine on both devices; bluetoothctl is also working 
and able to find ble devices.
  I would normally 

[Touch-packages] [Bug 203997] Re: new upstream release 1.05 with security fix

[Bug Watch Updater]

Launchpad has imported 14 comments from the remote bug at
https://bugs.gentoo.org/show_bug.cgi?id=213820.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2008-03-18T12:30:45+00:00 hanno wrote:

CERT-FI did a fuzzing tool test and discovered issues in various
archiving tools.

bzip2 is vulnerable, fixed in 1.0.5. This code is probably bundled in
some other packages.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bzip2/+bug/203997/comments/0


On 2008-03-18T13:38:19+00:00 vapier wrote:

ive added 1.0.5 to the tree ... now if only they didnt screw up the
packaging of it ...

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bzip2/+bug/203997/comments/1


On 2008-03-18T13:47:14+00:00 rbu wrote:

Arches, please test and mark stable:
=app-arch/bzip2-1.0.5
Target keywords : "alpha amd64 arm hppa ia64 m68k mips ppc ppc64 release s390 
sh sparc x86"


Reply at: https://bugs.launchpad.net/ubuntu/+source/bzip2/+bug/203997/comments/2


On 2008-03-18T14:16:44+00:00 rbu wrote:

Created attachment 146488
bzip2-CERT-FI-20469.patch

Just for reference, the patch.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bzip2/+bug/203997/comments/3


On 2008-03-18T16:31:22+00:00 fmccor wrote:

Sparc stable.  All tests pass, it works on my files, and portage can use
it.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bzip2/+bug/203997/comments/4


On 2008-03-18T17:17:26+00:00 jer wrote:

(In reply to comment #4)
> Sparc stable.  All tests pass, it works on my files, and portage can use it.

That's odd. Ferris forgot to mark the ebuild. So er, stable for HPPA and
SPARC then. :)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bzip2/+bug/203997/comments/5


On 2008-03-18T18:28:17+00:00 dertobi123 wrote:

ppc stable

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bzip2/+bug/203997/comments/6


On 2008-03-18T18:30:32+00:00 armin76 wrote:

alpha/ia64/x86 stable

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bzip2/+bug/203997/comments/7


On 2008-03-19T00:34:46+00:00 beandog wrote:

amd64 stable

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bzip2/+bug/203997/comments/8


On 2008-03-19T01:58:29+00:00 rhill wrote:

there's no need to cc mips on security stabilization bugs.  we're ~arch
only.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bzip2/+bug/203997/comments/9


On 2008-03-19T19:00:37+00:00 corsair wrote:

ppc64 stable

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bzip2/+bug/203997/comments/11


On 2008-03-19T20:53:31+00:00 pva wrote:

Fixed in release snapshot.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bzip2/+bug/203997/comments/13


On 2008-03-21T02:17:53+00:00 rbu wrote:

request filed

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bzip2/+bug/203997/comments/14


On 2008-04-02T21:31:43+00:00 py wrote:

GLSA 200804-02

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bzip2/+bug/203997/comments/16

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

Title:
  new upstream release 1.05 with security fix

Status in bzip2 package in Ubuntu:
  Fix Released
Status in bzip2 package in Arch Linux:
  Fix Released
Status in bzip2 package in Gentoo Linux:
  Fix Released
Status in bzip2 package in Mandriva:
  Unknown

Bug description:
  Binary package hint: bzip2

  The current version is 1.0.5, released 17 March 2008.

  Version 1.0.5 removes a potential security vulnerability (CERT-FI
  20469 as it applies to bzip2) in versions 1.0.4 and earlier, so all
  users are recommended to upgrade immediately.

  https://www.cert.fi/haavoittuvuudet/joint-advisory-archive-
  formats.html

  CHANGES:
  1.0.5 (10 Dec 07)
  ~
  Security fix only.  Fixes CERT-FI 20469 as it applies 

[Touch-packages] [Bug 218652] Re: CVE-2008-1686: Multiple speex implementations insufficient boundary checks

[Bug Watch Updater]

Launchpad has imported 18 comments from the remote bug at
https://bugs.gentoo.org/show_bug.cgi?id=217715.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2008-04-14T20:01:33+00:00 rbu wrote:

xiph's (lib)speex 1.2 beta 3.2 has been tagged that fixes CVE-2008-1686
directly in the the speex_header_to_packet() function which applications
use. Sanitations inside applications are therefore unnecessary.

Patch:
  https://trac.xiph.org/changeset/14701

Reply at:
https://bugs.launchpad.net/ubuntu/+source/speex/+bug/218652/comments/11


On 2008-04-15T09:35:05+00:00 ssuominen wrote:

And we have it in Portage now,

*speex-1.2_beta3_p2 (15 Apr 2008)

  15 Apr 2008; Samuli Suominen  -speex-1.1.7.ebuild,
  +speex-1.2_beta3_p2.ebuild:
  Version bump.


Reply at: 
https://bugs.launchpad.net/ubuntu/+source/speex/+bug/218652/comments/13


On 2008-04-15T10:38:43+00:00 rbu wrote:

Arch Security Liaisons, please test and mark stable:
=media-libs/speex-1.2_beta3_p2
Target keywords : "alpha amd64 arm hppa ia64 ppc ppc64 release sh sparc x86"

CC'ing current Liaisons:
   alpha : ferdy
   amd64 : welp
hppa : jer
 ppc : dertobi123
   ppc64 : corsair
 release : pva
   sparc : fmccor
 x86 : opfer


Reply at: 
https://bugs.launchpad.net/ubuntu/+source/speex/+bug/218652/comments/14


On 2008-04-15T13:17:57+00:00 armin76 wrote:

Adding Tobias for alpha

Reply at:
https://bugs.launchpad.net/ubuntu/+source/speex/+bug/218652/comments/15


On 2008-04-15T13:46:01+00:00 fmccor wrote:

Sparc stable (tested with {.wav}).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/speex/+bug/218652/comments/16


On 2008-04-15T16:17:10+00:00 corsair wrote:

ppc64 stable

Reply at:
https://bugs.launchpad.net/ubuntu/+source/speex/+bug/218652/comments/18


On 2008-04-15T16:51:29+00:00 ssuominen wrote:

amd64 stable, tested by playing with ogg123 (vorbis-tools using USE speex) and
converting .spx to .wav and back to .spx using speexdec and speexenc
also tested by an AT (VQuickSilver, Freenode), thanks to him


Reply at:
https://bugs.launchpad.net/ubuntu/+source/speex/+bug/218652/comments/19


On 2008-04-15T20:00:45+00:00 klausman wrote:

Stable for alpha.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/speex/+bug/218652/comments/21


On 2008-04-15T21:53:19+00:00 rbu wrote:

*** Bug 217820 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/speex/+bug/218652/comments/22


On 2008-04-16T19:08:12+00:00 dertobi123 wrote:

ppc stable

Reply at:
https://bugs.launchpad.net/ubuntu/+source/speex/+bug/218652/comments/23


On 2008-04-17T01:04:10+00:00 maekke wrote:

x86 stable

Reply at:
https://bugs.launchpad.net/ubuntu/+source/speex/+bug/218652/comments/24


On 2008-04-17T09:42:39+00:00 vorlon wrote:

now public via http://www.ocert.org/advisories/ocert-2008-004.html

Reply at:
https://bugs.launchpad.net/ubuntu/+source/speex/+bug/218652/comments/29


On 2008-04-17T09:59:20+00:00 vorlon wrote:

removing arch security liaisons, adding missing arches, adding sound herd
hope I didn't forget to remove/add anyone

glsa request filed

Reply at:
https://bugs.launchpad.net/ubuntu/+source/speex/+bug/218652/comments/30


On 2008-04-17T10:02:30+00:00 vorlon wrote:

really removing this time

Reply at:
https://bugs.launchpad.net/ubuntu/+source/speex/+bug/218652/comments/31


On 2008-04-17T10:18:10+00:00 armin76 wrote:

ia64 stable

Reply at:
https://bugs.launchpad.net/ubuntu/+source/speex/+bug/218652/comments/32


On 2008-04-17T10:53:48+00:00 klausman wrote:

Removing myself since I stood in for ferdy as sec liaison for Alpha.

Reply at:

[Touch-packages] [Bug 1871465] [NEW] ssh_config(5) contains outdated information

[iBug]

Public bug reported:

The release of OpenSSH 8.2 has removed `ssh-rsa` from the default list
of CACertificateAlgorithms. However the latest `openssh-client` still
ships the man page for ssh_config(5) that contains the following
description:

 CASignatureAlgorithms
 Specifies which algorithms are allowed for signing of certificates 
 by certificate authorities (CAs).  The default is:

   ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,
   ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa

 ssh(1) will not accept host certificates signed using algorithms 
 other than those specified.

As far as I am concerned, `ssh-rsa` should be dropped from the list so
as to match the behavior of ssh(1).

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


** Tags: manpage

** Description changed:

  The release of OpenSSH 8.2 has removed `ssh-rsa` from the default list
  of CACertificateAlgorithms. However the latest `openssh-client` still
  ships the man page for ssh_config(5) that contains the following
  description:
  
-  CASignatureAlgorithms
-  Specifies which algorithms are allowed for signing of 
certificates by certificate authorities (CAs).  The default is:
+  CASignatureAlgorithms
+  Specifies which algorithms are allowed for signing of 
certificates 
+  by certificate authorities (CAs).  The default is:
  
-
ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,
-ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa
+    
ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,
+    ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa
  
-  ssh(1) will not accept host certificates signed using
- algorithms other than those specified.
+  ssh(1) will not accept host certificates signed using algorithms 
+  other than those specified.
  
  As far as I am concerned, `ssh-rsa` should be dropped from the list so
  as to match the behavior of ssh(1).

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

Title:
  ssh_config(5) contains outdated information

Status in openssh package in Ubuntu:
  New

Bug description:
  The release of OpenSSH 8.2 has removed `ssh-rsa` from the default list
  of CACertificateAlgorithms. However the latest `openssh-client` still
  ships the man page for ssh_config(5) that contains the following
  description:

   CASignatureAlgorithms
   Specifies which algorithms are allowed for signing of 
certificates 
   by certificate authorities (CAs).  The default is:

     
ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,
     ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa

   ssh(1) will not accept host certificates signed using algorithms 
   other than those specified.

  As far as I am concerned, `ssh-rsa` should be dropped from the list so
  as to match the behavior of ssh(1).

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

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

[Touch-packages] [Bug 1871458] [NEW] No display signal if NVIDIA driver and display scaling is active

[Erik Steiner]

Public bug reported:

I recently installed Ubuntu 20.04 (20200402) with LVM encryption and automatic 
logon.
So I enter my encryption password and after the motherboards boot logo it will 
login automatically to desktop. I also chose the additional drivers and so 
nvidia-driver-440.
Everything seems to be OK until I select a scaling above 100% (e.g. 200%) in 
settings. Next reboot, I enter my encryption password. When the automatic logon 
process should happen, the monitor turns off and says that no display signal is 
available.

Currently I was able to return to a working setup by pressing CTRL + ALT + F4, 
login and enter the following commands to remove nvidia-driver and use XORG 
instead:
sudo apt purge nvidia-driver-440
sudo apt autoremove
sudo reboot

I am pretty sure that the issue will occur again, if I choose NVIDIA
driver again.

Any thoughts?

EDIT: On Ubuntu 19.04 I had a similar bug: If I started my PC and the
monitor was not turned on, the monitor reported no signal available
after turning it on. I was not able to see the boot-up field to enter my
encryption password. Unfortunately I didn't test, if I were able to
enter my password and logon anyway. Workaround was to turn the monitor
on, before starting the PC.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr  7 19:31:50 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd GP102 [GeForce GTX 1080 Ti] 
[1458:3762]
InstallationDate: Installed on 2020-04-05 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
MachineType: Micro-Star International Co., Ltd. MS-7B45
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/03/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A.80
dmi.board.asset.tag: Default string
dmi.board.name: Z370 GAMING PRO CARBON (MS-7B45)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 2.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 2.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.80:bd04/03/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B45:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ370GAMINGPROCARBON(MS-7B45):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
dmi.product.family: Default string
dmi.product.name: MS-7B45
dmi.product.sku: Default string
dmi.product.version: 2.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

** Description changed:

  I recently installed Ubuntu 20.04 (20200402) with LVM encryption and 
automatic logon.
  So I enter my encryption password and after the motherboards boot logo it 
will login automatically to desktop. I also chose the additional drivers and so 
nvidia-driver-440.
  Everything seems to be OK until I select a scaling above 100% (e.g. 200%) in 
settings. Next reboot, I enter my encryption password. When the automatic logon 
process should happen, the monitor turns off and says that no display signal is 
available.
  
  Currently I was able to return to a working setup by pressing CTRL + ALT + 
F4, login and enter the following commands to remove nvidia-driver and use XORG 
instead:
  sudo apt purge nvidia-driver-440
  sudo apt autoremove
  sudo reboot
  
  I am pretty sure that the issue will occur again, if I choose NVIDIA
  driver again.
  
  Any thoughts?
+ 
+ EDIT: On Ubuntu 19.04 I had a similar bug: If I started my PC and the
+ monitor was not turned on, the monitor reported no signal available
+ after turning it on. I was not able to see the boot-up field to enter my
+ encryption password. 

[Touch-packages] [Bug 1871434] Re: apport general-hooks/powerpc.py crashes on ppc64el

[Dimitri John Ledkov]

** Changed in: apport (Ubuntu)
   Importance: Undecided => Critical

** Branch linked: lp:~xnox/ubuntu/focal/apport/apport-on-powerpc-
crashes-subiquity-during-crash-reporting

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

Title:
  apport general-hooks/powerpc.py crashes on ppc64el

Status in apport package in Ubuntu:
  New

Bug description:
  During subiquity, apport seems to be crashing

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

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

[Touch-packages] [Bug 1871439] Re: subiquity should detect when apport crashes collecting crash report

[Dimitri John Ledkov]

Or like we should disable subiquity crash-handler, during apport crash
reporting?

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

Title:
  subiquity should detect when apport crashes collecting crash report

Status in subiquity:
  New
Status in apport package in Ubuntu:
  New

Bug description:
  apport i think needs a crash handler, to stop apport crashes, when it
  crahes during crash collection.

  not sure if subiquity can detect that.

  see https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1871434

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

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

[Touch-packages] [Bug 1871451] Re: powerpc segfault on exponential of negative in python

[Jakub Kaczmarzyk]

** Also affects: python3-defaults (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  When calculating the exponential of a negative number in python 3.6 with
  the Ubuntu 18.04 Docker image (ppcle64), I receive a segfault.
  
  ```
- python -c "import math; math.exp(-1)"
+ python3 -c "import math; math.exp(-1)"
  qemu: uncaught target signal 11 (Segmentation fault) - core dumped
  Segmentation fault
  ```
  
  I am running this in Docker on macOS. Here are the steps to reproduce
  the error.
  
  ```
  docker run --rm -it --platform linux/ppc64le ubuntu:18.04
  apt-get update -qq && apt-get install -y -qq python3
  python3 -c "import math; print(math.exp(0))"  # 1.0
  python3 -c "import math; print(math.exp(-0))"  # 1.0
  python3 -c "import math; print(math.exp(1))"  # 2.718281828459045
  python3 -c "import math; print(math.exp(-1))"
  ```
  
  This error does not happen when using the debian:10 or alpine images.
  
  Here is the output of docker version on my machine:
  
  ```
  Client: Docker Engine - Community
-  Version:   19.03.8
-  API version:   1.40
-  Go version:go1.12.17
-  Git commit:afacb8b
-  Built: Wed Mar 11 01:21:11 2020
-  OS/Arch:   darwin/amd64
-  Experimental:  true
+  Version:   19.03.8
+  API version:   1.40
+  Go version:go1.12.17
+  Git commit:afacb8b
+  Built: Wed Mar 11 01:21:11 2020
+  OS/Arch:   darwin/amd64
+  Experimental:  true
  
  Server: Docker Engine - Community
-  Engine:
-   Version:  19.03.8
-   API version:  1.40 (minimum version 1.12)
-   Go version:   go1.12.17
-   Git commit:   afacb8b
-   Built:Wed Mar 11 01:29:16 2020
-   OS/Arch:  linux/amd64
-   Experimental: true
-  containerd:
-   Version:  v1.2.13
-   GitCommit:7ad184331fa3e55e52b890ea95e65ba581ae3429
-  runc:
-   Version:  1.0.0-rc10
-   GitCommit:dc9208a3303feef5b3839f4323d9beb36df0a9dd
-  docker-init:
-   Version:  0.18.0
-   GitCommit:fec3683
+  Engine:
+   Version:  19.03.8
+   API version:  1.40 (minimum version 1.12)
+   Go version:   go1.12.17
+   Git commit:   afacb8b
+   Built:Wed Mar 11 01:29:16 2020
+   OS/Arch:  linux/amd64
+   Experimental: true
+  containerd:
+   Version:  v1.2.13
+   GitCommit:7ad184331fa3e55e52b890ea95e65ba581ae3429
+  runc:
+   Version:  1.0.0-rc10
+   GitCommit:dc9208a3303feef5b3839f4323d9beb36df0a9dd
+  docker-init:
+   Version:  0.18.0
+   GitCommit:fec3683
  ```
  
  Cross-posted to StackOverflow:
  https://stackoverflow.com/questions/61084969/python-segfault-
  calculating-exponential-of-negative-ppc64le

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

Title:
  powerpc segfault on exponential of negative in python

Status in cloud-images:
  New
Status in python3-defaults package in Ubuntu:
  New

Bug description:
  When calculating the exponential of a negative number in python 3.6
  with the Ubuntu 18.04 Docker image (ppcle64), I receive a segfault.

  ```
  python3 -c "import math; math.exp(-1)"
  qemu: uncaught target signal 11 (Segmentation fault) - core dumped
  Segmentation fault
  ```

  I am running this in Docker on macOS. Here are the steps to reproduce
  the error.

  ```
  docker run --rm -it --platform linux/ppc64le ubuntu:18.04
  apt-get update -qq && apt-get install -y -qq python3
  python3 -c "import math; print(math.exp(0))"  # 1.0
  python3 -c "import math; print(math.exp(-0))"  # 1.0
  python3 -c "import math; print(math.exp(1))"  # 2.718281828459045
  python3 -c "import math; print(math.exp(-1))"
  ```

  This error does not happen when using the debian:10 or alpine images.

  Here is the output of docker version on my machine:

  ```
  Client: Docker Engine - Community
   Version:   19.03.8
   API version:   1.40
   Go version:go1.12.17
   Git commit:afacb8b
   Built: Wed Mar 11 01:21:11 2020
   OS/Arch:   darwin/amd64
   Experimental:  true

  Server: Docker Engine - Community
   Engine:
    Version:  19.03.8
    API version:  1.40 (minimum version 1.12)
    Go version:   go1.12.17
    Git commit:   afacb8b
    Built:Wed Mar 11 01:29:16 2020
    OS/Arch:  linux/amd64
    Experimental: true
   containerd:
    Version:  v1.2.13
    GitCommit:7ad184331fa3e55e52b890ea95e65ba581ae3429
   runc:
    Version:  1.0.0-rc10
    GitCommit:dc9208a3303feef5b3839f4323d9beb36df0a9dd
   docker-init:
    Version:  0.18.0
    GitCommit:fec3683
  ```

  Cross-posted to StackOverflow:
  https://stackoverflow.com/questions/61084969/python-segfault-
  

[Touch-packages] [Bug 1871023] Re: json_gvariant_deserialize can fail due to unrelated code setting errno

[Launchpad Bug Tracker]

This bug was fixed in the package json-glib - 1.4.4-2ubuntu2

---
json-glib (1.4.4-2ubuntu2) focal; urgency=medium

  * 
debian/patches/0001-json-gvariant-Stop-string-to-GVariant-conversion-fai.patch:
- Fix JSON to GVariant conversion failing sometimes (LP: #1871023)

 -- Robert Ancell   Tue, 07 Apr 2020
09:50:05 +1200

** Changed in: json-glib (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  json_gvariant_deserialize can fail due to unrelated code setting errno

Status in json-glib package in Ubuntu:
  Fix Released
Status in json-glib source package in Bionic:
  In Progress
Status in json-glib source package in Eoan:
  In Progress
Status in json-glib source package in Focal:
  Fix Released

Bug description:
  [Impact]
  json_gvariant_deserialize can fail due to unrelated code setting errno, this 
is causing snapd-glib to not be able to decode responses from snapd. Fixed in 
https://gitlab.gnome.org/GNOME/json-glib/-/merge_requests/22

  [Test Case]
  1. Run GNOME Software from the command line
  2. Browse to postman

  Expected result:
  Errors are not shown on the command line

  Observed result:
  The following errors are shown on the command line:
  05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed
  05:17:29:0875 GLib g_variant_new_variant: assertion 'value != NULL' failed
  05:17:29:0877 Gs  not GsPlugin error g-io-error-quark:35: Invalid string 
value converting to GVariant
  05:17:29:0877 Gs  not handling error failed for action refine: Invalid string 
value converting to GVariant

  (These errors may not always occur, and is likely racy).

  [Regression Potential]
  Small risk of introducing other bugs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1871023/+subscriptions

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

[Touch-packages] [Bug 1871439] [NEW] subiquity should detect when apport crashes collecting crash report

[Dimitri John Ledkov]

Public bug reported:

apport i think needs a crash handler, to stop apport crashes, when it
crahes during crash collection.

not sure if subiquity can detect that.

see https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1871434

** Affects: subiquity
 Importance: Undecided
 Status: New

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

** Also affects: subiquity
   Importance: Undecided
   Status: New

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

Title:
  subiquity should detect when apport crashes collecting crash report

Status in subiquity:
  New
Status in apport package in Ubuntu:
  New

Bug description:
  apport i think needs a crash handler, to stop apport crashes, when it
  crahes during crash collection.

  not sure if subiquity can detect that.

  see https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1871434

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

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

[Touch-packages] [Bug 1871434] [NEW] apport general-hooks/powerpc.py crashes on ppc64el

[Dimitri John Ledkov]

Public bug reported:

During subiquity, apport seems to be crashing

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


** Tags: ppc64el

** Attachment added: "Screenshot from 2020-04-07 17-00-05.png"
   
https://bugs.launchpad.net/bugs/1871434/+attachment/5348834/+files/Screenshot%20from%202020-04-07%2017-00-05.png

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

Title:
  apport general-hooks/powerpc.py crashes on ppc64el

Status in apport package in Ubuntu:
  New

Bug description:
  During subiquity, apport seems to be crashing

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

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

[Touch-packages] [Bug 1870824] Re: Errors in script /usr/lib/avahi/avahi-daemon-check-dns.sh

[rklemme]

I think the script will still work most of the time so severity is not
too high.

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

Title:
  Errors in script /usr/lib/avahi/avahi-daemon-check-dns.sh

Status in avahi package in Ubuntu:
  New

Bug description:
  In line 42 and 46 Command Substitution is used wrongly because the
  shell expects to execute what it returns.  See attached patch.

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

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

[Touch-packages] [Bug 1871429] [NEW] session of user time out at shutdown/reboot

[elhoir]

Public bug reported:

closing user session always times out at reboot/shutdown

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

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

Title:
  session of user time out at shutdown/reboot

Status in systemd package in Ubuntu:
  New

Bug description:
  closing user session always times out at reboot/shutdown

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

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

[Touch-packages] [Bug 1871417] [NEW] kernel update to 5.3.0-46.38 broke wifi

[Michael]

Public bug reported:

my system updated to 5.3.0-46.38 and now I no longer have wifi. The
driver doesn't seem to be installed since when I go to setup, wifi isn't
an available option.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: network-manager 1.20.4-2ubuntu2.2
ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
Uname: Linux 5.3.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr  7 11:00:53 2020
InstallationDate: Installed on 2019-10-29 (160 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
IpRoute:
 
IwConfig:
 lono wireless extensions.
 
 enp2s0no wireless extensions.
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
 PATH=(custom, user)
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE  TYPE  STATEIP4-CONNECTIVITY  IP6-CONNECTIVITY  DBUS-PATH   
   CONNECTION  CON-UUID  CON-PATH 
 enp2s0  ethernet  unavailable  none  none  
/org/freedesktop/NetworkManager/Devices/2  --  ----   
 lo  loopback  unmanagedunknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --  ----
nmcli-nm:
 RUNNING  VERSION  STATE STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
 running  1.20.4   disconnected  started  none  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug eoan

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

Title:
  kernel update to 5.3.0-46.38 broke wifi

Status in network-manager package in Ubuntu:
  New

Bug description:
  my system updated to 5.3.0-46.38 and now I no longer have wifi. The
  driver doesn't seem to be installed since when I go to setup, wifi
  isn't an available option.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: network-manager 1.20.4-2ubuntu2.2
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 11:00:53 2020
  InstallationDate: Installed on 2019-10-29 (160 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IpRoute:
   
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEIP4-CONNECTIVITY  IP6-CONNECTIVITY  DBUS-PATH 
 CONNECTION  CON-UUID  CON-PATH 
   enp2s0  ethernet  unavailable  none  none  
/org/freedesktop/NetworkManager/Devices/2  --  ----   
   lo  loopback  unmanagedunknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --  ----
  nmcli-nm:
   RUNNING  VERSION  STATE STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.20.4   disconnected  started  none  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1871417/+subscriptions

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

[Touch-packages] [Bug 1871414] Re: Pulseaudio incorrectly detects a headphone being plugged in

[Yosep Perez]

** Package changed: alsa-lib (Ubuntu) => pulseaudio (Ubuntu)

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

Title:
  Pulseaudio incorrectly detects a headphone being plugged in

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Software details:
  Distro: Kubuntu 20.04 Beta
  Kernel: 5.4.0-21-generic
  alsa-base version 1.0.25+dfsg-0ubuntu5
  alsa-utils version 1.2.2-1ubuntu1
  pulseaudio version 1:13.99.1-1ubuntu1

  Hardware details:
  Motherboard: Gigabyte GA-AB350M-D3H
  Audio Codec: Realtek ALC887
  GPU: Nvidia RTX 2060 Super (with the audio output disabled in PulseAudio)

  Regarding the issue:
  Every time I start an audio stream (regardless of the application), I can 
hear interruptions in the sound and when opening alsamixer I can also see the 
interface kind of flickering for a few milliseconds.
  After running pulseaudio with logging enabled for a few seconds (while 
playing music), this pattern can be seen:

  [pulseaudio] sink.c: alsa_output.pci-_0a_00.3.analog-stereo: state: IDLE 
-> RUNNING
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
unplugged
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status no
  D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now 
plugged in
  D: [pulseaudio] device-port.c: Setting port analog-output-headphones to 
status yes

  Note: I've no headphones attached ! Only the line out is connected to
  a 2.1 Speaker

  It seems basically the same bug as this: 
https://bbs.archlinux.org/viewtopic.php?id=147225
  but in my case disabling "module-switch-on-port-available" 

[Touch-packages] [Bug 1871414] [NEW] Pulseaudio incorrectly detects a headphone being plugged in

[Yosep Perez]

Public bug reported:

Software details:
Distro: Kubuntu 20.04 Beta
Kernel: 5.4.0-21-generic
alsa-base version 1.0.25+dfsg-0ubuntu5
alsa-utils version 1.2.2-1ubuntu1
pulseaudio version 1:13.99.1-1ubuntu1

Hardware details:
Motherboard: Gigabyte GA-AB350M-D3H
Audio Codec: Realtek ALC887
GPU: Nvidia RTX 2060 Super (with the audio output disabled in PulseAudio)

Regarding the issue:
Every time I start an audio stream (regardless of the application), I can hear 
interruptions in the sound and when opening alsamixer I can also see the 
interface kind of flickering for a few milliseconds.
After running pulseaudio with logging enabled for a few seconds (while playing 
music), this pattern can be seen:

[pulseaudio] sink.c: alsa_output.pci-_0a_00.3.analog-stereo: state: IDLE -> 
RUNNING
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged 
in
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
yes
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
no
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged 
in
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
yes
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
no
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged 
in
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
yes
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
no
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged 
in
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
yes
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
no
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged 
in
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
yes
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
no
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged 
in
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
yes
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
no
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged 
in
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
yes
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
no
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged 
in
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
yes
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
no
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged 
in
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
yes
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
no
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged 
in
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
yes
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
no
D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged 
in
D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status 
yes

Note: I've no headphones attached ! Only the line out is connected to a
2.1 Speaker

It seems basically the same bug as this: 
https://bbs.archlinux.org/viewtopic.php?id=147225
but in my case disabling "module-switch-on-port-available" doesn't remove the 
audio "artifacts"

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

** Attachment added: "Verbose Logs"
   
https://bugs.launchpad.net/bugs/1871414/+attachment/5348776/+files/pulseverbose.log

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

Title:
  Pulseaudio incorrectly detects a headphone being plugged 

[Touch-packages] [Bug 1848394] Re: software properteries shows "open source" for proprietary nvidia driver

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: software-properties (Ubuntu)
   Status: New => Confirmed

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

Title:
  software properteries shows "open source" for proprietary nvidia
  driver

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  User installed 19.10 and opened software properties. 
  The nvidia binary driver shows as an "open source" driver. It should show 
"proprietary"
  See screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: software-properties-gtk 0.98.5
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 01:23:12 2019
  InstallationDate: Installed on 2019-10-16 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191015)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1848394/+subscriptions

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

[Touch-packages] [Bug 1848394] Re: software properteries shows "open source" for proprietary nvidia driver

[Stefan Pappalardo]

It's the same on Ubuntu 18.04.

$ LANG=C apt-cache policy software-properties-gtk
software-properties-gtk:
  Installed: 0.96.24.32.12
  Candidate: 0.96.24.32.12
  Version table:
 *** 0.96.24.32.12 500
500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main i386 
Packages
100 /var/lib/dpkg/status
 0.96.24.32.1 500
500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
500 http://de.archive.ubuntu.com/ubuntu bionic/main i386 Packages

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.4 LTS
Release:18.04
Codename:   bionic

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

Title:
  software properteries shows "open source" for proprietary nvidia
  driver

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  User installed 19.10 and opened software properties. 
  The nvidia binary driver shows as an "open source" driver. It should show 
"proprietary"
  See screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: software-properties-gtk 0.98.5
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 01:23:12 2019
  InstallationDate: Installed on 2019-10-16 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191015)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1848394/+subscriptions

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

[Touch-packages] [Bug 1871329] Re: No "Select Audio Device" panel when plugging headphones, and no sound output to headphones

[Martin Wimpress]

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

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

Title:
  No "Select Audio Device" panel when plugging headphones, and no sound
  output to headphones

Status in pulseaudio package in Ubuntu:
  New

Bug description:

  
  Summary
  ===

  Internal speakers work as expected, but when plugging headphones
  through the 3.5mm jack, the "Select Audio Device" panel doesn't show
  up (it normally shows up to allow user to select what kind of device
  has been plugged in, be it headphones, microphone or headset). In the
  Sound Settings, the Output Device automatically switches to
  "Headphones - sof-hda-dsp", but no sound can be heard even though the
  vumeter in the Sound Settings moves!

  Steps to reproduce
  ==

  1. Install focal beta
  2. Make sure the sound works as expected using the internal speakers and an 
audio file or Youtube
  3. Plug headphones in jack 3.5mm interface

  Expected Results
  

  - In Sound Settings, the headphones are automatically selected as output 
device
  - In Sound Settings, the vumeter under the Output Device moves according to 
the sound
  - Sound can be heard through the headphones

  
  Actual results
  ==

  - In Sound Settings, the headphones are automatically selected as output 
device (OK)
  - In Sound Settings, the vumeter under the Output Device moves according to 
the sound (OK)
  - No sound can be heard (Not OK)

  Attached are output of `pactl info` and `pactl list` before and after
  plugging headphones, while playing a tune on Bandcamp in Firefox.

  
  Additional Info
  ===

  Ubuntu: 20.04 beta image
  Certified device: 
  system-manufacturer: Dell Inc.
  system-product-name: Vostro 5590
  bios-version: 1.1.0
  CPU: Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:9b41] (rev 02)
  01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:1d13] (rev a1)
  kernel-version: 5.4.0-21-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1768 F pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1768 F...m pulseaudio
   /dev/snd/pcmC0D6c:   pieq   1768 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 16:33:27 2020
  InstallationDate: Installed on 2020-04-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd07/18/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5590
  dmi.product.sku: 095A
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18

[Dan Streetman]

Yep, we will get this fixed - I'll assign Seyeong work with him on it.

** Changed in: network-manager (Ubuntu Focal)
 Assignee: (unassigned) => Seyeong Kim (xtrusia)

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

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Artful:
  Won't Fix
Status in network-manager source package in Disco:
  Won't Fix
Status in network-manager source package in Eoan:
  Won't Fix
Status in network-manager source package in Focal:
  New

Bug description:
  [Impact]

  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill
  block/unblock. Adding a sleep before calling nmcli fixes the issue.

  ppc64el ADT log from failed testcase:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/ppc64el/n/network-
  manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

  
  [Test Case]

  2.1. Download network-manager package source code
  $ apt-get source network-manager

  2.2. Run killswitches-no-urfkill testcase
  $ cd network-manager-1.8.4
  $ sudo ./debian/tests/killswitches-no-urfkill

  
  [Regression Potential]

  No regression potential. The fix touches only the testcase shipped
  with the source package and it doesn't change the binary package. The
  sleep time added is very small, so no possibility of causing testcase
  timeout.

  
  [Other Info]

  On ppc64el architecture, it was observed that a fix for systemd is
  also needed (see bug 1734908) for the testcase to be successful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1733321/+subscriptions

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

[Touch-packages] [Bug 1843982] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user()

[Martin Wimpress]

** Changed in: accountsservice (Ubuntu)
 Assignee: (unassigned) => Iain Lane (laney)

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

Title:
  Various programs crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from update_user()

Status in accountsservice:
  New
Status in accountsservice package in Ubuntu:
  Triaged
Status in accountsservice package in Debian:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 10:29:16 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-05-24 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () 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
   ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Touch-packages] [Bug 1870508] Re: ubiquity crashed with SIGSEGV in g_type_check_instance_is_a()

[Martin Wimpress]

** Changed in: atk1.0 (Ubuntu)
 Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson)

** Changed in: ubiquity (Ubuntu)
 Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson)

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

Title:
  ubiquity crashed with SIGSEGV in g_type_check_instance_is_a()

Status in atk1.0 package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed

Bug description:
  == Test Case ==
  1. Boot to ubiquity-dm
  2. Enable the screenreader (Alt+Super+S)
  3. Select "Install Ubuntu"
  4. Proceed with all the steps of the installer

  = Actual Result = 
  During installation, when the slideshow is running, this crash occurs.

  
  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  3 10:55:58 2020
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  ExecutableTimestamp: 1585729537
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet 
splash --- maybe-ubiquity
  InterpreterPath: /usr/bin/python3.8
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity --greeter --only
  ProcCwd: /
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonDetails: N/A
  SegvAnalysis:
   Segfault happened at: 0x7fbd15f8f16a :   
mov%rax,-0x20(%rsp)
   PC (0x7fbd15f8f16a) ok
   source "%rax" ok
   destination "-0x20(%rsp)" (0x7ffe329d3ff0) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: ubiquity
  StacktraceTop:
   g_type_check_instance_is_a () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   atk_component_get_extents () from /lib/x86_64-linux-gnu/libatk-1.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   atk_component_get_extents () from /lib/x86_64-linux-gnu/libatk-1.0.so.0
   atk_component_get_extents () from /lib/x86_64-linux-gnu/libatk-1.0.so.0
  Title: ubiquity crashed with SIGSEGV in g_type_check_instance_is_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/atk1.0/+bug/1870508/+subscriptions

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

[Touch-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18

[Sebastien Bacher]

Dan, Seyeong, is one of you commited to work on a proper fix there? Can
you take assignement of the bug? It would be nice to see the problem
resolved and without a slap hacking if possible :-)

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

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Artful:
  Won't Fix
Status in network-manager source package in Disco:
  Won't Fix
Status in network-manager source package in Eoan:
  Won't Fix
Status in network-manager source package in Focal:
  New

Bug description:
  [Impact]

  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill
  block/unblock. Adding a sleep before calling nmcli fixes the issue.

  ppc64el ADT log from failed testcase:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/ppc64el/n/network-
  manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

  
  [Test Case]

  2.1. Download network-manager package source code
  $ apt-get source network-manager

  2.2. Run killswitches-no-urfkill testcase
  $ cd network-manager-1.8.4
  $ sudo ./debian/tests/killswitches-no-urfkill

  
  [Regression Potential]

  No regression potential. The fix touches only the testcase shipped
  with the source package and it doesn't change the binary package. The
  sleep time added is very small, so no possibility of causing testcase
  timeout.

  
  [Other Info]

  On ppc64el architecture, it was observed that a fix for systemd is
  also needed (see bug 1734908) for the testcase to be successful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1733321/+subscriptions

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

[Touch-packages] [Bug 1870729] Re: DHCP Server regularly killed code=killed, status=6/ABRT

[Launchpad Bug Tracker]

This bug was fixed in the package isc-dhcp - 4.4.1-2.1ubuntu4

---
isc-dhcp (4.4.1-2.1ubuntu4) focal; urgency=medium

  * debian/apparmor/usr.sbin.dhcpd: allow owner read on /proc/*/comm and
/proc/*/task/*/comm (LP: #1870729)

 -- Jamie Strandboge   Mon, 06 Apr 2020 21:58:35 +

** Changed in: isc-dhcp (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  DHCP Server regularly killed code=killed, status=6/ABRT

Status in isc-dhcp package in Ubuntu:
  Fix Released

Bug description:
  On Ubuntu 20.04 The idc-dhcp- server version is
  isc-dhcp-server:
Installed: (none)
Candidate: 4.4.1-2.1ubuntu3
Version table:
   4.4.1-2.1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  
  The DHCP server is being regularly killed, when searching google the  bug 
looks very similar to an older bug regarding accessing a lease file, that was 
fixed year ago. As a temporary fix in systemd I have enabled a restart every 
time the main process fails. The error got worse when i start to run a pair of 
dhcp servers syncing state between each other

  
  I regularly see the following in the syslog

  Apr  4 00:04:55 gw sh[1500]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
  Apr  4 00:04:55 gw sh[1500]: #0 0x7f36befeda4a in ??
  Apr  4 00:04:55 gw sh[1500]: #1 0x7f36befed980 in ??
  Apr  4 00:04:55 gw sh[1500]: #2 0x7f36bf0297e1 in ??
  Apr  4 00:04:55 gw sh[1500]: #3 0x7f36bedd0609 in ??
  Apr  4 00:04:55 gw sh[1500]: #4 0x7f36bef0c153 in ??
  Apr  4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Main process exited, 
code=killed, status=6/ABRT
  Apr  4 00:04:55 gw systemd[1]: isc-dhcp-server.service: Failed with result 
'signal'.
  Apr  4 00:05:00 gw systemd[1]: isc-dhcp-server.service: Scheduled restart 
job, restart counter is at 3.
  Apr  4 00:05:00 gw systemd[1]: Stopped ISC DHCP IPv4 server.
  Apr  4 00:05:00 gw systemd[1]: Started ISC DHCP IPv4 server.
  Apr  4 00:05:00 gw kernel: [ 3508.161248] audit: type=1400 
audit(1585958700.678:46): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2068/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw dhcpd[2049]: Internet Systems Consortium DHCP Server 4.4.1
  Apr  4 00:05:00 gw sh[2049]: Internet Systems Consortium DHCP Server 4.4.1
  Apr  4 00:05:00 gw sh[2049]: Copyright 2004-2018 Internet Systems Consortium.
  Apr  4 00:05:00 gw sh[2049]: All rights reserved.
  Apr  4 00:05:00 gw sh[2049]: For info, please visit 
https://www.isc.org/software/dhcp/
  Apr  4 00:05:00 gw dhcpd[2049]: Copyright 2004-2018 Internet Systems 
Consortium.
  Apr  4 00:05:00 gw dhcpd[2049]: All rights reserved.
  Apr  4 00:05:00 gw dhcpd[2049]: For info, please visit 
https://www.isc.org/software/dhcp/
  Apr  4 00:05:00 gw kernel: [ 3508.161561] audit: type=1400 
audit(1585958700.678:47): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2069/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw kernel: [ 3508.161563] audit: type=1400 
audit(1585958700.682:48): apparmor="DENIED" operation="open" 
profile="/usr/sbin/dhcpd" name="/proc/2049/task/2070/comm" pid=2049 
comm="dhcpd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  Apr  4 00:05:00 gw dhcpd[2049]: Config file: /etc/dhcp/dhcpd.conf
  Apr  4 00:05:00 gw sh[2049]: Config file: /etc/dhcp/dhcpd.conf
  Apr  4 00:05:00 gw sh[2049]: Database file: /var/lib/dhcp/dhcpd.leases
  Apr  4 00:05:00 gw sh[2049]: PID file: /run/dhcp-server/dhcpd.pid
  Apr  4 00:05:00 gw dhcpd[2049]: Database file: /var/lib/dhcp/dhcpd.leases
  Apr  4 00:05:00 gw dhcpd[2049]: PID file: /run/dhcp-server/dhcpd.pid
  Apr  4 00:05:00 gw dhcpd[2049]: Wrote 0 deleted host decls to leases file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1870729/+subscriptions

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

[Touch-packages] [Bug 1871394] [NEW] no dual head video with 2 on board sources: ast2500 and i915

[Chris Sheppard]

Public bug reported:

I am creating a new computer platforms.  It provides two video sources:
an Intel i915 DisplayPort and an AST2500 VGA.  The i915 also provides
HDMI, but it is disconnected/disabled.

EXPECTED BEHAVIOR: Video is presented through the AST2500 to VGA and the
i915 to DisplayPort, mergine the displays to a unified layout when a
layout is provided to xorg.

ACTUAL BEHAVIOR: Both monitors present a purple background at login, but
the VGA monitor is quickly disabled at login.

When I had a problem with these video sources under Windows the Intel
team provided me a "Switchable Graphics" BIOS module.  It resolved the
issue there.  My BIOS settings define "Switchable Graphics" as the
Primary Display.

When I set the BIOS to use the ast2500 as the only display source the
system works as intended.  I mention this to confirm the ast2500 and
kernel can display video even if the ast2500 won't display video
alongside the i915.

Description:Ubuntu 18.04.4 LTS
Release:18.04

xorg:
  Installed: 1:7.7+19ubuntu7.1
  Candidate: 1:7.7+19ubuntu7.1
  Version table:
 *** 1:7.7+19ubuntu7.1 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1:7.7+19ubuntu7 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

test@test:~$ modinfo ast | grep -version
filename:   /lib/modules/5.3.0-46-generic/kernel/drivers/gpu/drm/ast/ast.ko
license:GPL and additional rights
description:AST
author: Dave Airlie
firmware:   ast_dp501_fw.bin
alias:  pci:v1A03d2010sv*sd*bc03sc*i*
alias:  pci:v1A03d2000sv*sd*bc03sc*i*
depends:drm,drm_kms_helper,drm_vram_helper,i2c-algo-bit
retpoline:  Y
intree: Y
name:   ast
vermagic:   5.3.0-46-generic SMP mod_unload 
signat: PKCS#7
signer: 
sig_key:
sig_hashalgo:   md4
parm:   modeset:Disable/Enable modesetting (int)

test@test:~$ xrandr --listproviders
Providers: number : 2
Provider 0: id: 0x6e cap: 0x9, Source Output, Sink Offload crtcs: 3 outputs: 2 
associated providers: 0 name:modesetting
Provider 1: id: 0x41 cap: 0x0 crtcs: 1 outputs: 1 associated providers: 0 
name:modesetting

Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
DP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 
496mm x 292mm
   1920x1080 60.00*+
   1680x1050 59.95  
   1600x900  60.00  
   1280x1024 60.02  
   1440x900  59.89  
   1280x800  59.81  
   1280x720  60.00  
   1024x768  60.00  
   800x600   60.32  
   640x480   59.94  
   720x400   70.08  
HDMI-1 disconnected (normal left inverted right x axis y axis)

test@test:~$ sudo lshw -C video
[sudo] password for test: 
  *-display 
   description: VGA compatible controller
   product: Intel Corporation
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 02
   width: 64 bits
   clock: 33MHz
   capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
   configuration: driver=i915 latency=0
   resources: irq:152 memory:9000-90ff memory:8000-8fff 
ioport:6000(size=64) memory:c-d
  *-display
   description: VGA compatible controller
   product: ASPEED Graphics Family
   vendor: ASPEED Technology, Inc.
   physical id: 0
   bus info: pci@:04:00.0
   version: 41
   width: 32 bits
   clock: 33MHz
   capabilities: pm msi vga_controller cap_list
   configuration: driver=ast latency=0
   resources: irq:18 memory:9100-91ff memory:9200-9201 
ioport:4000(size=128)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-46-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr  7 09:02:34 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Device [8086:3e9a] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation Device [8086:2212]
 ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 41) (prog-if 
00 [VGA controller])
   Subsystem: ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000]
InstallationDate: Installed on 2020-04-06 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: Trenton Systems Inc. MXT8287 00
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 

[Touch-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18

[Martin Wimpress]

** Changed in: network-manager (Ubuntu Eoan)
   Status: New => Won't Fix

** Tags removed: artful

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

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Artful:
  Won't Fix
Status in network-manager source package in Disco:
  Won't Fix
Status in network-manager source package in Eoan:
  Won't Fix
Status in network-manager source package in Focal:
  New

Bug description:
  [Impact]

  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill
  block/unblock. Adding a sleep before calling nmcli fixes the issue.

  ppc64el ADT log from failed testcase:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/ppc64el/n/network-
  manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

  
  [Test Case]

  2.1. Download network-manager package source code
  $ apt-get source network-manager

  2.2. Run killswitches-no-urfkill testcase
  $ cd network-manager-1.8.4
  $ sudo ./debian/tests/killswitches-no-urfkill

  
  [Regression Potential]

  No regression potential. The fix touches only the testcase shipped
  with the source package and it doesn't change the binary package. The
  sleep time added is very small, so no possibility of causing testcase
  timeout.

  
  [Other Info]

  On ppc64el architecture, it was observed that a fix for systemd is
  also needed (see bug 1734908) for the testcase to be successful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1733321/+subscriptions

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

[Touch-packages] [Bug 1868988] Stacktrace.txt

[Apport retracing service]

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1868988/+attachment/5348637/+files/Stacktrace.txt

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

Title:
  apt assert failure: malloc(): mismatching next->prev_size (unsorted)

Status in apt package in Ubuntu:
  New

Bug description:
  libwxbase3.0-0v5 libwxgtk3.0-gtk3-0v5

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.0
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AssertionMessage: malloc(): mismatching next->prev_size (unsorted)
  Date: Wed Mar 25 14:19:48 2020
  ExecutablePath: /usr/bin/apt
  InstallationDate: Installed on 2020-03-17 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  ProcCmdline: apt upgrade
  Signal: 6
  SourcePackage: apt
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5e92ba0285 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7f5e92ba2aa0 "malloc(): mismatching 
next->prev_size (unsorted)") at malloc.c:5347
   _int_malloc (av=av@entry=0x7f5e92bd1b80 , bytes=bytes@entry=128) 
at malloc.c:3741
   __GI___libc_malloc (bytes=128) at malloc.c:3058
   operator new(unsigned long) () from /lib/x86_64-linux-gnu/libstdc++.so.6
  Title: apt assert failure: malloc(): mismatching next->prev_size (unsorted)
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  separator:

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

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

[Touch-packages] [Bug 1868988] ThreadStacktrace.txt

[Apport retracing service]

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1868988/+attachment/5348639/+files/ThreadStacktrace.txt

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1868988/+attachment/5341414/+files/CoreDump.gz

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

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

Title:
  apt assert failure: malloc(): mismatching next->prev_size (unsorted)

Status in apt package in Ubuntu:
  New

Bug description:
  libwxbase3.0-0v5 libwxgtk3.0-gtk3-0v5

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.0
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AssertionMessage: malloc(): mismatching next->prev_size (unsorted)
  Date: Wed Mar 25 14:19:48 2020
  ExecutablePath: /usr/bin/apt
  InstallationDate: Installed on 2020-03-17 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  ProcCmdline: apt upgrade
  Signal: 6
  SourcePackage: apt
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5e92ba0285 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7f5e92ba2aa0 "malloc(): mismatching 
next->prev_size (unsorted)") at malloc.c:5347
   _int_malloc (av=av@entry=0x7f5e92bd1b80 , bytes=bytes@entry=128) 
at malloc.c:3741
   __GI___libc_malloc (bytes=128) at malloc.c:3058
   operator new(unsigned long) () from /lib/x86_64-linux-gnu/libstdc++.so.6
  Title: apt assert failure: malloc(): mismatching next->prev_size (unsorted)
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  separator:

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

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

[Touch-packages] [Bug 1868988] apt assert failure: malloc(): mismatching next->prev_size (unsorted)

[Apport retracing service]

StacktraceTop:
 __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5e92ba0285 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
 malloc_printerr (str=str@entry=0x7f5e92ba2aa0 "malloc(): mismatching 
next->prev_size (unsorted)") at malloc.c:5347
 _int_malloc (av=av@entry=0x7f5e92bd1b80 , bytes=bytes@entry=128) 
at malloc.c:3741
 __GI___libc_malloc (bytes=128) at malloc.c:3058
 operator new(unsigned long) () from /srv/vms/apport-sandbox-dir/Ubuntu 
20.04/amd64/report-sandbox/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.28

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

Title:
  apt assert failure: malloc(): mismatching next->prev_size (unsorted)

Status in apt package in Ubuntu:
  New

Bug description:
  libwxbase3.0-0v5 libwxgtk3.0-gtk3-0v5

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.0
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AssertionMessage: malloc(): mismatching next->prev_size (unsorted)
  Date: Wed Mar 25 14:19:48 2020
  ExecutablePath: /usr/bin/apt
  InstallationDate: Installed on 2020-03-17 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  ProcCmdline: apt upgrade
  Signal: 6
  SourcePackage: apt
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5e92ba0285 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7f5e92ba2aa0 "malloc(): mismatching 
next->prev_size (unsorted)") at malloc.c:5347
   _int_malloc (av=av@entry=0x7f5e92bd1b80 , bytes=bytes@entry=128) 
at malloc.c:3741
   __GI___libc_malloc (bytes=128) at malloc.c:3058
   operator new(unsigned long) () from /lib/x86_64-linux-gnu/libstdc++.so.6
  Title: apt assert failure: malloc(): mismatching next->prev_size (unsorted)
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  separator:

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

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

[Touch-packages] [Bug 1868988] Re: apt assert failure: malloc(): mismatching next->prev_size (unsorted)

[Brian Murray]

** Tags removed: apport-failed-retrace

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

Title:
  apt assert failure: malloc(): mismatching next->prev_size (unsorted)

Status in apt package in Ubuntu:
  New

Bug description:
  libwxbase3.0-0v5 libwxgtk3.0-gtk3-0v5

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.0
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AssertionMessage: malloc(): mismatching next->prev_size (unsorted)
  Date: Wed Mar 25 14:19:48 2020
  ExecutablePath: /usr/bin/apt
  InstallationDate: Installed on 2020-03-17 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  ProcCmdline: apt upgrade
  Signal: 6
  SourcePackage: apt
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5e92ba0285 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7f5e92ba2aa0 "malloc(): mismatching 
next->prev_size (unsorted)") at malloc.c:5347
   _int_malloc (av=av@entry=0x7f5e92bd1b80 , bytes=bytes@entry=128) 
at malloc.c:3741
   __GI___libc_malloc (bytes=128) at malloc.c:3058
   operator new(unsigned long) () from /lib/x86_64-linux-gnu/libstdc++.so.6
  Title: apt assert failure: malloc(): mismatching next->prev_size (unsorted)
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  separator:

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

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

[Touch-packages] [Bug 1868988] StacktraceSource.txt

[Apport retracing service]

** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1868988/+attachment/5348638/+files/StacktraceSource.txt

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

Title:
  apt assert failure: malloc(): mismatching next->prev_size (unsorted)

Status in apt package in Ubuntu:
  New

Bug description:
  libwxbase3.0-0v5 libwxgtk3.0-gtk3-0v5

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.0
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AssertionMessage: malloc(): mismatching next->prev_size (unsorted)
  Date: Wed Mar 25 14:19:48 2020
  ExecutablePath: /usr/bin/apt
  InstallationDate: Installed on 2020-03-17 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  ProcCmdline: apt upgrade
  Signal: 6
  SourcePackage: apt
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5e92ba0285 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7f5e92ba2aa0 "malloc(): mismatching 
next->prev_size (unsorted)") at malloc.c:5347
   _int_malloc (av=av@entry=0x7f5e92bd1b80 , bytes=bytes@entry=128) 
at malloc.c:3741
   __GI___libc_malloc (bytes=128) at malloc.c:3058
   operator new(unsigned long) () from /lib/x86_64-linux-gnu/libstdc++.so.6
  Title: apt assert failure: malloc(): mismatching next->prev_size (unsorted)
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  separator:

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

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

[Touch-packages] [Bug 1871391] [NEW] sound output dont change

[Otávio Schwanck dos Santos]

Public bug reported:

Even with right output selected, the sound plays on the notebook output.

I've tried restart the system, it dont change.  If i test the sound on
the configs, i hear the sound right (on my phones).  But on spotify \
chrome, the sound plays on notebook output.

https://imgur.com/a/9SMeTYA

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu24
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  otavio154337 F pulseaudio
 /dev/snd/controlC0:  otavio154337 F pulseaudio
 /dev/snd/pcmC0D0c:   otavio154337 F...m pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr  7 14:26:53 2020
InstallationDate: Installed on 2020-02-27 (40 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to focal on 2020-04-06 (0 days ago)
dmi.bios.date: 11/08/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 9VCN15WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R33126 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Legion Y530-15ICH-1060
dmi.modalias: 
dmi:bvnLENOVO:bvr9VCN15WW:bd11/08/2018:svnLENOVO:pn81M7:pvrLenovoLegionY530-15ICH-1060:rvnLENOVO:rnLNVNB161216:rvrSDK0R33126WIN:cvnLENOVO:ct10:cvrLenovoLegionY530-15ICH-1060:
dmi.product.family: Legion Y530-15ICH-1060
dmi.product.name: 81M7
dmi.product.sku: LENOVO_MT_81M7_BU_idea_FM_Legion Y530-15ICH-1060
dmi.product.version: Lenovo Legion Y530-15ICH-1060
dmi.sys.vendor: LENOVO

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

Title:
  sound output dont change

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Even with right output selected, the sound plays on the notebook
  output.

  I've tried restart the system, it dont change.  If i test the sound on
  the configs, i hear the sound right (on my phones).  But on spotify \
  chrome, the sound plays on notebook output.

  https://imgur.com/a/9SMeTYA

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  otavio154337 F pulseaudio
   /dev/snd/controlC0:  otavio154337 F pulseaudio
   /dev/snd/pcmC0D0c:   otavio154337 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 14:26:53 2020
  InstallationDate: Installed on 2020-02-27 (40 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-04-06 (0 days ago)
  dmi.bios.date: 11/08/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9VCN15WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R33126 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion Y530-15ICH-1060
  dmi.modalias: 
dmi:bvnLENOVO:bvr9VCN15WW:bd11/08/2018:svnLENOVO:pn81M7:pvrLenovoLegionY530-15ICH-1060:rvnLENOVO:rnLNVNB161216:rvrSDK0R33126WIN:cvnLENOVO:ct10:cvrLenovoLegionY530-15ICH-1060:
  dmi.product.family: Legion Y530-15ICH-1060
  dmi.product.name: 81M7
  dmi.product.sku: LENOVO_MT_81M7_BU_idea_FM_Legion Y530-15ICH-1060
  dmi.product.version: Lenovo Legion Y530-15ICH-1060
  dmi.sys.vendor: LENOVO

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

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

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

[hugh chao]

upload patch for focal

** Patch added: "dual-jacks.patch"
   
https://bugs.launchpad.net/oem-priority/+bug/1869819/+attachment/5348635/+files/dual-jacks.patch

** Tags added: verification-needed

** Changed in: pulseaudio (Ubuntu Focal)
   Status: Triaged => In Progress

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

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

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

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

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

  [Expected result]
  Can detect external headset

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

  [Regression Potential]
  Low.

  [Failure rate]
  100%

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

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

  Ubuntu-Focal-Source:
  
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

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

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

[Touch-packages] [Bug 1870074] Re: python-glanceclient ftbfs in focal

[James Page]

Uploaded to focal for release team review.

Also submitted upstream - https://review.opendev.org/718093

** Changed in: python-glanceclient (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  python-glanceclient ftbfs in focal

Status in openssl package in Ubuntu:
  Invalid
Status in python-glanceclient package in Ubuntu:
  Fix Committed

Bug description:
  seen in the second focal test rebuild
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18963677/+files/buildlog_ubuntu-focal-amd64.python-glanceclient_1%3A2.17.0-0ubuntu2_BUILDING.txt.gz

  During handling of the above exception, another exception occurred:

  
  Traceback (most recent call last):

File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 
665, in urlopen
  httplib_response = self._make_request(

File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 
376, in _make_request
  self._validate_conn(conn)

File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 
996, in _validate_conn
  conn.connect()

File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 352, 
in connect
  self.sock = ssl_wrap_socket(

File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 383, 
in ssl_wrap_socket
  return context.wrap_socket(sock)

File "/usr/lib/python3/dist-packages/urllib3/contrib/pyopenssl.py", 
line 491, in wrap_socket
  raise ssl.SSLError("bad handshake: %r" % e)

  ssl.SSLError: ("bad handshake: SysCallError(-1, 'Unexpected
  EOF')",)

  
  During handling of the above exception, another exception occurred:

  
  Traceback (most recent call last):

File "/usr/lib/python3/dist-packages/requests/adapters.py", line 439, 
in send
  resp = conn.urlopen(

File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 
719, in urlopen
  retries = retries.increment(

File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 436, 
in increment
  raise MaxRetryError(_pool, url, error or ResponseError(cause))

  urllib3.exceptions.MaxRetryError:
  HTTPSConnectionPool(host='0.0.0.0', port=45175): Max retries exceeded
  with url: /v2/images/image123 (Caused by SSLError(SSLError("bad
  handshake: SysCallError(-1, 'Unexpected EOF')")))

  
  During handling of the above exception, another exception occurred:

  
  Traceback (most recent call last):

File "/<>/glanceclient/common/http.py", line 269, in 
_request
  resp = self.session.request(method,

File "/usr/lib/python3/dist-packages/requests/sessions.py", line 533, 
in request
  resp = self.send(prep, **send_kwargs)

File "/usr/lib/python3/dist-packages/requests/sessions.py", line 646, 
in send
  r = adapter.send(request, **kwargs)

File "/usr/lib/python3/dist-packages/requests/adapters.py", line 514, 
in send
  raise SSLError(e, request=request)

  requests.exceptions.SSLError: HTTPSConnectionPool(host='0.0.0.0',
  port=45175): Max retries exceeded with url: /v2/images/image123
  (Caused by SSLError(SSLError("bad handshake: SysCallError(-1,
  'Unexpected EOF')")))

  
  During handling of the above exception, another exception occurred:

  
  Traceback (most recent call last):

File "/<>/glanceclient/tests/unit/test_ssl.py", line 124, 
in test_v2_requests_cert_verification
  gc.images.get('image123')

File "/<>/glanceclient/v2/images.py", line 198, in get
  return self._get(image_id)

File "/<>/glanceclient/common/utils.py", line 598, in inner
  return RequestIdProxy(wrapped(*args, **kwargs))

File "/<>/glanceclient/v2/images.py", line 191, in _get
  resp, body = self.http_client.get(url, headers=header)

File "/<>/glanceclient/common/http.py", line 315, in get
  return self._request('GET', url, **kwargs)

File "/<>/glanceclient/common/http.py", line 282, in 
_request
  raise exc.CommunicationError(message=message)

  glanceclient.exc.CommunicationError: Error finding address for
  https://0.0.0.0:45175/v2/images/image123:
  HTTPSConnectionPool(host='0.0.0.0', port=45175): Max retries exceeded
  with url: /v2/images/image123 (Caused by SSLError(SSLError("bad
  handshake: SysCallError(-1, 'Unexpected EOF')")))

  
  During handling of the above exception, another exception occurred:

  
  Traceback (most recent call last):

File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in 
patched
  return func(*args, **keywargs)

File "/<>/glanceclient/tests/unit/test_ssl.py", line 128, 
in test_v2_requests_cert_verification
  self.fail('No certificate failure message is received')

File 

[Touch-packages] [Bug 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]

[Kai-Heng Feng]

Hi Phuc Minh Cai,

Please remove the old kernel and test this one:
https://people.canonical.com/~khfeng/lp1860754-3/

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

Title:
  ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to
  submit batchbuffer: Input/output error]

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't 
recognize graphic driver.
  - run udo apt-get install xserver-xorg-video-intel
  0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 24 14:29:01 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd]
  InstallationDate: Installed on 2020-01-24 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub
   Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. T100HAN
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: T100HAN.221
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: T100HAN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: T
  dmi.product.name: T100HAN
  dmi.product.sku: ASUS-TabletSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1870074] Re: python-glanceclient ftbfs in focal

[James Page]

Actually this resolved to be due to use of older algs in the certs which
are no longer considered strong.

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

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

Title:
  python-glanceclient ftbfs in focal

Status in openssl package in Ubuntu:
  Invalid
Status in python-glanceclient package in Ubuntu:
  In Progress

Bug description:
  seen in the second focal test rebuild
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18963677/+files/buildlog_ubuntu-focal-amd64.python-glanceclient_1%3A2.17.0-0ubuntu2_BUILDING.txt.gz

  During handling of the above exception, another exception occurred:

  
  Traceback (most recent call last):

File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 
665, in urlopen
  httplib_response = self._make_request(

File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 
376, in _make_request
  self._validate_conn(conn)

File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 
996, in _validate_conn
  conn.connect()

File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 352, 
in connect
  self.sock = ssl_wrap_socket(

File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 383, 
in ssl_wrap_socket
  return context.wrap_socket(sock)

File "/usr/lib/python3/dist-packages/urllib3/contrib/pyopenssl.py", 
line 491, in wrap_socket
  raise ssl.SSLError("bad handshake: %r" % e)

  ssl.SSLError: ("bad handshake: SysCallError(-1, 'Unexpected
  EOF')",)

  
  During handling of the above exception, another exception occurred:

  
  Traceback (most recent call last):

File "/usr/lib/python3/dist-packages/requests/adapters.py", line 439, 
in send
  resp = conn.urlopen(

File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 
719, in urlopen
  retries = retries.increment(

File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 436, 
in increment
  raise MaxRetryError(_pool, url, error or ResponseError(cause))

  urllib3.exceptions.MaxRetryError:
  HTTPSConnectionPool(host='0.0.0.0', port=45175): Max retries exceeded
  with url: /v2/images/image123 (Caused by SSLError(SSLError("bad
  handshake: SysCallError(-1, 'Unexpected EOF')")))

  
  During handling of the above exception, another exception occurred:

  
  Traceback (most recent call last):

File "/<>/glanceclient/common/http.py", line 269, in 
_request
  resp = self.session.request(method,

File "/usr/lib/python3/dist-packages/requests/sessions.py", line 533, 
in request
  resp = self.send(prep, **send_kwargs)

File "/usr/lib/python3/dist-packages/requests/sessions.py", line 646, 
in send
  r = adapter.send(request, **kwargs)

File "/usr/lib/python3/dist-packages/requests/adapters.py", line 514, 
in send
  raise SSLError(e, request=request)

  requests.exceptions.SSLError: HTTPSConnectionPool(host='0.0.0.0',
  port=45175): Max retries exceeded with url: /v2/images/image123
  (Caused by SSLError(SSLError("bad handshake: SysCallError(-1,
  'Unexpected EOF')")))

  
  During handling of the above exception, another exception occurred:

  
  Traceback (most recent call last):

File "/<>/glanceclient/tests/unit/test_ssl.py", line 124, 
in test_v2_requests_cert_verification
  gc.images.get('image123')

File "/<>/glanceclient/v2/images.py", line 198, in get
  return self._get(image_id)

File "/<>/glanceclient/common/utils.py", line 598, in inner
  return RequestIdProxy(wrapped(*args, **kwargs))

File "/<>/glanceclient/v2/images.py", line 191, in _get
  resp, body = self.http_client.get(url, headers=header)

File "/<>/glanceclient/common/http.py", line 315, in get
  return self._request('GET', url, **kwargs)

File "/<>/glanceclient/common/http.py", line 282, in 
_request
  raise exc.CommunicationError(message=message)

  glanceclient.exc.CommunicationError: Error finding address for
  https://0.0.0.0:45175/v2/images/image123:
  HTTPSConnectionPool(host='0.0.0.0', port=45175): Max retries exceeded
  with url: /v2/images/image123 (Caused by SSLError(SSLError("bad
  handshake: SysCallError(-1, 'Unexpected EOF')")))

  
  During handling of the above exception, another exception occurred:

  
  Traceback (most recent call last):

File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in 
patched
  return func(*args, **keywargs)

File "/<>/glanceclient/tests/unit/test_ssl.py", line 128, 
in test_v2_requests_cert_verification
  self.fail('No certificate failure message is received')

File "/usr/lib/python3/dist-packages/unittest2/case.py", 

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

[Hui Wang]

@Eric

Command line: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic
root=UUID=8d9177a5-95ca-4bd3-9c51-db760f7300b3 ro quiet splash
snd_hda_intel.dmic_detect=0 vt.handoff=1

You add "snd_hda_intel.dmic_detect=0" somewhere, maybe it is in the
grub.conf?

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The sound card is not detected on my machine

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 00:51:33 2020
  InstallationDate: Installed on 2020-02-25 (37 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2020
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 86FA
  dmi.board.vendor: HP
  dmi.board.version: 87.46
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd03/02/2020:svnHP:pnHPSpectrex360Convertible13-aw0xxx:pvr:rvnHP:rn86FA:rvr87.46:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-aw0xxx
  dmi.product.sku: 8UR41PA#ABG
  dmi.sys.vendor: HP

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

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