Thanks for reporting this bug and any supporting documentation. Since
this bug has enough information provided for a developer to begin work,
I'm going to mark it as confirmed and let them handle it from here.
Thanks for taking the time to make Ubuntu better!
Troubleshooting done in #ubuntu+1 on 2010-02-19:
<borschty> rr72, if you made the connection available to all users it is not
stored in keyring
<rr72> it was working yesterday though borschty
<rr72> was this a recent change?
<borschty> rr72, what is not working?
<rr72> when i login it asks me fore my wireless password, it used to not do that
<rr72> it used to be stored somewhere
<borschty> does it ask you for your wireless password or for your keyring
password?
<rr72> wireless
<borschty> the 2.29 version of keyring has hit the repos today, so that might
still be broken
<borschty> the code was pretty much rewritten
<borschty> but there were no changes to nm that would disable the keyring
usage, afaik
<BluesKaj-Laptop> rr72, using network manager ?
<rr72> BluesKaj-Laptop~ yes, on xubuntu
<borschty> ah, xubuntu
<rr72> that in issue?
<borschty> i'm not sure how xubuntu sessions look like, but i guess they have a
dbus-session started by default too
<borschty> rr72, was dbus the problem?
<rr72> borschty~ i have no idea, it's still not fixed
<borschty> ah
<rr72> i am saying thankyou for being serious about my problem
<borschty> what is the session binary of xfce called? xfce-session? xfsession4?
(their naming was quite inconsistent when i used it the last time)
<charlie-tca> borschty: I think it is xfce4-session ?
<rr72> ** (seahorse:6875): WARNING **: couldn't get default keyring name: Error
communicating with gnome-keyring-daemon
<rr72> could that be bad?
<borschty> that sounds more and more like a dbus-related problem
<borschty> but it would be weird if xfce didn't start a dbus-session
<borschty> rr72, strings /proc/$(pidof xfce4-session)/environ | grep DBUS
<borschty> what's the output?
<borschty> also did you restart your session since the keyring-update?
<borschty> if you didn't and you are still running the old daemon while the new
version of the library is trying to connect to the new daemon, that won't work
<rr72> it's not working
<borschty> what's not working?
<rr72> put the PID in () or no?
<rr72> w/o them it gets rid of the leading number
<borschty> ok, try running: ps ux | grep session
<borschty> is there anything like "xfce-session" "xfce4-session" "xfsession4"?
<rr72> i found pid
<rr72> yes
<rr72> but if i put that number in the after $ it craps out
<borschty> aaah
<borschty> you weren't supposed to put it in the command, pidof does that for
you ;)
<rr72> abstract=/tmp/dbus-EZXannScer
<rr72> something like that
<borschty> "abstract" is "DBUS_SESSION_BUS_ADDRESS"?
<rr72> no "=unix"
<borschty> ah, i see what i confused here
<borschty> but that all is part of the DBUS_SESSION_BUS_ADDRESS environment
variable
<borschty> i.e. it is the first word in that line ;)
<rr72> so dbus is running fine?
<borschty> so there is a dbus-session and thats not the source of the problem
<borschty> dpkg -s gnome-keyring | grep Version
<rr72> 2.29.90git20100218-0ubuntu1
<borschty> dpkg -s libgnome-keyring0 | grep Version
<rr72> 2.29.4git20100216-0ubuntu1
<borschty> did you restart your session after the problem occured?
<rr72> not sure lol i can if you want me to
<rr72> that's when i noticed it
<rr72> i turned on my laptop and it requested my password
<rr72> and it doesn't do that
<rr72> it just connects to the network, i did do an upgrade before that
<borschty> that would at least rule a few things out, so could you try it?
<rr72> borschty~ problem persists after restart
<borschty> rr72, ps ux | grep gnome-keyring
<rr72> its running
<rr72> /usr/bin/gnome-keyring-daemon --daemonize --login
<borschty> rr72, is there any file with "keyring" or "gnome" in its name in
/etc/X11/Xsession.d/
<rr72> nope
<rr72> gnome-session-gnomerc
<rr72> wait that's the only one
<borschty> i think xubuntu might be starting gnome-keyring before dbus and thus
it can't register correctly
<borschty> rr72, could you try killing gnome-keyring-daemon?
<rr72> killed
<borschty> now start it again
<borschty> and then try seahorse
<rr72> should i mention xubuntu doesn't come with seahorse? I installed it
seperatly cause i wanted gpg administration
<rr72> borschty~ i see something now
<rr72> borschty~ it works now!!
<borschty> ok, xubuntu starts gnome-keyring too early
<borschty> but i don't know how its startup works, so i can't help that much
with it
** Changed in: xubuntu-meta (Ubuntu)
Status: New => Confirmed
** Changed in: xubuntu-meta (Ubuntu)
Importance: Undecided => Medium
** Description changed:
on lucid gnome-keyring starts too early for some programs to access it
+
+ Wireless would not connect without asking for wpa2 password.
--
lucid: gnome-keyring-daemon gets started before dbus-session
https://bugs.launchpad.net/bugs/524693
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
--
universe-bugs mailing list
universe-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/universe-bugs
