[Desktop-packages] [Bug 2002377] Re: Update to 108.0.2
Package Release Information: https://launchpad.net/ubuntu/+source/firefox/108.0.2+build1-0ubuntu0.20.04.1 https://launchpad.net/ubuntu/+source/firefox/108.0.2+build1-0ubuntu0.18.04.1 ** Changed in: firefox (Ubuntu) Status: New => Fix Released -- 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/2002377 Title: Update to 108.0.2 Status in firefox package in Ubuntu: Fix Released Bug description: https://www.mozilla.org/en-US/firefox/108.0.2/releasenotes/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2002377/+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 2002377] [NEW] Update to 108.0.2
Public bug reported: https://www.mozilla.org/en-US/firefox/108.0.2/releasenotes/ ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- 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/2002377 Title: Update to 108.0.2 Status in firefox package in Ubuntu: New Bug description: https://www.mozilla.org/en-US/firefox/108.0.2/releasenotes/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2002377/+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 2002349] Re: I powered off and when I turned my computer on this hapened
Setting the bug to Invalid because we know the cause of the "stuck at 640x480". Separate to that it does look like some updates caused this by breaking the previously installed Nvidia driver but I can't find much detail here as to what went wrong. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid ** Summary changed: - I powered off and when I turned my computer on this hapened + Stuck at 640x480. No Nvidia driver anymore -- 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/2002349 Title: Stuck at 640x480. No Nvidia driver anymore Status in Ubuntu: Invalid Bug description: It's stuck at 640x480 and I can barely do anything at all I'm using Ubuntu 20.04 I cannot even update my computer ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-57.63~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 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: Mon Jan 9 14:36:01 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rtl882bu, 5.8.7.1, 5.15.0-57-generic, x86_64: installed rtl88x2bu, 5.8.7.1, 5.13.0-30-generic, x86_64: installed rtl88x2bu, 5.8.7.1, 5.15.0-57-generic, x86_64: installed (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] [19da:2476] InstallationDate: Installed on 2023-01-08 (1 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-57-generic root=UUID=9456410b-fb68-463f-b197-a8e997ea4477 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-I dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd03/07/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-I:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer 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.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2002349/+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 2002349] Re: I powered off and when I turned my computer on this hapened
Thanks for the bug report. It appears you don't have a working graphics driver installed. Please open the 'Additional Drivers' app and use it to install an Nvidia driver. -- 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/2002349 Title: Stuck at 640x480. No Nvidia driver anymore Status in Ubuntu: Invalid Bug description: It's stuck at 640x480 and I can barely do anything at all I'm using Ubuntu 20.04 I cannot even update my computer ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-57.63~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 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: Mon Jan 9 14:36:01 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rtl882bu, 5.8.7.1, 5.15.0-57-generic, x86_64: installed rtl88x2bu, 5.8.7.1, 5.13.0-30-generic, x86_64: installed rtl88x2bu, 5.8.7.1, 5.15.0-57-generic, x86_64: installed (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] [19da:2476] InstallationDate: Installed on 2023-01-08 (1 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-57-generic root=UUID=9456410b-fb68-463f-b197-a8e997ea4477 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-I dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd03/07/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-I:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer 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.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2002349/+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 2002321] Re: computer is too slow.
Thanks for the bug report. The main problem I can see here is that you have the kernel graphics driver in debug mode. To fix that you will need to remove "drm.debug=0xe plymouth:debug" from /etc/default/grub and then run: sudo update-grub and reboot. If that doesn't fix the problem then I would next recommend upgrading to Ubuntu 22.04.1 which is much faster. You also seem to be running an unsupported kernel that is actually older than the official kernel for Ubuntu 20.04. Fixing these problems that you seem to have created for yourself is a little bit complicated so if you are not very technical then I suggest the simplest solution is: 1. Backup all your data to external drives. 2. Reinstall from scratch using Ubuntu 22.04.1: https://ubuntu.com/download/desktop ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2002321 Title: computer is too slow. Status in Ubuntu: Incomplete Bug description: i dont know much about those computer term,but if could you help me somehow i would be very greatfull. thanx A.B. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.4.0-050400-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Jan 9 16:11:37 2023 DistUpgraded: 2022-12-25 23:43:14,353 INFO cache.commit() DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:064b] InstallationDate: Installed on 2018-04-19 (1726 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Acer TravelMate P253 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-050400-generic root=UUID=a81ad045-d2f8-4909-8aef-d7239d261ada ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2022-12-25 (14 days ago) dmi.bios.date: 12/16/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: BA51_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.21 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.21:bd12/16/2013:svnAcer:pnTravelMateP253:pvrV2.21:rvnAcer:rnBA51_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.21: dmi.product.family: Type1Family dmi.product.name: TravelMate P253 dmi.product.sku: TravelMate P253_064B_V2.21 dmi.product.version: V2.21 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.110-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sat Dec 1 18:03:02 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2002321/+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 2000739] Re: Window actions (like maximize) no more work in wayland for QEMU using GTK backend once the guest UI is intialized.
** No longer affects: wayland (Ubuntu) ** Tags added: focal session wayland ** Tags removed: session ** Tags added: wayland-session ** Tags added: jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2000739 Title: Window actions (like maximize) no more work in wayland for QEMU using GTK backend once the guest UI is intialized. Status in qemu package in Ubuntu: Confirmed Bug description: Window actions (like maximize) no more work in wayland for QEMU using GTK backend once the guest UI is intialized. This can be seen by running an installed or even a trial Ubuntu from an ISO like: $ qemu-system-x86_64 \ -boot d \ -cdrom ubuntu-22.04.1-desktop-amd64.iso \ -m 4096M \ -machine type=q35,accel=kvm \ -cpu host \ -smp 2 \ -device qxl-vga The GTK UI of qemu has a feature called "fullscreen" which disables the screen decorations and sets the window to maximize. The decorations go away, but maximize doesn't work. The following details were found so far: - running with GDK_BACKEND=x11 works - using sdl instead of gtk backend works - using the old qemu of Focal, or the newest from upstream git in jammy all fails (no qemu change AFAICS) - host UI widgets (the square at the window top) do not work either - hotkeys (super-up) do not work either It seems that once the guest has enabled the desktop something changes and the maximize/minimize/... actions are no more processed. Not sure were to debug next in regard to the gnome/wayland UI handling of this - any idea? P.S. We can reproduce this in git builds of qemu, so we can debug of modify the code as needed. The code for this is mostly in [1] [1]: https://gitlab.com/qemu-project/qemu/-/blob/master/ui/gtk.c --- original report --- Running QEMU version 4.2.1 on Ubuntu 20.04 via qemu-system-x86_64 \ -boot d \ -cdrom ubuntu-22.04.1-desktop-amd64.iso \ -m 4096M \ -machine type=q35,accel=kvm \ -cpu host \ -smp 2 \ -device qxl-vga and pressing ctrl+alt+f after booting the Ubuntu 22.04 live ISO and adjusting the display resolution to match the native resolution, works as expected, i.e., the VM screen is correctly displayed in fullscreen. However, after running the same command for QEMU version 6.2.0 on Ubuntu 22.04 and pressing ctrl+alt+f after making the resolution adjustment, yields a fullscreen view where the space occupied by the GNOME top bar (top panel with date in center) of the host is not used. The top bar itself is not visible but instead the purple background is shown where the top bar resides. The problem also occurs when replacing '-device qxl-vga' by '-device VGA,vgamem_mb=64'. The problem however does not occur when using '-device virtio-vga'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2000739/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2001922] Re: Xorg crash
Next time a crash happens please: 1. Wait 10 seconds. 2. Reboot. 3. Run: journalctl -b-1 > prevboot.txt 4. Attach the resulting text file here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2001922 Title: Xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: My Ubuntu 22.04.1 LTS installation crashes, but I was not able to figure out how to reproducibly trigger the crash. The last time it happened was with firefox and zoom running, the display suddenly went black and after a few seconds the X login screen appeared, my session gone. There are files in /var/crash/ -rw-r--r-- 1 root whoopsie0 Jan 5 14:09 _usr_lib_xorg_Xorg.0.upload -rw-r- 1 root whoopsie 12792518 Jan 5 14:09 _usr_lib_xorg_Xorg.0.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:09 _usr_lib_xorg_Xorg.0.uploaded -rw-r--r-- 1 petr whoopsie0 Jan 5 14:13 _usr_bin_xfsettingsd.1000.upload -rw-r- 1 petr whoopsie 516897 Jan 5 14:13 _usr_bin_xfsettingsd.1000.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:13 _usr_bin_xfsettingsd.1000.uploaded -rw-r--r-- 1 petr whoopsie0 Jan 5 14:13 _opt_zoom_zoom.1000.upload -rw-r- 1 petr whoopsie 46590288 Jan 5 14:13 _opt_zoom_zoom.1000.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:13 _opt_zoom_zoom.1000.uploaded and .xsession-errors.old ends with (xfwm4:8122): xfwm4-WARNING **: 14:11:00.736: unmanaged net_wm_state (window 0x649, atom "_NET_WM_STATE_STAYS_ON_TOP") (xfwm4:10847): Gtk-WARNING **: 14:13:01.216: cannot open display: :0.0 Exiting due to channel error. Failed to parse arguments: Cannot open display: :0.0 Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. (xfsettingsd:10849): xfsettingsd-ERROR **: 14:13:01.239: Unable to open display. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. (xfwm4:10854): Gtk-WARNING **: 14:13:01.244: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 (xfwm4:10860): Gtk-WARNING **: 14:13:01.264: cannot open display: :0.0 (xfwm4:10863): Gtk-WARNING **: 14:13:01.280: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 (xfwm4:10865): Gtk-WARNING **: 14:13:01.293: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Is it safe and useful to upload the files from /var/crash/? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Thu Jan 5 14:17:42 2023 DistUpgraded: 2022-12-25 11:03:07,557 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.13.0-35-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-56-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:3f96] InstallationDate: Installed on 2021-11-07 (424 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20YA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-35-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to jammy on 2022-12-25 (11 days ago) dmi.bios.date: 09/23/2021 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: GMCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: ThinkBook 13s G3 ACN dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrGMCN27WW:bd09/23/2021:br1.27:efr1.19:svnLENOVO:pn20YA:pvrThinkBook13sG3ACN:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrThinkBook13sG3ACN:skuLENOVO_MT_20YA_BU_idea_FM_ThinkBook13sG3ACN: dmi.product.family: ThinkBook 13s
[Desktop-packages] [Bug 1846398] Re: [modeset] xrandr transformations cause significant visible tearing in Xorg sessions
Just a reminder that most Ubuntu users can ignore this bug now because most are getting Wayland by default instead. -- 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/1846398 Title: [modeset] xrandr transformations cause significant visible tearing in Xorg sessions Status in X.Org X server: New Status in xorg-server package in Ubuntu: Triaged Bug description: On my laptop, fractional scaling seems fine, including watching a YouTube video. It has a quad HD display. Enabling fractional scaling on my desktop which is attached to a single 4k display, fractional scaling isn't usable. The video appears to be constantly refreshing and not using the same acceleration as if I just run at 100% or 200%. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 2 14:23:33 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-07-24 (435 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-07-19 (74 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1846398/+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 1985869] Re: Screen does not update [Failed to post KMS update: CRTC property (GAMMA_LUT) not found and Page flip discarded: CRTC property (GAMMA_LUT) not found]
*** This bug is a duplicate of bug 1995573 *** https://bugs.launchpad.net/bugs/1995573 Fixed in bug 1995573. ** This bug has been marked a duplicate of bug 1995573 Screen cannot turn on after screen off with Matrox G200eW3 [102b:0536] ** Summary changed: - Screen does not update [Failed to post KMS update: CRTC property (GAMMA_LUT) not found and Page flip discarded: CRTC property (GAMMA_LUT) not found] + [mgag200] Screen does not update [Failed to post KMS update: CRTC property (GAMMA_LUT) not found and Page flip discarded: CRTC property (GAMMA_LUT) not found] -- 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/1985869 Title: [mgag200] Screen does not update [Failed to post KMS update: CRTC property (GAMMA_LUT) not found and Page flip discarded: CRTC property (GAMMA_LUT) not found] Status in Mutter: New Status in OEM Priority Project: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: == ApportVersion = 2.20.11-0ubuntu82.1 == Architecture = amd64 == CasperMD5CheckResult = pass == Date = Fri Aug 12 16:01:31 2022 == Dependencies = accountsservice 22.07.5-2ubuntu1.3 acl 2.3.1-1 adduser 3.118ubuntu5 adwaita-icon-theme 41.0-1ubuntu1 alsa-topology-conf 1.2.5.1-2 alsa-ucm-conf 1.2.6.3-1ubuntu1 apg 2.2.3.dfsg.1-5build2 apport 2.20.11-0ubuntu82.1 apport-symptoms 0.24 apt 2.4.6 apt-utils 2.4.6 aptdaemon 1.1.1+bzr982-0ubuntu39 aptdaemon-data 1.1.1+bzr982-0ubuntu39 aspell 0.60.8-4build1 aspell-en 2018.04.16-0-1 at-spi2-core 2.44.0-3 avahi-daemon 0.8-5ubuntu5 avahi-utils 0.8-5ubuntu5 base-files 12ubuntu4.2 bash 5.1-6ubuntu1 bash-completion 1:2.11-5ubuntu1 bind9-host 1:9.18.1-1ubuntu1.1 bind9-libs 1:9.18.1-1ubuntu1.1 bluez 5.64-0ubuntu1 bolt 0.9.2-1 bsdextrautils 2.37.2-4ubuntu3 bubblewrap 0.6.1-1 ca-certificates 20211016 cheese-common 41.1-1build1 colord 1.4.6-1 colord-data 1.4.6-1 coreutils 8.32-4.1ubuntu1 cpp 4:11.2.0-1ubuntu1 cpp-11 11.2.0-19ubuntu1 cracklib-runtime 2.9.6-3.4build4 cups-pk-helper 0.2.6-1ubuntu5 [ 6902.723370] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property (GAMMA_LUT) not found [ 7123.822417] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC property (GAMMA_LUT) not found [ 7123.823384] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property (GAMMA_LUT) not found [ 7124.335913] ubuntu1 gnome-shell[2773]: JS ERROR: Failed to initialize fprintd service: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name net.reactivated.Fprint was not provided by any .service files asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23 [ 7180.309459] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC property (GAMMA_LUT) not found [ 7180.311605] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property (GAMMA_LUT) not found [ 7218.558479] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC property (GAMMA_LUT) not found [ 7218.559502] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property (GAMMA_LUT) not found [ 7244.319195] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC property (GAMMA_LUT) not found [ 7244.320182] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property (GAMMA_LUT) not found [ 7295.446436] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC property (GAMMA_LUT) not found [ 7295.447812] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property (GAMMA_LUT) not found [ 7573.588299] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC property (GAMMA_LUT) not found [ 7573.590411] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property (GAMMA_LUT) not found [ 7574.868039] ubuntu1 gnome-shell[2773]: JS ERROR: Failed to initialize fprintd service: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name net.reactivated.Fprint was not provided by any .service files asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23 [ 7654.509594] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC property (GAMMA_LUT) not found [ 7654.510955] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property (GAMMA_LUT) not found [ 7751.955703] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC property (GAMMA_LUT) not found [ 7751.957582] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property (GAMMA_LUT) not found [ 7965.552231] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC property (GAMMA_LUT) not found [ 7965.553842] ubuntu1 gnome-shell[2773]
[Desktop-packages] [Bug 1991777] Re: gnome-shell deadlocked on startup [Failed to post KMS update: CRTC property (GAMMA_LUT) not found] on Alder Lake with older kernels
** Summary changed: - gnome-shell deadlocked on startup + gnome-shell deadlocked on startup [Failed to post KMS update: CRTC property (GAMMA_LUT) not found] on Alder Lake with older kernels ** This bug is no longer a duplicate of bug 1985869 Screen does not update [Failed to post KMS update: CRTC property (GAMMA_LUT) not found and Page flip discarded: CRTC property (GAMMA_LUT) not found] ** Package changed: gnome-shell (Ubuntu) => mutter (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/1991777 Title: gnome-shell deadlocked on startup [Failed to post KMS update: CRTC property (GAMMA_LUT) not found] on Alder Lake with older kernels Status in mutter package in Ubuntu: New Bug description: My Ubuntu session is currently impossible to launch. Upon trying, I get a couple ~blank displays, sometimes along with a cursor at the position it was in GDM. Only way out is `chvt …`, or killing gnome-shell, over SSH. "Ubuntu on Xorg" works fine. The wayland session does work for a test user as well. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Oct 5 11:47:11 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-08-31 (34 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 43.0-1ubuntu1 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/mutter/+bug/1991777/+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 2002349] Re: I powered off and when I turned my computer on this hapened
** 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/2002349 Title: I powered off and when I turned my computer on this hapened Status in xorg package in Ubuntu: New Bug description: It's stuck at 640x480 and I can barely do anything at all I'm using Ubuntu 20.04 I cannot even update my computer ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-57.63~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 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: Mon Jan 9 14:36:01 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rtl882bu, 5.8.7.1, 5.15.0-57-generic, x86_64: installed rtl88x2bu, 5.8.7.1, 5.13.0-30-generic, x86_64: installed rtl88x2bu, 5.8.7.1, 5.15.0-57-generic, x86_64: installed (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] [19da:2476] InstallationDate: Installed on 2023-01-08 (1 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-57-generic root=UUID=9456410b-fb68-463f-b197-a8e997ea4477 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-I dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd03/07/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-I:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer 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.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2002349/+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 2002349] [NEW] I powered off and when I turned my computer on this hapened
You have been subscribed to a public bug: It's stuck at 640x480 and I can barely do anything at all I'm using Ubuntu 20.04 I cannot even update my computer ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-57.63~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 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: Mon Jan 9 14:36:01 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rtl882bu, 5.8.7.1, 5.15.0-57-generic, x86_64: installed rtl88x2bu, 5.8.7.1, 5.13.0-30-generic, x86_64: installed rtl88x2bu, 5.8.7.1, 5.15.0-57-generic, x86_64: installed (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] [19da:2476] InstallationDate: Installed on 2023-01-08 (1 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-57-generic root=UUID=9456410b-fb68-463f-b197-a8e997ea4477 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-I dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd03/07/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-I:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer 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.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal resolution ubuntu -- I powered off and when I turned my computer on this hapened https://bugs.launchpad.net/bugs/2002349 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg 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 1917887] Re: Network Manager OpenVPN nested connections fail to setup routes correctly
** Changed in: openvpn Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1917887 Title: Network Manager OpenVPN nested connections fail to setup routes correctly Status in OpenVPN: Fix Released Status in network-manager package in Ubuntu: Triaged Status in openvpn package in Ubuntu: Invalid Bug description: Setup: Host lan: 192.168.0.238/24 Host Default gw: 192.168.0.1 ip route: default via 192.168.0.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 Primary OpenVPN (check "Use this connection only for resources on its network"): server ip: public a.b.c.d OpenVPN Tunnel: 192.168.1.0/24 routes pushed: 192.168.100.0/24 First VPN works OK: default via 192.168.0.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 192.168.0.1 dev eno1 proto static scope link metric 100 192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 Secondary OpenVPN (check "Use this connection only for resources on its network"): server ip: private 192.168.100.10 OpenVPN Tunnel: 192.168.20.0/24 routes pushed: 192.168.200.0/24 Second VPN Connect OK, routing table is wrong: default via 192.168.0.1 dev eno1 proto dhcp metric 100 192.168.200.0/24 via 192.168.20.1 dev tun1 192.168.20.0/24 dev tun1 proto kernel scope link src 192.168.20.59 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 192.168.0.1 dev eno1 proto static scope link metric 100 192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 192.168.100.10 via 192.168.0.1 dev eno1 proto static metric 100 <- this is wrong, the openVPN#2 Gateway is not on the local lan Correct routing table using "sudo /usr/sbin/openvpn /path/to/config.openvpn" (same a Network Manager) default via 192.168.0.1 dev eno1 proto dhcp metric 100 192.168.200.0/24 via 192.168.20.1 dev tun1 192.168.20.0/24 dev tun1 proto kernel scope link src 192.168.20.59 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 192.168.0.1 dev eno1 proto static scope link metric 100 192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 It seems that Network Manager add a wrong additional route not added by the openvpn bin: 192.168.100.10 via 192.168.0.1 dev eno1 proto static metric 100 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openvpn 2.4.7-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Mar 5 12:44:39 2021 InstallationDate: Installed on 2021-02-19 (13 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: openvpn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/openvpn/+bug/1917887/+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 1803885] Re: Lenovo R60 screen corrupt immediately after install
We have found that most of our users are Espanol speaking, So for a better experience and enjoyable moment https://wordle-unlimited.online/spanish-wordle/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1803885 Title: Lenovo R60 screen corrupt immediately after install Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: Version : Ubuntu 18.04.1 LTS Immediately after the install completes. The computer restarts to a corrupt login screen. Hardware : Lenovo R60 Video : 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV515/M54 [Mobility Radeon X1400] Xorg.log AMD Radeon HD 6900M Series, Mobility Radeon HD 6000 Series, BARTS, AMD Radeon HD 6800 Series, AMD Radeon HD 6700 Series, TURKS, CAICOS, ARUBA, TAHITI, PITCAIRN, VERDE, OLAND, HAINAN, BONAIRE, KABINI, MULLINS, KAVERI, HAWAII [13.133] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [13.133] (II) FBDEV: driver for framebuffer: fbdev [13.133] (II) VESA: driver for VESA chipsets: vesa [13.135] (II) [KMS] drm report modesetting isn't supported. [13.135] (EE) open /dev/dri/card0: No such file or directory [13.135] (WW) Falling back to old probe method for modesetting [13.135] (EE) open /dev/dri/card0: No such file or directory [13.135] (II) Loading sub module "fbdevhw" [13.135] (II) LoadModule: "fbdevhw" [13.136] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so [13.137] (II) Module fbdevhw: vendor="X.Org Foundation" [13.137]compiled for 1.19.6, module version = 0.0.2 [13.137]ABI class: X.Org Video Driver, version 23.0 [13.137] (**) FBDEV(2): claimed PCI slot 1@0:0:0 [13.137] (II) FBDEV(2): using default device [13.137] (WW) Falling back to old probe method for vesa [13.137] (EE) Screen 0 deleted because of no matching config section. [13.137] (II) UnloadModule: "radeon" [13.137] (EE) Screen 0 deleted because of no matching config section. [13.137] (II) UnloadModule: "modesetting" [13.138] (II) FBDEV(0): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 24/32 [13.138] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32 After some digging, on another computer, adding nomodeset to the kernal startup parameters helps. Edited /etc/default/grub GRUB_CMDLINE_LINUX="nomodeset" $update-grub provides a usable but degraded session. The screen resolution is 1400x1050. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1803885/+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 1010683] Re: ATI Resume from Suspend leads into black screen (VGA_Switcheroo)
This means that you cannot simply guess the word right away; you must use the clues given to you to figure out the secret word. https://wordle-unlimited.us/wordle-junior/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1010683 Title: ATI Resume from Suspend leads into black screen (VGA_Switcheroo) Status in Linux: Confirmed Status in xserver-xorg-driver-ati: Unknown Status in xserver-xorg-video-ati package in Ubuntu: Incomplete Bug description: I have a HP Touchsmart 2 (tm2). This Notebook has 2 Graphiccars: Intel (DIS) and ATI (IGD): # lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Manhattan [Mobility Radeon HD 5400 Series] If i use the Intel-Graphiccard, everything works well, i can suspend and resume as often as i'd like. Edit: As soon as I switched (switch to ATI and back to Intel, the below problem happens on Intel-GPU too). If i use the ATI-Graphiccard i can suspend (wich takes a longer time than with the Intel one) however I can't resume. I get a blank/black screen and can't change brightness. Plus I can't switch to any tty. I've tried this instructions to find an error: https://wiki.ubuntu.com/DebuggingKernelSuspend but it dosn't seem to bring relevant informations (however, I'll add the dmesg.txt to this bugreport) PS: to switch between graphiccards, I use "vga_switcheroo" and i have "vanilla"-ubuntu, no third party software. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.1.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.317 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Fri Jun 8 20:54:43 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1486] Advanced Micro Devices [AMD] nee ATI Manhattan [Mobility Radeon HD 5400 Series] [1002:68e0] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TouchSmart tm2-2050er discrete GPU (Mobility Radeon HD 5450) [103c:1486] LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120606.2) MachineType: Hewlett-Packard HP TouchSmart tm2 Notebook PC ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/username.seed boot=casper quiet splash -- persistent BOOT_IMAGE=/casper/vmlinuz SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2010 dmi.bios.vendor: Insyde dmi.bios.version: F.12 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1486 dmi.board.vendor: Hewlett-Packard dmi.board.version: 83.1A dmi.chassis.asset.tag: CNU0250216 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.12:bd07/30/2010:svnHewlett-Packard:pnHPTouchSmarttm2NotebookPC:pvr048920252A2000122:rvnHewlett-Packard:rn1486:rvr83.1A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP TouchSmart tm2 Notebook PC dmi.product.version: 048920252A2000122 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.7.8-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu11 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.19.0-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20120322+ab7291d-1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1010683/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Uns
[Desktop-packages] [Bug 1721960] Re: Flickering on AMD R9 270X
This means that you cannot simply guess the word right away; you must use the clues given to you to figure out the secret word. https://wordle-unlimited.us/wordle-junior/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1721960 Title: Flickering on AMD R9 270X Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: SO: Ubuntu 17.04 xserver-xorg-video-ati version: 1:7.9.0-0ubuntu1 Graphics: Gallium 0.4 on AMD PITCAIRN (DRM 2.49.0 / 4.10.0-35-generic, LLVM 4.0.0) GPU: Sapphire R9 270X The screen flickers every time the GPU recieves some workload (e.g. moving the mouse or opening a window). This is probably caused by the DPM (dynamic power management). The bug is gone when I set /sys/class/drm/card0/device/power_dpm_force_performance_level to high or low. The bug is present when set to auto. I know that some people has removed his R9 270X from the quirk list and recompiled the kernel fixing the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1721960/+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 1923153] Re: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
With these factors in mind, you’re sure to find https://www.printersjet.com/best-sublimation-ink/ the best sublimation inks for your needs. So what are you waiting for? Start shopping today! -- 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/1923153 Title: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) Status in OEM Priority Project: Confirmed Status in xserver-xorg-driver-ati: New Status in xorg-server package in Ubuntu: New Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: [Steps to reproduce this issue] 1. Install a focal base image 2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it. 3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or AMD(amdgpu)). 4. After logging it, the display shows laggy. [Additional information] 1. doesn't see this issue if selecting 'Wayland' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18 Uname: Linux 5.10.0-1019-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 9 16:23:42 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [103c:3375] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:872b] InstallationDate: Installed on 2021-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210324-23:53 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 2.0 dmi.bios.vendor: HP dmi.bios.version: S09 Ver. 02.02.00 dmi.board.name: 872B dmi.board.vendor: HP dmi.board.version: KBC Version 09.94.00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.148 dmi.modalias: dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923153/+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 1846398] Re: [modeset] xrandr transformations cause significant visible tearing in Xorg sessions
For testing I've created a PPA with the patches applied to 21.1.6: https://launchpad.net/%7Ejeff250/+archive/ubuntu/xserver-xorg-with- tearfree-modesetting Since using it I haven't seen any tearing, and I haven't seen any new issues (yet!) either. -- 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/1846398 Title: [modeset] xrandr transformations cause significant visible tearing in Xorg sessions Status in X.Org X server: New Status in xorg-server package in Ubuntu: Triaged Bug description: On my laptop, fractional scaling seems fine, including watching a YouTube video. It has a quad HD display. Enabling fractional scaling on my desktop which is attached to a single 4k display, fractional scaling isn't usable. The video appears to be constantly refreshing and not using the same acceleration as if I just run at 100% or 200%. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 2 14:23:33 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-07-24 (435 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-07-19 (74 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1846398/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2001922] Re: Xorg crash
Two more crashes, this time without a new entries in /var/crash/. What can I do to collect more information? The system was stable before I upgraded from impish to 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/2001922 Title: Xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: My Ubuntu 22.04.1 LTS installation crashes, but I was not able to figure out how to reproducibly trigger the crash. The last time it happened was with firefox and zoom running, the display suddenly went black and after a few seconds the X login screen appeared, my session gone. There are files in /var/crash/ -rw-r--r-- 1 root whoopsie0 Jan 5 14:09 _usr_lib_xorg_Xorg.0.upload -rw-r- 1 root whoopsie 12792518 Jan 5 14:09 _usr_lib_xorg_Xorg.0.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:09 _usr_lib_xorg_Xorg.0.uploaded -rw-r--r-- 1 petr whoopsie0 Jan 5 14:13 _usr_bin_xfsettingsd.1000.upload -rw-r- 1 petr whoopsie 516897 Jan 5 14:13 _usr_bin_xfsettingsd.1000.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:13 _usr_bin_xfsettingsd.1000.uploaded -rw-r--r-- 1 petr whoopsie0 Jan 5 14:13 _opt_zoom_zoom.1000.upload -rw-r- 1 petr whoopsie 46590288 Jan 5 14:13 _opt_zoom_zoom.1000.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:13 _opt_zoom_zoom.1000.uploaded and .xsession-errors.old ends with (xfwm4:8122): xfwm4-WARNING **: 14:11:00.736: unmanaged net_wm_state (window 0x649, atom "_NET_WM_STATE_STAYS_ON_TOP") (xfwm4:10847): Gtk-WARNING **: 14:13:01.216: cannot open display: :0.0 Exiting due to channel error. Failed to parse arguments: Cannot open display: :0.0 Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. (xfsettingsd:10849): xfsettingsd-ERROR **: 14:13:01.239: Unable to open display. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. (xfwm4:10854): Gtk-WARNING **: 14:13:01.244: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 (xfwm4:10860): Gtk-WARNING **: 14:13:01.264: cannot open display: :0.0 (xfwm4:10863): Gtk-WARNING **: 14:13:01.280: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 (xfwm4:10865): Gtk-WARNING **: 14:13:01.293: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Is it safe and useful to upload the files from /var/crash/? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Thu Jan 5 14:17:42 2023 DistUpgraded: 2022-12-25 11:03:07,557 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.13.0-35-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-56-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:3f96] InstallationDate: Installed on 2021-11-07 (424 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20YA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-35-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to jammy on 2022-12-25 (11 days ago) dmi.bios.date: 09/23/2021 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: GMCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: ThinkBook 13s G3 ACN dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrGMCN27WW:bd09/23/2021:br1.27:efr1.19:svnLENOVO:pn20YA:pvrThinkBook13sG3ACN:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrThinkBook13sG3ACN:skuLENOVO_MT_20YA_BU_idea_FM_ThinkBook13sG3ACN: dmi.product.fa
[Desktop-packages] [Bug 2001914] Re: The gpu hangs and is not possible to work with GPU-envioronment
*** This bug is a duplicate of bug 1998950 *** https://bugs.launchpad.net/bugs/1998950 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/2001914 Title: The gpu hangs and is not possible to work with GPU-envioronment Status in gnome-shell package in Ubuntu: Confirmed Bug description: When I open the terminal or just browsing, gnom sometimes freezes for a second, but sometimes restart the machine is necessary. The log is: Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm]i915 :00:02.0: [drm] GPU HANG: ecode 12:0: Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] GuC firmware i915/adlp_guc_62.0.3.bin version 62.0 submission:enabled Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] GuC SLPC: enabled Jan 05 12:10:40 Linux kernel: i915 :00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin version 7.9 authenticated:yes Jan 05 12:10:40 Linux gnome-shell[2584]: Window manager warning: last_user_time (2748010) is greater than comparison timestamp (2743419). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Jan 05 12:10:40 Linux gnome-shell[2584]: Window manager warning: 0xc0003c appears to be one of the offending windows with a timestamp of 2748010. Working around... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg ./boot/grub/loopback.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Thu Jan 5 12:25:49 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-02 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.5-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/2001914/+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 1998893] Re: NV reverse prime HDMI has no output
** Changed in: mesa (Ubuntu Jammy) Status: Fix Committed => In Progress -- 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/1998893 Title: NV reverse prime HDMI has no output Status in OEM Priority Project: New Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: In Progress Bug description: [Impact] The X failed to load glamoregl module on Dell's new platforms, the module is needed by NV dGPU. 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) LoadModule: "glamoregl" 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Loading /usr/lib/xorg/modules/libglamoregl.so 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Module glamoregl: vendor="X.Org Foundation" 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: compiled for 1.21.1.3, module version = 1.0.1 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: ABI class: X.Org ANSI C Emulation, version 0.4 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: MESA: warning: Driver does not support the 0xa78b PCI ID. 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): Refusing to try glamor on llvmpipe 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): glamor initialization failed [Fix] The upstream PR added missing ID for the platforms. https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/16320/ https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/17569/ After creating the test build to include the PR above, ODM verified passed on those platform. [Test case] Install fixed package on the systems, check that display works. [Where things could go wrong] Although one commit drops a couple of pci-id's, they were already dropped from the jammy kernel for lp1990242 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998893/+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 1998893] Re: NV reverse prime HDMI has no output
I think this bug/SRU snowballed. Let's take a step back. It started with fixing two bugs: this one, and bug #1972977. At some point later, #1972977 was deemed not really fixed[1], and was dropped in the 0ubuntu0.3 upload[2]. That upload failed to build in jammy-proposed on arm64[3] and amd64[4]. It was deemed to be a problem introduced by some other jammy-proposed upload (unclear which one). A new upload was made to jammy unapproved[5] (still missing an update- maintainer run, btw), stating: Changes: mesa (22.0.5-0ubuntu0.4) jammy; urgency=medium . * Add a patch to build with a newer directx-headers. (LP: #1998893) . mesa (22.0.5-0ubuntu0.3) jammy; urgency=medium . * crocus-fix-leak-in-query-code.patch: Drop the patch so the other fix can get through to updates. . mesa (22.0.5-0ubuntu0.2) jammy; urgency=medium . * crocus-fix-leak-in-query-code.patch: Fix gnome-shell crashing on older Intel hw. (LP: #1972977) * patches: Update pci-id's for ADL-S/RPL-S. (LP: #1998893) That is quite a big patch in an area I know nothing about. My concerns are: - shouldn't we have a separate bug for the FTBFS? This bug here is about PCI IDs. - what is the other package in jammy proposed that is breaking this build? Must it be released at the same time as mesa? - the original PR[6] mentioned in the DEP3 header of the FTBFS patch is huge and complex, is that (and the backport done here) really the minimal fix for the FTBFS? - what are the other changes incurring via this patch, now the the build is fixed? What else is changing? What is the risk analysis of that change? I feel there is a lot of missing information, but it could just be because I'm not familiar with mesa and the graphic/3d stack. So I prefer to leave this review for another SRU team member, but thought I should leave this comment here instead of just "disappearing" :) 1. https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1972977/comments/15 2. https://launchpad.net/ubuntu/+source/mesa/22.0.5-0ubuntu0.3 3. https://launchpad.net/ubuntu/+source/mesa/22.0.5-0ubuntu0.3/+build/25458695 4. https://launchpad.net/ubuntu/+source/mesa/22.0.5-0ubuntu0.3/+build/25458694 5. https://launchpadlibrarian.net/645131833/mesa_22.0.5-0ubuntu0.4_source.changes 6. https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/15751/diffs -- 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/1998893 Title: NV reverse prime HDMI has no output Status in OEM Priority Project: New Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: In Progress Bug description: [Impact] The X failed to load glamoregl module on Dell's new platforms, the module is needed by NV dGPU. 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) LoadModule: "glamoregl" 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Loading /usr/lib/xorg/modules/libglamoregl.so 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Module glamoregl: vendor="X.Org Foundation" 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: compiled for 1.21.1.3, module version = 1.0.1 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: ABI class: X.Org ANSI C Emulation, version 0.4 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: MESA: warning: Driver does not support the 0xa78b PCI ID. 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): Refusing to try glamor on llvmpipe 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): glamor initialization failed [Fix] The upstream PR added missing ID for the platforms. https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/16320/ https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/17569/ After creating the test build to include the PR above, ODM verified passed on those platform. [Test case] Install fixed package on the systems, check that display works. [Where things could go wrong] Although one commit drops a couple of pci-id's, they were already dropped from the jammy kernel for lp1990242 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998893/+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 1998207] Re: netplan network-manager plugin tries to save temporary connections
Unfortunately this is still happening with the patch from comment #3. In fact I do not even need to create a VPN connection for this. If I install easy-openvpn-server: $ snap install easy-openvpn-server it creates two tun devices (tun0 and tun1) that can be seen with "ip address" command. That makes NM create the corresponding devices and connections: /ssh:ubuntu@localhost#8022: $ /snap/bin/network-manager.nmcli c NAME UUID TYPE DEVICE netplan-ens3 bec3d02a-c9e5-3283-92ab-ee43a4246c85 ethernet ens3 tun0 edc2d2e1-b126-475d-8d5b-1a5b3bfd43d3 tun tun0 tun1 2945f4f4-2d44-4a61-83b4-cee73fd81129 tun tun1 /ssh:ubuntu@localhost#8022: $ /snap/bin/network-manager.nmcli d DEVICE TYPE STATE CONNECTION ens3ethernet connected netplan-ens3 tun0tun connected (externally) tun0 tun1tun connected (externally) tun1 lo loopback unmanaged but unfortunately these connections are still written as static connections in /etc/netplan/. And when I reboot, I see 4 of them: /ssh:ubuntu@localhost#8022: $ /snap/bin/network-manager.nmcli c NAME UUID TYPE DEVICE netplan-ens3 bec3d02a-c9e5-3283-92ab-ee43a4246c85 ethernet ens3 tun0 864e0de2-e5c6-4c9b-aa7f-20aef970067c tun tun0 tun1 ddfc7db2-2baa-488f-95da-c8e1e66e458b tun tun1 default be2bc22c-fc98-4b2b-9484-fd4d5c838d5f vpn -- tun0 3c1e12f9-1a08-4a6f-aef3-5ea22d9e9bb2 tun -- tun1 eb8ed73b-3312-401f-a4c4-c26aadb3a014 tun -- The files look like https://paste.ubuntu.com/p/KvTVXPwK75/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1998207 Title: netplan network-manager plugin tries to save temporary connections Status in netplan: Triaged Status in network-manager package in Ubuntu: Fix Committed Bug description: When creating an OpenVPN connection, a temporal connection called tunN is created. For instance, after activating a connection called vpntest, I have: NAME UUID TYPE DEVICE vpntest 458856e6-8f0f-4dc6-82f2-dd72868252a0 vpn ens3 tun0 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 tun tun0 tun0 is created/removed after activating/deactivating vpntest and should not really be saved, but I see netplan adding it in /etc/netplan. And while doing so the plugin also reports some errors (I see these when stopping the connection): Nov 28 16:16:57 ubuntu NetworkManager[11752]: [1669652217.2920] BUG: the profile cannot be stored in keyfile format without becoming unusable: cannot access file: No such file or directory Nov 28 16:16:57 ubuntu NetworkManager[11752]: ((src/libnm-core-impl/nm-connection.c:342)): assertion '' failed Nov 28 16:16:57 ubuntu NetworkManager[11752]: [1669652217.2920] keyfile: commit: failure to write 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 ((null)) to "/run/NetworkManager/system-connections/tun0-1eb1dbe8-5678-4818-9adf-fb2dc01ed132.nmconnection": keyfile writer produces an invalid connection: cannot access file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1998207/+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 2002332] [NEW] [22.04] Cannot see thumbnail in MTP of PTP mode in Nautilus
Public bug reported: Usage of USB to see / copy photos from an Android phone is still useful in 2023 With Ubuntu 22.04 up to date : - Connect your Android phone ( Android 10 lineageos here ) - Choose MTP : open nautilus and browse -> No thumbnail for your pictures - Choose PTP : open nautilus and browse -> No thumbnail for your pictures - Choose PTP : open Shotwell and browse -> Some thumbnails appears Without thumbnails , it is almost impossible to choose what to copy. ** Affects: libmtp (Ubuntu) Importance: Undecided Status: New ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Also affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmtp in Ubuntu. https://bugs.launchpad.net/bugs/2002332 Title: [22.04] Cannot see thumbnail in MTP of PTP mode in Nautilus Status in libmtp package in Ubuntu: New Status in nautilus package in Ubuntu: New Bug description: Usage of USB to see / copy photos from an Android phone is still useful in 2023 With Ubuntu 22.04 up to date : - Connect your Android phone ( Android 10 lineageos here ) - Choose MTP : open nautilus and browse -> No thumbnail for your pictures - Choose PTP : open nautilus and browse -> No thumbnail for your pictures - Choose PTP : open Shotwell and browse -> Some thumbnails appears Without thumbnails , it is almost impossible to choose what to copy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/2002332/+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 1991934] Re: mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied error pipewire on Ubuntu kinetic
** Bug watch added: gitlab.freedesktop.org/pipewire/pipewire/-/issues #1069 https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1069 ** Also affects: pipewire via https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1069 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/1991934 Title: mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied error pipewire on Ubuntu kinetic Status in PipeWire: Unknown Status in pipewire package in Ubuntu: Confirmed Status in pipewire package in Debian: New Bug description: Started PipeWire Multimedia Service. mod.rt: Can't find xdg-portal: (null) mod.rt: found session bus but no portal mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied mod.rt: could not make thread 4909 realtime using RTKit: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/pipewire/+bug/1991934/+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 2002324] [NEW] Unable to paste to X11 app
Public bug reported: If I copy text from gnome-text-editor 43.1 (from ubuntu 22.10) to the clipboard, the mime type is only set to "text/plain;charset=utf-8". This mime type does not allow to "paste" the content to X11 apps (e.g., Putty). For most of the wayland apps (e.g., gnome terminal), the mime type is more broad: text/plain text/plain;charset=utf-8 STRING TEXT COMPOUND_TEXT UTF8_STRING How to reproduce: 1. Login to ubuntu using wayland 2. Open "gnonme-text-editor" and copy some text 3. Use "wl-paste --list-types" to show the mime type ** Affects: gnome-text-editor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-text-editor in Ubuntu. https://bugs.launchpad.net/bugs/2002324 Title: Unable to paste to X11 app Status in gnome-text-editor package in Ubuntu: New Bug description: If I copy text from gnome-text-editor 43.1 (from ubuntu 22.10) to the clipboard, the mime type is only set to "text/plain;charset=utf-8". This mime type does not allow to "paste" the content to X11 apps (e.g., Putty). For most of the wayland apps (e.g., gnome terminal), the mime type is more broad: text/plain text/plain;charset=utf-8 STRING TEXT COMPOUND_TEXT UTF8_STRING How to reproduce: 1. Login to ubuntu using wayland 2. Open "gnonme-text-editor" and copy some text 3. Use "wl-paste --list-types" to show the mime type To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-text-editor/+bug/2002324/+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 2002321] [NEW] computer is too slow.
Public bug reported: i dont know much about those computer term,but if could you help me somehow i would be very greatfull. thanx A.B. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.4.0-050400-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Jan 9 16:11:37 2023 DistUpgraded: 2022-12-25 23:43:14,353 INFO cache.commit() DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:064b] InstallationDate: Installed on 2018-04-19 (1726 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Acer TravelMate P253 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-050400-generic root=UUID=a81ad045-d2f8-4909-8aef-d7239d261ada ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2022-12-25 (14 days ago) dmi.bios.date: 12/16/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: BA51_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.21 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.21:bd12/16/2013:svnAcer:pnTravelMateP253:pvrV2.21:rvnAcer:rnBA51_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.21: dmi.product.family: Type1Family dmi.product.name: TravelMate P253 dmi.product.sku: TravelMate P253_064B_V2.21 dmi.product.version: V2.21 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.110-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sat Dec 1 18:03:02 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages 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/2002321 Title: computer is too slow. Status in xorg package in Ubuntu: New Bug description: i dont know much about those computer term,but if could you help me somehow i would be very greatfull. thanx A.B. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.4.0-050400-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Jan 9 16:11:37 2023 DistUpgraded: 2022-12-25 23:43:14,353 INFO cache.commit() DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:064b] InstallationDate: Installed on 2018-04-19 (1726 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Acer TravelMate P253 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-050400-generic root=UUID=a81ad045-d2f8-4909-8aef-d7239d261ada ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2022-12-25 (14 days ago) dmi.bios.date: 12/16/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: BA51_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.21 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.21:bd12/16/2013:svnAcer:pnTravelMateP253:pvrV2.21:rvnAcer:rnBA51_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.21: dmi.product.family: Type1Family dmi.product.name: TravelMate P253 dmi.p
[Desktop-packages] [Bug 2002314] Re: System freezes after locking screen with the nouveau driver
** Description changed: - This is a Hybrid graphics laptop with Ubuntu 22.10 and xserver-xorg- - video-nouveau version 1.0.17-2build1. + This is a Hybrid graphics laptop with Ubuntu 22.10 (also happened with + 22.04) and xserver-xorg-video-nouveau version 1.0.17-2build1. After locking the screen manually or automatically after the specified timeout, the whole laptop freeze or behave extremely slow, either ways a hard reset is a must by holding the power button to bring it back to life. This doesn't happen if the nvidia proprietary driver is used. Right after a fresh boot, you can see the nouveau error in the attached dmesg.txt file. Sometimes while trying to unlock or switching to tty it shows such errors: 4010.649752) rcus INFO: rcu preempt detected stalls on CPUs/tasks: 4010.649766) rcus $0-...1: (1 GPs behind) idle-a58/0/0x0 softirq=30921/30922 fqs=0 (false positive?) 4010.649774) rout $2-... (0 ticks this GP) idle-4dc/0/0x0 softirq-26935/26935 fas-0 (false positive?) 4010.649776) rcut $3-...: (0 ticks this GP) idle-8ce/0/0x0 softirq-27111/27111 fqs=0 (false positive?) 4010.649777) rcus $4-...1: (1 GPs behind) idle-340/0/0x0 softirq-28041/28042 fqs=0 (false positive?) 4010.649779) rcus $6-...11 (0 ticks this GP) idle-86a/0/0x0 softirq-33526/33526 fas=0 (false positive?) 4010.649780) rous $7-... (1 GPs behind) idle=c01/1/0x4000 softirq-29455/29456 fqs=0 3115.864965) watchdog: BUG: soft lockup CPU#4 stuck for 515s! [Timer:5288) 3115.864972) 1915 :00:02.0: [drm] ERROR [CRTC:98:pipe A) filp.done timed out 3115.865030) watchdog: BUG: soft lockup- CPUW7 stuck for 515s! [Socket Thread:4856] 3115.865034) watchdog: BUG: soft lockup CPUW2 stuck for 515s! [snapd:5977) 3115.865046) watchdog: BUG: soft lockup- CPUW3 stuck for 515s! (openvpn:4633] 3115.865080) watchdog: BUG: soft lockup- CPU#6 stuck for $15s! [HebExtensions:5140) And: [2639.153118] NMI watchdog: Watchdog detected hard LOCKUP on cpu 7 [2661.862757] NHI watchdog: Watchdog detected hard LOCKUP on cpu 0 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xserver-xorg-video-nouveau 1:1.0.17-2build1 ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 Uname: Linux 5.19.0-28-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 9 15:59:37 2023 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.19.0-26-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-28-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 (4 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-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau 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 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/2002314 Title: System freezes after locking screen with the n
[Desktop-packages] [Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gtk+3.0 (Ubuntu Kinetic) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in Mozilla Firefox: New Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Status in gtk+3.0 source package in Jammy: Confirmed Status in gtk4 source package in Jammy: Triaged Status in gtk+3.0 source package in Kinetic: Confirmed Status in gtk4 source package in Kinetic: Triaged Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+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 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gtk+3.0 (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in Mozilla Firefox: New Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Status in gtk+3.0 source package in Jammy: Confirmed Status in gtk4 source package in Jammy: Triaged Status in gtk+3.0 source package in Kinetic: Confirmed Status in gtk4 source package in Kinetic: Triaged Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+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 2002314] Re: System freezes after locking screen with the nouveau driver
** Description changed: This is a Hybrid graphics laptop with Ubuntu 22.10 and xserver-xorg- video-nouveau version 1.0.17-2build1. After locking the screen manually or automatically after the specified timeout, the whole laptop freeze or behave extremely slow, either ways a hard reset is a must by holding the power button to bring it back to life. This doesn't happen if the nvidia proprietary driver is used. Right after a fresh boot, you can see the nouveau error in the attached dmesg.txt file. Sometimes while trying to unlock or switching to tty it shows such errors: 4010.649752) rcus INFO: rcu preempt detected stalls on CPUs/tasks: 4010.649766) rcus $0-...1: (1 GPs behind) idle-a58/0/0x0 softirq=30921/30922 fqs=0 (false positive?) 4010.649774) rout $2-... (0 ticks this GP) idle-4dc/0/0x0 softirq-26935/26935 fas-0 (false positive?) 4010.649776) rcut $3-...: (0 ticks this GP) idle-8ce/0/0x0 softirq-27111/27111 fqs=0 (false positive?) 4010.649777) rcus $4-...1: (1 GPs behind) idle-340/0/0x0 softirq-28041/28042 fqs=0 (false positive?) 4010.649779) rcus $6-...11 (0 ticks this GP) idle-86a/0/0x0 softirq-33526/33526 fas=0 (false positive?) 4010.649780) rous $7-... (1 GPs behind) idle=c01/1/0x4000 softirq-29455/29456 fqs=0 3115.864965) watchdog: BUG: soft lockup CPU#4 stuck for 515s! [Timer:5288) 3115.864972) 1915 :00:02.0: [drm] ERROR [CRTC:98:pipe A) filp.done timed out 3115.865030) watchdog: BUG: soft lockup- CPUW7 stuck for 515s! [Socket Thread:4856] 3115.865034) watchdog: BUG: soft lockup CPUW2 stuck for 515s! [snapd:5977) 3115.865046) watchdog: BUG: soft lockup- CPUW3 stuck for 515s! (openvpn:4633] 3115.865080) watchdog: BUG: soft lockup- CPU#6 stuck for $15s! [HebExtensions:5140) - And: [2639.153118] NMI watchdog: Watchdog detected hard LOCKUP on cpu 7 [2661.862757] NHI watchdog: Watchdog detected hard LOCKUP on cpu 0 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xserver-xorg-video-nouveau 1:1.0.17-2build1 ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 Uname: Linux 5.19.0-28-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 9 15:59:37 2023 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: - virtualbox/6.1.38, 5.19.0-26-generic, x86_64: installed - virtualbox/6.1.38, 5.19.0-28-generic, x86_64: installed + virtualbox/6.1.38, 5.19.0-26-generic, x86_64: installed + virtualbox/6.1.38, 5.19.0-28-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 (4 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-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau 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: ATN12345678901234567 + 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-
[Desktop-packages] [Bug 2000784] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2000784 Title: booting issue snd_hda_ intel codec dummy and intel issue Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: booting delay nvidia-smi shows no usage with some memory usage errors : snd_hda_intel :01:00.1: no codecs found! acpi MSFT0101:00: platform device creation failed: -16 ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220) Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_01_00.1" card_name="alsa_card.pci-_01_00.1" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-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: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Fri Dec 30 17:58:15 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3828] Subsystem: Lenovo GK208BM [GeForce 920M] [17aa:3829] InstallationDate: Installed on 2021-06-05 (573 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e360 Qualcomm Atheros Communications Bus 001 Device 003: ID 5986:0670 Acer, Inc Lenovo EasyCamera Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80Q3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=dca8371c-92df-441a-ba2f-acbb9bb611d3 ro quiet splash loglevel=3 vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2018 dmi.bios.release: 1.39 dmi.bios.vendor: LENOVO dmi.bios.version: D3CN39WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo ideapad 500S-14ISK dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 500S-14ISK dmi.ec.firmware.release: 1.26 dmi.modalias: dmi:bvnLENOVO:bvrD3CN39WW:bd06/26/2018:br1.39:efr1.26:svnLENOVO:pn80Q3:pvrLenovoideapad500S-14ISK:rvnLENOVO:rnLenovoideapad500S-14ISK:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad500S-14ISK:skuLENOVO_MT_80Q3_BU_idea_FM_Lenovoideapad500S-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80Q3 dmi.product.sku: LENOVO_MT_80Q3_BU_idea_FM_Lenovo ideapad 500S-14ISK dmi.product.version: Lenovo ideapad 500S-14ISK dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.112+git2208190500.46d1e9~oibaf~j version.libgl1-mesa-dri: libgl1-mesa-dri 22.3~git2208220600.7b81db~oibaf~j 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/linux/+bug/2000784/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 2002314] [NEW] System freezes after locking screen with the nouveau driver
Public bug reported: This is a Hybrid graphics laptop with Ubuntu 22.10 and xserver-xorg- video-nouveau version 1.0.17-2build1. After locking the screen manually or automatically after the specified timeout, the whole laptop freeze or behave extremely slow, either ways a hard reset is a must by holding the power button to bring it back to life. This doesn't happen if the nvidia proprietary driver is used. Right after a fresh boot, you can see the nouveau error in the attached dmesg.txt file. Sometimes while trying to unlock or switching to tty it shows such errors: 4010.649752) rcus INFO: rcu preempt detected stalls on CPUs/tasks: 4010.649766) rcus $0-...1: (1 GPs behind) idle-a58/0/0x0 softirq=30921/30922 fqs=0 (false positive?) 4010.649774) rout $2-... (0 ticks this GP) idle-4dc/0/0x0 softirq-26935/26935 fas-0 (false positive?) 4010.649776) rcut $3-...: (0 ticks this GP) idle-8ce/0/0x0 softirq-27111/27111 fqs=0 (false positive?) 4010.649777) rcus $4-...1: (1 GPs behind) idle-340/0/0x0 softirq-28041/28042 fqs=0 (false positive?) 4010.649779) rcus $6-...11 (0 ticks this GP) idle-86a/0/0x0 softirq-33526/33526 fas=0 (false positive?) 4010.649780) rous $7-... (1 GPs behind) idle=c01/1/0x4000 softirq-29455/29456 fqs=0 3115.864965) watchdog: BUG: soft lockup CPU#4 stuck for 515s! [Timer:5288) 3115.864972) 1915 :00:02.0: [drm] ERROR [CRTC:98:pipe A) filp.done timed out 3115.865030) watchdog: BUG: soft lockup- CPUW7 stuck for 515s! [Socket Thread:4856] 3115.865034) watchdog: BUG: soft lockup CPUW2 stuck for 515s! [snapd:5977) 3115.865046) watchdog: BUG: soft lockup- CPUW3 stuck for 515s! (openvpn:4633] 3115.865080) watchdog: BUG: soft lockup- CPU#6 stuck for $15s! [HebExtensions:5140) And: [2639.153118] NMI watchdog: Watchdog detected hard LOCKUP on cpu 7 [2661.862757] NHI watchdog: Watchdog detected hard LOCKUP on cpu 0 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xserver-xorg-video-nouveau 1:1.0.17-2build1 ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 Uname: Linux 5.19.0-28-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 9 15:59:37 2023 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.19.0-26-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-28-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 (4 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-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau 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-nouveau (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic ubuntu ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/bugs/2002314/+attachment/5640131/+files/dmesg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/2002314 Title: System freezes after locking screen with the nouveau driver Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: Th
[Desktop-packages] [Bug 1998207] Re: netplan network-manager plugin tries to save temporary connections
https://github.com/slyon/NetworkManager/commit/d7730ee3736bdcb7704d96e7bdf4adf46a562a0f ** Changed in: network-manager (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1998207 Title: netplan network-manager plugin tries to save temporary connections Status in netplan: Triaged Status in network-manager package in Ubuntu: Fix Committed Bug description: When creating an OpenVPN connection, a temporal connection called tunN is created. For instance, after activating a connection called vpntest, I have: NAME UUID TYPE DEVICE vpntest 458856e6-8f0f-4dc6-82f2-dd72868252a0 vpn ens3 tun0 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 tun tun0 tun0 is created/removed after activating/deactivating vpntest and should not really be saved, but I see netplan adding it in /etc/netplan. And while doing so the plugin also reports some errors (I see these when stopping the connection): Nov 28 16:16:57 ubuntu NetworkManager[11752]: [1669652217.2920] BUG: the profile cannot be stored in keyfile format without becoming unusable: cannot access file: No such file or directory Nov 28 16:16:57 ubuntu NetworkManager[11752]: ((src/libnm-core-impl/nm-connection.c:342)): assertion '' failed Nov 28 16:16:57 ubuntu NetworkManager[11752]: [1669652217.2920] keyfile: commit: failure to write 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 ((null)) to "/run/NetworkManager/system-connections/tun0-1eb1dbe8-5678-4818-9adf-fb2dc01ed132.nmconnection": keyfile writer produces an invalid connection: cannot access file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1998207/+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 2000739] Re: Window actions (like maximize) no more work in wayland for QEMU using GTK backend once the guest UI is intialized.
Thank you very much Christian for the confirmation (upstream as well) and your further analysis of the issue. Your comment #12 (qemu- system-x86_64 -display gtk) is also reflected in my observation in comment #7. I also appreciate your GDK_BACKEND=x11 ... workaround. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2000739 Title: Window actions (like maximize) no more work in wayland for QEMU using GTK backend once the guest UI is intialized. Status in qemu package in Ubuntu: Confirmed Status in wayland package in Ubuntu: New Bug description: Window actions (like maximize) no more work in wayland for QEMU using GTK backend once the guest UI is intialized. This can be seen by running an installed or even a trial Ubuntu from an ISO like: $ qemu-system-x86_64 \ -boot d \ -cdrom ubuntu-22.04.1-desktop-amd64.iso \ -m 4096M \ -machine type=q35,accel=kvm \ -cpu host \ -smp 2 \ -device qxl-vga The GTK UI of qemu has a feature called "fullscreen" which disables the screen decorations and sets the window to maximize. The decorations go away, but maximize doesn't work. The following details were found so far: - running with GDK_BACKEND=x11 works - using sdl instead of gtk backend works - using the old qemu of Focal, or the newest from upstream git in jammy all fails (no qemu change AFAICS) - host UI widgets (the square at the window top) do not work either - hotkeys (super-up) do not work either It seems that once the guest has enabled the desktop something changes and the maximize/minimize/... actions are no more processed. Not sure were to debug next in regard to the gnome/wayland UI handling of this - any idea? P.S. We can reproduce this in git builds of qemu, so we can debug of modify the code as needed. The code for this is mostly in [1] [1]: https://gitlab.com/qemu-project/qemu/-/blob/master/ui/gtk.c --- original report --- Running QEMU version 4.2.1 on Ubuntu 20.04 via qemu-system-x86_64 \ -boot d \ -cdrom ubuntu-22.04.1-desktop-amd64.iso \ -m 4096M \ -machine type=q35,accel=kvm \ -cpu host \ -smp 2 \ -device qxl-vga and pressing ctrl+alt+f after booting the Ubuntu 22.04 live ISO and adjusting the display resolution to match the native resolution, works as expected, i.e., the VM screen is correctly displayed in fullscreen. However, after running the same command for QEMU version 6.2.0 on Ubuntu 22.04 and pressing ctrl+alt+f after making the resolution adjustment, yields a fullscreen view where the space occupied by the GNOME top bar (top panel with date in center) of the host is not used. The top bar itself is not visible but instead the purple background is shown where the top bar resides. The problem also occurs when replacing '-device qxl-vga' by '-device VGA,vgamem_mb=64'. The problem however does not occur when using '-device virtio-vga'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2000739/+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 2000739] Re: Window actions (like maximize) no more work in wayland for QEMU using GTK backend once the guest UI is intialized.
** Description changed: + Window actions (like maximize) no more work in wayland for QEMU using + GTK backend once the guest UI is intialized. + + This can be seen by running an installed or even a trial Ubuntu from an + ISO like: + + $ qemu-system-x86_64 \ + -boot d \ + -cdrom ubuntu-22.04.1-desktop-amd64.iso \ + -m 4096M \ + -machine type=q35,accel=kvm \ + -cpu host \ + -smp 2 \ + -device qxl-vga + + The GTK UI of qemu has a feature called "fullscreen" which disables the + screen decorations and sets the window to maximize. The decorations go + away, but maximize doesn't work. + + + The following details were found so far: + - running with GDK_BACKEND=x11 works + - using sdl instead of gtk backend works + - using the old qemu of Focal, or the newest from upstream git in jammy all fails (no qemu change AFAICS) + - host UI widgets (the square at the window top) do not work either + - hotkeys (super-up) do not work either + + It seems that once the guest has enabled the desktop something changes + and the maximize/minimize/... actions are no more processed. Not sure + were to debug next in regard to the gnome/wayland UI handling of this - + any idea? + + P.S. We can reproduce this in git builds of qemu, so we can debug of + modify the code as needed. The code for this is mostly in [1] + + [1]: https://gitlab.com/qemu-project/qemu/-/blob/master/ui/gtk.c + + --- original report --- + Running QEMU version 4.2.1 on Ubuntu 20.04 via qemu-system-x86_64 \ - -boot d \ - -cdrom ubuntu-22.04.1-desktop-amd64.iso \ - -m 4096M \ - -machine type=q35,accel=kvm \ - -cpu host \ - -smp 2 \ - -device qxl-vga + -boot d \ + -cdrom ubuntu-22.04.1-desktop-amd64.iso \ + -m 4096M \ + -machine type=q35,accel=kvm \ + -cpu host \ + -smp 2 \ + -device qxl-vga and pressing ctrl+alt+f after booting the Ubuntu 22.04 live ISO and adjusting the display resolution to match the native resolution, works as expected, i.e., the VM screen is correctly displayed in fullscreen. However, after running the same command for QEMU version 6.2.0 on Ubuntu 22.04 and pressing ctrl+alt+f after making the resolution adjustment, yields a fullscreen view where the space occupied by the GNOME top bar (top panel with date in center) of the host is not used. The top bar itself is not visible but instead the purple background is shown where the top bar resides. The problem also occurs when replacing '-device qxl-vga' by '-device VGA,vgamem_mb=64'. The problem however does not occur when using '-device virtio-vga'. ** Also affects: wayland (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2000739 Title: Window actions (like maximize) no more work in wayland for QEMU using GTK backend once the guest UI is intialized. Status in qemu package in Ubuntu: Confirmed Status in wayland package in Ubuntu: New Bug description: Window actions (like maximize) no more work in wayland for QEMU using GTK backend once the guest UI is intialized. This can be seen by running an installed or even a trial Ubuntu from an ISO like: $ qemu-system-x86_64 \ -boot d \ -cdrom ubuntu-22.04.1-desktop-amd64.iso \ -m 4096M \ -machine type=q35,accel=kvm \ -cpu host \ -smp 2 \ -device qxl-vga The GTK UI of qemu has a feature called "fullscreen" which disables the screen decorations and sets the window to maximize. The decorations go away, but maximize doesn't work. The following details were found so far: - running with GDK_BACKEND=x11 works - using sdl instead of gtk backend works - using the old qemu of Focal, or the newest from upstream git in jammy all fails (no qemu change AFAICS) - host UI widgets (the square at the window top) do not work either - hotkeys (super-up) do not work either It seems that once the guest has enabled the desktop something changes and the maximize/minimize/... actions are no more processed. Not sure were to debug next in regard to the gnome/wayland UI handling of this - any idea? P.S. We can reproduce this in git builds of qemu, so we can debug of modify the code as needed. The code for this is mostly in [1] [1]: https://gitlab.com/qemu-project/qemu/-/blob/master/ui/gtk.c --- original report --- Running QEMU version 4.2.1 on Ubuntu 20.04 via qemu-system-x86_64 \ -boot d \ -cdrom ubuntu-22.04.1-desktop-amd64.iso \ -m 4096M \ -machine type=q35,accel=kvm \ -cpu host \ -smp 2 \ -device qxl-vga and pressing ctrl+alt+f after booting the Ubuntu 22.04 live ISO and adjusting the display resolution to match the native resolution, works as expected, i.e., the VM screen is correctly displayed in fullscreen. However, after running the same command for QEMU version 6.2.0 on Ubuntu 22.04 and
[Desktop-packages] [Bug 1994527] Re: ISO8859-02 encoding not respected on saving
** Package changed: textedit.app (Ubuntu) => gedit (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1994527 Title: ISO8859-02 encoding not respected on saving Status in gedit package in Ubuntu: New Bug description: Gedit used to keep the file encoding on saving. With the introduction of the new text editor all my application specific files (which are required to be in iso8859-02) save with scrambled characters which look read well as utf-8. It looks like it's always saving in utf-8 irrespectfully whether auto or manually saving as iso encoding... is selected in the save dialog. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: textedit.app (not installed) ProcVersionSignature: Ubuntu 5.19.0-1009.10-lowlatency 5.19.7 Uname: Linux 5.19.0-1009-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Oct 26 13:44:55 2022 InstallationDate: Installed on 2018-09-15 (1501 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: textedit.app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1994527/+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 1994527] [NEW] ISO8859-02 encoding not respected on saving
You have been subscribed to a public bug: Gedit used to keep the file encoding on saving. With the introduction of the new text editor all my application specific files (which are required to be in iso8859-02) save with scrambled characters which look read well as utf-8. It looks like it's always saving in utf-8 irrespectfully whether auto or manually saving as iso encoding... is selected in the save dialog. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: textedit.app (not installed) ProcVersionSignature: Ubuntu 5.19.0-1009.10-lowlatency 5.19.7 Uname: Linux 5.19.0-1009-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Oct 26 13:44:55 2022 InstallationDate: Installed on 2018-09-15 (1501 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: textedit.app UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic regression-release -- ISO8859-02 encoding not respected on saving https://bugs.launchpad.net/bugs/1994527 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit 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 1978989] Re: FTBFS on armhf since version 102: the final link step segfaults
** Changed in: chromium-browser (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1978989 Title: FTBFS on armhf since version 102: the final link step segfaults Status in chromium-browser package in Ubuntu: Fix Released Bug description: Example build log: [51110/51110] LINK ./chrome FAILED: chrome python3 "../../build/toolchain/gcc_link_wrapper.py" --output="./chrome" -- ../../../../../usr/bin/clang++-10 -Wl,--version-script=../../build/linux/chrome.map -Wl,--build-id=sha1 -fPIC -Wl,-z,noexecstack -Wl,-z,relro -Wl,-z,now --target=arm-linux-gnueabihf -no-canonical-prefixes -Wl,-O2 -Wl,--gc-sections -rdynamic -Wl,-z,defs -Wl,--as-needed -nostdlib++ -pie -Wl,--disable-new-dtags -Wl,-rpath=\$ORIGIN -o "./chrome" -Wl,--start-group @"./chrome.rsp" ./libffmpeg.so -Wl,--end-group -ldl -lpthread -lrt -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lnss3 -lnssutil3 -lsmime3 -lplds4 -lplc4 -lnspr4 -latk-1.0 -latk-bridge-2.0 -lcups -lgio-2.0 -ldbus-1 -latomic -lresolv -lexpat -luuid -ldrm -lxcb -lxkbcommon -lX11 -lXcomposite -lXdamage -lXext -lXfixes -lXrender -lXrandr -lXtst -lgbm -lwayland-client -lpangocairo-1.0 -lpango-1.0 -lcairo -lasound -lXi -lpci -latspi -lxshmfence clang++-10: error: unable to execute command: Segmentation fault (core dumped) clang++-10: error: linker command failed due to signal (use -v to see invocation) ninja: build stopped: subcommand failed. This is observed for the deb package builds targeting bionic (built with clang 10), on armhf only (other architectures build fine). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1978989/+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
Re: [Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
Hey Marc, you can follow
https://code.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/+ref/hwacc-dev,
-beta and -candidate.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
To test the snap with VA-API changes,
1. Install the Chromium snap,
sudo snap install --channel stable/hwacc chromium
2. Start Chromium,
snap run chromium
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples.
4. Enter about:media-internals in the address bar, click the
corresponding box (if the video is playing, it will have the "(kPlay)"
identifier) and note what the page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx,Dav1d}VideoDecoder;
- Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);
- CPU generation (`lscpu`).
Currently it seems to work for all reporters on Xorg.
The version in stable/hwacc is fixed.
Versions in other channels (edge/hwacc, beta/hwacc, candidate/hwacc)
follow the Chromium release cycle (dev, beta and stable channels as in
https://omahaproxy.appspot.com/all.json?os=linux).
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc`
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2001922] Re: Xorg crash
Updated now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2001922 Title: Xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: My Ubuntu 22.04.1 LTS installation crashes, but I was not able to figure out how to reproducibly trigger the crash. The last time it happened was with firefox and zoom running, the display suddenly went black and after a few seconds the X login screen appeared, my session gone. There are files in /var/crash/ -rw-r--r-- 1 root whoopsie0 Jan 5 14:09 _usr_lib_xorg_Xorg.0.upload -rw-r- 1 root whoopsie 12792518 Jan 5 14:09 _usr_lib_xorg_Xorg.0.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:09 _usr_lib_xorg_Xorg.0.uploaded -rw-r--r-- 1 petr whoopsie0 Jan 5 14:13 _usr_bin_xfsettingsd.1000.upload -rw-r- 1 petr whoopsie 516897 Jan 5 14:13 _usr_bin_xfsettingsd.1000.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:13 _usr_bin_xfsettingsd.1000.uploaded -rw-r--r-- 1 petr whoopsie0 Jan 5 14:13 _opt_zoom_zoom.1000.upload -rw-r- 1 petr whoopsie 46590288 Jan 5 14:13 _opt_zoom_zoom.1000.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:13 _opt_zoom_zoom.1000.uploaded and .xsession-errors.old ends with (xfwm4:8122): xfwm4-WARNING **: 14:11:00.736: unmanaged net_wm_state (window 0x649, atom "_NET_WM_STATE_STAYS_ON_TOP") (xfwm4:10847): Gtk-WARNING **: 14:13:01.216: cannot open display: :0.0 Exiting due to channel error. Failed to parse arguments: Cannot open display: :0.0 Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. (xfsettingsd:10849): xfsettingsd-ERROR **: 14:13:01.239: Unable to open display. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. (xfwm4:10854): Gtk-WARNING **: 14:13:01.244: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 (xfwm4:10860): Gtk-WARNING **: 14:13:01.264: cannot open display: :0.0 (xfwm4:10863): Gtk-WARNING **: 14:13:01.280: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 (xfwm4:10865): Gtk-WARNING **: 14:13:01.293: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Is it safe and useful to upload the files from /var/crash/? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Thu Jan 5 14:17:42 2023 DistUpgraded: 2022-12-25 11:03:07,557 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.13.0-35-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-56-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:3f96] InstallationDate: Installed on 2021-11-07 (424 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20YA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-35-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to jammy on 2022-12-25 (11 days ago) dmi.bios.date: 09/23/2021 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: GMCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: ThinkBook 13s G3 ACN dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrGMCN27WW:bd09/23/2021:br1.27:efr1.19:svnLENOVO:pn20YA:pvrThinkBook13sG3ACN:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrThinkBook13sG3ACN:skuLENOVO_MT_20YA_BU_idea_FM_ThinkBook13sG3ACN: dmi.product.family: ThinkBook 13s G3 ACN dmi.product.name: 20YA dmi.product.sku: LENOVO_MT_20YA_BU_idea_FM_ThinkBook 13s G3 ACN dmi.product.version: ThinkBook 13s G3 A
[Desktop-packages] [Bug 2001922] Re: Xorg crash
It just happened again 3aa3f8c4-8f92-11ed-aafb-fa163e55efd0 In the logs I see Jan 09 09:38:34 xlap whoopsie-upload-all[1059]: INFO:root:/var/crash/_usr_bin_xfsettingsd.1000.crash already marked for upload, skipping Jan 09 09:38:34 xlap whoopsie-upload-all[1059]: INFO:root:/var/crash/_opt_zoom_zoom.1000.crash already marked for upload, skipping Jan 09 09:38:34 xlap whoopsie-upload-all[1059]: INFO:root:/var/crash/_usr_lib_xorg_Xorg.0.crash already marked for upload, skipping Jan 09 09:38:34 xlap whoopsie-upload-all[1059]: INFO:root:Waiting for whoopsie to upload reports (timeout: 20 s) Jan 09 09:38:34 xlap whoopsie-upload-all[1059]: INFO:root:All reports uploaded successfully I will try to the apt commands, but that should not be a problem, I upgraded my system very recently. And since then have been getting these crashes... :-/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2001922 Title: Xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: My Ubuntu 22.04.1 LTS installation crashes, but I was not able to figure out how to reproducibly trigger the crash. The last time it happened was with firefox and zoom running, the display suddenly went black and after a few seconds the X login screen appeared, my session gone. There are files in /var/crash/ -rw-r--r-- 1 root whoopsie0 Jan 5 14:09 _usr_lib_xorg_Xorg.0.upload -rw-r- 1 root whoopsie 12792518 Jan 5 14:09 _usr_lib_xorg_Xorg.0.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:09 _usr_lib_xorg_Xorg.0.uploaded -rw-r--r-- 1 petr whoopsie0 Jan 5 14:13 _usr_bin_xfsettingsd.1000.upload -rw-r- 1 petr whoopsie 516897 Jan 5 14:13 _usr_bin_xfsettingsd.1000.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:13 _usr_bin_xfsettingsd.1000.uploaded -rw-r--r-- 1 petr whoopsie0 Jan 5 14:13 _opt_zoom_zoom.1000.upload -rw-r- 1 petr whoopsie 46590288 Jan 5 14:13 _opt_zoom_zoom.1000.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:13 _opt_zoom_zoom.1000.uploaded and .xsession-errors.old ends with (xfwm4:8122): xfwm4-WARNING **: 14:11:00.736: unmanaged net_wm_state (window 0x649, atom "_NET_WM_STATE_STAYS_ON_TOP") (xfwm4:10847): Gtk-WARNING **: 14:13:01.216: cannot open display: :0.0 Exiting due to channel error. Failed to parse arguments: Cannot open display: :0.0 Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. (xfsettingsd:10849): xfsettingsd-ERROR **: 14:13:01.239: Unable to open display. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. (xfwm4:10854): Gtk-WARNING **: 14:13:01.244: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 (xfwm4:10860): Gtk-WARNING **: 14:13:01.264: cannot open display: :0.0 (xfwm4:10863): Gtk-WARNING **: 14:13:01.280: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 (xfwm4:10865): Gtk-WARNING **: 14:13:01.293: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Is it safe and useful to upload the files from /var/crash/? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Thu Jan 5 14:17:42 2023 DistUpgraded: 2022-12-25 11:03:07,557 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.13.0-35-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-56-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:3f96] InstallationDate: Installed on 2021-11-07 (424 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20YA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-35-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to jammy on
[Desktop-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-525 (Ubuntu) Status: New => Confirmed -- 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/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend Status in GNOME Shell: New Status in Mutter: Fix Released Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Bug description: [Impact] The Nvidia driver corrupts and/or forgets its textures when resuming from suspend, by design. Documented here: https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt Although it's so awkward to implement everywhere that realistically compositors will never support it fully. Instead we're waiting for an Nvidia driver fix. *NOTE* that this is actually not a common problem because the system must be using Nvidia as the primary GPU to be affected. So generally only desktop users will encounter the bug, not laptops. And even then, only desktops that use suspend/resume and VT switching may trigger it, if ever. Even in development the bug cannot be reproduced reliably. [Workarounds] * Always log into a Xorg session and if corruption occurs then type: Alt+F2, R, Enter * https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0 [Test Plan] [Where problems could occur] [Original Bug Report] I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd.
[Desktop-packages] [Bug 2002290] [NEW] Poor Arabic rendering in VTE
Public bug reported: VTE has a number of issues when it comes to rendering Arabic letters in the terminal, which could affect a number of languages (Arabic, Urdu, Persian... etc). Bug 1: Any Arabic word in any VTE-based terminal is choppily displayed with spaces between its letters, making readability hard and sometimes not possible. Sometimes the letters are crushed together very closely making reading impossible too. Bug 2: If a non-Arabic text and an Arabic text are displayed together in the same line, then the entire line will be missed up and you won't be able to understand what is being said. Both of these bugs can be seen from the image I attached. I reported both of these bugs together because it's unlikely they can be fixed separately, probably they are related to each other. Problem can be seen in any VTE-based terminal. Here I am using GNOME Terminal 3.44.0 on Ubuntu 22.04, but it can be seen in any Ubuntu version and in any terminal version as well (it has been there since forever). I reported the bug here instead of upstream because that's what they said at the page: https://wiki.gnome.org/Apps/Terminal/ReportingBugs, but this bug is not related to Ubuntu only; it happens on all Linux distributions. Happy to provide any information you need, or any do tests or experiments. ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Affects: vte (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Image demonstrating the issues" https://bugs.launchpad.net/bugs/2002290/+attachment/5640107/+files/2023-01-09_10-18.png ** Also affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/2002290 Title: Poor Arabic rendering in VTE Status in gnome-terminal package in Ubuntu: New Status in vte package in Ubuntu: New Bug description: VTE has a number of issues when it comes to rendering Arabic letters in the terminal, which could affect a number of languages (Arabic, Urdu, Persian... etc). Bug 1: Any Arabic word in any VTE-based terminal is choppily displayed with spaces between its letters, making readability hard and sometimes not possible. Sometimes the letters are crushed together very closely making reading impossible too. Bug 2: If a non-Arabic text and an Arabic text are displayed together in the same line, then the entire line will be missed up and you won't be able to understand what is being said. Both of these bugs can be seen from the image I attached. I reported both of these bugs together because it's unlikely they can be fixed separately, probably they are related to each other. Problem can be seen in any VTE-based terminal. Here I am using GNOME Terminal 3.44.0 on Ubuntu 22.04, but it can be seen in any Ubuntu version and in any terminal version as well (it has been there since forever). I reported the bug here instead of upstream because that's what they said at the page: https://wiki.gnome.org/Apps/Terminal/ReportingBugs, but this bug is not related to Ubuntu only; it happens on all Linux distributions. Happy to provide any information you need, or any do tests or experiments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2002290/+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 1998893] Re: NV reverse prime HDMI has no output
** 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/1998893 Title: NV reverse prime HDMI has no output Status in OEM Priority Project: New Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] The X failed to load glamoregl module on Dell's new platforms, the module is needed by NV dGPU. 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) LoadModule: "glamoregl" 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Loading /usr/lib/xorg/modules/libglamoregl.so 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Module glamoregl: vendor="X.Org Foundation" 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: compiled for 1.21.1.3, module version = 1.0.1 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: ABI class: X.Org ANSI C Emulation, version 0.4 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: MESA: warning: Driver does not support the 0xa78b PCI ID. 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): Refusing to try glamor on llvmpipe 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): glamor initialization failed [Fix] The upstream PR added missing ID for the platforms. https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/16320/ https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/17569/ After creating the test build to include the PR above, ODM verified passed on those platform. [Test case] Install fixed package on the systems, check that display works. [Where things could go wrong] Although one commit drops a couple of pci-id's, they were already dropped from the jammy kernel for lp1990242 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998893/+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 1998893] Re: NV reverse prime HDMI has no output
the pci-id's were dropped from the jammy kernel for lp1990242 ** Description changed: [Impact] The X failed to load glamoregl module on Dell's new platforms, the module is needed by NV dGPU. 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) LoadModule: "glamoregl" 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Loading /usr/lib/xorg/modules/libglamoregl.so 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Module glamoregl: vendor="X.Org Foundation" 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: compiled for 1.21.1.3, module version = 1.0.1 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: ABI class: X.Org ANSI C Emulation, version 0.4 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: MESA: warning: Driver does not support the 0xa78b PCI ID. 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): Refusing to try glamor on llvmpipe 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): glamor initialization failed [Fix] The upstream PR added missing ID for the platforms. https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/16320/ https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/17569/ After creating the test build to include the PR above, ODM verified passed on those platform. [Test case] Install fixed package on the systems, check that display works. [Where things could go wrong] - Although one commit drops a couple of pci-id's, they were synced from the kernel and such id's should not be in the wild. Other than that these just add id's and modify some vendor branding. + Although one commit drops a couple of pci-id's, they were already dropped from the jammy kernel for lp1990242 -- 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/1998893 Title: NV reverse prime HDMI has no output Status in OEM Priority Project: New Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] The X failed to load glamoregl module on Dell's new platforms, the module is needed by NV dGPU. 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) LoadModule: "glamoregl" 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Loading /usr/lib/xorg/modules/libglamoregl.so 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Module glamoregl: vendor="X.Org Foundation" 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: compiled for 1.21.1.3, module version = 1.0.1 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: ABI class: X.Org ANSI C Emulation, version 0.4 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: MESA: warning: Driver does not support the 0xa78b PCI ID. 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): Refusing to try glamor on llvmpipe 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): glamor initialization failed [Fix] The upstream PR added missing ID for the platforms. https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/16320/ https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/17569/ After creating the test build to include the PR above, ODM verified passed on those platform. [Test case] Install fixed package on the systems, check that display works. [Where things could go wrong] Although one commit drops a couple of pci-id's, they were already dropped from the jammy kernel for lp1990242 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998893/+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
