#2394 closed defect (fixed)
Terminal issues in F14
| Reported by: | erikos | Owned by: | erikos |
|---|---|---|---|
| Priority: | Unspecified by Maintainer | Milestone: | |
| Component: | Terminal | Version: | Unspecified |
| Severity: | Unspecified | Keywords: | olpc-0.90 |
| Cc: | Distribution/OS: | Unspecified | |
| Bug Status: | Assigned |
Description
In latest soas builds I can not scroll when using less: "Warning Terminal is not fully functional".
On the XO builds I could not edit files with Vi neither, which works in Soas ok.
There was a new version of VTE in updates-testing (0.26.0-1) but that one did not fix that issue (tested in soas).
Change History (10)
comment:1 Changed 14 years ago by sascha_silbe
comment:2 Changed 14 years ago by erikos
Sascha, thanks for your quick feedback.
TERM is set to dumb (setting it to xterm fixes it). Looks like behavior in vte has changed.
https://bugs.launchpad.net/terminator/+bug/621606
I have not found the exact message for the change - but I guess like others we just have to hardcode it.
comment:3 Changed 14 years ago by erikos
- Keywords olpc-0.90 added
comment:4 Changed 14 years ago by erikos
Filed upstream as: https://bugzilla.gnome.org/show_bug.cgi?id=631589
comment:5 Changed 14 years ago by erikos
- Bug Status changed from Unconfirmed to Assigned
- Owner changed from sayamindu to erikos
- Status changed from new to assigned
comment:6 Changed 14 years ago by erikos
- Milestone changed from Unspecified by Release Team to 0.90
We have an upstream solution, thanks to Tomeu: https://bugzilla.gnome.org/show_bug.cgi?id=631589#c13 Yipee!
comment:7 Changed 14 years ago by tomeu
What should we do with this ticket? I'd probably close it as notsugar and open tickets in our downstreams so they patch their packages or ping the vte maintainers to make a new stable release.
comment:8 Changed 14 years ago by tomeu
Btw, the patch is here:
http://git.gnome.org/browse/vte/commit/?id=e5fd6c3cda63cad2e3d7af8728a168b90eb009dc
comment:9 Changed 13 years ago by erikos
- Resolution set to fixed
- Status changed from assigned to closed
Has been fixed in vte 2.26.1, verified in recent builds.
Sounds like $TERM isn't set properly or the terminfo database is broken. What does
say?
If it's non-empty, the tack tool might be useful for debugging (I've never tried it before, though).