Where F26 succeeds with exactly the same setup steps, F28 fails with multiple symptoms. Any print job only ends up in the queue and leads to disabling the printer and either a "filter failed" or "printer paused" error.
I've filed one SELinux error that occurs when trying to print a test page: https://bugzilla.redhat.com/show_bug.cgi?id=1572231
Has anyone managed to set up a networked "Windows Printer via Samba" using system-config-printer with F28?
On Friday, 27 April 2018 01.24.53 WEST Michael Schwendt wrote:
Where F26 succeeds with exactly the same setup steps, F28 fails with multiple symptoms. Any print job only ends up in the queue and leads to disabling the printer and either a "filter failed" or "printer paused" error.
I've filed one SELinux error that occurs when trying to print a test page: https://bugzilla.redhat.com/show_bug.cgi?id=1572231
Has anyone managed to set up a networked "Windows Printer via Samba" using system-config-printer with F28?
I have a similar problem, I am unable to print in F28 while it worked on F27 (same setup).
I described the problem here: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/t... I33KB3DVOWXCSP23NHEORDSXTQ65PTMC/
Although I had not mentioned it there I am using windows printers via samba but I did not notice any selinux issue.
Regards,
On Fri, 27 Apr 2018 10:19:43 +0100, José Abílio Matos wrote:
I described the problem here: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/t...
test@ list must be popular. No replies since April 10th despite a clear subject! What other list these days would have drawn the attention of someone with interest in Fedora's printing functionality?
On Fri, 27 Apr 2018, Michael Schwendt wrote:
test@ list must be popular. No replies since April 10th despite a clear subject! What other list these days would have drawn the attention of someone with interest in Fedora's printing functionality?
Oh -- I don't know -- for reasons unclear,the 'Reply-to' is to the initial poster alone, not the list -- just noticed this
That causes list traffic to simply disappear, unanswered
RFE to List-Owner: Please alter the Reply-to: test@lists.fedoraproject.org for this list
=======
I have 'cc'd the proper 'owner' identiy -- we shall see.
================================
That said, I was corresponding privately with a well known poster to this list about the fact that:
acceptance testing did not include a working printer for a 'Workstation' class unit
I received a prompt reply thus:
the upgrade criteria. That is noted here: https://bugzilla.redhat.com/show_bug.cgi?id=1503321#c7
Interesting bug
I see:
The decision to classify this bug as an AcceptedBlocker was made, even though there is no current criteria to warrant blocking on this. We plan to make a near-future change to the criteria so that a bug like this from this point on will be blocker-qualifying
==========
What IS the process and proper venue / place to seek changes in blocker-qualifying criteria?
Send a proposal to test@ (usually worth CCing to other lists that may be interested too). Ideally include the words 'proposal' or 'proposed' and 'criteria' or 'criterion' in the subject, cos it makes it a lot easier to find it later.
You can find lots of previous examples by, well, searching the list archives for those words. A proposal typically includes a general explanation of the nature of the proposed change and the reason for it, and the specific text you want to add or change or remove.
Thanks!
==============
I have not gotten back to searching the archives for a 'worked example' to follow yet -- not enough 'tuits'
Long form was:
I am thinking here of a comment ... made a while back, that did not provoke any response, that there was no requirement that printing actually work, much of anywhere
I particularly think that a unit in 'workstation' role should:
1. have a working LPR, [and so a matching LPD] to receive print jobs, and
2. either a. (worst choice) catch and route such to root's email as a an attachment print job file via mailx -- bad idea as it fills up /var/spool/mqueue/ [/] /var/spool/mail/
b. (perhaps better) pop up a message that print services are not yet configured, and optionally offer suggestions in a 'want to know more' link
c. (best of the lot) if print services ARE configured, hand off the print job to that service
I've been unclear about where to champion such a proposed change in release criteria
Thank you
-- Russ herrold
On Fri, Apr 27, 2018 at 12:47 PM, Michael Schwendt mschwendt@gmail.com wrote:
On Fri, 27 Apr 2018 10:19:43 +0100, José Abílio Matos wrote:
I described the problem here: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/t...
test@ list must be popular. No replies since April 10th despite a clear subject! What other list these days would have drawn the attention of someone with interest in Fedora's printing functionality?
I'd go to devel@ if something basic like this isn't working in a release version. I actually don't know off hand what release criteria we even have for printing.
On Fri, Apr 27, 2018 at 2:34 PM, Chris Murphy lists@colorremedies.com wrote:
On Fri, Apr 27, 2018 at 12:47 PM, Michael Schwendt mschwendt@gmail.com wrote:
On Fri, 27 Apr 2018 10:19:43 +0100, José Abílio Matos wrote:
I described the problem here: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/t...
test@ list must be popular. No replies since April 10th despite a clear subject! What other list these days would have drawn the attention of someone with interest in Fedora's printing functionality?
I'd go to devel@ if something basic like this isn't working in a release version. I actually don't know off hand what release criteria we even have for printing.
Or desktop@ actually is also reasonable, but that is more of a Workstation edition specific list.
On Fri, 2018-04-27 at 14:34 -0600, Chris Murphy wrote:
On Fri, Apr 27, 2018 at 12:47 PM, Michael Schwendt mschwendt@gmail.com wrote:
On Fri, 27 Apr 2018 10:19:43 +0100, José Abílio Matos wrote:
I described the problem here: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/t...
test@ list must be popular. No replies since April 10th despite a clear subject! What other list these days would have drawn the attention of someone with interest in Fedora's printing functionality?
I'd go to devel@ if something basic like this isn't working in a release version. I actually don't know off hand what release criteria we even have for printing.
We don't have any, but RP Herrold is considering proposing some.
IIRC, I've always been somewhat put off in the past by the fact that it's a *highly* driver/vendor-dependent area, which makes it tricky to formulate good criteria...
On Fri, Apr 27, 2018 at 3:16 PM, Adam Williamson adamwill@fedoraproject.org wrote:
On Fri, 2018-04-27 at 14:34 -0600, Chris Murphy wrote:
On Fri, Apr 27, 2018 at 12:47 PM, Michael Schwendt mschwendt@gmail.com wrote:
On Fri, 27 Apr 2018 10:19:43 +0100, José Abílio Matos wrote:
I described the problem here: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/t...
test@ list must be popular. No replies since April 10th despite a clear subject! What other list these days would have drawn the attention of someone with interest in Fedora's printing functionality?
I'd go to devel@ if something basic like this isn't working in a release version. I actually don't know off hand what release criteria we even have for printing.
We don't have any, but RP Herrold is considering proposing some.
IIRC, I've always been somewhat put off in the past by the fact that it's a *highly* driver/vendor-dependent area, which makes it tricky to formulate good criteria...
It's super messy everywhere.
My current opinion is: Workstation should have a release criteria for IPP Everywhere printing only (i.e. Workstation should as a client print to any IPP Everywhere printer). That's "driverless" printing. CUPS can turn any printer it supports (however indirectly, foomatic, ghostscript, gutenprint, tequila drinking games) into an IPP Everywhere printer - but I would not make it a release requirement that some random CUPS supported printer is by extension supported by Fedora. I'd make it, OK if you can get CUPS to print to your printer correctly and announce it as an IPP Everywhere printer, then any Fedora Workstation should be able to find, connect/authenticate, and print something sensible.
On Fri, 27 Apr 2018 10:19:43 +0100, José Abílio Matos wrote:
I described the problem here: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/t...
The same kid3 filter errors appear in the cups log *much* earlier. Had to skim over it with full journalctl output.