Actions
Bug #1241
openkioskOpenURI[dbkiosk.c:455] INFO error on read(): No such device
Status:
In Progress
Priority:
Immediate
Assignee:
Category:
Runtime
Target version:
Start date:
30 Oct 2025
Due date:
% Done:
50%
Estimated time:
Severity:
01 - Critical
Description
The log message is incorrect. It's not coming from kioskOpenURI. It comes from these lines in the new events.c code.
/* Read the event - but we don't care about what's in it. */
if (read(eventsfd, &ev, sizeof(struct input_event)) != sizeof(struct input_event))
{
piboxLogger(LOG_TRACE1, "error on read(): %s\n", strerror(errno));
continue;
}
So there are two issues here:
- If this happens I may need to restart the events processor. It's getting events but I'm not using the keyboard.
- I think this happens because the keyboard it was watching has been detached.
- log.c needs a mutex to make sure threads don't overwrite each other.
Updated by Hammel 10 days ago
- % Done changed from 10 to 50
I tested a fix for this but the test was on a Kiosk and the event processor doesn't run there. It only runs on the AutoKiosk.
So I need to retry this on the AutoKiosk, which has currently been running for 14 days as a stress test. It also has NOT had the monitor enabled, though it is connected to the HDMI switch. So I need to see if it's still working before I retry this fix.
Actions