[Desktop-packages] [Bug 924836] Re: network-manager does not tell plymouth it has started

2012-02-02 Thread Launchpad Bug Tracker
This bug was fixed in the package resolvconf - 1.63ubuntu7 --- resolvconf (1.63ubuntu7) precise; urgency=low [ Stéphane Graber ] * Revert change from 1.63ubuntu5 where /etc/resolv.conf would be linkified by the upstart/sysvinit job. This wasn't working as / wasn't necessarily

[Desktop-packages] [Bug 924836] Re: network-manager does not tell plymouth it has started

2012-02-01 Thread Steve Langasek
This has been tracked down to a bug in the resolvconf package, causing /etc/network/if-up.d/000resolvconf to fail and taking the rest of the ifupdown hooks with it. We can't create the initial /etc/resolv.conf symlink from the upstart job when using the live installer, because the job is never run

[Desktop-packages] [Bug 924836] Re: network-manager does not tell plymouth it has started

2012-02-01 Thread Brian Murray
This only happened to me on the first boot so I was unable to get the upstart logs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/924836 Title: network-manager does not tell

[Desktop-packages] [Bug 924836] Re: network-manager does not tell plymouth it has started

2012-02-01 Thread Brian Murray
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/924836/+attachment/2706043/+files/syslog -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.ne

[Desktop-packages] [Bug 924836] Re: network-manager does not tell plymouth it has started

2012-02-01 Thread Brian Murray
I've seen this too: ubuntu@ubuntu-virtual-machine:~$ ls /run/network ifstate ifup.eth0 ubuntu@ubuntu-virtual-machine:~$ cat /etc/network/interfaces auto lo iface lo inet loopback -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network

Re: [Desktop-packages] [Bug 924836] Re: network-manager does not tell plymouth it has started

2012-02-01 Thread Steve Langasek
On Wed, Feb 01, 2012 at 06:04:27PM -, Stéphane Graber wrote: > Can you please give /var/log/syslog and /etc/network/interfaces on the > affected system. Ideally, I'd also need /var/log/upstart/network* from a > boot with --log used on the kernel command line. A listing of /run/network from t

[Desktop-packages] [Bug 924836] Re: network-manager does not tell plymouth it has started

2012-02-01 Thread Stéphane Graber
18:02 < stgraber> slangasek: oh, right, misread the script ... I'll eventually get a clear picture of all that in my head :) right. when lo is brought up, the ifupdown hook should emit static-network-up as all the interfaces are ready 18:03 < stgraber> slangasek: so the questio

[Desktop-packages] [Bug 924836] Re: network-manager does not tell plymouth it has started

2012-02-01 Thread Steve Langasek
> ifupdown never does anything for interfaces that aren't listed in > /etc/network/interfaces Yes, and it doesn't matter, because interfaces not listed in /etc/network/interfaces have no impact on the 'static-network-up' event being issued from /etc/network/if-up.d/upstart. *Only* interfaces that

[Desktop-packages] [Bug 924836] Re: network-manager does not tell plymouth it has started

2012-02-01 Thread Stéphane Graber
Moving back to NM :) ifupdown never does anything for interfaces that aren't listed in /etc/network/interfaces It's Network Manager that's calling the up/post-up scripts through /etc/NetworkManager/dispatcher.d/01ifupdown One of these, /etc/network/if-up.d/upstart emits net-device-up. I did a qu

[Desktop-packages] [Bug 924836] Re: network-manager does not tell plymouth it has started

2012-02-01 Thread Mathieu Trudel-Lapierre
NetworkManager indeed doesn't deal with this kind of signal, nor does it need to, AFAIK. Reassigning to ifupdown, that's my best guess for what goes wrong (need to emit static-network-up AFAICT, as required by the failsafe upstart job, which is what writes this plymouth message). ** Also affects:

[Desktop-packages] [Bug 924836] Re: network-manager does not tell plymouth it has started

2012-02-01 Thread Jean-Baptiste Lallement
it is not specific to alternate and reproducible with Desktop images. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/924836 Title: network-manager does not tell plymouth it ha

[Desktop-packages] [Bug 924836] Re: network-manager does not tell plymouth it has started

2012-02-01 Thread Mathieu Trudel-Lapierre
I'm not entirely sure that's NetworkManager's job, but rather one of the other upstart jobs. Is this happening on all the installs or is it specific to alternate? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu.

[Desktop-packages] [Bug 924836] Re: network-manager does not tell plymouth it has started

2012-02-01 Thread Jean-Baptiste Lallement
confirmed with Ubuntu Desktop. ** Changed in: network-manager (Ubuntu) Importance: Undecided => High ** Changed in: network-manager (Ubuntu) Status: New => Confirmed ** Also affects: network-manager (Ubuntu Precise) Importance: High Status: Confirmed ** Changed in: network-m

[Desktop-packages] [Bug 924836] Re: network-manager does not tell plymouth it has started

2012-02-01 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/924836 ** Tags added: iso-testing -- You received this bug notification because you are a member of Desktop Packages, which