Here are the bugs I posted today: 137579 No sound/artsd goes wild in fresh FC3rc3 137582 kfind hangs on search in FC3t3 and FC3rc3 137610 Kdevelop crashes in FC3rc3. Looks like glibc related. 137617 kwireless reports no network when session is resumed or n... 137619 files lose file assocations in FC3T3 and TC3rc3. 137620 Ark chokes on large tar files. 137625 K3b jumps ahead while burning DVD+RW with 2 files. FC3T3... All of these problems were present in FC3T3 except the kwireless issue. That is new. Here is something funny: everyone says not to use the test releases a real work machines, but it is only when these releases are used for real work that that one finds the issue. I'm a bit choked about something: I posted issues to the list for a day and repeatedly was told that the problem was because I UPGRADED from a stable FC2 to FC3T3. I was assured that if I did a fresh install all my problems would disappear. In fact, none of them did. Now today I've heard from several people that they want to hear responses from people who are specifically UPGRADING. I'll bet that 50% of the FC3 installs are going to be UPGRADES, probably half of them from FC2. I do not think it was smart for the board to write off my issues as being "upgrade related" and "solved". They should have been given attention when they existed as a upgraded installation. One more thing: I had an installation glitch with FC3rc3 last night. I'll report it as a bug when I get the info from it later tonight. (I sent an email from my neighbors machines outlining it and he will email it to me when he gets home.) Basically, I got an out of disk space error when there was lots of disk space. This was on a fresh install.