Author Topic: [SOLVED] network authentication problem  (Read 5192 times)

0 Members and 1 Guest are viewing this topic.

Offline herbie643

  • Sr. Mitglied
  • ****
  • Posts: 324
  • Branch: Unstable
  • Desktop: Xfce
  • GPU Card: Intel Mobile 4 Series Integrated Graphics Controller
  • GPU driver: free
  • Kernel: i686 3.16.7.9-1-MANJARO #1 SMP PREEMPT
  • Skill: Intermediate
Re: network authentication problem
« Reply #15 on: 15. May 2015, 22:39:15 »
Do you by chance have Wicd installed.  I remember, it's been a while, that I had the same problem and I think it might have been wicked, get it.. lol

Offline oberon

  • Core Team
  • *****
  • Posts: 3858
  • I'm nice. Be new!
  • Branch: unstable
  • Desktop: i3, Deepin, Cinnamon
  • GPU Card: Intel ValleyView Gen7
  • GPU driver: Intel
  • Kernel: 4.1 / 4.4
  • Skill: Intermediate
Re: network authentication problem
« Reply #16 on: 15. May 2015, 23:11:54 »
I have tried wicd already. Same thing there: Asking for pw, trying to connect, asking for pw again...
Sorry, I don't know how to provide any output form networkmanager, I am using the applet... ???
wicd anyway has this to say:
Code: [Select]
ERROR:dbus.connection:Exception in handler for D-Bus signal:
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 230, in maybe_handle_message
    self._handler(*args, **kwargs)
  File "/usr/share/wicd/gtk/gui.py", line 281, in handle_connection_results
    error(self.window, language[results], block=False)
KeyError: dbus.String(u'bad_pass')
« Last Edit: 15. May 2015, 23:14:33 by oberon2007 »
manjaro is addictive ::)
* manjaro-i3  * manjaro-cinnamon  * manjaro-deepin

Offline oberon

  • Core Team
  • *****
  • Posts: 3858
  • I'm nice. Be new!
  • Branch: unstable
  • Desktop: i3, Deepin, Cinnamon
  • GPU Card: Intel ValleyView Gen7
  • GPU driver: Intel
  • Kernel: 4.1 / 4.4
  • Skill: Intermediate
Re: network authentication problem
« Reply #17 on: 15. May 2015, 23:41:13 »
Right. nm-applet says
Code: [Select]
nm-applet-Message: No keyring secrets found for xxxxx/802-11-wireless-security; asking user. ;) ???
manjaro is addictive ::)
* manjaro-i3  * manjaro-cinnamon  * manjaro-deepin

Offline herbie643

  • Sr. Mitglied
  • ****
  • Posts: 324
  • Branch: Unstable
  • Desktop: Xfce
  • GPU Card: Intel Mobile 4 Series Integrated Graphics Controller
  • GPU driver: free
  • Kernel: i686 3.16.7.9-1-MANJARO #1 SMP PREEMPT
  • Skill: Intermediate
Re: network authentication problem
« Reply #18 on: 16. May 2015, 00:09:17 »
What does systemctl status NetworkManager say?

Offline Ponder

  • Held Mitglied
  • *****
  • Posts: 577
  • When in doubt, go ahead.
  • Branch: OpenRC/Stable
  • Desktop: Xfce 4.12
  • GPU Card: Intel Haswell IGP
  • GPU driver: Free
  • Kernel: Buttered
  • Skill: Intermediate
Re: network authentication problem
« Reply #19 on: 16. May 2015, 00:16:38 »
Right. nm-applet says
Code: [Select]
nm-applet-Message: No keyring secrets found for xxxxx/802-11-wireless-security; asking user. ;) ???

So is the password kept by the keyring? Do you have a keyring installed? 

Don't have any wireless on Manjaro presently, but will soon, so I'm curious about this stuff.
-- systemd free, by design --

Try Manjaro OpenRC Edition for a Poettering free experience.

Offline herbie643

  • Sr. Mitglied
  • ****
  • Posts: 324
  • Branch: Unstable
  • Desktop: Xfce
  • GPU Card: Intel Mobile 4 Series Integrated Graphics Controller
  • GPU driver: free
  • Kernel: i686 3.16.7.9-1-MANJARO #1 SMP PREEMPT
  • Skill: Intermediate
Re: network authentication problem
« Reply #20 on: 16. May 2015, 00:19:40 »
If this is any help here is my output

● NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
   Active: active (running) since Fri 2015-05-15 14:22:39 CDT; 2h 55min ago
 Main PID: 547 (NetworkManager)
   CGroup: /system.slice/NetworkManager.service
           ├─547 /usr/bin/NetworkManager --no-daemon
           └─632 /usr/bin/dhclient -d -q -sf /usr/lib/networkmanager/nm-dhcp-helper -pf /var/run/dhclient-wlp3s0.pid -lf /var/lib/NetworkManager/dhclient-6...

May 15 14:22:54 gort dhclient[692]: XMT: Info-Request on wlp3s0, interval 7500ms.
May 15 14:23:01 gort dhclient[692]: XMT: Info-Request on wlp3s0, interval 14680ms.
May 15 14:23:16 gort dhclient[692]: XMT: Info-Request on wlp3s0, interval 28210ms.
May 15 14:23:31 gort NetworkManager[547]: <warn>  (wlp3s0): DHCPv6 request timed out.
May 15 14:23:31 gort NetworkManager[547]: <info>  (wlp3s0): DHCPv6 state changed unknown -> timeout
May 15 14:23:31 gort NetworkManager[547]: <info>  (wlp3s0): canceled DHCP transaction, DHCP client pid 692
May 15 14:23:31 gort NetworkManager[547]: <info>  (wlp3s0): DHCPv6 state changed timeout -> done
May 15 14:23:31 gort NetworkManager[547]: <info>  (wlp3s0): Activation: Stage 5 of 5 (IPv6 Commit) scheduled...
May 15 14:23:31 gort NetworkManager[547]: <info>  (wlp3s0): Activation: Stage 5 of 5 (IPv6 Commit) started...
May 15 14:23:31 gort NetworkManager[547]: <info>  (wlp3s0): Activation: Stage 5 of 5 (IPv6 Commit) complete.

Offline DevCode

  • Neuling
  • *
  • Posts: 33
  • Branch: stable
  • Desktop: xfce4
  • GPU Card: r9 290
  • GPU driver: free
  • Kernel: 4.1.15
  • Skill: Intermediate
Re: network authentication problem
« Reply #21 on: 16. May 2015, 10:54:42 »
Can I get a list of your running services I still have somehow the feeling that some program is blocking your network (output of systemctl).
Other than that some people had the same issue as you but just with networkmanager itself because the wpa2 password couldn't be saved. This was because  gnome-keyring-daemon wasn't running, so you could check that too.

Offline artoo

  • OpenRC Team
  • ****
  • Posts: 2373
  • Branch: Unstable
  • Desktop: LXQT/Plasma5, openrc & eudev
  • Kernel: x86_64
  • Skill: Advanced
Re: network authentication problem
« Reply #22 on: 16. May 2015, 12:48:54 »
@artoo: Nono, I am on systemd. Anyway, removing netctl didn't help


I am sorry, I confused threads and posters, and can't be of any help with systemd stuff.

Offline oberon

  • Core Team
  • *****
  • Posts: 3858
  • I'm nice. Be new!
  • Branch: unstable
  • Desktop: i3, Deepin, Cinnamon
  • GPU Card: Intel ValleyView Gen7
  • GPU driver: Intel
  • Kernel: 4.1 / 4.4
  • Skill: Intermediate
Re: network authentication problem
« Reply #23 on: 16. May 2015, 18:39:38 »
Thank you all! Here is the output of sysctl immediately after booting into the live environment: http://pastebin.com/tjfqPKQs
I have been wondering for a while already what
Code: [Select]
● systemd-tmpfiles-setup.service                                loaded failed failed    Create Volatile Files and Directoriesmeans. ??? I have no idea what those "Volatile Files and Directories" are and couldn't find anithing about that stuff...
Could that be related to my problem?
Code: [Select]
$ gnome-keyring version
gnome-keyring: 3.16.0
is installed at least. How can I check if its running?
gksu is working in case that proves anything  ::)
« Last Edit: 16. May 2015, 18:55:58 by oberon2007 »
manjaro is addictive ::)
* manjaro-i3  * manjaro-cinnamon  * manjaro-deepin

Offline Ponder

  • Held Mitglied
  • *****
  • Posts: 577
  • When in doubt, go ahead.
  • Branch: OpenRC/Stable
  • Desktop: Xfce 4.12
  • GPU Card: Intel Haswell IGP
  • GPU driver: Free
  • Kernel: Buttered
  • Skill: Intermediate
Re: network authentication problem
« Reply #24 on: 16. May 2015, 19:39:26 »

gnome-keyring: 3.16.0[/code]is installed at least. How can I check if its running?
gksu is working in case that proves anything  ::)

Code: [Select]
# ps -A | grep keyring
  1975 pts/0    00:00:00 gnome-keyring-d
#

You need to start gnome-keyring-daemon. It shows as gnome-keyring-d when it actually running.

The Arch Wiki has info on how to start it. Mine is started from OpenRC, which doesn't apply to you.
« Last Edit: 16. May 2015, 19:43:21 by Ponder »
-- systemd free, by design --

Try Manjaro OpenRC Edition for a Poettering free experience.

Offline oberon

  • Core Team
  • *****
  • Posts: 3858
  • I'm nice. Be new!
  • Branch: unstable
  • Desktop: i3, Deepin, Cinnamon
  • GPU Card: Intel ValleyView Gen7
  • GPU driver: Intel
  • Kernel: 4.1 / 4.4
  • Skill: Intermediate
Re: network authentication problem
« Reply #25 on: 16. May 2015, 20:18:30 »
Will check that later, when I have i3x-1.03 back on my USB. At the moment I am running again i3x-1.01 on it, and with that one the wifi works flawlessly  :-\

Meanwhile more investigation: I have now compared the complete lists of packages between 01 and 03 and it makes definitely not much sense:
from 01 >> 03 I have only lost manjaro-artwork and added
Code: [Select]
flashplugin
htop
lib32-bzip2
mozilla-common
terminus-font

Of course the package versions are not identical, because 01 was built on May 7, so before that latest stable updates. But I just did an update and logged out and back in and the network is still working fine. The only thing I cannot do like this of course is reboot, because the updates will be lost in the live environment.
This is so mysterious!  :P
???
« Last Edit: 16. May 2015, 20:42:40 by oberon2007 »
manjaro is addictive ::)
* manjaro-i3  * manjaro-cinnamon  * manjaro-deepin

Offline DevCode

  • Neuling
  • *
  • Posts: 33
  • Branch: stable
  • Desktop: xfce4
  • GPU Card: r9 290
  • GPU driver: free
  • Kernel: 4.1.15
  • Skill: Intermediate
Re: network authentication problem
« Reply #26 on: 16. May 2015, 20:43:56 »
Oh I read one of your posts more carefull.
You said that wicd is asking for your pw over and over again.
That is definitly a hint that it can't find your already saved pw.
It also matches what your nm-applet says. I think it it is gnome-keyring-daemon that is not running and when I take a look at the output of systemctl I can't see it. So enabling it should correct your problem.

Offline oberon

  • Core Team
  • *****
  • Posts: 3858
  • I'm nice. Be new!
  • Branch: unstable
  • Desktop: i3, Deepin, Cinnamon
  • GPU Card: Intel ValleyView Gen7
  • GPU driver: Intel
  • Kernel: 4.1 / 4.4
  • Skill: Intermediate
Re: network authentication problem
« Reply #27 on: 16. May 2015, 20:51:38 »
I have no idea what those "Volatile Files and Directories" are and couldn't find anything about that stuff...
meanwhile I have found this: https://bbs.archlinux.org/viewtopic.php?id=196341

Just, I don't see any way of fixing this when creating an ISO with manjaro-tools.
Will open a new thread on this in the respective section ...
Anyway, can this bis connected with the network-issue - I'm afraid I don't really understand what the consequences of this journal-problem are for the system...
The 1.01 ISO (which is pre 05-08 as I said and working for wifi-authentication) does NOT give that 'volatile file...' error!
manjaro is addictive ::)
* manjaro-i3  * manjaro-cinnamon  * manjaro-deepin

Offline Ponder

  • Held Mitglied
  • *****
  • Posts: 577
  • When in doubt, go ahead.
  • Branch: OpenRC/Stable
  • Desktop: Xfce 4.12
  • GPU Card: Intel Haswell IGP
  • GPU driver: Free
  • Kernel: Buttered
  • Skill: Intermediate
Re: network authentication problem
« Reply #28 on: 16. May 2015, 21:14:53 »
I don't know much about systemd, but I do know there is some way to tell it which services you want it to start at boot up. Thre will be a list of them, probably in a text file or something similar. Find that and make sure it is starting gnome-keyring-daemon.
-- systemd free, by design --

Try Manjaro OpenRC Edition for a Poettering free experience.

Offline oberon

  • Core Team
  • *****
  • Posts: 3858
  • I'm nice. Be new!
  • Branch: unstable
  • Desktop: i3, Deepin, Cinnamon
  • GPU Card: Intel ValleyView Gen7
  • GPU driver: Intel
  • Kernel: 4.1 / 4.4
  • Skill: Intermediate
Re: network authentication problem
« Reply #29 on: 16. May 2015, 21:43:03 »
I'm back in the other live environment now.
Code: [Select]
$ gnome-keyring-daemon
gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
GPG_AGENT_INFO=/run/user/1000/keyring/gpg:0:1
I guess that means gnome-keyring-daemon IS actually running, right?
Also only now I just remembered something myself that I had mentioned in an earlier post: The same ISO on my other laptop does not have that problem!!!

edit:
Code: [Select]
$ sudo ps -A | grep keyring
 1145 pts/0    00:00:00 gnome-keyring-d
« Last Edit: 16. May 2015, 22:01:53 by oberon2007 »
manjaro is addictive ::)
* manjaro-i3  * manjaro-cinnamon  * manjaro-deepin