By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.

Bug 521

Summary:	Trinity networking breaks with network-manager 0.9
Product:	TDE	Reporter:	Philip Ashmore <contact>
Component:	tdenetwork	Assignee:	Timothy Pearson <kb9vqf>
Status:	RESOLVED FIXED
Severity:	normal	CC:	bugwatch, contact, darrella, kb9vqf, neptunia
Priority:	P5
Version:	3.5.12 [Trinity]
Hardware:	amd64
OS:	Debian Squeeze
Compiler Version:		TDE Version String:
Application Version:		Application Name:

Description Philip Ashmore 2011-09-26 03:48:54 CDT

I'm running Squeeze/Wheezy.
I ran synaptic to update and along came network-manager-0.9.0-2 (testing)
I had network-manager-0.8.1-6+squeeze1 installed.

Quoting Michael Biebl (Debian)
It appears that the user session agent (nm-applet and pnm) need to be updated for NM 0.9 to provide the necessary secrets (passwords/keys) to NM.

See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642784
for the details.

Comment 1 Timothy Pearson 2011-09-26 03:54:06 CDT

Assigning to Ilya Chernykh, the OpenSUSE maintainer, as KNetworkManager was originally an OpenSUSE project and I suspect that they will be able to repair it faster than the TDE project can alone.

Also, for now remember that only Squeeze is supported; trying to merge in Wheezy packages can cause unexpected problems such as this one.

Comment 2 Timothy Pearson 2011-10-06 17:26:47 CDT

Ilya, any progress on this?  If you have something working in OpenSUSE feel free to share the link to your patch.

Comment 3 Timothy Pearson 2011-10-07 13:45:00 CDT

See http://projects.gnome.org/NetworkManager/developers/api/09/ref-migrating.html#id428142 for details on what has changed in NM API 0.9, specifically the removal of the user settings service ("Elimination of the User Settings Service" in the link).

Comment 4 Ilya 2011-11-11 15:03:16 CST

I am not a Trinity developer. I will not fix it in Trinity.

Comment 5 Timothy Pearson 2011-11-11 15:06:18 CST

(In reply to comment #4)
> I am not a Trinity developer. I will not fix it in Trinity.

Which according to your own comments indicate you will not fix it in your obsolete, broken KDE3:KDE3 repository either.

Fine.

Comment 6 Ilya 2011-11-11 15:08:31 CST

KDE:KDE3 repository is not broken and not obsolete.

Comment 7 Timothy Pearson 2011-11-11 15:13:27 CST

(In reply to comment #6)
> KDE:KDE3 repository is not broken and not obsolete.

It does not support networkmanager API 0.9, therefore it IS broken in this area.

Keep the politics off the bug reports please, and don't mislead us into thinking you are actually going to work on fixing a problem in you repository (which would port quite easily to TDE) when you in fact have no plans to.

Comment 8 Ilya 2011-11-11 15:18:58 CST

Okay. Let's wait for somebody who can help. May be Sergei Amelian can do it.

Comment 9 Timothy Pearson 2012-09-11 01:54:04 CDT

A new NetworkManager-0.9 compatible backend and ported tdenetworkmanager client are now available in GIT.  If defects exist in these new software libraries and/or applications, please open new bug reports for those defects.

Thanks for reporting!

Comment 10 Philip Ashmore 2012-10-11 20:09:14 CDT

I just tried to install network-manager-kde-trinity but it failed as it has a Depends: network-manager (<0.8.9).

How do I build trinity from git, and how do I tell which git version is associated with the current 3.5.13.1 SRU release?

Comment 11 Philip Ashmore 2012-10-11 21:26:42 CDT

Re: "How do I build trinity from git"

What I'm looking for is a build script that I can use regularly.

I know there are instructions to do this manually but such a script must exist for automated builds.

A variant that just builds it for direct installation/removal would help out too.

My SourceForge projects all use a makefile that can build a Debian/Ubuntu package in debug or release mode, and also from git, so the script just decides which order to build/install them in, and does the reverse for removal, so I'd be looking for something along those lines.

For the next release, each package has a "v3c-local" target since it already knows which other packages it needs, putting inter-package dependencies under version control.

Just my 2c.