Bug 66494 - error: kdeprintd not detectable while printout from kde applications
Summary: error: kdeprintd not detectable while printout from kde applications
Status: CLOSED NOT A BUG
Alias: None
Product: kdeprint
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KDEPrint Devel Mailinglist
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-24 12:19 UTC by Unknown
Modified: 2008-12-31 13:19 UTC (History)
1 user (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description karl moharis 2003-10-24 12:19:08 UTC 
Version:            (using KDE KDE 3.1.3)
Installed from:    SuSE RPMs
OS:          Linux

I use KDE 3.1.3(updated with Suse-rpms) on Suse 8.2.

Cups is working fine, i can print several testpages and documents via OpenOffice.
When I try to print in any KDE-application, I get the following error:
***
Fehler bei der Druckausgabe. Das System meldet:

Abh
Comment 1 Michael Goffioul 2003-11-28 17:59:13 UTC 
No, you shouldn't link...
Could you check that the service is available in service configuration
(KControl -> System -> ...)

Michael.
Comment 2 karl moharis 2003-11-29 14:02:52 UTC 
Sorry, I couldn't really relive this bug, cause I have had several problems with my system and after fixing, i've just installed the vanilla SuSE(/Novell:)8.2.

I'm shure the printer was shown on Kcontrol->System->...and I've also tried to mark as standard.
Comment 3 Michael Goffioul 2004-02-24 10:23:00 UTC 
Do you still have the problem?
Can you check the service is active using "dcop" utility?

dcop kded
dcop kded kdeprintd

Michael.
Comment 4 Stephan Kulow 2004-06-01 19:13:29 UTC 
Replaced madxray@lycos.de with null@kde.org due to bounces by reporter
Comment 5 Cristian Tibirna 2005-08-22 21:30:48 UTC 
UNCONFIRMED (batch reassigning messed this)
Comment 6 Cristian Tibirna 2005-09-24 05:02:59 UTC 
No answer after 19 months. Also, original reporter seems to have moved ahead. No confirmation possible.
Comment 7 John Layt 2008-12-31 13:19:48 UTC 
Closing old Resolved status bug.