[kmail2] [Bug 357179] New: Email remains in inbox after moving it to a folder

2015-12-26 Thread Richard Bos via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357179

Bug ID: 357179
   Summary: Email remains in inbox after moving it to a folder
   Product: kmail2
   Version: 4.14.7
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: message list
  Assignee: kdepim-bugs@kde.org
  Reporter: richard@xs4all.nl

When an email is moved from inbox to another folder, it re-appears in inbox (
the copy in the other folder stays there btw ).


Reproducible: Always

Steps to Reproduce:
1. receive an email
2. move it from inbox to another folder
3. verify that the email has been moved to the other folder
4. go back to the inbox
5. the moved email appears again in the inbox

This behavior is the same for messages moved manually as well as filtered
emails

Actual Results:  
The moved email re-appears in inbox

Expected Results:  
The moved email should not re-appear in the inbox, as it has been copied to
another folder.

I'm using pop email.

I recently updated from openSUSE_13.1 where emails moving and filtering worked
just great ( as expected ).

Currently running kmail-4.14.10.

Looks a bit similar to bug report: 350059
But indeed also for me email filters are at the moment not usuable.

Restarting akonadictl does not help.

-- 
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


[kontact] [Bug 355279] Kontact crashes on App Start

2015-12-26 Thread Russell Greene via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=355279

Russell Greene  changed:

   What|Removed |Added

 CC||russellgree...@gmail.com

--- Comment #1 from Russell Greene  ---
Do you remember what you were doing two days ago when it stopped working?

-- 
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


[kontact] [Bug 355439] kontact crashed after updating an event

2015-12-26 Thread Russell Greene via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=355439

Russell Greene  changed:

   What|Removed |Added

 CC||russellgree...@gmail.com

--- Comment #1 from Russell Greene  ---
Could you tell us what you were doing when this crash occurred (if you
remember)? That would make it possible to try to reproduce the bug. Thank you!

-- 
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


[kontact] [Bug 357184] New: kontact crashed switching from kmail to korganizer

2015-12-26 Thread Dj YB via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357184

Bug ID: 357184
   Summary: kontact crashed switching from kmail to korganizer
   Product: kontact
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: yehi...@mail.ru

Application: kontact (4.14.10)
KDE Platform Version: 4.14.14
Qt Version: 4.8.6
Operating System: Linux 4.2.8-200.fc22.x86_64 x86_64
Distribution: "Fedora release 22 (Twenty Two)"

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

I have raised the kontact window and clicked on the korganizer icon to switch
from kmail to korganizer.

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

Thread 4 (Thread 0x7fbab42df700 (LWP 2593)):
#0  0x003cbc80c540 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x0034b4f8af61 in JSC::BlockAllocator::blockFreeingThreadMain() () at
/lib64/libQtWebKit.so.4
#2  0x0034b52896d6 in WTF::wtfThreadEntryPoint(void*) () at
/lib64/libQtWebKit.so.4
#3  0x7fbb023ee754 in  () at /lib64/libGL.so.1
#4  0x003cbc807555 in start_thread () at /lib64/libpthread.so.0
#5  0x003cbbd02b9d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7fbaa8440700 (LWP 3478)):
#0  0x003cbc80f29d in __lll_lock_wait () at /lib64/libpthread.so.0
#1  0x003cbc809906 in pthread_mutex_lock () at /lib64/libpthread.so.0
#2  0x7fbb023e89f2 in  () at /lib64/libGL.so.1
#3  0x7fbb023ed290 in  () at /lib64/libGL.so.1
#4  0x7fbb023ed766 in  () at /lib64/libGL.so.1
#5  0x7fbb0212bbf7 in  () at /lib64/tls/libnvidia-tls.so.304.128
#6  0x003cbdc8db00 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0
#7  0x003cbdc498b4 in g_main_context_check () at /lib64/libglib-2.0.so.0
#8  0x003cbdc49d60 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#9  0x003cbdc49ecc in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#10 0x0034a0fba4ee in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQtCore.so.4
#11 0x0034a0f88791 in
QEventLoop::processEvents(QFlags) () at
/lib64/libQtCore.so.4
#12 0x0034a0f88b05 in
QEventLoop::exec(QFlags) () at
/lib64/libQtCore.so.4
#13 0x0034a0e78289 in QThread::exec() () at /lib64/libQtCore.so.4
#14 0x0034a0e7aaac in QThreadPrivate::start(void*) () at
/lib64/libQtCore.so.4
#15 0x7fbb023ee754 in  () at /lib64/libGL.so.1
#16 0x003cbc807555 in start_thread () at /lib64/libpthread.so.0
#17 0x003cbbd02b9d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7fbaa4eb0700 (LWP 3786)):
#0  0x003cbbcf2fad in read () at /lib64/libc.so.6
#1  0x7fbb023ed73c in  () at /lib64/libGL.so.1
#2  0x7fbb0212bbf7 in  () at /lib64/tls/libnvidia-tls.so.304.128
#3  0x003cbdc8db00 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0
#4  0x003cbdc498b4 in g_main_context_check () at /lib64/libglib-2.0.so.0
#5  0x003cbdc49d60 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#6  0x003cbdc49ecc in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#7  0x0034a0fba4ee in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQtCore.so.4
#8  0x0034a0f88791 in
QEventLoop::processEvents(QFlags) () at
/lib64/libQtCore.so.4
#9  0x0034a0f88b05 in
QEventLoop::exec(QFlags) () at
/lib64/libQtCore.so.4
#10 0x0034a0e78289 in QThread::exec() () at /lib64/libQtCore.so.4
#11 0x0034a0f68863 in QInotifyFileSystemWatcherEngine::run() () at
/lib64/libQtCore.so.4
#12 0x0034a0e7aaac in QThreadPrivate::start(void*) () at
/lib64/libQtCore.so.4
#13 0x7fbb023ee754 in  () at /lib64/libGL.so.1
#14 0x003cbc807555 in start_thread () at /lib64/libpthread.so.0
#15 0x003cbbd02b9d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fbaffd18900 (LWP 2573)):
[KCrash Handler]
#6  0x0034a3c3e29e in KSelectionProxyModelPrivate::mapTopLevelToSource(int,
int) const () at /lib64/libkdeui.so.5
#7  0x0034a3c3e531 in KSelectionProxyModel::mapToSource(QModelIndex const&)
const () at /lib64/libkdeui.so.5
#8  0x0034a3c399c3 in KSelectionProxyModel::data(QModelIndex const&, int)
const () at /lib64/libkdeui.so.5
#9  0x0034b9e3ec5f in Akonadi::CalFilterProxyModel::filterAcceptsRow(int,
QModelIndex const&) const () at /lib64/libakonadi-calendar.so.4
#10 0x0034a27842c7 in
QSortFilterProxyModelPrivate::source_items_inserted(QModelIndex const&, int,
int, Qt::Orientation) () at /lib64/libQtGui.so.4
#11 0x0034a278457f in
QSortFilterProxyModelPrivate::_q_sourceRowsInserted(QModelIndex const&, int,
int) () at /lib64/libQtGui.so.4
#12 0x0034a0f9e0c0 in QMetaObject::activate(QObject*, QMetaObject const*,
int, 

[kontact] [Bug 134145] Kontact's components are not very consistent and intuitive

2015-12-26 Thread Russell Greene via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=134145

Russell Greene  changed:

   What|Removed |Added

 CC||russellgree...@gmail.com

--- Comment #2 from Russell Greene  ---
This is not a bug, but a feature request, and one that probably has been
addressed. I suggest that if you still feel this way you should reopen this as
a wishlist item.

-- 
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


[kmail2] [Bug 357174] New: KMail5 Crash when moving folder to inbox

2015-12-26 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357174

Bug ID: 357174
   Summary: KMail5 Crash when moving folder to inbox
   Product: kmail2
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: a.skemb...@gmail.com

Application: kmail (5.0.3)

Qt Version: 5.5.1
Operating System: Linux 4.3.3-1-default x86_64
Distribution: "openSUSE Tumbleweed (20151221) (x86_64)"

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

I imported a large number of e-mails from another computer. Moving the imported
folders to the main "inbox" folder (so that all folders are under "inbox"
instead of the container of the imports) causes the crash. It does not happen
everytime, but 2 out of 3 times Kmail will crash. Also, the folder is
eventually moved - restarting KMail shows the folder in the intended location.

The crash can be reproduced sometimes.

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

Thread 8 (Thread 0x7f5443aec700 (LWP 4545)):
#0  0x7f5466e0e24d in poll () from /lib64/libc.so.6
#1  0x7f545a4f2432 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f545a4f4007 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f5445814e29 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f546771694f in QThreadPrivate::start (arg=0x9d93e0) at
thread/qthread_unix.cpp:331
#5  0x7f545d7e74a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7f5466e16bdd in clone () from /lib64/libc.so.6

Thread 7 (Thread 0x7f5439456700 (LWP 4555)):
#0  0x7f5466e0a22d in read () from /lib64/libc.so.6
#1  0x7f545d00e210 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f545cfcbd94 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f545cfcc208 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7f545cfcc36c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7f546793b52b in QEventDispatcherGlib::processEvents
(this=0x7f54340008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#6  0x7f54678e563a in QEventLoop::exec (this=this@entry=0x7f5439455c90,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#7  0x7f5467711b1c in QThread::exec (this=) at
thread/qthread.cpp:503
#8  0x7f546771694f in QThreadPrivate::start (arg=0xf807c0) at
thread/qthread_unix.cpp:331
#9  0x7f545d7e74a4 in start_thread () from /lib64/libpthread.so.0
#10 0x7f5466e16bdd in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7f5433fff700 (LWP 4556)):
#0  0x7f545d7ed07f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f545835e3bb in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f545835e3f9 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f545d7e74a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7f5466e16bdd in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7f53f2698700 (LWP 4563)):
#0  0x7f545d7ed07f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f545806c764 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f545838d441 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f545d7e74a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7f5466e16bdd in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f53f1e97700 (LWP 4564)):
#0  0x7f545d7ed07f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f545806d793 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f545838d441 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f545d7e74a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7f5466e16bdd in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f53f1696700 (LWP 4565)):
#0  0x7f545d7ed07f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f545806d793 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f545838d441 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f545d7e74a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7f5466e16bdd in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f53f0e95700 (LWP 4566)):
#0  0x7f545d7ed07f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f545806d793 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7f545838d441 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7f545d7e74a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7f5466e16bdd in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f5469e17940 (LWP 4544)):
[KCrash Handler]
#6  count (this=0x50004) at ../../src/corelib/tools/qvector.h:203
#7  QSortFilterProxyModel::sibling (this=, row=1, column=1,
idx=...) at 

[Akonadi] [Bug 330250] Support preemptive authentication

2015-12-26 Thread Jonas Schürmann via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=330250

Jonas Schürmann  changed:

   What|Removed |Added

 CC||jonasschuerm...@aol.de

-- 
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


[kontact] [Bug 313825] Kontact crashes when replying to an email

2015-12-26 Thread Russell Greene via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=313825

Russell Greene  changed:

   What|Removed |Added

 CC||russellgree...@gmail.com

--- Comment #2 from Russell Greene  ---
Could you try upgrading to kontact 5.0.2 and see if the problem still exists?
Also, has this always happened or is this recent?

-- 
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


[kontact] [Bug 313825] Kontact crashes when replying to an email

2015-12-26 Thread Myriam Schweingruber via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=313825

Myriam Schweingruber  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from Myriam Schweingruber  ---
(In reply to Russell Greene from comment #2)
> Could you try upgrading to kontact 5.0.2 and see if the problem still exists?
> Also, has this always happened or is this recent?

Thank you for testing, Russel. 
This is already not reproducible with KMail 4.14.2, so no need to jump to
another version. I have sent several mails through Kontact, no crash so far.

-- 
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


[kmail2] [Bug 357204] Buttons in email have hard-to-see dark blue font over light blue background.

2015-12-26 Thread Sudhir Khanger via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357204

--- Comment #1 from Sudhir Khanger  ---
Created attachment 96312
  --> https://bugs.kde.org/attachment.cgi?id=96312=edit
dark blue font over light blue background

-- 
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


[kmail2] [Bug 357204] New: Buttons in email have hard-to-see dark blue font over light blue background.

2015-12-26 Thread Sudhir Khanger via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357204

Bug ID: 357204
   Summary: Buttons in email have hard-to-see dark blue font over
light blue background.
   Product: kmail2
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: sud...@sudhirkhanger.com

A good number of html emails have this button with dark blue font over light
blue background which is impossibly hard to see. Can we tweak the theme to make
it more visible?

Please see the attachment for a screenshot.

Reproducible: Always

-- 
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


[kmail2] [Bug 357204] Buttons in email have hard-to-see dark blue font over light blue background.

2015-12-26 Thread Sudhir Khanger via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357204

--- Comment #3 from Sudhir Khanger  ---
Created attachment 96314
  --> https://bugs.kde.org/attachment.cgi?id=96314=edit
another example

As you can see email from several providers have same problem. Dark blue
colored font over blue background.

-- 
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


[kmail2] [Bug 357204] Buttons in email have hard-to-see dark blue font over light blue background.

2015-12-26 Thread Sudhir Khanger via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357204

--- Comment #2 from Sudhir Khanger  ---
Created attachment 96313
  --> https://bugs.kde.org/attachment.cgi?id=96313=edit
another example

-- 
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