Bug 490670 - NetworkManager fails to start after update
Summary: NetworkManager fails to start after update
Status: RESOLVED NORESPONSE
Alias: None
Product: openSUSE 11.1
Classification: openSUSE
Component: Network (show other bugs)
Version: Final
Hardware: i586 openSUSE 11.1
: P5 - None : Major with 5 votes (vote)
Target Milestone: ---
Assignee: Tambet Ingo
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-31 11:48 UTC by Andrei Zhekov
Modified: 2009-12-02 09:32 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrei Zhekov 2009-03-31 11:48:46 UTC
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; ru; rv:1.9.0.8) Gecko/2009032600 SUSE/3.0.8-1.1 Firefox/3.0.8

OpenSuSE 11.1
After my last update NetworkManager filed to start. I ran the "nm-applet" application in the console and I got the following output:

** (nm-applet:10421): WARNING **: <WARN>  applet_dbus_manager_start_service(): Could not acquire the NetworkManagerUserSettings service as it is already taken.  Return: 3


Reproducible: Always

Steps to Reproduce:
1. Install all updates for OpenSuSE 11.1
2. Reboot (with new kernel)
3. ...and the icon in the tray is gone
4. Try to run the nm-applet in the console: fails
Actual Results:  
NetworkManager doesn't work. Can't launch dsl internet connection previously configured in it. No local and Internet connection. The only thing I can do is managing the network interfaces with old ifup/ifdown thing and installing Kinternet, for example.

Expected Results:  
Working NetworkManager
Comment 1 Andrei Zhekov 2009-03-31 12:07:52 UTC
0.7.0.r4359-15.1.1 - the version of NM
Comment 2 Andrei Zhekov 2009-03-31 12:55:47 UTC
Today also I get a little bit different output when running as root:

cherokee:/home/tux # nm-applet 
libnotify-Message: Unable to get session bus: 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.
Ошибка системы GConf: Сбой при контакте с сервером конфигурации; среди возможных причин то, что необходимо включить сетевые возможности TCP/IP для ORBit, или то, что остались старые блокировки NFS из-за краха системы. Для получения информации смотрите http://www.gnome.org/projects/gconf/ . (Подробно -  1: Не удалось подсоединиться к сеансу: 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.)

** (nm-applet:11548): WARNING **: <WARN>  applet_dbus_manager_start_service(): Could not acquire the NetworkManagerUserSettings service as it is already taken.  Return: 3


(nm-applet:11548): GConf-WARNING **: Directory `/system/networking/connections' was not being monitored by GConfClient 0x812e280
Comment 4 Tambet Ingo 2009-04-14 06:37:41 UTC
The message means that nm-applet is already running and exactly one copy of it can be active. It looks more like NetworkManager process isn't running. Please attach it's log file /var/log/NetworkManager.
Comment 5 Bin Li 2009-12-02 09:32:39 UTC
->noresponse.