You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2018/02/06 19:15:00 UTC
[jira] [Commented] (KARAF-5526) [ERROR] Failed to construct
terminal; falling back to unsupported
[ https://issues.apache.org/jira/browse/KARAF-5526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16354401#comment-16354401 ]
Guillaume Nodet commented on KARAF-5526:
----------------------------------------
See https://github.com/jline/jline2/issues/281, this has been fixed in jline 2.14.4.
> [ERROR] Failed to construct terminal; falling back to unsupported
> -----------------------------------------------------------------
>
> Key: KARAF-5526
> URL: https://issues.apache.org/jira/browse/KARAF-5526
> Project: Karaf
> Issue Type: Bug
> Affects Versions: 4.0.9
> Environment: % mvn -version
> Apache Maven 3.5.0 (Red Hat 3.5.0-6)
> Maven home: /usr/share/maven
> Java version: 1.8.0_151, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.151-1.b12.fc27.x86_64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.13.16-302.fc27.x86_64", arch: "amd64", family: "unix"
> % java -version
> openjdk version "1.8.0_151"
> OpenJDK Runtime Environment (build 1.8.0_151-b12)
> OpenJDK 64-Bit Server VM (build 25.151-b12, mixed mode)
> % cat /etc/redhat-release
> Fedora release 27 (Twenty Seven)
> % env|grep TERM
> COLORTERM=truecolor
> TERM=screen-256color
> Reporter: Lars Kiesow
> Priority: Major
>
> Upgrading to Fedora 27 which comes with a newer Java and Maven version, I found that the Karaf shell was not working properly anymore. For once, I got a stack trace right after starting the application and then the shell history does not work and Ctrl+C which previously would stop commands like `log:tail`, now terminates the application.
> A workaround I could find in this answer on StackOverflow:
> https://stackoverflow.com/a/44361749/2352895
> …setting the `TERM` variable to `xterm-color` did help. Though previously, it worked just fine with the set `screen-256color`
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)