Bug 407970 - "Detect proxy configuration automatically" causes screen locker greeter to be stuck at starting
Summary: "Detect proxy configuration automatically" causes screen locker greeter to be...
Status: RESOLVED FIXED
Alias: None
Product: kscreenlocker
Classification: Unmaintained
Component: greeter (other bugs)
Version First Reported In: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-26 21:21 UTC by hexchain
Modified: 2022-09-19 21:55 UTC (History)
3 users (show)

See Also:
Latest Commit: 1912a8b9
Version Fixed/Implemented In: 5.26.0
Sentry Crash Report:

Attachments
GDB backtrace when kscreenlocker_greet is stuck (4.34 KB, text/x-log)
2019-05-26 21:21 UTC, hexchain 		Details
dbus-monitor output (5.59 KB, application/gzip)
2019-05-26 21:22 UTC, hexchain 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description hexchain 2019-05-26 21:21:20 UTC 
Created attachment 120330 [details]
GDB backtrace when kscreenlocker_greet is stuck

SUMMARY
If "Detect proxy configuration automatically" is set in Network->Settings->Proxy and the current network does not have any proxy configuration, kscreenlocker_greet will be stuck at starting.

Note that the screen locker wallpaper is set to "Picture of the day".

STEPS TO REPRODUCE
1. Set proxy to that option
2. Execute /usr/lib/kscreenlocker_greet

OBSERVED RESULT
The screen locks after 10+ seconds.

EXPECTED RESULT
The screen is immediately locked.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.15.5
(available in About System)
KDE Frameworks Version: 5.58.2
Qt Version: 5.12.3-2

ADDITIONAL INFORMATION
Comment 1 hexchain 2019-05-26 21:22:40 UTC 
Created attachment 120331 [details]
dbus-monitor output

A dbus-monitor output is attached. Search for "nasa.gov" for a DBus call that took 25 seconds.
Comment 2 Aleix Pol 2022-09-19 21:55:32 UTC 
I see the problem is because we were allowing the picture of the day background to access online resources and took its sweet time, blocking itself.

I see that 1912a8b9 addresses it using NoAccessNetworkAccessManagerFactory to drop internet access to the lock screen, so this should address the problem at the very least. That is for 5.26.0.