[Touch-packages] [Bug 1942764] Re: Enable riscv64 build of mesa-opencl-icd
** Tags added: fr-1691 -- 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/1942764 Title: Enable riscv64 build of mesa-opencl-icd Status in mesa package in Ubuntu: In Progress Bug description: Ubuntu release: impish Package version: 21.2.1-2ubuntu1 `mesa-opencl-icd` is needed for `libhmsbeagle` to be installable, so is it possible to enable this package as I have done here: https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/12687486/+listing- archive-extra ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1942764/+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 413278]
http://www.iu-bloomington.com/
https://komiya-dental.com/
http://steemfilter.space/
http://michielleunens.tech/
http://sleepypoetstuff.website/
http://biciclubvalencia.website/
http://reputation-management.site/
http://pitesti.online/
http://tobuweb.space/
http://ancientmariners.online/
http://betwsycoednet.online
http://kuzin.website
http://kundaliniyoga.tech
http://localpay.tech
http://my-iframe.online
http://getimov.xyz/
http://ooviv.xyz/
http://mirei.xyz
http://toblek.xyz/
http://sevenwonders.store
http://peralga.xyz/
https://texastourgear.live
http://freixenet.site/influencerprogramme/
http://timvanorden.store/
http://rhee.tech/
http://f3group.online/
https://www.hlungomare.store/
https://www.lungomarebikehotel.store
http://www.lvmaimai.xyz/
https://sozdanie.site/
http://www.tabletshop.xyz/
http://steroidslegit.xyz/
http://ruirui.store/
http://www.foamhands.store/
http://www.i-obchody.info/
http://naughtyrobot.digital/
https://www.webb-dev.co.uk/
https://waytowhatsnext.com/
http://troubadourtunes.online/
http://www.babygadgets.xyz/
http://agens128.site/
http://hydra-official.site/
http://www.gardensupplies.xyz/
http://www.learntosurf.xyz/
http://www.handmadecandle.xyz/
http://www.divingcourses.xyz/
http://www.vapingpro.xyz/
http://www.partypieces.xyz/
http://www.cookwareonline.xyz/
http://www.fencesuppliers.xyz/
http://alaskamysterypictures.website/
http://j70sanfranciscobay.website
http://vloerverwarming.xyz/
http://koffieautomaat.xyz/
http://motherlode.store/
http://yamaro-everyfish.store/
http://ipatovo.store/
http://tinguely.site/
http://wasillahomes.website/
http://www-look-4.com/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to eglibc in Ubuntu.
https://bugs.launchpad.net/bugs/413278
Title:
stack protector guard value does not lead with a NULL byte
Status in GLibC:
Fix Released
Status in eglibc package in Ubuntu:
Fix Released
Status in glibc package in Ubuntu:
Invalid
Status in eglibc source package in Jaunty:
Invalid
Status in glibc source package in Jaunty:
Fix Released
Status in eglibc source package in Karmic:
Fix Released
Status in glibc source package in Karmic:
Invalid
Bug description:
IMPACT: stack protections are weakened due to strcpy function being able to
write the stack guard (since it does not start with a zero byte).
ADDRESSED: correctly implement leading zero, as done in Karmic.
DISCUSSION: regression potential is low, since the patch is isolated and well
tested.
TEST CASE:
$ bzr branch lp:~ubuntu-bugcontrol/qa-regression-testing/master
qa-regression-testing
$ cd qa-regression-testing/scripts
$ ./test-glibc-security.py -v
Build helper tools ... (9.10) ok
glibc heap protection ... ok
sprintf not pre-truncated with -D_FORTIFY_SOURCE=2 ... ok
glibc pointer obfuscation ... ok
Password hashes ... (sha512) ok
Stack guard exists ... ok
Stack guard leads with zero byte ... FAIL
Stack guard is randomized ... ok
==
FAIL: Stack guard leads with zero byte
--
Traceback (most recent call last):
File "./test-glibc-security.py", line 170, in test_81_stack_guard_leads_zero
self.assertEqual(one.startswith('00 '), expected, one)
AssertionError: 62 55 59 69 cd 20 39 80
--
Ran 8 tests in 0.145s
FAILED (failures=1)
expected outcome: 0 failures.
ProblemType: Bug
Architecture: amd64
Date: Thu Aug 13 13:59:02 2009
Dependencies:
findutils 4.4.2-1
gcc-4.4-base 4.4.1-1ubuntu3
libc6 2.10.1-0ubuntu6
libgcc1 1:4.4.1-1ubuntu3
DistroRelease: Ubuntu 9.10
Package: libc6 2.10.1-0ubuntu6
ProcEnviron:
LANGUAGE=en_US.UTF-8
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
SourcePackage: eglibc
Uname: Linux 2.6.31-5-generic x86_64
To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/413278/+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 1940996]
Did the patch ever get sent to libc-alpha? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1940996 Title: test failure - test-regex Status in grep: In Progress Status in grep package in Ubuntu: New Bug description: 'test-regex' fails when building grep against glibc 2.34. Per commentary from grep upstream at https://debbugs.gnu.org/cgi/bugreport.cgi?bug=50069, the test failure can be attributed to skew between the glibc built-in regex and the one that is found in the grep source code. To manage notifications about this bug go to: https://bugs.launchpad.net/grep/+bug/1940996/+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 1940996]
(In reply to Michael Hudson-Doyle from comment #11) > Did the patch ever get sent to libc-alpha? Unfortunately I never got around to it. Someone else can shepherd it if it's urgent; otherwise I suppose it can wait until someone gets around to syncing Gnulib with glibc. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1940996 Title: test failure - test-regex Status in grep: In Progress Status in grep package in Ubuntu: New Bug description: 'test-regex' fails when building grep against glibc 2.34. Per commentary from grep upstream at https://debbugs.gnu.org/cgi/bugreport.cgi?bug=50069, the test failure can be attributed to skew between the glibc built-in regex and the one that is found in the grep source code. To manage notifications about this bug go to: https://bugs.launchpad.net/grep/+bug/1940996/+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 1941752] Re: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable
Launchpad has imported 5 comments from the remote bug at https://bugs.kde.org/show_bug.cgi?id=441121. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2021-08-18T09:17:31+00:00 Friendofanimals wrote: Application: gwenview (20.12.3) Qt Version: 5.15.2 Frameworks Version: 5.80.0 Operating System: Linux 5.11.0-31-generic x86_64 Windowing System: X11 Drkonqi Version: 5.21.4 Distribution: Ubuntu 21.04 -- Information about the crash: - What I was doing when the application crashed: tried to open a .jpg picture out of dolphin. retried with different pictures, always crashing. Same happening when opening a picture out of gwenview. The crash can be reproduced every time. -- Backtrace: Application: Gwenview (gwenview), signal: Aborted [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 #5 0x7efd984e8864 in __GI_abort () at abort.c:79 #6 0x7efd9874fa31 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6 #7 0x7efd9875b4fc in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6 #8 0x7efd9875b567 in std::terminate() () from /lib/x86_64-linux-gnu/libstdc++.so.6 #9 0x7efd9875b809 in __cxa_throw () from /lib/x86_64-linux-gnu/libstdc++.so.6 #10 0x7efd98752452 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6 #11 0x7efd981bbad3 in ?? () from /lib/x86_64-linux-gnu/libexiv2.so.27 #12 0x7efd9815f92d in Exiv2::Xmpdatum::write(std::ostream&, Exiv2::ExifData const*) const () from /lib/x86_64-linux-gnu/libexiv2.so.27 #13 0x7efd9a66a250 in Gwenview::ImageMetaInfoModel::setExiv2Image(Exiv2::Image const*) () from /lib/x86_64-linux-gnu/libgwenviewlib.so.5 #14 0x7efd9a634a70 in Gwenview::Document::setExiv2Image(std::unique_ptr >) () from /lib/x86_64-linux-gnu/libgwenviewlib.so.5 #15 0x7efd9a63e39b in ?? () from /lib/x86_64-linux-gnu/libgwenviewlib.so.5 #16 0x7efd98bb75c7 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7efd9899ea25 in QFutureWatcherBase::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7efd99854783 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7efd98b7f7ba in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7efd98b827e1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7efd98bd9ba7 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7efd962c38eb in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7efd96316d28 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7efd962c1023 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7efd98bd9204 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7efd98b7e11b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7efd98b86604 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x564728787c1f in ?? () #29 0x7efd984ea565 in __libc_start_main (main=0x5647287876f0, argc=2, argv=0x7ffe3e40e118, init=, fini=, rtld_fini=, stack_end=0x7ffe3e40e108) at ../csu/libc-start.c:332 #30 0x56472878813e in _start () [Inferior 1 (process 13527) detached] Possible duplicates by query: bug 440777, bug 440257, bug 434072, bug 429344, bug 427716. Reported using DrKonqi Reply at: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1941752/comments/0 On 2021-08-19T19:37:18+00:00 Alexander Fieroch wrote: same here since this week. Maybe a bug through latest gwenview, x11 or libjpeg library because last week I had no problem?! I can load original JPGs from my digital camera with gwenview but trying to load edited and exported jpegs by darktable will crash gwenview immediately. Until last week this was working! gwenview 4:21.04.3-0ubuntu1~ubuntu21.04~ppa1 libgl1-mesa-dri (21.0.3-0ubuntu0.2 => 21.0.3-0ubuntu0.3) darktable org.darktable.Darktable 3.6.0 stable system Reply at: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1941752/comments/1 On 2021-08-24T20:33:52+00:00 Jan Rathmann wrote: This seems to be related to a recent security update of exiv2 in Ubuntu 21.04. libexiv2-27 version 0.27.3-3ubuntu1.5: Gwenview (21.08.0) crashes when I try to open JPEG files generated by darktable. libexiv2-27 version 0.27.3-3ubuntu1.4: Gwenview (21.08.0) doesn't crash. Link to the changelog of exiv2 package on Ubuntu: http://changelogs
[Touch-packages] [Bug 1685878] Re: Gedit bottom scroll bar goes on top of final line
** Changed in: gtk Status: Unknown => New -- 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/1685878 Title: Gedit bottom scroll bar goes on top of final line Status in GTK+: New Status in Ubuntu GNOME: New Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: I am on Ubuntu GNOME 17.04 with GNOME 3.24, though obviously still Gedit 3.22, and I have found something slightly annoying with it, and that is that when mousing over the last line to try to copy and paste it for instance, the bottom scroll bar goes on top of it and obscures it. I have attached two screenshots of what I mean. This also affects me on Arch so I have filled an upstream report on this. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1685878/+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 1943053] Re: fernseher wird nach upload nicht mehr erkannt
Thanks for the bug report. Can you provide more details about what is not working? --- Danke für den Fehlerbericht. Können Sie genauere Angaben dazu machen, was nicht funktioniert? ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-340 (Ubuntu) ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1943053 Title: fernseher wird nach upload nicht mehr erkannt Status in nvidia-graphics-drivers-340 package in Ubuntu: Incomplete Bug description: fernseher wird nach upload nicht mehr erkannt ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 NonfreeKernelModules: nvidia wl .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Sep 8 17:11:50 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-80-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-81-generic, x86_64: installed nvidia-340, 340.108, 5.4.0-80-generic, x86_64: installed nvidia-340, 340.108, 5.4.0-81-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation G98M [Quadro NVS 160M] [10de:06eb] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G98M [Quadro NVS 160M] [1028:024f] InstallationDate: Installed on 2017-05-13 (1578 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Latitude E6500 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=bcd1ee35-e00c-4690-9976-68edba31a164 ro plymouth:debug drm.debug=0xe SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.asset.tag: NB000272 dmi.board.vendor: Dell Inc. dmi.chassis.asset.tag: NB000272 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd10/30/2009:svnDellInc.:pnLatitudeE6500:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude E6500 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Wed Sep 8 17:06:29 2021 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.11-1ubuntu1~20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1943053/+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 1943025] Re: [Dell Inspiron 5301] Touch pad
Thanks for the bug report. > When i'm going to the applications page and that i do anything, suddenly i can't scroll. Does that mean you only can't scroll the applications page, or that you can't scroll app windows *after* using the applications page? And is it only scrolling? Can you still move the pointer? ** Summary changed: - Touch pad + [Dell Inspiron 5301] Touch pad ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1943025 Title: [Dell Inspiron 5301] Touch pad Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hi ! I have a little problem with my Touch pad. When i'm going to the applications page and that i do anything, suddenly i can't scroll. When i run xinput list i see that touchpad is in DLL and not in Synaptics maybe it's the problem or not, it's like that i'm doing this report. Thank you for the help ! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 8 11:54:45 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fb] InstallationDate: Installed on 2021-09-07 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. Inspiron 5301 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=45878a68-e793-429d-a95b-fc468f5a9ba3 ro quiet splash i8042.reset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2020 dmi.bios.release: 1.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0R29K5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd10/27/2020:br1.3:svnDellInc.:pnInspiron5301:pvr:sku09FB:rvnDellInc.:rn0R29K5:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5301 dmi.product.sku: 09FB dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1943025/+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 1917148] Re: ps version is UNKNOWN in procps 2:3.3.16-1ubuntu2
Autopkgtest for the attached debdiff. ** Attachment added: "log" https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1917148/+attachment/5523941/+files/log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1917148 Title: ps version is UNKNOWN in procps 2:3.3.16-1ubuntu2 Status in procps package in Ubuntu: Fix Released Status in procps source package in Bionic: Fix Released Status in procps source package in Focal: In Progress Status in procps source package in Hirsute: Fix Released Status in procps source package in Impish: Fix Released Bug description: [Impact] * Breakage of tools expecting the version number or the number to substantially match the Debian package version. * May confuse users expecting the version to substantially match the Debian package version. * Restores behavior to that provided in Groovy/Hirsute+ and Bionic and prior releases. - Focal is the only release affected. * Backported Debian fix to restore ".tarball-version" file to provide version information during build. - Also included the autopkgtests for versioning from the same Debian fix. [Test Plan] 1) Create a Focal (or derived from Focal) system. 2) Execute "ps --version" or any of the binaries provided by the package with their respective version flags. 3) Instead of desired output of the version, the output is: the invoked binary name followed by "from procps-ng UNKNOWN" Example: "ps from procps-ng UNKNOWN" [Where problems could occur] * This fix could cause issues if applications have come to depend on the incorrect behavior. IE, an application that uses a version string of "UNKNOWN" as part of a heuristic for identifying a Focal system. * If the version of procps-ng is incremented, this patch would need to be updated or removed if it is no longer relevant. Otherwise, an incorrect version would be reported by the binaries. * The addition of the autopkgtests could cause testing failures. [Other Info] * This change is in Groovy+ and Debian packaging with the same version of procps-ng. - Introduced in procps (2:3.3.16-5) unstable in Debian. [Original Description] From Linux Lint 20.1, so Focal Fossa 20.04.1 Package procps 2:3.3.16-1ubuntu2 $ LANG=C ps --version ps from procps-ng UNKNOWN I don't know if it comes from Ubuntu or upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1917148/+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 1917148] Re: ps version is UNKNOWN in procps 2:3.3.16-1ubuntu2
Proposed debdiff for Focal ** Patch added: "lp1917148_focal.debdiff" https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1917148/+attachment/5523939/+files/lp1917148_focal.debdiff ** Description changed: [Impact] - * Breakage of tools expecting the version number or the number to substantially -match the Debian package version. - * May confuse users expecting the version to substantially match the Debian -package version. - * Restores behavior to that provided in Groovy/Hirsute+ and Bionic and prior releases. -- Focal is the only release affected. - * Backported Debian fix to restore ".tarball-version" file to provide version information -during build. -- Also included the autopkgtests for versioning from the same Debian fix. + * Breakage of tools expecting the version number or the number to substantially match the Debian package version. + * May confuse users expecting the version to substantially match the Debian package version. + * Restores behavior to that provided in Groovy/Hirsute+ and Bionic and prior releases. + - Focal is the only release affected. + * Backported Debian fix to restore ".tarball-version" file to provide version information during build. + - Also included the autopkgtests for versioning from the same Debian fix. [Test Plan] - 1) Create a Focal (or derived from Focal) system. - 2) Execute "ps --version" or any of the binaries provided by the package with - their respective version flags. - 3) Instead of desired output of the version, the output is: - the invoked binary name followed by "from procps-ng UNKNOWN" - Example: "ps from procps-ng UNKNOWN" + 1) Create a Focal (or derived from Focal) system. + 2) Execute "ps --version" or any of the binaries provided by the package with their respective version flags. + 3) Instead of desired output of the version, the output is: + the invoked binary name followed by "from procps-ng UNKNOWN" + Example: "ps from procps-ng UNKNOWN" [Where problems could occur] - * This fix could cause issues if applications have come to depend on the incorrect -behavior. IE, an application that uses a version string of "UNKNOWN" as part of a heuristic -for identifying a Focal system. - * If the version of procps-ng is incremented, this patch would need to be updated or removed -if it is no longer relevant. Otherwise, an incorrect version would be reported by the binaries. - * The addition of the autopkgtests could cause testing failures. + * This fix could cause issues if applications have come to depend on the incorrect behavior. IE, an application that uses a version string of "UNKNOWN" as part of a heuristic for identifying a Focal system. + * If the version of procps-ng is incremented, this patch would need to be updated or removed if it is no longer relevant. Otherwise, an incorrect version would be reported by the binaries. + * The addition of the autopkgtests could cause testing failures. [Other Info] - * This change is in Groovy+ and Debian packaging with the same version of procps-ng. -- Introduced in procps (2:3.3.16-5) unstable in Debian. + * This change is in Groovy+ and Debian packaging with the same version of procps-ng. + - Introduced in procps (2:3.3.16-5) unstable in Debian. [Original Description] From Linux Lint 20.1, so Focal Fossa 20.04.1 Package procps 2:3.3.16-1ubuntu2 $ LANG=C ps --version ps from procps-ng UNKNOWN I don't know if it comes from Ubuntu or upstream. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1917148 Title: ps version is UNKNOWN in procps 2:3.3.16-1ubuntu2 Status in procps package in Ubuntu: Fix Released Status in procps source package in Bionic: Fix Released Status in procps source package in Focal: In Progress Status in procps source package in Hirsute: Fix Released Status in procps source package in Impish: Fix Released Bug description: [Impact] * Breakage of tools expecting the version number or the number to substantially match the Debian package version. * May confuse users expecting the version to substantially match the Debian package version. * Restores behavior to that provided in Groovy/Hirsute+ and Bionic and prior releases. - Focal is the only release affected. * Backported Debian fix to restore ".tarball-version" file to provide version information during build. - Also included the autopkgtests for versioning from the same Debian fix. [Test Plan] 1) Create a Focal (or derived from Focal) system. 2) Execute "ps --version" or any of the binaries provided by the package with their respective version flags. 3) Instead of desired output of the version, the output is: the invoked binary name followed by "from procps-ng UNKNOWN" Example: "ps from procps-ng UN
[Touch-packages] [Bug 1917148] Re: ps version is UNKNOWN in procps 2:3.3.16-1ubuntu2
** Description changed: [Impact] + * Breakage of tools expecting the version number or the number to substantially +match the Debian package version. + * May confuse users expecting the version to substantially match the Debian +package version. + * Restores behavior to that provided in Groovy/Hirsute+ and Bionic and prior releases. +- Focal is the only release affected. + * Backported Debian fix to restore ".tarball-version" file to provide version information +during build. +- Also included the autopkgtests for versioning from the same Debian fix. [Test Plan] + 1) Create a Focal (or derived from Focal) system. + 2) Execute "ps --version" or any of the binaries provided by the package with + their respective version flags. + 3) Instead of desired output of the version, the output is: + the invoked binary name followed by "from procps-ng UNKNOWN" + Example: "ps from procps-ng UNKNOWN" [Where problems could occur] + * This fix could cause issues if applications have come to depend on the incorrect +behavior. IE, an application that uses a version string of "UNKNOWN" as part of a heuristic +for identifying a Focal system. + * If the version of procps-ng is incremented, this patch would need to be updated or removed +if it is no longer relevant. Otherwise, an incorrect version would be reported by the binaries. + * The addition of the autopkgtests could cause testing failures. [Other Info] - + * This change is in Groovy+ and Debian packaging with the same version of procps-ng. +- Introduced in procps (2:3.3.16-5) unstable in Debian. [Original Description] From Linux Lint 20.1, so Focal Fossa 20.04.1 Package procps 2:3.3.16-1ubuntu2 $ LANG=C ps --version ps from procps-ng UNKNOWN I don't know if it comes from Ubuntu or upstream. ** Changed in: procps (Ubuntu Focal) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1917148 Title: ps version is UNKNOWN in procps 2:3.3.16-1ubuntu2 Status in procps package in Ubuntu: Fix Released Status in procps source package in Bionic: Fix Released Status in procps source package in Focal: In Progress Status in procps source package in Hirsute: Fix Released Status in procps source package in Impish: Fix Released Bug description: [Impact] * Breakage of tools expecting the version number or the number to substantially match the Debian package version. * May confuse users expecting the version to substantially match the Debian package version. * Restores behavior to that provided in Groovy/Hirsute+ and Bionic and prior releases. - Focal is the only release affected. * Backported Debian fix to restore ".tarball-version" file to provide version information during build. - Also included the autopkgtests for versioning from the same Debian fix. [Test Plan] 1) Create a Focal (or derived from Focal) system. 2) Execute "ps --version" or any of the binaries provided by the package with their respective version flags. 3) Instead of desired output of the version, the output is: the invoked binary name followed by "from procps-ng UNKNOWN" Example: "ps from procps-ng UNKNOWN" [Where problems could occur] * This fix could cause issues if applications have come to depend on the incorrect behavior. IE, an application that uses a version string of "UNKNOWN" as part of a heuristic for identifying a Focal system. * If the version of procps-ng is incremented, this patch would need to be updated or removed if it is no longer relevant. Otherwise, an incorrect version would be reported by the binaries. * The addition of the autopkgtests could cause testing failures. [Other Info] * This change is in Groovy+ and Debian packaging with the same version of procps-ng. - Introduced in procps (2:3.3.16-5) unstable in Debian. [Original Description] From Linux Lint 20.1, so Focal Fossa 20.04.1 Package procps 2:3.3.16-1ubuntu2 $ LANG=C ps --version ps from procps-ng UNKNOWN I don't know if it comes from Ubuntu or upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1917148/+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 1943077] Re: snapd fails to autopkgtest on mksquashfs, which is looking for libgcc_s
https://github.com/snapcore/snapd/pull/10757 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1943077 Title: snapd fails to autopkgtest on mksquashfs, which is looking for libgcc_s Status in snapd: New Status in openssh package in Ubuntu: New Status in squashfs-tools package in Ubuntu: New Bug description: During current snapd autopkgtest, a failure can be observed: https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/amd64/s/snapd/20210907_175258_5451b@/log.gz error: cannot pack "/home/gopath/src/github.com/snapcore/snapd/tests/smoke/sandbox/test-snapd-sandbox": mksquashfs call failed: - libgcc_s.so.1 must be installed for pthread_cancel to work Parallel mksquashfs: Using 1 processor Creating 4.0 filesystem on /home/gopath/src/github.com/snapcore/snapd/tests/smoke/sandbox/test-snapd-sandbox/test-snapd-sandbox_1.0_all.snap, block size 131072. - error: cannot read snap file: "/var/lib/snapd/snaps/.local-install-136125945" is not a snap or snapdir I traced the underlying call to the following: "/snap/snapd/current/lib/x86_64-linux-gnu/ld-2.23.so" "--library-path" "/snap/snapd/current/usr/local/lib:/snap/snapd/current/lib/x86_64-linux-gnu:/snap/snapd/current/usr/lib/x86_64-linux-gnu" "/snap/snapd/current/usr/bin/mksquashfs" asdf asdf.squashfs (the real call has more arguments, this is a simplified version that produces the failure) To observe this, one can create a VM based a cloud image from https://cloud-images.ubuntu.com/impish/current, then run the above command in the resulting environment. Doing so will test against snapd v2.51.4 (12883). Retesting with edge 2.52+git635.gada2d87 (13323) produces an equivalent result. Running a more bland `/snap/snapd/current/usr/bin/mksquashfs asdf asdf.squashfs` without messing with library paths has mksquashfs behaving as expected. Also, getting a v2.51.3 snapd seems to behave itself. Updating from 2.51.3 -> 2.51.4 also works. One can see a passing mksquashfs by taking libgcc_s.so.1 from hirsute and placing it in the library path for the above call. In the working scenario, it appears that libgcc_s is being obtained from outside of /snap (and also libz). In the failing scenario, this external copy of libgcc_s is not being loaded (per gdb info sharedlibrary), but libz still is. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1943077/+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 1943077] Re: snapd fails to autopkgtest on mksquashfs, which is looking for libgcc_s
So what is going on here is that libc is trying to load libgcc_s.so.1 and as it is not in the snap it ends up loading it from the host. Apparently in all releases from xenial through to hirsute this has worked but for whatever reason it does not work on impish. I think the appropriate fix is for the snapd snap to bundle libgcc_s.so.1 too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1943077 Title: snapd fails to autopkgtest on mksquashfs, which is looking for libgcc_s Status in snapd: New Status in openssh package in Ubuntu: New Status in squashfs-tools package in Ubuntu: New Bug description: During current snapd autopkgtest, a failure can be observed: https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/amd64/s/snapd/20210907_175258_5451b@/log.gz error: cannot pack "/home/gopath/src/github.com/snapcore/snapd/tests/smoke/sandbox/test-snapd-sandbox": mksquashfs call failed: - libgcc_s.so.1 must be installed for pthread_cancel to work Parallel mksquashfs: Using 1 processor Creating 4.0 filesystem on /home/gopath/src/github.com/snapcore/snapd/tests/smoke/sandbox/test-snapd-sandbox/test-snapd-sandbox_1.0_all.snap, block size 131072. - error: cannot read snap file: "/var/lib/snapd/snaps/.local-install-136125945" is not a snap or snapdir I traced the underlying call to the following: "/snap/snapd/current/lib/x86_64-linux-gnu/ld-2.23.so" "--library-path" "/snap/snapd/current/usr/local/lib:/snap/snapd/current/lib/x86_64-linux-gnu:/snap/snapd/current/usr/lib/x86_64-linux-gnu" "/snap/snapd/current/usr/bin/mksquashfs" asdf asdf.squashfs (the real call has more arguments, this is a simplified version that produces the failure) To observe this, one can create a VM based a cloud image from https://cloud-images.ubuntu.com/impish/current, then run the above command in the resulting environment. Doing so will test against snapd v2.51.4 (12883). Retesting with edge 2.52+git635.gada2d87 (13323) produces an equivalent result. Running a more bland `/snap/snapd/current/usr/bin/mksquashfs asdf asdf.squashfs` without messing with library paths has mksquashfs behaving as expected. Also, getting a v2.51.3 snapd seems to behave itself. Updating from 2.51.3 -> 2.51.4 also works. One can see a passing mksquashfs by taking libgcc_s.so.1 from hirsute and placing it in the library path for the above call. In the working scenario, it appears that libgcc_s is being obtained from outside of /snap (and also libz). In the failing scenario, this external copy of libgcc_s is not being loaded (per gdb info sharedlibrary), but libz still is. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1943077/+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 1943077] Re: snapd fails to autopkgtest on mksquashfs, which is looking for libgcc_s
(I confirmed by bind mount shenanigans that putting the libgcc_s.so.1 from the core snapd into the snapd snap makes this work) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1943077 Title: snapd fails to autopkgtest on mksquashfs, which is looking for libgcc_s Status in snapd: New Status in openssh package in Ubuntu: New Status in squashfs-tools package in Ubuntu: New Bug description: During current snapd autopkgtest, a failure can be observed: https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/amd64/s/snapd/20210907_175258_5451b@/log.gz error: cannot pack "/home/gopath/src/github.com/snapcore/snapd/tests/smoke/sandbox/test-snapd-sandbox": mksquashfs call failed: - libgcc_s.so.1 must be installed for pthread_cancel to work Parallel mksquashfs: Using 1 processor Creating 4.0 filesystem on /home/gopath/src/github.com/snapcore/snapd/tests/smoke/sandbox/test-snapd-sandbox/test-snapd-sandbox_1.0_all.snap, block size 131072. - error: cannot read snap file: "/var/lib/snapd/snaps/.local-install-136125945" is not a snap or snapdir I traced the underlying call to the following: "/snap/snapd/current/lib/x86_64-linux-gnu/ld-2.23.so" "--library-path" "/snap/snapd/current/usr/local/lib:/snap/snapd/current/lib/x86_64-linux-gnu:/snap/snapd/current/usr/lib/x86_64-linux-gnu" "/snap/snapd/current/usr/bin/mksquashfs" asdf asdf.squashfs (the real call has more arguments, this is a simplified version that produces the failure) To observe this, one can create a VM based a cloud image from https://cloud-images.ubuntu.com/impish/current, then run the above command in the resulting environment. Doing so will test against snapd v2.51.4 (12883). Retesting with edge 2.52+git635.gada2d87 (13323) produces an equivalent result. Running a more bland `/snap/snapd/current/usr/bin/mksquashfs asdf asdf.squashfs` without messing with library paths has mksquashfs behaving as expected. Also, getting a v2.51.3 snapd seems to behave itself. Updating from 2.51.3 -> 2.51.4 also works. One can see a passing mksquashfs by taking libgcc_s.so.1 from hirsute and placing it in the library path for the above call. In the working scenario, it appears that libgcc_s is being obtained from outside of /snap (and also libz). In the failing scenario, this external copy of libgcc_s is not being loaded (per gdb info sharedlibrary), but libz still is. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1943077/+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 1943077] Re: snapd fails to autopkgtest on mksquashfs, which is looking for libgcc_s
Added openssh and squashfs-tools so that this bug shows on the proposed- migration report. ** Also affects: openssh (Ubuntu) Importance: Undecided Status: New ** Also affects: squashfs-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1943077 Title: snapd fails to autopkgtest on mksquashfs, which is looking for libgcc_s Status in snapd: New Status in openssh package in Ubuntu: New Status in squashfs-tools package in Ubuntu: New Bug description: During current snapd autopkgtest, a failure can be observed: https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/amd64/s/snapd/20210907_175258_5451b@/log.gz error: cannot pack "/home/gopath/src/github.com/snapcore/snapd/tests/smoke/sandbox/test-snapd-sandbox": mksquashfs call failed: - libgcc_s.so.1 must be installed for pthread_cancel to work Parallel mksquashfs: Using 1 processor Creating 4.0 filesystem on /home/gopath/src/github.com/snapcore/snapd/tests/smoke/sandbox/test-snapd-sandbox/test-snapd-sandbox_1.0_all.snap, block size 131072. - error: cannot read snap file: "/var/lib/snapd/snaps/.local-install-136125945" is not a snap or snapdir I traced the underlying call to the following: "/snap/snapd/current/lib/x86_64-linux-gnu/ld-2.23.so" "--library-path" "/snap/snapd/current/usr/local/lib:/snap/snapd/current/lib/x86_64-linux-gnu:/snap/snapd/current/usr/lib/x86_64-linux-gnu" "/snap/snapd/current/usr/bin/mksquashfs" asdf asdf.squashfs (the real call has more arguments, this is a simplified version that produces the failure) To observe this, one can create a VM based a cloud image from https://cloud-images.ubuntu.com/impish/current, then run the above command in the resulting environment. Doing so will test against snapd v2.51.4 (12883). Retesting with edge 2.52+git635.gada2d87 (13323) produces an equivalent result. Running a more bland `/snap/snapd/current/usr/bin/mksquashfs asdf asdf.squashfs` without messing with library paths has mksquashfs behaving as expected. Also, getting a v2.51.3 snapd seems to behave itself. Updating from 2.51.3 -> 2.51.4 also works. One can see a passing mksquashfs by taking libgcc_s.so.1 from hirsute and placing it in the library path for the above call. In the working scenario, it appears that libgcc_s is being obtained from outside of /snap (and also libz). In the failing scenario, this external copy of libgcc_s is not being loaded (per gdb info sharedlibrary), but libz still is. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1943077/+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 1917148] Re: ps version is UNKNOWN in procps 2:3.3.16-1ubuntu2
** Tags added: sts-sponsors-slashd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1917148 Title: ps version is UNKNOWN in procps 2:3.3.16-1ubuntu2 Status in procps package in Ubuntu: Fix Released Status in procps source package in Bionic: Fix Released Status in procps source package in Focal: Confirmed Status in procps source package in Hirsute: Fix Released Status in procps source package in Impish: Fix Released Bug description: [Impact] [Test Plan] [Where problems could occur] [Other Info] [Original Description] From Linux Lint 20.1, so Focal Fossa 20.04.1 Package procps 2:3.3.16-1ubuntu2 $ LANG=C ps --version ps from procps-ng UNKNOWN I don't know if it comes from Ubuntu or upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1917148/+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 1939750] Re: Please merge 7.74.0-1.3
Marking Fix Released as 7.74.0-1.3ubuntu1 can now be found in impish. ** Changed in: curl (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1939750 Title: Please merge 7.74.0-1.3 Status in curl package in Ubuntu: Fix Released Status in curl package in Debian: Unknown Bug description: Debian version 7.74.0-1.3 cherry-picks a fix for a command line API breakage that would be unexpected in a minor version release. Please help merge. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989064 https://github.com/curl/curl/issues/6321 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1939750/+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 1889010] Re: [Inspiron 5482, Realtek ALC3204, Black Headphone Out, Front] Playback problem
I am able to fix this, temporarily, by going into pavucontrol, unmuting the microphone under Input Devices, and muting it again. I will have to check later what the exact name of the microphone device in question is. Note this applies even to headphones that do not have a built-in microphone. -- 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/1889010 Title: [Inspiron 5482, Realtek ALC3204, Black Headphone Out, Front] Playback problem Status in alsa-driver package in Ubuntu: Confirmed Bug description: I'm unable to play sound through the headphone jack on this laptop. When I try to play a wav with aplay (e.g. aplay /usr/share/sounds/speech-dispatcher/test.wav) the level indicators in pavucontrol fluctuate, but no sound results. Adjusting the volume does not help. Also, when the headphones are plugged in, I cannot play sound through the internal speakers by selecting the "Speakers" port in pavucontrol Output Devices. With the headphones unplugged, the internal speakers work fine. I tested the Ubuntu 19.10 live USB and I am able to play sound through the headphones without doing anything special (plug in headphones, select "Headphones" from the popup that appears, and use aplay as above), so the hardware itself is apparently okay. The headphones do not work when booting the Ubuntu 20.04 live USB. The problem may be intermittent as I seem to recall I have been able to use the headphones since upgrading to 20.04, but I am not sure of my recollection. I also think that in some of my tests, I was able to play sound through the speakers with the headphones plugged in (by selecting Speakers in pavucontrol) but I cannot reproduce this now. Happy to provide more information, try troubleshooting ideas, etc. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nate 2549 F pulseaudio CasperMD5CheckResult: skip Date: Sun Jul 26 14:20:31 2020 InstallationDate: Installed on 2019-06-03 (419 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_Type: Only some of outputs are working Title: [Inspiron 5482, Realtek ALC3204, Black Headphone Out, Front] Playback problem UpgradeStatus: Upgraded to focal on 2020-06-14 (42 days ago) dmi.bios.date: 07/02/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0G7VYP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/02/2019:svnDellInc.:pnInspiron5482:pvr:rvnDellInc.:rn0G7VYP:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5482 dmi.product.sku: 089E dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1889010/+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 1917148] Re: ps version is UNKNOWN in procps 2:3.3.16-1ubuntu2
** Tags added: seg sts ** Also affects: procps (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: procps (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: procps (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: procps (Ubuntu Impish) Importance: Undecided Assignee: Kellen Renshaw (krenshaw) Status: Confirmed ** Changed in: procps (Ubuntu Bionic) Status: New => Fix Released ** Changed in: procps (Ubuntu Hirsute) Status: New => Fix Released ** Changed in: procps (Ubuntu Impish) Status: Confirmed => Fix Released ** Changed in: procps (Ubuntu Focal) Assignee: (unassigned) => Kellen Renshaw (krenshaw) ** Changed in: procps (Ubuntu Impish) Assignee: Kellen Renshaw (krenshaw) => (unassigned) ** Changed in: procps (Ubuntu Focal) Importance: Undecided => Low ** Description changed: + [Impact] + + + [Test Plan] + + + [Where problems could occur] + + + [Other Info] + + + [Original Description] + From Linux Lint 20.1, so Focal Fossa 20.04.1 Package procps 2:3.3.16-1ubuntu2 $ LANG=C ps --version ps from procps-ng UNKNOWN I don't know if it comes from Ubuntu or upstream. ** Changed in: procps (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1917148 Title: ps version is UNKNOWN in procps 2:3.3.16-1ubuntu2 Status in procps package in Ubuntu: Fix Released Status in procps source package in Bionic: Fix Released Status in procps source package in Focal: Confirmed Status in procps source package in Hirsute: Fix Released Status in procps source package in Impish: Fix Released Bug description: [Impact] [Test Plan] [Where problems could occur] [Other Info] [Original Description] From Linux Lint 20.1, so Focal Fossa 20.04.1 Package procps 2:3.3.16-1ubuntu2 $ LANG=C ps --version ps from procps-ng UNKNOWN I don't know if it comes from Ubuntu or upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1917148/+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 1943053] [NEW] fernseher wird nach upload nicht mehr erkannt
Public bug reported: fernseher wird nach upload nicht mehr erkannt ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 NonfreeKernelModules: nvidia wl .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Sep 8 17:11:50 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-80-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-81-generic, x86_64: installed nvidia-340, 340.108, 5.4.0-80-generic, x86_64: installed nvidia-340, 340.108, 5.4.0-81-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation G98M [Quadro NVS 160M] [10de:06eb] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G98M [Quadro NVS 160M] [1028:024f] InstallationDate: Installed on 2017-05-13 (1578 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Latitude E6500 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=bcd1ee35-e00c-4690-9976-68edba31a164 ro plymouth:debug drm.debug=0xe SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.asset.tag: NB000272 dmi.board.vendor: Dell Inc. dmi.chassis.asset.tag: NB000272 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd10/30/2009:svnDellInc.:pnLatitudeE6500:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude E6500 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Wed Sep 8 17:06:29 2021 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.11-1ubuntu1~20.04.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1943053 Title: fernseher wird nach upload nicht mehr erkannt Status in xorg package in Ubuntu: New Bug description: fernseher wird nach upload nicht mehr erkannt ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 NonfreeKernelModules: nvidia wl .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Sep 8 17:11:50 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-80-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-81-generic, x86_64: installed nvidia-340, 340.108, 5.4.0-80-generic, x86_64: installed nvidia-340, 340.108, 5.4.0-81-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation G98M [Quadro NVS 160M] [10de:06eb] (rev a1) (prog-if 00 [VGA controller]) Subsystem: De
[Touch-packages] [Bug 1889010] Re: [Inspiron 5482, Realtek ALC3204, Black Headphone Out, Front] Playback problem
I've done instructions on #3, but that did not solve the problem. My computer is a Dell Inspiron 14 3480 with latest Ubuntu 20.04.3 ~$ cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC3204 Codec: Intel Kabylake HDMI -- 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/1889010 Title: [Inspiron 5482, Realtek ALC3204, Black Headphone Out, Front] Playback problem Status in alsa-driver package in Ubuntu: Confirmed Bug description: I'm unable to play sound through the headphone jack on this laptop. When I try to play a wav with aplay (e.g. aplay /usr/share/sounds/speech-dispatcher/test.wav) the level indicators in pavucontrol fluctuate, but no sound results. Adjusting the volume does not help. Also, when the headphones are plugged in, I cannot play sound through the internal speakers by selecting the "Speakers" port in pavucontrol Output Devices. With the headphones unplugged, the internal speakers work fine. I tested the Ubuntu 19.10 live USB and I am able to play sound through the headphones without doing anything special (plug in headphones, select "Headphones" from the popup that appears, and use aplay as above), so the hardware itself is apparently okay. The headphones do not work when booting the Ubuntu 20.04 live USB. The problem may be intermittent as I seem to recall I have been able to use the headphones since upgrading to 20.04, but I am not sure of my recollection. I also think that in some of my tests, I was able to play sound through the speakers with the headphones plugged in (by selecting Speakers in pavucontrol) but I cannot reproduce this now. Happy to provide more information, try troubleshooting ideas, etc. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nate 2549 F pulseaudio CasperMD5CheckResult: skip Date: Sun Jul 26 14:20:31 2020 InstallationDate: Installed on 2019-06-03 (419 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_Type: Only some of outputs are working Title: [Inspiron 5482, Realtek ALC3204, Black Headphone Out, Front] Playback problem UpgradeStatus: Upgraded to focal on 2020-06-14 (42 days ago) dmi.bios.date: 07/02/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0G7VYP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/02/2019:svnDellInc.:pnInspiron5482:pvr:rvnDellInc.:rn0G7VYP:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5482 dmi.product.sku: 089E dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1889010/+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 1889010] Re: [Inspiron 5482, Realtek ALC3204, Black Headphone Out, Front] Playback problem
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1889010 Title: [Inspiron 5482, Realtek ALC3204, Black Headphone Out, Front] Playback problem Status in alsa-driver package in Ubuntu: Confirmed Bug description: I'm unable to play sound through the headphone jack on this laptop. When I try to play a wav with aplay (e.g. aplay /usr/share/sounds/speech-dispatcher/test.wav) the level indicators in pavucontrol fluctuate, but no sound results. Adjusting the volume does not help. Also, when the headphones are plugged in, I cannot play sound through the internal speakers by selecting the "Speakers" port in pavucontrol Output Devices. With the headphones unplugged, the internal speakers work fine. I tested the Ubuntu 19.10 live USB and I am able to play sound through the headphones without doing anything special (plug in headphones, select "Headphones" from the popup that appears, and use aplay as above), so the hardware itself is apparently okay. The headphones do not work when booting the Ubuntu 20.04 live USB. The problem may be intermittent as I seem to recall I have been able to use the headphones since upgrading to 20.04, but I am not sure of my recollection. I also think that in some of my tests, I was able to play sound through the speakers with the headphones plugged in (by selecting Speakers in pavucontrol) but I cannot reproduce this now. Happy to provide more information, try troubleshooting ideas, etc. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nate 2549 F pulseaudio CasperMD5CheckResult: skip Date: Sun Jul 26 14:20:31 2020 InstallationDate: Installed on 2019-06-03 (419 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_Type: Only some of outputs are working Title: [Inspiron 5482, Realtek ALC3204, Black Headphone Out, Front] Playback problem UpgradeStatus: Upgraded to focal on 2020-06-14 (42 days ago) dmi.bios.date: 07/02/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0G7VYP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/02/2019:svnDellInc.:pnInspiron5482:pvr:rvnDellInc.:rn0G7VYP:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5482 dmi.product.sku: 089E dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1889010/+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 1917148] Re: ps version is UNKNOWN in procps 2:3.3.16-1ubuntu2
I'll be reviewing the change with my colleague Kellen. In the meanwhile ... What is the concern/impact behind not having the version available in ps ? (Outside it should output/report it) ? The version can be found in the package version (dpkg -l procps) Is it for integrity purposes in order to make sure the ps binary in place really comes from that given procps package ? If it is the case, making --version works won't help much as an integrity check. There are other approaches that can be used to achieve this goal such as 'dpkg '-- verify' and '--audit' To summarize, I'm trying to find the rationale behind it to clearly document the bug when we'll reach the SRU approval/justification. Eric -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1917148 Title: ps version is UNKNOWN in procps 2:3.3.16-1ubuntu2 Status in procps package in Ubuntu: Confirmed Bug description: From Linux Lint 20.1, so Focal Fossa 20.04.1 Package procps 2:3.3.16-1ubuntu2 $ LANG=C ps --version ps from procps-ng UNKNOWN I don't know if it comes from Ubuntu or upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1917148/+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 1939861] Re: dpdk: ppc64el autopkgtest regressed in release
Test built the test-modified version and uploaded to Hirsute-unapproved -- 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/1939861 Title: dpdk: ppc64el autopkgtest regressed in release Status in dpdk package in Ubuntu: Fix Released Status in glibc package in Ubuntu: Invalid Status in pexpect package in Ubuntu: Invalid Status in util-linux package in Ubuntu: Invalid Status in zlib package in Ubuntu: Invalid Status in dpdk source package in Hirsute: Triaged Bug description: [Impact] * Some tests (just a small portion of a vast list of tests) is not really breaking due to real issues but just happen to be notorious timeouts or flaky in the Ubuntu build&test environment. * We have fixed that in Debian and Impish already, but the same behavior now also affects the MRE of 20.11.3 therefore backport the same test improvements to Hirsute. [Test Plan] * Build time and autopkgtests are supposed to work (they are anyway for an SRU, but for this fix this is exactly the test that we want/need to do) [Where problems could occur] * If the patches would be wrong they could have broken the tests, but that would then just not build and thereby not migrate. OTOH there is theoretical chance that the few disabled tests would have catched something down the road which they now no more do - but that isn't that much of a regression, more a trade-off that we want to make. [Other Info] * This initially only affected impish, but later it was found that Hirsute is affected as well. Therefore on this MRE we want to improve it here as well. * To be clear this really is flaky, we could have just hit retry a few times and get through without - but I think we agree that flaky tests are not really helpful and can cause a lot of pain. --- dpkg's autopkgtest on ppc64el has regressed in release [1]. This currently blocks pexpect/8.0-2ubuntu1 from migrating to -release. [1] https://autopkgtest.ubuntu.com/packages/dpdk/impish/ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1939861/+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 1943037] [NEW] Automounts do not reset properly after TimeoutIdleSec automatic unmounts
Public bug reported: Ubuntu version: Ubuntu 20.04.3 LTS systemd version: 245.4-4ubuntu3.11 Expected behavior: Automount units whose associated mount units have been auto-unmounted with TimeoutIdleSec will trigger the associated mount unit when the automount path is accessed again Current behavior: Automount units whose associated mount units have been auto-unmounted with TimeoutIdleSec do not trigger the associated mount unit when the automount path is accessed again until the automount unit is completely restarted. Steps to reproduce the problem 1. Trigger any automount unit with TimeoutIdleSec= set 2- Wait for the idle time to occur and systemd to unmount the associated mount unit 3. Then try to access the automount location again. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1943037 Title: Automounts do not reset properly after TimeoutIdleSec automatic unmounts Status in systemd package in Ubuntu: New Bug description: Ubuntu version: Ubuntu 20.04.3 LTS systemd version: 245.4-4ubuntu3.11 Expected behavior: Automount units whose associated mount units have been auto-unmounted with TimeoutIdleSec will trigger the associated mount unit when the automount path is accessed again Current behavior: Automount units whose associated mount units have been auto-unmounted with TimeoutIdleSec do not trigger the associated mount unit when the automount path is accessed again until the automount unit is completely restarted. Steps to reproduce the problem 1. Trigger any automount unit with TimeoutIdleSec= set 2- Wait for the idle time to occur and systemd to unmount the associated mount unit 3. Then try to access the automount location again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1943037/+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 1943025] Re: Touch pad
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1943025 Title: Touch pad Status in xorg package in Ubuntu: New Bug description: Hi ! I have a little problem with my Touch pad. When i'm going to the applications page and that i do anything, suddenly i can't scroll. When i run xinput list i see that touchpad is in DLL and not in Synaptics maybe it's the problem or not, it's like that i'm doing this report. Thank you for the help ! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 8 11:54:45 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fb] InstallationDate: Installed on 2021-09-07 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. Inspiron 5301 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=45878a68-e793-429d-a95b-fc468f5a9ba3 ro quiet splash i8042.reset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2020 dmi.bios.release: 1.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0R29K5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd10/27/2020:br1.3:svnDellInc.:pnInspiron5301:pvr:sku09FB:rvnDellInc.:rn0R29K5:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5301 dmi.product.sku: 09FB dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1943025/+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 1943025] [NEW] Touch pad
You have been subscribed to a public bug: Hi ! I have a little problem with my Touch pad. When i'm going to the applications page and that i do anything, suddenly i can't scroll. When i run xinput list i see that touchpad is in DLL and not in Synaptics maybe it's the problem or not, it's like that i'm doing this report. Thank you for the help ! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 8 11:54:45 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fb] InstallationDate: Installed on 2021-09-07 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. Inspiron 5301 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=45878a68-e793-429d-a95b-fc468f5a9ba3 ro quiet splash i8042.reset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2020 dmi.bios.release: 1.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0R29K5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd10/27/2020:br1.3:svnDellInc.:pnInspiron5301:pvr:sku09FB:rvnDellInc.:rn0R29K5:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5301 dmi.product.sku: 09FB dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ubuntu -- Touch pad https://bugs.launchpad.net/bugs/1943025 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783987] Re: German Neo2 Problem with Xubuntu 18.04 (try out mode)
Had the same issue in Ubuntu 20.04. I plugged in a keyboard with a Numlock key and switch that off. That fixed it for me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1783987 Title: German Neo2 Problem with Xubuntu 18.04 (try out mode) Status in xkeyboard-config: Unknown Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: When trying Xubuntu 18.04 Bionic Beaver from a USB Stick, I am offered the Neo2 Keyboard Layout, but it does not work. What I get is apparently Neo2 Mod4, but not Mod 1, as it should be. I wonder if Neo2 does work if I install 18.04 properly? To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1783987/+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 1935051] Re: systemd pid 1 memory leak
@brian-murray Hi. Tested that build, all seems fine, still no memory
leak.
# apt-cache policy systemd
systemd:
Installed: 245.4-4ubuntu3.13
Candidate: 245.4-4ubuntu3.13
Version table:
*** 245.4-4ubuntu3.13 500
500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages
100 /var/lib/dpkg/status
Test was performed like i was describe at original post, i run chef-
client and it start checking for all .service and .timers units, and it
cause memory leak, after upgrade no mem leak.
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1935051
Title:
systemd pid 1 memory leak
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
Fix Committed
Bug description:
[impact]
pid1 leaks memory when rebuilding unit path cache
[test case]
see original description.
also, the patch contains an example of how to reproduce:
$ for i in {1..300}; do cp ~/.config/systemd/user/test0001.service
~/.config/systemd/user/test$(printf %04d $i).service; systemctl --user
start test$(printf %04d $i).service;done
[regression]
any problems would occur when rebuilding the path cache, possibly
resulting in memory leaks or pid1 crashes.
[scope]
this is needed only in f
fixed upstream by 3fb2326f3ed87aa0b26078d307ebfb299e36286d which is
included in v246, so fixed in h and later
the code in b is very different and doesn't appear to have the leak,
per original report
[original description]
Hi everybody.
We've meet a memory leak of pid1 process on the focal release.
When we launch chef-client, several systemd .service and .timers are checked
for state.
Every time of this run pid1 increase VSZ/RSS on ~ 232 Kb, this don't happen
on xenial and bionic releases.
I straced pid1 when that leak happen and found brk call.
On pmap view of pid 1 it's anon memory grow on the same address and all
marked as dirty.
All that leak memory can be freed by calling systemctl daemon-reexec.
Searching in systemd github repo i found this commit
https://github.com/systemd/systemd/commit/3fb2326f3ed87aa0b26078d307ebfb299e36286d
- it may be related to this leak.
Environment:
Distributor ID: Ubuntu
Description:Ubuntu 20.04.2 LTS
Release:20.04
Codename: focal
Uname: 5.4.0-77-generic #83-Ubuntu SMP Sat May 8 02:35:39 UTC 2021
x86_64
Package:
systemd:
Installed: 245.4-4ubuntu3.7
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1935051/+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 1939973] Re: make 4.3-4.1 triggers build failures
Building cross-toolchain-base in ppa:xypron/merge-from-debian did not show the described failure. How can it be reproduced? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to make-dfsg in Ubuntu. https://bugs.launchpad.net/bugs/1939973 Title: make 4.3-4.1 triggers build failures Status in make-dfsg package in Ubuntu: Confirmed Status in make-dfsg source package in Impish: Confirmed Bug description: trying to rebuild cross-toolchain-base from https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/volatile/+packages triggers a build failure: [...] START stamp-dir/init-binutils tar -x -f /usr/src/binutils/binutils-2.37.tar.xz set -e; cd binutils-2.37 ; cp -a /usr/src/binutils/debian/ . ; if [ -n "$(grep -v '^\#' /<>/debian/patches/binutils/series)" ]; then QUILT_PATCHES=/<>/debian/patches/binutils quilt --quiltrc /dev/null push -a; fi; rm -rf .pc cd binutils-2.37 ; env -i CROSS_ARCHS="amd64 i386 s390x ppc64el arm64 armhf armel powerpc" debian/rules stamps/control make: dpkg-architecture: No such file or directory make: lsb_release: No such file or directory make: lsb_release: No such file or directory make: pwd: No such file or directory make: dpkg-parsechangelog: No such file or directory make: dpkg-parsechangelog: No such file or directory make: dpkg-parsechangelog: No such file or directory make: dpkg-parsechangelog: No such file or directory debian/rules:163: *** unexpected source package name: . Stop. make: *** [debian/rules:215: stamp-dir/init-binutils] Error 2 dpkg-buildpackage.pl: error: debian/rules build subprocess returned exit status 2 working around by omitting the -i option to env, or by setting PATH explicitly. Reverting to the version in the release pocket lets the c-t-b- build succeed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/make-dfsg/+bug/1939973/+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 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Tags added: rls-ii-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Invalid Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Incomplete Status in gnome-shell source package in Focal: Invalid Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Incomplete Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Incomplete Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Incomplete Status in gnome-shell source package in Impish: Invalid Bug description: This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=> Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request repeated too quickly. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53 But that already was only triggered by a gnome restart that kicked of earlier: Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session is initialized. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland Session. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session (session: gnome-login). X was recycleing before: Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11... ... Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) systemd-logind: ReleaseControl failed: Unknown object '/org/freedesktop/login1/session/_32'. Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server terminated successfully (0). Closing log file. It seems like some internal service broke and everything that followed was a secondary issue to that: Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeiche
[Touch-packages] [Bug 1939861] Re: dpdk: ppc64el autopkgtest regressed in release
** Description changed: + [Impact] + + * Some tests (just a small portion of a vast list of tests) is not really +breaking due to real issues but just happen to be notorious timeouts +or flaky in the Ubuntu build&test environment. + + * We have fixed that in Debian and Impish already, but the same behavior +now also affects the MRE of 20.11.3 therefore backport the same test +improvements to Hirsute. + + [Test Plan] + + * Build time and autopkgtests are supposed to work (they are anyway for +an SRU, but for this fix this is exactly the test that we want/need +to do) + + [Where problems could occur] + + * If the patches would be wrong they could have broken the tests, but +that would then just not build and thereby not migrate. OTOH there is +theoretical chance that the few disabled tests would have catched +something down the road which they now no more do - but that isn't +that much of a regression, more a trade-off that we want to make. + + [Other Info] + + * This initially only affected impish, but later it was found that +Hirsute is affected as well. Therefore on this MRE we want to improve +it here as well. + * To be clear this really is flaky, we could have just hit retry a few +times and get through without - but I think we agree that flaky tests +are not really helpful and can cause a lot of pain. + + --- + dpkg's autopkgtest on ppc64el has regressed in release [1]. This currently blocks pexpect/8.0-2ubuntu1 from migrating to -release. - [1] https://autopkgtest.ubuntu.com/packages/dpdk/impish/ppc64el ** Also affects: util-linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: glibc (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: pexpect (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: zlib (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: dpdk (Ubuntu Hirsute) Importance: Undecided Status: New ** No longer affects: glibc (Ubuntu Hirsute) ** No longer affects: pexpect (Ubuntu Hirsute) ** No longer affects: util-linux (Ubuntu Hirsute) ** No longer affects: zlib (Ubuntu Hirsute) ** Changed in: dpdk (Ubuntu Hirsute) Status: New => Triaged -- 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/1939861 Title: dpdk: ppc64el autopkgtest regressed in release Status in dpdk package in Ubuntu: Fix Released Status in glibc package in Ubuntu: Invalid Status in pexpect package in Ubuntu: Invalid Status in util-linux package in Ubuntu: Invalid Status in zlib package in Ubuntu: Invalid Status in dpdk source package in Hirsute: Triaged Bug description: [Impact] * Some tests (just a small portion of a vast list of tests) is not really breaking due to real issues but just happen to be notorious timeouts or flaky in the Ubuntu build&test environment. * We have fixed that in Debian and Impish already, but the same behavior now also affects the MRE of 20.11.3 therefore backport the same test improvements to Hirsute. [Test Plan] * Build time and autopkgtests are supposed to work (they are anyway for an SRU, but for this fix this is exactly the test that we want/need to do) [Where problems could occur] * If the patches would be wrong they could have broken the tests, but that would then just not build and thereby not migrate. OTOH there is theoretical chance that the few disabled tests would have catched something down the road which they now no more do - but that isn't that much of a regression, more a trade-off that we want to make. [Other Info] * This initially only affected impish, but later it was found that Hirsute is affected as well. Therefore on this MRE we want to improve it here as well. * To be clear this really is flaky, we could have just hit retry a few times and get through without - but I think we agree that flaky tests are not really helpful and can cause a lot of pain. --- dpkg's autopkgtest on ppc64el has regressed in release [1]. This currently blocks pexpect/8.0-2ubuntu1 from migrating to -release. [1] https://autopkgtest.ubuntu.com/packages/dpdk/impish/ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1939861/+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
