[Akonadi] [Bug 407017] New: akonadi_maildir_resource crash

[Alexander Schier]

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

Bug ID: 407017
   Summary: akonadi_maildir_resource crash
   Product: Akonadi
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: Maildir Resource
  Assignee: kdepim-bugs@kde.org
  Reporter: a...@laxu.de
  Target Milestone: ---

I had a akonadi_maildir_resource crash in Ubuntu disco. I do not see what
version number is correct, as the different libakonadi-packages seem to have
different version numbers, but none with 5.x

Application: akonadi_maildir_resource (akonadi_maildir_resource), signal:
Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8e88e39800 (LWP 2778))]

Thread 4 (Thread 0x7f8e7f7fe700 (LWP 2814)):
[KCrash Handler]
#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#7  0x7f8e8cb57535 in __GI_abort () at abort.c:79
#8  0x7f8e8cdd0642 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#9  0x7f8e8cddc186 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#10 0x7f8e8cddc1d1 in std::terminate() () from
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#11 0x7f8e8cf9cdd3 in qTerminate() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7f8e8cf9e7c0 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7f8e8cb14182 in start_thread (arg=) at
pthread_create.c:486
#14 0x7f8e8cc4fb1f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7f8e7700 (LWP 2805)):
#0  0x7f8e8cc43729 in __GI___poll (fds=0x7f8e78026410, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f8e8b48bcb6 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f8e8b48bddc in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f8e8d1de063 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f8e8d1895bb in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f8e8cfd42c6 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f8e8e06a565 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7f8e8cfd5612 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f8e8cb14182 in start_thread (arg=) at
pthread_create.c:486
#9  0x7f8e8cc4fb1f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f8e87b2f700 (LWP 2785)):
#0  0x7f8e8cc43729 in __GI___poll (fds=0x7f8e87b2eca8, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f8e8bf5f917 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f8e8bf6153a in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f8e8871f6a8 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7f8e8cfd5612 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f8e8cb14182 in start_thread (arg=) at
pthread_create.c:486
#6  0x7f8e8cc4fb1f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f8e88e39800 (LWP 2778)):
#0  0x7f8e8b48b1d4 in g_main_context_prepare () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f8e8b48bbeb in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f8e8b48bddc in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f8e8d1de063 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f8e8d1895bb in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f8e8d1915e2 in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f8e8e5bc31e in Akonadi::ResourceBase::init(Akonadi::ResourceBase*)
() from /usr/lib/x86_64-linux-gnu/libKF5AkonadiAgentBase.so.5
#7  0x55eb81799f11 in ?? ()
#8  0x7f8e8cb58b6b in __libc_start_main (main=0x55eb81799d80, argc=3,
argv=0x7ffc99443a28, init=, fini=,
rtld_fini=, stack_end=0x7ffc99443a18) at ../csu/libc-start.c:308
#9  0x55eb81799dba in _start ()
[Inferior 1 (process 2778) detached]

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

[kmail2] [Bug 316153] can't move or delete messages in imap inbox

[Alexander Schier]

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

Alexander Schier <a...@laxu.de> changed:

   What|Removed |Added

 CC||a...@laxu.de

--- Comment #45 from Alexander Schier <a...@laxu.de> ---
Still a problem in KMail 5.6.3 (Debian buster)

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

[kmail2] [Bug 389427] New: Setup Wizard does not show if TLS will be used

[Alexander Schier]

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

Bug ID: 389427
   Summary: Setup Wizard does not show if TLS will be used
   Product: kmail2
   Version: 5.6.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: UI
  Assignee: kdepim-bugs@kde.org
  Reporter: a...@laxu.de
  Target Milestone: ---

The setup wizard asks first for Name, email and password and later (if you
choose manual IMAP) for a server name.
You can see nowhere if it will use TLS and when it will try to connect for the
first time. This means I do not know if my password may be sent in plaintext.

Please add a clear option 
TLS: yes, starttls, starttls (optional), no
where I can be sure that I will use TLS when using "yes" or "starttls".

I guess it defaults to TLS, but I have no idea about its fallback behaviour and
I am not even sure if it doesn't try without TLS. That's a bad thing for
setting up an email account.

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

[kmail2] [Bug 389426] Cannot cancel IMAP connection to server with wrong certificate

[Alexander Schier]

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

Alexander Schier <a...@laxu.de> changed:

   What|Removed |Added

   Platform|Other   |Debian testing

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

[kmail2] [Bug 389426] New: Cannot cancel IMAP connection to server with wrong certificate

[Alexander Schier]

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

Bug ID: 389426
   Summary: Cannot cancel IMAP connection to server with wrong
certificate
   Product: kmail2
   Version: 5.6.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: a...@laxu.de
  Target Milestone: ---

Use a wrong servername for the mail server in the setup wizard or the
"accounts" settings.

Then you get a "certificate error" message with "details, cancel, continue"
buttons. 
When clicking "cancel", the box reopens instantly with a second error message
box for "login failed, tls negotiation failed" in the background. Closing the
second one is not possible before you closed the first one, which reopens
quickly.

The only option to get back to the program is to keep ESC pressed until first
the TLS error message closes and then the login error message.

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

[Bug 125084] Do not move/re-upload messages where no filter applies

[Alexander Schier]

http://bugs.kde.org/show_bug.cgi?id=125084


Alexander Schier alexander_schier yahoo de changed:

   What|Removed |Added

 CC||alexander_sch...@yahoo.de




--- Comment #27 from Alexander Schier alexander_schier yahoo de  2009-02-02 
08:31:35 ---
The reupload behaviour is very annoying. It seems, kmail adds one or two
headers to each Mail? Is there some way to disable this? I even do not like it
very much, if a Mailprogram alters existing Mail. Who need stuff like X-Length,
if the length could be determined at display time?


-- 
Configure bugmail: http://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