[SOLVED] Wi-Fi Issue: Similiar Problem As Bluebriz

[perknh]

Well, right now it gives me the options of Repair
                                                              Disable

I then left-clicked Repair and then, again, for a moment, I had the list of five  of six Wi-Fi networks available to me -- mine included.

I put in my password to connect -- and nothing,  Sometimes I left-click and I get the message Wireless Networks not found in range, and sometimes I get a list of six networks, mine included, with blue bars representing their respective network strengths -- all right now at about 80% strength.

It's almost 7:00 in the morning here, everyone is beginning to get online around this time.

And now, two minutes later, there are four networks appearing, mine included.

[MoroS]

Well, right now it gives me the options of Repair
                                                              Disable

That's not the icon I'm talking about. It's not the two network icons that are beside each other. This is the LXDE network applet, that doesn't work too well. There should be a third icon that shows up when you run the nm-applet in the terminal (to tell the truth you should even see it without the need of running nm-applet, but right now run it from the terminal do you can see the icon that shows up). Left-clicking it gives you a menu similar to this:

[perknh]

No, I've never seen that menu!  i just ran sudo mn-applet and I got this for a result:

****@bluecat:~$ sudo nm-applet
[sudo] password for ****:

(nm-applet:2187): Gtk-WARNING **: Theme directory scalable/stock of theme NoirCrystal has no size field

But, no, MoroS, I've never seen that menu of which you are speaking.

[MoroS]

Don't use sudo for running nm-applet. It's not necessary. Just run:

Code Select Expand

nm-applet
in the terminal and look for any new traybar icons apprearing. Left-clicking the new icon will give you the menu I posted.

[MoroS]

It's in the lower-right corner of the screen if you're using the default LXDE settings.

[perknh]

This is what I get:

*****@bluecat:~$ nm-applet

** (nm-applet:2318): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(nm-applet:2318): Gtk-WARNING **: Theme directory scalable/stock of theme NoirCrystal has no size field


(nm-applet:2318): libnm-glib-CRITICAL **: nm_secret_agent_register: assertion 'priv->registered == FALSE' failed

[perknh]

Okay, I'll try again.

[perknh]

I'm sorry, MoroS, but I see nothing new appearing anywhere on my screen.

I still get this message in the terminal:

*****@bluecat:~$ nm-applet

** (nm-applet:2500): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(nm-applet:2500): Gtk-WARNING **: Theme directory scalable/stock of theme NoirCrystal has no size field

[MoroS]

** (nm-applet:2500): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Ok. That's why you're not getting anything... :/ This error causes the icon not to show... I'll have to look it up before we can go any further.

[MoroS]

Ok. A couple things to check here:
1. The group list on your system:

Code Select Expand

cat /etc/group
2. DBus state:

Code Select Expand

ps aux | grep dbus

This is either a DBus connection issue or a privilege issue.

[perknh]

[spoiler]1) *****@bluecat:~$ cat /etc/group
root:x:0:
daemon:x:1:
bin:x:2:
sys:x:3:*****
adm:x:4:*****
tty:x:5:
disk:x:6:
lp:x:7:*****
mail:x:8:
news:x:9:
uucp:x:10:
man:x:12:
proxy:x:13:
kmem:x:15:
dialout:x:20:*****
fax:x:21:
voice:x:22:
cdrom:x:24:*****
floppy:x:25:*****
tape:x:26:
sudo:x:27:*****
audio:x:29:pulse,*****
dip:x:30:*****
www-data:x:33:
backup:x:34:
operator:x:37:
list:x:38:
irc:x:39:
src:x:40:
gnats:x:41:
shadow:x:42:
utmp:x:43:
video:x:44:*****
sasl:x:45:
plugdev:x:46:*****
staff:x:50:
games:x:60:
users:x:100:
libuuid:x:101:
crontab:x:102:
fuse:x:103:
avahi-autoipd:x:104:
scanner:x:105:saned
messagebus:x:106:
colord:x:107:
lpadmin:x:108:*****
ssl-cert:x:109:
bluetooth:x:110:
utempter:x:111:
Debian-exim:x:112:
mlocate:x:113:
ssh:x:114:
avahi:x:115:
netdev:x:116:
pulse:x:117:
pulse-access:x:118:
rtkit:x:119:
saned:x:120:
lightdm:x:122:
ntp:x:121:
systemd-journal:x:123:
firebird:x:124:
nogroup:x:65534:
*****:!:1000:
geoclue:x:125:
*****@bluecat:~$

2)  *****@bluecat:~$ ps aux | grep dbus
message+   655  0.0  0.0  42420  2568 ?        Ss   05:47   0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
lightdm   1219  0.0  0.0  24312   572 ?        S    05:47   0:00 /usr/bin/dbus-launch --autolaunch b85d8de0981079fb68762217504659b9 --binary-syntax --close-stderr
lightdm   1220  0.0  0.0  41560  1120 ?        Ss   05:47   0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
lightdm   1226  0.0  0.0  41560  1732 ?        S    05:47   0:00 /usr/bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork --print-address 3
*****   1279  0.0  0.0  10604   340 ?        Ss   05:47   0:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session /usr/bin/startlxde
*****    1282  0.0  0.0  24312   572 ?        S    05:47   0:00 /usr/bin/dbus-launch --exit-with-session /usr/bin/startlxde
*****    1283  0.0  0.0  41956  1524 ?        Ss   05:47   0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
*****    2959  0.0  0.0  27700   936 pts/2    R+   07:51   0:00 grep dbus
*****@bluecat:~$ [/spoiler]

[MoroS]

Ok. DBus seems to be running.

Now then, add yourself to a few more privilege groups:

Code Select Expand

sudo usermod -a -G users,netdev,messagebus your_user_name

After that reboot. Check the traybar icons after reboot. If nothing changed then fire up the terminal and run "nm-applet" again and see if a new icon appers (and the previous error message is gone).

[perknh]

Nope.  I'm afraid we get the same message:

*****@bluecat:~$ nm-applet

** (nm-applet:1554): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(nm-applet:1554): Gtk-WARNING **: Theme directory scalable/stock of theme NoirCrystal has no size field


(nm-applet:1554): nm-applet-WARNING **: Failed to register as an agent: (32) An agent with this ID is already registered for this user.

[MoroS]

One more thing: is the polkit daemon running?

Code Select Expand

ps aux | grep polkit

[perknh]

*****@bluecat:~$ ps aux | grep polkit
root       807  0.0  0.0 272592  5012 ?        Ssl  08:08   0:00 /usr/lib/policykit-1/polkitd --no-debug
*****    1358  0.0  0.0 247572  5628 ?        Sl   08:08   0:00 /usr/bin/lxpolkit
*****    1659  0.0  0.0  27700   936 pts/1    S+   08:22   0:00 grep polkit
*****@bluecat:~$