Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#53725 - [ncurses]tput: terminal attributes: No such device or address

Attached to Project: Arch Linux
Opened by Andrew Davis (reconmaster) - Thursday, 20 April 2017, 14:31 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 10 December 2019, 10:11 GMT
Task Type Bug Report
Category Packages: Core
Status Assigned
Assigned To Bartłomiej Piotrowski (Barthalion)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

Description:

In Jan 2017, I did a system upgrade. I noticed that a variety of
backend functions in emacs started to dump they following into various
buffers such as emails in mu4e and a variety of grep/rgrep interfaces.

tput: terminal attributes: No such device or address

As this is apparently an ncurses related method, I suspect it may have
something to do with ncurses.

From looking at the ncurses change log, it looks like tput was
modified on 2017/01/21:

"remove a restriction in tput's support for termcap names which
omitted capabilities normally not shown in termcap
translations"

This problem seems to be affecting a number of different users. Here
are the related issues I have found.

- https://github.com/boldpoker/edeliver/issues/188
- https://github.com/boldpoker/edeliver/issues/196
- https://github.com/rmarquis/pacaur/issues/655
- https://lists.opensuse.org/opensuse-factory/2017-02/msg00502.html


Additional info:

* nucrses 6.0+20170128-1
* emacs 25.1-4
* zsh 5.3.1-2

Steps to reproduce:

Install the latest ncurses. If mu is configured with mu4e, the error
message will appear at the top of every email opened and will
subsequently be part of outgoing emails.

Similarly attempting to use any commands such as grep/rgrep will
produce the same error message in the output buffer. The use cases for
the other bug reports may be informative too.
This task depends upon

Comment by Andreas Radke (AndyRTR) - Tuesday, 10 December 2019, 10:11 GMT
Is this still an issue?

Loading...