Bug 95267

Summary:	CUPS printers not displayed after KDE installation
Product:	[Unmaintained] kdeprint	Reporter:	David Jarvie <djarvie>
Component:	general	Assignee:	KDEPrint Devel Mailinglist <kde-print-devel>
Status:	CLOSED NOT A BUG
Severity:	normal	CC:	jlayt
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description David Jarvie 2004-12-16 14:59:59 UTC

Version:            (using KDE KDE 3.3.2)
Installed from:    Compiled From Sources
Compiler:          gcc 3.3.4 
OS:                Linux

I have CUPS installed, and not LPD. I built KDE from sources. When I displayed any of the kdeprint dialogs (Print dialog, Printing Manager dialog, Control Centre printers dialog), the CUPS printers didn't show up, despite CUPS being the selected print system. But switching to Administrator mode in the Control Centre did display the CUPS printers.

Additionally, three error messages appeared each time I displayed the Printing Manager or Control Centre print dialogs, complaining about kdeprint_lpd.la being missing.

I managed to fix the problem by selecting LPD as the print system, and then selecting CUPS again. Now the printers show up and work fine from KDE.

There must be a bug somewhere which allowed the selected print system to be LPD in some parts of kdeprint, while the dialogs displayed CUPS.

Comment 1 Cristian Tibirna 2005-09-24 07:00:53 UTC

I need a way to reproduce this.

Please, with your KDE session closed, in console mde, move (temporarily) your .kde* directory (ies) to a temporary dir. Like

mkdir ~/TEMPKDE
mv ~/.kde* ~/TEMPKDE

Then restart KDE (this will effectively reinitialize user-side configuration). See if you can reproduce the behavior that you describe.

Thanks.

Comment 2 David Jarvie 2005-10-02 17:16:12 UTC

I removed my $KDEHOME directory as you asked, and logged on to start a fresh KDE configuration, but my CUPS printers showed up correctly this time without needing to do any configuration. Note that I have upgraded to KDE 3.4.2  since the original fault report, so I'm not using the same version of KDE any more.

Also note that after installing KDE 3.3.2, I almost certainly used my existing KDE 3.3.1 $KDEHOME when I logged on for the first time, so I wouldn't have been creating a fresh KDE configuration. Perhaps it was some hangover from the previous config files which caused the problem.

Comment 3 Cristian Tibirna 2005-10-02 17:47:17 UTC

Hmmm... That means I won't be able to reproduce your first report.

I will close this report. If it ever gets reproduced (by you or somebody else) we could reopen it.

Thanks for all the tests and the report.

Comment 4 John Layt 2008-12-31 17:48:42 UTC

Closing old Resolved status bug.