Ubuntu
motion package

Hardy installation configuration starts capturing

Bug #235599 reported by Mihai Militaru
4
Affects Status Importance Assigned to Milestone
motion (Ubuntu)
New
Undecided
Unassigned

Bug Description

After the installation of the motion package on Ubuntu Hardy, the configuration process starts capturing with the default settings in /etc/motion/... . It looks like it never stops until Ctrl+C 'ed.
Besides, the installer enables motion as a boot starting program, being started by /etc/init.d/motion, beginning to capture at every boot as the root user. This is abnormal, pretty annoying and probably a bug.
To reproduce the bug, a webcam is probably needed.
System:
X/Ubuntu 8.04 - amd64, Acer Aspire 5520G laptop with CrystalEye (v4l2) camera.

Revision history for this message
nine (niin-deactivatedaccount-deactivatedaccount) wrote :

This is probably the same as #198292

Revision history for this message
Mihai Militaru (mihai.militaru) wrote :

Yes, it is. What about the second part, should I fill another report?

Revision history for this message
Rog (roger-mindsocket) wrote :

Halting the upgrade is one thing, introducing a security/privacy problem by starting a motion server on startup/install without telling the user is another.

Specifically in my case, I already had motion set up to record on a schedule in Gutsy. Suddenly after upgrade to Hardy, motion started capturing video frames. Good thing I wasn't picking my nose at the time! :)

But seriously, this sort of change is disruptive to existing users and is something that should be prompted as a priority if it's to stay as an installation feature (which incidentally, I think it shouldn't, motion invariably requires tweaking before being readily usable).

Revision history for this message
Mihai Militaru (mihai.militaru) wrote :

That's true, Rog, though I think this topic is not explicit enough. Do you also get motion enabled at startup as a root process? In this case either we should change (if possible) this description of the bug to something like "Motion does it its own way" or to fill another bug report with this problem. ;) Any suggestions?

Revision history for this message
nine (niin-deactivatedaccount-deactivatedaccount) wrote :

I am marking this particular bug report as a duplicate of bug 198292. For Hardy, the bug is resolved through a stable release update. For the Intrepid release, the bug is fixed in Debian bug 461763 and synced into the Ubuntu archives.

As for motion automatically starting on boot: motion still is configured as such. However starting on boot could be considered valid behaviour for a server like motion. If you still feel that it is an issue that should be fixed, please file a separate bug for it.

In any case: thank you for filing this bug and please feel free to report any bug you find.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.