Bug 105885 - kpdf keeps crashing when PDF file refreshes (pdflatex)
Summary: kpdf keeps crashing when PDF file refreshes (pdflatex)
Status: RESOLVED DUPLICATE of bug 98891
Alias: None
Product: kpdf
Classification: Applications
Component: general (show other bugs)
Version: 0.4.1
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Albert Astals Cid
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-18 13:21 UTC by Jens
Modified: 2005-05-18 15:46 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jens 2005-05-18 13:21:35 UTC
Version:           0.4.1 (using KDE 3.4.0 Level "b" , SUSE 9.3)
Compiler:          gcc version 3.3.5 20050117 (prerelease) (SUSE Linux)
OS:                Linux (i686) release 2.6.11.4-20a-default

Hello,

I'm using kpdf to preview PDF files that I create with Kile (LaTeX frontend). There are several problems:

- KPDF does not act properly when the PDF file changes, the new PDF has *fewer* pages than the old one and KPDF was previously on a page that does not exist any more. (eg. old document: 25 pages, new document: 20 page, current page: 23) It keeps displaying the old document and refuses to refresh.

- KPDF crashes quite often if images in the PDF document change locations or disappear. (backtraces appended below)


Backtraces:

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(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)
(no debugging symbols found)
[KCrash handler]
#3  0x40c504b3 in QPixmap::convertFromImage ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#4  0x40c506e7 in QPixmap::QPixmap () from /usr/lib/qt3/lib/libqt-mt.so.3
#5  0x417d146c in PDFGenerator::customEvent ()
   from /opt/kde3/lib/kde3/libkpdfpart.so
#6  0x40c3a49e in QObject::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#7  0x40bd7d5f in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#8  0x40bd9a83 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#9  0x408626b1 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#10 0x40bd8ed0 in QApplication::sendPostedEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#11 0x40bd8f54 in QApplication::sendPostedEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#12 0x40b84bc0 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#13 0x40befe51 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#14 0x40befc96 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#15 0x40bd994f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#16 0x08050987 in ?? ()
#17 0xbfffed10 in ?? ()
#18 0xbfffece0 in ?? ()
#19 0x00000001 in ?? ()
#20 0x00000000 in ?? ()
#21 0x03df6174 in ?? ()
#22 0x0804d1e6 in ?? ()
#23 0x40016ff4 in ?? () from /lib/ld-linux.so.2
#24 0x400176ac in ?? ()
#25 0x00000000 in ?? ()
#26 0xbfffed88 in ?? ()
#27 0x40007c5c in _dl_rtld_di_serinfo () from /lib/ld-linux.so.2
#28 0x41438e90 in __libc_start_main () from /lib/tls/libc.so.6
#29 0x0804f241 in ?? ()


Another crash destroyed the "stack frame" (no backtrace possible).

Is it possible to debug this somehow, to get rid of this bug?

Thanks!

Jens
Comment 1 Albert Astals Cid 2005-05-18 15:46:16 UTC

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