GNOME Bugzilla – Bug 150135
gpdf crashes when link is email address
Last modified: 2004-12-22 21:47:04 UTC
(1) create document using pdflatex and hyperref package (2) put some email address in it, as a hyperlink (using \url{} macro) (3) open using gpdf (4) click on email-link (5) crash Expected behaviour: "New Email" dialog from say, Evolution should open to be consistent with mailto: links in html documents. Have to figure out how to provide bt, seems only the bonobo component is crashing, not the whole app.
To get a backtrace, run /usr/lib/gpdf/gnome-pdf-viewer inside gdb (close all instances of gpdf before doing that). When it crashes, get its bt. What would help, is if you could attach the pdf to test it (or the TeX source)
Created attachment 30638 [details] Testcase source
Created attachment 30639 [details] Testcase compiled
Didn't manage to get the bt yet since /usr/local/libexec/gnome-pdf-viewer doesn't startup but silently exits. Hopefully the textcase helps.
Thanks for attaching the test files! When gnome-pdf-viewer exits immediately, another instance of it is still running. Close all gpdf windows (and maybe kill gnome-pdf-viewer), then you can try in gdb again.
Dunno if it makes a difference but naive "./configure --prefix=/usr/local && make ..." gave me the gnome-pdf-viewer binary in /usr/local/libexec instead of "lib" as you suggest. In addition to that it doesn't exit immediately but after half a minute or so after running it inside gdb. Running /usr/local/libexec/gnome-pdf-viewer outside gdb behaves the same. Maybe the reason is that because it's in /usr/local while all other stuff us in /usr it's not known to bonobo-activation?
I said /usr/lib/gpdf/gnome-pdf-viewer because that's where debian puts it. /usr/local/libexec is the default location. You have to uncomment the /usr/local/lib/bonobo/servers line in /etc/bonobo-activation/bonobo-activation-config.xml to use gnome-pdf-viewer from /usr/local. Otherwise it autoexits IIRC. Fortunately Dan Williams from Red Hat alread sent a patch to fix the problem (but he didn't see this bug report) I mark this as duplicate of the bug with the patch.
*** This bug has been marked as a duplicate of 150476 ***