Summary: | Desktop effects disabled on boot | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | SP <scp.stjohn> |
Component: | compositing | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED NOT A BUG | ||
Severity: | normal | Keywords: | reproducible |
Priority: | NOR | ||
Version: | 4.9.5 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
SP
2012-10-14 20:42:07 UTC
when compositing is inavailable, is kwin running at all (do windows have a titlebar, can you move them around, pass the focus by clicking into them, alt+tab navigate through them, etc.) Yes - Kwin is running as are titlebars and normal navigation. 3D effects, shadows, transparency etc effects etc are not enabled. - does just restarting "kwin --replace &" "fix" it - can you log into a failsafe session (just X11 + xterm) after the re/boot and there attempt to launch "glxgears"? @Thomas I appear to have resolved this. Not sure how - but here is what I did. 1. I renamed /etc/kde/kdm/kdmrc to kdmrc_hold (as root). 2. Rebooted and logged into KDE 3. Of course, this gives a minimal desktop 4. Opened up a terminal window and renamed kdmrc_hold back to kdmrc 5. Rebooted. 6. Desktop effects are enabled on straight boot and login. Tried it repeatedly - no change. My guess is that booting without a kdmrc and then rebooting with it caused KDE to rewrite the settings in its local home directory config files and this removed an outmoded script or line. Just guessing. I will wait a day or two to see if the problem recurs before marking this as solved. Thanks for your help and input. Spoke too soon - kde effects are not working again. Here is the output from: kwin --replace & [1] 2431 OpenGL vendor string: ATI Technologies Inc. OpenGL renderer string: AMD Radeon HD 7500 Series OpenGL version string: 2.1 (4.2.11762 Compatibility Profile Context) Driver: Catalyst Driver version: 2.1 GPU class: Unknown OpenGL version: 2.1 Linux kernel version: 3.6.1 Direct rendering: no Requires strict binding: yes GLSL shaders: no Texture NPOT support: yes NO VSYNC! glXGetVideoSync, glXSwapInterval, glXIsDirect false true 0 kwin(2431): Shaders are not supported ^C running glxgears in a kde failsafe session brings up the graphic with the following output in the terminal: glxgears 301 frames in 5.0 seconds = 60.087 FPS 300 frames in 5.0 seconds = 59.945 FPS 300 frames in 5.0 seconds = 59.986 FPS 300 frames in 5.0 seconds = 59.997 FPS 301 frames in 5.0 seconds = 60.001 FPS 300 frames in 5.0 seconds = 59.999 FPS not a kde failsafe session, it must be a naked x11 server, w/o desktop environment or WM and esp. anything linking libGL (ie. also Qt) - you can have a running xterm or launch glxgears from vt1 @Thomas - Loading basic X11 and running glxgears from vt terminal produces a similar result as above. The animation opens in a corner window and the frames per second reading is more or less the same (could not paste from the vt terminal). Ok, doesn't sound like the GPU is somehow not inited on first invocation. -> Does it work to start KDE with disfuntional compositing and then to later on simply run "kwin --replace&" (restarting the WM, this could point that the GPU is not initialized time driven, the driver may require some setup during the session start and KWin starts very early) I have to apologize for misreporting here - there is something either I did not notice before or things have changed since i first filed this. I have been so busy looking at the panel that I failed to notice that desktop effects for windows were enabled/disabled by both kwin --replace& and the alt-shif-F12 sequence. The problem is that neither of these restores the panel and taskbar to its normal plasma transparency. Only logging out and in again (not rebooting) restores this. The panel has a dark bronze background. New panels have a grey non-transparent background. falls into categories of bug #179042 then, could also have relation to creating the session bus. marking as dupe for now, please monitor https://git.reviewboard.kde.org/r/106844/ as well and what's the setting of "enable compositor on start" setting in the first tab of "kcmshell4 kwincompositing"? *** This bug has been marked as a duplicate of bug 179042 *** > and what's the setting of "enable compositor on start" setting in the first tab of "kcmshell4 kwincompositing"?
It is enabled
Any guess why logging out and in again restores the transparency of the panel (rather than a reboot - which invariably does not)? It would seem that some scripts are not loading on a straight boot and login to kde but they are on logging out and then in again\? (In reply to comment #13) > Any guess why logging out and in again restores the transparency of the > panel (rather than a reboot - which invariably does not)? Plasma-desktop doesn't notice that a compositor is running, because a) it does not (eg. kwin crashes eg. for a GL error in the cold system, then restarts) b) the selectionowner has not been updated (plasma-desktop starts up too early, doesn't wait for the server to be synced) That's hard to say being absent from the system, you'd have to try on the plasma-desktop sources (log debug infor about the system when it checks for the compositing state, like whether there's already a kwin process, whether bypassing the KWindowSystem routine and asking XGetSelectionOwner( QX11Info::display(), net_wm_cm ); directly works, whether injecting an XSync(False) helps etc. Thanks, Thomas. Latest Kernel update x3.7.3-101.fc17.x86_64 does not update akmod-catalyst package and therefore the appropriate kmod-catalyst package is not updated thus causing desktop effects with opengl to be disabled. The solution is to manually update the kmod-catalyst package for the recent kernel. No akmod-catalyst package is yet available for the recent kernel update. An oversight? sorry we are not responsible for kernel updates or driver updates. |