© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
7020100
(Get the code!)
Computerjy could you run a valgrind for me?
valgrind --leak-check=full gnome-power-manager > ./outfile.valgrind 2>&1
should do it, with the output redirected to outfile.valgrind. Run it for a long enough period so you believe you're experiencing a leak then hit ctrl+c which will end the logging session. You'll need to kill gnome-power-manager before you do this.
Now once you do that, I'll interpret the logs best i can and see if there's an actual leak left behind. My testing ran for a good few hours on my laptop and came up with dbusmenu about 3 separate times, that hashtable is definitely fixed now as I found in my most recent valgrinding.
All that seemed to be left were some references to Xorg and Xlib which are probably just false positives.