I suppose the error comes from GStreamer. There is something wrong with libav.

Here is the (relevant) debugging output of GStreamer (GST_DEBUG=*:LOG):

0:00:02.676333219 24856 0x7fad6c002850 LOG                    libav 
gstavcodecmap.c:747:gst_ffmpeg_codecid_to_caps: codec_id:28, context:(nil), 
encode:1
0:00:02.676341292 24856 0x7fad6c002850 LOG                    libav 
gstavcodecmap.c:277:gst_ff_vid_caps_new: context:(nil), codec_id:28, 
mimetype:video/x-h264
0:00:02.676353238 24856 0x7fad6c002850 LOG                    libav 
gstavcodecmap.c:2184:gst_ffmpeg_codecid_to_caps: caps for codec_id=28: 
video/x-h264, alignment=(string)au
0:00:02.676363757 24856 0x7fad6c002850 LOG                    libav 
gstavcodecmap.c:2333:gst_ffmpeg_codectype_to_video_caps: context:(nil), 
codec_id:28, encode:1, codec:0x7fad6b8b5d00
0:00:02.676377510 24856 0x7fad6c002850 LOG                    libav 
gstavcodecmap.c:277:gst_ff_vid_caps_new: context:(nil), codec_id:28, 
mimetype:video/x-raw
0:00:02.676388714 24856 0x7fad6c002850 DEBUG                  libav 
gstavcodecmap.c:2634:gst_ffmpeg_pixfmt_to_videoformat: Unknown pixel format 53
0:00:02.676545307 24856 0x7fad6c002850 ERROR                  libav :0:: 
Invalid chars '.0' at the end of expression '1.0'
0:00:02.676554253 24856 0x7fad6c002850 ERROR                  libav :0:: Unable 
to parse option value "1.0"
0:00:02.676561254 24856 0x7fad6c002850 INFO                   libav :0:: 
Assertion ret >= 0 failed at src/libavcodec/options.c:142
+++Aborted+++

And yes, libav was updated a day before...

----
libav-tools (7:3.0.2-4) to 7:3.1.1-3
libavcodec-dev (7:3.0.2-4) to 7:3.1.1-3
libavcodec-extra (7:3.0.2-4) to 7:3.1.1-3
libavcodec-extra57 (7:3.0.2-4) to 7:3.1.1-3
libavdevice57 (7:3.0.2-4) to 7:3.1.1-3
libavfilter6 (7:3.0.2-4) to 7:3.1.1-3
libavformat-dev (7:3.0.2-4) to 7:3.1.1-3
libavformat57 (7:3.0.2-4) to 7:3.1.1-3
libavresample3 (7:3.0.2-4) to 7:3.1.1-3
libavutil-dev (7:3.0.2-4) to 7:3.1.1-3
libavutil55 (7:3.0.2-4) to 7:3.1.1-3
----


Elías Alejandro schrieb:
> uh... experimental?
> 
> I have this:
> $apt-cache policy python
> python:
>   Installed: 2.7.11-2
> 
> $python -V
> Python 2.7.12
> 
> I have all these packages with unstable.
> 
> i python-apt
>  1.1.0~beta4
> i python-apt-common
> 1.1.0~beta4
> i python-cryptography                                             1.4-2
> 
> i python-debianbts                                                2.6.1
> 
> i python-dnspython                                                1.14.0-3
> 
> i python-enum34                                                   1.1.6-1
> 
> i python-libxml2
>  2.9.4+dfsg1-1
> i python-louis                                                    2.6.5-1
> 
> i python-mutagen                                                  1.33.2-1
> 
> i python-openssl                                                  16.0.0-2
> 
> i python-utidylib                                                 0.3-1
> 
> i python-webob                                                    1.6.1-1
> 
> p python3-apt
> 1.1.0~beta4
> p python3-louis                                                   2.6.5-1
> 
> p python3-pyatspi
> 2.20.2+dfsg-1
> 
> and I have no problems with radiotray. Did you upgrade any other package?
> 
> Regards,
> 
> Elías Alejandro
> 
> On Thu, Jul 28, 2016 at 11:46 PM, Jens Schmidt <crashd...@meine-dateien.info
>> wrote:
> 
>> Python version is latest version of Debian stretch/experimental.
>>
>> python2.7: 2.7.12-1
>> python3:   3.5.1-4
>>
>> Update was:
>>
>> python-apt (1.1.0~beta3) to 1.1.0~beta4
>> python-apt-common (1.1.0~beta3) to 1.1.0~beta4
>> python-cryptography (1.4-1) to 1.4-2
>> python-debianbts (2.6.0) to 2.6.1
>> python-dnspython (1.14.0-2) to 1.14.0-3
>> python-enum34 (1.1.5-1) to 1.1.6-1
>> python-libxml2 (2.9.3+dfsg1-1.2) to 2.9.4+dfsg1-1
>> python-louis (2.6.4-2) to 2.6.5-1
>> python-mutagen (1.33.1-1) to 1.33.2-1
>> python-openssl (16.0.0-1) to 16.0.0-2
>> python-utidylib (0.2-9) to 0.3-1
>> python-webob (1.6.0-1) to 1.6.1-1
>> python3-apt (1.1.0~beta3) to 1.1.0~beta4
>> python3-louis (2.6.4-2) to 2.6.5-1
>> python3-pyatspi (2.20.1+dfsg-1) to 2.20.2+dfsg-1
>>
>>
>>
>>
>>
>> Elías Alejandro schrieb:
>>> Hello Jens,
>>> Thanks for your report. Could you please send me your python version?
>>>
>>>
>>> Thanks.
>>> Elías Alejandro
>>>
>>> On Wed, Jul 27, 2016 at 3:39 AM, Jens Schmidt
>>> <crashd...@meine-dateien.info> wrote:
>>>> Package: radiotray
>>>> Version: 0.7.3-6
>>>> Severity: normal
>>>>
>>>> Dear Maintainer,
>>>>
>>>> radiotray didn't play any stream since some days. radiotray worked for
>> years,
>>>> but since latest Python update it crashes when I tray to play a stream.
>> I did
>>>> not change anything within my config which worked for years.
>>>>
>>>> The only error message is: "Aborted". Not very helpful..
>>>>
>>>>
>>>>
>>>>
>>>> -- System Information:
>>>> Debian Release: stretch/sid
>>>>   APT prefers testing
>>>>   APT policy: (500, 'testing')
>>>> Architecture: amd64 (x86_64)
>>>> Foreign Architectures: i386
>>>>
>>>> Kernel: Linux 4.2.6-bulldozer (SMP w/4 CPU cores)
>>>> Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
>>>> Shell: /bin/sh linked to /bin/dash
>>>> Init: systemd (via /run/systemd/system)
>>>>
>>>> Versions of packages radiotray depends on:
>>>> ii  gir1.2-gtk-3.0             3.20.6-2
>>>> ii  gir1.2-keybinder-3.0       0.3.1-1
>>>> ii  gir1.2-notify-0.7          0.7.6-2
>>>> ii  gstreamer1.0-plugins-bad   1.8.2-1+b1
>>>> ii  gstreamer1.0-plugins-base  1.8.2-1
>>>> ii  gstreamer1.0-plugins-good  1.8.2-1
>>>> ii  gstreamer1.0-plugins-ugly  1.8.2-1
>>>> ii  python-dbus                1.2.4-1
>>>> ii  python-gi                  3.20.1-1
>>>> ii  python-glade2              2.24.0-4
>>>> ii  python-gst-1.0             1.8.2-1
>>>> ii  python-lxml                3.6.0-1
>>>> ii  python-xdg                 0.25-4
>>>> pn  python:any                 <none>
>>>>
>>>> radiotray recommends no packages.
>>>>
>>>> radiotray suggests no packages.
>>>>
>>>> -- no debconf information
>>
>>
> 

Reply via email to