Bug 191561 - crash open chm file
Summary: crash open chm file
Status: RESOLVED NOT A BUG
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: 0.8
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-04 06:59 UTC by Kitsonkit
Modified: 2012-08-08 21:25 UTC (History)
1 user (show)

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

Attachments
crash on this file (531.79 KB, application/x-chm)
2009-05-04 07:02 UTC, Kitsonkit 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Kitsonkit 2009-05-04 06:59:27 UTC 
Version:           0.8 (using KDE 4.2.2)
OS:                Linux
Installed from:    Debian testing/unstable Packages

Application: Okular (okular), signal SIGABRT

Thread 1 (Thread 0xb6065920 (LWP 17635)):
#0  0xb7f59424 in __kernel_vsyscall ()
#1  0xb695c350 in nanosleep () from /lib/i686/cmov/libc.so.6
#2  0xb695c18e in sleep () from /lib/i686/cmov/libc.so.6
#3  0xb7b2f048 in ?? () from /usr/lib/libkdeui.so.5
#4  0x00000000 in ?? ()
Comment 1 Kitsonkit 2009-05-04 07:02:13 UTC 
Created attachment 33337 [details]
crash on this file

Crash on this file
Comment 2 Pino Toscano 2009-05-04 11:50:27 UTC 
Hi,

unfortunately, the backtrace is not helpful. You can get a better one by
a) disabling the "background generation" in the Settings -> Performance section
b) following the instructions in: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Thanks!
Comment 3 Pino Toscano 2009-05-25 16:47:16 UTC 
Hi Kitsonskit,

do you still have the problem with a more recent version of Okular?
Comment 4 Pino Toscano 2009-07-28 13:10:25 UTC 
No news since some time; if you have any, just tell.
Comment 5 Albert Astals Cid 2012-08-08 21:25:01 UTC 
User doesn't care, closing as invalid. Luis if you can still reproduce this error and are able to provide the requested information please add it to the bug and reopen it.