+++ This bug was initially created as a clone of Bug #12137 +++ I've spent some considerable time getting up to speed with CUPS and M4RC. First connecting and setting up my HP 5510 USB printer locally on real hardware M4RC 32-bit works just fine. I can print locally. CUPS installs and localhost:631 works. I have two side by side 32-bit machines. One is an M3 print server that the 5510 is normally connected to. That works just fine and any M3 system on the LAN can print to it. It also prints locally. The other machine is a 32-bit updated install of M4RC. All the print utilities are installed and simply unplugging the 5510 from the M3 print server to the M4RC system that works just fine and I can print locally from the M4RC system. What does not work is any other system on the LAN, M3 or M4x, sees the CUPS printer on the M4RC system but cannot print to it. Feel free to suggest testing methods. Reproducible: Steps to Reproduce:
Assignee: bugsquad => doktor5000Status: NEW => ASSIGNED
Fix submitted via system-config-printer-1.4.3-1.1.mga4 to core/updates_testing. Will add advisory and QA procedure stuff tomorrow.
Many thanks for all your efforts.
On real hardware, M4, KDE, 32-bit Package(s) under test: system-config-printer MCC -> Hardware -> Set up the printer(s) [root@localhost wilcal]# urpmi system-config-printer Package system-config-printer-1.4.3-1.mga4.i586 is already installed Prints locally, remote M3 system on LAN does not see printer install system-config-printer from updates_testing [root@localhost wilcal]# urpmi system-config-printer Package system-config-printer-1.4.3-1.1.mga4.i586 is already installed Prints locally, remote M3 system on LAN does not see printer Test platform: Intel Core i7-2600K Sandy Bridge 3.4GHz GIGABYTE GA-Z68X-UD3-B3 LGA 1155 MoBo GIGABYTE GV-N440D3-1GI Nvidia GeForce GT 440 (Fermi) 1GB RTL8111/8168B PCI Express 1Gbit Ethernet DRAM 16GB (4 x 4GB) VirtualBox 4.2.16-1.mga3.x86_64.rpm
IMHO, the changes I made in mga_backend need to be done also in mga_printer_custom.py (see my post in dev list https://ml.mageia.org/l/arc/dev/2014-02/msg00353.html )
Question, will any fix also involve a change to M3 systems?
In VirtualBox, M4, KDE, 32-bit Package(s) under test: system-config-printer MCC -> Hardware -> Set up the printer(s) [root@localhost wilcal]# urpmi system-config-printer Package system-config-printer-1.4.3-1.mga4.i586 is already installed Prints to the updated remote printer on the updates_testing M4 system. Remote M3 system on LAN still does not see printer. Test platform: Intel Core i7-2600K Sandy Bridge 3.4GHz GIGABYTE GA-Z68X-UD3-B3 LGA 1155 MoBo GIGABYTE GV-N440D3-1GI Nvidia GeForce GT 440 (Fermi) 1GB RTL8111/8168B PCI Express 1Gbit Ethernet DRAM 16GB (4 x 4GB) VirtualBox 4.2.16-1.mga3.x86_64.rpm
I brought up another M3 system on the LAN, this time a 64-bit system, and attempted to print to the updates_testing M4 system. It was unable to see, and print, to that system. So clearly we have multiple problems here. It appears that with the installation of system-config-printer-1.4.3-1.1.mga4.i586 that the M4 systems, both local and remote, will be able to CUPS print. But at this point M3 systems cannot.
@William: seems you're testing for the wrong thing. What was fixed here is that your M4 system with the update candidate should see other CUPS servers on the same LAN (if firewall allows that) . Nothing more and nothing less. And due to some code duplication (cf. #c4 ) the fix is not complete, but searching for printers should work already as mentioned in the other bug.
(In reply to Florian Hubold from comment #8) > @William: seems you're testing for the wrong thing. What was fixed here is > that your M4 system with the update candidate should see other CUPS servers > on the same LAN (if firewall allows that) . Nothing more and nothing less. Right now it appears to me that the BUG is fixed for M4 systems both CUPS server and clients. But not for M3. And that's fine. These systems are always running here now. Likely though in the next weeks all the real hardware systems will become M4 systems so any M3 testing will have to be in Vbox.
For your M3 systems have a look if you can run the following directly: python /usr/lib/cups/backend/mga_backend If not you could easily try to download the fixed file: http://svnweb.mageia.org/packages/cauldron/system-config-printer/current/SOURCES/mga_backend?revision=589454&view=co Check for more details https://bugs.mageia.org/show_bug.cgi?id=12137#c40
(In reply to Florian Hubold from comment #10) > For your M3 systems have a look if you can run the following directly:.... Which means we do need to make a change to M3 to get it to work with an M4 CUPS server. Here's my concern. If M4 is being used as a CUPS server will an Ubuntu/SUSE/ect ect system be able to use it or are we doing something unique to Mageia?
No. This bug is not related to CUPS, but to the network printer detection in system-config-printer. So if you use CUPS directly and search for printers, this and the originating bug https://bugs.mageia.org/show_bug.cgi?id=12137 should not affect you. If there are issues with printer sharing in CUPS itself or remote printer recognition in CUPS, that would be a separate bug, and has nothing to do with this issue.
Created attachment 5047 [details] patch to mga_printer_custom.py (duplicated code from mga_backend) I think that this patch have to be applied as it was in mga_backend (http://svnweb.mageia.org/packages?view=revision&revision=592371)
please try Updated packages in core/updates_testing: ======================== system-config-printer-1.4.3-1.2.mga4.x86_64 system-config-printer-udev-1.4.3-1.2.mga4.i586 system-config-printer-debuginfo-1.4.3-1.2.mga4.x86_64 system-config-printer-debuginfo-1.4.3-1.2.mga4.i586 system-config-printer-udev-1.4.3-1.2.mga4.x86_64 system-config-printer-1.4.3-1.2.mga4.i586 system-config-printer-libs-1.4.3-1.2.mga4.x86_64 system-config-printer-libs-1.4.3-1.2.mga4.i586 from SRPMS: system-config-printer-1.4.3-1.2.mga4.src
(In reply to Philippe Makowski from comment #14) > please try.... Will try to get to that today. Thanks.
Hasn't percolated through the repo's yet. I should get to this in the next day or two.
Just to check if Mageia 3 need a fix or not in s-c-p, can you run the following : LC_ALL=C nmap -n -r -vd2 -P0 --max-retries 1 --host_timeout 16000 --initial_rtt_timeout 8000 -p 9100 -d0 10.0.0.40 with at the end the IP of the box where your printer is on LAN (10.0.0.40 on my sample) and if it fails, this : LC_ALL=C nmap -n -r -v -P0 --max-retries 1 --host_timeout 16000ms --initial_rtt_timeout 8000ms -p 9100 -d0 10.0.0.40 with at the end the IP of the box where your printer is on LAN (10.0.0.40 on my sample)
I have installed the new system-config-printer-1.4.3-1.2.mga4.x86_64 packages into my M4 32-bit CUPS server and indeed I am now able to print from the CUPS server and two other M4 Clients on the LAN see, and they are able to print, to the CUPS server. The two clients are another M4 32-bit device that was not updated with the new packages and a Vbox M4 32-bit Client that also was not updated. So the M4 clients using the old system-config-printer package were able to print to the M4 CUPS server. Also localhost:631 does in fact see the CUPS server and printer properly. I printed both from Kwrite and LibreOffice Writer. I'll put some more time into this this weekend and check M3 32/64-bit and M4 32/64-bit installs again.
(In reply to Philippe Makowski from comment #17) > Just to check if Mageia 3 need a fix or not in s-c-p, can you run the > following : > > LC_ALL=C nmap -n -r -vd2 -P0 --max-retries 1 --host_timeout 16000 > --initial_rtt_timeout 8000 -p 9100 -d0 10.0.0.40 > ok I found a Mageia3 box and it fails so s-c-p need to be patched too it relies on a old version of nmap it seems, strange that this bug raised so late so if you confirm that, we will need to apply these two patches to Mageia3 : http://svnweb.mageia.org/packages/cauldron/system-config-printer/current/SOURCES/mga_backend?r1=389214&r2=589454&view=patch http://svnweb.mageia.org/packages/cauldron/system-config-printer/current/SOURCES/mga_printer_custom.py?r1=558640&r2=609018&view=patch I let Florian doing it if need.
I've spent some considerable time this morning working with my M4 CUPS server and three M4 CUPS clients. The Server is on real hardware and is 32-bit. One of the clients is M4 32-bit and is also on real hardware. Two others, 32 & 64 bit, are Vbox clients. I also cleaned up my host naming such that there is less confusion for me as to what's where. I do have a working M3 CUPS server on the LAN. It appears that installing system-config-printer-1.4.3-1.2 does in fact for M4 appear to allow the M4 server to be accessed by the M4 clients. I have successfully printed with both Kwrite and LibreOffice Write. I'm not sure I'm quite ready to call this fixed for M4 as I'd like to see some other folks get it to work on their M4 CUPS server.
Using an M3 32 & 64 bit Vbox client I have been successful to print to the M4 32-bit CUPS server that has been updated with system-config-printer-1.4.3-1.2. The M3 Vbox clients were to the latest update and needed no basic changes to recognize and print to the M4 CUPS server. I did have to go through the printer set up at: MCC -> Hardware -> Configure Printing and allow the process to find the printer. That took a few seconds but once found I was able to access and print. localhost:631 did work on all systems tested and saw the M4 CUPS server. If we can find some other folks who can get this update to work on their systems this one may behind us. Note: as a matter of exercise I do a warm boot on the CUPS servers and clients after CUPS install and updates.
CC: makowski.mageia => (none)
(In reply to Philippe Makowski from comment #19) > I let Florian doing it if need. Sorry to reply so late. Unfortuantely I've no printer or even an mga3 install to test. Feel free to commit.
Thanks Florian
As mentioned, I've got no printer to test. philippem was working on this, assigning to him.
Assignee: doktor5000 => makowski.mageiaStatus: ASSIGNED => NEW
Seems that then system-config-printer-1.4.3-1.2.mga4 can move from testing to update Updated packages in core/updates_testing: ======================== system-config-printer-1.4.3-1.2.mga4.x86_64 system-config-printer-udev-1.4.3-1.2.mga4.i586 system-config-printer-debuginfo-1.4.3-1.2.mga4.x86_64 system-config-printer-debuginfo-1.4.3-1.2.mga4.i586 system-config-printer-udev-1.4.3-1.2.mga4.x86_64 system-config-printer-1.4.3-1.2.mga4.i586 system-config-printer-libs-1.4.3-1.2.mga4.x86_64 system-config-printer-libs-1.4.3-1.2.mga4.i586 from SRPMS: system-config-printer-1.4.3-1.2.mga4.src
Assignee: makowski.mageia => qa-bugs
(In reply to Philippe Makowski from comment #25) > Seems that then system-config-printer-1.4.3-1.2.mga4 can move from testing > to update https://bugs.mageia.org/show_bug.cgi?id=12137#c55 I believe that Bugs 12137 & 12781 are one and the same. The 1.4.3-1.2 packages seem to fix the problem for me. But, am I the only one who can test this?
On real hardware, M4, KDE, 32-bit Package(s) under test: system-config-printer system-config-printer-libs system-config-printer-udev system-config-printer-debuginfo default install of system-config-printer system-config-printer-libs system-config-printer-udev [root@localhost wilcal]# urpmi system-config-printer Package system-config-printer-1.4.3-1.mga4.i586 is already installed [root@localhost wilcal]# urpmi system-config-printer-libs Package system-config-printer-libs-1.4.3-1.mga4.i586 is already installed [root@localhost wilcal]# urpmi system-config-printer-udev Package system-config-printer-udev-1.4.3-1.mga4.i586 is already installed [root@localhost wilcal]# urpmi system-config-printer-debuginfo No package named system-config-printer-debuginfo HP 5510 printer installs, and works, locally. localhost:631 recognizes local printer install system-config-printer system-config-printer-libs system-config-printer-udev system-config-printer-debuginfo from updates_testing [root@localhost wilcal]# urpmi system-config-printer Package system-config-printer-1.4.3-1.2.mga4.i586 is already installed [root@localhost wilcal]# urpmi system-config-printer-libs Package system-config-printer-libs-1.4.3-1.2.mga4.i586 is already installed [root@localhost wilcal]# urpmi system-config-printer-udev Package system-config-printer-udev-1.4.3-1.2.mga4.i586 is already installed [root@localhost wilcal]# urpmi system-config-printer-debuginfo No package named system-config-printer-debuginfo HP 5510 printer works locally. localhost:631 recognizes local printer HP 5510 printer can be used from both a Vbox and real hardware M4 system on the LAN. Both systems see the printer at http://localhost:631/printers/ For some reason system-config-printer-debuginfo can't be found by either the MCC or urpmi even though it's there. 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
On real hardware, M4, KDE, 64-bit Package(s) under test: system-config-printer system-config-printer-libs system-config-printer-udev system-config-printer-debuginfo default install of system-config-printer system-config-printer-libs system-config-printer-udev [root@localhost wilcal]# urpmi system-config-printer Package system-config-printer-1.4.3-1.mga4.x86_64 is already installed [root@localhost wilcal]# urpmi system-config-printer-libs Package system-config-printer-libs-1.4.3-1.mga4.x86_64 is already installed [root@localhost wilcal]# urpmi system-config-printer-udev Package system-config-printer-udev-1.4.3-1.mga4.x86_64 is already installed [root@localhost wilcal]# urpmi system-config-printer-debuginfo No package named system-config-printer-debuginfo HP 5510 printer installs, and works, locally. localhost:631 recognizes local printer install system-config-printer system-config-printer-libs system-config-printer-udev system-config-printer-debuginfo from updates_testing [root@localhost wilcal]# urpmi system-config-printer Package system-config-printer-1.4.3-1.2.mga4.i586 is already installed [root@localhost wilcal]# urpmi system-config-printer-libs Package system-config-printer-libs-1.4.3-1.2.mga4.i586 is already installed [root@localhost wilcal]# urpmi system-config-printer-udev Package system-config-printer-udev-1.4.3-1.2.mga4.i586 is already installed [root@localhost wilcal]# urpmi system-config-printer-debuginfo No package named system-config-printer-debuginfo HP 5510 printer works locally. localhost:631 recognizes local printer HP 5510 printer can be used from both a Vbox and real hardware M4 system on the LAN. Both systems see the printer at http://localhost:631/printers/ For some reason system-config-printer-debuginfo can't be found by either the MCC or urpmi even though it's there. Test platform: Intel Core i7-2600K Sandy Bridge 3.4GHz GIGABYTE GA-Z68X-UD3-B3 LGA 1155 MoBo GIGABYTE GV-N440D3-1GI Nvidia GeForce GT 440 (Fermi) 1GB RTL8111/8168B PCI Express 1Gbit Ethernet DRAM 16GB (4 x 4GB) Mageia 4 64-bit, Nvidia driver
*-debuginfo are in the associated Debug medias, so if this is in Core Updates Testing then that one will be in Core Updates Testing Debug.
CC: eeeemail => (none)
(In reply to claire robinson from comment #29) > *-debuginfo are in the associated Debug medias, so if this is in Core > Updates Testing then that one will be in Core Updates Testing Debug. Do we want to include this in this testing? Or just see that it installs? I have successfully completed my testing on the x86-64 hardware. I have not enabled that repo in my testing and yes I do see that package in there.
We don't normally Bill.
For me this update works fine. I've encountered one small error here. For some reason the HP Device Manager in x86-64 is not seeing the supplies ( cartridge levels ) but that has nothing to do with CUPS working. Anyway if I don't see any objections, or further testing, I'll validate this in 24-hours.
Testing complete for mga4 32-bit & 64-bit Validating the update. Could someone from the sysadmin team push this to updates. Thanks
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugsWhiteboard: (none) => MGA4-32-OK MGA4-64-OK
Could somebody please try to summarise all this into an advisory. Is it just what was in comment 0 with the packages from comment 25? Thanks
Blocks: (none) => 14069
(In reply to claire robinson from comment #34) > Could somebody please try to summarise all this into an advisory. > > Is it just what was in comment 0 with the packages from comment 25? > yes s-c-p rely on nmap, and nmap output changed, so in s-c-p the specific Mageia code that try to discover network printers was broken.
CC: (none) => makowski.mageia
Blocks: 14069 => (none)
Advisory uploaded.
Whiteboard: MGA4-32-OK MGA4-64-OK => advisory MGA4-32-OK MGA4-64-OK
An update for this issue has been pushed to Mageia Updates repository. http://advisories.mageia.org/MGAA-2014-0173.html
Status: NEW => RESOLVEDResolution: (none) => FIXED