You're going to need to use the gnome-bluetooth applet, not blueman. I have no idea what blueman is doing underneath, but it's not really a supported way to interact with NetworkManager. NM has the functionality that you're looking for, so if there's a problem with NM or nm-applet's handling of DUN, then we can try to fix this bug.
But otherwise, it's a blueman bug. The nm-applet GConf data is an implementation detail that's not public API, and that's what blueman is modifying. The NM gnome-bluetooth plugin is the supported way of configuring PAN and DUN connections.
You're going to need to use the gnome-bluetooth applet, not blueman. I have no idea what blueman is doing underneath, but it's not really a supported way to interact with NetworkManager. NM has the functionality that you're looking for, so if there's a problem with NM or nm-applet's handling of DUN, then we can try to fix this bug.
But otherwise, it's a blueman bug. The nm-applet GConf data is an implementation detail that's not public API, and that's what blueman is modifying. The NM gnome-bluetooth plugin is the supported way of configuring PAN and DUN connections.
See:
http:// blogs.gnome. org/dcbw/ 2009/07/ 10/unwire- with-networkman ager/
If that procedure fails to work, then we can investigate the issue. Otherwise, if that procedure does work, then it's a Blueman bug.