[Desktop-packages] [Bug 2043956] Re: gnome-shell crashed with SIGSEGV in __GI_getenv("EXPAT_ENTROPY_DEBUG") from getDebugLevel() from ENTROPY_DEBUG() from generate_hash_secret_salt() from startParsing
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2043956
Title:
gnome-shell crashed with SIGSEGV in __GI_getenv("EXPAT_ENTROPY_DEBUG")
from getDebugLevel() from ENTROPY_DEBUG() from
generate_hash_secret_salt() from startParsing()
Status in gnome-shell package in Ubuntu:
Confirmed
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-shell. This problem was most recently seen with package version
45.0-1ubuntu2, the problem page at
https://errors.ubuntu.com/problem/080d61cb7dd904bc62db89c3c56f38a66fc8754a
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2043956/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2047629] Re: gnome-shell crashed with SIGSEGV in __GI_getenv()
*** This bug is a duplicate of bug 2043956 ***
https://bugs.launchpad.net/bugs/2043956
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2043956, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.
** This bug has been marked a duplicate of bug 2043956
gnome-shell crashed with SIGSEGV in __GI_getenv("EXPAT_ENTROPY_DEBUG") from
getDebugLevel() from ENTROPY_DEBUG() from generate_hash_secret_salt() from
startParsing()
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2047629
Title:
gnome-shell crashed with SIGSEGV in __GI_getenv()
Status in gnome-shell package in Ubuntu:
New
Bug description:
Just started, no applications active
ProblemType: Crash
DistroRelease: Ubuntu 24.04
Package: gnome-shell 45.2-1ubuntu1
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: pass
CurrentDesktop: GNOME-Greeter:GNOME
Date: Thu Dec 28 08:28:30 2023
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
InstallationDate: Installed on 2023-12-10 (18 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20231210)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/false
XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 45.2-3ubuntu1
SegvAnalysis:
Segfault happened at: 0x7f8199c45e5d <__GI_getenv+77>: cmp
(%rbx),%r12b
PC (0x7f8199c45e5d) ok
source "(%rbx)" (0x5596cecb6618) not located in a known VMA region (needed
readable region)!
destination "%r12b" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
__GI_getenv (name=0x7f81962d5e5a "EXPAT_ENTROPY_DEBUG") at
./stdlib/getenv.c:31
?? () from /lib/x86_64-linux-gnu/libexpat.so.1
?? () from /lib/x86_64-linux-gnu/libexpat.so.1
XML_ParseBuffer () from /lib/x86_64-linux-gnu/libexpat.so.1
?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1
Title: gnome-shell crashed with SIGSEGV in __GI_getenv()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2047629/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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 44 24 18 31
[Desktop-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 Desktop Packages, which is subscribed to mutter 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:
[Desktop-packages] [Bug 2047144] Re: Black screen stays forever after inactivity
Next time the bug occurs, please reboot and then run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter 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:
[Desktop-packages] [Bug 2047146] Re: Issues Encountered with Ubuntu 23.10 - Icon Minimization and Full-Screen App Behavior
Please provide a screenshot or photo of the problem so we have a better idea of where to direct the bug. ** Tags added: mantic ** Package changed: gnome-desktop (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2047146 Title: Issues Encountered with Ubuntu 23.10 - Icon Minimization and Full- Screen App Behavior Status in Ubuntu: Incomplete Bug description: # System Details Report --- ## Report details - **Date generated:** 2023-12-21 14:00:57 ## Hardware Information: - **Hardware Model:** ASUSTeK COMPUTER INC. N552VW - **Memory:** 32,0 GiB - **Processor:** Intel® Core™ i7-6700HQ × 8 - **Graphics:**NVIDIA GeForce GTX 960M - **Graphics 1:** NVIDIA GeForce GTX 960M - **Disk Capacity:** 1,5 TB ## Software Information: - **Firmware Version:**N552VW.304 - **OS Name:** Ubuntu 23.10 - **OS Build:**(null) - **OS Type:** 64-bit - **GNOME Version:** 45.1 - **Windowing System:**X11 - **Kernel Version:** Linux 6.5.0-14-generic Dear Ubuntu Development Team, I recently managed to install the Ubuntu image with the kernel version 6.6.7. Before installing Ubuntu 23.10, I noticed logs related to the configuration of the Linux 6.6.7 kernel, which, however, did not boot successfully on my system. After successfully installing Ubuntu 23.10, I removed the newly installed 6.6.7 kernel and reverted to a more stable version of the kernel (version 6) that boots without any issues. However, I've encountered a unique problem post-installation. When I minimize applications, their icons appear in the upper right corner of the horizontal toolbar as expected. However, the mouse cursor behaves oddly around these icons. Even if I move the cursor slightly away from an icon (about a hundred pixels or so), and click on an area of the desktop (not on the toolbar itself), it unexpectedly activates the corresponding minimized application. This issue, which did not occur before, is not urgent but becomes increasingly inconvenient over time. Furthermore, in certain applications like Spotify, I sometimes encounter another issue where the window control buttons (close, maximize, minimize) disappear, and the application enters a full-screen mode, akin to a video game. This behavior seems sporadic, and I'm unsure how to consistently resolve it. Could these issues be related to screen settings or other system configurations? Also, is the full-screen behavior a known bug? Any guidance on avoiding or rectifying these problems would be greatly appreciated. Thank you for your attention to these matters. Best regards, Luigi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2047146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046847] Re: Ubuntu Desktop fails to login with Active Directory credentials on arm64 systems
** Package changed: gdm (Ubuntu) => gdm3 (Ubuntu) ** Tags added: ad arm64 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2046847 Title: Ubuntu Desktop fails to login with Active Directory credentials on arm64 systems Status in gdm3 package in Ubuntu: New Bug description: When attempting to log in to an Ubuntu Desktop session on ARM64 systems using Active Directory credentials. User login will fail and dump the user back to the login prompt. Login with local accounts work. Authentication checks succeed in logs. The Active Directory users are added, but login still fails. This issue has been seen on a Xilinx system and replicated using a Raspberry Pi 4. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2046847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046808] Re: Screencast app crashes after recording is stopped
That might be an amdgpu-specific issue. Sadly it doesn't seem common enough to show up in the top 100 gjs crashes for 22.04: https://errors.ubuntu.com/?release=Ubuntu%2022.04=gjs=month It sounds like this bug though: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6747 which is fixed in mutter 45.1 and later. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #6747 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6747 ** Tags added: amdgpu ** Summary changed: - Screencast app crashes after recording is stopped + [amdgpu] Screencast app crashes after recording is stopped -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2046808 Title: [amdgpu] Screencast app crashes after recording is stopped Status in gnome-shell package in Ubuntu: New Bug description: Every time I try to record a screencast via the built-in feature triggered by Ctrl+Alft+Shift+R, it starts recording successfully but when I click the stop button, the recording stops and nothing is saved to ~/Videos/Screencasts. This happens with both Wayland and Xorg sessions. Here are the relevant journal records: dbus-daemon[101710]: [session uid=1000 pid=101710] Activating service name='org.gnome.Shell.Screencast' requested by ':1.29' (uid=1000 pid=101851 comm="/usr/bin/gnome-shell " label="unconfined") dbus-daemon[101710]: [session uid=1000 pid=101710] Successfully activated service 'org.gnome.Shell.Screencast' kernel: gjs[109549]: segfault at 8 ip 7f915005edf6 sp 7ffcd2710130 error 4 in libgstpipewire.so[7f915004e000+14000] kernel: Code: 50 48 8d 15 93 44 00 00 31 c0 41 b8 bc 04 00 00 48 8d 0d 3d 52 00 00 be 05 00 00 00 e8 73 06 ff ff 58 5a 48 8b 85 00 03 00 00 <48> 8b 78 08 e8 81 0e ff ff 48 8b 85 00 03 00 00 31 f6 c7 85 e4 02 gnome-shell[101851]: D-Bus client with active sessions vanished gnome-shell[101851]: Error stopping screencast: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-91.101-generic 5.15.131 Uname: Linux 5.15.0-91-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Dec 18 19:28:49 2023 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2018-03-17 (2101 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316) RelatedPackageVersions: mutter-common 42.9-0ubuntu5 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-06-02 (563 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2046808/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046847] [NEW] Ubuntu Desktop fails to login with Active Directory credentials on arm64 systems
You have been subscribed to a public bug: When attempting to log in to an Ubuntu Desktop session on ARM64 systems using Active Directory credentials. User login will fail and dump the user back to the login prompt. Login with local accounts work. Authentication checks succeed in logs. The Active Directory users are added, but login still fails. This issue has been seen on a Xilinx system and replicated using a Raspberry Pi 4. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New -- Ubuntu Desktop fails to login with Active Directory credentials on arm64 systems https://bugs.launchpad.net/bugs/2046847 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046798] Re: Ubuntu Wayland does not support 21:9 monitor
That's odd because 3440x1440 actually has lower bandwidth requirements (fewer pixels) than 3840x2160. Still, to go above 60Hz you will need both your HDMI cable and your graphics card to be capable of HDMI 2.1, not just 2.0. Please tell us the model of graphics card you are using. If you're just using the integrated graphics of the Intel i7--1255U chip then I'm not sure that can do it with HDMI. DisplayPort looks more certain to work (you may need a USB-C to DisplayPort cable for that). Please also run this so we can see the modes that the kernel driver believes are possible: sudo apt install drm-info drm_info > drminfo.txt and attach the resulting text file here. ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2046798 Title: Ubuntu Wayland does not support 21:9 monitor Status in mutter package in Ubuntu: Incomplete Bug description: My second monitor attached to HDMI of my Lenovo V15 is DELL S3422DWG and has aspect 21:9 with resolution 3440x1440, with supported resfresh at 100Hz. I could not set native resolution on my second HDMI DELL S3422DWG in any way. I tried cvt, modeset, passing boot parameters to grub, porting EDID from Windows 10 to custom EDID with grub parameters. Every one move ended up with 4k resolution 3840x2160(16:9). And I saw a lot of similar reports on unresolved 21:9 issue on reddit, stackoverflow etc. Kind regards. --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2023-11-01 (49 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) Package: mutter 45.2-0ubuntu1 PackageArchitecture: amd64 ProcEnviron: LANG=ru_RU.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Tags: mantic wayland-session Uname: Linux 6.5.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2046798/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop
Packages, which is subscribed to xorg-server 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-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
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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046189] Re: Xorg freezes on external displays when in Gnome Shell on Nvidia graphics
The attached files show that the kernel does indeed have an 'nvidia'
driver but it's not being used for some reason. And Xorg, as of Dec 11
at least, does not have any knowledge of an Nvidia card.
Please run:
lspci -k > lspci.txt
journalctl -b0 > journal.txt
and attach the resulting text files here so we can see more up to date
information.
Please also open the 'Additional Drivers' app and verify that it shows
an Nvidia driver is currently in use.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043027] Re: Wacom Intuos S stop working after upgrading to Ubuntu 23.10
Oh that explain why it stopped working again
:(
I guess I have to full reinstall 22.04 again in order to be able to
work.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2043027
Title:
Wacom Intuos S stop working after upgrading to Ubuntu 23.10
Status in mutter package in Ubuntu:
Fix Released
Status in mutter source package in Mantic:
In Progress
Bug description:
Impact
--
Clicking does not work correctly with Wacom tablets in the Ubuntu/GNOME X11
sessions
Test Case
-
One of the people affected by this issue will verify whether their Wacom
tablet is working noticably better with the upgraded Mutter packages
What Could Go Wrong
---
The fix for this issue is included in upstream's mutter 45.2 release so
please see bug 2043000 as the master bug for this upgrade
Original Bug Report
---
Tablet seems to work until I open Krita (as I could read on Internet, it may
be related with Qt Apps).
When Krita is open, mouse movement works ok with the tablet, but when
it comes to click action it doesn't work and any further action with
mouse is not captured (even outside Krita!).
To regain control of the mouse I have to Alt+Tab and then I can click
again.
Some details that may be handy:
- I've got two monitors
- Maybe Qt apps related
- My graphic card is nVidia GTX 1060 6Gb, driver used nvidia-driver-535
Thanks for your effort. I love Ubuntu!
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-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..06.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] Permiso denegado: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 8 17:20:34 2023
DistUpgraded: 2023-11-08 00:54:28,961 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
nvidia/535.129.03, 6.2.0-36-generic, x86_64: installed (WARNING! Diff
between built and installed module!) (WARNING! Diff between built and installed
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff
between built and installed module!) (WARNING! Diff between built and installed
module!)
nvidia/535.129.03, 6.5.0-10-generic, x86_64: installed (WARNING! Diff
between built and installed module!) (WARNING! Diff between built and installed
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff
between built and installed module!) (WARNING! Diff between built and installed
module!)
virtualbox/7.0.10, 6.2.0-36-generic, x86_64: installed
virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 6GB]
[19da:1438]
InstallationDate: Installed on 2022-04-09 (578 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=9dd904a0-11bb-40fa-9fe8-2f10449a416c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-11-07 (1 days ago)
dmi.bios.date: 06/15/2020
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0608
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING B550-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0608:bd06/15/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGB550-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name:
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2018316] Re: wireplumber sometime segfault on bluez devices disconnect
This bug was fixed in the package pipewire - 0.3.65-3ubuntu1 --- pipewire (0.3.65-3ubuntu1) lunar; urgency=medium * debian/patches/git_bluez_disconnect.patch: - cherry pick a patch to fix wireplumber segfaulting sometime on bluez devices disconnect (lp: #2018316) -- Sebastien Bacher Tue, 02 May 2023 17:56:31 +0200 ** Changed in: pipewire (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/2018316 Title: wireplumber sometime segfault on bluez devices disconnect Status in PipeWire: Fix Released Status in pipewire package in Ubuntu: Fix Released Status in pipewire source package in Jammy: Confirmed Status in pipewire source package in Lunar: Fix Released Bug description: * Impact wireplumber sometime segfault on bluez devices disconnect leading to non working pipewire audio * Test case Connect and disconnect bluetooth audio devices and ensure wireplumber/pipewire-pulse don't hit an error and sound keeps working in the desktop (sound settings testsound, rhythmbox, firefox playing video) and check that error reports stop on https://errors.ubuntu.com/problem/a1b673a5eb264d829f8851e55351dec64a517f53 * Regression potential The change is in the pipewire bluez plugin so the testing should focus on bluetooth audio devices To manage notifications about this bug go to: https://bugs.launchpad.net/pipewire/+bug/2018316/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038951] Re: Welcome To Ubuntu application not in specified language after installing offline.
** Changed in: gnome-initial-setup (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/2038951 Title: Welcome To Ubuntu application not in specified language after installing offline. Status in gnome-initial-setup package in Ubuntu: New Bug description: I installed in swedish with no internet connection, and after the install completed and rebooted, everything was in swedish except the Welcome To Ubuntu application. This is not the case with an installation with internet access. --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2023-10-10 (0 days ago) InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64 (20231010) Package: ubiquity (not installed) ProcEnviron: LANG=sv_SE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Tags: mantic wayland-session ubiquity-23.10.8 Uname: Linux 6.5.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2038951/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039475] Re: Desktop icons in Mantic doesn't honor dock margins
This bug was fixed in the package gnome-shell-extension-desktop-icons-ng - 46+really47.0.7-0ubuntu1 --- gnome-shell-extension-desktop-icons-ng (46+really47.0.7-0ubuntu1) mantic; urgency=medium * New upstream release - Fix regression that allowed desktop icons to be placed under autohidden Dock (LP: #2039475) -- Sergio Costas Rodriguez Wed, 18 Oct 2023 10:04:14 -0400 ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons-ng in Ubuntu. https://bugs.launchpad.net/bugs/2039475 Title: Desktop icons in Mantic doesn't honor dock margins Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons-ng source package in Mantic: Fix Released Bug description: [Impact] The port to Gnome Shell 45 of Desktop Icons had a bug that prevents it from honoring the Dock size when in "IntelliHide" mode, thus allowing to put icons under it. It has been fixed in upstream by fixing in DING the implementation of the protocol that allows other extensions (like Dash-to-dock, Dash-to-panel, Hide-top-bar and more) to notify DING which zones are being used by them and thus allow to avoid putting icons there, which would be unreachable when the panel/dock/bar are visible. [Test plan] Go to the extensions properties of Dash-to-dock or Ubuntu-dock and ensure that the "IntelliHide" option (which hides the dock when a window is below it, and shows it again when there's only "empty desktop" below it) is ENABLED, the option "panel mode: extend up to the screen borders" is DISABLED, and the "maximum size of the dock" is BELOW 100% (90% is fine). In an empty desktop (this is, without any window) the dock should be visible, with some free space in each side (top and bottom if the dock is vertical; left and right if it is horizontal) where the underlying desktop can be seen. Now, open any window and maximize it; the dock should hide, thus allowing the window to fill the whole screen. Close the window. The dock should appear again. Try to move a desktop icon (any icon; a folder, a file, the trash, the personal folder... any is right) into the free zone of any of the sides. If the patch works, it should NOT be possible to place the icon there; if the bug is present, then it will be possible to place the icon there. It must be also test if it is possible to put an icon in any place of the "free" desktop surface (this is: any zone that won't be obscured by a bar, dock or panel). [Where problems could occur] If there are problems, they can show in several ways: - the bugfix doesn't work, and thus it will still be possible to put icons in zones that should be forbidden - DING might fail and no icons would be visible - DING might wrongly interpret the data sent by other extensions, reducing too much the usable zone. [ Other info ] It seems easiest to take the new upstream release (47.0.5 -> 47.0.7) which includes this single code commit, plus translation updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/2039475/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040488] Update Released
The verification of the Stable Release Update for udisks2 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 Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/2040488 Title: loading lvm2 module crashes: udisks_module_lvm2_new: assertion 'UDISKS_IS_DAEMON (daemon)' failed Status in udisks2 package in Ubuntu: Fix Released Status in udisks2 source package in Mantic: Fix Released Bug description: [Impact] Trying to load the lvm2 module crashes udisks immediately: busctl call org.freedesktop.UDisks2 /org/freedesktop/UDisks2/Manager org.freedesktop.UDisks2.Manager EnableModule sb lvm2 true udisksd[5709]: cannot register existing type 'UDisksDaemon' udisksd[5709]: g_once_init_leave: assertion 'result != 0' failed udisksd[5709]: udisks_module_lvm2_new: assertion 'UDISKS_IS_DAEMON (daemon)' failed systemd[1]: Started systemd-coredump@2-5767-0.service - Process Core Dump (PID 5767/UID 0). Module libudev.so.1 from deb systemd-253.5-1ubuntu6.amd64 Module libsystemd.so.0 from deb systemd-253.5-1ubuntu6.amd64 Stack trace of thread 5709: #0 0x56079be701ad udisks_module_manager_load_modules (udisksd + 0x601ad) #1 0x56079be5fdf5 n/a (udisksd + 0x4fdf5) #2 0x7f7d5f122a11 n/a (libglib-2.0.so.0 + 0x5aa11) #3 0x7f7d5f17e46f n/a (libglib-2.0.so.0 + 0xb646f) #4 0x7f7d5f12346f g_main_loop_run (libglib-2.0.so.0 + 0x5b46f) #5 0x56079be323d2 main (udisksd + 0x223d2) #6 0x7f7d5ee280d0 __libc_start_call_main (libc.so.6 + 0x280d0) #7 0x7f7d5ee28189 __libc_start_main_impl (libc.so.6 + 0x28189) #8 0x56079be324f5 _start (udisksd + 0x224f5) This breaks at least cockpit, and possibly other consumers of udisks (GNOME Disks perhaps?). This is a regression in mantic, earlier releases were fine. [Test Plan] The above reproducer confirms the check. The busctl command should succeed, and afterwards `systemctl status udisks2` should still be "active (running)" instead of "failed". autopkgtests should take care of regression testing, and they were happy with the noble update. I'm also happy to run cockpit's integration tests against the updated version; it exercises udisks2 thoroughly (and we find lots of bugs with it). At the moment we don't test 23.10 mantic at all, because it is so broken (https://github.com/cockpit-project/bots/pull/5432). [Where problems could occur] Changing the linker options is quite invasive. The autopkgtests cover the runtime functionality though, and as modules are currently 100% broken they can't possibly get any worse. [Other info] Fix committed to Debian: https://salsa.debian.org/utopia- team/udisks2/-/commit/e22881abdd90bd4878add165ccc46008a17163f8 Noble debdiff: http://launchpadlibrarian.net/701038246/udisks2_2.10.1-1ubuntu1_2.10.1-1ubuntu2.diff.gz ProblemType: Crash Architecture: amd64 Date: Wed Oct 25 12:13:14 2023 DistroRelease: Ubuntu 23.10 ExecutablePath: /usr/libexec/udisks2/udisksd Package: udisks2 2.10.1-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/2040488/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040488] Re: loading lvm2 module crashes: udisks_module_lvm2_new: assertion 'UDISKS_IS_DAEMON (daemon)' failed
This bug was fixed in the package udisks2 - 2.10.1-1ubuntu1.1 --- udisks2 (2.10.1-1ubuntu1.1) mantic-proposed; urgency=medium * Don't build with -Wl,-Bsymbolic-functions. It breaks module loading, as it confuses GObject's type loading cache: "cannot register existing type 'UDisksDaemon'". (Patch also applied to Debian packaging git, can be synced next time). (LP: #2040488) -- Martin Pitt Tue, 05 Dec 2023 11:25:08 + ** Changed in: udisks2 (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/2040488 Title: loading lvm2 module crashes: udisks_module_lvm2_new: assertion 'UDISKS_IS_DAEMON (daemon)' failed Status in udisks2 package in Ubuntu: Fix Released Status in udisks2 source package in Mantic: Fix Released Bug description: [Impact] Trying to load the lvm2 module crashes udisks immediately: busctl call org.freedesktop.UDisks2 /org/freedesktop/UDisks2/Manager org.freedesktop.UDisks2.Manager EnableModule sb lvm2 true udisksd[5709]: cannot register existing type 'UDisksDaemon' udisksd[5709]: g_once_init_leave: assertion 'result != 0' failed udisksd[5709]: udisks_module_lvm2_new: assertion 'UDISKS_IS_DAEMON (daemon)' failed systemd[1]: Started systemd-coredump@2-5767-0.service - Process Core Dump (PID 5767/UID 0). Module libudev.so.1 from deb systemd-253.5-1ubuntu6.amd64 Module libsystemd.so.0 from deb systemd-253.5-1ubuntu6.amd64 Stack trace of thread 5709: #0 0x56079be701ad udisks_module_manager_load_modules (udisksd + 0x601ad) #1 0x56079be5fdf5 n/a (udisksd + 0x4fdf5) #2 0x7f7d5f122a11 n/a (libglib-2.0.so.0 + 0x5aa11) #3 0x7f7d5f17e46f n/a (libglib-2.0.so.0 + 0xb646f) #4 0x7f7d5f12346f g_main_loop_run (libglib-2.0.so.0 + 0x5b46f) #5 0x56079be323d2 main (udisksd + 0x223d2) #6 0x7f7d5ee280d0 __libc_start_call_main (libc.so.6 + 0x280d0) #7 0x7f7d5ee28189 __libc_start_main_impl (libc.so.6 + 0x28189) #8 0x56079be324f5 _start (udisksd + 0x224f5) This breaks at least cockpit, and possibly other consumers of udisks (GNOME Disks perhaps?). This is a regression in mantic, earlier releases were fine. [Test Plan] The above reproducer confirms the check. The busctl command should succeed, and afterwards `systemctl status udisks2` should still be "active (running)" instead of "failed". autopkgtests should take care of regression testing, and they were happy with the noble update. I'm also happy to run cockpit's integration tests against the updated version; it exercises udisks2 thoroughly (and we find lots of bugs with it). At the moment we don't test 23.10 mantic at all, because it is so broken (https://github.com/cockpit-project/bots/pull/5432). [Where problems could occur] Changing the linker options is quite invasive. The autopkgtests cover the runtime functionality though, and as modules are currently 100% broken they can't possibly get any worse. [Other info] Fix committed to Debian: https://salsa.debian.org/utopia- team/udisks2/-/commit/e22881abdd90bd4878add165ccc46008a17163f8 Noble debdiff: http://launchpadlibrarian.net/701038246/udisks2_2.10.1-1ubuntu1_2.10.1-1ubuntu2.diff.gz ProblemType: Crash Architecture: amd64 Date: Wed Oct 25 12:13:14 2023 DistroRelease: Ubuntu 23.10 ExecutablePath: /usr/libexec/udisks2/udisksd Package: udisks2 2.10.1-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/2040488/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040488] Re: loading lvm2 module crashes: udisks_module_lvm2_new: assertion 'UDISKS_IS_DAEMON (daemon)' failed
The autopkgtests for udisks2 did run for mantic they are just not appearing in the excuses report for unknown reasons. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/2040488 Title: loading lvm2 module crashes: udisks_module_lvm2_new: assertion 'UDISKS_IS_DAEMON (daemon)' failed Status in udisks2 package in Ubuntu: Fix Released Status in udisks2 source package in Mantic: Fix Released Bug description: [Impact] Trying to load the lvm2 module crashes udisks immediately: busctl call org.freedesktop.UDisks2 /org/freedesktop/UDisks2/Manager org.freedesktop.UDisks2.Manager EnableModule sb lvm2 true udisksd[5709]: cannot register existing type 'UDisksDaemon' udisksd[5709]: g_once_init_leave: assertion 'result != 0' failed udisksd[5709]: udisks_module_lvm2_new: assertion 'UDISKS_IS_DAEMON (daemon)' failed systemd[1]: Started systemd-coredump@2-5767-0.service - Process Core Dump (PID 5767/UID 0). Module libudev.so.1 from deb systemd-253.5-1ubuntu6.amd64 Module libsystemd.so.0 from deb systemd-253.5-1ubuntu6.amd64 Stack trace of thread 5709: #0 0x56079be701ad udisks_module_manager_load_modules (udisksd + 0x601ad) #1 0x56079be5fdf5 n/a (udisksd + 0x4fdf5) #2 0x7f7d5f122a11 n/a (libglib-2.0.so.0 + 0x5aa11) #3 0x7f7d5f17e46f n/a (libglib-2.0.so.0 + 0xb646f) #4 0x7f7d5f12346f g_main_loop_run (libglib-2.0.so.0 + 0x5b46f) #5 0x56079be323d2 main (udisksd + 0x223d2) #6 0x7f7d5ee280d0 __libc_start_call_main (libc.so.6 + 0x280d0) #7 0x7f7d5ee28189 __libc_start_main_impl (libc.so.6 + 0x28189) #8 0x56079be324f5 _start (udisksd + 0x224f5) This breaks at least cockpit, and possibly other consumers of udisks (GNOME Disks perhaps?). This is a regression in mantic, earlier releases were fine. [Test Plan] The above reproducer confirms the check. The busctl command should succeed, and afterwards `systemctl status udisks2` should still be "active (running)" instead of "failed". autopkgtests should take care of regression testing, and they were happy with the noble update. I'm also happy to run cockpit's integration tests against the updated version; it exercises udisks2 thoroughly (and we find lots of bugs with it). At the moment we don't test 23.10 mantic at all, because it is so broken (https://github.com/cockpit-project/bots/pull/5432). [Where problems could occur] Changing the linker options is quite invasive. The autopkgtests cover the runtime functionality though, and as modules are currently 100% broken they can't possibly get any worse. [Other info] Fix committed to Debian: https://salsa.debian.org/utopia- team/udisks2/-/commit/e22881abdd90bd4878add165ccc46008a17163f8 Noble debdiff: http://launchpadlibrarian.net/701038246/udisks2_2.10.1-1ubuntu1_2.10.1-1ubuntu2.diff.gz ProblemType: Crash Architecture: amd64 Date: Wed Oct 25 12:13:14 2023 DistroRelease: Ubuntu 23.10 ExecutablePath: /usr/libexec/udisks2/udisksd Package: udisks2 2.10.1-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/2040488/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2045056] Update Released
The verification of the Stable Release Update for gnome-characters 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 Desktop Packages, which is subscribed to gnome-characters in Ubuntu. https://bugs.launchpad.net/bugs/2045056 Title: Update the Characters app for Unicode 15.1 Status in gnome-characters package in Ubuntu: Fix Released Status in gnome-characters source package in Mantic: Fix Released Bug description: Impact -- This adds one new feature: new emoji and Unicode characters from Unicode 15.1 for easier browsing, selecting, and copying. Prerequisite Install fonts-noto-color-emoji 2.041 . See LP: #2045043 Make sure the Characters app is not running and wait a few seconds for it to finish closing in the background. Test Case 1 --- Install the update Open the Characters app. Select an emoji character and click Copy Character Paste the emoji somewhere. You should see the emoji you pasted. Test Case 2 --- Open the Characters app. Use the search feature to search for "phoenix" A phoenix emoji should show up. This is one of the new Emoji 15. https://blog.emojipedia.org/whats-new-in-unicode-15-1-and-emoji-15-1/ What Could Go Wrong --- GNOME Characters is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME It is installed by default in Ubuntu Desktop, Edubuntu, Ubuntu Budgie, and Ubuntu Cinnamon. However, a bug in this app should not impact anything else on the system. Other Info -- The GNOME Characters app in Ubuntu 22.04 LTS uses a different mechanism to display emoji and does not support any emoji from recent years. The update to enable recent emoji is entangled with the switch to GTK4 and Ubuntu Budgie has requested that we not switch any apps to GTK4 for Ubuntu 22.04 LTS. Therefore, this update is only for Ubuntu 23.10. This particular change was proposed upstream but was not merged because at the time it was proposed, Google had yet to update the color emoji font. I expect it to be merged "soon", but it seems better for our users to not wait until then. https://gitlab.gnome.org/GNOME/gnome-characters/-/merge_requests/110 === Note to SRU team This update can be accepted into mantic-proposed now, but let's wait to push it to mantic-updates until after fonts-noto-color-emoji is fully phased. It is a minor detail but this would prevent a few broken emoji sequences from temporarily showing in the app. For instance, phoenix would be represented as bird+fire. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-characters/+bug/2045056/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2045056] Re: Update the Characters app for Unicode 15.1
This bug was fixed in the package gnome-characters - 45.0-1ubuntu1 --- gnome-characters (45.0-1ubuntu1) mantic; urgency=medium * Cherry-pick proposed patch for Unicode 15.1 updates (LP: #2045056) -- Jeremy Bícha Tue, 28 Nov 2023 15:16:44 -0500 ** Changed in: gnome-characters (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-characters in Ubuntu. https://bugs.launchpad.net/bugs/2045056 Title: Update the Characters app for Unicode 15.1 Status in gnome-characters package in Ubuntu: Fix Released Status in gnome-characters source package in Mantic: Fix Released Bug description: Impact -- This adds one new feature: new emoji and Unicode characters from Unicode 15.1 for easier browsing, selecting, and copying. Prerequisite Install fonts-noto-color-emoji 2.041 . See LP: #2045043 Make sure the Characters app is not running and wait a few seconds for it to finish closing in the background. Test Case 1 --- Install the update Open the Characters app. Select an emoji character and click Copy Character Paste the emoji somewhere. You should see the emoji you pasted. Test Case 2 --- Open the Characters app. Use the search feature to search for "phoenix" A phoenix emoji should show up. This is one of the new Emoji 15. https://blog.emojipedia.org/whats-new-in-unicode-15-1-and-emoji-15-1/ What Could Go Wrong --- GNOME Characters is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME It is installed by default in Ubuntu Desktop, Edubuntu, Ubuntu Budgie, and Ubuntu Cinnamon. However, a bug in this app should not impact anything else on the system. Other Info -- The GNOME Characters app in Ubuntu 22.04 LTS uses a different mechanism to display emoji and does not support any emoji from recent years. The update to enable recent emoji is entangled with the switch to GTK4 and Ubuntu Budgie has requested that we not switch any apps to GTK4 for Ubuntu 22.04 LTS. Therefore, this update is only for Ubuntu 23.10. This particular change was proposed upstream but was not merged because at the time it was proposed, Google had yet to update the color emoji font. I expect it to be merged "soon", but it seems better for our users to not wait until then. https://gitlab.gnome.org/GNOME/gnome-characters/-/merge_requests/110 === Note to SRU team This update can be accepted into mantic-proposed now, but let's wait to push it to mantic-updates until after fonts-noto-color-emoji is fully phased. It is a minor detail but this would prevent a few broken emoji sequences from temporarily showing in the app. For instance, phoenix would be represented as bird+fire. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-characters/+bug/2045056/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973812] Re: i cannot install package libenchant1c2a. It is not available on ubuntu 22.04 LTS. It is necessary for software 1C Enterprise. Please help me to install it!!!
Sorry, Ubuntu 22.04 LTS will only include one version of the enchant library. I suggest asking your vendor to update their software to support Ubuntu 22.04 LTS. They might find the Snap format interesting since it allows for easier distribution to all Ubuntu users (or even non-Ubuntu users). ** Changed in: enchant-2 (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to enchant-2 in Ubuntu. https://bugs.launchpad.net/bugs/1973812 Title: i cannot install package libenchant1c2a. It is not available on ubuntu 22.04 LTS. It is necessary for software 1C Enterprise. Please help me to install it!!! Status in enchant-2 package in Ubuntu: Won't Fix Bug description: i cannot install package libenchant1c2a. It is not available on ubuntu 22.04 LTS. It is necessary for software 1C Enterprise. Please help me to install it!!! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/enchant-2/+bug/1973812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2047818] Re: Only shows snaps
This is related: https://bugs.launchpad.net/ubuntu/+source/gnome- software/+bug/1992498 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2047818 Title: Only shows snaps Status in gnome-software package in Ubuntu: New Status in gnome-software package in Debian: Unknown Bug description: Hi, Noble up to date, GNOME Software 45.2 Does only show snaps in search results. Example: - search for "xournal" - search result is snap-only, deb package is not listed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2047818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2047818] Re: Only shows snaps
** Bug watch added: Debian Bug tracker #1058924 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058924 ** Also affects: gnome-software (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058924 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2047818 Title: Only shows snaps Status in gnome-software package in Ubuntu: New Status in gnome-software package in Debian: Unknown Bug description: Hi, Noble up to date, GNOME Software 45.2 Does only show snaps in search results. Example: - search for "xournal" - search result is snap-only, deb package is not listed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2047818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2047818] Re: Only shows snaps
** Description changed: Hi, Noble up to date, GNOME Software 45.2 Does only show snaps in search results. Example: - search for "xournal" - search result is snap-only, deb package is not listed - - If flatpak plugin is installed, only snaps are shown => unusable flatpak - plugin. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2047818 Title: Only shows snaps Status in gnome-software package in Ubuntu: New Status in gnome-software package in Debian: Unknown Bug description: Hi, Noble up to date, GNOME Software 45.2 Does only show snaps in search results. Example: - search for "xournal" - search result is snap-only, deb package is not listed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2047818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2047818] Re: Only shows snaps
** Changed in: gnome-software (Ubuntu) Importance: Undecided => High ** Tags added: noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2047818 Title: Only shows snaps Status in gnome-software package in Ubuntu: New Bug description: Hi, Noble up to date, GNOME Software 45.2 Does only show snaps in search results. Example: - search for "xournal" - search result is snap-only, deb package is not listed If flatpak plugin is installed, only snaps are shown => unusable flatpak plugin. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2047818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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
[Desktop-packages] [Bug 2047842] [NEW] wireless network connetion no longer working after noble upgrade
Public bug reported: Wireless network was working fine with matic, but system can no longer connect to wlan after noble upgrade. NetworkManager logs contains this: Jan 02 15:42:02 zeus NetworkManager[1105]: [1704206522.9854] device (wlan0): Activation: starting connection 'example.net' (x----x) Jan 02 15:42:02 zeus NetworkManager[1105]: [1704206522.9855] audit: op="connection-activate" uuid="x----x" name="example.net" pid=3441 uid=1000 result="success" Jan 02 15:42:02 zeus NetworkManager[1105]: [1704206522.9855] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Jan 02 15:42:02 zeus NetworkManager[1105]: [1704206522.9859] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Jan 02 15:42:02 zeus NetworkManager[1105]: [1704206522.9973] device (wlan0): new IWD device state is connecting Jan 02 15:42:03 zeus NetworkManager[1105]: [1704206523.3188] device (wlan0): Activation: (wifi) Network.Connect failed: GDBus.Error:net.connman.iwd.Failed: Operation failed Jan 02 15:42:03 zeus NetworkManager[1105]: [1704206523.3193] device (wlan0): state change: config -> failed (reason 'no-secrets', sys-iface-state: 'managed') Jan 02 15:42:03 zeus NetworkManager[1105]: [1704206523.3205] device (wlan0): Activation: failed for connection 'example.net' Jan 02 15:42:03 zeus NetworkManager[1105]: [1704206523.3207] device (wlan0): new IWD device state is disconnected Jan 02 15:42:03 zeus NetworkManager[1105]: [1704206523.3215] device (wlan0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') Iwd logs does have this log entry: Jan 02 15:44:19 zeus iwd[6299]: AP did not include group number in response! However, that warning is not new and was present before the upgrade. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: iwd 2.8-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Jan 2 15:38:11 2024 InstallationDate: Installed on 2017-09-26 (2289 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170924) ProcEnviron: LANG=en_US.UTF-8 LANGUAGE=en_US:en PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: iwd UpgradeStatus: Upgraded to noble on 2024-01-02 (0 days ago) mtime.conffile..etc.iwd.main.conf: 2024-01-02T15:02:42.100607 ** Affects: iwd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iwd in Ubuntu. https://bugs.launchpad.net/bugs/2047842 Title: wireless network connetion no longer working after noble upgrade Status in iwd package in Ubuntu: New Bug description: Wireless network was working fine with matic, but system can no longer connect to wlan after noble upgrade. NetworkManager logs contains this: Jan 02 15:42:02 zeus NetworkManager[1105]: [1704206522.9854] device (wlan0): Activation: starting connection 'example.net' (x----x) Jan 02 15:42:02 zeus NetworkManager[1105]: [1704206522.9855] audit: op="connection-activate" uuid="x----x" name="example.net" pid=3441 uid=1000 result="success" Jan 02 15:42:02 zeus NetworkManager[1105]: [1704206522.9855] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Jan 02 15:42:02 zeus NetworkManager[1105]: [1704206522.9859] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Jan 02 15:42:02 zeus NetworkManager[1105]: [1704206522.9973] device (wlan0): new IWD device state is connecting Jan 02 15:42:03 zeus NetworkManager[1105]: [1704206523.3188] device (wlan0): Activation: (wifi) Network.Connect failed: GDBus.Error:net.connman.iwd.Failed: Operation failed Jan 02 15:42:03 zeus NetworkManager[1105]: [1704206523.3193] device (wlan0): state change: config -> failed (reason 'no-secrets', sys-iface-state: 'managed') Jan 02 15:42:03 zeus NetworkManager[1105]: [1704206523.3205] device (wlan0): Activation: failed for connection 'example.net' Jan 02 15:42:03 zeus NetworkManager[1105]: [1704206523.3207] device (wlan0): new IWD device state is disconnected Jan 02 15:42:03 zeus NetworkManager[1105]: [1704206523.3215] device (wlan0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') Iwd logs does have this log entry: Jan 02 15:44:19 zeus iwd[6299]: AP did not include group number in response! However, that warning is not new and was present before the upgrade. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: iwd
[Desktop-packages] [Bug 2028864] Re: [snap] chromium browser does not work with accelerated graphics on Tegra (arm64)
hey Sandeep, there has been no (direct) progress so far on this issue. However we now have Ubuntu 22.04 images/support for Jetson Orin. For now without graphics/desktop support, but we are planning to enable desktop/graphics in our current development cycle (before end of April). We will look further into this issue during this timeframe. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2028864 Title: [snap] chromium browser does not work with accelerated graphics on Tegra (arm64) Status in chromium-browser package in Ubuntu: Confirmed Bug description: Tegra Orin platforms come in various flavor / dev kit. They all ship with a 'slightly' customized Ubuntu image. One of the customization is the addition of the Nvidia GPU drivers for Tegra. When running chromium browser debian package (either when running 18.04, or when running 22.04 with the package fetched from this PPA: https://launchpad.net/~nteodosio/+archive/ubuntu/chromium/+packages) then chromium works with hardware acceleration, as reported in chrome://gpu: Graphics Feature Status Canvas: Hardware accelerated Canvas out-of-process rasterization: Disabled Direct Rendering Display Compositor: Disabled Compositing: Hardware accelerated Multiple Raster Threads: Enabled OpenGL: Enabled Rasterization: Hardware accelerated Raw Draw: Disabled Video Decode: Hardware accelerated Video Encode: Software only. Hardware acceleration disabled Vulkan: Disabled WebGL: Hardware accelerated WebGL2: Hardware accelerated WebGPU: Disabled When using the snap version of chromium browser (on either 20.04 or 22.04), hardware acceleration is disabled, as shown in chrome://gpu: Graphics Feature Status Canvas: Software only, hardware acceleration unavailable Canvas out-of-process rasterization: Disabled Direct Rendering Display Compositor: Disabled Compositing: Software only. Hardware acceleration disabled Multiple Raster Threads: Enabled OpenGL: Disabled Rasterization: Software only. Hardware acceleration disabled Raw Draw: Disabled Skia Graphite: Disabled Video Decode: Software only. Hardware acceleration disabled Video Encode: Software only. Hardware acceleration disabled Vulkan: Disabled WebGL: Software only, hardware acceleration unavailable WebGL2: Software only, hardware acceleration unavailable WebGPU: Disabled Problems Detected WebGPU has been disabled via blocklist or the command line. Disabled Features: webgpu Accelerated video encode has been disabled, either via blocklist, about:flags or the command line. Disabled Features: video_encode Gpu compositing has been disabled, either via blocklist, about:flags or the command line. The browser will fall back to software compositing and hardware acceleration will be unavailable. Disabled Features: gpu_compositing These tests are done with X11. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2028864/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop Packages, which is subscribed to evince 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043000] Re: Update mutter to 45.2
To help the SRU team review, I am attaching a debdiff comparing my proposed upload today with mutter 45.2-0ubuntu1 which was briefly in mantic-updates before the end of year holidays. ** Description changed: Impact -- There is a new bugfix release in the stable 45 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/45.2/NEWS Test Case - Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- - Ubuntu 24.04 "Noble" has mutter 45.1 with all the non translation commits cherry-picked. It will get updated to 45.2 (and eventually to 46) after a mesa regression is handled. + This update landed in mantic-updates just before the end of year holidays but was reverted with https://launchpad.net/ubuntu/+source/mutter/45.2-0ubuntu2~really45.0 + + Compared to mutter 45.2-0ubuntu1, this changes or adds about 3 lines of + code in the triple buffering patch to avoid the regression reported in + LP: #2046360 ** Changed in: mutter (Ubuntu Mantic) Status: Triaged => In Progress ** Tags removed: verification-done verification-done-mantic ** Patch added: "mutter-lp2043000-try2.debdiff" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2043000/+attachment/5735544/+files/mutter-lp2043000-try2.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2043000 Title: Update mutter to 45.2 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Mantic: In Progress Bug description: Impact -- There is a new bugfix release in the stable 45 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/45.2/NEWS Test Case - Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- This update landed in mantic-updates just before the end of year holidays but was reverted with https://launchpad.net/ubuntu/+source/mutter/45.2-0ubuntu2~really45.0 Compared to mutter 45.2-0ubuntu1, this changes or adds about 3 lines of code in the triple buffering patch to avoid the regression reported in LP: #2046360 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2043000/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880411] Re: Support both Super keys simultaneously on org.gnome.mutter overlay-key
Thanks Ladar, that workaround works great for me. Exactly what I needed. I have a keyboard that _only_ has a right meta key that I often plug in to my laptop (Kinesis Advantage). My laptop, however, _only_ has a left meta key. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1880411 Title: Support both Super keys simultaneously on org.gnome.mutter overlay-key Status in Mutter: New Status in gnome-tweaks package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: The right super key doesn't show the overlay. Ubuntu 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1880411/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2035076] Re: Can't enter capital accented letters with Caps Lock on Wayland
** Changed in: mutter (Ubuntu Mantic) Status: Triaged => In Progress ** Tags removed: verification-done verification-done-mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2035076 Title: Can't enter capital accented letters with Caps Lock on Wayland Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Mantic: In Progress Status in mutter package in Fedora: Unknown Bug description: Impact -- Capital accented letters can't be entered using CAPS LOCK in the Wayland session Test Case - Open a terminal and install basic French support: sudo apt install language-pack-gnome-fr Open the Settings app. In the sidebar, click Keyboard Click +, choose French (France), then choose the French (AZERTY) keyboard Close the Settings app In the top right of the screen, click en and switch the keyboard layout to French (AZERTY) In the text editor, type é (this is the number 2 key on a US English keyboard). Now, press the Caps Lock key to enable Caps Lock. Press the same key. You should get É What Could Go Wrong --- This fix is included in mutter 45.2 so see the master bug for this upstream update: LP: #2043000 Original bug report --- Most programs don't recognize Italian accented capital letters. When "Caps Lock" is on àèìòù should be written as ÀÈÌÒÙ... but for some reasons they are not capitalized. I've noticed that everything works fine using the Live session which still uses X11 session. It looks there's no problem with programs that use xwayland like Gimp and MarkText. WORKAROUND === In "Settings -> Keyboard" it's possible to set a "compose key". For example I've selected the [Super left] key. If I want to compose È I press and immediately release each key: [Super left] + [E] + [Alt Gr] + ['] If you want É: [Super left] + [E] + ['] Do the same for the other vowels. === ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-text-editor 45~beta-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 11 11:48:41 2023 InstallationDate: Installed on 2023-09-07 (4 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230906.3) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2035076/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043027] Re: Wacom Intuos S stop working after upgrading to Ubuntu 23.10
** Tags removed: ubuntu verification-done verification-done-mantic
** Changed in: mutter (Ubuntu Mantic)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2043027
Title:
Wacom Intuos S stop working after upgrading to Ubuntu 23.10
Status in mutter package in Ubuntu:
Fix Released
Status in mutter source package in Mantic:
In Progress
Bug description:
Impact
--
Clicking does not work correctly with Wacom tablets in the Ubuntu/GNOME X11
sessions
Test Case
-
One of the people affected by this issue will verify whether their Wacom
tablet is working noticably better with the upgraded Mutter packages
What Could Go Wrong
---
The fix for this issue is included in upstream's mutter 45.2 release so
please see bug 2043000 as the master bug for this upgrade
Original Bug Report
---
Tablet seems to work until I open Krita (as I could read on Internet, it may
be related with Qt Apps).
When Krita is open, mouse movement works ok with the tablet, but when
it comes to click action it doesn't work and any further action with
mouse is not captured (even outside Krita!).
To regain control of the mouse I have to Alt+Tab and then I can click
again.
Some details that may be handy:
- I've got two monitors
- Maybe Qt apps related
- My graphic card is nVidia GTX 1060 6Gb, driver used nvidia-driver-535
Thanks for your effort. I love Ubuntu!
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-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..06.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] Permiso denegado: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 8 17:20:34 2023
DistUpgraded: 2023-11-08 00:54:28,961 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
nvidia/535.129.03, 6.2.0-36-generic, x86_64: installed (WARNING! Diff
between built and installed module!) (WARNING! Diff between built and installed
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff
between built and installed module!) (WARNING! Diff between built and installed
module!)
nvidia/535.129.03, 6.5.0-10-generic, x86_64: installed (WARNING! Diff
between built and installed module!) (WARNING! Diff between built and installed
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff
between built and installed module!) (WARNING! Diff between built and installed
module!)
virtualbox/7.0.10, 6.2.0-36-generic, x86_64: installed
virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 6GB]
[19da:1438]
InstallationDate: Installed on 2022-04-09 (578 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=9dd904a0-11bb-40fa-9fe8-2f10449a416c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-11-07 (1 days ago)
dmi.bios.date: 06/15/2020
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0608
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING B550-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0608:bd06/15/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGB550-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
[Desktop-packages] [Bug 2046360] Re: Heavy stuttering in Firefox with mutter 45.1/45.2
I am reopening this bug because I am reuploading mutter 45.2 for mantic and we need to verify that this bug does not return with the new update. ** Changed in: mutter (Ubuntu Mantic) Status: Fix Released => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2046360 Title: Heavy stuttering in Firefox with mutter 45.1/45.2 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Mantic: In Progress Bug description: [ Impact ] There is heavy stuttering visible in Firefox with mutter 45.1/45.2 when kinetic scrolling a non-animated web page with a touchpad. This is a regression introduced upstream in mutter 45.1 (8f27ebf8). [ Test Plan ] 0. Find a laptop with a touchpad. 1. Open a simple web page like a Wikipedia page in Firefox. 2. Use two fingers on the touchpad to fling it so it continues scrolling. Expect: The scrolling proceeds and slows perfectly smoothly. [ Where problems could occur ] Anywhere in frame scheduling (visual smoothness), since that is the code affected. [ Other Info ] The bug was introduced upstream in 45.1 by https://gitlab.gnome.org/GNOME/mutter/-/commit/8f27ebf87eee6057992a90560d4118ab7bdf138d but since it only hurts the triple buffering patch, that's where it has been fixed: https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commit/0b896518b2028d9c4d6ea44806d093fd33793689 https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commits/triple-buffering-v4-45 [ Workaround ] In /etc/environment: MUTTER_DEBUG_TRIPLE_BUFFERING=always or "never" also works. Just not "auto" because the bug is in auto mode (the default). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2046360/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2041751] Re: RM: Remove dangerously insecure MPPE PPTP from Ubuntu
The seeding [1] of it is also quite clear on why it is still there. """ # This stack is no more very relevant, but was in the early days of internet # dialin. This stack is a candidate for demotion, but OTOH received no # bugs/CVEs over the last years and therefore can stay as-is for now. # ppp itself is still recommended by network-manager and thereby has quite # an install base. """ Removing is maybe too hard as Steve outlined, but what about at least demoting to universe (to encourage it a bit less)? The seed change to the section linked above would be trivial, but it would need coordination with the Desktop variants as a dependency to network-manager-pptp is in most of the meta packages. reverse-depends --release=noble src:network-manager-pptp Reverse-Recommends == * network-manager (for network-manager-pptp) * ubuntu-budgie-desktop [amd64 arm64 armhf ppc64el] * ubuntu-budgie-desktop-minimal [amd64 arm64 armhf ppc64el] * ubuntu-budgie-desktop-raspi [arm64 armhf] * ubuntu-desktop [amd64 arm64 armhf ppc64el] * ubuntu-desktop-minimal [amd64 arm64 armhf ppc64el] * ubuntu-mate-core (for network-manager-pptp-gnome) * ubuntu-mate-desktop (for network-manager-pptp-gnome) * ubuntu-unity-desktop [amd64 arm64 armhf ppc64el] * ubuntukylin-desktop (for network-manager-pptp-gnome) * vanilla-gnome-desktop [amd64 arm64 armhf ppc64el] * xubuntu-desktop (for network-manager-pptp-gnome) * xubuntu-desktop (for network-manager-pptp) Reverse-Depends === * lomiri-indicator-network (for network-manager-pptp) It comes at a comfort loss though, since this is depended on by all those meta packages to work right away in a fresh install, which would be a behavior that will be lost. Also if there is a CVE, then only people using ubuntu pro would get a fix. Which is free for personal use, but those forced to use pptp are likely people with non-personal use of outdated infrastructure. So we'd make the world a bit less secure as likely not all would get the fixes then. Still I'd want to know from Steve and Seth which discussed so far - what would you think about that as a compromise? [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/platform/tree/supported-misc-servers#n190 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-pptp in Ubuntu. https://bugs.launchpad.net/bugs/2041751 Title: RM: Remove dangerously insecure MPPE PPTP from Ubuntu Status in linux package in Ubuntu: New Status in network-manager-pptp package in Ubuntu: New Status in pptp-linux package in Ubuntu: New Status in pptpd package in Ubuntu: Incomplete Bug description: Remove dangerously insecure MPPE PPTP from Ubuntu https://pptpclient.sourceforge.net/protocol-security.phtml It has been dead for over 20 years now. IPSec OpenVPN Strongswan are much better alternatives. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046189] Re: Xorg freezes on external displays when in Gnome Shell on Nvidia graphics
I didn't note it here, but this issue does not occur on the Wayland
session. That's a different kettle of fish (Gnome crashes if add or
remove an external monitor, and when waking from sleep (but this also
seems related to if displays are connected)).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046189] Re: Xorg freezes on external displays when in Gnome Shell on Nvidia graphics
I do have the Nvidia driver installed and working.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2047818] Re: Only shows snaps
Sorry, flatpaks are shown. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2047818 Title: Only shows snaps Status in gnome-software package in Ubuntu: New Bug description: Hi, Noble up to date, GNOME Software 45.2 Does only show snaps in search results. Example: - search for "xournal" - search result is snap-only, deb package is not listed If flatpak plugin is installed, only snaps are shown => unusable flatpak plugin. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2047818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop
Packages, which is subscribed to xorg-server 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2045977] Re: GNOME Shell crash with Wayland
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. 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. 2. If step 1 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. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2045977 Title: GNOME Shell crash with Wayland Status in gnome-shell package in Ubuntu: Incomplete Bug description: My GNOME session got idle and crashed. In the journalctl logs there is more details ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.1-0ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Dec 8 10:43:43 2023 DisplayManager: gdm3 InstallationDate: Installed on 2021-11-26 (742 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 45.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-08-18 (113 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2045977/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046074] Re: The monitor screen appears black when connecting the PC through the sound bar to the monitor
Sound and display coexisting on the same HDMI cable would be a kernel issue so reassigning... ** Package changed: mutter (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2046074 Title: The monitor screen appears black when connecting the PC through the sound bar to the monitor Status in linux package in Ubuntu: Incomplete Bug description: When I connect the laptop to the sound bar hdmi and the sound bar to the monitor, it tries to connect and Ubuntu detects it, but nothing appears on the screen. My HDMI works as it should, tested directly when it's connected to the monitor. I have tried on a laptop other than my computer with Windows to test if it is something of the sound bar and it works perfectly without problems. Don't really know what package should be interfering here. Mesa? Mutter? MSI laptop. CPU: AMD Ryzen 7 Series 4000 GPU: AMD Radeon RX 5600m RAM: 16GB NVM: 1TB. OS: Ubuntu 23.10 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: mutter (not installed) Uname: Linux 6.6.5-060605-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Dec 10 17:39:27 2023 InstallationDate: Installed on 2023-10-13 (58 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011) ProcEnviron: LANG=es_ES.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046074/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039570] Re: [amdgpu] Fullscreen in any Wayland / Xwayland window shows a black screen (no screen detected)
** No longer affects: mutter (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2039570
Title:
[amdgpu] Fullscreen in any Wayland / Xwayland window shows a black
screen (no screen detected)
Status in Linux:
Fix Released
Status in linux package in Ubuntu:
New
Bug description:
When I go into "fullscreen" watching a video while browsing in Firefox
or when playing a game through Steam (fullscreen mode), the screen
goes black.
The workaround I have discovered to get back is to enter the gdm from
"Ctrl + alt + F1" and then return to the session you were in
(normally, "Ctrl + alt + F2).
Edit: It happens when I connect a second monitor and use it as the
primary display while the laptop screen is disabled.
MSI laptop.
CPU: AMD Ryzen 7 Series 4000
GPU: AMD Radeon RX 5600m
RAM: 16GB
NVM: 1TB.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: noctis 2095 F wireplumber
/dev/snd/controlC0: noctis 2095 F wireplumber
/dev/snd/seq:noctis 2090 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 17 15:00:55 2023
InstallationDate: Installed on 2023-10-13 (4 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB:
0 amdgpudrmfb
1 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=fb325c2c-11c5-43e3-aceb-e921d5a7b323 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/26/2020
dmi.bios.release: 1.1
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E17EKAMS.101
dmi.board.asset.tag: Default string
dmi.board.name: MS-17EK
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrE17EKAMS.101:bd10/26/2020:br1.1:svnMicro-StarInternationalCo.,Ltd.:pnAlpha17A4DEK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17EK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku17EK.1:
dmi.product.family: Al
dmi.product.name: Alpha 17 A4DEK
dmi.product.sku: 17EK.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039570/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2047818] [NEW] Only shows snaps
Public bug reported: Hi, Noble up to date, GNOME Software 45.2 Does only show snaps in search results. Example: - search for "xournal" - search result is snap-only, deb package is not listed If flatpak plugin is installed, only snaps are shown => unusable flatpak plugin. ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2047818 Title: Only shows snaps Status in gnome-software package in Ubuntu: New Bug description: Hi, Noble up to date, GNOME Software 45.2 Does only show snaps in search results. Example: - search for "xournal" - search result is snap-only, deb package is not listed If flatpak plugin is installed, only snaps are shown => unusable flatpak plugin. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2047818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1968907] Re: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Yes it looks like the fix here only made it into Ubuntu 22.10 and later. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1968907 Title: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Status in gnome-session: Fix Released Status in gnome-session package in Ubuntu: Fix Released Bug description: Hi, I see the following errors in the system logs: # journalctl | grep gnome-session-binary Apr 13 18:22:54 vougeot gnome-session[3453]: gnome-session-binary[3453]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Apr 13 18:22:54 vougeot gnome-session[3453]: gnome-session-binary[3453]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Apr 13 18:22:54 vougeot gnome-session-binary[3453]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Apr 13 18:22:54 vougeot gnome-session-binary[3453]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-session-bin 42.0-1ubuntu2 Uname: Linux 5.17.2-051702-generic x86_64 ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Apr 13 19:48:49 2022 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1968907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1929209] Re: [i915] external monitor goes black for several seconds at a time, randomly
My previous comments one year ago were probably premature. And on top of that I'm now using a different primary desktop (also Intel 12th gen, now kernel 6.2) that periodically has a similar bug. My next plan is to try replacing the USB-C cable with an expensive Apple Thunderbolt cable. ** Changed in: mutter (Ubuntu) Status: Fix Released => Confirmed ** Tags added: jammy ** Changed in: mutter (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1929209 Title: [i915] external monitor goes black for several seconds at a time, randomly Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: At times it is completely debilitating; at other times it does not happen for hours. The physical connections are clean and solid. I guess the attachments will show that I'm using Intel graphics hardware. The monitor is a very popular Samsung one. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 20 16:56:04 2021 DistUpgraded: 2020-06-01 15:46:34,953 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:5036] InstallationDate: Installed on 2019-01-24 (847 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20BXCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-06-01 (353 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929209/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845601] Re: Images blurry in Background selection screen when scaling > 100%
** Changed in: gnome-control-center (Ubuntu) Status: Won't Fix => Fix Committed ** Tags added: fixed-in-gnome-control-center-46 fixed-upstream -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1845601 Title: Images blurry in Background selection screen when scaling > 100% Status in gnome-control-center: Fix Released Status in gnome-control-center package in Ubuntu: Fix Committed Bug description: Image: 19.10 beta – http://cdimage.ubuntu.com/daily-live/20190926.1/eoan-desktop-amd64.iso Device: Dell XPS 13 7390 (201908-27305) Steps to reproduce: 0. Go to Settings > Devices > Displays and make sure the scaling is 200% or more 1. Go to Settings > Background Expected result: 1. The thumbnails for the suggested backgrounds are sharp Actual result: 1. The thumbnails are blurry. I attached 3 screenshots of the Background screen at different scales (100%, 200%, 300%). This is a problem for people with UHD (4K) screens which are likely to select a 200% scaling. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.0.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 27 15:03:35 2019 InstallationDate: Installed on 2019-09-27 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1845601/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1804568] Re: [HP Spectre x360 Convertible 13] click position is flipped to cursor position when in tent mode
** Changed in: mutter (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1804568 Title: [HP Spectre x360 Convertible 13] click position is flipped to cursor position when in tent mode Status in Mutter: New Status in mutter package in Ubuntu: New Bug description: Hello, same bug is present 18.04 and 18.10: after I log in in tent mode the screen goes upside down, and after xrandr --output eDP-1 --rotate normal it goes back to normal however now the cursor is upside down, and click position and cursor position isnt the same, they are flipped thank you for the fix in advance ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: coreutils 8.28-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 22 04:28:21 2018 ExecutablePath: /bin/sleep InstallationDate: Installed on 2018-11-22 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: LANG=hu_HU.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: imi1950 F pulseaudio /dev/snd/controlC1: imi1950 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-03-30 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190329) MachineType: HP HP Spectre x360 Convertible 13-w0XX Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 RelatedPackageVersions: linux-restricted-modules-5.0.0-8-generic N/A linux-backports-modules-5.0.0-8-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 5.0.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.31 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827E dmi.board.vendor: HP dmi.board.version: 94.60 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.31:bd04/27/2017:svnHP:pnHPSpectrex360Convertible13-w0XX:pvr:rvnHP:rn827E:rvr94.60:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Spectre x360 Convertible 13-w0XX dmi.product.sku: Z9E46EA#ABV dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: imi1333 F pulseaudio /dev/snd/controlC1: imi1333 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-09-23 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190917) MachineType: HP HP Spectre x360 Convertible 13-w0XX Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 Tags: eoan Uname: Linux 5.3.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/03/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.49 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827E dmi.board.vendor: HP dmi.board.version: 94.71 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.49:bd05/03/2019:svnHP:pnHPSpectrex360Convertible13-w0XX:pvr:rvnHP:rn827E:rvr94.71:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Spectre x360 Convertible 13-w0XX dmi.product.sku: Z9E46EA#ABV dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu16 Architecture:
[Desktop-packages] [Bug 2030963] Re: Window/app switcher highlights hard to see
** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Committed ** Tags added: fixed-in-gnome-shell-46 fixed-upstream -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2030963 Title: Window/app switcher highlights hard to see Status in GNOME Shell: Fix Released Status in Yaru Theme: New Status in gnome-shell package in Ubuntu: Fix Committed Status in yaru-theme package in Ubuntu: Triaged Bug description: In 22.04's default theme, it's almost impossible for me to make out which app or window is the currently selected one in the window switcher (alt-tab) or the application switcher (super-tab). The "highlighted" item is just a slightly different shade of grey. I mean, I can make it out if I squint at it, but ... that just isn't a *highlight*. This is a use where Ubuntu Orange shines, too. :-( "Ok, boomer, you're blind. I can see that just fine". Fair enough. Are you under thirty and (thus still) have 20:20 vision, by any chance? The point is, it isn't good UI design either way. What's worse, the high contrast accessibility setting doesn't touch any of it, and that is definitely a bug. == EDIT: Rearranged the submission so that the bit this bug is meant to be primarily about is on top. The below bits are preserved so that the discussion still makes sense. Similarly, the active workspace in the workspace overview (?) does get an orange frame, but it's very thin, much too thin to see unless you look closely. Again, that's not a highlight. A highlight is supposed to pop out. In comparison, the highlighting for the current tab in Terminal is ok- ish. I'd *prefer* for the entire tab to become orange, or to become a lighter colour in addition to the orange bar, but it's usable. (I could go on. For example, windows' title bars are now white vs the iconic Ubuntu Brown, which makes it hard to tell where the title bar is vs the window contents. Many applications also have buttons in the title bar now. It's no longer possible to just grab a window and move it on auto-pilot ... If the title bar can't be a different colour any more, at least separate it with a thick line or something. In any case, 22.04 is a massive regression in terms of visual UI design vs 18.04. Form should follow function, not the other way around.) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13 Uname: Linux 6.2.0-1009-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 10 12:58:31 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-02 (7 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) RelatedPackageVersions: mutter-common 42.9-0ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2030963/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028864] Re: [snap] chromium browser does not work with accelerated graphics on Tegra (arm64)
Hi, is there any update on the issue? When should we expect the fix to be available by? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2028864 Title: [snap] chromium browser does not work with accelerated graphics on Tegra (arm64) Status in chromium-browser package in Ubuntu: Confirmed Bug description: Tegra Orin platforms come in various flavor / dev kit. They all ship with a 'slightly' customized Ubuntu image. One of the customization is the addition of the Nvidia GPU drivers for Tegra. When running chromium browser debian package (either when running 18.04, or when running 22.04 with the package fetched from this PPA: https://launchpad.net/~nteodosio/+archive/ubuntu/chromium/+packages) then chromium works with hardware acceleration, as reported in chrome://gpu: Graphics Feature Status Canvas: Hardware accelerated Canvas out-of-process rasterization: Disabled Direct Rendering Display Compositor: Disabled Compositing: Hardware accelerated Multiple Raster Threads: Enabled OpenGL: Enabled Rasterization: Hardware accelerated Raw Draw: Disabled Video Decode: Hardware accelerated Video Encode: Software only. Hardware acceleration disabled Vulkan: Disabled WebGL: Hardware accelerated WebGL2: Hardware accelerated WebGPU: Disabled When using the snap version of chromium browser (on either 20.04 or 22.04), hardware acceleration is disabled, as shown in chrome://gpu: Graphics Feature Status Canvas: Software only, hardware acceleration unavailable Canvas out-of-process rasterization: Disabled Direct Rendering Display Compositor: Disabled Compositing: Software only. Hardware acceleration disabled Multiple Raster Threads: Enabled OpenGL: Disabled Rasterization: Software only. Hardware acceleration disabled Raw Draw: Disabled Skia Graphite: Disabled Video Decode: Software only. Hardware acceleration disabled Video Encode: Software only. Hardware acceleration disabled Vulkan: Disabled WebGL: Software only, hardware acceleration unavailable WebGL2: Software only, hardware acceleration unavailable WebGPU: Disabled Problems Detected WebGPU has been disabled via blocklist or the command line. Disabled Features: webgpu Accelerated video encode has been disabled, either via blocklist, about:flags or the command line. Disabled Features: video_encode Gpu compositing has been disabled, either via blocklist, about:flags or the command line. The browser will fall back to software compositing and hardware acceleration will be unavailable. Disabled Features: gpu_compositing These tests are done with X11. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2028864/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
