David C. Rankin wrote:
Wireless is flawless. AP is about 20 ft. + 1 wall from the laptop. Doing the wireless config manually, each step is instantaneous. It's looking like 10+15+dbus+something screwy with "on cable connect" is the culprit.
--- Hope you find it -- am sorta at the end of my ideas since I don't run wireless. Though, as for the 10+15 coincidence -- I've seen things like that turn out to be red-herrings about 35-40% of the time with the numbers just happened to be the same as ones used somewhere else. So I wouldn't be too overfocused on the source for those 2 numbers. It would be useful if you could trace what the chain of actions was from the time you plugged it in, through 'what' actions in udev, and if it is really calling out the dhcp the way we think it is--... If nothing else, would resort to inserting print's or adding something like: [[ -n ${DEBUG:-} || -O /tmp/debug_local ]] && { echo "(${#BASH_LINENO[@]})entering $BASH_SOURCE..." >&2; [[ -O /tmp/debug_local ]] && source /tmp/debug_local ; } to spots in the script(s) that drive things, That way you could toggle debugging by creating a tmp file that has to be owned by you... ;-) Sprinkled statements like that throughout my login scripts to find where hang-ups/problems were. If you can't see stderr, append it to a tmpfile (>>/tmp/log )... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org