On Mon, Mar 4, 2019, 2:08 PM Ben Koenig <techkoe...@gmail.com> wrote:
> I would try removing gnome-keyring, and leave the libgnome-keyring > package alone. That annoying prompt is an executable program, and a > daemon process that likes to autostart itself. Removing that will > probably avoid breaking anything that relies on the infrastructure. > > The program can't run if the program doesn't exist... And you can > always add it back. Worst case scenario is that something doesn't run, > it won't actually break or corrupt anything to not have it. > > On Mon, Mar 4, 2019 at 8:18 AM Rich Shepard <rshep...@appl-ecosys.com> > wrote: > > > > On Mon, 4 Mar 2019, Dick Steffens wrote: > > > > > Neither of those are in the list I have. > > > > Oh! Darn! I wonder ... > > > > Here, 'ls /var/log/packages | grep keyring' returns > > gnome-keyring-3.16.0 > > libgnome-keyring-3.12.0 > > > > I wonder if removing those two would stop GE from asking for a keyring > > password. Someone (such as Ed) more familiar with the internals of > Slackware > > are more qualified than I to write if there might be unintended > consequences > > in removing those packages. > > > > Regards, > > > > Rich > > _______________________________________________ > > Do you auto login on this machine? I had Chrome do that to me on Mint > Mate because I didn't type in my password to login. Vernon _______________________________________________ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
