[Touch-packages] [Bug 1916931] Re: omshell returns inconsistent results or segfaults
> Bill, Lukas asked a question in comment #10 and set the bug to 'incomplete', > hoping > to get feedback from someone who could reproduce the problem. If you can > provide an > answer, please do set the bug back to 'confirmed' when answering. I don't agree with Lukas' action. The bug is still valid for Jammy, the LTS version. If Lukas wants to provide a package to test on Jammy I can do that, but setting up a DHCP peer environment in a version of Ubuntu that I don't have a build environment for will take quite a bit of effort. It is particularly onerous because I only use LTS versions of Ubuntu, so even if the Kinetic works it doesn't solve my problem for another 2 years. > Could somebody confirm if this issue is still happening with omshell v4.4.3 > from > the Ubuntu Kinetic package? I suppose there is an alternative. I'll see if I can backport the 4.4.3 version from Kinetic to Jammy. I can confirm that the bug exists in 4.4.1 on Debian 11, Bullseye. Bill -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1916931 Title: omshell returns inconsistent results or segfaults Status in isc-dhcp package in Ubuntu: Expired Bug description: I have just built a Ubuntu 20.04 server and installed isc-dhcp-server 4.4.1 on it and I am seeing inconsistent returns from omshell. Initially omshell returns data as expected, but when I exit and re-enter omshell connections fail. Here is the initial, working, session: # omshell > server localhost > port 7911 > key omapi_key > connect obj: > new failover-state obj: failover-state > set name = "dhcp-failover" obj: failover-state name = "dhcp-failover" > open obj: failover-state name = "dhcp-failover" partner-address = c0:9d:e9:76:e9:55:00:00 partner-port = 00:00:02:07 local-address = 10:9d:e9:76:e9:55:00:00 local-port = 00:00:02:07 max-outstanding-updates = 00:00:00:0a mclt = 00:00:01:2c load-balance-max-secs = 00:00:00:03 load-balance-hba = ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 partner-state = 00:00:00:02 local-state = 00:00:00:02 partner-stos = 60:36:d0:68 local-stos = 60:36:8b:3b hierarchy = 00:00:00:01 last-packet-sent = 00:00:00:00 last-timestamp-received = 00:00:00:00 skew = 00:00:00:00 max-response-delay = 00:00:00:3c cur-unacked-updates = 00:00:00:00 Here is what I see when the connect fails. Well, just hangs really. # omshell > server localhost > port 7911 > key omapi_key > connect And then I hit ctrl-c to break out and tried again: # omshell > server localhost > port 7911 > key omapi_key > connect Segmentation fault (core dumped) Note, the peer to this server is still running Ubuntu 18.04 with isc-dhcp-server 4.3.5. Running the exact same commands on the peer works reliably. (They are using the same python script to drive omshell.) The DHCP server on the new system appears to be working just fine as reported by omshell on the peer and systemctl. I was curious if the problem could be with the mis-matched versions of isc-dhcp-server so I shutdown isc-dhcp-server on the 18.04 system and get the same results. I also tried using a python script with the pypureomapi module to try and determine if the problem was in omshell or the server. I got very similar results when I attempted to get information about the failover state of the server. Interestingly interrogating the server about host information seems to work just fine. This is a critical bug since I don't see how to fail over a DHCP that is running the isc-dhcp-server on 20.04 without being able to issue omapi commands. I am attaching apport output to this bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1916931/+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 1998765] Re: libnl3 3.4.0 doesn't work with WCN3980
I installed the updated version on the platform which needs this patch. After updating the packages, the platform can scan and connect to a WiFi network correctly. I also tried other amd64, armhf and arm64 platforms which don't require the patch originally and their wifi device still work after upgrading. $ dpkg -l |grep libnl ii libnl-3-200:armhf 3.4.0-1ubuntu0.1 armhf library for dealing with netlink sockets ii libnl-genl-3-200:armhf 3.4.0-1ubuntu0.1 armhf library for dealing with netlink sockets - generic netlink ii libnl-route-3-200:armhf3.4.0-1ubuntu0.1 armhf library for dealing with netlink sockets - route interface $ sudo netplan apply $ ip a ... 3: wlan0: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether dc:a6:32:37:fa:a7 brd ff:ff:ff:ff:ff:ff inet 10.102.138.56/22 brd 10.102.139.255 scope global dynamic wlan0 valid_lft 600sec preferred_lft 600sec inet6 fe80::dea6:32ff:fe37:faa7/64 scope link valid_lft forever preferred_lft forever $ sudo ping -I wlan0 8.8.8.8 PING 8.8.8.8 (8.8.8.8) from 10.102.138.56 wlan0: 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=57 time=10.4 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=57 time=5.64 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=57 time=5.73 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=57 time=6.09 ms 64 bytes from 8.8.8.8: icmp_seq=5 ttl=57 time=6.98 ms ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal ** Changed in: oem-priority/focal Status: New => Fix Committed ** Changed in: oem-priority/focal Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1998765 Title: libnl3 3.4.0 doesn't work with WCN3980 Status in OEM Priority Project: Fix Committed Status in OEM Priority Project focal series: Fix Committed Status in libnl3 package in Ubuntu: Fix Released Status in libnl3 source package in Focal: Fix Committed Status in libnl3 source package in Jammy: Invalid Bug description: [ Impact ] When testing Qualcomm qcs410 with WCN3980 with 20.04 and UC20, WCN3980 is not able connect to an AP. However, with the libnl3 (3.5.0) from BSP, WCN3980 can work correctly. After bisecting the commits from 3.4.0 to 3.5.0, this commit[1] is identified as the root cause. According to the commit, the "NLA_F_NESTED" flag should be set for kernel later than 5.2. [ Test Plan ] Verify with the updated version, the WIFI module can: 1. scan WIFI networks 2. connect to an available network 3. access to the connected network [ Where problems could occur ] 1. kernel versions without NLA_F_NESTED flag defined This flag is introduced before Linux kernel v5 (checked v3.x and v4.x have it). It would not be a problem for an older kernel to understand/work with this change. Since the GA kernel is 5.4, so a generic image would still work. 2. Drivers don't use the NESTED flag. According to hui.wang's input, this change should not affect drivers which don't use the NESTED flag. But, it'd be better to cover more Wifi modules. [ Other Info ] 22.04 is using libnl3 3.0.5-0.1, so only 20.04 needs this patch. [1] https://github.com/thom311/libnl/commit/7de65a051fb37ece16f896a7385073274b77a133 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998765/+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 2003140] Re: Ubuntu laptop can't use external monitors
Thanks for the bug report. The Nvidia Xorg driver doesn't appear to be loading for some reason, which is the main problem. Although the Nvidia kernel driver is loaded. You are using Nvidia driver version 470.161.03 but their website suggests the current supported version for your Quadro P620 is 525.78.01. But regardless of version, it looks like the issue here is a failed installation of the Xorg driver. And the bug reporting system is suggesting you might have tried a manual driver installation in the past too. To fix this, please open the 'Additional Drivers' app and use it to install a newer Nvidia driver. Please do not attempt to install drivers manually without using the Additional Drivers app because doing so can lead to bugs like this one. ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-470 (Ubuntu) ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: New => Incomplete ** Tags added: multimonitor nvidia -- 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/2003140 Title: Ubuntu laptop can't use external monitors Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Bug description: # What happens (Steps to reproduce): 1. Install a clean version of Ubuntu onto a laptop: Hardware="https://www.dell.com/support/manuals/en-uk/precision-15-3541-laptop/precision_3541_setupspecs/video?guid=guid-0712681b-956e-4229-96a7-545baca605fc=en-us; VERSION="20.04.5 LTS (Focal Fossa)" nick@Precision-3541:~$ sudo lshw -C display [sudo] password for nick: *-display description: 3D controller product: GP107GLM [Quadro P620] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list rom configuration: driver=nvidia latency=0 resources: irq:168 memory:ec00-ecff memory:c000-cfff memory:d000-d1ff ioport:3000(size=128) memory:ed00-ed07 *-display description: VGA compatible controller product: UHD Graphics 630 (Mobile) vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 00 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:166 memory:eb00-ebff memory:8000-8fff ioport:4000(size=64) memory:c-d 2. Connect a monitor and laptop with an HDMI cable 3. Result - The monitor should display "No Signal" - Ubuntu should recognize the monitor, but not display anything on it. # What should happen Ubuntu should send signal to external monitors connected to the HDMI port. It should automatically configure discrete graphics cards. The same hardware works when booted from the Windows partition. # What I've tried ## Things that worked None ## Things that worked temporarily https://askubuntu.com/questions/1105332/external-monitor-not-working-ubuntu-nvidia/1134579#1134579 Installing NVidia-Prime, Setting "Performance Mode" to always use the discrete GPU ## Things that did not work (from various forums) 1. Using multiple different drivers via "Software/Additional Drivers" 2. Using the driver from NVidia's website 3. Enabling NVidia via a modprob parameter at startup 4. Varius xorg configuration files ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.161.03 Wed Oct 19 00:10:36 UTC 2022 GCC version: gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1) ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 16:58:33 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.161.03, 5.15.0-58-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00
[Touch-packages] [Bug 2003136] Re: Settings window becomes broken and unresponsive when changing scales, sometimes
** Summary changed: - video corruption when using gnome-display settings + Settings window becomes broken and unresponsive when changing scales, sometimes ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Settings window becomes broken and unresponsive when changing scales, sometimes + Settings window becomes broken and unresponsive when changing display scale, sometimes -- 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/2003136 Title: Settings window becomes broken and unresponsive when changing display scale, sometimes Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I might need help routing this to the correct project. gnome-display-properties I believe is the application in foreground. I was using it normally, then switched the screen resolution scale to 100% (down from 200%). I had a Chrome window open which now had the inner icons shrunk, but not the boundaries of the window. So I moved the chrome window around, and noticed this corruption / tearing. The video is interesting because I believe it is telling us that the boundaries of the window are not (re?)set properly for the gnome- display-properties when display scale is applied. Is this what you see in the video too ? ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..52.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.161.03 Wed Oct 19 00:10:36 UTC 2022 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1) ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 17:49:57 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. TU117 [GeForce GTX 1650] [3842:1257] InstallationDate: Installed on 2023-01-09 (8 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-01-15 (2 days ago) dmi.bios.date: 12/05/2022 dmi.bios.release: 1.58 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET82W (1.58 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET82W(1.58):bd12/05/2022:br1.58:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
[Touch-packages] [Bug 2003099] Re: Flickering when minimizing
*** This bug is a duplicate of bug 1969140 *** https://bugs.launchpad.net/bugs/1969140 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 1969140, 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) => mutter (Ubuntu) ** This bug has been marked a duplicate of bug 1969140 Window minimize animation flickers and appears in the wrong place in Xorg sessions -- 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/2003099 Title: Flickering when minimizing Status in mutter package in Ubuntu: New Bug description: When minimizing windowed applications, the animation sometimes jumps wildly around, mostly to the top left corner of the screen. I found a temporary workaround with a config file in /etc/X11/xorg.conf.d/20-intel.conf, which supposedly has some other unwanted effects on other programs. Thanks for your help!! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..3c.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.60.11 Wed Nov 23 23:04:03 UTC 2022 GCC version: 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: Tue Jan 17 17:12:59 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo WhiskeyLake-U GT2 [UHD Graphics 620] [17aa:2283] Subsystem: Lenovo GP108M [GeForce MX250] [17aa:2283] InstallationDate: Installed on 2023-01-02 (14 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20N4002VGE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=72ad0f02-9e2a-4714-8427-9372619f5f04 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2020 dmi.bios.release: 1.68 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET90W (1.68 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N4002VGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnLENOVO:bvrN2IET90W(1.68):bd07/06/2020:br1.68:efr1.17:svnLENOVO:pn20N4002VGE:pvrThinkPadT590:rvnLENOVO:rn20N4002VGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20N4_BU_Think_FM_ThinkPadT590: dmi.product.family: ThinkPad T590 dmi.product.name: 20N4002VGE dmi.product.sku: LENOVO_MT_20N4_BU_Think_FM_ThinkPad T590 dmi.product.version: ThinkPad T590 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.3 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.3-2ubuntu2.5 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/+source/mutter/+bug/2003099/+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 2003140] Re: Ubuntu laptop can't use external monitors
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is mostly about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 -- 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/2003140 Title: Ubuntu laptop can't use external monitors Status in xorg package in Ubuntu: New Bug description: # What happens (Steps to reproduce): 1. Install a clean version of Ubuntu onto a laptop: Hardware="https://www.dell.com/support/manuals/en-uk/precision-15-3541-laptop/precision_3541_setupspecs/video?guid=guid-0712681b-956e-4229-96a7-545baca605fc=en-us; VERSION="20.04.5 LTS (Focal Fossa)" nick@Precision-3541:~$ sudo lshw -C display [sudo] password for nick: *-display description: 3D controller product: GP107GLM [Quadro P620] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list rom configuration: driver=nvidia latency=0 resources: irq:168 memory:ec00-ecff memory:c000-cfff memory:d000-d1ff ioport:3000(size=128) memory:ed00-ed07 *-display description: VGA compatible controller product: UHD Graphics 630 (Mobile) vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 00 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:166 memory:eb00-ebff memory:8000-8fff ioport:4000(size=64) memory:c-d 2. Connect a monitor and laptop with an HDMI cable 3. Result - The monitor should display "No Signal" - Ubuntu should recognize the monitor, but not display anything on it. # What should happen Ubuntu should send signal to external monitors connected to the HDMI port. It should automatically configure discrete graphics cards. The same hardware works when booted from the Windows partition. # What I've tried ## Things that worked None ## Things that worked temporarily https://askubuntu.com/questions/1105332/external-monitor-not-working-ubuntu-nvidia/1134579#1134579 Installing NVidia-Prime, Setting "Performance Mode" to always use the discrete GPU ## Things that did not work (from various forums) 1. Using multiple different drivers via "Software/Additional Drivers" 2. Using the driver from NVidia's website 3. Enabling NVidia via a modprob parameter at startup 4. Varius xorg configuration files ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.161.03 Wed Oct 19 00:10:36 UTC 2022 GCC version: gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1) ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 16:58:33 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.161.03, 5.15.0-58-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:091a] Subsystem: Dell GP107GLM [Quadro P620] [1028:091a] InstallationDate: Installed on 2023-01-06 (11 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. Precision 3541 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash
[Touch-packages] [Bug 2003140] Re: Ubuntu laptop can't use external monitors
** Description changed: # What happens (Steps to reproduce): 1. Install a clean version of Ubuntu onto a laptop: Hardware="https://www.dell.com/support/manuals/en-uk/precision-15-3541-laptop/precision_3541_setupspecs/video?guid=guid-0712681b-956e-4229-96a7-545baca605fc=en-us; VERSION="20.04.5 LTS (Focal Fossa)" nick@Precision-3541:~$ sudo lshw -C display [sudo] password for nick: *-display description: 3D controller product: GP107GLM [Quadro P620] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list rom configuration: driver=nvidia latency=0 resources: irq:168 memory:ec00-ecff memory:c000-cfff memory:d000-d1ff ioport:3000(size=128) memory:ed00-ed07 *-display description: VGA compatible controller product: UHD Graphics 630 (Mobile) vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 00 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:166 memory:eb00-ebff memory:8000-8fff ioport:4000(size=64) memory:c-d 2. Connect a monitor and laptop with an HDMI cable 3. Result - The monitor should display "No Signal" - Ubuntu should recognize the monitor, but not display anything on it. # What should happen Ubuntu should send signal to external monitors connected to the HDMI port. It should automatically configure discrete graphics cards. The same hardware works when booted from the Windows partition. # What I've tried ## Things that worked + None + + ## Things that worked temporarily https://askubuntu.com/questions/1105332/external-monitor-not-working-ubuntu-nvidia/1134579#1134579 - Edit /lib/modprobe.d/nvidia-kms.conf to enable modsetting - - ## Things that worked temporarily - Installing NVidia-Prime, Setting "Performance Mode" to always use the discrete GPU + Installing NVidia-Prime, Setting "Performance Mode" to always use the + discrete GPU ## Things that did not work (from various forums) 1. Using multiple different drivers via "Software/Additional Drivers" 2. Using the driver from NVidia's website 3. Enabling NVidia via a modprob parameter at startup 4. Varius xorg configuration files ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.161.03 Wed Oct 19 00:10:36 UTC 2022 GCC version: gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1) ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 16:58:33 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.161.03, 5.15.0-58-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:091a] Subsystem: Dell GP107GLM [Quadro P620] [1028:091a] InstallationDate: Installed on 2023-01-06 (11 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. Precision 3541 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=90df9afc-2dd2-439d-a69c-3aa27146e9fc ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: dmi.bios.date: 09/13/2022 dmi.bios.release: 1.23 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.23.0 dmi.board.name: 0Y8H01 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.23.0:bd09/13/2022:br1.23:svnDellInc.:pnPrecision3541:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:sku091A:
[Touch-packages] [Bug 2003140] Re: Ubuntu laptop can't use external monitors
** 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/2003140 Title: Ubuntu laptop can't use external monitors Status in xorg package in Ubuntu: New Bug description: # What happens (Steps to reproduce): 1. Install a clean version of Ubuntu onto a laptop: Hardware="https://www.dell.com/support/manuals/en-uk/precision-15-3541-laptop/precision_3541_setupspecs/video?guid=guid-0712681b-956e-4229-96a7-545baca605fc=en-us; VERSION="20.04.5 LTS (Focal Fossa)" nick@Precision-3541:~$ sudo lshw -C display [sudo] password for nick: *-display description: 3D controller product: GP107GLM [Quadro P620] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list rom configuration: driver=nvidia latency=0 resources: irq:168 memory:ec00-ecff memory:c000-cfff memory:d000-d1ff ioport:3000(size=128) memory:ed00-ed07 *-display description: VGA compatible controller product: UHD Graphics 630 (Mobile) vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 00 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:166 memory:eb00-ebff memory:8000-8fff ioport:4000(size=64) memory:c-d 2. Connect a monitor and laptop with an HDMI cable 3. Result - The monitor should display "No Signal" - Ubuntu should recognize the monitor, but not display anything on it. # What should happen Ubuntu should send signal to external monitors connected to the HDMI port. It should automatically configure discrete graphics cards. The same hardware works when booted from the Windows partition. # What I've tried ## Things that worked https://askubuntu.com/questions/1105332/external-monitor-not-working-ubuntu-nvidia/1134579#1134579 Edit /lib/modprobe.d/nvidia-kms.conf to enable modsetting ## Things that worked temporarily Installing NVidia-Prime, Setting "Performance Mode" to always use the discrete GPU ## Things that did not work (from various forums) 1. Using multiple different drivers via "Software/Additional Drivers" 2. Using the driver from NVidia's website 3. Enabling NVidia via a modprob parameter at startup 4. Varius xorg configuration files ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.161.03 Wed Oct 19 00:10:36 UTC 2022 GCC version: gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1) ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 16:58:33 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.161.03, 5.15.0-58-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:091a] Subsystem: Dell GP107GLM [Quadro P620] [1028:091a] InstallationDate: Installed on 2023-01-06 (11 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. Precision 3541 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=90df9afc-2dd2-439d-a69c-3aa27146e9fc ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: dmi.bios.date: 09/13/2022 dmi.bios.release: 1.23 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.23.0 dmi.board.name: 0Y8H01 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc.
[Touch-packages] [Bug 2003140] [NEW] Ubuntu laptop can't use external monitors
You have been subscribed to a public bug: # What happens (Steps to reproduce): 1. Install a clean version of Ubuntu onto a laptop: Hardware="https://www.dell.com/support/manuals/en-uk/precision-15-3541-laptop/precision_3541_setupspecs/video?guid=guid-0712681b-956e-4229-96a7-545baca605fc=en-us; VERSION="20.04.5 LTS (Focal Fossa)" nick@Precision-3541:~$ sudo lshw -C display [sudo] password for nick: *-display description: 3D controller product: GP107GLM [Quadro P620] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list rom configuration: driver=nvidia latency=0 resources: irq:168 memory:ec00-ecff memory:c000-cfff memory:d000-d1ff ioport:3000(size=128) memory:ed00-ed07 *-display description: VGA compatible controller product: UHD Graphics 630 (Mobile) vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 00 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:166 memory:eb00-ebff memory:8000-8fff ioport:4000(size=64) memory:c-d 2. Connect a monitor and laptop with an HDMI cable 3. Result - The monitor should display "No Signal" - Ubuntu should recognize the monitor, but not display anything on it. # What should happen Ubuntu should send signal to external monitors connected to the HDMI port. It should automatically configure discrete graphics cards. The same hardware works when booted from the Windows partition. # What I've tried ## Things that worked https://askubuntu.com/questions/1105332/external-monitor-not-working-ubuntu-nvidia/1134579#1134579 Edit /lib/modprobe.d/nvidia-kms.conf to enable modsetting ## Things that worked temporarily Installing NVidia-Prime, Setting "Performance Mode" to always use the discrete GPU ## Things that did not work (from various forums) 1. Using multiple different drivers via "Software/Additional Drivers" 2. Using the driver from NVidia's website 3. Enabling NVidia via a modprob parameter at startup 4. Varius xorg configuration files ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.161.03 Wed Oct 19 00:10:36 UTC 2022 GCC version: gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1) ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 16:58:33 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.161.03, 5.15.0-58-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:091a] Subsystem: Dell GP107GLM [Quadro P620] [1028:091a] InstallationDate: Installed on 2023-01-06 (11 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. Precision 3541 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=90df9afc-2dd2-439d-a69c-3aa27146e9fc ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: dmi.bios.date: 09/13/2022 dmi.bios.release: 1.23 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.23.0 dmi.board.name: 0Y8H01 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.23.0:bd09/13/2022:br1.23:svnDellInc.:pnPrecision3541:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:sku091A: dmi.product.family: Precision dmi.product.name: Precision 3541 dmi.product.sku: 091A dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers:
[Touch-packages] [Bug 2003136] Re: video corruption when using gnome-display settings
attached file. Timeout was received for the file upload. Attaching a vimeo link instead. https://vimeo.com/790229569 ** Attachment added: "PXL_20230117_224753761.mp4" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2003136/+attachment/5642093/+files/PXL_20230117_224753761.mp4 -- 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/2003136 Title: video corruption when using gnome-display settings Status in xorg package in Ubuntu: New Bug description: I might need help routing this to the correct project. gnome-display-properties I believe is the application in foreground. I was using it normally, then switched the screen resolution scale to 100% (down from 200%). I had a Chrome window open which now had the inner icons shrunk, but not the boundaries of the window. So I moved the chrome window around, and noticed this corruption / tearing. The video is interesting because I believe it is telling us that the boundaries of the window are not (re?)set properly for the gnome- display-properties when display scale is applied. Is this what you see in the video too ? ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..52.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.161.03 Wed Oct 19 00:10:36 UTC 2022 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1) ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 17:49:57 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. TU117 [GeForce GTX 1650] [3842:1257] InstallationDate: Installed on 2023-01-09 (8 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-01-15 (2 days ago) dmi.bios.date: 12/05/2022 dmi.bios.release: 1.58 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET82W (1.58 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET82W(1.58):bd12/05/2022:br1.58:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 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:
[Touch-packages] [Bug 2002043] Re: Python extension modules get built using wrong compiler flags with python2
@Nafees,
I'm sorry, I hadn't noticed that the file produced by python3 was
different (and I did have the test.so in my directory because I had
built it with python2 before, so I was just grepping the same file). I
see the problem now and I'm checking it with our Engineering team.
Regards,
Fabio Martins
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/2002043
Title:
Python extension modules get built using wrong compiler flags with
python2
Status in python2.7 package in Ubuntu:
New
Bug description:
Compiling a Python extension using Python2 (Python 2.7.18) is making
use of wrong compiler flags, hence dropping required optimizations
when required. This is happening only when python2 is installed from
Ubuntu's repositories. By default, Python's distutils module uses
compiler and linker flags used to compile Python itself to be used to
compile extensions.
Steps to reproduce:
1) On Ubuntu 20.04, install python2 using apt package manager.
2) After successful installation, verify the CFLAGS variable from sysconfig
module. On my machine, the output is
Python 2.7.18 (default, Jul 1 2022, 12:27:04)
[GCC 9.4.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sysconfig
>>> sysconfig.get_config_var('CFLAGS')
'-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes
-Wdate-time -D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security '
3) Build a test extension module using python2 and verify the compilation
flags.
python2 setup.py build_ext --inplace
Output from below command is not matching with our expected above CFLAGS.
aarch64-linux-gnu-gcc -pthread -fno-strict-aliasing -Wdate-time
-D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security -fPIC
-I/usr/include/python2.7 -c testmodule.c -o
build/temp.linux-aarch64-2.7/testmodule.o
On further investigation, it looks like Ubuntu's specific patch applied on
libpython2.7-stdlib package is altering the original upstream implementation of
distutils/sysconfig.py code.
Package - https://packages.ubuntu.com/focal/libpython2.7-stdlib
Patch -
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
Below is the code block which is causing the issue, where the presence of
configure_cflags is modifying cflags. This code is result of ubuntu's patch and
doesn't come directly from upstream python implementation.
File - /usr/lib/python2.7/distutils/sysconfig.py
Part of code block:
elif configure_cflags:
cflags = ' '.join(str(x) for x in (basecflags, configure_cflags,
extra_cflags) if x)
ldshared = ldshared + ' ' + configure_cflags
I don't see problem on Python3 though we have extra code added from patch
there as well. Patch used on python3, is not modifying the cflags completely
and instead appending new flags to cflags.
On python3 (tested on Ubuntu 20.04)
File - /usr/lib/python3.8/distutils/sysconfig.py
Part of code block which doesn't alter cflags completely
elif configure_cflags:
cflags = cflags + ' ' + configure_cflags
ldshared = ldshared + ' ' + configure_cflags
Request to update the python2 patch to behave similar to what is been done on
python3.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/2002043/+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 2003136] [NEW] video corruption when using gnome-display settings
Public bug reported: I might need help routing this to the correct project. gnome-display-properties I believe is the application in foreground. I was using it normally, then switched the screen resolution scale to 100% (down from 200%). I had a Chrome window open which now had the inner icons shrunk, but not the boundaries of the window. So I moved the chrome window around, and noticed this corruption / tearing. The video is interesting because I believe it is telling us that the boundaries of the window are not (re?)set properly for the gnome- display-properties when display scale is applied. Is this what you see in the video too ? ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..52.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.161.03 Wed Oct 19 00:10:36 UTC 2022 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1) ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 17:49:57 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. TU117 [GeForce GTX 1650] [3842:1257] InstallationDate: Installed on 2023-01-09 (8 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-01-15 (2 days ago) dmi.bios.date: 12/05/2022 dmi.bios.release: 1.58 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET82W (1.58 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET82W(1.58):bd12/05/2022:br1.58:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption kinetic 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/2003136 Title: video corruption when using gnome-display settings Status in xorg package in Ubuntu: New Bug description: I might need help routing this to the correct project. gnome-display-properties I believe is the application in foreground. I was using it normally, then switched the screen resolution scale to 100% (down from 200%). I had a Chrome window open which now had the
[Touch-packages] [Bug 1863894] Re: /etc/bash.bashrc invokes groups command which is slow in large environments
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bash (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1863894 Title: /etc/bash.bashrc invokes groups command which is slow in large environments Status in bash package in Ubuntu: Confirmed Bug description: /etc/bash.bashrc runs groups(1) whenever a new shell is started. This command calls getgrgid(3) on every group of which the user is a member. In an environment where FreeIPA is used to allow users to log into their computers using their Active Directory accounts, I have seen each call to getgrid(3) take over ten seconds. My Active Directory user is a member of 30 groups and it is not uncommon for users to be a member of 50 or more groups. This results in enormous delays when logging in to a system with SSH, launching a terminal emulator or even creating a new tab in an existing terminal emulator. The code from /etc/bash.bashrc wants to find out whether the user is a member of the 'sudo' or 'admin' groups in order to display a hint to the user. # sudo hint if [ ! -e "$HOME/.sudo_as_admin_successful" ] && [ ! -e "$HOME/.hushlogin" ] ; then case " $(groups) " in *\ admin\ *|*\ sudo\ *) if [ -x /usr/bin/sudo ]; then cat <<-EOF To run a command as administrator (user "root"), use "sudo ". See "man sudo_root" for details. EOF fi esac fi This can be rewritten to avoid calling getgrgid(3) for every group that the user is a member of by doing something like this (untested): # sudo hint if [[ -x /usr/bin/sudo ]]; then if [[ ! -e $HOME/.sudo_as_admin_successful && ! -e $HOME/.hushlogin ]]; then sudo_gid=$(getent group sudo | cut -d: -f3) admin_gid=$(getent group admin | cut -d: -f3) for gid in $(id -G); do if [[ $gid -eq $sudo_gid || $gid -eq $admin_gid ]]; then cat <<-EOF To run a command as administrator (user "root"), use "sudo ". See "man sudo_root" for details. EOF break fi done fi fi As an aside: the reason that getgrid(3) is so slow is because it must fetch the members of each group. There is no quick way to do this in Active Directory: a recursive search for group members must be performed, followed by a lookups to retrieve each of their their POSIX UIDs, and then more lookup to retrieve their POSIX username. Even when the 'ignore_group_members' sssd(8) option is enabled, which causes getgrid(3) to report that a group has no members, calling getgrid(3) on 30-40 groups still takes a few seconds. And this option is not the default. It's also not uncommon to have groups with spaces in their names, which causes groups(1) to produce ambiguous output. For these reasons it is best to avoid the use of groups(1) in scripts where more performant and robust alternatives are available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1863894/+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 1998265] Re: OverFlow error when using cnf-extractor
This bug was fixed in the package python-apt - 2.0.1 --- python-apt (2.0.1) focal; urgency=medium * We're back to a proper upstream release with CI and all * AcquireFile: Handle large files (LP: #1998265) * Update mirror list * debian/gbp.conf: Point at 2.0.y branch * d/t/control: Add missing binutils test dependency -- Julian Andres Klode Thu, 01 Dec 2022 13:33:42 +0100 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1998265 Title: OverFlow error when using cnf-extractor Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Bionic: Fix Released Status in python-apt source package in Focal: Fix Released Status in python-apt source package in Jammy: Fix Released Status in python-apt source package in Kinetic: Fix Released Bug description: [Impact] Large files can't be downloaded as we use a 32-bit integer in AcquireFile constructor, this breaks e.g. command-not-found generator: I'm trying to update the command-not-found indexes (bin/cnf-extract.py $MIRROR $suite $component $arch) on the production cnf extractor system (running bionic) and have encountered Tracebacks when generating them for Jammy and Lunar. This is causing the command not found indexes to be out of date for all(?) releases of Ubuntu. The lunar failure: Get:1 dotnet-sdk-6.0_6.0.111-0ubuntu3_amd64.deb [79.1 MB] Fetched 79.1 MB in 0s (0 B/s) Traceback (most recent call last):64... 7% File "./bin/cnf-extract.py", line 54, in mirror_root, suite, component, arch) File "/srv/cnf-extractor/extractor/extractor.py", line 174, in command_not_found_extract debpath = pkg.candidate.fetch_binary(destdir=tmpdir) File "/usr/lib/python3/dist-packages/apt/package.py", line 883, in fetch_binary self.size, base, destfile=destfile) OverflowError: signed integer is greater than maximum I'll get more context for the Jammy failure but it wouldn't surprise me if it was the same package. [Test plan] I have included a test for the AcquireFile constructor to accept a large file size, and then a test that ensures it can read the file size. Run the autopkgtest suite. [Where problems could occur] It could fail in other places now. For kinetic, the package was copied in from lunar without changes. This upload is actually built in kinetic and hence there is additional regression potential from toolchain changes. [Other info] Also including some auxiliary changes as we move back to proper upstream releases to enable testing, mostly around d/gbp.conf, .gitlab-ci.yml - being updated to point at right places d/t/control - adding a missing test dependency data/ - updated mirror lists The mirror lists are standard updates; the debian/tests/control change is needed to enable testing on more minimal autopkgtest images (our images accidentally include binutils); the other changes have zero impact on the Ubuntu infra or end user side as they only run during development. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1998265/+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 1998265] Re: OverFlow error when using cnf-extractor
This bug was fixed in the package python-apt - 2.4.0 --- python-apt (2.4.0) jammy; urgency=medium [ Julian Andres Klode ] * 2.4.0 marks this as a stable upstream release series. * AcquireFile: Handle large files (LP: #1998265) * .gitlab-ci.yml: Test in jammy and fix mypy version to jammy * Update mirror lists * debian/gbp.conf: Point at 2.4.y branch * d/t/control: Add missing binutils test dependency [ Michael Vogt ] * apt: fix mypy in apt.progress.text.AcquireProgress (LP: #1998488) -- Julian Andres Klode Thu, 01 Dec 2022 17:30:57 +0100 ** Changed in: python-apt (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1998265 Title: OverFlow error when using cnf-extractor Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Bionic: Fix Released Status in python-apt source package in Focal: Fix Released Status in python-apt source package in Jammy: Fix Released Status in python-apt source package in Kinetic: Fix Released Bug description: [Impact] Large files can't be downloaded as we use a 32-bit integer in AcquireFile constructor, this breaks e.g. command-not-found generator: I'm trying to update the command-not-found indexes (bin/cnf-extract.py $MIRROR $suite $component $arch) on the production cnf extractor system (running bionic) and have encountered Tracebacks when generating them for Jammy and Lunar. This is causing the command not found indexes to be out of date for all(?) releases of Ubuntu. The lunar failure: Get:1 dotnet-sdk-6.0_6.0.111-0ubuntu3_amd64.deb [79.1 MB] Fetched 79.1 MB in 0s (0 B/s) Traceback (most recent call last):64... 7% File "./bin/cnf-extract.py", line 54, in mirror_root, suite, component, arch) File "/srv/cnf-extractor/extractor/extractor.py", line 174, in command_not_found_extract debpath = pkg.candidate.fetch_binary(destdir=tmpdir) File "/usr/lib/python3/dist-packages/apt/package.py", line 883, in fetch_binary self.size, base, destfile=destfile) OverflowError: signed integer is greater than maximum I'll get more context for the Jammy failure but it wouldn't surprise me if it was the same package. [Test plan] I have included a test for the AcquireFile constructor to accept a large file size, and then a test that ensures it can read the file size. Run the autopkgtest suite. [Where problems could occur] It could fail in other places now. For kinetic, the package was copied in from lunar without changes. This upload is actually built in kinetic and hence there is additional regression potential from toolchain changes. [Other info] Also including some auxiliary changes as we move back to proper upstream releases to enable testing, mostly around d/gbp.conf, .gitlab-ci.yml - being updated to point at right places d/t/control - adding a missing test dependency data/ - updated mirror lists The mirror lists are standard updates; the debian/tests/control change is needed to enable testing on more minimal autopkgtest images (our images accidentally include binutils); the other changes have zero impact on the Ubuntu infra or end user side as they only run during development. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1998265/+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 1998265] Re: OverFlow error when using cnf-extractor
This bug was fixed in the package python-apt - 2.4.0+22.10 --- python-apt (2.4.0+22.10) kinetic; urgency=medium [ Julian Andres Klode ] * 2.4.0 marks this as a stable upstream release series. * AcquireFile: Handle large files (LP: #1998265) * .gitlab-ci.yml: Test in jammy and fix mypy version to jammy * Update mirror lists * debian/gbp.conf: Point at 2.4.y branch * d/t/control: Add missing binutils test dependency [ Michael Vogt ] * apt: fix mypy in apt.progress.text.AcquireProgress (LP: #1998488) -- Julian Andres Klode Thu, 01 Dec 2022 17:30:57 +0100 ** Changed in: python-apt (Ubuntu Kinetic) Status: Fix Committed => Fix Released ** Changed in: python-apt (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1998265 Title: OverFlow error when using cnf-extractor Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Bionic: Fix Released Status in python-apt source package in Focal: Fix Released Status in python-apt source package in Jammy: Fix Released Status in python-apt source package in Kinetic: Fix Released Bug description: [Impact] Large files can't be downloaded as we use a 32-bit integer in AcquireFile constructor, this breaks e.g. command-not-found generator: I'm trying to update the command-not-found indexes (bin/cnf-extract.py $MIRROR $suite $component $arch) on the production cnf extractor system (running bionic) and have encountered Tracebacks when generating them for Jammy and Lunar. This is causing the command not found indexes to be out of date for all(?) releases of Ubuntu. The lunar failure: Get:1 dotnet-sdk-6.0_6.0.111-0ubuntu3_amd64.deb [79.1 MB] Fetched 79.1 MB in 0s (0 B/s) Traceback (most recent call last):64... 7% File "./bin/cnf-extract.py", line 54, in mirror_root, suite, component, arch) File "/srv/cnf-extractor/extractor/extractor.py", line 174, in command_not_found_extract debpath = pkg.candidate.fetch_binary(destdir=tmpdir) File "/usr/lib/python3/dist-packages/apt/package.py", line 883, in fetch_binary self.size, base, destfile=destfile) OverflowError: signed integer is greater than maximum I'll get more context for the Jammy failure but it wouldn't surprise me if it was the same package. [Test plan] I have included a test for the AcquireFile constructor to accept a large file size, and then a test that ensures it can read the file size. Run the autopkgtest suite. [Where problems could occur] It could fail in other places now. For kinetic, the package was copied in from lunar without changes. This upload is actually built in kinetic and hence there is additional regression potential from toolchain changes. [Other info] Also including some auxiliary changes as we move back to proper upstream releases to enable testing, mostly around d/gbp.conf, .gitlab-ci.yml - being updated to point at right places d/t/control - adding a missing test dependency data/ - updated mirror lists The mirror lists are standard updates; the debian/tests/control change is needed to enable testing on more minimal autopkgtest images (our images accidentally include binutils); the other changes have zero impact on the Ubuntu infra or end user side as they only run during development. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1998265/+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 1998488] Re: Wrong type annotation in apt.progress.text.AcquireProgress
This bug was fixed in the package python-apt - 2.4.0 --- python-apt (2.4.0) jammy; urgency=medium [ Julian Andres Klode ] * 2.4.0 marks this as a stable upstream release series. * AcquireFile: Handle large files (LP: #1998265) * .gitlab-ci.yml: Test in jammy and fix mypy version to jammy * Update mirror lists * debian/gbp.conf: Point at 2.4.y branch * d/t/control: Add missing binutils test dependency [ Michael Vogt ] * apt: fix mypy in apt.progress.text.AcquireProgress (LP: #1998488) -- Julian Andres Klode Thu, 01 Dec 2022 17:30:57 +0100 ** Changed in: python-apt (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1998488 Title: Wrong type annotation in apt.progress.text.AcquireProgress Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Jammy: Fix Released Status in python-apt source package in Kinetic: Fix Released Status in python-apt source package in Lunar: Fix Released Bug description: [Impact] Type checking fails in CI [Test plan] Have CI type check successfully [Where problems could occur] It's only a comment *inside* the function, so not really anywhere. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1998488/+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 1998488] Update Released
The verification of the Stable Release Update for python-apt has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1998488 Title: Wrong type annotation in apt.progress.text.AcquireProgress Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Jammy: Fix Released Status in python-apt source package in Kinetic: Fix Released Status in python-apt source package in Lunar: Fix Released Bug description: [Impact] Type checking fails in CI [Test plan] Have CI type check successfully [Where problems could occur] It's only a comment *inside* the function, so not really anywhere. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1998488/+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 1998488] Re: Wrong type annotation in apt.progress.text.AcquireProgress
This bug was fixed in the package python-apt - 2.4.0+22.10 --- python-apt (2.4.0+22.10) kinetic; urgency=medium [ Julian Andres Klode ] * 2.4.0 marks this as a stable upstream release series. * AcquireFile: Handle large files (LP: #1998265) * .gitlab-ci.yml: Test in jammy and fix mypy version to jammy * Update mirror lists * debian/gbp.conf: Point at 2.4.y branch * d/t/control: Add missing binutils test dependency [ Michael Vogt ] * apt: fix mypy in apt.progress.text.AcquireProgress (LP: #1998488) -- Julian Andres Klode Thu, 01 Dec 2022 17:30:57 +0100 ** Changed in: python-apt (Ubuntu Kinetic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1998488 Title: Wrong type annotation in apt.progress.text.AcquireProgress Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Jammy: Fix Released Status in python-apt source package in Kinetic: Fix Released Status in python-apt source package in Lunar: Fix Released Bug description: [Impact] Type checking fails in CI [Test plan] Have CI type check successfully [Where problems could occur] It's only a comment *inside* the function, so not really anywhere. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1998488/+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 1993395] Re: Merge cyrus-sasl2 from Debian unstable for l-series
This migrated.
** Changed in: cyrus-sasl2 (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/1993395
Title:
Merge cyrus-sasl2 from Debian unstable for l-series
Status in cyrus-sasl2 package in Ubuntu:
Fix Released
Bug description:
Scheduled-For: ubuntu-23.01
Upstream: tbd
Debian: 2.1.28+dfsg-8
Ubuntu: 2.1.28+dfsg-6ubuntu2
### New Debian Changes ###
cyrus-sasl2 (2.1.28+dfsg-8) unstable; urgency=medium
[ Andreas Hasenack ]
* Add SASL channel binding support for GSSAPI and GSS-SPNEGO
(LP: #1912256):
- d/p/0034-channel-binding-gssapi-gss-spnego.patch: add SASL channel
binding support for GSSAPI and GSS-SPNEGO
- d/p/0035-Add-support-for-setting-max-ssf-0-to-GSS-SPNEGO-1.patch:
allow setting maxssf to 0 when using GSS-SPNEGO inside SSL/TLS
- d/p/0035-Add-support-for-setting-max-ssf-0-to-GSS-SPNEGO-2.patch:
be more conformant to RFC4752
-- Bastian Germann Mon, 05 Sep 2022 14:30:39 +0200
cyrus-sasl2 (2.1.28+dfsg-7) unstable; urgency=medium
* d/tests: Relicense to GPL-3
* Patch: honor log level option on clients (LP: #827151)
-- Bastian Germann Thu, 18 Aug 2022 23:24:01 +0200
cyrus-sasl2 (2.1.28+dfsg-6) unstable; urgency=high
* d/copyright: Add debian/tests info
[ Andreas Hasenack ]
* d/p/0026-Gracefully-handle-failed-init.patch (Closes: #1011249)
* d/p/0027-Catch-errors-from-EVP_Digest-functions.patch
* d/p/0029-Load-OpenSSL3-legacy-provider-digestmd5.patch
* d/t/{control,shared-secret-mechs}: test shared secret mechanisms
-- Bastian Germann Thu, 19 May 2022 22:10:49 +0200
cyrus-sasl2 (2.1.28+dfsg-5) unstable; urgency=medium
* Recover upstream-compatible debian/* license
* debian/po: Convert non-UTF-8 to UTF-8
* Patch: Fix time.h check (fixes implicit-function-declarations)
[ Andreas Hasenack ]
* d/t/{control,pluginviewer}: test available mechanisms
* d/t/{control,saslauthd}: saslauthd tests with multiple mechanisms
* d/t/{control,gssapi}: test for SASL GSSAPI using OpenLDAP
-- Bastian Germann Sat, 14 May 2022 14:32:58 +0200
cyrus-sasl2 (2.1.28+dfsg-4) unstable; urgency=medium
* d/copyright: java/* files were removed upstream
* d/copyright: Reformat the default license's margin
* d/copyright: Add project's license to include/makemd5.c
* Move SCRAM to libsasl2-modules (Closes: #977360)
* Install additional GS2 module for Heimdal
* Remove Roberto from the Uploaders
* Drop 0005-Fixes-in-library-mutexes.patch
* Drop 0021-Fix-keytab-option-for-MIT-Kerberos.patch
* Remove former logcheck conffile (Closes: #1009851)
* lintian: Fix excessive-priority-for-library-package
* lintian: Fix package-contains-empty-directory
-- Bastian Germann Wed, 20 Apr 2022 01:01:01 +0200
cyrus-sasl2 (2.1.28+dfsg-3) unstable; urgency=high
* Set MIT/Heimdal CFLAGS instead of CPPFLAGS
* Drop unnecessary 0027-properly-create-libsasl2.pc.patch
* Prevent installing outdated ChangeLog (Closes: #1009681)
* Remove debug log message and its logcheck rule (Closes: #805310)
* Self-reference pluginviewer man as saslpluginviewer (Closes: #1009380)
* Get rid of broken README.configure-options
* Add sasldbconverter2.8 manpage
* d/copyright: Add missing KTH license
* Install libsasl.5 manpage
[ Debian Janitor ]
* Remove constraints unnecessary since buster
-- Bastian Germann Fri, 15 Apr 2022 12:02:13 +0200
cyrus-sasl2 (2.1.28+dfsg-2) unstable; urgency=medium
* Remove cruft
-- Bastian Germann Fri, 25 Feb 2022 18:58:54 +0100
cyrus-sasl2 (2.1.28+dfsg-1) experimental; urgency=medium
* Drop upstream patches
* Import new release signing key
* Reset repacksuffix
* New upstream version 2.1.28+dfsg (CVE-2022-24407)
* Rebase 0027-properly-create-libsasl2.pc.patch
-- Bastian Germann Tue, 22 Feb 2022 23:40:47 +0100
cyrus-sasl2 (2.1.27+dfsg2-3) unstable; urgency=medium
[ Andreas Hasenack ]
* Fix configure.ac for autoconf 2.70 (Closes: #1003355, #1000152)
### Old Ubuntu Delta ###
cyrus-sasl2 (2.1.28+dfsg-6ubuntu2) kinetic; urgency=medium
* Add SASL channel binding support for GSSAPI and GSS-SPNEGO
(LP: #1912256):
- d/p/0034-channel-binding-gssapi-gss-spnego.patch: add SASL channel
binding support for GSSAPI and GSS-SPNEGO
- d/p/0035-Add-support-for-setting-max-ssf-0-to-GSS-SPNEGO-1.patch:
allow setting maxssf to 0 when using GSS-SPNEGO inside SSL/TLS
- d/p/0035-Add-support-for-setting-max-ssf-0-to-GSS-SPNEGO-2.patch:
be more conformant to RFC4752
-- Andreas Hasenack Tue, 16 Aug 2022
17:08:44 -0300
cyrus-sasl2 (2.1.28+dfsg-6ubuntu1) kinetic; urgency=medium
*
[Touch-packages] [Bug 2002994] Re: sshd_config makes some changes awkward
Thank you for your report. I agree. When I wrote the TOTP/HOTP section in https://ubuntu.com/server/docs/service-openssh, I wanted to use sshd_config.d/ but was unable to instruct readers without also changing sshd_config directly, so I gave up on the former to keep the instructions simpler. We're making progress at least though, in that now that we have the .d directory, defaults have somewhere to be moved to. -- 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/2002994 Title: sshd_config makes some changes awkward Status in openssh package in Ubuntu: Confirmed Bug description: As distribted, the file sshd_config has apparently been modified from an upstream version -- those lines that are NOT comments. There is no good way for me to change any of them, even though there is a sshd_config.d directory for my changes. That is because the files in the sshd_config.d directory are invoked early, and the uncommented lines in the sshd_config file override them. I would have to modify the sshd_config file which defeats the purpose of having the directory. I suggest to adopt a method that I have seen elsewhere: put all of your changes in a file and put the file in the .d directory. Start the filename with something like '50' so that it can sort before or after any file contributed by the local admin. Keep the sshd_config file as you get it from upstream. This is, after all, the reason that the .d directories exist. In this way, admins do not have to modify distributed files, which avoids awkwardness when the package is updated. The same applies to ssh_config. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.2p1-4ubuntu0.5 ProcVersionSignature: Ubuntu 5.4.0-122.138-generic 5.4.192 Uname: Linux 5.4.0-122-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Jan 16 06:29:16 2023 SourcePackage: openssh UpgradeStatus: Upgraded to focal on 2021-02-19 (696 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2002994/+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 2002994] Re: sshd_config makes some changes awkward
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: openssh (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2002994 Title: sshd_config makes some changes awkward Status in openssh package in Ubuntu: Confirmed Bug description: As distribted, the file sshd_config has apparently been modified from an upstream version -- those lines that are NOT comments. There is no good way for me to change any of them, even though there is a sshd_config.d directory for my changes. That is because the files in the sshd_config.d directory are invoked early, and the uncommented lines in the sshd_config file override them. I would have to modify the sshd_config file which defeats the purpose of having the directory. I suggest to adopt a method that I have seen elsewhere: put all of your changes in a file and put the file in the .d directory. Start the filename with something like '50' so that it can sort before or after any file contributed by the local admin. Keep the sshd_config file as you get it from upstream. This is, after all, the reason that the .d directories exist. In this way, admins do not have to modify distributed files, which avoids awkwardness when the package is updated. The same applies to ssh_config. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.2p1-4ubuntu0.5 ProcVersionSignature: Ubuntu 5.4.0-122.138-generic 5.4.192 Uname: Linux 5.4.0-122-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Jan 16 06:29:16 2023 SourcePackage: openssh UpgradeStatus: Upgraded to focal on 2021-02-19 (696 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2002994/+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 2003115] [NEW] bluetooth headphones poor sound quality
Public bug reported: Hello, I have jabra elite 3 bluetooth headphones. On my machine (ubuntu 22.10), the sound rings, stutters, and often stops. On this same machine, under windows or with a live cd of ubuntu 22.04, I have no problem. thank you to consider ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dob3008 F wireplumber /dev/snd/seq:dob3005 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 20:08:51 2023 InstallationDate: Installed on 2023-01-03 (13 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2022 dmi.bios.release: 15.26 dmi.bios.vendor: Insyde dmi.bios.version: F.26 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84BB dmi.board.vendor: HP dmi.board.version: 15.32 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 15.32 dmi.modalias: dmi:bvnInsyde:bvrF.26:bd07/25/2022:br15.26:efr15.32:svnHP:pnHPPavilionLaptop14-ce2xxx:pvrType1ProductConfigId:rvnHP:rn84BB:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku8KZ34EA#ABF: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 14-ce2xxx dmi.product.sku: 8KZ34EA#ABF dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2003115 Title: bluetooth headphones poor sound quality Status in alsa-driver package in Ubuntu: New Bug description: Hello, I have jabra elite 3 bluetooth headphones. On my machine (ubuntu 22.10), the sound rings, stutters, and often stops. On this same machine, under windows or with a live cd of ubuntu 22.04, I have no problem. thank you to consider ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dob3008 F wireplumber /dev/snd/seq:dob3005 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 20:08:51 2023 InstallationDate: Installed on 2023-01-03 (13 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2022 dmi.bios.release: 15.26 dmi.bios.vendor: Insyde dmi.bios.version: F.26 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84BB dmi.board.vendor: HP dmi.board.version: 15.32 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 15.32 dmi.modalias: dmi:bvnInsyde:bvrF.26:bd07/25/2022:br15.26:efr15.32:svnHP:pnHPPavilionLaptop14-ce2xxx:pvrType1ProductConfigId:rvnHP:rn84BB:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku8KZ34EA#ABF: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 14-ce2xxx dmi.product.sku: 8KZ34EA#ABF dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2003115/+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 2002923] Re: Please merge 2.5.0-4 into lunar
** Changed in: python-testtools (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-testtools in Ubuntu. https://bugs.launchpad.net/bugs/2002923 Title: Please merge 2.5.0-4 into lunar Status in python-testtools package in Ubuntu: Fix Released Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-testtools/+bug/2002923/+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 2003105] Re: rsyslog fills the root filesystem by spamming messages
Note that this applies `rsyslog-8.2112.0-2ubuntu2.2`, but I needed to remove it from my machine before system allowed me to do anything. Otherwise rsyslog spams SSD, and I am unable to do anything, and some programs crash due to lack of disk space. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2003105 Title: rsyslog fills the root filesystem by spamming messages Status in rsyslog package in Ubuntu: New Bug description: Today, I lost some of my data. I had a file open in Vim, and lost it, since rsyslog quickly produced over 450GB on 1TB root filesystem within a day. It should correctly limit the log spam by default, but instead it creates its own log file. Since it is installed by other software, end user is surprised when is root filesystem is filled with useless messages. In my case the messages came from `snap` for desktop integration continuously restarting for unknown reasons. journald and `printk` limit rate of log spamming by default just to prevent data loss for the same reason. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: rsyslog (not installed) ProcVersionSignature: Ubuntu 5.15.0-57.63-lowlatency 5.15.74 Uname: Linux 5.15.0-57-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 18:37:49 2023 InstallationDate: Installed on 2022-11-08 (70 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.rsyslog: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2003105/+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 2003105] [NEW] rsyslog fills the root filesystem by spamming messages
Public bug reported: Today, I lost some of my data. I had a file open in Vim, and lost it, since rsyslog quickly produced over 450GB on 1TB root filesystem within a day. It should correctly limit the log spam by default, but instead it creates its own log file. Since it is installed by other software, end user is surprised when is root filesystem is filled with useless messages. In my case the messages came from `snap` for desktop integration continuously restarting for unknown reasons. journald and `printk` limit rate of log spamming by default just to prevent data loss for the same reason. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: rsyslog (not installed) ProcVersionSignature: Ubuntu 5.15.0-57.63-lowlatency 5.15.74 Uname: Linux 5.15.0-57-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 18:37:49 2023 InstallationDate: Installed on 2022-11-08 (70 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.rsyslog: [deleted] ** Affects: rsyslog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2003105 Title: rsyslog fills the root filesystem by spamming messages Status in rsyslog package in Ubuntu: New Bug description: Today, I lost some of my data. I had a file open in Vim, and lost it, since rsyslog quickly produced over 450GB on 1TB root filesystem within a day. It should correctly limit the log spam by default, but instead it creates its own log file. Since it is installed by other software, end user is surprised when is root filesystem is filled with useless messages. In my case the messages came from `snap` for desktop integration continuously restarting for unknown reasons. journald and `printk` limit rate of log spamming by default just to prevent data loss for the same reason. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: rsyslog (not installed) ProcVersionSignature: Ubuntu 5.15.0-57.63-lowlatency 5.15.74 Uname: Linux 5.15.0-57-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 18:37:49 2023 InstallationDate: Installed on 2022-11-08 (70 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.rsyslog: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2003105/+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 1978301] Re: Broken contact URL in German translation
On 2022-12-15 I uploaded apport 2.20.11-0ubuntu82.4 to jammy to fix this bug. -- 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/1978301 Title: Broken contact URL in German translation Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Jammy: Confirmed Bug description: Impact -- All German users (and all translations that use "%s." in their translation template) will get a broken URL link for bug reports against snaps (e.g. Firefox). Test Case - 1. Execute following command: LANGUAGE=de ubuntu-bug firefox 2. Click on the URL 3. A browser window should open and not display a 404 page Regression Potential Since there was no test case for converting text to HTML before this fix, there might be some URLs that will become broken by this fix. Original Description "LANGUAGE=de ubuntu-bug firefox" end up in a dialog saying: firefox wird durch einen von mozilla veröffentlichten Snap bereitgestellt. Für Hilfe gehen Sie über https://support.mozilla.org/kb/file-bug-report-or-feature-request- mozilla. The dot at the end is included in the URL link. The dot makes the URL link broken. The regular expression in gtk/apport-gtk for http URLs should become smarter. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1978301/+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 2002428] Re: Autopkgtest failure due to moved testcase
Looks like this was sponsored (thanks William!), unsubscribing the sponsors team. ** Changed in: coreutils (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2002428 Title: Autopkgtest failure due to moved testcase Status in coreutils package in Ubuntu: Fix Committed Bug description: In 9.1-1ubuntu1 (lunar), a testcase has been renamed from proc- selinux-segfault.sh to selinux-segfault.sh . This changes debian/tests/upstream to reflect the change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2002428/+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 1978301] Re: Broken contact URL in German translation
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apport (Ubuntu Jammy) Status: New => Confirmed -- 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/1978301 Title: Broken contact URL in German translation Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Jammy: Confirmed Bug description: Impact -- All German users (and all translations that use "%s." in their translation template) will get a broken URL link for bug reports against snaps (e.g. Firefox). Test Case - 1. Execute following command: LANGUAGE=de ubuntu-bug firefox 2. Click on the URL 3. A browser window should open and not display a 404 page Regression Potential Since there was no test case for converting text to HTML before this fix, there might be some URLs that will become broken by this fix. Original Description "LANGUAGE=de ubuntu-bug firefox" end up in a dialog saying: firefox wird durch einen von mozilla veröffentlichten Snap bereitgestellt. Für Hilfe gehen Sie über https://support.mozilla.org/kb/file-bug-report-or-feature-request- mozilla. The dot at the end is included in the URL link. The dot makes the URL link broken. The regular expression in gtk/apport-gtk for http URLs should become smarter. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1978301/+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 2002043] Re: Python extension modules get built using wrong compiler flags with python2
Thanks for looking into this. On python3, can we make sure if we are
looking into right output file?
>From your pasted output on Python3, I do see, there is -O2 but I see
from next command the query is against test.so file which seems
incorrect. From the compilation output, the file name when python3 is
used is test.cpython-38-aarch64-linux-gnu.so.
On my machine (Ubuntu 20.04) with Python3:-
ubuntu@ip-172-31-18-56:~/test$ python3 setup.py build_ext --inplace
running build_ext
building 'test' extension
creating build
creating build/temp.linux-aarch64-3.8
aarch64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g
-fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security
-g -fwrapv -O2 -g -fstack-protector-strong -Wformat -Werror=format-security
-Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.8 -c testmodule.c
-o build/temp.linux-aarch64-3.8/testmodule.o
creating build/lib.linux-aarch64-3.8
aarch64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions
-Wl,-Bsymbolic-functions -Wl,-z,relro -g -fwrapv -O2 -Wl,-Bsymbolic-functions
-Wl,-z,relro -g -fwrapv -O2 -g -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2
build/temp.linux-aarch64-3.8/testmodule.o -o
build/lib.linux-aarch64-3.8/test.cpython-38-aarch64-linux-gnu.so
copying build/lib.linux-aarch64-3.8/test.cpython-38-aarch64-linux-gnu.so ->
ubuntu@ip-172-31-18-56:~/test$ strings test.cpython-38-aarch64-linux-gnu.so |
grep -- -O
GNU C17 9.4.0 -mlittle-endian -mabi=lp64 -g -g -g -g -O2 -O2
-fstack-protector-strong -fwrapv -fstack-protector-strong -fPIC
-fasynchronous-unwind-tables -fstack-protector-strong -fstack-clash-protection
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/2002043
Title:
Python extension modules get built using wrong compiler flags with
python2
Status in python2.7 package in Ubuntu:
New
Bug description:
Compiling a Python extension using Python2 (Python 2.7.18) is making
use of wrong compiler flags, hence dropping required optimizations
when required. This is happening only when python2 is installed from
Ubuntu's repositories. By default, Python's distutils module uses
compiler and linker flags used to compile Python itself to be used to
compile extensions.
Steps to reproduce:
1) On Ubuntu 20.04, install python2 using apt package manager.
2) After successful installation, verify the CFLAGS variable from sysconfig
module. On my machine, the output is
Python 2.7.18 (default, Jul 1 2022, 12:27:04)
[GCC 9.4.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sysconfig
>>> sysconfig.get_config_var('CFLAGS')
'-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes
-Wdate-time -D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security '
3) Build a test extension module using python2 and verify the compilation
flags.
python2 setup.py build_ext --inplace
Output from below command is not matching with our expected above CFLAGS.
aarch64-linux-gnu-gcc -pthread -fno-strict-aliasing -Wdate-time
-D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security -fPIC
-I/usr/include/python2.7 -c testmodule.c -o
build/temp.linux-aarch64-2.7/testmodule.o
On further investigation, it looks like Ubuntu's specific patch applied on
libpython2.7-stdlib package is altering the original upstream implementation of
distutils/sysconfig.py code.
Package - https://packages.ubuntu.com/focal/libpython2.7-stdlib
Patch -
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
Below is the code block which is causing the issue, where the presence of
configure_cflags is modifying cflags. This code is result of ubuntu's patch and
doesn't come directly from upstream python implementation.
File - /usr/lib/python2.7/distutils/sysconfig.py
Part of code block:
elif configure_cflags:
cflags = ' '.join(str(x) for x in (basecflags, configure_cflags,
extra_cflags) if x)
ldshared = ldshared + ' ' + configure_cflags
I don't see problem on Python3 though we have extra code added from patch
there as well. Patch used on python3, is not modifying the cflags completely
and instead appending new flags to cflags.
On python3 (tested on Ubuntu 20.04)
File - /usr/lib/python3.8/distutils/sysconfig.py
Part of code block which doesn't alter cflags completely
elif configure_cflags:
cflags = cflags + ' ' + configure_cflags
ldshared = ldshared + ' ' + configure_cflags
Request to update the python2 patch to behave similar to what is
[Touch-packages] [Bug 1991761] Re: Backport packages for 22.04.2 HWE stack
At least from AMD's tests, backported mesa stack is working properly with RDNA3. Adjusting tag accordingly. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- 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/1991761 Title: Backport packages for 22.04.2 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-15 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in spirv-headers package in Ubuntu: Invalid Status in spirv-llvm-translator-14 package in Ubuntu: Invalid Status in spirv-llvm-translator-15 package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in libdrm source package in Jammy: Fix Committed Status in llvm-toolchain-15 source package in Jammy: Fix Committed Status in mesa source package in Jammy: Fix Committed Status in spirv-headers source package in Jammy: Fix Committed Status in spirv-llvm-translator-14 source package in Jammy: Fix Committed Status in spirv-llvm-translator-15 source package in Jammy: Fix Committed Bug description: [Impact The graphics HWE stack from kinetic needs to be backported for 22.04.2 directx-headers - build-dep of the new Mesa libdrm - build-dep of the new Mesa llvm-15 - new package in jammy - build-dep of the new Mesa mesa - new major release (22.2.x) - new HW support, like AMD RDNA3, Intel DG2 spirv-headers - needed by s-l-t-15 spirv-llvm-translator-14 - needed to bootstrap libclc from llvm spirv-llvm-translator-15 - needed for the actual libclc-15 after initial bootstrap Bootstrapping plan: - s-l-t-14 built from NEW - llvm-15 built with s-l-t-14 - s-l-t-15 built against llvm-15 - llvm-15 built again with s-l-t-15 -> mesa ready for building [Test case] Install the new mesa on various hw, see that everything still works like before or better. spirv-headers: - test reverse-build-deps that they still build Reverse-Build-Depends * glslang * intel-graphics-compiler * spirv-llvm-translator-14 * spirv-llvm-translator-15 * spirv-tools * vkbasalt * vkd3d * vulkan-validationlayers [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll backport the final stable release of 22.2.x in order to minimize the chance for those. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1991761/+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 2002994] Re: sshd_config makes some changes awkward
** Tags added: server-triage-discuss -- 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/2002994 Title: sshd_config makes some changes awkward Status in openssh package in Ubuntu: New Bug description: As distribted, the file sshd_config has apparently been modified from an upstream version -- those lines that are NOT comments. There is no good way for me to change any of them, even though there is a sshd_config.d directory for my changes. That is because the files in the sshd_config.d directory are invoked early, and the uncommented lines in the sshd_config file override them. I would have to modify the sshd_config file which defeats the purpose of having the directory. I suggest to adopt a method that I have seen elsewhere: put all of your changes in a file and put the file in the .d directory. Start the filename with something like '50' so that it can sort before or after any file contributed by the local admin. Keep the sshd_config file as you get it from upstream. This is, after all, the reason that the .d directories exist. In this way, admins do not have to modify distributed files, which avoids awkwardness when the package is updated. The same applies to ssh_config. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.2p1-4ubuntu0.5 ProcVersionSignature: Ubuntu 5.4.0-122.138-generic 5.4.192 Uname: Linux 5.4.0-122-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Jan 16 06:29:16 2023 SourcePackage: openssh UpgradeStatus: Upgraded to focal on 2021-02-19 (696 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2002994/+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 2003099] [NEW] Flickering when minimizing
Public bug reported: When minimizing windowed applications, the animation sometimes jumps wildly around, mostly to the top left corner of the screen. I found a temporary workaround with a config file in /etc/X11/xorg.conf.d/20-intel.conf, which supposedly has some other unwanted effects on other programs. Thanks for your help!! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..3c.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.60.11 Wed Nov 23 23:04:03 UTC 2022 GCC version: 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: Tue Jan 17 17:12:59 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo WhiskeyLake-U GT2 [UHD Graphics 620] [17aa:2283] Subsystem: Lenovo GP108M [GeForce MX250] [17aa:2283] InstallationDate: Installed on 2023-01-02 (14 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20N4002VGE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=72ad0f02-9e2a-4714-8427-9372619f5f04 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2020 dmi.bios.release: 1.68 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET90W (1.68 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N4002VGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnLENOVO:bvrN2IET90W(1.68):bd07/06/2020:br1.68:efr1.17:svnLENOVO:pn20N4002VGE:pvrThinkPadT590:rvnLENOVO:rn20N4002VGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20N4_BU_Think_FM_ThinkPadT590: dmi.product.family: ThinkPad T590 dmi.product.name: 20N4002VGE dmi.product.sku: LENOVO_MT_20N4_BU_Think_FM_ThinkPad T590 dmi.product.version: ThinkPad T590 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.3 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.3-2ubuntu2.5 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 -- 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/2003099 Title: Flickering when minimizing Status in xorg package in Ubuntu: New Bug description: When minimizing windowed applications, the animation sometimes jumps wildly around, mostly to the top left corner of the screen. I found a temporary workaround with a config file in /etc/X11/xorg.conf.d/20-intel.conf, which supposedly has some other unwanted effects on other programs. Thanks for your help!! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..3c.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.60.11 Wed Nov 23 23:04:03 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13]
[Touch-packages] [Bug 2003098] [NEW] whoopsie-upload-all: package specific hooks not run
Public bug reported: Commit f8edc7280d492e710218c193e53542f1f86cfa91 (for fixing bug #1983481) introduces a regression: The package specific hooks are not run in whoopsie-upload-all because add_hooks_info is called with ui=None. add_hooks_info will raise an AssertionError for ui=None. ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- 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/2003098 Title: whoopsie-upload-all: package specific hooks not run Status in apport package in Ubuntu: New Bug description: Commit f8edc7280d492e710218c193e53542f1f86cfa91 (for fixing bug #1983481) introduces a regression: The package specific hooks are not run in whoopsie-upload-all because add_hooks_info is called with ui=None. add_hooks_info will raise an AssertionError for ui=None. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2003098/+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 1926139] Re: dhclient: thread concurrency race leads to DHCPOFFER packets not being received
** Tags removed: sts-sponsor -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1926139 Title: dhclient: thread concurrency race leads to DHCPOFFER packets not being received Status in bind9-libs package in Ubuntu: Fix Released Status in isc-dhcp package in Ubuntu: Invalid Status in bind9-libs source package in Focal: In Progress Status in bind9-libs source package in Jammy: In Progress Bug description: [Impact] Occasionally, during instance boot or machine start-up, dhclient will attempt to acquire a dhcp lease and fail, leaving the instance with no IP address and making it unreachable. This happens about once every 100 reboots on bare metal, or Chris Patterson in comment #2 describes it as affecting between ~0.3% to 2% of deployments on Microsoft Azure. Azure uses dhclient called from cloud-init instead of systemd-networkd, and this is causing issues with larger deployments. The logs of an affected dhclient produce the following: Listening on LPF/enp1s0/52:54:00:1c:d7:00 Sending on LPF/enp1s0/52:54:00:1c:d7:00 Sending on Socket/fallback DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 interval 3 (xid=0xd222950f) DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 interval 5 (xid=0xd222950f) ... (omitting 20 similar lines) ... DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 interval 13 (xid=0xd222950f) DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 interval 8 (xid=0xd222950f) DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 interval 6 (xid=0xd222950f) No DHCPOFFERS received. No working leases in persistent database - sleeping. Full log: https://paste.ubuntu.com/p/8yBfw2KR5h/ Log of a working run: https://paste.ubuntu.com/p/N3ZgqrxyQD/ The bizarre thing is when you tcpdump dhclient, we see all DHCPDISOVER packets being replied to with DHCPOFFER packets, but the got_one() callback is never called, dhclient does not read these DHCPOFFER packets, and continues sending DHCPDISCOVER packets. Once it reaches 25 DHCPDISCOVER packets sent, it gives up. tcpdump: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1926139/+attachment/5641810/+files/test.pcap Screenshot of Wireshark: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1926139/+attachment/5641811/+files/Screenshot_2023-01-17-16-14-21_1920x1200%250A1920x1080%250A1920x1080.png This behaviour led several bug reporters to believe it was a kernel issue, with the kernel not pushing DHCPOFFER packets to dhclient. This is not the case, the actual problem is dhclient containing a thread concurrency race condition, and when the race occurs, the read socket is closed prematurely, and dhclient does not read any of the DHCPOFFER replies. The full explanation is in the "Other Info" section, but the fix for this is to change bind9-libs from being built multithreaded, back to single threaded as intended by dhclient maintainers. In Focal and Jammy, isc-dhcp links against bind9 libraries provided in bind9-libs, while in Kinetic onward isc-dhcp has an in-tree bind9 library it uses, which is already configured properly to --disable- threads. Change the Focal and Jammy bind9-libs to --disable-threads and update symbol files to reflect the library is single threaded again. [Testcase] Start a fresh Focal or Jammy instance. Download and set executable test-parallel.sh, and edit some lines: 1) wget https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1926139/+attachment/5593045/+files/test-parallel.sh 2) chmod +x test-parallel.sh 3) vim test-parallel.sh Change iface="enp5s0" to your interface, likely iface="enp1s0". Comment out the line "# cp bionic-dhclient $workdir/dhclient". 4) sudo ./test-parallel.sh After five minutes, if you issue reproduces, you will see "TEST FAILED". You can watch the output with: 5) cat /tmp/dhclient-* | less Next, for instrumented runs, you need to build dhclient from source. 1) sudo apt install build-essential devscripts 2) apt source isc-dhcp 3) sudo apt build-dep isc-dhcp 4) cd isc-dhcp Apply the below patch: https://paste.ubuntu.com/p/hGsssrVyG4/ 5) patch -p1 < ~/patch.patch 6) debuild -b -uc -us 7) cd .. 8) sudo dpkg -i isc-dhcp-client-* 9) sudo ./test-parallel.sh 10) cat /tmp/dhclient-* | less Look for the race, as described in "Other Info", namely: mruffell: registering with socket manager mruffell: callback called mruffell: omapi object is NULL mruffell: omapi object is NULL mruffell: Adding obj to linked list mruffell: Obj added to list The issue has reproduced. If you install the test package from the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf337873-test Instructions to install (on a Focal or Jammy system): 1) sudo add-apt-repository
[Touch-packages] [Bug 2000551] Re: [System Fonts] Replace default sinhala font from LKLUG to Noto
On 2023-01-17 08:48, Aurora wrote: >> Or they can simply do: sudo apt install fonts-noto-core > > but flatpak users said that flatpak apps still use LKLUG, how to > solve that problem? I don't know anything about Flatpak, sorry. Can't tell to which extent Flatpak honors fontconfig. Maybe try Ask Ubuntu or some Flatpak oriented support resource. I know that the Firefox snap provided in Ubuntu honors the configuration in /etc/fonts/conf.d, and so do conventionally installed applications too. > if a sinhala language speaker or foreigner keeps only english > (default) or other language in the system and when they view a > sinhala web page using a web browser or use a text editor to edit > something, it looks like ubuntu still uses LKLUG as the default > font. That's not what I see. I just made an English install of the coming Ubuntu 23.04 in VirtualBox and updated the packages. Then I * Opened a terminal and run: sudo apt install fonts-noto-core * Opened Firefox, went to https://si.wikipedia.org, and found that the page was rendered using Noto Sans Sinhala and Noto Serif Sinhala — not LKLUG. > should i propose a small font package like LKLUG? What would the point be with doing so? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2000551 Title: [System Fonts] Replace default sinhala font from LKLUG to Noto Status in language-selector package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Won't Fix Status in language-selector source package in Jammy: Fix Committed Status in language-selector source package in Kinetic: Fix Committed Bug description: [ Impact ] The current default font for Sinhala (LKLUG) is unmaintained and comes with issues. Noto offers Sinhala fonts with significantly higher quality. fonts-lklug-sinhala is pulled by quite a few meta packages. Instead of changing that, the proposed change makes fontconfig give Noto Sans Sinhala respective Noto Serif Sinhala higher precedence than LKLUG, and that — together with installation of fonts-noto-core — seems to be sufficient to achieve the desired result. [ Test Plan ] * Install language-selector-[common,gnome] from [jammy,kinetic]-proposed. * Open Language Support and install the Sinhala language. * Open a terminal window and run this command: fc-match -a | grep -E 'LKLUG|Sinhala' * Confirm that Noto Sans Sinhala is listed before LKLUG. * Close Firefox and re-open it. * Visit e.g. https://si.wikipedia.org and confirm the improvement. (Also I (Gunnar), who don't speak Sinhala, notice a remarkable difference.) [ Where problems could occur ] No real problem in sight. Some Sinhala speaking users with fonts-noto- core installed will indeed see a surprise change when it starts to render Sinhala via Noto fonts instead of LKLUG. But that surprise ought to make them happy. :) Please note Robie Basak's warning about the changed font metrics in comment #7, though. [ Original description ] **What's the problem?** Currently ubuntu comes with LKLUG font for sinhala (si). it's not clear. e.g. we cannot recognize vowel signs and read websites using that font. We can change it manually but such changes do not apply to some applications or application types e.g. snap apps etc. LKLUG (last active: 2012) no one maintain it now. https://web.archive.org/web/202200*/http://www.lug.lk/ http://www.lug.lk/fonts/lklug **What expected to happen?** We would like to see Noto serif sinhala as the default font for sinhala language https://fonts.google.com/noto/specimen/Noto+Serif+Sinhala [Highlighs: clear (readable), thin, takes less space than sans sinhala] If noto sans is more suitable for ubuntuOS, you can add noto sans sinhala https://fonts.google.com/noto/specimen/Noto+Sans+Sinhala [Highlighs: clear (readable), thick, takes more space than serif sinhala] **Additional details** Screenshots (see the difference: LKLUG/Noto) LKLUG https://i.ibb.co/nbHM5Mw/lklug.jpg Noto Sinhala https://i.ibb.co/k9dbtYb/noto.jpg If you need more examples or clarifications, please add a comment Random posts 1. https://groups.google.com/g/Sinhala-Unicode/c/LYxuJ44dY3g 2. https://twitter.com/thilinag/status/1598707165920825344#m (LKLUG bug with some apps) 3. https://www.reddit.com/r/srilanka/comments/nzpl9p/change_sinhala_font_in_ubuntu/ Also, some developers already have designed tools, scripts for that problem however many people do not try to find these scripts and switch to other OS 1. https://github.com/IMS94/UbuntuSinhalaFont (developer: PMC chair @apache) 2. https://gist.github.com/thilinag/66577033fafd00c3dfdaa898c2478c79 3. https://github.com/hankyoTutorials/linux-system-sinhala-font-changer Please review details, screenshots and posts. This is not a personal
[Touch-packages] [Bug 1998765] Re: libnl3 3.4.0 doesn't work with WCN3980
Hello Robert, or anyone else affected, Accepted libnl3 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libnl3/3.4.0-1ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libnl3 (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1998765 Title: libnl3 3.4.0 doesn't work with WCN3980 Status in OEM Priority Project: New Status in OEM Priority Project focal series: New Status in libnl3 package in Ubuntu: Fix Released Status in libnl3 source package in Focal: Fix Committed Status in libnl3 source package in Jammy: Invalid Bug description: [ Impact ] When testing Qualcomm qcs410 with WCN3980 with 20.04 and UC20, WCN3980 is not able connect to an AP. However, with the libnl3 (3.5.0) from BSP, WCN3980 can work correctly. After bisecting the commits from 3.4.0 to 3.5.0, this commit[1] is identified as the root cause. According to the commit, the "NLA_F_NESTED" flag should be set for kernel later than 5.2. [ Test Plan ] Verify with the updated version, the WIFI module can: 1. scan WIFI networks 2. connect to an available network 3. access to the connected network [ Where problems could occur ] 1. kernel versions without NLA_F_NESTED flag defined This flag is introduced before Linux kernel v5 (checked v3.x and v4.x have it). It would not be a problem for an older kernel to understand/work with this change. Since the GA kernel is 5.4, so a generic image would still work. 2. Drivers don't use the NESTED flag. According to hui.wang's input, this change should not affect drivers which don't use the NESTED flag. But, it'd be better to cover more Wifi modules. [ Other Info ] 22.04 is using libnl3 3.0.5-0.1, so only 20.04 needs this patch. [1] https://github.com/thom311/libnl/commit/7de65a051fb37ece16f896a7385073274b77a133 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998765/+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
