Bug#473993: Setting date in the past causes conky to use 100% CPU

2008-04-14 Thread Laurence Alexander Hurst
On Mon, Apr 14, 2008 at 07:01:38AM +0530, Kapil Hari Paranjape wrote: tags 473993 + unreproducible thanks On Fri, 04 Apr 2008, Laurence Alexander Hurst wrote: The problem does still persist. I ran Conky in a terminal (without forking to the background) and when I set the system time back

Bug#473993: Setting date in the past causes conky to use 100% CPU

2008-04-13 Thread Kapil Hari Paranjape
tags 473993 + unreproducible thanks On Fri, 04 Apr 2008, Laurence Alexander Hurst wrote: The problem does still persist. I ran Conky in a terminal (without forking to the background) and when I set the system time back it began printing Conky: can't select(): Invalid argument and using 100%

Bug#473993: Setting date in the past causes conky to use 100% CPU

2008-04-04 Thread Laurence Alexander Hurst
On Wed, Apr 02, 2008 at 11:40:55PM +0530, Kapil Hari Paranjape wrote: tags 473993 + moreinfo thanks Hello, On Wed, 02 Apr 2008, Laurence Alexander Hurst wrote: Setting the current system time to some point in the past (e.g. when setting the clock back as part of daylight saving) causes

Bug#473993: Setting date in the past causes conky to use 100% CPU

2008-04-02 Thread Laurence Alexander Hurst
Package: conky Version: 1.4.9-4 Severity: normal Setting the current system time to some point in the past (e.g. when setting the clock back as part of daylight saving) causes Conky to use 100% CPU until the time is altered back to the point it was changed or the clock advances normally to the

Bug#473993: Setting date in the past causes conky to use 100% CPU

2008-04-02 Thread Kapil Hari Paranjape
tags 473993 + moreinfo thanks Hello, On Wed, 02 Apr 2008, Laurence Alexander Hurst wrote: Setting the current system time to some point in the past (e.g. when setting the clock back as part of daylight saving) causes Conky to use 100% CPU until the time is altered back to the point it was