Red Hat Bugzilla – Bug 435439
xterm-232-1.fc8.rpm update causes segfault in xterm
Last modified: 2008-03-13 06:14:45 EDT
Description of problem:
Installing the latest update for xterm (232-1.fc8) causes xterm to seg fault.
Version-Release number of selected component (if applicable):
Every time it's installed on both mine and my colleague's machines, either as
root or a normal user.
Steps to Reproduce:
1. Update xterm to 232-1.fc8:
# yum update xterm
2. Run xterm:
xterm runs OK
Backing out to the previous version (229-2.fc8) fixes the problem:
# yum remove xterm
# yum install xterm-229-2.fc8
(xterm runs OK)
$ uname -a
Linux hagrid 22.214.171.124-137.fc8 #1 SMP Sun Feb 10 17:48:34 EST 2008 i686 i686
Created attachment 296327 [details]
strace output for xterm-232-1.fc8
Can you please try xterm-233-1.fc9 from rawhide?
The rawhide RPM works a treat. Thanks.
I forgot to mention that we were forwarding X over SSH to cygwin X. When I
found a colleague with a local gnome desktop, xterm worked OK displaying to his
desktop so maybe it's something to do with that.
Thanks for the pointer to the rawhide RPM.
Ok, I'll prepare updates for F7 and F8.
xterm-233-1.fc7 has been submitted as an update for Fedora 7
xterm-233-1.fc8 has been submitted as an update for Fedora 8
Cool. Thanks Miroslav.
xterm-233-1.fc7 has been pushed to the Fedora 7 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update xterm'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F7/FEDORA-2008-2130
xterm-234-1.fc8 has been submitted as an update for Fedora 8
xterm-234-1.fc7 has been submitted as an update for Fedora 7
*** Bug 436897 has been marked as a duplicate of this bug. ***
xterm-234-1.fc7 has been pushed to the Fedora 7 stable repository. If problems still persist, please make note of it in this bug report.
xterm-234-1.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.
Works fine. Thanks for fixing it.