Dolphin emulator taking control of window manager

I'm using awesome wm but I have a weird issue. Whenever I have dolphin-emu (a qt based gamecube emulator) open, I cannot right click on my desktop or click on anything in the awesome panel. I can still use keyboard shortcuts to switch between tags, but I can't do anything with the mouse except click on things in the dolphin window.
This occurs even when dolphin isn't maximized or fullscreen. It occurs even when dolphin is minimized. Pretty much as long as dolphin is running. I can still see the awesome panel and my wallpaper, but it's completely unresponsive to mouse actions.
This only occurs with dolphin. No other QT or GTK apps cause this issue. Any advice?
edit: I suspect this may be a bug in Dolphin. I tried running it with openbox and have the same issues. Can't access openbox menus.
Last edited by Exershio (2015-04-15 05:24:52)

This is definitely a bug in Dolphin. I downgraded to 4.0.2 (the latest stable version, over a year old) and the problem went away. I have reported the issue on the bug tracker.
Link if anyone is curious or having the same problems:
https://code.google.com/p/dolphin-emu/i … il?id=8469

Similar Messages

  • LightDM suddenly broke after uninstalling a window manager

    I've been using LightDM with XFCE fine for months. I just installed the i3 window manager to try it out. I didn't like it, so I uninstalled it. All of the sudden, LightDM no longer works. When it starts, I see just a black screen with a black cursor. The screen flashes once, then comes back with the same black screen/cursor. If I switch to a TTY, I see that systemd-journal is using 100% CPU. I have no idea what went wrong.
    I also tried using SLiM. It doesn't freeze like LightDM, but when I try to login, it says "failed to execute login command."
    I tried reinstalling LightDM but that didn't make a difference. I know this is really little information, but does anyone know what I can do to fix it?
    Last edited by corban (2013-05-12 03:48:43)

    [ 131.232]
    X.Org X Server 1.14.1
    Release Date: 2013-04-17
    [ 131.232] X Protocol Version 11, Revision 0
    [ 131.232] Build Operating System: Linux 3.8.7-1-ARCH x86_64
    [ 131.232] Current Operating System: Linux daz 3.8.11-1-ARCH #1 SMP PREEMPT Wed May 1 20:18:57 CEST 2013 x86_64
    [ 131.232] Kernel command line: root=/dev/sda1 ro initrd=../initramfs-linux.img BOOT_IMAGE=../vmlinuz-linux
    [ 131.232] Build Date: 17 April 2013 02:37:06PM
    [ 131.232]
    [ 131.232] Current version of pixman: 0.30.0
    [ 131.232] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 131.232] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 131.232] (==) Log file: "/var/log/Xorg.0.log", Time: Sun May 12 11:24:05 2013
    [ 131.232] (==) Using config file: "/etc/X11/xorg.conf"
    [ 131.232] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 131.232] (==) No Layout section. Using the first Screen section.
    [ 131.232] (==) No screen section available. Using defaults.
    [ 131.232] (**) |-->Screen "Default Screen Section" (0)
    [ 131.232] (**) | |-->Monitor "<default monitor>"
    [ 131.232] (==) No device specified for screen "Default Screen Section".
    Using the first device section listed.
    [ 131.232] (**) | |-->Device "Gfx card"
    [ 131.232] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 131.232] (==) Automatically adding devices
    [ 131.232] (==) Automatically enabling devices
    [ 131.232] (==) Automatically adding GPU devices
    [ 131.232] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 131.232] Entry deleted from font path.
    [ 131.232] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 131.232] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 131.232] Entry deleted from font path.
    [ 131.232] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 131.232] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/OTF/,
    /usr/share/fonts/Type1/
    [ 131.232] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 131.232] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 131.232] (II) Loader magic: 0x7fcc20
    [ 131.232] (II) Module ABI versions:
    [ 131.232] X.Org ANSI C Emulation: 0.4
    [ 131.232] X.Org Video Driver: 14.1
    [ 131.232] X.Org XInput driver : 19.1
    [ 131.232] X.Org Server Extension : 7.0
    [ 131.233] (--) PCI:*(0:1:0:0) 10de:1201:1043:83b4 rev 161, Mem @ 0xf6000000/33554432, 0xe0000000/134217728, 0xec000000/67108864, I/O @ 0x0000bf00/128, BIOS @ 0x????????/524288
    [ 131.233] Initializing built-in extension Generic Event Extension
    [ 131.233] Initializing built-in extension SHAPE
    [ 131.233] Initializing built-in extension MIT-SHM
    [ 131.233] Initializing built-in extension XInputExtension
    [ 131.233] Initializing built-in extension XTEST
    [ 131.233] Initializing built-in extension BIG-REQUESTS
    [ 131.233] Initializing built-in extension SYNC
    [ 131.233] Initializing built-in extension XKEYBOARD
    [ 131.233] Initializing built-in extension XC-MISC
    [ 131.233] Initializing built-in extension SECURITY
    [ 131.233] Initializing built-in extension XINERAMA
    [ 131.233] Initializing built-in extension XFIXES
    [ 131.233] Initializing built-in extension RENDER
    [ 131.233] Initializing built-in extension RANDR
    [ 131.233] Initializing built-in extension COMPOSITE
    [ 131.233] Initializing built-in extension DAMAGE
    [ 131.234] Initializing built-in extension MIT-SCREEN-SAVER
    [ 131.234] Initializing built-in extension DOUBLE-BUFFER
    [ 131.234] Initializing built-in extension RECORD
    [ 131.234] Initializing built-in extension DPMS
    [ 131.234] Initializing built-in extension X-Resource
    [ 131.234] Initializing built-in extension XVideo
    [ 131.234] Initializing built-in extension XVideo-MotionCompensation
    [ 131.234] Initializing built-in extension XFree86-VidModeExtension
    [ 131.234] Initializing built-in extension XFree86-DGA
    [ 131.234] Initializing built-in extension XFree86-DRI
    [ 131.234] Initializing built-in extension DRI2
    [ 131.234] (II) LoadModule: "glx"
    [ 131.234] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 131.239] (II) Module glx: vendor="NVIDIA Corporation"
    [ 131.239] compiled for 4.0.2, module version = 1.0.0
    [ 131.239] Module class: X.Org Server Extension
    [ 131.239] (II) NVIDIA GLX Module 313.30 Wed Mar 27 15:51:21 PDT 2013
    [ 131.239] Loading extension GLX
    [ 131.239] (==) Matched nouveau as autoconfigured driver 0
    [ 131.239] (==) Matched nvidia as autoconfigured driver 1
    [ 131.239] (==) Matched nv as autoconfigured driver 2
    [ 131.239] (==) Matched vesa as autoconfigured driver 3
    [ 131.239] (==) Matched modesetting as autoconfigured driver 4
    [ 131.239] (==) Matched fbdev as autoconfigured driver 5
    [ 131.239] (==) Assigned the driver to the xf86ConfigLayout
    [ 131.239] (II) LoadModule: "nouveau"
    [ 131.240] (WW) Warning, couldn't open module nouveau
    [ 131.240] (II) UnloadModule: "nouveau"
    [ 131.240] (II) Unloading nouveau
    [ 131.240] (EE) Failed to load module "nouveau" (module does not exist, 0)
    [ 131.240] (II) LoadModule: "nvidia"
    [ 131.240] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
    [ 131.240] (II) Module nvidia: vendor="NVIDIA Corporation"
    [ 131.240] compiled for 4.0.2, module version = 1.0.0
    [ 131.240] Module class: X.Org Video Driver
    [ 131.240] (II) LoadModule: "nv"
    [ 131.240] (WW) Warning, couldn't open module nv
    [ 131.240] (II) UnloadModule: "nv"
    [ 131.240] (II) Unloading nv
    [ 131.240] (EE) Failed to load module "nv" (module does not exist, 0)
    [ 131.240] (II) LoadModule: "vesa"
    [ 131.240] (WW) Warning, couldn't open module vesa
    [ 131.240] (II) UnloadModule: "vesa"
    [ 131.240] (II) Unloading vesa
    [ 131.240] (EE) Failed to load module "vesa" (module does not exist, 0)
    [ 131.240] (II) LoadModule: "modesetting"
    [ 131.240] (WW) Warning, couldn't open module modesetting
    [ 131.240] (II) UnloadModule: "modesetting"
    [ 131.240] (II) Unloading modesetting
    [ 131.240] (EE) Failed to load module "modesetting" (module does not exist, 0)
    [ 131.240] (II) LoadModule: "fbdev"
    [ 131.240] (WW) Warning, couldn't open module fbdev
    [ 131.240] (II) UnloadModule: "fbdev"
    [ 131.240] (II) Unloading fbdev
    [ 131.240] (EE) Failed to load module "fbdev" (module does not exist, 0)
    [ 131.240] (II) NVIDIA dlloader X Driver 313.30 Wed Mar 27 15:33:21 PDT 2013
    [ 131.240] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
    [ 131.240] (++) using VT number 7
    [ 131.243] (II) Loading sub module "wfb"
    [ 131.243] (II) LoadModule: "wfb"
    [ 131.243] (II) Loading /usr/lib/xorg/modules/libwfb.so
    [ 131.243] (II) Module wfb: vendor="X.Org Foundation"
    [ 131.243] compiled for 1.14.1, module version = 1.0.0
    [ 131.243] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 131.243] (II) Loading sub module "ramdac"
    [ 131.243] (II) LoadModule: "ramdac"
    [ 131.243] (II) Module "ramdac" already built-in
    [ 131.243] (II) NVIDIA(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 131.243] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
    [ 131.243] (==) NVIDIA(0): RGB weight 888
    [ 131.243] (==) NVIDIA(0): Default visual is TrueColor
    [ 131.243] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
    [ 131.243] (**) NVIDIA(0): Option "NoLogo" "1"
    [ 131.243] (**) NVIDIA(0): Option "DamageEvents" "1"
    [ 131.243] (**) NVIDIA(0): Option "OnDemandVBlankInterrupts" "1"
    [ 131.243] (**) NVIDIA(0): Enabling 2D acceleration
    [ 131.515] (II) NVIDIA(GPU-0): Display (Acer G235H (DFP-2)) does not support NVIDIA 3D Vision
    [ 131.515] (II) NVIDIA(GPU-0): stereo.
    [ 131.516] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 560 (GF114) at PCI:1:0:0 (GPU-0)
    [ 131.516] (--) NVIDIA(0): Memory: 1048576 kBytes
    [ 131.516] (--) NVIDIA(0): VideoBIOS: 70.24.21.00.00
    [ 131.516] (II) NVIDIA(0): Detected PCI Express Link width: 16X
    [ 131.517] (--) NVIDIA(0): Valid display device(s) on GeForce GTX 560 at PCI:1:0:0
    [ 131.517] (--) NVIDIA(0): CRT-0
    [ 131.517] (--) NVIDIA(0): CRT-1
    [ 131.517] (--) NVIDIA(0): DFP-0
    [ 131.517] (--) NVIDIA(0): DFP-1
    [ 131.517] (--) NVIDIA(0): Acer G235H (DFP-2) (connected)
    [ 131.517] (--) NVIDIA(0): CRT-0: 400.0 MHz maximum pixel clock
    [ 131.517] (--) NVIDIA(0): CRT-1: 400.0 MHz maximum pixel clock
    [ 131.517] (--) NVIDIA(0): DFP-0: 330.0 MHz maximum pixel clock
    [ 131.517] (--) NVIDIA(0): DFP-0: Internal Single Link TMDS
    [ 131.517] (--) NVIDIA(0): DFP-1: 165.0 MHz maximum pixel clock
    [ 131.517] (--) NVIDIA(0): DFP-1: Internal Single Link TMDS
    [ 131.517] (--) NVIDIA(0): Acer G235H (DFP-2): 330.0 MHz maximum pixel clock
    [ 131.517] (--) NVIDIA(0): Acer G235H (DFP-2): Internal Dual Link TMDS
    [ 131.517] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 131.517] (**) NVIDIA(0): device Acer G235H (DFP-2) (Using EDID frequencies has been
    [ 131.517] (**) NVIDIA(0): enabled on all display devices.)
    [ 131.518] (==) NVIDIA(0):
    [ 131.518] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
    [ 131.518] (==) NVIDIA(0): will be used as the requested mode.
    [ 131.518] (==) NVIDIA(0):
    [ 131.518] (II) NVIDIA(0): Validated MetaModes:
    [ 131.518] (II) NVIDIA(0): "DFP-2:nvidia-auto-select"
    [ 131.518] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
    [ 131.554] (--) NVIDIA(0): DPI set to (95, 94); computed from "UseEdidDpi" X config
    [ 131.554] (--) NVIDIA(0): option
    [ 131.554] (--) Depth 24 pixmap format is 32 bpp
    [ 131.554] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
    [ 131.554] (II) NVIDIA: access.
    [ 131.556] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
    [ 131.556] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
    [ 131.556] (II) NVIDIA(0): configuration option may not be set correctly. When the
    [ 131.556] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
    [ 131.556] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
    [ 131.556] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
    [ 131.556] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
    [ 131.556] (II) NVIDIA(0): Config Options in the README.
    [ 131.557] (II) NVIDIA(0): Setting mode "DFP-2:nvidia-auto-select"
    [ 131.578] Loading extension NV-GLX
    [ 131.630] (==) NVIDIA(0): Disabling shared memory pixmaps
    [ 131.630] (==) NVIDIA(0): Backing store disabled
    [ 131.630] (==) NVIDIA(0): Silken mouse enabled
    [ 131.630] (==) NVIDIA(0): DPMS enabled
    [ 131.630] Loading extension NV-CONTROL
    [ 131.630] Loading extension XINERAMA
    [ 131.630] (II) Loading sub module "dri2"
    [ 131.630] (II) LoadModule: "dri2"
    [ 131.630] (II) Module "dri2" already built-in
    [ 131.630] (II) NVIDIA(0): [DRI2] Setup complete
    [ 131.630] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
    [ 131.630] (--) RandR disabled
    [ 131.633] (II) Initializing extension GLX
    [ 131.656] (II) config/udev: Adding input device Power Button (/dev/input/event5)
    [ 131.656] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 131.656] (II) LoadModule: "evdev"
    [ 131.656] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 131.656] (II) Module evdev: vendor="X.Org Foundation"
    [ 131.656] compiled for 1.14.0, module version = 2.8.0
    [ 131.656] Module class: X.Org XInput Driver
    [ 131.656] ABI class: X.Org XInput driver, version 19.1
    [ 131.656] (II) Using input driver 'evdev' for 'Power Button'
    [ 131.656] (**) Power Button: always reports core events
    [ 131.656] (**) evdev: Power Button: Device: "/dev/input/event5"
    [ 131.656] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 131.656] (--) evdev: Power Button: Found keys
    [ 131.656] (II) evdev: Power Button: Configuring as keyboard
    [ 131.656] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input5/event5"
    [ 131.656] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 131.656] (**) Option "xkb_rules" "evdev"
    [ 131.656] (**) Option "xkb_model" "evdev"
    [ 131.656] (**) Option "xkb_layout" "us"
    [ 131.668] (II) config/udev: Adding input device Power Button (/dev/input/event4)
    [ 131.668] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 131.668] (II) Using input driver 'evdev' for 'Power Button'
    [ 131.668] (**) Power Button: always reports core events
    [ 131.668] (**) evdev: Power Button: Device: "/dev/input/event4"
    [ 131.668] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 131.668] (--) evdev: Power Button: Found keys
    [ 131.668] (II) evdev: Power Button: Configuring as keyboard
    [ 131.668] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input4/event4"
    [ 131.668] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
    [ 131.668] (**) Option "xkb_rules" "evdev"
    [ 131.668] (**) Option "xkb_model" "evdev"
    [ 131.668] (**) Option "xkb_layout" "us"
    [ 131.669] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event15)
    [ 131.669] (II) No input driver specified, ignoring this device.
    [ 131.669] (II) This device may have been added with another device file.
    [ 131.669] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event16)
    [ 131.669] (II) No input driver specified, ignoring this device.
    [ 131.669] (II) This device may have been added with another device file.
    [ 131.669] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event17)
    [ 131.669] (II) No input driver specified, ignoring this device.
    [ 131.669] (II) This device may have been added with another device file.
    [ 131.669] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event18)
    [ 131.669] (II) No input driver specified, ignoring this device.
    [ 131.669] (II) This device may have been added with another device file.
    [ 131.669] (II) config/udev: Adding input device Saitek Cyborg R.A.T.7 Mouse (/dev/input/event0)
    [ 131.669] (**) Saitek Cyborg R.A.T.7 Mouse: Applying InputClass "evdev pointer catchall"
    [ 131.669] (**) Saitek Cyborg R.A.T.7 Mouse: Applying InputClass "Mouse Remap"
    [ 131.669] (II) Using input driver 'evdev' for 'Saitek Cyborg R.A.T.7 Mouse'
    [ 131.669] (**) Saitek Cyborg R.A.T.7 Mouse: always reports core events
    [ 131.669] (**) evdev: Saitek Cyborg R.A.T.7 Mouse: Device: "/dev/input/event0"
    [ 131.669] (**) evdev: Saitek Cyborg R.A.T.7 Mouse: ButtonMapping '1 2 3 4 5 6 7 8 9 10 11 12 0 0 0'
    [ 131.669] (--) evdev: Saitek Cyborg R.A.T.7 Mouse: Vendor 0x6a3 Product 0xcd7
    [ 131.669] (--) evdev: Saitek Cyborg R.A.T.7 Mouse: Found 17 mouse buttons
    [ 131.669] (--) evdev: Saitek Cyborg R.A.T.7 Mouse: Found scroll wheel(s)
    [ 131.669] (--) evdev: Saitek Cyborg R.A.T.7 Mouse: Found relative axes
    [ 131.669] (--) evdev: Saitek Cyborg R.A.T.7 Mouse: Found x and y relative axes
    [ 131.669] (II) evdev: Saitek Cyborg R.A.T.7 Mouse: Configuring as mouse
    [ 131.669] (II) evdev: Saitek Cyborg R.A.T.7 Mouse: Adding scrollwheel support
    [ 131.669] (**) evdev: Saitek Cyborg R.A.T.7 Mouse: YAxisMapping: buttons 4 and 5
    [ 131.669] (**) evdev: Saitek Cyborg R.A.T.7 Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 131.669] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/input/input0/event0"
    [ 131.669] (II) XINPUT: Adding extended input device "Saitek Cyborg R.A.T.7 Mouse" (type: MOUSE, id 8)
    [ 131.669] (II) evdev: Saitek Cyborg R.A.T.7 Mouse: initialized for relative axes.
    [ 131.669] (**) Saitek Cyborg R.A.T.7 Mouse: (accel) keeping acceleration scheme 1
    [ 131.669] (**) Saitek Cyborg R.A.T.7 Mouse: (accel) acceleration profile 0
    [ 131.669] (**) Saitek Cyborg R.A.T.7 Mouse: (accel) acceleration factor: 2.000
    [ 131.669] (**) Saitek Cyborg R.A.T.7 Mouse: (accel) acceleration threshold: 4
    [ 131.670] (II) config/udev: Adding input device Saitek Cyborg R.A.T.7 Mouse (/dev/input/mouse0)
    [ 131.670] (II) No input driver specified, ignoring this device.
    [ 131.670] (II) This device may have been added with another device file.
    [ 131.670] (II) config/udev: Adding input device Corsair Corsair Vengeance K60 Keyboard (/dev/input/event1)
    [ 131.670] (**) Corsair Corsair Vengeance K60 Keyboard: Applying InputClass "evdev keyboard catchall"
    [ 131.670] (II) Using input driver 'evdev' for 'Corsair Corsair Vengeance K60 Keyboard'
    [ 131.670] (**) Corsair Corsair Vengeance K60 Keyboard: always reports core events
    [ 131.670] (**) evdev: Corsair Corsair Vengeance K60 Keyboard: Device: "/dev/input/event1"
    [ 131.670] (--) evdev: Corsair Corsair Vengeance K60 Keyboard: Vendor 0x1b1c Product 0xa60
    [ 131.670] (--) evdev: Corsair Corsair Vengeance K60 Keyboard: Found keys
    [ 131.670] (II) evdev: Corsair Corsair Vengeance K60 Keyboard: Configuring as keyboard
    [ 131.670] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input1/event1"
    [ 131.670] (II) XINPUT: Adding extended input device "Corsair Corsair Vengeance K60 Keyboard" (type: KEYBOARD, id 9)
    [ 131.670] (**) Option "xkb_rules" "evdev"
    [ 131.670] (**) Option "xkb_model" "evdev"
    [ 131.670] (**) Option "xkb_layout" "us"
    [ 131.670] (II) config/udev: Adding input device Corsair Corsair Vengeance K60 Keyboard (/dev/input/event2)
    [ 131.670] (**) Corsair Corsair Vengeance K60 Keyboard: Applying InputClass "evdev keyboard catchall"
    [ 131.670] (II) Using input driver 'evdev' for 'Corsair Corsair Vengeance K60 Keyboard'
    [ 131.670] (**) Corsair Corsair Vengeance K60 Keyboard: always reports core events
    [ 131.670] (**) evdev: Corsair Corsair Vengeance K60 Keyboard: Device: "/dev/input/event2"
    [ 131.670] (--) evdev: Corsair Corsair Vengeance K60 Keyboard: Vendor 0x1b1c Product 0xa60
    [ 131.670] (--) evdev: Corsair Corsair Vengeance K60 Keyboard: Found 1 mouse buttons
    [ 131.670] (--) evdev: Corsair Corsair Vengeance K60 Keyboard: Found scroll wheel(s)
    [ 131.670] (--) evdev: Corsair Corsair Vengeance K60 Keyboard: Found relative axes
    [ 131.670] (II) evdev: Corsair Corsair Vengeance K60 Keyboard: Forcing relative x/y axes to exist.
    [ 131.670] (--) evdev: Corsair Corsair Vengeance K60 Keyboard: Found absolute axes
    [ 131.670] (II) evdev: Corsair Corsair Vengeance K60 Keyboard: Forcing absolute x/y axes to exist.
    [ 131.670] (--) evdev: Corsair Corsair Vengeance K60 Keyboard: Found keys
    [ 131.670] (II) evdev: Corsair Corsair Vengeance K60 Keyboard: Configuring as mouse
    [ 131.670] (II) evdev: Corsair Corsair Vengeance K60 Keyboard: Configuring as keyboard
    [ 131.670] (II) evdev: Corsair Corsair Vengeance K60 Keyboard: Adding scrollwheel support
    [ 131.670] (**) evdev: Corsair Corsair Vengeance K60 Keyboard: YAxisMapping: buttons 4 and 5
    [ 131.670] (**) evdev: Corsair Corsair Vengeance K60 Keyboard: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 131.670] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.1/input/input2/event2"
    [ 131.670] (II) XINPUT: Adding extended input device "Corsair Corsair Vengeance K60 Keyboard" (type: KEYBOARD, id 10)
    [ 131.670] (**) Option "xkb_rules" "evdev"
    [ 131.670] (**) Option "xkb_model" "evdev"
    [ 131.670] (**) Option "xkb_layout" "us"
    [ 131.670] (II) evdev: Corsair Corsair Vengeance K60 Keyboard: initialized for relative axes.
    [ 131.670] (WW) evdev: Corsair Corsair Vengeance K60 Keyboard: ignoring absolute axes.
    [ 131.670] (**) Corsair Corsair Vengeance K60 Keyboard: (accel) keeping acceleration scheme 1
    [ 131.670] (**) Corsair Corsair Vengeance K60 Keyboard: (accel) acceleration profile 0
    [ 131.670] (**) Corsair Corsair Vengeance K60 Keyboard: (accel) acceleration factor: 2.000
    [ 131.670] (**) Corsair Corsair Vengeance K60 Keyboard: (accel) acceleration threshold: 4
    [ 131.671] (II) config/udev: Adding input device Corsair Corsair Vengeance K60 Keyboard (/dev/input/event3)
    [ 131.671] (**) Corsair Corsair Vengeance K60 Keyboard: Applying InputClass "evdev keyboard catchall"
    [ 131.671] (II) Using input driver 'evdev' for 'Corsair Corsair Vengeance K60 Keyboard'
    [ 131.671] (**) Corsair Corsair Vengeance K60 Keyboard: always reports core events
    [ 131.671] (**) evdev: Corsair Corsair Vengeance K60 Keyboard: Device: "/dev/input/event3"
    [ 131.671] (--) evdev: Corsair Corsair Vengeance K60 Keyboard: Vendor 0x1b1c Product 0xa60
    [ 131.671] (--) evdev: Corsair Corsair Vengeance K60 Keyboard: Found keys
    [ 131.671] (II) evdev: Corsair Corsair Vengeance K60 Keyboard: Configuring as keyboard
    [ 131.671] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.2/input/input3/event3"
    [ 131.671] (II) XINPUT: Adding extended input device "Corsair Corsair Vengeance K60 Keyboard" (type: KEYBOARD, id 11)
    [ 131.671] (**) Option "xkb_rules" "evdev"
    [ 131.671] (**) Option "xkb_model" "evdev"
    [ 131.671] (**) Option "xkb_layout" "us"
    [ 131.671] (II) config/udev: Adding input device HDA Intel PCH Line Out Side (/dev/input/event10)
    [ 131.671] (II) No input driver specified, ignoring this device.
    [ 131.671] (II) This device may have been added with another device file.
    [ 131.671] (II) config/udev: Adding input device HDA Intel PCH Line Out CLFE (/dev/input/event11)
    [ 131.671] (II) No input driver specified, ignoring this device.
    [ 131.671] (II) This device may have been added with another device file.
    [ 131.671] (II) config/udev: Adding input device HDA Intel PCH Line Out Surround (/dev/input/event12)
    [ 131.671] (II) No input driver specified, ignoring this device.
    [ 131.671] (II) This device may have been added with another device file.
    [ 131.671] (II) config/udev: Adding input device HDA Intel PCH Line Out Front (/dev/input/event13)
    [ 131.671] (II) No input driver specified, ignoring this device.
    [ 131.671] (II) This device may have been added with another device file.
    [ 131.671] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event6)
    [ 131.671] (II) No input driver specified, ignoring this device.
    [ 131.671] (II) This device may have been added with another device file.
    [ 131.671] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event7)
    [ 131.671] (II) No input driver specified, ignoring this device.
    [ 131.671] (II) This device may have been added with another device file.
    [ 131.672] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event8)
    [ 131.672] (II) No input driver specified, ignoring this device.
    [ 131.672] (II) This device may have been added with another device file.
    [ 131.672] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event9)
    [ 131.672] (II) No input driver specified, ignoring this device.
    [ 131.672] (II) This device may have been added with another device file.
    [ 131.672] (II) config/udev: Adding input device PC Speaker (/dev/input/event14)
    [ 131.672] (II) No input driver specified, ignoring this device.
    [ 131.672] (II) This device may have been added with another device file.
    Doesn't seem like there's anything wrong. Here's /var/log/lightdm/lightdm.log
    [+0.47s] DEBUG: Logging to /var/log/lightdm/lightdm.log
    [+0.47s] DEBUG: Starting Light Display Manager 1.6.0, UID=0 PID=255
    [+0.47s] DEBUG: Loaded configuration from /etc/lightdm/lightdm.conf
    [+0.47s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
    [+0.87s] DEBUG: Registered seat module xlocal
    [+0.87s] DEBUG: Registered seat module xremote
    [+0.87s] DEBUG: Adding default seat
    [+0.87s] DEBUG: Starting seat
    [+0.87s] DEBUG: Starting new display for greeter
    [+0.87s] DEBUG: Starting local X display
    [+1.08s] DEBUG: Could not run plymouth --ping: Failed to execute child process "plymouth" (No such file or directory)
    [+1.08s] DEBUG: Using VT 7
    [+1.09s] DEBUG: Activating VT 7
    [+1.09s] DEBUG: Logging to /var/log/lightdm/x-0.log
    [+1.16s] DEBUG: Writing X server authority to /run/lightdm/root/:0
    [+1.16s] DEBUG: Launching X Server
    [+1.19s] DEBUG: Launching process 263: /usr/bin/X :0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
    [+1.19s] DEBUG: Waiting for ready signal from X server :0
    [+1.19s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
    [+1.19s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
    [+7.12s] DEBUG: Got signal 10 from process 263
    [+7.12s] DEBUG: Got signal from X server :0
    [+7.12s] DEBUG: Connecting to XServer :0
    [+7.13s] DEBUG: Starting greeter
    [+7.13s] DEBUG: Started session 284 with service 'lightdm-greeter', username 'lightdm'
    [+7.42s] DEBUG: Session 284 authentication complete with return value 0: Success
    [+7.42s] DEBUG: Greeter authorized
    [+7.42s] DEBUG: Logging to /var/log/lightdm/x-0-greeter.log
    [+7.47s] DEBUG: Session 284 running command /usr/sbin/lightdm-gtk-greeter
    [+7.47s] DEBUG: org.freedesktop.Accounts does not exist, falling back to passwd file
    [+9.12s] DEBUG: Greeter connected version=1.6.0
    [+9.12s] DEBUG: Greeter connected, display is ready
    [+9.12s] DEBUG: New display ready, switching to it
    [+9.12s] DEBUG: Activating VT 7
    [+11.04s] DEBUG: Greeter closed communication channel
    [+11.04s] DEBUG: Session 284 exited with return value 139
    [+11.04s] DEBUG: Greeter quit
    [+11.04s] DEBUG: Failed to start greeter
    [+11.04s] DEBUG: Stopping display
    [+11.04s] DEBUG: Sending signal 15 to process 263
    [+11.47s] DEBUG: Process 263 exited with return value 0
    [+11.47s] DEBUG: X server stopped
    [+11.47s] DEBUG: Removing X server authority /run/lightdm/root/:0
    [+11.47s] DEBUG: Releasing VT 7
    [+11.47s] DEBUG: Display server stopped
    [+11.47s] DEBUG: Switching to greeter
    [+11.47s] DEBUG: Starting new display for greeter
    [+11.47s] DEBUG: Starting local X display
    [+11.47s] DEBUG: Using VT 7
    [+11.48s] DEBUG: Logging to /var/log/lightdm/x-0.log
    [+11.48s] DEBUG: Writing X server authority to /run/lightdm/root/:0
    [+11.48s] DEBUG: Launching X Server
    [+11.48s] DEBUG: Launching process 360: /usr/bin/X :0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
    [+11.48s] DEBUG: Waiting for ready signal from X server :0
    [+11.91s] DEBUG: Got signal 10 from process 360
    [+11.91s] DEBUG: Got signal from X server :0
    [+11.91s] DEBUG: Connecting to XServer :0
    [+11.91s] DEBUG: Starting greeter
    [+11.91s] DEBUG: Started session 372 with service 'lightdm-greeter', username 'lightdm'
    [+11.92s] DEBUG: Session 372 authentication complete with return value 0: Success
    [+11.92s] DEBUG: Greeter authorized
    [+11.92s] DEBUG: Logging to /var/log/lightdm/x-0-greeter.log
    [+11.92s] DEBUG: Session 372 running command /usr/sbin/lightdm-gtk-greeter
    [+12.07s] DEBUG: Greeter connected version=1.6.0
    [+12.07s] DEBUG: Greeter connected, display is ready
    [+12.07s] DEBUG: New display ready, switching to it
    [+12.07s] DEBUG: Activating VT 7
    [+12.39s] DEBUG: Greeter closed communication channel
    [+12.39s] DEBUG: Session 372 exited with return value 139
    [+12.39s] DEBUG: Greeter quit
    [+12.39s] DEBUG: Failed to start greeter
    [+12.39s] DEBUG: Stopping display
    [+12.39s] DEBUG: Sending signal 15 to process 360
    [+12.73s] DEBUG: Process 360 exited with return value 0
    [+12.73s] DEBUG: X server stopped
    [+12.73s] DEBUG: Removing X server authority /run/lightdm/root/:0
    [+12.73s] DEBUG: Releasing VT 7
    [+12.73s] DEBUG: Display server stopped
    [+12.73s] DEBUG: Switching to greeter
    [+12.73s] DEBUG: Starting new display for greeter
    [+12.73s] DEBUG: Starting local X display
    [+12.73s] DEBUG: Using VT 7
    [+12.73s] DEBUG: Logging to /var/log/lightdm/x-0.log
    [+12.73s] DEBUG: Writing X server authority to /run/lightdm/root/:0
    [+12.73s] DEBUG: Launching X Server
    [+12.73s] DEBUG: Launching process 396: /usr/bin/X :0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
    [+12.73s] DEBUG: Waiting for ready signal from X server :0
    [+13.18s] DEBUG: Got signal 10 from process 396
    [+13.18s] DEBUG: Got signal from X server :0
    [+13.18s] DEBUG: Connecting to XServer :0
    [+13.18s] DEBUG: Starting greeter
    [+13.18s] DEBUG: Started session 401 with service 'lightdm-greeter', username 'lightdm'
    [+13.18s] DEBUG: Session 401 authentication complete with return value 0: Success
    [+13.18s] DEBUG: Greeter authorized
    [+13.18s] DEBUG: Logging to /var/log/lightdm/x-0-greeter.log
    [+13.18s] DEBUG: Session 401 running command /usr/sbin/lightdm-gtk-greeter
    [+13.28s] DEBUG: Greeter connected version=1.6.0
    [+13.28s] DEBUG: Greeter connected, display is ready
    [+13.28s] DEBUG: New display ready, switching to it
    [+13.28s] DEBUG: Activating VT 7
    [+36.01s] DEBUG: Greeter closed communication channel
    [+36.01s] DEBUG: Session 401 exited with return value 139
    [+36.01s] DEBUG: Greeter quit
    [+36.01s] DEBUG: Failed to start greeter
    [+36.01s] DEBUG: Stopping display
    [+36.01s] DEBUG: Sending signal 15 to process 396
    [+36.02s] DEBUG: Process 396 exited with return value 0
    [+36.02s] DEBUG: X server stopped
    [+36.02s] DEBUG: Removing X server authority /run/lightdm/root/:0
    [+36.02s] DEBUG: Releasing VT 7
    [+36.02s] DEBUG: Display server stopped
    [+36.02s] DEBUG: Switching to greeter
    [+36.02s] DEBUG: Starting new display for greeter
    [+36.02s] DEBUG: Starting local X display
    [+36.02s] DEBUG: Using VT 7
    [+36.02s] DEBUG: Activating VT 7
    [+36.02s] DEBUG: Logging to /var/log/lightdm/x-0.log
    [+36.02s] DEBUG: Writing X server authority to /run/lightdm/root/:0
    [+36.02s] DEBUG: Launching X Server
    [+36.02s] DEBUG: Launching process 440: /usr/bin/X :0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
    [+36.02s] DEBUG: Waiting for ready signal from X server :0
    [+36.48s] DEBUG: Got signal 10 from process 440
    [+36.48s] DEBUG: Got signal from X server :0
    [+36.48s] DEBUG: Connecting to XServer :0
    [+36.48s] DEBUG: Starting greeter
    [+36.48s] DEBUG: Started session 457 with service 'lightdm-greeter', username 'lightdm'
    [+36.48s] DEBUG: Session 457 authentication complete with return value 0: Success
    [+36.48s] DEBUG: Greeter authorized
    [+36.48s] DEBUG: Logging to /var/log/lightdm/x-0-greeter.log
    [+36.48s] DEBUG: Session 457 running command /usr/sbin/lightdm-gtk-greeter
    [+36.56s] DEBUG: Greeter connected version=1.6.0
    [+36.56s] DEBUG: Greeter connected, display is ready
    [+36.56s] DEBUG: New display ready, switching to it
    [+36.56s] DEBUG: Activating VT 7
    [+36.77s] DEBUG: Greeter closed communication channel
    [+36.77s] DEBUG: Session 457 exited with return value 139
    [+36.77s] DEBUG: Greeter quit
    [+36.77s] DEBUG: Failed to start greeter
    [+36.77s] DEBUG: Stopping display
    [+36.77s] DEBUG: Sending signal 15 to process 440
    [+37.10s] DEBUG: Process 440 exited with return value 0
    [+37.10s] DEBUG: X server stopped
    [+37.10s] DEBUG: Removing X server authority /run/lightdm/root/:0
    [+37.10s] DEBUG: Releasing VT 7
    [+37.10s] DEBUG: Display server stopped
    [+37.10s] DEBUG: Switching to greeter
    [+37.10s] DEBUG: Starting new display for greeter
    [+37.10s] DEBUG: Starting local X display
    [+37.10s] DEBUG: Using VT 7
    [+37.10s] DEBUG: Logging to /var/log/lightdm/x-0.log
    [+37.10s] DEBUG: Writing X server authority to /run/lightdm/root/:0
    [+37.10s] DEBUG: Launching X Server
    [+37.10s] DEBUG: Launching process 482: /usr/bin/X :0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
    [+37.10s] DEBUG: Waiting for ready signal from X server :0
    [+37.52s] DEBUG: Got signal 10 from process 482
    [+37.52s] DEBUG: Got signal from X server :0
    [+37.52s] DEBUG: Connecting to XServer :0
    [+37.52s] DEBUG: Starting greeter
    [+37.52s] DEBUG: Started session 487 with service 'lightdm-greeter', username 'lightdm'
    [+37.53s] DEBUG: Session 487 authentication complete with return value 0: Success
    [+37.53s] DEBUG: Greeter authorized
    [+37.53s] DEBUG: Logging to /var/log/lightdm/x-0-greeter.log
    [+37.53s] DEBUG: Session 487 running command /usr/sbin/lightdm-gtk-greeter
    [+37.61s] DEBUG: Greeter connected version=1.6.0
    [+37.61s] DEBUG: Greeter connected, display is ready
    [+37.61s] DEBUG: New display ready, switching to it
    [+37.61s] DEBUG: Activating VT 7
    [+60.57s] DEBUG: Greeter closed communication channel
    [+60.57s] DEBUG: Session 487 exited with return value 139
    [+60.57s] DEBUG: Greeter quit
    [+60.57s] DEBUG: Failed to start greeter
    [+60.57s] DEBUG: Stopping display
    [+60.57s] DEBUG: Sending signal 15 to process 482
    [+60.59s] DEBUG: Process 482 exited with return value 0
    [+60.59s] DEBUG: X server stopped
    [+60.59s] DEBUG: Removing X server authority /run/lightdm/root/:0
    [+60.59s] DEBUG: Releasing VT 7
    [+60.59s] DEBUG: Display server stopped
    [+60.59s] DEBUG: Switching to greeter
    [+60.59s] DEBUG: Starting new display for greeter
    [+60.59s] DEBUG: Starting local X display
    [+60.59s] DEBUG: Using VT 7
    [+60.59s] DEBUG: Activating VT 7
    [+60.59s] DEBUG: Logging to /var/log/lightdm/x-0.log
    [+60.59s] DEBUG: Writing X server authority to /run/lightdm/root/:0
    [+60.59s] DEBUG: Launching X Server
    [+60.59s] DEBUG: Launching process 543: /usr/bin/X :0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
    [+60.59s] DEBUG: Waiting for ready signal from X server :0
    [+61.04s] DEBUG: Got signal 10 from process 543
    [+61.04s] DEBUG: Got signal from X server :0
    [+61.04s] DEBUG: Connecting to XServer :0
    [+61.04s] DEBUG: Starting greeter
    [+61.04s] DEBUG: Started session 548 with service 'lightdm-greeter', username 'lightdm'
    [+61.04s] DEBUG: Session 548 authentication complete with return value 0: Success
    [+61.04s] DEBUG: Greeter authorized
    [+61.04s] DEBUG: Logging to /var/log/lightdm/x-0-greeter.log
    [+61.04s] DEBUG: Session 548 running command /usr/sbin/lightdm-gtk-greeter
    [+61.12s] DEBUG: Greeter connected version=1.6.0
    [+61.12s] DEBUG: Greeter connected, display is ready
    [+61.12s] DEBUG: New display ready, switching to it
    [+61.12s] DEBUG: Activating VT 7
    [+61.34s] DEBUG: Greeter closed communication channel
    [+61.34s] DEBUG: Session 548 exited with return value 139
    [+61.34s] DEBUG: Greeter quit
    [+61.34s] DEBUG: Failed to start greeter
    [+61.34s] DEBUG: Stopping display
    [+61.34s] DEBUG: Sending signal 15 to process 543
    [+61.67s] DEBUG: Process 543 exited with return value 0
    [+61.67s] DEBUG: X server stopped
    [+61.67s] DEBUG: Removing X server authority /run/lightdm/root/:0
    [+61.67s] DEBUG: Releasing VT 7
    [+61.67s] DEBUG: Display server stopped
    [+61.67s] DEBUG: Switching to greeter
    [+61.67s] DEBUG: Starting new display for greeter
    [+61.67s] DEBUG: Starting local X display
    [+61.67s] DEBUG: Using VT 7
    [+61.67s] DEBUG: Logging to /var/log/lightdm/x-0.log
    [+61.67s] DEBUG: Writing X server authority to /run/lightdm/root/:0
    [+61.67s] DEBUG: Launching X Server
    [+61.67s] DEBUG: Launching process 568: /usr/bin/X :0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
    [+61.67s] DEBUG: Waiting for ready signal from X server :0
    [+62.12s] DEBUG: Got signal 10 from process 568
    [+62.12s] DEBUG: Got signal from X server :0
    [+62.12s] DEBUG: Connecting to XServer :0
    [+62.12s] DEBUG: Starting greeter
    [+62.12s] DEBUG: Started session 573 with service 'lightdm-greeter', username 'lightdm'
    [+62.13s] DEBUG: Session 573 authentication complete with return value 0: Success
    [+62.13s] DEBUG: Greeter authorized
    [+62.13s] DEBUG: Logging to /var/log/lightdm/x-0-greeter.log
    [+62.13s] DEBUG: Session 573 running command /usr/sbin/lightdm-gtk-greeter
    [+62.22s] DEBUG: Greeter connected version=1.6.0
    [+62.22s] DEBUG: Greeter connected, display is ready
    [+62.22s] DEBUG: New display ready, switching to it
    [+62.22s] DEBUG: Activating VT 7
    [+65.92s] DEBUG: Got signal 15 from process 1
    [+65.92s] DEBUG: Caught Terminated signal, shutting down
    [+65.92s] DEBUG: Stopping display manager
    [+65.92s] DEBUG: Stopping seat
    [+65.92s] DEBUG: Stopping display
    [+65.92s] DEBUG: Session 573: Sending SIGTERM
    [+65.92s] DEBUG: Greeter closed communication channel
    [+65.92s] DEBUG: Session 573 exited with return value 0
    [+65.92s] DEBUG: Greeter quit
    [+65.92s] DEBUG: Sending signal 15 to process 568
    Looks like the greeter is repeatedly exiting, but I don't know how to diagnose the problem. Thanks for the help.
    Last edited by corban (2013-05-12 16:50:57)

  • New window manager (with prototype!) [wmii-like] --- looking for help

    I have a prototype for a new window manager in the style of wmii. It is called
    cakewm. I currently have a prototype version implemented in pygame, and would
    like help moving this to use X---making it a real window manager.
    Disclaimer: I have a very limited knowledge of X11 and window manager
    development. The most I've done is add a couple new features to wmfs.
    To get the code
    > git clone git://github.com/saikobee/cakewm.git
    Then run main.py. cakewm depends on pygame.
    Upon running, press Alt-Enter to fullscreen cakewm and intercept keybinds, or
    Alt-Space to just intercept keybinds.  Press Alt-Esc to quit. The window
    manager related keybinds are listed in the file binds.conf.
    Config note: <WSCA-x> means Windows-Shift-Control-Alt-x
    Implementation note: pypixel.py is a large and mostly useless dependency. I
    forked a library I made previously rather than coding straight in pygame.
    cakewm's goals are to be similar to wmii, but with more functionality, easier
    configurability, and saner defaults.
    - cakewm is fully functional using the keyboard. Mouse support can come later.
    - cakewm provides 9 workspaces per monitor.
    - cakewm manages each workspace as a group of columns. Each column is like a
      wmii default split, except each window can have other windows "stacked" on
      top of or behind it.
    - cakewm manages column sizes (and window sizes within columns) using a
      master/slave paradigm, with the ability to adjust the size ratios.
    - cakewm's configuration file is simple key=val pairs, with the ability to
      include other files like in C.
    - cakewm has a slightly larger emphasis on window decorations (adjustable
      size---even in tiled mode) and themes (nothing bloated, like pixmaps or
      gradients---it's all still simple colors).
    - cakewm will have proper support for international text (Japanese text in
      window titles or the wmii status bar generally render as boxes) through the
      use of a more advanced text library such as Pango.
    Please let me know if you have comments, questions, or concerns. If you are
    interested in helping, get in touch with me. If you know somewhere better to
    look for volunteers, please let me know.

    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).

  • [Lync 2013] - Desktop Sharing and taking control

    Hello,
    In Lync 2013 when someone shares his/her screen and I'm taking control of the shared screen I have the following problem:
    Everything works fine when I'm in control with other person's desktop, however when the Lync IM/Sharing window looses focus and then the focus is regained by clicking on the shared desktop, all the input is frozen in the Lync IM window.
    for example:
    I take control of shared screen, do something on the shared desktop, then I open something on my own PC (the Lync window is loosing focus at this moment), then when I click on the shared screen inside Lync IM window to continue controlling the remote desktop
    any input to the Lync window is "frozen".
    There is some error sound comming everytime I click in the Lync IM window during this time - just as there was some invisible popup that is blocking interaction with parent window
    to solve this I have to once again loose focus of Lync IM window and then regain it again.
    This is on many machines (Windows 7 64bit / Windows 8.1 Preview 64bit) using Lync 2013 32bit with and without updates
    I'm using multiple monitors, but it's the same on a single display - just open Lync IM/Sharing window in one half of the screen and open notepad on other half (don't minimize windows, just switch between them during sharing)
    Best Regards

    Hi Bartek,
    Did the issue happen on Windows 7/8 32 bit using Lync 2013 32 bit?
    Try Clean Boot to disable all non-Microsoft services and start Lync again:
    How to Clean Boot:
    http://support.microsoft.com/kb/929135
    Since the OS is 64 bit, please remove Lync 2013 32 bit and install Lync 2013 client 64 bit and apply the latest update then test the issue again.
    Best Regards,
    Eason Huang
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • 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.

  • How To Install/Configure OEM Grid Control On Windows

    Hi,
    I've downloaded OEM Grid Control for windows (32-bit) from oracle site.
    This .zip files has 3 more .zip files eg
    File Size
    3822442.zip 510 MB (535,208,588 bytes)
    3731596.zip 275 KB (282,502 bytes)
    3731593.zip 510 MB (535,047,905 bytes)
    Can you pls tell me which one is actual OEM Grid Control software, and what are the other .zip files ?
    Pls email me at [email protected]
    Your help greatly appretiated.
    Regards,

    You will be needing all three zip files. It will contain all files needed for installation of a repository Database Instance, the Management Server and an Management Agent.
    cheers
    Rob

  • Desktop Window Manager Service on Windows 7 Starter - Any Reason to Leave It Running?

    Hello everyone,
    -As per title, I'd like to know whether is it better to turn off Desktop Window Manager Session Manager (UxSms) service on Windows 7 Starter - or not. I mean changing the service's default startup type from Automatic to Manual (or Disabled).
    -In Windows 7 Starter, the Aero theme and desktop composition are not available at all (not even a basic/partial one), so letting Desktop Window Manager (DWM.exe) to continuously run is useless as it does absolutely nothing. Is my deduction correct?
    -All opinions and suggestions are welcomed, thank you very much.
    Regards,
    -Musafir_86.

    Please read the information posted @
    http://msdn.microsoft.com/en-us/library/windows/desktop/aa969540%28v=vs.85%29.aspx
    Desktop Window Manager
    The desktop composition feature, introduced in Windows Vista, fundamentally changed the way applications display pixels on the screen.  When desktop composition is enabled, individual windows no longer draw directly to the screen or primary display
    device as they did in previous versions of Windows. Instead, their drawing is redirected to off-screen surfaces in video memory, which are then rendered into a desktop image and presented on the display.
    Desktop composition is performed by the Desktop Window Manager (DWM).  Through desktop composition, DWM enables visual effects on the desktop
    as well as various features such as glass window frames, 3-D window transition animations, Windows Flip and Windows Flip3D, and high resolution support.
    The Desktop Window Manager runs as a Windows service. It can be enabled and disabled through the Administrative Tools Control Panel item, under Services, as Desktop Window Manager Session Manager.
    Many of the DWM features can be controlled or accessed by an application through the DWM APIs.  The following documentation describes the features and requirements of the DWM APIs.
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

  • How do I change twm to fvwm2 window manager switch?

    Apple's X11 offering uses twm, which unfortunately I don't really like, and would like to replace it with fvwm2. I've tried this little trick, and boy, so far, no luck. Too bad I'm not a better systems admin. Does anyone have a howto on getting the Apple to be happy with a different window manager??
    Failing that, has anyone found the dot file that defines the twm as using a "drawn" window placement system. This really is a bother when trying to use Unix apps in rootless mode, since there is no "background" on which to draw the new window.

    A-okay. This was resolved using the suggested enlightenment as my new window manager... light footprint, and excellent window control.
    Enlightenment is easy to use as a simple call from the .xinitrc file. Used xnest to try a variety of window managers out side by side, bringing up a window running each of several wm's in each of the xnest windows.
    Downloaded from fink...
    In .xinitrc file in home area (cd + carriage return location)
    exec /sw/bin/enlightenment

  • Grid Control for windows

    Hi Experts,
    We're trying to download and install Oracle grid control for windows 64bit but we can't find any 64bit release!
    Can we safely download and install Enterprise Manager 11g Grid Control Release (11.1.0.1.0) - Windows 32bit from http://www.oracle.com/technetwork/oem/grid-control/downloads/index.html ? or should we be installing a different version??
    Should Grid control be installed on the DB server in the 1st place or should it be installed on another server?
    Current Oracle Software: 11.2.0.1 64bit.
    Server OS: Windows 2008 Server 64bit.
    Can you kindly let us know.
    Thanks

    We finally got our facts right..
    The Grid Control Enterprise Manager comes only in 32 bits.. However the Grid Control agent that needs to be installed on the DB server comes in 32/64bits and is supported under different OS platforms.
    Metalink (Doc ID 412431.1) shows the Oracle Enterprise Manager Grid Control Certification Checker/matrix that we found extremely useful.
    Enterprise Manager Grid Control comes with the basic features and is free to use. Any extra features are considered addons and do need to be properly licensed.
    Thanks

  • Subtle - another tiling window manager

    It's been a while since the first subtle AUR package came up and there was never neither an introduction nor a thread here in the forum. Time to get this started and to hopefully get opinions/feedback of the of users who already gave/want to give subtle a try.
    For all of you who never heared about subtle - here comes the intro:
    subtle is another tiling window manager on the field with a grid-based manual tiling window manager with a strong focus on easy but customizable look and feel. In comparison to other tiling windows managers, subtle has no automatic tiling of the screen size in any way, instead windows are arranged according to positions inside of a grid - these positions are called gravities - which can completely be controlled with key bindings.
    subtle also has a Ruby based config with support for lambdas as key bind actions, a wmctrl-like commandline tool (subtler) to interact with subtle and an extension (subtlext) for Ruby that is capable of doing the same and even more!
    There are also small Ruby applets (sublets) that can show various stuff like system load and the time. The management of these scripts can be done with sur (Subtle User Repository) - a small command line script similar to gem which makes installing of a subtlet a piece of cake e.g.:
    sur install clock
    Windows placement and window properties are determined by a complete tagging system for clients and views and can be manipulated in the config and/or per runtime with subtler/subtlext.
    Features
    - Ruby integration for config/key actions and hooks
    - Flexible panels with loadable Ruby scripts (sublets)
    - Integrated System tray
    - Complete tagging system
    - ICCM/EWMH-compliant
    - Lightweight
    Screenshots
    Install
    The AUR packages: subtle subtle-hg sur-hg
    I would suggest to pick the subtle-hg package to get the latest changes.
    Contact
    If you have problems, suggestions or just want to talk about subtle feel free to join #subtle on irc.freenode.org or drop a mail to unexist at dorfelite dot net.
    Last edited by unexist (2010-04-24 15:40:02)

    dcurtis wrote:
    I love this gravity idea but the WM in it's current state would not allow me to be productive (no offense) and I have a distaste for ruby ( love python ) but I'm willing to grow.  However, here are my comments:
    1) being able to tweak the gravity settings would be nice, and per-tag.  I like to have a big left window (stacked) and a column of two windows on the right.  I use wmii and this does this OK by dividing the right column.  My one grip is the I could stack on the right, but I couldn't divide AND stack.  I see the potential for that w/ subtle.  Here is my current ss: http://static.milkbox.net/ss/ss-2009-05-06.png
    2) it would be nice if you could have movement between gravities.  I'd like to move between columns.  And my gripe about like, musca and ratpoison is that when i do move between columns it doesn't keep track of the previous vertical position.  Starting with the bottom right focused, moving to the left, and then moving back to the right focuses me in the top right.  I think it would be _REALLY_ cool if you had some sort of column based movement (left gravity, center gravity, right gravity) that would cycle, and also movement up through the stack.  Not sure how this would work.
    3) I prefer that new windows are created with the same gravity as the windows already open.  I would guess this is fairly easy to do.
    4) switch to python... I AM KIDDING.  but seriously, i know it'll never happen but that's cool.  I just wanted to post this #4!...
    anyways, keep up the good work.
    1 + 2) What do you mean with 'per tag'? You can assign gravity tags to clients witht he config so that any layout is possible and you can freely create your own movement stuff with the grabs. Subtlext gives you control over gravities of the clients. Yes, it's Ruby and I won't argue about like you did in 4) - it's a matter of taste and I really like Ruby.
    3) So just to understand this: If you set the top left gravity to a client, you would prefer that the next client also gets top left gravity?
    Wra!th wrote:Floating windows need to be stackable (egbe able to bring one infront of another using the mouse)
    Well, actually this was in subtle but was removed in favor for the WindowRaise and WindowLower grab that allows e.g. to cycle through windows with center gravity.
    milomouse wrote:A smaller complaint, which may or may not be due to my own ignorance, is that switching views (jump) with the shortcut seems to be a little picky. Sometimes I can use the shortcut to switch views and sometimes it refuses to work. Seems to happen mostly when I'm on an empty view and try to switch (with the shortcut) to another . I don't know if it loses focus or what. Anyway, these are minor compared to my enjoyment with Subtle so far. Thanks again.
    Oh, yes. I will fix it shortly tomorrow - you may write a ticket for it so that you can see when it's fixed.
    Last edited by unexist (2009-05-10 09:57:51)

  • Window manager service object

    We use a user-visible service object to manage the positioning and
    cascading of our client windows, whether modal or not. Before each
    window performs an Open(), it registers it's reference and title
    with the SO. If there are other active windows of the same type,
    the title is modified to include a colon and count number, as in
    normal Windows applications. After the window performs the Close()
    method, it de-registers itself with the SO. Whilst open, the window
    can also call a method on the SO to cascade all active windows.
    (Every window has a Window\Cascade menu item for this purpose.)
    One of the reasons for using the SO to implement cascading, was to
    enable the user to cascade only the Forte application windows. If a
    non-Forte window gets in the way, you can use the Forte cascade to
    bring the Forte windows in front of it again !
    As an aside, the only windows that we have that are modal, are very
    small input windows that don't need much in the way of behaviour.
    As most of our windows are started using START TASKs, all windows
    need to keep references to child windows that they have
    instantiated, in order to perform orderly shutdowns, iconising and
    re-opening.
    Have fun !
    Justin Levis
    Hydro-Electric Commission
    Hobart, Tasmania
    Australia

    Please read the information posted @
    http://msdn.microsoft.com/en-us/library/windows/desktop/aa969540%28v=vs.85%29.aspx
    Desktop Window Manager
    The desktop composition feature, introduced in Windows Vista, fundamentally changed the way applications display pixels on the screen.  When desktop composition is enabled, individual windows no longer draw directly to the screen or primary display
    device as they did in previous versions of Windows. Instead, their drawing is redirected to off-screen surfaces in video memory, which are then rendered into a desktop image and presented on the display.
    Desktop composition is performed by the Desktop Window Manager (DWM).  Through desktop composition, DWM enables visual effects on the desktop
    as well as various features such as glass window frames, 3-D window transition animations, Windows Flip and Windows Flip3D, and high resolution support.
    The Desktop Window Manager runs as a Windows service. It can be enabled and disabled through the Administrative Tools Control Panel item, under Services, as Desktop Window Manager Session Manager.
    Many of the DWM features can be controlled or accessed by an application through the DWM APIs.  The following documentation describes the features and requirements of the DWM APIs.
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

  • Window Manager\Window Manager Group

    Based on customer requirements we need to set Bypass traverse checking rights for our Server 2012 boxes. In doing so we noticed that there is a user or group named Window Manager\Window Manager Group. I have seen references in other threads to this user
    pointing to the SID (S-1-5-90-0), but this is not documented anywhere on Microsoft website that I can find. I used Powershell to list all of the users, and I do not see a user or group on my Server 2012 box that matches this.
    Given no response from Microsoft and no documentation, I cannot effectively decide what I should do with this.
    It looks kind of shady that we are granting rights to a SID / Account that we cannot see, so I am wondering if this is some remnant for a part of Server 2012 that didn't get deployed when the code was released to manufacturing. Can some please confirm that
    it is OK to drop this user or group (not even sure which one it is) from the Bypass Traverse Checking user right?

    Hi，
    Based on my research,it is not recommended to remove the group ‘Window manager\Windows manager group’ from Bypass traverse checking or Increase a process working set.
    • Both the above user rights are utilized in windows 8/2012 for performance impacts.
    • The above mentioned group cannot be added manually to any other groups or no user can be a part of it as it does not resolve in object picker. We cannot even add ACLs to this group.
    • Due to above reasons, it is not a security breach in your environment.
    This group is a virtual group that is present on every Windows 2012 machine. The DWM.EXE that is used to manage he desktop experience runs under the security context of an account under this group and this is used to provide less privilege to the DWM.EXE.
    As such this is not documented anywhere in any of public documents. This is a design decision made by the product team which is part of the architecture of the OS. As such the practice is not to remove this group from both the user rights assignment mentioned.
    How Bypass traverse checking affects performance:
    When you try to access c:\foo\bar\baz\bletch\george.txt, “the rules” say that you need to confirm that the user has traverse access to:
              C:\foo
              C:\foo\bar
              C:\foo\bar\baz
              C:\foo\bar\baz\bletch
    If you didn’t have the “bypass traverse checking” privilege, the system would have to open each of these directories in turn and do an access check to make sure you had access to all the intermediate nodes in the path to the file.  With bypass traverse
    checking, the filesystems skip all those checks and just check to make sure you have your desired access to the file you’re opening.
    How increase a process working set affects performance:
    This settings controls who can increase the working set of a process when in memory. Working set is the data that is resending in the Ram that is visible to the process. This helps in expanding the memory a process stores in RAM thereby reducing page faults
    (paging out memory to virtual memory which will induce delays of copying the memory back to RAM).
    Given the above reasons, I strongly recommend you not to remove ‘Windows manager\Windows manager group’ from Bypass traverse checking as well as increase a process working set user rights assignment.
    Thanks.

  • Favourite window manager config file format

    My quest for the perfect window manager never seems to end. And even though my needs in a window manager are pretty simple, one thing I often get hung up on is the configuration format/syntax. Some window managers, though perfectly useable, are such a nuisance to configure (for example: Openbox's nasty XML files).
    So if you had to choose your favourite window manager solely based upon its configuration file format, which window manager would you choose?
    For me, ratpoison is probably the winner. A ratpoisonrc file is really easy to read and edit, and all of the commands and variables are well documented in the manual page.
    Please share your ideas - maybe it will help me to settle on a window manager that I'm happy with!

    I've used Window Maker the most over the past many years. It's extremely light and fast. (As opposed to something like GNOME) It handles multiple desktops, application launching, and application switching by itself. (As opposed to something like OpenBox)
    I think the configuration format is the "official" NeXTSTEP / GNUstep configuration format, which looks like this:
    DontLinkWorkspaces = NO;
    MenuDisabledColor = "#999999";
    IconTitleBack = "#333333";
    PixmapPath = (
    "/home/tester/GNUstep/Library/WindowMaker/Pixmaps",
    "/home/tester/GNUstep/Library/WindowMaker/Backgrounds",
    "/usr/share/WindowMaker/Pixmaps",
    "/usr/share/WindowMaker/Backgrounds",
    "/usr/X11R6/include/X11/pixmaps",
    "/usr/local/share/pixmaps",
    "/usr/share/pixmaps"
    FTitleBack = (solid, "#0088CC");
    ClipTitleFont = "Arial:slant=0:weight=200:width=100:pixelsize=10";
    MaximizeKey = "Mod1+F";
    IconTitleFont = "Arial:slant=0:weight=80:width=100:pixelsize=9";
    LargeDisplayFont = "Arial:slant=0:weight=80:width=100:pixelsize=24";
    DisableClip = YES;
    MoveDisplay = none;
    WindowShortcut10Key = None;
    IconTitleColor = white;
    WindowShortcut3Key = None;
    MenuTitleFont = "Arial:slant=0:weight=200:width=100:pixelsize=12";
    WindowShortcut4Key = None;
    NoWindowOverDock = NO;
    WorkspaceBack = (
    tpixmap,
    "/home/couzelis/Library/Wallpaper/Tiles/Black Holly.png",
    gray20
    HighlightTextColor = white;
    EdgeResistance = 0;
    WindowShortcut9Key = None;
    HelpBalloons = YES;
    PrevWorkspaceKey = "Control+Mod1+Left";
    AutoArrangeIcons = YES;
    MoveResizeKey = None;
    AppIconBalloons = YES;
    WindowTitleFont = "Arial:slant=0:weight=200:width=100:pixelsize=12";
    WindowPlaceOrigin = (0, 0);
    LHMaximizeKey = None;
    UseSaveUnders = YES;
    ResizebarBack = (solid, "#333333");
    KbdModeLock = NO;
    CycleActiveHeadOnly = NO;
    WindowShortcut1Key = None;
    ShowClipTitle = NO;
    RHMaximizeKey = None;
    WindowShortcut2Key = None;
    ToggleKbdModeKey = None;
    MiniwindowTitleBalloons = YES;
    ShadeKey = "Mod1+S";
    MaximusKey = None;
    WindowShortcut7Key = None;
    MenuTextBack = (solid, "#ECF2F5");
    WindowPlacement = random;
    RaiseAppIconsWhenBouncing = YES;
    ResizeIncrement = 0;
    CycleWorkspaces = YES;
    WindowShortcut8Key = None;
    GroupNextKey = None;
    Attraction = NO;
    SingleClickLaunch = NO;
    IconBack = (solid, "#ECF2F5");
    DisableBlinking = NO;
    AntialiasedText = NO;
    NewStyle = new;
    WorkspaceNameDisplayPosition = center;
    MenuTextFont = "Arial:slant=0:weight=80:width=100:pixelsize=12";
    ScreenSwitchKey = None;
    MenuTitleBack = (solid, "#0088CC");
    MouseWheelAction = SwitchWorkspaces;
    HMaximizeKey = None;
    CloseKey = "Mod1+F4";
    HighlightColor = "#333333";
    NextWorkspaceKey = "Control+Mod1+Right";
    GroupPrevKey = None;
    WrapMenus = YES;
    MinimizeAllKey = None;
    CClipTitleColor = gray20;
    WindowShortcut5Key = None;
    MenuStyle = flat;
    HideOthersKey = "Shift+Mod1+H";
    IconPath = (
    "/usr/share/WindowMaker/Icons",
    "/usr/share/WindowMaker/Pixmaps",
    "/usr/X11R6/include/X11/pixmaps",
    "/usr/share/icons",
    "/usr/local/share/pixmaps",
    "/usr/share/pixmaps",
    "/usr/share/icons/hicolor/48x48/apps",
    "/usr/share/lyx/images",
    "/usr/share/devede",
    "/home/couzelis/Library/Icons",
    "/usr/share/icons/gnome/48x48/places"
    DisableSound = YES;
    WindowShortcut6Key = None;
    PTitleBack = (solid, "#333333");
    UTitleColor = "#999999";
    BounceAppIconsWhenUrgent = YES;
    UTitleBack = (solid, "#333333");
    CirculateRaise = YES;
    PTitleColor = "#999999";
    ResizeDisplay = floating;
    The file format doesn't look very special. It's not particularly easy to modify by hand, but not particularly difficult either.
    I changed my settings by hand for a long time. More recently I realized that absolutely everything can be changed with the GUI preferences application that comes with Window Maker. Also, I discovered that it's a really easy application to use. So, I use that now.

  • Dmenu_themed - Applies the colors of your window manager to dmenu

    Hi everybody,
    i put together a little script named dmenu_themed which reads the window colors from the configuration of the i3 window manager and calls dmenu_run with those colors. Currently, only i3 is supported, but i'll eventually add support for gtk+ colors and other window managers.
    You can use it like dmenu_run and append all dmenu_run options as they will be handed over to dmenu_run.
    Head over to github and check it out:
    https://github.com/okraits/dmenu_themed
    Any feedback including questions, suggestions, feature requests, improvements etc is highly appreciated.
    Greetings,
    Oliver

    unexist wrote:Well, I must admit the overall idea really sounds like subtle and I don't understand some of the named differences, but I agree that the grid approach nice.
    Perhaps mentioning the idea of the 3x3 grid up front was too distracting, given folks' experience with subtle. The goomwwm grid is really just a guide for fast floating window movement. Tiling functionality is not strongly linked to it, nor limited by it. Don't think of this as a tiling WM with strict grids, but a stacking WM that makes it easy to tile.
    Some screenshots of tiling layouts done on the fly using a few keyboard commands:
    I'm still working on the controls, but the above was done pretty quickly. I'd guess easily as fast as most manual tiling WMs, once one knows the controls...
    unexist wrote:So basically all windows are stacked above each other, how do you plan multiscreen support without a virtual desktop concept? Just span the single desktop across all screens?
    From the EWMH perspective of a desktop, goomwwm tags are the same thing.  Use the desktop pager from any dock or panel to switch tags, just like desktops.  The only oddities are that, like any good tiling WM, goomwwm's windows can have multiple tags and raising a tag does not hide other tags.
    Multiscreen support for Xinerama and Xrandr is done and tested on what hardware I have access to (an Nvidia Twinview box, a regular Xinerama box, and a Laptop using xrandr to run an external monitor). Each physical screen has it's own grid -- that is, a fullscreen app would only fill one physical screen and splash windows center on the active monitor -- but nothing more strict than that. I suppose tags-as-desktop could be limited to each screen, but that is up to the user doing the tagging.

  • 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)

Maybe you are looking for

  • Problem in deleting a request from ODS

    Hi, i am trying to delete a request (not activated) from ODS, when i checked in SM37 for the status of the job it shows as Cancelled, but when i see for the request in ODS, the requested is deleted, could anyone please let me know why job in SM37 is

  • Retaining the Color of the row when it is refreshed in Javascript

    Hi, I have a checkbox when it is checked it will highlight the row with the color. When it is unchecked the color will go off. This is happening fine. But the problem i have is that when i refresh the page or goes to some other page and come back the

  • Create folder and copy files problem

    Hello all indesign script Members where I work we use a permanent folder structure for an example a jobnumber called "123123" I have wrote a little interface called interface.jsx, this file is saved and located in 123123/scripts/interface I want my i

  • What does the setting "auto increment column templates"

    I have noticed that there is now a setting "auto increment column templates" but I cannot find out what this setting does. There are no sequences generated nor triggers. Version 3.0. Thanks, Joep

  • Windows 2008 AD Sites and Services: Multiple Connection links between same sites

    Hello, Our AD Sites  & Services is showing Multiple Connection links between the same sites. How is this possible and can i delete extra ones?