Apper Software Management does not respect the system proxy configurations (/etc/sysconfig/proxy) WITH USER/PASS and the popup notifications in openSUSE check for updates periodically always show error message when try to update.
** See the error:**
"*There was a (possibly temporary) problem connecting to a software origins.
Please check the detailed error for further details.
I don’t use a proxy, so it is hard for me to check.
Given that Apper is a KDE application, it should follow the KDE proxy settings.
When I check my KDE proxy settings, they say “No proxy”, which I assume is the default. There is an option to change that to “Use system proxy configuration.”
>
>darkliz;2654692 Wrote:
>>
>> THE Temporary solution is disable Apper and use update only in Yast,
>> zypper, etc! Nooo!
>While I am with you that it should function, I can not follow this last
>sentence.
>
>I do not have Apper installed (nor Packagekit) and I am a happy YaST >
>software and zypper user.
I did the tests setting the ‘System Proxy’ and ‘KDE Proxy’ and none of them solved the problem with “407 - Authentication required”.
ps.: Others KDE applications work with Proxy smoothly.
On 2014-07-21 14:26, nrickert wrote:
>
> robin_listas;2655020 Wrote:
>> If the setting is per user, you would have to do that as root. :-?
>
> Why? I’m not seeing any obvious reason for that.
Well… network settings in network manager by default apply to the
current user only. You have to specify a system connection for a global
connection, and then you have to supply the root password.
I don’t know where the proxy settings in KDE are, in network manager or
outside, and I don’t know if they are applied to all programs, or only
to those of the user owning the session. And apper is different than
yast, I think it runs as user, and gets permissions for the actual
install via policy kit.
But if the updater runs as root, and takes settings from the session, it
would need to adjust them as that user, ie, root.
That’s a different issue. Proxy is done on top of the basic network connection, not as part of it.
And apper is different than
yast, I think it runs as user, and gets permissions for the actual
install via policy kit.
Apper runs as the user, and passes requests to packagekitd. Presumably, it could pass proxy information to packagekitd, though comment #7 seems to suggest that it doesn’t
But if the updater runs as root, and takes settings from the session, it
would need to adjust them as that user, ie, root.
>> But if the updater runs as root, and takes settings from the session, it
>> would need to adjust them as that user, ie, root.
>
> That’s what I don’t see.
Well, it stands to reason. A KDE application running as root takes
configs and settings from the settings for root, not from the user that
did “su”. I’m unsure what “KDE” does regarding “su” / “su -”
differences, though.
I notice that, for instance, in how dates are sorted in KDE apps when
used as root or as user (I don’t have a proxy to check). Or in the
language used by applications (root always in English, user in Spanish).
> I did the tests setting the ‘System Proxy’ and ‘KDE Proxy’ and none of
> them solved the problem with “407 - Authentication required”.
> ps.: Others KDE applications work with Proxy smoothly.
Try those settings as root. It is unknown if this is needed, it is what
nrickert and I are discussing about
Just do “su -” in a terminal and then call “systemsettings”, and let’s
us find if it makes a difference.
Trying with su there are an exception in X11:
“systemsettings(15581): KUniqueApplication: Cannot find the D-Bus session server: “Unable to autolaunch a dbus-daemon without a $DISPLAY for X11”
systemsettings(15580): KUniqueApplication: Pipe closed unexpectedly.”
