File a new bug. See http://wiki.ubuntu.com/X/Reporting for directions
on how to report a bug.
** Changed in: nvidia-graphics-drivers-180 (Ubuntu)
Status: Incomplete => Invalid
--
terminal output frequently not current or blank
https://bugs.launchpad.net/bugs/244356
You received this bug
There are plenty of people in this bug report also experiencing the
issue including myself, so just because jasonq can't provide more
information doesn't mean others including myself cannot. Just let us
know what information to provide!
** Changed in: nvidia-graphics-drivers-180 (Ubuntu)
St
Since the hardware cannot be used for doing troubleshooting with, we'll
have to close the bug for now. However please feel free to reopen if
you or anyone else has the same HW and can reproduce this issue using
the latest development version of Ubuntu and is willing to do some
troubleshooting with
On Mon, Jul 6, 2009 at 9:33 AM, jasonq wrote:
> Bug still occurs on Ubuntu 9.04 with NVIDIA driver 180.44.
Have you tried enabling "Force synchronization between X and GLX" in
the "Workarounds" section of compizconfig-settingsmanager? This seems
to be the general solution.
--
terminal output fre
Bug still occurs on Ubuntu 9.04 with NVIDIA driver 180.44.
I haven't seen the bug as frequently as in the past but it's still there
and still happens with the testcase I posted where you pull the top of a
terminal down after a "clear" command.
I don't want to try a more recent driver because I'm
I've posted a new version of the -nvidia driver to our xorg-edgers PPA,
would you mind testing it either on Jaunty or Karmic and see if it
resolves this bug?
Get nvidia-graphics-drivers-180 - 185.18.14 here:
https://edge.launchpad.net/~xorg-edgers/+archive/ppa
** Changed in: nvidia-graphics-
I haven't seen the terminal issue for a while with recent nvidia drivers,
and the recent compiz update seems to have addressed the issue with Wing IDE
that I was having:
compiz-fusion-plugins-main (0.8.2-0ubuntu2) jaunty; urgency=low
* debian/patches/07_workarounds_force_glx_sync.patch:
- w
[This is an automated message]
In Jaunty (9.04), we have just updated to the latest
nvidia-graphics-drivers-180 package from nVidia, version 180.44.
This package provides fixes for a large number of bugs, and we need your
assistance in testing if it fixes the issue you reported.
To do this, ple
[This is an automated message]
In Jaunty (9.04) we have dropped the nvidia-graphics-driver-177 package, as
it is superseded by nvidia-graphics-drivers-180.
Because of this, we are closing this bug as expired.
You are encouraged to file your -nvidia bug reports against the
nvidia-graphics-driver
[This is an automated message]
In Jaunty (9.04), we are dropping the nvidia-graphics-drivers-177 package, which
is now superseded by then nvidia-graphics-drivers-180 package.
http://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-180
To transition your bug into the new package, we n
I can also confirm it in Jaunty with nvidia's 180.27 drivers. It seems
to happen slightly less often in Jaunty, although I may be incorrect
about that.
--
terminal output frequently not current or blank
https://bugs.launchpad.net/bugs/244356
You received this bug notification because you are a me
I can now confirm this on Intrepid with the nvidia 177 and 180.11
drivers. It actually isn't limited to the terminal (I've experienced it
in Wing IDE as well) but it certainly isn't most applications that
experience it.
** Changed in: nvidia-graphics-drivers-180 (Ubuntu)
Sourcepackagename: None =>
I can confirm what I think is the same bug (but who knows). I cannot
reproduce it by resizing the window, but the problem is reproducible
with "ls". As jasonq describes, repeatedly using "ls" in gnome-terminal
eventually leads to a window that is not correctly redrawn. (To
reproduce this, I have to
Added video showing problem and also shows that I am not using
restricted nvidia drivers.
The "clear and drag top" is not the only way this problem occurs. The
bug occurs during regular use without resizing the window but I have not
found a way to reproduce that.
The video is a little jumpy in pa
FYI I am unable to duplicate this on my Intrepid machine.
--
terminal output frequently not current or blank
https://bugs.launchpad.net/bugs/244356
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@
It has the information needed to investigate the problem. I posted it
but nobody refered to it. Here it is again:
1) Open a gnome-terminal
2) execute a "clear" command
4) When the window is resized by pulling the *top* of the window down below
where the cursor was, the prompt will become invisibl
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering is this still an issue
for you? Can you try with latest Ubuntu release? Thanks in advance.
** Changed in: ubunt
I think this may well be an nvidia driver bug, for some time now the
driver has chosen to handle anti-aliasing for fonts and I suspect this
to be the issue, if you use a console with non-AA fonts i.e. xterm I am
sure this would not happen.
--
terminal output frequently not current or blank
https:
Neither Compiz nor my dual monitor setup worked with the free drivers.
(The xorg.conf file also got screwed up after switching drivers. I'm
afraid to try more driver tests now that I have everything running again
because this is my work machine.)
I did, however, figure out a pattern for a small re
So Mark, does the issue occur on both setups? The next time it happens,
could you take a screenshot and attach it here; it will most likely make
it easier for someone who may know something to quickly diagnose it.
--
terminal output frequently not current or blank
https://bugs.launchpad.net/bugs/
Additionally, you could try using the free open-source drivers with
compiz for a few days and see if you can duplicate it. If not, we can
file it against the restricted nvidia drivers!
--
terminal output frequently not current or blank
https://bugs.launchpad.net/bugs/244356
You received this bug
Thanks, Mike for your attention to this issue. I am using restricted
drivers and the output of lspci gives
VGA compatible controller: nVidia Corporation G71 [GeForce 7300 GS] (rev
a1)
as my video card. My laptop's video card is also nVidia (but an 8600)
and I was also using restricted drivers.
-
I am guessing this has to do with your video driver. I will mark this as
New again and someone else who knows more about video issues can
hopefully chime in. If the drivers are the issue it isn't Compiz so I am
also unmarking that. Do you know if you are using restricted drivers?
** Changed in: ub
Hi, Mike. It seems impossible to construct a testcase regarding this
bug. I've been trying to notice a pattern for weeks now. You can just
sit there typing "ls" over and over and occasionally the output will not
show properly. My guess is that there is some sort of time syncing issue
going on betwe
Hi Jason, thanks for using Ubuntu and taking the time to file this bug
report! I have personally never experienced this issue, but I think the
best thing for you to do is to find a set of steps that can reproduce it
from startup. It may not be easy, but eventually after trying
combinations, you sho
Could this be a problem with the terminal program, not redrawing
properly? Are you using gnome-terminal? Does the same happen with
another terminal program, e.g. xterm?
--
terminal output frequently not current or blank
https://bugs.launchpad.net/bugs/244356
You received this bug notification bec
I guess I could mention that I am using the desktop cube, wobbly
windows, cube caps. I can provide more detail if it helps but since I
haven't found an exact sequence that always reproduces the problem, the
best way to start debugging this would be to find other users
experiencing a similar problem
28 matches
Mail list logo
