Comment 6 for bug 864656


Unfortunately, everything failed to mesh this time. I set Loglevel debug. As there was no cups program nor "service" program, I rebooted, hoping that would do. Hp-check gets stuck somewhere and does not report anything. I could try to send the other logs anyway. Also, whenever HPLIP programs run, they complain there is no ReportLab. And I have ver 2.11.3a of HPLIP. I am hesitant to install a later version, as package replacement is a chancy business in my opinion, but I would do so if it would help.

=====Robert Armstrong====

From: Sanjay Kumar <email address hidden>
To: <email address hidden>
Sent: Tuesday, October 4, 2011 11:19 PM
Subject: [Bug 864656] Re: HP-SETUP does not detect Officejet_4500_G510a


Thanks for the update. However to find the root cause of the new issue,
I need some logs. Please follow following steps and send me the logs.

a)Open /etc/cups/cupsd.conf in root mode and replace

        LogLevel warn


      LogLevel debug
      hpLogLevel 15

    b) Open Terminal and run following commands:
      => su
      => /etc/init.d/cups restart
      => service cups restart
      => cd /tmp
      => rm *.out
      => rm *.bmp
      => hp-check -t > /tmp/hpcheck.log

    c) Try to print the file and then send
          => /var/log/syslog (if present),
          => /var/log/messages (if present),
          => /var/log/cups/error_log
          => /tmp/*.bmp
          => /tmp/*.out
          => /tmp/hpcheck.log


You received this bug notification because you are subscribed to the bug

  HP-SETUP does not detect Officejet_4500_G510a

Status in HP Linux Imaging and Printing:

Bug description:
  Use Slackware 13.37. Had a Deskjet 1000 which broke.  Deskjet remains
  default printer. "lpr -P Officejet... textfile" prints to Officejet.
  HPLIP (ver.3.11.3a) detects both Deskjet and "Officejet 4500 G510a-f",
  printer and FAX. hp-setup says it finds no devices. If HPLIP finds it,
  why cannot hp-setup? (And question: how get rid of Deskjet 1000 as
  default printer?)

To manage notifications about this bug go to: