[Ubuntu-x-swat] [Bug 2042975] [NEW] Kisak-mesa fresh mpv crash
Public bug reported: PPA affected is https://launchpad.net/~kisak/+archive/ubuntu/kisak-mesa I'll comment up top there's a patch to fix this issue, and a viable workaround. I decided to file a bug report primarily so if anyone else comes across this issue they can see the workaround. It's highly likely Kisak doesn't have to do anything about this, that 23.2.2 will ship with this fixed. Running Mesa 23.2.1, mpv seg faults. "Videos" video player doesn't crash but doesn't play video either. As a workaround I went to .config/mpv/mpv.conf and put in "vo=xv". (I'm not sure what the equivalent is if you're running Wayland.) I found a bug report of this issue: https://gitlab.freedesktop.org/mesa/mesa/-/issues/9922 It seems there were some changes made to AMD radeon driver, and both radeon and Intel driver now have a few functions with the same names! The link above has a backported patch from 24.0 development branch. I assume 23.2.2 will most likely have a fix incorporated. Thanks for the great work Kisak!! ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- 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/2042975 Title: Kisak-mesa fresh mpv crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2042975/+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 1643239] Re: Xorg crash on compiz login, with Intel 945
No problem! I don't still have the D620 (or run 16.04 on anything...). Side note, Intel GPU drivers sure have come along way since then! Back in the day, the Intel driver OpenGL was somewhat questionable, it worked or it didn't with various games and 3D-using stuff see this very bug report. Now I can generally run anything even under wine and proton up to the limits of the hardware. I.e. you won't be running dx12 games on a 10 year old Intel GPU but it'll do dx11...whether it'll do it fast enough is another matter but better drivers can't do anything for the GPU being too slow. Well apparently they can to some extent -- the cherry on the cake, my friend's (almost as old as the D620) Sandy Bridge system got about a 40-50% FPS improvement with some Mesa/Intel stack changes in 2020 or so (and has kept that extra speed in 22.04) and I saw 30%+ speedups on a few other Intel GPU systems I had around that time. (This was not a matter of Intel GPU drivers being slow before; on the contrary, running some games on Intel GPU head-to-head between Windows and Linux with wine or proton shows higher framerates in Linux virtually across the board.) Great job Xorg, Mesa, and Intel driver devs! --Henry -- 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/1643239 Title: Xorg crash on compiz login, with Intel 945 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1643239/+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 1952970] Re: mesa GLX change leads to wine showing GLXBadFBConfig
Suggested patch. For now, I've been running mesa 20.0.x on the affected system from (21.0.x is in ubuntu-updates, 20.0.x in base ubuntu repo, so I downgraded to that and thank goodness for apt-mark hold...) But I can update it straight away to test any update that comes out. Thanks! --Henry ** Patch added: "wine-fix-updated.diff" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1952970/+attachment/5544778/+files/wine-fix-updated.diff -- 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/1952970 Title: mesa GLX change leads to wine showing GLXBadFBConfig To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1952970/+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 1952970] [NEW] mesa GLX change leads to wine showing GLXBadFBConfig
Public bug reported: A mesa GLX change (somewhere between the 20.0.4 and 21.0.3) causes both wine and Proton (on an older system that does not have Vulkan.. SandyBridge, OpenGL 3.3..) to exit with GLXBadFBConf when it tries to fire up OpenGL. Wine, for Direct3D support it tries to fire up (in order) Vulkan then progressively older OpenGL versions fro 4.5 down to 2.1 or maybe even 1.4 (of course the older the OpenGL the lower supported Direct3D version). Wine does not like getting an error back with the same transaction serial number as it sent out. See https://gitlab.freedesktop.org/mesa/mesa/-/issues/3969 Mesa issue 3969, The patch there throws in an "XNoOp()" to increment the transaction serial number. But the patch there caused issues in other apps, per https://gitlab.freedesktop.org/mesa/mesa/-/issues/4763 Mes issue 4763, They found XNoOp() increments the serial number, but xcb keeps a "shadow copy" of the serial number which is not incremented, causing problems. XFlush() increments the serial number, keeps xcb in sync and happy, with no real side effects (running XFlush() frequently would slow things down, but this code only runs when a GLX context is being created anyway which just doesn't happen all that frequently.) Please find attached a patch implementing the updated patch suggested in issue 4763. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libglx-mesa0 21.0.3-0ubuntu0.3~20.04.5 ProcVersionSignature: Ubuntu 5.13.0-22.22~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Wed Dec 1 18:59:43 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Dell Picasso [1028:0a12] InstallationDate: Installed on 2020-05-05 (575 days ago) InstallationMedia: MachineType: Dell Inc. Inspiron 3505 ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=57669cb0-fd65-4eb0-9898-ed10f33d44d0 ro quiet splash nvme_core.io_timeout=300 nosmt vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2021 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.7 dmi.board.asset.tag: not specified dmi.board.name: 0RV9WY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.4.7 dmi.modalias: dmi:bvnDellInc.:bvr1.4.7:bd05/31/2021:br5.3:svnDellInc.:pnInspiron3505:pvr1.4.7:rvnDellInc.:rn0RV9WY:rvrA00:cvnDellInc.:ct10:cvr1.4.7:sku0A12: dmi.product.family: Inspiron dmi.product.name: Inspiron 3505 dmi.product.sku: 0A12 dmi.product.version: 1.4.7 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: mesa (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 mesa in Ubuntu. https://bugs.launchpad.net/bugs/1952970 Title: mesa GLX change leads to wine showing GLXBadFBConfig To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1952970/+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 1643239] Re: Xorg crash on compiz login, with Intel 945
I haven't verified this yet, but it looks from the XOrg log like these systems are booting into dual head (with the SVideo out on head 2), 2128x800 total. That width over 2048 is probably what's causing the problem. I did "lose the mouse" on one, and suspected a "phantom head." I went to System Settings -> Display, it didn't show a second head but the whole desktop flickered (I suspect it turned the superfluos head off then.) I suspect it stored this in .config/monitors.xml, I'll check tomorrow if it'll now log into compiz, and if it's got some hotkey that may toggle that on and off. I guess if that works out, then there's no real X bug; perhaps compiz should fall back to llvmpipe if it sees an an otherwise-working opengl implementation, but asks for a large texture and has it fail. Kudos to the compiz, Xorg, and llvmpipe developers btw... the CPU and RAM use were already decent in 14.04 but much lower now, and llvmpipe's actually reasonably fast too. -- 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/1643239 Title: Xorg crash on compiz login, with Intel 945 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1643239/+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 1643239] [NEW] Xorg crash on compiz login, with Intel 945
Public bug reported: I went to install Ubuntu (via systemback) onto some Dell D620s, and found "Gnome Flashback (compiz)" crashes back to login prompt, while "Gnome Flashback (Metacity)" does not. The attached logs reflect booting up, (attempting to) log in with Flashback (compiz) then logging in with Flashback (Metacity) to file a bug report. This may be chipset-specific, as I have several other rather antiquated systems: Intel 865-based (Compaq DC5000): Works. (Using LLVMPipe -- this chip is missing a few OpenGL features compiz requires.) Intel 915-based (Dell Inspiron 2200): Works. Intel 945-based (Dell Latitude D620): Crashes to login prompt (this is the machine in this bug report.) Intel 965-based (Dell Latitude 755?): Works. Intel G35-based (slightly newer Dell Latitude 755): Works. I can rule out software differences; since I knew Compiz worked on a 915, I assumed I'd screwed up my systemback LiveUSB somehow, and test- ran it on the D620, 2200, and one of the 755s, and it worked on the 2200 and 755. Left up to me, I'd categorize this as severity "low", I'm just setting these to Flashback Metacity and then stability seems fine. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 BootLog: SB@: clean, 208182/2244608 files, 1302234/8973568 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity Date: Sat Nov 19 10:12:40 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [1028:01c2] Subsystem: Dell Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [1028:01c2] InstallationDate: Installed on 2016-04-29 (203 days ago) InstallationMedia: MachineType: Dell Inc. Latitude D620 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=702f73f8-ca72-4102-9c59-48f182329bfa ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/16/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0TD761 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/16/2008:svnDellInc.:pnLatitudeD620:pvr:rvnDellInc.:rn0TD761:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D620 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat Nov 19 10:12:01 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 0 vendor LPL xserver.version: 2:1.18.4-0ubuntu0.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug crash i386 ubuntu xenial -- 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/1643239 Title: Xorg crash on compiz login, with Intel 945 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1643239/+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 968218] Re: ssh x11 forwarding precise to oneiric causes glibc malloc(): memory corruption
Note, I see this bug between my Natty too... between my Natty netbook and my Gentoo desktop (once the X server upgraded to 1.12.99, and still with 1.13.0. Not sure why, because this computer just has a mouse and keyboard, no touch screen or touchpad to provide exciting new XInput events.) Installing libxi6_1.4.3-3ubuntu1.1_i386.deb from Oneiric-updates works fine (no dependency problems and fixes the bug.) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libxi in Ubuntu. https://bugs.launchpad.net/bugs/968218 Title: ssh x11 forwarding precise to oneiric causes glibc malloc(): memory corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxi/+bug/968218/+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 566324] Re: Xorg crash
Me too, also with a GX260. dmesg shows streams of errors such as: [97544.908019] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung [97544.908032] render error detected, EIR: 0x [97544.908056] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -5 (awaiting 6540 at 6213) when this happens. I think this is why the Failed to submit batchbuffer: Input/output error occurs within XOrg, the GPU indeed is hung. I have ssh on this box and can verify that other than XOrg going into a restart loop and burning a few CPU cycles (until I run sudo /etc/init.d/gdm stop) everything else is unaffected. If anyone has a patch to try, I have a head on this box but mostly treat it as headless, so I'm in a good position to try out patches. -- Xorg crash https://bugs.launchpad.net/bugs/566324 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel 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
