KDE Fullscreen

Hi.
I'm having some problems with KDE and fullscreen apps. For example, while switching a flash movie to fullscreen it gets really slow.
Everything started today. I was playing Pro Evolution Soccer 2010 (L) on Wine, and suddenly (I didn't do anything weird) it started to slowdown. This happened during the game, not in the menu screen.
I restarted the game, and this time the game started slow (not the menu) but after quitting the game the menu screen was also slow.
Now everytime I start the game EVERYTHING is slow from the beginning, both the menu screen and the game itself.
I tried another games (Devil May Cry 4 is now a PAIN) and same result.
After this, fullscreen flash is also slow.
This doesn't happen on another desktop environments such as OpenBox. Neither happens if I disable the kwin effects before playing.
But I don't know what happened... I used to play games on fullscreen with Kwin effects on and they used to work very well. I didn't change any configuration, no -Syu, nothing at all. It just... happened.
Thanks to all.

Just like the way it came, it went away: by doing nothing at all.
Fixed... =/

Similar Messages

  • [KDE] Img viewer fullscreen backgrd color dark grey instead of black

    I've noticed that while running native qt image viewers in KDE to view images in full-screen mode the background color is set to dark grey instead of pure black. If a run a gtk image viewer I get a black background.
    In xfce4 this is corrected since most qt image viewers will display a black background, with the exception gwenview.
    This leaves me wondering if there is some setting I must fiddle with...

    That slider only affects the color of the background in non-fullscreen mode, at least on my end...
    edit: furthermore just tried the Fedora Live CD and this issue is not present. So I can only conclude something must be wrong with KDE setup...
    Last edited by snoxu (2013-05-05 17:40:54)

  • KDE panels in Chrome/Chromium "covers" YouTube controls in fullscreen

    I have a wierd problem. If I start KDE and open a fullscreen YouTube video in Google Chrome or Chromium, the controls not working. I figured out that this is caused by the panels, if I remove a panel for example from the top, I can use the controls on the top of fullscreen YouTube player, and also if I remove the bottom panel, I can use the bottom controls of fullscreen YouTube player. But I don't want to use vertical panels, I use Chromium and I watch several YouTube videos, so I don't know what to do. The panels are just cover the YouTube controls, even if they're set to auto-hide, which makes no sense. And this problem occures only in Chrome and in Chromium, it makes no sense either. Is this a bug of Plasma Desktop or of Chrome/Chromium?
    Any ideas?

    Nobody? If it makes this more clear, that one could say that the image gets pixelated.

  • Error Fullscreen Flash with KDE on 64bits

    Hey guys, my problem is this I have a flash nsplugin pressing the button the video full screen goes away but you can hear, the problem is for the Gnome libraries 32a there any solution without installing a 32-bit subsystem?
    The error output is:
    *** NSPlugin Viewer *** WARNING: unhandled variable 18 (<unknown variable>) in NPN_GetValue()
    (npviewer.bin:12045): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libpixmap.so: wrong ELF class: ELFCLASS64
    (npviewer.bin:12045): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libpixmap.so: wrong ELF class: ELFCLASS64
    (npviewer.bin:12045): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libpixmap.so: wrong ELF class: ELFCLASS64
    (npviewer.bin:12045): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libpixmap.so: wrong ELF class: ELFCLASS64
    (npviewer.bin:12045): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libpixmap.so: wrong ELF class: ELFCLASS64
    (npviewer.bin:12045): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libpixmap.so: wrong ELF class: ELFCLASS64
    (npviewer.bin:12045): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libpixmap.so: wrong ELF class: ELFCLASS64
    *** NSPlugin Viewer *** WARNING: unhandled variable 18 (<unknown variable>) in NPN_GetValue()
    *** NSPlugin Viewer *** WARNING: unhandled variable 18 (<unknown variable>) in NPN_GetValue()
    *** NSPlugin Viewer *** WARNING: unhandled variable 18 (<unknown variable>) in NPN_GetValue()
    *** NSPlugin Viewer *** WARNING: unhandled variable 18 (<unknown variable>) in NPN_GetValue()
    *** NSPlugin Viewer *** WARNING: unhandled variable 18 (<unknown variable>) in NPN_GetValue()
    [11912:11912:11072062493:ERROR:chrome/app/chrome_dll_main.cc(248)] Gdk: gdk_cursor_new_from_pixbuf: assertion `0 <= x && x < gdk_pixbuf_get_width (pixbuf)' failed
    [11912:11912:11072121399:ERROR:chrome/app/chrome_dll_main.cc(248)] Gdk: gdk_cursor_new_from_pixbuf: assertion `0 <= x && x < gdk_pixbuf_get_width (pixbuf)' failed
    [11912:11912:11078768692:ERROR:chrome/app/chrome_dll_main.cc(248)] Gdk: gdk_cursor_new_from_pixbuf: assertion `0 <= x && x < gdk_pixbuf_get_width (pixbuf)' failed
    [11912:11912:11086161594:ERROR:chrome/app/chrome_dll_main.cc(248)] Gdk: gdk_cursor_new_from_pixbuf: assertion `0 <= x && x < gdk_pixbuf_get_width (pixbuf)' failed
    [11912:11912:11087481569:ERROR:chrome/app/chrome_dll_main.cc(248)] Gdk: gdk_cursor_new_from_pixbuf: assertion `0 <= x && x < gdk_pixbuf_get_width (pixbuf)' failed
    [11912:11912:11087678971:ERROR:chrome/app/chrome_dll_main.cc(248)] Gdk: gdk_cursor_new_from_pixbuf: assertion `0 <= x && x < gdk_pixbuf_get_width (pixbuf)' failed
    [11912:11912:11087902480:ERROR:chrome/app/chrome_dll_main.cc(248)] Gdk: gdk_cursor_new_from_pixbuf: assertion `0 <= x && x < gdk_pixbuf_get_width (pixbuf)' failed
    [11912:11912:11088324635:ERROR:chrome/app/chrome_dll_main.cc(248)] Gdk: gdk_cursor_new_from_pixbuf: assertion `0 <= x && x < gdk_pixbuf_get_width (pixbuf)' failed
    [11912:11912:11088553302:ERROR:chrome/app/chrome_dll_main.cc(248)] Gdk: gdk_cursor_new_from_pixbuf: assertion `0 <= x && x < gdk_pixbuf_get_width (pixbuf)' failed
    [11912:11912:11088768123:ERROR:chrome/app/chrome_dll_main.cc(248)] Gdk: gdk_cursor_new_from_pixbuf: assertion `0 <= x && x < gdk_pixbuf_get_width (pixbuf)' failed
    [11912:11912:11093912862:ERROR:chrome/app/chrome_dll_main.cc(248)] Gdk: gdk_cursor_new_from_pixbuf: assertion `0 <= x && x < gdk_pixbuf_get_width (pixbuf)' failed
    *** NSPlugin Viewer *** WARNING: unhandled variable 18 (<unknown variable>) in NPN_GetValue()
    Thank you in advance
    Last edited by madtrap (2010-08-11 21:02:37)

    I have this bug: https://bugzilla.redhat.com/show_bug.cgi?id=608957#c6
    But described workaround does not work for me.
    KDE 4.5.1, effects on,
    xf86-video-intel 2.12.0-1,
    xorg-server 1.8.1.902-1

  • Wine and KDE hotkeys

    I LIKE the KDE shortcuts so I don't want to permanently disable them.  I would like them to be disabled whenever I run games in fullscreen under wine.  For instance:  Ctrl-F2 switches to desktop 2 which is great...  Accept when I'm playing Diablo II.  Can anyone think of any creative way to have shortcuts toggled on and off as I run wine?

    simongmzlj wrote:You could start wine games in another xserver...
    Very cool idea!  Google found me this: http://ubuntuforums.org/showthread.php? … b&t=634067
    This is way simpler than I thought it'd be.  Thanks.

  • Compiz and kde kicker panel

    Hello, I am having a problem using compiz with kde's kicker panel.  I have my kicker set on auto-hide and when I enable the option in CCSM "unredirect fullscreen windows" my screen flickers when the kicker panels is raised.   This problem dissapears when I again unmark the CCSM option.
    I am using kde 4.6.2 and nvidia 270.41.06-1
    Any help or workarounds would be appreciated.

    From the Compiz Fusion wiki:
    Should programs be allowed to draw directly into a fullscreen window, bypassing the compositing process? This can significantly increase the performance of fullscreen games and videos, but may also cause visual glitches. If you don't know which setting is right for your use case, it's safer to leave this option disabled.
    Seems like this is an expected issue, since Plasma renders itself independently of other apps and windows and therefore wouldn't comply with Compiz options (accept those found under "KDE Compatability").  I'm not sure how much of the issue would be your video driver and how much would be the window manager.

  • [SOLVED] Compositing causes screen to freeze in KDE 4.7 with Nouveau

    Hello,
    since the upgrade to KDE 4.7 screen gets [partial] freezes for several seconds (differs) especialy when some repainting is to be done (scrolling in Rekonq/KWrite, opening and closing tabs in Rekonq, playing video in KDE). Usually I can stil see moving the mouse, though the cursor doesn't change on links etc. Also repainting of plasma widgets freezes.
    I'm using nouvea driver for 7600 GS video card:
    multilib/lib32-nouveau-dri 7.11-1
    extra/nouveau-dri 7.11-1
    extra/nouveau-firmware 20091212-4
    extra/xf86-video-nouveau 0.0.16_git20110726-1
    And get foloving in dmesg after a freeze:
    [43244.176746] [drm] nouveau 0000:04:00.0: vm flush timeout: 0x00000022
    and in xorg.log:
    [ 43235.667] [mi] EQ overflowing. The server is probably stuck in an infinite loop.
    Everything is ok with disabled compositing, or with nvidia driver, thogh I do not prefer to use it since it lacks KMS and is proprietary.
    Any idea which splendid new feature of KDE 4.7 causes this? And how to turn it off so I can use compositing again? I tried diasbling new GL 2.0 shaders and setting worser filter in advanced Plasma settings but it didn't help.
    I'll happily provide more info, if I am pointed which one.
    Thank you.
    Last edited by Nicky726 (2011-08-13 10:20:57)

    3-D is currently an unsupported use-at-your-own-risk feature in nouveau. That leads me to conclude that neither project (kwin or nouveau) can be blamed at the moment.
    I had irrecoverable freezes (had to ssh in and reboot) on my 9800 GT while playing videos fullscreen. Turning off the option to disable 3-D for full screen applications solved that problem for me. Compared to that, I'm okay with the temporary one-second freezes (which I see as well).
    Your best bet is to play around and isolate which effects cause the issues for you. Start with no desktop effects checked and work your way up, adding one effect at a time. Maybe you'll discover the culprit that way. Hope that helps.

  • Configure KDE panels to stay on secondary screen.

    Greetings.
    I got a tiny problem with KDE. To be more specific: The panels won't stay put.
    Here is my simple setup:
    I got two monitors connected to a Radeon GPU (Using proprietary driver aur/catalyst-total version 13.4). Configured with help of ATI configuration tool. See attached Xorg config below for details.
    To this, I got two panels and a few widgets/plasmoids for each screen. They're both at the bottom of the screen. Auto hiding is turned on.
    The problem:
    Whenever the secondary monitor is deactivated, or when I run a fullscreen application, the panels and widgets/plasmoids on the screen that deactivates will move over to the active screen. That is okay. They're supposed to do that.
    Once the screen reactivates, or when the fullscreen application quits, the panels and widgets/plasmoids in question won't move back again.
    I have to unlock, manually move panels and widgets/plasmoids back to the other screen, and relock them. This have to be repeated each and every time  a screen deactivates or when the system runs a full screen application.
    What I want:
    I want the panels and widgets/plasmoids to move back to their original positions once the other screen is reactivated/full screen application quits.
    Suggestions?
    My xorg.conf follows:
    Section "ServerLayout"
    Identifier "aticonfig Layout"
    Screen 0 "aticonfig-Screen[0]-0" 0 0
    EndSection
    Section "Module"
    EndSection
    Section "Monitor"
    Identifier "0-DFP2"
    Option "VendorName" "ATI Proprietary Driver"
    Option "ModelName" "Generic Autodetecting Monitor"
    Option "DPMS" "true"
    Option "PreferredMode" "1680x1050"
    Option "TargetRefresh" "60"
    Option "Position" "0 0"
    Option "Rotate" "normal"
    Option "Disable" "false"
    Option "Primary" "true"
    EndSection
    Section "Monitor"
    Identifier "0-CRT1"
    Option "VendorName" "ATI Proprietary Driver"
    Option "ModelName" "Generic Autodetecting Monitor"
    Option "DPMS" "true"
    Option "PreferredMode" "1280x1024"
    Option "TargetRefresh" "60"
    Option "Position" "1680 26"
    Option "Rotate" "normal"
    Option "Disable" "false"
    EndSection
    Section "Device"
    Identifier "aticonfig-Device[0]-0"
    Driver "fglrx"
    Option "Monitor-DFP2" "0-DFP2"
    Option "Monitor-CRT1" "0-CRT1"
    BusID "PCI:0:1:0"
    EndSection
    Section "Screen"
    Identifier "aticonfig-Screen[0]-0"
    Device "aticonfig-Device[0]-0"
    DefaultDepth 24
    SubSection "Display"
    Viewport 0 0
    Virtual 2960 2960
    Depth 24
    EndSubSection
    EndSection
    Last edited by SysGhost (2013-10-08 05:42:44)

    kokoko3k wrote:It is (or it is related) a long standing bug:
    https://bugs.kde.org/show_bug.cgi?id=293453
    Understood.
    Looks like I have to wait it out and "hope" the bug will be resolved within my lifetime

  • Exclusive Fullscreen mode

    Hi
    Whilst i can switch my windows into fullscreen mode via graphicdevice that doesn't make Windows, so for platform inter exchangability, i'm emulating a fullscreen setting, by extending the window beyond the bounds of the screen, which works grand.
    Regardless of GraphicsDevice way or the (dodgy) Windows way, i can't get something that hides the kicker in KDE (3.1 or 3.0.5 or 3.0.3) or the taskbar.
    So my question how do i get the OS (or whatever) to return a true on GraphicsEnvironment's .isFullScreenSupported()?
    OR
    How do I get something like an "Always on top" setting, which would (in theory) go over the top of the taskbar / kicker.
    If more detail is required on what the problem is, grab the code from http://naiv.sourceforge.net , and check it out.
    The code in question is in NAIV_Viewer.java at setupFullscreenSupport().
    Any help would be appreachiated.
    Christian chakkerz Unger

    Check out the Java Tutorial on Full Screen Exclusive mode in the tutorials homepage. You will need JDK1.4 for this.
    As for the Always on top code, I have some code that a kind person named Mitch Goldstein posted here in the forum. You can email him for this code but ask someone in this forum for his email address as I dont have it.
    Alternatively, look at:
    http://forum.java.sun.com/thread.jsp?forum=25&thread=230042
    Hope this helps
    Riz

  • Compiz is 12 times faster than kwin on KDE. Is it normal?

    Hello. Just tried compiz on kde, and I'm impressed: it consumes just 1% of cpu, while kwin was consuming 12% on Core2Duo E6550 with NVidia 8600.
    Is it normal, that kwin is so slow?

    Thank you for the answer.
    If it is not normal, I will try to dig something on this. Maybe I need some xorg extension.
    Worth to mention, that kwin with XRender consumes just 3%. The problem appears, when using OpenGL.
    2karol
    It is not big deal with those 10%, but sometimes animation isn't smooth. Also there are some misterious speaks in cpu load, while playing 720p in mplayer with VDPAU in window mode. Mplayer can consume up to 30% with kwin, but only 3% with compiz. Moreover, video always flickers, when control bar appears in fullscreen.
    There are no such issues with compiz.
    I thought, that this is normal, but now I see, that I need to search for bug reports on this.
    Last edited by eDio (2010-09-12 08:35:45)

  • [SOLVED] snapshot of window in KDE

    Hello.
    How do I make a snapshot of window in KDE by a keyboard shortcut? I tried Alt+PrintScreen and it doesn't work. By PrintScreen I can capture the fullscreen (by Ksnapshot), but I don't know how to capture a window by the shortcut...
    Anyone can help me?
    Thanks a lot!
    Last edited by ancient_archer (2011-10-20 13:45:13)

    Well, in fact I changed the command in KDE Control Panel (Shortcuts and gestures) → Own shortcuts → Preset Actions → and on the right on the Action card, I modified the command to: ksnapshot --current.
    Now it snapshot only a current window, not the whole desktop after pressing the PrintScreen. Problem solved :-)
    Last edited by ancient_archer (2011-10-20 13:49:28)

  • Firefox blacks out on fullscreen

    I just noticed this as I don't use fullscreen firefox almost ever, so i can't say when it began.
    There are actually three different "usecases" that i compared doing the same with extra/chromium:
    - activate fullscreen (pressing F11) on whatever page, right click on whatever point -> all screen flashes black, except for the right click menu area [chromium too, but a bit faster]
    - deactivate fullscreen from a previously fullscreened page -> all screen flashes black, no except and longer than first case [chromium too, but a bit faster]
    - activate fullscreen, middleclick -> all screen flashes black, no except and longer than first case [chromium doesn't show this problem]
    I'm using extra/kde and extra/nvidia...
    Note about third case: i changed the middleclick configs in firefox as said in http://wiki.archlinux.org/index.php/Fir … ick_errors and that could be the reason why firefox does it and chromium doesn't (i didn't change anything there)
    I apologize if a thread already existed but i couldn't find anything
    EDIT: forgot to mention that the thingy for fast scrolling and relative problem appear only if the page is long enough to be scrolled. Don't pick Google Search as test for that, but something like Slashdot or so...
    Last edited by lucak3 (2010-09-29 15:51:58)

    I fear it's KWin effects fault: deactivating compositing(*) makes firefox behave perfectly on those cases...
    I'll try to see which effects are at fault
    *: to make it fast, click Meta+F12 (Meta is usually Alt+Shift) or type this in a bash shell "qdbus org.kde.kwin /KWin org.kde.KWin.toggleCompositing" (without double quotes ofc)

  • [Solved] Intel full screen scaling in KDE

    I can't seem to change the full screen scale on my intel onboard card with KDE. The instruction on the Intel Arch Wiki only works in Gnome.
    Edit: The second command in the wiki page works!
    Last edited by nghiavd (2011-01-08 02:54:22)

    sredna wrote:Never heard of that before := I can run the commands to change the mode witout error, but i do not know why I would want to. using dragonplayer fullscreen does not seem to differ.
    That's because dragonplayer scales the video to your screen's native resolution. This option matters when you're running something with a lower resolution that the screen's native. Though I don't see why KDE vs. Gnome vs. anything would matter here. Unless KDE is being stubborn and is overriding what you set on the commandline. For me that would be one further reason to move away from KDE.

  • Future of QT and KDE

    So Qt5&KDE5 will be a horrible mess if:
    1. Nokia/Trolltech and community drops support for X11
    2. Kwin drop support for X11
    3. Nokia/Trolltech and community drops support for QtSvg
    4. OpenGL Qt Graphics system is buggy
    Dropping support for X11 isn't happening anytime soon as long as there is no offical support from Nvidia/Ati. That pretty much rules out the 1st and 2nd. I'm not saying that it's impossible but unlikely.
    QtSvg is important for KDE so they will most likely maintain it, 3rd point ruled out. I don't see how inactive Qt windows using OpenGL cause any problems with games that are most likely run in fullscreen mode, the 4th.
    Just to make clear, I don't know much about the situation but I highly doubt that KDE and Qt developers are intentionally trying to destroy the desktop.
    Last edited by Teho (2011-09-06 14:54:49)

    Somethings that I am excited about on and off Qt campus
    1. It appears QML2 will use v8
    2. v8 for QtScript
    3. Mozilla is building a Qt4 native port <-- I tested it out works for the most part
        visuals are a little messed up. Could this mean that a Native Qt4 Gecko widget
        might be possible? Don't know maybe
    4. We might even see a QtWebkit that uses v8!!!!
    v8 in Qt is what I am most excited about. I use nodejs for my web development
    and that uses v8, but I also use Ogre3D as my main 3D graphics engine on top
    of Qt. My hopes are to be able to use Javascript when ever and where ever I see fit
    and have it just work. With one javascript engine. Be it Desktop, Game, Multimedia
    or Web Applications. Granted it's possible now, but the situation would be better
    if I didnt have to use v8 for this and JSCore for that.
    let me say it a few more times v8, v8, v8!!!!!
    I am also looking forward to a OAuth 2 library then I could do all kinds of cool-things
    with Google Storage for Developers
    Last couple of months I have really gotten into doing stuff with Cloud Storage and what not.
    Ill be doing alot of stuff in regards to Google services and YES I am a google Fan boy.. Love Google
    Here have a Skia Example Won't find many of these on the web that are not directed at android.
    #include "SkCanvas.h"
    #include "SkGraphics.h"
    #include "SkImageEncoder.h"
    #include "SkString.h"
    #include "SkTemplates.h"
    int main (int argc, char * const argv[]) {
    SkAutoGraphics ag;
    //Output filename
    SkString path("skhello.png");
    //Set Text To Draw
    SkString text("Hello, World");
    SkPaint paint;
    //Set Text ARGB Color
    paint.setARGB(255, 255, 255, 255);
    //Turn AntiAliasing On
    paint.setAntiAlias(true);
    //Set Text Size
    paint.setTextSize(SkIntToScalar(30));
    //Set Image Width & Height
    SkScalar width = 800;
    SkScalar height = 600;
    SkBitmap bitmap;
    bitmap.setConfig(SkBitmap::kARGB_8888_Config, width, height);
    bitmap.allocPixels();
    //Create Canvas
    SkCanvas canvas(bitmap);
    canvas.drawARGB(255, 101, 33, 131);
    //Text X, Y Position Varibles
    SkScalar x = 80;
    SkScalar y = 60;
    canvas.drawText(text.c_str(), text.size(), x, y, paint);
    //Set Style and Stroke Width
    paint.setStyle(SkPaint::kStroke_Style);
    paint.setStrokeWidth(10);
    //Draw A Rectangle
    SkRect rect;
    paint.setARGB(255, 0, 0, 0);
    //Left, Top, Right, Bottom
    rect.set(50, 100, 200, 200);
    canvas.drawRoundRect(rect, 20, 20, paint);
    //Draw A Line
    canvas.drawLine(10, 300, 300, 300, paint);
    //Draw Circle (X, Y, Size, Paint)
    canvas.drawCircle(100, 400, 50, paint);
    //Same Image (file, bitmap, image_type, quality)
    SkImageEncoder::EncodeFile(path.c_str(), bitmap, SkImageEncoder::kPNG_Type, 100);
    return 0;
    Larger View
    Last edited by zester (2011-09-06 16:46:53)

  • Strange fullscreen behaviour

    Hey guys,
    First I want to say that I use KDE SC 4.4.2.
    I have some strange behaviour with fullscreen and any OSD by KDE.
    For example when I watch a movie with kaffeine and change the speaker level the upcoming osd is causing a short black screen. The same happens when there is a notification by knotify. The same thing happens when I have VirtualBox in Fullscreen or anything else.
    The Problem disappears when I toggle Compositing of, so it seems to have to do anythning with kwin I guess?
    I hope you can help me
    Locke

    Pattie,
    Not to answer for Simeon, but this is different behavior in PsCS6.  Say you scale two  text layers (for example- 10 pt scaled 200%) and commit the scale. When you target each layer individually, the pt size reflects the scale (so it will appear around 20 pt). However. if you target BOTH text layers the font size is indicated as 10 pt - the original size before the scale. One would expect if you target 2 text layers of same font and size, the Character Panel would show the correct size, as happens in PsCS5.
    Steps to reproduce:
    Open default RGB 8 bit document.
    Select Type tool at default settings 12pt type. Type a word and commit type.
    Type another word at same font and commit (you’ll now have two text layers, same font and size)
    Target both text layers and Edit>Transform>Scale 200%. Commit the transform.
    When each layer is targeted individually, the Type Tool Option bar (or Character Panel) shows the new, scaled size of 24pt
    Shift click to target both the 24pt text layers… now Type Tool Option bar reverts to show 12 pt.
    Expected behavior: that the Option Bar would show the new pt size of the two layers.

Maybe you are looking for