Odd terminal response when editing a file

[varaonaid]

Hi,

I've noticed the past several times I've edited a file from the terminal (ie fstab), I get an odd output when it's trying to open my editor:

X Error: BadDevice, invalid or uninitialized input device 168
Major opcode: 145
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 168
Major opcode: 145
Minor opcode: 3
Resource id: 0x0
Failed to open device
DCOPClient::attachInternal. Attach failed Could not open network socket
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

kdeinit: Can't connect to the X Server.
kdeinit: Might not terminate at end of session.
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

kded: cannot connect to X server :0.0
DCOP aborting call from 'anonymous-6682' to 'kded'
kded: ERROR: Communication problem with kded, it probably crashed.

After all those errors, kwrite opens up and I can successfully edit and save the file but I found it kind of odd. It also does the same when I tried using kate instead. However, nano doesn't have this trouble.

Any ideas on this? Is it even a problem I should worry about since in the end, I can still edit?

Thanks in advance!

[Husse]

It is a problem in as much as you get annoyed by it - I do!
I get a similar message and I have looked it up and it has something to do with mouse or keyboard not configured right in xorg.conf. I don't use KDE normally so I've not looked deeper into it, but it should be possible to get rid of it.
But as long as the application opens up as it should it's just a minor nuisance

[varaonaid]

Thanks Husse. I think I'll just deal with it for the moment. More pressing matters in life than that. Plus, hopefuly I can look forward to a Cassandra KDE sometime before too long