<!-- 
.. title: Chitty Chitty Bang Bang
.. slug: chitty-chitty-bang-bang
.. date: 2013-11-17 16:39:11 UTC+01:00 
.. tags: archlinux, desktop, suse, 
.. link: 
.. description: 
.. type: text 
--> 

New hardware always has the effect that everything else suddenly feels slow and outdated. After experiencing the ease and effortlessness with which my [desktop](custom-made.html "desktop") handles everything I throw at it, my notebook (a Fujitsu Lifebook AH530) running [OpenSuse 12.3](bleeding-edge.html "OpenSuse 12.3") felt unresponsive and sluggish. Instead of updating to OpenSuse 13.1, I decided to install [Archbang](http://archbang.org "Archbang"), a distribution I [always](psychological-factors.html "always") wanted to run on one of my systems. Similar to [Crunchbang](http://crunchbang.org "Crunchbang") which [runs on my Mini](turbo.html "runs on my Mini"), Archbang offers an [Openbox](https://en.wikipedia.org/wiki/Openbox "Openbox") powered desktop which is about as lightweight and snappy as it gets.

Archbang, however, is even more frugal and spartan than Crunchbang. For example, there's no out-of-the-box support for Bluetooth devices.

The [Archlinux Wiki](https://wiki.archlinux.org/ "Archlinux Wiki") has [detailed instructions](https://wiki.archlinux.org/index.php/Bluetooth_Mouse "detailed instructions") as to the configuration of a Bluetooth mouse:

	systemctl start bluetooth
	systemctl enable bluetooth
	bluetoothctl
	 [bluetooth]# list
	  Controller <cmac> BlueZ 5.5 [default]
	 [bluetooth]# select <cmac>
	 [bluetooth]# power on
	 [bluetooth]# scan on
	 [bluetooth]# devices
	   Device <mmac> Name: Bluetooth Mouse
	 [bluetooth]# trust <mmac>
	 [bluetooth]# pairable on
	 [bluetooth]# pair <mmac>
	 [bluetooth]# connect <mmac>

After that, you only need to create a [new udev rule](https://bbs.archlinux.org/viewtopic.php?id=166362 "new udev rule") to activate the mouse upon a reboot:

	vim /etc/udev/rules.d/10-local.rules
	# Set bluetooth power up
	ACTION=="add", KERNEL=="hci0", RUN+="/usr/bin/hciconfig hci0 up"

All that works well until I suspend the session by closing the lid of the laptop. After that, the bluetooth mouse is inactive until I reboot the system.

Turns out that other people using Arch have the [same problem.](https://bbs.archlinux.org/viewtopic.php?id=170970 "same problem.") They even file [bug reports.](https://bugs.archlinux.org/task/37320 "bug reports.") Well, what's more, people using other distributions have this problem too, and they fill out reports on the respective ([Ubuntu](https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213239 "Ubuntu"), [Fedora](https://bugzilla.redhat.com/show_bug.cgi?id=1010410 "Fedora")) platform as well.

There's even a [fix,](http://thread.gmane.org/gmane.linux.kernel.stable/65406/focus=66112 "fix,") but for reasons I don't understand it didn't even make it into the recently released 3.12. What a bummer. **Update:** The fix has been included in 3.12.4. 😊

Apart from this, everything's just perfect. In the spirit of the distro, I try to use lightweight applications. For example, I use aarchup, guake and geany instead of yapan, kuake and texmaker or kile. Other than that, I just moved tint2 to the top and changed the conkyrc, but I even kept the wallpaper.

[![Desktop screenie](../images/deepgreen_screenshot_scaled_90.webp)](../images/deepgreen_screenshot_90.webp)

