Comment 29 for bug 334122

Clarification: I'm not the maintainer so I can't do much about your problem directly either. I was just suggesting that you submitted more information so that the maintainer can actually see if he/she can do anything about it.

In any case, I think most of us know that the NM widget isn't exactly fully ready yet by now. But it's not as if they just let us run into a brick wall with no way around it. The legacy knetworkmanager still can be used and I was using it to get on 3G quite satisfactorily. Please do use that as a workaround. If even that cannot work, I think it'd be another separate bug report.

But in my limited capacity, let's see if I can help out or not:

1) Your NM widget configuration files are in $HOME/.kde/share/apps/networkmanagement/connections
2) You'll see quite a few files in there, I gather. Run the command "grep Vivo *" to find the configuration file for your 3G connection.
3) It *may* be possible that your phone wasn't initialized properly to dial out so let's compare your NM widget configuration with your knetworkmanager configuration (assuming that you were using that in previous versions of Kubuntu)
4) The knetworkmanager config file is in $HOME/.kde/share/config/knetworkmanagerrc. Open it and be prepared to compare manually.
5) Assuming that you had named your connection "Vivo Internet", search for that string inside the file.
6) For e.g., my connection was called "Celcom3G" and I found that string in a block containing the following:

[ConnectionSetting_lzWk2MQybtGkFIQh_connection]
Type=connection
Value_autoconnect=<bool>false</bool>\n
Value_id=<string>Celcom3G</string>\n
Value_timestamp=<uint32>1241581159</uint32>\n
Value_type=<string>gsm</string>\n
Value_uuid=<string>lzWk2MQybtGkFIQh</string>\n

7) Note the string "lzWk2MQybtGkFIQh" at the top (the string will be different in your case). That is the unique ID for your connection settings.
8) After that, there will be a successive sequence of sections with that same unique ID. E.g.:

[ConnectionSetting_lzWk2MQybtGkFIQh_connection]
[ConnectionSetting_lzWk2MQybtGkFIQh_gsm]
[ConnectionSetting_lzWk2MQybtGkFIQh_ipv4]
[ConnectionSetting_lzWk2MQybtGkFIQh_ppp]
[ConnectionSetting_lzWk2MQybtGkFIQh_serial]

Note that they all share the same unique ID. The contents of those sections constitutes your settings for your connection.

9) Compare those settings in knetworkmanager (which used to work) with the settings in the NM widget's settings file. You should be able to match them by looking at the individual settings' key. If they don't match, modify it (though I'd suggest backing up the original file first).

Try again after that. *Maybe* it'd solve your problem. If you find it too much trouble, well, as I said, try to fall back to knetworkmanager.

I don't wish to get into the whole "ready or not" debate here, it's been argued to death in many other forums.

P.S. to the package maintainer: I did note that the default settings for NM widget 3G connections are markedly different from that of knetworkmanager's. I'm not sure if that is the cause of some modems not being able to dial out but it may be worth looking into.