Tag Info

Hot answers tagged

9

KDE Control Modules Command: kcmshell4 --help Will tell: Usage: kcmshell4 [Qt-options] [KDE-options] [options] module A tool to start single KDE control modules Generic options: --help Show help about options --help-qt Show Qt specific options --help-kde Show KDE specific options --help-all ...


6

As described in the official Kwin documentation, a good way to go would be to try this either on a running terminal application or on a virtual console (i.e.: Ctrl+Alt+F1), : DISPLAY=:0 kwin --replace


5

After a serious bit of Googling I came across this post: The only purpose of this file is to be later in the link order than (nvidia's) libGL, thus being initialized by the dynamic linker before it, allowing it to set __GL_YIELD=NOTHING soon enough for libGL to notice it. Given that the quote is from a certain M-Graesslin, Martin is the chief ...


4

I had the same problem with 3.10 kernel, fglrx 13-8 beta, and kde 4.11. Here is what worked: Run the driver installer with the extract option: ./amd-catalyst-13.8-beta1-linux-x86.x86_64.run --extract [dirname]` Then cd [dirname] and open file "common/lib/modules/fglrx/build_mod/firegl_public.c". Find line 821 or 822. Change: root = ...


4

Try System Settings - Display and Monitor - Multiple Monitors. The setting Show Unmanaged Windows on allows you to select a display or use the display the mouse pointer is on. I had this problem but only when I first started a session, anything I ran would always initially open on the second screen (which is a TV and usually turned off) If you're having ...


3

Your drivers are corrupted - there's a lot of bugs in 13.8, such as lack of access rights to procfs / proc / ati / ... are patches on it, but these drivers are highly "inappropriate" for example, memory leaks, etc.. : P I would recommend for now 13.3 beta3 - by our NeteXt'73 - I built Catalyst 13.3 beta3 v4 so, and would ideally operate under 3.10.x kernels, ...


2

The ability to show borders on maximized windows was removed from kwin in KDE 4.11. You can find more information about this decision in bug 299245. Basically, the implementation was a hack that caused multiple bugs, and the developer said that the proper place for this feature was in the decoration rather than in kwin. So, this feature was added to the ...


2

I've been using Unity-2D with KWin for about two weeks now. In the login screen, choose Unity-2D as your session type. Install the kde-window-manager package to get kwin. Then fire up a terminal and run kwin --replace &!. You'll probably want the systemsettings and kde-config-gtk packages for configuration.


2

Press Ctrl+Alt+F1. Log in. Type killall kwin. Press Ctrl+Alt+F7. Quit all open applications until a terminal becomes visible. Hover the mouse over the terminal application. Type kwin &. What's that, no terminal application open? Tough - you'll just have to reboot.


2

Similar to Robin Green's answer, but this does not require a terminal window to be open already. Instead, specify the display in which to start kwin from tty1. Hence, Press Ctrl+Alt+F1 to access a terminal. Log in. Type killall kwin. Then, type in DISPLAY=:0 kwin. Press Ctrl+Alt+F7 to change back to your primary display.


2

Auto stretch ? KDE Forums / Windows auto-resize width : http://forum.kde.org/viewtopic.php?f=66&t=97839 Window rules Configure settings specifically for a window System Settings > Window Behavior > Window Rules Special Window/Application Settings Right click the window border > Advanced > Special Window/Application Settings > Size & Position ...


1

As @warwaruk said, you already have KWin. "Plasma" is the name of the desktop environment that uses KWin, so you should select Plasma when you log in. You said "I have installed KDE by command sudo apt-get install kde-window-manager". If you want the full KDE environment, you should install kubuntu-desktop or at least kde-workspace, to be sure you're not ...


1

In the "windows behaviour" settings, you have to enable "Active screen follows mouse pointer". (approximate translation from French but I'm sure you'll find it). This way, by default, windows will open on the current screen. (except some rare specific apps like VLC which use the last used screen).


1

I have the same problem. Nvidia 660ti KDE 4.8 and 304 drivers. I ran some tests with different configurations (Nvidia settings and KWin) and it is related to the PowerMizer settings. On adaptive, I get tearing both on desktop and video (both with VDPAU and without). On max performance, tearing is gone. Hope it helps.


1

As I do not have enough information to write a comment, I am forced to write an answer. First of all, I see what you mean and often ran in the situation of having no space left, especially if experiment with small installs. I noticed different issues, but none of the issues 2. or 3. In case of KDE Plasma for example suddenly all my desktop widgets were ...


1

kwin does have a DBUS interface, but it doesn't do what you're describing. To take a look at the calls that are available to you, run qdbusviewer (which be available in your distro's repository), choose the Session Bus tab, and search for kwin in the search box. From there, choose org.kde.KWin on the left panel, and on the right panel, you'l see KWin -> ...


1

The AMD Catalyst software has an option to reduce tearing. Open a terminal and type gksudo amdcccle, then find the section for reducing tearing and check the option. Additionally, I should mention that I had some tearing issues with VLC and Totem a while ago (before the 13.1 driver was released), but using smplayer instead of VLC dramatically improved my ...


1

When searching with the error message Gdk: IA__gdk_window_thaw_updates: assertion `impl_window->update_freeze_count > 0' failed A hit: http://racket-lang.org/irc-logs/20111018.txt 14:52 mithos28: There is a known bug with gnome 3. 14:52 mithos28: It is fixed in the nightlies, and will be in the release coming out soon. Versions Ubuntu ...



Only top voted, non community-wiki answers of a minimum length are eligible