Bug 190239 - Okular can't open chm document
Summary: Okular can't open chm document
Status: RESOLVED DUPLICATE of bug 178539
Alias: None
Product: okular
Classification: Applications
Component: CHM backend (show other bugs)
Version: 0.7.3
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-21 12:36 UTC by Dmitry Kholodilov
Modified: 2009-04-21 13:12 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
chm document that causes okular crash (524.60 KB, application/octet-stream)
2009-04-21 12:52 UTC, Dmitry Kholodilov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dmitry Kholodilov 2009-04-21 12:36:41 UTC
Version:           0.7.3 (using KDE 3.5.10)
OS:                Linux
Installed from:    SuSE RPMs

It is single case with concrete chm file, other files okular opens properly.

Application: Okular (okular), signal SIGSEGV
[?1034h(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
(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)
(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)
(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]
#5  0x00007f2e57267958 in Okular::Page::deletePixmap(int) ()
   from /usr/lib64/libokularcore.so.1
#6  0x00007f2e5724ba27 in Okular::Document::removeObserver(Okular::DocumentObserver*) () from /usr/lib64/libokularcore.so.1
#7  0x00007f2e5752f3a6 in ?? () from /usr/lib64/kde4/okularpart.so
#8  0x00000000004084e3 in _start ()
Comment 1 Pino Toscano 2009-04-21 12:45:01 UTC
Hello,

unfortunately, the backtrace doesn't say much about the problem. You can get a better one by following the instructions on the page:
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Also, could you attach the CHM document you cannot open?

Thanks.
Comment 2 Dmitry Kholodilov 2009-04-21 12:52:53 UTC
Created attachment 32979 [details]
chm document that causes okular crash
Comment 3 Dmitry Kholodilov 2009-04-21 13:02:06 UTC
To reproduce this crashing, you need open my chm file in okular. After it okular don't crashes, but also don't opens document. Message about crash appears after closing okular.
I use qt version 4.5.0-44.1-x86_64 from http://download.opensuse.org/repositories/KDE:/Qt45/openSUSE_11.1/, but in openSUSE 11.1 default qt version is 4.4.3. May be, it causes a problem?
Comment 4 Pino Toscano 2009-04-21 13:07:19 UTC
This has been fixed in Okular 0.8.1 (KDE 4.2.1).

*** This bug has been marked as a duplicate of bug 178539 ***
Comment 5 Dmitry Kholodilov 2009-04-21 13:12:18 UTC
Thank you!