HPLIP

bluetooth printing with dapper and hp460

Asked by nsa1001

I wish to print via bluetooth with an hp460, using ubuntu dapper.
I have successfully connected to the printer via hcitool cc "device number".
I have added the printer as a CUPS printer, using the network address bluetooth://"device number"

The interface, however, adds ipp:// to this, giving a URI of ipp://bluetooth://"device number", which is clearly nonsense.
There is no way to remove the "ipp://" before the bluetooth address: the interface just adds it again.
Thus, I get the status error: "Ready: Unable to lookup host 'bluetooth' - Unknown host"
This is known bug identified at http://ubuntuforums.org/archive/index.php/t-454720.html

The suggested workaround is to go through http://localhost:631/admin and to add the printer there. However, at the end of the process, it requests a username and password, and does not recognise my login and password. So that doesn't work either.

Is there any other way to get Ubuntu Dapper to get the right URI for the printer?
Many thanks!

Question information

Language:
English Edit question
Status:
Solved
For:
HPLIP Edit question
Assignee:
No assignee Edit question
Solved by:
Aaron Albright
Solved:
Last query:
Last reply:
Revision history for this message
Best Aaron Albright (albrigha-deactivatedaccount) said : 		#1

The problem you are encountering is unrelated to HPLIP and HPLIP does not support this configuration.

However to work around the cups login problem edit the /etc/cups/cupsd.conf file and near the end of the file comment out the authentication lines. This may have other security implications so I take no responsibility for any system problems and or anything else that may or may not happen as a result of doing this. However it will get you past the CUPS login problem.. the lines look like this:

  # All administration operations require an administrator to authenticate...
  <Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default>
    AuthType Default
    Require user @SYSTEM
    Order deny,allow
  </Limit>

  # All printer operations require a printer operator to authenticate...
  <Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After CUPS-Accept-Jobs CUPS-Reject-Jobs>
    AuthType Default
    Require user @SYSTEM
    Order deny,allow
  </Limit>

  # Only the owner or an administrator can cancel or authenticate a job...
  <Limit Cancel-Job CUPS-Authenticate-Job>
    Require user @OWNER @SYSTEM
    Order deny,allow
  </Limit>

Simply put a # in front of the lines so it looks something like this:

  # All administration operations require an administrator to authenticate...
  <Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default>
  # AuthType Default
   # Require user @SYSTEM
   # Order deny,allow
  </Limit>

  # All printer operations require a printer operator to authenticate...
  <Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After CUPS-Accept-Jobs CUPS-Reject-Jobs>
  # AuthType Default
   # Require user @SYSTEM
    #Order deny,allow
  </Limit>

  # Only the owner or an administrator can cancel or authenticate a job...
  <Limit Cancel-Job CUPS-Authenticate-Job>
   # Require user @OWNER @SYSTEM
    #Order deny,allow
  </Limit>

Then restart cups:

sudo /etc/init.d/cupsys restart

and try going to http://localhost:631/admin again.

Hope this helps.

Aaron

Revision history for this message
nsa1001 (nsa1001) said : 		#2

Thanks Aaron Albright, that solved my question.

Revision history for this message
nsa1001 (nsa1001) said : 		#3

Aaron, it worked! Many thanks.
Test page completed successfully.

If anyone else is browsing and hits this answer, NB, I went back afterwards and restored the /etc/cups/cupsd.conf file file to its former state, so no security issues to worry about.

I hope others will find this useful too.