[Touch-packages] [Bug 2002349] Re: I powered off and when I turned my computer on this hapened
Setting the bug to Invalid because we know the cause of the "stuck at 640x480". Separate to that it does look like some updates caused this by breaking the previously installed Nvidia driver but I can't find much detail here as to what went wrong. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid ** Summary changed: - I powered off and when I turned my computer on this hapened + Stuck at 640x480. No Nvidia driver anymore -- 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/2002349 Title: Stuck at 640x480. No Nvidia driver anymore Status in Ubuntu: Invalid Bug description: It's stuck at 640x480 and I can barely do anything at all I'm using Ubuntu 20.04 I cannot even update my computer ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-57.63~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 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: Mon Jan 9 14:36:01 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rtl882bu, 5.8.7.1, 5.15.0-57-generic, x86_64: installed rtl88x2bu, 5.8.7.1, 5.13.0-30-generic, x86_64: installed rtl88x2bu, 5.8.7.1, 5.15.0-57-generic, x86_64: installed (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] [19da:2476] InstallationDate: Installed on 2023-01-08 (1 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-57-generic root=UUID=9456410b-fb68-463f-b197-a8e997ea4477 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-I dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd03/07/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-I:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer 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.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.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-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2002349/+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 2002349] Re: I powered off and when I turned my computer on this hapened
Thanks for the bug report. It appears you don't have a working graphics driver installed. Please open the 'Additional Drivers' app and use it to install an Nvidia driver. -- 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/2002349 Title: Stuck at 640x480. No Nvidia driver anymore Status in Ubuntu: Invalid Bug description: It's stuck at 640x480 and I can barely do anything at all I'm using Ubuntu 20.04 I cannot even update my computer ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-57.63~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 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: Mon Jan 9 14:36:01 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rtl882bu, 5.8.7.1, 5.15.0-57-generic, x86_64: installed rtl88x2bu, 5.8.7.1, 5.13.0-30-generic, x86_64: installed rtl88x2bu, 5.8.7.1, 5.15.0-57-generic, x86_64: installed (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] [19da:2476] InstallationDate: Installed on 2023-01-08 (1 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-57-generic root=UUID=9456410b-fb68-463f-b197-a8e997ea4477 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-I dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd03/07/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-I:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer 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.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.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-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2002349/+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 2002321] Re: computer is too slow.
Thanks for the bug report. The main problem I can see here is that you have the kernel graphics driver in debug mode. To fix that you will need to remove "drm.debug=0xe plymouth:debug" from /etc/default/grub and then run: sudo update-grub and reboot. If that doesn't fix the problem then I would next recommend upgrading to Ubuntu 22.04.1 which is much faster. You also seem to be running an unsupported kernel that is actually older than the official kernel for Ubuntu 20.04. Fixing these problems that you seem to have created for yourself is a little bit complicated so if you are not very technical then I suggest the simplest solution is: 1. Backup all your data to external drives. 2. Reinstall from scratch using Ubuntu 22.04.1: https://ubuntu.com/download/desktop ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2002321 Title: computer is too slow. Status in Ubuntu: Incomplete Bug description: i dont know much about those computer term,but if could you help me somehow i would be very greatfull. thanx A.B. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.4.0-050400-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Jan 9 16:11:37 2023 DistUpgraded: 2022-12-25 23:43:14,353 INFO cache.commit() DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:064b] InstallationDate: Installed on 2018-04-19 (1726 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Acer TravelMate P253 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-050400-generic root=UUID=a81ad045-d2f8-4909-8aef-d7239d261ada ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2022-12-25 (14 days ago) dmi.bios.date: 12/16/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: BA51_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.21 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.21:bd12/16/2013:svnAcer:pnTravelMateP253:pvrV2.21:rvnAcer:rnBA51_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.21: dmi.product.family: Type1Family dmi.product.name: TravelMate P253 dmi.product.sku: TravelMate P253_064B_V2.21 dmi.product.version: V2.21 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.110-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sat Dec 1 18:03:02 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2002321/+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 1283309] Re: bash built-in read timeout (-t) doesn't work
[Expired for bash (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bash (Ubuntu) Status: Incomplete => Expired -- 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/1283309 Title: bash built-in read timeout (-t) doesn't work Status in bash package in Ubuntu: Expired Bug description: This should timeout after 2 seconds (based on bash man page) but it doesn't: #read -t 2 test (waits infinitely, only terminates after pressing [enter] or ctrl-C, etc..) bash --version: GNU bash, version 4.2.25(1)-release (x86_64-pc-linux-gnu) Installed bash package version: 4.2-2ubuntu2.1 $ lsb_release -rd Description: Ubuntu 12.04.4 LTS Release: 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1283309/+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 2000739] Re: Window actions (like maximize) no more work in wayland for QEMU using GTK backend once the guest UI is intialized.
** No longer affects: wayland (Ubuntu) ** Tags added: focal session wayland ** Tags removed: session ** Tags added: wayland-session ** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2000739 Title: Window actions (like maximize) no more work in wayland for QEMU using GTK backend once the guest UI is intialized. Status in qemu package in Ubuntu: Confirmed Bug description: Window actions (like maximize) no more work in wayland for QEMU using GTK backend once the guest UI is intialized. This can be seen by running an installed or even a trial Ubuntu from an ISO like: $ qemu-system-x86_64 \ -boot d \ -cdrom ubuntu-22.04.1-desktop-amd64.iso \ -m 4096M \ -machine type=q35,accel=kvm \ -cpu host \ -smp 2 \ -device qxl-vga The GTK UI of qemu has a feature called "fullscreen" which disables the screen decorations and sets the window to maximize. The decorations go away, but maximize doesn't work. The following details were found so far: - running with GDK_BACKEND=x11 works - using sdl instead of gtk backend works - using the old qemu of Focal, or the newest from upstream git in jammy all fails (no qemu change AFAICS) - host UI widgets (the square at the window top) do not work either - hotkeys (super-up) do not work either It seems that once the guest has enabled the desktop something changes and the maximize/minimize/... actions are no more processed. Not sure were to debug next in regard to the gnome/wayland UI handling of this - any idea? P.S. We can reproduce this in git builds of qemu, so we can debug of modify the code as needed. The code for this is mostly in [1] [1]: https://gitlab.com/qemu-project/qemu/-/blob/master/ui/gtk.c --- original report --- Running QEMU version 4.2.1 on Ubuntu 20.04 via qemu-system-x86_64 \ -boot d \ -cdrom ubuntu-22.04.1-desktop-amd64.iso \ -m 4096M \ -machine type=q35,accel=kvm \ -cpu host \ -smp 2 \ -device qxl-vga and pressing ctrl+alt+f after booting the Ubuntu 22.04 live ISO and adjusting the display resolution to match the native resolution, works as expected, i.e., the VM screen is correctly displayed in fullscreen. However, after running the same command for QEMU version 6.2.0 on Ubuntu 22.04 and pressing ctrl+alt+f after making the resolution adjustment, yields a fullscreen view where the space occupied by the GNOME top bar (top panel with date in center) of the host is not used. The top bar itself is not visible but instead the purple background is shown where the top bar resides. The problem also occurs when replacing '-device qxl-vga' by '-device VGA,vgamem_mb=64'. The problem however does not occur when using '-device virtio-vga'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2000739/+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 2002349] Re: I powered off and when I turned my computer on this hapened
** 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/2002349 Title: I powered off and when I turned my computer on this hapened Status in xorg package in Ubuntu: New Bug description: It's stuck at 640x480 and I can barely do anything at all I'm using Ubuntu 20.04 I cannot even update my computer ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-57.63~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 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: Mon Jan 9 14:36:01 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rtl882bu, 5.8.7.1, 5.15.0-57-generic, x86_64: installed rtl88x2bu, 5.8.7.1, 5.13.0-30-generic, x86_64: installed rtl88x2bu, 5.8.7.1, 5.15.0-57-generic, x86_64: installed (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] [19da:2476] InstallationDate: Installed on 2023-01-08 (1 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-57-generic root=UUID=9456410b-fb68-463f-b197-a8e997ea4477 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-I dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd03/07/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-I:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer 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.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.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-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2002349/+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 2002349] [NEW] I powered off and when I turned my computer on this hapened
You have been subscribed to a public bug: It's stuck at 640x480 and I can barely do anything at all I'm using Ubuntu 20.04 I cannot even update my computer ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-57.63~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 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: Mon Jan 9 14:36:01 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rtl882bu, 5.8.7.1, 5.15.0-57-generic, x86_64: installed rtl88x2bu, 5.8.7.1, 5.13.0-30-generic, x86_64: installed rtl88x2bu, 5.8.7.1, 5.15.0-57-generic, x86_64: installed (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] [19da:2476] InstallationDate: Installed on 2023-01-08 (1 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-57-generic root=UUID=9456410b-fb68-463f-b197-a8e997ea4477 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-I dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd03/07/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-I:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer 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.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.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-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal resolution ubuntu -- I powered off and when I turned my computer on this hapened https://bugs.launchpad.net/bugs/2002349 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1917887] Re: Network Manager OpenVPN nested connections fail to setup routes correctly
** Changed in: openvpn Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1917887 Title: Network Manager OpenVPN nested connections fail to setup routes correctly Status in OpenVPN: Fix Released Status in network-manager package in Ubuntu: Triaged Status in openvpn package in Ubuntu: Invalid Bug description: Setup: Host lan: 192.168.0.238/24 Host Default gw: 192.168.0.1 ip route: default via 192.168.0.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 Primary OpenVPN (check "Use this connection only for resources on its network"): server ip: public a.b.c.d OpenVPN Tunnel: 192.168.1.0/24 routes pushed: 192.168.100.0/24 First VPN works OK: default via 192.168.0.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 192.168.0.1 dev eno1 proto static scope link metric 100 192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 Secondary OpenVPN (check "Use this connection only for resources on its network"): server ip: private 192.168.100.10 OpenVPN Tunnel: 192.168.20.0/24 routes pushed: 192.168.200.0/24 Second VPN Connect OK, routing table is wrong: default via 192.168.0.1 dev eno1 proto dhcp metric 100 192.168.200.0/24 via 192.168.20.1 dev tun1 192.168.20.0/24 dev tun1 proto kernel scope link src 192.168.20.59 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 192.168.0.1 dev eno1 proto static scope link metric 100 192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 192.168.100.10 via 192.168.0.1 dev eno1 proto static metric 100 <- this is wrong, the openVPN#2 Gateway is not on the local lan Correct routing table using "sudo /usr/sbin/openvpn /path/to/config.openvpn" (same a Network Manager) default via 192.168.0.1 dev eno1 proto dhcp metric 100 192.168.200.0/24 via 192.168.20.1 dev tun1 192.168.20.0/24 dev tun1 proto kernel scope link src 192.168.20.59 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 192.168.0.1 dev eno1 proto static scope link metric 100 192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 It seems that Network Manager add a wrong additional route not added by the openvpn bin: 192.168.100.10 via 192.168.0.1 dev eno1 proto static metric 100 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openvpn 2.4.7-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Mar 5 12:44:39 2021 InstallationDate: Installed on 2021-02-19 (13 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: openvpn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/openvpn/+bug/1917887/+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 2002355] [NEW] package libssl-dev 3.0.2-0ubuntu1.7 [modified: usr/include/openssl/aes.h usr/include/openssl/asn1.h usr/include/openssl/asn1_mac.h usr/include/openssl/asn1t.h usr/
Public bug reported: openssl lib ProblemType: Package DistroRelease: Ubuntu 22.04 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 AptOrdering: libssl-dev:i386: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Jan 10 00:43:30 2023 DpkgTerminalLog: Preparing to unpack .../libssl-dev_3.0.2-0ubuntu1.7_i386.deb ... Unpacking libssl-dev:i386 (3.0.2-0ubuntu1.7) over (1.0.1f-1ubuntu2.27) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/libssl-dev_3.0.2-0ubuntu1.7_i386.deb (--unpack): trying to overwrite shared '/usr/include/openssl/aes.h', which is different from other instances of package libssl-dev:i386 ErrorMessage: trying to overwrite shared '/usr/include/openssl/aes.h', which is different from other instances of package libssl-dev:i386 InstallationDate: Installed on 2023-01-03 (5 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: openssl UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2002355 Title: package libssl-dev 3.0.2-0ubuntu1.7 [modified: usr/include/openssl/aes.h usr/include/openssl/asn1.h usr/include/openssl/asn1_mac.h usr/include/openssl/asn1t.h usr/include/openssl/bio.h usr/include/openssl/blowfish.h usr/include/openssl/bn.h usr/include/openssl/buffer.h usr/include/openssl/camellia.h usr/include/openssl/cast.h usr/include/openssl/cmac.h usr/include/openssl/cms.h usr/include/openssl/comp.h usr/include/openssl/conf.h usr/include/openssl/conf_api.h usr/include/openssl/crypto.h usr/include/openssl/des.h usr/include/openssl/dh.h usr/include/openssl/dsa.h usr/include/openssl/dtls1.h usr/include/openssl/e_os2.h usr/include/openssl/ebcdic.h usr/include/openssl/ec.h usr/include/openssl/ecdh.h usr/include/openssl/ecdsa.h usr/include/openssl/engine.h usr/include/openssl/err.h usr/include/openssl/evp.h usr/include/openssl/hmac.h usr/include/openssl/lhash.h usr/include/openssl/md4.h usr/include/openssl/md5.h usr/include/openssl/modes.h usr/include/openssl/obj_mac.h usr/include/openssl/objects.h usr/include/openssl/ocsp.h usr/include/openssl/opensslv.h usr/include/openssl/ossl_typ.h usr/include/openssl/pem.h usr/include/openssl/pem2.h usr/include/openssl/pkcs12.h usr/include/openssl/pkcs7.h usr/include/openssl/rand.h usr/include/openssl/rc2.h usr/include/openssl/rc4.h usr/include/openssl/ripemd.h usr/include/openssl/rsa.h usr/include/openssl/safestack.h usr/include/openssl/seed.h usr/include/openssl/sha.h usr/include/openssl/srp.h usr/include/openssl/srtp.h usr/include/openssl/ssl.h usr/include/openssl/ssl2.h usr/include/openssl/ssl3.h usr/include/openssl/stack.h usr/include/openssl/symhacks.h usr/include/openssl/tls1.h usr/include/openssl/ts.h usr/include/openssl/txt_db.h usr/include/openssl/ui.h usr/include/openssl/whrlpool.h usr/include/openssl/x509.h usr/include/openssl/x509_vfy.h usr/include/openssl/x509v3.h] failed to install/upgrade: trying to overwrite shared '/usr/include/openssl/aes.h', which is different from other instances of package libssl-dev:i386 Status in openssl package in Ubuntu: New Bug description: openssl lib ProblemType: Package DistroRelease: Ubuntu 22.04 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 AptOrdering: libssl-dev:i386: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Jan 10 00:43:30 2023 DpkgTerminalLog: Preparing to unpack .../libssl-dev_3.0.2-0ubuntu1.7_i386.deb ... Unpacking libssl-dev:i386 (3.0.2-0ubuntu1.7) over (1.0.1f-1ubuntu2.27) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/libssl-dev_3.0.2-0ubuntu1.7_i386.deb (--unpack): trying to overwrite shared '/usr/include/openssl/aes.h', which is different from other instances of package libssl-dev:i386 ErrorMessage: trying to overwrite shared '/usr/include/openssl/aes.h', which is different from other instances of package libssl-dev:i386 InstallationDate: Installed on 2023-01-03 (5 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions:
[Touch-packages] [Bug 1873519] Re: Package should own adduser.conf
** Changed in: adduser (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to adduser in Ubuntu. https://bugs.launchpad.net/bugs/1873519 Title: Package should own adduser.conf Status in adduser package in Ubuntu: Fix Released Status in adduser package in Debian: Fix Released Bug description: /etc/adduser.conf isn't recorded as belonging to the package, but this is addressed easily by adding adduser.conf to the debian/install file. adduser.conf is generated by a postinst script, so it isn't covered by the normal install stuff. Regardless, it seems to become registered by just adding it to the install file on the same line as deluser.conf, which is already there. I often customize deployments using the config-package-dev extension to Debhelper, but this relies on package ownership to manage config files. Hopefully this is a trivial suggestion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1873519/+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 1998893] Re: NV reverse prime HDMI has no output
** Changed in: mesa (Ubuntu Jammy) Status: Fix Committed => In Progress -- 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/1998893 Title: NV reverse prime HDMI has no output Status in OEM Priority Project: New Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: In Progress Bug description: [Impact] The X failed to load glamoregl module on Dell's new platforms, the module is needed by NV dGPU. 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) LoadModule: "glamoregl" 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Loading /usr/lib/xorg/modules/libglamoregl.so 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Module glamoregl: vendor="X.Org Foundation" 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: compiled for 1.21.1.3, module version = 1.0.1 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: ABI class: X.Org ANSI C Emulation, version 0.4 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: MESA: warning: Driver does not support the 0xa78b PCI ID. 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): Refusing to try glamor on llvmpipe 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): glamor initialization failed [Fix] The upstream PR added missing ID for the platforms. https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/16320/ https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/17569/ After creating the test build to include the PR above, ODM verified passed on those platform. [Test case] Install fixed package on the systems, check that display works. [Where things could go wrong] Although one commit drops a couple of pci-id's, they were already dropped from the jammy kernel for lp1990242 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998893/+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 1998893] Re: NV reverse prime HDMI has no output
I think this bug/SRU snowballed. Let's take a step back. It started with fixing two bugs: this one, and bug #1972977. At some point later, #1972977 was deemed not really fixed[1], and was dropped in the 0ubuntu0.3 upload[2]. That upload failed to build in jammy-proposed on arm64[3] and amd64[4]. It was deemed to be a problem introduced by some other jammy-proposed upload (unclear which one). A new upload was made to jammy unapproved[5] (still missing an update- maintainer run, btw), stating: Changes: mesa (22.0.5-0ubuntu0.4) jammy; urgency=medium . * Add a patch to build with a newer directx-headers. (LP: #1998893) . mesa (22.0.5-0ubuntu0.3) jammy; urgency=medium . * crocus-fix-leak-in-query-code.patch: Drop the patch so the other fix can get through to updates. . mesa (22.0.5-0ubuntu0.2) jammy; urgency=medium . * crocus-fix-leak-in-query-code.patch: Fix gnome-shell crashing on older Intel hw. (LP: #1972977) * patches: Update pci-id's for ADL-S/RPL-S. (LP: #1998893) That is quite a big patch in an area I know nothing about. My concerns are: - shouldn't we have a separate bug for the FTBFS? This bug here is about PCI IDs. - what is the other package in jammy proposed that is breaking this build? Must it be released at the same time as mesa? - the original PR[6] mentioned in the DEP3 header of the FTBFS patch is huge and complex, is that (and the backport done here) really the minimal fix for the FTBFS? - what are the other changes incurring via this patch, now the the build is fixed? What else is changing? What is the risk analysis of that change? I feel there is a lot of missing information, but it could just be because I'm not familiar with mesa and the graphic/3d stack. So I prefer to leave this review for another SRU team member, but thought I should leave this comment here instead of just "disappearing" :) 1. https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1972977/comments/15 2. https://launchpad.net/ubuntu/+source/mesa/22.0.5-0ubuntu0.3 3. https://launchpad.net/ubuntu/+source/mesa/22.0.5-0ubuntu0.3/+build/25458695 4. https://launchpad.net/ubuntu/+source/mesa/22.0.5-0ubuntu0.3/+build/25458694 5. https://launchpadlibrarian.net/645131833/mesa_22.0.5-0ubuntu0.4_source.changes 6. https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/15751/diffs -- 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/1998893 Title: NV reverse prime HDMI has no output Status in OEM Priority Project: New Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: In Progress Bug description: [Impact] The X failed to load glamoregl module on Dell's new platforms, the module is needed by NV dGPU. 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) LoadModule: "glamoregl" 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Loading /usr/lib/xorg/modules/libglamoregl.so 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Module glamoregl: vendor="X.Org Foundation" 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: compiled for 1.21.1.3, module version = 1.0.1 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: ABI class: X.Org ANSI C Emulation, version 0.4 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: MESA: warning: Driver does not support the 0xa78b PCI ID. 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): Refusing to try glamor on llvmpipe 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): glamor initialization failed [Fix] The upstream PR added missing ID for the platforms. https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/16320/ https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/17569/ After creating the test build to include the PR above, ODM verified passed on those platform. [Test case] Install fixed package on the systems, check that display works. [Where things could go wrong] Although one commit drops a couple of pci-id's, they were already dropped from the jammy kernel for lp1990242 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998893/+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 1873519] Re: Package should own adduser.conf
** Bug watch added: Debian Bug tracker #541620 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541620 ** Also affects: adduser (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541620 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to adduser in Ubuntu. https://bugs.launchpad.net/bugs/1873519 Title: Package should own adduser.conf Status in adduser package in Ubuntu: Fix Released Status in adduser package in Debian: Unknown Bug description: /etc/adduser.conf isn't recorded as belonging to the package, but this is addressed easily by adding adduser.conf to the debian/install file. adduser.conf is generated by a postinst script, so it isn't covered by the normal install stuff. Regardless, it seems to become registered by just adding it to the install file on the same line as deluser.conf, which is already there. I often customize deployments using the config-package-dev extension to Debhelper, but this relies on package ownership to manage config files. Hopefully this is a trivial suggestion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1873519/+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 1795278] Re: software-properties-{qt, kde} attempts to use KUrl but it doesn't exist
This is still occuring in Lubuntu Lunar. ** Tags added: lunar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1795278 Title: software-properties-{qt,kde} attempts to use KUrl but it doesn't exist Status in software-properties package in Ubuntu: Triaged Status in software-properties source package in Focal: Triaged Status in software-properties source package in Jammy: Triaged Status in software-properties source package in Kinetic: Triaged Bug description: Release: Kubuntu 18.04 Version: 0.96.24.32.1 When clicking the "Import Key" button in the "Authentication" section of the panel it throws this error: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/kde/SoftwarePropertiesKDE.py", line 667, in add_key_clicked url = KUrl.fromPath(home) NameError: name 'KUrl' is not defined While this doesn't crash the program it causes nothing to happen when clicking the button. Running the program in a terminal reveals the error being printed to stderr. After debugging it appears KUrl doesn't exist anywhere and I'm not sure if's a python module that has changed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1795278/+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 1998207] Re: netplan network-manager plugin tries to save temporary connections
Unfortunately this is still happening with the patch from comment #3. In fact I do not even need to create a VPN connection for this. If I install easy-openvpn-server: $ snap install easy-openvpn-server it creates two tun devices (tun0 and tun1) that can be seen with "ip address" command. That makes NM create the corresponding devices and connections: /ssh:ubuntu@localhost#8022: $ /snap/bin/network-manager.nmcli c NAME UUID TYPE DEVICE netplan-ens3 bec3d02a-c9e5-3283-92ab-ee43a4246c85 ethernet ens3 tun0 edc2d2e1-b126-475d-8d5b-1a5b3bfd43d3 tun tun0 tun1 2945f4f4-2d44-4a61-83b4-cee73fd81129 tun tun1 /ssh:ubuntu@localhost#8022: $ /snap/bin/network-manager.nmcli d DEVICE TYPE STATE CONNECTION ens3ethernet connected netplan-ens3 tun0tun connected (externally) tun0 tun1tun connected (externally) tun1 lo loopback unmanaged but unfortunately these connections are still written as static connections in /etc/netplan/. And when I reboot, I see 4 of them: /ssh:ubuntu@localhost#8022: $ /snap/bin/network-manager.nmcli c NAME UUID TYPE DEVICE netplan-ens3 bec3d02a-c9e5-3283-92ab-ee43a4246c85 ethernet ens3 tun0 864e0de2-e5c6-4c9b-aa7f-20aef970067c tun tun0 tun1 ddfc7db2-2baa-488f-95da-c8e1e66e458b tun tun1 default be2bc22c-fc98-4b2b-9484-fd4d5c838d5f vpn -- tun0 3c1e12f9-1a08-4a6f-aef3-5ea22d9e9bb2 tun -- tun1 eb8ed73b-3312-401f-a4c4-c26aadb3a014 tun -- The files look like https://paste.ubuntu.com/p/KvTVXPwK75/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1998207 Title: netplan network-manager plugin tries to save temporary connections Status in netplan: Triaged Status in network-manager package in Ubuntu: Fix Committed Bug description: When creating an OpenVPN connection, a temporal connection called tunN is created. For instance, after activating a connection called vpntest, I have: NAME UUID TYPE DEVICE vpntest 458856e6-8f0f-4dc6-82f2-dd72868252a0 vpn ens3 tun0 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 tun tun0 tun0 is created/removed after activating/deactivating vpntest and should not really be saved, but I see netplan adding it in /etc/netplan. And while doing so the plugin also reports some errors (I see these when stopping the connection): Nov 28 16:16:57 ubuntu NetworkManager[11752]: [1669652217.2920] BUG: the profile cannot be stored in keyfile format without becoming unusable: cannot access file: No such file or directory Nov 28 16:16:57 ubuntu NetworkManager[11752]: ((src/libnm-core-impl/nm-connection.c:342)): assertion '' failed Nov 28 16:16:57 ubuntu NetworkManager[11752]: [1669652217.2920] keyfile: commit: failure to write 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 ((null)) to "/run/NetworkManager/system-connections/tun0-1eb1dbe8-5678-4818-9adf-fb2dc01ed132.nmconnection": keyfile writer produces an invalid connection: cannot access file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1998207/+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 1977710] Re: /etc/adduser.conf.dpkg-save created by postinst since 3.121ubuntu1
This bug was fixed in the package adduser - 3.129ubuntu1 --- adduser (3.129ubuntu1) lunar; urgency=medium * Merge from Debian unstable (LP: #1873519, #1977710). Remaining changes: - Add support for encrypting home directories: + adduser: Add --encrypt-home option, which calls ecryptfs-setup-private for the hard work. + doc/adduser.8: document the --encrypt-home option + debian/control: suggest ecryptfs-utils >= 67-1 + deluser: remove all of /var/lib/ecryptfs/$user with --remove-home - extrausers support for adduser and gpasswd (LP: #1323732) - Add support for ZFS home directories (LP: #1873263) - Enable private home directories by default (LP: #48734) + Set DIR_MODE=0750 and SYS_DIR_MODE=0750 in the default adduser.conf * Rename NAME_REGEX_SYSTEM to SYS_NAME_REGEX - AdduserCommon.pm, adduser.conf: Change default SYS_NAME_REGEX to allow uppercase letters in the names of system users. * Removed changes (superseded by Debian): - AdduserCommon.pm, adduser, adduser.8, adduser.conf.5: Allow uppercase letters in the names of system users. This is done by having a separate NAME_REGEX_SYSTEM configuration setting which applies when --system is specified. adduser (3.129) unstable; urgency=medium * improve parameter interpretation for adduser. Thanks to Boris Kolpackov (Closes: #1018861) adduser (3.128) unstable; urgency=medium [ Marc Haber ] * increase timeouts, reduce number of tests for delgroup_perf.t they have timed out in Debian infrastructure * even the legacy testsuite needs cron * Write defaults explicitly in configuration file templates. Thanks to Christoph Anton Mitterer (Closes: #1017888) * skip most of the version checks in preinst Thanks to Vincent Lefevre (Closes: #1017912) * document that the --ingroup group must exist * fix handling of explicitly set --uid and --gid. Thanks to Samuel Thibault (Closes: #1017952) [ Benjamin Drung ] * Document parameter for checkname function adduser (3.127) unstable; urgency=low [ Jason Franklin ] * Document the intent of the --no-create-home option (Closes: #152195) [ Marc Haber ] * create home directory with primary group of the user (Closes: #1017694) * update and extend README adduser (3.126) experimental; urgency=medium * more clear conffile handling in debian/preinst. Thanks to Simon McVittie (Closes: #1016574) * add postrm script cleaning up better after purge * add a Debian README, move too long DIR_MODE explanation from NEWS.Debian to README. adduser (3.125) experimental; urgency=medium [ Marc Haber ] * remove debconf. (Closes: #57280, #398802) * install (add|del)user.conf as examples. * install adduser.conf as dpkg-conffile directly to /etc. (Closes: #541620) * remove postinst/postrm. (Closes: #1012492) [ Jason Franklin ] * Remove the unused "get_users_groups" subroutine. (Closes: #1015907) [ Matt Barry ] * Do not check for group being empty on 'delgroup'. (Closes: #682156) adduser (3.124) experimental; urgency=medium * experimental upload * implement new USERS_GROUP semantics * adapt documentation * implement testcases * re-work adduser logic to support USERGROUPS mechanics. This also kind of drive-by implements --firstgid and --lastgid (Closes: #609114, #678615, #440801) * rework adduser.conf * improve test infrastructure * implement new test for non membership in group * implement new group_has_gid test * implement new apply_config_hash function. * fix bugs and docs in --add-extra-groups * update debian/copyright * Update of German program translation. Thanks to Dr. Tobias Quathamer (Closes: #1015283) adduser (3.123) unstable; urgency=medium [ Marc Haber ] * flip default for DIR_MODE to 0700 again. Thanks to Josh Triplett (Closes: #1014901) * add debian.NEWS entry to document the DIR_MODE change * remove superficial examples/adduser.local.conf.examples/adduser.conf [ Matt Barry ] * Check explicitly for <= 32 byte names. (Closes: #1014450) adduser (3.122) unstable; urgency=low [ Marc Haber ] * improve package description. * Standards-Version: 4.6.1 (no changes necessary) * clean out EXTRA_GROUPS to only contain users. Thanks to Daniel Keast. (Closes: #849265) * add SECURITY section to manual pages. * add test for backups of home directory. * improve and update lintian overrides. * Formatting changes to manual pages. Thanks to Markus Hiereth. (Closes: #874560) * fix some typos in manual pages. * set VERBOSE and DEBUG envvars in deluser as well. (Closes: #1006897) * add documentation about adduser being a policy layer. (Closes: #1007785) * try to clarify system account terminology (policy vs system). (Closes: #1006975) * Document that only adduser --system is idempotent. (Closes: #723572) * error out for two-argument addgroup. Thank
[Touch-packages] [Bug 1873519] Re: Package should own adduser.conf
This bug was fixed in the package adduser - 3.129ubuntu1 --- adduser (3.129ubuntu1) lunar; urgency=medium * Merge from Debian unstable (LP: #1873519, #1977710). Remaining changes: - Add support for encrypting home directories: + adduser: Add --encrypt-home option, which calls ecryptfs-setup-private for the hard work. + doc/adduser.8: document the --encrypt-home option + debian/control: suggest ecryptfs-utils >= 67-1 + deluser: remove all of /var/lib/ecryptfs/$user with --remove-home - extrausers support for adduser and gpasswd (LP: #1323732) - Add support for ZFS home directories (LP: #1873263) - Enable private home directories by default (LP: #48734) + Set DIR_MODE=0750 and SYS_DIR_MODE=0750 in the default adduser.conf * Rename NAME_REGEX_SYSTEM to SYS_NAME_REGEX - AdduserCommon.pm, adduser.conf: Change default SYS_NAME_REGEX to allow uppercase letters in the names of system users. * Removed changes (superseded by Debian): - AdduserCommon.pm, adduser, adduser.8, adduser.conf.5: Allow uppercase letters in the names of system users. This is done by having a separate NAME_REGEX_SYSTEM configuration setting which applies when --system is specified. adduser (3.129) unstable; urgency=medium * improve parameter interpretation for adduser. Thanks to Boris Kolpackov (Closes: #1018861) adduser (3.128) unstable; urgency=medium [ Marc Haber ] * increase timeouts, reduce number of tests for delgroup_perf.t they have timed out in Debian infrastructure * even the legacy testsuite needs cron * Write defaults explicitly in configuration file templates. Thanks to Christoph Anton Mitterer (Closes: #1017888) * skip most of the version checks in preinst Thanks to Vincent Lefevre (Closes: #1017912) * document that the --ingroup group must exist * fix handling of explicitly set --uid and --gid. Thanks to Samuel Thibault (Closes: #1017952) [ Benjamin Drung ] * Document parameter for checkname function adduser (3.127) unstable; urgency=low [ Jason Franklin ] * Document the intent of the --no-create-home option (Closes: #152195) [ Marc Haber ] * create home directory with primary group of the user (Closes: #1017694) * update and extend README adduser (3.126) experimental; urgency=medium * more clear conffile handling in debian/preinst. Thanks to Simon McVittie (Closes: #1016574) * add postrm script cleaning up better after purge * add a Debian README, move too long DIR_MODE explanation from NEWS.Debian to README. adduser (3.125) experimental; urgency=medium [ Marc Haber ] * remove debconf. (Closes: #57280, #398802) * install (add|del)user.conf as examples. * install adduser.conf as dpkg-conffile directly to /etc. (Closes: #541620) * remove postinst/postrm. (Closes: #1012492) [ Jason Franklin ] * Remove the unused "get_users_groups" subroutine. (Closes: #1015907) [ Matt Barry ] * Do not check for group being empty on 'delgroup'. (Closes: #682156) adduser (3.124) experimental; urgency=medium * experimental upload * implement new USERS_GROUP semantics * adapt documentation * implement testcases * re-work adduser logic to support USERGROUPS mechanics. This also kind of drive-by implements --firstgid and --lastgid (Closes: #609114, #678615, #440801) * rework adduser.conf * improve test infrastructure * implement new test for non membership in group * implement new group_has_gid test * implement new apply_config_hash function. * fix bugs and docs in --add-extra-groups * update debian/copyright * Update of German program translation. Thanks to Dr. Tobias Quathamer (Closes: #1015283) adduser (3.123) unstable; urgency=medium [ Marc Haber ] * flip default for DIR_MODE to 0700 again. Thanks to Josh Triplett (Closes: #1014901) * add debian.NEWS entry to document the DIR_MODE change * remove superficial examples/adduser.local.conf.examples/adduser.conf [ Matt Barry ] * Check explicitly for <= 32 byte names. (Closes: #1014450) adduser (3.122) unstable; urgency=low [ Marc Haber ] * improve package description. * Standards-Version: 4.6.1 (no changes necessary) * clean out EXTRA_GROUPS to only contain users. Thanks to Daniel Keast. (Closes: #849265) * add SECURITY section to manual pages. * add test for backups of home directory. * improve and update lintian overrides. * Formatting changes to manual pages. Thanks to Markus Hiereth. (Closes: #874560) * fix some typos in manual pages. * set VERBOSE and DEBUG envvars in deluser as well. (Closes: #1006897) * add documentation about adduser being a policy layer. (Closes: #1007785) * try to clarify system account terminology (policy vs system). (Closes: #1006975) * Document that only adduser --system is idempotent. (Closes: #723572) * error out for two-argument addgroup. Thank
[Touch-packages] [Bug 1964636] Re: Incorrect handling of apparmor `bpf` capability
In regards to @sil2100 questions, I can review the patches(~24) and double check any use cases. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1964636 Title: Incorrect handling of apparmor `bpf` capability Status in apparmor package in Ubuntu: In Progress Status in snapd package in Ubuntu: Incomplete Status in apparmor source package in Focal: Fix Committed Bug description: [ Impact ] The apparmor_parser before the 3.0 release would build its capability list from the installed kernel headers. The apparmor_parser was built against a kernel without support for cap 'bpf' This was fixed in 3.0 by having a static caps list (with full mapping info) and the dynamic auto-generated list (against the kernel headers) that is used to check that the static list has not become stale. In addition the parser can pull kernel supported caps straight from the apparmor kernel module (it will however be missing the mapping info). Backporting the patches from 3.0 fixes the issue. [ Test Plan ] Before the fix, the following profile fails loading: # echo "profile foo { capability bpf, }" | apparmor_parser -Q AppArmor parser error, in stdin line 1: Invalid capability bpf. # echo $? 1 After the fix, it works as expected: # echo "profile foo { capability bpf, }" | apparmor_parser -Q # echo $? 0 [ Where problems could occur ] With these changes, the parser can change its behavior based on a few things. 1. the kernel its built against. This would not change behavior when run in a container vs at system level. 2. If a feature-file is specified, via --features-file, --policy- features, or --kernel-features. This allows overriding the normal policy and kernel examination that the parser does when compiling policy. 3. If /sys/kernel/security/apparmor/features is not available. The parser will fallback to an old set of features available in a kernel before the kernel module started exporting what the kernel module supports on the running kernel. [ Other Info ] The patches for focal (apparmor-2.13) can be found at: https://launchpad.net/~georgiag/+archive/ubuntu/mqueue-sru/ As mentioned before, these patches are already running on apparmor-3.0. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1964636/+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 1964636] Re: Incorrect handling of apparmor `bpf` capability
I did a quick test with apparmor focal-yoga and -proposed this morning to verify it fixes https://bugs.launchpad.net/cloud-archive/+bug/1988270 # testing with focal-yoga Apparmor version tested - 2.13.3-7ubuntu5.2 generate focal-yoga instance juju ssh nova-compute/0 sudo apt-cache policy apparmor sudo vim /etc/apt/sources.list # add -proposed deb http://nova.clouds.archive.ubuntu.com/ubuntu/ focal-proposed main universe # save and exit sudo apt-get upgrade apparmor sudo systemctl restart apparmor tail -n 1000 /var/log/syslog # no errors are thrown by apparmor Jan 9 15:27:40 juju-3151fe-testapparmor-9 apparmor.systemd[62260]: Restarting AppArmor Jan 9 15:27:40 juju-3151fe-testapparmor-9 apparmor.systemd[62260]: Reloading AppArmor profiles Jan 9 15:27:40 juju-3151fe-testapparmor-9 apparmor.systemd[62274]: Skipping profile in /etc/apparmor.d/disable: usr.bin.nova-compute Jan 9 15:27:40 juju-3151fe-testapparmor-9 kernel: [ 1440.404862] audit: type=1400 audit(1673278060.118:74): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="virt-aa-helper" pid=62273 comm="apparmor_parser" Jan 9 15:27:40 juju-3151fe-testapparmor-9 kernel: [ 1440.406888] audit: type=1400 audit(1673278060.118:75): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/usr/bin/man" pid=62275 comm="apparmor_parser" Jan 9 15:27:40 juju-3151fe-testapparmor-9 kernel: [ 1440.406890] audit: type=1400 audit(1673278060.118:76): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="man_filter" pid=62275 comm="apparmor_parser" Jan 9 15:27:40 juju-3151fe-testapparmor-9 kernel: [ 1440.406892] audit: type=1400 audit(1673278060.118:77): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="man_groff" pid=62275 comm="apparmor_parser" Jan 9 15:27:40 juju-3151fe-testapparmor-9 kernel: [ 1440.408833] audit: type=1400 audit(1673278060.122:78): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/usr/lib/snapd/snap-confine" pid=62276 comm="apparmor_parser" Jan 9 15:27:40 juju-3151fe-testapparmor-9 kernel: [ 1440.408838] audit: type=1400 audit(1673278060.122:79): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=62276 comm="apparmor_parser" Jan 9 15:27:40 juju-3151fe-testapparmor-9 kernel: [ 1440.415917] audit: type=1400 audit(1673278060.130:80): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=62277 comm="apparmor_parser" Jan 9 15:27:40 juju-3151fe-testapparmor-9 kernel: [ 1440.415921] audit: type=1400 audit(1673278060.130:81): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=62277 comm="apparmor_parser" Jan 9 15:27:40 juju-3151fe-testapparmor-9 kernel: [ 1440.415924] audit: type=1400 audit(1673278060.130:82): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=62277 comm="apparmor_parser" Jan 9 15:27:40 juju-3151fe-testapparmor-9 kernel: [ 1440.415926] audit: type=1400 audit(1673278060.130:83): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/{,usr/}sbin/dhclient" pid=62277 comm="apparmor_parser" Jan 9 15:27:40 juju-3151fe-testapparmor-9 apparmor.systemd[62279]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Jan 9 15:27:40 juju-3151fe-testapparmor-9 systemd[1]: Finished Load AppArmor profiles. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1964636 Title: Incorrect handling of apparmor `bpf` capability Status in apparmor package in Ubuntu: In Progress Status in snapd package in Ubuntu: Incomplete Status in apparmor source package in Focal: Fix Committed Bug description: [ Impact ] The apparmor_parser before the 3.0 release would build its capability list from the installed kernel headers. The apparmor_parser was built against a kernel without support for cap 'bpf' This was fixed in 3.0 by having a static caps list (with full mapping info) and the dynamic auto-generated list (against the kernel headers) that is used to check that the static list has not become stale. In addition the parser can pull kernel supported caps straight from the apparmor kernel module (it will however be missing the mapping info). Backporti
[Touch-packages] [Bug 2002321] [NEW] computer is too slow.
Public bug reported: i dont know much about those computer term,but if could you help me somehow i would be very greatfull. thanx A.B. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.4.0-050400-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Jan 9 16:11:37 2023 DistUpgraded: 2022-12-25 23:43:14,353 INFO cache.commit() DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:064b] InstallationDate: Installed on 2018-04-19 (1726 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Acer TravelMate P253 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-050400-generic root=UUID=a81ad045-d2f8-4909-8aef-d7239d261ada ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2022-12-25 (14 days ago) dmi.bios.date: 12/16/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: BA51_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.21 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.21:bd12/16/2013:svnAcer:pnTravelMateP253:pvrV2.21:rvnAcer:rnBA51_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.21: dmi.product.family: Type1Family dmi.product.name: TravelMate P253 dmi.product.sku: TravelMate P253_064B_V2.21 dmi.product.version: V2.21 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.110-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sat Dec 1 18:03:02 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages 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/2002321 Title: computer is too slow. Status in xorg package in Ubuntu: New Bug description: i dont know much about those computer term,but if could you help me somehow i would be very greatfull. thanx A.B. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.4.0-050400-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Jan 9 16:11:37 2023 DistUpgraded: 2022-12-25 23:43:14,353 INFO cache.commit() DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:064b] InstallationDate: Installed on 2018-04-19 (1726 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Acer TravelMate P253 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-050400-generic root=UUID=a81ad045-d2f8-4909-8aef-d7239d261ada ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2022-12-25 (14 days ago) dmi.bios.date: 12/16/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: BA51_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.21 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.21:bd12/16/2013:svnAcer:pnTravelMateP253:pvrV2.21:rvnAcer:rnBA51_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.21: dmi.product.family: Type1Family dmi.product.name: TravelMate
[Touch-packages] [Bug 1875882] Re: debconf attempts interactive configuration; breaks Docker image builds
** Changed in: debconf (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1875882 Title: debconf attempts interactive configuration; breaks Docker image builds Status in cloud-images: Invalid Status in debconf package in Ubuntu: Fix Released Status in debconf package in Debian: Fix Released Bug description: When I build a container image using a Dockerfile based on the official "ubuntu" image, if I try to install packages that use debconf to obtain configuration information, the build fails because debconf tries to interact with the user (which is not possible when building a container, since the build process must be non-interactive). How to reproduce: 1) install Docker (the version doesn't seem to matter; tried with various 19.03 variants) 2) run the following command to try and build an image: ``` docker build -
[Touch-packages] [Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gtk+3.0 (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in Mozilla Firefox: New Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Status in gtk+3.0 source package in Jammy: Confirmed Status in gtk4 source package in Jammy: Triaged Status in gtk+3.0 source package in Kinetic: Confirmed Status in gtk4 source package in Kinetic: Triaged Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+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 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gtk+3.0 (Ubuntu Kinetic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in Mozilla Firefox: New Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Status in gtk+3.0 source package in Jammy: Confirmed Status in gtk4 source package in Jammy: Triaged Status in gtk+3.0 source package in Kinetic: Confirmed Status in gtk4 source package in Kinetic: Triaged Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+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 2002318] [NEW] Please merge lsb 11.5 from Debian unstable.
Public bug reported: Please merge lsb 11.5 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. ** Affects: lsb (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lsb in Ubuntu. https://bugs.launchpad.net/bugs/2002318 Title: Please merge lsb 11.5 from Debian unstable. Status in lsb package in Ubuntu: New Bug description: Please merge lsb 11.5 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/2002318/+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 2000784] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2000784 Title: booting issue snd_hda_ intel codec dummy and intel issue Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: booting delay nvidia-smi shows no usage with some memory usage errors : snd_hda_intel :01:00.1: no codecs found! acpi MSFT0101:00: platform device creation failed: -16 ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220) Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_01_00.1" card_name="alsa_card.pci-_01_00.1" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-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: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Fri Dec 30 17:58:15 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3828] Subsystem: Lenovo GK208BM [GeForce 920M] [17aa:3829] InstallationDate: Installed on 2021-06-05 (573 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e360 Qualcomm Atheros Communications Bus 001 Device 003: ID 5986:0670 Acer, Inc Lenovo EasyCamera Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80Q3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=dca8371c-92df-441a-ba2f-acbb9bb611d3 ro quiet splash loglevel=3 vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2018 dmi.bios.release: 1.39 dmi.bios.vendor: LENOVO dmi.bios.version: D3CN39WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo ideapad 500S-14ISK dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 500S-14ISK dmi.ec.firmware.release: 1.26 dmi.modalias: dmi:bvnLENOVO:bvrD3CN39WW:bd06/26/2018:br1.39:efr1.26:svnLENOVO:pn80Q3:pvrLenovoideapad500S-14ISK:rvnLENOVO:rnLenovoideapad500S-14ISK:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad500S-14ISK:skuLENOVO_MT_80Q3_BU_idea_FM_Lenovoideapad500S-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80Q3 dmi.product.sku: LENOVO_MT_80Q3_BU_idea_FM_Lenovo ideapad 500S-14ISK dmi.product.version: Lenovo ideapad 500S-14ISK dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.112+git2208190500.46d1e9~oibaf~j version.libgl1-mesa-dri: libgl1-mesa-dri 22.3~git2208220600.7b81db~oibaf~j 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/linux/+bug/2000784/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More hel
[Touch-packages] [Bug 2000798] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2000798 Title: cannot connect to K380 bluetooth keyboard Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Had trouble connecting my K380 keyboard with the laptop (previously used it without issues), unpaired and now I can no longer pair it. Other bluetooth devices work with this particular laptop (mouse, earbuds), the keyboard works flawlessly with a different laptop (running the same Ubuntu 20.04 OS) and an Android phone. Used bluetoothctl to peek under the hood and got nowhere after turning scan on on the controller and activating the keyboard: [NEW] Device [...mac address of the keyboard...] Keyboard K380 [CHG] Device [...mac address of the keyboard...] Connected: no [DEL] Device [...mac address of the keyboard...] Keyboard K380 After this action, I get: # connect [...mac address of the keyboard...] Device [...mac address of the keyboard...] not available When I activate the keyboard (by pressing any key on it while it's turned on), in the bluetooth settings GUI tool I see the keyboard appear for a fraction of a second in the list of unpaired devices and then it disappears. Help? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3.6 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Dec 30 19:41:41 2022 InstallationDate: Installed on 2022-11-03 (57 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Intel(R) Client Systems LAPKC71E ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2021 dmi.bios.release: 5.19 dmi.bios.vendor: Intel Corp. dmi.bios.version: KCTGL357.0037.2021.0712.0948 dmi.board.name: LAPKC71E dmi.board.vendor: Intel Corporation dmi.board.version: M1-402 dmi.chassis.type: 10 dmi.chassis.vendor: Intel(R) Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnIntelCorp.:bvrKCTGL357.0037.2021.0712.0948:bd07/12/2021:br5.19:efr1.5:svnIntel(R)ClientSystems:pnLAPKC71E:pvrM38559-402:rvnIntelCorporation:rnLAPKC71E:rvrM1-402:cvnIntel(R)Corporation:ct10:cvr2.0:skuBKC71EBFB6000: dmi.product.family: KC dmi.product.name: LAPKC71E dmi.product.sku: BKC71EBFB6000 dmi.product.version: M38559-402 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 20:1E:88:3C:4C:FD ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:221779 acl:5063 sco:0 events:6018 errors:0 TX bytes:785416 acl:104 sco:0 commands:4168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2000798/+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 1998207] Re: netplan network-manager plugin tries to save temporary connections
https://github.com/slyon/NetworkManager/commit/d7730ee3736bdcb7704d96e7bdf4adf46a562a0f ** Changed in: network-manager (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1998207 Title: netplan network-manager plugin tries to save temporary connections Status in netplan: Triaged Status in network-manager package in Ubuntu: Fix Committed Bug description: When creating an OpenVPN connection, a temporal connection called tunN is created. For instance, after activating a connection called vpntest, I have: NAME UUID TYPE DEVICE vpntest 458856e6-8f0f-4dc6-82f2-dd72868252a0 vpn ens3 tun0 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 tun tun0 tun0 is created/removed after activating/deactivating vpntest and should not really be saved, but I see netplan adding it in /etc/netplan. And while doing so the plugin also reports some errors (I see these when stopping the connection): Nov 28 16:16:57 ubuntu NetworkManager[11752]: [1669652217.2920] BUG: the profile cannot be stored in keyfile format without becoming unusable: cannot access file: No such file or directory Nov 28 16:16:57 ubuntu NetworkManager[11752]: ((src/libnm-core-impl/nm-connection.c:342)): assertion '' failed Nov 28 16:16:57 ubuntu NetworkManager[11752]: [1669652217.2920] keyfile: commit: failure to write 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 ((null)) to "/run/NetworkManager/system-connections/tun0-1eb1dbe8-5678-4818-9adf-fb2dc01ed132.nmconnection": keyfile writer produces an invalid connection: cannot access file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1998207/+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 2000739] Re: Window actions (like maximize) no more work in wayland for QEMU using GTK backend once the guest UI is intialized.
Thank you very much Christian for the confirmation (upstream as well) and your further analysis of the issue. Your comment #12 (qemu- system-x86_64 -display gtk) is also reflected in my observation in comment #7. I also appreciate your GDK_BACKEND=x11 ... workaround. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2000739 Title: Window actions (like maximize) no more work in wayland for QEMU using GTK backend once the guest UI is intialized. Status in qemu package in Ubuntu: Confirmed Status in wayland package in Ubuntu: New Bug description: Window actions (like maximize) no more work in wayland for QEMU using GTK backend once the guest UI is intialized. This can be seen by running an installed or even a trial Ubuntu from an ISO like: $ qemu-system-x86_64 \ -boot d \ -cdrom ubuntu-22.04.1-desktop-amd64.iso \ -m 4096M \ -machine type=q35,accel=kvm \ -cpu host \ -smp 2 \ -device qxl-vga The GTK UI of qemu has a feature called "fullscreen" which disables the screen decorations and sets the window to maximize. The decorations go away, but maximize doesn't work. The following details were found so far: - running with GDK_BACKEND=x11 works - using sdl instead of gtk backend works - using the old qemu of Focal, or the newest from upstream git in jammy all fails (no qemu change AFAICS) - host UI widgets (the square at the window top) do not work either - hotkeys (super-up) do not work either It seems that once the guest has enabled the desktop something changes and the maximize/minimize/... actions are no more processed. Not sure were to debug next in regard to the gnome/wayland UI handling of this - any idea? P.S. We can reproduce this in git builds of qemu, so we can debug of modify the code as needed. The code for this is mostly in [1] [1]: https://gitlab.com/qemu-project/qemu/-/blob/master/ui/gtk.c --- original report --- Running QEMU version 4.2.1 on Ubuntu 20.04 via qemu-system-x86_64 \ -boot d \ -cdrom ubuntu-22.04.1-desktop-amd64.iso \ -m 4096M \ -machine type=q35,accel=kvm \ -cpu host \ -smp 2 \ -device qxl-vga and pressing ctrl+alt+f after booting the Ubuntu 22.04 live ISO and adjusting the display resolution to match the native resolution, works as expected, i.e., the VM screen is correctly displayed in fullscreen. However, after running the same command for QEMU version 6.2.0 on Ubuntu 22.04 and pressing ctrl+alt+f after making the resolution adjustment, yields a fullscreen view where the space occupied by the GNOME top bar (top panel with date in center) of the host is not used. The top bar itself is not visible but instead the purple background is shown where the top bar resides. The problem also occurs when replacing '-device qxl-vga' by '-device VGA,vgamem_mb=64'. The problem however does not occur when using '-device virtio-vga'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2000739/+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 2000739] Re: Window actions (like maximize) no more work in wayland for QEMU using GTK backend once the guest UI is intialized.
** Description changed: + Window actions (like maximize) no more work in wayland for QEMU using + GTK backend once the guest UI is intialized. + + This can be seen by running an installed or even a trial Ubuntu from an + ISO like: + + $ qemu-system-x86_64 \ + -boot d \ + -cdrom ubuntu-22.04.1-desktop-amd64.iso \ + -m 4096M \ + -machine type=q35,accel=kvm \ + -cpu host \ + -smp 2 \ + -device qxl-vga + + The GTK UI of qemu has a feature called "fullscreen" which disables the + screen decorations and sets the window to maximize. The decorations go + away, but maximize doesn't work. + + + The following details were found so far: + - running with GDK_BACKEND=x11 works + - using sdl instead of gtk backend works + - using the old qemu of Focal, or the newest from upstream git in jammy all fails (no qemu change AFAICS) + - host UI widgets (the square at the window top) do not work either + - hotkeys (super-up) do not work either + + It seems that once the guest has enabled the desktop something changes + and the maximize/minimize/... actions are no more processed. Not sure + were to debug next in regard to the gnome/wayland UI handling of this - + any idea? + + P.S. We can reproduce this in git builds of qemu, so we can debug of + modify the code as needed. The code for this is mostly in [1] + + [1]: https://gitlab.com/qemu-project/qemu/-/blob/master/ui/gtk.c + + --- original report --- + Running QEMU version 4.2.1 on Ubuntu 20.04 via qemu-system-x86_64 \ - -boot d \ - -cdrom ubuntu-22.04.1-desktop-amd64.iso \ - -m 4096M \ - -machine type=q35,accel=kvm \ - -cpu host \ - -smp 2 \ - -device qxl-vga + -boot d \ + -cdrom ubuntu-22.04.1-desktop-amd64.iso \ + -m 4096M \ + -machine type=q35,accel=kvm \ + -cpu host \ + -smp 2 \ + -device qxl-vga and pressing ctrl+alt+f after booting the Ubuntu 22.04 live ISO and adjusting the display resolution to match the native resolution, works as expected, i.e., the VM screen is correctly displayed in fullscreen. However, after running the same command for QEMU version 6.2.0 on Ubuntu 22.04 and pressing ctrl+alt+f after making the resolution adjustment, yields a fullscreen view where the space occupied by the GNOME top bar (top panel with date in center) of the host is not used. The top bar itself is not visible but instead the purple background is shown where the top bar resides. The problem also occurs when replacing '-device qxl-vga' by '-device VGA,vgamem_mb=64'. The problem however does not occur when using '-device virtio-vga'. ** Also affects: wayland (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2000739 Title: Window actions (like maximize) no more work in wayland for QEMU using GTK backend once the guest UI is intialized. Status in qemu package in Ubuntu: Confirmed Status in wayland package in Ubuntu: New Bug description: Window actions (like maximize) no more work in wayland for QEMU using GTK backend once the guest UI is intialized. This can be seen by running an installed or even a trial Ubuntu from an ISO like: $ qemu-system-x86_64 \ -boot d \ -cdrom ubuntu-22.04.1-desktop-amd64.iso \ -m 4096M \ -machine type=q35,accel=kvm \ -cpu host \ -smp 2 \ -device qxl-vga The GTK UI of qemu has a feature called "fullscreen" which disables the screen decorations and sets the window to maximize. The decorations go away, but maximize doesn't work. The following details were found so far: - running with GDK_BACKEND=x11 works - using sdl instead of gtk backend works - using the old qemu of Focal, or the newest from upstream git in jammy all fails (no qemu change AFAICS) - host UI widgets (the square at the window top) do not work either - hotkeys (super-up) do not work either It seems that once the guest has enabled the desktop something changes and the maximize/minimize/... actions are no more processed. Not sure were to debug next in regard to the gnome/wayland UI handling of this - any idea? P.S. We can reproduce this in git builds of qemu, so we can debug of modify the code as needed. The code for this is mostly in [1] [1]: https://gitlab.com/qemu-project/qemu/-/blob/master/ui/gtk.c --- original report --- Running QEMU version 4.2.1 on Ubuntu 20.04 via qemu-system-x86_64 \ -boot d \ -cdrom ubuntu-22.04.1-desktop-amd64.iso \ -m 4096M \ -machine type=q35,accel=kvm \ -cpu host \ -smp 2 \ -device qxl-vga and pressing ctrl+alt+f after booting the Ubuntu 22.04 live ISO and adjusting the display resolution to match the native resolution, works as expected, i.e., the VM screen is correctly displayed in fullscreen. However, after running the same command for QEMU version 6.2.0 on Ubun
[Touch-packages] [Bug 1956039] Re: BADSIG 871920D1991BC93C Ubuntu Archive Automatic Signing Key (2018)
I got the same error, also going via apt-cacher-ng: $ sudo apt-get update Hit:1 http://gb.archive.ubuntu.com/ubuntu jammy InRelease Get:2 http://gb.archive.ubuntu.com/ubuntu jammy-updates InRelease [114 kB] Get:3 http://gb.archive.ubuntu.com/ubuntu jammy-backports InRelease [99.8 kB] Hit:4 https://ppa.launchpadcontent.net/gns3/ppa/ubuntu jammy InRelease Hit:5 https://download.docker.com/linux/ubuntu jammy InRelease Get:6 http://gb.archive.ubuntu.com/ubuntu jammy-security InRelease [110 kB] Err:2 http://gb.archive.ubuntu.com/ubuntu jammy-updates InRelease The following signatures were invalid: BADSIG 871920D1991BC93C Ubuntu Archive Automatic Signing Key (2018) Hit:7 https://packagecloud.io/netdata/netdata/ubuntu jammy InRelease Hit:8 https://packagecloud.io/netdata/netdata-repoconfig/ubuntu jammy InRelease Hit:9 https://apt.syncthing.net syncthing InRelease Fetched 324 kB in 2s (148 kB/s) Reading package lists... Done W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://gb.archive.ubuntu.com/ubuntu jammy-updates InRelease: The following signatures were invalid: BADSIG 871920D1991BC93C Ubuntu Archive Automatic Signing Key (2018) W: Failed to fetch http://gb.archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease The following signatures were invalid: BADSIG 871920D1991BC93C Ubuntu Archive Automatic Signing Key (2018) W: Some index files failed to download. They have been ignored, or old ones used instead. Note that in my case the error was for "jammy-updates". The solution for me was: $ sudo rm -rf /var/cache/apt-cacher-ng/uburep/dists/jammy-updates/ Then: $ sudo apt-get update Hit:1 http://gb.archive.ubuntu.com/ubuntu jammy InRelease Get:2 http://gb.archive.ubuntu.com/ubuntu jammy-backports InRelease [99.8 kB] Get:3 http://gb.archive.ubuntu.com/ubuntu jammy-security InRelease [110 kB] Get:4 http://gb.archive.ubuntu.com/ubuntu jammy-updates InRelease [114 kB] Hit:5 https://ppa.launchpadcontent.net/gns3/ppa/ubuntu jammy InRelease Hit:6 https://download.docker.com/linux/ubuntu jammy InRelease Hit:7 https://apt.syncthing.net syncthing InRelease Get:8 http://gb.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [795 kB] Get:9 http://gb.archive.ubuntu.com/ubuntu jammy-updates/main Translation-en [177 kB] Get:10 http://gb.archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packages [521 kB] Get:11 http://gb.archive.ubuntu.com/ubuntu jammy-updates/restricted Translation-en [79.7 kB] Hit:12 https://packagecloud.io/netdata/netdata/ubuntu jammy InRelease Hit:13 https://packagecloud.io/netdata/netdata-repoconfig/ubuntu jammy InRelease Fetched 1,897 kB in 2s (938 kB/s) Reading package lists... Done $ Hence getting into this bad state looks like some internal problem with apt-cacher-ng. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1956039 Title: BADSIG 871920D1991BC93C Ubuntu Archive Automatic Signing Key (2018) Status in apt package in Ubuntu: Confirmed Bug description: Updating Jammy fails with: Get:2 http://archive.ubuntu.com/ubuntu jammy InRelease [270 kB] Err:2 http://archive.ubuntu.com/ubuntu jammy InRelease The following signatures were invalid: BADSIG 871920D1991BC93C Ubuntu Archive Automatic Signing Key (2018) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1956039/+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 1998942] Re: openssl: merge 3.0.7-1 from Debian unstable
Attached is the debdiff from 3.0.7-2 to 3.0.7-2ubuntu1. ** Patch added: "openssl_3.0.7-2-to-openssl_3.0.7-2ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1998942/+attachment/5640127/+files/openssl_3.0.7-2-to-openssl_3.0.7-2ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1998942 Title: openssl: merge 3.0.7-1 from Debian unstable Status in openssl package in Ubuntu: In Progress Bug description: Debian has moved to 3.0.7 in unstable. Now is a good time to merge it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1998942/+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 1998942] Re: openssl: merge 3.0.7-1 from Debian unstable
Updated because Debian now has 3.0.7-2 which includes a patch for a low severity security issue (CVE-2022-3996). PPA is still at https://launchpad.net/~adrien-n/+archive/ubuntu/merge- openssl-3.0.7 . Attached is the debdiff from 3.0.5-2ubuntu2 to 3.0.7-2ubuntu1 . ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-3996 ** Patch added: "openssl_3.0.5-2ubuntu2-to-openssl_3.0.7-2ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1998942/+attachment/5640126/+files/openssl_3.0.5-2ubuntu2-to-openssl_3.0.7-2ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1998942 Title: openssl: merge 3.0.7-1 from Debian unstable Status in openssl package in Ubuntu: In Progress Bug description: Debian has moved to 3.0.7 in unstable. Now is a good time to merge it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1998942/+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 1740666] Re: systemd-timesyncd doesn't sync time after resume from hibernate
** Changed in: systemd (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1740666 Title: systemd-timesyncd doesn't sync time after resume from hibernate Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: When resuming, the clock remains at the time when the hibernate happened, even if timedatectl claims that it is being synced: $ timedatectl status Local time: Вс 2017-12-31 13:46:16 +05 Universal time: Вс 2017-12-31 08:46:16 UTC RTC time: Вс 2017-12-31 08:46:16 Time zone: Asia/Yekaterinburg (+05, +0500) Network time on: yes NTP synchronized: yes RTC in local TZ: no I've tried waiting a bit, but this persisted for some minutes, so I forced an update with systemctl restart systemd-timesyncd.service And afterwards the time was (apparently) correctly synced. Please, let me know what further informations are needed to debug the issue, and I would be happy to do some other test. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12.1 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: MATE Date: Sun Dec 31 13:41:51 2017 InstallationDate: Installed on 2017-06-05 (208 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Gigabyte Technology Co., Ltd. P35-DS3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=1bda199b-5177-4ed2-babe-46c9ab503918 ro quiet splash zswap.enabled=1 zswap.compressor=lz4 zswap.max_pool_percent=33 vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-12-16 (14 days ago) dmi.bios.date: 06/18/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740666/+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 1899343] Re: tzdata sets /etc/timezone to `/UTC`, not `Etc/UTC`
** Changed in: debconf (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1899343 Title: tzdata sets /etc/timezone to `/UTC`, not `Etc/UTC` Status in tzdata package in Ubuntu: Triaged Status in debconf package in Debian: New Bug description: When installed within the `ubuntu` Docker container, `tzdata` sets `etc/timezone` to `/UTC`, not `Etc/UTC`, which breaks applications that are reading `etc/timezone` and expecting a valid timezone name. I'm guess that this wasn't noticed, since technically `/usr/share/zoneinfo//UTC` (double slash) still works. Here is a Dockerfile that reproduces the issue: ```dockerfile FROM ubuntu RUN apt-get update && \ apt-get install -y tzdata ``` Here is the output of `docker build`: ``` test (master)$ docker build --no-cache -t tztest . Sending build context to Docker daemon 2.56kB Step 1/3 : FROM ubuntu ---> 9140108b62dc Step 2/3 : RUN apt-get update && apt install -y tzdata ---> Running in 03da406f73cb Get:1 http://archive.ubuntu.com/ubuntu focal InRelease [265 kB] Get:2 http://security.ubuntu.com/ubuntu focal-security InRelease [107 kB] Get:3 http://archive.ubuntu.com/ubuntu focal-updates InRelease [111 kB] Get:4 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 Packages [75.9 kB] Get:5 http://archive.ubuntu.com/ubuntu focal-backports InRelease [98.3 kB] Get:6 http://security.ubuntu.com/ubuntu focal-security/multiverse amd64 Packages [1169 B] Get:7 http://security.ubuntu.com/ubuntu focal-security/universe amd64 Packages [626 kB] Get:8 http://archive.ubuntu.com/ubuntu focal/restricted amd64 Packages [33.4 kB] Get:9 http://archive.ubuntu.com/ubuntu focal/multiverse amd64 Packages [177 kB] Get:10 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages [11.3 MB] Get:11 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages [406 kB] Get:12 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages [1275 kB] Get:13 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages [745 kB] Get:14 http://archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages [832 kB] Get:15 http://archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages [88.7 kB] Get:16 http://archive.ubuntu.com/ubuntu focal-updates/multiverse amd64 Packages [21.6 kB] Get:17 http://archive.ubuntu.com/ubuntu focal-backports/universe amd64 Packages [4277 B] Fetched 16.2 MB in 4s (3919 kB/s) Reading package lists... WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Reading package lists... Building dependency tree... Reading state information... The following NEW packages will be installed: tzdata 0 upgraded, 1 newly installed, 0 to remove and 4 not upgraded. Need to get 293 kB of archives. After this operation, 4026 kB of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 tzdata all 2020a-0ubuntu0.20.04 [293 kB] debconf: delaying package configuration, since apt-utils is not installed Fetched 293 kB in 1s (262 kB/s) Selecting previously unselected package tzdata. (Reading database ... 4121 files and directories currently installed.) Preparing to unpack .../tzdata_2020a-0ubuntu0.20.04_all.deb ... Unpacking tzdata (2020a-0ubuntu0.20.04) ... Setting up tzdata (2020a-0ubuntu0.20.04) ... debconf: unable to initialize frontend: Dialog debconf: (TERM is not set, so the dialog frontend is not usable.) debconf: falling back to frontend: Readline debconf: unable to initialize frontend: Readline debconf: (Can't locate Term/ReadLine.pm in @INC (you may need to install the Term::ReadLine module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 /usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/perl5/Debconf/FrontEnd/Readline.pm line 7.) debconf: falling back to frontend: Teletype Configuring tzdata -- Please select the geographic area in which you live. Subsequent configuration questions will narrow this down by presenting a list of cities, representing the time zones in which they are located. 1. Africa 4. Australia 7. Atlantic 10. Pacific 13. Etc 2. America 5. Arctic 8. Europe11. SystemV 3. Antarctica 6. Asia 9. Indian12. US Geographic area: Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111. Current default time zone: '/UTC' Local time is now: Sun Oct 11 11:35:33 UTC 2020. Universal Time is now: Sun Oct 11 11:35:33 UTC 2020. Run 'dpkg-reconfigu
[Touch-packages] [Bug 1875882] Re: debconf attempts interactive configuration; breaks Docker image builds
The Debian bug #929417 is fixed in debconf 1.5.81 and therefore will be in Ubuntu 23.04 (lunar). The "Use of uninitialized value" warning is caused by the separate bug #1899343. ** Also affects: debconf (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929417 Importance: Unknown Status: Unknown ** Changed in: debconf (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1875882 Title: debconf attempts interactive configuration; breaks Docker image builds Status in cloud-images: Invalid Status in debconf package in Ubuntu: Fix Released Status in debconf package in Debian: Unknown Bug description: When I build a container image using a Dockerfile based on the official "ubuntu" image, if I try to install packages that use debconf to obtain configuration information, the build fails because debconf tries to interact with the user (which is not possible when building a container, since the build process must be non-interactive). How to reproduce: 1) install Docker (the version doesn't seem to matter; tried with various 19.03 variants) 2) run the following command to try and build an image: ``` docker build -
[Touch-packages] [Bug 1899343] Re: tzdata sets /etc/timezone to `/UTC`, not `Etc/UTC`
** Bug watch added: Debian Bug tracker #723843 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723843 ** Also affects: debconf (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723843 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1899343 Title: tzdata sets /etc/timezone to `/UTC`, not `Etc/UTC` Status in tzdata package in Ubuntu: Triaged Status in debconf package in Debian: Unknown Bug description: When installed within the `ubuntu` Docker container, `tzdata` sets `etc/timezone` to `/UTC`, not `Etc/UTC`, which breaks applications that are reading `etc/timezone` and expecting a valid timezone name. I'm guess that this wasn't noticed, since technically `/usr/share/zoneinfo//UTC` (double slash) still works. Here is a Dockerfile that reproduces the issue: ```dockerfile FROM ubuntu RUN apt-get update && \ apt-get install -y tzdata ``` Here is the output of `docker build`: ``` test (master)$ docker build --no-cache -t tztest . Sending build context to Docker daemon 2.56kB Step 1/3 : FROM ubuntu ---> 9140108b62dc Step 2/3 : RUN apt-get update && apt install -y tzdata ---> Running in 03da406f73cb Get:1 http://archive.ubuntu.com/ubuntu focal InRelease [265 kB] Get:2 http://security.ubuntu.com/ubuntu focal-security InRelease [107 kB] Get:3 http://archive.ubuntu.com/ubuntu focal-updates InRelease [111 kB] Get:4 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 Packages [75.9 kB] Get:5 http://archive.ubuntu.com/ubuntu focal-backports InRelease [98.3 kB] Get:6 http://security.ubuntu.com/ubuntu focal-security/multiverse amd64 Packages [1169 B] Get:7 http://security.ubuntu.com/ubuntu focal-security/universe amd64 Packages [626 kB] Get:8 http://archive.ubuntu.com/ubuntu focal/restricted amd64 Packages [33.4 kB] Get:9 http://archive.ubuntu.com/ubuntu focal/multiverse amd64 Packages [177 kB] Get:10 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages [11.3 MB] Get:11 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages [406 kB] Get:12 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages [1275 kB] Get:13 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages [745 kB] Get:14 http://archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages [832 kB] Get:15 http://archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages [88.7 kB] Get:16 http://archive.ubuntu.com/ubuntu focal-updates/multiverse amd64 Packages [21.6 kB] Get:17 http://archive.ubuntu.com/ubuntu focal-backports/universe amd64 Packages [4277 B] Fetched 16.2 MB in 4s (3919 kB/s) Reading package lists... WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Reading package lists... Building dependency tree... Reading state information... The following NEW packages will be installed: tzdata 0 upgraded, 1 newly installed, 0 to remove and 4 not upgraded. Need to get 293 kB of archives. After this operation, 4026 kB of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 tzdata all 2020a-0ubuntu0.20.04 [293 kB] debconf: delaying package configuration, since apt-utils is not installed Fetched 293 kB in 1s (262 kB/s) Selecting previously unselected package tzdata. (Reading database ... 4121 files and directories currently installed.) Preparing to unpack .../tzdata_2020a-0ubuntu0.20.04_all.deb ... Unpacking tzdata (2020a-0ubuntu0.20.04) ... Setting up tzdata (2020a-0ubuntu0.20.04) ... debconf: unable to initialize frontend: Dialog debconf: (TERM is not set, so the dialog frontend is not usable.) debconf: falling back to frontend: Readline debconf: unable to initialize frontend: Readline debconf: (Can't locate Term/ReadLine.pm in @INC (you may need to install the Term::ReadLine module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 /usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/perl5/Debconf/FrontEnd/Readline.pm line 7.) debconf: falling back to frontend: Teletype Configuring tzdata -- Please select the geographic area in which you live. Subsequent configuration questions will narrow this down by presenting a list of cities, representing the time zones in which they are located. 1. Africa 4. Australia 7. Atlantic 10. Pacific 13. Etc 2. America 5. Arctic 8. Europe11. SystemV 3. Antarctica 6. Asia 9. Indian12. US Geographic area: Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDr
[Touch-packages] [Bug 1998893] Re: NV reverse prime HDMI has no output
** 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/1998893 Title: NV reverse prime HDMI has no output Status in OEM Priority Project: New Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] The X failed to load glamoregl module on Dell's new platforms, the module is needed by NV dGPU. 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) LoadModule: "glamoregl" 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Loading /usr/lib/xorg/modules/libglamoregl.so 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Module glamoregl: vendor="X.Org Foundation" 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: compiled for 1.21.1.3, module version = 1.0.1 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: ABI class: X.Org ANSI C Emulation, version 0.4 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: MESA: warning: Driver does not support the 0xa78b PCI ID. 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): Refusing to try glamor on llvmpipe 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): glamor initialization failed [Fix] The upstream PR added missing ID for the platforms. https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/16320/ https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/17569/ After creating the test build to include the PR above, ODM verified passed on those platform. [Test case] Install fixed package on the systems, check that display works. [Where things could go wrong] Although one commit drops a couple of pci-id's, they were already dropped from the jammy kernel for lp1990242 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998893/+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 1997093] Re: bash 5.2 regression too-aggressive optimizing of forks in an `eval' command inside a (command) subshell
https://launchpad.net/ubuntu/+source/bash/5.2.15-2ubuntu1 ** Changed in: bash (Ubuntu) Status: New => Fix Committed -- 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/1997093 Title: bash 5.2 regression too-aggressive optimizing of forks in an `eval' command inside a (command) subshell Status in bash package in Ubuntu: Fix Committed Status in ovn package in Ubuntu: New Bug description: OVN makes use of GNU autotest for its testsuite. This in turn is a heavy user of bash. For some reason, when the 'ovn-controller incremental processing' test is executed using bash 5.2 on Debian experimental or Ubuntu Kinetic/Lunar, the `eval` [0] in the `counter_delta_` function misinterprets successful execution of commands [1], leading to a false negative for the 'ovn-controller incremental processing' test [2]. Backporting the bash 5.1 package from Jammy, or compiling bash 5.1 from upstream sources and rerunning the test makes it succeed. This does come across as a regression in bash. 0: https://github.com/ovn-org/ovn/blob/a042aa23e79a0d36f1ce7b0ccfcf0a5995b045cd/tests/ovn-performance.at#L116 1: https://github.com/ovn-org/ovn/blob/a042aa23e79a0d36f1ce7b0ccfcf0a5995b045cd/tests/ovn-performance.at#L479 2: https://github.com/ovn-org/ovn/blob/a042aa23e79a0d36f1ce7b0ccfcf0a5995b045cd/tests/ovn-performance.at#L227 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1997093/+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 1998893] Re: NV reverse prime HDMI has no output
the pci-id's were dropped from the jammy kernel for lp1990242 ** Description changed: [Impact] The X failed to load glamoregl module on Dell's new platforms, the module is needed by NV dGPU. 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) LoadModule: "glamoregl" 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Loading /usr/lib/xorg/modules/libglamoregl.so 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Module glamoregl: vendor="X.Org Foundation" 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: compiled for 1.21.1.3, module version = 1.0.1 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: ABI class: X.Org ANSI C Emulation, version 0.4 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: MESA: warning: Driver does not support the 0xa78b PCI ID. 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): Refusing to try glamor on llvmpipe 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): glamor initialization failed [Fix] The upstream PR added missing ID for the platforms. https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/16320/ https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/17569/ After creating the test build to include the PR above, ODM verified passed on those platform. [Test case] Install fixed package on the systems, check that display works. [Where things could go wrong] - Although one commit drops a couple of pci-id's, they were synced from the kernel and such id's should not be in the wild. Other than that these just add id's and modify some vendor branding. + Although one commit drops a couple of pci-id's, they were already dropped from the jammy kernel for lp1990242 -- 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/1998893 Title: NV reverse prime HDMI has no output Status in OEM Priority Project: New Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] The X failed to load glamoregl module on Dell's new platforms, the module is needed by NV dGPU. 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) LoadModule: "glamoregl" 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Loading /usr/lib/xorg/modules/libglamoregl.so 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Module glamoregl: vendor="X.Org Foundation" 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: compiled for 1.21.1.3, module version = 1.0.1 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: ABI class: X.Org ANSI C Emulation, version 0.4 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: MESA: warning: Driver does not support the 0xa78b PCI ID. 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): Refusing to try glamor on llvmpipe 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): glamor initialization failed [Fix] The upstream PR added missing ID for the platforms. https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/16320/ https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/17569/ After creating the test build to include the PR above, ODM verified passed on those platform. [Test case] Install fixed package on the systems, check that display works. [Where things could go wrong] Although one commit drops a couple of pci-id's, they were already dropped from the jammy kernel for lp1990242 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998893/+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