Bug 188985 - hp-sendfax cannot fax to network printer
hp-sendfax cannot fax to network printer
Status: CLOSED ERRATA
Product: Fedora
Classification: Fedora
Component: hplip (Show other bugs)
5
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Tim Waugh
:
Depends On: 191444
Blocks: FC6Target
  Show dependency treegraph
 
Reported: 2006-04-14 04:05 EDT by Bernard Johnson
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-05-31 19:57:02 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)
return channel id in device.cpp (1.72 KB, patch)
2006-04-17 12:52 EDT, Bernard Johnson
no flags Details | Diff
return channel id in device.cpp (1.72 KB, patch)
2006-04-17 15:15 EDT, Bernard Johnson
no flags Details | Diff

  None (edit)
Description Bernard Johnson 2006-04-14 04:05:28 EDT
Description of problem:
hp-sendfax prints errors and is unable to send a fax

Version-Release number of selected component (if applicable):
hplip-0.9.9-5.1

How reproducible:
always

Steps to Reproduce:
1. /usr/bin/hp-sendfax
2. select a recipient
3. select a file
4. click "send fax"
  
Actual results:
[bjohnson@localhost ~]$ hp-sendfax
 [ERROR]: Coverpages disabled. Reportlab not installed.

HP Linux Imaging and Printing System (ver. 0.9.9)
PC Sendfax Utility ver. 1.7

Copyright (c) 2003-6 Hewlett-Packard Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

QSettings: failed to open file '/usr/lib/qt-3.3/etc/settings/qt_plugins_3.3rc'
sendfax Using device: hpfax:/net/HP_Color_LaserJet_2840?ip=192.168.1.1
sendfax [ERROR]: Unable to open channel (Unknown internal error).
sendfax [ERROR]: Fax send error.
sendfax [ERROR]: Error, aborting.
[bjohnson@localhost ~]$


Expected results:
Fax to be sent.

Additional info:
I also tried this with selinux in permissive mode.
Comment 1 Bernard Johnson 2006-04-17 12:52:59 EDT
Created attachment 127812 [details]
return channel id in device.cpp

I'm beginning to think that this could not have ever worked for anyone. 
Attached is a patch to get past the "Unknown internal error".  It appears that
the communication protocol between device.py and device.cpp (hpiod) is broken.

Once I apply this patch, I get further - to the point that my fax is detected
in the idle state and needs to go to ready state (long debug log not attached
at this time).	Unfortunately, it then fails with this error:

sendfax [ERROR]: Could not get into active state!
sendfax [ERROR]: D/L error state=2
sendfax [ERROR]: Fax send error.
sendfax [ERROR]: Error, aborting.
Comment 2 Bernard Johnson 2006-04-17 15:15:00 EDT
Created attachment 127822 [details]
return channel id in device.cpp

fixed typo
Comment 3 Tim Waugh 2006-04-18 12:50:38 EDT
From the upstream discussion (thanks) it looks like we should hold off applying
this patch for the moment.
Comment 4 Bernard Johnson 2006-04-18 13:07:49 EDT
Definately - it seems my patch does nothing more than cover up the error.
Comment 5 Bernard Johnson 2006-04-18 22:52:29 EDT
Seems hplip is using the wrong port.  The hplip guys are on it.
http://www.mail-archive.com/hplip-devel@lists.sourceforge.net/msg00031.html
Comment 6 Bernard Johnson 2006-05-10 12:00:09 EDT
Tim,

I downloaded the just released hplip-0.9.11, built, and tested it.  The fax
capability seems to work just fine in this release.
Comment 7 Bernard Johnson 2006-05-11 19:40:12 EDT
I just tested your hplip-0.9.11-1.1 from updates-testing.  Everything in hplip
looks good, however, the port changed required to fix the bug has caused selinux
to complain.
Comment 8 Tim Waugh 2006-05-12 04:01:48 EDT
What AVC message do you see?
Comment 9 Bernard Johnson 2006-05-12 10:29:38 EDT
bugzilla #191444
Comment 10 Bernard Johnson 2006-05-31 19:57:02 EDT
Tested with hplip-0.9.11-1.2.  Working fine.

Note You need to log in before you can comment on or make changes to this bug.