When I am in system settings and choose "Colors" and then press the "Get New Schemes..." button, system settings hangs. The window stop responding to input and does not repaint itself. Even waiting a long time does not help. I have to kill it. After some discussion on the OpenSUSE forums, it seems this is somehow related to being behind a proxy, but every other aspect of using the proxied connection is working. Reproducible: Always Steps to Reproduce: 1.Go to System Settings 2.Select Color 3.Click Get New Schemes or Upload Scheme Actual Results: System Settings freezes. I have to kill system settings. I can still use Suse. Expected Results: Relevant Window opens. I have tried starting system settings from the command line, here is the output up to the hang: ----------8<----------8<----------8<----------8<---------- cristiano@xmper8q3:~> systemsettings5 kf5.kservice.sycoca: Trying to open ksycoca from "/home/cristiano/.cache/ksycoca5" checking permissions of "/usr/share/color-schemes/Breeze.colors" Invalid framesize. knewstuff: Initializing KNS3::Engine from ' "colorschemes.knsrc" ' No frame loaded No frame loaded No frame loaded knewstuff: Loading KNewStuff3 config: "colorschemes.knsrc" knewstuff: Categories: ("KDE Color Scheme KDE4") knewstuff: Using registry file: "/home/cristiano/.local/share/knewstuff3/colorschemes.knsregistry" knewstuff: Loading KNS2 registry of files for the component: "colorschemes" The file "/home/cristiano/.local/share/knewstuff3/colorschemes.knsregistry" could not be opened. knewstuff: loading providers from "http://download.kde.org/ocs/providers.xml" knewstuff: XmlLoader::load(): url: QUrl( "http://download.kde.org/ocs/providers.xml" ) ----------8<----------8<----------8<----------8<---------- After some discussion on the OpenSUSE forums, it seems this is somehow related to being behind a proxy, but every other aspect of using the proxied connection is working. I have tried adding a web browser widget to the desktop, and then downloading the providers.xml file from there: it downloaded without problems.
Just wanted to add that this same crash happens with "Get New Widgets" too, and everything that related to the "Get Hot New Stuff" functionality. It is a major showstopper. Is there any progress, please?
Appears to be the same underlying issues I've been having with a suite of KDE apps. I issued a bug https://bugs.kde.org/show_bug.cgi?id=349586 before I've done more research and have seen all of these related proxy bugs causing hangs due to being unable to download files. Even muon-updater is failing because of this. A few other related bug reports: https://bugs.kde.org/show_bug.cgi?id=341334 https://bugs.kde.org/show_bug.cgi?id=348049
I am running OpenSUSE 13.2 tumbleweed (installed from scratch) running behind a proxy. I am using cntlm to control proxy locally. systemsettings freezes for me too when getting "Get New....."
Hi, The issue was fixed on my machine by putting the ipaddress of the proxy and adding localhost as a exception in systemsettings. If I use cntlm and set localhost as a ipaddress it does not work.
Anas, Could you be a bit more specific? Where in systemsettings are you adding localhost as an exception? and putting the ip address of the proxy etc.? I.e. which kcm/area of systemsettings are you using to enter that and into which fields? Christiano, If you follow Anas' guide are you able to get it to work behind your proxy?
Hi, Open SystemSettings 5. Click on Settings in "Network group" Select "Use manually specified proxy configuration" In HTTP Proxy: (add proxy ip address) and enter the port the proxy is running on in Port: field. Check "Use this proxy for all protocols. In Exceptions add localhost,127.0.0.1 and any other intranet exception required. Leave "Use proxy settings only for addresses in the Exceptions list unchecked. Restart the machine and try again. I am also using cntlm for Yast and firefox By the way in Chrome I have No Proxy selected and for some reason it is working. In firefox I am using "Manual proxy configuration" HTTP Proxy: localhost port: same as the port set in cntlm Check "Use this proxy server fo all protocols No proxy for localhost, 127.0.0.1 Yast proxy is set up as following: HTTP proxy URL http://localhost:port (port being the port set in cntlm) Tick "Use the same proxy for all protocols" No proxy Domains: localhost, 127.0.0.1 Proxy Authentication: (put your domain login prefixed with domain i.e. (LLLL/joeblogs) + password and if you have to login into proxy,
Created attachment 94192 [details] Proxy configuration in system settings (In reply to Jeremy Whiting from comment #5) > Christiano, > > If you follow Anas' guide are you able to get it to work behind your proxy? No, I already had a very similar setup, but it is not working for me. I am attaching a screenshot of my proxy configuration from system settings.
(In reply to Cristiano Guadagnino from comment #7) > No, I already had a very similar setup, but it is not working for me. > I am attaching a screenshot of my proxy configuration from system settings. But it was advised to enable "Use manually specified proxy configuration", you are using "Use system proxy configuration". Could it be that this commit fixes your problem? https://quickgit.kde.org/?p=kio.git&a=commit&h=2879a29090863621dec1348a1297e38c8e78e2a4 IOW, try updating to KDE Frameworks 5.15 and see if it helps. 5.15 has been submitted to Tumbleweed, it's not in the repo yet though but should be in one of the next snapshots. You could also use the KDE:Frameworks5 repo to update meanwhile. See also Bug#350890, which sounds very similar to your problem.
Wolfgang, you're right that it was advised to enable ""Use manually specified proxy configuration", but since the rest of the setup is identical I thought it wouldn't make a difference the way the proxy address is made known to the system. I may have been wrong though, since the codepath may be different. https://bugs.kde.org/show_bug.cgi?id=350890 seems exactly the problem I am experiencing. Reading that bug, it seems that the way the proxy is specified doesn't make any difference. Anyway, I'll wait until Tumbleweed updates to 5.15 and then will get back to you. Thank you! Cris
I can confirm that 5.15 fixes the bug for me.
(In reply to Cristiano Guadagnino from comment #10) > I can confirm that 5.15 fixes the bug for me. Great! Let's close this as duplicate then. *** This bug has been marked as a duplicate of bug 350890 ***