Bug 20248

Summary: VLC segfaults on startup
Product: Mageia Reporter: Doug Laidlaw <laidlaws>
Component: RPM PackagesAssignee: José Jorge <lists.jjorge>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: Normal CC: curtis_mageia, lists.jjorge, tarazed25
Version: Cauldron   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: vlc-2.2.4-9.mga6 CVE:
Status comment:

Description Doug Laidlaw 2017-02-06 06:47:44 CET
Description of problem:

When started, VLC segfaults immediately.  From dmesg:

vlc[12936]: segfault at 7f3c6ab0c220 ip 00007f3c69e80042 sp 00007ffcce6e3530 error 6 in libGL.so.375.26[7f3c69dd0000+c9000]

This seems to have been an issue in 2014 and earlier, related to proprietary nVidia drivers, e.g. 

https://bbs.archlinux.org/viewtopic.php?id=151935

I am running a GeForce 750 card.

I tried the fix mentioned there:

/usr/lib/vlc/vlc-cache-gen -f usr/lib/vlc/plugins

and got reply that the file didn't exist.
José Jorge 2017-02-06 10:43:01 CET

CC: (none) => lists.jjorge
Assignee: bugsquad => lists.jjorge

Comment 1 José Jorge 2017-02-06 10:44:10 CET
Can you please test with vlc 3.0.0 from updates_testing?

Status: NEW => ASSIGNED

Comment 2 Doug Laidlaw 2017-02-06 11:07:18 CET
Sorry, it is no different.  I did a normal update with updates-testing enabled.  It seemed to replace all packages.  Cauldron doesn't have a user config file I can remove.
Comment 3 Len Lawrence 2017-02-12 15:44:27 CET
x86_64, nvidia GTX970
There is a fault with vlc when installed from GNOME after installation of the latest GNOME Live iso.  It may be associated with his bug.

vlc segfaults on the command line invoked using e.g.
$ vlc cpr.mov
and this occurs with both free and tainted versions.

The vlc installation included svlc and ended with a scriptlet error; extract:

/var/tmp/rpm-tmp.gGcX0e: line 3:
11342 Segmentation fault
/usr/lib64/vlc/vlc-cache-gen -f /usr/lib64/vlc/plugins
warning: %triggerin(vlc-2.2.4-9.mga6.x86_64)
scriptlet failed .... error status 139
'script' failed for svlc-2.2.4-9....

dmesg indicates that the segfault occurs in libGL.

I tried removing vlc and svlc and reinstalling vlc without svlc; scriptlet failed again but this time at plugin-theora.

$ ls /usr/lib64/vlc
lua/  plugins/  vlc-cache-gen* 
$ ls /usr/lib64/vlc/plugins
access/         codec/    meta_engine/         stream_filter/  video_output/
access_output/  control/  misc/                stream_out/     video_splitter/
audio_filter/   demux/    mux/                 text_renderer/  visualization/
audio_mixer/    gui/      packetizer/          video_chroma/

CC: (none) => tarazed25

Comment 4 Len Lawrence 2017-02-12 16:10:33 CET
Installed vlc-3.0 from tainted updates testing without any errors.
vlc still segfaults but without any additional information.  The last line of dmesg contains the only reference to vlc:
[ 2397.573934] vlc[7304]: segfault at 7f0d3fec3220 ip 00007f0d3de8e042 sp 00007ffc4593e2d0 error 7 in libGL.so.375.26[7f0d3ddde000+c9000]

The boot journal has no references to vlc.
Running under strace gives this:

close(3)                                = 0
munmap(0x7f74e4b97000, 4096)            = 0
write(2, "[\33[32;1m0000000001d56188\33[0m] ", 30[0000000001d56188] ) = 30
write(2, "core libvlc error: \33[31;1m", 26core libvlc error: ) = 26
write(2, "No plugins found! Check your VLC"..., 46No plugins found! Check your VLC installation.) = 46
write(2, "\33[0m\n", 5
)                 = 5
Comment 5 Len Lawrence 2017-02-12 16:17:58 CET
Also, there is world read and execute permissions on all the files in the /usr/lib64/vlc hierarchy.
Comment 6 Len Lawrence 2017-02-12 16:35:06 CET
# /usr/lib64/vlc/vlc-cache-gen  /usr/lib64/vlc/plugins
Segmentation fault (core dumped)

dmesg again shows that libGL is involved.
Curtis Hildebrand 2017-02-12 19:34:01 CET

CC: (none) => curtis_mageia

Comment 7 Doug Laidlaw 2017-03-07 08:51:32 CET
Now crashing on 5.1 as well.
Comment 8 José Jorge 2017-03-07 22:16:37 CET
(In reply to Doug Laidlaw from comment #7)
> Now crashing on 5.1 as well.

Huh? What is 5.1? MGA5 updated?
Comment 9 Rémi Verschelde 2017-03-07 22:22:18 CET
(In reply to José Jorge from comment #8)
> (In reply to Doug Laidlaw from comment #7)
> > Now crashing on 5.1 as well.
> 
> Huh? What is 5.1? MGA5 updated?

If that's a genuine question, you need to start following mailing lists and maybe our blog... http://blog.mageia.org/en/2016/12/02/happily-announcing-mageia-5-1/
Comment 10 José Jorge 2017-03-07 22:31:37 CET
(In reply to Rémi Verschelde from comment #9)
> (In reply to José Jorge from comment #8)
> > (In reply to Doug Laidlaw from comment #7)
> > > Now crashing on 5.1 as well.
> > 
> > Huh? What is 5.1? MGA5 updated?
> 
> If that's a genuine question, you need to start following mailing lists and
> maybe our blog...
> http://blog.mageia.org/en/2016/12/02/happily-announcing-mageia-5-1/

Of course it wasn't. But this bug talks about vlc on MGA6, so I am surprised that it now talks about MGA5 and wanted to ensure. I have a MGA5 with proprietery nv 319 here that does not crash at all in vlc...
Comment 11 Doug Laidlaw 2017-03-08 00:49:23 CET
I just reinstalled 5.1 with the current VLC.  VLC won't start.  I assumed that the one in Cauldron had made it to the 5.1 release.  It had the same codename as the release in Cauldron (Whipstick, or something similar.  Whipstick Forest is the name of our local State Forest.)
Comment 12 José Jorge 2017-03-08 09:16:46 CET
(In reply to Doug Laidlaw from comment #11)
> I just reinstalled 5.1 with the current VLC.  VLC won't start.  I assumed
> that the one in Cauldron had made it to the 5.1 release.  It had the same
> codename as the release in Cauldron (Whipstick, or something similar. 
> Whipstick Forest is the name of our local State Forest.)

Did you keep your home directory? I suspect you are not using vlc in it's default settings.
Comment 13 Doug Laidlaw 2017-03-08 10:28:09 CET
Ypou were right.  I renamed .config/vlc, and vlc started normally.  The usual nuisance message "Unable to load extensions module." The RPM is 

vlc-2.2.4-1.mga5.
Comment 14 Len Lawrence 2017-03-08 11:07:30 CET
That nuisance message might go away if you also install svlc (which helps manage skins).
Comment 15 Doug Laidlaw 2017-03-08 11:11:16 CET
I don't know if I would bother.  I rarely use the command line, only the default GUI.  

The VLC release is Weatherwax
Comment 16 José Jorge 2017-03-11 18:44:12 CET
Closing as this is a config problem.

Status: ASSIGNED => RESOLVED
Resolution: (none) => INVALID

Comment 17 Doug Laidlaw 2017-03-11 18:52:44 CET
The issue on 5.1 is a config problem.  Still need to test on sta2.
Comment 18 Doug Laidlaw 2017-03-11 19:01:23 CET
No problem on sta2 either. Running on a clean install of sta2, all on one partition, no existing config directory.  But that is how I normally install Cauldron.

Anyway, no action needed unless it happens again.