http://qa.mandrakesoft.com/show_bug.cgi?id=3349





------- Additional Comments From [EMAIL PROTECTED]  2003-03-16 11:54 -------
Can you just confirm whether, when there is no local account in /etc/passwd,
whether:

$ getent passwd <user> 
works correctly?

(this is the mechanism all programs should use, the getpw* fuctions, which
getent is just a simple frontend for).

Have you got ssl or tls enabled in /etc/ldap.conf? (I have mine disabled for
ssh, and have not seen this issue, although I don't print via kprinter that
much, but have at least once in the last month on cooker).



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: UNCONFIRMED
creation_date: 
description: 
My PC is configured as a LDAP-client for an LDAP-server on my main linux-box
(Mdk9.0). Everything works like a charm except printing through KDE.
I have cups configured on both machines and printing works with all printing
commands ( lp,lpr,lpr-cups,lpr-xpp ) except the ones supplied by kdebase
(kprinter, lpr-kprinter, embedded prining from konqueror, ...). The KDE-commands
crash and I receive the following message (only the relevant part):
...
(no debugging symbols found)...(no debugging symbols found)...[New Thread 16384
(LWP 4257)]

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
0x40fcdf32 in waitpid () from /lib/libpthread.so.0
#0  0x40fcdf32 in waitpid () from /lib/libpthread.so.0
#1  0x406f2e7b in KCrash::defaultCrashHandler(int) ()
   from /usr/lib/libkdecore.so.4
#2  0x41139d58 in __libc_sigaction () from /lib/libc.so.6

I think this isn't very useful, more interesting is, that all printing-related
KDE-programs ( kjobviewer, kcontrolcenter-part for printing) crash the same way !!

By the way, CUPS is left to standard-configuration, that is 'base' is accessible
by everyone without authentication, only 'admin' is left up to 'System' and
basic authentication.

Any ideas?

Reply via email to