Here's an update on the items 1-7 in my original list (based on testing with an up-to-date Kubuntu Maverick; I haven't tested Ubuntu Maverick, or Natty in any form):
1 to 4 were reported as working fine in Kubuntu, and they still are.
5. Still a problem
6. Still a problem (note 5&6 are trivial to reproduce---just yank out the VGA cable and see what happens. Can I really be the only person experiencing this problem?)
7. Still a problem. There is now a very clear diagnosis of the problem: see https://bugs.kde.org/show_bug.cgi?id=249636
Note the xrandr command-line application should also be fixed: https://bugs.freedesktop.org/show_bug.cgi?id=29929
Both of these bug reports would, I think, qualify as having sufficient detail to be "useful," but both seem to have dropped into a black hole. If you know who to poke, even if it's simply to get them to tell me "we've read your bug report, we'll get to it someday," that would be reassuring.
Here's an update on the items 1-7 in my original list (based on testing with an up-to-date Kubuntu Maverick; I haven't tested Ubuntu Maverick, or Natty in any form): /bugs.kde. org/show_ bug.cgi? id=249636 /bugs.freedeskt op.org/ show_bug. cgi?id= 29929
1 to 4 were reported as working fine in Kubuntu, and they still are.
5. Still a problem
6. Still a problem (note 5&6 are trivial to reproduce---just yank out the VGA cable and see what happens. Can I really be the only person experiencing this problem?)
7. Still a problem. There is now a very clear diagnosis of the problem: see
https:/
Note the xrandr command-line application should also be fixed: https:/
Both of these bug reports would, I think, qualify as having sufficient detail to be "useful," but both seem to have dropped into a black hole. If you know who to poke, even if it's simply to get them to tell me "we've read your bug report, we'll get to it someday," that would be reassuring.