Cups 2.3.1 CUPS_SIDES returns different default value than sides-default #1324
Replies: 3 comments 3 replies
-
|
Please attach a file with the whole code - you can put .txt as suffix and github allows it. I don't see how you get dest, or where do you print all attributes - I suspect you might not be talking to the same object. |
Beta Was this translation helpful? Give feedback.
-
|
I included the full output in the file as well. It is a very simple program lifted almost verbatim from one of the examples. When one physically checks the printer in question, going through the menu on the little display, the default really is 2-sided. That printer/fax doesn't get used a lot so spends most of its life sleeping. Since you didn't respond with "oh, yeah, that's fixed in . . . " I suspect but have not dug into
That is just a knee-jerk suspicion though. |
Beta Was this translation helpful? Give feedback.
-
|
Not an answer, but have identified the bulk of the problem. cupsEnumDests() returns 6 printers. 3 configured for only "defaults" and 3 others showing some of the actual capabilities. cupsGetDests() and cupsGetDests2() return only the 3 configured for defaults. The Brother printers have 600 default then either 1200 or 2400dpi for their fine/high quality. There is no real work around here. To build a list of valid dests one would have to have a bogus cupsEnumDests() call each and every time just to build the list cupsGetDests() should be building. It is also odd that the ancient HP OfficeJet Pro is playing nicest with Cups given the brother printers are much newer and driverless. I don't think I can provide more information. Yes, I know Ubuntu 20.04 and the Cups 2.3.x it has is old, but . . .
|
Beta Was this translation helpful? Give feedback.






Uh oh!
There was an error while loading. Please reload this page.
-
Yes, I know 2.3.1 is old but I'm on Ubuntu 20.04. In case this issue still exists I wish to report it and I also wish to get edification on what method should actually be trusted. My little test program dumps out the following at the start.
`Dest Name: Brother_MFC_L3770CDW_series
uri:
resolution printer-resolution-default: 600dpi
text value: 600 integer value: 600
DPI 600
xxxxxxxxxxxx found CUPS_PRINT_QUALITY_SUPPORTED
jjj: 0 integer: 4 string version: normal
A bit later down when I'm dumping all of the attributes for same printer.
output-bin-default = face-down tag: 4 output-mode-default = color tag: 4 print-quality-default = normal tag: 4 printer-resolution-default = 600dpi tag: 4 sides-default = two-sided-long-edge tag: 4 print-color-mode-default = color tag: 4 print-content-optimize-default = auto tag: 4 print-scaling-default = auto tag: 4Shouldn't the output match?
The little test program doesn't do anything kinky.
` if ( ( attr = cupsFindDestDefault( CUPS_HTTP_DEFAULT, dest, info, CUPS_PRINT_COLOR_MODE ) ) != NULL )
{
name = ippGetName( attr );
ippAttributeString( attr, value, sizeof( value ) );
out << endl << "\t---------- CUPS_PRINT_COLOR_MODE name: " << QString::fromUtf8( name ) << " default: "
<< QString::fromUtf8( value ) << endl;
}
`
value is a generic char [4096] dumping ground that got used for color in the output just prior to this so not a stale data issue.
If this has been fixed in later versions, so be it. I included the printer model here in case this was a known Brother issue for one or more models. Am I correct in assuming CUPS_SIDES should return the same value as the sides-default attribute when it gets dumped just a little later?
Beta Was this translation helpful? Give feedback.
All reactions