http://bugzilla.novell.com/show_bug.cgi?id=277721 User jsmeix@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=277721#c3 --- Comment #3 from Johannes Meixner 2009-08-06 03:18:34 MDT --- Ken Yu, after you changed whatever settings for print queues, you should not restart the whole OOo again. You should first launch OOo and open its print dialog to view what OOo shows initially about print queues, then change whatever stuff in the print queues, then keep OOo running but re-open only its print dialog any check if the re-opened print dialog shows the actual current changed settings of the queues (compare my initial comment #0). If even a re-start of the whole OOo does not adapt to changes of print queues as you described in comment #2 it is even more broken but in general a restart of the whole application should not be needed to let it adapt to changes in the print queues. A note in particular regarding "default queue": For CUPS under Linux there are at least two places where a default queue is defined: 1. The system's default queue in /etc/cups/printers.conf via an <DefaultPrinter queue_name> ... </Printer> entry. 2. For each user his own default queue in ~/.cups/lpoptions via an Default queue_name entry. For each user the command lpstat -d shows the current default queue setting for this user. This default queue is what also applications should show as default queue when this user runs the application. On the other hand it could be a perfectly valid policy when an application does not adapt its printing dialog to the user's default queue but simply keeps the queue which was last used for printing from this application, provided this queue (still) exists. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.