Bug 161894
Summary: | xterm SIGSEGV after resize | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Karel Zak <kzak> |
Component: | xterm | Assignee: | Jason Vas Dias <jvdias> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | dickey |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-10-13 00:57:25 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 150221 |
Description
Karel Zak
2005-06-28 09:00:06 UTC
see http://invisible-island.net/xterm/xterm.log.html#xterm_201 add a limit check for scrolling margins in a one-line screen, overlooked in fixes for patch #198 (Debian #297430). I'll be updating xterm in Fedora devel to the latest version in the near future, which will fix this bug in rawhide. We'll also be releasing an update for FC3/FC4 soon of xterm-200. If someone has an isolated unified diff that fixes this issue available somewhere, I'd be happy to include it in the upcoming FC3/FC4 updates as well. I'll update the report again once the new xterm hits rawhide. Thanks guys. I don't recall this as a large change, will check as I review this (perhaps tomorrow), to see. This is fixed with xterm-2.0.5-1 in rawhide-20051013 . Once this version has been tested in rawhide for a week or so, I'll produce FC-4 / FC-3 versions. From User-Agent: XML-RPC xterm-205-1.FC4 has been pushed for FC4, which should resolve this issue. If these problems are still present in this version, then please make note of it in this bug report. From User-Agent: XML-RPC xterm-205-1.FC4 has been pushed for FC4, which should resolve this issue. If these problems are still present in this version, then please make note of it in this bug report. |