There is nothing specific except 'should be fixed with current git'
It's too late in the cycle to just pull all the stuff in there, please try to find out the specific commits so we can apply them, I'll set you up with fixed rpms to test then.

Yet another mobile broadband networking deficiency in KDE:
https://bugs.kde.org/show_bug.cgi?id=266807

(In reply to comment #1)
> There is nothing specific except 'should be fixed with current git'
> It's too late in the cycle to just pull all the stuff in there, please try to
> find out the specific commits so we can apply them, I'll set you up with fixed
> rpms to test then.

sadly I'm not familiar with git and other development tools. KDE 4.6.1 would probably solve the problem. Which KDE version will be included in 11.4 final?

You can ask the developer to please point out specific important commits, he knows best about this.
4.6.0 will be shipped on 11.4, only important fixes allowed now.

https://bugs.kde.org/show_bug.cgi?id=256031#c6

This I what I got: https://bugs.kde.org/show_bug.cgi?id=256031#c6

It's true in fact that the NM version used by KDE repositories of openSUSE didn't advance for months.

Oh boy, looks like we forget :-/

Please add http://download.opensuse.org/repositories/KDE:/Unstable:/Playground/openSUSE_Factory/ and update all the networkmanager related stuff from there and test, this is a clone from 19th of january. We are nearing 11.4 release so let's hope for some good results :-)

Tamás time is an issue here, rc2 tag is on friday, so for an updated networkmanager plasmoid we need feedback from you.

(In reply to comment #7)
> Tamás time is an issue here, rc2 tag is on friday, so for an updated
> networkmanager plasmoid we need feedback from you.


I'm testing it. The crash described by this bugreport still happens with the updated version.

There is another crash condition ( https://bugs.kde.org/show_bug.cgi?id=266818 ) which doesn't happen on openSUSE 11.3 in spite of the fact that I'm using the same kde networkmanagement version as in the plain 11.4 RC1. Interestingly this new crash remained even after upgrading 11.4 kde networkmanagement to 0.9.1git20110127. So, the problem may hide in deeper layers KDE/Qt.

Otherwise the update networkmanagement doesn't seem to be worse than the original. It's a bit more aesthetic and intuitive but practically still unusable with mobile broadband devices.

I will continue testing it and will give more feedback in tens of hours.

ah ok sorry for the panic, no chance to get it into 11.4 anyways I was just told, we'll ship a more recent snapshot per online update I guess, we will also get better test coverage by moving it in a more widely used repository.

(In reply to comment #9)
> no chance to get it into 11.4

http://www.totallyfuzzy.net/ourtube/beethoven/symphony-no-7-2nd-movement-video_738152adf.html

*** Bug 673599 has been marked as a duplicate of this bug. ***

I have to disagree with the decision to ship a fix after the official release, it seems like usual behavior to ship broken stuff; if it does not work we should just remove or disable the UI, in this case the "Mobile Broadband" tab should go away, or at least gray the "Add" button. It makes the user lose a lot of time and energy trying to find a cause for the problem, and in the end they just fall back to other distros/versions. I can say because I have been there.

Looks like the problem comes from upstream, but this is being shipped here as a supported option.

As a bare minimum, the release notes for the final product should list this kind of known issues. I have added an entry for this bug in http://en.opensuse.org/openSUSE:Most_annoying_bugs_11.4_dev

The mobile broadband connection can be set up, and then works as it used to do in 11.3, by manually editing knetworkmanager configuration. That is what I did:

0. Have a look and get barely familiar with knetworkmanager configuration files; I would recommend adding some connections (wifi or wired or something) and watching what happens under the hood:
  ~/.kde4/share/config/networkmanagementrc
  ~/.kde4/share/apps/networkmanagement/connections/

1. Log off the user in X (not sure if this is actually required)

2. Copy an old connection file (or prepare a new one) in the connections directory, e.g.:

  # contents of ~/.kde4/share/apps/networkmanagement/connections/{baacee48-1409-4907-8fed-0be2ff3add46}
[connection]
autoconnect=false
icon=phone
id=Pepephone
timestamp=2011,2,26,20,53,45
type=gsm
uuid={baacee48-1409-4907-8fed-0be2ff3add46}

[gsm]
apn=gprs.pepephone.com
band=0
networkid=
networktype=0
number=*99#
username=

[ipv4]
addresses=
dhcpclientid=
dhcphostname=
dns=
dnssearch=
ignoreautoroute=false
ignoredhcpdns=false
method=Automatic
neverdefault=false
routes=

[ppp]
baud=0
crtscts=false
lcpechofailure=0
lcpechointerval=0
mppestateful=false
mru=0
mtu=0
noauth=false
nobsdcomp=false
nodeflate=false
novjcomp=false
refusechap=false
refuseeap=false
refusemschap=false
refusemschapv2=false
refusepap=false
requiremppe=false
requiremppe128=false

[serial]
baud=115200
bits=8
parity=None
senddelay=0
stopbits=1

  # end of ~/.kde4/share/apps/networkmanagement/connections/{baacee48-1409-4907-8fed-0be2ff3add46}

3. Add a definition and a reference to this connection in ~/.kde4/share/config/networkmanagementrc

  ## connection definition
[Connection_{baacee48-1409-4907-8fed-0be2ff3add46}]
LastUsed=2011,2,26,20,54,7
Name=Pepephone
Type=gsm

  ## append a comma and the ID (with curly braces) to the Connections variable in [General] section
[General]
Connections={d7b90f22-d183-488e-a358-6b9e062cde5b},{98e415e6-e0cb-496e-9ccd-e1114cc92511},{9615439a-fc98-470c-a124-c9cbc8360713},{ef2b1151-1c30-4ee8-bd9d-817f9ab56121},{baacee48-1409-4907-8fed-0be2ff3add46}

4. Log in again and try to connect -- keep an eye on tail -f /var/log/NetworkManager

5. The connection details can now be edited on the GUI, you probably want to enter the PIN etc.

cheers!

(In reply to comment #12)

I agree with you. You can't publish a version that contains such bugs! Set up a mobile connection works like a charme with the first eee-pc some years ago! I can't understand why it is not possible to support this essential feature?

We are too late in the cycle to change stuff like that, after rc1 there will only be really urgent fixes. No one complained before that.

Feel free to use the gnome applet for now, as this is developed by networkmanager team they don't have to continously play catch up.

(And yes, 11.4 be published with a bug like that)

(In reply to comment #15)
> We are too late in the cycle to change stuff like that, after rc1 there will
> only be really urgent fixes. No one complained before that.
> 
> Feel free to use the gnome applet for now, as this is developed by
> networkmanager team they don't have to continously play catch up.
> 
> (And yes, 11.4 be published with a bug like that)

Well I understand that the release workflow is not to be discussed here but then I would insist in referring to this bug on the release notes document.

I don't know what qualifies for release notes, coolo could you drop a short note please? Is the release workflow documented anywhere already?

we do not really list known bugs in the release notes, but in the wiki. That's much more dynamic and editable by all. If you think this bug deserves a special mentioning, open a new bug for component "Release Notes" - I suggest to leave this bug for the actual problem.

And it would be really great if people started testing before RC2 ;(

nm-applet is not a workaround. When KDE is running, nm-applet will not start:

marcel@linux-mur9:~> nm-applet 
** Message: applet now removed from the notification area

** (nm-applet:30560): WARNING **: get_all_cb: couldn't retrieve system settings properties: (2) The name org.freedesktop.NetworkManagerSystemSettings was not provided by any .service files.
** Message: applet now embedded in the notification area

** (nm-applet:30560): WARNING **: Fallback icon 'gtk-dialog-error' missing: (0) Symbol »gtk-dialog-error« nicht im Thema vorhanden
**
ERROR:applet.c:2800:nma_icons_reload: assertion failed: (applet->fallback_icon)
Abgebrochen

OpenSuSE 11.4 Final will not be able to connect to mobile networks? This is something essential. Wondering what "really urgent" fixes are, if not something that does breaks essential functionality which was working before?

11.4 is announced to be an excellent choice for netbooks and mobile devices. Read the news on OpenSuSE and KDE ( http://news.opensuse.org/2011/03/02/opensuse-11-4-and-kde-2/ ). It's a whole paragraph at the beginning of the news.

Sorry, but without mobile networking.. this sounds like a joke. This post is not meant to blame anyone, OpenSuSE is a great peace of software. It's OSS and you are doing an excellent job.

I am able to edit my config files by hand, so no problem on my side. But my oppinion is that OpenSuSE is a desktop distribution used by a lot of people that are not that experienced - and they will receive a bad experience with 11.4.

Well nobody tested it before 11.4rc1 and this shows it's not as important to most people as you make it sound, right before goldmaster there is tons of bugreports where people tried the next release for the first time and come up with unaccaptable bugs that have to be fixed before release =(
Help out testing the newer networkmanager-kde4 bundle, the more feedback the easier we get this into the update queue.

Also there is a usable simple workaround so it's no shipstopper, and no I am not happy about that myself.

(In reply to comment #21)
> Well nobody tested it before 11.4rc1 and this shows it's not as important to
> most people as you make it sound, right before goldmaster there is tons of
> bugreports where people tried the next release for the first time and come up
> with unaccaptable bugs that have to be fixed before release =(

Yes - unfortunately this bug did not show up earlier. But not sure if this shows that it is not important. My explanation would be that people affected by this bug need to work with their machines and are not adventurous enough to put alpha releases onto their notebooks.

> Help out testing the newer networkmanager-kde4 bundle, the more feedback the
> easier we get this into the update queue.

Where to get the newer bundle that needs testing? The one in Factory? 
 
> Also there is a usable simple workaround so it's no shipstopper, and no I am
> not happy about that myself.

Yeah - like mentioned before its no real problem to me or any other experienced user. Just a little inconvenience. Newbies or standard users - well, they install a distribution and want it to work, especially if it is something that worked before.

But sure - there is no sense to argue further. The die is cast. Let's make the best out of it.

Usually from KDE:Unstable:Playground but that is also quite outdated, please wait for the 11.4 release so all the repos will be reactivated and we can get some work done

With the version in playground (0.9.1.60git.1299449104-1.1) this works again!

not quite!
i also updated to kde 4.6.1 via official repository 
http://download.opensuse.org/repositories/KDE:/Release:/46/openSUSE_11.4/x86_64/
then i added the playground networkmanager stuff
my broadband connection works but there is no user interface 4 it. also it only works when i create it via wizzard. a manual created connection does not work.
when i set the connection to connect automatically it works. but there is no way to activate it / deactivate it manually.
thats not quite what it should be like.

do you need any further infos?

*** Bug 690329 has been marked as a duplicate of this bug. ***

(In reply to comment #9)
> ah ok sorry for the panic, no chance to get it into 11.4 anyways I was just
> told, we'll ship a more recent snapshot per online update I guess, we will also
> get better test coverage by moving it in a more widely used repository.

This didn't happen yet. Even http://download.opensuse.org/repositories/KDE:/Release:/46/openSUSE_11.4 still has the ages old knetworkmanager software. Aren't you planning updating it?

In openSUSE 11.4 with KDE 4.7 Beta 1 from Unstable KDE repository still not fixed

plasmoid-networkmanagement-0.9.2.60git.1308963099-15.1.i586.rpm from Playground works quite stable with a deactivated PIN query.

If the PIN code query is activated KDE4 will extremly slow down with nearly 100% CPU time (used by the KDE4 process). Sometimes a windows for entering the PIN code pops up, but sometimes this window just only remains in a complete gray color and nothing more happens. Best workaround to avoid this is to deactivate the PIN code query on the SIM card.

I can confirm that bringing up a mobile broadband connection (USB Huawei E220) does work with NetworkManager-gnome 0.8.2-9.10.1 in the gnome desktop even for SIMs with activated PIN -- and also in KDE!
Maybe it is important to answer the dialog window with the request for PIN as soon as possible (root password is necessary in the next dialog window...).

Maybe important the list of NetworkManager rpms I got installed:
NetworkManager-openvpn-gnome-0.8.2-6.1.x86_64
NetworkManager-kde4-libs-0.9.svn1192577-7.2.x86_64
NetworkManager-vpnc-lang-0.8.2-4.1.noarch
NetworkManager-gnome-0.8.2-9.10.1.x86_64
NetworkManager-openvpn-0.8.2-6.1.x86_64
NetworkManager-doc-0.8.2-15.24.1.x86_64
NetworkManager-pptp-0.8.2-4.1.x86_64
NetworkManager-gnome-lang-0.8.2-9.10.1.noarch
NetworkManager-0.8.2-15.24.1.x86_64
NetworkManager-vpnc-gnome-0.8.2-4.1.x86_64
NetworkManager-lang-0.8.2-15.24.1.noarch
NetworkManager-pptp-lang-0.8.2-4.1.noarch
NetworkManager-vpnc-0.8.2-4.1.x86_64
NetworkManager-glib-0.8.2-15.24.1.x86_64
NetworkManager-openvpn-lang-0.8.2-6.1.noarch
NetworkManager-pptp-gnome-0.8.2-4.1.x86_64
plasmoid-networkmanagement-0.9.1git20110503-8.1.x86_64

(In reply to comment #30)
> I can confirm that bringing up a mobile broadband connection (USB Huawei E220)
> does work with NetworkManager-gnome 0.8.2-9.10.1 in the gnome desktop even for
> SIMs with activated PIN -- and also in KDE!
> Maybe it is important to answer the dialog window with the request for PIN as
> soon as possible (root password is necessary in the next dialog window...).
> 
snip]
> plasmoid-networkmanagement-0.9.1git20110503-8.1.x86_64

I'm sorry it was to good to be true :-(
It worked until I had to reboot (it did survive hibernate, but not the reboot)
then I had to deinstall plasmoid-networkmanagement to make any connection...

Now I have best results with the command line client nmcli ...

http://euroquis.nl/bobulate/?p=1211 suggests that it does not crash if one installs mobile-broadband-provider-info.

Yes, installing mobile-broadband-provider "solves" the issue.

Of course the real solution still is:

- make knetworkmanger robust enough so does it does not crash if there is no data, the user could still make manual configurations

- declare a suitable dependency that mobile-broadband-provider-info gets installed to all systems with knetworkmanager by default.

this should have been closed ages ago.
11.4 is dead
works without problems nowadays...

Alin