On Monday 02 Jun 2008 2:16:54 am Raphael Manfredi wrote: > I discovered accidentally that if there is a window partially covering the > xosview window, then a CPU frequency change does not cause a reset of the > CPU line. However, if nothing is before (i.e. the window is in the front), > then this resetting occurs. Moving the xosview back behind another window > will cause the CPU line to be displayed correctly again with the history. > > This may be an X bug and not an xosview bug...
It looks like X bug.. > Maybe the developers can try to reproduce the problem and see whether > what is causing this behaviour is due to an event not properly handled > by xosview? Is this similar to: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=384453 ? Please check. Thanks for your inputs. -- Cheers, Kartik Mistry | GPG: 0xD1028C8D | IRC: kart_ Blogs: {ftbfs,kartikm}.wordpress.com Why do they call it baby-SITTING when all you do is run after them? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
