[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-azure/5.19.0-1021.22)
All autopkgtests for the newly accepted linux-restricted-modules-azure (5.19.0-1021.22) for kinetic have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.10.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/kinetic/update_excuses.html#linux-restricted-modules-azure [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 1945760] Re: Window manager warning: WM_TRANSIENT_FOR window 0x56994b0 for 0x572b45a window override-redirect is an override-redirect window and this is not correct according t
consistently get this when i right click in gnome-terminal and enter the Profiles submenu -- 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/1945760 Title: Window manager warning: WM_TRANSIENT_FOR window 0x56994b0 for 0x572b45a window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x560003f. Status in gnome-shell package in Ubuntu: Confirmed Bug description: Window manager warning: WM_TRANSIENT_FOR window 0x56994b0 for 0x572b45a window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x560003f. Ubuntu 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 Uname: Linux 5.13.0-9.1-liquorix-amd64 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 1 10:48:53 2021 DisplayManager: gdm3 InstallationDate: Installed on 2018-06-28 (1190 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-12-05 (299 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-06-08T10:33:29.519300 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1945760/+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 2007180] Re: 3rd Monitor detected but not activated
Thanks for the bug report. Please run: lspci -k > lspci.txt journalctl -b0 > journal.txt xrandr --verbose > xrandr.txt grep . /sys/class/drm/*/status > drmconn.txt and attach the resulting text files here. ** Tags added: nvidia ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Package changed: gnome-shell (Ubuntu) => ubuntu -- 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/2007180 Title: 3rd Monitor detected but not activated Status in Ubuntu: Incomplete Bug description: I have 2 external monitors, both external monitors are detected but the display is allowing only 1 to be activated. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Feb 14 01:42:11 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-05 (344 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-09-10 (156 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2007180/+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 2001922] Re: Xorg crash
Are you using the built-in amdgpu driver or did you install it manually? -- 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/2001922 Title: Xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: My Ubuntu 22.04.1 LTS installation crashes, but I was not able to figure out how to reproducibly trigger the crash. The last time it happened was with firefox and zoom running, the display suddenly went black and after a few seconds the X login screen appeared, my session gone. There are files in /var/crash/ -rw-r--r-- 1 root whoopsie0 Jan 5 14:09 _usr_lib_xorg_Xorg.0.upload -rw-r- 1 root whoopsie 12792518 Jan 5 14:09 _usr_lib_xorg_Xorg.0.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:09 _usr_lib_xorg_Xorg.0.uploaded -rw-r--r-- 1 petr whoopsie0 Jan 5 14:13 _usr_bin_xfsettingsd.1000.upload -rw-r- 1 petr whoopsie 516897 Jan 5 14:13 _usr_bin_xfsettingsd.1000.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:13 _usr_bin_xfsettingsd.1000.uploaded -rw-r--r-- 1 petr whoopsie0 Jan 5 14:13 _opt_zoom_zoom.1000.upload -rw-r- 1 petr whoopsie 46590288 Jan 5 14:13 _opt_zoom_zoom.1000.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:13 _opt_zoom_zoom.1000.uploaded and .xsession-errors.old ends with (xfwm4:8122): xfwm4-WARNING **: 14:11:00.736: unmanaged net_wm_state (window 0x649, atom "_NET_WM_STATE_STAYS_ON_TOP") (xfwm4:10847): Gtk-WARNING **: 14:13:01.216: cannot open display: :0.0 Exiting due to channel error. Failed to parse arguments: Cannot open display: :0.0 Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. (xfsettingsd:10849): xfsettingsd-ERROR **: 14:13:01.239: Unable to open display. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. (xfwm4:10854): Gtk-WARNING **: 14:13:01.244: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 (xfwm4:10860): Gtk-WARNING **: 14:13:01.264: cannot open display: :0.0 (xfwm4:10863): Gtk-WARNING **: 14:13:01.280: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 (xfwm4:10865): Gtk-WARNING **: 14:13:01.293: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Is it safe and useful to upload the files from /var/crash/? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Thu Jan 5 14:17:42 2023 DistUpgraded: 2022-12-25 11:03:07,557 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.13.0-35-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-56-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:3f96] InstallationDate: Installed on 2021-11-07 (424 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20YA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-35-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to jammy on 2022-12-25 (11 days ago) dmi.bios.date: 09/23/2021 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: GMCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: ThinkBook 13s G3 ACN dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrGMCN27WW:bd09/23/2021:br1.27:efr1.19:svnLENOVO:pn20YA:pvrThinkBook13sG3ACN:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrThinkBook13sG3ACN:skuLENOVO_MT_20YA_BU_idea_FM_ThinkBook13sG3ACN: dmi.product.family: ThinkBook 13s G3 ACN dmi.product.name: 20YA dmi.product.sku: LENOVO_MT_20YA_BU_idea_FM_Th
[Desktop-packages] [Bug 1392053] Re: gnome-screenshot sometimes hangs leaving a transparent white square over the screen
Created Bug #2007194 as suggested by the last comment. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1392053 Title: gnome-screenshot sometimes hangs leaving a transparent white square over the screen Status in gnome-screenshot package in Ubuntu: Fix Released Bug description: Sometimes after taking some screenshots gnome-screenshots hangs and leaves a transparent white filled zone over my screen. The PrintScreen key does not work anymore in that situation. If I kill the gnome-screenshot process the white zone disappears and the PrintScreen key becomes functional again. I am using Ubuntu 14.10 with Unity. It comes with gnome-screenshot 3.10.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1392053/+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 2001922] Re: Xorg crash
Still much the same. No usable backtrace but one at least has a system log (which isn't useful). I wonder if this is a Xubuntu-specific problem with crash reports. -- 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/2001922 Title: Xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: My Ubuntu 22.04.1 LTS installation crashes, but I was not able to figure out how to reproducibly trigger the crash. The last time it happened was with firefox and zoom running, the display suddenly went black and after a few seconds the X login screen appeared, my session gone. There are files in /var/crash/ -rw-r--r-- 1 root whoopsie0 Jan 5 14:09 _usr_lib_xorg_Xorg.0.upload -rw-r- 1 root whoopsie 12792518 Jan 5 14:09 _usr_lib_xorg_Xorg.0.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:09 _usr_lib_xorg_Xorg.0.uploaded -rw-r--r-- 1 petr whoopsie0 Jan 5 14:13 _usr_bin_xfsettingsd.1000.upload -rw-r- 1 petr whoopsie 516897 Jan 5 14:13 _usr_bin_xfsettingsd.1000.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:13 _usr_bin_xfsettingsd.1000.uploaded -rw-r--r-- 1 petr whoopsie0 Jan 5 14:13 _opt_zoom_zoom.1000.upload -rw-r- 1 petr whoopsie 46590288 Jan 5 14:13 _opt_zoom_zoom.1000.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:13 _opt_zoom_zoom.1000.uploaded and .xsession-errors.old ends with (xfwm4:8122): xfwm4-WARNING **: 14:11:00.736: unmanaged net_wm_state (window 0x649, atom "_NET_WM_STATE_STAYS_ON_TOP") (xfwm4:10847): Gtk-WARNING **: 14:13:01.216: cannot open display: :0.0 Exiting due to channel error. Failed to parse arguments: Cannot open display: :0.0 Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. (xfsettingsd:10849): xfsettingsd-ERROR **: 14:13:01.239: Unable to open display. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. (xfwm4:10854): Gtk-WARNING **: 14:13:01.244: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 (xfwm4:10860): Gtk-WARNING **: 14:13:01.264: cannot open display: :0.0 (xfwm4:10863): Gtk-WARNING **: 14:13:01.280: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 (xfwm4:10865): Gtk-WARNING **: 14:13:01.293: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Is it safe and useful to upload the files from /var/crash/? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Thu Jan 5 14:17:42 2023 DistUpgraded: 2022-12-25 11:03:07,557 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.13.0-35-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-56-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:3f96] InstallationDate: Installed on 2021-11-07 (424 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20YA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-35-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to jammy on 2022-12-25 (11 days ago) dmi.bios.date: 09/23/2021 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: GMCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: ThinkBook 13s G3 ACN dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrGMCN27WW:bd09/23/2021:br1.27:efr1.19:svnLENOVO:pn20YA:pvrThinkBook13sG3ACN:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrThinkBook13sG3ACN:skuLENOVO_MT_20YA_BU_idea_FM_ThinkBook13sG3ACN: dmi.product.family: Th
[Desktop-packages] [Bug 2007194] [NEW] gnome-screenshot sometimes hangs leaving a transparent white square over the screen
Public bug reported: Based on Bug #1392053's closing comment, creating a new bug report as I am also facing this issue with gnome-screenshot. It's the same error, where there's a white outline in the centre (where the screenshot area is), and everything else on the screen is darker. Uncertain how to reproduce the error currently. My system details are as follows. $ lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 $ apt-cache policy gnome-screenshot gnome-screenshot: Installed: (none) Candidate: 41.0-2 Version table: 41.0-2 500 500 http://in.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-screenshot (not installed) ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 14 07:21:02 2023 InstallationDate: Installed on 2023-02-03 (10 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-screenshot (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/2007194 Title: gnome-screenshot sometimes hangs leaving a transparent white square over the screen Status in gnome-screenshot package in Ubuntu: New Bug description: Based on Bug #1392053's closing comment, creating a new bug report as I am also facing this issue with gnome-screenshot. It's the same error, where there's a white outline in the centre (where the screenshot area is), and everything else on the screen is darker. Uncertain how to reproduce the error currently. My system details are as follows. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ apt-cache policy gnome-screenshot gnome-screenshot: Installed: (none) Candidate: 41.0-2 Version table: 41.0-2 500 500 http://in.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-screenshot (not installed) ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 14 07:21:02 2023 InstallationDate: Installed on 2023-02-03 (10 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/2007194/+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 2006646] Re: hwacc branch builds with minigbm switch to software compositor on amd.
This could be a hint on why: WARNING:ozone_platform_wayland.cc(273)] Failed to find drm render node path. WARNING:wayland_buffer_manager_gpu.cc(424)] Failed to initialize drm render node handle. -- 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/2006646 Title: hwacc branch builds with minigbm switch to software compositor on amd. Status in chromium-browser package in Ubuntu: In Progress Bug description: This pertains to the hwacc branches of snap_from_source chromium builds. Following the guide-0.9.1, we switched from system gbm to minigbm. (These switches are in args.gn) use_system_minigbm = false use_intel_minigbm = true use_amdgpu_minigbm = true This enables us to better support intel hardware. However, there seems to be a regression on other gpus. Chromium will switch to software compositing on amd. When I revert back to system gbm, I get hardware compositing again. See attached screenshot. To reproduce: build chromium in two different ways, and compare the output from the chrome://gpu url. tested on: Radeon RX580 GPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006646/+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 2007188] [NEW] package firefox 109.0.1+build1-0ubuntu0.20.04.2 failed to install/upgrade: »neues firefox-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1
Public bug reported: none available. failed Update ubuntu 20 to 22 LTS ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 109.0.1+build1-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 Uname: Linux 5.4.0-139-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wolli 1794 F pulseaudio BuildID: 20230127170202 CasperMD5CheckResult: unknown Channel: Unavailable Date: Mon Feb 13 22:43:23 2023 ErrorMessage: »neues firefox-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-02-14 (1094 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IpRoute: default via 192.168.178.1 dev wlp0s20f3 proto dhcp metric 600 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 192.168.178.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.178.34 metric 600 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 109.0.1+build1-0ubuntu0.20.04.2 failed to install/upgrade: »neues firefox-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to jammy on 2023-02-13 (0 days ago) dmi.bios.date: 06/18/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0073.2019.0618.1409 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72692-308 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0073.2019.0618.1409:bd06/18/2019:svnIntel(R)ClientSystems:pnNUC8i5BEH:pvrJ72747-306:rvnIntelCorporation:rnNUC8BEB:rvrJ72692-308:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: BE dmi.product.name: NUC8i5BEH dmi.product.sku: BOXNUC8i5BEH dmi.product.version: J72747-306 dmi.sys.vendor: Intel(R) Client Systems ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2007188 Title: package firefox 109.0.1+build1-0ubuntu0.20.04.2 failed to install/upgrade: »neues firefox-Skript des Paketes pre- installation«-Unterprozess gab den Fehlerwert 1 zurück Status in firefox package in Ubuntu: New Bug description: none available. failed Update ubuntu 20 to 22 LTS ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 109.0.1+build1-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 Uname: Linux 5.4.0-139-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wolli 1794 F pulseaudio BuildID: 20230127170202 CasperMD5CheckResult: unknown Channel: Unavailable Date: Mon Feb 13 22:43:23 2023 ErrorMessage: »neues firefox-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-02-14 (1094 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IpRoute: default via 192.168.178.1 dev wlp0s20f3 proto dhcp metric 600 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 192.168.178.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.178.34 metric 600 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 109.0.1+build1-0ubuntu0.20.04.2 failed to install/upgrade: »neues firefox-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to jammy on 2023-02-13 (0 days ago) dmi.bios.date: 06/18
[Desktop-packages] [Bug 1175608] Re: Thumbnails too small in 'open file' dialog nautilus
This is mostly fixed in the next development release of Ubuntu. Ubuntu 23.04 is not a Long Term Support release but will be released in April. I am leaving this issue open because although the thumbnails are larger now, I don't see a way to change the thumbnail size. ** Also affects: gtk4 (Ubuntu) Importance: Undecided Status: New ** Changed in: gtk4 (Ubuntu) Status: New => Fix Committed ** Changed in: gtk4 (Ubuntu) Importance: Undecided => Wishlist ** Changed in: gtk4 (Ubuntu) Status: Fix Committed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1175608 Title: Thumbnails too small in 'open file' dialog nautilus Status in Nautilus: Expired Status in gtk+3.0 package in Ubuntu: Triaged Status in gtk4 package in Ubuntu: Triaged Bug description: When trying to upload image files to e.g. websites like marktplaats.nl (kind of ebay) I get very, very small image thumbnails. There seems no way to enlarge these thumbnails. All options only work if Nautilus is used stand alone, but not with the open file dialog that is being used to upload files. I have attached a screen dump just to show what I mean. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1175608/+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 1980937] Re: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise
I'm running on Ubuntu 22.04, kernel 5.15.0-60-generic and this still happens. -- 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/1980937 Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise Status in alsa-driver package in Ubuntu: Confirmed Bug description: New laptop with fresh installation of Xubuntu 22.04. Intel Tiger Lake- LP audio controller. When playing any audio, the internal speaker plays no sound except periodic loud crackling noise. The 3.5mm jack does not work either, producing the same craclking noise alongside some eletrical noise. HDMI audio skimmishly tested, but also gave no sound. Curiously, USB headphone (along with microphone) works perfectly, also the internal microphone. As attempts to fix the problem, I have tried the following separately, with no avail: - Installing some Ubuntu OEM version of the 5.17 kernel - Updating to the v2.2 firmware from Sound Open Firmware Project (thesofproject on github), reverted afterwards I found exactly the same problem reported in the Fedora community: https://forums.fedoraforum.org/showthread.php?328627-HP-Elitebook-840-G8-Tiger-Lake-audio-only-produces-popping-sound&p=1860086 As the pre-installed Windows has been destroyed, no further test on Windows has been done. Since USB headphone and internal microphone work, I think that there is no problem on the Intel Tiger Lake-LP controller and its driver. The bug probably lies elsewhere, like in the handling of ALC245 on this new laptop model. Thank you very much for your time and effort in advance. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fwjmath2810 F pulseaudio fwjmath 72467 F alsamixer CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Thu Jul 7 10:59:22 2022 InstallationDate: Installed on 2022-06-29 (7 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fwjmath2810 F pulseaudio fwjmath 72467 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2022 dmi.bios.release: 9.1 dmi.bios.vendor: HP dmi.bios.version: T37 Ver. 01.09.01 dmi.board.name: 8AB8 dmi.board.vendor: HP dmi.board.version: KBC Version 58.03.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 88.3 dmi.modalias: dmi:bvnHP:bvrT37Ver.01.09.01:bd05/05/2022:br9.1:efr88.3:svnHP:pnHPEliteBook840G8NotebookPC:pvr:rvnHP:rn8AB8:rvrKBCVersion58.03.00:cvnHP:ct10:cvr:sku6A3P3AV: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 G8 Notebook PC dmi.product.sku: 6A3P3AV dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-07-02T17:07:35.783239 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1980937/+subscriptions -- Mailing list: https://launchpad.net/~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 2007180] [NEW] 3rd Monitor detected but not activated
Public bug reported: I have 2 external monitors, both external monitors are detected but the display is allowing only 1 to be activated. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Feb 14 01:42:11 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-05 (344 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-09-10 (156 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/2007180 Title: 3rd Monitor detected but not activated Status in gnome-shell package in Ubuntu: New Bug description: I have 2 external monitors, both external monitors are detected but the display is allowing only 1 to be activated. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Feb 14 01:42:11 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-05 (344 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-09-10 (156 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2007180/+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 1980937] Re: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise
Same problem Laptop Product Name: Victus by HP Laptop 16-e17xxx Serial Number: 5CD212MCYY OS DISTRIB_ID=Kubuntu DISTRIB_RELEASE=22.10 -- 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/1980937 Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise Status in alsa-driver package in Ubuntu: Confirmed Bug description: New laptop with fresh installation of Xubuntu 22.04. Intel Tiger Lake- LP audio controller. When playing any audio, the internal speaker plays no sound except periodic loud crackling noise. The 3.5mm jack does not work either, producing the same craclking noise alongside some eletrical noise. HDMI audio skimmishly tested, but also gave no sound. Curiously, USB headphone (along with microphone) works perfectly, also the internal microphone. As attempts to fix the problem, I have tried the following separately, with no avail: - Installing some Ubuntu OEM version of the 5.17 kernel - Updating to the v2.2 firmware from Sound Open Firmware Project (thesofproject on github), reverted afterwards I found exactly the same problem reported in the Fedora community: https://forums.fedoraforum.org/showthread.php?328627-HP-Elitebook-840-G8-Tiger-Lake-audio-only-produces-popping-sound&p=1860086 As the pre-installed Windows has been destroyed, no further test on Windows has been done. Since USB headphone and internal microphone work, I think that there is no problem on the Intel Tiger Lake-LP controller and its driver. The bug probably lies elsewhere, like in the handling of ALC245 on this new laptop model. Thank you very much for your time and effort in advance. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fwjmath2810 F pulseaudio fwjmath 72467 F alsamixer CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Thu Jul 7 10:59:22 2022 InstallationDate: Installed on 2022-06-29 (7 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fwjmath2810 F pulseaudio fwjmath 72467 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2022 dmi.bios.release: 9.1 dmi.bios.vendor: HP dmi.bios.version: T37 Ver. 01.09.01 dmi.board.name: 8AB8 dmi.board.vendor: HP dmi.board.version: KBC Version 58.03.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 88.3 dmi.modalias: dmi:bvnHP:bvrT37Ver.01.09.01:bd05/05/2022:br9.1:efr88.3:svnHP:pnHPEliteBook840G8NotebookPC:pvr:rvnHP:rn8AB8:rvrKBCVersion58.03.00:cvnHP:ct10:cvr:sku6A3P3AV: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 G8 Notebook PC dmi.product.sku: 6A3P3AV dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-07-02T17:07:35.783239 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1980937/+subscriptions -- Mailing list: https://launchpad.net/~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 2001922] Re: Xorg crash
And another one... 35f5fbf4-abc7-11ed-9e34-fa163e993415 -- 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/2001922 Title: Xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: My Ubuntu 22.04.1 LTS installation crashes, but I was not able to figure out how to reproducibly trigger the crash. The last time it happened was with firefox and zoom running, the display suddenly went black and after a few seconds the X login screen appeared, my session gone. There are files in /var/crash/ -rw-r--r-- 1 root whoopsie0 Jan 5 14:09 _usr_lib_xorg_Xorg.0.upload -rw-r- 1 root whoopsie 12792518 Jan 5 14:09 _usr_lib_xorg_Xorg.0.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:09 _usr_lib_xorg_Xorg.0.uploaded -rw-r--r-- 1 petr whoopsie0 Jan 5 14:13 _usr_bin_xfsettingsd.1000.upload -rw-r- 1 petr whoopsie 516897 Jan 5 14:13 _usr_bin_xfsettingsd.1000.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:13 _usr_bin_xfsettingsd.1000.uploaded -rw-r--r-- 1 petr whoopsie0 Jan 5 14:13 _opt_zoom_zoom.1000.upload -rw-r- 1 petr whoopsie 46590288 Jan 5 14:13 _opt_zoom_zoom.1000.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:13 _opt_zoom_zoom.1000.uploaded and .xsession-errors.old ends with (xfwm4:8122): xfwm4-WARNING **: 14:11:00.736: unmanaged net_wm_state (window 0x649, atom "_NET_WM_STATE_STAYS_ON_TOP") (xfwm4:10847): Gtk-WARNING **: 14:13:01.216: cannot open display: :0.0 Exiting due to channel error. Failed to parse arguments: Cannot open display: :0.0 Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. (xfsettingsd:10849): xfsettingsd-ERROR **: 14:13:01.239: Unable to open display. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. (xfwm4:10854): Gtk-WARNING **: 14:13:01.244: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 (xfwm4:10860): Gtk-WARNING **: 14:13:01.264: cannot open display: :0.0 (xfwm4:10863): Gtk-WARNING **: 14:13:01.280: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 (xfwm4:10865): Gtk-WARNING **: 14:13:01.293: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Is it safe and useful to upload the files from /var/crash/? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Thu Jan 5 14:17:42 2023 DistUpgraded: 2022-12-25 11:03:07,557 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.13.0-35-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-56-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:3f96] InstallationDate: Installed on 2021-11-07 (424 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20YA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-35-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to jammy on 2022-12-25 (11 days ago) dmi.bios.date: 09/23/2021 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: GMCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: ThinkBook 13s G3 ACN dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrGMCN27WW:bd09/23/2021:br1.27:efr1.19:svnLENOVO:pn20YA:pvrThinkBook13sG3ACN:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrThinkBook13sG3ACN:skuLENOVO_MT_20YA_BU_idea_FM_ThinkBook13sG3ACN: dmi.product.family: ThinkBook 13s G3 ACN dmi.product.name: 20YA dmi.product.sku: LENOVO_MT_20YA_BU_idea_FM_ThinkBook 13s G3 AC
[Desktop-packages] [Bug 2006641] Re: hwacc branches fail to build
** Tags removed: beta-ok ** Tags added: beta-failed ** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => Triaged ** Description changed: Currently the hwacc branches of snap_from_source fail to build. This is caused by the fact that the guide-0.9.1 patches are against 107 chromium, and no longer apply cleanly. - build logs here: - https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-hwacc-beta + build logs here: + Candidate: https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-hwacc-candidate + Beta: https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-hwacc-beta + Dev: https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-hwacc-dev -- 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/2006641 Title: hwacc branches fail to build Status in chromium-browser package in Ubuntu: Triaged Bug description: Currently the hwacc branches of snap_from_source fail to build. This is caused by the fact that the guide-0.9.1 patches are against 107 chromium, and no longer apply cleanly. build logs here: Candidate: https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-hwacc-candidate Beta: https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-hwacc-beta Dev: https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-hwacc-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006641/+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 2007052] Re: package chromium-browser 109.0.5414.74-0ubuntu0.18.04.14 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error
*** This bug is a duplicate of bug 1729576 *** https://bugs.launchpad.net/bugs/1729576 If your /home is not actually symlinked let me know so I can reopen the bug targeted to snapd. ** Also affects: snap (Ubuntu) Importance: Undecided Status: New ** No longer affects: snap (Ubuntu) ** Changed in: chromium-browser (Ubuntu) Status: New => Invalid ** This bug has been marked a duplicate of bug 1729576 cannot perform operation: mount --rbind /snap /snap: Permission denied -- 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/2007052 Title: package chromium-browser 109.0.5414.74-0ubuntu0.18.04.14 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 Status in chromium-browser package in Ubuntu: Invalid Bug description: crash occurred during 18.04 -> 20.04 do-release-upgrade, transition from dpkg/deb to snap install ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 109.0.5414.74-0ubuntu0.18.04.14 ProcVersionSignature: Ubuntu 5.4.0-137.154~18.04.1-generic 5.4.218 Uname: Linux 5.4.0-137-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 DRM.card0-Virtual-1: enabled: enabled dpms: On status: connected edid-base64: modes: preferred 1152x864 1024x768 800x600 640x480 DRM.card0-Virtual-2: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-Virtual-3: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-Virtual-4: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-Virtual-5: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-Virtual-6: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-Virtual-7: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-Virtual-8: enabled: disabled dpms: On status: disconnected edid-base64: modes: Date: Mon Feb 13 01:03:59 2023 Desktop-Session: 'None' 'None' 'None' Env: 'None' 'None' ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2015-11-04 (2657 days ago) InstallationMedia: Ubuntu-Server 12.04.5 LTS "Precise Pangolin" - Release amd64 (20140806.1) InstalledPlugins: Load-Avg-1min: 0.71 Load-Processes-Running-Percent: 0.3% Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware7,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-137-generic root=UUID=152d5d4a-70ca-4be1-a626-b450c2b7965b ro Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: chromium-browser Title: package chromium-browser 109.0.5414.74-0ubuntu0.18.04.14 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2023-02-13 (0 days ago) dmi.bios.date: 06/25/2021 dmi.bios.vendor: VMware, Inc. dmi.bios.version: VMW71.00V.18227214.B64.2106252220 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnVMware,Inc.:bvrVMW71.00V.18227214.B64.2106252220:bd06/25/2021:svnVMware,Inc.:pnVMware7,1:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware7,1 dmi.product.version: None dmi.sys.vendor: VMware, Inc. modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007052/+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 2007160] [NEW] Image properties does nothing in lunar
Public bug reported: When testing the current lunar (23.04) pre-installed desktop image for the Raspberry Pi, I attempted to retrieve the properties of a captured JPEG from nautilus: * Right click on a JPEG image * Select "Properties" item at the bottom * Click on the "Image Properties" link at the bottom of the dialog that opens However, nothing happens when clicking on the link. I presume this is meant to go to a page listing the details that nautilus used to display (resolution, etc). I tested with a couple of different JPEGs that display their properties correctly under jammy and kinetic. I'm happy to provide test images if required, but I don't think it's specific to the JPEGs I'm using. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2007160 Title: Image properties does nothing in lunar Status in nautilus package in Ubuntu: New Bug description: When testing the current lunar (23.04) pre-installed desktop image for the Raspberry Pi, I attempted to retrieve the properties of a captured JPEG from nautilus: * Right click on a JPEG image * Select "Properties" item at the bottom * Click on the "Image Properties" link at the bottom of the dialog that opens However, nothing happens when clicking on the link. I presume this is meant to go to a page listing the details that nautilus used to display (resolution, etc). I tested with a couple of different JPEGs that display their properties correctly under jammy and kinetic. I'm happy to provide test images if required, but I don't think it's specific to the JPEGs I'm using. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2007160/+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 1997168] Re: [snap] Passwords are saved but not loaded with gnome keyring
** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => Fix Released -- 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/1997168 Title: [snap] Passwords are saved but not loaded with gnome keyring Status in chromium-browser package in Ubuntu: Fix Released Bug description: Steps to reproduce: * System: Fresh (minimal, desktop) installation of Ubuntu 22.04 LTS in VirtualBox to rule out any side-effects from preexisting configurations * Install latest updates: `sudo apt update && sudo apt upgrade -y && sudo apt dist-upgrade -y && sudo snap refresh` * Install chromium from snap (`sudo snap install chromium`) * Connect chromium to password manager service (`sudo snap connect chromium:password-manager-service`) -> now chromium should be able to use gnome keyring to store its master password * Launch chromium, navigate to "chrome://settings/passwords" * Add a new password ("Saved Passwords" -> "Add") * Password shows up under "Saved Passwords" as expected. * Close chromium and open it again, navigate to "chrome://settings/passwords" * Expected: Password should show up. Instead: The list is empty. * Add another password: List stays empty. What I found out so far: * Despite of the list showing up as empty in chromium, both passwords have been stored in "~/snap/chromium/common/chromium/Default/Login Data" (to confirm, grep for the username of the saved login, as the password itself will be encrypted) * It seems that the snap version of chromium does not create the entries "Chrome Safe Storage" and "Chrome Safe Storage Control" in the gnome keyring, which seems to be necessary at the moment (see http://crbug.com/660005). If a non-snap version of chromium (e.g. from https://launchpad.net/~savoury1/+archive/ubuntu/chromium) is installed first, which is used to bootstrap the user's chromium config folder and which creates the aforementioned entries in the gnome keyring, things are working fine, even after transitioning to the snap version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1997168/+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 2006633] Re: Merge librsvg 2.54.5+dfsg-1 (main) from Debian unstable (main)
Thanks for the upload and for your comments, Simon; noted. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/2006633 Title: Merge librsvg 2.54.5+dfsg-1 (main) from Debian unstable (main) Status in librsvg package in Ubuntu: New Bug description: Please merge librsvg 2.54.5+dfsg-1 (main) from Debian unstable (main) Changelog entries since current lunar version 2.54.4+dfsg-1ubuntu1: librsvg (2.54.5+dfsg-1) unstable; urgency=medium * New upstream release * debian/librsvg2-2.docs: NEWS.md -> NEWS -- Jeremy Bicha Thu, 22 Sep 2022 17:00:54 -0400 Remaining differences with librsvg from Debian unstable: * Don't fail the build on tests error for i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/2006633/+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 2001922] Re: Xorg crash
I reinstalled the system and it happened again. The crash id from /var/crash/_usr_lib_xorg_Xorg.0.uploaded is f5810a24-aba6-11ed-b81a-fa163ef35206 -- 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/2001922 Title: Xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: My Ubuntu 22.04.1 LTS installation crashes, but I was not able to figure out how to reproducibly trigger the crash. The last time it happened was with firefox and zoom running, the display suddenly went black and after a few seconds the X login screen appeared, my session gone. There are files in /var/crash/ -rw-r--r-- 1 root whoopsie0 Jan 5 14:09 _usr_lib_xorg_Xorg.0.upload -rw-r- 1 root whoopsie 12792518 Jan 5 14:09 _usr_lib_xorg_Xorg.0.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:09 _usr_lib_xorg_Xorg.0.uploaded -rw-r--r-- 1 petr whoopsie0 Jan 5 14:13 _usr_bin_xfsettingsd.1000.upload -rw-r- 1 petr whoopsie 516897 Jan 5 14:13 _usr_bin_xfsettingsd.1000.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:13 _usr_bin_xfsettingsd.1000.uploaded -rw-r--r-- 1 petr whoopsie0 Jan 5 14:13 _opt_zoom_zoom.1000.upload -rw-r- 1 petr whoopsie 46590288 Jan 5 14:13 _opt_zoom_zoom.1000.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:13 _opt_zoom_zoom.1000.uploaded and .xsession-errors.old ends with (xfwm4:8122): xfwm4-WARNING **: 14:11:00.736: unmanaged net_wm_state (window 0x649, atom "_NET_WM_STATE_STAYS_ON_TOP") (xfwm4:10847): Gtk-WARNING **: 14:13:01.216: cannot open display: :0.0 Exiting due to channel error. Failed to parse arguments: Cannot open display: :0.0 Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. (xfsettingsd:10849): xfsettingsd-ERROR **: 14:13:01.239: Unable to open display. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. (xfwm4:10854): Gtk-WARNING **: 14:13:01.244: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 (xfwm4:10860): Gtk-WARNING **: 14:13:01.264: cannot open display: :0.0 (xfwm4:10863): Gtk-WARNING **: 14:13:01.280: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 (xfwm4:10865): Gtk-WARNING **: 14:13:01.293: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Is it safe and useful to upload the files from /var/crash/? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Thu Jan 5 14:17:42 2023 DistUpgraded: 2022-12-25 11:03:07,557 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.13.0-35-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-56-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:3f96] InstallationDate: Installed on 2021-11-07 (424 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20YA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-35-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to jammy on 2022-12-25 (11 days ago) dmi.bios.date: 09/23/2021 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: GMCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: ThinkBook 13s G3 ACN dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrGMCN27WW:bd09/23/2021:br1.27:efr1.19:svnLENOVO:pn20YA:pvrThinkBook13sG3ACN:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrThinkBook13sG3ACN:skuLENOVO_MT_20YA_BU_idea_FM_ThinkBook13sG3ACN: dmi.product.family: ThinkBook 13s G3 AC
[Desktop-packages] [Bug 1980937] Re: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise
I'm having the same problem with HP Elitebook 860 G9. I get sound through headphones and HDMI output, but not through built-in speakers. Upgrading to kernel 5.9.17 seems to fix the problem. -- 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/1980937 Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise Status in alsa-driver package in Ubuntu: Confirmed Bug description: New laptop with fresh installation of Xubuntu 22.04. Intel Tiger Lake- LP audio controller. When playing any audio, the internal speaker plays no sound except periodic loud crackling noise. The 3.5mm jack does not work either, producing the same craclking noise alongside some eletrical noise. HDMI audio skimmishly tested, but also gave no sound. Curiously, USB headphone (along with microphone) works perfectly, also the internal microphone. As attempts to fix the problem, I have tried the following separately, with no avail: - Installing some Ubuntu OEM version of the 5.17 kernel - Updating to the v2.2 firmware from Sound Open Firmware Project (thesofproject on github), reverted afterwards I found exactly the same problem reported in the Fedora community: https://forums.fedoraforum.org/showthread.php?328627-HP-Elitebook-840-G8-Tiger-Lake-audio-only-produces-popping-sound&p=1860086 As the pre-installed Windows has been destroyed, no further test on Windows has been done. Since USB headphone and internal microphone work, I think that there is no problem on the Intel Tiger Lake-LP controller and its driver. The bug probably lies elsewhere, like in the handling of ALC245 on this new laptop model. Thank you very much for your time and effort in advance. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fwjmath2810 F pulseaudio fwjmath 72467 F alsamixer CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Thu Jul 7 10:59:22 2022 InstallationDate: Installed on 2022-06-29 (7 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fwjmath2810 F pulseaudio fwjmath 72467 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2022 dmi.bios.release: 9.1 dmi.bios.vendor: HP dmi.bios.version: T37 Ver. 01.09.01 dmi.board.name: 8AB8 dmi.board.vendor: HP dmi.board.version: KBC Version 58.03.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 88.3 dmi.modalias: dmi:bvnHP:bvrT37Ver.01.09.01:bd05/05/2022:br9.1:efr88.3:svnHP:pnHPEliteBook840G8NotebookPC:pvr:rvnHP:rn8AB8:rvrKBCVersion58.03.00:cvnHP:ct10:cvr:sku6A3P3AV: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 G8 Notebook PC dmi.product.sku: 6A3P3AV dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-07-02T17:07:35.783239 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1980937/+subscriptions -- Mailing list: https://launchpad.net/~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 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap
** Tags added: kivu -- 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/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in chromium-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 640x480 640x480 640x480 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 916G 222G 648G 26% / tmpfs tmpfs 16G 0 16G 0% /dev/shm /dev/nvme0n1p2 ext4 916G 222G 648G 26% / DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2020-08-02 (914 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS System Product Name Package: chromium-browser 1:85.0.4183.83-0ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1a37d538-d59f-477b-96f0-f949ce9b4553 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Snap.Changes: no changes found Snap.ChromeDriverVersion: ChromeDriver 109.0.5414.119 (772095164c7d5d4e73160f858efed3b5e87eca83-refs/branch-heads/5414@{#1458}) Snap.ChromiumVersion: update.go:85: cannot change mount namesp
[Desktop-packages] [Bug 2006966] Re: Missing flag causing lack of hardware encoding in hwacc build.
** Changed in: chromium-browser (Ubuntu) Status: In Progress => Fix Committed -- 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/2006966 Title: Missing flag causing lack of hardware encoding in hwacc build. Status in chromium-browser package in Ubuntu: Fix Committed Bug description: This is about the hwacc branch of snap-from-source package. The chromium 110 version of the build guide came with the instruction to add an additional flag when launching chromium: VaapiVideoDecodeLinuxGL This flag is not present in chromium.launcher of the beta branch of hwacc, causing hw acceleration to fail. This was caught by checkbox kivu run. I will make a merge request adding this flag. $ snap info chromium | grep installed installed: 110.0.5481.77-hwacc(2320) 174MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006966/+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 2006966] Re: Missing flag causing lack of hardware encoding in hwacc build.
** Merge proposal linked: https://code.launchpad.net/~b-stolk/chromium-browser/+git/snap-from-source/+merge/437157 -- 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/2006966 Title: Missing flag causing lack of hardware encoding in hwacc build. Status in chromium-browser package in Ubuntu: In Progress Bug description: This is about the hwacc branch of snap-from-source package. The chromium 110 version of the build guide came with the instruction to add an additional flag when launching chromium: VaapiVideoDecodeLinuxGL This flag is not present in chromium.launcher of the beta branch of hwacc, causing hw acceleration to fail. This was caught by checkbox kivu run. I will make a merge request adding this flag. $ snap info chromium | grep installed installed: 110.0.5481.77-hwacc(2320) 174MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006966/+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 2003176] Re: SRU: metacity crashes while minimizing a windows that has undocked child
Verification is done for Focal and Jammy, I've run the test case 3 times for both, and experienced no crashes while minimizing a parent window with undocked child. Also, the window is restored properly when un- minimized. ** Attachment added: "Screenshot from 2023-02-13 13-45-20.png" https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/2003176/+attachment/5646788/+files/Screenshot%20from%202023-02-13%2013-45-20.png ** Tags removed: verification-needed verification-needed-focal verification-needed-jammy ** Tags added: verification-done-focal verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/2003176 Title: SRU: metacity crashes while minimizing a windows that has undocked child Status in metacity package in Ubuntu: New Status in metacity source package in Focal: Fix Committed Status in metacity source package in Jammy: Fix Committed Bug description: [General information about the SRU] * It includes the fix for the bug https://gitlab.gnome.org/GNOME/metacity/-/issues/31 * The fix is already included in 3.46.0 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/77f1d55479bfef479f76011a1ee5636f9bf6b08b#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8 * The reproducer also revealed another issue with docked windows, undocked windows are not being restored after parent window is minimized and restored * The fix for restore is included in 3.46.1 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/3db07fafa1c7ff9749b6a82ccb36d8b62f2304d9 * Focal(3.36.1) and Jammy (3.44.0) needs both fixes to be backported [Impact] This affects users using applications that have docked windows [Test Case] * Install gnome-session-flashback (metacity) and reproducer's dependencies `sudo apt install lightdm gnome-session-flashback pyside2-tools python3-pyside2.qtwidgets` * Start a graphical session with metacity * run python3 Untitled.py * Undock one of the application's child windows * Minimize main window * Result: Metacity will crash * Fix: install fix from ppa: * sudo add-apt-repository ppa:mustafakemalgilor/lp-2003176-0 * sudo apt update * sudo reboot # or alternatively, restart display manager * run python3 Untitled.py * Undock one of the application's child windows * Minimize main window * Expectation: it should not crash and the application should be minimized. [Regression Potential] The fix is small in size and localized, it should not cause any regressions. - Bug Version: 1:3.36.1-1 / 1:3.44.0-1 Metacity is running without the composite manager. Users cannot minimize an application with an undocked child window ProblemType: Bug DistroRelease: Ubuntu 20.04 / Ubuntu 22.04 Package: metacity 1:3.36.1-1 / 1:3.44.0-1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/2003176/+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 1966635] Re: can't move file/directory by drag and drop by using touch monitor
** Tags added: originate-from-2006441 ** Tags added: originate-from-2006547 -- 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/1966635 Title: can't move file/directory by drag and drop by using touch monitor Status in Mutter: New Status in OEM Priority Project: Confirmed Status in mutter package in Ubuntu: New Status in nautilus package in Ubuntu: Incomplete Bug description: Can't move file/directory by drag and drop by using a touch monitor OS: 22.04, up to date @ Mar 28, 2022. nautilus: 1:42~rc-1-ubuntu1 mode: wayland To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1966635/+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 2007124] [NEW] Move available config files from /etc to /usr
Public bug reported: At the upgrade to fontconfig 2.10 a decade ago, the directory for storing available config files was changed from /etc/fonts/conf.avail to /usr/share/fontconfig/conf.avail. It was done upstream as well as in Debian, but Ubuntu delayed the transition for some reason. I think we should do that transition in Ubuntu too. That will get Ubuntu in sync with the upstream documentation and the delta to Debian gets reduced a little. The changes needed are straightforward. I put a proposed upload in this PPA: https://launchpad.net/~gunnarhj/+archive/ubuntu/fontconfig and I would appreciate someone's eyes on it. So, what's the caveat? The only thing I can think of is that distros, system admins and individual users may have tweaked the font configuration by including symlinks which point to the moved files. While I don't have the impression that such symlinks are very frequent — custom conf files put directly in /etc/fonts/conf.d or equivalent places in $HOME seem to be more common — to the extent they exist, they will be silently disabled. Bug #2005124 revealed an example of a symlink which pointed to a file which will be moved if we do this. OTOH, in that case upstream added a symlink with the very same name, so we had to deal with that conflict. If the name of Kubuntu's link had been something else, we might not be aware of it yet. The changelog for this upload: https://launchpad.net/ubuntu/+source/fontconfig/2.10.1-0ubuntu1 states that the transition will be done "later with another upload once the details are sorted". Are there other details which I have missed? If not, I suppose that the potential inconvenience is approximately as big today as it was 2012. And since next LTS release is more than one year ahead, this ought to be an appropriate time to make the change. ** Affects: fontconfig (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2007124 Title: Move available config files from /etc to /usr Status in fontconfig package in Ubuntu: New Bug description: At the upgrade to fontconfig 2.10 a decade ago, the directory for storing available config files was changed from /etc/fonts/conf.avail to /usr/share/fontconfig/conf.avail. It was done upstream as well as in Debian, but Ubuntu delayed the transition for some reason. I think we should do that transition in Ubuntu too. That will get Ubuntu in sync with the upstream documentation and the delta to Debian gets reduced a little. The changes needed are straightforward. I put a proposed upload in this PPA: https://launchpad.net/~gunnarhj/+archive/ubuntu/fontconfig and I would appreciate someone's eyes on it. So, what's the caveat? The only thing I can think of is that distros, system admins and individual users may have tweaked the font configuration by including symlinks which point to the moved files. While I don't have the impression that such symlinks are very frequent — custom conf files put directly in /etc/fonts/conf.d or equivalent places in $HOME seem to be more common — to the extent they exist, they will be silently disabled. Bug #2005124 revealed an example of a symlink which pointed to a file which will be moved if we do this. OTOH, in that case upstream added a symlink with the very same name, so we had to deal with that conflict. If the name of Kubuntu's link had been something else, we might not be aware of it yet. The changelog for this upload: https://launchpad.net/ubuntu/+source/fontconfig/2.10.1-0ubuntu1 states that the transition will be done "later with another upload once the details are sorted". Are there other details which I have missed? If not, I suppose that the potential inconvenience is approximately as big today as it was 2012. And since next LTS release is more than one year ahead, this ought to be an appropriate time to make the change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2007124/+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 1956248] Re: I get two characters in Activities when I press one key for the first key I press...
** Tags added: kinetic -- 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/1956248 Title: I get two characters in Activities when I press one key for the first key I press... Status in Dash to dock: New Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: If I click the Activities in the upper right hand corner of the screen, then do NOT click in the search bar and begin to type, I get two of whatever character I hit. At first I thought it was due to my keyboard wearing out, but it happens on multiple computers, and whatever key I type, even infrequently used ones. If I click in the search bar before I type, then the characters are not duplicated. If I then backspace over the single character that was correctly displayed in the search bar and type another character, that character is doubled. Bounce keys will not eliminate this either. I started noticing doubling characters a couple of weeks (approximately) ago. I didn't start to suspect the real reason until recently. Thanks for working on this for all of us! Rob ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jan 3 11:43:59 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-04-19 (990 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2021-10-12 (82 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1956248/+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 2007011] Re: In the Applications search, the first letter I type is repeated so there are two.
*** This bug is a duplicate of bug 1956248 *** https://bugs.launchpad.net/bugs/1956248 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 1956248, 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 1956248 I get two characters in Activities when I press one key for the first key I press... -- 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/2007011 Title: In the Applications search, the first letter I type is repeated so there are two. Status in gnome-shell package in Ubuntu: New Bug description: To reproduce this: Start a gnome-shell session, go to the Activities on the upper left hand corner of the screen. This opens up a "Type to search box at the top of the screen. Type any letter. It will appear twice. If you are looking for a program, for example, LTspice, the first two letters will repeat giving LLTspice, and it won't find the program until you backspace back until you have only L, then LTspice shows up. Thanks for all the fixes you provide! Rob ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Feb 11 18:44:18 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-12-09 (65 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2007011/+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 2006955] Re: Screens not detected anymore
Thanks for the bug report. Please try reinstalling this package: https://launchpad.net/ubuntu/+archive/primary/+files/linux-modules- extra-5.15.0-60-generic_5.15.0-60.66_amd64.deb and then reboot. If the problem persists after that then please run: journalctl -b0 > journal.txt and attach the resulting text file here. ** Tags added: amdgpu ** Summary changed: - Screens not detected anymore + [amdgpu] Screens not detected anymore in 5.15.0-60-generic (but 5.15.0-58-generic works) ** 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/2006955 Title: [amdgpu] Screens not detected anymore in 5.15.0-60-generic (but 5.15.0-58-generic works) Status in linux package in Ubuntu: Incomplete Bug description: I have 3 monitors, but since very recently (yesterday or so), only 1 of them seems to be detected. In the Settings app, under "Screen Display", I used to have a place where I can move my monitors relatively to each other, and adjust each of their settings. Now, I no longer have the monitor drag-and-drop zone, I only have one detected "Unknown display", fixed at 1920x1080 77.00 Hz (physically, it's a 1920x1080 144Hz) and I cannot change any setting except orientation, scaling, and fractional scaling. The bug started happening just when the kernel was auto-updated to 5.15.0-60-generic from 5.15.0-58-generic. `uname -a` reports: `Linux user-desktop 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux`. When I reboot with 5.15.0-58-generic, all of my 3 displays are detected and working fine. I also noticed the same problem happened when I installed 5.15.0-58-lowlatency. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 10 11:00:59 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-57-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-60-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1462:3816] InstallationDate: Installed on 2021-01-27 (743 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-60-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.name: B550 Phantom Gaming 4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd08/13/2020:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 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/2006955/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~d