now I've made the comment I see the solution is to be found in this
page ... sorry.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/932177
Title:
XFCE (and other non-GNOM
The solutions here did not work in my case, but a solution which did work for
me can be found in
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1022322
which says:
The file causing the problem is /etc/xdg/autostart/gnome-keyring-pkcs11.desktop
. The line
OnlyShowIn=GNOME;Unity
sho
** Changed in: gnome-keyring (Fedora)
Status: Unknown => Fix Released
** Changed in: gnome-keyring (Fedora)
Importance: Unknown => Undecided
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bu
Facing the same. gnome-keyring-daemon often fails to start, if it
manages to start it asks for Login keyring password.
BTW gnome-keyring-daemon always starts from root, even if I run it from
user in terminal!
xubuntu 16.04, it became broken in these two months.
--
You received this bug notifica
** Changed in: gnome-keyring (Debian)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/932177
Title:
XFCE (and other non-GNOME) desktops do not
I have this problem in R using the jsonlite package. Ubuntu 12.04 i686.
Using awesome window manager.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/932177
Title:
XFCE (and o
It's 2014, this bug is already 2 years old, and hasn't been fixed yet,
at least on Xubuntu 12.04. Fixing it seems trivial.
Possible solutions:
1. If the package gnome-keyring is not needed on Xubuntu (or other
affected Ubuntu flavors), it should be considered to be removed from
it as a
Confirmed with Chromium on 14.04.
** Also affects: xubuntu-desktop
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/932177
Title:
X
** Changed in: kde-workspace (Ubuntu)
Status: Confirmed => Triaged
** Changed in: kde-workspace (Ubuntu)
Importance: Undecided => Medium
** Changed in: gnome-keyring (Ubuntu)
Importance: Undecided => Medium
** Changed in: xfce4-session (Ubuntu)
Importance: Undecided => Medium
**
I can confirm that the script in comment #55 resolves the issue in
Kubuntu 12.10, and does not seem to contain malicious content. Note that
it must be mae executable, i.e. "chmod +x".
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gno
Confirmed in xubuntu 13.04. The OnlyShowIn modification works.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/932177
Title:
XFCE (and other non-GNOME) desktops do not initia
As the bug is still present in 13.04 and probably 13.10 Kubuntu users
may be interested in a workaround:
Copy the attached script 01gnome-keyring-daemon.sh into ~/.kde/env
directory.
Files in this directory are sources by /usr/bin/startkde so the script
can finish gnome-keyring-daemon initializat
This is actually a security bug for users of Chrome / Chromium. Chrome will
store passwords in cleartext if gnome-keyring isn't functional. This is
mentioned in the upstream Chrome disk encryption bug
https://code.google.com/p/chromium/issues/detail?id=25404
$ cp ~/.config/chromium/Default/Logi
Reproducible in xubuntu 13.04.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/932177
Title:
XFCE (and other non-GNOME) desktops do not initialise gnome-keyring
correctly /
Reproducible in Lubuntu 13.04.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/932177
Title:
XFCE (and other non-GNOME) desktops do not initialise gnome-keyring
correctly /
Also in Kubuntu 13.10.
Have added "saucy" and "kubuntu" to tags so that bugs reports might be
received by those that can apply or push for a fix.
** Tags added: kubuntu saucy
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyr
I can confirm the bug in Kubuntu 13.04, where the upgrade from 12.10
overwrote the file
/etc/xdg/autostart/gnome-keyring-pkcs11.desktop
in which I had previously applied a fix as the one described by
RichardNeill, i.e. appending "KDE;" to the line
"OnlyShowIn=GNOME;Unity;MATE;"
--
You received
I'd like to confirm this bug for KUbuntu Raring Beta-final. Please fix
it; it's most definitely not invalid.
To reproduce:
1. Install both sets of desktops: apt-get install ubuntu-desktop
kubuntu-desktop
2. Log into a KDE session.
3. launch an application from the terminal "eg libre-office".
4.
does exist any solution which works as for desktop as for terminal
commands ?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/932177
Title:
XFCE (and other non-GNOME) desktops
I'm on precise and using ldap auth along with local auth. I only get the
error on ldap auth
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/932177
Title:
XFCE (and other non-G
** Tags added: quantal raring
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/932177
Title:
XFCE (and other non-GNOME) desktops do not initialise gnome-keyring
correctly / W
@Julián the only problem is that gnome-keyring won't actually work (see
comment #27), but if you don't use it, and none of the apps you use rely
on it, then that won't affect you.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-k
I ran into this issue when tried to run "git svn fetch" on a repo I've
cloned just a few seconds previously (which prompted me from username &
password).
$ git svn fetch
WARNING: gnome-keyring:: couldn't connect to:
/home/x/.cache/keyring-6DeUlo/pkcs11: No such file or directory
The workarou
I ran into same issue after I removed my ecrypt'ed $HOME and tried to start
conky & some apps using wine.
$ conky -c /home/x/.conky/conky-autostart
WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-YiWUvh/pkcs11: No
such file or directory
I use UbuntuStudio 12.04.1 LTS ; lightdm ;
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: kde-workspace (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpa
** Also affects: kde-workspace (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/932177
Title:
XFCE (and other non-GNOME) de
@abone
Nice observation!
I'm using MATE.
I once noted that when LightDM is running, there are g-s-d and gnome-keyring
processes.
After entering MATE session, gnome-keyring is still there.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed t
In my opinion, for Ubuntu-based distributions the root cause of the bug
is in lightdm package. At least, in quantal it becomes default display
manager for all desktops including non-GNOME ones.
In files:
* /etc/pam.d/lightdm
* /etc/pam.d/lightdm-greeter
it has the following line:
session optio
I found a nice solution to this problem at
http://hongouru.blogspot.fr/2012/07/sol … uldnt.html
In my case I add MATE instead of LXDE.
I believe those working with Mint have to add Mint or MINT.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subsc
I get this problem still. I am running XFCE 4.10 and i see the error
when i do git clone or git pull. Following is the error
"git pull
WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-ySN77r/pkcs11: No
such file or directory
Already up-to-date.
"
--
You received this bug notification
Any permanent fix planned for Lubuntu/LXDE?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/932177
Title:
XFCE (and other non-GNOME) desktops do not initialise gnome-keyring
This gnome WARNING has been bothering me for weeks. but now my Brother
HL-3040CN printer fails and the string is issured more frequently:
WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-vlN7D3/pkcs11: No
such file or directory
Following the suggestion directly above make
I got an other workaround for the bug from http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=649408#109
Open /etc/pkcs11/modules/gnome-keyring-module and comment out the line
"module: gnome-keyring-pkcs11.so".
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
This should be fixed with xfce4-session 4.10 (in quantal), but gnome-
compat needs to be reenabled by default now (Bug #1008993).
** Changed in: xfce4-session (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
suggested upstream xfce patch on
https://bugzilla.xfce.org/attachment.cgi?id=3953&action=diff
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/932177
Title:
XFCE (and other non
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xfce4-session (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpa
Thanks for the details, the fact it's a affecting non GNOME session only
explains why most people around don't get the issue
** Changed in: gnome-keyring (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is s
I just wanted to add (or confirm) that adding the following line to my
.xsession file
eval $(gnome-keyring-daemon --start)
allows me to get this working with ratpoison or fluxbox as my window
managers.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
** Summary changed:
- WARNING: gnome-keyring:: couldn't connect to PKCS11
+ XFCE (and other non-GNOME) desktops do not initialise gnome-keyring correctly
/ WARNING: gnome-keyring:: couldn't connect to PKCS11
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
39 matches
Mail list logo
