Would the maintainer of the HP/CUPS print system please attempt a new, from the ground up, install of the print system on M4 Cauldron. I use an HP All-in-One USB printer that's worked for years on Mandriva/Mageia(3) and continues to do so. This morning I tried to install the HP/CUPS system on real hardware and although the software installed the printer did not work. I test using the following with the printer connected and turned on: MCC -> Hardware -> Set up the printer(s),.... With the printer turned on using Xsane I am successful in scanning a document, and saving a document. So the connection is good. The HP Manager does not see the printer function of the same printer. Also I use a seperate M3 system connected to the same printer for my LAN printer and that works both locally and from any other Mageia system on the LAN. Thanks. Reproducible: Steps to Reproduce:
and is the cups service running ?
Component: Installer => RPM Packages
(In reply to Manuel Hiebel from comment #1) > and is the cups service running ? Yes, it is. Everything seems to load and start just fine. I've completely turned off shorewall.
Created attachment 4361 [details] List of running processes Here's a ps -A listing of what's running on the test platform. It's real hardware. Modular HD and a HD with M3 and cups running on it supports the printer just fine.
With the latest M4 Alpha3 a new install the printer will work locally but for some reason other Mageia systems on the LAN don't see the CUPS printer.
Whiteboard: (none) => 4alpha3
Have you disabled/opened the firewall? Port 631 for cups
CC: (none) => eeeemail
I believe I have. I'm gonna take another look at it tomorrow. Personal Firewall is set to nothing.
Do you have avahi running on both the print server and client machines? I think the new CUPS needs that for remote printer browsing.
On the M3 client box: [root@sherman wilcal]# urpmi avahi Package avahi-0.6.31-2.3.mga3.i586 is already installed [wilcal@sherman ~]$ ps -A PID TTY TIME CMD 1 ? 00:00:02 systemd 2 ? 00:00:00 kthreadd 3 ? 00:00:03 ksoftirqd/0 5 ? 00:00:00 kworker/0:0H 7 ? 00:00:00 kworker/u:0H ... ... ... 585 ? 00:00:00 systemd-logind 589 ? 00:00:03 dbus-daemon 590 ? 00:00:00 avahi-daemon 591 ? 00:00:00 rsyslogd 595 ? 00:00:00 upowerd 601 ? 00:00:00 kdm 604 ? 00:00:00 avahi-daemon 648 ? 00:00:00 acpid 762 ? 00:00:00 sensord
More testing on my part in the next days. Probably over the weekend.
CC: (none) => thierry.vignaud
After a full install to an initially blank drive using 32-bit M4 boot.iso ( 10/03/13 ) with the source being ftp://mirrors.kernel.org I find that this situation continues. I can print, and scan, from my All-in-one HP printer locally but for some reason other M3 clients on the LAN network cannot see the printer nor print. Turning the M3 "Print Server" back on and I can print from any of those clients. Note that this newly created M4A3 platform proftpd, httpd and sshd all work just fine with the same clients on the LAN.
cups-browsed is running .... 774 ? 00:00:00 polkitd 778 ? 00:00:00 cups-browsed 783 ? 00:00:00 sensord .... but cupsd is not. Is that a problem?
MCC -> System -> Manage system services -> cups indicates it's running MCC -> System -> Manage system services -> cups-browsed indicates it's running
More sanity testing today. I have several M3 installs on my LAN, all different hardware, all are loaded with the HP printing utilities and CUPS. There was a recent M3 update of these printing apps and as far as I can test the local, and remote via CUPS, function continues to operate properly as long as I am using M3 everywhere. The M3 system that is connected to the printer is real hardware and features a removable replaceable hard drive system. One hard drive contains the working M3. Another contains an updated M4 Cauldron install. Switching out the M3 drive for the M4 drive, updating that as of today, this bug persists. I can print locally but none of the M3 workstations ( that worked with the same hardware with the M3 drive ) are able to print. They are all reporting that the printer is "not connected". All the systems have installed httpd, proftpd, webmin @ Port 10000, sshd and all that works just fine everywhere. The firewalls of all the systems are turned off.
I confirm that this condition exists in M4B1. In addition the printer install process in M4B1 has become overly onerous. Would the developer of the HP Printer / CUPS process please execute a from a blank drive up install of M4B1 the install the printer/cups/HP USB printer system and try to improve the experience. Thanks
Whiteboard: 4alpha3 => 4beta1
I think you're getting bitten by bug#10985 , which is now fixed.
CC: (none) => ftg
Thanks for the update Frank. This morning I updated my hardware based M4B1 test system. That appeared to included an update to CUPS. I then rebooted the system. This issue still exists. Do note that the M4B1 test system does in fact print locally now but seems not to be accessable via CUPS from other M3 systems on my LAN. Is there some kind of CUPS tool to check its status? Thanks
If your local system couldn't define the printer before, but can now, it was definitely bug#10985 . As for the remote access, I've noticed for some months now that s-c-p, which used to autodetect shared printers, doesn't any more. I have to do "Add Printer" -> "Network Printer" -> "Find Network Printer" and search on the hostname which owns the printer. Then it gets found just fine. I wasn't sure if this was by design or not, but since something worked, I didn't pursue it.
Lemme tinker with it. Your comment: ""Add Printer" -> "Network Printer" -> "Find Network Printer" is with the HP Device Manager correct? Several versions ago the installation of an HP USP printer on Mandriva/Mageia was extremely easy. With nothing installed at all you simply connected the USB printer to the system and turned it on. A popup window would open and ask if you wanted to install the printer. You clicked on Yes, it would ask for Admin ID/PW and the process would complete quickly. The printer would then be usable both locally and on the LAN. Now this process has become very difficult at best. Thanks
(In reply to William Kenney from comment #18) > Lemme tinker with it. Your comment: > > ""Add Printer" -> "Network Printer" -> "Find Network Printer" > > is with the HP Device Manager correct? No, it's with s-c-p (system-config-printer), which is what you execute when you run mcc -> Hardware -> Set up Printers. You shouldn't need HP-specific software to install a local printer at all. s-c-p is supposed to know about HP printers, and even about those with scanners. And it does, at least on my system. I have an MF 3030 which gets detected as soon as it's plugged in, and a printer created for it automatically. As for detecting network printers, AFAIK that's supposed to happen because CUPS on each system which has attached printers broadcasts those printers every 30 seconds or so. s-c-p used to detect this. I can't recall whether it created printers automatically, but if you said "Add a printer", it would show you all the ones for which it had received broadcasts without you having to tell it to probe a particular host. Now it doesn't. > > Several versions ago the installation of an HP USP printer on > Mandriva/Mageia was extremely easy. It still is. More so than before. It used to be that just plugging the printer in would get it recognized by the kernel, but not CUPS or s-c-p. You had to do "Add a printer" and have CUPS or s-c-prun some kind of detection logic to find the device. Now the printer creation is launched out of the dbus recognition that the device has become available.
OK thanks for the info This is the way I'm gonna test this in the next days. I have a hardware based M4B1 system that now on which my HP All-in-One printer works just fine. I see that CUPS ( server and client ) software appears to be installed. So this system should be static and working. On my bigger system I can generate test M4B1, M3 and M2 systems in Vbox at will. These are basic systems in which no printer software has been installed. So using these Virtual Vbox test systems I'll try various ways to get them to talk to the hardware based M4B1 system on the LAN. I think we can remain in priority "normal" on this for now. Thanks for the help.
still valid ?
(In reply to Manuel Hiebel from comment #21) > still valid ? Yes, I will take some time this week to rerun this test. It does take some time to run as you have to start with real hardware and a blank drive. Set up of ( USB ) printer is just not intuitive. CUPS set up is even more complex.
well is looks like summary doesn't match cuurent status then, I didn't see any other cups bug report
Things have settled down a bit and that should free up some time for me to go through this test process again. Approach it as a new user to Mageia and simply connecting their USB printer to their newly installed Mageia 4 computer. The result of that is that nothing happens. You then have to put on your geek cap and start the process to get, #1, the local M4 install to recognize and use the printer attached to it. And then, #2 and much more complex, how to get other M3/M4 computers installed on the local LAN to see that new printer and use it. The process is not intuitive at all. Maybe a new BUG would be the right thing to do.
I'm gonna start a new bug on this one after the testing I've done.
Changing this to resolved old and opening a new BUG
Status: NEW => RESOLVEDResolution: (none) => OLD