Bug 135522 - No printing manager in kmenu and no printing option in konqueror menu
Summary: No printing manager in kmenu and no printing option in konqueror menu
Status: CLOSED DUPLICATE of bug 135561
Alias: None
Product: kdeprint
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KDEPrint Devel Mailinglist
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-12 18:16 UTC by nikos v
Modified: 2008-12-31 20:24 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description nikos v 2006-10-12 18:16:37 UTC
Version:            (using KDE KDE 3.5.5)
Installed from:    SuSE RPMs
OS:                Linux

After upgrading kde from 3.4.2 to 3.5.5 on suse linux 10.0 from open suse repositories , I have lost the ability to print from kde. Konqueror printing menu is not working, neither the printing manager exists in kmenu. Also trying to print from kate I get the following error :The connection with the  CUPS failed. Check that the  CUPS is rightly installed and that it is executed. Fault: localhost: the reading failed (15).
Printing from open office and firefox is available. CUPS is reinstalled,I don' have any idea how to fix this problem. cupsd seems to be running when executing processtable
Comment 1 Halla Rempt 2006-10-15 09:43:32 UTC
It works on my kubuntu Dapper installation with cups 1.2.2. (Just adding a datapoint)
Comment 2 Rich Johnson 2006-10-15 18:15:40 UTC
In re: to Christian's "pledge for help"
-----------------------------------------------------------------------
Kubuntu Edgy 6.10
KDE 3.5.5
CUPS 1.2.4

No problems noted with Kubuntu at this time. I even worked through the issues others were having with Bug #135561, and couldn't duplicate any of their issues.

Comment 3 Cristian Tibirna 2006-10-15 20:19:45 UTC

*** This bug has been marked as a duplicate of 135561 ***
Comment 4 John Layt 2008-12-31 20:24:53 UTC
Closing old Resolved status bug.