Since moving to 5.3.3 I too have been noticing more X freezeups after a resume. The previous version I was using, 5.3.2 or 5.3.1. (I can't remember which one, sorry), rarely had that problem.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=157276\"][{POST_SNAPBACK}][/a][/div]
I wasn't seeing that with the original 5.3.3 or with what I'm stuck with at the moment. See below.
I ipk upgraded my 5.3.3 after rev3 was announced. That was a mistake since package list for Meanie's Custom feed seems to be unreadable. That means that the upgrade was from the combined Beta3 feed only. I ended up with a mutant distro. My Firefox, GTK2, GPE PIM were "upgraded" for the worse.
Most of the fonts reverted to 10 point both in the WM and the Apps. I have fixed most of the fonts back to 14 point but, FireFox is stuck at 12 point
FireFox got that god awful 80s fire icon. Luckily, I had backed up that icon after I had that ugly icon show up on my 1000 a few weeks ago. FireFox also now refuses to automatically login me in on the oesf forums. Auto-login works fine with tyrannozaurus.
The GPE PIMs are just brain damaged now. GPE Contacts refuses to import a CSV contact dump. GPE Announce is stuck in a loop and notifies me of the same appointments over and over everytime I resume. Dismissing does not help. I also can't get into GPE Calendar because it locks up on startup with a lovely blank window so, I can't delete that offending appointments. I have to go into the Process Manager and play Whack-A-Mole with all the instances of GPE Calendar and GPE Announce that are running. The offending processes respawn a few times with GPE Announce looping the notifications again. If I can't fix this soon I'm going to have ipkg remove all the GPE PIMs because it does not look good in a meeting when your Z goes psycho everytime you resume it.
In case you are wondering why I did an ipkg upgrade. Besides wanting to get Meanie's rev3 fixes (especially the TimeZone ones). I was having trouble with GPE Announce not waking up my Z for alarms and I was hoping that an upgrade would fix that. Boy, was I ever wrong!