CUPS has historically applied page-ranges after number-up, to match how
page ranges and number-up interact in desktop environments and to match
user expectations ("I need to re-print the 3rd page of my presentation
that I printed 2-up")
I agree this is non-conforming to RFC 2911 section 15.3, but
Lars,
Due to the amount of information contained in the current notifications
and the lack of aggregation, the existing dbus notifier is the right way
to do this to avoid serious performance issues.
FWIW, OS X uses three "look at me" notifications (via Darwin's
notify_post API) to let application
The current release of CUPS does not have this problem. And
unfortunately we do not have time to re-develop "fixes" for old CUPS
releases that we no longer support in order to work around a design
deficiency in a Linux-specific monitoring application which should not
be using 15-minute lease times
The current scheduler/file.c code was last changed back when we added
the SyncOnClose option. The sync-on-close was removed in r9766 in May of
2011 for STR #3715, as part of the 1.5.0 release (patches are attached).
On Oct 30, 2013, at 1:02 PM, Till Kamppeter <1244...@bugs.launchpad.net> wrote:
Make up your mind. You want sync. You don't want sync.
There is no reason to renew a subscription every 15 minutes. Stop doing
that and this problem goes away.
On Oct 30, 2013, at 12:58 PM, Launchpad Bug Tracker
<1244...@bugs.launchpad.net> wrote:
> You have been subscribed to a public bug by
Well, all of that looks OK as well. Given that Epson/Avasys decided not
to log anything at all from their driver, and there is nothing obviously
wrong with the binary, there isn't much help *I* can provide...
Sorry...
--
You received this bug notification because you are a member of Desktop
Pack
Still nothing from the filter; can you provide the output from the
following commands?
file
/opt/epson-inkjet-printer-201115w/cups/lib/filter/epson_inkjet_printer_filter
ldd
/opt/epson-inkjet-printer-201115w/cups/lib/filter/epson_inkjet_printer_filter
--
You received this bug notificat
Looking at the error_log, the results are singularly unhelpful - just
that the epson driver filter exited with status 1 but nothing is logged
by the filter to say what it is doing...
You might try:
cupsctl LogLevel=debug2
and print something; perhaps the Epson driver is writing something as
8 matches
Mail list logo
