| Summary: | net-misc/hylafax-6.0.3: Unspecified Transmit Phase B error +(code 20) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Thomas Rausch <Thomas.Rausch> |
| Component: | Current packages | Assignee: | Steve Arnold <nerdboy> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | normal | CC: | comm-fax+disabled |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 361187 | ||
| Attachments: | emerege --info hylafax | ||
|
Description
Thomas Rausch
2011-02-22 14:29:48 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 Created attachment 263591 [details]
emerege --info hylafax
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. 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... 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. |
