User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.8.1.3) Gecko/20070403 Firefox/2.0.0.3 Build Identifier: The disk performance plugin can be configured by using the configuration dialog. It will apply the new configuration after clicking on the close button and save the configuration to a config file. However, after restarting the panel or xfce the new configuration is not applied (except for device and label). Reproducible: Always Steps to Reproduce: 1. Set a different color than green in the gui configuration -> color changes. 2. Quit XFCE or the panel. 3. Restart XFCE or the panel. Actual Results: 1. Bar color is green. Expected Results: 2. Bar color should be anything else if green was not selected. This happens only with the disk performance plugin, all other plugins work fine. Same result on three different machines, all using gentoo distribution. Disk performance monitor version: 2.1.0
Sorry, this actually *only* concerns the bar colors. The rest of the configuration options is read fine.
Created attachment 1272 Fix for the configuration being read too late. I've fixed the bug by myself, it is actually just one line in the diskperf_construct() function. While the configuration is read, it seems it is read too late (after the monitor bars have been created). With this patch, the configuration will be read before creation time so that the previously saved settings will be used.
This bug still exists in the newer version 2.2.0, and the patch still applies correctly. Another solution to this issue has been provided in bug #3074. It would be helpful if the developer could decide which version is the better one and include it in the next release, or fix it him/herself. Simply raising the version numbers without acknowledging the bug and applying the fix won't make it go away. Sorry for the rant, it works fine otherwise.
Thanks for your patch. Both your patch and the one in 3074 look fine to me, but the patch for 3074 was already applied a while ago, so I won't use this one. This issue will be solved in the next release. *** This bug has been marked as a duplicate of bug 3074 ***