Bug 139680 - KDEInit could not launch 'tryprint.pl'
Summary: KDEInit could not launch 'tryprint.pl'
Alias: None
Product: Fedora
Classification: Fedora
Component: kdelibs (Show other bugs)
(Show other bugs)
Version: 3
Hardware: i686 Linux
Target Milestone: ---
Assignee: Ngo Than
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2004-11-17 14:36 UTC by Nuno
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-11-17 16:03:55 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Nuno 2004-11-17 14:36:22 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20040914

Description of problem:
I recently upgraded from Fedora Core 2 to Fedora Core 3.

In Fedora Core 2, when I pressed the Print Manager button in the KDE
bottom panel (the panel with the K button), it opened the print
manager, where I could see and manage printers and print jobs.

Now, in Fedora Core 3, when I press the Print Manager button, I get
this error:

"KDEInit could not launch 'tryprint.pl':

Could not find 'tryprint.pl' executable."

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Press the Print Manager button in the KDE panel

Actual Results:  I get the error described and the print manager
doesn't work

Expected Results:  Print Manager should open

Additional info:

Comment 1 Ngo Than 2004-11-17 15:15:35 UTC
strange, i did not see the "Print Manager" button any more! and it
should not show up on panel. Have you restart KDE after FC3 update?

could you please send a screenshot of this button. thanks

Comment 2 Ngo Than 2004-11-17 16:03:55 UTC
ok, it seems that the 'tryprint.pl' file is removed in new 
desktop-printing in FC3. The "Print Manager" button still has the old
Exec entry and it caused this problem.

In this case you have to remove this button and readd it again.

Note You need to log in before you can comment on or make changes to this bug.