Bug#473993: Setting date in the past causes conky to use 100% CPU
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 it began printing Conky: can't select(): Invalid argument and using 100% CPU. As soon as I set the time back forwards it stopped printing these messages. I was trying to locate the source of the problem on my machine and I could no longer replicate the bug! (I think there have been some upgrades on my system since I last tested). Could you please re-check that the bug persists? I also wanted to check whether you are using a different .conkyrc from the default one in /etc/conky/conky.conf. If so could you please send that to me? Thanks, Kapil. -- Changing 'own_window yes' = 'own_window no' causes the problem to occur. If the config is set to 'own_window yes' it does not occur. Aside from that, no changes have been made to the stock config. Regards -Laurence -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#473993: Setting date in the past causes conky to use 100% CPU
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% CPU. As soon as I set the time back forwards it stopped printing these messages. I was trying to locate the source of the problem on my machine and I could no longer replicate the bug! (I think there have been some upgrades on my system since I last tested). Could you please re-check that the bug persists? I also wanted to check whether you are using a different .conkyrc from the default one in /etc/conky/conky.conf. If so could you please send that to me? Thanks, Kapil. -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#473993: Setting date in the past causes conky to use 100% CPU
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 Conky to use 100% CPU until the time is altered back to the point it was changed or the clock advances normally to the point it was changed back. Thank you for your report. I recently (as in today!) uploaded version 1.5.1-1. Could you please cross-check whether the bug persists with this version? Thanks and regards, Kapil. -- I have upgraded to the latest version in unstable: [EMAIL PROTECTED]:~$ conky -v Conky 1.5.1 compiled Wed Apr 2 09:21:05 UTC 2008 for Linux 2.6.24-1-686 (i686) Compiled in features: System config file: /etc/conky/conky.conf X11: * Xdamage extension * Xdbe extension (double buffer) * xft Music detection: * mpd General features: * hddtemp * portmon * rss * wireless 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% CPU. As soon as I set the time back forwards it stopped printing these messages. Hope this helps -Laurence -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#473993: Setting date in the past causes conky to use 100% CPU
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 point it was changed back. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages conky depends on: ii libc6 2.7-10GNU C Library: Shared libraries ii libcurl3-gnutls7.18.0-1 Multi-protocol file transfer libra ii libglib2.0-0 2.16.1-2 The GLib library of C routines ii libiw2929-1 Wireless tools - library ii libx11-6 2:1.0.3-7 X11 client-side library ii libxdamage11:1.1.1-3 X11 damaged region extension libra ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar ii libxfixes3 1:4.0.3-2 X11 miscellaneous 'fixes' extensio ii libxft22.1.12-2 FreeType-based font drawing librar ii libxml22.6.31.dfsg-2 GNOME XML library conky recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#473993: Setting date in the past causes conky to use 100% CPU
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 changed or the clock advances normally to the point it was changed back. Thank you for your report. I recently (as in today!) uploaded version 1.5.1-1. Could you please cross-check whether the bug persists with this version? Thanks and regards, Kapil. -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
