The audible bell does not work in x11-terms/xterm-242, but works in xterm-243. This seems to affect users of other distributions too: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=520405 (#520405 - xterm: bell no longer sounds - Debian Bug report logs) Since xterm-243 entered the tree in 2009-05-05, has not been changed since then, and a Gentoo bugzilla search[0] uncover no regressions, I think it should be stabilized soon. I myself am on stable x86, and have been using xterm-243 for a couple of days. My usage, consisting of bash, screen and elinks shows no bug in this version (and I get an audible bell, which was the reason for adding ~x11-terms/xterm-243 to package.keywords). Also applications such as alsamixer and the kernel menuconfig work well. [0] http://bugs.gentoo.org/buglist.cgi?quicksearch=x11-terms%2fxterm Reproducible: Always
Thanks for reporting your results from using xterm-243 -- assigning stabilization request to maintainers.
I have not noticed any problems with XTerm 243 on amd64 too.
We'll do that one along with xorg-server 1.6
#243 has a display bug. #248 is preferable no regressions found so far, though https://bugzilla.redhat.com/show_bug.cgi?id=524503 is an older bug aggravated by the #244 changes. I'm working on #249, which will be bug-fixes only.
Hi Thomas, Please let me know which xterm you would like us to stabilize along with xorg 1.6 Thanks
hmm - the Redhat bug report is for a fatal error which would occur in a relatively rare case. The display bug is here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522141 and the fix was more than a couple of lines (so it's unsuitable for a backport). It's cosmetic, but sooner reported than the Redhat bug, and #243 is from March - getting old. But no one in this group seems to have tested anything more recent. So I guess you should finish this one (with #243) and open a new issue to stabilize with #249 (which will be "soon").
#243 is on the list for bug 282290, so closing as dupe Thomas, I've added #248 to Portage today so we are up to date again *** This bug has been marked as a duplicate of bug 282290 ***