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 2280

Summary:	network-manager-tde connections lost after upgrade
Product:	TDE	Reporter:	linux
Component:	tdenetwork	Assignee:	Timothy Pearson <kb9vqf>
Status:	RESOLVED WONTFIX
Severity:	major	CC:	bugwatch, linux, michele.calgaro
Priority:	P5
Version:	R14.0.x [Trinity]
Hardware:	Other
OS:	Linux
Compiler Version:		TDE Version String:
Application Version:		Application Name:
Attachments:	tdenetworkmanagerrc

Description linux 2014-12-28 14:44:50 CST

After upgrading to Trinity R14, TDENetworkManager does not show any previously configured connections - they're lost. They're still present in ~/.trinity/share/config/tdenetworkmanagerrc but not available.

Newly configured connections are saved as network-manager system-connections. Maybe there should be a script to convert connections from tdenetworkmanagerrc to network-manager.

Comment 1 Michele Calgaro 2018-11-10 09:52:23 CST

Are you able to attach a sample version of ~/.trinity/share/config/tdenetworkmanagerrc for using as a test file? Feel free to remove whatever is not important.

Comment 2 linux 2018-11-14 12:26:44 CST

Created attachment 2907 [details]
tdenetworkmanagerrc

Found this on one of my machines.

Comment 3 Michele Calgaro 2018-11-15 07:38:00 CST

Thank you. 
knetworkmanager pre-R14.0.0 and tdenetworkmanager are very different. I will see if a conversion can be done.

Comment 4 linux 2018-11-16 09:25:52 CST

It's probably not worth it 4 years later. I doubt there are (m)any users still running pre-R14 Trinity.

Comment 5 Michele Calgaro 2020-02-05 19:45:10 CST

> It's probably not worth it 4 years later. I doubt there are (m)any users still
> running pre-R14 Trinity.
I have to agree with your view. Given the most likely users are already on R14.0.x, lot of years have gone by and that there are definitely bigger priorities to work on, it is not really worth investing time fixing this bug anymore. I am unwillingly closing this bug as wontfix :-(