I work all day long in X on my laptop with xterms (xterm -geometry 80x50 -sb -sl
9999 -fn fixed) covering the screen.
In beta4, xterm is extremely unstable. After I start X and my initial terminals
get launched, roughly 50% of the time one or more of the terminals will exit
approximately a minute after first appearing on the screen. They've died while
I'm working in them, but also before I even get a chance to run any commands in
them (so its something inherent to xterm or the X server, and not a program I'm
running in them that's killing them)
No errors appear in /var/log/X* log files about this
This is new in beta 4 -- xterm worked fine in previous betas
This is only seen on my laptop so far (but I've been on the road all week, so
its all I've run beta4 on...). The laptop has a Trident Cyberblade chipset and
is running at 1024x768x24. I'm running gnome w/ metacity as the wm
I've got core dumps enabled now, so if one dumps core next time it happens, I'll
Please do. We don't officially support xterm, however from your bug
report alone it is inconclusive if it is an xterm bug, Xlib bug, glibc,
some other X library, kernel, NPTL, or something else perhaps.
Update with any info you can muster. If you get a core dump, don't attach the
core, but attach a backtrace instead.
FYI. No problems with xterm here so far using the latest rawhide packages from
Thanks for the update Kjartan. With this update, I'm assuming whatever
problem may have been present is no longer present. Nobody else has
reported any xterm stability issues, and I can't reproduce any stability
problems while running our latest tree and using xterm for hours to work
with. I know many other Red Hatters use xterm as their primary terminal
as well, so I'd hear a ruckus if something were amiss. ;o)
Assuming that the problem is fixed now whatever it was and changing
bug state to MODIFIED pending final confirmation from Chris that it is
working for him now. Please set to RAWHIDE if it works, or back to
ASSIGNED if not.
I still had some (though not as many) segfaults with pre-beta5. I've got beta5
installed on my road machine now, so I'll see how it does over the next couple
Cleaning up old bugs -- this one seems fixed now, thanks