Bug 861746
| Summary: | GDM login screen artefacts and corruption with Geforce 210 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ryan K <ryanskingsbury> | ||||
| Component: | xorg-x11-drv-nouveau | Assignee: | Ben Skeggs <bskeggs> | ||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 18 | CC: | airlied, ajax, awilliam, bskeggs, ozan.caglayan, robatino, ryanskingsbury, vonbehren.c | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | RejectedBlocker | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-06-25 16:45:50 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Ryan K
2012-09-30 12:15:51 UTC
Created attachment 619410 [details]
dmesg output during test
These set of errors seem to reoccur in the dmesg output around the time of login: [ 32.300612] [drm] nouveau 0000:01:00.0: fail set_domain [ 32.300617] [drm] nouveau 0000:01:00.0: validate vram_list [ 32.300663] [drm] nouveau 0000:01:00.0: validate: -22 Discussed at 2012-10-04 blocker review meeting: http://meetbot.fedoraproject.org/fedora-qa/2012-10-04/f18-beta-blocker-review-2.1.2012-10-04-16.00.log.txt . As this looks like a single-system X showstopper, we reject it as a blocker by established precedent (X bugs that affect only a single system or small range of systems are not considered to be wide enough to be blockers; we don't have the development capacity to commit to fixing all such bugs). If it turns out to affect a wider range of systems, it can be re-proposed as a blocker. i have the same problem here sometimes (can't recognize any pattern) but I have an amd/ati graphics card. (Advanced Micro Devices [AMD] nee ATI Cypress PRO [Radeon HD 5800 Series]) Most of the time at the place where the fedora logo in gdm is supposed to be, i have only some artifacts. Sometimes I have the black/white error with the accessibility icon. But the worst thing is, that every fourth reboot, gdm fails to show up. It hangs after plymouth and shows me just my mouse on a black screen. switching with Strg+Alt+F2 logging in and execute "startx" works just fine. I don't know if these problems are connected as the last has a own bugreport https://bugzilla.redhat.com/show_bug.cgi?id=879385 Chris, you have a different graphics card with a different manufacturer from Ryan. Please file your bug separately (or look for an existing report with your graphics card). Thanks! I'm having this too on F18 after upgrading from 3.6.x to 3.7.1 recently with an Nvidia card. Same dmesg output as Ryan. This wasn't happening on 3.6.x kernels. I see exact the same display errors using a Ati HD6850 and Gallium Drivers. Artifacts on - Fedora Logo (GDM Login Screen) - Power-/Bluetooth-/Volume-/Network Icon in BOTH (GDM + Gnome Shell) - Activities Background in Gnome Shell Note that the image/icon corruption does no longer persist after relaunch of Gnome shell (Alt+F2 -> r) What I do not see and suppose to be another problem is gdm failing to show up completely as chris stated.. @ Adam Williamson: Why should we (disgarding the gdm shuw up error) file another bug as these problem of image corruption seem to occur hardware independant? that's why I mentioned it here. I thought it would be interesting that it might not be nvidia specific. My bug is now filed as https://bugzilla.redhat.com/show_bug.cgi?id=885506 anyway. Christian: because you're using completely different graphics hardware which uses a completely different set of code. It's _possible_ the bug is the same and lies in the X server or the kernel or something, but it's really not very likely. There's only so many forms of 'corruption' a display can really suffer, and they're likely to follow similar patterns; it's not so weird for two entirely different bugs in two different drivers to produce similar-looking corruption. It would of course be a deal easier to compare the 'corruption' in question if people would post screen pics... Okay, thanks for the explanation. I filed a new bug and made a screenshot as wished: https://bugzilla.redhat.com/show_bug.cgi?id=903976 I will extend the bug report with a GDM screenshot later. The first one though which is not based on native reporting tools - if anyone needs additional infos or logs let me know. Ryan, are you able to reproduce it on latest Fedora 18 or 19? Regrettably I'm not able to test anymore. I removed the NVIDIA card from my system and switched to Linux Mint before Fedora 18 was released. Thanks for getting back to us! Sorry about the bug. Ozan Çağlayan, are you still around and still seeing this bug? If so, we could keep it open. Please let us know. Thanks! Hi, No I'm not having this issue anymore. OK, we'd better close this then. |