Bug#691078: motion keeps restarting after recent upgrade, and appears unable to find some av codec

2012-11-06 Thread gregor herrmann
On Tue, 06 Nov 2012 21:52:17 -0500, H. S. wrote: > I reinstalled the system, however, motion was not happy with the > target directory permissions. Once I fixed that, it started to work > properly. Nice! > In short, on a freshly installed Wheezy system, motion now works fine. > > Next up, I us

Bug#691078: motion keeps restarting after recent upgrade, and appears unable to find some av codec

2012-11-06 Thread H. S.
Correction: I reinstalled the system, however, motion was not happy with the target directory permissions. Once I fixed that, it started to work properly. In short, on a freshly installed Wheezy system, motion now works fine. Next up, I usually change my distro to "testing" ... will do so with my

Processed: Re: Bug#691078: motion keeps restarting after recent upgrade, and appears unable to find some av codec

2012-11-06 Thread Debian Bug Tracking System
Processing control commands: > tag -1 - moreinfo Bug #691078 [motion] motion keeps restarting after recent upgrade, and appears unable to find some av codec Removed tag(s) moreinfo. -- 691078: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691078 Debian Bug Tracking System Contact ow...@bugs.

Bug#691078: motion keeps restarting after recent upgrade, and appears unable to find some av codec

2012-11-06 Thread gregor herrmann
Control: tag -1 - moreinfo > >> [UPGRADE] ffmpeg:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1 > >> [UPGRADE] gstreamer0.10-ffmpeg:amd64 0.10.13-5 -> 1:0.10.13-dmo1 > >> [UPGRADE] libxine2-ffmpeg:amd64 1.2.2-4 -> 1:1.2.2-dmo3 > >> [UPGRADE] libavcodec54:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1 > >> [UPGRADE] libavde

Bug#691078: motion keeps restarting after recent upgrade, and appears unable to find some av codec

2012-11-05 Thread H. S.
On Sun, Nov 4, 2012 at 12:54 PM, gregor herrmann wrote: > Control: tag -1 + moreinfo > > On Sat, 20 Oct 2012 23:21:37 -0400, H. S. wrote: > >> Earlier (till yesterday, part of the output included something like: >> Oct 18 09:40:28 red motion: [0] ffmpeg LIBAVCODEC_BUILD 3482368 >> LIBAVFORMAT_BUIL

Bug#691078: motion keeps restarting after recent upgrade, and appears unable to find some av codec

2012-11-04 Thread gregor herrmann
Control: tag -1 + moreinfo On Sat, 20 Oct 2012 23:21:37 -0400, H. S. wrote: > Earlier (till yesterday, part of the output included something like: > Oct 18 09:40:28 red motion: [0] ffmpeg LIBAVCODEC_BUILD 3482368 > LIBAVFORMAT_BUILD 3478784 > > That line is missing from the console output now (a

Processed: Re: Bug#691078: motion keeps restarting after recent upgrade, and appears unable to find some av codec

2012-11-04 Thread Debian Bug Tracking System
Processing control commands: > tag -1 + moreinfo Bug #691078 [motion] motion keeps restarting after recent upgrade, and appears unable to find some av codec Added tag(s) moreinfo. -- 691078: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691078 Debian Bug Tracking System Contact ow...@bugs.de

Bug#691078: motion keeps restarting after recent upgrade, and appears unable to find some av codec

2012-10-20 Thread H. S.
Package: motion Version: 3.2.12-3.2 Severity: grave Justification: renders package unusable Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? Possibly my recent upgraded to my Debian system. * What exactly did you do (or n