[kontact] [Bug 362817] Kontact crash on open addressbook from the email window

2020-12-16 Thread Michael Brach
https://bugs.kde.org/show_bug.cgi?id=362817

--- Comment #28 from Michael Brach  ---
Dear Justin,
I could but now cannot replicate the bug, because I changed the system 
an do not work with kontact anymore.
Kind regards,
Michael

Am 17.12.20 um 06:39 schrieb Justin Zobel:
> https://bugs.kde.org/show_bug.cgi?id=362817
> 
> Justin Zobel  changed:
> 
> What|Removed |Added
> 
>   Resolution|--- |WAITINGFORINFO
>   Status|REPORTED|NEEDSINFO
> 
> --- Comment #27 from Justin Zobel  ---
> Thank you for the crash report.
> 
> As it has been a while since this was reported, can you please test and 
> confirm
> if this issue is still occurring or if this bug report can be marked as
> resolved.
> 
> I have set the bug status to "needsinfo" pending your response, please change
> back to "reported" or "resolved/worksforme" when you respond, thank you.
>

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 375221] Kontact crashes after deleting multiple message tags ("Nachrichten-Markierungen")

2020-12-06 Thread Michael Brach
https://bugs.kde.org/show_bug.cgi?id=375221

--- Comment #2 from Michael Brach  ---
Dear Justin,

Icannot deliver additional info. There were too many bugs and problems 
increasing over the years, thus I unfortunately had to leave kontact and 
now use thunderbird.

Kind regards,
Michael

Am 07.12.20 um 05:20 schrieb Justin Zobel:
> https://bugs.kde.org/show_bug.cgi?id=375221
> 
> Justin Zobel  changed:
> 
> What|Removed |Added
> 
>   Resolution|--- |WAITINGFORINFO
>   CC||justin.zo...@gmail.com
>   Status|REPORTED|NEEDSINFO
> 
> --- Comment #1 from Justin Zobel  ---
> Thank you for the report, Michael.
> 
> As it has been a while since this was reported, can you please test and 
> confirm
> if this issue is still occurring or if this bug report can be marked as
> resolved.
> 
> I have set the bug status to "needsinfo" pending your response, please change
> back to "reported" or "resolved/worksforme" when you respond, thank you.
>

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 416254] New: Kontact / Kmail crash while forwarding email

2020-01-14 Thread Michael Brach
https://bugs.kde.org/show_bug.cgi?id=416254

Bug ID: 416254
   Summary: Kontact / Kmail crash while forwarding email
   Product: kontact
   Version: 5.7.3
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: michael.br...@uni-muenster.de
  Target Milestone: ---

Application: kontact (5.7.3)

Qt Version: 5.9.5
Frameworks Version: 5.47.0
Operating System: Linux 4.15.0-74-generic x86_64
Distribution: Ubuntu 18.04.3 LTS

-- Information about the crash:
- What I was doing when the application crashed:

Kontact / Kmail crashes in the moment, when I pressed f for forwarding an
email.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6bf26c1b80 (LWP 22579))]

Thread 29 (Thread 0x7f6baa7fc700 (LWP 25021)):
#0  0x7f6bef0680b4 in __GI___libc_read (fd=128, buf=0x7f6baa7fb810,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27
#1  0x7f6be8dbb2d0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f6be8d760b7 in g_main_context_check () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f6be8d76570 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f6be8d766dc in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f6befbcd99b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f6befb729fa in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f6bef99123a in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f6bef99617d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f6beadf76db in start_thread (arg=0x7f6baa7fc700) at
pthread_create.c:463
#10 0x7f6bef07988f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 28 (Thread 0x7f6a8e56c700 (LWP 22651)):
#0  0x7f6bef0680b4 in __GI___libc_read (fd=91, buf=0x7f6a8e56b810,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27
#1  0x7f6be8dbb2d0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f6be8d760b7 in g_main_context_check () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f6be8d76570 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f6be8d766dc in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f6befbcd99b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f6befb729fa in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f6bef99123a in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f6bef99617d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f6beadf76db in start_thread (arg=0x7f6a8e56c700) at
pthread_create.c:463
#10 0x7f6bef07988f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 27 (Thread 0x7f6a9e937700 (LWP 22618)):
#0  0x7f6beadfd9f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x563d9c4b8860) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f6beadfd9f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x563d9c4b8810, cond=0x563d9c4b8838) at pthread_cond_wait.c:502
#2  0x7f6beadfd9f3 in __pthread_cond_wait (cond=0x563d9c4b8838,
mutex=0x563d9c4b8810) at pthread_cond_wait.c:655
#3  0x7f6bef9975ab in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f6bef98fc1b in QSemaphore::acquire(int) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f6a9f92580c in  () at
/usr/lib/x86_64-linux-gnu/qt5/plugins/texttospeech/libqttexttospeech_flite.so
#6  0x7f6bef99617d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f6beadf76db in start_thread (arg=0x7f6a9e937700) at
pthread_create.c:463
#8  0x7f6bef07988f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 26 (Thread 0x7f6aa032a700 (LWP 22616)):
#0  0x7f6bef06cbf9 in __GI___poll (fds=0x7f6a980049b0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f6be8d765c9 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f6be8d766dc in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f6befbcd99b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f6befb729fa in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f6bef99123a in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f6bef99617d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f6beadf76db in start_thread 

[kontact] [Bug 408062] New: Kontact (Kmail) crashed in the moment of email reply

2019-05-29 Thread Michael Brach
https://bugs.kde.org/show_bug.cgi?id=408062

Bug ID: 408062
   Summary: Kontact (Kmail) crashed in the moment of email reply
   Product: kontact
   Version: 5.7.3
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: michael.br...@uni-muenster.de
  Target Milestone: ---

Application: kontact (5.7.3)

Qt Version: 5.9.5
Frameworks Version: 5.44.0
Operating System: Linux 4.15.0-50-generic x86_64
Distribution: Ubuntu 18.04.2 LTS

-- Information about the crash:
- What I was doing when the application crashed:
Kmail: I wanted to reply to an email. Kmail disappeared in the moment when I
hit the shortcut.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fed76d43b80 (LWP 1669))]

Thread 31 (Thread 0x7fec18e73700 (LWP 8596)):
#0  0x7fed73706762 in __libc_disable_asynccancel () at
../sysdeps/unix/sysv/linux/x86_64/cancellation.S:96
#1  0x7fed736eac0d in __GI___poll (fds=0x7fed10002be0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#2  0x7fed6d3f55c9 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fed6d3f56dc in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fed7424b9bb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fed741f0a1a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fed7400f23a in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fed7401417d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fed6f4766db in start_thread (arg=0x7fec18e73700) at
pthread_create.c:463
#9  0x7fed736f788f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 30 (Thread 0x7fec09ed8700 (LWP 8372)):
#0  0x7fed6d43b664 in g_mutex_unlock () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fed6d3f4b18 in g_main_context_prepare () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fed6d3f54fb in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fed6d3f56dc in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fed7424b9bb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fed741f0a1a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fed7400f23a in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fed7401417d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fed6f4766db in start_thread (arg=0x7fec09ed8700) at
pthread_create.c:463
#9  0x7fed736f788f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 29 (Thread 0x7fec1af48700 (LWP 2326)):
#0  0x7fed6d43b649 in g_mutex_lock () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fed6d3f55af in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fed6d3f56dc in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fed7424b9bb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fed741f0a1a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fed7400f23a in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fed7401417d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fed6f4766db in start_thread (arg=0x7fec1af48700) at
pthread_create.c:463
#8  0x7fed736f788f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 28 (Thread 0x7fec1ba49700 (LWP 2032)):
#0  0x7fed6f47c9f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x5613e4c228dc) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7fed6f47c9f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x5613e4c22888, cond=0x5613e4c228b0) at pthread_cond_wait.c:502
#2  0x7fed6f47c9f3 in __pthread_cond_wait (cond=0x5613e4c228b0,
mutex=0x5613e4c22888) at pthread_cond_wait.c:655
#3  0x7fed6446ec95 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7fed6446f177 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7fed6446ff11 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7fed6446c5eb in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7fed6f4766db in start_thread (arg=0x7fec1ba49700) at
pthread_create.c:463
#8  0x7fed736f788f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 27 (Thread 0x7fec1c44a700 (LWP 2028)):
#0  0x7fed6f47c9f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x5613e4c228dc) at

[kontact] [Bug 375221] New: Kontact crashes after deleting multiple message tags ("Nachrichten-Markierungen")

2017-01-18 Thread Michael Brach
https://bugs.kde.org/show_bug.cgi?id=375221

Bug ID: 375221
   Summary: Kontact crashes after deleting multiple message tags
("Nachrichten-Markierungen")
   Product: kontact
   Version: 5.2.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: michael.br...@uni-muenster.de
  Target Milestone: ---

Application: kontact (5.2.3)

Qt Version: 5.6.1
Frameworks Version: 5.28.0
Operating System: Linux 4.4.0-59-generic x86_64
Distribution: Ubuntu 16.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed:

I configered Kontact - Mail - Appearance and on the last tab I deleted some
message tags (German: "Nachrichten-Markierungen"). 

After confirming changes, Kontact crashed.

BTW: The reason for deleting the tags was, that my original tags had doubled
and mutliplied themselves over time. This I deleted all but one of the
identical tags. maybe this behaviour contributed to the crash.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f65aaee6940 (LWP 2918))]

Thread 38 (Thread 0x7f64925f2700 (LWP 6958)):
#0  0x7f65bbd10ae4 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f65bbccb9b0 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f65bbccc2cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f65bbccc4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f65c309737b in QEventDispatcherGlib::processEvents
(this=0x7f654821a000, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#5  0x7f65c303fffa in QEventLoop::exec (this=this@entry=0x7f64925f1c80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f65c2e689e4 in QThread::exec (this=) at
thread/qthread.cpp:500
#7  0x7f65c2e6d808 in QThreadPrivate::start (arg=0x4b36680) at
thread/qthread_unix.cpp:341
#8  0x7f65bc4f66ba in start_thread (arg=0x7f64925f2700) at
pthread_create.c:333
#9  0x7f65c256582d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 37 (Thread 0x7f6492df3700 (LWP 6956)):
#0  0x7fff29d999a9 in ?? ()
#1  0x7fff29d99cd5 in clock_gettime ()
#2  0x7f65c2573c86 in __GI___clock_gettime (clock_id=1,
tp=tp@entry=0x7f6492df29e0) at ../sysdeps/unix/clock_gettime.c:115
#3  0x7f65c2f196c6 in qt_clock_gettime (ts=0x7f6492df29e0, clock=) at tools/qelapsedtimer_unix.cpp:105
#4  do_gettime (frac=, sec=) at
tools/qelapsedtimer_unix.cpp:156
#5  qt_gettime () at tools/qelapsedtimer_unix.cpp:165
#6  0x7f65c3094f09 in QTimerInfoList::updateCurrentTime
(this=this@entry=0x7f6544000e00) at kernel/qtimerinfo_unix.cpp:84
#7  0x7f65c3095475 in QTimerInfoList::timerWait (this=0x7f6544000e00,
tm=...) at kernel/qtimerinfo_unix.cpp:381
#8  0x7f65c309685e in timerSourcePrepareHelper (timeout=0x7f6492df2ab4,
src=) at kernel/qeventdispatcher_glib.cpp:126
#9  timerSourcePrepare (source=, timeout=0x7f6492df2ab4) at
kernel/qeventdispatcher_glib.cpp:159
#10 0x7f65bbccb92d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x7f65bbccc2cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x7f65bbccc4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x7f65c309737b in QEventDispatcherGlib::processEvents
(this=0x7f65440014e0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#14 0x7f65c303fffa in QEventLoop::exec (this=this@entry=0x7f6492df2c80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#15 0x7f65c2e689e4 in QThread::exec (this=) at
thread/qthread.cpp:500
#16 0x7f65c2e6d808 in QThreadPrivate::start (arg=0x6a85d90) at
thread/qthread_unix.cpp:341
#17 0x7f65bc4f66ba in start_thread (arg=0x7f6492df3700) at
pthread_create.c:333
#18 0x7f65c256582d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 36 (Thread 0x7f64a0a95700 (LWP 6954)):
#0  0x7f65bbd10ac9 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f65bbccbddc in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f65bbccc340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f65bbccc4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f65c309737b in QEventDispatcherGlib::processEvents
(this=0x7f653c009480, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#5  0x7f65c303fffa in QEventLoop::exec (this=this@entry=0x7f64a0a94c80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f65c2e689e4 in QThread::exec (this=) at
thread/qthread.cpp:500
#7  0x7f65c2e6d808 in 

[kontact] [Bug 373729] New: Kontact crash while editing a new email and selecting email address

2016-12-16 Thread Michael Brach
https://bugs.kde.org/show_bug.cgi?id=373729

Bug ID: 373729
   Summary: Kontact crash while editing a new email and selecting
email address
   Product: kontact
   Version: 5.1.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: michael.br...@uni-muenster.de
  Target Milestone: ---

Application: kontact (5.1.3)

Qt Version: 5.5.1
Frameworks Version: 5.23.0
Operating System: Linux 4.4.0-53-generic x86_64
Distribution: Ubuntu 16.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed:
1. new email edit window is open
2. klick on select email adress icon, in order to show addressbook list.
3. Kontact crashes while or after selecting an email address from the
addressbook

- Unusual behavior I noticed:
heavy CPU load due to baloo re-indexing

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f2f01566940 (LWP 2857))]

Thread 23 (Thread 0x7f2e33ffc700 (LWP 16297)):
#0  0x7f2f14030433 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f2f140328cb in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f2f140332cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f2f140334ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f2f1b3657eb in QEventDispatcherGlib::processEvents
(this=0x7f2e20010be0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f2f1b30cb4a in QEventLoop::exec (this=this@entry=0x7f2e33ffbc80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f2f1b129834 in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7f2f1b12e7be in QThreadPrivate::start (arg=0x3ac31d0) at
thread/qthread_unix.cpp:331
#8  0x7f2f1485d6ba in start_thread (arg=0x7f2e33ffc700) at
pthread_create.c:333
#9  0x7f2f1a82e82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 22 (Thread 0x7f2e315ea700 (LWP 16296)):
#0  0x7f2f1a822b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f2f1403339c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f2f140334ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f2f1b3657eb in QEventDispatcherGlib::processEvents
(this=0x7f2e080010f0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f2f1b30cb4a in QEventLoop::exec (this=this@entry=0x7f2e315e9c80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f2f1b129834 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7f2f1b12e7be in QThreadPrivate::start (arg=0x5f8cd40) at
thread/qthread_unix.cpp:331
#7  0x7f2f1485d6ba in start_thread (arg=0x7f2e315ea700) at
pthread_create.c:333
#8  0x7f2f1a82e82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 21 (Thread 0x7f2e5d1e1700 (LWP 5562)):
#0  0x7f2f140332b4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f2f140334ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f2f1b3657eb in QEventDispatcherGlib::processEvents
(this=0x7f2e4c003800, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#3  0x7f2f1b30cb4a in QEventLoop::exec (this=this@entry=0x7f2e5d1e0c80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#4  0x7f2f1b129834 in QThread::exec (this=) at
thread/qthread.cpp:503
#5  0x7f2f1b12e7be in QThreadPrivate::start (arg=0x5ef1100) at
thread/qthread_unix.cpp:331
#6  0x7f2f1485d6ba in start_thread (arg=0x7f2e5d1e1700) at
pthread_create.c:333
#7  0x7f2f1a82e82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 20 (Thread 0x7f2e6b7fe700 (LWP 5540)):
#0  0x7f2f14077ae4 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f2f14032f3a in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f2f14033400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f2f140334ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f2f1b3657eb in QEventDispatcherGlib::processEvents
(this=0x7f2e58003be0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f2f1b30cb4a in QEventLoop::exec (this=this@entry=0x7f2e6b7fdc80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f2f1b129834 in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7f2f1b12e7be in QThreadPrivate::start (arg=0x24d5cf0) at
thread/qthread_unix.cpp:331
#8  0x7f2f1485d6ba in start_thread (arg=0x7f2e6b7fe700) at
pthread_create.c:333
#9  0x7f2f1a82e82d in clone () at

[kontact] [Bug 357299] New: kmail crashes during some curious activity done simultaneously in all folders above the one I moved a message into

2015-12-29 Thread Michael Brach via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357299

Bug ID: 357299
   Summary: kmail crashes during some curious activity done
simultaneously in all folders above the one I moved a
message into
   Product: kontact
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: michael.br...@uni-muenster.de

Application: kontact (4.14.3)
KDE Platform Version: 4.14.13
Qt Version: 4.8.6
Operating System: Linux 3.13.0-74-generic x86_64
Distribution: Ubuntu 14.04.3 LTS

-- Information about the crash:
- What I was doing when the application crashed:

1. On the left I have my folders view, say there are 20 folders. In the middle
I have my message list, on the right a certain message text is shown.
2. Using the mouse, I grab this message from the list and move it into the one
folder, say it is the 9th counted from the top. 
3. When I would release the mouse button above the 9th folder, something would
happen in all folders from the 1st to the 9th, indicated by an icon with a a
rotating arrow, which is shown instead of the normal folder icon.

After 5-15 seconds, 
a) the activity is over, I can work normally
b) kmail would crash

I cannot say when point 3 will happen, It seems to be in the beginning of daily
work. However, it is not each time (each day and it may happen more than one
time per day. For instance, if (3) happens, and case (a) happens,  I would move
another message into folder 12, then the same (3) would happen again.  I think
that  it would not, when I move a message to say folder 4 (a folder above
folder 9). But I'm not sure at the moment.

I tried to differentiate the issue and move messages by using the context menu.
I never experienced the problem this way. Maybe it is a problem with the mouse?
HOwever, only in kmail I have unexpected behaviour.

MAybe s.o. can give me a int where to watch, or what to triy out.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8e9be70800 (LWP 4748))]

Thread 5 (Thread 0x7f8e7ae7f700 (LWP 4749)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f8e96c1c81d in WTF::TCMalloc_PageHeap::scavengerThread() () from
/usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7f8e96c1c859 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) ()
from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7f8e9333d182 in start_thread (arg=0x7f8e7ae7f700) at
pthread_create.c:312
#4  0x7f8e993f047d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 4 (Thread 0x7f8e3a57c700 (LWP 4750)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f8e9695d20d in JSC::BlockAllocator::blockFreeingThreadMain() () from
/usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7f8e96c4bfd6 in WTF::wtfThreadEntryPoint(void*) () from
/usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7f8e9333d182 in start_thread (arg=0x7f8e3a57c700) at
pthread_create.c:312
#4  0x7f8e993f047d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7f8e2ad84700 (LWP 4756)):
#0  0x7f8e99b69b50 in testAndSetOrdered (newValue=0, expectedValue=1,
this=0x1a3de90) at
../../include/QtCore/../../src/corelib/arch/qatomic_x86_64.h:145
#1  testAndSetRelease (newValue=0, expectedValue=1, this=0x1a3de90) at
../../include/QtCore/../../src/corelib/arch/qatomic_x86_64.h:272
#2  unlockInline (this=0x1a3de48) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:171
#3  unlock (this=) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:121
#4  ~QMutexLocker (this=, __in_chrg=) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:115
#5  canWaitLocked (this=0x1a3de00) at
../../include/QtCore/private/../../../src/corelib/thread/qthread_p.h:229
#6  postEventSourcePrepare (s=0x7f8e24001350, timeout=0x7f8e2ad83c24) at
kernel/qeventdispatcher_glib.cpp:270
#7  0x7f8e92e5d68d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f8e92e5df03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f8e92e5e0ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7f8e99b697be in QEventDispatcherGlib::processEvents
(this=0x7f8e240008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#11 0x7f8e99b3b0af in QEventLoop::processEvents
(this=this@entry=0x7f8e2ad83de0, flags=...) at kernel/qeventloop.cpp:149
#12 0x7f8e99b3b3a5 in QEventLoop::exec (this=this@entry=0x7f8e2ad83de0,
flags=...) at kernel/qeventloop.cpp:204
#13 

[kontact] [Bug 320430] New: Kontact crashes after switch to Akregator and viewing a news tab

2013-05-29 Thread Michael Brach
https://bugs.kde.org/show_bug.cgi?id=320430

Bug ID: 320430
   Summary: Kontact crashes after switch to Akregator and viewing
a news tab
Classification: Unclassified
   Product: kontact
   Version: 4.10.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: michael.br...@wwu.de

Application: kontact (4.10.3)
KDE Platform Version: 4.10.3
Qt Version: 4.8.2
Operating System: Linux 3.2.0-44-generic x86_64
Distribution: Ubuntu 12.04.2 LTS

-- Information about the crash:
- What I was doing when the application crashed:
1. Working with kontact/kmail and switching to Akregator
2. For this was the first time after starting kontact, the start window showed
up in the right part of Akregator
3. Click on the first news tab which has been pre-loaded from restoring the
last session.
4. crash

I could replicate this crash one time by doing exactly the same mouse clicks.
During a 2nd trial, I went to the 2nd news tab, and Kontact/Akregator did not
crash.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
[Current thread is 1 (Thread 0x7f970f3f27c0 (LWP 12083))]

Thread 5 (Thread 0x7f96f202e700 (LWP 12084)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x7f970bbe5dec in WTF::TCMalloc_PageHeap::scavengerThread
(this=0x7f970c5aede0) at wtf/FastMalloc.cpp:2495
#2  0x7f970bbe5f19 in WTF::TCMalloc_PageHeap::runScavengerThread
(context=optimized out) at wtf/FastMalloc.cpp:1618
#3  0x7f9706c7ee9a in start_thread (arg=0x7f96f202e700) at
pthread_create.c:308
#4  0x7f970c91accd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x in ?? ()

Thread 4 (Thread 0x7f96f171d700 (LWP 12085)):
#0  0x7f97063f55d1 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f97063ba02a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f97063ba164 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f970dd5f926 in QEventDispatcherGlib::processEvents
(this=0x7f96ec0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x7f970dd2ee62 in QEventLoop::processEvents (this=optimized out,
flags=...) at kernel/qeventloop.cpp:149
#5  0x7f970dd2f0b7 in QEventLoop::exec (this=0x7f96f171cdc0, flags=...) at
kernel/qeventloop.cpp:204
#6  0x7f970dc2e077 in QThread::exec (this=optimized out) at
thread/qthread.cpp:501
#7  0x7f970dc3109b in QThreadPrivate::start (arg=0x1ec7fb0) at
thread/qthread_unix.cpp:307
#8  0x7f9706c7ee9a in start_thread (arg=0x7f96f171d700) at
pthread_create.c:308
#9  0x7f970c91accd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#10 0x in ?? ()

Thread 3 (Thread 0x7f96a43d6700 (LWP 12088)):
#0  0x7f97063b9832 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f97063b9f5b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f97063ba164 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f970dd5f926 in QEventDispatcherGlib::processEvents
(this=0x7f969c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x7f970dd2ee62 in QEventLoop::processEvents (this=optimized out,
flags=...) at kernel/qeventloop.cpp:149
#5  0x7f970dd2f0b7 in QEventLoop::exec (this=0x7f96a43d5d90, flags=...) at
kernel/qeventloop.cpp:204
#6  0x7f970dc2e077 in QThread::exec (this=optimized out) at
thread/qthread.cpp:501
#7  0x7f970dd0eb6f in QInotifyFileSystemWatcherEngine::run (this=0x215a880)
at io/qfilesystemwatcher_inotify.cpp:248
#8  0x7f970dc3109b in QThreadPrivate::start (arg=0x215a880) at
thread/qthread_unix.cpp:307
#9  0x7f9706c7ee9a in start_thread (arg=0x7f96a43d6700) at
pthread_create.c:308
#10 0x7f970c91accd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x in ?? ()

Thread 2 (Thread 0x7f9699fb2700 (LWP 18929)):
#0  0x7f970c90d8cd in read () at ../sysdeps/unix/syscall-template.S:82
#1  0x7f97063f48cf in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f97063b9ba4 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f97063b9fd6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f97063ba164 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f970dd5f926 in QEventDispatcherGlib::processEvents
(this=0x7f96880008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0x7f970dd2ee62 in QEventLoop::processEvents (this=optimized out,
flags=...) at kernel/qeventloop.cpp:149
#7  0x7f970dd2f0b7 in QEventLoop::exec 

[kontact] [Bug 316652] New: Kontact crashed after closing a second instance

2013-03-13 Thread Michael Brach
https://bugs.kde.org/show_bug.cgi?id=316652

Bug ID: 316652
   Summary: Kontact crashed after closing a second instance
Classification: Unclassified
   Product: kontact
   Version: 4.10.1
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: michael.br...@wwu.de

Application: kontact (4.10.1)
KDE Platform Version: 4.10.1
Qt Version: 4.8.2
Operating System: Linux 3.2.0-38-generic x86_64
Distribution: Ubuntu 12.04.2 LTS

-- Information about the crash:
- What I was doing when the application crashed:
After logging into KDE, the last session was restored as usual. However, this
time two instances of Kontact were started, although there was only one in the
previous session. After closing instance 1 and picking up work with instance 2,
this instance crashed.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
[Current thread is 1 (Thread 0x7f023c8547c0 (LWP 2182))]

Thread 5 (Thread 0x7f021e5bd700 (LWP 2272)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x7f0239046dec in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7f0239046f19 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7f02340dfe9a in start_thread (arg=0x7f021e5bd700) at
pthread_create.c:308
#4  0x7f0239d7bcbd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x in ?? ()

Thread 4 (Thread 0x7f021dcac700 (LWP 2278)):
#0  0x7f02340e1f69 in __pthread_mutex_lock (mutex=0x7f0218000a60) at
pthread_mutex_lock.c:92
#1  0x7f02338565a1 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f023381a675 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f023381af5b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f023381b164 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f023b1c0926 in QEventDispatcherGlib::processEvents
(this=0x7f02180008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0x7f023b18fe62 in QEventLoop::processEvents (this=optimized out,
flags=...) at kernel/qeventloop.cpp:149
#7  0x7f023b1900b7 in QEventLoop::exec (this=0x7f021dcabdc0, flags=...) at
kernel/qeventloop.cpp:204
#8  0x7f023b08f077 in QThread::exec (this=optimized out) at
thread/qthread.cpp:501
#9  0x7f023b09209b in QThreadPrivate::start (arg=0x11e1e70) at
thread/qthread_unix.cpp:307
#10 0x7f02340dfe9a in start_thread (arg=0x7f021dcac700) at
pthread_create.c:308
#11 0x7f0239d7bcbd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#12 0x in ?? ()

Thread 3 (Thread 0x7f01cf7bc700 (LWP 2387)):
#0  0x7f0239d70303 in __GI___poll (fds=optimized out, nfds=optimized
out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x7f023381b036 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f023381b164 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f023b1c0926 in QEventDispatcherGlib::processEvents
(this=0x7f01c80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x7f023b18fe62 in QEventLoop::processEvents (this=optimized out,
flags=...) at kernel/qeventloop.cpp:149
#5  0x7f023b1900b7 in QEventLoop::exec (this=0x7f01cf7bbd90, flags=...) at
kernel/qeventloop.cpp:204
#6  0x7f023b08f077 in QThread::exec (this=optimized out) at
thread/qthread.cpp:501
#7  0x7f023b16fb6f in QInotifyFileSystemWatcherEngine::run (this=0x19b4160)
at io/qfilesystemwatcher_inotify.cpp:248
#8  0x7f023b09209b in QThreadPrivate::start (arg=0x19b4160) at
thread/qthread_unix.cpp:307
#9  0x7f02340dfe9a in start_thread (arg=0x7f01cf7bc700) at
pthread_create.c:308
#10 0x7f0239d7bcbd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x in ?? ()

Thread 2 (Thread 0x7f01bc90a700 (LWP 2939)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:215
#1  0x7f023b09250f in wait (time=3, this=0x2158690) at
thread/qwaitcondition_unix.cpp:84
#2  QWaitCondition::wait (this=optimized out, mutex=0x2158d48, time=3) at
thread/qwaitcondition_unix.cpp:158
#3  0x7f023b08568f in QThreadPoolThread::run (this=0x4bec6b0) at
concurrent/qthreadpool.cpp:141
#4  0x7f023b09209b in QThreadPrivate::start (arg=0x4bec6b0) at
thread/qthread_unix.cpp:307
#5  0x7f02340dfe9a in start_thread (arg=0x7f01bc90a700) at
pthread_create.c:308
#6  0x7f0239d7bcbd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x in ?? ()

Thread 1 (Thread 0x7f023c8547c0 (LWP 2182)):
[KCrash Handler]
#6  0x7f01d4e71078 

[Bug 304372] New: Kontact crashes after each KDE login

2012-08-01 Thread Michael Brach
https://bugs.kde.org/show_bug.cgi?id=304372

Bug ID: 304372
  Severity: crash
   Version: 4.8.4
  Priority: NOR
  Assignee: kdepim-bugs@kde.org
   Summary: Kontact crashes after each KDE login
Classification: Unclassified
OS: Linux
  Reporter: michael.br...@wwu.de
  Hardware: Ubuntu Packages
Status: UNCONFIRMED
 Component: general
   Product: kontact

Application: kontact (4.8.4)
KDE Platform Version: 4.8.4 (4.8.4)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-27-generic x86_64
Distribution: Ubuntu 12.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:
Each time after KDE login Kontact would crash (typically it hangs until I
manually kill it).
Today I (see report attached) tried to shut down Kontact before the crash but
did not succeed.

Re-Starting Kontact would still cause a second crash. My workaround is: 
1. Tolerating the first crach
2. ps aux | grep kontact
3. killing all tasks shown by (2) and wating until they shut down
4. wainting until nepomuk, virtuoso and so on have done some work
5. starting Kontact

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
[Current thread is 1 (Thread 0x7f15cdc5c7c0 (LWP 1970))]

Thread 4 (Thread 0x7f15b161a700 (LWP 1982)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x7f15ca44fdec in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7f15ca44ff19 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7f15c5913e9a in start_thread (arg=0x7f15b161a700) at
pthread_create.c:308
#4  0x7f15cb1814bd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x in ?? ()

Thread 3 (Thread 0x7f15b0d01700 (LWP 1983)):
#0  0x7f15cb175b03 in __GI___poll (fds=optimized out, nfds=optimized
out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x7f15c5447036 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f15c5447164 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f15cb8f6426 in QEventDispatcherGlib::processEvents
(this=0x7f15ac0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x7f15cb8c5c82 in QEventLoop::processEvents (this=optimized out,
flags=...) at kernel/qeventloop.cpp:149
#5  0x7f15cb8c5ed7 in QEventLoop::exec (this=0x7f15b0d00dc0, flags=...) at
kernel/qeventloop.cpp:204
#6  0x7f15cb7c4fa7 in QThread::exec (this=optimized out) at
thread/qthread.cpp:501
#7  0x7f15cb7c7fcb in QThreadPrivate::start (arg=0xd73a20) at
thread/qthread_unix.cpp:298
#8  0x7f15c5913e9a in start_thread (arg=0x7f15b0d01700) at
pthread_create.c:308
#9  0x7f15cb1814bd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#10 0x in ?? ()

Thread 2 (Thread 0x7f1556a84700 (LWP 2347)):
#0  0x7fff581648de in ?? ()
#1  0x7f15c3c7715d in __GI_clock_gettime (clock_id=optimized out,
tp=optimized out) at ../sysdeps/unix/clock_gettime.c:116
#2  0x7f15cb81ebb4 in do_gettime (frac=0x7f1556a83b58, sec=0x7f1556a83b50)
at tools/qelapsedtimer_unix.cpp:123
#3  qt_gettime () at tools/qelapsedtimer_unix.cpp:140
#4  0x7f15cb8f6b8d in QTimerInfoList::updateCurrentTime
(this=0x7f1548002660) at kernel/qeventdispatcher_unix.cpp:343
#5  0x7f15cb8f6ec3 in QTimerInfoList::timerWait (this=0x7f1548002660,
tm=...) at kernel/qeventdispatcher_unix.cpp:450
#6  0x7f15cb8f597c in timerSourcePrepareHelper (src=optimized out,
timeout=0x7f1556a83c2c) at kernel/qeventdispatcher_glib.cpp:136
#7  0x7f15cb8f5a25 in timerSourcePrepare (source=optimized out,
timeout=optimized out) at kernel/qeventdispatcher_glib.cpp:169
#8  0x7f15c5446846 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f15c5446f5b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7f15c5447164 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x7f15cb8f6426 in QEventDispatcherGlib::processEvents
(this=0x7f15480008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#12 0x7f15cb8c5c82 in QEventLoop::processEvents (this=optimized out,
flags=...) at kernel/qeventloop.cpp:149
#13 0x7f15cb8c5ed7 in QEventLoop::exec (this=0x7f1556a83d90, flags=...) at
kernel/qeventloop.cpp:204
#14 0x7f15cb7c4fa7 in QThread::exec (this=optimized out) at
thread/qthread.cpp:501
#15 0x7f15cb8a59ff in QInotifyFileSystemWatcherEngine::run (this=0x1d0ce30)
at io/qfilesystemwatcher_inotify.cpp:248
#16 0x7f15cb7c7fcb in QThreadPrivate::start (arg=0x1d0ce30) at
thread/qthread_unix.cpp:298
#17 0x7f15c5913e9a in start_thread (arg=0x7f1556a84700) at
pthread_create.c:308
#18 0x7f15cb1814bd in clone () at

[Bug 250047] kontact crashed while searching for a recipient

2010-12-01 Thread Michael Brach
https://bugs.kde.org/show_bug.cgi?id=250047





--- Comment #4 from Michael Brach michael brach wwu de  2010-12-02 00:22:22 
---
Dear Louis-Philippe. Perhaps I (the reporter) was not precise: Kmail would hang
and freeze as in your bug, therefore I had to stop Kmail. Thus both reports
could contain the same bug. Are you able to verify my workaround as laid down
in  https://bugs.kde.org/show_bug.cgi?id=248541 ?

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[Bug 250047] kontact crashed while searching for a recipient

2010-09-16 Thread Michael Brach
https://bugs.kde.org/show_bug.cgi?id=250047


Michael Brach michael.br...@wwu.de changed:

   What|Removed |Added

 CC||michael.br...@wwu.de




--- Comment #1 from Michael Brach michael brach wwu de  2010-09-16 10:21:09 
---
This bug happens all the time, if I am not cautious. This is my workaround:


1. Don't edit an email (for kontact would hang / crash while
searching/completing  email addresses -- see bug report)
2. Wait until the Akonadi list of status and error messages appears (especially
no resorce found will show up)
3. Open Akonadi server configuration (KDE menu)
4. Stop and then restart Akonadi server
5. Click on test
6. no error is in the list
7. Edit and send email as you wish to

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[Bug 250047] New: kontact crashed while searching for a recipient

2010-09-03 Thread Michael Brach
https://bugs.kde.org/show_bug.cgi?id=250047

   Summary: kontact crashed while searching for a recipient
   Product: kontact
   Version: unspecified
  Platform: Ubuntu Packages
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: michael.br...@wwu.de


Application: kontact (4.4.2)
KDE Platform Version: 4.4.2 (KDE 4.4.2)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-24-generic x86_64
Distribution: Ubuntu 10.04.1 LTS

-- Information about the crash:
After typing some letters into the To: field of the mail editor, Kontact was
searching for an email address (animated hourglass as mouse pointer). For it
did not stop, I closed Kontact, but instead of closing, it crashed.

The crash can be reproduced some of the time.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f608b86a780 (LWP 2422))]

Thread 2 (Thread 0x7f606b331710 (LWP 2497)):
#0  0x7f6081474430 in ?? () from /lib/libglib-2.0.so.0
#1  0x7f60814748fc in g_main_context_iteration () from
/lib/libglib-2.0.so.0
#2  0x7f6089d2b566 in QEventDispatcherGlib::processEvents (this=0x2172e20,
flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:414
#3  0x7f6089d00992 in QEventLoop::processEvents (this=value optimized
out, flags=) at kernel/qeventloop.cpp:149
#4  0x7f6089d00d6c in QEventLoop::exec (this=0x7f606b330d90, flags=) at
kernel/qeventloop.cpp:201
#5  0x7f6089c0ad59 in QThread::exec (this=value optimized out) at
thread/qthread.cpp:487
#6  0x7f6089ce1178 in QInotifyFileSystemWatcherEngine::run (this=0x27b6300)
at io/qfilesystemwatcher_inotify.cpp:248
#7  0x7f6089c0d775 in QThreadPrivate::start (arg=0x27b6300) at
thread/qthread_unix.cpp:248
#8  0x7f60839eb9ca in start_thread (arg=value optimized out) at
pthread_create.c:300
#9  0x7f608894c6fd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#10 0x in ?? ()

Thread 1 (Thread 0x7f608b86a780 (LWP 2422)):
[KCrash Handler]
#5  0x in ?? ()
#6  0x7f608b195598 in KPIM::AddresseeLineEdit::doCompletion
(this=0x410, ctrlT=false) at ../../libkdepim/addresseelineedit.cpp:456
#7  0x7f608b19a734 in KPIM::AddresseeLineEdit::qt_metacall (this=0x410,
_c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff475dde10)
at ./addresseelineedit.moc:97
#8  0x7f6070ed6478 in KMLineEdit::qt_metacall (this=0x410,
_c=1197333520, _id=0, _a=0x0) at ./kmlineeditspell.moc:74
#9  0x7f6070f44908 in RecipientLineEdit::qt_metacall (this=0x410,
_c=1197333520, _id=0, _a=0x0) at ./recipientseditor.moc:135
#10 0x7f6089d14e3f in QMetaObject::activate (sender=0x410, m=value
optimized out, local_signal_index=value optimized out, argv=0x0) at
kernel/qobject.cpp:3293
#11 0x7f608a7b8a25 in KLineEdit::completion (this=0x410, _t1=value
optimized out) at ./klineedit.moc:233
#12 0x7f608a7b8b6b in KLineEdit::doCompletion (this=0x410, txt=...) at
../../kdeui/widgets/klineedit.cpp:1769
#13 0x7f608a7bcbae in KLineEdit::keyPressEvent (this=0x410,
e=0x7fff475debd0) at ../../kdeui/widgets/klineedit.cpp:926
#14 0x7f608b198e25 in KPIM::AddresseeLineEdit::keyPressEvent
(this=0x410, e=0x7fff475debd0) at ../../libkdepim/addresseelineedit.cpp:233
#15 0x7f6070f460d1 in RecipientLineEdit::keyPressEvent (this=0x410,
ev=0x7fff475debd0) at ../../kmail/recipientseditor.cpp:144
#16 0x7f608911122e in QWidget::event (this=0x410, event=0x7fff475debd0)
at kernel/qwidget.cpp:8033
#17 0x7f60894c6ce3 in QLineEdit::event (this=0x410, e=0x7fff475debd0)
at widgets/qlineedit.cpp:1474
#18 0x7f608a7bddca in KLineEdit::event (this=0x410, ev=0x7fff475debd0)
at ../../kdeui/widgets/klineedit.cpp:1329
#19 0x7f60890bb22c in QApplicationPrivate::notify_helper (this=0x16552a0,
receiver=0x410, e=0x7fff475debd0) at kernel/qapplication.cpp:4300
#20 0x7f60890c2ec5 in QApplication::notify (this=value optimized out,
receiver=0x410, e=0x7fff475debd0) at kernel/qapplication.cpp:3763
#21 0x7f608a6ea526 in KApplication::notify (this=0x7fff475dfb90,
receiver=0x410, event=0x7fff475debd0) at
../../kdeui/kernel/kapplication.cpp:302
#22 0x7f6089d0206c in QCoreApplication::notifyInternal
(this=0x7fff475dfb90, receiver=0x410, event=0x7fff475debd0) at
kernel/qcoreapplication.cpp:704
#23 0x7f608916616a in QKeyMapper::sendKeyEvent (keyWidget=0x410,
grab=value optimized out, type=QEvent::KeyPress, code=82, modifiers=value
optimized out, text=..., autorepeat=false, 
count=1, nativeScanCode=27, nativeVirtualKey=114, nativeModifiers=0) at
kernel/qkeymapper_x11.cpp:1861
#24 0x7f60891686f0 in QKeyMapperPrivate::translateKeyEvent (this=0x16919e0,
keyWidget=0x410, event=value optimized out, grab=16) at
kernel/qkeymapper_x11.cpp:1831
#25 

[Bug 249834] New: Kontact crashed while reading mail

2010-09-02 Thread Michael Brach
https://bugs.kde.org/show_bug.cgi?id=249834

   Summary: Kontact crashed while reading mail
   Product: kontact
   Version: 4.4.2
  Platform: Ubuntu Packages
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: michael.br...@wwu.de


Application: kontact (4.4.2)
KDE Platform Version: 4.4.2 (KDE 4.4.2)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-24-generic x86_64
Distribution: Ubuntu 10.04.1 LTS

-- Information about the crash:
While reading mail, kontact crashed suddenly. The last thing I did before was
opening link in an email message. The crash came several seconds late, so I
don't wether this may have caused it.

I would like to mention that there are aslo several problems with akonadi, but
I did not research yet.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f3c51f15780 (LWP 1842))]

Thread 2 (Thread 0x7f3c319d6710 (LWP 2319)):
#0  0x7f3c4efeaf83 in *__GI___poll (fds=value optimized out, nfds=value
optimized out, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x7f3c47b1f4a9 in ?? () from /lib/libglib-2.0.so.0
#2  0x7f3c47b1f8fc in g_main_context_iteration () from
/lib/libglib-2.0.so.0
#3  0x7f3c503d6566 in QEventDispatcherGlib::processEvents (this=0xfcbd90,
flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:414
#4  0x7f3c503ab992 in QEventLoop::processEvents (this=value optimized
out, flags=) at kernel/qeventloop.cpp:149
#5  0x7f3c503abd6c in QEventLoop::exec (this=0x7f3c319d5d90, flags=) at
kernel/qeventloop.cpp:201
#6  0x7f3c502b5d59 in QThread::exec (this=value optimized out) at
thread/qthread.cpp:487
#7  0x7f3c5038c178 in QInotifyFileSystemWatcherEngine::run (this=0x2257980)
at io/qfilesystemwatcher_inotify.cpp:248
#8  0x7f3c502b8775 in QThreadPrivate::start (arg=0x2257980) at
thread/qthread_unix.cpp:248
#9  0x7f3c4a0969ca in start_thread (arg=value optimized out) at
pthread_create.c:300
#10 0x7f3c4eff76fd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x in ?? ()

Thread 1 (Thread 0x7f3c51f15780 (LWP 1842)):
[KCrash Handler]
#5  0x02fa6b90 in ?? ()
#6  0x7f3c5183da92 in KPIM::AddresseeLineEdit::loadContacts
(this=0x2993af0) at ../../libkdepim/addresseelineedit.cpp:580
#7  0x7f3c3758250b in KMLineEdit::loadContacts (this=0x2993af0) at
../../kmail/kmlineeditspell.cpp:195
#8  0x7f3c518404dc in KPIM::AddresseeLineEdit::doCompletion
(this=0x2993af0, ctrlT=false) at ../../libkdepim/addresseelineedit.cpp:422
#9  0x7f3c51845734 in KPIM::AddresseeLineEdit::qt_metacall (this=0x2993af0,
_c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff676bf0c0)
at ./addresseelineedit.moc:97
#10 0x7f3c37582478 in KMLineEdit::qt_metacall (this=0x2993af0, _c=63270792,
_id=60, _a=0x0) at ./kmlineeditspell.moc:74
#11 0x7f3c375f0908 in RecipientLineEdit::qt_metacall (this=0x2993af0,
_c=63270792, _id=60, _a=0x0) at ./recipientseditor.moc:135
#12 0x7f3c503bfe3f in QMetaObject::activate (sender=0x2993af0, m=value
optimized out, local_signal_index=value optimized out, argv=0x0) at
kernel/qobject.cpp:3293
#13 0x7f3c50e63a25 in KLineEdit::completion (this=0x2993af0, _t1=value
optimized out) at ./klineedit.moc:233
#14 0x7f3c50e63b6b in KLineEdit::doCompletion (this=0x2993af0, txt=...) at
../../kdeui/widgets/klineedit.cpp:1769
#15 0x7f3c50e67bae in KLineEdit::keyPressEvent (this=0x2993af0,
e=0x7fff676bfe80) at ../../kdeui/widgets/klineedit.cpp:926
#16 0x7f3c51843e25 in KPIM::AddresseeLineEdit::keyPressEvent
(this=0x2993af0, e=0x7fff676bfe80) at ../../libkdepim/addresseelineedit.cpp:233
#17 0x7f3c375f20d1 in RecipientLineEdit::keyPressEvent (this=0x2993af0,
ev=0x7fff676bfe80) at ../../kmail/recipientseditor.cpp:144
#18 0x7f3c4f7bc22e in QWidget::event (this=0x2993af0, event=0x7fff676bfe80)
at kernel/qwidget.cpp:8033
#19 0x7f3c4fb71ce3 in QLineEdit::event (this=0x2993af0, e=0x7fff676bfe80)
at widgets/qlineedit.cpp:1474
#20 0x7f3c50e68dca in KLineEdit::event (this=0x2993af0, ev=0x7fff676bfe80)
at ../../kdeui/widgets/klineedit.cpp:1329
#21 0x7f3c4f76622c in QApplicationPrivate::notify_helper (this=0xe77730,
receiver=0x2993af0, e=0x7fff676bfe80) at kernel/qapplication.cpp:4300
#22 0x7f3c4f76dec5 in QApplication::notify (this=value optimized out,
receiver=0x2993af0, e=0x7fff676bfe80) at kernel/qapplication.cpp:3763
#23 0x7f3c50d95526 in KApplication::notify (this=0x7fff676c0e40,
receiver=0x2993af0, event=0x7fff676bfe80) at
../../kdeui/kernel/kapplication.cpp:302
#24 0x7f3c503ad06c in QCoreApplication::notifyInternal
(this=0x7fff676c0e40, receiver=0x2993af0, event=0x7fff676bfe80) at
kernel/qcoreapplication.cpp:704
#25 0x7f3c4f81116a in QKeyMapper::sendKeyEvent (keyWidget=0x2993af0,
grab=value optimized