antons workaround was a saver after weeks of furstration
kudos to anton
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
https://bugs.launchpad.net/bugs/360818
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Why has this fix only been released for vpnc, not openvpn?
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
https://bugs.launchpad.net/bugs/360818
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
well I believe Anton's fix is not a fix but a workaround, and yes it
works for openvpn
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
https://bugs.launchpad.net/bugs/360818
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@bnight: KDE4 is installed by default under (K)Ubuntu 9.10.
KDE3 is not anymore supported under (K)Ubuntu 9.10.
Please update to KDE4!
Otherwise please write a new bug report (to distinguish, because it is a
another bug)
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
I know that KDE3 is not anymore supported.
But i don`t want to use KDE4.
What should i do to have this issue fixed i think that this is the same
issue as the others but only that the workaround with +password don`t
work.
Please told me what should i do to get this working.
It`s not a big issue
** Changed in: network-manager-vpnc (Ubuntu)
Status: Fix Released = Fix Committed
** Changed in: network-manager-vpnc (Ubuntu)
Status: Fix Committed = Fix Released
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
https://bugs.launchpad.net/bugs/360818
You
Hi,
I have Ubuntu 9.10 x64 with kde3 from ppd and have the same problem:
NetworkManager: nm-vpn-connection.c.828: NeedSecrets failed: dbus-glib-
error-quark Invalid connection type.
I use:
ii network-manager-kde-kde3 1:0.8-0ubuntu12
KDE systray
The workaround which Anton describes works for me too.
Thanks Anton
Now the big question is, why is it working with wrong settings and not
when everything is setup correctly!
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
https://bugs.launchpad.net/bugs/360818
You received
Works for me, too. Thanks Anton!
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
https://bugs.launchpad.net/bugs/360818
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Thank you very much Anton! The workaround works.
It looks like the cause of the failure is still unknown. I'd like to help
solving this issue. But how?
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
https://bugs.launchpad.net/bugs/360818
You received this bug notification
Thank you Anton.
I've just made an attempt using your waorkaround and everthing went fine.
If other problems occur I'll add some comment here.
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
https://bugs.launchpad.net/bugs/360818
You received this bug notification because
Just want to comment that I have found a workaround for network-manager-
openvpn: Instead of selecting authentication type Certificate (TLS)
(I'm translating this to English so it might not be exactly the same) I
select Password with certificate (TLS). Then I fill in a bogus
username and password.
Thank you, Anton! It's really good workaround.
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
https://bugs.launchpad.net/bugs/360818
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Anton, thank you very much! It's also working for me.
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
https://bugs.launchpad.net/bugs/360818
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I look at nm_setting_vpn_get_secret.
nm_setting_vpn_get_secret (NMSettingVPN *setting, const char *key)
{
g_return_val_if_fail (NM_IS_SETTING_VPN (setting), NULL);
return (const char *) g_hash_table_lookup (NM_SETTING_VPN_GET_PRIVATE
(setting)-secrets, key);
}
It's return TRUE
I first posted this accidently to a duplicate of this bug...
I experience this problem too, and its getting really anying. Therefor I
started to debug this problem by myself. If have no idea of
NetworkManager by grepping through the source I found out that the
message is generated from
Just to further muddy the waters :)
I use openvpn, no private password. Been working pretty reliably on 8.10
and then 9.04 for a year. 9.10 was fine until most recent update, when
no secrets problem popped up. I was studying the synaptic history to see
if I could maybe guess which package broke
I seems like this problem is already fixed upstream:
http://bugs.kde.org/show_bug.cgi?id=213900#c3
I gave it a try and recompiled plasma-widget-networkmanagement after
applying this patch. This seems to fix the No VPN secrets! issue.
Here is what I did in detail:
apt-get source
If you tried the upstream patch and still experience problems please
tell us how you configured Network Manager. Are you using KDE with
plasma-widget-networkmanagement or Gnome?
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
https://bugs.launchpad.net/bugs/360818
You
network-manager-openvpn was working fine under Jaunty, but since
updating to Karmic it doesn't. However, I got the opposite behavior of
the workaround listed -- with a root shell open, it connects properly;
without one, it fails with the 'No VPN secrets!' error.
The at_console patch in #80 does
I got more than one confirm that it works with just default ... can
you recheck that please?
- Alexander
Already confirmed in the post immediately before the one where you asked this.
To quote myself - (I know the post was long as I included logs, hoping they
might be useful.)
As I've
This affect me too...
Tried reboot, does not help. Running Karmic, upgraded from Jaunty. Using
OpenVPN. I've never tried setting this up before. Starting the VPN from console
with
sudo /etc/init.d/openvpn start
works. I'd happily assist in any debugging...
Nov 14 01:40:00 localhost
I think the openvpn bugs should been detach from this vpnc bugs because
it seems to be a absolutely different bug.
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
https://bugs.launchpad.net/bugs/360818
You received this bug notification because you are a member of Ubuntu
Hi n3m3s1s4u .
You have posted the text from the previous fix too literally I think,
and as such you have fixed the problem for the vpnc plugin rather than the
openvpn plugin.
Try this instead: the target file is /etc/dbus-1/system.d/nm-openvpn-
service.conf
!DOCTYPE busconfig PUBLIC
Not sure this fix openvpn connection in 100% of the cases as I still get
the No VPN secrets! error time to time
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
https://bugs.launchpad.net/bugs/360818
You received this bug notification because you are a member of Ubuntu
Bugs,
For me this fix does not fix anything! That's why i am asking
Alexander to give me some hints how to debug/help debugging the openvpn
plugin!
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
https://bugs.launchpad.net/bugs/360818
You received this bug notification because you
I've just done a fresh install with network-manager-openvpn on a laptop.
Adding my keys to create a new connection fails with the Need Secrets message
immediately after installation.
I can confirm a succesful connection after a reboot without applying the dbus
patch I used on my other
On Thu, Nov 12, 2009 at 01:27:17PM -, Niall Brosnan wrote:
Hi n3m3s1s4u .
You have posted the text from the previous fix too literally I think,
and as such you have fixed the problem for the vpnc plugin rather than the
openvpn plugin.
Try this instead: the target file is
On Thu, Nov 12, 2009 at 03:52:08PM -, Rene Jablonski wrote:
For me this fix does not fix anything! That's why i am asking
Alexander to give me some hints how to debug/help debugging the openvpn
plugin!
well ... i think it would be easiest if you get us steps to reproduce.
For instance,
Well for me I only see that (IIRC) on an openvpn connection (tcp+lzo +
TLS keys)
With another connection (UDP, login/password + TLS key) I don't remember
having seen that error once
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
https://bugs.launchpad.net/bugs/360818
You
I have the same error after a fresh installation of the openpvn plugin.
nm-vpn-connection.c.828: NeedSecrets failed: dbus-glib-error-quark
Rejected send message, 1 matched rules; type=method_call,
sender=:1.4 (uid=0 pid=991 comm=NetworkManager)
interface=org.freedesktop.NetworkManager.VPN.Plugin
Could some of you check your config file: does it have an IP address for
remote? Or a host name?
My openvpn config is as follows: no password; single user (i.e. not for
everyone); remote site is an IP address first (our office wifi is VPN
protected), then a hostname (when I'm connected to the
Well, never mind my previous posting - DNS is not the problem.
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
https://bugs.launchpad.net/bugs/360818
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Hi Alexander!
I want to debug the openvpn plugin because of this bug: #453807 but i don't
know exactly how! ^^
Can you please give me some hints how i could debug the plugin or the dbus on
Karmic?
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
I would also be willing to do the same. What can I do to help get to the
bottom of this matter? I have rebooted and this still isn't working for
me.
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
https://bugs.launchpad.net/bugs/360818
You received this bug notification
HI - I am too getting this problem - fresh copy of Karmic - Open Vpn connection
to me server at work:
no password needed - 2 cert files and a key file
and I get this error when connecting
Nov 10 21:29:57 glenn-laptop NetworkManager: info Starting VPN service
On Mon, Nov 02, 2009 at 06:12:05AM -, Michael Rooney wrote:
I can confirm the openvpn task as I hit this there. All I had to do was
restart my machine and everything worked as expected, however.
So ... you did this stop working again or did this go away completely?
- Alexander
--
On Mon, Nov 9, 2009 at 3:41 AM, Alexander Sack a...@ubuntu.com wrote:
So ... you did this stop working again or did this go away completely?
I have used it a bunch of times over the past week since, and haven't
encountered a single issue. It seems to only necessitate a single
restart somewhere
Hi, I had the same issues as Niall. In my case my existing openvpn
connection from Jaunty stopped working throwing the No valid VPN
secret message in the syslog. Also tried to create a new connection
using the same settings but that also didn't fix the issue. Can confirm,
that Patrick Healy's
9.10 upgraded form 9.04 has the same problem with PPPoE connections.
Fresh install stills the same:
pppd[2291]: pppd 2.4.5 started by root, uid 0
pppd[2291]: PPP session is 4346
pppd[2291]: Connected to 00:90:1a:42:90:c9 via interface eth0
pppd[2291]: Using interface ppp0
pppd[2291]: Connect:
I can confirm the openvpn task as I hit this there. All I had to do was
restart my machine and everything worked as expected, however.
** Changed in: network-manager-openvpn (Ubuntu)
Status: New = Confirmed
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
I still get that bug on karmic with openvpn connections...
** Also affects: network-manager-openvpn (Ubuntu)
Importance: Undecided
Status: New
** Changed in: network-manager-openvpn (Ubuntu)
Importance: Undecided = Medium
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900:
I am seeing it on a fresh install of Karmic with openvpn configuration from
Jaunty.
Recreating the connection with my original keys makes no difference.
Adding at_console permissions to /etc/dbus-1/system.d/nm-openvpn-service.conf
as described above by Patrick Healy for vpnc on 2009-04-18
On Tue, Oct 27, 2009 at 08:50:25PM -, KillerKiwi wrote:
Getting this error which looks like the same issue
Oct 28 09:44:04 jason-laptop NetworkManager: nm-vpn-connection.c.828:
NeedSecrets failed: dbus-glib-error-quark Rejected send message, 1
matched rules; type=method_call, sender=:1.4
I confirm with another one:
Oct 28 14:45:35 kurmis NetworkManager: nm-vpn-connection.c.828: NeedSecrets
failed: dbus-glib-error-quark Rejected send message, 1 matched rules;
type=method_call, sender=:1.5 (uid=0 pid=1109 comm=NetworkManager)
interface=org.freedesktop.NetworkManager.VPN.Plugin
I'm getting:
Oct 28 23:59:07 ubuntu dbus-daemon: Rejected send message, 1 matched rules;
type=method_call, sender=:1.36 (uid=1000 pid=3994
comm=/usr/lib/indicator-applet/indicator-applet --oaf-a)
interface=org.freedesktop.DBus.Properties member=Get error
name=(unset) requested_reply=0
Getting this error which looks like the same issue
Oct 28 09:44:04 jason-laptop NetworkManager: nm-vpn-connection.c.828:
NeedSecrets failed: dbus-glib-error-quark Rejected send message, 1
matched rules; type=method_call, sender=:1.4 (uid=0 pid=1090
comm=NetworkManager)
Karmic, updated from Jaunty; in Jaunty, a working VPN, in Karmic, my auth.log
says:
Oct 19 14:15:53 abrikoos dbus-daemon: Rejected send message, 3 matched rules;
type=method_call, sender=:1.52 (uid=1001 pid=2332
comm=/usr/lib/indicator-messages/indicator-messages-ser)
anyway. i dont see how the initial bug cannot be fixed now in karmic.
even if not the code is different enough to justify a new bug. If you
still get this with a up-to-date karmic pristine install, please open a
new bug and drop your bug id here.
** Changed in: network-manager-vpnc (Ubuntu)
david, what versions do you have? for nm and nm-vpnc and applet?
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
https://bugs.launchpad.net/bugs/360818
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I'm fully up to date on Mythbuntu 9.10 beta and seeing the there were
no valid VPN secrets message. I think I have the same NM setup as my
fedora rawhide configuration that works.
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
https://bugs.launchpad.net/bugs/360818
You
Sorry for not responding, I obviously failed to register for
notifications on this bug. I just wanted to add that after yesterdays
update to networkmanager-vpnc I had no problems connecting this morning.
If problems do reappear I will comment again, otherwise assume that they
are gone. Thanks
if you said that it wasnt fixed in latest karmic and you run amd64 (e.g.
64-bit), then please try to upgrade again. the package got stuck
somewhere, so you probably didnt test what i wanted you to test. Thanks
for reconfirming.
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
Me too. Karmic beta, fully up-to-date. Trying to connect using
network-manager-vpnc, the message is that the VPN service stopped
unexpectedly.
I installed yesterday, and yesterday a reboot fixed the problem. From
yesterday, I have a number of messages in auth.log as follows:
{{{
Oct 6
On Wed, Oct 07, 2009 at 09:50:50AM -, Michael wrote:
Today I am unable to connect with the same bubble message, but nothing
in auth.log. Today, I have messages in daemon.log like the following:
{{{
Oct 7 11:41:53 michael-laptop NetworkManager: info Starting VPN service
On Thu, Oct 01, 2009 at 08:23:53PM -, Brendan Braybrook wrote:
note on workaround:
it seems that you must reboot, then not start any root session (ie sudo
bash). something about having a root shell spawned before network
manager runs (even if the root shell no longer exists) triggers the
note on workaround:
it seems that you must reboot, then not start any root session (ie sudo
bash). something about having a root shell spawned before network
manager runs (even if the root shell no longer exists) triggers the
problem.
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900:
Same here - restarting got me to the keyring dialog.
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
https://bugs.launchpad.net/bugs/360818
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I'm another user who just restarted and it worked.
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
https://bugs.launchpad.net/bugs/360818
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I have this same problem with Jaunty 64-bit and a new PPTP connection.
I did not have it available for all users. I fixed it by restarting
NetworkManager. It seems that NetworkManager either doesn't recognize
with the PPTP NM plugin gets installed or when a new connection is
configured.
--
Can confirm bug and fix on up-to-date Jaunty 64-bit and network-manager-vpnc.
However I did not reboot before applying the fix, only after - so could also be
fixed by that.
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
https://bugs.launchpad.net/bugs/360818
You received
Can confirm my experience also matches #23 and #48 on up-to-date 9.04.
This time with network-manager-pptp.
I installed the plugin, configured the connection, tried to connect and
got the no valid secrets GUI message. Rebooted after reading this and
then on connection got the keyring message and
My experience on my up to date Jaunty system matches that of #23 from
Mike Crowe. After installing network-manager-openvpn I initially got
VPN Connection failed because there were no valid VPN secrets back
from the GUI. After playing with the password settings to try and work
around that, the
Alex said the following though:
Also dont apply the none fix with at_console ... that really makes no
sense and opens security issues for you. Dont spread that stuff around
please.
If this works, why is this such a bad thing to do? What sort of security
issues can this potentially cause? And if
I suppose I should have also added: What is at_console anyway? try as I
might, I can't find any documentation on this. And yes, I did try
google. :-)
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
https://bugs.launchpad.net/bugs/360818
You received this bug notification
There is some information on at_console at
http://markmail.org/message/34mwbf6ozkuwb3o7
Also, more information in bug37181
athttps://bugs.launchpad.net/ubuntu/+source/dbus/+bug/37181
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
https://bugs.launchpad.net/bugs/360818
You
Reboot after installing of network-manager-vpnc is a workaround and
works.
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
https://bugs.launchpad.net/bugs/360818
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Confirm Problem and Patch from Patrick Healy wrote on 2009-04-18.
Ubuntu 64 9.04
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
https://bugs.launchpad.net/bugs/360818
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I also saw this problem, but it seems all I had to do was reboot after
installing the network-manager-vpnc package. No at_console fix needed.
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
https://bugs.launchpad.net/bugs/360818
You received this bug notification because you
I can confirm the problem after an upgrade from 8.04. I can also
confirm that Patrick Healy's fix solves the problem for me. Yay!
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
https://bugs.launchpad.net/bugs/360818
You received this bug notification because you are a
I have had the same issue after installing vpnc and network-manager-
vpnc. Tried the fix by Patrick Healy - but it didn't help. Actually a
reboot (first one after installing the packages mentioned before) did
the trick (reverting the fix by Healy to the original), it even works
with a root shell
In 9.04 I have the same error: NeedSecrets failed: dbus-glib-error
No root shell is running (var/run/console).
sudo vpnc-connect works at the terminal.
Patrick Healy's user=at_console policy fixes the problem.
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
Sorry, I forgot to note that I have rebooted since then - same issue :-)
I'd love to get a VPN connection to my work's network, I am willing to
assist further. Tell me what is required and I'll do it, gladly!
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
I had the same problem and was able to correct it using Patrick Healy's
patch.
I'm running up-to-date Ubuntu 9.04 x86_64.
network-manager: 0.7.1~rc4.1.cf199a964-0ubuntu2
network-manager-gnome: 0.7.1~rc4.1-0ubuntu2
network-manager-vpnc: 0.7.1~rc4.20090316+bzr21-0ubuntu
Please let me know if
so back to topic: if you see this issue, could you please confirm that
there is a /var/run/console/root file? If so, please verify that exiting
all root shells fixes this. Thanks!
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
https://bugs.launchpad.net/bugs/360818
You
I don't have a /var/run/console/root file, there are no root shells
running, but I'm still getting this issue.
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
https://bugs.launchpad.net/bugs/360818
You received this bug notification because you are a member of Ubuntu
Bugs,
Chris, could you please also attach the syslog output you get while
trying to connect? I want to check that you are really seeing this
issue.
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
https://bugs.launchpad.net/bugs/360818
You received this bug notification because you
Chris, did you reboot in between?
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
https://bugs.launchpad.net/bugs/360818
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
May 7 08:22:08 ubuntu NetworkManager: info Starting VPN service
'org.freedesktop.NetworkManager.vpnc'...
May 7 08:22:08 ubuntu NetworkManager: info VPN service
'org.freedesktop.NetworkManager.vpnc' started
(org.freedesktop.NetworkManager.vpnc), PID 8365
May 7 08:22:08 ubuntu
** Description changed:
+ WORKAROUND: ensure that you have no root shells (e.g. close/exit all
+ sudo su terminals etc.) open while connecting.
+
Binary package hint: network-manager-vpnc
vpnc:
Installed: 0.5.3-1
Candidate: 0.5.3-1
Version table:
*** 0.5.3-1 0
meanwhile running 'sudo vpnc' works without problems, I'm using this
while waiting for the elegant solution
Thats great. but please don't post such things as workaround to network-
manager bugs ... while this might sound like a smart idea (and maybe its
indeed smart), its not productive (trust
meanwhile running 'sudo vpnc' works without problems, I'm using this
while waiting for the elegant solution :)
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
https://bugs.launchpad.net/bugs/360818
You received this bug notification because you are a member of Ubuntu
Bugs,
ok. after getting more complains about these issues we debugged this and
it turned out to be caused by new consolekit behaviour.
Problem is that root becomes @console if you have a root shell open
(like sudo su). So to connect you just need to log out all root shells.
We are working on a
this stays invalid. dbus policy changes only get applied after reboot in
ubuntu ... you can manually try to reload dbus config.
Also dont apply the none fix with at_console ... that really makes no
sense and opens security issues for you. Dont spread that stuff around
please.
** Changed in:
also remember that as soon as you touched any file in /etc/ you wont get
those files auto updated anymore ... so in future you might end up in
more issues if we need to change the dbus rules.
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
I can confirm the bug and the fix of Patrick Healy does work.
@Stpehen, you must have another issue. please look in your log-files and see
what you have.
@Alexander, I normally do not reboot my pc except for kernel-changes. In
Windows rebooting might be called a fix, in Linux it remains a bug.
I can confirm this error as well. I am receiving the same error as the
one pasted in the original description in my /var/log/syslog file.
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
https://bugs.launchpad.net/bugs/360818
You received this bug notification because you
I have the same problem and fixedwith Patrick Healy 's method.
Thanks for help!
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
https://bugs.launchpad.net/bugs/360818
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I had what looks like the same problem with network-manager-openvpn (it
looked like the same type of DBUS miscommunication.)
The problem went away after a complete system restart. I made no
configuration file changes elsewhere.
I only mention this because many people seem to be reporting that
The patch to nm-vpnc-service.conf above is incorrect, instead of
user=at_console it should be at_console=true
policy at_console=true
allow own=org.freedesktop.NetworkManager.vpnc/
allow send_destination=org.freedesktop.NetworkManager.vpnc/
/policy
This makes vpnc work, but still I set tons of
maybe you never rebooted before?
** Changed in: network-manager-vpnc (Ubuntu)
Status: Confirmed = Invalid
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
https://bugs.launchpad.net/bugs/360818
You received this bug notification because you are a member of Ubuntu
the vpnc profile fixing this is really really unlikely. you clearly had
dbus communication issues, which usually mean your system.d policies are
messed up. Did you revert to the default files there? Maybe you still
have the at_console hack in it?
--
NetworkManager.vpn fails --
ok. we need to get more output from dbus.
can you please stop dbus (sudo /etc/init.d/dbus stop) and start it from
a command line like:
sudo DBUS_DEBUG_OUTPUT=1 dbus-daemon --nofork 21 | tee
/tmp/dbus.log.txt
... then please reproduce and attach the dbus.log.txt.
Thanks!
--
NetworkManager.vpn
I've just removed the patch and the vpn connection is still working .
Even setting up a new user and new vpn connection is fine, so am unable
to do any more tests. I'll upgrade my PC to jaunty tomorrow to see if
it has the same issue as my laptop had so I can do some more debugging.
--
Alexander,
Despite my best efforts to hack away around it, I cannot seem to stop dbus
without being logged out of gnome and my system becoming unresponsive. Any
suggestions?
--
NetworkManager.vpn fails -- nm-vpn-connection.c.900: NeedSecrets
https://bugs.launchpad.net/bugs/360818
You received
you could see if adding a line:
export DBUS_DEBUG_OUTPUT=1
in /etc/default/dbus
enables debug output for you (usually would go to syslog i think). but
be careful that could produce really a lot of output, so in case
everything slows down or causing other issues, remember to remove that
again.
so in case it works, let the system settle and (assuming its syslog
where the output goes to) do a
tail -n0 -f /var/log/syslog /tmp/dbus.log.txt
right before clicking on the VPN menu entry. hit ctrl-c to abort that
tail thing right after the bug happened.
--
NetworkManager.vpn fails --
Adding export DBUS_DEBUG_OUTPUT=1 to the params section of
/etc/default/dbus resulted in the same errors as before, with system
unresponsiveness at the login screen. A hard restart is required to
reboot, and I had to recovery console into the config file and remove
the option to get my system to
Adding export DBUS_DEBUG_OUTPUT=1 to the params section of
/etc/default/dbus
not sure i understand. did you add that into PARAMS=...? doing that
will probably make dbus not start, yes.
please check if you did you do what i said:
you could see if adding a line:
export DBUS_DEBUG_OUTPUT=1
in
Ahh nope, that was my mistake.
However, I just tried the connection and it worked. Doesn't make any sense,
wasn't working even this morning. Maybe an update got it? I didn't pay
attention to see if network-manager or network-manager-vpnc was patched. Or
maybe it was on my school's end? Either
1 - 100 of 110 matches
Mail list logo
