Bug 203585 – Printing widget does not update printers

Bug 203585 - Printing widget does not update printers

Summary:	Printing widget does not update printers

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	gtk2 (Show other bugs)
Sub Component:
Version:	rawhide
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Matthias Clasen
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	FC6Target 203586
	Show dependency tree / graph

Reported:	2006-08-22 12:26 EDT by Bill Nottingham
Modified:	2014-03-16 23:01 EDT (History)
CC List:	3 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2006-08-28 13:52:32 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Bill Nottingham 2006-08-22 12:26:52 EDT

Description of problem:

When using OO.o to print, I was only given a list of ~30 printers; a later
run of 'lpstat -a' showed 62 printers, but the printing widget never updated.

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

gtk2-2.10.2-2.fc6
openoffice.org-core-2.0.3-7.9

Comment 1 Matthias Clasen 2006-08-25 14:30:12 EDT

John, how does this work, are we not monitoring cups for new printers, after
initially populating the list ? 

What does libgnomeprintui do here ?

Comment 2 John (J5) Palmieri 2006-08-25 15:04:54 EDT

We should have a timeout that kicks in every three seconds and calls
list_printers or something like that.  Libgnomeprintui does something similar to
this.

Comment 3 Matthias Clasen 2006-08-28 12:59:46 EDT

oh, I see you are adding the timeout, but with and awesome interval of 300000
seconds instead of 3...

Comment 4 Matthias Clasen 2006-08-28 13:52:32 EDT

Fixed in 2.10.2-4.fc6

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