| Summary: | KDM displays garbage | ||
|---|---|---|---|
| Product: | TDE | Reporter: | Jan Stolarek <jwstolarek> |
| Component: | tdebase | Assignee: | Timothy Pearson <kb9vqf> |
| Status: | RESOLVED FIXED | ||
| Severity: | critical | CC: | albator78, alexispm_stellaluna, bugwatch, darrella, jwstolarek, kb9vqf, slavek.banko |
| Priority: | P5 | ||
| Version: | 3.5.13 [Trinity] | ||
| Hardware: | amd64 | ||
| OS: | Debian Squeeze | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
| Bug Depends on: | 1226 | ||
| Bug Blocks: | |||
| Attachments: |
KDM background garbage
Black edit fields after logging out 'uname -a' output Black widgets after upgrade to 3.5.13.1 Patch to add check box GUI control for tdmrc [X-:*-Core] TerminateServer |
||
Created attachment 841 [details]
Black edit fields after logging out
This is how edit fields look after logging out of TDE. After selecting another user they become white again.
Are you using Xorg from Squeeze - stable? I'm using XOrg from Squeeze - backports and no such problems I noticed. Interesting! This definitely needs to be fixed. Are you using the TDE compositor? One way to know is if a 'kompmgr' process is running when TDM is active. Also, are you using the integrated Intel graphics on that laptop, or a more powerful discrete graphics chip? Thanks! (In reply to comment #2) > Are you using Xorg from Squeeze - stable? I'm using XOrg from Squeeze - > backports and no such problems I noticed. I'm using xserver-xorg 7.5+8+squeeze1 from stable. (In reply to comment #3) > Are you using the TDE compositor? One way to know is if a 'kompmgr' process is > running when TDM is active. No. (In reply to comment #3) > Also, are you using the integrated Intel graphics on that laptop, or a more > powerful discrete graphics chip? Nvidia Quadro NVS 140M with proprietary drivers. I'm not sure but I think this also happened once or twice with nouveau driver. > (In reply to comment #3)
> > Also, are you using the integrated Intel graphics on that laptop, or a more
> > powerful discrete graphics chip?
> Nvidia Quadro NVS 140M with proprietary drivers. I'm not sure but I think this
> also happened once or twice with nouveau driver.
I asked because I have seen the exact same problem once or twice on a test system with nVidia cards installed. I have never seen the bug on a non-nVidia system, and you just provided one more data point in favor of something going wrong in TDE, TQt3 or Xorg on nVidia-based graphics cards.
Are you using a x64 or i386 kernel?
Created attachment 845 [details]
'uname -a' output
After upgrading to 3.5.13.1 this bug has spread beyond KDM. After I log out and log in again all widgets become black and only become normal when I hover mouse onto them. Bumping that bug to blocker, as it makes logging out virtually useless and forces a computer restart. Created attachment 862 [details]
Black widgets after upgrade to 3.5.13.1
Can you try in /etc/trinity/kdm/kdmrc enable: TerminateServer=true (In reply to comment #9) > Can you try in /etc/trinity/kdm/kdmrc enable: > TerminateServer=true In which section? I added that in [General] and this does not help. Now that you mention it I recall adding this once on my openSuse to fix some re-logging issues. BTW I noticed that if I change KDM settings in Control Center the kdmrc file gets overwritten. I think it should have a lot of comments and commented out options - on my system it does not after I made changes in Control Center. I found a sort of workaround: after logging out I switch to text console, log in as root and 'service kdm-trinity restart'. (In reply to comment #10) > (In reply to comment #9) > > Can you try in /etc/trinity/kdm/kdmrc enable: > > TerminateServer=true > In which section? I added that in [General] and this does not help. Now that > you mention it I recall adding this once on my openSuse to fix some re-logging > issues. > > BTW I noticed that if I change KDM settings in Control Center the kdmrc file > gets overwritten. I think it should have a lot of comments and commented out > options - on my system it does not after I made changes in Control Center. > > I found a sort of workaround: after logging out I switch to text console, log > in as root and 'service kdm-trinity restart'. I wonder why the TerminateServer option does not have a GUI control (checkbox) in kcontrol. This seems like another simple bug that should be fixed for R14. In section [X-:*-Core] Note: I'm always doing the changes manually in kdmrc file - so as not to overwrite by Control Center. :) (In reply to comment #12) > In section [X-:*-Core] > > Note: I'm always doing the changes manually in kdmrc file - so as not to > overwrite by Control Center. :) Ah, OK. I will give feedback on that on Saturday. (In reply to comment #12) > In section [X-:*-Core] > > Note: I'm always doing the changes manually in kdmrc file - so as not to > overwrite by Control Center. :) Adding TerminateServer=true in [X-:*-Core] section of /etc/trinity/kdm/kdmrc file solves both problems (with KDM and Trinity itself). Thanks! Nevertheless I consider this a workaround than a real solution. Created attachment 944 [details]
Patch to add check box GUI control for tdmrc [X-:*-Core] TerminateServer
I cobbled together a patch to add a check box GUI control for the kdmrc/tdmrc [X-:*-Core] TerminateServer setting.
The new check box control is located in KControl->System Administration->Login Manager->Shutdown.
The check box is disabled when the user is not root.
I tested several ways and everything is functional. Sombody should review the patch and another person should test before pushing to GIT.
Slavek, you should be able to backport the patch to 3.5.13.1 if interested.
The patch does not resolve the original bug report. However, adding the GUI control should be popular because browsing the web reveals that this setting resolves many X related problems. The real question is why the setting is necessary in KDE/Trinity.
Patch in attachment 944 [details] pushed to GIT in commit 882522b2.
This patch does not resolve the bug report but only adds a GUI control to an existing tdmrc configuration option.
I confirm this bug on Mageia 2 x86_64, TDE 3.5.13.2~pre. I've just installed up to tdebase (no other programs). I'm using TDM, login to TDE, then logout. Then the TSAK popup appears again, but in the grey zone where the black text should appear, everything is black. The next screen (login/password) has black zones too. Of course adding the "TerminateServer=true" workarounds the problem. The problem described in comment 0 and displayed on attachment 840 [details] should be resolved by commit 8b0d1b32 - see bug 1226. However I'm afraid that the problem displayed on attachment 841 [details], attachment 862 [details] and described in comment 17, is not resolved by this patch. I'm not sure this is TDE specific...there is at least one report of nVidia causing this exact same problem on KDE4: http://phoronix.com/forums/showthread.php?15162-kdm-logout-crash-black-screen-on-next-login-on-KDE4-%28solved%29 Is it possible the new versions of kdm (or lightdm or whatever is currently used with KDE) terminate the X server by default? From where I sit, the only reasonable courses of action are: 1.) do nothing, but add this issue to a known third part software problem list or 2.) add a blacklist whereby using nvidia (and possibly other drivers) automatically sets the TerminateServer option to true. Thoughts? Here is a more recent thread indicating the issue is nVidia specific and does affect more than just TDE: http://www.linuxquestions.org/questions/slackware-14/nvidia-and-kdm-de-artifacts-4175411895/ Right now I am leaning toward adding a line in the release notes mentioning the problem and its (simple) point+click workaround in the TDM control center module. Not all nVidia drivers/cards are affected, so a blacklist may become unweildy/obsolete/difficult to maintain very rapidly. On a more philosophical level, either nVidia should fix their drivers or Xorg should add a workaround. These kinds of hacks (blacklists) for known buggy/broken hardware really don't belong at the level of a desktop environment. If this is a 3rd party issue, not TDE's, then I think that the workaround should be documented in user guide or release notes and we can consider the problem solved. We have a GUI check box and the tool tip explains when to enable the option. We have bug report 1367 to address the deletion of comments from tdmrc. The tool tip should be sufficient but I can update the TDM handbook regarding the GUI check box if desired. Should we close this report? Yes, we can close it. Do we have "known bugs" section in the release notes? If so then perhaps it would be good to place information about this in there? *** Bug 1401 has been marked as a duplicate of this bug. *** I copied the tool tip text into the TDM help handbook. Commit 888a696a. |
Created attachment 840 [details] KDM background garbage Upon login KDM displays garbage, as shown in attachment. Problem occurs both when KDM themes are enabled and when they are not. It seems to disappear when a background image is set. When I log out of Trinity the KDM displays black backgrounds for password and user edit fields. This seems to happen always, regardless of background image.