Summary: | Crash on opening okular | ||
---|---|---|---|
Product: | [Applications] okular | Reporter: | Andreas Neustifter <andreas.neustifter> |
Component: | general | Assignee: | Okular developers <okular-devel> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | andresbajotierra |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Andreas Neustifter
2009-12-11 15:07:40 UTC
- Does running "kbuildsycoca4 --noincremental" prior to launching Okular fixes the issue ? Thanks (In reply to comment #1) > - Does running "kbuildsycoca4 --noincremental" prior to launching Okular fixes > the issue ? Thanks No, sorry: > astifter@astifter:/tmp$ okular empirical-fortran.pdf > KCrash: Application 'okular' crashing... > sock_file=/home/astifter/.kde/socket-astifter/kdeinit4__0 > > [1]+ Stopped okular empirical-fortran.pdf > astifter@astifter:/tmp$ kbuildsycoca4 --noincremental > kbuildsycoca4 running... > [1]+ Exit 253 okular empirical-fortran.pdf > astifter@astifter:/tmp$ okular empirical-fortran.pdf > KCrash: Application 'okular' crashing... > sock_file=/home/astifter/.kde/socket-astifter/kdeinit4__0 > > [1]+ Stopped okular empirical-fortran.pdf > astifter@astifter:/tmp$ > [1]+ Exit 253 okular empirical-fortran.pdf > astifter@astifter:/tmp$ same backtrace? No asnwer from the reporter in 6 months, thus closing the bug, if you still have the problem please reopen the bug. |