I grabbed 3.2.9-1ubuntu1 from hardy-proposed, but I ran into a couple of problems.
First, if I install it after purging the old version (3.2.9-1), it works ok, except that it still fails to create a PID file in /var/run. I'm not sure why. But the process does daemonize and I verified that it's working, i.e., detecting motion and producing jpgs and swfs in /tmp/motion. Also /etc/init.d/motion can stop and restart it properly. Second, if I upgrade from 3.2.9-1 without uninstalling the old version, it doesn't restart the motion process. This is because the old /etc/init.d/motion script fails to shut down the old daemon, because the PID file never got created. Here's the output from the upgrade: Preparing to replace motion 3.2.9-1 (using .../motion_3.2.9-1ubuntu1_i386.deb) ... Stopping motion detection : motion No /usr/bin/motion found running; none killed. . Unpacking replacement motion ... Setting up motion (3.2.9-1ubuntu1) ... Installing new version of config file /etc/init.d/motion ... Starting motion detection : motion /usr/bin/motion already running. . Reading package lists... Done Building dependency tree Reading state information... Done Reading extended state information Initializing package states... Done Building tag database... Done I'm happy to do more testing if it will help. -- Hardy upgrade - motion halts upgrade https://bugs.launchpad.net/bugs/198292 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
