[Ubuntu-x-swat] [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 Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2002349 Title: Stuck at 640x480. No Nvidia driver anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2002349/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [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 Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2002349 Title: Stuck at 640x480. No Nvidia driver anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2002349/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [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 Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2002321 Title: computer is too slow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2002321/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [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 Ubuntu-X, 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2000739/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [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 Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2001922 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2001922/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [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 Ubuntu-X, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1846398/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [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 Ubuntu-X, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2002349/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [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 Ubuntu-X, which is subscribed to xorg in Ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1980663] Re: [MIR] false-positives, do not promote
packages in main should not pull in packages in universe by default. Either libnet-dns-perl needs to list libnet-libidn-perl as the first alternative, or libnet-libidn2-perl needs to be promoted. ** Changed in: libnet-dns-perl (Ubuntu) Status: New => Triaged ** Changed in: libnet-dns-perl (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xterm in Ubuntu. https://bugs.launchpad.net/bugs/1980663 Title: [MIR] false-positives, do not promote To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/esmtp/+bug/1980663/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [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 Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1803885 Title: Lenovo R60 screen corrupt immediately after install 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/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [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 Ubuntu-X, 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) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1010683/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [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 Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1721960 Title: Flickering on AMD R9 270X 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/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [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 Ubuntu-X, 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) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923153/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [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 Ubuntu-X, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1846398/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [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 Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2001922 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2001922/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [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 Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1998893 Title: NV reverse prime HDMI has no output To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998893/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [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 Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1998893 Title: NV reverse prime HDMI has no output To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998893/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [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 Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2002321 Title: computer is too slow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2002321/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [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 Ubuntu-X, 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
[Ubuntu-x-swat] [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
[Ubuntu-x-swat] [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 Ubuntu-X, 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 To manage notifications about this bug go to:
[Ubuntu-x-swat] [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 Ubuntu-X, 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2000739/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [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 Ubuntu-X, 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2000739/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2001922] Re: Xorg crash
Updated now. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2001922 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2001922/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [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 Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2001922 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2001922/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [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 Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1998893 Title: NV reverse prime HDMI has no output To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998893/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [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 Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1998893 Title: NV reverse prime HDMI has no output To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998893/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
