| Summary: | PNG snapshot feature is corrupted | ||
|---|---|---|---|
| Product: | Fedora | Reporter: | Sander Salazar <sstsalazar> |
| Component: | vlc | Assignee: | Nicolas Chauvet <kwizart> |
| Status: | RESOLVED EXPIRED | ||
| Severity: | normal | CC: | jlp1981, MeSat, nucleo |
| Priority: | P5 | ||
| Version: | 19 | ||
| Hardware: | x86_64 | ||
| OS: | GNU/Linux | ||
| namespace: | |||
| Attachments: | changes in libpng-devel | ||
|
Description
Sander Salazar
2012-12-08 13:12:23 CET
I confirm problem both with vlc-2.0.4 and 2.0.5 in F18. Produced PNG files filled with zeros. No problem in F17. Probably something related to newer libpng support ? F17 have libpng-1.5.10, F18 - libpng-1.5.13, looks like minor release that should not much differ from 1.5.10. Changelog libpng-1.5.13-1.fc18 * Thu Sep 27 2012 Tom Lane <tgl@redhat.com> 2:1.5.13-1 - Update to libpng 1.5.13 for minor bug fixes * Sat Aug 04 2012 Tom Lane <tgl@redhat.com> 2:1.5.12-1 - Update to libpng 1.5.12 for minor bug fixes - Activate chunk size limits by default, with a very generous default limit * Wed Aug 01 2012 Tom Lane <tgl@redhat.com> 2:1.5.10-3 - Remove compat subpackage (it's now a separate package "libpng12") - Minor specfile cleanup per suggestions from Tom Callaway Related: #845110 The same corrupted snapshot after I downgraded libpng in F18 to libpng-1.5.10-1.fc17.i686. libpng-1.5.13 also in Rawhide but snapshots are fine in vlc-2.0.4-3.fc19. Created attachment 1013 [details]
changes in libpng-devel
In 1.5.13 was some changes in libpng-devel headers but I don't know how essential.
Can you reproduce with vlc-2.0.6 from rpmfusion-free-updates-testing vlc-2.0.6 still makes corrupted png screenshots with zeros. With F18 with updates-testing, rpmfusion-free-updates-testing, rpmfusion-nonfree-updates-testing enabled, using vlc-2.0.6 and 1.5.13-1, I am currently not able to reproduce the error. I am also seeing this bug on F19 with VLC 2.0.6 and libpng-1.5.13-2. PNG screenshots still contains from zeros in Fedora 19, vlc-2.0.6-1.fc19.i686, libpng-1.5.13-2.fc19.i686. When the same vlc version running on F19 live image PNG screenshots created correctly, but on my installed F19 system they broken. Maybe some conflicts with other installed packages or missing package in installed system? This looks like the same issue in the upstream bug tracker: https://trac.videolan.org/vlc/ticket/8544 Still occurring with VLC VLC media player 2.0.8 Twoflower (revision 2.0.7-29-g12aebf9) and libpng-1.5.13-2.fc19.x86_64 libpng-1.5.13-2.fc19.x86_64 This is the current open bug. Not sure if VLC 2.1 fixes the problem yet and waiting to see if it it answered in this bug. VLC 2.1 has been released in September. https://trac.videolan.org/vlc/ticket/8403 This bug, https://trac.videolan.org/vlc/ticket/8544 was marked fixed and closed Date: Tue May 28 11:29:07 2013 +0200. hexdump SomeVideo.avi_00001.png 0000000 0000 0000 0000 0000 0000 0000 0000 0000 * 00e10c0 0000 0000 0000 0000 00e10c8 Still an issue in vlc-2.0.9-1.fc19.x86_64. The comment I have read that it is related to multi-threading or is that Windows only? Until the fix is done, can the quality of JPG captures be improved? I cannot find an option to do this. Have not updated to FC20 on any computer yet to test. In F20 PNG screenshots looks fine for me with vlc-2.1.2-1.fc20.i686. In comment 15, I said that 2.1 was released in September and that it looked like the problem was fixed upstream. F19 is still active but the latest version is vlc-2.0.9-1.fc19.x86_64. So four months later, not available for F19. Is there a good reason that F19 cannot get 2.1.X? An answer would be nice to see. I keep checking the update testing. I plan on testing Fedup soon to see how well it works. Last update was 2013-11-06. Well, it is now June and the problem is still in VLC. If it wasn't for conflicts, I would use ATRPMS to get a working VLC. I posted my last comment in January. Latest version is 2.1.3 on the VLC web site. I don't know why this is still marked as new either being over two years old. RPMFusion is no longer releasing updates for this version of Fedora. This bug will be set to RESOLVED:EXPIRED next week to reflect this. If the problem persists after upgrading to the latest version of Fedora, please update the version field of this bug (and re-open it if it has been closed). Setting to RESOLVED:EXPIRED since RPMFusion is no longer releasing updates for this version of Fedora. |