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.

Unrelated to this, did you lock down your other blog? It tells me I’m not invited. It’s okay if that’s what you intended, just thought I’d ask in case it’s not.

Oh, and Amsterdam rocks. Hope you get to go there.

X-Men kolmosta pidetään käsittääkseni kolmikon heikoimpana, vaikka minä kyllä nautin siitä ihan siinä missä kahdesta aiemmastakin… Joo, kyllä (piti tässä välissä varmistaa omista muistiinpanoista tuo, jotten tulisi puhuneeksi itseni kanssa ristiin. Mitä siitäkin nyt tulisi jos yhdessä kohtaa Internetiä sanoisi yhtä ja toisessa toista!) Ja näköjään et sinäkään jaa tuota yleistä mielipidettä sen kuruudesta.

First Class on minulta vielä näkemättä, samoin se Wolverinen oma seikkailu (Origins?). Niin ja Hämis kolmonen. Viimeisen kohdalla ilmeisesti hyvä niin, kun kerta olet sinäkin samaa mieltä yleisen mielipiteen kanssa.

Daredevilia välttäisin sinuna kuin ruttoa. Myönnettäköön, että yritin itse katsoa sitä masennukseni ollessa syvimmillään, mikä ehkä hieman häiritsi keskittymis- ja arvostelukykyäni, mutta ei se ainakaan vointiani yhtään parantanut, se on asia mikä on varma.

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.)

I’ve specified three different specific cases to demonstrate what I mean by the title, below. I could have filed three different bite-sized bugs, but all in all I believe they are part of the generic accessibility problem with the ’Revert’ button that could be fixed in one go. (If the developers think otherwise, I’ll be happy to split this into different reports.)

When you first run Software Sources, ’Revert’ is ghosted as it probably should, implying no changes have been made that could be reverted.

Issue #1:
Steps to reproduce:
When Download from: is pointing at main servers, change it to something else and ’Revert’ becomes active. Now click ’Revert’, and main servers are restored as Download from: site.

What happens:
’Revert’ stays active, implying there are still changes left to revert. Clicking it does nothing of course, as all changes have just been reverted.

What should happen:
’Revert’ should become ghosted once pressed after becoming active.

Issue #2:
Steps to reproduce:
Point Download from: to your local mirror (other than main servers). Close Software Sources. Start it again. ’Revert’ is now ghosted, implying there are again no changes to be reverted. Point Download from: to a third mirror, and ’Revert’ becomes active. Click ’Revert’.

What happens:
Download from: now points to main servers.

What should happen:
I’d expect it to point to my local mirror, which was the initial state opening the window.

Issue #3:
Perhaps ’Revert’ wrt the Download from: site means not reverting back to initial state of this SS session, but reverting back to the very initial state of pointing to main servers. But in that case, ’Revert’ should *not* be ghosted when Software Sources starts with Download from: pointing somewhere else, as it just did.

Python-gobject 3.0.3-2 here and I’m able to reproduce this. I haven’t got an exact recipe for it, but enough wiggling around in software sources (with the mirror and such) seems to bring it on. I *think* it happens only when I finally close the window and not before. I’ll keep looking for the exact steps, but I’m pretty confident this is still unfixed, as apport always points me to this report.

@Roger: Thanks for the solution. On Ubuntu Precise, GMM 1.0.23.1334-r0 seems to use /usr/local/share/applications instead of /usr/share/applications for the desktop file (there’s also a copy in /opt/google/musicmanager/, but it’s apparently just used for installing the effective file into /usr/local/).

@Nuno: I’m not sure I see the point of encrypting the application-specific password, and then be prompted to enter the key for decrypting the password. Isn’t it more straightforward to just specify the application-specific password when GMM prompts you to? Actually, with the caveat that specifying the password on the commandline means exposing it to trusted users, isn’t having GMM prompt for it a *better* solution securitywise? I guess you do get the benefit of getting to specify your own password which can be as easily memorizable as you dare use though (the application-specific passwords are difficult). Instead of OpenSSL I’d probably use GNOME Keyring, as it gets unlocked during login without an extra prompt for another password. Then pick the key for GMM using gkeyring.

FTFY.