Bug 466727 - Plasmashell doesn't start properly under Wayland.
Summary: Plasmashell doesn't start properly under Wayland.
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: Startup process (other bugs)
Version First Reported In: 5.27.2
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: wayland-only
Depends on:
Blocks:
 
Reported: 2023-03-02 16:59 UTC by Doug
Modified: 2023-04-26 03:46 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:
dougshaw77: X11-


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Doug 2023-03-02 16:59:08 UTC
SUMMARY
***
Since upgrading to 5.27.1, I cannot log in to a Wayland session reliably.  I am getting a black screen instead.  I was able to get plasmashell to start up using plasmashell --replace at first, but now that is not working, either.  X11 is unaffected- if I start an X11 session, then logout and start a Wayland session, sometimes it starts properly, except the screen scaling is back to 100% instead of 150%.  When that happened, I tried setting the scaling to 100% and not changing it in case that setting was causing the problem, but it still won't start when I logout/login.  I started a new profile, and I can log in to a Wayland session under that profile consistently
***


STEPS TO REPRODUCE
1. Start up computer
2. attempt to login to a Wayland session
3. Optional- start Konsole, try to login with plasmashell --replace

OBSERVED RESULT
Screen flicks on and off 3 times, then gives black screen

EXPECTED RESULT
Plasmashell starts successfully

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux 
KDE Plasma Version: 5.27.2
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.2.1-2-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz
Memory: 15.4 GiB of RAM
Graphics Processor: AMD Radeon Pro WX 3200 Series
Manufacturer: Dell Inc.
Product Name: Precision 7540

ADDITIONAL INFORMATION
Comment 1 David Edmundson 2023-03-02 17:13:06 UTC
Please attach log from when you run plasmashell --replace
Comment 2 Doug 2023-03-03 05:31:45 UTC
(In reply to David Edmundson from comment #1)
> Please attach log from when you run plasmashell --replace

plasmashell is still not starting properly, but plasmashell --replace is now working.  I tried to pull logs after failing to start, and after plasmashell --replace.  I got the same thing both times:

journalctl /usr/bin/plasmashell -f 2> plasmashell.log            ✔ 
Mar 03 00:15:35 douglas-home plasmashell[1864]: qml: PlasmaExtras.ScrollArea is deprecated. Use PlasmaComponents3.ScrollView instead.
Mar 03 00:15:35 douglas-home plasmashell[1864]: qml: PlasmaExtras.ScrollArea is deprecated. Use PlasmaComponents3.ScrollView instead.
Mar 03 00:15:35 douglas-home plasmashell[1864]: qml: PlasmaExtras.ScrollArea is deprecated. Use PlasmaComponents3.ScrollView instead.
Mar 03 00:15:35 douglas-home plasmashell[1864]: qml: PlasmaExtras.ScrollArea is deprecated. Use PlasmaComponents3.ScrollView instead.
Mar 03 00:15:35 douglas-home plasmashell[1864]: qml: PlasmaExtras.ScrollArea is deprecated. Use PlasmaComponents3.ScrollView instead.
Mar 03 00:15:35 douglas-home plasmashell[1864]: qml: PlasmaExtras.ScrollArea is deprecated. Use PlasmaComponents3.ScrollView instead.
Mar 03 00:15:35 douglas-home plasmashell[1864]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Mar 03 00:15:35 douglas-home plasmashell[1864]: 2
Mar 03 00:15:35 douglas-home plasmashell[1864]: file:///usr/share/plasma/plasmoids/org.kde.kscreen/contents/ui/main.qml:30:5: Unable to assign [undefined] to bool
Mar 03 00:15:35 douglas-home plasmashell[1864]: The Wayland connection broke. Did the Wayland compositor die?

I don't know if any of that helps.  I don't know how to work with logs.
Comment 3 Nate Graham 2023-03-08 15:11:07 UTC
> The Wayland connection broke. Did the Wayland compositor die
This would seem to indicate that kwin_wayland crashed. If you open the "Crashes Processes Viewer" app, do you see any crashes for kwin_wayland?
Comment 4 Doug 2023-03-10 04:14:59 UTC
(In reply to Nate Graham from comment #3)
> > The Wayland connection broke. Did the Wayland compositor die
> This would seem to indicate that kwin_wayland crashed. If you open the
> "Crashes Processes Viewer" app, do you see any crashes for kwin_wayland?

Yes, several, and also several for baloo_file_extractor.  Do you want me to post any of the stack traces here?
Comment 5 Nate Graham 2023-03-10 16:32:59 UTC
Yes please. Can you bet a backtrace (not the full stack trace) of the latest kwin_wayland crash? For instructions how, see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
Comment 6 Doug 2023-03-11 17:54:57 UTC
(In reply to Nate Graham from comment #5)
> Yes please. Can you bet a backtrace (not the full stack trace) of the latest
> kwin_wayland crash? For instructions how, see
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl

coredumpctl gdb 1907                                                             INT ✘  4m 32s  
           PID: 1907 (kwin_wayland)
           UID: 1000 (doug)
           GID: 1000 (doug)
        Signal: 6 (ABRT)
     Timestamp: Sat 2023-03-11 12:41:24 EST (11min ago)
  Command Line: /usr/bin/kwin_wayland --wayland-fd 7 --socket wayland-0 --xwayland-fd 8 --xwayland-fd 9 --xwayland-display :1 --xwayland-xauthority /run/user/1000/xauth_YKfrLf --xwayland
    Executable: /usr/bin/kwin_wayland
 Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kwin_wayland.service
          Unit: user@1000.service
     User Unit: plasma-kwin_wayland.service
         Slice: user-1000.slice
     Owner UID: 1000 (doug)
       Boot ID: 9441289aa7524f7783644aab8afb54ae
    Machine ID: cf812b87541a48de95d492dd3b54a43d
      Hostname: douglas-home
       Storage: /var/lib/systemd/coredump/core.kwin_wayland.1000.9441289aa7524f7783644aab8afb54ae.1907.1678556484000000.zst (inaccessible)
       Message: Process 1907 (kwin_wayland) of user 1000 dumped core.
                
                Stack trace of thread 1907:
                #0  0x00007f1bf76a08ec n/a (libc.so.6 + 0x878ec)
                #1  0x00007f1bf7651ea8 raise (libc.so.6 + 0x38ea8)
                #2  0x00007f1bf763b53d abort (libc.so.6 + 0x2253d)
                #3  0x00007f1bf978bc8e n/a (libepoxy.so.0 + 0xbfc8e)
                #4  0x00007f1bf978f52a n/a (libepoxy.so.0 + 0xc352a)
                #5  0x00007f1bfa22bc97 n/a (libkwin.so.5 + 0x42bc97)
                #6  0x00007f1bfa22db39 _ZN4KWin9EglDmabufD1Ev (libkwin.so.5 + 0x42db39)
                #7  0x00007f1bfa22f091 _ZN4KWin18AbstractEglBackendD2Ev (libkwin.so.5 + 0x42f091)
                #8  0x00007f1bfa16c84d n/a (libkwin.so.5 + 0x36c84d)
                #9  0x00007f1bf9fbed6b _ZN4KWin10Compositor4stopEv (libkwin.so.5 + 0x1bed6b)
                #10 0x00007f1bf9fb7ae8 _ZN4KWin10Compositor12reinitializeEv (libkwin.so.5 + 0x1b7ae8)
                #11 0x00007f1bf86bea71 n/a (libQt5Core.so.5 + 0x2bea71)
                #12 0x00007f1bfa10ac7a _ZN4KWin9Workspace15slotReconfigureEv (libkwin.so.5 + 0x30ac7a)
                #13 0x00007f1bf86bea71 n/a (libQt5Core.so.5 + 0x2bea71)
                #14 0x00007f1bf86c0fcf _ZN6QTimer7timeoutENS_14QPrivateSignalE (libQt5Core.so.5 + 0x2c0fcf)
                #15 0x00007f1bf86b1b56 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2b1b56)
                #16 0x00007f1bf7d78b5c _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x178b5c)
                #17 0x00007f1bf868df48 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x28df48)
                #18 0x00007f1bf86d84b3 _ZN14QTimerInfoList14activateTimersEv (libQt5Core.so.5 + 0x2d84b3)
                #19 0x00007f1bf86d8962 _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2d8962)
                #20 0x0000558dd03855f2 n/a (kwin_wayland + 0x1335f2)
                #21 0x00007f1bf86866ec _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2866ec)
                #22 0x00007f1bf8691219 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x291219)
                #23 0x0000558dd02a2242 n/a (kwin_wayland + 0x50242)
                #24 0x00007f1bf763c790 n/a (libc.so.6 + 0x23790)
                #25 0x00007f1bf763c84a __libc_start_main (libc.so.6 + 0x2384a)
                #26 0x0000558dd02a3e95 n/a (kwin_wayland + 0x51e95)
                
                Stack trace of thread 2081:
                #0  0x00007f1bf769b766 n/a (libc.so.6 + 0x82766)
                #1  0x00007f1bf769df90 pthread_cond_wait (libc.so.6 + 0x84f90)
                #2  0x00007f1bea50c4ce n/a (radeonsi_dri.so + 0x10c4ce)
                #3  0x00007f1bea4bc89c n/a (radeonsi_dri.so + 0xbc89c)
                #4  0x00007f1bea50c3fc n/a (radeonsi_dri.so + 0x10c3fc)
                #5  0x00007f1bf769ebb5 n/a (libc.so.6 + 0x85bb5)
                #6  0x00007f1bf7720d90 n/a (libc.so.6 + 0x107d90)
                
                Stack trace of thread 2080:
                #0  0x00007f1bf769b766 n/a (libc.so.6 + 0x82766)
                #1  0x00007f1bf769df90 pthread_cond_wait (libc.so.6 + 0x84f90)
                #2  0x00007f1bea50c4ce n/a (radeonsi_dri.so + 0x10c4ce)
                #3  0x00007f1bea4bc89c n/a (radeonsi_dri.so + 0xbc89c)
                #4  0x00007f1bea50c3fc n/a (radeonsi_dri.so + 0x10c3fc)
                #5  0x00007f1bf769ebb5 n/a (libc.so.6 + 0x85bb5)
                #6  0x00007f1bf7720d90 n/a (libc.so.6 + 0x107d90)
                
                Stack trace of thread 2079:
                #0  0x00007f1bf769b766 n/a (libc.so.6 + 0x82766)
                #1  0x00007f1bf769df90 pthread_cond_wait (libc.so.6 + 0x84f90)
                #2  0x00007f1bea50c4ce n/a (radeonsi_dri.so + 0x10c4ce)
                #3  0x00007f1bea4bc89c n/a (radeonsi_dri.so + 0xbc89c)
                #4  0x00007f1bea50c3fc n/a (radeonsi_dri.so + 0x10c3fc)
                #5  0x00007f1bf769ebb5 n/a (libc.so.6 + 0x85bb5)
                #6  0x00007f1bf7720d90 n/a (libc.so.6 + 0x107d90)
                
                Stack trace of thread 2078:
                #0  0x00007f1bf769b766 n/a (libc.so.6 + 0x82766)
                #1  0x00007f1bf769df90 pthread_cond_wait (libc.so.6 + 0x84f90)
                #2  0x00007f1bea50c4ce n/a (radeonsi_dri.so + 0x10c4ce)
                #3  0x00007f1bea4bc89c n/a (radeonsi_dri.so + 0xbc89c)
                #4  0x00007f1bea50c3fc n/a (radeonsi_dri.so + 0x10c3fc)
                #5  0x00007f1bf769ebb5 n/a (libc.so.6 + 0x85bb5)
                #6  0x00007f1bf7720d90 n/a (libc.so.6 + 0x107d90)
                
                Stack trace of thread 2084:
                #0  0x00007f1bf77139df __poll (libc.so.6 + 0xfa9df)
                #1  0x00007f1bf636dc2f n/a (libglib-2.0.so.0 + 0xacc2f)
                #2  0x00007f1bf63150e2 g_main_context_iteration (libglib-2.0.so.0 + 0x540e2)
                #3  0x00007f1bf86d8c6c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2d8c6c)
                #4  0x00007f1bf86866ec _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2866ec)
                #5  0x00007f1bf84e725f _ZN7QThread4execEv (libQt5Core.so.5 + 0xe725f)
                #6  0x00007f1bf84e432a n/a (libQt5Core.so.5 + 0xe432a)
                #7  0x00007f1bf769ebb5 n/a (libc.so.6 + 0x85bb5)
                #8  0x00007f1bf7720d90 n/a (libc.so.6 + 0x107d90)
                
                Stack trace of thread 1909:
                #0  0x00007f1bf77139df __poll (libc.so.6 + 0xfa9df)
                #1  0x00007f1bf636dc2f n/a (libglib-2.0.so.0 + 0xacc2f)
                #2  0x00007f1bf63150e2 g_main_context_iteration (libglib-2.0.so.0 + 0x540e2)
                #3  0x00007f1bf86d8c6c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2d8c6c)
                #4  0x00007f1bf86866ec _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2866ec)
                #5  0x00007f1bf84e725f _ZN7QThread4execEv (libQt5Core.so.5 + 0xe725f)
                #6  0x00007f1bfa4d5cba n/a (libQt5DBus.so.5 + 0x23cba)
                #7  0x00007f1bf84e432a n/a (libQt5Core.so.5 + 0xe432a)
                #8  0x00007f1bf769ebb5 n/a (libc.so.6 + 0x85bb5)
                #9  0x00007f1bf7720d90 n/a (libc.so.6 + 0x107d90)
                
                Stack trace of thread 2105:
                #0  0x00007f1bf769b766 n/a (libc.so.6 + 0x82766)
                #1  0x00007f1bf769df90 pthread_cond_wait (libc.so.6 + 0x84f90)
                #2  0x00007f1bea50c4ce n/a (radeonsi_dri.so + 0x10c4ce)
                #3  0x00007f1bea4bc89c n/a (radeonsi_dri.so + 0xbc89c)
                #4  0x00007f1bea50c3fc n/a (radeonsi_dri.so + 0x10c3fc)
                #5  0x00007f1bf769ebb5 n/a (libc.so.6 + 0x85bb5)
                #6  0x00007f1bf7720d90 n/a (libc.so.6 + 0x107d90)
                
                Stack trace of thread 2125:
                #0  0x00007f1bf769b766 n/a (libc.so.6 + 0x82766)
                #1  0x00007f1bf769e294 pthread_cond_timedwait (libc.so.6 + 0x85294)
                #2  0x00007f1bf84eb754 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xeb754)
                #3  0x00007f1bf84e82f7 n/a (libQt5Core.so.5 + 0xe82f7)
                #4  0x00007f1bf84e432a n/a (libQt5Core.so.5 + 0xe432a)
                #5  0x00007f1bf769ebb5 n/a (libc.so.6 + 0x85bb5)
                #6  0x00007f1bf7720d90 n/a (libc.so.6 + 0x107d90)
                
                Stack trace of thread 2128:
                #0  0x00007f1bf77139df __poll (libc.so.6 + 0xfa9df)
                #1  0x00007f1bf636dc2f n/a (libglib-2.0.so.0 + 0xacc2f)
                #2  0x00007f1bf63150e2 g_main_context_iteration (libglib-2.0.so.0 + 0x540e2)
                #3  0x00007f1bf86d8c6c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2d8c6c)
                #4  0x00007f1bf86866ec _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2866ec)
                #5  0x00007f1bf84e725f _ZN7QThread4execEv (libQt5Core.so.5 + 0xe725f)
                #6  0x00007f1bf94c00e0 n/a (libQt5Qml.so.5 + 0x2c00e0)
                #7  0x00007f1bf84e432a n/a (libQt5Core.so.5 + 0xe432a)
                #8  0x00007f1bf769ebb5 n/a (libc.so.6 + 0x85bb5)
                #9  0x00007f1bf7720d90 n/a (libc.so.6 + 0x107d90)
                ELF object binary architecture: AMD x86-64

Failed to open /var/lib/systemd/coredump/core.kwin_wayland.1000.9441289aa7524f7783644aab8afb54ae.1907.1678556484000000.zst: Permission denied
Comment 7 Doug 2023-03-11 17:56:49 UTC
I do think there's some relation to display scale.  It won't allow me to start the session at 150% scale, but if I set it to 100% and reboot it is starting fine.  I can then change it to 150%.
Comment 8 Nate Graham 2023-03-13 14:38:01 UTC
Thanks, getting there. We're still missing debug symbols for kwin, and we need a backtrace of just the crashing thread, not a full stacktrace of everything. Can you install debug symbols for KWin, re-read https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl, and follow the instructions there exactly?

Thanks again!
Comment 9 Doug 2023-03-17 00:40:04 UTC
OK, here it is, I think. 

coredumpctl gdb 1907                                                                                                                         ✔ 
           PID: 1907 (kwin_wayland)
           UID: 1000 (doug)
           GID: 1000 (doug)
        Signal: 6 (ABRT)
     Timestamp: Sat 2023-03-11 12:41:24 EST (5 days ago)
  Command Line: /usr/bin/kwin_wayland --wayland-fd 7 --socket wayland-0 --xwayland-fd 8 --xwayland-fd 9 --xwayland-display :1 --xwayland-xauthority /run/user/1000/xauth_YKfrLf --xwayland
    Executable: /usr/bin/kwin_wayland
 Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kwin_wayland.service
          Unit: user@1000.service
     User Unit: plasma-kwin_wayland.service
         Slice: user-1000.slice
     Owner UID: 1000 (doug)
       Boot ID: 9441289aa7524f7783644aab8afb54ae
    Machine ID: cf812b87541a48de95d492dd3b54a43d
      Hostname: douglas-home
       Storage: /var/lib/systemd/coredump/core.kwin_wayland.1000.9441289aa7524f7783644aab8afb54ae.1907.1678556484000000.zst (missing)
       Message: Process 1907 (kwin_wayland) of user 1000 dumped core.
                
                Stack trace of thread 1907:
                #0  0x00007f1bf76a08ec n/a (libc.so.6 + 0x878ec)
                #1  0x00007f1bf7651ea8 raise (libc.so.6 + 0x38ea8)
                #2  0x00007f1bf763b53d abort (libc.so.6 + 0x2253d)
                #3  0x00007f1bf978bc8e n/a (libepoxy.so.0 + 0xbfc8e)
                #4  0x00007f1bf978f52a n/a (libepoxy.so.0 + 0xc352a)
                #5  0x00007f1bfa22bc97 n/a (libkwin.so.5 + 0x42bc97)
                #6  0x00007f1bfa22db39 _ZN4KWin9EglDmabufD1Ev (libkwin.so.5 + 0x42db39)
                #7  0x00007f1bfa22f091 _ZN4KWin18AbstractEglBackendD2Ev (libkwin.so.5 + 0x42f091)
                #8  0x00007f1bfa16c84d n/a (libkwin.so.5 + 0x36c84d)
                #9  0x00007f1bf9fbed6b _ZN4KWin10Compositor4stopEv (libkwin.so.5 + 0x1bed6b)
                #10 0x00007f1bf9fb7ae8 _ZN4KWin10Compositor12reinitializeEv (libkwin.so.5 + 0x1b7ae8)
                #11 0x00007f1bf86bea71 n/a (libQt5Core.so.5 + 0x2bea71)
                #12 0x00007f1bfa10ac7a _ZN4KWin9Workspace15slotReconfigureEv (libkwin.so.5 + 0x30ac7a)
                #13 0x00007f1bf86bea71 n/a (libQt5Core.so.5 + 0x2bea71)
                #14 0x00007f1bf86c0fcf _ZN6QTimer7timeoutENS_14QPrivateSignalE (libQt5Core.so.5 + 0x2c0fcf)
                #15 0x00007f1bf86b1b56 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2b1b56)
                #16 0x00007f1bf7d78b5c _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x178b5c)
                #17 0x00007f1bf868df48 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x28df48)
                #18 0x00007f1bf86d84b3 _ZN14QTimerInfoList14activateTimersEv (libQt5Core.so.5 + 0x2d84b3)
                #19 0x00007f1bf86d8962 _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2d8962)
                #20 0x0000558dd03855f2 n/a (kwin_wayland + 0x1335f2)
                #21 0x00007f1bf86866ec _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2866ec)
                #22 0x00007f1bf8691219 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x291219)
                #23 0x0000558dd02a2242 n/a (kwin_wayland + 0x50242)
                #24 0x00007f1bf763c790 n/a (libc.so.6 + 0x23790)
                #25 0x00007f1bf763c84a __libc_start_main (libc.so.6 + 0x2384a)
                #26 0x0000558dd02a3e95 n/a (kwin_wayland + 0x51e95)
Comment 10 Nate Graham 2023-03-27 18:47:19 UTC
After you run `coredumpctl gdb 1907` you need to enter `bt`
Comment 11 Bug Janitor Service 2023-04-11 03:45:54 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 12 Bug Janitor Service 2023-04-26 03:46:17 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!