Bug 3460

Summary:	motion appears to have no support for ffmpeg. No video recorded.
Product:	Fedora	Reporter:	Alex <bugzilla>
Component:	motion	Assignee:	Tomasz Torcz <zdzichu>
Status:	RESOLVED EXPIRED
Severity:	major	CC:	sergio
Priority:	P5
Version:	21
Hardware:	i386
OS:	GNU/Linux
namespace:

Description Alex 2014-12-14 11:34:00 CET

This system was updated from F20 32bit to F21 32bit using fedup.
Motion was running great on F20.

The rpm used is  motion-3.3.0.trunkREV557-9.fc21.i686

After the update when motion is run it gives:

[0] [NTC] [ALL] conf_load: Processing thread 0 - config file /etc/motion/motion.conf
[0] [ALR] [ALL] conf_cmdparse: Unknown config option "ffmpeg_output_movies"
[0] [ALR] [ALL] conf_cmdparse: Unknown config option "ffmpeg_output_debug_movies"
[0] [ALR] [ALL] conf_cmdparse: Unknown config option "ffmpeg_timelapse"
[0] [ALR] [ALL] conf_cmdparse: Unknown config option "ffmpeg_timelapse_mode"
[0] [ALR] [ALL] conf_cmdparse: Unknown config option "ffmpeg_bps"
[0] [ALR] [ALL] conf_cmdparse: Unknown config option "ffmpeg_variable_bitrate"
[0] [ALR] [ALL] conf_cmdparse: Unknown config option "ffmpeg_video_codec"
[0] [ALR] [ALL] conf_cmdparse: Unknown config option "ffmpeg_deinterlace"
[0] [ALR] [ALL] conf_cmdparse: Unknown config option "sdl_threadnr"
[0] [ALR] [ALL] conf_cmdparse: Unknown config option "movie_filename"
[0] [ALR] [ALL] conf_cmdparse: Unknown config option "timelapse_filename"
[0] [NTC] [ALL] motion_startup: Motion 3.3.0 Started
[0] [NTC] [ALL] motion_startup: Logging to file (/var/log/motion.log)

In other words it does not recognise any of the ffmpeg related options on motion.conf

It also fails to recognise the sdl option. We know this rpm is compiled without support for sdl, but it seems from this output that it is also lacking ffmpeg support, eventhough in the rpm details it says that ffmpeg-compat was used. ffmpeg-compat and ffmpeg are both installed in the system.

Thank you.

Comment 1 Tomasz Torcz 2014-12-14 12:51:08 CET

Indeed, it seems someone has changed F21 version of package, losing fixes made to F20 version. I will bring both vesion in sync again.

Comment 2 Tomasz Torcz 2014-12-14 16:02:41 CET

New build is here: http://buildsys.rpmfusion.org/plague-results/fedora-21-rpmfusion_free/motion/3.3.0.trunkREV557-10.fc21/

It will take some time until it gets to RPMFusion repositories.

Comment 3 Alex 2014-12-14 18:30:27 CET

Solved!

Thanks very much for the hard work. Trully grateful!

Comment 4 Sérgio Basto 2014-12-20 03:43:59 CET

Hi!, 

http://www.lavrsen.dk/foswiki/bin/view/Motion/DownloadFiles 
announce : motion-3.2.12.tar.gz

and on github we have 117 forks ! 
I foun this one that claims version 3.4.1 

https://github.com/tosiara/motion/commit/6b2a5047ae75cc54b7884e560c92ae71282a8bb4

Meanwhile submit another build for F21 because , last build doesn't build with mirror  problem , now it finish successfully 
will be on rpmfusionfree-updates-testing soon (2 or 3 days most) before you can install from here: 
http://buildsys.rpmfusion.org/plague-results/fedora-21-rpmfusion_free/motion/3.3.0.trunkREV557-10.fc21/

BTW: 
http://www.lavrsen.dk/foswiki/bin/view/Motion is the official page , should we move to 3.2.12 ?
and try build with ffmpeg-devel ? is the best , but if we can't , we have to use  ffmpeg-compat ...

Comment 5 Sérgio Basto 2014-12-20 15:22:46 CET

(In reply to comment #4)
> Hi!, 
> 
> http://www.lavrsen.dk/foswiki/bin/view/Motion/DownloadFiles 
> announce : motion-3.2.12.tar.gz

sorry 
motion-3.2.12 is lower than 3.3.0 

so no updates in road

Comment 6 Sérgio Basto 2014-12-21 13:04:11 CET

Updating info: 
in Motion - Web Home:
These unofficial versions exists that hopefully will soon be merged into the official project

    Git Sackmotion - unofficial fork
    Git Dr. dave - unofficial fork 

git of Mr-Dave have the commits of Sackmotion , so seems to me, we should try 
update motion to : 
https://github.com/Mr-Dave/motion/commits/master  

Unfortunately I don't have much free time for motion and it is not a good time. I prefer dedicate myself, to see if rpmfusion have a new infrastructure .

Comment 7 Tomasz Torcz 2014-12-21 13:15:27 CET

Sergio,

switching to new upstream requires re-review of the package. It would need another developer to find enough time to go through .spec file.
This is unlikely.

Comment 8 Emmanuel Seyman 2015-12-04 13:48:44 CET

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).

Comment 9 Emmanuel Seyman 2015-12-13 11:12:53 CET

Closing this bug with the EXPIRED resolution since Fedora no longer ships updates for this version of Fedora.

Please set the Version field to a supported version of Fedora if you re-open this bug.