Bug 102987

Summary:	hangs when regenerating pdf
Product:	[Unmaintained] kpdf	Reporter:	Oliver Heins <olli>
Component:	general	Assignee:	Albert Astals Cid <aacid>
Status:	RESOLVED DUPLICATE
Severity:	crash
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Oliver Heins 2005-04-01 11:21:34 UTC

Version:            (using KDE KDE 3.4.0)
Installed from:    Debian testing/unstable Packages
OS:                Linux

kpdf crashes reproducable when regenerating an already-opened  and reloading pdf-file. (It happens quite often that one needs two or three LaTeX-runs.)

Sometimes kpdf even crashes when simply doing another TeX-run.

Here's the backtrace:

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1215629376 (LWP 10013)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#3  0xb7b3d873 in QPixmap::convertFromImage () from /usr/lib/libqt-mt.so.3
#4  0xb7b3c467 in QPixmap::QPixmap () from /usr/lib/libqt-mt.so.3
#5  0xb767cbe1 in PDFGenerator::customEvent ()
   from /usr/lib/kde3/libkpdfpart.so
#6  0xb7b28f2c in QObject::event () from /usr/lib/libqt-mt.so.3
#7  0xb7acee1f in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#8  0xb7ace41e in QApplication::notify () from /usr/lib/libqt-mt.so.3
#9  0x427c29f5 in KApplication::notify () from /usr/lib/libkdecore.so.4
#10 0xb7acfc16 in QApplication::sendPostedEvents ()
   from /usr/lib/libqt-mt.so.3
#11 0xb7acfa96 in QApplication::sendPostedEvents ()
   from /usr/lib/libqt-mt.so.3
#12 0xb7a781cd in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#13 0xb7ae11d8 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#14 0xb7ae1088 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#15 0xb7acf071 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#16 0x0804ee5e in ?? ()
#17 0xbffff9e0 in ?? ()
#18 0xbffff9b0 in ?? ()
#19 0x00000000 in ?? ()

Comment 1 Oliver Heins 2005-04-01 11:24:47 UTC

Well, at least the used packages are not from the Debian testing/unstable-tree but from the Debian experimental-tree (to be honest, they are located not even there but made by the official debian-maintainers and expected to get into unstable).

Comment 2 Albert Astals Cid 2005-04-01 12:09:55 UTC

This is a bug duplicate but the other bug that spoke of that had a really bad summary so i've change it to yours and i'm closing your bug as duplicate

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