motion package stops upgrade
Bug #220924 reported by
Tom
This bug report is a duplicate of:
Bug #198292: motion starts on install and stalls upgrades.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
motion (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: motion
The "motion" package ends up running in the foreground during the upgrade, causing the upgrade process to stop (it did record images of me while trying to fix the problem, however!).
Furthermore, in my case, when I ^C'ed out of motion, the system was in a state where I couldn't sudo anymore and hence couldn't continue with the upgrade.
To post a comment you must log in.
I ran into this also. You can reproduce it without running an upgrade though: just install motion with a webcam plugged in. If the default settings in the new /etc/motion.conf script installed with the package will work with the webcam, the process won't return. It looks like the default should be changed to "daemon yes".
There seems to be another problem though: if I just set "daemon yes" and then do "sudo /etc/init.d/motion start", I get this:
Starting motion detection : motion motion. conf motion. pid: Permission denied
[0] Processing thread 0 - config file /etc/motion/
[0] Motion 3.2.9 Started
[0] Exit motion, cannot create process id file (pid file) /var/run/
[0] Motion going to daemon mode
.
It doesn't actually start: ps -e | grep motion shows nothing.