Running classic framebuffer tools from terminology #9

New Issue

defdefred · 2023-03-20T00:13:34-07:00

defdefred commented

2023-03-20 00:13:34 -07:00

Terminology in framebuffer mode is quite impressive!

When I try to run some classic framebuffer tools like fim, mpv or netsurf -f sdl, I get error like:

ioctl VT_GETSTATE: Inappropriate ioctl for device (not a linux console?)
ioctl VT_GETSTATE: Inappropriate ioctl for device

Is it possible to temporaray share the framebuffer with theses tools?

(sorry, I also open an issue here: https://github.com/borisfaure/terminology/issues/157, maybe issue creation should be disable on github if not really used?)

Terminology in framebuffer mode is quite impressive! When I try to run some classic framebuffer tools like fim, mpv or netsurf -f sdl, I get error like: ``` ioctl VT_GETSTATE: Inappropriate ioctl for device (not a linux console?) ioctl VT_GETSTATE: Inappropriate ioctl for device ``` Is it possible to temporaray share the framebuffer with theses tools? (sorry, I also open an issue here: https://github.com/borisfaure/terminology/issues/157, maybe issue creation should be disable on github if not really used?)

defdefred changed title from ~~running classic framebuffer tools from terminology~~ to Running classic framebuffer tools from terminology

2023-03-20 00:34:42 -07:00

raster commented

2023-03-20 01:42:34 -07:00

it's not possible. vt's are owned by some process. it's a co-operative setup. any new process would follow the convention of requesting the vt - but finding it's owned and will give up. you'd get the same problems above if you run fim etc. in x11 - the xserver owns the vt. same with the case of terminology + fb - no different to the xserver case.

you can run chvt to another vt (this will result in a signal to the current vt owner to give it up), then run fim/mpv etc. then chvt back to the vt terminology was on - so you'll have to make a script to wrap commands in to do this. in theory the above ytools could also do the same thing chvt does - check currently active vt, chvt (request giving up the vt), switch to a custom new vt of their own, do their thing, give up that vt and switch back to the original vt.

it's not possible. vt's are owned by some process. it's a co-operative setup. any new process would follow the convention of requesting the vt - but finding it's owned and will give up. you'd get the same problems above if you run fim etc. in x11 - the xserver owns the vt. same with the case of terminology + fb - no different to the xserver case. you can run chvt to another vt (this will result in a signal to the current vt owner to give it up), then run fim/mpv etc. then chvt back to the vt terminology was on - so you'll have to make a script to wrap commands in to do this. in theory the above ytools could also do the same thing chvt does - check currently active vt, chvt (request giving up the vt), switch to a custom new vt of their own, do their thing, give up that vt and switch back to the original vt.

defdefred commented

2023-03-20 04:15:49 -07:00

I will test this, thanks!

defdefred commented

2023-03-21 14:59:00 -07:00

Hello,

sudo openvt -slw /usr/bin/fim Images is working perfectly.

Thanks!

Hello, `sudo openvt -slw /usr/bin/fim Images` is working perfectly. Thanks!

defdefred closed this issue

2023-03-21 14:59:01 -07:00

Sign in to join this conversation.

No Label

No Milestone

No project

No Assignees

2 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: enlightenment/terminology#9