https://bugs.kde.org/show_bug.cgi?id=482713

Ilia Kats <ilia-k...@gmx.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ilia-k...@gmx.net

--- Comment #82 from Ilia Kats <ilia-k...@gmx.net> ---
This is happening to me after waking up from suspend to disk. Powerdevil seems
to be crashing due to a failed assertion:

Apr 03 08:45:30 Serenity org_kde_powerdevil[1278]: [  9574] Removing connected
display on bus 3
Apr 03 08:45:30 Serenity org_kde_powerdevil[1278]: [  9574] Emitting
DDCA_Display_Status_Event[70590.441:  DDCA_EVENT_DISPLAY_DISCONNECTED,
card1-HDMI-A-1, dref: DDCA_Display_Ref[9], io_pa>
Apr 03 08:45:30 Serenity org_kde_powerdevil[1278]: [  9574] libddcutil callback
thread 0x75353c02acc0 started
Apr 03 08:45:30 Serenity org_kde_powerdevil[1278]: [  9574] Started 1 event
callback thread(s)
Apr 03 08:45:30 Serenity org_kde_powerdevil[1278]: [  9574] Adding connected
display with bus 3
Apr 03 08:45:31 Serenity org_kde_powerdevil[1278]: [  9575] (ddc_open_display)
Delay before rechecking attribute status: Slept for 1000 millisec
Apr 03 08:45:31 Serenity org_kde_powerdevil[1278]: [  9575] Assertion failed:
"bus_info" in file ddc_packet_io.c at line 266
Apr 03 08:45:31 Serenity org_kde_powerdevil[1278]: QtDBus: cannot relay signals
from parent QObject(0x60093617b9a0 "") unless they are emitted in the object's
thread QThread(0x600936130c00>
Apr 03 08:45:31 Serenity org_kde_powerdevil[1278]: QSocketNotifier: Socket
notifiers cannot be enabled or disabled from another thread
Apr 03 08:45:31 Serenity org_kde_powerdevil[1278]: [  9575] Watch thread
terminated.
Apr 03 08:45:31 Serenity org_kde_powerdevil[1278]: QMutex: destroying locked
mutex

This is on Plasma 6.3.3 and ddcutil 2.2.0 on a laptop with an external screen
that is disconnected after starting hibernation and reconnected before
resuming.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to