[kmail2] [Bug 395910] KMail segfaults upon exit

2018-12-06 Thread Øystein Olsen 
https://bugs.kde.org/show_bug.cgi?id=395910

--- Comment #5 from Øystein Olsen  ---
Based on the backtrace and given the correct bug number, I can see that this is
an unrelated bug.

Now, I do not use kontact and I do exactly the same as described in this bug.
Start kmail, then exit through the system tray icon (or Ctrl+Q). The
segmentation fault happens without ever opening an email in a subwindow. 

Two different users found a bug with an exact matching description. How were we
supposed to figure out that this was an unrelated bug and find the correct one,
which has completely different description?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 395910] KMail segfaults upon exit

2018-12-05 Thread Christoph Feck 
https://bugs.kde.org/show_bug.cgi?id=395910

Christoph Feck  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #4 from Christoph Feck  ---
Please do not add unrelated backtraces. Comment #2 and comment #3 are bug
398577.

*** This bug has been marked as a duplicate of bug 387177 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 395910] KMail segfaults upon exit

2018-12-01 Thread Dennis Schridde 
https://bugs.kde.org/show_bug.cgi?id=395910

--- Comment #3 from Dennis Schridde  ---
Created attachment 116615
  --> https://bugs.kde.org/attachment.cgi?id=116615=edit
New crash information added by DrKonqi

kmail (5.9.3) using Qt 5.11.1

- What I was doing when the application crashed:

I quit KMail (^Q) and received the crash notification immediately afterwards.

-- Backtrace (Reduced):
#7  0x7f929f2adce5 in content::RenderProcessHostImpl::ShutdownRequest () at
../../3rdparty/chromium/content/browser/renderer_host/render_process_host_impl.cc:3769
#8  0x7f929eaaf755 in content::mojom::RendererHostStubDispatch::Accept ()
at ./gen/content/common/renderer_host.mojom.cc:491
#9  0x7f92a06e02fd in mojo::InterfaceEndpointClient::HandleValidatedMessage
() at
../../3rdparty/chromium/mojo/public/cpp/bindings/lib/interface_endpoint_client.cc:419
#10 0x7f92a0718f49 in AcceptOnProxyThread () at
../../3rdparty/chromium/ipc/ipc_mojo_bootstrap.cc:789
#12 MakeItSo
const&, mojo::Message> () at ../../3rdparty/chromium/base/bind_internal.h:294

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 395910] KMail segfaults upon exit

2018-12-01 Thread Dennis Schridde 
https://bugs.kde.org/show_bug.cgi?id=395910

Dennis Schridde  changed:

   What|Removed |Added

 CC||devuran...@gmx.net

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 395910] KMail segfaults upon exit

2018-11-29 Thread Øystein Olsen 
https://bugs.kde.org/show_bug.cgi?id=395910

Øystein Olsen  changed:

   What|Removed |Added

 CC||dr.sci...@gmail.com

--- Comment #2 from Øystein Olsen  ---
I have the same issue with kmail 18.08.3. 

Qt version: 5.11.2
Framework: 5.52.0
OS: OpenSUSE Tumbleweed.

I believe this back-trace should be more useful:


Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
28return SYSCALL_CANCEL (nanosleep, requested_time, remaining);
[Current thread is 1 (Thread 0x7f53c794ba40 (LWP 3780))]

Thread 31 (Thread 0x7f529d801700 (LWP 3859)):
#0  futex_reltimed_wait_cancelable (private=0, reltime=0x7f529d8008c0,
expected=0, futex_word=0x7f529d800aa8) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  __pthread_cond_wait_common (abstime=0x7f529d800960, mutex=0x7f529d800a58,
cond=0x7f529d800a80) at pthread_cond_wait.c:533
#2  __pthread_cond_timedwait (cond=0x7f529d800a80, mutex=0x7f529d800a58,
abstime=0x7f529d800960) at pthread_cond_wait.c:667
#3  0x7f53d38b7d37 in base::ConditionVariable::TimedWait () at
./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:120
#4  0x7f53d38b9a0a in base::WaitableEvent::TimedWaitUntil () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:221
#5  0x7f53d38b9af2 in base::WaitableEvent::TimedWait () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:161
#6  0x7f53d38be8b1 in
base::internal::SchedulerWorker::Delegate::WaitForWork () at
./../../3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:171
#7  0x7f53d38bfbaf in base::internal::SchedulerWorker::Thread::ThreadMain
() at ./../../3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:42
#8  0x7f53d38ca1c1 in ThreadFunc () at
./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:75
#9  0x7f53dab27554 in start_thread (arg=) at
pthread_create.c:463
#10 0x7f53dd49cccf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 30 (Thread 0x7f529ede5700 (LWP 3857)):
#0  futex_reltimed_wait_cancelable (private=0, reltime=0x7f529ede48c0,
expected=0, futex_word=0x7f529ede4aa8) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  __pthread_cond_wait_common (abstime=0x7f529ede4960, mutex=0x7f529ede4a58,
cond=0x7f529ede4a80) at pthread_cond_wait.c:533
#2  __pthread_cond_timedwait (cond=0x7f529ede4a80, mutex=0x7f529ede4a58,
abstime=0x7f529ede4960) at pthread_cond_wait.c:667
#3  0x7f53d38b7d37 in base::ConditionVariable::TimedWait () at
./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:120
#4  0x7f53d38b9a0a in base::WaitableEvent::TimedWaitUntil () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:221
#5  0x7f53d38b9af2 in base::WaitableEvent::TimedWait () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:161
#6  0x7f53d38be8b1 in
base::internal::SchedulerWorker::Delegate::WaitForWork () at
./../../3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:171
#7  0x7f53d38bfbaf in base::internal::SchedulerWorker::Thread::ThreadMain
() at ./../../3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:42
#8  0x7f53d38ca1c1 in ThreadFunc () at
./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:75
#9  0x7f53dab27554 in start_thread (arg=) at
pthread_create.c:463
#10 0x7f53dd49cccf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 29 (Thread 0x7f529f5e6700 (LWP 3856)):
#0  futex_reltimed_wait_cancelable (private=0, reltime=0x7f529f5e58c0,
expected=0, futex_word=0x7f529f5e5aa8) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  __pthread_cond_wait_common (abstime=0x7f529f5e5960, mutex=0x7f529f5e5a58,
cond=0x7f529f5e5a80) at pthread_cond_wait.c:533
#2  __pthread_cond_timedwait (cond=0x7f529f5e5a80, mutex=0x7f529f5e5a58,
abstime=0x7f529f5e5960) at pthread_cond_wait.c:667
#3  0x7f53d38b7d37 in base::ConditionVariable::TimedWait () at
./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:120
#4  0x7f53d38b9a0a in base::WaitableEvent::TimedWaitUntil () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:221
#5  0x7f53d38b9af2 in base::WaitableEvent::TimedWait () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:161
#6  0x7f53d38be8b1 in
base::internal::SchedulerWorker::Delegate::WaitForWork () at
./../../3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:171
#7  0x7f53d38bfd91 in base::internal::SchedulerWorker::Thread::ThreadMain
() at ./../../3rdparty/chromium/base/task_scheduler/scheduler_worker.cc:68
#8  0x7f53d38ca1c1 in ThreadFunc () at
./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:75
#9  0x7f53dab27554 in start_thread (arg=) at

[kmail2] [Bug 395910] KMail segfaults upon exit

2018-10-04 Thread Christoph Feck 
https://bugs.kde.org/show_bug.cgi?id=395910

Christoph Feck  changed:

   What|Removed |Added

 CC||mat...@ant.gliwice.pl

--- Comment #1 from Christoph Feck  ---
*** Bug 398530 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.