[Desktop-packages] [Bug 1998765] Re: libnl3 3.4.0 doesn't work with WCN3980
I installed the updated version on the platform which needs this patch. After updating the packages, the platform can scan and connect to a WiFi network correctly. I also tried other amd64, armhf and arm64 platforms which don't require the patch originally and their wifi device still work after upgrading. $ dpkg -l |grep libnl ii libnl-3-200:armhf 3.4.0-1ubuntu0.1 armhf library for dealing with netlink sockets ii libnl-genl-3-200:armhf 3.4.0-1ubuntu0.1 armhf library for dealing with netlink sockets - generic netlink ii libnl-route-3-200:armhf3.4.0-1ubuntu0.1 armhf library for dealing with netlink sockets - route interface $ sudo netplan apply $ ip a ... 3: wlan0: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether dc:a6:32:37:fa:a7 brd ff:ff:ff:ff:ff:ff inet 10.102.138.56/22 brd 10.102.139.255 scope global dynamic wlan0 valid_lft 600sec preferred_lft 600sec inet6 fe80::dea6:32ff:fe37:faa7/64 scope link valid_lft forever preferred_lft forever $ sudo ping -I wlan0 8.8.8.8 PING 8.8.8.8 (8.8.8.8) from 10.102.138.56 wlan0: 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=57 time=10.4 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=57 time=5.64 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=57 time=5.73 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=57 time=6.09 ms 64 bytes from 8.8.8.8: icmp_seq=5 ttl=57 time=6.98 ms ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal ** Changed in: oem-priority/focal Status: New => Fix Committed ** Changed in: oem-priority/focal Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1998765 Title: libnl3 3.4.0 doesn't work with WCN3980 Status in OEM Priority Project: Fix Committed Status in OEM Priority Project focal series: Fix Committed Status in libnl3 package in Ubuntu: Fix Released Status in libnl3 source package in Focal: Fix Committed Status in libnl3 source package in Jammy: Invalid Bug description: [ Impact ] When testing Qualcomm qcs410 with WCN3980 with 20.04 and UC20, WCN3980 is not able connect to an AP. However, with the libnl3 (3.5.0) from BSP, WCN3980 can work correctly. After bisecting the commits from 3.4.0 to 3.5.0, this commit[1] is identified as the root cause. According to the commit, the "NLA_F_NESTED" flag should be set for kernel later than 5.2. [ Test Plan ] Verify with the updated version, the WIFI module can: 1. scan WIFI networks 2. connect to an available network 3. access to the connected network [ Where problems could occur ] 1. kernel versions without NLA_F_NESTED flag defined This flag is introduced before Linux kernel v5 (checked v3.x and v4.x have it). It would not be a problem for an older kernel to understand/work with this change. Since the GA kernel is 5.4, so a generic image would still work. 2. Drivers don't use the NESTED flag. According to hui.wang's input, this change should not affect drivers which don't use the NESTED flag. But, it'd be better to cover more Wifi modules. [ Other Info ] 22.04 is using libnl3 3.0.5-0.1, so only 20.04 needs this patch. [1] https://github.com/thom311/libnl/commit/7de65a051fb37ece16f896a7385073274b77a133 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998765/+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 1999008] Re: Xorg crashed with SIGABRT in xf86ModeVRefresh() from drmmode_output_add_gtf_modes() from drmmode_output_get_modes() from xf86ProbeOutputModes() from xf86InitialCon
Hello errors.ubuntu.com, or anyone else affected, Accepted xorg-server into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server/2:21.1.3-2ubuntu2.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: xorg-server (Ubuntu Jammy) Status: Confirmed => Fix Committed ** Tags added: verification-needed-jammy -- 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/1999008 Title: Xorg crashed with SIGABRT in xf86ModeVRefresh() from drmmode_output_add_gtf_modes() from drmmode_output_get_modes() from xf86ProbeOutputModes() from xf86InitialConfiguration() Status in xorg-server package in Ubuntu: Confirmed Status in xorg-server source package in Jammy: Fix Committed Status in xorg-server source package in Kinetic: Fix Committed Status in xorg-server source package in Lunar: Confirmed Bug description: [Impact] The recent SRU'd patch had a bug in it that caused a crash if xf86ModeVRefresh returned 0. Amend the patch to fix this. [Test case] Would need an affected system to test this on, but we haven't been able to reproduce this even on an identical system as on one of the reported errors (XPS 15 9560). [Where things could go wrong] This only adds a new check. -- The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:21.1.4-2ubuntu1.2, the problem page at https://errors.ubuntu.com/problem/67a241f90d338c8f1b9c48466cf1f6121bece6bf 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/xorg-server/+bug/1999008/+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 1999008] Re: Xorg crashed with SIGABRT in xf86ModeVRefresh() from drmmode_output_add_gtf_modes() from drmmode_output_get_modes() from xf86ProbeOutputModes() from xf86InitialCon
Hello errors.ubuntu.com, or anyone else affected, Accepted xorg-server into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server/2:21.1.4-2ubuntu1.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: xorg-server (Ubuntu Kinetic) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-kinetic -- 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/1999008 Title: Xorg crashed with SIGABRT in xf86ModeVRefresh() from drmmode_output_add_gtf_modes() from drmmode_output_get_modes() from xf86ProbeOutputModes() from xf86InitialConfiguration() Status in xorg-server package in Ubuntu: Confirmed Status in xorg-server source package in Jammy: Confirmed Status in xorg-server source package in Kinetic: Fix Committed Status in xorg-server source package in Lunar: Confirmed Bug description: [Impact] The recent SRU'd patch had a bug in it that caused a crash if xf86ModeVRefresh returned 0. Amend the patch to fix this. [Test case] Would need an affected system to test this on, but we haven't been able to reproduce this even on an identical system as on one of the reported errors (XPS 15 9560). [Where things could go wrong] This only adds a new check. -- The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:21.1.4-2ubuntu1.2, the problem page at https://errors.ubuntu.com/problem/67a241f90d338c8f1b9c48466cf1f6121bece6bf 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/xorg-server/+bug/1999008/+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 2003140] Re: Ubuntu laptop can't use external monitors
Thanks for the bug report. The Nvidia Xorg driver doesn't appear to be loading for some reason, which is the main problem. Although the Nvidia kernel driver is loaded. You are using Nvidia driver version 470.161.03 but their website suggests the current supported version for your Quadro P620 is 525.78.01. But regardless of version, it looks like the issue here is a failed installation of the Xorg driver. And the bug reporting system is suggesting you might have tried a manual driver installation in the past too. To fix this, please open the 'Additional Drivers' app and use it to install a newer Nvidia driver. Please do not attempt to install drivers manually without using the Additional Drivers app because doing so can lead to bugs like this one. ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-470 (Ubuntu) ** Changed in: nvidia-graphics-drivers-470 (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 in Ubuntu. https://bugs.launchpad.net/bugs/2003140 Title: Ubuntu laptop can't use external monitors Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Bug description: # What happens (Steps to reproduce): 1. Install a clean version of Ubuntu onto a laptop: Hardware="https://www.dell.com/support/manuals/en-uk/precision-15-3541-laptop/precision_3541_setupspecs/video?guid=guid-0712681b-956e-4229-96a7-545baca605fc=en-us; VERSION="20.04.5 LTS (Focal Fossa)" nick@Precision-3541:~$ sudo lshw -C display [sudo] password for nick: *-display description: 3D controller product: GP107GLM [Quadro P620] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list rom configuration: driver=nvidia latency=0 resources: irq:168 memory:ec00-ecff memory:c000-cfff memory:d000-d1ff ioport:3000(size=128) memory:ed00-ed07 *-display description: VGA compatible controller product: UHD Graphics 630 (Mobile) vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 00 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:166 memory:eb00-ebff memory:8000-8fff ioport:4000(size=64) memory:c-d 2. Connect a monitor and laptop with an HDMI cable 3. Result - The monitor should display "No Signal" - Ubuntu should recognize the monitor, but not display anything on it. # What should happen Ubuntu should send signal to external monitors connected to the HDMI port. It should automatically configure discrete graphics cards. The same hardware works when booted from the Windows partition. # What I've tried ## Things that worked None ## Things that worked temporarily https://askubuntu.com/questions/1105332/external-monitor-not-working-ubuntu-nvidia/1134579#1134579 Installing NVidia-Prime, Setting "Performance Mode" to always use the discrete GPU ## Things that did not work (from various forums) 1. Using multiple different drivers via "Software/Additional Drivers" 2. Using the driver from NVidia's website 3. Enabling NVidia via a modprob parameter at startup 4. Varius xorg configuration files ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-58-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 470.161.03 Wed Oct 19 00:10:36 UTC 2022 GCC version: gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1) ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 16:58:33 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.161.03, 5.15.0-58-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA
[Desktop-packages] [Bug 2003136] Re: Settings window becomes broken and unresponsive when changing display scale, sometimes
I experience this bug occasionally too. For me the workaround is to find the invisible close button in the old window and just close the Settings app. I suppose Alt+F4 might work too? Then just open the Settings app again. -- 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/2003136 Title: Settings window becomes broken and unresponsive when changing display scale, sometimes Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I might need help routing this to the correct project. gnome-display-properties I believe is the application in foreground. I was using it normally, then switched the screen resolution scale to 100% (down from 200%). I had a Chrome window open which now had the inner icons shrunk, but not the boundaries of the window. So I moved the chrome window around, and noticed this corruption / tearing. The video is interesting because I believe it is telling us that the boundaries of the window are not (re?)set properly for the gnome- display-properties when display scale is applied. Is this what you see in the video too ? ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..52.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 470.161.03 Wed Oct 19 00:10:36 UTC 2022 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1) ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 17:49:57 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. TU117 [GeForce GTX 1650] [3842:1257] InstallationDate: Installed on 2023-01-09 (8 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-01-15 (2 days ago) dmi.bios.date: 12/05/2022 dmi.bios.release: 1.58 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET82W (1.58 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET82W(1.58):bd12/05/2022:br1.58:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 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
[Desktop-packages] [Bug 2003136] Re: Settings window becomes broken and unresponsive when changing display scale, sometimes
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- 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/2003136 Title: Settings window becomes broken and unresponsive when changing display scale, sometimes Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I might need help routing this to the correct project. gnome-display-properties I believe is the application in foreground. I was using it normally, then switched the screen resolution scale to 100% (down from 200%). I had a Chrome window open which now had the inner icons shrunk, but not the boundaries of the window. So I moved the chrome window around, and noticed this corruption / tearing. The video is interesting because I believe it is telling us that the boundaries of the window are not (re?)set properly for the gnome- display-properties when display scale is applied. Is this what you see in the video too ? ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..52.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 470.161.03 Wed Oct 19 00:10:36 UTC 2022 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1) ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 17:49:57 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. TU117 [GeForce GTX 1650] [3842:1257] InstallationDate: Installed on 2023-01-09 (8 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-01-15 (2 days ago) dmi.bios.date: 12/05/2022 dmi.bios.release: 1.58 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET82W (1.58 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET82W(1.58):bd12/05/2022:br1.58:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 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
[Desktop-packages] [Bug 2003107] Re: Video player doesn't start
*** This bug is a duplicate of bug 1965563 *** https://bugs.launchpad.net/bugs/1965563 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 1965563, 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. ** Tags added: nvidia ** This bug has been marked a duplicate of bug 1965563 GNOME apps crash with "Protocol error" in NVIDIA Wayland sessions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/2003107 Title: Video player doesn't start Status in totem package in Ubuntu: New Bug description: Video player doesn't start at all. Running `totem` from the terminal I get: ``` (totem:97829): GStreamer-GL-CRITICAL **: 18:47:08.513: Failed to flush Wayland connection Gdk-Message: 18:47:08.513: Error reading events from display: Protocol error ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: totem 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 18:48:34 2023 InstallationDate: Installed on 2022-04-22 (270 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/2003107/+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 2003136] Re: Settings window becomes broken and unresponsive when changing display scale, sometimes
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- 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/2003136 Title: Settings window becomes broken and unresponsive when changing display scale, sometimes Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I might need help routing this to the correct project. gnome-display-properties I believe is the application in foreground. I was using it normally, then switched the screen resolution scale to 100% (down from 200%). I had a Chrome window open which now had the inner icons shrunk, but not the boundaries of the window. So I moved the chrome window around, and noticed this corruption / tearing. The video is interesting because I believe it is telling us that the boundaries of the window are not (re?)set properly for the gnome- display-properties when display scale is applied. Is this what you see in the video too ? ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..52.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 470.161.03 Wed Oct 19 00:10:36 UTC 2022 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1) ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 17:49:57 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. TU117 [GeForce GTX 1650] [3842:1257] InstallationDate: Installed on 2023-01-09 (8 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-01-15 (2 days ago) dmi.bios.date: 12/05/2022 dmi.bios.release: 1.58 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET82W (1.58 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET82W(1.58):bd12/05/2022:br1.58:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 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
[Desktop-packages] [Bug 2003136] Re: Settings window becomes broken and unresponsive when changing scales, sometimes
** Summary changed: - video corruption when using gnome-display settings + Settings window becomes broken and unresponsive when changing scales, sometimes ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Settings window becomes broken and unresponsive when changing scales, sometimes + Settings window becomes broken and unresponsive when changing display scale, sometimes -- 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/2003136 Title: Settings window becomes broken and unresponsive when changing display scale, sometimes Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I might need help routing this to the correct project. gnome-display-properties I believe is the application in foreground. I was using it normally, then switched the screen resolution scale to 100% (down from 200%). I had a Chrome window open which now had the inner icons shrunk, but not the boundaries of the window. So I moved the chrome window around, and noticed this corruption / tearing. The video is interesting because I believe it is telling us that the boundaries of the window are not (re?)set properly for the gnome- display-properties when display scale is applied. Is this what you see in the video too ? ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..52.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 470.161.03 Wed Oct 19 00:10:36 UTC 2022 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1) ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 17:49:57 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. TU117 [GeForce GTX 1650] [3842:1257] InstallationDate: Installed on 2023-01-09 (8 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-01-15 (2 days ago) dmi.bios.date: 12/05/2022 dmi.bios.release: 1.58 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET82W (1.58 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET82W(1.58):bd12/05/2022:br1.58:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core:
[Desktop-packages] [Bug 1770990] Re: Dock not shown in second monitor except by pressing SUPER
** Bug watch added: github.com/micheleg/dash-to-dock/issues #1877 https://github.com/micheleg/dash-to-dock/issues/1877 ** Also affects: dash-to-dock via https://github.com/micheleg/dash-to-dock/issues/1877 Importance: Unknown Status: Unknown ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1770990 Title: Dock not shown in second monitor except by pressing SUPER Status in Dash to dock: Unknown Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: The dock is not visible in second monitor except when I press SUPER key. The dock's configuration is set to "All monitors" but even when set only to my second monitor the problem also happens. Furthemore, I tried to use 'mirrored' monitors and the dock is not shown in any of them! $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 $ apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Instalado: 0.9.1 Candidato: 0.9.1 Tabela de versão: *** 0.9.1 500 500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://br.archive.ubuntu.com/ubuntu bionic/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.9.1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun May 13 14:12:06 2018 InstallationDate: Installed on 2018-04-27 (16 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1770990/+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 2000423] Re: "Alternate Characters Key" UI not reflecting current choice
Hello Gunnar, or anyone else affected, Accepted gnome-control-center into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-control- center/1:41.7-0ubuntu0.22.04.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-control-center (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- 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/2000423 Title: "Alternate Characters Key" UI not reflecting current choice Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Jammy: Fix Committed Status in gnome-control-center source package in Kinetic: Won't Fix Bug description: [ Impact ] When you set an "Alternate Characters Key", only two of the available options — "None" and "Right Alt" — are correctly reflected in the UI. If you select some of the other options, the UI tells you that "None" is selected. The xkb-options dconf value is correct, though. As an example: If I pick Right Ctrl, xkb-options is correctly changed to ['lv3:ralt_alt', 'lv3:switch']. So it looks like it parses lv3:ralt_alt instead of lv3:switch, and incorrectly concludes that the current value is "None". [ Test Plan ] * Install gnome-control-center from jammy-proposed. * Go to Settings -> Keyboard -> Alternate Characters Key and pick some other option but "None" or "Right Alt". * Make sure that the option you selected is correctly reflected in the UI. [ Where problems could occur ] This is a targeted fix which only affects a specific control in Settings. Considering the current broken state, I'd say that the risk is minimal that the change would make it worse. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2000423/+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 2003031] Re: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7"
Please report all issues not relating to "adding CRTC not allowed without modesets" as new bugs. -- 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/2003031 Title: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7" Status in Linux: Unknown Status in linux package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: GJS crashes - here's the crashdump. I saw the crash occur after a screensaver had been running, and the screens had gone blank. I assume this means they were turned off by the sleep timer. When I worke the machine, I was presented with a prompt, I *quickly* entered my login credentials and momentarily saw the desktop and all open programs on it. Then, the screens (3) flickered and I saw the login prompt again. I logged in (again), and all applications had been shut down. I checked /var/log/syslog and saw the following details -- see (log). Uploaded file, and the crashdump. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 16 20:52:55 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] InstallationDate: Installed on 2023-01-09 (7 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to kinetic on 2023-01-15 (1 days ago) dmi.bios.date: 07/27/2022 dmi.bios.release: 1.55 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET79W (1.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 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/linux/+bug/2003031/+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 2003024] Re: Dock prevents Search switching to some apps in different workspaces
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2003024 Title: Dock prevents Search switching to some apps in different workspaces Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: While the Ubuntu Dock extension is active, searching for certain applications on the overview screen and pressing Enter does not switch to them if an instance exists on other workspaces. Notably a few GNOME Apps such as Nautilus and gedit. From the programs I've tested: - Pressing Enter on Nautilus, gedit and Firefox does nothing, not even close the overview nor switch to an open instance. - Pressing Enter on Thunderbird switches to it properly. - Pressing Enter on KeepassXC gets you a notification and clicking it will switch to it. - Pressing Enter on Terminal opens a new instance on the current workspace instead of switching to an existing one if one exists on another workspace. If the dock extension is disabled, searching for a program and pressing Enter behaves as expected, that is, the program becomes focused and is switched to. Edit: After some more testing, it only happens if either "Include applications from the current workspace only" or "Include applications from each monitor only" options are activated in Control Center > Multitasking > Application Switching I apologize in case that wasn't well explained, if there are any doubts, I'll attempt to record a video of it. Ubuntu: 22.04.01 LTS Ubuntu Dock: 72~ubuntu5.22.04.1 gnome-shell: 42.5-0ubuntu1 Running on Xorg. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 16 20:04:47 2023 InstallationDate: Installed on 2022-09-12 (126 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2003024/+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 2003031] Re: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7"
Comment #8 is a crash in the 'nouveau' kernel driver unrelated to this bug. Although you should technically report a new bug for that, 'nouveau' is not very well maintained and we would always just recommend using the 'Additional Drivers' app to install one of the official Nvidia drivers instead. -- 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/2003031 Title: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7" Status in Linux: Unknown Status in linux package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: GJS crashes - here's the crashdump. I saw the crash occur after a screensaver had been running, and the screens had gone blank. I assume this means they were turned off by the sleep timer. When I worke the machine, I was presented with a prompt, I *quickly* entered my login credentials and momentarily saw the desktop and all open programs on it. Then, the screens (3) flickered and I saw the login prompt again. I logged in (again), and all applications had been shut down. I checked /var/log/syslog and saw the following details -- see (log). Uploaded file, and the crashdump. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 16 20:52:55 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] InstallationDate: Installed on 2023-01-09 (7 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to kinetic on 2023-01-15 (1 days ago) dmi.bios.date: 07/27/2022 dmi.bios.release: 1.55 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET79W (1.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 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/linux/+bug/2003031/+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 1969140] Re: Window minimize animation flickers and appears in the wrong place in Xorg sessions
** No longer affects: nautilus (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/1969140 Title: Window minimize animation flickers and appears in the wrong place in Xorg sessions Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Bug description: Graphical glitches appears while minimizing or maximizing apps in x11 session randomly, screencast below ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 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: Thu Apr 14 17:07:49 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2022-04-12 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1969140/+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 2003099] Re: Flickering when minimizing
*** This bug is a duplicate of bug 1969140 *** https://bugs.launchpad.net/bugs/1969140 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 1969140, 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. ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** This bug has been marked a duplicate of bug 1969140 Window minimize animation flickers and appears in the wrong place in Xorg sessions -- 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/2003099 Title: Flickering when minimizing Status in mutter package in Ubuntu: New Bug description: When minimizing windowed applications, the animation sometimes jumps wildly around, mostly to the top left corner of the screen. I found a temporary workaround with a config file in /etc/X11/xorg.conf.d/20-intel.conf, which supposedly has some other unwanted effects on other programs. Thanks for your help!! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-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..3c.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.60.11 Wed Nov 23 23:04:03 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 17:12:59 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo WhiskeyLake-U GT2 [UHD Graphics 620] [17aa:2283] Subsystem: Lenovo GP108M [GeForce MX250] [17aa:2283] InstallationDate: Installed on 2023-01-02 (14 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20N4002VGE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=72ad0f02-9e2a-4714-8427-9372619f5f04 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2020 dmi.bios.release: 1.68 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET90W (1.68 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N4002VGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnLENOVO:bvrN2IET90W(1.68):bd07/06/2020:br1.68:efr1.17:svnLENOVO:pn20N4002VGE:pvrThinkPadT590:rvnLENOVO:rn20N4002VGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20N4_BU_Think_FM_ThinkPadT590: dmi.product.family: ThinkPad T590 dmi.product.name: 20N4002VGE dmi.product.sku: LENOVO_MT_20N4_BU_Think_FM_ThinkPad T590 dmi.product.version: ThinkPad T590 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.3 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.3-2ubuntu2.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/mutter/+bug/2003099/+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 2003104] Re: Transparency ignored in full screen mode
Bug 561370 might have moved to happening less often (or never when windowed) since the switch to Wayland. If we can show it's still intermittent when windowed under Xorg then I would recommend marking this as a duplicate of bug 561370. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2003104 Title: Transparency ignored in full screen mode Status in gnome-terminal package in Ubuntu: New Bug description: Ubuntu 23.04 running wayland gnome-terminal 3.46.7-1ubuntu1 In gnome-terminal, I have set the transparency to some amount. When I go to full screen (F11), the transparency is lost and the default transparency is used. When I exit full screen, the transparency comes back and I can see in the profile settings that the transparency has not changed. It seems that tranparency was accidentally removed, and then re-added via https://git.launchpad.net/ubuntu/+source/gnome-terminal/tree/debian/patches/0001-Restore-transparency.patch?h=applied/ubuntu/lunar-devel However, maybe something was missed with regards to full screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2003104/+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 2003140] Re: Ubuntu laptop can't use external monitors
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is mostly about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 -- 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/2003140 Title: Ubuntu laptop can't use external monitors Status in xorg package in Ubuntu: New Bug description: # What happens (Steps to reproduce): 1. Install a clean version of Ubuntu onto a laptop: Hardware="https://www.dell.com/support/manuals/en-uk/precision-15-3541-laptop/precision_3541_setupspecs/video?guid=guid-0712681b-956e-4229-96a7-545baca605fc=en-us; VERSION="20.04.5 LTS (Focal Fossa)" nick@Precision-3541:~$ sudo lshw -C display [sudo] password for nick: *-display description: 3D controller product: GP107GLM [Quadro P620] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list rom configuration: driver=nvidia latency=0 resources: irq:168 memory:ec00-ecff memory:c000-cfff memory:d000-d1ff ioport:3000(size=128) memory:ed00-ed07 *-display description: VGA compatible controller product: UHD Graphics 630 (Mobile) vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 00 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:166 memory:eb00-ebff memory:8000-8fff ioport:4000(size=64) memory:c-d 2. Connect a monitor and laptop with an HDMI cable 3. Result - The monitor should display "No Signal" - Ubuntu should recognize the monitor, but not display anything on it. # What should happen Ubuntu should send signal to external monitors connected to the HDMI port. It should automatically configure discrete graphics cards. The same hardware works when booted from the Windows partition. # What I've tried ## Things that worked None ## Things that worked temporarily https://askubuntu.com/questions/1105332/external-monitor-not-working-ubuntu-nvidia/1134579#1134579 Installing NVidia-Prime, Setting "Performance Mode" to always use the discrete GPU ## Things that did not work (from various forums) 1. Using multiple different drivers via "Software/Additional Drivers" 2. Using the driver from NVidia's website 3. Enabling NVidia via a modprob parameter at startup 4. Varius xorg configuration files ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-58-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 470.161.03 Wed Oct 19 00:10:36 UTC 2022 GCC version: gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1) ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 16:58:33 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.161.03, 5.15.0-58-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:091a] Subsystem: Dell GP107GLM [Quadro P620] [1028:091a] InstallationDate: Installed on 2023-01-06 (11 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. Precision 3541 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash
[Desktop-packages] [Bug 2003108] Re: Nautilus still says "do not unplug the device" even if the writing process is finished
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2003108 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- 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/2003108 Title: Nautilus still says "do not unplug the device" even if the writing process is finished Status in nautilus package in Ubuntu: New Bug description: After I click on the "unmount" icon next to the USB device in the file tree sidebar on Nautilus, the notification appears with the text "do not unplug/remove the device". The problem is that the notification doesn't go away for several time, even if the writing process is already finished, also with that notification still visible in the right top corner I can remount the USN by clicking its name in Nautilus, use it, and unmount it. If I copy something in the USB, the "copying files" popup process should finish only if the writing process is really completed (as it was in the previous Ubuntu versions...). I'm using Ubuntu 22.04.1 LTS. apt-cache policy nautilus: nautilus: Installato: 1:42.2-0ubuntu1 Candidato: 1:42.2-0ubuntu1 Tabella versione: *** 1:42.2-0ubuntu1 100 100 /var/lib/dpkg/status 1:42.0-1ubuntu2 500 500 http://it.archive.ubuntu.com/ubuntu jammy/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2003108/+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 2003104] Re: Transparency ignored in full screen mode
If the problem is intermittent then that's bug 561370 unfortunately. ** Tags added: lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2003104 Title: Transparency ignored in full screen mode Status in gnome-terminal package in Ubuntu: New Bug description: Ubuntu 23.04 running wayland gnome-terminal 3.46.7-1ubuntu1 In gnome-terminal, I have set the transparency to some amount. When I go to full screen (F11), the transparency is lost and the default transparency is used. When I exit full screen, the transparency comes back and I can see in the profile settings that the transparency has not changed. It seems that tranparency was accidentally removed, and then re-added via https://git.launchpad.net/ubuntu/+source/gnome-terminal/tree/debian/patches/0001-Restore-transparency.patch?h=applied/ubuntu/lunar-devel However, maybe something was missed with regards to full screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2003104/+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 2003031] Re: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7"
Should I open this as a different issue with the Core X Chroma Thunderbolt 3 enclosure ? It's very similar. -- 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/2003031 Title: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7" Status in Linux: Unknown Status in linux package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: GJS crashes - here's the crashdump. I saw the crash occur after a screensaver had been running, and the screens had gone blank. I assume this means they were turned off by the sleep timer. When I worke the machine, I was presented with a prompt, I *quickly* entered my login credentials and momentarily saw the desktop and all open programs on it. Then, the screens (3) flickered and I saw the login prompt again. I logged in (again), and all applications had been shut down. I checked /var/log/syslog and saw the following details -- see (log). Uploaded file, and the crashdump. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 16 20:52:55 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] InstallationDate: Installed on 2023-01-09 (7 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to kinetic on 2023-01-15 (1 days ago) dmi.bios.date: 07/27/2022 dmi.bios.release: 1.55 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET79W (1.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 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/linux/+bug/2003031/+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 2003031] Re: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7"
Ok, I am getting a slightly different, but perhaps related problem with another USB-C / eGPU encapsulation (PCIE tunneles over USB-C basically) device. I've done some testing with the Razer Core X Chroma, a USB-C connected Thunderbolt 3 eGPU enclosure. Reference to hardware is here : https://www.razer.com/gaming-egpus/Razer-Core-X/RC21-01430100-R3U1 I have 2x displays now connected to the internal PCIE nVidia TU117 [GeForce GTX 1650] loaded in the unit. The BIOS seems to work fine, , but when I get to the gnome login screen things hang. I am narrowing it down, but just like the display blanking on the Intel based on cursor location, I am seeing the same behavior with this enclosure - if at boot time the enclosure is connected, then the displays will lock up. If, I move the mouse to the right edge of the screen , the desktop will also lock up. Attached are the logs of the attachment, then detachment of this enclosure. Note that on re-attaching the enclosure the USB devices which previously worked fine attached to the enclosure no longer function (perhaps not deregistered properly?). Details for HW info beadon@semiauto:~$ hwinfo --gfxcard --short graphics card: nVidia TU117 [GeForce GTX 1650] Intel TigerLake-LP GT2 [Iris Xe Graphics] Primary display adapter: #26 ** Attachment added: "log-for-chroma.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003031/+attachment/5642118/+files/log-for-chroma.txt -- 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/2003031 Title: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7" Status in Linux: Unknown Status in linux package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: GJS crashes - here's the crashdump. I saw the crash occur after a screensaver had been running, and the screens had gone blank. I assume this means they were turned off by the sleep timer. When I worke the machine, I was presented with a prompt, I *quickly* entered my login credentials and momentarily saw the desktop and all open programs on it. Then, the screens (3) flickered and I saw the login prompt again. I logged in (again), and all applications had been shut down. I checked /var/log/syslog and saw the following details -- see (log). Uploaded file, and the crashdump. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 16 20:52:55 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] InstallationDate: Installed on 2023-01-09 (7 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to kinetic on 2023-01-15 (1 days ago) dmi.bios.date: 07/27/2022 dmi.bios.release: 1.55 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET79W (1.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6:
[Desktop-packages] [Bug 2003140] Re: Ubuntu laptop can't use external monitors
** Description changed: # What happens (Steps to reproduce): 1. Install a clean version of Ubuntu onto a laptop: Hardware="https://www.dell.com/support/manuals/en-uk/precision-15-3541-laptop/precision_3541_setupspecs/video?guid=guid-0712681b-956e-4229-96a7-545baca605fc=en-us; VERSION="20.04.5 LTS (Focal Fossa)" nick@Precision-3541:~$ sudo lshw -C display [sudo] password for nick: *-display description: 3D controller product: GP107GLM [Quadro P620] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list rom configuration: driver=nvidia latency=0 resources: irq:168 memory:ec00-ecff memory:c000-cfff memory:d000-d1ff ioport:3000(size=128) memory:ed00-ed07 *-display description: VGA compatible controller product: UHD Graphics 630 (Mobile) vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 00 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:166 memory:eb00-ebff memory:8000-8fff ioport:4000(size=64) memory:c-d 2. Connect a monitor and laptop with an HDMI cable 3. Result - The monitor should display "No Signal" - Ubuntu should recognize the monitor, but not display anything on it. # What should happen Ubuntu should send signal to external monitors connected to the HDMI port. It should automatically configure discrete graphics cards. The same hardware works when booted from the Windows partition. # What I've tried ## Things that worked + None + + ## Things that worked temporarily https://askubuntu.com/questions/1105332/external-monitor-not-working-ubuntu-nvidia/1134579#1134579 - Edit /lib/modprobe.d/nvidia-kms.conf to enable modsetting - - ## Things that worked temporarily - Installing NVidia-Prime, Setting "Performance Mode" to always use the discrete GPU + Installing NVidia-Prime, Setting "Performance Mode" to always use the + discrete GPU ## Things that did not work (from various forums) 1. Using multiple different drivers via "Software/Additional Drivers" 2. Using the driver from NVidia's website 3. Enabling NVidia via a modprob parameter at startup 4. Varius xorg configuration files ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-58-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 470.161.03 Wed Oct 19 00:10:36 UTC 2022 GCC version: gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1) ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 16:58:33 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.161.03, 5.15.0-58-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:091a] Subsystem: Dell GP107GLM [Quadro P620] [1028:091a] InstallationDate: Installed on 2023-01-06 (11 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. Precision 3541 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=90df9afc-2dd2-439d-a69c-3aa27146e9fc ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: dmi.bios.date: 09/13/2022 dmi.bios.release: 1.23 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.23.0 dmi.board.name: 0Y8H01 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.23.0:bd09/13/2022:br1.23:svnDellInc.:pnPrecision3541:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:sku091A:
[Desktop-packages] [Bug 2003140] Re: Ubuntu laptop can't use external monitors
** Package changed: ubuntu => xorg (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/2003140 Title: Ubuntu laptop can't use external monitors Status in xorg package in Ubuntu: New Bug description: # What happens (Steps to reproduce): 1. Install a clean version of Ubuntu onto a laptop: Hardware="https://www.dell.com/support/manuals/en-uk/precision-15-3541-laptop/precision_3541_setupspecs/video?guid=guid-0712681b-956e-4229-96a7-545baca605fc=en-us; VERSION="20.04.5 LTS (Focal Fossa)" nick@Precision-3541:~$ sudo lshw -C display [sudo] password for nick: *-display description: 3D controller product: GP107GLM [Quadro P620] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list rom configuration: driver=nvidia latency=0 resources: irq:168 memory:ec00-ecff memory:c000-cfff memory:d000-d1ff ioport:3000(size=128) memory:ed00-ed07 *-display description: VGA compatible controller product: UHD Graphics 630 (Mobile) vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 00 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:166 memory:eb00-ebff memory:8000-8fff ioport:4000(size=64) memory:c-d 2. Connect a monitor and laptop with an HDMI cable 3. Result - The monitor should display "No Signal" - Ubuntu should recognize the monitor, but not display anything on it. # What should happen Ubuntu should send signal to external monitors connected to the HDMI port. It should automatically configure discrete graphics cards. The same hardware works when booted from the Windows partition. # What I've tried ## Things that worked https://askubuntu.com/questions/1105332/external-monitor-not-working-ubuntu-nvidia/1134579#1134579 Edit /lib/modprobe.d/nvidia-kms.conf to enable modsetting ## Things that worked temporarily Installing NVidia-Prime, Setting "Performance Mode" to always use the discrete GPU ## Things that did not work (from various forums) 1. Using multiple different drivers via "Software/Additional Drivers" 2. Using the driver from NVidia's website 3. Enabling NVidia via a modprob parameter at startup 4. Varius xorg configuration files ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-58-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 470.161.03 Wed Oct 19 00:10:36 UTC 2022 GCC version: gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1) ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 16:58:33 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.161.03, 5.15.0-58-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:091a] Subsystem: Dell GP107GLM [Quadro P620] [1028:091a] InstallationDate: Installed on 2023-01-06 (11 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. Precision 3541 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=90df9afc-2dd2-439d-a69c-3aa27146e9fc ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: dmi.bios.date: 09/13/2022 dmi.bios.release: 1.23 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.23.0 dmi.board.name: 0Y8H01 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc.
[Desktop-packages] [Bug 2003140] [NEW] Ubuntu laptop can't use external monitors
You have been subscribed to a public bug: # What happens (Steps to reproduce): 1. Install a clean version of Ubuntu onto a laptop: Hardware="https://www.dell.com/support/manuals/en-uk/precision-15-3541-laptop/precision_3541_setupspecs/video?guid=guid-0712681b-956e-4229-96a7-545baca605fc=en-us; VERSION="20.04.5 LTS (Focal Fossa)" nick@Precision-3541:~$ sudo lshw -C display [sudo] password for nick: *-display description: 3D controller product: GP107GLM [Quadro P620] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list rom configuration: driver=nvidia latency=0 resources: irq:168 memory:ec00-ecff memory:c000-cfff memory:d000-d1ff ioport:3000(size=128) memory:ed00-ed07 *-display description: VGA compatible controller product: UHD Graphics 630 (Mobile) vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 00 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:166 memory:eb00-ebff memory:8000-8fff ioport:4000(size=64) memory:c-d 2. Connect a monitor and laptop with an HDMI cable 3. Result - The monitor should display "No Signal" - Ubuntu should recognize the monitor, but not display anything on it. # What should happen Ubuntu should send signal to external monitors connected to the HDMI port. It should automatically configure discrete graphics cards. The same hardware works when booted from the Windows partition. # What I've tried ## Things that worked https://askubuntu.com/questions/1105332/external-monitor-not-working-ubuntu-nvidia/1134579#1134579 Edit /lib/modprobe.d/nvidia-kms.conf to enable modsetting ## Things that worked temporarily Installing NVidia-Prime, Setting "Performance Mode" to always use the discrete GPU ## Things that did not work (from various forums) 1. Using multiple different drivers via "Software/Additional Drivers" 2. Using the driver from NVidia's website 3. Enabling NVidia via a modprob parameter at startup 4. Varius xorg configuration files ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-58-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 470.161.03 Wed Oct 19 00:10:36 UTC 2022 GCC version: gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1) ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 16:58:33 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.161.03, 5.15.0-58-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:091a] Subsystem: Dell GP107GLM [Quadro P620] [1028:091a] InstallationDate: Installed on 2023-01-06 (11 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. Precision 3541 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=90df9afc-2dd2-439d-a69c-3aa27146e9fc ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: dmi.bios.date: 09/13/2022 dmi.bios.release: 1.23 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.23.0 dmi.board.name: 0Y8H01 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.23.0:bd09/13/2022:br1.23:svnDellInc.:pnPrecision3541:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:sku091A: dmi.product.family: Precision dmi.product.name: Precision 3541 dmi.product.sku: 091A dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers:
[Desktop-packages] [Bug 2003136] Re: video corruption when using gnome-display settings
attached file. Timeout was received for the file upload. Attaching a vimeo link instead. https://vimeo.com/790229569 ** Attachment added: "PXL_20230117_224753761.mp4" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2003136/+attachment/5642093/+files/PXL_20230117_224753761.mp4 -- 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/2003136 Title: video corruption when using gnome-display settings Status in xorg package in Ubuntu: New Bug description: I might need help routing this to the correct project. gnome-display-properties I believe is the application in foreground. I was using it normally, then switched the screen resolution scale to 100% (down from 200%). I had a Chrome window open which now had the inner icons shrunk, but not the boundaries of the window. So I moved the chrome window around, and noticed this corruption / tearing. The video is interesting because I believe it is telling us that the boundaries of the window are not (re?)set properly for the gnome- display-properties when display scale is applied. Is this what you see in the video too ? ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..52.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 470.161.03 Wed Oct 19 00:10:36 UTC 2022 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1) ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 17:49:57 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. TU117 [GeForce GTX 1650] [3842:1257] InstallationDate: Installed on 2023-01-09 (8 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-01-15 (2 days ago) dmi.bios.date: 12/05/2022 dmi.bios.release: 1.58 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET82W (1.58 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET82W(1.58):bd12/05/2022:br1.58:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 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:
[Desktop-packages] [Bug 1870597] Re: libinput says "your system is too slow"
I am seeing this issue in Ubuntu 22.10 , specifically for a Razer Deathadder mouse : Jan 17 17:59:28 semiauto /usr/libexec/gdm-x-session[2147]: (EE) event20 - Razer Razer DeathAdder: client bug: event processing lagging behind by 24ms, your system is too slow Which information do you need to troubleshoot further ? -- 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/1870597 Title: libinput says "your system is too slow" Status in GNOME Shell: Fix Released Status in libinput: Fix Released Status in Linux: Confirmed Status in libinput package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Confirmed Bug description: During the freeze, the output of the install had a message from "gdm- x-session" saying "your system is too slow". To reproduce: 1. Launch the Ubuntu installer 2. Begin the installation process 3. When the installation process begins, move the cursor around 4. Notice how the PC freezes and drops mouse events Description: Ubuntu Focal Fossa (development branch) Release: 20.04 gnome-shell: Installed: 3.36.0-2ubuntu2 Candidate: 3.36.0-2ubuntu2 Version table: *** 3.36.0-2ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CasperVersion: 1.442 Date: Fri Apr 3 14:24:21 2020 DisplayManager: gdm3 GsettingsChanges: LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 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/1870597/+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 2003136] [NEW] video corruption when using gnome-display settings
Public bug reported: I might need help routing this to the correct project. gnome-display-properties I believe is the application in foreground. I was using it normally, then switched the screen resolution scale to 100% (down from 200%). I had a Chrome window open which now had the inner icons shrunk, but not the boundaries of the window. So I moved the chrome window around, and noticed this corruption / tearing. The video is interesting because I believe it is telling us that the boundaries of the window are not (re?)set properly for the gnome- display-properties when display scale is applied. Is this what you see in the video too ? ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..52.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 470.161.03 Wed Oct 19 00:10:36 UTC 2022 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1) ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 17:49:57 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. TU117 [GeForce GTX 1650] [3842:1257] InstallationDate: Installed on 2023-01-09 (8 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-01-15 (2 days ago) dmi.bios.date: 12/05/2022 dmi.bios.release: 1.58 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET82W (1.58 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET82W(1.58):bd12/05/2022:br1.58:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption kinetic 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/2003136 Title: video corruption when using gnome-display settings Status in xorg package in Ubuntu: New Bug description: I might need help routing this to the correct project. gnome-display-properties I believe is the application in foreground. I was using it normally, then switched the screen resolution scale to 100% (down from 200%). I had a Chrome window open which now had the inner icons
[Desktop-packages] [Bug 2002941] Re: [BPO] libreoffice 7.4.4 for jammy
** Description changed: [Impact] * LibreOffice 7.4.4 is in its forth bugfix release of the 7.4 line: https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.4_release * This source packages matches the proposed SRU for kinetic handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2001911 and its backport is currently provided by the LibreOffice Fresh PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/ppa/+packages * LibreOffice 7.3.7 (EOL since November 30, 2022) is currently released in jammy. * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.4.4-0ubuntu0.22.10.1 * Backport target is Jammy/22.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_74/1542/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/amd64/libr/libreoffice/20230117_121308_55f21@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/arm64/libr/libreoffice/20230117_004531_c08ab@/log.gz - * [armhf] ... + * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/armhf/libr/libreoffice/20230117_192827_df4b4@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/ppc64el/libr/libreoffice/20230116_230929_28cc3@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/s390x/libr/libreoffice/20230117_034834_09f33@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. ** Description changed: [Impact] * LibreOffice 7.4.4 is in its forth bugfix release of the 7.4 line: https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.4_release * This source packages matches the proposed SRU for kinetic handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2001911 and its backport is currently provided by the LibreOffice Fresh PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/ppa/+packages * LibreOffice 7.3.7 (EOL since November 30, 2022) is currently released in jammy. * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.4.4-0ubuntu0.22.10.1 * Backport target is Jammy/22.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_74/1542/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. +
[Desktop-packages] [Bug 2003031] Re: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7"
I have applied the workaround for mutter : MUTTER_DEBUG_FORCE_KMS_MODE=simple I am seeing no further logs at the moment. I will continue to monitor for issues. To address any low-level issues I also have applied the system firmware update, available via ISO from the Lenovo support site "n32ur20w.iso". the release date on this was Jan 02 , 2023, so only about 2 weeks ago. I expect the issue to re-occur. Reference for anyone following along at home : https://pcsupport.lenovo.com/us/en/products/laptops-and- netbooks/thinkpad-x-series-laptops/thinkpad-x1-yoga-6th-gen- type-20xy-20y0/20xy/20xy0027us/downloads/driver- list/component?name=BIOS%2FUEFI Release notes for this firmware update included here too : ** Attachment added: "n32ur20w.txt" https://bugs.launchpad.net/linux/+bug/2003031/+attachment/5642055/+files/n32ur20w.txt -- 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/2003031 Title: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7" Status in Linux: Unknown Status in linux package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: GJS crashes - here's the crashdump. I saw the crash occur after a screensaver had been running, and the screens had gone blank. I assume this means they were turned off by the sleep timer. When I worke the machine, I was presented with a prompt, I *quickly* entered my login credentials and momentarily saw the desktop and all open programs on it. Then, the screens (3) flickered and I saw the login prompt again. I logged in (again), and all applications had been shut down. I checked /var/log/syslog and saw the following details -- see (log). Uploaded file, and the crashdump. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 16 20:52:55 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] InstallationDate: Installed on 2023-01-09 (7 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to kinetic on 2023-01-15 (1 days ago) dmi.bios.date: 07/27/2022 dmi.bios.release: 1.55 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET79W (1.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 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
[Desktop-packages] [Bug 2003031] Re: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7"
Yes, there is a USB-C "port extender" (dock) attached to this Lenovo laptop. The model is the MUC-0501B. It is this exact device : https://amzn.to/3XA5u5N -- "USB C Adapters for MacBook Pro/Air,Mac Dongle with 3 USB Port,USB C to HDMI, USB C to RJ45 Ethernet,MOKiN 9 in 1 USB C to HDMI Adapter,100W Pd Charging, USB C to SD/TF Card Reader USB C Hub". I also have noticed occassional flickering. What's interesting is that either the display controlled via this, or via the direct HDMI port will "drop out" for a second or 2 when the mouse moves between the screens. If I move the mouse back to the alternate screen, the display comes back. ** Attachment added: "video of a related(?) problem." https://bugs.launchpad.net/linux/+bug/2003031/+attachment/5642054/+files/PXL_20230117_204102229.mp4 -- 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/2003031 Title: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7" Status in Linux: Unknown Status in linux package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: GJS crashes - here's the crashdump. I saw the crash occur after a screensaver had been running, and the screens had gone blank. I assume this means they were turned off by the sleep timer. When I worke the machine, I was presented with a prompt, I *quickly* entered my login credentials and momentarily saw the desktop and all open programs on it. Then, the screens (3) flickered and I saw the login prompt again. I logged in (again), and all applications had been shut down. I checked /var/log/syslog and saw the following details -- see (log). Uploaded file, and the crashdump. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 16 20:52:55 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] InstallationDate: Installed on 2023-01-09 (7 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to kinetic on 2023-01-15 (1 days ago) dmi.bios.date: 07/27/2022 dmi.bios.release: 1.55 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET79W (1.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 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
[Desktop-packages] [Bug 1983717] Re: Monitor layout hotkey does not show single display options
Is there an alternative to disable all monitor's but primary e.g 'builtin only' option on desktop? -- 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/1983717 Title: Monitor layout hotkey does not show single display options Status in gnome-shell package in Ubuntu: Confirmed Bug description: 0) More detailed description: The default hotkey to switch which monitor to display the desktop on (Super+P) only shows two options: Mirror and Join Displays. There is no option "External Only" or "Built-in Only". This computer is configured with an AMD graphics card plugged into two external monitors, running Ubuntu 22.04 in the Wayland session. 1) lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 2) apt-cache policy gnome-shell gnome-shell: Installed: 42.2-0ubuntu0.2 Candidate: 42.2-0ubuntu0.2 Version table: *** 42.2-0ubuntu0.2 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) Expected to happen: Meta+P hotkey showing all four possibilities for display configurations (Mirror, Join Displays, External Only, Built-in Only). 4) What happened instead: Only two options appear on screen while pressing Meta+P: "Mirror" and "Join Displays". ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.2-0ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Aug 5 09:17:19 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-01 (95 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 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/1983717/+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 2003104] Re: Transparency ignored in full screen mode
Installing a fresh install of Lunar, everything works fine. Updating Gtk3, LibVTE, Cairo and other libraries doesn't make it fail. But doing a dist-upgrade makes it fail like described. There is no new version neither of Gnome Terminal, nor of Gnome Shell, so it doesn't seem a problem there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2003104 Title: Transparency ignored in full screen mode Status in gnome-terminal package in Ubuntu: New Bug description: Ubuntu 23.04 running wayland gnome-terminal 3.46.7-1ubuntu1 In gnome-terminal, I have set the transparency to some amount. When I go to full screen (F11), the transparency is lost and the default transparency is used. When I exit full screen, the transparency comes back and I can see in the profile settings that the transparency has not changed. It seems that tranparency was accidentally removed, and then re-added via https://git.launchpad.net/ubuntu/+source/gnome-terminal/tree/debian/patches/0001-Restore-transparency.patch?h=applied/ubuntu/lunar-devel However, maybe something was missed with regards to full screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2003104/+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 1983717] Re: Monitor layout hotkey does not show single display options
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/1983717 Title: Monitor layout hotkey does not show single display options Status in gnome-shell package in Ubuntu: Confirmed Bug description: 0) More detailed description: The default hotkey to switch which monitor to display the desktop on (Super+P) only shows two options: Mirror and Join Displays. There is no option "External Only" or "Built-in Only". This computer is configured with an AMD graphics card plugged into two external monitors, running Ubuntu 22.04 in the Wayland session. 1) lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 2) apt-cache policy gnome-shell gnome-shell: Installed: 42.2-0ubuntu0.2 Candidate: 42.2-0ubuntu0.2 Version table: *** 42.2-0ubuntu0.2 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) Expected to happen: Meta+P hotkey showing all four possibilities for display configurations (Mirror, Join Displays, External Only, Built-in Only). 4) What happened instead: Only two options appear on screen while pressing Meta+P: "Mirror" and "Join Displays". ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.2-0ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Aug 5 09:17:19 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-01 (95 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 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/1983717/+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 2003115] [NEW] bluetooth headphones poor sound quality
Public bug reported: Hello, I have jabra elite 3 bluetooth headphones. On my machine (ubuntu 22.10), the sound rings, stutters, and often stops. On this same machine, under windows or with a live cd of ubuntu 22.04, I have no problem. thank you to consider ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dob3008 F wireplumber /dev/snd/seq:dob3005 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 20:08:51 2023 InstallationDate: Installed on 2023-01-03 (13 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2022 dmi.bios.release: 15.26 dmi.bios.vendor: Insyde dmi.bios.version: F.26 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84BB dmi.board.vendor: HP dmi.board.version: 15.32 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 15.32 dmi.modalias: dmi:bvnInsyde:bvrF.26:bd07/25/2022:br15.26:efr15.32:svnHP:pnHPPavilionLaptop14-ce2xxx:pvrType1ProductConfigId:rvnHP:rn84BB:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku8KZ34EA#ABF: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 14-ce2xxx dmi.product.sku: 8KZ34EA#ABF dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- 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/2003115 Title: bluetooth headphones poor sound quality Status in alsa-driver package in Ubuntu: New Bug description: Hello, I have jabra elite 3 bluetooth headphones. On my machine (ubuntu 22.10), the sound rings, stutters, and often stops. On this same machine, under windows or with a live cd of ubuntu 22.04, I have no problem. thank you to consider ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dob3008 F wireplumber /dev/snd/seq:dob3005 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 20:08:51 2023 InstallationDate: Installed on 2023-01-03 (13 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2022 dmi.bios.release: 15.26 dmi.bios.vendor: Insyde dmi.bios.version: F.26 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84BB dmi.board.vendor: HP dmi.board.version: 15.32 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 15.32 dmi.modalias: dmi:bvnInsyde:bvrF.26:bd07/25/2022:br15.26:efr15.32:svnHP:pnHPPavilionLaptop14-ce2xxx:pvrType1ProductConfigId:rvnHP:rn84BB:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku8KZ34EA#ABF: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 14-ce2xxx dmi.product.sku: 8KZ34EA#ABF dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2003115/+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 1946769] Re: [snap] [' + c] produces "ć" instead of "ç" with US intl. layout
> One workaround is to GTK_IM_MODULE= firefox Did you mean GTK_IM_MODULE=cedilla ? -- 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/1946769 Title: [snap] [' + c] produces "ć" instead of "ç" with US intl. layout Status in firefox package in Ubuntu: Confirmed Bug description: Since I upgraded to impish, firefox is the only application on my desktop which produces "ć" instead of "ç" when I enter the combination "'" + "c". I suspect it's because now it's a snap, and is not respecting some system-wide configuration. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1946769/+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 2003108] [NEW] Nautilus still says "do not unplug the device" even if the writing process is finished
Public bug reported: After I click on the "unmount" icon next to the USB device in the file tree sidebar on Nautilus, the notification appears with the text "do not unplug/remove the device". The problem is that the notification doesn't go away for several time, even if the writing process is already finished, also with that notification still visible in the right top corner I can remount the USN by clicking its name in Nautilus, use it, and unmount it. If I copy something in the USB, the "copying files" popup process should finish only if the writing process is really completed (as it was in the previous Ubuntu versions...). I'm using Ubuntu 22.04.1 LTS. apt-cache policy nautilus: nautilus: Installato: 1:42.2-0ubuntu1 Candidato: 1:42.2-0ubuntu1 Tabella versione: *** 1:42.2-0ubuntu1 100 100 /var/lib/dpkg/status 1:42.0-1ubuntu2 500 500 http://it.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: nautilus ** Description changed: After I click on the "unmount" icon next to the USB device in the file - tree sidear on Nautilus, the notification appears with the text "do not + tree sidebar on Nautilus, the notification appears with the text "do not unplug/remove the device". The problem is that the notification doesn't go away for several time, even if the writing process is already finished, also with that notification still visible in the right top corner I can remount the USN by clicking its name in Nautilus, use it, and unmount it. If I copy something in the USB, the "copying files" popup process should finish only if the writing process is really completed (as it was in the previous Ubuntu versions...). I'm using Ubuntu 22.04.1 LTS. apt-cache policy nautilus: nautilus: - Installato: 1:42.2-0ubuntu1 - Candidato: 1:42.2-0ubuntu1 - Tabella versione: - *** 1:42.2-0ubuntu1 100 - 100 /var/lib/dpkg/status - 1:42.0-1ubuntu2 500 - 500 http://it.archive.ubuntu.com/ubuntu jammy/main amd64 Packages + Installato: 1:42.2-0ubuntu1 + Candidato: 1:42.2-0ubuntu1 + Tabella versione: + *** 1:42.2-0ubuntu1 100 + 100 /var/lib/dpkg/status + 1:42.0-1ubuntu2 500 + 500 http://it.archive.ubuntu.com/ubuntu jammy/main amd64 Packages -- 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/2003108 Title: Nautilus still says "do not unplug the device" even if the writing process is finished Status in nautilus package in Ubuntu: New Bug description: After I click on the "unmount" icon next to the USB device in the file tree sidebar on Nautilus, the notification appears with the text "do not unplug/remove the device". The problem is that the notification doesn't go away for several time, even if the writing process is already finished, also with that notification still visible in the right top corner I can remount the USN by clicking its name in Nautilus, use it, and unmount it. If I copy something in the USB, the "copying files" popup process should finish only if the writing process is really completed (as it was in the previous Ubuntu versions...). I'm using Ubuntu 22.04.1 LTS. apt-cache policy nautilus: nautilus: Installato: 1:42.2-0ubuntu1 Candidato: 1:42.2-0ubuntu1 Tabella versione: *** 1:42.2-0ubuntu1 100 100 /var/lib/dpkg/status 1:42.0-1ubuntu2 500 500 http://it.archive.ubuntu.com/ubuntu jammy/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2003108/+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 2003107] [NEW] Video player doesn't start
Public bug reported: Video player doesn't start at all. Running `totem` from the terminal I get: ``` (totem:97829): GStreamer-GL-CRITICAL **: 18:47:08.513: Failed to flush Wayland connection Gdk-Message: 18:47:08.513: Error reading events from display: Protocol error ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: totem 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 18:48:34 2023 InstallationDate: Installed on 2022-04-22 (270 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/2003107 Title: Video player doesn't start Status in totem package in Ubuntu: New Bug description: Video player doesn't start at all. Running `totem` from the terminal I get: ``` (totem:97829): GStreamer-GL-CRITICAL **: 18:47:08.513: Failed to flush Wayland connection Gdk-Message: 18:47:08.513: Error reading events from display: Protocol error ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: totem 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 18:48:34 2023 InstallationDate: Installed on 2022-04-22 (270 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/2003107/+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 2002845] Re: debhelper 13.11.4ubuntu1 broke dh-translations
** Changed in: debhelper (Debian)
Status: Unknown => Fix Released
--
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/2002845
Title:
debhelper 13.11.4ubuntu1 broke dh-translations
Status in debhelper package in Ubuntu:
Fix Committed
Status in gnome-control-center package in Ubuntu:
Invalid
Status in gnome-text-editor package in Ubuntu:
Invalid
Status in pkgbinarymangler package in Ubuntu:
Fix Released
Status in debhelper package in Debian:
Fix Released
Bug description:
Today's debhelper 13.11.4ubuntu1 merge broke dh-translations.
https://launchpad.net/ubuntu/+source/gnome-text-editor/43.2-1ubuntu1
gnome-text-editor build log excerpt
---
dh_translations
Can't exec "meson introspect '/<>/obj-x86_64-linux-gnu'
--targets |
jq -r -M '.[].name | select(endswith("-pot")) | sub("-pot"; "")'":
No such file or directory at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm
line 518.
dh_translations: error: exec (for cmd: "meson introspect
'/<>/obj-x86_64-linux-gnu'
--targets | jq -r -M '.[].name | select(endswith(\"-pot\")) |
sub(\"-pot\"; \"\")'") failed: No such file or directory
dh_translations: error: "meson introspect
'/<>/obj-x86_64-linux-gnu'
--targets | jq -r -M '.[].name | select(endswith(\"-pot\")) |
sub(\"-pot\"; \"\")'" returned exit code 25
Other Info
--
Gunnar identified the bad commit as
https://salsa.debian.org/debian/debhelper/-/commit/62a8608
https://launchpad.net/~gunnarhj/+archive/ubuntu/debhelper/+packages
https://pastebin.ubuntu.com/p/P8qM2sHn9C/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/2002845/+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 2003104] [NEW] Transparency ignored in full screen mode
Public bug reported: Ubuntu 23.04 running wayland gnome-terminal 3.46.7-1ubuntu1 In gnome-terminal, I have set the transparency to some amount. When I go to full screen (F11), the transparency is lost and the default transparency is used. When I exit full screen, the transparency comes back and I can see in the profile settings that the transparency has not changed. It seems that tranparency was accidentally removed, and then re-added via https://git.launchpad.net/ubuntu/+source/gnome-terminal/tree/debian/patches/0001-Restore-transparency.patch?h=applied/ubuntu/lunar-devel However, maybe something was missed with regards to full screen. ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Attachment added: "video of the issue" https://bugs.launchpad.net/bugs/2003104/+attachment/5642008/+files/Screencast%20from%202023-01-17%2009-26-27.webm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2003104 Title: Transparency ignored in full screen mode Status in gnome-terminal package in Ubuntu: New Bug description: Ubuntu 23.04 running wayland gnome-terminal 3.46.7-1ubuntu1 In gnome-terminal, I have set the transparency to some amount. When I go to full screen (F11), the transparency is lost and the default transparency is used. When I exit full screen, the transparency comes back and I can see in the profile settings that the transparency has not changed. It seems that tranparency was accidentally removed, and then re-added via https://git.launchpad.net/ubuntu/+source/gnome-terminal/tree/debian/patches/0001-Restore-transparency.patch?h=applied/ubuntu/lunar-devel However, maybe something was missed with regards to full screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2003104/+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 1991761] Re: Backport packages for 22.04.2 HWE stack
At least from AMD's tests, backported mesa stack is working properly with RDNA3. Adjusting tag accordingly. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1991761 Title: Backport packages for 22.04.2 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-15 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in spirv-headers package in Ubuntu: Invalid Status in spirv-llvm-translator-14 package in Ubuntu: Invalid Status in spirv-llvm-translator-15 package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in libdrm source package in Jammy: Fix Committed Status in llvm-toolchain-15 source package in Jammy: Fix Committed Status in mesa source package in Jammy: Fix Committed Status in spirv-headers source package in Jammy: Fix Committed Status in spirv-llvm-translator-14 source package in Jammy: Fix Committed Status in spirv-llvm-translator-15 source package in Jammy: Fix Committed Bug description: [Impact The graphics HWE stack from kinetic needs to be backported for 22.04.2 directx-headers - build-dep of the new Mesa libdrm - build-dep of the new Mesa llvm-15 - new package in jammy - build-dep of the new Mesa mesa - new major release (22.2.x) - new HW support, like AMD RDNA3, Intel DG2 spirv-headers - needed by s-l-t-15 spirv-llvm-translator-14 - needed to bootstrap libclc from llvm spirv-llvm-translator-15 - needed for the actual libclc-15 after initial bootstrap Bootstrapping plan: - s-l-t-14 built from NEW - llvm-15 built with s-l-t-14 - s-l-t-15 built against llvm-15 - llvm-15 built again with s-l-t-15 -> mesa ready for building [Test case] Install the new mesa on various hw, see that everything still works like before or better. spirv-headers: - test reverse-build-deps that they still build Reverse-Build-Depends * glslang * intel-graphics-compiler * spirv-llvm-translator-14 * spirv-llvm-translator-15 * spirv-tools * vkbasalt * vkd3d * vulkan-validationlayers [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll backport the final stable release of 22.2.x in order to minimize the chance for those. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1991761/+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 2003099] [NEW] Flickering when minimizing
Public bug reported: When minimizing windowed applications, the animation sometimes jumps wildly around, mostly to the top left corner of the screen. I found a temporary workaround with a config file in /etc/X11/xorg.conf.d/20-intel.conf, which supposedly has some other unwanted effects on other programs. Thanks for your help!! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-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..3c.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.60.11 Wed Nov 23 23:04:03 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 17:12:59 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo WhiskeyLake-U GT2 [UHD Graphics 620] [17aa:2283] Subsystem: Lenovo GP108M [GeForce MX250] [17aa:2283] InstallationDate: Installed on 2023-01-02 (14 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20N4002VGE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=72ad0f02-9e2a-4714-8427-9372619f5f04 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2020 dmi.bios.release: 1.68 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET90W (1.68 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N4002VGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnLENOVO:bvrN2IET90W(1.68):bd07/06/2020:br1.68:efr1.17:svnLENOVO:pn20N4002VGE:pvrThinkPadT590:rvnLENOVO:rn20N4002VGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20N4_BU_Think_FM_ThinkPadT590: dmi.product.family: ThinkPad T590 dmi.product.name: 20N4002VGE dmi.product.sku: LENOVO_MT_20N4_BU_Think_FM_ThinkPad T590 dmi.product.version: ThinkPad T590 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.3 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.3-2ubuntu2.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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy 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/2003099 Title: Flickering when minimizing Status in xorg package in Ubuntu: New Bug description: When minimizing windowed applications, the animation sometimes jumps wildly around, mostly to the top left corner of the screen. I found a temporary workaround with a config file in /etc/X11/xorg.conf.d/20-intel.conf, which supposedly has some other unwanted effects on other programs. Thanks for your help!! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-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..3c.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.60.11 Wed Nov 23 23:04:03 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission
[Desktop-packages] [Bug 2003031] Re: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7"
Spelling error : "When I woke the machine..." -- 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/2003031 Title: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7" Status in Linux: Unknown Status in linux package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: GJS crashes - here's the crashdump. I saw the crash occur after a screensaver had been running, and the screens had gone blank. I assume this means they were turned off by the sleep timer. When I worke the machine, I was presented with a prompt, I *quickly* entered my login credentials and momentarily saw the desktop and all open programs on it. Then, the screens (3) flickered and I saw the login prompt again. I logged in (again), and all applications had been shut down. I checked /var/log/syslog and saw the following details -- see (log). Uploaded file, and the crashdump. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 16 20:52:55 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] InstallationDate: Installed on 2023-01-09 (7 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to kinetic on 2023-01-15 (1 days ago) dmi.bios.date: 07/27/2022 dmi.bios.release: 1.55 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET79W (1.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 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/linux/+bug/2003031/+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 2002941] Re: [BPO] libreoffice 7.4.4 for jammy
** Description changed: [Impact] * LibreOffice 7.4.4 is in its forth bugfix release of the 7.4 line: https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.4_release * This source packages matches the proposed SRU for kinetic handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2001911 and its backport is currently provided by the LibreOffice Fresh PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/ppa/+packages * LibreOffice 7.3.7 (EOL since November 30, 2022) is currently released in jammy. * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.4.4-0ubuntu0.22.10.1 * Backport target is Jammy/22.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_74/1542/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. - * [amd64] ... - * [arm64] ... + * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/amd64/libr/libreoffice/20230117_121308_55f21@/log.gz + * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/arm64/libr/libreoffice/20230117_004531_c08ab@/log.gz * [armhf] ... - * [ppc64el] ... - * [s390x] ... + * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/ppc64el/libr/libreoffice/20230116_230929_28cc3@/log.gz + * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/s390x/libr/libreoffice/20230117_034834_09f33@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] - * A minor release with a total of 114 bug fixes always carries the - potential for introducing regressions, even though it is a bugfix-only - release, meaning that no new features were added, and no existing - features were removed. - * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. ** Changed in: libreoffice (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: libreoffice (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2002941 Title: [BPO] libreoffice 7.4.4 for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: In Progress Bug description: [Impact] * LibreOffice 7.4.4 is in its forth bugfix release of the 7.4 line: https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.4_release * This source packages matches the proposed SRU for kinetic handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2001911 and its backport is currently provided by the LibreOffice Fresh PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/ppa/+packages * LibreOffice 7.3.7 (EOL since November 30, 2022) is currently released in jammy. * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.4.4-0ubuntu0.22.10.1 * Backport target is Jammy/22.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be
[Desktop-packages] [Bug 2003024] Re: Dock prevents Search switching to some apps in different workspaces
Auto-hide was already disabled, however I've done as instructed in the other bug report and ran journalctl on /usr/bin/gnome-shell, I'll be attaching the parts of the log relevant to the time the bug happened. I've pressed enter multiple times so there are multiple instances of "JS ERROR: TypeError: window is undefined" ** Attachment added: "gnomejournal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2003024/+attachment/5641947/+files/gnomejournal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2003024 Title: Dock prevents Search switching to some apps in different workspaces Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: While the Ubuntu Dock extension is active, searching for certain applications on the overview screen and pressing Enter does not switch to them if an instance exists on other workspaces. Notably a few GNOME Apps such as Nautilus and gedit. From the programs I've tested: - Pressing Enter on Nautilus, gedit and Firefox does nothing, not even close the overview nor switch to an open instance. - Pressing Enter on Thunderbird switches to it properly. - Pressing Enter on KeepassXC gets you a notification and clicking it will switch to it. - Pressing Enter on Terminal opens a new instance on the current workspace instead of switching to an existing one if one exists on another workspace. If the dock extension is disabled, searching for a program and pressing Enter behaves as expected, that is, the program becomes focused and is switched to. Edit: After some more testing, it only happens if either "Include applications from the current workspace only" or "Include applications from each monitor only" options are activated in Control Center > Multitasking > Application Switching I apologize in case that wasn't well explained, if there are any doubts, I'll attempt to record a video of it. Ubuntu: 22.04.01 LTS Ubuntu Dock: 72~ubuntu5.22.04.1 gnome-shell: 42.5-0ubuntu1 Running on Xorg. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 16 20:04:47 2023 InstallationDate: Installed on 2022-09-12 (126 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2003024/+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 2002510] Re: bbswitch-dkms fails to build with jammy/linux-hwe-5.19
** Changed in: bbswitch (Ubuntu) Status: New => Fix Released ** Changed in: bbswitch (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bbswitch in Ubuntu. https://bugs.launchpad.net/bugs/2002510 Title: bbswitch-dkms fails to build with jammy/linux-hwe-5.19 Status in bbswitch package in Ubuntu: Fix Released Status in bbswitch source package in Jammy: In Progress Bug description: [Impact] bbswitch-dkms fails to build with jammy/linux-hwe-5.19. [Test case] $ sudo apt-get install bbswitch-dkms [Fix] To fix it we can take two approches: a) we import the Lunar version (0.8-14) into Jammy, and it's missing dependency (dh-dkms) or b) we apply the attached debdiff that is syncing the Jammy version up to Lunar, reverting on top the bits depending on dh-dkms. Whichever is the path of last resistance, i'm happy with it. [Regression potential] It's the same DKMS we are already using in Lunar, and it contains all the fixes upstream developed so far: Jammy and Lunar share the same base version (0.8). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/2002510/+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 2002510] Re: bbswitch-dkms fails to build with jammy/linux-hwe-5.19
uploaded changes into lunar to make it more backport friendly. for jammy, i think i will upload cherrypick of linux-5.18 compat patch. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bbswitch in Ubuntu. https://bugs.launchpad.net/bugs/2002510 Title: bbswitch-dkms fails to build with jammy/linux-hwe-5.19 Status in bbswitch package in Ubuntu: Fix Released Status in bbswitch source package in Jammy: In Progress Bug description: [Impact] bbswitch-dkms fails to build with jammy/linux-hwe-5.19. [Test case] $ sudo apt-get install bbswitch-dkms [Fix] To fix it we can take two approches: a) we import the Lunar version (0.8-14) into Jammy, and it's missing dependency (dh-dkms) or b) we apply the attached debdiff that is syncing the Jammy version up to Lunar, reverting on top the bits depending on dh-dkms. Whichever is the path of last resistance, i'm happy with it. [Regression potential] It's the same DKMS we are already using in Lunar, and it contains all the fixes upstream developed so far: Jammy and Lunar share the same base version (0.8). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/2002510/+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 2003078] [NEW] Desktop freezes for seconds
Public bug reported: Ubuntu 22.10 on hybrid graphics laptop. Sometimes while normal workflow the desktop freezes for seconds: Asynchronous wait on fence :00:02.0:gnome-shell[4401]:96352 timed out (hint:intel_atomic_commit_ready [i915]) i915 :00:02.0: [drm] GPU HANG: ecode 12:1:85db, in Renderer [5405] i915 :00:02.0: [drm] Resetting rcs0 for stopped heartbeat on rcs0 i915 :00:02.0: [drm] Renderer[5405] context reset due to GPU hang ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xserver-xorg-video-intel 2:2.99.917+git20210115-1 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 BootLog: CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 14:01:20 2023 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.19.0-28-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. TigerLake-LP GT2 [Iris Xe Graphics] [1043:1e6f] Subsystem: ASUSTeK Computer Inc. TU117M [GeForce MX450] [1043:1e6f] InstallationDate: Installed on 2023-01-04 (12 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: ASUSTeK COMPUTER INC. ZenBook UX435EG_UX435EG ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-29-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX435EG.315 dmi.board.asset.tag: dmi.board.name: UX435EG dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX435EG.315:bd04/22/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX435EG_UX435EG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX435EG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX435EG_UX435EG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic ubuntu ** Description changed: Ubuntu 22.10 on hybrid graphics laptop. Sometimes while normal workflow the desktop freezes for seconds: Asynchronous wait on fence :00:02.0:gnome-shell[4401]:96352 timed out (hint:intel_atomic_commit_ready [i915]) i915 :00:02.0: [drm] GPU HANG: ecode 12:1:85db, in Renderer [5405] i915 :00:02.0: [drm] Resetting rcs0 for stopped heartbeat on rcs0 i915 :00:02.0: [drm] Renderer[5405] context reset due to GPU hang ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xserver-xorg-video-intel 2:2.99.917+git20210115-1 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 BootLog: - + CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 14:01:20 2023 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: - virtualbox/6.1.38, 5.19.0-28-generic, x86_64: installed - virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed + virtualbox/6.1.38, 5.19.0-28-generic, x86_64: installed + virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. TigerLake-LP GT2 [Iris Xe Graphics] [1043:1e6f] -Subsystem: ASUSTeK Computer Inc. TU117M [GeForce MX450] [1043:1e6f] + Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. TigerLake-LP GT2 [Iris Xe Graphics] [1043:1e6f] + Subsystem: ASUSTeK Computer Inc. TU117M [GeForce MX450] [1043:1e6f] InstallationDate: Installed on 2023-01-04 (12 days ago)
[Desktop-packages] [Bug 2003052] Re: App launch animation is glitchy when opening Chrome browser
The problem has been resolved by disabling the "Use hardware acceleration when available" option in Google Chrome. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2003052 Title: App launch animation is glitchy when opening Chrome browser Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: When opening Firefox browser, the dock hides with good animation, but when opening Chrome browser, the dock animation has bugs before it hides. This behavior is observed on Ubuntu Lunar Lobster (development branch) version 23.04, Wayland, Linux 5.19.0-21-generic using the built-in dock. The problem does not happen with other applications. Steps to reproduce: Open Firefox browser Observe the dock hides with good animation Open Chrome browser Observe the dock animation bugs before it hides ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 43.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 10:08:36 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-16 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221209) RelatedPackageVersions: mutter-common 43.2-4ubuntu1 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-extension-ubuntu-dock/+bug/2003052/+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 2003064] Re: package firefox (not installed) failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1
** Package changed: ubuntu => firefox (Ubuntu) -- 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/2003064 Title: package firefox (not installed) failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 Status in firefox package in Ubuntu: New Bug description: Version 108.0.2 ProblemType: Package DistroRelease: Ubuntu 22.04 Uname: Linux 5.10.60-qnap x86_64 ApportVersion: 2.20.11-0ubuntu82.3 AptOrdering: firefox:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Jan 17 10:11:56 2023 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 Snap: firefox 108.0.2-1 (latest/stable) Title: package firefox (not installed) failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2003064/+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 2003064] [NEW] package firefox (not installed) failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1
You have been subscribed to a public bug: Version 108.0.2 ProblemType: Package DistroRelease: Ubuntu 22.04 Uname: Linux 5.10.60-qnap x86_64 ApportVersion: 2.20.11-0ubuntu82.3 AptOrdering: firefox:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Jan 17 10:11:56 2023 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 Snap: firefox 108.0.2-1 (latest/stable) Title: package firefox (not installed) failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- package firefox (not installed) failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 https://bugs.launchpad.net/bugs/2003064 You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox 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 2000551] Re: [System Fonts] Replace default sinhala font from LKLUG to Noto
On 2023-01-17 08:48, Aurora wrote: >> Or they can simply do: sudo apt install fonts-noto-core > > but flatpak users said that flatpak apps still use LKLUG, how to > solve that problem? I don't know anything about Flatpak, sorry. Can't tell to which extent Flatpak honors fontconfig. Maybe try Ask Ubuntu or some Flatpak oriented support resource. I know that the Firefox snap provided in Ubuntu honors the configuration in /etc/fonts/conf.d, and so do conventionally installed applications too. > if a sinhala language speaker or foreigner keeps only english > (default) or other language in the system and when they view a > sinhala web page using a web browser or use a text editor to edit > something, it looks like ubuntu still uses LKLUG as the default > font. That's not what I see. I just made an English install of the coming Ubuntu 23.04 in VirtualBox and updated the packages. Then I * Opened a terminal and run: sudo apt install fonts-noto-core * Opened Firefox, went to https://si.wikipedia.org, and found that the page was rendered using Noto Sans Sinhala and Noto Serif Sinhala — not LKLUG. > should i propose a small font package like LKLUG? What would the point be with doing so? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2000551 Title: [System Fonts] Replace default sinhala font from LKLUG to Noto Status in language-selector package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Won't Fix Status in language-selector source package in Jammy: Fix Committed Status in language-selector source package in Kinetic: Fix Committed Bug description: [ Impact ] The current default font for Sinhala (LKLUG) is unmaintained and comes with issues. Noto offers Sinhala fonts with significantly higher quality. fonts-lklug-sinhala is pulled by quite a few meta packages. Instead of changing that, the proposed change makes fontconfig give Noto Sans Sinhala respective Noto Serif Sinhala higher precedence than LKLUG, and that — together with installation of fonts-noto-core — seems to be sufficient to achieve the desired result. [ Test Plan ] * Install language-selector-[common,gnome] from [jammy,kinetic]-proposed. * Open Language Support and install the Sinhala language. * Open a terminal window and run this command: fc-match -a | grep -E 'LKLUG|Sinhala' * Confirm that Noto Sans Sinhala is listed before LKLUG. * Close Firefox and re-open it. * Visit e.g. https://si.wikipedia.org and confirm the improvement. (Also I (Gunnar), who don't speak Sinhala, notice a remarkable difference.) [ Where problems could occur ] No real problem in sight. Some Sinhala speaking users with fonts-noto- core installed will indeed see a surprise change when it starts to render Sinhala via Noto fonts instead of LKLUG. But that surprise ought to make them happy. :) Please note Robie Basak's warning about the changed font metrics in comment #7, though. [ Original description ] **What's the problem?** Currently ubuntu comes with LKLUG font for sinhala (si). it's not clear. e.g. we cannot recognize vowel signs and read websites using that font. We can change it manually but such changes do not apply to some applications or application types e.g. snap apps etc. LKLUG (last active: 2012) no one maintain it now. https://web.archive.org/web/202200*/http://www.lug.lk/ http://www.lug.lk/fonts/lklug **What expected to happen?** We would like to see Noto serif sinhala as the default font for sinhala language https://fonts.google.com/noto/specimen/Noto+Serif+Sinhala [Highlighs: clear (readable), thin, takes less space than sans sinhala] If noto sans is more suitable for ubuntuOS, you can add noto sans sinhala https://fonts.google.com/noto/specimen/Noto+Sans+Sinhala [Highlighs: clear (readable), thick, takes more space than serif sinhala] **Additional details** Screenshots (see the difference: LKLUG/Noto) LKLUG https://i.ibb.co/nbHM5Mw/lklug.jpg Noto Sinhala https://i.ibb.co/k9dbtYb/noto.jpg If you need more examples or clarifications, please add a comment Random posts 1. https://groups.google.com/g/Sinhala-Unicode/c/LYxuJ44dY3g 2. https://twitter.com/thilinag/status/1598707165920825344#m (LKLUG bug with some apps) 3. https://www.reddit.com/r/srilanka/comments/nzpl9p/change_sinhala_font_in_ubuntu/ Also, some developers already have designed tools, scripts for that problem however many people do not try to find these scripts and switch to other OS 1. https://github.com/IMS94/UbuntuSinhalaFont (developer: PMC chair @apache) 2. https://gist.github.com/thilinag/66577033fafd00c3dfdaa898c2478c79 3. https://github.com/hankyoTutorials/linux-system-sinhala-font-changer Please review details, screenshots and posts. This is not a personal opinion
[Desktop-packages] [Bug 1962349] Re: Bolt doesn't work with native USB4 hosts
** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: bolt (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Kinetic) Status: New => Fix Released ** Changed in: linux-oem-5.17 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Kinetic) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bolt in Ubuntu. https://bugs.launchpad.net/bugs/1962349 Title: Bolt doesn't work with native USB4 hosts Status in OEM Priority Project: Fix Released Status in bolt package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in bolt source package in Focal: Fix Released Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in bolt source package in Impish: Fix Released Status in linux source package in Impish: Won't Fix Status in linux-oem-5.14 source package in Impish: Invalid Status in linux-oem-5.17 source package in Impish: Invalid Status in bolt source package in Jammy: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in bolt source package in Kinetic: New Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [SRU Justification] [Impact] * AMD Yellow Carp provides integrated USB4 host controllers * When plugging in a Thunderbolt3 or USB4 device, users are unable to authorize it using the GUI due to an error message: "parent not authorized, deferring" [Test Plan] AMD Yellow Carp Host (issue this bug is about) -- * Plug in USB4 device or TBT3 to AMD Yellow Carp host * Ensure that PCI topology has populated * Observe that /sys/bus/thunderbolt/devices/DEVICE/authorized is "0" * Try to run `boltctl enroll $UUID` Alpine Ridge / Titan Ridge host (discrete controller) -- Start out on a host with discrete controller (Alpine Ridge or Titan Ridge) 1. sudo boltctl forget -a 2. Plug in dock 3. Make sure 'boltctl list' enumerates dock. 4. Check /sys/bus/thunderbolt/devices/domain0/iommu_dma_protection (value dependent upon host) - If 0; try to manually enroll using 'boltctl enroll $UUID' - If 1; ensure that device automatically enrolled with bolt. GUI Check - Ensure that devices show up in the Settings GUI and are now able to authorize. Note: for AMD platforms enumerating PCIe devices is a separate problem from BOLT handled by kernel tasks. GUI check is only about "authorization". [Where problems could occur] * Intel USB4 or TBT3 hosts also use bolt. They could have a problem with the new version of bolt. * This is very unlikely however since there is a through test suite, and up until now the entire industry has been using bolt on Intel controllers for a long time. * There haven't been any significant bugs reported upstream or in Ubuntu since 0.9.1 release. [Other Info] * This bug also occurs on Intel controllers from ICL, TGL or ALD, but in many cases they are automatically authorized to an iommu DMA policy. * It is fixed in bolt 0.9.1 or later release. * To solve the SRU, will backport 0.9.1 release from Impish. * I did look into backporting just the commit(s) for fixing this, but it's not a trivial backport. Quoting the changelog (https://gitlab.freedesktop.org/bolt/bolt/-/blob/master/CHANGELOG.md): "Additionally the unique_id of said host controller changes with every boot, which breaks one of the fundamental assumptions in boltd". To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962349/+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 2003052] Re: App launch animation is glitchy when opening Chrome browser
** Summary changed: - Dock launch animation is glitchy when opening Chrome browser + App launch animation is glitchy when opening Chrome browser -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2003052 Title: App launch animation is glitchy when opening Chrome browser Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: When opening Firefox browser, the dock hides with good animation, but when opening Chrome browser, the dock animation has bugs before it hides. This behavior is observed on Ubuntu Lunar Lobster (development branch) version 23.04, Wayland, Linux 5.19.0-21-generic using the built-in dock. The problem does not happen with other applications. Steps to reproduce: Open Firefox browser Observe the dock hides with good animation Open Chrome browser Observe the dock animation bugs before it hides ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 43.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 10:08:36 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-16 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221209) RelatedPackageVersions: mutter-common 43.2-4ubuntu1 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-extension-ubuntu-dock/+bug/2003052/+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 2003052] Re: Dock launch animation is glitchy when opening Chrome browser
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2003052 Title: Dock launch animation is glitchy when opening Chrome browser Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: When opening Firefox browser, the dock hides with good animation, but when opening Chrome browser, the dock animation has bugs before it hides. This behavior is observed on Ubuntu Lunar Lobster (development branch) version 23.04, Wayland, Linux 5.19.0-21-generic using the built-in dock. The problem does not happen with other applications. Steps to reproduce: Open Firefox browser Observe the dock hides with good animation Open Chrome browser Observe the dock animation bugs before it hides ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 43.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 10:08:36 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-16 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221209) RelatedPackageVersions: mutter-common 43.2-4ubuntu1 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-extension-ubuntu-dock/+bug/2003052/+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 2003052] Re: Dock launch animation is glitchy when opening Chrome browser
** Summary changed: - "Dock animation bugs when opening Chrome browser on Ubuntu Lunar Lobster (development branch)" + Dock launch animation is glitchy when opening Chrome browser ** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension- ubuntu-dock (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/2003052 Title: Dock launch animation is glitchy when opening Chrome browser Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: When opening Firefox browser, the dock hides with good animation, but when opening Chrome browser, the dock animation has bugs before it hides. This behavior is observed on Ubuntu Lunar Lobster (development branch) version 23.04, Wayland, Linux 5.19.0-21-generic using the built-in dock. The problem does not happen with other applications. Steps to reproduce: Open Firefox browser Observe the dock hides with good animation Open Chrome browser Observe the dock animation bugs before it hides ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 43.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 10:08:36 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-16 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221209) RelatedPackageVersions: mutter-common 43.2-4ubuntu1 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-extension-ubuntu-dock/+bug/2003052/+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 1998765] Re: libnl3 3.4.0 doesn't work with WCN3980
Hello Robert, or anyone else affected, Accepted libnl3 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libnl3/3.4.0-1ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libnl3 (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1998765 Title: libnl3 3.4.0 doesn't work with WCN3980 Status in OEM Priority Project: New Status in OEM Priority Project focal series: New Status in libnl3 package in Ubuntu: Fix Released Status in libnl3 source package in Focal: Fix Committed Status in libnl3 source package in Jammy: Invalid Bug description: [ Impact ] When testing Qualcomm qcs410 with WCN3980 with 20.04 and UC20, WCN3980 is not able connect to an AP. However, with the libnl3 (3.5.0) from BSP, WCN3980 can work correctly. After bisecting the commits from 3.4.0 to 3.5.0, this commit[1] is identified as the root cause. According to the commit, the "NLA_F_NESTED" flag should be set for kernel later than 5.2. [ Test Plan ] Verify with the updated version, the WIFI module can: 1. scan WIFI networks 2. connect to an available network 3. access to the connected network [ Where problems could occur ] 1. kernel versions without NLA_F_NESTED flag defined This flag is introduced before Linux kernel v5 (checked v3.x and v4.x have it). It would not be a problem for an older kernel to understand/work with this change. Since the GA kernel is 5.4, so a generic image would still work. 2. Drivers don't use the NESTED flag. According to hui.wang's input, this change should not affect drivers which don't use the NESTED flag. But, it'd be better to cover more Wifi modules. [ Other Info ] 22.04 is using libnl3 3.0.5-0.1, so only 20.04 needs this patch. [1] https://github.com/thom311/libnl/commit/7de65a051fb37ece16f896a7385073274b77a133 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998765/+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 2003052] Re: "Dock animation bugs when opening Chrome browser on Ubuntu Lunar Lobster (development branch)"
"I wanted to note that when I recorded the desktop and despite the existence of the problem, but after the end of the recording, the problem did not appear in the recorded video, although the problem still exists. -- 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/2003052 Title: "Dock animation bugs when opening Chrome browser on Ubuntu Lunar Lobster (development branch)" Status in gnome-shell package in Ubuntu: New Bug description: When opening Firefox browser, the dock hides with good animation, but when opening Chrome browser, the dock animation has bugs before it hides. This behavior is observed on Ubuntu Lunar Lobster (development branch) version 23.04, Wayland, Linux 5.19.0-21-generic using the built-in dock. The problem does not happen with other applications. Steps to reproduce: Open Firefox browser Observe the dock hides with good animation Open Chrome browser Observe the dock animation bugs before it hides ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 43.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 10:08:36 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-16 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221209) RelatedPackageVersions: mutter-common 43.2-4ubuntu1 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/2003052/+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 2003052] [NEW] "Dock animation bugs when opening Chrome browser on Ubuntu Lunar Lobster (development branch)"
Public bug reported: When opening Firefox browser, the dock hides with good animation, but when opening Chrome browser, the dock animation has bugs before it hides. This behavior is observed on Ubuntu Lunar Lobster (development branch) version 23.04, Wayland, Linux 5.19.0-21-generic using the built-in dock. The problem does not happen with other applications. Steps to reproduce: Open Firefox browser Observe the dock hides with good animation Open Chrome browser Observe the dock animation bugs before it hides ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 43.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 10:08:36 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-16 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221209) RelatedPackageVersions: mutter-common 43.2-4ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- 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/2003052 Title: "Dock animation bugs when opening Chrome browser on Ubuntu Lunar Lobster (development branch)" Status in gnome-shell package in Ubuntu: New Bug description: When opening Firefox browser, the dock hides with good animation, but when opening Chrome browser, the dock animation has bugs before it hides. This behavior is observed on Ubuntu Lunar Lobster (development branch) version 23.04, Wayland, Linux 5.19.0-21-generic using the built-in dock. The problem does not happen with other applications. Steps to reproduce: Open Firefox browser Observe the dock hides with good animation Open Chrome browser Observe the dock animation bugs before it hides ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 43.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 10:08:36 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-16 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221209) RelatedPackageVersions: mutter-common 43.2-4ubuntu1 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/2003052/+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
