Thanks to Craig for pointing this out to me. Yes, this is precisely the
problem I encountered with my colleagues AMD64 Ubuntu Edgy box.
I got as far as determining that it is the gnomeui code behind the
gtk_widget_destroy call that causes the crash. That means that if the
fault is in the plugin it could be any one of a number of memory
allocation related calls. I will have a scan over the most likely bits
of the code again to see if I spot anything obvious, but I don't have an
AMD64 Edgy box to try this with.
Things to do/Questions to answer:
1) Is this only an AMD64 issue? (I can't reproduce it on my Intel Core Duo)
2) Is this only an Ubuntu issue? And is it only Edgy?
3) Does the version in CVS HEAD work?
The issue can be tested for quite simply without the need to install the
plugin or even NetworkManager in full (though most of the dev libs will
still be needed to get the plugin to configure). In my tests simply
running the auth-dialog tool on it's own was sufficient to see the
error.
(This is from memory so please excuse any minor mistakes)
As a normal (non-root) user simply run:
nm-ppp-auth-dialog
which on an Ubuntu box is in
/usr/lib/networkmanager
but may be in
/usr/libexec
on other distros.
The tools requires two options, a NetworkManager DBUS service name and a
VPN connection name. Both can be fake as they are only used to to label
any information stored in the keyring. So running for example:
/usr/lib/networkmanager/nm-ppp-auth-dialog -s
org.freedesktop.NetworkManager.ppp_starter -n "Test Connection"
should display a dialog prompting for the username+password to access
"Test Connection".
Enter a username and password and hit OK. Don't tick the session or
keyring boxes for a fake connection or else you'll have to go and delete
the entries using Keyring manager later! After hitting OK, the dialog
should sit there doing nothing. It will be waiting for a carriage return
in the terminal (some handshaking method not implemented by me!)where
you should also find it has printed out "CHAP" followed by the username
and password you entered. Return keyboard focus to the terminal, hit
enter and the program should terminate normally.
If the fault occurs it should happen immediately on hitting OK I think.
Maybe I have just found the issue. It seems that despite a call to
gtk_widget_hide in the gnome_two_password_dialog code, the dialog stays
visible after hitting OK on my Intel box. I wonder if it is trying to
destroy a widget that is currently visible and whether or not that is
allowed.
If building the plugin from source, once built this test may also be
performed with the binary in the auth-dialog directory without performin
"make install".
Any assistance would be appreciated.
--
Crash while trying to connect to PPTP server
https://launchpad.net/bugs/67881
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
