Bugzilla – Bug 487092
kde default installation: kupdateapplet -- repo-non-oss valid metadata not found at specified URL(s)
Last modified: 2012-07-09 11:33:14 UTC
+++ This bug was initially created as a clone of Bug #458359 +++ kde default installation: kupdateapplet -- repo-non-oss valid metadata not found at specified URL(s) Network CD RC1 installation -> KDE4.1 install -> default system, no changes -> after installation system started from HDD and just from the start I get this error.
First it looks to me that my issue is dublicate of 458359, but my system is up to date and I still see the error message after login (see also attachment for screenshot): kupdateapplet NVIDIA Repository: [|] Valid metadata not found at specified URL(s) repo-non-oss: [|] Valid metadata not found at specified URL(s) repo-oss: [|] Valid metadata not found at specified URL(s) repo-update: [|] Valid metadata not found at specified URL(s) Could that be related due to our proxy that uses authentication? Proxy is configured via YaST2. I have also added the yast2 logs. Do you need more logs? Does kupdate applet has it's own log not included in yast2 logs? Please let me know.
Created attachment 280835 [details] Screenshot of the error
Created attachment 280836 [details] YaST2 logs
"Valid metadata not found at specified URL(s)" is reported by libzypp. Therefore it isn't a bug in kupdateapplet. Does libzypp support proxies with authentication?
It should support support proxies with authentication. I don't see an error in the yast logs, but updater AFAIK uses zypper. Maybe there... Hendrik please attach /var/log/zypper.log.
(In reply to comment #5) > It should support support proxies with authentication. > I don't see an error in the yast logs, but updater AFAIK uses zypper. Maybe > there... PackageKit with zypp back-end is the default now, we will need your /var/log/pk_backend_zypp.
Created attachment 284197 [details] /var/log/zypper.log
Created attachment 284198 [details] /var/log/pk_backend_zypp
I just have reproduced the problem and added both log files.
[zypp++] MediaCurl.cc(attachTo):625 Proxy: http://proxy.barco.com:80 [zypp++] MediaCurl.cc(attachTo):651 ~/.curlrc does not contain the proxy-user option Did you configure the authentication for proxy (does your /root/.curlrc contain the credentials?). If yes, try to copy them over to $HOME/.curlrc and try again. I suspect this is bug 227511.
Yes, proxy is propperly initialized using YaSt2 proxy configuration tool. Also updates and downloading data is working propperly, only the update applet seems to have a problem. The .curlrc file does exist for /root, but not for $HOME. I have copied it. After that the initial error when starting KDE desktop seems to be gone, but when doing a right click on the update applet and choosing 'update now' error still occurs.
(In reply to comment #11) > I have copied it. After that the initial error when starting KDE desktop seems > to be gone, but when doing a right click on the update applet and choosing > 'update now' error still occurs. Can you attach the pk_backend_zypp from doing the "update now" after copying the .curlrc to $HOME?
Created attachment 284952 [details] new log file: /var/log/pk_backend_zypp
I have verified this morning: When booting PC and starting KDE hte error popup didn't appear anymore (with that .curlrc in $HOME). But when triggering 'check now' manualy, error still appears. New bk_backend_zypp added (this time as gzip).
Thanx. Hm, still the same error, indeed. Can you please attach the .curlrc file (replace the password with a few *** chars)?
Created attachment 285027 [details] $HOME/.curlrc
added
Seems alright... I can reproduce it on my machine, too. Seems like PackageKit resets the $HOME env. variable. Libzypp needs it to locate $HOME/.curlrc in which the username:password is stored. Thomas, can you please check this?
It seems this happens with the zypp backend, too. So this bug will have to do something with the old bug 227511 at last.
This morning the problem accoured again directly after reboot. I don't know if that has to do with available updates. Anyhow, I have not changed by setup (i.e. $HOME/.curlrc is still there).
It could take up to 45 minutes after booting PC until the error message box appears.
(In reply to comment #18) > Seems like PackageKit resets the $HOME env. variable. Libzypp needs it to > locate $HOME/.curlrc in which the username:password is stored. > Thomas, can you please check this? The PackageKit deamon runs as root. I guess that's the reason why the user's environment isn't available. Did you try to write the settings to /root/.curlrc ?
That's not the point. The point is the $HOME variable is not defined. Whether root or non-root, that's less important. Can you check this?
(In reply to comment #23) > That's not the point. The point is the $HOME variable is not defined. Whether > root or non-root, that's less important. Can you check this? That's very PackageKit specific. I guess packagekit maintainers know details about the PackgeKit's environment.
Gnome maintainers, can you please tell me whether the PackageKit with ZYpp backend gets the user's $HOME env var? ZYpp needs it to get location of file with proxy credentials ($HOME/.curlrc). @Thomas: can you check what is the situation with $HOME when zypper backend is used? (bug 227511 - please reply there).
ping gnome.maintainers
Scott, you'd be the best one to answer this...
See question in comment 5.
There's no intention to provide an update for that project any longer. Sorry. We suggest to upgrade to a newer openSUSE version.