Bug 244150

Summary:	Monolithic knetworkmanager does not show connections under KDE 4.5 RC1
Product:	knetworkmanager	Reporter:	Andrey Borzenkov <arvidjaar>
Component:	general	Assignee:	Will Stephenson <wstephenson>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	adrien.futschik, antonio.guadagnin, grzesiekw, johann-nikolaus, lamarque, llg, zarzych
Priority:	NOR
Version:	0.9
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:

Description Andrey Borzenkov 2010-07-10 19:40:28 UTC

Version:           0.9 (using Devel) 
OS:                Linux

After update to 4.5RC1 the knetworkmanager stopped showing connections. It shows two empty menu lines where I previously did have connection name (I am not sure what second line is, I have only one connection defined). Moving mouse visually selects line. Clicking it does nothing. It makes it impossible to initiate connection.

The problem was reproduced both using r1084746 compiled under 4.4 and r1148396 compiled under 4.5 RC1.

Reproducible: Always

Comment 1 Johann-Nikolaus Andreae 2010-07-29 15:26:00 UTC

I can confirm this bug with 4.5 rc2 and rc3

Comment 2 grzesiekw 2010-07-30 22:42:14 UTC

I have the same effect like described in comment 0 on OpenSuse 11.3 with Factory KDE (4.4.95). Network Manager is unusable right now.

Comment 3 antonio.guadagnin 2010-08-22 11:51:19 UTC

I confirm this bug on Opensuse 11.3 with KDE4 Factory repository.

Also, I tried to upgrade knetworkmanager to KDE4 Playground repository like suggested here: 
http://forum.kde.org/viewtopic.php?f=18&t=89599

but problem still occurs.


List installed packages:

NetworkManager-openvpn-0.8-3.1.i586
NetworkManager-kde4-0.9.svn1166287-1.1.i586
NetworkManager-kde4-libs-0.9.svn1166287-1.1.i586
NetworkManager-vpnc-kde4-0.9.svn1166287-1.1.i586
NetworkManager-gnome-0.8-5.1.i586
NetworkManager-openvpn-kde4-0.9.svn1166287-1.1.i586
NetworkManager-pptp-kde4-0.9.svn1166287-1.1.i586
NetworkManager-pptp-0.8-3.1.i586
NetworkManager-vpnc-0.8-3.1.i586
NetworkManager-glib-0.8-8.1.1.i586
NetworkManager-kde4-lang-0.9.svn1166287-1.1.noarch
NetworkManager-0.8-8.1.1.i586
libproxy0-networkmanager-0.3.1-2.2.i586
libproxy1-networkmanager-0.4.3-1.3.i586

Comment 4 A. Futschik 2010-08-31 23:06:10 UTC

I confirm this bug on Fedora 13 x86_64 & KDE 4.5.1, Qt 4.6.3

with the following packages:

knetworkmanager-0.9-0.20.20100603.fc13.x86_64
system-config-network-tui-1.6.0-2.fc13.noarch
NetworkManager-glib-0.8.1-4.git20100817.fc13.x86_64
knetworkmanager-libs-0.9-0.20.20100603.fc13.x86_64
system-config-network-1.6.0-2.fc13.noarch
NetworkManager-0.8.1-4.git20100817.fc13.x86_64
kdenetwork-4.5.1-0.1.fc13.x86_64
kdenetwork-libs-4.5.1-0.1.fc13.x86_64

Comment 5 llg 2010-09-01 15:50:18 UTC

Same problem on Fedora 13 x86_64 & KDE 4.5.1 with qt-4.7.0-0.27.rc1.
Reproducible: Always

Regards
llg

Comment 6 Lamarque V. Souza 2011-05-08 20:19:47 UTC

The monolithic knetworkmanager is unmaintained, use the plasmoid version instead. Preferrably a recent version, there have been several bugs fixed in the last two months.