Bug 137960 - Missing gnome-print-manager component
Summary: Missing gnome-print-manager component
Keywords:
Status: CLOSED DUPLICATE of bug 139647
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: desktop-printing
Version: 4.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Tim Waugh
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-11-03 10:01 UTC by Taco Scargo
Modified: 2007-11-30 22:07 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:06:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Taco Scargo 2004-11-03 10:01:04 UTC
Description of problem:
gnome-print-manager is missing

Comment 1 Tim Waugh 2004-11-03 10:43:22 UTC
Fixing product.

Comment 2 Tim Waugh 2004-11-03 10:43:38 UTC
Fixing ownership.

Comment 3 Taco Scargo 2004-11-12 10:47:26 UTC
Product was moved to 'bugzilla' by Tim Waugh, moved back to RHEL 4
public beta

Comment 4 Taco Scargo 2004-11-12 10:51:53 UTC
Also missing in beta2

Comment 5 Owen Taylor 2004-11-25 14:53:37 UTC
This isn't supposed to be included, is it? 

Taco - What particular functionality are you looking for?



Comment 6 Taco Scargo 2004-11-26 08:04:01 UTC
It is included with RHEL3, so why not in RHEL4. It is the
functionality to view printer status and the documents being printed etc

Comment 7 Colin Walters 2004-11-27 17:13:51 UTC
Taco: its functionality has been broken up into several components:

1) Printer status (number of jobs) is now integrated into the print dialog
2) Your print job status is now part of the "eggcups" icon in the
notification area
3) Default printer setting is now part of the "Default Printer"
preference in GNOME

See the bug this one is duplicated as for more information.  Please
follow up on that bug if you have additional concerns.

*** This bug has been marked as a duplicate of 139647 ***

Comment 8 Red Hat Bugzilla 2006-02-21 19:06:46 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


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