Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1406549 - fbtv won't run
Summary: fbtv won't run
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xawtv
Version: 27
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Dmitry Butskoy
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-20 22:02 UTC by jamie
Modified: 2018-06-12 16:04 UTC (History)
2 users (show)

Fixed In Version: xawtv-3.103-15.fc27 xawtv-3.103-15.fc28
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-12 15:20:03 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
strace (deleted)
2018-05-18 18:46 UTC, jamie
no flags Details
strace -f (deleted)
2018-05-20 14:41 UTC, jamie
no flags Details
After ruining FBTV with the spefic font. (deleted)
2018-05-20 17:19 UTC, jamie
no flags Details
VLC output (deleted)
2018-05-20 21:12 UTC, jamie
no flags Details
FBTV console output (deleted)
2018-06-11 17:49 UTC, jamie
no flags Details

Description jamie 2016-12-20 22:02:16 UTC
Description of problem:
The program 'fbtv' does not work. 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.Go to a tty and type 'fbtv' 
2.You will get the error 'can't use font /usr/lib/kbd/consolefonts/lat1-16.psfu.gz' but the font is present. 
3.

Actual results:
The error as stated above. 

Expected results:
The program runs. 

Additional info:
I seriously debt people are using this part of the package.(I tired it just to see if it would work.) AFIK frame buffer is not even supported on Linux anymore.

Comment 1 Fedora End Of Life 2017-07-26 00:07:21 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 2 jamie 2017-07-26 20:46:09 UTC
Still, happens in Fedora 26.

Comment 3 jamie 2017-10-22 23:35:15 UTC
Frame buffer IS supported on Linux but I still have to question what this is doing in the package.

Comment 4 jamie 2017-12-13 17:51:09 UTC
Still happens in fc 27.

Comment 5 Fedora End Of Life 2018-05-03 09:05:14 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 6 jamie 2018-05-03 19:04:51 UTC
Forget to update the Fedora Core version.

Comment 7 jamie 2018-05-17 21:34:59 UTC
I should add the error has two lines:
"can't use font /usr/lib/kbd/consolefonts/lat1-16.psfu.gz
no font available"

Comment 8 Dmitry Butskoy 2018-05-18 17:03:42 UTC
Well, do you have package "kbd-misc" installed? If not, try to install it.

Comment 9 jamie 2018-05-18 17:22:13 UTC
Yes I have 'kbd-misc' installed and I installed "kdb" but it did not make a difference.Kdb is a database thing? Is there another things called "kdb" I might be missing.

Comment 10 Dmitry Butskoy 2018-05-18 17:33:08 UTC
"kbd" -- "keyboard"...

It looks strange. If you have "kbd-misc" installed, then the file /lib/kbd/consolefonts/lat1-16.psfu.gz should be present. (Note "/lib", not "/usr/lib", but fbtv tries to search all the possible places anyway).

What happens if you try to specify some another font by `-f' option (see "man fbtv" for more info)?

Also try to run fbtv with strace and/or ltrace to see what happens in details:

"strace fbtv"  and/or "ltrace fbtv".

Normally, you should see there how fbtv tries to search the font, and why it does not find it...

Comment 11 jamie 2018-05-18 18:46:50 UTC
Created attachment 1438767 [details]
strace

Comment 12 jamie 2018-05-18 18:48:07 UTC
I tried a couple of different console fonts in '/lib/kbd/consolefonts' none of them worked. I have attached the strace output. 
'

Comment 13 Dmitry Butskoy 2018-05-19 19:54:11 UTC
According to the strace output, your system has /usr/lib/kbd/consolefonts/lat1-16.psfu.gz, whereas the font (provided by kbd-misc package) should be at /lib/kbd/consolefonts/lat1-16.psfu.gz (note missing "/usr" fron the start).

When fbtv run, it searches for fonts in the several directories, and "/usr/lib" variant takes precedence over "/lib". In other word, if the font file is present under "/usr/lib/....", the actual font (under "/lib/.....") is mot reached.

Verify, why you have the font filename in this ("/usr/lib") location (probably some garbage, some rests from other third-party packages etc.). Ie., by "rpm -q -f /usr/lib/kbd/consolefonts/lat1-16.psfu.gz"

Make sure you have the font in the right place ("/lib/....."), rename/move the wrong ("/usr/lib") somewhere and try to run fbtv without the font under /usr/lib .

Comment 14 jamie 2018-05-19 22:53:11 UTC
"rpm -q -f /usr/lib/kbd/consolefonts/lat1-16.psfu.gz"outputs 'kbd-misc-2.0.4-4.fc27.noarch'. "/lib" is a symbalic link to "/usr/lib".

Comment 15 Dmitry Butskoy 2018-05-19 23:40:35 UTC
Could you repeat strace with `-f' option to catch all the child processes, ie.:

"strace -f fbtv"

Comment 16 jamie 2018-05-20 14:41:45 UTC
Created attachment 1439168 [details]
strace -f

Comment 17 Dmitry Butskoy 2018-05-20 16:49:21 UTC
Since kbd-1.15.3, kbd was mostly switched from psf1 to psf2 console font format. Xawtv (and fbtv) was written too ago, and does not support psf2.

Fortunately, there are some fonts still in psf1, including the default for Fedora latarcyrheb-sun16. The full psf1 list for today is:

LatGrkCyr-8x16
eurlatgr
lat0-sun16
lat2-sun16
latarcyrheb-sun16
pancyrillic.f16

Could you please try to run fbtv with lat0-sun16 and latarcyrheb-sun16 ? Ie.:

fbtv -f /lib/kbd/consolefonts/lat0-sun16.psfu.gz

and

fbtv -f /lib/kbd/consolefonts/latarcyrheb-sun16.psfu.gz

(Note it requires full patch to the fontfile specified)

Comment 18 Dmitry Butskoy 2018-05-20 16:50:10 UTC
full patch --> full path ...

Comment 19 jamie 2018-05-20 17:18:05 UTC
That works from a TTY but now I get a blank screen. When I go to X-windows and go back I see some messages which are in the "write" section of the stack trace I will attach. 

I have to question whether Fedora should be still supporting 'fbtv' it seems old and probably hard to get running on new systems. Should this new issue be a new bug?

Comment 20 jamie 2018-05-20 17:19:32 UTC
Created attachment 1439257 [details]
After ruining FBTV with the spefic font.

Comment 21 Dmitry Butskoy 2018-05-20 17:25:29 UTC
It seems some hardware-specific issue.

Does "xawtv" (under X-window) work in your environment?

Do you have a whole blank screen under TTY, or some text appeared at the top of the screen? (Ie. just to make sure the font latarcyrheb-sun16 is working with fbtv...)

Comment 22 Dmitry Butskoy 2018-05-20 17:27:32 UTC
Also try v4l-conf under TTY ...

Comment 23 jamie 2018-05-20 18:13:07 UTC
>>Does "xawtv" (under Xwindow) work in your environment?

Sort of, I get a black window and can click on it and get a menu. If I lunch it from a terminal(in Xwindows), it gives a lot of output including(Device or resource busy). 

>>Do you have a whole blank screen under TTY, or some text appeared at the top of the screen? (Ie. just to make sure the font latarcyrheb-sun16 is working with fbtv...)

I have a whole black screen but when I switch too Xwindows and switch back(useing control + alt + F2 and control + alt + f1) I get the errors shown in the stack trace.(and I have to log out before the tty works properly)

Also try v4l-conf under TTY ...

v4l-conf on tty outputs(transcribed): 

map: vt02->fb0
v4l-conf:useing frambuffer device /dev/fb0
mode:2048x1152, depth=32 bpp=32 bpl=8192 base=0xd034d000
/dev/video0 [v4l2]: no overlay support 

Is this what you expected to see? 

----
VLC can run in framebuffer mode if this helps.

Comment 24 Dmitry Butskoy 2018-05-20 20:18:42 UTC
Well, try to cause xawtv to work first, then fbtv (there are much more possibilities for debug/tune etc. under X).

It seems that xawtv/fbtv does not support non 4:3 aspect ratio, and does not support some WxH combinations.

Try to obtain what supports your TV card, utilizing verbose vlc output, ie.
"vlc -vv v4l://", search for "frame size" in the output.

Then try to start xawtv with some of those geometries, ie.
"xawtv -geometry 320x240" .  If all the variants fail, then probably your card is too modern for ancient Xawtv...

Comment 25 jamie 2018-05-20 21:12:12 UTC
Let me catch you up, I tried to get my card to work under Linux, I talked about it here: 
https://www.linuxquestions.org/questions/linux-hardware-18/software-for-a-%27wintv-hvr-1600mce%27-4175607127/page2.html

-------

The best I could get was this script: 
#/bin/bash
v4l2-ctl --set-input=1
v4l2-ctl --set-ctrl stream_type=1
mplayer /dev/video0

It was unsuccessful because I could not stop it from lagging. 

VLC never worked for me with the card(the test was done with I mentioned was done with an MPEG). XawTV never worked, either I tried fbtv just in case but I did not expect it to work. 

xawtv -geometry 320x240 made no diffence. 

It's hard to support my card, since the output is not a raw single but an MPEG2 encoded video.(nice cause my computer has less(?) work to do. 

I will attach the VLC output incase it helps.

Comment 26 jamie 2018-05-20 21:12:48 UTC
Created attachment 1439318 [details]
VLC output

Comment 27 Dmitry Butskoy 2018-05-20 21:51:11 UTC
Yep, XawTV is not for MPEG-output-only cards.

Anyway, thanks for the recent reports about font issues. I'll provide a patched release soon.

Comment 28 jamie 2018-05-21 00:44:21 UTC
Your welcome :)

Comment 29 jamie 2018-05-21 00:45:51 UTC
If they are other issues, we probably need someone with supported hardware to test it.

Comment 30 Xose Vazquez Perez 2018-06-01 00:25:16 UTC
FYI 3.104 was released at: https://git.linuxtv.org/xawtv3.git

3.104
=====

* disable DGA if client is not local, fixing usage over ssh
* Drop supplementary group IDs when dropping privileges
* Add desktop and appdata files for xawtv, motv and mtt
* Fix mtt not being able to tune tv channels
* Remove superfluous ; add end of functions
* Add a workaround for bttv kernel driver planar fmt width bug
* Allow setting alsa_latency from ~/.xawtv
* Fix not being able to get a larger latency on capture devices with small
  max period sizes
* prefer CAP_STREAMING over CAP_READWRITE
* Fix segfault under certain conditions

Comment 31 Dmitry Butskoy 2018-06-02 15:22:23 UTC
Well, it is marked as 3.104 at https://git.linuxtv.org/xawtv3.git , but does not appeared at https://linuxtv.org/downloads/xawtv/ .

Actually, all the patches already applied here (in Fedora) lead to the same code as the resent 3.104, ie. the update is not needed...

Comment 32 Fedora Update System 2018-06-02 15:24:40 UTC
xawtv-3.103-15.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-b187c608c4

Comment 33 Fedora Update System 2018-06-02 15:25:10 UTC
xawtv-3.103-15.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-8a872dbdbb

Comment 34 Fedora Update System 2018-06-02 15:25:40 UTC
xawtv-3.103-9.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-5d635d16f9

Comment 35 jamie 2018-06-02 16:57:29 UTC
How do I test that the new binary at least takes me to the black screen I got before?(where do I get the binary)

Comment 36 Dmitry Butskoy 2018-06-02 17:01:57 UTC
For now, from https://koji.fedoraproject.org/koji/buildinfo?buildID=1087873 ,
should appear soon at standard updates-testing repo (and at updates after a week).

Comment 37 jamie 2018-06-02 17:25:29 UTC
Ok now I have the black screen with the binary but that is expected. I can't comment on whether or not the program is 'generally functional' since as we determined I don't have the correct hardware.

Comment 38 Fedora Update System 2018-06-02 20:28:37 UTC
xawtv-3.103-15.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-8a872dbdbb

Comment 39 Fedora Update System 2018-06-02 22:03:41 UTC
xawtv-3.103-9.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-5d635d16f9

Comment 40 Fedora Update System 2018-06-02 22:34:19 UTC
xawtv-3.103-15.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-b187c608c4

Comment 41 Mauro Carvalho Chehab 2018-06-11 15:39:17 UTC
(In reply to Dmitry Butskoy from comment #17)
> Since kbd-1.15.3, kbd was mostly switched from psf1 to psf2 console font
> format. Xawtv (and fbtv) was written too ago, and does not support psf2.

That was true until Xawtv version 3.104. I added support to psf2 format for version 3.105. It also fixes a few other issues at fbtv.  So, it should now work without any patches.

Could you please test it? For now, the new packages are only at Koji.

The rawhide packages are at:
    https://koji.fedoraproject.org/koji/buildinfo?buildID=1090851

The packages for Fedora 28 are at:
    https://koji.fedoraproject.org/koji/taskinfo?taskID=27562216

Comment 42 jamie 2018-06-11 15:42:39 UTC
I tested it and got to the blank screen that I had in comment#23. I did not rate it as working as I feel it's best for me to step down from this. (as I don't have the correct hardware to use it correctly.)

Comment 43 Mauro Carvalho Chehab 2018-06-11 15:57:37 UTC
(In reply to Dmitry Butskoy from comment #17)

> fbtv -f /lib/kbd/consolefonts/latarcyrheb-sun16.psfu.gz
> 
> (Note it requires full patch to the fontfile specified)

Forgot to mention but, on xawtv 3.105, the full patch is not required anymore. 

Just:
   fbtv -f latarcyrheb-sun16
or
   fbtv -f latarcyrheb-sun16.psfu.gz

Would equally work for any PSF1 or PSF2 font.

(In reply to Dmitry Butskoy from comment #31)
> Well, it is marked as 3.104 at https://git.linuxtv.org/xawtv3.git , but does
> not appeared at https://linuxtv.org/downloads/xawtv/ .

I also added both 3.105 and the missing 3.104 tarballs at linuxtv.org.

(In reply to jamie from comment #42)
> I tested it and got to the blank screen that I had in comment#23. I did not
> rate it as working as I feel it's best for me to step down from this. (as I
> don't have the correct hardware to use it correctly.)

Yeah, mpeg decoding is not directly supported by xawtv. It may work via libv4l, if one would add a parser there for MPEG formats (the closest one it supports is JPEG). That would make it work also with other V4L2 apps.

Comment 44 Mauro Carvalho Chehab 2018-06-11 16:50:29 UTC
(In reply to jamie from comment #42)
> I tested it and got to the blank screen that I had in comment#23. I did not
> rate it as working as I feel it's best for me to step down from this. (as I
> don't have the correct hardware to use it correctly.)

Could you please test this version:

https://koji.fedoraproject.org/koji/taskinfo?taskID=27563207

It won't make xawtv compatible with MPEG, but it should at least restore the screen and show an error message.

Comment 45 jamie 2018-06-11 17:49:18 UTC
Created attachment 1450162 [details]
FBTV console output

Comment 46 jamie 2018-06-11 17:52:25 UTC
I get this output at the console. We can ignore the lines saying that I can't output the correct format. Not sure where 1256x1008 32, comes from, probably both my monitors put together to make that res. I don't know how to force a res on tty, I've reed using Grub is not supported by ATI cards?

Comment 47 jamie 2018-06-11 20:39:08 UTC
Installing "fbset" generates a '/etc/fb.modes' and this gets rid of the last error for me. At this point, I think I can't run it because I don't have the supported hardware.

Comment 48 Mauro Carvalho Chehab 2018-06-12 09:53:19 UTC
(In reply to jamie from comment #46)
> I get this output at the console. We can ignore the lines saying that I
> can't output the correct format.

Thanks for the test! It is weird that try_fmt and set_fmt aren't returning the same thing, though. That's either a bug at the driver or at libv4l.

> Not sure where 1256x1008 32, comes from,
> probably both my monitors put together to make that res. 

Likely yes.

> I don't know how to
> force a res on tty, I've reed using Grub is not supported by ATI cards?

You could tell fbtv to set a resolution for the camera with the -s parameter, for instance "fbtv -s 640x480". That actually tries to set the closest resolution at the V4L2 driver. It will keep using whatever framebuffer resolution it detects.

Comment 49 Fedora Update System 2018-06-12 09:57:06 UTC
xawtv-3.105-2.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-46c0f78f34

Comment 50 Dmitry Butskoy 2018-06-12 12:58:41 UTC
Fine.

Do you plan to update for F27, EL6, EL7 as well?
Or tell me when I can do it myself...

Comment 51 jamie 2018-06-12 15:03:07 UTC
No matter what I try I still get "can't find useful capture format"

Comment 52 Fedora Update System 2018-06-12 15:12:27 UTC
xawtv-3.105-2.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-46c0f78f34

Comment 53 Fedora Update System 2018-06-12 15:20:03 UTC
xawtv-3.103-15.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.

Comment 54 Fedora Update System 2018-06-12 16:04:08 UTC
xawtv-3.103-15.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.