[Touch-packages] [Bug 2013333] Re: Quick Settings in the wrong place after Rotation
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Tags added: lunar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/201 Title: Quick Settings in the wrong place after Rotation Status in gnome-shell package in Ubuntu: New Bug description: I am currently testing the Ubuntu Desktop amd64 in Lunar Beta. - I opened the quick settings in the top right corner (Good) - I rotated the Laptop by ca. 90 deg => This triggered the Desktop Environment to rotate too (Good) - Note: quick settings are still open - I rotated the Laptop back => This triggered the Desktop Environment to rotate back too (Good) - The quick settings are now Horizontally centered (Unexpected) Note: I tested this during the Installation. I attached a screenshot that shows this. - ISO used: https://cdimage.ubuntu.com/daily-live/20230329/lunar-desktop-amd64.iso - ISO hash and signature verified Device: Lenovo ThinkPad Yoga 460 CPU: 64-Bit Intel Core i7-6500U @2.50GHz x 4 RAM: 8GB Graphics: Mesa Intel HD Graphics 520 (SKL GT2) Storage: 256GB SSD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/201/+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 1988133] Re: Arabic keyboard layout sends ligatures as one character (Laa Problem)
Thanks for the bug report. Please clarify what Ubuntu release and desktop environment you are using. ** Changed in: xorg (Ubuntu) Status: New => Incomplete ** Package changed: xorg (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1988133 Title: Arabic keyboard layout sends ligatures as one character (Laa Problem) Status in Ubuntu: Incomplete Bug description: Ubuntu sends [Arabic ligature glyphs](https://en.wikipedia.org/wiki/Arabic_alphabet#Ligatures) as a single glyph. For example, Laa+Alif ligature "لا" (U+0644, U+0627) is sent as "ﻻ" (U+FEFB), and similarly for (ﻷ، ﻵ، ﻹ). STEPS TO REPRODUCE Settings > Keyboard > Add default Arabic layout Type "ﻻ" (i.e: "b" in QWERTY keyboards) OBSERVED RESULT Output is ﻻ (U+FEFB) EXPECTED RESULT Output is لا (U+0644, U+0627). To clarify for English speakers, this is like having a key to type a ligature. Say that you want to press "b" to type two characters: fi but instead you get fi as a single character. This is exactly what's happening with this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1988133/+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 2006517] Re: Bluetooth works on desktop but not on ubuntu core
1. Downgraded bluez from 5.64-0ubuntu1 to 5.53-0ubuntu3.6 2. forgot the bt device on my phone and power cycle the machine ii bluez 5.53-0ubuntu3.6 amd64Bluetooth tools and daemons Linux u-Precision-5570 5.15.0-69-generic #76-Ubuntu SMP Fri Mar 17 17:19:29 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux 3. Ran setup again, and then ran demo, the move command still works, I can see cursor move. BTW, the commit Dilyn found shoule not be relavent, I see the same warning message with 5.15 kernel + 5.64 bluez 09572fca7223 Bluetooth: hci_sock: Add support for BT_{SND,RCV}BUF 2023-03-31T05:00:02.985301Z WARN ble::sys::mgmt: Failed to set BT_SNDMTU: Protocol not available (os error 92) -- 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/2006517 Title: Bluetooth works on desktop but not on ubuntu core Status in bluez package in Ubuntu: Confirmed Bug description: We have built a snap that uses some bluetooth functionality. The snap runs well when using Ubuntu desktop 22.04 (all updates applied end of Jan 2022). We have tried using this same snap on Ubuntu Core 22 running on X86_64. On some hardware platforms (thinkpad E15 and x86 Mac) everything works as expected. We can install the snap on Jammy 22.04 or Core 22 on these platforms and get expected functionality regardless of OS. On our targeted platform (a Dell 5570) things are not working. When running 22.04 Jammy, everything works. When running Core 22, some advanced bluetooth functionality is not available. Since the Core 22 image installs and runs on other X86_64 hardware we suspect a device driver issue. Attached are several files taken from the Dell 5570 1) dmesg from Core 22. 2) dmesg from Jammy 22.04 3) output of lspci from Jammy 22.04 4) Output of lsusb from Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+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 2006517] Re: Bluetooth works on desktop but not on ubuntu core
1. Fresh installed ubuntu-22.04.2-desktop 2. Installed 5.15 kernel ii bluez 5.64-0ubuntu1 amd64Bluetooth tools and daemons Linux u-Precision-5570 5.15.0-69-generic #76-Ubuntu SMP Fri Mar 17 17:19:29 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux 3. Installed customer's 2 snaps and run the setup and connect the bt device from my phone 4. The move command works, I can see cursor on my phone. -- 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/2006517 Title: Bluetooth works on desktop but not on ubuntu core Status in bluez package in Ubuntu: Confirmed Bug description: We have built a snap that uses some bluetooth functionality. The snap runs well when using Ubuntu desktop 22.04 (all updates applied end of Jan 2022). We have tried using this same snap on Ubuntu Core 22 running on X86_64. On some hardware platforms (thinkpad E15 and x86 Mac) everything works as expected. We can install the snap on Jammy 22.04 or Core 22 on these platforms and get expected functionality regardless of OS. On our targeted platform (a Dell 5570) things are not working. When running 22.04 Jammy, everything works. When running Core 22, some advanced bluetooth functionality is not available. Since the Core 22 image installs and runs on other X86_64 hardware we suspect a device driver issue. Attached are several files taken from the Dell 5570 1) dmesg from Core 22. 2) dmesg from Jammy 22.04 3) output of lspci from Jammy 22.04 4) Output of lsusb from Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+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 2012879] Re: indicator-messages-service crashed with SIGSEGV in ACT_IS_USER() from _act_user_update_from_object_path() from fetch_user_incrementally() from on_find_user_by_name_f
I'm hoping this was fixed at the same time as bug 1966905 by accountsservice 22.08.8-1ubuntu5 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2012879 Title: indicator-messages-service crashed with SIGSEGV in ACT_IS_USER() from _act_user_update_from_object_path() from fetch_user_incrementally() from on_find_user_by_name_finished() from g_task_return_now() Status in accountsservice package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/2416b63fd3efcd8ec09f184b6f50981fc56fb16d Crash in indicator-messages-service ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: indicator-messages 13.10.1+18.10.20180918-0ubuntu3 Uname: Linux 6.2.0-18-generic x86_64 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 14:25:09 2023 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service ExecutableTimestamp: 1633601577 ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service ProcCwd: /home/dan ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 11 SourcePackage: indicator-messages UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2012879/+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 2011309] Re: [HDA-Intel - HD-Audio Generic, playback] Pulseaudio fails to detect card- also hdaudio fails to load on boot, codecs not found, no sound from HDMI sources. also for
Current the machine in use is a mini-pc. Per other purchasers of the mini-pc on Amazon, the sound chips on this pc are not compatible with Ubuntu jammy-jellyfish and thus this writer should NOT have upgraded the pc to jammy-jellyfish which did not immediately but eventually appeared to kill sound on the pc. I have since USB ported Focal-Fossa back on this machine and the sound works fine and I set the pc to NEVER upgrade Ubuntu to Jammy. So there is no current reason to continue this bug, unless someone is aware of how Jammy would become compatible. I will leave it to the community to decide to close this bug. But I do not intend to pursue it since the mini-pc is a useful tool as it is and works quite fine with what it has got. It only costs $129 so it is not worth the sweat. -- 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/2011309 Title: [HDA-Intel - HD-Audio Generic, playback] Pulseaudio fails to detect card- also hdaudio fails to load on boot, codecs not found, no sound from HDMI sources. also for some reason Bluetooth does not work it has a fail loop that constantly connects and disconnects to Bluetooth devices. Status in pulseaudio package in Ubuntu: Opinion Bug description: Main issue is that HDMI sound does not work or load at all, it is not even an option in the 'Sound Settings' in GUI when it was working fine before. This started around March 3-4, 2023 per my syslog. Also on boot, 'hdaudio' fails and says no codecs found. And also I tried using Bluetooth devices but instead of connecting to Bluetooth they started a connect/disconnect loop which meant as far as I could tell Bluetooth was trying to connect but not succeeding when it had before. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2 ProcVersionSignature: User Name 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2013 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Mar 11 10:07:40 2023 InstallationDate: Installed on 2022-10-16 (145 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: USB Audio Device - USB Audio Device Title: [HDA-Intel - HD-Audio Generic, playback] Pulseaudio fails to detect card UpgradeStatus: Upgraded to jammy on 2022-11-24 (107 days ago) dmi.bios.date: 07/19/2022 dmi.bios.release: 0.8 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: ASB20008 dmi.board.asset.tag: Default string dmi.board.name: ATOPNUC MA90 dmi.board.vendor: ATOPNUC dmi.board.version: Version 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrASB20008:bd07/19/2022:br0.8:efr1.18:svnATOPNUC:pnATOPNUCMA90:pvrV1.0:rvnATOPNUC:rnATOPNUCMA90:rvrVersion1.0:cvnDefaultstring:ct35:cvrDefaultstring:skuDefaultSKU: dmi.product.family: Series 20 dmi.product.name: ATOPNUC MA90 dmi.product.sku: Default SKU dmi.product.version: V1.0 dmi.sys.vendor: ATOPNUC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2011309/+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 2011309] Re: [HDA-Intel - HD-Audio Generic, playback] Pulseaudio fails to detect card- also hdaudio fails to load on boot, codecs not found, no sound from HDMI sources. also for
** Changed in: pulseaudio (Ubuntu) Status: New => Opinion -- 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/2011309 Title: [HDA-Intel - HD-Audio Generic, playback] Pulseaudio fails to detect card- also hdaudio fails to load on boot, codecs not found, no sound from HDMI sources. also for some reason Bluetooth does not work it has a fail loop that constantly connects and disconnects to Bluetooth devices. Status in pulseaudio package in Ubuntu: Opinion Bug description: Main issue is that HDMI sound does not work or load at all, it is not even an option in the 'Sound Settings' in GUI when it was working fine before. This started around March 3-4, 2023 per my syslog. Also on boot, 'hdaudio' fails and says no codecs found. And also I tried using Bluetooth devices but instead of connecting to Bluetooth they started a connect/disconnect loop which meant as far as I could tell Bluetooth was trying to connect but not succeeding when it had before. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2 ProcVersionSignature: User Name 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2013 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Mar 11 10:07:40 2023 InstallationDate: Installed on 2022-10-16 (145 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: USB Audio Device - USB Audio Device Title: [HDA-Intel - HD-Audio Generic, playback] Pulseaudio fails to detect card UpgradeStatus: Upgraded to jammy on 2022-11-24 (107 days ago) dmi.bios.date: 07/19/2022 dmi.bios.release: 0.8 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: ASB20008 dmi.board.asset.tag: Default string dmi.board.name: ATOPNUC MA90 dmi.board.vendor: ATOPNUC dmi.board.version: Version 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrASB20008:bd07/19/2022:br0.8:efr1.18:svnATOPNUC:pnATOPNUCMA90:pvrV1.0:rvnATOPNUC:rnATOPNUCMA90:rvrVersion1.0:cvnDefaultstring:ct35:cvrDefaultstring:skuDefaultSKU: dmi.product.family: Series 20 dmi.product.name: ATOPNUC MA90 dmi.product.sku: Default SKU dmi.product.version: V1.0 dmi.sys.vendor: ATOPNUC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2011309/+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 1988133] Re: Arabic keyboard layout sends ligatures as one character (Laa Problem)
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1988133 Title: Arabic keyboard layout sends ligatures as one character (Laa Problem) Status in xorg package in Ubuntu: New Bug description: Ubuntu sends [Arabic ligature glyphs](https://en.wikipedia.org/wiki/Arabic_alphabet#Ligatures) as a single glyph. For example, Laa+Alif ligature "لا" (U+0644, U+0627) is sent as "ﻻ" (U+FEFB), and similarly for (ﻷ، ﻵ، ﻹ). STEPS TO REPRODUCE Settings > Keyboard > Add default Arabic layout Type "ﻻ" (i.e: "b" in QWERTY keyboards) OBSERVED RESULT Output is ﻻ (U+FEFB) EXPECTED RESULT Output is لا (U+0644, U+0627). To clarify for English speakers, this is like having a key to type a ligature. Say that you want to press "b" to type two characters: fi but instead you get fi as a single character. This is exactly what's happening with this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1988133/+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 1988133] [NEW] Arabic keyboard layout sends ligatures as one character (Laa Problem)
You have been subscribed to a public bug: Ubuntu sends [Arabic ligature glyphs](https://en.wikipedia.org/wiki/Arabic_alphabet#Ligatures) as a single glyph. For example, Laa+Alif ligature "لا" (U+0644, U+0627) is sent as "ﻻ" (U+FEFB), and similarly for (ﻷ، ﻵ، ﻹ). STEPS TO REPRODUCE Settings > Keyboard > Add default Arabic layout Type "ﻻ" (i.e: "b" in QWERTY keyboards) OBSERVED RESULT Output is ﻻ (U+FEFB) EXPECTED RESULT Output is لا (U+0644, U+0627). To clarify for English speakers, this is like having a key to type a ligature. Say that you want to press "b" to type two characters: fi but instead you get fi as a single character. This is exactly what's happening with this issue. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Arabic keyboard layout sends ligatures as one character (Laa Problem) https://bugs.launchpad.net/bugs/1988133 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 2006959] Re: package linux-image-5.14.0-1057-oem 5.14.0-1057.64 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
*** This bug is a duplicate of bug 2006793 *** https://bugs.launchpad.net/bugs/2006793 ** This bug has been marked a duplicate of bug 2006793 package linux-image-5.15.0-60-generic 5.15.0-60.66~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 -- 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/2006959 Title: package linux-image-5.14.0-1057-oem 5.14.0-1057.64 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: I don't have any further information. I got this message when I started using my machine for the day, without having interacted with the package manager recently. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1057-oem 5.14.0-1057.64 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Feb 10 09:03:27 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-10-09 (488 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: initramfs-tools Title: package linux-image-5.14.0-1057-oem 5.14.0-1057.64 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 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/2006959/+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 1856871] Re: i/o error if next unused loop device is queried
** Also affects: parted (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: udev (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: snapd (Ubuntu Bionic) Importance: Undecided Status: New ** No longer affects: parted (Ubuntu Bionic) ** No longer affects: snapd (Ubuntu Bionic) ** No longer affects: systemd (Ubuntu Bionic) ** No longer affects: udev (Ubuntu Bionic) ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Jorge Merlino (jorge-merlino) -- 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/1856871 Title: i/o error if next unused loop device is queried Status in linux package in Ubuntu: Fix Released Status in parted package in Ubuntu: Invalid Status in snapd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in udev package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: Fix Released Bug description: [Impact] * There's an I/O error on fsync() in a detached loop device if it has been previously attached. The issue is that write cache is enabled in the attach path in loop_configure() but it isn't disabled in the detach path; thus it remains enabled in the block device regardless of whether it is attached or not. * fsync() on detached loop devices can be called by partition tools and commands run by sosreport, so the unexpected kernel error message might surprise users or even distract from the actual issue being investigatedr. It might also trigger alerts in logging/monitoring/alerting stacks [Fix] * Disable write cache in the detach path [Test Plan] * Attach and detach an image to a loop device and test fsync return value aterwards # DEV=/dev/loop7 # IMG=/tmp/image # truncate --size 1M $IMG # losetup $DEV $IMG # losetup -d $DEV Before: # strace -e fsync parted -s $DEV print 2>&1 | grep fsync fsync(3)= -1 EIO (Input/output error) Warning: Error fsyncing/closing /dev/loop7: Input/output error [ 982.529929] blk_update_request: I/O error, dev loop7, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 After: # strace -e fsync parted -s $DEV print 2>&1 | grep fsync fsync(3)= 0 [Where problems could occur] * The detach path for block devices is modified. Worst case scenario would be an error when detaching loop devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856871/+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 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)
We are seeing SIGSEGV related to this in Bionic. lp1815101-0006-network- make-KeepConfiguration-static-drop-DHCP-addr.patch is missing network checks in link_drop_foreign_config Would it be possible to incorporate this patch from upstream to prevent this? https://github.com/systemd/systemd/commit/b1b0b42e48303134731e017a108c6c334ef5f4c8 Core was generated by `/lib/systemd/systemd-networkd'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x555962aa1c34 in link_drop_foreign_config (link=link@entry=0x555963583f30) at ../src/network/networkd-link.c:2741 2741../src/network/networkd-link.c: No such file or directory. (gdb) bt #0 0x555962aa1c34 in link_drop_foreign_config (link=link@entry=0x555963583f30) at ../src/network/networkd-link.c:2741 #1 0x555962aa233d in link_carrier_lost.lto_priv.328 (link=, link=) at ../src/network/networkd-link.c:3462 #2 0x555962a8e9b2 in link_update (m=0x5559635702c0, link=) at ../src/network/networkd-link.c:3698 #3 manager_rtnl_process_link (rtnl=, message=0x5559635702c0, userdata=) at ../src/network/networkd-manager.c:713 #4 0x555962a48a16 in process_match (m=0x5559635702c0, rtnl=0x55596355d990) at ../src/libsystemd/sd-netlink/sd-netlink.c:388 #5 process_running (ret=0x0, rtnl=0x55596355d990) at ../src/libsystemd/sd-netlink/sd-netlink.c:418 #6 sd_netlink_process (rtnl=0x55596355d990, ret=ret@entry=0x0) at ../src/libsystemd/sd-netlink/sd-netlink.c:452 #7 0x555962a48cb3 in time_callback (s=, usec=, userdata=) at ../src/libsystemd/sd-netlink/sd-netlink.c:759 #8 0x555962a4dbae in source_dispatch (s=s@entry=0x55596355dce0) at ../src/libsystemd/sd-event/sd-event.c:2311 #9 0x555962a4de2a in sd_event_dispatch (e=, e@entry=0x55596355bf70) at ../src/libsystemd/sd-event/sd-event.c:2663 #10 0x555962a4dfb9 in sd_event_run (e=, e@entry=0x55596355bf70, timeout=timeout@entry=18446744073709551615) at ../src/libsystemd/sd-event/sd-event.c:2723 #11 0x555962a4e1fb in sd_event_loop (e=) at ../src/libsystemd/sd-event/sd-event.c:2744 #12 0x555962a223d6 in main (argc=, argv=) at ../src/network/networkd.c:158 (gdb) p link->network $2 = (struct Network *) 0x0 -- 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/1815101 Title: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted) Status in netplan: Triaged Status in heartbeat package in Ubuntu: Won't Fix Status in keepalived package in Ubuntu: In Progress Status in systemd package in Ubuntu: Fix Released Status in keepalived source package in Xenial: Confirmed Status in systemd source package in Xenial: Won't Fix Status in keepalived source package in Bionic: Confirmed Status in systemd source package in Bionic: Fix Released Status in systemd source package in Disco: Won't Fix Status in systemd source package in Eoan: Fix Released Status in keepalived source package in Focal: Confirmed Status in systemd source package in Focal: Fix Released Bug description: [impact] - ALL related HA software has a small problem if interfaces are being managed by systemd-networkd: nic restarts/reconfigs are always going to wipe all interfaces aliases when HA software is not expecting it to (no coordination between them. - keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is smarter in this case because it has a service monitor that will restart the virtual IP resource, in affected node & nic, before considering a real failure, but other HA service might consider a real failure when it is not. [test case] - comment #14 is a full test case: to have 3 node pacemaker, in that example, and cause a networkd service restart: it will trigger a failure for the virtual IP resource monitor. - other example is given in the original description for keepalived. both suffer from the same issue (and other HA softwares as well). [regression potential] - this backports KeepConfiguration parameter, which adds some significant complexity to networkd's configuration and behavior, which could lead to regressions in correctly configuring the network at networkd start, or incorrectly maintaining configuration at networkd restart, or losing network state at networkd stop. - Any regressions are most likely to occur during networkd start, restart, or stop, and most likely to involve missing or incorrect ip address(es). - the change is based in upstream patches adding the exact feature we needed to fix this issue & it will be integrated with a netplan change to add the needed stanza to systemd nic configuration file (KeepConfiguration=) [other info] original description: --- Configure netplan for interfaces, for example (a working config with IP addresses obfuscated) network: ethernets:
[Touch-packages] [Bug 2012563] Re: unsupported mount options: 'nofail', 'nostrictatime', 'lazytime', and 'nolazytime'
I submitted an issue and accompanying PR for this bug on the apparmor GitLab repository. Issue: https://gitlab.com/apparmor/apparmor/-/issues/312 PR: https://gitlab.com/apparmor/apparmor/-/merge_requests/1004 ** Bug watch added: gitlab.com/apparmor/apparmor/-/issues #312 https://gitlab.com/apparmor/apparmor/-/issues/312 -- 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/2012563 Title: unsupported mount options: 'nofail', 'nostrictatime', 'lazytime', and 'nolazytime' Status in apparmor package in Ubuntu: New Bug description: The following mount options are unsupported: 'nofail', 'nostrictatime', 'lazytime', and 'nolazytime'. Other mount options have mappings from options to bitflags in `parser/mount.cc`, and the bitflags themselves are defined in `parser/mount.h`. Should the aforementioned mount options be included as well, or is there a reason why they are excluded? snapd currently assumes that they are supported, resulting in an error from the apparmor parser when a snap is connected with those options. I'd be happy to file a PR to add these mappings if I knew what the new bitflags should be defined as, and if/how they should be used elsewhere. For completeness: 1) This is a question/bug regarding the source code from the 'ubuntu/devel' branch (and presumably other branches), not a particular release. 2) Same as 1). 3) I expected the apparmor parser to recognize the 'nofail', 'nostrictatime', 'laztime', and 'nolazytime' mount options. 4) The apparmor parser threw an error with message "unsupported mount options" (from within `parser/mount.cc`). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2012563/+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 2000817] Re: Wrong SHA256-value computed on kinetic
https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/1983605 is the exim4 bug. I would ask the SRU team to ignore the exim4 DEP8 errors on basis of that. -- 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/2000817 Title: Wrong SHA256-value computed on kinetic Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Jammy: In Progress Status in openldap source package in Kinetic: Fix Committed Status in openldap source package in Lunar: Fix Released Status in openldap package in Debian: Fix Released Bug description: [ Impact ] OpenLDAP deployments using the contrib pw-sha2 module are not able to authenticate their users because the SHA2 calculation is done incorrectly. Even though this is a contrib module, from an upstream PoV, it is shipped in the Ubuntu (and Debian) OpenLDAP packages, and available for use. Some fix possibilities were discussed in comment #5, and we selected the one with the least impact to OpenLDAP users at large, which is to recompile that module only without the strict-aliasing optimization. This update makes that change, and also includes a DEP8 change to verify it. We didn't use a patch for the pw-sha2 Makefile because d/rules overrides the OPT variable in the make command line (https://git.launchpad.net/~ahasenack/ubuntu/+source/openldap/tree/debian/rules?h=lunar- slapd-sha2-2000817#n44) [ Test Plan ] # Install slapd and openssl $ sudo apt install slapd openssl # Run the following script #!/bin/bash reference_hash="{SHA256}$(echo -n secret | openssl dgst -sha256 -binary | openssl enc -base64)" test_hash=$(slappasswd -s secret -h '{SHA256}' -o module-load=pw-sha2) echo "Reference hash of \"secret\" (openssl): ${reference_hash}" echo "slapd's pw-sha2 hash: ${test_hash}" if [ "${reference_hash}" != "${test_hash}" ]; then echo "ERROR: hashes differ" exit 1 else echo "PASS: hashes are identical" fi With the affected openldap package installed, the script should print an error. With the packages from proposed, the hashes should be identical. [ Where problems could occur ] The fix is a change of a compiler option strictly when building only the pw-sha2 module, so it's very localized. It could affect the performance of this module (for the worse), but it's already not working correctly. [ Other Info ] Not at this time. [Original Description] The OpenLDAP-contrib module sha2 (located in contrib/slapd- modules/passwd/sha2/) computes a wrong SHA256/SSHA256-hash on Ubuntu kinetic. This breaks our current password-authentication in ldap. The problematic computation: $ slappasswd -s secret -h '{SHA256}' -o module-load=pw-sha2 {SHA256}WIrrpN3OjEVOUf6yrH1j+o+ODuUuNBo979Od4UXnu54= The (correct) reference-value on the same system (or older ubuntu Versions): $ echo -n "secret" | openssl dgst -sha256 -binary | openssl enc -base64 K7gNU3sdo+OL0wNhqoVWhr3g6s1xYv72ol/pe/Unols= We nailed the problem down to a bug in the gcc-optimizer for strict- aliasing. so most probably the gcc-version on kinetic (v12.2.0) is the reason. The workaround is to compile the sha2-Module with the flag "-fno-strict-aliasing". Then the correct value is computed. An example taken from a git-compiled version of OpenLDAP 2.5.13: $ ./servers/slapd/slappasswd -T passwd -s secret -h '{SHA256}' -o module-load=pw-sha2 -o module-path=contrib/slapd-modules/passwd/sha2/.libs {SHA256}K7gNU3sdo+OL0wNhqoVWhr3g6s1xYv72ol/pe/Unols= Ubuntu: Description:Ubuntu 22.10 Release:22.10 OpenLDAP-Package: 2.5.13+dfsg-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2000817/+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 2013376] Re: package libmagic1 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/magic.mime', which is different from other instances of package libmagi
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to file in Ubuntu. https://bugs.launchpad.net/bugs/2013376 Title: package libmagic1 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/magic.mime', which is different from other instances of package libmagic1:i386 Status in file package in Ubuntu: New Bug description: package libmagic1 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/magic.mime', which is different from other instances of package libmagic1:i386 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libmagic1 (not installed) ProcVersionSignature: Ubuntu 4.15.0-106.107~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-106-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 Date: Tue Mar 28 01:31:18 2023 DpkgHistoryLog: Start-Date: 2023-03-28 01:31:17 Commandline: apt-get install libmagic1:i386 Requested-By: suneel (1000) Install: libmagic1:i386 (1:5.25-2ubuntu1) DpkgTerminalLog: Preparing to unpack .../libmagic1_1%3a5.25-2ubuntu1_i386.deb ... Unpacking libmagic1:i386 (1:5.25-2ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/libmagic1_1%3a5.25-2ubuntu1_i386.deb (--unpack): trying to overwrite shared '/etc/magic.mime', which is different from other instances of package libmagic1:i386 DuplicateSignature: package:libmagic1:(not installed) Unpacking libmagic1:i386 (1:5.25-2ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/libmagic1_1%3a5.25-2ubuntu1_i386.deb (--unpack): trying to overwrite shared '/etc/magic.mime', which is different from other instances of package libmagic1:i386 ErrorMessage: trying to overwrite shared '/etc/magic.mime', which is different from other instances of package libmagic1:i386 InstallationDate: Installed on 2019-09-27 (1280 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32ubuntu0.1 SourcePackage: file Title: package libmagic1 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/magic.mime', which is different from other instances of package libmagic1:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file/+bug/2013376/+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 2013376] [NEW] package libmagic1 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/magic.mime', which is different from other instances of package libma
Public bug reported: package libmagic1 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/magic.mime', which is different from other instances of package libmagic1:i386 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libmagic1 (not installed) ProcVersionSignature: Ubuntu 4.15.0-106.107~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-106-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 Date: Tue Mar 28 01:31:18 2023 DpkgHistoryLog: Start-Date: 2023-03-28 01:31:17 Commandline: apt-get install libmagic1:i386 Requested-By: suneel (1000) Install: libmagic1:i386 (1:5.25-2ubuntu1) DpkgTerminalLog: Preparing to unpack .../libmagic1_1%3a5.25-2ubuntu1_i386.deb ... Unpacking libmagic1:i386 (1:5.25-2ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/libmagic1_1%3a5.25-2ubuntu1_i386.deb (--unpack): trying to overwrite shared '/etc/magic.mime', which is different from other instances of package libmagic1:i386 DuplicateSignature: package:libmagic1:(not installed) Unpacking libmagic1:i386 (1:5.25-2ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/libmagic1_1%3a5.25-2ubuntu1_i386.deb (--unpack): trying to overwrite shared '/etc/magic.mime', which is different from other instances of package libmagic1:i386 ErrorMessage: trying to overwrite shared '/etc/magic.mime', which is different from other instances of package libmagic1:i386 InstallationDate: Installed on 2019-09-27 (1280 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32ubuntu0.1 SourcePackage: file Title: package libmagic1 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/magic.mime', which is different from other instances of package libmagic1:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: file (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-conflict xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to file in Ubuntu. https://bugs.launchpad.net/bugs/2013376 Title: package libmagic1 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/magic.mime', which is different from other instances of package libmagic1:i386 Status in file package in Ubuntu: New Bug description: package libmagic1 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/magic.mime', which is different from other instances of package libmagic1:i386 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libmagic1 (not installed) ProcVersionSignature: Ubuntu 4.15.0-106.107~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-106-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 Date: Tue Mar 28 01:31:18 2023 DpkgHistoryLog: Start-Date: 2023-03-28 01:31:17 Commandline: apt-get install libmagic1:i386 Requested-By: suneel (1000) Install: libmagic1:i386 (1:5.25-2ubuntu1) DpkgTerminalLog: Preparing to unpack .../libmagic1_1%3a5.25-2ubuntu1_i386.deb ... Unpacking libmagic1:i386 (1:5.25-2ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/libmagic1_1%3a5.25-2ubuntu1_i386.deb (--unpack): trying to overwrite shared '/etc/magic.mime', which is different from other instances of package libmagic1:i386 DuplicateSignature: package:libmagic1:(not installed) Unpacking libmagic1:i386 (1:5.25-2ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/libmagic1_1%3a5.25-2ubuntu1_i386.deb (--unpack): trying to overwrite shared '/etc/magic.mime', which is different from other instances of package libmagic1:i386 ErrorMessage: trying to overwrite shared '/etc/magic.mime', which is different from other instances of package libmagic1:i386 InstallationDate: Installed on 2019-09-27 (1280 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32ubuntu0.1 SourcePackage: file Title: package libmagic1 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/magic.mime', which is different from other instances of package libmagic1:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file/+bug/2013376/+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 1994936] Re: initramfs need to mount efivarfs because kernel 6.0 deprecated 'efivars' sysfs interface
Due to lunar bumped shellcheck to version 0.9.0-1, a lot of shellcheck findings need to be fixed to prevent build failure. -- 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/1994936 Title: initramfs need to mount efivarfs because kernel 6.0 deprecated 'efivars' sysfs interface Status in OEM Priority Project: In Progress Status in initramfs-tools package in Ubuntu: New Status in initramfs-tools package in Debian: Fix Released Bug description: [ Impact ] kernel 6.0 deprecated efivars sysfs interface [1]. For Intel VROC RAID, mdadm needs initramfs to mount efivarfs instead. [1] The commit: commit 0f5b2c69a4cbe4166ca24b76d5ada98ed2867741 Author: Ard Biesheuvel Date: Mon Jun 20 13:34:03 2022 +0200 efi: vars: Remove deprecated 'efivars' sysfs interface [ Test Plan ] 1. Install initramfs-tools 2. update-initramfs -u 3. unmkinitramfs initrd.img-`uname -r` /tmp/extract-initramfs 4. Check if boot script 00_mount_efivarfs exists in directory /tmp/extract-initramfs/main/scripts/init-top/ 5. Check /tmp/extract-initramfs/main/scripts/init-top/ORDER if the boot script 00_mount_efivarfs will be execute before udev. [ Where problems could occur ] Not sure if there any other tools/utilities also need to mount efivarfs as early as mdadm but the probability of file conflict should be very low. Also, there are no impact mounting efivarfs multiple times. mount: /sys/firmware/efi/efivars: efivarfs already mounted on /sys/firmware/efi/efivars. [ Scope ] Jammy, Kinetic [ Other Info ] The private bug link https://bugs.launchpad.net/somerville/+bug/1990231 debian MR: https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/66 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1994936/+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 1956112] Re: Livepatch icon is shown on non-Livepatch systems
This may be solved now? I didn't see the icon in brand new jammy or lunar VMs. -- 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/1956112 Title: Livepatch icon is shown on non-Livepatch systems Status in software-properties package in Ubuntu: Triaged Bug description: The icon included with software-properties-gtk is shown in the applications list by default. This consumes screen real estate for something a large number of people cannot or are not using. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1956112/+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 2012298] Re: PasswordAuthenticaion in sshd_config.d
I think I found a relevant upstream bug [0], fixed by [1]. If the patch applies fairly cleanly to the version in Focal this could be good SRU material. [0] https://bugzilla.mindrot.org/show_bug.cgi?id=3122 [1] https://github.com/openssh/openssh-portable/commit/7af1e92cd289b7eaa9a683e9a6f2fddd98f37a01 ** Changed in: openssh (Ubuntu Focal) Status: Confirmed => Triaged ** Bug watch added: OpenSSH Portable Bugzilla #3122 https://bugzilla.mindrot.org/show_bug.cgi?id=3122 ** Also affects: openssh via https://bugzilla.mindrot.org/show_bug.cgi?id=3122 Importance: Unknown Status: Unknown -- 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/2012298 Title: PasswordAuthenticaion in sshd_config.d Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Focal: Triaged Bug description: The stanza Match User PasswordAuthentication no in /etc/ssh/sshd_config works as expected. The same stanza in /etc/ssh/sshd_config.d/username.conf does not work. The Include in /etc/ssh/sshd_config is not commented out, and /usr/sbin/sshd -D -ddd shows the username.config file being parsed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.2p1-4ubuntu0.5 ProcVersionSignature: Ubuntu 5.4.0-131.147-generic 5.4.210 Uname: Linux 5.4.0-131-generic x86_64 NonfreeKernelModules: falcon_lsm_serviceable falcon_nf_netcontain falcon_kal falcon_lsm_pinned_14713 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Mar 20 13:34:14 2023 InstallationDate: Installed on 2022-11-04 (136 days ago) InstallationMedia: SSHDConfig: Error: command ['pkexec', '/usr/sbin/sshd', '-T'] failed with exit code 127: pkexec must be setuid root SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/2012298/+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 2012563] Re: unsupported mount options: 'nofail', 'nostrictatime', 'lazytime', and 'nolazytime'
The attachment "Patch adding mount options nostrictatime, lazytime, and nolazytime" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- 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/2012563 Title: unsupported mount options: 'nofail', 'nostrictatime', 'lazytime', and 'nolazytime' Status in apparmor package in Ubuntu: New Bug description: The following mount options are unsupported: 'nofail', 'nostrictatime', 'lazytime', and 'nolazytime'. Other mount options have mappings from options to bitflags in `parser/mount.cc`, and the bitflags themselves are defined in `parser/mount.h`. Should the aforementioned mount options be included as well, or is there a reason why they are excluded? snapd currently assumes that they are supported, resulting in an error from the apparmor parser when a snap is connected with those options. I'd be happy to file a PR to add these mappings if I knew what the new bitflags should be defined as, and if/how they should be used elsewhere. For completeness: 1) This is a question/bug regarding the source code from the 'ubuntu/devel' branch (and presumably other branches), not a particular release. 2) Same as 1). 3) I expected the apparmor parser to recognize the 'nofail', 'nostrictatime', 'laztime', and 'nolazytime' mount options. 4) The apparmor parser threw an error with message "unsupported mount options" (from within `parser/mount.cc`). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2012563/+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 2012879] Re: indicator-messages-service crashed with SIGSEGV in ACT_IS_USER() from _act_user_update_from_object_path() from fetch_user_incrementally() from on_find_user_by_name_f
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: https://iso.qa.ubuntu.com/qatracker/reports/bugs/2012879 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2012879 Title: indicator-messages-service crashed with SIGSEGV in ACT_IS_USER() from _act_user_update_from_object_path() from fetch_user_incrementally() from on_find_user_by_name_finished() from g_task_return_now() Status in accountsservice package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/2416b63fd3efcd8ec09f184b6f50981fc56fb16d Crash in indicator-messages-service ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: indicator-messages 13.10.1+18.10.20180918-0ubuntu3 Uname: Linux 6.2.0-18-generic x86_64 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 14:25:09 2023 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service ExecutableTimestamp: 1633601577 ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service ProcCwd: /home/dan ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 11 SourcePackage: indicator-messages UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2012879/+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 1973734] Re: FTBFS on riscv64 in focal
@brian I'm sorry, but with block-proposed-focal set it means that affected users on riscv64 don't have uptodata pulseaudio. can we please release this? -- 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/1973734 Title: FTBFS on riscv64 in focal Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Committed Bug description: [Impact] * FTBFS on riscv64 in focal in unittest of volume test * Disable that unit test, as later releases do not run unittests on riscv64, and it's better to have up to date pulseaudio on riscv64 (with many security fixes), even if it doesn't completely correctly work. [Test Plan] * autopkgtests pass * riscv64 build is successful [Where problems could occur] * volume-test probably indicates that one can't set volume correctly on riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1973734/+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 2012374] Re: Cannot enable the TUI: error opening terminal [TERM=]
https://github.com/canonical/apport/pull/147 got merged. ** Changed in: apport (Ubuntu) Status: In Progress => Fix Committed ** Changed in: apport Status: In Progress => Fix Committed -- 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/2012374 Title: Cannot enable the TUI: error opening terminal [TERM=] Status in Apport: Fix Committed Status in apport package in Ubuntu: Fix Committed Bug description: I try to analyze a crash report on riscv64. I am connected to the system via ssh. sudo DEBUGINFOD_VERBOSE=1 apport-retrace --gdb --sandbox system --cache ~/.cache/apport-retrace /var/crash/_usr_bin_qemu-x86_64-static.0.crash In the opened gdb I try to show the source: (gdb) lay src Cannot enable the TUI: error opening terminal [TERM=] My expectation is that gdb shows the source layout. gdb works fine outside apport-retrace. # echo $TERM xterm-256color To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2012374/+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 2012563] Re: unsupported mount options: 'nofail', 'nostrictatime', 'lazytime', and 'nolazytime'
Attached is a patch which adds support for 'nostrictatime', 'lazytime', and 'nolazytime'. Since 'strictatime' already existed and documentation suggested 'nostrictatime' should already be included as well, 'nostrictatime' is a simple inclusion. The kernel supports `MS_LAZYTIME` as `(1 << 25)`, so I added that to `parser/mount.h` with the corresponding 'lazytime' and 'nolazytime' options in `parser/mount.cc`. More work is needed to understand userspace mount options such as 'nofail' which mount supports, so this patch does not include any fixes in that regard. ** Patch added: "Patch adding mount options nostrictatime, lazytime, and nolazytime" https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2012563/+attachment/5659128/+files/0001-Bug-2012563-added-mount-options-nostrictatime-lazyti.patch -- 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/2012563 Title: unsupported mount options: 'nofail', 'nostrictatime', 'lazytime', and 'nolazytime' Status in apparmor package in Ubuntu: New Bug description: The following mount options are unsupported: 'nofail', 'nostrictatime', 'lazytime', and 'nolazytime'. Other mount options have mappings from options to bitflags in `parser/mount.cc`, and the bitflags themselves are defined in `parser/mount.h`. Should the aforementioned mount options be included as well, or is there a reason why they are excluded? snapd currently assumes that they are supported, resulting in an error from the apparmor parser when a snap is connected with those options. I'd be happy to file a PR to add these mappings if I knew what the new bitflags should be defined as, and if/how they should be used elsewhere. For completeness: 1) This is a question/bug regarding the source code from the 'ubuntu/devel' branch (and presumably other branches), not a particular release. 2) Same as 1). 3) I expected the apparmor parser to recognize the 'nofail', 'nostrictatime', 'laztime', and 'nolazytime' mount options. 4) The apparmor parser threw an error with message "unsupported mount options" (from within `parser/mount.cc`). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2012563/+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 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
Another affected user. Here using VNC through Apache Guacamole with XFCE4 as a desktop manager. Similar errors to others: $ firefox 2023/03/30 14:56:04.261227 cmd_run.go:1055: WARNING: cannot start document portal: Can't mount path /home/student/.cache/doc /user.slice/user-1000.slice/session-1.scope is not a snap cgroup The DBUS_SESSION_ADDRESS is set: DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus- XNw4LGQaye,guid=488bab5d48a052fe381e2fa76425a2f9 ..but the path it refers to doesn't exist. If I try to check the systemd --user status I get: $ systemd --user Trying to run as user instance, but $XDG_RUNTIME_DIR is not set. ..so the fixes involving manually changing the DBUS address won't work. All other graphical apps work, it's just the confined snap apps which don't. -- 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/1951491 Title: Can't run snaps: .slice/session-1.scope is not a snap cgroup Status in X2Go: New Status in Xpra Terminal Server: New Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Status in x2goserver package in Ubuntu: Confirmed Status in snapd package in Debian: New Status in snapd package in Fedora: New Bug description: I just upgraded from hirsute to impish using do-release-upgrade. On the upgraded system, I can't run either firefox or chromium (both of which worked fine under hirsute). Both fail with: /user.slice/user-NNN.slice/session-1.scope is not a snap cgroup where NNN is my uid With firefox, I was able to fix the problem with: snap remove --purge firefox apt purge firefox apt install firefox Now firefox works. But I tried the same thing substituting chromium- browser for firefox, and it didn't help: chromium fails with the same error message. I guess there must be something left over from the hirsute version of snapd that isn't getting noticed or cleared by the impish version? Someone suggested this might be related to bug 1850667, but that bug is marked fixed as of a couple months ago, and I just did this upgrade today. Also, it doesn't mention the error message I'm seeing. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: snapd 2.53+21.10ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Nov 18 18:12:45 2021 InstallationDate: Installed on 2020-04-29 (568 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snapd UpgradeStatus: Upgraded to impish on 2021-11-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/x2go/+bug/1951491/+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 1994936] Re: initramfs need to mount efivarfs because kernel 6.0 deprecated 'efivars' sysfs interface
that debdiff does a lot more than just adds the script? -- 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/1994936 Title: initramfs need to mount efivarfs because kernel 6.0 deprecated 'efivars' sysfs interface Status in OEM Priority Project: In Progress Status in initramfs-tools package in Ubuntu: New Status in initramfs-tools package in Debian: Fix Released Bug description: [ Impact ] kernel 6.0 deprecated efivars sysfs interface [1]. For Intel VROC RAID, mdadm needs initramfs to mount efivarfs instead. [1] The commit: commit 0f5b2c69a4cbe4166ca24b76d5ada98ed2867741 Author: Ard Biesheuvel Date: Mon Jun 20 13:34:03 2022 +0200 efi: vars: Remove deprecated 'efivars' sysfs interface [ Test Plan ] 1. Install initramfs-tools 2. update-initramfs -u 3. unmkinitramfs initrd.img-`uname -r` /tmp/extract-initramfs 4. Check if boot script 00_mount_efivarfs exists in directory /tmp/extract-initramfs/main/scripts/init-top/ 5. Check /tmp/extract-initramfs/main/scripts/init-top/ORDER if the boot script 00_mount_efivarfs will be execute before udev. [ Where problems could occur ] Not sure if there any other tools/utilities also need to mount efivarfs as early as mdadm but the probability of file conflict should be very low. Also, there are no impact mounting efivarfs multiple times. mount: /sys/firmware/efi/efivars: efivarfs already mounted on /sys/firmware/efi/efivars. [ Scope ] Jammy, Kinetic [ Other Info ] The private bug link https://bugs.launchpad.net/somerville/+bug/1990231 debian MR: https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/66 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1994936/+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 2012599] Re: tzdata 2023a/2023b/2023c release - Egypt restoring DST
Thanks for the detailed response. I stripped down the SRU to the absolute minimum (backport all test cases and fix the issues found by the test cases). Building timezones that differ pre-1970 (LP: #2003797) will be deferred to a subsequent separate SRU. Generating debconf templates with Python instead of bash has some consistency checks included. I will probably have to write test cases to have those consistency checks in the stable releases. Attached SRU debdiff for kinetic and force pushed the changes to https://code.launchpad.net/~ubuntu-core- dev/ubuntu/+source/tzdata/+git/tzdata/+ref/ubuntu/kinetic ** Patch added: "tzdata_2023c-0ubuntu0.22.10.0.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+attachment/5659119/+files/tzdata_2023c-0ubuntu0.22.10.0.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2012599 Title: tzdata 2023a/2023b/2023c release - Egypt restoring DST Status in tzdata package in Ubuntu: Fix Committed Status in tzdata source package in Bionic: Triaged Status in tzdata source package in Focal: Triaged Status in tzdata source package in Jammy: Triaged Status in tzdata source package in Kinetic: Triaged Status in tzdata source package in Lunar: Fix Committed Bug description: [ Impact ] Recently the Egyptian authorities decided to restore DST. The first switch after the change is expected to take place on last Friday of April. The upstream tzdata 2023a release already reflects this change. The 2023a release contains the following changes: * Egypt now uses DST again, from April through October. * This year Morocco springs forward April 23, not April 30. * Palestine delays the start of DST this year. * Much of Greenland still uses DST from 2024 on. The 2023c release reverts the changes done in 2023b. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2023a * python: test_2023c * python: test_systemv_timezones (for releases <= 20.04 LTS) * python-icu: test_2023a (only for kinetic, jammy, focal) So the test plan is to check that the autopkgtest succeeds. Alternatively the python test_2023a can be run manually: * Set system timezone to Egypt (e.g. Africa/Cairo). * Set system time to 2023-04-27 23:59. * Wait and observe what happens at 2023-04-28 0:00 [Test Case for releases <= 20.04 LTS] Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. This is done by the test_systemv_timezones test case or can be checked manually with the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) [ Where problems could occur ] * Systems with incorrect timezone set (e.g. located outside of Egypt but still using Egyptian time) may observe unexpected time shift. [ Other Info ] The autopkgtest for chrony is flaky on jammy and kinetic (see bug #2002910). * More information with sources: https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023. The SRUs to the stable releases include the recent changes for generating the debconf template (switching from shell code to Python) and the timezone mappings in convert_timezone(). This is done to ease future tzdata updates since those parts of the packaging need to be updated when timezone are added, renamed, or removed. Having the same code in that part makes backporting the changes easier. I added a consistency check to generate_debconf_templates in 2023c-2 which I want to backport in a future SRU. Previous SRUs did sometimes forget to update convert_timezone or the exclusion list for the debconf template for the changes from upstream. All added tests (for testing the debconf template and convert_timezone) were also backported to catch missing those changes. The sorting change of the debconf template was included in the SRU to allow taking the debconf translations from later releases. debian/test_timezone_conversions finds following issues in the kinetic packaging 2022g-0ubuntu0.22.10.1: ``` ERROR: Following 14 timezones can be selected, but will be converted: Asia/Rangoon Europe/Uzhgorod Europe/Zaporozhye US/Alaska US/Aleutian US/Arizona US/Central US/Eastern US/Hawaii US/Indiana-Starke US/Michigan US/Mountain US/Pacific US/Samoa ERROR: Following 5 timezones cannot be selected, but are not converted: America/Fort_Wayne America/Indianapolis America/Knox_IN America/Louisville Pacific/Enderbury ERROR: Following 3 timezones are conversion targets, but are not available: Asia/Riyadh87 Asia/Riyadh88 Asia/Riyadh89 ERROR: Following 4 timezones are conversion
[Touch-packages] [Bug 2012563] Re: unsupported mount options: 'nofail', 'nostrictatime', 'lazytime', and 'nolazytime'
The bitflags for the other mount options are defined in `include/uapi/linux/mount.h` of the Linux source tree, and there is no such definitions for 'nofail', so I don't think adding kernel mappings of this form (e.g. MS_RDONLY) is the solution. These options are supported by 'mount' using userspace option mappings of the form MNT_MS_NOFAIL (see: https://github.com/util-linux/util- linux/blob/master/libmount/src/optmap.c). Perhaps a similar approach could be used by apparmor to validate fs-independent userspace mount options such as nofail? Note, however, that the 'lazytime' option does have a kernel option mapping: `#define MS_LAZYTIME (1<<25)` (in `include/uapi/linux/mount.h`). There is no option mapping for (1<<25) in `parser/mount.h`. Was this option deliberately excluded, or can it be added? If it can be added, then 'nolazytime' is simply a matter of clearing the 'lazytime' bit. There already exists a mapping for 'strictatime', so it should be simple enough for me to add a mapping for `nostrictatime` which sets 0 and clears MS_STRICTATIME. -- 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/2012563 Title: unsupported mount options: 'nofail', 'nostrictatime', 'lazytime', and 'nolazytime' Status in apparmor package in Ubuntu: New Bug description: The following mount options are unsupported: 'nofail', 'nostrictatime', 'lazytime', and 'nolazytime'. Other mount options have mappings from options to bitflags in `parser/mount.cc`, and the bitflags themselves are defined in `parser/mount.h`. Should the aforementioned mount options be included as well, or is there a reason why they are excluded? snapd currently assumes that they are supported, resulting in an error from the apparmor parser when a snap is connected with those options. I'd be happy to file a PR to add these mappings if I knew what the new bitflags should be defined as, and if/how they should be used elsewhere. For completeness: 1) This is a question/bug regarding the source code from the 'ubuntu/devel' branch (and presumably other branches), not a particular release. 2) Same as 1). 3) I expected the apparmor parser to recognize the 'nofail', 'nostrictatime', 'laztime', and 'nolazytime' mount options. 4) The apparmor parser threw an error with message "unsupported mount options" (from within `parser/mount.cc`). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2012563/+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 1848587] Re: lxc 3.0.4-0ubuntu1 ADT test failure with linux 5.4.0-1.2
Is bionic-proposed sufficient (ie. block-proposed-bionic then) or do you specifically need it in bionic-updates? -- 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/1848587 Title: lxc 3.0.4-0ubuntu1 ADT test failure with linux 5.4.0-1.2 Status in lxc package in Ubuntu: Fix Released Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/amd64/l/lxc/20191016_150939_0f81d@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/arm64/l/lxc/20191016_152027_0f81d@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/ppc64el/l/lxc/20191016_150251_0f81d@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/s390x/l/lxc/20191016_150201_0f81d@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1848587/+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 1988270] Re: AppArmor fails to start with Yoga UCA libvirt profile on Focal
** Changed in: cloud-archive/yoga Status: Confirmed => 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/1988270 Title: AppArmor fails to start with Yoga UCA libvirt profile on Focal Status in Ubuntu Cloud Archive: Confirmed Status in Ubuntu Cloud Archive antelope series: Confirmed Status in Ubuntu Cloud Archive yoga series: Fix Released Status in Ubuntu Cloud Archive zed series: Confirmed Status in apparmor package in Ubuntu: Invalid Status in apparmor source package in Focal: Confirmed Status in apparmor source package in Jammy: Confirmed Bug description: [ Impact ] AppArmor fails to start with yoga-focal uca libvirt profile [ Test Plan ] generate yoga-focal openstack instance juju ssh nova-compute/0 sudo systemctl restart apparmor journalctl -xe # Error message ct 04 15:55:32 juju-6d4862-apparmorbug-9 apparmor.systemd[94081]: AppArmor parser error for /etc/apparmor.d/usr.sbin.libvirtd in /etc/apparmor.d/usr.sbin.li> Oct 04 15:55:32 juju-6d4862-apparmorbug-9 apparmor.systemd[94082]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Oct 04 15:55:32 juju-6d4862-apparmorbug-9 audit[94084]: AVC apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="u> Oct 04 15:55:32 juju-6d4862-apparmorbug-9 apparmor.systemd[94005]: Error: At least one profile failed to load [ Other Notes ] On a fully patched Ubuntu Focal with Yoga UCA enabled, after installation of libvirt-daemon-system, restarting apparmor would fail with error: Aug 31 07:40:52 ubuntu2004.localdomain apparmor.systemd[6335]: Restarting AppArmor Aug 31 07:40:52 ubuntu2004.localdomain apparmor.systemd[6335]: Reloading AppArmor profiles Aug 31 07:40:52 ubuntu2004.localdomain apparmor.systemd[6341]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Aug 31 07:40:52 ubuntu2004.localdomain apparmor.systemd[6348]: AppArmor parser error for /etc/apparmor.d in /etc/apparmor.d/usr.sbin.libvirtd at line 29: Invalid capability bpf. Aug 31 07:40:52 ubuntu2004.localdomain apparmor.systemd[6413]: AppArmor parser error for /etc/apparmor.d/usr.sbin.libvirtd in /etc/apparmor.d/usr.sbin.libvirtd at line 29: Invalid capability bpf. Aug 31 07:40:52 ubuntu2004.localdomain apparmor.systemd[6418]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Aug 31 07:40:52 ubuntu2004.localdomain apparmor.systemd[6335]: Error: At least one profile failed to load Aug 31 07:40:52 ubuntu2004.localdomain systemd[1]: apparmor.service: Main process exited, code=exited, status=1/FAILURE Aug 31 07:40:52 ubuntu2004.localdomain systemd[1]: apparmor.service: Failed with result 'exit-code'. Aug 31 07:40:52 ubuntu2004.localdomain systemd[1]: Failed to start Load AppArmor profiles. In addition to bpf, perfmon capability, which is also enabled in /etc/apparmor.d/usr.sbin.libvirtd profile, would lead to the same error. System information: root@ubuntu2004:~# uname -a Linux ubuntu2004.localdomain 5.4.0-125-generic #141-Ubuntu SMP Wed Aug 10 13:42:03 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux root@ubuntu2004:~# dpkg -l libvirt\* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--= ii libvirt-clients8.0.0-1ubuntu7.1~cloud0 amd64 Programs for the libvirt library ii libvirt-daemon 8.0.0-1ubuntu7.1~cloud0 amd64 Virtualization daemon ii libvirt-daemon-config-network 8.0.0-1ubuntu7.1~cloud0 all Libvirt daemon configuration files (default network) ii libvirt-daemon-config-nwfilter 8.0.0-1ubuntu7.1~cloud0 all Libvirt daemon configuration files (default network filters) un libvirt-daemon-driver-lxc (no description available) ii libvirt-daemon-driver-qemu 8.0.0-1ubuntu7.1~cloud0 amd64 Virtualization daemon QEMU connection driver un libvirt-daemon-driver-storage-gluster (no description available) un libvirt-daemon-driver-storage-iscsi-direct (no description available) un libvirt-daemon-driver-storage-rbd (no description available) un libvirt-daemon-driver-storage-zfs (no description available) un libvirt-daemon-driver-vbox (no
[Touch-packages] [Bug 1895486] Re: [media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll Lock" keyboards
About the fix for this bug: This fix solves the problem only for ABNT2 keyboards (used in Brazil, only). But this bug affects all keyboards with "Scroll Lock" key. The solution proposed in the merge request that I made in project xkeyboard-config is not a suitable solution yet. It is not a definitive solution for this problem. It was just a workaround. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1895486 Title: [media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll Lock" keyboards Status in GNOME Shell: New Status in xkeyboard-config package in Ubuntu: Fix Released Bug description: I use Ubuntu 20.04.1. After some use, I noticed a delay when using keyboard media controls (for example: increase volume audio). The first time I push these key Gnome hangs for a short time before display the action on the screen. (This problem is still happening in Ubuntu 18.04 too. Even worse some times, the system crashes when using media keys.) For some reason, my Gnome freezes when using Fn keys, or when I try to use two keyboards. A friend of mine pointed to me that it occurs when switching to a keyboard layout that has Scroll Lock enabled, so I disabled it in the X11 keyboard layout file for my language, and it solved the problem. A workaround to solve the problem is: 1) Opened the keyboard layout file for my language, in my case: sudo nano /usr/share/X11/xkb/symbols/br 2) Commented the line: modifier_map Mod3 { Scroll_Lock }; 3) Logged out and logged in again or run command setxkbmap. These steps are specific for the Brazilian Portuguese ABNT2 Layout and may not work for other layouts, but it can help you find a similar solution. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: x11-xkb-utils 7.7+5 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .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 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Sep 13 21:52:03 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Subsystem: Dell UHD Graphics 630 (Desktop) [1028:0859] NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP107 [GeForce GTX 1050 Ti] [1028:3512] InstallationDate: Installed on 2020-08-15 (29 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) MachineType: Dell Inc. XPS 8930 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=706721d5-f527-41fe-98ca-96706a36bb42 ro quiet splash SourcePackage: x11-xkb-utils UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.15 dmi.board.name: 0T88YD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.15:bd07/01/2020:svnDellInc.:pnXPS8930:pvr1.1.15:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified: dmi.product.family: XPS dmi.product.name: XPS 8930 dmi.product.sku: 0859 dmi.product.version: 1.1.15 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.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:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1895486/+subscriptions -- Mailing
[Touch-packages] [Bug 2013080] Re: On rpi desktop images, grow root leaving slack for LUKS
** Also affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu) Milestone: None => ubuntu-23.04 ** Changed in: livecd-rootfs (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2013080 Title: On rpi desktop images, grow root leaving slack for LUKS Status in livecd-rootfs package in Ubuntu: New Status in ubuntu-settings package in Ubuntu: New Bug description: To aid in user-implemented FDE we wish to leave 16MB of the file- system unexpanded during first boot. The growth of the partition is unaffected, but rather than relying on systemd's growfs facility in fstab, we should use a service that runs a simple script to handle calculating the resize in early boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2013080/+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 2000817] Re: Wrong SHA256-value computed on kinetic
And also without the updated packages. It's a bit random. When exim4 is failing, it stays failing. Restart it, and it might or might not be in failing mode. Sometimes it works, and keeps working. It's not related to the openldap update. I think the migration-reference/0 run that succeeded was a fluke. -- 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/2000817 Title: Wrong SHA256-value computed on kinetic Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Jammy: In Progress Status in openldap source package in Kinetic: Fix Committed Status in openldap source package in Lunar: Fix Released Status in openldap package in Debian: Fix Released Bug description: [ Impact ] OpenLDAP deployments using the contrib pw-sha2 module are not able to authenticate their users because the SHA2 calculation is done incorrectly. Even though this is a contrib module, from an upstream PoV, it is shipped in the Ubuntu (and Debian) OpenLDAP packages, and available for use. Some fix possibilities were discussed in comment #5, and we selected the one with the least impact to OpenLDAP users at large, which is to recompile that module only without the strict-aliasing optimization. This update makes that change, and also includes a DEP8 change to verify it. We didn't use a patch for the pw-sha2 Makefile because d/rules overrides the OPT variable in the make command line (https://git.launchpad.net/~ahasenack/ubuntu/+source/openldap/tree/debian/rules?h=lunar- slapd-sha2-2000817#n44) [ Test Plan ] # Install slapd and openssl $ sudo apt install slapd openssl # Run the following script #!/bin/bash reference_hash="{SHA256}$(echo -n secret | openssl dgst -sha256 -binary | openssl enc -base64)" test_hash=$(slappasswd -s secret -h '{SHA256}' -o module-load=pw-sha2) echo "Reference hash of \"secret\" (openssl): ${reference_hash}" echo "slapd's pw-sha2 hash: ${test_hash}" if [ "${reference_hash}" != "${test_hash}" ]; then echo "ERROR: hashes differ" exit 1 else echo "PASS: hashes are identical" fi With the affected openldap package installed, the script should print an error. With the packages from proposed, the hashes should be identical. [ Where problems could occur ] The fix is a change of a compiler option strictly when building only the pw-sha2 module, so it's very localized. It could affect the performance of this module (for the worse), but it's already not working correctly. [ Other Info ] Not at this time. [Original Description] The OpenLDAP-contrib module sha2 (located in contrib/slapd- modules/passwd/sha2/) computes a wrong SHA256/SSHA256-hash on Ubuntu kinetic. This breaks our current password-authentication in ldap. The problematic computation: $ slappasswd -s secret -h '{SHA256}' -o module-load=pw-sha2 {SHA256}WIrrpN3OjEVOUf6yrH1j+o+ODuUuNBo979Od4UXnu54= The (correct) reference-value on the same system (or older ubuntu Versions): $ echo -n "secret" | openssl dgst -sha256 -binary | openssl enc -base64 K7gNU3sdo+OL0wNhqoVWhr3g6s1xYv72ol/pe/Unols= We nailed the problem down to a bug in the gcc-optimizer for strict- aliasing. so most probably the gcc-version on kinetic (v12.2.0) is the reason. The workaround is to compile the sha2-Module with the flag "-fno-strict-aliasing". Then the correct value is computed. An example taken from a git-compiled version of OpenLDAP 2.5.13: $ ./servers/slapd/slappasswd -T passwd -s secret -h '{SHA256}' -o module-load=pw-sha2 -o module-path=contrib/slapd-modules/passwd/sha2/.libs {SHA256}K7gNU3sdo+OL0wNhqoVWhr3g6s1xYv72ol/pe/Unols= Ubuntu: Description:Ubuntu 22.10 Release:22.10 OpenLDAP-Package: 2.5.13+dfsg-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2000817/+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 2012599] Re: tzdata 2023a/2023b/2023c release - Egypt restoring DST
Summary: there are too many apparently SRU-inappropriate changes bundled into this upload; please remove them and supply the minimal necessary changes only. Full review: This bug has had some unavoidable churn in -proposed due to external factors resulting in multiple releases of tzdata upstream in quick succession. This type of thing usually increases the risk of error in my experience, so I gave this a more thorough SRU review than usual from the perspective of the changes that would be experienced by users. Specifically this is the diff to this upload all the way from what is currently in the -updates pockets. The pulling in of the actual upstreams (tzdata and icu-data) look fine, assuming that it's OK for the icu-data version to mismatch tzdata as the newest icu-data wasn't available at the time of upload. I haven't checked the updates to *.pot and *.po but I assume that they are also fine. The addition and improvement of automated tests are always OK and very welcome. However, some remaining changes I'm not sure about. These weren't documented in the SRU paperwork, though we (bdrung and I) did discuss them extensively in #ubuntu-release - thank you for explaining them. However I'm still not sure if these changes are appropriate for an SRU. Generating debconf templates with Python instead of bash seems like a reasonable improvement, but I'd expect this to be done in the development release only. SRU policy says: > ...the requirements for stable updates are not necessarily the same as those in the development release. When preparing future releases, one of our goals is to construct the most elegant and maintainable system possible, and this often involves fundamental improvements to the system's architecture, rearranging packages to avoid bundled copies of other software so that we only have to maintain it in one place, and so on. However, once we have completed a release, the priority is normally to minimise risk caused by changes not explicitly required to fix qualifying bugs, and this tends to be well-correlated with minimising the size of those changes. As such, the same bug may need to be fixed in different ways in stable and development releases. I'd therefore not expect this change to be present in the SRU, but instead for the existing mechanism to be used. If the existing mechanism is broken or not practical in some way, then I think this needs a separate SRU bug with a full justification of the reasons so that regression risk can be considered, and a QA plan can be agreed. I appreciate that you added a dep8 test, but it isn't clear to me that the dep8 test covers *all* the previous behaviour. That discussion should happen in that bug. There are also multiple and extensive changes and refactorings to debian/tzdata.config. Some of these are unnecessary (reordering and normalising of shell syntax) and these mask the remaining changes, making the rest harder to review. Looking past those, there are some additional indirections, but also the removal of at least one indirection (upstream source at [1]) that we discussed. There's also the new use of convert_timezone. If these changes are necessary then they should be covered by separate bugs with their own individual SRU justifications. I've tried to cover what would be needed if you feel you *must* push these additional changes in an SRU. But please also consider that this consumes a great deal of SRU reviewers' time (which is currently in short supply), and the answer may still be no. I strongly suggest that you simply stop trying to push extensive changes in SRUs except where there's actually a significant and direct benefit to users to do so. I think it'll probably be fine to just update upstream, icu-data and update the templates with the existing bash generator only? This would then be much easier to review and land safely. Note that I've not actually found anything wrong with your changes here. But it's not enough for the upload to merely be correct. It's also necessary to demonstrate to others why and how it is correct, as well as why and how choices have been made such that the risk of an inadvertent oversight has been minimised. This aspect is currently mostly missing, resulting in a significant review burden on others. This apsect should be taken into consideration when deciding whether to seek an SRU backport of something or not. [1] https://git.launchpad.net/~ubuntu-core- dev/ubuntu/+source/tzdata/commit/?id=4c2b898ef99c134a9d202405643136d4b0d38048 ** Changed in: tzdata (Ubuntu Bionic) Status: Fix Committed => Triaged ** Changed in: tzdata (Ubuntu Focal) Status: Fix Committed => Triaged ** Changed in: tzdata (Ubuntu Jammy) Status: Fix Committed => Triaged ** Changed in: tzdata (Ubuntu Kinetic) Status: Fix Committed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu.
[Touch-packages] [Bug 1353792] Re: Detect renamed files and handle by renaming instead of delete/re-send
** Bug watch added: Samba Bugzilla #2294 https://bugzilla.samba.org/show_bug.cgi?id=2294 ** Also affects: rsync via https://bugzilla.samba.org/show_bug.cgi?id=2294 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1353792 Title: Detect renamed files and handle by renaming instead of delete/re-send Status in rsync: Unknown Status in rsync package in Ubuntu: Confirmed Bug description: There has been a report in rsync[0] about this issue since 2005, some patches has been developed detect-renamed[1] and detect-renamed-lax[2] to target the issue, I think it would be great if Ubuntu could patch itself rsync to provide such feature. I've updated those[3] patches[4] to apply to the latest rsync package (3.1.1) and they're working great in my own setup, I also put them in a ppa[5] for further testing. The patches aren't intrusive, they provide some extra flags (--detect-renamed, --detec-moved and --detect-renamed-lax) so I think it shouldn't be disastrous for those who won't use the extra features. [0] https://bugzilla.samba.org/show_bug.cgi?id=2294 [1] https://bugzilla.samba.org/attachment.cgi?id=7435 [2] http://gitweb.samba.org/?p=rsync-patches.git;a=blob;f=detect-renamed-lax.diff;h=4cd23bd4524662f1d0db0bcc90336a77d0bb61c9;hb=HEAD [3] https://github.com/chilicuil/learn/blob/master/patches/rsync-3.1.1-trusty-detect-renamed.diff [4] https://github.com/chilicuil/learn/blob/master/patches/rsync-3.1.1-trusty-detect-renamed-lax.diff [5] https://launchpad.net/~minos-archive/+archive/ubuntu/main/+packages To manage notifications about this bug go to: https://bugs.launchpad.net/rsync/+bug/1353792/+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 1568143] Re: apport-kde crashed with SIGSEGV
This bug is very old, and I am no longer seeing this crash. ** Changed in: apport (Ubuntu) Status: Confirmed => Fix Released -- 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/1568143 Title: apport-kde crashed with SIGSEGV Status in apport package in Ubuntu: Fix Released Bug description: Random crash ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: apport-kde 2.20.1-0ubuntu1 Uname: Linux 4.5.0-040500-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CrashReports: 640:1000:136:9666180:2016-04-08 20:43:09.867370128 +0200:2016-04-08 20:43:10.867370128 +0200:/var/crash/_usr_share_apport_apport-kde.1000.crash CurrentDesktop: KDE Date: Fri Apr 8 20:43:03 2016 ExecutablePath: /usr/share/apport/apport-kde InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-kde systemd ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f666ccc6105:mov(%rax),%rax PC (0x7f666ccc6105) ok source "(%rax)" (0x7575757575757575) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: apport StacktraceTop: () at /usr/lib/python3/dist-packages/PyQt5/QtCore.cpython-35m-x86_64-linux-gnu.so QObject::~QObject() (this=, __in_chrg=) at kernel/qobject.cpp:987 (anonymous namespace)::Q_QGS_qAccessibleCache::Holder::~Holder() (this=0x7f66691ccb40 <(anonymous namespace)::Q_QGS_qAccessibleCache::innerFunction()::holder>, __in_chrg=) at accessible/qaccessiblecache_p.h:60 (anonymous namespace)::Q_QGS_qAccessibleCache::Holder::~Holder() (this=0x7f66691ccb40 <(anonymous namespace)::Q_QGS_qAccessibleCache::innerFunction()::holder>, __in_chrg=) at accessible/qaccessiblecache.cpp:46 __run_exit_handlers (status=1, listp=0x7f6670b925f8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82 Title: apport-kde crashed with SIGSEGV UpgradeStatus: Upgraded to xenial on 2016-03-31 (8 days ago) UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare staff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1568143/+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 1597415] Re: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument
This bug is very old, and I do not see it any longer on a newer Dell laptop and a newer Ubuntu release. ** Changed in: linux (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/1597415 Title: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Won't Fix Bug description: Hi, the symptom is this error message in my system's logs: juin 29 16:56:39 vougeot systemd-udevd[522]: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument According to /proc/bus/input/devices the corresponding input device is: I: Bus=0019 Vendor= Product= Version= N: Name="Dell WMI hotkeys" P: Phys=wmi/input0 S: Sysfs=/devices/virtual/input/input10 U: Uniq= H: Handlers=kbd event9 B: PROP=0 B: EV=13 B: KEY=1000b0400 0 e 0 B: MSC=10 This laptop is a Dell Latitude E6520. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu6 Uname: Linux 4.6.3-040603-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: KDE CustomUdevRuleFiles: 60-ssd-scheduler.rules Date: Wed Jun 29 17:43:01 2016 EcryptfsInUse: Yes MachineType: Dell Inc. Latitude E6520 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to xenial on 2016-04-09 (80 days ago) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0NVF5K dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597415/+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 2013333] [NEW] Quick Settings in the wrong place after Rotation
Public bug reported: I am currently testing the Ubuntu Desktop amd64 in Lunar Beta. - I opened the quick settings in the top right corner (Good) - I rotated the Laptop by ca. 90 deg => This triggered the Desktop Environment to rotate too (Good) - Note: quick settings are still open - I rotated the Laptop back => This triggered the Desktop Environment to rotate back too (Good) - The quick settings are now Horizontally centered (Unexpected) Note: I tested this during the Installation. I attached a screenshot that shows this. - ISO used: https://cdimage.ubuntu.com/daily-live/20230329/lunar-desktop-amd64.iso - ISO hash and signature verified Device: Lenovo ThinkPad Yoga 460 CPU: 64-Bit Intel Core i7-6500U @2.50GHz x 4 RAM: 8GB Graphics: Mesa Intel HD Graphics 520 (SKL GT2) Storage: 256GB SSD ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2023-03-30 11-13-37.png" https://bugs.launchpad.net/bugs/201/+attachment/5659110/+files/Screenshot%20from%202023-03-30%2011-13-37.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/201 Title: Quick Settings in the wrong place after Rotation Status in xorg package in Ubuntu: New Bug description: I am currently testing the Ubuntu Desktop amd64 in Lunar Beta. - I opened the quick settings in the top right corner (Good) - I rotated the Laptop by ca. 90 deg => This triggered the Desktop Environment to rotate too (Good) - Note: quick settings are still open - I rotated the Laptop back => This triggered the Desktop Environment to rotate back too (Good) - The quick settings are now Horizontally centered (Unexpected) Note: I tested this during the Installation. I attached a screenshot that shows this. - ISO used: https://cdimage.ubuntu.com/daily-live/20230329/lunar-desktop-amd64.iso - ISO hash and signature verified Device: Lenovo ThinkPad Yoga 460 CPU: 64-Bit Intel Core i7-6500U @2.50GHz x 4 RAM: 8GB Graphics: Mesa Intel HD Graphics 520 (SKL GT2) Storage: 256GB SSD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/201/+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 1876068] Re: DeprecationWarning: an integer is required
Proposed fix: https://github.com/canonical/apport/pull/151 -- 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/1876068 Title: DeprecationWarning: an integer is required Status in apport package in Ubuntu: Fix Released Bug description: Hi, when I use ubuntu-bug to report a bug, I see the following python deprecation warning: $ ubuntu-bug apport-kde /usr/share/apport/apport-kde:129: DeprecationWarning: an integer is required (got type float). Implicit conversion to integers using __int__ is deprecated, and may be removed in a future version of Python. progress.setValue(value * 1000) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport-kde 2.20.11-0ubuntu27 Uname: Linux 5.6.7-050607-generic x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Apr 30 11:16:12 2020 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/1876068/+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 1876068] Re: DeprecationWarning: an integer is required
This DeprecationWarning warning was fixed by https://github.com/canonical/apport/commit/57c674a6d906a6e66a5c795aa45710cd2844d24d which is part of Apport 2.21.0. While looking at this commit, I noticed that this fix is broken. The float value is between 0 and 1. Converting it to integer before multiplying it results in a progress bar that is always 0% or 100%. -- 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/1876068 Title: DeprecationWarning: an integer is required Status in apport package in Ubuntu: Fix Released Bug description: Hi, when I use ubuntu-bug to report a bug, I see the following python deprecation warning: $ ubuntu-bug apport-kde /usr/share/apport/apport-kde:129: DeprecationWarning: an integer is required (got type float). Implicit conversion to integers using __int__ is deprecated, and may be removed in a future version of Python. progress.setValue(value * 1000) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport-kde 2.20.11-0ubuntu27 Uname: Linux 5.6.7-050607-generic x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Apr 30 11:16:12 2020 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/1876068/+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 1847493] Re: recentmanager crashed with signal 5 in _g_log_abort()
Hi, the recentmanager test seems to run OK, but it generates a crash file: $ /usr/libexec/installed-tests/gtk+/recentmanager TAP version 13 # random seed: R02S11301a509f5dd29b12965d40796527a7 1..8 # Start of recent-manager tests # GLib-GIO-DEBUG: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3) # GLib-GIO-DEBUG: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ?gio-vfs? ok 1 /recent-manager/get-default ok 2 /recent-manager/add ok 3 /recent-manager/add-many ok 4 /recent-manager/has-item ok 5 /recent-manager/move-item ok 6 /recent-manager/lookup-item ok 7 /recent-manager/remove-item ok 8 /recent-manager/purge # End of recent-manager tests $ ls -l /var/crash/ total 1156 -rw-r- 1 bonnaudl whoopsie 1175991 Mar 30 12:10 _usr_libexec_installed-tests_gtk+_recentmanager.1000.crash -rw-r--r-- 1 bonnaudl whoopsie 0 Mar 30 12:10 _usr_libexec_installed-tests_gtk+_recentmanager.1000.upload -rw--- 1 whoopsie whoopsie 37 Mar 30 12:10 _usr_libexec_installed-tests_gtk+_recentmanager.1000.uploaded -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1847493 Title: recentmanager crashed with signal 5 in _g_log_abort() Status in gtk+3.0 package in Ubuntu: New Bug description: recentmanager crashed while I was running gnome-desktop-testing-runner ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gtk-3-examples 3.24.12-1ubuntu1 Uname: Linux 5.3.5-050305-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 9 11:44:28 2019 ExecutablePath: /usr/libexec/installed-tests/gtk+/recentmanager ProcCmdline: /usr/libexec/installed-tests/gtk+/recentmanager --tap Signal: 5 SourcePackage: gtk+3.0 StacktraceTop: _g_log_abort (breakpoint=1) at ../../../glib/gmessages.c:554 g_log_writer_default (log_level=18, log_level@entry=G_LOG_LEVEL_WARNING, fields=fields@entry=0x7ffd694bb840, n_fields=n_fields@entry=6, user_data=user_data@entry=0x0) at ../../../glib/gmessages.c:2694 g_log_structured_array (n_fields=6, fields=0x7ffd694bb840, log_level=G_LOG_LEVEL_WARNING) at ../../../glib/gmessages.c:1925 g_log_structured_array (log_level=G_LOG_LEVEL_WARNING, fields=0x7ffd694bb840, n_fields=6) at ../../../glib/gmessages.c:1898 g_log_structured_standard (log_domain=log_domain@entry=0x7f4c5831c047 "Gtk", log_level=log_level@entry=G_LOG_LEVEL_WARNING, file=file@entry=0x7f4c58379b60 "../../../../gtk/gtkrecentmanager.c", line=, func=, message_format=) at ../../../glib/gmessages.c:1982 Title: recentmanager crashed with signal 5 in _g_log_abort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fuse kvm libvirt libvirt-qemu libvirtd lpadmin plugdev sambashare staff sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1847493/+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 2013324] [NEW] gnome-desktop-testing-runner finds a crash in /usr/libexec/installed-tests/gtk+/scrolledwindow
Public bug reported: Hi, here is the problem: $ gnome-desktop-testing-runner [...] FAIL: gtk+/scrolledwindow.test (Child process killed by signal 6) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gtk-3-examples 3.24.37-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 30 12:05:24 2023 SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2013324 Title: gnome-desktop-testing-runner finds a crash in /usr/libexec/installed- tests/gtk+/scrolledwindow Status in gtk+3.0 package in Ubuntu: New Bug description: Hi, here is the problem: $ gnome-desktop-testing-runner [...] FAIL: gtk+/scrolledwindow.test (Child process killed by signal 6) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gtk-3-examples 3.24.37-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 30 12:05:24 2023 SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2013324/+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 1847493] Re: recentmanager crashed with signal 5 in _g_log_abort()
** Tags removed: eoan groovy hirsute ** Tags added: jammy kinetic lunar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1847493 Title: recentmanager crashed with signal 5 in _g_log_abort() Status in gtk+3.0 package in Ubuntu: New Bug description: recentmanager crashed while I was running gnome-desktop-testing-runner ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gtk-3-examples 3.24.12-1ubuntu1 Uname: Linux 5.3.5-050305-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 9 11:44:28 2019 ExecutablePath: /usr/libexec/installed-tests/gtk+/recentmanager ProcCmdline: /usr/libexec/installed-tests/gtk+/recentmanager --tap Signal: 5 SourcePackage: gtk+3.0 StacktraceTop: _g_log_abort (breakpoint=1) at ../../../glib/gmessages.c:554 g_log_writer_default (log_level=18, log_level@entry=G_LOG_LEVEL_WARNING, fields=fields@entry=0x7ffd694bb840, n_fields=n_fields@entry=6, user_data=user_data@entry=0x0) at ../../../glib/gmessages.c:2694 g_log_structured_array (n_fields=6, fields=0x7ffd694bb840, log_level=G_LOG_LEVEL_WARNING) at ../../../glib/gmessages.c:1925 g_log_structured_array (log_level=G_LOG_LEVEL_WARNING, fields=0x7ffd694bb840, n_fields=6) at ../../../glib/gmessages.c:1898 g_log_structured_standard (log_domain=log_domain@entry=0x7f4c5831c047 "Gtk", log_level=log_level@entry=G_LOG_LEVEL_WARNING, file=file@entry=0x7f4c58379b60 "../../../../gtk/gtkrecentmanager.c", line=, func=, message_format=) at ../../../glib/gmessages.c:1982 Title: recentmanager crashed with signal 5 in _g_log_abort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fuse kvm libvirt libvirt-qemu libvirtd lpadmin plugdev sambashare staff sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1847493/+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 2013320] Re: Gnome terminal drag bug
The dark grey square looks like a small window with a shadow. So I think this might be some application or extension listening for drag-and-drop. Please logout and retest without any other apps running. Please also check to see what extensions are installed: gnome-extensions list that might be causing the issue. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2013320 Title: Gnome terminal drag bug Status in Ubuntu: Incomplete Bug description: Hi Ubuntuers, When I'm using the Gnome default terminal that comes with Ubuntu, the terminal spawns a black square on the left of the screen while dragging the mouse to the corner of the screen. At the same time this square spawn a default gear application icon also spawns in the task/application bar, when i stop dragging the bug disappear. I adjunct a screenshot of the bug. Best rewards, ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 30 10:52:03 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2022-06-21 (282 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: VMware, Inc. VMware Virtual Platform ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=38094230-c44e-432a-863b-9c02503bf5f5 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2013320/+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 1876068] Re: DeprecationWarning: an integer is required
The bug is now fixed. Thanks! ** Changed in: apport (Ubuntu) Status: Confirmed => Fix Released -- 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/1876068 Title: DeprecationWarning: an integer is required Status in apport package in Ubuntu: Fix Released Bug description: Hi, when I use ubuntu-bug to report a bug, I see the following python deprecation warning: $ ubuntu-bug apport-kde /usr/share/apport/apport-kde:129: DeprecationWarning: an integer is required (got type float). Implicit conversion to integers using __int__ is deprecated, and may be removed in a future version of Python. progress.setValue(value * 1000) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport-kde 2.20.11-0ubuntu27 Uname: Linux 5.6.7-050607-generic x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Apr 30 11:16:12 2020 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/1876068/+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 1899749] Re: Please add DCCP to rarely used protocols
** Tags removed: groovy hirsute ** Tags added: jammy kinetic lunar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1899749 Title: Please add DCCP to rarely used protocols Status in kmod package in Ubuntu: New Bug description: Hi, according to this message: https://www.openwall.com/lists/oss-security/2020/10/13/7 the DCCP protocol may be used as an attack vector to the kernel. So could you please add it to /etc/modprobe.d/blacklist-rare- network.conf ? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: kmod 27-1ubuntu2 Uname: Linux 5.8.14-050814-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 14 10:21:37 2020 SourcePackage: kmod UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.modprobe.d.blacklist-rare-network.conf: 2020-10-14T10:21:22.472169 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1899749/+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 2013320] [NEW] Gnome terminal drag bug
Public bug reported: Hi Ubuntuers, When I'm using the Gnome default terminal that comes with Ubuntu, the terminal spawns a black square on the left of the screen while dragging the mouse to the corner of the screen. At the same time this square spawn a default gear application icon also spawns in the task/application bar, when i stop dragging the bug disappear. I adjunct a screenshot of the bug. Best rewards, ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 30 10:52:03 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2022-06-21 (282 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: VMware, Inc. VMware Virtual Platform ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=38094230-c44e-432a-863b-9c02503bf5f5 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9 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 ubuntu wayland-session ** Attachment added: "Screenshot from 2023-03-30 11-06-11.png" https://bugs.launchpad.net/bugs/2013320/+attachment/5659075/+files/Screenshot%20from%202023-03-30%2011-06-11.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2013320 Title: Gnome terminal drag bug Status in xorg package in Ubuntu: New Bug description: Hi Ubuntuers, When I'm using the Gnome default terminal that comes with Ubuntu, the terminal spawns a black square on the left of the screen while dragging the mouse to the corner of the screen. At the same time this square spawn a default gear application icon also spawns in the task/application bar, when i stop dragging the bug disappear. I adjunct a screenshot of the bug. Best rewards, ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 30 10:52:03 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2022-06-21 (282 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: VMware, Inc. VMware Virtual Platform ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=38094230-c44e-432a-863b-9c02503bf5f5 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation
[Touch-packages] [Bug 2013311] [NEW] pulseaudio recommends invalid package
Public bug reported: Installing pulseaudio/focal-updates,now 1:13.99.1-1ubuntu3.13 amd64 recommends packages pavumeter paman paprefs ubuntu-sounds Attempting to install paman gives error: Package paman is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'paman' has no installation candidate cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu-Server 20.04.3 LTS amd64 (Cubic 2022-03-16 07:21)" ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- 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/2013311 Title: pulseaudio recommends invalid package Status in pulseaudio package in Ubuntu: New Bug description: Installing pulseaudio/focal-updates,now 1:13.99.1-1ubuntu3.13 amd64 recommends packages pavumeter paman paprefs ubuntu-sounds Attempting to install paman gives error: Package paman is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'paman' has no installation candidate cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu-Server 20.04.3 LTS amd64 (Cubic 2022-03-16 07:21)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2013311/+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 1966203] Re: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04
** Tags added: lunar -- 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/1966203 Title: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04 Status in snapd: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: Configuration: OS:jammy-live-server20220320-amd64.iso CPU:AMD EPYC 7702 64-Core Processor UEFI Version:D8E119A BMC Version:D8BT19I SSD:Intel 1.60TB NVMe SSD Boot mode:legacy Reproduce Steps: 1.Boot into BIOS and set boot mode to legacy 2.install ubuntu 22.04 on NVMe SSD 3.Check syslog log Current behaviors: syslog shows systemd-udevd errors in Ubuntu 22.04 Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2877]: nvme0n1p3: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p3' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2876]: nvme0n1p2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1p1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2828]: sr0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sr0' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2850]: dm-0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/dm-0' failed with exit code 1. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1966203/+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 2012563] Re: unsupported mount options: 'nofail', 'nostrictatime', 'lazytime', and 'nolazytime'
This also affects "functionfs" that uses "uid=2000,gid=2000,no_disconnect=1,rmode=0550,fmode=0660 ". -- 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/2012563 Title: unsupported mount options: 'nofail', 'nostrictatime', 'lazytime', and 'nolazytime' Status in apparmor package in Ubuntu: New Bug description: The following mount options are unsupported: 'nofail', 'nostrictatime', 'lazytime', and 'nolazytime'. Other mount options have mappings from options to bitflags in `parser/mount.cc`, and the bitflags themselves are defined in `parser/mount.h`. Should the aforementioned mount options be included as well, or is there a reason why they are excluded? snapd currently assumes that they are supported, resulting in an error from the apparmor parser when a snap is connected with those options. I'd be happy to file a PR to add these mappings if I knew what the new bitflags should be defined as, and if/how they should be used elsewhere. For completeness: 1) This is a question/bug regarding the source code from the 'ubuntu/devel' branch (and presumably other branches), not a particular release. 2) Same as 1). 3) I expected the apparmor parser to recognize the 'nofail', 'nostrictatime', 'laztime', and 'nolazytime' mount options. 4) The apparmor parser threw an error with message "unsupported mount options" (from within `parser/mount.cc`). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2012563/+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 1983794] Re: Evolution not deleting autosave files
This bug is biting me multiple times per week. Came here through https://gitlab.gnome.org/GNOME/evolution/-/issues/1972 . Digging through the comments there found that is was solved here, now to find out the package with solution is stuck in the release workflow for two month. Who or what do we need to poke to get this to completion? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcanberra in Ubuntu. https://bugs.launchpad.net/bugs/1983794 Title: Evolution not deleting autosave files Status in Evolution: Fix Released Status in evolution package in Ubuntu: Invalid Status in libcanberra package in Ubuntu: Fix Released Status in libcanberra source package in Jammy: Fix Committed Status in evolution source package in Kinetic: Confirmed Status in libcanberra source package in Kinetic: Fix Committed Bug description: [ Impact ] Autosave files are not removed from evolution local state directories (and windows leaked) [ Test case ] 1. Open evolution, and start to compose a new email 2. Write enough text and wait few minutes so that this command returns a file ls -l ~/.local/share/evolution/.evolution-composer.autosave-* 3. Close the email composer window, hitting "Do not save" 4. ls -l ~/.local/share/evolution/.evolution-composer.autosave-* should list no files 5. Opening and closing again evolution should not ask to restore the previous email [ Regression potential ] No sounds could be performed during some UI actions --- Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1 was installed with the distribution on a new system and received settings imported from an earlier version on another computer. When composing an email, if the process takes long enough an autosave file is created as ~/.local/share/evolution/.evolution- composer.autosave-xx ("xx" is a random 6 character string). When the email is successfully sent, the autosave file SHOULD be deleted. It's not. When evolution is shut down and restarted I'm asked if I want to recover an unfinished email. Answering No to this will delete the autosave file, but otherwise it persists and the recovery query recurs the next time I open evolution. Other people are having the same issue, see https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome people aren't dealing with it, perhaps considering it a distro- specific bug. On a system used by many people this is a potential security issue. To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1983794/+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 1856871] Re: i/o error if next unused loop device is queried
** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium -- 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/1856871 Title: i/o error if next unused loop device is queried Status in linux package in Ubuntu: Fix Released Status in parted package in Ubuntu: Invalid Status in snapd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in udev package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux source package in Jammy: Fix Released Bug description: [Impact] * There's an I/O error on fsync() in a detached loop device if it has been previously attached. The issue is that write cache is enabled in the attach path in loop_configure() but it isn't disabled in the detach path; thus it remains enabled in the block device regardless of whether it is attached or not. * fsync() on detached loop devices can be called by partition tools and commands run by sosreport, so the unexpected kernel error message might surprise users or even distract from the actual issue being investigatedr. It might also trigger alerts in logging/monitoring/alerting stacks [Fix] * Disable write cache in the detach path [Test Plan] * Attach and detach an image to a loop device and test fsync return value aterwards # DEV=/dev/loop7 # IMG=/tmp/image # truncate --size 1M $IMG # losetup $DEV $IMG # losetup -d $DEV Before: # strace -e fsync parted -s $DEV print 2>&1 | grep fsync fsync(3)= -1 EIO (Input/output error) Warning: Error fsyncing/closing /dev/loop7: Input/output error [ 982.529929] blk_update_request: I/O error, dev loop7, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 After: # strace -e fsync parted -s $DEV print 2>&1 | grep fsync fsync(3)= 0 [Where problems could occur] * The detach path for block devices is modified. Worst case scenario would be an error when detaching loop devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856871/+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 2013257] Re: two-finger-zoom not working on Elan touchpad
** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Summary changed: - two-finger-zoom not working on Elan touchpad + Multi-touch gestures don't work in Xorg sessions ** Changed in: mutter (Ubuntu) Status: New => Confirmed ** Tags added: multitouch ** Summary changed: - Multi-touch gestures don't work in Xorg sessions + Multi-touch touchpad gestures don't work in Xorg sessions ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2013257 Title: Multi-touch touchpad gestures don't work in Xorg sessions Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: On my Elan touchpad, using the two finger pinch zoom gesture does not work, neither in Firefox nor in LibreOffice. Other gestures like two- finger-scrolling work fine. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.157 Wed Oct 12 09:19:07 UTC 2022 GCC version: ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 30 04:09:14 2023 DistUpgraded: 2023-03-17 13:44:54,645 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] 3rd Gen Core processor Graphics Controller [1462:10d7] NVIDIA Corporation GK107M [GeForce GTX 660M] [10de:0fd4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK107M [GeForce GTX 660M] [1462:10d7] InstallationDate: Installed on 2023-02-24 (33 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Micro-Star International Co., Ltd. GE60 0NC\0ND ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=c297f9ee-3b13-4ae2-a84f-5197cc9c13d4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-03-17 (12 days ago) dmi.bios.date: 11/08/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16GAIMS.513 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16GA dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16GAIMS.513:bd11/08/2012:br4.6:svnMicro-StarInternationalCo.,Ltd.:pnGE600NC\0ND:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16GA:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GE60 0NC\0ND dmi.product.sku: To be filled by O.E.M. dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.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 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2013257/+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 1895486] Re: [media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll Lock" keyboards
Continued in bug 1892747. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1895486 Title: [media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll Lock" keyboards Status in GNOME Shell: New Status in xkeyboard-config package in Ubuntu: Fix Released Bug description: I use Ubuntu 20.04.1. After some use, I noticed a delay when using keyboard media controls (for example: increase volume audio). The first time I push these key Gnome hangs for a short time before display the action on the screen. (This problem is still happening in Ubuntu 18.04 too. Even worse some times, the system crashes when using media keys.) For some reason, my Gnome freezes when using Fn keys, or when I try to use two keyboards. A friend of mine pointed to me that it occurs when switching to a keyboard layout that has Scroll Lock enabled, so I disabled it in the X11 keyboard layout file for my language, and it solved the problem. A workaround to solve the problem is: 1) Opened the keyboard layout file for my language, in my case: sudo nano /usr/share/X11/xkb/symbols/br 2) Commented the line: modifier_map Mod3 { Scroll_Lock }; 3) Logged out and logged in again or run command setxkbmap. These steps are specific for the Brazilian Portuguese ABNT2 Layout and may not work for other layouts, but it can help you find a similar solution. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: x11-xkb-utils 7.7+5 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .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 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Sep 13 21:52:03 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Subsystem: Dell UHD Graphics 630 (Desktop) [1028:0859] NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP107 [GeForce GTX 1050 Ti] [1028:3512] InstallationDate: Installed on 2020-08-15 (29 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) MachineType: Dell Inc. XPS 8930 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=706721d5-f527-41fe-98ca-96706a36bb42 ro quiet splash SourcePackage: x11-xkb-utils UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.15 dmi.board.name: 0T88YD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.15:bd07/01/2020:svnDellInc.:pnXPS8930:pvr1.1.15:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified: dmi.product.family: XPS dmi.product.name: XPS 8930 dmi.product.sku: 0859 dmi.product.version: 1.1.15 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.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:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1895486/+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 2013255] Re: changing screen brightness with keyboard hotkeys reacts very slow
*** This bug is a duplicate of bug 1892747 *** https://bugs.launchpad.net/bugs/1892747 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1892747, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** This bug has been marked a duplicate of bug 1892747 GNOME hangs while changing display brightness from keyboard shortcut -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2013255 Title: changing screen brightness with keyboard hotkeys reacts very slow Status in gnome-shell package in Ubuntu: Confirmed Bug description: Using "Fn" key + brightness up/down (arrow up/down) keys reacts very delayed (up to 2 seconds) and system freezes enirely during these brightness-changes being applied by the system. It however works flawless in the brightness slider menu in the top right. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.157 Wed Oct 12 09:19:07 UTC 2022 GCC version: ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 30 03:38:51 2023 DistUpgraded: 2023-03-17 13:44:54,645 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] 3rd Gen Core processor Graphics Controller [1462:10d7] NVIDIA Corporation GK107M [GeForce GTX 660M] [10de:0fd4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK107M [GeForce GTX 660M] [1462:10d7] InstallationDate: Installed on 2023-02-24 (33 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Micro-Star International Co., Ltd. GE60 0NC\0ND ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=c297f9ee-3b13-4ae2-a84f-5197cc9c13d4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-03-17 (12 days ago) dmi.bios.date: 11/08/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16GAIMS.513 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16GA dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16GAIMS.513:bd11/08/2012:br4.6:svnMicro-StarInternationalCo.,Ltd.:pnGE600NC\0ND:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16GA:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GE60 0NC\0ND dmi.product.sku: To be filled by O.E.M. dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.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 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 To manage notifications about this bug go to:
[Touch-packages] [Bug 2013128] Re: [feature request] Upgrade libglx-mesa0
would've been best to just add the info from the question instead, as your request didn't even contain the link to the fix ** Description changed: + I have a bug that occurs in Ubuntu 22.04's most up to date libmesa + related packages (=22.2.5-0ubuntu0.1~22.04.1) that was not there in + =22.0.1-1ubuntu2. It has since been solved in mesa's repo and pulled + into debian's repo. I do not know the proper way to request an updated + version be made for Ubuntu. I've manually installed many different + versions of libmesa to test on my own that it was working in an older + version, is broken in this update, and was fixed again in 22.3.4 and + 22.3.5. + + The one-line fix is implemented here in libmesa's repo: + https://gitlab.freedesktop.org/mesa/mesa/-/commit/7e68cf91d74e6bd9a88c2b52417451d9afec4782/pipelines + + -- + Feature Request: Upgrade mesa libraries to apply upstream bugfix to a bug introduced in 22.2.5-0ubuntu0.1~22.04.1. I was directed to report this bug via my question at answers.launchpad.net/ubuntu: https://answers.launchpad.net/ubuntu/+question/705988 Please let me know if you need further information. Thanks! - - > lsb_release -rd + > lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 - > apt-cache policy libglx-mesa0 + > apt-cache policy libglx-mesa0 libglx-mesa0: - Installed: 22.2.5-0ubuntu0.1~22.04.1 - Candidate: 22.2.5-0ubuntu0.1~22.04.1 - Version table: - *** 22.2.5-0ubuntu0.1~22.04.1 500 - 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages - 100 /var/lib/dpkg/status - 22.0.1-1ubuntu2 500 - 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages + Installed: 22.2.5-0ubuntu0.1~22.04.1 + Candidate: 22.2.5-0ubuntu0.1~22.04.1 + Version table: + *** 22.2.5-0ubuntu0.1~22.04.1 500 + 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages + 100 /var/lib/dpkg/status + 22.0.1-1ubuntu2 500 + 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libglx-mesa0 22.2.5-0ubuntu0.1~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: i3 Date: Tue Mar 28 15:30:59 2023 InstallationDate: Installed on 2022-04-28 (334 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2022-04-29T14:47:14.568862 ** Also affects: mesa (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Status: New => Fix Released ** Also affects: mesa (Ubuntu Kinetic) Importance: Undecided Status: New -- 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/2013128 Title: [feature request] Upgrade libglx-mesa0 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: New Status in mesa source package in Kinetic: New Bug description: I have a bug that occurs in Ubuntu 22.04's most up to date libmesa related packages (=22.2.5-0ubuntu0.1~22.04.1) that was not there in =22.0.1-1ubuntu2. It has since been solved in mesa's repo and pulled into debian's repo. I do not know the proper way to request an updated version be made for Ubuntu. I've manually installed many different versions of libmesa to test on my own that it was working in an older version, is broken in this update, and was fixed again in 22.3.4 and 22.3.5. The one-line fix is implemented here in libmesa's repo: https://gitlab.freedesktop.org/mesa/mesa/-/commit/7e68cf91d74e6bd9a88c2b52417451d9afec4782/pipelines -- Feature Request: Upgrade mesa libraries to apply upstream bugfix to a bug introduced in 22.2.5-0ubuntu0.1~22.04.1. I was directed to report this bug via my question at answers.launchpad.net/ubuntu: https://answers.launchpad.net/ubuntu/+question/705988 Please let me know if you need further information. Thanks! > lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 > apt-cache policy libglx-mesa0 libglx-mesa0: Installed: 22.2.5-0ubuntu0.1~22.04.1 Candidate: 22.2.5-0ubuntu0.1~22.04.1 Version table: ***