[kmail2] [Bug 387025] KMail crashes when launched

[Allan Sandfeld]

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

--- Comment #5 from Allan Sandfeld  ---
I downgraded to neon user instead of dev stable, so I don't know if it still
happens there.

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

[kmail2] [Bug 387025] KMail crashes when launched

[David Faure]

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

--- Comment #4 from David Faure  ---
To remove drkonqi from the equation, simply export KDE_DEBUG=1.

Either this is a miscompilation... or I did something wrong in terms of
KConfigGroup lifetime in https://phabricator.kde.org/D8783 ... but the calling
code is simply
KConfigGroup grp(KernelIf->config(), "CollectionTreeOrder");
d->entityOrderProxy->setOrderConfig(grp);
which should be fine...

Does this still happen?

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

[Akonadi] [Bug 388178] New: Agent zur E-Mail-Archivierung (akonadi_archivemail_agent), signal: Segmentation fault - ArchiveJob::~ArchiveJob() (this=0x24b1080, __in_chrg=)

[Don Curtis]

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

Bug ID: 388178
   Summary: Agent zur E-Mail-Archivierung
(akonadi_archivemail_agent), signal: Segmentation
fault - ArchiveJob::~ArchiveJob() (this=0x24b1080,
__in_chrg=)
   Product: Akonadi
   Version: 5.5.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: Archive Mail Agent
  Assignee: kdepim-bugs@kde.org
  Reporter: bugrprt21...@online.de
  Target Milestone: ---

Application: akonadi_archivemail_agent (5.5.2)

Qt Version: 5.6.2
Frameworks Version: 5.32.0
Operating System: Linux 4.4.103-36-default x86_64
Distribution: "openSUSE Leap 42.3"

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

Letting the automatic e-Mail Archive run as planned -- noticed this crash when
I returned to the machine.

-- Backtrace:
Application: Agent zur E-Mail-Archivierung (akonadi_archivemail_agent), signal:
Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3a02c52940 (LWP 32612))]

Thread 9 (Thread 0x7f39c6d42700 (LWP 336)):
#0  0x7f39fdebb555 in clock_gettime () at /lib64/libc.so.6
#1  0x7f39fe86fa46 in  () at /usr/lib64/libQt5Core.so.5
#2  0x7f39fe9d5809 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#3  0x7f39fe9d5d85 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#4  0x7f39fe9d6f7e in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f39f729895d in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#6  0x7f39f7299230 in  () at /usr/lib64/libglib-2.0.so.0
#7  0x7f39f729942c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#8  0x7f39fe9d71ab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#9  0x7f39fe984bfb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#10 0x7f39fe7bff5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#11 0x7f39fe7c4a29 in  () at /usr/lib64/libQt5Core.so.5
#12 0x7f39f816d744 in start_thread () at /lib64/libpthread.so.0
#13 0x7f39fdeaeaad in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7f39c7543700 (LWP 32742)):
#0  0x7f39fe7bd44a in QMutex::lock() () at /usr/lib64/libQt5Core.so.5
#1  0x7f39fe9d77c5 in  () at /usr/lib64/libQt5Core.so.5
#2  0x7f39f7298da1 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f39f72992a8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f39f729942c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f39fe9d71ab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f39fe984bfb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f39fe7bff5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7f39fe7c4a29 in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f39f816d744 in start_thread () at /lib64/libpthread.so.0
#10 0x7f39fdeaeaad in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f39c7d44700 (LWP 32736)):
#0  0x7f39f7298efb in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#1  0x7f39f7299388 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f39f729942c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f39fe9d71ab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f39fe984bfb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f39fe7bff5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f3a00014295 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x7f39fe7c4a29 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f39f816d744 in start_thread () at /lib64/libpthread.so.0
#9  0x7f39fdeaeaad in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f39c8c39700 (LWP 32714)):
#0  0x7f39f81720bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f39d6383b4b in  () at /usr/lib64/dri/radeonsi_dri.so
#2  0x7f39d63838c7 in  () at /usr/lib64/dri/radeonsi_dri.so
#3  0x7f39f816d744 in start_thread () at /lib64/libpthread.so.0
#4  0x7f39fdeaeaad in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f39c943a700 (LWP 32713)):
#0  0x7f39f81720bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f39d6383b4b in  () at /usr/lib64/dri/radeonsi_dri.so
#2  0x7f39d63838c7 in  () at /usr/lib64/dri/radeonsi_dri.so
#3  0x7f39f816d744 in start_thread () at /lib64/libpthread.so.0
#4  0x7f39fdeaeaad in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f39c9c3b700 (LWP 32712)):
#0  0x7f39f81720bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f39d6383b4b in  () at /usr/lib64/dri/radeonsi_dri.so
#2  0x7f39d63838c7 in  () at 

[Akonadi] [Bug 336581] accidental database loss causes Akonadi / KMail to silently break correct folder assignments

[Kai Maerzhaeuser]

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

Kai Maerzhaeuser  changed:

   What|Removed |Added

 CC||ka...@freenet.de

--- Comment #11 from Kai Maerzhaeuser  ---
A short comment on this, since Martin perfectly summarizes my frustration. A
user's opinion, I am not a developer.

Since introduction of akonadi, I experience broken database issue about 1-2
times a Year (last time some days ago) and none of the proposed solutions
anywhere in posts resolves my given issues. Because I don't have the time for
extensive investigations I have to delete ~/.local/share/akonadi which then
totally mixes up folder associations with the described impacts on filters etc.
as described above.

Email is among the most critical applications for daily use and this weakness
in architecture (as I learned from above) is a total mess.

This is not a bug, but a totally broken architecture !!!
Martin's suggestions seem already very reasonable to me, and promising.

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

[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1

[Urs Joss]

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

--- Comment #34 from Urs Joss  ---
Thanks Fabian. The patch (via archlinux ksmtp-17.12.0-2) solves the issue for
me.

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

[kmail2] [Bug 388170] Often in kmail the information bar shows a hanging message about synchronizing the trash folder of a specific IMAP account

[Freek de Kruijf]

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

--- Comment #2 from Freek de Kruijf  ---
I checked the number of messages in the Trash folder on the dovecot server. The
number there was 10 more than what was shown in kmail. So I decided to lower
the number of days messages should be kept. This lowered the number in kmail to
2304, however nothing happened on the dovecot server. I still have the original
amount 2375.

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

[kmail2] [Bug 388170] Often in kmail the information bar shows a hanging message about synchronizing the trash folder of a specific IMAP account

[Freek de Kruijf]

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

--- Comment #1 from Freek de Kruijf  ---
After the description in #1 I logged out and in again to start akonadi fresh.
Before starting kontact I did a "akonadictl fsck" and "akonadictl vacuum"; both
finished OK. However fsck reported a few duplicated messages in that trash
folder. I decided use akonadiconsole. I selected the IMAP account with the
problematic trash folder and activated Settings...->Configure Natively.
Selecting tab Advanced I noticed that the field for the Trash folder was empty.
Trying to configure the Trash folder of that account, which should have been
there, I got nothing to choose from. I canceled the configuration action.
Pressed Restart went back to Settings...->Configure Natively, and found that
field for the Trash folder contained the Trash folder of the IMAP account, as
it should have. Currently, a few minutes after the Restart, it shows Folder
Trash being synchronized (149%). A Restart at the bottom of the console does
not work. Toggling off and on does work and shows the account connected.
However the configuration again shows an empty Trash folder field. Using the
context menu I restarted the agent and it shows Ready and the field shows again
the right Trash folder.

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

[kmailtransport] [Bug 388160] ksmtp EHLO sends server hostname as domain parameter by default

[kzi]

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

--- Comment #3 from kzi  ---
Thank you, Fabian!

localhost.invalid and foo.localnet make up nice domain names, too. :)

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

[kmailtransport] [Bug 388160] ksmtp EHLO sends server hostname as domain parameter by default

[Fabian Vogt]

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

Fabian Vogt  changed:

   What|Removed |Added

 CC||fab...@ritter-vogt.de
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Fabian Vogt  ---
Fixed by https://phabricator.kde.org/D9485.

It simply does the exact same in ksmtp now as kmailtransport's smtp kio slave
used to (it worked, so why change).

The version in bugzilla does not match ksmtp as there is no ksmtp component in
bugzilla (yet).

FYI: Patch got added to KDE:Applications for openSUSE - I assume other distros
will pick it soon as well.

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

[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1

[Fabian Vogt]

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

Fabian Vogt  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/ksm
   ||tp/5199ed07428a03f1aa340da3
   ||ae99fcfa62ba2751
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED FIXED
  Latest Commit||https://commits.kde.org/ksm
   ||tp/ec2afd27c790fbde63a9c2bd
   ||d1f97a59fe04b18e
 Status|CONFIRMED   |RESOLVED

--- Comment #32 from Fabian Vogt  ---
Git commit 5199ed07428a03f1aa340da3ae99fcfa62ba2751 by Fabian Vogt.
Committed on 23/12/2017 at 12:09.
Pushed by fvogt into branch 'Applications/17.12'.

Send the correct hostname with the HELO/EHLO command

Summary:
It sent the server's hostname previously, which some reject.

Test Plan: Ran nc as smtp server, uses the right hostname for EHLO now.

Reviewers: mlaurent, dvratil

Subscribers: #kde_pim

Tags: #kde_pim

Differential Revision: https://phabricator.kde.org/D9485

M  +13   -1src/session.cpp

https://commits.kde.org/ksmtp/5199ed07428a03f1aa340da3ae99fcfa62ba2751

--- Comment #33 from Fabian Vogt  ---
Git commit ec2afd27c790fbde63a9c2bdd1f97a59fe04b18e by Fabian Vogt.
Committed on 23/12/2017 at 12:09.
Pushed by fvogt into branch 'Applications/17.12'.

Fix duplicate authentication

Summary:
The response to EHLO triggers an authentication command, but with TLS
two EHLOs are sent: For the 220 from the server and after TLS negotiation.
However, sending it twice results in an unexpected "503 already authenticated"
response which ends up getting parsed by the SendJob, causing confusion.

By leaving the EHLO-resending to the SessionPrivate, the state can be properly
tracked.
Related: bug 388068

Reviewers: mlaurent, dvratil

Subscribers: lbeltrame, cgiboudeaux

Differential Revision: https://phabricator.kde.org/D9476

M  +19   -10   src/session.cpp
M  +1-0src/session_p.h
M  +0-1src/sessionthread.cpp

https://commits.kde.org/ksmtp/ec2afd27c790fbde63a9c2bdd1f97a59fe04b18e

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

[kmail2] [Bug 388068] With the kmail version 5.7 can no longer send mails.

[Fabian Vogt]

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

Fabian Vogt  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://commits.kde.org/ksm
   ||tp/ec2afd27c790fbde63a9c2bd
   ||d1f97a59fe04b18e

--- Comment #20 from Fabian Vogt  ---
Git commit ec2afd27c790fbde63a9c2bdd1f97a59fe04b18e by Fabian Vogt.
Committed on 23/12/2017 at 12:09.
Pushed by fvogt into branch 'Applications/17.12'.

Fix duplicate authentication

Summary:
The response to EHLO triggers an authentication command, but with TLS
two EHLOs are sent: For the 220 from the server and after TLS negotiation.
However, sending it twice results in an unexpected "503 already authenticated"
response which ends up getting parsed by the SendJob, causing confusion.

By leaving the EHLO-resending to the SessionPrivate, the state can be properly
tracked.
Related: bug 387926

Reviewers: mlaurent, dvratil

Subscribers: lbeltrame, cgiboudeaux

Differential Revision: https://phabricator.kde.org/D9476

M  +19   -10   src/session.cpp
M  +1-0src/session_p.h
M  +0-1src/sessionthread.cpp

https://commits.kde.org/ksmtp/ec2afd27c790fbde63a9c2bdd1f97a59fe04b18e

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

[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1

[Fabian Vogt]

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

Fabian Vogt  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/ksm
   ||tp/5199ed07428a03f1aa340da3
   ||ae99fcfa62ba2751
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED FIXED
  Latest Commit||https://commits.kde.org/ksm
   ||tp/ec2afd27c790fbde63a9c2bd
   ||d1f97a59fe04b18e
 Status|CONFIRMED   |RESOLVED

--- Comment #32 from Fabian Vogt  ---
Git commit 5199ed07428a03f1aa340da3ae99fcfa62ba2751 by Fabian Vogt.
Committed on 23/12/2017 at 12:09.
Pushed by fvogt into branch 'Applications/17.12'.

Send the correct hostname with the HELO/EHLO command

Summary:
It sent the server's hostname previously, which some reject.

Test Plan: Ran nc as smtp server, uses the right hostname for EHLO now.

Reviewers: mlaurent, dvratil

Subscribers: #kde_pim

Tags: #kde_pim

Differential Revision: https://phabricator.kde.org/D9485

M  +13   -1src/session.cpp

https://commits.kde.org/ksmtp/5199ed07428a03f1aa340da3ae99fcfa62ba2751

--- Comment #33 from Fabian Vogt  ---
Git commit ec2afd27c790fbde63a9c2bdd1f97a59fe04b18e by Fabian Vogt.
Committed on 23/12/2017 at 12:09.
Pushed by fvogt into branch 'Applications/17.12'.

Fix duplicate authentication

Summary:
The response to EHLO triggers an authentication command, but with TLS
two EHLOs are sent: For the 220 from the server and after TLS negotiation.
However, sending it twice results in an unexpected "503 already authenticated"
response which ends up getting parsed by the SendJob, causing confusion.

By leaving the EHLO-resending to the SessionPrivate, the state can be properly
tracked.
Related: bug 388068

Reviewers: mlaurent, dvratil

Subscribers: lbeltrame, cgiboudeaux

Differential Revision: https://phabricator.kde.org/D9476

M  +19   -10   src/session.cpp
M  +1-0src/session_p.h
M  +0-1src/sessionthread.cpp

https://commits.kde.org/ksmtp/ec2afd27c790fbde63a9c2bdd1f97a59fe04b18e

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

[kmail2] [Bug 388170] New: Often in kmail the information bar shows a hanging message about synchronizing the trash folder of a specific IMAP account

[Freek de Kruijf]

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

Bug ID: 388170
   Summary: Often in kmail the information bar shows a hanging
message about synchronizing the trash folder of a
specific IMAP account
   Product: kmail2
   Version: 5.7.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: freekdekru...@kde.nl
  Target Milestone: ---

I have quite large IMAP account on a server with dovecot (~12000 messages) .
After starting kontact/kmail and after a while the information bar at the
bottom of the window shows a message indicating that the trash folder of that
IMAP account is being synchronized. The progress shown is not 100%, it varies,
but it does not change anymore. A click on the arrow to show more info shows
only the progress bar of synchronizing the trash folder of that particular IMAP
account at 100%. However it stays that way.
I tried command "akonadictl fsck", which sometimes shows irregular things, but
a second time, these are gone.
Currently "akonadictl vacuum" hangs after showing "optimizing table
CollectionTable..."
Also kontact/kmail does not show new messages. It shows turning dots in front
of the inbox.
After quite a while I give the command "akonadictl stop", which sometimes shows
a bug report, but even after installing the requested debug package, it shows a
that the bug report is not usable. akonadiserver crashed with a Segmentation
fault (11). Now akonadi vacuum continues but hangs in "optimizing table
PartTable...". "akonadictl status" shows "stopped".
The bApplication: akonadiserver (5.7.0)

Qt Version: 5.9.3
Frameworks Version: 5.40.0
Operating System: Linux 4.14.6-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:


The crash can be reproduced every time.

-- Backtrace:
A useful backtrace could not be generatedug report is:

akonadictl vacuum still hangs.
In kmail I can start akonadi again and things look normal apart from the
message in the messages bar where only the filter agent hangs.
After deleting some messages in the inbox of that IMAP acount I have the
situation back where the message bar shows 59% progress, but clicking the arrow
on that bar shows 100% progress on synchronizing the trash folder. The number
of messages in the trash folder is not updated after deleting the messages in
the inbox.

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

[kmail2] [Bug 388167] New: reply, reply to all and forward templates should be consistent with account dictionary

[avlas]

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

Bug ID: 388167
   Summary: reply, reply to all and forward templates should be
consistent with account dictionary
   Product: kmail2
   Version: 5.7.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: jsar...@gmail.com
  Target Milestone: ---

Use case: my computer is in my mother tongue and I use a professional email
account in a different language (my personal email account matches the system
language).

Conclusion: It would seem more professional if reply and forward templates in
the context of each email account would follow the language that is configured
for spell checking, instead of the system language.

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