Feature #751
closed
Add function to find X.org VT
Added by Hammel over 4 years ago.
Updated over 4 years ago.
Description
This can be done with this command:
ps -l | grep "X :0" | grep -v grep | tr -s " "| cut -f7 -d" "
This doesn't appear to fail under ash (Busybox shell) if the first grep doesn't find anything. We can use this to find the correct "vtsrc" for any app.
- Severity changed from 03 - Medium to 01 - Critical
This was a problem during release testing for 1.1 on B/B+ models so I'm moving it up in severity.
- Priority changed from High to Immediate
- Status changed from New to In Progress
- % Done changed from 0 to 10
- % Done changed from 10 to 20
I Have a branch with functions for supporting getting the VT for the current process (getVTNum) and any named process (getVT) in the RM-751 branch of libpibox.
The merge request for this is here: https://gitlab.com/pibox/libpibox/-/merge_requests/1
These functions need to be tested. There are unit tests already written. There is no app currently using this so I think adding it to videofe would be the best place to start (since it needs it most).
- % Done changed from 20 to 50
Unit tests are implemented and run successfully.
Now I need to test with videofe.
- % Done changed from 50 to 60
Initial test without full media system shows piboxGetVTNum() works as expected in videofe. It finds the vt that X is on. This was true even when I remotely logged in, set DISPLAY=unix:0.0 and ran videofe.
A more complete test is needed to make sure videofe switches vts correctly given the use of the new piboxGetVTNum() api.
- % Done changed from 60 to 70
Works on touchscreen/rpi3. Need to test on monitor/rpi2.
- % Done changed from 70 to 90
Verified working on monitor/rpi2.
Just need to commit and push now.
- Status changed from In Progress to Closed
- % Done changed from 90 to 100
All changes committed and pushed. All PR's approved and merged.
Closing issue.
Also available in: Atom
PDF