xbrlapi debugging message spamming .xsession-errors; please silence it.

Bug #1579531 reported by TJ on 2016-05-08
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
brltty (Ubuntu)
Wishlist
Unassigned

Bug Description

16.04 amd64.

$HOME/.xsession-errors contains cryptic messages that do not indicate where they come from. They turn out to be harmless but it would be good if they at least were prefixed with the source.

openConnection: connect: No such file or directory
cannot connect to brltty at :0

They indicate the absence of a braille tty so how about:

xbrlapi: Cannot find a Braille Teletype device
xbrlapi: cannot connect to brltty at :0

TJ (tj) on 2016-05-08
Changed in brltty (Ubuntu):
status: New → Confirmed
importance: Undecided → Wishlist

I have suggested a patch to Dave, upstream maintainer of brltty

dino99 (9d9) wrote :

This error is polluting .xsession-errors on yakkety too.

openConnection: connect: No such file or directory
cannot connect to brltty at :0

Glancing at such error , i've found that answer from a Debian dev:

> openConnection: connect: No such file or directory
> cannot connect to brltty at :0

That's no error, they're just debugging messages. They come from xbrlapi which
is trying to connect to a braille display but you have none so it can't. Nothing
to worry about.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728947

So what is only needed is to silence this debugging message from xbrlapi.
This may affect most of the users, as they does not have use of braille.

tags: added: yakkety
dino99 (9d9) on 2016-08-02
summary: - openConnection: connect: No such file or directory
+ xbrlapi debugging message spamming .xsession-errors; please silence it.
tags: added: xenial
dino99 (9d9) wrote :

xbrlapi 5.4 on yakkety seems clean now; nothing logged into xsession-errors.

tags: removed: yakkety
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.