Window Manager Warning In Gnome

I'm running Arch 2010.05 i686 With just the gnome base installed 'pacman -S gnome' but also some other apps and dependencies.
I noticed when I log out of Gnome into the console I see these two messages;
Window Manager Warning: Got a request to focus the no_focus_window with a timestamp of 0, this shouldn't happen
Window Manager Warning: Current Time used to choose focus window: focus window may not be correct
I'm using the default WM for Gnome Metacity, I haven't made any changes to Gnome...
THANKS

skottish wrote:Does everything work properly? If so, the messages can be ignored.
Everything seems to work properly, but if they work properly then we shouldn't be seeing messages telling us something isn't working correct should we...
So something is up and no matter what it is, even if it's a simple bug reporting an incorrect error, I'd like to fix if it I can, unless this might be at the code level and needs a patch, meaning this isn't going to be fixed until an update...
I appreciate your reply, but you telling me to ignore this means what? That you understand what is going on and why this is happening and that there is nothing I can do to fix it?
THANKS
Last edited by DasFox (2010-11-28 03:22:46)

Similar Messages

Metacity crashes - Window manager warning: Received a _NET_WM_MOVERES

Hello!
I need help. I tried to install xmonad, but instead of this metacity has crashed and it doesn't executes on the startup. I can execute it manually and it works, but I get such an error:
Window manager warning: Failed to read saved session file /home/zayac/.config/metacity/sessions/10b6d74b675d6fdde8126124551975668900000060560000.ms:
Failed to open file '/home/zayac/.config/metacity/sessions/10b6d74b675d6fdde8126124551975668900000060560000.ms': No such file or directory
How can I avoid this dependency as there are no /home/zayac/.config/metacity/ directory. In addition I need it to execute on startup.
Thanks in advance.
Last edited by zayac (2009-12-19 18:10:40)

skottish wrote:Does everything work properly? If so, the messages can be ignored.
Everything seems to work properly, but if they work properly then we shouldn't be seeing messages telling us something isn't working correct should we...
So something is up and no matter what it is, even if it's a simple bug reporting an incorrect error, I'd like to fix if it I can, unless this might be at the code level and needs a patch, meaning this isn't going to be fixed until an update...
I appreciate your reply, but you telling me to ignore this means what? That you understand what is going on and why this is happening and that there is nothing I can do to fix it?
THANKS
Last edited by DasFox (2010-11-28 03:22:46)

[SOLVED] Odd window manager problem...

I have installed Arch and a full Gnome DE. However when I start gnome, I get an odd window manager. I tried metacity and metacity --replace in a terminal, but I just get "Window manager warning: Screen 0 on display ":0.0" already has a window manager"
Here is what it looks like:
Any way I can get some metacity going?
Edit: [SOLVED]
I just put metacity as startup application and restarted. Still not sure what that window manager was, but I'll be okay I guess...
Last edited by phohammer (2010-03-03 02:59:43)

sand_man wrote:
haha you had gnome running with twm as the window manager instead of metacity.
You need to put 'exec gnome-session' in your .xinitrc file.
twm huh? Well that's a new one for me!
I tried to do that but the .xinitrc file didn't exist yet and I wasn't sure if I should make it...I think I tried ~/.xinitrc . Would it be in another directory?

Openbox as gnome window manager doesn't work

So, this is my first time with arch, and I have some experience with Ubuntu so I installed the gnome winow manager to start.
It looks fine but I like some themes and how openbox looks/works more. I decided saw in a wiki that you can make it the window manager for gnome, so I followed the instructions in the wiki, loged out then back in, but nothing happens. Still the same old gnome.
bash-3.2# gconftool-2 -g /desktop/gnome/session/required_components/windowmanager
openbox
bash-3.2# cat /usr/share/applications/openbox.desktop
[Desktop Entry]
Type=Application
Encoding=UTF-8
Name=OpenBox
Exec=openbox
NoDisplay=true
# name of loadable control center module
X-GNOME-WMSettingsModule=openbox
# name we put on the WM spec check window
X-GNOME-WMName=OpenBox

I believe you want it to be openbox-gnome-session
http://icculus.org/openbox/index.php/Help:GNOME/Openbox
Last edited by thayer (2009-02-02 00:22:18)

X11 dual head - want to get window manager (gnome) on one screen only

What I want sounds simple, but I just can't get it done... Hope anyone is able to help me!
What I've got:
Four monitors (two at each of my nVidia graphic cards). Both devices are configured using nVidia's Twinview, giving me two virtual screens (:0.0 and :0.1).
I can use xinerama to get one huge desktop, but this doesn't work well, as the borders between two screens of the same device are no longer recognized in this case, causing windows to always span over two monitors on maximization.
I can also not use xinerama, giving me two independant gnome session.
What I want:
I want gnome to only start on one screen (i.e. two monitors), leaving the other screen blank but available. They don't need a WM as they will run nothing but a fullscreen mplayer or an xterm that will periodically output some stuff. I actually don't even need input devices for the second screen and it would be good if the mouse was restricted to the gnome-screen.
However, I didn't manage to make gnome start on only one screen. I don't care if it's done using one xsever with two screens attached or if I can do it starting a second xserver, I just want it resolved in some way.
I've tried to restrict gnome to :0.0 by setting the DISPLAY variable or giving gnome-sessions --display option. Both to no avail. When trying to start a second xsever (different layouts, each using one of the screens), my original screen becomes all white and on the second screen nothing happens. Any ideas?

What I want sounds simple, but I just can't get it done... Hope anyone is able to help me!
What I've got:
Four monitors (two at each of my nVidia graphic cards). Both devices are configured using nVidia's Twinview, giving me two virtual screens (:0.0 and :0.1).
I can use xinerama to get one huge desktop, but this doesn't work well, as the borders between two screens of the same device are no longer recognized in this case, causing windows to always span over two monitors on maximization.
I can also not use xinerama, giving me two independant gnome session.
What I want:
I want gnome to only start on one screen (i.e. two monitors), leaving the other screen blank but available. They don't need a WM as they will run nothing but a fullscreen mplayer or an xterm that will periodically output some stuff. I actually don't even need input devices for the second screen and it would be good if the mouse was restricted to the gnome-screen.
However, I didn't manage to make gnome start on only one screen. I don't care if it's done using one xsever with two screens attached or if I can do it starting a second xserver, I just want it resolved in some way.
I've tried to restrict gnome to :0.0 by setting the DISPLAY variable or giving gnome-sessions --display option. Both to no avail. When trying to start a second xsever (different layouts, each using one of the screens), my original screen becomes all white and on the second screen nothing happens. Any ideas?

Maximize Application without Window Manager

What I'd like to do is use xwininfo and wmctrl to maximize an application in X without a window manager. Here is what I've worked out:
#!/bin/sh
# ~/.xinitrc
# Executed by startx (run your window manager from here)
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fi
# exec gnome-session
# exec startkde
# exec startxfce4
# ...or the Window Manager of your choice
MAXIMIZE_ID=$(xwininfo -root -child | grep "st-256color" | grep -o "^[[:space:]]*0x[[:alnum:]]*" | grep -o "0x[[:alnum:]]*")
MAXIMIZE_WIDTH=$(xwininfo -root | grep "Width" | grep -o "[[:digit:]]*")
MAXIMIZE_HEIGHT=$(xwininfo -root | grep "Height" | grep -o "[[:digit:]]*")
while [ "$MAXIMIZE_ID" = "" ]
do
MAXIMIZE_ID=$(xwininfo -root -child | grep "st-256color" | grep -o "^[[:space:]]*0x[[:alnum:]]*" | grep -o "0x[[:alnum:]]*")
if [ "$MAXIMIZE_ID" != "" ]
then
wmctrl -i -r $MAXIMIZE_ID -e 0,0,0,$MAXIMIZE_WIDTH,$MAXIMIZE_HEIGHT
fi
done &
exec st
As intended it maximizes the st terminal. However, the terminal simply hangs there, I can provide it with no input, any clues as to what I'm missing and/or doing incorrectly? I realize st uses the geometry parameter, I'm only using it here as an example application as not all applications support that parameter.
Last edited by grimpirate (2014-08-12 19:20:00)

It's much more complex than that. Wmctrl requires a EWMH compliant window manager. Many of the lightest weight WMs are not EWMH compliant.
Is this just for st, or do you want all windows maximized? Does st have a 'geometry' flag?
You could write a WM that does nothing but fullscreen every window that is mapped in about a dozen lines of code. Note, however, that without a WM, windows will generally not properly be assigned the input focus - one result is that cursors on most terminals will remain 'hollow'. For the cost of one or two more lines of code, this new WM could also set input focus appropriately.
EDIT: st does have a geometry flag, just use that.
Also, your 'grep | grep' pipe could just be "awk '/Width/ { print $2;}'", or two get both width and height in one go:
xwininfo -root | awk '/Width/ { printf "%s", $2;} /Height/ {printf "x%s", $2;}'
Though this wouldn't be quite right for a st geometry string as that takes rows and columns, not pixels.
EDIT2: your solution will also fail miserably for two other reasons. There is not point in initializing the MAXIMIZEID variable before the loop starts - because if there actually are any windows there, the while loop will never run. Also, without a sleep command, or something, all that while loop will be very good for will be to turn your cpu into a frying pan (100% cpu use -> heat).
Here's a very plain WM that will do the same thing without melting your CPU:
#include <X11/Xlib.h>
int main(void) {
Display *dpy;
if(!(dpy = XOpenDisplay(0x0))) return 1;
XEvent ev;
int scr = DefaultScreen(dpy);
int sw = DisplayWidth(dpy, scr);
int sh = DisplayHeight(dpy, scr);
Window w, root = RootWindow(dpy, scr);
XSelectInput(dpy, root, SubstructureRedirectMask);
while (!XNextEvent(dpy, &ev)) {
if (ev.type == MapRequest && (w=ev.xmaprequest.window)) {
XMoveResizeWindow(dpy, w, 0, 0, sw, sh);
XMapWindow(dpy, w);
XSetInputFocus(dpy, w, RevertToPointerRoot, CurrentTime);
XFlush(dpy);
return 0;
Last edited by Trilby (2014-08-13 13:03:59)

My window manager only starts 50% of the time.

Hello all, I installed arch about a week ago and it has run perfectly.
Unfortunately about 2 days ago I have a strange issue that I can't seem to diagnose.
When I boot my arch install, (dual boot win8 with seperate hard drive), and login using slim, around 50% of the time everything will load up and my panel will show etc.
The other 50% of the time the desktop brings up just my mouse, I'm using a tiling manager and the hotkeys dont work either which makes me think that .xinit isn't being executed, yet other things in there work fine.
bspwm is my window manager, slim is my login manager, I looked in xorg.0.log a few times and couldn't find anything. Any help would be appreciated!
(Sorry if this is in the wrong place, also ask for any files you need)

Trilby wrote:
Chazza, using exec is common, but not at all necessary. Without the exec, the parent shell process just hangs around - this is unneeded, but it does no harm. One can even put many WMs one after the other with no exec command to run one right after the other. Or put a few (or just one) WM in a loop with no 'exec' in order to restart the WM without restarting X (this can be seen in the dwm wiki for one example).
Toqoz, please post (or link to) 2 xorg logs: 1 for a successful run, and one for the failed attempt.
Heres my /var/log/Xorg.0.log file for a successful boot, couldn't find the xorg folder in ~/.local/share/xorg.
[ 15.806]
X.Org X Server 1.17.1
Release Date: 2015-02-10
[ 15.806] X Protocol Version 11, Revision 0
[ 15.806] Build Operating System: Linux 3.18.6-1-ARCH x86_64
[ 15.806] Current Operating System: Linux qhost 3.19.2-1-ARCH #1 SMP PREEMPT Wed Mar 18 16:21:02 CET 2015 x86_64
[ 15.806] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=db8748e8-ddcb-48c6-ac0c-e8560a1c3848 rw quiet
[ 15.806] Build Date: 14 March 2015 06:45:50PM
[ 15.806]
[ 15.806] Current version of pixman: 0.32.6
[ 15.807] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 15.807] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 15.807] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Apr 2 20:30:04 2015
[ 15.871] (==) Using config file: "/etc/X11/xorg.conf"
[ 15.872] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 15.872] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 16.049] (==) ServerLayout "Layout0"
[ 16.049] (**) |-->Screen "Screen0" (0)
[ 16.049] (**) | |-->Monitor "Monitor0"
[ 16.050] (**) | |-->Device "Device0"
[ 16.050] (**) |-->Input Device "Keyboard0"
[ 16.050] (**) |-->Input Device "Mouse0"
[ 16.050] (==) Automatically adding devices
[ 16.050] (==) Automatically enabling devices
[ 16.050] (==) Automatically adding GPU devices
[ 16.084] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/OTF/".
[ 16.084] Entry deleted from font path.
[ 16.084] (Run 'mkfontdir' on "/usr/share/fonts/OTF/").
[ 16.084] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 16.084] Entry deleted from font path.
[ 16.084] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 16.084] Entry deleted from font path.
[ 16.084] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 16.085] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 16.085] Entry deleted from font path.
[ 16.085] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 16.085] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/
[ 16.085] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 16.085] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 16.085] (WW) Disabling Keyboard0
[ 16.085] (WW) Disabling Mouse0
[ 16.085] (II) Loader magic: 0x815d80
[ 16.085] (II) Module ABI versions:
[ 16.085] X.Org ANSI C Emulation: 0.4
[ 16.085] X.Org Video Driver: 19.0
[ 16.085] X.Org XInput driver : 21.0
[ 16.085] X.Org Server Extension : 9.0
[ 16.086] (EE) systemd-logind: failed to get session: PID 333 does not belong to any known session
[ 16.086] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 16.088] (--) PCI:*(0:1:0:0) 10de:1187:3842:2765 rev 161, Mem @ 0xf6000000/16777216, 0xe8000000/134217728, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[ 16.088] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 16.088] (II) LoadModule: "glx"
[ 16.097] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 17.059] (II) Module glx: vendor="NVIDIA Corporation"
[ 17.059] compiled for 4.0.2, module version = 1.0.0
[ 17.059] Module class: X.Org Server Extension
[ 17.067] (II) NVIDIA GLX Module 346.47 Thu Feb 19 18:09:07 PST 2015
[ 17.089] (II) LoadModule: "nvidia"
[ 17.130] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 17.222] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 17.222] compiled for 4.0.2, module version = 1.0.0
[ 17.222] Module class: X.Org Video Driver
[ 17.232] (II) NVIDIA dlloader X Driver 346.47 Thu Feb 19 17:47:18 PST 2015
[ 17.232] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 17.233] (++) using VT number 7
[ 17.321] (II) Loading sub module "fb"
[ 17.321] (II) LoadModule: "fb"
[ 17.321] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 17.347] (II) Module fb: vendor="X.Org Foundation"
[ 17.347] compiled for 1.17.1, module version = 1.0.0
[ 17.347] ABI class: X.Org ANSI C Emulation, version 0.4
[ 17.347] (II) Loading sub module "wfb"
[ 17.347] (II) LoadModule: "wfb"
[ 17.347] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 17.364] (II) Module wfb: vendor="X.Org Foundation"
[ 17.364] compiled for 1.17.1, module version = 1.0.0
[ 17.364] ABI class: X.Org ANSI C Emulation, version 0.4
[ 17.364] (II) Loading sub module "ramdac"
[ 17.364] (II) LoadModule: "ramdac"
[ 17.364] (II) Module "ramdac" already built-in
[ 17.366] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[ 17.366] (==) NVIDIA(0): RGB weight 888
[ 17.366] (==) NVIDIA(0): Default visual is TrueColor
[ 17.366] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 17.368] (**) NVIDIA(0): Option "MetaModes" "nvidia-auto-select +0+0 { ForceFullCompositionPipeline = On }"
[ 17.368] (**) NVIDIA(0): Enabling 2D acceleration
[ 18.022] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20150116)
[ 18.024] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 760 (GK104) at PCI:1:0:0 (GPU-0)
[ 18.024] (--) NVIDIA(0): Memory: 2097152 kBytes
[ 18.024] (--) NVIDIA(0): VideoBIOS: 80.04.c4.00.60
[ 18.024] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 18.033] (--) NVIDIA(0): Valid display device(s) on GeForce GTX 760 at PCI:1:0:0
[ 18.033] (--) NVIDIA(0): CRT-0
[ 18.033] (--) NVIDIA(0): DFP-0
[ 18.033] (--) NVIDIA(0): Samsung S27B370 (DFP-1) (boot, connected)
[ 18.033] (--) NVIDIA(0): DFP-2
[ 18.033] (--) NVIDIA(0): DFP-3
[ 18.033] (--) NVIDIA(0): DFP-4
[ 18.033] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
[ 18.033] (--) NVIDIA(0): DFP-0: Internal TMDS
[ 18.033] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[ 18.033] (--) NVIDIA(0): Samsung S27B370 (DFP-1): Internal TMDS
[ 18.033] (--) NVIDIA(GPU-0): Samsung S27B370 (DFP-1): 340.0 MHz maximum pixel clock
[ 18.033] (--) NVIDIA(0): DFP-2: Internal TMDS
[ 18.033] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
[ 18.033] (--) NVIDIA(0): DFP-3: Internal TMDS
[ 18.033] (--) NVIDIA(GPU-0): DFP-3: 330.0 MHz maximum pixel clock
[ 18.033] (--) NVIDIA(0): DFP-4: Internal DisplayPort
[ 18.033] (--) NVIDIA(GPU-0): DFP-4: 960.0 MHz maximum pixel clock
[ 18.033] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 18.033] (**) NVIDIA(0): device Samsung S27B370 (DFP-1) (Using EDID frequencies has
[ 18.033] (**) NVIDIA(0): been enabled on all display devices.)
[ 18.035] (II) NVIDIA(0): Validated MetaModes:
[ 18.036] (II) NVIDIA(0): "nvidia-auto-select+0+0{ForceFullCompositionPipeline=On}"
[ 18.036] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
[ 18.103] (--) NVIDIA(0): DPI set to (81, 80); computed from "UseEdidDpi" X config
[ 18.103] (--) NVIDIA(0): option
[ 18.103] (--) Depth 24 pixmap format is 32 bpp
[ 18.103] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
[ 18.103] (II) NVIDIA: access.
[ 18.106] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 18.106] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 18.106] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 18.106] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 18.106] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 18.106] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 18.106] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 18.106] (II) NVIDIA(0): Config Options in the README.
[ 18.115] (II) NVIDIA(0): Setting mode "nvidia-auto-select+0+0{ForceFullCompositionPipeline=On}"
[ 18.327] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 18.327] (==) NVIDIA(0): Backing store enabled
[ 18.327] (==) NVIDIA(0): Silken mouse enabled
[ 18.328] (**) NVIDIA(0): DPMS enabled
[ 18.328] (II) Loading sub module "dri2"
[ 18.328] (II) LoadModule: "dri2"
[ 18.328] (II) Module "dri2" already built-in
[ 18.328] (II) NVIDIA(0): [DRI2] Setup complete
[ 18.328] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 18.328] (--) RandR disabled
[ 18.334] (II) Initializing extension GLX
[ 18.334] (II) Indirect GLX disabled.(II) config/udev: Adding input device Power Button (/dev/input/event4)
[ 18.892] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 18.892] (II) LoadModule: "evdev"
[ 18.893] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 18.935] (II) Module evdev: vendor="X.Org Foundation"
[ 18.935] compiled for 1.17.1, module version = 2.9.2
[ 18.935] Module class: X.Org XInput Driver
[ 18.935] ABI class: X.Org XInput driver, version 21.0
[ 18.935] (II) Using input driver 'evdev' for 'Power Button'
[ 18.935] (**) Power Button: always reports core events
[ 18.935] (**) evdev: Power Button: Device: "/dev/input/event4"
[ 18.935] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 18.935] (--) evdev: Power Button: Found keys
[ 18.935] (II) evdev: Power Button: Configuring as keyboard
[ 18.935] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input6/event4"
[ 18.935] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 18.935] (**) Option "xkb_rules" "evdev"
[ 18.935] (**) Option "xkb_model" "pc104"
[ 18.935] (**) Option "xkb_layout" "us"
[ 18.961] (II) config/udev: Adding input device Power Button (/dev/input/event3)
[ 18.961] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 18.961] (II) Using input driver 'evdev' for 'Power Button'
[ 18.961] (**) Power Button: always reports core events
[ 18.961] (**) evdev: Power Button: Device: "/dev/input/event3"
[ 18.961] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 18.961] (--) evdev: Power Button: Found keys
[ 18.961] (II) evdev: Power Button: Configuring as keyboard
[ 18.961] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input5/event3"
[ 18.961] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[ 18.961] (**) Option "xkb_rules" "evdev"
[ 18.961] (**) Option "xkb_model" "pc104"
[ 18.961] (**) Option "xkb_layout" "us"
[ 18.961] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event13)
[ 18.961] (II) No input driver specified, ignoring this device.
[ 18.961] (II) This device may have been added with another device file.
[ 18.962] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event14)
[ 18.962] (II) No input driver specified, ignoring this device.
[ 18.962] (II) This device may have been added with another device file.
[ 18.962] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event15)
[ 18.962] (II) No input driver specified, ignoring this device.
[ 18.962] (II) This device may have been added with another device file.
[ 18.962] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event16)
[ 18.962] (II) No input driver specified, ignoring this device.
[ 18.962] (II) This device may have been added with another device file.
[ 18.962] (II) config/udev: Adding input device Logitech USB Keyboard (/dev/input/event0)
[ 18.962] (**) Logitech USB Keyboard: Applying InputClass "evdev keyboard catchall"
[ 18.962] (II) Using input driver 'evdev' for 'Logitech USB Keyboard'
[ 18.962] (**) Logitech USB Keyboard: always reports core events
[ 18.962] (**) evdev: Logitech USB Keyboard: Device: "/dev/input/event0"
[ 18.962] (--) evdev: Logitech USB Keyboard: Vendor 0x46d Product 0xc31d
[ 18.962] (--) evdev: Logitech USB Keyboard: Found keys
[ 18.962] (II) evdev: Logitech USB Keyboard: Configuring as keyboard
[ 18.963] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.3/3-1.3:1.0/0003:046D:C31D.0001/input/input2/event0"
[ 18.963] (II) XINPUT: Adding extended input device "Logitech USB Keyboard" (type: KEYBOARD, id 8)
[ 18.963] (**) Option "xkb_rules" "evdev"
[ 18.963] (**) Option "xkb_model" "pc104"
[ 18.963] (**) Option "xkb_layout" "us"
[ 18.963] (II) config/udev: Adding input device Logitech USB Keyboard (/dev/input/event1)
[ 18.963] (**) Logitech USB Keyboard: Applying InputClass "evdev keyboard catchall"
[ 18.963] (II) Using input driver 'evdev' for 'Logitech USB Keyboard'
[ 18.963] (**) Logitech USB Keyboard: always reports core events
[ 18.963] (**) evdev: Logitech USB Keyboard: Device: "/dev/input/event1"
[ 18.963] (--) evdev: Logitech USB Keyboard: Vendor 0x46d Product 0xc31d
[ 18.963] (--) evdev: Logitech USB Keyboard: Found absolute axes
[ 18.963] (II) evdev: Logitech USB Keyboard: Forcing absolute x/y axes to exist.
[ 18.963] (--) evdev: Logitech USB Keyboard: Found keys
[ 18.963] (II) evdev: Logitech USB Keyboard: Forcing relative x/y axes to exist.
[ 18.963] (II) evdev: Logitech USB Keyboard: Configuring as mouse
[ 18.963] (II) evdev: Logitech USB Keyboard: Configuring as keyboard
[ 18.963] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.3/3-1.3:1.1/0003:046D:C31D.0002/input/input3/event1"
[ 18.963] (II) XINPUT: Adding extended input device "Logitech USB Keyboard" (type: KEYBOARD, id 9)
[ 18.963] (**) Option "xkb_rules" "evdev"
[ 18.963] (**) Option "xkb_model" "pc104"
[ 18.963] (**) Option "xkb_layout" "us"
[ 18.964] (II) evdev: Logitech USB Keyboard: initialized for absolute axes.
[ 18.964] (**) Logitech USB Keyboard: (accel) keeping acceleration scheme 1
[ 18.964] (**) Logitech USB Keyboard: (accel) acceleration profile 0
[ 18.964] (**) Logitech USB Keyboard: (accel) acceleration factor: 2.000
[ 18.964] (**) Logitech USB Keyboard: (accel) acceleration threshold: 4
[ 18.964] (II) config/udev: Adding input device Razer Razer DeathAdder (/dev/input/event2)
[ 18.964] (**) Razer Razer DeathAdder: Applying InputClass "evdev pointer catchall"
[ 18.964] (**) Razer Razer DeathAdder: Applying InputClass "My Mouse"
[ 18.964] (II) Using input driver 'evdev' for 'Razer Razer DeathAdder'
[ 18.964] (**) Razer Razer DeathAdder: always reports core events
[ 18.964] (**) evdev: Razer Razer DeathAdder: Device: "/dev/input/event2"
[ 19.016] (--) evdev: Razer Razer DeathAdder: Vendor 0x1532 Product 0x16
[ 19.016] (--) evdev: Razer Razer DeathAdder: Found 12 mouse buttons
[ 19.016] (--) evdev: Razer Razer DeathAdder: Found scroll wheel(s)
[ 19.016] (--) evdev: Razer Razer DeathAdder: Found relative axes
[ 19.016] (--) evdev: Razer Razer DeathAdder: Found x and y relative axes
[ 19.016] (II) evdev: Razer Razer DeathAdder: Configuring as mouse
[ 19.016] (II) evdev: Razer Razer DeathAdder: Adding scrollwheel support
[ 19.016] (**) evdev: Razer Razer DeathAdder: YAxisMapping: buttons 4 and 5
[ 19.016] (**) evdev: Razer Razer DeathAdder: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 19.016] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.4/3-1.4:1.0/0003:1532:0016.0006/input/input22/event2"
[ 19.016] (II) XINPUT: Adding extended input device "Razer Razer DeathAdder" (type: MOUSE, id 10)
[ 19.016] (II) evdev: Razer Razer DeathAdder: initialized for relative axes.
[ 19.017] (**) Option "AccelerationScheme" "none"
[ 19.017] (**) Razer Razer DeathAdder: (accel) selected scheme none/0
[ 19.017] (**) Razer Razer DeathAdder: (accel) acceleration factor: 2.000
[ 19.017] (**) Razer Razer DeathAdder: (accel) acceleration threshold: 4
[ 19.017] (II) config/udev: Adding input device Razer Razer DeathAdder (/dev/input/mouse0)
[ 19.017] (**) Razer Razer DeathAdder: Applying InputClass "My Mouse"
[ 19.017] (II) No input driver specified, ignoring this device.
[ 19.017] (II) This device may have been added with another device file.
[ 19.017] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event7)
[ 19.017] (II) No input driver specified, ignoring this device.
[ 19.017] (II) This device may have been added with another device file.
[ 19.018] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event8)
[ 19.018] (II) No input driver specified, ignoring this device.
[ 19.018] (II) This device may have been added with another device file.
[ 19.018] (II) config/udev: Adding input device HDA Intel PCH Line Out Front (/dev/input/event9)
[ 19.018] (II) No input driver specified, ignoring this device.
[ 19.018] (II) This device may have been added with another device file.
[ 19.018] (II) config/udev: Adding input device HDA Intel PCH Line Out Surround (/dev/input/event10)
[ 19.018] (II) No input driver specified, ignoring this device.
[ 19.018] (II) This device may have been added with another device file.
[ 19.018] (II) config/udev: Adding input device HDA Intel PCH Line Out CLFE (/dev/input/event11)
[ 19.018] (II) No input driver specified, ignoring this device.
[ 19.018] (II) This device may have been added with another device file.
[ 19.019] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event12)
[ 19.019] (II) No input driver specified, ignoring this device.
[ 19.019] (II) This device may have been added with another device file.
[ 19.019] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event6)
[ 19.019] (II) No input driver specified, ignoring this device.
[ 19.019] (II) This device may have been added with another device file.
[ 19.019] (II) config/udev: Adding input device PC Speaker (/dev/input/event5)
[ 19.019] (II) No input driver specified, ignoring this device.
[ 19.019] (II) This device may have been added with another device file.
[ 213.516] (II) config/udev: removing device Razer Razer DeathAdder
[ 213.556] (II) evdev: Razer Razer DeathAdder: Close
[ 213.556] (II) UnloadModule: "evdev"
[ 328.612] (II) config/udev: Adding input device Razer Razer DeathAdder (/dev/input/mouse0)
[ 328.612] (**) Razer Razer DeathAdder: Applying InputClass "My Mouse"
[ 328.612] (II) No input driver specified, ignoring this device.
[ 328.612] (II) This device may have been added with another device file.
[ 328.612] (II) config/udev: Adding input device Razer Razer DeathAdder (/dev/input/event2)
[ 328.612] (**) Razer Razer DeathAdder: Applying InputClass "evdev pointer catchall"
[ 328.612] (**) Razer Razer DeathAdder: Applying InputClass "My Mouse"
[ 328.612] (II) Using input driver 'evdev' for 'Razer Razer DeathAdder'
[ 328.612] (**) Razer Razer DeathAdder: always reports core events
[ 328.612] (**) evdev: Razer Razer DeathAdder: Device: "/dev/input/event2"
[ 328.663] (--) evdev: Razer Razer DeathAdder: Vendor 0x1532 Product 0x16
[ 328.663] (--) evdev: Razer Razer DeathAdder: Found 12 mouse buttons
[ 328.663] (--) evdev: Razer Razer DeathAdder: Found scroll wheel(s)
[ 328.663] (--) evdev: Razer Razer DeathAdder: Found relative axes
[ 328.663] (--) evdev: Razer Razer DeathAdder: Found x and y relative axes
[ 328.663] (II) evdev: Razer Razer DeathAdder: Configuring as mouse
[ 328.663] (II) evdev: Razer Razer DeathAdder: Adding scrollwheel support
[ 328.663] (**) evdev: Razer Razer DeathAdder: YAxisMapping: buttons 4 and 5
[ 328.663] (**) evdev: Razer Razer DeathAdder: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 328.663] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.4/3-1.4:1.0/0003:1532:0016.000A/input/input26/event2"
[ 328.663] (II) XINPUT: Adding extended input device "Razer Razer DeathAdder" (type: MOUSE, id 10)
[ 328.663] (II) evdev: Razer Razer DeathAdder: initialized for relative axes.
[ 328.663] (**) Option "AccelerationScheme" "none"
[ 328.663] (**) Razer Razer DeathAdder: (accel) selected scheme none/0
[ 328.663] (**) Razer Razer DeathAdder: (accel) acceleration factor: 2.000
[ 328.663] (**) Razer Razer DeathAdder: (accel) acceleration threshold: 4
[ 425.481] (II) config/udev: removing device Razer Razer DeathAdder
[ 425.513] (II) evdev: Razer Razer DeathAdder: Close
[ 425.513] (II) UnloadModule: "evdev"
[ 425.536] (II) config/udev: Adding input device Razer Razer DeathAdder (/dev/input/mouse0)
[ 425.536] (**) Razer Razer DeathAdder: Applying InputClass "My Mouse"
[ 425.536] (II) No input driver specified, ignoring this device.
[ 425.536] (II) This device may have been added with another device file.
[ 425.536] (II) config/udev: Adding input device Razer Razer DeathAdder (/dev/input/event2)
[ 425.536] (**) Razer Razer DeathAdder: Applying InputClass "evdev pointer catchall"
[ 425.536] (**) Razer Razer DeathAdder: Applying InputClass "My Mouse"
[ 425.536] (II) Using input driver 'evdev' for 'Razer Razer DeathAdder'
[ 425.536] (**) Razer Razer DeathAdder: always reports core events
[ 425.536] (**) evdev: Razer Razer DeathAdder: Device: "/dev/input/event2"
[ 425.590] (--) evdev: Razer Razer DeathAdder: Vendor 0x1532 Product 0x16
[ 425.590] (--) evdev: Razer Razer DeathAdder: Found 12 mouse buttons
[ 425.590] (--) evdev: Razer Razer DeathAdder: Found scroll wheel(s)
[ 425.590] (--) evdev: Razer Razer DeathAdder: Found relative axes
[ 425.590] (--) evdev: Razer Razer DeathAdder: Found x and y relative axes
[ 425.590] (II) evdev: Razer Razer DeathAdder: Configuring as mouse
[ 425.590] (II) evdev: Razer Razer DeathAdder: Adding scrollwheel support
[ 425.590] (**) evdev: Razer Razer DeathAdder: YAxisMapping: buttons 4 and 5
[ 425.590] (**) evdev: Razer Razer DeathAdder: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 425.590] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.4/3-1.4:1.0/0003:1532:0016.000B/input/input27/event2"
[ 425.590] (II) XINPUT: Adding extended input device "Razer Razer DeathAdder" (type: MOUSE, id 10)
[ 425.590] (II) evdev: Razer Razer DeathAdder: initialized for relative axes.
[ 425.590] (**) Option "AccelerationScheme" "none"
[ 425.590] (**) Razer Razer DeathAdder: (accel) selected scheme none/0
[ 425.590] (**) Razer Razer DeathAdder: (accel) acceleration factor: 2.000
[ 425.590] (**) Razer Razer DeathAdder: (accel) acceleration threshold: 4
I've tried booting with the razer service disabled, I have to plug in my mouse again to use it when booting from Windows.
Will edit with a failed boot very soon.

Looking for a new window manager

Hello all!
My first post here and I'd like to share a little discussion.
So I have this idea of "perfect desktop" in my mind:
- It must be lightweight
- Very clean.
- No menus
- Highly customizable.
- Able to run compiz
I've come to Enlightenment 17 on Fedora and that was close to perfection.
I just loved, everything I wanted. Nice animations, clean, and man you can change absolutely everything there.
But then I started getting frustrated with bugs since it's not stable and I had to move on.
Then I came to XFCE4.6. Great, fairly customizable. Fewer bugs that you can live with it.
And I could run compiz. I just love using compiz here and got used to it. I use compiz to be more productive with the desktops , shortcuts and just a few animations.
But I few like trying something new. XFCE is just here for a lack of a better choice. It doesn't feel it fits me.
So maybe someone could recommend a new Window Manager for me?
I am interested in OpenBox and FluxBox.
I'm astonished with some OpenBox screenshots where you don't have anything, just the right-click menu and some apps running.
That's exactly what I would want.
But then, things like NetworkManager. How do you connect to internet (wireless)? On the command line?
What if I'd need to scan for open wireless networks..everything would have to be on command line?
Laptop Battery widget that warns when it's almost over, etc..
Are those WM really that raw or am I missing a few hidden goodies?
Would LXDE be a better choice?

m4co wrote:
Wow is this forum active. Makes me feel welcome here
The thing about wireless, I actually like command line, but there are a few things that are worth having a applet or something.
And wireless is one of those. I guess I can take a look on wicd.
It's a good idea to have compiz as the WM actually. Would it be lightweight to have it like that?
Is there anybody here that uses compiz as a WM?
For the xfce4-panel, is it possible to get transparency on it? That's probably the only thing holding me back with xfce4-panel.
If "able to run compiz" wasn't a requisite, what other WM would you suggest for my "profile" ?
I would like to hear other users opinions who like to customize everything on a WM.
I recommend running Compiz by itself. There is a good wiki page on it in the Arch wiki. Some apps you'll want to go with it are:
LXAppearance --change GTK/icon theme
Feh or Nitrogen --Set Wallpaper
Xfce4-panel --The lightest one that works with Compiz properly
Or, if you don't want a panel: stalonetray
Compiz-deskmenu --For a customizable right-click main menu
Gmrun --Run dialog (Alt+F2 in most DEs)
And this helped me a lot.
Thank you all for the replies. I appreciate.
Xfce4-panel can have transparency. The only problem is that everything become transparent: text, icons, everything.
I use Compiz as a standalone WM and it is much lighter than DE+Compiz. My Compiz setup uses about 30MB(out of 1GB) more RAM than my Openbox setup (which are both the same except for the WM).

[SOLVED!] KDE 4.11 - Window Manager seems not to be running?

Greetings,
I still seem unable to fix the fact that systemsettings will run. However it will run if you do kdesu systemsettings.
Doing so I started checking around in it and thought I'd look at the desktop effects, when I was greeted with this:
So, I am guessing that the window borders and buttons are a figment of my imagination....
This is after me pretty much starting over with KDE, removing the .kde and .kde4 folders.
Help?
Edit: That pic seems to not link right. Yay. Basically it says that effects can not be activated or whatever because a window manager seems not to be running. The irony of it is you can see the fact that there are window borders and buttons and such, evidence of a WM...
I wonder if there is something here that is related to me not being able to run systemsettings... yet systemsettings will run fine in any other environment - including Gnome Shell.
Another thing, KDE 4.11 ran great in testing and kde_unstable. Once it went to extra, things happened. I find that odd. Maybe something is missing on my end that most archers already have?
Edit2: fixed image link
Last edited by mythus (2013-08-25 20:49:38)

No omeringen, Nvidia user.
I can try again Thaodan since I've had some updates come through (and weeded out some dot files). Last time I tried I saw OpenGL 2 selected. Trying to change to 3 or anything else also got the screenshot in my OP.
I'll log into KDE and see if it still does the same, after a brief check for last minute updates.
EDIT: OK, so I can mark this as solved. I found an odd dot file, who's name excapes me but deals with kde sessions, just sitting around in the home folder. Once I deleted it and restarted, I found that not only System Settings finally ran again as a user, but I could also change and apply desktop effects. Peculiar. I thought that maybe it was a dot file that was causing the problem, that wasn't in the .kde or .kde4 folder. It just took finding it and removing it.
I wish I knew more to tell, but this at least solves my issue, and the issue with the non-running-as-user system settings I had posted in another thread (thinking that they were separate events. Thanks again for all your help guys!
Last edited by mythus (2013-08-25 20:49:05)

Error in xfce4-settings-manager When Click on Window Manager

Hello all,
I have a problem with the xfce4 environment.
First, I can't see any panel by default.
Second, the settings button near the shutdown button does not work.
Finally and more importantly, when I call from the terminal settings from terminal, settings start fine, but when I click on Window Manager or Window Manager Tweaks I get:
[jav@localhost ~]$ xfce4-settings-manager
These settings cannot work with your current window manager (GNOME Shell)
I already tried deleting sessions as mentioned in Arch wiki and also called startxfce4 again.
Any ideas?

startxfce4 should be used to start xfce4-session. It can be run from the virtual terminal(the screen-filling terminal you see when you boot up a (fresh) machine) directly or can be called in your .xinitrc. Instead of
exec xfce4-session
you should have
exec startxfce4
in your .xinitrc.
It looks like you're running startxfce4 from an X session(probably Gnome). Xfce is a replacement for Gnome, it's not run inside of Gnome or any other window manager or desktop environment(well, some parts can, like the panel). What's in your .xinitrc, especially at the exec line? Note that there should be only one exec line.
Last edited by Steef435 (2014-01-03 14:26:09)

Themable Window Manager

I have been switching window managers for a while now and have gotten to where I have a specific set of requirements and no contenders. I was wondering if anyone could recommend some apps.
I am looking for a window manager that is almost fully themable. By this I mean full transparencies and the ability to create anything as a window border. If is not important for me to have the window title on the sides, that aspect of theming is not too important.
I currently am using openbox and I love every aspect of it except for the limitations on the themes. I need the window manager to do the following things:
keybindings (fully customizable).
Modular. I don't want to pull in (lots of) desktop specific libraries (IE Qt OK, KDE not-OK)
Provide nothing but a window manager (unless it is easily turned off)
Multiple desktops.
I'm going to add a couple of thinks I would also like to see but shouldn't stop you from posting any,
Not too fat
Stacking
Please post even if they don't fill all of the requirements and I would like to have a little explanation of why you like each window manager. (Please no "fluxbox ftw!")

I'm going to start off with my findings. Many of my explanations are short and most of them are only highlighting the problems. Please don't accuse me of hating any of the window managers as I respect each an every one. Many just aren't for me.
KWin really wants to find and start KDE. Also can't bind modifier keys (Qt limitation). KWin is also quite slow due to the effects. If you turn them all off it speeds right up and takes a lot less memory. Unfortunately it is still linked to the graphics libraries though so it takes a long time to start.
Metacity has too few options. (For example no desktop wrap around). This is not a progress issue but a design philosophy. Hence the logo "A WM for old people". It does have great theming capabilities and does it's job very well. I does not start up any gnome processes (as far as I noticed).
Openbox and fluxbox have the theming problems. They are great window managers though. Openbox is simple and elegant. The config file is awesome. Openbox also has a strong user base if you don't want to write your own themes. Fluxbox has a ton of extra features if you like them (I don't) such as grouping.
xfwm wants some settings daemons. (not too bad) I does have nice themes and is quite lightweight. It also has all of the common features.
mutter won't start. (I'm looking into this)
eggwm won't start (No errors or anything) It will also probably have the same Qt problem as KWin.
e16 is nice and themable (although it is a ton of work) but it puts too much stuff on my desktop.
Last edited by youarefunny (2012-02-11 03:15:51)

Best tiling window manager for two monitors

I am looking for a window manager, that will work thus, my main window on my main left monitor, and my stack (my unfocused windows) on my right monitor. Is there a WM that can do this or anyone know one that comes close.
Thanks

skottish wrote:
If it helps at all, this is a useful way to look at awesome vs. xmonad:
awesome is pretty much a complete WM/DE (it's close to being a full DE) with a task bar, system tray, run dialog, something like nine preconfigured window management algorithms, right-click menus, etc. Through lua scripting it can be fully extended. There's a lot to awesome by default and more often than not users are going to start to tear it down because there's just so much of it.
xmonad out of the box is about 5% WM and 95% toolkit to build your own. It has no DE features upon first start and few layouts. If your objective is to build up your WM and not to tear it down, this is a good place to start. The GHC dependency is irrelevant if this is your goal (assuming you can afford the hard drive space) in my opinion.
One thing that's pretty cool about xmonad that a lot people may not realize is that some of it's developers are involved with Arch. Arch-haskell (the bazillion packages in AUR), Real World Haskell (the book), and GHC are all tied nicely together by some of these people.
What is cool about XMonad too that you can integrate Gnome and KDE easily in XMonad and bluetile is really cool for starters

Window Manager

So I was messing around with awesome window manager last night, and then I thought: what about my battery power?
All I really need is a battery meter for my laptop. That's it. Is there anyway to do with awesome?
Edit: how do you connect to wifi with just a wm? I've heard about wicd, but I'm still not sure.
Also - can you use TWM under XFCE?
Last edited by COMMUNISTCHINA (2008-07-01 13:40:23)

when it comes to wireless management, i have used netcfg2 even under kde and gnome. imho it's the best wifi managers out there.
all you have to do is create simple files(s) under /etc/network.d/ (you can use files in /etc/network.d/example/ - just copy wpa.example or ethernet.example form there, then modify and rename it to your needs) with connection information.
then add NETWORKS=("auto-wireless wlan0" ethernet) line into network section in rc.conf.
you also have to add net-profiles into the dameons list in the rc.conf file and you're done.
it loads the connection on boot and the connection stays active even when the x cannot start. and also it's very stable (which i can't say about networkmanager).
if you need to connect different network after the boot, just type netcfg2 networkname and it's up.
simple and easy - the arch way.
netcfg wiki page

Window manager suggestions

Hey all,
I'm looking for a new window manager. I love fluxbox, it's great. However at the moment I'm going on a style craze and flux just isn't doing it for me. At the moment I'm running E17 but it's not quite stable enough or supported enough for my liking yet. I'm really not a fan of E16 but that's probably cause I don't know it. I want a window manager that's light, doesn't have stupid virtual root windows like E17 and I believe GNOME does, right click menu and pixmap support. By pixmap support, I mean I want to be able to design window borders and menu stuff with transparencies and crap like that. Any suggestions would be appreciated.
Thanks

Meshuggin wrote:
Legout wrote:
sure i can
${execi 3 ~/.torsmo/mpc.sh}
Can you post that script(mpc.sh) Legout? , and ... it will works for me if I use ncmpc?, or it's something diferent to grab this kind of information?
Install mpc with pacman -S mpc and the script will work!!
#!/bin/sh
STATUS=`mpc | head -n2 | tail -n1 | cut -d ' ' -f1 | sed 's/[//' | sed -e 's/]//'`
ARTIST=`mpc --format %artist% | head -n1`
TITLE=`mpc --format %title% | head -n1`
TOTALTIME=`mpc --format %time% | head -n1`
TIME=`mpc | head -n2 | tail -n1 | cut -d ' ' -f5`
REPEAT=`mpc | tail -n1 | cut -d ' ' -f6`
RNDOM=`mpc | tail -n1 | cut -d ' ' -f10`
PERCENT=`mpc | head -n2 | tail -n1 | cut -d ' ' -f6`
STATUS1="off"
ARTIST1="--"
TITLE1="--"
TOTALTIME1="--"
TIME1="--"
REPEAT1="--"
RNDOM1="--"
PERCENT1="--"
if [ -f /var/run/daemons/mpd ];then
if [ "$STATUS" = "playing" -o "$STATUS" = "paused " ];then
#echo ""
echo " | "
echo " +--Status"
echo " | |"
echo " | +--an/aus - $STATUS"
echo " | +--repeat - $REPEAT"
echo " | +--random - $RNDOM"
echo " |"
echo " +--songinfo"
echo " |"
echo " +--artist - $ARTIST"
echo " +--title - $TITLE"
echo -n " +--time - ${TIME} min / ${TOTALTIME} min ${PERCENT}"
else
# echo ""
echo " |"
echo " +--Status"
echo " | |"
echo " | +--an/aus - $STATUS"
echo " | +--repeat - $REPEAT"
echo " | +--random - $RNDOM"
echo " |"
echo " +--songinfo"
echo " |"
echo " +--artist - $ARTIST1"
echo " +--title - $TITLE1"
echo -n " +--time - $TIME1 min / $TOTALTIME1 min $PERCENT1"
fi
else
echo ""
echo " |"
echo " +--Status"
echo " |"
echo -n " +--an/aus - $STATUS1"
fi
[/b]

Changing default window manager

Is there a way to use Gnome or KDE as default desktop environment on my current build of mac os x (10.4.9)?

Hi B1|\|ARY,
   You can use a desktop manager with Apple's X11 but it runs inside X11 and doesn't replace Aqua. It's simply a matter of what you execute in your xinitrc file. Apple starts the Quartz window manager by "execing" the quartz-wm executable in the /etc/X11/xinit/xinitrc file. However, you can copy that to a ~/.xinitrc and the copy will by used instead. Then you can comment out the "exec quartz-wm" line and replace it with the command that starts your preferred desktop manager. For instance, to start gnome, you would make the last command in that file:
exec gnome-session
Of course you might need to use an absolute path.
   You can then set the window manager in the configuration of the desktop manager. However, if you're not going to use the Quartz window manager then I recommend that you include the following line before the "exec" line:
/usr/X11R6/bin/quartz-wm --only-proxy &
This will allow you to still use Apple's cut-and-paste mechanism, such as it is, with their X11.
Gary
~~~~
   Expect the worst, it's the least you can do.

Window Manager Warning In Gnome

Similar Messages

Maybe you are looking for