Followup to the testing in Description I brought up two KDE installs
in Vbox. The first M3-32bit the second M4RC-32-bit. Neither install
had the printer files installed. My M3 32-bit print server is up and
running and usable locally and by any M3 system on the LAN. CUPs is
running on the Server and the M3 systems on the LAN. I installed
the printer services on this M3 Vbox system, it immediately saw
the printer on the print server and I was able to use it.

I then brought up an M4RC 32-bit Live CD and set up the repos. I
then went through the printer files install process and noted that
CUPS is running. The install does not see the active, and working,
M3 Print server. localhost:631 on Firefox does not see any available
printer.

One more piece here. I brought up my working M3 print server
then at the same time brought up my real hardware M4RC test
system. I installed all the CUPS files on the M4RC. Using
the M4RC system I am able to print to the M3 print server.

All of the CUPS services on the M4RC system appear to be
working locally. I just can't use it as a print server
on the rest of the LAN.

http://localhost:631/printers/ on one of the M3 systems
on the LAN does not see the printer set up on the M4RC
system.

On real hardware.
Today I did a test install of M4 release, 32-bit KDE using:

Mageia-4-i586-DVD.iso
MD5: 5b2d9c08495497d4df641f08fa36f7ef

Installed all the necessary Printer apps. Connected my
HP All-in-One USB printer and after setting the printer
up with the HP Printer Manager I was able to print to
that locally attached USB printer. No other M3 system
on the LAN saw the printer, or was able to print to
it.

I brought up my M3 Print server. It works just fine
and any M3 system on the LAN can see it and use it.
Including the test install M4 system.

Localhost:631 on the M4 test system appears to be correctly
operating. localhost:631 on any other system on the
LAN does not see the printer on the M4 test system.

I'm seeing the same thing.  If I go through the SCP Network Printer dialog and tell it to look at the host that owns the printer, it will find it and create the printer.  But SCP no longer finds network printers automatically.

Also, if I try to print a test page on the remote printer, the job is held in the local print queue with a userid of "Unknown" and a status of "Held for authentication", if that's significant.

CC: (none) => ftg

(In reply to Frank Griffin from comment #4)

> I'm seeing the same thing.....

SUPER!!! Many thanks for the confirmation.
Makes me crazy if I'm the only one seeing
the BUG.

Actually, rereading your initial description, you say that your remote systems can see the printer but just can't print to it.

Did SCP find the remote printer automatically ?  If not, can you test the Add Network Printer using the hostname or IP of the MGA4 system and see if you can add it like that ?  I'm wondering if this procedure adds the printer but in an unusable way...

(In reply to Frank Griffin from comment #6)

> Actually, rereading your initial description, you say that your remote
> systems can see the printer but just can't print to it.

Actually I think this thing has morphed a bit since I started testing it.

You'll have to explain to me what "SCP" is and how to use it.

A couple times during this testing I was actually able to "print"
but it would only print blank pages. It's been a couple weeks
since it's done that.

Ah, sorry.  SCP is system-config-printer.  It's what runs when you do MCC -> Hardware -> Set up Printer Queues.

(In reply to Frank Griffin from comment #8)

> Ah, sorry.  SCP is system-config-printer.  It's what runs when you do MCC ->
> Hardware -> Set up Printer Queues.

I'm very carful about how I go step by step through these tough BUGs.
Everybody here is smarter then me :-0... Yes I use the SCP and also
the HP Printer Manager to set it up. The local set up and use for
a USB HP printer on M4 is now very logical and works every time.
The setted up printer is just not avaiable to other Mageia systems
on the LAN.  :-((

Will, just a thing to check, have you disabled the firewall on the mga4 server? It will rule out any issues there. You might have to restart cups there after doing so.

(In reply to claire robinson from comment #10)

> Will, just a thing to check, have you disabled the firewall on the mga4
> server? It will rule out any issues there. You might have to restart cups
> there after doing so.

Yes, there is no firewall and shorewall is completely turned off, on
all my test systems. Remember I have a completely functional M3 based
print sever on my LAN. That print server can be used by any Mageia
system on the LAN including any M4 system.

As of my testing M4 cannot be used as a print server. An M4 can be used
to print through an M3 print server.

Reproduced this here. Printer configured and tested in mga4, firewall disabled.
Printing to it via network from mga3 fails, it shows as cups-remote-pending-held. 

The print that failed was the test print from system-config-printer. I tested printing from thunderbird though and it was sent through OK.

(In reply to claire robinson from comment #12)

> Reproduced this here. Printer configured and tested in mga4, firewall
> disabled.
> Printing to it via network from mga3 fails, it shows as
> cups-remote-pending-held....

Many thanks.

is lib64nss-mdns2 ( or libnss-mdns2 ) installed ?

Tested here with server using mga3 and client under cauldron.

CC: (none) => mageia

Yes, libnss-mdns2 is installed on this M4 platform.

[root@localhost wilcal]# urpmi libnss-mdns2
Package libnss-mdns2-0.10-12.mga4.i586 is already installed

ok i update my printer server to mga4 to test more.

in cupsd.conf in the server can you remove the line 

BrowseLocalProtocols dnssd


reboot and see if it works better.

(In reply to Nicolas Lécureuil from comment #17)

> in cupsd.conf in the server can you remove the line 
> 
> BrowseLocalProtocols dnssd
> 
> 
> reboot and see if it works better.

Sorry, I commented out that line, rebooted and still the same.
It continues to work locally. Also the HP All-in-One scanner
works fine too, locally.

and nothing when you open s-c-p ?

(In reply to Nicolas Lécureuil from comment #19)

> and nothing when you open s-c-p ?

On the M4 system under test the

MCC -> Hardware ->  Set up the printer(s)...

Looks just fine and works locally.

The system I am using for this reply is an M3, 32-bit, KDE system
that I use all the time and works fine with the M3 print server.
MCC -> Hardware ->  Set up the printer(s)...
does not see the M4 test system printer.
localhost:631 in Firefox on the M3 system does not see the printer
on the M4 test system.
localhost:631 in Firefox on the M4 system under test does see the
printer and indicates it's shared.

There is no firewall on either of the systems. My protection here
is a Netgear router.

It's 1PM here in California and I can leave the test system running
for quite some time. Feel free to present any hints.

My schedule over the next days.

FYI. I am on California time.
Monday I will be available off and on. For sure in the evening.
Tuesday morning and afternoon I will be in until about 3PM.
I will then be starting my travels to FOSDEM. Tuesday evening
I will be out of my apt and away from my testing machines but
will be able to receive and send e-mails and update this BUG.
Wed early I am on a plane headed for Brussels. I'm not bringing
my printer with me.  :-))

Oh, if there are no protocols defined you likely wont see anything by magic.

You will need at least:

BrowseLocalProtocols CUPS

to see the printers which advertise themselves on the network via the CUPS native protocol.

The dnssd is a more generic alternative that's getting more popular which uses avahi/bonjour/zeroconf/mDNS to do service discovery.

So assuming the M3 print server advertises itself via CUPS protocol, and BrowseLocalProtocols is set to CUPS on the print client, then they should see each other... in theory!

CC: (none) => mageia

One more sanity test here. I set up a new install, up-to-date,
M4 32-bit in Vbox and:

MCC -> Hardware ->  Set up the printer(s)

that allowed all the necessary CUPS bits and parts to install.
Just for yuks I rebooted the M4 Vbox system under test. The
LAN M3 print server is up and running and can be used by any
M3 system on my LAN. I then opened Kwrite, created a one
line document, and was able to print ( from the M4 system
under test ) to the printer on the M3 print server.

So it appears that M4 can use a properly set up CUPS print
server it just can't be one.

this statement is wrong because here it works for me with a server using M4

Please try new cups rpm.

(In reply to Nicolas Lécureuil from comment #24)

> this statement is wrong because here it works for me with a server using M4
> 
> Please try new cups rpm.

Is the new CUPS rpm in the M4 ( cauldron ) repo?
What is the name of the rpm?

Bill IIUC you are using Mga4 in Vbox, do you have the networking type set to bridged?

(In reply to claire robinson from comment #26)

> Bill IIUC you are using Mga4 in Vbox, do you have the networking type set to
> bridged?

Yes, the test installs in Vbox the network is set to Bridged.
Also I am testing the M4 print server install on real hardware.
And the M3 install trying to use it is real hardware.
I have a little time this morning to do further testing.
Shorewall on all systems is turned completely off.

Can you please test again using  cups-1.7.0-7.mga4? It should be available soon on public mirrors.

CC: (none) => ennael1

(In reply to Anne Nicolas from comment #28)

> Can you please test again using  cups-1.7.0-7.mga4? It should
> be available soon on public mirrors.

Sorry Anne, I'm going to have to count on Claire going forward.
I am out the door headed to FOSDEM right now. I trust this
will work itself out. I'll leave it to you guys to decide if
this can really be remedied after release and not hold that up.
If it's simply an update of an RPM then be it so.

Next time I'm really going to get a chance
to look at this will be Sunday, 9 Feb.

(In reply to William Kenney from comment #30)
> Next time I'm really going to get a chance
> to look at this will be Sunday, 9 Feb.

I think this will have to do for release.

I guess we can continue to debug and issue updates as needed.

(In reply to Colin Guthrie from comment #31)

> I think this will have to do for release.
> 
> I guess we can continue to debug and issue updates as needed.

I have no problem with that Colin.
Thanks for all the hard work.

OK back on line here after FOSDEM.

I have executed a completely new install using:

Mageia-4-i586-DVD.iso
MD5: 452b3003766f2bcec202e0399a6708e8

On real hardware and updated it. This is the offical
release ISO. Install went fine as well as all the
printer/CUPS rpms. Printing using a local printer
runs just fine. The printer is still not visable
from another Mageia(3) system(s) on the LAN. Now that
I am back and organized I can continue testing this
as needed.

Hi Bill,

For the MGA3 system with which you're testing, you'll need to make sure it's advertising itself properly via mdns. This is the only system now supported by CUPS since the "CUPS" advertising method was removed (it was a horrible design!)

You can browse for such services using the avahi-browse utility: avahi-browse -ta

This should show you your printer. If it does not, then there is no chance that cups will see it. I suspect it needs to be enabled on your MGA3 box and restarted first.

All the best

I am creating a new M4 64-bit on real hardware install
now. That to test the Kwrite on Nvidia problem. Should
this M4 system see the printer on another M4 system
straight up?

(In reply to William Kenney from comment #35)
> I am creating a new M4 64-bit on real hardware install
> now. That to test the Kwrite on Nvidia problem. Should
> this M4 system see the printer on another M4 system
> straight up?

I guess that depends on firewall settings. You may have to open up UDP port 5353 if they are locked down.

(In reply to Colin Guthrie from comment #36)

> I guess that depends on firewall settings. You may have to open up UDP port
> 5353 if they are locked down.

I count on my Netgear Router for security. All the installs
in the LAN, including in Vbox, the Firewall is pulled down.

Created attachment 4977 [details]
avahi-browse -ta results

Ok, the just newly installed M4 64-bit system sees the printer
on the just installed M4 32-bit system. Kwrite and LibreOffice
see the correct printer on the correct system. localhost:631
on the M4 64-bit system sees the M4 32-bit printer.

But....

Printing does not occur if I tell the app to print.

I have attached to this bug the avahi-browse -ta results
on both systems.

(In reply to Frank Griffin from comment #4)
> I'm seeing the same thing.  If I go through the SCP Network Printer dialog
> and tell it to look at the host that owns the printer, it will find it and
> create the printer.  But SCP no longer finds network printers automatically.

Just noticed that because a user stumbled upon it by sheer luck.

Have a look at or execute /usr/lib/cups/backend/mga_backend which is our custom backend for s-c-p to detect network printers. It simply will not return any printer because nobody detected that the script doesn't work anymore :/

This is what it looks like (even in Cauldron)

[doktor5000@Mageia3 ~]$ python /usr/lib/cups/backend/mga_backend
Traceback (most recent call last):
  File "/usr/lib/cups/backend/mga_backend", line 65, in <module>
    detect_network_printers()
  File "/usr/lib/cups/backend/mga_backend", line 13, in detect_network_printers
    defaultiface = defaultentry[0]
TypeError: 'NoneType' object has no attribute '__getitem__'

philippem was so kind to fix this via http://svnweb.mageia.org/packages/cauldron/system-config-printer/current/SOURCES/?view=log just some minutes ago, output should look like this now:

http://pastebin.mozilla.org/4258997

I've just pushed this (system-config-printer-1.4.3-3.mga5) for cauldron, as it was broken anyway and needed fixing.
I've not followed the bug further, but isn't this the original root cause, or should I open a separate bug for this system-config-printer issue?

And thanks to Philippe :)

CC: (none) => doktor5000, makowski.mageia
Hardware: i586 => All
Summary: Remote CUPS server not working on (M4RC) Cauldron => Remote CUPS server not being detected automatically, only when searching for hostname
Source RPM: (none) => system-config-printer
Whiteboard: 4RC => (none)

Your children and your children's children shall rise up and call you blessed (you too, Phillipe).

Thanks, I was just about to post here saying that I'm seeing this with an all MGA4 (actually cauldron) mix as opposed to an MGA3/MGA4 issue.

(In reply to Florian Hubold from comment #40)
> or should I open a separate bug for this system-config-printer issue?

We'll need one once the fix is backported to Mageia 4.

It makes my day to see other people experiencing the same thing.  :-)))
Thanks all.

The new s-c-p now shows only "Find network printer" under Network Printer, and wwhen you supply a hostname, it correctly displays the two IPP printers for the host and allows them to be added.  

However, trying to print a test page still gives the error "cups-remote-stopped" with reason "Filter Failed", and the log messages:

D [12/Feb/2014:08:41:36 -0500] [Job 28] gs: No such file or directory
D [12/Feb/2014:08:41:36 -0500] [Job 28] PID 2394 (/usr/lib/cups/filter/gstoraster) exited with no errors.
D [12/Feb/2014:08:41:36 -0500] [Job 28] prnt/hpcups/HPCupsFilter.cpp 542: cupsRasterOpen failed, fd = 0
D [12/Feb/2014:08:41:36 -0500] [Job 28] PID 2395 (/usr/lib/cups/filter/hpcups) stopped with status 1.
D [12/Feb/2014:08:41:36 -0500] [Job 28] Hint: Try setting the LogLevel to "debug" to find out more.
D [12/Feb/2014:08:41:36 -0500] [Job 28] prnt/backend/hp.c 833: ERROR: null print job total=0
D [12/Feb/2014:08:41:36 -0500] [Job 28] PID 2396 (/usr/lib/cups/backend/hp) exited with no errors.
D [12/Feb/2014:08:41:36 -0500] [Job 28] End of messages
D [12/Feb/2014:08:41:36 -0500] [Job 28] printer-state=3(idle)
D [12/Feb/2014:08:41:36 -0500] [Job 28] printer-state-message="Filter failed"
D [12/Feb/2014:08:41:36 -0500] [Job 28] printer-state-reasons=none
E [12/Feb/2014:08:46:39 -0500] [Job 28] Stopping unresponsive job.

The problem in comment#44 is unrelated, as it fails in the same way on the system that owns the printer.  Changing the driver to Foomatic fixed it, so the problem is with GhostScript.

For ghostscript see https://bugs.mageia.org/show_bug.cgi?id=11684#c18

For s-c-p I've prepared the fix for Mageia 4 already and will commit and submit it after opening a new bug.

Priority: release_blocker => High
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=11684
Assignee: mageia => doktor5000

See https://bugs.mageia.org/show_bug.cgi?id=12781#c1 for update candidate for Mageia 4 which can be tested already.

*** Bug 12871 has been marked as a duplicate of this bug. ***

CC: (none) => geiger.david68210

What's up ?

This bug is still not fixed,

I can not print locally, all shared printers from my post mga4 are not visible and usable on MGAGROUP network.

(In reply to David GEIGER from comment #49)
> What's up ?
> 
> This bug is still not fixed

Feel free to fix it. As mentioned, I've got no printer to test. philippem was working on this, assigning to him.

Status: ASSIGNED => NEW
Assignee: doktor5000 => makowski.mageia

(In reply to David GEIGER from comment #49)
> What's up ?
> 
> This bug is still not fixed,
> 
> I can not print locally, all shared printers from my post mga4 are not
> visible and usable on MGAGROUP network.

can you please first under Mga4 use system-config-printer-1.4.3-1.2.mga4
and after that report clearly what your problem is or if it is solved using this version

I can certainly work on this too.

Note that I do in fact have a working M4 system to which is connected
an HP 5510 ( USB ) and that works both locally and from any other
Mageia system on the LAN. This "print server" was modified by a fix
quite some time ago. I will not be using this as my test platform.

On real hardware, M4, KDE, 32-bit

Package(s) under test:
system-config-printer system-config-printer-libs system-config-printer-udev

Actually in fact I have two M4 i586 platforms that can support both
a local USB printer and any M4 ( and I believe M3 ) systems on the LAN.
Here are the system-config-printer rpms on those two systems:

[root@truman wilcal]# urpmi system-config-printer
Package system-config-printer-1.4.3-1.2.mga4.i586 is already installed
[root@truman wilcal]# urpmi system-config-printer-libs
Package system-config-printer-libs-1.4.3-1.2.mga4.i586 is already installed
[root@truman wilcal]# urpmi system-config-printer-udev
Package system-config-printer-udev-1.4.3-1.2.mga4.i586 is already installed

HP 5510 all-in-one USB printer connected to system under test Prints
locally and any other M4, and I believe M3, system on the LAN can print
through this device.

Test platform:
Intel, P4 530J 3.0 GHz, 800MHz FSB, 1MB L2, LGA 775
GigaByte  GA-81915G Pro F4  i915G  LGA 775  MoBo
 Marvel Yukon 88E8001 Gigabit LAN
 Intel High Def Audio, Azalia (C-Media 9880) (snd-hda-intel)
 Intel Graphics Media Accelerator 900 (Intel 82915G)
Kingston 4GB (2 x 2GB) DDR400 PC-3200
250GB Seagate
Kingwin KF-91-BK SATA Mobile Rack
Kingwin KF-91-T-BK SATA Mobile Rack Tray
Sony CD/DVD-RW DWQ120AB2

http://localhost:631/ works locally and on the LAN

The "print server" is at IP 192.168.1.9

http://192.168.1.9:631/  also works from any other M4 system on the LAN

This is a duplicate of:

https://bugs.mageia.org/show_bug.cgi?id=12781

which has been resolved.

Status: NEW => RESOLVED
Resolution: (none) => FIXED