Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 287747 - x11-apps/luit-1.0.4 causes xterm -lc not to close
Summary: x11-apps/luit-1.0.4 causes xterm -lc not to close
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Thomas Dickey
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-05 12:05 UTC by Alexander Huemer
Modified: 2011-07-09 12:25 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info (emerge_info,4.17 KB, text/plain)
2009-10-05 12:17 UTC, Alexander Huemer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Huemer 2009-10-05 12:05:49 UTC
please see [1].
downgrading to 1.0.3 reverts the problem.
no solution so far.

[1]: http://forums.gentoo.org/viewtopic-t-795560-highlight-.html

Reproducible: Always

Steps to Reproduce:
Comment 1 Alexander Huemer 2009-10-05 12:17:33 UTC
Created attachment 206074 [details]
emerge --info

emerge --info
Comment 2 Justin Lecher (RETIRED) gentoo-dev 2009-10-09 09:08:22 UTC
which version of xterm are you using? Please explain your problem here again.
Comment 3 Alexander Huemer 2009-10-09 09:41:13 UTC
from f.g.o.:
i just noticed that my xterms do not close any more when i hit "exit" or "^D".
the option that causes this is "-lc". without that (or with "+lc") it works fine.
what happens is that x11-apps/luit is called. downgrading luit from 1.0.4 to 1.0.3 solves the problem.

i am currently running xterm-249, but tried 243 too, same result.
Comment 4 Thomas Dickey 2009-10-09 20:31:31 UTC
That's a known defect which I fixed in my alternate version of luit:

2009/8/16 - 
reset connection to blocking mode on exit. 
modify poll-flavor of waitForInput to also check if the connection has hung up.

(It's a defect introduced by xorg changes in April 2009).
Comment 5 Thomas Dickey 2009-10-09 20:32:07 UTC
fwiw - the changelog is here:

http://invisible-island.net/luit/luit.log.html
Comment 6 Alexander Huemer 2009-10-09 21:33:16 UTC
ok. but what does that mean ?
when will this fix appear in the portage tree ?
Comment 7 Thomas Dickey 2009-10-09 21:44:56 UTC
I don't know - perhaps xorg will fix it sometime.
Comment 9 Rémi Cardona (RETIRED) gentoo-dev 2009-10-11 22:36:28 UTC
Thomas,

Could you send the patch to the xorg-devel mailing list? Let's try to merge back your fork and the xorg one, seems like a good central place for collaboration.

Thanks
Comment 10 Thomas Dickey 2009-10-12 00:22:26 UTC
The proper place for discussing that would be on the xorg list.
I pointed to that thread, to give some context.
Comment 11 Rémi Cardona (RETIRED) gentoo-dev 2009-10-12 00:32:48 UTC
Could anyone who actually uses luit file a bug upstream [1] so that they actually get notified of the bug?

@Thomas, I don't know what the discussion should be about, everyone seems to be using the Xorg fork of luit. So it's rather whether you want to keep maintaining your own version or not. I have commit access to fd.o, so if you provide patches to the mailing list, I'll gladly commit them once they are ACKed.

Thanks

[1] https://bugs.freedesktop.org
Comment 12 Samuli Suominen (RETIRED) gentoo-dev 2010-11-05 20:39:42 UTC
after a year:  ping :)
Comment 13 Samuli Suominen (RETIRED) gentoo-dev 2011-07-09 12:25:58 UTC
"Aside from that (and some cosmetic changes to C source, as well as providing a different configure script), and omitting this change-log, the xorg 1.1.0 is the same as the 2010/6/1 version."

And I can't reproduce this bug anymore with xterm-270 and luit-1.1.0 so assuming this one is fixed now.