compositing trouble after update
Page 1 of 1 (10 posts)
Tags:
None
Registered Member 
|
A few days ago, I performed an update from Fedora 16 to Fedora 17.
After that everything runs smoothly (including login in graphical environment KDM), until I get a black screen at startup of "KDE Plasma Workspace". In GNOME and 'KDE Plasma Workspace failsafe', I haven't a black screen. The version of KDE is 4.9 (also kwin). After much searching, I encountered the compositing press ctrl+shift+F12, and my screen was filled again with a beautiful painting and my familiar icons. This was a great help, because now I can continue working in my familiar environment. But the problem isn't solved. First I thought it is due to a malfunctioning video driver (NVIDIA => nouveau), but if it worked before the upgrade then something went wrong during the update. I stay in a black screen even after I change the compisiting type to 'XRender", and also here ctrl+shift+F12 is the solution. This is what I have already undertaken to solve the problem after google searching, but without success.
create new fresh dummy user and login with that user. reinstall all KDE related software : $> yum reinstall kde* mv $HOME/.kde.share/config/plasma-desktop-appletsrc $HOME/.kde.share/config/plasma-desktop-appletsrc-broken add a new file in /etc/sysconfig/desktop with one line : DISPLAYMANAGER=KDE and mush more => but all without success !
The content of the log file '.xsession-errors': Regards, |
|
KDE Developer
|
my recommendation would be to switch to the proprietary NVIDIA driver.
|
|
Registered Member
|
Thanks, the installation of the native driver is something for the W.E. and I will indicate here the result. regards |
|
Registered Member
|
The installation of my native NVIDIA driver is finally successful. I'm not going into details, because not relevant to this forum. What is important to mention is that ACPID daemon must be running to avoid the same performance problems as with the NOUVEAU driver.
But unfortunately, the problem associated with the black screen persists. Only after a compositing press 'ctrl+shift+F12', my screen reappears. Here is a new .xsession-error, with the new native NVIDIA driver installed:
Thanks in advance for your help. |
|
run "kcmshell4 kwincompositing" and in the second tab disable the login effect, in the 3rd tab uncheck "Use OpenGL 2 shaders"
See what happens and esp. whether you get a black screen even when logging in using the xrender compositor. |
|
Registered Member
|
@luebking thanks, I had already experimented using 'System Settings', but for some reason the changes are not permanent, keep getting the message 'kdeinit could not launch /usr/libexec/kde4/kdesu'. At the start of the 'kde plasma desktop" I get no black screen anymore. At first sight it seems that I can easily work with XRender (panel is transparent), but XRender has jammed a few times. I can only solve this by pressing twice the composite key "cntrl+shift+F12". Is XRender also supported with old graphics card in combination with acpi? If you (or others) deem it appropriate, I will further communicate about this issue. But only during the W.E. I have time to investigate. Meanwhile I turn XRender off each time it jams. Thanks again. |
|
kdesu is relevant to impact system settings (when you need root permissions) - not for the regular session or application configuration.
You'll have to ask fedora on this (eg. on whether they've completely substituted by some policykit rules etc.) So, I read using XRender does work (in a way) - did you also try deactivating GL2 Shaders and/or the login effect? Reg. "jamming" - i've never seen such and use the XRender compositor -occasionally- on an FX5200 (NV34 while you're on an NV38) -> Do you have "suspend comspositing for fullscreen windows" enabled and could that be related (ie. the "jam" would usually occur when leaving -or maybe even entering- a fullscreen state in some application?) When using the XRender compositor, you usually want to use the "native" graphicssystem as well to avoid some superfluous conversions in the compositor. |
|
Registered Member
|
I did some 'try and error' after my last post. And indeed with XRender instead of GL2 there are no more blocks, at least until now. What I find strange is that it takes a moment before a window can minimize or restore (approximately 2 seconds). But it's my first day with XRender, I never used it in previous Fedora releases. When changing 'compositing type' I get two messages : - Blur effect requires OpenGL - Startup Feedback effect requires OpenGL But I still have 'blur' effects, and I don't know what effect I miss at startup. I suppose I can ignore these messages. I can not remember having worked in fullscreen mode. But I enabled it now (it was disabled). This parameter has always equaled 'native'. With the exception of the minimize and restore problems, it seems that I finally can work without crossed fingers. Your help was most welcome. Thanks again. |
|
Registered Member
|
Minimize window is no longer a problem, and to solve it: run "kcmshell4 kwincompositing" and in the second tab disable the 'Minimize animation'. I don't know what I miss with the minimize animation, but I don't need it for now. Greetings. |
|
Those effects require OpenGL Blur because it needs shaders to operate on single pixels (though a POC for XRender "distorsion" exists - but in bad shape since i've not touched it for quite a while. Rather don't use it) Startup Feedback because it's only most relevant for OpenGL (it's the boucing cursor) while the regular implementation that works w/o compositing as well is pretty much of for XRender compositing.
DON'T - it's likely gonna cause you far more trouble than good.
Sounds as if scaling is slow on your xrender implementation - it animates the transition from and to the taskbar when un/minimizing a window. The zoom or magnifier effects will probably share similar problems. However my personal experiences with the nvidia blob do not match this - it is very fast on scaling and alpha blending on XRender - check the Xorg log on whether acceleration is disabled. (/var/log/Xorg.0.log) |
Page 1 of 1 (10 posts)
Bookmarks
Who is online
Registered users: bartoloni, Bing [Bot], Evergrowing, Google [Bot], q.ignora, watchstar
