Bug#567160: [Fwd: Bug#567160: serna segfault when publishing PDF]

[Joachim Breitner]

Hi,

Am Mittwoch, den 27.01.2010, 22:55 +0100 schrieb Joachim Breitner:
> > serna segfault when publishind a PDF file.
> > 
> > Steps to reproduce:
> > - Start serna
> > - Select simple docbook example
> > - Click Publish
> > - Select PDF
> > - Click Publish
> > 
> > It should fails with:
> > GLib:ERROR:/tmp/buildd/glib2.0-2.22.4/glib/gmain.c:1963:g_main_dispatch: 
> > assertion failed: (current->dispatching_sources == &current_source_link)
> > 
> > backtrace:
> > Program received signal SIGABRT, Aborted.
> > 0x00007ffff308ff55 in raise () from /lib/libc.so.6
> > (gdb) bt
> > #0  0x00007ffff308ff55 in raise () from /lib/libc.so.6
> > #1  0x00007ffff3092d90 in abort () from /lib/libc.so.6
> > #2  0x00007ffff255ce9c in g_assertion_message () from /lib/libglib-2.0.so.0
> > #3  0x00007ffff255d410 in g_assertion_message_expr () from 
> > /lib/libglib-2.0.so.0
> > #4  0x00007ffff2538947 in g_main_context_dispatch () from 
> > /lib/libglib-2.0.so.0
> > #5  0x00007ffff253c2c8 in ?? () from /lib/libglib-2.0.so.0
> > #6  0x00007ffff253c3f0 in g_main_context_iteration () from 
> > /lib/libglib-2.0.so.0
> > #7  0x00007ffff6f0639c in 
> > QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) 
> > () from /usr/lib/libQtCore.so.4
> > #8  0x00007ffff7442f1f in ?? () from /usr/lib/libQtGui.so.4
> > #9  0x00007ffff6edc562 in 
> > QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from 
> > /usr/lib/libQtCore.so.4
> > #10 0x00007ffff6edc934 in 
> > QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from 
> > /usr/lib/libQtCore.so.4
> > #11 0x00007ffff6edeba4 in QCoreApplication::exec() () from 
> > /usr/lib/libQtCore.so.4
> > #12 0x00000000005202b7 in ?? ()
> > #13 0x000000000076ee37 in ?? ()
> > #14 0x00007ffff307cabd in __libc_start_main () from /lib/libc.so.6
> > #15 0x0000000000445179 in ?? ()
> > #16 0x00007fffffffec18 in ?? ()
> > #17 0x000000000000001c in ?? ()
> > #18 0x0000000000000001 in ?? ()
> > #19 0x00007fffffffee37 in ?? ()
> > #20 0x0000000000000000 in ?? ()

as can be seen in the detailed output of the publish window, serna looks
for a java binary in /usr/lib/serna/jre/bin/java, fails to find that and
crashes.

@upstream developers: such an error should obviously be handled more
gracefully. I hope you can reproduce it by removing the java binary from
the expected path.

I’m now trying to convince serna on Debian to use /usr/bin/java.

Greetings,
Joachim
-- 
Joachim "nomeata" Breitner
Debian Developer
  nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C
  JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata

signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil