Project

General

Profile

Actions
Copy link

Bug #1129

closed

Launcher/appmgr appear to be ignoring /etc/pibox-env settings.

Added by Hammel 8 months ago. Updated 8 months ago.

Status:
Closed
Priority:
Immediate
Assignee:
Hammel
Target version:
PiBox - 3.0 - Corrino
Start date:
17 Apr 2024
Due date:
% Done:

100%

Estimated time:
Severity:
01 - Critical

Description

On a fresh install the /etc/pibox-env file is there and contains

TSLIB_TSDEVICE=/dev/input/event2

This is the correct setting. But launcher does not recognize touch events. It's not clear if appmgr is having the same problem. Manually setting the env var seems to work if you launch the app manually.

Actions
Copy link
 #1

Updated by Hammel 8 months ago

  • Priority changed from Urgent to Immediate
Actions
Copy link
 #2

Updated by Hammel 8 months ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 10

Rebuilt libpibox and the rootfs and installed, but that didn't fix things.

Will need to run launcher in debug mode to find out why it's not picking up the env var.

Actions
Copy link
 #3

Updated by Hammel 8 months ago

  • % Done changed from 10 to 60

Found it - there is a /etc/pointercal file that is incorrect. In fact, it's not needed at all. It isn't in the source skeleton tree. I think this is leftover in the pushed skeleton tree (under package/customize/source) that ends up on the target rootfs.

Actions
Copy link
 #4

Updated by Hammel 8 months ago

It's under buildroot/xeon/pointercal.landscape. This needs to be removed and references to it in configs/buildroot.mk should also be removed.

Actions
Copy link
 #5

Updated by Hammel 8 months ago

  • Status changed from In Progress to Closed
  • % Done changed from 60 to 100

Code tested, committed and pushed.

Closing issue.

Actions
Copy link

Also available in: Atom PDF