Subject: Re: (1.5.2) KDE / konqueror problems: ssl, cd player, printing
To: Anne Bennett <anne@alcor.concordia.ca>
From: Nick Hudson <skrll@netbsd.org>
List: netbsd-users
Date: 02/23/2002 15:29:52
On Saturday 23 February 2002 2:31 pm, Anne Bennett wrote:
> Nick Hudson <skrll@netbsd.org> responds to my problems with KDE:
> 
> >> Does anyone have KDE 2.2.2 (especially Konqueror) working properly 
under
> >> NetBSD 1.5.2?  Things that don't work for me:
> >> 
> >>   - https URLs in Konqueror: a window is popped up claiming that 
the
> >>     certificate "failed the authenticity test", when I know that 
the
> >>     certificate is perfectly valid.  The "spewing output" shows :
> [...]
> >>     Trying to "continue" and "accept forever" continues, but does 
not
> >>     seem to store the certificate, so the errors keep popping up 
(so
> >>     to speak!).
> > 
> > This is known, but no-one has had time to look into it yet.
> [...]
> > I now know why this is and it shouldn't be too hard to fix.
> 
> OK, now you've got me all excited. :-)  Seriously, I usually try to
> fix a problem before I report it, but KDE is so huge that in this case
> the learning curve is insurmountable in the time I have to play with
> it. :-(  Will you post a patch?

I've commited the fix to pkgsrc.

> >>   - I can't print; I get complaints that "kdeprintd" cannot be
> >>     contacted, no matter whether I try printing with an external
> >>     program (lpr -Pps), or with the "lpd" or "lpr" options.  (At 
least
> >>     I can print to a file).
> > 
> > This is related (I think) to a problem in the 1.5.2 toolchain. It 
> > doesn't exist if you compile KDE with 1.5.3_ALPHA or -current.
> 
> Interesting.  I don't see myself upgrading the O/S again just yet (I
> just came up to 1.5.2 from 1.4.1 last month!).  What do you mean by
> "toolchain"?  Is the difference something I can patch in to 1.5.2?  Is
> there *supposed* to be a "kdeprintd" daemon running?  I would have
> hoped that when I selected "print through external program", all fancy
> stuff would be bypassed...

I'm not sure what fixes the problem between 1.5.2 and 1.5.3_ALPHA maybe 
you could test a few things for me?

Nick