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

--- Comment #3 from McCak <fauzanrizqimuham...@gmail.com> ---
(In reply to Méven Car from comment #2)
> (In reply to McCak from comment #0)
> > SUMMARY
> > Plasma Wayland (5.25.0) Multi Monitor or Display settings doesnt work on
> > Hybrid AMD CPU + AMD GPU Laptop.. 
> > 
> > 
> > STEPS TO REPRODUCE (First Version)
> > 1. Boot with Display port/HDMI connected
> > 2. Login to SDDM
> > 3. Wait.. 
> > 
> > OBSERVED RESULT (First Version)
> > Black screen on both laptop monitor and external one.. Waiting more than 10
> > mins didnt indicate any sign of life.. However going to the TTY seems fine
> > 
> > EXPECTED RESULT (First Version)
> > Show some content on the external screen only (that was my setting tried
> > previously)
> > 
> > STEPS TO REPRODUCE (Second Version)
> > 1. Boot without display port/HDMI connected
> > 2. Login to SDDM
> > 3. Wait..
> > 4. Plug DP/HDMI 
> > 
> > OBSERVED RESULT (Second Version)
> > Blackscreen on the external display and cant be enabled via Display settings
> > (the apps just straight up crashed)
> > 
> > EXPECTED RESULT (Second Version)
> > Display Settings should work.. or atleast it show something on the external
> > display.. 
> > 
> > SOFTWARE/OS VERSIONS
> > 
> > Linux : Arch Linux
> > KDE Plasma Version: 5.25.0 
> > KDE Frameworks Version: 5.95.0
> > Qt Version: 5.15.4
> > 
> > ADDITIONAL INFORMATION
> > Both HDMI and DP connected directly to the dGPU.. And yes its already
> > activated.. However X11 doesnt have any similiar issue..
> > 
> > Hardware Specifications
> > Laptop : MSI Delta 15
> > CPU :Ryzen 7 5800H
> > GPU0 : RX 6700M 
> > GPU1: Vega 8
> > 
> > Logs 
> > https://pastebin.com/0RnCFX2g
> > 2804 1000 998 SIGSEGV present  /usr/bin/kded5
> 
> Thank you, and for the added stacktrace.
> 
> Extract from trace:
> 
> #0  0x00007f204acd036c n/a (libc.so.6 + 0x8e36c)
>                                               #1  0x00007f204ac80838 raise
> (libc.so.6 + 0x3e838)
>                                               #2  0x00007f204bd9f384
> _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x7384)
>                                               #3  0x00007f204ac808e0 n/a
> (libc.so.6 + 0x3e8e0)
>                                               #4  0x00007f20478c5ee7
> _ZN9QtWayland9wl_output11handle_doneEPvP9wl_output (libQt5WaylandCl>
>                                               #5  0x00007f2047793536 n/a
> (libffi.so.8 + 0x7536)
>                                               #6  0x00007f2047790037 n/a
> (libffi.so.8 + 0x4037)
>                                               #7  0x00007f204c50e5e2 n/a
> (libwayland-client.so.0 + 0x75e2)
>                                               #8  0x00007f204c50ed73 n/a
> (libwayland-client.so.0 + 0x7d73)
>                                               #9  0x00007f204c50ef8c
> wl_display_dispatch_queue_pending (libwayland-client.so.0 + 0x7f8c)
>                                               #10 0x00007f20478a0c56
> _ZN15QtWaylandClient15QWaylandDisplay13flushRequestsEv (libQt5Wayla>
>                                               #11 0x00007f204b336430
> _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2b1430)
>                                               #12 0x00007f204bfbea7c
> _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Wi>
>                                               #13 0x00007f204b312b28
> _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Cor>
> 
> The stacktrace is limited, someone will need to reproduce it again.
> One would need at least libkscreen and qt5-wayland debug symbols to have
> more hindsight.
> Using debuginfod, it should be easy to install those on arch
> https://wiki.archlinux.org/title/Debugging/Getting_traces#Debuginfod

I am trying my best to debug the one that you requested.. sadly i dont know
where is the path for that.. (In reply to Méven Car from comment #2)
> (In reply to McCak from comment #0)
> > SUMMARY
> > Plasma Wayland (5.25.0) Multi Monitor or Display settings doesnt work on
> > Hybrid AMD CPU + AMD GPU Laptop.. 
> > 
> > 
> > STEPS TO REPRODUCE (First Version)
> > 1. Boot with Display port/HDMI connected
> > 2. Login to SDDM
> > 3. Wait.. 
> > 
> > OBSERVED RESULT (First Version)
> > Black screen on both laptop monitor and external one.. Waiting more than 10
> > mins didnt indicate any sign of life.. However going to the TTY seems fine
> > 
> > EXPECTED RESULT (First Version)
> > Show some content on the external screen only (that was my setting tried
> > previously)
> > 
> > STEPS TO REPRODUCE (Second Version)
> > 1. Boot without display port/HDMI connected
> > 2. Login to SDDM
> > 3. Wait..
> > 4. Plug DP/HDMI 
> > 
> > OBSERVED RESULT (Second Version)
> > Blackscreen on the external display and cant be enabled via Display settings
> > (the apps just straight up crashed)
> > 
> > EXPECTED RESULT (Second Version)
> > Display Settings should work.. or atleast it show something on the external
> > display.. 
> > 
> > SOFTWARE/OS VERSIONS
> > 
> > Linux : Arch Linux
> > KDE Plasma Version: 5.25.0 
> > KDE Frameworks Version: 5.95.0
> > Qt Version: 5.15.4
> > 
> > ADDITIONAL INFORMATION
> > Both HDMI and DP connected directly to the dGPU.. And yes its already
> > activated.. However X11 doesnt have any similiar issue..
> > 
> > Hardware Specifications
> > Laptop : MSI Delta 15
> > CPU :Ryzen 7 5800H
> > GPU0 : RX 6700M 
> > GPU1: Vega 8
> > 
> > Logs 
> > https://pastebin.com/0RnCFX2g
> > 2804 1000 998 SIGSEGV present  /usr/bin/kded5
> 
> Thank you, and for the added stacktrace.
> 
> Extract from trace:
> 
> #0  0x00007f204acd036c n/a (libc.so.6 + 0x8e36c)
>                                               #1  0x00007f204ac80838 raise
> (libc.so.6 + 0x3e838)
>                                               #2  0x00007f204bd9f384
> _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x7384)
>                                               #3  0x00007f204ac808e0 n/a
> (libc.so.6 + 0x3e8e0)
>                                               #4  0x00007f20478c5ee7
> _ZN9QtWayland9wl_output11handle_doneEPvP9wl_output (libQt5WaylandCl>
>                                               #5  0x00007f2047793536 n/a
> (libffi.so.8 + 0x7536)
>                                               #6  0x00007f2047790037 n/a
> (libffi.so.8 + 0x4037)
>                                               #7  0x00007f204c50e5e2 n/a
> (libwayland-client.so.0 + 0x75e2)
>                                               #8  0x00007f204c50ed73 n/a
> (libwayland-client.so.0 + 0x7d73)
>                                               #9  0x00007f204c50ef8c
> wl_display_dispatch_queue_pending (libwayland-client.so.0 + 0x7f8c)
>                                               #10 0x00007f20478a0c56
> _ZN15QtWaylandClient15QWaylandDisplay13flushRequestsEv (libQt5Wayla>
>                                               #11 0x00007f204b336430
> _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2b1430)
>                                               #12 0x00007f204bfbea7c
> _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Wi>
>                                               #13 0x00007f204b312b28
> _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Cor>
> 
> The stacktrace is limited, someone will need to reproduce it again.
> One would need at least libkscreen and qt5-wayland debug symbols to have
> more hindsight.
> Using debuginfod, it should be easy to install those on arch
> https://wiki.archlinux.org/title/Debugging/Getting_traces#Debuginfod

kded5
https://pastebin.com/erL0cH97

org_kde_powerdevil
https://pastebin.com/KHtvLHkE

plasmashell
https://pastebin.com/9dtktAez

I just found out that power devil and plasma shell is crashing too.. just
sending the logs in case hoping that is helpful... i apologize if that is not
the one you requested

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

Reply via email to