[Touch-packages] [Bug 2018352] Re: Scaling wrong on external display when setting 100% scaling
** Summary changed: - Resolution wrong on external display when setting 100% scaling + Scaling wrong on external display when setting 100% scaling ** Description changed: - Resolution on external display is wrong when setting 100% scaling on it. It becomes too big, bigger than when set to 125% + Scaling on external display is wrong when setting 100% scaling on it. It becomes too big, bigger than when set to 125% This happens with Xorg on Ubuntu 23.04 with NVIDIA GPU set as only GPU in the system ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-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 525.105.17 Tue Mar 28 18:02:59 UTC 2023 - GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-17ubuntu1) + NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.105.17 Tue Mar 28 18:02:59 UTC 2023 + GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-17ubuntu1) ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 3 08:27:32 2023 DistUpgraded: 2023-04-20 10:00:59,509 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: nvidia/525.105.17, 6.2.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: - NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] [10de:24dc] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: Lenovo GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] [17aa:3a58] + NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] [10de:24dc] (rev a1) (prog-if 00 [VGA controller]) + Subsystem: Lenovo GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] [17aa:3a58] InstallationDate: Installed on 2023-02-09 (82 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 82N6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=2a43fd27-b65c-4d7a-bc19-b001521b0771 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-20 (12 days ago) dmi.bios.date: 03/07/2023 dmi.bios.release: 1.60 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN60WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.60 dmi.modalias: dmi:bvnLENOVO:bvrGKCN60WW:bd03/07/2023:br1.60:efr1.60:svnLENOVO:pn82N6:pvrLegion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 -- 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/2018352 Title: Scaling wrong on external display when setting 100% scaling Status in nvidia-graphics-drivers-525 package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: Scaling on external display is wrong when setting 100% scaling on it. It becomes too big, bigger than when set to 125% This happens with Xorg on Ubuntu 23.04 with NVIDIA GPU set as only GPU in the system ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver
[Touch-packages] [Bug 1942703] Re: Remove-Unused-Kernel-Packages leaves unused linux-hwe-.*-headers-.* packages around
** Changed in: unattended-upgrades Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1942703 Title: Remove-Unused-Kernel-Packages leaves unused linux-hwe-.*-headers-.* packages around Status in unattended-upgrades: New Status in unattended-upgrades package in Ubuntu: New Bug description: If user has linux-generic-hwe-18.04 installed, versioned linux-headers packages depend on versioned linux-hwe-5.4-headers packages that will not get removed. Consequently in time there will be hundreds of thousands of unused files under /usr/src. For example I have about 45 totalling 1.4 GB. The number of inodes may be bigger issue, because file systems have some limitations. I noted the issue when using my linux-purge tool. It is supposed to be able to remove kernels, even if the file system runs out of inodes. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.14 ProcVersionSignature: Ubuntu 5.4.0-81.91~18.04.1-generic 5.4.128 Uname: Linux 5.4.0-81-generic i686 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: i386 Date: Sun Sep 5 14:38:49 2021 InstallationDate: Installed on 2016-09-05 (1826 days ago) InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: Upgraded to bionic on 2019-04-06 (882 days ago) modified.conffile..etc.apt.apt.conf.d.10periodic: [modified] mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-03-26T11:42:30.041160 To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1942703/+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 1983100] Re: dotnet build intermittently crashes with segfault on Ubuntu 18.04
** Changed in: openssl (Ubuntu Bionic) Status: Incomplete => In Progress -- 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/1983100 Title: dotnet build intermittently crashes with segfault on Ubuntu 18.04 Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Bionic: In Progress Bug description: [Impact] Bionic's OpenSSL 1.1.1 package (https://launchpad.net/ubuntu/bionic/+source/openssl) is the only version of openssl 1.1.1 on any distro that we've encountered that does not have support for the OPENSSL_NO_ATEXIT functionality from 1.1.1b (openssl/openssl@c2b3db2). The threading model in .NET has the possibility that background threads are still running when exit() is called, which can cause SIGSEGV if a background thread interacts with OpenSSL after/while it has unloaded. For that reason, we always initialize OpenSSL 1.1.1 with the OPENSSL_NO_ATEXIT flag (which, of all the distros we run on only has no effect on Bionic). We feel that the stability of applications on Ubuntu 18.04 would be improved if the functionality of OPENSSL_NO_ATEXIT was merged into the bionic openssl 1.1.1 package, even if the constant isn't published into the header for the dev package. Context: https://github.com/dotnet/runtime/issues/48411#issuecomment-1178405101 [Test Plan] The described behavior can be reproduced by passing the OPENSSL_NO_ATEXIT to the OPENSSL_init_ssl() call. The application will terminate with a SEGFAULT. More concretely, a minimal reproducer is: #include #include #include #ifndef OPENSSL_INIT_NO_ATEXIT #define OPENSSL_INIT_NO_ATEXIT 0x0008L #endif static void print_error_string() { printf("print_error_string:\n"); printf("ERR_reason_error_string(0) => %s\n", ERR_reason_error_string(0)); } int main(int argc, char* argv[]) { // register this handler first, so it runs last. atexit(print_error_string); OPENSSL_init_ssl( OPENSSL_INIT_ADD_ALL_CIPHERS | OPENSSL_INIT_ADD_ALL_DIGESTS | OPENSSL_INIT_LOAD_CONFIG | OPENSSL_INIT_NO_ATEXIT | OPENSSL_INIT_LOAD_CRYPTO_STRINGS | OPENSSL_INIT_LOAD_SSL_STRINGS, NULL); print_error_string(); return 0; } Building $ sudo apt install libssl-dev $ gcc test.c -lssl -lcrypto $ ./a.out print_error_string: ERR_reason_error_string(0) => (null) print_error_string: Segmentation fault (core dumped) [Other Info] All of these patches are included in upstream release 1.1.1b - lp1983100-0001-Fix-shlibloadtest-to-properly-execute-the-dso_ref-te.patch Fixes the shlibloadtest that was updated as part of #0005 - lp1983100-0002-Implement-OPENSSL_INIT_NO_ATEXIT.patch Patch adds the OPENSSL_INIT_NO_ATEXIT option - lp1983100-0003-Don-t-link-shlibloadtest-against-libcrypto.patch Additional fixes for shlibloadtest - lp1983100-0004-Fix-rpath-related-Linux-test_shlibload-failure.patch Additional fixes for shlibloadtest - lp1983100-0005-Test-atexit-handlers.patch Adds test for OPENSSL_INIT_NO_ATEXIT option and updates the shlibloadtest - lp1983100-0006-Introduce-a-no-pinshared-option.patch This patch includes tests to ensure that if OPENSSL_INIT_NO_ATEXIT is not defined then the atexit() handler is run - lp1983100-0007-Support-_onexit-in-preference-to-atexit-on-Windows.patch This patch ensures that atexit() is only called when on non-Windows systems as Windows uses _onexit() during library unloading All seven patches are required to ensure the correct logic and operation of the OPENSSL_INIT_NO_ATEXIT option. [Where problems could occur] The patches adds an option to the OPENSSL_init_crypto() function to disable the default behavior of calling of a cleanup function on application exit. The patch also includes a few bug fixes around various initializations that were supposed to happen once when running threaded but were not. These changes have the potential for regressions and it is conceivable that they lead to incorrect behavior. However, I have also backported and included all new testing functions in the hope that the changed behavior will get appropriate testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1983100/+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 2018444] [NEW] Kernel 6.2 touchpad won´t drag and drop
Public bug reported: After upgrading to lunar lobster, I can´t drag and drop with my touchpad - it jumps around uncontrollably. If I reboot to the last version 5.19, it works ok. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Wed May 3 23:33:53 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:19ad] InstallationDate: Installed on 2020-07-11 (1026 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0bda:57b5 Realtek Semiconductor Corp. USB Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/11p, 480M |__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M |__ Port 8: Dev 3, If 0, Class=Vendor Specific Class, Driver=rtsx_usb, 480M MachineType: ASUSTeK COMPUTER INC. X555LAB ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic root=UUID=70b396bb-907c-46c9-a9da-18fecdb5f2d0 ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LAB.603 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LAB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555LAB.603:bd04/16/2019:br5.11:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: X dmi.product.name: X555LAB dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kubuntu lunar 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/2018444 Title: Kernel 6.2 touchpad won´t drag and drop Status in xorg package in Ubuntu: New Bug description: After upgrading to lunar lobster, I can´t drag and drop with my touchpad - it jumps around uncontrollably. If I reboot to the last version 5.19, it works ok. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Wed May 3 23:33:53 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:19ad] InstallationDate: Installed on 2020-07-11 (1026 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0bda:57b5 Realtek Semiconductor Corp. USB Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xh
[Touch-packages] [Bug 2017927] Re: Failed to start SLAPD and B&R operation failed in ansible
** Package changed: openldap (Ubuntu) => starlingx -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/2017927 Title: Failed to start SLAPD and B&R operation failed in ansible Status in StarlingX: New Bug description: Ldap conf is pointing to itself as the provider in sync-replication directive hence the restore is failing. Getting the below error while executing ansible playbook for restore. stdout: 'Starting SLAPD: Failed to start SLAPD. To manage notifications about this bug go to: https://bugs.launchpad.net/starlingx/+bug/2017927/+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 1995650] Re: Trivial: Unclosed tag in distro.py
It looks like this goes back to all currently supported versions. ** Merge proposal linked: https://code.launchpad.net/~wontfix/ubuntu/+source/software-properties/+git/software-properties/+merge/442311 -- 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/1995650 Title: Trivial: Unclosed tag in distro.py Status in software-properties package in Ubuntu: In Progress Bug description: Hi, distro.py, line: 37 starts with a tag but does not close it. The code is here: return(_("To improve the user experiece of Debian please take " "part in the popularity contest. If you do so the list of " "installed software and how often it was used will be " "collected and sent anonymously to the Debian project.\n\n" "The results are used to optimise the layout of the " "installation CDs.")) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1995650/+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 2018439] Re: Apparmor crashes GPU acceleration
** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New -- 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/2018439 Title: Apparmor crashes GPU acceleration Status in apparmor package in Ubuntu: New Status in firefox package in Ubuntu: New Bug description: Apparmor crashes GPU acceleration Firefox GPU acceleration started crashing after updating from Ubuntu 22.10 to 23.04. $ lsb_release -rd No LSB modules are available. Description:Ubuntu 23.04 Release:23.04 $ apt-cache policy firefox firefox: Installed: 113.0+build1-0ubuntu0.23.04.1~mt1 Candidate: 113.0+build1-0ubuntu0.23.04.1~mt1 Version table: 1:1snap1-0ubuntu3 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu lunar/main amd64 Packages *** 113.0+build1-0ubuntu0.23.04.1~mt1 999 500 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy libglx-mesa0 libglx-mesa0: Installed: 23.0.3~kisak1~k Candidate: 23.0.3~kisak1~k Version table: *** 23.0.3~kisak1~k 500 500 https://ppa.launchpadcontent.net/kisak/kisak-mesa/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status 23.0.2-1ubuntu1 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu lunar/main amd64 Packages $ apt-cache policy apparmor apparmor: Installed: 3.0.8-1ubuntu2 Candidate: 3.0.8-1ubuntu2 Version table: *** 3.0.8-1ubuntu2 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status # Expected behavior Firefox should not crash in WebGL aquarium and continue to work properly like on 22.10. It should successfully use my GPU to make scrolling smooths and save battery when watching videos. # Actual behavior 1. Startup takes a second or two longer than usual 2. Typing in the address bar is slow 3. Scrolling takes 400% CPU usage 4. Scrolling stutters 5. VAAPI on https://www.w3schools.com/html/html5_video.asp is no longer used as shown in intel_gpu_top 6. Fans start spinning and battery goes down fast 7. glxtest failures had to be manually deleted in about:config 8. Only a few fish in WebGL aquarium (https://webglsamples.org/aquarium/aquarium.html) load before Firefox force-closes with the message: "Mozilla Crash Reporter Firefox had a problem and crashed. Unfortunately, the crash reporter is unable to submit a crash report. Details: The application did not leave a crash dump file. Close" 9. The following lines are relevant in dmesg after clearing it: [22157.695580] kauditd_printk_skb: 6 callbacks suppressed [22157.695582] audit: type=1400 audit(1683153440.994:2583): apparmor="DENIED" operation="capable" class="cap" profile="firefox" pid=15898 comm="firefox" capability=21 capname="sys_admin" [22157.739641] audit: type=1400 audit(1683153441.038:2584): apparmor="DENIED" operation="open" class="file" profile="firefox" name="/sys/devices/pci:00/:00:02.0/revision" pid=15901 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [22157.739647] audit: type=1400 audit(1683153441.038:2585): apparmor="DENIED" operation="open" class="file" profile="firefox" name="/sys/devices/pci:00/:00:02.0/config" pid=15901 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [22157.739719] audit: type=1400 audit(1683153441.038:2586): apparmor="DENIED" operation="open" class="file" profile="firefox" name="/sys/devices/pci:00/:00:02.0/revision" pid=15901 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [22157.739729] audit: type=1400 audit(1683153441.038:2587): apparmor="DENIED" operation="open" class="file" profile="firefox" name="/sys/devices/pci:00/:00:02.0/config" pid=15901 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [22157.769407] audit: type=1400 audit(1683153441.070:2588): apparmor="DENIED" operation="open" class="file" profile="firefox" name="/proc/15898/oom_score_adj" pid=15898 comm="firefox" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 [22157.773042] audit: type=1400 audit(1683153441.074:2589): apparmor="DENIED" operation="file_mmap" class="file" profile="firefox//lsb_release" name="/usr/bin/dash" pid=15934 comm="lsb_release" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [22157.974718] audit: type=1400 audit(1683153441.274:2590): apparmor="DENIED" operation="open" class="file" profile="firefox" name="/proc/15898/cgroup" pid=15898 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 [22157.996255] audit: type=1400 audit(1683153441.298:2591): apparmor="DENIED" operation="open" class="file" profile="firefox" name="/sys/devices/pci:0
[Touch-packages] [Bug 1995650] Re: Trivial: Unclosed tag in distro.py
** Tags added: focal jammy lunar mantic ** Changed in: software-properties (Ubuntu) Status: Confirmed => In Progress -- 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/1995650 Title: Trivial: Unclosed tag in distro.py Status in software-properties package in Ubuntu: In Progress Bug description: Hi, distro.py, line: 37 starts with a tag but does not close it. The code is here: return(_("To improve the user experiece of Debian please take " "part in the popularity contest. If you do so the list of " "installed software and how often it was used will be " "collected and sent anonymously to the Debian project.\n\n" "The results are used to optimise the layout of the " "installation CDs.")) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1995650/+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 2017414] Re: cp --parents fails without reason
** Description changed: + Upstream bug: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=63245 + The following example of a copy command fails without reason: # rm -Rf /tmp/f && mkdir /tmp/f && cp --verbose -t /tmp/f -L --preserve=all --parents /etc/apt/sources.list && echo yes ; ls -lR /tmp/f/etc/apt/sources.list /etc/apt/sources.list /etc -> /tmp/f/etc /etc/apt -> /tmp/f/etc/apt '/etc/apt/sources.list' -> '/tmp/f/etc/apt/sources.list' cp: ‘etc/apt’: No such file or directory -rw-r--r-- 1 root root 2437 Apr 23 09:53 /etc/apt/sources.list -rw-r--r-- 1 root root 2437 Apr 23 09:53 /tmp/f/etc/apt/sources.list # /tmp is on the same filesystem as /. The same on Ubuntu 22.04 works without a problem: # rm -Rf /tmp/f && mkdir /tmp/f && cp --verbose -t /tmp/f -L --preserve=all --parents /etc/apt/sources.list && echo yes ; ls -lR /tmp/f/etc/apt/sources.list /etc/apt/sources.list /etc -> /tmp/f/etc /etc/apt -> /tmp/f/etc/apt '/etc/apt/sources.list' -> '/tmp/f/etc/apt/sources.list' yes -rw-r--r-- 1 root root 263 Mär 26 15:20 /etc/apt/sources.list -rw-r--r-- 1 root root 263 Mär 26 15:20 /tmp/f/etc/apt/sources.list # Why I omit the --preservce=all then it works without a problem: # rm -Rf /tmp/f && mkdir /tmp/f && cp --verbose -t /tmp/f -L --parents /etc/apt/sources.list && echo yes ; ls -lR /tmp/f/etc/apt/sources.list /etc/apt/sources.list /etc -> /tmp/f/etc /etc/apt -> /tmp/f/etc/apt '/etc/apt/sources.list' -> '/tmp/f/etc/apt/sources.list' yes -rw-r--r-- 2 root root 2437 Apr 23 09:53 /etc/apt/sources.list -rw-r--r-- 1 root root 2437 Apr 23 11:02 /tmp/f/etc/apt/sources.list # Also, when I only use --preserve=mode, then it again fails: # rm -Rf /tmp/f && mkdir /tmp/f && cp --verbose -t /tmp/f -L --preserve=mode --parents /etc/apt/sources.list && echo yes ; ls -lR /tmp/f/etc/apt/sources.list /etc/apt/sources.list /etc -> /tmp/f/etc /etc/apt -> /tmp/f/etc/apt '/etc/apt/sources.list' -> '/tmp/f/etc/apt/sources.list' cp: ‘etc/apt’: No such file or directory -rw-r--r-- 2 root root 2437 Apr 23 09:53 /etc/apt/sources.list -rw-r--r-- 1 root root 2437 Apr 23 11:02 /tmp/f/etc/apt/sources.list # Is this a bug in cp or something else? I'm one of the maintainers of Relax-and-Recover (rear) and noticed this in https://github.com/rear/rear/issues/2972 OS Release Info: PRETTY_NAME="Ubuntu 23.04" NAME="Ubuntu" VERSION_ID="23.04" VERSION="23.04 (Lunar Lobster)" VERSION_CODENAME=lunar ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; UBUNTU_CODENAME=lunar LOGO=ubuntu-logo Coreutils version: # cp --version cp (GNU coreutils) 9.1 # dpkg-query -l coreutils Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii coreutils 9.1-1ubuntu2 amd64GNU core utilities ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: coreutils 9.1-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Apr 23 10:48:56 2023 InstallationDate: Installed on 2023-04-23 (0 days ago) InstallationMedia: Ubuntu-Server 23.04 "Lunar Lobster" - Release amd64 (20230415) SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2017414 Title: cp --parents fails without reason Status in coreutils package in Ubuntu: New Bug description: Upstream bug: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=63245 The following example of a copy command fails without reason: # rm -Rf /tmp/f && mkdir /tmp/f && cp --verbose -t /tmp/f -L --preserve=all --parents /etc/apt/sources.list && echo yes ; ls -lR /tmp/f/etc/apt/sources.list /etc/apt/sources.list /etc -> /tmp/f/etc /etc/apt -> /tmp/f/etc/apt '/etc/apt/sources.list' -> '/tmp/f/etc/apt/sources.list' cp: ‘etc/apt’: No such file or directory -rw-r--r-- 1 root root 2437 Apr 23 09:53 /etc/apt/sources.list -rw-r--r-- 1 root root 2437 Apr 23 09:53 /tmp/f/etc/apt/sources.list # /tmp is on the same filesystem as /. The same on Ubuntu 22.04 works without a problem: # rm -Rf /tmp/f && mkdir /tmp/f && cp --verbose -t /tmp/f -L --preserve=all --parents /etc/apt/sources.list && echo yes ; ls -lR /tmp/f/etc/apt/sources.list /e
[Touch-packages] [Bug 2017414] Re: cp --parents fails without reason
** Summary changed: - cp --preserve=all or --preserve=mode fails without reason + cp --parents fails without reason -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2017414 Title: cp --parents fails without reason Status in coreutils package in Ubuntu: New Bug description: The following example of a copy command fails without reason: # rm -Rf /tmp/f && mkdir /tmp/f && cp --verbose -t /tmp/f -L --preserve=all --parents /etc/apt/sources.list && echo yes ; ls -lR /tmp/f/etc/apt/sources.list /etc/apt/sources.list /etc -> /tmp/f/etc /etc/apt -> /tmp/f/etc/apt '/etc/apt/sources.list' -> '/tmp/f/etc/apt/sources.list' cp: ‘etc/apt’: No such file or directory -rw-r--r-- 1 root root 2437 Apr 23 09:53 /etc/apt/sources.list -rw-r--r-- 1 root root 2437 Apr 23 09:53 /tmp/f/etc/apt/sources.list # /tmp is on the same filesystem as /. The same on Ubuntu 22.04 works without a problem: # rm -Rf /tmp/f && mkdir /tmp/f && cp --verbose -t /tmp/f -L --preserve=all --parents /etc/apt/sources.list && echo yes ; ls -lR /tmp/f/etc/apt/sources.list /etc/apt/sources.list /etc -> /tmp/f/etc /etc/apt -> /tmp/f/etc/apt '/etc/apt/sources.list' -> '/tmp/f/etc/apt/sources.list' yes -rw-r--r-- 1 root root 263 Mär 26 15:20 /etc/apt/sources.list -rw-r--r-- 1 root root 263 Mär 26 15:20 /tmp/f/etc/apt/sources.list # Why I omit the --preservce=all then it works without a problem: # rm -Rf /tmp/f && mkdir /tmp/f && cp --verbose -t /tmp/f -L --parents /etc/apt/sources.list && echo yes ; ls -lR /tmp/f/etc/apt/sources.list /etc/apt/sources.list /etc -> /tmp/f/etc /etc/apt -> /tmp/f/etc/apt '/etc/apt/sources.list' -> '/tmp/f/etc/apt/sources.list' yes -rw-r--r-- 2 root root 2437 Apr 23 09:53 /etc/apt/sources.list -rw-r--r-- 1 root root 2437 Apr 23 11:02 /tmp/f/etc/apt/sources.list # Also, when I only use --preserve=mode, then it again fails: # rm -Rf /tmp/f && mkdir /tmp/f && cp --verbose -t /tmp/f -L --preserve=mode --parents /etc/apt/sources.list && echo yes ; ls -lR /tmp/f/etc/apt/sources.list /etc/apt/sources.list /etc -> /tmp/f/etc /etc/apt -> /tmp/f/etc/apt '/etc/apt/sources.list' -> '/tmp/f/etc/apt/sources.list' cp: ‘etc/apt’: No such file or directory -rw-r--r-- 2 root root 2437 Apr 23 09:53 /etc/apt/sources.list -rw-r--r-- 1 root root 2437 Apr 23 11:02 /tmp/f/etc/apt/sources.list # Is this a bug in cp or something else? I'm one of the maintainers of Relax-and-Recover (rear) and noticed this in https://github.com/rear/rear/issues/2972 OS Release Info: PRETTY_NAME="Ubuntu 23.04" NAME="Ubuntu" VERSION_ID="23.04" VERSION="23.04 (Lunar Lobster)" VERSION_CODENAME=lunar ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; UBUNTU_CODENAME=lunar LOGO=ubuntu-logo Coreutils version: # cp --version cp (GNU coreutils) 9.1 # dpkg-query -l coreutils Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii coreutils 9.1-1ubuntu2 amd64GNU core utilities ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: coreutils 9.1-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Apr 23 10:48:56 2023 InstallationDate: Installed on 2023-04-23 (0 days ago) InstallationMedia: Ubuntu-Server 23.04 "Lunar Lobster" - Release amd64 (20230415) SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2017414/+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 2017414] Re: cp --preserve=all or --preserve=mode fails without reason
I reported this bug upstream and somebody even provided a patch: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=63245 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2017414 Title: cp --preserve=all or --preserve=mode fails without reason Status in coreutils package in Ubuntu: New Bug description: The following example of a copy command fails without reason: # rm -Rf /tmp/f && mkdir /tmp/f && cp --verbose -t /tmp/f -L --preserve=all --parents /etc/apt/sources.list && echo yes ; ls -lR /tmp/f/etc/apt/sources.list /etc/apt/sources.list /etc -> /tmp/f/etc /etc/apt -> /tmp/f/etc/apt '/etc/apt/sources.list' -> '/tmp/f/etc/apt/sources.list' cp: ‘etc/apt’: No such file or directory -rw-r--r-- 1 root root 2437 Apr 23 09:53 /etc/apt/sources.list -rw-r--r-- 1 root root 2437 Apr 23 09:53 /tmp/f/etc/apt/sources.list # /tmp is on the same filesystem as /. The same on Ubuntu 22.04 works without a problem: # rm -Rf /tmp/f && mkdir /tmp/f && cp --verbose -t /tmp/f -L --preserve=all --parents /etc/apt/sources.list && echo yes ; ls -lR /tmp/f/etc/apt/sources.list /etc/apt/sources.list /etc -> /tmp/f/etc /etc/apt -> /tmp/f/etc/apt '/etc/apt/sources.list' -> '/tmp/f/etc/apt/sources.list' yes -rw-r--r-- 1 root root 263 Mär 26 15:20 /etc/apt/sources.list -rw-r--r-- 1 root root 263 Mär 26 15:20 /tmp/f/etc/apt/sources.list # Why I omit the --preservce=all then it works without a problem: # rm -Rf /tmp/f && mkdir /tmp/f && cp --verbose -t /tmp/f -L --parents /etc/apt/sources.list && echo yes ; ls -lR /tmp/f/etc/apt/sources.list /etc/apt/sources.list /etc -> /tmp/f/etc /etc/apt -> /tmp/f/etc/apt '/etc/apt/sources.list' -> '/tmp/f/etc/apt/sources.list' yes -rw-r--r-- 2 root root 2437 Apr 23 09:53 /etc/apt/sources.list -rw-r--r-- 1 root root 2437 Apr 23 11:02 /tmp/f/etc/apt/sources.list # Also, when I only use --preserve=mode, then it again fails: # rm -Rf /tmp/f && mkdir /tmp/f && cp --verbose -t /tmp/f -L --preserve=mode --parents /etc/apt/sources.list && echo yes ; ls -lR /tmp/f/etc/apt/sources.list /etc/apt/sources.list /etc -> /tmp/f/etc /etc/apt -> /tmp/f/etc/apt '/etc/apt/sources.list' -> '/tmp/f/etc/apt/sources.list' cp: ‘etc/apt’: No such file or directory -rw-r--r-- 2 root root 2437 Apr 23 09:53 /etc/apt/sources.list -rw-r--r-- 1 root root 2437 Apr 23 11:02 /tmp/f/etc/apt/sources.list # Is this a bug in cp or something else? I'm one of the maintainers of Relax-and-Recover (rear) and noticed this in https://github.com/rear/rear/issues/2972 OS Release Info: PRETTY_NAME="Ubuntu 23.04" NAME="Ubuntu" VERSION_ID="23.04" VERSION="23.04 (Lunar Lobster)" VERSION_CODENAME=lunar ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; UBUNTU_CODENAME=lunar LOGO=ubuntu-logo Coreutils version: # cp --version cp (GNU coreutils) 9.1 # dpkg-query -l coreutils Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii coreutils 9.1-1ubuntu2 amd64GNU core utilities ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: coreutils 9.1-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Apr 23 10:48:56 2023 InstallationDate: Installed on 2023-04-23 (0 days ago) InstallationMedia: Ubuntu-Server 23.04 "Lunar Lobster" - Release amd64 (20230415) SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2017414/+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 1983100] Re: dotnet build intermittently crashes with segfault on Ubuntu 18.04
This updated debdiff (openssl-atexit-v2.debdiff) includes the DEP-3 headers, cleans up the patch names by prepending lp1983100- to each patch, and is rebased on the latest release in bionic-security. ** Description changed: [Impact] Bionic's OpenSSL 1.1.1 package (https://launchpad.net/ubuntu/bionic/+source/openssl) is the only version of openssl 1.1.1 on any distro that we've encountered that does not have support for the OPENSSL_NO_ATEXIT functionality from 1.1.1b (openssl/openssl@c2b3db2). The threading model in .NET has the possibility that background threads are still running when exit() is called, which can cause SIGSEGV if a background thread interacts with OpenSSL after/while it has unloaded. For that reason, we always initialize OpenSSL 1.1.1 with the OPENSSL_NO_ATEXIT flag (which, of all the distros we run on only has no effect on Bionic). We feel that the stability of applications on Ubuntu 18.04 would be improved if the functionality of OPENSSL_NO_ATEXIT was merged into the bionic openssl 1.1.1 package, even if the constant isn't published into the header for the dev package. Context: https://github.com/dotnet/runtime/issues/48411#issuecomment-1178405101 [Test Plan] The described behavior can be reproduced by passing the OPENSSL_NO_ATEXIT to the OPENSSL_init_ssl() call. The application will terminate with a SEGFAULT. More concretely, a minimal reproducer is: #include #include #include #ifndef OPENSSL_INIT_NO_ATEXIT #define OPENSSL_INIT_NO_ATEXIT 0x0008L #endif static void print_error_string() { printf("print_error_string:\n"); printf("ERR_reason_error_string(0) => %s\n", ERR_reason_error_string(0)); } int main(int argc, char* argv[]) { // register this handler first, so it runs last. atexit(print_error_string); OPENSSL_init_ssl( OPENSSL_INIT_ADD_ALL_CIPHERS | OPENSSL_INIT_ADD_ALL_DIGESTS | OPENSSL_INIT_LOAD_CONFIG | OPENSSL_INIT_NO_ATEXIT | OPENSSL_INIT_LOAD_CRYPTO_STRINGS | OPENSSL_INIT_LOAD_SSL_STRINGS, NULL); print_error_string(); return 0; } Building $ sudo apt install libssl-dev $ gcc test.c -lssl -lcrypto $ ./a.out print_error_string: ERR_reason_error_string(0) => (null) print_error_string: Segmentation fault (core dumped) + [Other Info] + All of these patches are included in upstream release 1.1.1b + - lp1983100-0001-Fix-shlibloadtest-to-properly-execute-the-dso_ref-te.patch + Fixes the shlibloadtest that was updated as part of #0005 + + - lp1983100-0002-Implement-OPENSSL_INIT_NO_ATEXIT.patch + Patch adds the OPENSSL_INIT_NO_ATEXIT option + + - lp1983100-0003-Don-t-link-shlibloadtest-against-libcrypto.patch + Additional fixes for shlibloadtest + + - lp1983100-0004-Fix-rpath-related-Linux-test_shlibload-failure.patch + Additional fixes for shlibloadtest + + - lp1983100-0005-Test-atexit-handlers.patch + Adds test for OPENSSL_INIT_NO_ATEXIT option and updates the shlibloadtest + + - lp1983100-0006-Introduce-a-no-pinshared-option.patch + This patch includes tests to ensure that if OPENSSL_INIT_NO_ATEXIT is not defined then the atexit() handler is run + + - lp1983100-0007-Support-_onexit-in-preference-to-atexit-on-Windows.patch + This patch ensures that atexit() is only called when on non-Windows systems as Windows uses _onexit() during library unloading + + All seven patches are required to ensure the correct logic and operation + of the OPENSSL_INIT_NO_ATEXIT option. + [Where problems could occur] The patches adds an option to the OPENSSL_init_crypto() function to disable the default behavior of calling of a cleanup function on application exit. The patch also includes a few bug fixes around various initializations that were supposed to happen once when running threaded but were not. These changes have the potential for regressions and it is conceivable that they lead to incorrect behavior. However, I have also backported and included all new testing functions in the hope that the changed behavior will get appropriate testing. ** Patch added: "openssl-atexit-v2.debdiff" https://bugs.launchpad.net/ubuntu/bionic/+source/openssl/+bug/1983100/+attachment/5670692/+files/openssl-atexit-v2.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/1983100 Title: dotnet build intermittently crashes with segfault on Ubuntu 18.04 Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Bionic: Incomplete Bug description: [Impact] Bionic's OpenSSL 1.1.1 package (https://launchpad.net/ubuntu/bionic/+source/openssl) is the only version of openssl 1.1.1 on any distro that we've encountered that does not have s
[Touch-packages] [Bug 2018330] Re: routel script gives shift errors
Web form kept defaulting to package "avahi" no matter how many times I typed in iproute2... ** Package changed: avahi (Ubuntu) => iproute2 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/2018330 Title: routel script gives shift errors Status in iproute2 package in Ubuntu: New Bug description: The routel(8) shell script is meant to format the output of ip(8) commands for human viewing, but the script is not robust enough. Running 22.04.2 LTS jammy jellyfish, freshly installed on an AWS EC2 instance and then "apt upgrade"d. (It's headless and remote, so it can't submit bug reports. I generated an apport file, but have no other Ubuntu system that could re-parse it to submit the report. But it's here if it would be useful.) The iproute2 package is: iproute2: Installed: 5.15.0-1ubuntu2 Candidate: 5.15.0-1ubuntu2 Version table: *** 5.15.0-1ubuntu2 500 500 http://us-east-2.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Here's the raw output of ip(8): $ ip route list table 0 default via 10.37.67.1 dev eth0 proto dhcp src 10.37.67.187 metric 100 10.37.64.2 via 10.37.67.1 dev eth0 proto dhcp src 10.37.67.187 metric 100 10.37.64.231 via 10.37.67.1 dev eth0 proto dhcp src 10.37.67.187 metric 100 10.37.65.30 via 10.37.67.1 dev eth0 proto dhcp src 10.37.67.187 metric 100 10.37.67.0/24 dev eth0 proto kernel scope link src 10.37.67.187 metric 100 10.37.67.1 dev eth0 proto dhcp scope link src 10.37.67.187 metric 100 local 10.37.67.187 dev eth0 table local proto kernel scope host src 10.37.67.187 broadcast 10.37.67.255 dev eth0 table local proto kernel scope link src 10.37.67.187 local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1 local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1 broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1 ::1 dev lo proto kernel metric 256 pref medium fe80::/64 dev eth0 proto kernel metric 256 pref medium local ::1 dev lo table local proto kernel metric 0 pref medium local fe80::458:96ff:fe61:6829 dev eth0 table local proto kernel metric 0 pref medium multicast ff00::/8 dev eth0 table local proto kernel metric 256 pref medium Running routel, however, yields this: $ routel targetgateway sourceprotoscopedev tbl default 10.37.67.110.37.67.187 dhcpeth0 10.37.64.2 10.37.67.110.37.67.187 dhcpeth0 10.37.64.231 10.37.67.110.37.67.187 dhcpeth0 10.37.65.30 10.37.67.110.37.67.187 dhcpeth0 10.37.67.0/ 2410.37.67.187 kernel link eth0 10.37.67.1 10.37.67.187 dhcp link eth0 10.37.67.187 local10.37.67.187 kernel host eth0 local 10.37.67.255 broadcast10.37.67.187 kernel link eth0 local 127.0.0.0/ 8local 127.0.0.1 kernel host lo local 127.0.0.1 local 127.0.0.1 kernel host lo local 127.255.255.255 broadcast 127.0.0.1 kernel link lo local /usr/bin/routel: 48: shift: ::1 kernel lo fe80::/ 64 kerneleth0 ::1 local kernel lo local fe80::458:96ff:fe61:6829 local kernel eth0 local can't shift that many Splitting stdout and stderr for readability: $ routel 2> /tmp/err targetgateway sourceprotoscopedev tbl default 10.37.67.110.37.67.187 dhcpeth0 10.37.64.2 10.37.67.110.37.67.187 dhcpeth0 10.37.64.231 10.37.67.110.37.67.187 dhcpeth0 10.37.65.30 10.37.67.110.37.67.187 dhcpeth0 10.37.67.0/ 2410.37.67.187 kernel link eth0 10.37.67.1 10.37.67.187 dhcp link eth0 10.37.67.187 local10.37.67.187 kernel host eth0 local 10.37.67.255 broadcast10.37.67.187 kernel link eth0 local 127.0.0.0/ 8local 127.0.0.1 kernel host lo local 127.0.0.1 local 127.0.0.1 kernel host lo local 127.255.255.255 broadcast 127.0.0.1 kernel link lo local ::1 kernel lo fe80::/ 64
[Touch-packages] [Bug 2018352] Re: Resolution wrong on external display when setting 100% scaling
** Also affects: nvidia-graphics-drivers-525 (Ubuntu) Importance: Undecided Status: New -- 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/2018352 Title: Resolution wrong on external display when setting 100% scaling Status in nvidia-graphics-drivers-525 package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: Resolution on external display is wrong when setting 100% scaling on it. It becomes too big, bigger than when set to 125% This happens with Xorg on Ubuntu 23.04 with NVIDIA GPU set as only GPU in the system ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-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 525.105.17 Tue Mar 28 18:02:59 UTC 2023 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-17ubuntu1) ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 3 08:27:32 2023 DistUpgraded: 2023-04-20 10:00:59,509 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: nvidia/525.105.17, 6.2.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] [10de:24dc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] [17aa:3a58] InstallationDate: Installed on 2023-02-09 (82 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 82N6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=2a43fd27-b65c-4d7a-bc19-b001521b0771 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-20 (12 days ago) dmi.bios.date: 03/07/2023 dmi.bios.release: 1.60 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN60WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.60 dmi.modalias: dmi:bvnLENOVO:bvrGKCN60WW:bd03/07/2023:br1.60:efr1.60:svnLENOVO:pn82N6:pvrLegion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-525/+bug/2018352/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1956102] Re: Time for the US is shown in 24h format. It should be 12h with AM/PM
** Also affects: hundredpapercuts Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1956102 Title: Time for the US is shown in 24h format. It should be 12h with AM/PM Status in GSettings Desktop Schemas: New Status in One Hundred Papercuts: New Status in gsettings-desktop-schemas package in Ubuntu: In Progress Status in subiquity package in Ubuntu: Won't Fix Status in gsettings-desktop-schemas package in Debian: New Bug description: Source- https://time.gov/ To manage notifications about this bug go to: https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1956102/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2018401] [NEW] Backport neon27 to 0.32.5 in Ubunto 22.04, 0.32.2 has bugs
Public bug reported: Due to a bug in neon27 it is not possible to mount WebDAV folders with davfs. See https://github.com/notroj/neon/issues/78 and https://github.com/notroj/neon/issues/88 This is solved in 0.32.5 as available in newer Ubuntu versions. Please provide a backport to upgrade neon27 to 0.32.5 in Ubuntu 22.04 ** Affects: neon27 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to neon27 in Ubuntu. https://bugs.launchpad.net/bugs/2018401 Title: Backport neon27 to 0.32.5 in Ubunto 22.04, 0.32.2 has bugs Status in neon27 package in Ubuntu: New Bug description: Due to a bug in neon27 it is not possible to mount WebDAV folders with davfs. See https://github.com/notroj/neon/issues/78 and https://github.com/notroj/neon/issues/88 This is solved in 0.32.5 as available in newer Ubuntu versions. Please provide a backport to upgrade neon27 to 0.32.5 in Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neon27/+bug/2018401/+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 2018261] Re: package udev 249.11-0ubuntu3.9 failed to install/upgrade: le sous-processus paquet udev script post-installation installé a renvoyé un état de sortie d'erreur 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2018261 Title: package udev 249.11-0ubuntu3.9 failed to install/upgrade: le sous- processus paquet udev script post-installation installé a renvoyé un état de sortie d'erreur 1 Status in systemd package in Ubuntu: Confirmed Bug description: upgrade error from 20.04 to 22.04 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: udev 249.11-0ubuntu3.9 ProcVersionSignature: Ubuntu 5.4.0-148.165-generic 5.4.231 Uname: Linux 5.4.0-148-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CustomUdevRuleFiles: 70-snap.gnome-characters.rules 95-oem-hotkey-osd.rules 70-snap.ubuntu-frame.rules 70-snap.firefox.rules 70-snap.snap-store.rules 70-snap.snapd.rules 70-snap.cups.rules 70-snap.gnome-calculator.rules 10-ubports.rules 70-snap.multipass.rules 70-snap.gnome-system-monitor.rules 70-snap.xibo-player.rules 70-snap.chromium.rules 70-snap.gnome-logs.rules Date: Mon May 1 21:25:19 2023 ErrorMessage: le sous-processus paquet udev script post-installation installé a renvoyé un état de sortie d'erreur 1 InstallationDate: Installed on 2021-01-22 (829 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20180507-04:30 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse Bus 001 Device 002: ID 413c:2106 Dell Computer Corp. QuietKey Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation NUC7i5DNKE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-148-generic root=UUID=527a0826-742d-45c2-bd7b-cb43d2f0fa5c ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.9 SourcePackage: systemd Title: package udev 249.11-0ubuntu3.9 failed to install/upgrade: le sous-processus paquet udev script post-installation installé a renvoyé un état de sortie d'erreur 1 UpgradeStatus: Upgraded to jammy on 2023-05-01 (0 days ago) dmi.bios.date: 03/04/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: DNKBLi5v.86A.0062.2019.0304.1757 dmi.board.name: NUC7i5DNB dmi.board.vendor: Intel Corporation dmi.board.version: J57626-506 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrDNKBLi5v.86A.0062.2019.0304.1757:bd03/04/2019:svnIntelCorporation:pnNUC7i5DNKE:pvrJ72865-506:rvnIntelCorporation:rnNUC7i5DNB:rvrJ57626-506:cvnIntelCorporation:ct35:cvr2: dmi.product.family: Intel NUC dmi.product.name: NUC7i5DNKE dmi.product.version: J72865-506 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2018261/+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 2011458] Re: ssh fails to rebind when it is killed with -HUP
Reuploaded with fixed autopkgtest and ready for re-review. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2011458 Title: ssh fails to rebind when it is killed with -HUP Status in openssh package in Ubuntu: In Progress Status in openssh source package in Kinetic: In Progress Bug description: [Impact] The sshd re-execution logic is generally broken with systemd socket activation, which means that (1) sshd fails when it is told to re-exec via SIGHUP (e.g. systemctl reload ssh), and (2) sshd fails when started in debug mode. [Test Case] (1) Test systemctl reload ssh: * On a machine with openssh-server installed, make a connection to localhost to activate ssh.service (the connection does not need to be complete, so you can just say "no" at the host key verification stage): $ ssh localhost [...] * Send SIGHUP to sshd by calling systemctl reload ssh: $ systemctl reload ssh * Check the service state: $ systemctl status ssh × ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: enabled) Drop-In: /etc/systemd/system/ssh.service.d └─00-socket.conf Active: failed (Result: exit-code) since Mon 2023-04-17 20:43:27 UTC; 4s ago Duration: 2min 44.132s TriggeredBy: ● ssh.socket Docs: man:sshd(8) man:sshd_config(5) Process: 1112 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255/EXCEPTION) Process: 1152 ExecReload=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS) Process: 1153 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS) Main PID: 1112 (code=exited, status=255/EXCEPTION) CPU: 79ms Apr 17 20:40:43 lunar systemd[1]: Started ssh.service - OpenBSD Secure Shell server. Apr 17 20:41:06 lunar sshd[1113]: Connection closed by 127.0.0.1 port 54666 [preauth] Apr 17 20:43:27 lunar systemd[1]: Reloading ssh.service - OpenBSD Secure Shell server... Apr 17 20:43:27 lunar sshd[1112]: Received SIGHUP; restarting. Apr 17 20:43:27 lunar systemd[1]: Reloaded ssh.service - OpenBSD Secure Shell server. Apr 17 20:43:27 lunar sshd[1112]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use. Apr 17 20:43:27 lunar sshd[1112]: error: Bind to port 22 on :: failed: Address already in use. Apr 17 20:43:27 lunar sshd[1112]: fatal: Cannot bind any address. Apr 17 20:43:27 lunar systemd[1]: ssh.service: Main process exited, code=exited, status=255/EXCEPTION Apr 17 20:43:27 lunar systemd[1]: ssh.service: Failed with result 'exit-code'. * On an affected machine, the service will fail as shown above. (2) Test debug mode: * On a machine with openssh-server installed, edit /etc/default/ssh to configure debug mode for sshd: $ cat /etc/default/ssh # Default settings for openssh-server. This file is sourced by /bin/sh from # /etc/init.d/ssh. # Options to pass to sshd SSHD_OPTS=-ddd * Attempt to make a connection to localhost: $ ssh localhost kex_exchange_identification: read: Connection reset by peer Connection reset by 127.0.0.1 port 22 * On an affected machine, the attempt will fail as shown above, and the service will be in a failed state: $ systemctl status ssh × ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: enabled) Drop-In: /etc/systemd/system/ssh.service.d └─00-socket.conf Active: failed (Result: exit-code) since Mon 2023-04-17 20:46:34 UTC; 2min 27s ago Duration: 5ms TriggeredBy: ● ssh.socket Docs: man:sshd(8) man:sshd_config(5) Process: 1166 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS) Process: 1167 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255/EXCEPTION) Main PID: 1167 (code=exited, status=255/EXCEPTION) CPU: 40ms Apr 17 20:46:34 lunar sshd[1167]: Server listening on :: port 22. Apr 17 20:46:34 lunar sshd[1167]: debug3: fd 4 is not O_NONBLOCK Apr 17 20:46:34 lunar sshd[1167]: debug1: Server will not fork when running in debugging mode. Apr 17 20:46:34 lunar sshd[1167]: debug3: send_rexec_state: entering fd = 7 config len 3456 Apr 17 20:46:34 lunar sshd[1167]: debug3: ssh_msg_send: type 0 Apr 17 20:46:34 lunar sshd[1167]: debug3: send_rexec_state: done Apr 17 20:46:34 lunar sshd[1167]: debug1: rexec start in 4 out 4 newsock 4 pipe -1 sock 7 Apr 17 20:46:34 lunar systemd[1]: Started ssh.service - OpenBSD Secure Shell server. Apr 17 20:46:34 lunar systemd[1]: ssh.service: Main process exited, code=exited, status=255/EXCEPTION Apr 17 20:46:34 lunar systemd[1]: ssh.service: Failed with result 'exit-code'. [Where problems could occur] The fix expands Ubuntu's patch for systemd socket activa
[Touch-packages] [Bug 2017786] Re: update script in ubuntu-meta not handling germinate or specified versions
** Changed in: ubuntukylin-meta (Ubuntu) Assignee: (unassigned) => handsome_feng (feng-kylin) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2017786 Title: update script in ubuntu-meta not handling germinate or specified versions Status in edubuntu-meta package in Ubuntu: Won't Fix Status in kubuntu-meta package in Ubuntu: New Status in lubuntu-meta package in Ubuntu: New Status in ubuntu-budgie-meta package in Ubuntu: New Status in ubuntu-mate-meta package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-unity-meta package in Ubuntu: New Status in ubuntucinnamon-meta package in Ubuntu: New Status in ubuntukylin-meta package in Ubuntu: New Status in ubuntustudio-meta package in Ubuntu: Won't Fix Status in xubuntu-meta package in Ubuntu: New Bug description: update script handled debootstrap and devscripts, does not handle germinate. also doesn't handle potential specified versions in the package directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edubuntu-meta/+bug/2017786/+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 2017984] Re: Browser "Save as" dialog is not in dark mode
** Summary changed: - Microsoft Edge "Save as" dialog is not in dark mode + Browser "Save as" dialog is not in dark mode ** Changed in: gtk+3.0 (Ubuntu) Status: Incomplete => Confirmed ** Changed in: yaru-theme (Ubuntu) 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/2017984 Title: Browser "Save as" dialog is not in dark mode Status in gtk+3.0 package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: Confirmed Bug description: After update to 23.04 I'm having the following issue. In dark mode of Yaru-dark theme, when downloading the file and choosing the "Save as" option - popup window for folder selection is not in dark mode. When using Xorg session problem is not reproduced. The same applies for upload logic. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 28 12:31:55 2023 DistUpgraded: 2023-04-25 21:06:12,927 DEBUG icon theme changed, re-reading DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:508f] InstallationDate: Installed on 2022-08-26 (244 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20X4S1GH08 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro usbcore.autosuspend=-1 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-25 (2 days ago) dmi.bios.date: 11/22/2022 dmi.bios.release: 1.60 dmi.bios.vendor: LENOVO dmi.bios.version: R1JET60W (1.60 ) dmi.board.asset.tag: Not Available dmi.board.name: 20X4S1GH08 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.48 dmi.modalias: dmi:bvnLENOVO:bvrR1JET60W(1.60):bd11/22/2022:br1.60:efr1.48:svnLENOVO:pn20X4S1GH08:pvrThinkPadL15Gen2:rvnLENOVO:rn20X4S1GH08:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20X4_BU_Think_FM_ThinkPadL15Gen2: dmi.product.family: ThinkPad L15 Gen 2 dmi.product.name: 20X4S1GH08 dmi.product.sku: LENOVO_MT_20X4_BU_Think_FM_ThinkPad L15 Gen 2 dmi.product.version: ThinkPad L15 Gen 2 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2017984/+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