https://bugs.kde.org/show_bug.cgi?id=264168
Summary: Okular crash when opening pdf
Product: okular
Version: 0.10.5
Platform: Debian stable
OS/Version: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
https://bugs.kde.org/show_bug.cgi?id=264168
Pino Toscano changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|
https://bugs.kde.org/show_bug.cgi?id=243434
Pino Toscano changed:
What|Removed |Added
CC||achim_schae...@gmx.de
--- Comment #31 from P
https://bugs.kde.org/show_bug.cgi?id=243434
haz...@hazardous-area.org changed:
What|Removed |Added
CC||haz...@hazardous-area.org
--
Co
https://bugs.kde.org/show_bug.cgi?id=243434
--- Comment #32 from2011-01-24 19:24:14 ---
Created an attachment (id=56394)
--> (http://bugs.kde.org/attachment.cgi?id=56394)
New crash information added by DrKonqi
okular (0.11.2) on KDE Platform 4.5.5 (KDE 4.5.5) using Qt 4.7.1
- What I was
https://bugs.kde.org/show_bug.cgi?id=243434
--- Comment #33 from Albert Astals Cid 2011-01-24 20:01:33
---
#32 is that really the valgrind trace you get? It doesn't make any sense and
it's totally different from the gdb trace :-S
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?ta
https://bugs.kde.org/show_bug.cgi?id=243434
--- Comment #34 from2011-01-24 21:51:51 ---
Yes, this is what valgrind gave me, you can see from valgrind's output:
==18617== Command: okular 02_AT_Quote_SPQ.ID.OPP-08958.pdf
I was opening the same PDF as for the crash in the backtrace.
Al
https://bugs.kde.org/show_bug.cgi?id=243434
--- Comment #35 from Achim Schaefer 2011-01-24
22:20:47 ---
Hi,
as I saw this valgrind discussion, I run my one as well with valgrind.
What happens is:
after started once with valgrind, it works even without valgrind.
I got that for the pdf and t
https://bugs.kde.org/show_bug.cgi?id=243434
--- Comment #36 from Albert Astals Cid 2011-01-24 22:56:52
---
Achim valgrind log makes much more sense.
#34 I find interesting the comment you make about NX not crashing as it shows
it's maybe not Okular's fault. So can you guys try using differe