On Wed, 17 Jun 2009 14:54:02 +0200 Patrik Fimml <pat...@fimml.at> wrote:
Thank you very much for your quick reply. The last time I reported the bug in question (about 5 weeks ago) I didn't get any response at all. > You are very welcome to fix it yourself. If that's not an option, then > please drop the reproachful tone. > > > What's the exact issue you were experiencing? The exact issue is simply nothing. When I press Ctrl-p or click the respective button, abiword simply vanishes into thin air without leaving any trace. Nearly the same happens when I choose "Save as PDF" or "Save as Postscript" - except from that then it takes a second or two for abiword to realize that it probably ought to crash now. ;) > > For me, that prints the document in question. This is not what the > documentation claims --print=- should do, but that's not related to the > crash described by the original submitter. > > I can only guess that abiword probably didn't print the document in > question for you, then. But in your console-output snippet, I do not see > anything crash-related. No abort, no segfault. What makes you think it's > a crash? When I call abiword from the shell and try to print the document interactively I find the message "Aborted" after the mysterious disappearance of abiword. Else (when called from the shell to print) the snippet I sent is everything I get. > > Please clarify this. > > In addition, please check whether you find the bug to persist in abiword > SVN. If it does, and it is a crash, then please compile with debugging > symbols and attach a backtrace. I downloaded version 2.7.4 yesterday from abisource.com. Will this be ok for you? Or how can I reach the SVN repository? (However I'm not good in CVS/ SVN, so I should prefer a tarball.) Regards Martin -- Volk ist Opium für die Religion. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
