https://bugs.kde.org/show_bug.cgi?id=489169
--- Comment #6 from Jakob Petsovits <jpe...@petsovits.com> --- I don't see it in this backtrace, but the one from Bug 489163 has two different threads (Thread 1 and Thread 3) both in BrightnessWorker::ddcSetBrightness(). This made me think - the DDCutilDisplay class's m_brightnessWorkerThread is created per instance, which means that for more than one monitor we'd have more than one brightness setter thread. I think this could be the root of this issue, and would explain why I've never seen the crash in my single-DDC-monitor setup despite months of use. I'll try tomorrow to refactor it so that the same thread is used across all different monitors, to prevent simultaneous function execution messing up ddcutil's internal (global) state. -- You are receiving this mail because: You are watching all bug changes.
