After launching the gnome-keyring-demon my mounted mp3-player is no longer accessible. In /var/log/messages I get the message "gnome-keyring-demon removes usb device". As long as the gnome-keyring-demon is running, I cant not remount the device though it is visible using lsusb. I'm running an FC12 system.
View 1 Replies
I recently ran apt-get remove lamp-server^ and without noticing gnome was also removed.
How can I fix this.
So I can't install Firefox, because it conflicts with Iceweasel, but it appears that uninstalling Iceweasel uninstalls GNOME (gnome & gnome-core).Is there any way around this? Perhaps telling apt that Firefox is an alternate to Iceweasel?
View 3 Replies View RelatedI want to store my svn password in the gnome-keyring so it is encrypted and 'secure'. I made the necessary changes to ~/.subversion/config, but even after running a few svn commands, I do not see an entry for SVN in the keyring.
What else do I need to do to get SVN using gnome-keyring? I will also be using this with git-svn.
Is Epiphany the only browser for Gnome supporting password storage in keyring?Firefox and Chromium both seem to store login credentials in own storage thus limiting interoperability.
View 2 Replies View RelatedFor several weeks now I have been experiencing a problem with GNOME keyrings in Fedora 10 x86. Here is the thing: somehow out of the sudden GNOME started requesting the "Default Keyring" in order to connect to protected wireless networks it already knows. I don't remember having set one, maybe I did, and just in case I tried all my passwords to no avail.
On the other hand, XFCE, the desktop environment I use the most in that machine, has lost its ability to 'remember' passwords, which is a little painful in the long run.
I wouldn't want to just delete the keyrings because there are many stored already, and I want them back. Needless to say I have root access to the machine. Is it possible somehow as root (or as user) to fix that problem and restore both access to the stored passwords and the ability for Network Manager to remember them?
Just to be on the safe side I created another user and that one 'remembers' the stored passwords and is not prompted for the "Default Keyring".
I wana know the difference between PAM and GNOME-KEYRING.
I have googled both of them and I found that they both are for authenticating users. and then some tutorials say that I can use gnome-keyring with PAM support!
So what is the difference and if there is no difference how then can I use gnome-keyring with PAM?
I'm trying Lubuntu for my low-resource netbook and I'm lovin' it.
But I can't get my ssh key passphrase work with the keyring manager.
I even created a new user account with a fresh home directory and it doesn't work. You run "ssh myname@mydomain.net" and it prompts you for the key passphrase in the terminal.
Expected behavior: with Gnome, you run "ssh myname@mydomain.net" and the password manager opens a GUI to ask for the passphrase. Once unlocked, it remains unlocked until you log off. Moreover, at that moment of unlocking you can tell it to remember the passphrase forever so it gets automatically unlocked next time you login.
The keyring works fine for the wireless password, and for luks-encrypted volumes, but not for Secure Shell keys.
I'm using Ubuntu Lucid, installed lubuntu-desktop package, using gdm session manager, all updated.
F15 from fresh install off LiveCD. I find that on fresh login my ssh agent situation is a bit confused.
I normally ssh-add my keys to the authentication agent, and then ssh to remote hosts without thinking too much about it. Recently, the ssh command has been hanging. Running with -vvv shows it stops at the point it should talk to gnome-keyring:
At that point it hangs and a ctrl-c will kill it.
The ssh-add command cannot connect to the ssh agent:
If I run to that ssh hang again, and this time grep ps for keyring:
I haven't had any gnome-keyring-prompt window appear on my desktop. Checking all workspaces, and using the Gnome 3 Overview screen to visually view open windows, doesn't show it. "kill -9 2101" returns the hung ssh attempt to the prompt immediately. Thinking about it, I don't believe I've had the Gnome 'enter your password to unlock your keyring' prompt once since installing F15.
I noticed that SSH_AUTH_SOCK seems a little confused:
So it seems that gnome-keyring-daemon is using one tmp directory while my shell has been set up with another. If i manually set the SSH_AUTH_SOCK variable, things start working again:
As I now have to reset SSH_AUTH_SOCK in every terminal I want to use the agent in.
What's the next best step to investigating why the gnome keyring prompt isn't appearing, and how the SSH_AUTH_SOCK variable is getting mismatched with the gnome-keyring-daemon's tmp dir?
I cannot log on to my server because of the pop up window that asks for a password to unlock the keyring. I have tried to just hit cancel
View 5 Replies View RelatedI'm running an up-to-date installation of Lucid, and have come upon a little problem. It seems that applications are having trouble communicating with gnome-keyring-daemon.
When I connect to wireless networks -- even ones that are in the network manager -- it always asks me for a password.
Gwibber is crashing because it can't connect to the gnome keyring daemon.
And when I open the Passwords and Encryption Keys utility (on the Accessories menu), I get the error: "Couldn't communicate with key ring daemon."
I have verified that the daemon is starting up when I log in, that all of the appropriate keyring-related login items (certificate and key storage, secret service, & SSH key agent) are in place, and that the keyring works in other accounts on my machine. I have tried deleting my extant keyrings, but that has produced any success. And when I kill and restart the keyring daemon once I'm already logged in, the problem seems to abate.
I don't know if it matters, but for OS X compatibility purposes, I'm running as a UID under 1000.
For a while now, firefox has been prompting gnome-keyring (twice)
There is one applet i know of on my system that wants me to enter my keyring pw twice "CPU Frequency Scaling Monitor" (i have a core2-duo cpu, a monitor for each cpu), but i have no clue why ff would be invoking a change in how ubuntu controls that app.
Is there any way of finding out, which application (or perhaps an add-on?) is actually asking for my keyring-pw (the input window just says "an application..." not like e.g. "synaptic package manager...".
I've done the process with no problem on Ubuntu, but I can't get it working with Lubuntu.
I installed the pam package. I then added the @include common-pamkeyring line to my /etc/pam.d/lxdm file.
Here's my complete /etc/pam.d/lxdm file:
Code:
Am I doing something wrong? Does something have to be done differently in LXDE?
A few days ago, I decided to setup my emailing applications (I use mutt, with offlineimap, imapfilter, and msmtp) to use gnome-keyring rather than have my email passwords stored in plain text inside these application's respective configuration files.
[1].I am successfully able to run them from the command line myself, but looking up the passwords from gnome-keyring fails when running from cron.
I came across a person calling svn with a cron job and authenticating via gnome-keyring
[2]. I've tried to adapt his solution, but I don't think I'm doing it right. I've made a comment on the blog author's post, but am still waiting to hear back.
Does anyone know how I'm supposed to incorporate the bash function from that author's post to give cron the correct environmental variables?
[1]:[url]
[2]:[url]
I have never configured any keyrings. I set up Evolution, and it's working, but sometimes Gnome wants me to allow it to access the default keyring to get the email password. It takes 3 cancel-deny tries to finally dismiss this dialog box, after which Evolution is working fine. I see that this is not an Evolution thing. Other users report the same thing in VINO, and on wireless access. The GNOME forum seems to think there is a bug when accessing severs, and has a bug and milestone. Some other distros have the same problem.
One user says that they were able to Delete the default keyring (which must have had an unknown default password) and then create a New default keyring with thier own password. This seems to have solved that user's problem. However there were no instructions on how to do it. I think someone else was able to just stop the default keyring daemon. That would work too, although it's not as elegant. I'm now unable to find instructions.
NetworkManager stores its connection secrets in a keyring called "default". I am prompted to supply the keyring password every time I log in, regardless of whether I select the "automatically unlock this keyring when I log in" radio button.
View 4 Replies View RelatedSince I've upgraded to Ubuntu 10.04 my gnome-keyring-daemon isn't working on login. It is running - ps ax shows:
4927 ? SLl 0:00 /usr/bin/gnome-keyring-daemon --daemonize
but it doesn't seem to be accessible. Seahorse says: "Couldn't communicate with key ring daemon", and I never get asked to unlock my keyring on login (thus saved wireless keys are not available, for example). If I kill the gnome-keyring-daemon process and run it again from the command line, everything works. There are not messages in /var/log/messages from the keyring daemon, so i don't know what it is doing wrong.
I have Ubuntu 10.04 configured to login with Kerberos (as in [url]). Everything works fine, except gnome-keyring-daemon:
-If I login with a local user, gnome-keyring-daemon works right. Besides, the keyring is automatically unlocked with the login password.
-If I login with a Kerberos user:
- The session startup is considerably slower.
- /var/log/auth.log says something like:
Code:
- If I execute a program that needs the gnome-keyring (like Evolution), is desperately slow, and it says:
Code:
Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
- If I kill all gnome-keyring-daemon (killall gnome-keyring-daemon), start a new one (gnome-keyring-daemon), and restart the application that uses the gnome-keyring, it works fine, but it ask me for the password to unlock the keyring (I think that this is the normal behaviour if gnome-keyring-daemon did not start before).
I have seen the configurations in /etc/pam.d and everything looks fine (with pam_gnome_keyring.so). Indeed, I think that if something was wrong here, the local user would not have the keyring unlocked automatically.
How to permanently disable the gnome-keyring-daemon.
I've seen posts where there was a work around to store passwords in clear text. That's not a real solution. I've seen posts where killing the process and removing ~/.gnome2/keyrings is a temporary solution until next time you log in or reboot machine. Removing the package, will force removal of the whole kitchen sink. That's too intrusive.
There must be a way to stop this thing from starting up, ever.
I tried commenting out the entries in the /etc/pam.d/* files that refer to "pam_gnome_keyring.so", and have also unchecked the 3 keyring related entries under System --> Preferences --> Startup Applications, which are affiliated with these 3 files:
But I still get this one process once I log into the console window:
There must be one more file somewhere that says, "hey when someone logs in and starts up gdm, start the gnome keyring daemon".
My computer keeps spawning new and massive numbers of "gnome-keyring-d" which require me to reboot the PC to clear.
What is happening? Why? And how do I stop it?
Code:
I have written a demon/service listening to a socket to accept and process connecting clients. I've modelled the service on the multi-threaded example given by [url].
The service seems to work correctly, processing clients then at what appears to be random points, it will terminate and I don't seem to get any error messages or information.
I'm executing the demon script by using another script, attempting to catch any output.
Both scripts are attached.
I have a hard drive with the following layout:
I want to delete the first two partitions (a 243 MB Linux swap partition and a 5.87 GB root partition). Problem is, every time I deleted them, Windows would also delete Drive G: and H:, leaving only drive F: intact. Deleting the two Linux partitions using GParted from a Live CD also gave the same result. I've attempted this multiple times now and, after each attempt, TestDisk always managed to recover all the deleted partitions.
Any ideas on how to delete these two partitions without affecting the rest?
I'm trying to configure a script the deletes the file and directories with more than 10 weeks on my /tmp directory, this is what i'm trying to do:
Quote:
#!/bin/bash
#Script para borrado de ficheros y PDFs de /tmp
### Directorios/PDFs a borrar
[code]....
I am running Debian testing with XFCE and have been trying various GTK email clients looking for something I like. So far I like Balsa but everytime I start the program, Debian asks for my gnome-keyring password. How do I kill this behavior?
View 2 Replies View RelatedSo, "unable to update .IECauthority hit me yesterday in a big way. After trying all sorts of suggested remedies in the [solved] and unsolved threads, it became quite evident that the chown and chmod would not work coz ubuntu cant find the "file or directory specified" by .IECauthority. {pardon the n00bspeak}
So i looked around for the "new user" option, i.e. creating a new user so i can log in. That worked. i got to terminal and used sudo adduser guest and now i can at least log in but, predictably i cant access the files of my home directory that was under my "owner" login.
How i can access these files as my new "guest" user alias?
I feel like im so close to beating this friggin .IECauthority error though i am well aware i brought all this misery upon myself coz i just had to have the extra skins for this particular screenlet...
I'm asking this in the right place. I'm using Ubuntu 10.04 LTS and recently started getting a pop-up similar to the following at every boot up: Login keyring failed Your login keyring did not succeed. Enter login keyring here: That's not [exactly] what it says, but very similar. I should probably add that I have not set up any different 'user profiles' or whatever they're called, but am the only one using this PC...at least, at the present time. Again, this only started a couple of weeks ago and I don't know what I did to start it nor what to do to stop it. I guess it's not extremely painful to have to type my password in every time, but a PITA nevertheless.
View 5 Replies View Relatedi am trying to prevent Gnome from automounting my NTFS partition. Gnome uses for this package gvfs-mount. This package with other small one's is respnsible for automounting USB changeable media like USB sticks. That works fine for me. But I don't want Gnome mount my NTFS partition on my internal storage device, where Debian Squeeze is installed too. Since Squeeze Gnome works with gvfs-mount to bind smb, ftp NTFS in. For binding a whole NTFS partition I am guessing Gnome use ntfs-3g as well. But I don't know exactly. Is there any possibility to adjust Gnome to automatically mount ONLY USB devices?
View 1 Replies View RelatedI just installed 11.2 and have this warning in messages:
gnomesu-pam-backend: gkr-pam: couldn't unlock 'login' keyring: 255
Also, there's no login screen and I can't remember how to configure for that.
I downloaded Adobe Air, both the rpm and the .bin versions. First I tried the rpm, it went through the motions of installing but just disappeared. then I tied the .bin, got tot the installer, accepted the license, entered my root password, but it stopped installing with "an error occurred. Adobe AIR could not be installed. Install either Gnome Keyring or KDE KWallet before installing Adobe AIR". I opened Kwallet and tried again, but to no avail. I am running OS11.4 64 bit. What can I do to get this thing working?
View 6 Replies View RelatedThe apt-get autoremove command, I use Debian 8 for some time now and I often install a package, test it for some minutes and remove it then. I noticed that in most cases (if not all, I'm not completely sure) all the dependencies that were installed with the package (mostly libraries, of course) stay installed on the system when I remove the package.
And there is no output of apt-get that there are unnecessary pacakges which I can remove with apt-get autoremove. The autoremove command does nothing.Before I changed to Debian, I used Ubuntu and there all the dependencies are removed with apt-get autoremove when I uninstalled a package.My question is now, is this normal? if there are fundamental differences in which packages "autoremove" removes between Debian and Ubuntu?
