My very alpha weekend...

[Tom Horsley]

My fedora 12 alpha experiences so far: (I see why it is alpha :-)

kvm file images created under fedora 11 do not work in rawhide
   https://bugzilla.redhat.com/show_bug.cgi?id=524499

   This seems to be the most serious problem. I have Windows XP
   and Ubuntu KVM machines I installed while running fedora 11,
   and rawhide's KVM can't seem to run the images at all, for
   various different reasons. I'd hope I could just do a "virsh
   define" from a dumpxml saved under fedora 11 and have the same
   machines up and running under fedora 12.

drag lock mess
   https://bugzilla.redhat.com/show_bug.cgi?id=524428

   Tried to use the new evdev & xinput stuff to get my trackball
   to have a draglock button, and instead of drag lock, I get
   weird alien button behavior.

xinput list ignores device name argument
   https://bugzilla.redhat.com/show_bug.cgi?id=524393

   While trying to decrypt the utterly cryptic man page for
   xinput during experiments with draglock, I found that the
   "list" option claims to take a device name as an argument, but
   actually ignores it. (Not a big deal, but very very confusing
   when you are trying to figure out just what the heck a "device
   name" actually looks like).

keycode confusion
   https://bugzilla.redhat.com/show_bug.cgi?id=524422

   Tried to disable evdev and go back to the old way of doing
   xinput, and found the "kbd" driver lies about using pc105 as
   the default. Eventually made it work by explicitly defining a
   keyboard input device and setting us pc105.

   (At least I can make drag lock work the old way once I got the
   keyboard pressing all the right buttons again).

deiconify does not refresh window
   https://bugzilla.redhat.com/show_bug.cgi?id=524395

   I called this an ATI driver problem, but maybe it is somewhere
   else.  Whatever is actually going on, it acts like refresh
   events are being buffered up somewhere and only delivered to
   the window after a mouse movement event shows up. Maybe it is
   just firefox trying to be tricky, I'm not sure I saw it happen
   in any other app.

popup messages unreadable
   https://bugzilla.redhat.com/show_bug.cgi?id=522970

   This is an older bug I found when testing on a different
   machine with a really old original radeon all-in-wonder
   card. Whatever it is that selinux popup messages are doing to
   draw themselves seems to trigger it.