Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

main interface error: no suitable interface module #195

Open
xplosionmind opened this issue Nov 30, 2023 · 4 comments
Open

main interface error: no suitable interface module #195

xplosionmind opened this issue Nov 30, 2023 · 4 comments

Comments

@xplosionmind
Copy link

When I run

flatpak run org.videolan.VLC

I get this error:

VLC media player 3.0.20 Vetinari (revision 3.0.20-0-g6f0d0ab126b)
[00005617e8954080] main interface error: no suitable interface module
[00005617e88747e0] main libvlc error: interface "globalhotkeys,none" initialization failed
[00005617e88747e0] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface.
[00005617e8954080] skins2 interface error: cannot initialize OSFactory
[00005617e8909cd0] main playlist: playlist is empty
[00005617e8954080] [cli] lua interface: Listening on host "*console".
VLC media player 3.0.20 Vetinari
Command Line Interface initialized. Type `help' for help.
> %                          

The application does not start!

@nurupo
Copy link
Contributor

nurupo commented Dec 16, 2023

Can't reproduce if I run in my regular terminal, but if I remove all env variables via env -i bash --noprofile --norc then I get a similar interface error (along with additional errors about PulseAudio, dbus, etc). If I add the DISPLAY env variable, i.e. DISPLAY=:0 flatpak run org.videolan.VLC, then the error goes away and the VLC window appears, but in the wrong styling as env variables dictating which style to use are not set.

Anyway, it sounds like the issue is not in the VLC Flatpak but in your shell environment. Run env in your shell and see what variables you might be missing.

@xplosionmind
Copy link
Author

xplosionmind commented Jan 4, 2024

It might have happened that I accidentally deleted all files in my ~/.config directory, but I thought everything would be solved by installing and reinstalling the flatpak and/or the rpm package, but I still have the same issue!

I had no issues in all my other packages/flatpaks.

Is there a default config file or env variables set I can use as reference to see if that is the problem?

@xplosionmind
Copy link
Author

Hello, I have been trying many different tweaks, but no result… could you please help me troubleshoot this?

@xplosionmind
Copy link
Author

I also tried running flatpak repair

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants