You are not logged in.

#1 2011-11-02 12:23:26

SanskritFritz
Member
From: Budapest, Hungary
Registered: 2009-01-08
Posts: 1,600
Website

[solved] Need help debugging logkeys

It looks like there is an archlinux specific problem with logkeys:
http://code.google.com/p/logkeys/issues/detail?id=60
I also am hit by this, and would like to ask for your help guys. Any idea what could cause this?

In a nutshell:

strace -f logkeys -s 

shows that the logfile could not be written for some reason:

[pid 10516] write(1, "Logging started ...\n\n2011-11-02 "..., 48) = -1 EBADF (Bad file descriptor)

The comments all have in common that they use archlinux, hence I dared to post here.

Last edited by SanskritFritz (2012-01-05 08:56:19)


zʇıɹɟʇıɹʞsuɐs AUR || Cycling in Budapest with a helmet camera || Revised log levels proposal: "FYI" "WTF" and "OMG" (John Barnette)

Offline

#2 2011-11-24 15:39:09

roygbiv
Member
Registered: 2011-05-18
Posts: 204

Re: [solved] Need help debugging logkeys

I have the exact same problem here, getting bad file descriptor errors. It simply doesn't work. When pressing the 'a' for instance:

write(1, "a", 1)                        = -1 EBADF (Bad file descriptor)

As I understand It tries to write 1 character from the string "a" to the file descriptor 1. What exactly is the fd number one? Also noticed that in my case the read calls, reads the key inputs from fd 0 - assuming this corresponds to /dev/input/event0? Should I 1+ this on googlecode?

Last edited by roygbiv (2011-11-24 15:41:29)

Offline

#3 2011-11-24 16:12:11

SanskritFritz
Member
From: Budapest, Hungary
Registered: 2009-01-08
Posts: 1,600
Website

Re: [solved] Need help debugging logkeys

roygbiv wrote:

I have the exact same problem here, getting bad file descriptor errors. It simply doesn't work. When pressing the 'a' for instance:

write(1, "a", 1)                        = -1 EBADF (Bad file descriptor)

As I understand It tries to write 1 character from the string "a" to the file descriptor 1. What exactly is the fd number one?

Hmm, this sounds like the STDOUT?

roygbiv wrote:

Also noticed that in my case the read calls, reads the key inputs from fd 0 - assuming this corresponds to /dev/input/event0?

That might be. You can change this on the command line, see the man.

roygbiv wrote:

Should I 1+ this on googlecode?

I think you should.


zʇıɹɟʇıɹʞsuɐs AUR || Cycling in Budapest with a helmet camera || Revised log levels proposal: "FYI" "WTF" and "OMG" (John Barnette)

Offline

#4 2011-11-24 22:48:40

roygbiv
Member
Registered: 2011-05-18
Posts: 204

Re: [solved] Need help debugging logkeys

SanskritFritz wrote:

Hmm, this sounds like the STDOUT?

Correct. From man stdin: ... the streams stdin, stdout, and stderr are (associated with) 0, 1, and 2, respectively ... Just for clarification. Left my comment on google code.

Last edited by roygbiv (2011-11-24 22:49:42)

Offline

#5 2012-01-05 08:48:46

SanskritFritz
Member
From: Budapest, Hungary
Registered: 2009-01-08
Posts: 1,600
Website

Re: [solved] Need help debugging logkeys

For the record:
http://www.linux-archive.org/general-di … gkeys.html
The logkeys-svn package already contains the patch by upstream, and I applied the patch in the logkeys package for the time being.


zʇıɹɟʇıɹʞsuɐs AUR || Cycling in Budapest with a helmet camera || Revised log levels proposal: "FYI" "WTF" and "OMG" (John Barnette)

Offline

#6 2012-01-08 14:00:17

hesse
Member
Registered: 2011-12-08
Posts: 88

Re: [solved] Need help debugging logkeys

Thank man! My evil plans continue..

Offline

Board footer

Powered by FluxBB