[Touch-packages] [Bug 1955388] [NEW] Sound problem after changing the desktop enviroment to KDE Plasma
Public bug reported: after installing Ubuntu 20.04 and changing its desktop environment from its default to KDE Plasma my sound card stopped from begin working, although I did some modifications bu it didn't work. my system info is: Card: HDA Interl PCH Chip: Realtek ALC3235 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 20 10:55:08 2021 InstallationDate: Installed on 2021-12-07 (12 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2016 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.3 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.3:bd11/09/2016:br1.11:svnDellInc.:pnLatitudeE7470:pvr:sku06DC:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Latitude dmi.product.name: Latitude E7470 dmi.product.sku: 06DC dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-12-14T11:09:06.124726 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages wayland-session -- 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/1955388 Title: Sound problem after changing the desktop enviroment to KDE Plasma Status in alsa-driver package in Ubuntu: New Bug description: after installing Ubuntu 20.04 and changing its desktop environment from its default to KDE Plasma my sound card stopped from begin working, although I did some modifications bu it didn't work. my system info is: Card: HDA Interl PCH Chip: Realtek ALC3235 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 20 10:55:08 2021 InstallationDate: Installed on 2021-12-07 (12 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2016 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.3 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.3:bd11/09/2016:br1.11:svnDellInc.:pnLatitudeE7470:pvr:sku06DC:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Latitude dmi.product.name: Latitude E7470 dmi.product.sku: 06DC dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-12-14T11:09:06.124726 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1955388/+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 1940377] Re: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute.
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Low ** Changed in: oem-priority Importance: Low => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1940377 Title: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute. Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Confirmed Status in usb-modeswitch package in Ubuntu: Confirmed Bug description: u@u-ThinkPad-L460:~$ uname -a Linux u-ThinkPad-L460 Kernel 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux u@u-ThinkPad-L460:~$ cat /etc/issue Ubuntu 21.04 \n \l CPU : Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz WWAN : 12d1:15c1 Huawei Technologies Co., Ltd. ME906s LTE M.2 Module [Steps] 1. Make a Live CD for Ubuntu Hirsute 2. Plug in the Live CD 3. Boot ThinkPad L460 4. Install Ubuntu Hirsute and completed all configurations 5. Make sure the installation done 6. Boot the system and log in 7. Enable the proposed channel 8. Do the update and upgrade 9. Reboot the system and check mmcli is upgraded to 1.16.6 7. Verify the WWAN working or not. [Actual result] The WWAN can not be detected. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.16 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu Date: Wed Aug 18 01:32:17 2021 InstallationDate: Installed on 2021-08-18 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-08-18 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) IpRoute: default via 10.1.1.1 dev wlp3s0 proto dhcp metric 600 10.1.1.0/24 dev wlp3s0 proto kernel scope link src 10.1.1.106 metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.30.0-1ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Tags: hirsute Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1940377/+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 1955384] [NEW] Xorg freeze
Public bug reported: This bug happened when I clicked and held the left mouse button on the desktop and moved it to make a rectangular selection window. Next, I moved the window to highlight 4 desktop shortcuts on my desktop (Middle- earth Shadow of Mordor.desktop, steam.desktop, Trash, and the icelancet or Home folder). Next, while still holding the left mouse button down, I pressed and released the right mouse button. Now a window pops up with more options, however, the window is not removable using a normal method like clicking somewhere else on the desktop or even choosing an option in the window which does nothing. Also, it introduces more bugs like: 1. clicking the icelancet/Home shortcut on the desktop does not open the Home folder, or 2. while clicking the Home folder shortcut on the sidebar does open the Home folder, this window is not moveable by the usual method of pressing down the left mouse button on the title bar of the window and moving the mouse. As such, when this bug occurs, a hard reboot is necessary to restore the stability of the system. I have reproduced the bug after a reboot and doing the same procedure - the same thing happens. This is on the latest version of Ubuntu (Release 20.04) with all the latest upstream updates installed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.94 Mon Dec 6 22:42:02 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 20 00:46:44 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:862a] InstallationDate: Installed on 2021-11-23 (27 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Micro-Star International Co., Ltd. MS-7C39 ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-43-generic root=UUID=d206716a-6a84-411d-9038-eb4654efc2ec ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.10 dmi.board.asset.tag: Default string dmi.board.name: B365M PRO-VDH(MS-7C39) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.10:bd09/05/2019:br5.12:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C39:pvr1.0:skuDefaultstring:rvnMicro-StarInternationalCo.,Ltd.:rnB365MPRO-VDH(MS-7C39):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7C39 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal possible-manual-nvidia-install 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/1955384 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: This bug happened when I clicked and held the left mouse bu
[Touch-packages] [Bug 1955349] [NEW] /usr/lib/x86_64-linux-gnu/libtinfo.so: error: undefined reference to 'stat', version 'GLIBC_2.33'
Public bug reported: Error compiling ncurses bindings for kotlin-native. Full details here: https://github.com/reubenfirmin/lucifer/pull/1 ...but I think this is probably self explanatory. This is on Ubuntu 21.10. /usr/lib/x86_64-linux-gnu/libtinfo.so: error: undefined reference to 'stat', version 'GLIBC_2.33' ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: libtinfo6 6.2+20201114-2build1 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sun Dec 19 13:32:51 2021 InstallationDate: Installed on 2021-12-16 (3 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: ncurses UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ncurses (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ncurses in Ubuntu. https://bugs.launchpad.net/bugs/1955349 Title: /usr/lib/x86_64-linux-gnu/libtinfo.so: error: undefined reference to 'stat', version 'GLIBC_2.33' Status in ncurses package in Ubuntu: New Bug description: Error compiling ncurses bindings for kotlin-native. Full details here: https://github.com/reubenfirmin/lucifer/pull/1 ...but I think this is probably self explanatory. This is on Ubuntu 21.10. /usr/lib/x86_64-linux-gnu/libtinfo.so: error: undefined reference to 'stat', version 'GLIBC_2.33' ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: libtinfo6 6.2+20201114-2build1 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sun Dec 19 13:32:51 2021 InstallationDate: Installed on 2021-12-16 (3 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: ncurses UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/1955349/+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 1950193] Re: libqt5svg5 affected by CVE-2021-38593
Tested in an Impish chroot: root@mitya57:/test# time ./test-2021-38593 ./input.svg Testing for CVE-2021-38593... If the test doesn't finish immediately, you probably are affected. Test finished. real0m0.033s user0m0.004s sys 0m0.017s root@mitya57:/test# echo $? 0 root@mitya57:/test# apt policy libqt5gui5 libqt5gui5: Installed: 5.15.2+dfsg-12ubuntu1 Candidate: 5.15.2+dfsg-12ubuntu1 Version table: *** 5.15.2+dfsg-12ubuntu1 500 500 http://archive.ubuntu.com/ubuntu impish-proposed/universe amd64 Packages 100 /var/lib/dpkg/status 5.15.2+dfsg-12 500 500 http://archive.ubuntu.com/ubuntu impish/universe amd64 Packages With the version from release pocket, the test program does not finish after 30 seconds. ** Tags removed: verification-needed verification-needed-impish ** Tags added: verification-done verification-done-impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1950193 Title: libqt5svg5 affected by CVE-2021-38593 Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Focal: Fix Committed Status in qtbase-opensource-src source package in Impish: Fix Committed Bug description: [Impact] libqt5svg5 5.12.8-0ubuntu1 in Ubuntu 20.04 is affected by CVE-2021-38593: https://nvd.nist.gov/vuln/detail/CVE-2021-38593 Trying to open the attached svg file will block one core at 100% and occupy much memory. Depending on the configuration, it might even run out of memory and crash. This is fixed upstream by: https://codereview.qt-project.org/c/qt/qtbase/+/377942 The original issue is public since July 29th. [Test Plan] 1. Install libqt5svg5-dev, qtbase5-dev and their dependencies. 2. Build the attached project with the system's version of Qt: /usr/lib/qt5/bin/qmake test-2021-38593.pro && make 3. Start the resulting binary and pass the path to the included input file as first parameter: ./test-2021-38593 ./input.svg The binary should return immediately and without error messages. If it doesn't, you might be affected. [Where problems could occur] The fix tries to skip drawing dashes that would be invisible anyway. So a potential problem may that it skips too much. In fact, this has already happened, and upstream had to adjust the fix. [Other Info] The patch is a combination of the following upstream commits: - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=7f345f2a1c8d9f60 - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=9378ba2ae857df7e - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=81998f50d039a631 - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=cca8ed0547405b1c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1950193/+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 1955347] [NEW] rsync works bad with encfs now
Public bug reported:
Hello,
I think rsync works bad with encfs now.
When root uses it, rsync cannot read a directory encrypted with encfs by
a user. More precisely, it cannot read the mounted directory, the
virtual one where the user can read the datas.
Until now there was only a warning like this
"rsync: readlink_stat("/home/claude/Documents_chiffres") failed:
Permission denied (13)"
and the software went on working (only ignoring the content of the mounted
directory and of course without saving this content)
But recently there is this more:
"IO error encountered -- skipping file deletion"
and because of this "skipping file deletion", the software can't work normally.
The destination gets bigger more and more because the deleted files in the
source are not deleted in the destination.
Thanks for reading me.
rsync 3.1.3-8ubuntu0.1
Description:Ubuntu 20.04.3 LTS
Release:20.04
** Affects: rsync (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1955347
Title:
rsync works bad with encfs now
Status in rsync package in Ubuntu:
New
Bug description:
Hello,
I think rsync works bad with encfs now.
When root uses it, rsync cannot read a directory encrypted with encfs
by a user. More precisely, it cannot read the mounted directory, the
virtual one where the user can read the datas.
Until now there was only a warning like this
"rsync: readlink_stat("/home/claude/Documents_chiffres") failed:
Permission denied (13)"
and the software went on working (only ignoring the content of the mounted
directory and of course without saving this content)
But recently there is this more:
"IO error encountered -- skipping file deletion"
and because of this "skipping file deletion", the software can't work
normally. The destination gets bigger more and more because the deleted files
in the source are not deleted in the destination.
Thanks for reading me.
rsync 3.1.3-8ubuntu0.1
Description:Ubuntu 20.04.3 LTS
Release:20.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1955347/+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 1953065] Re: 2.13.0 FTBFS
Fix was merged usptream, and 2.13.1 contains it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ust in Ubuntu.
https://bugs.launchpad.net/bugs/1953065
Title:
2.13.0 FTBFS
Status in LTTng-UST:
Unknown
Status in ust package in Ubuntu:
In Progress
Bug description:
I tried to merge ust from debian into ubuntu, to fix a build-time
dependency, but stumbled on an FTBFS with that version.
I filed upstream bug at https://bugs.lttng.org/issues/1337
It basically happens in some new test cases that were added in 2.13.0
and crash when we build it using our default -Wl,-Bsymbolic-flags
linker option, which we have been using for years in Ubuntu.
Here is the testsuite log output:
lttng-ust 2.14.0-pre: tests/test-suite.log
# TOTAL: 246
# PASS: 241
# SKIP: 0
# XFAIL: 0
# FAIL: 4
# XPASS: 0
# ERROR: 1
.. contents:: :depth: 2
ERROR: regression/abi0-conflict/test_abi0_conflict
==
1..22
# LD_PRELOAD
# regression/abi0-conflict/test_abi0_conflict: LD_PRELOAD
ok 1 - LD_PRELOAD: no-ust app works
PASS: regression/abi0-conflict/test_abi0_conflict 1 - LD_PRELOAD: no-ust app
works
ok 2 - LD_PRELOAD: no-ust app with abi0 preload succeeds
PASS: regression/abi0-conflict/test_abi0_conflict 2 - LD_PRELOAD: no-ust app
with abi0 preload succeeds
./regression/abi0-conflict/test_abi0_conflict: line 56: 592651 Aborted
(core dumped) LD_PRELOAD="${LIBFAKEUST0}:${LIBUST1}"
"${CURDIR}/app_noust" > "$STD_OUTPUT" 2> "$STD_ERROR"
ok 3 - LD_PRELOAD: no-ust app with abi0 and abi1 preload fails
PASS: regression/abi0-conflict/test_abi0_conflict 3 - LD_PRELOAD: no-ust app
with abi0 and abi1 preload fails
./regression/abi0-conflict/test_abi0_conflict: line 59: 592652 Aborted
(core dumped) LD_PRELOAD="${LIBUST1}:${LIBFAKEUST0}"
"${CURDIR}/app_noust" > "$STD_OUTPUT" 2> "$STD_ERROR"
ok 4 - LD_PRELOAD: no-ust app with abi1 and abi0 preload fails
PASS: regression/abi0-conflict/test_abi0_conflict 4 - LD_PRELOAD: no-ust app
with abi1 and abi0 preload fails
ok 5 - LD_PRELOAD: ust app works
PASS: regression/abi0-conflict/test_abi0_conflict 5 - LD_PRELOAD: ust app
works
./regression/abi0-conflict/test_abi0_conflict: line 68: 592669 Aborted
(core dumped) LD_PRELOAD="${LIBFAKEUST0}" "${CURDIR}/app_ust" >
"$STD_OUTPUT" 2> "$STD_ERROR"
ok 6 - LD_PRELOAD: ust app with abi0 preload fails
PASS: regression/abi0-conflict/test_abi0_conflict 6 - LD_PRELOAD: ust app
with abi0 preload fails
./regression/abi0-conflict/test_abi0_conflict: line 71: 592683 Aborted
(core dumped) LD_PRELOAD="${LIBFAKEUST0}:${LIBUST1}"
"${CURDIR}/app_ust" > "$STD_OUTPUT" 2> "$STD_ERROR"
ok 7 - LD_PRELOAD: ust app with abi0 and abi1 preload fails
PASS: regression/abi0-conflict/test_abi0_conflict 7 - LD_PRELOAD: ust app
with abi0 and abi1 preload fails
./regression/abi0-conflict/test_abi0_conflict: line 74: 592684 Aborted
(core dumped) LD_PRELOAD="${LIBUST1}:${LIBFAKEUST0}"
"${CURDIR}/app_ust" > "$STD_OUTPUT" 2> "$STD_ERROR"
ok 8 - LD_PRELOAD: ust app with abi1 and abi0 preload fails
PASS: regression/abi0-conflict/test_abi0_conflict 8 - LD_PRELOAD: ust app
with abi1 and abi0 preload fails
# dlopen
# regression/abi0-conflict/test_abi0_conflict: dlopen
ok 9 - dlopen: no-ust app works
PASS: regression/abi0-conflict/test_abi0_conflict 9 - dlopen: no-ust app works
ok 10 - dlopen: no-ust app with abi1 and abi1 succeeds
PASS: regression/abi0-conflict/test_abi0_conflict 10 - dlopen: no-ust app
with abi1 and abi1 succeeds
./regression/abi0-conflict/test_abi0_conflict: line 92: 592689 Aborted
(core dumped) LD_LIBRARY_PATH="$LIBFAKEUST0_PATH:$LIBUST1_PATH"
"${CURDIR}/app_noust_dlopen" abi0_abi1 > "$STD_OUTPUT" 2> "$STD_ERROR"
ok 11 - dlopen: no-ust app with abi0 and abi1 fails
PASS: regression/abi0-conflict/test_abi0_conflict 11 - dlopen: no-ust app
with abi0 and abi1 fails
not ok 12 - dlopen: no-ust app with abi1 and abi0 fails
FAIL: regression/abi0-conflict/test_abi0_conflict 12 - dlopen: no-ust app
with abi1 and abi0 fails
# Failed test 'dlopen: no-ust app with abi1 and abi0 fails'
# regression/abi0-conflict/test_abi0_conflict: Failed test 'dlopen: no-ust
app with abi1 and abi0 fails'
# in /home/ubuntu/git/packages/ust/lttng-ust/tests/utils/tap.sh:isnt() at
line 300.
# regression/abi0-conflict/test_abi0_conflict: in
/home/ubuntu/git/packages/ust/lttng-ust/tests/utils/tap.sh:isnt() at line 300.
# got: '0'
# regression/abi0-conflict/test_abi0_conflict: got: '0'
# expected: '0'
# regression/abi0-conflict/test_abi0_conflict: expected: '0'
ok 13 - dlopen: ust app works
PASS: regression/abi0-conflict/test_abi0_conflic
[Touch-packages] [Bug 1938065] Re: systemd 248.3-1ubuntu2 fails to install (when upgrading 21.04->21.10)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1938065 Title: systemd 248.3-1ubuntu2 fails to install (when upgrading 21.04->21.10) Status in systemd package in Ubuntu: Confirmed Bug description: This happened when trying to upgrade from 21.04 to 21.10. Setting up systemd (248.3-1ubuntu2) ... systemd-machine-id-setup: error while loading shared libraries: libsystemd-shared-247.so: cannot open shared object file: No such file or directory dpkg: error processing package systemd (--configure): installed systemd package post-installation script subprocess returned error exit status 127 Processing triggers for initramfs-tools (0.140ubuntu6) ... update-initramfs: Generating /boot/initrd.img-5.11.0-25-generic Processing triggers for libc-bin (2.33-0ubuntu7) ... Processing triggers for man-db (2.9.4-2) ... Processing triggers for dbus (1.12.20-2ubuntu1) ... Errors were encountered while processing: systemd I reverted to old version by manualing installing the hirsute's debs (from 21.04: libsystemd0_247.3-3ubuntu3.4_i386.deb systemd_247.3-3ubuntu3.4_amd64.deb libnss- systemd_247.3-3ubuntu3.4_amd64.deb libsystemd- dev_247.3-3ubuntu3.4_amd64.deb systemd-sysv_247.3-3ubuntu3.4_amd64.deb libpam-systemd_247.3-3ubuntu3.4_amd64.deb libudev1_247.3-3ubuntu3.4_amd64.deb udev_247.3-3ubuntu3.4_amd64.deb libsystemd0_247.3-3ubuntu3.4_amd64.deb libudev- dev_247.3-3ubuntu3.4_amd64.deb) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1938065/+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 1955316] Re: Wishlist - Make apport entries copy-able
** Summary changed: - Wishlist - Make apport entires copy-able + Wishlist - Make apport entries copy-able -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1955316 Title: Wishlist - Make apport entries copy-able Status in Apport: New Status in apport package in Ubuntu: New Bug description: Due to previous experiences with other software I'm not comfortable to just send some large unchecked logs. Apparently that might also be an issue with apport, which is why it's disabled by default in Ubuntu- Mater. I'd still like to help with bug-reports by providing the information which I can check easily. Not being able to just copy entries from the gui makes this much more time-consuming then necessary and might result in cases where users provide less information than they would otherwise. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1955316/+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
