Bug 211453 - okular crashes at start if navegation panel not showed
Summary: okular crashes at start if navegation panel not showed
Status: RESOLVED WORKSFORME
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-22 16:44 UTC by Jonjox
Modified: 2010-01-03 14:10 UTC (History)
1 user (show)

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


Attachments
This file will crash okular (kde4-okular-4.2.2-84.18) on opensuse-11.1 64bit (64.88 KB, application/pdf)
2010-01-03 11:57 UTC, Amir M
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jonjox 2009-10-22 16:44:01 UTC
Version:            (using KDE 4.2.4)
OS:                Linux
Installed from:    Ubuntu Packages

Backtraces: This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.

How to reproduce: At start if okular's 'show navigation panel' option is not selected okular crashes with many pdf files, not with all. If at start 'show navigation panel' is selected it doesn't crash with so many files, but it still crashes with some of them.
Comment 1 Pino Toscano 2009-10-22 16:47:20 UTC
Please provide a backtrace of the crash, as explained in
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Comment 2 Amir M 2010-01-03 11:57:24 UTC
Created attachment 39511 [details]
This file will crash okular (kde4-okular-4.2.2-84.18) on opensuse-11.1 64bit
Comment 3 Amir M 2010-01-03 12:05:52 UTC
this attached pdf file (Comment #2 From  Amir M   2010-01-03 11:57:24) is not crashing the okular version (okular-4.3.1-3.3.x86_64) on opensuse-11.2 64bit
Comment 4 Albert Astals Cid 2010-01-03 14:10:50 UTC
Marking as worksforme then as you can get it working in newer versions means the bug was fixed somewhen