Has anyone else noticed VLC on Linux getting wonkier over the past year? Its gotten bad enough I started using the default media apps under Pop, Mint, and Ubuntu, instead of it. #vlc #linux
I even built a whole new VM in case it had gone wonky. Similar problems. It may be something that’s gone off with VirtualBox but Celluloid isn’t having these problems.
While playing a playlist, keep hitting the next video button pretty quickly (trying to find that one video) and it will crash after putting up a dialog box telling you something has gone wrong.
Celluloid (Linux Mint, probably elsewhere too) is just a front-end to mpv with too much real-estate on-screen and paltry options. SMPlayer as a front-end for mpv is to me far superior.
Only VLC uses xspf playlists. Much better to use m3u / m3u8. There are no good utilities to create xspf files. Best is to fill VLC queue, then save as xspf playlist. Not necessary to play the playlist.
When I first became interested in GNU/Linux back in 2006, I multi-booted about 18 of the mainline distributions (Debian, Slackware, SuSE, Mandriva, Fedora, CentOS, etc.) on my system. I wanted to learn the ins and outs of each distribution so I could make an informed decision on what to use as my primary operating system.
I settled on Slackware relatively quickly because I loved its simplicity and its legendary stability. I've been a slacker ever since. I never looked back. It has served me very well for nearly 20 years now.
Oh, and when I say "simplicity" above, I mean it in the UNIX way... K I S S -> keep it simple, stupid. Slackware is not an "easy" distribution to learn to install and use. I do not recommend it to folks new to GNU/Linux. You have to take your time and commit yourself to learning Slackware. It's definitely NOT a simple point and click type operating system like MS Windows or Ubuntu Linux.
There's an old saying that if you just want to play around with GNU/Linux, install Ubuntu; however, if you really want to learn GNU/Linux, install Sla
... show more
When I first became interested in GNU/Linux back in 2006, I multi-booted about 18 of the mainline distributions (Debian, Slackware, SuSE, Mandriva, Fedora, CentOS, etc.) on my system. I wanted to learn the ins and outs of each distribution so I could make an informed decision on what to use as my primary operating system.
I settled on Slackware relatively quickly because I loved its simplicity and its legendary stability. I've been a slacker ever since. I never looked back. It has served me very well for nearly 20 years now.
Oh, and when I say "simplicity" above, I mean it in the UNIX way... K I S S -> keep it simple, stupid. Slackware is not an "easy" distribution to learn to install and use. I do not recommend it to folks new to GNU/Linux. You have to take your time and commit yourself to learning Slackware. It's definitely NOT a simple point and click type operating system like MS Windows or Ubuntu Linux.
There's an old saying that if you just want to play around with GNU/Linux, install Ubuntu; however, if you really want to learn GNU/Linux, install Slackware. There's a lot of truth in that saying... you cannot help but learn GNU/Linux if you run Slackware for any length of time.
All fun stuff! I'm not nearly as active or "techie" as I used to be years ago, though. Nowadays, I'm old and happy if the damned thing works when I push the power button. ;)
Yes I did, ten years ago. 90% of my hardware is cheap and underpowered, I learned to use the right tools with lesser impact on the performance, VLC doesn't belong to them.
Instead I warmly recommend #MPV and only it, any other player based on it belongs to the bloated group.
Slackware community is very in to knowing the system top to bottom. I'm in the middle. I use a portable ssd bootable Linux Mint with two NTFS partitions in my volunteer secretary role. So yep it's great to be able to keep delving in to the system but for me its more a question of not stuffing up the system ;- On the desktop I can try anything with no responsibility !
Gettng back to VLC, it is open source you can examine how it works and compile it yourself. And if there were any dodgy stuff somebody would point that out.
As a professional software developer, open source contributer to several projects, and even someone who has done their own FOSS projects, I'm going to say absolutely not. This is not an area I have much expertise in. To get up to speed on that, this particular code base, etc. would be a monumental effort. It was hard enough debugging front end wrapper library in Flutter that I use which was way more in my wheel house. Most I'd do is add a bug to the bug tracker if there was a repeatable actionable specific bug that I find. General "this seems more unstable" is not going to be helpful to them through that vector.
The point of my comment was that the tools are there to verify the integrity of the VLC product. That a given person is averse to using these tools due to perceived or actual inability does not invalidate the point. In a world where, as Paul Simon lyricised "Paranoia strikes deep in the Heartland", this particular fear that VLC presents a danger to a User can be dispelled.
Are you saying VLC is not a danger in terms of security? On the contrary. It is an attack surface in itself and the truth is that those gstreamer and codec packages required for playing media are well known for to be exploitable. This may go to other players as well. It is how it is... Zero days and vulnerabilities are crucial for a certain industry and for certain organizations. Some of them just happen, some of them are made to be happen. They can be worth millions of $US in some cases. The more popular a software is, the better to have it backdoored (three letters folks attitude) - it's been like that for a while.
I ask you to detail even ONE backdoor in VLC and then do the right thing - advise the developers. Just ONE. And I don't mean 'assert', I mean DETAIL. - Thanks. Incidentally Zero Day Vulnerabilities generally arise out of malformed (badly formed) code, and can be a nefarious plant, or can be as a result of a coding flaw, such as buffer-overruns, in a compiled-in library. The point is that the FOSS code can be independently compiled and tested, which is precisely what security research is about. FOSS is no guarantee of flaw-free code, but is a guarantee that the code can be vetted. This holds true for VLC.
Yes, it's a good thing to have FOSS code instead of proprietary products. However, unfortunately, there always have been issues with VLC in the past - dozens of articles (older and newer ones) turn up when searching for VLC and security vulnerability. This indicates (if we do not look at it in a naive way) that it won't be different in the future (affecting the software that we may use right now). But it's not only about VLC. Even Chrome had eight zero days discovered last year. Still, I cannot name a more secure browser than Chromium (preferably Ungoogled).
If there were no alternatives, and if the code was not being corrected, THAT would be sad. If you update your system according to a sensible schedule, the fixes are available, depending on your version of desktop, in a very timely manner. It is up to you to pick that desktop, and to keep it updated by applying security fixes automatically.
David
in reply to Hank G ☑️ • • •Hank G ☑️ likes this.
korvroffe
in reply to Hank G ☑️ • • •Hank G ☑️ likes this.
hummingbird
in reply to Hank G ☑️ • • •Ilkka
in reply to Hank G ☑️ • • •Hank G ☑️
in reply to Ilkka • •Ilkka
in reply to Hank G ☑️ • • •Ilkka
in reply to Ilkka • • •Just uninstalled the dev-build and installed #vlc 3.0.20.
Video playback worked ok with wayland environment and pipewire audio system with opengl video output.
You could try with '--reset-config' in case there is some funky config that goes sideways?
Hank G ☑️
in reply to Ilkka • •Ilkka
in reply to Hank G ☑️ • • •Hank G ☑️
in reply to Ilkka • •David
in reply to Hank G ☑️ • • •Hank G ☑️ likes this.
hummingbird
in reply to Hank G ☑️ • • •hummingbird
in reply to Hank G ☑️ • • •hummingbird
in reply to Hank G ☑️ • • •V. T. Eric Layton
in reply to Hank G ☑️ • • •Hank G ☑️ likes this.
hummingbird
in reply to Hank G ☑️ • • •V. T. Eric Layton
in reply to Hank G ☑️ • • •When I first became interested in GNU/Linux back in 2006, I multi-booted about 18 of the mainline distributions (Debian, Slackware, SuSE, Mandriva, Fedora, CentOS, etc.) on my system. I wanted to learn the ins and outs of each distribution so I could make an informed decision on what to use as my primary operating system.
I settled on Slackware relatively quickly because I loved its simplicity and its legendary stability. I've been a slacker ever since. I never looked back. It has served me very well for nearly 20 years now.
Oh, and when I say "simplicity" above, I mean it in the UNIX way... K I S S -> keep it simple, stupid. Slackware is not an "easy" distribution to learn to install and use. I do not recommend it to folks new to GNU/Linux. You have to take your time and commit yourself to learning Slackware. It's definitely NOT a simple point and click type operating system like MS Windows or Ubuntu Linux.
There's an old saying that if you just want to play around with GNU/Linux, install Ubuntu; however, if you really want to learn GNU/Linux, install Sla
... show moreWhen I first became interested in GNU/Linux back in 2006, I multi-booted about 18 of the mainline distributions (Debian, Slackware, SuSE, Mandriva, Fedora, CentOS, etc.) on my system. I wanted to learn the ins and outs of each distribution so I could make an informed decision on what to use as my primary operating system.
I settled on Slackware relatively quickly because I loved its simplicity and its legendary stability. I've been a slacker ever since. I never looked back. It has served me very well for nearly 20 years now.
Oh, and when I say "simplicity" above, I mean it in the UNIX way... K I S S -> keep it simple, stupid. Slackware is not an "easy" distribution to learn to install and use. I do not recommend it to folks new to GNU/Linux. You have to take your time and commit yourself to learning Slackware. It's definitely NOT a simple point and click type operating system like MS Windows or Ubuntu Linux.
There's an old saying that if you just want to play around with GNU/Linux, install Ubuntu; however, if you really want to learn GNU/Linux, install Slackware. There's a lot of truth in that saying... you cannot help but learn GNU/Linux if you run Slackware for any length of time.
This also got me quite active in the Slackware communities at LinuxQuestions.org, Scot's Newsletter Forums (where I'm an Admin), and The Slackware Documentation Project (where I'm a senior editor).
All fun stuff! I'm not nearly as active or "techie" as I used to be years ago, though. Nowadays, I'm old and happy if the damned thing works when I push the power button. ;)
start - SlackDocs
docs.slackware.comharry haller
in reply to Hank G ☑️ • • •That's it exactly - simple, not easy, but the documentation is quite clear.
V. T. Eric Layton
in reply to Hank G ☑️ • • •gunnar
in reply to Hank G ☑️ • • •❄️ freezr ❄️
in reply to Hank G ☑️ • • •Yes I did, ten years ago.
90% of my hardware is cheap and underpowered, I learned to use the right tools with lesser impact on the performance, VLC doesn't belong to them.
Instead I warmly recommend #MPV and only it, any other player based on it belongs to the bloated group.
hummingbird
in reply to Hank G ☑️ • • •hummingbird
in reply to Hank G ☑️ • • •Hank G ☑️
in reply to hummingbird • •hummingbird
in reply to Hank G ☑️ • • •gunnar
in reply to Hank G ☑️ • • •It is how it is... Zero days and vulnerabilities are crucial for a certain industry and for certain organizations. Some of them just happen, some of them are made to be happen. They can be worth millions of $US in some cases. The more popular a software is, the better to have it backdoored (three letters folks attitude) - it's been like that for a while.
hummingbird
in reply to Hank G ☑️ • • •hummingbird
in reply to Hank G ☑️ • • •gunnar
in reply to Hank G ☑️ • • •hummingbird
in reply to Hank G ☑️ • • •hummingbird
in reply to Hank G ☑️ • • •