[Touch-packages] [Bug 2017323] [NEW] Triple 4K monitor setup with fractional scaling truncated
Public bug reported: I have three monitors arranged horizontally left-to-right, with fractional scaling enabled in Xorg mode (not Wayland): #1: laptop, 3840x2400 native, scaled at 225% #2: external monitor 1, 3840x2160 native, scaled at 150% (main display) #3: external monitor 2, 3840x2160 native, scaled at 150% In this setup, a little more than half of the rightmost monitor is truncated black. I suspect it is caused by oversampled screens (fractional scaling) not fitting into the maximum framebuffer size of 16384x16384, as evidenced by the following xrandr(1): $ xrandr | awk '/^[^ ]/ && $2 != "disconnected"' Screen 0: minimum 320 x 200, current 16384 x 4320, maximum 16384 x 16384 eDP-1 connected 5112x3195+0+0 (normal left inverted right x axis y axis) 366mm x 229mm DP-2 connected primary 7680x4320+5112+0 (normal left inverted right x axis y axis) 597mm x 336mm DP-3 connected 7680x4320+12792+0 (normal left inverted right x axis y axis) 597mm x 336mm ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xserver-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 zfs zunicode zavl icp zcommon znvpair .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: ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 21 18:51:29 2023 DistUpgraded: 2023-04-20 13:31:05,017 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Alder Lake-P Integrated Graphics Controller [1028:0aff] NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2520] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GA106M [GeForce RTX 3060 Mobile / Max-Q] [1028:0aff] MachineType: Dell Inc. XPS 17 9720 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_bm2y56@/vmlinuz-6.2.0-20-generic root=ZFS=rpool/ROOT/ubuntu_bm2y56 ro init_on_alloc=0 i915.enable_psr2_sel_fetch=0 SourcePackage: xorg UpgradeStatus: Upgraded to lunar on 2023-04-20 (1 days ago) dmi.bios.date: 03/20/2023 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 0W7GHH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd03/20/2023:br1.15:svnDellInc.:pnXPS179720:pvr:rvnDellInc.:rn0W7GHH:rvrA00:cvnDellInc.:ct10:cvr:sku0AFF: dmi.product.family: XPS dmi.product.name: XPS 17 9720 dmi.product.sku: 0AFF dmi.sys.vendor: Dell Inc. mtime.conffile..etc.logrotate.d.apport: 2023-01-31T20:57:54.273339 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/2017323 Title: Triple 4K monitor setup with fractional scaling truncated Status in xorg package in Ubuntu: New Bug description: I have three monitors arranged horizontally left-to-right, with fractional scaling enabled in Xorg mode (not Wayland): #1: laptop, 3840x2400 native, scaled at 225% #2: external monitor 1, 3840x2160 native, scaled at 150% (main display) #3: external monitor 2, 3840x2160 native, scaled at 150% In this setup, a little more than half of the rightmost monitor is truncated black. I suspect it is caused by oversampled screens (fractional scaling) not fitting into the maximum framebuffer size of 16384x16384, as evidenced by
[Touch-packages] [Bug 1978301] Re: Broken contact URL in German translation
The reason for that is described in the git commit message: "`GLib.markup_escape_text` takes a `str` as well. So converting `text` to `bytes` is not needed." That claim is verified by the added test cases. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1978301 Title: Broken contact URL in German translation Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Jammy: Incomplete Bug description: Impact -- All German users (and all translations that use "%s." in their translation template) will get a broken URL link for bug reports against snaps (e.g. Firefox). Test Case - 1. Execute following command: LANGUAGE=de ubuntu-bug firefox 2. Click on the URL 3. A browser window should open and not display a 404 page Regression Potential Since there was no test case for converting text to HTML before this fix, there might be some URLs that will become broken by this fix. Original Description "LANGUAGE=de ubuntu-bug firefox" end up in a dialog saying: firefox wird durch einen von mozilla veröffentlichten Snap bereitgestellt. Für Hilfe gehen Sie über https://support.mozilla.org/kb/file-bug-report-or-feature-request- mozilla. The dot at the end is included in the URL link. The dot makes the URL link broken. The regular expression in gtk/apport-gtk for http URLs should become smarter. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1978301/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2017317] Re: Ubuntu: upon reboot, forever waiting for encrypted swapfile ...
I've initially reported this bug there https://gitlab.com/cryptsetup/cryptsetup/-/issues/811#note_1361818938 But got recommended posting it here instead. There, Milan Broz added following: "My guess here is that /etc/crypttab is missing something about cryptswap device, but we cannot do anything with these problems in the upstream cryptsetup project (also, Debian/Ubuntu specific cryptsetup tools are not even maintained upstream." -- 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/2017317 Title: Ubuntu: upon reboot, forever waiting for encrypted swapfile ... Status in systemd package in Ubuntu: New Bug description: ### Issue description When restarting my machine, cryptsetup waits forever. Waiting for the swapfile. Unable to start Ubuntu at all. Error message is: ``` cryptsetup: Waiting for encrypted source device /swapfile... ``` ### Steps for reproducing the issue 1. Do a fresh installation of Ubuntu, unencrypted. 2. Later, due to restrictions at work, encrypt Ubuntu POST installation accordingly to this article: https://jumpcloud.com/blog/how-to-encrypt-ubuntu-20-04-desktop-post-installation 3. Reboot, all works fine, but ... 4. Later, after a couple of months, install a new Linux kernel and then ... 5. Upon boot cryptsetup gets stuck, waits forever. See attached photo. ### Additional info I've found a temporary, painful workaround by rebooting in recovery mode and running this command every time: ``` sudo update-initramfs -u -k all ``` Then I can boot again. But I have to do this every time. Why? ### Debug log Hard to say but here's the output of this command `journalctl | grep crypt`, not sure if you can find anything interesting about it: ``` Apr 21 13:48:28 M1 audit[179547]: AVC apparmor="DENIED" operation="getattr" class="file" info="Failed name lookup - disconnected path" error=-13 profile="/usr/bin/evince-thumbnailer" name="home/.ecryptfs/michael-heuberger/.Private/ECRYPTFS_FNEK_ENCRYPTED.FWaKkF5ZO-vAFETGnoPriOb55KN8iA.SprD0W8LFNkfXu75b-QusjTdAA---/ECRYPTFS_FNEK_ENCRYPTED.FXaKkF5ZO-vAFETGnoPriOb55KN8iA.SprD0JjExLlqv3Fk6x4GGYcQdjXda2554lHGsMAmCwjYZWGA-" pid=179547 comm="evince-thumbnai" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Apr 21 17:01:49 M1 gdm-password][219451]: pam_ecryptfs: pam_sm_authenticate: /home/michael-heuberger is already mounted Apr 21 17:26:59 M1 systemd[1]: Requested transaction contradicts existing jobs: Transaction for plymouth-quit.service/start is destructive (dev-disk-by\x2did-dm\x2duuid\x2dCRYPT\x2dPLAIN\x2dcryptswap1.swap has 'stop' job queued, but 'start' is included in transaction). Apr 21 17:26:59 M1 systemd[1]: gdm.service: Failed to enqueue OnFailure= job, ignoring: Transaction for plymouth-quit.service/start is destructive (dev-disk-by\x2did-dm\x2duuid\x2dCRYPT\x2dPLAIN\x2dcryptswap1.swap has 'stop' job queued, but 'start' is included in transaction). Apr 21 17:26:59 M1 systemd[3094]: Stopping GnuPG cryptographic agent and passphrase cache... Apr 21 17:27:00 M1 systemd[3094]: Stopped GnuPG cryptographic agent and passphrase cache. Apr 21 17:27:07 M1 systemd[1]: Stopped target Local Encrypted Volumes. Apr 21 17:27:08 M1 umount.ecryptfs[231225]: Failed to find key with sig [2bda85c181b04823]: Required key not available Apr 21 17:27:08 M1 umount.ecryptfs[231225]: Failed to find key with sig [96c111e5680ecc45]: Required key not available Apr 21 17:27:09 M1 systemd[1]: Deactivating swap /dev/disk/by-id/dm-name-cryptswap1... Apr 21 17:27:09 M1 systemd[1]: dev-disk-by\x2dlabel-cryptswap1.swap: Deactivated successfully. Apr 21 17:27:09 M1 systemd[1]: Deactivated swap /dev/disk/by-label/cryptswap1. ``` Do you have any tips, advice please, how to fix this, how can I reboot my machine without running `update-initramfs` every time? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2017317/+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 2017317] [NEW] Ubuntu: upon reboot, forever waiting for encrypted swapfile ...
Public bug reported: ### Issue description When restarting my machine, cryptsetup waits forever. Waiting for the swapfile. Unable to start Ubuntu at all. Error message is: ``` cryptsetup: Waiting for encrypted source device /swapfile... ``` ### Steps for reproducing the issue 1. Do a fresh installation of Ubuntu, unencrypted. 2. Later, due to restrictions at work, encrypt Ubuntu POST installation accordingly to this article: https://jumpcloud.com/blog/how-to-encrypt-ubuntu-20-04-desktop-post-installation 3. Reboot, all works fine, but ... 4. Later, after a couple of months, install a new Linux kernel and then ... 5. Upon boot cryptsetup gets stuck, waits forever. See attached photo. ### Additional info I've found a temporary, painful workaround by rebooting in recovery mode and running this command every time: ``` sudo update-initramfs -u -k all ``` Then I can boot again. But I have to do this every time. Why? ### Debug log Hard to say but here's the output of this command `journalctl | grep crypt`, not sure if you can find anything interesting about it: ``` Apr 21 13:48:28 M1 audit[179547]: AVC apparmor="DENIED" operation="getattr" class="file" info="Failed name lookup - disconnected path" error=-13 profile="/usr/bin/evince-thumbnailer" name="home/.ecryptfs/michael-heuberger/.Private/ECRYPTFS_FNEK_ENCRYPTED.FWaKkF5ZO-vAFETGnoPriOb55KN8iA.SprD0W8LFNkfXu75b-QusjTdAA---/ECRYPTFS_FNEK_ENCRYPTED.FXaKkF5ZO-vAFETGnoPriOb55KN8iA.SprD0JjExLlqv3Fk6x4GGYcQdjXda2554lHGsMAmCwjYZWGA-" pid=179547 comm="evince-thumbnai" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Apr 21 17:01:49 M1 gdm-password][219451]: pam_ecryptfs: pam_sm_authenticate: /home/michael-heuberger is already mounted Apr 21 17:26:59 M1 systemd[1]: Requested transaction contradicts existing jobs: Transaction for plymouth-quit.service/start is destructive (dev-disk-by\x2did-dm\x2duuid\x2dCRYPT\x2dPLAIN\x2dcryptswap1.swap has 'stop' job queued, but 'start' is included in transaction). Apr 21 17:26:59 M1 systemd[1]: gdm.service: Failed to enqueue OnFailure= job, ignoring: Transaction for plymouth-quit.service/start is destructive (dev-disk-by\x2did-dm\x2duuid\x2dCRYPT\x2dPLAIN\x2dcryptswap1.swap has 'stop' job queued, but 'start' is included in transaction). Apr 21 17:26:59 M1 systemd[3094]: Stopping GnuPG cryptographic agent and passphrase cache... Apr 21 17:27:00 M1 systemd[3094]: Stopped GnuPG cryptographic agent and passphrase cache. Apr 21 17:27:07 M1 systemd[1]: Stopped target Local Encrypted Volumes. Apr 21 17:27:08 M1 umount.ecryptfs[231225]: Failed to find key with sig [2bda85c181b04823]: Required key not available Apr 21 17:27:08 M1 umount.ecryptfs[231225]: Failed to find key with sig [96c111e5680ecc45]: Required key not available Apr 21 17:27:09 M1 systemd[1]: Deactivating swap /dev/disk/by-id/dm-name-cryptswap1... Apr 21 17:27:09 M1 systemd[1]: dev-disk-by\x2dlabel-cryptswap1.swap: Deactivated successfully. Apr 21 17:27:09 M1 systemd[1]: Deactivated swap /dev/disk/by-label/cryptswap1. ``` Do you have any tips, advice please, how to fix this, how can I reboot my machine without running `update-initramfs` every time? Thanks! ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot of error message upon boot" https://bugs.launchpad.net/bugs/2017317/+attachment/5666561/+files/IMG_2291.jpg ** Bug watch added: gitlab.com/cryptsetup/cryptsetup/-/issues #811 https://gitlab.com/cryptsetup/cryptsetup/-/issues/811 -- 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/2017317 Title: Ubuntu: upon reboot, forever waiting for encrypted swapfile ... Status in systemd package in Ubuntu: New Bug description: ### Issue description When restarting my machine, cryptsetup waits forever. Waiting for the swapfile. Unable to start Ubuntu at all. Error message is: ``` cryptsetup: Waiting for encrypted source device /swapfile... ``` ### Steps for reproducing the issue 1. Do a fresh installation of Ubuntu, unencrypted. 2. Later, due to restrictions at work, encrypt Ubuntu POST installation accordingly to this article: https://jumpcloud.com/blog/how-to-encrypt-ubuntu-20-04-desktop-post-installation 3. Reboot, all works fine, but ... 4. Later, after a couple of months, install a new Linux kernel and then ... 5. Upon boot cryptsetup gets stuck, waits forever. See attached photo. ### Additional info I've found a temporary, painful workaround by rebooting in recovery mode and running this command every time: ``` sudo update-initramfs -u -k all ``` Then I can boot again. But I have to do this every time. Why? ### Debug log Hard to say but here's the output of this command `journalctl | grep crypt`, not sure if you can find anything interesting about it: ``` Apr 21 13:48:28 M1 audit[179547]: AVC
[Touch-packages] [Bug 1951586] Re: Need option to specify wifi regulatory domain
Shoot, guess the wait will be for 20.04 to be updated. -- 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/1951586 Title: Need option to specify wifi regulatory domain Status in cloud-init: Invalid Status in netplan: Fix Released Status in NetworkManager: New Status in netplan.io package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Incomplete Status in netplan.io source package in Jammy: Triaged Status in network-manager source package in Jammy: Incomplete Status in netplan.io source package in Kinetic: Fix Released Status in network-manager source package in Kinetic: Incomplete Bug description: It would be nice if netplan offered an option to specify the wifi regulatory domain (country code). For devices such as the Raspberry Pi you are currently advertising that users can simply setup Ubuntu Server headless by putting the wifi configuration details in cloudinit/netplan's "network-config" on the FAT partition of the SD card: https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet But an option to set the wifi country code there does not seem to exist, so may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1951586/+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 2017076] Re: default Chinese font in snap apps is ugly
** Changed in: fontconfig (Ubuntu) Importance: High => Undecided ** Changed in: fontconfig (Ubuntu) Status: New => Invalid ** Changed in: language-selector (Ubuntu) Status: New => Invalid ** Changed in: snappy Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font in snap apps is ugly Status in Snappy: Confirmed Status in fontconfig package in Ubuntu: Invalid Status in language-selector package in Ubuntu: Invalid Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 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 CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2017076/+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 2017076] Re: default Chinese font in snap apps is ugly
On 2023-04-21 21:18, Sebastien Bacher wrote: > @Gunnar, that's because the only channel which has the core22 > firefox atm is stable/ubuntu-23.04 (which is specific to Lunar). So, then I just learned that if you are on lunar aka 23.04 and install firefox from the latest/stable channel, you get something different compared to installing it from the latest/stable/ubuntu-23.04 channel. Hmm.. I recall someone who talked earlier today about the need to be an expert... ;) > Your testing suggest that the issue was the one I mentioned earlier > that https://github.com/ubuntu/gnome-sdk/pull/72 is missing from the > core22 based gnome sdk Right, by doing snap refresh firefox --channel=latest/stable/ubuntu-23.04 (with the Chinese locale) I could finally reproduce the default font issue. So that seems to be it for this bug. This exercise raised a few other font related issues in my head, but they are less urgent. Let's take those separately later. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font in snap apps is ugly Status in Snappy: Confirmed Status in fontconfig package in Ubuntu: Invalid Status in language-selector package in Ubuntu: Invalid Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 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 CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2017076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1978301] Re: Broken contact URL in German translation
The refactor of apport-gtk in the jammy queue includes this change: -if not isinstance(text, bytes): -text = text.encode('UTF-8') This code is not included in the refactored function. Why is it safe to drop this code? ** Changed in: apport (Ubuntu Jammy) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1978301 Title: Broken contact URL in German translation Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Jammy: Incomplete Bug description: Impact -- All German users (and all translations that use "%s." in their translation template) will get a broken URL link for bug reports against snaps (e.g. Firefox). Test Case - 1. Execute following command: LANGUAGE=de ubuntu-bug firefox 2. Click on the URL 3. A browser window should open and not display a 404 page Regression Potential Since there was no test case for converting text to HTML before this fix, there might be some URLs that will become broken by this fix. Original Description "LANGUAGE=de ubuntu-bug firefox" end up in a dialog saying: firefox wird durch einen von mozilla veröffentlichten Snap bereitgestellt. Für Hilfe gehen Sie über https://support.mozilla.org/kb/file-bug-report-or-feature-request- mozilla. The dot at the end is included in the URL link. The dot makes the URL link broken. The regular expression in gtk/apport-gtk for http URLs should become smarter. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1978301/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2017224] 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/2017224 Title: Cannot enable bluetooth in gnome-shell Status in bluez package in Ubuntu: New Status in gnome-settings-daemon package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: After upgrade to 23.04, Bluetooth service is started but can't enable it in gnome-shell. Apr 21 11:34:15 ZB systemd[1]: Starting bluetooth.service - Bluetooth service... Apr 21 11:34:15 ZB systemd[1403]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555) Apr 21 11:34:15 ZB bluetoothd[1403]: Bluetooth daemon 5.66 Apr 21 11:34:15 ZB bluetoothd[1403]: Starting SDP server Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/vcp.c:vcp_init() D-Bus experimental not enabled Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to init vcp plugin Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to init mcp plugin Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to init bap plugin Apr 21 11:34:15 ZB systemd[1]: Started bluetooth.service - Bluetooth service. Apr 21 11:34:15 ZB bluetoothd[1403]: Bluetooth management interface 1.22 initialized I installed the latest linux-firmware from the repo but it didn't help. # dmesg | grep -i bluetooth [ 18.861759] Bluetooth: Core ver 2.22 [ 18.863617] NET: Registered PF_BLUETOOTH protocol family [ 18.863621] Bluetooth: HCI device and connection manager initialized [ 18.863628] Bluetooth: HCI socket layer initialized [ 18.863631] Bluetooth: L2CAP socket layer initialized [ 18.863638] Bluetooth: SCO socket layer initialized [ 19.146683] Bluetooth: hci0: Bootloader revision 0.4 build 0 week 30 2018 [ 19.147702] Bluetooth: hci0: Device revision is 2 [ 19.147707] Bluetooth: hci0: Secure boot is enabled [ 19.147709] Bluetooth: hci0: OTP lock is enabled [ 19.147712] Bluetooth: hci0: API lock is enabled [ 19.147714] Bluetooth: hci0: Debug lock is disabled [ 19.147716] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 19.150729] Bluetooth: hci0: Found device firmware: intel/ibt-19-0-4.sfi [ 19.150841] Bluetooth: hci0: Boot Address: 0x24800 [ 19.150843] Bluetooth: hci0: Firmware Version: 15-45.22 [ 19.998952] Bluetooth: hci0: urb 8cd2a5b0 failed to resubmit (2) [ 20.015315] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 20.015321] Bluetooth: BNEP filters: protocol multicast [ 20.015329] Bluetooth: BNEP socket layer initialized [ 22.005627] Bluetooth: hci0: command 0xfc09 tx timeout [ 30.037760] Bluetooth: hci0: Failed to send firmware data (-110) [ 30.037855] Bluetooth: hci0: Intel reset sent to retry FW download [ 32.213626] Bluetooth: hci0: Failed to read MSFT supported features (-110) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: bluez 5.66-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 21 11:44:40 2023 InstallationDate: Installed on 2023-01-04 (106 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) InterestingModules: bnep btusb bluetooth MachineType: ASUSTeK COMPUTER INC. ZenBook UX435EG_UX435EG ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash SourcePackage: bluez UpgradeStatus: Upgraded to lunar on 2023-04-21 (0 days ago) dmi.bios.date: 04/22/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX435EG.315 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX435EG dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX435EG.315:bd04/22/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX435EG_UX435EG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX435EG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX435EG_UX435EG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: mtime.conffile..etc.bluetooth.input.conf: 2023-02-28T07:11:41.547346 To manage notifications about this bug go
[Touch-packages] [Bug 2017224] Re: Cannot enable bluetooth in gnome-shell
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: After upgrade to 23.04, Bluetooth service is started but can't enable it in gnome-shell. Apr 21 11:34:15 ZB systemd[1]: Starting bluetooth.service - Bluetooth service... Apr 21 11:34:15 ZB systemd[1403]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555) Apr 21 11:34:15 ZB bluetoothd[1403]: Bluetooth daemon 5.66 Apr 21 11:34:15 ZB bluetoothd[1403]: Starting SDP server Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/vcp.c:vcp_init() D-Bus experimental not enabled Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to init vcp plugin Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to init mcp plugin Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to init bap plugin Apr 21 11:34:15 ZB systemd[1]: Started bluetooth.service - Bluetooth service. Apr 21 11:34:15 ZB bluetoothd[1403]: Bluetooth management interface 1.22 initialized + + + + I installed the latest linux-firmware from the repo but it didn't help. + + # dmesg | grep -i bluetooth + [ 18.861759] Bluetooth: Core ver 2.22 + [ 18.863617] NET: Registered PF_BLUETOOTH protocol family + [ 18.863621] Bluetooth: HCI device and connection manager initialized + [ 18.863628] Bluetooth: HCI socket layer initialized + [ 18.863631] Bluetooth: L2CAP socket layer initialized + [ 18.863638] Bluetooth: SCO socket layer initialized + [ 19.146683] Bluetooth: hci0: Bootloader revision 0.4 build 0 week 30 2018 + [ 19.147702] Bluetooth: hci0: Device revision is 2 + [ 19.147707] Bluetooth: hci0: Secure boot is enabled + [ 19.147709] Bluetooth: hci0: OTP lock is enabled + [ 19.147712] Bluetooth: hci0: API lock is enabled + [ 19.147714] Bluetooth: hci0: Debug lock is disabled + [ 19.147716] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 + [ 19.150729] Bluetooth: hci0: Found device firmware: intel/ibt-19-0-4.sfi + [ 19.150841] Bluetooth: hci0: Boot Address: 0x24800 + [ 19.150843] Bluetooth: hci0: Firmware Version: 15-45.22 + [ 19.998952] Bluetooth: hci0: urb 8cd2a5b0 failed to resubmit (2) + [ 20.015315] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 + [ 20.015321] Bluetooth: BNEP filters: protocol multicast + [ 20.015329] Bluetooth: BNEP socket layer initialized + [ 22.005627] Bluetooth: hci0: command 0xfc09 tx timeout + [ 30.037760] Bluetooth: hci0: Failed to send firmware data (-110) + [ 30.037855] Bluetooth: hci0: Intel reset sent to retry FW download + [ 32.213626] Bluetooth: hci0: Failed to read MSFT supported features (-110) + ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: bluez 5.66-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 21 11:44:40 2023 InstallationDate: Installed on 2023-01-04 (106 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) InterestingModules: bnep btusb bluetooth MachineType: ASUSTeK COMPUTER INC. ZenBook UX435EG_UX435EG ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash SourcePackage: bluez UpgradeStatus: Upgraded to lunar on 2023-04-21 (0 days ago) dmi.bios.date: 04/22/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX435EG.315 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX435EG dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX435EG.315:bd04/22/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX435EG_UX435EG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX435EG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX435EG_UX435EG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: - + mtime.conffile..etc.bluetooth.input.conf: 2023-02-28T07:11:41.547346 -- 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/2017224 Title: Cannot enable bluetooth in gnome-shell Status in bluez package in Ubuntu: New Status in gnome-settings-daemon package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: After upgrade to
[Touch-packages] [Bug 2015126] Re: systemd doesn't successfully enforce RuntimeMaxSec for gnome session
Okay, so internally systemd is using CLOCK_MONOTONIC for the event source that counts up to RuntimeMaxSec, and CLOCK_MONOTONIC does not count the time when the system is suspended. Your use case wants CLOCK_BOOTTIME, which does count time when the system is suspended. I will work on a fix for this. [1] https://man7.org/linux/man-pages/man3/clock_gettime.3.html -- 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/2015126 Title: systemd doesn't successfully enforce RuntimeMaxSec for gnome session Status in systemd package in Ubuntu: Triaged Status in systemd source package in Jammy: Triaged Status in systemd source package in Kinetic: Triaged Bug description: On Jammy, I have configured systemd to set RuntimeMaxSec on certain user sessions: # cat /run/systemd/transient/session-43.scope # This is a transient unit file, created programmatically via the systemd API. Do not edit. [Scope] Slice=user-1000.slice [Unit] Description=Session 43 of User xavier Wants=user-runtime-dir@1000.service Wants=user@1000.service After=systemd-logind.service After=systemd-user-sessions.service After=user-runtime-dir@1000.service After=user@1000.service RequiresMountsFor=/home/xavier [Scope] SendSIGHUP=yes TasksMax=infinity RuntimeMaxSec=2h # I have verified that this does what's expected on an ssh session, and kills the session when the runtime max has been reached. But on a GNOME login session (using X), this apparently doesn't work: the session is still running 17 hours after it should have been terminated. My guess is that systemd is ending the session by sending a signal that is being ignored by the GNOME login session? RuntimeMaxSec is not very useful if it's advisory... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.7 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 3 12:20:22 2023 InstallationDate: Installed on 2023-01-22 (70 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 2306CTO ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=c415e6a8-5cd2-4d08-913d-14c00b792374 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.release: 2.57 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:br2.57:efr1.13:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2306: dmi.product.family: ThinkPad X230 dmi.product.name: 2306CTO dmi.product.sku: LENOVO_MT_2306 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2015126/+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 1906138] Re: Indeterminate Qt progress bars don't display properly in 20.04
Okay, I can try patching out the QT_NO_ANIMATION line in our packaging. ** No longer affects: qtbase-opensource-src (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1906138 Title: Indeterminate Qt progress bars don't display properly in 20.04 Status in qtstyleplugins-src package in Ubuntu: New Bug description: In Ubuntu MATE 20.04, a Qt program with an indeterminate progress bar (meaning its minimum and maximum values have both been set to zero) does not display properly. It is supposed to animate in a way that shows that something is happening with an unknown time remaining. Instead, it sits still with its progress bar showing approximately 25 to 30% progress. To test this, make a simple Qt program with a QProgressBar in the main window, and add these lines to the constructor of the main window: ui->progressBar->setMinimum(0); ui->progressBar->setMaximum(0); This problem is not present in standard Ubuntu 20.04. Standard Ubuntu correctly animates the indeterminate progress bar. It's unclear to me which package is at fault, but it seems to be something specific to Ubuntu MATE because standard Ubuntu 20.04 doesn't have this problem. Ubuntu MATE 18.04 also has this problem with Qt 5. With Qt 4 it doesn't have this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtstyleplugins-src/+bug/1906138/+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 1906138] Re: Indeterminate Qt progress bars don't display properly in 20.04
Wow, thanks for responding so quickly! That's great to hear. FWIW, to this day, Ubuntu MATE 23.04 is still using the gtk2 style plugin (export QT_QPA_PLATFORMTHEME=gtk2 in /etc/profile.d) so indeterminate progress bars have been broken in Ubuntu MATE for years. I think there would be value in at least patching this in Ubuntu's build or something... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1906138 Title: Indeterminate Qt progress bars don't display properly in 20.04 Status in qtbase-opensource-src package in Ubuntu: New Status in qtstyleplugins-src package in Ubuntu: New Bug description: In Ubuntu MATE 20.04, a Qt program with an indeterminate progress bar (meaning its minimum and maximum values have both been set to zero) does not display properly. It is supposed to animate in a way that shows that something is happening with an unknown time remaining. Instead, it sits still with its progress bar showing approximately 25 to 30% progress. To test this, make a simple Qt program with a QProgressBar in the main window, and add these lines to the constructor of the main window: ui->progressBar->setMinimum(0); ui->progressBar->setMaximum(0); This problem is not present in standard Ubuntu 20.04. Standard Ubuntu correctly animates the indeterminate progress bar. It's unclear to me which package is at fault, but it seems to be something specific to Ubuntu MATE because standard Ubuntu 20.04 doesn't have this problem. Ubuntu MATE 18.04 also has this problem with Qt 5. With Qt 4 it doesn't have this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1906138/+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 1906138] Re: Indeterminate Qt progress bars don't display properly in 20.04
I don't remember why I disabled animation in that commit. Probably I had some build failure when it's enabled. Anyway, qtstyleplugins is abandoned and no longer developed (the last commit was more than 6 years ago). I recommend to NOT include it in dependencies of any package. Qt 6.5.0 will have a much improved GTK 3 integration support: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=4ca8a6840842d5ff. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1906138 Title: Indeterminate Qt progress bars don't display properly in 20.04 Status in qtbase-opensource-src package in Ubuntu: New Status in qtstyleplugins-src package in Ubuntu: New Bug description: In Ubuntu MATE 20.04, a Qt program with an indeterminate progress bar (meaning its minimum and maximum values have both been set to zero) does not display properly. It is supposed to animate in a way that shows that something is happening with an unknown time remaining. Instead, it sits still with its progress bar showing approximately 25 to 30% progress. To test this, make a simple Qt program with a QProgressBar in the main window, and add these lines to the constructor of the main window: ui->progressBar->setMinimum(0); ui->progressBar->setMaximum(0); This problem is not present in standard Ubuntu 20.04. Standard Ubuntu correctly animates the indeterminate progress bar. It's unclear to me which package is at fault, but it seems to be something specific to Ubuntu MATE because standard Ubuntu 20.04 doesn't have this problem. Ubuntu MATE 18.04 also has this problem with Qt 5. With Qt 4 it doesn't have this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1906138/+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 1906138] Re: Indeterminate Qt progress bars don't display properly in 20.04
I finally found some time to look further into this, it appears to be an upstream problem with qtstyleplugins. The logic in the gtk2 plugin (used by Ubuntu MATE by default) doesn't animate indeterminate progress bars if QT_NO_ANIMATION is defined, yet it seems to be intentionally defined to disable animation for some reason: https://code.qt.io/cgit/qt/qtstyleplugins.git/commit/src/plugins/styles/gtk2/gtk2.pro?id=102da7d50231fc5723dba6e72340bef3d29471aa Removing DEFINES += QT_NO_ANIMATION from gtk2.pro fixes the problem and allows the indeterminate progress bars to animate properly. ** Also affects: qtstyleplugins-src (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1906138 Title: Indeterminate Qt progress bars don't display properly in 20.04 Status in qtbase-opensource-src package in Ubuntu: New Status in qtstyleplugins-src package in Ubuntu: New Bug description: In Ubuntu MATE 20.04, a Qt program with an indeterminate progress bar (meaning its minimum and maximum values have both been set to zero) does not display properly. It is supposed to animate in a way that shows that something is happening with an unknown time remaining. Instead, it sits still with its progress bar showing approximately 25 to 30% progress. To test this, make a simple Qt program with a QProgressBar in the main window, and add these lines to the constructor of the main window: ui->progressBar->setMinimum(0); ui->progressBar->setMaximum(0); This problem is not present in standard Ubuntu 20.04. Standard Ubuntu correctly animates the indeterminate progress bar. It's unclear to me which package is at fault, but it seems to be something specific to Ubuntu MATE because standard Ubuntu 20.04 doesn't have this problem. Ubuntu MATE 18.04 also has this problem with Qt 5. With Qt 4 it doesn't have this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1906138/+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 2017311] [NEW] gdb wrong dependency to python3.10
Public bug reported: Just updated to Ubuntu 13.04 and gdb needs libpython3.10.so.1.0 even though it depends on 3.11 I have removed and installed gdb to make sure I got the latest version. gdb: Installed: 13.1-2ubuntu2 Candidate: 13.1-2ubuntu2 Version table: *** 13.1-2ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status but when I run it > gdb: error while loading shared libraries: libpython3.10.so.1.0: cannot open shared object file: No such file or directory Which is correct because > ldd $(which gdb) > libpython3.10.so.1.0 => not found ** Affects: gdb (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/2017311 Title: gdb wrong dependency to python3.10 Status in gdb package in Ubuntu: New Bug description: Just updated to Ubuntu 13.04 and gdb needs libpython3.10.so.1.0 even though it depends on 3.11 I have removed and installed gdb to make sure I got the latest version. gdb: Installed: 13.1-2ubuntu2 Candidate: 13.1-2ubuntu2 Version table: *** 13.1-2ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status but when I run it > gdb: error while loading shared libraries: libpython3.10.so.1.0: cannot open shared object file: No such file or directory Which is correct because > ldd $(which gdb) > libpython3.10.so.1.0 => not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2017311/+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 2015126] Re: systemd doesn't successfully enforce RuntimeMaxSec for gnome session
Thanks, that is very helpful. I tested this for service units too, and got the same result: $ systemd-run -u test-1.service -p RuntimeMaxSec=1m /usr/bin/bash -c 'while true; do sleep 1; done' $ systemctl suspend # Waited a bit... After resume: $ systemctl status test-1.service ● test-1.service - /usr/bin/bash -c while true; do sleep 1; done Loaded: loaded (/run/systemd/transient/test-1.service; transient) Transient: yes Active: active (running) since Fri 2023-04-21 15:35:17 EDT; 2min 15s ago Until: Fri 2023-04-21 15:36:17 EDT; 1min 15s ago Main PID: 61473 (bash) Tasks: 2 (limit: 18896) Memory: 572.0K CPU: 138ms CGroup: /system.slice/test-1.service ├─61473 /usr/bin/bash -c "while true; do sleep 1; done" └─62087 sleep 1 Apr 21 15:35:17 six systemd[1]: Started test-1.service - /usr/bin/bash -c while true; do sleep 1; done. $ systemctl status test-1.service × test-1.service - /usr/bin/bash -c while true; do sleep 1; done Loaded: loaded (/run/systemd/transient/test-1.service; transient) Transient: yes Active: failed (Result: timeout) since Fri 2023-04-21 15:37:35 EDT; 1s ago Duration: 2min 18.274s Process: 61473 ExecStart=/usr/bin/bash -c while true; do sleep 1; done (code=killed, signal=TERM) Main PID: 61473 (code=killed, signal=TERM) CPU: 145ms Apr 21 15:35:17 six systemd[1]: Started test-1.service - /usr/bin/bash -c while true; do sleep 1; done. Apr 21 15:37:35 six systemd[1]: test-1.service: Service reached runtime time limit. Stopping. Apr 21 15:37:35 six systemd[1]: test-1.service: Failed with result 'timeout'. I am not sure if this is the intended behavior, so I will look into it further. The fact that the "Until: " line shows a time in the past makes me think this is not the intended behavior, and that timers should be restarted on suspend (which will immediately timeout if the time is in the past). -- 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/2015126 Title: systemd doesn't successfully enforce RuntimeMaxSec for gnome session Status in systemd package in Ubuntu: Triaged Status in systemd source package in Jammy: Triaged Status in systemd source package in Kinetic: Triaged Bug description: On Jammy, I have configured systemd to set RuntimeMaxSec on certain user sessions: # cat /run/systemd/transient/session-43.scope # This is a transient unit file, created programmatically via the systemd API. Do not edit. [Scope] Slice=user-1000.slice [Unit] Description=Session 43 of User xavier Wants=user-runtime-dir@1000.service Wants=user@1000.service After=systemd-logind.service After=systemd-user-sessions.service After=user-runtime-dir@1000.service After=user@1000.service RequiresMountsFor=/home/xavier [Scope] SendSIGHUP=yes TasksMax=infinity RuntimeMaxSec=2h # I have verified that this does what's expected on an ssh session, and kills the session when the runtime max has been reached. But on a GNOME login session (using X), this apparently doesn't work: the session is still running 17 hours after it should have been terminated. My guess is that systemd is ending the session by sending a signal that is being ignored by the GNOME login session? RuntimeMaxSec is not very useful if it's advisory... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.7 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 3 12:20:22 2023 InstallationDate: Installed on 2023-01-22 (70 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 2306CTO ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=c415e6a8-5cd2-4d08-913d-14c00b792374 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.release: 2.57 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:br2.57:efr1.13:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2306: dmi.product.family: ThinkPad X230 dmi.product.name:
[Touch-packages] [Bug 2017229] Re: Update evolution-data-server to 3.48.1
Hello Jeremy, or anyone else affected, Accepted evolution-data-server into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/evolution-data- server/3.48.1-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-lunar. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: evolution-data-server (Ubuntu Lunar) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-lunar ** Also affects: evolution (Ubuntu) Importance: Undecided Status: New ** No longer affects: evolution (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/2017229 Title: Update evolution-data-server to 3.48.1 Status in evolution-data-server package in Ubuntu: Fix Committed Status in evolution-data-server source package in Lunar: Fix Committed Bug description: Impact -- This is a new stable release in the stable 3.48 series. https://gitlab.gnome.org/GNOME/evolution-data- server/-/blob/3.48.1/NEWS It is required to update the evolution app to 3.48.1 (LP: #2017231) Test Case - Install the update Log out and log back in (or restart) Ensure that GNOME Calendar and Evolution still work fine. What Could Go Wrong --- As a component of GNOME core, there is a micro-release exception for evolution-data-server https://wiki.ubuntu.com/StableReleaseUpdates/GNOME evolution-data-server is included in all the Ubuntu Desktop flavors except for Kubuntu, Lubuntu, and Xubuntu Other Info -- There will be new evolution-data-server bugfix releases monthly until September. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/2017229/+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 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object
This bug report is lacking required information for an SRU. ** Changed in: ayatana-indicator-messages (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2015962 Title: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() Status in accountsservice: Fix Released Status in accountsservice package in Ubuntu: Fix Committed Status in ayatana-indicator-messages package in Ubuntu: Incomplete Status in indicator-messages package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/2015962/+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
** Changed in: openssh (Ubuntu Kinetic) Status: Triaged => In Progress ** Changed in: openssh (Ubuntu) Status: Triaged => In Progress -- 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'.
[Touch-packages] [Bug 2011458] Re: ssh fails to rebind when it is killed with -HUP
Please make sure to forward this to Debian as well. -- 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 activation
[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly
@Gunnar, that's because the only channel which has the core22 firefox atm is stable/ubuntu-23.04 (which is specific to Lunar). We transitioned Lunar to core22 but we still need to work with Mozilla on updating the other channels Your testing suggest that the issue was the one I mentioned earlier that https://github.com/ubuntu/gnome-sdk/pull/72 is missing from the core22 based gnome sdk which I'm going to propose a fix for -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font in snap apps is ugly Status in Snappy: New Status in fontconfig package in Ubuntu: New Status in language-selector package in Ubuntu: New Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 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 CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2017076/+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 2017076] Re: default Chinese font in snap apps is ugly
Oh, I miss that the lunar desktop image installs firefox snap from latest/stable/ubuntu-23.04 branch. So, if I install firefox from latest/stable channel (which uses core20), then Noto CJK is rightfully selected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font in snap apps is ugly Status in Snappy: New Status in fontconfig package in Ubuntu: New Status in language-selector package in Ubuntu: New Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 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 CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2017076/+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 2015126] Re: systemd doesn't successfully enforce RuntimeMaxSec for gnome session
The session did eventually exit: Active: failed (Result: timeout) since Fri 2023-04-21 11:24:31 PDT; 2min 48s ago However, the time while the system was suspended didn't count towards the session limit. This kind of makes sense, but is also at odds with my goal of also using pam_time to enforce specific bedtime limits. -- 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/2015126 Title: systemd doesn't successfully enforce RuntimeMaxSec for gnome session Status in systemd package in Ubuntu: Triaged Status in systemd source package in Jammy: Triaged Status in systemd source package in Kinetic: Triaged Bug description: On Jammy, I have configured systemd to set RuntimeMaxSec on certain user sessions: # cat /run/systemd/transient/session-43.scope # This is a transient unit file, created programmatically via the systemd API. Do not edit. [Scope] Slice=user-1000.slice [Unit] Description=Session 43 of User xavier Wants=user-runtime-dir@1000.service Wants=user@1000.service After=systemd-logind.service After=systemd-user-sessions.service After=user-runtime-dir@1000.service After=user@1000.service RequiresMountsFor=/home/xavier [Scope] SendSIGHUP=yes TasksMax=infinity RuntimeMaxSec=2h # I have verified that this does what's expected on an ssh session, and kills the session when the runtime max has been reached. But on a GNOME login session (using X), this apparently doesn't work: the session is still running 17 hours after it should have been terminated. My guess is that systemd is ending the session by sending a signal that is being ignored by the GNOME login session? RuntimeMaxSec is not very useful if it's advisory... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.7 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 3 12:20:22 2023 InstallationDate: Installed on 2023-01-22 (70 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 2306CTO ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=c415e6a8-5cd2-4d08-913d-14c00b792374 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.release: 2.57 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:br2.57:efr1.13:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2306: dmi.product.family: ThinkPad X230 dmi.product.name: 2306CTO dmi.product.sku: LENOVO_MT_2306 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2015126/+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 2015126] Re: systemd doesn't successfully enforce RuntimeMaxSec for gnome session
ok, reproduced the failure - if the system is suspended at the session expiry, the session apparently is never closed. Active: active (running) since Fri 2023-04-21 11:13:02 PDT; 7min ago RuntimeMaxUSec=5min -- 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/2015126 Title: systemd doesn't successfully enforce RuntimeMaxSec for gnome session Status in systemd package in Ubuntu: Triaged Status in systemd source package in Jammy: Triaged Status in systemd source package in Kinetic: Triaged Bug description: On Jammy, I have configured systemd to set RuntimeMaxSec on certain user sessions: # cat /run/systemd/transient/session-43.scope # This is a transient unit file, created programmatically via the systemd API. Do not edit. [Scope] Slice=user-1000.slice [Unit] Description=Session 43 of User xavier Wants=user-runtime-dir@1000.service Wants=user@1000.service After=systemd-logind.service After=systemd-user-sessions.service After=user-runtime-dir@1000.service After=user@1000.service RequiresMountsFor=/home/xavier [Scope] SendSIGHUP=yes TasksMax=infinity RuntimeMaxSec=2h # I have verified that this does what's expected on an ssh session, and kills the session when the runtime max has been reached. But on a GNOME login session (using X), this apparently doesn't work: the session is still running 17 hours after it should have been terminated. My guess is that systemd is ending the session by sending a signal that is being ignored by the GNOME login session? RuntimeMaxSec is not very useful if it's advisory... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.7 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 3 12:20:22 2023 InstallationDate: Installed on 2023-01-22 (70 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 2306CTO ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=c415e6a8-5cd2-4d08-913d-14c00b792374 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.release: 2.57 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:br2.57:efr1.13:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2306: dmi.product.family: ThinkPad X230 dmi.product.name: 2306CTO dmi.product.sku: LENOVO_MT_2306 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2015126/+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 2015126] Re: systemd doesn't successfully enforce RuntimeMaxSec for gnome session
Ah, now, rechecking, it appears the gdm session is mostly dead: $ systemctl status session-35.scope --no-pager -l | sed -e's/User .*/User foo/' × session-35.scope - Session 35 of User foo Loaded: loaded (/run/systemd/transient/session-35.scope; transient) Transient: yes Active: failed (Result: timeout) since Fri 2023-04-21 10:47:20 PDT; 18min ago CPU: 2.916s Apr 21 10:47:20 virgil /usr/libexec/gdm-x-session[15751]: (II) systemd-logind: releasing fd for 13:65 Apr 21 10:47:20 virgil /usr/libexec/gdm-x-session[15751]: (II) UnloadModule: "libinput" Apr 21 10:47:20 virgil /usr/libexec/gdm-x-session[15751]: (II) systemd-logind: releasing fd for 13:74 Apr 21 10:47:20 virgil /usr/libexec/gdm-x-session[15751]: (II) UnloadModule: "libinput" Apr 21 10:47:20 virgil /usr/libexec/gdm-x-session[15751]: (II) systemd-logind: releasing fd for 13:66 Apr 21 10:47:20 virgil /usr/libexec/gdm-x-session[15751]: (WW) xf86CloseConsole: KDSETMODE failed: Input/output error Apr 21 10:47:20 virgil /usr/libexec/gdm-x-session[15751]: (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error Apr 21 10:47:20 virgil /usr/libexec/gdm-x-session[15751]: (II) Server terminated successfully (0). Closing log file. Apr 21 10:47:20 virgil systemd[1]: session-35.scope: Failed with result 'timeout'. Apr 21 10:47:20 virgil systemd[1]: session-35.scope: Consumed 2.916s CPU time. $ But there are still some processes owned by the user lingering: $ ps awxfu|grep ^x | cut -f2- -d' ' 9185 0.0 0.0 18152 10956 ?Ss 09:40 0:04 /lib/systemd/systemd --user 9186 0.0 0.0 170764 4508 ?S09:40 0:00 \_ (sd-pam) 9192 0.0 0.0 48216 6756 ?Shttps://bugs.launchpad.net/bugs/2015126 Title: systemd doesn't successfully enforce RuntimeMaxSec for gnome session Status in systemd package in Ubuntu: Triaged Status in systemd source package in Jammy: Triaged Status in systemd source package in Kinetic: Triaged Bug description: On Jammy, I have configured systemd to set RuntimeMaxSec on certain user sessions: # cat /run/systemd/transient/session-43.scope # This is a transient unit file, created programmatically via the systemd API. Do not edit. [Scope] Slice=user-1000.slice [Unit] Description=Session 43 of User xavier Wants=user-runtime-dir@1000.service Wants=user@1000.service After=systemd-logind.service After=systemd-user-sessions.service After=user-runtime-dir@1000.service After=user@1000.service RequiresMountsFor=/home/xavier [Scope] SendSIGHUP=yes TasksMax=infinity RuntimeMaxSec=2h # I have verified that this does what's expected on an ssh session, and kills the session when the runtime max has been reached. But on a GNOME login session (using X), this apparently doesn't work: the session is still running 17 hours after it should have been terminated. My guess is that systemd is ending the session by sending a signal that is being ignored by the GNOME login session? RuntimeMaxSec is not very useful if it's advisory... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.7 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 3 12:20:22 2023 InstallationDate: Installed on 2023-01-22 (70 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 2306CTO ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=c415e6a8-5cd2-4d08-913d-14c00b792374 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.release: 2.57 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:br2.57:efr1.13:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2306: dmi.product.family: ThinkPad X230 dmi.product.name: 2306CTO dmi.product.sku: LENOVO_MT_2306 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2015126/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages
Re: [Touch-packages] [Bug 2015126] Re: systemd doesn't successfully enforce RuntimeMaxSec for gnome session
On Fri, Apr 21, 2023 at 03:57:58PM -, Nick Rosbrook wrote: > Also, to check the active runtime, can you use `systemctl show > --property=ActiveEnterTimestamp session-X.scope`? Or just show the full > output of systemctl status session-X.scope. It should inform us if it is > counting up to RuntimeMaxSec. A test session with a 5-minute limit: # systemctl status session-35.scope --no-pager -l | sed -e's/User .*/User foo/' ● session-35.scope - Session 35 of User foo Loaded: loaded (/run/systemd/transient/session-35.scope; transient) Transient: yes Active: active (running) since Fri 2023-04-21 10:42:20 PDT; 2min 15s ago Tasks: 18 Memory: 56.8M CPU: 2.325s CGroup: /user.slice/user-1000.slice/session-35.scope ├─15573 "gdm-session-worker [pam/gdm-password]" ├─15745 /usr/bin/gnome-keyring-daemon --daemonize --login ├─15749 /usr/libexec/gdm-x-session --run-script "env GNOME_SHELL_SESSION_MODE=ubuntu /usr/bin/gnome-session --session=ubuntu" ├─15751 /usr/lib/xorg/Xorg vt3 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -novtswitch -verbose 3 └─15762 /usr/libexec/gnome-session-binary --session=ubuntu Apr 21 10:42:21 virgil /usr/libexec/gdm-x-session[15799]: dbus-update-activation-environment: setting QT_ACCESSIBILITY=1 Apr 21 10:42:21 virgil gnome-keyring-daemon[15745]: The Secret Service was already initialized Apr 21 10:42:21 virgil gnome-keyring-daemon[15745]: The PKCS#11 component was already initialized Apr 21 10:42:21 virgil gnome-keyring-daemon[15745]: The SSH agent was already initialized Apr 21 10:42:21 virgil /usr/libexec/gdm-x-session[15751]: (II) modeset(0): EDID vendor "AUO", prod id 4204 Apr 21 10:42:21 virgil /usr/libexec/gdm-x-session[15751]: (II) modeset(0): Printing DDC gathered Modelines: Apr 21 10:42:21 virgil /usr/libexec/gdm-x-session[15751]: (II) modeset(0): Modeline "1366x768"x0.0 69.30 1366 1414 1446 1454 768 771 777 793 -hsync -vsync (47.7 kHz eP) Apr 21 10:42:25 virgil /usr/libexec/gdm-x-session[15751]: (II) modeset(0): EDID vendor "AUO", prod id 4204 Apr 21 10:42:25 virgil /usr/libexec/gdm-x-session[15751]: (II) modeset(0): Printing DDC gathered Modelines: Apr 21 10:42:25 virgil /usr/libexec/gdm-x-session[15751]: (II) modeset(0): Modeline "1366x768"x0.0 69.30 1366 1414 1446 1454 768 771 777 793 -hsync -vsync (47.7 kHz eP) # systemctl show --property=ActiveEnterTimestamp session-35.scope ActiveEnterTimestamp=Fri 2023-04-21 10:42:20 PDT # systemctl show --property=RuntimeMaxUSec session-35.scope RuntimeMaxUSec=5min # # date Fri Apr 21 10:52:23 PDT 2023 # Still running past the limit. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- 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/2015126 Title: systemd doesn't successfully enforce RuntimeMaxSec for gnome session Status in systemd package in Ubuntu: Triaged Status in systemd source package in Jammy: Triaged Status in systemd source package in Kinetic: Triaged Bug description: On Jammy, I have configured systemd to set RuntimeMaxSec on certain user sessions: # cat /run/systemd/transient/session-43.scope # This is a transient unit file, created programmatically via the systemd API. Do not edit. [Scope] Slice=user-1000.slice [Unit] Description=Session 43 of User xavier Wants=user-runtime-dir@1000.service Wants=user@1000.service After=systemd-logind.service After=systemd-user-sessions.service After=user-runtime-dir@1000.service After=user@1000.service RequiresMountsFor=/home/xavier [Scope] SendSIGHUP=yes TasksMax=infinity RuntimeMaxSec=2h # I have verified that this does what's expected on an ssh session, and kills the session when the runtime max has been reached. But on a GNOME login session (using X), this apparently doesn't work: the session is still running 17 hours after it should have been terminated. My guess is that systemd is ending the session by sending a signal that is being ignored by the GNOME login session? RuntimeMaxSec is not very useful if it's advisory... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.7 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 3 12:20:22 2023 InstallationDate: Installed on 2023-01-22 (70 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy
[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly
This is confusing. If you install Ubuntu 23.04, you get FF from latest/stable/23.04 together with core22. Now I did a test where I removed FF, set the zh_CN.UTF-8 locale, and installed FF again. Whichever channel I pick (tried latest/stable, latest/beta and latest/edge) it pulls core20, and then it defaults to Noto CJK fonts. So I wasn't able to reproduce the issue with "AR PL UMing" as default this way. I get the same result as Shengjing Zhu got when installing from esr. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font in snap apps is ugly Status in Snappy: New Status in fontconfig package in Ubuntu: New Status in language-selector package in Ubuntu: New Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 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 CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2017076/+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 2017076] Re: default Chinese font in snap apps is ugly
@seb128, I think you mean esr/stable channel? esr channel which uses core20 is using Noto font. See the attachment. ** Attachment added: "screenshot" https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/+attachment/5666489/+files/2023-04-22_00-34.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font in snap apps is ugly Status in Snappy: New Status in fontconfig package in Ubuntu: New Status in language-selector package in Ubuntu: New Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 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 CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2017076/+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 2015126] Re: systemd doesn't successfully enforce RuntimeMaxSec for gnome session
Also, to check the active runtime, can you use `systemctl show --property=ActiveEnterTimestamp session-X.scope`? Or just show the full output of systemctl status session-X.scope. It should inform us if it is counting up to RuntimeMaxSec. -- 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/2015126 Title: systemd doesn't successfully enforce RuntimeMaxSec for gnome session Status in systemd package in Ubuntu: Triaged Status in systemd source package in Jammy: Triaged Status in systemd source package in Kinetic: Triaged Bug description: On Jammy, I have configured systemd to set RuntimeMaxSec on certain user sessions: # cat /run/systemd/transient/session-43.scope # This is a transient unit file, created programmatically via the systemd API. Do not edit. [Scope] Slice=user-1000.slice [Unit] Description=Session 43 of User xavier Wants=user-runtime-dir@1000.service Wants=user@1000.service After=systemd-logind.service After=systemd-user-sessions.service After=user-runtime-dir@1000.service After=user@1000.service RequiresMountsFor=/home/xavier [Scope] SendSIGHUP=yes TasksMax=infinity RuntimeMaxSec=2h # I have verified that this does what's expected on an ssh session, and kills the session when the runtime max has been reached. But on a GNOME login session (using X), this apparently doesn't work: the session is still running 17 hours after it should have been terminated. My guess is that systemd is ending the session by sending a signal that is being ignored by the GNOME login session? RuntimeMaxSec is not very useful if it's advisory... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.7 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 3 12:20:22 2023 InstallationDate: Installed on 2023-01-22 (70 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 2306CTO ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=c415e6a8-5cd2-4d08-913d-14c00b792374 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.release: 2.57 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:br2.57:efr1.13:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2306: dmi.product.family: ThinkPad X230 dmi.product.name: 2306CTO dmi.product.sku: LENOVO_MT_2306 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2015126/+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 2017224] Re: Cannot enable bluetooth in gnome-shell
I installed the latest linux-firmware from the repo but it didn't help. # dmesg | grep -i bluetooth [ 18.861759] Bluetooth: Core ver 2.22 [ 18.863617] NET: Registered PF_BLUETOOTH protocol family [ 18.863621] Bluetooth: HCI device and connection manager initialized [ 18.863628] Bluetooth: HCI socket layer initialized [ 18.863631] Bluetooth: L2CAP socket layer initialized [ 18.863638] Bluetooth: SCO socket layer initialized [ 19.146683] Bluetooth: hci0: Bootloader revision 0.4 build 0 week 30 2018 [ 19.147702] Bluetooth: hci0: Device revision is 2 [ 19.147707] Bluetooth: hci0: Secure boot is enabled [ 19.147709] Bluetooth: hci0: OTP lock is enabled [ 19.147712] Bluetooth: hci0: API lock is enabled [ 19.147714] Bluetooth: hci0: Debug lock is disabled [ 19.147716] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 19.150729] Bluetooth: hci0: Found device firmware: intel/ibt-19-0-4.sfi [ 19.150841] Bluetooth: hci0: Boot Address: 0x24800 [ 19.150843] Bluetooth: hci0: Firmware Version: 15-45.22 [ 19.998952] Bluetooth: hci0: urb 8cd2a5b0 failed to resubmit (2) [ 20.015315] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 20.015321] Bluetooth: BNEP filters: protocol multicast [ 20.015329] Bluetooth: BNEP socket layer initialized [ 22.005627] Bluetooth: hci0: command 0xfc09 tx timeout [ 30.037760] Bluetooth: hci0: Failed to send firmware data (-110) [ 30.037855] Bluetooth: hci0: Intel reset sent to retry FW download [ 32.213626] Bluetooth: hci0: Failed to read MSFT supported features (-110) -- 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/2017224 Title: Cannot enable bluetooth in gnome-shell Status in bluez package in Ubuntu: New Status in gnome-settings-daemon package in Ubuntu: New Bug description: After upgrade to 23.04, Bluetooth service is started but can't enable it in gnome-shell. Apr 21 11:34:15 ZB systemd[1]: Starting bluetooth.service - Bluetooth service... Apr 21 11:34:15 ZB systemd[1403]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555) Apr 21 11:34:15 ZB bluetoothd[1403]: Bluetooth daemon 5.66 Apr 21 11:34:15 ZB bluetoothd[1403]: Starting SDP server Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/vcp.c:vcp_init() D-Bus experimental not enabled Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to init vcp plugin Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to init mcp plugin Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to init bap plugin Apr 21 11:34:15 ZB systemd[1]: Started bluetooth.service - Bluetooth service. Apr 21 11:34:15 ZB bluetoothd[1403]: Bluetooth management interface 1.22 initialized ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: bluez 5.66-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 21 11:44:40 2023 InstallationDate: Installed on 2023-01-04 (106 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) InterestingModules: bnep btusb bluetooth MachineType: ASUSTeK COMPUTER INC. ZenBook UX435EG_UX435EG ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash SourcePackage: bluez UpgradeStatus: Upgraded to lunar on 2023-04-21 (0 days ago) dmi.bios.date: 04/22/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX435EG.315 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX435EG dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX435EG.315:bd04/22/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX435EG_UX435EG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX435EG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX435EG_UX435EG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: mtime.conffile..etc.bluetooth.input.conf: 2023-02-28T07:11:41.547346 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2017224/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to
[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly
Do you get the same issue on core20 snaps (like firefox from the stable channel)? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font in snap apps is ugly Status in Snappy: New Status in fontconfig package in Ubuntu: New Status in language-selector package in Ubuntu: New Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 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 CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2017076/+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 2017184] Re: Please change default HandlePowerKey value
By default, GNOME has an inhibitor in place for handle-power-key for this exact reason: $ systemd-inhibit --list | grep handle-power-key nr 1000 nr 7827 gsd-media-keys handle-power-key:handle-suspend-key:handle-hibernate-key GNOME handling keypresses It looks like you are using GNOME flashback (not something I am familiar with) - maybe it's not configuring this inhibitor? Can you share the output of systemd-inhibit --list? ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- 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/2017184 Title: Please change default HandlePowerKey value Status in systemd package in Ubuntu: Incomplete Bug description: By default, /etc/systemd/logind.conf sets HandlePowerKey to poweroff. This is a terrible default, because this poweroff action does not ask for any confirmation whatsoever, encouraging data loss. The power key does get pressed inadvertently from time to time: - It's usually also the resume-from-suspend key, so if you thought you had suspended the computer but in fact it only locked after inactivity, you could press the power key to resume, only to find that you just nuked your session. - On many laptops, the power button is close to backspace. A single slip of your pinky nukes your session. Each of these mishaps can result in loss of unsaved data, and/or data corruption if some background task is running that doesn't expect to get killed in the middle. This is an especially terrible user experience for novices who have little prior exposure to system setting files, who will likely have a hard time fixing it. This is not a sensible default. Please at least show confirmation for this poweroff action by default, or if that's difficult to do, make the default more benign, like ignore or lock. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.7 ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME-Flashback:GNOME Date: Fri Apr 21 10:01:27 2023 InstallationDate: Installed on 2023-02-02 (77 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Supermicro Super Server ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic root=UUID=7851a3b8-a4dc-460a-abb0-6f754ae2d343 ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/27/2022 dmi.bios.release: 5.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.5 dmi.board.asset.tag: Default string dmi.board.name: X11SRA dmi.board.vendor: Supermicro dmi.board.version: 1.02 dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd01/27/2022:br5.15:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SRA:rvr1.02:cvnSupermicro:ct17:cvr0123456789:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Super Server dmi.product.sku: Default string dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro modified.conffile..etc.systemd.logind.conf: [modified] mtime.conffile..etc.systemd.logind.conf: 2023-04-21T09:55:04.295695 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2017184/+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 1951586] Re: Need option to specify wifi regulatory domain
>Might want to reconsider that position given the latest release of 22.04 >posted on 2023-02-17 >http://cdimage.ubuntu.com/ubuntu/releases/22.04/release/ubuntu-22.04.2-preinstalled-server- >arm64+raspi.manifest contains netplan.io 0.105-0ubuntu2~22.04.1 which is >offered by Imager as an >install option. Problem is you also still list Ubuntu 20.04 in your Imager repository file at: https://changelogs.ubuntu.com/raspi/os_list_imagingutility_ubuntu.json Suggest you either toss any release that does not support 'regulatory- domain' from the repository first, or backport your fix to that as well. -- 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/1951586 Title: Need option to specify wifi regulatory domain Status in cloud-init: Invalid Status in netplan: Fix Released Status in NetworkManager: New Status in netplan.io package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Incomplete Status in netplan.io source package in Jammy: Triaged Status in network-manager source package in Jammy: Incomplete Status in netplan.io source package in Kinetic: Fix Released Status in network-manager source package in Kinetic: Incomplete Bug description: It would be nice if netplan offered an option to specify the wifi regulatory domain (country code). For devices such as the Raspberry Pi you are currently advertising that users can simply setup Ubuntu Server headless by putting the wifi configuration details in cloudinit/netplan's "network-config" on the FAT partition of the SD card: https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet But an option to set the wifi country code there does not seem to exist, so may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1951586/+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 91418] Re: Time not updated when daylight savings switch made
The bug is not about tzdata itself (that package contains only the information about the timezones). Instead it is about the part of the system that takes care of changing the local time when the daylight saving switch is done. A solution/workaround is to change the system clock to be in UTC. Then the hardware clock does not need to be changed. Is someone still affected by this bug? ** Package changed: tzdata (Ubuntu) => ubuntu ** Changed in: ubuntu Status: Confirmed => Incomplete -- 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/91418 Title: Time not updated when daylight savings switch made Status in Ubuntu: Incomplete Bug description: Binary package hint: tzdata March 11, 2007, edgy did not update my clock. I had installed the edgy updates and i do find Adept Manager listing the tzdata_2007b_0ubuntu0.6.10_all.deb as been installed on 03/07/2007. I am using Dell Inspiron 5160, dual booting with XP. $ sudo dpkg -s tzdata Package: tzdata Status: install ok installed Priority: required Section: libs Installed-Size: 5728 Maintainer: Ubuntu Core Developers Architecture: all Version: 2007b-0ubuntu0.6.10 Replaces: libc0.1, libc0.3, libc6, libc6.1, locales Description: Time Zone and Daylight Saving Time Data This package contains data that represent the history of local time for many representative locations around the globe. It is updated periodically to reflect changes made by political bodies to time zone boundaries, UTC offsets, and daylight-saving rules Original-Maintainer: GNU Libc Maintainers $ sudo zdump -v /etc/localtime | grep 2007 /etc/localtime Sun Mar 11 06:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 EST isdst=0 gmtoff=-18000 /etc/localtime Sun Mar 11 07:00:00 2007 UTC = Sun Mar 11 03:00:00 2007 EDT isdst=1 gmtoff=-14400 /etc/localtime Sun Nov 4 05:59:59 2007 UTC = Sun Nov 4 01:59:59 2007 EDT isdst=1 gmtoff=-14400 /etc/localtime Sun Nov 4 06:00:00 2007 UTC = Sun Nov 4 01:00:00 2007 EST isdst=0 gmtoff=-18000 $ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/91418/+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 2017184] Re: Please change default HandlePowerKey value
** Summary changed: - Terrible Default for HandlePowerKey + Please change default HandlePowerKey value -- 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/2017184 Title: Please change default HandlePowerKey value Status in systemd package in Ubuntu: New Bug description: By default, /etc/systemd/logind.conf sets HandlePowerKey to poweroff. This is a terrible default, because this poweroff action does not ask for any confirmation whatsoever, encouraging data loss. The power key does get pressed inadvertently from time to time: - It's usually also the resume-from-suspend key, so if you thought you had suspended the computer but in fact it only locked after inactivity, you could press the power key to resume, only to find that you just nuked your session. - On many laptops, the power button is close to backspace. A single slip of your pinky nukes your session. Each of these mishaps can result in loss of unsaved data, and/or data corruption if some background task is running that doesn't expect to get killed in the middle. This is an especially terrible user experience for novices who have little prior exposure to system setting files, who will likely have a hard time fixing it. This is not a sensible default. Please at least show confirmation for this poweroff action by default, or if that's difficult to do, make the default more benign, like ignore or lock. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.7 ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME-Flashback:GNOME Date: Fri Apr 21 10:01:27 2023 InstallationDate: Installed on 2023-02-02 (77 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Supermicro Super Server ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic root=UUID=7851a3b8-a4dc-460a-abb0-6f754ae2d343 ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/27/2022 dmi.bios.release: 5.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.5 dmi.board.asset.tag: Default string dmi.board.name: X11SRA dmi.board.vendor: Supermicro dmi.board.version: 1.02 dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd01/27/2022:br5.15:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SRA:rvr1.02:cvnSupermicro:ct17:cvr0123456789:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Super Server dmi.product.sku: Default string dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro modified.conffile..etc.systemd.logind.conf: [modified] mtime.conffile..etc.systemd.logind.conf: 2023-04-21T09:55:04.295695 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2017184/+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 835297] Re: sometimes /etc/timezone is not being created
Comment #22 says that tzdata's maintainer scripts never remove /etc/timezone and therefore it is not the fault of the tzdata package. Due to that and the age of this bug, I am marking it invalid for tzdata. Please report back if you experience it with a recent Ubuntu version. ** Changed in: tzdata (Ubuntu) Status: Confirmed => Invalid -- 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/835297 Title: sometimes /etc/timezone is not being created Status in Indicator Date and Time: Invalid Status in indicator-datetime package in Ubuntu: Invalid Status in tzdata package in Ubuntu: Invalid Bug description: I'm not convinced this isn't already reported or is genuinely in unity but I can't think of a search query that will track it down. Since upgrading to Oneiric I'm no longer seeing the clock, simply the word "Time". I really can't explain it very well so screenshot attached. I didn't use Unity pre-Oneiric although I did boot into it on at east one occassion and think I would have noticed the missing clock. I've been through a full set of video drivers for other reasons (nv, nouveau, vesa, nvidia-current) without any effect. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: unity 4.8.2-0ubuntu4 ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3 Uname: Linux 3.0.0-9-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 280.13 Wed Jul 27 16:53:56 PDT 2011 GCC version: gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-7ubuntu1) Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell] CompositorRunning: compiz CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Sat Aug 27 09:04:30 2011 DistUpgraded: Log time: 2011-08-21 09:12:55.859993 DistroCodename: oneiric DistroVariant: ubuntu DkmsStatus: nvidia-current, 280.13, 3.0.0-9-generic, x86_64: installed vboxhost, 4.0.12, 3.0.0-9-generic, x86_64: installed GraphicsCard: nVidia Corporation G98 [GeForce 8400 GS] [10de:06e4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: nVidia Corporation Device [10de:050f] MachineType: System manufacturer M2NS-NVM ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: root=UUID=d70f0f0c-60c0-45e9-acf0-250be6dcd21e ro quiet splash nomodeset SourcePackage: unity UpgradeStatus: Upgraded to oneiric on 2011-08-21 (5 days ago) dmi.bios.date: 09/28/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS M2NS-NVM ACPI BIOS Revision 0401 dmi.board.name: M2NS-NVM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2NS-NVMACPIBIOSRevision0401:bd09/28/2006:svnSystemmanufacturer:pnM2NS-NVM:pvr1.XX:rvnASUSTeKComputerINC.:rnM2NS-NVM:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: M2NS-NVM dmi.product.version: 1.XX dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.5.92+bzr2791-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu16 version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/835297/+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 1980937] Re: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise
Ubuntu 23.04 kernel 6.2.0-20-generic still no luck. Speakers not working with following in alsa-base.conf speakers works, but microphone doesn't options snd-hda-intel dmic_detect=0 options snd-hda-intel model=laptop-amic enable=yes -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1980937 Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise Status in alsa-driver package in Ubuntu: Confirmed Bug description: New laptop with fresh installation of Xubuntu 22.04. Intel Tiger Lake- LP audio controller. When playing any audio, the internal speaker plays no sound except periodic loud crackling noise. The 3.5mm jack does not work either, producing the same craclking noise alongside some eletrical noise. HDMI audio skimmishly tested, but also gave no sound. Curiously, USB headphone (along with microphone) works perfectly, also the internal microphone. As attempts to fix the problem, I have tried the following separately, with no avail: - Installing some Ubuntu OEM version of the 5.17 kernel - Updating to the v2.2 firmware from Sound Open Firmware Project (thesofproject on github), reverted afterwards I found exactly the same problem reported in the Fedora community: https://forums.fedoraforum.org/showthread.php?328627-HP-Elitebook-840-G8-Tiger-Lake-audio-only-produces-popping-sound=1860086 As the pre-installed Windows has been destroyed, no further test on Windows has been done. Since USB headphone and internal microphone work, I think that there is no problem on the Intel Tiger Lake-LP controller and its driver. The bug probably lies elsewhere, like in the handling of ALC245 on this new laptop model. Thank you very much for your time and effort in advance. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fwjmath2810 F pulseaudio fwjmath 72467 F alsamixer CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Thu Jul 7 10:59:22 2022 InstallationDate: Installed on 2022-06-29 (7 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fwjmath2810 F pulseaudio fwjmath 72467 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2022 dmi.bios.release: 9.1 dmi.bios.vendor: HP dmi.bios.version: T37 Ver. 01.09.01 dmi.board.name: 8AB8 dmi.board.vendor: HP dmi.board.version: KBC Version 58.03.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 88.3 dmi.modalias: dmi:bvnHP:bvrT37Ver.01.09.01:bd05/05/2022:br9.1:efr88.3:svnHP:pnHPEliteBook840G8NotebookPC:pvr:rvnHP:rn8AB8:rvrKBCVersion58.03.00:cvnHP:ct10:cvr:sku6A3P3AV: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 G8 Notebook PC dmi.product.sku: 6A3P3AV dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-07-02T17:07:35.783239 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1980937/+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 1951586] Re: Need option to specify wifi regulatory domain
>Imager does not fill in the 'regulatory-domain' field in network-config because the last time we tried that the existing Ubuntu editions in the Imager repository did not support the field yet, and reacted badly to it. As in error'ing out instead of just ignoring. Might want to reconsider that position given the latest release of 22.04 posted on 2023-02-17 http://cdimage.ubuntu.com/ubuntu/releases/22.04/release/ubuntu-22.04.2-preinstalled-server-arm64+raspi.manifest contains netplan.io 0.105-0ubuntu2~22.04.1 which is offered by Imager as an install option. -- 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/1951586 Title: Need option to specify wifi regulatory domain Status in cloud-init: Invalid Status in netplan: Fix Released Status in NetworkManager: New Status in netplan.io package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Incomplete Status in netplan.io source package in Jammy: Triaged Status in network-manager source package in Jammy: Incomplete Status in netplan.io source package in Kinetic: Fix Released Status in network-manager source package in Kinetic: Incomplete Bug description: It would be nice if netplan offered an option to specify the wifi regulatory domain (country code). For devices such as the Raspberry Pi you are currently advertising that users can simply setup Ubuntu Server headless by putting the wifi configuration details in cloudinit/netplan's "network-config" on the FAT partition of the SD card: https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet But an option to set the wifi country code there does not seem to exist, so may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1951586/+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 1325949] Re: Add note to Debconf template about unintuitive inverted Etc/GMT offsets
I reported this unintuitive behavior to upstream: https://mm.icann.org/pipermail/tz/2023-April/032897.html -- 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/1325949 Title: Add note to Debconf template about unintuitive inverted Etc/GMT offsets Status in tzdata package in Ubuntu: Confirmed Status in tzdata package in Debian: New Bug description: Looks like GMT[+-} timezones have signs swapped. My local timezone is Europe/Tallinn When timezone is set to "Europe/Tallinn", everything is ok: # dpkg-reconfigure tzdata -> Europe/Tallinn # date Tue Jun 3 14:34:21 EEST 2014 # date +%z +0300 # date -u Tue Jun 3 11:34:59 UTC 2014 I need to set timezone to GMT+2, to avoid dailight savings time. When I set timezone to "GMT+2", things fall apart. Timezone is shown GMT+2/GMT-2. Clock is set to GMT-2. # dpkg-reconfigure tzdata -> Etc/GMT+2 # date Tue Jun 3 09:36:21 GMT+2 2014 # date +%z -0200 # date -u Tue Jun 3 11:37:43 UTC 2014 When I set timezone to "GMT-2", then it's turned around. Timezone is shown GMT-2/GMT+2. Clock is set to GMT+2. #dpkg-reconfigure tzdata -> Etc/GMT-2 # date Tue Jun 3 13:39:35 GMT-2 2014 # date +%z +0200 # date -u Tue Jun 3 11:39:56 UTC 2014 # lsb_release -rd Description:Ubuntu 12.04.4 LTS Release:12.04 # apt-cache policy tzdata tzdata: Installed: 2014c-0ubuntu0.12.04 Candidate: 2014c-0ubuntu0.12.04 Version table: *** 2014c-0ubuntu0.12.04 0 500 http://ee.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 2012e-0ubuntu0.12.04.1 0 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 2012b-1 0 500 http://ee.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages # apt-get update # apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1325949/+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 1554806] Re: Change of behavior: "dpkg-reconfigure -f noninteractive" unconditionally overwrites /etc/timezone now
I documented how to change the time zone non-interactively in https://discourse.ubuntu.com/t/how-to-change-the-time-zone-in-ubuntu- using-the-command-line/35307 because the log-in to https://help.ubuntu.com/community/UbuntuTime timed out. As mentioned in the linked Debian bug reports and here, this change was intentional and /etc/timezone will go away soon. Therefore marking this bug as invalid. ** Changed in: tzdata (Ubuntu) Status: Confirmed => Invalid ** Changed in: tzdata (Ubuntu) Importance: Undecided => Medium -- 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/1554806 Title: Change of behavior: "dpkg-reconfigure -f noninteractive" unconditionally overwrites /etc/timezone now Status in tzdata package in Ubuntu: Invalid Bug description: In previous versions it was possible to set the system's timezone by editing /etc/timezone before running "dpkg-reconfigure -f noninteractive tzdata". This behavior changed, /etc/timezone gets overwritten unconditionally during "dpkg-reconfigure -f noninteractive tzdata": --- root@xenial:/# echo "Europe/Berlin" > /etc/timezone root@xenial:/# cat /etc/timezone Europe/Berlin root@xenial:/# dpkg-reconfigure -f noninteractive tzdata Current default time zone: 'Etc/UTC' Local time is now: Tue Mar 8 23:09:39 UTC 2016. Universal Time is now: Tue Mar 8 23:09:39 UTC 2016. root@xenial:/# cat /etc/timezone Etc/UTC --- As a workaround to programmatically set the timezone one now needs to point "/etc/localtime" to the new timezone: --- root@xenial:/# ln -fs /usr/share/zoneinfo/Europe/Berlin /etc/localtime root@xenial:/# ll /etc/localtime lrwxrwxrwx 1 root root 33 Mar 9 00:48 /etc/localtime -> /usr/share/zoneinfo/Europe/Berlin root@xenial:/# cat /etc/timezone Etc/UTC root@xenial:/# dpkg-reconfigure -f noninteractive tzdata Current default time zone: 'Europe/Berlin' Local time is now: Wed Mar 9 00:49:05 CET 2016. Universal Time is now: Tue Mar 8 23:49:05 UTC 2016. root@xenial:/# cat /etc/timezone Europe/Berlin --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1554806/+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 2015126] Re: systemd doesn't successfully enforce RuntimeMaxSec for gnome session
Okay. I'm curious what the output is when RuntimeMaxSec does not seem to be enforced. Does this fail consistently again or is it irregular? -- 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/2015126 Title: systemd doesn't successfully enforce RuntimeMaxSec for gnome session Status in systemd package in Ubuntu: Triaged Status in systemd source package in Jammy: Triaged Status in systemd source package in Kinetic: Triaged Bug description: On Jammy, I have configured systemd to set RuntimeMaxSec on certain user sessions: # cat /run/systemd/transient/session-43.scope # This is a transient unit file, created programmatically via the systemd API. Do not edit. [Scope] Slice=user-1000.slice [Unit] Description=Session 43 of User xavier Wants=user-runtime-dir@1000.service Wants=user@1000.service After=systemd-logind.service After=systemd-user-sessions.service After=user-runtime-dir@1000.service After=user@1000.service RequiresMountsFor=/home/xavier [Scope] SendSIGHUP=yes TasksMax=infinity RuntimeMaxSec=2h # I have verified that this does what's expected on an ssh session, and kills the session when the runtime max has been reached. But on a GNOME login session (using X), this apparently doesn't work: the session is still running 17 hours after it should have been terminated. My guess is that systemd is ending the session by sending a signal that is being ignored by the GNOME login session? RuntimeMaxSec is not very useful if it's advisory... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.7 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 3 12:20:22 2023 InstallationDate: Installed on 2023-01-22 (70 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 2306CTO ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=c415e6a8-5cd2-4d08-913d-14c00b792374 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.release: 2.57 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:br2.57:efr1.13:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2306: dmi.product.family: ThinkPad X230 dmi.product.name: 2306CTO dmi.product.sku: LENOVO_MT_2306 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2015126/+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 2017076] Re: default Chinese font in snap apps is ugly
I had an IRC conversion with Sebastien Bacher and learned that things no longer work as I thought they did. Unlike what I thought, the snaps do no longer honor the font configuration of the host system, but live in their own world in this respect. https://github.com/ubuntu/gnome-sdk/issues/49#issuecomment-1216321729 So, what's determining the default font for a snap application is this list: https://github.com/ubuntu/gnome-sdk/pull/72/files There is an apparent need to reconsider that list, but that's a separate thing. Let's first try to understand how the specific issue reported in this bug could happen. The list includes the fonts-noto-cjk package, which also installs 70-fonts-noto-cjk.conf. The latter includes: zh-cn sans-serif Noto Sans CJK SC Well, fonts-arphic-uming is also included currently, and it installs 65-fonts-arphic-uming.conf which includes: sans-serif AR PL UMing CN AR PL UMing HK AR PL UMing TW Note that this one is not language guarded, so it's effective irrespective of locale. But still, with the zh_CN.UTF-8 locale 70-fonts-noto-cjk.conf should safely result in Noto Sans CJK SC being preferred over AR PL UMing CN. To confirm that I installed the Chinese (Simplified) language in 23.04 and purged language-selector-common (which made gnome-control-center being uninstalled...). And yes: $ LC_CTYPE=zh_CN.UTF-8 fc-match NotoSansCJK-Regular.ttc: "Noto Sans CJK SC" "Regular" More playing with fc-match: $ LC_CTYPE=zh_CN.UTF-8 fc-match -a | grep -iE 'cjk sc|uming cn' | head -3 NotoSansCJK-Regular.ttc: "Noto Sans CJK SC" "Regular" NotoSansCJK-Bold.ttc: "Noto Sans CJK SC" "Bold" uming.ttc: "AR PL UMing CN" "Light" $ LC_CTYPE=en_US.UTF-8 fc-match -a | grep -iE 'cjk sc|uming cn' | head -3 uming.ttc: "AR PL UMing CN" "Light" NotoSansCJK-Regular.ttc: "Noto Sans CJK SC" "Regular" NotoSansCJK-Regular.ttc: "Noto Sans Mono CJK SC" "Regular" So I now have a (vague) theory about what happens when you install Ubuntu using the zh_CN.UTF-8 locale: While it honors the locale when determining which packages get installed (apparently, since fonts-arphic-uming is there), the locale is not properly taken into account at the stage when the default Chinese (Simplified) font of the snaps is determined. ** Bug watch added: github.com/ubuntu/gnome-sdk/issues #49 https://github.com/ubuntu/gnome-sdk/issues/49 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font in snap apps is ugly Status in Snappy: New Status in fontconfig package in Ubuntu: New Status in language-selector package in Ubuntu: New Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 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 CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2017076/+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 1586848] Re: On Ubuntu touch it is not possible to change timezone while filesystem is mounted readonly (default)
Thank you for taking the time to report this bug and helping to make Ubuntu better. Having the file system read-only leads to tzdata not be able to change the timezone. This is not a bug in tzdata IMO, but an issue with how Ubuntu touch is setup (or how Ubuntu touch integrates tzdata). Therefore I remove tzdata from the affected package. ** Package changed: tzdata (Ubuntu) => ubuntu -- 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/1586848 Title: On Ubuntu touch it is not possible to change timezone while filesystem is mounted readonly (default) Status in Ubuntu: Confirmed Bug description: On Ubuntu touch, by default, the filesystem is mounted as read only by default. However, in this state the timezone cannot be changed neither through the GUI, nor through dpkg-reconfigure tzdata Through GUI, I tried the following: 1. Swipe from top, through Time & Date 2. Click "Time & Date settings" 3. Under timezone, click the currently set timezone (in my case Europe/Luxembourg UTC+2) 4. Under current location, enter Helsinki 5. Click on "Helsinki, Uusimaa, Finland" 6. "Helsinki, Uusimaa, Finland" gets blue writing on grey background, but nothing else happens. Clicking "back" at top of the screen allows to exit this dialog, but timezone is not changed. In contrast, if filesystem is mounted read-write (not the default state), the button disappears on click, I get back to the previous page, and timezone is indeed changed. When trying to change the timezone through the command line (dpkg- reconfigure tzdata), I get the following error message: cp: cannot create regular file '/etc/localtime.dpkg-new': Read-only file system Current default time zone: 'Europe/Helsinki' Local time is now: Mon May 30 00:13:08 CEST 2016. Universal Time is now: Sun May 29 22:13:08 UTC 2016. debconf: DbDriver "config": could not write /var/cache/debconf/config.dat-new: Read-only file system root@alains-pocket-penguin:~# lsb_release -rd Description:Ubuntu 15.04 Release:15.04 root@alains-pocket-penguin:~# apt-cache policy tzdata tzdata: Installed: 2015g-0ubuntu0.15.04 Candidate: 2015g-0ubuntu0.15.04 Version table: *** 2015g-0ubuntu0.15.04 0 500 http://ports.ubuntu.com/ubuntu-ports/ vivid-updates/main armhf Packages 500 http://ports.ubuntu.com/ubuntu-ports/ vivid-security/main armhf Packages 100 /var/lib/dpkg/status 2015c-1 0 500 http://ports.ubuntu.com/ubuntu-ports/ vivid/main armhf Packages What I expected to happen: - Timezone should change What happened instead: - In GUI, button for new timezone is highlighted (blue writing on grey background), but dialog does not go away. Leaving it via "back" at top left of screen leaves timezone unchanged - In command line, I get the following error: cp: cannot create regular file '/etc/localtime.dpkg-new': Read-only file system Current default time zone: 'Europe/Helsinki' Local time is now: Mon May 30 00:13:08 CEST 2016. Universal Time is now: Sun May 29 22:13:08 UTC 2016. debconf: DbDriver "config": could not write /var/cache/debconf/config.dat-new: Read-only file system Suggested fix: /var/cache/debconf should be on a filesystem which is always writeable /etc/localtime should be a symlink to writable/localtime (just like is the case for /etc/timezone) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1586848/+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 1499472] Re: Wrong local time in tzdata
Thank you for taking the time to report this bug and helping to make Ubuntu better. tzdata 2023c still says that Jerusalem had a 3 hours offset: ``` $ LC_ALL=C TZ=Asia/Jerusalem date -d "2015-09-24 19:20:38 Z" Thu Sep 24 22:20:38 IDT 2015 ``` So your clock was set incorrectly (two hour offset). ** Changed in: tzdata (Ubuntu) Status: New => Invalid ** Summary changed: - Wrong local time in tzdata + Wrong local time in tzdata for Asia/Jerusalem -- 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/1499472 Title: Wrong local time in tzdata for Asia/Jerusalem Status in tzdata package in Ubuntu: Invalid Bug description: When running the following, I get the correct time zone, but incorrect local time: ~$ sudo dpkg-reconfigure tzdata Current default time zone: 'Asia/Jerusalem' Local time is now: Thu Sep 24 22:20:38 IDT 2015. Universal Time is now: Thu Sep 24 19:20:38 UTC 2015. The correct local time is, in fact, 20:20, so, apparently, the current version of tzdata in Precise is way off. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: tzdata 2015f-0ubuntu0.12.04 ProcVersionSignature: Ubuntu 3.2.0-90.128-generic 3.2.69 Uname: Linux 3.2.0-90-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.9 Architecture: amd64 Date: Thu Sep 24 22:21:18 2015 InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: tzdata UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1499472/+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 1437805] Re: Time didn't change itself after Daylight Saving Time started in Edinburgh
Marking this bug as invalid for tzdata, because there is no indication that the timezone data were wrong. ** Changed in: tzdata (Ubuntu) Status: New => Invalid -- 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/1437805 Title: Time didn't change itself after Daylight Saving Time started in Edinburgh Status in Ubuntu Clock App: Invalid Status in ubuntu-system-settings: New Status in tzdata package in Ubuntu: Invalid Status in ubuntu-system-settings package in Ubuntu: New Bug description: Today (29/03/2015) at 7:59 in the morning I've noticed the clock on my bq phone shows 6:59. I remember setting the time zone to "Edinburgh" when setting the phone. Today, when I opened the clock app I've seen this [1]. You can also notice that time for Warsaw is correct. Then I went to time and date settings. It displayed "UTC+0". I set "Time zone:" to Edinburgh again. After that it showed "UTC+1" and time was correct. I must add that yesterday I set alarm on another device (Android phone) which thankfully woken me up on the right time. Otherwise my son's football training would be missed. [1] see the attached screenshot, please. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1437805/+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 1573045] Re: tzdata is swapping UTC for CDT local time
Thank you for taking the time to report this bug and helping to make Ubuntu better. Your clock was running with the local time, but the system expected the clock to run in UTC. The solution is to update the clock to the correct time in UTC. Then setting the correct timezone will give you the correct local time. ** Changed in: tzdata (Ubuntu) Status: New => Invalid -- 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/1573045 Title: tzdata is swapping UTC for CDT local time Status in tzdata package in Ubuntu: Invalid Bug description: I'm in Chicago and the correct date/time is Thu Apr 21 08:33:02 UTC 2016. There is no way I would be at work in the office at 3am :-) The UTC is picking up my CDT data. Even when I switch to another timezone, like Africa, UTC is showing local time CDT. jcrochon@achilles:~$ sudo dpkg-reconfigure tzdata Current default time zone: 'America/Chicago' Local time is now: Thu Apr 21 03:33:02 CDT 2016. Universal Time is now: Thu Apr 21 08:33:02 UTC 2016. jcrochon@achilles:~$ sudo dpkg-reconfigure tzdata Current default time zone: 'Africa/Abidjan' Local time is now: Thu Apr 21 08:33:11 GMT 2016. Universal Time is now: Thu Apr 21 08:33:11 UTC 2016. jcrochon@achilles:~$ sudo dpkg-reconfigure tzdata Current default time zone: 'America/Chicago' Local time is now: Thu Apr 21 03:33:20 CDT 2016. Universal Time is now: Thu Apr 21 08:33:20 UTC 2016. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: tzdata 2016d-0ubuntu0.16.04 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Apr 21 03:36:03 2016 InstallationDate: Installed on 2016-04-07 (13 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) PackageArchitecture: all SourcePackage: tzdata UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1573045/+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 1797941] Re: package tzdata 2018e-0ubuntu0.18.04 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Were you able to successfully re-install tzdata? ** Changed in: tzdata (Ubuntu) Status: Confirmed => Incomplete -- 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/1797941 Title: package tzdata 2018e-0ubuntu0.18.04 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in tzdata package in Ubuntu: Incomplete Bug description: package installation failed, inconsistent content ProblemType: Package DistroRelease: Ubuntu 18.04 Package: tzdata 2018e-0ubuntu0.18.04 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Mon Oct 15 20:16:55 2018 DuplicateSignature: package:tzdata:2018e-0ubuntu0.18.04 Setting up libcurl3-gnutls:amd64 (7.58.0-2ubuntu3.3) ... dpkg: error processing package tzdata (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-10-15 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: tzdata Title: package tzdata 2018e-0ubuntu0.18.04 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1797941/+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 1638014] Re: package tzdata 2016h-0ubuntu0.16.04 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Thank you for taking the time to report this bug and helping to make Ubuntu better. Relevant log: ``` dpkg: error processing package tzdata (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration ``` Were you able to update your system since your report? ** Changed in: tzdata (Ubuntu) Status: New => Incomplete -- 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/1638014 Title: package tzdata 2016h-0ubuntu0.16.04 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in tzdata package in Ubuntu: Incomplete Bug description: computer turning grey and not wanting to respond ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tzdata 2016h-0ubuntu0.16.04 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 Uname: Linux 4.4.0-42-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Mon Oct 31 08:54:57 2016 DuplicateSignature: package:tzdata:2016h-0ubuntu0.16.04 Processing triggers for libc-bin (2.23-0ubuntu3) ... dpkg: error processing package tzdata (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-08-11 (80 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: tzdata Title: package tzdata 2016h-0ubuntu0.16.04 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1638014/+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 1732408] Re: package tzdata 2017c-0ubuntu0.16.04 failed to install/upgrade: нет доступа к архиву: Нет такого файла или каталога
Thank you for taking the time to report this bug and helping to make Ubuntu better. The translated bug title says: "no access to archive: No such file or directory" DpkgTerminalLog.txt does not contain logs for tzdata. Were you able to update your system since your report? ** Changed in: tzdata (Ubuntu) Status: New => Incomplete -- 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/1732408 Title: package tzdata 2017c-0ubuntu0.16.04 failed to install/upgrade: нет доступа к архиву: Нет такого файла или каталога Status in tzdata package in Ubuntu: Incomplete Bug description: during update ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tzdata 2017c-0ubuntu0.16.04 ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Wed Nov 15 13:00:07 2017 ErrorMessage: нет доступа к архиву: Нет такого файла или каталога InstallationDate: Installed on 2017-10-09 (37 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: tzdata Title: package tzdata 2017c-0ubuntu0.16.04 failed to install/upgrade: нет доступа к архиву: Нет такого файла или каталога UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1732408/+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 1877934] Re: package tzdata 2019c-3ubuntu1 failed to install/upgrade: unable to open '/usr/share/zoneinfo/posix/Australia/Lord_Howe.dpkg-new': Operation not permitted
Thank you for taking the time to report this bug and helping to make Ubuntu better. Relevant log: ``` Unpacking tzdata (2019c-3ubuntu1) over (2019c-3) ... dpkg: error processing archive /tmp/apt-dpkg-install-3xiD6g/20-tzdata_2019c-3ubuntu1_all.deb (--unpack): unable to open '/usr/share/zoneinfo/posix/Australia/Lord_Howe.dpkg-new': Operation not permitted ``` Were you able to update your system since your report? ** Changed in: tzdata (Ubuntu) Status: New => Incomplete -- 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/1877934 Title: package tzdata 2019c-3ubuntu1 failed to install/upgrade: unable to open '/usr/share/zoneinfo/posix/Australia/Lord_Howe.dpkg-new': Operation not permitted Status in tzdata package in Ubuntu: Incomplete Bug description: Crashing again and again ProblemType: Package DistroRelease: Ubuntu 20.04 Package: tzdata 2019c-3ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun May 10 14:59:54 2020 DuplicateSignature: package:tzdata:2019c-3ubuntu1 Unpacking tzdata (2019c-3ubuntu1) over (2019c-3) ... dpkg: error processing archive /tmp/apt-dpkg-install-3xiD6g/20-tzdata_2019c-3ubuntu1_all.deb (--unpack): unable to open '/usr/share/zoneinfo/posix/Australia/Lord_Howe.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/share/zoneinfo/posix/Australia/Lord_Howe.dpkg-new': Operation not permitted InstallationDate: Installed on 2019-05-29 (347 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: tzdata Title: package tzdata 2019c-3ubuntu1 failed to install/upgrade: unable to open '/usr/share/zoneinfo/posix/Australia/Lord_Howe.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1877934/+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 1447347] Re: package tzdata 2015b-0ubuntu0.14.04 failed to install/upgrade: package tzdata is not ready for configuration cannot configure (current status `half-installed')
Thank you for taking the time to report this bug and helping to make Ubuntu better. Relevant log: ``` dpkg: error processing package tzdata (--configure): package tzdata is not ready for configuration cannot configure (current status `half-installed') ``` Were you able to update your system? ** Changed in: tzdata (Ubuntu) Status: New => Incomplete -- 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/1447347 Title: package tzdata 2015b-0ubuntu0.14.04 failed to install/upgrade: package tzdata is not ready for configuration cannot configure (current status `half-installed') Status in tzdata package in Ubuntu: Incomplete Bug description: System message when I logged in. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: tzdata 2015b-0ubuntu0.14.04 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.8 AptOrdering: tzdata: Configure Architecture: amd64 Date: Tue Apr 21 07:12:05 2015 DuplicateSignature: package:tzdata:2015b-0ubuntu0.14.04:package tzdata is not ready for configuration cannot configure (current status `half-installed') ErrorMessage: package tzdata is not ready for configuration cannot configure (current status `half-installed') InstallationDate: Installed on 2014-10-19 (185 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: tzdata Title: package tzdata 2015b-0ubuntu0.14.04 failed to install/upgrade: package tzdata is not ready for configuration cannot configure (current status `half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1447347/+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 1972977] Re: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_q
is fixed for real now ** Changed in: mesa (Ubuntu Jammy) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1972977 Title: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_query() Status in Mesa: Fix Released Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Fix Released Bug description: [Impact] Gnome-shell is crashing on older gen Intel hw due to a memory leak. [Fix] An upstream commit that fixes the memleak in the crocus driver (which is only used on Intel 4th gen chips and older) [Test case] Either test this on an old Intel or see if there's a dent in the reported crashes. [Where things could go wrong] Mainly if this would not fix the crashes. -- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 42.0-2ubuntu1, the problem page at https://errors.ubuntu.com/problem/d8aa1211f7e8b219a4ee6dcae294ac16decd7fe3 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1972977/+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 1990089] Re: Screen freeze when performing memory stress in Wayland mode
** Changed in: mesa (Ubuntu Jammy) Status: Confirmed => 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/1990089 Title: Screen freeze when performing memory stress in Wayland mode Status in Linux: New Status in Mutter: Fix Released Status in OEM Priority Project: Incomplete Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: In Progress Status in mesa source package in Kinetic: Won't Fix Status in mesa source package in Lunar: Fix Released Bug description: [Impact] Running stress-ng freezes the screen under wayland on intel iris. Upstream has fixed it in 5aae8a05264c354aa93017d323ce238858f68227 iris: Retry DRM_IOCTL_I915_GEM_EXECBUFFER2 on ENOMEM 646cff13bca8a92b846984d782ef00e57d34d7a1 Revert "iris: Avoid abort() if kernel can't allocate memory" which need to be backported for 22.2.5 [Test case] Install the update, then 1. stress-ng --stack 0 --timeout 300 2. check the screen and note that it shouldn't freeze anymore. [Where things could go wrong] This moves checking ENOMEM to the right place, so it's hard to see how it might cause issues. -- [Steps to reproduce] (disable systemd-oomd or executing over ssh) (below command allocates a lot of memory to stress kernel page fault) 1. stress-ng --stack 0 --timeout 300 2. check the screen [Expected result] Screen will update slowly when performing the stress-test. but screen needs back to work after stress. [Actual result] Screen freeze after stress test. [Additional information] kernel version: vmlinuz-5.17.0-1017-oem kernel version: vmlinuz-6.0.0-06rc4drmtip20220910-generic Mesa version: 22.0.5-0ubuntu0.1 Mutter version: 42.2-0ubuntu1 Gnome-shell version: 42.2-0ubuntu0.2 * Issue happens in Wayland only * gnome-shell keeps issuing ioctl() ``` (gdb) bt #0 __GI___ioctl (fd=fd@entry=14, request=request@entry=3223348419) at ../sysdeps/unix/sysv/linux/ioctl.c:36 #1 0x7fcacab0eb4f in intel_ioctl (arg=0x7fffc5404d80, request=3223348419, fd=14) at ../src/intel/common/intel_gem.h:75 #2 iris_wait_syncobj (timeout_nsec=140736502713808, syncobj=, bufmgr=) at ../src/gallium/drivers/iris/iris_fence.c:229 #3 iris_wait_syncobj (bufmgr=, syncobj=, timeout_nsec=timeout_nsec@entry=9223372036854775807) at ../src/gallium/drivers/iris/iris_fence.c:215 #4 0x7fcacab8beab in iris_get_query_result (result=0x7fffc5404e50, wait=, query=0x55774159b800, ctx=) at ../src/gallium/drivers/iris/iris_query.c:635 #5 iris_get_query_result (ctx=, query=0x55774159b800, wait=, result=0x7fffc5404e50) at ../src/gallium/drivers/iris/iris_query.c:601 #6 0x7fcaca405e89 in tc_get_query_result (_pipe=, query=0x55774159b800, wait=, result=0x7fffc5404e50) at ../src/gallium/auxiliary/util/u_threaded_context.c:881 #7 0x7fcaca0f0e64 in get_query_result (pipe=pipe@entry=0x55773f87bad0, q=q@entry=0x557741a0c790, wait=wait@entry=1 '\001') at ../src/mesa/main/queryobj.c:266 #8 0x7fcaca0f1b12 in _mesa_wait_query (q=0x557741a0c790, ctx=0x55773f8af980) at ../src/mesa/main/queryobj.c:344 #9 get_query_object (ctx=0x55773f8af980, func=func@entry=0x7fcacaf28283 "glGetQueryObjecti64v", id=, pname=34918, ptype=ptype@entry=5134, buf=0x0, offset=140736502714192) at ../src/mesa/main/queryobj.c:1174 #10 0x7fcaca0f2d65 in _mesa_GetQueryObjecti64v (id=, pname=, params=) at ../src/mesa/main/queryobj.c:1257 #11 0x7fcadfa39b90 in ?? () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #12 0x7fcadfa751b9 in cogl_frame_info_get_rendering_duration_ns () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #13 0x7fcadf8819c4 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #14 0x7fcadfa6e7a2 in _cogl_onscreen_notify_complete () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #15 0x7fcadf969cdd in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #16 0x7fcadf96ec7b in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #17 0x7fcadf969601 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #18 0x7fcadf98395e in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #19 0x7fcadf96962d in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #20 0x7fcae0743c24 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x7fcae07986f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7fcae0743293 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7fcadf8d0849 in meta_context_run_main_loop () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #24 0x55773f1a4f12 in ?? () #25 0x7fcadf429d90 in __libc_start_call_main (main=main@entry=0x55773f1a4a70, argc=argc@entry=1, argv=argv@entry=0x7fffc54053e8) at
[Touch-packages] [Bug 1510261] Re: package tzdata-java 2015g-0ubuntu0.14.04 failed to install/upgrade: пакет tzdata-java уже установлен и настроен
Thank you for taking the time to report this bug and helping to make Ubuntu better. Relevant log: ``` (Чтение базы данных … на данный момент установлено 186863 \D1 \84айла и каталога.) Подготовка к распаковке …/libqt4-opengl_4%3a4.8.5+git192-g085f851+dfsg-2ubuntu4.1_i386.deb … Распаковывается libqt4-opengl:i386 (4:4.8.5+git192-g085f851+dfsg-2ubuntu4.1) … Выбор ранее не выбранного пакета libqtwebkit4:i386. Подготовка к распаковке …/libqtwebkit4_2.3.2-0ubuntu7_i386.deb … Распаковывается libqtwebkit4:i386 (2.3.2-0ubuntu7) … Выбор ранее не выбранного пакета qtchooser. Подготовка к распаковке …/qtchooser_39-g4717841-3_i386.deb … Распаковывается qtchooser (39-g4717841-3) … Выбор ранее не выбранного пакета qdbus. Подготовка к распаковке …/qdbus_4%3a4.8.5+git192-g085f851+dfsg-2ubuntu4.1_i386.deb … Распаковывается qdbus (4:4.8.5+git192-g085f851+dfsg-2ubuntu4.1) … Выбор ранее не выбранного пакета libqt4-dbus:i386. Подготовка к распаковке …/libqt4-dbus_4%3a4.8.5+git192-g085f851+dfsg-2ubuntu4.1_i386.deb … Распаковывается libqt4-dbus:i386 (4:4.8.5+git192-g085f851+dfsg-2ubuntu4.1) … Выбор ранее не выбранного пакета libqt4-webkit. Подготовка к распаковке …/libqt4-webkit_4%3a4.8.5+git192-g085f851+dfsg-2ubuntu4.1_i386.deb … Распаковывается libqt4-webkit (4:4.8.5+git192-g085f851+dfsg-2ubuntu4.1) … Обрабатываются триггеры для man-db (2.6.7.1-1ubuntu1) … dpkg: ошибка при обработке пакета tzdata-java (--configure): пакет tzdata-java уже установлен и настроен ``` The package tzdata-java is not shipped in Ubuntu any more and the bug is quite old. I will close this bug. Please respond back if you still have troubles. ** Changed in: tzdata (Ubuntu) Status: New => Fix Released -- 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/1510261 Title: package tzdata-java 2015g-0ubuntu0.14.04 failed to install/upgrade: пакет tzdata-java уже установлен и настроен Status in tzdata package in Ubuntu: Fix Released Bug description: dunno what that is ProblemType: Package DistroRelease: Ubuntu 14.04 Package: tzdata-java 2015g-0ubuntu0.14.04 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-32-generic i686 ApportVersion: 2.14.1-0ubuntu3.17 Architecture: i386 Date: Mon Oct 26 22:23:35 2015 ErrorMessage: пакет tzdata-java уже установлен и настроен InstallationDate: Installed on 2015-10-26 (0 days ago) InstallationMedia: It PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: tzdata Title: package tzdata-java 2015g-0ubuntu0.14.04 failed to install/upgrade: пакет tzdata-java уже установлен и настроен UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1510261/+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 2003339] Re: kwin_x11: The X11 connection broke: I/O error (code 1)
** Changed in: mesa (Ubuntu Jammy) Status: New => 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/2003339 Title: kwin_x11: The X11 connection broke: I/O error (code 1) Status in KDE Base Workspace: Fix Released Status in Mesa: Fix Released Status in kwin package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in kwin source package in Jammy: Invalid Status in mesa source package in Jammy: In Progress Status in kwin package in Debian: New Bug description: [Impact] kwin might crash after running some time Two commits have been reverted upstream since 22.2.x branch was closed, needs those backported to fix this. [Test case] Run kwin for a day or so, which is usually enough time to hit this. [Where things could go wrong] This just reverts two commits, and they have been upstream for a few months now, so these causing a regression is unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+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 2013128] Re: mesa: set info.separate_shader for ARB programs
** Changed in: mesa (Ubuntu Jammy) Status: New => 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/2013128 Title: mesa: set info.separate_shader for ARB programs Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: In Progress Status in mesa source package in Kinetic: Won't Fix Bug description: [Impact] There's a shader bug in 22.2.x, fixed upstream in commit https://gitlab.freedesktop.org/mesa/mesa/-/commit/7e68cf91d74e6bd9a88c2b52417451d9afec4782 but since 22.2.x is already EOL, we need to backport it. [Test case] Install update, check that the application from the submitter works. [Where things could go wrong] This is a oneliner that flips a bool, but it's hard to imagine use-cases which would expect the old value. -- I have a bug that occurs in Ubuntu 22.04's most up to date libmesa related packages (=22.2.5-0ubuntu0.1~22.04.1) that was not there in =22.0.1-1ubuntu2. It has since been solved in mesa's repo and pulled into debian's repo. I do not know the proper way to request an updated version be made for Ubuntu. I've manually installed many different versions of libmesa to test on my own that it was working in an older version, is broken in this update, and was fixed again in 22.3.4 and 22.3.5. The one-line fix is implemented here in libmesa's repo: https://gitlab.freedesktop.org/mesa/mesa/-/commit/7e68cf91d74e6bd9a88c2b52417451d9afec4782 Unfortunately I'm not using libmesa directly. I'm programming an application using fox-toolkit which interfaces with libmesa behind the scenes for me. I reported my issue to them first, and they stated it appears to be in the mesa library, which is what ultimately led me down the path to their repo, debian's repo, and here. Please let me know if I'm in the right spot, and, if so, what my next step is to properly report this. -- Feature Request: Upgrade mesa libraries to apply upstream bugfix to a bug introduced in 22.2.5-0ubuntu0.1~22.04.1. I was directed to report this bug via my question at answers.launchpad.net/ubuntu: https://answers.launchpad.net/ubuntu/+question/705988 Please let me know if you need further information. Thanks! > lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 > apt-cache policy libglx-mesa0 libglx-mesa0: Installed: 22.2.5-0ubuntu0.1~22.04.1 Candidate: 22.2.5-0ubuntu0.1~22.04.1 Version table: *** 22.2.5-0ubuntu0.1~22.04.1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 22.0.1-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libglx-mesa0 22.2.5-0ubuntu0.1~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: i3 Date: Tue Mar 28 15:30:59 2023 InstallationDate: Installed on 2022-04-28 (334 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2022-04-29T14:47:14.568862 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2013128/+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 2017142] Re: [jammy] VA-API doesn't work on DCN 3.1.4
** Changed in: mesa (Ubuntu Jammy) Status: New => 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/2017142 Title: [jammy] VA-API doesn't work on DCN 3.1.4 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: In Progress Bug description: [ Impact ] VA-API decoding doesn't work on DCN 3.1.4. Mesa 22.2.5 includes all the code to support it but is missing the chip ID. The device ID was included in upstream mesa 22.3.1. [ Test Plan ] * Verify that VA-API works using "mpv" or a similar tool that uses VA-API * Verify that '# vainfo' shows the correct information. [ Where problems could occur ] * If just the new ID is backported then they would be unique to DCN 3.1.4 as it's now running VA-API codepaths. * If newer mesa point release is adopted, then it could be a regression that happened in changes on common code in mesa between those two point releases. [ Other Info ] * It can be cherry picked with this single commit: https://gitlab.freedesktop.org/mesa/mesa/-/commit/4291e545d5a0f18c652f0ea57907f445392e8858 * AMD has already tested cherry-picked commit on top of the Ubuntu mesa 22.2.5 package and verified it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2017142/+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 1295911] Re: package tzdata-java 2014a-0ubuntu0.13.10 failed to install/upgrade: package tzdata-java is already installed and configured
Thank you for taking the time to report this bug and helping to make Ubuntu better. The package tzdata-java is not shipped in Ubuntu any more. The bug is quite old. Please respond back if you still have troubles. ** Changed in: tzdata (Ubuntu) Status: New => Fix Released -- 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/1295911 Title: package tzdata-java 2014a-0ubuntu0.13.10 failed to install/upgrade: package tzdata-java is already installed and configured Status in tzdata package in Ubuntu: Fix Released Bug description: accessing the menu ProblemType: Package DistroRelease: Ubuntu 13.10 Package: tzdata-java 2014a-0ubuntu0.13.10 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 Date: Wed Mar 19 19:49:06 2014 DuplicateSignature: package:tzdata-java:2014a-0ubuntu0.13.10:package tzdata-java is already installed and configured ErrorMessage: package tzdata-java is already installed and configured InstallationDate: Installed on 2010-09-21 (1277 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1) MarkForUpload: True PackageArchitecture: all SourcePackage: tzdata Title: package tzdata-java 2014a-0ubuntu0.13.10 failed to install/upgrade: package tzdata-java is already installed and configured UpgradeStatus: Upgraded to saucy on 2013-11-16 (125 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1295911/+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 1299716] Re: package tzdata 2014a-0ubuntu0.13.10 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. The end of dpkg terminal log says: ``` Обрабатываются триггеры для hicolor-icon-theme … (gtk-update-icon-cache:5903): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': Нет такого файла или каталога This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. (gtk-update-icon-cache-3.0:5909): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': Нет такого файла или каталога This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. Обрабатываются триггеры для gconf2 … ``` So it does not contain the part for the failing tzdata. Therefore I am marking this bug as invalid. Feel free to continue to report any other bugs you may find. ** Changed in: tzdata (Ubuntu) Status: New => Invalid -- 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/1299716 Title: package tzdata 2014a-0ubuntu0.13.10 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 Status in tzdata package in Ubuntu: Invalid Bug description: display manager crashed on log in ProblemType: Package DistroRelease: Ubuntu 13.10 Package: tzdata 2014a-0ubuntu0.13.10 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Sun Mar 30 13:31:06 2014 ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 InstallationDate: Installed on 2014-01-13 (76 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) MarkForUpload: True PackageArchitecture: all SourcePackage: tzdata Title: package tzdata 2014a-0ubuntu0.13.10 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1299716/+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 2003339] Re: kwin_x11: The X11 connection broke: I/O error (code 1)
** Description changed: - ... + [Impact] + + kwin might crash after running some time + + Two commits have been reverted upstream since 22.2.x branch was closed, + needs those backported to fix this. + + [Test case] + + Run kwin for a day or so, which is usually enough time to hit this. + + [Where things could go wrong] + + This just reverts two commits, and they have been upstream for a few + months now, so these causing a regression is unlikely. ** Also affects: mesa (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: kwin (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: kwin (Ubuntu Jammy) Status: New => Invalid -- 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/2003339 Title: kwin_x11: The X11 connection broke: I/O error (code 1) Status in KDE Base Workspace: Fix Released Status in Mesa: Fix Released Status in kwin package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in kwin source package in Jammy: Invalid Status in mesa source package in Jammy: New Status in kwin package in Debian: New Bug description: [Impact] kwin might crash after running some time Two commits have been reverted upstream since 22.2.x branch was closed, needs those backported to fix this. [Test case] Run kwin for a day or so, which is usually enough time to hit this. [Where things could go wrong] This just reverts two commits, and they have been upstream for a few months now, so these causing a regression is unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+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 627098] Re: package tzdata 2010l-0ubuntu0.10.04 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 10
*** This bug is a duplicate of bug 883739 *** https://bugs.launchpad.net/bugs/883739 Thank you for taking the time to report this bug and helping to make Ubuntu better. Relevant log message: ``` Préparation du remplacement de tzdata 2010k-0ubuntu0.10.04 (en utilisant .../tzdata_2010l-0ubuntu0.10.04_all.deb) ... Dépaquetage de la mise à jour de tzdata ... Paramétrage de tzdata (2010l-0ubuntu0.10.04) ... dpkg : erreur de traitement de tzdata (--configure) : le sous-processus script post-installation installé a retourné une erreur de sortie d'état 10 ``` Translation: ``` Preparing to replace tzdata 2010k-0ubuntu0.10.04 (using .../tzdata_2010l-0ubuntu0.10.04_all.deb) ... Unpacking tzdata update... Setting tzdata (2010l-0ubuntu0.10.04)... dpkg: error processing tzdata (--configure): installed post install script subprocess returned status exit error 10 ``` This is a duplicate of bug #883739 ** This bug has been marked a duplicate of bug 883739 package tzdata 2011m-0ubuntu0.11.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 -- 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/627098 Title: package tzdata 2010l-0ubuntu0.10.04 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 10 Status in tzdata package in Ubuntu: New Bug description: Binary package hint: tzdata Error with mixxx ProblemType: Package DistroRelease: Ubuntu 10.04 Package: tzdata 2010l-0ubuntu0.10.04 ProcVersionSignature: Ubuntu 2.6.32-24.41-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Fri Aug 27 23:54:46 2010 ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) PackageArchitecture: all SourcePackage: tzdata Title: package tzdata 2010l-0ubuntu0.10.04 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/627098/+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 883739] Re: package tzdata 2011m-0ubuntu0.11.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: tzdata (Ubuntu) Status: New => Confirmed -- 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/883739 Title: package tzdata 2011m-0ubuntu0.11.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 Status in tzdata package in Ubuntu: Incomplete Bug description: sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done The following packages have been kept back: linux-generic linux-headers-generic linux-image-generic The following packages will be upgraded: acpid empathy empathy-common libpam-modules libpam-modules-bin libpam-runtime libpam0g libreoffice-emailmerge libreoffice-help-en-us libreoffice-style-human libsyncdaemon-1.0-1 linux-libc-dev nautilus-sendto-empathy python-ubuntuone-client software-center ttf-opensymbol tzdata tzdata-java ubuntuone-client ubuntuone-client-gnome unity unity-common update-manager update-manager-core whois xserver-common xserver-xorg-core xserver-xorg-video-intel 28 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. 2 not fully installed or removed. Need to get 16.8 MB of archives. After this operation, 32.8 kB of additional disk space will be used. Do you want to continue [Y/n]? y Get:1 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main libpam0g i386 1.1.2-2ubuntu8.4 [50.6 kB] Get:2 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main libpam-modules-bin i386 1.1.2-2ubuntu8.4 [34.1 kB] Get:3 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main libpam-modules i386 1.1.2-2ubuntu8.4 [265 kB] Get:4 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main libpam-runtime all 1.1.2-2ubuntu8.4 [41.8 kB] Get:5 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main tzdata-java all 2011m-0ubuntu0.11.04 [136 kB] Get:6 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main tzdata all 2011m-0ubuntu0.11.04 [629 kB] Get:7 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main update-manager-core i386 1:0.150.5 [165 kB] Get:8 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main update-manager all 1:0.150.5 [651 kB] Get:9 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main acpid i386 1:2.0.7-1ubuntu2.1 [33.3 kB] Get:10 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main nautilus-sendto-empathy i386 2.34.0-0ubuntu3.2 [451 kB] Get:11 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main empathy i386 2.34.0-0ubuntu3.2 [956 kB] Get:12 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main empathy-common all 2.34.0-0ubuntu3.2 [389 kB] Get:13 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main libreoffice-emailmerge all 1:3.3.4-0ubuntu1 [5,876 B] Get:14 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main libreoffice-help-en-us all 1:3.3.4-0ubuntu1 [6,006 kB] Get:15 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main libreoffice-style-human all 1:3.3.4-0ubuntu1 [2,856 kB] Get:16 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main ubuntuone-client-gnome i386 1.6.2-0ubuntu2 [56.0 kB] Get:17 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main libsyncdaemon-1.0-1 i386 1.6.2-0ubuntu2 [42.7 kB] Get:18 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main ubuntuone-client all 1.6.2-0ubuntu2 [45.7 kB] Get:19 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main python-ubuntuone-client all 1.6.2-0ubuntu2 [210 kB] Get:20 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main linux-libc-dev i386 2.6.38-12.51 [786 kB] Get:21 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main software-center all 4.0.5 [462 kB] Get:22 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main ttf-opensymbol all 2:2.4.3+LibO3.3.4-0ubuntu1 [109 kB] Get:23 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main unity i386 3.8.16-0ubuntu1~natty3 [624 kB] Get:24 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main unity-common all 3.8.16-0ubuntu1~natty3 [17.8 kB] Get:25 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main whois i386 5.0.11ubuntu1.1 [29.8 kB] Get:26 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main xserver-common all 2:1.10.1-1ubuntu1.3 [31.7 kB] Get:27 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main xserver-xorg-core i386 2:1.10.1-1ubuntu1.3 [1,497 kB] Get:28 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main xserver-xorg-video-intel i386 2:2.14.0-4ubuntu7.2 [224 kB] Fetched 16.8 MB in 1min 10s (238 kB/s) Preconfiguring packages ... debconf: warning: possible database corruption. Will attempt to repair by adding back missing question libpam0g:i386. debconf: warning: possible database corruption. Will attempt to repair
[Touch-packages] [Bug 883739] Re: package tzdata 2011m-0ubuntu0.11.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10
Thank you for taking the time to report this bug and helping to make Ubuntu better. Relevant log message: ``` Preparing to replace tzdata-java 2011k-0ubuntu0.11.04 (using .../tzdata-java_2011m-0ubuntu0.11.04_all.deb) ... Unpacking replacement tzdata-java ... Preparing to replace tzdata 2011k-0ubuntu0.11.04 (using .../tzdata_2011m-0ubuntu0.11.04_all.deb) ... Unpacking replacement tzdata ... Setting up tzdata (2011m-0ubuntu0.11.04) ... dpkg: error processing tzdata (--configure): subprocess installed post-installation script returned error exit status 10 ``` There is not enough log output for further investigation. Do you still experience a similar issue with a recent Ubuntu version? ** Changed in: tzdata (Ubuntu) Status: Confirmed => Incomplete -- 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/883739 Title: package tzdata 2011m-0ubuntu0.11.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 Status in tzdata package in Ubuntu: Incomplete Bug description: sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done The following packages have been kept back: linux-generic linux-headers-generic linux-image-generic The following packages will be upgraded: acpid empathy empathy-common libpam-modules libpam-modules-bin libpam-runtime libpam0g libreoffice-emailmerge libreoffice-help-en-us libreoffice-style-human libsyncdaemon-1.0-1 linux-libc-dev nautilus-sendto-empathy python-ubuntuone-client software-center ttf-opensymbol tzdata tzdata-java ubuntuone-client ubuntuone-client-gnome unity unity-common update-manager update-manager-core whois xserver-common xserver-xorg-core xserver-xorg-video-intel 28 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. 2 not fully installed or removed. Need to get 16.8 MB of archives. After this operation, 32.8 kB of additional disk space will be used. Do you want to continue [Y/n]? y Get:1 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main libpam0g i386 1.1.2-2ubuntu8.4 [50.6 kB] Get:2 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main libpam-modules-bin i386 1.1.2-2ubuntu8.4 [34.1 kB] Get:3 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main libpam-modules i386 1.1.2-2ubuntu8.4 [265 kB] Get:4 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main libpam-runtime all 1.1.2-2ubuntu8.4 [41.8 kB] Get:5 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main tzdata-java all 2011m-0ubuntu0.11.04 [136 kB] Get:6 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main tzdata all 2011m-0ubuntu0.11.04 [629 kB] Get:7 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main update-manager-core i386 1:0.150.5 [165 kB] Get:8 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main update-manager all 1:0.150.5 [651 kB] Get:9 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main acpid i386 1:2.0.7-1ubuntu2.1 [33.3 kB] Get:10 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main nautilus-sendto-empathy i386 2.34.0-0ubuntu3.2 [451 kB] Get:11 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main empathy i386 2.34.0-0ubuntu3.2 [956 kB] Get:12 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main empathy-common all 2.34.0-0ubuntu3.2 [389 kB] Get:13 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main libreoffice-emailmerge all 1:3.3.4-0ubuntu1 [5,876 B] Get:14 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main libreoffice-help-en-us all 1:3.3.4-0ubuntu1 [6,006 kB] Get:15 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main libreoffice-style-human all 1:3.3.4-0ubuntu1 [2,856 kB] Get:16 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main ubuntuone-client-gnome i386 1.6.2-0ubuntu2 [56.0 kB] Get:17 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main libsyncdaemon-1.0-1 i386 1.6.2-0ubuntu2 [42.7 kB] Get:18 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main ubuntuone-client all 1.6.2-0ubuntu2 [45.7 kB] Get:19 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main python-ubuntuone-client all 1.6.2-0ubuntu2 [210 kB] Get:20 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main linux-libc-dev i386 2.6.38-12.51 [786 kB] Get:21 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main software-center all 4.0.5 [462 kB] Get:22 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main ttf-opensymbol all 2:2.4.3+LibO3.3.4-0ubuntu1 [109 kB] Get:23 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main unity i386 3.8.16-0ubuntu1~natty3 [624 kB] Get:24 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main unity-common all 3.8.16-0ubuntu1~natty3 [17.8 kB] Get:25 http://in.archive.ubuntu.com/ubuntu/ natty-updates/main whois i386 5.0.11ubuntu1.1 [29.8 kB] Get:26
[Touch-packages] [Bug 2015562] Re: Segfault in dnsmasq when using certain static domain entries + DoH (bugfix possibly exists upstream)
Hi Gordon, I prepared a package with the fix, as suggested by Bryce. Would you be so kind as to test it and share your results? The package is in the following PPA: https://launchpad.net/~mirespace/+archive/ubuntu/dnsmasq-lp2015562 I could check that the SIGSEV scenario goes away with the fix (thanks, Sergio, for the help and extra pair of eyes on checking the setup for the steps to reproduce!). A curious thing to me is that the error is not present in Kinetic, but Kinetic and Jammy share the same upstream version: 2.86-1.1. I'm taking a look at the ubuntu modifications that are different between them to see if we can narrow it down to the bits that make it possible, and maybe that would be more feasible to be SRUed to Jammy. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/2015562 Title: Segfault in dnsmasq when using certain static domain entries + DoH (bugfix possibly exists upstream) Status in dnsmasq package in Ubuntu: Fix Released Status in dnsmasq source package in Jammy: In Progress Bug description: Hi folks, I've been using dnsmasq for my home DNS needs, which includes returning null entries for certain domain queries. The specific case in which I found this segfault was returning null records for Netflix (to ensure Netflix does not try to use my IPv6 tunnel to egress traffic through). I've been using very simple configuration snippet to achieve this, this is attached as netflix-nov6.conf (the full file contains more entries). Ever since I've upgraded from Ubuntu 20.04 to 22.04, dnsmasq kept segfaulting at random occasions. I also attempted do an apt update&, but there are no newer versions of this package available. Further research into this issue showed that a surefire way to trigger this segfault was to go to a website blocked via this method (for testing purposes, a dig query works quite well). The segfault can be reproduced reliably, and always occurs after one or a few queries towards the "blocked" domain entries. I found a commit in the upstream dnsmasq git repo which seems to fix this issue, the fix made it into 2.87: https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=de372d6914ae20a1f9997815f258efbf3b14c39b Would it be possible to backport this into the version used in the current LTS Ubuntu release? Thanks! -- $ lsb_release -d Description: Ubuntu 22.04.2 LTS $ apt-cache policy dnsmasq dnsmasq: Installed: 2.86-1.1ubuntu0.2 Candidate: 2.86-1.1ubuntu0.2 Version table: *** 2.86-1.1ubuntu0.2 500 500 http://de.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages 100 /var/lib/dpkg/status 2.86-1.1ubuntu0.1 500 500 http://de.archive.ubuntu.com/ubuntu jammy-security/universe amd64 Packages 2.86-1.1 500 500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages -- Excerpt from the dnsmasq logs, with debugging enabled, after I loaded fast.com: Apr 07 13:47:41 budgie systemd[1]: Started dnsmasq - A lightweight DHCP and caching DNS server. Apr 07 13:47:42 budgie dnsmasq[109976]: query[type=65] fast.dradis.netflix.com from 192.168.10.82 Apr 07 13:47:42 budgie dnsmasq[109976]: config error is REFUSED (EDE: network error) Apr 07 13:47:43 budgie dnsmasq[109976]: query[type=65] ichnaea-web.netflix.com from 192.168.10.82 Apr 07 13:47:43 budgie systemd[1]: dnsmasq.service: Main process exited, code=dumped, status=11/SEGV Apr 07 13:47:43 budgie systemd[1]: dnsmasq.service: Failed with result 'core-dump'. Core dump is also attached. Reproduction steps: - 1. Install dnsmasq on Ubuntu 22.04 (or any Ubuntu release using dnsmasq 2.86) - 1.5. Configure one or multiple DNS servers for dnsmasq - 2. Copy netflix-nov6.conf into /etc/dnsmasq.d/ - 3. Restart/reload dnsmasq - 3.5 Verify that dnsmasq resolves domains correctly: root@budgie:~# dig +short -tA ubuntu.com @127.0.0.1 185.125.190.21 185.125.190.20 185.125.190.29 root@budgie:~# dig +short -t ubuntu.com @127.0.0.1 2620:2d:4000:1::28 2620:2d:4000:1::26 2620:2d:4000:1::27 - 4. Perform a type65 / HTTPS recordtype query for netflix.com towards the dnsmasq server once or twice: root@budgie:~# dig +short -tTYPE65 netflix.com @127.0.0.1 root@budgie:~# dig +short -tTYPE65 netflix.com @127.0.0.1 ;; communications error to 127.0.0.1#53: timed out ;; communications error to 127.0.0.1#53: connection refused ;; communications error to 127.0.0.1#53: connection refused ;; no servers could be reached - 5. Check logs to verify segfault: Apr 07 14:03:28 budgie systemd[1]: Started dnsmasq - A lightweight DHCP and caching DNS server. Apr 07 14:03:32 budgie dnsmasq[111585]: query[type=65] netflix.com from 127.0.0.1 Apr 07 14:03:32 budgie dnsmasq[111585]: config error is REFUSED
[Touch-packages] [Bug 672322] Re: Time not adjusted automatically for DST (transition from EDT to EST)
This is bug report is quite old and it is unclear what the cause was. Do you still experience issues during DST adjustments? ** Changed in: tzdata (Ubuntu) Status: New => Incomplete -- 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/672322 Title: Time not adjusted automatically for DST (transition from EDT to EST) Status in Indicator Date and Time: Invalid Status in tzdata package in Ubuntu: Incomplete Bug description: Binary package hint: indicator-datetime Today, time changed from North American Eastern Daylight Time to Eastern Standard Time. I assumed that Ubuntu would change my clock automatically since every other electronic device I own does so. See attached picture. Do I need to be synced with time servers for the DST adjustment? I don't think that should be a requirement. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: indicator-datetime 0.0.6-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 Architecture: i386 Date: Sun Nov 7 16:13:52 2010 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: indicator-datetime To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/672322/+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 2015562] Re: Segfault in dnsmasq when using certain static domain entries + DoH (bugfix possibly exists upstream)
** Changed in: dnsmasq (Ubuntu Jammy) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/2015562 Title: Segfault in dnsmasq when using certain static domain entries + DoH (bugfix possibly exists upstream) Status in dnsmasq package in Ubuntu: Fix Released Status in dnsmasq source package in Jammy: In Progress Bug description: Hi folks, I've been using dnsmasq for my home DNS needs, which includes returning null entries for certain domain queries. The specific case in which I found this segfault was returning null records for Netflix (to ensure Netflix does not try to use my IPv6 tunnel to egress traffic through). I've been using very simple configuration snippet to achieve this, this is attached as netflix-nov6.conf (the full file contains more entries). Ever since I've upgraded from Ubuntu 20.04 to 22.04, dnsmasq kept segfaulting at random occasions. I also attempted do an apt update&, but there are no newer versions of this package available. Further research into this issue showed that a surefire way to trigger this segfault was to go to a website blocked via this method (for testing purposes, a dig query works quite well). The segfault can be reproduced reliably, and always occurs after one or a few queries towards the "blocked" domain entries. I found a commit in the upstream dnsmasq git repo which seems to fix this issue, the fix made it into 2.87: https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=de372d6914ae20a1f9997815f258efbf3b14c39b Would it be possible to backport this into the version used in the current LTS Ubuntu release? Thanks! -- $ lsb_release -d Description: Ubuntu 22.04.2 LTS $ apt-cache policy dnsmasq dnsmasq: Installed: 2.86-1.1ubuntu0.2 Candidate: 2.86-1.1ubuntu0.2 Version table: *** 2.86-1.1ubuntu0.2 500 500 http://de.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages 100 /var/lib/dpkg/status 2.86-1.1ubuntu0.1 500 500 http://de.archive.ubuntu.com/ubuntu jammy-security/universe amd64 Packages 2.86-1.1 500 500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages -- Excerpt from the dnsmasq logs, with debugging enabled, after I loaded fast.com: Apr 07 13:47:41 budgie systemd[1]: Started dnsmasq - A lightweight DHCP and caching DNS server. Apr 07 13:47:42 budgie dnsmasq[109976]: query[type=65] fast.dradis.netflix.com from 192.168.10.82 Apr 07 13:47:42 budgie dnsmasq[109976]: config error is REFUSED (EDE: network error) Apr 07 13:47:43 budgie dnsmasq[109976]: query[type=65] ichnaea-web.netflix.com from 192.168.10.82 Apr 07 13:47:43 budgie systemd[1]: dnsmasq.service: Main process exited, code=dumped, status=11/SEGV Apr 07 13:47:43 budgie systemd[1]: dnsmasq.service: Failed with result 'core-dump'. Core dump is also attached. Reproduction steps: - 1. Install dnsmasq on Ubuntu 22.04 (or any Ubuntu release using dnsmasq 2.86) - 1.5. Configure one or multiple DNS servers for dnsmasq - 2. Copy netflix-nov6.conf into /etc/dnsmasq.d/ - 3. Restart/reload dnsmasq - 3.5 Verify that dnsmasq resolves domains correctly: root@budgie:~# dig +short -tA ubuntu.com @127.0.0.1 185.125.190.21 185.125.190.20 185.125.190.29 root@budgie:~# dig +short -t ubuntu.com @127.0.0.1 2620:2d:4000:1::28 2620:2d:4000:1::26 2620:2d:4000:1::27 - 4. Perform a type65 / HTTPS recordtype query for netflix.com towards the dnsmasq server once or twice: root@budgie:~# dig +short -tTYPE65 netflix.com @127.0.0.1 root@budgie:~# dig +short -tTYPE65 netflix.com @127.0.0.1 ;; communications error to 127.0.0.1#53: timed out ;; communications error to 127.0.0.1#53: connection refused ;; communications error to 127.0.0.1#53: connection refused ;; no servers could be reached - 5. Check logs to verify segfault: Apr 07 14:03:28 budgie systemd[1]: Started dnsmasq - A lightweight DHCP and caching DNS server. Apr 07 14:03:32 budgie dnsmasq[111585]: query[type=65] netflix.com from 127.0.0.1 Apr 07 14:03:32 budgie dnsmasq[111585]: config error is REFUSED (EDE: network error) Apr 07 14:03:33 budgie dnsmasq[111585]: query[type=65] netflix.com from 127.0.0.1 Apr 07 14:03:33 budgie systemd[1]: dnsmasq.service: Main process exited, code=dumped, status=11/SEGV Apr 07 14:03:33 budgie systemd[1]: dnsmasq.service: Failed with result 'core-dump'. -- netflix-nov6.conf: # Null response on these domains server=/netflix.com/# address=/netflix.com/:: server=/netflix.net/# address=/netflix.net/:: server=/nflxext.com/# address=/nflxext.com/:: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2015562/+subscriptions -- Mailing list:
[Touch-packages] [Bug 2003339] Re: kwin_x11: The X11 connection broke: I/O error (code 1)
noticed that if disabling compositing right after kwin restart - then it seem to crash much less often (3 days so far without crash), but plasmashell still freezes approx once a day (default ubuntu 22.04.2 with kept back 5.15 kernel (because of amdgpu bugs in 5.19)) KDE Plasma: 5.24.7 KDE Frameworks: 5.92.0 QT Version: 5.15.3 MESA: 22.2.5 amdgpu -- 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/2003339 Title: kwin_x11: The X11 connection broke: I/O error (code 1) Status in KDE Base Workspace: Fix Released Status in Mesa: Fix Released Status in kwin package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in kwin package in Debian: New Bug description: ... To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+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 2017209] Re: systemd-oomd fails with "ConditionControlGroupController=memory was not met"
** Tags added: linux-raspi raspberry-pi -- 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/2017209 Title: systemd-oomd fails with "ConditionControlGroupController=memory was not met" Status in linux-raspi package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: PROBLEM SUMMARY: Just upgraded to Ubuntu 23.04 (lunar) from Ubuntu 22.10 (kinetic). systemd-oomd fails with "ConditionControlGroupController=memory was not met" during boot. If you manually started it after boot it starts but after a few minutes it fails with the same error. These are the journalctl entries regarding this problem: abr 20 23:12:48 fpgrpi systemd[1]: Listening on systemd-oomd.socket - Userspace Out-Of-Memory (OOM) Killer Socket. abr 20 23:12:48 fpgrpi systemd[1]: systemd-oomd.service - Userspace Out-Of-Memory (OOM) Killer was skipped because of an unmet condition check (ConditionControlGroupController=memory). --- Line repeat 20 times --- abr 20 23:12:49 fpgrpi systemd[1]: systemd-oomd.service - Userspace Out-Of-Memory (OOM) Killer was skipped because of an unmet condition check (ConditionControlGroupController=memory). abr 20 23:12:49 fpgrpi systemd[1]: systemd-oomd.socket: Trigger limit hit, refusing further activation. abr 20 23:12:49 fpgrpi systemd[1]: systemd-oomd.socket: Failed with result 'trigger-limit-hit'. This is the systemctl status for systemd-oomd.service and systemd-oomd.socket: # systemctl status systemd-oomd.service ○ systemd-oomd.service - Userspace Out-Of-Memory (OOM) Killer Loaded: loaded (/lib/systemd/system/systemd-oomd.service; enabled; preset: enabled) Active: inactive (dead) TriggeredBy: × systemd-oomd.socket Condition: start condition failed at Thu 2023-04-20 23:21:07 CEST; 9h ago └─ ConditionControlGroupController=memory was not met Docs: man:systemd-oomd.service(8) # systemctl status systemd-oomd.socket × systemd-oomd.socket - Userspace Out-Of-Memory (OOM) Killer Socket Loaded: loaded (/lib/systemd/system/systemd-oomd.socket; enabled; preset: enabled) Active: failed (Result: trigger-limit-hit) since Thu 2023-04-20 23:21:07 CEST; 9h ago Duration: 2min 2.252s Triggers: ● systemd-oomd.service Docs: man:systemd-oomd.service(8) Listen: /run/systemd/oom/io.system.ManagedOOM (Stream) ADITIONAL INFO: --- Machine is an arm64 "Raspberry Pi 4 Model B Rev 1.4 8GB" # uname -a Linux fpgrpi 6.2.0-1004-raspi #5-Ubuntu SMP PREEMPT Mon Apr 3 11:15:14 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux # lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 # apt-cache policy systemd-oomd systemd-oomd: Instalados: 252.5-2ubuntu3 Candidato: 252.5-2ubuntu3 Tabla de versión: *** 252.5-2ubuntu3 500 500 http://ports.ubuntu.com/ubuntu-ports lunar/main arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2017209/+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 2017229] Re: Update evolution-data-server to 3.48.1
** Description changed: Impact -- This is a new stable release in the stable 3.48 series. https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/3.48.1/NEWS - It is required to update the evolution app to 3.48.1 + It is required to update the evolution app to 3.48.1 (LP: #2017231) Test Case - Install the update Log out and log back in (or restart) Ensure that GNOME Calendar and Evolution still work fine. What Could Go Wrong --- As a component of GNOME core, there is a micro-release exception for evolution-data-server https://wiki.ubuntu.com/StableReleaseUpdates/GNOME evolution-data-server is included in all the Ubuntu Desktop flavors except for Kubuntu, Lubuntu, and Xubuntu + + Other Info + -- + There will be new evolution-data-server bugfix releases monthly until September. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/2017229 Title: Update evolution-data-server to 3.48.1 Status in evolution-data-server package in Ubuntu: In Progress Bug description: Impact -- This is a new stable release in the stable 3.48 series. https://gitlab.gnome.org/GNOME/evolution-data- server/-/blob/3.48.1/NEWS It is required to update the evolution app to 3.48.1 (LP: #2017231) Test Case - Install the update Log out and log back in (or restart) Ensure that GNOME Calendar and Evolution still work fine. What Could Go Wrong --- As a component of GNOME core, there is a micro-release exception for evolution-data-server https://wiki.ubuntu.com/StableReleaseUpdates/GNOME evolution-data-server is included in all the Ubuntu Desktop flavors except for Kubuntu, Lubuntu, and Xubuntu Other Info -- There will be new evolution-data-server bugfix releases monthly until September. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/2017229/+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 2016908] Re: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default)
vmlinuz-6.2.0-18-generic is good, so regression introduced in 6.2.0-19 abi, suspecting new apparmor stack https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012136 ** Also affects: apparmor Importance: Undecided Status: New ** 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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/2016908 Title: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default) Status in AppArmor: New Status in MAAS: Triaged Status in maas-images: Invalid Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in systemd package in Ubuntu: Invalid Bug description: I'm assuming the image being used for these deploys is 20230417 or 20230417.1 based on the fact that I saw a 6.2 kernel being used which I don't believe was part of the 20230319 serial. I don't have access to the maas server, so I can't directly check any log files. MAAS Version: 3.3.2 Here's where the serial log indicates it can't download the squashfs. The full log is attached as scobee-lunar-no-squashfs.log (there are some other console message intermixed): no search or nameservers found in /run/net-BOOTIF.conf /run/net-*.conf /run/net6 -*.conf :: root=squash:http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.04/lunar/candi date/squa[ 206.804704] Btrfs loaded, crc32c=crc32c-generic, zoned=yes, fsverity =yes shfs :: mount_squash downloading http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.0 4/lunar/candidate/squashfs to /root.tmp.img Connecting to 10.229.32.21:5248 (10.229.32.21:5248) wget: can't connect to remote host (10.229.32.21): Network is unreachable :: mount -t squashfs -o loop '/root.tmp.img' '/root.tmp' mount: mounting /root.tmp.img on /root.tmp failed: No such file or directory done. Still gathering logs and info and will update as I go. Kernel Bug / Apparmor reproducer $ wget https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-kernel $ wget https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-initrd $ qemu-system-x86_64 -nographic -m 2G -kernel ./boot-kernel -initrd ./boot-initrd -append 'console=ttyS0 break=modules apparmor=0' #start the VM Starting systemd-udevd version 252.5-2ubuntu3 Spawning shell within the initramfs BusyBox v1.35.0 (Ubuntu 1:1.35.0-4ubuntu1) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) udevadm info --export-db Failed to set death signal: Invalid argument Observe that udevadm fails to setup death signal, with in systemd code is this https://github.com/systemd/systemd/blob/08c2f9c626e0f0052d505b1b7e52f335c0fbfa1d/src/basic/process- util.c#L1252 if (flags & (FORK_DEATHSIG|FORK_DEATHSIG_SIGINT)) if (prctl(PR_SET_PDEATHSIG, (flags & FORK_DEATHSIG_SIGINT) ? SIGINT : SIGTERM) < 0) { log_full_errno(prio, errno, "Failed to set death signal: %m"); _exit(EXIT_FAILURE); } workaround set kernel commandline to `apparmor=1` MAAS bug Why is maas setting `apparmor=0` ? Ubuntu shouldn't be used without apparmor. Even for deployment and commisioning. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2016908/+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 2017209] Re: systemd-oomd fails with "ConditionControlGroupController=memory was not met"
I see that memory cgroup is not enabled: # cat /proc/cgroups | grep y #subsys_name hierarchy num_cgroups enabled memory 0 121 0 So a workaround is to enable it adding "cgroup_enable=memory" to "/boot/firmware/cmdline.txt" kernel parameters file for Raspberry Pi boards. As systemd-oomd worked in Ubuntu 22.10 (Kinetic) without the need of set this kernel parameter the only conclusion I've reached is that this cgroup has been disabled in a point between kernel 5.19 (kinetic) and kernel 6.2 (lunar) releases. So I've searched the Raspberry Pi kernel commits related and found this one: https://github.com/raspberrypi/linux/commit/28aec65bb1743c9bfa53b036999f9835c889704e cgroup: Disable cgroup "memory" by default Some Raspberry Pis have limited RAM and most users won't use the cgroup memory support so it is disabled by default. Enable with: cgroup_enable=memory At this point I don't know what team should fix this bug. I've updated it for linux-raspi package. ** Package changed: systemd (Ubuntu) => linux-raspi (Ubuntu) ** Also affects: systemd (Ubuntu) Importance: Undecided Status: 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/2017209 Title: systemd-oomd fails with "ConditionControlGroupController=memory was not met" Status in linux-raspi package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: PROBLEM SUMMARY: Just upgraded to Ubuntu 23.04 (lunar) from Ubuntu 22.10 (kinetic). systemd-oomd fails with "ConditionControlGroupController=memory was not met" during boot. If you manually started it after boot it starts but after a few minutes it fails with the same error. These are the journalctl entries regarding this problem: abr 20 23:12:48 fpgrpi systemd[1]: Listening on systemd-oomd.socket - Userspace Out-Of-Memory (OOM) Killer Socket. abr 20 23:12:48 fpgrpi systemd[1]: systemd-oomd.service - Userspace Out-Of-Memory (OOM) Killer was skipped because of an unmet condition check (ConditionControlGroupController=memory). --- Line repeat 20 times --- abr 20 23:12:49 fpgrpi systemd[1]: systemd-oomd.service - Userspace Out-Of-Memory (OOM) Killer was skipped because of an unmet condition check (ConditionControlGroupController=memory). abr 20 23:12:49 fpgrpi systemd[1]: systemd-oomd.socket: Trigger limit hit, refusing further activation. abr 20 23:12:49 fpgrpi systemd[1]: systemd-oomd.socket: Failed with result 'trigger-limit-hit'. This is the systemctl status for systemd-oomd.service and systemd-oomd.socket: # systemctl status systemd-oomd.service ○ systemd-oomd.service - Userspace Out-Of-Memory (OOM) Killer Loaded: loaded (/lib/systemd/system/systemd-oomd.service; enabled; preset: enabled) Active: inactive (dead) TriggeredBy: × systemd-oomd.socket Condition: start condition failed at Thu 2023-04-20 23:21:07 CEST; 9h ago └─ ConditionControlGroupController=memory was not met Docs: man:systemd-oomd.service(8) # systemctl status systemd-oomd.socket × systemd-oomd.socket - Userspace Out-Of-Memory (OOM) Killer Socket Loaded: loaded (/lib/systemd/system/systemd-oomd.socket; enabled; preset: enabled) Active: failed (Result: trigger-limit-hit) since Thu 2023-04-20 23:21:07 CEST; 9h ago Duration: 2min 2.252s Triggers: ● systemd-oomd.service Docs: man:systemd-oomd.service(8) Listen: /run/systemd/oom/io.system.ManagedOOM (Stream) ADITIONAL INFO: --- Machine is an arm64 "Raspberry Pi 4 Model B Rev 1.4 8GB" # uname -a Linux fpgrpi 6.2.0-1004-raspi #5-Ubuntu SMP PREEMPT Mon Apr 3 11:15:14 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux # lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 # apt-cache policy systemd-oomd systemd-oomd: Instalados: 252.5-2ubuntu3 Candidato: 252.5-2ubuntu3 Tabla de versión: *** 252.5-2ubuntu3 500 500 http://ports.ubuntu.com/ubuntu-ports lunar/main arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2017209/+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 2017224] Re: Cannot enable bluetooth in gnome-shell
Adding: Experimental = true KernelExperimental = true To: /etc/bluetooth/main.conf Cleared the above message but still can't enable bluetooth in Gnome Settings. -- 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/2017224 Title: Cannot enable bluetooth in gnome-shell Status in bluez package in Ubuntu: New Status in gnome-settings-daemon package in Ubuntu: New Bug description: After upgrade to 23.04, Bluetooth service is started but can't enable it in gnome-shell. Apr 21 11:34:15 ZB systemd[1]: Starting bluetooth.service - Bluetooth service... Apr 21 11:34:15 ZB systemd[1403]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555) Apr 21 11:34:15 ZB bluetoothd[1403]: Bluetooth daemon 5.66 Apr 21 11:34:15 ZB bluetoothd[1403]: Starting SDP server Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/vcp.c:vcp_init() D-Bus experimental not enabled Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to init vcp plugin Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to init mcp plugin Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to init bap plugin Apr 21 11:34:15 ZB systemd[1]: Started bluetooth.service - Bluetooth service. Apr 21 11:34:15 ZB bluetoothd[1403]: Bluetooth management interface 1.22 initialized ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: bluez 5.66-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 21 11:44:40 2023 InstallationDate: Installed on 2023-01-04 (106 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) InterestingModules: bnep btusb bluetooth MachineType: ASUSTeK COMPUTER INC. ZenBook UX435EG_UX435EG ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash SourcePackage: bluez UpgradeStatus: Upgraded to lunar on 2023-04-21 (0 days ago) dmi.bios.date: 04/22/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX435EG.315 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX435EG dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX435EG.315:bd04/22/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX435EG_UX435EG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX435EG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX435EG_UX435EG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: mtime.conffile..etc.bluetooth.input.conf: 2023-02-28T07:11:41.547346 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2017224/+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 2017229] [NEW] Update evolution-data-server to 3.48.1
Public bug reported: Impact -- This is a new stable release in the stable 3.48 series. https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/3.48.1/NEWS It is required to update the evolution app to 3.48.1 Test Case - Install the update Log out and log back in (or restart) Ensure that GNOME Calendar and Evolution still work fine. What Could Go Wrong --- As a component of GNOME core, there is a micro-release exception for evolution-data-server https://wiki.ubuntu.com/StableReleaseUpdates/GNOME evolution-data-server is included in all the Ubuntu Desktop flavors except for Kubuntu, Lubuntu, and Xubuntu ** Affects: evolution-data-server (Ubuntu) Importance: Medium Status: In Progress ** Tags: lunar upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/2017229 Title: Update evolution-data-server to 3.48.1 Status in evolution-data-server package in Ubuntu: In Progress Bug description: Impact -- This is a new stable release in the stable 3.48 series. https://gitlab.gnome.org/GNOME/evolution-data- server/-/blob/3.48.1/NEWS It is required to update the evolution app to 3.48.1 Test Case - Install the update Log out and log back in (or restart) Ensure that GNOME Calendar and Evolution still work fine. What Could Go Wrong --- As a component of GNOME core, there is a micro-release exception for evolution-data-server https://wiki.ubuntu.com/StableReleaseUpdates/GNOME evolution-data-server is included in all the Ubuntu Desktop flavors except for Kubuntu, Lubuntu, and Xubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/2017229/+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 2017224] [NEW] Cannot enable bluetooth in gnome-shell
Public bug reported: After upgrade to 23.04, Bluetooth service is started but can't enable it in gnome-shell. Apr 21 11:34:15 ZB systemd[1]: Starting bluetooth.service - Bluetooth service... Apr 21 11:34:15 ZB systemd[1403]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555) Apr 21 11:34:15 ZB bluetoothd[1403]: Bluetooth daemon 5.66 Apr 21 11:34:15 ZB bluetoothd[1403]: Starting SDP server Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/vcp.c:vcp_init() D-Bus experimental not enabled Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to init vcp plugin Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to init mcp plugin Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to init bap plugin Apr 21 11:34:15 ZB systemd[1]: Started bluetooth.service - Bluetooth service. Apr 21 11:34:15 ZB bluetoothd[1403]: Bluetooth management interface 1.22 initialized ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: bluez 5.66-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 21 11:44:40 2023 InstallationDate: Installed on 2023-01-04 (106 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) InterestingModules: bnep btusb bluetooth MachineType: ASUSTeK COMPUTER INC. ZenBook UX435EG_UX435EG ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash SourcePackage: bluez UpgradeStatus: Upgraded to lunar on 2023-04-21 (0 days ago) dmi.bios.date: 04/22/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX435EG.315 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX435EG dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX435EG.315:bd04/22/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX435EG_UX435EG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX435EG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX435EG_UX435EG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: mtime.conffile..etc.bluetooth.input.conf: 2023-02-28T07:11:41.547346 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ** Also affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- 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/2017224 Title: Cannot enable bluetooth in gnome-shell Status in bluez package in Ubuntu: New Status in gnome-settings-daemon package in Ubuntu: New Bug description: After upgrade to 23.04, Bluetooth service is started but can't enable it in gnome-shell. Apr 21 11:34:15 ZB systemd[1]: Starting bluetooth.service - Bluetooth service... Apr 21 11:34:15 ZB systemd[1403]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555) Apr 21 11:34:15 ZB bluetoothd[1403]: Bluetooth daemon 5.66 Apr 21 11:34:15 ZB bluetoothd[1403]: Starting SDP server Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/vcp.c:vcp_init() D-Bus experimental not enabled Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to init vcp plugin Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to init mcp plugin Apr 21 11:34:15 ZB bluetoothd[1403]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled Apr 21 11:34:15 ZB bluetoothd[1403]: src/plugin.c:plugin_init() Failed to init bap plugin Apr 21 11:34:15 ZB systemd[1]: Started bluetooth.service - Bluetooth service. Apr 21 11:34:15 ZB bluetoothd[1403]: Bluetooth management interface 1.22 initialized ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: bluez 5.66-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop:
[Touch-packages] [Bug 2016908] Re: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default)
alexsander-souza - if you can make this on per-distro basis that would be great. Indeed empty (thus apparmor=1) should work on jammy and up, but yes we can never know. And having it for lunar onwards would be super nice, because yes overlayfs apparmor things got fixed a while back and are expected to work from now on. And there are more and more things that rely on apparmor to be there. -- 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/2016908 Title: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default) Status in MAAS: Triaged Status in maas-images: Invalid Status in linux package in Ubuntu: Triaged Status in systemd package in Ubuntu: Invalid Bug description: I'm assuming the image being used for these deploys is 20230417 or 20230417.1 based on the fact that I saw a 6.2 kernel being used which I don't believe was part of the 20230319 serial. I don't have access to the maas server, so I can't directly check any log files. MAAS Version: 3.3.2 Here's where the serial log indicates it can't download the squashfs. The full log is attached as scobee-lunar-no-squashfs.log (there are some other console message intermixed): no search or nameservers found in /run/net-BOOTIF.conf /run/net-*.conf /run/net6 -*.conf :: root=squash:http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.04/lunar/candi date/squa[ 206.804704] Btrfs loaded, crc32c=crc32c-generic, zoned=yes, fsverity =yes shfs :: mount_squash downloading http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.0 4/lunar/candidate/squashfs to /root.tmp.img Connecting to 10.229.32.21:5248 (10.229.32.21:5248) wget: can't connect to remote host (10.229.32.21): Network is unreachable :: mount -t squashfs -o loop '/root.tmp.img' '/root.tmp' mount: mounting /root.tmp.img on /root.tmp failed: No such file or directory done. Still gathering logs and info and will update as I go. Kernel Bug / Apparmor reproducer $ wget https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-kernel $ wget https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-initrd $ qemu-system-x86_64 -nographic -m 2G -kernel ./boot-kernel -initrd ./boot-initrd -append 'console=ttyS0 break=modules apparmor=0' #start the VM Starting systemd-udevd version 252.5-2ubuntu3 Spawning shell within the initramfs BusyBox v1.35.0 (Ubuntu 1:1.35.0-4ubuntu1) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) udevadm info --export-db Failed to set death signal: Invalid argument Observe that udevadm fails to setup death signal, with in systemd code is this https://github.com/systemd/systemd/blob/08c2f9c626e0f0052d505b1b7e52f335c0fbfa1d/src/basic/process- util.c#L1252 if (flags & (FORK_DEATHSIG|FORK_DEATHSIG_SIGINT)) if (prctl(PR_SET_PDEATHSIG, (flags & FORK_DEATHSIG_SIGINT) ? SIGINT : SIGTERM) < 0) { log_full_errno(prio, errno, "Failed to set death signal: %m"); _exit(EXIT_FAILURE); } workaround set kernel commandline to `apparmor=1` MAAS bug Why is maas setting `apparmor=0` ? Ubuntu shouldn't be used without apparmor. Even for deployment and commisioning. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/2016908/+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 1990089] Re: Screen freeze when performing memory stress in Wayland mode
** Description changed: [Impact] Running stress-ng freezes the screen under wayland on intel iris. Upstream has fixed it in 5aae8a05264c354aa93017d323ce238858f68227 iris: Retry DRM_IOCTL_I915_GEM_EXECBUFFER2 on ENOMEM 646cff13bca8a92b846984d782ef00e57d34d7a1 Revert "iris: Avoid abort() if kernel can't allocate memory" which need to be backported for 22.2.5 [Test case] Install the update, then 1. stress-ng --stack 0 --timeout 300 2. check the screen and note that it shouldn't freeze anymore. [Where things could go wrong] - WIP + This moves checking ENOMEM to the right place, so it's hard to see how + it might cause issues. -- [Steps to reproduce] (disable systemd-oomd or executing over ssh) (below command allocates a lot of memory to stress kernel page fault) 1. stress-ng --stack 0 --timeout 300 2. check the screen [Expected result] Screen will update slowly when performing the stress-test. but screen needs back to work after stress. [Actual result] Screen freeze after stress test. [Additional information] kernel version: vmlinuz-5.17.0-1017-oem kernel version: vmlinuz-6.0.0-06rc4drmtip20220910-generic Mesa version: 22.0.5-0ubuntu0.1 Mutter version: 42.2-0ubuntu1 Gnome-shell version: 42.2-0ubuntu0.2 * Issue happens in Wayland only * gnome-shell keeps issuing ioctl() ``` (gdb) bt #0 __GI___ioctl (fd=fd@entry=14, request=request@entry=3223348419) at ../sysdeps/unix/sysv/linux/ioctl.c:36 #1 0x7fcacab0eb4f in intel_ioctl (arg=0x7fffc5404d80, request=3223348419, fd=14) at ../src/intel/common/intel_gem.h:75 #2 iris_wait_syncobj (timeout_nsec=140736502713808, syncobj=, bufmgr=) at ../src/gallium/drivers/iris/iris_fence.c:229 #3 iris_wait_syncobj (bufmgr=, syncobj=, timeout_nsec=timeout_nsec@entry=9223372036854775807) at ../src/gallium/drivers/iris/iris_fence.c:215 #4 0x7fcacab8beab in iris_get_query_result (result=0x7fffc5404e50, wait=, query=0x55774159b800, ctx=) at ../src/gallium/drivers/iris/iris_query.c:635 #5 iris_get_query_result (ctx=, query=0x55774159b800, wait=, result=0x7fffc5404e50) at ../src/gallium/drivers/iris/iris_query.c:601 #6 0x7fcaca405e89 in tc_get_query_result (_pipe=, query=0x55774159b800, wait=, result=0x7fffc5404e50) at ../src/gallium/auxiliary/util/u_threaded_context.c:881 #7 0x7fcaca0f0e64 in get_query_result (pipe=pipe@entry=0x55773f87bad0, q=q@entry=0x557741a0c790, wait=wait@entry=1 '\001') at ../src/mesa/main/queryobj.c:266 #8 0x7fcaca0f1b12 in _mesa_wait_query (q=0x557741a0c790, ctx=0x55773f8af980) at ../src/mesa/main/queryobj.c:344 #9 get_query_object (ctx=0x55773f8af980, func=func@entry=0x7fcacaf28283 "glGetQueryObjecti64v", id=, pname=34918, ptype=ptype@entry=5134, buf=0x0, offset=140736502714192) at ../src/mesa/main/queryobj.c:1174 #10 0x7fcaca0f2d65 in _mesa_GetQueryObjecti64v (id=, pname=, params=) at ../src/mesa/main/queryobj.c:1257 #11 0x7fcadfa39b90 in ?? () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #12 0x7fcadfa751b9 in cogl_frame_info_get_rendering_duration_ns () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #13 0x7fcadf8819c4 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #14 0x7fcadfa6e7a2 in _cogl_onscreen_notify_complete () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #15 0x7fcadf969cdd in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #16 0x7fcadf96ec7b in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #17 0x7fcadf969601 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #18 0x7fcadf98395e in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #19 0x7fcadf96962d in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #20 0x7fcae0743c24 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x7fcae07986f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7fcae0743293 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7fcadf8d0849 in meta_context_run_main_loop () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #24 0x55773f1a4f12 in ?? () #25 0x7fcadf429d90 in __libc_start_call_main (main=main@entry=0x55773f1a4a70, argc=argc@entry=1, argv=argv@entry=0x7fffc54053e8) at ../sysdeps/nptl/libc_start_call_main.h:58 #26 0x7fcadf429e40 in __libc_start_main_impl (main=0x55773f1a4a70, argc=1, argv=0x7fffc54053e8, init=, fini=, rtld_fini=, stack_end=0x7fffc54053d8) at ../csu/libc-start.c:392 #27 0x55773f1a51b5 in ?? () ``` Other discussion thread: https://gitlab.freedesktop.org/drm/intel/-/issues/6851 https://gitlab.gnome.org/GNOME/mutter/-/issues/2431 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter (not installed) Uname: Linux 5.18.0-rc2+ x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64
[Touch-packages] [Bug 2011415] Re: /usr/bin/software-properties-gtk:AttributeError:on_pktask_finish:net_status_changed
The autopkgtest issue raised before has been resolved after a retry it seems. -- 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/2011415 Title: /usr/bin/software-properties- gtk:AttributeError:on_pktask_finish:net_status_changed Status in software-properties package in Ubuntu: Invalid Status in software-properties source package in Focal: Fix Committed Bug description: * Impact The change from the previous revision to handle connectivity change use an API not available on focal and trigger an exception * Test case - detach the system from ubuntu pro if it's attached - open software-properties - go the ubuntu pro tab - click on 'enable ubuntu pro' - while the dialog is open disconnect and reconnect the network - change the selection from manual token to PIN the UI should update and no error should be triggered Check also that the error reports stop for the new version (url referenced below) * Regression potential If the callback were not working as expected the UI could end up not responding to status change or not accepting the PIN or token entered, validate that the different methods still work as expected to register -- The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.9.11, the problem page at https://errors.ubuntu.com/problem/22525c20f3bbf4ac03854d8a844e8d5f746b2959 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2011415/+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 1990089] Re: Screen freeze when performing memory stress in Wayland mode
** Description changed: - [Fix] - The fix is in upstream mesa as + [Impact] + + Running stress-ng freezes the screen under wayland on intel iris. + Upstream has fixed it in + 5aae8a05264c354aa93017d323ce238858f68227 iris: Retry DRM_IOCTL_I915_GEM_EXECBUFFER2 on ENOMEM 646cff13bca8a92b846984d782ef00e57d34d7a1 Revert "iris: Avoid abort() if kernel can't allocate memory" + + which need to be backported for 22.2.5 + + [Test case] + + Install the update, then + + 1. stress-ng --stack 0 --timeout 300 + 2. check the screen + + and note that it shouldn't freeze anymore. + + [Where things could go wrong] + + WIP + + -- [Steps to reproduce] (disable systemd-oomd or executing over ssh) (below command allocates a lot of memory to stress kernel page fault) 1. stress-ng --stack 0 --timeout 300 2. check the screen [Expected result] Screen will update slowly when performing the stress-test. but screen needs back to work after stress. [Actual result] Screen freeze after stress test. [Additional information] kernel version: vmlinuz-5.17.0-1017-oem kernel version: vmlinuz-6.0.0-06rc4drmtip20220910-generic Mesa version: 22.0.5-0ubuntu0.1 Mutter version: 42.2-0ubuntu1 Gnome-shell version: 42.2-0ubuntu0.2 * Issue happens in Wayland only * gnome-shell keeps issuing ioctl() ``` (gdb) bt #0 __GI___ioctl (fd=fd@entry=14, request=request@entry=3223348419) at ../sysdeps/unix/sysv/linux/ioctl.c:36 #1 0x7fcacab0eb4f in intel_ioctl (arg=0x7fffc5404d80, request=3223348419, fd=14) at ../src/intel/common/intel_gem.h:75 #2 iris_wait_syncobj (timeout_nsec=140736502713808, syncobj=, bufmgr=) at ../src/gallium/drivers/iris/iris_fence.c:229 #3 iris_wait_syncobj (bufmgr=, syncobj=, timeout_nsec=timeout_nsec@entry=9223372036854775807) at ../src/gallium/drivers/iris/iris_fence.c:215 #4 0x7fcacab8beab in iris_get_query_result (result=0x7fffc5404e50, wait=, query=0x55774159b800, ctx=) at ../src/gallium/drivers/iris/iris_query.c:635 #5 iris_get_query_result (ctx=, query=0x55774159b800, wait=, result=0x7fffc5404e50) at ../src/gallium/drivers/iris/iris_query.c:601 #6 0x7fcaca405e89 in tc_get_query_result (_pipe=, query=0x55774159b800, wait=, result=0x7fffc5404e50) at ../src/gallium/auxiliary/util/u_threaded_context.c:881 #7 0x7fcaca0f0e64 in get_query_result (pipe=pipe@entry=0x55773f87bad0, q=q@entry=0x557741a0c790, wait=wait@entry=1 '\001') at ../src/mesa/main/queryobj.c:266 #8 0x7fcaca0f1b12 in _mesa_wait_query (q=0x557741a0c790, ctx=0x55773f8af980) at ../src/mesa/main/queryobj.c:344 #9 get_query_object (ctx=0x55773f8af980, func=func@entry=0x7fcacaf28283 "glGetQueryObjecti64v", id=, pname=34918, ptype=ptype@entry=5134, buf=0x0, offset=140736502714192) at ../src/mesa/main/queryobj.c:1174 #10 0x7fcaca0f2d65 in _mesa_GetQueryObjecti64v (id=, pname=, params=) at ../src/mesa/main/queryobj.c:1257 #11 0x7fcadfa39b90 in ?? () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #12 0x7fcadfa751b9 in cogl_frame_info_get_rendering_duration_ns () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #13 0x7fcadf8819c4 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #14 0x7fcadfa6e7a2 in _cogl_onscreen_notify_complete () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #15 0x7fcadf969cdd in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #16 0x7fcadf96ec7b in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #17 0x7fcadf969601 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #18 0x7fcadf98395e in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #19 0x7fcadf96962d in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #20 0x7fcae0743c24 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x7fcae07986f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7fcae0743293 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7fcadf8d0849 in meta_context_run_main_loop () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #24 0x55773f1a4f12 in ?? () #25 0x7fcadf429d90 in __libc_start_call_main (main=main@entry=0x55773f1a4a70, argc=argc@entry=1, argv=argv@entry=0x7fffc54053e8) at ../sysdeps/nptl/libc_start_call_main.h:58 #26 0x7fcadf429e40 in __libc_start_main_impl (main=0x55773f1a4a70, argc=1, argv=0x7fffc54053e8, init=, fini=, rtld_fini=, stack_end=0x7fffc54053d8) at ../csu/libc-start.c:392 #27 0x55773f1a51b5 in ?? () ``` Other discussion thread: https://gitlab.freedesktop.org/drm/intel/-/issues/6851 https://gitlab.gnome.org/GNOME/mutter/-/issues/2431 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter (not installed) Uname: Linux 5.18.0-rc2+ x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5json: { "result": "skip" } Date: Mon
[Touch-packages] [Bug 2016950] Re: ubuntu 23.o4 新安装ssh默认端口修改不成功
** Changed in: openssh (Ubuntu) Status: New => Invalid -- 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/2016950 Title: ubuntu 23.o4 新安装ssh默认端口修改不成功 Status in openssh package in Ubuntu: Invalid Bug description: ubuntu 23.04新安装的系统,安装openssh-server 后,修改默认22端口不成功。 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubuntu-release-upgrader-core 1:23.04.5 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 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Apr 19 13:01:31 2023 InstallationDate: Installed on 2022-01-02 (471 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211105) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to lunar on 2022-11-12 (158 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting mtime.conffile..etc.update-manager.release-upgrades: 2022-11-13T20:00:56.608141 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2016950/+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 2017212] Re: ASUS N56VM fails to load GUI fresh install of Ubuntu 23.04
That error message sounds like a problem with the Nvidia driver, but your primary GPU seems to be Intel so I don't know why it would fail to "load GUI". ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-390 (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/2017212 Title: ASUS N56VM fails to load GUI fresh install of Ubuntu 23.04 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: NVRM: failed to copy vbios to system memory. NVRM: RmInitAdapter failed! 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.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.157 Wed Oct 12 09:19:07 UTC 2022 GCC version: ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Apr 21 07:45:45 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:1477] NVIDIA Corporation GF108M [GeForce GT 620M/630M/635M/640M LE] [10de:0de9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF108M [GeForce GT 620M/630M/635M/640M LE] [1043:1477] InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: ASUSTeK COMPUTER INC. N56VM ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=linux ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=0d37dcc1-3316-40c4-b4d9-7c5f62470833 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N56VM.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N56VM dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN56VM.214:bd08/28/2012:br4.6:svnASUSTeKCOMPUTERINC.:pnN56VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: N dmi.product.name: N56VM 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.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-390/+bug/2017212/+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 2017212] Re: ASUS N56VM fails to load GUI fresh install of Ubuntu 23.04
** 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/2017212 Title: ASUS N56VM fails to load GUI fresh install of Ubuntu 23.04 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: NVRM: failed to copy vbios to system memory. NVRM: RmInitAdapter failed! 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.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.157 Wed Oct 12 09:19:07 UTC 2022 GCC version: ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Apr 21 07:45:45 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:1477] NVIDIA Corporation GF108M [GeForce GT 620M/630M/635M/640M LE] [10de:0de9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF108M [GeForce GT 620M/630M/635M/640M LE] [1043:1477] InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: ASUSTeK COMPUTER INC. N56VM ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=linux ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=0d37dcc1-3316-40c4-b4d9-7c5f62470833 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N56VM.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N56VM dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN56VM.214:bd08/28/2012:br4.6:svnASUSTeKCOMPUTERINC.:pnN56VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: N dmi.product.name: N56VM 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.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-390/+bug/2017212/+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 1990089] Re: Screen freeze when performing memory stress in Wayland mode
lunar is released, skipping kinetic ** Changed in: mesa (Ubuntu Kinetic) Status: Confirmed => Won't Fix -- 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/1990089 Title: Screen freeze when performing memory stress in Wayland mode Status in Linux: New Status in Mutter: Fix Released Status in OEM Priority Project: Incomplete Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Confirmed Status in mesa source package in Kinetic: Won't Fix Status in mesa source package in Lunar: Fix Released Bug description: [Fix] The fix is in upstream mesa as 5aae8a05264c354aa93017d323ce238858f68227 iris: Retry DRM_IOCTL_I915_GEM_EXECBUFFER2 on ENOMEM 646cff13bca8a92b846984d782ef00e57d34d7a1 Revert "iris: Avoid abort() if kernel can't allocate memory" [Steps to reproduce] (disable systemd-oomd or executing over ssh) (below command allocates a lot of memory to stress kernel page fault) 1. stress-ng --stack 0 --timeout 300 2. check the screen [Expected result] Screen will update slowly when performing the stress-test. but screen needs back to work after stress. [Actual result] Screen freeze after stress test. [Additional information] kernel version: vmlinuz-5.17.0-1017-oem kernel version: vmlinuz-6.0.0-06rc4drmtip20220910-generic Mesa version: 22.0.5-0ubuntu0.1 Mutter version: 42.2-0ubuntu1 Gnome-shell version: 42.2-0ubuntu0.2 * Issue happens in Wayland only * gnome-shell keeps issuing ioctl() ``` (gdb) bt #0 __GI___ioctl (fd=fd@entry=14, request=request@entry=3223348419) at ../sysdeps/unix/sysv/linux/ioctl.c:36 #1 0x7fcacab0eb4f in intel_ioctl (arg=0x7fffc5404d80, request=3223348419, fd=14) at ../src/intel/common/intel_gem.h:75 #2 iris_wait_syncobj (timeout_nsec=140736502713808, syncobj=, bufmgr=) at ../src/gallium/drivers/iris/iris_fence.c:229 #3 iris_wait_syncobj (bufmgr=, syncobj=, timeout_nsec=timeout_nsec@entry=9223372036854775807) at ../src/gallium/drivers/iris/iris_fence.c:215 #4 0x7fcacab8beab in iris_get_query_result (result=0x7fffc5404e50, wait=, query=0x55774159b800, ctx=) at ../src/gallium/drivers/iris/iris_query.c:635 #5 iris_get_query_result (ctx=, query=0x55774159b800, wait=, result=0x7fffc5404e50) at ../src/gallium/drivers/iris/iris_query.c:601 #6 0x7fcaca405e89 in tc_get_query_result (_pipe=, query=0x55774159b800, wait=, result=0x7fffc5404e50) at ../src/gallium/auxiliary/util/u_threaded_context.c:881 #7 0x7fcaca0f0e64 in get_query_result (pipe=pipe@entry=0x55773f87bad0, q=q@entry=0x557741a0c790, wait=wait@entry=1 '\001') at ../src/mesa/main/queryobj.c:266 #8 0x7fcaca0f1b12 in _mesa_wait_query (q=0x557741a0c790, ctx=0x55773f8af980) at ../src/mesa/main/queryobj.c:344 #9 get_query_object (ctx=0x55773f8af980, func=func@entry=0x7fcacaf28283 "glGetQueryObjecti64v", id=, pname=34918, ptype=ptype@entry=5134, buf=0x0, offset=140736502714192) at ../src/mesa/main/queryobj.c:1174 #10 0x7fcaca0f2d65 in _mesa_GetQueryObjecti64v (id=, pname=, params=) at ../src/mesa/main/queryobj.c:1257 #11 0x7fcadfa39b90 in ?? () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #12 0x7fcadfa751b9 in cogl_frame_info_get_rendering_duration_ns () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #13 0x7fcadf8819c4 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #14 0x7fcadfa6e7a2 in _cogl_onscreen_notify_complete () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #15 0x7fcadf969cdd in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #16 0x7fcadf96ec7b in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #17 0x7fcadf969601 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #18 0x7fcadf98395e in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #19 0x7fcadf96962d in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #20 0x7fcae0743c24 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x7fcae07986f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7fcae0743293 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7fcadf8d0849 in meta_context_run_main_loop () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #24 0x55773f1a4f12 in ?? () #25 0x7fcadf429d90 in __libc_start_call_main (main=main@entry=0x55773f1a4a70, argc=argc@entry=1, argv=argv@entry=0x7fffc54053e8) at ../sysdeps/nptl/libc_start_call_main.h:58 #26 0x7fcadf429e40 in __libc_start_main_impl (main=0x55773f1a4a70, argc=1, argv=0x7fffc54053e8, init=, fini=, rtld_fini=, stack_end=0x7fffc54053d8) at ../csu/libc-start.c:392 #27 0x55773f1a51b5 in ?? () ``` Other discussion thread: https://gitlab.freedesktop.org/drm/intel/-/issues/6851
[Touch-packages] [Bug 2013128] Re: [feature request] Upgrade libglx-mesa0
lunar is released, so I'm skipping kinetic ** Description changed: - I have a bug that occurs in Ubuntu 22.04's most up to date libmesa - related packages (=22.2.5-0ubuntu0.1~22.04.1) that was not there in - =22.0.1-1ubuntu2. It has since been solved in mesa's repo and pulled - into debian's repo. I do not know the proper way to request an updated - version be made for Ubuntu. I've manually installed many different - versions of libmesa to test on my own that it was working in an older - version, is broken in this update, and was fixed again in 22.3.4 and - 22.3.5. + [Impact] + There's a shader bug in 22.2.x, fixed upstream in commit + + https://gitlab.freedesktop.org/mesa/mesa/-/commit/7e68cf91d74e6bd9a88c2b52417451d9afec4782 + + but since 22.2.x is already EOL, we need to backport it. + + [Test case] + + Install update, check that the application from the submitter works. + + + [Where things could go wrong] + This is a oneliner that flips a bool, but it's hard to imagine use-cases which would expect the old value. + + + -- + + + I have a bug that occurs in Ubuntu 22.04's most up to date libmesa related packages (=22.2.5-0ubuntu0.1~22.04.1) that was not there in =22.0.1-1ubuntu2. It has since been solved in mesa's repo and pulled into debian's repo. I do not know the proper way to request an updated version be made for Ubuntu. I've manually installed many different versions of libmesa to test on my own that it was working in an older version, is broken in this update, and was fixed again in 22.3.4 and 22.3.5. The one-line fix is implemented here in libmesa's repo: - https://gitlab.freedesktop.org/mesa/mesa/-/commit/7e68cf91d74e6bd9a88c2b52417451d9afec4782/pipelines + https://gitlab.freedesktop.org/mesa/mesa/-/commit/7e68cf91d74e6bd9a88c2b52417451d9afec4782 + + Unfortunately I'm not using libmesa directly. I'm programming an + application using fox-toolkit which interfaces with libmesa behind the + scenes for me. I reported my issue to them first, and they stated it + appears to be in the mesa library, which is what ultimately led me down + the path to their repo, debian's repo, and here. Please let me know if + I'm in the right spot, and, if so, what my next step is to properly + report this. -- Feature Request: Upgrade mesa libraries to apply upstream bugfix to a bug introduced in 22.2.5-0ubuntu0.1~22.04.1. I was directed to report this bug via my question at answers.launchpad.net/ubuntu: https://answers.launchpad.net/ubuntu/+question/705988 Please let me know if you need further information. Thanks! > lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 > apt-cache policy libglx-mesa0 libglx-mesa0: Installed: 22.2.5-0ubuntu0.1~22.04.1 Candidate: 22.2.5-0ubuntu0.1~22.04.1 Version table: *** 22.2.5-0ubuntu0.1~22.04.1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 22.0.1-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libglx-mesa0 22.2.5-0ubuntu0.1~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: i3 Date: Tue Mar 28 15:30:59 2023 InstallationDate: Installed on 2022-04-28 (334 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2022-04-29T14:47:14.568862 ** Summary changed: - [feature request] Upgrade libglx-mesa0 + set info.separate_shader ** Summary changed: - set info.separate_shader + mesa: set info.separate_shader for ARB programs ** Changed in: mesa (Ubuntu Kinetic) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2013128 Title: mesa: set info.separate_shader for ARB programs Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: New Status in mesa source package in Kinetic: Won't Fix Bug description: [Impact] There's a shader bug in 22.2.x, fixed upstream in commit https://gitlab.freedesktop.org/mesa/mesa/-/commit/7e68cf91d74e6bd9a88c2b52417451d9afec4782 but since 22.2.x is already EOL, we need to backport it. [Test case] Install update, check that the application from the
[Touch-packages] [Bug 1990089] Re: Screen freeze when performing memory stress in Wayland mode
** Changed in: mesa (Ubuntu Lunar) Status: In Progress => Fix Released ** Changed in: mesa (Ubuntu Lunar) Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned) ** Description changed: + [Fix] + The fix is in upstream mesa as + 5aae8a05264c354aa93017d323ce238858f68227 iris: Retry DRM_IOCTL_I915_GEM_EXECBUFFER2 on ENOMEM + 646cff13bca8a92b846984d782ef00e57d34d7a1 Revert "iris: Avoid abort() if kernel can't allocate memory" + [Steps to reproduce] (disable systemd-oomd or executing over ssh) (below command allocates a lot of memory to stress kernel page fault) 1. stress-ng --stack 0 --timeout 300 2. check the screen [Expected result] Screen will update slowly when performing the stress-test. but screen needs back to work after stress. [Actual result] Screen freeze after stress test. [Additional information] kernel version: vmlinuz-5.17.0-1017-oem kernel version: vmlinuz-6.0.0-06rc4drmtip20220910-generic Mesa version: 22.0.5-0ubuntu0.1 Mutter version: 42.2-0ubuntu1 Gnome-shell version: 42.2-0ubuntu0.2 * Issue happens in Wayland only * gnome-shell keeps issuing ioctl() ``` (gdb) bt #0 __GI___ioctl (fd=fd@entry=14, request=request@entry=3223348419) at ../sysdeps/unix/sysv/linux/ioctl.c:36 #1 0x7fcacab0eb4f in intel_ioctl (arg=0x7fffc5404d80, request=3223348419, fd=14) at ../src/intel/common/intel_gem.h:75 #2 iris_wait_syncobj (timeout_nsec=140736502713808, syncobj=, bufmgr=) at ../src/gallium/drivers/iris/iris_fence.c:229 #3 iris_wait_syncobj (bufmgr=, syncobj=, timeout_nsec=timeout_nsec@entry=9223372036854775807) at ../src/gallium/drivers/iris/iris_fence.c:215 #4 0x7fcacab8beab in iris_get_query_result (result=0x7fffc5404e50, wait=, query=0x55774159b800, ctx=) at ../src/gallium/drivers/iris/iris_query.c:635 #5 iris_get_query_result (ctx=, query=0x55774159b800, wait=, result=0x7fffc5404e50) at ../src/gallium/drivers/iris/iris_query.c:601 #6 0x7fcaca405e89 in tc_get_query_result (_pipe=, query=0x55774159b800, wait=, result=0x7fffc5404e50) at ../src/gallium/auxiliary/util/u_threaded_context.c:881 #7 0x7fcaca0f0e64 in get_query_result (pipe=pipe@entry=0x55773f87bad0, q=q@entry=0x557741a0c790, wait=wait@entry=1 '\001') at ../src/mesa/main/queryobj.c:266 #8 0x7fcaca0f1b12 in _mesa_wait_query (q=0x557741a0c790, ctx=0x55773f8af980) at ../src/mesa/main/queryobj.c:344 #9 get_query_object (ctx=0x55773f8af980, func=func@entry=0x7fcacaf28283 "glGetQueryObjecti64v", id=, pname=34918, ptype=ptype@entry=5134, buf=0x0, offset=140736502714192) at ../src/mesa/main/queryobj.c:1174 #10 0x7fcaca0f2d65 in _mesa_GetQueryObjecti64v (id=, pname=, params=) at ../src/mesa/main/queryobj.c:1257 #11 0x7fcadfa39b90 in ?? () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #12 0x7fcadfa751b9 in cogl_frame_info_get_rendering_duration_ns () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #13 0x7fcadf8819c4 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #14 0x7fcadfa6e7a2 in _cogl_onscreen_notify_complete () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #15 0x7fcadf969cdd in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #16 0x7fcadf96ec7b in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #17 0x7fcadf969601 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #18 0x7fcadf98395e in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #19 0x7fcadf96962d in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #20 0x7fcae0743c24 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x7fcae07986f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7fcae0743293 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7fcadf8d0849 in meta_context_run_main_loop () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #24 0x55773f1a4f12 in ?? () #25 0x7fcadf429d90 in __libc_start_call_main (main=main@entry=0x55773f1a4a70, argc=argc@entry=1, argv=argv@entry=0x7fffc54053e8) at ../sysdeps/nptl/libc_start_call_main.h:58 #26 0x7fcadf429e40 in __libc_start_main_impl (main=0x55773f1a4a70, argc=1, argv=0x7fffc54053e8, init=, fini=, rtld_fini=, stack_end=0x7fffc54053d8) at ../csu/libc-start.c:392 #27 0x55773f1a51b5 in ?? () ``` Other discussion thread: https://gitlab.freedesktop.org/drm/intel/-/issues/6851 https://gitlab.gnome.org/GNOME/mutter/-/issues/2431 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter (not installed) Uname: Linux 5.18.0-rc2+ x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5json: { "result": "skip" } Date: Mon Sep 19 10:39:59 2022 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see
[Touch-packages] [Bug 2017209] [NEW] systemd-oomd fails with "ConditionControlGroupController=memory was not met"
Public bug reported: PROBLEM SUMMARY: Just upgraded to Ubuntu 23.04 (lunar) from Ubuntu 22.10 (kinetic). systemd-oomd fails with "ConditionControlGroupController=memory was not met" during boot. If you manually started it after boot it starts but after a few minutes it fails with the same error. These are the journalctl entries regarding this problem: abr 20 23:12:48 fpgrpi systemd[1]: Listening on systemd-oomd.socket - Userspace Out-Of-Memory (OOM) Killer Socket. abr 20 23:12:48 fpgrpi systemd[1]: systemd-oomd.service - Userspace Out-Of-Memory (OOM) Killer was skipped because of an unmet condition check (ConditionControlGroupController=memory). --- Line repeat 20 times --- abr 20 23:12:49 fpgrpi systemd[1]: systemd-oomd.service - Userspace Out-Of-Memory (OOM) Killer was skipped because of an unmet condition check (ConditionControlGroupController=memory). abr 20 23:12:49 fpgrpi systemd[1]: systemd-oomd.socket: Trigger limit hit, refusing further activation. abr 20 23:12:49 fpgrpi systemd[1]: systemd-oomd.socket: Failed with result 'trigger-limit-hit'. This is the systemctl status for systemd-oomd.service and systemd-oomd.socket: # systemctl status systemd-oomd.service ○ systemd-oomd.service - Userspace Out-Of-Memory (OOM) Killer Loaded: loaded (/lib/systemd/system/systemd-oomd.service; enabled; preset: enabled) Active: inactive (dead) TriggeredBy: × systemd-oomd.socket Condition: start condition failed at Thu 2023-04-20 23:21:07 CEST; 9h ago └─ ConditionControlGroupController=memory was not met Docs: man:systemd-oomd.service(8) # systemctl status systemd-oomd.socket × systemd-oomd.socket - Userspace Out-Of-Memory (OOM) Killer Socket Loaded: loaded (/lib/systemd/system/systemd-oomd.socket; enabled; preset: enabled) Active: failed (Result: trigger-limit-hit) since Thu 2023-04-20 23:21:07 CEST; 9h ago Duration: 2min 2.252s Triggers: ● systemd-oomd.service Docs: man:systemd-oomd.service(8) Listen: /run/systemd/oom/io.system.ManagedOOM (Stream) ADITIONAL INFO: --- Machine is an arm64 "Raspberry Pi 4 Model B Rev 1.4 8GB" # uname -a Linux fpgrpi 6.2.0-1004-raspi #5-Ubuntu SMP PREEMPT Mon Apr 3 11:15:14 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux # lsb_release -rd No LSB modules are available. Description:Ubuntu 23.04 Release:23.04 # apt-cache policy systemd-oomd systemd-oomd: Instalados: 252.5-2ubuntu3 Candidato: 252.5-2ubuntu3 Tabla de versión: *** 252.5-2ubuntu3 500 500 http://ports.ubuntu.com/ubuntu-ports lunar/main arm64 Packages 100 /var/lib/dpkg/status ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: lunar systemd-oomd systemd-oomd.service systemd-oomd.socket -- 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/2017209 Title: systemd-oomd fails with "ConditionControlGroupController=memory was not met" Status in systemd package in Ubuntu: New Bug description: PROBLEM SUMMARY: Just upgraded to Ubuntu 23.04 (lunar) from Ubuntu 22.10 (kinetic). systemd-oomd fails with "ConditionControlGroupController=memory was not met" during boot. If you manually started it after boot it starts but after a few minutes it fails with the same error. These are the journalctl entries regarding this problem: abr 20 23:12:48 fpgrpi systemd[1]: Listening on systemd-oomd.socket - Userspace Out-Of-Memory (OOM) Killer Socket. abr 20 23:12:48 fpgrpi systemd[1]: systemd-oomd.service - Userspace Out-Of-Memory (OOM) Killer was skipped because of an unmet condition check (ConditionControlGroupController=memory). --- Line repeat 20 times --- abr 20 23:12:49 fpgrpi systemd[1]: systemd-oomd.service - Userspace Out-Of-Memory (OOM) Killer was skipped because of an unmet condition check (ConditionControlGroupController=memory). abr 20 23:12:49 fpgrpi systemd[1]: systemd-oomd.socket: Trigger limit hit, refusing further activation. abr 20 23:12:49 fpgrpi systemd[1]: systemd-oomd.socket: Failed with result 'trigger-limit-hit'. This is the systemctl status for systemd-oomd.service and systemd-oomd.socket: # systemctl status systemd-oomd.service ○ systemd-oomd.service - Userspace Out-Of-Memory (OOM) Killer Loaded: loaded (/lib/systemd/system/systemd-oomd.service; enabled; preset: enabled) Active: inactive (dead) TriggeredBy: × systemd-oomd.socket Condition: start condition failed at Thu 2023-04-20 23:21:07 CEST; 9h ago └─ ConditionControlGroupController=memory was not met Docs: man:systemd-oomd.service(8) # systemctl status systemd-oomd.socket × systemd-oomd.socket - Userspace Out-Of-Memory (OOM) Killer Socket Loaded: loaded (/lib/systemd/system/systemd-oomd.socket; enabled; preset: enabled) Active: failed