Issue 12173 - Printer setup loses queue after computer goes into sleep mode
Summary: Printer setup loses queue after computer goes into sleep mode
Status: CLOSED FIXED
Alias: None
Product: General
Classification: Code
Component: www (show other issues)
Version: current
Hardware: Mac Mac OS X, all
: P5 (lowest) Trivial (vote)
Target Milestone: OOo 1.0.4
Assignee: fa
QA Contact: issues@qa
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-03-10 03:04 UTC by Unknown
Modified: 2004-05-19 15:45 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

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

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2003-03-10 03:04:23 UTC 
The printer setup (spadmin) loses the queue name and flags for lp when it comes out of sleep mode. The only thing left was an lp command.  The printer is a shared USB printer.  A new printer had to be set up and the original printer queue needed to be deleted.   Then the Office and X11 (Mac beta) environment had to be completely restarted with only the new printer.  

Open office in this situation is started from the shell, using an apple script that opens the terminal sets the environment variables (it can be downloaded) and starts open office.    Printing except in the above sitution works very well.
Comment 1 scarr 2003-03-21 04:04:31 UTC 
I am assuming this is framework.  If not, please select a better
componant for this.

Thanks.
Comment 2 michael.bemmer 2003-03-24 12:47:16 UTC 
We at Sun won't handle Mac issues, sorry. Dan, can you do that?
Comment 3 fa 2003-03-24 13:57:11 UTC 
I'll take a look at it.
Comment 4 michael.bemmer 2003-05-06 15:52:09 UTC 
Too late for beta2, re-targeted to 1.1 RC.
Comment 5 michael.bemmer 2003-05-06 16:15:35 UTC 
Sorry, my last comment was nonsense, I didn't want to re-target this one.
Comment 6 Martin Hollmichel 2003-05-07 11:42:29 UTC 
this seems the wrong target to me, set to 1.0.4.
Comment 7 fa 2003-08-05 03:39:38 UTC 
Hi,

Can you reconfirm that this is still a problem when using our 1.0.3.1 release from 
June 2003?

Thanks,
Dan
Comment 8 utomo99 2003-11-17 07:31:31 UTC 
Hello, 

I found that this Issue is targetted to 1.0.4. 
Is this already solved in 1.1 ? if not Can you please retargetting
this issue since 1.0.4 is not planned. maybe to 1.1.1 ? 

Thanks
Comment 9 fa 2004-05-19 15:32:11 UTC 
closing due to inactivity, have never been able to reproduce with 1.1.x either
Comment 10 Joost Andrae 2004-05-19 15:45:50 UTC 
JA: closing