https://bugs.kde.org/show_bug.cgi?id=382635
--- Comment #14 from Christoph Feck ---
Camille, this crash is fixed in KMail 5.3.0 or newer.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=382635
--- Comment #13 from Camille Chabot ---
Thank you M. Feck
Crashing conditions still exist. As i open Kadress book at tool menu
with Kmail open it still crash
Les paquets contenant les informations de débogage pour l'application et
les bibliothèques
https://bugs.kde.org/show_bug.cgi?id=382635
Christoph Feck changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=382635
--- Comment #11 from Christoph Feck ---
*** Bug 384623 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=382635
Christoph Feck changed:
What|Removed |Added
CC||camillei...@videotron.ca
--- Comment #10 from
https://bugs.kde.org/show_bug.cgi?id=382635
Christoph Feck changed:
What|Removed |Added
Severity|normal |crash
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=382635
--- Comment #9 from Christoph Feck ---
Both backtraces look useful. If you are debugging with 'gdb', it is normal that
the application window is not closed when it crashes, because gdb immediately
stops the process. This is also the reason you can no lo
https://bugs.kde.org/show_bug.cgi?id=382635
--- Comment #8 from odysseus...@nord-com.net ---
Maybe this log is more useful - but it didn't crash too:
Breakpoint 2 at 0xb6697160
Breakpoint 3 at 0xb66971d0
Continuing.
[New Thread 0xad480b40 (LWP 4280)]
[New Thread 0xac8beb40 (LWP 4281)]
[New Thread
https://bugs.kde.org/show_bug.cgi?id=382635
--- Comment #7 from odysseus...@nord-com.net ---
I forgot to mention: there is a GUI of kaddressbook, but it doesn't react on
inputs like mouse-clicks...
Odysseus24
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=382635
--- Comment #6 from odysseus...@nord-com.net ---
Now I have a backtrace, but I don't think that it's useful. kaddressbook
doesn't crash. But it always crashes on startup when I don't debug it... So
here's the backtrace of a running kaddressbook:
(gdb) r
https://bugs.kde.org/show_bug.cgi?id=382635
--- Comment #5 from Christoph Feck ---
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=382635
--- Comment #4 from odysseus...@nord-com.net ---
Hi Laurent !
To be honstly: I don't know what exactly You mean and a backtrace of what...
How can I do this ?
Regards
Odysseus24
--
You are receiving this mail because:
You are watching all bug changes
https://bugs.kde.org/show_bug.cgi?id=382635
Laurent Montel changed:
What|Removed |Added
CC||mon...@kde.org
--- Comment #3 from Laurent Mon
https://bugs.kde.org/show_bug.cgi?id=382635
--- Comment #2 from odysseus...@nord-com.net ---
Created attachment 106816
--> https://bugs.kde.org/attachment.cgi?id=106816&action=edit
MySQL-Protokoll (InnoDB) of the akonadi-system (reprted by akonadiselftest)
--
You are receiving this mail becaus
https://bugs.kde.org/show_bug.cgi?id=382635
--- Comment #1 from odysseus...@nord-com.net ---
p.s. in "Jessie" it all worked fine...
--
You are receiving this mail because:
You are watching all bug changes.
15 matches
Mail list logo
