[Desktop-packages] [Bug 2059033] Re: Xorg crashes with SIGABRT
Tried kernel parameter i915.enable_dc=0 as suggested by https://wiki.archlinux.org/title/intel_graphics#Crash.2Ffreeze_on_low_power_Intel_CPUs; still crashes -- 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/2059033 Title: Xorg crashes with SIGABRT Status in Mesa: New Status in mesa package in Ubuntu: New Bug description: I am running an Intel Kabylake CPU with Ubuntu 22.04, and i915 graphics driver. I am seeing random Xorg crashes due to SIGABRT, which kicks me back to the login screen. Ubuntu version: 22.04 Kernel version: 5.19.0-50-generic libgl1-mesa-dri version: 23.0.4-0ubuntu1~22.04.1 I am seeing this message in kern.log: i915 :00:02.0: [drm] GPU HANG: ecode 9:1:85db, in Xorg [1617] I have also gotten a core dump; here is the track trace: #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=140131874372224, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #3 0x7f72fec42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x7f72fec287f3 in __GI_abort () at ./stdlib/abort.c:79 #5 0x560c5cc756a0 in OsAbort () at ../../../../os/utils.c:1352 #6 0x560c5cc7aea9 in AbortServer () at ../../../../os/log.c:879 #7 0x560c5cc7be9a in FatalError (f=f@entry=0x560c5ccadc10 "Caught signal %d (%s). Server aborting\n") at ../../../../os/log.c:1017 #8 0x560c5cc72abd in OsSigHandler (unused=, sip=0x713ae7b0, signo=6) at ../../../../os/osinit.c:156 #9 OsSigHandler (signo=6, sip=0x713ae7b0, unused=) at ../../../../os/osinit.c:110 #10 #11 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:44 #12 __pthread_kill_internal (signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:78 #13 __GI___pthread_kill (threadid=140131874372224, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #14 0x7f72fec42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #15 0x7f72fec287f3 in __GI_abort () at ./stdlib/abort.c:79 #16 0x7f72fc49d86d in _iris_batch_flush (batch=0x560c5e916118, file=, line=) at ../src/gallium/drivers/iris/iris_batch.c:1116 #17 0x7f72fd1da6ff in iris_fence_flush (ctx=0x560c5e915be0, out_fence=0x0, flags=) at ../src/gallium/drivers/iris/iris_fence.c:267 #18 0x7f72fc55f127 in st_flush (flags=0, fence=0x0, st=0x560c5e93bbc0) at ../src/mesa/state_tracker/st_cb_flush.c:60 #19 st_glFlush (ctx=, gallium_flush_flags=0) at ../src/mesa/state_tracker/st_cb_flush.c:94 #20 0x7f72fe56b604 in _glamor_block_handler (screen=0x560c5e8655a0, timeout=0x713af054) at ../../../../glamor/glamor.c:285 #21 0x7f72fe5a6157 in msBlockHandler (pScreen=0x560c5e8655a0, timeout=0x713af054) at ../../../../../../../hw/xfree86/drivers/modesetting/driver.c:701 #22 0x560c5cb01095 in BlockHandler (pTimeout=pTimeout@entry=0x713af054) at ../../../../dix/dixutils.c:394 #23 0x560c5cc6c0c9 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:201 #24 0x560c5cafc3e7 in Dispatch () at ../../../../dix/dispatch.c:492 #25 0x560c5cb006b4 in dix_main (argc=11, argv=0x713af268, envp=) at ../../../../dix/main.c:272 #26 0x7f72fec29d90 in __libc_start_call_main (main=main@entry=0x560c5cae95d0 , argc=argc@entry=11, argv=argv@entry=0x713af268) at ../sysdeps/nptl/libc_start_call_main.h:58 #27 0x7f72fec29e40 in __libc_start_main_impl (main=0x560c5cae95d0 , argc=11, argv=0x713af268, init=, fini=, rtld_fini=, stack_end=0x713af258) at ../csu/libc-start.c:392 #28 0x560c5cae9605 in _start () This post describes a similar issue: https://gitlab.freedesktop.org/drm/intel/-/issues/4858 I tried using a workaround from the above link, to set GPU to max frequency using command "intel_gpu_frequency -m", this seemed to reduce the rate of occurrence from once per day to once every 3 days, but this is not a permanent solution. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2059033/+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 2059033] [NEW] Xorg crashes with SIGABRT
Public bug reported: I am running an Intel Kabylake CPU with Ubuntu 22.04, and i915 graphics driver. I am seeing random Xorg crashes due to SIGABRT, which kicks me back to the login screen. Ubuntu version: 22.04 Kernel version: 5.19.0-50-generic libgl1-mesa-dri version: 23.0.4-0ubuntu1~22.04.1 I am seeing this message in kern.log: i915 :00:02.0: [drm] GPU HANG: ecode 9:1:85db, in Xorg [1617] I have also gotten a core dump; here is the track trace: #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=140131874372224, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #3 0x7f72fec42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x7f72fec287f3 in __GI_abort () at ./stdlib/abort.c:79 #5 0x560c5cc756a0 in OsAbort () at ../../../../os/utils.c:1352 #6 0x560c5cc7aea9 in AbortServer () at ../../../../os/log.c:879 #7 0x560c5cc7be9a in FatalError (f=f@entry=0x560c5ccadc10 "Caught signal %d (%s). Server aborting\n") at ../../../../os/log.c:1017 #8 0x560c5cc72abd in OsSigHandler (unused=, sip=0x713ae7b0, signo=6) at ../../../../os/osinit.c:156 #9 OsSigHandler (signo=6, sip=0x713ae7b0, unused=) at ../../../../os/osinit.c:110 #10 #11 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:44 #12 __pthread_kill_internal (signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:78 #13 __GI___pthread_kill (threadid=140131874372224, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #14 0x7f72fec42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #15 0x7f72fec287f3 in __GI_abort () at ./stdlib/abort.c:79 #16 0x7f72fc49d86d in _iris_batch_flush (batch=0x560c5e916118, file=, line=) at ../src/gallium/drivers/iris/iris_batch.c:1116 #17 0x7f72fd1da6ff in iris_fence_flush (ctx=0x560c5e915be0, out_fence=0x0, flags=) at ../src/gallium/drivers/iris/iris_fence.c:267 #18 0x7f72fc55f127 in st_flush (flags=0, fence=0x0, st=0x560c5e93bbc0) at ../src/mesa/state_tracker/st_cb_flush.c:60 #19 st_glFlush (ctx=, gallium_flush_flags=0) at ../src/mesa/state_tracker/st_cb_flush.c:94 #20 0x7f72fe56b604 in _glamor_block_handler (screen=0x560c5e8655a0, timeout=0x713af054) at ../../../../glamor/glamor.c:285 #21 0x7f72fe5a6157 in msBlockHandler (pScreen=0x560c5e8655a0, timeout=0x713af054) at ../../../../../../../hw/xfree86/drivers/modesetting/driver.c:701 #22 0x560c5cb01095 in BlockHandler (pTimeout=pTimeout@entry=0x713af054) at ../../../../dix/dixutils.c:394 #23 0x560c5cc6c0c9 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:201 #24 0x560c5cafc3e7 in Dispatch () at ../../../../dix/dispatch.c:492 #25 0x560c5cb006b4 in dix_main (argc=11, argv=0x713af268, envp=) at ../../../../dix/main.c:272 #26 0x7f72fec29d90 in __libc_start_call_main (main=main@entry=0x560c5cae95d0 , argc=argc@entry=11, argv=argv@entry=0x713af268) at ../sysdeps/nptl/libc_start_call_main.h:58 #27 0x7f72fec29e40 in __libc_start_main_impl (main=0x560c5cae95d0 , argc=11, argv=0x713af268, init=, fini=, rtld_fini=, stack_end=0x713af258) at ../csu/libc-start.c:392 #28 0x560c5cae9605 in _start () This post describes a similar issue: https://gitlab.freedesktop.org/drm/intel/-/issues/4858 I tried using a workaround from the above link, to set GPU to max frequency using command "intel_gpu_frequency -m", this seemed to reduce the rate of occurrence from once per day to once every 3 days, but this is not a permanent solution. ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- 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/2059033 Title: Xorg crashes with SIGABRT Status in mesa package in Ubuntu: New Bug description: I am running an Intel Kabylake CPU with Ubuntu 22.04, and i915 graphics driver. I am seeing random Xorg crashes due to SIGABRT, which kicks me back to the login screen. Ubuntu version: 22.04 Kernel version: 5.19.0-50-generic libgl1-mesa-dri version: 23.0.4-0ubuntu1~22.04.1 I am seeing this message in kern.log: i915 :00:02.0: [drm] GPU HANG: ecode 9:1:85db, in Xorg [1617] I have also gotten a core dump; here is the track trace: #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=140131874372224, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #3 0x7f72fec42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x7f72fec287f3 in __GI_abort () at
[Desktop-packages] [Bug 1868160] [NEW] vino does not receive Shift+Function key events correctly
Public bug reported: If I connect to vino (using UltraVNC client from Windows), any Shift+Function key press is received as the plain function key (no shift). This breaks my application which uses separate actions for F12 vs Shift+F12. I experimented with xev, and it prints a KeyRelease event for the shift key before the KeyPress for the function key. All function keys F1 through F12 are affected. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: vino 3.8.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-137.163~14.04.1-generic 4.4.144 Uname: Linux 4.4.0-137-generic x86_64 NonfreeKernelModules: mtxservmanager mtxmemmanager ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 19 14:45:58 2020 ExecutablePath: /usr/lib/vino/vino-server InstallationDate: Installed on 2016-01-11 (1528 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/tcsh SourcePackage: vino UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: vino (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1868160 Title: vino does not receive Shift+Function key events correctly Status in vino package in Ubuntu: New Bug description: If I connect to vino (using UltraVNC client from Windows), any Shift+Function key press is received as the plain function key (no shift). This breaks my application which uses separate actions for F12 vs Shift+F12. I experimented with xev, and it prints a KeyRelease event for the shift key before the KeyPress for the function key. All function keys F1 through F12 are affected. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: vino 3.8.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-137.163~14.04.1-generic 4.4.144 Uname: Linux 4.4.0-137-generic x86_64 NonfreeKernelModules: mtxservmanager mtxmemmanager ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 19 14:45:58 2020 ExecutablePath: /usr/lib/vino/vino-server InstallationDate: Installed on 2016-01-11 (1528 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/tcsh SourcePackage: vino UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1868160/+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