Bug 94901 - dvipdfm seg faults if using hyperref package
Bug#: 94901 Product:  Gentoo Linux Version: unspecified Platform: x86
OS/Version: Linux Status: RESOLVED Severity: normal Priority: P2
Resolution: FIXED Assigned To: text-markup@gentoo.org Reported By: murray.alex@gmail.com
Component: Applications
URL:  http://lists.debian.org/debian-tetex-maint/2005/01/msg00170.html
Summary: dvipdfm seg faults if using hyperref package
Keywords:  
Status Whiteboard: 
Opened: 2005-06-03 02:23 0000
Description:   Opened: 2005-06-03 02:23 0000
When trying to convert a dvi to pdf with dvipdfm from tetex-2.0.2-r5, a
segmentation fault occurs.
I have tried this with the most recent version of tetex in portage also
(tetex-3.0-r2) which also results in the same error


Reproducible: Always
Steps to Reproduce:
1.
2.
3.




Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.3.5-20050130,
glibc-2.3.4.20041102-r1, 2.6.11-gentoo-r9 i686)
=================================================================
System uname: 2.6.11-gentoo-r9 i686 Intel(R) Pentium(R) 4 CPU 2.40GHz
Gentoo Base System version 1.4.16
Python:              dev-lang/python-2.3.5 [2.3.5 (#1, Apr 28 2005, 12:54:02)]
dev-lang/python:     2.3.5
sys-apps/sandbox:    [Not Present]
sys-devel/autoconf:  2.59-r6, 2.13
sys-devel/automake:  1.5, 1.9.5, 1.7.9-r1, 1.6.3, 1.4_p6, 1.8.5-r3
sys-devel/binutils:  2.15.92.0.2-r10
sys-devel/libtool:   1.5.16
virtual/os-headers:  2.6.8.1-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-O2 -march=pentium4 -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/share/config /usr/share/texmf/dvipdfm/config/
/usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/
/usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=pentium4 -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms strict"
GENTOO_MIRRORS="ftp://206.75.217.181/ http://mirror.datapipe.net/gentoo"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.au.gentoo.org/gentoo-portage"
USE="x86 X acpi alsa avi berkdb bitmap-fonts cddb cdr cups eds emacs emboss
encode evo fam fbcon gdbm gif gimp gnome gnutls gpm gstreamer gtk gtk2 hal imap
imlib jpeg libg++ mad mmx mp3 mpeg ncurses nls nptl offensive ogg oggvorbis
opengl pam pdflib png ppds python quicktime readline samba scanner sdl spell sse
sse2 ssl svg svga tcpd tetex tiff truetype truetype-fonts type1-fonts usb vorbis
win32codecs wmf xine xml xml2 xpm xv zlib userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS

------- Comment #1 From Martin Ehmsen (RETIRED) 2006-05-21 14:44:16 0000 -------
Created an attachment (id=87212) [details]
tetex-3.0_p1-time-zone.patch

Let me take a wild guess... you are in a not-whole-hour-time-zone? :)

The above patch should fix your problem. Can you please try it out and report
back if it works.

If you know C you are more than welcome to look at the patch and comment on
it... it took some time to figure out how the PDF standard wants time zones and
how tm_gmtoff defines time zones. I think the sign should be right in every
case.

------- Comment #2 From Alex Murray 2006-05-21 23:36:28 0000 -------
Unfortunately I am unable to verify the patch, as I am now using an amd64
install and the bug is not present... In this case I think it is because
previously I had CLOCK="local" set in /etc/conf.d/clock whereas I now use
CLOCK="UTC"

I will try to reproduce it, and will let you know how I go.

Perhaps you should forward the patch upstream?

------- Comment #3 From Martin Ehmsen (RETIRED) 2006-05-23 13:34:52 0000 -------
(In reply to comment #2)
> I will try to reproduce it, and will let you know how I go.

Doesn't matter. I have been able to reproduce it myself and (a slightly
modified) patch has been appplied to the -r3 revision.

> Perhaps you should forward the patch upstream?

dvipdfm upstream is dead (they promised Debian to fixed it in jan 2005, nothing
has happend since).
The project has been forked (or taken over) by dvipdfmx. dvipdfmx has tried to
fix it themself but apperently their fix is wrong (at least acording to the PDF
standard), so I sent my patch to them.