Bug 492219 - Recent updates have broken xterm
Summary: Recent updates have broken xterm
Keywords:
Status: CLOSED DUPLICATE of bug 491813
Alias: None
Product: Fedora
Classification: Fedora
Component: xterm
Version: 10
Hardware: All
OS: Linux
low
urgent
Target Milestone: ---
Assignee: Miroslav Lichvar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-25 22:26 UTC by Michael Forrest
Modified: 2009-03-26 08:59 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-03-26 08:59:06 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Michael Forrest 2009-03-25 22:26:41 UTC
Description of problem:
xterm 242-2 and 242-3 (from rawhide) both hang indefinitely before displaying main window.

Version-Release number of selected component (if applicable):
xterm-242-2.fc10.i586
xterm-242-3.fc11.i586

How reproducible:


Steps to Reproduce:
1. Update to libX11-1.1.5-1.fc10
2. Try to run xterm or uxterm

  
Actual results:
Both xterm and uxterm indefinitely before displaying main window

Expected results:
The main vt100 widget displays as per normal.


Additional info:
This obviously could be a bug in libX11, but gnome-terminal and other gtk apps all appear to fo be functioning normally.

"strace" shows xterm process is stuck in a select:

read(3, "\1\0\234\0\0\0\0\0f\1\0\0\0\0\0\0\20\0\0\0\0\0\0\0\2101\352\10\0\0\0\0"..., 4096) = 32
read(3, 0x85279dc, 4096)                = -1 EAGAIN (Resource temporarily unavailable)
select(4, [3], [3], NULL, NULL)         = 1 (out [3])
writev(3, [{"\30\1\6\0.\0\0\7i\1\0\0f\1\0\0f\1\0\0\0\0\0\0"..., 24}], 1) = 24
select(4, [3], [], NULL, NULL

Comment 1 Michael Forrest 2009-03-25 22:50:16 UTC
The hang in the select occurs without the main window displaying at all.

Comment 2 Jindrich Novy 2009-03-26 08:59:06 UTC
Closing as duplicate of the libX11-1.1.5-1.fc10 failure tracker.

Just out of curiosity, is it fixed by upgrade to libX11-1.2-3.fc11 in rawhide?

*** This bug has been marked as a duplicate of bug 491813 ***


Note You need to log in before you can comment on or make changes to this bug.