date:20170212

[kmail2] [Bug 376420] New: kmail crash while starting

2017-02-12 Thread bugzilla_noreply

https://bugs.kde.org/show_bug.cgi?id=376420

Bug ID: 376420
   Summary: kmail crash while starting
   Product: kmail2
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: th...@gmx.de
  Target Milestone: ---

Application: kmail (5.4.2)

Qt Version: 5.7.1
Frameworks Version: 5.30.0
Operating System: Linux 4.4.0-62-generic x86_64
Distribution: KDE neon User Edition 5.9

-- Information about the crash:
Maybe I've performed an update, I can't remember, but after reboot kmail
doesn't start anymore.
BTW, "akonadiconsole" crashes too.

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0742b03a00 (LWP 4792))]

Thread 5 (Thread 0x7f0732dee700 (LWP 4800)):
#0  0x7f0771de0b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f076684738c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f076684749c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f077291675b in QEventDispatcherGlib::processEvents
(this=0x7f07280008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f07728c10ba in QEventLoop::exec (this=this@entry=0x7f0732dedbc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f07726f0f64 in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7f07726f5b48 in QThreadPrivate::start (arg=0xe0a820) at
thread/qthread_unix.cpp:368
#7  0x7f07685a06ba in start_thread (arg=0x7f0732dee700) at
pthread_create.c:333
#8  0x7f0771dec82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f07335ef700 (LWP 4797)):
#0  0x7f077291499a in QTimerInfoList::timerWait (this=0x7f0724002ed0,
tm=...) at kernel/qtimerinfo_unix.cpp:413
#1  0x7f0772915d0e in timerSourcePrepareHelper (timeout=0x7f07335ee9f4,
src=) at kernel/qeventdispatcher_glib.cpp:132
#2  timerSourcePrepare (source=, timeout=0x7f07335ee9f4) at
kernel/qeventdispatcher_glib.cpp:165
#3  0x7f076684691d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f07668472bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f076684749c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f077291675b in QEventDispatcherGlib::processEvents
(this=0x7f07240008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#7  0x7f07728c10ba in QEventLoop::exec (this=this@entry=0x7f07335eebc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#8  0x7f07726f0f64 in QThread::exec (this=) at
thread/qthread.cpp:507
#9  0x7f07726f5b48 in QThreadPrivate::start (arg=0xdd0fc0) at
thread/qthread_unix.cpp:368
#10 0x7f07685a06ba in start_thread (arg=0x7f07335ef700) at
pthread_create.c:333
#11 0x7f0771dec82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f07388bd700 (LWP 4796)):
#0  0x7ffd026eacaf in clock_gettime ()
#1  0x7f0771dfac86 in __GI___clock_gettime (clock_id=clock_id@entry=1,
tp=tp@entry=0x7f07388bc990) at ../sysdeps/unix/clock_gettime.c:115
#2  0x7f077279b241 in qt_clock_gettime (ts=0x7f07388bc990, clock=) at tools/qelapsedtimer_unix.cpp:109
#3  do_gettime (frac=, sec=) at
tools/qelapsedtimer_unix.cpp:164
#4  qt_gettime () at tools/qelapsedtimer_unix.cpp:173
#5  0x7f07729143d9 in QTimerInfoList::updateCurrentTime
(this=0x7f072c002cd0) at kernel/qtimerinfo_unix.cpp:91
#6  0x7f07729160b6 in timerSourceCheckHelper (src=) at
kernel/qeventdispatcher_glib.cpp:146
#7  timerSourceCheck (source=) at
kernel/qeventdispatcher_glib.cpp:173
#8  0x7f0766846dc1 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f0766847330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7f076684749c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x7f077291675b in QEventDispatcherGlib::processEvents
(this=0x7f072c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#12 0x7f07728c10ba in QEventLoop::exec (this=this@entry=0x7f07388bcbc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#13 0x7f07726f0f64 in QThread::exec (this=) at
thread/qthread.cpp:507
#14 0x7f07726f5b48 in QThreadPrivate::start (arg=0xe26b70) at
thread/qthread_unix.cpp:368
#15 0x7f07685a06ba in start_thread (arg=0x7f07388bd700) at
pthread_create.c:333
#16 0x7f0771dec82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f07390be700 (LWP 4795)):
#0  0x7ffd026eacaf in clock_gettime ()
#1  0x7f0771dfac86 in __GI___clock_gettime (clock_id=clock_id@entry=1,
tp=tp@entry=0x7f07390bd8f0) at

[kmail2] [Bug 376404] New: KMail crashed after closing the program

2017-02-12 Thread Roberto

https://bugs.kde.org/show_bug.cgi?id=376404

Bug ID: 376404
   Summary: KMail crashed after closing the program
   Product: kmail2
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: rtuchsche...@web.de
  Target Milestone: ---

Application: kmail (5.4.2)

Qt Version: 5.8.0
Frameworks Version: 5.30.0
Operating System: Linux 4.9.9-1-MANJARO x86_64
Distribution: "Manjaro Linux"

-- Information about the crash:
Several times I close KMail, the program crashed. This bug happend after the
upgrade to KDE Plasma 5.9.1.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f4716e47900 (LWP 1392))]

Thread 8 (Thread 0x7f45b66fb700 (LWP 1598)):
#0  0x7f4703d1d10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f46fe8c7563 in  () at /usr/lib/libQt5WebKit.so.5
#2  0x7f46febff781 in  () at /usr/lib/libQt5WebKit.so.5
#3  0x7f4703d17454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f4713d0a7df in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7f45b6efc700 (LWP 1597)):
#0  0x7f4703d1d10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f46fe8c6411 in  () at /usr/lib/libQt5WebKit.so.5
#2  0x7f46febff781 in  () at /usr/lib/libQt5WebKit.so.5
#3  0x7f4703d17454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f4713d0a7df in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7f45f7e1d700 (LWP 1596)):
#0  0x7f4703d1d10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f46febce60b in  () at /usr/lib/libQt5WebKit.so.5
#2  0x7f46febce649 in  () at /usr/lib/libQt5WebKit.so.5
#3  0x7f4703d17454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f4713d0a7df in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f4678fb4700 (LWP 1595)):
#0  0x7f4703d1d10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f46f24b2234 in  () at /usr/lib/libQt5Script.so.5
#2  0x7f46f24b2279 in  () at /usr/lib/libQt5Script.so.5
#3  0x7f4703d17454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f4713d0a7df in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f46bb7fe700 (LWP 1437)):
#0  0x7f4703d1d10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f4707d03285 in  () at /usr/lib/libQt5WebEngineCore.so.5
#2  0x7f4707d03344 in  () at /usr/lib/libQt5WebEngineCore.so.5
#3  0x7f4707ce0453 in  () at /usr/lib/libQt5WebEngineCore.so.5
#4  0x7f4707cf65c4 in  () at /usr/lib/libQt5WebEngineCore.so.5
#5  0x7f4707d0eae5 in  () at /usr/lib/libQt5WebEngineCore.so.5
#6  0x7f4707d0ee04 in  () at /usr/lib/libQt5WebEngineCore.so.5
#7  0x7f4707d0b342 in  () at /usr/lib/libQt5WebEngineCore.so.5
#8  0x7f4703d17454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f4713d0a7df in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f46d897a700 (LWP 1395)):
#0  0x7f4702013db9 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0
#1  0x7f4701fce680 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f4701fce89c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f471483c06b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f47147e589a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f4714607a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f4712c37125 in  () at /usr/lib/libQt5DBus.so.5
#7  0x7f471460c6d8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f4703d17454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f4713d0a7df in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f46e1d5b700 (LWP 1394)):
#0  0x7f4713d0148d in poll () at /usr/lib/libc.so.6
#1  0x7f47013d28e0 in  () at /usr/lib/libxcb.so.1
#2  0x7f47013d4679 in xcb_wait_for_event () at /usr/lib/libxcb.so.1
#3  0x7f46e3c49239 in  () at /usr/lib/libQt5XcbQpa.so.5
#4  0x7f471460c6d8 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f4703d17454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f4713d0a7df in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7f4716e47900 (LWP 1392)):
[KCrash Handler]
#6  0x7f46da6eacf8 in  () at /usr/lib/xorg/modules/dri//fglrx_dri.so
#7  0x7f46da7a07bc in  () at /usr/lib/xorg/modules/dri//fglrx_dri.so
#8  0x7f46da6ec58b in  () at /usr/lib/xorg/modules/dri//fglrx_dri.so
#9  0x7f46da76d752 in  () at /usr/lib/xorg/modules/dri//fglrx_dri.so
#10 0x7f46da76d990 in  () at /usr/lib/xorg/modules/dri//fglrx_dri.so
#11 0x7f46d9a3b403 in  () at

[kmail2] [Bug 376381] Ability to skip spell-check

2017-02-12 Thread Vishnu

https://bugs.kde.org/show_bug.cgi?id=376381

--- Comment #2 from Vishnu  ---
After clicking 'send' at the composer.

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

[kmail2] [Bug 376398] New: Crash on shutting down kmail

2017-02-12 Thread Con Kolivas

https://bugs.kde.org/show_bug.cgi?id=376398

Bug ID: 376398
   Summary: Crash on shutting down kmail
   Product: kmail2
   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: k...@kolivas.org
  Target Milestone: ---

Application: kmail (5.2.3)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.9.0-ck1+ x86_64
Distribution: Ubuntu 16.10

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

Kmail was misbehaving on my imap server - pressing the del key was not deleting
the email which has happened before. The solution last time was to simply
restart kmail. However this time on closing kmail it crashed.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f11ed685940 (LWP 4235))]

Thread 27 (Thread 0x7f1177ffd700 (LWP 27660)):
#0  0x7f120c56b0bd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f1202d479d6 in g_main_context_poll (priority=,
n_fds=1, fds=0x7f11b8002e20, timeout=, context=0x7f11b8000990)
at ././glib/gmain.c:4228
#2  0x7f1202d479d6 in g_main_context_iterate
(context=context@entry=0x7f11b8000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3924
#3  0x7f1202d47aec in g_main_context_iteration (context=0x7f11b8000990,
may_block=may_block@entry=1) at ././glib/gmain.c:3990
#4  0x7f120d0b04ab in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f11b80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#5  0x7f120d0580fa in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f1177ffcc80, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x7f120ce7dd43 in QThread::exec() (this=) at
thread/qthread.cpp:500
#7  0x7f120ce82c68 in QThreadPrivate::start(void*) (arg=0x5559592ab490) at
thread/qthread_unix.cpp:341
#8  0x7f120326b6ca in start_thread (arg=0x7f1177ffd700) at
pthread_create.c:333
#9  0x7f120c5770af in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 26 (Thread 0x7f11c5a05700 (LWP 27658)):
#0  0x7f120c56b0bd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f1202d479d6 in g_main_context_poll (priority=,
n_fds=1, fds=0x7f1170003270, timeout=, context=0x7f11700040a0)
at ././glib/gmain.c:4228
#2  0x7f1202d479d6 in g_main_context_iterate
(context=context@entry=0x7f11700040a0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3924
#3  0x7f1202d47aec in g_main_context_iteration (context=0x7f11700040a0,
may_block=may_block@entry=1) at ././glib/gmain.c:3990
#4  0x7f120d0b04ab in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f1170003650, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#5  0x7f120d0580fa in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f11c5a04c80, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x7f120ce7dd43 in QThread::exec() (this=) at
thread/qthread.cpp:500
#7  0x7f120ce82c68 in QThreadPrivate::start(void*) (arg=0x5559597498d0) at
thread/qthread_unix.cpp:341
#8  0x7f120326b6ca in start_thread (arg=0x7f11c5a05700) at
pthread_create.c:333
#9  0x7f120c5770af in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 25 (Thread 0x7f11777fc700 (LWP 27656)):
#0  0x7f1202d449cf in g_source_iter_next (iter=iter@entry=0x7f11777fbac0,
source=source@entry=0x7f11777fbab8) at ././glib/gmain.c:987
#1  0x7f1202d46e7b in g_main_context_prepare
(context=context@entry=0x7f1168003ea0, priority=priority@entry=0x7f11777fbb40)
at ././glib/gmain.c:3479
#2  0x7f1202d478fb in g_main_context_iterate
(context=context@entry=0x7f1168003ea0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3909
#3  0x7f1202d47aec in g_main_context_iteration (context=0x7f1168003ea0,
may_block=may_block@entry=1) at ././glib/gmain.c:3990
#4  0x7f120d0b04ab in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f1168003450, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#5  0x7f120d0580fa in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f11777fbc80, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x7f120ce7dd43 in QThread::exec() (this=) at
thread/qthread.cpp:500
#7  0x7f120ce82c68 in QThreadPrivate::start(void*) (arg=0x555958e89d70) at
thread/qthread_unix.cpp:341
#8  0x7f120326b6ca in start_thread (arg=0x7f11777fc700) at
pthread_create.c:333
#9  0x7f120c5770af in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 24 (Thread 0x7f1176ffb700 (LWP 27654)):
#0  0x7f1202d46e98 in g_main_context_prepare
(context=context@entry=0x7f116c002700,

[kmail2] [Bug 376396] Kmail crashes when starting it

2017-02-12 Thread Stefano Carlesso

https://bugs.kde.org/show_bug.cgi?id=376396

--- Comment #1 from Stefano Carlesso  ---
Created attachment 104000
  --> https://bugs.kde.org/attachment.cgi?id=104000=edit
New crash information added by DrKonqi

kmail (5.4.2) using Qt 5.7.1

- What I was doing when the application crashed:
Starting Kmail both from the Plasma Application Menu and from the terminal
result in the application closing unexpectedly.
When Launching from the terminal, I get this message
```
$ kmail 
org.kde.pim.kidentitymanagement: IdentityManager: There was no default
identity. Marking first one as default.   
Could not find QtWebEngineProcess   
*** KMail got signal 6 (Exiting)
*** Dead letters dumped.
KCrash: crashing... crashRecursionCounter = 2   
KCrash: Application Name = kmail path = /usr/bin pid = 5983 
KCrash: Arguments: /usr/bin/kmail   
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from
kdeinit   
sock_file=/run/user/1001/kdeinit5__0
[1] + Stopped (signal)   kmail   
```
- Custom settings of the application:
I created a new user to test Kmail. Default settings. I haven't setup any mail
account yet.

-- Backtrace (Reduced):
#6  0x7f8ccd08e428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7f8ccd09002a in __GI_abort () at abort.c:89
#8  0x7f8ccda4f811 in QMessageLogger::fatal(char const*, ...) const
(context=..., message=) at global/qlogging.cpp:1682
#9  0x7f8ccda4f811 in QMessageLogger::fatal(char const*, ...) const
(this=this@entry=0x7ffdd880ef60, msg=msg@entry=0x7f8cbb8d60ad "Could not find
%s") at global/qlogging.cpp:793
#10 0x7f8cb8171ea6 in WebEngineLibraryInfo::getPath(int) () at
/workspace/build/src/core/web_engine_library_info.cpp:149

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

[kmail2] [Bug 376396] Kmail crashes when starting it

2017-02-12 Thread Stefano Carlesso

https://bugs.kde.org/show_bug.cgi?id=376396

Stefano Carlesso  changed:

   What|Removed |Added

 CC||stefano.carle...@yahoo.it

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

[kmail2] [Bug 376396] New: Kmail crashes when starting it

2017-02-12 Thread Stefano Carlesso

https://bugs.kde.org/show_bug.cgi?id=376396

Bug ID: 376396
   Summary: Kmail crashes when starting it
   Product: kmail2
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: stefano.carle...@yahoo.it
  Target Milestone: ---

Application: kmail (5.4.2)

Qt Version: 5.7.1
Frameworks Version: 5.30.0
Operating System: Linux 4.4.0-62-generic x86_64
Distribution: KDE neon LTS User Edition 5.8

-- Information about the crash:
- What I was doing when the application crashed:
Every time I start Kmail fom both the Plasma Application Menu and the terminal,
it crashes. 
When starting from terminal, I get this message.
```
ste@pegasus (~): kmail
Pass a valid window to KWallet::Wallet::openWallet().
org.kde.pim.kidentitymanagement: IdentityManager: There was no default
identity. Marking first one as default.
Could not find QtWebEngineProcess
*** KMail got signal 6 (Exiting)
*** Dead letters dumped.
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kmail path = /usr/bin pid = 4885
KCrash: Arguments: /usr/bin/kmail 
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from
kdeinit
sock_file=/run/user/1000/kdeinit5__0

[1]+  Stopped kmail
```

- Custom settings of the application:
I've setup two accounts: Yahoo Mail and GMX.com both using the IMAP protocol.

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0f4ab0ea00 (LWP 4741))]

Thread 6 (Thread 0x7f0f2700 (LWP 4750)):
#0  0x7f0f6ee82929 in g_main_context_prepare
(context=context@entry=0x7f0f28000990, priority=priority@entry=0x7f0f2fffea80)
at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3453
#1  0x7f0f6ee832bb in g_main_context_iterate
(context=context@entry=0x7f0f28000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3820
#2  0x7f0f6ee8349c in g_main_context_iteration (context=0x7f0f28000990,
may_block=may_block@entry=1) at
/build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3901
#3  0x7f0f7af5475b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f0f280008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f0f7aeff0ba in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f0f2fffebc0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:212
#5  0x7f0f7ad2ef64 in QThread::exec() (this=) at
thread/qthread.cpp:507
#6  0x7f0f7ad33b48 in QThreadPrivate::start(void*) (arg=0x1aa7370) at
thread/qthread_unix.cpp:368
#7  0x7f0f70bdc6ba in start_thread (arg=0x7f0f2700) at
pthread_create.c:333
#8  0x7f0f7a42a82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f0f3ce4c700 (LWP 4748)):
#0  0x7f0f6ee82da0 in g_main_context_check
(context=context@entry=0x7f0f34000990, max_priority=2147483647,
fds=fds@entry=0x7f0f34003020, n_fds=n_fds@entry=1) at
/build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3673
#1  0x7f0f6ee83330 in g_main_context_iterate
(context=context@entry=0x7f0f34000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3837
#2  0x7f0f6ee8349c in g_main_context_iteration (context=0x7f0f34000990,
may_block=may_block@entry=1) at
/build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3901
#3  0x7f0f7af5475b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f0f340008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f0f7aeff0ba in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f0f3ce4bbc0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:212
#5  0x7f0f7ad2ef64 in QThread::exec() (this=) at
thread/qthread.cpp:507
#6  0x7f0f7ad33b48 in QThreadPrivate::start(void*) (arg=0x1a95910) at
thread/qthread_unix.cpp:368
#7  0x7f0f70bdc6ba in start_thread (arg=0x7f0f3ce4c700) at
pthread_create.c:333
#8  0x7f0f7a42a82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f0f3d6c6700 (LWP 4747)):
#0  0x7f0f7a41eb5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f0f6ee8338c in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7f0f30002e70, timeout=, context=0x7f0f3990) at
/build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:4135
#2  0x7f0f6ee8338c in g_main_context_iterate
(context=context@entry=0x7f0f3990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3835
#3  0x7f0f6ee8349c in g_main_context_iteration (context=0x7f0f3990,
may_block=may_block@entry=1) at
/build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3901
#4

[kmail2] [Bug 376393] Regression kMail 5.4.1/2: Invitations are not displayed as such any more

2017-02-12 Thread Gunter Ohrner

https://bugs.kde.org/show_bug.cgi?id=376393

--- Comment #2 from Gunter Ohrner  ---
Created attachment 103998
  --> https://bugs.kde.org/attachment.cgi?id=103998=edit
Outlook-2010-generated invitation displayed in kMail. There's also no way to
accept this invitation.

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

[kmail2] [Bug 376393] Regression kMail 5.4.1/2: Invitations are not displayed as such any more

2017-02-12 Thread Gunter Ohrner

https://bugs.kde.org/show_bug.cgi?id=376393

--- Comment #1 from Gunter Ohrner  ---
Created attachment 103997
  --> https://bugs.kde.org/attachment.cgi?id=103997=edit
kOrganizer-generated Calendar Invitation displayed in kMail. There is no way to
accept the invitation.

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

[kmail2] [Bug 376393] New: Regression kMail 5.4.1/2: Invitations are not displayed as such any more

2017-02-12 Thread Gunter Ohrner

https://bugs.kde.org/show_bug.cgi?id=376393

Bug ID: 376393
   Summary: Regression kMail 5.4.1/2: Invitations are not
displayed as such any more
   Product: kmail2
   Version: Git (master)
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: UI
  Assignee: kdepim-bugs@kde.org
  Reporter: kdeb...@customcdrom.de
  Target Milestone: ---

Since about kMail 5.4.2 or 5.4.1, iCal invitations sent by other calendar
applications are displayed as raw inline text or attachments only.

kMail 5.4.0 and earlier displayed an invitation info message with clickable
links to accept or decline the inviation, or whatever. This is gone now.

This is a major regression, as due to kOrganizer bug #352214 it's even not
possible to import the invitation manually in a way which is actually usable...

Or maybe this is caused by a KDE Neon packaging problem?


ii  akonadi-backend-mysql  
4:16.12.2-0neon+16.04+build23all  MySQL storage
backend for Akonadi
ii  akonadi-contacts-data  
4:16.12.2-0neon+16.04+build15all 
akonadi-contact data files
ii  akonadi-mime-data  
4:16.12.2-0neon+16.04+build14all  akonadi-mime
- data files
ii  akonadi-server 
4:16.12.2-0neon+16.04+build23amd64Akonadi PIM
storage service
ii  akonadiconsole 
4:16.12.2-0neon+16.04+build5 amd64management
and debugging console for akonadi
ii  kmail  
4:16.12.2-0neon+16.04+build9 amd64full featured
graphical email client
ii  korganizer 
4:16.12.2-0neon+16.04+build8 amd64calendar and
personal organizer
ii  libakonadi-kde4
4:4.14.10-1ubuntu2   amd64library for
using the Akonadi PIM data server
ii  libakonadi-kmime4  
4:4.14.10-1ubuntu2   amd64Akonadi MIME
handling library
ii  libakonadiprotocolinternals11.13.0-8ubuntu2
 amd64libraries for the Akonadi PIM
storage service
ii  libkf5akonadiagentbase5:amd64  
4:16.12.2-0neon+16.04+build23amd64Akonadi agent
base library
ii  libkf5akonadicalendar5:amd64   
4:16.12.2-0neon+16.04+build20amd64library
providing calendar helpers for Akonadi items
ii  libkf5akonadicontact5:amd64
4:16.12.2-0neon+16.04+build15amd64Akonadi
contacts access library 
ii  libkf5akonadicore5:amd64   
4:16.12.2-0neon+16.04+build23amd64Akonadi core
library 
ii  libkf5akonadimime5:amd64   
4:16.12.2-0neon+16.04+build14amd64Akonadi MIME
handling library
ii  libkf5akonadinotes5:amd64  
4:16.12.2-0neon+16.04+build14amd64Akonadi notes
access library  
ii  libkf5akonadiprivate5:amd64
4:16.12.2-0neon+16.04+build23amd64libraries for
the Akonadi PIM storage service 
ii  libkf5akonadisearch-bin
4:16.12.2-0neon+16.04+build21amd64Akonadi
search library - runtime binaries   
ii  libkf5akonadisearch-data   
4:16.12.2-0neon+16.04+build21all  Akonadi
search library - data files 
ii  libkf5akonadisearch-plugins:amd64  
4:16.12.2-0neon+16.04+build21amd64Akonadi
search library - runtime plugins
ii  libkf5akonadisearchcore5:amd64 
4:16.12.2-0neon+16.04+build21

[kmail2] [Bug 376388] Regression kMail 5.4.2: "Shift-Delete" hotkey does not work as expected any more, while "Strg-A" does not work as advertised in the Edit menu

2017-02-12 Thread Gunter Ohrner

https://bugs.kde.org/show_bug.cgi?id=376388

Gunter Ohrner  changed:

   What|Removed |Added

Summary|Regression kMail 5.4.2: |Regression kMail 5.4.2:
   |"Current" message does not  |"Shift-Delete" hotkey does
   |have keyboard focus in  |not work as expected any
   |message list after message  |more, while "Strg-A" does
   |navigation  |not work as advertised in
   ||the Edit menu

--- Comment #1 from Gunter Ohrner  ---
Mh, the problem behaves slightly different than I first thought:

The focus gets removed from the message list after just clicking the message
for the first time. The focus is then transfered to the message content pane.

Hotkeys for message navigation still work as expected.

Yet at least two hotkeys I tested stopped working now:

* Shift-Delete: It only works if the message has the focus in the message list.
  If the message content pane is focused, this hotkey does nothing.

  Curiously, pressing just "Delete" (move to trash) works in both cases.

  Maybe the Shift-Delete hotkey just needs to be activated if the message
  content pane, in addition to the message list?

  Then I'd be happy, as far as I can tell at the moment. ;)

* Another hotkey which does not work any longer as advertised is Ctrl-A.

  In the Edit menu, it explicitly states that it will select all messages in
  the message list.

  What it now actually does is selecting the message's text.

  Actually, for my usage behaviour this is an improvement, as I already pressed
  Ctrl-A in the past several times, implicitly expecting the message text to be
  selected, and always was slightly surprised all messages in the list got
  selected instead.

  Maybe you should assign a new hotkey to "Select all messages in list" and
  leave Ctrl-A to mean "select everything in the currently focused window area"
  as it is now?

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

[kmail2] [Bug 376388] New: Regression kMail 5.4.2: "Current" message does not have keyboard focus in message list after message navigation

2017-02-12 Thread Gunter Ohrner

https://bugs.kde.org/show_bug.cgi?id=376388

Bug ID: 376388
   Summary: Regression kMail 5.4.2: "Current" message does not
have keyboard focus in message list after message
navigation
   Product: kmail2
   Version: Git (master)
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: message list
  Assignee: kdepim-bugs@kde.org
  Reporter: kdeb...@customcdrom.de
  Target Milestone: ---

My use case for removing unwanted mail in folder was to jump to other mails
using the "->" button or "+"/"n" keys and pressing Shift-Delete to remove them
for good if I do not want to keep them.

This still worked fine since ages until kMail 5.4.1 but not any more with
5.4.2:

After navigating to another message using "+", "n" or by clicking a folder, the
next message is highlighted in the message list but does not get keyboard focus
- any additional hotkey pressed at this point does not work on this message.

You have to explicitly click the message again with the mouse to make
Shift-Delete work, after which the keyboard focus gets lost again, so I even
cannot delete subsequent mails using the keyboard IF I explicitly clicked into
the message list.

This is pretty annoying as if I want to delete 10 mails in a folder one after
another and have a quick glance at their contents before doing so, this
previously just required pressing "Shift-Delete" ten times and looking at the
message content pane in between. Since the last update, it requires 10
additional changes between keyboard and mouse and ten additional mouse
clicks... :-(

KMail Version 5.4.2
KDE Frameworks 5.30.0
Qt 5.7.1 (kompiliert gegen 5.7.0)
Das xcb Fenstersystem

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

[Akonadi] [Bug 376385] New: Restarting Akonadi while it fails to deliver content to frontend makes it crash

2017-02-12 Thread Dennis Schridde

https://bugs.kde.org/show_bug.cgi?id=376385

Bug ID: 376385
   Summary: Restarting Akonadi while it fails to deliver content
to frontend makes it crash
   Product: Akonadi
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: server
  Assignee: kdepim-bugs@kde.org
  Reporter: devuran...@gmx.net
  Target Milestone: ---

Application: akonadiserver (5.4.2)

Qt Version: 5.7.1
Frameworks Version: 5.30.0
Operating System: Linux 4.9.9-gentoo x86_64
Distribution: "Gentoo Base System release 2.3"

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

I ran `akonadictl restart` to resolve a server hang that might be related to
bug #338658.

- Unusual behavior I noticed:

Using KMail, I noticed that KMail seems to be unable to exchange information
with Akonadi. At first, messages did not get marked as read. When I switched to
other folders, the rotating "loading" icon appeared for them in the folder
tree, but their content never appeared and the icon never stopped spinning.
Also, "Check Mail" did not sync with the IMAP server of this account. The sync
progress bar for other accounts appears, but for this particular account it
does not. Syncing only this particular account (from the "Check Mail" sub menu)
has no effect at all.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Akonadi Server (akonadiserver), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f4babed3f00 (LWP 5018))]

Thread 18 (Thread 0x7f4b77904700 (LWP 16418)):
#0  0x7f4ba9c0a2c8 in pthread_cond_timedwait () from /lib64/libpthread.so.0
#1  0x7f4bab28ac28 in QWaitConditionPrivate::wait_relative (time=3,
this=0x7f4b940284c0) at thread/qwaitcondition_unix.cpp:133
#2  QWaitConditionPrivate::wait (time=3, this=0x7f4b940284c0) at
thread/qwaitcondition_unix.cpp:141
#3  QWaitCondition::wait (this=this@entry=0x7f4b94027dc0,
mutex=mutex@entry=0x7f4b940035a0, time=3) at
thread/qwaitcondition_unix.cpp:215
#4  0x7f4bab2877f2 in QThreadPoolThread::run (this=0x7f4b94027db0) at
thread/qthreadpool.cpp:133
#5  0x7f4bab28a60b in QThreadPrivate::start (arg=0x7f4b94027db0) at
thread/qthread_unix.cpp:368
#6  0x7f4ba9c0434c in start_thread () from /lib64/libpthread.so.0
#7  0x7f4baa92339f in clone () from /lib64/libc.so.6

Thread 17 (Thread 0x7f4b3b7fe700 (LWP 16417)):
#0  0x7f4ba9c0a2c8 in pthread_cond_timedwait () from /lib64/libpthread.so.0
#1  0x7f4bab28ac28 in QWaitConditionPrivate::wait_relative (time=3,
this=0x7f4b9401cdd0) at thread/qwaitcondition_unix.cpp:133
#2  QWaitConditionPrivate::wait (time=3, this=0x7f4b9401cdd0) at
thread/qwaitcondition_unix.cpp:141
#3  QWaitCondition::wait (this=this@entry=0x7f4b9401cc10,
mutex=mutex@entry=0x7f4b940035a0, time=3) at
thread/qwaitcondition_unix.cpp:215
#4  0x7f4bab2877f2 in QThreadPoolThread::run (this=0x7f4b9401cc00) at
thread/qthreadpool.cpp:133
#5  0x7f4bab28a60b in QThreadPrivate::start (arg=0x7f4b9401cc00) at
thread/qthread_unix.cpp:368
#6  0x7f4ba9c0434c in start_thread () from /lib64/libpthread.so.0
#7  0x7f4baa92339f in clone () from /lib64/libc.so.6

Thread 16 (Thread 0x7f4b750ff700 (LWP 16416)):
#0  0x7f4ba9c0a2c8 in pthread_cond_timedwait () from /lib64/libpthread.so.0
#1  0x7f4bab28ac28 in QWaitConditionPrivate::wait_relative (time=3,
this=0x7f4b9401d690) at thread/qwaitcondition_unix.cpp:133
#2  QWaitConditionPrivate::wait (time=3, this=0x7f4b9401d690) at
thread/qwaitcondition_unix.cpp:141
#3  QWaitCondition::wait (this=this@entry=0x7f4b9401d4d0,
mutex=mutex@entry=0x7f4b940035a0, time=3) at
thread/qwaitcondition_unix.cpp:215
#4  0x7f4bab2877f2 in QThreadPoolThread::run (this=0x7f4b9401d4c0) at
thread/qthreadpool.cpp:133
#5  0x7f4bab28a60b in QThreadPrivate::start (arg=0x7f4b9401d4c0) at
thread/qthread_unix.cpp:368
#6  0x7f4ba9c0434c in start_thread () from /lib64/libpthread.so.0
#7  0x7f4baa92339f in clone () from /lib64/libc.so.6

Thread 15 (Thread 0x7f4b3bfff700 (LWP 16415)):
#0  0x7f4ba9c0a2c8 in pthread_cond_timedwait () from /lib64/libpthread.so.0
#1  0x7f4bab28ac28 in QWaitConditionPrivate::wait_relative (time=3,
this=0x7f4b9401d210) at thread/qwaitcondition_unix.cpp:133
#2  QWaitConditionPrivate::wait (time=3, this=0x7f4b9401d210) at
thread/qwaitcondition_unix.cpp:141
#3  QWaitCondition::wait (this=this@entry=0x7f4b9401d050,
mutex=mutex@entry=0x7f4b940035a0, time=3) at
thread/qwaitcondition_unix.cpp:215
#4  0x7f4bab2877f2 in QThreadPoolThread::run (this=0x7f4b9401d040) at
thread/qthreadpool.cpp:133
#5  0x7f4bab28a60b in QThreadPrivate::start (arg=0x7f4b9401d040) at
thread/qthread_unix.cpp:368
#6  0x7f4ba9c0434c in

[kmail2] [Bug 376420] New: kmail crash while starting

[kmail2] [Bug 376404] New: KMail crashed after closing the program

[kmail2] [Bug 376381] Ability to skip spell-check

[kmail2] [Bug 376398] New: Crash on shutting down kmail

[kmail2] [Bug 376396] Kmail crashes when starting it

[kmail2] [Bug 376396] Kmail crashes when starting it

[kmail2] [Bug 376396] New: Kmail crashes when starting it

[kmail2] [Bug 376393] Regression kMail 5.4.1/2: Invitations are not displayed as such any more

[kmail2] [Bug 376393] Regression kMail 5.4.1/2: Invitations are not displayed as such any more

[kmail2] [Bug 376393] New: Regression kMail 5.4.1/2: Invitations are not displayed as such any more

[kmail2] [Bug 376388] Regression kMail 5.4.2: "Shift-Delete" hotkey does not work as expected any more, while "Strg-A" does not work as advertised in the Edit menu

[kmail2] [Bug 376388] New: Regression kMail 5.4.2: "Current" message does not have keyboard focus in message list after message navigation

[Akonadi] [Bug 376385] New: Restarting Akonadi while it fails to deliver content to frontend makes it crash

13 matches

Site Navigation

Mail list logo

Footer information