Bug 1175341 - Could not configure "print over network" with yast2 printer
Could not configure "print over network" with yast2 printer
Status: RESOLVED WONTFIX
Classification: openSUSE
Product: openSUSE Distribution
Classification: openSUSE
Component: Printing
Leap 15.2
Other Other
: P5 - None : Major (vote)
: ---
Assigned To: Johannes Meixner
Johannes Meixner
https://lists.opensuse.org/yast-devel...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2020-08-17 09:15 UTC by Ralf Habacker
Modified: 2020-09-11 09:48 UTC (History)
0 users

See Also:
Found By: Community User
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ralf Habacker 2020-08-17 09:15:50 UTC
I started 'yast2 printer' and tried to configure "Do all printing via One Single Server".

I selected  

   [x] Do all printing via One Single Server

and entered a print server running cups. 

After pressing the "Test Server" button it says that the print server is reachable.

After pressing "okay" I get 

    Error
    "A locally running CUPS daemon is still accessable" [1]

and after pressing "okay"

    Error
    "Failed to apply the settings to the system"

and the settings is not applied.

ADDITIONAL INFORMATION
1. A workaround I found out it to add a new line specifying the requested server to /etc/cups/client.conf as 

    ServerName <host>

and to restart cups.

2. Another workaround is to run

    systemctl stop cups.path cups.socket

before running the yast2 printer module and 

    systemctl start cups.path cups.socket

afterwards.

3. Running

    systemctl stop cups

prints

    Warning: Stopping cups.service, but it can still be activated by
       cups.path
       cups.socket

This let me think that the parser in the yast2 printer module detecting the cups state after restarting has an issue. 

4. Running 

    systemctl -q stop cups 

does not print the warning and let me think that this would be the smallest fix for the yast2 printer module.
Comment 1 Johannes Meixner 2020-09-11 09:48:16 UTC
Regarding the YaST printer module:

In practice the YaST printer module is no longer
acually further developed since it was
"converted from YCP to Ruby by YCP Killer" that happened
in July 2013, see the yast2-printer.changes entry
----------------------------------------------------------
Wed Jul 31 08:37:43 UTC 2013 - yast-devel@opensuse.org

- converted from YCP to Ruby by YCP Killer
  (https://github.com/yast/ycp-killer)
- version 3.0.0
----------------------------------------------------------
at
https://build.opensuse.org/package/view_file/YaST:Head/yast2-printer/yast2-printer.changes?expand=1

My last change is dated Mon Jan 19 14:51:39 UTC 2015
and my last actual further development enhancement are dated
before it was "converted from YCP to Ruby by YCP Killer".

Since that time the YaST printer module is kept working as is
as far as possible with reasonable effort by YaST team members
who know about how to deal with their generated Ruby code.

Since my YCP code was converted into generated Ruby code
it is no longer my code and it is no longer code
that I could further develop with reasonable effort.

Because the YaST printer module is based on the traditional
way how printing works with CUPS <= 1.5.4 in particular for
printing in the network, the YaST printer module intentionally
fails with error messages when things won't work with nowadays
way how printing in the network works with CUPS >= 1.6
cf. "CUPS >= 1.6 has major incompatible changes" in
https://en.opensuse.org/SDB:CUPS_in_a_Nutshell

According to
htps://bugzilla.suse.com/page.cgi?id=status_resolution_matrix.html
I can only close it as "wontfix" because this issue is a bug
but it cannot be fixed in practice in foreseeable future.

See also
https://lists.opensuse.org/yast-devel/2015-03/msg00044.html
https://features.opensuse.org/308045
https://features.opensuse.org/316789
At least currently links to features.opensuse.org fail with
"the service you want to access is not supported any longer"
so it seems those feature requests are no longer accessible.