as my header says, Glaze 1.1 has begun to use 100% cpu at start up, it' won't go pass the login screen
I have to stop the process to get into windows
Any who had simelair probs?
I haven't heard of this before, sorry. Try downloading the theme again and re-installing it.
And for reference my ZIP files have a known bug that prevents the files from being extracted with Power Archiver and Windows XP ZIP. Be sure to use another utility such as WinZIP to extract all the files successfully.
I've used winrar, but it worked just days ago... so it's strange...
but thx for a great theme DrWorm
actually, I had the same problem, but I forgot to tell you about it doc. the only way I could get around it was to switch to a different theme before logging off/shutting down/restarting, so that it wouldn't be loaded on startup.
So do you still have to do this when using Glaze? It's the first I've heard of it and I wouldn't know where to begin looking for the cause.
I don't know, I haven't fired up glaze in a while. I'll try it out a little later, see if it still happens. I'll let you know, either way.
I had this problem with another theme. I read somewhere that if you change the order the modules load in your step.rc, it may solve the problem. It did for me!!
You may be experiancing this problem if you are using LS 0.24.7. A friend who was experiancing this problem narrowed the cause back to RabidVWM. You could try either replacing this module with another VWM (but you may loose multi-monitor support) or change your LS version to 0.24.6.
There does seem to be an impossible bug in RabidVWM that will cause it to freeze under certain conditions. I can stop it from freezing, it's actually very simple, but I haven't done it because it would just be hiding the bug instead of fixing it.
It seems that this is more widespread than I realized though, so I'll try to get a build out before long that won't freeze. Hiding the bug will probably render it harmless, as frustrating as it is to not know the real cause.
Since upgrading to LS 0.24.7 I'm experiancing this problem myself. An easier method, than what Deuce described, to get around this issue is to either !recycle or !togglemodules.
RabidCow >> I'm not sure if it helps but for some reason !togglemodules get RabidVWM out of it's freeze. Whilst it's in it's freeze my hotkeys work but I can't mouse-click on the desktop to make the popup appear. It seems a bit funny that the hotkey module loads before the freeze but jdesk or popup doesn't (seem to).