Bug 123730 - kpdf (or any other kde program) does not find cups printer
Summary: kpdf (or any other kde program) does not find cups printer
Status: CLOSED WORKSFORME
Alias: None
Product: kdeprint
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KDEPrint Devel Mailinglist
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-16 16:38 UTC by Ivan
Modified: 2008-12-31 19:39 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
KDE print dialog with CUPS enabled (68.07 KB, image/png)
2007-01-13 00:13 UTC, Kurt Pfeifle 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Ivan 2006-03-16 16:38:32 UTC 
Version:            (using KDE KDE 3.4.2)
Installed from:    Ubuntu Packages

The kpdf (or any other kde program) does not find cups printer, correctly configured (and printable via gnome-printer). When kprinter is ran by a terminal, it does find the cups printer. When one tries to configure via kde-printer-assistant, only putting localhost we are able to find the printer, and then no to finish configuration (it asks for a password, but none passoword works for configuration). The cups printer is configured in another machine at the same network, and works perfectly with gnome-applications.

Is this a bug?
Comment 1 Albert Astals Cid 2006-03-16 19:33:19 UTC 
No idea if it is a bug, but it is surely not a kpdf bug as we do nothing with printers than calling kdeprint to do the work.
Comment 2 Ivan 2006-03-16 19:36:27 UTC 
Should I post it to kdeprint?
Comment 3 Kurt Pfeifle 2007-01-13 00:11:41 UTC 
Ivan,

is this still a problem for you?

Look at the attached screenshot, and make sure you have "CUPS" selected as "Print system currently used:" (see bottom of screenshot).

Cheers,
Kurt
Comment 4 Kurt Pfeifle 2007-01-13 00:13:08 UTC 
Created attachment 19260 [details]
KDE print dialog with CUPS enabled


(Note, for *most* people the "port" part will be "631" not "23631")
Comment 5 Ivan 2007-01-13 00:26:41 UTC 
No more problems, it seems that everything is working all right now.
Comment 6 Ivan 2007-01-13 00:27:14 UTC 
No more problems, it seems that everything is working all right now.
Comment 7 Kurt Pfeifle 2007-01-13 06:15:56 UTC 
Thanks for confirming this, Ivan.
Comment 8 John Layt 2008-12-31 19:39:18 UTC 
Closing old Resolved status bug.