[Touch-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
@ajg-charlbury: yes, firefox we are well aware of the problem, the firefox profile has been tweaked for beta3 (landing this week) so that it should work with the new deb. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in AppArmor: New Status in akonadiconsole package in Ubuntu: Fix Released Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Fix Released Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Fix Released Status in evolution package in Ubuntu: Fix Released Status in falkon package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Confirmed Status in freecad package in Ubuntu: Invalid Status in geary package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Invalid Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Fix Released Status in kgeotag package in Ubuntu: Fix Released Status in kiwix package in Ubuntu: Incomplete Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Released Status in kontact package in Ubuntu: Fix Released Status in loupe package in Ubuntu: Confirmed Status in marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Fix Released Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Fix Released Status in plasma-welcome package in Ubuntu: Fix Released Status in privacybrowser package in Ubuntu: Invalid Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Fix Released Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: Fix Released Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+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 2051895] Re: Lenovo XT99 BT headset can't work in HFP profile
Analysis of autpkgtest failure for Mantic (about comment #16): 1) For libopenmpt/0.7.2-1 (i386), it is a building erorr which has nothing to do with pulesaudio: 755s /usr/lib/gcc-cross/i686-linux-gnu/13/../../../../i686-linux-gnu/bin/ld: /tmp/ccQalxLn.o: in function `main': 755s pattern-dump-c.c:(.text+0x458): undefined reference to `openmpt_error_func_default' 755s /usr/lib/gcc-cross/i686-linux-gnu/13/../../../../i686-linux-gnu/bin/ld: pattern-dump-c.c:(.text+0x461): undefined reference to `openmpt_log_func_default' 755s /usr/lib/gcc-cross/i686-linux-gnu/13/../../../../i686-linux-gnu/bin/ld: pattern-dump-c.c:(.text+0x473): undefined reference to `openmpt_module_create2' 755s /usr/lib/gcc-cross/i686-linux-gnu/13/../../../../i686-linux-gnu/bin/ld: pattern-dump-c.c:(.text+0x4be): undefined reference to `openmpt_module_get_num_orders' 755s /usr/lib/gcc-cross/i686-linux-gnu/13/../../../../i686-linux-gnu/bin/ld: pattern-dump-c.c:(.text+0x4f8): undefined reference to `openmpt_module_get_order_pattern' 755s /usr/lib/gcc-cross/i686-linux-gnu/13/../../../../i686-linux-gnu/bin/ld: pattern-dump-c.c:(.text+0x509): undefined reference to `openmpt_module_get_num_channels' 755s /usr/lib/gcc-cross/i686-linux-gnu/13/../../../../i686-linux-gnu/bin/ld: pattern-dump-c.c:(.text+0x544): undefined reference to `openmpt_module_get_pattern_row_channel_command' 755s /usr/lib/gcc-cross/i686-linux-gnu/13/../../../../i686-linux-gnu/bin/ld: pattern-dump-c.c:(.text+0x55f): undefined reference to `openmpt_module_get_pattern_row_channel_command' 755s /usr/lib/gcc-cross/i686-linux-gnu/13/../../../../i686-linux-gnu/bin/ld: pattern-dump-c.c:(.text+0x58e): undefined reference to `openmpt_module_destroy' 755s collect2: error: ld returned 1 exit status 2) For libsdl2/2.28.3+dfsg-2 (i386), it is a buliding error which has nothing to do with pusleaudio: 440s use-ttf.c:7:11: fatal error: SDL_ttf.h: No such file or directory 440s 7 | # include 440s | ^~~ 440s compilation terminated. 440s + rm -rf /tmp/tmp.CcXjR8RPS6 440s autopkgtest [21:27:55]: test deprecated-use: ---] 440s deprecated-use FAIL non-zero exit status 1 3) For pipewire/0.3.79-2 (i386), it is a buliding error which has nothing to do with pusleaudio: 1333s + i686-linux-gnu-gcc -otrivial trivial.c -lm 1333s trivial.c:1:10: fatal error: pipewire/pipewire.h: No such file or directory 1333s 1 | #include 1333s | ^ 1333s compilation terminated. 1333s autopkgtest [21:42:52]: test libpipewire-0.3-dev: ---] 1333s libpipewire-0.3-dev FAIL non-zero exit status 1 So in my opinion, these 3 failure have nothing to do with pulseaudio, probably we should hint them in the tests on i386 enviroment. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2051895 Title: Lenovo XT99 BT headset can't work in HFP profile Status in HWE Next: New Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Jammy: Fix Committed Status in pulseaudio source package in Mantic: Fix Committed Status in pulseaudio source package in Noble: Fix Committed Bug description: [Summary] When use the ThinkPluse xt99 bluetooth head set to run the test com.canonical.certification::bluetooth/audio_record_playback, it cannot record the sound and playback. It seems this device cannot switch to Hand free mode in this platform. [Steps to reproduce] Connect the ThinkPluse xt99, use the Handfree mode, then try to record some voice. [Expected result] The bluetooth headset ThinkPluse xt99 can use as a MIC to input sound. [Actual result] The bluetooth headset xt99 cannot work in the Handfree mode. [Failure rate] 100% [Impact] With the current Ubuntu 22.04 oem image, we try to connect the LENOVO XT99 bt headset and let it work in HFP mode, we select HFP profile from gnome sound-setting, but the microphone will not auto change to bt microphone and the bt output could not work too. So this BT headset could only work in A2DP mode with the current 22.04 OEM image. And we tried ubuntu 22.04 generic image, mantic image and noble image, none of them could make the headset work in HFP mode. [Fix] Cherry-pick a pulseaudio commit from upstream. [Test] I installed ubuntu 22.04 and 23.10 on 2 different Thinkpad laptops, then upgraded the pulseaudio from my ppa (ppa:hui.wang/pa-testing), in theory my change only affects bluetooth audio devices, it will not bring any impact to non-audio bluetooth devices, here I did the test with 7 bluetooth audio devices and 2 non-audio devices: BT audio devices (pairing, connection, re-connection, playback and capture all worked well): PLT_BBTGO2 (headset) Xiaomi Air3 SE (headset) Crusher Wireless (headset) SOAIY S18 (sound box) HK Soho
[Touch-packages] [Bug 2051895] Re: Lenovo XT99 BT headset can't work in HFP profile
Analysis of autpkgtest failure for Jammy (about comment #15): 1) For libsdl2/2.0.20+dfsg-2ubuntu1.22.04.1 (i386), It is a building failure which has nothing to do with the pulseaudio: 275s + i686-linux-gnu-gcc -o use-pkg-config use-ttf.c 275s use-ttf.c:7:11: fatal error: SDL_ttf.h: No such file or directory 275s 7 | # include 275s | ^~~ 275s compilation terminated. 2) For pipewire/0.3.48-1ubuntu3 (i386), it is the gstreamer1.0-pipewire's issue, it doesn't have the plugin libgstpipewire.so: 1170s autopkgtest [21:40:06]: test gstreamer1.0-pipewire: [--- 1170s + export GST_INSPECT_NO_COLORS=1 1170s + export PAGER=cat 1170s + gst-inspect-1.0 pipewire 1170s No such element or plugin 'pipewire' 1170s autopkgtest [21:40:06]: test gstreamer1.0-pipewire: ---] So in my opinion, these 2 failure have nothing to do with pulseaudio, probably we should hint them in the tests on i386 enviroment. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2051895 Title: Lenovo XT99 BT headset can't work in HFP profile Status in HWE Next: New Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Jammy: Fix Committed Status in pulseaudio source package in Mantic: Fix Committed Status in pulseaudio source package in Noble: Fix Committed Bug description: [Summary] When use the ThinkPluse xt99 bluetooth head set to run the test com.canonical.certification::bluetooth/audio_record_playback, it cannot record the sound and playback. It seems this device cannot switch to Hand free mode in this platform. [Steps to reproduce] Connect the ThinkPluse xt99, use the Handfree mode, then try to record some voice. [Expected result] The bluetooth headset ThinkPluse xt99 can use as a MIC to input sound. [Actual result] The bluetooth headset xt99 cannot work in the Handfree mode. [Failure rate] 100% [Impact] With the current Ubuntu 22.04 oem image, we try to connect the LENOVO XT99 bt headset and let it work in HFP mode, we select HFP profile from gnome sound-setting, but the microphone will not auto change to bt microphone and the bt output could not work too. So this BT headset could only work in A2DP mode with the current 22.04 OEM image. And we tried ubuntu 22.04 generic image, mantic image and noble image, none of them could make the headset work in HFP mode. [Fix] Cherry-pick a pulseaudio commit from upstream. [Test] I installed ubuntu 22.04 and 23.10 on 2 different Thinkpad laptops, then upgraded the pulseaudio from my ppa (ppa:hui.wang/pa-testing), in theory my change only affects bluetooth audio devices, it will not bring any impact to non-audio bluetooth devices, here I did the test with 7 bluetooth audio devices and 2 non-audio devices: BT audio devices (pairing, connection, re-connection, playback and capture all worked well): PLT_BBTGO2 (headset) Xiaomi Air3 SE (headset) Crusher Wireless (headset) SOAIY S18 (sound box) HK Soho Wireless (headset) Thinkplus XT99 (headset) Wl-1000X (headset) BT non-audio devices (pairing, connection, re-connection, key input all worked well): BT3.0 Keyboard The Pinao 2 keyboard [Where problems could occur] This change will impact bt headset negotiation process in the pulseaudio, so the possiblity of regression is limited to bt headset, it could make the bt headset fail to connect, but this possibility is very low, we tested the patch with different bt headset and bt speaker, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051895/+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 2058162] [NEW] regression: "pacmd dump" reports incorrect status for muted microphone
Public bug reported: pacmd dump | grep mute The "set-source-mute" for my mic should say "no" when my mic is not muted but it always says "yes" nowadays. This used to work earlier. Broken version: $ apt policy pulseaudio-utils pulseaudio-utils: Installed: 1:15.99.1+dfsg1-1ubuntu2.1 Candidate: 1:15.99.1+dfsg1-1ubuntu2.1 I'm pretty sure at least version 1:11.1-1ubuntu7.11 used to work correctly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio-utils 1:15.99.1+dfsg1-1ubuntu2.1 ProcVersionSignature: Ubuntu 6.5.0-25.25.1~22.04.1-lowlatency 6.5.13 Uname: Linux 6.5.0-25-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Mon Mar 18 01:38:38 2024 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (1898 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: pulseaudio UpgradeStatus: Upgraded to jammy on 2023-08-11 (219 days ago) dmi.bios.date: 10/17/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1505 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-M PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.init.d.apport: [modified] modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.init.d.apport: 2022-05-19T12:50:20.029158 mtime.conffile..etc.pulse.daemon.conf: 2021-11-19T14:33:38.709428 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2058162 Title: regression: "pacmd dump" reports incorrect status for muted microphone Status in pulseaudio package in Ubuntu: New Bug description: pacmd dump | grep mute The "set-source-mute" for my mic should say "no" when my mic is not muted but it always says "yes" nowadays. This used to work earlier. Broken version: $ apt policy pulseaudio-utils pulseaudio-utils: Installed: 1:15.99.1+dfsg1-1ubuntu2.1 Candidate: 1:15.99.1+dfsg1-1ubuntu2.1 I'm pretty sure at least version 1:11.1-1ubuntu7.11 used to work correctly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio-utils 1:15.99.1+dfsg1-1ubuntu2.1 ProcVersionSignature: Ubuntu 6.5.0-25.25.1~22.04.1-lowlatency 6.5.13 Uname: Linux 6.5.0-25-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Mon Mar 18 01:38:38 2024 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (1898 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: pulseaudio UpgradeStatus: Upgraded to jammy on 2023-08-11 (219 days ago) dmi.bios.date: 10/17/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1505 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-M PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.init.d.apport: [modified] modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.init.d.apport: 2022-05-19T12:50:20.029158 mtime.conffile..etc.pulse.daemon.conf: 2021-11-19T14:33:38.709428 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2058162/+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 2058017] Re: openssl is not LTO-safe
** Description changed: tl;dr: since it's too much work to make openssl LTO-safe, upstream doesn't see it as a goal and doesn't test it, and there are probably no performance gains to LTO for this package. Openssl is an old project and the codebase wasn't written with aliasing rules in mind. There are several reports of issues related to LTO. The openssl technical commitee says "currently we're not going to fix all the strict aliasing and other LTO problems" and "Fixes raised in pull requests will be considered."; in other words: if you find a violation, we'll merge your fixes but we're not going to dedicate time to fixing them ourselves. We don't have specific reports on launchpad at the moment but there has been at least one issue experienced by the FIPS: the compiler decided a 0-filled array could be removed and proceeded to do so. In addition to that, compilers are only pushing this further and further. Issues are impossible to predict and even security updates could trigger issues. Gentoo prevents usage of LTO for openssl and has some links related to this at https://gitweb.gentoo.org/repo/gentoo.git/tree/dev-libs/openssl/openssl-3.2.1-r1.ebuild#n131 : - https://github.com/llvm/llvm-project/issues/55255 - https://github.com/openssl/openssl/issues/12247 - https://github.com/openssl/openssl/issues/18225 - https://github.com/openssl/openssl/issues/18663 - https://github.com/openssl/openssl/issues/18663#issuecomment-1181478057 Gentoo also prevents usage of -fstrict-aliasing and always set -fno- strict-aliasing. I don't plan to do the same at least at the moment and for Noble since I don't have time to investigate more changes. Performance shouldn't be impacted much if at all: - crypto algorithms are implemented in ASM (funnily, using C implementations can trigger issues because these got miscompiled) - the rest of the openssl codebase probably doesn't benefit from LTO because source files match codepaths quite well - at the moment, openssl performance for servers is bad due to algorithmic/architectural issues, not micro-optimizations and these wouldn't be noticed - if LTO-compliance was doable and thought to be useful by upstream, they would have certainly pushed that forward, especially in the wake of openssl 3.0's performance issues. Code size increases by a few percents except for libcrypto which gets 17% larger. The corresponding .deb file increases by 2.6% only. I ran "openssl speed" with a long benchmark time in order to get good results (there is a variation of several percents with the default - times). I then scripted a diff which output is shown below (hopefully it - will display fine...); entries within 2% are not displayed. Also note + times). I then scripted a diff which output is shown below; "." + means the difference is within 2% which is the vast majority. Also note that some important ciphers are not present due to how openssl speed works; small aes-*-cbc are negatively impacted, up to -10% but that would -50% if you compared between "software" and "hardware" implementations, the results would be reversed at anything but the smallest data sizes, and the fact that you want to use hardware implementations as much as possible means that you also want to avoid places where LTO could have an effect. type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes 16384 bytes md5 . . . . .. sha1 . . . . .. rmd160. . . . .. sha256+2.3% . . . .. sha512. . . . .. hmac(md5) . . . . .. des-ede3 . . . . .. aes-128-cbc -10.0% . . . .. aes-192-cbc -7.6% . . . .. aes-256-cbc -5.2% . . . .. camellia-128-cbc . . . . .. camellia-192-cbc . . . . .. camellia-256-cbc . . . . .. ghash . . +21.2% -27.3% +30.5% +39.3% rand -2.8% -2.9% -2.9% -2.8% .. sign verify sign/s verify/s rsa 512 bits0.31s 0.02s -2.7%. rsa 1024bits. 0.05s .. rsa 2048bits+2.4%
[Touch-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
I have seen the problem with firefox tabs crashing in the .deb installation and when running direct from the downloaded .tar.bz from Mozilla. Firefox opens but tabs show error saying "Tab crashed" This has forced me to use the snap version which works fine though I prefer not to use snaps at all as I dislike the lack of control of them and the restrictions on use that they create -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in AppArmor: New Status in akonadiconsole package in Ubuntu: Fix Released Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Fix Released Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Fix Released Status in evolution package in Ubuntu: Fix Released Status in falkon package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Confirmed Status in freecad package in Ubuntu: Invalid Status in geary package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Invalid Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Fix Released Status in kgeotag package in Ubuntu: Fix Released Status in kiwix package in Ubuntu: Incomplete Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Released Status in kontact package in Ubuntu: Fix Released Status in loupe package in Ubuntu: Confirmed Status in marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Fix Released Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Fix Released Status in plasma-welcome package in Ubuntu: Fix Released Status in privacybrowser package in Ubuntu: Invalid Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Fix Released Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: Fix Released Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+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 2058017] Re: openssl is not LTO-safe
** Description changed: tl;dr: since it's too much work to make openssl LTO-safe, upstream doesn't see it as a goal and doesn't test it, and there are probably no performance gains to LTO for this package. Openssl is an old project and the codebase wasn't written with aliasing rules in mind. There are several reports of issues related to LTO. The openssl technical commitee says "currently we're not going to fix all the strict aliasing and other LTO problems" and "Fixes raised in pull requests will be considered."; in other words: if you find a violation, we'll merge your fixes but we're not going to dedicate time to fixing them ourselves. We don't have specific reports on launchpad at the moment but there has been at least one issue experienced by the FIPS: the compiler decided a 0-filled array could be removed and proceeded to do so. In addition to that, compilers are only pushing this further and further. Issues are impossible to predict and even security updates could trigger issues. Gentoo prevents usage of LTO for openssl and has some links related to this at https://gitweb.gentoo.org/repo/gentoo.git/tree/dev-libs/openssl/openssl-3.2.1-r1.ebuild#n131 : - https://github.com/llvm/llvm-project/issues/55255 - https://github.com/openssl/openssl/issues/12247 - https://github.com/openssl/openssl/issues/18225 - https://github.com/openssl/openssl/issues/18663 - https://github.com/openssl/openssl/issues/18663#issuecomment-1181478057 Gentoo also prevents usage of -fstrict-aliasing and always set -fno- strict-aliasing. I don't plan to do the same at least at the moment and for Noble since I don't have time to investigate more changes. Performance shouldn't be impacted much if at all: - crypto algorithms are implemented in ASM (funnily, using C implementations can trigger issues because these got miscompiled) - the rest of the openssl codebase probably doesn't benefit from LTO because source files match codepaths quite well - at the moment, openssl performance for servers is bad due to algorithmic/architectural issues, not micro-optimizations and these wouldn't be noticed - if LTO-compliance was doable and thought to be useful by upstream, they would have certainly pushed that forward, especially in the wake of openssl 3.0's performance issues. Code size increases by a few percents except for libcrypto which gets 17% larger. The corresponding .deb file increases by 2.6% only. - I will add results of "openssl speed" soon (in a few hours). + I ran "openssl speed" with a long benchmark time in order to get good + results (there is a variation of several percents with the default + times). I then scripted a diff which output is shown below (hopefully it + will display fine...); entries within 2% are not displayed. Also note + that some important ciphers are not present due to how openssl speed + works; small aes-*-cbc are negatively impacted, up to -10% but that + would -50% if you compared between "software" and "hardware" + implementations, the results would be reversed at anything but the + smallest data sizes, and the fact that you want to use hardware + implementations as much as possible means that you also want to avoid + places where LTO could have an effect. + + type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes 16384 bytes + md5 + sha1 + rmd160 + sha256+2.3% + sha512 + hmac(md5) + des-ede3 + aes-128-cbc -10.0% + aes-192-cbc -7.6% + aes-256-cbc -5.2% + camellia-128-cbc + camellia-192-cbc + camellia-256-cbc + ghash +21.2% -27.3% +30.5% +39.3% + rand -2.8% -2.9% -2.9% -2.8% + sign verify sign/s verify/s + rsa 512 bits0.31s 0.02s -2.7% + rsa 1024bits0.05s + rsa 2048bits+2.4% 0.15s -2.3% + rsa 3072bits0.32s + rsa 4096bits + rsa 7680bits30.2 + rsa 15360 bits5.9 + sign verify sign/s verify/s + dsa 512 bits+4.8% 0.24s -3.9% + dsa 1024bits+2.5% -3.3% +2.4% + dsa 2048bits+2.0% + sign verify sign/s verify/s + 160 bitsecdsa (secp160r1)+100.0%+100.0% -2.2% + 192 bitsecdsa (nistp192) 0.0002s0.0002s -3.6% -3.3% + 224 bitsecdsa (nistp224) 0.s0.0001s + 256 bitsecdsa (nistp256) 0.s0.0001s + 384 bitsecdsa (nistp384) +14.3% 0.0006s -3.2% + 521 bitsecdsa (nistp521) 0.0002s0.0005s + 163 bitsecdsa (nistk163) 0.0002s0.0003s -3.2%
[Touch-packages] [Bug 2054716] Re: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1
I came across this after being offered an upgrade prematurely (which appears to be another bug). Please note #9 in https://answers.launchpad.net/ubuntu/+question/709594 if you are fettling the postinst for polkitd. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/2054716 Title: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1 Status in policykit-1 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I was working on recreating bug 2054319 and did so by modifying my /etc/apt/sources.list file from jammy to noble and installing polkit and all its dependencies. bdmurray@clean-jammy-amd64:~$ sudo apt-get install gir1.2-polkit-1.0 libpolkit-agent-1-0:amd64 libpolkit-gobject-1-0:amd64 pkexec policykit-1 polkitd Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-6.2.0-26-generic linux-headers-6.2.0-36-generic linux-headers-6.5.0-14-generic linux-hwe-6.2-headers-6.2.0-26 linux-hwe-6.2-headers-6.2.0-36 linux-hwe-6.5-headers-6.5.0-14 linux-image-6.2.0-26-generic linux-image-6.2.0-36-generic linux-image-6.5.0-14-generic linux-modules-6.2.0-26-generic linux-modules-6.2.0-36-generic linux-modules-6.5.0-14-generic linux-modules-extra-6.2.0-26-generic linux-modules-extra-6.2.0-36-generic linux-modules-extra-6.5.0-14-generic Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg libc6-dev libduktape207 libgcrypt20 libglib2.0-0 libglib2.0-bin libnss-systemd libpam-systemd libsystemd-shared libsystemd0 libudev1 libzstd1 locales systemd systemd-dev systemd-oomd systemd-resolved systemd-sysv systemd-timesyncd udev Suggested packages: glibc-doc rng-tools low-memory-monitor polkitd-pkla systemd-container systemd-homed systemd-userdbd systemd-boot libqrencode4 libtss2-rc0 Recommended packages: libnss-nis libnss-nisplus The following NEW packages will be installed: libduktape207 libsystemd-shared systemd-dev systemd-resolved The following packages will be upgraded: gir1.2-polkit-1.0 libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg libc6-dev libgcrypt20 libglib2.0-0 libglib2.0-bin libnss-systemd libpam-systemd libpolkit-agent-1-0 libpolkit-gobject-1-0 libsystemd0 libudev1 libzstd1 locales pkexec policykit-1 polkitd systemd systemd-oomd systemd-sysv systemd-timesyncd udev 26 upgraded, 4 newly installed, 0 to remove and 1407 not upgraded. Need to get 34.9 MB of archives. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: polkitd 124-1 ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail Date: Thu Feb 22 08:46:48 2024 ErrorMessage: installed polkitd package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-11-02 (112 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: policykit-1 Title: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/2054716/+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 2053146] Re: openssh 8.9p1 for Jammy auth2-gss patch for gssapi-keyex method is slightly wrong
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/openssh/+git/openssh/+merge/462552
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/openssh/+git/openssh/+merge/462553
--
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/2053146
Title:
openssh 8.9p1 for Jammy auth2-gss patch for gssapi-keyex method is
slightly wrong
Status in openssh package in Ubuntu:
In Progress
Status in openssh source package in Jammy:
In Progress
Status in openssh source package in Mantic:
In Progress
Status in openssh source package in Noble:
In Progress
Bug description:
[ Impact ]
The gssapi-keyex authentication mechanism has been inadvertently
broken in openssh. It comes from a distro patch[1], and while the
patch still applied, it was no longer correct.
Without the fix, sshd will fail to start if gssapi-keyex is listed in
the AuthenticationMethods of the server, and if not, sshd will still
start, but gssapi-keyex will not be available.
[ Test Plan ]
This update adds a new autopkgtest to the package, which tests both
gssapi-with-mic ("normal" gssapi, which is not affected by this bug),
and gssapi-keyex, which, before this update, does not work.
The test plan is to run the new ssh-gssapi autopkgtest and verify it
succeeds.
[ Where problems could occur ]
ssh is a critical piece of infrastructure, and problems with it could
have catastrophic consequences. The service itself has a test command
before it starts up to verify the syntax of the config file, but that
test is not applied on shutdown, so a restart with an invalid config
file could still leave sshd dead.
The patch adds a change to an authentication structure, but that
change is already present in the upstream code, and we are just
updating it in the new gssapi-keyex code (introduced by the distro[1]
patch, already present). Therefore, mistakes here should manifest
themselves just in the gssapi-keyex code, which wasn't working anyway.
Effectively, though, we are enabling a new authentication mechanism in
sshd, one that was not supposed to have been removed, but was broken
by mistake.
[ Other Info ]
The fact no-one noticed this problem for more than two years could be
telling that there are not many users of this authentication mechanism
out there. The same applies to debian: it has also been broken for a
while there. Maybe we should drop it for future ubuntu releases, since
upstream refuses to take it in.
[ Original Description ]
The Authmethod struct now have 4 entries but the initialization of the
method_gsskeyex in the debian/patches/gssapi.patch only have 3
entries.
The struct was changed in upstream commit
dbb339f015c33d63484261d140c84ad875a9e548 as
===
@@ -104,7 +104,8 @@ struct Authctxt {
struct Authmethod {
char*name;
- int (*userauth)(struct ssh *);
+ char*synonym;
+ int (*userauth)(struct ssh *, const char *);
int *enabled;
};
===
The incorrect code does
===
+Authmethod method_gsskeyex = {
+ "gssapi-keyex",
+ userauth_gsskeyex,
+ _authentication
+};
===
but should have a NULL between the "gssapi-keyex" string and userauth_gsskeyex
This is now (change from Focal) causing gssapi-keyex to be disabled.
===
lsb_release -rd
Description: Ubuntu 22.04.3 LTS
Release: 22.04
===
apt-cache policy openssh-server
openssh-server:
Installed: 1:8.9p1-3ubuntu0.6
Candidate: 1:8.9p1-3ubuntu0.6
Version table:
*** 1:8.9p1-3ubuntu0.6 500
500 http://faiserver.hpc2n.umu.se/mirrors/ubuntu/ubuntu
jammy-updates/main amd64 Packages
500 http://faiserver.hpc2n.umu.se/mirrors/ubuntu/ubuntu
jammy-security/main amd64 Packages
100 /var/lib/dpkg/status
1:8.9p1-3 500
500 http://faiserver.hpc2n.umu.se/mirrors/ubuntu/ubuntu jammy/main
amd64 Packages
===
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2053146/+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 2051895] Autopkgtest regression report (pulseaudio/1:16.1+dfsg1-2ubuntu4.1)
All autopkgtests for the newly accepted pulseaudio (1:16.1+dfsg1-2ubuntu4.1) for mantic have finished running. The following regressions have been reported in tests triggered by the package: libopenmpt/0.7.2-1 (i386) libsdl2/2.28.3+dfsg-2 (i386) pipewire/0.3.79-2 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/mantic/update_excuses.html#pulseaudio [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2051895 Title: Lenovo XT99 BT headset can't work in HFP profile Status in HWE Next: New Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Jammy: Fix Committed Status in pulseaudio source package in Mantic: Fix Committed Status in pulseaudio source package in Noble: Fix Committed Bug description: [Summary] When use the ThinkPluse xt99 bluetooth head set to run the test com.canonical.certification::bluetooth/audio_record_playback, it cannot record the sound and playback. It seems this device cannot switch to Hand free mode in this platform. [Steps to reproduce] Connect the ThinkPluse xt99, use the Handfree mode, then try to record some voice. [Expected result] The bluetooth headset ThinkPluse xt99 can use as a MIC to input sound. [Actual result] The bluetooth headset xt99 cannot work in the Handfree mode. [Failure rate] 100% [Impact] With the current Ubuntu 22.04 oem image, we try to connect the LENOVO XT99 bt headset and let it work in HFP mode, we select HFP profile from gnome sound-setting, but the microphone will not auto change to bt microphone and the bt output could not work too. So this BT headset could only work in A2DP mode with the current 22.04 OEM image. And we tried ubuntu 22.04 generic image, mantic image and noble image, none of them could make the headset work in HFP mode. [Fix] Cherry-pick a pulseaudio commit from upstream. [Test] I installed ubuntu 22.04 and 23.10 on 2 different Thinkpad laptops, then upgraded the pulseaudio from my ppa (ppa:hui.wang/pa-testing), in theory my change only affects bluetooth audio devices, it will not bring any impact to non-audio bluetooth devices, here I did the test with 7 bluetooth audio devices and 2 non-audio devices: BT audio devices (pairing, connection, re-connection, playback and capture all worked well): PLT_BBTGO2 (headset) Xiaomi Air3 SE (headset) Crusher Wireless (headset) SOAIY S18 (sound box) HK Soho Wireless (headset) Thinkplus XT99 (headset) Wl-1000X (headset) BT non-audio devices (pairing, connection, re-connection, key input all worked well): BT3.0 Keyboard The Pinao 2 keyboard [Where problems could occur] This change will impact bt headset negotiation process in the pulseaudio, so the possiblity of regression is limited to bt headset, it could make the bt headset fail to connect, but this possibility is very low, we tested the patch with different bt headset and bt speaker, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051895/+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 1721763] Re: ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1721763 Title: ubuntu is stuck with black screen and blinking cursos at top left on all shutdown or restart Status in ubuntu-meta package in Ubuntu: Incomplete Bug description: I really do not know which package to assign this incident, please excuse me. Any way, the release candidates is near, and this problem continues to occur since linux kernel was updated from 4.11 to 4.12 ... and now with version 4.13 the problem continues. I noticed that this problem does not occur with my other two older notebooks (one Sony Vaio and the other a generic one integrated by me) both old notes use NVIDIA video card in versions of more than 5 years ago. My new Dell notebook has a GTX 1050 video card ... but I also do not know if the cause of this problem may be linked to the video card and the fact that Nouveau driver and linux Kernel have received recent implementations for compatibilities with this new NVIDIA technology. The fact is that Ubuntu 17.10 has potential to be distributed with this problem and I think this may not be interesting, so I am reporting this case. Thank you. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-desktop 1.402 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 08:25:20 2017 InstallationDate: Installed on 2017-09-29 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1721763/+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 2058130] Re: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1
*** This bug is a duplicate of bug 2054716 *** https://bugs.launchpad.net/bugs/2054716 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #2054716, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 2054716 package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/2058130 Title: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1 Status in policykit-1 package in Ubuntu: New Bug description: Executed "do-release-upgrade" at Raspberry Pi 4 Ubuntu 22.04.4 LTS (GNU/Linux 5.15.0-1047-raspi aarch64) Usage of /:22.7% of 28.93GB ProblemType: Package DistroRelease: Ubuntu 24.04 Package: polkitd 124-1 ProcVersionSignature: Ubuntu 5.15.0-1048.51-raspi 5.15.143 Uname: Linux 5.15.0-1048-raspi aarch64 ApportVersion: 2.28.0-0ubuntu1 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: CloudSubPlatform: config-disk (/dev/mmcblk0p1) Date: Sun Mar 17 08:46:32 2024 ErrorMessage: installed polkitd package post-installation script subprocess returned error exit status 1 ImageMediaBuild: 20230217.1 Python3Details: /usr/bin/python3.12, Python 3.12.2, python3-minimal, 3.12.1-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.4ubuntu5 apt 2.7.12 SourcePackage: policykit-1 Title: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-03-17 (0 days ago) mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/2058130/+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 2058130] [NEW] package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1
*** This bug is a duplicate of bug 2054716 *** https://bugs.launchpad.net/bugs/2054716 Public bug reported: Executed "do-release-upgrade" at Raspberry Pi 4 Ubuntu 22.04.4 LTS (GNU/Linux 5.15.0-1047-raspi aarch64) Usage of /:22.7% of 28.93GB ProblemType: Package DistroRelease: Ubuntu 24.04 Package: polkitd 124-1 ProcVersionSignature: Ubuntu 5.15.0-1048.51-raspi 5.15.143 Uname: Linux 5.15.0-1048-raspi aarch64 ApportVersion: 2.28.0-0ubuntu1 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: CloudSubPlatform: config-disk (/dev/mmcblk0p1) Date: Sun Mar 17 08:46:32 2024 ErrorMessage: installed polkitd package post-installation script subprocess returned error exit status 1 ImageMediaBuild: 20230217.1 Python3Details: /usr/bin/python3.12, Python 3.12.2, python3-minimal, 3.12.1-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.4ubuntu5 apt 2.7.12 SourcePackage: policykit-1 Title: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-03-17 (0 days ago) mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00 ** Affects: policykit-1 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 arm64-image cloud-image noble raspi-image -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/2058130 Title: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1 Status in policykit-1 package in Ubuntu: New Bug description: Executed "do-release-upgrade" at Raspberry Pi 4 Ubuntu 22.04.4 LTS (GNU/Linux 5.15.0-1047-raspi aarch64) Usage of /:22.7% of 28.93GB ProblemType: Package DistroRelease: Ubuntu 24.04 Package: polkitd 124-1 ProcVersionSignature: Ubuntu 5.15.0-1048.51-raspi 5.15.143 Uname: Linux 5.15.0-1048-raspi aarch64 ApportVersion: 2.28.0-0ubuntu1 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: CloudSubPlatform: config-disk (/dev/mmcblk0p1) Date: Sun Mar 17 08:46:32 2024 ErrorMessage: installed polkitd package post-installation script subprocess returned error exit status 1 ImageMediaBuild: 20230217.1 Python3Details: /usr/bin/python3.12, Python 3.12.2, python3-minimal, 3.12.1-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.4ubuntu5 apt 2.7.12 SourcePackage: policykit-1 Title: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-03-17 (0 days ago) mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/2058130/+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 2037210] Re: unable to add PPA by its sources.list line
Bug is not fixed in latest build of Ubuntu 24.04 LTS. Please fix it before final LTS release. You are breaking user-experience. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2037210 Title: unable to add PPA by its sources.list line Status in Software Properties: Confirmed Status in software-properties package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 23.10 installed 2. Run ``` sudo apt-key adv --keyserver keyserver.ubuntu.com --recv E756285F30DB2B2BB35012E219BFCAF5168D33A9 sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/vte/ubuntu jammy main" sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/wnck/ubuntu jammy main" ``` Expected results: * key added, two repositories are added to the relevant *.list files at /etc/apt/sources.list.d/ Actual results: * relevant *.list files at /etc/apt/sources.list.d/ are not created, having errors instead ``` $ sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/vte/ubuntu jammy main" Repository: 'deb http: //ppa.launchpad.net/nrbrtx/vte/ubuntu jammy main Components: ' Description: This PPA contains VTE library from Ubuntu 20.04 LTS which is not affected by stupid bug https://pad.lv/1922276 . So user will be able to select all terminal output with full scroll-back in MATE Terminal and other VTE-based terminals as it is expected. This PPA is useful for Ubuntu 22.04 LTS, Debian 11 (bullseye) and Debian 12 (bookworm). As usual one can always remove this PPA and downgrade VTE packages by using `sudo apt-get install ppa-purge` and `sudo ppa-purge ppa:nrbrtx/vte`. More info: https://launchpad.net/~nrbrtx/+archive/ubuntu/vte Adding repository. E: Malformed entry 1 in sources file /etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources (URI) E: The list of sources could not be read. $ sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/wnck/ubuntu jammy main" Repository: 'deb http: //ppa.launchpad.net/nrbrtx/wnck/ubuntu jammy main Components: ' Description: This PPA provides patched libwnck3 package to fix https://github.com/mate-desktop/mate-panel/issues/1230 and https://pad.lv/1947420 . See details at https://github.com/mate-desktop/mate-panel/issues/1230#issuecomment-997422612 . This PPA is useful for Ubuntu 22.04 LTS and Debian 12 (bookworm). As usual one can always remove this PPA and downgrade WNCK packages by using `sudo apt-get install ppa-purge` and `sudo ppa-purge ppa:nrbrtx/wnck`. More info: https://launchpad.net/~nrbrtx/+archive/ubuntu/wnck Adding repository. Found existing deb entry in /etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources E: Malformed entry 1 in sources file /etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources (URI) E: The list of sources could not be read. $ sudo apt-get update E: Malformed entry 1 in sources file /etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources (URI) E: The list of sources could not be read. ``` ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: software-properties-common 0.99.39 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME-Flashback Date: Sun Sep 24 14:02:10 2023 PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to mantic on 2023-04-13 (164 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-09-24T13:25:34.901411 To manage notifications about this bug go to: https://bugs.launchpad.net/software-properties/+bug/2037210/+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
