kde-nm-connection-editor is completely useless for setting up TLS connections
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plasma-nm (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Try to set up TLS connection using KDE native NetworkManager.
Choose 802.1x Security tab, choose "TLS" in "Authentication:" combobox and fill all its fields, even if all key info valid, kde-nm-
Dec 10 12:40:43 DimanNeYa NetworkManager[
Dec 10 12:40:43 DimanNeYa NetworkManager[
Dec 10 12:40:43 DimanNeYa NetworkManager[
BUT(!!!) if you accomplish all these actions in nm-applet (from package network-
PS And even now, when connection created by nm-applet and I have working internet, I can not fill "Private Key password:" field, ie I can fill it, but after I press "Ok" all changes disgarded
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: plasma-nm 0.9.3.1-
ProcVersionSign
Uname: Linux 3.11.0-14-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
Date: Tue Dec 10 12:34:47 2013
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2012-11-28 (377 days ago)
InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1)
MarkForUpload: True
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: plasma-nm
UpgradeStatus: Upgraded to saucy on 2013-10-18 (52 days ago)
Changed in plasma-nm (Ubuntu): | |
milestone: | none → ubuntu-14.04 |
tags: | added: kubuntu |
Changed in plasma-nm (Ubuntu): | |
status: | Confirmed → Won't Fix |
status: | Won't Fix → Fix Released |
Status changed to 'Confirmed' because the bug affects multiple users.