Hide Forgot
Description of problem: To describe I copy here part of a thread "Re: [Test-Announce] Fedora 24 Candidate Beta-1.2 Available Now!", where Adam Williamson describes, what he understands from my not technical description of this problem: "If I'm understanding correctly, when you try to set the wifi passphrase via GNOME Initial Setup (the wizard that pops up on first boot / login) or directly from the Shell overview, you get a Shell overlay dialog (like in screenshot 2), and that doesn't work, you don't get connected. Right? But if you go into nm-connection-editor and enter the passphrase there - that's where you are in screenshot 6 - it works. Right? If I've got all that right, I think you should file a bug on GNOME Shell, and I will see if I can reproduce it here too. Thanks! CCing desktop@ for info. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XM" Adams description is correct. My description of this problem in this thread: Hi, it's curious. There seem to be another problem. I have documented it in 6 screenshots, my technical English is not so perfect to explain the situation clearly in words. The behaviour after installation is the same without updates or after dnf update. In screenshot 1 and 2 You see what happens during completion of installation after the first reboot. The entry of the pw is unsuccessful, no connection to wifi possible. In screenshots 4,5 and 6 I am using the way via the network icon, if I click i.e on the wifi name the situation is the same as in screenshots 1 and 2 - no connection to wifi possible. The only way to connect is clicking on the "circle with the gear-wheel in it", then another window with saying wpa2.... opens, entering in this window the pw, connection to wifi is ok. Known problem? Bug? Kind regards I attach screenshots for a better description. Version-Release number of selected component (if applicable): F24 Beta 1.2 How reproducible: For me always at F24 installation Steps to Reproduce: 1. Install F24 Beta 1.2 2. In the initial set up try to enter the wifi pass phrase 3. Actual results: No wifi connection Expected results: successful wifi connection Additional info:
Created attachment 1152497 [details] gnome initial setup, phase to enter wifi passphrase
Created attachment 1152498 [details] gnome initial setup, "enter wifi passphrase"
Created attachment 1152499 [details] try to connect wifi via nm-connection-editor
Created attachment 1152500 [details] try to connect wifi via nm-connection-editor next screenshot
Created attachment 1152501 [details] successful wifi connection
Could you provide the relevant journal output? There are several components involved here, and from just the screenshots it is not clear whether it's an issue with gnome-shell, gnome-keyring or NetworkManager ...
I will do, but I not a big Linux expert, can You tell me which journal output You need?
Trial to log gnome-shell: journalctl /usr/bin/gnome-shell No entry while trying to connect to wifi Trial to log Gnome-Keyring: journalctl /usr/bin/gnome-keyring No entries before and after trying to connect to wifi Please tell me which commands to run.
Log for journalctl -b -u NetworkManager Mai 03 19:39:59 linux.fritz.box NetworkManager[1124]: <info> [1462297199.9838] device (wlp2s0): state change: prepare -> config (reason 'none') [40 Mai 03 19:39:59 linux.fritz.box NetworkManager[1124]: <info> [1462297199.9840] device (wlp2s0): Activation: (wifi) access point 'intern!haus:lan' ha Mai 03 19:39:59 linux.fritz.box NetworkManager[1124]: <info> [1462297199.9840] device (wlp2s0): state change: config -> need-auth (reason 'none') [5 Mai 03 19:40:25 linux.fritz.box NetworkManager[1124]: <warn> [1462297225.0259] device (wlp2s0): No agents were available for this request. Mai 03 19:40:25 linux.fritz.box NetworkManager[1124]: <info> [1462297225.0259] device (wlp2s0): state change: need-auth -> failed (reason 'no-secret Mai 03 19:40:25 linux.fritz.box NetworkManager[1124]: <warn> [1462297225.0263] device (wlp2s0): Activation: failed for connection 'intern!haus:lan' Mai 03 19:40:25 linux.fritz.box NetworkManager[1124]: <info> [1462297225.0269] device (wlp2s0): state change: failed -> disconnected (reason 'none') Mai 03 19:40:25 linux.fritz.box NetworkManager[1124]: <warn> [1462297225.0416] firewall: [0x560c941d9730,remove:"wlp2s0"]: complete: request failed lines 257-279/279 (END)
Sure. You use the 'journalctl' command to display the journal content. There are several ways to filter the output (by process/service, time range etc.). The easiest option in this case is probably: (1) run "journalctl -f > wifi-password.log" in a terminal (2) reproduce the issue (activate the wifi entry in the menu, enter password etc.) (3) switch back to the terminal and terminate the journalctl command with <ctrl>c (4) make sure wifi-password.log doesn't contain sensitive information, then attach it here
trying to connect in the way it does not work. [root@linux joerg]# journalctl -f -- Logs begin at Sa 2016-04-30 08:38:22 CEST. -- Mai 03 19:49:29 linux.fritz.box NetworkManager[1124]: <info> [1462297769.6567] device (wlp2s0): state change: prepare -> config (reason 'none') [40 50 0] Mai 03 19:49:29 linux.fritz.box NetworkManager[1124]: <info> [1462297769.6571] device (wlp2s0): Activation: (wifi) access point 'intern!haus:lan' has security, but secrets are required. Mai 03 19:49:29 linux.fritz.box NetworkManager[1124]: <info> [1462297769.6571] device (wlp2s0): state change: config -> need-auth (reason 'none') [50 60 0] Mai 03 19:49:54 linux.fritz.box NetworkManager[1124]: <warn> [1462297794.6895] device (wlp2s0): No agents were available for this request. Mai 03 19:49:54 linux.fritz.box NetworkManager[1124]: <info> [1462297794.6895] device (wlp2s0): state change: need-auth -> failed (reason 'no-secrets') [60 120 7] Mai 03 19:49:54 linux.fritz.box NetworkManager[1124]: <warn> [1462297794.6900] device (wlp2s0): Activation: failed for connection 'intern!haus:lan' Mai 03 19:49:54 linux.fritz.box NetworkManager[1124]: <info> [1462297794.6919] device (wlp2s0): state change: failed -> disconnected (reason 'none') [120 30 0] Mai 03 19:49:54 linux.fritz.box kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready Mai 03 19:49:54 linux.fritz.box /firewalld[1010]: ERROR: UNKNOWN_INTERFACE: 'wlp2s0' is not in any zone Mai 03 19:49:54 linux.fritz.box NetworkManager[1124]: <warn> [1462297794.7028] firewall: [0x560c942138a0,remove:"wlp2s0"]: complete: request failed (UNKNOWN_INTERFACE: 'wlp2s0' is not in any zone) If helpful, connection to wifi in the way which is ok: ------------------------------------------------------ [root@linux joerg]# [root@linux joerg]# journalctl -f -- Logs begin at Sa 2016-04-30 08:38:22 CEST. -- Mai 03 19:49:54 linux.fritz.box NetworkManager[1124]: <info> [1462297794.6919] device (wlp2s0): state change: failed -> disconnected (reason 'none') [120 30 0] Mai 03 19:49:54 linux.fritz.box kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready Mai 03 19:49:54 linux.fritz.box /firewalld[1010]: ERROR: UNKNOWN_INTERFACE: 'wlp2s0' is not in any zone Mai 03 19:49:54 linux.fritz.box NetworkManager[1124]: <warn> [1462297794.7028] firewall: [0x560c942138a0,remove:"wlp2s0"]: complete: request failed (UNKNOWN_INTERFACE: 'wlp2s0' is not in any zone) Mai 03 19:53:48 linux.fritz.box systemd[1]: Starting dnf makecache... Mai 03 19:53:49 linux.fritz.box dnf[4381]: Metadaten-Zwischenspeicher wurde kürzlich aktualisiert. Mai 03 19:53:49 linux.fritz.box systemd[1]: Started dnf makecache. Mai 03 19:53:49 linux.fritz.box audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf-makecache comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Mai 03 19:53:49 linux.fritz.box audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf-makecache comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Mai 03 19:55:52 linux.fritz.box PackageKit[1836]: search-file transaction /20_bdaccccd from uid 0 finished with success after 105ms Mai 03 19:56:14 linux.fritz.box dbus[1003]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' Mai 03 19:56:14 linux.fritz.box systemd[1]: Starting Hostname Service... Mai 03 19:56:14 linux.fritz.box audit: NETFILTER_CFG table=filter family=2 entries=0 Mai 03 19:56:14 linux.fritz.box audit: NETFILTER_CFG table=filter family=10 entries=0 Mai 03 19:56:14 linux.fritz.box audit: NETFILTER_CFG table=mangle family=2 entries=0 Mai 03 19:56:14 linux.fritz.box audit: NETFILTER_CFG table=security family=2 entries=0 Mai 03 19:56:14 linux.fritz.box audit: NETFILTER_CFG table=raw family=2 entries=0 Mai 03 19:56:14 linux.fritz.box audit: NETFILTER_CFG table=nat family=2 entries=0 Mai 03 19:56:14 linux.fritz.box audit: NETFILTER_CFG table=mangle family=10 entries=0 Mai 03 19:56:14 linux.fritz.box audit: NETFILTER_CFG table=security family=10 entries=0 Mai 03 19:56:14 linux.fritz.box audit: NETFILTER_CFG table=raw family=10 entries=0 Mai 03 19:56:14 linux.fritz.box audit: NETFILTER_CFG table=nat family=10 entries=0 Mai 03 19:56:14 linux.fritz.box dbus[1003]: [system] Successfully activated service 'org.freedesktop.hostname1' Mai 03 19:56:14 linux.fritz.box systemd[1]: Started Hostname Service. Mai 03 19:56:14 linux.fritz.box audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Mai 03 19:56:44 linux.fritz.box audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Mai 03 19:56:44 linux.fritz.box NetworkManager[1124]: <info> [1462298204.9424] audit: op="connection-update" uuid="deleted" name="intern!haus:lan" pid=3777 uid=1000 result="success" Mai 03 19:56:52 linux.fritz.box NetworkManager[1124]: <info> [1462298212.2110] device (wlp2s0): Activation: starting connection 'intern!haus:lan' (deleted) Mai 03 19:56:52 linux.fritz.box NetworkManager[1124]: <info> [1462298212.2111] audit: op="connection-activate" uuid="deleted" name="intern!haus:lan" pid=3777 uid=1000 result="success" Mai 03 19:56:52 linux.fritz.box NetworkManager[1124]: <info> [1462298212.2113] device (wlp2s0): state change: disconnected -> prepare (reason 'none') [30 40 0] Mai 03 19:56:52 linux.fritz.box NetworkManager[1124]: <info> [1462298212.2120] device (wlp2s0): state change: prepare -> config (reason 'none') [40 50 0] Mai 03 19:56:52 linux.fritz.box NetworkManager[1124]: <info> [1462298212.2123] device (wlp2s0): Activation: (wifi) access point 'intern!haus:lan' has security, but secrets are required. Mai 03 19:56:52 linux.fritz.box NetworkManager[1124]: <info> [1462298212.2123] device (wlp2s0): state change: config -> need-auth (reason 'none') [50 60 0] Mai 03 19:56:52 linux.fritz.box NetworkManager[1124]: <info> [1462298212.2376] device (wlp2s0): state change: need-auth -> prepare (reason 'none') [60 40 0] Mai 03 19:56:52 linux.fritz.box NetworkManager[1124]: <info> [1462298212.2380] device (wlp2s0): state change: prepare -> config (reason 'none') [40 50 0] Mai 03 19:56:52 linux.fritz.box NetworkManager[1124]: <info> [1462298212.2383] device (wlp2s0): Activation: (wifi) connection 'intern!haus:lan' has security, and secrets exist. No new secrets needed. Mai 03 19:56:52 linux.fritz.box NetworkManager[1124]: <info> [1462298212.2383] Config: added 'ssid' value 'intern!haus:lan' Mai 03 19:56:52 linux.fritz.box NetworkManager[1124]: <info> [1462298212.2383] Config: added 'scan_ssid' value '1' Mai 03 19:56:52 linux.fritz.box NetworkManager[1124]: <info> [1462298212.2384] Config: added 'key_mgmt' value 'WPA-PSK' Mai 03 19:56:52 linux.fritz.box NetworkManager[1124]: <info> [1462298212.2384] Config: added 'psk' value '<omitted>' Mai 03 19:56:52 linux.fritz.box NetworkManager[1124]: <info> [1462298212.2536] sup-iface[0x560c94168b50,wlp2s0]: config: set interface ap_scan to 1 Mai 03 19:56:52 linux.fritz.box NetworkManager[1124]: <info> [1462298212.2731] device (wlp2s0): supplicant interface state: disconnected -> scanning Mai 03 19:56:53 linux.fritz.box wpa_supplicant[1254]: wlp2s0: SME: Trying to authenticate with 9c:c7:a6:f0:38:0d (SSID='intern!haus:lan' freq=2462 MHz) Mai 03 19:56:53 linux.fritz.box kernel: wlp2s0: authenticate with xx:xx:xx:xx:xx:xx ------> don't know, I modified to xx:xx...etc Mai 03 19:56:53 linux.fritz.box kernel: wlp2s0: send auth to xx:xx:xx:xx:xx:xx ------> don't know, I modified to xx:xx...etc (try 1/3) Mai 03 19:56:53 linux.fritz.box NetworkManager[1124]: <info> [1462298213.1808] device (wlp2s0): supplicant interface state: scanning -> authenticating Mai 03 19:56:53 linux.fritz.box wpa_supplicant[1254]: wlp2s0: Trying to associate with 9c:c7:a6:f0:38:0d (SSID='intern!haus:lan' freq=2462 MHz) Mai 03 19:56:53 linux.fritz.box kernel: wlp2s0: authenticated Mai 03 19:56:53 linux.fritz.box kernel: wlp2s0: associate with 9c:c7:a6:f0:38:0d (try 1/3) Mai 03 19:56:53 linux.fritz.box NetworkManager[1124]: <info> [1462298213.1894] device (wlp2s0): supplicant interface state: authenticating -> associating Mai 03 19:56:53 linux.fritz.box wpa_supplicant[1254]: wlp2s0: Associated with 9c:c7:a6:f0:38:0d Mai 03 19:56:53 linux.fritz.box kernel: wlp2s0: RX AssocResp from 9c:c7:a6:f0:38:0d (capab=0x431 status=0 aid=2) Mai 03 19:56:53 linux.fritz.box kernel: wlp2s0: associated Mai 03 19:56:53 linux.fritz.box kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready Mai 03 19:56:53 linux.fritz.box wpa_supplicant[1254]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=DE Mai 03 19:56:53 linux.fritz.box kernel: ath: EEPROM regdomain: 0x8114 Mai 03 19:56:53 linux.fritz.box kernel: ath: EEPROM indicates we should expect a country code Mai 03 19:56:53 linux.fritz.box kernel: ath: doing EEPROM country->regdmn map search Mai 03 19:56:53 linux.fritz.box kernel: ath: country maps to regdmn code: 0x37 Mai 03 19:56:53 linux.fritz.box kernel: ath: Country alpha2 being used: DE Mai 03 19:56:53 linux.fritz.box kernel: ath: Regpair used: 0x37 Mai 03 19:56:53 linux.fritz.box kernel: ath: regdomain 0x8114 dynamically updated by country IE Mai 03 19:56:53 linux.fritz.box NetworkManager[1124]: <info> [1462298213.1998] device (wlp2s0): supplicant interface state: associating -> associated Mai 03 19:56:53 linux.fritz.box NetworkManager[1124]: <info> [1462298213.2085] device (wlp2s0): supplicant interface state: associated -> 4-way handshake Mai 03 19:56:53 linux.fritz.box wpa_supplicant[1254]: wlp2s0: WPA: Key negotiation completed with 9c:c7:a6:f0:38:0d [PTK=CCMP GTK=TKIP] Mai 03 19:56:53 linux.fritz.box wpa_supplicant[1254]: wlp2s0: CTRL-EVENT-CONNECTED - Connection to 9c:c7:a6:f0:38:0d completed [id=0 id_str=] Mai 03 19:56:53 linux.fritz.box NetworkManager[1124]: <info> [1462298213.2163] device (wlp2s0): supplicant interface state: 4-way handshake -> completed Mai 03 19:56:53 linux.fritz.box NetworkManager[1124]: <info> [1462298213.2164] device (wlp2s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'intern!haus:lan'. Mai 03 19:56:53 linux.fritz.box audit: NETFILTER_CFG table=mangle family=2 entries=41 Mai 03 19:56:53 linux.fritz.box audit: NETFILTER_CFG table=filter family=2 entries=96 Mai 03 19:56:53 linux.fritz.box audit: NETFILTER_CFG table=nat family=2 entries=57 Mai 03 19:56:53 linux.fritz.box audit: NETFILTER_CFG table=mangle family=10 entries=40 Mai 03 19:56:53 linux.fritz.box audit: NETFILTER_CFG table=filter family=10 entries=87 Mai 03 19:56:53 linux.fritz.box audit: NETFILTER_CFG table=nat family=10 entries=52 Mai 03 19:56:53 linux.fritz.box NetworkManager[1124]: <info> [1462298213.2280] device (wlp2s0): state change: config -> ip-config (reason 'none') [50 70 0] Mai 03 19:56:53 linux.fritz.box NetworkManager[1124]: <info> [1462298213.2285] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds) Mai 03 19:56:53 linux.fritz.box NetworkManager[1124]: <info> [1462298213.2309] dhcp4 (wlp2s0): dhclient started with pid 4480 Mai 03 19:56:53 linux.fritz.box dhclient[4480]: Created duid \000\004\347\264\201\265\031\365Ar\272\354x\344`\353\212\311. Mai 03 19:56:53 linux.fritz.box dhclient[4480]: DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 7 (xid=0x9b81f654) Mai 03 19:56:54 linux.fritz.box dhclient[4480]: DHCPREQUEST on wlp2s0 to 255.255.255.255 port 67 (xid=0x9b81f654) Mai 03 19:56:54 linux.fritz.box dhclient[4480]: DHCPOFFER from 192.168.178.1 Mai 03 19:56:54 linux.fritz.box dhclient[4480]: DHCPACK from 192.168.178.1 (xid=0x9b81f654) Mai 03 19:56:54 linux.fritz.box NetworkManager[1124]: <info> [1462298214.2863] address 192.168.178.21 Mai 03 19:56:54 linux.fritz.box NetworkManager[1124]: <info> [1462298214.2863] plen 24 (255.255.255.0) Mai 03 19:56:54 linux.fritz.box NetworkManager[1124]: <info> [1462298214.2863] gateway 192.168.178.1 Mai 03 19:56:54 linux.fritz.box NetworkManager[1124]: <info> [1462298214.2863] server identifier 192.168.178.1 Mai 03 19:56:54 linux.fritz.box NetworkManager[1124]: <info> [1462298214.2863] lease time 864000 Mai 03 19:56:54 linux.fritz.box NetworkManager[1124]: <info> [1462298214.2864] nameserver '192.168.178.1' Mai 03 19:56:54 linux.fritz.box NetworkManager[1124]: <info> [1462298214.2864] domain name 'fritz.box' Mai 03 19:56:54 linux.fritz.box NetworkManager[1124]: <info> [1462298214.2864] dhcp4 (wlp2s0): state changed unknown -> bound Mai 03 19:56:54 linux.fritz.box avahi-daemon[1029]: Joining mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.178.21. Mai 03 19:56:54 linux.fritz.box avahi-daemon[1029]: New relevant interface wlp2s0.IPv4 for mDNS. Mai 03 19:56:54 linux.fritz.box avahi-daemon[1029]: Registering new address record for 192.168.178.21 on wlp2s0.IPv4. Mai 03 19:56:54 linux.fritz.box NetworkManager[1124]: <info> [1462298214.2898] device (wlp2s0): state change: ip-config -> ip-check (reason 'none') [70 80 0] Mai 03 19:56:54 linux.fritz.box dhclient[4480]: bound to 192.168.178.21 -- renewal in 377186 seconds. Mai 03 19:56:54 linux.fritz.box dbus[1003]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Mai 03 19:56:54 linux.fritz.box systemd[1]: Starting Network Manager Script Dispatcher Service... Mai 03 19:56:54 linux.fritz.box dbus[1003]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Mai 03 19:56:54 linux.fritz.box systemd[1]: Started Network Manager Script Dispatcher Service. Mai 03 19:56:54 linux.fritz.box audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Mai 03 19:56:54 linux.fritz.box nm-dispatcher[4491]: req:1 'pre-up' [wlp2s0]: new request (1 scripts) Mai 03 19:56:54 linux.fritz.box NetworkManager[1124]: <info> [1462298214.3349] device (wlp2s0): state change: ip-check -> secondaries (reason 'none') [80 90 0] Mai 03 19:56:54 linux.fritz.box NetworkManager[1124]: <info> [1462298214.3353] device (wlp2s0): state change: secondaries -> activated (reason 'none') [90 100 0] Mai 03 19:56:54 linux.fritz.box NetworkManager[1124]: <info> [1462298214.3545] device (wlp2s0): Activation: successful, device activated. Mai 03 19:56:54 linux.fritz.box dnsmasq[1646]: reading /etc/resolv.conf Mai 03 19:56:54 linux.fritz.box dnsmasq[1646]: using nameserver 192.168.178.1#53 Mai 03 19:56:54 linux.fritz.box dnsmasq[1646]: using nameserver fd00::9ec7:a6ff:fef0:380b#53 Mai 03 19:56:54 linux.fritz.box nm-dispatcher[4491]: req:2 'up' [wlp2s0]: new request (5 scripts) Mai 03 19:56:54 linux.fritz.box nm-dispatcher[4491]: req:2 'up' [wlp2s0]: start running ordered scripts... Mai 03 19:56:54 linux.fritz.box systemd[1]: iscsi.service: Unit cannot be reloaded because it is inactive. Mai 03 19:56:54 linux.fritz.box avahi-daemon[1029]: Joining mDNS multicast group on interface wlp2s0.IPv6 with address fe80::d40a:ab7a:f70:3ff9. Mai 03 19:56:54 linux.fritz.box avahi-daemon[1029]: New relevant interface wlp2s0.IPv6 for mDNS. Mai 03 19:56:54 linux.fritz.box avahi-daemon[1029]: Registering new address record for fe80::d40a:ab7a:f70:3ff9 on wlp2s0.*. Mai 03 19:56:54 linux.fritz.box NetworkManager[1124]: <info> [1462298214.7398] dhcp6 (wlp2s0): activation: beginning transaction (timeout in 45 seconds) Mai 03 19:56:54 linux.fritz.box NetworkManager[1124]: <info> [1462298214.7420] dhcp6 (wlp2s0): dhclient started with pid 4545 Mai 03 19:56:54 linux.fritz.box dnsmasq[1646]: reading /etc/resolv.conf Mai 03 19:56:54 linux.fritz.box dnsmasq[1646]: using nameserver 192.168.178.1#53 Mai 03 19:56:54 linux.fritz.box dnsmasq[1646]: using nameserver fd00::9ec7:a6ff:fef0:380b#53 Mai 03 19:56:55 linux.fritz.box dhclient[4545]: XMT: Info-Request on wlp2s0, interval 990ms. Mai 03 19:56:55 linux.fritz.box dhclient[4545]: RCV: Reply message on wlp2s0 from fe80::9ec7:a6ff:fef0:380b. Mai 03 19:56:55 linux.fritz.box NetworkManager[1124]: <info> [1462298215.6680] nameserver 'fd00::9ec7:a6ff:fef0:380b' Mai 03 19:56:55 linux.fritz.box NetworkManager[1124]: <info> [1462298215.6683] dhcp6 (wlp2s0): state changed unknown -> bound Mai 03 19:56:55 linux.fritz.box NetworkManager[1124]: <info> [1462298215.6700] dhcp6 (wlp2s0): client pid 4545 exited with status 0 Mai 03 19:56:55 linux.fritz.box NetworkManager[1124]: <info> [1462298215.6701] dhcp6 (wlp2s0): state changed bound -> done Mai 03 19:56:55 linux.fritz.box nm-dispatcher[4491]: req:3 'dhcp6-change' [wlp2s0]: new request (5 scripts) Mai 03 19:56:55 linux.fritz.box nm-dispatcher[4491]: req:3 'dhcp6-change' [wlp2s0]: start running ordered scripts... Mai 03 19:56:56 linux.fritz.box avahi-daemon[1029]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::d40a:ab7a:f70:3ff9. Mai 03 19:56:56 linux.fritz.box avahi-daemon[1029]: Joining mDNS multicast group on interface wlp2s0.IPv6 with address 2a02:8071:9286:1500:8e64:f6a0:7533:43ec. Mai 03 19:56:56 linux.fritz.box avahi-daemon[1029]: Registering new address record for 2a02:8071:9286:1500:8e64:f6a0:7533:43ec on wlp2s0.*. Mai 03 19:56:56 linux.fritz.box avahi-daemon[1029]: Withdrawing address record for fe80::d40a:ab7a:f70:3ff9 on wlp2s0. Mai 03 19:57:06 linux.fritz.box audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' If additional logs are required, please let me know
Mmh, if you run 'seahorse', does it show the 'Login' keyring?
It's a keyring menue, which comes up, see screenshot attached
Created attachment 1154300 [details] running seahorse, as requested by fmueller
Mmmh, the login keyring is indeed missing there. Can you make it show up by running something like gnome-keyring-daemon -r -c secrets in the <alt>f2 run dialog? When the "Login" keyring shows up in seahorse (run "pkill seahorse" first, to make sure it's not running in the background), does the wifi password dialog start working?
Hi, my linux knowledge about the handling of seahorse and keyring is very low. I show what I did, possibly it's nonsense. In addition I attach a screenshot, but I think that's not what You wanted. I could only login to wifi in the described way, but not hitting to the "wifi name". Please give a more detailed information, which I need to understand, how to test. [joerg@linux ~]$ su Passwort: [root@linux joerg]# gnome-keyring-daemon -r -c secrets ** Message: couldn't access control socket: /run/user/1000/keyring/control: Permission denied ** Message: couldn't connect to dbus session bus: Verbindung ist gescheitert:Permission denied ** Message: Replacing daemon, using directory: /run/user/1000/keyring ** Message: The gnome-keyring control directory cannot be accessed: /run/user/1000/keyring: Permission denied ** Message: The gnome-keyring control directory cannot be accessed: /run/user/1000/keyring: Permission denied ** (gnome-keyring-daemon:28913): WARNING **: couldn't create socket directory: /run/user/1000/keyring-2R1AHY: Permission denied ** (gnome-keyring-daemon:28913): WARNING **: couldn't bind to control socket: /run/user/1000/keyring-2R1AHY/control: Permission denied [root@linux joerg]# pkill seahorse [root@linux joerg]# seahorse (seahorse:28952): seahorse-WARNING **: gkr-backend.vala:90: couldn't connect to secret service: Verbindung ist geschlossen (seahorse:28952): dconf-WARNING **: failed to commit changes to dconf: Verbindung ist geschlossen (seahorse:28952): dconf-WARNING **: failed to commit changes to dconf: Verbindung ist geschlossen (seahorse:28952): dconf-WARNING **: failed to commit changes to dconf: Verbindung ist geschlossen (seahorse:28952): dconf-WARNING **: failed to commit changes to dconf: Verbindung ist geschlossen (seahorse:28952): dconf-WARNING **: failed to commit changes to dconf: Verbindung ist geschlossen (seahorse:28952): dconf-WARNING **: failed to commit changes to dconf: Verbindung ist geschlossen (seahorse:28952): dconf-WARNING **: failed to commit changes to dconf: Verbindung ist geschlossen (seahorse:28952): dconf-WARNING **: failed to commit changes to dconf: Verbindung ist geschlossen (seahorse:28952): dconf-WARNING **: failed to commit changes to dconf: Verbindung ist geschlossen (seahorse:28952): dconf-WARNING **: failed to commit changes to dconf: Verbindung ist geschlossen (seahorse:28952): dconf-WARNING **: failed to commit changes to dconf: Verbindung ist geschlossen (seahorse:28952): dconf-WARNING **: failed to commit changes to dconf: Verbindung ist geschlossen (seahorse:28952): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_has_connection: assertion 'G_IS_DBUS_CONNECTION (connection)' failed [root@linux joerg]# gnome-keyring-daemon -r -c secrets ** Message: couldn't access control socket: /run/user/1000/keyring/control: Permission denied ** Message: couldn't connect to dbus session bus: Verbindung ist gescheitert:Permission denied ** Message: Replacing daemon, using directory: /run/user/1000/keyring ** Message: The gnome-keyring control directory cannot be accessed: /run/user/1000/keyring: Permission denied ** Message: The gnome-keyring control directory cannot be accessed: /run/user/1000/keyring: Permission denied ** (gnome-keyring-daemon:30590): WARNING **: couldn't create socket directory: /run/user/1000/keyring-IGHBHY: Permission denied ** (gnome-keyring-daemon:30590): WARNING **: couldn't bind to control socket: /run/user/1000/keyring-IGHBHY/control: Permission denied [root@linux joerg]# pkill seahorse [root@linux joerg]# seahorse (seahorse:30621): seahorse-WARNING **: gkr-backend.vala:90: couldn't connect to secret service: Verbindung ist geschlossen
Created attachment 1156725 [details] keyring - seahorse, trying to test, without understanding
(In reply to joerg.lechner from comment #16) > [joerg@linux ~]$ su > Passwort: > [root@linux joerg]# gnome-keyring-daemon -r -c secrets All commands I mention should be run as user, not root: $ gnome-keyring-daemon -r -c secrets $ pkill seahorse && seahorse If there is an item called "Login" in the sidebar (at the top under the heading "Passwörter"), please retest connecting to the wifi through the top bar menu.
Created attachment 1156762 [details] Answer to comment 18 The command string $ gnome-keyring-daemon -r -c secrets $ pkill seahorse && seahorse doesn't start seahorse, I had to start seahorse separately. I didn't find a login field. Am I erroneous again?
Problem solved with F24 Desktop Final 1.2. For me works, ok now.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.