VLC crash ( '/ dev / fb0' failed, globalhotkeys,none, ..)

[torreone]

Greetings everyone, I just signed up. I have I have this problem
VLC, previously fully functional, suddenly started not playing videos.
Executed from the terminal, both as vlc file.mp4 and as cvlc file.mp4 it gave the following error:
(*) DirectFB / Core: Single Application Core. (2014-10-24 12:33)
(*) Direct / Memcpy: Using Generic 64bit memcpy ()
(!) Direct / Util: opening '/ dev / fb0' failed
-> Permission denied
(!) DirectFB / FBDev: Error opening framebuffer device!
(!) DirectFB / FBDev: Use 'fbdev' option or set FRAMEBUFFER environment variable.
(!) DirectFB / Core: Could not initialize 'system_core' core!
-> Initialization error!
[00007f6ffc01e4d8] directfb vout display error: Cannot create primary surface
[00007f6ffc01e4d8] fb vout display error: cannot get terminal mode (Inappropriate ioctl for device)
[00007f6fd8000958] core video output error: video output creation failed
[00007f7008c2b7f8] core decoder error: failed to create video output

I then followed the following indications
"Change the permissions on the framebuffer by creating a udev rule
sudo nano /etc/udev/my-rules.d/framebuffer.rules
Then put a line in it like this
KERNEL == "fb0", OWNER = "root", MODE = "0660"
Then add yourself to the video group
sudo usermod -a -G video username
Change username for your actual username, then restart "

found here https://ubuntuforums.org/archive/index. ... 92216.html

I didn't get any results, but from that moment the error changed and became the following
(*) DirectFB / Core: Single Application Core. (2014-10-24 12:33)
(*) Direct / Memcpy: Using libc memcpy ()
(!) DirectFB / core / vt: Error opening `/ dev / tty0 '!
-> Permission denied
(!) DirectFB / Core: Could not initialize 'system_core' core!
-> Initialization error!
[00007f54b8001268] directfb vout display error: Cannot create primary surface
[00007f54b8001268] fb vout display error: cannot get terminal mode (Inappropriate ioctl for device)
[00007f54d0061a98] core video output error: video output creation failed
[00007f54e0c6c168] core decoder error: failed to create video output

Even trying to delete the /etc/udev/my-rules.d/framebuffer.rules file and removing / relocating my user from the video group, I was no longer able to get the error back on dev / fb0
Also, / dev / tty0 'should have no relation to videos

In / var / log / syslog the error reported is instead:
kernel: [2649.437090] vlc [10188]: segfault at 4 ip 00007f3f92905652 sp 00007f3f50a38d28 error 4 in i965_dri.so [7f3f9201d000 + b8d000]

where error 4 in i965_dri.so should be:
libGL error: unable to load driver: i965_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: i965

The ts → mp4 conversion was also impossible. The error reported in / var / log / syslog is:
Aug 11 09:10:17 ... vlc [3226]: avcodec: cannot open hevc video encoder
Aug 11 09:10:18 ... vlc [3226]: main: no encoder modules matched
Aug 11 09:10:18 ... vlc [3226]: stream_out_transcode: cannot find video encoder (module: any fourcc: hevc).

I tried to uninstall and reinstall vlc several times (using snap) trying to erase all traces of previous installations, without changing the situation.
Running vlc from the terminal, you see it in the active processes of ubuntu, you hear the audio but you don't see any video, and if you don't kill the process it continues indefinitely.
On the contrary, both ffmpeg and fflplay seem to work perfectly (I converted file.ts to file.mp4 without problems)

I do not know what to do

[torreone]

Opening from terminal vlc (or cvlc) not followed by filevideoname, I always get this error

[00000000010e1098] core interface debug: using interface module "hotkeys"
[0000000001131408] core interface debug: looking for interface module matching "globalhotkeys, none": 15 candidates
[0000000001131408] core interface debug: no interface modules matched
[0000000001131408] core interface error: no suitable interface module
[0000000000fb5148] core libvlc error: interface "globalhotkeys, none" initialization failed

Also passing the filename to the following error follows, at the end:

(!) Direct / Util: opening '/ dev / fb0' failed
-> Permission denied
(!) DirectFB / FBDev: Error opening framebuffer device!
(!) DirectFB / FBDev: Use 'fbdev' option or set FRAMEBUFFER environment variable.
(!) DirectFB / Core: Could not initialize 'system_core' core!

-> Initialization error!
[00007fd5d4001f08] directfb vout display error: Cannot create primary surface
[00007fd5d4001f08] fb vout display warning: disabling TTY handling, use with caution because there is no way to return to the TTY
[00007fd5d4001f08] fb vout display error: cannot get terminal mode (Inappropriate ioctl for device)
[00007fd5d4001f08] core vout display debug: no vout display modules matched
[00007fd5ac0610d8] core video output error: video output creation failed
[00007fd5ac0624e8] core spu text debug: removing module "freetype"
[00007fd5ac0c5dc8] core scale debug: removing module "yuvp"
[00007fd5ac095818] core scale debug: removing module "swscale"
[00007fd5d0c26528] core decoder error: failed to create video output
[00007fd5d0c26528] core decoder warning: can't get output picture
[00007fd5d0c26528] avcodec decoder warning: disabling direct rendering
[00007fd5cc0009b8] core input debug: Decoder wait done in 27 ms
[0000000001089638] core audio output debug: inserting 1408 zeroes

[Rémi Denis-Courmont]

The DirectFB library version provided by Ubuntu wants to access tty0 for whatever reason. That's just how it is.

Running VLC without a display server is not recommended.

[torreone]

Running VLC without a display server is not recommended.

I tried to run it also from the terminal to see the error messages.
Using the display server (opening vlc from dash and opening a video file with open, it crashes immediately giving this message in syslog, which closes with the loading error (does not find a driver load)

Aug 11 13:16:01 giancarlo-Aspire-E5-573G kernel: [16338.892452] vlc[14175]: segfault at 4 ip 00007f8876905652 sp 00007f883a18fd28 error 4 in i965_dri.so[7f887601d000+b8d000]

The DirectFB library version provided by Ubuntu wants to access tty0 for whatever reason. That's just how it is.

How resolve, if it's possible ?

[Rémi Denis-Courmont]

i965_dri.so is your Intel GPU driver crashing

DirectFB is no longer supported in VLC, so it's very unlikely that anybody can help you with it.

[torreone]

i965_dri.so is your Intel GPU driver crashing

DirectFB is no longer supported in VLC, so it's very unlikely that anybody can help you with it.

Thanks for the reply.
Totem, ffmpeg and ffplay (ubuntu 16.04) are working normally, and they should all, like vlc, access the graphics card drivers.
If the problem is directFB I don't understand why they work while VLC doesn't,
Now I have installed vlc 3.0.16.
If it no longer supports directFB is it possible to install the drivers it needs in parallel with the incompatible directFB (which however seems to work well with all other graphics software)?

[Rémi Denis-Courmont]

If DirectFB fails due to permission problem in VLC, it will fail in any other app just as well. Again, your problem has nothing to do with VLC and everything to do with DirectFB.

My point is just that DirectFB knowledge on this forum is nonexistent. DirectFB as a project is pretty much dead since the middle of the previous decade, and VLC 4.0 will drop the DirectFB plugin entirely.

[torreone]

For this I was wondering, if vlc no longer supports directDB its requests must be made to the graphics card without going through directFB
Is there any way to do this by installing additional software?
Otherwise I will no longer be able to use vlc (at least on my pc) which until two days ago worked without any problem

[Rémi Denis-Courmont]

Of course, you could write a media player that would substitute the display server and take full control of the GPU. VLC does not currently support that because it's considerable work for a niche use case (or well, because nobody cared to implement it).

[dma_k]

If DirectFB fails due to permission problem in VLC, it will fail in any other app just as well. Again, your problem has nothing to do with VLC and everything to do with DirectFB.

My point is just that DirectFB knowledge on this forum is nonexistent. DirectFB as a project is pretty much dead since the middle of the previous decade, and VLC 4.0 will drop the DirectFB plugin entirely.

Would be pity to loose this renderer. Have you checked DirectFB2?

[unidan]

The fb output has been replaced by a KMS video output to match the development upstream in linux.