compiz team mailing list archive

[Mauro <740126@xxxxxxxxxxxxxxxxxx>]

Just to fill in my little bit of experience (as I've been reading about
the same glitch I notice): other than the prettyor ugly workarounds
proposed in this thread, Ctrl-Alt-Bksp works as well.

I'm running on a toshiba satellite P200, with GM965/GL960 integrated
chip, and I've noticed a couple more behaviours not listed here:

1) When restoring from screensaver's screen power off, I see the normal
desktop screen as if the screensaver never kicked in (windows are all
there), I can move the pointer around, but it's as if the screensaver
was actually on; in other words, it's a variant of the "blank frozen
screensaver" where instead of the blank screen I see the normal desktop
with which I cannot interact; more often than not, when that happens,
after a while the screen goes back to blank and I get the regular
password dialogue, from which I can then proceed to uset he laptop
normally; this time though, it just stayed like that, visibile windows
on the background, pointer moveable with no effects whatsoever... Ctrl-
Alt-Bksp for me

2) If I try and do ctrl-alt-f1, and then again ctrl-alt-f7, I often get
no the blank screen anymore, but the last text screen before gdm
started, as if I had set the verbose boot mode on, but that screen i
cannot interact with, I can type characters in there that are displayed
on screen, but issuing commands or key combinations deals no effect
(including ctrl-alt-bksp); sometimes, switching back to ttty1 and then
to ctrl-alt-f7,a few times, shows the blank screen again, and I can
ctrl-alt-bksp out of it.

-- 
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/740126

Title:
  Disabling an output can cause vblank events to be missed

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/740126/+subscriptions