[Bug 293755] Re: [intrepid] network manager has startup race

2010-11-19 Thread Launchpad Bug Tracker
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete = Expired -- [intrepid] network manager has startup race https://bugs.launchpad.net/bugs/293755 You received this bug notification because you

[Bug 293755] Re: [intrepid] network manager has startup race

2009-10-19 Thread Ralph Janke
Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance. --

[Bug 293755] Re: [intrepid] network manager has startup race

2008-11-28 Thread Stephan Trebels
I fixed the double startup problem in /etc/init.d/rc, will report the issue there. The startup race with NetworkManager persists, though, so this was nto the issue. -- [intrepid] network manager has startup race https://bugs.launchpad.net/bugs/293755 You received this bug notification because

[Bug 293755] Re: [intrepid] network manager has startup race

2008-11-28 Thread Stephan Trebels
double startup issue was: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/303074 -- [intrepid] network manager has startup race https://bugs.launchpad.net/bugs/293755 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. --

[Bug 293755] Re: [intrepid] network manager has startup race

2008-11-17 Thread Stephan Trebels
This appears to be in upstart, not network manager. Somehow the rc2 symlinks are started twice, at least I see atd complaining about being started twice as well. Only NetworkManager really fails if being started while running. I suspect that some of the underlying infrastructure like dbus does

[Bug 293755] Re: [intrepid] network manager has startup race

2008-11-06 Thread Stephan Trebels
I traced this part now. It seems that it is not NetworkManager per se, but rather start-stop-daemon complaining that NetworkManager is already running. Now I have to find which other mechanism has started NetworkManager earlier. The rc*.d links look perfectly ok... Looking... This now could be

[Bug 293755] Re: [intrepid] network manager has startup race

2008-11-05 Thread Alexander Sack
its strange, NM should spit out something to syslog. How could it spit out fail when its actually running? ** Changed in: network-manager (Ubuntu) Status: New = Incomplete -- [intrepid] network manager has startup race https://bugs.launchpad.net/bugs/293755 You received this bug

[Bug 293755] Re: [intrepid] network manager has startup race

2008-11-04 Thread Stephan Trebels
** Attachment added: interfaces http://launchpadlibrarian.net/19345771/interfaces -- [intrepid] network manager has startup race https://bugs.launchpad.net/bugs/293755 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs

[Bug 293755] Re: [intrepid] network manager has startup race

2008-11-04 Thread Stephan Trebels
** Attachment added: nm-system-settings.conf http://launchpadlibrarian.net/19345779/nm-system-settings.conf -- [intrepid] network manager has startup race https://bugs.launchpad.net/bugs/293755 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 293755] Re: [intrepid] network manager has startup race

2008-11-04 Thread Alexander Sack
have you checked that the process isnt running at all? maybe it didnt properly connect to dbus on startup or something. If not, do we see the startup failure in some log? -- [intrepid] network manager has startup race https://bugs.launchpad.net/bugs/293755 You received this bug notification

[Bug 293755] Re: [intrepid] network manager has startup race

2008-11-04 Thread Stephan Trebels
I think I'll add a bit of debug to my private version of NetworkManager... I only saw the [fail] on the console, and NetworkManager did certainly run, so did nm-system-settings. I wondered whether dbus or hal were not up properly, yet, at the time NetworkManager was started. The logs are in the