On Wednesday, 29 August, 2012 08:25:45 [email protected] wrote: > On Tuesday, 21 August, 2012 10:10:11 [email protected] wrote: > > > > Just had the failure again, and still no supplicant log. > > > > > > On Tuesday, 21 August, 2012 07:53:26 [email protected] wrote: > > > On Monday, 20 August, 2012 09:54:13 you wrote: > > > > > Not enough of the log? I wonder what a reason 4 is? > > > > > > > > "disassociated due to inactivity" > > > > > > > > That can be any number of reasons, if there's any way to get AP logs, > > > > that would help. Otherwise it could be a driver problem. But it's > > > > pretty clear that it's an issue lower than NetworkManager. To figure > > > > that out, we need detailed supplicant debugging logs. You can do this > > > > via the instructions here: > > > > > > > > https://live.gnome.org/NetworkManager/Debugging > > > > > > > > Then we'll get more information about why. > > > > > > I don't have a /var/log/wpa_supplicant.log file, so I edited > > > /usr/share/dbus-1/system-services/fi.w1.wpa_supplicant1.service and added > > > to Exec=: -f /var/log/wpa_supplicant.log, then restarted NetworkManager. > > > > > > Still don't have the log file for some reason, but went ahead and > > > sudo dbus-send --system --print-reply --dest=fi.w1.wpa_supplicant1 > > > /fi/w1/wpa_supplicant1 org.freedesktop.DBus.Properties.Set > > > string:fi.w1.wpa_supplicant1 string:DebugTimestamp variant:boolean:true > > > sudo dbus-send --system --print-reply --dest=fi.w1.wpa_supplicant1 > > > /fi/w1/wpa_supplicant1 org.freedesktop.DBus.Properties.Set > > > string:fi.w1.wpa_supplicant1 string:DebugLevel variant:string:"msgdump" > > > > > > To each it responded with the obtuse: > > > method return sender=:1.12 -> dest=:1.50 reply_serial=2 > > > > > > No idea if debugging will work. > > > Can anyone advise? NM is failing almost every 30 minutes and I have to > restart the daemon.
Nobody knows. Well NM isn't even starting my interfaces on boot, even though I have /etc/rc5.d/S04network-manager. And no one here is willing to even attempt to help with these problems. Clearly NM is as busted as it's always been. _______________________________________________ networkmanager-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/networkmanager-list
