>> >> >> >> >> Hi folks, I have a super weird situation on my Sony VAIO >> >> >> >> >> VGN-FZ240E: >> >> >> >> >> >> >> >> >> >> I have Fedora 8 which ships network manager 0.7.0-0.5.svn3030 >> >> >> >> >> and >> >> >> >> >> until yesterday everything has been working perfectly well, >> >> >> >> >> nm-applet >> >> >> >> >> connected to both wired and wireless networks without a >> >> >> >> >> problem. >> >> >> >> >> And >> >> >> >> >> the strange thing is that I didn't do anything, no new >> >> >> >> >> installs, >> >> >> >> >> no >> >> >> >> >> upgrades, absolutely nothing (that I know of). >> >> >> >> > >> >> >> >> > What's the output of 'nm-tool' when that command is run in a >> >> >> >> > terminal, >> >> >> >> > when you're experiencing the problem? >> >> >> >> >> >> >> >> Thanks for the answer, so nm-tool says this: >> >> >> >> >> >> >> >> >> >> >> >> NetworkManager Tool >> >> >> >> >> >> >> >> State: disconnected >> >> >> >> >> >> >> >> - Device: eth0 >> >> >> >> ---------------------------------------------------------------- >> >> >> >> Type: Wired >> >> >> >> Driver: sky2 >> >> >> >> Active: no >> >> >> >> HW Address: 00:1A:80:49:CF:34 >> >> >> >> >> >> >> >> Capabilities: >> >> >> >> Supported: yes >> >> >> >> Carrier Detect: yes >> >> >> >> Speed: 100 Mb/s >> >> >> >> >> >> >> >> Wired Settings >> >> >> >> >> >> >> >> >> >> >> >> - Device: wlan0 >> >> >> >> ---------------------------------------------------------------- >> >> >> >> Type: 802.11 Wireless >> >> >> >> Driver: iwl4965 >> >> >> >> Active: no >> >> >> >> HW Address: 00:13:E8:87:8E:4F >> >> >> >> >> >> >> >> Capabilities: >> >> >> >> Supported: yes >> >> >> >> >> >> >> >> Wireless Settings >> >> >> >> WEP Encryption: yes >> >> >> >> WPA Encryption: yes >> >> >> >> WPA2 Encryption: yes >> >> >> >> >> >> >> >> Wireless Access Points >> >> >> >> >> >> >> >> >> >> >> >> I noticed the line 'State: disconnected' however right now I'm >> >> >> >> connected, I'm sending this email :) Again I had to manually >> >> >> >> 'dhclient >> >> >> >> eth0' which results in a working connection, only nm-applet >> >> >> >> thinks >> >> >> >> that somehow there is no wired network connection. >> >> >> > >> >> >> > Right, because the connection wasn't made through NetworkManager, >> >> >> > and >> >> >> > thus the information about the connection isn't available to >> >> >> > NEtworkManager because dhclient wasn't run with the right callout >> >> >> > script, etc. >> >> >> > >> >> >> > Can you grab /var/log/messages for me? That will show what NM >> >> >> > thinks >> >> >> > is >> >> >> > going on. It may be a carrier change race that was fixed in F10 >> >> >> > and >> >> >> > higher and the logs might help us figure that out. >> >> >> >> >> >> My reply with the attached /var/log/messages got held up for >> >> >> moderation because it was too big so I've uploaded the >> >> >> /var/log/messages file to >> >> >> >> >> >> http://danielfetchinson.appspot.com/ >> >> > >> >> > I think it's more these: >> >> > >> >> > Nov 17 02:29:48 localhost NetworkManager: Missing required value >> >> > 'name'. >> >> > Nov 17 02:29:48 localhost NetworkManager: 'connection' setting not >> >> > present. >> >> > >> >> > I don't know what the cause of that could be off the top of my head, >> >> > but >> >> > you said you're running svn3030, which is from "Sat Oct 27 2007". >> >> > That's really, really old :) The latest NetworkManager available for >> >> > Fedora 8 is: >> >> > >> >> > NetworkManager-0.7.0-0.12.svn4326.fc8 >> >> >> >> From which repo is this available? yum tells me no upgrades are >> >> available. My enabled repos are: fedora, fedora-updates, livna. >> > >> > It looks like the updates have been cleared from the mirrors since F8 >> > has been unsupported for a year already. You have to play roulette to >> > find a mirror that has them, and I got lucky when I tried: >> > >> > http://mirror.steadfast.net/fedora//updates/8/ >> > >> > None of the other mirrors have F-8 anymore. >> > >> > Assuming you aren't running a 64-bit install (if you are, replace i386 >> > with x86_64 as appropriate), install this RPM with "rpm -Uhv >> > <filename>": >> > >> > http://mirror.steadfast.net/fedora//updates/8/i386.newkey/fedora-release-8-6.transition.noarch.rpm >> > >> > Then update your fedora.repo and fedora-updates.repo files to point to >> > the steadfast.net mirror. The sections should look like this: >> > >> > [updates] >> > name=Fedora $releasever - $basearch - Updates >> > failovermethod=priority >> > baseurl=http://mirror.steadfast.net/fedora//updates/$releasever/$basearch.newkey/ >> > #mirrorlist= >> > >> > (and the same for fedora.repo) >> > >> > And then 'yum upgrade NetworkManager*" >> >> >> Thanks Dan, I've done all of this, NetworkManager* is at the latest >> fedora 8 version. >> >> However this didn't solve the problem, the only difference I'm seeing >> is that the nm-applet icon that showed no connection before (static >> icon) is now an animated icon as if it were trying to connect but >> couldn't. Again clicking the 'Wired network' radio button doesn't do >> anything. >> >> The relevant section of /var/log/messages is this, it's full of >> suspicious items from NetworkManager, I'm pretty sure something is >> screwed up with gconf connections and it's not the fault of >> NetworkManager itself. As I've said everything was working everywhere >> (home, office, 2 different continents, about 5 countries :)) in the >> last 2 years: >> >> Nov 18 23:57:24 localhost acpid: starting up >> Nov 18 23:57:25 localhost gpm[1991]: *** info [startup.c(95)]: >> Nov 18 23:57:25 localhost gpm[1991]: Started gpm successfully. Entered >> daemon mode. >> Nov 18 23:57:28 localhost acpid: client connected from 2133[68:68] >> Nov 18 23:57:29 localhost NetworkManager: <info> starting... >> Nov 18 23:57:29 localhost NetworkManager: <WARN> >> nm_generic_enable_loopback(): error -17 returned from >> rtnl_addr_add():#012Sucess#012 >> Nov 18 23:57:29 localhost NetworkManager: <info> Found radio >> killswitch /org/freedesktop/Hal/devices/ipw_wlan_switch >> Nov 18 23:57:29 localhost NetworkManager: <info> eth0: driver is 'sky2'. >> Nov 18 23:57:29 localhost NetworkManager: <info> Found new Ethernet >> device 'eth0'. >> Nov 18 23:57:29 localhost NetworkManager: <info> (eth0): exported as >> /org/freedesktop/Hal/devices/net_00_1a_80_49_cf_34 >> Nov 18 23:57:29 localhost NetworkManager: <info> Trying to start the >> supplicant... >> Nov 18 23:57:29 localhost NetworkManager: <info> Trying to start the >> system settings daemon... >> Nov 18 23:57:29 localhost console-kit-daemon[2000]: WARNING: Couldn't >> read /proc/2170/environ: Error reading file '/proc/2170/environ': No >> such process >> Nov 18 23:57:29 localhost NetworkManager: <WARN> >> killswitch_getpower_reply(): Error getting killswitch power: >> hal-ipw-killswitch-linux returned 255. >> Nov 18 23:57:30 localhost nm-system-settings: >> initial_add_devices_of_type: could not get device from HAL: An SELinux >> policy prevents this sender from sending this message to this >> recipient (rejected message had interface >> "org.freedesktop.Hal.Manager" member "FindDeviceByCapability" error >> name "(unset)" destination "org.freedesktop.Hal") (9). >> Nov 18 23:57:30 localhost nm-system-settings:last message repeated 2 times >> Nov 18 23:57:30 localhost nm-system-settings: Cannot initialize >> libpolkit: unknown error >> Nov 18 23:57:30 localhost nm-system-settings: Loaded plugin >> ifcfg-fedora: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use >> the NetworkManager mailing list. >> Nov 18 23:57:30 localhost nm-system-settings: ifcfg-fedora: parsing >> /etc/sysconfig/network-scripts/ifcfg-wlan0 ... >> Nov 18 23:57:30 localhost nm-system-settings: ifcfg-fedora: >> error: Missing SSID >> Nov 18 23:57:30 localhost nm-system-settings: ifcfg-fedora: parsing >> /etc/sysconfig/network-scripts/ifcfg-lo ... >> Nov 18 23:57:30 localhost nm-system-settings: ifcfg-fedora: >> error: Ignoring loopback device config. >> Nov 18 23:57:33 localhost NetworkManager: <info> (eth0): device state >> change: 1 -> 2 >> Nov 18 23:57:33 localhost NetworkManager: <info> (eth0): bringing up >> device. >> Nov 18 23:57:33 localhost kernel: sky2 eth0: enabling interface >> Nov 18 23:57:33 localhost kernel: ADDRCONF(NETDEV_UP): eth0: link is not >> ready >> Nov 18 23:57:33 localhost NetworkManager: <info> (eth0): preparing >> device. >> Nov 18 23:57:33 localhost NetworkManager: <info> (eth0): deactivating >> device (reason: 2). >> Nov 18 23:57:33 localhost NetworkManager: <info> Setting system >> hostname to 'localhost.localdomain' (no default device) >> Nov 18 23:57:33 localhost NetworkManager: <WARN> >> set_system_hostname(): set_system_hostname: couldn't set the system >> hostname to 'localhost.localdomain': (1) Operation not permitted >> Nov 18 23:57:33 localhost NetworkManager: <info> Setting system >> hostname to 'localhost.localdomain' (no default device) >> Nov 18 23:57:33 localhost NetworkManager: <WARN> >> set_system_hostname(): set_system_hostname: couldn't set the system >> hostname to 'localhost.localdomain': (1) Operation not permitted >> Nov 18 23:57:33 localhost NetworkManager: <info> (eth0): carrier now >> ON (device state 2) >> Nov 18 23:57:33 localhost NetworkManager: <info> (eth0): device state >> change: 2 -> 3 >> Nov 18 23:57:33 localhost NetworkManager: <info> Setting system >> hostname to 'localhost.localdomain' (no default device) >> Nov 18 23:57:33 localhost NetworkManager: <WARN> >> set_system_hostname(): set_system_hostname: couldn't set the system >> hostname to 'localhost.localdomain': (1) Operation not permitted >> Nov 18 23:57:33 localhost NetworkManager: <info> (eth0): carrier now >> OFF (device state 3) >> Nov 18 23:57:33 localhost NetworkManager: <info> (eth0): device state >> change: 3 -> 2 >> Nov 18 23:57:33 localhost NetworkManager: <info> (eth0): deactivating >> device (reason: 40). >> Nov 18 23:57:33 localhost NetworkManager: <info> Setting system >> hostname to 'localhost.localdomain' (no default device) >> Nov 18 23:57:33 localhost NetworkManager: <WARN> >> set_system_hostname(): set_system_hostname: couldn't set the system >> hostname to 'localhost.localdomain': (1) Operation not permitted >> Nov 18 23:57:33 localhost NetworkManager: <info> Setting system >> hostname to 'localhost.localdomain' (no default device) >> Nov 18 23:57:33 localhost NetworkManager: <WARN> >> set_system_hostname(): set_system_hostname: couldn't set the system >> hostname to 'localhost.localdomain': (1) Operation not permitted >> Nov 18 23:57:36 localhost kernel: sky2 eth0: Link is up at 100 Mbps, >> full duplex, flow control both >> Nov 18 23:57:36 localhost kernel: ADDRCONF(NETDEV_CHANGE): eth0: link >> becomes ready >> Nov 18 23:57:36 localhost NetworkManager: <info> (eth0): carrier now >> ON (device state 2) >> Nov 18 23:57:36 localhost NetworkManager: <info> (eth0): device state >> change: 2 -> 3 >> Nov 18 23:57:36 localhost NetworkManager: <info> Setting system >> hostname to 'localhost.localdomain' (no default device) >> Nov 18 23:57:36 localhost NetworkManager: <WARN> >> set_system_hostname(): set_system_hostname: couldn't set the system >> hostname to 'localhost.localdomain': (1) Operation not permitted >> Nov 18 23:57:37 localhost acpid: client connected from 2323[0:500] >> Nov 18 23:57:37 localhost kernel: ACPI: PCI Interrupt 0000:00:02.0[A] >> -> GSI 16 (level, low) -> IRQ 16 >> Nov 18 23:57:40 localhost kernel: [drm] Initialized drm 1.1.0 20060810 >> Nov 18 23:57:40 localhost kernel: [drm] Initialized i915 1.6.0 >> 20060119 on minor 0 >> Nov 18 23:57:51 localhost gconfd (nogradi-2427): starting (version >> 2.20.1), pid 2427 user 'nogradi' >> Nov 18 23:57:51 localhost gconfd (nogradi-2427): Resolved address >> "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only >> configuration source at position 0 >> Nov 18 23:57:51 localhost gconfd (nogradi-2427): Resolved address >> "xml:readwrite:/home/nogradi/.gconf" to a writable configuration >> source at position 1 >> Nov 18 23:57:51 localhost gconfd (nogradi-2427): Resolved address >> "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only >> configuration source at position 2 >> Nov 18 23:57:55 localhost NetworkManager: <WARN> >> system_settings_get_unmanaged_devices_cb(): >> system_settings_get_unmanaged_devices_cb: Error getting unmanaged >> devices from the system settings service: (4) Did not receive a reply. >> Possible causes include: the remote application did not send a reply, >> the message bus security policy blocked the reply, the reply timeout >> expired, or the network connection was broken. >> Nov 18 23:57:55 localhost NetworkManager: <WARN> >> system_settings_get_hostname_cb(): system_settings_get_hostname_cb: >> Error getting hostname from the system settings service: (4) Did not >> receive a reply. Possible causes include: the remote application did >> not send a reply, the message bus security policy blocked the reply, >> the reply timeout expired, or the network connection was broken. >> Nov 18 23:57:55 localhost NetworkManager: <WARN> >> list_connections_cb(): Couldn't retrieve connections: Did not receive >> a reply. Possible causes include: the remote application did not send >> a reply, the message bus security policy blocked the reply, the reply >> timeout expired, or the network connection was broken.. >> Nov 18 23:58:24 localhost NetworkManager: <WARN> >> connection_get_settings_cb(): connection_get_settings_cb: Invalid >> connection: 'NMSettingConnection' / 'uuid' invalid: 2 >> Nov 18 23:58:24 localhost NetworkManager:last message repeated 173 times >> Nov 18 23:58:24 localhost NetworkManager: <WARN> one_property_cb(): >> Ignorning invalid property 'eap' >> Nov 18 23:58:24 localhost NetworkManager: <WARN> one_property_cb(): >> Ignorning invalid property 'identity' >> Nov 18 23:58:24 localhost NetworkManager: <WARN> >> connection_get_settings_cb(): connection_get_settings_cb: Invalid >> connection: 'NMSettingConnection' / 'uuid' invalid: 2 >> >> >> Does this ring any bells? > > Yeah, first thing to try to isolate the issue is: > > setenforce 0
Hi Dan, I tried this and didn't fix the problem. Did a 'setenforce 0', then restarted the network, restarted NM and nm-applet, but it still wouldn't connect. When the 'Wired Network' radio button is clicked on nm-applet I get the following in the console: ** Message: Found connection 'Auto Ethernet' to activate at /org/freedesktop/NetworkManagerSettings/0. ** (nm-applet:3839): WARNING **: <WARN> activate_device_cb(): Device Activation failed: Method "ActivateDevice" with signature "osoo" on interface "org.freedesktop.NetworkManager" doesn't exist Since this fedora is still version 8, I will probably upgrade to 12 and be done with it. It's just so weird that something like this would happen :) Cheers, Daniel > Since it looks to be SELinux related. If that makes NM work, then: > > yum update selinux-policy* > > to get the latest policy, then: > > touch /.autorelabel > > and reboot. It may be that messing around somewhere messed up selinux > file labels, the files got the wrong context, and now some operations > are denied. Let me know. -- Psss, psss, put it down! - http://www.cafepress.com/putitdown _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
