[en - My English is bad..] When I changed the window dressing of the windows, the top panel disappeared. Buttoms (close, turn, etc) and the title window missing, when I change [ru] Когда я пытаюсь поменять оформление окнон, то верняя часть окна пропадает (там где заголовок окна и кнопки зыкрыть, свернуть, и т.д.). Reproducible: Always Steps to Reproduce: 1. Open System settings. 2. Change theme of windows. Actual Results: [en] The title of window missing. [ru] Пропал верхняя панель окна (где заголовок).
Pot. KWin crashed and for some reason did not restart. Does "alt+tab" still work as expected? Can you select windows with the mouse? From what to what decoration did you change? Did you get a window where you could click on "developer information"? Did this happen immediately after an update (and eventuall w/o logout/login)? In doubt, set the decoration to "oxygen" and run "kwin --replace&" (eg. from alt+f2) If you can no more login with kwin running, edit [1] ~/.kde4/share/config/kwinrc and in [Style] set PluginLib=kwin3_oxygen [1] from VT1, using vim, nano, emacs etc.
>> Did you get a window where you could click on "developer information"? No. >> Does "alt+tab" still work as expected? Can you select windows with the mouse? Yes, Alt + Tab works. Yes, I can move windows (Alt + click mouse on window and move window). >> Did this happen immediately after an update (and eventuall w/o logout/login)? It happend after an update and relogin and change some theme window. After relogin windows is normal. After command "kwin --replace": 1. http://s.wapke.ru/files/20130209-104406.jpg 2. http://s.wapke.ru/files/20130209-104532.jpg Video: http://wapke.ru/other/kwin-bug-window.tar.gz
did that happen exactly during the update? That is 4.10 installed, but 4.9 still running?
>> did that happen exactly during the update? That is 4.10 installed, but 4.9 still running? No. I installed updates and reboot. Later I changed theme of windows. You can see it on the video. >> $ kwin --version >> QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. >> Qt: 4.8.4 >> KDE: 4.10.00 >> KWin: 4.10.00
- is this limited to certain aurorae themes? - please post the output of "qdbus org.kde.kwin /KWin supportInformation" - Does this also happen with xrender or when changing the graphicssystem (between "native" and "raster")?
>> is this limited to certain aurorae themes? This happens when I change some theme of windows (Auroblack, FormaN, Air-Oxegen and some default themes). >> Does this also happen with xrender or when changing the graphicssystem (between "native" and "raster")? Yes. I changed graphicssystem on native and raster, but this bug still happen. >> $ qdbus org.kde.kwin /KWin supportInformation KWin Support Information: The following information should be used when requesting support on e.g. http://forum.kde.org. It provides information about the currently running instance, which options are used, what OpenGL driver and which effects are running. Please post the information provided underneath this introductory text to a paste bin service like http://paste.kde.org instead of pasting into support threads. ========================== Version ======= KWin version: 4.10.0 KDE SC version (runtime): 4.10.00 KDE SC version (compile): 4.10.00 Qt Version: 4.8.4 Options ======= focusPolicy: 0 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 0 delayFocusInterval: 0 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false activeMouseScreen: false placement: 4 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false showDesktopIsMinimizeAll: false rollOverDesktops: false focusStealingPreventionLevel: 1 legacyFullscreenSupport: false operationTitlebarDblClick: commandActiveTitlebar1: 0 commandActiveTitlebar2: 30 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInactiveTitlebar2: 30 commandInactiveTitlebar3: 2 commandWindow1: 7 commandWindow2: 8 commandWindow3: 8 commandWindowWheel: 31 commandAll1: 10 commandAll2: 3 commandAll3: 14 keyCmdAllModKey: 16777251 showGeometryTip: false condensedTitle: false electricBorders: true electricBorderDelay: 150 electricBorderCooldown: 350 electricBorderPushbackPixels: 1 electricBorderMaximize: true electricBorderTiling: true electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true inactiveTabsSkipTaskbar: false autogroupSimilarWindows: false autogroupInForeground: true compositingMode: 1 useCompositing: true compositingInitialized: true hiddenPreviews: 1 unredirectFullscreen: false glSmoothScale: 2 glVSync: true colorCorrected: false xrenderSmoothScale: false maxFpsInterval: 17 refreshRate: 0 vBlankTime: 6144 glDirect: true glStrictBinding: false glStrictBindingFollowsDriver: true glLegacy: false Screens ======= Multi-Head: no Number of Screens: 1 Screen 0 Geometry: 0,0,1366x768 Compositing =========== Qt Graphics System: raster Compositing is active Compositing Type: OpenGL OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Mobile Intel® GM45 Express Chipset OpenGL version string: 2.1 Mesa 9.0.2 Driver: Intel GPU class: i965 OpenGL version: 2.1 Mesa version: 9.0.2 X server version: 1.13.2 Linux kernel version: 3.7.6 Direct rendering: yes Requires strict binding: no GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no OpenGL 2 Shaders are used Loaded Effects: --------------- kwin4_effect_zoom kwin4_effect_slidingpopups kwin4_effect_coverswitch kwin4_effect_minimizeanimation kwin4_effect_screenshot kwin4_effect_slide kwin4_effect_desktopgrid kwin4_effect_flipswitch kwin4_effect_fade kwin4_effect_dialogparent kwin4_effect_highlightwindow kwin4_effect_taskbarthumbnail kwin4_effect_presentwindows kwin4_effect_blur kwin4_effect_logout kwin4_effect_dashboard kwin4_effect_outline kwin4_effect_startupfeedback Currently Active Effects: ------------------------- kwin4_effect_blur Effect Settings: ---------------- kwin4_effect_zoom: zoomFactor: 1.2 mousePointer: 0 mouseTracking: 0 enableFocusTracking: false followFocus: true focusDelay: 350 moveFactor: 20 targetZoom: 1 kwin4_effect_slidingpopups: fadeInTime: 250 fadeOutTime: 250 kwin4_effect_coverswitch: animationDuration: 200 animateSwitch: true animateStart: true animateStop: true reflection: true windowTitle: true zPosition: 900 dynamicThumbnails: true thumbnailWindows: 8 primaryTabBox: true secondaryTabBox: false kwin4_effect_minimizeanimation: kwin4_effect_screenshot: kwin4_effect_slide: kwin4_effect_desktopgrid: zoomDuration: 300 border: 10 desktopNameAlignment: 0 layoutMode: 0 customLayoutRows: 2 usePresentWindows: true kwin4_effect_flipswitch: tabBox: false tabBoxAlternative: false duration: 200 angle: 30 xPosition: 0.330000013113022 yPosition: 1 windowTitle: true kwin4_effect_fade: kwin4_effect_dialogparent: changeTime: 300 kwin4_effect_highlightwindow: kwin4_effect_taskbarthumbnail: kwin4_effect_presentwindows: layoutMode: 0 showCaptions: true showIcons: true doNotCloseWindows: false ignoreMinimized: false accuracy: 20 fillGaps: true fadeDuration: 150 showPanel: false leftButtonWindow: 1 rightButtonWindow: 2 middleButtonWindow: 0 leftButtonDesktop: 2 middleButtonDesktop: 0 rightButtonDesktop: 0 dragToClose: false kwin4_effect_blur: blurRadius: 8 cacheTexture: true kwin4_effect_logout: useBlur: true kwin4_effect_dashboard: brightness: 0.5 saturation: 0.5 blur: false kwin4_effect_outline: kwin4_effect_startupfeedback:
> Auroblack, FormaN, Air-Oxegen Does it happen when switching between the (default, regular) Oxygen, Plastik and Laptop decoration?
>> Does it happen when switching between the (default, regular) Oxygen, Plastik and Laptop decoration? No. It happen when I changing theme of windows between FormaN or Air-Oxygen or Auroblack and sometime with Oxygen. PS: with Oxygen it happen no always.
I strongly assume this one's a dupe of bug #316033 See https://git.reviewboard.kde.org/r/109273/ - if you can, please apply the patch and confirm or deny that this is the same issue, thanks.
*** This bug has been marked as a duplicate of bug 316033 ***