[Touch-packages] [Bug 2051292] [NEW] blutooth
You have been subscribed to a public bug: when I connect to my headset it's work couple of seconds or minutes then disconnect alone ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jan 25 22:15:26 2024 InstallationDate: Installed on 2023-06-27 (211 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) InterestingModules: btusb rfcomm bnep bluetooth MachineType: Dell Inc. Inspiron 3721 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic root=UUID=4d42ff5a-4c75-44c8-a459-6df10d860db0 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 044D20 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A11 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/29/2013:efr1.1:svnDellInc.:pnInspiron3721:pvrA11:rvnDellInc.:rn044D20:rvrA00:cvnDellInc.:ct8:cvrA11:skuInspiron3721: dmi.product.family: 103C_5335KV dmi.product.name: Inspiron 3721 dmi.product.sku: Inspiron 3721 dmi.product.version: A11 dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: Primary Bus: USB BD Address: 9C:2A:70:BE:D0:62 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:5227 acl:60 sco:0 events:440 errors:0 TX bytes:36549 acl:67 sco:0 commands:391 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- blutooth https://bugs.launchpad.net/bugs/2051292 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez 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 2051346] Re: No longer preseed LXD snap to allow for LXD 5.20 release
** Merge proposal linked: https://code.launchpad.net/~philroche/ubuntu-seeds/+git/ubuntu/+merge/459502 -- 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/2051346 Title: No longer preseed LXD snap to allow for LXD 5.20 release Status in ubuntu-meta package in Ubuntu: New Bug description: With LXD 5.20 there is a license change to AGPL and it has been decided to no longer seed the snap in Ubuntu 24.04 and later and instead seed the lxd-installer package instead. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n60 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346/+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 2051367] [NEW] [81YM, ATI R6xx HDMI, Digital Out, HDMI] Playback problem
You have been subscribed to a public bug: When using 2 external monitors via a dual HDMI adapter plugged on the usb-c port, when i go to play sound at all, 1 of the external monitors is always selected as the default output device when this should still be the laptop internal speakers. Annoying as hell to have to go into the settings everytime i switch the laptop on and there is no sound on sound output. It would be great if you could fix it so it leaves its always "laptop internal speakers" as default. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-92.102-generic 5.15.131 Uname: Linux 5.15.0-92-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: smiler 7478 F pulseaudio /dev/snd/pcmC2D0c: smiler 7478 F...m pulseaudio /dev/snd/controlC1: smiler 7478 F pulseaudio /dev/snd/controlC0: smiler 7478 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 26 14:17:02 2024 InstallationDate: Installed on 2022-02-04 (720 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Renoir Radeon High Definition Audio Controller - HD-Audio Generic Symptom_Jack: Digital Out, HDMI Symptom_Type: None of the above Title: [81YM, ATI R6xx HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2021 dmi.bios.release: 1.25 dmi.bios.vendor: LENOVO dmi.bios.version: DTCN25WW(V1.11) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 14ARE05 dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrDTCN25WW(V1.11):bd09/14/2021:br1.25:efr1.25:svnLENOVO:pn81YM:pvrIdeaPad514ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad514ARE05:skuLENOVO_MT_81YM_BU_idea_FM_IdeaPad514ARE05: dmi.product.family: IdeaPad 5 14ARE05 dmi.product.name: 81YM dmi.product.sku: LENOVO_MT_81YM_BU_idea_FM_IdeaPad 5 14ARE05 dmi.product.version: IdeaPad 5 14ARE05 dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- [81YM, ATI R6xx HDMI, Digital Out, HDMI] Playback problem https://bugs.launchpad.net/bugs/2051367 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver 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 2036473] Re: [82Y7, Realtek ALC287, Speaker, Internal] volume either 100% or off
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/2036473 Title: [82Y7, Realtek ALC287, Speaker, Internal] volume either 100% or off Status in alsa-driver package in Ubuntu: Confirmed Bug description: The audio on my laptop, specifically when booting on ubuntu, is not working properly. The volume slider either turns my audio off or it turns it up to 100%. Anything else than muted is 100% on the volume slider. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: erik 1872 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Sep 19 00:42:13 2023 InstallationDate: Installed on 2023-09-07 (11 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: sep 19 00:35:47 erik-Yoga-Pro-7-14IRH8 pulseaudio[1239]: After module unload, module 'module-null-sink' was still loaded! Symptom_Type: Volume slider, or mixer problems Title: [82Y7, Realtek ALC287, Speaker, Internal] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2023 dmi.bios.release: 1.22 dmi.bios.vendor: LENOVO dmi.bios.version: LWCN22WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Pro 7 14IRH8 dmi.ec.firmware.release: 1.22 dmi.modalias: dmi:bvnLENOVO:bvrLWCN22WW:bd03/07/2023:br1.22:efr1.22:svnLENOVO:pn82Y7:pvrYogaPro714IRH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrYogaPro714IRH8:skuLENOVO_MT_82Y7_BU_idea_FM_YogaPro714IRH8: dmi.product.family: Yoga Pro 7 14IRH8 dmi.product.name: 82Y7 dmi.product.sku: LENOVO_MT_82Y7_BU_idea_FM_Yoga Pro 7 14IRH8 dmi.product.version: Yoga Pro 7 14IRH8 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2036473/+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 1995790] Re: regression: ?garbage does not work correctly in install commands
This bug was fixed in the package apt - 2.7.10 --- apt (2.7.10) unstable; urgency=medium * pkgcachegen: Use placement new to construct header to make valgrind happy when we hash/write out padding bytes * Add Conflicts: apt-verify. The APT team is very concerned about the encroachement of its namespace and the impact on security of its file verification process. We have expressed those concerns in the ITP bug, but the package was nonetheless uploaded and accepted, so we have to take this extraordinary step to protect our users. -- Julian Andres Klode Fri, 19 Jan 2024 09:31:13 +0100 ** Changed in: apt (Ubuntu Noble) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1995790 Title: regression: ?garbage does not work correctly in install commands Status in apt package in Ubuntu: Fix Released Status in apt source package in Jammy: Triaged Status in apt source package in Lunar: Won't Fix Status in apt source package in Mantic: Triaged Status in apt source package in Noble: Fix Released Bug description: The awesome apt has a some wonderful tips on their EXAMPLES section (printed below). The choice of name to "garbage" might not have been the best but the function is extremely useful. $ man apt-patterns | sed '/EXAMPLES/,/^[^ ]/!d;/^[^ ]/d' apt remove ?garbage Remove all packages that are automatically installed and no longer needed - same as apt autoremove apt purge ?config-files Purge all packages that only have configuration files left apt list '~i !~M (~slibs|~sperl|~spython)' List all manually-installed packages in sections matching libs, perl, or python. Lets mark a package as automatically installed, and use the examples. $ sudo apt-mark auto shotwell shotwell set to automatically installed. $ sudo apt remove ?garbage Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: libraw20 shotwell shotwell-common Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. $ sudo apt autoremove Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: libraw20 shotwell shotwell-common 0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded. After this operation, 9.806 kB disk space will be freed. Do you want to continue? [Y/n] N Abort. Apt-patterns works as it should everywhere else, as far as I can see, it works wonders with ie `apt list '~g|~c'` and many other applications. I used `apt purge '~g|~c'` successfully in Ubuntu 20.04 for years, so I feel this is a regression. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apt 2.4.8 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Nov 6 10:57:52 2022 SourcePackage: apt UpgradeStatus: Upgraded to jammy on 2022-03-26 (224 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1995790/+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 2051454] Re: pipewire wireplumber can not detect the sound output device when using an unofficial linux kernel
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apparmor (Ubuntu) Status: New => Confirmed -- 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/2051454 Title: pipewire wireplumber can not detect the sound output device when using an unofficial linux kernel Status in apparmor package in Ubuntu: Confirmed Status in pipewire package in Ubuntu: Confirmed Status in wireplumber package in Ubuntu: Confirmed Bug description: Ubuntu 24.04 noble I tested on Kernel-6.7.2, 6.7.1, 6.6.8, don't work. relating service status: gsd-media-keys[6441]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed pipewire-pulse[5768]: mod.protocol-pulse: client 0x5e701af4f9a0 [Mutter]: ERROR command:-1 (invalid) tag:418 error:25 (Input/output error) pipewire-pulse[5768]: mod.protocol-pulse: client 0x5e701af4f9a0 [Mutter]: ERROR command:-1 (invalid) tag:426 error:25 (Input/output error) pipewire-pulse[5298]: default: snap_get_audio_permissions: failed to get the AppArmor info. wireplumber[61568]: si-standard-link: in/out items are not valid anymore wireplumber[61568]: 2 of 2 PipeWire links failed to activate It's worked on kernel linux-image-6.5.0-14-generic. I built the same version 1.0.1 from the https://gitlab.freedesktop.org/pipewire source code, The sound card can be detected normally and shown in the gnome setting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2051454/+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 2051454] Re: pipewire wireplumber can not detect the sound output device when using an unofficial linux kernel
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: wireplumber (Ubuntu) Status: New => Confirmed -- 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/2051454 Title: pipewire wireplumber can not detect the sound output device when using an unofficial linux kernel Status in apparmor package in Ubuntu: Confirmed Status in pipewire package in Ubuntu: Confirmed Status in wireplumber package in Ubuntu: Confirmed Bug description: Ubuntu 24.04 noble I tested on Kernel-6.7.2, 6.7.1, 6.6.8, don't work. relating service status: gsd-media-keys[6441]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed pipewire-pulse[5768]: mod.protocol-pulse: client 0x5e701af4f9a0 [Mutter]: ERROR command:-1 (invalid) tag:418 error:25 (Input/output error) pipewire-pulse[5768]: mod.protocol-pulse: client 0x5e701af4f9a0 [Mutter]: ERROR command:-1 (invalid) tag:426 error:25 (Input/output error) pipewire-pulse[5298]: default: snap_get_audio_permissions: failed to get the AppArmor info. wireplumber[61568]: si-standard-link: in/out items are not valid anymore wireplumber[61568]: 2 of 2 PipeWire links failed to activate It's worked on kernel linux-image-6.5.0-14-generic. I built the same version 1.0.1 from the https://gitlab.freedesktop.org/pipewire source code, The sound card can be detected normally and shown in the gnome setting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2051454/+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 2051506] Re: apparmor blocks libnss-resolve socket
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apparmor (Ubuntu)
Status: New => Confirmed
--
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/2051506
Title:
apparmor blocks libnss-resolve socket
Status in apparmor package in Ubuntu:
Confirmed
Bug description:
Usage of `libnss-resolve` socket is blocked by apparmor.
Evidence:
- Install `libnss-resolve`
- Set /etc/nsswitch.conf to have `hosts: files resolve`
- Try resolving anything, it fails
`strace` of affected process reveals:
`connect(5, {sa_family=AF_UNIX,
sun_path="/run/systemd/resolve/io.systemd.Resolve"}, 42) = -1 EACCES
(Permission denied)`
Run `aa-disable` on affected profile and `strace` it again, it works:
`connect(5, {sa_family=AF_UNIX,
sun_path="/run/systemd/resolve/io.systemd.Resolve"}, 42) = 0`
Note that using `aa-complain` DOES NOT work.
p.s. has this ever worked?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2051506/+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 2051118] Re: DEP8 error on armhf
** Merge proposal linked: https://code.launchpad.net/~ahasenack/ubuntu/+source/libseccomp/+git/libseccomp/+merge/459586 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/2051118 Title: DEP8 error on armhf Status in libseccomp package in Ubuntu: In Progress Bug description: Version 2.5.4-2 introduced this change in d/t/control: libseccomp (2.5.4-2) unstable; urgency=medium * Fix watch file. (Closes: #1050659) * Dynamically skip autopkgtests when the test runner already applies seccomp restrictions. - Drop isolation-machine restriction. -Restrictions: isolation-machine, allow-stderr +Restrictions: skippable, allow-stderr This made the test run in Ubuntu again on armhf, where we use a lxd container (it wasn't running previously). This change is relying on this check in d/t/common: if ! grep -q -E '^Seccomp:[[:blank:]]+0$' /proc/self/status; then echo "Skipping autpkgptest as the test environment already applies a seccomp filter" exit 77 fi In Debian, where they also use containers, the testsuite-live-python3 test is skipped correctly, but in Ubuntu, it is run and fails[1] with timeout limit: 541s live 541s ./regression: line 253: cd: /tmp/autopkgtest.X55y55/autopkgtest_tmp/tests/../src/python/build/lib.*: No such file or directory 10468s autopkgtest [01:49:37]: kill with SIGTERM did not work sending SIGKILL 1. https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/armhf/libs/libseccomp/20231225_015646_12139@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/2051118/+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 2051572] Re: Always preseed core and snapd snap in server seed
** Merge proposal linked: https://code.launchpad.net/~philroche/ubuntu-seeds/+git/ubuntu/+merge/459599 -- 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/2051572 Title: Always preseed core and snapd snap in server seed Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Noble: New Bug description: In removing the LXD snap from preseeding in the server seed for Ubuntu 24.04 as part LP #2051346 [1] we also removed the snaps snap and the core22 snap. This means that are subsequent snap install, like LXD, will take much longer than expected for a non minimized image. Time taken to install LXD snap using the lxd-installer package without snapd and core22 preinstalled/seeded ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m29.107s user 0m0.006s sys 0m0.005s ``` Time taken to install LXD snap using the lxd-installer package with snapd and core22 already installed. ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m15.034s user 0m0.005s sys 0m0.005s ``` This is a significant difference and for a workload we intend to remain as a core tested and tracked workload. As such I propose we re- introduce core22 and snaps snaps to our seed. LXD do intend to move to the core24 snap as their base as I'm sure snapd does too so when that does happen we need to update the preseeded core snap. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n69 [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051572/+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 2051454] Re: pipewire wireplumber can not detect the sound output device when using an unofficial linux kernel
This bug was fixed in the package pipewire - 1.0.1-1ubuntu3 --- pipewire (1.0.1-1ubuntu3) noble; urgency=medium * Fix broken audio when using a kernel without "fine grained unix mediation" patch (LP: #2051504, LP: #2051454) -- Sergio Costas Rodriguez Mon, 29 Jan 2024 19:03:45 +0200 ** Changed in: pipewire (Ubuntu) Status: In Progress => Fix Released -- 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/2051454 Title: pipewire wireplumber can not detect the sound output device when using an unofficial linux kernel Status in apparmor package in Ubuntu: Confirmed Status in pipewire package in Ubuntu: Fix Released Status in wireplumber package in Ubuntu: Confirmed Bug description: Ubuntu 24.04 noble I tested on Kernel-6.7.2, 6.7.1, 6.6.8, don't work. relating service status: gsd-media-keys[6441]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed pipewire-pulse[5768]: mod.protocol-pulse: client 0x5e701af4f9a0 [Mutter]: ERROR command:-1 (invalid) tag:418 error:25 (Input/output error) pipewire-pulse[5768]: mod.protocol-pulse: client 0x5e701af4f9a0 [Mutter]: ERROR command:-1 (invalid) tag:426 error:25 (Input/output error) pipewire-pulse[5298]: default: snap_get_audio_permissions: failed to get the AppArmor info. wireplumber[61568]: si-standard-link: in/out items are not valid anymore wireplumber[61568]: 2 of 2 PipeWire links failed to activate It's worked on kernel linux-image-6.5.0-14-generic. I built the same version 1.0.1 from the https://gitlab.freedesktop.org/pipewire source code, The sound card can be detected normally and shown in the gnome setting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2051454/+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 2051617] [NEW] Raspberry Pi mouse buttons left and right unresponsive
You have been subscribed to a public bug:
Using the event tracker tool
(
xmodmap -pp > ~/xmodmap-pp
xev | grep -i button
), buttons 4 and 5 are responsive, optical works (the cursor moves across the
screen).
Left and right click buttons are unresponsive. Mouse connected via USB.
MOUSE INFO:
Raspberry Pi Mouse
CAN ICES-3 (B)/NMB-3(B)
Model No.: RPI-MOUSE
This issue has been extant every since I have tried to use this mouse.
Currently using Ubuntu Mantic Minotaur (23.10)
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 29 21:24:11 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus: virtualbox/7.0.12, 6.5.0-15-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if
00 [VGA controller])
Subsystem: Dell CometLake-U GT2 [UHD Graphics] [1028:09ed]
InstallationDate: Installed on 2023-12-16 (45 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 001 Device 002: ID 8087:0026 Intel Corp. AX201 Bluetooth
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 3: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 10: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 10: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic
root=UUID=aa49e6e1-853a-4b59-81d9-ea0fcd3ca2cf ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/05/2021
dmi.bios.release: 1.10
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.10.1
dmi.board.name: 00V66M
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.10.1:bd08/05/2021:br1.10:svnDellInc.:pnLatitude3510:pvr:rvnDellInc.:rn00V66M:rvrA00:cvnDellInc.:ct10:cvr:sku09ED:
dmi.product.family: Latitude
dmi.product.name: Latitude 3510
dmi.product.sku: 09ED
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic ubuntu wayland-session
--
Raspberry Pi mouse buttons left and right unresponsive
https://bugs.launchpad.net/bugs/2051617
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 2045245] Re: ubuntu22.04 ibus Chinese pinying input not response
[Expired for ibus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ibus (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2045245 Title: ubuntu22.04 ibus Chinese pinying input not response Status in ibus package in Ubuntu: Expired Bug description: I have used 22.04 many times, and I encountered this problem every time. During the first period of installing the system, everything was fine, but once I used the system for more than a few months, the ibus started to stop responding and I could not enter. There is no response when pressing any keys on the keyboard. The only solution is to manually click the input method icon in the upper right corner, switch to English, and then enter `ibus restart`. But this problem of input method not responding is too frequent and occurs every few minutes. I can't stand this torture anymore, and I now use a third-party input method. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2045245/+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 2051350] [NEW] package libasound2-plugins 1.2.7.1-1ubuntu2 failed to install/upgrade: trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is d
You have been subscribed to a public bug: wa installing wine ProblemType: Package DistroRelease: Ubuntu 23.10 Package: libasound2-plugins 1.2.7.1-1ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-15.15.1-lowlatency 6.5.3 Uname: Linux 6.5.0-15-lowlatency x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jan 26 10:23:45 2024 DuplicateSignature: package:libasound2-plugins:1.2.7.1-1ubuntu2 Unpacking libasound2-plugins:i386 (1.2.7.1-1ubuntu2) ... dpkg: error processing archive /tmp/apt-dpkg-install-LCQD0p/134-libasound2-plugins_1.2.7.1-1ubuntu2_i386.deb (--unpack): trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from other instances of package libasound2-plugins:i386 ErrorMessage: trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from other instances of package libasound2-plugins:i386 InstallationDate: Installed on 2024-01-25 (1 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: alsa-plugins Title: package libasound2-plugins 1.2.7.1-1ubuntu2 failed to install/upgrade: trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from other instances of package libasound2-plugins:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: alsa-plugins (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package mantic need-duplicate-check package-conflict -- package libasound2-plugins 1.2.7.1-1ubuntu2 failed to install/upgrade: trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from other instances of package libasound2-plugins:i386 https://bugs.launchpad.net/bugs/2051350 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-plugins 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 2008491] Re: Memory leak in pulseaudio
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- 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/2008491 Title: Memory leak in pulseaudio Status in pulseaudio package in Ubuntu: Confirmed Bug description: This is very weird, but my pulseaudio uses 3.5GB as I type this. That seems big for audio stuff. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Feb 24 14:56:46 2023 InstallationDate: Installed on 2023-01-04 (51 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2022 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET62W (1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CKCTO1WW dmi.board.vendor: LENOVO dmi.board.version: ThinkPad dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrR23ET62W(1.32):bd11/11/2022:br1.32:efr1.23:svnLENOVO:pn21CKCTO1WW:pvrThinkPadP16sGen1:rvnLENOVO:rn21CKCTO1WW:rvrThinkPad:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CK_BU_Think_FM_ThinkPadP16sGen1: dmi.product.family: ThinkPad P16s Gen 1 dmi.product.name: 21CKCTO1WW dmi.product.sku: LENOVO_MT_21CK_BU_Think_FM_ThinkPad P16s Gen 1 dmi.product.version: ThinkPad P16s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2008491/+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 2051540] Re: ufw ftbfs with Python 3.12 as default
** Merge proposal linked:
https://code.launchpad.net/~alexmurray/ufw/+git/ufw/+merge/459690
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/2051540
Title:
ufw ftbfs with Python 3.12 as default
Status in ufw:
New
Status in ufw package in Ubuntu:
Confirmed
Bug description:
==
ERROR: test_ufwcommand_parse
(tests.unit.test_parser.ParserTestCase.test_ufwcommand_parse)
Test UFWCommand.parse()
--
Traceback (most recent call last):
File "/<>/tests/unit/test_parser.py", line 88, in
test_ufwcommand_parse
self.assertEquals('status', pr.action, "%s != 'status'" % (pr.action))
^
AttributeError: 'ParserTestCase' object has no attribute 'assertEquals'. Did
you mean: 'assertEqual'?
==
ERROR: test_ufwcommand_rule_get_command
(tests.unit.test_parser.ParserTestCase.test_ufwcommand_rule_get_command)
Test UFWCommand(Route)Rule.get_command()
--
Traceback (most recent call last):
File "/<>/tests/unit/test_parser.py", line 375, in
test_ufwcommand_rule_get_command
self.assertEquals(len(errors), 0,
^
AttributeError: 'ParserTestCase' object has no attribute 'assertEquals'. Did
you mean: 'assertEqual'?
--
Ran 24 tests in 7.584s
FAILED (errors=9)
test_skeleton
test_example (tests.unit.test_skeleton.SkeletonTestCase.test_example)
Test example dummy test ... ok
--
Ran 1 test in 0.000s
OK
To manage notifications about this bug go to:
https://bugs.launchpad.net/ufw/+bug/2051540/+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 2000430] Re: iwconfig shows implausible bitrate.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: wireless-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wireless-tools in Ubuntu. https://bugs.launchpad.net/bugs/2000430 Title: iwconfig shows implausible bitrate. Status in wireless-tools package in Ubuntu: Confirmed Bug description: When displaying connection info, `iwconfig` shows implausible information. wlp1s0IEEE 802.11 ESSID:"xx" Mode:Managed Frequency:5.24 GHz Access Point: 7E:45:58:xx:xx:xx Bit Rate=-1.89307e+06 kb/s Tx-Power=20 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:on Link Quality=70/70 Signal level=-40 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:46 Invalid misc:15697 Missed beacon:0 while `iw` is fine Connected to 7e:45:58:xx:xx:xx (on wlp1s0) SSID: xx freq: 5240 RX: 2036803929 bytes (1776517 packets) TX: 100215785 bytes (575761 packets) signal: -41 dBm rx bitrate: 2161.3 MBit/s 160MHz HE-MCS 10 HE-NSS 2 HE-GI 0 HE-DCM 0 tx bitrate: 2401.9 MBit/s 160MHz HE-MCS 11 HE-NSS 2 HE-GI 0 HE-DCM 0 bss flags: short-slot-time dtim period:3 beacon int: 100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-tools/+bug/2000430/+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 2045570] Re: dnsmasq crash when no servers in resolv.conf
This bug was fixed in the package dnsmasq - 2.86-1.1ubuntu0.5 --- dnsmasq (2.86-1.1ubuntu0.5) jammy; urgency=medium * src/dnsmasq.c: Fix a crash that can happen when an empty resolv.conf is reloaded (LP: #2045570) * src/helper.c: Fix wrong client address for dhcp-script when DHCPv4 relay in use (LP: #2042587) -- Andreas Hasenack Thu, 11 Jan 2024 09:21:27 -0300 ** Changed in: dnsmasq (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/2045570 Title: dnsmasq crash when no servers in resolv.conf Status in dnsmasq package in Ubuntu: Fix Released Status in dnsmasq source package in Jammy: Fix Released Bug description: [ Impact ] dnsmasq "keeps an eye" on /etc/resolv.conf, and reloads it whenever the file is updated. When that happens and for some reason there were no "nameserver" declarations in the updated file, dnsmasq can crash. Here is a log of a reproducer: $ dig +short @127.0.0.1 ubuntu.com ;; communications error to 127.0.0.1#53: timed out ;; communications error to 127.0.0.1#53: connection refused ;; communications error to 127.0.0.1#53: connection refused ;; no servers could be reached We can see the startup, then when resolv.conf is read again and no nameservers were found, and the crash: Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: started, version 2.86 cachesize 150 Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: DNS service limited to local subnets Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: compile time options: IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset auth cryptohash DNSSEC loop-detect inotify dumpfile Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: reading /etc/resolv.conf Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: using nameserver 10.0.100.1#53 Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: read /etc/hosts - 7 addresses Jan 03 13:57:13 j-dnsmasq-2045570 systemd[1]: Started dnsmasq - A lightweight DHCP and caching DNS server. Jan 03 13:58:01 j-dnsmasq-2045570 dnsmasq[1507]: no servers found in /etc/resolv.conf, will retry Jan 03 13:58:22 j-dnsmasq-2045570 systemd[1]: dnsmasq.service: Main process exited, code=dumped, status=11/SEGV Jan 03 13:58:22 j-dnsmasq-2045570 systemd[1]: dnsmasq.service: Failed with result 'core-dump'. dnsmasq has provisions for this situation, we can see that in the 13:58:01 message where it says it will retry, but due to this bug, it crashes instead. The problem was introduced[1] in version 2.86, and fixed in 2.87, so only jammy is affected. 1. https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=patch;h=d290630d31f4517ab26392d00753d1397f9a4114;hp=d2ad5dc073aaacaf22b117f16106282a73586803 The commit message says: """ This problem was introduced in 2.86. """ And indeed, I wasn't able to crash 2.80 shipped in focal. [ Test Plan ] It might take a few tries to reproduce the bug, but here is the general outline. Also keep in mind that it's important to use a DNS name that isn't cached already by a previous query. # Create a jammy lxd container lxc launch ubuntu-daily:jammy j-dnsmasq-2045570 # Enter the container lxc shell j-dnsmasq-2045570 # From now on, all commands should be executed in the container. # Install dnsmasq, and disable systemd-resolved apt update && apt install -y dnsmasq # Disable systemd-resolved, and start dnsmasq systemctl disable --now systemd-resolved systemctl enable --now dnsmasq # In one terminal inside the container, watch the dnsmasq logs: journalctl -u dnsmasq.service -f # In another terminal, remove /etc/resolv.conf and create a new one, empty rm /etc/resolv.conf echo "nameserver 1.1.1.1" > /etc/resolv.conf # restart dnsmasq systemctl restart dnsmasq.service # Perform a dns query dig @127.0.0.1 +short linux.com # Comment the namserver directive in resolv.conf echo "#nameserver 1.1.1.1" > /etc/resolv.conf # Observe in the dnsmasq logs that it notices the change with a message like: Jan 03 14:14:51 j-dnsmasq-2045570 dnsmasq[2274]: no servers found in /etc/resolv.conf, will retry # Perform a *different* DNS query dig @127.0.0.1 +short ubuntu.com # Observe in the dnsmasq logs that it crashes. Jan 03 13:58:22 j-dnsmasq-2045570 systemd[1]: dnsmasq.service: Main process exited, code=dumped, status=11/SEGV Jan 03 13:58:22 j-dnsmasq-2045570 systemd[1]: dnsmasq.service: Failed with result 'core-dump'. If it doesn't crash right away, repeat these steps a few times, but using a different domain name each time: - add "nameserver 127.0.0.1" to /etc/resolv.conf - observe that dnsmasq notices the change to the file - perform a query for some random domain using "dig @127.0.0.1 +short " - remove "nameserver" from /et
[Touch-packages] [Bug 2042587] Re: jammy's version breaks existing dhcp scripts with relay
This bug was fixed in the package dnsmasq - 2.86-1.1ubuntu0.5 --- dnsmasq (2.86-1.1ubuntu0.5) jammy; urgency=medium * src/dnsmasq.c: Fix a crash that can happen when an empty resolv.conf is reloaded (LP: #2045570) * src/helper.c: Fix wrong client address for dhcp-script when DHCPv4 relay in use (LP: #2042587) -- Andreas Hasenack Thu, 11 Jan 2024 09:21:27 -0300 ** Changed in: dnsmasq (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/2042587 Title: jammy's version breaks existing dhcp scripts with relay Status in dnsmasq package in Ubuntu: Fix Released Status in dnsmasq source package in Jammy: Fix Released Bug description: [ Impact ] When upgrading from focal to jammy, existing dnsmasq dhcp-scripts stopped working in an environment where a DHCP relay is in use. Instead of the expected client IP address, the script gets the _relay_ IP address as an argument. This was fixed in 2.87, therefore making only jammy carry an affected package. [ Test Plan ] To easily test this on a single machine, a test script is being provided to setup networking and dnsmasq configuration. # Launch a jammy VM lxc launch ubuntu-daily:jammy j-dnsmasq-2042587 --vm # open a root shell in that VM. All subsequent commands must be executed as root in that VM lxc shell j-dnsmasq-2042587 # download test script wget https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2042587/+attachment/5738174/+files/setup- and-server.sh # make it executable chmod +x setup-and-server.sh # install dnsmasq. Ignore the postinst error (because systemd-resolved is also running and there is a port conflict) apt update && apt install dnsmasq -y # run the setup script. It will configure things and start dnsmasq ready to be tested ./setup-and-server.sh # in another root session inside the vm (so run "lxc shell j-dnsmasq-2042587" in another terminal), run the proposed commands from the setup script (and press ctrl-c after the result is shown): No DHCP relay: ip netns exec client dhclient -d -v p2 The setup script should log an IP that is not a relay. For example: dnsmasq-dhcp: DHCPDISCOVER(p1) aa:a0:9d:00:5b:d6 dnsmasq-dhcp: DHCPOFFER(p1) 192.168.47.150 aa:a0:9d:00:5b:d6 dnsmasq-dhcp: DHCPREQUEST(p1) 192.168.47.150 aa:a0:9d:00:5b:d6 dnsmasq-dhcp: DHCPACK(p1) 192.168.47.150 aa:a0:9d:00:5b:d6 j-dnsmasq-2042587 ### IP = 192.168.47.150 ### With DHCP relay set to 192.168.47.9, IP should NOT be that address: ip netns exec client dhclient -d -v p2 -g 192.168.47.9 With the affected dnsmasq package, we will see an error: dnsmasq-dhcp: DHCPREQUEST(p1) 192.168.47.150 aa:a0:9d:00:5b:d6 dnsmasq-dhcp: DHCPACK(p1) 192.168.47.150 aa:a0:9d:00:5b:d6 j-dnsmasq-2042587 ### IP = 192.168.47.9 TEST FAILED ### The error is that the obtained IP is that of the dhcp relay (provided via the -g option). With the fixed dnsmasq package, "TEST FAILED" must not appear, and the IP should not be that of the provided dhcp relay. [ Where problems could occur ] If the fix is incorrect, it would mean the dhcp-script would get an incorrect IP again, or perhaps we could have crashes in dnsmasq when dealing with buffers and pointers if the dhcp-script option is in use. This fix was committed upstream a few months after the bug was introduced, so it took a while to be noticed. [ Other Info ] Not at this time. [ Original description ] When upgrading from focal to jammy, existing dnsmasq dhcp-scripts stopped working in an environment where a DHCP relay is in use. Instead of the expected client IP address, the script gets the _relay_ IP address as an argument. From dnsmasq documentation for --dhcp- script: > The arguments to the process are "add", "old" or "del", the MAC address of the host (or DUID for IPv6) , the IP address, and the hostname, if known. I believe the change has been inadverently made in upstream commit 527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692 (https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=blobdiff;f=src/helper.c;h=02340a01c00031db0cc682c8a4a279cfc1db574e;hp=d81de9622e6d484a264496b2cd3638b4e15e9677;hb=527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692;hpb=fcb4dcaf7cc8a86ac2533b933161b6455f75bf8f) as the commit message only speaks about inet_ntoa replacement and not the behavioral change it also introduces (previously the relay address was only set to the environment variable, now it effectively overrides the prevoiusly set client's IP address). dnsmasq 2.86-1.1ubuntu0.3 / Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2042587/+sub
[Touch-packages] [Bug 1790418] Re: ditch ipconfig entirely in 19.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1790418 Title: ditch ipconfig entirely in 19.04 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Bug 1782802 used to be about ripping ipconfig entirely out of the initramfs. But that was too hard to do for cosmic, hence this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1790418/+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 1782802] Re: use dhclient -4 instead of ipconfig in easy cases in 18.10
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1782802 Title: use dhclient -4 instead of ipconfig in easy cases in 18.10 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: When adding ipv6 netboot support to initramfs-tools in yakkety/zesty, this was initially attempted with replacing ipconfig with dhclient. As described in LP: #1621507, the use of dhclient for ipv4 dhcp was backed out in favor of ipconfig. So at the moment, we are using both ipconfig from klibc-utils and dhclient from isc-dhcp-client in the initramfs. We want to switch off of klibc-utils completely and use isc-dhcp- client for both ipv4 and ipv6 in initramfs-tools. But for cosmic, we'll only do the easy bits. Bug 1790418 is about finishing the job. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1782802/+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 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable
** Merge proposal linked: https://code.launchpad.net/~dannf/livecd-rootfs/+git/livecd-rootfs/+merge/459549 -- 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/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: New Bug description: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+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] [NEW] Lenovo XT99 BT headset can't work in HFP profile
You have been subscribed to a public bug: [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% ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- Lenovo XT99 BT headset can't work in HFP profile https://bugs.launchpad.net/bugs/2051895 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio 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 2051118] Re: DEP8 error on armhf
This bug was fixed in the package libseccomp - 2.5.4-2ubuntu2 --- libseccomp (2.5.4-2ubuntu2) noble; urgency=medium * d/t/testsuite-live-python3: skip this test if on a) armhf; b) ubuntu; c) lxd (LP: #2051118) libseccomp (2.5.4-2ubuntu1) noble; urgency=medium * Merge with Debian; remaining changes: - Add autopkgtests -- Andreas Hasenack Fri, 26 Jan 2024 15:04:52 -0300 ** Changed in: libseccomp (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/2051118 Title: DEP8 error on armhf Status in libseccomp package in Ubuntu: Fix Released Bug description: Version 2.5.4-2 introduced this change in d/t/control: libseccomp (2.5.4-2) unstable; urgency=medium * Fix watch file. (Closes: #1050659) * Dynamically skip autopkgtests when the test runner already applies seccomp restrictions. - Drop isolation-machine restriction. -Restrictions: isolation-machine, allow-stderr +Restrictions: skippable, allow-stderr This made the test run in Ubuntu again on armhf, where we use a lxd container (it wasn't running previously). This change is relying on this check in d/t/common: if ! grep -q -E '^Seccomp:[[:blank:]]+0$' /proc/self/status; then echo "Skipping autpkgptest as the test environment already applies a seccomp filter" exit 77 fi In Debian, where they also use containers, the testsuite-live-python3 test is skipped correctly, but in Ubuntu, it is run and fails[1] with timeout limit: 541s live 541s ./regression: line 253: cd: /tmp/autopkgtest.X55y55/autopkgtest_tmp/tests/../src/python/build/lib.*: No such file or directory 10468s autopkgtest [01:49:37]: kill with SIGTERM did not work sending SIGKILL 1. https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/armhf/libs/libseccomp/20231225_015646_12139@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/2051118/+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 2049552] Re: [noble] ftbfs with new zlib 1.3
This bug was fixed in the package openssh - 1:9.6p1-3ubuntu1 --- openssh (1:9.6p1-3ubuntu1) noble; urgency=medium * Merge with Debian unstable (LP: #2040406). Remaining changes: - debian/rules: modify dh_installsystemd invocations for socket-activated sshd. - debian/openssh-server.postinst: handle migration of sshd_config options to systemd socket options on upgrade. - debian/README.Debian: document systemd socket activation. - debian/patches/socket-activation-documentation.patch: Document in sshd_config(5) that ListenAddress and Port no longer work. - debian/openssh-server.templates: include debconf prompt explaining when migration cannot happen due to multiple ListenAddress values. - debian/.gitignore: drop file. - debian/openssh-server.postrm: remove systemd drop-ins for socket-activated sshd on purge. - debian/openssh-server.ucf-md5sum: update for Ubuntu delta - debian/openssh-server.tmpfile,debian/systemd/ssh.service: Move /run/sshd creation out of the systemd unit to a tmpfile config so that sshd can be run manually if necessary without having to create this directory by hand. - debian/patches/systemd-socket-activation.patch: Fix sshd re-execution behavior when socket activation is used. - debian/tests/systemd-socket-activation: Add autopkgtest for systemd socket activation functionality. - d/p/test-set-UsePAM-no-on-some-tests.patch: set UsePAM=no for some tests. * Dropped changes, fixed upstream: - d/p/fix-ftbfs-with-zlib13.patch: fix ftbfs when using zlib 1.3 (LP #2049552) openssh (1:9.6p1-3) unstable; urgency=medium * Allow passing extra ssh-agent arguments via "/usr/lib/openssh/agent-launch start", making it possible to override things like identity lifetime using a systemd drop-in unit (closes: #1059639). * Don't try to start rescue-ssh.target in postinst (LP: #2047082). openssh (1:9.6p1-2) unstable; urgency=medium * Improve detection of broken -fzero-call-used-regs=used (see https://bugzilla.mindrot.org/show_bug.cgi?id=3645; fixes build on ppc64/ppc64el). openssh (1:9.6p1-1) unstable; urgency=medium * Use single quotes in suggested ssh-keygen commands (closes: #1057835). * Debconf translations: - Catalan (thanks, Pablo Huguet; closes: #1049995). * New upstream release (https://www.openssh.com/releasenotes.html#9.6p1): - [CVE-2023-48795] ssh(1), sshd(8): implement protocol extensions to thwart the so-called "Terrapin attack" discovered by Fabian Bäumer, Marcus Brinkmann and Jörg Schwenk. This attack allows a MITM to effect a limited break of the integrity of the early encrypted SSH transport protocol by sending extra messages prior to the commencement of encryption, and deleting an equal number of consecutive messages immediately after encryption starts. A peer SSH client/server would not be able to detect that messages were deleted. - [CVE-2023-51384] ssh-agent(1): when adding PKCS#11-hosted private keys while specifying destination constraints, if the PKCS#11 token returned multiple keys then only the first key had the constraints applied. Use of regular private keys, FIDO tokens and unconstrained keys are unaffected. - [CVE-2023-51385] ssh(1): if an invalid user or hostname that contained shell metacharacters was passed to ssh(1), and a ProxyCommand, LocalCommand directive or "match exec" predicate referenced the user or hostname via %u, %h or similar expansion token, then an attacker who could supply arbitrary user/hostnames to ssh(1) could potentially perform command injection depending on what quoting was present in the user-supplied ssh_config(5) directive. OpenSSH 9.6 now bans most shell metacharacters from user and hostnames supplied via the command-line. - ssh(1), sshd(8): the RFC4254 connection/channels protocol provides a TCP-like window mechanism that limits the amount of data that can be sent without acceptance from the peer. In cases where this limit was exceeded by a non-conforming peer SSH implementation, ssh(1)/sshd(8) previously discarded the extra data. From OpenSSH 9.6, ssh(1)/sshd(8) will now terminate the connection if a peer exceeds the window limit by more than a small grace factor. This change should have no effect of SSH implementations that follow the specification. - ssh(1): add a %j token that expands to the configured ProxyJump hostname (or the empty string if this option is not being used) that can be used in a number of ssh_config(5) keywords. - ssh(1): add ChannelTimeout support to the client, mirroring the same option in the server and allowing ssh(1) to terminate quiescent channels. - ssh(1), sshd(8), ssh-add(1), ssh-keygen(1): add support for reading ED25519 private ke
[Touch-packages] [Bug 2047082] Re: upgrading openssh-server always shows error: rescue-ssh.target is a disabled or a static unit not running, not starting it.
This bug was fixed in the package openssh - 1:9.6p1-3ubuntu1 --- openssh (1:9.6p1-3ubuntu1) noble; urgency=medium * Merge with Debian unstable (LP: #2040406). Remaining changes: - debian/rules: modify dh_installsystemd invocations for socket-activated sshd. - debian/openssh-server.postinst: handle migration of sshd_config options to systemd socket options on upgrade. - debian/README.Debian: document systemd socket activation. - debian/patches/socket-activation-documentation.patch: Document in sshd_config(5) that ListenAddress and Port no longer work. - debian/openssh-server.templates: include debconf prompt explaining when migration cannot happen due to multiple ListenAddress values. - debian/.gitignore: drop file. - debian/openssh-server.postrm: remove systemd drop-ins for socket-activated sshd on purge. - debian/openssh-server.ucf-md5sum: update for Ubuntu delta - debian/openssh-server.tmpfile,debian/systemd/ssh.service: Move /run/sshd creation out of the systemd unit to a tmpfile config so that sshd can be run manually if necessary without having to create this directory by hand. - debian/patches/systemd-socket-activation.patch: Fix sshd re-execution behavior when socket activation is used. - debian/tests/systemd-socket-activation: Add autopkgtest for systemd socket activation functionality. - d/p/test-set-UsePAM-no-on-some-tests.patch: set UsePAM=no for some tests. * Dropped changes, fixed upstream: - d/p/fix-ftbfs-with-zlib13.patch: fix ftbfs when using zlib 1.3 (LP #2049552) openssh (1:9.6p1-3) unstable; urgency=medium * Allow passing extra ssh-agent arguments via "/usr/lib/openssh/agent-launch start", making it possible to override things like identity lifetime using a systemd drop-in unit (closes: #1059639). * Don't try to start rescue-ssh.target in postinst (LP: #2047082). openssh (1:9.6p1-2) unstable; urgency=medium * Improve detection of broken -fzero-call-used-regs=used (see https://bugzilla.mindrot.org/show_bug.cgi?id=3645; fixes build on ppc64/ppc64el). openssh (1:9.6p1-1) unstable; urgency=medium * Use single quotes in suggested ssh-keygen commands (closes: #1057835). * Debconf translations: - Catalan (thanks, Pablo Huguet; closes: #1049995). * New upstream release (https://www.openssh.com/releasenotes.html#9.6p1): - [CVE-2023-48795] ssh(1), sshd(8): implement protocol extensions to thwart the so-called "Terrapin attack" discovered by Fabian Bäumer, Marcus Brinkmann and Jörg Schwenk. This attack allows a MITM to effect a limited break of the integrity of the early encrypted SSH transport protocol by sending extra messages prior to the commencement of encryption, and deleting an equal number of consecutive messages immediately after encryption starts. A peer SSH client/server would not be able to detect that messages were deleted. - [CVE-2023-51384] ssh-agent(1): when adding PKCS#11-hosted private keys while specifying destination constraints, if the PKCS#11 token returned multiple keys then only the first key had the constraints applied. Use of regular private keys, FIDO tokens and unconstrained keys are unaffected. - [CVE-2023-51385] ssh(1): if an invalid user or hostname that contained shell metacharacters was passed to ssh(1), and a ProxyCommand, LocalCommand directive or "match exec" predicate referenced the user or hostname via %u, %h or similar expansion token, then an attacker who could supply arbitrary user/hostnames to ssh(1) could potentially perform command injection depending on what quoting was present in the user-supplied ssh_config(5) directive. OpenSSH 9.6 now bans most shell metacharacters from user and hostnames supplied via the command-line. - ssh(1), sshd(8): the RFC4254 connection/channels protocol provides a TCP-like window mechanism that limits the amount of data that can be sent without acceptance from the peer. In cases where this limit was exceeded by a non-conforming peer SSH implementation, ssh(1)/sshd(8) previously discarded the extra data. From OpenSSH 9.6, ssh(1)/sshd(8) will now terminate the connection if a peer exceeds the window limit by more than a small grace factor. This change should have no effect of SSH implementations that follow the specification. - ssh(1): add a %j token that expands to the configured ProxyJump hostname (or the empty string if this option is not being used) that can be used in a number of ssh_config(5) keywords. - ssh(1): add ChannelTimeout support to the client, mirroring the same option in the server and allowing ssh(1) to terminate quiescent channels. - ssh(1), sshd(8), ssh-add(1), ssh-keygen(1): add support for reading ED25519 private ke
[Touch-packages] [Bug 2040406] Re: Merge openssh from Debian unstable for noble
This bug was fixed in the package openssh - 1:9.6p1-3ubuntu1 --- openssh (1:9.6p1-3ubuntu1) noble; urgency=medium * Merge with Debian unstable (LP: #2040406). Remaining changes: - debian/rules: modify dh_installsystemd invocations for socket-activated sshd. - debian/openssh-server.postinst: handle migration of sshd_config options to systemd socket options on upgrade. - debian/README.Debian: document systemd socket activation. - debian/patches/socket-activation-documentation.patch: Document in sshd_config(5) that ListenAddress and Port no longer work. - debian/openssh-server.templates: include debconf prompt explaining when migration cannot happen due to multiple ListenAddress values. - debian/.gitignore: drop file. - debian/openssh-server.postrm: remove systemd drop-ins for socket-activated sshd on purge. - debian/openssh-server.ucf-md5sum: update for Ubuntu delta - debian/openssh-server.tmpfile,debian/systemd/ssh.service: Move /run/sshd creation out of the systemd unit to a tmpfile config so that sshd can be run manually if necessary without having to create this directory by hand. - debian/patches/systemd-socket-activation.patch: Fix sshd re-execution behavior when socket activation is used. - debian/tests/systemd-socket-activation: Add autopkgtest for systemd socket activation functionality. - d/p/test-set-UsePAM-no-on-some-tests.patch: set UsePAM=no for some tests. * Dropped changes, fixed upstream: - d/p/fix-ftbfs-with-zlib13.patch: fix ftbfs when using zlib 1.3 (LP #2049552) openssh (1:9.6p1-3) unstable; urgency=medium * Allow passing extra ssh-agent arguments via "/usr/lib/openssh/agent-launch start", making it possible to override things like identity lifetime using a systemd drop-in unit (closes: #1059639). * Don't try to start rescue-ssh.target in postinst (LP: #2047082). openssh (1:9.6p1-2) unstable; urgency=medium * Improve detection of broken -fzero-call-used-regs=used (see https://bugzilla.mindrot.org/show_bug.cgi?id=3645; fixes build on ppc64/ppc64el). openssh (1:9.6p1-1) unstable; urgency=medium * Use single quotes in suggested ssh-keygen commands (closes: #1057835). * Debconf translations: - Catalan (thanks, Pablo Huguet; closes: #1049995). * New upstream release (https://www.openssh.com/releasenotes.html#9.6p1): - [CVE-2023-48795] ssh(1), sshd(8): implement protocol extensions to thwart the so-called "Terrapin attack" discovered by Fabian Bäumer, Marcus Brinkmann and Jörg Schwenk. This attack allows a MITM to effect a limited break of the integrity of the early encrypted SSH transport protocol by sending extra messages prior to the commencement of encryption, and deleting an equal number of consecutive messages immediately after encryption starts. A peer SSH client/server would not be able to detect that messages were deleted. - [CVE-2023-51384] ssh-agent(1): when adding PKCS#11-hosted private keys while specifying destination constraints, if the PKCS#11 token returned multiple keys then only the first key had the constraints applied. Use of regular private keys, FIDO tokens and unconstrained keys are unaffected. - [CVE-2023-51385] ssh(1): if an invalid user or hostname that contained shell metacharacters was passed to ssh(1), and a ProxyCommand, LocalCommand directive or "match exec" predicate referenced the user or hostname via %u, %h or similar expansion token, then an attacker who could supply arbitrary user/hostnames to ssh(1) could potentially perform command injection depending on what quoting was present in the user-supplied ssh_config(5) directive. OpenSSH 9.6 now bans most shell metacharacters from user and hostnames supplied via the command-line. - ssh(1), sshd(8): the RFC4254 connection/channels protocol provides a TCP-like window mechanism that limits the amount of data that can be sent without acceptance from the peer. In cases where this limit was exceeded by a non-conforming peer SSH implementation, ssh(1)/sshd(8) previously discarded the extra data. From OpenSSH 9.6, ssh(1)/sshd(8) will now terminate the connection if a peer exceeds the window limit by more than a small grace factor. This change should have no effect of SSH implementations that follow the specification. - ssh(1): add a %j token that expands to the configured ProxyJump hostname (or the empty string if this option is not being used) that can be used in a number of ssh_config(5) keywords. - ssh(1): add ChannelTimeout support to the client, mirroring the same option in the server and allowing ssh(1) to terminate quiescent channels. - ssh(1), sshd(8), ssh-add(1), ssh-keygen(1): add support for reading ED25519 private ke
[Touch-packages] [Bug 2050033] Re: gettext: msgfmt --java2 does not support Java 21
This bug was fixed in the package gettext - 0.21-14ubuntu1 --- gettext (0.21-14ubuntu1) noble; urgency=medium * Update patches to support Java 21 (LP: #2050033): - d/p/12-in-language-java-avoid-stack-overflow.patch: cherry-pick upstream patch to resolve Java 21 FTBFS. - d/p/07-java-17-support.patch: add Java versions, set release level 8. -- Vladimir Petko Mon, 22 Jan 2024 13:33:17 +1300 ** Changed in: gettext (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/2050033 Title: gettext: msgfmt --java2 does not support Java 21 Status in gettext package in Ubuntu: Fix Released Status in gettext package in Debian: New Bug description: When building 'ssl-utils-clojure' package with Java 21 as default, the build fails with the following trace: -- Applying task i18n to [make] Running 'make i18n' make[1]: *** [debian/rules:19: override_dh_auto_build] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:12: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 -- Running make in the build chroot produces the following error: --- msgfmt --java2 -d resources -r puppetlabs.ssl_utils.Messages -l eo locales/eo.po msgfmt: Java compiler not found, try installing gcj or set $JAVAC msgfmt: compilation of Java class failed, please try --verbose or set $JAVAC make: *** [dev-resources/Makefile.i18n:94: resources/puppetlabs/ssl_utils/Messages_eo.class] Error 1 --- It appears that gettext package does not support Java 21. Note: gettext 0.22.4 refactors Java support. This delta can be safely dropped after a new upstream release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gettext/+bug/2050033/+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 2045494] Re: did not upgrade to 23.10
[Expired for apt (Ubuntu) because there has been no activity for 60 days.] ** Changed in: apt (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2045494 Title: did not upgrade to 23.10 Status in apt package in Ubuntu: Expired Bug description: root@localhost:/home/larsmartin# sudo apt update && sudo apt upgrade Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease Hit:2 http://archive.ubuntu.com/ubuntu jammy-updates InRelease Hit:3 http://archive.ubuntu.com/ubuntu jammy-backports InRelease Hit:4 http://archive.ubuntu.com/ubuntu jammy-security InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done 1 package can be upgraded. Run 'apt list --upgradable' to see it. Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done Get more security updates through Ubuntu Pro with 'esm-apps' enabled: exo-utils libopenexr25 libpostproc55 libavcodec58 libavutil56 libswscale5 xrdp libexo-2-0 libswresample3 libavformat58 libexo-common libavfilter7 Learn more about Ubuntu Pro at https://ubuntu.com/pro The following packages have been kept back: libayatana-appindicator3-1 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. root@localhost:/home/larsmartin# sudo do-release-upgrade Checking for a new Ubuntu release Please install all available updates for your release before upgra ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apt 2.4.11 ProcVersionSignature: Ubuntu 5.15.0-89.99-generic 5.15.126 Uname: Linux 5.15.0-89-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sun Dec 3 09:21:14 2023 InstallationDate: Installed on 2020-07-05 (1245 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: apt UpgradeStatus: Upgraded to jammy on 2022-03-24 (618 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2045494/+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 2052295] Re: autopkgtest unshare-qemuwrapper failing on amd64
This bug was fixed in the package cpio - 2.15+dfsg-1ubuntu1 --- cpio (2.15+dfsg-1ubuntu1) noble; urgency=medium * d/prerm, d/postinst: fix path according to /usr movement (LP: #2052295) -- Miriam España Acebal Fri, 02 Feb 2024 13:03:45 +0100 ** Changed in: cpio (Ubuntu Noble) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cpio in Ubuntu. https://bugs.launchpad.net/bugs/2052295 Title: autopkgtest unshare-qemuwrapper failing on amd64 Status in cpio package in Ubuntu: Fix Released Status in sbuild package in Ubuntu: New Status in cpio source package in Noble: Fix Released Status in sbuild source package in Noble: New Status in cpio package in Debian: New Bug description: While watching Noble openssh migration, I saw this test failing and marking amd64 as regression. Log : https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest- noble/noble/amd64/s/sbuild/20240201_000224_2a4c6@/log.gz Relevant part of the log: 1565s Chrooting into /tmp/mmdebstrap.bsT6cbiWIs/ 1565s Setting up cpio (2.15+dfsg-1) ... 1565s update-alternatives: error: alternative path /bin/mt-gnu doesn't exist 1565s dpkg: error processing package cpio (--configure): 1565s installed cpio package post-installation script subprocess returned error exit status 2 It can be reproduced locally, too. The most recent test working is from 01/08/2024: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/s/sbuild/20240108_203545_af566@/log.gz The cpio version in the immediately log above is lower. The same (working) part is: 2188s Chrooting into /tmp/mmdebstrap.qSEp1fU8f3/ 2188s Setting up cpio (2.14+dfsg-1) ... 2188s update-alternatives: using /bin/mt-gnu to provide /bin/mt (mt) in auto mode cpio diff : https://launchpadlibrarian.net/709448424/cpio_2.14+dfsg-1_2.15+dfsg-1.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpio/+bug/2052295/+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 2047457] Re: GLib-GIO-CRITICAL **: GFileInfo created without standard::symlink-target sort-order
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: glib-networking (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib-networking in Ubuntu. https://bugs.launchpad.net/bugs/2047457 Title: GLib-GIO-CRITICAL **: GFileInfo created without standard::symlink- target sort-order Status in glib-networking package in Ubuntu: Confirmed Bug description: Just noticed ```.xsession-errors``` somewhat big with a timestamp from today. After checking the log out I mostly see: ``` (caja:2681): GLib-GIO-CRITICAL **: 17:16:08.920: GFileInfo created without standard::sort-order (caja:2681): GLib-GIO-CRITICAL **: 17:16:08.920: file ../../../gio/gfileinfo.c: line 2108 (g_file_info_get_sort_order): should not be reached (caja:2681): GLib-GIO-CRITICAL **: 17:16:08.920: GFileInfo created without standard::symlink-target (caja:2681): GLib-GIO-CRITICAL **: 17:16:08.920: file ../../../gio/gfileinfo.c: line 2062 (g_file_info_get_symlink_target): should not be reached (caja:2681): GLib-GIO-CRITICAL **: 17:16:11.722: GFileInfo created without standard::sort-order (caja:2681): GLib-GIO-CRITICAL **: 17:16:11.723: file ../../../gio/gfileinfo.c: line 2108 (g_file_info_get_sort_order): should not be reached (caja:2681): GLib-GIO-CRITICAL **: 17:16:11.723: GFileInfo created without standard::symlink-target (caja:2681): GLib-GIO-CRITICAL **: 17:16:11.723: file ../../../gio/gfileinfo.c: line 2062 (g_file_info_get_symlink_target): should not be reached (caja:2681): GLib-GIO-CRITICAL **: 17:16:14.527: GFileInfo created without standard::sort-order (caja:2681): GLib-GIO-CRITICAL **: 17:16:14.527: file ../../../gio/gfileinfo.c: line 2108 (g_file_info_get_sort_order): should not be reached (caja:2681): GLib-GIO-CRITICAL **: 17:16:14.527: GFileInfo created without standard::symlink-target (caja:2681): GLib-GIO-CRITICAL **: 17:16:14.527: file ../../../gio/gfileinfo.c: line 2062 (g_file_info_get_symlink_target): should not be reached ``` Going through that log it is not always "caja" showing up. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: glib-networking 2.78.0-1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue Dec 26 17:16:53 2023 InstallationDate: Installed on 2023-04-14 (256 days ago) InstallationMedia: Ubuntu-MATE 22.10 "Kinetic Kudu" - Release amd64 (20221018) SourcePackage: glib-networking UpgradeStatus: Upgraded to mantic on 2023-10-13 (74 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/2047457/+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 1971090] Re: OS fully crashes when I exit an app folder.
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1971090 Title: OS fully crashes when I exit an app folder. Status in vim package in Ubuntu: Expired Bug description: When I leave a app folder in a specific place, the OS crashes and I need to do a force shut down to restart. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: vim (not installed) ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 1 10:17:57 2022 InstallationDate: Installed on 2021-05-31 (334 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1971090/+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 1785813] Re: gvim crashes when clicking on manager to shade the window
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1785813 Title: gvim crashes when clicking on manager to shade the window Status in vim package in Ubuntu: Expired Bug description: I am running xubuntu 18.04 and when I click the "shade" button of gvim frame the window disappears with gvim crashing. It happens only to gvim all other windows I've tested are ok ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vim-gtk3 2:8.0.1453-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Aug 7 14:08:10 2018 InstallationDate: Installed on 2017-11-02 (278 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) SourcePackage: vim UpgradeStatus: Upgraded to bionic on 2018-04-30 (99 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1785813/+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 1745902] Re: gvim will freeze when partial window is out of current desktop using Wayland
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1745902 Title: gvim will freeze when partial window is out of current desktop using Wayland Status in vim package in Ubuntu: Expired Bug description: Reproduce Steps: 0. Login ubuntu 17.10 using Wayland 1. Open Gvim 2. Move Gvim window to partially out of current desktop 3. Press i to change current mode to insert mode <- problem 4. Input some chars and new lines 5. Press ESC to return to normal mode 6. Press j or k to move cursor <- problem The problem is: gvim window will freeze unless: 1. you move your mouse 2. wait a few seconds ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: vim-gtk 2:8.0.0197-4ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 29 10:43:36 2018 InstallationDate: Installed on 2016-04-24 (644 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: vim UpgradeStatus: Upgraded to artful on 2017-10-23 (98 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1745902/+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 1721280] Re: vim.gtk3 crashed with SIGSEGV in __new_sem_wait_fast()
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1721280 Title: vim.gtk3 crashed with SIGSEGV in __new_sem_wait_fast() Status in vim package in Ubuntu: Expired Bug description: Might be related to one of my extensions camelcasemotion lightline.vim vim-fetch inorirust.vim validator.vim vim-fugitive Please also double check that it's not a duplicate of #96263 "vim crashed with sigsegv" ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: vim-gtk3 2:8.0.0197-4ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 4 16:13:33 2017 ExecutablePath: /usr/bin/vim.gtk3 InstallationDate: Installed on 2017-05-30 (127 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. ProcCmdline: vim update_test_projects.sh Signal: 11 SourcePackage: vim StacktraceTop: kill () at ../sysdeps/unix/syscall-template.S:84 mch_exit () getout () () at /lib/x86_64-linux-gnu/libpthread.so.0 __new_sem_wait_fast (definitive_result=0, sem=0x0) at sem_waitcommon.c:135 Title: vim.gtk3 crashed with SIGSEGV in kill() UpgradeStatus: Upgraded to artful on 2017-09-25 (8 days ago) UserGroups: dialout plugdev sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1721280/+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 1647771] Re: Undefined variable in vim netrw when netrw_browse_split = 3
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1647771 Title: Undefined variable in vim netrw when netrw_browse_split = 3 Status in vim package in Ubuntu: Expired Bug description: To reproduce, open the netrw explorer in a new tab, and set opened files to go to a new tab: :let g:netrw_browse_split = 3 :Texplore When the user selects a file from the explorer with Enter, this error appears: Error detected while processing function 20_NetrwBrowseChgDir: line 135: E121: Undefined variable: b:netrw_curdir And this is displayed for a second: Invalid arguments for function SetRexDir Saw this after upgrade to Ubuntu 16.04 (vim 7.4.1689-3ubuntu1.2). The error didn't show with vim 7.4.052-1ubuntu3.1 on Ubuntu-14.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1647771/+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 1535809] Re: Segfaults in current vim in xenial (16.04)
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1535809 Title: Segfaults in current vim in xenial (16.04) Status in vim package in Ubuntu: Expired Bug description: Version: 2:7.4.826-1ubuntu2 I can't tell what causes it, but i haven't gotten such segfaults in 14.04 and my vimrc was the same. From vims changelog i see some segfaulting has been fixed in newer revisions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1535809/+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 1772050] Re: 't' and 'T' command used in vi editor is not working its working only for first occurrence of character.
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1772050 Title: 't' and 'T' command used in vi editor is not working its working only for first occurrence of character. Status in vim package in Ubuntu: Expired Bug description: 't' and 'T' command used in vi editor is not working its working only for first occurrence of character. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.14 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Fri May 18 20:28:09 2018 InstallationDate: Installed on 2018-05-17 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1772050/+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 1584539] Re: 16.04 regression: exceptions in ruby code in plugins have started causing vim to segfault
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1584539 Title: 16.04 regression: exceptions in ruby code in plugins have started causing vim to segfault Status in vim package in Ubuntu: Expired Bug description: In 14.04, an exception in the ruby code of a plugin caused the error to be printed to stderr, after which vim would launch, skipping the offending plugin: Error detected while processing /mnt/terra/home/simon/dev/vim-livecoding/plugin/livecoding.vim: line 37: NameError: undefined local variable or method `undefined_method_causing_an_exception' for main:Object Press ENTER or type command to continue But in 16.04, the same thing causes vim to segfault: Vim: Caught deadly signal SEGV Vim: Finished. Segmentation fault (core dumped) --- Vim version in 14.04: VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Jan 2 2014 19:39:59) Included patches: 1-52 Modified by pkg-vim-maintain...@lists.alioth.debian.org Compiled by buildd@ Huge version with GTK2 GUI. Vim version in 16.04: VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Apr 08 2016 11:38:28) Included patches: 1-1689 Modified by pkg-vim-maintain...@lists.alioth.debian.org Compiled by pkg-vim-maintain...@lists.alioth.debian.org Huge version with GTK2 GUI. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: vim-gtk 2:7.4.1689-3ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Sun May 22 22:33:45 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2015-04-25 (392 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: vim UpgradeStatus: Upgraded to xenial on 2016-05-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1584539/+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 1499899] Re: Gvim displays lots of scary messages about UNITY_GTK_IS_MENU_SHELL
[Expired for unity (Ubuntu) because there has been no activity for 60 days.] ** Changed in: unity (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1499899 Title: Gvim displays lots of scary messages about UNITY_GTK_IS_MENU_SHELL Status in Unity: Incomplete Status in unity package in Ubuntu: Expired Status in vim package in Ubuntu: Expired Bug description: When launched from a terminal the widely used text editor gvim displays lots WARNING and CRITICAL messages such as: ** (gvim:3608): WARNING **: (../../../lib/unity-gtk-menu- shell.c:176):unity_gtk_menu_shell_show_item: code should not be reached ** (gvim:3608): CRITICAL **: unity_gtk_menu_shell_handle_item_notify: assertion 'UNITY_GTK_IS_MENU_SHELL (shell)' failed This did not happen in 15.04. It is a most embarrassing bug. Gvim is an essential tool for many users. I am using Ubuntu 15.10 Beta 2. $ lsb_release -rd Description: Ubuntu Wily Werewolf (development branch) Release: 15.10 $ apt-cache policy vim-gnome vim-gnome: Installed: 2:7.4.712-2ubuntu3 Candidate: 2:7.4.712-2ubuntu3 Version table: *** 2:7.4.712-2ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy vim-gtk vim-gtk: Installed: 2:7.4.712-2ubuntu3 Candidate: 2:7.4.712-2ubuntu3 Version table: *** 2:7.4.712-2ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ wily/universe amd64 Packages 100 /var/lib/dpkg/status I expected to be able to use Gvim. Now Gvim pollutes the terminal with scary messages, and disturbs the messages shown by other programs running in the terminal. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: vim-gnome 2:7.4.712-2ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1 Uname: Linux 4.2.0-11-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 26 00:40:37 2015 InstallationDate: Installed on 2015-09-25 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1499899/+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 1499899] Re: Gvim displays lots of scary messages about UNITY_GTK_IS_MENU_SHELL
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1499899 Title: Gvim displays lots of scary messages about UNITY_GTK_IS_MENU_SHELL Status in Unity: Incomplete Status in unity package in Ubuntu: Expired Status in vim package in Ubuntu: Expired Bug description: When launched from a terminal the widely used text editor gvim displays lots WARNING and CRITICAL messages such as: ** (gvim:3608): WARNING **: (../../../lib/unity-gtk-menu- shell.c:176):unity_gtk_menu_shell_show_item: code should not be reached ** (gvim:3608): CRITICAL **: unity_gtk_menu_shell_handle_item_notify: assertion 'UNITY_GTK_IS_MENU_SHELL (shell)' failed This did not happen in 15.04. It is a most embarrassing bug. Gvim is an essential tool for many users. I am using Ubuntu 15.10 Beta 2. $ lsb_release -rd Description: Ubuntu Wily Werewolf (development branch) Release: 15.10 $ apt-cache policy vim-gnome vim-gnome: Installed: 2:7.4.712-2ubuntu3 Candidate: 2:7.4.712-2ubuntu3 Version table: *** 2:7.4.712-2ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy vim-gtk vim-gtk: Installed: 2:7.4.712-2ubuntu3 Candidate: 2:7.4.712-2ubuntu3 Version table: *** 2:7.4.712-2ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ wily/universe amd64 Packages 100 /var/lib/dpkg/status I expected to be able to use Gvim. Now Gvim pollutes the terminal with scary messages, and disturbs the messages shown by other programs running in the terminal. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: vim-gnome 2:7.4.712-2ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1 Uname: Linux 4.2.0-11-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 26 00:40:37 2015 InstallationDate: Installed on 2015-09-25 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1499899/+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 1394891] Re: evim search fails with message: "E486: Pattern not found: \\/\c" followed by the string searched for
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1394891 Title: evim search fails with message: "E486: Pattern not found: \\/\c" followed by the string searched for Status in vim package in Ubuntu: Expired Bug description: Ubuntu Trusty 64 bit system built from the mini.iso with Openbox as the WM and sole DE as well. Vim version 2:7.4.052-1ubuntu3. Recently, search has started failing about half the time. In Evim, if I search for "some string that IS there somewhere" I'll get the following message: E486: Pattern not found: \\/\csome string that IS there somewhere as if it had prepended some stuff to what I what I wanted to search for and searched for that instead. Whenever it does this it is always the same string that gets prepended: \\/\c Seems the longer the string the more likely it is to happen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1394891/+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 1334168] Re: vim defaults for tm and ttm are wrong
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1334168 Title: vim defaults for tm and ttm are wrong Status in vim package in Ubuntu: Expired Bug description: While scouring the net for info on curious lag in vim that can eat keystrokes (devastating over a laggy link, which is one of the primary situations where vim is useful), every conversation pointed me to `:help ttm`, which says: A useful setting would be :set timeout timeoutlen=3000 ttimeoutlen=100 (time out on mapping after three seconds, time out on key codes after a tenth of a second). So it appears that insead of putting the correct defaults in as the defaults, vim chose to bury the information deep inside the documentation. As a distro packaging vim, we have an opportunity to fix this. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: vim 2:7.4.052-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jun 25 10:01:05 2014 InstallationDate: Installed on 2014-05-29 (26 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1334168/+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 1314238] Re: Account logged off when gvim is started from terminal
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1314238 Title: Account logged off when gvim is started from terminal Status in vim package in Ubuntu: Expired Bug description: The issue: When I open a terminal and start gvim with gvim command, I'm immediately logged off. Before the login dialog appears, a text-only framebuffer appears briefly with nothing but cursor blinking on the first line, which leads me to believe it's an Unity or X crash. I have just installed a fresh copy of 14.04. unity version 7.2.0+14.04.20140416-0ubuntu1 vim-runtime version 2:7.4.052-1ubuntu3 This happens with both vim-gtk and vim-gnome packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1314238/+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 1305778] Re: Misinterpretation of key sequence
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1305778 Title: Misinterpretation of key sequence Status in vim package in Ubuntu: Expired Bug description: Ubuntu 13.10 Vim: Installed: 2:7.4.000-1ubuntu2 Entering the commands to leave insert mode & insert a new line above the current one, beginning with certain letters, results in punctuation on the current line instead. To reproduce: Start vim, *quickly* type the keys: iOm Expected result: New line created above the current one with the letter 'm' in it Actual result: Hyphen inserted on current line Also affects: Letters j,k,n,o j gives *, k gives +, m gives -, n gives ., o gives / Vim version: 7.4 (as installed by Ubuntu 13.10) Happens on my machine, my co-worker's machine, several VMs and to some (not all) of the people I asked about it on IRC. Definitely requires that the typing is done quickly. Causes me problems very frequently because I write a lot of Perl and when I go to declare a variable, I get "-y $foo" on the current line instead of "my $foo" on the previous line. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: vim 2:7.4.000-1ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Thu Apr 10 11:51:03 2014 InstallationDate: Installed on 2013-11-27 (134 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1305778/+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 1195448] Re: Gvim problem
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1195448 Title: Gvim problem Status in vim package in Ubuntu: Expired Bug description: Upon lauchaing GVIM to update a shell file I get (gvim:335): GLib-GObject-WARNING **: cannot retrieve class for invalid (unclassed) type `' The file is loaded without problem. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: vim-gnome 2:7.3.429-2ubuntu2.1 ProcVersionSignature: Ubuntu 3.2.0-48.74-generic-pae 3.2.46 Uname: Linux 3.2.0-48-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.3 Architecture: i386 Date: Thu Jun 27 12:54:21 2013 ExecutablePath: /usr/bin/vim.gnome InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) MarkForUpload: True SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1195448/+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 1282345] Re: vim crashes on ruby files with very long lines
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1282345 Title: vim crashes on ruby files with very long lines Status in vim package in Ubuntu: Expired Bug description: 1. edit a file to be called test in vim: vi test. 2. Insert the following line: vln = "Nowisthetimeforareallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyr eallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallreallyreallyreallyreallyreallyy" 3. Play with the file to reassure you have no problem editing it. 4. Exit vi and mv test test.rb. 5. vi test.rb. Note that now the file freezes up. You can exit the terminal, and try going back and forth. It is 100%. When the file is called test.rb, it freezes up, apparently from formatting for ruby. When it is called just test, it is fine. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: vim 2:7.4.000-1ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Wed Feb 19 17:37:36 2014 InstallationDate: Installed on 2013-10-25 (117 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vim UpgradeStatus: Upgraded to saucy on 2013-10-26 (117 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1282345/+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 1074454] Re: resize during insert problem
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1074454 Title: resize during insert problem Status in vim package in Ubuntu: Expired Bug description: resize during insert seems to cause a problem. to reproduce: create a textfile using the 21 lines of text given below. resize an xterm to 12 lines long and 80 characters wide. in the xterm, edit (vim) the textfile. position the cursor on the / preceeding "vmlinuz", and type cB/ (with no escape)(still in insert mode) resize the xterm to 10 lines by 80 characters. vim is now in an inconsistent state. the first visible cue is the disappearance of text following the cursor. further inserted characters appear to insert on the wrong line. as things progress it may recover itself, or it may ABRT or SEGV. for example if at this point i hit (end the insert) type :ls (with no CR) enlarge the window i get Vim: Caught deadly signal SEGV Vim: preserving files... and it hangs thus. uuid 960c92bd-69d3-415f-93b6-2242187e3557 uuid 960c92bd-69d3-415f-93b6-2242187e3557 uuid 960c92bd-69d3-415f-93b6-2242187e3557 uuid 960c92bd-69d3-415f-93b6-2242187e3557 uuid 960c92bd-69d3-415f-93b6-2242187e3557 uuid 960c92bd-69d3-415f-93b6-2242187e3557 uuid 960c92bd-69d3-415f-93b6-2242187e3557 uuid 960c92bd-69d3-415f-93b6-2242187e3557 uuid 960c92bd-69d3-415f-93b6-2242187e3557 uuid 960c92bd-69d3-415f-93b6-2242187e3557 kernel/SL-60-i386/Install-DVD/vmlinuz quiet panic=30 method=hd:sda7: ksdevice= initrd/SL-60-i386/Install-DVD/initrd.img initrd/SL-60-i386/Install-DVD/initrd.img initrd/SL-60-i386/Install-DVD/initrd.img initrd/SL-60-i386/Install-DVD/initrd.img initrd/SL-60-i386/Install-DVD/initrd.img initrd/SL-60-i386/Install-DVD/initrd.img initrd/SL-60-i386/Install-DVD/initrd.img initrd/SL-60-i386/Install-DVD/initrd.img initrd/SL-60-i386/Install-DVD/initrd.img initrd/SL-60-i386/Install-DVD/initrd.img $ lsb_release -rd Description:Ubuntu 12.10 Release:12.10 $ apt-cache policy vim vim: Installed: 2:7.3.547-4ubuntu1 Candidate: 2:7.3.547-4ubuntu1 Version table: *** 2:7.3.547-4ubuntu1 0 500 http://ie.archive.ubuntu.com/ubuntu/ quantal/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1074454/+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 1157538] Re: vim.basic crashed with SIGSEGV in modify_fname()
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1157538 Title: vim.basic crashed with SIGSEGV in modify_fname() Status in vim package in Ubuntu: Expired Bug description: creating a desktop launcher ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: vim 2:7.3.547-6ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-12.21-generic 3.8.2 Uname: Linux 3.8.0-12-generic i686 ApportVersion: 2.9.1-0ubuntu1 Architecture: i386 CrashCounter: 1 Date: Wed Mar 20 04:49:43 2013 ExecutablePath: /usr/bin/vim.basic InstallationDate: Installed on 2013-03-15 (4 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130314) MarkForUpload: True ProcCmdline: vim Signal: 11 SourcePackage: vim StacktraceTop: modify_fname () _r_debug () ?? () ?? () Title: vim.basic crashed with SIGSEGV in modify_fname() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1157538/+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 808941] Re: gvim in ubuntu is slow when switching tabs or navigating lines
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/808941 Title: gvim in ubuntu is slow when switching tabs or navigating lines Status in vim package in Ubuntu: Expired Bug description: It's been like this forever really. Because I worked both on Ubuntu and MacOSX interchangeably I didn't care as much. Now I think maybe it's time to finally find out what is wrong with it. THE PROBLEM: when I switch tabs or navigate the lines with arrows or J,K keys and when I do it repeatedly (as if when trying to find the right tab holding Ctrl and hitting Tab) it seems to be delaying the action. When I stop hitting the keys gvim may still be finishing the operations (for instance, I stop hitting Ctrl+Tab, gvim may switch 5 more tabs - the number depends on how long I've been hitting Ctrl+Tab - before it stops). MacVim with similar settings in .vimrc works just fine. The delays are present both when Compiz is turned off and turned on. Any ideas? ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: vim-gnome 2:7.3.035+hg~8fdc1210-1ubuntu7 ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic 2.6.39-rc5 Uname: Linux 2.6.39-0-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Jul 11 22:24:32 2011 ExecutablePath: /usr/bin/vim.gnome ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vim UpgradeStatus: Upgraded to natty on 2011-06-05 (36 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/808941/+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 938469] Re: vim cannot regain control of mouse
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/938469 Title: vim cannot regain control of mouse Status in vim package in Ubuntu: Expired Bug description: In Precise, vim is unable to reassert control of the mouse once it has started. The mouse works normally upon starting vim. If it loses control of the mouse in the pseudo-terminal, however, perhaps due to being suspended with ^Z, or turning the mouse off with ':set mouse=', then vim becomes unable to regain control of the mouse when it should, such as being resumed or ':set mouse=a'. The expected behavior is that suspending should have no effect on the mouse within vim, and clearing and resetting the mouse variable should also have no effect on the mouse. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/938469/+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 788481] Re: Unity can't handle two GVIM's at the same time
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/788481 Title: Unity can't handle two GVIM's at the same time Status in vim package in Ubuntu: Expired Bug description: Binary package hint: vim When I open two gvim's at the same time (from the command prompt), only one of them has a global menu, the other does not. This is not a duplicate of: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/781180 As I see no warnings. Just the first menu works, and the second GVIM has no menu. Which also means copy & paste between gvims using menu shortcuts is broken :( SInce only one instance has a menu... Alt+E 'C' is probably one of the most common things I do with two gvims open... Take care, -stu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/788481/+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 876262] Re: Gvim launcher doesn't appear in dash; appears in launcher with bad icon
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/876262 Title: Gvim launcher doesn't appear in dash; appears in launcher with bad icon Status in vim package in Ubuntu: Expired Bug description: After installing vim-gnome a shortcut to Gvim text editor is not available in the dash. After starting it (e.g. Alt-F2 -> 'gvim') the icon it appears with in the launcher is not pretty. This is a regression from Ubuntu 11.04. /usr/share/applications/gvim.desktop exists in 11.10 and the only difference between this and the same file in 11.04 is: $ diff 11.10/gvim.desktop 11.04/gvim.desktop 75c75 < Icon=/usr/share/pixmaps/vim.svg --- > Icon=vim Furthermore, the icon used in 11.04 also exists in 11.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/876262/+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 751726] Re: gvim icon is low-res and blurry in Unity
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/751726 Title: gvim icon is low-res and blurry in Unity Status in vim package in Ubuntu: Expired Bug description: Binary package hint: vim The icon used for gvim in Unity is a low-res bitmap. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: vim-gnome 2:7.3.035+hg~8fdc1210-1ubuntu7 ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38 Uname: Linux 2.6.38-7-generic x86_64 NonfreeKernelModules: wl Architecture: amd64 Date: Tue Apr 5 20:48:39 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110329.1) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/751726/+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 627332] Re: Scroll bars do not appear correctly on new splits
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/627332 Title: Scroll bars do not appear correctly on new splits Status in vim package in Ubuntu: Expired Bug description: Binary package hint: vim-gnome vim-gnome 2:7.2.330-1ubuntu3 ubuntu 10.04.1 LTS Easiest steps to reproduce: - Open gvim - Maximise (currently reproduced under Compiz - not tried without) - Open a file with more lines than available. - :vsp Expected behaviour: New split has a scrollbar on the right Actual behaviour: Scrollbar exists, but appears to be attached to the outside of the maximised window, and thus not visible. Workaround: Restore gvim and maximise again. This is how it should originally have displayed. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: vim-gnome 2:7.2.330-1ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-24.41-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic i686 NonfreeKernelModules: fglrx Architecture: i386 Date: Tue Aug 31 11:06:43 2010 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1) ProcEnviron: PATH=(custom, user) LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: vim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/627332/+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 616858] Re: Mouse cursor in gvim is sometimes invisible
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/616858 Title: Mouse cursor in gvim is sometimes invisible Status in vim package in Ubuntu: Expired Bug description: Binary package hint: vim-gnome In some cases the mouse cursor within a gvim window disappears. It is still there, just not visible, or under the window. Left clicking and selecting text will make it reappear. Searching within gvim for matching text can (sometimes) make the cursor disappear again. This doesn't happen with every gvim window opened up, but even if it didn't happen when first opened, searching will cause it to disappear again. [opiet@doodle ~] --> lsb_release -rd Description: Ubuntu 10.04.1 LTS Release: 10.04 [opiet@doodle ~] --> [opiet@doodle ~] --> apt-cache policy vim-gnome vim-gnome: Installed: 2:7.2.330-1ubuntu3 Candidate: 2:7.2.330-1ubuntu3 Version table: *** 2:7.2.330-1ubuntu3 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status [opiet@doodle ~] --> To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/616858/+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 560217] Re: vim-gnome omnicompletion mousewheel bug
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/560217 Title: vim-gnome omnicompletion mousewheel bug Status in vim package in Ubuntu: Expired Bug description: Binary package hint: vim-gnome Huge version with GTK2-GNOME GUI version has the mousewheel broken on the omni complete popup. It works on the command version in gnome-terminal. 9.10 / vim 7.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/560217/+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 560157] Re: vim-gtk, vim-gnome menu_bar error
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/560157 Title: vim-gtk,vim-gnome menu_bar error Status in vim package in Ubuntu: Expired Bug description: Binary package hint: vim vim-gtk,vim-gnome menu_bar error, only the item was show in the menu bar. Others have no context. but, export LANG=xxx can solve the problem. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: vim-gnome 2:7.2.330-1ubuntu2 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Sun Apr 11 01:12:41 2010 ExecutablePath: /usr/bin/vim.gnome InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318) ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=zh_CN.utf8 LANGUAGE=zh_CN:zh SourcePackage: vim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/560157/+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 320700] Re: gvim rendering is slow
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/320700 Title: gvim rendering is slow Status in vim package in Ubuntu: Expired Bug description: Binary package hint: vim Rendering in gvim is very slow compared to previous Ubuntu releases. It's usable, but takes patience. I'm using vim/gvim 7.1.314-3ubuntu3.1 on Ubuntu 8.10. Others have reported this same issue on a thread from the vim mailing list. Many solutions have been tried w/o success: http://groups.google.com/group/vim_use/browse_thread/thread/dd1d8d9a799adf4a From the thread, someone provided this benchmark script: -- -- -- " Benchmark vim's redrawing speed let i = 0 while i < 2000 1 redraw $ redraw let i = i + 1 endwhile qa! -- -- -- I've run it with /etc/init.d/README as an input file (just to pick something consistent across Ubuntu machines): $ time vim -u NONE -U NONE -S test-redraw-speed.vim /etc/init.d/README real 0m5.407s user 0m0.568s sys 0m0.048s $ time gvim -u NONE -U NONE -f -S test-redraw-speed.vim /etc/init.d/README real 3m27.614s user 0m11.685s sys 0m0.312s As you can see gvim is almost 40x slower then vim (running in gnome- terminal). You'd expect gvim to be slower then vim, but not by this much. Note, from the thread, not all users experience this huge difference. Some only report 2-3x slowdown, which I'd be very happy with at this point :) I'm using the radeon X11 driver (open source) on a ThinkPad T42p, and do _not_ experience slow rendering in other apps (for example, gedit). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/320700/+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 293331] Re: vim-gnome mousewheel/scrollbar strange behavior
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/293331 Title: vim-gnome mousewheel/scrollbar strange behavior Status in vim package in Ubuntu: Expired Bug description: Binary package hint: vim-gnome 8.04 x86 and amd64 under gnome, run gvim and open a file or create text that has more lines than are shown. when hovering the mouse over the up and down buttons on the scrollbar and using the mouse scroll wheel, the bar moves according to the scroll wheel but the text moves as if you had pressed the scroll button with a left mouse click. i expect it to scroll as it would if i had the mouse over the text and used the mouse scroll wheel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/293331/+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 253576] Re: Buffer content is lost when opening file over network that doesn't exsist
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/253576 Title: Buffer content is lost when opening file over network that doesn't exsist Status in vim package in Ubuntu: Expired Bug description: Binary package hint: vim I'm using VIM 7.1.138 (netrw v109) on Ubuntu 8.04. The fastest way to see this bug happening seems to be this: 1) Start vim, type :e ftp://u...@domain.xxx//path/to/existing/file 2) Enter the password - file content appears in the buffer. 3) Type :w 4) Type :sp ftp://u...@domain.xxx//path/to/NOT/existing/file What happens after this is: 1) 2 new buffers are opened: the first one says '/path/to/NOT/existing/file: No such file or directory', and the second is the buffer for that file. You can edit that buffer and save it, so a new file is created on the server. 2) The old buffer which had the contents of ftp://u...@domain.xxx//path/to/existing/file is empty. I expect that the second consequence above is a bug. If I was in a middle of editing in one buffer and opened another which would create a new file, all my work on the first one is lost - it's impossible to undo any changes, it says 'Already at oldest change', and the old buffer is cleared and not saved on the server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/253576/+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 2016303] Re: Rebuild NSS with support for system-wide config file
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nss (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/2016303 Title: Rebuild NSS with support for system-wide config file Status in nss package in Ubuntu: Confirmed Bug description: NSS should be rebuilt with this patch: diff --git a/debian/libnss3.dirs b/debian/libnss3.dirs new file mode 100644 index ..0f796964 --- /dev/null +++ b/debian/libnss3.dirs @@ -0,0 +1 @@ +etc/nss diff --git a/debian/rules b/debian/rules index 5ab1ced0..51bee160 100755 --- a/debian/rules +++ b/debian/rules @@ -128,6 +128,8 @@ override_dh_auto_build: NSS_USE_SYSTEM_SQLITE=1 \ NSS_ENABLE_ECC=1 \ CHECKLOC= \ + POLICY_FILE=pkcs11.txt \ + POLICY_PATH=/etc/nss \ $(TOOLCHAIN) override_dh_auto_clean: The directory could be another one, of course. This will allow us to create a system-wide /etc/nss/pkcs11.txt file which could load the NSS policy module. The upstream documentation is quite poor and outdated, unfortunately: https://firefox-source-docs.mozilla.org/security/nss/legacy/nss_config_options/ https://firefox-source-docs.mozilla.org/security/nss/legacy/pkcs11/module_specs/index.html The current source code is the best documentation, and has a ton of tests that show how to use the policy module: - allow/disallow options: https://git.launchpad.net/ubuntu/+source/nss/tree/nss/lib/pk11wrap/pk11pars.c#n144 - versions and key sizes: https://git.launchpad.net/ubuntu/+source/nss/tree/nss/lib/pk11wrap/pk11pars.c#n437 - other qualifiers for algorithms (which types of signatures): https://git.launchpad.net/ubuntu/+source/nss/tree/nss/lib/pk11wrap/pk11pars.c#n451 - tons of policy tests: https://git.launchpad.net/ubuntu/+source/nss/tree/nss/tests/ssl/sslpolicy.txt and https://git.launchpad.net/ubuntu/+source/nss/tree/nss/tests/policy Here is a sample /etc/nss/pkcs11.txt which enables the policy module with certain values: library= name=Policy NSS=flags=policyOnly,moduleDB config="disallow=ALL allow=HMAC-SHA256:HMAC-SHA1:HMAC-SHA384:HMAC-SHA512:CURVE25519:SECP256R1:SECP384R1:SECP521R1:aes256-gcm:chacha20-poly1305:aes256-cbc:aes128-gcm:aes128-cbc:SHA256:SHA384:SHA512:SHA224:ECDHE-RSA:ECDHE-ECDSA:RSA:DHE-RSA:ECDSA:RSA-PSS:RSA-PKCS:tls-version-min=tls1.2:dtls-version-min=dtls1.2:DH-MIN=2048:DSA-MIN=2048:RSA-MIN=2048" The same config snippet can of course be used in ~/.pki/nssdb/pkcs11.txt or in any of the other many places we have a pkcs11.txt file on the system (hence the need for this build option: to have just one place): - firefox: ~/snap/firefox/common/.mozilla/firefox/pqx65eu1.default/pkcs11.txt - thunderbid: ~/.thunderbird/6mxs87xg.default-release/pkcs11.txt - chrome and system-provided libnss3: ~/.pki/nssdb/pkcs11.txt Note thunderbird ships its own libnss3 (zomg), and would not be affected by this build change (unless it's done in the thunderbird source package too). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/2016303/+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 1970069] Re: Annoying boot messages interfering with splash screen
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/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 2004003] Re: /etc/network/if-up.d/resolved: line 20: return: can only `return' from a function or sourced script
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ifupdown (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/2004003 Title: /etc/network/if-up.d/resolved: line 20: return: can only `return' from a function or sourced script Status in ifupdown package in Ubuntu: Confirmed Bug description: Just found the following errors in "systemctl status networking" × networking.service - Raise network interfaces Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2023-01-27 12:26:29 MSK; 3min 10s ago Docs: man:interfaces(5) Process: 3963 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE) Main PID: 3963 (code=exited, status=1/FAILURE) CPU: 147ms янв 27 12:26:29 gerbera systemd[1]: Starting Raise network interfaces... янв 27 12:26:29 gerbera ifup[3976]: /etc/network/if-up.d/resolved: line 12: mystatedir: command not found янв 27 12:26:29 gerbera ifup[3973]: /etc/network/if-up.d/resolved: line 20: return: can only `return' from a function or sourced script янв 27 12:26:29 gerbera ifup[3969]: run-parts: /etc/network/if-up.d/resolved exited with return code 2 янв 27 12:26:29 gerbera ifup[3963]: ifup: failed to bring up lo янв 27 12:26:29 gerbera systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE янв 27 12:26:29 gerbera systemd[1]: networking.service: Failed with result 'exit-code'. янв 27 12:26:29 gerbera systemd[1]: Failed to start Raise network interfaces. The error with mystatedir has been already reported as bug#1907878. However, patches there do not fix unexpected return statement. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/2004003/+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 2052489] Re: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apparmor (Ubuntu) Status: New => Confirmed -- 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/2052489 Title: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration Status in apparmor package in Ubuntu: Confirmed Bug description: Noble Mate Daily 20230205 ISO Boots up past Splash to black screen. Last errors in logs are about apparmor denied on snap desktop integration... So the graphics layer is being denied because of an apparmor error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2052489/+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 2052505] [NEW] Can't install openssl/libssl3 debug package
You have been subscribed to a public bug: I'm building an application in docker, using `mcr.microsoft.com/dotnet/runtime:7.0-jammy` (https://github.com/dotnet/dotnet- docker/blob/main/src/runtime/7.0/jammy/amd64/Dockerfile) image, that is using `amd64/buildpack-deps:jammy-curl`(https://github.com/docker- library/buildpack- deps/blob/93d6db0797f91ab674535553b7e0e762941a02d0/ubuntu/jammy/curl/Dockerfile) as base image. In my docker file I added ubuntu debug repositories and install debug packages: ```bash apt-get install -y software-properties-common echo "deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe multiverse deb http://ddebs.ubuntu.com $(lsb_release -cs)-updates main restricted universe multiverse | \ deb http://ddebs.ubuntu.com $(lsb_release -cs)-proposed main restricted universe multiverse" | \ tee -a /etc/apt/sources.list.d/ddebs.list apt install ubuntu-dbgsym-keyring apt-get update -y apt-get install -y --no-install-recommends libc6-dbg libssl3-dbgsym openssl-dbgsym libicu70-dbgsym libstdc++6-dbgsym ``` Yesterday I tried and the build isn'T running anymore with the error message: ```output 1.884 Some packages could not be installed. This may mean that you have 1.884 requested an impossible situation or if you are using the unstable 1.884 distribution that some required packages have not yet been created 1.884 or been moved out of Incoming. 1.884 The following information may help to resolve the situation: 1.884 1.887 The following packages have unmet dependencies: 2.072 libssl3-dbgsym : Depends: libssl3 (= 3.0.2-0ubuntu1.13) but 3.0.2-0ubuntu1.14 is to be installed 2.075 openssl-dbgsym : Depends: openssl (= 3.0.2-0ubuntu1.13) but 3.0.2-0ubuntu1.14 is to be installed 2.080 E: Unable to correct problems, you have held broken packages. ``` It looks like the debug symbol oackage for libssl3 and openssl should be updated. I waited 24h for mirror sync, but error still persist. ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Can't install openssl/libssl3 debug package https://bugs.launchpad.net/bugs/2052505 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl 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 2045855] Re: package bluez 5.64-0ubuntu1.1 failed to install/upgrade: end of file on stdin at conffile prompt
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2045855 Title: package bluez 5.64-0ubuntu1.1 failed to install/upgrade: end of file on stdin at conffile prompt Status in bluez package in Ubuntu: Expired Bug description: I did not recognized the error. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: bluez:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Dec 7 15:44:57 2023 ErrorMessage: end of file on stdin at conffile prompt InstallationDate: Installed on 2021-01-30 (1040 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. OptiPlex 7010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic root=UUID=1aa27b2f-8d22-4b4e-931f-bd8e304ed0d4 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.12, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: bluez Title: package bluez 5.64-0ubuntu1.1 failed to install/upgrade: end of file on stdin at conffile prompt UpgradeStatus: Upgraded to jammy on 2023-03-28 (253 days ago) dmi.bios.date: 03/25/2013 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0GY6Y8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd03/25/2013:br4.6:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0GY6Y8:rvrA00:cvnDellInc.:ct6:cvr:sku: dmi.product.name: OptiPlex 7010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:1A:7D:DA:71:03 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:1332 acl:0 sco:0 events:84 errors:0 TX bytes:3786 acl:0 sco:0 commands:81 errors:0 mtime.conffile..etc.bluetooth.input.conf: 2020-04-03T15:47:01 mtime.conffile..etc.bluetooth.main.conf: 2020-02-26T18:57:50 mtime.conffile..etc.bluetooth.network.conf: 2012-12-25T02:46:55 mtime.conffile..etc.dbus-1.system.d.bluetooth.conf: 2022-03-24T15:30:38 mtime.conffile..etc.init.d.bluetooth: 2020-02-26T18:57:50 rfkill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2045855/+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 2051576] Re: Please merge 1.9.15p5-3 into noble
This bug was fixed in the package sudo - 1.9.15p5-3ubuntu1 --- sudo (1.9.15p5-3ubuntu1) noble; urgency=medium * Merge with Debian unstable (LP: #2051576). Remaining changes: - debian/sudo[-ldap].manpages: install man/man8/sudo_root.8 - debian/sudo[-ldap].init: delete init scripts, as they are no longer necessary. - debian/etc/pam.d/sudo[-i]: + Use pam_env to read /etc/environment and /etc/default/locale environment files. Reading ~/.pam_environment is not permitted due to security reasons. - debian/etc/sudoers: + also grant admin group sudo access + include /snap/bin in the secure_path - debian/tests/control: 03-getroot-ldap + allow removal of 'sudo' in autopkgtest (SUDO_FORCE_REMOVE=yes) - debian/tests/04-getroot-sssd: + Check if the slapd daemon is ready before proceeding. In some situations, the next command (ldapmodify) runs before the service is ready. See LP#2026888 sudo (1.9.15p5-3) unstable; urgency=medium * add --with-devel configure option. Thanks to Bastien Roucariès (Closes: #1061272) sudo (1.9.15p5-2) unstable; urgency=medium * switch Build-Depends from systemd to systemd-dev Thanks to Michael Biebl (Closes: #1060511) * set Multi-Arch: foreign on sudo and sudo-ldap. Thanks to Andreas Rottmann (Closes: #1060445) * add debian/copyright clause for source_sudo.py. Oops. sudo (1.9.15p5-1) unstable; urgency=medium * new upstream version 1.9.15p5 * This is supposed to properly malloc on hurd. Thanks to Martin-Éric Racine (Closes: #1057833) * add durch debconf translation. Thanks to Frans Spiesschaert (Closes: #1059567) sudo (1.9.15p4-2) unstable; urgency=medium * upload to unstable * use pkg-config to place systemd units. Thanks to Chris Hofstaedtler (Closes: #1059063) * Add french debconf translation. Thanks to bubu (Closes: #1058939) * fix typo in NEWS.Debian. Thanks to Vincent Danjean (Closes: #1058925) * add persian debconf translation. Thanks to Danial Behzadi * add spanish debconf translation. Thanks to Camaleón (Closes: #1059460) sudo (1.9.15p4-1) experimental; urgency=medium * new upstream version 1.9.15p4 * add de.po template translation. Thanks to Christoph Brinkhaus (Closes: #1058762) * Enable AppArmor (MR 15, manually apṕlied) Thanks to Will Shand * remove legacy debian/rules.predh7 sudo (1.9.15p3-1) unstable; urgency=medium * new upstream version 1.9.15p3 sudo (1.9.15p2-2) unstable; urgency=medium * upload to unstable sudo (1.9.15p2-1) experimental; urgency=medium * the #DENOG15 release * New upstream version 1.9.15p2 * mark sudo-ldap as deprecated. -- Danilo Egea Gondolfo Mon, 29 Jan 2024 17:09:56 + ** Changed in: sudo (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/2051576 Title: Please merge 1.9.15p5-3 into noble Status in sudo package in Ubuntu: Fix Released Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2051576/+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 2052717] [NEW] USB sound card not detected
You have been subscribed to a public bug: Xubuntu 22.04. Updating the kernel from 5.15.0-92 to 5.15.0-94 results in my headset and webcam no longer being recognized. Rebooting back into the old kernel, and everything works as expected. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-94.104-generic 5.15.136 Uname: Linux 5.15.0-94-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:brad 4147 F pipewire CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Thu Feb 8 17:37:04 2024 InstallationDate: Installed on 2022-08-05 (552 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/19/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4501 dmi.board.asset.tag: Default string dmi.board.name: ROG CROSSHAIR VIII HERO (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4501:bd04/19/2023:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIIIHERO(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: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: ASUS ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- USB sound card not detected https://bugs.launchpad.net/bugs/2052717 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver 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 2052735] Re: python-memcache: autopkgtests fails due to invalid escape sequence '\ ' with python 3.12
This bug was fixed in the package python-memcache - 1.59-7ubuntu1 --- python-memcache (1.59-7ubuntu1) noble; urgency=medium * d/p/debian/patches/python312-remove-a-spurious-backslash.patch: fix Python 3.12 invalid escape sequence '\ ' warning (LP: #2052735). -- Vladimir Petko Fri, 09 Feb 2024 10:23:54 +1300 ** Changed in: python-memcache (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2052735 Title: python-memcache: autopkgtests fails due to invalid escape sequence '\ ' with python 3.12 Status in python-memcache package in Ubuntu: Fix Released Status in python3-defaults package in Ubuntu: New Status in python-memcache package in Debian: New Bug description: When running autopkgtests with python 3.12 the following failure occurs: 39s Removing autopkgtest-satdep (0) ... 439s autopkgtest [14:50:01]: test command1: python3 -c "import memcache; print(memcache.__version__)" 439s autopkgtest [14:50:01]: test command1: [--- 439s /tmp/autopkgtest.K47W5d/build.QVn/src/memcache.py:110: SyntaxWarning: invalid escape sequence '\ ' 439s """Object representing a pool of memcache servers. 439s 1.58 440s autopkgtest [14:50:02]: test command1: ---] 440s autopkgtest [14:50:02]: test command1: - - - - - - - - - - results - - - - - - - - - - 440s command1 FAIL stderr: /tmp/autopkgtest.K47W5d/build.QVn/src/memcache.py:110: SyntaxWarning: invalid escape sequence '\ ' 440s autopkgtest [14:50:02]: test command1: - - - - - - - - - - stderr - - - - - - - - - - 440s /tmp/autopkgtest.K47W5d/build.QVn/src/memcache.py:110: SyntaxWarning: invalid escape sequence '\ ' 440s """Object representing a pool of memcache servers. 440s autopkgtest [14:50:02]: test unittests: preparing testbed [1] This warning was fixed upstream in the following commit[2] [1] https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-noble/noble/amd64/p/python-memcache/20240207_145048_20ad0@/log.gz [2] https://github.com/linsomniac/python-memcached/commit/6e57445fd3be869e9928ef609a107342500c8e97 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-memcache/+bug/2052735/+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 2052755] [NEW] CPU spikes observed when playing youtube videos
You have been subscribed to a public bug: CPU is going almost 100% and videos feel laggy. Playing just one video on youtube , the cpu goes to almost 70% usage and then if 2 or 3 tabs are opened for video playback, the cpu goes to 100% usage. Its a recent phenomenon. I tried uninstalling and reinstalling nvidia drivers, still the same issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-17-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 535.154.05 Thu Dec 28 15:37:48 UTC 2023 GCC version: gcc version 12.3.0 (Ubuntu 12.3.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 9 06:45:36 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GA106 [RTX A2000 12GB] [10de:2571] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:1611] InstallationDate: Installed on 2023-08-16 (176 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic root=UUID=44a159e4-2bf4-4656-bf23-dd33975faef6 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.00 dmi.board.name: A320M-HDV R4.0 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.00:bd07/16/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA320M-HDVR4.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy performance possible-manual-nvidia-install ubuntu -- CPU spikes observed when playing youtube videos https://bugs.launchpad.net/bugs/2052755 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 1529431] Re: Add insert-text icon to non-full icon package
This bug was fixed in the package adwaita-icon-theme - 45.0-4 --- adwaita-icon-theme (45.0-4) unstable; urgency=medium * Depend on ubuntu-mono on Ubuntu * Run wrap-and-sort * Sync to Ubuntu and drop adwaita-icon-theme-full (LP: #2045962, LP: #1961495, LP: #1882271, LP: #1529431) -- Jeremy Bícha Fri, 09 Feb 2024 07:40:37 -0500 ** Changed in: adwaita-icon-theme (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1529431 Title: Add insert-text icon to non-full icon package Status in adwaita-icon-theme package in Ubuntu: Fix Released Status in gnome-icon-theme package in Ubuntu: Fix Released Bug description: Please can you move the "insert-text" icon from gnome-icon-theme-full to gnome-icon-theme, and from adwaita-icon-theme-full to adwaita-icon- theme. Currently easytag has an ubuntu specific patch to use gnome-icon- theme-full instead of gnome-icon-theme so it can use this icon, but reading the description of the package split it seems to me that gnome-icon-theme should still "provide" it somehow - even if it gets installed through a dependency on an ubuntu specific icon theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1529431/+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 2028972] Re: Crash prompt dialog says that netplan script encountered an error
[Expired for netplan.io (Ubuntu) because there has been no activity for
60 days.]
** Changed in: netplan.io (Ubuntu)
Status: Incomplete => Expired
--
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/2028972
Title:
Crash prompt dialog says that netplan script encountered an error
Status in apport package in Ubuntu:
Expired
Status in netplan.io package in Ubuntu:
Expired
Bug description:
I think this is on the ethernet NIC of this machine, which it is
having a problem connecting static... But generates and applies
without error.
I just replaced the motherboard from a Supermicro H8SGL-F with an AMD
Opteron 6386 SE to a MSI MPG Z790 Edge Wifi with Intel i9-13900K and
migrated the system to it: Legacy to UEFI, and LVM2 to ZFS.
This does have KVM and OpenVSwitch...
Output of Netplan Generate and Apply is:
mafoelffen@msi-ubuntu:~$ sudo netplan --debug generate
[sudo] password for mafoelffen:
DEBUG:command generate: running ['/lib/netplan/generate']
** (generate:37983): DEBUG: 11:58:12.511: starting new processing pass
** (generate:37983): DEBUG: 11:58:12.511: starting new processing pass
** (generate:37983): DEBUG: 11:58:12.511: enp5s0: adding new route
** (generate:37983): DEBUG: 11:58:12.511: We have some netdefs, pass them
through a final round of validation
** (generate:37983): DEBUG: 11:58:12.511: enp5s0: setting default backend to 1
** (generate:37983): DEBUG: 11:58:12.511: Configuration is valid
** (generate:37983): DEBUG: 11:58:12.511: Generating output files..
** (generate:37983): DEBUG: 11:58:12.511: openvswitch: definition enp5s0 is
not for us (backend 1)
** (generate:37983): DEBUG: 11:58:12.511: NetworkManager: definition enp5s0
is not for us (backend 1)
mafoelffen@msi-ubuntu:~$ sudo netplan --debug apply
** (generate:39541): DEBUG: 11:59:58.834: starting new processing pass
** (generate:39541): DEBUG: 11:59:58.834: starting new processing pass
** (generate:39541): DEBUG: 11:59:58.834: enp5s0: adding new route
** (generate:39541): DEBUG: 11:59:58.834: We have some netdefs, pass them
through a final round of validation
** (generate:39541): DEBUG: 11:59:58.834: enp5s0: setting default backend to 1
** (generate:39541): DEBUG: 11:59:58.834: Configuration is valid
** (generate:39541): DEBUG: 11:59:58.834: Generating output files..
** (generate:39541): DEBUG: 11:59:58.834: openvswitch: definition enp5s0 is
not for us (backend 1)
** (generate:39541): DEBUG: 11:59:58.834: NetworkManager: definition enp5s0
is not for us (backend 1)
DEBUG:netplan generated networkd configuration changed, reloading networkd
** (process:39539): DEBUG: 11:59:59.479: starting new processing pass
** (process:39539): DEBUG: 11:59:59.479: starting new processing pass
** (process:39539): DEBUG: 11:59:59.479: enp5s0: adding new route
** (process:39539): DEBUG: 11:59:59.479: We have some netdefs, pass them
through a final round of validation
** (process:39539): DEBUG: 11:59:59.479: enp5s0: setting default backend to 1
** (process:39539): DEBUG: 11:59:59.479: Configuration is valid
DEBUG:Merged config:
b''
DEBUG:no netplan generated NM configuration exists
** (process:39539): DEBUG: 11:59:59.490: starting new processing pass
** (process:39539): DEBUG: 11:59:59.491: starting new processing pass
** (process:39539): DEBUG: 11:59:59.491: enp5s0: adding new route
** (process:39539): DEBUG: 11:59:59.491: We have some netdefs, pass them
through a final round of validation
** (process:39539): DEBUG: 11:59:59.491: enp5s0: setting default backend to 1
** (process:39539): DEBUG: 11:59:59.491: Configuration is valid
DEBUG:Merged config:
b''
DEBUG:Link changes: {}
DEBUG:netplan triggering .link rules for lo
DEBUG:netplan triggering .link rules for enp5s0
DEBUG:netplan triggering .link rules for wlo1
DEBUG:netplan triggering .link rules for virbr2
DEBUG:netplan triggering .link rules for virbr1
DEBUG:netplan triggering .link rules for virbr0
DEBUG:netplan triggering .link rules for virbr3
** (process:39539): DEBUG: 11:59:59.604: starting new processing pass
** (process:39539): DEBUG: 11:59:59.604: starting new processing pass
** (process:39539): DEBUG: 11:59:59.604: enp5s0: adding new route
** (process:39539): DEBUG: 11:59:59.604: We have some netdefs, pass them
through a final round of validation
** (process:39539): DEBUG: 11:59:59.604: enp5s0: setting default backend to 1
** (process:39539): DEBUG: 11:59:59.604: Configuration is valid
** (process:39539): DEBUG: 11:59:59.604: starting new processing pass
** (process:39539): DEBUG: 11:59:59.604: starting new processing pass
** (process:39539): DEBUG: 11:59:59.604: enp5s0: adding new route
** (process:39539): DEBUG: 11:59:59.604: We have some netdefs, pass them
through a final round of validation
** (process:39539): DEBUG: 1
[Touch-packages] [Bug 2028972] Re: Crash prompt dialog says that netplan script encountered an error
[Expired for apport (Ubuntu) because there has been no activity for 60
days.]
** Changed in: apport (Ubuntu)
Status: Incomplete => Expired
--
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/2028972
Title:
Crash prompt dialog says that netplan script encountered an error
Status in apport package in Ubuntu:
Expired
Status in netplan.io package in Ubuntu:
Expired
Bug description:
I think this is on the ethernet NIC of this machine, which it is
having a problem connecting static... But generates and applies
without error.
I just replaced the motherboard from a Supermicro H8SGL-F with an AMD
Opteron 6386 SE to a MSI MPG Z790 Edge Wifi with Intel i9-13900K and
migrated the system to it: Legacy to UEFI, and LVM2 to ZFS.
This does have KVM and OpenVSwitch...
Output of Netplan Generate and Apply is:
mafoelffen@msi-ubuntu:~$ sudo netplan --debug generate
[sudo] password for mafoelffen:
DEBUG:command generate: running ['/lib/netplan/generate']
** (generate:37983): DEBUG: 11:58:12.511: starting new processing pass
** (generate:37983): DEBUG: 11:58:12.511: starting new processing pass
** (generate:37983): DEBUG: 11:58:12.511: enp5s0: adding new route
** (generate:37983): DEBUG: 11:58:12.511: We have some netdefs, pass them
through a final round of validation
** (generate:37983): DEBUG: 11:58:12.511: enp5s0: setting default backend to 1
** (generate:37983): DEBUG: 11:58:12.511: Configuration is valid
** (generate:37983): DEBUG: 11:58:12.511: Generating output files..
** (generate:37983): DEBUG: 11:58:12.511: openvswitch: definition enp5s0 is
not for us (backend 1)
** (generate:37983): DEBUG: 11:58:12.511: NetworkManager: definition enp5s0
is not for us (backend 1)
mafoelffen@msi-ubuntu:~$ sudo netplan --debug apply
** (generate:39541): DEBUG: 11:59:58.834: starting new processing pass
** (generate:39541): DEBUG: 11:59:58.834: starting new processing pass
** (generate:39541): DEBUG: 11:59:58.834: enp5s0: adding new route
** (generate:39541): DEBUG: 11:59:58.834: We have some netdefs, pass them
through a final round of validation
** (generate:39541): DEBUG: 11:59:58.834: enp5s0: setting default backend to 1
** (generate:39541): DEBUG: 11:59:58.834: Configuration is valid
** (generate:39541): DEBUG: 11:59:58.834: Generating output files..
** (generate:39541): DEBUG: 11:59:58.834: openvswitch: definition enp5s0 is
not for us (backend 1)
** (generate:39541): DEBUG: 11:59:58.834: NetworkManager: definition enp5s0
is not for us (backend 1)
DEBUG:netplan generated networkd configuration changed, reloading networkd
** (process:39539): DEBUG: 11:59:59.479: starting new processing pass
** (process:39539): DEBUG: 11:59:59.479: starting new processing pass
** (process:39539): DEBUG: 11:59:59.479: enp5s0: adding new route
** (process:39539): DEBUG: 11:59:59.479: We have some netdefs, pass them
through a final round of validation
** (process:39539): DEBUG: 11:59:59.479: enp5s0: setting default backend to 1
** (process:39539): DEBUG: 11:59:59.479: Configuration is valid
DEBUG:Merged config:
b''
DEBUG:no netplan generated NM configuration exists
** (process:39539): DEBUG: 11:59:59.490: starting new processing pass
** (process:39539): DEBUG: 11:59:59.491: starting new processing pass
** (process:39539): DEBUG: 11:59:59.491: enp5s0: adding new route
** (process:39539): DEBUG: 11:59:59.491: We have some netdefs, pass them
through a final round of validation
** (process:39539): DEBUG: 11:59:59.491: enp5s0: setting default backend to 1
** (process:39539): DEBUG: 11:59:59.491: Configuration is valid
DEBUG:Merged config:
b''
DEBUG:Link changes: {}
DEBUG:netplan triggering .link rules for lo
DEBUG:netplan triggering .link rules for enp5s0
DEBUG:netplan triggering .link rules for wlo1
DEBUG:netplan triggering .link rules for virbr2
DEBUG:netplan triggering .link rules for virbr1
DEBUG:netplan triggering .link rules for virbr0
DEBUG:netplan triggering .link rules for virbr3
** (process:39539): DEBUG: 11:59:59.604: starting new processing pass
** (process:39539): DEBUG: 11:59:59.604: starting new processing pass
** (process:39539): DEBUG: 11:59:59.604: enp5s0: adding new route
** (process:39539): DEBUG: 11:59:59.604: We have some netdefs, pass them
through a final round of validation
** (process:39539): DEBUG: 11:59:59.604: enp5s0: setting default backend to 1
** (process:39539): DEBUG: 11:59:59.604: Configuration is valid
** (process:39539): DEBUG: 11:59:59.604: starting new processing pass
** (process:39539): DEBUG: 11:59:59.604: starting new processing pass
** (process:39539): DEBUG: 11:59:59.604: enp5s0: adding new route
** (process:39539): DEBUG: 11:59:59.604: We have some netdefs, pass them
through a final round of validation
** (process:39539): DEBUG: 11:59:59.
[Touch-packages] [Bug 2028970] Re: Apport Crash
[Expired for apport (Ubuntu) because there has been no activity for 60 days.] ** Changed in: apport (Ubuntu) Status: Incomplete => Expired -- 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/2028970 Title: Apport Crash Status in apport package in Ubuntu: Expired Bug description: Powerglt crashed, but on report bug, apport-gtk crashed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport-gtk 2.20.11-0ubuntu82.5 ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17 Uname: Linux 5.19.0-50-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: GNOME Date: Fri Jul 28 11:41:11 2023 InstallationDate: Installed on 2022-09-19 (312 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2028970/+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 1959866] Re: lubuntu jammy - unable to submit bug via `ubuntu-bug calamares`
[Expired for apport (Ubuntu) because there has been no activity for 60 days.] ** Changed in: apport (Ubuntu) Status: Incomplete => Expired -- 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/1959866 Title: lubuntu jammy - unable to submit bug via `ubuntu-bug calamares` Status in apport package in Ubuntu: Expired Bug description: Lubuntu jammy QA-test install on - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) but it failed; calamares issue... No prob; file bug. I had issues filing bug, thus this additional report. ** BACKGROUND on the install & other report calamares bug filed as https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1959865 was filed online; then apport-collect run successfully on box. That link is now added to this report here as `apport-collect` was run during the same boot or live session as issue occurred. As noted in comment #7 (of this report) and the now provided link; a end-users filing of an install issue had me attempt a 'strange' (stupid?) install; a QA-testcase we call "install using existing partition"; https://discourse.lubuntu.me/t/testing-checklist- understanding-the-testcases/2743 where you just re-use existing partitions without format.. EXCEPT I was attempting it here with an encrypted partition... no mount or anything; just selecting in calamares)... it was this install type that no doubt led to this error. ** EXPECTED OUTCOME `ubuntu-bug calamares` and file bug report via firefox.. ** ACTUAL OUTCOME Alas `ubuntu-bug` won't work with this error --- The problem cannot be reported: Your /tmp partition has less than 32.33792 MB of free space available, which leads to problems using applications and installing updates. Please free some space. Press any key to continue... --- Full terminal session follows --- lubuntu@lubuntu:~$ ubuntu-bug calamares *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. *** The contents of the files attached to this report will help developers diagnose your bug more quickly. It may be possible that there is sensitive information in these files. You will be able to review these attachments before they are sent. Do you want to include these files? What would you like to do? Your options are: Y: Yes N: No C: Cancel Please choose (Y/N/C): y *** Problem in calamares The problem cannot be reported: Your /tmp partition has less than 32.33792 MB of free space available, which leads to problems using applications and installing updates. Please free some space. Press any key to continue... No pending crash reports. Try --help for more information. -- Note: apport-collect has NOW been run on same box; same daily ISO, but it's a later reboot/session --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: LXQt DistroRelease: Ubuntu 22.04 LiveMediaBuild: Lubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) Package: apport 2.20.11-0ubuntu76 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1959866/+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 2052859] [NEW] Windows go to behind others when clicking with mouse
You have been subscribed to a public bug:
After installing ubuntu graphics-drivers ppa nvidia-550 driver, the bug
appears.
When there are several windows on top of each other, clicking within the
topmost window, the window seems to disappear. Actually, the window is
still there, but just goes behind another window, that comes in front of
the clicked window. The program in the window that is clicked will not
notice the click.
This does not happen with all programs. Mines is a good example
program. If the window fills full screen, this happens, but if it is
smaller, only partially covering the screen, it does not happen.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.fabric-imex-mgmt:
DeviceFileMinor: 4323
DeviceFileMode: 256
DeviceFileModify: 1
.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..2d.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 550.40.07 Thu Jan 18 07:30:58
UTC 2024
GCC version: gcc version 13.2.0 (Ubuntu 13.2.0-4ubuntu3)
.tmp.unity_support_test.0:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CompizPlugins:
[core,bailer,detection,composite,opengl,compiztoolbox,decor,snap,gnomecompat,resize,regex,imgpng,grid,mousepoll,move,unitymtgrabhandles,animation,vpswitch,place,session,workarounds,expo,wall,fade,ezoom,scale,unityshell]
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 10 17:56:32 2024
DistUpgraded: 2023-11-03 20:23:14,648 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
NVIDIA Corporation AD103 [GeForce RTX 4070 Ti SUPER] [10de:2705] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:e130]
InstallationDate: Installed on 2012-12-22 (4067 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic
root=UUID=a21f1300-e2a3-44c9-a667-86fc6184627b ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-11-03 (99 days ago)
dmi.bios.date: 02/28/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: A.J0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MPG X570 GAMING PLUS (MS-7C37)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 2.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 2.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.J0:bd02/28/2023:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C37:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGX570GAMINGPLUS(MS-7C37):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7C37
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 2.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz 1:0.9.14.2+22.10.20220822-0ubuntu4
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~23.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
xserver.bootTime: Fri Feb 9 20:05:59 2024
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
xserver.version: 2:21.1.7-3ubuntu2.7
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic ubuntu
--
Windows go to behind others when clicking with mouse
https://bugs.launchpad.net/bugs/2052859
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-pac
[Touch-packages] [Bug 2051540] Re: ufw ftbfs with Python 3.12 as default
This bug was fixed in the package ufw - 0.36.2-4
---
ufw (0.36.2-4) unstable; urgency=medium
* debian/test/control: install python3-setuptools instead of
python3-distutils (LP: #2051540)
-- Jamie Strandboge Sat, 10 Feb 2024 23:34:53
+
** Changed in: ufw (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/2051540
Title:
ufw ftbfs with Python 3.12 as default
Status in ufw:
Fix Committed
Status in ufw package in Ubuntu:
Fix Released
Status in ufw package in Debian:
Fix Released
Bug description:
==
ERROR: test_ufwcommand_parse
(tests.unit.test_parser.ParserTestCase.test_ufwcommand_parse)
Test UFWCommand.parse()
--
Traceback (most recent call last):
File "/<>/tests/unit/test_parser.py", line 88, in
test_ufwcommand_parse
self.assertEquals('status', pr.action, "%s != 'status'" % (pr.action))
^
AttributeError: 'ParserTestCase' object has no attribute 'assertEquals'. Did
you mean: 'assertEqual'?
==
ERROR: test_ufwcommand_rule_get_command
(tests.unit.test_parser.ParserTestCase.test_ufwcommand_rule_get_command)
Test UFWCommand(Route)Rule.get_command()
--
Traceback (most recent call last):
File "/<>/tests/unit/test_parser.py", line 375, in
test_ufwcommand_rule_get_command
self.assertEquals(len(errors), 0,
^
AttributeError: 'ParserTestCase' object has no attribute 'assertEquals'. Did
you mean: 'assertEqual'?
--
Ran 24 tests in 7.584s
FAILED (errors=9)
test_skeleton
test_example (tests.unit.test_skeleton.SkeletonTestCase.test_example)
Test example dummy test ... ok
--
Ran 1 test in 0.000s
OK
To manage notifications about this bug go to:
https://bugs.launchpad.net/ufw/+bug/2051540/+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 2039873] Re: [SRU] liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases
This bug was fixed in the package lxc - 1:5.0.1-0ubuntu8~23.10.1 --- lxc (1:5.0.1-0ubuntu8~23.10.1) mantic; urgency=medium [ Alexander Mikhalitsyn ] * Fix the LXC_DEVEL value to be 0 (LP: #2039873) - d/p/0003-meson-Set-DEVEL-flag-post-release.patch was dropped as it should not be in the production builds * Added autopkgtest to ensure that LXC_DEVEL is always 0 - debian/tests/no-devel: add "no-devel" autopkgtest script - debian/tests/control: declare "no-devel" autopkgtest -- Dave Jones Wed, 24 Jan 2024 16:25:47 + ** Changed in: lxc (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/2039873 Title: [SRU] liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Jammy: Fix Committed Status in lxc source package in Mantic: Fix Released Status in lxc source package in Noble: Fix Released Bug description: [ Impact ] LXC 5.0.0 was built with LXC_DEVEL=1 set for Jammy. But for release build we should have LXC_DEVEL=0. LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h and then can be (and actually it is) used by other projects to detect if liblxc-dev is a development build or stable. Having LXC_DEVEL=1 makes problems for the users who want to build projects those are depend on liblxc from source (for example, LXD, go-lxc: https://github.com/canonical/lxd/pull/12420). Q: Why it was not a problem for so long? A: Because LXC API was stable for a long time, but recently we have extended liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc was updated too (https://github.com/lxc/go-lxc/pull/166). This change was developed properly to be backward compatible with the old versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro check VERSION_AT_LEAST (https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7) is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release build of LXC. [ Test Plan ] Install liblxc-dev package and check /usr/include/lxc/version.h file LXC_DEVEL should be 0 [ Where problems could occur ] Theoretically, build of a software which depends on liblxc-dev may start to fail if it assumes that LXC_DEVEL is 1. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+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 2039873] Re: [SRU] liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases
This bug was fixed in the package lxc - 1:5.0.0~git2209-g5a7b9ce67-0ubuntu1.1 --- lxc (1:5.0.0~git2209-g5a7b9ce67-0ubuntu1.1) jammy; urgency=medium [ Dave Jones ] * Fix the LXC_DEVEL value to be 0 (LP: #2039873) - d/p/0002-Set-DEVEL-flag-post-release.patch added to force this value in the autoconf script [ Alexander Mikhalitsyn ] * Added autopkgtest to ensure that LXC_DEVEL is always 0 - debian/tests/no-devel: add "no-devel" autopkgtest script - debian/tests/control: declare "no-devel" autopkgtest -- Dave Jones Wed, 24 Jan 2024 16:26:06 + ** Changed in: lxc (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/2039873 Title: [SRU] liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Jammy: Fix Released Status in lxc source package in Mantic: Fix Released Status in lxc source package in Noble: Fix Released Bug description: [ Impact ] LXC 5.0.0 was built with LXC_DEVEL=1 set for Jammy. But for release build we should have LXC_DEVEL=0. LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h and then can be (and actually it is) used by other projects to detect if liblxc-dev is a development build or stable. Having LXC_DEVEL=1 makes problems for the users who want to build projects those are depend on liblxc from source (for example, LXD, go-lxc: https://github.com/canonical/lxd/pull/12420). Q: Why it was not a problem for so long? A: Because LXC API was stable for a long time, but recently we have extended liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc was updated too (https://github.com/lxc/go-lxc/pull/166). This change was developed properly to be backward compatible with the old versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro check VERSION_AT_LEAST (https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7) is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release build of LXC. [ Test Plan ] Install liblxc-dev package and check /usr/include/lxc/version.h file LXC_DEVEL should be 0 [ Where problems could occur ] Theoretically, build of a software which depends on liblxc-dev may start to fail if it assumes that LXC_DEVEL is 1. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+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 2049318] Re: [SRU] free(): double free detected in tcache 2
This bug was fixed in the package iptables - 1.8.7-1ubuntu5.2 --- iptables (1.8.7-1ubuntu5.2) jammy; urgency=medium * Apply upstream patch to fix a double free of unrecognized base-chains. (LP: #2049318) -- Sudip Mukherjee Tue, 16 Jan 2024 21:14:30 + ** Changed in: iptables (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/2049318 Title: [SRU] free(): double free detected in tcache 2 Status in iptables package in Ubuntu: Fix Released Status in iptables source package in Jammy: Fix Released Bug description: [ Impact ] iptables is unable to list the iptables rules or save the iptables rules if a nftables ruleset is defined which iptables does not recognize. [ Test Plan ] 1. Simple test plan based on upstream test case: sudo nft -f - < rules.txt * Convert the rule to nftables ruleset - sudo iptables-nft-restore < rules.txt * List the nftables ruleset - sudo nft list ruleset * Also confirm that iptables can list the old rule - sudo iptables -L * Now add another nftables rule (this rule is taken from upstream test case) sudo nft -f -
[Touch-packages] [Bug 2047450] Re: tail emits no output for sysfs files when using large page kernels
This bug was fixed in the package coreutils - 9.1-1ubuntu2.23.10.1 --- coreutils (9.1-1ubuntu2.23.10.1) mantic; urgency=medium * d/p/tail-fix-tailing-sysfs-files-where-PAGE_SIZE-BUFSIZ.patch: Fix tailing of sysfs files on systems using a 64K page size. (LP: #2047450) -- dann frazier Sat, 06 Jan 2024 11:28:58 -0700 ** Changed in: coreutils (Ubuntu Mantic) Status: Fix Committed => Fix Released ** Changed in: coreutils (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2047450 Title: tail emits no output for sysfs files when using large page kernels Status in coreutils package in Ubuntu: Fix Released Status in coreutils source package in Jammy: Fix Released Status in coreutils source package in Lunar: Won't Fix Status in coreutils source package in Mantic: Fix Released Status in coreutils source package in Noble: Fix Released Bug description: [Impact] Ubuntu provides 64K page size kernels for ppc64el (always) and arm64 (optional -64k flavors). When booted on 64K kernels, tail emits no output when tailing a sysfs file. The difference in behavior can be a source for bugs in scripts that use tail, and general user confusion. [Test Plan] The upstream fix includes a test case that tails the /sys/kernel/profiling file, if it exists. That case would fail with an unfixed coreutils package as shown below: = When booted on a 4K kernel = ubuntu@gunyolk:~$ tail /sys/kernel/profiling 0 = When booted on a 64K kernel = ubuntu@gunyolk:~$ tail /sys/kernel/profiling ubuntu@gunyolk:~$ Since the upstream test cases are executed at build time, the existing tests and this new test will be used to regression test behavior. This should cover both 4K (!ppc64el) and 64K (ppc64el) cases. We should also do a manual verification on arm64 w/ the 64K kernel since that case is not covered by our builders. [Where Problems Could Occur] The biggest risk for a regression I see is due to the side-effect of the fix now allocating a dynamic buffer instead of the stack. An error in logic there could cause a crash or a memory leak in scenarios undetected during testing. I used valgrind when developing the fix to derisk the memory leak scenario. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2047450/+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 2047450] Re: tail emits no output for sysfs files when using large page kernels
This bug was fixed in the package coreutils - 8.32-4.1ubuntu1.1 --- coreutils (8.32-4.1ubuntu1.1) jammy; urgency=medium * d/p/assure-new-macro-affirm.patch, d/p/tail-fix-tailing-sysfs-files-where-PAGE_SIZE-BUFSIZ.patch: Fix tailing of sysfs files on systems using a 64K page size. (LP: #2047450) -- dann frazier Mon, 08 Jan 2024 07:56:36 -0700 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2047450 Title: tail emits no output for sysfs files when using large page kernels Status in coreutils package in Ubuntu: Fix Released Status in coreutils source package in Jammy: Fix Released Status in coreutils source package in Lunar: Won't Fix Status in coreutils source package in Mantic: Fix Released Status in coreutils source package in Noble: Fix Released Bug description: [Impact] Ubuntu provides 64K page size kernels for ppc64el (always) and arm64 (optional -64k flavors). When booted on 64K kernels, tail emits no output when tailing a sysfs file. The difference in behavior can be a source for bugs in scripts that use tail, and general user confusion. [Test Plan] The upstream fix includes a test case that tails the /sys/kernel/profiling file, if it exists. That case would fail with an unfixed coreutils package as shown below: = When booted on a 4K kernel = ubuntu@gunyolk:~$ tail /sys/kernel/profiling 0 = When booted on a 64K kernel = ubuntu@gunyolk:~$ tail /sys/kernel/profiling ubuntu@gunyolk:~$ Since the upstream test cases are executed at build time, the existing tests and this new test will be used to regression test behavior. This should cover both 4K (!ppc64el) and 64K (ppc64el) cases. We should also do a manual verification on arm64 w/ the 64K kernel since that case is not covered by our builders. [Where Problems Could Occur] The biggest risk for a regression I see is due to the side-effect of the fix now allocating a dynamic buffer instead of the stack. An error in logic there could cause a crash or a memory leak in scenarios undetected during testing. I used valgrind when developing the fix to derisk the memory leak scenario. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2047450/+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 2036761] Re: [mantic] ppa-purge no longer purges what add-apt-repository adds
** Merge proposal linked: https://code.launchpad.net/~ghadi-rahme/ubuntu/+source/ppa-purge/+git/ppa-purge/+merge/460394 -- 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/2036761 Title: [mantic] ppa-purge no longer purges what add-apt-repository adds Status in ppa-purge package in Ubuntu: Triaged Status in software-properties package in Ubuntu: Confirmed Status in ppa-purge source package in Mantic: Triaged Status in software-properties source package in Mantic: Confirmed Bug description: Test Case - From Ubuntu 23.10: sudo apt install hello sudo add-apt-repository ppa:jbicha/temp sudo apt upgrade apt policy hello sudo ppa-purge ppa:jbicha/temp apt policy hello reveals that the PPA version of hello is still installed Also /etc/apt/sources.list.d/jbicha-ubuntu-temp-mantic.sources is still present and active What Should Happen -- ppa-purge should disable the PPA and reinstall any PPA packages with the version apt currently sees. Background -- add-apt-repository creates deb822 sources lists, starting in Ubuntu 23.10 https://discourse.ubuntu.com/t/spec-apt-deb822-sources-by- default/29333 Other Info -- add-apt-repository has a --remove option But it does not do the reinstall part which is important Honestly, that feature is so important, I suggest that add-apt-repository take over the functionality of ppa-purge so that we always get the ppa-purge behavior To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/2036761/+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 2051541] Re: unattended-upgrades ftbfs with Python 3.12 as default
This bug was fixed in the package unattended-upgrades - 2.9.1+nmu4ubuntu1 --- unattended-upgrades (2.9.1+nmu4ubuntu1) noble; urgency=medium * Merge from Debian unstable. Remaining changes: - kernel/postinst.d/unattended-upgrades: check to see if canonical- livepatch is installed and enabled. In the event that it is and it says a reboot is required do not update reboot-required files so that only one reboot message appears in the message of the day. - d/t/control: Restrict kernel-patterns test to isolation-machine as the test assumes a meaningful link between the running kernel and the archive - Make debian/tests/test-systemd.py and test/autopkgtest_kernel_patterns.py executable again * tests/test_pep484.py, tests/test_pyflakes.py: Add a faux test to make sure we don't fail the test suite because the only test in the file was skipped... (LP: #2051541) unattended-upgrades (2.9.1+nmu4) unstable; urgency=medium * Non-maintainer upload. * Don't run pyflakes, it dropped support for type comments. (Closes: #1058172) -- Julian Andres Klode Mon, 12 Feb 2024 18:50:35 +0100 ** Changed in: unattended-upgrades (Ubuntu Noble) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/2051541 Title: unattended-upgrades ftbfs with Python 3.12 as default Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Noble: Fix Released Bug description: [...] Running ./test_pep484.py with python3 s -- Ran 0 tests in 0.000s NO TESTS RAN (skipped=1) make[2]: *** [Makefile:9: check] Error 5 make[2]: Leaving directory '/<>/test' make[1]: *** [debian/rules:16: override_dh_auto_test] Error 2 5 is a new exit value when all tests are skipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2051541/+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 2022927] Re: Busybox mount fails to mount Snaps
[Expired for busybox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: busybox (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/2022927 Title: Busybox mount fails to mount Snaps Status in busybox package in Ubuntu: Expired Bug description: Snapd tries to mount squashfs Snaps with non-standard mount flags like "x-gdu.hide" and "x-gvfs-hide", both of which are used to indicate to userspace programs that a given mount should not be shown in a list of mounted partitions/filesystems. Busybox does not support these flags, and so fails with "Invalid argument". $ sudo busybox mount -t tmpfs -o x-gdu-hide test /tmp/test mount: mounting test on /tmp/test failed: Invalid argument These flags can likely be be safely ignored, as they don't actually affect the functionality of the mount. This goes for all mount options starting with "x-", as these generally denote non-standard mount option "extensions". I've created a patch against Busybox which adds an optional configuration item to ignore all mount options beginning with "x-". An additional verbose option has also been added to enable the ability to report that the mount flags have been ignored, rather than silently ignoring them. This is a requirement for a customer project, where we are limited to using Busybox (due to coreutils' GPL-3.0 licence) but would also require using Snaps like checkbox for testing and verification. This was posted on the Busybox mailing list a few months ago (http://lists.busybox.net/pipermail/busybox/2023-March/090202.html) but patch acceptance there seems to take quite a long time, and we need this for the customer. A PPA containing the patched Busybox version is available on the project's Launchpad team: https://launchpad.net/~nemos- team/+archive/ubuntu/ppa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2022927/+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 2034986] Re: some text became unreadable during a distribution upgrade
This bug was fixed in the package ubuntu-release-upgrader - 1:22.04.18 --- ubuntu-release-upgrader (1:22.04.18) jammy; urgency=medium * do-release-upgrade: pass XDG_CURRENT_DESKTOP env var (LP: #2034986) * Run pre-build.sh: updating po files, mirrors, and demotions. -- Nick Rosbrook Thu, 12 Oct 2023 11:56:03 -0400 ** Changed in: ubuntu-release-upgrader (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034986 Title: some text became unreadable during a distribution upgrade Status in Cinnamon: New Status in Ubuntu MATE: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in ubuntu-release-upgrader source package in Jammy: Fix Released Status in ubuntu-release-upgrader source package in Lunar: Fix Released Status in ubuntu-meta source package in Mantic: Fix Released Status in ubuntu-release-upgrader source package in Mantic: Fix Released Bug description: [ Impact ] * On Ubuntu Mate with the Lunar series, when running ubuntu-release-upgrader, the displayed font of running applications (including the upgrader) becomes very corrupted. * This is not just a display problem, it is also a functional one. The release upgrader will have text corrupted to the point where a dialog asks a decision, and displays two buttons, but the text is unreadable and one has to guess which button is the one that carries out their desired action. * In the early parts of the upgrader tool, users are told in bold: "To prevent data loss close all open applications and documents." This is just before the "Start Upgrade" button is available. But they may not do so. Many applications may have a corrupted font. * To address this, an additional environment variable is being passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the critical criteria for making the Mate version of the fix work. * Also in the change are * an update to tests * from pre-build.sh * an update of the mirrors.cfg, adding and removing several mirrors * a refresh of the po files [ Test Plan ] * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64 * as user, run "update-manager -d" * monitor the "Distribution Upgrade" screen. During the "Installing the upgrades" step (and mind that this step will be long), observe the text of the "Distribution Upgrade" screen and verify that the font does not corrupt. * Repeat the above for Ubuntu Desktop [ Where problems could occur ] * We are changing, at release time, ubuntu-release upgrader. If we are careless, we could regress upgrades for a wider group of users than just Ubuntu Mate. That said, it is believed that passing the additional XDG_CURRENT_DESKTOP variable is relatively low risk. [ Other Info ] * TBD --- Original description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-project/+bug/2034986/+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 1956102] Re: Time for the US is shown in 24h format. It should be 12h with AM/PM
This bug was fixed in the package gsettings-desktop-schemas - 46~beta-1ubuntu1 --- gsettings-desktop-schemas (46~beta-1ubuntu1) noble; urgency=medium * Merge with Debian. Remaining changes: - Add ubuntu_lock-on-suspend.patch - Add dark-theme migration script using dh-migrations - Drop Breaks: ukwm because ukwm still runs but fails to build from source for unrelated reasons gsettings-desktop-schemas (46~beta-1) unstable; urgency=medium * New upstream release - Enable tap-to-click by default - Add new show-status-shapes schema to show shapes in Adwaita on/off switches, disabled by default - Add xkb-model schema, used by GNOME Shell 46 - Allow localization of clock format (in coordination with glib 2.78) (LP: #1956102) * Add patch to keep using the 45 default wallpaper. See #1060278 -- Jeremy Bícha Tue, 13 Feb 2024 08:30:42 -0500 ** Changed in: gsettings-desktop-schemas (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1956102 Title: Time for the US is shown in 24h format. It should be 12h with AM/PM Status in GSettings Desktop Schemas: Fix Released Status in gsettings-desktop-schemas package in Ubuntu: Fix Released Bug description: Source- https://time.gov/ To manage notifications about this bug go to: https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1956102/+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 2034065] Re: package linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2
[Expired for initramfs-tools (Ubuntu) because there has been no activity for 60 days.] ** Changed in: initramfs-tools (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2034065 Title: package linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 Status in initramfs-tools package in Ubuntu: Expired Bug description: hello and thanks for developing Linux and Ubuntu. i was updating and upgrading packages as always i do. sudo apt update && sudo apt upgrade and after some downloads and ... in 96% progress i got issue and progress didn't go done. i'm new in linux ubuntu and i decided to don't change anything manually. it's good to help me figure out. thanks again. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 Uname: Linux 6.2.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Sep 4 20:33:34 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 InstallationDate: Installed on 2023-08-18 (16 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 RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: initramfs-tools Title: package linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2034065/+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 2051405] Re: ProtectHome setting in debian/rsyslog.service isn't understood by systemd
** Merge proposal linked: https://code.launchpad.net/~xypron/ubuntu/+source/rsyslog/+git/rsyslog/+merge/459640 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2051405 Title: ProtectHome setting in debian/rsyslog.service isn't understood by systemd Status in rsyslog package in Ubuntu: Confirmed Bug description: Small bug introduced in commit e175f5c3668adc1c65f66efb61f70060569c9fe8 https://git.launchpad.net/ubuntu/+source/rsyslog/commit/?id=e175f5c3668adc1c65f66efb61f70060569c9fe8 which changed the rsyslog.service line of ProtectHome=yes to ProtectHome=readonly Systemd doesn't understand "readonly" https://www.freedesktop.org/software/systemd/man/latest/systemd.exec.html and will mention in its journal: systemd[1]: /lib/systemd/system/rsyslog.service:24: Failed to parse protect home value, ignoring: readonly Quickfix: just needs a hyphen on line 24 to read 'read-only' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2051405/+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 mathod is slightly wrong
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: openssh (Ubuntu)
Status: New => Confirmed
--
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:
Confirmed
Bug 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,
+ &options.gss_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 2033949] Re: Does not work with Ubuntu sources in deb822 format
This bug was fixed in the package software-properties - 0.99.42 --- software-properties (0.99.42) noble; urgency=medium * Support deb822 lists for Ubuntu sources (LP: #2033949) * Bump python3-apt dependency to 2.7.1~ -- Julian Andres Klode Tue, 05 Dec 2023 18:47:47 +0100 ** Changed in: software-properties (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2033949 Title: Does not work with Ubuntu sources in deb822 format Status in python-apt package in Ubuntu: Fix Committed Status in software-properties package in Ubuntu: Fix Released Status in python-apt source package in Mantic: Won't Fix Status in software-properties source package in Mantic: Won't Fix Bug description: On my Mantic I have sources in new deb822 format. Starting software-properties-gtk seems my server is Main server, but from /etc/apt/sources.list.d/ubuntu.sources I see server from Italy and I software-properties-gtk seems unable to change. corrado@corrado-n16-mm-0901:~$ cat /etc/apt/sources.list.d/ubuntu.sources Types: deb URIs: http://it.archive.ubuntu.com/ubuntu Suites: mantic mantic-updates mantic-backports Components: main restricted universe multiverse Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg Types: deb URIs: http://it.archive.ubuntu.com/ubuntu Suites: mantic-security Components: main restricted universe multiverse Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg corrado@corrado-n16-mm-0901:~$ ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: software-properties-gtk 0.99.39 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 2 10:33:12 2023 InstallationDate: Installed on 2023-09-01 (1 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2033949/+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 2051512] Re: apport ftbfs with Python 3.12 as the default
** Merge proposal linked:
https://code.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/+git/apport/+merge/458513
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/2051512
Title:
apport ftbfs with Python 3.12 as the default
Status in apport package in Ubuntu:
Confirmed
Status in python3-defaults package in Ubuntu:
New
Status in python3.12 package in Ubuntu:
New
Status in apport source package in Noble:
Confirmed
Status in python3-defaults source package in Noble:
New
Status in python3.12 source package in Noble:
New
Bug description:
[Description]
Python 3.12 gzip.GZipFile.write() outputs truncated data in some cases
(maybe all?)
[Test Plan]
Run the following script:
import gzip
import io
out = io.BytesIO()
gzip.GzipFile("foo", mode="wb", fileobj=out, mtime=0).write(b"FooFoo")
# print(out.getvalue())
print(gzip.decompress(out.getvalue()))
Expected output (as on Python 3.11):
FooFoo
Buggy output (tail end of the stack trace):
EOFError: Compressed file ended before the end-of-stream marker was reached
[Original report]
debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
tests/run-linters --errors-only
Skipping mypy tests, mypy is not installed
Running pylint...
* Module apport-retrace
bin/apport-retrace:577:44: E0601: Using variable 'crashid' before assignment
(used-before-assignment)
make[1]: *** [debian/rules:23: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:4: binary] Error 2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2051512/+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 2046498] Re: test-execute fails in LXD with failure in exec-networknamespacepath-privatemounts-no.service
This bug was fixed in the package systemd - 255.2-3ubuntu2 --- systemd (255.2-3ubuntu2) noble; urgency=medium * test: skip test_exec_networknamespacepath if netns setup fails (LP: #2046498) Files: - debian/patches/lp2046498-test-skip-test_exec_networknamespacepath-if-netns-setup-f.patch - debian/patches/test-skip-failing-test-execute-tests-in-LXC.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=de1fcf756e47858f4a206db97434bce4a71384d0 * test: skip TEST-43-PRIVATEUSER-UNPRIV if unprivileged userns is restricted File: debian/patches/test-skip-TEST-43-PRIVATEUSER-UNPRIV-if-unprivileged-user.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=2aba69874c83289c43d199ca360aa2fc451486a7 * Drop debian/UBUNTU-src-test-test-execute.c-Skip-parts-of-test-execute-in-con.patch. This will be re-addressed with a different patch. File: debian/patches/debian/UBUNTU-src-test-test-execute.c-Skip-parts-of-test-execute-in-con.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c3cd814e028364fe0c641d4bacfce22aafd1b572 * Drop test-skip-failing-test-execute-tests-in-LXC.patch. This will be re-addressed with different patches. File: debian/patches/test-skip-failing-test-execute-tests-in-LXC.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ab853707f4cc3e7e2d5993ff38998c3c2c789f62 * test: temporarily skip credentials tests in LXC. This was already skipped in another patch, but now that we know what's going on with it, split it out. File: debian/patches/test-temporarily-skip-credentials-tests-in-LXC.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c71acb411d315267fe811f024cdab97e032453f3 * test: skip test-execute in arhmf LXC containers File: debian/patches/test-skip-test-execute-in-arhmf-LXC-containers.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1cb1e3060822bfadddead564e779942e73e02f62 * test: skip exec-privatenetwork-yes-privatemounts-yes.service in LXC (LP: #2046495) File: debian/patches/test-skip-exec-privatenetwork-yes-privatemounts-yes.servi.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3ab76fd2db4291ee0531a07085c72cee06cb0d12 * test: skip a systemd-run test if unprivileged userns is restricted File: debian/patches/test-skip-a-systemd-run-test-if-unprivileged-userns-is-re.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c85f2b4e32ee8fd1c0dc58d23e7fabdb7590d3cc * test-execute: skip tests that are broken without unprivileged userns File: debian/patches/test-execute-skip-tests-that-are-broken-without-unprivile.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7a6573c4f5133a7fec11fb059dd215f7c8c2204e -- Nick Rosbrook Wed, 24 Jan 2024 14:53:46 -0500 ** Changed in: systemd (Ubuntu) Status: Triaged => Fix Released -- 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/2046498 Title: test-execute fails in LXD with failure in exec-networknamespacepath- privatemounts-no.service Status in systemd package in Ubuntu: Fix Released Bug description: This is in v255. This log snippet is taken from a local autopkgtest build: exec-networknamespacepath-privatemounts-no.service: Child 4580 belongs to exec-networknamespacepath-privatemounts-no.service. exec-networknamespacepath-privatemounts-no.service: Main process exited, code=exited, status=0/SUCCESS (success) exec-networknamespacepath-privatemounts-no.service: Running next main command for state start. exec-networknamespacepath-privatemounts-no.service: Will spawn child (service_run_next_main): /bin/sh exec-networknamespacepath-privatemounts-no.service: Passing 0 fds to service exec-networknamespacepath-privatemounts-no.service: About to execute: /bin/sh -x -c "ip link show dummy-test-ns" Serializing sd-executor-state to memfd. exec-networknamespacepath-privatemounts-no.service: Forked /bin/sh as 4581 Closing set fd 19 (socket:[109908]) Closing set fd 21 (socket:[51]) Closing set fd 20 (socket:[50]) Received SIGCHLD from PID 4581 (sh). Child 4581 (sh) died (code=exited, status=1/FAILURE) exec-networknamespacepath-privatemounts-no.service: Child 4581 belongs to exec-networknamespacepath-privatemounts-no.service. exec-networknamespacepath-privatemounts-no.service: Main process exited, code=exited, status=1/FAILURE exec-networknamespacepath-privatemounts-no.service: Failed with result 'exit-code'. exec-networknamespacepath-privatemounts-no.service: Service will not restart (restart setting) exec-networknamespacepath-privatemounts-no.service: Changed start -> faile
[Touch-packages] [Bug 2046495] Re: test-execute fails in LXD with failure in exec-privatenetwork-yes-privatemounts-yes.service
This bug was fixed in the package systemd - 255.2-3ubuntu2 --- systemd (255.2-3ubuntu2) noble; urgency=medium * test: skip test_exec_networknamespacepath if netns setup fails (LP: #2046498) Files: - debian/patches/lp2046498-test-skip-test_exec_networknamespacepath-if-netns-setup-f.patch - debian/patches/test-skip-failing-test-execute-tests-in-LXC.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=de1fcf756e47858f4a206db97434bce4a71384d0 * test: skip TEST-43-PRIVATEUSER-UNPRIV if unprivileged userns is restricted File: debian/patches/test-skip-TEST-43-PRIVATEUSER-UNPRIV-if-unprivileged-user.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=2aba69874c83289c43d199ca360aa2fc451486a7 * Drop debian/UBUNTU-src-test-test-execute.c-Skip-parts-of-test-execute-in-con.patch. This will be re-addressed with a different patch. File: debian/patches/debian/UBUNTU-src-test-test-execute.c-Skip-parts-of-test-execute-in-con.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c3cd814e028364fe0c641d4bacfce22aafd1b572 * Drop test-skip-failing-test-execute-tests-in-LXC.patch. This will be re-addressed with different patches. File: debian/patches/test-skip-failing-test-execute-tests-in-LXC.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ab853707f4cc3e7e2d5993ff38998c3c2c789f62 * test: temporarily skip credentials tests in LXC. This was already skipped in another patch, but now that we know what's going on with it, split it out. File: debian/patches/test-temporarily-skip-credentials-tests-in-LXC.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c71acb411d315267fe811f024cdab97e032453f3 * test: skip test-execute in arhmf LXC containers File: debian/patches/test-skip-test-execute-in-arhmf-LXC-containers.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1cb1e3060822bfadddead564e779942e73e02f62 * test: skip exec-privatenetwork-yes-privatemounts-yes.service in LXC (LP: #2046495) File: debian/patches/test-skip-exec-privatenetwork-yes-privatemounts-yes.servi.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3ab76fd2db4291ee0531a07085c72cee06cb0d12 * test: skip a systemd-run test if unprivileged userns is restricted File: debian/patches/test-skip-a-systemd-run-test-if-unprivileged-userns-is-re.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c85f2b4e32ee8fd1c0dc58d23e7fabdb7590d3cc * test-execute: skip tests that are broken without unprivileged userns File: debian/patches/test-execute-skip-tests-that-are-broken-without-unprivile.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7a6573c4f5133a7fec11fb059dd215f7c8c2204e -- Nick Rosbrook Wed, 24 Jan 2024 14:53:46 -0500 ** Changed in: systemd (Ubuntu) Status: New => Fix Released -- 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/2046495 Title: test-execute fails in LXD with failure in exec-privatenetwork-yes- privatemounts-yes.service Status in systemd package in Ubuntu: Fix Released Bug description: This is in v255. This log snippet is taken from a local autopkgtest build: exec-privatenetwork-yes-privatemounts-yes.service: Will spawn child (service_enter_start): /bin/sh exec-privatenetwork-yes-privatemounts-yes.service: Failed to set 'trusted.invocation_id' xattr on control group /system.slice/test-execute-48e27182b3724b7.scope/99d288e6f11f869e/system.slice/exec-privatenetwork-yes-privatemounts-yes.service, ignoring: Operation not permitted exec-privatenetwork-yes-privatemounts-yes.service: Failed to remove 'trusted.delegate' xattr flag on control group /system.slice/test-execute-48e27182b3724b7.scope/99d288e6f11f869e/system.slice/exec-privatenetwork-yes-privatemounts-yes.service, ignoring: Operation not permitted exec-privatenetwork-yes-privatemounts-yes.service: Failed to remove 'trusted.survive_final_kill_signal' xattr flag on control group /system.slice/test-execute-48e27182b3724b7.scope/99d288e6f11f869e/system.slice/exec-privatenetwork-yes-privatemounts-yes.service, ignoring: Operation not permitted exec-privatenetwork-yes-privatemounts-yes.service: Passing 0 fds to service exec-privatenetwork-yes-privatemounts-yes.service: About to execute: /bin/sh -x -c "! ip link show dummy-test-exec" Serializing sd-executor-state to memfd. exec-privatenetwork-yes-privatemounts-yes.service: Forked /bin/sh as 5092 Closing set fd 21 (socket:[116840]) Closing set fd 19 (socket:[113527]) Closing set fd 20 (socket:[116839]) exec-privatenetwork-yes-privatemounts-yes.service: Changed dead -> start
[Touch-packages] [Bug 2046459] Re: systemd-gpt-auto-generator is omitted since 253.5-1ubuntu5 resulting in boot failure
This bug was fixed in the package systemd - 255.2-3ubuntu2 --- systemd (255.2-3ubuntu2) noble; urgency=medium * test: skip test_exec_networknamespacepath if netns setup fails (LP: #2046498) Files: - debian/patches/lp2046498-test-skip-test_exec_networknamespacepath-if-netns-setup-f.patch - debian/patches/test-skip-failing-test-execute-tests-in-LXC.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=de1fcf756e47858f4a206db97434bce4a71384d0 * test: skip TEST-43-PRIVATEUSER-UNPRIV if unprivileged userns is restricted File: debian/patches/test-skip-TEST-43-PRIVATEUSER-UNPRIV-if-unprivileged-user.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=2aba69874c83289c43d199ca360aa2fc451486a7 * Drop debian/UBUNTU-src-test-test-execute.c-Skip-parts-of-test-execute-in-con.patch. This will be re-addressed with a different patch. File: debian/patches/debian/UBUNTU-src-test-test-execute.c-Skip-parts-of-test-execute-in-con.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c3cd814e028364fe0c641d4bacfce22aafd1b572 * Drop test-skip-failing-test-execute-tests-in-LXC.patch. This will be re-addressed with different patches. File: debian/patches/test-skip-failing-test-execute-tests-in-LXC.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ab853707f4cc3e7e2d5993ff38998c3c2c789f62 * test: temporarily skip credentials tests in LXC. This was already skipped in another patch, but now that we know what's going on with it, split it out. File: debian/patches/test-temporarily-skip-credentials-tests-in-LXC.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c71acb411d315267fe811f024cdab97e032453f3 * test: skip test-execute in arhmf LXC containers File: debian/patches/test-skip-test-execute-in-arhmf-LXC-containers.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1cb1e3060822bfadddead564e779942e73e02f62 * test: skip exec-privatenetwork-yes-privatemounts-yes.service in LXC (LP: #2046495) File: debian/patches/test-skip-exec-privatenetwork-yes-privatemounts-yes.servi.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3ab76fd2db4291ee0531a07085c72cee06cb0d12 * test: skip a systemd-run test if unprivileged userns is restricted File: debian/patches/test-skip-a-systemd-run-test-if-unprivileged-userns-is-re.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c85f2b4e32ee8fd1c0dc58d23e7fabdb7590d3cc * test-execute: skip tests that are broken without unprivileged userns File: debian/patches/test-execute-skip-tests-that-are-broken-without-unprivile.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7a6573c4f5133a7fec11fb059dd215f7c8c2204e -- Nick Rosbrook Wed, 24 Jan 2024 14:53:46 -0500 ** Changed in: systemd (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2046459 Title: systemd-gpt-auto-generator is omitted since 253.5-1ubuntu5 resulting in boot failure Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Mantic: Triaged Bug description: I have my system set up to rely on GPT auto generator together with Discoverable Partitions Specification (DPS). After upgrading my system the gpt generator is no longer included resulting in boot failure. I have been able to workaround this by setting up the mounts in fstab but that is unsatisfactory. Furthermore I work on an embedded device which uses Ubuntu as a base and relies on the GPT auto generator. In this case it is not possible for me to switch back to an old fstab file as we rely on some autodiscovery possible only with DPS. Even though it is not used by the default installation, I kindly request to revert a366279a84730e92ed734710560ea833709f359d. Even though the default does not require it does not mean that no one else does. Also the generator binary fairly small at a few dozen KB so not much is gained from omitting it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2046459/+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 1959047] Re: systemd ignores RootDirectory option in .service units
This bug was fixed in the package systemd - 255.2-3ubuntu2 --- systemd (255.2-3ubuntu2) noble; urgency=medium * test: skip test_exec_networknamespacepath if netns setup fails (LP: #2046498) Files: - debian/patches/lp2046498-test-skip-test_exec_networknamespacepath-if-netns-setup-f.patch - debian/patches/test-skip-failing-test-execute-tests-in-LXC.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=de1fcf756e47858f4a206db97434bce4a71384d0 * test: skip TEST-43-PRIVATEUSER-UNPRIV if unprivileged userns is restricted File: debian/patches/test-skip-TEST-43-PRIVATEUSER-UNPRIV-if-unprivileged-user.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=2aba69874c83289c43d199ca360aa2fc451486a7 * Drop debian/UBUNTU-src-test-test-execute.c-Skip-parts-of-test-execute-in-con.patch. This will be re-addressed with a different patch. File: debian/patches/debian/UBUNTU-src-test-test-execute.c-Skip-parts-of-test-execute-in-con.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c3cd814e028364fe0c641d4bacfce22aafd1b572 * Drop test-skip-failing-test-execute-tests-in-LXC.patch. This will be re-addressed with different patches. File: debian/patches/test-skip-failing-test-execute-tests-in-LXC.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ab853707f4cc3e7e2d5993ff38998c3c2c789f62 * test: temporarily skip credentials tests in LXC. This was already skipped in another patch, but now that we know what's going on with it, split it out. File: debian/patches/test-temporarily-skip-credentials-tests-in-LXC.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c71acb411d315267fe811f024cdab97e032453f3 * test: skip test-execute in arhmf LXC containers File: debian/patches/test-skip-test-execute-in-arhmf-LXC-containers.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1cb1e3060822bfadddead564e779942e73e02f62 * test: skip exec-privatenetwork-yes-privatemounts-yes.service in LXC (LP: #2046495) File: debian/patches/test-skip-exec-privatenetwork-yes-privatemounts-yes.servi.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3ab76fd2db4291ee0531a07085c72cee06cb0d12 * test: skip a systemd-run test if unprivileged userns is restricted File: debian/patches/test-skip-a-systemd-run-test-if-unprivileged-userns-is-re.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c85f2b4e32ee8fd1c0dc58d23e7fabdb7590d3cc * test-execute: skip tests that are broken without unprivileged userns File: debian/patches/test-execute-skip-tests-that-are-broken-without-unprivile.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7a6573c4f5133a7fec11fb059dd215f7c8c2204e -- Nick Rosbrook Wed, 24 Jan 2024 14:53:46 -0500 ** Changed in: systemd (Ubuntu) Status: Confirmed => Fix Released -- 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/1959047 Title: systemd ignores RootDirectory option in .service units Status in lxd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in lxd source package in Bionic: Fix Released Status in systemd source package in Bionic: Confirmed Status in systemd source package in Focal: Confirmed Status in systemd source package in Impish: Confirmed Bug description: [Impact] Ubuntu carries a patch on top of systemd [a] to silence namespace set up failures. This is meant as a workaround for a bug in the LXD version shipped in Ubuntu 18.04. Masking namespace set up failures creates a false sense of security for the user/admin. As mentioned in comment #1, systemd upstream explains that silencing this kind of error is dangerous and should be avoided. Backporting the LXD fix [b] to Ubuntu 18.04 would allow namespaces to work inside containers. This is the goal of this SRU. Ultimately, once LXD in Ubuntu 18.04 includes the fix [b], it would be possible to drop the Ubuntu-specific patch for systemd [a]. This is however *not an immediate concern for this SRU*. [Test Plan] 1) Create a 18.04 VM: $ lxc launch images:ubuntu/18.04 lp1959047 --vm $ sleep 30 # give it time to boot 1.5) Enable bionic-proposed: $ echo "deb http://archive.ubuntu.com/ubuntu bionic-proposed main restricted universe multiverse" | lxc file push - lp1959047/etc/apt/sources.list.d/proposed.list 2) Install and initialize LXD in it: $ lxc exec lp1959047 -- apt-get update $ lxc exec lp1959047 -- apt-get install -y lxd $ lxc exec lp1959047 -- lxd init --auto 3) Create a Jammy container and enable systemd debugging: $ lxc exec lp1959047 -- lxc
[Touch-packages] [Bug 2040405] Re: Merge openldap from Debian unstable for noble
This bug was fixed in the package openldap - 2.6.7+dfsg-1~exp1ubuntu1
---
openldap (2.6.7+dfsg-1~exp1ubuntu1) noble; urgency=medium
* Merge with Debian unstable (LP: #2040405). Remaining changes:
- Enable AppArmor support:
+ d/apparmor-profile: add AppArmor profile
+ d/rules: use dh_apparmor
+ d/control: Build-Depends on dh-apparmor
+ d/slapd.README.Debian: add note about AppArmor
- Enable ufw support:
+ d/control: suggest ufw.
+ d/rules: install ufw profile.
+ d/slapd.ufw.profile: add ufw profile.
- d/{rules,slapd.py}: Add apport hook.
- d/rules: better regexp to match the Maintainer tag in d/control,
needed in the Ubuntu case because of XSBC-Original-Maintainer
(Closes #960448, LP #1875697)
- d/t/smbk5pwd: Allow the openldap user to read the Heimdal master key in
the
smbk5pwd DEP8 test (LP #2004560)
[ Partially incorporated by Debian. ]
-- Sergio Durigan Junior Tue, 06 Feb
2024 14:46:16 -0500
** Changed in: openldap (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/2040405
Title:
Merge openldap from Debian unstable for noble
Status in openldap package in Ubuntu:
Fix Released
Bug description:
Upstream: tbd
Debian: 2.5.13+dfsg-52.6.6+dfsg-1~exp2
Ubuntu: 2.6.6+dfsg-1~exp1ubuntu1
Debian new has 2.6.6+dfsg-1~exp2, which may be available for merge
soon.
If it turns out this needs a sync rather than a merge, please change
the tag 'needs-merge' to 'needs-sync', and (optionally) update the
title as desired.
### New Debian Changes ###
openldap (2.5.13+dfsg-5) unstable; urgency=medium
* Fix sha2-contrib autopkgtest failure. Call slappasswd using its full path.
(Closes: #1030814)
* Disable flaky test test069-delta-multiprovider-starttls.
-- Ryan Tandy Tue, 07 Feb 2023 17:56:12 -0800
openldap (2.5.13+dfsg-4) unstable; urgency=medium
[ Andreas Hasenack ]
* d/rules: Fix passwd/sha2 build (Closes: #1030716, LP: #2000817)
* d/t/sha2-contrib: add test for sha2 module
-- Ryan Tandy Mon, 06 Feb 2023 19:21:05 -0800
openldap (2.5.13+dfsg-3) unstable; urgency=medium
[ Ryan Tandy ]
* Disable flaky test test063-delta-multiprovider. Mitigates #1010608.
[ Gioele Barabucci ]
* slapd.scripts-common: Avoid double-UTF8-encoding org name (Closes:
#1016185)
* d/slapd.scripts-common: Remove outdated `migrate_to_slapd_d_style`
* d/slapd.postinst: Remove test for ancient version
* slapd.scripts-common: Remove unused `normalize_ldif`
* d/slapd.scripts-common: Use sed instead of perl in `release_diagnostics`
-- Ryan Tandy Fri, 13 Jan 2023 16:29:59 -0800
openldap (2.5.13+dfsg-2) unstable; urgency=medium
* d/tests/smbk5pwd: Grant slapd access to /var/lib/heimdal-kdc. Fixes the
autopkgtest failure due to heimdal setting mode 700 on this directory.
(Closes: #1020442)
* d/source/lintian-overrides: Add wildcards to make overrides compatible
with both older and newer versions of lintian.
* d/slapd-contrib.lintian-overrides: Remove unused
custom-library-search-path override now that krb5-config no longer sets
-rpath.
-- Ryan Tandy Sat, 24 Sep 2022 12:40:21 -0700
openldap (2.5.13+dfsg-1) unstable; urgency=medium
* d/rules: Remove get-orig-source, now unnecessary.
* Check PGP signature when running uscan.
* d/watch: Modernize watch file; use repacksuffix.
* d/copyright: Update according to DEP-5.
* d/control: Add myself to Uploaders.
* New upstream release.
-- Sergio Durigan Junior Sun, 18 Sep 2022
18:29:46 -0400
openldap (2.5.12+dfsg-2) unstable; urgency=medium
* Stop slapd explicitly in prerm as a workaround for #1006147, which caused
dpkg-reconfigure to not restart the service, so the new configuration was
not applied. See also #994204. (Closes: #1010971)
-- Ryan Tandy Mon, 23 May 2022 10:14:53 -0700
openldap (2.5.12+dfsg-1) unstable; urgency=medium
* New upstream release.
- Fixed SQL injection in back-sql (ITS#9815) (CVE-2022-29155)
* Update debconf translations:
- German, thanks to Helge Kreutzmann. (Closes: #1007728)
- Spanish, thanks to Camaleón. (Closes: #1008529)
- Dutch, thanks to Frans Spiesschaert. (Closes: #1010034)
-- Ryan Tandy Wed, 04 May 2022 18:00:16 -0700
openldap (2.5.11+dfsg-1) unstable; urgency=medium
* Upload to unstable.
-- Ryan Tandy Fri, 11 Mar 2022 19:38:02 -0800
openldap (2.5.11+dfsg-1~exp1) experimental; urgency=medium
* New upstream release.
* Add openssl to Build-Depends to enable more checks in test067-tls.
* Update slapd-contrib's custom-library-search-path override to work with
current Lintian.
-- Ryan Tandy Sun, 23
[Touch-packages] [Bug 2047982] Re: Highlighting of patches offers insufficient contrast
This bug was fixed in the package vim - 2:9.1.0016-1ubuntu2 --- vim (2:9.1.0016-1ubuntu2) noble; urgency=medium * No-change rebuild with Python 3.12 as default -- Graham Inggs Fri, 19 Jan 2024 21:04:08 + ** Changed in: vim (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/2047982 Title: Highlighting of patches offers insufficient contrast Status in vim package in Ubuntu: Fix Released Bug description: With vim 2:9.0.2189-1ubuntu1 the coloring of patches has been changed. The result is that in konsole patches have become illegible. See appendix. Deleted lines have foreground cyan #18b2b2 and background light blue #7f7fff. Kind of blue on blue. Please, provide sane color defaults. The previous release used bright white on black for deleted lines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/2047982/+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 2051068] Re: GUI crashed after installed proposed package libegl-mesa0
This bug was fixed in the package mesa - 23.2.1-1ubuntu3.1~22.04.2 --- mesa (23.2.1-1ubuntu3.1~22.04.2) jammy; urgency=medium * patches: Revert a patch that caused GUI fail with OEM-6.1 kernel on Intel DG2. (LP: #2051068) mesa (23.2.1-1ubuntu3.1~22.04.1) jammy; urgency=medium * Backport to 22.04. (LP: #2037604) * rules: Disable rusticl, FTBFS on jammy. -- Timo Aaltonen Wed, 24 Jan 2024 14:01:34 +0200 ** Changed in: mesa (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2051068 Title: GUI crashed after installed proposed package libegl-mesa0 Status in linux-oem-6.1 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Won't Fix Status in mesa source package in Jammy: Fix Released Bug description: [Impact] OEM-6.1 kernel is missing support for minimum page size of 64k on DG2 (gfx12.5). Mesa 23.2 started using that, so it broke initializing the gpu on boot, causing a blank screen with no GDM running (with wayland, and fallback to X failed too). [Fix] Revert the commit that allows using 64k page size, since that's what the current version in jammy-updates is using. OEM-6.1 kernel is going away, no need to patch that anymore. No other kernel is affected, >6.2 works fine and thus this revert is not necessary in mantic or noble. [Test case] Install the update, boot up a machine with DG2 (iGPU or dGPU, doesn't matter). The login screen should appear. [Where things could go wrong] Hard to see how this could regress anything, as it just restores the limits for intel gfx12.5 as they were in the current mesa version in jammy. --- [Summary] After installed proposed package libegl-mesa0, reboot system. GUI crashed but still able to access system by ssh. [Steps to reproduce] 1. Boot into OS 2. sudo apt update 3. sudo apt upgrade 4. After upgrade process finished, reboot system. 5. GUI crashed. [Expected result] GUI displayed normally [Actual result] GUI crashed [Failure rate] 100% Tester comments --- if we don't upgrade libegl-mesa0, GUI will be fine. [Additional information] CID: 202303-31429 SKU: MYBY-DVT2-C5 Image: dell-bto-jammy-jellyfish-muk-X105-20231026-26_A02.iso system-manufacturer: Dell Inc. system-product-name: Precision 5680 CPU: Intel(R) Core(TM) i7-13700H kernel-version: 6.1.0-1028-oem [Stage] Issue reported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2051068/+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
