![]() However, in any case, Firefox should have a config option that the user can use to tell Firefox not to query NetworkManager upon startup.Ģ. If NetworkManager intends that it is accurately reporting the "online" status of the computer (does it? or does it intend to only report the state of the connections that it is managing?), then I suppose that NetworkManager has a bug. NetworkManager appears not to be running (could not get its state). Get_nm_state(): didn't get a reply from NetworkManager. This caused Firefox 3 to startup in Offline mode, which forced me to manually uncheck File->Work Offline at the beginning of each session.Īs a workaround, I now disable the NetworkManager service before starting Firefox (now nm-tool reports Print_devices(): didn't get a reply from NetworkManager. Therefore, when using the wired interface, I had network access, however, NetworkManager reports no network devices present (the commandline program nm-tool yielded: ![]() On my Debian system, I had the NetworkManager service running, however, my wired network interface was controlled manually (in my case, the relevant entry in /etc/network/ interfaces was "iface eth1 inet static", which prevents NetworkManager from managing that interface).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |