[Touch-packages] [Bug 2047388] Re: System reboots automatically when lock screen screen enabled.
Only the kernel can crash that hard, so reassigning there. ** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (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/2047388 Title: System reboots automatically when lock screen screen enabled. Status in linux-hwe-6.2 package in Ubuntu: New Bug description: System reboots automatically when lock screen screen enabled. The same is tested on ubuntu-20.04 as well as ubuntu-22.04. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 26 11:42:52 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-S GT2 [UHD Graphics 630] [8086:3e92] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company CometLake-S GT2 [UHD Graphics 630] [103c:85a2] InstallationDate: Installed on 2023-12-07 (19 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: HP HP ProOne 400 G5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=3a72d508-3f06-4b45-a814-8d4bef8b43d0 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2021 dmi.bios.release: 9.0 dmi.bios.vendor: HP dmi.bios.version: R12 Ver. 02.09.00 dmi.board.name: 85A2 dmi.board.vendor: HP dmi.board.version: KBC Version 08.98.00 dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.ec.firmware.release: 8.152 dmi.modalias: dmi:bvnHP:bvrR12Ver.02.09.00:bd04/21/2021:br9.0:efr8.152:svnHP:pnHPProOne400G5:pvr:rvnHP:rn85A2:rvrKBCVersion08.98.00:cvnHP:ct13:cvr:sku6AE46AV: dmi.product.family: 103C_53307F HP ProOne dmi.product.name: HP ProOne 400 G5 dmi.product.sku: 6AE46AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2047388/+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 2047511] Re: [Lenovo IdeaPad Z500] Screen brightness
** Summary changed: - Screen brightness + [Lenovo IdeaPad Z500] Screen brightness ** Summary changed: - [Lenovo IdeaPad Z500] Screen brightness + [Lenovo IdeaPad Z500] Brightness of the screen is down to minimum and I can't change it ** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (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/2047511 Title: [Lenovo IdeaPad Z500] Brightness of the screen is down to minimum and I can't change it Status in linux-hwe-6.2 package in Ubuntu: New Bug description: Ubuntu 22.04.3 LTS Release: 22.04 Brightness of the screen is down to minimum and I can't change it. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-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.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 27 11:15:19 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3904] NVIDIA Corporation GK107M [GeForce GT 645M] [10de:0fd9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GK107M [GeForce GT 645M] [17aa:3904] InstallationDate: Installed on 2023-12-10 (16 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: LENOVO 20202 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-39-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2012 dmi.bios.release: 0.49 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN31WW(V1.10) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvr71CN31WW(V1.10):bd11/16/2012:br0.49:efr1.49:svnLENOVO:pn20202:pvrLenovoIdeaPadZ500:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500:skuLENOVO_MT_20202: dmi.product.family: IDEAPAD dmi.product.name: 20202 dmi.product.sku: LENOVO_MT_20202 dmi.product.version: Lenovo IdeaPad Z500 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2047511/+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 2047154] Re: [drm] *ERROR* flip_done timed out
** Tags added: amdgpu ** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (Ubuntu) ** Summary changed: - [drm] *ERROR* flip_done timed out + [amdgpu][drm] *ERROR* flip_done timed out -- 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/2047154 Title: [amdgpu][drm] *ERROR* flip_done timed out Status in linux-hwe-6.2 package in Ubuntu: New Bug description: amdgpu :0c:00.0: [drm] *ERROR* flip_done timed out gru 21 16:32:25 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* [CRTC:84:crtc-0] commit wait timed out gru 21 16:32:36 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* flip_done timed out gru 21 16:32:36 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* [CONNECTOR:119:HDMI-A-1] commit wait timed out gru 21 16:32:40 karol.home.prv dbus-daemon[1317]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=2> gru 21 16:32:46 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* flip_done timed out gru 21 16:32:46 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* [PLANE:67:plane-5] commit wait timed out gru 21 16:32:46 karol.home.prv kernel: [ cut here ] gru 21 16:32:46 karol.home.prv kernel: WARNING: CPU: 3 PID: 100858 at /var/lib/dkms/amdgpu/6.2.4-1664922.22.04/build/amd/amdgpu/../di> gru 21 16:32:46 karol.home.prv kernel: Modules linked in: xt_recent tls xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_i> gru 21 16:32:46 karol.home.prv kernel: reed_solomon pstore_zone efi_pstore sunrpc ip_tables x_tables autofs4 ib_uverbs ib_core amdgp> gru 21 16:32:46 karol.home.prv kernel: CPU: 3 PID: 100858 Comm: Xorg Tainted: PW OE 6.2.0-26-generic #26~22.04.1-Ubuntu gru 21 16:32:46 karol.home.prv kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X470 Master SLI, BIOS P4.40 03/29> gru 21 16:32:46 karol.home.prv kernel: RIP: 0010:amdgpu_dm_atomic_commit_tail+0x3b20/0x4200 [amdgpu] gru 21 16:32:46 karol.home.prv kernel: Code: ff 4c 89 9d 78 fc ff ff ba 01 00 00 00 31 f6 4c 89 95 80 fc ff ff 41 b9 01 00 00 00 50 5> gru 21 16:32:46 karol.home.prv kernel: RSP: 0018:b5fb50ee7818 EFLAGS: 00010002 gru 21 16:32:46 karol.home.prv kernel: RAX: 0246 RBX: 00013195 RCX: gru 21 16:32:46 karol.home.prv kernel: RDX: RSI: RDI: gru 21 16:32:46 karol.home.prv kernel: RBP: b5fb50ee7ba0 R08: R09: gru 21 16:32:46 karol.home.prv kernel: R10: 0002 R11: R12: 0246 gru 21 16:32:46 karol.home.prv kernel: R13: R14: 9710a5d8d118 R15: 9710a5d8d000 gru 21 16:32:46 karol.home.prv kernel: FS: 7f3267b4ea80() GS:97179eac() knlGS: gru 21 16:32:46 karol.home.prv kernel: CS: 0010 DS: ES: CR0: 80050033 gru 21 16:32:46 karol.home.prv kernel: CR2: 55ef7d6bfb20 CR3: 000250f4e000 CR4: 003506e0 gru 21 16:32:46 karol.home.prv kernel: Call Trace: gru 21 16:32:46 karol.home.prv kernel: gru 21 16:32:46 karol.home.prv kernel: commit_tail+0xc5/0x1a0 [drm_kms_helper] gru 21 16:32:46 karol.home.prv kernel: ? drm_atomic_helper_swap_state+0x246/0x380 [drm_kms_helper] gru 21 16:32:46 karol.home.prv kernel: drm_atomic_helper_commit+0x137/0x160 [drm_kms_helper] gru 21 16:32:46 karol.home.prv kernel: drm_atomic_commit+0x99/0xd0 [drm] gru 21 16:32:46 karol.home.prv kernel: ? __pfx___drm_printfn_info+0x10/0x10 [drm] gru 21 16:32:46 karol.home.prv kernel: drm_mode_obj_set_property_ioctl+0x179/0x430 [drm] gru 21 16:32:46 karol.home.prv kernel: ? drm_mode_createblob_ioctl+0xff/0x130 [drm] gru 21 16:32:46 karol.home.prv kernel: ? __pfx_drm_mode_obj_set_property_ioctl+0x10/0x10 [drm] gru 21 16:32:46 karol.home.prv kernel: drm_ioctl_kernel+0xc3/0x160 [drm] gru 21 16:32:46 karol.home.prv kernel: drm_ioctl+0x27b/0x4c0 [drm] gru 21 16:32:46 karol.home.prv kernel: ? __pfx_drm_mode_obj_set_property_ioctl+0x10/0x10 [drm] gru 21 16:32:46 karol.home.prv kernel: ? __pm_runtime_suspend+0x7b/0x110 gru 21 16:32:46 karol.home.prv kernel: amdgpu_drm_ioctl+0x4e/0x90 [amdgpu] gru 21 16:32:46 karol.home.prv kernel: __x64_sys_ioctl+0x9d/0xe0 gru 21 16:32:46 karol.home.prv kernel: do_syscall_64+0x5c/0x90 gru 21 16:32:46 karol.home.prv kernel: ? do_syscall_64+0x69/0x90 gru 21 16:32:46 karol.home.prv kernel: ? exit_to_user_mode_prepare+0x3b/0xd0 gru 21 16:32:46 karol.home.prv kernel: ? syscall_exit_to_user_mode+0x2a/0x50 ? do_syscall_64+0x69/0x90 gru 21 16:32:46 karol.home.prv kernel: entry_SYSCALL_64_after_hwframe+0x72/0xdc gru 21 16:32:46 karol.home.prv kernel: RIP: 0033:0x7f3267f1a75f gru 21 16:32:46 karol.home.prv kernel: Code: 00 48 89
[Touch-packages] [Bug 2047144] Re: Black screen stays forever after inactivity
Do you have an external monitor plugged in when the bug occurs? ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Tags added: hybrid i915 multigpu nvidia -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2047144 Title: Black screen stays forever after inactivity Status in mutter package in Ubuntu: Incomplete Bug description: IMPORTANT this only happens with WAYLAND but i couldn't choose wayland in the bug report options. On my Ubuntu 22.04.03 I have set the time for my screen to go black/shut off in case of inactivity in the energy settings (to save energy) to 5 minutes. So I go back to my computer after 10 minutes or so and the screen is black like it should be. Problem is, that I can't turn the screen on or what I really mean is: get back to the desktop. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.129.03 Thu Oct 19 18:56:32 UTC 2023 GCC version: ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 21 13:08:29 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] CoffeeLake-H GT2 [UHD Graphics 630] [1462:120f] NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c20] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106M [GeForce GTX 1060 Mobile] [1462:120f] InstallationDate: Installed on 2023-10-22 (59 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1038:1122 SteelSeries ApS SteelSeries KLC Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd. GS73 Stealth 8RE ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=e4b68fb9-8f19-4768-9b90-c84e28ec65ef ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2019 dmi.bios.release: 1.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17B5IMS.110 dmi.board.asset.tag: Default string dmi.board.name: MS-17B5 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE17B5IMS.110:bd05/17/2019:br1.16:svnMicro-StarInternationalCo.,Ltd.:pnGS73Stealth8RE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17B5:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17B5.1: dmi.product.family: GS dmi.product.name: GS73 Stealth 8RE dmi.product.sku: 17B5.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to:
[Touch-packages] [Bug 2046802] Re: External display stay blank when connected through the docking station (HP USB-C Dock G5) but is OK when directly connected
Indeed the kernel seems to be crashing in drm graphics code so I'd
recommend trying some newer kernels such as
https://kernel.ubuntu.com/mainline/?C=M;O=D
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Tags added: amdgpu dock multimonitor
--
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/2046802
Title:
External display stay blank when connected through the docking station
(HP USB-C Dock G5) but is OK when directly connected
Status in linux package in Ubuntu:
New
Bug description:
External display is detected and X believes it is OK as the desktop
correctly extends to the 2nd monitor but said monitor remains blank.
It used to work a couple of days ago but I guess some upgrade is the
cause. I tried to downgrade amd64-microcode and linux-firmware, to no
avail : dmesg still shows issues with drivers.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: XFCE
Date: Mon Dec 18 12:14:54 2023
DistUpgraded: 2023-12-18 10:58:52,052 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Barcelo [1002:15e7] (rev c5) (prog-if
00 [VGA controller])
Subsystem: Hewlett-Packard Company Barcelo [103c:8b5c]
InstallationDate: Installed on 2023-08-08 (132 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=d29d3432-7c6f-4376-a050-c86365d7b922 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-12-18 (0 days ago)
dmi.bios.date: 04/25/2023
dmi.bios.release: 2.1
dmi.bios.vendor: HP
dmi.bios.version: V78 Ver. 01.02.01
dmi.board.name: 8B5C
dmi.board.vendor: HP
dmi.board.version: KBC Version 53.1D.00
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 83.29
dmi.modalias:
dmi:bvnHP:bvrV78Ver.01.02.01:bd04/25/2023:br2.1:efr83.29:svnHP:pnHPProBook44514inchG10NotebookPC:pvr:rvnHP:rn8B5C:rvrKBCVersion53.1D.00:cvnHP:ct10:cvr:sku852U8ES#UUZ:
dmi.product.family: 103C_5336AN HP ProBook
dmi.product.name: HP ProBook 445 14 inch G10 Notebook PC
dmi.product.sku: 852U8ES#UUZ
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/linux/+bug/2046802/+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 2047314] Re: tzdata 2023d release (leap-second.list expiring this week)
This bug was fixed in the package tzdata - 2023d-1ubuntu1 --- tzdata (2023d-1ubuntu1) noble; urgency=medium * Merge with Debian unstable. Remaining changes: - Ship 2023c ICU timezone data which are utilized by PHP in tzdata-icu - Add autopkgtest test case for ICU timezone data - Do not rename NEWS into changelog.gz, this fixes a build failure on moment-timezone.js - Point Vcs-Browser/Git to Launchpad - generate_debconf_templates: Work around AttributeError on icu import * No ICU data update yet as none is yet available upstream. tzdata (2023d-1) unstable; urgency=medium * New upstream version (LP: #2047314): - Ittoqqortoormiit, Greenland changes time zones on 2024-03-31. - Vostok, Antarctica changed time zones on 2023-12-18. - Casey, Antarctica changed time zones five times since 2020. - Code and data fixes for Palestine timestamps starting in 2072. - A new data file zonenow.tab for timestamps starting now. * Install zonenow.tab in tzdata * Add autopkgtest test case for 2023d release * Document tzdata-legacy split in NEWS.Debian (Closes: #1051973, #1056908) tzdata (2023c-11) unstable; urgency=medium * Update Swedish debconf translation. Thanks to Martin Bagge / brother (Closes: #1054616) * Update leap-seconds.list from upstream * Remove leapseconds during clean target -- Benjamin Drung Tue, 02 Jan 2024 15:24:25 +0100 ** Changed in: tzdata (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2047314 Title: tzdata 2023d release (leap-second.list expiring this week) Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Lunar: New Status in tzdata source package in Mantic: New Bug description: [ Impact ] leap-seconds.list shipped by tzdata 2023c expired on Dec 28th 2023. The 2023d release contains the following changes: Briefly: Ittoqqortoormiit, Greenland changes time zones on 2024-03-31. Vostok, Antarctica changed time zones on 2023-12-18. Casey, Antarctica changed time zones five times since 2020. Code and data fixes for Palestine timestamps starting in 2072. A new data file zonenow.tab for timestamps starting now. Changes to future timestamps Ittoqqortoormiit, Greenland (America/Scoresbysund) joins most of the rest of Greenland's timekeeping practice on 2024-03-31, by changing its time zone from -01/+00 to -02/-01 at the same moment as the spring-forward transition. Its clocks will therefore not spring forward as previously scheduled. The time zone change reverts to its common practice before 1981. Fix predictions for DST transitions in Palestine in 2072-2075, correcting a typo introduced in 2023a. Changes to past and future timestamps Vostok, Antarctica changed to +05 on 2023-12-18. It had been at +07 (not +06) for years. (Thanks to Zakhary V. Akulov.) Change data for Casey, Antarctica to agree with timeanddate.com, by adding five time zone changes since 2020. Casey is now at +08 instead of +11. Changes to past tm_isdst flags Much of Greenland, represented by America/Nuuk, changed its standard time from -03 to -02 on 2023-03-25, not on 2023-10-28. This does not affect UTC offsets, only the tm_isdst flag. (Thanks to Thomas M. Steenholdt.) New data file A new data file zonenow.tab helps configure applications that use timestamps dated from now on. This simplifies configuration, since users choose from a smaller Zone set. The file's format is experimental and subject to change. [ Test Plan ] Test cases were added to autopkgtest to cover the testing: * python: test_2023d So the test plan is to check that all autopkgtest succeeds. [ Other Info ] The autopkgtest for chrony is flaky on jammy and newer (see bug #2002910). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2047314/+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 2047705] Re: Packaging ships /etc/gtk-3.0/settings.ini, forcing the GTK3 theme to Yaru and preventing flavors from overriding it with XDG configuration
A bug still exists here. GTK as a standalone package should not set Yaru as a default, especially if it doesn't declare it as a dependency. lxqt-session was simply a workaround. The Ubuntu Desktop Team needs to move this to their default settings package, and adjust GTK to appropriately read $XDG_CONFIG_DIRS for the appropriate configuration. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2047705 Title: Packaging ships /etc/gtk-3.0/settings.ini, forcing the GTK3 theme to Yaru and preventing flavors from overriding it with XDG configuration Status in gtk+3.0 package in Ubuntu: Confirmed Status in lxqt-session package in Ubuntu: Fix Released Bug description: Lubuntu uses Qt as the primary framework for most of the apps we ship. However, some functionality we ship in Lubuntu doesn't have a Qt application that provides that functionality, so we have some GTK3 apps that we ship as well. Starting in Lubuntu 24.04, we are adding and enabling the breeze-gtk-theme package, providing more uniform theming between Qt and GTK apps on Lubuntu. However, this bug makes this impossible. As we do not ship xsettingsd, but instead use the XDG specification for shipping configuration, we are attempting to place the default configuration files for GTK2 and GTK3 theming in /etc/xdg/xdg- Lubuntu/gtk-2.0/gtkrc and /etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini. This solutions works for GTK2 apps, however GTK3 apps silently ignore the vendored configuration file and are using a different theme. As it turns out, this is because the /etc directory is given higher priority than /etc/xdg/xdg-Lubuntu when searching for XDG configuration files, and as it happens, libgtk-3-0 ships a /etc/gtk-3.0/settings.ini file that sets Yaru as the default theme. GTK3 applications end up selecting this configuration file rather than /etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini. /etc/gtk-3.0 is, I would argue, *not* a place where GTK3's settings.ini file should go, as it makes it difficult for flavors who rely on XDG configuration to override it without risking a file conflict. (Technically I guess a flavor package *could* use dpkg- divert to simply "get rid of" the /etc/gtk-3.0/settings.ini file, but that seems like the wrong way to approach this.) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libgtk-3-0 3.24.38-5ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Fri Dec 29 10:08:23 2023 InstallationDate: Installed on 2023-10-22 (69 days ago) InstallationMedia: Lubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2047705/+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 1964506] Update Released
The verification of the Stable Release Update for iputils has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1964506 Title: Ping: checks payloads incorrectly, ignores all mismatch replies Status in iputils package in Ubuntu: Fix Released Status in iputils source package in Focal: Fix Committed Bug description: = Impact = the ping statistics are incorrect when dealing with truncated packets = Test case = $ ping -c 1 -s 1200 8.8.8.8 should list truncated replies and received packets = Regression potential = the changes are limited to the ping source any regression would impact that utility, check that responses are correctly handled and statistics reflecting what is expected -- Problematic commit reverted upstream causing incorrect behavior in Ubuntu Focal. Discussion: https://github.com/iputils/iputils/issues/320 Fix: https://github.com/iputils/iputils/pull/321 Release: https://github.com/iputils/iputils/releases/tag/20210722 Could this patch be added for a Focal update please? 1) Ubuntu 20.04.3 LTS 2) 3:20190709-3 3) focal$ ping -c 1 -s 1200 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data. --- 8.8.8.8 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms 4) xenial$ ping -c 1 -s 1200 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data. 76 bytes from 8.8.8.8: icmp_seq=1 ttl=61 (truncated) --- 8.8.8.8 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.284/0.284/0.284/0.000 ms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1964506/+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 2046627] Re: Xorg freeze
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.
2. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.
3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.
Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
** Summary changed:
- Xorg freeze
+ System reeze
** Summary changed:
- System reeze
+ System freeze
--
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/2046627
Title:
System freeze
Status in Ubuntu:
Incomplete
Bug description:
My Dell XPS 15 has a touchscreen. If I use the touchscreen, at some
point the computer will completely lock up.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Dec 16 14:05:39 2023
DistUpgraded: 2023-11-08 08:37:56,248 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if
00 [VGA controller])
Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:0905]
Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:0905]
InstallationDate: Installed on 2022-02-15 (669 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=eed7bf21-88c9-44aa-a905-ee4a5ccc7e4d ro quiet splash loglevel=3
vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to mantic on 2023-11-08 (38 days ago)
dmi.bios.date: 09/11/2023
dmi.bios.release: 1.24
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.24.0
dmi.board.name: 018W12
dmi.board.vendor: Dell Inc.
dmi.board.version: A06
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.24.0:bd09/11/2023:br1.24:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn018W12:rvrA06:cvnDellInc.:ct10:cvr:sku0905:
dmi.product.family: XPS
dmi.product.name: XPS 15 7590
dmi.product.sku: 0905
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/+bug/2046627/+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 2046553] Re: i am unable to pair and connect bluetooth
Please check that you have Bluetooth enabled because this shows it is disabled in software: 2: dell-bluetooth: Bluetooth Soft blocked: yes Hard blocked: no Also is this a new problem since the last software update? ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- 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/2046553 Title: i am unable to pair and connect bluetooth Status in bluez package in Ubuntu: Incomplete Bug description: sudo apt-get install fwupd sudo fwupdmgr update Reading package lists... Done Building dependency tree... Done Reading state information... Done fwupd is already the newest version (1.7.9-1~22.04.3). fwupd set to manually installed. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Devices with no available firmware updates i have configered also but no problem found Type: Primary Bus: USB BD Address: 34:41:5D:32:F1:53 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:19216 acl:0 sco:0 events:2629 errors:0 TX bytes:603774 acl:0 sco:0 commands:2570 errors:0 please fix this ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1.1 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Dec 15 18:29:38 2023 InstallationDate: Installed on 2023-08-31 (106 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:58ca Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 002: ID 1ea7:0064 SHARKOON Technologies GmbH 2.4GHz Wireless rechargeable vertical mouse [More] Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7490 ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=3e546dec-b6ab-4cff-9ae6-19d09ccec9e4 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2023 dmi.bios.release: 1.33 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.33.0 dmi.board.name: 0KP0FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.33.0:bd07/06/2023:br1.33:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr:sku081C: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.product.sku: 081C dmi.sys.vendor: Dell Inc. hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2046553/+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 2046485] Re: intel 3000 hd graphics not working
Please don't use xserver-xorg-video-intel because it's buggy and
deprecated. The default Xorg driver ('modesetting') is the correct
driver.
I will make this bug about the screen being too bright. If you want to
discuss "3rd class video quality" then please open a new bug for that...
** Summary changed:
- intel 3000 hd graphics not working
+ [HP Pavilion dv6] Screen is too bright
--
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/2046485
Title:
[HP Pavilion dv6] Screen is too bright
Status in linux package in Ubuntu:
Incomplete
Bug description:
when i try this command
sudo apt-get install xserver-xorg-video-intel
i get this
xserver-xorg-video-intel is already the newest version
(2:2.99.917+git20210115-1).
i have intel 3000 hd graphics built-in in my laptop.
but my screen is too bright and i am getting 3rd class video quality
in youtube in browser, i checked videos in 720p, 1080p, but same
issue.
when i check some videos in my laptop, that are in good quality
downloaded from internet. issue is same.
i have no issue in windows 7, 10.
but only i have issue is in Linux mint, and Lubuntu
Lubuntu 22.04 LTS
Lubuntu 22.04.3 LTS JAMMY JELLYFISH RELEASE AMD 20230807
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
Uname: Linux 6.2.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5json:
{
"result": "skip"
}
CasperVersion: 1.470.2
CompositorRunning: None
CurrentDesktop: LXQt
Date: Thu Dec 14 23:55:58 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation 2nd Generation Core Processor Family Integrated Graphics
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family
Integrated Graphics Controller [103c:1658]
LiveMediaBuild: Lubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807)
MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
ProcKernelCmdLine: fsck.mode=skip noprompt boot=casper
floppy.allowed_drive_mask=0 ignore_uuid --
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/05/2011
dmi.bios.release: 15.27
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.1B
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1658
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 10.31
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 16.49
dmi.modalias:
dmi:bvnHewlett-Packard:bvrF.1B:bd10/05/2011:br15.27:efr16.49:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058C11244720001620100:rvnHewlett-Packard:rn1658:rvr10.31:cvnHewlett-Packard:ct10:cvrChassisVersion:skuA3X35UA#ABA:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
dmi.product.name: HP Pavilion dv6 Notebook PC
dmi.product.sku: A3X35UA#ABA
dmi.product.version: 058C11244720001620100
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046485/+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 2046485] Re: [HP Pavilion dv6] Screen is too bright
Does "screen is too bright" mean the backlight brightness can't be
adjusted?
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2046485
Title:
[HP Pavilion dv6] Screen is too bright
Status in linux package in Ubuntu:
Incomplete
Bug description:
when i try this command
sudo apt-get install xserver-xorg-video-intel
i get this
xserver-xorg-video-intel is already the newest version
(2:2.99.917+git20210115-1).
i have intel 3000 hd graphics built-in in my laptop.
but my screen is too bright and i am getting 3rd class video quality
in youtube in browser, i checked videos in 720p, 1080p, but same
issue.
when i check some videos in my laptop, that are in good quality
downloaded from internet. issue is same.
i have no issue in windows 7, 10.
but only i have issue is in Linux mint, and Lubuntu
Lubuntu 22.04 LTS
Lubuntu 22.04.3 LTS JAMMY JELLYFISH RELEASE AMD 20230807
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
Uname: Linux 6.2.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5json:
{
"result": "skip"
}
CasperVersion: 1.470.2
CompositorRunning: None
CurrentDesktop: LXQt
Date: Thu Dec 14 23:55:58 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation 2nd Generation Core Processor Family Integrated Graphics
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family
Integrated Graphics Controller [103c:1658]
LiveMediaBuild: Lubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807)
MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
ProcKernelCmdLine: fsck.mode=skip noprompt boot=casper
floppy.allowed_drive_mask=0 ignore_uuid --
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/05/2011
dmi.bios.release: 15.27
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.1B
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1658
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 10.31
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 16.49
dmi.modalias:
dmi:bvnHewlett-Packard:bvrF.1B:bd10/05/2011:br15.27:efr16.49:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058C11244720001620100:rvnHewlett-Packard:rn1658:rvr10.31:cvnHewlett-Packard:ct10:cvrChassisVersion:skuA3X35UA#ABA:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
dmi.product.name: HP Pavilion dv6 Notebook PC
dmi.product.sku: A3X35UA#ABA
dmi.product.version: 058C11244720001620100
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046485/+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 2046553] Re: i am unable to pair and connect bluetooth
** Summary changed: - i am unable to pair and connect blutoothsudo apt-get install fwupd sudo fwupdmgr update Reading package lists... Done Building dependency tree... Done Reading state information... Done fwupd is already the newest version (1.7.9-1~22.04.3). fwupd set to manually installed. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Devices with no available firmware updates ** i have done this no updatws found but i am unable to connect bt devices such as earbud + i am unable to pair and connect bluetooth -- 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/2046553 Title: i am unable to pair and connect bluetooth Status in bluez package in Ubuntu: New Bug description: sudo apt-get install fwupd sudo fwupdmgr update Reading package lists... Done Building dependency tree... Done Reading state information... Done fwupd is already the newest version (1.7.9-1~22.04.3). fwupd set to manually installed. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Devices with no available firmware updates i have configered also but no problem found Type: Primary Bus: USB BD Address: 34:41:5D:32:F1:53 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:19216 acl:0 sco:0 events:2629 errors:0 TX bytes:603774 acl:0 sco:0 commands:2570 errors:0 please fix this ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1.1 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Dec 15 18:29:38 2023 InstallationDate: Installed on 2023-08-31 (106 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:58ca Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 002: ID 1ea7:0064 SHARKOON Technologies GmbH 2.4GHz Wireless rechargeable vertical mouse [More] Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7490 ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=3e546dec-b6ab-4cff-9ae6-19d09ccec9e4 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2023 dmi.bios.release: 1.33 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.33.0 dmi.board.name: 0KP0FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.33.0:bd07/06/2023:br1.33:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr:sku081C: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.product.sku: 081C dmi.sys.vendor: Dell Inc. hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2046553/+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 2046224] Re: Resolutions lower than max results in corrupted screen
On laptop screens, non-max resolutions are faked. They should work
obviously, but it's up to the display server and kernel driver to fake
it properly.
Do you experience the same issue in a Wayland session?
** Tags added: amdgpu
** Summary changed:
- Resolutions lower than max results in corrupted screen
+ [amdgpu] Resolutions lower than max results in corrupted screen
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2046224
Title:
[amdgpu] Resolutions lower than max results in corrupted screen
Status in linux package in Ubuntu:
New
Status in xorg-server package in Ubuntu:
New
Bug description:
Upgrading from 23.04 to 23.10 resulted in corrupt screen when
switching to lower resolutions. Only maximum resolution works.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: MATE
Date: Tue Dec 12 01:21:01 2023
DistUpgraded: 2023-12-10 13:34:46,170 DEBUG icon theme changed, re-reading
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev c2)
(prog-if 00 [VGA controller])
Subsystem: Lenovo Phoenix [17aa:3c92]
InstallationDate: Installed on 2023-11-04 (38 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=2a5d61f3-134e-404f-bc44-06c827cf55f6 ro quiet splash
amd_pstate=guided vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-12-10 (1 days ago)
dmi.bios.date: 06/16/2023
dmi.bios.release: 1.34
dmi.bios.vendor: LENOVO
dmi.bios.version: M3CN34WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76463 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion Slim 5 16APH8
dmi.ec.firmware.release: 1.34
dmi.modalias:
dmi:bvnLENOVO:bvrM3CN34WW:bd06/16/2023:br1.34:efr1.34:svnLENOVO:pn82Y9:pvrLegionSlim516APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrLegionSlim516APH8:skuLENOVO_MT_82Y9_BU_idea_FM_LegionSlim516APH8:
dmi.product.family: Legion Slim 5 16APH8
dmi.product.name: 82Y9
dmi.product.sku: LENOVO_MT_82Y9_BU_idea_FM_Legion Slim 5 16APH8
dmi.product.version: Legion Slim 5 16APH8
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
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/linux/+bug/2046224/+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 2047875] [NEW] package libasound2-plugins 1.2.7.1-1ubuntu1 failed to install/upgrade: trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is d
Public bug reported: amd64 installing wine fails ProblemType: Package DistroRelease: Ubuntu 23.04 Package: libasound2-plugins 1.2.7.1-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-39.40-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Jan 2 20:59:47 2024 ErrorMessage: trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from other instances of package libasound2-plugins:amd64 InstallationDate: Installed on 2023-07-24 (163 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0ubuntu0.1 SourcePackage: alsa-plugins Title: package libasound2-plugins 1.2.7.1-1ubuntu1 failed to install/upgrade: trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from other instances of package libasound2-plugins:amd64 UpgradeStatus: Upgraded to lunar on 2024-01-03 (0 days ago) ** Affects: alsa-plugins (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-plugins in Ubuntu. https://bugs.launchpad.net/bugs/2047875 Title: package libasound2-plugins 1.2.7.1-1ubuntu1 failed to install/upgrade: trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio- default.conf.example', which is different from other instances of package libasound2-plugins:amd64 Status in alsa-plugins package in Ubuntu: New Bug description: amd64 installing wine fails ProblemType: Package DistroRelease: Ubuntu 23.04 Package: libasound2-plugins 1.2.7.1-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-39.40-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Jan 2 20:59:47 2024 ErrorMessage: trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from other instances of package libasound2-plugins:amd64 InstallationDate: Installed on 2023-07-24 (163 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0ubuntu0.1 SourcePackage: alsa-plugins Title: package libasound2-plugins 1.2.7.1-1ubuntu1 failed to install/upgrade: trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from other instances of package libasound2-plugins:amd64 UpgradeStatus: Upgraded to lunar on 2024-01-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/2047875/+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 2046116] Re: bluetooth device connected but not recognised as output device
** Tags added: regression-security -- 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/2046116 Title: bluetooth device connected but not recognised as output device Status in bluez package in Ubuntu: New Bug description: bluetooth device connected but not recognised as output device ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Dec 11 15:28:00 2023 InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 81EK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic root=UUID=6f698382-a806-46af-9a4b-472e96795c6f ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2018 dmi.bios.release: 1.28 dmi.bios.vendor: LENOVO dmi.bios.version: 7QCN28WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 530-14IKB dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvr7QCN28WW:bd08/02/2018:br1.28:efr1.28:svnLENOVO:pn81EK:pvrLenovoYOGA530-14IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA530-14IKB:skuLENOVO_MT_81EK_BU_idea_FM_YOGA530-14IKB: dmi.product.family: YOGA 530-14IKB dmi.product.name: 81EK dmi.product.sku: LENOVO_MT_81EK_BU_idea_FM_YOGA 530-14IKB dmi.product.version: Lenovo YOGA 530-14IKB dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 0C:54:15:91:FA:4F ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:83770 acl:295 sco:0 events:4208 errors:0 TX bytes:879445 acl:1667 sco:0 commands:1184 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2046116/+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 2040386] Re: Merge krb5 from Debian unstable for noble
This is a sync at the moment. ** Changed in: krb5 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/2040386 Title: Merge krb5 from Debian unstable for noble Status in krb5 package in Ubuntu: Incomplete Bug description: Upstream: tbd Debian: 1.20.1-5 Ubuntu: 1.20.1-3ubuntu1 Debian does new releases regularly, so it's likely there will be newer versions available before FF that we can pick up if this merge is done later in the cycle. If it turns out this needs a sync rather than a merge, please change the tag 'needs-merge' to 'needs-sync', and (optionally) update the title as desired. ### New Debian Changes ### krb5 (1.20.1-5) unstable; urgency=medium [ Helmut Grohne ] * Annotate test dependencies . (Closes: #1054461) [ Sam Hartman ] * Fix keyutils to be linux-any -- Helmut Grohne Tue, 24 Oct 2023 07:17:27 +0200 krb5 (1.20.1-4) unstable; urgency=low [ Steve Langasek ] * libkrb5support0: require strict binary dependency to deal with glibc 2.38, Closes: #1043184 [Jelmer Vernooij] * krb5-user: Use alternatives for kinit, klist, kswitch, ksu, kpasswd, kdestroy, kadmin and ktutil. This allows installation together with heimdal-clients. Closes: #213316, #751203 [ Sam Hartman ] * Enable build-time tests, Thanks Andreas Hasenack, Closes: #1017763 * Work around doxygen change that breaks doc build, Thanks Greg Hudson, Closes: #1051523 -- Sam Hartman Mon, 11 Sep 2023 11:06:57 -0600 krb5 (1.20.1-3) unstable; urgency=high * Fixes CVE-2023-36054: a remote authenticated attacker can cause kadmind to free an uninitialized pointer. Upstream believes remote code execusion is unlikely, Closes: #1043431 -- Sam Hartman Mon, 14 Aug 2023 14:06:53 -0600 krb5 (1.20.1-2) unstable; urgency=medium * Tighten dependencies on libkrb5support0. This means that the entire upgrade from bullseye to bookworm needs to be lockstep, but it appears that's what is required, Closes: #1036055 -- Sam Hartman Mon, 15 May 2023 17:44:41 -0600 krb5 (1.20.1-1) unstable; urgency=high [ Bastian Germann ] * Sync debian/copyright with NOTICE from upstream [ Debian Janitor ] * Trim trailing whitespace. * Strip unusual field spacing from debian/control. * Use secure URI in Homepage field. * Merge upstream signing key files. * Update renamed lintian tag names in lintian overrides. * Update standards version to 4.6.1, no changes needed. * Remove field Section on binary package krb5-gss-samples that duplicates source. * Fix field name cases in debian/control (VCS-Browser => Vcs-Browser, VCS-Git => Vcs-Git). [ Sam Hartman ] * New upstream release - Integer overflows in PAC parsing; potentially critical for 32-bit KDCs or when cross-realm acts maliciously; DOS in other conditions; CVE-2022-42898, Closes: #1024267 * Tighten version dependencies around crypto library, Closes: 1020424 * krb5-user reccomends rather than Depends on krb5-config. This avoids a hard dependency on bind9-host, but also supports cases where krb5-config is externally managed, Closes: #1005821 -- Sam Hartman Thu, 17 Nov 2022 10:34:28 -0700 krb5 (1.20-1) unstable; urgency=medium * New Upstream Version * Do not specify master key type to avoid weak crypto, Closes: #1009927 -- Sam Hartman Fri, 22 Jul 2022 16:32:38 -0600 krb5 (1.20~beta1-1) experimental; urgency=medium * New Upstream version -- Sam Hartman Thu, 07 Apr 2022 11:57:27 -0600 krb5 (1.19.2-2) unstable; urgency=medium * Standards version 4.6.0; no change * kpropd: run after network.target, Closes: #948820 * krb5-kdc: Remove /var from PidFile, Closes: #982009 -- Sam Hartman Mon, 21 Feb 2022 13:05:20 -0700 krb5 (1.19.2-1) experimental; urgency=medium * New Upstream version * Include patch to work with OpenSSL 3.0, Closes: #995152 * Depend on tex-gyre, Closes: #997407 ### Old Ubuntu Delta ### krb5 (1.20.1-3ubuntu1) mantic; urgency=medium * Make krb5int_strl(cat|copy) optional symbols, since they are not needed when built against glibc 2.38. Closes: #1043184. * Declare Breaks: against older packages using these symbols. * Make dependencies on libkrb5support0 strict to avoid future symbol skew. -- Steve Langasek Thu, 24 Aug 2023 18:07:33 + To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/2040386/+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 2047343] Re: The steam profile in 4.0.0~alpha2-0ubuntu7 does not support steam installed by steam-installer package
The following profile worked for me, if it works for you I will get it
uploaded asap. You can just drop it in a file and do
sudo apparmor_parser -r /path/to/your/file
to test it.
# This profile allows everything and only exists to give the
# application a name instead of having the label "unconfined"
abi ,
include
profile steam /usr/{lib/steam/bin_steam.sh,games/steam} flags=(unconfined) {
userns,
# Site-specific additions and overrides. See local/README for details.
include if exists
}
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2047343
Title:
The steam profile in 4.0.0~alpha2-0ubuntu7 does not support steam
installed by steam-installer package
Status in apparmor package in Ubuntu:
New
Status in steam-installer package in Ubuntu:
New
Bug description:
The steam profile in 4.0.0~alpha2-0ubuntu7 only supports steam
installed from the official website
(https://cdn.cloudflare.steamstatic.com/client/installer/steam.deb),
but does not support the installation by the steam-installer in the
repository.
The new user namespace creation restrictions will prevent steam
installed by steam-installer from running Windows games.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2047343/+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 2046356] Re: Update URL for Support information in MOTD message
This bug was fixed in the package base-files - 13ubuntu6 --- base-files (13ubuntu6) noble; urgency=medium * motd/10-help-text: Update support url for new Ubuntu Pro webpage (LP: #2046356) -- Lucas Moura Tue, 02 Jan 2024 10:25:08 -0300 ** Changed in: base-files (Ubuntu Noble) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/2046356 Title: Update URL for Support information in MOTD message Status in base-files package in Ubuntu: Fix Released Status in base-files source package in Xenial: New Status in base-files source package in Bionic: New Status in base-files source package in Focal: New Status in base-files source package in Jammy: New Status in base-files source package in Mantic: New Status in base-files source package in Noble: Fix Released Bug description: [Impact] When users see the MOTD message, they are currently seeing an outdated url under the support information. Even though the outdated url redirects to new Ubuntu Pro webpage, we believe the users should still see the correct url from the start [Test Case] - Launch a LXD container for any of the affected releases - Install the package with this fix applied - Install `update-motd` package - Run `update-motd` and confirm the Support url is now the correct one [Regression Potential] If users are parsing MOTD for some reason, the url change might break that logic now. However, parsing MOTD messages is not a supported flow, so we believe regression potential is low here. [Discussion] Since we want users to be aware of what Ubuntu Pro is, we should highlight the right product name on any place that is still using the old "advantage" name. Updating the support URL here is a step into this direction [Original Bug Description] On the file 10-help-text, we are printing the following line on MOTD: * Support: https://ubuntu.com/advantage We should update the url to https://ubuntu.com/pro instead, as this will the default url for support information now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2046356/+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 2031186] Re: failed to add/activate wifi connection after netplan intalled_resolved
** Summary changed: - failed to add/activate wifi connection after netplan intalled_unresolved + failed to add/activate wifi connection after netplan intalled_resolved -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libasyncns in Ubuntu. https://bugs.launchpad.net/bugs/2031186 Title: failed to add/activate wifi connection after netplan intalled_resolved Status in libasyncns package in Ubuntu: New Bug description: message recipient disconnected from message bus without replying lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Mantic Minotaur (development branch) Release: 23.10 Codename: mantic hi libasyncns0:amd64 0.8-6build3 amd64Asynchronous name service query library hi libasyncns0:i386 0.8-6build3 i386 Asynchronous name service query library Expected wifi connection as anticipated with 0.8-6build2. Wifi connection failure notice when selecting network connection after update to 0.8-6build3. Restore from backup with system upgrade excluding above problem packages does not produce wifi connection problem. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: libasyncns0 0.8-6build2 Uname: Linux 6.5.0-rc1 x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Fri Aug 11 16:39:25 2023 InstallationDate: Installed on 2016-08-04 (2563 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha amd64 (20160727.1) SourcePackage: libasyncns UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libasyncns/+bug/2031186/+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 2031186] Re: failed to add/activate wifi connection after netplan intalled_unresolved
Interestingly enough, the following information was recenly encountered regarding using netplan: Change your /etc/netplan/01-netcfg.yaml to the following code (and only this)... using sudo -H gedit /etc/netplan/01-netcfg.yaml... network: version: 2 renderer: NetworkManager Then, in terminal... sudo netplan generate # generate config files sudo netplan apply # apply configuration note this message appeared but apparently did not apply to desktop configuration: Cannot call Open vSwitch: ovsdb-server.service is not running. reboot # reboot the computer Then use the standard Network Manager GUI to establish a wired/wireless connection. Note that sudo netplan generate would not execute if .yaml files in /etc/netplan contained a reference to 'random' generated MAC. Note that sudo netplan would not execute if file permissions in /etc/netplan were too lenieent. used chown to configure root:root and chmod at 600 It would appear that a routine apt upgrade from network-manager to network-manager/netplan is not making necessary changes/creating needed file structure. This appears to be a bug, because only manual intervention appears to have enabled netplan to work without error messages and connection failures. This should be addressed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libasyncns in Ubuntu. https://bugs.launchpad.net/bugs/2031186 Title: failed to add/activate wifi connection after netplan intalled_resolved Status in libasyncns package in Ubuntu: New Bug description: message recipient disconnected from message bus without replying lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Mantic Minotaur (development branch) Release: 23.10 Codename: mantic hi libasyncns0:amd64 0.8-6build3 amd64Asynchronous name service query library hi libasyncns0:i386 0.8-6build3 i386 Asynchronous name service query library Expected wifi connection as anticipated with 0.8-6build2. Wifi connection failure notice when selecting network connection after update to 0.8-6build3. Restore from backup with system upgrade excluding above problem packages does not produce wifi connection problem. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: libasyncns0 0.8-6build2 Uname: Linux 6.5.0-rc1 x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Fri Aug 11 16:39:25 2023 InstallationDate: Installed on 2016-08-04 (2563 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha amd64 (20160727.1) SourcePackage: libasyncns UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libasyncns/+bug/2031186/+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 2047314] Re: tzdata 2023d release (leap-second.list expiring this week)
I prepared the ESM updates for trusty, xenial, and bionic in git: https://code.launchpad.net/~ubuntu-core- dev/ubuntu/+source/tzdata/+git/tzdata -- 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/2047314 Title: tzdata 2023d release (leap-second.list expiring this week) Status in tzdata package in Ubuntu: Fix Committed Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Lunar: New Status in tzdata source package in Mantic: New Bug description: [ Impact ] leap-seconds.list shipped by tzdata 2023c expired on Dec 28th 2023. The 2023d release contains the following changes: Briefly: Ittoqqortoormiit, Greenland changes time zones on 2024-03-31. Vostok, Antarctica changed time zones on 2023-12-18. Casey, Antarctica changed time zones five times since 2020. Code and data fixes for Palestine timestamps starting in 2072. A new data file zonenow.tab for timestamps starting now. Changes to future timestamps Ittoqqortoormiit, Greenland (America/Scoresbysund) joins most of the rest of Greenland's timekeeping practice on 2024-03-31, by changing its time zone from -01/+00 to -02/-01 at the same moment as the spring-forward transition. Its clocks will therefore not spring forward as previously scheduled. The time zone change reverts to its common practice before 1981. Fix predictions for DST transitions in Palestine in 2072-2075, correcting a typo introduced in 2023a. Changes to past and future timestamps Vostok, Antarctica changed to +05 on 2023-12-18. It had been at +07 (not +06) for years. (Thanks to Zakhary V. Akulov.) Change data for Casey, Antarctica to agree with timeanddate.com, by adding five time zone changes since 2020. Casey is now at +08 instead of +11. Changes to past tm_isdst flags Much of Greenland, represented by America/Nuuk, changed its standard time from -03 to -02 on 2023-03-25, not on 2023-10-28. This does not affect UTC offsets, only the tm_isdst flag. (Thanks to Thomas M. Steenholdt.) New data file A new data file zonenow.tab helps configure applications that use timestamps dated from now on. This simplifies configuration, since users choose from a smaller Zone set. The file's format is experimental and subject to change. [ Test Plan ] Test cases were added to autopkgtest to cover the testing: * python: test_2023d So the test plan is to check that all autopkgtest succeeds. [ Other Info ] The autopkgtest for chrony is flaky on jammy and newer (see bug #2002910). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2047314/+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 2040389] Re: Merge libmnl from Debian unstable for noble
libmnl | 1.0.5-2| sid libmnl | 1.0.4-3ubuntu1 | noble Reopening since a new version is available in Debian ** Changed in: libmnl (Ubuntu) Status: Expired => New ** Description changed: Scheduled-For: Backlog Upstream: tbd - Debian: 1.0.4-3 + Debian: 1.0.5.2 Ubuntu: 1.0.4-3ubuntu1 - There is nothing yet to merge for libmnl currently, but this ticket is filed prospectfully for tracking purposes in case a merge does become available later this cycle. If it turns out this needs a sync rather than a merge, please change the tag 'needs-merge' to 'needs-sync', and (optionally) update the title as desired. - ### Old Ubuntu Delta ### libmnl (1.0.4-3ubuntu1) kinetic; urgency=medium - * Static build does not work for libmnl (-lmnl) (LP: #1971523) + * Static build does not work for libmnl (-lmnl) (LP: #1971523) - -- Michal Maloszewski Thu, 21 Jul + -- Michal Maloszewski Thu, 21 Jul 2022 14:02:16 +0200 libmnl (1.0.4-3build2) jammy; urgency=high - * No change rebuild for ppc64el baseline bump. + * No change rebuild for ppc64el baseline bump. - -- Julian Andres Klode Thu, 24 Mar 2022 13:13:28 + -- Julian Andres Klode Thu, 24 Mar 2022 13:13:28 +0100 libmnl (1.0.4-3build1) impish; urgency=medium - * No-change rebuild to build packages with zstd compression. + * No-change rebuild to build packages with zstd compression. - -- Matthias Klose Thu, 07 Oct 2021 12:16:42 +0200 + -- Matthias Klose Thu, 07 Oct 2021 12:16:42 +0200 ** Changed in: libmnl (Ubuntu) Milestone: None => ubuntu-24.01 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libmnl in Ubuntu. https://bugs.launchpad.net/bugs/2040389 Title: Merge libmnl from Debian unstable for noble Status in libmnl package in Ubuntu: New Bug description: Scheduled-For: Backlog Upstream: tbd Debian: 1.0.5.2 Ubuntu: 1.0.4-3ubuntu1 There is nothing yet to merge for libmnl currently, but this ticket is filed prospectfully for tracking purposes in case a merge does become available later this cycle. If it turns out this needs a sync rather than a merge, please change the tag 'needs-merge' to 'needs-sync', and (optionally) update the title as desired. ### Old Ubuntu Delta ### libmnl (1.0.4-3ubuntu1) kinetic; urgency=medium * Static build does not work for libmnl (-lmnl) (LP: #1971523) -- Michal Maloszewski Thu, 21 Jul 2022 14:02:16 +0200 libmnl (1.0.4-3build2) jammy; urgency=high * No change rebuild for ppc64el baseline bump. -- Julian Andres Klode Thu, 24 Mar 2022 13:13:28 +0100 libmnl (1.0.4-3build1) impish; urgency=medium * No-change rebuild to build packages with zstd compression. -- Matthias Klose Thu, 07 Oct 2021 12:16:42 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmnl/+bug/2040389/+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 2040273] Re: [SRU] Enable support for Caracal Cloud Archive
This bug was fixed in the package software-properties - 0.99.22.9 --- software-properties (0.99.22.9) jammy; urgency=medium * cloudarchive: Enable support for the Caracal Ubuntu Cloud Archive on 22.04 (LP: #2040273). -- Corey Bryant Tue, 24 Oct 2023 09:07:34 -0400 ** Changed in: software-properties (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2040273 Title: [SRU] Enable support for Caracal Cloud Archive Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Jammy: Fix Released Status in software-properties source package in Noble: Fix Released Bug description: Please add support for: cloud-archive:caracal cloud-archive:caracal-proposed This will also need to be SRU'd back to jammy. [Impact] End users have to manually enable the caracal cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:caracal sudo add-apt-repository cloud-archive:caracal-proposed [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2040273/+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 1958019]
(In reply to zacherytapp from comment #796) > Hey it looks like Lenovo has released a new BIOS version for the Legion S7 > 16ARHA7 Slim model (the one I have that still has no sound). I'm curious if > anyone has updated to this BIOS yet and if that's resolved any issues or if > this would allow further development on the audio issue. I checked new BIOS version on my legion S7 16ARHA7. Nothing changed unfortunately -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]
(In reply to Andrew from comment #789) > Created attachment 305523 [details] > alsa-info.txt > > Thanks Cameron! Adding those files to /lib/firmware didn't work (I copied > the files directly), so I'm probably out of luck for now. I've attached my > alsa-info.txt in case it helps. Hey, try to run the script from Thomas from comment 778. I have the same model and it worked for me. (In reply to Thomas Gfeller from comment #778) > This change will be included in the kernel in the next couple of weeks / > months so no workaround will be necessary anymore. Thomas, can you give more details about how did you find the values used on the script and the current status of merging it to the kernel? -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 2040273] Update Released
The verification of the Stable Release Update for software-properties has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2040273 Title: [SRU] Enable support for Caracal Cloud Archive Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Jammy: Fix Committed Status in software-properties source package in Noble: Fix Released Bug description: Please add support for: cloud-archive:caracal cloud-archive:caracal-proposed This will also need to be SRU'd back to jammy. [Impact] End users have to manually enable the caracal cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:caracal sudo add-apt-repository cloud-archive:caracal-proposed [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2040273/+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 2047314] Re: tzdata 2023d release (leap-second.list expiring this week)
** Patch added: "tzdata_2023d-0ubuntu0.20.04.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2047314/+attachment/5735596/+files/tzdata_2023d-0ubuntu0.20.04.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2047314 Title: tzdata 2023d release (leap-second.list expiring this week) Status in tzdata package in Ubuntu: Fix Committed Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Lunar: New Status in tzdata source package in Mantic: New Bug description: [ Impact ] leap-seconds.list shipped by tzdata 2023c expired on Dec 28th 2023. The 2023d release contains the following changes: Briefly: Ittoqqortoormiit, Greenland changes time zones on 2024-03-31. Vostok, Antarctica changed time zones on 2023-12-18. Casey, Antarctica changed time zones five times since 2020. Code and data fixes for Palestine timestamps starting in 2072. A new data file zonenow.tab for timestamps starting now. Changes to future timestamps Ittoqqortoormiit, Greenland (America/Scoresbysund) joins most of the rest of Greenland's timekeeping practice on 2024-03-31, by changing its time zone from -01/+00 to -02/-01 at the same moment as the spring-forward transition. Its clocks will therefore not spring forward as previously scheduled. The time zone change reverts to its common practice before 1981. Fix predictions for DST transitions in Palestine in 2072-2075, correcting a typo introduced in 2023a. Changes to past and future timestamps Vostok, Antarctica changed to +05 on 2023-12-18. It had been at +07 (not +06) for years. (Thanks to Zakhary V. Akulov.) Change data for Casey, Antarctica to agree with timeanddate.com, by adding five time zone changes since 2020. Casey is now at +08 instead of +11. Changes to past tm_isdst flags Much of Greenland, represented by America/Nuuk, changed its standard time from -03 to -02 on 2023-03-25, not on 2023-10-28. This does not affect UTC offsets, only the tm_isdst flag. (Thanks to Thomas M. Steenholdt.) New data file A new data file zonenow.tab helps configure applications that use timestamps dated from now on. This simplifies configuration, since users choose from a smaller Zone set. The file's format is experimental and subject to change. [ Test Plan ] Test cases were added to autopkgtest to cover the testing: * python: test_2023d So the test plan is to check that all autopkgtest succeeds. [ Other Info ] The autopkgtest for chrony is flaky on jammy and newer (see bug #2002910). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2047314/+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 2047314] Re: tzdata 2023d release (leap-second.list expiring this week)
** Tags added: patch -- 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/2047314 Title: tzdata 2023d release (leap-second.list expiring this week) Status in tzdata package in Ubuntu: Fix Committed Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Lunar: New Status in tzdata source package in Mantic: New Bug description: [ Impact ] leap-seconds.list shipped by tzdata 2023c expired on Dec 28th 2023. The 2023d release contains the following changes: Briefly: Ittoqqortoormiit, Greenland changes time zones on 2024-03-31. Vostok, Antarctica changed time zones on 2023-12-18. Casey, Antarctica changed time zones five times since 2020. Code and data fixes for Palestine timestamps starting in 2072. A new data file zonenow.tab for timestamps starting now. Changes to future timestamps Ittoqqortoormiit, Greenland (America/Scoresbysund) joins most of the rest of Greenland's timekeeping practice on 2024-03-31, by changing its time zone from -01/+00 to -02/-01 at the same moment as the spring-forward transition. Its clocks will therefore not spring forward as previously scheduled. The time zone change reverts to its common practice before 1981. Fix predictions for DST transitions in Palestine in 2072-2075, correcting a typo introduced in 2023a. Changes to past and future timestamps Vostok, Antarctica changed to +05 on 2023-12-18. It had been at +07 (not +06) for years. (Thanks to Zakhary V. Akulov.) Change data for Casey, Antarctica to agree with timeanddate.com, by adding five time zone changes since 2020. Casey is now at +08 instead of +11. Changes to past tm_isdst flags Much of Greenland, represented by America/Nuuk, changed its standard time from -03 to -02 on 2023-03-25, not on 2023-10-28. This does not affect UTC offsets, only the tm_isdst flag. (Thanks to Thomas M. Steenholdt.) New data file A new data file zonenow.tab helps configure applications that use timestamps dated from now on. This simplifies configuration, since users choose from a smaller Zone set. The file's format is experimental and subject to change. [ Test Plan ] Test cases were added to autopkgtest to cover the testing: * python: test_2023d So the test plan is to check that all autopkgtest succeeds. [ Other Info ] The autopkgtest for chrony is flaky on jammy and newer (see bug #2002910). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2047314/+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 2047314] Re: tzdata 2023d release (leap-second.list expiring this week)
** Patch added: "tzdata_2023d-0ubuntu0.22.04.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2047314/+attachment/5735595/+files/tzdata_2023d-0ubuntu0.22.04.debdiff ** Description changed: [ Impact ] leap-seconds.list shipped by tzdata 2023c expired on Dec 28th 2023. The 2023d release contains the following changes: Briefly: Ittoqqortoormiit, Greenland changes time zones on 2024-03-31. Vostok, Antarctica changed time zones on 2023-12-18. Casey, Antarctica changed time zones five times since 2020. Code and data fixes for Palestine timestamps starting in 2072. A new data file zonenow.tab for timestamps starting now. Changes to future timestamps Ittoqqortoormiit, Greenland (America/Scoresbysund) joins most of the rest of Greenland's timekeeping practice on 2024-03-31, by changing its time zone from -01/+00 to -02/-01 at the same moment as the spring-forward transition. Its clocks will therefore not spring forward as previously scheduled. The time zone change reverts to its common practice before 1981. Fix predictions for DST transitions in Palestine in 2072-2075, correcting a typo introduced in 2023a. Changes to past and future timestamps Vostok, Antarctica changed to +05 on 2023-12-18. It had been at +07 (not +06) for years. (Thanks to Zakhary V. Akulov.) Change data for Casey, Antarctica to agree with timeanddate.com, by adding five time zone changes since 2020. Casey is now at +08 instead of +11. Changes to past tm_isdst flags Much of Greenland, represented by America/Nuuk, changed its standard time from -03 to -02 on 2023-03-25, not on 2023-10-28. This does not affect UTC offsets, only the tm_isdst flag. (Thanks to Thomas M. Steenholdt.) New data file A new data file zonenow.tab helps configure applications that use timestamps dated from now on. This simplifies configuration, since users choose from a smaller Zone set. The file's format is experimental and subject to change. [ Test Plan ] Test cases were added to autopkgtest to cover the testing: * python: test_2023d So the test plan is to check that all autopkgtest succeeds. [ Other Info ] - The autopkgtest for chrony is flaky on jammy and kinetic (see bug + The autopkgtest for chrony is flaky on jammy and newer (see bug #2002910). -- 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/2047314 Title: tzdata 2023d release (leap-second.list expiring this week) Status in tzdata package in Ubuntu: Fix Committed Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Lunar: New Status in tzdata source package in Mantic: New Bug description: [ Impact ] leap-seconds.list shipped by tzdata 2023c expired on Dec 28th 2023. The 2023d release contains the following changes: Briefly: Ittoqqortoormiit, Greenland changes time zones on 2024-03-31. Vostok, Antarctica changed time zones on 2023-12-18. Casey, Antarctica changed time zones five times since 2020. Code and data fixes for Palestine timestamps starting in 2072. A new data file zonenow.tab for timestamps starting now. Changes to future timestamps Ittoqqortoormiit, Greenland (America/Scoresbysund) joins most of the rest of Greenland's timekeeping practice on 2024-03-31, by changing its time zone from -01/+00 to -02/-01 at the same moment as the spring-forward transition. Its clocks will therefore not spring forward as previously scheduled. The time zone change reverts to its common practice before 1981. Fix predictions for DST transitions in Palestine in 2072-2075, correcting a typo introduced in 2023a. Changes to past and future timestamps Vostok, Antarctica changed to +05 on 2023-12-18. It had been at +07 (not +06) for years. (Thanks to Zakhary V. Akulov.) Change data for Casey, Antarctica to agree with timeanddate.com, by adding five time zone changes since 2020. Casey is now at +08 instead of +11. Changes to past tm_isdst flags Much of Greenland, represented by America/Nuuk, changed its standard time from -03 to -02 on 2023-03-25, not on 2023-10-28. This does not affect UTC offsets, only the tm_isdst flag. (Thanks to Thomas M. Steenholdt.) New data file A new data file zonenow.tab helps configure applications that use timestamps dated from now on. This simplifies configuration, since users choose from a smaller Zone set. The file's format is experimental and subject to change.
[Touch-packages] [Bug 2047314] Re: tzdata 2023d release (leap-second.list expiring this week)
-- 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/2047314 Title: tzdata 2023d release (leap-second.list expiring this week) Status in tzdata package in Ubuntu: Fix Committed Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Lunar: New Status in tzdata source package in Mantic: New Bug description: [ Impact ] leap-seconds.list shipped by tzdata 2023c expired on Dec 28th 2023. The 2023d release contains the following changes: Briefly: Ittoqqortoormiit, Greenland changes time zones on 2024-03-31. Vostok, Antarctica changed time zones on 2023-12-18. Casey, Antarctica changed time zones five times since 2020. Code and data fixes for Palestine timestamps starting in 2072. A new data file zonenow.tab for timestamps starting now. Changes to future timestamps Ittoqqortoormiit, Greenland (America/Scoresbysund) joins most of the rest of Greenland's timekeeping practice on 2024-03-31, by changing its time zone from -01/+00 to -02/-01 at the same moment as the spring-forward transition. Its clocks will therefore not spring forward as previously scheduled. The time zone change reverts to its common practice before 1981. Fix predictions for DST transitions in Palestine in 2072-2075, correcting a typo introduced in 2023a. Changes to past and future timestamps Vostok, Antarctica changed to +05 on 2023-12-18. It had been at +07 (not +06) for years. (Thanks to Zakhary V. Akulov.) Change data for Casey, Antarctica to agree with timeanddate.com, by adding five time zone changes since 2020. Casey is now at +08 instead of +11. Changes to past tm_isdst flags Much of Greenland, represented by America/Nuuk, changed its standard time from -03 to -02 on 2023-03-25, not on 2023-10-28. This does not affect UTC offsets, only the tm_isdst flag. (Thanks to Thomas M. Steenholdt.) New data file A new data file zonenow.tab helps configure applications that use timestamps dated from now on. This simplifies configuration, since users choose from a smaller Zone set. The file's format is experimental and subject to change. [ Test Plan ] Test cases were added to autopkgtest to cover the testing: * python: test_2023d So the test plan is to check that all autopkgtest succeeds. [ Other Info ] The autopkgtest for chrony is flaky on jammy and newer (see bug #2002910). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2047314/+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 2047314] Re: tzdata 2023d release (leap-second.list expiring this week)
** Patch added: "tzdata_2023d-0ubuntu0.23.04.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2047314/+attachment/5735593/+files/tzdata_2023d-0ubuntu0.23.04.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2047314 Title: tzdata 2023d release (leap-second.list expiring this week) Status in tzdata package in Ubuntu: Fix Committed Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Lunar: New Status in tzdata source package in Mantic: New Bug description: [ Impact ] leap-seconds.list shipped by tzdata 2023c expired on Dec 28th 2023. The 2023d release contains the following changes: Briefly: Ittoqqortoormiit, Greenland changes time zones on 2024-03-31. Vostok, Antarctica changed time zones on 2023-12-18. Casey, Antarctica changed time zones five times since 2020. Code and data fixes for Palestine timestamps starting in 2072. A new data file zonenow.tab for timestamps starting now. Changes to future timestamps Ittoqqortoormiit, Greenland (America/Scoresbysund) joins most of the rest of Greenland's timekeeping practice on 2024-03-31, by changing its time zone from -01/+00 to -02/-01 at the same moment as the spring-forward transition. Its clocks will therefore not spring forward as previously scheduled. The time zone change reverts to its common practice before 1981. Fix predictions for DST transitions in Palestine in 2072-2075, correcting a typo introduced in 2023a. Changes to past and future timestamps Vostok, Antarctica changed to +05 on 2023-12-18. It had been at +07 (not +06) for years. (Thanks to Zakhary V. Akulov.) Change data for Casey, Antarctica to agree with timeanddate.com, by adding five time zone changes since 2020. Casey is now at +08 instead of +11. Changes to past tm_isdst flags Much of Greenland, represented by America/Nuuk, changed its standard time from -03 to -02 on 2023-03-25, not on 2023-10-28. This does not affect UTC offsets, only the tm_isdst flag. (Thanks to Thomas M. Steenholdt.) New data file A new data file zonenow.tab helps configure applications that use timestamps dated from now on. This simplifies configuration, since users choose from a smaller Zone set. The file's format is experimental and subject to change. [ Test Plan ] Test cases were added to autopkgtest to cover the testing: * python: test_2023d So the test plan is to check that all autopkgtest succeeds. [ Other Info ] The autopkgtest for chrony is flaky on jammy and kinetic (see bug #2002910). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2047314/+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 2047314] Re: tzdata 2023d release (leap-second.list expiring this week)
** Patch added: "tzdata_2023d-0ubuntu0.23.10.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2047314/+attachment/5735592/+files/tzdata_2023d-0ubuntu0.23.10.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2047314 Title: tzdata 2023d release (leap-second.list expiring this week) Status in tzdata package in Ubuntu: Fix Committed Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Lunar: New Status in tzdata source package in Mantic: New Bug description: [ Impact ] leap-seconds.list shipped by tzdata 2023c expired on Dec 28th 2023. The 2023d release contains the following changes: Briefly: Ittoqqortoormiit, Greenland changes time zones on 2024-03-31. Vostok, Antarctica changed time zones on 2023-12-18. Casey, Antarctica changed time zones five times since 2020. Code and data fixes for Palestine timestamps starting in 2072. A new data file zonenow.tab for timestamps starting now. Changes to future timestamps Ittoqqortoormiit, Greenland (America/Scoresbysund) joins most of the rest of Greenland's timekeeping practice on 2024-03-31, by changing its time zone from -01/+00 to -02/-01 at the same moment as the spring-forward transition. Its clocks will therefore not spring forward as previously scheduled. The time zone change reverts to its common practice before 1981. Fix predictions for DST transitions in Palestine in 2072-2075, correcting a typo introduced in 2023a. Changes to past and future timestamps Vostok, Antarctica changed to +05 on 2023-12-18. It had been at +07 (not +06) for years. (Thanks to Zakhary V. Akulov.) Change data for Casey, Antarctica to agree with timeanddate.com, by adding five time zone changes since 2020. Casey is now at +08 instead of +11. Changes to past tm_isdst flags Much of Greenland, represented by America/Nuuk, changed its standard time from -03 to -02 on 2023-03-25, not on 2023-10-28. This does not affect UTC offsets, only the tm_isdst flag. (Thanks to Thomas M. Steenholdt.) New data file A new data file zonenow.tab helps configure applications that use timestamps dated from now on. This simplifies configuration, since users choose from a smaller Zone set. The file's format is experimental and subject to change. [ Test Plan ] Test cases were added to autopkgtest to cover the testing: * python: test_2023d So the test plan is to check that all autopkgtest succeeds. [ Other Info ] The autopkgtest for chrony is flaky on jammy and kinetic (see bug #2002910). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2047314/+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 2047314] Re: tzdata 2023d release (leap-second.list expiring this week)
** Changed in: tzdata (Ubuntu) Status: Triaged => Fix Committed -- 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/2047314 Title: tzdata 2023d release (leap-second.list expiring this week) Status in tzdata package in Ubuntu: Fix Committed Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Lunar: New Status in tzdata source package in Mantic: New Bug description: [ Impact ] leap-seconds.list shipped by tzdata 2023c expired on Dec 28th 2023. The 2023d release contains the following changes: Briefly: Ittoqqortoormiit, Greenland changes time zones on 2024-03-31. Vostok, Antarctica changed time zones on 2023-12-18. Casey, Antarctica changed time zones five times since 2020. Code and data fixes for Palestine timestamps starting in 2072. A new data file zonenow.tab for timestamps starting now. Changes to future timestamps Ittoqqortoormiit, Greenland (America/Scoresbysund) joins most of the rest of Greenland's timekeeping practice on 2024-03-31, by changing its time zone from -01/+00 to -02/-01 at the same moment as the spring-forward transition. Its clocks will therefore not spring forward as previously scheduled. The time zone change reverts to its common practice before 1981. Fix predictions for DST transitions in Palestine in 2072-2075, correcting a typo introduced in 2023a. Changes to past and future timestamps Vostok, Antarctica changed to +05 on 2023-12-18. It had been at +07 (not +06) for years. (Thanks to Zakhary V. Akulov.) Change data for Casey, Antarctica to agree with timeanddate.com, by adding five time zone changes since 2020. Casey is now at +08 instead of +11. Changes to past tm_isdst flags Much of Greenland, represented by America/Nuuk, changed its standard time from -03 to -02 on 2023-03-25, not on 2023-10-28. This does not affect UTC offsets, only the tm_isdst flag. (Thanks to Thomas M. Steenholdt.) New data file A new data file zonenow.tab helps configure applications that use timestamps dated from now on. This simplifies configuration, since users choose from a smaller Zone set. The file's format is experimental and subject to change. [ Test Plan ] Test cases were added to autopkgtest to cover the testing: * python: test_2023d So the test plan is to check that all autopkgtest succeeds. [ Other Info ] The autopkgtest for chrony is flaky on jammy and kinetic (see bug #2002910). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2047314/+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 2046356] Re: Update URL for Support information in MOTD message
** Merge proposal linked: https://code.launchpad.net/~lamoura/ubuntu/+source/base-files/+git/base-files/+merge/457845 ** Merge proposal linked: https://code.launchpad.net/~lamoura/ubuntu/+source/base-files/+git/base-files/+merge/457851 ** Merge proposal linked: https://code.launchpad.net/~lamoura/ubuntu/+source/base-files/+git/base-files/+merge/457846 ** Merge proposal linked: https://code.launchpad.net/~lamoura/ubuntu/+source/base-files/+git/base-files/+merge/457847 ** Merge proposal linked: https://code.launchpad.net/~lamoura/ubuntu/+source/base-files/+git/base-files/+merge/457849 ** Merge proposal linked: https://code.launchpad.net/~lamoura/ubuntu/+source/base-files/+git/base-files/+merge/457850 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/2046356 Title: Update URL for Support information in MOTD message Status in base-files package in Ubuntu: New Status in base-files source package in Xenial: New Status in base-files source package in Bionic: New Status in base-files source package in Focal: New Status in base-files source package in Jammy: New Status in base-files source package in Mantic: New Status in base-files source package in Noble: New Bug description: [Impact] When users see the MOTD message, they are currently seeing an outdated url under the support information. Even though the outdated url redirects to new Ubuntu Pro webpage, we believe the users should still see the correct url from the start [Test Case] - Launch a LXD container for any of the affected releases - Install the package with this fix applied - Install `update-motd` package - Run `update-motd` and confirm the Support url is now the correct one [Regression Potential] If users are parsing MOTD for some reason, the url change might break that logic now. However, parsing MOTD messages is not a supported flow, so we believe regression potential is low here. [Discussion] Since we want users to be aware of what Ubuntu Pro is, we should highlight the right product name on any place that is still using the old "advantage" name. Updating the support URL here is a step into this direction [Original Bug Description] On the file 10-help-text, we are printing the following line on MOTD: * Support: https://ubuntu.com/advantage We should update the url to https://ubuntu.com/pro instead, as this will the default url for support information now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2046356/+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 2030977] Re: icu data files shipped in tzdata source package are generated and miss original form
** Description changed: The tzdata source packages ships four files in debian/icu that are not built from source: ``` $ grep -i generated debian/icu/* debian/icu/metaZones.txt:// Generated using tools/cldr/cldr-to-icu/build-icu-data.xml debian/icu/timezoneTypes.txt:// Generated using tools/cldr/cldr-to-icu/build-icu-data.xml debian/icu/windowsZones.txt:// Generated using tools/cldr/cldr-to-icu/build-icu-data.xml debian/icu/zoneinfo64.txt:// >> !!! >> THIS IS A MACHINE-GENERATED FILE << !!! << ``` They're not considered as the preferred form of modification. Please replace them with the original form and generate them with - tools/cldr/cldr-to-icu/build-icu-data.xml during package build. + tools/cldr/cldr-to-icu/build-icu-data.xml during package build: + https://github.com/unicode-org/icu/blob/main/tools/cldr/cldr-to- + icu/build-icu-data.xml -- 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/2030977 Title: icu data files shipped in tzdata source package are generated and miss original form Status in tzdata package in Ubuntu: New Bug description: The tzdata source packages ships four files in debian/icu that are not built from source: ``` $ grep -i generated debian/icu/* debian/icu/metaZones.txt:// Generated using tools/cldr/cldr-to-icu/build-icu-data.xml debian/icu/timezoneTypes.txt:// Generated using tools/cldr/cldr-to-icu/build-icu-data.xml debian/icu/windowsZones.txt:// Generated using tools/cldr/cldr-to-icu/build-icu-data.xml debian/icu/zoneinfo64.txt:// >> !!! >> THIS IS A MACHINE-GENERATED FILE << !!! << ``` They're not considered as the preferred form of modification. Please replace them with the original form and generate them with tools/cldr/cldr-to-icu/build-icu-data.xml during package build: https://github.com/unicode-org/icu/blob/main/tools/cldr/cldr-to- icu/build-icu-data.xml To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2030977/+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 2047843] Re: libEGL Crashes and locks applications
See also: * [libEGL "failed to create dri2 screen" and coredump](https://gitlab.freedesktop.org/glvnd/libglvnd/-/issues/246) The EGL tool: eglinfo, coredump-s under several conditions, eg: $ eglinfo -B GBM platform: EGL API version: 1.5 EGL vendor string: NVIDIA EGL version string: 1.5 EGL client APIs: OpenGL_ES OpenGL OpenGL core profile vendor: NVIDIA Corporation OpenGL core profile renderer: NVIDIA GeForce RTX 2080/PCIe/SSE2 OpenGL core profile version: 4.6.0 NVIDIA 535.129.03 OpenGL core profile shading language version: 4.60 NVIDIA OpenGL compatibility profile vendor: NVIDIA Corporation OpenGL compatibility profile renderer: NVIDIA GeForce RTX 2080/PCIe/SSE2 OpenGL compatibility profile version: 4.6.0 NVIDIA 535.129.03 OpenGL compatibility profile shading language version: 4.60 NVIDIA OpenGL ES profile vendor: NVIDIA Corporation OpenGL ES profile renderer: NVIDIA GeForce RTX 2080/PCIe/SSE2 OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 535.129.03 OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20 corrupted size vs. prev_size Aborted (core dumped) ** Tags added: regression ** Bug watch added: gitlab.freedesktop.org/glvnd/libglvnd/-/issues #246 https://gitlab.freedesktop.org/glvnd/libglvnd/-/issues/246 -- 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/2047843 Title: libEGL Crashes and locks applications Status in mesa package in Ubuntu: New Bug description: I am getting this error or something very similar quite regularly since befor 25 December 2023. ERROR: $ flatpak run org.wezfurlong.wezterm libEGL warning: egl: failed to create dri2 screen MESA: error: CreateSwapchainKHR failed with VK_ERROR_INITIALIZATION_FAILED MESA: error: zink: could not create swapchain I have pasted this error output from the console, because it is the most informative version I've seen so far. The first time I saw this problem, I mistakenly thought it was an issue with a Rust library I was using, details are available here: * [egl: failed to create dri2 screen #355](https://github.com/amethyst/bracket-lib/issues/355) When I posted that bug, I thought there was something to do witih the moust -- No. Lots of things crash (or hang) with no activity on my part. The only common denominator seems to be using the OpenGL or something in Mesa. I am happy to turn-on a log or diagnostics and send someone the output. I do not feel equiped to figure things out as the end user. I peeked at the syslog file but nothing there seemed to relate to the message I'm seeing. * So if theres some diagnostic I can do, let me know. EXPECTED * Not to get the crash/error from libEGL * Top level user applications run with no issues * Perhaps there is a way to turn-off the libEGL so this problem can be side-stepped until such time there is a working solution ~ I am running Kubuntu 23.10 using Wayland. NVIDIA graphics: Graphics: Device-1: NVIDIA TU104 [GeForce RTX 2080 Rev. A] vendor: Gigabyte driver: nvidia v: 535.129.03 arch: Turing bus-ID: 07:00.0 Display: wayland server: X.org v: 1.21.1.7 with: Xwayland v: 23.2.0 compositor: kwin_wayland driver: X: loaded: nvidia unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia resolution: 1: 1920x1080 2: 1920x1080 API: OpenGL v: 4.5 Mesa 23.2.1-1ubuntu3.1 renderer: llvmpipe (LLVM 15.0.7 256 bits) direct-render: Yes System information: System: Kernel: 6.5.0-14-generic arch: x86_64 bits: 64 compiler: N/A Desktop: KDE Plasma v: 5.27.8 Distro: Ubuntu 23.10 (Mantic Minotaur) Release: $ lsb_release -a: Distributor ID: Ubuntu Description: Ubuntu 23.10 Release: 23.10 Codename: mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2047843/+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 2045033] Re: Merge rsyslog 8.2312.0-2 from Debian
** Summary changed: - Merge rsyslog 8.2312.0-1 from Debian + Merge rsyslog 8.2312.0-2 from Debian -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2045033 Title: Merge rsyslog 8.2312.0-2 from Debian Status in rsyslog package in Ubuntu: New Bug description: Debian has released rsyslog 8.2310.0-4. Merge it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2045033/+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 2047843] [NEW] libEGL Crashes and locks applications
Public bug reported: I am getting this error or something very similar quite regularly since befor 25 December 2023. ERROR: $ flatpak run org.wezfurlong.wezterm libEGL warning: egl: failed to create dri2 screen MESA: error: CreateSwapchainKHR failed with VK_ERROR_INITIALIZATION_FAILED MESA: error: zink: could not create swapchain I have pasted this error output from the console, because it is the most informative version I've seen so far. The first time I saw this problem, I mistakenly thought it was an issue with a Rust library I was using, details are available here: * [egl: failed to create dri2 screen #355](https://github.com/amethyst/bracket-lib/issues/355) When I posted that bug, I thought there was something to do witih the moust -- No. Lots of things crash (or hang) with no activity on my part. The only common denominator seems to be using the OpenGL or something in Mesa. I am happy to turn-on a log or diagnostics and send someone the output. I do not feel equiped to figure things out as the end user. I peeked at the syslog file but nothing there seemed to relate to the message I'm seeing. * So if theres some diagnostic I can do, let me know. EXPECTED * Not to get the crash/error from libEGL * Top level user applications run with no issues * Perhaps there is a way to turn-off the libEGL so this problem can be side-stepped until such time there is a working solution ~ I am running Kubuntu 23.10 using Wayland. NVIDIA graphics: Graphics: Device-1: NVIDIA TU104 [GeForce RTX 2080 Rev. A] vendor: Gigabyte driver: nvidia v: 535.129.03 arch: Turing bus-ID: 07:00.0 Display: wayland server: X.org v: 1.21.1.7 with: Xwayland v: 23.2.0 compositor: kwin_wayland driver: X: loaded: nvidia unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia resolution: 1: 1920x1080 2: 1920x1080 API: OpenGL v: 4.5 Mesa 23.2.1-1ubuntu3.1 renderer: llvmpipe (LLVM 15.0.7 256 bits) direct-render: Yes System information: System: Kernel: 6.5.0-14-generic arch: x86_64 bits: 64 compiler: N/A Desktop: KDE Plasma v: 5.27.8 Distro: Ubuntu 23.10 (Mantic Minotaur) Release: $ lsb_release -a: Distributor ID: Ubuntu Description:Ubuntu 23.10 Release:23.10 Codename: mantic ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: kubuntu mesa opengl wayland -- 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/2047843 Title: libEGL Crashes and locks applications Status in mesa package in Ubuntu: New Bug description: I am getting this error or something very similar quite regularly since befor 25 December 2023. ERROR: $ flatpak run org.wezfurlong.wezterm libEGL warning: egl: failed to create dri2 screen MESA: error: CreateSwapchainKHR failed with VK_ERROR_INITIALIZATION_FAILED MESA: error: zink: could not create swapchain I have pasted this error output from the console, because it is the most informative version I've seen so far. The first time I saw this problem, I mistakenly thought it was an issue with a Rust library I was using, details are available here: * [egl: failed to create dri2 screen #355](https://github.com/amethyst/bracket-lib/issues/355) When I posted that bug, I thought there was something to do witih the moust -- No. Lots of things crash (or hang) with no activity on my part. The only common denominator seems to be using the OpenGL or something in Mesa. I am happy to turn-on a log or diagnostics and send someone the output. I do not feel equiped to figure things out as the end user. I peeked at the syslog file but nothing there seemed to relate to the message I'm seeing. * So if theres some diagnostic I can do, let me know. EXPECTED * Not to get the crash/error from libEGL * Top level user applications run with no issues * Perhaps there is a way to turn-off the libEGL so this problem can be side-stepped until such time there is a working solution ~ I am running Kubuntu 23.10 using Wayland. NVIDIA graphics: Graphics: Device-1: NVIDIA TU104 [GeForce RTX 2080 Rev. A] vendor: Gigabyte driver: nvidia v: 535.129.03 arch: Turing bus-ID: 07:00.0 Display: wayland server: X.org v: 1.21.1.7 with: Xwayland v: 23.2.0 compositor: kwin_wayland driver: X: loaded: nvidia unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia resolution: 1: 1920x1080 2: 1920x1080 API: OpenGL v: 4.5 Mesa 23.2.1-1ubuntu3.1 renderer: llvmpipe (LLVM 15.0.7 256 bits) direct-render: Yes System information: System: Kernel: 6.5.0-14-generic arch: x86_64 bits: 64 compiler: N/A Desktop: KDE Plasma v: 5.27.8 Distro: Ubuntu 23.10 (Mantic Minotaur) Release: $ lsb_release -a: Distributor ID: Ubuntu Description: Ubuntu 23.10 Release: 23.10 Codename: mantic To manage
[Touch-packages] [Bug 2046356] Re: Update URL for Support information in MOTD message
** Description changed: + + [Impact] + When users see the MOTD message, they are currently seeing an outdated url under the support information. + Even though the outdated url redirects to new Ubuntu Pro webpage, we believe the users should still see + the correct url from the start + + [Test Case] + + - Launch a LXD container for any of the affected releases + - Install the package with this fix applied + - Install `update-motd` package + - Run `update-motd` and confirm the Support url is now the correct one + + [Regression Potential] + If users are parsing MOTD for some reason, the url change might break that logic now. However, parsing MOTD messages is not a supported flow, so we believe regression potential is low here. + + [Discussion] + Since we want users to be aware of what Ubuntu Pro is, we should highlight the right product name on any place that is still using the old "advantage" name. Updating the support URL here is a step into this direction + + [Original Bug Description] On the file 10-help-text, we are printing the following line on MOTD: * Support: https://ubuntu.com/advantage We should update the url to https://ubuntu.com/pro instead, as this will the default url for support information now -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/2046356 Title: Update URL for Support information in MOTD message Status in base-files package in Ubuntu: New Status in base-files source package in Xenial: New Status in base-files source package in Bionic: New Status in base-files source package in Focal: New Status in base-files source package in Jammy: New Status in base-files source package in Mantic: New Status in base-files source package in Noble: New Bug description: [Impact] When users see the MOTD message, they are currently seeing an outdated url under the support information. Even though the outdated url redirects to new Ubuntu Pro webpage, we believe the users should still see the correct url from the start [Test Case] - Launch a LXD container for any of the affected releases - Install the package with this fix applied - Install `update-motd` package - Run `update-motd` and confirm the Support url is now the correct one [Regression Potential] If users are parsing MOTD for some reason, the url change might break that logic now. However, parsing MOTD messages is not a supported flow, so we believe regression potential is low here. [Discussion] Since we want users to be aware of what Ubuntu Pro is, we should highlight the right product name on any place that is still using the old "advantage" name. Updating the support URL here is a step into this direction [Original Bug Description] On the file 10-help-text, we are printing the following line on MOTD: * Support: https://ubuntu.com/advantage We should update the url to https://ubuntu.com/pro instead, as this will the default url for support information now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2046356/+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 2047314] Re: tzdata 2023d release (leap-second.list expiring this week)
** Description changed: + [ Impact ] + leap-seconds.list shipped by tzdata 2023c expired on Dec 28th 2023. The 2023d release contains the following changes: -Briefly: - Ittoqqortoormiit, Greenland changes time zones on 2024-03-31. - Vostok, Antarctica changed time zones on 2023-12-18. - Casey, Antarctica changed time zones five times since 2020. - Code and data fixes for Palestine timestamps starting in 2072. - A new data file zonenow.tab for timestamps starting now. + Briefly: + Ittoqqortoormiit, Greenland changes time zones on 2024-03-31. + Vostok, Antarctica changed time zones on 2023-12-18. + Casey, Antarctica changed time zones five times since 2020. + Code and data fixes for Palestine timestamps starting in 2072. + A new data file zonenow.tab for timestamps starting now. -Changes to future timestamps + Changes to future timestamps - Ittoqqortoormiit, Greenland (America/Scoresbysund) joins most of - the rest of Greenland's timekeeping practice on 2024-03-31, by - changing its time zone from -01/+00 to -02/-01 at the same moment - as the spring-forward transition. Its clocks will therefore not - spring forward as previously scheduled. The time zone change - reverts to its common practice before 1981. + Ittoqqortoormiit, Greenland (America/Scoresbysund) joins most of + the rest of Greenland's timekeeping practice on 2024-03-31, by + changing its time zone from -01/+00 to -02/-01 at the same moment + as the spring-forward transition. Its clocks will therefore not + spring forward as previously scheduled. The time zone change + reverts to its common practice before 1981. - Fix predictions for DST transitions in Palestine in 2072-2075, - correcting a typo introduced in 2023a. + Fix predictions for DST transitions in Palestine in 2072-2075, + correcting a typo introduced in 2023a. -Changes to past and future timestamps + Changes to past and future timestamps - Vostok, Antarctica changed to +05 on 2023-12-18. It had been at - +07 (not +06) for years. (Thanks to Zakhary V. Akulov.) + Vostok, Antarctica changed to +05 on 2023-12-18. It had been at + +07 (not +06) for years. (Thanks to Zakhary V. Akulov.) - Change data for Casey, Antarctica to agree with timeanddate.com, - by adding five time zone changes since 2020. Casey is now at +08 - instead of +11. + Change data for Casey, Antarctica to agree with timeanddate.com, + by adding five time zone changes since 2020. Casey is now at +08 + instead of +11. -Changes to past tm_isdst flags + Changes to past tm_isdst flags - Much of Greenland, represented by America/Nuuk, changed its - standard time from -03 to -02 on 2023-03-25, not on 2023-10-28. - This does not affect UTC offsets, only the tm_isdst flag. - (Thanks to Thomas M. Steenholdt.) + Much of Greenland, represented by America/Nuuk, changed its + standard time from -03 to -02 on 2023-03-25, not on 2023-10-28. + This does not affect UTC offsets, only the tm_isdst flag. + (Thanks to Thomas M. Steenholdt.) -New data file + New data file - A new data file zonenow.tab helps configure applications that use - timestamps dated from now on. This simplifies configuration, - since users choose from a smaller Zone set. The file's format is - experimental and subject to change. + A new data file zonenow.tab helps configure applications that use + timestamps dated from now on. This simplifies configuration, + since users choose from a smaller Zone set. The file's format is + experimental and subject to change. + + [ Test Plan ] + + Test cases were added to autopkgtest to cover the testing: + + * python: test_2023d + + So the test plan is to check that all autopkgtest succeeds. + + [ Other Info ] + + The autopkgtest for chrony is flaky on jammy and kinetic (see bug + #2002910). ** Also affects: tzdata (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: tzdata (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: tzdata (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: tzdata (Ubuntu Lunar) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2047314 Title: tzdata 2023d release (leap-second.list expiring this week) Status in tzdata package in Ubuntu: Triaged Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Lunar: New Status in tzdata source package in Mantic: New Bug description: [ Impact ] leap-seconds.list shipped by tzdata 2023c expired on
[Touch-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
Hi Gerard Brave does not work currently because we only added support to Chromium, Firefox and Opera as you can see in the current snap_browsers abstraction [1]. I'm adding Brave support as well [2]. While that change is not applied to the apparmor package, as a workaround, you could apply the same changes from [2] in /etc/apparmor.d/abstractions/snap_browsers and reload the evince profile sudo apparmor_parser -r /etc/apparmor.d/usr.bin.evince In regards to #include, it is not commented out. The apparmor policy allows the "include" keyword to be preceded by # or not. That said, #include is now being deprecated due to this exact confusion and we recommend using it without #. [1] https://gitlab.com/apparmor/apparmor/-/blob/31c9cf6845cb78cca59a753d7c5b27312d579be8/profiles/apparmor.d/abstractions/snap_browsers [2] https://gitlab.com/apparmor/apparmor/-/merge_requests/1137 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Fix Released Status in evince package in Ubuntu: Fix Released Status in apparmor source package in Jammy: Fix Released Status in evince source package in Jammy: Fix Released Status in apparmor source package in Lunar: Fix Released Status in evince source package in Lunar: Fix Released Status in apparmor package in Debian: Fix Released Status in evince package in Debian: Confirmed Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1117804] Re: ausearch doesn't show AppArmor denial messages
Any news on this? It has been open for over ten years now. AppArmor is on by default on Ubuntu, and if auditd is used, then the events are logged using it. Isn't it a security bug if the events don't show up when queried using ausearch? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to audit in Ubuntu. https://bugs.launchpad.net/bugs/1117804 Title: ausearch doesn't show AppArmor denial messages Status in AppArmor: Confirmed Status in audit package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: The following command should display all AVC denials: ausearch -m avc However, it doesn't work with AppArmor denials. Here's a quick test case to generate a denial, search for it with ausearch, and see that no messages are displayed: $ aa-exec -p /usr/sbin/tcpdump cat /proc/self/attr/current cat: /proc/self/attr/current: Permission denied $ sudo ausearch -m avc -c cat ausearch claims that there are no matches, but there's a matching audit message if you look in audit.log: type=AVC msg=audit(1360193426.539:64): apparmor="DENIED" operation="open" parent=8253 profile="/usr/sbin/tcpdump" name="/proc/8485/attr/current" pid=8485 comm="cat" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1117804/+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 2040273] Re: [SRU] Enable support for Caracal Cloud Archive
Verified successfully on jammy. root@j1:~# sudo apt install software-properties-common --yes Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: python3-software-properties The following packages will be upgraded: python3-software-properties software-properties-common 2 upgraded, 0 newly installed, 0 to remove and 186 not upgraded. Need to get 42.9 kB of archives. After this operation, 5120 B of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 software-properties-common all 0.99.22.9 [14.1 kB] Get:2 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 python3-software-properties all 0.99.22.9 [28.8 kB] Fetched 42.9 kB in 0s (453 kB/s) (Reading database ... 60171 files and directories currently installed.) Preparing to unpack .../software-properties-common_0.99.22.9_all.deb ... Unpacking software-properties-common (0.99.22.9) over (0.99.22.7) ... Preparing to unpack .../python3-software-properties_0.99.22.9_all.deb ... Unpacking python3-software-properties (0.99.22.9) over (0.99.22.7) ... Setting up python3-software-properties (0.99.22.9) ... Setting up software-properties-common (0.99.22.9) ... Processing triggers for man-db (2.10.2-1) ... Processing triggers for dbus (1.12.20-2ubuntu4.1) ... Scanning processes... No services need to be restarted. No containers need to be restarted.
[Touch-packages] [Bug 2046356] Re: Update URL for Support information in MOTD message
** Merge proposal linked: https://code.launchpad.net/~lamoura/ubuntu/+source/base-files/+git/base-files/+merge/457829 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/2046356 Title: Update URL for Support information in MOTD message Status in base-files package in Ubuntu: New Status in base-files source package in Xenial: New Status in base-files source package in Bionic: New Status in base-files source package in Focal: New Status in base-files source package in Jammy: New Status in base-files source package in Mantic: New Status in base-files source package in Noble: New Bug description: On the file 10-help-text, we are printing the following line on MOTD: * Support: https://ubuntu.com/advantage We should update the url to https://ubuntu.com/pro instead, as this will the default url for support information now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2046356/+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 2045886] Re: Please merge 8.5.0-2 into noble
** Merge proposal linked: https://code.launchpad.net/~danilogondolfo/ubuntu/+source/curl/+git/curl/+merge/457830 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/2045886 Title: Please merge 8.5.0-2 into noble Status in curl package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2045886/+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 1489489] Re: The org.freedesktop.DBus.GetConnectionAppArmorSecurityContext() method is deprecated
** Merge proposal linked: https://code.launchpad.net/~ogayot/ubuntu/+source/dbus/+git/dbus/+merge/456880 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1489489 Title: The org.freedesktop.DBus.GetConnectionAppArmorSecurityContext() method is deprecated Status in Ubuntu Online Accounts API: Confirmed Status in snapd: Confirmed Status in apparmor package in Ubuntu: Fix Released Status in biometryd package in Ubuntu: New Status in content-hub package in Ubuntu: Confirmed Status in dbus package in Ubuntu: Triaged Status in deepin-notifications package in Ubuntu: New Status in lomiri-download-manager package in Ubuntu: Fix Released Status in mediascanner2 package in Ubuntu: Fix Released Status in signon-apparmor-extension package in Ubuntu: Fix Released Status in ubuntu-system-settings-online-accounts package in Ubuntu: Fix Released Bug description: When upstream D-Bus merged the AppArmor mediation patches, they did not like the GetConnectionAppArmorSecurityContext() bus method. Instead, they decided to expose a peer's AppArmor context using the org.freedesktop.DBus.GetConnectionCredentials() bus method. All users of the GetConnectionAppArmorSecurityContext() method should switch to the GetConnectionCredentials() method as soon as possible so that Ubuntu can drop the patch that implements GetConnectionAppArmorSecurityContext() by the time 16.04 LTS is released. In order to switch to the new method, you'll need to depend on libapparmor 2.10 or newer. I'll be adding example code that illustrates how to switch from GetConnectionAppArmorSecurityContext() to GetConnectionCredentials(). content-hub, media-hub, mediascanner2, signon-apparmor-extension, ubuntu-download-manager, and ubuntu-system-settings-online-accounts all need to transition to the new method of obtaining the AppArmor label. The apparmor package should be updated to drop the libapparmor- mention-dbus-method-in-getcon-man.patch patch and the dbus package should be updated to drop the aa-get-connection-apparmor-security- context.patch patch. To manage notifications about this bug go to: https://bugs.launchpad.net/online-accounts-api/+bug/1489489/+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 1964506] Re: Ping: checks payloads incorrectly, ignores all mismatch replies
Focal verification # Reproducing the bug ubuntu@f-ping-1964506:~$ apt-cache policy iputils-ping iputils-ping: Installed: 3:20190709-3 Candidate: 3:20190709-3 Version table: *** 3:20190709-3 500 500 http://br.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ubuntu@f-ping-1964506:~$ ping -c 1 -s 1200 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data. --- 8.8.8.8 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms # Confirming the fix with the package from proposed ubuntu@f-ping-1964506:~$ apt-cache policy iputils-ping iputils-ping: Installed: 3:20190709-3ubuntu1 Candidate: 3:20190709-3ubuntu1 Version table: *** 3:20190709-3ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3:20190709-3 500 500 http://br.archive.ubuntu.com/ubuntu focal/main amd64 Packages ubuntu@f-ping-1964506:~$ ping -c 1 -s 1200 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data. 76 bytes from 8.8.8.8: icmp_seq=1 ttl=118 (truncated) --- 8.8.8.8 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 9.690/9.690/9.690/0.000 ms ubuntu@f-ping-1964506:~$ # Focal verification succeeded ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1964506 Title: Ping: checks payloads incorrectly, ignores all mismatch replies Status in iputils package in Ubuntu: Fix Released Status in iputils source package in Focal: Fix Committed Bug description: = Impact = the ping statistics are incorrect when dealing with truncated packets = Test case = $ ping -c 1 -s 1200 8.8.8.8 should list truncated replies and received packets = Regression potential = the changes are limited to the ping source any regression would impact that utility, check that responses are correctly handled and statistics reflecting what is expected -- Problematic commit reverted upstream causing incorrect behavior in Ubuntu Focal. Discussion: https://github.com/iputils/iputils/issues/320 Fix: https://github.com/iputils/iputils/pull/321 Release: https://github.com/iputils/iputils/releases/tag/20210722 Could this patch be added for a Focal update please? 1) Ubuntu 20.04.3 LTS 2) 3:20190709-3 3) focal$ ping -c 1 -s 1200 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data. --- 8.8.8.8 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms 4) xenial$ ping -c 1 -s 1200 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data. 76 bytes from 8.8.8.8: icmp_seq=1 ttl=61 (truncated) --- 8.8.8.8 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.284/0.284/0.284/0.000 ms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1964506/+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 2047719] Re: package slapd 2.4.49+dfsg-2ubuntu1.9 failed to install/upgrade: new slapd package pre-installation script subprocess returned error exit status 1
Thank you for taking the time to report bugs and help make Ubuntu better. This looks like a local configuration issue rather than a bug in the software itself. Please check your configuration to make sure it's correct. If you need help configuring, you can get community support in the Ubuntu channels on libera.chat, or in http://www.ubuntu.com/support/community I'm marking this "Invalid" because it doesn't appear to be a bug, but if I'm wrong, please change it back to "New" and add some more info to point me in the right direction. Use this link as a guide: http://www.chiark.greenend.org.uk/~sgtatham/bugs.html ** Changed in: openldap (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/2047719 Title: package slapd 2.4.49+dfsg-2ubuntu1.9 failed to install/upgrade: new slapd package pre-installation script subprocess returned error exit status 1 Status in openldap package in Ubuntu: Incomplete Bug description: Happened while upgrading ubuntu distro ProblemType: Package DistroRelease: Ubuntu 22.04 Package: slapd 2.4.49+dfsg-2ubuntu1.9 ProcVersionSignature: Ubuntu 5.15.0-1053.61~20.04.1-azure 5.15.131 Uname: Linux 5.15.0-1053-azure x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Dec 29 23:55:31 2023 ErrorMessage: new slapd package pre-installation script subprocess returned error exit status 1 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1053-azure root=UUID=b9df59e6-c806-4851-befa-12402bca5828 ro console=tty1 console=ttyS0 earlyprintk=ttyS0 rootdelay=300 Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: openldap Title: package slapd 2.4.49+dfsg-2ubuntu1.9 failed to install/upgrade: new slapd package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2023-12-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2047719/+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 2047719] Re: package slapd 2.4.49+dfsg-2ubuntu1.9 failed to install/upgrade: new slapd package pre-installation script subprocess returned error exit status 1
Hi and thanks for the report, it seems that the automatic "try to backup and upgrade" failed. That is usually due to local config that does not behave well as it needs knowledge or assumptions the package can't have. Or at other times by using features that have been removed. The log output is actually quite clear on what it tried, and that it suggests to the admin to overcome this to continue. """ Preparing to unpack .../20-slapd_2.5.16+dfsg-0ubuntu0.22.04.1_amd64.deb ... Saving current slapd configuration to /var/backups/slapd-2.4.49+dfsg-2ubuntu1.9... Dumping to /var/backups/slapd-2.4.49+dfsg-2ubuntu1.9: - directory dc=1tmfm1mfbauutnso5ahdvmpnma,dc=gx,dc=internal,dc=cloudapp,dc=ne... slapcat: slap_init no backend for "dc=1tmfm1mfbauutnso5ahdvmpnma,dc=gx,dc=internal,dc=cloudapp,dc=ne" failed. [?1049h[?1h=[1;43r[4l[?25l[m[37m[40m[1;43r[H[J[1;1H[1m[37m[45m [2;1H [3;1H [4;1H [5;1H [6;1H [7;1H [8;1H [9;1H [10;1H [11;1H [12;1H [13;1H [14;1H [15;1H [16;1H [17;1H [18;1H [19;1H [20;1H [21;1H
[Touch-packages] [Bug 2045668] Re: Please merge dbus 1.14.10-3 (main) from Debian unstable
Thanks vorlon. This makes sense. I'll do go ahead and remove dbus's dependency on usr-is-merged. Unsubscribing Ubuntu Package Archive. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/2045668 Title: Please merge dbus 1.14.10-3 (main) from Debian unstable Status in dbus package in Ubuntu: In Progress Bug description: 1.14.10-3 Published in sid-release on 2023-10-30 dbus (1.14.10-3) unstable; urgency=medium * d/control: dbus Depends on usr-is-merged (>= 38~). Non-merged /usr has been unsupported since Debian 12, as per Technical Committee resolutions #978636 and #994388 (please see the Debian 12 release notes for details). The version of usr-is-merged shipped in Debian 12 had an undocumented opt-out mechanism intended for use on buildds and QA systems targeting Debian 12 (piuparts, reproducible-builds, autopkgtest and similar), to ensure that the upgrade path from Debian 11 to 12 will continue to work and continue to undergo automated tests. That opt-out is no longer applicable or available in trixie/sid, and was removed in usrmerge version 38. Since version 1.14.10-2, dbus ships its systemd units in /usr/lib/systemd/system, as part of the distro-wide transition away from making use of "aliased" paths. This is entirely valid on merged-/usr systems, but will no longer work in the unsupported filesystem layout with non-merged /usr, because for historical reasons, current versions of systemd on non-merged-/usr systems will only read units from /lib/systemd/system. In the case of dbus, the symptom when this assumption is broken is particularly bad (various key system services will not start, with long delays during boot, login and shutdown), so let's hold back this upgrade on unsupported non-merged-/usr systems until they have completed the switch to merged-/usr and can install usr-is-merged (>= 38~). (Closes: #1054650) -- Simon McVittie Mon, 30 Oct 2023 11:51:35 + 1.14.10-2 Superseded in sid-release on 2023-10-30 dbus (1.14.10-2) unstable; urgency=low * Backport packaging changes from experimental: - Install systemd system units into /usr/lib/systemd/system. This was allowed by TC resolution #1053901. The shared library is still in /lib, for now. Build-depend on debhelper 13.11.6~ to ensure that the units are still picked up by dh_installsystemd. - Build-depend on pkgconf rather than pkg-config - dbus-x11: Don't copy XDG_SEAT_PATH, XDG_SESSION_PATH to activation environment. These variables are specific to a single login session. * d/copyright: Drop unused entry for pkg.m4. This is no longer included in the upstream source release since 1.14.6. * d/dbus-tests.lintian-overrides: Drop unused overrides. Lintian no longer flags our RUNPATH as problematic. -- Simon McVittie Wed, 25 Oct 2023 15:56:36 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/2045668/+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 2047082] Re: upgrading openssh-server always shows error: rescue-ssh.target is a disabled or a static unit not running, not starting it.
** Tags added: server-todo -- 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/2047082 Title: upgrading openssh-server always shows error: rescue-ssh.target is a disabled or a static unit not running, not starting it. Status in openssh package in Ubuntu: New Bug description: In our project we regularly build Ubuntu VM images for current 23.10 (stable). In https://github.com/cockpit-project/bots/issues/5691 we ran into an upgrade failure of openssh-server. It starts with the current cloud image and then apt upgrades it, with "DEBIAN_FRONTEND=noninteractive". openssh was updated a few days ago indeed: Setting up openssh-server (1:9.3p1-1ubuntu3.1) ... Creating SSH2 ECDSA key; this may take some time ... 256 SHA256:UqrRSpQNM7SIixVivYP/WwZRjt7Sv89P31W/Gxaf+Z8 root@ubuntu (ECDSA) Creating SSH2 ED25519 key; this may take some time ... 256 SHA256:hy9AEDydfnZeY9nf9P4Sb90kx39Oqr101A6tz5j4RQw root@ubuntu (ED25519) rescue-ssh.target is a disabled or a static unit not running, not starting it. Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145. dpkg: error processing package openssh-server (--configure): installed openssh-server package post-installation script subprocess returned error exit status 1 I.e. of course that security update itself [1] didn't introduce the regression, but earlier VM builds just didn't have a pending openssh update -- looks like this has been a luring upgrade trap in the release already. As a first naïve reproducer I tried apt update DEBIAN_FRONTEND=noninteractive apt update openssh-server on our current VM (with the release version 1:9.3p1-1ubuntu3), and that worked fine. Same with installing all 9 available packages. rescue.target is loaded/inactive/static, as it should be. Updating without DEBIAN_FRONTEND does show me a conffile prompt about /etc/ssh/sshd_config, which is justified as we do modify the config: # Allow root login with password sed -i 's/^[# ]*PermitRootLogin .*/PermitRootLogin yes/' /etc/ssh/sshd_config # Prevent SSH from hanging for a long time when no external network access echo 'UseDNS no' >> /etc/ssh/sshd_config this also leads to a merge conflict. However, I suppose all of that is tangential to the rescue-ssh.target issue. In all my interactive upgrades, it seemed to handle that just fine: Setting up openssh-server (1:9.3p1-1ubuntu3.1) ... rescue-ssh.target is a disabled or a static unit not running, not starting it. So this seems to be related to the first-time installation of openssh- server -- it is part of the cloud image, but it does the host key generation during our image builds. So reproducing this is a bit tricky, but aside from that: Why does it even do this in the first place? # Automatically added by dh_installsystemd/13.11.6ubuntu1 if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = "abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then if [ -d /run/systemd/system ]; then systemctl --system daemon-reload >/dev/null || true if [ -n "$2" ]; then _dh_action=restart else _dh_action=start fi deb-systemd-invoke $_dh_action 'rescue-ssh.target' >/dev/null || true fi fi It feels like the postinst should *never* try to start rescue- ssh.target. That's an alternative boot mode, and should never run un multi-user.target, isn't it? [1] https://launchpad.net/ubuntu/+source/openssh/1:9.3p1-1ubuntu3.1 DistroRelease: Ubuntu 23.10 PackageVersion: openssh-server 1:9.3p1-1ubuntu3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2047082/+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 2045886] Re: Please merge 8.5.0-2 into noble
The problem seems to be fixed in 8.5.0-2 by https://github.com/curl/curl/commit/fa6e123929de94064f1b1cb135f30b0a945ba399 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/2045886 Title: Please merge 8.5.0-2 into noble Status in curl package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2045886/+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 2046477] Re: Enable unprivileged user namespace restrictions by default
Can you please explain how all of this is handled during dist-upgrades?
Have all the packages with affected profiles have versioned depends
added?
Is the featured _not_ turned on during dist-upgrade from jammy hwe to
noble, but only after reboot? (as the kernel is compatible, yet during
upgrade the profiles may not be updated in the correct order)
** Changed in: apparmor (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2046477
Title:
Enable unprivileged user namespace restrictions by default
Status in apparmor package in Ubuntu:
Triaged
Bug description:
As per https://discourse.ubuntu.com/t/spec-unprivileged-user-
namespace-restrictions-via-apparmor-in-ubuntu-23-10/37626,
unprivileged user namespace restrictions for Ubuntu 23.10 are to be
enabled by default via a sysctl.d conf file in apparmor, and for that
to happen, the restrictions need to be enabled for 24.04
When the unprivileged user namespace restrictions are enabled, various
applications within and outside the Ubuntu archive fail to function,
as they use unprivileged user namespaces as part of their normal
operation.
A search of the Ubuntu archive for the 23.10 release was performed
looking for all applications that make legitimate use of the
CLONE_NEWUSER argument, the details of which can be seen in
https://docs.google.com/spreadsheets/d/1MOPVoTW0BROF1TxYqoWeJ3c6w2xKElI4w-VjdCG0m9s/edit#gid=2102562502
For each package identified in that list, an investigation was made to
determine if the application actually used this as an unprivileged
user, and if so which of the binaries within the package were
affected.
The full investigation can be seen in
https://warthogs.atlassian.net/browse/SEC-1898 (which is unfortunately
private) but is summarised to the following list of Ubuntu source
packages, as well as some out-of-archive applications that are known
to use unprivileged user namespaces.
For each of these binaries, an apparmor profile is required so that
the binary can be granted use of unprivileged user namespaces - an
example profile for the ch-run binary within the charliecloud package
is shown:
$ cat /etc/apparmor.d/ch-run
abi ,
include
profile ch-run /usr/bin/ch-run flags=(unconfined) {
userns,
# Site-specific additions and overrides. See local/README for details.
include if exists
}
However, in a few select cases, it has been decided not to ship an apparmor
profile, since this would effectively allow this mitigation to be bypassed. In
particular, the unshare and setns binaries within the util-linux package are
installed on every Ubuntu system, and allow an unprivileged user the ability to
launch an arbitrary application within a new user namespace. Any malicious
application then that wished to exploit an unprivileged user namespace to
conduct an attack on the kernel would simply need to spawn itself via `unshare
-U` or similar to be granted this permission. Therefore, due to the ubiquitous
nature of the unshare (and setns) binaries, profiles are not planned to be
provided for these by default.
Similarly, the bwrap binary within bubblewrap is also installed by default on
Ubuntu Desktop 24.04 and can also be used to launch arbitrary binaries within a
new user namespace and so no profile is planned to be provided for this either.
In Bug 2035315 new apparmor profiles were added to the apparmor
package for various applications which require unprivileged user
namespaces, using a new unconfined profile mode. They were also added
in the AppArmor upstream project.
As well as enabling the sysctl via the sysctl.d conf file, it is
proposed to add logic into the apparmor.service systemd unit to check
that the kernel supports the unconfined profile mode and that it is
enabled - and if not then to force disable the userns restrictions
sysctl via the following logic:
userns_restricted=$(sysctl -n kernel.apparmor_restrict_unprivileged_userns)
unconfined_userns=$([ -f
/sys/kernel/security/apparmor/features/policy/unconfined_restrictions/userns ]
&& cat
/sys/kernel/security/apparmor/features/policy/unconfined_restrictions/userns ||
echo 0)
if [ -n "$userns_restricted" ] && [ "$userns_restricted" -eq 1 ]; then
if [ "$unconfined_userns" -eq 0 ]; then
# userns restrictions rely on unconfined userns to be supported
echo "disabling unprivileged userns restrictions since unconfined userns
is not supported / enabled"
sysctl -w kernel.apparmor_restrict_unprivileged_userns=0
fi
fi
This allows a local admin to disable the sysctl via the regular
sysctl.d conf approach, but to also make sure we don't inadvertently
enable it when it is not supported by the kernel.
To manage notifications about this bug go to:
[Touch-packages] [Bug 2030784] Re: Backport Intel's AVX512 patches on openssl 3.0
I tested this patch set on a Zen 4 machine too and saw roughly similar speedups. And before someone asks: no, I'm not testing that on Via CPUs! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2030784 Title: Backport Intel's AVX512 patches on openssl 3.0 Status in openssl package in Ubuntu: Fix Released Bug description: https://github.com/openssl/openssl/pull/14908 https://github.com/openssl/openssl/pull/17239 These should provide a nice performance bonus on recent CPUs, and the patches are fairly self-contained. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2030784/+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 2037703] Re: dpkg-reconfigure openssh-server doesn't ask questions again
** Tags added: server-triage-discuss -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2037703 Title: dpkg-reconfigure openssh-server doesn't ask questions again Status in openssh package in Ubuntu: New Bug description: openssh-server does provide a couple of configuration options: [~]$ sudo debconf-get-selections |grep openssh-server openssh-serveropenssh-server/listenstream-may-failerror openssh-serveropenssh-server/password-authentication boolean true openssh-serveropenssh-server/permit-root-loginboolean true I want to change those options now interactively but nothing I tried worked and showed a dialog: [~]$ sudo dpkg-reconfigure -p low openssh-server Warning: Stopping ssh.service, but it can still be activated by: ssh.socket rescue-ssh.target is a disabled or a static unit not running, not starting it. [~]$ sudo dpkg-reconfigure -p low --force --frontend dialog openssh-server Warning: Stopping ssh.service, but it can still be activated by: ssh.socket rescue-ssh.target is a disabled or a static unit not running, not starting it. But the documentation (https://manpages.debian.org/testing/debconf- doc/debconf.7.en.html#Reconfiguring_packages) does state that those commands should ask those questions again. p.s. also tried with a lxc debian-sid container and had the same problem there. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: openssh-server 1:9.3p1-1ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 29 10:35:33 2023 InstallationDate: Installed on 2023-05-10 (142 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: openssh UpgradeStatus: Upgraded to mantic on 2023-07-19 (71 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2037703/+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: [SRU] Segfault in dnsmasq when using certain static domain entries + DoH (bugfix possibly exists upstream)
Verifying according to the instructions - Before the update I got this as expected: root@Jdnsmasq:~# dig A 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 ; <<>> DiG 9.18.18-0ubuntu0.22.04.1-Ubuntu <<>> A netflix.com @127.0.0.1 ;; global options: +cmd ;; no servers could be reached Jan 02 11:13:01 Jdnsmasq systemd[1]: dnsmasq.service: Main process exited, code=dumped, status=11/SEGV Jan 02 11:13:01 Jdnsmasq systemd[1]: dnsmasq.service: Failed with result 'core-dump'. --- Upgrade ... Preparing to unpack .../12-dnsmasq-base_2.86-1.1ubuntu0.4_amd64.deb ... Unpacking dnsmasq-base (2.86-1.1ubuntu0.4) over (2.86-1.1ubuntu0.3) ... Preparing to unpack .../13-dnsmasq_2.86-1.1ubuntu0.4_all.deb ... Unpacking dnsmasq (2.86-1.1ubuntu0.4) over (2.86-1.1ubuntu0.3) ... ... worked without issues --- root@Jdnsmasq:~# systemctl status dnsmasq ● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2024-01-02 11:18:03 UTC; 3s ago Process: 4327 ExecStartPre=/etc/init.d/dnsmasq checkconfig (code=exited, status=0/SUCCESS) Process: 4335 ExecStart=/etc/init.d/dnsmasq systemd-exec (code=exited, status=0/SUCCESS) Process: 4344 ExecStartPost=/etc/init.d/dnsmasq systemd-start-resolvconf (code=exited, status=0/SUCCESS) Main PID: 4343 (dnsmasq) Tasks: 1 (limit: 38247) Memory: 588.0K CPU: 45ms CGroup: /system.slice/dnsmasq.service └─4343 /usr/sbin/dnsmasq -x /run/dnsmasq/dnsmasq.pid -u dnsmasq -7 /etc/dnsmasq.d,.dpkg-dist,.dpkg-old,.dpkg-new --local-service --trust-anchor=.,20326,8,2,e06d44b80b8f1d39a95c0b0d7c65d08458e880409bb> Jan 02 11:18:03 Jdnsmasq dnsmasq[4343]: using standard nameservers for netflix.com Jan 02 11:18:03 Jdnsmasq dnsmasq[4343]: reading /etc/resolv.conf Jan 02 11:18:03 Jdnsmasq dnsmasq[4343]: using nameserver 8.8.8.8#53 Jan 02 11:18:03 Jdnsmasq dnsmasq[4343]: ignoring nameserver 127.0.0.1 - local interface Jan 02 11:18:03 Jdnsmasq dnsmasq[4343]: using standard nameservers for example.com Jan 02 11:18:03 Jdnsmasq dnsmasq[4343]: using standard nameservers for nflxext.com Jan 02 11:18:03 Jdnsmasq dnsmasq[4343]: using standard nameservers for netflix.net Jan 02 11:18:03 Jdnsmasq dnsmasq[4343]: using standard nameservers for netflix.com Jan 02 11:18:03 Jdnsmasq dnsmasq[4343]: read /etc/hosts - 7 addresses Jan 02 11:18:03 Jdnsmasq systemd[1]: Started dnsmasq - A lightweight DHCP and caching DNS server. --- Trying the issue trigger again: root@Jdnsmasq:~# dig +short -tA ubuntu.com @127.0.0.1 185.125.190.29 185.125.190.20 185.125.190.21 root@Jdnsmasq:~# dig +short -t ubuntu.com @127.0.0.1 2620:2d:4000:1::27 2620:2d:4000:1::28 2620:2d:4000:1::26 root@Jdnsmasq:~# dig A netflix.com @127.0.0.1 ; <<>> DiG 9.18.18-0ubuntu0.22.04.1-Ubuntu <<>> A netflix.com @127.0.0.1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63180 ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;netflix.com. IN A ;; ANSWER SECTION: netflix.com.60 IN A 18.200.8.190 netflix.com.60 IN A 54.155.246.232 netflix.com.60 IN A 54.73.148.110 ;; Query time: 16 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) (UDP) ;; WHEN: Tue Jan 02 11:18:36 UTC 2024 ;; MSG SIZE rcvd: 88 root@Jdnsmasq:~# dig A netflix.com @127.0.0.1 ; <<>> DiG 9.18.18-0ubuntu0.22.04.1-Ubuntu <<>> A netflix.com @127.0.0.1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29034 ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ;; QUESTION SECTION: ;netflix.com. IN A ;; ANSWER SECTION: netflix.com.52 IN A 54.73.148.110 netflix.com.52 IN A 54.155.246.232 netflix.com.52 IN A 18.200.8.190 ;; Query time: 0 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) (UDP) ;; WHEN: Tue Jan 02 11:18:44 UTC 2024 ;; MSG SIZE rcvd: 88 --- working fine now, no segfault log only has the start: Jan 02 11:18:03 Jdnsmasq dnsmasq[4343]: compile time options: IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset auth cryptohash DNSSEC loop-detect inotify dumpfile --- Setting as verified ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
[Touch-packages] [Bug 2046189] Re: Xorg freezes on external displays when in Gnome Shell on Nvidia graphics
It doesn't look like you have a working Nvidia driver installed. Please
try using the 'Additional Drivers' app to install an Nvidia driver.
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Changed in: xorg-server (Ubuntu)
Status: New => Incomplete
** Tags added: multimonitor nvidia
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2046189
Title:
Xorg freezes on external displays when in Gnome Shell on Nvidia
graphics
Status in xorg-server package in Ubuntu:
Incomplete
Bug description:
When using external displays, they randomly freeze, but the internal
display works just fine. Windows remain interactive, but frozen, on
external displays, and the cursor disappears.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: XFCE
Date: Mon Dec 11 15:14:50 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01)
(prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] TigerLake-H GT1 [UHD
Graphics] [1462:1305]
NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2520] (rev
a1) (prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] GA106M [GeForce RTX
3060 Mobile / Max-Q] [1462:1305]
InstallationDate: Installed on 2022-06-28 (531 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=70390c05-b447-4e39-b596-a9f9eb4ac62b ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/15/2021
dmi.bios.release: 1.27
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: E17K3IMS.11B
dmi.board.asset.tag: Default string
dmi.board.name: MS-17K3
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE17K3IMS.11B:bd09/15/2021:br1.27:svnMicro-StarInternationalCo.,Ltd.:pnGE76Raider11UE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17K3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17K3.1:
dmi.product.family: GE
dmi.product.name: GE76 Raider 11UE
dmi.product.sku: 17K3.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz 1:0.9.14.2+22.10.20220822-0ubuntu4
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
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/xorg-server/+bug/2046189/+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 2046116] Re: bluetooth device connected but not recognised as output device
** Tags added: regression-update -- 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/2046116 Title: bluetooth device connected but not recognised as output device Status in bluez package in Ubuntu: New Bug description: bluetooth device connected but not recognised as output device ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Dec 11 15:28:00 2023 InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 81EK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic root=UUID=6f698382-a806-46af-9a4b-472e96795c6f ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2018 dmi.bios.release: 1.28 dmi.bios.vendor: LENOVO dmi.bios.version: 7QCN28WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 530-14IKB dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvr7QCN28WW:bd08/02/2018:br1.28:efr1.28:svnLENOVO:pn81EK:pvrLenovoYOGA530-14IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA530-14IKB:skuLENOVO_MT_81EK_BU_idea_FM_YOGA530-14IKB: dmi.product.family: YOGA 530-14IKB dmi.product.name: 81EK dmi.product.sku: LENOVO_MT_81EK_BU_idea_FM_YOGA 530-14IKB dmi.product.version: Lenovo YOGA 530-14IKB dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 0C:54:15:91:FA:4F ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:83770 acl:295 sco:0 events:4208 errors:0 TX bytes:879445 acl:1667 sco:0 commands:1184 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2046116/+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 2046076] Re: cursor dissapears when I type
This is a feature of most terminals and editors. If you're typing then
they expect that hiding the mouse cursor is helpful to not cover any
text.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Invalid
--
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/2046076
Title:
cursor dissapears when I type
Status in Ubuntu:
Invalid
Bug description:
I'm using version Ubuntu 23.10 (gnome), and when I type in the default
terminal the cursor dissapears when I'm typing and I have the cursor
placed on the terminal window, this also happens when Im using
IntellyJ IDEA community
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..29.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 535.129.03 Thu Oct 19
18:56:32 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Dec 10 18:35:58 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
NVIDIA Corporation TU116 [GeForce GTX 1660 SUPER] [10de:21c4] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: ZOTAC International (MCO) Ltd. TU116 [GeForce GTX 1660 SUPER]
[19da:5527]
InstallationDate: Installed on 2023-12-10 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic
root=UUID=655899b5-3bf1-4977-87ff-935d66071b9b ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/08/2020
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.40
dmi.board.asset.tag: 229200
dmi.board.name: A320M-A PRO (MS-7C51)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: 229200
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1.40:bd12/08/2020:br5.14:svnMegaport:pn229200:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnA320M-APRO(MS-7C51):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:sku34:
dmi.product.family: 229200
dmi.product.name: 229200
dmi.product.sku: 34
dmi.product.version: 1.0
dmi.sys.vendor: Megaport
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
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/+bug/2046076/+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 1972790] Re: Can't connect to hotspot created on ubuntu
Hello, I faced the same issue. The source of the problem was that I had already used that hotspot name previously with a different device, therefore the wrong data was persisted and the connection could not be established. The solution was changing the name of the hotspot on the Android device and then establishing a new connection. Hope that helps someone. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1972790 Title: Can't connect to hotspot created on ubuntu Status in wpa package in Ubuntu: Confirmed Bug description: We currently have older systems (18.04) with hotspot's and we will migrate to 22.04. Anything work's fine, expect the hotspot. The Hotspot will be created and is visible in the WLAN-List, but if the security is set to "WPA & WPA2 Personal" we get the error message "Failed to connect to the network". If we change the Security to "WPA3 Personal" we get the error message "Invalid Password", even if the password is correct. As soon we remove the security (change it to "none"), we can connect with out any problems. We can reproduce it with a fresh installtion of the Ubuntu Server 22.04 and the following two commands: apt install network-manager nmcli c add type wifi ifname wlp3s0 con-name Hotspot autoconnect yes ssid test-ap 802-11-wireless.mode ap 802-11-wireless.band bg 802-11-wireless.mac-address "80:45:dd:f0:27:ba" wifi-sec.group ccmp wifi-sec.key-mgmt wpa-psk wifi-sec.pairwise ccmp wifi-sec.proto rsn wifi-sec.psk "test12345" ipv4.addresses 192.168.60.1/24 ipv4.method shared && nmcli connection up Hotspot We thought it could be similar to this issue: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267 Because if we test it with 20.04 it worked fine, because 20.04 uses the Version 2:2.9.0-21build1 as described in the Ticket. As @Sebastian Bacher suggested (https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/58), i created a own report. In the attachment is the requested log file. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-6 [modified: lib/systemd/system/wpa_supplicant.service] ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue May 10 07:24:15 2022 InstallationDate: Installed on 2022-05-10 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1972790/+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 2045886] Re: Please merge 8.5.0-2 into noble
** Summary changed: - Please merge 8.5.0-1 into noble + Please merge 8.5.0-2 into noble -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/2045886 Title: Please merge 8.5.0-2 into noble Status in curl package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2045886/+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 2047314] Re: tzdata 2023d release (leap-second.list expiring this week)
** Summary changed: - leap-second.list expiring this week + tzdata 2023d release (leap-second.list expiring this week) ** Description changed: - It appears the tzdata package has not been updated with the 2023d - timezone data. Current distribution is 2023c. + leap-seconds.list shipped by tzdata 2023c expired on Dec 28th 2023. - leap-seconds.list is expiring Dec 28th 2023, + The 2023d release contains the following changes: - My fix was to download and extract https://data.iana.org/time- - zones/releases/tzdata2023d.tar.gz. Then copy the included leap- - seconds.list and leapseconds files to /usr/share/zoneinfo. +Briefly: + Ittoqqortoormiit, Greenland changes time zones on 2024-03-31. + Vostok, Antarctica changed time zones on 2023-12-18. + Casey, Antarctica changed time zones five times since 2020. + Code and data fixes for Palestine timestamps starting in 2072. + A new data file zonenow.tab for timestamps starting now. + +Changes to future timestamps + + Ittoqqortoormiit, Greenland (America/Scoresbysund) joins most of + the rest of Greenland's timekeeping practice on 2024-03-31, by + changing its time zone from -01/+00 to -02/-01 at the same moment + as the spring-forward transition. Its clocks will therefore not + spring forward as previously scheduled. The time zone change + reverts to its common practice before 1981. + + Fix predictions for DST transitions in Palestine in 2072-2075, + correcting a typo introduced in 2023a. + +Changes to past and future timestamps + + Vostok, Antarctica changed to +05 on 2023-12-18. It had been at + +07 (not +06) for years. (Thanks to Zakhary V. Akulov.) + + Change data for Casey, Antarctica to agree with timeanddate.com, + by adding five time zone changes since 2020. Casey is now at +08 + instead of +11. + +Changes to past tm_isdst flags + + Much of Greenland, represented by America/Nuuk, changed its + standard time from -03 to -02 on 2023-03-25, not on 2023-10-28. + This does not affect UTC offsets, only the tm_isdst flag. + (Thanks to Thomas M. Steenholdt.) + +New data file + + A new data file zonenow.tab helps configure applications that use + timestamps dated from now on. This simplifies configuration, + since users choose from a smaller Zone set. The file's format is + experimental and subject to change. -- 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/2047314 Title: tzdata 2023d release (leap-second.list expiring this week) Status in tzdata package in Ubuntu: Triaged Bug description: leap-seconds.list shipped by tzdata 2023c expired on Dec 28th 2023. The 2023d release contains the following changes: Briefly: Ittoqqortoormiit, Greenland changes time zones on 2024-03-31. Vostok, Antarctica changed time zones on 2023-12-18. Casey, Antarctica changed time zones five times since 2020. Code and data fixes for Palestine timestamps starting in 2072. A new data file zonenow.tab for timestamps starting now. Changes to future timestamps Ittoqqortoormiit, Greenland (America/Scoresbysund) joins most of the rest of Greenland's timekeeping practice on 2024-03-31, by changing its time zone from -01/+00 to -02/-01 at the same moment as the spring-forward transition. Its clocks will therefore not spring forward as previously scheduled. The time zone change reverts to its common practice before 1981. Fix predictions for DST transitions in Palestine in 2072-2075, correcting a typo introduced in 2023a. Changes to past and future timestamps Vostok, Antarctica changed to +05 on 2023-12-18. It had been at +07 (not +06) for years. (Thanks to Zakhary V. Akulov.) Change data for Casey, Antarctica to agree with timeanddate.com, by adding five time zone changes since 2020. Casey is now at +08 instead of +11. Changes to past tm_isdst flags Much of Greenland, represented by America/Nuuk, changed its standard time from -03 to -02 on 2023-03-25, not on 2023-10-28. This does not affect UTC offsets, only the tm_isdst flag. (Thanks to Thomas M. Steenholdt.) New data file A new data file zonenow.tab helps configure applications that use timestamps dated from now on. This simplifies configuration, since users choose from a smaller Zone set. The file's format is experimental and subject to change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2047314/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 2030977] Re: icu data files shipped in tzdata source package are generated and miss original form
** Changed in: tzdata (Ubuntu) Importance: Undecided => High -- 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/2030977 Title: icu data files shipped in tzdata source package are generated and miss original form Status in tzdata package in Ubuntu: New Bug description: The tzdata source packages ships four files in debian/icu that are not built from source: ``` $ grep -i generated debian/icu/* debian/icu/metaZones.txt:// Generated using tools/cldr/cldr-to-icu/build-icu-data.xml debian/icu/timezoneTypes.txt:// Generated using tools/cldr/cldr-to-icu/build-icu-data.xml debian/icu/windowsZones.txt:// Generated using tools/cldr/cldr-to-icu/build-icu-data.xml debian/icu/zoneinfo64.txt:// >> !!! >> THIS IS A MACHINE-GENERATED FILE << !!! << ``` They're not considered as the preferred form of modification. Please replace them with the original form and generate them with tools/cldr/cldr-to-icu/build-icu-data.xml during package build. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2030977/+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 1642112] Re: Can’t connect to the second BT device successfully
Nicolas, this bug was reported over 7 years ago against an Ubuntu version that will reach end of life in a few months. I suggest to keep your issue alive that it should be reported as a new bug. ** Tags added: trusty -- 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/1642112 Title: Can’t connect to the second BT device successfully Status in bluez package in Ubuntu: New Bug description: OS: 14.04 bluez version: 4.x After first bt device(eg. mouse) connected, try to connect second device(eg. keyboard), found it has no function when connected, and sometimes it fails to connect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1642112/+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
