SUMMARY same as the summary. STEPS TO REPRODUCE 1. Enable night color 2. reboot 3. start any app/service that offer an external systray component OBSERVED RESULT The systray component of the app does not load or show EXPECTED RESULT The systray component should sow and be usable SOFTWARE/OS VERSIONS KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96 Qt Version: 5.15.3
Does it show any errors? Is the kded5 process running?
Please attach the output of "systemctl --user status plasma-kded.service"
Created attachment 151112 [details] sysctl output output of: systemctl --user status plasma-kded.service
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!
(In reply to lucamilo123123 from comment #3) > Created attachment 151112 [details] > sysctl output > > output of: > systemctl --user status plasma-kded.service
Do you have a network proxy configured in Systemsettings > Network > Settings > Proxy ?
(In reply to Nicolas Fella from comment #6) > Do you have a network proxy configured in Systemsettings > Network > > Settings > Proxy ? Yeah, I have the automatic detection of proxies enabled, even if, in fact, I don't have any in my networks. So… The option is enabled, but in my everyday use no proxy is actually used. Although the option for automatic detection is enabled.
Does changing the setting to "No Proxy" fix the issue? I think this has the same root cause as https://bugs.kde.org/show_bug.cgi?id=449984
(In reply to Nicolas Fella from comment #8) > Does changing the setting to "No Proxy" fix the issue? > > I think this has the same root cause as > https://bugs.kde.org/show_bug.cgi?id=449984 Yeah, thanks a lot!
Git commit 98cadd48c21c89b81fdeb3499a557a6551a09d8a by Nicolas Fella. Committed on 11/09/2022 at 23:21. Pushed by nicolasfella into branch 'master'. [dataengines/geolocation] Port from KIO::http_post to QNetworkAccessManager Not only does this slightly simplify the code, it also avoids a deadlock in kded when automatic proxy detection is enabled Related: bug 449984 M +1 -1 dataengines/geolocation/CMakeLists.txt M +34 -50 dataengines/geolocation/location_ip.cpp https://invent.kde.org/plasma/plasma-workspace/commit/98cadd48c21c89b81fdeb3499a557a6551a09d8a
Git commit d693026676cc6bf2b7c23e9ff4b620679cf15d10 by Nicolas Fella. Committed on 11/10/2022 at 15:46. Pushed by nicolasfella into branch 'Plasma/5.24'. [dataengines/geolocation] Port from KIO::http_post to QNetworkAccessManager Not only does this slightly simplify the code, it also avoids a deadlock in kded when automatic proxy detection is enabled Related: bug 449984 (cherry picked from commit 98cadd48c21c89b81fdeb3499a557a6551a09d8a) M +1 -1 dataengines/geolocation/CMakeLists.txt M +34 -50 dataengines/geolocation/location_ip.cpp https://invent.kde.org/plasma/plasma-workspace/commit/d693026676cc6bf2b7c23e9ff4b620679cf15d10