OK I used seahorse to make it unencrypted as a workaround.
___
pkg-fso-maint mailing list
pkg-fso-maint@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-fso-maint
Or maybe I can like https://superuser.com/a/141232 use
-l, --login
This argument tells the daemon it is being run by PAM. It reads all
of stdin (including any newlines) as a login password and does not
complete actual initialization.
(But I will not touch
https://ubuntuforums.org/showthread.php?t=192281=2524785#post2524785
got me thinking, maybe I can write a script...
I see the gnome-keyring-daemon man page has --unlock.
Maybe I can do
echo "my password"| gnome-keyring-daemon --unlock
in my bash profile, and then the rest of the day all apps
RT> I believe it's possible to store the GNOME keyring unencrypted, if
RT> that's what you want (based on reading your comments in the upstream
RT> report). In seahorse ("Passwords and Encryption Keys") you should be
RT> able to change the keyring password to an empty password. If I'm
RT>
OOPS DO NOT PUT THOSE FOUR LINES IN THAT FILE.
Those four lines are from a non-Debian distribution.
The immediate consequence of adding those four lines:
Upon systemctl stop nodm you will get black screen.
Nothing you can do will break out.
You will have to hit the power button. Let's hope
Package: nodm
Version: 0.13-1.3
Severity: important
File: /etc/pam.d/nodm
https://bugzilla.gnome.org/show_bug.cgi?id=784992#c2 says
It's a distribution bug for the keyring to not be unlocked automatically at
startup.
https://wiki.archlinux.org/index.php/Nodm says you should add
auth
AJ> This is documented behaviour and thus not RC, please see the release notes:
AJ> "You should not upgrade using telnet, rlogin, rsh, or from an X
AJ> session managed by xdm, gdm or kdm etc. on the machine you are
AJ> upgrading. That is because each of those services may well be terminated
AJ>
severity 853016 grave
thanks
In fact, you terminate the window the aptitude upgrade was running.
The next time the user runs apt/aptitude, he will be met with
E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct
the problem.
W: Could not lock the cache file; this
reopen 796203
found 796203 0.13-1
thanks
I've used nodm for years.
Suddenly it is asking me if it should start by default again.
You should really copy the original settings if found,
instead of asking the user something he answered already.
___
X-Debbugs-cc: 679...@bugs.debian.org, fsate...@debian.org
Package: nodm
Version: 0.12-1
>>>>> "FS" == Felipe Sateler <
FS> Control: notfound -1 231-1
FS> On 23 August 2016 at 17:40, 積丹尼 Dan Jacobson <jida...@jidanni.org> wrote:
>> reopen
Package: nodm
Version: 0.12-1
7月 11 14:51:35 jidanni2 nodm[1933]: PAM unable to dlopen(pam_ck_connector.so):
/lib/security/pam_ck_connector.so: cannot open shared object file: No such file
or directory
7月 11 14:51:35 jidanni2 nodm[1933]: PAM adding faulty module:
pam_ck_connector.so
Package: nodm
Version: 0.11-1.3
Please add NODM_OPTIONS to /etc/default/nodm,
thus finally giving the user a way to pass e.g.,
NODM_OPTIONS='--syslog --verbose'
Else believe it or not, there is no simple way to use any of the
options listed on the nodm man page!
12 matches
Mail list logo