Valgrind memory leaks still reachable after calling Simplebluez::Bluez::init()

[mscottwvc]

On Ubuntu if I run the example programs or even have a simple program that only calls Simplebluez::Bluez::init() I get a bunch of still reachable memory leaks as shown in the attached file. Anyway to fix these or are these caused by dbus or something? Similar stuff happens with Simpleble as well. Valgrind was run as follows: valgrind --leak-check=full --show-leak-kinds=all --track-origins=yes --verbose --log-file=val.txt val.txt

[kdewald]

Hey @mscottwvc, thanks for the report, I'll look into it!