You’re right: it’s announce-ip and another local script from /etc/network/if-up.d/ (I’m attaching it here) that both seem to trigger this if either is present. This other one’s sort of like the opposite of my announce-ip, there to update /etc/hosts with data from hosts elsewhere on the net my server knows about (that announce themselves with announce-ip). This combination used to work back with ifupdown alpha but now with beta causes the wait.

To clarify: with both scripts removed from if-up.d the 60+ second wait doesn’t appear during boot, but with either script in place the wait is there.

To be sure, I installed the latest ifupdown that’s just appeared in the repos (0.7~beta2ubuntu2) also, and there’s no change compared to 0.7~beta2ubuntu1 (wait is there when the scripts are there).

The question now becomes whether I’ve initially designed the scripts wrong with regards to how things in if-up.d should work, and it just happened to work with the alpha, or did something in ifupdown’s handling of if-up.d change between alpha and beta so that things that should work no longer do.

With my knowledge of things I’d bet on the former, but you can probably enlighten me on this. My assumption’s been that the scripts in if-up.d are run after network interfaces have been brought up.

Sure. This script sources another local file for configuration, but that one’s just a one-line variable declaration for the $URL. (I’m omitting that one because it has my password for the script’s server side.)

Steps to reproduce:
1. Take a screenshot, save it to Pictures. (Works.)
2. Create a subdirectory under Pictures, say Pictures/Test
3. Take a screenshot, save it to Pictures/Test (Works.)
4. Take a screenshot, try to save it directly under Pictures.

What happens:
The directory chooser always picks the ’Test’ subdirectory.

What I expect to happen:
To be able to choose ’Pictures’ as the directory to save my screenshot in.

Workaround:
In the directory chooser, click the pen icon to edit the path. Navigate to parent directory of ’Pictures’. Click to edit the path, make sure you delete the trailing slash (and anything thereafter) from after ’Pictures’, hit enter.

Additional notes:
Maybe this is a general bug of the directory chooser, but without looking, I haven’t come across other apps that make use of it to verify it’s not just Gnome Screenshot that’s affected.

I’m marking this as duplicate of Bug #916631 even though this was filed earlier, as #916631 is triaged and has an upstream bug.

The initctl command apparently needs some additional parameter:

jani@amilo:~$ initctl status
initctl: missing job name
Try `initctl –help’ for more information.
jani@amilo:~$ sudo initctl status
initctl: missing job name
Try `initctl –help’ for more information.

I’ll attach the list of jobs it currently knows about.

Thanks for taking a look Stéphane. Here’s /var/log/syslog, the rest will follow below. And do ask if you need more, it’s no problem for me to reboot or otherwise test things on this laptop, as I also have my main desktop to work with.

Upgrade from 0.7~alpha5.1ubuntu6 to 0.7~beta2ubuntu1 brought this on: on every boot the ”Waiting for network configuration” and ”Waiting up to 60 seconds more for network” messages appear and boot is thus about 2 minutes slower than before. It also says it’s booting without network, but the network is in fact there after I log in.

Downgrading back to 0.7~alpha5.1ubuntu6 makes the wait go away again.

Reproduced this on three different computers on two different networks, both wired and wireless.

I’ve reproduced this on three separate computers, each running Precise.

Steps to reproduce:
1. Start Software Center.
2. From the File menu, choose Sync Between Computers…
3. From the registration window, choose to login to you existing account. Enter your credentials and continue forward.

What happens:
In addition to the window saying you’re now signed in, you also get the registration window. Sync is not available in the main window.

What I expect to happen:
To have only the successful sign-in window appear (i.e. not the registration window again) and have sync working in the main window.

Workaround:
Start the Sync procedure again. Repeat steps 1.-3. above. This time it works as I expect it to: the registration window doesn’t re-appear after entering my credentials, and I get the sync view in the main window.

With both client and the server upgraded to Synergy 1.4.5 Beta from Synergy’s download page, the crash no longer occurs.

This is on Unity 2D and Bug #780803 is at least tangentially related. Synergyc is connected to server through an ssh tunnel (which I set up according to http://ur1.ca/7g6o9#), with client positioned left of the server.

Steps to reproduce:
1. Bring mouse cursor from server screen to client screen.
2. Press Super on server keyboard.
3. Bring mouse cursor back to server screen.

What happens:
Synergyc dies with a segfault:
segfault at 8b0a75c8 ip 0062fbf2 sp bff05108 error 4 in libstdc++.so.6.0.16[5d8000+d8000]

(Also, pressing Super at step 2 brings up launcher on server, not on client – that’s probably Bug #780803 manifesting on U2D.)