Assigning to maintainer Shlomi Fish and adding some other packagers in CC.

CC: (none) => cjw, lists.jjorge, yann.cantin
Assignee: bugsquad => shlomif

I can reproduce this problem on my x86-64 Acer Laptop running MGA5 x86-64, so I set the architecture as "All". Now I am going to try the same with a vanilla VLC-2.2.x built from source without patching and if it exists there too - I'll report it upstream.

Hardware: i586 => All

(In reply to Shlomi Fish from comment #2)
> I can reproduce this problem on my x86-64 Acer Laptop running MGA5 x86-64,
> so I set the architecture as "All". Now I am going to try the same with a
> vanilla VLC-2.2.x built from source without patching and if it exists there
> too - I'll report it upstream.

It also happens there with vlc-2.2.x from the vlc-2.2 git master built from source and install under ~/apps/vlc-2.2/ . I'm going to report it upstream .

Reported upstream here - https://trac.videolan.org/vlc/ticket/15665 .

URL: (none) => https://trac.videolan.org/vlc/ticket/15665

(In reply to Shlomi Fish from comment #4)
> Reported upstream here - https://trac.videolan.org/vlc/ticket/15665 .

OK, the upstream report was closed as incomplete and I was told to follow the bug reporting rules (probably these - https://wiki.videolan.org/Report_bugs/ ). Original reporter ( Jan Kulhanek ) : can you file a new report there while following the rules in question? This bug does not personally bother me and there's a limit to how much I wish to help.

(In reply to Shlomi Fish from comment #5)
> (In reply to Shlomi Fish from comment #4)
> > Reported upstream here - https://trac.videolan.org/vlc/ticket/15665 .
> 
> OK, the upstream report was closed as incomplete and I was told to follow
> the bug reporting rules (probably these -
> https://wiki.videolan.org/Report_bugs/ ). Original reporter ( Jan Kulhanek )
> : can you file a new report there while following the rules in question?
> This bug does not personally bother me and there's a limit to how much I
> wish to help.

Jan Kulhanek - ping! Please reply.

I have to ask again for excuse, I unfortunately commented initially to the wrong bug: 16519

My comments from there actually was related to the issue within XFCE and lid close, so to this bug here (16893).

Below my last comment:

Hello,

I am sorry for the bad english I used.
I am not yet used to reporting bugs to community bug trackers.

In the meanwhile I compiled a Nightly build of VLC 2.2.2 (vlc-2.2.0-20151014-0039) and tested the lid-close-and-resume issue and was not able to reproduce it with that version.
Afterwards I compiled the latest official released version of VLC as offered on there page (vlc-2.2.1).
Strangely I was not able to reproduce the issue with that version either.
I then rechecked with the mageia version (installed the package) and was able to reproduce the issue.
All the tests where done in Mageia 5.

For the versions I compiled myself I used the following flasg as I ran ./configure:
./configure --disable-avcodec --disable-swscale --disable-libgcrypt --enable-skins2


During the startup of the versions I compiled the following messages showed up in the terminal (they don't appear when using the mageia vlc package):

[jan@localhost .config]$ /usr/local/bin/vlc
VLC media player 2.2.1 Terry Pratchett (Weatherwax) (revision 2.2.1-0-ga425c42)
[08c529b8] core interface error: no suitable interface module
[08bc7928] core libvlc error: interface "globalhotkeys,none" initialization failed
[08bc7928] core libvlc: VLC wird mit dem Standard-Interface ausgeführt. Benutzen Sie 'cvlc', um VLC ohne Interface zu verwenden.
Unable to load library icui18n "Cannot load library icui18n: (icui18n: Kann die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden)" 

(vlc:31546): Gtk-WARNING **: /usr/local/lib/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /usr/lib/gtk-2.0/2.10.0/engines/liboxygen-gtk.so)


So what I did was:

- used Mageia 5
- deinstalled the vlc Mageia package
- compiled Nightly Build of vlc 2.2.2 (vlc-2.2.0-20151014-0039)
- ./configure has been run --disable-avcodec --disable-swscale --disable-libgcrypt --enable-skins2
- started vlc from terminal by calling /usr/local/bin/vlc
- closed the lid (suspend to ram)
- opened the lid (resume)
- vlc didn't crashed
- repeated that 2 times with the same result

- compiled latest official release of vlc (2.2.1)
- ./configure has been run --disable-avcodec --disable-swscale --disable-libgcrypt --enable-skins2
- started vlc from terminal by calling /usr/local/bin/vlc
- checked in the helpmenu that it shows 2.2.1
- closed the lid (suspend to ram)
- opened the lid (resume)
- vlc was still running
- repeated that 2 times

- installed mageia vlc package
- started vlc from terminal by calling /usr/bin/vlc
- closed the lid
- opened the lid (resume)
- vlc had crashed

The test from above was not clean, since the files of the tests with vlc 2.2.2 nightly where not removed, but just overwritten as I did "make install" for the test with the vlc version 2.2.1.
So I could not say definitively that there where no remains of vlc 2.2.2 as I tested 2.2.1 influencing the test.
Unfortunately I don't have the equipment currently to create a clean installation between the tests.
So it would be good if someone could repeat the test with the vlc 2.2.1 version.

Also I assume the options past to ./configure and maybe the compiler option used at the time the mageia vlc version has been build where different to mine.

I posted the information for the case somebody with more knowledge may be able to find the reason why the Mageia 5 vlc version crashes, while the same version compiled by me does not.
Maybe there is a easy way to find a solution, such as a ./configure option or something similar.

Thanks for the time.

Your next response within the other Bug was:

OK. Some notes:

1. Did you install all the --buildrequires of the Mageia VLC SRPM first?

2. Why did you add the --disable flags to configure?

3. The lid-close/open bug is tracked in a different bug.

4. You can use the --prefix flag to ./configure to install VLC under a certain path prefix instead of cluttering /usr/local .

Regards,

-- Shlomi



Answer:

1. No, I used the source from VLC website, I didn't compiled the Source RPM. 
However I assume --buildrequires is some parameter for something (urpmi?) - could you please explain little more.

2. Because ./configure was complaining about that it was not able to find the dev libraries required to compile with avcodec and and swscale and I was not able to find them in the repositories.

3. Correct, I posted by accident within the wrong Bug

4. O.K. I will try that and report back whether this changes something at the results

Hi Jan,

you can reply to each item separately by hitting the [reply] button/link and using it in interim.

(In reply to Jan Kulhanek from comment #8)
> Your next response within the other Bug was:
> 
> OK. Some notes:
> 
> 1. Did you install all the --buildrequires of the Mageia VLC SRPM first?
> 
> 2. Why did you add the --disable flags to configure?
> 
> 3. The lid-close/open bug is tracked in a different bug.
> 
> 4. You can use the --prefix flag to ./configure to install VLC under a
> certain path prefix instead of cluttering /usr/local .
> 
> Regards,
> 
> -- Shlomi
> 
> 
> 
> Answer:
> 
> 1. No, I used the source from VLC website, I didn't compiled the Source RPM. 
> However I assume --buildrequires is some parameter for something (urpmi?) -
> could you please explain little more.

You can use «urpmi --buildrequires /path/to/my.src.rpm» or «urpmi --buildrequires /path/to/my.spec» to install the necessary build-requires for a source package. For more information, see the urpmi documentation.

As a result, you were probably missing some of the libraries that VLC compiles against on Mageia, and as a result it was not feature-complete. Please install them before building VLC from source, even if you're using the source from the VLC web site.

> 
> 2. Because ./configure was complaining about that it was not able to find
> the dev libraries required to compile with avcodec and and swscale and I was
> not able to find them in the repositories.

Ah, so you were probably lacking some packages . Please follow my instructions reqarding  --buildrequires above.

> 
> 3. Correct, I posted by accident within the wrong Bug
> 

I see.

> 4. O.K. I will try that and report back whether this changes something at
> the results

Also use --buildrequires.

I experienced a crash if vlc is playing a video while xrandr add a screen. Maybe the suspend triggers the same bug?

Setting bug as ASSIGNED - Jan - please comply with my requests.

Status: NEW => ASSIGNED

Hi Jan,

Thank you for having taken the needed time to report this issue!

We regret if we weren't able to fix this issue in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues.

If the bug still exists in Mageia 6, then please do what Shlomi asked you to do in comment #5 
> (In reply to Shlomi Fish from comment #4)
> > Reported upstream here - https://trac.videolan.org/vlc/ticket/15665 .
> 
> OK, the upstream report was closed as incomplete and I was told to follow
> the bug reporting rules (probably these -
> https://wiki.videolan.org/Report_bugs/ ). Original reporter ( Jan Kulhanek )
> : can you file a new report there while following the rules in question?

And then:
* give a link to that new upstream report in a new comment here
* change the Version (near the top of this report, at the left) to "6" and 
* change the Status (at the bottom left) to "REOPENED"

Thanks,
Marja

Status: ASSIGNED => RESOLVED
CC: (none) => marja11
Resolution: (none) => OLD