You are not logged in.
Hi,
Since upgrading to Gnome 2.20 from testing repository, I haven't been able to use nm-applet. It crashes almost right away when I logon. Running nm-applet from the console yields this message when crashing:
[sims@macbookpro ~]# nm-applet
683db3e4-d3d5-0166-589c8948-3f07ee7c is dumped
It makes no difference if it's run by a regular user or root
Does anyone have an idea what's causing this, where to look for causes?
Regards,
Simon
Offline
Offline
strange I have "nm-applet --sm-disable" at System > Preferences > Sessions and I'm using testing as well and network manager just works fine.
Same for me, it works fine with --sm-disable.
Last edited by jordz (2007-09-26 19:42:18)
Offline
There's no difference for me running nm-applet with --sm-disable option. I've tried to create a whole new user to see if it could a bad configuration, but still the same result. Maybe someone has a suggestion where to debug?
Offline
no one else is experiencing this? or has an idea how to find the source of the problem?
Regards,
Simon
Offline
I'm experiencing this too, probably troubles with gnome-keyring as it only crashes when it tries to autoconnect to my network. When I restart nm-applet and I try another network (whose pw isn't in the keyring) it doesn't crash.
Quick workaround: kill gnome-keyring-daemon, and you'll be able to connect (with your wpa-key etc).
Last edited by Linteg (2007-10-05 08:15:49)
Offline
fetched everything from testing and nm-applet works fine, apart from the fact that the keyring is supposed to be accessible by applications without asking for your 'keyring password' as of gnome 2.20
Offline
http://bugs.archlinux.org/task/8216 solved my problem.
As for bboozzoo's problem about the keyring password, well the modules are there but pam needs to be configured (some files in /etc/pam.d), look at this page. I haven't tried it but I would presume it works, but it also seems to require that the user's and the "login" keyrings' passwords match.
Last edited by Linteg (2007-10-05 15:05:59)
Offline