DWM 6.0 statuscolors and xft

Does anyone have a patch for statuscolors and xft (so that I could use other fonts in the bar) patch for dwm 6.0.*?
I can apply any of those separately, but both of them .. I've spent a couple of hours and nothing (patching fails).

https://bitbucket.org/jasonwryan/dwm-pa … tuscolours

Similar Messages

[SOLVED] Getting freezes after using dwm for some time and exiting it

Hello, I have an Asus Ux51, with a fresh (less than a month) arch installation. If I recall correctly I had a couple of freezes in other occasions but I don't remember much about those so I rather focus on the only freeze I can more or less reproduce and I've been having lately. After using dwm for some time with a couple of programs opened (rTorrent, browser, and some terminals for instance), if I close dwm or just press the power button to shut down, it starts closing everything and either stays with a black screen, or hangs while X prints the log information. It's not always though, for example, if I just boot it, open dwm and close it without giving it much use it usually closes fine.
Tried googling a bit to see the usual ways to troubleshoot this but didn't get really far.
This is my /var/log/Xorg.0.log
[ 7.573]
X.Org X Server 1.14.2
Release Date: 2013-06-25
[ 7.573] X Protocol Version 11, Revision 0
[ 7.573] Build Operating System: Linux 3.9.7-1-ARCH x86_64
[ 7.574] Current Operating System: Linux arch 3.10.3-1-ARCH #1 SMP PREEMPT Fri Jul 26 11:26:59 CEST 2013 x86_64
[ 7.574] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=74e92d67-41b6-4911-8ceb-009ae8c9cdab ro quiet add_efi_memmap i915.i915_enable_rc6=1 pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 "acpi_osi=!Windows 2012"
[ 7.574] Build Date: 01 July 2013 10:48:42AM
[ 7.574]
[ 7.574] Current version of pixman: 0.30.0
[ 7.574] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 7.574] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 7.574] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Aug 10 19:08:34 2013
[ 7.574] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 7.575] (==) No Layout section. Using the first Screen section.
[ 7.575] (==) No screen section available. Using defaults.
[ 7.575] (**) |-->Screen "Default Screen Section" (0)
[ 7.575] (**) | |-->Monitor "<default monitor>"
[ 7.575] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 7.575] (==) Automatically adding devices
[ 7.575] (==) Automatically enabling devices
[ 7.575] (==) Automatically adding GPU devices
[ 7.578] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 7.578] Entry deleted from font path.
[ 7.578] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 7.578] Entry deleted from font path.
[ 7.578] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 7.578] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 7.578] Entry deleted from font path.
[ 7.578] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 7.578] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/
[ 7.578] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 7.578] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 7.578] (II) Loader magic: 0x7fdc20
[ 7.578] (II) Module ABI versions:
[ 7.578] X.Org ANSI C Emulation: 0.4
[ 7.578] X.Org Video Driver: 14.1
[ 7.578] X.Org XInput driver : 19.1
[ 7.578] X.Org Server Extension : 7.0
[ 7.578] (II) xfree86: Adding drm device (/dev/dri/card1)
[ 7.579] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 7.580] (--) PCI:*(0:0:2:0) 8086:0166:1043:15a7 rev 9, Mem @ 0xf7400000/4194304, 0xd0000000/268435456, I/O @ 0x0000f000/64
[ 7.580] (--) PCI: (0:1:0:0) 10de:0fd1:1043:15a7 rev 161, Mem @ 0xf6000000/16777216, 0xe0000000/268435456, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[ 7.580] Initializing built-in extension Generic Event Extension
[ 7.580] Initializing built-in extension SHAPE
[ 7.580] Initializing built-in extension MIT-SHM
[ 7.580] Initializing built-in extension XInputExtension
[ 7.580] Initializing built-in extension XTEST
[ 7.580] Initializing built-in extension BIG-REQUESTS
[ 7.580] Initializing built-in extension SYNC
[ 7.580] Initializing built-in extension XKEYBOARD
[ 7.580] Initializing built-in extension XC-MISC
[ 7.580] Initializing built-in extension SECURITY
[ 7.580] Initializing built-in extension XINERAMA
[ 7.580] Initializing built-in extension XFIXES
[ 7.580] Initializing built-in extension RENDER
[ 7.581] Initializing built-in extension RANDR
[ 7.581] Initializing built-in extension COMPOSITE
[ 7.581] Initializing built-in extension DAMAGE
[ 7.581] Initializing built-in extension MIT-SCREEN-SAVER
[ 7.581] Initializing built-in extension DOUBLE-BUFFER
[ 7.581] Initializing built-in extension RECORD
[ 7.581] Initializing built-in extension DPMS
[ 7.581] Initializing built-in extension X-Resource
[ 7.581] Initializing built-in extension XVideo
[ 7.581] Initializing built-in extension XVideo-MotionCompensation
[ 7.582] Initializing built-in extension XFree86-VidModeExtension
[ 7.583] Initializing built-in extension XFree86-DGA
[ 7.583] Initializing built-in extension XFree86-DRI
[ 7.584] Initializing built-in extension DRI2
[ 7.584] (II) LoadModule: "glx"
[ 7.585] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 7.586] (II) Module glx: vendor="X.Org Foundation"
[ 7.586] compiled for 1.14.2, module version = 1.0.0
[ 7.586] ABI class: X.Org Server Extension, version 7.0
[ 7.586] (==) AIGLX enabled
[ 7.587] Loading extension GLX
[ 7.587] (==) Matched intel as autoconfigured driver 0
[ 7.587] (==) Matched nouveau as autoconfigured driver 1
[ 7.587] (==) Matched nvidia as autoconfigured driver 2
[ 7.587] (==) Matched nv as autoconfigured driver 3
[ 7.587] (==) Matched intel as autoconfigured driver 4
[ 7.587] (==) Matched vesa as autoconfigured driver 5
[ 7.587] (==) Matched modesetting as autoconfigured driver 6
[ 7.587] (==) Matched fbdev as autoconfigured driver 7
[ 7.587] (==) Assigned the driver to the xf86ConfigLayout
[ 7.587] (II) LoadModule: "intel"
[ 7.588] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 7.592] (II) Module intel: vendor="X.Org Foundation"
[ 7.592] compiled for 1.14.2, module version = 2.21.12
[ 7.592] Module class: X.Org Video Driver
[ 7.592] ABI class: X.Org Video Driver, version 14.1
[ 7.592] (II) LoadModule: "nouveau"
[ 7.592] (WW) Warning, couldn't open module nouveau
[ 7.592] (II) UnloadModule: "nouveau"
[ 7.592] (II) Unloading nouveau
[ 7.592] (EE) Failed to load module "nouveau" (module does not exist, 0)
[ 7.592] (II) LoadModule: "nvidia"
[ 7.592] (WW) Warning, couldn't open module nvidia
[ 7.592] (II) UnloadModule: "nvidia"
[ 7.592] (II) Unloading nvidia
[ 7.592] (EE) Failed to load module "nvidia" (module does not exist, 0)
[ 7.592] (II) LoadModule: "nv"
[ 7.592] (WW) Warning, couldn't open module nv
[ 7.592] (II) UnloadModule: "nv"
[ 7.592] (II) Unloading nv
[ 7.592] (EE) Failed to load module "nv" (module does not exist, 0)
[ 7.592] (II) LoadModule: "vesa"
[ 7.593] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 7.593] (II) Module vesa: vendor="X.Org Foundation"
[ 7.593] compiled for 1.14.0, module version = 2.3.2
[ 7.593] Module class: X.Org Video Driver
[ 7.593] ABI class: X.Org Video Driver, version 14.1
[ 7.593] (II) LoadModule: "modesetting"
[ 7.593] (WW) Warning, couldn't open module modesetting
[ 7.593] (II) UnloadModule: "modesetting"
[ 7.593] (II) Unloading modesetting
[ 7.593] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 7.593] (II) LoadModule: "fbdev"
[ 7.593] (WW) Warning, couldn't open module fbdev
[ 7.593] (II) UnloadModule: "fbdev"
[ 7.593] (II) Unloading fbdev
[ 7.593] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 7.593] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,
E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),
Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),
Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),
Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),
Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server,
Ivybridge Server (GT2), HD Graphics, HD Graphics 4600,
Haswell Desktop (GT3), HD Graphics, HD Graphics 4600,
Haswell Mobile (GT3), HD Graphics, HD Graphics P4600/P4700,
Haswell Server (GT3), Haswell (GT1), Haswell (GT2), Haswell (GT3),
HD Graphics, Haswell (GT2), Haswell (GT3), Haswell SDV Desktop (GT1),
Haswell SDV Desktop (GT2), Haswell SDV Desktop (GT3),
Haswell SDV Mobile (GT1), Haswell SDV Mobile (GT2),
Haswell SDV Mobile (GT3), Haswell SDV Server (GT1),
Haswell SDV Server (GT2), Haswell SDV Server (GT3),
Haswell SDV (GT1), Haswell SDV (GT2), Haswell SDV (GT3),
Haswell SDV (GT1), Haswell SDV (GT2), Haswell SDV (GT3),
Haswell ULT Desktop (GT1), Haswell ULT Desktop (GT2),
Iris(TM) Graphics 5100, HD Graphics, HD Graphics 4400,
HD Graphics 5000, Haswell ULT Server (GT1), Haswell ULT Server (GT2),
Iris(TM) Graphics 5100, Haswell ULT (GT1), Haswell ULT (GT2),
Iris(TM) Graphics 5100, HD Graphics, HD Graphics 4200,
Iris(TM) Graphics 5100, Haswell CRW Desktop (GT1), HD Graphics 4600,
Iris(TM) Pro Graphics 5200, Haswell CRW Mobile (GT1),
HD Graphics 4600, Iris(TM) Pro Graphics 5200,
Haswell CRW Server (GT1), Haswell CRW Server (GT2),
Iris(TM) Pro Graphics 5200, Haswell CRW (GT1), Haswell CRW (GT2),
Iris(TM) Pro Graphics 5200, Haswell CRW (GT1), Haswell CRW (GT2),
Iris(TM) Pro Graphics 5200, ValleyView PO board
[ 7.594] (II) VESA: driver for VESA chipsets: vesa
[ 7.594] (++) using VT number 1
[ 7.594] (WW) Falling back to old probe method for vesa
[ 7.594] (II) intel(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 7.594] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[ 7.594] (==) intel(0): RGB weight 888
[ 7.594] (==) intel(0): Default visual is TrueColor
[ 7.594] (--) intel(0): Integrated Graphics Chipset: Intel(R) Ivybridge Mobile (GT2)
[ 7.594] (**) intel(0): Relaxed fencing enabled
[ 7.594] (**) intel(0): Wait on SwapBuffers? enabled
[ 7.594] (**) intel(0): Triple buffering? enabled
[ 7.594] (**) intel(0): Framebuffer tiled
[ 7.594] (**) intel(0): Pixmaps tiled
[ 7.594] (**) intel(0): 3D buffers tiled
[ 7.594] (**) intel(0): SwapBuffers wait enabled
[ 7.594] (==) intel(0): video overlay key set to 0x101fe
[ 7.594] (II) intel(0): Output eDP1 has no monitor section
[ 7.595] (--) intel(0): found backlight control interface /sys/class/backlight/acpi_video1
[ 7.596] (II) intel(0): Output VGA1 has no monitor section
[ 7.596] (II) intel(0): EDID for output eDP1
[ 7.596] (II) intel(0): Manufacturer: LGD Model: 323 Serial#: 0
[ 7.596] (II) intel(0): Year: 2012 Week: 0
[ 7.596] (II) intel(0): EDID Version: 1.4
[ 7.596] (II) intel(0): Digital Display Input
[ 7.596] (II) intel(0): 6 bits per channel
[ 7.596] (II) intel(0): Digital interface is DisplayPort
[ 7.596] (II) intel(0): Max Image Size [cm]: horiz.: 35 vert.: 19
[ 7.596] (II) intel(0): Gamma: 2.20
[ 7.596] (II) intel(0): No DPMS capabilities specified
[ 7.596] (II) intel(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
[ 7.596] (II) intel(0): First detailed timing is preferred mode
[ 7.596] (II) intel(0): Preferred mode is native pixel format and refresh rate
[ 7.596] (II) intel(0): redX: 0.629 redY: 0.350 greenX: 0.349 greenY: 0.614
[ 7.596] (II) intel(0): blueX: 0.154 blueY: 0.112 whiteX: 0.313 whiteY: 0.329
[ 7.596] (II) intel(0): Manufacturer's mask: 0
[ 7.596] (II) intel(0): Supported detailed timing:
[ 7.596] (II) intel(0): clock: 138.0 MHz Image Size: 345 x 194 mm
[ 7.596] (II) intel(0): h_active: 1920 h_sync: 1952 h_sync_end 1988 h_blank_end 2088 h_border: 0
[ 7.596] (II) intel(0): v_active: 1080 v_sync: 1085 v_sync_end 1090 v_blanking: 1102 v_border: 0
[ 7.596] (II) intel(0): LG Display
[ 7.596] (II) intel(0): LP156WF4-SPB1
[ 7.596] (II) intel(0): EDID (in hex):
[ 7.596] (II) intel(0): 00ffffffffffff0030e4230300000000
[ 7.596] (II) intel(0): 00160104952313780a25b5a159599d27
[ 7.596] (II) intel(0): 1c505400000001010101010101010101
[ 7.596] (II) intel(0): 010101010101e83580a8703816402024
[ 7.596] (II) intel(0): 550059c2100000180000000000000000
[ 7.596] (II) intel(0): 00000000000000000000000000fe004c
[ 7.596] (II) intel(0): 4720446973706c61790a2020000000fe
[ 7.596] (II) intel(0): 004c503135365746342d535042310069
[ 7.596] (II) intel(0): Not using default mode "320x240" (doublescan mode not supported)
[ 7.597] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
[ 7.597] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
[ 7.597] (II) intel(0): Not using default mode "512x384" (doublescan mode not supported)
[ 7.597] (II) intel(0): Not using default mode "640x480" (doublescan mode not supported)
[ 7.597] (II) intel(0): Not using default mode "640x512" (doublescan mode not supported)
[ 7.597] (II) intel(0): Not using default mode "800x600" (doublescan mode not supported)
[ 7.597] (II) intel(0): Not using default mode "896x672" (doublescan mode not supported)
[ 7.597] (II) intel(0): Not using default mode "928x696" (doublescan mode not supported)
[ 7.597] (II) intel(0): Not using default mode "960x720" (doublescan mode not supported)
[ 7.597] (II) intel(0): Not using default mode "700x525" (doublescan mode not supported)
[ 7.597] (II) intel(0): Not using default mode "1024x768" (doublescan mode not supported)
[ 7.597] (II) intel(0): Printing probed modes for output eDP1
[ 7.597] (II) intel(0): Modeline "1920x1080"x60.0 138.00 1920 1952 1988 2088 1080 1085 1090 1102 -hsync -vsync (66.1 kHz eP)
[ 7.597] (II) intel(0): Modeline "1400x1050"x60.0 122.00 1400 1488 1640 1880 1050 1052 1064 1082 +hsync +vsync (64.9 kHz d)
[ 7.597] (II) intel(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz d)
[ 7.597] (II) intel(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz d)
[ 7.597] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz d)
[ 7.597] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz d)
[ 7.597] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz d)
[ 7.597] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz d)
[ 7.598] (II) intel(0): EDID for output VGA1
[ 7.598] (II) intel(0): Output eDP1 connected
[ 7.598] (II) intel(0): Output VGA1 disconnected
[ 7.598] (II) intel(0): Using exact sizes for initial modes
[ 7.598] (II) intel(0): Output eDP1 using initial mode 1920x1080
[ 7.598] (II) intel(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 7.598] (II) intel(0): Kernel page flipping support detected, enabling
[ 7.598] (==) intel(0): DPI set to (96, 96)
[ 7.598] (II) Loading sub module "fb"
[ 7.598] (II) LoadModule: "fb"
[ 7.598] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 7.599] (II) Module fb: vendor="X.Org Foundation"
[ 7.599] compiled for 1.14.2, module version = 1.0.0
[ 7.599] ABI class: X.Org ANSI C Emulation, version 0.4
[ 7.599] (II) Loading sub module "dri2"
[ 7.599] (II) LoadModule: "dri2"
[ 7.599] (II) Module "dri2" already built-in
[ 7.599] (II) UnloadModule: "vesa"
[ 7.599] (II) Unloading vesa
[ 7.599] (==) Depth 24 pixmap format is 32 bpp
[ 7.599] (II) intel(0): [DRI2] Setup complete
[ 7.599] (II) intel(0): [DRI2] DRI driver: i965
[ 7.599] (II) intel(0): Allocated new frame buffer 1920x1080 stride 7680, tiled
[ 7.599] (II) UXA(0): Driver registered support for the following operations:
[ 7.599] (II) solid
[ 7.599] (II) copy
[ 7.599] (II) composite (RENDER acceleration)
[ 7.599] (II) put_image
[ 7.599] (II) get_image
[ 7.599] (==) intel(0): Backing store disabled
[ 7.599] (==) intel(0): Silken mouse enabled
[ 7.600] (II) intel(0): Initializing HW Cursor
[ 7.600] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 7.600] (==) intel(0): DPMS enabled
[ 7.600] (==) intel(0): Intel XvMC decoder enabled
[ 7.600] (II) intel(0): Set up textured video
[ 7.600] (II) intel(0): [XvMC] xvmc_vld driver initialized.
[ 7.600] (II) intel(0): direct rendering: DRI2 Enabled
[ 7.600] (==) intel(0): hotplug detection: "enabled"
[ 7.613] (--) RandR disabled
[ 7.634] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 7.634] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 7.634] (II) AIGLX: enabled GLX_ARB_create_context
[ 7.634] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 7.634] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
[ 7.634] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[ 7.634] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 7.634] (II) AIGLX: Loaded and initialized i965
[ 7.634] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 7.634] (II) intel(0): Setting screen physical size to 508 x 285
[ 7.669] (II) config/udev: Adding input device Video Bus (/dev/input/event9)
[ 7.669] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 7.669] (II) LoadModule: "evdev"
[ 7.669] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 7.670] (II) Module evdev: vendor="X.Org Foundation"
[ 7.670] compiled for 1.14.2, module version = 2.8.1
[ 7.670] Module class: X.Org XInput Driver
[ 7.670] ABI class: X.Org XInput driver, version 19.1
[ 7.670] (II) Using input driver 'evdev' for 'Video Bus'
[ 7.670] (**) Video Bus: always reports core events
[ 7.670] (**) evdev: Video Bus: Device: "/dev/input/event9"
[ 7.670] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 7.670] (--) evdev: Video Bus: Found keys
[ 7.670] (II) evdev: Video Bus: Configuring as keyboard
[ 7.670] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:01/input/input10/event9"
[ 7.670] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 6)
[ 7.670] (**) Option "xkb_rules" "evdev"
[ 7.670] (**) Option "xkb_model" "pc104"
[ 7.670] (**) Option "xkb_layout" "us"
[ 7.684] (II) config/udev: Adding input device Video Bus (/dev/input/event8)
[ 7.684] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 7.684] (II) Using input driver 'evdev' for 'Video Bus'
[ 7.684] (**) Video Bus: always reports core events
[ 7.684] (**) evdev: Video Bus: Device: "/dev/input/event8"
[ 7.684] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 7.684] (--) evdev: Video Bus: Found keys
[ 7.684] (II) evdev: Video Bus: Configuring as keyboard
[ 7.684] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:03/LNXVIDEO:00/input/input9/event8"
[ 7.684] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[ 7.684] (**) Option "xkb_rules" "evdev"
[ 7.684] (**) Option "xkb_model" "pc104"
[ 7.684] (**) Option "xkb_layout" "us"
[ 7.684] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[ 7.685] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 7.685] (II) Using input driver 'evdev' for 'Power Button'
[ 7.685] (**) Power Button: always reports core events
[ 7.685] (**) evdev: Power Button: Device: "/dev/input/event2"
[ 7.685] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 7.685] (--) evdev: Power Button: Found keys
[ 7.685] (II) evdev: Power Button: Configuring as keyboard
[ 7.685] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input2/event2"
[ 7.685] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 8)
[ 7.685] (**) Option "xkb_rules" "evdev"
[ 7.685] (**) Option "xkb_model" "pc104"
[ 7.685] (**) Option "xkb_layout" "us"
[ 7.685] (II) config/udev: Adding input device Lid Switch (/dev/input/event1)
[ 7.685] (II) No input driver specified, ignoring this device.
[ 7.685] (II) This device may have been added with another device file.
[ 7.685] (II) config/udev: Adding input device Sleep Button (/dev/input/event3)
[ 7.685] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[ 7.685] (II) Using input driver 'evdev' for 'Sleep Button'
[ 7.685] (**) Sleep Button: always reports core events
[ 7.685] (**) evdev: Sleep Button: Device: "/dev/input/event3"
[ 7.685] (--) evdev: Sleep Button: Vendor 0 Product 0x3
[ 7.685] (--) evdev: Sleep Button: Found keys
[ 7.685] (II) evdev: Sleep Button: Configuring as keyboard
[ 7.685] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input3/event3"
[ 7.685] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 9)
[ 7.685] (**) Option "xkb_rules" "evdev"
[ 7.685] (**) Option "xkb_model" "pc104"
[ 7.685] (**) Option "xkb_layout" "us"
[ 7.685] (II) config/udev: Adding drm device (/dev/dri/card1)
[ 7.685] (II) config/udev: Adding drm device (/dev/dri/card0)
[ 7.686] (II) config/udev: Adding input device USB2.0 HD UVC WebCam (/dev/input/event6)
[ 7.686] (**) USB2.0 HD UVC WebCam: Applying InputClass "evdev keyboard catchall"
[ 7.686] (II) Using input driver 'evdev' for 'USB2.0 HD UVC WebCam'
[ 7.686] (**) USB2.0 HD UVC WebCam: always reports core events
[ 7.686] (**) evdev: USB2.0 HD UVC WebCam: Device: "/dev/input/event6"
[ 7.686] (--) evdev: USB2.0 HD UVC WebCam: Vendor 0x4f2 Product 0xb36e
[ 7.686] (--) evdev: USB2.0 HD UVC WebCam: Found keys
[ 7.686] (II) evdev: USB2.0 HD UVC WebCam: Configuring as keyboard
[ 7.686] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.3/3-1.3:1.0/input/input6/event6"
[ 7.686] (II) XINPUT: Adding extended input device "USB2.0 HD UVC WebCam" (type: KEYBOARD, id 10)
[ 7.686] (**) Option "xkb_rules" "evdev"
[ 7.686] (**) Option "xkb_model" "pc104"
[ 7.686] (**) Option "xkb_layout" "us"
[ 7.686] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event5)
[ 7.686] (II) No input driver specified, ignoring this device.
[ 7.686] (II) This device may have been added with another device file.
[ 7.686] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 7.686] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 7.686] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 7.686] (**) AT Translated Set 2 keyboard: always reports core events
[ 7.686] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 7.686] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[ 7.686] (--) evdev: AT Translated Set 2 keyboard: Found keys
[ 7.686] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[ 7.686] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 7.686] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 11)
[ 7.686] (**) Option "xkb_rules" "evdev"
[ 7.686] (**) Option "xkb_model" "pc104"
[ 7.686] (**) Option "xkb_layout" "us"
[ 7.686] (II) config/udev: Adding input device ETPS/2 Elantech Touchpad (/dev/input/event7)
[ 7.686] (**) ETPS/2 Elantech Touchpad: Applying InputClass "evdev touchpad catchall"
[ 7.686] (**) ETPS/2 Elantech Touchpad: Applying InputClass "touchpad catchall"
[ 7.687] (**) ETPS/2 Elantech Touchpad: Applying InputClass "Default clickpad buttons"
[ 7.687] (II) LoadModule: "synaptics"
[ 7.687] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 7.687] (II) Module synaptics: vendor="X.Org Foundation"
[ 7.687] compiled for 1.14.1, module version = 1.7.1
[ 7.687] Module class: X.Org XInput Driver
[ 7.687] ABI class: X.Org XInput driver, version 19.1
[ 7.687] (II) Using input driver 'synaptics' for 'ETPS/2 Elantech Touchpad'
[ 7.687] (**) ETPS/2 Elantech Touchpad: always reports core events
[ 7.687] (**) Option "Device" "/dev/input/event7"
[ 7.810] (II) synaptics: ETPS/2 Elantech Touchpad: found clickpad property
[ 7.810] (--) synaptics: ETPS/2 Elantech Touchpad: x-axis range 0 - 3260 (res 32)
[ 7.810] (--) synaptics: ETPS/2 Elantech Touchpad: y-axis range 0 - 2119 (res 32)
[ 7.810] (--) synaptics: ETPS/2 Elantech Touchpad: pressure range 0 - 255
[ 7.810] (--) synaptics: ETPS/2 Elantech Touchpad: finger width range 0 - 15
[ 7.810] (--) synaptics: ETPS/2 Elantech Touchpad: buttons: left double triple
[ 7.810] (--) synaptics: ETPS/2 Elantech Touchpad: Vendor 0x2 Product 0xe
[ 7.810] (**) Option "TapButton1" "1"
[ 7.810] (**) Option "TapButton2" "2"
[ 7.810] (**) Option "TapButton3" "3"
[ 7.810] (**) Option "SoftButtonAreas" "50% 0 82% 0 0 0 0 0"
[ 7.810] (--) synaptics: ETPS/2 Elantech Touchpad: touchpad found
[ 7.810] (**) ETPS/2 Elantech Touchpad: always reports core events
[ 7.853] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio4/input/input8/event7"
[ 7.853] (II) XINPUT: Adding extended input device "ETPS/2 Elantech Touchpad" (type: TOUCHPAD, id 12)
[ 7.853] (**) synaptics: ETPS/2 Elantech Touchpad: (accel) MinSpeed is now constant deceleration 2.5
[ 7.853] (**) synaptics: ETPS/2 Elantech Touchpad: (accel) MaxSpeed is now 1.75
[ 7.853] (**) synaptics: ETPS/2 Elantech Touchpad: (accel) AccelFactor is now 0.051
[ 7.853] (**) ETPS/2 Elantech Touchpad: (accel) keeping acceleration scheme 1
[ 7.853] (**) ETPS/2 Elantech Touchpad: (accel) acceleration profile 1
[ 7.853] (**) ETPS/2 Elantech Touchpad: (accel) acceleration factor: 2.000
[ 7.853] (**) ETPS/2 Elantech Touchpad: (accel) acceleration threshold: 4
[ 7.853] (--) synaptics: ETPS/2 Elantech Touchpad: touchpad found
[ 7.853] (II) config/udev: Adding input device ETPS/2 Elantech Touchpad (/dev/input/mouse0)
[ 7.853] (**) ETPS/2 Elantech Touchpad: Ignoring device from InputClass "touchpad ignore duplicates"
[ 7.853] (II) config/udev: Adding input device PC Speaker (/dev/input/event4)
[ 7.853] (II) No input driver specified, ignoring this device.
[ 7.853] (II) This device may have been added with another device file.
Found this recent thread in the forums, I'll give REISUB a try late, but the times it freezed I remember trying to blindly reboot it, or switching off virtual console and couldn't.
In case it's of any use, this is my # uname -a
Linux arch 3.10.3-1-ARCH #1 SMP PREEMPT Fri Jul 26 11:26:59 CEST 2013 x86_64 GNU/Linux
Could it have something to do with the nvidia optimus setup that this laptop has? When installing arch I found out that there was no support yet for it so I'm just using the intel drivers (following what the arch wiki said).
Any ideas or advice to point me in the right direction would be very much appreciated.
Thanks in advance.
Last edited by contiver (2013-08-16 20:25:34)

I don't start st in my .xinitrc. I launch it from dmenu and usually everything is fine. If I launch it from dwm's internal command using Alt-Shf-Return, X freezes 100% of the time. A workaround was suggested by st's main developer to call st like this:
static const char *termcmd[] = { "/bin/sh", "-c", "st", NULL };
but it didn't work for me.
Very rarely X will freeze anyway. I haven't been able to pin it down. When X fails, my journal returns this:
BUG: unable to handle kernel paging request at ffffc90014ce8000
IP: [<ffffffff812bfe7f>] bitfill_aligned+0x8f/0x140
PGD 7c00b067 PUD 7c018067 PMD 7b3eb067 PTE 0
Oops: 0002 [#1] PREEMPT SMP
Modules linked in: nls_cp437 vfat fat snd_usb_audio snd_usbmidi_lib snd_hwdep snd_rawmidi snd_seq_device snd_pcm snd_page_alloc snd_timer
CPU: 1 PID: 7520 Comm: X Not tainted 3.10.5-1-ck #1
Hardware name: /D410PT, BIOS MOPNV10N.86A.0155.2009.1106.0430 11/06/2009
task: ffff88007aa786b0 ti: ffff8800797ee000 task.ti: ffff8800797ee000
RIP: 0010:[<ffffffff812bfe7f>] [<ffffffff812bfe7f>] bitfill_aligned+0x8f/0x140
RSP: 0018:ffff8800797efaa8 EFLAGS: 00010212
RAX: 0000000003ffff5c RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000003ffff5c RSI: ffffc90014901520 RDI: ffffc90014ce7fe0
RBP: ffff8800797efab8 R08: 00000000ffffd700 R09: 0000000003f83204
R10: 0000000000000000 R11: ffffc90014ce7fd8 R12: ffffffffffffffff
R13: ffffc90014901520 R14: ffffffff812bfdf0 R15: 0000000000000320
FS: 00007fb350033880(0000) GS:ffff88007ea80000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: ffffc90014ce8000 CR3: 000000007b104000 CR4: 00000000000007e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Stack:
0000000000000000 ffff88007a4d3000 ffff8800797efb28 ffffffff812bfbb9
ffffffff00000000 ffff88007c00c000 0000000000000000 ffffffff8186f240
0000000000000000 ffffffff00000006 ffffd700797efb58 ffff88007a4d3000
Call Trace:
[<ffffffff812bfbb9>] cfb_fillrect+0x1c9/0x400
[<ffffffff812ba2e5>] bit_clear_margins+0x165/0x190
[<ffffffff812b3633>] fbcon_clear_margins+0x63/0x90
[<ffffffff812b7a9f>] fbcon_switch+0x3df/0x570
[<ffffffff813200bd>] redraw_screen+0x17d/0x240
[<ffffffff812b6eeb>] fbcon_blank+0x20b/0x2d0
[<ffffffff81320767>] do_unblank_screen+0xa7/0x1b0
[<ffffffff813175d1>] vt_ioctl+0x10d1/0x1170
[<ffffffff8130b407>] tty_ioctl+0x277/0xb90
[<ffffffff8118fb21>] ? mntput_no_expire+0x41/0x150
[<ffffffff81183a3e>] do_vfs_ioctl+0x2de/0x4c0
[<ffffffff8117328e>] ? ____fput+0xe/0x10
[<ffffffff8107766c>] ? task_work_run+0x9c/0xe0
[<ffffffff81183ca3>] SyS_ioctl+0x83/0xa0
[<ffffffff814bab9d>] system_call_fastpath+0x1a/0x1f
Code: 08 45 01 d8 31 d2 44 89 c0 41 f7 f1 83 f8 07 89 c2 76 4f 44 8d 08 48 8d 3e 0f 1f 00 4c 89 17 4c 89 57 08 4c 89 57 10 4c 89 57 18 <4
RIP [<ffffffff812bfe7f>] bitfill_aligned+0x8f/0x140
RSP <ffff8800797efaa8>
CR2: ffffc90014ce8000
---[ end trace aff6cb5ad5097aef ]---

Conky and xft fonts

WM: Openbox
I have these in my conkyrc:
override_utf8_locale yes
use_xft yes
xftfont Terminus:size=8
xftalpha 0.8
But it doesn't display the desired fonts, if launched from a terminal error is:
Conky: can't load Xft font 'Pie charts for maps:size=8'
Conky: can't load Xft font 'Radio Space:size=8'
Conky: can't load Xft font 'Pie charts for maps:size=8'
Conky: can't load Xft font 'Radio Space:size=8'

Hi Shy
You have to install dmenu-xft
Look here: http://aur.archlinux.org/packages.php?ID=28745
There is a problem with the packagebuild on this page though.
It should be:
pkgname=dmenu-xft
pkgver=4.0
pkgrel=1
pkgdesc="Dynamic X menu - with xft support"
arch=('i686' 'x86_64')
url="http://code.suckless.org/"
license=('MIT')
depends=('libx11' 'libxinerama' 'libxft')
conflicts=('dmenu')
provides=('dmenu')
source=(http://dl.suckless.org/tools/dmenu-4.0.tar.gz
http://z.ip.fi/~henkka/dmenu-xft/dmenu-4.0-xft.diff)
md5sums=('66e761a653930cc8a21614ba9fedf903'
'1f3ecd819a39dea88a3dde9b5271bec6')
build() {
cd $srcdir/dmenu-$pkgver
patch -p1 < ../dmenu-4.0-xft.diff || return 1 make || return 1 make DESTDIR=$startdir/pkg PREFIX=/usr install || return 1 # LICENSE mkdir -p $startdir/pkg/usr/share/licenses/$pkgname || return 1 cp LICENSE $startdir/pkg/usr/share/licenses/$pkgname/ || return 1
Save this as PKGBUILD textfile and run makepkg where you saved PKGBUILD.
But first uninstall the dmenu version you have with
sudo pacman -Rd dmenu

Dzen2 and xft

I edited the PKGBUILD of dzen2-svn from AUR so instead of checking out trunk, it'd check svn/branches/dzen-xft. Everything went fine during installation, but now when I run dzen2, it shows no text.
When I using xmonad, the background of the selected workspace changes, so I know it's working. Or at leat half-working.
Any idea?

andre.ramaciotti wrote:
It's working here!
edit: Only a question, though. How can I use bold fonts? "dzen2 -fn 'DejaVu Sans Bold:size=8' " didn't work.
Does that font really exist on your system?
What works for me is:
echo "Normal ^fn(Vera:bold) bold ^fn(Vera:italic) italic ^fn(Vera:size=8) small ^fn() normal" | dzen2 -fn Vera -p
Respectively for the '-fn' parameter.
Bye, Rob.
Last edited by gotmor (2009-02-12 17:27:29)

[Solved] Using Artwiz lime with DWM

Hi all,
I have dwm configured with statuscolors and pertag, but changing the font to lime doesn't work. It keeps falling back on the "fixed" font.
For the font line in config.h, I've tried:
static const char font[] = "-artwiz-lime-medium-r-normal--10-110-75-75-m-50-ISO8859-1";
and
static const char font[] = "-*-lime-*-*-*--*-*-*-*-*-*-*-*";
I've redirected stderr from dwm, and it always outputs something to this effect:
dwm: missing fontset: ISO10646-1
dwm: missing fontset: JISX0201.1976-0
dwm: missing fontset: GB2312.1980-0
dwm: missing fontset: KSC5601.1987-0
dwm: missing fontset: JISX0208.1983-0
dwm: missing fontset: ISO8859-15
dwm: missing fontset: ISO8859-14
dwm: missing fontset: ISO8859-13
dwm: missing fontset: ISO8859-9
dwm: missing fontset: ISO8859-7
dwm: missing fontset: KOI8-R
dwm: missing fontset: ISO8859-5
dwm: missing fontset: ISO8859-4
dwm: missing fontset: ISO8859-3
dwm: missing fontset: ISO8859-2
dwm: missing fontset: ISO8859-1
dwm: missing fontset: ISO8859-1
I installed the font by copying it (the pcf) into /usr/share/fonts/artwiz and running fc-cache -vf. I also added to my .xinitrc the following lines:
xset +fp /usr/share/fonts/artwiz
xset fp rehash
Nothing seems to be working, as it keeps falling back on "fixed".
Could anyone help me?
Thanks
-scen
Last edited by uberness132 (2011-12-06 06:04:37)

uberness132 wrote:
static const char font[] = "-artwiz-lime-medium-r-normal--10-110-75-75-m-50-ISO8859-1";
static const char font[] = "-*-lime-*-*-*--*-*-*-*-*-*-*-*";
The first of these lines is wrong (too may fields and there should be an asterisk in any empty fields).
I don't know about the second, but are you sure that is the correct font name.
The easiest way to generate a correct string is to use xfontsel.
Last edited by jasonwryan (2011-12-06 04:51:29)

DWM "statuscolors" Patch

Hey there,
Newbie to DWM and today I've decided to delve into patches. I've been looking at the "statuscolors" patch (http://dwm.suckless.org/patches/statuscolors) for a while now, but I can't seem to get it installed properly. I've downloaded the "dwm-5.9-statuscolors.diff" to my dwm directory (~/dwm), and am running
$ patch-pl <~/dwm/dwm-5.9-statuscolors.diff
That results in the following:
patch: **** strip count 1 is not a number
I'm pretty a pretty big newb, and what I'm thinking is that the patch version number and dwm's version number must be the same. So what I'm wondering is if there's an updated version out there somewhere, or if I could possibly mod it for the current version.
Thanks.

ccc1 wrote:
Farehe wrote:
$ patch-pl <~/dwm/dwm-5.9-statuscolors.diff
That results in the following:
patch: **** strip count 1 is not a number
The problem: you wrote "-pl" instead of "-p1"
ccc1
Haha, I feel dumb. Thanks.
Hmm, now I'm getting this when using "patch -p1 <~/dwm/dwm-5.9-statuscolors.diff"
can't find file to patch at input line 4
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
|diff -up dwm-5.9/config.def.h dwm-5.9-colors/config.def.h
|--- dwm-5.9/config.def.h 2011-07-10 16:24:25.000000000 -0400
|+++ dwm-5.9-colors/config.def.h 2011-08-18 02:02:47.033830823 -0400
File to patch:
Last edited by Farehe (2013-04-21 12:20:31)

[Solved] DWM and extra key's.

Hello.
I'm using DWM and now I have new keyboard with extra kyes Audio Mute, Raise or Lower volume you know
I tried:
showkey
And I have my key in .Xmodmap , I typed:
/path/to/.Xmodmap
and all was ok
And typed xmodmap and my keys was in mod4 section , this is the output of xmodmap:
xmodmap: up to 4 keys per modifier, (keycodes in parentheses):
shift Shift_L (0x32), Shift_R (0x3e)
lock Caps_Lock (0x42)
control Control_L (0x25), Control_R (0x6d)
mod1 Alt_L (0x40), Meta_L (0x9c)
mod2 Num_Lock (0x4d)
mod3
mod4 XF86AudioRaiseVolume (0x73), XF86AudioRaiseVolume (0x74), Super_L (0x7f), Hyper_L (0x80)
mod5 Mode_switch (0x5d), ISO_Level3_Shift (0x71), ISO_Level3_Shift (0x7c)
Now I care to play with config.h of my DWM.
Here is part of it:
{ MODKEY, XF86AudioRaiseVolume, spawn, SHCMD("exec mpc volume -5")}
And when I tried to compile it with that config I got following errors:
In file included from dwm.c:271:
config.h:41: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'Key'
config.h:65: warning: ISO C does not allow extra ';' outside of a function
config.h:69: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'Button'
config.h:80: warning: ISO C does not allow extra ';' outside of a function
dwm.c: In function 'buttonpress':
dwm.c:440: error: 'buttons' undeclared (first use in this function)
dwm.c:440: error: (Each undeclared identifier is reported only once
dwm.c:440: error: for each function it appears in.)
dwm.c: In function 'grabbuttons':
dwm.c:929: error: 'buttons' undeclared (first use in this function)
dwm.c: In function 'grabkeys':
dwm.c:952: error: 'keys' undeclared (first use in this function)
dwm.c: In function 'keypress':
dwm.c:1020: error: 'keys' undeclared (first use in this function)
make: *** [dwm.o] Errpr 1
And building stop's :(
Is someone use extra keys with DWM.
Thanks for any help
Last edited by SpeedVin (2009-08-12 18:33:25)

SpeedVin wrote:
Tillotson wrote:/* See /* appearance */
static const char font[] static const char normbordercolor[] static const char normbgcolor[] static const char normfgcolor[] static const char selbordercolor[] static const char selbgcolor[] static const char selfgcolor[] static unsigned int borderpx static unsigned int snap static Bool showbar static Bool topbar /* tagging */
static const char *tags[] static Rule rules[] = {
/* class { "Thunar", { "VirtualBox", { "MPlayer", { "Vlc", { "XCalc", /* layout(s) */
static const float mfact static const Bool resizehints static const Layout layouts[] = {
/* symbol arrange { "[]=", { "><>", { "[M]", /* key definitions */
#define MODKEY Mod4Mask
#define TAGKEYS(KEY,TAG) \
{ MODKEY, { MODKEY|ControlMask, { MODKEY|ShiftMask, { MODKEY|ControlMask|ShiftMask, KEY, /* helper for spawning #define SHCMD(cmd) { .v /* commands */
static const char *dmenucmd[] static const char *termcmd[] static const char *browsercmd[] static const char *musiccmd[] static const char *talkcmd[] static const char *shutcmd[] static const char *filebrowse[] static const char *mutecmd[] static const char *volupcmd[] static const char *voldowncmd[] static const char *calccmd[] static Key keys[] = {
/* modifier { 0, { 0, { 0, { 0, { MODKEY, { MODKEY|ShiftMask, { MODKEY|ShiftMask, { MODKEY|ShiftMask, { MODKEY|ShiftMask, { MODKEY|ShiftMask, { MODKEY|ShiftMask, { MODKEY, { MODKEY, { MODKEY, { MODKEY, { MODKEY, { MODKEY, { MODKEY, { MODKEY|ShiftMask, { MODKEY, { MODKEY, { MODKEY, { MODKEY, { MODKEY|ShiftMask, { MODKEY, { MODKEY|ShiftMask, { MODKEY, { MODKEY, { MODKEY|ShiftMask, { MODKEY|ShiftMask, TAGKEYS( TAGKEYS( TAGKEYS( TAGKEYS( TAGKEYS( TAGKEYS( TAGKEYS( TAGKEYS( TAGKEYS( { MODKEY|ShiftMask, /* button definitions */
/* click can be a tag * ClkLtSymbol, ClkStatusText, static Button buttons[] = {
/* click { ClkLtSymbol, 0, { ClkLtSymbol, 0, { ClkWinTitle, 0, { ClkStatusText, 0, { ClkClientWin, MODKEY, { ClkClientWin, MODKEY, { ClkClientWin, MODKEY, { ClkTagBar, 0, { ClkTagBar, 0, { ClkTagBar, MODKEY, { ClkTagBar, MODKEY, Thank you very much I Sadly still no reaction LICENSE file for copyright and license details. */
= "-*-fixed-medium-r-*-*-18-*-*-*-*-*-iso8859-*";
= "#C7C7C7";
= "#000000";
= "#888888";
= "#1793D1";
= "#000000";
= "#FFFFFF";
= 1; /* border pixel of windows */
= 32; /* snap pixel */
= True; /* False means no bar */
= True; /* False means bottom bar */
= { "1", "2", "3", "4", "5", "6", "7", "8", "9" };
instance title tags mask isfloating */
NULL, NULL, 0, True },
NULL, NULL, 0, True },
NULL, NULL, 0, True },
NULL, NULL, 0, True },
NULL, NULL, 0, True },
= 0.55; /* factor of master area size [0.05..0.95] */
= True; /* False means respect size hints in tiled resizals */
function */
tile }, /* first entry is default */
NULL }, /* no layout function means floating behavior */
monocle },
KEY, view, {.ui = 1 << TAG} }, \
KEY, toggleview, {.ui = 1 << TAG} }, \
KEY, tag, {.ui = 1 << TAG} }, \
toggletag, {.ui = 1 << TAG} },
shell commands in the pre dwm-5.0 fashion */
= (const char*[]){ "/bin/sh", "-c", cmd, NULL } }
= { "dmenu_run", "-fn", font, "-nb", normbgcolor, "-nf", normfgcolor, "-sb", selbgcolor, "-sf", selfgcolor, NULL };
= { "urxvtc", NULL };
= { "firefox", NULL };
= { "urxvtc", "-e", "ncmpcpp", NULL };
= { "urxvtc", "-e", "weechat-curses", NULL };
= { "sudo", "shutdown", "-h", "now", NULL };
= { "thunar", NULL };
= { "amixer", "-q", "sset", "Master", "toggle", NULL };
= { "amixer", "-q", "sset", "PCM", "5-", "unmute", NULL };
= { "amixer", "-q", "sset", "PCM", "5+", "unmute", NULL };
= { "xcalc", NULL };
key function argument */
0x1008ff12, spawn, {.v = mutecmd } },
0x1008ff11, spawn, {.v = volupcmd } },
0x1008ff13, spawn, {.v = voldowncmd } },
0x1008ff1d, spawn, {.v = calccmd } },
XK_p, spawn, {.v = dmenucmd } },
XK_Return, spawn, {.v = termcmd } },
XK_b, spawn, {.v = browsercmd } },
XK_m, spawn, {.v = musiccmd } },
XK_f, spawn, {.v = filebrowse } },
XK_t, spawn, {.v = talkcmd } },
XK_Delete, spawn, {.v = shutcmd } },
XK_b, togglebar, {0} },
XK_j, focusstack, {.i = +1 } },
XK_k, focusstack, {.i = -1 } },
XK_h, setmfact, {.f = -0.05} },
XK_l, setmfact, {.f = +0.05} },
XK_Return, zoom, {0} },
XK_Tab, view, {0} },
XK_c, killclient, {0} },
XK_t, setlayout, {.v = &layouts[0]} },
XK_f, setlayout, {.v = &layouts[1]} },
XK_m, setlayout, {.v = &layouts[2]} },
XK_space, setlayout, {0} },
XK_space, togglefloating, {0} },
XK_0, view, {.ui = ~0 } },
XK_0, tag, {.ui = ~0 } },
XK_comma, focusmon, {.i = -1 } },
XK_period, focusmon, {.i = +1 } },
XK_comma, tagmon, {.i = -1 } },
XK_period, tagmon, {.i = +1 } },
XK_1, 0)
XK_2, 1)
XK_3, 2)
XK_4, 3)
XK_5, 4)
XK_6, 5)
XK_7, 6)
XK_8, 7)
XK_9, 8)
XK_q, quit, {0} },
number (starting at 0),
ClkWinTitle, ClkClientWin, or ClkRootWin */
event mask button function argument */
Button1, setlayout, {0} },
Button3, setlayout, {.v = &layouts[2]} },
Button2, zoom, {0} },
Button2, spawn, {.v = termcmd } },
Button1, movemouse, {0} },
Button2, togglefloating, {0} },
Button3, resizemouse, {0} },
Button1, view, {0} },
Button3, toggleview, {0} },
Button1, tag, {0} },
Button3, toggletag, {0} },
will see what I can do .

What's the difference in the user experience of ion3, wmii and dwm.

I want to try something new, especially some new concepts, not just another wm, nor I actually 'need' something - in the moment xfce just works for me. Of course, I have thoroughly read the (available) documentation of these WMs and tested a session, but they are all too different and I feel I need some shared experience in order to decide in which one to invest more time. I would like to ask people that have wider experience to spot some strong or weak points of each WM - but in no way it should be like 'this one is better' or sth. - especially ones that are not instantly obvious - from the descriptions on the home site or limited testing,
For example - wmii talk 9P, and this sound really cool, but I have no damn idea how this could be actually useful. Dwm is extremely minimalist, and I am not sure if it is not too minimalist to be practical.
Again, I don't need advice like what Wm to choose (which is essentially a stupid question), but just mentioning peculiar spots of each one, especially not instantly obvious ones.
Thank you in advance.
P.S. If there is already a topic, that is close to that, I'll appreciate provided link - my search found just general WM topics, as well as topics for specific WM, which was useful, but not completely enough.
P.P.S. If someone thinks ratpoison is unfairly ignored, one may provide its advantages, although I just somehow do not like it (nothing reasanoble)

The three (and I'll throw in Ratpoison because I love it) seem to have distinct approaches to the way you're expected to use windows.
DWM expects you to have one main window focused and a few others that you do want to see, but don't need to have focused at full size. The way it puts them along the edge is pretty nice on a widescreen monitor. Virtual desktops are provided since it would be a pain to cycle all the way through your window list whenever you wanted to change.
wmii seems (I only played with it a little) to be based largely on columns. This is very similar to Plan 9's editor Acme. Heck, when I first saw the screen shot on the wmii page I thought I was looking at Acme. You divide the screen into (usually two) columns and can arrange your windows within those as you choose. It's a fairly nice approach, marrying the simplicity of DWM's "main window" concept with the flexibility of other managers by having only a couple of "places" for windows (the columns), but multiple windows in each, whose exact positioning doesn't matter much. Tags are substituted for conventional workspaces. I haven't played with this feature.
Ion3 (which I used for a while) is based on the idea that you will divide the screen into just a couple of panes, and group your windows into those. Most of your windows will be invisible at any given time, but you can get to them all easily with the tab strip at the top of each pane, showing its associated windows. In this WM each window is in a definite place, unlike in Ratpoison, in which hidden windows are just hidden, and associated with no pane in particular. Ion also assumes that you will have some programs that don't play nice with a tiled manager, and allows the creation of virtual desktops that contain floating windows. Virtual desktops in this WM are pretty much the same as those in your standard floating WM.
The key to "getting" Ratpoison (which I have used a lot, and am using now) is that unlike the other three, you're not expected to have a complex layout of screen panes. Although you could create something of arbitrary complexity using the vertical and horizontal spit commands, it would quickly become a nightmare to work with, and there is no easy way to switch between layouts because, while you can save and load them, windows are not associated with particular panes on the screen, and will end up who-knows where. Instead, a Ratpoison user wants to switch between windows by hitting ^T (remappable, I use my Windows key) and then the number that was assigned when each window was created. As you may notice, this is how screen works as well. You quickly learn to remember these numbers, just like a screen user or Nethack player. 90% of the time I work with only one window on the screen switching between it and my alternate window, and the other 9% of the time I have two windows (mostly when I want to drag and drop things, but sometimes for reference material). 1% of the time I might hit three or [gasp!] four.
While the other three WMs seek to make it easier to manage your on screen windows, Ratpoison takes the approach that you probably don't need to have more than a couple of windows on screen at one time. Based on this logic, Ratpoison doesn't provide virtual desktops. If your windows aren't on screen, why do you need more virtual screens for them not to be on? Ratpoison does provide window groups, which serve a similar function. Unlike virtual desktops, switching groups does not change what's on your screen; it only changes the list of windows you are working with. This may sound like a pain, but keep in mind that you, as a Ratpoison user, probably have fewer than two panes on your screen. It's not hard to switch both of those to something else, and half the time you only want to change one of them (e.g. drag and drop between window groups). Ratpoison also supports multiple screens, which are treated much like panes on a single screen, except of course you can not delete them (senseless) or move windows between them (X11 limitation; not Ratpoison specific).
Another nice Ratpoison feature is that you can tell it not to manage certain windows, and you can tell it to leave some padding between windows and the edge of the screen. So I can run an unmanaged Rox sidebar to hold try icons, status monitors, a trash can, and volume control, and reserve that space for it with some padding. I can also remove that padding or change its size if I want to cover the sidebar.
Last edited by pauldonnelly (2007-04-22 19:52:16)

UZBL wants to remove dmenu-vertical-xft and replace with dmenu

Thinking that UZBL may have a PKGBUILD that asks for dmenu.
uzbl-tabbed and uzbl-browser that is.
uzbl-core installed fine after removing uzbl-git.
Currentlyusing dmenu-vertical-xft
all good all fun!
pacman -S uzbl-tabbed
resolving dependencies...
looking for inter-conflicts...
:: dmenu conflicts with dmenu-vertical-xft. Remove dmenu-vertical-xft? [Y/n] n
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: dmenu: conflicts with dmenu-vertical-xft
Last edited by yvonney (2010-04-10 01:17:38)

most iteresting new tip for me. thank you.
so, the PKGBUILD first half of it is below and I'll change the last line or two? to:
conflicts=('dmenu')
"provides=('dmenu=4.0')"
um, what about conflicts.... leave it as is I think. makes sense.
Actually seem quick a brilliant way, change it slightly like that.
And of course a lot more I won't yet understand.
in any event, great!
-------- PKGBUILD FIRST PART BELOW
pkgname=dmenu-vertical-xft
pkgver=4.0
pkgrel=4
pkgdesc="Dynamic X menu with zenix's vertical patch and xft support"
url="http://tools.suckless.org/dmenu/"
arch=('i686' 'x86_64')
license=('MIT')
depends=('libxinerama' 'libxft')
makedepends=('xineramaproto')
conflicts=('dmenu')
provides=('dmenu')
Last edited by yvonney (2010-04-10 06:56:23)

DWM statusbar produces strange gap to the right

I'm using dwm-5.9 patched with statuscolors and when I use color codes with something like
xsetroot -name "\x05$somestring\x01"
the statusbar gets a bigger gap to the right even though there's nothing set to display there. A picture would explain this better: (the statusbar script used is displayed in the terminal)
The gap gets bigger when adding more colored elements to the output string. This does not happen when not using statuscolor codes. What's wrong here?
Last edited by hesse (2012-03-15 14:54:58)

Ok. I forgot to say that I patched dwm-5.9 with the statuscolor-5.9 patch. You say there are separate spacing issues on different versions - would it be worth trying to patch with an older version of statuscolor? My guess is it will require an older version of dwm..
Last edited by hesse (2012-03-15 16:32:14)

[SOLVED] DWM - how do you apply patches with patch?

I'm totally new to dwm (it's working great by the way) and patching. I'm having problems understanding how to use the patch program. The basic usage on dwm site says basically:
patch -p1 < path/to/patch.diff
Great, now I have the patch file ~/builds/dwn/patch/dwm-5.9-statuscolors.diff and my altered ~/builds/dwn/config.h. Here's what I did
herman@sam ~/builds/dwm $ patch -p1 <patch/dwm-5.9-statuscolors.diff
can't find file to patch at input line 4
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
|diff -up dwm-5.9/config.def.h dwm-5.9-colors/config.def.h
|--- dwm-5.9/config.def.h 2011-07-10 16:24:25.000000000 -0400
|+++ dwm-5.9-colors/config.def.h 2011-08-18 02:02:47.033830823 -0400
File to patch: config.def.h
config.def.h: No such file or directory
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 41
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
|Only in dwm-5.9: config.h
|Only in dwm-5.9: dwm
|diff -up dwm-5.9/dwm.c dwm-5.9-colors/dwm.c
|--- dwm-5.9/dwm.c 2011-07-10 16:24:25.000000000 -0400
|+++ dwm-5.9-colors/dwm.c 2011-08-18 02:07:20.788935100 -0400
File to patch: dwm.c
dwm.c: No such file or directory
Skip this patch? [y]
Skipping patch.
12 out of 12 hunks ignored
and it asks me for the filename it didn't find at line 4. Looking at the patch, I see it's a diff on config.def.h so I suppose this is the file to be patched and that I should supply this filename and the same with dwm.c? I'm not new to C coding but fresh out when it comes to diffing and patching, how do I actually go forward from here?
Edit:
More info - I used the description using ABS to download the PKGBUILD for dwm and making dwm. My files
herman@sam ~/builds/dwm $ ls -R
PKGBUILD config.h dwm-5.9-2-x86_64.pkg.tar.xz dwm-5.9.tar.gz dwm.desktop dwm.install patch pkg src
./patch:
dwm-5.9-statuscolors.diff
./pkg:
usr
./pkg/usr:
bin share
./pkg/usr/bin:
dwm
./pkg/usr/share:
doc licenses man xsessions
./pkg/usr/share/doc:
dwm
./pkg/usr/share/doc/dwm:
README
./pkg/usr/share/licenses:
dwm
./pkg/usr/share/licenses/dwm:
LICENSE
./pkg/usr/share/man:
man1
./pkg/usr/share/man/man1:
dwm.1.gz
./pkg/usr/share/xsessions:
dwm.desktop
./src:
config.h dwm-5.9 dwm-5.9.tar.gz dwm.desktop
./src/dwm-5.9:
LICENSE Makefile README config.def.h config.def.h.orig config.def.h.rej config.h config.mk dwm dwm.1 dwm.c dwm.o
Last edited by roygbiv (2011-12-06 20:37:40)

Ok thanks but I'm confused again (I know..). I managed to patch the files config.def.h and dwm.c in the source dir and noticed there is yet another config.h file there as well. Now, the in the top level dir with the PKGBUILD I also have a config.h, which is the one I do my config changes. I'm confused because I now have these three header files (2x config.h + config.def.h) which are supposed to have the same source code? I've read around on the net, but haven't gotten any further answers yet. What are the purpose of each config and how should I use/update/manage them when recompiling? This is my situation:
herman@sam ~/build/dwm $ tree .
├── PKGBUILD
├── config.h <----------------------------------------------------- this one
├── dwm-5.9-2-x86_64.pkg.tar.xz
├── dwm-5.9.tar.gz
├── dwm.desktop
├── dwm.install
├── pkg
│   └── usr
│   ├── bin
│   │   └── dwm
│   └── share
│   ├── doc
│   │   └── dwm
│   │   └── README
│   ├── licenses
│   │   └── dwm
│   │   └── LICENSE
│   ├── man
│   │   └── man1
│   │   └── dwm.1.gz
│   └── xsessions
│   └── dwm.desktop
└── src
├── config.h -> /home/herman/build/dwm/config.h
├── dwm-5.9
│   ├── LICENSE
│   ├── Makefile
│   ├── README
│   ├── config.def.h <-----------------------------------------------------this one
│   ├── config.def.h.orig
│   ├── config.h <----------------------------------------------------------this one
│   ├── config.mk
│   ├── dwm
│   ├── dwm-5.9-statuscolors.diff
│   ├── dwm.1
│   ├── dwm.c
│   ├── dwm.c.orig
│   └── dwm.o
├── dwm-5.9.tar.gz -> /home/herman/build/dwm/dwm-5.9.tar.gz
└── dwm.desktop -> /home/herman/build/dwm/dwm.desktop
Thanks guys!
Last edited by roygbiv (2011-12-06 20:06:10)

Dwm-pango escaping ansi status color

Hi, i'm trying to ouput to dwm-pango default status bar some colored info like date and time. I patched the dwm.c file with this correctly because I didn't get errors.
Trying this simple example below the bar outputs literally the string, without escaping.
xsetroot -name "\033[1;36mHELLO"
Does the patch work with pango patched dwm?
If yes, can somebody, kindly, explain me how to output colors to the statusbar?`
Bye!

Thanks, mhhm someting goes wrong with the patch.
I copied your diff to src folder, where there is dwm.c, and I did this and the output:
patch -Np1 < ../02-dwm-6.0-statuscolors.diff
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
|--- dwm.c.orig 2013-03-30 22:57:38.146738373 +0100
|+++ dwm.c 2013-03-30 23:04:34.136731375 +0100
File to patch: dwm.c
patching file dwm.c
Hunk #1 succeeded at 49 (offset -1 lines).
Hunk #2 succeeded at 101 (offset -1 lines).
Hunk #3 succeeded at 178 (offset -12 lines).
Hunk #4 FAILED at 782.
Hunk #5 succeeded at 771 (offset -55 lines).
Hunk #6 succeeded at 808 (offset -55 lines).
Hunk #7 FAILED at 886.
Hunk #8 succeeded at 878 (offset -55 lines).
Hunk #9 succeeded at 1146 (offset -54 lines).
Hunk #10 succeeded at 1614 (offset -54 lines).
Hunk #11 FAILED at 1745.
Hunk #12 succeeded at 1771 (offset -65 lines).
3 out of 12 hunks FAILED -- saving rejects to file dwm.c.rej
Anyway thank you again for the reply!

Desktop Windows Composition and Windows 8.1 Pro x64 [SOLVED]

Hi, I'm Jenn, also new to these forums.
I stumbled upon a problem when switching from Windows 7 x64 to Windows 8.1 Pro x64.
I have the EXACT same setup, same laptop, same hardware, same programs, same configuration, everything.
Windows 7 never did anything like the problem I now have in Win 8.1. Here's the problem;
Whenever I run more than 1 3D application, after 1-5 minutes the screen blinks, and hangs the graphics of one, some or all the programs (randomly). It doesn't hang the actual program (or game), it just stops rendering the graphics -- I can still hear the software's
sound and if I click around, I can hear myself interacting with it.
I have ALL the latest drivers for the computer, motherboard, ALL devices including graphics cards etc. Also ALL Windows Updates installed, nothing more to install.
All of the programs I use is specifically set to use only the nVidia adapter, forcibly through the nVidia Control Panel, so it's not a switching graphics problem because it's a laptop. Also, never was a problem in Windows 7 either.
Here's what I gathered from event viewer right when it happened;
A logon was attempted using explicit credentials.
Subject:
Security ID: SYSTEM
Account Name: PIXIELIGHT$
Account Domain: HYPERUNKNOWN
Logon ID: 0x3E7
Logon GUID: {00000000-0000-0000-0000-000000000000}
Account Whose Credentials Were Used:
Account Name: DWM-1
Account Domain: Window Manager
Logon GUID: {00000000-0000-0000-0000-000000000000}
An account was successfully logged on.
Subject:
Security ID: SYSTEM
Account Name: PIXIELIGHT$
Account Domain: HYPERUNKNOWN
Logon ID: 0x3E7
Logon Type: 2
Impersonation Level: Impersonation
New Logon:
Security ID: Window Manager\DWM-1
Account Name: DWM-1
Account Domain: Window Manager
Logon ID: 0x412659B
Logon GUID: {00000000-0000-0000-0000-000000000000}
Process Information:
Process ID: 0x304
Process Name: C:\Windows\System32\winlogon.exe
Special privileges assigned to new logon.
Subject:
Security ID: Window Manager\DWM-1
Account Name: DWM-1
Account Domain: Window Manager
Logon ID: 0x412659B
Privileges: SeAssignPrimaryTokenPrivilege
SeAuditPrivilege
SeImpersonatePrivilege
An account was logged off.
Subject:
Security ID: Window Manager\DWM-1
Account Name: DWM-1
Account Domain: Window Manager
Logon ID: 0x3E3290A
Logon Type: 2
So as you can see, DWM is logging in and out some account that can be all the way up to DWM-7 from what I've seen so far. It just logs in, sets some parameters and the directly logs out.
This is a ONE-user system, Only my user account is on it, and remote login has been disabled.
In Windows 7, at least DWM could be disabled - not that I ever had to, because it worked with all my stuff, but seeing as DWM is screwing up totally in Win8, I thought I'd just disable the server, but it's nowhere to be found.
Also, it seems Microsoft changed how it works, the system has been redesigned to generate an OK even if it's still on, like this example below:
DwmEnableComposition( DWM_EC_DISABLECOMPOSITION ) does not work on Windows 8, even though it returns S_OK. Confirmation is by calling DwmIsCompositionEnabled(), which shows the former function had no effect.
There's only 1 dwm.exe running.
There's only 1 user logged in (me).
There's only 1 user in the userlist (except for the Administrator account).
Running only 1 of the softwares at a time is not an option for me, either for work or for home use, so how can I fix this?
// Jenn

Hi Jenn,
Please take a look at the following article.
http://msdn.microsoft.com/en-us/library/windows/desktop/hh848042(v=vs.85).aspx
In Windows 8, Desktop Window Manager (DWM) is always ON and cannot be disabled by end users and apps.
I suggest you to download and install the graphic driver from the manufacturer and check if this issue still exist.
As you may have two graphic cards, we could temporally disable one and check if there are compatibility issues.
Best regards,
Fangzhou CHEN
Fangzhou CHEN
TechNet Community Support

[SOLVED] dwm pertag patch no working properly

Hello everybody! I recently had to redo my system.
Before this change I was using the DWM 6.0 with patches NMaster and pertag.
link to the source code used - https://github.com/abara/config/tree/master/dwm-pertag
But now, after having reinstalled the base system, I realized that the same code that I used before is no longer behaving as it should.
He is working as if there is no patch applied in dwm.c
I wonder what would be the possible reasons.
P.S. will not use sprinkles fork
Last edited by abarahc (2013-07-11 23:14:07)

ANOKNUSA wrote:NMaster patch is now part of the base code, so applying a patch for it is superfluous.
Yeah, that's what I meant ;P http://dwm.suckless.org/patches/nmaster
I'm using dwm with pertag patch and things are working as expected.

DWM is not installing properly

I have followed and read the arch wiki top to bottom, but am still unable to boot into dwm from LXDM. Here is what I did:
First I downloaded the base-devel packages (using pacman)
Then I downloaded all the abs packages (also using pacman)
Then I ran:
pacman -S base-devel abs dmenu
Then abs:
abs community/dwm
cp -r /var/abs/community/dwm ~/dwm
Then I made the package:
makepkg -i
Then I made the custom start script and an alternative .desktop file, as said in the wiki
Here are my current files:
/usr/share/xsessions/dwm-personalized.desktop
[Desktop Entry]
Encoding=UTF-8
Name=Dwm-personalized
Comment=Dynamic window manager
Exec=dwm-personalized
Icon=dwm
Type=XSession
/usr/bin/dwm-personalized
#!/bin/sh
exec dwm
(I changed #!/bin/zsh to /sh because I'm using bash)
Then I made /usr/bin/dwm-personalized executable:
chmod +x /usr/bin/dwm-personalized
I did these steps literally 3 days ago and it installed dwm without error, but yesterday I decided I would change up the config a bit, but broke everything. So I decided to start fresh and delete everything, so I ran:
sudo pacman -Rs dwm
and then manually removed the two custom files as said in the wiki.
However, for the past day, I have been trying to literally do the same thing, but now I cannot get into dwm. I turn on my computer, get into LXDM, choose "dwm" or "dwm-personalized" on the drop down menu, then I type in my username and password, then it looks like it's booting into dwm for 1 second, but it doesn't and just boots me out. Would anyone know a fix for this? I am literally doing the same steps that I preformed 3 days ago, but they do not work anymore.

runical is probably right; were the problem in dwm itself, dwm almost certainly wouldn't have compiled and installed in the first place. With regard to the "dwm-personalized" script: All your copy the script does is launch the one and only dwm binary you have installed. It's no different from a symlink. The "personalized" aspect of the script on the wiki page is to set a couple environment variables that could just as easily be set in your Bash configuration, so in your case (and most cases, IMHO) that script is probably unnecessary.
I'm really not familiar with lxdm, but I would guess the problem lies there. If you want to start dwm from lxdm, just use the desktop file that comes with the dwm package from ABS and see if that works; otherwise, try just adding it to ~/.xinitrc again, this time making sure that every command in ~/.xinitrc is appended with '&'. Without the '&' aftear each command the X start-up process will hang, waiting for a command to finish before continuing.

DWM 6.0 statuscolors and xft

Similar Messages

Maybe you are looking for