Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 329507 - =app-office/abiword-2.6.8 crashes when printing
Summary: =app-office/abiword-2.6.8 crashes when printing
Status: RESOLVED DUPLICATE of bug 256954
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-22 22:31 UTC by Richard Carter
Modified: 2010-07-23 20:45 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Carter 2010-07-22 22:31:43 UTC
Abiword crashes with File->Print or File->Print Preview.

This has apparently been fixed for other versions under 272097 but I still have a problem with 2.6.8 the current highest stable version. Maybe 256954 (2.6.5) could be closed too.
Comment 1 Richard Carter 2010-07-23 15:00:59 UTC
(In reply to comment #0)
> Abiword crashes with File->Print or File->Print Preview.
> 
> This has apparently been fixed for other versions under 272097 but I still have
> a problem with 2.6.8 the current highest stable version. Maybe 256954 (2.6.5)
> could be closed too.
> 

Having re-read the details of 272097 and 256954 more carefully I think perhaps whatever it was that was fixed under 272097 was not this problem, in which case this is simply (yet another) duplicate of 256954 which should remain open.

If this is the case can anything be done to escalate 256954? This was first raised in August last year (almost twelve months ago) and pushed across to the folks at Abiword a couple of weeks later. Since then no-one seems to have been able to agree if it is an Abiword issue or a Gentoo issue. Considering that Abiword is such an important package and the bug makes it practically useless it is a POOR SHOW!   

 
Comment 2 Richard Carter 2010-07-23 20:45:49 UTC

*** This bug has been marked as a duplicate of bug 256954 ***