[Touch-packages] [Bug 1876065] Re: After unplug headphones and plug them again no sound can be heard
Looks good. And it's now in git: https://git.launchpad.net/~ubuntu-audio-dev/pulseaudio/log/?h=ubuntu- 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/1876065 Title: After unplug headphones and plug them again no sound can be heard Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Focal: In Progress Status in pulseaudio source package in Groovy: Fix Committed Bug description: * Impact Sound isn't automatically redirected to headphones when those are connected to a jack interface * Test case Disconnect the headsets Start your webbrowser/music player/video player and play some sound Connect the headsets to the jack interface -> the sound should be directly redirected to the plugged headsets * Regression potential Check that audio routing when connecting/disconnecting devices to the hack entry is working correctly After startup with headset plugged in they play sound nicely - no issue. When they are unplugged, the sound is switched to the speaker (laptop) - all good. However, when I plug the headset back there is no sound. I see the app on pavucontrol, the volume is fine - everything looks fine except there is no sound. I dumped output of "pactl list" command on startup (headset plugged), after unplugging the headset, and when it is plugged back. From the comparison of these outputs, it looks like the source has got muted after the headset is plugged. Source #1 State: RUNNING Name: alsa_input.pci-_00_1f.3.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 7 Mute: yes Attached three outputs: headset-in.txt - after startup with headset plugged - all fine. headset-out.txt - after unplugged headset - sound through the speaker - all fine. headset-back.txt - after plugged headset back - no sound. Any help greatly appreciated. Regards, Roman To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876065/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
It's now in git: https://git.launchpad.net/~ubuntu-audio-dev/pulseaudio/log/?h=ubuntu- bionic But I would recommend adding a blank line in the changelog entry. You have full access to the git repo so please feel free to commit there. -- 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: Fix Released Status in pulseaudio source package in Bionic: In Progress Status in pulseaudio source package in Focal: Fix Released 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 1870729] Re: DHCP Server regularly killed code=killed, status=6/ABRT
Problem still exists even after disabling apparmor completely: May 14 09:46:18 dc sh[4241]: ../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, back trace May 14 09:46:18 dc sh[4241]: #0 0x7fdeeb0dca4a in ?? May 14 09:46:18 dc sh[4241]: #1 0x7fdeeb0dc980 in ?? May 14 09:46:18 dc sh[4241]: #2 0x7fdeeb1187e1 in ?? May 14 09:46:18 dc sh[4241]: #3 0x7fdeeaebf609 in ?? May 14 09:46:18 dc sh[4241]: #4 0x7fdeeaffb103 in ?? May 14 09:46:18 dc systemd[1]: isc-dhcp-server.service: Main process exited, code=killed, status=6/ABRT May 14 09:46:18 dc systemd[1]: isc-dhcp-server.service: Failed with result 'signal'. isc-dhcp-server 4.4.1-2.1ubuntu5 amd64 -- 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 Status in isc-dhcp source package in Focal: 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 1875493] Re: [core] log rotation doesn't properly restart rsyslogd
it is a hard requirement of the SRU process that fixes land in the devel release and then propagate backwards through all other releases ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1875493 Title: [core] log rotation doesn't properly restart rsyslogd Status in Snappy: New Status in rsyslog package in Ubuntu: New Bug description: One of our commercial partners is developing a device agent snap for UC16. One of their engineers just shared the following bug report: I wanted to give you a heads up on an issue that we encountered with one of our gateways (a Dell 3000) regarding a full disk (/writable). It seems as though rsyslog had a bad logrotate config and was holding on to deleted files as described here: - https://www.claudiokuenzler.com/blog/861/after-ubuntu-update-trusty-xenial-disk-filled-syslog-logrotate - https://bugzilla.redhat.com/show_bug.cgi?id=1713358 Both df and du where showing different results for the “/writable” path on the Dell gateway. We were able to copy the lsof binary over and found this: $ sudo /tmp/lsof | grep deleted ... rsyslogd 1765 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog (deleted) rsyslogd 1765 syslog 6w REG 179,4 45056 130836 /var/log/auth.log (deleted) rsyslogd 1765 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log (deleted) in:imuxso 1765 1776 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog (deleted) in:imuxso 1765 1776 syslog 6w REG 179,4 45056 130836 /var/log/auth.log (deleted) in:imuxso 1765 1776 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log (deleted) in:imklog 1765 1777 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog (deleted) in:imklog 1765 1777 syslog 6w REG 179,4 45056 130836 /var/log/auth.log (deleted) in:imklog 1765 1777 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log (deleted) rs:main 1765 1778 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog (deleted) rs:main 1765 1778 syslog 6w REG 179,4 45056 130836 /var/log/auth.log (deleted) rs:main 1765 1778 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log (deleted) ... Restarting the service freed up the deleted files / disk space: sudo service rsyslog restart The rsyslog config (/etc/logrotate.d/rsyslog) calls this script post rotate: /usr/lib/rsyslog/rsyslog-rotate Which does not actually kill the rsyslog process: admin@GR0GP42:~$ ps aux | grep rsyslog syslog 2305 0.7 0.1 262692 3432 ? Ssl 20:35 0:00 /usr/sbin/rsyslogd -n admin 2464 0.0 0.0 12984 932 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog admin@GR0GP42:~$ sudo /usr/lib/rsyslog/rsyslog-rotate admin@GR0GP42:~$ ps aux | grep rsyslog syslog 2305 0.6 0.1 262692 3432 ? Ssl 20:35 0:00 /usr/sbin/rsyslogd -n admin 2469 0.0 0.0 12984 972 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog The fix appears to be using the following command: sudo systemctl restart rsyslog >/dev/null 2>&1 || true admin@GR0GP42:~$ ps aux | grep rsyslog syslog 2305 0.6 0.1 262692 3432 ? Ssl 20:35 0:00 /usr/sbin/rsyslogd -n admin 2482 0.0 0.0 12984 972 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog admin@GR0GP42:~$ sudo systemctl restart rsyslog >/dev/null 2>&1 || true admin@GR0GP42:~$ ps aux | grep rsyslog syslog 2487 1.0 0.1 262692 3432 ? Ssl 20:36 0:00 /usr/sbin/rsyslogd -n admin 2496 0.0 0.0 12984 980 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1875493/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1867375] Re: systemd-networkd: UseRoutes behavior change with introduction of UseGateway param
This bug was fixed in the package systemd - 245.5-2ubuntu2 --- systemd (245.5-2ubuntu2) groovy; urgency=medium [ Dan Streetman ] * network: Change IgnoreCarrierLoss default to value of ConfigureWithoutCarrier. This fixes bridges with static IP configuration. (LP: #1860926) File: debian/patches/lp1860926-network-Change-IgnoreCarrierLoss-default-to-value-of.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=59d655136ca05d830d46e5cd90e6b549406cd670 * Cherry-pick fix from upstream master to adjust UseGateway= default - network: change UseGateway= default to UseRoutes= setting - network: honor SetDNSRoutes= even if UseGateway=False (LP: #1867375) Files: - debian/patches/network-change-UseGateway-default-to-UseRoutes-setting.patch - debian/patches/network-honor-SetDNSRoutes-even-if-UseGateway-False.patch - debian/patches/test-modify-add-tests-for-UseRoutes-and-UseGateway-config.patch - debian/patches/test-verify-RoutesToDNS-is-independent-of-UseGateway.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=4ddb639d6bb0ca07368348bc588c21c41f08a5e7 * refresh quilt patches [ Balint Reczey ] * Rename a few patches which are expected to stay longer in Ubuntu Files: - debian/patches/Revert-cgroup-Continue-unit-reset-if-cgroup-is-busy.patch - debian/patches/Revert-namespace-be-more-careful-when-handling-namespacin.patch - debian/patches/resolved-Mitigate-DVE-2018-0001-by-retrying-NXDOMAIN-with.patch - debian/patches/debian/UBUNTU-Revert-cgroup-Continue-unit-reset-if-cgroup-is-busy.patch - debian/patches/debian/UBUNTU-Revert-namespace-be-more-careful-when-handling-namespacin.patch - debian/patches/debian/UBUNTU-resolved-Mitigate-DVE-2018-0001-by-retrying-NXDOMAIN-with.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=41e97add3900c761fafc58c7a2b024f7b618d313 * test: Skip test-boot-timestamps on permission denied. This fixes root-unittests in unprivileged LXD containers File: debian/patches/test-Skip-test-boot-timestamps-on-permission-denied.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b98a63c04e9e82b0f57617e21233aa103b069785 * tests: Skip test-execute in containers File: debian/tests/root-unittests https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=2d6f282bf20866f711c6ae509228b0c513218ca9 * Run some tests in LXD, too Files: - debian/tests/control - debian/tests/tests-in-lxd https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=bf0bb5176284d9ec1b348b84e70f961ee12e3cac -- Balint Reczey Tue, 12 May 2020 16:59:54 +0200 ** Changed in: systemd (Ubuntu Groovy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1867375 Title: systemd-networkd: UseRoutes behavior change with introduction of UseGateway param Status in netplan.io package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in netplan.io source package in Bionic: Invalid Status in systemd source package in Bionic: In Progress Status in netplan.io source package in Eoan: Invalid Status in systemd source package in Eoan: In Progress Status in netplan.io source package in Focal: Confirmed Status in systemd source package in Focal: Fix Committed Status in netplan.io source package in Groovy: Confirmed Status in systemd source package in Groovy: Fix Released Bug description: [impact] the networkd UseRoutes parameter allowed ignoring all routes provided by a dhcp4 server, including the route via the dhcp4-provided gateway. This was the behavior of networkd until recently, and in Focal the UseRoutes parameter does *not* prevent networkd from adding the route via the dhcp4-provided gateway. This is now controlled with a new parameter, UseGateway. The systemd in Focal unfortunately has part of the upstream code; it no longer ignores the gateway route when UseRoutes=false is specified, but also it does not include the UseGateway parameter. Before Focal, networkd did not allow ignoring dhcpv4 routes and the gateway separately; the UseRoutes= parameter either used, or ignored, both. This is why upstream added the UseGateway= paramter, which should be backported to allow control of ignoring the dhcpv4 routes and gateway separately. [test case] In Focal, bug 1872589 has a good test case netplan config, but a very quick test can be done with the networkd config: [Match] Name=eth0 [Network] DHCP=ipv4 LinkLocalAddressing=ipv6 [DHCP] RouteMetric=100 UseMTU=true UseRoutes=false this results in the system incorrectly setting a route via the default gateway:
[Touch-packages] [Bug 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network
This bug was fixed in the package systemd - 245.5-2ubuntu2 --- systemd (245.5-2ubuntu2) groovy; urgency=medium [ Dan Streetman ] * network: Change IgnoreCarrierLoss default to value of ConfigureWithoutCarrier. This fixes bridges with static IP configuration. (LP: #1860926) File: debian/patches/lp1860926-network-Change-IgnoreCarrierLoss-default-to-value-of.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=59d655136ca05d830d46e5cd90e6b549406cd670 * Cherry-pick fix from upstream master to adjust UseGateway= default - network: change UseGateway= default to UseRoutes= setting - network: honor SetDNSRoutes= even if UseGateway=False (LP: #1867375) Files: - debian/patches/network-change-UseGateway-default-to-UseRoutes-setting.patch - debian/patches/network-honor-SetDNSRoutes-even-if-UseGateway-False.patch - debian/patches/test-modify-add-tests-for-UseRoutes-and-UseGateway-config.patch - debian/patches/test-verify-RoutesToDNS-is-independent-of-UseGateway.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=4ddb639d6bb0ca07368348bc588c21c41f08a5e7 * refresh quilt patches [ Balint Reczey ] * Rename a few patches which are expected to stay longer in Ubuntu Files: - debian/patches/Revert-cgroup-Continue-unit-reset-if-cgroup-is-busy.patch - debian/patches/Revert-namespace-be-more-careful-when-handling-namespacin.patch - debian/patches/resolved-Mitigate-DVE-2018-0001-by-retrying-NXDOMAIN-with.patch - debian/patches/debian/UBUNTU-Revert-cgroup-Continue-unit-reset-if-cgroup-is-busy.patch - debian/patches/debian/UBUNTU-Revert-namespace-be-more-careful-when-handling-namespacin.patch - debian/patches/debian/UBUNTU-resolved-Mitigate-DVE-2018-0001-by-retrying-NXDOMAIN-with.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=41e97add3900c761fafc58c7a2b024f7b618d313 * test: Skip test-boot-timestamps on permission denied. This fixes root-unittests in unprivileged LXD containers File: debian/patches/test-Skip-test-boot-timestamps-on-permission-denied.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b98a63c04e9e82b0f57617e21233aa103b069785 * tests: Skip test-execute in containers File: debian/tests/root-unittests https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=2d6f282bf20866f711c6ae509228b0c513218ca9 * Run some tests in LXD, too Files: - debian/tests/control - debian/tests/tests-in-lxd https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=bf0bb5176284d9ec1b348b84e70f961ee12e3cac -- Balint Reczey Tue, 12 May 2020 16:59:54 +0200 ** Changed in: systemd (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1860926 Title: Ubuntu 20.04 Systemd fails to configure bridged network Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Status in systemd source package in Eoan: In Progress Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Released Bug description: [impact] A bridged interface with static ipv4 address and gateway configuration will fail to properly add the route via the gateway, leaving the system without a globally working network. [test case] On a Focal system, remove all network configuration and create this netplan: network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false bridges: br0: interfaces: [enp4s0] dhcp4: no addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] Replace the interface name 'enp4s0' with the actual interface name on the test system. Reboot the system, and check the route to the gateway, which will be missing: root@lp1860926-f:~# ip r 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 The route is expected to be present, e.g.: ubuntu@lp1860926-e:~$ ip r default via 192.168.0.1 dev br0 proto static 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 [test case, pre-focal] same netplan as above, but remove ethernets: section. Reboot, and the bridge should have its address and route: ubuntu@test-e:~$ ip a show br0 3: br0: mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff inet 192.168.0.4/24 brd 192.168.0.255 scope global br0 valid_lft forever preferred_lft forever ubuntu@test-e:~$ ip r default via 192.168.0.1 dev br0 proto
[Touch-packages] [Bug 1832632] Re: building from source on Ubuntu 18.04 fails
On Ubuntu 20.04 I had to add DEB_BUILD_OPTIONS=nocheck at the beginning of debian/rules -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1832632 Title: building from source on Ubuntu 18.04 fails Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Trying to build gtk+3.0-3.22.30 from source fails. I got the source using package gtk-3-examples. $ apt policy gtk-3-examples gtk-3-examples: Installed: 3.22.30-1ubuntu3 Candidate: 3.22.30-1ubuntu3 Version table: *** 3.22.30-1ubuntu3 500 500 http://il.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.22.30-1ubuntu1 500 500 http://il.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Ubuntu version: Description: Ubuntu 18.04.2 LTS Release: 18.04 Steps to reproduce: apt source gtk-3-examples sudo apt build-dep gtk-3-examples sudo apt install devscripts cd gtk+3.0-3.22.30 debuild -i -us -uc -d -b 2>&1 | tee build.log The build failed. First error (to the best of my knowledge): ERROR:../../../../../testsuite/gtk/scrolledwindow.c:100:test_size: assertion failed (min_size == MIN_SIZE): (153 == 150) FAIL Attached is the build log (build.log) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1832632/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
See https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1872118 still no acknowledgement -- 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 Status in isc-dhcp source package in Focal: 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 1877159] Re: netlink: 'systemd-network': attribute type 5 has an invalid length.
Hello Simon, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.41 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. ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1877159 Title: netlink: 'systemd-network': attribute type 5 has an invalid length. Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Eoan: Fix Released Status in systemd source package in Focal: Fix Released Bug description: [impact] systemd-networkd uses incorrect netlink attribute length for wireguard's persistent keepalive interval, which logs error messages from the kernel, and may incorrectly set the parameter. [test case] Only 1 Bionic VM is required to reproduce the problem: $ lxc launch images:ubuntu/bionic --vm -c security.secureboot=false foo $ sleep 10 # allow booting $ lxc exec foo -- apt install -y software-properties-common $ lxc exec foo -- add-apt-repository -y ppa:wireguard/wireguard $ lxc exec foo -- apt install -y wireguard-tools $ cat << EOF | lxc exec foo -- tee /etc/systemd/network/wg0.netdev # foo [NetDev] Name=wg0 Kind=wireguard [WireGuard] ListenPort= PrivateKey=cBkljQSKhtEe/U8GZmCAk2MBbKWL4TLC9PVtbMFyCVQ= [WireGuardPeer] PublicKey=emfIuZ3hZ+AnWIrKex/EqCp2mfzip8AxJu6RuweyRGc= AllowedIPs=192.168.255.2 Endpoint=bar.lxd: EOF $ cat << EOF | lxc exec foo -- tee /etc/systemd/network/wg0.network # foo [Match] Name=wg0 [Network] Address=192.168.255.1/24 EOF $ lxc exec foo -- systemctl restart systemd-networkd # notice the invalid length in dmesg $ lxc exec foo -- journalctl -kn 8 -- Logs begin at Mon 2020-05-11 16:56:40 UTC, end at Mon 2020-05-11 17:03:46 UTC. -- May 11 16:58:25 foo kernel: nf_tables: (c) 2007-2009 Patrick McHardy May 11 17:01:57 foo kernel: PKCS#7 signature not signed with a trusted key May 11 17:01:57 foo kernel: wireguard: module verification failed: signature and/or required key missing - tainting kernel May 11 17:01:57 foo kernel: wireguard: WireGuard 1.0.20200429 loaded. See www.wireguard.com for information. May 11 17:01:57 foo kernel: wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld . All Rights Reserved. May 11 17:01:57 foo kernel: netlink: 'systemd-network': attribute type 5 has an invalid length. May 11 17:01:57 foo kernel: netlink: 'systemd-network': attribute type 5 has an invalid length. May 11 17:02:23 foo kernel: netlink: 'systemd-network': attribute type 5 has an invalid length. [regression potential] this adjusts the length of the specific netlink parameter, so any regression would likely relate to incorrectly setting the persistent keepalive interval parameter, or failure to set the parameter. [scope] this is needed only for Bionic. this was fixed upstream in commit 7d0b26a027118ca063780421cb31c74e9d2664ee which was first included in v240, so this is fixed in Eoan and later. Xenial does not include support for wireguard, so this does not apply there. [original description] This morning, our 2 Bionic machine configured with the wireguard's PPA and using systemd-networkd to configure the wireguard tunnel started misbehaving. Why this started just now is unclear ATM but their dmesg was filled with this: validate_nla: 100 callbacks suppressed netlink: 'systemd-network': attribute type 5 has an invalid length. netlink: 'systemd-network': attribute type 5 has an invalid length. netlink: 'systemd-network': attribute type 5 has an invalid
[Touch-packages] [Bug 1876600] Re: cookie overruns can cause org.freedesktop.systemd1 dbus to hang
Hello Heitor, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.41 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. ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1876600 Title: cookie overruns can cause org.freedesktop.systemd1 dbus to hang Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: Fix Committed Bug description: [Impact] Long-running services overflow the sd_bus->cookie counter, causing further communication with org.freedesktop.systemd1 to stall. [Description] Systemd dbus messages include a "cookie" value to uniquely identify them in their bus context. This value is obtained from the bus header, and incremented for each exchanged message in the same bus object. For services that run for longer periods of time and keep communicating through dbus, it's possible to overflow the cookie value, causing further messages to the org.freedesktop.systemd1 dbus to fail. This can lead to these services becoming unresponsive, as they get stuck trying to communicate with invalid bus cookie values. This issue has been fixed upstream by the commit below: - sd-bus: deal with cookie overruns (1f82f5bb4237) $ git describe --contains 1f82f5bb4237 v242-rc1~228 $ rmadison systemd systemd | 229-4ubuntu4 | xenial | source, ... systemd | 229-4ubuntu21.27 | xenial-security | source, ... systemd | 229-4ubuntu21.27 | xenial-updates | source, ... systemd | 229-4ubuntu21.28 | xenial-proposed | source, ... systemd | 237-3ubuntu10| bionic | source, ... systemd | 237-3ubuntu10.38 | bionic-security | source, ... systemd | 237-3ubuntu10.39 | bionic-updates | source, ... systemd | 237-3ubuntu10.40 | bionic-proposed | source, ... < systemd | 242-7ubuntu3 | eoan| source, ... Releases starting with Eoan already have this fix. [Test Case] There doesn't seem to be an easy test case for this, as the cookie values start at zero and won't overflow until (1<<32). There have been reports from users hitting this on Kubernetes clusters continuously running for longer periods (~5 months). Using GDB, we can construct an artificial test case to test the cookie overflow. The test case below performs the following steps: 1. Create a new system bus object through sd_bus_default_system() 2. Allocate and append a new method_call message to the bus 3. Send the message through sd_bus_call() 4. Handle the response message and free up the message objects It's essentially the example code from the sd_bus_message_new_method_call() manpage, with minor modifications: this is done continuously, to keep incrementing the bus cookie value. We step in with GDB when it reaches 0x1, and set its value to 0xff00 which then causes the test program to fail shortly afterwards. An example test run of an impacted system: ubuntu@bionic:~$ gcc -Wall test.c -o cookie -lsystemd -g ubuntu@bionic:~$ gdb --batch --command=test.gdb --args ./cookie Breakpoint 1 at 0xe61: file test.c, line 38. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". (16s) cookie: 0x0001reply-cookie: 0x0001 Breakpoint 1, print_unit_path (bus=0x55757290) at test.c:38 38 r = sd_bus_message_new_method_call(bus, , $1 = 0x1 $2 = 0xff00 Call failed: Operation not supported Sleeping and retrying... Call failed: Invalid argument
[Touch-packages] [Bug 1873607] Re: systemd segv coredump, reboot/poweroff ignored.
Hello Harry, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.41 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. ** Changed in: systemd (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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1873607 Title: systemd segv coredump, reboot/poweroff ignored. Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Eoan: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Released Bug description: [impact] during systemctl daemon-reload, systemd sometimes segfaults while serializing a service. [test case] problem is intermittent, but the upstream bug suggests a reproducer. Also see original description. [regression potential] this adjusts serialization, so any regression would likely occur during serialization/deserialization, e.g. at daemon-reload. [scope] This is needed for Bionic and later. this was introduced by commit e266c068b5597e18b2299f9c9d3ee6cf04198c41 which is included starting in v234. The commit to fix it is e9da62b18af647bfa73807e1c7fc3bfa4bb4b2ac which is not yet included in any release. The PR to fix this is https://github.com/systemd/systemd/pull/15546 [other info] there is an additional PR that further avoids the error, but has not yet been accepted, and may not be accepted as it may not be necessary. https://github.com/systemd/systemd/pull/15370 [original description] Proximate syslog: Apr 18 16:26:56 gate2 rssmonitor.py[2001]: settings: Running: ip -all netns del Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/dbus.socket:4: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /r un/dbus/system_bus_socket; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/sssd.service:11: PIDFile= references a path below legacy directory /var/run/, updating /var/run/sssd.pid → /run/sssd.pid; plea se update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/oddjobd.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/oddjobd.pid → /run/oddjobd.p id; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /r un/fail2ban/fail2ban.pid; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/certmonger.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/certmonger.pid → /run/cer tmonger.pid; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: Reloading. Apr 18 16:26:56 gate2 kernel: [ 454.966336] systemd[1]: segfault at 50 ip 55946ed0d6f0 sp 7fff8409d210 error 4 in systemd[55946ecb4000+ae000] Apr 18 16:26:56 gate2 kernel: [ 454.966354] Code: a8 48 8b 75 a0 c7 45 ac 00 00 00 00 48 8b 94 c7 a0 04 00 00 48 89 45 88 48 89 f0 48 39 d6 74 17 66 2e 0f 1f 84 00 00 00 00 00 <48 > 8b 40 50 83 45 ac 01 48 39 c2 75 f3 48 8b 45 a0 31 db 4c 8d 7d Apr 18 16:26:56 gate2 rssmonitor.py[1213]: rssmain: Ran OK: systemctl daemon-reload Apr 18 16:26:57 gate2 rssmonitor.py[1213]: rssmain: Running: systemctl enable rssmonitor.service Apr 18 16:27:23 gate2 sssd[nss]: Enumeration requested but not enabled Apr 18 16:27:24 gate2 kernel: [
[Touch-packages] [Bug 1867375] Re: systemd-networkd: UseRoutes behavior change with introduction of UseGateway param
Hello Sunil, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.41 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. ** Changed in: systemd (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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1867375 Title: systemd-networkd: UseRoutes behavior change with introduction of UseGateway param Status in netplan.io package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in netplan.io source package in Bionic: Invalid Status in systemd source package in Bionic: Fix Committed Status in netplan.io source package in Eoan: Invalid Status in systemd source package in Eoan: Fix Committed Status in netplan.io source package in Focal: Confirmed Status in systemd source package in Focal: Fix Committed Status in netplan.io source package in Groovy: Confirmed Status in systemd source package in Groovy: Fix Released Bug description: [impact] the networkd UseRoutes parameter allowed ignoring all routes provided by a dhcp4 server, including the route via the dhcp4-provided gateway. This was the behavior of networkd until recently, and in Focal the UseRoutes parameter does *not* prevent networkd from adding the route via the dhcp4-provided gateway. This is now controlled with a new parameter, UseGateway. The systemd in Focal unfortunately has part of the upstream code; it no longer ignores the gateway route when UseRoutes=false is specified, but also it does not include the UseGateway parameter. Before Focal, networkd did not allow ignoring dhcpv4 routes and the gateway separately; the UseRoutes= parameter either used, or ignored, both. This is why upstream added the UseGateway= paramter, which should be backported to allow control of ignoring the dhcpv4 routes and gateway separately. [test case] In Focal, bug 1872589 has a good test case netplan config, but a very quick test can be done with the networkd config: [Match] Name=eth0 [Network] DHCP=ipv4 LinkLocalAddressing=ipv6 [DHCP] RouteMetric=100 UseMTU=true UseRoutes=false this results in the system incorrectly setting a route via the default gateway: root@lp1867375-f:~# ip r default via 10.202.51.1 dev eth0 proto dhcp src 10.202.51.86 metric 100 10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.86 10.202.51.1 dev eth0 proto dhcp scope link src 10.202.51.86 metric 100 Before Focal, the above test case shows "correct" behavior, but there is no way to ignore the dhcpv4 routes but use the dhcpv4 gateway. This pre-Focal, the test case would be to use the UseGateway= parameter, e.g.: [Match] Name=eth0 [Network] DHCP=ipv4 LinkLocalAddressing=ipv6 [DHCP] RouteMetric=100 UseMTU=true UseRoutes=false UseGateway=true which *should* result in the default gateway being configured: root@lp1867375-f:~# ip r default via 10.202.51.1 dev eth0 proto dhcp src 10.202.51.86 metric 100 10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.86 10.202.51.1 dev eth0 proto dhcp scope link src 10.202.51.86 metric 100 [regression potential] Any regression would likely involve incorrect setting, or ignoring, of dhcpv4-provided routes, and/or incorrect setting, or ignoring, of the dhcpv4-provided gateway. [scope] This is fixed by these upstream PRs: https://github.com/systemd/systemd/pull/15443 https://github.com/systemd/systemd/pull/15136 https://github.com/systemd/systemd/pull/14983 Parts of all those PRs are required in Focal, Eoan, and Bionic. I am not fixing this for Xenial, at this time. For Debian, I opened this MR:
[Touch-packages] [Bug 1878723] [NEW] Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
Public bug reported: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a ** Affects: json-c (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: New Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: json-c (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Confirmed Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
Also ran into this. It looks like this bug got backported https://github.com/json-c/json-c/issues/599. The upstream fix is this: https://github.com/besser82/json-c/commit/7a4807fe0cdb1d9e20273c79762cbf54833aaae4 ** Bug watch added: github.com/json-c/json-c/issues #599 https://github.com/json-c/json-c/issues/599 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Confirmed Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878598] Re: Screen orientation Portrait is broken
*** This bug is a duplicate of bug 1874567 *** https://bugs.launchpad.net/bugs/1874567 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 1874567, 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 1874567 [nvidia] Rotating secondary monitor to portrait fails, results in landscape -- 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/1878598 Title: Screen orientation Portrait is broken Status in xorg package in Ubuntu: New Bug description: I have two screens, one is 27'' plugged with displayport and the other 21'' plugged via HDMI. The 21'' doesn't accept the Portrait (Right or Left), it stays landscape. This same setup was ok in 19.10. I don't know for sure if it's xorg related of if it's related to display config screen but the options led me to this report. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/:01: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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 14 08:57:55 2020 DistUpgraded: 2020-05-13 09:40:01,957 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: Dell Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [1028:0527] NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP107 [GeForce GTX 1050 Ti] [3842:6251] InstallationDate: Installed on 2020-02-29 (75 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Alienware Alienware X51 ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=09e42201-f85d-4c4b-916b-452b980fa5e3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-13 (0 days ago) dmi.bios.date: 11/04/2013 dmi.bios.vendor: Alienware dmi.bios.version: A14 dmi.board.name: 06G6JW dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: 00 dmi.modalias: dmi:bvnAlienware:bvrA14:bd11/04/2013:svnAlienware:pnAlienwareX51:pvr00:rvnAlienware:rn06G6JW:rvrA00:cvnAlienware:ct3:cvr00: dmi.product.family: 0 dmi.product.name: Alienware X51 dmi.product.sku: Alienware X51 dmi.product.version: 00 dmi.sys.vendor: Alienware version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 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.8-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+git20200226-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/1878598/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878738] Re: program abort by "lh_table_new: calloc failed"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: json-c (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878738 Title: program abort by "lh_table_new: calloc failed" Status in json-c package in Ubuntu: Confirmed Bug description: I wrote small sample program which abort by lh_table_new calloc failed. see this. https://gist.github.com/735eec6fd0869df1facb08da5baa402c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878738/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 784055] Re: CPU usage increases dramatically when running indicator-multiload
** Tags added: performance -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libindicator in Ubuntu. https://bugs.launchpad.net/bugs/784055 Title: CPU usage increases dramatically when running indicator-multiload Status in libindicator: Fix Committed Status in The Ubuntu Power Consumption Project: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Status in indicator-multiload package in Ubuntu: Confirmed Status in libindicator package in Ubuntu: Fix Released Bug description: using 0.1-0~5~natty1 on mostly up to date natty system, when running the indicator-multiload with with just cpu monitor and the default update interval of 500 milliseconds, I see (via top) that compiz usage when generally idle goes from either 0 or 1% of CPU to 3 or 4% of CPU. Reducing the update interval does seem to have an affect. I realize that a.) top is not scientific b.) there could be something I'm missing here c.) saying "300%" (in the subject) is not scientific To manage notifications about this bug go to: https://bugs.launchpad.net/libindicator/+bug/784055/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878630] Re: Two Docks apears on my screen display.
Dash-to-dock is not part of Ubuntu and is not supported here. Please discuss that with its developers instead at: https://github.com/micheleg /dash-to-dock/issues Also, the problem with extensions not being configurable is probably bug 1718850. ** Changed in: xorg (Ubuntu) Status: New => Invalid ** Package changed: xorg (Ubuntu) => 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/1878630 Title: Two Docks apears on my screen display. Status in Ubuntu: Invalid Bug description: I don't know exactly what is happening. Normally, after some time of use, two Docks appear on my screen display. One overlaps the other, but I can separate them (putting one of them to the right, for example, while the other remains in the same place) by using the settings in "Extensions", specifically in "Dash to dock". I can use the applications in both. During the lock screen I also can see one of them. Another thing that is going on, related to this problem, is that in "Extensions" the button "Dash to Dock" appears disabled, although it is actually enabled. Even when I enable it, when I back to "Extensions" the button is disabled again. My technical knowledge of computers and systems is limited. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 14 11:06:41 2020 DistUpgraded: 2020-04-26 16:12:50,424 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falha ao executar processo filho “./xorg_fix_proprietary.py” (Arquivo ou diretório inexistente) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: anbox, 1, 4.15.0-96-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family Integrated Graphics Controller [144d:c0b6] Lsusb: Bus 002 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. 300V3A/300V4A/300V5A/200A4B/200A5B ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=c9037370-4dff-4489-a6dc-e00d62311c2f ro SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-26 (17 days ago) dmi.bios.date: 10/12/2011 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 05FI dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 300V3A/300V4A/300V5A/200A4B/200A5B dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr05FI:bd10/12/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pn300V3A/300V4A/300V5A/200A4B/200A5B:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn300V3A/300V4A/300V5A/200A4B/200A5B:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: HuronRiver System dmi.product.name: 300V3A/300V4A/300V5A/200A4B/200A5B dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-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+git20200226-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/+bug/1878630/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878738] Re: program abort by "lh_table_new: calloc failed"
I have identified the same issue. Parsing a relatively small file may result in a calloc failure because lh_table_new attempts to allocate an incorrectly size block of memory. In my case it attempted to allocate over 68 GiB in a single allocation. The cause seems to be the changes in the CVE patch: json-c (0.12.1-1.3ubuntu0.1) bionic-security; urgency=medium * SECURITY UPDATE: Integer overflows - debian/patches/CVE-2020-12762-*.patch: fix a series of integer overflows adding checks in linkhash.c, printbuf.c. - CVE-2020-12762 -- (Leonidas S. Barbosa) Mon, 11 May 2020 16:29:02 -0300 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-12762 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878738 Title: program abort by "lh_table_new: calloc failed" Status in json-c package in Ubuntu: Confirmed Bug description: I wrote small sample program which abort by lh_table_new calloc failed. see this. https://gist.github.com/735eec6fd0869df1facb08da5baa402c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878738/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
I also experienced this bug today. What seems to have happened is that upstart init filled all of the memory on my machine while libjson-c2 was updating, leading to oom-killer killing everything. The kernel panic here would happen if oom-killer tries to act on init. After a reboot my machine managed to upgrade fully before crashing due to running out of memory again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Confirmed Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878738] [NEW] program abort by "lh_table_new: calloc failed"
Public bug reported: I wrote small sample program which abort by lh_table_new calloc failed. see this. https://gist.github.com/735eec6fd0869df1facb08da5baa402c ** Affects: json-c (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878738 Title: program abort by "lh_table_new: calloc failed" Status in json-c package in Ubuntu: New Bug description: I wrote small sample program which abort by lh_table_new calloc failed. see this. https://gist.github.com/735eec6fd0869df1facb08da5baa402c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878738/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876065] Re: After unplug headphones and plug them again no sound can be heard
@Daniel van Vugt (vanvugt) Pardon my ignorance. I am a novice. I am trying to install it from the git for the past one day as per the guidance here: https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/Developer/PulseAudioFromGit/ However, I am unsuccessful. I couldn't install it. Else, I could have got back with the result for bug 1878327. Currently, I am waiting for it to move to Pre-released updates to test it or for the release of a patch by Kai-Heng Feng (kaihengfeng). If you (or anyone here) can give me a hint on how to install it from git, I will be more than happy to be a part of your team and to come back here and tell you the outcome with my machine. -- 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/1876065 Title: After unplug headphones and plug them again no sound can be heard Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Focal: In Progress Status in pulseaudio source package in Groovy: Fix Committed Bug description: * Impact Sound isn't automatically redirected to headphones when those are connected to a jack interface * Test case Disconnect the headsets Start your webbrowser/music player/video player and play some sound Connect the headsets to the jack interface -> the sound should be directly redirected to the plugged headsets * Regression potential Check that audio routing when connecting/disconnecting devices to the hack entry is working correctly After startup with headset plugged in they play sound nicely - no issue. When they are unplugged, the sound is switched to the speaker (laptop) - all good. However, when I plug the headset back there is no sound. I see the app on pavucontrol, the volume is fine - everything looks fine except there is no sound. I dumped output of "pactl list" command on startup (headset plugged), after unplugging the headset, and when it is plugged back. From the comparison of these outputs, it looks like the source has got muted after the headset is plugged. Source #1 State: RUNNING Name: alsa_input.pci-_00_1f.3.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 7 Mute: yes Attached three outputs: headset-in.txt - after startup with headset plugged - all fine. headset-out.txt - after unplugged headset - sound through the speaker - all fine. headset-back.txt - after plugged headset back - no sound. Any help greatly appreciated. Regards, Roman To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876065/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832632] Re: building from source on Ubuntu 18.04 fails
Same with 20.04 (gtk+3.0_3.24.18-1ubuntu1) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1832632 Title: building from source on Ubuntu 18.04 fails Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Trying to build gtk+3.0-3.22.30 from source fails. I got the source using package gtk-3-examples. $ apt policy gtk-3-examples gtk-3-examples: Installed: 3.22.30-1ubuntu3 Candidate: 3.22.30-1ubuntu3 Version table: *** 3.22.30-1ubuntu3 500 500 http://il.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.22.30-1ubuntu1 500 500 http://il.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Ubuntu version: Description: Ubuntu 18.04.2 LTS Release: 18.04 Steps to reproduce: apt source gtk-3-examples sudo apt build-dep gtk-3-examples sudo apt install devscripts cd gtk+3.0-3.22.30 debuild -i -us -uc -d -b 2>&1 | tee build.log The build failed. First error (to the best of my knowledge): ERROR:../../../../../testsuite/gtk/scrolledwindow.c:100:test_size: assertion failed (min_size == MIN_SIZE): (153 == 150) FAIL Attached is the build log (build.log) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1832632/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832632] Re: building from source on Ubuntu 18.04 fails
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gtk+3.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1832632 Title: building from source on Ubuntu 18.04 fails Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Trying to build gtk+3.0-3.22.30 from source fails. I got the source using package gtk-3-examples. $ apt policy gtk-3-examples gtk-3-examples: Installed: 3.22.30-1ubuntu3 Candidate: 3.22.30-1ubuntu3 Version table: *** 3.22.30-1ubuntu3 500 500 http://il.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.22.30-1ubuntu1 500 500 http://il.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Ubuntu version: Description: Ubuntu 18.04.2 LTS Release: 18.04 Steps to reproduce: apt source gtk-3-examples sudo apt build-dep gtk-3-examples sudo apt install devscripts cd gtk+3.0-3.22.30 debuild -i -us -uc -d -b 2>&1 | tee build.log The build failed. First error (to the best of my knowledge): ERROR:../../../../../testsuite/gtk/scrolledwindow.c:100:test_size: assertion failed (min_size == MIN_SIZE): (153 == 150) FAIL Attached is the build log (build.log) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1832632/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1875708] Re: Truncated messages in journald since systemd v244
** Also affects: libvirt (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: libvirt (Ubuntu Groovy) Importance: Low Status: Invalid ** Also affects: systemd (Ubuntu Groovy) Importance: High Assignee: Balint Reczey (rbalint) Status: In Progress ** Changed in: systemd (Ubuntu Focal) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1875708 Title: Truncated messages in journald since systemd v244 Status in libvirt package in Ubuntu: Invalid Status in systemd package in Ubuntu: In Progress Status in libvirt source package in Focal: New Status in systemd source package in Focal: In Progress Status in libvirt source package in Groovy: Invalid Status in systemd source package in Groovy: In Progress Bug description: [Impact] * since 09d0b46a "journal: refresh cached credentials of stdout streams" in ~244 output may be trincated. * Upstream has a fix in https://github.com/systemd/systemd/pull/15685 * Backporting the fix will avoid truncation of log output to journald [Test Case] * This could happen in any case, but is more likely when a program that has output going to journald is spawning short-lived sub-programs often. Therefore the test emphasizes on that: - Use a test service like /etc/systemd/system/test.service: [Unit] Description=Test Truncate After=network.target [Service] ExecStart=/usr/lib/test.sh long-test-for-start ExecStop=/usr/lib/test.sh long-test-for-stop Type=oneshot RemainAfterExit=yes StandardOutput=journal+console TimeoutStopSec=0 [Install] WantedBy=multi-user.target - And a test script like /usr/lib/test.sh: #!/bin/sh gettext "This will" echo gettext "usually fail" echo gettext "and be truncated" echo Start/Stopping that service without the fix will look like: Apr 30 18:56:40 f systemd[1]: Stopping Test Truncate... Apr 30 18:56:40 f test.sh[1165]: T Apr 30 18:56:40 f test.sh[1167]: T Apr 30 18:56:40 f test.sh[1167]: sually fai Apr 30 18:56:40 f test.sh[1165]: s Apr 30 18:56:40 f test.sh[1168]: s Apr 30 18:56:40 f test.sh[1168]: nd be truncate Apr 30 18:56:40 f test.sh[1165]: n Apr 30 18:56:40 f systemd[1]: test.service: Succeeded. Apr 30 18:56:40 f systemd[1]: Stopped Test Truncate. [Regression Potential] * The patches are rather small, but there might be a slightly increased memory consumption of journald for output buffers. * Issues (if any and I couldn't find any so far) should be only to journald output handling. Systemd is huge, this at least narrows down the potential places of a regression a lot. [Other Info] * n/a --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- Originally reported against libvirt which happens to be one of the example-triggers Hi, when I shut down my machine I see messages from /usr/lib/libvirt /libvirt-guests.sh but there are 2 anomalies: - 3 libvirt-guests.sh processes are run - messages are truncated ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libvirt-daemon 6.0.0-0ubuntu8 Uname: Linux 5.6.7-050607-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Apr 28 19:42:56 2020 SourcePackage: libvirt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.libvirt.nwfilter.allow-arp.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-arp.xml'] modified.conffile..etc.libvirt.nwfilter.allow-dhcp-server.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp-server.xml'] modified.conffile..etc.libvirt.nwfilter.allow-dhcp.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp.xml'] modified.conffile..etc.libvirt.nwfilter.allow-incoming-ipv4.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-incoming-ipv4.xml'] modified.conffile..etc.libvirt.nwfilter.allow-ipv4.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-ipv4.xml'] modified.conffile..etc.libvirt.nwfilter.clean-traffic-gateway.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/clean-traffic-gateway.xml'] modified.conffile..etc.libvirt.nwfilter.clean-traffic.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/clean-traffic.xml'] modified.conffile..etc.libvirt.nwfilter.no-arp-ip-spoofing.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-arp-ip-spoofing.xml']
[Touch-packages] [Bug 1872564] Re: /proc/sys/kernel/random/boot_id rule missing from abstractions/nameservice
This bug was fixed in the package apparmor - 2.13.3-7ubuntu6
---
apparmor (2.13.3-7ubuntu6) groovy; urgency=medium
* Add missing "boot_id" rule to abstractions/nameservice. (LP: #1872564)
- d/p/upstream-commit-454fca7-Add-run-variable.patch: Add the
definition for the "@{run}" variable.
-
d/p/upstream-commit-ef591a67-Add-trailing-slash-to-the-run-variable-definition.patch:
Add trailing slash to the "@{run}" variable.
-
d/p/upstream-commit-1f319c3870-abstractions-nameservice-allow-accessing-run-systemd-user.patch:
Add a missing rule to allow systemd to access
@{PROC}/sys/kernel/random/boot_id and @{run}/systemd/userdb.
- d/apparmor.install: Install new file 'tunables/run' under
'/etc/apparmor.d'.
-- Sergio Durigan Junior Mon, 11 May
2020 09:55:16 -0400
** 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/1872564
Title:
/proc/sys/kernel/random/boot_id rule missing from
abstractions/nameservice
Status in apparmor package in Ubuntu:
Fix Released
Status in apparmor source package in Focal:
Confirmed
Bug description:
[Impact]
On a default Focal install, systemd is used when looking up passwd and
group information:
# grep systemd /etc/nsswitch.conf
passwd: files systemd
group: files systemd
Daemons confined by Apparmor that also query those "databases" will
cause this Apparmor denial:
audit: type=1400 audit(1586825456.411:247): apparmor="DENIED"
operation="open" namespace="root//lxd-fb1_"
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id"
pid=7370 comm="named" requested_mask="r" denied_mask="r" fsuid=100
ouid=100
Many daemons confined by Apparmor also happen to downgrade their
privileges so they always end up looking up user/group information.
To fix this problem, we had to backport an upstream patch which adds
new directives to the 'nameservices' apparmor profile.
[Test Case]
In order to reproduce the bug, one can:
1) launch a Focal container (named fb1 here)
$ lxc launch images:ubuntu/focal fb1
2) setup apparmor inside the container (already done on official Ubuntu
images)
$ lxc exec fb1 -- apt update && lxc exec fb1 -- apt install apparmor -y
3) install bind9
$ lxc exec fb1 -- apt install bind9 -y
4) check kernel logs for DENIED
$ journalctl -o cat -b0 -k | grep 'apparmor="DENIED"' | grep -F
'profile="/usr/sbin/named"'
or, depending on how logging is configured:
$ dmesg | grep 'apparmor="DENIED"' | grep -F
'profile="/usr/sbin/named"'
Step 4, should not return anything. Because systemd is involved in the
user/group lookups, it currently returns the following:
audit: type=1400 audit(1586826072.115:266): apparmor="DENIED"
operation="open" namespace="root//lxd-fb1_"
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
audit: type=1400 audit(1586826072.115:267): apparmor="DENIED"
operation="open" namespace="root//lxd-fb1_"
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
audit: type=1400 audit(1586826072.115:268): apparmor="DENIED"
operation="open" namespace="root//lxd-fb1_"
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
audit: type=1400 audit(1586826072.115:269): apparmor="DENIED"
operation="open" namespace="root//lxd-fb1_"
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
audit: type=1400 audit(1586826072.115:270): apparmor="DENIED"
operation="open" namespace="root//lxd-fb1_"
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
[Regression Potential]
In order to fix this issue, 3 separate patches had to be backported.
They are simple and self-contained, especially two of them, whose
purposes are to add the definition of the @{run} variable and then to
add a trailing slash at the end of the "/run" pathname.
The other patch, albeit very simple, adds three statements to the
'nameservice' profile in order to let processes access (read-only)
files under "/run/systemd/userdb" and
"/proc/sys/kernel/random/boot_id". After thinking about the possible
cases, the only possible problem I could envision was for a program
that, not being able to access some of these files before, will now be
able to do that and therefore exercise a part of its codebase which
was not being used, possibly uncovering
[Touch-packages] [Bug 1878662] Re: [Satellite A500, Realtek ALC272, Black SPDIF Out, Left] No sound at all
** Package changed: 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/1878662 Title: [Satellite A500, Realtek ALC272, Black SPDIF Out, Left] No sound at all Status in pulseaudio package in Ubuntu: New Bug description: After upgrading to Ubuntu 20.04 , first I heard sound , later it was suddenly gone . Had a few automatic updates . When trying Ubuntu 20.04 from boot cd , the sound works . First bug test I heard the internal speakers , second test they were silent. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jack 9526 F pulseaudio /dev/snd/controlC0: jack 9526 F pulseaudio /dev/snd/pcmC0D1p: jack 9526 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 14 19:31:35 2020 InstallationDate: Installed on 2020-04-15 (29 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Black SPDIF Out, Left Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [Satellite A500, Realtek ALC272, Black SPDIF Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/10 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.50 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NSKAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 9 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvr1.50:bd02/12/10:svnTOSHIBA:pnSatelliteA500:pvrPSAR9E-01M00QGR:rvnTOSHIBA:rnNSKAA:rvr1.00:cvnTOSHIBA:ct9:cvrN/A: dmi.product.family: ABCDEFGHIJKLMNOPQRTUVWXYZ dmi.product.name: Satellite A500 dmi.product.sku: * dmi.product.version: PSAR9E-01M00QGR dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1878662/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1877271] Re: networkd does not enable ipv6 when requested
Hello Dan, or anyone else affected, Accepted systemd into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/242-7ubuntu3.9 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: systemd (Ubuntu Eoan) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-eoan -- 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/1877271 Title: networkd does not enable ipv6 when requested Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Eoan: Fix Committed Bug description: [impact] if networkd is configured with ipv6 address but the 'disable_ipv6' sysctl is enabled, networkd does not enable it and set the ipv6 configuration. [test case] [Match] Name=ens3 [Network] DHCP=ipv4 LinkLocalAddressing=ipv6 Address=2001:db8::100/64 manually disable ipv6 for the interface: ubuntu@lp1859862-b:~$ echo 1 | sudo tee /proc/sys/net/ipv6/conf/ens3/disable_ipv6 1 the interface should not contain any ipv6 addresses: ubuntu@lp1859862-b:~$ ip -6 a show ens3 ubuntu@lp1859862-b:~$ restart networkd; it should enable ipv6 as ipv6 addresses are configured, but it does not: ubuntu@lp1859862-b:~$ sudo systemctl restart systemd-networkd ubuntu@lp1859862-b:~$ ip -6 a show ens3 ubuntu@lp1859862-b:~$ [regression potential] any regression would likely result in failure to configure ipv6 addresses/routes. [scope] this is needed only for Eoan. this is fixed by commit 57ad76074670d4859e808a6aabd69fd6e58514c5, which is included starting in v243, so this is fixed in Focal and later. this bug was introduced by a series of patches starting at 54a1a535bd60f13964bbddd8f381601e33e8e56f, which is included starting in v243, but was also pulled into Debian v242-4, and so included in Eoan. This bug is not present in earlier versions so is not needed in Xenial or Bionic. [other info] this is a follow on for the fix in bug 1859862. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1877271/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1867375] Re: systemd-networkd: UseRoutes behavior change with introduction of UseGateway param
Hello Sunil, or anyone else affected, Accepted systemd into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/242-7ubuntu3.9 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: systemd (Ubuntu Eoan) Status: In Progress => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-eoan -- 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/1867375 Title: systemd-networkd: UseRoutes behavior change with introduction of UseGateway param Status in netplan.io package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in netplan.io source package in Bionic: Invalid Status in systemd source package in Bionic: In Progress Status in netplan.io source package in Eoan: Invalid Status in systemd source package in Eoan: Fix Committed Status in netplan.io source package in Focal: Confirmed Status in systemd source package in Focal: Fix Committed Status in netplan.io source package in Groovy: Confirmed Status in systemd source package in Groovy: Fix Released Bug description: [impact] the networkd UseRoutes parameter allowed ignoring all routes provided by a dhcp4 server, including the route via the dhcp4-provided gateway. This was the behavior of networkd until recently, and in Focal the UseRoutes parameter does *not* prevent networkd from adding the route via the dhcp4-provided gateway. This is now controlled with a new parameter, UseGateway. The systemd in Focal unfortunately has part of the upstream code; it no longer ignores the gateway route when UseRoutes=false is specified, but also it does not include the UseGateway parameter. Before Focal, networkd did not allow ignoring dhcpv4 routes and the gateway separately; the UseRoutes= parameter either used, or ignored, both. This is why upstream added the UseGateway= paramter, which should be backported to allow control of ignoring the dhcpv4 routes and gateway separately. [test case] In Focal, bug 1872589 has a good test case netplan config, but a very quick test can be done with the networkd config: [Match] Name=eth0 [Network] DHCP=ipv4 LinkLocalAddressing=ipv6 [DHCP] RouteMetric=100 UseMTU=true UseRoutes=false this results in the system incorrectly setting a route via the default gateway: root@lp1867375-f:~# ip r default via 10.202.51.1 dev eth0 proto dhcp src 10.202.51.86 metric 100 10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.86 10.202.51.1 dev eth0 proto dhcp scope link src 10.202.51.86 metric 100 Before Focal, the above test case shows "correct" behavior, but there is no way to ignore the dhcpv4 routes but use the dhcpv4 gateway. This pre-Focal, the test case would be to use the UseGateway= parameter, e.g.: [Match] Name=eth0 [Network] DHCP=ipv4 LinkLocalAddressing=ipv6 [DHCP] RouteMetric=100 UseMTU=true UseRoutes=false UseGateway=true which *should* result in the default gateway being configured: root@lp1867375-f:~# ip r default via 10.202.51.1 dev eth0 proto dhcp src 10.202.51.86 metric 100 10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.86 10.202.51.1 dev eth0 proto dhcp scope link src 10.202.51.86 metric 100 [regression potential] Any regression would likely involve incorrect setting, or ignoring, of dhcpv4-provided routes, and/or incorrect setting, or ignoring, of the dhcpv4-provided gateway. [scope] This is fixed by these upstream PRs: https://github.com/systemd/systemd/pull/15443 https://github.com/systemd/systemd/pull/15136 https://github.com/systemd/systemd/pull/14983 Parts of all those PRs are required in Focal, Eoan, and Bionic. I am not fixing this for Xenial, at this time. For
[Touch-packages] [Bug 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network
Hello Andrew, or anyone else affected, Accepted systemd into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/242-7ubuntu3.9 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: systemd (Ubuntu Eoan) Status: In Progress => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-eoan -- 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/1860926 Title: Ubuntu 20.04 Systemd fails to configure bridged network Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Status in systemd source package in Eoan: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Released Bug description: [impact] A bridged interface with static ipv4 address and gateway configuration will fail to properly add the route via the gateway, leaving the system without a globally working network. [test case] On a Focal system, remove all network configuration and create this netplan: network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false bridges: br0: interfaces: [enp4s0] dhcp4: no addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] Replace the interface name 'enp4s0' with the actual interface name on the test system. Reboot the system, and check the route to the gateway, which will be missing: root@lp1860926-f:~# ip r 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 The route is expected to be present, e.g.: ubuntu@lp1860926-e:~$ ip r default via 192.168.0.1 dev br0 proto static 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 [test case, pre-focal] same netplan as above, but remove ethernets: section. Reboot, and the bridge should have its address and route: ubuntu@test-e:~$ ip a show br0 3: br0: mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff inet 192.168.0.4/24 brd 192.168.0.255 scope global br0 valid_lft forever preferred_lft forever ubuntu@test-e:~$ ip r default via 192.168.0.1 dev br0 proto static linkdown 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 linkdown add and remove carrier, by adding and removing a slave interface: ubuntu@test-e:~$ sudo ip l set dev ens3 master br0 up ubuntu@test-e:~$ ip a show br0 3: br0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff inet 192.168.0.4/24 brd 192.168.0.255 scope global br0 valid_lft forever preferred_lft forever inet6 fe80::5411:daff:fe23:bb93/64 scope link valid_lft forever preferred_lft forever ubuntu@test-e:~$ sudo ip l set dev ens3 nomaster the bridge no longer has its address after losing carrier: ubuntu@test-e:~$ ip a show br0 3: br0: mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff inet6 fe80::5411:daff:fe23:bb93/64 scope link valid_lft forever preferred_lft forever [regression potential] Any regression would likely involve incorrectly configured network after an interface carrier gain/loss. [scope] This is needed for Focal, Eoan, and Bionic. While this only reproduces at boot for Focal, the general loss of configuration on carrier loss even when ConfigureWithoutCarrier=true is reproducable on all releases except Xenial, which does not have the ConfigureWithoutCarrier= parameter. [original
[Touch-packages] [Bug 1873607] Re: systemd segv coredump, reboot/poweroff ignored.
Hello Harry, or anyone else affected, Accepted systemd into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/242-7ubuntu3.9 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: systemd (Ubuntu Eoan) Status: In Progress => Fix Committed ** Tags added: verification-needed-eoan -- 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/1873607 Title: systemd segv coredump, reboot/poweroff ignored. Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Status in systemd source package in Eoan: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Released Bug description: [impact] during systemctl daemon-reload, systemd sometimes segfaults while serializing a service. [test case] problem is intermittent, but the upstream bug suggests a reproducer. Also see original description. [regression potential] this adjusts serialization, so any regression would likely occur during serialization/deserialization, e.g. at daemon-reload. [scope] This is needed for Bionic and later. this was introduced by commit e266c068b5597e18b2299f9c9d3ee6cf04198c41 which is included starting in v234. The commit to fix it is e9da62b18af647bfa73807e1c7fc3bfa4bb4b2ac which is not yet included in any release. The PR to fix this is https://github.com/systemd/systemd/pull/15546 [other info] there is an additional PR that further avoids the error, but has not yet been accepted, and may not be accepted as it may not be necessary. https://github.com/systemd/systemd/pull/15370 [original description] Proximate syslog: Apr 18 16:26:56 gate2 rssmonitor.py[2001]: settings: Running: ip -all netns del Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/dbus.socket:4: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /r un/dbus/system_bus_socket; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/sssd.service:11: PIDFile= references a path below legacy directory /var/run/, updating /var/run/sssd.pid → /run/sssd.pid; plea se update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/oddjobd.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/oddjobd.pid → /run/oddjobd.p id; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /r un/fail2ban/fail2ban.pid; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/certmonger.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/certmonger.pid → /run/cer tmonger.pid; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: Reloading. Apr 18 16:26:56 gate2 kernel: [ 454.966336] systemd[1]: segfault at 50 ip 55946ed0d6f0 sp 7fff8409d210 error 4 in systemd[55946ecb4000+ae000] Apr 18 16:26:56 gate2 kernel: [ 454.966354] Code: a8 48 8b 75 a0 c7 45 ac 00 00 00 00 48 8b 94 c7 a0 04 00 00 48 89 45 88 48 89 f0 48 39 d6 74 17 66 2e 0f 1f 84 00 00 00 00 00 <48 > 8b 40 50 83 45 ac 01 48 39 c2 75 f3 48 8b 45 a0 31 db 4c 8d 7d Apr 18 16:26:56 gate2 rssmonitor.py[1213]: rssmain: Ran OK: systemctl daemon-reload Apr 18 16:26:57 gate2 rssmonitor.py[1213]: rssmain: Running: systemctl enable rssmonitor.service Apr 18 16:27:23 gate2 sssd[nss]: Enumeration requested but not enabled Apr 18 16:27:24 gate2 kernel: [ 482.503042] printk:
[Touch-packages] [Bug 1831787] Re: Bogus routes after DHCP lease change
hmm, i can't reproduce this anymore, it seems one of my other patches to bionic fixed the problem. @ivoks, or anyone else, if you still see this with the latest systemd in bionic, please let me know. ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1831787 Title: Bogus routes after DHCP lease change Status in netplan: Invalid Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Disco: Won't Fix Status in systemd source package in Eoan: Fix Released Bug description: [impact] networkd does not remove old route(s) after DHCP address change [test case] on a system using networkd, that is connected to a network where you can control the addresses that the DHCP server provides, setup system with networkd to get address via DHCP, e.g. [Match] Name=ens3 [Network] DHCP=ipv4 (re)start networkd or reboot, so the system gets an ipv4 DHCP address, and corresponding route to the gateway. Then on the dhcp server, change the subnet to a different subnet. On the client, once its renews its DHCP address, the server will provide a new address in the new subnet, and the client will add a new default route to the new gateway address. However, the old default route to the old gateway address isn't removed. Note this also happens without changing the entire subnet, but is more subtle as shown in the original description. [regression potential] this affects how networkd handles routes, so has the potential to leave a system with partial or incorrect networking, or no networking at all. Any regression would most likely occur during networkd (re)start or during renewal of a DHCP lease, or when an interface is brought up. [other info] original description: --- Netplan config: network: version: 2 renderer: networkd ethernets: eno4: dhcp4: no eno1np0: dhcp4: no addresses: - 172.16.0.2/24 bridges: br0: dhcp4: yes interfaces: - eno4 On initial boot, machine got 10.0.15.109 IP address: May 03 13:09:41 ceph2 systemd-networkd[29349]: br0: Configured May 03 13:09:41 ceph2 systemd-networkd[29349]: br0: DHCPv4 address 10.0.15.109/23 via 10.0.15.253 At one point, DHCP server reserver this IP address and client eventually picked up new IP address: May 03 15:01:12 ceph2 systemd-networkd[1137]: br0: DHCPv4 address 10.0.15.128/23 via 10.0.15.253 This resulted in IP addresses: # ip -o a 1: loinet 127.0.0.1/8 scope host lo\ valid_lft forever preferred_lft forever 1: loinet6 ::1/128 scope host \ valid_lft forever preferred_lft forever 2: eno1np0inet 172.16.0.2/24 brd 172.16.0.255 scope global eno1np0\ valid_lft forever preferred_lft forever 2: eno1np0inet6 fe80::b226:28ff:fe53:56be/64 scope link \ valid_lft forever preferred_lft forever 6: br0inet 10.0.15.128/23 brd 10.0.15.255 scope global dynamic br0\ valid_lft 503sec preferred_lft 503sec 6: br0inet6 fe80::b8d7:5eff:fe6b:62a/64 scope link \ valid_lft forever preferred_lft forever So far, everything is fine. But, the routes on the machine are bogus: # ip r default via 10.0.15.253 dev br0 proto dhcp src 10.0.15.109 metric 100 default via 10.0.15.253 dev br0 proto dhcp src 10.0.15.128 metric 100 10.0.14.0/23 dev br0 proto kernel scope link src 10.0.15.128 10.0.15.253 dev br0 proto dhcp scope link src 10.0.15.109 metric 100 10.0.15.253 dev br0 proto dhcp scope link src 10.0.15.128 metric 100 172.16.0.0/24 dev eno1np0 proto kernel scope link src 172.16.0.2 routes with src 10.0.15.109 should have been removed when lease was renewed. I'm not sure if this is a bug in netplan or systemd. This is 18.04, systemd 37-3ubuntu10.21, netplan 0.40.1~18.04.4. To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1831787/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878686] [NEW] GNOME Settings crashes when clicking "Sign In / Register..." on Livepatch tab of Software & Updates
Public bug reported: GNOME Settings seems to crash when clicking the "Sign In / Register..." button that is available after clicking "Sign In..." on the Livepatch tab of Software & Updates. It seems to happen only one time on a clean, fully updated installation of Ubuntu 20.04. When clicking the button next time, it seems to work fine and correctly opens the Ubuntu Single Sign-On login dialog of GNOME Settings. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: focal ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- 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/1878686 Title: GNOME Settings crashes when clicking "Sign In / Register..." on Livepatch tab of Software & Updates Status in gnome-control-center package in Ubuntu: New Status in software-properties package in Ubuntu: New Bug description: GNOME Settings seems to crash when clicking the "Sign In / Register..." button that is available after clicking "Sign In..." on the Livepatch tab of Software & Updates. It seems to happen only one time on a clean, fully updated installation of Ubuntu 20.04. When clicking the button next time, it seems to work fine and correctly opens the Ubuntu Single Sign-On login dialog of GNOME Settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1878686/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878611] Re: accountsservice 0.6.55-0ubuntu12~20.04.1 update crashes into greeter
I can also confirm that if I disable autologin, reboot and then update to the current packages in focal-proposed updates that the installation of accountsservice 0.6.55-0ubuntu12~20.04.1 from the current accountsservice 0.6.55-0ubuntu11 package completes normally. -- 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/1878611 Title: accountsservice 0.6.55-0ubuntu12~20.04.1 update crashes into greeter Status in accountsservice package in Ubuntu: New Bug description: When updating Ubuntu 20.04 to the current proposed updates with the accountsservice 0.6.55-0ubuntu12~20.04.1 update, the current gnome session crashes out reproducibly into the the gdm3 greeter. At that point, when you try to log back in, only the background color is displayed but no desktop or menus ever appears. One has to perform a hard reboot at this point to get back to a greeter that will successfully login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1878611/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876230] Re: liburcu: Enable MEMBARRIER_CMD_PRIVATE_EXPEDITED to address performance problems with MEMBARRIER_CMD_SHARED
@sil2100, thanks for the trust. My TL;DR version for you is: >From one of liburcu maintainers (https://github.com/compudj): """ Posted Nov 24, 2013 23:55 UTC (Sun) by compudj (subscriber, #43335) [Link] Tracking threads running in multiple processes using a common shared memory is not possible with the currently implemented URCU flavors, but we look forward to adding a new URCU flavor to support this kind of use case. """ So that satisfies the corner case I have thought of. By that, I'm +1 on the SRU. continuing the longer version... > I agree with @ddstreet, I don't think liburcu gives that sort of guarantee when it comes to cross process synchronisation. It was my belief that liburcu targets synchronisation across a set of threads within the current process only. It does not (like stated above) but I had to check, specially cause I was just checking by the membarrier() syscall point of view (not too much into liburcu implementation). NOW with all that I got curious =)... >From liburcu documentation: """ There are multiple flavors of liburcu available: memb, qsbr, mb, signal, bp. The API members start with the prefix "urcu__", where is the chosen flavor name. Usage of liburcu-memb #include Link the application with -lurcu-memb This is the preferred version of the library, in terms of grace-period detection speed, read-side speed and flexibility. Dynamically detects kernel support for sys_membarrier(). Falls back on urcu-mb scheme if support is not present, which has slower read-side. Use the --disable-sys-membarrier-fallback configure option to disable the fall back, thus requiring sys_membarrier() to be available. This gives a small speedup when sys_membarrier() is supported by the kernel, and aborts in the library constructor if not supported. Usage of liburcu-qsbr #include Link with -lurcu-qsbr The QSBR flavor of RCU needs to have each reader thread executing rcu_quiescent_state() periodically to progress. rcu_thread_online() and rcu_thread_offline() can be used to mark long periods for which the threads are not active. It provides the fastest read-side at the expense of more intrusiveness in the application code. Usage of liburcu-mb #include Link with -lurcu-mb This version of the urcu library uses memory barriers on the writer and reader sides. This results in faster grace-period detection, but results in slower reads. Usage of liburcu-signal #include Link the application with -lurcu-signal Version of the library that requires a signal, typically SIGUSR1. Can be overridden with -DSIGRCU by modifying Makefile.build.inc. Usage of liburcu-bp #include Link with -lurcu-bp The BP library flavor stands for "bulletproof". It is specifically designed to help tracing library to hook on applications without requiring to modify these applications. urcu_bp_init(), and urcu_bp_unregister_thread() all become nops, whereas calling urcu_bp_register_thread() becomes optional. The state is dealt with by the library internally at the expense of read-side and write-side performance. """ > If the program links against liburcu 0.9 or lower, the sys_membarrier syscall did not exist yet, and liburcu will use the default compiler based membarrier, which is only good within the current process. Synchronisation across shared memory pages fails. This is the case on Xenial, Trusty and the like. > If the program links against liburcu 0.11 or newer, the sys_membarrier syscall does exist, but MEMBARRIER_CMD_SHARED is only used if the current running kernel does not support MEMBARRIER_CMD_PRIVATE_EXPEDITED. Yep. Showed here => https://tinyurl.com/y96692o8 > There is no toggle option in the API at all, so for users with a kernel 4.14 or higher, MEMBARRIER_CMD_PRIVATE_EXPEDITED will be used, and synchronisation across shared memory pages will fail. This is the case on Eoan, Focal, Groovy. Understood and agreed. The SRU line of thinking is always "not introducing regressions" so I was more interested in the "change of behavior" (even if "it is all broken"). > If the program links against liburcu 0.10, and uses the -qsbr, -md and > -signal variants, sys_membarrier is not used at all, and it falls back to the > compiler based membarrier, which is only good within the current process. > Synchronisation across shared memory pages will fail. Agreed per documentation. > If the program links against liburcu 0.10, and is used within a container, with a kernel version less than 4.3 that does not support sys_membarrier, such as a Bionic container on a Trusty 3.13 host, or on a 3.10 RHEL host, the sys_membarrier syscall fails, and it falls back to the compiler based membarrier. Synchronisation across shared memory pages will fail. Agreed, per "urcu_bp_sys_membarrier_status()". > Now, the upstream developers added MEMBARRIER_CMD_PRIVATE_EXPEDITED as the default in liburcu 0.11. They did not change the API to accommodate both MEMBARRIER_CMD_SHARED and MEMBARRIER_CMD_PRIVATE_EXPEDITED,
Re: [Touch-packages] [Bug 1873607] Re: systemd segv coredump, reboot/poweroff ignored.
Trying it now on 1 of 4 previously affected systems. Accepted all 'proposed' items, including changes to libvirt. Will advise. On 5/14/20 3:19 PM, Brian Murray wrote: > Hello Harry, or anyone else affected, > > Accepted systemd into eoan-proposed. The package will build now and be > available at https://launchpad.net/ubuntu/+source/systemd/242-7ubuntu3.9 > 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: systemd (Ubuntu Eoan) > Status: In Progress => Fix Committed > > ** Tags added: verification-needed-eoan > -- 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/1873607 Title: systemd segv coredump, reboot/poweroff ignored. Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Eoan: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Released Bug description: [impact] during systemctl daemon-reload, systemd sometimes segfaults while serializing a service. [test case] problem is intermittent, but the upstream bug suggests a reproducer. Also see original description. [regression potential] this adjusts serialization, so any regression would likely occur during serialization/deserialization, e.g. at daemon-reload. [scope] This is needed for Bionic and later. this was introduced by commit e266c068b5597e18b2299f9c9d3ee6cf04198c41 which is included starting in v234. The commit to fix it is e9da62b18af647bfa73807e1c7fc3bfa4bb4b2ac which is not yet included in any release. The PR to fix this is https://github.com/systemd/systemd/pull/15546 [other info] there is an additional PR that further avoids the error, but has not yet been accepted, and may not be accepted as it may not be necessary. https://github.com/systemd/systemd/pull/15370 [original description] Proximate syslog: Apr 18 16:26:56 gate2 rssmonitor.py[2001]: settings: Running: ip -all netns del Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/dbus.socket:4: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /r un/dbus/system_bus_socket; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/sssd.service:11: PIDFile= references a path below legacy directory /var/run/, updating /var/run/sssd.pid → /run/sssd.pid; plea se update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/oddjobd.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/oddjobd.pid → /run/oddjobd.p id; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /r un/fail2ban/fail2ban.pid; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/certmonger.service:6: PIDFile= references a path below legacy directory /var/run/, updating /var/run/certmonger.pid → /run/cer tmonger.pid; please update the unit file accordingly. Apr 18 16:26:56 gate2 systemd[1]: Reloading. Apr 18 16:26:56 gate2 kernel: [ 454.966336] systemd[1]: segfault at 50 ip 55946ed0d6f0 sp 7fff8409d210 error 4 in systemd[55946ecb4000+ae000] Apr 18 16:26:56 gate2 kernel: [ 454.966354] Code: a8 48 8b 75 a0 c7 45 ac 00 00 00 00 48 8b 94 c7 a0 04 00 00 48 89 45 88 48 89 f0 48 39 d6 74 17 66 2e 0f 1f 84 00 00 00 00 00 <48 > 8b 40 50 83 45 ac 01 48 39 c2 75 f3 48 8b 45 a0 31 db 4c 8d 7d Apr 18 16:26:56 gate2 rssmonitor.py[1213]: rssmain: Ran OK: systemctl
[Touch-packages] [Bug 1843982] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user()
I can also confirm that if I disable autologin, reboot and then update to the current packages in focal-proposed updates that the installation of accountsservice 0.6.55-0ubuntu12~20.04.1 from the current accountsservice 0.6.55-0ubuntu11 package completes normally. -- 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: Fix Released Status in accountsservice source package in Focal: Fix Committed Status in accountsservice package in Debian: Confirmed Bug description: [ Description ] When accountsservice's daemon is restarted - particularly when there is a user configured for auto login - it can cause code using its library to crash. This is bad because gnome-shell is one of those users which crashes. [ QA ] Configure a user for automatic login in gnome-shell. Restart accounts-daemon.service (sudo systemctl restart accounts- daemon.service) a few times, leaving several seconds between each attempt. See that it crashes if you don't have this SRU, and doesn't if you do have it. --- Test that fast user switching still works properly. --- Take a look at the error reports listed below and hopefully see them not occurring (barring the usual noise) with the SRU. [ Regression potential ] We think this is safe - it tells clients that the daemon is away when it quits, and is back when it comes back. They should get appropriate signals to indicate this. Nevertheless, these signals are sent when they weren't before now, so that could cause problems. Watch out for errors creeping up with this SRU. We wondered upstream whether some more protections might be needed. I'm thinking that those should be *additional* safety rails around this fix, but it could actually be that more is needed and this fix isn't complete. [ Original report ] 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: 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 1529152] Re: slow completion for systemd units
Hello Karl-Philipp, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.41 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. ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1529152 Title: slow completion for systemd units Status in systemd: Fix Released Status in bash-completion package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in bash-completion source package in Xenial: Invalid Status in systemd source package in Xenial: Won't Fix Status in bash-completion source package in Bionic: Invalid Status in systemd source package in Bionic: Fix Committed Bug description: [impact] systemctl tab completion is annoyingly slow. [test case] on a bionic system: $ systemctl status systemd- any unit can be used, or even before specifying any unit name chars. That will hang for sometimes a few seconds. [regression potential] this updates systemctl bash completion, so any regression would likely result in systemctl command misbehaving; most likely, failure to tab- complete. [scope] This is needed for Bionic and Xenial, however I am not currently planning to fix this for Xenial. This is fixed by upstream commit f28255e2d5695b0d060558ff8cbb2b526fc94cc0 and a few other previous commits, which are all included starting in v240, so this is fixed already in Eoan and later. [original description] Pressing Tab after entering `sudo systemctl status [existing service name without .service suffix]` into console it takes up to 5 seconds until the auto-completion completes. Until then the cursor can't be moved. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bash-completion 1:2.1-4.1ubuntu2 Uname: Linux 4.2.5-040205-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Thu Dec 24 21:04:41 2015 InstallationDate: Installed on 2015-04-20 (248 days ago) InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 (20141022.2) PackageArchitecture: all ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: bash-completion UpgradeStatus: Upgraded to wily on 2015-10-26 (59 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1529152/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878611] Re: accountsservice 0.6.55-0ubuntu12~20.04.1 update crashes into greeter
** Tags added: focal regression-proposed -- 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/1878611 Title: accountsservice 0.6.55-0ubuntu12~20.04.1 update crashes into greeter Status in accountsservice package in Ubuntu: New Bug description: When updating Ubuntu 20.04 to the current proposed updates with the accountsservice 0.6.55-0ubuntu12~20.04.1 update, the current gnome session crashes out reproducibly into the the gdm3 greeter. At that point, when you try to log back in, only the background color is displayed but no desktop or menus ever appears. One has to perform a hard reboot at this point to get back to a greeter that will successfully login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1878611/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878662] [NEW] [Satellite A500, Realtek ALC272, Black SPDIF Out, Left] No sound at all
You have been subscribed to a public bug: After upgrading to Ubuntu 20.04 , first I heard sound , later it was suddenly gone . Had a few automatic updates . When trying Ubuntu 20.04 from boot cd , the sound works . First bug test I heard the internal speakers , second test they were silent. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jack 9526 F pulseaudio /dev/snd/controlC0: jack 9526 F pulseaudio /dev/snd/pcmC0D1p: jack 9526 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 14 19:31:35 2020 InstallationDate: Installed on 2020-04-15 (29 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Black SPDIF Out, Left Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [Satellite A500, Realtek ALC272, Black SPDIF Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/10 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.50 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NSKAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 9 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvr1.50:bd02/12/10:svnTOSHIBA:pnSatelliteA500:pvrPSAR9E-01M00QGR:rvnTOSHIBA:rnNSKAA:rvr1.00:cvnTOSHIBA:ct9:cvrN/A: dmi.product.family: ABCDEFGHIJKLMNOPQRTUVWXYZ dmi.product.name: Satellite A500 dmi.product.sku: * dmi.product.version: PSAR9E-01M00QGR dmi.sys.vendor: TOSHIBA ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- [Satellite A500, Realtek ALC272, Black SPDIF Out, Left] No sound at all https://bugs.launchpad.net/bugs/1878662 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio 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 1876486] Re: Kernel panic booting after 18.04 to 20.04 upgrade
Moving back to incomplete as stated by @paelzer. ** Changed in: libseccomp (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1876486 Title: Kernel panic booting after 18.04 to 20.04 upgrade Status in libseccomp package in Ubuntu: Incomplete Bug description: Upgraded Ubuntu 18.04 to 20.04. Following the upgrade, booting was not possible. The error messages is: /sbin/init: symbol lookup error: /lib/systemd/libsystemd-shared-245.so: undefined symbol: seccomp_api_get [4.608900] Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 See also attached photograph of screen during boot. Upgrade followed steps from here: https://help.ubuntu.com/community/FocalUpgrades/Kubuntu With the excpetion that The -d flag was used for the do-release-upgrade: sudo do-release-upgrade -d -m desktop 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Prior to upgrade: Ubuntu 18.04.4 After upgrade (but never booted): Ubuntu (Kubuntu) 20.04 Note that Ubuntu had originally be installed, but kubuntu-desktop was recently installed to change to Kubuntu, but no booting problems were experienced before updating to 20.04. 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Unknown -- Package version may have changed when upgrading to 20.04. 3) What you expected to happen Boot without kernel panic. 4) What happened instead Could not boot. Even selecting safe mode from grub could not boot. Had to restore system from backups. Will not attempt upgrade again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876486/+subscriptions -- Mailing list: https://launchpad.net/~touch-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()
Looking at the syslog for the failed upgrade to accountsservice 0.6.55-0ubuntu12~20.04.1 with autologin enabled, I find that the first failure appears at... May 13 17:04:50 howarth-MacPro systemd[1]: Stopping Accounts Service... May 13 17:04:50 howarth-MacPro systemd[1]: accounts-daemon.service: Succeeded. May 13 17:04:50 howarth-MacPro systemd[1]: Stopped Accounts Service. May 13 17:04:50 howarth-MacPro systemd[1]: Starting Accounts Service... May 13 17:04:50 howarth-MacPro accounts-daemon[12151]: started daemon version 0.6.55 May 13 17:04:50 howarth-MacPro systemd[1]: Started Accounts Service. May 13 17:04:50 howarth-MacPro kernel: [ 311.779519] gsd-keyboard[2260]: segfault at 0 ip 7f330b6b1494 sp 7ffed49c6f88 error 4 in libglib-2.0.so.0.6400.2[7f330b68d000+84000] May 13 17:04:50 howarth-MacPro kernel: [ 311.779530] Code: f8 5b 5d c3 66 90 f3 0f 1e fa 48 83 ec 08 e8 a3 cf fd ff 85 c0 0f 94 c0 48 83 c4 08 0f b6 c0 c3 66 0f 1f 44 00 00 f3 0f 1e fa < 0f> be 07 41 b8 05 15 00 00 84 c0 74 1d 0f 1f 80 00 00 00 00 44 89 May 13 17:04:50 howarth-MacPro kernel: [ 311.779639] gdm3[1405]: segfault at 0 ip 7f719bbe3494 sp 7ffc4861af48 error 4 in libglib-2.0.so.0.6400.2[7f719bbbf000+84000] May 13 17:04:50 howarth-MacPro kernel: [ 311.779650] Code: f8 5b 5d c3 66 90 f3 0f 1e fa 48 83 ec 08 e8 a3 cf fd ff 85 c0 0f 94 c0 48 83 c4 08 0f b6 c0 c3 66 0f 1f 44 00 00 f3 0f 1e fa < 0f> be 07 41 b8 05 15 00 00 84 c0 74 1d 0f 1f 80 00 00 00 00 44 89 May 13 17:04:50 howarth-MacPro kernel: [ 311.779653] gdm-session-wor[1519]: segfault at 0 ip 7f6a8d633494 sp 7ffe7b13c2a8 error 4 in libglib-2.0.so.0.6400.2[7f6a8d60f000+84000] May 13 17:04:50 howarth-MacPro kernel: [ 311.779662] Code: f8 5b 5d c3 66 90 f3 0f 1e fa 48 83 ec 08 e8 a3 cf fd ff 85 c0 0f 94 c0 48 83 c4 08 0f b6 c0 c3 66 0f 1f 44 00 00 f3 0f 1e fa < 0f> be 07 41 b8 05 15 00 00 84 c0 74 1d 0f 1f 80 00 00 00 00 44 89 May 13 17:04:50 howarth-MacPro gnome-shell[1882]: GNOME Shell crashed with signal 11 May 13 17:04:50 howarth-MacPro gnome-shell[1882]: == Stack trace for context 0x55ed1ab076e0 == May 13 17:04:50 howarth-MacPro systemd[1534]: Stopped target GNOME Keyboard handling. May 13 17:04:50 howarth-MacPro systemd[1534]: gsd-keyboard.service: Main process exited, code=dumped, status=11/SEGV May 13 17:04:50 howarth-MacPro /usr/lib/gdm3/gdm-x-session[1562]: (II) modeset(0): Disabling kernel dirty updates, not required. May 13 17:04:50 howarth-MacPro systemd[1534]: gsd-keyboard.service: Failed with result 'core-dump'. May 13 17:04:50 howarth-MacPro systemd[1534]: Stopped GNOME Keyboard handling. May 13 17:04:50 howarth-MacPro systemd[1534]: gsd-keyboard.service: Triggering OnFailure= dependencies. May 13 17:04:50 howarth-MacPro systemd[1534]: Started GNOME Session Failed lockdown screen (user). May 13 17:04:50 howarth-MacPro systemd[1534]: Reached target GNOME Session Failed. May 13 17:04:50 howarth-MacPro systemd[1534]: Starting Notification regarding a crash report... May 13 17:04:50 howarth-MacPro update-notifier-crash[12175]: /usr/bin/whoopsie May 13 17:04:50 howarth-MacPro systemd[1534]: gnome-shell-x11.service: Main process exited, code=dumped, status=11/SEGV May 13 17:04:50 howarth-MacPro systemd[1534]: gnome-shell-x11.service: Failed with result 'core-dump'. May 13 17:04:50 howarth-MacPro systemd[1534]: gnome-shell-x11.service: Scheduled restart job, restart counter is at 1. May 13 17:04:50 howarth-MacPro systemd[1534]: Stopped target GNOME X11 Session (session: ubuntu). May 13 17:04:50 howarth-MacPro systemd[1534]: Stopping GNOME X11 Session (session: ubuntu). May 13 17:04:50 howarth-MacPro systemd[1534]: Stopped target GNOME X11 Session. May 13 17:04:50 howarth-MacPro systemd[1534]: Stopping GNOME X11 Session. May 13 17:04:50 howarth-MacPro systemd[1534]: Stopped target GNOME Shell on X11. May 13 17:04:50 howarth-MacPro systemd[1534]: Stopping GNOME Shell on X11. May 13 17:04:50 howarth-MacPro systemd[1534]: Stopped GNOME Shell on X11. May 13 17:04:50 howarth-MacPro systemd[1534]: Starting GNOME Shell on X11... May 13 17:04:51 howarth-MacPro /usr/lib/gdm3/gdm-x-session[1562]: (II) modeset(0): EDID vendor "APP", prod id 37404 May 13 17:04:51 howarth-MacPro /usr/lib/gdm3/gdm-x-session[1562]: (II) modeset(0): Printing DDC gathered Modelines: May 13 17:04:51 howarth-MacPro /usr/lib/gdm3/gdm-x-session[1562]: (II) modeset(0): Modeline "1920x1200"x0.0 154.00 1920 1968 2000 2080 1200 1203 1209 1235 +hsync -vsync (74.0 kHz eP) May 13 17:04:51 howarth-MacPro update-notifier-crash[12190]: gdm-session-worker May 13 17:04:51 howarth-MacPro update-notifier-crash[12190]: gdm3 May 13 17:04:51 howarth-MacPro gsd-media-keys[2262]: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell” on object at pa th /org/gnome/Shell May 13 17:04:51 howarth-MacPro systemd[1]: gdm.service: Main process exited, code=dumped, status=11/SEGV May 13 17:04:51
[Touch-packages] [Bug 1827253] Proposed package removed from archive
The version of rsyslog in the proposed pocket of Bionic that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1827253 Title: [apparmor] missing 'mr' on binary for usage on containers Status in rsyslog package in Ubuntu: Fix Released Status in rsyslog source package in Bionic: In Progress Status in rsyslog source package in Disco: In Progress Status in rsyslog source package in Eoan: In Progress Bug description: [Impact] * rsyslog ships with a (Default disable) apparmor profile. * Security sensitive users are in general encouraged to enable such profiles but unfortunately due to slightly new behavior of the program the profile prevents its usage. * Allow the program to map/read its binary to get this working again [Test Case] 1) Create a 'eoan' container called rs1 here: lxc launch ubuntu-daily:e rs1 2) Enter the container lxc shell rs1 3) Enable apparmor profile rm /etc/apparmor.d/disable/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog 4) notice rsyslog failed to start systemctl status rsyslog [Regression Potential] * This is just opening up the apparmor profile a bit. Therefore the only regression it could cause IMHO is a security issue. But then what it actually allows is reading (not writing!) its own binary which should be very safe. * Thinking further it came to my mind that package updates (independent to the change) might restart services and that means if there is any issue e.g. in a local config that worked but now fails (not by this change but in general) then the upgrade will not cause, but trigger this. This is a general regression risk for any upload, but in this case worth to mention as it is about log handling - which if broken - makes large scale systems hard to debug. [Other Info] * n/a --- Issue description: Enabling the rsyslog (disabled by default) Apparmor profile causes rsyslog to fail to start when running *inside a container*. Steps to reproduce: 1) Create a 'eoan' container called rs1 here: lxc launch ubuntu-daily:e rs1 2) Enter the container lxc shell rs1 3) Enable apparmor profile rm /etc/apparmor.d/disable/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog 4) notice rsyslog failed to start systemctl status rsyslog Workaround: echo ' /usr/sbin/rsyslogd mr,' >> /etc/apparmor.d/local/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog Additional information: root@rs1:~# uname -a Linux rs1 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@rs1:~# lsb_release -rd Description: Ubuntu Eoan EANIMAL (development branch) Release: 19.10 root@rs1:~# dpkg -l| grep -wE 'apparmor|rsyslog' ii apparmor 2.13.2-9ubuntu6 amd64user-space parser utility for AppArmor ii rsyslog 8.32.0-1ubuntu7 amd64reliable system and kernel logging daemon ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: rsyslog 8.32.0-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Wed May 1 17:36:29 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1827253/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1827253] Proposed package removed from archive
The version of rsyslog in the proposed pocket of Bionic that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1827253 Title: [apparmor] missing 'mr' on binary for usage on containers Status in rsyslog package in Ubuntu: Fix Released Status in rsyslog source package in Bionic: In Progress Status in rsyslog source package in Disco: In Progress Status in rsyslog source package in Eoan: In Progress Bug description: [Impact] * rsyslog ships with a (Default disable) apparmor profile. * Security sensitive users are in general encouraged to enable such profiles but unfortunately due to slightly new behavior of the program the profile prevents its usage. * Allow the program to map/read its binary to get this working again [Test Case] 1) Create a 'eoan' container called rs1 here: lxc launch ubuntu-daily:e rs1 2) Enter the container lxc shell rs1 3) Enable apparmor profile rm /etc/apparmor.d/disable/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog 4) notice rsyslog failed to start systemctl status rsyslog [Regression Potential] * This is just opening up the apparmor profile a bit. Therefore the only regression it could cause IMHO is a security issue. But then what it actually allows is reading (not writing!) its own binary which should be very safe. * Thinking further it came to my mind that package updates (independent to the change) might restart services and that means if there is any issue e.g. in a local config that worked but now fails (not by this change but in general) then the upgrade will not cause, but trigger this. This is a general regression risk for any upload, but in this case worth to mention as it is about log handling - which if broken - makes large scale systems hard to debug. [Other Info] * n/a --- Issue description: Enabling the rsyslog (disabled by default) Apparmor profile causes rsyslog to fail to start when running *inside a container*. Steps to reproduce: 1) Create a 'eoan' container called rs1 here: lxc launch ubuntu-daily:e rs1 2) Enter the container lxc shell rs1 3) Enable apparmor profile rm /etc/apparmor.d/disable/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog 4) notice rsyslog failed to start systemctl status rsyslog Workaround: echo ' /usr/sbin/rsyslogd mr,' >> /etc/apparmor.d/local/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog Additional information: root@rs1:~# uname -a Linux rs1 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@rs1:~# lsb_release -rd Description: Ubuntu Eoan EANIMAL (development branch) Release: 19.10 root@rs1:~# dpkg -l| grep -wE 'apparmor|rsyslog' ii apparmor 2.13.2-9ubuntu6 amd64user-space parser utility for AppArmor ii rsyslog 8.32.0-1ubuntu7 amd64reliable system and kernel logging daemon ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: rsyslog 8.32.0-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Wed May 1 17:36:29 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1827253/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1684588] Re: ADT upstream tests should run with QEMU on more architectures
ppc64el now finds qemu, but arm64 and s390x still does not. -- 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/1684588 Title: ADT upstream tests should run with QEMU on more architectures Status in systemd package in Ubuntu: Confirmed Bug description: ADT upstream tests should run with QEMU on more architectures. Currently there is: TEST RUN: Job-related tests Could not find a suitable QEMU binary W: can't run QEMU, skipping On e.g. ppc64el. This needs testing to make sure upstream tests know how to correctly setup a serial console on all arches (e.g. might not know specifics of s390x/ppc64el/etc) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1684588/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878617] [NEW] Apple pages file type should be added to MIME types
Public bug reported: LibreOffice can open .pages files (from Apple pages). However, the mime type for these files is incorrectly just application/zip: $ file --mime-type example.pages example.pages: application/zip Instead, it should be application/vnd.apple.pages . This would allow the user to associate LibreOffice Writer with these types of files, and use it to open this file. (LibreOffice Writer can open .pages files) Apple Keynote files should have this MIME type: application/vnd.apple.keynote Apple Numbers files should have this MIME type: application/vnd.apple.numbers ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mime-support 3.64ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 14 14:46:40 2020 InstallationDate: Installed on 2018-11-11 (550 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: mime-support UpgradeStatus: Upgraded to focal on 2020-04-18 (25 days ago) ** Affects: mime-support (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mime-support in Ubuntu. https://bugs.launchpad.net/bugs/1878617 Title: Apple pages file type should be added to MIME types Status in mime-support package in Ubuntu: New Bug description: LibreOffice can open .pages files (from Apple pages). However, the mime type for these files is incorrectly just application/zip: $ file --mime-type example.pages example.pages: application/zip Instead, it should be application/vnd.apple.pages . This would allow the user to associate LibreOffice Writer with these types of files, and use it to open this file. (LibreOffice Writer can open .pages files) Apple Keynote files should have this MIME type: application/vnd.apple.keynote Apple Numbers files should have this MIME type: application/vnd.apple.numbers ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mime-support 3.64ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 14 14:46:40 2020 InstallationDate: Installed on 2018-11-11 (550 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: mime-support UpgradeStatus: Upgraded to focal on 2020-04-18 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mime-support/+bug/1878617/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876230] Re: liburcu: Enable MEMBARRIER_CMD_PRIVATE_EXPEDITED to address performance problems with MEMBARRIER_CMD_SHARED
This is a very tricky SRU to be reviewing. Not having too much expertise in RCU, I need to rely on the opinion of people with more experience in this regard. Performance improvements like these are certainly SRUable, but we need to make sure that all the regression potential is covered and behavior for existing users stays relatively the same - at least without any ill-effects. So Matthew, your analysis and rationale in #8 seems legit. The change also looks good, well documented and well contained. Also, the check for static-linking also seems to be reassuring. I think content-wise we're good to go here. What I'd like before we proceed is for Rafael to take a look at your analysis in comment #8 and say if that addresses his concerns as well (since as I said, I'd like someone with more expertise to also +1). @rafaeldtinoco could you take a look? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to liburcu in Ubuntu. https://bugs.launchpad.net/bugs/1876230 Title: liburcu: Enable MEMBARRIER_CMD_PRIVATE_EXPEDITED to address performance problems with MEMBARRIER_CMD_SHARED Status in liburcu package in Ubuntu: Fix Released Status in liburcu source package in Bionic: In Progress Bug description: [Impact] In Linux 4.3, a new syscall was defined, called "membarrier". This systemcall was defined specifically for use in userspace-rcu (liburcu) to speed up the fast path / reader side of the library. The original implementation in Linux 4.3 only supported the MEMBARRIER_CMD_SHARED subcommand of the membarrier syscall. MEMBARRIER_CMD_SHARED executes a memory barrier on all threads from all processes running on the system. When it exits, the userspace thread which called it is guaranteed that all running threads share the same world view in regards to userspace addresses which are consumed by readers and writers. The problem with MEMBARRIER_CMD_SHARED is system calls made in this fashion can block, since it deploys a barrier across all threads in a system, and some other threads can be waiting on blocking operations, and take time to reach the barrier. In Linux 4.14, this was addressed by adding the MEMBARRIER_CMD_PRIVATE_EXPEDITED command to the membarrier syscall. It only targets threads which share the same mm as the thread calling the membarrier syscall, aka, threads in the current process, and not all threads / processes in the system. Calls to membarrier with the MEMBARRIER_CMD_PRIVATE_EXPEDITED command are guaranteed non-blocking, due to using inter-processor interrupts to implement memory barriers. Because of this, membarrier calls that use MEMBARRIER_CMD_PRIVATE_EXPEDITED are much faster than those that use MEMBARRIER_CMD_SHARED. Since Bionic uses a 4.15 kernel, all kernel requirements are met, and this SRU is to enable support for MEMBARRIER_CMD_PRIVATE_EXPEDITED in the liburcu package. This brings the performance of the liburcu library back in line to where it was in Trusty, as this particular user has performance problems upon upgrading from Trusty to Bionic. [Test] Testing performance is heavily dependant on the application which links against liburcu, and the workload which it executes. A test package is available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf276198-test For the sake of testing, we can use the benchmarks provided in the liburcu source code. Download a copy of the source code for liburcu either from the repos or from github: $ pull-lp-source liburcu bionic # OR $ git clone https://github.com/urcu/userspace-rcu.git $ git checkout v0.10.1 # version in bionic Build the code: $ ./bootstrap $ ./configure $ make Go into the tests/benchmark directory $ cd tests/benchmark From there, you can run benchmarks for the four main usages of liburcu: urcu, urcu-bp, urcu-signal and urcu-mb. On a 8 core machine, 6 threads for readers and 2 threads for writers, with a 10 second runtime, execute: $ ./test_urcu 6 2 10 $ ./test_urcu_bp 6 2 10 $ ./test_urcu_signal 6 2 10 $ ./test_urcu_mb 6 2 10 Results: ./test_urcu 6 2 10 0.10.1-1: 17612527667 reads, 268 writes, 17612527935 ops 0.10.1-1ubuntu1: 14988437247 reads, 810069 writes, 14989247316 ops $ ./test_urcu_bp 6 2 10 0.10.1-1: 1177891079 reads, 1699523 writes, 1179590602 ops 0.10.1-1ubuntu1: 13230354737 reads, 575314 writes, 13230930051 ops $ ./test_urcu_signal 6 2 10 0.10.1-1: 20128392417 reads, 6859 writes, 20128399276 ops 0.10.1-1ubuntu1: 20501430707 reads, 6890 writes, 20501437597 ops $ ./test_urcu_mb 6 2 10 0.10.1-1: 627996563 reads, 5409563 writes, 633406126 ops 0.10.1-1ubuntu1: 653194752 reads, 4590020 writes, 657784772 ops The SRU only changes behaviour for urcu and urcu-bp, since they are the only "flavours" of liburcu which the patches change. From a pure ops standpoint: $
[Touch-packages] [Bug 1878482] Re: EPSON WF 3520 driver problem - PpdFiles: Error
What is the actual problem here? Is the printer model not found during setup? Are you not able to print? Could you follow the instructions on https://wiki.ubuntu.com/DebuggingPrintingProblems Thanks. ** Changed in: cups (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1878482 Title: EPSON WF 3520 driver problem - PpdFiles: Error Status in cups package in Ubuntu: Incomplete Bug description: doesn't work ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 13 23:17:35 2020 InstallationDate: Installed on 2020-05-06 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for Generic-ESC-P-Dot-Matrix: lpd://192.168.1.133:515/PASSTHRU Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 04f2:b413 Chicony Electronics Co., Ltd FJ Camera Bus 001 Device 002: ID 062a:4101 MosArt Semiconductor Corp. Wireless Keyboard/Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: FUJITSU LIFEBOOK A555 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Generic-ESC-P-Dot-Matrix.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Generic-ESC-P-Dot-Matrix.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=85a6cbd6-a8d0-4ee5-ac82-9f54acbb0106 ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2016 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: 1.21 dmi.board.name: FJNBB3E dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvr1.21:bd05/31/2016:svnFUJITSU:pnLIFEBOOKA555:pvr:rvnFUJITSU:rnFJNBB3E:rvr:cvnFUJITSU:ct10:cvr: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK A555 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1878482/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878322] Re: cupsaddsmb
cupsaddsmb got discontinued upstream. It is not part of the CUPS package any more. This happened in Dec 2018 already. Closing ... ** Changed in: cups (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1878322 Title: cupsaddsmb Status in cups package in Ubuntu: Invalid Bug description: this app is not into this package ! ubuntu server 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1878322/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0
** Package changed: linux-signed-5.4 (Ubuntu) => linux-signed (Ubuntu) ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-signed (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: Incomplete ** Also affects: systemd (Ubuntu Groovy) Importance: High Assignee: Balint Reczey (rbalint) Status: New ** Also affects: linux-signed (Ubuntu Groovy) Importance: Medium Assignee: Colin Ian King (colin-king) Status: New ** Tags removed: rls-ff-incoming rls-gg-incoming -- 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/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: New Status in systemd package in Ubuntu: New Status in linux source package in Focal: New Status in linux-signed source package in Focal: New Status in systemd source package in Focal: New Status in linux source package in Groovy: Incomplete Status in linux-signed source package in Groovy: New Status in systemd source package in Groovy: New Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861941/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878611] [NEW] accountsservice 0.6.55-0ubuntu12~20.04.1 update crashes into greeter
Public bug reported: When updating Ubuntu 20.04 to the current proposed updates with the accountsservice 0.6.55-0ubuntu12~20.04.1 update, the current gnome session crashes out reproducibly into the the gdm3 greeter. At that point, when you try to log back in, only the background color is displayed but no desktop or menus ever appears. One has to perform a hard reboot at this point to get back to a greeter that will successfully login. ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: New ** Description changed: When updating Ubuntu 20.04 to the current proposed updates with the accountsservice 0.6.55-0ubuntu12~20.04.1 update, the current gnome session crashes out reproducibly into the the gdm3 greeter. At that - point, when you try to log back in, the only background color is + point, when you try to log back in, only the background color is displayed but no desktop or menus ever appears. One has to perform a hard reboot at this point to get back to a greeter that will successfully login. -- 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/1878611 Title: accountsservice 0.6.55-0ubuntu12~20.04.1 update crashes into greeter Status in accountsservice package in Ubuntu: New Bug description: When updating Ubuntu 20.04 to the current proposed updates with the accountsservice 0.6.55-0ubuntu12~20.04.1 update, the current gnome session crashes out reproducibly into the the gdm3 greeter. At that point, when you try to log back in, only the background color is displayed but no desktop or menus ever appears. One has to perform a hard reboot at this point to get back to a greeter that will successfully login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1878611/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878611] Re: accountsservice 0.6.55-0ubuntu12~20.04.1 update crashes into greeter
I noticed that one of the changes in accountsservice 0.6.55-0ubuntu12~20.04.1 is... * Add patch to not crash in the library when the daemon goes away (Closes: #948228) (LP: #1843982) Does this imply that the existing accountsservice 0.6.55-0ubuntu11 package in 20.04 will crash during upgrades to the newer version due to the absence of this bug fix in the currently running daemon? -- 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/1878611 Title: accountsservice 0.6.55-0ubuntu12~20.04.1 update crashes into greeter Status in accountsservice package in Ubuntu: New Bug description: When updating Ubuntu 20.04 to the current proposed updates with the accountsservice 0.6.55-0ubuntu12~20.04.1 update, the current gnome session crashes out reproducibly into the the gdm3 greeter. At that point, when you try to log back in, only the background color is displayed but no desktop or menus ever appears. One has to perform a hard reboot at this point to get back to a greeter that will successfully login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1878611/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1659719] Re: ssh can't call a binary from a snap without the full path
+1, tweaking /etc/environment makes it work. It seems that this has to be fixed in the libpam-modules postinst script then. ** Changed in: pam (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1659719 Title: ssh can't call a binary from a snap without the full path Status in Snappy: Fix Committed Status in livecd-rootfs package in Ubuntu: Fix Committed Status in openssh package in Ubuntu: Confirmed Status in pam package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: ssh can't call a binary from a snap, it will only work using the full path. Let's say I have the hello snap installed in 192.168.122.24. Then: elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 hello elopio@192.168.122.24's password: bash: hello: command not found elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 /snap/bin/hello elopio@192.168.122.24's password: Hello, world! To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1659719/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
This bug is marked fixed release. As I suggested in comment #13, please file a new bug. This will allow you to use apport to upload any crash information/etc that will assist developers in fixing this. -- 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 Status in isc-dhcp source package in Focal: 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 1878702] Re: [UX530UX, Realtek ALC295, Speaker, Internal] No sound
** Summary changed: - [UX530UX, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card + [UX530UX, Realtek ALC295, Speaker, Internal] No sound -- 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/1878702 Title: [UX530UX, Realtek ALC295, Speaker, Internal] No sound Status in pulseaudio package in Ubuntu: New Bug description: After upgrading to 20.04 from 18.04, I cannot hear anything, music and videos. In Settings/Sound "System Volume" and "Volume Levels" are OK, I can decrease and increase the volume, but I don't hear anything. Only "Input Volume" has the Speaker icon a cross, but I can increase and decrease the level. 1. DistroRelease: Ubuntu 20.04 2. Package: pulseaudio 1:13.99.1-1ubuntu3.2 3. I expect hear music or video 4. None sound came from the computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 14 23:38:54 2020 InstallationDate: Installed on 2018-05-14 (731 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [UX530UX, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to focal on 2020-05-13 (1 days ago) dmi.bios.date: 03/03/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX530UX.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX530UX 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.:bvrUX530UX.301:bd03/03/2017:svnASUSTeKCOMPUTERINC.:pnUX530UX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX530UX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX530UX dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1878702/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04
** Changed in: linux-azure (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-gcp (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-kvm (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-oracle (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-riscv (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rtkit in Ubuntu. https://bugs.launchpad.net/bugs/1875665 Title: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04 Status in linux package in Ubuntu: Fix Committed Status in linux-azure package in Ubuntu: Invalid Status in linux-gcp package in Ubuntu: Invalid Status in linux-kvm package in Ubuntu: Invalid Status in linux-oracle package in Ubuntu: Invalid Status in linux-riscv package in Ubuntu: Invalid Status in rtkit package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Committed Status in linux-azure source package in Focal: Fix Committed Status in linux-gcp source package in Focal: Fix Committed Status in linux-kvm source package in Focal: Fix Committed Status in linux-oracle source package in Focal: Fix Committed Status in linux-riscv source package in Focal: Fix Committed Status in rtkit source package in Focal: Confirmed Bug description: SRU Justification Impact: CONFIG_RT_GROUP_SCHED was enabled in focal, except for the lowlatency kernel since we expected most RT users to use that kernel. However we are getting RT regressions with the generic kernel. Digging deeper into this option, it seems to be pretty specialized and to require quite a bit of workload-specific configuration/tuning to be useful, so it doesn't really seem to make sense for a general-purpose kernel. Fix: Turn this option back off. Test Case: See comment #4. Regression Potential: This was turned on to support some docker functionality, so this functionality will no longer be available. We've had this option off for all releases prior to focal, so this seems acceptable. --- These errors started right after upgrading to 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rtkit 0.12-4 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 10:31:43 2020 InstallationDate: Installed on 2019-06-18 (315 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rtkit UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876046] Re: [XPS L501X, Realtek ALC665, Speaker, Internal] "Analog Stereo" and "Build-in speaker" appears "unplugged/unavailable"
*** This bug is a duplicate of bug 1876065 *** https://bugs.launchpad.net/bugs/1876065 Thanks for the bug report. The regression in pulseaudio update 1:13.99.1-1ubuntu3.2 (particularly on some Dells) is already covered by bug 1878327 and bug 1876065 so we should use those. ** This bug has been marked a duplicate of bug 1876065 After unplug headphones and plug them again no sound can be heard -- 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/1876046 Title: [XPS L501X, Realtek ALC665, Speaker, Internal] "Analog Stereo" and "Build-in speaker" appears "unplugged/unavailable" Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrading from 19.04 to 20.04 sound did not work. "Analog Stereo" and "Build-in speaker" appears "unplugged/unavaiable". I can change it in volume control -> configuration to Analog Stereo Duplex (unplugged)(unavaiable) and sound does play, but after each reboot computer changes to Digital Stereo IEC985 and do not play sound until changed again. I did reinstall of alsa and pulse according to some forums but this didn't work. Before upgrade everything always worked out of the box since 2009 on this computer. I know it's a little old but it works excellent! Please help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kwiatek1472 F pulseaudio /dev/snd/controlC0: kwiatek1472 F pulseaudio /dev/snd/pcmC0D0c: kwiatek1472 F...m pulseaudio /dev/snd/pcmC0D0p: kwiatek1472 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Apr 30 09:25:27 2020 InstallationDate: Installed on 2020-02-25 (64 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kwiatek1472 F pulseaudio /dev/snd/controlC0: kwiatek1472 F pulseaudio /dev/snd/pcmC0D0c: kwiatek1472 F...m pulseaudio /dev/snd/pcmC0D0p: kwiatek1472 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [XPS L501X, Realtek ALC665, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to focal on 2020-04-25 (4 days ago) dmi.bios.date: 07/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd07/26/2011:svnDellInc.:pnXPSL501X:pvrA08:rvnDellInc.:rn:rvrA08:cvnDellInc.:ct8:cvrA08: dmi.product.name: XPS L501X dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876046/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876065] Re: After unplug headphones and plug them again no sound can be heard
Git is only for developers. Please wait for the official update. -- 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/1876065 Title: After unplug headphones and plug them again no sound can be heard Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Focal: In Progress Status in pulseaudio source package in Groovy: Fix Committed Bug description: * Impact Sound isn't automatically redirected to headphones when those are connected to a jack interface * Test case Disconnect the headsets Start your webbrowser/music player/video player and play some sound Connect the headsets to the jack interface -> the sound should be directly redirected to the plugged headsets * Regression potential Check that audio routing when connecting/disconnecting devices to the hack entry is working correctly After startup with headset plugged in they play sound nicely - no issue. When they are unplugged, the sound is switched to the speaker (laptop) - all good. However, when I plug the headset back there is no sound. I see the app on pavucontrol, the volume is fine - everything looks fine except there is no sound. I dumped output of "pactl list" command on startup (headset plugged), after unplugging the headset, and when it is plugged back. From the comparison of these outputs, it looks like the source has got muted after the headset is plugged. Source #1 State: RUNNING Name: alsa_input.pci-_00_1f.3.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 7 Mute: yes Attached three outputs: headset-in.txt - after startup with headset plugged - all fine. headset-out.txt - after unplugged headset - sound through the speaker - all fine. headset-back.txt - after plugged headset back - no sound. Any help greatly appreciated. Regards, Roman To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876065/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1586771] Re: unable to On wifi (Air plane mode always ON) in ubuntu gnome 16.04.
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete => Expired -- 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/1586771 Title: unable to On wifi (Air plane mode always ON) in ubuntu gnome 16.04. Status in network-manager package in Ubuntu: Expired Bug description: Previously Wifi was in working condition By adding extra packages from software updates -> Additional Drivers. But now I can not able to connect with wifi. It only shows in Air Plane mode. I am using Laptop Thinkpad T520 OS = ubuntu gnome 16.04 Network card = Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] (Centrino Advanced-N 6205 AGN) Kernel version = 4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:46 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Thank you. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun May 29 18:26:15 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-16 (42 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) IpRoute: default via 192.168.1.1 dev enp0s25 proto static metric 100 169.254.0.0/16 dev enp0s25 scope link metric 1000 192.168.1.0/24 dev enp0s25 proto kernel scope link src 192.168.1.105 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH enp0s25 ethernet connected/org/freedesktop/NetworkManager/Devices/1 enp0s25 dacd31ad-8949-42a6-8115-142800960f1c /org/freedesktop/NetworkManager/ActiveConnection/0 wlp3s0 wifi unavailable /org/freedesktop/NetworkManager/Devices/0 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1586771/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1274857] Re: wi-fi continually fails to connect (after previous success)
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete => Expired -- 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/1274857 Title: wi-fi continually fails to connect (after previous success) Status in network-manager package in Ubuntu: Expired Bug description: Wi-fi had been working fine, but this morning, nothing doing. syslog shows many instances of: Activation (wlan0/wireless): association took too long, failing activation. Some info which may or may not be relevant: Removing the network and adding it made no difference. Deactivating, then reactivating the hardware wi-fi network switch made no difference. This was happening on two independent wi-fi networks (my hotel and the bluefin office) Rebooting fixed the issue. Closing the laptop did not reliably send it to sleep last night. Two competent Canonical engineers were unable to diagnose the problem. % lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 % uname -a Linux rog-ThinkPad-X220 3.13.0-2-generic #17-Ubuntu SMP Fri Jan 10 12:14:30 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux % lspci 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b4) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b4) 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b4) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b4) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation QM67 Express Chipset Family LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 04) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 04) 03:00.0 Network controller: Intel Corporation Centrino Wireless-N 1000 [Condor Peak] 0d:00.0 System peripheral: Ricoh Co Ltd MMC/SD Host Controller (rev 07) % I have attached my syslog starting just before the most recent successful connection until just before I rebooted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1274857/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876046] Re: [XPS L501X, Realtek ALC665, Speaker, Internal] "Analog Stereo" and "Build-in speaker" appears "unplugged/unavailable"
After today's upgrade: pulseaudio/focal-updates,focal-security,now 1:13.99.1-1ubuntu3.2 amd64 [installed] Sound stopped completely: "Establishing connection to pulseaudio. Please wait" - goes forever. How can I downgrade to pulseaudio-module-bluetooth_13.99.1-1ubuntu3? # sudo apt install pulseaudio=13.99.1-lubuntu3 This says Version '13.99.1-lubuntu3' for 'pulseaudio' was not found" despite this: Listing... Done pulseaudio/focal-updates,focal-security 1:13.99.1-1ubuntu3.2 amd64 pulseaudio/focal 1:13.99.1-1ubuntu3 amd64 Greetings -- 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/1876046 Title: [XPS L501X, Realtek ALC665, Speaker, Internal] "Analog Stereo" and "Build-in speaker" appears "unplugged/unavailable" Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrading from 19.04 to 20.04 sound did not work. "Analog Stereo" and "Build-in speaker" appears "unplugged/unavaiable". I can change it in volume control -> configuration to Analog Stereo Duplex (unplugged)(unavaiable) and sound does play, but after each reboot computer changes to Digital Stereo IEC985 and do not play sound until changed again. I did reinstall of alsa and pulse according to some forums but this didn't work. Before upgrade everything always worked out of the box since 2009 on this computer. I know it's a little old but it works excellent! Please help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kwiatek1472 F pulseaudio /dev/snd/controlC0: kwiatek1472 F pulseaudio /dev/snd/pcmC0D0c: kwiatek1472 F...m pulseaudio /dev/snd/pcmC0D0p: kwiatek1472 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Apr 30 09:25:27 2020 InstallationDate: Installed on 2020-02-25 (64 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kwiatek1472 F pulseaudio /dev/snd/controlC0: kwiatek1472 F pulseaudio /dev/snd/pcmC0D0c: kwiatek1472 F...m pulseaudio /dev/snd/pcmC0D0p: kwiatek1472 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [XPS L501X, Realtek ALC665, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to focal on 2020-04-25 (4 days ago) dmi.bios.date: 07/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd07/26/2011:svnDellInc.:pnXPSL501X:pvrA08:rvnDellInc.:rn:rvrA08:cvnDellInc.:ct8:cvrA08: dmi.product.name: XPS L501X dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876046/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878718] Re: Hotkey for switching display output unusable due to switching to next option immediately after release
Thanks for the bug report. I didn't know about that hotkey. On my system it is Super+P and only works when a secondary monitor is plugged in. Are you using Super+P or some function key unique to your model of laptop? ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Tags added: multimonitor -- 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/1878718 Title: Hotkey for switching display output unusable due to switching to next option immediately after release Status in mutter package in Ubuntu: Incomplete Bug description: Steps to reproduce: 1. Press the functional button for switching output to displays (joint, mirror, bulit-in, external) 2. The dialog is invoked What is expected: I should be able to select the desired option and confirm it What happened instead: While the functional button for invoking the dialog is pressed, it iterates extremely fast over the options. I cannot control it. After releasing the key, the currently selected option is confirmed, which is effectively random. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01: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: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 15 01:28:30 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117GLM [Quadro T2000 Mobile / Max-Q] [10de:1fb8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU117GLM [Quadro T2000 Mobile / Max-Q] [103c:8611] InstallationDate: Installed on 2020-05-11 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ZBook 15 G6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=9895584a-6648-494d-9d91-e64ba192dd95 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2019 dmi.bios.vendor: HP dmi.bios.version: R92 Ver. 01.02.01 dmi.board.name: 860F dmi.board.vendor: HP dmi.board.version: KBC Version 65.23.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR92Ver.01.02.01:bd09/25/2019:svnHP:pnHPZBook15G6:pvr:rvnHP:rn860F:rvrKBCVersion65.23.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook 15 dmi.product.name: HP ZBook 15 G6 dmi.product.sku: 6CJ09AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-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+git20200226-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/1878718/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1862797] Re: Systemd does not allow hibernation when Chrome/chromium is running
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- 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/1862797 Title: Systemd does not allow hibernation when Chrome/chromium is running Status in systemd package in Ubuntu: Expired Bug description: 1/ Linux Mint 19.3/Ubuntu Bionic 18.04 LTS 2/ systemd: Installed: 237-3ubuntu10.38 3/ & 4/ Problem: hibernation stops working as soon as you start Chromium Steps to reproduce $ busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager CanSuspend s "yes" $ busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager CanHibernate s "yes" start chromium $ busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager CanHibernate s "na" $ sudo systemctl hibernate Failed to hibernate system via logind: Sleep verb not supported When this happens Cinnamon/Gnome no longer show hibernate buttons of course. $ systemd-inhibit --list Who: ecotech (UID 1000/ecotech, PID 1607/csd-media-keys) What: handle-power-key:handle-suspend-key:handle-hibernate-key Why: Cinnamon handling keypresses Mode: block Who: ModemManager (UID 0/root, PID 996/ModemManager) What: sleep Why: ModemManager needs to reset devices Mode: delay Who: ecotech (UID 1000/ecotech, PID 1656/csd-power) What: sleep Why: Cinnamon needs to lock the screen Mode: delay Who: ecotech (UID 1000/ecotech, PID 1656/csd-power) What: handle-lid-switch Why: Multiple displays attached Mode: block Who: NetworkManager (UID 0/root, PID 1012/NetworkManager) What: sleep Why: NetworkManager needs to turn off networks Mode: delay Who: UPower (UID 0/root, PID 1279/upowerd) What: sleep Why: Pause device polling Mode: delay Systemd-inhibit does not mention anything Chrome/Chromium related Stop Chromium and hibernation works again. Similar issues found: https://bugzilla.redhat.com/show_bug.cgi?id=1346908 $ cat /sys/power/state freeze mem disk $ cat /sys/power/disk [platform] shutdown reboot suspend test_resume Tried logind.conf default (all commented out) and below. No difference. $ cat /etc/systemd/logind.conf [Login] #NAutoVTs=6 #ReserveVT=6 #KillUserProcesses=no #KillOnlyUsers= #KillExcludeUsers=root #InhibitDelayMaxSec=5 HandlePowerKey=poweroff HandleSuspendKey=suspend HandleHibernateKey=hibernate #HandleLidSwitch=suspend #HandleLidSwitchDocked=ignore PowerKeyIgnoreInhibited=no #SuspendKeyIgnoreInhibited=no HibernateKeyIgnoreInhibited=no #LidSwitchIgnoreInhibited=yes #HoldoffTimeoutSec=30s #IdleAction=ignore #IdleActionSec=30min #RuntimeDirectorySize=10% #RemoveIPC=yes #InhibitorsMax=8192 #SessionsMax=8192 #UserTasksMax=33% Can also not file a bug @ https://github.com/systemd/system since my version is more than 2 versions older than the last version (2.44.1). Thanks in advance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1862797/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1827253] Proposed package removed from archive
The version of rsyslog in the proposed pocket of Bionic that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1827253 Title: [apparmor] missing 'mr' on binary for usage on containers Status in rsyslog package in Ubuntu: Fix Released Status in rsyslog source package in Bionic: In Progress Status in rsyslog source package in Disco: In Progress Status in rsyslog source package in Eoan: In Progress Bug description: [Impact] * rsyslog ships with a (Default disable) apparmor profile. * Security sensitive users are in general encouraged to enable such profiles but unfortunately due to slightly new behavior of the program the profile prevents its usage. * Allow the program to map/read its binary to get this working again [Test Case] 1) Create a 'eoan' container called rs1 here: lxc launch ubuntu-daily:e rs1 2) Enter the container lxc shell rs1 3) Enable apparmor profile rm /etc/apparmor.d/disable/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog 4) notice rsyslog failed to start systemctl status rsyslog [Regression Potential] * This is just opening up the apparmor profile a bit. Therefore the only regression it could cause IMHO is a security issue. But then what it actually allows is reading (not writing!) its own binary which should be very safe. * Thinking further it came to my mind that package updates (independent to the change) might restart services and that means if there is any issue e.g. in a local config that worked but now fails (not by this change but in general) then the upgrade will not cause, but trigger this. This is a general regression risk for any upload, but in this case worth to mention as it is about log handling - which if broken - makes large scale systems hard to debug. [Other Info] * n/a --- Issue description: Enabling the rsyslog (disabled by default) Apparmor profile causes rsyslog to fail to start when running *inside a container*. Steps to reproduce: 1) Create a 'eoan' container called rs1 here: lxc launch ubuntu-daily:e rs1 2) Enter the container lxc shell rs1 3) Enable apparmor profile rm /etc/apparmor.d/disable/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog 4) notice rsyslog failed to start systemctl status rsyslog Workaround: echo ' /usr/sbin/rsyslogd mr,' >> /etc/apparmor.d/local/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog Additional information: root@rs1:~# uname -a Linux rs1 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@rs1:~# lsb_release -rd Description: Ubuntu Eoan EANIMAL (development branch) Release: 19.10 root@rs1:~# dpkg -l| grep -wE 'apparmor|rsyslog' ii apparmor 2.13.2-9ubuntu6 amd64user-space parser utility for AppArmor ii rsyslog 8.32.0-1ubuntu7 amd64reliable system and kernel logging daemon ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: rsyslog 8.32.0-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Wed May 1 17:36:29 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1827253/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1827253] Proposed package removed from archive
The version of rsyslog in the proposed pocket of Bionic that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1827253 Title: [apparmor] missing 'mr' on binary for usage on containers Status in rsyslog package in Ubuntu: Fix Released Status in rsyslog source package in Bionic: In Progress Status in rsyslog source package in Disco: In Progress Status in rsyslog source package in Eoan: In Progress Bug description: [Impact] * rsyslog ships with a (Default disable) apparmor profile. * Security sensitive users are in general encouraged to enable such profiles but unfortunately due to slightly new behavior of the program the profile prevents its usage. * Allow the program to map/read its binary to get this working again [Test Case] 1) Create a 'eoan' container called rs1 here: lxc launch ubuntu-daily:e rs1 2) Enter the container lxc shell rs1 3) Enable apparmor profile rm /etc/apparmor.d/disable/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog 4) notice rsyslog failed to start systemctl status rsyslog [Regression Potential] * This is just opening up the apparmor profile a bit. Therefore the only regression it could cause IMHO is a security issue. But then what it actually allows is reading (not writing!) its own binary which should be very safe. * Thinking further it came to my mind that package updates (independent to the change) might restart services and that means if there is any issue e.g. in a local config that worked but now fails (not by this change but in general) then the upgrade will not cause, but trigger this. This is a general regression risk for any upload, but in this case worth to mention as it is about log handling - which if broken - makes large scale systems hard to debug. [Other Info] * n/a --- Issue description: Enabling the rsyslog (disabled by default) Apparmor profile causes rsyslog to fail to start when running *inside a container*. Steps to reproduce: 1) Create a 'eoan' container called rs1 here: lxc launch ubuntu-daily:e rs1 2) Enter the container lxc shell rs1 3) Enable apparmor profile rm /etc/apparmor.d/disable/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog 4) notice rsyslog failed to start systemctl status rsyslog Workaround: echo ' /usr/sbin/rsyslogd mr,' >> /etc/apparmor.d/local/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog Additional information: root@rs1:~# uname -a Linux rs1 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@rs1:~# lsb_release -rd Description: Ubuntu Eoan EANIMAL (development branch) Release: 19.10 root@rs1:~# dpkg -l| grep -wE 'apparmor|rsyslog' ii apparmor 2.13.2-9ubuntu6 amd64user-space parser utility for AppArmor ii rsyslog 8.32.0-1ubuntu7 amd64reliable system and kernel logging daemon ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: rsyslog 8.32.0-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Wed May 1 17:36:29 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1827253/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1877580] Re: [Latitude 7490, Realtek ALC3246, Black Headphone Out, Front] No sound at all
Checking a bit more, I've realized the following: - After a reboot, the microphone is not detected and nothing is proposed in pavucontrol - If I plug any headphone (3-pins without mic) then the "Internal microphone" device appears. Which doesn't also don't work (neither output nor input). After unplugging the headphone, sometimes the mic starts working despite manually selecting it. I cannot find the combination to make the mic work all the time. - If I plug a headset with (4-pins including mic) when the Input device is changed to Port: Headset Microphone (plugged in) in pavucontrol, and I get sound on the headphones only on the left channel. Strangely enough if I change the microphone setting I lose the sound again, why the input should affect the output. - USB headset with microphone works both ok. -- 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/1877580 Title: [Latitude 7490, Realtek ALC3246, Black Headphone Out, Front] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: After upgrade from 19.10 to 20.04 (xubuntu) I've lost the sound on the headphones. The internal loud speakers works ok when the headphones are not plugged in. More specifically: If I open the pavucontrol without the headphones plugged in I see that is correctly mentioning the output as Port: "Speakers (plugged-in)" and everything works ok, I have sound from the speakers. The moment I plug in the headphones, for a fraction of a second I can hear sound on the headphones, and then the output port switches to "headphones" which is the moment I lose the sound. The fraction that I hear the sound is when the jack is half-inserted and I get the sound on one channel only. When is fully inserted, the computer detects it and makes the switch. I've tried also in alsamixer all possibilities I could imagine, playing with mute/unmute and gain of each channel, with no success ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bnv1312 F pulseaudio bnv 21367 F alsamixer /dev/snd/pcmC0D0c: bnv1312 F...m pulseaudio /dev/snd/pcmC0D0p: bnv1312 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri May 8 15:41:08 2020 InstallationDate: Installed on 2019-08-08 (274 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bnv1312 F pulseaudio bnv 21367 F alsamixer /dev/snd/pcmC0D0c: bnv1312 F...m pulseaudio /dev/snd/pcmC0D0p: bnv1312 F...m pulseaudio Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [Latitude 7490, Realtek ALC3246, Black Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0KP0FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd11/08/2019:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.product.sku: 081C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1877580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878527] Re: "Dummy Output" as Audio Device in Ubuntu settings - Ubuntu 20.04.
** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Invalid -- 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/1878527 Title: "Dummy Output" as Audio Device in Ubuntu settings - Ubuntu 20.04. Status in pulseaudio package in Ubuntu: Invalid Bug description: Hi All As soon as i boot to OS, my sound device is shown as "Dummy Output". i wait for 10 to 15 minutes and run below commands and then, it kills few processes and sound starts working. I have to do this step every time system is rebooted. # pulseaudio --kill; sleep 2s; sudo alsa force-reload ; pulseaudio --start Thanks. RD ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.3.0-7625.27~1576774585~18.04~c7868f8-generic 5.3.13 Uname: Linux 5.3.0-7625-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 14 09:39:15 2020 InstallationDate: Installed on 2018-07-12 (671 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-04-28 (15 days ago) dmi.bios.date: 12/04/2018 dmi.bios.vendor: System76 dmi.bios.version: 1.07.11RSA4-1 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp4 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnSystem76:bvr1.07.11RSA4-1:bd12/04/2018:svnSystem76:pnOryxPro:pvroryp4:rvnSystem76:rnOryxPro:rvroryp4:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp4 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1878527/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878527] Re: "Dummy Output" as Audio Device in Ubuntu settings - Ubuntu 20.04.
Hi Daniel Thanks for your response/suggestion. Both packages are installed in my system and i have removed and rebooted the system. Sound started working. Thanks again. Removed packages :: jackd timidity Thanks again. -- 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/1878527 Title: "Dummy Output" as Audio Device in Ubuntu settings - Ubuntu 20.04. Status in pulseaudio package in Ubuntu: Incomplete Bug description: Hi All As soon as i boot to OS, my sound device is shown as "Dummy Output". i wait for 10 to 15 minutes and run below commands and then, it kills few processes and sound starts working. I have to do this step every time system is rebooted. # pulseaudio --kill; sleep 2s; sudo alsa force-reload ; pulseaudio --start Thanks. RD ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.3.0-7625.27~1576774585~18.04~c7868f8-generic 5.3.13 Uname: Linux 5.3.0-7625-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 14 09:39:15 2020 InstallationDate: Installed on 2018-07-12 (671 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-04-28 (15 days ago) dmi.bios.date: 12/04/2018 dmi.bios.vendor: System76 dmi.bios.version: 1.07.11RSA4-1 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp4 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnSystem76:bvr1.07.11RSA4-1:bd12/04/2018:svnSystem76:pnOryxPro:pvroryp4:rvnSystem76:rnOryxPro:rvroryp4:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp4 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1878527/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1875708] Re: Truncated messages in journald since systemd v244
** Changed in: systemd (Ubuntu) Importance: Undecided => High ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Balint Reczey (rbalint) ** Changed in: systemd (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1875708 Title: Truncated messages in journald since systemd v244 Status in libvirt package in Ubuntu: Invalid Status in systemd package in Ubuntu: In Progress Bug description: [Impact] * since 09d0b46a "journal: refresh cached credentials of stdout streams" in ~244 output may be trincated. * Upstream has a fix in https://github.com/systemd/systemd/pull/15685 * Backporting the fix will avoid truncation of log output to journald [Test Case] * This could happen in any case, but is more likely when a program that has output going to journald is spawning short-lived sub-programs often. Therefore the test emphasizes on that: - Use a test service like /etc/systemd/system/test.service: [Unit] Description=Test Truncate After=network.target [Service] ExecStart=/usr/lib/test.sh long-test-for-start ExecStop=/usr/lib/test.sh long-test-for-stop Type=oneshot RemainAfterExit=yes StandardOutput=journal+console TimeoutStopSec=0 [Install] WantedBy=multi-user.target - And a test script like /usr/lib/test.sh: #!/bin/sh gettext "This will" echo gettext "usually fail" echo gettext "and be truncated" echo Start/Stopping that service without the fix will look like: Apr 30 18:56:40 f systemd[1]: Stopping Test Truncate... Apr 30 18:56:40 f test.sh[1165]: T Apr 30 18:56:40 f test.sh[1167]: T Apr 30 18:56:40 f test.sh[1167]: sually fai Apr 30 18:56:40 f test.sh[1165]: s Apr 30 18:56:40 f test.sh[1168]: s Apr 30 18:56:40 f test.sh[1168]: nd be truncate Apr 30 18:56:40 f test.sh[1165]: n Apr 30 18:56:40 f systemd[1]: test.service: Succeeded. Apr 30 18:56:40 f systemd[1]: Stopped Test Truncate. [Regression Potential] * The patches are rather small, but there might be a slightly increased memory consumption of journald for output buffers. * Issues (if any and I couldn't find any so far) should be only to journald output handling. Systemd is huge, this at least narrows down the potential places of a regression a lot. [Other Info] * n/a --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- Originally reported against libvirt which happens to be one of the example-triggers Hi, when I shut down my machine I see messages from /usr/lib/libvirt /libvirt-guests.sh but there are 2 anomalies: - 3 libvirt-guests.sh processes are run - messages are truncated ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libvirt-daemon 6.0.0-0ubuntu8 Uname: Linux 5.6.7-050607-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Apr 28 19:42:56 2020 SourcePackage: libvirt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.libvirt.nwfilter.allow-arp.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-arp.xml'] modified.conffile..etc.libvirt.nwfilter.allow-dhcp-server.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp-server.xml'] modified.conffile..etc.libvirt.nwfilter.allow-dhcp.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp.xml'] modified.conffile..etc.libvirt.nwfilter.allow-incoming-ipv4.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-incoming-ipv4.xml'] modified.conffile..etc.libvirt.nwfilter.allow-ipv4.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-ipv4.xml'] modified.conffile..etc.libvirt.nwfilter.clean-traffic-gateway.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/clean-traffic-gateway.xml'] modified.conffile..etc.libvirt.nwfilter.clean-traffic.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/clean-traffic.xml'] modified.conffile..etc.libvirt.nwfilter.no-arp-ip-spoofing.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-arp-ip-spoofing.xml'] modified.conffile..etc.libvirt.nwfilter.no-arp-mac-spoofing.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-arp-mac-spoofing.xml'] modified.conffile..etc.libvirt.nwfilter.no-arp-spoofing.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-arp-spoofing.xml'] modified.conffile..etc.libvirt.nwfilter.no-ip-multicast.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-ip-multicast.xml'] modified.conffile..etc.libvirt.nwfilter.no-ip-spoofing.xml: [inaccessible: [Errno 13]
[Touch-packages] [Bug 1875708] Re: Truncated messages in journald since systemd v244
This is now merged upstream. Eventually https://github.com/systemd/systemd/pull/15801 was the PR that got merged. I'd ask to backport those to Groovy/Focal to fix this kind of output truncation. -- 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/1875708 Title: Truncated messages in journald since systemd v244 Status in libvirt package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Bug description: [Impact] * since 09d0b46a "journal: refresh cached credentials of stdout streams" in ~244 output may be trincated. * Upstream has a fix in https://github.com/systemd/systemd/pull/15685 * Backporting the fix will avoid truncation of log output to journald [Test Case] * This could happen in any case, but is more likely when a program that has output going to journald is spawning short-lived sub-programs often. Therefore the test emphasizes on that: - Use a test service like /etc/systemd/system/test.service: [Unit] Description=Test Truncate After=network.target [Service] ExecStart=/usr/lib/test.sh long-test-for-start ExecStop=/usr/lib/test.sh long-test-for-stop Type=oneshot RemainAfterExit=yes StandardOutput=journal+console TimeoutStopSec=0 [Install] WantedBy=multi-user.target - And a test script like /usr/lib/test.sh: #!/bin/sh gettext "This will" echo gettext "usually fail" echo gettext "and be truncated" echo Start/Stopping that service without the fix will look like: Apr 30 18:56:40 f systemd[1]: Stopping Test Truncate... Apr 30 18:56:40 f test.sh[1165]: T Apr 30 18:56:40 f test.sh[1167]: T Apr 30 18:56:40 f test.sh[1167]: sually fai Apr 30 18:56:40 f test.sh[1165]: s Apr 30 18:56:40 f test.sh[1168]: s Apr 30 18:56:40 f test.sh[1168]: nd be truncate Apr 30 18:56:40 f test.sh[1165]: n Apr 30 18:56:40 f systemd[1]: test.service: Succeeded. Apr 30 18:56:40 f systemd[1]: Stopped Test Truncate. [Regression Potential] * The patches are rather small, but there might be a slightly increased memory consumption of journald for output buffers. * Issues (if any and I couldn't find any so far) should be only to journald output handling. Systemd is huge, this at least narrows down the potential places of a regression a lot. [Other Info] * n/a --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- Originally reported against libvirt which happens to be one of the example-triggers Hi, when I shut down my machine I see messages from /usr/lib/libvirt /libvirt-guests.sh but there are 2 anomalies: - 3 libvirt-guests.sh processes are run - messages are truncated ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libvirt-daemon 6.0.0-0ubuntu8 Uname: Linux 5.6.7-050607-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Apr 28 19:42:56 2020 SourcePackage: libvirt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.libvirt.nwfilter.allow-arp.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-arp.xml'] modified.conffile..etc.libvirt.nwfilter.allow-dhcp-server.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp-server.xml'] modified.conffile..etc.libvirt.nwfilter.allow-dhcp.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp.xml'] modified.conffile..etc.libvirt.nwfilter.allow-incoming-ipv4.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-incoming-ipv4.xml'] modified.conffile..etc.libvirt.nwfilter.allow-ipv4.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-ipv4.xml'] modified.conffile..etc.libvirt.nwfilter.clean-traffic-gateway.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/clean-traffic-gateway.xml'] modified.conffile..etc.libvirt.nwfilter.clean-traffic.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/clean-traffic.xml'] modified.conffile..etc.libvirt.nwfilter.no-arp-ip-spoofing.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-arp-ip-spoofing.xml'] modified.conffile..etc.libvirt.nwfilter.no-arp-mac-spoofing.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-arp-mac-spoofing.xml'] modified.conffile..etc.libvirt.nwfilter.no-arp-spoofing.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-arp-spoofing.xml'] modified.conffile..etc.libvirt.nwfilter.no-ip-multicast.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-ip-multicast.xml'] modified.conffile..etc.libvirt.nwfilter.no-ip-spoofing.xml: [inaccessible: [Errno 13] Permission denied:
[Touch-packages] [Bug 1878587] Re: pk-client-error-quarl could not get lock when selecting driver from synaptic
Maybe you would like to set concerned package to "synaptic"... -- 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/1878587 Title: pk-client-error-quarl could not get lock when selecting driver from synaptic Status in software-properties package in Ubuntu: New Bug description: Steps to reproduce (Ubuntu 20.04, synaptic 0.84.6ubuntu5, software-properties-gtk 0.98.9) 1. Open synaptic 2. click in "parameters" menu, then "repositories". This will open a "Software and update" window 3. click on "additional drivers" tab 4. select a new driver (example : I have nvidia 435 installed, I select nvidia 440) 5. click apply Expected behaviour : the selected driver is installed Actual behaviour: you get an error window with message: "pk-client-error-quark: E: could not get lock /var/lib/dpkg/lock-front-end. It is held by process 9246 (synaptic)" Workaround: launch "software update" directly without synaptic I understand that synaptic must be closed in order to let another software updating process operate. But this software update has been initiated from synaptic and I cannot close synaptic when software update is opened. It is opened like a modal window... Ithink either this feature should be removed from synaptic or avtrick must be found to have it releasing the lock as long as the "software update" window it has triggered is opened; or maybe synaptic and software-update-gtk could share the lock in this situation ? For now it is impossible to install additional driver if you launched it from synaptic. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.9 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu May 14 11:34:44 2020 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2020-05-12 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterpreterPath: /usr/bin/python3.8 PackageArchitecture: all ProcEnviron: SHELL=/bin/bash LANG=fr_FR.UTF-8 PATH=(custom, no user) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2020-05-12 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1878587/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878587] [NEW] pk-client-error-quarl could not get lock when selecting driver from synaptic
Public bug reported: Steps to reproduce (Ubuntu 20.04, synaptic 0.84.6ubuntu5, software-properties-gtk 0.98.9) 1. Open synaptic 2. click in "parameters" menu, then "repositories". This will open a "Software and update" window 3. click on "additional drivers" tab 4. select a new driver (example : I have nvidia 435 installed, I select nvidia 440) 5. click apply Expected behaviour : the selected driver is installed Actual behaviour: you get an error window with message: "pk-client-error-quark: E: could not get lock /var/lib/dpkg/lock-front-end. It is held by process 9246 (synaptic)" Workaround: launch "software update" directly without synaptic I understand that synaptic must be closed in order to let another software updating process operate. But this software update has been initiated from synaptic and I cannot close synaptic when software update is opened. It is opened like a modal window... Ithink either this feature should be removed from synaptic or avtrick must be found to have it releasing the lock as long as the "software update" window it has triggered is opened; or maybe synaptic and software-update-gtk could share the lock in this situation ? For now it is impossible to install additional driver if you launched it from synaptic. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.9 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu May 14 11:34:44 2020 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2020-05-12 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterpreterPath: /usr/bin/python3.8 PackageArchitecture: all ProcEnviron: SHELL=/bin/bash LANG=fr_FR.UTF-8 PATH=(custom, no user) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2020-05-12 (1 days ago) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "screenshot of error message with sofware_properties-gtk and synaptic opened." https://bugs.launchpad.net/bugs/1878587/+attachment/5371450/+files/bug_synaptic_software-properties-gtk.png -- 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/1878587 Title: pk-client-error-quarl could not get lock when selecting driver from synaptic Status in software-properties package in Ubuntu: New Bug description: Steps to reproduce (Ubuntu 20.04, synaptic 0.84.6ubuntu5, software-properties-gtk 0.98.9) 1. Open synaptic 2. click in "parameters" menu, then "repositories". This will open a "Software and update" window 3. click on "additional drivers" tab 4. select a new driver (example : I have nvidia 435 installed, I select nvidia 440) 5. click apply Expected behaviour : the selected driver is installed Actual behaviour: you get an error window with message: "pk-client-error-quark: E: could not get lock /var/lib/dpkg/lock-front-end. It is held by process 9246 (synaptic)" Workaround: launch "software update" directly without synaptic I understand that synaptic must be closed in order to let another software updating process operate. But this software update has been initiated from synaptic and I cannot close synaptic when software update is opened. It is opened like a modal window... Ithink either this feature should be removed from synaptic or avtrick must be found to have it releasing the lock as long as the "software update" window it has triggered is opened; or maybe synaptic and software-update-gtk could share the lock in this situation ? For now it is impossible to install additional driver if you launched it from synaptic. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.9 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu May 14 11:34:44 2020 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2020-05-12 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterpreterPath: /usr/bin/python3.8 PackageArchitecture: all ProcEnviron: SHELL=/bin/bash LANG=fr_FR.UTF-8 PATH=(custom, no user) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2020-05-12 (1 days ago) To manage
[Touch-packages] [Bug 1843476] Re: running `apt download atop` ; `sudo dpkg -x atop_2.4.0-3_amd64.deb /` kills the system
** Tags added: focal ** Also affects: base-files (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1843476 Title: running `apt download atop` ; `sudo dpkg -x atop_2.4.0-3_amd64.deb /` kills the system Status in base-files package in Ubuntu: New Status in dpkg package in Ubuntu: New Bug description: Steps to reproduce: 1. Have Ubuntu 19.10 installed 2. Ensure that all dependencies for needed packages are satisfied: $ apt install -s atop NOTE: This is only a simulation! apt needs root privileges for real execution. Keep also in mind that locking is deactivated, so don't depend on the relevance to the real current situation! Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: atop 0 upgraded, 1 newly installed, 0 to remove and 199 not upgraded. Inst atop (2.4.0-3 Ubuntu:19.10/eoan [amd64]) Conf atop (2.4.0-3 Ubuntu:19.10/eoan [amd64]) 3. Download the package with `apt download atop` 4. Extract the package by hand with `sudo dpkg -x atop_2.4.0-3_amd64.deb /` (this is needed if system is broken and it is used in practice; atop is just an example) Expected results: package is extracted normally Actual results: package is extracted, but system is killed - unable to use `sudo` and many other commands - $ sudo bash: /usr/bin/sudo: No such file or directory $ bash bash: /usr/bin/bash: No such file or directory $ dash bash: /usr/bin/dash: No such file or directory $ systemctl bash: /usr/bin/systemctl: No such file or directory $ journalctl bash: /usr/bin/journalctl: No such file or directory $ ip a bash: /usr/sbin/ip: No such file or directory $ ldd bash: /usr/bin/ldd: /bin/bash: bad interpreter: No such file or directory $ mc bash: /usr/lib/command-not-found: /usr/bin/python3: bad interpreter: No such file or directory $ python bash: /usr/bin/python: No such file or directory $ apt bash: /usr/bin/apt: No such file or directory ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: dpkg 1.19.7ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: MATE Date: Tue Sep 10 21:25:58 2019 InstallationDate: Installed on 2019-09-06 (4 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Alpha amd64 (20190906) SourcePackage: dpkg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1843476/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878707] [NEW] Openconnect provided DNS servers are not read by NetworkManager
Public bug reported: If I connect using openconnect comamnd line, all works fine! If I add connection to NetworkManager, when I connect, I loose dns, and with that, all connectivity! PS: worked without issue on 19.10 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1878707 Title: Openconnect provided DNS servers are not read by NetworkManager Status in network-manager package in Ubuntu: New Bug description: If I connect using openconnect comamnd line, all works fine! If I add connection to NetworkManager, when I connect, I loose dns, and with that, all connectivity! PS: worked without issue on 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878702] [NEW] [UX530UX, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card
Public bug reported: After upgrading to 20.04 from 18.04, I cannot hear anything, music and videos. In Settings/Sound "System Volume" and "Volume Levels" are OK, I can decrease and increase the volume, but I don't hear anything. Only "Input Volume" has the Speaker icon a cross, but I can increase and decrease the level. 1. DistroRelease: Ubuntu 20.04 2. Package: pulseaudio 1:13.99.1-1ubuntu3.2 3. I expect hear music or video 4. None sound came from the computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 14 23:38:54 2020 InstallationDate: Installed on 2018-05-14 (731 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [UX530UX, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to focal on 2020-05-13 (1 days ago) dmi.bios.date: 03/03/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX530UX.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX530UX 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.:bvrUX530UX.301:bd03/03/2017:svnASUSTeKCOMPUTERINC.:pnUX530UX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX530UX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX530UX dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** 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/1878702 Title: [UX530UX, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: New Bug description: After upgrading to 20.04 from 18.04, I cannot hear anything, music and videos. In Settings/Sound "System Volume" and "Volume Levels" are OK, I can decrease and increase the volume, but I don't hear anything. Only "Input Volume" has the Speaker icon a cross, but I can increase and decrease the level. 1. DistroRelease: Ubuntu 20.04 2. Package: pulseaudio 1:13.99.1-1ubuntu3.2 3. I expect hear music or video 4. None sound came from the computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 14 23:38:54 2020 InstallationDate: Installed on 2018-05-14 (731 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [UX530UX, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to focal on 2020-05-13 (1 days ago) dmi.bios.date: 03/03/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX530UX.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX530UX 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.:bvrUX530UX.301:bd03/03/2017:svnASUSTeKCOMPUTERINC.:pnUX530UX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX530UX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX530UX dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to:
[Touch-packages] [Bug 1878686] Re: GNOME Settings crashes when clicking "Sign In / Register..." on Livepatch tab of Software & Updates
*** This bug is a duplicate of bug 1862553 *** https://bugs.launchpad.net/bugs/1862553 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 1862553), 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 1862553 gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget() -- 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/1878686 Title: GNOME Settings crashes when clicking "Sign In / Register..." on Livepatch tab of Software & Updates Status in gnome-control-center package in Ubuntu: New Status in software-properties package in Ubuntu: New Bug description: GNOME Settings seems to crash when clicking the "Sign In / Register..." button that is available after clicking "Sign In..." on the Livepatch tab of Software & Updates. It seems to happen only one time on a clean, fully updated installation of Ubuntu 20.04. When clicking the button next time, it seems to work fine and correctly opens the Ubuntu Single Sign-On login dialog of GNOME Settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1878686/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network
autopkgtest analysis for focal: prometheus fails in all archs due to bug 1878709 (ignore) gvfs (arm64) is flaky, test retried (ignore if it fails again) -- 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/1860926 Title: Ubuntu 20.04 Systemd fails to configure bridged network Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Status in systemd source package in Eoan: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Released Bug description: [impact] A bridged interface with static ipv4 address and gateway configuration will fail to properly add the route via the gateway, leaving the system without a globally working network. [test case] On a Focal system, remove all network configuration and create this netplan: network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false bridges: br0: interfaces: [enp4s0] dhcp4: no addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] Replace the interface name 'enp4s0' with the actual interface name on the test system. Reboot the system, and check the route to the gateway, which will be missing: root@lp1860926-f:~# ip r 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 The route is expected to be present, e.g.: ubuntu@lp1860926-e:~$ ip r default via 192.168.0.1 dev br0 proto static 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 [test case, pre-focal] same netplan as above, but remove ethernets: section. Reboot, and the bridge should have its address and route: ubuntu@test-e:~$ ip a show br0 3: br0: mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff inet 192.168.0.4/24 brd 192.168.0.255 scope global br0 valid_lft forever preferred_lft forever ubuntu@test-e:~$ ip r default via 192.168.0.1 dev br0 proto static linkdown 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 linkdown add and remove carrier, by adding and removing a slave interface: ubuntu@test-e:~$ sudo ip l set dev ens3 master br0 up ubuntu@test-e:~$ ip a show br0 3: br0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff inet 192.168.0.4/24 brd 192.168.0.255 scope global br0 valid_lft forever preferred_lft forever inet6 fe80::5411:daff:fe23:bb93/64 scope link valid_lft forever preferred_lft forever ubuntu@test-e:~$ sudo ip l set dev ens3 nomaster the bridge no longer has its address after losing carrier: ubuntu@test-e:~$ ip a show br0 3: br0: mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff inet6 fe80::5411:daff:fe23:bb93/64 scope link valid_lft forever preferred_lft forever [regression potential] Any regression would likely involve incorrectly configured network after an interface carrier gain/loss. [scope] This is needed for Focal, Eoan, and Bionic. While this only reproduces at boot for Focal, the general loss of configuration on carrier loss even when ConfigureWithoutCarrier=true is reproducable on all releases except Xenial, which does not have the ConfigureWithoutCarrier= parameter. [original description] Freshly installed Ubuntu 20.04 fully patched to days date with static IP address works fine and survives a reboot network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] however when converted to a bridged network for kvm network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false bridges: br0: interfaces: [enp4s0] dhcp4: no addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] will not survive a reboot and required systemd-network to be restarted or @reboot /usr/sbin/netplan apply added to the crontab after a reboot the network can not b eaccseed and a systemctl status systemd-networkd produces systemd-networkd.service - Network Service Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2020-01-26 16:36:28 UTC; 2min 27s ago TriggeredBy: ●
[Touch-packages] [Bug 1878718] [NEW] Hotkey for switching display output unusable due to switching to next option immediately after release
Public bug reported: Steps to reproduce: 1. Press the functional button for switching output to displays (joint, mirror, bulit-in, external) 2. The dialog is invoked What is expected: I should be able to select the desired option and confirm it What happened instead: While the functional button for invoking the dialog is pressed, it iterates extremely fast over the options. I cannot control it. After releasing the key, the currently selected option is confirmed, which is effectively random. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01: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: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 15 01:28:30 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117GLM [Quadro T2000 Mobile / Max-Q] [10de:1fb8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU117GLM [Quadro T2000 Mobile / Max-Q] [103c:8611] InstallationDate: Installed on 2020-05-11 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ZBook 15 G6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=9895584a-6648-494d-9d91-e64ba192dd95 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2019 dmi.bios.vendor: HP dmi.bios.version: R92 Ver. 01.02.01 dmi.board.name: 860F dmi.board.vendor: HP dmi.board.version: KBC Version 65.23.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR92Ver.01.02.01:bd09/25/2019:svnHP:pnHPZBook15G6:pvr:rvnHP:rn860F:rvrKBCVersion65.23.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook 15 dmi.product.name: HP ZBook 15 G6 dmi.product.sku: 6CJ09AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-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+git20200226-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 ** Attachment added: "Screencast from 2020-05-15 01:45:04.webm" https://bugs.launchpad.net/bugs/1878718/+attachment/5371766/+files/Screencast%20from%202020-05-15%2001%3A45%3A04.webm -- 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/1878718 Title: Hotkey for switching display output unusable due to switching to next option immediately after release Status in xorg package in Ubuntu: New Bug description: Steps to reproduce: 1. Press the functional button for switching output to displays (joint, mirror, bulit-in, external) 2. The dialog is invoked What is expected: I should be able to select the desired option and confirm it What happened instead: While the functional button for invoking the dialog is pressed, it iterates extremely fast over the options. I cannot control it. After releasing the key, the currently selected option is confirmed, which is effectively random. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01: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: ApportVersion:
[Touch-packages] [Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)
TL;DR TODO SUMMARY:
- netplan change to support KeepConfiguration= for systemd-networkd backend
(Groovy)
- backport this change: netplan for Ubuntu Focal (SRU)
- backport this change: netplan for Ubuntu Eoan (SRU, WontFix due to EOL ?)
- backport this change: netplan for Ubuntu Bionic (SRU)
- backport this change: netplan for Ubuntu Xenial (SRU, WontFix ?)
--
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/1815101
Title:
[master] Restarting systemd-networkd breaks keepalived, heartbeat,
corosync, pacemaker (interface aliases are restarted)
Status in netplan:
Confirmed
Status in heartbeat package in Ubuntu:
Won't Fix
Status in keepalived package in Ubuntu:
In Progress
Status in systemd package in Ubuntu:
In Progress
Status in keepalived source package in Xenial:
Confirmed
Status in systemd source package in Xenial:
Confirmed
Status in keepalived source package in Bionic:
Confirmed
Status in systemd source package in Bionic:
Confirmed
Status in systemd source package in Disco:
Won't Fix
Status in systemd source package in Eoan:
Fix Released
Status in keepalived source package in Focal:
Confirmed
Status in systemd source package in Focal:
Fix Released
Bug description:
[impact]
- ALL related HA software has a small problem if interfaces are being
managed by systemd-networkd: nic restarts/reconfigs are always going
to wipe all interfaces aliases when HA software is not expecting it to
(no coordination between them.
- keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is
smarter in this case because it has a service monitor that will
restart the virtual IP resource, in affected node & nic, before
considering a real failure, but other HA service might consider a real
failure when it is not.
[test case]
- comment #14 is a full test case: to have 3 node pacemaker, in that
example, and cause a networkd service restart: it will trigger a
failure for the virtual IP resource monitor.
- other example is given in the original description for keepalived.
both suffer from the same issue (and other HA softwares as well).
[regression potential]
- this backports KeepConfiguration parameter, which adds some
significant complexity to networkd's configuration and behavior, which
could lead to regressions in correctly configuring the network at
networkd start, or incorrectly maintaining configuration at networkd
restart, or losing network state at networkd stop.
- Any regressions are most likely to occur during networkd start,
restart, or stop, and most likely to involve missing or incorrect ip
address(es).
- the change is based in upstream patches adding the exact feature we
needed to fix this issue & it will be integrated with a netplan change
to add the needed stanza to systemd nic configuration file
(KeepConfiguration=)
[other info]
original description:
---
Configure netplan for interfaces, for example (a working config with
IP addresses obfuscated)
network:
ethernets:
eth0:
addresses: [192.168.0.5/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth2:
addresses:
- 12.13.14.18/29
- 12.13.14.19/29
gateway4: 12.13.14.17
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth3:
addresses: [10.22.11.6/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth4:
addresses: [10.22.14.6/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth7:
addresses: [9.5.17.34/29]
dhcp4: false
optional: true
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
version: 2
Configure keepalived (again, a working config with IP addresses
obfuscated)
global_defs # Block id
{
notification_email {
sysadm...@blah.com
}
notification_email_from keepali...@system3.hq.blah.com
smtp_server 10.22.11.7 # IP
smtp_connect_timeout 30 # integer, seconds
router_id system3 # string identifying the machine,
# (doesn't have
[Touch-packages] [Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)
@napsty: the "workaround" (from your blog) is actually to use: - ifupdown/bridge-utils/vlan/resolvconf for network setup OR - use systemd-networkd DIRECTLY with the KeepConfiguration= option in .network file Just highlighting it here. @ddstreet, you said you would try to come up with the netplan change for KeepConfiguration. Did you have time to check on this ? (just checking). Cheers o/ ** Changed in: keepalived (Ubuntu) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** Changed in: keepalived (Ubuntu Xenial) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** Changed in: keepalived (Ubuntu Bionic) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** Changed in: keepalived (Ubuntu Disco) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** Changed in: keepalived (Ubuntu Eoan) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** Changed in: systemd (Ubuntu) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** Changed in: systemd (Ubuntu Xenial) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** Changed in: systemd (Ubuntu Bionic) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** Changed in: systemd (Ubuntu Disco) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** Changed in: systemd (Ubuntu Eoan) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** Changed in: netplan Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** No longer affects: keepalived (Ubuntu Eoan) ** No longer affects: keepalived (Ubuntu Disco) ** Also affects: heartbeat (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: keepalived (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Focal) Status: New => Fix Released ** Changed in: keepalived (Ubuntu Focal) Status: New => Confirmed ** No longer affects: heartbeat (Ubuntu Focal) -- 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/1815101 Title: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted) Status in netplan: Confirmed Status in heartbeat package in Ubuntu: Won't Fix Status in keepalived package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Status in keepalived source package in Xenial: Confirmed Status in systemd source package in Xenial: Confirmed Status in keepalived source package in Bionic: Confirmed Status in systemd source package in Bionic: Confirmed Status in systemd source package in Disco: Won't Fix Status in systemd source package in Eoan: Fix Released Status in keepalived source package in Focal: Confirmed Status in systemd source package in Focal: Fix Released Bug description: [impact] - ALL related HA software has a small problem if interfaces are being managed by systemd-networkd: nic restarts/reconfigs are always going to wipe all interfaces aliases when HA software is not expecting it to (no coordination between them. - keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is smarter in this case because it has a service monitor that will restart the virtual IP resource, in affected node & nic, before considering a real failure, but other HA service might consider a real failure when it is not. [test case] - comment #14 is a full test case: to have 3 node pacemaker, in that example, and cause a networkd service restart: it will trigger a failure for the virtual IP resource monitor. - other example is given in the original description for keepalived. both suffer from the same issue (and other HA softwares as well). [regression potential] - this backports KeepConfiguration parameter, which adds some significant complexity to networkd's configuration and behavior, which could lead to regressions in correctly configuring the network at networkd start, or incorrectly maintaining configuration at networkd restart, or losing network state at networkd stop. - Any regressions are most likely to occur during networkd start, restart, or stop, and most likely to involve missing or incorrect ip address(es). - the change is based in upstream patches adding the exact feature we needed to fix this issue & it will be integrated with a netplan change to add the needed stanza to systemd nic configuration file (KeepConfiguration=) [other info] original description: --- Configure netplan for interfaces, for example (a working config with IP addresses obfuscated) network: ethernets: eth0: addresses: [192.168.0.5/24] dhcp4: false
[Touch-packages] [Bug 1878178] Re: EPSON WF 3520 driver problem - PpdFiles: Error
** Description changed: - After an upgrade from Ubuntu 18.04.2 to 19.10 my printer EPSON WF-3520 - won't work. Same problem upgrading from 19.10 to 20.01. It is recognized - on the printer menu but after finding the proper driver from EPSON it - gives en error in the process. There is a ppdfiles:error + After an upgrade from Ubuntu 18.04.2 to 19.10 my printer EPSON WF-3520 won't work. Same problem upgrading from 19.10 to 20.01. It is recognized on the printer menu but after finding the proper driver from EPSON it gives en error in the process. There is a ppdfiles:error + --- + The actual problem is that despite the fact that the printer is automatically found correctly as an Espon wf 3520 it is not working, neither the test page nor other documents. + + I have then removed the printer and add a new one. Again the printer + (network one) had been found and when it tries to find a driver it opens + a menu Seiko-Epson driver, i choose yes and apply and then in the end it + gives me an error, I'll attach a print screen. + + The driver which the system is using grabs from epson is the "epson- + 201212w" + + i have also tried the https://wiki.ubuntu.com/DebuggingPrintingProblems with no result. + + ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1.1 ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CupsErrorLog: E [12/May/2020:10:44:55 +0300] [Client 16] Returning IPP server-error-not-accepting-jobs for Print-Job (ipp://localhost/printers/EPSON_WF_3520_Series) from localhost. E [12/May/2020:10:45:59 +0300] [Client 22] Returning IPP server-error-not-accepting-jobs for Print-Job (ipp://localhost/printers/EPSON_WF_3520_Series) from localhost. E [12/May/2020:11:23:51 +0300] [Client 16] Returning IPP server-error-not-accepting-jobs for Print-Job (ipp://localhost/printers/EPSON_WF_3520_Series) from localhost. CurrentDesktop: ubuntu:GNOME Date: Tue May 12 12:28:09 2020 InstallationDate: Installed on 2019-12-21 (142 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lpstat: device for EPSON_WF_3520_Series: ///dev/null MachineType: Dell Inc. Precision M4600 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_WF_3520_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_WF_3520_Series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=a5d00ddf-aa19-41bf-8139-ac7c317aa04c ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to eoan on 2020-05-04 (7 days ago) dmi.bios.date: 09/14/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 08V9YG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd09/14/2018:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn08V9YG:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1878178 Title: EPSON WF 3520 driver problem - PpdFiles: Error Status in cups package in Ubuntu: New Bug description: After an upgrade from Ubuntu 18.04.2 to 19.10 my printer EPSON WF-3520 won't work. Same problem upgrading from 19.10 to 20.01. It is recognized on the printer menu but after finding the proper driver from EPSON it gives en error in the process. There is a ppdfiles:error --- The actual problem is that despite the fact that the printer is automatically found correctly as an Espon wf 3520 it is not working, neither the test page nor other documents. I have then removed the printer and add a new one. Again the printer (network one) had been found and when it tries to find a driver it opens a menu Seiko-Epson driver, i choose yes and apply and then in the end it gives me an error, I'll attach a print screen. The driver which the system is using grabs from epson is the "epson- 201212w" i have also tried the https://wiki.ubuntu.com/DebuggingPrintingProblems with no result. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1.1 ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CupsErrorLog: E [12/May/2020:10:44:55 +0300] [Client 16] Returning IPP
[Touch-packages] [Bug 1428121]
"intel_iommu=on intremap=off" yields no sound. -- 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/1428121 Title: Intel HDMI Audio not working with IOMMU enabled Status in ALSA driver: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: New ASRock Z97 Extreme 6 motherboard with an Intel i7 4790S and an Nvidia GTX 650. Host uses Intel IGD for video and HDMI audio out. When I pass kernel flags 'intel_iommu=on' or 'intel_iommu=on,igfx_on' HDMI audio no longer functions although the device and modules seem to load and I cannot locate any error messages. In this configuration IOMMU functions as expected and I can successfully pass the Nvidia card through to a KVM guest using VFIO. As per this (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1223840) bug report and the linked bugzilla thread I attempted to use kernel flag 'intel_iommu=on,igfx_off'. This resolves the HDMI audio out but breaks IOMMU as in VGA pass through generates DMA errors. I'm running from a clean installation of 14.10 with no modifications to the kernel or kvm, qemu, libvirt or virt-manager. In either scenario above the analogue audio out continues to function, I haven't tested the optical out as I have no hardware to do so. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-31-generic 3.16.0-31.41 ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kelvin 3468 F pulseaudio /dev/snd/controlC3: kelvin 3468 F pulseaudio /dev/snd/controlC0: kelvin 3468 F pulseaudio /dev/snd/controlC1: kelvin 3468 F pulseaudio CurrentDesktop: Unity Date: Wed Mar 4 12:53:17 2015 HibernationDevice: RESUME=UUID=4d35060a-85c4-45fd-9f8e-530491588931 InstallationDate: Installed on 2015-02-26 (5 days ago) InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 (20141022.2) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic.efi.signed root=UUID=4914f227-6bb0-40bb-a781-9ad7111a996f ro intremap=no_x2apic_optout intel_iommu=on,forcedac pci-stub.ids=10de:11c8,10de:0e0b nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-3.16.0-31-generic N/A linux-backports-modules-3.16.0-31-generic N/A linux-firmware 1.138.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.70 dmi.board.name: Z97 Extreme6 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd12/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1428121/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1878482] Re: EPSON WF 3520 driver problem - PpdFiles: Error
Hello Till, thanks for your reply The actual problem is that despite the fact that the printer is automatically found correctly as an Espon wf 3520 it is not working, neither the test page nor other documents. I have then remove the printer and add a new one. Again the printer (network one) had been found and when it tries to find a driver it opens a menu Seiko-Epson driver, i choose yes and apply and then in the end it gives me an error, I'll attach a print screen. The driver which the system is using grabs from epson is the "epson-201212w" i have also tried the https://wiki.ubuntu.com/DebuggingPrintingProblems with no result. That's why i made a bug report. Thank you George Anastasakos On 14/5/20 4:18 μ.μ., Till Kamppeter wrote: > What is the actual problem here? Is the printer model not found during > setup? Are you not able to print? > > Could you follow the instructions on > > https://wiki.ubuntu.com/DebuggingPrintingProblems > > Thanks. > > ** Changed in: cups (Ubuntu) > Status: New => Incomplete > ** Attachment added: "Screenshot from 2020-05-14 16-43-37.png" https://bugs.launchpad.net/bugs/1878482/+attachment/5371563/+files/Screenshot%20from%202020-05-14%2016-43-37.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1878482 Title: EPSON WF 3520 driver problem - PpdFiles: Error Status in cups package in Ubuntu: Incomplete Bug description: doesn't work ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 13 23:17:35 2020 InstallationDate: Installed on 2020-05-06 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for Generic-ESC-P-Dot-Matrix: lpd://192.168.1.133:515/PASSTHRU Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 04f2:b413 Chicony Electronics Co., Ltd FJ Camera Bus 001 Device 002: ID 062a:4101 MosArt Semiconductor Corp. Wireless Keyboard/Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: FUJITSU LIFEBOOK A555 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Generic-ESC-P-Dot-Matrix.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Generic-ESC-P-Dot-Matrix.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=85a6cbd6-a8d0-4ee5-ac82-9f54acbb0106 ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2016 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: 1.21 dmi.board.name: FJNBB3E dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvr1.21:bd05/31/2016:svnFUJITSU:pnLIFEBOOKA555:pvr:rvnFUJITSU:rnFJNBB3E:rvr:cvnFUJITSU:ct10:cvr: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK A555 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1878482/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Jorge Niedbalski (niedbalski)
** Changed in: systemd (Ubuntu Bionic)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1815101
Title:
[master] Restarting systemd-networkd breaks keepalived, heartbeat,
corosync, pacemaker (interface aliases are restarted)
Status in netplan:
Confirmed
Status in heartbeat package in Ubuntu:
Won't Fix
Status in keepalived package in Ubuntu:
In Progress
Status in systemd package in Ubuntu:
In Progress
Status in keepalived source package in Xenial:
Confirmed
Status in systemd source package in Xenial:
Confirmed
Status in keepalived source package in Bionic:
Confirmed
Status in systemd source package in Bionic:
In Progress
Status in systemd source package in Disco:
Won't Fix
Status in systemd source package in Eoan:
Fix Released
Status in keepalived source package in Focal:
Confirmed
Status in systemd source package in Focal:
Fix Released
Bug description:
[impact]
- ALL related HA software has a small problem if interfaces are being
managed by systemd-networkd: nic restarts/reconfigs are always going
to wipe all interfaces aliases when HA software is not expecting it to
(no coordination between them.
- keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is
smarter in this case because it has a service monitor that will
restart the virtual IP resource, in affected node & nic, before
considering a real failure, but other HA service might consider a real
failure when it is not.
[test case]
- comment #14 is a full test case: to have 3 node pacemaker, in that
example, and cause a networkd service restart: it will trigger a
failure for the virtual IP resource monitor.
- other example is given in the original description for keepalived.
both suffer from the same issue (and other HA softwares as well).
[regression potential]
- this backports KeepConfiguration parameter, which adds some
significant complexity to networkd's configuration and behavior, which
could lead to regressions in correctly configuring the network at
networkd start, or incorrectly maintaining configuration at networkd
restart, or losing network state at networkd stop.
- Any regressions are most likely to occur during networkd start,
restart, or stop, and most likely to involve missing or incorrect ip
address(es).
- the change is based in upstream patches adding the exact feature we
needed to fix this issue & it will be integrated with a netplan change
to add the needed stanza to systemd nic configuration file
(KeepConfiguration=)
[other info]
original description:
---
Configure netplan for interfaces, for example (a working config with
IP addresses obfuscated)
network:
ethernets:
eth0:
addresses: [192.168.0.5/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth2:
addresses:
- 12.13.14.18/29
- 12.13.14.19/29
gateway4: 12.13.14.17
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth3:
addresses: [10.22.11.6/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth4:
addresses: [10.22.14.6/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth7:
addresses: [9.5.17.34/29]
dhcp4: false
optional: true
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
version: 2
Configure keepalived (again, a working config with IP addresses
obfuscated)
global_defs # Block id
{
notification_email {
sysadm...@blah.com
}
notification_email_from keepali...@system3.hq.blah.com
smtp_server 10.22.11.7 # IP
smtp_connect_timeout 30 # integer, seconds
router_id system3 # string identifying the machine,
# (doesn't have to be hostname).
vrrp_mcast_group4 224.0.0.18 # optional, default 224.0.0.18
vrrp_mcast_group6 ff02::12 # optional, default ff02::12
enable_traps
[Touch-packages] [Bug 1878517] Re: please apply bash 5.0 patch 17
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1878517
Title:
please apply bash 5.0 patch 17
Status in bash package in Ubuntu:
New
Bug description:
I am using Ubuntu 20.04 for development and has hit a bug in bash 5.0
patch 16.
I can't reproduce it in pure bash, but with bats from
https://github.com/bats-core/bats-core/ it is very easy to repro:
```
# cat << EOF > ya.bats
check() {
echo "check $@"
ls -l /proc/self/fd
}
@test "here file" {
check -p <(echo "hey")
false
}
EOF
$ bats ya.bats
```
Normally the output should contain the line
lr-x-- 1 kir kir 64 May 14 02:01 63 -> pipe:[4616918]
which is a result of a "here file" created by bash via <(echo "hey").
In my testing, about 50% of runs don't have /dev/fd/63 listed.
I found out this is a manifest of a bug introduced in bash 5.0 patch
16 (see http://ftp.gnu.org/gnu/bash/bash-5.0-patches/bash50-016)
The bug is fixed in 5.0 patch 17 (see
http://ftp.gnu.org/gnu/bash/bash-5.0-patches/bash50-017).
Please update bash to patchlevel 17.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1878517/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1861408] Re: firefox apparmor messages
That commit/fix was only a small part of all that has been reported in
this bug, and that was an opportunistic fix. I don't plan on working on
the apparmor profile in the near future, unless some serious problem
with it is reported (which, unless I have misread, is not the case of
any of the comments in this bug report).
It doesn't hurt to keep the bug open, though.
** Changed in: firefox (Ubuntu)
Status: Fix Released => Triaged
--
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/1861408
Title:
firefox apparmor messages
Status in apparmor package in Ubuntu:
New
Status in firefox package in Ubuntu:
Triaged
Bug description:
firefox version 72.0.1 64 bit, 72.0.1+linuxmint1+tricia , linux mint
19.3.
i see there is newer ubuntu version in
https://www.ubuntuupdates.org/package/ubuntu_mozilla_security/bionic/main/base/firefox
, 72.0.2+build1-0ubuntu0.18.04.1 , but its changes are not for
apparmor.
i have not found a page for firefox bugs in linux mint sites, so i
belive i should report here. but i have also asked about that in linux
mint's irc and then github.
i have enabled apparmor for firefox and see these types of messages in
syslog:
Jan 28 18:43:33 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
[system] Activating via systemd: service
name='org.freedesktop.hostname1' unit='dbus-
org.freedesktop.hostname1.service' requested by ':1.111' (uid=1000
pid=1922 comm="/usr/lib/firefox/firefox " label="unconfined")
Jan 28 18:44:36 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5525.077960] audit: type=1400 audit(1580226276.440:27):
apparmor="DENIED" operation="capable"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=15948
comm="firefox" capability=21 capname="sys_admin"
Jan 28 18:44:37 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5526.471731] audit: type=1107 audit(1580226277.832:28): pid=735
uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system"
path="/org/freedesktop/RealtimeKit1"
interface="org.freedesktop.DBus.Properties" member="Get" mask="send"
name="org.freedesktop.RealtimeKit1" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1320
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/Daemon" interface="org.gtk.vfs.Daemon"
member="ListMonitorImplementations" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/Private/RemoteVolumeMonitor"
interface="org.gtk.Private.RemoteVolumeMonitor" member="IsSupported"
mask="send" name=":1.35" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1385
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
member="ListMounts2" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
member="LookupMount" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
[system] Activating via systemd: service
name='org.freedesktop.hostname1' unit='dbus-
org.freedesktop.hostname1.service' requested by ':1.119' (uid=1000
pid=15948 comm="/usr/lib/firefox/firefox "
label="/usr/lib/firefox/firefox{,*[^s][^h]} (enforce)")
Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5536.783313] audit: type=1107 audit(1580226288.143:34): pid=735
uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system"
path="/org/freedesktop/hostname1"
interface="org.freedesktop.DBus.Properties" member="GetAll"
mask="send" name=":1.120" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=16177
peer_label="unconfined"
Jan 28 18:45:02 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/ca/desrt/dconf/Writer/user" interface="ca.desrt.dconf.Writer"
member="Change" mask="send" name="ca.desrt.dconf" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1370
peer_label="unconfined"
Jan 28 21:51:30 dinar-HP-Pavilion-g7-Notebook-PC
[Touch-packages] [Bug 1876882] Re: Backport packages for 18.04.5 HWE stack
** Also affects: libglvnd (Ubuntu) Importance: Undecided Status: New ** No longer affects: libglvnd (Ubuntu) ** No longer affects: libglvnd (Ubuntu Bionic) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1876882 Title: Backport packages for 18.04.5 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-10 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: New Status in libdrm source package in Bionic: New Status in llvm-toolchain-10 source package in Bionic: New Status in mesa source package in Bionic: New Status in xorg-server-hwe-18.04 source package in Bionic: New Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: New Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: New Bug description: [Impact] These are needed for 18.04.5 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-10: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 20.0.x series, so there shouldn't be any regressions left at that point xserver: a new point-release xorg drivers: modest updates, if any [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1876882/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in
It might be of interest that together with this "no sound in jack" problem, my screen stopped to turn off after the specified amount of time. It locks, but does not turn off. I resolved this with xset +dpms xset dpms 300 but the Ubuntu Settings / Brightness & Lock didn't work as regards turning off the screen. So it might be another hint the problem is somehow related to power management (Dell 7790 17" G7 Gaming Laptop) -- 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/1583801 Title: No sound via headphones (headset) when Ubuntu boots with them plugged in Status in PulseAudio: New Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/193 The bug is twofold, first when computer boots if the headset (headphones with built-in mic, one audio jack) is plugged in, then there is no sound (via headphones or otherwise). If you plug headphones out and back in, then it usually works as expected. The second scenario is the same, except that plugging out and back in again doesn't help. In that case, I just restart the laptop, then plug them back in again and it works. In all cases, microphone works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio CurrentDesktop: Unity Date: Thu May 19 22:13:20 2016 InstallationDate: Installed on 2016-05-07 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1583801/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878598] [NEW] Screen orientation Portrait is broken
Public bug reported: I have two screens, one is 27'' plugged with displayport and the other 21'' plugged via HDMI. The 21'' doesn't accept the Portrait (Right or Left), it stays landscape. This same setup was ok in 19.10. I don't know for sure if it's xorg related of if it's related to display config screen but the options led me to this report. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/:01: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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 14 08:57:55 2020 DistUpgraded: 2020-05-13 09:40:01,957 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: Dell Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [1028:0527] NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP107 [GeForce GTX 1050 Ti] [3842:6251] InstallationDate: Installed on 2020-02-29 (75 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Alienware Alienware X51 ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=09e42201-f85d-4c4b-916b-452b980fa5e3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-13 (0 days ago) dmi.bios.date: 11/04/2013 dmi.bios.vendor: Alienware dmi.bios.version: A14 dmi.board.name: 06G6JW dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: 00 dmi.modalias: dmi:bvnAlienware:bvrA14:bd11/04/2013:svnAlienware:pnAlienwareX51:pvr00:rvnAlienware:rn06G6JW:rvrA00:cvnAlienware:ct3:cvr00: dmi.product.family: 0 dmi.product.name: Alienware X51 dmi.product.sku: Alienware X51 dmi.product.version: 00 dmi.sys.vendor: Alienware version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 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.8-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+git20200226-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 -- 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/1878598 Title: Screen orientation Portrait is broken Status in xorg package in Ubuntu: New Bug description: I have two screens, one is 27'' plugged with displayport and the other 21'' plugged via HDMI. The 21'' doesn't accept the Portrait (Right or Left), it stays landscape. This same setup was ok in 19.10. I don't know for sure if it's xorg related of if it's related to display config screen but the options led me to this report. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/:01: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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada:
[Touch-packages] [Bug 1872200] Re: apt does not accept globs and regexes in some cases
Tested similar to Doug with successful results. ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1872200 Title: apt does not accept globs and regexes in some cases Status in apt package in Ubuntu: Fix Released Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Released Bug description: [Impact] Users can't use * wildcards anymore in focal, except by accident in apt list. For apt list, we now start restricting wildcard syntax to the same syntax install now accepts, and at the same time we remove the restrictions on which patterns are accepted (which only accepted patterns starting in ~ or ?), so !~napt now works, and does not accidentally match as a wildcard. [Test case] Test that * wildcards work for both install and list, and test that a ? wildcard does not. We included autopkgtests for those: BEGIN TESTS # # * wildcards should still work testsuccessequal "Listing... automatic1/now 1.0 i386 [installed,local] automatic2/now 1.0 i386 [installed,local]" apt list 'automatic*' testfailureequal "Reading package lists... Building dependency tree... Reading state information... Note, selecting 'automatic1' for glob 'automatic*' Note, selecting 'automatic2' for glob 'automatic*' automatic1 is already the newest version (1.0). automatic1 set to manually installed. automatic2 is already the newest version (1.0). automatic2 set to manually installed. You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: broken : Depends: does-not-exist but it is not installable E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution)." apt install -s 'automatic*' # other wildcards should fail testfailureequal "Listing... E: input:0-10: error: Expected pattern automatic? ^^" apt list 'automatic?' testfailureequal "Reading package lists... Building dependency tree... Reading state information... E: Unable to locate package automatic?" apt install -s 'automatic?' END TESTS # Also it might be worth checking that apt list !~napt works. This used to produce an empty list, as it was accidentally matched as a wildcard and produced no result - now it produces every package whose name does not contain "apt". [Regression potential] The changes only affect interactive users, as apt(8) is not stable for in-script use, hence they can fix up their command-line if it stops working for them (though, really, more should work now). No scripts will be broken :) [Squashed in changes] The SRU also fixes potential build failures by correctly prefxing nullptr_t with the std:: namespace, and includes updated Dutch documentation. [Original bug report] Observed with Ubuntu 20.04 Beta. apt remove 'mypackage*' does not remove all installed packages starting with “mypackage”. Instead: $ sudo apt remove 'mypackage*' Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package mypackage* However: $ sudo apt list --installed 'mypackage*' Listing... Done mypackage-data-v1/focal,focal,now 0.3.2-5build1 all [installed,automatic] mypackage1/focal,now 0.3.2-5build1 amd64 [installed] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1872200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872200] Re: apt does not accept globs and regexes in some cases
FWIW, The upload has been superceded by a security update, and will need revalidation when 2.0.4 is uploaded. -- 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/1872200 Title: apt does not accept globs and regexes in some cases Status in apt package in Ubuntu: Fix Released Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Released Bug description: [Impact] Users can't use * wildcards anymore in focal, except by accident in apt list. For apt list, we now start restricting wildcard syntax to the same syntax install now accepts, and at the same time we remove the restrictions on which patterns are accepted (which only accepted patterns starting in ~ or ?), so !~napt now works, and does not accidentally match as a wildcard. [Test case] Test that * wildcards work for both install and list, and test that a ? wildcard does not. We included autopkgtests for those: BEGIN TESTS # # * wildcards should still work testsuccessequal "Listing... automatic1/now 1.0 i386 [installed,local] automatic2/now 1.0 i386 [installed,local]" apt list 'automatic*' testfailureequal "Reading package lists... Building dependency tree... Reading state information... Note, selecting 'automatic1' for glob 'automatic*' Note, selecting 'automatic2' for glob 'automatic*' automatic1 is already the newest version (1.0). automatic1 set to manually installed. automatic2 is already the newest version (1.0). automatic2 set to manually installed. You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: broken : Depends: does-not-exist but it is not installable E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution)." apt install -s 'automatic*' # other wildcards should fail testfailureequal "Listing... E: input:0-10: error: Expected pattern automatic? ^^" apt list 'automatic?' testfailureequal "Reading package lists... Building dependency tree... Reading state information... E: Unable to locate package automatic?" apt install -s 'automatic?' END TESTS # Also it might be worth checking that apt list !~napt works. This used to produce an empty list, as it was accidentally matched as a wildcard and produced no result - now it produces every package whose name does not contain "apt". [Regression potential] The changes only affect interactive users, as apt(8) is not stable for in-script use, hence they can fix up their command-line if it stops working for them (though, really, more should work now). No scripts will be broken :) [Squashed in changes] The SRU also fixes potential build failures by correctly prefxing nullptr_t with the std:: namespace, and includes updated Dutch documentation. [Original bug report] Observed with Ubuntu 20.04 Beta. apt remove 'mypackage*' does not remove all installed packages starting with “mypackage”. Instead: $ sudo apt remove 'mypackage*' Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package mypackage* However: $ sudo apt list --installed 'mypackage*' Listing... Done mypackage-data-v1/focal,focal,now 0.3.2-5build1 all [installed,automatic] mypackage1/focal,now 0.3.2-5build1 amd64 [installed] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1872200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860826] Re: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory
** Also affects: pam (Ubuntu Groovy) Importance: Low Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1860826 Title: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Status in pam package in Ubuntu: Confirmed Status in pam source package in Groovy: Confirmed Status in pam package in Debian: New Bug description: Hello, after upgrading to focal I found the following in my journalctl output: Jan 24 23:07:00 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Jan 24 23:07:01 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory The login package stopped packaging this file: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731656 and now forcibly removes the file: https://paste.ubuntu.com/p/myh9cGWrHD/ However, the pam package's pam_unix.so module has not yet been adapted to ignore this file: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674857#25 Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libpam-modules 1.3.1-5ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 Date: Fri Jan 24 23:35:33 2020 ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pam UpgradeStatus: Upgraded to focal on 2020-01-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1860826/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768625] Re: Bluetooth headset HSP/HFP mode not working in Bionic
*** This bug is a duplicate of bug 1576559 *** https://bugs.launchpad.net/bugs/1576559 Also having this problem in Ubuntu 20.04 with the Anker Soundcore Life 2 headset: Device 88:D0:39:39:83:07 (public) Name: Soundcore Life 2 Alias: Soundcore Life 2 Class: 0x00240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) Audio profile set to Headset (HSP/HFP). Headset connection LED blinks (error). Works in A2DP mode (without microphone). These headphones work fine as a headset in Windows 10. Seriously frustrating, trying to switch to Ubuntu for work and something this basic really should be fixed by now. -- 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/1768625 Title: Bluetooth headset HSP/HFP mode not working in Bionic Status in pulseaudio package in Ubuntu: Incomplete Bug description: There is a previous bug with almost the same title, but for Xenial (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1549163). I have had this issue in Artful, and when commented on the old bug, I was asked to raise a new one instead. I waited to see if Bionic fixed it for me, but it does not seem to work still. So! Steps to reproduce: 1. enable bluetooth on computer and switch on the headset. 2. pair and connect the headset 3. go to settings to switch headset to HSP/HFP mode to enable mic 4. save and close window. Expected behaviour: 1. mic should be enabled and headset should be usable to attend calls on laptop. Behaviour in error: 1. Headset profile switches back to A2DP and mic is not enabled. I am using a generic bluetooth headset on a fresh updated Kubuntu 18.04 bionic with plasma DE. Software versions: Kernel: 4.15.0-20-generic Bluez version: 5.48-0ubuntu3 pulseaudio: 1:11.1-1ubuntu7 pulseaudio-module-bluetooth: 1:11.1-1ubuntu7 Additional information: Running "pacmd list-cards" says that HSF/HFP is 'not available' on the headset: Output from Headset section: profiles: a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, available: unknown) headset_head_unit: Headset Head Unit (HSP/HFP) (priority 30, available: no) off: Off (priority 0, available: yes) active profile: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768625/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876035] Re: Consider making '-o Acquire::Retries=3' the default for 'apt-get update/install/dist-upgrade'
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apt (Ubuntu) Status: New => Confirmed -- 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/1876035 Title: Consider making '-o Acquire::Retries=3' the default for 'apt-get update/install/dist-upgrade' Status in apt package in Ubuntu: Confirmed Status in apt source package in Groovy: Confirmed Bug description: Hi, We operate archive.ubuntu.com as well as mirrors of it in various places. We're getting reports of various CI/CD jobs failing. Sometimes due to routing issues, issues with overloaded servers/VMs hosting archive, etc. Any chance we can make '-o Acquire::Retries=3' the default for 'apt- get update/install/dist-upgrade'? Preferably with a randomised skew between retries. Also, any chance of having apt-get retry with different IPs/hosts returned from the DNS lookup? (e.g. for archive.ubuntu.com - 91.189.88.142, 91.189.88.152, ...). Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1876035/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876035] Re: Consider making '-o Acquire::Retries=3' the default for 'apt-get update/install/dist-upgrade'
** Also affects: apt (Ubuntu Groovy) Importance: Undecided Status: Confirmed ** Changed in: apt (Ubuntu Groovy) 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/1876035 Title: Consider making '-o Acquire::Retries=3' the default for 'apt-get update/install/dist-upgrade' Status in apt package in Ubuntu: Confirmed Status in apt source package in Groovy: Confirmed Bug description: Hi, We operate archive.ubuntu.com as well as mirrors of it in various places. We're getting reports of various CI/CD jobs failing. Sometimes due to routing issues, issues with overloaded servers/VMs hosting archive, etc. Any chance we can make '-o Acquire::Retries=3' the default for 'apt- get update/install/dist-upgrade'? Preferably with a randomised skew between retries. Also, any chance of having apt-get retry with different IPs/hosts returned from the DNS lookup? (e.g. for archive.ubuntu.com - 91.189.88.142, 91.189.88.152, ...). Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1876035/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878630] [NEW] Two Docks apears on my screen display.
You have been subscribed to a public bug: I don't know exactly what is happening. Normally, after some time of use, two Docks appear on my screen display. One overlaps the other, but I can separate them (putting one of them to the right, for example, while the other remains in the same place) by using the settings in "Extensions", specifically in "Dash to dock". I can use the applications in both. During the lock screen I also can see one of them. Another thing that is going on, related to this problem, is that in "Extensions" the button "Dash to Dock" appears disabled, although it is actually enabled. Even when I enable it, when I back to "Extensions" the button is disabled again. My technical knowledge of computers and systems is limited. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 14 11:06:41 2020 DistUpgraded: 2020-04-26 16:12:50,424 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falha ao executar processo filho “./xorg_fix_proprietary.py” (Arquivo ou diretório inexistente) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: anbox, 1, 4.15.0-96-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family Integrated Graphics Controller [144d:c0b6] Lsusb: Bus 002 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. 300V3A/300V4A/300V5A/200A4B/200A5B ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=c9037370-4dff-4489-a6dc-e00d62311c2f ro SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-26 (17 days ago) dmi.bios.date: 10/12/2011 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 05FI dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 300V3A/300V4A/300V5A/200A4B/200A5B dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr05FI:bd10/12/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pn300V3A/300V4A/300V5A/200A4B/200A5B:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn300V3A/300V4A/300V5A/200A4B/200A5B:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: HuronRiver System dmi.product.name: 300V3A/300V4A/300V5A/200A4B/200A5B dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-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+git20200226-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 -- Two Docks apears on my screen display. https://bugs.launchpad.net/bugs/1878630 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 1878630] Re: Two Docks apears on my screen display.
** 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/1878630 Title: Two Docks apears on my screen display. Status in xorg package in Ubuntu: New Bug description: I don't know exactly what is happening. Normally, after some time of use, two Docks appear on my screen display. One overlaps the other, but I can separate them (putting one of them to the right, for example, while the other remains in the same place) by using the settings in "Extensions", specifically in "Dash to dock". I can use the applications in both. During the lock screen I also can see one of them. Another thing that is going on, related to this problem, is that in "Extensions" the button "Dash to Dock" appears disabled, although it is actually enabled. Even when I enable it, when I back to "Extensions" the button is disabled again. My technical knowledge of computers and systems is limited. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 14 11:06:41 2020 DistUpgraded: 2020-04-26 16:12:50,424 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falha ao executar processo filho “./xorg_fix_proprietary.py” (Arquivo ou diretório inexistente) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: anbox, 1, 4.15.0-96-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family Integrated Graphics Controller [144d:c0b6] Lsusb: Bus 002 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. 300V3A/300V4A/300V5A/200A4B/200A5B ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=c9037370-4dff-4489-a6dc-e00d62311c2f ro SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-26 (17 days ago) dmi.bios.date: 10/12/2011 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 05FI dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 300V3A/300V4A/300V5A/200A4B/200A5B dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr05FI:bd10/12/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pn300V3A/300V4A/300V5A/200A4B/200A5B:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn300V3A/300V4A/300V5A/200A4B/200A5B:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: HuronRiver System dmi.product.name: 300V3A/300V4A/300V5A/200A4B/200A5B dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-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+git20200226-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/1878630/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1870408] Re: casper-md5check should leave a breadcrumb which apport, ubiquity, subiquity could use
I'm closing the ubiquity task here in favor of
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1874714.
** Changed in: ubiquity (Ubuntu)
Status: New => Invalid
--
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/1870408
Title:
casper-md5check should leave a breadcrumb which apport, ubiquity,
subiquity could use
Status in subiquity:
Fix Released
Status in apport package in Ubuntu:
Fix Released
Status in casper package in Ubuntu:
In Progress
Status in ubiquity package in Ubuntu:
Invalid
Bug description:
casper-md5check should leave a breadcrumb which apport & ubiquity can
pick up. (subiquity too)
There will be a file called:
/run/casper-md5check.json
If it does not exist, or is empty the check did not run enough to
validate anything. Treat as skip.
If it has content it will have:
{
"checksum_missmatch" : [
"./pics/red-upperleft.png",
"./pics/red-lowerleft.png"
],
"result" : "fail"
}
optional checksum_missmatch key, which will have a list of strings
that are files that failed md5sum.
result key, which can have string values "pass" "fail" "skip".
One can use python's json or yaml safe_load to parse the file into a
dictionary.
To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1870408/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878611] Re: accountsservice 0.6.55-0ubuntu12~20.04.1 update crashes into greeter
Thanks for your report. Can you please add a comment to bug #1843982 too. What you observed might be a regression, and important for the decision whether to let 0.6.55-0ubuntu12 migrate to focal-updates. -- 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/1878611 Title: accountsservice 0.6.55-0ubuntu12~20.04.1 update crashes into greeter Status in accountsservice package in Ubuntu: New Bug description: When updating Ubuntu 20.04 to the current proposed updates with the accountsservice 0.6.55-0ubuntu12~20.04.1 update, the current gnome session crashes out reproducibly into the the gdm3 greeter. At that point, when you try to log back in, only the background color is displayed but no desktop or menus ever appears. One has to perform a hard reboot at this point to get back to a greeter that will successfully login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1878611/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
