[Touch-packages] [Bug 1952083] Re: Add support for Beige Goby
Hello Timo, or anyone else affected, Accepted mesa into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/21.0.3-0ubuntu0.3~20.04.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mesa (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1952083 Title: Add support for Beige Goby Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: Fix Committed Bug description: Impact] New hardware support for AMD's Beige Goby needs a commit backported to mesa. This is only needed on focal, skipping hirsute (no kernel support there). Fixed in impish and up. [Test plan] Install updates, boot a BG machine and check that the desktop has full hardware acceleration. [Where problems could occur] Mesa adds a single commit for enabling BEIGE_GOBY, hard to see what could go wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1952083/+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 1251178] Re: qdbus and qdbusviewer crash with "No such file or directory"
Problem still exist in kubuntu 22.04 as of 21/11/25 qttools5-dev-tools is the package that provides the applications apt tells the user this user@kde-test-system:~$ qdbusviewe Command 'qdbusviewe' not found, did you mean: command 'qdbusviewer' from deb qtchooser (66-2build1) Try: sudo apt install qtchooser is installed ad you get the error user@kde-test-system:~$ qdbusviewer qdbusviewer: could not exec '/usr/lib/qt5/bin/qdbusviewer': No such file or directory this should at lease give a error saying that you need the qttools5-dev- tools package -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1251178 Title: qdbus and qdbusviewer crash with "No such file or directory" Status in qt4-x11 package in Ubuntu: Confirmed Status in qtchooser package in Ubuntu: Confirmed Bug description: Release: Ubuntu 13.10 (32-bit) Package versions: qtdbus 4:4.8.4+dfsg-0ubuntu18 qtchooser 26-3ubuntu2 Expected behavior: The `qdbus` program runs, as does the related program `qdbusviewer`. Actual behavior: If I run the `qdbus` program, it always crashes: user@host:~$ qdbus --help qdbus: could not exec '/usr/lib/i386-linux-gnu/qt5/bin/qdbus': No such file or directory The `qdbus` executable is actually: user@host:~$ ls --full-time $(which qdbus) lrwxrwxrwx 1 root root 9 2013-08-07 14:48:40.0 + /usr/bin/qdbus -> qtchooser Note that `/usr/lib/i386-linux-gnu/qt4/bin/qdbus` exists and seems to work if I invoke it directly. There's a `qdbus-qt5` package in the universe repository. It was not pulled in as a dependency, but manually installing it fixes the issue. Therefore it's either a packaging error or a bug in qtchooser. A similar thing happens if I run `qdbusviewer`: user@host:~$ qdbusviewer qdbusviewer: could not exec '/usr/lib/i386-linux-gnu/qt5/bin/qdbusviewer': No such file or directory except that installing `qdbus-qt5` doesn't fix the issue. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: qdbus 4:4.8.4+dfsg-0ubuntu18 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic i686 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 Date: Thu Nov 14 09:34:24 2013 MarkForUpload: True SourcePackage: qt4-x11 UpgradeStatus: Upgraded to saucy on 2013-10-23 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1251178/+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 1952375] Re: Blutooth headset not taking
Please tell us: 1. The exact model of headset. 2. Whether the Bluetooth pairing is stable and just audio not working, or the whole pairing is lost. ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- 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/1952375 Title: Blutooth headset not taking Status in bluez package in Ubuntu: Incomplete Bug description: Blutooth Headset problem ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: bluez 5.60-0ubuntu2.1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Nov 26 01:09:24 2021 InstallationDate: Installed on 2020-07-22 (491 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b64f Chicony Electronics Co., Ltd HD User Facing Bus 001 Device 003: ID 8087:0026 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A515-54 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.13.0-21-generic root=UUID=c9b8ebcf-747e-454e-8dfb-68b609629c3a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to impish on 2021-10-15 (41 days ago) dmi.bios.date: 08/01/2019 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Doc_WC dmi.board.vendor: CML dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd08/01/2019:br1.11:efr1.6:svnAcer:pnAspireA515-54:pvrV1.11:rvnCML:rnDoc_WC:rvrV1.11:cvnChassisManufacturer:ct10:cvrChassisVersion:sku: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-54 dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: 84:FD:D1:EA:D2:2D ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:151467 acl:66 sco:0 events:20824 errors:0 TX bytes:13788724 acl:20413 sco:0 commands:299 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1952375/+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 1952217] Re: bluetoothd coredumps from double free on connection of headset
Please also check for crash reports so we can identify *which* double- free this is: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment -- 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/1952217 Title: bluetoothd coredumps from double free on connection of headset Status in bluez package in Ubuntu: Incomplete Bug description: Problem: Since the security updates on 2021-11-23 connecting my headset causes bluetoothd to crash, which drops all the other connections. Expected: Headset connects and works as it has done previously. ❯ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 ❯ apt-cache policy bluez bluez: Installed: 5.53-0ubuntu3.4 Candidate: 5.53-0ubuntu3.4 Headset is a Sony WH-1000XM3. I have ppa:berglh/pulseaudio-a2dp installed for the LDAC codecs for this headset. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1952217/+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 1952217] Re: bluetoothd coredumps from double free on connection of headset
Thanks for the bug report. It appears there have been a few double-free fixes in BlueZ over the years. Please try the latest version by live booting Ubuntu 22.04 from USB: http://cdimage.ubuntu.com/daily- live/current/ ** Tags added: focal ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- 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/1952217 Title: bluetoothd coredumps from double free on connection of headset Status in bluez package in Ubuntu: Incomplete Bug description: Problem: Since the security updates on 2021-11-23 connecting my headset causes bluetoothd to crash, which drops all the other connections. Expected: Headset connects and works as it has done previously. ❯ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 ❯ apt-cache policy bluez bluez: Installed: 5.53-0ubuntu3.4 Candidate: 5.53-0ubuntu3.4 Headset is a Sony WH-1000XM3. I have ppa:berglh/pulseaudio-a2dp installed for the LDAC codecs for this headset. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1952217/+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 1698083] Re: Maximize vertically/horizontally doesn't work (in some apps)
Yeah we know. There is an upstream bug about it which was only closed *because* of lack of interest: https://gitlab.gnome.org/GNOME/gtk/-/issues/539 It can always be reopened by a GNOME developer. -- 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/1698083 Title: Maximize vertically/horizontally doesn't work (in some apps) Status in GTK+: Unknown Status in gtk+3.0 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Triaged Bug description: Upstream: https://gitlab.gnome.org/GNOME/gtk/issues/539 In Gnome Tweak Tool you can configure vertical maximizing for: Windows > Titlebar Actions > Middle-Click However this feature seems to get ignored in Wayland sessions (it just maximizes fully instead). It only works correctly in Xorg Gnome sessions. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu6 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Thu Jun 15 14:46:04 2017 DisplayManager: lightdm InstallationDate: Installed on 2017-05-03 (43 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1698083/+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 1952264] Re: ntpd interface listing is bugged
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ntp (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1952264 Title: ntpd interface listing is bugged Status in NTP Charm: Invalid Status in ntp package in Ubuntu: Confirmed Bug description: This charm sets up ntpmon and nagios checks to alert when ntp was not able to select a sync peer. On a server without a routable ipv6 configured, ntpq -p fails with: $ ntpq -p localhost: timed out, nothing received ***Request timed out $ /opt/ntpmon-ntp-charm/check_ntpmon.py --check sync CRITICAL: No sync peer selected | frequency= offset=nan peers=0 reach=nan result=2 rootdelay= rootdisp= runtime= stratum= sync=0.00 sysjitter= sysoffset= tracehosts= traceloops= tracetime= This results in a nagios alert complaining about the problem. Although: $ ntpq -p -4 remote refid st t when poll reach delay offset jitter == *hostname1 xxx.xxx.xxx.x2 u 210 256 3770.8420.031 0.050 +hostname2 xxx.xxx.xxx.x2 u 88 256 3770.3270.062 0.107 -hostname3 xxx.xxx.xxx.x2 u 210 256 377 75.810 -1.198 1.035 +hostname4 xxx.xxx.xxx.x2 u 68 256 3770.7510.078 0.193 $ ntpq -p -4 | /opt/ntpmon-ntp-charm/check_ntpmon.py --check sync --test OK: Time is in sync with hostname1 | frequency= offset=0.57 peers=4 reach=100.00 result=0 rootdelay= rootdisp= runtime= stratum= sync=1.00 sysjitter= sysoffset= tracehosts= traceloops= tracetime= Maybe this is a bug to file against ntp itself ? Or some configuration could allow ntpq -p and check_ntpmon.py to succeed ? I've tested running ntpd with -4 (using defaults file) but with no luck. Let us know if you need more information. Thank you, Loïc To manage notifications about this bug go to: https://bugs.launchpad.net/ntp-charm/+bug/1952264/+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 1952375] [NEW] Blutooth headset not taking
Public bug reported: Blutooth Headset problem ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: bluez 5.60-0ubuntu2.1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Nov 26 01:09:24 2021 InstallationDate: Installed on 2020-07-22 (491 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b64f Chicony Electronics Co., Ltd HD User Facing Bus 001 Device 003: ID 8087:0026 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A515-54 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.13.0-21-generic root=UUID=c9b8ebcf-747e-454e-8dfb-68b609629c3a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to impish on 2021-10-15 (41 days ago) dmi.bios.date: 08/01/2019 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Doc_WC dmi.board.vendor: CML dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd08/01/2019:br1.11:efr1.6:svnAcer:pnAspireA515-54:pvrV1.11:rvnCML:rnDoc_WC:rvrV1.11:cvnChassisManufacturer:ct10:cvrChassisVersion:sku: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-54 dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer hciconfig: hci0: Type: Primary Bus: USB BD Address: 84:FD:D1:EA:D2:2D ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:151467 acl:66 sco:0 events:20824 errors:0 TX bytes:13788724 acl:20413 sco:0 commands:299 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- 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/1952375 Title: Blutooth headset not taking Status in bluez package in Ubuntu: New Bug description: Blutooth Headset problem ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: bluez 5.60-0ubuntu2.1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Nov 26 01:09:24 2021 InstallationDate: Installed on 2020-07-22 (491 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b64f Chicony Electronics Co., Ltd HD User Facing Bus 001 Device 003: ID 8087:0026 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A515-54 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.13.0-21-generic root=UUID=c9b8ebcf-747e-454e-8dfb-68b609629c3a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to impish on 2021-10-15 (41 days ago) dmi.bios.date: 08/01/2019 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Doc_WC dmi.board.vendor: CML dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd08/01/2019:br1.11:efr1.6:svnAcer:pnAspireA515-54:pvrV1.11:rvnCML:rnDoc_WC:rvrV1.11:cvnChassisManufacturer:ct10:cvrChassisVersion:sku: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-54 dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: 84:FD:D1:EA:D2:2D ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:151467 acl:66 sco:0 events:20824 errors:0 TX bytes:13788724 acl:20413 sco:0 commands:299 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1952375/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1951470] Re: webkit javascript segmentation fault
This bug was fixed in the package qtwebkit-opensource-src - 5.212.0~alpha4-14 --- qtwebkit-opensource-src (5.212.0~alpha4-14) unstable; urgency=medium * debian/patches/jscore_big_endian.diff: Fix segmentation fault on s390x and potentially other 64-bit big endian systems (LP: #1951470). Thanks Andreas Krebbel for the patch and Frank Heimes for the initial debdiff! * Update debian/source/lintian-overrides for Lintian 2.109. -- Dmitry Shachnev Wed, 24 Nov 2021 22:27:08 +0300 ** Changed in: qtwebkit-opensource-src (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtwebkit-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1951470 Title: webkit javascript segmentation fault Status in Ubuntu on IBM z Systems: In Progress Status in qtwebkit-opensource-src package in Ubuntu: Fix Released Status in qtwebkit-opensource-src source package in Focal: In Progress Status in qtwebkit-opensource-src source package in Hirsute: In Progress Status in qtwebkit-opensource-src source package in Impish: In Progress Status in qtwebkit-opensource-src source package in Jammy: Fix Released Bug description: SRU Justification: [Impact] * WebKit Javascript engine is causing a segmentation fault on big endian (s390x) systems. * This happens for example when transferring an html to a pdf file using wkhtmltopdf. * The fix is relatively simple with changing loadisFromInstruction to loadpFromInstruction in macro getProperty(slow), which solves this unpleasant situation. * The JIT ocde is 32bit (even on 64bit systems), hence is crucial to make sure the lower part of a 64bit value is taken on big endian systems. [Test Plan] * Testing is very straight forward by following these steps: * install the following packages (incl. their dependencies): $ sudo apt install libqt5webkit5 wkhtmltopdf * create an html file like this: $ vi index.html $ cat index.html * create a JavaScript file like this: $ vi min.js $ cat min.js var i = Math.max * call wkhtmltopdf to process the local files: $ wkhtmltopdf --enable-local-file-access index.html test.pdf * if it's broken one gets this output: Loading page (1/2) Segmentation fault (core dumped) ] 50% and no pdf file was generated: $ ls *.pdf ls: cannot access '*.pdf': No such file or directory * in case it's fixed one gets this output: Loading page (1/2) Printing pages (2/2) Done and a pdf file was generated and in placed in the current directory (with more than 0 bytes size): $ ls -l ./*.pdf -rw-rw-r-- 1 ubuntu ubuntu 1339 Nov 24 11:48 ./test.pdf [Where problems could occur] * While this issue only affects big endian systems (like s390x), a bad fix may have an impact on little endian systems, too for example in case the wrong function got used in the macro. * But loadpFromInstruction is known to work for LE and BE systems; * and on top cross-architecture builds were done: https://launchpad.net/~fheimes/+archive/ubuntu/lp1951470 * and tested on s390x (if the fix works) and on non-s390x (regression testing). * The changes are otherwise very limited, just: macro getProperty(slow) -loadisFromInstruction(6, t1) +loadpFromInstruction(6, t1) hence I think there is not much more to say. [Other Info] * The maintainer of the Debian packages (Dmitry Shachnev) is going to add this to the Debian package, too. * This issue affects Ubuntu jammy, impish, hirsute and focal - SRUs are ongoing. * The issue does not occur with the very latest upstream version anymore, and was fixed in a similar way as part of a commit that fixes numerous other CLoop issues on top: "Fix all CLoop JSC test failures (including some LLInt bugs due to recent bytecode format change)." commit 3fdde71c7d95d758a61fcbc4c58168616794c102 __ == Comment: #0 - Andreas Krebbel - 2021-11-15 09:29:44 == ---Problem Description--- Segmentation fault from WebKit Javascript engine Contact Information = andreas.kreb...@de.ibm.com ---uname output--- Linux 193438490afd 5.8.15-301.fc33.s390x #1 SMP Thu Oct 15 15:55:57 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = IBM Z ---Debugger--- A debugger is not configured ---Steps to Reproduce--- index.html: min.js: var i = Math.max wkhtmltopdf index.html test.pdf QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' Loading page (1/2) Segmentation fault
[Touch-packages] [Bug 1927255] Re: [USB-Audio - RODECaster Pro, playback] Sound is distorted (20.04)
My bad, I thought that the brand of the main USB controller was directly correlated to the motherboard chipset. (In my case, the Intel PC includes an Intel USB controller and the AMD an AMD USB controller). In any case, if you have the possibility to post a log of your different configurations, it might help us (dmesg, pacmd list-sinks output), thanks! -- 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/1927255 Title: [USB-Audio - RODECaster Pro, playback] Sound is distorted (20.04) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I got a Rodecaster Pro USB device that has been causing trouble before and already lead to quirk handling in the kernel for the sample rate, see https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/sound/usb/format.c?h=v5.8#n412 The Rodecaster is running fine on my laptop, but on my desktop, only audio input is working. The audio output is distorted. It's played kind of very slowly. Interestingly, if the source is a video file, the video plays slower, e.g. YouTube in a browser. I have never seen anything like that before. I have tried to figure out what the cause might be and I think I have reached the end of where I can get to on my own. I have documented most things at https://ubuntuforums.org/showthread.php?t=2461568 Putting my last step it in a nutshell: I have booted both my computers with a plain Ubuntu 21.04 from a pen drive (it uses kernel version 5.11.0-16-generic) to make sure it's not some different configuration that I have set up over the years on my systems (both Ubuntu 20.04 with kernel 5.8.18). I attached the Rodecaster. It runs fine on my laptop, but not on my desktop (used the output test from). I then detected the card number with aplay -l I killed pulseaudio with pulseaudio -k I then played the same sample (encoded in 48000 Hz in PCM signed 32 bit little endian format) using aplay -f S32_LE -c 2 -r 48000 -D hw:x ~/sample.wav where x is the appropriate card number and the rest of the arguments meet the Rodecaster's narrow specification. It's playing fine on the laptop, but distorted on the desktop. As far as I understand using aplay this way without a plugin should send the file directly to the device, so I assume there's something on the way from aplay to the Rodecaster that's interfering (kernel or even some piece of hardware) - and that definitely is where my expertise ends (rather a little before :-)). I'll gladly contribute any information that could be useful and I will willingly help to debug this problem if it may be related to the kernel. If there's anything I can do, please let me know. Cheers, Oliver ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.8.18-050818-generic x86_64 NonfreeKernelModules: blackmagic_io nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed May 5 18:28:46 2021 InstallationDate: Installed on 2020-05-15 (355 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Pro failed Symptom_Card: RODECaster Pro - RODECaster Pro Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [USB-Audio - RODECaster Pro, playback] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550-A PRO (MS-7C56) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C56 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1927255/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1952264] Re: ntpd interface listing is bugged
** Summary changed: - ntp sync checks fail when server as no IPv6 connectivity + ntpd interface listing is bugged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1952264 Title: ntpd interface listing is bugged Status in NTP Charm: Invalid Status in ntp package in Ubuntu: New Bug description: This charm sets up ntpmon and nagios checks to alert when ntp was not able to select a sync peer. On a server without a routable ipv6 configured, ntpq -p fails with: $ ntpq -p localhost: timed out, nothing received ***Request timed out $ /opt/ntpmon-ntp-charm/check_ntpmon.py --check sync CRITICAL: No sync peer selected | frequency= offset=nan peers=0 reach=nan result=2 rootdelay= rootdisp= runtime= stratum= sync=0.00 sysjitter= sysoffset= tracehosts= traceloops= tracetime= This results in a nagios alert complaining about the problem. Although: $ ntpq -p -4 remote refid st t when poll reach delay offset jitter == *hostname1 xxx.xxx.xxx.x2 u 210 256 3770.8420.031 0.050 +hostname2 xxx.xxx.xxx.x2 u 88 256 3770.3270.062 0.107 -hostname3 xxx.xxx.xxx.x2 u 210 256 377 75.810 -1.198 1.035 +hostname4 xxx.xxx.xxx.x2 u 68 256 3770.7510.078 0.193 $ ntpq -p -4 | /opt/ntpmon-ntp-charm/check_ntpmon.py --check sync --test OK: Time is in sync with hostname1 | frequency= offset=0.57 peers=4 reach=100.00 result=0 rootdelay= rootdisp= runtime= stratum= sync=1.00 sysjitter= sysoffset= tracehosts= traceloops= tracetime= Maybe this is a bug to file against ntp itself ? Or some configuration could allow ntpq -p and check_ntpmon.py to succeed ? I've tested running ntpd with -4 (using defaults file) but with no luck. Let us know if you need more information. Thank you, Loïc To manage notifications about this bug go to: https://bugs.launchpad.net/ntp-charm/+bug/1952264/+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 1721398] Re: Missing "idevicerestore" & "libirecovery" from libimobiledevice-utils package
** Changed in: libimobiledevice (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1721398 Title: Missing "idevicerestore" & "libirecovery" from libimobiledevice-utils package Status in libimobiledevice package in Ubuntu: Fix Released Status in libimobiledevice package in Debian: Fix Released Bug description: Currently all of the other important utilities are included for installation on Ubuntu. However currently though a Ubuntu Linux user, is unable to perform an iOS device restore. In order to do so currently the user needs to have some way of running an up to date iTunes software with a usb connection to the iPhone, iPad or iPod Touch. Which is quite a hassle to go through in order to completely reload the device's iOS software. It would be much better if a binary compiled version of the software (idevicerestore and libirecovery) could be included in the utilities package. It would allow the Ubuntu user to be able to quickly and easily perform software update or device restore functions. Without the need for a virtual machine running a compatible version of Windows and iTunes etc. While also saving them from having to run Wine, its dependencies, iTunes and its own software requirements. All the would need is what is required to install idevicerestore and run its actions (the appropriate iOS release download image file). The code for idevice restore is available here (https://cgit.sukimashita.com/idevicerestore.git/) and the library from here (https://cgit.sukimashita.com/libirecovery.git/). Running Ubuntu 16.04.3 libimobiledevice-utils 1.2.0+dfsg-3~ubuntu0.2 installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1721398/+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 1952264] Re: ntp sync checks fail when server as no IPv6 connectivity
I investigated this quite a bit, and this appears to be an ntp bug and not a charm bug. This host is a trusty host, running ntp version 1:4.2.6.p5+dfsg-3ubuntu2.14.04.13. We have other hosts running the same version that don't have the problem described above. I spent quite some time investigating this, comparing the hosts, running strace etc, and I noticed a subtle difference in /etc/hosts : on the working host, the ::1 entry doesn't have "localhost", but it does on the failing host. When I removed "localhost" from the ::1 entry on the failing host, "ntpq -pn" started working. Investigating things a bit more, I found out that on the working host, ntpd was listening on ::1 but on the failing host, it wasn't (by checking "ss -anupe" output as well as ntpd starting logs). Comparing straces of starting ntpd, I think I was able to find what's going on. On the working host it gives (only relevant output is posted here) : 3973 19:41:32 socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 5 [...] 3973 19:41:32 ioctl(5, SIOCGIFFLAGS, {ifr_name="qvobb268af4-e9", ifr_flags=IFF_UP|IFF_BROADCAST|IFF_RUNNING|IFF_PROMISC|IFF_MULTICAST}) = 0 3973 19:41:32 ioctl(5, SIOCGIFFLAGS, {ifr_name="qbrd5588b49-e3", ifr_flags=IFF_UP|IFF_BROADCAST|IFF_RUNNING|IFF_MULTICAST}) = 0 3973 19:41:32 ioctl(5, SIOCGIFFLAGS, {ifr_name="qvb1693c156-5f", ifr_flags=IFF_UP|IFF_BROADCAST|IFF_RUNNING|IFF_PROMISC|IFF_MULTICAST}) = 0 [... the same for a bunch of interfaces - this is a nova compute node so this is expected ...] 3973 19:41:32 close(5) = 0 But on the failing host, it checks a single interface : 56717 19:37:03 socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 5 [...] 56717 19:37:03 ioctl(5, SIOCGIFFLAGS, {ifr_name="qvbba244f00-69", ifr_flags=IFF_UP|IFF_BROADCAST|IFF_RUNNING|IFF_PROMISC|IFF_MULTICAST}) = 0 56717 19:37:03 close(5) = 0 So I thought this interface was a bit special : $ ip li sh dev qvbba244f00-69 67772: qvbba244f00-69@qvoba244f00-69: mtu 1500 qdisc noqueue master qbrba244f00-69 state UP mode DEFAULT group default qlen 1000 link/ether 0e:ac:86:b1:c8:24 brd ff:ff:ff:ff:ff:ff It appears completely normal, except that it has an unusually high ifindex (67772). Could that be the cause of the problem ? Looking at the source code at https://git.launchpad.net/ubuntu/+source/ntp/tree/?h=ubuntu/trusty- updates : interfaces are parsed looking at the /proc/net/if_inet6 file (https://git.launchpad.net/ubuntu/+source/ntp/tree/lib/isc/unix/ifiter_getifaddrs.c?h=ubuntu/trusty- updates#n54) which strace confirms : 3973 19:41:32 open("/proc/net/if_inet6", O_RDONLY) = 6 Each line is parsed using fgets : fgets(iter->entry, sizeof(iter->entry), iter->proc) != NULL) https://git.launchpad.net/ubuntu/+source/ntp/tree/lib/isc/unix/interfaceiter.c?h=ubuntu/trusty- updates#n181 What's sizeof(iter->entry) ? Well "entry" is defined like that : charentry[ISC_IF_INET6_SZ]; https://git.launchpad.net/ubuntu/+source/ntp/tree/lib/isc/unix/ifiter_getifaddrs.c?h=ubuntu/trusty- updates#n48 And ISC_IF_INET6_SZ is : #define ISC_IF_INET6_SZ \ sizeof("0001 01 80 10 80 XXlo\n") https://git.launchpad.net/ubuntu/+source/ntp/tree/lib/isc/unix/interfaceiter.c?h=ubuntu/trusty- updates#n153 And this is where the problem is. The computation of ISC_IF_INET6_SZ assumes that ifindex will be 2 chars (in hex), so that ifindex will be < 256. However, ifindexes higher than that are likely common, so why don't we see this bug elsewhere ? Well because the computation of ISC_IF_INET6_SZ also assumes that the interface name is 16 chars. In our example, the interface name is "only" 14 chars, so we have a buffer of 2 chars for the ifindex. But that's not enough, it's off by 1 in fact ! "0001 01 80 10 80 XXlo\n" is 62 chars long. The first line of if_inet6 on our machine is : fe800cac86fffeb1c824 108bc 40 20 80 qvbba244f00-69, and that's 62 chars long... but without the \n ! So what might be happening here is that the first iteration of the loop will properly read the whole line except the \n, and the next iteration will resume at that location, and because fgets() stops at EOF or newline, it will just return a newline, which will make the whole iteration stop. The fix here is pretty simple : the computation of ISC_IF_INET6_SZ should assume an ifindex of UINT_MAX, ie (or any 8-chars number). If I can trust https://git.launchpad.net/ubuntu/+source/ntp/tree/lib/isc/unix/interfaceiter.c?h=applied/ubuntu/jammy this is still present in Jammy. Redirecting the bug to the "ntp" package. ** Also affects: ntp (Ubuntu) Importance: Undecided Status: New ** Changed in: ntp-charm Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1952264 Title: ntp sync
[Touch-packages] [Bug 1927255] Re: [USB-Audio - RODECaster Pro, playback] Sound is distorted (20.04)
@cijay Amendmend, since you're mentioning your computer's CPUs - that's not what I was referring to when I mentioned an AMD chipset, but the USB controller chipset that's also made by AMD. -- 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/1927255 Title: [USB-Audio - RODECaster Pro, playback] Sound is distorted (20.04) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I got a Rodecaster Pro USB device that has been causing trouble before and already lead to quirk handling in the kernel for the sample rate, see https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/sound/usb/format.c?h=v5.8#n412 The Rodecaster is running fine on my laptop, but on my desktop, only audio input is working. The audio output is distorted. It's played kind of very slowly. Interestingly, if the source is a video file, the video plays slower, e.g. YouTube in a browser. I have never seen anything like that before. I have tried to figure out what the cause might be and I think I have reached the end of where I can get to on my own. I have documented most things at https://ubuntuforums.org/showthread.php?t=2461568 Putting my last step it in a nutshell: I have booted both my computers with a plain Ubuntu 21.04 from a pen drive (it uses kernel version 5.11.0-16-generic) to make sure it's not some different configuration that I have set up over the years on my systems (both Ubuntu 20.04 with kernel 5.8.18). I attached the Rodecaster. It runs fine on my laptop, but not on my desktop (used the output test from). I then detected the card number with aplay -l I killed pulseaudio with pulseaudio -k I then played the same sample (encoded in 48000 Hz in PCM signed 32 bit little endian format) using aplay -f S32_LE -c 2 -r 48000 -D hw:x ~/sample.wav where x is the appropriate card number and the rest of the arguments meet the Rodecaster's narrow specification. It's playing fine on the laptop, but distorted on the desktop. As far as I understand using aplay this way without a plugin should send the file directly to the device, so I assume there's something on the way from aplay to the Rodecaster that's interfering (kernel or even some piece of hardware) - and that definitely is where my expertise ends (rather a little before :-)). I'll gladly contribute any information that could be useful and I will willingly help to debug this problem if it may be related to the kernel. If there's anything I can do, please let me know. Cheers, Oliver ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.8.18-050818-generic x86_64 NonfreeKernelModules: blackmagic_io nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed May 5 18:28:46 2021 InstallationDate: Installed on 2020-05-15 (355 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Pro failed Symptom_Card: RODECaster Pro - RODECaster Pro Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [USB-Audio - RODECaster Pro, playback] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550-A PRO (MS-7C56) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C56 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1927255/+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 1927255] Re: [USB-Audio - RODECaster Pro, playback] Sound is distorted (20.04)
@cijay The AMD chipset as the culprit is the best hypothesis so far. I have not checked for differences in the configuration, but only been enjoying the Rødecaster on a non-AMD chipset port. -- 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/1927255 Title: [USB-Audio - RODECaster Pro, playback] Sound is distorted (20.04) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I got a Rodecaster Pro USB device that has been causing trouble before and already lead to quirk handling in the kernel for the sample rate, see https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/sound/usb/format.c?h=v5.8#n412 The Rodecaster is running fine on my laptop, but on my desktop, only audio input is working. The audio output is distorted. It's played kind of very slowly. Interestingly, if the source is a video file, the video plays slower, e.g. YouTube in a browser. I have never seen anything like that before. I have tried to figure out what the cause might be and I think I have reached the end of where I can get to on my own. I have documented most things at https://ubuntuforums.org/showthread.php?t=2461568 Putting my last step it in a nutshell: I have booted both my computers with a plain Ubuntu 21.04 from a pen drive (it uses kernel version 5.11.0-16-generic) to make sure it's not some different configuration that I have set up over the years on my systems (both Ubuntu 20.04 with kernel 5.8.18). I attached the Rodecaster. It runs fine on my laptop, but not on my desktop (used the output test from). I then detected the card number with aplay -l I killed pulseaudio with pulseaudio -k I then played the same sample (encoded in 48000 Hz in PCM signed 32 bit little endian format) using aplay -f S32_LE -c 2 -r 48000 -D hw:x ~/sample.wav where x is the appropriate card number and the rest of the arguments meet the Rodecaster's narrow specification. It's playing fine on the laptop, but distorted on the desktop. As far as I understand using aplay this way without a plugin should send the file directly to the device, so I assume there's something on the way from aplay to the Rodecaster that's interfering (kernel or even some piece of hardware) - and that definitely is where my expertise ends (rather a little before :-)). I'll gladly contribute any information that could be useful and I will willingly help to debug this problem if it may be related to the kernel. If there's anything I can do, please let me know. Cheers, Oliver ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.8.18-050818-generic x86_64 NonfreeKernelModules: blackmagic_io nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed May 5 18:28:46 2021 InstallationDate: Installed on 2020-05-15 (355 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Pro failed Symptom_Card: RODECaster Pro - RODECaster Pro Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [USB-Audio - RODECaster Pro, playback] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550-A PRO (MS-7C56) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C56 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1927255/+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 1927255] Re: [USB-Audio - RODECaster Pro, playback] Sound is distorted (20.04)
Not sure about this rumor about AMD chipset being the culprit. Two of my computers (running Ubuntu 20.04 with the 5.11.0-40-generic kernel) have the problem of distorted sound when I use the Rodecaster Pro as audio output. The first is a desktop using an AMD Rysen 9 and the other is a Dell XPS laptop using a 10ᵉ generation Intel Core i7. @otacke, when you use a regular USB port of your motherboard or when you use a USB port of the PCI card, have you noticed any difference in the Pulseaudio or Alsa configurations? -- 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/1927255 Title: [USB-Audio - RODECaster Pro, playback] Sound is distorted (20.04) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I got a Rodecaster Pro USB device that has been causing trouble before and already lead to quirk handling in the kernel for the sample rate, see https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/sound/usb/format.c?h=v5.8#n412 The Rodecaster is running fine on my laptop, but on my desktop, only audio input is working. The audio output is distorted. It's played kind of very slowly. Interestingly, if the source is a video file, the video plays slower, e.g. YouTube in a browser. I have never seen anything like that before. I have tried to figure out what the cause might be and I think I have reached the end of where I can get to on my own. I have documented most things at https://ubuntuforums.org/showthread.php?t=2461568 Putting my last step it in a nutshell: I have booted both my computers with a plain Ubuntu 21.04 from a pen drive (it uses kernel version 5.11.0-16-generic) to make sure it's not some different configuration that I have set up over the years on my systems (both Ubuntu 20.04 with kernel 5.8.18). I attached the Rodecaster. It runs fine on my laptop, but not on my desktop (used the output test from). I then detected the card number with aplay -l I killed pulseaudio with pulseaudio -k I then played the same sample (encoded in 48000 Hz in PCM signed 32 bit little endian format) using aplay -f S32_LE -c 2 -r 48000 -D hw:x ~/sample.wav where x is the appropriate card number and the rest of the arguments meet the Rodecaster's narrow specification. It's playing fine on the laptop, but distorted on the desktop. As far as I understand using aplay this way without a plugin should send the file directly to the device, so I assume there's something on the way from aplay to the Rodecaster that's interfering (kernel or even some piece of hardware) - and that definitely is where my expertise ends (rather a little before :-)). I'll gladly contribute any information that could be useful and I will willingly help to debug this problem if it may be related to the kernel. If there's anything I can do, please let me know. Cheers, Oliver ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.8.18-050818-generic x86_64 NonfreeKernelModules: blackmagic_io nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed May 5 18:28:46 2021 InstallationDate: Installed on 2020-05-15 (355 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Pro failed Symptom_Card: RODECaster Pro - RODECaster Pro Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [USB-Audio - RODECaster Pro, playback] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550-A PRO (MS-7C56) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C56 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to:
[Touch-packages] [Bug 1951470] Re: webkit javascript segmentation fault
** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtwebkit-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1951470 Title: webkit javascript segmentation fault Status in Ubuntu on IBM z Systems: In Progress Status in qtwebkit-opensource-src package in Ubuntu: Fix Committed Status in qtwebkit-opensource-src source package in Focal: In Progress Status in qtwebkit-opensource-src source package in Hirsute: In Progress Status in qtwebkit-opensource-src source package in Impish: In Progress Status in qtwebkit-opensource-src source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] * WebKit Javascript engine is causing a segmentation fault on big endian (s390x) systems. * This happens for example when transferring an html to a pdf file using wkhtmltopdf. * The fix is relatively simple with changing loadisFromInstruction to loadpFromInstruction in macro getProperty(slow), which solves this unpleasant situation. * The JIT ocde is 32bit (even on 64bit systems), hence is crucial to make sure the lower part of a 64bit value is taken on big endian systems. [Test Plan] * Testing is very straight forward by following these steps: * install the following packages (incl. their dependencies): $ sudo apt install libqt5webkit5 wkhtmltopdf * create an html file like this: $ vi index.html $ cat index.html * create a JavaScript file like this: $ vi min.js $ cat min.js var i = Math.max * call wkhtmltopdf to process the local files: $ wkhtmltopdf --enable-local-file-access index.html test.pdf * if it's broken one gets this output: Loading page (1/2) Segmentation fault (core dumped) ] 50% and no pdf file was generated: $ ls *.pdf ls: cannot access '*.pdf': No such file or directory * in case it's fixed one gets this output: Loading page (1/2) Printing pages (2/2) Done and a pdf file was generated and in placed in the current directory (with more than 0 bytes size): $ ls -l ./*.pdf -rw-rw-r-- 1 ubuntu ubuntu 1339 Nov 24 11:48 ./test.pdf [Where problems could occur] * While this issue only affects big endian systems (like s390x), a bad fix may have an impact on little endian systems, too for example in case the wrong function got used in the macro. * But loadpFromInstruction is known to work for LE and BE systems; * and on top cross-architecture builds were done: https://launchpad.net/~fheimes/+archive/ubuntu/lp1951470 * and tested on s390x (if the fix works) and on non-s390x (regression testing). * The changes are otherwise very limited, just: macro getProperty(slow) -loadisFromInstruction(6, t1) +loadpFromInstruction(6, t1) hence I think there is not much more to say. [Other Info] * The maintainer of the Debian packages (Dmitry Shachnev) is going to add this to the Debian package, too. * This issue affects Ubuntu jammy, impish, hirsute and focal - SRUs are ongoing. * The issue does not occur with the very latest upstream version anymore, and was fixed in a similar way as part of a commit that fixes numerous other CLoop issues on top: "Fix all CLoop JSC test failures (including some LLInt bugs due to recent bytecode format change)." commit 3fdde71c7d95d758a61fcbc4c58168616794c102 __ == Comment: #0 - Andreas Krebbel - 2021-11-15 09:29:44 == ---Problem Description--- Segmentation fault from WebKit Javascript engine Contact Information = andreas.kreb...@de.ibm.com ---uname output--- Linux 193438490afd 5.8.15-301.fc33.s390x #1 SMP Thu Oct 15 15:55:57 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = IBM Z ---Debugger--- A debugger is not configured ---Steps to Reproduce--- index.html: min.js: var i = Math.max wkhtmltopdf index.html test.pdf QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' Loading page (1/2) Segmentation fault (core dumped) ] 17% Userspace tool common name: wkhtmltopdf The userspace tool has the following bit modes: 64 Userspace rpm: libqt5webkit5 Userspace tool obtained from project website: na *Additional Instructions for andreas.kreb...@de.ibm.com: -Attach ltrace and strace of userspace application. == Comment: #1 - Andreas Krebbel - 2021-11-15 09:44:04 == In CodeBlock.cpp the code preparing the operands of op_get_from_scope writes the property offset
[Touch-packages] [Bug 1951470] Re: webkit javascript segmentation fault
** Changed in: qtwebkit-opensource-src (Ubuntu Focal) Status: New => In Progress ** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtwebkit-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1951470 Title: webkit javascript segmentation fault Status in Ubuntu on IBM z Systems: In Progress Status in qtwebkit-opensource-src package in Ubuntu: Fix Committed Status in qtwebkit-opensource-src source package in Focal: In Progress Status in qtwebkit-opensource-src source package in Hirsute: In Progress Status in qtwebkit-opensource-src source package in Impish: In Progress Status in qtwebkit-opensource-src source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] * WebKit Javascript engine is causing a segmentation fault on big endian (s390x) systems. * This happens for example when transferring an html to a pdf file using wkhtmltopdf. * The fix is relatively simple with changing loadisFromInstruction to loadpFromInstruction in macro getProperty(slow), which solves this unpleasant situation. * The JIT ocde is 32bit (even on 64bit systems), hence is crucial to make sure the lower part of a 64bit value is taken on big endian systems. [Test Plan] * Testing is very straight forward by following these steps: * install the following packages (incl. their dependencies): $ sudo apt install libqt5webkit5 wkhtmltopdf * create an html file like this: $ vi index.html $ cat index.html * create a JavaScript file like this: $ vi min.js $ cat min.js var i = Math.max * call wkhtmltopdf to process the local files: $ wkhtmltopdf --enable-local-file-access index.html test.pdf * if it's broken one gets this output: Loading page (1/2) Segmentation fault (core dumped) ] 50% and no pdf file was generated: $ ls *.pdf ls: cannot access '*.pdf': No such file or directory * in case it's fixed one gets this output: Loading page (1/2) Printing pages (2/2) Done and a pdf file was generated and in placed in the current directory (with more than 0 bytes size): $ ls -l ./*.pdf -rw-rw-r-- 1 ubuntu ubuntu 1339 Nov 24 11:48 ./test.pdf [Where problems could occur] * While this issue only affects big endian systems (like s390x), a bad fix may have an impact on little endian systems, too for example in case the wrong function got used in the macro. * But loadpFromInstruction is known to work for LE and BE systems; * and on top cross-architecture builds were done: https://launchpad.net/~fheimes/+archive/ubuntu/lp1951470 * and tested on s390x (if the fix works) and on non-s390x (regression testing). * The changes are otherwise very limited, just: macro getProperty(slow) -loadisFromInstruction(6, t1) +loadpFromInstruction(6, t1) hence I think there is not much more to say. [Other Info] * The maintainer of the Debian packages (Dmitry Shachnev) is going to add this to the Debian package, too. * This issue affects Ubuntu jammy, impish, hirsute and focal - SRUs are ongoing. * The issue does not occur with the very latest upstream version anymore, and was fixed in a similar way as part of a commit that fixes numerous other CLoop issues on top: "Fix all CLoop JSC test failures (including some LLInt bugs due to recent bytecode format change)." commit 3fdde71c7d95d758a61fcbc4c58168616794c102 __ == Comment: #0 - Andreas Krebbel - 2021-11-15 09:29:44 == ---Problem Description--- Segmentation fault from WebKit Javascript engine Contact Information = andreas.kreb...@de.ibm.com ---uname output--- Linux 193438490afd 5.8.15-301.fc33.s390x #1 SMP Thu Oct 15 15:55:57 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = IBM Z ---Debugger--- A debugger is not configured ---Steps to Reproduce--- index.html: min.js: var i = Math.max wkhtmltopdf index.html test.pdf QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' Loading page (1/2) Segmentation fault (core dumped) ] 17% Userspace tool common name: wkhtmltopdf The userspace tool has the following bit modes: 64 Userspace rpm: libqt5webkit5 Userspace tool obtained from project website: na *Additional Instructions for andreas.kreb...@de.ibm.com: -Attach ltrace and strace of userspace application. == Comment: #1 - Andreas Krebbel - 2021-11-15 09:44:04 == In CodeBlock.cpp the code preparing the operands of op_get_from_scope writes the property
[Touch-packages] [Bug 1951470] Re: webkit javascript segmentation fault
qtwebkit debdiff (focal) ** Patch added: "qtwebkit debdiff (focal)" https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/1951470/+attachment/5543391/+files/debdiff-qtwebkit-lp1951470-focal.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtwebkit-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1951470 Title: webkit javascript segmentation fault Status in Ubuntu on IBM z Systems: In Progress Status in qtwebkit-opensource-src package in Ubuntu: Fix Committed Status in qtwebkit-opensource-src source package in Focal: In Progress Status in qtwebkit-opensource-src source package in Hirsute: In Progress Status in qtwebkit-opensource-src source package in Impish: In Progress Status in qtwebkit-opensource-src source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] * WebKit Javascript engine is causing a segmentation fault on big endian (s390x) systems. * This happens for example when transferring an html to a pdf file using wkhtmltopdf. * The fix is relatively simple with changing loadisFromInstruction to loadpFromInstruction in macro getProperty(slow), which solves this unpleasant situation. * The JIT ocde is 32bit (even on 64bit systems), hence is crucial to make sure the lower part of a 64bit value is taken on big endian systems. [Test Plan] * Testing is very straight forward by following these steps: * install the following packages (incl. their dependencies): $ sudo apt install libqt5webkit5 wkhtmltopdf * create an html file like this: $ vi index.html $ cat index.html * create a JavaScript file like this: $ vi min.js $ cat min.js var i = Math.max * call wkhtmltopdf to process the local files: $ wkhtmltopdf --enable-local-file-access index.html test.pdf * if it's broken one gets this output: Loading page (1/2) Segmentation fault (core dumped) ] 50% and no pdf file was generated: $ ls *.pdf ls: cannot access '*.pdf': No such file or directory * in case it's fixed one gets this output: Loading page (1/2) Printing pages (2/2) Done and a pdf file was generated and in placed in the current directory (with more than 0 bytes size): $ ls -l ./*.pdf -rw-rw-r-- 1 ubuntu ubuntu 1339 Nov 24 11:48 ./test.pdf [Where problems could occur] * While this issue only affects big endian systems (like s390x), a bad fix may have an impact on little endian systems, too for example in case the wrong function got used in the macro. * But loadpFromInstruction is known to work for LE and BE systems; * and on top cross-architecture builds were done: https://launchpad.net/~fheimes/+archive/ubuntu/lp1951470 * and tested on s390x (if the fix works) and on non-s390x (regression testing). * The changes are otherwise very limited, just: macro getProperty(slow) -loadisFromInstruction(6, t1) +loadpFromInstruction(6, t1) hence I think there is not much more to say. [Other Info] * The maintainer of the Debian packages (Dmitry Shachnev) is going to add this to the Debian package, too. * This issue affects Ubuntu jammy, impish, hirsute and focal - SRUs are ongoing. * The issue does not occur with the very latest upstream version anymore, and was fixed in a similar way as part of a commit that fixes numerous other CLoop issues on top: "Fix all CLoop JSC test failures (including some LLInt bugs due to recent bytecode format change)." commit 3fdde71c7d95d758a61fcbc4c58168616794c102 __ == Comment: #0 - Andreas Krebbel - 2021-11-15 09:29:44 == ---Problem Description--- Segmentation fault from WebKit Javascript engine Contact Information = andreas.kreb...@de.ibm.com ---uname output--- Linux 193438490afd 5.8.15-301.fc33.s390x #1 SMP Thu Oct 15 15:55:57 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = IBM Z ---Debugger--- A debugger is not configured ---Steps to Reproduce--- index.html: min.js: var i = Math.max wkhtmltopdf index.html test.pdf QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' Loading page (1/2) Segmentation fault (core dumped) ] 17% Userspace tool common name: wkhtmltopdf The userspace tool has the following bit modes: 64 Userspace rpm: libqt5webkit5 Userspace tool obtained from project website: na *Additional Instructions for andreas.kreb...@de.ibm.com: -Attach ltrace and strace of userspace application. == Comment: #1 - Andreas Krebbel - 2021-11-15
[Touch-packages] [Bug 1951470] Re: webkit javascript segmentation fault
** Merge proposal linked: https://code.launchpad.net/~fheimes/ubuntu/+source/qtwebkit-opensource-src/+git/qtwebkit-opensource-src/+merge/412408 ** Merge proposal linked: https://code.launchpad.net/~fheimes/ubuntu/+source/qtwebkit-opensource-src/+git/qtwebkit-opensource-src/+merge/412410 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtwebkit-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1951470 Title: webkit javascript segmentation fault Status in Ubuntu on IBM z Systems: In Progress Status in qtwebkit-opensource-src package in Ubuntu: Fix Committed Status in qtwebkit-opensource-src source package in Focal: New Status in qtwebkit-opensource-src source package in Hirsute: In Progress Status in qtwebkit-opensource-src source package in Impish: In Progress Status in qtwebkit-opensource-src source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] * WebKit Javascript engine is causing a segmentation fault on big endian (s390x) systems. * This happens for example when transferring an html to a pdf file using wkhtmltopdf. * The fix is relatively simple with changing loadisFromInstruction to loadpFromInstruction in macro getProperty(slow), which solves this unpleasant situation. * The JIT ocde is 32bit (even on 64bit systems), hence is crucial to make sure the lower part of a 64bit value is taken on big endian systems. [Test Plan] * Testing is very straight forward by following these steps: * install the following packages (incl. their dependencies): $ sudo apt install libqt5webkit5 wkhtmltopdf * create an html file like this: $ vi index.html $ cat index.html * create a JavaScript file like this: $ vi min.js $ cat min.js var i = Math.max * call wkhtmltopdf to process the local files: $ wkhtmltopdf --enable-local-file-access index.html test.pdf * if it's broken one gets this output: Loading page (1/2) Segmentation fault (core dumped) ] 50% and no pdf file was generated: $ ls *.pdf ls: cannot access '*.pdf': No such file or directory * in case it's fixed one gets this output: Loading page (1/2) Printing pages (2/2) Done and a pdf file was generated and in placed in the current directory (with more than 0 bytes size): $ ls -l ./*.pdf -rw-rw-r-- 1 ubuntu ubuntu 1339 Nov 24 11:48 ./test.pdf [Where problems could occur] * While this issue only affects big endian systems (like s390x), a bad fix may have an impact on little endian systems, too for example in case the wrong function got used in the macro. * But loadpFromInstruction is known to work for LE and BE systems; * and on top cross-architecture builds were done: https://launchpad.net/~fheimes/+archive/ubuntu/lp1951470 * and tested on s390x (if the fix works) and on non-s390x (regression testing). * The changes are otherwise very limited, just: macro getProperty(slow) -loadisFromInstruction(6, t1) +loadpFromInstruction(6, t1) hence I think there is not much more to say. [Other Info] * The maintainer of the Debian packages (Dmitry Shachnev) is going to add this to the Debian package, too. * This issue affects Ubuntu jammy, impish, hirsute and focal - SRUs are ongoing. * The issue does not occur with the very latest upstream version anymore, and was fixed in a similar way as part of a commit that fixes numerous other CLoop issues on top: "Fix all CLoop JSC test failures (including some LLInt bugs due to recent bytecode format change)." commit 3fdde71c7d95d758a61fcbc4c58168616794c102 __ == Comment: #0 - Andreas Krebbel - 2021-11-15 09:29:44 == ---Problem Description--- Segmentation fault from WebKit Javascript engine Contact Information = andreas.kreb...@de.ibm.com ---uname output--- Linux 193438490afd 5.8.15-301.fc33.s390x #1 SMP Thu Oct 15 15:55:57 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = IBM Z ---Debugger--- A debugger is not configured ---Steps to Reproduce--- index.html: min.js: var i = Math.max wkhtmltopdf index.html test.pdf QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' Loading page (1/2) Segmentation fault (core dumped) ] 17% Userspace tool common name: wkhtmltopdf The userspace tool has the following bit modes: 64 Userspace rpm: libqt5webkit5 Userspace tool obtained from project website: na *Additional Instructions for andreas.kreb...@de.ibm.com: -Attach ltrace and strace of
[Touch-packages] [Bug 1952353] [NEW] dmesg: read kernel buffer failed: Operation not permitted
Public bug reported: Run /bin/dmesg, get: dmesg: read kernel buffer failed: Operation not permitted sudo dmesg works, but I should not have to do that. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: util-linux 2.36.1-8ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Thu Nov 25 11:13:58 2021 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= SHELL=/bin/tcsh SourcePackage: util-linux UpgradeStatus: Upgraded to impish on 2021-11-21 (3 days ago) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1952353 Title: dmesg: read kernel buffer failed: Operation not permitted Status in util-linux package in Ubuntu: New Bug description: Run /bin/dmesg, get: dmesg: read kernel buffer failed: Operation not permitted sudo dmesg works, but I should not have to do that. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: util-linux 2.36.1-8ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Thu Nov 25 11:13:58 2021 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= SHELL=/bin/tcsh SourcePackage: util-linux UpgradeStatus: Upgraded to impish on 2021-11-21 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1952353/+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 1650688] Re: timedatectl set-timezone fails on UC16
** Tags added: fr-1885 -- 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/1650688 Title: timedatectl set-timezone fails on UC16 Status in Snappy: Triaged Status in systemd package in Ubuntu: New Bug description: SRU === [Impact] * The bug prevents timedated from recognizing and correctly set the system's timezone when running Ubuntu Core 16, 18 and 20. * This causes by timedated fails to take Ubuntu Core's /etc/writable redirection into account. * The recognizing part is fixed by making the code take writable redirection into account. * The set part is fixed by making the code link to the absolute path instead of a relative one. * Currently core snaps worked around the set part by providing a wrapper script which re-create /etc/writable/localtime afterward. However this does not cover DBus users. [Test Plan] * On classics systems: ensure the proposed systemd package is installed. On Ubuntu Core systems: build a new core snap including proposed package, and install it. Replaces timedatectl with timedatectl.real to test skipping the wrapper. (Note that one can simulate core snap's /etc/writable redirection by running this image creation hook [1] on the system.) [1] https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu- core/hooks/08-etc-writable.chroot?h=ubuntu/focal * On freshly boot system: query the timezone using `timedatectl`. The timezone should corresponds to `readlink -f /etc/localtime` and does not show `n/a`. * Set a new timezone: `sudo timedatectl set-timezone Asia/Bangkok`. `readlink -f /etc/localtime` should points to an existing file. * Run `sudo systemctl restart systemd-timedated.service`. Then, query the timezone again: `timedatectl`. It should show the previously set timezone and not `n/a`. * Run `sudo systemctl status systemd-timedated.service`. This should show no sign of timedated crashing. [Where problems could occur] * It's possible that the redirection handling code will be sub-par and causes crash. However, it's not likely because the similar pieces of code is in the previous patch since Ubuntu 16.04. * If it does: the patched `get_timezone()` function is used in 2 places: the networkd's DHCP server [3] and the timedated itself. - Networkd is used primarily on servers where NetworkManage is absent. It's possible that this patch causes the user to loss access to the server due to networkd crash when setting up network interfaces, and requires physical access to fix. However, the code path is executed when DHCP is enabled only. I think it's not common for users to have networkd's DHCP server enabled: the feature seems to gear towards desktop users wanting to share internet connection, and in those cases they're more likely to use NetworkManager. - The timedated itself is likely used by the programs that involves in time-related functions. If a crash occur, in the worst case users won't be able to set time or timezone via timedated. However, users should still be able to e.g. set time using `date` or set timezone using /etc/localtime (assuming online guides still consider systems without systemd). Timedated is DBus-activated, and thus a crash should be self-healing. * The set part would also affects the clasic systems. However, I believe nothing else actually rely on /etc/localtime being a relative path, otherwise the /etc/writable redirection would causes even more problem, and would have been reported. [3] Yes, I'm surprised that there's a DHCP server inside systemd codebase. [Other Info] * This is also useful for UBports's Ubuntu Touch. We continue using system-image system where the rootfs is read-only, and thus is affected by this bug similarly to Ubuntu Core. I've tested the Focal version of the package on our (currently in development) Focal Ubuntu Touch image, and the fix works. [Original bug description] On a system running UC16, the file /etc/localtime is a link that points to /etc/writable/localtime. On a freshly installed system, /etc/writable/localtime is a fully- qualified link that points at /usr/share/zoneinfo/UTC. If timedatectl is used to set the timezone to something else, timedated updates the localtime symbolic link with a relative path to the zoneinfo directory, which results in an invalid link. $ sudo timedatectl set-timezone America/Detroit $ sudo timedatectl Local time: Fri 2016-12-16 18:18:49 EST Universal time: Fri 2016-12-16 23:18:49 UTC RTC time: Fri 2016-12-16 23:18:49 Time zone: America/Detroit (EST, -0500) Network time on: yes NTP synchronized: yes RTC in local TZ: no $ ls -l /etc/writable/localtime /etc/writable/localtime -->
[Touch-packages] [Bug 1951214] Re: ubuntu-bug isn't opening firefox (snap) on jammy, instead gedit gets data
** Tags added: fr-1884 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1951214 Title: ubuntu-bug isn't opening firefox (snap) on jammy, instead gedit gets data Status in apport package in Ubuntu: Confirmed Bug description: This has been reported before on Ubuntu Community Hub, but I want/need a bug report filed on launchpad to report/track on iso.qa.ubuntu.com On a `ubuntu-bug` or apport opening up a bug report; a gedit window opens with --- OpenID transaction in progress https://login.launchpad.net/+openid; method="post" accept-charset="UTF-8" enctype="application/x-www-form-urlencoded">http://openid.net/extensions/sreg/1.1"/>https://launchpad.net/+openid-callback?starting_url=https%3A%2F%2Fbugs.launchpad.net%2Fsubiquity%2F%2Bfilebug%2Ff55a6274-4767-11ec-a1ce-d485646cd9a4%3Ffield.title%3Dinstall%2Bfailed%2Bcrashed%2Bwith%2BCalledProcessErrorjanrain_nonce=2021-11-17T05%3A34%3A05Zo24b46"/>https://launchpad.net/"/>http://specs.openid.net/auth/2.0/identifier_select"/>http://specs.openid.net/auth/2.0"/>http://specs.openid.net/auth/2.0/identifier_select"/> var elements = document.forms[0].elements; for (var i = 0; i < elements.length; i++) { elements[i].style.display = "none"; } --- this is detail that belongs in `firefox` and not `gedit` ... ie. bug. This issue is NOT new. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu73 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportLog: ERROR: apport (pid 2820) Wed Nov 17 16:33:33 2021: called for pid 2593, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 2820) Wed Nov 17 16:33:33 2021: executable: /snap/ubuntu-desktop-installer/171/bin/ubuntu_desktop_installer (command line "/snap/ubuntu-desktop-installer/171/bin/ubuntu_desktop_installer") ERROR: apport (pid 2820) Wed Nov 17 16:33:33 2021: executable does not belong to a package, ignoring ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465+canary3.3 CrashReports: 644:0:0:30:2021-11-17 16:33:08.496906043 +1100:2021-11-17 16:33:08.496906043 +1100:/var/crash/1637127188.494807005.install_fail.meta 640:0:0:726809:2021-11-17 16:33:41.277731657 +1100:2021-11-17 16:33:42.277731657 +1100:/var/crash/1637127188.494807005.install_fail.crash 644:0:0:0:2021-11-17 16:33:45.953817607 +1100:2021-11-17 16:33:45.953817607 +1100:/var/crash/1637127188.494807005.install_fail.upload 600:116:123:5:2021-11-17 16:48:24.898416884 +1100:2021-11-17 16:33:45.953817607 +1100:/var/crash/1637127188.494807005.install_fail.uploaded CurrentDesktop: ubuntu:GNOME Date: Wed Nov 17 16:52:32 2021 LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2026) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1951214/+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 1698083] Re: Maximize vertically/horizontally doesn't work (in some apps)
Since this bug was logged 5 years ago, and is still present... in fact it is now on a shortlist of 2 bugs that will stop my adoption of Wayland, I thought I would confirm that it is still present in Ubuntu 22.04 (development branch), at the time of writing, with Gnome 41.1. -- 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/1698083 Title: Maximize vertically/horizontally doesn't work (in some apps) Status in GTK+: Unknown Status in gtk+3.0 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Triaged Bug description: Upstream: https://gitlab.gnome.org/GNOME/gtk/issues/539 In Gnome Tweak Tool you can configure vertical maximizing for: Windows > Titlebar Actions > Middle-Click However this feature seems to get ignored in Wayland sessions (it just maximizes fully instead). It only works correctly in Xorg Gnome sessions. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu6 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Thu Jun 15 14:46:04 2017 DisplayManager: lightdm InstallationDate: Installed on 2017-05-03 (43 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1698083/+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 1951214] Re: ubuntu-bug isn't opening firefox (snap) on jammy, instead gedit gets data
One equivalent cmd to show the issue $ sudo -H -u ubuntu --preserve-env=DBUS_SESSION_BUS_ADDRESS gio open https://www.ubuntu.com adding XDG_DATA_DIRS leads to the right behaviour -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1951214 Title: ubuntu-bug isn't opening firefox (snap) on jammy, instead gedit gets data Status in apport package in Ubuntu: Confirmed Bug description: This has been reported before on Ubuntu Community Hub, but I want/need a bug report filed on launchpad to report/track on iso.qa.ubuntu.com On a `ubuntu-bug` or apport opening up a bug report; a gedit window opens with --- OpenID transaction in progress https://login.launchpad.net/+openid; method="post" accept-charset="UTF-8" enctype="application/x-www-form-urlencoded">http://openid.net/extensions/sreg/1.1"/>https://launchpad.net/+openid-callback?starting_url=https%3A%2F%2Fbugs.launchpad.net%2Fsubiquity%2F%2Bfilebug%2Ff55a6274-4767-11ec-a1ce-d485646cd9a4%3Ffield.title%3Dinstall%2Bfailed%2Bcrashed%2Bwith%2BCalledProcessErrorjanrain_nonce=2021-11-17T05%3A34%3A05Zo24b46"/>https://launchpad.net/"/>http://specs.openid.net/auth/2.0/identifier_select"/>http://specs.openid.net/auth/2.0"/>http://specs.openid.net/auth/2.0/identifier_select"/> var elements = document.forms[0].elements; for (var i = 0; i < elements.length; i++) { elements[i].style.display = "none"; } --- this is detail that belongs in `firefox` and not `gedit` ... ie. bug. This issue is NOT new. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu73 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportLog: ERROR: apport (pid 2820) Wed Nov 17 16:33:33 2021: called for pid 2593, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 2820) Wed Nov 17 16:33:33 2021: executable: /snap/ubuntu-desktop-installer/171/bin/ubuntu_desktop_installer (command line "/snap/ubuntu-desktop-installer/171/bin/ubuntu_desktop_installer") ERROR: apport (pid 2820) Wed Nov 17 16:33:33 2021: executable does not belong to a package, ignoring ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465+canary3.3 CrashReports: 644:0:0:30:2021-11-17 16:33:08.496906043 +1100:2021-11-17 16:33:08.496906043 +1100:/var/crash/1637127188.494807005.install_fail.meta 640:0:0:726809:2021-11-17 16:33:41.277731657 +1100:2021-11-17 16:33:42.277731657 +1100:/var/crash/1637127188.494807005.install_fail.crash 644:0:0:0:2021-11-17 16:33:45.953817607 +1100:2021-11-17 16:33:45.953817607 +1100:/var/crash/1637127188.494807005.install_fail.upload 600:116:123:5:2021-11-17 16:48:24.898416884 +1100:2021-11-17 16:33:45.953817607 +1100:/var/crash/1637127188.494807005.install_fail.uploaded CurrentDesktop: ubuntu:GNOME Date: Wed Nov 17 16:52:32 2021 LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2026) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1951214/+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 1952242] [NEW] [jammy] missing rules for samba profile
Public bug reported: ubuntu jammy apparmor-profiles 3.0.3-0ubuntu3 samba 2:4.13.5+dfsg-2ubuntu3 smbd: Nov 25 14:59:56 jammy-samba-apparmor systemd[1]: Starting Samba SMB Daemon... Nov 25 14:59:56 jammy-samba-apparmor kernel: [ 227.586080] audit: type=1400 audit(1637852396.969:77): apparmor="ALLOWED" operation="capable" profile="smbd" pid=1094 comm="smbd" capability=12 capname="net_admin" Nov 25 14:59:56 jammy-samba-apparmor kernel: [ 227.586241] audit: type=1400 audit(1637852396.969:78): apparmor="ALLOWED" operation="sendmsg" profile="smbd" name="/run/systemd/notify" pid=1094 comm="smbd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 Nov 25 14:59:56 jammy-samba-apparmor kernel: [ 227.592258] audit: type=1400 audit(1637852396.977:79): apparmor="ALLOWED" operation="open" profile="smbd" name="/proc/sys/kernel/osrelease" pid=1094 comm="smbd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Nov 25 14:59:56 jammy-samba-apparmor kernel: [ 227.592460] audit: type=1400 audit(1637852396.977:80): apparmor="ALLOWED" operation="open" profile="smbd" name="/proc/1/environ" pid=1094 comm="smbd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Nov 25 14:59:56 jammy-samba-apparmor kernel: [ 227.592532] audit: type=1400 audit(1637852396.977:81): apparmor="ALLOWED" operation="ptrace" profile="smbd" pid=1094 comm="smbd" requested_mask="read" denied_mask="read" peer="unconfined" Nov 25 14:59:56 jammy-samba-apparmor kernel: [ 227.592683] audit: type=1400 audit(1637852396.977:82): apparmor="ALLOWED" operation="open" profile="smbd" name="/proc/cmdline" pid=1094 comm="smbd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Nov 25 14:59:56 jammy-samba-apparmor kernel: [ 227.600378] audit: type=1400 audit(1637852396.985:83): apparmor="ALLOWED" operation="sendmsg" profile="smbd" name="/run/systemd/notify" pid=1094 comm="smbd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 nmbd: Nov 25 14:59:26 jammy-samba-apparmor systemd[1]: Starting Samba NMB Daemon... Nov 25 14:59:26 jammy-samba-apparmor kernel: [ 196.718721] audit: type=1400 audit(1637852366.105:76): apparmor="ALLOWED" operation="capable" profile="nmbd" pid=1067 comm="nmbd" capability=1 2 capname="net_admin" The systemd notify one for smbd was first fixed for nmbd in https://gitlab.com/apparmor/apparmor/-/merge_requests/236 for nmbd, but smbd was missed. net_admin might be https://github.com/systemd/systemd/pull/10085, I didn't check if jammy's systemd has that patch (it should, since it's old) ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1952242 Title: [jammy] missing rules for samba profile Status in apparmor package in Ubuntu: New Bug description: ubuntu jammy apparmor-profiles 3.0.3-0ubuntu3 samba 2:4.13.5+dfsg-2ubuntu3 smbd: Nov 25 14:59:56 jammy-samba-apparmor systemd[1]: Starting Samba SMB Daemon... Nov 25 14:59:56 jammy-samba-apparmor kernel: [ 227.586080] audit: type=1400 audit(1637852396.969:77): apparmor="ALLOWED" operation="capable" profile="smbd" pid=1094 comm="smbd" capability=12 capname="net_admin" Nov 25 14:59:56 jammy-samba-apparmor kernel: [ 227.586241] audit: type=1400 audit(1637852396.969:78): apparmor="ALLOWED" operation="sendmsg" profile="smbd" name="/run/systemd/notify" pid=1094 comm="smbd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 Nov 25 14:59:56 jammy-samba-apparmor kernel: [ 227.592258] audit: type=1400 audit(1637852396.977:79): apparmor="ALLOWED" operation="open" profile="smbd" name="/proc/sys/kernel/osrelease" pid=1094 comm="smbd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Nov 25 14:59:56 jammy-samba-apparmor kernel: [ 227.592460] audit: type=1400 audit(1637852396.977:80): apparmor="ALLOWED" operation="open" profile="smbd" name="/proc/1/environ" pid=1094 comm="smbd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Nov 25 14:59:56 jammy-samba-apparmor kernel: [ 227.592532] audit: type=1400 audit(1637852396.977:81): apparmor="ALLOWED" operation="ptrace" profile="smbd" pid=1094 comm="smbd" requested_mask="read" denied_mask="read" peer="unconfined" Nov 25 14:59:56 jammy-samba-apparmor kernel: [ 227.592683] audit: type=1400 audit(1637852396.977:82): apparmor="ALLOWED" operation="open" profile="smbd" name="/proc/cmdline" pid=1094 comm="smbd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Nov 25 14:59:56 jammy-samba-apparmor kernel: [ 227.600378] audit: type=1400 audit(1637852396.985:83): apparmor="ALLOWED" operation="sendmsg" profile="smbd" name="/run/systemd/notify" pid=1094 comm="smbd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 nmbd: Nov 25 14:59:26
[Touch-packages] [Bug 1951943] Re: Engine crashes when loading the configuration more than once
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: openssl (Ubuntu Bionic) Status: New => Confirmed -- 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/1951943 Title: Engine crashes when loading the configuration more than once Status in openssl package in Ubuntu: Confirmed Status in openssl source package in Bionic: Confirmed Status in openssl source package in Focal: In Progress Status in openssl source package in Hirsute: In Progress Status in openssl source package in Impish: In Progress Status in openssl source package in Jammy: Confirmed Bug description: [Impact] * Engine crashes when loading the configuration more than once * Upstream started to avoid loading engines twice by using dynamic ids to track the loaded engines correctly * OpenSSL 3 https://github.com/openssl/openssl/commit/81c11349c2a0e945aa3dfc6bd81c957363dd2011 (bugfix) https://github.com/openssl/openssl/commit/38e2957249c90317a26a080c7e7eb186dd5b6598 (test case) * OpenSSL 1.1.1 backports: https://github.com/openssl/openssl/commit/9b06ebb1edfddffea083ba36090af7eb7cad207b (bugfix) https://github.com/openssl/openssl/pull/17083 (test case) [Test Plan] * https://github.com/openssl/openssl/issues/17023 lists multiple ways how one can trigger the issue at hand, but also test case implements this issue too by explicitly attempting to load an engine multiple times and checking that it is operational. The test a is run during the build as part of the upstream regression test suite, for the shared library build (as static build does not support engines), so you'll see one pass and one skip in the log. [Where problems could occur] * Separately we have started to fix userspace packages that needlessly load configuration files multiple times, which used to trigger this issue. The codepaths changed are with engine use, how they are loaded/unloaded/used. It is possible that this fix will make some engines to start working and be used resulting in new behaviour. But also exposing bugs in the engines that previously were installed & configured but not actually used. [Other Info] * Previous bug reports about this issues are: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1921518 https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1940528 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1951943/+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 1951943] Re: Engine crashes when loading the configuration more than once
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: openssl (Ubuntu) Status: New => Confirmed -- 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/1951943 Title: Engine crashes when loading the configuration more than once Status in openssl package in Ubuntu: Confirmed Status in openssl source package in Bionic: Confirmed Status in openssl source package in Focal: In Progress Status in openssl source package in Hirsute: In Progress Status in openssl source package in Impish: In Progress Status in openssl source package in Jammy: Confirmed Bug description: [Impact] * Engine crashes when loading the configuration more than once * Upstream started to avoid loading engines twice by using dynamic ids to track the loaded engines correctly * OpenSSL 3 https://github.com/openssl/openssl/commit/81c11349c2a0e945aa3dfc6bd81c957363dd2011 (bugfix) https://github.com/openssl/openssl/commit/38e2957249c90317a26a080c7e7eb186dd5b6598 (test case) * OpenSSL 1.1.1 backports: https://github.com/openssl/openssl/commit/9b06ebb1edfddffea083ba36090af7eb7cad207b (bugfix) https://github.com/openssl/openssl/pull/17083 (test case) [Test Plan] * https://github.com/openssl/openssl/issues/17023 lists multiple ways how one can trigger the issue at hand, but also test case implements this issue too by explicitly attempting to load an engine multiple times and checking that it is operational. The test a is run during the build as part of the upstream regression test suite, for the shared library build (as static build does not support engines), so you'll see one pass and one skip in the log. [Where problems could occur] * Separately we have started to fix userspace packages that needlessly load configuration files multiple times, which used to trigger this issue. The codepaths changed are with engine use, how they are loaded/unloaded/used. It is possible that this fix will make some engines to start working and be used resulting in new behaviour. But also exposing bugs in the engines that previously were installed & configured but not actually used. [Other Info] * Previous bug reports about this issues are: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1921518 https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1940528 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1951943/+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 1639452] Re: systemd ExecStartPre test config
** Changed in: dnsmasq (Ubuntu) Assignee: Miriam España Acebal (mirespace) => (unassigned) ** Changed in: dnsmasq (Ubuntu Bionic) Assignee: Miriam España Acebal (mirespace) => (unassigned) ** Changed in: dnsmasq (Ubuntu Focal) Assignee: Miriam España Acebal (mirespace) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1639452 Title: systemd ExecStartPre test config Status in dnsmasq package in Ubuntu: Fix Released Status in dnsmasq source package in Bionic: Opinion Status in dnsmasq source package in Focal: Opinion Bug description: The standard configuration file of dnsmasq is complete commented out. The real configuration is saved in /etc/dnsmasq.d, so the test of systemd is a fake. In the Service Section of /lib/systemd/system/dnsmasq.service the ExecStartPre directive should be set to "/usr/sbin/dnsmasq --conf- dir=/etc/dnsmasq.d --test" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639452/+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 1686183] Re: Ship ubuntu-advantage in ubuntu-minimal
Bug 1950692 and this mailing list thread https://lists.ubuntu.com/archives/ubuntu-devel/2021-November/041688.html are follow ups from comments 42 and 44 requesting that the ubuntu- advantage-tools package be removable. If you want this, please participate in the discussion - otherwise it's unlikely to happen. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1686183 Title: Ship ubuntu-advantage in ubuntu-minimal Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Precise: Fix Released Status in ubuntu-meta source package in Precise: Fix Released Status in ubuntu-advantage-tools source package in Trusty: Fix Released Status in ubuntu-meta source package in Trusty: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-meta source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Yakkety: Won't Fix Status in ubuntu-meta source package in Yakkety: Won't Fix Status in ubuntu-advantage-tools source package in Zesty: Fix Released Status in ubuntu-meta source package in Zesty: Won't Fix Status in ubuntu-advantage-tools source package in Artful: Fix Released Status in ubuntu-meta source package in Artful: Fix Released Bug description: The ubuntu-advantage-tools package is a bit odd as it was first landed in precise to support the ESM effort inside canonical. [0] In order to bring this package up to date across other series in ubuntu, it has been recommended by the Ubuntu Foundations team to land into trusty next, then forward-port pocket-copy to all supported series until we get to the devel release. The version here: https://github.com/CanonicalLtd/ubuntu-advantage- script/releases/tag/v2 ... has all on-disk bits correctly working, for all series, but no-ops on any release other than precise (ESM is only for "unsupported" LTS releases as it were). This is a request to land ubuntu-advantage- tools into trusty, then pocket-copy it to supported series of ubuntu once that is finished. [Impact] * Allow ubuntu-advantage users to access the extended security maintenance script with a simple command line tool. This script needs to hit precise machines and be easy for ubuntu-advantage customers to enable, thus basefiles was chosen as a home. [Test Case] * Run ubuntu-advantage, it should print out help * Run sudo ubuntu-advantage enable (without sudo it will warn you), but you need to be an ubuntu-advantage customer to get that token. In the end, the script simply adds and removes an /etc/apt/sources.list.d entry. * Verify that the MOTD does not contain any mention of ubuntu- advantage esm or precise and its end of life * Verify that ubuntu-advantage enable-esm installs needed dependencies: - create the following file and its contents to have apt not install recommended packages by default: $ cat /etc/apt/apt.conf.d/no-recommends APT::Install-Recommends "false"; - remove ca-certificates and apt-transport-https: $ sudo apt remove ca-certificates apt-transport-https - run sudo ubuntu-advantage enable-esm and verify that the two removed packages are reinstalled * you can contact me (d...@canonical.com) if you would like a token for test purposes. [Regression Potential] * Low, this is a new script, not included in any automated startup paths. [Other Info] * http://blog.dustinkirkland.com/2017/03/ubuntu-1204-esm.html [0] https://insights.ubuntu.com/2017/03/14/introducing- ubuntu-12-04-esm-extended-security-maintenance/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1686183/+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 1951214] Re: ubuntu-bug isn't opening firefox (snap) on jammy, instead gedit gets data
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1951214 Title: ubuntu-bug isn't opening firefox (snap) on jammy, instead gedit gets data Status in apport package in Ubuntu: Confirmed Bug description: This has been reported before on Ubuntu Community Hub, but I want/need a bug report filed on launchpad to report/track on iso.qa.ubuntu.com On a `ubuntu-bug` or apport opening up a bug report; a gedit window opens with --- OpenID transaction in progress https://login.launchpad.net/+openid; method="post" accept-charset="UTF-8" enctype="application/x-www-form-urlencoded">http://openid.net/extensions/sreg/1.1"/>https://launchpad.net/+openid-callback?starting_url=https%3A%2F%2Fbugs.launchpad.net%2Fsubiquity%2F%2Bfilebug%2Ff55a6274-4767-11ec-a1ce-d485646cd9a4%3Ffield.title%3Dinstall%2Bfailed%2Bcrashed%2Bwith%2BCalledProcessErrorjanrain_nonce=2021-11-17T05%3A34%3A05Zo24b46"/>https://launchpad.net/"/>http://specs.openid.net/auth/2.0/identifier_select"/>http://specs.openid.net/auth/2.0"/>http://specs.openid.net/auth/2.0/identifier_select"/> var elements = document.forms[0].elements; for (var i = 0; i < elements.length; i++) { elements[i].style.display = "none"; } --- this is detail that belongs in `firefox` and not `gedit` ... ie. bug. This issue is NOT new. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu73 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportLog: ERROR: apport (pid 2820) Wed Nov 17 16:33:33 2021: called for pid 2593, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 2820) Wed Nov 17 16:33:33 2021: executable: /snap/ubuntu-desktop-installer/171/bin/ubuntu_desktop_installer (command line "/snap/ubuntu-desktop-installer/171/bin/ubuntu_desktop_installer") ERROR: apport (pid 2820) Wed Nov 17 16:33:33 2021: executable does not belong to a package, ignoring ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465+canary3.3 CrashReports: 644:0:0:30:2021-11-17 16:33:08.496906043 +1100:2021-11-17 16:33:08.496906043 +1100:/var/crash/1637127188.494807005.install_fail.meta 640:0:0:726809:2021-11-17 16:33:41.277731657 +1100:2021-11-17 16:33:42.277731657 +1100:/var/crash/1637127188.494807005.install_fail.crash 644:0:0:0:2021-11-17 16:33:45.953817607 +1100:2021-11-17 16:33:45.953817607 +1100:/var/crash/1637127188.494807005.install_fail.upload 600:116:123:5:2021-11-17 16:48:24.898416884 +1100:2021-11-17 16:33:45.953817607 +1100:/var/crash/1637127188.494807005.install_fail.uploaded CurrentDesktop: ubuntu:GNOME Date: Wed Nov 17 16:52:32 2021 LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2026) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1951214/+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 1951470] Re: webkit javascript segmentation fault
Thanks to Dmitry Shachnev, who picked the endianness patch for Debian, and a new and fixed version got was now synched over to Ubuntu jammy: 5.212.0~alpha4-14 qtwebkit-opensource-src (5.212.0~alpha4-14) unstable; urgency=medium * debian/patches/jscore_big_endian.diff: Fix segmentation fault on s390x and potentially other 64-bit big endian systems (LP: #1951470). Thanks Andreas Krebbel for the patch and Frank Heimes for the initial debdiff! * Update debian/source/lintian-overrides for Lintian 2.109. -- Dmitry Shachnev Wed, 24 Nov 2021 22:27:08 +0300 It's currently in jammy proposed: qtwebkit-opensource-src | 5.212.0~alpha4-13 | jammy/universe | source qtwebkit-opensource-src | 5.212.0~alpha4-14 | jammy-proposed/universe | source With that I delete my MP for jammy (since it's no longer needed) and set the affected jammy entry to Fix Committed. ** Tags removed: jammy ** Tags added: hirsute ** Changed in: qtwebkit-opensource-src (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtwebkit-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1951470 Title: webkit javascript segmentation fault Status in Ubuntu on IBM z Systems: In Progress Status in qtwebkit-opensource-src package in Ubuntu: Fix Committed Status in qtwebkit-opensource-src source package in Focal: New Status in qtwebkit-opensource-src source package in Hirsute: In Progress Status in qtwebkit-opensource-src source package in Impish: In Progress Status in qtwebkit-opensource-src source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] * WebKit Javascript engine is causing a segmentation fault on big endian (s390x) systems. * This happens for example when transferring an html to a pdf file using wkhtmltopdf. * The fix is relatively simple with changing loadisFromInstruction to loadpFromInstruction in macro getProperty(slow), which solves this unpleasant situation. * The JIT ocde is 32bit (even on 64bit systems), hence is crucial to make sure the lower part of a 64bit value is taken on big endian systems. [Test Plan] * Testing is very straight forward by following these steps: * install the following packages (incl. their dependencies): $ sudo apt install libqt5webkit5 wkhtmltopdf * create an html file like this: $ vi index.html $ cat index.html * create a JavaScript file like this: $ vi min.js $ cat min.js var i = Math.max * call wkhtmltopdf to process the local files: $ wkhtmltopdf --enable-local-file-access index.html test.pdf * if it's broken one gets this output: Loading page (1/2) Segmentation fault (core dumped) ] 50% and no pdf file was generated: $ ls *.pdf ls: cannot access '*.pdf': No such file or directory * in case it's fixed one gets this output: Loading page (1/2) Printing pages (2/2) Done and a pdf file was generated and in placed in the current directory (with more than 0 bytes size): $ ls -l ./*.pdf -rw-rw-r-- 1 ubuntu ubuntu 1339 Nov 24 11:48 ./test.pdf [Where problems could occur] * While this issue only affects big endian systems (like s390x), a bad fix may have an impact on little endian systems, too for example in case the wrong function got used in the macro. * But loadpFromInstruction is known to work for LE and BE systems; * and on top cross-architecture builds were done: https://launchpad.net/~fheimes/+archive/ubuntu/lp1951470 * and tested on s390x (if the fix works) and on non-s390x (regression testing). * The changes are otherwise very limited, just: macro getProperty(slow) -loadisFromInstruction(6, t1) +loadpFromInstruction(6, t1) hence I think there is not much more to say. [Other Info] * The maintainer of the Debian packages (Dmitry Shachnev) is going to add this to the Debian package, too. * This issue affects Ubuntu jammy, impish, hirsute and focal - SRUs are ongoing. * The issue does not occur with the very latest upstream version anymore, and was fixed in a similar way as part of a commit that fixes numerous other CLoop issues on top: "Fix all CLoop JSC test failures (including some LLInt bugs due to recent bytecode format change)." commit 3fdde71c7d95d758a61fcbc4c58168616794c102 __ == Comment: #0 - Andreas Krebbel - 2021-11-15 09:29:44 == ---Problem Description--- Segmentation fault from WebKit Javascript engine Contact Information = andreas.kreb...@de.ibm.com ---uname output--- Linux
[Touch-packages] [Bug 1639452] Re: systemd ExecStartPre test config
** Changed in: dnsmasq (Ubuntu) Importance: Undecided => Wishlist ** Changed in: dnsmasq (Ubuntu Bionic) Importance: Low => Wishlist ** Changed in: dnsmasq (Ubuntu Focal) Importance: Medium => Wishlist ** Tags removed: server-todo ** Changed in: dnsmasq (Ubuntu) Status: Opinion => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1639452 Title: systemd ExecStartPre test config Status in dnsmasq package in Ubuntu: Fix Released Status in dnsmasq source package in Bionic: Opinion Status in dnsmasq source package in Focal: Opinion Bug description: The standard configuration file of dnsmasq is complete commented out. The real configuration is saved in /etc/dnsmasq.d, so the test of systemd is a fake. In the Service Section of /lib/systemd/system/dnsmasq.service the ExecStartPre directive should be set to "/usr/sbin/dnsmasq --conf- dir=/etc/dnsmasq.d --test" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639452/+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 1639452] Re: systemd ExecStartPre test config
** Changed in: dnsmasq (Ubuntu) Assignee: (unassigned) => Miriam España Acebal (mirespace) ** Changed in: dnsmasq (Ubuntu Bionic) Status: Triaged => Opinion ** Changed in: dnsmasq (Ubuntu Focal) Status: Triaged => Opinion ** Changed in: dnsmasq (Ubuntu) Status: Fix Released => Opinion -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1639452 Title: systemd ExecStartPre test config Status in dnsmasq package in Ubuntu: Fix Released Status in dnsmasq source package in Bionic: Opinion Status in dnsmasq source package in Focal: Opinion Bug description: The standard configuration file of dnsmasq is complete commented out. The real configuration is saved in /etc/dnsmasq.d, so the test of systemd is a fake. In the Service Section of /lib/systemd/system/dnsmasq.service the ExecStartPre directive should be set to "/usr/sbin/dnsmasq --conf- dir=/etc/dnsmasq.d --test" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639452/+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 1951214] Re: ubuntu-bug isn't opening firefox (snap) on jammy, instead gedit gets data
confirmed now on a canary image that the fix works as expected -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1951214 Title: ubuntu-bug isn't opening firefox (snap) on jammy, instead gedit gets data Status in apport package in Ubuntu: Confirmed Bug description: This has been reported before on Ubuntu Community Hub, but I want/need a bug report filed on launchpad to report/track on iso.qa.ubuntu.com On a `ubuntu-bug` or apport opening up a bug report; a gedit window opens with --- OpenID transaction in progress https://login.launchpad.net/+openid; method="post" accept-charset="UTF-8" enctype="application/x-www-form-urlencoded">http://openid.net/extensions/sreg/1.1"/>https://launchpad.net/+openid-callback?starting_url=https%3A%2F%2Fbugs.launchpad.net%2Fsubiquity%2F%2Bfilebug%2Ff55a6274-4767-11ec-a1ce-d485646cd9a4%3Ffield.title%3Dinstall%2Bfailed%2Bcrashed%2Bwith%2BCalledProcessErrorjanrain_nonce=2021-11-17T05%3A34%3A05Zo24b46"/>https://launchpad.net/"/>http://specs.openid.net/auth/2.0/identifier_select"/>http://specs.openid.net/auth/2.0"/>http://specs.openid.net/auth/2.0/identifier_select"/> var elements = document.forms[0].elements; for (var i = 0; i < elements.length; i++) { elements[i].style.display = "none"; } --- this is detail that belongs in `firefox` and not `gedit` ... ie. bug. This issue is NOT new. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu73 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportLog: ERROR: apport (pid 2820) Wed Nov 17 16:33:33 2021: called for pid 2593, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 2820) Wed Nov 17 16:33:33 2021: executable: /snap/ubuntu-desktop-installer/171/bin/ubuntu_desktop_installer (command line "/snap/ubuntu-desktop-installer/171/bin/ubuntu_desktop_installer") ERROR: apport (pid 2820) Wed Nov 17 16:33:33 2021: executable does not belong to a package, ignoring ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465+canary3.3 CrashReports: 644:0:0:30:2021-11-17 16:33:08.496906043 +1100:2021-11-17 16:33:08.496906043 +1100:/var/crash/1637127188.494807005.install_fail.meta 640:0:0:726809:2021-11-17 16:33:41.277731657 +1100:2021-11-17 16:33:42.277731657 +1100:/var/crash/1637127188.494807005.install_fail.crash 644:0:0:0:2021-11-17 16:33:45.953817607 +1100:2021-11-17 16:33:45.953817607 +1100:/var/crash/1637127188.494807005.install_fail.upload 600:116:123:5:2021-11-17 16:48:24.898416884 +1100:2021-11-17 16:33:45.953817607 +1100:/var/crash/1637127188.494807005.install_fail.uploaded CurrentDesktop: ubuntu:GNOME Date: Wed Nov 17 16:52:32 2021 LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2026) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1951214/+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 1951779] Re: tempfile command removed from debianutils
We all wanted to have a look, this is what I found: boost/boost1.74-1.74.0/tools/quickbook/build/warning-check:5:tmpfile=$(tempfile) That is in jammy's current 1.74.0-13ubuntu1 but only referenced for travis runs (of the doc build). Worth a task to check in detail, but unlikely to need a fix. ceph/ceph/src/boost/tools/quickbook/build/warning-check:5:tmpfile=$(tempfile) ^^ That is the same as above as embedded source, worth a check if it is used indirectly anywhere (unlikely). get-docker-images/ubuntu-layer/bin/bzexe:123:tmpfile=`tempfile -p gztmp -d /tmp` || exit 1 I found it here but it is actually part of src:bzip2 Fixed by https://salsa.debian.org/debian/bzip2/-/commit/aff0bec9ea82646baf6d9d824022bc6f3cf46514 This is not yet uploaded to Debian and therefore missing in Jammy as well ** Also affects: boost1.74 (Ubuntu) Importance: Undecided Status: New ** Also affects: ceph (Ubuntu) Importance: Undecided Status: New ** Also affects: bzip2 (Ubuntu) Importance: Undecided Status: New ** Changed in: bzip2 (Ubuntu) Importance: Undecided => Medium ** Changed in: ceph (Ubuntu) Importance: Undecided => Wishlist ** Changed in: boost1.74 (Ubuntu) Importance: Undecided => Wishlist ** Changed in: grub-legacy-ec2 (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bzip2 in Ubuntu. https://bugs.launchpad.net/bugs/1951779 Title: tempfile command removed from debianutils Status in boost1.74 package in Ubuntu: New Status in bzip2 package in Ubuntu: New Status in ceph package in Ubuntu: New Status in grub-legacy-ec2 package in Ubuntu: Triaged Bug description: Error when do-release-upgrade -d from 20.04.3 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.13.0-19-generic 5.13.0-19.19 ProcVersionSignature: Ubuntu 5.4.0-90.101-generic 5.4.148 Uname: Linux 5.4.0-90-generic x86_64 ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown Date: Mon Nov 22 13:31:36 2021 ErrorMessage: run-parts: /etc/kernel/postinst.d/x-grub-legacy-ec2 exited with return code 127 InstallationDate: Installed on 2018-10-01 (1147 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 8087:07e6 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/8p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M MachineType: PAIQ EC3-BT19D4L ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-90-generic root=UUID=4c36d2b3-c1dd-469f-bfbf-5b7052d669d4 ro ipv6.disable=1 quiet reboot=pci ipv6.disable=1 Python3Details: Error: command ['readlink', '-f', "/usr/bin/which: this version of `which' is deprecated; use `command -v' in scripts instead.\n/usr/bin/python3"] failed with exit code 1: , Error: [Errno 2] No such file or directory: 'Error: command [\'readlink\', \'-f\', "/usr/bin/which: this version of `which\' is deprecated; use `command -v\' in scripts instead.\\n/usr/bin/python3"] failed with exit code 1: ', python3-minimal, 3.9.4-1build1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.04-1ubuntu48 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: grub-legacy-ec2 Title: package linux-image-5.13.0-19-generic 5.13.0-19.19 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/x-grub-legacy-ec2 exited with return code 127 UpgradeStatus: Upgraded to jammy on 2021-11-22 (0 days ago) dmi.bios.date: 02/28/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: EC3-BT19D4L dmi.board.vendor: PAIQ dmi.board.version: A1 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd02/28/2017:svnPAIQ:pnEC3-BT19D4L:pvrBIOSNameBT190003BIOSVersionA1BuildDate:rvnPAIQ:rnEC3-BT19D4L:rvrA1:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: EC3-BT19D4L dmi.product.sku: 18:19:28 dmi.product.version: BIOS Name:BT190003 BIOS Version:A1 Build Date: dmi.sys.vendor: PAIQ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boost1.74/+bug/1951779/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1951470] Re: webkit javascript segmentation fault
qtwebkit debdiff (hirsute) ** Patch added: "qtwebkit debdiff (hirsute)" https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/1951470/+attachment/5543299/+files/debdiff-qtwebkit-lp1951470-hirsute.patch ** Changed in: qtwebkit-opensource-src (Ubuntu Hirsute) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtwebkit-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1951470 Title: webkit javascript segmentation fault Status in Ubuntu on IBM z Systems: In Progress Status in qtwebkit-opensource-src package in Ubuntu: In Progress Status in qtwebkit-opensource-src source package in Focal: New Status in qtwebkit-opensource-src source package in Hirsute: In Progress Status in qtwebkit-opensource-src source package in Impish: In Progress Status in qtwebkit-opensource-src source package in Jammy: In Progress Bug description: SRU Justification: [Impact] * WebKit Javascript engine is causing a segmentation fault on big endian (s390x) systems. * This happens for example when transferring an html to a pdf file using wkhtmltopdf. * The fix is relatively simple with changing loadisFromInstruction to loadpFromInstruction in macro getProperty(slow), which solves this unpleasant situation. * The JIT ocde is 32bit (even on 64bit systems), hence is crucial to make sure the lower part of a 64bit value is taken on big endian systems. [Test Plan] * Testing is very straight forward by following these steps: * install the following packages (incl. their dependencies): $ sudo apt install libqt5webkit5 wkhtmltopdf * create an html file like this: $ vi index.html $ cat index.html * create a JavaScript file like this: $ vi min.js $ cat min.js var i = Math.max * call wkhtmltopdf to process the local files: $ wkhtmltopdf --enable-local-file-access index.html test.pdf * if it's broken one gets this output: Loading page (1/2) Segmentation fault (core dumped) ] 50% and no pdf file was generated: $ ls *.pdf ls: cannot access '*.pdf': No such file or directory * in case it's fixed one gets this output: Loading page (1/2) Printing pages (2/2) Done and a pdf file was generated and in placed in the current directory (with more than 0 bytes size): $ ls -l ./*.pdf -rw-rw-r-- 1 ubuntu ubuntu 1339 Nov 24 11:48 ./test.pdf [Where problems could occur] * While this issue only affects big endian systems (like s390x), a bad fix may have an impact on little endian systems, too for example in case the wrong function got used in the macro. * But loadpFromInstruction is known to work for LE and BE systems; * and on top cross-architecture builds were done: https://launchpad.net/~fheimes/+archive/ubuntu/lp1951470 * and tested on s390x (if the fix works) and on non-s390x (regression testing). * The changes are otherwise very limited, just: macro getProperty(slow) -loadisFromInstruction(6, t1) +loadpFromInstruction(6, t1) hence I think there is not much more to say. [Other Info] * The maintainer of the Debian packages (Dmitry Shachnev) is going to add this to the Debian package, too. * This issue affects Ubuntu jammy, impish, hirsute and focal - SRUs are ongoing. * The issue does not occur with the very latest upstream version anymore, and was fixed in a similar way as part of a commit that fixes numerous other CLoop issues on top: "Fix all CLoop JSC test failures (including some LLInt bugs due to recent bytecode format change)." commit 3fdde71c7d95d758a61fcbc4c58168616794c102 __ == Comment: #0 - Andreas Krebbel - 2021-11-15 09:29:44 == ---Problem Description--- Segmentation fault from WebKit Javascript engine Contact Information = andreas.kreb...@de.ibm.com ---uname output--- Linux 193438490afd 5.8.15-301.fc33.s390x #1 SMP Thu Oct 15 15:55:57 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = IBM Z ---Debugger--- A debugger is not configured ---Steps to Reproduce--- index.html: min.js: var i = Math.max wkhtmltopdf index.html test.pdf QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' Loading page (1/2) Segmentation fault (core dumped) ] 17% Userspace tool common name: wkhtmltopdf The userspace tool has the following bit modes: 64 Userspace rpm: libqt5webkit5 Userspace tool obtained from project website: na *Additional Instructions for andreas.kreb...@de.ibm.com: -Attach ltrace and
[Touch-packages] [Bug 1951470] Re: webkit javascript segmentation fault
** Merge proposal linked: https://code.launchpad.net/~fheimes/ubuntu/+source/qtwebkit-opensource-src/+git/qtwebkit-opensource-src/+merge/412383 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtwebkit-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1951470 Title: webkit javascript segmentation fault Status in Ubuntu on IBM z Systems: In Progress Status in qtwebkit-opensource-src package in Ubuntu: In Progress Status in qtwebkit-opensource-src source package in Focal: New Status in qtwebkit-opensource-src source package in Hirsute: New Status in qtwebkit-opensource-src source package in Impish: In Progress Status in qtwebkit-opensource-src source package in Jammy: In Progress Bug description: SRU Justification: [Impact] * WebKit Javascript engine is causing a segmentation fault on big endian (s390x) systems. * This happens for example when transferring an html to a pdf file using wkhtmltopdf. * The fix is relatively simple with changing loadisFromInstruction to loadpFromInstruction in macro getProperty(slow), which solves this unpleasant situation. * The JIT ocde is 32bit (even on 64bit systems), hence is crucial to make sure the lower part of a 64bit value is taken on big endian systems. [Test Plan] * Testing is very straight forward by following these steps: * install the following packages (incl. their dependencies): $ sudo apt install libqt5webkit5 wkhtmltopdf * create an html file like this: $ vi index.html $ cat index.html * create a JavaScript file like this: $ vi min.js $ cat min.js var i = Math.max * call wkhtmltopdf to process the local files: $ wkhtmltopdf --enable-local-file-access index.html test.pdf * if it's broken one gets this output: Loading page (1/2) Segmentation fault (core dumped) ] 50% and no pdf file was generated: $ ls *.pdf ls: cannot access '*.pdf': No such file or directory * in case it's fixed one gets this output: Loading page (1/2) Printing pages (2/2) Done and a pdf file was generated and in placed in the current directory (with more than 0 bytes size): $ ls -l ./*.pdf -rw-rw-r-- 1 ubuntu ubuntu 1339 Nov 24 11:48 ./test.pdf [Where problems could occur] * While this issue only affects big endian systems (like s390x), a bad fix may have an impact on little endian systems, too for example in case the wrong function got used in the macro. * But loadpFromInstruction is known to work for LE and BE systems; * and on top cross-architecture builds were done: https://launchpad.net/~fheimes/+archive/ubuntu/lp1951470 * and tested on s390x (if the fix works) and on non-s390x (regression testing). * The changes are otherwise very limited, just: macro getProperty(slow) -loadisFromInstruction(6, t1) +loadpFromInstruction(6, t1) hence I think there is not much more to say. [Other Info] * The maintainer of the Debian packages (Dmitry Shachnev) is going to add this to the Debian package, too. * This issue affects Ubuntu jammy, impish, hirsute and focal - SRUs are ongoing. * The issue does not occur with the very latest upstream version anymore, and was fixed in a similar way as part of a commit that fixes numerous other CLoop issues on top: "Fix all CLoop JSC test failures (including some LLInt bugs due to recent bytecode format change)." commit 3fdde71c7d95d758a61fcbc4c58168616794c102 __ == Comment: #0 - Andreas Krebbel - 2021-11-15 09:29:44 == ---Problem Description--- Segmentation fault from WebKit Javascript engine Contact Information = andreas.kreb...@de.ibm.com ---uname output--- Linux 193438490afd 5.8.15-301.fc33.s390x #1 SMP Thu Oct 15 15:55:57 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = IBM Z ---Debugger--- A debugger is not configured ---Steps to Reproduce--- index.html: min.js: var i = Math.max wkhtmltopdf index.html test.pdf QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' Loading page (1/2) Segmentation fault (core dumped) ] 17% Userspace tool common name: wkhtmltopdf The userspace tool has the following bit modes: 64 Userspace rpm: libqt5webkit5 Userspace tool obtained from project website: na *Additional Instructions for andreas.kreb...@de.ibm.com: -Attach ltrace and strace of userspace application. == Comment: #1 - Andreas Krebbel - 2021-11-15 09:44:04 == In CodeBlock.cpp the code preparing the operands of op_get_from_scope writes
[Touch-packages] [Bug 1952217] Re: bluetoothd coredumps from double free on connection of headset
bluetoothd 5.62 (installed from source @ `applied/ubuntu/devel` ) working well. ** Attachment added: "syslog.5.62.txt" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1952217/+attachment/5543298/+files/syslog.5.62.txt -- 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/1952217 Title: bluetoothd coredumps from double free on connection of headset Status in bluez package in Ubuntu: New Bug description: Problem: Since the security updates on 2021-11-23 connecting my headset causes bluetoothd to crash, which drops all the other connections. Expected: Headset connects and works as it has done previously. ❯ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 ❯ apt-cache policy bluez bluez: Installed: 5.53-0ubuntu3.4 Candidate: 5.53-0ubuntu3.4 Headset is a Sony WH-1000XM3. I have ppa:berglh/pulseaudio-a2dp installed for the LDAC codecs for this headset. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1952217/+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 1951214] Re: ubuntu-bug isn't opening firefox (snap) on jammy, instead gedit gets data
I've debugged the issue and here is what is going on * the report is a system one so ubuntu-bug is using sudo * the environment is filtered which includes XDG_DATA_DIRS * when XDG_DATA_DIRS is missing glib fallbacks to the standard path, /usr/share/applications * there is no browser installed in this directory since we install firefox as a snap and the desktop is in /var/lib/snapd/desktop/applications * gio fallbacks for some reason to use a text editor but could as well error out The attached patch should fix the issue, I didn't confirm yet though ** Changed in: apport (Ubuntu) Status: New => Confirmed ** Changed in: apport (Ubuntu) Importance: Undecided => High ** Tags added: rls-jj-incoming ** Patch added: "tentative patch to fix the issue" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1951214/+attachment/5543297/+files/apport.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1951214 Title: ubuntu-bug isn't opening firefox (snap) on jammy, instead gedit gets data Status in apport package in Ubuntu: Confirmed Bug description: This has been reported before on Ubuntu Community Hub, but I want/need a bug report filed on launchpad to report/track on iso.qa.ubuntu.com On a `ubuntu-bug` or apport opening up a bug report; a gedit window opens with --- OpenID transaction in progress https://login.launchpad.net/+openid; method="post" accept-charset="UTF-8" enctype="application/x-www-form-urlencoded">http://openid.net/extensions/sreg/1.1"/>https://launchpad.net/+openid-callback?starting_url=https%3A%2F%2Fbugs.launchpad.net%2Fsubiquity%2F%2Bfilebug%2Ff55a6274-4767-11ec-a1ce-d485646cd9a4%3Ffield.title%3Dinstall%2Bfailed%2Bcrashed%2Bwith%2BCalledProcessErrorjanrain_nonce=2021-11-17T05%3A34%3A05Zo24b46"/>https://launchpad.net/"/>http://specs.openid.net/auth/2.0/identifier_select"/>http://specs.openid.net/auth/2.0"/>http://specs.openid.net/auth/2.0/identifier_select"/> var elements = document.forms[0].elements; for (var i = 0; i < elements.length; i++) { elements[i].style.display = "none"; } --- this is detail that belongs in `firefox` and not `gedit` ... ie. bug. This issue is NOT new. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu73 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportLog: ERROR: apport (pid 2820) Wed Nov 17 16:33:33 2021: called for pid 2593, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 2820) Wed Nov 17 16:33:33 2021: executable: /snap/ubuntu-desktop-installer/171/bin/ubuntu_desktop_installer (command line "/snap/ubuntu-desktop-installer/171/bin/ubuntu_desktop_installer") ERROR: apport (pid 2820) Wed Nov 17 16:33:33 2021: executable does not belong to a package, ignoring ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465+canary3.3 CrashReports: 644:0:0:30:2021-11-17 16:33:08.496906043 +1100:2021-11-17 16:33:08.496906043 +1100:/var/crash/1637127188.494807005.install_fail.meta 640:0:0:726809:2021-11-17 16:33:41.277731657 +1100:2021-11-17 16:33:42.277731657 +1100:/var/crash/1637127188.494807005.install_fail.crash 644:0:0:0:2021-11-17 16:33:45.953817607 +1100:2021-11-17 16:33:45.953817607 +1100:/var/crash/1637127188.494807005.install_fail.upload 600:116:123:5:2021-11-17 16:48:24.898416884 +1100:2021-11-17 16:33:45.953817607 +1100:/var/crash/1637127188.494807005.install_fail.uploaded CurrentDesktop: ubuntu:GNOME Date: Wed Nov 17 16:52:32 2021 LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2026) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1951214/+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 1921518] Update Released
The verification of the Stable Release Update for wget has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/1921518 Title: OpenSSL "double free" error Status in wget package in Ubuntu: Fix Released Status in wget source package in Focal: Fix Released Bug description: [Impact] openssl config file is being loaded twice, causing engines to be loaded twice if specified therein, causing double free errors and other strange behavior. [Test plan] Run the command of the package being tested in gdb -ex "break CONF_modules_load_file" -ex "run" --args and make sure it only breaks one. Regression test: In default Ubuntu configuration, either no openssl configuration is provided, or it contains no settings that affect wget. This code path changes how/when openssl configuration is loaded and used by openssl. One should verify that: 1) wget continues to work without openssl.cnf 2) wget continues to work with stock ubuntu unmodified openssl.cnf 3) wget continue to honor and use custom TLS settings that one may have specified in openssl.cnf (for example custom engine) [Where problems could occur] wget: This is an upstream change that changes initialization and is in use in later releases. Since it mostly removes an unneeded call to the load file function, a regression could be a config file being ignored, but it seems unlikely given the use in later releases [Original bug report] "double free" error is seen when using curl utility. Error is from libcrypto.so which is part of the OpenSSL package. This happens only when OpenSSL is configured to use a dynamic engine. OpenSSL version is 1.1.1f The issue is not encountered if http://www.openssl.org/source/openssl-1.1.1f.tar.gz is used instead. OpenSSL can be configured to use a dynamic engine by editing the default openssl config file which is located at '/etc/ssl/openssl.cnf' on Ubuntu systems. On Bluefield systems, config diff to enable PKA dynamic engine, is as below: +openssl_conf = conf_section + # Extra OBJECT IDENTIFIER info: #oid_file = $ENV::HOME/.oid oid_section= new_oids +[ conf_section ] +engines = engine_section + +[ engine_section ] +bf = bf_section + +[ bf_section ] +engine_id=pka +dynamic_path=/usr/lib/aarch64-linux-gnu/engines-1.1/pka.so +init=0 + engine_id above refers to dynamic engine name/identifier. dynamic_path points to the .so file for the dynamic engine. # curl -O https://tpo.pe/pathogen.vim double free or corruption (out) Aborted (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1921518/+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 1921518] Re: OpenSSL "double free" error
This bug was fixed in the package wget - 1.20.3-1ubuntu2 --- wget (1.20.3-1ubuntu2) focal; urgency=medium * Cherry-pick upstream fix fix-ssl_init-for-openssl-1.1.1.patch: - Fix initialization of openssl for 1.1.1 (LP: #1921518) -- Julian Andres Klode Fri, 12 Nov 2021 18:09:16 +0100 ** Changed in: wget (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/1921518 Title: OpenSSL "double free" error Status in wget package in Ubuntu: Fix Released Status in wget source package in Focal: Fix Released Bug description: [Impact] openssl config file is being loaded twice, causing engines to be loaded twice if specified therein, causing double free errors and other strange behavior. [Test plan] Run the command of the package being tested in gdb -ex "break CONF_modules_load_file" -ex "run" --args and make sure it only breaks one. Regression test: In default Ubuntu configuration, either no openssl configuration is provided, or it contains no settings that affect wget. This code path changes how/when openssl configuration is loaded and used by openssl. One should verify that: 1) wget continues to work without openssl.cnf 2) wget continues to work with stock ubuntu unmodified openssl.cnf 3) wget continue to honor and use custom TLS settings that one may have specified in openssl.cnf (for example custom engine) [Where problems could occur] wget: This is an upstream change that changes initialization and is in use in later releases. Since it mostly removes an unneeded call to the load file function, a regression could be a config file being ignored, but it seems unlikely given the use in later releases [Original bug report] "double free" error is seen when using curl utility. Error is from libcrypto.so which is part of the OpenSSL package. This happens only when OpenSSL is configured to use a dynamic engine. OpenSSL version is 1.1.1f The issue is not encountered if http://www.openssl.org/source/openssl-1.1.1f.tar.gz is used instead. OpenSSL can be configured to use a dynamic engine by editing the default openssl config file which is located at '/etc/ssl/openssl.cnf' on Ubuntu systems. On Bluefield systems, config diff to enable PKA dynamic engine, is as below: +openssl_conf = conf_section + # Extra OBJECT IDENTIFIER info: #oid_file = $ENV::HOME/.oid oid_section= new_oids +[ conf_section ] +engines = engine_section + +[ engine_section ] +bf = bf_section + +[ bf_section ] +engine_id=pka +dynamic_path=/usr/lib/aarch64-linux-gnu/engines-1.1/pka.so +init=0 + engine_id above refers to dynamic engine name/identifier. dynamic_path points to the .so file for the dynamic engine. # curl -O https://tpo.pe/pathogen.vim double free or corruption (out) Aborted (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1921518/+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 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
Hey guys, sorry for taking so long to comment. I agree with Eric here that we should get this patch upstreamed. Since we're only seeing this issue on bionic, I think it's safe to only backport it to bionic - but preferably after it's submitted upstream and some upstream people eyeballing it. It's always useful to get upstream's input on the changes we want to propose here + this will not be a dangling bionic-only change that way. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1947099 Title: ipconfig does not honour user-requested timeouts in some cases Status in klibc package in Ubuntu: New Status in klibc source package in Bionic: In Progress Bug description: [Impact] In some cases, ipconfig can take a longer time than the user-specified timeouts, causing unexpected delays. [Test Plan] Any situation where ipconfig encounters an error sending the DHCP packet, it will automatically set a delay of 10 seconds, which could be longer than the user-specified timeout. It can be reproduced by creating a dummy interface and attempting to run ipconfig on it with a timeout value of less than 10: # ip link add eth1 type dummy # date; /usr/lib/klibc/bin/ipconfig -t 2 eth1; date Thu Nov 18 04:46:13 EST 2021 IP-Config: eth1 hardware address ae:e0:f5:9d:7e:00 mtu 1500 DHCP RARP IP-Config: no response after 2 secs - giving up Thu Nov 18 04:46:23 EST 2021 ^ Notice above, ipconfig thinks that it waited 2 seconds, but the timestamps show an actual delay of 10 seconds. [Where problems could occur] Please see reproduction steps above. We are seeing this in production too (see comment #2). [Other Info] A patch to fix the issue is being proposed here. It is a safe fix - it only checks before going into sleep that the timeout never exceeds the user-requested value. [Original Description] In some cases, ipconfig can take longer than the user-specified timeouts, causing unexpected delays. in main.c, in function loop(), the process can go into process_timeout_event() (or process_receive_event() ) and if it encounters an error situation, will set an attempt to "try again later" at time equal now + 10 seconds by setting s->expire = now + 10; This can happen at any time during the main event loop, which can end up extending the user-specified timeout if "now + 10" is greater than "start_time + user-specified-timeout". I believe a patch like the following is needed to avoid this problem: --- a/usr/kinit/ipconfig/main.c +++ b/usr/kinit/ipconfig/main.c @@ -437,6 +437,13 @@ static int loop(void) if (timeout > s->expire - now.tv_sec) timeout = s->expire - now.tv_sec; + + /* Compensate for already-lost time */ + gettimeofday(, NULL); + if (now.tv_sec + timeout > start + loop_timeout) { + timeout = loop_timeout - (now.tv_sec - start); + printf("Lowered timeout to match user request = (%d s) \n", timeout); + } } I believe the current behaviour is buggy. This is confirmed when the following line is executed: if (loop_timeout >= 0 && now.tv_sec - start >= loop_timeout) { printf("IP-Config: no response after %d " "secs - giving up\n", loop_timeout); rc = -1; goto bail; } 'loop_timeout' is the user-specified time-out. With a value of 2, in case of error, this line prints: IP-Config: no response after 2 secs - giving up So it thinks that it waited 2 seconds - however, in reality it had actually waited for 10 seconds. The suggested code-change ensures that the timeout that is actually used never exceeds the user-specified timeout. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1947099/+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 1952217] Re: bluetoothd coredumps from double free on connection of headset
Syslog from affected system. - First action is to select the affected headset from the Bluetooth applet The first thing that happens is the coredum. Then the service restarts ; this seems to be fast enough that the connection is still in progress, you can see the audio endpoints being registered, ? because the state is lost this does not complete and the device reports disconnection. * - Second action is activation of a Bluetooth keyboard This connects and functions correctly - Third action is selecting the affected headset again Same response. The keyboard is also disconnected but reconnects automatically. * this is not true : these endpoints are re-registered merely on restarting the bluetooth service. ** Attachment added: "syslog.txt" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1952217/+attachment/5543295/+files/syslog.txt -- 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/1952217 Title: bluetoothd coredumps from double free on connection of headset Status in bluez package in Ubuntu: New Bug description: Problem: Since the security updates on 2021-11-23 connecting my headset causes bluetoothd to crash, which drops all the other connections. Expected: Headset connects and works as it has done previously. ❯ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 ❯ apt-cache policy bluez bluez: Installed: 5.53-0ubuntu3.4 Candidate: 5.53-0ubuntu3.4 Headset is a Sony WH-1000XM3. I have ppa:berglh/pulseaudio-a2dp installed for the LDAC codecs for this headset. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1952217/+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 1952217] [NEW] bluetoothd coredumps from double free on connection of headset
Public bug reported: Problem: Since the security updates on 2021-11-23 connecting my headset causes bluetoothd to crash, which drops all the other connections. Expected: Headset connects and works as it has done previously. ❯ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 ❯ apt-cache policy bluez bluez: Installed: 5.53-0ubuntu3.4 Candidate: 5.53-0ubuntu3.4 Headset is a Sony WH-1000XM3. I have ppa:berglh/pulseaudio-a2dp installed for the LDAC codecs for this headset. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- 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/1952217 Title: bluetoothd coredumps from double free on connection of headset Status in bluez package in Ubuntu: New Bug description: Problem: Since the security updates on 2021-11-23 connecting my headset causes bluetoothd to crash, which drops all the other connections. Expected: Headset connects and works as it has done previously. ❯ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 ❯ apt-cache policy bluez bluez: Installed: 5.53-0ubuntu3.4 Candidate: 5.53-0ubuntu3.4 Headset is a Sony WH-1000XM3. I have ppa:berglh/pulseaudio-a2dp installed for the LDAC codecs for this headset. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1952217/+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 1639452] Re: systemd ExecStartPre test config
Hi ingopingo and anyone else, I have looked closely at your perfectly valid bug report, and I have to say thank you for reporting it and helping to improve Ubuntu. It's true that the ExecStartPre directive is incomplete, as it is not using the --conf-dir/-7 option and there isn't a folder hardcoded anywhere that the daemon uses with the --test option without argument, as we can see experimenting a bit directly with the command in that directive (root@focal:~# grep ExecStartPre /lib/systemd/system/dnsmasq.service ExecStartPre=/usr/sbin/dnsmasq --test ): 1- Let's put a bad configuration file under /etc/dnsmasq.d : root@focal:~# cat /etc/dnsmasq.d/kk.conf HELLO="I need coffee to say hello in the morning" 2- Running the command from the directive, we get: root@focal:~# /usr/sbin/dnsmasq --test dnsmasq: syntax check OK. 3- Running the command with the --conf-dir/-7 option: root@focal:~# /usr/sbin/dnsmasq --test --conf-dir=/etc/dnsmasq.d dnsmasq: bad option at line 1 of /etc/dnsmasq.d/kk.conf So, as you pointed, the ExecStartPre is doing nothing in the service unit file. But, if we look the failed status after trying a "systemctl start dnsmasq" with the bad config, we get: - Not testing well, but with SUCCESS status for the directive (so the starting process continues): Process: 34824 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, status=0/SUCCESS) - and not starting the service, because the dnsmasq's init.d file check the configuration on start: Nov 25 10:16:43 focal dnsmasq[34824]: dnsmasq: syntax check OK. Nov 25 10:16:43 focal dnsmasq[34825]: dnsmasq: bad option at line 1 of /etc/dnsmasq.d/kk.conf Nov 25 10:16:43 focal dnsmasq[34825]: bad option at line 1 of /etc/dnsmasq.d/kk.conf root@focal:~# systemctl start dnsmasq Job for dnsmasq.service failed because the control process exited with error code. See "systemctl status dnsmasq.service" and "journalctl -xe" for details. root@focal:~# systemctl status dnsmasq ● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2021-11-25 10:16:43 UTC; 4s ago Process: 34824 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, status=0/SUCCESS) Process: 34825 ExecStart=/etc/init.d/dnsmasq systemd-exec (code=exited, status=1/FAILURE) Nov 25 10:16:43 focal systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server... Nov 25 10:16:43 focal dnsmasq[34824]: dnsmasq: syntax check OK. Nov 25 10:16:43 focal dnsmasq[34825]: dnsmasq: bad option at line 1 of /etc/dnsmasq.d/kk.conf Nov 25 10:16:43 focal dnsmasq[34825]: bad option at line 1 of /etc/dnsmasq.d/kk.conf Nov 25 10:16:43 focal dnsmasq[34825]: FAILED to start up Nov 25 10:16:43 focal systemd[1]: dnsmasq.service: Control process exited, code=exited, status=1/FAILURE Nov 25 10:16:43 focal systemd[1]: dnsmasq.service: Failed with result 'exit-code'. Nov 25 10:16:43 focal systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1639452 Title: systemd ExecStartPre test config Status in dnsmasq package in Ubuntu: Fix Released Status in dnsmasq source package in Bionic: Triaged Status in dnsmasq source package in Focal: Triaged Bug description: The standard configuration file of dnsmasq is complete commented out. The real configuration is saved in /etc/dnsmasq.d, so the test of systemd is a fake. In the Service Section of /lib/systemd/system/dnsmasq.service the ExecStartPre directive should be set to "/usr/sbin/dnsmasq --conf- dir=/etc/dnsmasq.d --test" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639452/+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 1952107] Re: Google Contacts API Deprecated
** Bug watch added: gitlab.gnome.org/GNOME/evolution/-/issues #1658 https://gitlab.gnome.org/GNOME/evolution/-/issues/1658 ** Also affects: evolution-data-server via https://gitlab.gnome.org/GNOME/evolution/-/issues/1658 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1952107 Title: Google Contacts API Deprecated Status in evolution-data-server: Unknown Status in evolution-data-server package in Ubuntu: New Bug description: I opened Evolution today and a red banner appeared on top with the following message: > Failed to connect address book “ : Contacts” > Invalid request URI or header, or unsupported nonstandard parameter: Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration. I found the upstream bug report for this[0], which references the commit[1] that fixes it. However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 3.40.4-1. Is it possible to backport this commit so that Evolution will continue to work properly? [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658 [1]: https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+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 1951667] Re: [SRU] pulseaudio: restore hdmi audio be active output after resume
OK, drop the hirsute then. Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1951667 Title: [SRU] pulseaudio: restore hdmi audio be active output after resume Status in HWE Next: New Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Focal: Fix Committed Status in pulseaudio source package in Hirsute: Won't Fix Status in pulseaudio source package in Impish: Fix Committed Status in pulseaudio source package in Jammy: Fix Committed Bug description: [Impact] On the machines with legacy HDA audio driver, when users plug a hdmi/dp monitor, the active output device is still speaker, need users to manually select the hdmi, then the hdmi audio will be the users' preference, once it is plugged, it should become the active output automatically. But with the current PA, after reboot and suspend/resume, the hdmi can't change to be active output automatically anymore. [Fix] Backport an upstream fix, this will fix the issue of "preferred ports being cleaned by a mistake" [Test] On a machine with legacy HDA audio driver, install the patched pulseaudio, then run 'rm ~/.config/pulse/*; reboot', plug a hdmi monitor, select the hdmi audio to be active, with the hdmi monitor plugged and reboot, suspend and resume, check what is the active output, it is still the hdmi audio. [Where problems could occur] This patch is in the card-restore.c, if it could introduce regression, it will be on the default active input/output devices, for example, users select a input or output device to be active, after reboot, if those devices are available, they should be active, but they could be replaced by other devices if a regression is introduced. But this possibility is very low since we tested the patch on a couple of desktop and laptop machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1951667/+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