Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

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
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andreas Radke (AndyRTR)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

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

Closed by  Andreas Radke (AndyRTR)
Monday, 12 March 2012, 20:35 GMT
Reason for closing:  Fixed
Comment by Andreas Radke (AndyRTR) - Saturday, 10 March 2012, 09:44 GMT
Does a rebuild of xorg-xkill fix it? If not please report it upstream.
Comment by Trevor Bramble (TrevorBramble) - Sunday, 11 March 2012, 03:48 GMT
Is this applicable?

https://bugs.freedesktop.org/show_bug.cgi?id=44589

Comment by Andreas Radke (AndyRTR) - Sunday, 11 March 2012, 08:59 GMT
Hm. Maybe our LDFLAGS break something here. Can you try to rebuild it with LDFLAGS unset or something similar?
Comment by Norbert Zeh (nzeh) - Monday, 12 March 2012, 04:40 GMT
Recompiled xkill and libxt with the LDFLAGS unset. This didn't change the behaviour. So I guess I'll go and report it upstream.
Comment by Christian Hesse (eworm) - Monday, 12 March 2012, 08:51 GMT
Possibly this is related: https://bugs.archlinux.org/task/28875

Can you try recompiling libxt with the commit reverted?
Comment by Norbert Zeh (nzeh) - Monday, 12 March 2012, 15:44 GMT
Recompiled with the commit reverted. Well, actually, I didn't want to create a PKGBUILD that pulls from git and reverts the patch, so I simply manually reverted it. No more CPU spinning by xclock, xmessage or xscreensaver. So I would think that patch is the culprit.
Comment by Andreas Radke (AndyRTR) - Monday, 12 March 2012, 20:17 GMT
Please test, if libxt 1.1.2-2 solves it for you.
Comment by Norbert Zeh (nzeh) - Monday, 12 March 2012, 20:27 GMT
Yup. 1.1.2-2 solves the problem. Kudos, guys - you rock.

Loading...