Comment #21 on issue 28544 by e...@chromium.org: Loss in responsiveness on
a remote NX session
http://code.google.com/p/chromium/issues/detail?id=28544
That is correct, Midori has a different drawing model than us.
--
You received this message because you are listed in the owner
or CC fields
Updates:
Status: Available
Cc: est...@chromium.org e...@chromium.org d...@chromium.org
Labels: HelpWanted
Comment #18 on issue 28544 by mikesm...@chromium.org: Loss in
responsiveness on a remote NX session
http://code.google.com/p/chromium/issues/detail?id=28544
Invest
Comment #11 on issue 28544 by e...@chromium.org: Loss in responsiveness on
a remote NX session
http://code.google.com/p/chromium/issues/detail?id=28544
I understand what you're saying, but you've given me nothing to work from
here. :)
--
You received this message because you are listed i
Comment #10 on issue 28544 by av...@shadypixel.com: Loss in responsiveness
on a remote NX session
http://code.google.com/p/chromium/issues/detail?id=28544
I understand what you're saying, but chrome is really the *only* X
application that
doesn't work very well over NX. I'm fairly sure that
Comment #9 on issue 28544 by e...@chromium.org: Loss in responsiveness on a
remote NX session
http://code.google.com/p/chromium/issues/detail?id=28544
Could someone file a bug with the NX people and link to it here? I'm not
sure we're
supposed to rewrite apps to work around NX; we've done
Comment #8 on issue 28544 by av...@shadypixel.com: Loss in responsiveness
on a remote NX session
http://code.google.com/p/chromium/issues/detail?id=28544
I'm seeing this too. firefox is fairly quick or nx and chrome is unusable.
Symptoms:
* as other people mentioned, both scrolling and se
Updates:
Cc: da...@chromium.org
Comment #7 on issue 28544 by e...@chromium.org: Loss in responsiveness on a
remote NX session
http://code.google.com/p/chromium/issues/detail?id=28544
Darin: I wonder if this could be related to your recent change on the way
we handle
repaint rects?
Comment #6 on issue 28544 by lschumac...@google.com: Loss in responsiveness
on a remote NX session
http://code.google.com/p/chromium/issues/detail?id=28544
Related and very easily reproduced - searching within the page over NX (eg,
ctl-f) is
unbelievably bad. This is due to the incremental
Updates:
Status: Untriaged
Comment #4 on issue 28544 by e...@chromium.org: Loss in responsiveness on a
remote NX session
http://code.google.com/p/chromium/issues/detail?id=28544
We try to make minimal X calls (so we are using the X move rect
optimizations); sadly,
NX must be confused.
Updates:
Labels: -OS-All OS-Linux
Comment #3 on issue 28544 by phajdan...@chromium.org: Loss in
responsiveness on a remote NX session
http://code.google.com/p/chromium/issues/detail?id=28544
(No comment was entered for this change.)
--
You received this message because you are listed i
Comment #2 on issue 28544 by asrivas: Loss in responsiveness on a remote NX
session
http://code.google.com/p/chromium/issues/detail?id=28544
Things are better and usable, but still slower with the client OS being
hardy and
nxclient 3.4.0-5.
With client OS being karmic 2.6.31-15 generic and n
11 matches
Mail list logo
