356083 – net-misc/hylafax-6.0.3: Unspecified Transmit Phase B error +(code 20)

Bug 356083 - net-misc/hylafax-6.0.3: Unspecified Transmit Phase B error +(code 20)

Summary: net-misc/hylafax-6.0.3: Unspecified Transmit Phase B error +(code 20)

Status:	RESOLVED WONTFIX

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Steve Arnold

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:	361187
	Show dependency tree

Reported:	2011-02-22 14:29 UTC by Thomas Rausch
Modified:	2012-02-26 17:49 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
emerege --info hylafax (emerge-info-hylafax.txt,9.06 KB, text/plain) 2011-02-23 04:17 UTC, Thomas Rausch	Details
View All Add an attachment (proposed patch, testcase, etc.)

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

Description Thomas Rausch 2011-02-22 14:29:48 UTC

The above error occurs when my modem is still on. If the bug fix for that? See here: http://www.nsnet15.com/doc/sdb/en/html/jg_hylafax_usr.html

Reproducible: Always

Comment 1 Jeroen Roovers (RETIRED) gentoo-dev

2011-02-23 03:21:07 UTC

Please attach all relevant information to this bug report, including what is at that URL and your `emerge --info =net-misc/hylafax-6.0.3' output and more information about your modem.. Also, this looks like an upstream bug

Comment 2 Thomas Rausch 2011-02-23 04:17:27 UTC

Created attachment 263591 [details]
emerege --info hylafax

Comment 3 Thomas Rausch 2011-02-23 04:29:14 UTC

With the solution in the URL in #1 above, I can not (yet) again send all fax machines. Before it was (probably) mostly just for fax modems. I have to get to the end of transmission always the error: Unspecified Transmit Phase B error +(code 20)

My Modem: MODEM "ELSA, AACHEN (GERMANY)" "MicroLink 28.8TQV"/"Ver. 1.10 vom 19.09.95"

The solution to #1 but only one solution seems to be because Hylafax does not really deal with this modem class.

Comment 4 Steve Arnold archtester

2011-03-04 20:34:21 UTC

If it has to do with specific Class support or that kind of thing, then it's definitely an upstream issue (so I would recommend filing a bug there).  Otherwise, you might try configuring it using a slightly different class config, ie, instead of Class 2.1 use Class 2, etc.  That sometimes works, depending on the exact hardware...

Comment 5 Samuli Suominen (RETIRED) gentoo-dev

2012-02-26 17:49:03 UTC

Closing as WONTFIX because hylafax was removed from Portage. But adding 361187 to Blocks: -line since this bug should get fixed if introduced back to Portage.