[SOLVED] rsync doesnt work on nfs shares

Ok, i have a nfs4 set up and i can copy files, delete files and move files around just fine from my desktop to my nas.
But as soon as i want to use rsync to sync directories it fails with this message:
rsync: chown "/mnt/nas/Audio/Rips/flac/Anthrax" failed: Invalid argument (22)
the user i am copying with is the very same on both systems:
[carnager@archnas ~]$ id
uid=1000(carnager) gid=100(users)
[carnager@freebox ~]$ id
uid=1000(carnager) gid=100(users)
One thing that i noticed is this:
When i do a "ls -l" on the mounted nas directory i get an output like this:
[carnager@freebox ~]$ ls -l /mnt/nas/ | tail -1
drwxr-xr-x 8 4294967294 4294967294 4096 Dec 31 18:03 Video
where it normally should show my username and group.
Any ideas?
Last edited by Rasi (2012-01-02 16:10:26)

tomk wrote:The wiki has the answer - at least for those funky numbers. Hope it solves your rsync issue.
ok, then i probably know my problem, but not how to solve it:
[carnager@freebox ~]$ sudo /etc/rc.d/nfs-common start
:: Mounting pipefs filesystem [DONE]
:: Starting rpc.idmapd daemon [FAIL]

Similar Messages

  • [SOLVED] sudo doesnt work

    Hi guys,
    I'm having the strangest issues since my last installation of archlinux. First I could not login into any tty (after entering the username, nothing happened). I could solve that by installing the util-linux package. Now I cannot use sudo.
    The user is in the group wheel (which is uncommented in sudoers). I have changed nothing in the sudoers file, here's the content:
    ## sudoers file.
    ## This file MUST be edited with the 'visudo' command as root.
    ## Failure to use 'visudo' may result in syntax or file permission errors
    ## that prevent sudo from running.
    ## See the sudoers man page for the details on how to write a sudoers file.
    ## Host alias specification
    ## Groups of machines. These may include host names (optionally with wildcards),
    ## IP addresses, network numbers or netgroups.
    # Host_Alias WEBSERVERS = www1, www2, www3
    ## User alias specification
    ## Groups of users. These may consist of user names, uids, Unix groups,
    ## or netgroups.
    # User_Alias ADMINS = millert, dowdy, mikef
    ## Cmnd alias specification
    ## Groups of commands. Often used to group related commands together.
    # Cmnd_Alias PROCESSES = /usr/bin/nice, /bin/kill, /usr/bin/renice, \
    # /usr/bin/pkill, /usr/bin/top
    ## Defaults specification
    ## You may wish to keep some of the following environment variables
    ## when running commands via sudo.
    ## Locale settings
    # Defaults env_keep += "LANG LANGUAGE LINGUAS LC_* _XKB_CHARSET"
    ## Run X applications through sudo; HOME is used to find the
    ## .Xauthority file. Note that other programs use HOME to find
    ## configuration files and this may lead to privilege escalation!
    # Defaults env_keep += "HOME"
    ## X11 resource path settings
    # Defaults env_keep += "XAPPLRESDIR XFILESEARCHPATH XUSERFILESEARCHPATH"
    ## Desktop path settings
    # Defaults env_keep += "QTDIR KDEDIR"
    ## Allow sudo-run commands to inherit the callers' ConsoleKit session
    # Defaults env_keep += "XDG_SESSION_COOKIE"
    ## Uncomment to enable special input methods. Care should be taken as
    ## this may allow users to subvert the command being run via sudo.
    # Defaults env_keep += "XMODIFIERS GTK_IM_MODULE QT_IM_MODULE QT_IM_SWITCHER"
    ## Uncomment to enable logging of a command's output, except for
    ## sudoreplay and reboot. Use sudoreplay to play back logged sessions.
    # Defaults log_output
    # Defaults!/usr/bin/sudoreplay !log_output
    # Defaults!/usr/local/bin/sudoreplay !log_output
    # Defaults!/sbin/reboot !log_output
    ## Runas alias specification
    ## User privilege specification
    root ALL=(ALL) ALL
    ## Uncomment to allow members of group wheel to execute any command
    %wheel ALL=(ALL) ALL
    ## Same thing without a password
    # %wheel ALL=(ALL) NOPASSWD: ALL
    ## Uncomment to allow members of group sudo to execute any command
    # %sudo ALL=(ALL) ALL
    ## Uncomment to allow any user to run sudo if they know the password
    ## of the user they are running the command as (root by default).
    # Defaults targetpw # Ask for the password of the target user
    # ALL ALL=(ALL) ALL # WARNING: only use this together with 'Defaults targetpw'
    ## Read drop-in files from /etc/sudoers.d
    ## (the '#' here does not indicate a comment)
    #includedir /etc/sudoers.d
    In the auth.log there are following lines which seem to be important:
    Jul 12 13:46:18 localhost sudo: PAM _pam_init_handlers: no default config /etc/pam.d/other
    Jul 12 13:46:21 localhost sudo: PAM no modules loaded for `sudo' service
    Jul 12 13:46:22 localhost sudo: pam_unix(sudo:auth): conversation failed
    Jul 12 13:46:22 localhost sudo: pam_unix(sudo:auth): auth could not identify password for [archUser]
    Jul 12 13:46:22 localhost sudo: archUser: 1 incorrect password attempt ; TTY=pts/2 ; PWD=/home/archUser; USER=root ; COMMAND=/usr/bin/pacman -Syyuu
    So I looked up the content of /etc/pam.d/sudo:
    root@arch /etc/pam.d # cat sudo
    #%PAM-1.0
    auth required pam_unix.so
    auth required pam_nologin.so
    The files pam_unix.so and pam_nologin.so are both saved in /usr/lib/security.
    I noticed that if I enter the password wrong, I need to wait one or two seconds before I can try it again (this behaviour seems to be normal). But when I enter the password correct, there is no waiting time and I can enter the pass again.
    I have no idea what to do and hope that anyone can help me to use sudo again.
    4 years ago, after installing archlinux the first time, I had not a single error. Everything worked just fine but now I get two errors at once after the installation!
    --blackdeagle
    Last edited by blackdeagle (2012-07-12 14:05:53)

    blackdeagle wrote:
    65kid wrote:
    blackdeagle wrote:Please stay away from my thread! I don't need people like you telling me to search the forums and which parameters I can use and which not!
    seriously? it is stated in multiple news, the wiki and in about every third forum thread that you shouldn't use force unless you know exactly what you are doing or you are explicitly told to use it. I don't blame you that you didn't notice this, a lot of people don't (unfortunately). But when people correct you and want to help you are like "whatever, I do what I want! go away!" ???
    And what do you think the search function is for?
    Please stay away from Arch... geez...
    Come on, do you seriously think you are the only one using the search function? Show me some threads with the solution for my issue!
    https://bbs.archlinux.org/viewtopic.php?id=143335
    https://bbs.archlinux.org/viewtopic.php?id=144079
    https://bbs.archlinux.org/viewtopic.php?id=143487
    https://bbs.archlinux.org/viewtopic.php?id=142729
    https://bbs.archlinux.org/viewtopic.php?id=142720
    https://bbs.archlinux.org/viewtopic.php?id=142941
    https://bbs.archlinux.org/viewtopic.php?id=144599

  • [SOLVED] WiFi doesnt working

    Hello,
    I am really newbie in Arch, but before that for four years used Ubuntu (and elOS, Mint etc..). This night I installed Arch (using this guide and wire (not wireless)), but still can't set up WiFi.
    So, I checked the WiFi adapter:
    [dante@arch ~]$ lspci -k | grep Net
    07:00.0 Network controller: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
    Found out its name:
    [dante@arch ~]$ iwconfig
    enp19s0 no wireless extensions.
    wlp7s0 IEEE 802.11bgn ESSID:""
    Mode:Managed Access Point: Not-Associated Tx-Power=15 dBm
    Retry short limit:7 RTS thr:off Fragment thr:off
    Power Management:off
    lo no wireless extensions.
    Set up:
    [dante@arch ~]$ sudo ip link set wlp7s0 up
    [sudo] password for dante:
    [dante@arch ~]$
    Note: My router using WPA-PSK, therefore I tried:
    [dante@arch ~]$ wpa_supplicant -B -i wlp7s0 -c <(wpa_passphrase TP-LINK_52807A K56DY4VGBQ)
    Successfully initialized wpa_supplicant
    wlp7s0: Failed to initialize driver interface
    First question: May anybody explain me this error? I checked driver using 'lspci' and found out that ath9k is used (if I understand correctly this error).
    Ok. Try another way (netctl guide). I created configuration using 'wifi-menu -o' (its name is 'Home'). Start it:
    [dante@arch ~]$ sudo netctl start Home
    [sudo] password for dante:
    Job for [email protected] failed. See 'systemctl status [email protected]' and 'journalctl -xn' for details
    Okay. Check logs:
    [dante@arch ~]$ netctl status Home
    [email protected] - Automatically generated profile by wifi-menu
    Loaded: loaded (/etc/systemd/system/[email protected]; enabled)
    Active: failed (Result: exit-code) since Вс 2014-04-13 16:53:14 UTC; 31s ago
    Docs: man:netctl.profile(5)
    Process: 4832 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
    Main PID: 4832 (code=exited, status=1/FAILURE)
    [dante@arch ~]$ journalctl -xn
    -- Logs begin at Вс 2014-04-13 05:12:58 UTC, end at Вс 2014-04-13 16:33:28 UTC.
    апр 13 16:33:18 arch dhcpcd[831]: enp19s0: if_init: Permission denied
    апр 13 16:33:22 arch dhcpcd[2912]: enp19s0: if_init: Permission denied
    апр 13 16:33:22 arch dhcpcd[835]: enp19s0: if_init: Permission denied
    апр 13 16:33:22 arch dhcpcd[831]: enp19s0: if_init: Permission denied
    апр 13 16:33:26 arch dhcpcd[831]: enp19s0: if_init: Permission denied
    апр 13 16:33:26 arch dhcpcd[835]: enp19s0: if_init: Permission denied
    апр 13 16:33:26 arch dhcpcd[2912]: enp19s0: if_init: Permission denied
    апр 13 16:33:28 arch dhcpcd[2912]: enp19s0: if_init: Permission denied
    апр 13 16:33:28 arch dhcpcd[835]: enp19s0: if_init: Permission denied
    апр 13 16:33:28 arch dhcpcd[831]: enp19s0: if_init: Permission denied
    So, in second part of logs other errors (I looked at logs in 16:54).
    Because I know that I have a PSK, I tried to encrypt the password using the 'wpa_passphrase' then to write it in configs. Here my /etc/netctl/Home:
    [dante@arch ~]Description='Automatically generated profile by wifi-menu'
    Interface=wlp7s0
    Connection=wireless
    Security=wpa
    ESSID=TP-LINK_52807A
    IP=dhcp
    Key=\"f4da2aecac4df71292291a2139c64b1a008a1d30e8c843ee68b4541ddd9a06bc
    (tried to escape \" -- ineffectually)
    Then I wrote on my local arch-forum and there I was advised Network Manager. Okay. Installed it using this manual. WiFi appeared!
    Then I change LightDM to SLiM -- WiFi disappeared. Change back, but not result. So, I googled this article. Step by step.. and edited my '.xinitr' (add 'exec dbus-launch startxfce4' instead of 'exec startxfce4'). Reboot. Great! WiFi appeared again. But after next reebot WiFi reconnect in endless loop. 'Enter the password' -- ... -- 'Enter the password' -- ... -- 'En..'.
    Only wireless internet does not work. Wired works perfectly.
    Second question:: Can anybody help me, please?
    P. S.:
    Linux arch 3.14.0-5-ARCH #1 SMP PREEMPT Fri Apr 11 21:02:33 CEST 2014 x86_64 GNU/Li
    And sorry for awful English. It's not my native language.
    Last edited by igoradamenko (2014-04-14 10:38:27)

    May be this logs will help.
    Run `journalctl -f` and then start NM. First time connecion is succesfully:
    апр 14 11:56:11 arch sudo[5416]: dante : TTY=pts/1 ; PWD=/home/dante ; USER=root ; COMMAND=/usr/bin/systemctl start NetworkManager
    апр 14 11:56:11 arch sudo[5416]: pam_unix(sudo:session): session opened for user root by dante(uid=0)
    апр 14 11:56:11 arch NetworkManager[5419]: <info> NetworkManager (version 0.9.8.8) is starting...
    апр 14 11:56:11 arch NetworkManager[5419]: <info> Read config file /etc/NetworkManager/NetworkManager.conf
    апр 14 11:56:11 arch NetworkManager[5419]: <info> WEXT support is enabled
    апр 14 11:56:11 arch NetworkManager[5419]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
    апр 14 11:56:11 arch NetworkManager[5419]: keyfile: parsing NOKIA Lumia 925 ...
    апр 14 11:56:11 arch systemd[1]: Starting Network Manager...
    апр 14 11:56:11 arch NetworkManager[5419]: keyfile: read connection 'NOKIA Lumia 925'
    апр 14 11:56:11 arch NetworkManager[5419]: keyfile: parsing TP-LINK_52807A ...
    апр 14 11:56:11 arch NetworkManager[5419]: keyfile: read connection 'TP-LINK_52807A'
    апр 14 11:56:11 arch NetworkManager[5419]: <info> monitoring kernel firmware directory '/lib/firmware'.
    апр 14 11:56:11 arch NetworkManager[5419]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:02/SNY5001:00/rfkill/rfkill0) (platform driver Sony Notebook Control Driver)
    апр 14 11:56:11 arch NetworkManager[5419]: <info> rfkill2: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.0/0000:07:00.0/ieee80211/phy0/rfkill2) (driver ath9k)
    апр 14 11:56:11 arch NetworkManager[5419]: <info> WiFi hardware radio set enabled
    апр 14 11:56:11 arch NetworkManager[5419]: <info> WiFi enabled by radio killswitch; enabled by state file
    апр 14 11:56:11 arch NetworkManager[5419]: <info> WWAN enabled by radio killswitch; enabled by state file
    апр 14 11:56:11 arch NetworkManager[5419]: <info> WiMAX enabled by radio killswitch; enabled by state file
    апр 14 11:56:11 arch NetworkManager[5419]: <info> Networking is enabled by state file
    апр 14 11:56:11 arch sudo[5416]: pam_unix(sudo:session): session closed for user root
    апр 14 11:56:11 arch systemd[1]: Started Network Manager.
    апр 14 11:56:11 arch NetworkManager[5419]: <info> (wlp7s0): using nl80211 for WiFi device control
    апр 14 11:56:11 arch NetworkManager[5419]: <info> (wlp7s0): driver supports Access Point (AP) mode
    апр 14 11:56:11 arch NetworkManager[5419]: <info> (wlp7s0): new 802.11 WiFi device (driver: 'ath9k' ifindex: 3)
    апр 14 11:56:11 arch NetworkManager[5419]: <info> (wlp7s0): exported as /org/freedesktop/NetworkManager/Devices/0
    апр 14 11:56:11 arch NetworkManager[5419]: <info> (wlp7s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
    апр 14 11:56:11 arch NetworkManager[5419]: <info> (wlp7s0): bringing up device.
    апр 14 11:56:11 arch NetworkManager[5419]: <info> (wlp7s0): preparing device.
    апр 14 11:56:11 arch NetworkManager[5419]: <info> (wlp7s0): deactivating device (reason 'managed') [2]
    апр 14 11:56:11 arch NetworkManager[5419]: <warn> failed to allocate link cache: (-26) Protocol mismatch
    апр 14 11:56:11 arch NetworkManager[5419]: <info> (enp19s0): carrier is OFF
    апр 14 11:56:11 arch NetworkManager[5419]: <info> (enp19s0): new Ethernet device (driver: 'r8169' ifindex: 2)
    апр 14 11:56:11 arch NetworkManager[5419]: <info> (enp19s0): exported as /org/freedesktop/NetworkManager/Devices/1
    апр 14 11:56:11 arch NetworkManager[5419]: <info> (enp19s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
    апр 14 11:56:11 arch NetworkManager[5419]: <info> (enp19s0): bringing up device.
    апр 14 11:56:11 arch kernel: IPv6: ADDRCONF(NETDEV_UP): wlp7s0: link is not ready
    апр 14 11:56:11 arch NetworkManager[5419]: <info> (enp19s0): preparing device.
    апр 14 11:56:11 arch NetworkManager[5419]: <info> (enp19s0): deactivating device (reason 'managed') [2]
    апр 14 11:56:11 arch NetworkManager[5419]: <info> Added default wired connection 'Проводное соединение 1' for /sys/devices/pci0000:00/0000:00:1c.5/0000:13:00.0/net/enp19s0
    апр 14 11:56:11 arch NetworkManager[5419]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
    апр 14 11:56:11 arch kernel: r8169 0000:13:00.0 enp19s0: link down
    апр 14 11:56:11 arch kernel: IPv6: ADDRCONF(NETDEV_UP): enp19s0: link is not ready
    апр 14 11:56:11 arch NetworkManager[5419]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
    апр 14 11:56:11 arch NetworkManager[5419]: <warn> Couldn't get managed objects: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.bluez was not provided by any .service files
    апр 14 11:56:11 arch NetworkManager[5419]: <info> (wlp7s0) supports 4 scan SSIDs
    апр 14 11:56:11 arch NetworkManager[5419]: <info> (wlp7s0): supplicant interface state: starting -> ready
    апр 14 11:56:11 arch NetworkManager[5419]: <info> (wlp7s0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
    апр 14 11:56:11 arch NetworkManager[5419]: <warn> Trying to remove a non-existant call id.
    апр 14 11:56:11 arch NetworkManager[5419]: <info> (wlp7s0): supplicant interface state: ready -> disconnected
    апр 14 11:56:11 arch NetworkManager[5419]: <info> (wlp7s0) supports 4 scan SSIDs
    апр 14 11:56:12 arch NetworkManager[5419]: <info> (wlp7s0): supplicant interface state: disconnected -> inactive
    апр 14 11:56:12 arch NetworkManager[5419]: <info> Auto-activating connection 'TP-LINK_52807A'.
    апр 14 11:56:12 arch NetworkManager[5419]: <info> Activation (wlp7s0) starting connection 'TP-LINK_52807A'
    апр 14 11:56:12 arch NetworkManager[5419]: <info> (wlp7s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    апр 14 11:56:12 arch NetworkManager[5419]: <info> NetworkManager state is now CONNECTING
    апр 14 11:56:12 arch NetworkManager[5419]: <info> Activation (wlp7s0) Stage 1 of 5 (Device Prepare) scheduled...
    апр 14 11:56:12 arch NetworkManager[5419]: <info> Activation (wlp7s0) Stage 1 of 5 (Device Prepare) started...
    апр 14 11:56:12 arch NetworkManager[5419]: <info> Activation (wlp7s0) Stage 2 of 5 (Device Configure) scheduled...
    апр 14 11:56:12 arch NetworkManager[5419]: <info> Activation (wlp7s0) Stage 1 of 5 (Device Prepare) complete.
    апр 14 11:56:12 arch NetworkManager[5419]: <info> Activation (wlp7s0) Stage 2 of 5 (Device Configure) starting...
    апр 14 11:56:12 arch NetworkManager[5419]: <info> (wlp7s0): device state change: prepare -> config (reason 'none') [40 50 0]
    апр 14 11:56:12 arch NetworkManager[5419]: <info> Activation (wlp7s0/wireless): connection 'TP-LINK_52807A' has security, and secrets exist. No new secrets needed.
    апр 14 11:56:12 arch NetworkManager[5419]: <info> Config: added 'ssid' value 'TP-LINK_52807A'
    апр 14 11:56:12 arch NetworkManager[5419]: <info> Config: added 'scan_ssid' value '1'
    апр 14 11:56:12 arch NetworkManager[5419]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
    апр 14 11:56:12 arch NetworkManager[5419]: <info> Config: added 'psk' value '<omitted>'
    апр 14 11:56:12 arch NetworkManager[5419]: <info> Activation (wlp7s0) Stage 2 of 5 (Device Configure) complete.
    апр 14 11:56:12 arch NetworkManager[5419]: <info> Config: set interface ap_scan to 1
    апр 14 11:56:12 arch kernel: wlp7s0: authenticate with 90:f6:52:52:80:7a
    апр 14 11:56:12 arch NetworkManager[5419]: <info> (wlp7s0): supplicant interface state: inactive -> authenticating
    апр 14 11:56:12 arch kernel: wlp7s0: send auth to 90:f6:52:52:80:7a (try 1/3)
    апр 14 11:56:12 arch kernel: wlp7s0: authenticated
    апр 14 11:56:12 arch kernel: wlp7s0: associate with 90:f6:52:52:80:7a (try 1/3)
    апр 14 11:56:12 arch NetworkManager[5419]: <info> (wlp7s0): supplicant interface state: authenticating -> associated
    апр 14 11:56:12 arch kernel: wlp7s0: RX AssocResp from 90:f6:52:52:80:7a (capab=0x431 status=0 aid=1)
    апр 14 11:56:12 arch kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp7s0: link becomes ready
    апр 14 11:56:12 arch kernel: wlp7s0: associated
    апр 14 11:56:12 arch NetworkManager[5419]: <info> (wlp7s0): supplicant interface state: associated -> group handshake
    апр 14 11:56:12 arch slim[285]: [769:921:0414/115612:ERROR:download.cc(109)] PostClientToServerMessage() failed during GetUpdates
    апр 14 11:56:12 arch NetworkManager[5419]: <info> (wlp7s0): supplicant interface state: group handshake -> completed
    апр 14 11:56:12 arch NetworkManager[5419]: <info> Activation (wlp7s0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'TP-LINK_52807A'.
    апр 14 11:56:12 arch NetworkManager[5419]: <info> Activation (wlp7s0) Stage 3 of 5 (IP Configure Start) scheduled.
    апр 14 11:56:12 arch NetworkManager[5419]: <info> Activation (wlp7s0) Stage 3 of 5 (IP Configure Start) started...
    апр 14 11:56:12 arch NetworkManager[5419]: <info> (wlp7s0): device state change: config -> ip-config (reason 'none') [50 70 0]
    апр 14 11:56:12 arch NetworkManager[5419]: <info> Activation (wlp7s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
    апр 14 11:56:12 arch NetworkManager[5419]: <info> dhclient started with pid 5425
    апр 14 11:56:12 arch NetworkManager[5419]: <info> Activation (wlp7s0) Beginning IP6 addrconf.
    апр 14 11:56:12 arch NetworkManager[5419]: <info> Activation (wlp7s0) Stage 3 of 5 (IP Configure Start) complete.
    апр 14 11:56:12 arch dhclient[5425]: Internet Systems Consortium DHCP Client 4.3.0
    апр 14 11:56:12 arch dhclient[5425]: Copyright 2004-2014 Internet Systems Consortium.
    апр 14 11:56:12 arch dhclient[5425]: All rights reserved.
    апр 14 11:56:12 arch dhclient[5425]: For info, please visit https://www.isc.org/software/dhcp/
    апр 14 11:56:12 arch dhclient[5425]:
    апр 14 11:56:12 arch NetworkManager[5419]: <info> (wlp7s0): DHCPv4 state changed nbi -> preinit
    апр 14 11:56:12 arch dhclient[5425]: Listening on LPF/wlp7s0/08:ed:b9:be:c2:fb
    апр 14 11:56:12 arch dhclient[5425]: Sending on LPF/wlp7s0/08:ed:b9:be:c2:fb
    апр 14 11:56:12 arch dhclient[5425]: Sending on Socket/fallback
    апр 14 11:56:12 arch dhclient[5425]: DHCPDISCOVER on wlp7s0 to 255.255.255.255 port 67 interval 7
    апр 14 11:56:13 arch dhclient[5425]: DHCPREQUEST on wlp7s0 to 255.255.255.255 port 67
    апр 14 11:56:13 arch dhclient[5425]: DHCPOFFER from 192.168.1.1
    апр 14 11:56:13 arch dhclient[5425]: DHCPACK from 192.168.1.1
    апр 14 11:56:13 arch dhclient[5425]: bound to 192.168.1.102 -- renewal in 2847 seconds.
    апр 14 11:56:13 arch NetworkManager[5419]: <info> (wlp7s0): DHCPv4 state changed preinit -> bound
    апр 14 11:56:13 arch NetworkManager[5419]: <info> address 192.168.1.102
    апр 14 11:56:13 arch NetworkManager[5419]: <info> prefix 24 (255.255.255.0)
    апр 14 11:56:13 arch NetworkManager[5419]: <info> gateway 192.168.1.1
    апр 14 11:56:13 arch NetworkManager[5419]: <info> nameserver '192.168.1.1'
    апр 14 11:56:13 arch NetworkManager[5419]: <info> Activation (wlp7s0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
    апр 14 11:56:13 arch NetworkManager[5419]: <info> Activation (wlp7s0) Stage 5 of 5 (IPv4 Commit) started...
    апр 14 11:56:13 arch slim[285]: [769:921:0414/115613:ERROR:download.cc(109)] PostClientToServerMessage() failed during GetUpdates
    апр 14 11:56:14 arch slim[285]: [769:921:0414/115614:ERROR:download.cc(109)] PostClientToServerMessage() failed during GetUpdates
    апр 14 11:56:14 arch NetworkManager[5419]: <info> (wlp7s0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
    апр 14 11:56:14 arch NetworkManager[5419]: <info> Activation (wlp7s0) Stage 5 of 5 (IPv4 Commit) complete.
    апр 14 11:56:14 arch NetworkManager[5419]: <info> (wlp7s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
    апр 14 11:56:14 arch NetworkManager[5419]: <info> NetworkManager state is now CONNECTED_GLOBAL
    апр 14 11:56:14 arch NetworkManager[5419]: <info> Policy set 'TP-LINK_52807A' (wlp7s0) as default for IPv4 routing and DNS.
    апр 14 11:56:14 arch NetworkManager[5419]: <info> Writing DNS information to /usr/bin/resolvconf
    апр 14 11:56:14 arch NetworkManager[5419]: <info> Activation (wlp7s0) successful, device activated.
    апр 14 11:56:14 arch dbus[267]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
    апр 14 11:56:14 arch systemd[1]: Starting Network Manager Script Dispatcher Service...
    апр 14 11:56:15 arch dbus[267]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
    апр 14 11:56:15 arch systemd[1]: Started Network Manager Script Dispatcher Service.
    апр 14 11:56:33 arch NetworkManager[5419]: <info> (wlp7s0): IP6 addrconf timed out or failed.
    апр 14 11:56:33 arch NetworkManager[5419]: <info> Activation (wlp7s0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
    апр 14 11:56:33 arch NetworkManager[5419]: <info> Activation (wlp7s0) Stage 4 of 5 (IPv6 Configure Timeout) started...
    апр 14 11:56:33 arch NetworkManager[5419]: <info> Activation (wlp7s0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
    апр 14 11:56:38 arch NetworkManager[5419]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
    Reboot. No connection. Three times it tried to connect (asked the password). No result. Logs:
    апр 14 12:30:33 arch sudo[1768]: dante : TTY=pts/1 ; PWD=/home/dante ; USER=root ; COMMAND=/usr/bin/systemctl start NetworkManager
    апр 14 12:30:33 arch sudo[1768]: pam_unix(sudo:session): session opened for user root by dante(uid=0)
    апр 14 12:30:33 arch systemd[1]: Starting Network Manager...
    апр 14 12:30:33 arch NetworkManager[1771]: <info> NetworkManager (version 0.9.8.8) is starting...
    апр 14 12:30:33 arch NetworkManager[1771]: <info> Read config file /etc/NetworkManager/NetworkManager.conf
    апр 14 12:30:33 arch NetworkManager[1771]: <info> WEXT support is enabled
    апр 14 12:30:33 arch NetworkManager[1771]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
    апр 14 12:30:33 arch NetworkManager[1771]: keyfile: parsing NOKIA Lumia 925 ...
    апр 14 12:30:33 arch NetworkManager[1771]: keyfile: read connection 'NOKIA Lumia 925'
    апр 14 12:30:33 arch NetworkManager[1771]: keyfile: parsing TP-LINK_52807A ...
    апр 14 12:30:33 arch NetworkManager[1771]: keyfile: read connection 'TP-LINK_52807A'
    апр 14 12:30:33 arch NetworkManager[1771]: <info> monitoring kernel firmware directory '/lib/firmware'.
    апр 14 12:30:33 arch NetworkManager[1771]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:02/SNY5001:00/rfkill/rfkill0) (platform driver Sony Notebook Control Driver)
    апр 14 12:30:33 arch NetworkManager[1771]: <info> rfkill3: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.0/0000:07:00.0/ieee80211/phy0/rfkill3) (driver ath9k)
    апр 14 12:30:33 arch NetworkManager[1771]: <info> WiFi hardware radio set enabled
    апр 14 12:30:33 arch NetworkManager[1771]: <info> WiFi enabled by radio killswitch; enabled by state file
    апр 14 12:30:33 arch NetworkManager[1771]: <info> WWAN enabled by radio killswitch; enabled by state file
    апр 14 12:30:33 arch NetworkManager[1771]: <info> WiMAX enabled by radio killswitch; enabled by state file
    апр 14 12:30:33 arch NetworkManager[1771]: <info> Networking is enabled by state file
    апр 14 12:30:33 arch sudo[1768]: pam_unix(sudo:session): session closed for user root
    апр 14 12:30:33 arch NetworkManager[1771]: <info> (wlp7s0): using nl80211 for WiFi device control
    апр 14 12:30:33 arch NetworkManager[1771]: <info> (wlp7s0): driver supports Access Point (AP) mode
    апр 14 12:30:33 arch NetworkManager[1771]: <info> (wlp7s0): new 802.11 WiFi device (driver: 'ath9k' ifindex: 3)
    апр 14 12:30:33 arch NetworkManager[1771]: <info> (wlp7s0): exported as /org/freedesktop/NetworkManager/Devices/0
    апр 14 12:30:33 arch NetworkManager[1771]: <info> (wlp7s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
    апр 14 12:30:33 arch NetworkManager[1771]: <info> (wlp7s0): bringing up device.
    апр 14 12:30:33 arch systemd[1]: Started Network Manager.
    апр 14 12:30:33 arch NetworkManager[1771]: <info> (wlp7s0): preparing device.
    апр 14 12:30:33 arch NetworkManager[1771]: <info> (wlp7s0): deactivating device (reason 'managed') [2]
    апр 14 12:30:33 arch NetworkManager[1771]: <warn> failed to allocate link cache: (-26) Protocol mismatch
    апр 14 12:30:33 arch kernel: IPv6: ADDRCONF(NETDEV_UP): wlp7s0: link is not ready
    апр 14 12:30:33 arch NetworkManager[1771]: <info> (enp19s0): carrier is OFF
    апр 14 12:30:33 arch NetworkManager[1771]: <info> (enp19s0): new Ethernet device (driver: 'r8169' ifindex: 2)
    апр 14 12:30:33 arch NetworkManager[1771]: <info> (enp19s0): exported as /org/freedesktop/NetworkManager/Devices/1
    апр 14 12:30:33 arch NetworkManager[1771]: <info> (enp19s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
    апр 14 12:30:33 arch NetworkManager[1771]: <info> (enp19s0): bringing up device.
    апр 14 12:30:33 arch kernel: r8169 0000:13:00.0 enp19s0: link down
    апр 14 12:30:33 arch kernel: IPv6: ADDRCONF(NETDEV_UP): enp19s0: link is not ready
    апр 14 12:30:33 arch NetworkManager[1771]: <info> (enp19s0): preparing device.
    апр 14 12:30:33 arch NetworkManager[1771]: <info> (enp19s0): deactivating device (reason 'managed') [2]
    апр 14 12:30:33 arch NetworkManager[1771]: <info> Added default wired connection 'Проводное соединение 1' for /sys/devices/pci0000:00/0000:00:1c.5/0000:13:00.0/net/enp19s0
    апр 14 12:30:33 arch NetworkManager[1771]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
    апр 14 12:30:33 arch NetworkManager[1771]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
    апр 14 12:30:33 arch NetworkManager[1771]: <warn> Couldn't get managed objects: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.bluez was not provided by any .service files
    апр 14 12:30:33 arch NetworkManager[1771]: <info> (wlp7s0) supports 4 scan SSIDs
    апр 14 12:30:33 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: starting -> ready
    апр 14 12:30:33 arch NetworkManager[1771]: <info> (wlp7s0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
    апр 14 12:30:33 arch NetworkManager[1771]: <warn> Trying to remove a non-existant call id.
    апр 14 12:30:33 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: ready -> disconnected
    апр 14 12:30:33 arch NetworkManager[1771]: <info> (wlp7s0) supports 4 scan SSIDs
    апр 14 12:30:34 arch kernel: wlp7s0: authenticate with 90:f6:52:52:80:7a
    апр 14 12:30:34 arch NetworkManager[1771]: <info> Auto-activating connection 'TP-LINK_52807A'.
    апр 14 12:30:34 arch NetworkManager[1771]: <info> Activation (wlp7s0) starting connection 'TP-LINK_52807A'
    апр 14 12:30:34 arch NetworkManager[1771]: <info> (wlp7s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    апр 14 12:30:34 arch NetworkManager[1771]: <info> NetworkManager state is now CONNECTING
    апр 14 12:30:34 arch NetworkManager[1771]: <info> Activation (wlp7s0) Stage 1 of 5 (Device Prepare) scheduled...
    апр 14 12:30:34 arch NetworkManager[1771]: <info> Activation (wlp7s0) Stage 1 of 5 (Device Prepare) started...
    апр 14 12:30:34 arch NetworkManager[1771]: <info> Activation (wlp7s0) Stage 2 of 5 (Device Configure) scheduled...
    апр 14 12:30:34 arch NetworkManager[1771]: <info> Activation (wlp7s0) Stage 1 of 5 (Device Prepare) complete.
    апр 14 12:30:34 arch NetworkManager[1771]: <info> Activation (wlp7s0) Stage 2 of 5 (Device Configure) starting...
    апр 14 12:30:34 arch NetworkManager[1771]: <info> (wlp7s0): device state change: prepare -> config (reason 'none') [40 50 0]
    апр 14 12:30:34 arch NetworkManager[1771]: <info> Activation (wlp7s0/wireless): connection 'TP-LINK_52807A' has security, and secrets exist. No new secrets needed.
    апр 14 12:30:34 arch NetworkManager[1771]: <info> Config: added 'ssid' value 'TP-LINK_52807A'
    апр 14 12:30:34 arch NetworkManager[1771]: <info> Config: added 'scan_ssid' value '1'
    апр 14 12:30:34 arch NetworkManager[1771]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
    апр 14 12:30:34 arch NetworkManager[1771]: <info> Config: added 'psk' value '<omitted>'
    апр 14 12:30:34 arch NetworkManager[1771]: <info> Activation (wlp7s0) Stage 2 of 5 (Device Configure) complete.
    апр 14 12:30:34 arch NetworkManager[1771]: <info> Config: set interface ap_scan to 1
    апр 14 12:30:34 arch kernel: wlp7s0: send auth to 90:f6:52:52:80:7a (try 1/3)
    апр 14 12:30:36 arch kernel: wlp7s0: send auth to 90:f6:52:52:80:7a (try 2/3)
    апр 14 12:30:36 arch kernel: wlp7s0: authenticated
    апр 14 12:30:36 arch kernel: wlp7s0: associate with 90:f6:52:52:80:7a (try 1/3)
    апр 14 12:30:36 arch kernel: wlp7s0: RX AssocResp from 90:f6:52:52:80:7a (capab=0x431 status=0 aid=2)
    апр 14 12:30:36 arch kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp7s0: link becomes ready
    апр 14 12:30:36 arch kernel: wlp7s0: associated
    апр 14 12:30:36 arch kernel: wlp7s0: deauthenticating from 90:f6:52:52:80:7a by local choice (reason=3)
    апр 14 12:30:36 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: disconnected -> associated
    апр 14 12:30:36 arch NetworkManager[1771]: <warn> Connection disconnected (reason -3)
    апр 14 12:30:36 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: associated -> disconnected
    апр 14 12:30:36 arch NetworkManager[1771]: <warn> Connection disconnected (reason -3)
    апр 14 12:30:36 arch kernel: cfg80211: Calling CRDA to update world regulatory domain
    апр 14 12:30:36 arch kernel: cfg80211: World regulatory domain updated:
    апр 14 12:30:36 arch kernel: cfg80211: DFS Master region: unset
    апр 14 12:30:36 arch kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    апр 14 12:30:36 arch kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm)
    апр 14 12:30:36 arch kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
    апр 14 12:30:36 arch kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm)
    апр 14 12:30:36 arch kernel: cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm)
    апр 14 12:30:36 arch kernel: cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm)
    апр 14 12:30:36 arch kernel: cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm)
    апр 14 12:30:36 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: disconnected -> scanning
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: WPA: Could not verify EAPOL-Key MIC - dropping packet
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: WPA: Could not verify EAPOL-Key MIC - dropping packet
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: Authentication with 90:f6:52:52:80:7a timed out.
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-DISCONNECTED bssid=90:f6:52:52:80:7a reason=3 locally_generated=1
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="TP-LINK_52807A" auth_failures=2 duration=20
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SCAN-STARTED
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: No network configuration found for the current AP
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-DISCONNECTED bssid=90:f6:52:52:80:7a reason=3 locally_generated=1
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SCAN-STARTED
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: No network configuration found for the current AP
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-DISCONNECTED bssid=90:f6:52:52:80:7a reason=3 locally_generated=1
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SCAN-STARTED
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: SME: Trying to authenticate with 90:f6:52:52:80:7a (SSID='TP-LINK_52807A' freq=2462 MHz)
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: SME: Authentication request to the driver failed
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="TP-LINK_52807A" auth_failures=1 duration=10
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-DISCONNECTED bssid=90:f6:52:52:80:7a reason=3 locally_generated=1
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SCAN-STARTED
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SCAN-STARTED
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SCAN-STARTED
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="TP-LINK_52807A"
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: Associated with 90:f6:52:52:80:7a
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: WPA: Could not verify EAPOL-Key MIC - dropping packet
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: WPA: Could not verify EAPOL-Key MIC - dropping packet
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: Authentication with 90:f6:52:52:80:7a timed out.
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-DISCONNECTED bssid=90:f6:52:52:80:7a reason=3 locally_generated=1
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="TP-LINK_52807A" auth_failures=2 duration=20
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SCAN-STARTED
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: No network configuration found for the current AP
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-DISCONNECTED bssid=90:f6:52:52:80:7a reason=3 locally_generated=1
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SCAN-STARTED
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: No network configuration found for the current AP
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-DISCONNECTED bssid=90:f6:52:52:80:7a reason=3 locally_generated=1
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SCAN-STARTED
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: SME: Trying to authenticate with 90:f6:52:52:80:7a (SSID='TP-LINK_52807A' freq=2462 MHz)
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: Trying to associate with 90:f6:52:52:80:7a (SSID='TP-LINK_52807A' freq=2462 MHz)
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: Associated with 90:f6:52:52:80:7a
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-DISCONNECTED bssid=90:f6:52:52:80:7a reason=3 locally_generated=1
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="TP-LINK_52807A" auth_failures=1 duration=10
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="TP-LINK_52807A" auth_failures=2 duration=20
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SCAN-STARTED
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SCAN-STARTED
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SCAN-STARTED
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SCAN-STARTED
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SCAN-STARTED
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: No network configuration found for the current AP
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-DISCONNECTED bssid=90:f6:52:52:80:7a reason=3 locally_generated=1
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SCAN-STARTED
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SCAN-STARTED
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SCAN-STARTED
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SCAN-STARTED
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: SME: Trying to authenticate with 90:f6:52:52:80:7a (SSID='TP-LINK_52807A' freq=2462 MHz)
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: SME: Authentication request to the driver failed
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: SME: Trying to authenticate with 90:f6:52:52:80:7a (SSID='TP-LINK_52807A' freq=2462 MHz)
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: SME: Authentication request to the driver failed
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SCAN-STARTED
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: SME: Trying to authenticate with 90:f6:52:52:80:7a (SSID='TP-LINK_52807A' freq=2462 MHz)
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: SME: Authentication request to the driver failed
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: No network configuration found for the current AP
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-DISCONNECTED bssid=90:f6:52:52:80:7a reason=3 locally_generated=1
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SCAN-STARTED
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SCAN-STARTED
    апр 14 12:30:53 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SCAN-STARTED
    апр 14 12:30:59 arch NetworkManager[1771]: <warn> Activation (wlp7s0/wireless): association took too long.
    апр 14 12:30:59 arch NetworkManager[1771]: <info> (wlp7s0): device state change: config -> need-auth (reason 'none') [50 60 0]
    апр 14 12:30:59 arch NetworkManager[1771]: <warn> Activation (wlp7s0/wireless): asking for new secrets
    апр 14 12:30:59 arch NetworkManager[1771]: <info> Activation (wlp7s0) Stage 1 of 5 (Device Prepare) scheduled...
    апр 14 12:30:59 arch NetworkManager[1771]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
    апр 14 12:30:59 arch NetworkManager[1771]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
    апр 14 12:30:59 arch NetworkManager[1771]: <info> Activation (wlp7s0) Stage 1 of 5 (Device Prepare) started...
    апр 14 12:30:59 arch NetworkManager[1771]: <info> (wlp7s0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
    апр 14 12:30:59 arch NetworkManager[1771]: <info> Activation (wlp7s0) Stage 2 of 5 (Device Configure) scheduled...
    апр 14 12:30:59 arch NetworkManager[1771]: <info> Activation (wlp7s0) Stage 1 of 5 (Device Prepare) complete.
    апр 14 12:30:59 arch NetworkManager[1771]: <info> Activation (wlp7s0) Stage 2 of 5 (Device Configure) starting...
    апр 14 12:30:59 arch NetworkManager[1771]: <info> (wlp7s0): device state change: prepare -> config (reason 'none') [40 50 0]
    апр 14 12:30:59 arch NetworkManager[1771]: <info> Activation (wlp7s0/wireless): connection 'TP-LINK_52807A' has security, and secrets exist. No new secrets needed.
    апр 14 12:30:59 arch NetworkManager[1771]: <info> Config: added 'ssid' value 'TP-LINK_52807A'
    апр 14 12:30:59 arch NetworkManager[1771]: <info> Config: added 'scan_ssid' value '1'
    апр 14 12:30:59 arch NetworkManager[1771]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
    апр 14 12:30:59 arch NetworkManager[1771]: <info> Config: added 'psk' value '<omitted>'
    апр 14 12:30:59 arch NetworkManager[1771]: <info> Activation (wlp7s0) Stage 2 of 5 (Device Configure) complete.
    апр 14 12:30:59 arch NetworkManager[1771]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
    апр 14 12:30:59 arch NetworkManager[1771]: <info> Config: set interface ap_scan to 1
    апр 14 12:30:59 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: scanning -> authenticating
    апр 14 12:30:59 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: authenticating -> associating
    апр 14 12:30:59 arch kernel: wlp7s0: authenticate with 90:f6:52:52:80:7a
    апр 14 12:30:59 arch kernel: wlp7s0: send auth to 90:f6:52:52:80:7a (try 1/3)
    апр 14 12:30:59 arch kernel: wlp7s0: authenticated
    апр 14 12:30:59 arch kernel: wlp7s0: associate with 90:f6:52:52:80:7a (try 1/3)
    апр 14 12:30:59 arch kernel: wlp7s0: RX AssocResp from 90:f6:52:52:80:7a (capab=0x431 status=0 aid=2)
    апр 14 12:30:59 arch kernel: wlp7s0: associated
    апр 14 12:30:59 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: associating -> 4-way handshake
    апр 14 12:30:59 arch dhcpcd[718]: wlp7s0: carrier acquired
    апр 14 12:30:59 arch dhcpcd[718]: wlp7s0: IAID b9:be:c2:fb
    апр 14 12:30:59 arch dhcpcd[718]: wlp7s0: rebinding lease of 192.168.1.102
    апр 14 12:31:04 arch dhcpcd[718]: wlp7s0: leased 192.168.1.102 for 7200 seconds
    апр 14 12:31:04 arch dhcpcd[718]: wlp7s0: adding route to 192.168.1.0/24
    апр 14 12:31:04 arch dhcpcd[718]: wlp7s0: adding default route via 192.168.1.1
    апр 14 12:31:09 arch kernel: wlp7s0: deauthenticating from 90:f6:52:52:80:7a by local choice (reason=3)
    апр 14 12:31:09 arch kernel: cfg80211: Calling CRDA to update world regulatory domain
    апр 14 12:31:09 arch dhcpcd[718]: wlp7s0: carrier lost
    апр 14 12:31:09 arch NetworkManager[1771]: <warn> Connection disconnected (reason -3)
    апр 14 12:31:09 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: 4-way handshake -> disconnected
    апр 14 12:31:09 arch NetworkManager[1771]: <info> Activation (wlp7s0/wireless): disconnected during association, asking for new key.
    апр 14 12:31:09 arch NetworkManager[1771]: <info> (wlp7s0): device state change: config -> need-auth (reason 'supplicant-disconnect') [50 60 8]
    апр 14 12:31:09 arch NetworkManager[1771]: <warn> Connection disconnected (reason -3)
    апр 14 12:31:09 arch kernel: cfg80211: World regulatory domain updated:
    апр 14 12:31:09 arch kernel: cfg80211: DFS Master region: unset
    апр 14 12:31:09 arch kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    апр 14 12:31:09 arch kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm)
    апр 14 12:31:09 arch kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
    апр 14 12:31:09 arch kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm)
    апр 14 12:31:09 arch kernel: cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm)
    апр 14 12:31:09 arch kernel: cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm)
    апр 14 12:31:09 arch kernel: cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm)
    апр 14 12:31:09 arch dhcpcd[718]: wlp7s0: deleting route to 192.168.1.0/24
    апр 14 12:31:09 arch dhcpcd[718]: wlp7s0: deleting default route via 192.168.1.1
    апр 14 12:31:09 arch slim[282]: nm-applet-Message: No keyring secrets found for TP-LINK_52807A/802-11-wireless-security; asking user.
    апр 14 12:31:09 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: disconnected -> inactive
    апр 14 12:31:10 arch kernel: wlp7s0: authenticate with 90:f6:52:52:80:7a
    апр 14 12:31:10 arch kernel: wlp7s0: send auth to 90:f6:52:52:80:7a (try 1/3)
    апр 14 12:31:10 arch kernel: wlp7s0: authenticated
    апр 14 12:31:10 arch kernel: wlp7s0: associate with 90:f6:52:52:80:7a (try 1/3)
    апр 14 12:31:10 arch kernel: wlp7s0: RX AssocResp from 90:f6:52:52:80:7a (capab=0x431 status=0 aid=2)
    апр 14 12:31:10 arch kernel: wlp7s0: associated
    апр 14 12:31:10 arch kernel: wlp7s0: deauthenticating from 90:f6:52:52:80:7a by local choice (reason=3)
    апр 14 12:31:10 arch kernel: cfg80211: Calling CRDA to update world regulatory domain
    апр 14 12:31:10 arch kernel: cfg80211: World regulatory domain updated:
    апр 14 12:31:10 arch kernel: cfg80211: DFS Master region: unset
    апр 14 12:31:10 arch kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    апр 14 12:31:10 arch kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm)
    апр 14 12:31:10 arch kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
    апр 14 12:31:10 arch kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm)
    апр 14 12:31:10 arch kernel: cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm)
    апр 14 12:31:10 arch kernel: cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm)
    апр 14 12:31:10 arch kernel: cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm)
    апр 14 12:31:10 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: inactive -> associated
    апр 14 12:31:10 arch NetworkManager[1771]: <warn> Connection disconnected (reason -3)
    апр 14 12:31:10 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: associated -> disconnected
    апр 14 12:31:10 arch NetworkManager[1771]: <warn> Connection disconnected (reason -3)
    апр 14 12:31:10 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: disconnected -> inactive
    апр 14 12:31:11 arch kernel: wlp7s0: authenticate with 90:f6:52:52:80:7a
    апр 14 12:31:11 arch kernel: wlp7s0: send auth to 90:f6:52:52:80:7a (try 1/3)
    апр 14 12:31:11 arch kernel: wlp7s0: authenticated
    апр 14 12:31:11 arch kernel: wlp7s0: associate with 90:f6:52:52:80:7a (try 1/3)
    апр 14 12:31:11 arch kernel: wlp7s0: RX AssocResp from 90:f6:52:52:80:7a (capab=0x431 status=0 aid=2)
    апр 14 12:31:11 arch kernel: wlp7s0: associated
    апр 14 12:31:11 arch kernel: wlp7s0: deauthenticating from 90:f6:52:52:80:7a by local choice (reason=3)
    апр 14 12:31:11 arch kernel: cfg80211: Calling CRDA to update world regulatory domain
    апр 14 12:31:11 arch kernel: cfg80211: World regulatory domain updated:
    апр 14 12:31:11 arch kernel: cfg80211: DFS Master region: unset
    апр 14 12:31:11 arch kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    апр 14 12:31:11 arch kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm)
    апр 14 12:31:11 arch kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
    апр 14 12:31:11 arch kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm)
    апр 14 12:31:11 arch kernel: cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm)
    апр 14 12:31:11 arch kernel: cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm)
    апр 14 12:31:11 arch kernel: cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm)
    апр 14 12:31:11 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: inactive -> associated
    апр 14 12:31:11 arch NetworkManager[1771]: <warn> Connection disconnected (reason -3)
    апр 14 12:31:11 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: associated -> disconnected
    апр 14 12:31:11 arch NetworkManager[1771]: <warn> Connection disconnected (reason -3)
    апр 14 12:31:11 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: disconnected -> inactive
    апр 14 12:31:12 arch kernel: wlp7s0: authenticate with 90:f6:52:52:80:7a
    апр 14 12:31:12 arch kernel: wlp7s0: send auth to 90:f6:52:52:80:7a (try 1/3)
    апр 14 12:31:12 arch kernel: wlp7s0: authenticated
    апр 14 12:31:12 arch kernel: wlp7s0: associate with 90:f6:52:52:80:7a (try 1/3)
    апр 14 12:31:12 arch kernel: wlp7s0: RX AssocResp from 90:f6:52:52:80:7a (capab=0x431 status=0 aid=2)
    апр 14 12:31:12 arch kernel: wlp7s0: associated
    апр 14 12:31:12 arch kernel: wlp7s0: deauthenticating from 90:f6:52:52:80:7a by local choice (reason=3)
    апр 14 12:31:12 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: inactive -> associated
    апр 14 12:31:12 arch NetworkManager[1771]: <warn> Connection disconnected (reason -3)
    апр 14 12:31:12 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: associated -> disconnected
    апр 14 12:31:12 arch NetworkManager[1771]: <warn> Connection disconnected (reason -3)
    апр 14 12:31:12 arch kernel: cfg80211: Calling CRDA to update world regulatory domain
    апр 14 12:31:12 arch kernel: cfg80211: World regulatory domain updated:
    апр 14 12:31:12 arch kernel: cfg80211: DFS Master region: unset
    апр 14 12:31:12 arch kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    апр 14 12:31:12 arch kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm)
    апр 14 12:31:12 arch kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
    апр 14 12:31:12 arch kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm)
    апр 14 12:31:12 arch kernel: cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm)
    апр 14 12:31:12 arch kernel: cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm)
    апр 14 12:31:12 arch kernel: cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm)
    апр 14 12:31:12 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: disconnected -> inactive
    апр 14 12:31:16 arch NetworkManager[1771]: get_secret_flags: assertion 'is_secret_prop (setting, secret_name, error)' failed
    апр 14 12:31:16 arch NetworkManager[1771]: <info> Activation (wlp7s0) Stage 1 of 5 (Device Prepare) scheduled...
    апр 14 12:31:16 arch NetworkManager[1771]: <info> Activation (wlp7s0) Stage 1 of 5 (Device Prepare) started...
    апр 14 12:31:16 arch NetworkManager[1771]: <info> (wlp7s0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
    апр 14 12:31:16 arch NetworkManager[1771]: <info> Activation (wlp7s0) Stage 2 of 5 (Device Configure) scheduled...
    апр 14 12:31:16 arch NetworkManager[1771]: <info> Activation (wlp7s0) Stage 1 of 5 (Device Prepare) complete.
    апр 14 12:31:16 arch NetworkManager[1771]: <info> Activation (wlp7s0) Stage 2 of 5 (Device Configure) starting...
    апр 14 12:31:16 arch NetworkManager[1771]: <info> (wlp7s0): device state change: prepare -> config (reason 'none') [40 50 0]
    апр 14 12:31:16 arch NetworkManager[1771]: <info> Activation (wlp7s0/wireless): connection 'TP-LINK_52807A' has security, and secrets exist. No new secrets needed.
    апр 14 12:31:16 arch NetworkManager[1771]: <info> Config: added 'ssid' value 'TP-LINK_52807A'
    апр 14 12:31:16 arch NetworkManager[1771]: <info> Config: added 'scan_ssid' value '1'
    апр 14 12:31:16 arch NetworkManager[1771]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
    апр 14 12:31:16 arch NetworkManager[1771]: <info> Config: added 'psk' value '<omitted>'
    апр 14 12:31:16 arch NetworkManager[1771]: <info> Activation (wlp7s0) Stage 2 of 5 (Device Configure) complete.
    апр 14 12:31:16 arch NetworkManager[1771]: <info> Config: set interface ap_scan to 1
    апр 14 12:31:16 arch kernel: wlp7s0: authenticate with 90:f6:52:52:80:7a
    апр 14 12:31:16 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: inactive -> authenticating
    апр 14 12:31:16 arch kernel: wlp7s0: send auth to 90:f6:52:52:80:7a (try 1/3)
    апр 14 12:31:16 arch kernel: wlp7s0: authenticated
    апр 14 12:31:16 arch kernel: wlp7s0: associate with 90:f6:52:52:80:7a (try 1/3)
    апр 14 12:31:16 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: authenticating -> associating
    апр 14 12:31:16 arch kernel: wlp7s0: RX AssocResp from 90:f6:52:52:80:7a (capab=0x431 status=0 aid=2)
    апр 14 12:31:16 arch kernel: wlp7s0: associated
    апр 14 12:31:16 arch kernel: wlp7s0: deauthenticating from 90:f6:52:52:80:7a by local choice (reason=3)
    апр 14 12:31:16 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: associating -> associated
    апр 14 12:31:16 arch kernel: cfg80211: Calling CRDA to update world regulatory domain
    апр 14 12:31:16 arch NetworkManager[1771]: <warn> Connection disconnected (reason -3)
    апр 14 12:31:16 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: associated -> disconnected
    апр 14 12:31:16 arch kernel: cfg80211: World regulatory domain updated:
    апр 14 12:31:16 arch kernel: cfg80211: DFS Master region: unset
    апр 14 12:31:16 arch kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    апр 14 12:31:16 arch kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm)
    апр 14 12:31:16 arch kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
    апр 14 12:31:16 arch kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm)
    апр 14 12:31:16 arch kernel: cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm)
    апр 14 12:31:16 arch kernel: cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm)
    апр 14 12:31:16 arch kernel: cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm)
    апр 14 12:31:17 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: disconnected -> scanning
    апр 14 12:31:35 arch kernel: wlp7s0: authenticate with 90:f6:52:52:80:7a
    апр 14 12:31:35 arch kernel: wlp7s0: send auth to 90:f6:52:52:80:7a (try 1/3)
    апр 14 12:31:35 arch kernel: wlp7s0: authenticated
    апр 14 12:31:35 arch kernel: wlp7s0: associate with 90:f6:52:52:80:7a (try 1/3)
    апр 14 12:31:35 arch kernel: wlp7s0: RX AssocResp from 90:f6:52:52:80:7a (capab=0x431 status=0 aid=2)
    апр 14 12:31:35 arch kernel: wlp7s0: associated
    апр 14 12:31:35 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: scanning -> 4-way handshake
    апр 14 12:31:35 arch dhcpcd[718]: wlp7s0: carrier acquired
    апр 14 12:31:35 arch dhcpcd[718]: wlp7s0: IAID b9:be:c2:fb
    апр 14 12:31:35 arch dhcpcd[718]: wlp7s0: rebinding lease of 192.168.1.102
    апр 14 12:31:40 arch dhcpcd[718]: wlp7s0: leased 192.168.1.102 for 7200 seconds
    апр 14 12:31:40 arch dhcpcd[718]: wlp7s0: adding route to 192.168.1.0/24
    апр 14 12:31:40 arch dhcpcd[718]: wlp7s0: adding default route via 192.168.1.1
    апр 14 12:31:42 arch NetworkManager[1771]: <warn> Activation (wlp7s0/wireless): association took too long.
    апр 14 12:31:42 arch NetworkManager[1771]: <info> (wlp7s0): device state change: config -> need-auth (reason 'none') [50 60 0]
    апр 14 12:31:42 arch NetworkManager[1771]: <warn> Activation (wlp7s0/wireless): asking for new secrets
    апр 14 12:31:42 arch kernel: wlp7s0: deauthenticating from 90:f6:52:52:80:7a by local choice (reason=3)
    апр 14 12:31:42 arch NetworkManager[1771]: <info> Activation (wlp7s0) Stage 1 of 5 (Device Prepare) scheduled...
    апр 14 12:31:42 arch NetworkManager[1771]: <info> Activation (wlp7s0) Stage 1 of 5 (Device Prepare) started...
    апр 14 12:31:42 arch NetworkManager[1771]: <info> (wlp7s0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
    апр 14 12:31:42 arch NetworkManager[1771]: <info> Activation (wlp7s0) Stage 2 of 5 (Device Configure) scheduled...
    апр 14 12:31:42 arch NetworkManager[1771]: <info> Activation (wlp7s0) Stage 1 of 5 (Device Prepare) complete.
    апр 14 12:31:42 arch NetworkManager[1771]: <info> Activation (wlp7s0) Stage 2 of 5 (Device Configure) starting...
    апр 14 12:31:42 arch NetworkManager[1771]: <info> (wlp7s0): device state change: prepare -> config (reason 'none') [40 50 0]
    апр 14 12:31:42 arch dhcpcd[718]: wlp7s0: carrier lost
    апр 14 12:31:42 arch NetworkManager[1771]: <info> Activation (wlp7s0/wireless): connection 'TP-LINK_52807A' has security, and secrets exist. No new secrets needed.
    апр 14 12:31:42 arch NetworkManager[1771]: <info> Config: added 'ssid' value 'TP-LINK_52807A'
    апр 14 12:31:42 arch NetworkManager[1771]: <info> Config: added 'scan_ssid' value '1'
    апр 14 12:31:42 arch NetworkManager[1771]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
    апр 14 12:31:42 arch NetworkManager[1771]: <info> Config: added 'psk' value '<omitted>'
    апр 14 12:31:42 arch NetworkManager[1771]: <info> Activation (wlp7s0) Stage 2 of 5 (Device Configure) complete.
    апр 14 12:31:42 arch NetworkManager[1771]: <warn> Connection disconnected (reason -3)
    апр 14 12:31:42 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: 4-way handshake -> disconnected
    апр 14 12:31:42 arch NetworkManager[1771]: <info> Activation (wlp7s0/wireless): disconnected during association, asking for new key.
    апр 14 12:31:42 arch NetworkManager[1771]: <info> (wlp7s0): device state change: config -> need-auth (reason 'supplicant-disconnect') [50 60 8]
    апр 14 12:31:42 arch NetworkManager[1771]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
    апр 14 12:31:42 arch NetworkManager[1771]: <warn> Connection disconnected (reason -3)
    апр 14 12:31:42 arch NetworkManager[1771]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
    апр 14 12:31:42 arch NetworkManager[1771]: <info> Config: set interface ap_scan to 1
    апр 14 12:31:42 arch kernel: cfg80211: Calling CRDA to update world regulatory domain
    апр 14 12:31:42 arch kernel: cfg80211: World regulatory domain updated:
    апр 14 12:31:42 arch kernel: cfg80211: DFS Master region: unset
    апр 14 12:31:42 arch kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    апр 14 12:31:42 arch kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm)
    апр 14 12:31:42 arch kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
    апр 14 12:31:42 arch kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm)
    апр 14 12:31:42 arch kernel: cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm)
    апр 14 12:31:42 arch kernel: cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm)
    апр 14 12:31:42 arch kernel: cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm)
    апр 14 12:31:42 arch slim[282]: nm-applet-Message: No keyring secrets found for TP-LINK_52807A/802-11-wireless-security; asking user.
    апр 14 12:31:42 arch dhcpcd[718]: wlp7s0: deleting route to 192.168.1.0/24
    апр 14 12:31:42 arch dhcpcd[718]: wlp7s0: deleting default route via 192.168.1.1
    апр 14 12:31:42 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: disconnected -> scanning
    апр 14 12:31:43 arch kernel: wlp7s0: authenticate with 90:f6:52:52:80:7a
    апр 14 12:31:43 arch kernel: wlp7s0: send auth to 90:f6:52:52:80:7a (try 1/3)
    апр 14 12:31:43 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: scanning -> authenticating
    апр 14 12:31:43 arch kernel: wlp7s0: send auth to 90:f6:52:52:80:7a (try 2/3)
    апр 14 12:31:43 arch kernel: wlp7s0: authenticated
    апр 14 12:31:43 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: authenticating -> associating
    апр 14 12:31:43 arch kernel: wlp7s0: associate with 90:f6:52:52:80:7a (try 1/3)
    апр 14 12:31:43 arch kernel: wlp7s0: RX AssocResp from 90:f6:52:52:80:7a (capab=0x431 status=0 aid=2)
    апр 14 12:31:43 arch kernel: wlp7s0: associated
    апр 14 12:31:43 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: associating -> 4-way handshake
    апр 14 12:31:43 arch dhcpcd[718]: wlp7s0: carrier acquired
    апр 14 12:31:43 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: 4-way handshake -> completed
    апр 14 12:31:44 arch dhcpcd[718]: wlp7s0: IAID b9:be:c2:fb
    апр 14 12:31:44 arch dhcpcd[718]: wlp7s0: rebinding lease of 192.168.1.102
    апр 14 12:31:49 arch dhcpcd[718]: wlp7s0: leased 192.168.1.102 for 7200 seconds
    апр 14 12:31:49 arch dhcpcd[718]: wlp7s0: adding route to 192.168.1.0/24
    апр 14 12:31:49 arch dhcpcd[718]: wlp7s0: adding default route via 192.168.1.1
    апр 14 12:31:53 arch kernel: wlp7s0: deauthenticating from 90:f6:52:52:80:7a by local choice (reason=3)
    апр 14 12:31:53 arch dhcpcd[718]: wlp7s0: carrier lost
    апр 14 12:31:53 arch NetworkManager[1771]: <warn> Connection disconnected (reason -3)
    апр 14 12:31:53 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: completed -> disconnected
    апр 14 12:31:53 arch dhcpcd[718]: wlp7s0: deleting route to 192.168.1.0/24
    апр 14 12:31:53 arch dhcpcd[718]: wlp7s0: deleting default route via 192.168.1.1
    апр 14 12:31:53 arch kernel: cfg80211: Calling CRDA to update world regulatory domain
    апр 14 12:31:53 arch kernel: cfg80211: World regulatory domain updated:
    апр 14 12:31:53 arch kernel: cfg80211: DFS Master region: unset
    апр 14 12:31:53 arch kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    апр 14 12:31:53 arch kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm)
    апр 14 12:31:53 arch kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
    апр 14 12:31:53 arch kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm)
    апр 14 12:31:53 arch kernel: cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm)
    апр 14 12:31:53 arch kernel: cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm)
    апр 14 12:31:53 arch kernel: cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm)
    апр 14 12:31:54 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: disconnected -> scanning
    апр 14 12:32:01 arch NetworkManager[1771]: get_secret_flags: assertion 'is_secret_prop (setting, secret_name, error)' failed
    апр 14 12:32:01 arch NetworkManager[1771]: <info> Activation (wlp7s0) Stage 1 of 5 (Device Prepare) scheduled...
    апр 14 12:32:01 arch NetworkManager[1771]: <info> Activation (wlp7s0) Stage 1 of 5 (Device Prepare) started...
    апр 14 12:32:01 arch NetworkManager[1771]: <info> (wlp7s0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
    апр 14 12:32:01 arch NetworkManager[1771]: <info> Activation (wlp7s0) Stage 2 of 5 (Device Configure) scheduled...
    апр 14 12:32:01 arch NetworkManager[1771]: <info> Activation (wlp7s0) Stage 1 of 5 (Device Prepare) complete.
    апр 14 12:32:01 arch NetworkManager[1771]: <info> Activation (wlp7s0) Stage 2 of 5 (Device Configure) starting...
    апр 14 12:32:01 arch NetworkManager[1771]: <info> (wlp7s0): device state change: prepare -> config (reason 'none') [40 50 0]
    апр 14 12:32:01 arch NetworkManager[1771]: <info> Activation (wlp7s0/wireless): connection 'TP-LINK_52807A' has security, and secrets exist. No new secrets needed.
    апр 14 12:32:01 arch NetworkManager[1771]: <info> Config: added 'ssid' value 'TP-LINK_52807A'
    апр 14 12:32:01 arch NetworkManager[1771]: <info> Config: added 'scan_ssid' value '1'
    апр 14 12:32:01 arch NetworkManager[1771]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
    апр 14 12:32:01 arch NetworkManager[1771]: <info> Config: added 'psk' value '<omitted>'
    апр 14 12:32:01 arch NetworkManager[1771]: <info> Activation (wlp7s0) Stage 2 of 5 (Device Configure) complete.
    апр 14 12:32:01 arch NetworkManager[1771]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
    апр 14 12:32:01 arch NetworkManager[1771]: <info> Config: set interface ap_scan to 1
    апр 14 12:32:01 arch kernel: wlp7s0: authenticate with 90:f6:52:52:80:7a
    апр 14 12:32:01 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: scanning -> authenticating
    апр 14 12:32:01 arch kernel: wlp7s0: send auth to 90:f6:52:52:80:7a (try 1/3)
    апр 14 12:32:01 arch kernel: wlp7s0: authenticated
    апр 14 12:32:01 arch kernel: wlp7s0: associate with 90:f6:52:52:80:7a (try 1/3)
    апр 14 12:32:01 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: authenticating -> associating
    апр 14 12:32:01 arch kernel: wlp7s0: RX AssocResp from 90:f6:52:52:80:7a (capab=0x431 status=0 aid=2)
    апр 14 12:32:01 arch kernel: wlp7s0: associated
    апр 14 12:32:01 arch kernel: wlp7s0: deauthenticating from 90:f6:52:52:80:7a by local choice (reason=3)
    апр 14 12:32:01 arch kernel: cfg80211: Calling CRDA to update world regulatory domain
    апр 14 12:32:01 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: associating -> associated
    апр 14 12:32:01 arch kernel: cfg80211: World regulatory domain updated:
    апр 14 12:32:01 arch kernel: cfg80211: DFS Master region: unset
    апр 14 12:32:01 arch kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    апр 14 12:32:01 arch kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm)
    апр 14 12:32:01 arch kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
    апр 14 12:32:01 arch kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm)
    апр 14 12:32:01 arch kernel: cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm)
    апр 14 12:32:01 arch kernel: cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm)
    апр 14 12:32:01 arch kernel: cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm)
    апр 14 12:32:01 arch NetworkManager[1771]: <warn> Connection disconnected (reason -3)
    апр 14 12:32:01 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: associated -> disconnected
    апр 14 12:32:01 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: disconnected -> scanning
    апр 14 12:32:14 arch kernel: wlp7s0: authenticate with 90:f6:52:52:80:7a
    апр 14 12:32:14 arch kernel: wlp7s0: send auth to 90:f6:52:52:80:7a (try 1/3)
    апр 14 12:32:14 arch kernel: wlp7s0: authenticated
    апр 14 12:32:14 arch kernel: wlp7s0: associate with 90:f6:52:52:80:7a (try 1/3)
    апр 14 12:32:14 arch kernel: wlp7s0: RX AssocResp from 90:f6:52:52:80:7a (capab=0x431 status=0 aid=2)
    апр 14 12:32:14 arch kernel: wlp7s0: associated
    апр 14 12:32:14 arch NetworkManager[1771]: <info> (wlp7s0): supplicant interface state: scanning -> 4-way handshake
    апр 14 12:32:14 arch dhcpcd[718]: wlp7s0: carrier acquired
    апр 14 12:32:14 arch dhcpcd[718]: wlp7s0: IAID b9:be:c2:fb
    апр 14 12:32:14 arch dhcpcd[718]: wlp7s0: rebinding lease of 192.168.1.102
    апр 14 12:32:19 arch dhcpcd[718]: wlp7s0: leased 192.168.1.102 for 7200 seconds
    апр 14 12:32:19 arch dhcpcd[718]: wlp7s0: adding route to 192.168.1.0/24
    апр 14 12:32:19 arch dhcpcd[718]: wlp7s0: adding default route via 192.168.1.1
    апр 14 12:32:24 arch kernel: wlp7s0: deauthenticating from 90:f6:52:52:80:7a by local choice (reason=3)
    апр 14 12:32:24 arch dhcpcd[718]: wlp7s0: carrier lost
    апр 14 12:32:24 arch kernel: cfg80211: Calling CRDA to update world regulatory domain
    апр 14 12:32:24 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SCAN-STARTED
    апр 14 12:32:24 arch wpa_supplicant[264]: wlp7s0: SME: Trying to authenticate with 90:f6:52:52:80:7a (SSID='TP-LINK_52807A' freq=2462 MHz)
    апр 14 12:32:24 arch wpa_supplicant[264]: wlp7s0: Trying to associate with 90:f6:52:52:80:7a (SSID='TP-LINK_52807A' freq=2462 MHz)
    апр 14 12:32:24 arch wpa_supplicant[264]: wlp7s0: Associated with 90:f6:52:52:80:7a
    апр 14 12:32:24 arch wpa_supplicant[264]: wlp7s0: WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
    апр 14 12:32:24 arch wpa_supplicant[264]: wlp7s0: WPA: Could not verify EAPOL-Key MIC - dropping packet
    апр 14 12:32:24 arch wpa_supplicant[264]: wlp7s0: WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
    апр 14 12:32:24 arch wpa_supplicant[264]: wlp7s0: WPA: Could not verify EAPOL-Key MIC - dropping packet
    апр 14 12:32:24 arch wpa_supplicant[264]: wlp7s0: Authentication with 90:f6:52:52:80:7a timed out.
    апр 14 12:32:24 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-DISCONNECTED bssid=90:f6:52:52:80:7a reason=3 locally_generated=1
    апр 14 12:32:24 arch wpa_supplicant[264]: wlp7s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
    апр 14 12:32:24 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="TP-LINK_52807A" auth_failures=1 duration=10
    апр 14 12:32:24 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="TP-LINK_52807A" auth_failures=2 duration=20
    апр 14 12:32:24 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SCAN-STARTED
    апр 14 12:32:24 arch wpa_supplicant[264]: wlp7s0: No network configuration found for the current AP
    апр 14 12:32:24 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-DISCONNECTED bssid=90:f6:52:52:80:7a reason=3 locally_generated=1
    апр 14 12:32:24 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SCAN-STARTED
    апр 14 12:32:24 arch wpa_supplicant[264]: wlp7s0: No network configuration found for the current AP
    апр 14 12:32:24 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-DISCONNECTED bssid=90:f6:52:52:80:7a reason=3 locally_generated=1
    апр 14 12:32:24 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SCAN-STARTED
    апр 14 12:32:24 arch wpa_supplicant[264]: wlp7s0: No network configuration found for the current AP
    апр 14 12:32:24 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-DISCONNECTED bssid=90:f6:52:52:80:7a reason=3 locally_generated=1
    апр 14 12:32:24 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SCAN-STARTED
    апр 14 12:32:24 arch wpa_supplicant[264]: wlp7s0: SME: Trying to authenticate with 90:f6:52:52:80:7a (SSID='TP-LINK_52807A' freq=2462 MHz)
    апр 14 12:32:24 arch wpa_supplicant[264]: wlp7s0: Trying to associate with 90:f6:52:52:80:7a (SSID='TP-LINK_52807A' freq=2462 MHz)
    апр 14 12:32:24 arch wpa_supplicant[264]: wlp7s0: Associated with 90:f6:52:52:80:7a
    апр 14 12:32:24 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-DISCONNECTED bssid=90:f6:52:52:80:7a reason=3 locally_generated=1
    апр 14 12:32:24 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="TP-LINK_52807A" auth_failures=1 duration=10
    апр 14 12:32:24 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SCAN-STARTED
    апр 14 12:32:24 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SCAN-STARTED
    апр 14 12:32:24 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SCAN-STARTED
    апр 14 12:32:24 arch wpa_supplicant[264]: wlp7s0: CTRL-EVENT-SCAN-STARTED
    апр 14 12:32:24 arch kernel: cfg80211: World regulatory domain updated:
    апр 14 12:32:24 arch kernel: cfg80211: DFS Master region: unset
    апр 14 12:32:24 arch kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    апр 14 12:32:24 arch kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm)
    апр 14 12:32:24 arch kernel: cfg8

  • [SOLVED] MPD through mounted NFS Share

    Hi all. I am using MPD paired with Ncmpcpp, and in my configuration (for both mpd & ncmpcpp) I have the music directory set to /mnt/Shares/Music which is where I am mounting a NFS share located on the local network.
    However ncmpcpp seems to be only partially reading the directory. In the server directory I have two subdirectories (mp3 and ogg) but my music player seems to only be reading the mp3 directory. I have tried updating the database through ncmpcpp, restarting the computer, restarting mpd through systemctl, and even tried using symlinks within the directory (and having "follow internal" and "follow external" symlinks set to "yes" in /etc/mpd.conf).
    None of these seem to work in making mpd read the ogg directory.
    Edit: Mounting through NFS automatically chowns the share to the local user, so not only did I have to sudo chown -R <user>:users the music share directory on the host I also had to reconfigure my MPD settings to run as a local user as well in order to have proper permissions for the NFS share. Prior to that it was running system wide as the MPD user. This has solved the problem completely.
    Last edited by felixculpa (2012-12-26 05:24:19)

    WonderWoofy wrote:
    Awesome, don't forget to mark your thread as [Solved] by editing your first posts.  Sorry I couldn't have been of better help to you.  Glad you solved it though.
    Edit: I did think it kind of odd (and unlikely) that ogg would not be an automatically supported format, but the source told me otherwise... strange.
    Thanks. The Arch community is awesome and I appreciate the help I get in the forums. I am currently updating the database but it is taking quiet some time, so I am not 100% I have fixed the problem. After it is done, and if it works I will update the thread as [Solved].
    Thanks again.
    Edit: I forgot to mention that I was mistaken in the not reading ogg files part. It was reading only some files from both directories; it just wasn't reading the files it didn't have permission for I'm guessing.
    Last edited by felixculpa (2012-12-26 03:47:46)

  • [SOLVED] Problem mounting nfs shares

    Hello everybody,
    I keep getting the following error when I try to mount an NFS share;
    mount.nfs4: an incorrect mount option was specified
    The corresponding line in /etc/fstab is this:
    pc-francois.local:/francois /mnt/pc-francois nfs4 rw,port=2049,noauto,users,intr  0 0
    showmount -e pc-francois.local gives this:
    Export list for pc-francois.local:
    /export/archives 192.168.1.0/24
    /export/portage  192.168.1.0/24
    /export/francois 10.8.0.0/24,192.168.1.0/24
    /export          10.8.0.0/24,192.168.1.0/24
    Finally, the nfs related modules are loaded. lsmod | grep nfs gives this:
    nfsv4                 129119  0
    nfsd                  228113  13
    auth_rpcgss            41857  1 nfsd
    nfs                   118782  1 nfsv4
    lockd                  57996  2 nfs,nfsd
    grace                   1706  2 nfsd,lockd
    sunrpc                170119  19 nfs,nfsd,auth_rpcgss,lockd,nfsv4
    It works perfectly fine from other client not running on arch linux. Like indicated in the howto, I have enabled and started the services rpcbind.service,nfs-client.target and remote-fs.target
    Can somebody explains what is happening ?
    Last edited by FrançoisVal (2015-05-02 16:48:14)

    I finally solved my problem by changing the mount options to  this in fstab:
    pc-francois.local:/francois /mnt/pc-francois nfs4 rw,proto=tcp,vers=4.0,noauto,users,intr  0 0
    One week to find it... Maybe it wants to use nfs 4.1 by default.

  • Please help i can't share my project I did try in all of them and it doesnt work it apears like that........ The share operation Master File has failed The operation could not be completed because an error occurred when creating frame 608 (error -1). and

    I did try in all of them and it doesnt work it apears like that........
    The share operation Master File has failed
    The operation could not be completed because an error occurred when creating frame 608 (error -1).
    and i dont know what to do plese hlp me....
    Re: when i try to share my project to quicktime aroun 50% appears error -1 and i can't share it what to do please help 

    Double post…

  • My home button doesnt work at all and its not broken and it didnt fall. What should I do to solve this issue?

    This is an iPad replacement because the ne that I had before rejected my sim card so Apple sent me a new ne for free. I received it last Wednesday and the home button didnt work correctly. And today, a week later, it just stopped working completely, whenever I press it, it doesnt work. What should I do? Are there any steps that I can take to try to solve this button issue?

    hmm.
    it literally does nothing?
    If the engraving is important to you, then you may wish to get it repaired.
    I would recommend calling iphone repair www.iphonerepair.com
    or iresq www.iresq.com
    but first try this:
    https://discussions.apple.com/message/15143496#15143496
    --Sam

  • I have problem with My dual LED flash On My iPhone 5s. The Amber LED doesnt work at All. I dont know Since when It happened,.. Does anyone Know how to solve This?

    When i bought This iPhone 5s one Month ago, all The functionalities of This iPhone 5s worked normally. And somehow, i have just noticed that My amber_led doesnt work when i use My Camera. I am sure that i have The flash turned On at The screen. And Also The white LED working properly. So., does anyone Know how to Solve The issue? Thank you

    I believe there are 1500 different mixes of brightness for the two LEDs to produce an accurate color tone on the "flashed" subject. So possibly there are situations where the bottom LED would appear brighter than the top one, especially in very cool lighting conditions...
    also there are software algorithms to control  how bright each is..reesetting the phones settings should fix the problem if notthen,  its a hardware related issue bring to apple its under warranty

  • [SOLVED]Unmounting NFS shares before network is brought down

    I'm using networkd and I have enabled the network-wait-online service, so at boot-time my NFS shares are mounted after the network becomes available. That all works perfectly.
    However, it doesn't work the other way around i.e. when shutting down. The network is brought down, and then systemd attempts to unmount the shares, which obviously doesn't work.
    Have I missed a step?
    Last edited by tomk (2014-07-04 12:31:47)

    Strike0 wrote:I'm not using it, but reading your topic made me associate the "nfs-client.target" mentioned here: https://mailman.archlinux.org/pipermail … 26393.html
    I checked this out too, but it has a lot of 'Wants' that I don't really need.  Maybe I could fix it up, but I use autofs so I don't have this problem (the real autofs, not the systemd one).
    % systemctl cat nfs-client.target
    # /usr/lib/systemd/system/nfs-client.target
    [Unit]
    Description=NFS client services
    Before=remote-fs-pre.target
    Wants=remote-fs-pre.target
    # Note: we don't "Wants=rpc-statd.service" as "mount.nfs" will arrange to
    # start that on demand if needed.
    Wants=rpc-gssd.service rpc-svcgssd.service
    Wants=nfs-blkmap.service rpc-statd-notify.service
    Before=rpc-gssd.service rpc-svcgssd.service nfs-blkmap.service
    [Install]
    WantedBy=multi-user.target
    WantedBy=remote-fs.target
    Last edited by WonderWoofy (2014-06-21 01:00:04)

  • Error code 1,iphone backup and restore,now phone doesnt work at all and apple not in any hurry to solve issue,only had phone 4 mths,wish id stuck with iphone3 and never upgraded

    what a nightmare,no phone for 3 days and no sign of any positive help from apple.done backup and restore as wifi on phone stopped working,error code 1 and now phone doesnt work at all,apple say other people having problem but havent heard of anyone else,really disappointed in way apple are keeping me hanging on,phone is only 4 mths old

    My iphone is only 6 months old and I am experiencing the same problems. I have already had to have the phone swapped once with a phone that has a blown speaker. (The apple store is 2.5hours away so I havent been able to go back to replace the replacement) Since I did the ios 5 update, my phone says NO SERVICE and drops calls. It was speratic but last night, same ERROR message as you. As you know, if forces you to restore which caused me to loose valuable information and documents. insert loud profanity here _________. lol

  • [SOLVED] NFS share not mounting at boot

    Hi All,
    I have an NFS share listed in fstab and it doesn't mount at boot; however, when i mount -a, it mounts fine. Any thoughts?
    Thanks.
    Shawn
    Last edited by shawn.abdushakur (2011-05-06 12:21:27)

    @damnshock: Good point . Here it is:
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    devpts /dev/pts devpts defaults 0 0
    shm /dev/shm tmpfs nodev,nosuid 0 0
    #/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
    #/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
    #/dev/fd0 /media/fl auto user,noauto 0 0
    /dev/sda1 swap swap defaults 0 0
    LABEL=arch / ext4 defaults 0 1
    UUID=c1a8b2e0-bf9e-4382-ac4e-15c2aec65090 /srv/nfs ext3 defaults 0 0
    /srv/nfs/shawn/Documents /home/shawn/Documents none bind
    /srv/nfs/shawn/Downloads /home/shawn/Downloads none bind
    /srv/nfs/shawn/Music /home/shawn/Music none bind
    /srv/nfs/shawn/Pictures /home/shawn/Pictures none bind
    /srv/nfs/shawn/Videos /home/shawn/Videos none bind
    xbmc:/srv/nfs/watch /home/shawn/Downloads/torrents/watch nfs rsize=8192,wsize=8192,timeo=14,intr

  • Issue with special character in NFS shares

    Hello,
    I run a Ubuntu 10.04 server for serving my files via NFS. I have no problems mounting the NFS shares in my iMac (OS X 10.6.3). I can access all files, even the ones containing special characters in their names. I can copy, create, move them with no problem, both on Finder and on the Terminal.
    The problem comes when I try to synchronize or backup files using backup tools. Files with accents in their names (á, é, ã, ç, etc) are simply ignored by the backup/sync tools I am using. I could reproduce the problem in different softwares like "ChronoSync" and "File Synchronization". Accents are a must have in my network.
    I saw in other posts in this forum that there might be some incompatibilities with Unicode and special chars while using Mac OS X as a NFS client for a Linux NFS server. What strikes me is that Finder and Terminal work just OK.
    Any clue?
    Some details of my NFS configuration:
    /etc/exports on my server:
    /mnt/disco01 10.209.1.0/24(rw,sync,nosubtree_check,anonuid=1000,anongid=1000,allsquash)
    /mnt/disco02 10.209.1.0/24(rw,sync,nosubtree_check,anonuid=1000,anongid=1000,allsquash)
    /mnt/disco03 10.209.1.0/24(rw,sync,nosubtree_check,anonuid=1000,anongid=1000,allsquash)
    /mnt/disco04 10.209.1.0/24(rw,sync,nosubtree_check,anonuid=1000,anongid=1000,allsquash)
    On my iMac I moount them like this using Disk Utility's NFS tool:
    URL: nfs://servidor/mnt/disco01
    Mount point: /Network/disco01
    Options: -P nosuid
    Thanks for any help you can give me.

    Well, I dug a little further and got a solution, although It make no sense to me.
    So, the scenario is:
    server URL: nfs://server/mnt/disco01
    mount point: /Network/disco01
    I was trying to synchronize a folder from the server called /Network/disco01/Música (meaning music in Portugueses) to a local folder /Users/shared/Música. I would use ChronoSync to keep the folders in sync, mirroring the NFS share to the local folder. ChronoSync was ignoring the folder.
    After not being able to copy using the ChronoSync tool, I tried to copy the folder via the Finder. I could browse the nfs share using the finder, but not copy the files the local folder.
    While trying to copy, I use Cmd-C then Cmd-V in the /User/shared/ folder. I noticed that first the Finder named the folder "Music" and then some instants after if would refuse to copy. Very strange.
    I first renamed the "Música" folder on the NFS share to "Músicas", then everything worked allright, even Chronosync. Turns out that Música is the name of one of the system folder OS X creates on the user's home folder. It is actually a translation to the underlying name Music.
    Why it was interfering with the copy of totally unrelated NFS and local folders I can really not understand.
    More interesting, afterwards I renamed the NFS folder again to Música (without s) and it kept working.
    I am happy now, but I have no clue as to why there was the problem, and why it got solved.
    Hope this helps somebody in a similar situation.

  • Downloaded iTunes 9...but the Home Sharing "drag and drop" doesnt work

    I just downloaded iTunes 9 to my ASUS laptop and..well im trying to transfer some of my other library to this computer using the home sharing..but the simple "drag and drop" to add from the shared library to yours doesn't work at all. I tired re-installing iTUnes but it still doesnt work. Help!

    Okay, FWIW I just solved this on my machines...was tearing my hair out too!
    Drag/drop and settings/import buttons are enabled only when the shared library is a yellow icon, and not a blue icon. So, what's the difference?
    A blue icon indicates just plain vanilla sharing--no drag/drop or import is allowed. This type of sharing is enabled by turning on "Look for shared libraries" and "Share my library on my local network" in preferences on both machines.
    I did this and signed in under the same account on both machines but still only got the blue icon and couldn't drag/drop or import. Then I discovered it (and felt pretty dumb that I missed it).
    Make sure you go to the Advanced menu option and select "Turn On Home Sharing", and sign-in. Once you do this, you should get the yellow sharing icon and things will work smoothly.
    Again, just turning on sharing in preferences and signing-in (under the Store menu option) will not do the trick. You need to enable home sharing through the Advanced menu option.
    Hope that helps!

  • Cannot mount NFS shares using the Finder

    Hello all!
    I have a directory structure on a OpenSuse NFS Server which I like to browse/read using my MAC OSX 10.5.6. It works like a joy when I am mounting the NFS share on the command line using "sudo":
    sudo mount -o resvport nfshost:/full/path/NFS/share /My/mount/point
    However, this is kind of unconvenient as I need to start Terminal and sudo always asks me for the root password. I would appreciate to mount the NFS share just as I mount afp shares using the Finder. But the NFS share is neither searchable using the Finder nor does it show up in the list of host in the side bar of the Finder.
    Does anyone has an idea how to solve that? Thx for your information!

    The problem is most likely that your NFS server requires that connections come from reserved ports but you can't connect that way from the Finder GUI.
    Your example:
    sudo mount -o resvport nfshost:/full/path/NFS/share /My/mount/point
    shows that you need to use "-o resvport" and that you need to do the mount as root. (This is because the networking stack requires you to be root to get a reserved port.) When you try to mount it via the Finder, you can't specify any mount options like "-o resvport" and even if you could the mount would fail because the Finder isn't running as root.
    My first suggestion would be to change the configuration of your server to not require clients to use reserved ports for the NFS protocol. Unfortunately, Linux chooses to call that option "insecure" even though requiring the use of reserved ports (using "secure") doesn't actually make NFS more secure.
    Alternatively, you could configure the mount to be performed by something that does do the mount as root - e.g. automount/autofs. You can do this by configuring the mount on Directory Utility's "Mounts" section... you'll want to add "resvport" to the "Advanced mount options" field.
    HTH
    --macko

  • Thunar freezing when mounting NFS shares

    I have used Thunar and NFS for some time without any problems, but in the past week Thunar has been locking up solid when I use it to access a NFS share for more than a minutes or so. It totally locks up the Thunar GUI and I have to force it to quit. When this happens I noticed that the rpc.mountd process becomes zombified or defunct, and AutoFS no longer works too. Restarting these processes with systemctl does not work, since the restart command just hangs.
    I run  "journalctl -xn" when this happens, but noting really stands out.
    I don't have any issues when I access the same NFS share using a terminal.
    Currently I have a less than satisfactory workaround - which is to use PCmanFM instead of Thunar. PCmanFM seems to have the good graces to just automatically crash after mounting a NFS share for more than a minute and thus not case all the problems with rpc.mountd & AutoFS.

    I finally solved my problem by changing the mount options to  this in fstab:
    pc-francois.local:/francois /mnt/pc-francois nfs4 rw,proto=tcp,vers=4.0,noauto,users,intr  0 0
    One week to find it... Maybe it wants to use nfs 4.1 by default.

Maybe you are looking for

  • ALL pictures in iPhoto *and* PhotoBooth are gone :(  please help

    Hello, I have a bit of a dilema here. On 6-27-07 (actually 6-28 cause it was after midnight), my daughter and I were taking pictures in photobooth. I selected the iPhoto icon from the PhotoBooth picture to send a copy of those pictures to iPhoto. Pho

  • How to automatically detect server ip address

    does any one know how to automatically detect an ip address of a server from the client with a socket based connection ? instead of prompting the client to connect to the server ip address which is trouble some.

  • Performing SQL in JSP okay for clustering?

    I'm running on WLS 8.1 SP2. I've a JSP which is part of my main post login page. There're some SQL logics there. Would this be a problem to cluster replication & failover?

  • Pipeline materials

    Hi All, I wantd to do Goods issue for pipeline materials. So i hav created one pipeline material and also maintained info record. when i tried to post the goods issue ( Mov type 201P) it gives me the error as "G/l account 1214002300 does not exists i

  • Backup 3.2 Help Menu won't help

    When I try to use the Help menu using my Account I got an error message saying : Help Viewer cannot open this content. When I log in to my wife's account I can access Help. Tried uninstalling and reinstalling, didn't help. Need help please.