PPTP authentication has a password option called "Always Ask". It doesn't seem to do anything, as I do not get a password prompt when I select this VPN connection. Reproducible: Always Steps to Reproduce: 1. Create a PPTP connection inside the Network Management Settings window 2. Select "Always Ask" in the "PPTP Settings" tab 3. Select this connection from the main network manager widget Actual Results: no password prompt Expected Results: a password prompt should appear and the chosen password should be used to initiate the connection works fine in the Gnome network manager
bug simillar to bug 259893
Perhaps a similar fix can be applied to the PPTP-specific code involved with this bug.
Which Plasma NM do you have installed? There is a fix for this problem in Plasma NM 0.9.0.6 (http://lamarque-lvs.blogspot.com.br/2012/12/plasma-nm-0906.html). If you are using anything below that version you should upgrade.
It appears to be 0.9.0.5. Thanks for your response. Hopefully there is an easy way to build and install a new version of a given plasma widget while retaining the existing versions of others :) I will investigate.
I've built 0.9.0.6 from source, using the link provided on the above-reference blog, using the following sequence: mkdir build;cd build;cmake -DCMAKE_INSTALL_PREFIX=`kde4-config --prefix` .. make sudo make install I verified that /usr/lib/kde4/networkmanagement_pptpui.so had been updated. I then logged out and back in again, and created a new PPTP VPN connection, with "Always Ask" checked. When I attempt to connect, there is no change to the behavior from 0.9.0.5: no password prompt appears, and the status remains "Connecting..."
Update: regardless of my previous observation that the .so files have been updated, the Manage Connections->Other page shows that the version is "0.9.0.5". Can you recommend a different installation procedure?
Uninstall the previous Plasma NM installation and try again. Plasma NM does not belong to KDE SC so maby Ubuntu installs it in a different prefix than `kde4-config --prefix`. You can check where it is installed suing "dpkg --list plasma-widget-networkmanagement" (I think that is the correct command line, I do not use Ubuntu so I cannot test that).
After removing the existing networkmanagement widget with "sudo apt-get remove plasma-widget-networkmanagement", building from the 0.9.0.6 tarball (SHA1 25762e4d0e4cd1f4f7e3e17739998b31a23ca316), installing as described above, then removing and re-adding the networkmanagement widget via the "cashew", the behavior described in this report is unchanged. I verified that the locations used for the Ubuntu package were the same as those given by "kde4-config --prefix". I do still observe that the version string shown in Network Management Settings -> Other is "Version 0.9.0.5 (nm09 20121206)". Is there some way to be certain this has been properly overwritten by the new code?
(In reply to comment #8) > After removing the existing networkmanagement widget with "sudo apt-get > remove plasma-widget-networkmanagement", building from the 0.9.0.6 tarball > (SHA1 25762e4d0e4cd1f4f7e3e17739998b31a23ca316), installing as described > above, then removing and re-adding the networkmanagement widget via the > "cashew", the behavior described in this report is unchanged. I verified > that the locations used for the Ubuntu package were the same as those given > by "kde4-config --prefix". You should relogin or restarted kded4 when upgrading Plasma NM. Just re-adding the plasmoid does not fully restart Plasma NM. The particular commit I talked about in comment #3 is going to take effect until you restart kded4. > I do still observe that the version string shown in Network Management > Settings -> Other is "Version 0.9.0.5 (nm09 20121206)". Is there some way > to be certain this has been properly overwritten by the new code? I have just checked and you have Plasma NM installed. The version string in networkmanagement-0.9.0.6.tar.bz2 is incorrect but the source code is correct.
Can you confirm this is working with Plasma NM 0.9.0.6 or 0.9.0.7?
My apologies for the delay in responding. I just checked, and there is still no password prompt. I re-verified that the version string is as described above, and I have rebooted my machine several times since I installed 0.9.0.6. Would it be worth trying 0.9.0.7?
Git commit 5d64ce14234c9ec9696132df6a65f0802c6d0c1f by Lamarque V. Souza. Committed on 01/02/2013 at 08:04. Pushed by lvsouza into branch 'master'. Relay NetworkManager's secret request even when using plain text storage. FIXED-IN: 0.9.0.8 M +1 -1 libs/service/secretstorage.cpp M +1 -1 plasma_nm_version.h http://commits.kde.org/networkmanagement/5d64ce14234c9ec9696132df6a65f0802c6d0c1f
Git commit 70387541b5d61b02fffaaba2f2120519c10fb46d by Lamarque V. Souza. Committed on 01/02/2013 at 08:04. Pushed by lvsouza into branch 'nm09'. Relay NetworkManager's secret request even when using plain text storage. FIXED-IN: 0.9.0.8 M +1 -1 libs/service/secretstorage.cpp M +1 -1 plasma_nm_version.h http://commits.kde.org/networkmanagement/70387541b5d61b02fffaaba2f2120519c10fb46d
This issue is still present in the latest release: Version 0.9.0.8 (nm09 20130310). I should reiterate that I am using "always prompt", not "plain text storage". Comment 13 implies that a fix was applied for plain text storage, but as far as I know that is not related to my problem.
reopen per comment #14
(In reply to comment #14) > This issue is still present in the latest release: Version 0.9.0.8 (nm09 > 20130310). I should reiterate that I am using "always prompt", not "plain > text storage". Comment 13 implies that a fix was applied for plain text > storage, but as far as I know that is not related to my problem. As I wrote in https://bugs.kde.org/show_bug.cgi?id=312963#c19 : if you have kwallet disable you *have* to set your storage to plain text in Plasma NM. Have you done that? However, I really do not recommend disabling kwallet with Plasma NM.
My apologies, kwallet is in fact *enabled* (settings says "Enable the kwallet subsystem"), and the password policy in networkmanagement is set to "always prompt". But I still see this issue. Is this a supported configuration? Thanks.
(In reply to comment #17) > My apologies, kwallet is in fact *enabled* (settings says "Enable the > kwallet subsystem"), and the password policy in networkmanagement is set to > "always prompt". But I still see this issue. Is this a supported > configuration? Thanks. Yes, it is. I just do not have a pptp server available to reproduce this problem. Send me the ~/.xsession-errors, NetworkManager's log and the dbus-monitor log. Maybe I can figure out what is wrong.
Created attachment 78356 [details] .xsession-errors fragment bracketing this issue
Created attachment 78357 [details] The contents of /var/log/syslog containing the string "NetworkManager" This may have more than one trial of the pptp connection as I didn't time it precisely.
Created attachment 78358 [details] dbus-monitor output for this trial
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years and I will be closing this bug. Please test again with the latest version and file a new bug in plasma-nm. Thank you!