http://bugs.kde.org/show_bug.cgi?id=183363
--- Comment #9 from Pino Toscano 2009-02-16 01:43:30 ---
Hi John,
I've seen that backtrace already, and I think that I could have fixed it;
although, if you could attach the file, I could double check that.
If the file is private, you can send it t
http://bugs.kde.org/show_bug.cgi?id=183363
--- Comment #8 from John Athanaselis 2009-02-15
23:13:41 ---
The full debug info:
Application: Okular (okular), signal SIGSEGV
[Current thread is 1 (Thread 0xb8097770 (LWP 6010))]
Thread 1 (Thread 0xb8097770 (LWP 6010)):
[KCrash Handler]
#6 QBas
http://bugs.kde.org/show_bug.cgi?id=183363
--- Comment #7 from Pino Toscano 2009-02-07 17:36:53 ---
Also, the faulty document would be something needed for reproducing the issue.
--
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because:
http://bugs.kde.org/show_bug.cgi?id=183363
Albert Astals Cid tsdgeos terra es changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
Resolut
http://bugs.kde.org/show_bug.cgi?id=183363
--- Comment #5 from Pino Toscano 2009-02-05 22:17:59 ---
This is another problem now.
Please follow
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
for getting a better backtrace.
--
Configure bugmail: h
http://bugs.kde.org/show_bug.cgi?id=183363
--- Comment #4 from John Athanaselis 2009-02-05
22:06:57 ---
(In reply to comment #2)
> In a terminal, please run:
> $ kbuildsycoca4 --noincremental
>
Problem remains
Thread 1 (Thread 0xb7fa7770 (LWP 3927)):
#0 0x00903416 in __kernel_vsyscall (
http://bugs.kde.org/show_bug.cgi?id=183363
John Athanaselis johnathana gmail com changed:
What|Removed |Added
Component|general |CHM backend
--- Comme
http://bugs.kde.org/show_bug.cgi?id=183363
Darío Andrés andresbajotierra gmail com changed:
What|Removed |Added
CC||andresbajotie...@gmail.
http://bugs.kde.org/show_bug.cgi?id=183363
Pino Toscano pino kde org changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Component|CHM back
