I recognized something important today: the startup brightness is not generally set to the lowest possible value but to the value specified in the power-management-dialog (which was set to 0% in my case). So it's basically not a real bug anymore depending on whether it is intentional that the brightness-applet is not in synchronization with the power-management-dialog.
I recognized something important today: the startup brightness is not generally set to the lowest possible value but to the value specified in the power-managemen t-dialog (which was set to 0% in my case). So it's basically not a real bug anymore depending on whether it is intentional that the brightness-applet is not in synchronization with the power-managemen t-dialog.