FS#64149 - wine fails to use CUPS printers and falls back to LPR

Attached to Project: Arch Linux
Opened by Ingo Lafrenz (Curly060) - Wednesday, 16 October 2019, 16:41 GMT
Last edited by Felix Yan (felixonmars) - Sunday, 17 November 2019, 03:07 GMT
Task Type Bug Report
Category Arch Projects
Status Closed
Assigned To Felix Yan (felixonmars)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
wine under Arch Linux falls back using LPR instead of using CUPS even though libcups or lib32-libcups is installed.


Additional info:
* package version(s): wine-4.17

Steps to reproduce:
- install base arch system, a working desktop environment, CUPS and wine (important packages: cups, libcups, lib32-libcups, wine, wine_gecko, wine-mono)
- configure any CUPS printer (e.g. the PDF printer)
- start Notepad in a clean Wine Prefix like so:
export WINEARCH=win32
export WINEPREFIX=~/.wine-test
rm -rf $WINEPREFIX
wine notepad
- Now open the printing dialog (Control+P or File/Print...)

Under "printer comment" it says: "WINEPS Printer using LPR"
What I expected is: "CUPS:PDF" (if the printer name was PDF)

The problem with the LPR fallback is that you only get a standard set of paper sizes and not the ones that are actually reported by CUPS.

Solution:
Make libcups a required dependency. I have rebuilt wine with libcups installed and then everything works as expected.
This task depends upon

Closed by  Felix Yan (felixonmars)
Sunday, 17 November 2019, 03:07 GMT
Reason for closing:  Fixed
Additional comments about closing:  4.19-1
Comment by Felix Yan (felixonmars) - Friday, 15 November 2019, 06:53 GMT
I have added libcups/lib32-libcups to makedepends and verified that my CUPS printers are now present in wine notepad. Please try wine/wine-staging 4.19-1.
Comment by Michel Koss (MichelKoss1) - Friday, 15 November 2019, 10:47 GMT
I can confirm it works however only with fresh clean WINEPREFIX
Comment by Ingo Lafrenz (Curly060) - Saturday, 16 November 2019, 07:36 GMT
I can confirm that this is working indeed - and in contrast to Michel's comment this is working in a "dirty" WINEPREFIX, too!

=> Task can be closed.
Comment by Michel Koss (MichelKoss1) - Saturday, 16 November 2019, 18:26 GMT
@Curly060 wierd, I tried 3 old prefixes and it didn't worked why work with any new prefix I created. Parhaps some config nuisance.
Comment by Felix Yan (felixonmars) - Saturday, 16 November 2019, 18:58 GMT
Here in my environment it works with both old and new clean prefixes.
Comment by Michel Koss (MichelKoss1) - Saturday, 16 November 2019, 22:48 GMT
@felixonmars whatever is the cause, its not related to this ticket. Feel free to close.

Loading...