| Summary: | net-misc/wicd-1.7.1_beta2 breaks with sys-apps/net-tools-1.60_p201111202031570500 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Robert Cabrera <robcab666> |
| Component: | New packages | Assignee: | Thomas Kahle (RETIRED) <tomka> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | asturm, c1pher, creideiki+gentoo-bugzilla, derk.tebokkel, gbin, gottlieb, hanno, j0inty, mgorny, radek, silvio.gerli, skrattaren, xor29a |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://bugs.launchpad.net/wicd/+bug/893964 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Robert Cabrera
2011-11-22 16:19:55 UTC
I can confirm. I had the same issue reverting to previous version of net-tools resolved the problem .. I can confirm too (~amd64) Same here on my ~amd64 box. The wicd log said everything is fine, but it didn't connect with the new net-tools package. Only a downgrade helped here out. 2011/11/22 17:17:28 :: Connecting to wireless network FRITZ!Box Fon WLAN 7270 2011/11/22 17:17:29 :: Putting interface down 2011/11/22 17:17:29 :: Releasing DHCP leases... 2011/11/22 17:17:29 :: Setting false IP... 2011/11/22 17:17:29 :: Stopping wpa_supplicant 2011/11/22 17:17:29 :: Flushing the routing table... 2011/11/22 17:17:29 :: Putting interface up... 2011/11/22 17:17:31 :: Generating psk... 2011/11/22 17:17:31 :: Attempting to authenticate... 2011/11/22 17:17:33 :: Setting static IP : 192.168.178.200 2011/11/22 17:17:33 :: Setting default gateway : 192.168.178.1 2011/11/22 17:17:33 :: Verifying AP association... 2011/11/22 17:17:33 :: Attempt 1 of 10... 2011/11/22 17:17:33 :: Successfully associated. 2011/11/22 17:17:33 :: Connecting thread exiting. 2011/11/22 17:17:35 :: Sending connection attempt result Success 2011/11/22 17:17:35 :: Autoconnecting... 2011/11/22 17:17:35 :: No wired connection present, attempting to autoconnect to wireless network 2011/11/22 17:17:39 :: trying to automatically connect to...FRITZ!Box Fon WLAN 7270 2011/11/22 17:17:39 :: Connecting to wireless network FRITZ!Box Fon WLAN 7270 2011/11/22 17:17:40 :: Putting interface down 2011/11/22 17:17:40 :: Releasing DHCP leases... 2011/11/22 17:17:40 :: Setting false IP... 2011/11/22 17:17:40 :: Stopping wpa_supplicant 2011/11/22 17:17:40 :: Flushing the routing table... 2011/11/22 17:17:40 :: Putting interface up... 2011/11/22 17:17:42 :: Generating psk... 2011/11/22 17:17:42 :: Attempting to authenticate... 2011/11/22 17:17:44 :: Setting static IP : 192.168.178.200 2011/11/22 17:17:44 :: Setting default gateway : 192.168.178.1 2011/11/22 17:17:44 :: Verifying AP association... 2011/11/22 17:17:44 :: Attempt 1 of 10... 2011/11/22 17:17:44 :: Successfully associated. 2011/11/22 17:17:44 :: Connecting thread exiting. 2011/11/22 17:17:46 :: Sending connection attempt result Success Does building net-tools with USE="old-output" help? (In reply to comment #4) > Does building net-tools with USE="old-output" help? Yes setting USE="old-output" fixes the issue (In reply to comment #4) > Does building net-tools with USE="old-output" help? Yes setting USE="old-output" fixes the issue not a bug in net-tools confirmed, just got hit by that bug myself, wicd-1.7.1_beta2-r7 needs net-tools[old-output] (In reply to comment #7) > not a bug in net-tools Wicd upstream is slow, I adjusted the dep of -r7 for now. + 22 Nov 2011; Thomas Kahle <tomka@gentoo.org> wicd-1.7.1_beta2-r7.ebuild: + Fix dep on net-tools[old-output] to work around bug 391397 Hey linuxsociety@gmail.com, why did you remove everybody from CC?? Adding back, just in case. (In reply to comment #10) > Hey linuxsociety@gmail.com, why did you remove everybody from CC?? Adding back, > just in case. Didn't know that i removed everyone from list? i removed myself, in the process i had a mid-air collision, i just continued anyway, i didn't know that I did that. Hmm why do i have permission to remove people from CC list anyway?? *** Bug 391723 has been marked as a duplicate of this bug. *** *** Bug 391451 has been marked as a duplicate of this bug. *** OK, I see why people keep reporting this.
The dep
|| (
<sys-apps/net-tools-0.60_p201111202031570500
>=sys-apps/net-tools-1.60_p201111202031570500[old-output]
sys-apps/ethtool
)
does not what I want it to do.
Any suggestions how to formulate the right logic?
It should pick up sys-apps/net-tools and if that has the old-output USE flag, then it should be set. Alternatively it can use ethtool.
I'm confused.
(In reply to comment #14) > It should pick up sys-apps/net-tools and if that has the old-output USE flag, > then it should be set. Alternatively it can use ethtool. Are you sure wicd uses net-tools *or* ethtool? I suspect that people might have both ethtool and net-tools installed (hence dependency is satisfied regardless of net-tools USE-flags). Probably wicd reasons thusly: 1. If net-tools is absent, use ethtool 2. If net-tools is present, use it, broken or not I'll dig sources later (night has creeped up here) in order to investigate further. (In reply to comment #6) > (In reply to comment #4) > > Does building net-tools with USE="old-output" help? > > Yes setting USE="old-output" fixes the issue I am still having trouble. I tried adding the USE to net-tools and also tried emerging the previous version of net-tools. wicd still will not connect either using wired or wireless. If I type killall dhcpcd; dhcpcd The network does come up but only stays up for a few minutes. The network was solid two days ago. Did those of you who had success do something else, reboot, re merge wicd /etc/init.d/wicd restart et. al. I have done most if not all of those but perhaps not in the same order as you. Sure you've done right? As far as I can see, there are two solutions: 1) use older net-tools version (as described) 2) USE="old-output" emerge -1v net-tools (as described) Both worked for me as 1) did the trick before I got to this bug telling me about 2). No rebooting or wicd recompiling required. (In reply to comment #17) > Sure you've done right? As far as I can see, there are two solutions: > > 1) use older net-tools version (as described) > 2) USE="old-output" emerge -1v net-tools (as described) > > Both worked for me as 1) did the trick before I got to this bug telling me > about 2). No rebooting or wicd recompiling required. I sure hope I did them wrong. I'd be happy to be embarrassed, but have my network working. I first did the USE and then the downgrade so now I have the downgraded net-tools with the old-output USE flag (I can remove the flag if that is suggested). ajglap gottlieb # eix net-tools [U] sys-apps/net-tools Available versions: 1.60_p20090728014017-r1 1.60_p20100815160931 1.60_p20110409135728{tbz2} (~)1.60_p20110820045617{tbz2} [m](~)1.60_p201111202031570500{tbz2} **9999 {nls old-output static} Installed versions: 1.60_p20110409135728{tbz2}(05:16:08 PM 11/25/2011)(nls -static) Homepage: http://net-tools.sourceforge.net/ Description: Standard Linux networking tools (In reply to comment #18) > (In reply to comment #17) > > Sure you've done right? As far as I can see, there are two solutions: > > > > 1) use older net-tools version (as described) > > 2) USE="old-output" emerge -1v net-tools (as described) > > > > Both worked for me as 1) did the trick before I got to this bug telling me > > about 2). No rebooting or wicd recompiling required. > > I sure hope I did them wrong. I'd be happy to be embarrassed, but have my > network working. > > I first did the USE and then the downgrade so now I have the downgraded > net-tools with the old-output USE flag (I can remove the flag if that is > suggested). > ajglap gottlieb # eix net-tools > [U] sys-apps/net-tools > Available versions: 1.60_p20090728014017-r1 1.60_p20100815160931 > 1.60_p20110409135728{tbz2} (~)1.60_p20110820045617{tbz2} > [m](~)1.60_p201111202031570500{tbz2} **9999 {nls old-output static} > Installed versions: 1.60_p20110409135728{tbz2}(05:16:08 PM > 11/25/2011)(nls -static) > Homepage: http://net-tools.sourceforge.net/ > Description: Standard Linux networking tools Actually I did remove the USE flag and the downgraded version doesn't have the flag anyway (as the above eix shows). Sorry, but it is still true that the wicd fails to start the network (fails while putting the network up). (In reply to comment #15) > (In reply to comment #14) > > It should pick up sys-apps/net-tools and if that has the old-output USE flag, > > then it should be set. Alternatively it can use ethtool. > Are you sure wicd uses net-tools *or* ethtool? Yes. You can configure which external programs to use via wicd's interface. > I suspect that people might > have both ethtool and net-tools installed (hence dependency is satisfied > regardless of net-tools USE-flags). Probably wicd reasons thusly: > 1. If net-tools is absent, use ethtool > 2. If net-tools is present, use it, broken or not wicd's default is 'automatic detection' which will try to use net-tools and fail exactly if you have the latest ~arch version without the old-output useflag. > I'll dig sources later (night has creeped up here) in order to investigate > further. You don't need to. Wicd devs are half way through making a proper patch, see the attached URL. tl;dr NOTE FOR PEOPLE WHO CAME HERE BECAUSE WICD STOPPED WORKING: You have two options: -> Mask the latest version of net-tools -> Set the old-output useflag on the latest version of net-tools. -> Wait for the fixed wicd due in December. If it does not work with an older version of net-tools or the old-output flag, then you are seeing a different bug. Please open a new report. > > Are you sure wicd uses net-tools *or* ethtool? > Yes. You can configure which external programs to use via wicd's interface. Hm. I use wicd-curses and it only offers me Wired Link Detection (X) Automatic (recommended) ( ) ethtool ( ) mii-tool Selecting ethtool there doesn't help. Maybe wicd-curses lags behind and lacks something, I don't know. > wicd's default is 'automatic detection' which will try to use net-tools and > fail exactly if you have the latest ~arch version without the old-output > useflag. Thought so. Talking about > Any suggestions how to formulate the right logic? I think that the best thing we could do in ebuild (i.e. without patching sources) is to add block: !>=sys-apps/net-tools-1.60_p201111202031570500[-old-output] (In reply to comment #17) > Sure you've done right? As far as I can see, there are two solutions: > > 1) use older net-tools version (as described) > 2) USE="old-output" emerge -1v net-tools (as described) > > Both worked for me as 1) did the trick before I got to this bug telling me > about 2). No rebooting or wicd recompiling required. Update. I definite did both of those work-arounds (one at a time) and neither fixed the problem. However, the next morning, after NO changes (I had rebooted several times previously), both machines came up working reasonably well. We had guests for thanksgiving and this resulted in sever phones, ipads, and laptops added to our lan. We were nowhere near the 50 dhcp limit on the "wireless router", but perhaps there was interference. Anyway. It is much better now Changelog says: "Fix dep on net-tools[old-output] to work around bug 391397" ...but emerge -uvaDN world still wants to [ebuild N ] sys-apps/ethtool-3.0 167 kB [0] [ebuild R ] sys-apps/net-tools-1.60_p201111202031570500 USE="nls -old-output* -static" 0 kB [0] (In reply to comment #21) > Talking about > > Any suggestions how to formulate the right logic? > I think that the best thing we could do in ebuild (i.e. without patching > sources) is to add block: > !>=sys-apps/net-tools-1.60_p201111202031570500[-old-output] That solution works for me. It forces the user to add the old-output flag to net-tools, after net-tools re-emerge ethtools doesn't show up anymore in 'emerge -uvaDN world' because the wicd RDEPEND was properly fulfilled. Should be fixed in the latest addition. Please test. +*wicd-1.7.1_pre20111210 (10 Dec 2011) + + 10 Dec 2011; Thomas Kahle <tomka@gentoo.org> +wicd-1.7.1_pre20111210.ebuild, + +files/wicd-1.7.1_pre20111210-wpa-psk-hex-template.patch: + Bump to snapshot of 1.7.1 beta 3 to fix accumulated bugs like bug 391397. I can verify that sys-apps/net-tools-1.60_p201111202031570500 and net-misc/wicd-1.7.1_pre20111210 are working together now, system was subject to this bug prior to this wicd update. I did have problems with configured wireless profiles, e.g. a specific SSID configured for WPA2-PSK with saved password, the password was first blank in the profile, entering it again, saving, connect. On a separate downgrade-upgrade cycle, I saw the profile values e.g. hostname and password enclosed in '[mypassword]' hard braces, indicating a possible change or error in parsing with the new version against old profiles. If anyone else can verify this behaviour, it could be added as an einfo for the end-user. I did several downgrade-updgrade cycles thinking the new versions didn't work, but it turns out what I needed to do was fix the saved profile for that SSID. Thanks for the new versions. (In reply to comment #26) > I did have problems with configured wireless profiles, e.g. a specific SSID > configured for WPA2-PSK with saved password, the password was first blank in > the profile, entering it again, saving, connect. On a separate > downgrade-upgrade cycle, I saw the profile values e.g. hostname and password > enclosed in '[mypassword]' hard braces, indicating a possible change or error > in parsing with the new version against old profiles. I don't have many machines to try with. So it seems like old configuration is gone/unparseable after the upgrade? I added some ewarn. Thanks for the notice. ewarn "If you upgrade from 1.7.1-beta2, then saved passwords, ssids, ..." ewarn "may vanish. In case you can't recover them otherwise, please" ewarn "backup directories /var/lib/wicd/configurations and /etc/wicd" ewarn "before restarting the wicd service." (In reply to comment #26) > I saw the profile values e.g. hostname and password > enclosed in '[mypassword]' hard braces, indicating a possible change or error > in parsing with the new version against old profiles. I confirm that. Thanks for ewarn, Thomas, but I think it should be more explicit about quotes and brackets (password becomes '[password]'), and it's sufficient to edit network settings. Please follow https://bugs.launchpad.net/wicd/+bug/902753 https://bugs.gentoo.org/show_bug.cgi?id=394309 for updates on this issue. |
