Re: Network-Manager 0.7.2 TLS problem
- From: DAVID ZHOU <zhouwei926 gmail com>
- To: Dan Williams <dcbw redhat com>
- Cc: networkmanager-list gnome org
- Subject: Re: Network-Manager 0.7.2 TLS problem
- Date: Tue, 10 Aug 2010 09:19:51 +0800
Hi Dan,
Thanks very much ! Here is my debug output. My steps is :
1. launch nm-connection-editor through the terminor and add a connection, input the fields I mentioned in the previous mail. Close it.
2. Re-launch the nm-connection editor again and check the connection.
(nm-connection-editor:19238): GLib-CRITICAL **: g_hash_table_foreach: assertion `hash_table != NULL' failed
** (nm-connection-editor:19238): WARNING **: nm_connection_list_new: failed to load VPN plugins: Couldn't read VPN .name files directory /etc/NetworkManager/VPN.
(nm-connection-editor:19238): libglade-WARNING **: unknown property `orientation' for class `GtkVBox'
** (nm-connection-editor:19238): WARNING **: Invalid setting Wireless: ssid
** (nm-connection-editor:19238): WARNING **: Invalid setting Wireless: ssid
** (nm-connection-editor:19238): WARNING **: Invalid setting Wireless Security: Invalid wireless security
** (nm-connection-editor:19238): WARNING **: Invalid setting Wireless Security: Invalid wireless security
** (nm-connection-editor:19238): WARNING **: Invalid setting Wireless Security: Invalid wireless security
** (nm-connection-editor:19238): WARNING **: Invalid setting Wireless Security: Invalid wireless security
** (nm-connection-editor:19238): WARNING **: Invalid setting Wireless Security: Invalid wireless security
** (nm-connection-editor:19238): WARNING **: Invalid setting Wireless Security: Invalid wireless security
** (nm-connection-editor:19238): WARNING **: Invalid setting Wireless Security: Invalid wireless security
** (nm-connection-editor:19238): WARNING **: Invalid setting Wireless Security: Invalid wireless security
** (nm-connection-editor:19238): WARNING **: Invalid setting Wireless Security: Invalid wireless security
** (nm-connection-editor:19238): WARNING **: Invalid setting Wireless Security: Invalid wireless security
** (nm-connection-editor:19238): WARNING **: Invalid setting Wireless Security: Invalid wireless security
** (nm-connection-editor:19238): WARNING **: Invalid setting Wireless Security: Invalid wireless security
** (nm-connection-editor:19238): WARNING **: Invalid setting Wireless Security: Invalid wireless security
** (nm-connection-editor:19238): WARNING **: Invalid setting Wireless Security: Invalid wireless security
** (nm-connection-editor:19238): WARNING **: Invalid setting Wireless Security: Invalid wireless security
** (nm-connection-editor:19238): WARNING **: Error: couldn't verify private key: 3 Unable to determine private key type.
** (nm-connection-editor:19238): WARNING **: Invalid setting Wireless Security: Invalid wireless security
** (nm-connection-editor:19238): WARNING **: Error: couldn't verify private key: 3 Unable to determine private key type.
** (nm-connection-editor:19238): WARNING **: Invalid setting Wireless Security: Invalid wireless security
** (nm-connection-editor:19238): WARNING **: Error: couldn't verify private key: 3 Unable to determine private key type.
** (nm-connection-editor:19238): WARNING **: Invalid setting Wireless Security: Invalid wireless security
** (nm-connection-editor:19238): WARNING **: Error: couldn't verify private key: 3 Unable to determine private key type.
** (nm-connection-editor:19238): WARNING **: Invalid setting Wireless Security: Invalid wireless security
** (nm-connection-editor:19238): WARNING **: Error: couldn't verify private key: 3 Unable to determine private key type.
** (nm-connection-editor:19238): WARNING **: Invalid setting Wireless Security: Invalid wireless security
** (nm-connection-editor:19238): WARNING **: Error: couldn't verify private key: 3 Unable to determine private key type.
** (nm-connection-editor:19238): WARNING **: Invalid setting Wireless Security: Invalid wireless security
** (nm-connection-editor:19238): CRITICAL **: crypto_get_private_key_data: assertion `password != NULL' failed
davidzhou debianzhouwei:~$ nm-connection-editor
(nm-connection-editor:19302): GLib-CRITICAL **: g_hash_table_foreach: assertion `hash_table != NULL' failed
** (nm-connection-editor:19302): WARNING **: nm_connection_list_new: failed to load VPN plugins: Couldn't read VPN .name files directory /etc/NetworkManager/VPN.
(nm-connection-editor:19302): libglade-WARNING **: unknown property `orientation' for class `GtkVBox'
** (nm-connection-editor:19302): WARNING **: Invalid setting Wireless Security: Invalid wireless security
2010/8/10 Dan Williams
<dcbw redhat com>
On Mon, 2010-08-09 at 14:20 +0800, DAVID ZHOU wrote:
> Hi,
> I am using Debian Lenny with Network-Manager 0.7.2
> Here is the problem I am currently meet:
>
> Use System--->Preference--->Network Connections to add a wireless
> connection, and I use WPA/WPA2 Enterprices, TLS, after I input
> identities,
> select the right CA file and Private Key file, password. After that I
> close the Network Connections Dialogue. Then reopen the Dialogue, only
> find that the CA file path and Private Key file path is missing. As
> the followed picture shown.
Can you run 'nm-connection-editor' in a terminal, reproduce the problem
in the editor, and then reply with the debug output from that terminal?
That might give us a better idea of what's going on.
Dan
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]