FS#28844 - Upgrade of libxt breaks xkill
Attached to Project:
Arch Linux
Opened by Norbert Zeh (nzeh) - Saturday, 10 March 2012, 03:07 GMT
Last edited by Andreas Radke (AndyRTR) - Monday, 12 March 2012, 20:35 GMT
Opened by Norbert Zeh (nzeh) - Saturday, 10 March 2012, 03:07 GMT
Last edited by Andreas Radke (AndyRTR) - Monday, 12 March 2012, 20:35 GMT
|
Details
Description: I'm running xdm as my display manager and
display an xclock as part of my login screen. The Xstartup
script kills this xclock using xkill. After upgrading libxt
from version 1.1.1-2 to version 1.1.2-1, xkill still kills
the xclock window upon login, but the process sticks around,
spinning one of my cores at 100%. On another machine, I'm
also showing an xmessage window as part of my login screen.
In this case, both the xclock and xmessage windows get
killed, but the processes remain and spin the CPU at maximum
load. Downgrading to version 1.1.1-2 fixes the problem. So
there is some regression in the transition from 1.1.1-2 to
1.1.2-1.
Additional info: * package version(s) libxt 1.1.2-1 * config and/or log files etc. Steps to reproduce: I guess the easiest is to install the xdm-archlinux theme and configure xdm to use it. Then login as an arbitrary user. |
This task depends upon
https://bugs.freedesktop.org/show_bug.cgi?id=44589
Can you try recompiling libxt with the commit reverted?