[kmail2] [Bug 389659] Please wait while the message is transferred

[Ian]

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

--- Comment #7 from Ian  ---
excuse typos, using one hand and can't see where to edit after posting.

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

[kmail2] [Bug 389659] Please wait while the message is transferred

[Ian]

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

--- Comment #6 from Ian  ---
hi

I'm starting to think that some IMAP and POP3 code got confused.

I can understand the subject line message if I was using IMAP but everythink is
POP3 this end.

I don't know if this is related, possibly, but it seems like the latest update
re-arranged my folders as shown in Kmail to have "Local Folder" and "Local
folders (offline)" and all my account folders got put into the "offline"
branch. 

However now when I delete messages they get moved to (the new?) Trash folder in
the "Local folders" branch rather than to where all my old trash is, in the
Trash folder in the 'offline' branch.

The same re-arrangement could also be why the auto filters no longer work (but
do work when run manually).

It 'feels' like changes were put in which were relevant to IMAP mail but were
also applied to POP3 handling when they should not have been.

Aren't these problems related to Akonadi rather than Kmail?

Back in 2013 I lost a lot of mail, at the time I thought the disk was getting
flaky. So I was very surprised yesterday when poking around my disk, to find
what looks like all these missing mails going back to the early 2000s, in
.local/share/akonadi/file_lost+found/

Thanks, Ian

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

[kmail2] [Bug 381707] Notified mail has "move to wastebin" greyed out

[Con Kolivas]

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

Con Kolivas  changed:

   What|Removed |Added

Version|5.2.3   |5.5.3

--- Comment #4 from Con Kolivas  ---
Updated to Kubuntu 17.10 and now the problem appears on every new email instead
of sporadically.

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

[kmail2] [Bug 389980] New: Add posibility to resend any given email

[Albert Astals Cid]

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

Bug ID: 389980
   Summary: Add posibility to resend any given email
   Product: kmail2
   Version: 5.7.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: aa...@kde.org
  Target Milestone: ---

At the moment you can only resend the emails you have sent.

In many ocasions it is useful to resend an email someone else already sent, for
example, when sending a reminder that you only have to change the date but want
to keep the text structure, etc.

I have a vague memory that this was possible with older versions of KMail but
seems it's not possible now, i would really welcome the feature back :)

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

[kmail2] [Bug 389659] Please wait while the message is transferred

[Kitsuna]

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

--- Comment #5 from Kitsuna  ---
Unfortunately i have not been able to reproduce this issue on my end. It could
possibly be related to the amount of emails you are working with, you did
mention that you have been using it since 2005. If possible please try fully
uninstalling kmail then install again and use a test email address (just make
one on like Google or something) see if you can reproduce the issue. If it
works ok add your usual email again and see if it breaks. That should at least
help narrow down where to look.

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

[kmail2] [Bug 389659] Please wait while the message is transferred

[Ian]

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

--- Comment #4 from Ian  ---
Is there a workaround or something I can do to fix this?

It's interfering with my ability to work... the only way I can open old emails
is to find then on disk with Dolphin and open them from there. Trying to open
them in Kmail just produces the wait-forever dialogue which is now producing
bad behaviour from me...

Mail needs to be 100% stable when released. It's business-critical.

Or is there some other package or library which needs to be updated?

Thanks, Ian

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

[akregator] [Bug 389969] Keyboard navigation does not update browser frame

[EkriirkE]

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

--- Comment #1 from EkriirkE  ---
It also marks the stories read despite not displaying the story.  (I have
auto-mark-as read; 0 seconds enabled)

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

[akregator] [Bug 389969] New: Keyboard navigation does not update browser frame

[EkriirkE]

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

Bug ID: 389969
   Summary: Keyboard navigation does not update browser frame
   Product: akregator
   Version: 5.7.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: internal browser
  Assignee: kdepim-bugs@kde.org
  Reporter: k...@ekriirke.net
  Target Milestone: ---

When navigating the feed with arrows (left/right) the story selection still
highlights but the browser frame no longer updates (it flickers like it
refreshes, but it only shows the last story you actually clicked with the
mouse)

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

[kleopatra] [Bug 388561] somehow Menubar hidden. No obvious way to get it back (or hide it again)

[Achim Bohnet]

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

--- Comment #2 from Achim Bohnet  ---
The dolphin bug is not the same AFAIU.  I could restore menubar when I edited
the Kleopatra config file.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[kontact] [Bug 389958] New: Crash during entering recipient e-mail address in kmail.

[Tobias Lorenz]

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

Bug ID: 389958
   Summary: Crash during entering recipient  e-mail address in
kmail.
   Product: kontact
   Version: 5.6.3
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: tobias.lor...@gmx.net
  Target Milestone: ---

Application: kontact (5.6.3)

Qt Version: 5.9.2
Frameworks Version: 5.37.0
Operating System: Linux 4.14.0-3-amd64 x86_64
Distribution: Debian GNU/Linux testing (buster)

-- Information about the crash:
- What I was doing when the application crashed:
This happens whenever I create a new e-mail in kmail. As soon as I start
entering the recipients e-mail address, kmail crashes.
I use the CardDAV/CalDAV plugin together with a SOGo server.
My system is Debian testing, which I have continuously updated since years.
Might be that there are some artifacts from older kmail versions cause the
crash...

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f2709358080 (LWP 10948))]

Thread 28 (Thread 0x7f25a9c90700 (LWP 11011)):
#0  0x7f27066910c0 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x7f27068c9501 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f26ff8bcb39 in g_main_context_check () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f26ff8bd0c0 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f26ff8bd22c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f27068c910b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f270686e2aa in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f270668d35a in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f270669222d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f2701b1651a in start_thread (arg=0x7f25a9c90700) at
pthread_create.c:465
#10 0x7f2705d8f3ef in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 27 (Thread 0x7f25aa491700 (LWP 11002)):
#0  0x7f2701b1c7dd in futex_wait_cancelable (private=,
expected=0, futex_word=0x556c4540cfc8) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f2701b1c7dd in __pthread_cond_wait_common (abstime=0x0,
mutex=0x556c4540cf78, cond=0x556c4540cfa0) at pthread_cond_wait.c:502
#2  0x7f2701b1c7dd in __pthread_cond_wait (cond=0x556c4540cfa0,
mutex=0x556c4540cf78) at pthread_cond_wait.c:655
#3  0x7f26f68e9555 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f26f68e9a37 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f26f68ea7d1 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7f26f68e6e9b in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7f2701b1651a in start_thread (arg=0x7f25aa491700) at
pthread_create.c:465
#8  0x7f2705d8f3ef in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 26 (Thread 0x7f25bac3f700 (LWP 10994)):
#0  0x7f26ff902569 in g_mutex_lock () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f26ff8bc4e5 in g_main_context_prepare () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f26ff8bd04b in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f26ff8bd22c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f27068c910b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f270686e2aa in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f270668d35a in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f270669222d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f2701b1651a in start_thread (arg=0x7f25bac3f700) at
pthread_create.c:465
#9  0x7f2705d8f3ef in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 25 (Thread 0x7f25bb440700 (LWP 10993)):
#0  0x7f26ff8bd03e in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f26ff8bd22c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f27068c910b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f270686e2aa in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f270668d35a in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f270669222d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f2701b1651a in start_thread (arg=0x7f25bb440700) at
pthread_create.c:465
#7  0x7f2705d8f3ef in clone () at

[kleopatra] [Bug 388561] somehow Menubar hidden. No obvious way to get it back (or hide it again)

[GuHua]

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

GuHua  changed:

   What|Removed |Added

 CC||renyune...@gmail.com

--- Comment #1 from GuHua  ---
Maybe this is the same as https://bugs.kde.org/show_bug.cgi?id=385236 ?

I'm also experiencing menubar missing recently, and have found many possibly
same bug reports (or I'll open a new one if none of them really matches mine).

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[akregator] [Bug 389945] New: Akregator segmentation fault on startup

[Gianni]

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

Bug ID: 389945
   Summary: Akregator segmentation fault on startup
   Product: akregator
   Version: 5.7.1
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: gianni_2...@hotmail.it
  Target Milestone: ---

Application: akregator (5.7.1)

Qt Version: 5.9.3
Frameworks Version: 5.42.0
Operating System: Linux 4.13.0-32-generic x86_64
Distribution: KDE neon User Edition 5.11

-- Information about the crash:
I launched akregator using krunner but it crashed before showing anything.
I was browsing with firefox when it happened.

-- Backtrace:
Application: Akregator (akregator), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa9ea918980 (LWP 20049))]

Thread 22 (Thread 0x7fa965860700 (LWP 20113)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa9d3750d04 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7fa9d3750d49 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7fa9e0b566ba in start_thread (arg=0x7fa965860700) at
pthread_create.c:333
#4  0x7fa9e682f41d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 21 (Thread 0x7fa975ffb700 (LWP 20108)):
#0  0x7fa9e682374d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fa9dede338c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa9dede349c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa9e714a6cb in QEventDispatcherGlib::processEvents
(this=0x7fa994001bd0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fa9e70f2e2a in QEventLoop::exec (this=this@entry=0x7fa975ffac40,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7fa9e6f1b8f4 in QThread::exec (this=) at
thread/qthread.cpp:515
#6  0x7fa9e6f20709 in QThreadPrivate::start (arg=0x1235b90) at
thread/qthread_unix.cpp:368
#7  0x7fa9e0b566ba in start_thread (arg=0x7fa975ffb700) at
pthread_create.c:333
#8  0x7fa9e682f41d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 20 (Thread 0x7fa9767fc700 (LWP 20106)):
#0  __memcpy_sse2 () at ../sysdeps/x86_64/multiarch/../memcpy.S:116
#1  0x7fa9e6757cb3 in __dcigettext (domainname=0x7fa9e68b4bc0
<_libc_intl_domainname> "libc", msgid1=0x7fa9e68b502c "Bad file descriptor",
msgid2=msgid2@entry=0x0, plural=plural@entry=0, n=n@entry=0,
category=category@entry=5) at dcigettext.c:553
#2  0x7fa9e675662f in __GI___dcgettext (domainname=,
msgid=, category=category@entry=5) at dcgettext.c:47
#3  0x7fa9e67b35ec in __GI___strerror_r (errnum=errnum@entry=9,
buf=buf@entry=0x0, buflen=buflen@entry=0) at _strerror.c:71
#4  0x7fa9e67b351f in strerror (errnum=9) at strerror.c:31
#5  0x7fa9cb228641 in event_warn () from
/usr/lib/x86_64-linux-gnu/libevent-2.0.so.5
#6  0x7fa9cb22cc38 in ?? () from
/usr/lib/x86_64-linux-gnu/libevent-2.0.so.5
#7  0x7fa9cb216e2d in event_base_loop () from
/usr/lib/x86_64-linux-gnu/libevent-2.0.so.5
#8  0x7fa9d6fb68fe in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#9  0x7fa9d6fb23b5 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#10 0x7fa9d6fceeea in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#11 0x7fa9d6fe6d86 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#12 0x7fa9d6fe2f2d in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#13 0x7fa9e0b566ba in start_thread (arg=0x7fa9767fc700) at
pthread_create.c:333
#14 0x7fa9e682f41d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 19 (Thread 0x7fa976ffd700 (LWP 20105)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa9d6fdb1e5 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#2  0x7fa9d6fdb294 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#3  0x7fa9d6fb636d in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7fa9d6fb23b5 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7fa9d6fceeea in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7fa9d6fe6d86 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7fa9d6fe2f2d in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#8  0x7fa9e0b566ba in start_thread (arg=0x7fa976ffd700) at
pthread_create.c:333
#9  0x7fa9e682f41d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 18 (Thread 0x7fa9777fe700 (LWP 20104)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at

[kleopatra] [Bug 389792] Kleopatra (gpg4win 3.0.3) crashes during *.sig verification

[Andre Heinecke]

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

Andre Heinecke  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Andre Heinecke  ---
Hi,

thank you for the report. It is indeed a mayor bug in the last release and we
might even do a new minor release mostly to fix this.

It was already reported in the GnuPG Bugtracker https://dev.gnupg.org/T3761 and
has been fixed since.

(Resolving as upstream as this has been reported in the upstream tracker even
if its not an upstream issue)

Regards,
Andre

-- 
You are receiving this mail because:
You are on the CC list for the bug.