Call for testing: VLC 3.0.0-rc1

is anyone having problems using kde-connect to control vlc 3.0.0-rc3 ?
edit: rc1 ~ rc2 worked with kde-connect

syslog with rev 59:

org.kde.kdeconnect[2046]: kdeconnect.plugin.mpris: MPRIS service “org.mpris.MediaPlayer2.vlc” just came online
org.kde.kdeconnect[2046]: kdeconnect.plugin.mpris: Mpris addPlayer “org.mpris.MediaPlayer2.vlc” -> “VLC media player”

in rc3 this doesn’t work anymore.

I believe removable-media needs to be connected manually:

sudo snap connect vlc:removable-media
1 Like

I think its the apparmor file connected to snap. They limit the directories an app can access. Which makes sense in most cases. What really sucks is that they do not support links properly. If they follow links, they use the physical location instead of the link. If your system is on an SSD and you have a hard drive for movies, statically mounted, you have no chance to use it.

I’m having a problem with the VLC snap.

I’m running the version in candidate (3.0.0-rc4-17-g661df83) and my laptop is using a HDPi configuration. When I try to seek I’m seeing this:

And if I click nothing happens.
It looks like if it was not detecting the cursor position correctly. Does anybody suffer from this?

just make sure to mount it under the /media folder, then the removable-media interface will giuve you full access …

Screen: 1920x1080, vlc 3.0.0-rc5: seeking works, but i’m seeing the same cursor behavior

Can someone tell me why vlc.snap is not recognize idiom system from my OS linuxmint 18.3. Idiom system spanish.?

Perhaps the snaps do not recognize the default language of the operating system.? I have seen that some applications in snap only come in English.

I have installed the same version vlc in flatpak and the flatpak recognizes the language of my system, which in this case is Spanish.

/usr/share/libdrm/amdgpu.ids: No such file or directory
amdgpu_device_initialize: Cannot parse ASIC IDs, 0xffffffea.[00007f58bc001430] filesystem stream error: cannot open file /media/haug/data-1/movie/MyMovie.m2t (Permission denied)

Did you connect the removable-media snap interface first ?

Hey guys any update on this? I still have no fonts :frowning:

ls still present in vlc 3.0.0 … :frowning:
(the snap is a great opportunity to test if new features/fixes landed :wink: )

Installation went smoothly. When trying to play a dvd vlc complains about missing css key. Tested on kde neon

VLC RC8 still can’t access some mounted devices. I have an internal HDD mounted under /mnt/ called “Daten”.
sudo snap connect vlc:removable-media does not work for any media under /mnt/Daten/
There is a screenshot where you can see how the HDD is mounted and how VLCs error looks like.

mount it under /media and it will work … the removable-media interface only allows access to devices monted there … (i guess even a bind mount would work if you want to keep the old location intact for scripts or whatnot)

1 Like

Vlc apparently does not access the regional settings, because it does not translate the language of the application into my regional language. When will this be implemented for vlc. Snap ?. The deb versions do.

So far it seems to function without issue. I mostly was streaming through youtube videos. the only issues I had were some of the same errors that others reported.

dustin  snap run vlc
VLC media player 3.0.0 Vetinari (revision 3.0.0-0-gef4c265)
[0000000001e943b0] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface.
Gtk-Message: Failed to load module "gail"
Gtk-Message: Failed to load module "atk-bridge"
Gtk-Message: Failed to load module "canberra-gtk-module"
Qt: Session management error: None of the authentication protocols specified are supported

I’ve just reported upstream the issue causing the indicator-icon not to work properly:


upnp (eg playing from DLNA servers) does not work (View/Playlist/Local Network/Universal Plug ‘n’ Play):

[00007f27ac619a80] upnp services discovery: Initializing libupnp on 'default' interface
[00007f27ac619a80] upnp services discovery error: Initialization failed: UPNP_E_SOCKET_BIND
[00007f27ac619a80] main services discovery error: no suitable services discovery module

I’ve read that this may be caused by: It seems like vlc could either build a working upnp as part of the snap or maybe build a working deb, put it in a ppa, and stage-packages that deb.

1 Like