It seems that it's a libav bug. If started like $ totem --gst-debug=6
the following output is produced: 0:00:05.212869886 17220 0x7fd284013b70 ERROR libav :0:: Invalid chars '.0' at the end of expression '1.0' 0:00:05.212878563 17220 0x7fd284013b70 ERROR libav :0:: Unable to parse option value "1.0" 0:00:05.212884114 17220 0x7fd284013b70 INFO libav :0:: Assertion ret >= 0 failed at src/libavcodec/options.c:142 The problem seems to be with libav trying to parse "1.0" string as a floating-point number, but current locale is set up to treat comma "," as a decimal-point instead of plain point ".". I don't know where "1.0" string comes from. Victor Nazarov On Mon, Aug 1, 2016 at 2:51 PM, Debian Bug Tracking System < ow...@bugs.debian.org> wrote: > Processing commands for cont...@bugs.debian.org: > > > tags 831039 + moreinfo > Bug #831039 [totem] totem crash on startup, can't start it > Added tag(s) moreinfo. > > thanks > Stopping processing here. > > Please contact me if you need assistance. > -- > 831039: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831039 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > > -- > To unsubscribe, send mail to 831039-unsubscr...@bugs.debian.org. >
