Description of problem: I added the medias for Cauldron & deleted the Testing & Backports-medias to make sure that Gnome would work better this time. As I upgraded via Terminal/Console I began to see "WARNING: no socket to connect to " during the upgrade-process. I thought it was just a temporary error that would go away after reboot, but it still shows up when you use urpmi to install things. Version-Release number of selected component (if applicable): 6.40-9 How reproducible: Everytime. Steps to Reproduce: 1. Open Terminal/Console. 2. Login as root (su -). 3. Type urpmi.removemedia -a & press Enter to remove all the Mageia 1-medias. 4. Do urpmi.addmedia --distrib --mirrorlist 'http://mirrors.mageia.org/api/mageia.cauldron.i586.list' & press Enter if nothing happens. 5. Then type edit-urpm-sources.pl --expert & press Enter. 6. Check all boxes except for Testing & Backports-medias. Mark them & click remove-button. 7. Now start the upgrade by typing urpmi --auto-upgrade --auto-select 8. During the upgrade-process & afterwards you'll see that message.
CC: (none) => kristoffer.grundstrom1983
Sorry, wrong of me. Step 7 should say "Now start the upgrade by typing urpmi --auto-upgrade --auto-select". My bad.
Baaaaaah! "Now start the upgrade by typing urpmi --auto-update --auto-select"!!!!!
"8. During the upgrade-process & afterwards you'll see that message." but for which packet ?
Keywords: (none) => NEEDINFO
Well it appears as soon as you do anything that involves Terminal/Console/Shell so I guess it's gnome-terminal.
I may be wrong thou.
Whiteboard: (none) => check
no answer, closing
Status: NEW => RESOLVEDResolution: (none) => INVALID
Manuel Hiebel: I'm not sure, but I think it's urpmi since the output only appears in Terminal when you use urpmi in any way so therefor REOPENING.
Status: RESOLVED => REOPENEDResolution: INVALID => (none)
Sorry about the double-post. I pressed F5 to update the page & then it asked me a bout the change I made on this bug when I reopened it.
so show us *ALL* the message.
Whiteboard: check => (none)
Yes, as soon as I can get Virtualbox working in Windows 7.
Definitively not an urpmi bug
CC: (none) => thierry.vignaudSource RPM: urpmi => aria2
Summary: Both during the upgrade to Cauldron & after upgrade via Terminal/Console you get "WARNING: no socket to connect to " in Terminal/Console when installing stuff. => aria2 spits out "WARNING: no socket to connect to " in Terminal/Console when installing stuff.
(In reply to comment #12) > Definitively not an urpmi bug So you DO see it?
No. But I know it's not an urpmi message but an aria2 one
kristoffer, where are waiting of your message...if you are not able of reproduce I close.
CC: thierry.vignaud => (none)
I do see it also some months now and yes it's seen only in terminal, i.e. running urpmi or if executing rpmdrake from command line. E.g. # urpmi.update -a WARNING: no socket to connect to WARNING: no socket to connect to $MIRRORLIST: media/core/release/media_info/20111029-200519-synthesis.hdlist.cz uuendati andmekandjat "Core Release" WARNING: no socket to connect to WARNING: no socket to connect to $MIRRORLIST: media/debug/core/release/media_info/20111029-200545-synthesis.hdlist.cz uuendati andmekandjat "Core Release Debug" WARNING: no socket to connect to andmekandja "Core Updates" on täiesti värske WARNING: no socket to connect to WARNING: no socket to connect to $MIRRORLIST: media/nonfree/release/media_info/20111027-185511-synthesis.hdlist.cz uuendati andmekandjat "Nonfree Release" WARNING: no socket to connect to andmekandja "Nonfree Updates" on täiesti värske WARNING: no socket to connect to WARNING: no socket to connect to $MIRRORLIST: media/tainted/release/media_info/20111028-165623-synthesis.hdlist.cz uuendati andmekandjat "Tainted Release"
Indeed I find some threads, sorry. :/ https://bbs.archlinux.org/viewtopic.php?id=127434 Can somebody make at upstream bug report ? http://sourceforge.net/tracker/?group_id=159897&atid=813673 Or it's time to drop the aria support in urpmi ? :)
Keywords: NEEDINFO => UPSTREAMCC: (none) => doktor5000, thierry.vignaud
From what I could understand, not aria is the culprit but gnome-keyring (or gnutls, I'm not sure as I lack any understanding in these matters).
From what i remember, this message started to appear after latest big gnutls upgrade, and was never fixed since then. First archived mentioning of this problem was here: https://www.mageia.org/pipermail/mageia-dev/2011-August/007216.html Can somebody try if those messages disappear if gnome-keyring is removed?
Unfortunately the system wants to remove half of my apps when trying to 'urpme gnome-keyring' :( I found out: This warning ("WARNING: gnome-keyring:: no socket to connect to") only occurs if you use $MIRRORLIST. When I changed my urpmi settings to a dedicated mirror (ftp.mandrivauser.de) the warning vanishes. See details here: https://forums.mageia.org/en/viewtopic.php?f=15&t=1414&p=10381#p10381 (and the next) Cauldron (KDE, 64bit) with updates as of Nov 21, 16:00 GMT+0200
CC: (none) => molch.b
Maybe it needs to be a different bug already but this is still open. Anyway, when running # urpmi drakrpm-edit-media there is constantly running message retrieved $MIRRORLIST media/core/backports_testing media_info/20110621-115117-synthesis.hdlist.cz computing md5sum of retrieved source synthesis WARNING: gnome-keyring:: no socket to connect to P.S. Mageia2 alpha1, WindowMaker installation
CC: (none) => palm_pre_stl
CC: (none) => etiennedau-site
I removed gnome-keyring package and the terminal is not spammed any longer as reported.
Hardware: i586 => All
Still present on cauldron. Removing gnome-keyring isn't an option here, wants to take 104 pkgs with it, many of which I'd like to keep (not to mention gnome-keyring is useful too).
CC: (none) => stewbintn
Keywords: (none) => USABILITYWhiteboard: (none) => Errata
Is this bug still valid?
Keywords: (none) => NEEDINFOCC: (none) => marja11
since the package was not rebuild, I would said yes
Keywords: NEEDINFO => (none)
> since the package was not rebuild, I would said yes There were two revisions for aria2, on Feb 28th and Feb 29th aria2-1.14.2-2.mga2 is the current version. If gnome-keyring is the culprit: that package had even more updates. gnome-keyring-3.4.0-1.mga2 is the last one. Or is the real culprit a third package? If so, I look over it in the comments above. Please put it in the "RPM Package:" field
@ Kristoffer @ Marek @ Florain @ Wolfgang @ Palm @ Dick @ Stew ping! is this bug still valid in current cauldron? Both aria2 and gnome-keyring have been updated since the last "me too"
I've not seen it anymore.
(In reply to comment #28) > I've not seen it anymore. @ Kristoffer @ Wolfgang @ Palm @ Dick @ Stew Please confirm, I don't want to close this bug and remove this from the errata https://wiki.mageia.org/en/Mageia_2_Errata#Aria2 and then find out many still have the problem.
(In reply to comment #29) > (In reply to comment #28) > > I've not seen it anymore. > > @ Kristoffer > @ Wolfgang > @ Palm > @ Dick > @ Stew > > Please confirm, I don't want to close this bug and remove this from the errata > https://wiki.mageia.org/en/Mageia_2_Errata#Aria2 > and then find out many still have the problem. Nope. Not for me.
(In reply to comment #30) > (In reply to comment #29) > > (In reply to comment #28) > > > I've not seen it anymore. > > > > @ Kristoffer > > @ Wolfgang > > @ Palm > > @ Dick > > @ Stew > > > > Please confirm, I don't want to close this bug and remove this from the errata > > https://wiki.mageia.org/en/Mageia_2_Errata#Aria2 > > and then find out many still have the problem. > > Nope. Not for me. Thx, Kristoffer. I would have liked to get one more confirmation. I'll close as fixed now, and wait a few days with removing this from the errata until I'm sure no one reopens this bug.
Status: REOPENED => RESOLVEDResolution: (none) => FIXED