On Thu, 19 May 2005, Russ Allbery wrote: > Julian T J Midgley <[EMAIL PROTECTED]> writes: > > > Attached - just shout if there's anything else I can do to help. > > I'm guessing that the problem is the following bit in your > .gtimer/.gtimerrc file: > > win_height > 30672 > > fvwm2 didn't have any problems handling this, but it makes the window look > rather strange. :) Could you try hand-editing this to change the height > of the window in pixels to something more reasonable (300, perhaps) and > see if that makes the problem go away?
It does. Ok, that looks like a separate bug in enlightenment as well ;-) It got into that state after gtimer froze for the first time. As I remember, I switched to the desktop that gtimer was running on, and tried to switch from one task to another, to find that it wouldn't work (I believe the timer was still running, but I couldn't change tasks, click on any of the menus or icons, and ^I and ^D didn't increment or decrement the current task time). I would then either have hit CTRL-C from the xterm in which I started it, or pkill'ed it (I don't remember which, I may have had to SIGKILL it, but I probably started with SIGTERM). After this, I started it up again, and it was at this point that the window corruption appeared (forgive me, I may have misremembered this in the original bug report - it happened a couple of days ago). I've not edited the .gtimerrc file myself - it was created afresh by gtimer after I updated to the latest version earlier this week. I moved my original .gtimer directory out of the way before updating. I'm guessing that gtimer wrote the dodgy winheight entry itself after/during that initial freeze. Reproducing the freeze could be difficult - is there anything I can do to get you more information if/when it happens again? All the best, Julian -- Julian T. J. Midgley http://www.xenoclast.org/ Cambridge, England. PGP: BCC7863F FP: 52D9 1750 5721 7E58 C9E1 A7D5 3027 2F2E BCC7 863F -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
