|
Bugzilla – Full Text Bug Listing |
| Summary: | gnome-keyring-ask: Gtk: cannot open display: :0.0 | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.1 | Reporter: | Stephane Delcroix <sdelcroix> |
| Component: | GNOME | Assignee: | Vincent Untz <vuntz> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P2 - High | CC: | vuntz |
| Version: | Beta 4 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| URL: | http://bugzilla.gnome.org/show_bug.cgi?id=562824 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Stephane Delcroix
2008-11-05 11:31:52 UTC
It seems like this should exist somewhere in seahorse/gnome-keyring. Magnus upgraded both of these packages between the Betas. Running: `ssh-add` is the temporary work around. This seems to be fixed, sort of, in Beta 5. For some reason my gnome-keyring password no longer works now. But, ssh-add is no longer necessary. (In reply to comment #2 from Brandon Philips) > This seems to be fixed, sort of, in Beta 5. For some reason my gnome-keyring > password no longer works now. But, ssh-add is no longer necessary. Could be bug 443693. Stephane: is it better in beta 5 for you? (In reply to comment #2 from Brandon Philips) > This seems to be fixed, sort of, in Beta 5. For some reason my gnome-keyring > password no longer works now. But, ssh-add is no longer necessary. It only worked for one session. I need to do ssh-add still... (In reply to comment #3 from Vincent Untz) > (In reply to comment #2 from Brandon Philips) > > This seems to be fixed, sort of, in Beta 5. For some reason my gnome-keyring > > password no longer works now. But, ssh-add is no longer necessary. > > Could be bug 443693. > > Stephane: is it better in beta 5 for you? > I upgraded to the libgcrypt in Bug 443693 Comment 15 and I see no improvement. However, I did just notice these logs from /var/log/messages Nov 14 11:23:36 plankton gnome-keyring-ask: Gtk: cannot open display: :0.0 Nov 14 11:23:36 plankton gnome-keyring-daemon[11366]: missing dialog response from ask tool Nov 14 11:23:36 plankton gnome-keyring-daemon[11366]: couldn't get private signing key Nov 14 11:26:14 plankton sudo: philips : TTY=pts/3 ; PWD=/home/philips ; USER=root ; COMMAND=/bin/su Nov 14 11:26:14 plankton su: (to root) philips on /dev/pts/3 Nov 14 11:27:30 plankton gnome-keyring-ask: Gtk: cannot open display: :0.0 Nov 14 11:27:30 plankton gnome-keyring-daemon[11366]: missing dialog response from ask tool Nov 14 11:27:30 plankton gnome-keyring-daemon[11366]: couldn't get private signing key (In reply to comment #3 from Vincent Untz) > > Stephane: is it better in beta 5 for you? > Not upgraded yet, will do on monday. (In reply to comment #5 from Brandon Philips) > (In reply to comment #3 from Vincent Untz) > > (In reply to comment #2 from Brandon Philips) > > > This seems to be fixed, sort of, in Beta 5. For some reason my gnome-keyring > > > password no longer works now. But, ssh-add is no longer necessary. > > > > Could be bug 443693. > > > > Stephane: is it better in beta 5 for you? > > > > I upgraded to the libgcrypt in Bug 443693 Comment 15 and I see no improvement. > > However, I did just notice these logs from /var/log/messages > > Nov 14 11:23:36 plankton gnome-keyring-ask: Gtk: cannot open display: :0.0 > Nov 14 11:23:36 plankton gnome-keyring-daemon[11366]: missing dialog response > from ask tool > Nov 14 11:23:36 plankton gnome-keyring-daemon[11366]: couldn't get private > signing key > Nov 14 11:26:14 plankton sudo: philips : TTY=pts/3 ; PWD=/home/philips ; > USER=root ; COMMAND=/bin/su > Nov 14 11:26:14 plankton su: (to root) philips on /dev/pts/3 > Nov 14 11:27:30 plankton gnome-keyring-ask: Gtk: cannot open display: :0.0 > Nov 14 11:27:30 plankton gnome-keyring-daemon[11366]: missing dialog response > from ask tool > Nov 14 11:27:30 plankton gnome-keyring-daemon[11366]: couldn't get private > signing key > I tested this with a freshly created user account to make sure something wasn't wrong with a gconf setting or .gnome and got the same output. (In reply to comment #3 from Vincent Untz) > Stephane: is it better in beta 5 for you? no, it's not :( still not working in rc1 Didn't see this part:
> Nov 14 11:23:36 plankton gnome-keyring-ask: Gtk: cannot open display: :0.0
Stéphane: do you also have this? I have no idea how this could happen, though.
here's the log from 2 consoles, one trying to svn up, the other tailing /var/log/messages > date ; svn up ; date Fri Nov 28 14:44:22 CET 2008 Agent admitted failure to sign using the key. Permission denied (publickey,keyboard-interactive). svn: Connection closed unexpectedly Fri Nov 28 14:44:24 CET 2008 > sudo tail -f /var/log/messages Nov 28 14:44:24 dogbert gnome-keyring-ask: Gtk: cannot open display: :0.0 Nov 28 14:44:24 dogbert gnome-keyring-daemon[10618]: missing dialog response from ask tool Nov 28 14:44:24 dogbert gnome-keyring-daemon[10618]: couldn't get private signing key Good (well bad...) news: I can see this now too. *** Bug 444434 has been marked as a duplicate of this bug. *** Raising priority. Still wondering why it didn't happen to me for a long time and happened to a few others :/ Maybe I was always doing ssh-add first in the session... (JP: cc'ed you because it might actually be a P1) Doing "xhost +" makes it work for me. Probably some missing environment variable for the keyring daemon -- although there's a synchronization that happens on login to get the right environment variables set. Playing around, it seems to be XAUTHLOCALHOSTNAME. See bug 441314. And also ICEAUTHORITY. I've opened a bug upstream: http://bugzilla.gnome.org/show_bug.cgi?id=562824 There will be packages in home:vuntz:branches:GNOME:Factory soon for people to check that the fix works. Fix submitted to oS:F: submission #4090. This is an autogenerated message for OBS integration: This bug (441789) was mentioned in https://build.opensuse.org/request/show/4090 Factory / gnome-keyring |