Comment 76 for bug 145360

I can confirm this:

When you open volume control and adjust something, you can sometimes induce a crash. It looks like this thing is very similar to #252046 gvfs-hal-volume-monitor crashed with SIGSEGV in strlen().

Another way to induce a (fatal) crash is simply: ($ sudo compiz).

This could be due to my /home/$USER settings:

thomas@thomas-laptop:~$ ls -la ./.d*
-rwxrwxrwx 1 thomas thomas 51 2008-10-08 00:22 ./.devede
-rwxrwxrwx 1 thomas thomas 28 2008-10-15 21:29 ./.dmrc

./.dbus:
total 12
drwxrwxrwx 3 thomas root 4096 2008-10-03 00:57 .
drwxrwxrwx 69 thomas thomas 4096 2008-10-16 23:26 ..
drwxrwxrwx 2 thomas root 4096 2008-10-03 00:57 session-bus
thomas@thomas-laptop:~$ cd ./.db*/sess*
thomas@thomas-laptop:~/.dbus/session-bus$ ls -la
total 12
drwxrwxrwx 2 thomas root 4096 2008-10-03 00:57 .
drwxrwxrwx 3 thomas root 4096 2008-10-03 00:57 ..
-rwxrwxrwx 1 thomas root 463 2008-10-16 23:22 00e2e23118afd712ae53375648e55de3-0
thomas@thomas-laptop:~/.dbus/session-bus$ cat ./00*
# This file allows processes on the machine with id 00e2e23118afd712ae53375648e55de3 using
# display :0 to find the D-Bus session bus with the below address.
# If the DBUS_SESSION_BUS_ADDRESS environment variable is set, it will
# be used rather than this file.
# See "man dbus-launch" for more details.
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-inY1BQYKBn,guid=b48c171592d4350b2150d3d048f7be87
DBUS_SESSION_BUS_PID=6306
DBUS_SESSION_BUS_WINDOWID=4194305
thomas@thomas-laptop:~/.dbus/session-bus$