On Thu, 2015-12-03 at 09:15 -0600, Mark Copper wrote:
> Has anyone started receiving the TLS fingerprint mismatch error in
> the
> last 24 hours?
>
> Thanks.
>
> $ pianobar
> Welcome to pianobar (2014.06.08)! Press ? for a list of commands.
> (i) Control fifo at /home/mark/.config/pianobar/ctl op
On 12/3/15, Mark Copper wrote:
> Has anyone started receiving the TLS fingerprint mismatch error in the
> last 24 hours?
One of the first questions I always have is did you just upgrade
anything? Yesterday's Sid Unstable upgrades caused a software fail
here that I'm currently trying to put into
Has anyone started receiving the TLS fingerprint mismatch error in the
last 24 hours?
Thanks.
$ pianobar
Welcome to pianobar (2014.06.08)! Press ? for a list of commands.
(i) Control fifo at /home/mark/.config/pianobar/ctl opened
(i) Login... Network error: TLS fingerprint mismatch.
# uname -a
L
pedro lopez wrote:
L01 No Login failed: authentication failure
Authentication failed. Generic failure
Security strength factor:0
i´m realy do this:
Leave sasl_mech_list in /etc/imapd.conf disabled:
allowplaintext: yes
#sasl_mech_list: PLAIN
sasl_pwcheck_method: saslauthd
If you create use
--- listrcv <[EMAIL PROTECTED]> escribió:
> pedro lopez wrote:
> > hi list
> >
> > this is de error, imtest
> >
> > L01 No Login failed: authentication failure
> > Authentication failed. Generic failure
> > Security strength factor:0
>
> Check out /etc/default/saslauthd and check for a
> runn
pedro lopez wrote:
hi list
this is de error, imtest
L01 No Login failed: authentication failure
Authentication failed. Generic failure
Security strength factor:0
Check out /etc/default/saslauthd and check for a running saslauthd.
Also, see man saslpasswd.
If you use PAM as authentication m
hi list
this is de error, imtest
L01 No Login failed: authentication failure
Authentication failed. Generic failure
Security strength factor:0
the right imtest out:
S: * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+
MAILBOX-REFERRALS NAMESPACE UIDPLUS ID
NO_ATOMIC_RENAME UNSELECT CHILDREN MULTI
Package: gdm
Version: 2.2.4.1-1
Severity: minor
On Mon, Oct 08, 2001 at 06:00:55PM -0400, Mike Kuhar wrote on
debian-user:
> I get this strange error after X starts, but before the GDM login
> screen:
>
> "No servers were defined in the
> configuration file and xdmcp was
> disabled. This can onl
Greetings,
I get this strange error after X starts, but before the GDM login screen:
"No servers were defined in the
configuration file and xdmcp was
disabled. This can only be a
configuration error. So I have started
a single server for you. You should
log in and fix the configuration.
Note
On Sat, 6 Oct 2001 17:09:07 -0400, "Mike Kuhar" <[EMAIL PROTECTED]> wrote:
> Greetings,
>
> I get this strange error after X starts, but before the GDM login
> screen:
>
> "No servers were defined in the
> configuration file and xdmcp was
> disabled. This can only be a
> configuration error. S
Greetings,
I get this strange error after X starts, but before the GDM login screen:
"No servers were defined in the
configuration file and xdmcp was
disabled. This can only be a
configuration error. So I have started
a single server for you. You should
log in and fix the configuration.
Note t
to override that delete the links to nologin in /etc/rc2.d
althnough its best to see whats hanging the machine at boot.
[mailto:[EMAIL PROTECTED] ]--
Linux System Administrator http://www.firetrail.com/
Firetrail Internet Services Limited
-BEGIN PGP SIGNED MESSAGE-
On Sun, 24 Oct 1999 [EMAIL PROTECTED] wrote:
> 1. I upgraded Debian 1.3.1 --> 2.1, but my kernel is still 2.0.29.
> What should I do to upgrade the kernel to 2.0.36?
If you have apt, apt-get install kernel-image-2.0.36
If you don't have apt, you can download t
I believe that installing the deb of the kernel-image 2.0.36 will get you to
2.0.36.
As for the boot question, i do not know. Perhaps you should wait a bit more ?
--- Begin Message ---
1. I upgraded Debian 1.3.1 --> 2.1, but my
kernel is still 2.0.29.
What should I do to upgrade the kernel t
[EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
> 2. When I login as any user other than root, the system rejects
> me with the error msg:
>
> "System bootup in progress -- please wait"
rm /etc/nologin
Then try to find out why the nologin file was left lying around
--
Greg Wooled
1. I upgraded Debian 1.3.1 --> 2.1, but my
kernel is still 2.0.29.
What should I do to upgrade the kernel to 2.0.36?
2. When I login as any user other than root, the system
rejects
me with the error msg:
"System bootup in progress -- please wait"
I incrementally killed all
Shalom,
i've created a dual boot/root disk and i have a problem
logging-in: I get this error:
invalid password for "UNKNOWN" on tty1
TIA,
Danny Ilan
ICQ 31119569
http://www.imagineradio.com/mymusiclisten.asp?name=danilan>
__
Get
17 matches
Mail list logo
