Comment 697 for bug 771788
Revision history for this message
| Alessandro Ceschini (alessandroceschini-it) wrote | #697 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
Hi Andrea
Wait. What you say would be true if the problem stemmed from the Nvidia drivers, but this seems not to be the case, the reality is that Unity is to be blamed, for the driver works well. I surfed many forums but they don't give me more pieces of information than I already have: usually everything revolves around installing drivers, forcing Unity start bla bla bla... I've already tried all that stuff and certainly I cannot say I didn't do something about that. Actually I've been trying everything. To no avail.
So why doesn't the bug team tell me they won't just solve that UNITY bug, it's Unity the problem, not the nvidia-driver, otherwise the control panel wouldn't tell me that the driver is IN USE.
When the nvidia-driver was buggy it used to tell me it was NOT IN USE. But now the situation has changed: it's IN USE.
Would someone please take notice, that I've got a problem with UNITY NOT WITH NVIDIA-DRIVERS?