[Touch-packages] [Bug 1981794] Re: Duplicate/retried DNS queries fail with REFUSED (Fixed in upstream)
I have tested version 2.86-1.1ubuntu0.2 and that seems to have fixed it. The bug only appears when dnsmasq is forwarding responses in --strict- order mode and there's a duplicate request packet received before dnsmasq has replied to the original request packet. This is a procedure I came up with to reproduce and test that specific circumstance: I am using a network namespace to simplify networking, avoid port conflicts, and maintain tcpdump's protocol decoding. This test process requires running and interacting with multiple processes at once, and so it's easiest to just open multiple terminal windows. I create the net namespace with the first terminal, and then join the created namespace with additional terminals. To create the NS in the first terminal: $ sudo unshare --net # echo $$ > 12123 # ip addr add 127.0.0.1/8 dev lo # ip link set up dev lo # The `echo $$` gives the shell PID (12123 in this example), which is also the namespace PID. This can optionally be verified with lsns: # lsns -t net > NS TYPE NPROCS PID USER NETNSID NSFS COMMAND > 1234567890 net 2 12123 root unassigned -bash To join the NS from subsequent terminals: $ sudo nsenter -n -t 12123 # Test process: The first process to run is a fake upstream server for dnsmasq to forward responses from. We will run this on an alternate port (5353) and have it respond to requests for a test domain. # dnsmasq -d -p 5353 --no-resolv -A /example.com/192.0.2.1 The second process is the main dnsmasq process we want to actually test. It uses --strict-order and uses our fake upstream to answer all requests. We will also use systemd-run to limit dnsmasq's cpu resources to slow it down enough to more easily queue up duplicate requests. # systemd-run --scope -p CPUQuota=1% -- dnsmasq -d --strict-order --no- resolv -S 127.0.0.1#5353 The third process is just tcpdump to monitor requests to and responses from dnsmasq. I have piped the output through grep to make it easier to analyze the results for refused packets, but you can also leave that off and search the output manually. # tcpdump -ln udp port 53 | grep --line-buffered -iC 5 refused The final process is using `scapy` to generate dns packets with a duplicated request id. Scapy can be installed from the default repositories as `python3-scapy`. Scapy has to be switched to raw sockets mode to be able to work over the loopback interface before we can start sending dns packets. # scapy >>> conf.L3socket = L3RawSocket Now we can send some dns packets with scapy. All the packets should have the same request id in them, so we set it to a static number (we picked 47 in this example). We have also set it to send 50 packets, which is usually enough to get a few packets queued before dnsmasq can process the previous ones. >>> send(IP(dst='127.0.0.1')/UDP()/DNS(id=47,qd=DNSQR(qname='example.com')),count=50) You can also choose to send packets continuously until cancelled with Ctrl-C. >>> send(IP(dst='127.0.0.1')/UDP()/DNS(id=47,qd=DNSQR(qname='example.com')),loop=True) We can now check tcpdump for refused packets, which should show up anytime after there are two or more requests in a row without a response in between them. If you don't see any send another batch or two of packets. Here's some example output: 22:10:39.518439 IP 127.0.0.1.53 > 127.0.0.1.53: 47+ A? example.com. (29) 22:10:39.518896 IP 127.0.0.1.53 > 127.0.0.1.53: 47+ A? example.com. (29) 22:10:39.519366 IP 127.0.0.1.53 > 127.0.0.1.53: 47+ A? example.com. (29) 22:10:39.519824 IP 127.0.0.1.53 > 127.0.0.1.53: 47+ A? example.com. (29) 22:10:39.520290 IP 127.0.0.1.53 > 127.0.0.1.53: 47+ A? example.com. (29) 22:10:39.524495 IP 127.0.0.1.53 > 127.0.0.1.53: 47 Refused 0/0/0 (29) 22:10:39.524504 IP 127.0.0.1.53 > 127.0.0.1.53: 47 Refused 0/0/0 (29) 22:10:39.524512 IP 127.0.0.1.53 > 127.0.0.1.53: 47 Refused 0/0/0 (29) 22:10:39.524534 IP 127.0.0.1.53 > 127.0.0.1.53: 47 Refused 0/0/0 (29) 22:10:39.524547 IP 127.0.0.1.53 > 127.0.0.1.53: 47* 1/0/0 A 192.0.2.1 (45) 22:10:39.524575 IP 127.0.0.1.53 > 127.0.0.1.53: 47 Refused 0/0/0 (29) 22:10:39.524583 IP 127.0.0.1.53 > 127.0.0.1.53: 47 Refused 0/0/0 (29) 22:10:39.524590 IP 127.0.0.1.53 > 127.0.0.1.53: 47* 1/0/0 A 192.0.2.1 (45) 22:10:39.524612 IP 127.0.0.1.53 > 127.0.0.1.53: 47 Refused 0/0/0 (29) 22:10:39.524620 IP 127.0.0.1.53 > 127.0.0.1.53: 47 Refused 0/0/0 (29) 22:10:39.524628 IP 127.0.0.1.53 > 127.0.0.1.53: 47* 1/0/0 A 192.0.2.1 (45) 22:10:39.524648 IP 127.0.0.1.53 > 127.0.0.1.53: 47 Refused 0/0/0 (29) 22:10:39.524657 IP 127.0.0.1.53 > 127.0.0.1.53: 47 Refused 0/0/0 (29) 22:10:39.524664 IP 127.0.0.1.53 > 127.0.0.1.53: 47* 1/0/0 A 192.0.2.1 (45) 22:10:40.537105 IP 127.0.0.1.53 > 127.0.0.1.53: 47+ A? example.com. (29) 22:10:40.537236 IP 127.0.0.1.53 > 127.0.0.1.53: 47* 1/0/0 A 192.0.2.1 (45) 22:10:40.537591 IP 127.0.0.1.53 > 127.0.0.1.53: 47+ A? example.com. (29) 22:10:40.537636 IP 127.0.0.1.53 > 127.0.0.1.53: 47* 1/0/0 A 192.0.2.1 (45)
[Touch-packages] [Bug 2007913] [NEW] HDMI Output sound has disappeared after Ubuntu update
Public bug reported: After months using the HDMI output without problems, it has stopped working after a system update two days ago. HDMI output is not listed in the list of available output devices. Same computer works with this sound output perfectly when booting with Windows or an older installation of Ubuntu (18.04). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 21 08:12:58 2023 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-30 (296 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ca_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: M01EWR120 dmi.board.asset.tag: OEM Default string000 dmi.board.name: OEM Default string000 dmi.board.vendor: OEM Default string000 dmi.board.version: OEM Default string000 dmi.chassis.asset.tag: OEM Default string000 dmi.chassis.type: 10 dmi.chassis.vendor: OEM Default string000 dmi.chassis.version: OEM Default string000 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000: dmi.product.family: OEM Default string000 dmi.product.name: CoreBox dmi.product.sku: OEM Default string000 dmi.product.version: OEM Default string000 dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/2007913 Title: HDMI Output sound has disappeared after Ubuntu update Status in alsa-driver package in Ubuntu: New Bug description: After months using the HDMI output without problems, it has stopped working after a system update two days ago. HDMI output is not listed in the list of available output devices. Same computer works with this sound output perfectly when booting with Windows or an older installation of Ubuntu (18.04). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 21 08:12:58 2023 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-30 (296 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ca_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: M01EWR120 dmi.board.asset.tag: OEM Default string000 dmi.board.name: OEM Default string000 dmi.board.vendor: OEM Default string000 dmi.board.version: OEM Default string000 dmi.chassis.asset.tag: OEM Default string000 dmi.chassis.type: 10 dmi.chassis.vendor: OEM Default string000 dmi.chassis.version: OEM Default string000 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000: dmi.product.family: OEM Default string000 dmi.product.name: CoreBox dmi.product.sku: OEM Default string000 dmi.product.version: OEM Default string000 dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007913/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Un
[Touch-packages] [Bug 938751] Re: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome)
** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/938751 Title: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome) Status in GNOME Shell: New Status in chromium-browser package in Ubuntu: Confirmed Status in colord package in Ubuntu: Confirmed Status in eog package in Ubuntu: Confirmed Status in inkscape package in Ubuntu: Confirmed Bug description: Images are washed out or colors are skewed in some apps, notably Chrome/Chromium and Image Viewer (eog). Workaround: 1. Settings > Colour > turn off the toggle switch for your monitor. 2. Restart any affected apps. Originally reported in https://bugzilla.gnome.org/show_bug.cgi?id=675645 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/938751/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1803840] Re: color calibration with huey pro greenish
*** This bug is a duplicate of bug 938751 *** https://bugs.launchpad.net/bugs/938751 ** This bug has been marked a duplicate of bug 938751 Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1803840 Title: color calibration with huey pro greenish Status in colord package in Ubuntu: Confirmed Bug description: First of all: Congratulations, after an absence due to bad configurability of my rig I came back to ubuntu and was very positively surprisedthere is one thing that bothers me: after using the calibration feature for my screens this leads to greenish displays, even a icc profile made with the same hardware under windows10 (where configurability decreased since my update to v10) makes the same effect used with ubuntu 16.04...am I not aware of some more setting or is this a bug? Please let me know what more information you need from me besides I am using a hp envy dv6 and a wacom cintiq 13 hd, the nvidia graphics card is turned off for displays, I am using it just for Blenders Cycles renderer. I am a left-handed CG enthusiast who needs the wacom buttons on the right-hand side... Thank you, Michael ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 17 23:43:53 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.77, 4.15.0-38-generic, x86_64: installed nvidia, 390.77, 4.15.0-39-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:181b] NVIDIA Corporation GF108M [GeForce GT 635M] [10de:0de3] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GF108M [GeForce GT 635M] [103c:181b] InstallationDate: Installed on 2018-11-11 (5 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP ENVY dv6 Notebook PC ProcEnviron: LANGUAGE=de_CH:de PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_CH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=befbe944-5e8a-4bfc-b541-c8ad84809dde ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/02/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 181B dmi.board.vendor: Hewlett-Packard dmi.board.version: 52.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.22:bd11/02/2012:svnHewlett-Packard:pnHPENVYdv6NotebookPC:pvr088A1230591620100:rvnHewlett-Packard:rn181B:rvr52.24:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY dv6 Notebook PC dmi.product.version: 088A1230591620100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1803840/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1970081] Re: The background image of the login window cannot be changed
login screen is controlled by lightdm, the configuration is under /etc/lighdm/lightdm.conf You can set the values on this file using menu -> control center -> Login Window However lightdm will take the configuration values from files under /etc/lightdm/lightdm.conf.d/ So... either rename the directory lightdm.conf.d or delete the files under this directory -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1970081 Title: The background image of the login window cannot be changed Status in Ubuntu MATE: New Status in arctica-greeter package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: After upgrading from Ubuntu 20.04 Mate to 22.04 Mate, my custom wallpaper was replaced with the default one. I can make a change via the menu, but it stays with the default background image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970081/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2006954] Re: openssl: merge unstable's 3.0.8-1
The attachment "openssl_3.0.7-1ubuntu1.dsc-to- openssl_3.0.8-1ubuntu1.dsc.diff" seems to be a debdiff. The ubuntu- sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2006954 Title: openssl: merge unstable's 3.0.8-1 Status in openssl package in Ubuntu: New Bug description: Openssl 3.0.8 has been released. Unstable now contains 3.0.8-1 which we can merge. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2006954/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2006954] Re: openssl: merge unstable's 3.0.8-1
I'm attaching patches for the merge. The diff from 3.0.7-1ubuntu1 to 3.0.8-1ubuntu1 is in openssl_3.0.8-1ubuntu1.dsc-to-openssl_3.0.8-1ubuntu1.dsc.diff . PPA is at https://launchpad.net/~adrien-n/+archive/ubuntu/openssl-3.0.8-1-merge-v2 ** Patch added: "openssl_3.0.7-1ubuntu1.dsc-to-openssl_3.0.8-1ubuntu1.dsc.diff" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2006954/+attachment/5648672/+files/openssl_3.0.7-1ubuntu1.dsc-to-openssl_3.0.8-1ubuntu1.dsc.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2006954 Title: openssl: merge unstable's 3.0.8-1 Status in openssl package in Ubuntu: New Bug description: Openssl 3.0.8 has been released. Unstable now contains 3.0.8-1 which we can merge. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2006954/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2006954] Re: openssl: merge unstable's 3.0.8-1
I'm attaching patches for the merge. The diff from 3.0.8-1 to 3.0.8-1ubuntu1 is in openssl_3.0.8-1.dsc-to- openssl_3.0.8-1ubuntu1.dsc.diff . ** Patch added: "openssl_3.0.8-1.dsc-to-openssl_3.0.8-1ubuntu1.dsc.diff" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2006954/+attachment/5648673/+files/openssl_3.0.8-1.dsc-to-openssl_3.0.8-1ubuntu1.dsc.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2006954 Title: openssl: merge unstable's 3.0.8-1 Status in openssl package in Ubuntu: New Bug description: Openssl 3.0.8 has been released. Unstable now contains 3.0.8-1 which we can merge. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2006954/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2007698] Re: Please merge 1.9.13p1-1 into lunar
** Summary changed: - Please merge 1.9.12p2-1 into lunar + Please merge 1.9.13p1-1 into lunar ** Merge proposal linked: https://code.launchpad.net/~danilogondolfo/ubuntu/+source/sudo/+git/sudo/+merge/437587 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/2007698 Title: Please merge 1.9.13p1-1 into lunar Status in sudo package in Ubuntu: New Bug description: PPA available at https://launchpad.net/~danilogondolfo/+archive/ubuntu/sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2007698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2006954] Re: openssl: merge unstable's 3.0.8-1
** Changed in: openssl (Ubuntu) Assignee: (unassigned) => Adrien Nader (adrien-n) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2006954 Title: openssl: merge unstable's 3.0.8-1 Status in openssl package in Ubuntu: New Bug description: Openssl 3.0.8 has been released. Unstable now contains 3.0.8-1 which we can merge. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2006954/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2007869] [NEW] /usr/lib/software-properties/software-properties-dbus:ModuleNotFoundError:/usr/lib/software-properties/software-properties-dbus@29:/lib/python3/dist-packages/softw
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.22.5, the problem page at https://errors.ubuntu.com/problem/2b8f5a04f21afd1671ea8b6b13ce433033f298f1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- 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/2007869 Title: /usr/lib/software-properties/software-properties- dbus:ModuleNotFoundError:/usr/lib/software-properties/software- properties-dbus@29:/lib/python3/dist- packages/softwareproperties/dbus/SoftwarePropertiesDBus.py@32:/lib/python3/dist- packages/softwareproperties/SoftwareProperties.py@64:/lib/python3/dist- packages/softwareproperties/shortcuts.py@23:/lib/python3/dist- packages/softwareproperties/ppa.py@25:/lib/python3/dist- packages/launchpadlib/launchpad.py@46:/lib/python3/dist- packages/lazr/restfulclient/authorize/oauth.py@32 Status in software-properties package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.22.5, the problem page at https://errors.ubuntu.com/problem/2b8f5a04f21afd1671ea8b6b13ce433033f298f1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2007869/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2007865] [NEW] package initramfs-tools 0.140ubuntu13.1 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status
Public bug reported: Occured on upgrading grub-efi package ProblemType: Package DistroRelease: Ubuntu 22.04 Package: initramfs-tools 0.140ubuntu13.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Feb 19 20:41:35 2023 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-05-09 (652 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2 RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: initramfs-tools Title: package initramfs-tools 0.140ubuntu13.1 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-06-27 (237 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2007865 Title: package initramfs-tools 0.140ubuntu13.1 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Occured on upgrading grub-efi package ProblemType: Package DistroRelease: Ubuntu 22.04 Package: initramfs-tools 0.140ubuntu13.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Feb 19 20:41:35 2023 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-05-09 (652 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2 RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: initramfs-tools Title: package initramfs-tools 0.140ubuntu13.1 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-06-27 (237 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2007865/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2007743] Re: intramfs Failed: ZSTD-compressed data
** Package changed: initramfs-tools (Ubuntu) => grub2-unsigned (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2007743 Title: intramfs Failed: ZSTD-compressed data Status in grub2-unsigned package in Ubuntu: Incomplete Bug description: The current updates of Ubuntu 22.04.2 LTS results on boot (black screen) the message "not enough memory, press any key" and after comes any others "error messages" too and then Ubuntu starts! Maybe this Bug results from the current AMD Kernel Updates on "modern" Prozessors or Update for the Grub or something - i'don't know - there are many System-Updates yesterday and all comes over Ubuntu Store as package # lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 # dpkg -l | grep init ii busybox-initramfs 1:1.30.1-7ubuntu3 amd64Standalone shell setup for initramfs ii gnome-initial-setup42.0.1-1ubuntu2.3 amd64Initial GNOME system setup helper ii init 1.62 amd64metapackage ensuring an init system is installed ii init-system-helpers1.62 all helper tools for all init systems ii initramfs-tools0.140ubuntu13.1 all generic modular initramfs generator (automation) ii initramfs-tools-bin0.140ubuntu13.1 amd64binaries used by initramfs-tools ii initramfs-tools-core 0.140ubuntu13.1 all generic modular initramfs generator (core tools) ii libatopology2:amd641.2.6.1-1ubuntu1 amd64shared library for handling ALSA topology definitions ii libklibc:amd64 2.0.10-4 amd64minimal libc subset for use with initramfs ii lsb-base 11.1.0ubuntu4 all Linux Standard Base init script functionality ii ncurses-base 6.3-2 all basic terminal type definitions ii sysvinit-utils 3.01-1ubuntu1 amd64System-V-like utilities ii xinit 1.4.1-0ubuntu4 amd64X server initialisation tool # dpkg -l | grep zfs -> brings no information here # zfs list -> zfs is not installed here if you need more system-infos to solve this Bug, please let me know! The first error means "Not Enough Memory, Please press any key" - you can press any key (but you don't need) and it comes the "intramfs Failed: ZSTD-compressed data ..." and then the Ubuntu Login screen comes up. Please be patient with me, I'm new to Ubuntu and Launchpad and don't know much about it yet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2007743/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2007743] Re: intramfs Failed: ZSTD-compressed data
i have a friend who has exactly the same PC with exactly the same hardware and exactly identical Ubuntu, i advised him not to do the system update, otherwise he will also get this error, i am quite sure. I can't be the only one with this error ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2007743 Title: intramfs Failed: ZSTD-compressed data Status in initramfs-tools package in Ubuntu: Incomplete Bug description: The current updates of Ubuntu 22.04.2 LTS results on boot (black screen) the message "not enough memory, press any key" and after comes any others "error messages" too and then Ubuntu starts! Maybe this Bug results from the current AMD Kernel Updates on "modern" Prozessors or Update for the Grub or something - i'don't know - there are many System-Updates yesterday and all comes over Ubuntu Store as package # lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 # dpkg -l | grep init ii busybox-initramfs 1:1.30.1-7ubuntu3 amd64Standalone shell setup for initramfs ii gnome-initial-setup42.0.1-1ubuntu2.3 amd64Initial GNOME system setup helper ii init 1.62 amd64metapackage ensuring an init system is installed ii init-system-helpers1.62 all helper tools for all init systems ii initramfs-tools0.140ubuntu13.1 all generic modular initramfs generator (automation) ii initramfs-tools-bin0.140ubuntu13.1 amd64binaries used by initramfs-tools ii initramfs-tools-core 0.140ubuntu13.1 all generic modular initramfs generator (core tools) ii libatopology2:amd641.2.6.1-1ubuntu1 amd64shared library for handling ALSA topology definitions ii libklibc:amd64 2.0.10-4 amd64minimal libc subset for use with initramfs ii lsb-base 11.1.0ubuntu4 all Linux Standard Base init script functionality ii ncurses-base 6.3-2 all basic terminal type definitions ii sysvinit-utils 3.01-1ubuntu1 amd64System-V-like utilities ii xinit 1.4.1-0ubuntu4 amd64X server initialisation tool # dpkg -l | grep zfs -> brings no information here # zfs list -> zfs is not installed here if you need more system-infos to solve this Bug, please let me know! The first error means "Not Enough Memory, Please press any key" - you can press any key (but you don't need) and it comes the "intramfs Failed: ZSTD-compressed data ..." and then the Ubuntu Login screen comes up. Please be patient with me, I'm new to Ubuntu and Launchpad and don't know much about it yet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2007743/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2007743] Re: intramfs Failed: ZSTD-compressed data
any news or updates here? i need a fix please. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2007743 Title: intramfs Failed: ZSTD-compressed data Status in initramfs-tools package in Ubuntu: Incomplete Bug description: The current updates of Ubuntu 22.04.2 LTS results on boot (black screen) the message "not enough memory, press any key" and after comes any others "error messages" too and then Ubuntu starts! Maybe this Bug results from the current AMD Kernel Updates on "modern" Prozessors or Update for the Grub or something - i'don't know - there are many System-Updates yesterday and all comes over Ubuntu Store as package # lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 # dpkg -l | grep init ii busybox-initramfs 1:1.30.1-7ubuntu3 amd64Standalone shell setup for initramfs ii gnome-initial-setup42.0.1-1ubuntu2.3 amd64Initial GNOME system setup helper ii init 1.62 amd64metapackage ensuring an init system is installed ii init-system-helpers1.62 all helper tools for all init systems ii initramfs-tools0.140ubuntu13.1 all generic modular initramfs generator (automation) ii initramfs-tools-bin0.140ubuntu13.1 amd64binaries used by initramfs-tools ii initramfs-tools-core 0.140ubuntu13.1 all generic modular initramfs generator (core tools) ii libatopology2:amd641.2.6.1-1ubuntu1 amd64shared library for handling ALSA topology definitions ii libklibc:amd64 2.0.10-4 amd64minimal libc subset for use with initramfs ii lsb-base 11.1.0ubuntu4 all Linux Standard Base init script functionality ii ncurses-base 6.3-2 all basic terminal type definitions ii sysvinit-utils 3.01-1ubuntu1 amd64System-V-like utilities ii xinit 1.4.1-0ubuntu4 amd64X server initialisation tool # dpkg -l | grep zfs -> brings no information here # zfs list -> zfs is not installed here if you need more system-infos to solve this Bug, please let me know! The first error means "Not Enough Memory, Please press any key" - you can press any key (but you don't need) and it comes the "intramfs Failed: ZSTD-compressed data ..." and then the Ubuntu Login screen comes up. Please be patient with me, I'm new to Ubuntu and Launchpad and don't know much about it yet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2007743/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2007856] [NEW] snmpd fails to recognize Docker's overlay filesystem
Public bug reported: Ubuntu release: 22.04 (Jammy) Package: https://packages.ubuntu.com/jammy/snmpd The net-snmp project switched to a new implementation of the fsys hardware module at their 5.8 version. This was not mentioned in the release notes, because the decision was made earlier through the build system. The new version did not recognize the /etc/mtab entry of "overlay" as a supported filesystem, so monitoring / inside a Docker container fails after Bionic (5.7.3), likely in every Ubuntu since Focal (5.8). The fix happened in this commit, already on their master: https://github.com/net-snmp/net-snmp/commit/798f206561b7de4bc54453c01ffd21de8ae59c87 Since it is an added item in a static list, it would be easy to backport to Jammy's 5.9.1, or most other releases really. A refactor happened at some point that makes backporting before a certain version a bit more interesting, but still easy based on the suggestions in this similar issue: https://github.com/net-snmp/net-snmp/issues/268 Steps to reproduce: 1. Extract the attached zip with a Dockerfile, a patch, and an snmpd.conf 2. Run "docker build -t repro . && docker run --rm -p 161:161/udp repro" to compile and start a Jammy container with a 5.9.1 snmpd inside. 3. Query the disk table from another terminal: "snmpwalk -v2c -c public 0.0.0.0:161 .1.3.6.1.4.1.2021.9" There should be no OID found. Repeat steps 2 and 3 after uncommenting the two lines in the Dockerfile that apply the patch. Now proper data should arrive about the root filesystem. I would like to get an SRU with this patch for Jammy. There should be no risk except for snmpd users. The patch is recent and not released, so it is not widely tested yet. It should only impact snmpd users with Docker containers, since it only expands the list of recognized filesystems with "overlay". This feature was broken since Focal, so I assume there aren't many such users. ** Affects: net-snmp (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Files for reproduction and verification" https://bugs.launchpad.net/bugs/2007856/+attachment/5648641/+files/repro.zip ** Package changed: unattended-upgrades (Ubuntu) => net-snmp (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/2007856 Title: snmpd fails to recognize Docker's overlay filesystem Status in net-snmp package in Ubuntu: New Bug description: Ubuntu release: 22.04 (Jammy) Package: https://packages.ubuntu.com/jammy/snmpd The net-snmp project switched to a new implementation of the fsys hardware module at their 5.8 version. This was not mentioned in the release notes, because the decision was made earlier through the build system. The new version did not recognize the /etc/mtab entry of "overlay" as a supported filesystem, so monitoring / inside a Docker container fails after Bionic (5.7.3), likely in every Ubuntu since Focal (5.8). The fix happened in this commit, already on their master: https://github.com/net-snmp/net-snmp/commit/798f206561b7de4bc54453c01ffd21de8ae59c87 Since it is an added item in a static list, it would be easy to backport to Jammy's 5.9.1, or most other releases really. A refactor happened at some point that makes backporting before a certain version a bit more interesting, but still easy based on the suggestions in this similar issue: https://github.com/net-snmp/net-snmp/issues/268 Steps to reproduce: 1. Extract the attached zip with a Dockerfile, a patch, and an snmpd.conf 2. Run "docker build -t repro . && docker run --rm -p 161:161/udp repro" to compile and start a Jammy container with a 5.9.1 snmpd inside. 3. Query the disk table from another terminal: "snmpwalk -v2c -c public 0.0.0.0:161 .1.3.6.1.4.1.2021.9" There should be no OID found. Repeat steps 2 and 3 after uncommenting the two lines in the Dockerfile that apply the patch. Now proper data should arrive about the root filesystem. I would like to get an SRU with this patch for Jammy. There should be no risk except for snmpd users. The patch is recent and not released, so it is not widely tested yet. It should only impact snmpd users with Docker containers, since it only expands the list of recognized filesystems with "overlay". This feature was broken since Focal, so I assume there aren't many such users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/2007856/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2007798] Re: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while
** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New -- 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/2007798 Title: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: [Summary] During the kernel SRU testing on focal-hwe, I found the audio output of some machines are broken. I've tested some of machine on Jammy using same kernel(5.15.0-66-generic) and haven't seen this happened. The volume bars in settings react to what sound is played correctly and device is detected as well. [Reproduce steps] 1. install focal 2. enable -proposed 3. run apt dist-upgrade. 4. reboot. 5. press fn keys to volume up then volume down or play a short youtube video. 6. after a while can't hear any sound from the speaker. [Failure rate] 10/10 [Additional info] If I run "sudo alsa force-reload" can make audio work again, but after a while it breaks again. These are machines that impacted by this bug: https://certification.canonical.com/hardware/202007-28045/ https://certification.canonical.com/hardware/201906-27109/ https://certification.canonical.com/hardware/201903-26881/ https://certification.canonical.com/hardware/202007-28047/ https://certification.canonical.com/hardware/202007-28055/ https://certification.canonical.com/hardware/202005-27899/ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.15.0-66.73~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1303 F pulseaudio CasperMD5CheckResult: skip Date: Sun Feb 19 21:24:59 2023 InstallationDate: Installed on 2020-08-03 (930 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Cannon Lake PCH cAVS - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: Feb 19 20:53:23 dell-inspiron-7591-nebula-n15a-c2-201903-26881 dbus-daemon[985]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.34' (uid=1000 pid=1303 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2019 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd11/06/2019:br1.5:svnDellInc.:pnInspiron7590:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0922: dmi.product.family: Inspiron dmi.product.name: Inspiron 7590 dmi.product.sku: 0922 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007798/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2007837] [NEW] 22.04: Backport request from 3.2.4 for fix of 3.2.3 regression
Public bug reported: rsync 3.2.3 (packaged in Ubuntu 22.04) changes stderr handling, leading another bug in libfile-rsyncp-perl (in Ubuntu 18.04 and 20.04) to surface [1]. It practically makes using BackupPC 3 impossible with clients using rsync 3.2.3, as is packaged for 22.04. The fact that BackupPC on 20.04 can't be used to back up machines with 22.04 is rather surprising and has bitten other users [2]. It's unclear whether the bug will be fixed in 18.04's and 20.04's libfile-rsyncp-perl package (for status, see [3]). Because of this, the rsync maintainer has included a patch in 3.2.4 that fixes this regression [4] (even though not strictly an rsync bug). As a result, rsync 3.2.3 is the only affected version, which happens to be the one packaged in 22.04. This report is to request backporting that fix [4] to Ubuntu 22.04, so that things don't silently break in scenarios where the backup server is left at 20.04, and some backup clients happen to upgrade to 22.04. I'm not sure what the criteria for security releases are, but as the issue causes backup denial of service and has easy mitigation, I think it would make sense to put it through the security channel. [1]: https://github.com/WayneD/rsync/issues/95#issuecomment-699185358 [2]: https://www.mail-archive.com/backuppc-users@lists.sourceforge.net/msg32673.html [3]: https://bugs.launchpad.net/ubuntu/+source/libfile-rsyncp-perl/+bug/2007833 [4]: https://github.com/WayneD/rsync/commit/4adfdaaf12db26c348b4d6150119b377f9b622c8 ** Affects: rsync (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/2007837 Title: 22.04: Backport request from 3.2.4 for fix of 3.2.3 regression Status in rsync package in Ubuntu: New Bug description: rsync 3.2.3 (packaged in Ubuntu 22.04) changes stderr handling, leading another bug in libfile-rsyncp-perl (in Ubuntu 18.04 and 20.04) to surface [1]. It practically makes using BackupPC 3 impossible with clients using rsync 3.2.3, as is packaged for 22.04. The fact that BackupPC on 20.04 can't be used to back up machines with 22.04 is rather surprising and has bitten other users [2]. It's unclear whether the bug will be fixed in 18.04's and 20.04's libfile-rsyncp-perl package (for status, see [3]). Because of this, the rsync maintainer has included a patch in 3.2.4 that fixes this regression [4] (even though not strictly an rsync bug). As a result, rsync 3.2.3 is the only affected version, which happens to be the one packaged in 22.04. This report is to request backporting that fix [4] to Ubuntu 22.04, so that things don't silently break in scenarios where the backup server is left at 20.04, and some backup clients happen to upgrade to 22.04. I'm not sure what the criteria for security releases are, but as the issue causes backup denial of service and has easy mitigation, I think it would make sense to put it through the security channel. [1]: https://github.com/WayneD/rsync/issues/95#issuecomment-699185358 [2]: https://www.mail-archive.com/backuppc-users@lists.sourceforge.net/msg32673.html [3]: https://bugs.launchpad.net/ubuntu/+source/libfile-rsyncp-perl/+bug/2007833 [4]: https://github.com/WayneD/rsync/commit/4adfdaaf12db26c348b4d6150119b377f9b622c8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2007837/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2007830] Re: Display issue after boot - secondary screen not working since last kernel upgrade
Thanks for the bug report. It looks like Nvidia is your primary GPU and that driver is working fine. If you have any monitors not working then they might be connected to the Intel GPU. Your Intel graphics driver is reporting some unusual kernel errors I've never seen before but they sound related. It also looks like your BIOS has hidden/disabled the Intel GPU completely. So this is really only a bug if the secondary monitor is connected to the Nvidia GPU. Please run these commands: grep . /sys/class/drm/*/status > drmconn.txt journalctl -b0 > journal.txt and attach the resulting text files here. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Tags added: i915 multigpu nvidia -- 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/2007830 Title: Display issue after boot - secondary screen not working since last kernel upgrade Status in Ubuntu: Incomplete Bug description: Display on the second screen does not work since last kernel upgrade. It works using the previous one. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .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 525.78.01 Mon Dec 26 05:58:42 UTC 2022 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1) ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 20 10:16:57 2023 DistUpgraded: 2022-10-21 09:45:54,530 DEBUG icon theme changed, re-reading DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: nvidia/525.78.01, 5.19.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: Dell HD Graphics 630 [1028:0774] NVIDIA Corporation GP104BM [GeForce GTX 1080 Mobile] [10de:1be0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GeForce GTX 1080 Max-Q [1028:07c0] InstallationDate: Installed on 2022-10-12 (130 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Alienware Alienware 15 R3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=/dev/mapper/vgubuntu-root ro SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2022-10-21 (122 days ago) dmi.bios.date: 07/21/2020 dmi.bios.release: 1.10 dmi.bios.vendor: Alienware dmi.bios.version: 1.10.0 dmi.board.name: Alienware 15 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.10.0:bd07/21/2020:br1.10:svnAlienware:pnAlienware15R3:pvr1.10.0:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:sku0774: dmi.product.family: Alienware dmi.product.name: Alienware 15 R3 dmi.product.sku: 0774 dmi.product.version: 1.10.0 dmi.sys.vendor: Alienware version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 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:21.1.4-2ubuntu1.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-3 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/+bug/2007830/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1997532] Re: Traffic leaks from the cellular when WIFI and cellular are opned at the same time;
** Package changed: compiz-plugins-main (Ubuntu) => modemmanager (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1997532 Title: Traffic leaks from the cellular when WIFI and cellular are opned at the same time; Status in modemmanager package in Ubuntu: New Bug description: 1.Environment FW Packkage=18601.5001.00.01.16.30 Enumeration Port：wwan0at0,wwan0at1,wwan0mbim0 OS: Ubuntu22.04.1 Test SIM Card: Unicom Module IMEI: 863714050025511 ModemManager：1.19.1； Libmbim:1.27.9 IOSM: 8.06.13 Kernel: 6.0 2. Test Steps 1). Open WIFI and connect available network; 2). Ping baidu.com always; 3). Send watch more /proc/net/dev to view WIFI traffic； 4). Insert SIM card; 5). Wait cellular connect successfully； 6). Send watch more /proc/net/dev to view WIFI and cellular traffic； 3. Expected Result Traffic only takes alway WIFI channel when WIFI and cellular opened at the same time. 4. Actual Result Traffic leaks from the cellular when WIFI and cellular are opned at the same time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1997532/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1997532] [NEW] Traffic leaks from the cellular when WIFI and cellular are opned at the same time;
You have been subscribed to a public bug: 1.Environment FW Packkage=18601.5001.00.01.16.30 Enumeration Port：wwan0at0,wwan0at1,wwan0mbim0 OS: Ubuntu22.04.1 Test SIM Card: Unicom Module IMEI: 863714050025511 ModemManager：1.19.1； Libmbim:1.27.9 IOSM: 8.06.13 Kernel: 6.0 2. Test Steps 1). Open WIFI and connect available network; 2). Ping baidu.com always; 3). Send watch more /proc/net/dev to view WIFI traffic； 4). Insert SIM card; 5). Wait cellular connect successfully； 6). Send watch more /proc/net/dev to view WIFI and cellular traffic； 3. Expected Result Traffic only takes alway WIFI channel when WIFI and cellular opened at the same time. 4. Actual Result Traffic leaks from the cellular when WIFI and cellular are opned at the same time. ** Affects: modemmanager (Ubuntu) Importance: Undecided Status: New -- Traffic leaks from the cellular when WIFI and cellular are opned at the same time; https://bugs.launchpad.net/bugs/1997532 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager 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 2007830] [NEW] Display issue after boot - secondary screen not working since last kernel upgrade
Public bug reported: Display on the second screen does not work since last kernel upgrade. It works using the previous one. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .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 525.78.01 Mon Dec 26 05:58:42 UTC 2022 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1) ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 20 10:16:57 2023 DistUpgraded: 2022-10-21 09:45:54,530 DEBUG icon theme changed, re-reading DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: nvidia/525.78.01, 5.19.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: Dell HD Graphics 630 [1028:0774] NVIDIA Corporation GP104BM [GeForce GTX 1080 Mobile] [10de:1be0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GeForce GTX 1080 Max-Q [1028:07c0] InstallationDate: Installed on 2022-10-12 (130 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Alienware Alienware 15 R3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=/dev/mapper/vgubuntu-root ro SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2022-10-21 (122 days ago) dmi.bios.date: 07/21/2020 dmi.bios.release: 1.10 dmi.bios.vendor: Alienware dmi.bios.version: 1.10.0 dmi.board.name: Alienware 15 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.10.0:bd07/21/2020:br1.10:svnAlienware:pnAlienware15R3:pvr1.10.0:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:sku0774: dmi.product.family: Alienware dmi.product.name: Alienware 15 R3 dmi.product.sku: 0774 dmi.product.version: 1.10.0 dmi.sys.vendor: Alienware version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 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:21.1.4-2ubuntu1.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-3 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 kinetic 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/2007830 Title: Display issue after boot - secondary screen not working since last kernel upgrade Status in xorg package in Ubuntu: New Bug description: Display on the second screen does not work since last kernel upgrade. It works using the previous one. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .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 525.78.01 Mon Dec 26 05:58:42 UTC 2022 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1) ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 20 10:16:57 2023 DistUpgraded: 2022-10-21 09:45:54,530 DEBUG icon theme changed, re-reading DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: nvid
[Touch-packages] [Bug 2007828] [NEW] /usr/bin/software-properties-gtk:http.client.RemoteDisconnected:poll_for_magic_token:wait:_wait:get_magic_attach_token_info:request_url:readurl:urlopen:open:_open:
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.22.5, the problem page at https://errors.ubuntu.com/problem/14dff5c7440aa4c34eafc2c75fbbad24211c0e85 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- 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/2007828 Title: /usr/bin/software-properties- gtk:http.client.RemoteDisconnected:poll_for_magic_token:wait:_wait:get_magic_attach_token_info:request_url:readurl:urlopen:open:_open:_call_chain:https_open:do_open:getresponse:begin:_read_status Status in software-properties package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.22.5, the problem page at https://errors.ubuntu.com/problem/14dff5c7440aa4c34eafc2c75fbbad24211c0e85 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2007828/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
