[kontact] [Bug 388896] New: Kontact crashed while first-time use in Kali Linux 2.0

[shi zhengyu]

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

Bug ID: 388896
   Summary: Kontact crashed while first-time use in Kali Linux 2.0
   Product: kontact
   Version: 5.2.3
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: 2357913...@qq.com
  Target Milestone: ---

Application: kontact (5.2.3)

Qt Version: 5.9.2
Frameworks Version: 5.37.0
Operating System: Linux 4.14.0-kali1-amd64 x86_64
Distribution: Kali GNU/Linux Rolling

-- Information about the crash:
i was setting the KMail account,and when i tried to receive mail from it ,it
boom.

-- 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 0x7f581feb9900 (LWP 9725))]

Thread 38 (Thread 0x7f5750ff9700 (LWP 11298)):
#0  0x7ffd4cad4a35 in clock_gettime ()
#1  0x7f581cafcd36 in __GI___clock_gettime (clock_id=1, tp=0x7f5750ff8a10)
at ../sysdeps/unix/clock_gettime.c:115
#2  0x7f581d61ea21 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f581d61d259 in QTimerInfoList::updateCurrentTime() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f581d61d835 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f581d61ee7e in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f58133a2698 in g_main_context_prepare () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f58133a308b in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f58133a326c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f581d61f10b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f581d5c42aa in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f581d3e335a in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7f581d3e822d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7f5815199519 in start_thread (arg=0x7f5750ff9700) at
pthread_create.c:456
#14 0x7f581caefa4f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 37 (Thread 0x7f57517fa700 (LWP 11296)):
#0  0x7f581cae5a5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f58133a3159 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f58133a326c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f581d61f10b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f581d5c42aa in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f581d3e335a in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f581d3e822d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f5815199519 in start_thread (arg=0x7f57517fa700) at
pthread_create.c:456
#8  0x7f581caefa4f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 36 (Thread 0x7f5751ffb700 (LWP 11294)):
#0  0x7f581cae5a5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f58133a3159 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f58133a326c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f581d61f10b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f581d5c42aa in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f581d3e335a in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f581d3e822d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f5815199519 in start_thread (arg=0x7f5751ffb700) at
pthread_create.c:456
#8  0x7f581caefa4f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 35 (Thread 0x7f57527fc700 (LWP 11292)):
#0  0x7f58133a25e4 in g_main_context_prepare () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f58133a308b in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f58133a326c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f581d61f10b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f581d5c42aa in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f581d3e335a in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f581d3e822d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f5815199519 in start_thread (arg=0x7f57527fc700) at
pthread_create.c:456
#8  0x7f581caefa4f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 34 (Thread 0x7f575b7fe700 (LWP 11290)):
#0  0x7f581cafc6b2 in 

[kontact] [Bug 388890] New: Kontact crash on close if Akregator tab was viewed opened

[Nikolay Brookstein]

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

Bug ID: 388890
   Summary: Kontact crash on close if Akregator tab was viewed
opened
   Product: kontact
   Version: 5.7.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: nikolay.brookst...@nextnetworks.eu
  Target Milestone: ---

Application: kontact (5.7.0)

Qt Version: 5.9.2
Frameworks Version: 5.41.0
Operating System: Linux 4.14.11-300.fc27.x86_64 x86_64
Distribution (Platform): Fedora RPMs

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

1) Open Kontact
2) Open Akregator tab
3) Read some news
4) Change an active tab or dont change (same effect)
5) Click on a window close button
6) Crash

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9c6b323980 (LWP 4904))]

Thread 25 (Thread 0x7f9b0ef3a700 (LWP 4986)):
#0  0x7f9c54c16434 in g_mutex_unlock () at /lib64/libglib-2.0.so.0
#1  0x7f9c54bd03d3 in g_main_context_prepare () at /lib64/libglib-2.0.so.0
#2  0x7f9c54bd0e0b in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#3  0x7f9c54bd0fec in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#4  0x7f9c657ca35b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#5  0x7f9c657780ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#6  0x7f9c655c98ba in QThread::exec() () at /lib64/libQt5Core.so.5
#7  0x7f9c655cdb92 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f9c5973461b in start_thread () at /lib64/libpthread.so.0
#9  0x7f9c6496b91f in clone () at /lib64/libc.so.6

Thread 24 (Thread 0x7f9b14964700 (LWP 4963)):
#0  0x7f9c5973ac4b in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f9c5e0c7cc5 in
base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*)
() at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5
#2  0x7f9c5e0c81a7 in base::SequencedWorkerPool::Worker::Run() () at
/usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5
#3  0x7f9c5e0c8f41 in base::SimpleThread::ThreadMain() () at
/usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5
#4  0x7f9c5e0c560b in base::(anonymous namespace)::ThreadFunc(void*) () at
/usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5
#5  0x7f9c5973461b in start_thread () at /lib64/libpthread.so.0
#6  0x7f9c6496b91f in clone () at /lib64/libc.so.6

Thread 23 (Thread 0x7f9b1761f700 (LWP 4953)):
#0  0x7f9c6495a888 in read () at /lib64/libc.so.6
#1  0x7f9c54c150e0 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0
#2  0x7f9c54bd09e8 in g_main_context_check () at /lib64/libglib-2.0.so.0
#3  0x7f9c54bd0e80 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#4  0x7f9c54bd0fec in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#5  0x7f9c657ca35b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#6  0x7f9c657780ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#7  0x7f9c655c98ba in QThread::exec() () at /lib64/libQt5Core.so.5
#8  0x7f9c655cdb92 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#9  0x7f9c5973461b in start_thread () at /lib64/libpthread.so.0
#10 0x7f9c6496b91f in clone () at /lib64/libc.so.6

Thread 22 (Thread 0x7f9b30881700 (LWP 4937)):
#0  0x7f9c54bcde71 in g_source_iter_next () at /lib64/libglib-2.0.so.0
#1  0x7f9c54bd0811 in g_main_context_check () at /lib64/libglib-2.0.so.0
#2  0x7f9c54bd0e80 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#3  0x7f9c54bd0fec in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#4  0x7f9c657ca35b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#5  0x7f9c657780ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#6  0x7f9c655c98ba in QThread::exec() () at /lib64/libQt5Core.so.5
#7  0x7f9c655cdb92 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f9c5973461b in start_thread () at /lib64/libpthread.so.0
#9  0x7f9c6496b91f in clone () at /lib64/libc.so.6

Thread 21 (Thread 0x7f9b31f23700 (LWP 4935)):
#0  0x7f9c6495f36b in poll () at /lib64/libc.so.6
#1  0x7f9c54bd0ed9 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f9c54bd0fec in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f9c657ca35b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f9c657780ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f9c655c98ba in 

[akregator] [Bug 381929] Feeds list gets corrupted when akregator is restored on log in

[Christos Gourdoupis]

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

--- Comment #17 from Christos Gourdoupis  ---
Unfortunately, with the updated 17.12.0 sources I cannot reproduce it in the
debugger, no matter what.
On the bright side, the corruption has not occured once since the update.
We'll see.

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

[kmail2] [Bug 388784] I cannot create a new folder!! resourceld 4 !!!!! HELP

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED
 CC||pointedst...@zoho.com

--- Comment #1 from Nate Graham  ---
There isn't enough information in this bug to help KDE developers debug, and
you're reporting against a very, very old version of KMail. Please try
upgrading to a newer one. For future bugs, please follow the following
guidelines: https://bugs.kde.org/page.cgi?id=bug-writing.html

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

[Akonadi] [Bug 283682] KMail duplicates filtered messages

[Árpi]

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

Árpi  changed:

   What|Removed |Added

 CC||lukacs.ar...@gmail.com

--- Comment #199 from Árpi  ---
With upgrading to version 5.5.3 on Kmail, the duplication problem got worse in
my case.
I have a rather large (~ 1) collection of messages. It happens after
filtering, it can be "fixed" by clearing akonadi cache with akonadiconsole, but
it appears again.
Adding a filter on top of the filter list, that executes "/usr/bin/sleep 15"
did not help. I could not find out if it happens with the folders that contain
many messages, or in all of them (i think the latter).
What did change with the new version (compared to the one there was in kubuntu
14.04) is that now I get an error message when trying to access the folder with
the duplicate messages, that kmail cannot fetch the message because of multiple
candidates. Previously, i could erase one.

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

[akregator] [Bug 381929] Feeds list gets corrupted when akregator is restored on log in

[Steve]

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

Steve  changed:

   What|Removed |Added

 CC||sweseme...@hotmail.com

--- Comment #16 from Steve  ---
Just wanted to add that this also happens on Fedora 26 and 27 (with all updates
applied).

The procedure in Comment 14 also works for me, ie it reproducible destroys the
feeds every time. 

Otherwise, the feed corruption is more hit and miss, ie it doesn't happen every
time I start Akregator but often enough to be annoying.

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

[kmail2] [Bug 375445] KMail2 hangs with 100% CPU usage when trying to preview or read large emails from IMAP server

[Rodney Baker]

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

Rodney Baker  changed:

   What|Removed |Added

  Component|general |commands and actions

--- Comment #9 from Rodney Baker  ---
The silence is deafening...

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

[kmail2] [Bug 388871] New: KMail reports message send failure, but sends multiple copies of same message

[Rodney Baker]

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

Bug ID: 388871
   Summary: KMail reports message send failure, but sends multiple
copies of same message
   Product: kmail2
   Version: 5.7.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: commands and actions
  Assignee: kdepim-bugs@kde.org
  Reporter: rodney.ba...@iinet.net.au
  Target Milestone: ---

When sending a 6.2MB message with attachments, KMail2 reported "Failed to
transport message; connection to server lost." 

The email was sent to 4 recipients (1 "To:" address, 1 CC and 2 BCC). 

The message remained in the outbox folder until moved to Drafts. Despite the
claimed failure, each recipient received 6 complete copies of the same 6.2MB
email.

Verified the failure by sending the same message from the drafts folder to
myself - I received 2 copies. The same happened with other large emails >2MB
(not sure exactly what the threshold is). 

All emails were successfully and correctly sent from Thunderbird.

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

[akregator] [Bug 379755] Can not read feeds that require authentication

[Marc Branchaud]

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

--- Comment #3 from Marc Branchaud  ---
I cannot express how disappointed I am with this regression.

I had to switch to Liferea!  :(

Unfortunately, its solution is to use a regular browser's cookie store.  I have
it using Firefox's store, but occasionally Firefox's cookie management removes
the cookies from its on-disk store (I think it's caching newly-acquired cookies
in RAM), so every few days Liferea can't authenticate until I either close all
Firefox windows or until Firefox finally decides to update its on-disk cookie
store.  :( :(

Please fix this.  I miss Akregator!

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

[kmail2] [Bug 388869] New: continuing problem with duplicate and/or missing messages

[Fred Jackson]

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

Bug ID: 388869
   Summary: continuing problem with duplicate and/or missing
messages
   Product: kmail2
   Version: 5.6.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: folders
  Assignee: kdepim-bugs@kde.org
  Reporter: fredrick.o.jack...@gmail.com
  Target Milestone: ---

Created attachment 109819
  --> https://bugs.kde.org/attachment.cgi?id=109819=edit
statusbar error message

when I collect one message from my localhost and filter it into the 'logs'
folder, I'm getting a duplicate message list entry and the error "unable to
fetch item from backend (collection -1): unable to retrieve item from resource:
[LRCONFLICT] Resource akonadi_maildir_resource_0 tries to modify item 15701 ()
(in collection 22) with dirty payload, aborting STORE." when I click on one of
the two message list entries created. Also, automatic archival of messages now
generates error messages indicating archival has failed.

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

[akregator] [Bug 379755] Can not read feeds that require authentication

[Alexander Potashev]

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

Alexander Potashev  changed:

   What|Removed |Added

 CC||aspotas...@gmail.com

--- Comment #2 from Alexander Potashev  ---
Same problem here: Atlassian JIRA's RSS URL looks like this:
  https://[customer
id].atlassian.net/activity?maxResults=5_authType=basic=undefined

Thus it relies on the authentication token stored in cookies.

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

[kmail2] [Bug 388828] Forward Redirect Fails

[Frank Noack]

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

--- Comment #2 from Frank Noack  ---
I'm a bit confused. Now it works without any changes in the system and without
re-start.

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

[kmail2] [Bug 388828] Forward Redirect Fails

[Frank Noack]

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

Frank Noack  changed:

   What|Removed |Added

 CC||fgro...@onlinehome.de

--- Comment #1 from Frank Noack  ---
I can confirm this failure on Gentoo, KDE Version 17.12.1

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

[kmail2] [Bug 342567] TLSv1.2 is not used on imap/smtp/managesieve

[zless]

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

--- Comment #25 from zless  ---
Some additional info:

The problem computer (KMail only uses TLSv1 for SMTP) has ksmtp-17.12.1 which
seems introduced in 17.12.

Another computer, with 17.08, has no ksmtp package and KMail successfully uses
TLSv1.2 for SMTP.

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

[korganizer] [Bug 374803] How to change start of the week from Monday to Sunday?

[davidblunkett]

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

--- Comment #9 from davidblunkett  ---
still no solution to this?

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

[korganizer] [Bug 388851] New: View: agenda:month:timeline:etc is poorly named

[davidblunkett]

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

Bug ID: 388851
   Summary: View: agenda:month:timeline:etc is poorly named
   Product: korganizer
   Version: 5.2.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: dav1dblunk...@hotmail.com
  Target Milestone: ---

the menu item "agenda" should surely be rename "week".  If you've switched to
another view and want to view by week why on earth would you expect view:agenda
to do this for you?

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

[korganizer] [Bug 388850] New: Error whiloe trying to modify calender item [llconflict]

[davidblunkett]

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

Bug ID: 388850
   Summary: Error whiloe trying to modify calender item
[llconflict]
   Product: korganizer
   Version: 5.2.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: dav1dblunk...@hotmail.com
  Target Milestone: ---

When I add an event there is an "apply" button.  If I press the apply button
and then make changes I get this error and nothing fixes the problem unless I
cancel (losing the information) and start again.

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

[korganizer] [Bug 388849] New: korganizer has problems syncing with google calender

[davidblunkett]

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

Bug ID: 388849
   Summary: korganizer has problems syncing with google calender
   Product: korganizer
   Version: 5.2.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: dav1dblunk...@hotmail.com
  Target Milestone: ---

Events I add to korganizer don't get uploaded to google calender and korganizer
requires manually syncing from akonadiconsole to get events added on google
calender to appear in korganizer.

Essentially it is pretty well borked - this has been going on for  and it
doesn't take that many missed appointments to render korganizer history.

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