You appear to be the only person on the planet who needs to do that to get networkmanager to work.

No one understand, ok.

My networkmanager works at system start , thats not the problem.

The problem is manually stop the service, and try to start again.

i get that if try to start dhcpcd manually.

dev: loaded udev
eth0: adding address fe80::6835:6817:c443:8549
if_addaddress6: Permission denied
wlan0: adding address fe80::486c:3a33:4040:fb7
if_addaddress6: Permission denied
no interfaces have a carrier


dev: loaded udev
eth0: adding address fe80::6835:6817:c443:8549
if_addaddress6: Permission denied
DUID 00:01:00:01:1e:6e:57:32:e4:d5:3d:ab:35:63
wlan0: IAID 3d:ab:35:63
eth0: waiting for carrier
wlan0: soliciting an IPv6 router
wlan0: rebinding lease of 192.168.1.106
wlan0: leased 192.168.1.106 for infinity
wlan0: adding route to 192.168.1.0/24
wlan0: adding default route via 192.168.1.1
forked to background, child pid 10208

It's nice that you are providing the output of some random commands, but perhaps you should:

• Tell us if you are logged in as root or not (the output of the command "id" would help).
• Show the commands that you are running to create that output.

Your problem is that you try to use together NM plus other network tools. This is useless and completely unsupported.

So, run "netconfig" as root then when asked (after having entered you hostname and domain name), chose NetworkManager, confirm and you are all set.

Do not use dhcp or dhclient anymore, all your connections will be managed by NetworkManager. Else you are sure to generate self-made problems that nobody will be able to solve.

Also, I am not sure if you do, but you should not run a desktop as root.

One million times, im on root acount.


id

uid=0(root) gid=0(root) grupos=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel)


some times i grep NetworkManager and cant kill

ps ax | grep NetworkManager


5348 ? Ssl 0:01 /usr/sbin/NetworkManager
5357 ? S 0:00 /sbin/dhclient -d -q -sf /usr/libexec/nm-dhcp-helper -pf /var/run/dhclient-wlan0.pid -lf /var/lib/NetworkManager/dhclient-102fc991-43e4-447e-a4c3-d87a2b29e9cd-wlan0.lease -cf /var/lib/NetworkManager/dhclient-wlan0.conf wlan0
10423 pts/0 S+ 0:00 grep NetworkManage


i think , to reinstall again , and start , but problem is here ever "clean install" as "ROOT"

# I switch from wicd some time ago , but i prefer if networkmanager works as spected.

when some time win and kill NetworkManager process , if try to execute on terminal

NetworkManager --> he no start
sudo /usr/sbin/NetworkManager --> then start , why ? ho god why ? IM ROOT , no need sudo to run it, but he no start without.



user --> root
desktop --> kde
runlevel --> init 4
linux --> big-smp-4.4.4

As the problem is reported to be occurring with three systems, it could be that the problem is with the access point hardware.
The AP is providing DHCP leases for an infinite period. Perhaps the AP needs the wireless signal to be lost (as would happen during a reboot) before a new connection is initiated and a new lease is requested.

It could be one of the triggers of the issue. What happens if you run KDE as a regular user (as you should anyway)?

im not test that ,i try...but im not sure, i think slackware installs as root by default.




@allend

if no networkmanager no nothing to do.
the inifinite message i get when connect and working all.

Right.

My laptop is running Slackware64-current. It's sitting downstairs while I write this, using wireless to connect to my LAN. I've used ssh to log into it from upstairs.

Hmm.

Hmm. What's in your /etc/rc.d/rc.inet1.conf file?

(FWIW, I'm running XFCE on that laptop.)

ifconfig eth0 down then igconfig the eth0 up.
it will not ask for a new pid you are stoping the networkmanager
and the pid for dhcpcd is still there.
Think about it your asking the networkmanager to create a pid that is already running.
If you use the program gui like it is made you would be doing the same thing when you disconnect
and reconnect from networkmanager.

No. During installation only a root account is created but then it's up to you to create accounts for regular users. Just run "adduser" in a terminal.

I walked downstairs and logged into my Slackware64-current laptop as root using KDE. (I actually re-booted and logged in as root.) NetworkManager worked just as if I had logged in as my normal account.

image better than a million of words.

normal user , cant stop networkmanager

http://subefotos.com/ver/?5a4dd3c311...391629694o.png


/etc/rc.d/rc.networkamanger stop


and status say is not running , but see in system monitor, process still up , and right side ..panel see wireless signals, then IS RUNNING.


1 - start as a regular user
2 - /etc/rc.d/rc.networkmanager stop
3 - open task manager and see HOW PROCESS NOT KILLED
4 - ENJOY !


Then i think when im using a restart process it fails ... because never stopped.

Random users aren't allowed to stop system daemons. The script doesn't bother to check if you have the permissions to run the script or not, so everything that it does fails but nonetheless reports "stopped". (It's a good argument that perhaps scripts in /etc/rc.d should not have global execute privileges.) /etc/rc.d/rc.networkmanager status reports that it isn't running because the random user isn't allowed to cat the pidfile, which the rest of the program interprets to mean that NetworkManager isn't running.

At this point, I'd like to know what you are trying to accomplish by running /etc/rc.d/rc.networkmanager as non-root.

Some say try to test as a normal user , and try.


Problem is using a root user conected via wireless

/etc/rc.d/rc.networkmanager restart

lost wireless connection

hard to understand this ?


if execute second time --> /etc/rc.d/rc.networkmanager restart

then lost ethernet connection

no ethernet , no wireless, no nothing.


ROOT , can STOP , START RESTART , but not working as spected.


In other hand , have , if use sudo AS ROOT , the services working...

why? ..im root , no need sudo to stop/start/restart