ubuntu-x-swat team mailing list archive

[John Clemens <767970@xxxxxxxxxxxxxxxxxx>]

Thanks for looking into this.  I fully realize its experimental, but
Ubuntu is now providing an easy way to test these things so that bugs
can be found.  That's the purpose of testing.  Plus, the last time
something like this happened, it was a real bug in Compiz that was
uncovered by a specific driver.  I'm not saying you've got to hold up
the Natty release or anything, I'm just reporting a bug.

This is my work machine, so I can't spend too much time debugging, but I
discovered something interesting today when I went to take a screenshot.
Whenever I ran xterm, not long afterwards, X crashed (no mouse or
keyboard, and I happened to not have sshd running at the time, but pings
responded).  So I couldn't get a screenshot.  Same thing happened again
when I ran xterm after rebooting.. that time the xterm window didn't
even show before it crashed.  The rest of the day, I didn't run xterm,
and the system and Unity was fine.  So, SOMETHING about xterm and unity
causes the nouveau driver to crash.

Tomorrow, assuming I have time, I'll try booting into regular gnome with
and without compiz and see if i can repeat and get a screenshot.  I'll
also be logged in via ssh and see if I can get some debug output from
either dmesg or .xsession-errors .

gnome-terminal is fine, I ran it all day, but I much prefer xterm
because it's faster and much less resource intensive. Also, a problem
with xterm, the most fundamental X-windows program, suggests a latent
problem that's bound to affect other applications.

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

Title:
  xterm font corruption with unity and nouveau experimental 3d