Bug 91866
| Summary: | flag screensaver combined with nvidia TNT2 bin driver | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Felipe Pereira <felmasper> |
| Component: | xscreensaver | Assignee: | Bill Nottingham <notting> |
| Status: | CLOSED NOTABUG | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 8.0 | CC: | menscher, rvokal |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2003-05-29 03:27:42 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
strace would be interesting. But since it's X that's going off into lalaland with nVidia's driver, the bug is almost certainly in their driver, and there's really not much of anything we can do to either debug or fix it; sorry. You're probably best served taking this up with nVidia. |
Description of problem: X goes to 99% CPU (mouse moves, keyboard does not respond). Then user must (and can) use ssh and kill X. I'm using nvidia's own driver. I guess I should not post bugs in this case since the kernel is tainted. Version-Release number of selected component (if applicable): Flag: from the XScreenSaver 4.05 distribution (28-May-2002.) How reproducible: Always I choose this screensaver in the properties dialog (occurs when it's executed normally as screen saver also). Steps to Reproduce: 1. Have nvidia's driver for TNT2 2. Execute flag (or choose it in the XScreensaver's properties dialog) Actual results: X stops. Keyboard does not respond. Mouse moves but does not click. Can't get off X (Ctrl+Alt+F1 etc.). Must use ssh and kill X. Expected results: I'd expect nvidia give away the source code for this driver... I guess the problem is with the driver. Additional info: I dont know how to get more info on this bug... I don't get any message since X stops... I'll try more later (maybe remote debugging and logging).