[Touch-packages] [Bug 2002994] Re: sshd_config makes some changes awkward
I agree as well, it is great that we have .d function at all, but it could be better. As reported there is no control yet at what goes early or late and that would be a great enhancement. Just including it late isn't an easy option either as you might unintentionally to a different section that was at the end of the former config. A bit of history: - initially added via - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845315 - https://salsa.debian.org/ssh-team/openssh/-/commit/cb37f2bf1 - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862316 (unclosed, but in theory adressed by the above) - having some troubles to work - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961007 - https://bugzilla.mindrot.org/show_bug.cgi?id=3122 - good but not yet as good as other .d config inclusions - this bug - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998834 - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954965 Overall a problem that I see after going through all those is that some settings seem to be "the earliest set wins" so including at the top is good. And others are "overwritten by later statements" which asks for an inclusion at the end of the file. This needs to be analyzed, maybe the behavior changed over time or there are different categories of settings? To do so I recommend to read through those bugs, some have more examples and how to debug them. Once that check is done one can propose a solution and it might very well be what Kevin suggested here which is to put the main config into the .d directory as well and include them in numerical order. That might not solve/address the behavior of different statements, but at least it would give full control to the admin without touching the package owned config file. Either way this is worth having a look, but needs more time than a usual bug fix. Therefore I've added it to a set of ideas that we pick the most important ones from each Ubuntu release cycle. If anyone else wants to tackle this before we get to it - great, keep the bug updated in that case. ** Bug watch added: Debian Bug tracker #845315 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845315 ** Bug watch added: Debian Bug tracker #862316 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862316 ** Bug watch added: Debian Bug tracker #961007 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961007 ** Bug watch added: OpenSSH Portable Bugzilla #3122 https://bugzilla.mindrot.org/show_bug.cgi?id=3122 ** Bug watch added: Debian Bug tracker #998834 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998834 ** Bug watch added: Debian Bug tracker #954965 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954965 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2002994 Title: sshd_config makes some changes awkward Status in openssh package in Ubuntu: Confirmed Bug description: As distribted, the file sshd_config has apparently been modified from an upstream version -- those lines that are NOT comments. There is no good way for me to change any of them, even though there is a sshd_config.d directory for my changes. That is because the files in the sshd_config.d directory are invoked early, and the uncommented lines in the sshd_config file override them. I would have to modify the sshd_config file which defeats the purpose of having the directory. I suggest to adopt a method that I have seen elsewhere: put all of your changes in a file and put the file in the .d directory. Start the filename with something like '50' so that it can sort before or after any file contributed by the local admin. Keep the sshd_config file as you get it from upstream. This is, after all, the reason that the .d directories exist. In this way, admins do not have to modify distributed files, which avoids awkwardness when the package is updated. The same applies to ssh_config. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.2p1-4ubuntu0.5 ProcVersionSignature: Ubuntu 5.4.0-122.138-generic 5.4.192 Uname: Linux 5.4.0-122-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Jan 16 06:29:16 2023 SourcePackage: openssh UpgradeStatus: Upgraded to focal on 2021-02-19 (696 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2002994/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815318] Re: mate 18.04.1 xserver won't open caja on local machine
I've discovered a hackish workaround that may be helpful for someone to know about. If I use 'sudo caja' then it displays as expected. Running caja as non-root user still spawns a window on the remote machine, just like for everyone else. $ ssh -X user@IP Welcome to Ubuntu $ export XAUTHORITY=$HOME/.Xauthority (needed to use sudo) $ sudo caja TERMINAL OUTPUT (caja:4273): dbind-WARNING **: 20:17:39.773: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-DgQ4NgfGBw: Connection refused Initializing caja-open-terminal extension RuntimeError: object at 0x7fdfe93a75c0 of type FolderColorMenu is not initialized RuntimeError: object at 0x7fdfe960d300 of type RenameMenu is not initialized Then caja forwards as expected from file-server to local workstation over ssh. But now you are user:root and modifying other users files can result in undesired permission changes so use with care. Can still use Thunar or Dolphin or whatever alternate file-manager...but we shouldn't have to! I still run x1 gnome2 desktop and simply never have/had this problem when caja was nautilus so it's likely something simple introduced EARLY in MATE. Please guys, fix this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1815318 Title: mate 18.04.1 xserver won't open caja on local machine Status in MATE Desktop: New Status in caja package in Ubuntu: Confirmed Status in openssh package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Have installed Ubuntu MATE 18.04 LTS (you know its hostname and IP - i.e. 192.168.1.162) 2. Install SSH server on Ubuntu MATE 18.04 LTS 3. Open terminal on other remote system (client) and execute command to run Caja over X forwarding: ssh -X user@192.168.1.162 caja Expected results: * Caja is shown on remote (client) screen with window title *folder (on hostname)* Actual results: * Caja is not shown on remote (client) screen, but launches on server locally. Note: this works normally if server runs Ubuntu MATE 16.04 LTS, but fails with 18.04 LTS. --- Original description below: I can open a remote terminal using ssh -X 192.168.1.162. All other gui's that I've tested opened locally except the file manager Caja. When issuing caja in the remote terminal, I get nothing locally. Caja does open on the remote machine however, just not locally. The ssh -X 18.04.1 client still works connecting to a mate 16.04 server. I've tested this on numerous mate 18.04 clients, two 16.04 servers and two 18.04 servers, all mate. Something is wonky with caja on an 18.04.1 server. Please let me know if I can provide any more information. The only file manager I've tested that works is an X file manager, xfimage. X2go works and connects to servers, SSH Connect to Server works, why isn't the remote X terminal working using caja? To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1815318/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1926139] Re: dhclient: thread concurrency race leads to DHCPOFFER packets not being received
** Patch added: "lp1926139_focal_isc-dhcp.debdiff" https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1926139/+attachment/5642442/+files/lp1926139_focal_isc-dhcp.debdiff -- 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/1926139 Title: dhclient: thread concurrency race leads to DHCPOFFER packets not being received Status in bind9-libs package in Ubuntu: Fix Released Status in isc-dhcp package in Ubuntu: Invalid Status in bind9-libs source package in Focal: In Progress Status in bind9-libs source package in Jammy: In Progress Bug description: [Impact] Occasionally, during instance boot or machine start-up, dhclient will attempt to acquire a dhcp lease and fail, leaving the instance with no IP address and making it unreachable. This happens about once every 100 reboots on bare metal, or Chris Patterson in comment #2 describes it as affecting between ~0.3% to 2% of deployments on Microsoft Azure. Azure uses dhclient called from cloud-init instead of systemd-networkd, and this is causing issues with larger deployments. The logs of an affected dhclient produce the following: Listening on LPF/enp1s0/52:54:00:1c:d7:00 Sending on LPF/enp1s0/52:54:00:1c:d7:00 Sending on Socket/fallback DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 interval 3 (xid=0xd222950f) DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 interval 5 (xid=0xd222950f) ... (omitting 20 similar lines) ... DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 interval 13 (xid=0xd222950f) DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 interval 8 (xid=0xd222950f) DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 interval 6 (xid=0xd222950f) No DHCPOFFERS received. No working leases in persistent database - sleeping. Full log: https://paste.ubuntu.com/p/8yBfw2KR5h/ Log of a working run: https://paste.ubuntu.com/p/N3ZgqrxyQD/ The bizarre thing is when you tcpdump dhclient, we see all DHCPDISOVER packets being replied to with DHCPOFFER packets, but the got_one() callback is never called, dhclient does not read these DHCPOFFER packets, and continues sending DHCPDISCOVER packets. Once it reaches 25 DHCPDISCOVER packets sent, it gives up. tcpdump: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1926139/+attachment/5641810/+files/test.pcap Screenshot of Wireshark: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1926139/+attachment/5641811/+files/Screenshot_2023-01-17-16-14-21_1920x1200%250A1920x1080%250A1920x1080.png This behaviour led several bug reporters to believe it was a kernel issue, with the kernel not pushing DHCPOFFER packets to dhclient. This is not the case, the actual problem is dhclient containing a thread concurrency race condition, and when the race occurs, the read socket is closed prematurely, and dhclient does not read any of the DHCPOFFER replies. The full explanation is in the "Other Info" section, but the fix for this is to change bind9-libs from being built multithreaded, back to single threaded as intended by dhclient maintainers. In Focal and Jammy, isc-dhcp links against bind9 libraries provided in bind9-libs, while in Kinetic onward isc-dhcp has an in-tree bind9 library it uses, which is already configured properly to --disable- threads. Change the Focal and Jammy bind9-libs to --disable-threads and update symbol files to reflect the library is single threaded again. [Testcase] Start a fresh Focal or Jammy instance. Download and set executable test-parallel.sh, and edit some lines: 1) wget https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1926139/+attachment/5593045/+files/test-parallel.sh 2) chmod +x test-parallel.sh 3) vim test-parallel.sh Change iface="enp5s0" to your interface, likely iface="enp1s0". Comment out the line "# cp bionic-dhclient $workdir/dhclient". 4) sudo ./test-parallel.sh After five minutes, if you issue reproduces, you will see "TEST FAILED". You can watch the output with: 5) cat /tmp/dhclient-* | less Next, for instrumented runs, you need to build dhclient from source. 1) sudo apt install build-essential devscripts 2) apt source isc-dhcp 3) sudo apt build-dep isc-dhcp 4) cd isc-dhcp Apply the below patch: https://paste.ubuntu.com/p/hGsssrVyG4/ 5) patch -p1 < ~/patch.patch 6) debuild -b -uc -us 7) cd .. 8) sudo dpkg -i isc-dhcp-client-* 9) sudo ./test-parallel.sh 10) cat /tmp/dhclient-* | less Look for the race, as described in "Other Info", namely: mruffell: registering with socket manager mruffell: callback called mruffell: omapi object is NULL mruffell: omapi object is NULL mruffell: Adding obj to linked list mruffell: Obj added to list The issue has reproduced. If you install the test package from the following ppa:
[Touch-packages] [Bug 1926139] Re: dhclient: thread concurrency race leads to DHCPOFFER packets not being received
Hi Matthew, Thanks for the excellent analysis and considerate fix proposal, as always! I looked at this for the last couple of days, for potential sponsorship. I have attentively gone through the SRU template and Other Info section, and considered the proposal to switch bind9-libs into --disable-threads, with the goal of not only address this issue, but also prevent others: > So, we have two options for a fix for Focal and Jammy: > > 1) We disable threading for dhclient. > 2) We add in a mutex to resolve this particular concurrency issue. > [...] > I think if we fix the problem, another issue will crop up in six months > time, and it will be another concurrency issue. ... I'm aware you realize such change is concerning :) thus explained it well. Changing this is Focal (around for almost 3 years) brings regression risk to an amount I have the _impression_ the SRU team would not be okay with. And even though I agree with your analysis, proposal and risk assessment, I'm a bit concerned too, specially as this touches DHCP / IP addressing. (I'm also very aware this is ultimately their call, not mine at all. :) ... However, considering how much work and time have likely gone into this (and internal status) I can't just say 'no' without trying to help out. I'd like to bring a different opinion. The reason it's concerning is the very same reason 2) is reasonable: This concurrency issue (and potential for other concurrency issues) has been around with Focal since 2020/04 (~3 years), and until now, its impact does not seem to statistically significant: > This happens about once every 100 reboots on bare metal, or [...] > affecting between ~0.3% to 2% of deployments on Microsoft Azure. So, if there's a way to fix this particular concurrency issue with less regression risk, that might be worth it, as it would build on top of dhclient's life on Focal, instead of starting it over again. ... So, while reviewing the source code for your analysis, I had ideas. First, a synthetic reproducer with GDB that works every time. Second, a patch that addressed the issue with the test above. (It's not final form, I'd like to add a way to turn it off.) ... Could you please review and verify both, and share your thoughts on possibly going with that proposal instead? Of course, if you disagree with the argument or approach, or if turns out not to work on your end/tests, that's OK! We would defer this to the Foundations team and SRU team. - Test steps in the next comment. - Test packages in ppa:mfo/lp1926139 [1]. - Debdiff attached for reference (code has details). (Right now only Focal patches/packages are available. I can go look at Jammy depending on your feedback.) Hope this helps, after all. Thanks again! [1] https://launchpad.net/~mfo/+archive/ubuntu/lp1926139 -- 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/1926139 Title: dhclient: thread concurrency race leads to DHCPOFFER packets not being received Status in bind9-libs package in Ubuntu: Fix Released Status in isc-dhcp package in Ubuntu: Invalid Status in bind9-libs source package in Focal: In Progress Status in bind9-libs source package in Jammy: In Progress Bug description: [Impact] Occasionally, during instance boot or machine start-up, dhclient will attempt to acquire a dhcp lease and fail, leaving the instance with no IP address and making it unreachable. This happens about once every 100 reboots on bare metal, or Chris Patterson in comment #2 describes it as affecting between ~0.3% to 2% of deployments on Microsoft Azure. Azure uses dhclient called from cloud-init instead of systemd-networkd, and this is causing issues with larger deployments. The logs of an affected dhclient produce the following: Listening on LPF/enp1s0/52:54:00:1c:d7:00 Sending on LPF/enp1s0/52:54:00:1c:d7:00 Sending on Socket/fallback DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 interval 3 (xid=0xd222950f) DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 interval 5 (xid=0xd222950f) ... (omitting 20 similar lines) ... DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 interval 13 (xid=0xd222950f) DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 interval 8 (xid=0xd222950f) DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 interval 6 (xid=0xd222950f) No DHCPOFFERS received. No working leases in persistent database - sleeping. Full log: https://paste.ubuntu.com/p/8yBfw2KR5h/ Log of a working run: https://paste.ubuntu.com/p/N3ZgqrxyQD/ The bizarre thing is when you tcpdump dhclient, we see all DHCPDISOVER packets being replied to with DHCPOFFER packets, but the got_one() callback is never called, dhclient does not read these DHCPOFFER packets, and continues sending DHCPDISCOVER packets. Once it reaches 25 DHCPDISCOVER packets sent, it gives up. tcpdump:
[Touch-packages] [Bug 1926139] Re: dhclient: thread concurrency race leads to DHCPOFFER packets not being received
Reproducer based on GDB and DHCP noise injection.
It uses 3 veth pairs (DHCP server/client/injector,
the latter two under namespaces) on a linux bridge.
LXD VM:
$ lxc launch ubuntu:focal lp1926139-focal --vm
$ lxc shell lp1926139-focal
Network Setup:
# ip link add br0 type bridge
# ip link set br0 up
# ip link add veth0 type veth peer name veth0br
# ip link set veth0 up
# ip link set veth0br up master br0
# ip netns add ns1
# ip link add veth1 netns ns1 type veth peer name veth1br
# ip -n ns1 link set veth1 up
# ip link set veth1br up master br0
# ip netns add ns2
# ip link add veth2 netns ns2 type veth peer name veth2br
# ip -n ns2 link set veth2 up
# ip link set veth2br up master br0
Network Check:
# ip link show type veth | grep veth
5: veth0br@veth0: mtu 1500 qdisc
noqueue master br0 state UP mode DEFAULT group default qlen 1000
6: veth0@veth0br: mtu 1500 qdisc
noqueue state UP mode DEFAULT group default qlen 1000
7: veth1br@if2: mtu 1500 qdisc
noqueue master br0 state UP mode DEFAULT group default qlen 1000
8: veth2br@if2: mtu 1500 qdisc
noqueue master br0 state UP mode DEFAULT group default qlen 1000
# ip -n ns1 link show type veth | grep veth
2: veth1@if7: mtu 1500 qdisc noqueue
state UP mode DEFAULT group default qlen 1000
# ip -n ns2 link show type veth | grep veth
2: veth2@if8: mtu 1500 qdisc noqueue
state UP mode DEFAULT group default qlen 1000
DHCP Server Setup:
# apt install -y isc-dhcp-server
# ip addr add 192.168.42.1/24 dev veth0
# echo 'INTERFACESv4="veth0"' >>/etc/default/isc-dhcp-server
# cat <>/etc/dhcp/dhcpd.conf
subnet 192.168.42.0 netmask 255.255.255.0 {
range 192.168.42.100 192.168.42.200;
}
EOF
# systemctl restart isc-dhcp-server.service
# systemctl status isc-dhcp-server.service | grep Active:
Active: active (running) since Thu 2023-01-19 02:06:18 UTC; 19s ago
# ss -nlp | grep 0.0.0.0:67
udp UNCONN 00
0.0.0.0:67 0.0.0.0:*
users:(("dhcpd",pid=3279,fd=9))
DHCP Server Check:
# ip netns exec ns1 \
dhclient -v veth1
...
DHCPDISCOVER on veth1 to 255.255.255.255 port 67 interval 3
(xid=0xd147ab17)
DHCPOFFER of 192.168.42.100 from 192.168.42.1
DHCPREQUEST for 192.168.42.100 on veth1 to 255.255.255.255 port 67
(xid=0x17ab47d1)
DHCPACK of 192.168.42.100 from 192.168.42.1 (xid=0xd147ab17)
bound to 192.168.42.100 -- renewal in 245 seconds.
# ip netns exec ns1 \
dhclient -v veth1 -r
...
DHCPRELEASE of 192.168.42.100 on veth1 to 192.168.42.1 port 67
(xid=0x1cd4aacf)
DHCP Noise Setup:
# ip -n ns2 addr add 192.168.42.2/24 dev veth2
# ip netns exec ns2 \
/bin/sh -c 'while sleep 0.1; do echo; done | nc -u -v -b -s
192.168.42.2 -p 67 255.255.255.255 68' &
Connection to 255.255.255.255 68 port [udp/bootpc] succeeded!
i.e., every 0.1 seconds, broadcast a message as DHCP (port 67)
to DHCP client receive (port 68).
DHCP Noise Check:
# tcpdump -i veth0 -n 'udp and host 255.255.255.255' -c 10
...
02:13:26.993233 IP 192.168.42.2.67 > 255.255.255.255.68: BOOTP/DHCP,
unknown (0x0a) [|bootp]
02:13:27.098317 IP 192.168.42.2.67 > 255.255.255.255.68: BOOTP/DHCP,
unknown (0x0a) [|bootp]
02:13:27.205879 IP 192.168.42.2.67 > 255.255.255.255.68: BOOTP/DHCP,
unknown (0x0a) [|bootp]
02:13:27.314234 IP 192.168.42.2.67 > 255.255.255.255.68: BOOTP/DHCP,
unknown (0x0a) [|bootp]
02:13:27.424486 IP 192.168.42.2.67 > 255.255.255.255.68: BOOTP/DHCP,
unknown (0x0a) [|bootp]
02:13:27.532431 IP 192.168.42.2.67 > 255.255.255.255.68: BOOTP/DHCP,
unknown (0x0a) [|bootp]
02:13:27.639614 IP 192.168.42.2.67 > 255.255.255.255.68: BOOTP/DHCP,
unknown (0x0a) [|bootp]
02:13:27.747633 IP 192.168.42.2.67 > 255.255.255.255.68: BOOTP/DHCP,
unknown (0x0a) [|bootp]
02:13:27.864037 IP 192.168.42.2.67 > 255.255.255.255.68: BOOTP/DHCP,
unknown (0x0a) [|bootp]
02:13:27.977402 IP 192.168.42.2.67 > 255.255.255.255.68: BOOTP/DHCP,
unknown (0x0a) [|bootp]
...
GDB Reproducer (original package):
==
# apt install -y gdb
Capture DHCP Server's UDP packets for reference:
# tcpdump -i veth0 -n 'udp and host 192.168.42.1' -w
veth0-udp-192-168-42-1.pcap & pid=$!
Debug symbols:
# wget
https://launchpad.net/ubuntu/+archive/primary/+files/isc-dhcp-client-dbgsym_4.4.1-2.1ubuntu5.20.04.4_amd64.ddeb
# apt install -y
[Touch-packages] [Bug 2003237] Re: Monitor does not turn off after idle timeout is reached
** Tags added: amdgpu ** Package changed: xorg (Ubuntu) => mutter (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/2003237 Title: Monitor does not turn off after idle timeout is reached Status in mutter package in Ubuntu: New Bug description: My Screen Blank setting is set to 15 minutes. My Lock Screen settings are also set to automatically lock the system after the blank screen timeout is reached. After 15 minutes Ubuntu does lock me out, but the monitor does not power off as it's supposed to - the screen is simply black. Please see the attached video. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 18 23:48:13 2023 DistUpgraded: 2022-06-02 20:38:07,324 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Radeon RX 570 Pulse 4GB [1da2:e353] InstallationDate: Installed on 2018-03-17 (1768 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=19f4e829-52cc-4c6f-8221-24750af577f9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-06-02 (230 days ago) dmi.bios.date: 05/29/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4211 dmi.board.asset.tag: Default string dmi.board.name: H110M-D dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4211:bd05/29/2019:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-D:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003237/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1988364] Re: Missing the A2DP profile and defaults to low quality
OK so you may or may not be commenting on the right bug. Assuming you are, we'll just ask you to test the proposed fix when it is built... ** Description changed: [ Impact ] Sony WH-1000XM4 missing the A2DP profile and defaults to low quality. Probably other headphone types would be affected too. https://github.com/bluez/bluez/issues/313 [ Test Plan ] - ANYONE AFFECTED BY THE BUG PLEASE FILL THIS IN + No verifiable test case yet. Will ask the community for testing, and if + it fails then consider reverting the fix. [ Where problems could occur ] The fix touches Bluetooth audio logic (only). So anything relating to Bluetooth audio (A2DP) is the main risk. A secondary risk is the rest of bluetoothd which could suffer side effects. [ Other Info ] None provided. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1988364 Title: Missing the A2DP profile and defaults to low quality Status in Bluez Utilities: Fix Released Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Jammy: In Progress Status in bluez source package in Kinetic: Fix Released Status in bluez source package in Lunar: Fix Released Bug description: [ Impact ] Sony WH-1000XM4 missing the A2DP profile and defaults to low quality. Probably other headphone types would be affected too. https://github.com/bluez/bluez/issues/313 [ Test Plan ] No verifiable test case yet. Will ask the community for testing, and if it fails then consider reverting the fix. [ Where problems could occur ] The fix touches Bluetooth audio logic (only). So anything relating to Bluetooth audio (A2DP) is the main risk. A secondary risk is the rest of bluetoothd which could suffer side effects. [ Other Info ] None provided. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1988364/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003104] Re: gnome-terminal transparency ignored in full screen mode
I was expecting upstream to say "won't fix". Aside from the protocol saying it's the expected behaviour, we also wouldn't want to impact performance of fullscreen games just because they accidentally used RGBA instead of RGBX or RGB. So disallowing anything to show through in full screen makes sense to me, on balance. ** Also affects: wayland (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.freedesktop.org/wayland/wayland-protocols/-/issues #116 https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/116 ** Also affects: wayland via https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/116 Importance: Unknown Status: Unknown ** Changed in: wayland (Ubuntu) Status: New => Won't Fix ** Changed in: mutter (Ubuntu) Status: Triaged => Won't Fix ** Changed in: mutter (Ubuntu) Importance: High => Undecided -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2003104 Title: gnome-terminal transparency ignored in full screen mode Status in Mutter: New Status in wayland: Unknown Status in mutter package in Ubuntu: Won't Fix Status in wayland package in Ubuntu: Won't Fix Bug description: Ubuntu 23.04 running wayland gnome-terminal 3.46.7-1ubuntu1 In gnome-terminal, I have set the transparency to some amount. When I go to full screen (F11), the transparency is lost and the default transparency is used. When I exit full screen, the transparency comes back and I can see in the profile settings that the transparency has not changed. It seems that tranparency was accidentally removed, and then re-added via https://git.launchpad.net/ubuntu/+source/gnome-terminal/tree/debian/patches/0001-Restore-transparency.patch?h=applied/ubuntu/lunar-devel However, maybe something was missed with regards to full screen. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2003104/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003266] Re: 22.04 package lacks GSSAPI support
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: neon27 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to neon27 in Ubuntu. https://bugs.launchpad.net/bugs/2003266 Title: 22.04 package lacks GSSAPI support Status in neon27 package in Ubuntu: Confirmed Bug description: For more information, please see https://github.com/notroj/neon/issues/102. The 22.04 built package of neon lacks GSSAPI support, whereas previous versions (e.g. 18.04) had this support built-in. This appears to be due to a recent-ish change in the build logic for neon, which changes when GSSAPI is compiled in to the library (https://github.com/notroj/neon/commit/b9b7425de38b35249e689c03c30c8fd8adfae806) We were able to get a work around building from source with the following envvar during build-time: KRB5_CONF_TOOL=/usr/bin/krb5-config.mit ./configure. TL;DR: KRB5_CONFIG became KRB5_CONF_TOOL. Version information: $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ apt show libneon27 Package: libneon27 Version: 0.32.2-1 Priority: optional Section: universe/libs Source: neon27 Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Laszlo Boszormenyi (GCS) Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 233 kB Depends: libc6 (>= 2.33), libssl3 (>= 3.0.0~~alpha1), libxml2 (>= 2.7.4), zlib1g (>= 1:1.1.4) Homepage: https://notroj.github.io/neon/ Download-Size: 102 kB APT-Manual-Installed: no APT-Sources: [corporate Launchpad mirror] Description: HTTP and WebDAV client library To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neon27/+bug/2003266/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003266] [NEW] 22.04 package lacks GSSAPI support
Public bug reported: For more information, please see https://github.com/notroj/neon/issues/102. The 22.04 built package of neon lacks GSSAPI support, whereas previous versions (e.g. 18.04) had this support built-in. This appears to be due to a recent-ish change in the build logic for neon, which changes when GSSAPI is compiled in to the library (https://github.com/notroj/neon/commit/b9b7425de38b35249e689c03c30c8fd8adfae806) We were able to get a work around building from source with the following envvar during build-time: KRB5_CONF_TOOL=/usr/bin/krb5-config.mit ./configure. TL;DR: KRB5_CONFIG became KRB5_CONF_TOOL. Version information: $ lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 $ apt show libneon27 Package: libneon27 Version: 0.32.2-1 Priority: optional Section: universe/libs Source: neon27 Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Laszlo Boszormenyi (GCS) Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 233 kB Depends: libc6 (>= 2.33), libssl3 (>= 3.0.0~~alpha1), libxml2 (>= 2.7.4), zlib1g (>= 1:1.1.4) Homepage: https://notroj.github.io/neon/ Download-Size: 102 kB APT-Manual-Installed: no APT-Sources: [corporate Launchpad mirror] Description: HTTP and WebDAV client library ** Affects: neon27 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to neon27 in Ubuntu. https://bugs.launchpad.net/bugs/2003266 Title: 22.04 package lacks GSSAPI support Status in neon27 package in Ubuntu: New Bug description: For more information, please see https://github.com/notroj/neon/issues/102. The 22.04 built package of neon lacks GSSAPI support, whereas previous versions (e.g. 18.04) had this support built-in. This appears to be due to a recent-ish change in the build logic for neon, which changes when GSSAPI is compiled in to the library (https://github.com/notroj/neon/commit/b9b7425de38b35249e689c03c30c8fd8adfae806) We were able to get a work around building from source with the following envvar during build-time: KRB5_CONF_TOOL=/usr/bin/krb5-config.mit ./configure. TL;DR: KRB5_CONFIG became KRB5_CONF_TOOL. Version information: $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ apt show libneon27 Package: libneon27 Version: 0.32.2-1 Priority: optional Section: universe/libs Source: neon27 Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Laszlo Boszormenyi (GCS) Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 233 kB Depends: libc6 (>= 2.33), libssl3 (>= 3.0.0~~alpha1), libxml2 (>= 2.7.4), zlib1g (>= 1:1.1.4) Homepage: https://notroj.github.io/neon/ Download-Size: 102 kB APT-Manual-Installed: no APT-Sources: [corporate Launchpad mirror] Description: HTTP and WebDAV client library To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neon27/+bug/2003266/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003263] [NEW] please RM flexbar and tbb fron lunar
Public bug reported: flexbar is the last package still depending on the old tbb 2020.3-2.1ubuntu1, all other packages have already migrated to onetbb 2021.8.0-1ubuntu2. flexbar was removed from Debian testing on 2022-07-07 due to https://bugs.debian.org/1008220 Please remove flexbar and tbb from lunar. ** Affects: flexbar (Ubuntu) Importance: Undecided Status: New ** Affects: tbb (Ubuntu) Importance: Undecided Status: New ** Also affects: tbb (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tbb in Ubuntu. https://bugs.launchpad.net/bugs/2003263 Title: please RM flexbar and tbb fron lunar Status in flexbar package in Ubuntu: New Status in tbb package in Ubuntu: New Bug description: flexbar is the last package still depending on the old tbb 2020.3-2.1ubuntu1, all other packages have already migrated to onetbb 2021.8.0-1ubuntu2. flexbar was removed from Debian testing on 2022-07-07 due to https://bugs.debian.org/1008220 Please remove flexbar and tbb from lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flexbar/+bug/2003263/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1981794] Re: Duplicate/retried DNS queries fail with REFUSED (Fixed in upstream)
** Description changed: [Impact] When a DNS query fails to complete and the system retries it, subsequent copies of the query will be refused by dnsmasq. The client will automatically receive the REFUSED return value without a retry attempt. Adding this fix will stop dnsmasq from unnecessarily breaking connections, especially for situations where an internet connection is flaky. This bug is fixed by patching in an upstream commit - https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=2561f9fe0eb9c0be - which allows retried DNS requests through rather than refusing them. [Test Plan] The fix can be tested using 2 lxd containers, 1 for running the fix, and 1 for acting as a dns server. Start by setting up the dns server container: # lxc launch images:ubuntu/jammy dns-resolver # lxc exec dns-resolver bash # apt update && apt dist-upgrade -y # systemctl disable systemd-resolved # systemctl stop systemd-resolved # unlink /etc/resolv.conf # echo nameserver 8.8.8.8 | tee /etc/resolv.conf # apt install net-tools dnsmasq -y # systemctl enable dnsmasq Get the container's ip on lxd's network, in this case ifconfig is used, showing 10.62.42.157: # ifconfig eth0: flags=4163 mtu 1500 inet 10.62.42.157 netmask 255.255.255.0 broadcast 10.62.42.255 ... Now set up the test container: # lxc launch images:ubuntu/jammy test-dnsmasq # lxc exec test-dnsmasq bash # apt update && apt dist-upgrade -y # systemctl disable systemd-resolved # systemctl stop systemd-resolved # unlink /etc/resolv.conf - Use other container's ip here + Use other container's ip here, along with an ip that does not resolve # echo "nameserver 10.62.42.157 - nameserver 127.0.0.1" | tee /etc/resolv.conf + nameserver 192.0.2.1" | tee /etc/resolv.conf # apt install dnsmasq -y # systemctl enable dnsmasq - - Setup bind9 to delay ping resolution failure when testing - - # apt install bind9 -y - - # cat swap containers # echo nameserver 8.8.8.8 | tee /etc/resolv.conf; systemctl restart dnsmasq Ping will continue to not pick up the domain and fails with: ping: ubuntu.com: Temporary failure in name resolution With the fix, ping should now pick up the new successful responses: PING ubuntu.com (185.125.190.29) 56(84) bytes of data. 64 bytes from website-content-cache-3.ps5.canonical.com (185.125.190.29): icmp_seq=1 ttl=48 time=165 ms 64 bytes from website-content-cache-3.ps5.canonical.com (185.125.190.29): icmp_seq=2 ttl=48 time=162 ms 64 bytes from website-content-cache-3.ps5.canonical.com (185.125.190.29): icmp_seq=3 ttl=48 time=166 ms 64 bytes from website-content-cache-3.ps5.canonical.com (185.125.190.29): icmp_seq=4 ttl=48 time=164 ms 64 bytes from website-content-cache-3.ps5.canonical.com (185.125.190.29): icmp_seq=5 ttl=48 time=163 ms 64 bytes from website-content-cache-3.ps5.canonical.com (185.125.190.29): icmp_seq=6 ttl=48 time=163 ms ^C --- ubuntu.com ping statistics --- 6 packets transmitted, 6 received, 0% packet loss, time 5005ms Note: ping is used here instead of another dns tester such as dig because it continues its dns resolution attempts with retry packets even after receiving a REFUSED error. Other programs fail immediately on REFUSED and are unable to send duplicate packets to reproduce the issue. [Where problems could occur] This change was added upstream in version 2.87, which means it has not been tested in many situations alongside 2.86. Allowing the retries could lead to a flood of requests to remote DNS servers if the replies are unable to make it back through dnsmasq to the user. [Other Info] This bug was fixed in Kinetic in version 2.86-1.1ubuntu2. [Original Description] Duplicate or retried DNS queries will return REFUSED for one of the queries causing intermittent failures in clients. This probably breaks lots of things, but for me is causing 22.04's internet connection sharing to be unstable. It's particularly bad for my Xbox which seems to like sending duplicate queries. Here's an example capture: 22:37:25.308212 IP 10.42.0.16.54248 > 10.42.0.1.53: 22442+ A?
[Touch-packages] [Bug 2003250] [NEW] networkctl reload with bond devices causes slaves to go DOWN and UP, causing couple of seconds of network loss
Public bug reported: We currently use Ubuntu 22.04.1 LTS including updates for our production cloud (switched from legacy Centos 7). Although we like the distribution we recently hit serious systemd buggy behavior described in [1] bugreport using packages [2]. Unfortunatelly the clouds we are running consist of openstack on top of kubernetes and we need to have complex network configuration including linux bond devices. Our observation is that every time we apply our configuration via CI/CD infrastructure using ansible and netplan (regardless whether there is actual network configuration change) we see approximatelly 8-16 seconds network interruptions and see bond interfaces going DOWN and then UP. We expect bond interfaces stay UP when there is no network configuration change. We went though couple of options how to solve the issue and the first one is to add such existing patch [3] into current systemd-249.11-0ubuntu3.6. Could you comment whether this kind of non-security patch is likely to land in 22.04.1 LTS soon. We are able to help to bring patch into systemd package community way if you suggest the steps. [1] https://github.com/systemd/systemd/issues/25067 [2] Packages root@controlplane-001:/etc/apt0# apt list | grep -E '^(systemd/|netplan.io)' netplan.io/jammy-updates,now 0.105-0ubuntu2~22.04.1 amd64 [installed,automatic] systemd/jammy-updates,now 249.11-0ubuntu3.6 amd64 [installed,automatic] [3] https://github.com/systemd/systemd/pull/25162 [4] # lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: networking -- 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/2003250 Title: networkctl reload with bond devices causes slaves to go DOWN and UP, causing couple of seconds of network loss Status in systemd package in Ubuntu: New Bug description: We currently use Ubuntu 22.04.1 LTS including updates for our production cloud (switched from legacy Centos 7). Although we like the distribution we recently hit serious systemd buggy behavior described in [1] bugreport using packages [2]. Unfortunatelly the clouds we are running consist of openstack on top of kubernetes and we need to have complex network configuration including linux bond devices. Our observation is that every time we apply our configuration via CI/CD infrastructure using ansible and netplan (regardless whether there is actual network configuration change) we see approximatelly 8-16 seconds network interruptions and see bond interfaces going DOWN and then UP. We expect bond interfaces stay UP when there is no network configuration change. We went though couple of options how to solve the issue and the first one is to add such existing patch [3] into current systemd-249.11-0ubuntu3.6. Could you comment whether this kind of non-security patch is likely to land in 22.04.1 LTS soon. We are able to help to bring patch into systemd package community way if you suggest the steps. [1] https://github.com/systemd/systemd/issues/25067 [2] Packages root@controlplane-001:/etc/apt0# apt list | grep -E '^(systemd/|netplan.io)' netplan.io/jammy-updates,now 0.105-0ubuntu2~22.04.1 amd64 [installed,automatic] systemd/jammy-updates,now 249.11-0ubuntu3.6 amd64 [installed,automatic] [3] https://github.com/systemd/systemd/pull/25162 [4] # lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2003250/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003237] Re: Monitor does not turn off after idle timeout is reached
** Attachment added: "Video" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2003237/+attachment/5642297/+files/bug.mp4 ** Description changed: My Screen Blank setting is set to 15 minutes. My Lock Screen settings are also set to automatically lock the system after the blank screen timeout is reached. After 15 minutes Ubuntu does lock me out, but the monitor does not power - off as it's supposed to - the screen is simply black. + off as it's supposed to - the screen is simply black. Please see the + attached video. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 18 23:48:13 2023 DistUpgraded: 2022-06-02 20:38:07,324 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: - Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) -Subsystem: Sapphire Technology Limited Radeon RX 570 Pulse 4GB [1da2:e353] + Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) + Subsystem: Sapphire Technology Limited Radeon RX 570 Pulse 4GB [1da2:e353] InstallationDate: Installed on 2018-03-17 (1768 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=19f4e829-52cc-4c6f-8221-24750af577f9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-06-02 (230 days ago) dmi.bios.date: 05/29/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4211 dmi.board.asset.tag: Default string dmi.board.name: H110M-D dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4211:bd05/29/2019:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-D:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 -- 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/2003237 Title: Monitor does not turn off after idle timeout is reached Status in xorg package in Ubuntu: New Bug description: My Screen Blank setting is set to 15 minutes. My Lock Screen settings are also set to automatically lock the system after the blank screen timeout is reached. After 15 minutes Ubuntu does lock me out, but the monitor does not power off as it's supposed to - the screen is simply black. Please see the attached video. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 18 23:48:13 2023 DistUpgraded: 2022-06-02 20:38:07,324 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
[Touch-packages] [Bug 2003237] [NEW] Monitor does not turn off after idle timeout is reached
Public bug reported: My Screen Blank setting is set to 15 minutes. My Lock Screen settings are also set to automatically lock the system after the blank screen timeout is reached. After 15 minutes Ubuntu does lock me out, but the monitor does not power off as it's supposed to - the screen is simply black. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 18 23:48:13 2023 DistUpgraded: 2022-06-02 20:38:07,324 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Radeon RX 570 Pulse 4GB [1da2:e353] InstallationDate: Installed on 2018-03-17 (1768 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=19f4e829-52cc-4c6f-8221-24750af577f9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-06-02 (230 days ago) dmi.bios.date: 05/29/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4211 dmi.board.asset.tag: Default string dmi.board.name: H110M-D dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4211:bd05/29/2019:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-D:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- 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/2003237 Title: Monitor does not turn off after idle timeout is reached Status in xorg package in Ubuntu: New Bug description: My Screen Blank setting is set to 15 minutes. My Lock Screen settings are also set to automatically lock the system after the blank screen timeout is reached. After 15 minutes Ubuntu does lock me out, but the monitor does not power off as it's supposed to - the screen is simply black. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 18 23:48:13 2023 DistUpgraded: 2022-06-02 20:38:07,324 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Radeon RX 570 Pulse 4GB [1da2:e353] InstallationDate: Installed on 2018-03-17 (1768 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=19f4e829-52cc-4c6f-8221-24750af577f9 ro quiet splash vt.handoff=7
[Touch-packages] [Bug 2000817] Re: Wrong SHA256-value computed on kinetic
Writing down some options from a quick handover discussion I had with Sergio,
in no particular order:
- rebuild openldap with the attached patch, disabling strict aliasing just for
that module
- check if LTO is having an effect on this: maybe disabling LTO also fixes it,
and there is precedence for such a change in an SRU
- maybe the module code can be changed to not trigger this bug
- future-land: make the module use gnutls for such functions
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/2000817
Title:
Wrong SHA256-value computed on kinetic
Status in openldap package in Ubuntu:
Triaged
Bug description:
The OpenLDAP-contrib module sha2 (located in contrib/slapd-
modules/passwd/sha2/) computes a wrong SHA256/SSHA256-hash on Ubuntu
kinetic. This breaks our current password-authentication in ldap.
The problematic computation:
$ slappasswd -s secret -h '{SHA256}' -o module-load=pw-sha2
{SHA256}WIrrpN3OjEVOUf6yrH1j+o+ODuUuNBo979Od4UXnu54=
The (correct) reference-value on the same system (or older ubuntu
Versions):
$ echo -n "secret" | openssl dgst -sha256 -binary | openssl enc -base64
K7gNU3sdo+OL0wNhqoVWhr3g6s1xYv72ol/pe/Unols=
We nailed the problem down to a bug in the gcc-optimizer for strict-aliasing.
so most probably the gcc-version on kinetic (v12.2.0) is the reason. The
workaround is to compile the sha2-Module with the flag "-fno-strict-aliasing".
Then the correct value is computed. An example taken from a git-compiled
version of OpenLDAP 2.5.13:
$ ./servers/slapd/slappasswd -T passwd -s secret -h '{SHA256}' -o
module-load=pw-sha2 -o module-path=contrib/slapd-modules/passwd/sha2/.libs
{SHA256}K7gNU3sdo+OL0wNhqoVWhr3g6s1xYv72ol/pe/Unols=
Ubuntu:
Description:Ubuntu 22.10
Release:22.10
OpenLDAP-Package: 2.5.13+dfsg-1ubuntu1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2000817/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2000817] Re: Wrong SHA256-value computed on kinetic
** Changed in: openldap (Ubuntu)
Assignee: Sergio Durigan Junior (sergiodj) => Andreas Hasenack (ahasenack)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/2000817
Title:
Wrong SHA256-value computed on kinetic
Status in openldap package in Ubuntu:
Triaged
Bug description:
The OpenLDAP-contrib module sha2 (located in contrib/slapd-
modules/passwd/sha2/) computes a wrong SHA256/SSHA256-hash on Ubuntu
kinetic. This breaks our current password-authentication in ldap.
The problematic computation:
$ slappasswd -s secret -h '{SHA256}' -o module-load=pw-sha2
{SHA256}WIrrpN3OjEVOUf6yrH1j+o+ODuUuNBo979Od4UXnu54=
The (correct) reference-value on the same system (or older ubuntu
Versions):
$ echo -n "secret" | openssl dgst -sha256 -binary | openssl enc -base64
K7gNU3sdo+OL0wNhqoVWhr3g6s1xYv72ol/pe/Unols=
We nailed the problem down to a bug in the gcc-optimizer for strict-aliasing.
so most probably the gcc-version on kinetic (v12.2.0) is the reason. The
workaround is to compile the sha2-Module with the flag "-fno-strict-aliasing".
Then the correct value is computed. An example taken from a git-compiled
version of OpenLDAP 2.5.13:
$ ./servers/slapd/slappasswd -T passwd -s secret -h '{SHA256}' -o
module-load=pw-sha2 -o module-path=contrib/slapd-modules/passwd/sha2/.libs
{SHA256}K7gNU3sdo+OL0wNhqoVWhr3g6s1xYv72ol/pe/Unols=
Ubuntu:
Description:Ubuntu 22.10
Release:22.10
OpenLDAP-Package: 2.5.13+dfsg-1ubuntu1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2000817/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1981623] Re: Save As Dialog Box does not allow filename change
Is there any work around for this? Other than not using MATE desktop.
It's driving me crazy.
--
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/1981623
Title:
Save As Dialog Box does not allow filename change
Status in gtk+3.0 package in Ubuntu:
New
Bug description:
Ubuntu Mate 22.04 - Save-as dialog boxes (chrome, firefox, etc.) open
as expected, but do not permit changing the filename. Text entry
triggers the find function as opposed to file rename.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.2-0ubuntu0.2
ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
Uname: Linux 5.15.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Wed Jul 13 14:33:18 2022
DisplayManager: lightdm
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.0'"
b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 'YaST']"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
b'org.gnome.mutter' b'draggable-border-width' b'20'
InstallationDate: Installed on 2022-05-21 (52 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42.2-0ubuntu1
ShellJournal: -- No entries --
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1981623/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2002994] Re: sshd_config makes some changes awkward
** Tags removed: server-triage-discuss -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2002994 Title: sshd_config makes some changes awkward Status in openssh package in Ubuntu: Confirmed Bug description: As distribted, the file sshd_config has apparently been modified from an upstream version -- those lines that are NOT comments. There is no good way for me to change any of them, even though there is a sshd_config.d directory for my changes. That is because the files in the sshd_config.d directory are invoked early, and the uncommented lines in the sshd_config file override them. I would have to modify the sshd_config file which defeats the purpose of having the directory. I suggest to adopt a method that I have seen elsewhere: put all of your changes in a file and put the file in the .d directory. Start the filename with something like '50' so that it can sort before or after any file contributed by the local admin. Keep the sshd_config file as you get it from upstream. This is, after all, the reason that the .d directories exist. In this way, admins do not have to modify distributed files, which avoids awkwardness when the package is updated. The same applies to ssh_config. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.2p1-4ubuntu0.5 ProcVersionSignature: Ubuntu 5.4.0-122.138-generic 5.4.192 Uname: Linux 5.4.0-122-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Jan 16 06:29:16 2023 SourcePackage: openssh UpgradeStatus: Upgraded to focal on 2021-02-19 (696 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2002994/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1988364] Re: Missing the A2DP profile and defaults to low quality
IIRC I tried to install it from source back then, but had missing build dependencies (or versions) which were not in the package repositories. I could be wrong, though. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1988364 Title: Missing the A2DP profile and defaults to low quality Status in Bluez Utilities: Fix Released Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Jammy: In Progress Status in bluez source package in Kinetic: Fix Released Status in bluez source package in Lunar: Fix Released Bug description: [ Impact ] Sony WH-1000XM4 missing the A2DP profile and defaults to low quality. Probably other headphone types would be affected too. https://github.com/bluez/bluez/issues/313 [ Test Plan ] ANYONE AFFECTED BY THE BUG PLEASE FILL THIS IN [ Where problems could occur ] The fix touches Bluetooth audio logic (only). So anything relating to Bluetooth audio (A2DP) is the main risk. A secondary risk is the rest of bluetoothd which could suffer side effects. [ Other Info ] None provided. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1988364/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1988364] Re: Missing the A2DP profile and defaults to low quality
Hmm, currently when connecting it via blueman it automatically connects with the last used profile. I just saw it says "High Fidelity Playback (A2DP sink, codec SBC-XQ)". So it seems to have A2DP there. But as soon as I change my Mic Input Device to my headphones it changes to "Headset Head Unit (HSP/HFP codec mSBC)". If try to change the profile back to the A2DP sink my input device is also switched back to my internal Laptop Mic. I'm not sure anymore if the A2DP sink was always there or if came back with a recent OS update (Linux Mint 21.1) - I'm also not sure if bluez 5.65 can fix this behavior. Is there a more or less easy way I can test this on my machine? Maybe just clone it from the GitHub repo, checkout 5.65, compile and install it? Or do I need additional steps? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1988364 Title: Missing the A2DP profile and defaults to low quality Status in Bluez Utilities: Fix Released Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Jammy: In Progress Status in bluez source package in Kinetic: Fix Released Status in bluez source package in Lunar: Fix Released Bug description: [ Impact ] Sony WH-1000XM4 missing the A2DP profile and defaults to low quality. Probably other headphone types would be affected too. https://github.com/bluez/bluez/issues/313 [ Test Plan ] ANYONE AFFECTED BY THE BUG PLEASE FILL THIS IN [ Where problems could occur ] The fix touches Bluetooth audio logic (only). So anything relating to Bluetooth audio (A2DP) is the main risk. A secondary risk is the rest of bluetoothd which could suffer side effects. [ Other Info ] None provided. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1988364/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003223] Re: package libgdk-pixbuf-2.0-0:i386 2.42.8+dfsg-1ubuntu0.2 failed to install/upgrade: triggers looping, abandoned
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/2003223 Title: package libgdk-pixbuf-2.0-0:i386 2.42.8+dfsg-1ubuntu0.2 failed to install/upgrade: triggers looping, abandoned Status in gdk-pixbuf package in Ubuntu: New Bug description: Upgrading from 20.04 to 22.04 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libgdk-pixbuf-2.0-0:i386 2.42.8+dfsg-1ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-57.63~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Jan 18 16:31:31 2023 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2021-08-30 (505 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: i386 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: gdk-pixbuf Title: package libgdk-pixbuf-2.0-0:i386 2.42.8+dfsg-1ubuntu0.2 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to jammy on 2023-01-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/2003223/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003223] [NEW] package libgdk-pixbuf-2.0-0:i386 2.42.8+dfsg-1ubuntu0.2 failed to install/upgrade: triggers looping, abandoned
Public bug reported: Upgrading from 20.04 to 22.04 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libgdk-pixbuf-2.0-0:i386 2.42.8+dfsg-1ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-57.63~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Jan 18 16:31:31 2023 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2021-08-30 (505 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: i386 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: gdk-pixbuf Title: package libgdk-pixbuf-2.0-0:i386 2.42.8+dfsg-1ubuntu0.2 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to jammy on 2023-01-18 (0 days ago) ** Affects: gdk-pixbuf (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/2003223 Title: package libgdk-pixbuf-2.0-0:i386 2.42.8+dfsg-1ubuntu0.2 failed to install/upgrade: triggers looping, abandoned Status in gdk-pixbuf package in Ubuntu: New Bug description: Upgrading from 20.04 to 22.04 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libgdk-pixbuf-2.0-0:i386 2.42.8+dfsg-1ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-57.63~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Jan 18 16:31:31 2023 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2021-08-30 (505 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: i386 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: gdk-pixbuf Title: package libgdk-pixbuf-2.0-0:i386 2.42.8+dfsg-1ubuntu0.2 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to jammy on 2023-01-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/2003223/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 869881] Re: rsyslogd fails to load lmnsd_gtls.so
Yeah, I figured it was likely the outcome when I replied to a bug that was last touched 10 years ago ;) The bug will close itself in ~60 days if nothing happen so I think that's OK. Thanks! -- 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/869881 Title: rsyslogd fails to load lmnsd_gtls.so Status in rsyslog package in Ubuntu: Incomplete Bug description: rsyslog fails to load tls functionality. Relevant section from rsyslog.conf: (full file is attached, contents of /etc/rsyslog.d is unmodified from package defaults, and running `rsyslogd -f /etc/rsyslog.conf -c4 -N1` does not show any configuration errors. The remote logging section is copy-pasted from a working debian 6 box) REMOTE LOGGING # certificate files $DefaultNetstreamDriverCAFile /root/ssl/ca.pem $DefaultNetstreamDriverCertFile /root/ssl/generic-cert.pem $DefaultNetstreamDriverKeyFile /root/ssl/generic-key.pem # set up the action $DefaultNetstreamDriver gtls # use gtls netstream driver $ActionSendStreamDriverMode 1 # require TLS for the connection $ActionSendStreamDriverAuthMode x509/certvalid *.* @@(o)10.181.60.127:10514 # send (all) messages Error written to syslog: Oct 7 09:59:01 alpha rsyslogd-2068: could not load module '/usr/lib/rsyslog/lmnsd_gtls.so', rsyslog error -2078 Relevant info from running in debug mode (full debug output is attached): 7508.666438320:main queue:Reg/w0: unexpected GnuTLS error -64 in nsd_gtls.c:574: Error while reading file. I have also attached strace output from rsyslog. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: rsyslog-gnutls 4.2.0-2ubuntu8.1 Uname: Linux 2.6.35.4-rscloud x86_64 Architecture: amd64 Date: Fri Oct 7 09:38:03 2011 ProcEnviron: SHELL=/bin/bash SourcePackage: rsyslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/869881/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799580] Re: Settings made by qasmixer are lost on next reboot
I have been frustrated by this before on several distro versions. in settings, there is the option of "from last session" in the startup section. i assume you have this selected, as well as "close to system tray" and "show tray icon" in the system tray section.a problem is, that when you "close to tray" via the close window icon you are not actually exiting the program, your setup is only written as permanent when you exit the program. (select "close qasmixer" from the tray icon,or CtrlQ from the main qasmixer window, this writes your preferences / setup to file. note : rebooting doesnt "close qasmixer". please excuse my overly verbalness, I'm not trying to talk down to you, 'tis my long winded way of preparing for my question to you: is qasmixer still running / not being fully shutdown before reboot? perhaps qasmixers process tree still has branches? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1799580 Title: Settings made by qasmixer are lost on next reboot Status in alsa-utils package in Ubuntu: Confirmed Bug description: I use qasmixer to set the "Synth" volume to full, on my SoundBlaster Live sound-card. On prior levels of Ubuntu (through 18.04), any settings I make are preserved over reboots. On the latest level of Ubuntu (18.10) the settings are effective only as long as the system is running. The next time I reboot, the settings are gone, and I have to use qasmixer to set them all over again. I expected the settings made by qasmixer to be preserved on the next reboot, as with past levels of Ubuntu. The settings made by qasmixer are not preserved over a reboot on Ubuntu 18.10. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: qasmixer 0.21.0-1.1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic i686 ApportVersion: 2.20.10-0ubuntu13 Architecture: i386 CurrentDesktop: LXQt Date: Tue Oct 23 14:59:06 2018 InstallationDate: Installed on 2018-10-23 (0 days ago) InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release i386 (20181017.2) SourcePackage: qastools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1799580/+subscriptions -- Mailing list: https://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 869881] Re: rsyslogd fails to load lmnsd_gtls.so
Hi Simon, It is unlikely I will be able to replicate the scenario at this time. Please feel free to close off this case. Kind regards, Gaz/schmooster On Mon, 16 Jan 2023 at 05:25, Simon Déziel <869...@bugs.launchpad.net> wrote: > I tested a rsyslog client talking to a rsyslog server both using > `rsyslog-gnutls 8.2112.0-2ubuntu2.2` on Ubuntu 22.04 and it worked fine. > There, there is no error loading "/usr/lib/x86_64-linux- > gnu/rsyslog/lmnsd_gtls.so" as long as the `-gnutls` package is > installed. I used only a cert (from Let's Encrypt) on the server side > but I enabled Apparmor on both sides. > > I'm not sure if your error could have been due to having enabled the > Apparmor profile and using certificate files stored under `/root/ssl` > which isn't permitted by the Apparmor profile? Marking as incomplete > until you can report on the Apparmor profile situation. > > ** Changed in: rsyslog (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/869881 > > Title: > rsyslogd fails to load lmnsd_gtls.so > > Status in rsyslog package in Ubuntu: > Incomplete > > Bug description: > rsyslog fails to load tls functionality. > > Relevant section from rsyslog.conf: > (full file is attached, contents of /etc/rsyslog.d is unmodified from > package defaults, and running `rsyslogd -f /etc/rsyslog.conf -c4 -N1` > does not show any configuration errors. The remote logging section is > copy-pasted from a working debian 6 box) > > REMOTE LOGGING > > # certificate files > $DefaultNetstreamDriverCAFile /root/ssl/ca.pem > $DefaultNetstreamDriverCertFile /root/ssl/generic-cert.pem > $DefaultNetstreamDriverKeyFile /root/ssl/generic-key.pem > > > # set up the action > $DefaultNetstreamDriver gtls # use gtls netstream driver > $ActionSendStreamDriverMode 1 # require TLS for the connection > $ActionSendStreamDriverAuthMode x509/certvalid > > *.* @@(o)10.181.60.127:10514 # send (all) messages > > > Error written to syslog: > Oct 7 09:59:01 alpha rsyslogd-2068: could not load module > '/usr/lib/rsyslog/lmnsd_gtls.so', rsyslog error -2078 > > Relevant info from running in debug mode (full debug output is > attached): > 7508.666438320:main queue:Reg/w0: unexpected GnuTLS error -64 in > nsd_gtls.c:574: Error while reading file. > > I have also attached strace output from rsyslog. > > ProblemType: Bug > DistroRelease: Ubuntu 10.04 > Package: rsyslog-gnutls 4.2.0-2ubuntu8.1 > Uname: Linux 2.6.35.4-rscloud x86_64 > Architecture: amd64 > Date: Fri Oct 7 09:38:03 2011 > ProcEnviron: SHELL=/bin/bash > SourcePackage: rsyslog > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/869881/+subscriptions > > -- 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/869881 Title: rsyslogd fails to load lmnsd_gtls.so Status in rsyslog package in Ubuntu: Incomplete Bug description: rsyslog fails to load tls functionality. Relevant section from rsyslog.conf: (full file is attached, contents of /etc/rsyslog.d is unmodified from package defaults, and running `rsyslogd -f /etc/rsyslog.conf -c4 -N1` does not show any configuration errors. The remote logging section is copy-pasted from a working debian 6 box) REMOTE LOGGING # certificate files $DefaultNetstreamDriverCAFile /root/ssl/ca.pem $DefaultNetstreamDriverCertFile /root/ssl/generic-cert.pem $DefaultNetstreamDriverKeyFile /root/ssl/generic-key.pem # set up the action $DefaultNetstreamDriver gtls # use gtls netstream driver $ActionSendStreamDriverMode 1 # require TLS for the connection $ActionSendStreamDriverAuthMode x509/certvalid *.* @@(o)10.181.60.127:10514 # send (all) messages Error written to syslog: Oct 7 09:59:01 alpha rsyslogd-2068: could not load module '/usr/lib/rsyslog/lmnsd_gtls.so', rsyslog error -2078 Relevant info from running in debug mode (full debug output is attached): 7508.666438320:main queue:Reg/w0: unexpected GnuTLS error -64 in nsd_gtls.c:574: Error while reading file. I have also attached strace output from rsyslog. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: rsyslog-gnutls 4.2.0-2ubuntu8.1 Uname: Linux 2.6.35.4-rscloud x86_64 Architecture: amd64 Date: Fri Oct 7 09:38:03 2011 ProcEnviron: SHELL=/bin/bash SourcePackage: rsyslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/869881/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages
[Touch-packages] [Bug 1988364] Re: Missing the A2DP profile and defaults to low quality
Rafael, I can't seem to find a way to reproduce the bug with the headphones I do have. Can you outline the steps (and the model of headphones) you are using? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1988364 Title: Missing the A2DP profile and defaults to low quality Status in Bluez Utilities: Fix Released Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Jammy: In Progress Status in bluez source package in Kinetic: Fix Released Status in bluez source package in Lunar: Fix Released Bug description: [ Impact ] Sony WH-1000XM4 missing the A2DP profile and defaults to low quality. Probably other headphone types would be affected too. https://github.com/bluez/bluez/issues/313 [ Test Plan ] ANYONE AFFECTED BY THE BUG PLEASE FILL THIS IN [ Where problems could occur ] The fix touches Bluetooth audio logic (only). So anything relating to Bluetooth audio (A2DP) is the main risk. A secondary risk is the rest of bluetoothd which could suffer side effects. [ Other Info ] None provided. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1988364/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916931] Re: omshell returns inconsistent results or segfaults
Apologies for the poorly wrapped response. I pulled down the isc-dhcp source package from Kinetic and built it for Jammy. In my initial test showed that this does indeed seem to fix the problem. There was an issue with 'gbp buildpackage' deleting some files in the source repository that caused the initial build to fail: deleted:config.guess deleted:config.sub deleted:keama/tests/samples/example.conf.orig deleted:keama/tests/samples/test-a6.conf.orig deleted:keama/tests/samples/vmnet8.conf.orig I just 'git commit'ed the deletions and the package built successfully. Bill -- 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/1916931 Title: omshell returns inconsistent results or segfaults Status in isc-dhcp package in Ubuntu: Expired Bug description: I have just built a Ubuntu 20.04 server and installed isc-dhcp-server 4.4.1 on it and I am seeing inconsistent returns from omshell. Initially omshell returns data as expected, but when I exit and re-enter omshell connections fail. Here is the initial, working, session: # omshell > server localhost > port 7911 > key omapi_key > connect obj: > new failover-state obj: failover-state > set name = "dhcp-failover" obj: failover-state name = "dhcp-failover" > open obj: failover-state name = "dhcp-failover" partner-address = c0:9d:e9:76:e9:55:00:00 partner-port = 00:00:02:07 local-address = 10:9d:e9:76:e9:55:00:00 local-port = 00:00:02:07 max-outstanding-updates = 00:00:00:0a mclt = 00:00:01:2c load-balance-max-secs = 00:00:00:03 load-balance-hba = ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 partner-state = 00:00:00:02 local-state = 00:00:00:02 partner-stos = 60:36:d0:68 local-stos = 60:36:8b:3b hierarchy = 00:00:00:01 last-packet-sent = 00:00:00:00 last-timestamp-received = 00:00:00:00 skew = 00:00:00:00 max-response-delay = 00:00:00:3c cur-unacked-updates = 00:00:00:00 Here is what I see when the connect fails. Well, just hangs really. # omshell > server localhost > port 7911 > key omapi_key > connect And then I hit ctrl-c to break out and tried again: # omshell > server localhost > port 7911 > key omapi_key > connect Segmentation fault (core dumped) Note, the peer to this server is still running Ubuntu 18.04 with isc-dhcp-server 4.3.5. Running the exact same commands on the peer works reliably. (They are using the same python script to drive omshell.) The DHCP server on the new system appears to be working just fine as reported by omshell on the peer and systemctl. I was curious if the problem could be with the mis-matched versions of isc-dhcp-server so I shutdown isc-dhcp-server on the 18.04 system and get the same results. I also tried using a python script with the pypureomapi module to try and determine if the problem was in omshell or the server. I got very similar results when I attempted to get information about the failover state of the server. Interestingly interrogating the server about host information seems to work just fine. This is a critical bug since I don't see how to fail over a DHCP that is running the isc-dhcp-server on 20.04 without being able to issue omapi commands. I am attaching apport output to this bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1916931/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
