[kmail2] [Bug 354875] New: Kmail imap sync takes long time with FetchItems Error

2015-11-04 Thread Sylvain via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354875

Bug ID: 354875
   Summary: Kmail imap sync takes long time with FetchItems Error
   Product: kmail2
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: ago.sylv...@gmail.com

perhaps a duplicate of https://bugs.kde.org/show_bug.cgi?id=338571 but the
akonadi console do not match and the kmail version are different too.

Since upgrade to kmail 5.0 (now kmail 5.0.2) an imap folders takes forever to
sync with lots of error in akonadi console. This only happen on one imap
account (my university one, gmail and personal imap server syncs are working).

Reproducible: Always

Steps to Reproduce:
1.I don't know as it seems specific to one account on which I do not have
control on.

Actual Results:  
The sync is extremely slow. i tried to remove old mails and now the mail count
is 1862 but still it takes a very long time (>1h) to sync. Reset akonadi
(delete folder, try with new user, etc.) did not do any good. Because the sync
is slow, filtering the mails or even deleting some, result in duplicate and/or
"ghost" greyed message. If I let the computer always on, it will finish to sync
and remove the messages, most of the time.
Akonadi console output for the imap ressource spit the following error for what
seems all messages:
[code]
akonadi_imap_resource_1 (0x7f69f000cb90) 1728 { Command: "StreamPayload"
Payload Name: "PLD:HEAD" Request: "0" Detination: "" }
akonadi_imap_resource_1 (0x7f69f000cb90) 1728 { Command: "StreamPayload"
Payload Name: "PLD:HEAD" Request: "1" Detination: "" }
akonadi_imap_resource_1 (0x7f69f000cb90) 1728 { Command: "StreamPayload"
Payload Name: "PLD:ENVELOPE" Request: "0" Detination: "" }
akonadi_imap_resource_1 (0x7f69f000cb90) 1728 { Command: "StreamPayload"
Payload Name: "PLD:ENVELOPE" Request: "1" Detination: "" }
akonadi_imap_resource_1 (0x7f69f000cb90) 1728 { Command: "StreamPayload"
Payload Name: "PLD:RFC822" Request: "0" Detination: "" }
akonadi_imap_resource_1 (0x7f69f000cb90) 1728 { Command: "StreamPayload"
Payload Name: "PLD:RFC822" Request: "1" Detination: "65489_r792" }
akonadi_imap_resource_1 (0x7f69f000cb90) 1728 { Response: "FetchItems" Error
Code: "0" Error Msg: "" ID: "29530" Revision: "0" Collection ID: "-1" Remote
ID: "" Remote Revision: "" GID: "" Size: "0" Mimetype: "" Time:
"QDateTime(2015-11-05 02:36:10.362 UTC Qt::TimeSpec(UTC))" Flags: "QVector()"
Tags: { } Relations: { } Virtual References: "QVector()" Ancestors: { } Cached
Parts: "QVector()" Parts: { } }
akonadi_imap_resource_1 (0x7f69f000cb90) 1728 { Response: "CreateItem" Error
Code: "0" Error Msg: "" }
akonadi_imap_resource_1 (0x7f69f000cb90) 1729 { Command: "CreateItem" Merge
mode: "(Remote ID, Silent)" Collection: "UID 11" MimeType: "message/rfc822"
GID: "" Remote ID: "4436" Remote Revision: "" Size: "273299" Time: "QDateTime(
Qt::TimeSpec(LocalTime))" Tags: "Invalid scope" Added Tags: "Invalid scope"
Removed Tags: "Invalid scope" Flags: "QSet()" Added Flags: "QSet(\SEEN,
$ATTACHMENT)" Removed Flags: "QSet()" Attributes: { } Parts: "QSet(PLD:HEAD,
PLD:ENVELOPE, PLD:RFC822)" }
[/code]

Expected Results:  
sync work as fast as in previous versions.

If you need more info tell me I will do my best to provide them.

-- 
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 352464] Regression kMail 5.0.0: HTML mails do not show external images

2015-11-04 Thread Stephen Anthony via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=352464

--- Comment #7 from Stephen Anthony  ---
Has anyone figured out what other package(s) on the system that could cause
this?  I *really* don't want to reinstall. I can confirm that installing from
scratch in a VM does work fine, and the images appear as they should.  Can
anyone point me in the right direction as to what package could possibly cause
such an issue??

-- 
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 317333] Filtering using Quick Search on folders changes folder selection in message list

2015-11-04 Thread Manny via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=317333

--- Comment #3 from Manny  ---
Followup:  A workaround that actually speeds things up is to select the
messages
one wants to move or copy, then use the keyboard shortcut, e.g. 'm' to move the
messages. This opens up a folder window, and one can type in parts of
the target folder, just like for quick search. Once the right folder is
selected,
a  or 'click on ok' finishes the job. 

Two comments: I am still sorry that the normal folder quick search changes the
messages
to  once one types things in, and is otherwise less functional. Also,
on the 'old' kmail, after 'm' and getting the folder window, it is possible to
type
paths across folder divides, e.g. 'adm/misc' to restrict the match (useful for
me, since
I have many 'misc' subfolders. Also, it shows the subfolders of the matching
folder
paths, which gives a lot more flexibility in filtering down the folder list.
Unfortunately,
this functionality is no longer present in 4.14.1

Manny

-- 
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 352464] Regression kMail 5.0.0: HTML mails do not show external images

2015-11-04 Thread Stephen Anthony via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=352464

Stephen Anthony  changed:

   What|Removed |Added

 CC||stephena@users.sourceforge.
   ||net

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


[Akonadi] [Bug 354417] crash on boot

2015-11-04 Thread David Jarvie via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354417

David Jarvie  changed:

   What|Removed |Added

  Latest Commit||a528dcf98582da1c49163ff9320
   ||9fd00090eac01
   Version Fixed In||15.08.3
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from David Jarvie  ---
This seems very likely to be the crash which was fixed by commit
a528dcf98582da1c49163ff93209fd00090eac01 (15.08 branch). The fix will be in the
15.08.3 release due out soon.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[kmail2] [Bug 354400] In Kmail 5.0.2 autocompletion only shows recent email addresses but not stored emails in Kaddressbook

2015-11-04 Thread Christoph Rüßler via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354400

Christoph Rüßler  changed:

   What|Removed |Added

 CC||christoph.ruessler@mailbox.
   ||org

-- 
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 354400] In Kmail 5.0.2 autocompletion only shows recent email addresses but not stored emails in Kaddressbook

2015-11-04 Thread fisch via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354400

fisch  changed:

   What|Removed |Added

 CC||cohen.lu...@gmail.com

--- Comment #1 from fisch  ---
I have identified precisely the same behaviour.  Auto-complete works fine for
"recent addresses" and those "contacts found in your data" but does not seem to
complete from the (akonadi) address books.

Just to be clear, I am running Kubuntu 15.10, KMail 5.0.2 and KDE Frameworks
5.15.0.

-- 
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 292285] Cannot specify IMAP server directory

2015-11-04 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=292285

bjoe...@arcor.de changed:

   What|Removed |Added

 CC||bjoe...@arcor.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


[libkgapi] [Bug 318405] Broken timezones handling

2015-11-04 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=318405

bjoe...@arcor.de changed:

   What|Removed |Added

 CC||bjoe...@arcor.de

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[Akonadi] [Bug 334412] Data of Akonadi Google are not synced

2015-11-04 Thread Dmitri Koulikoff via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=334412

Dmitri Koulikoff  changed:

   What|Removed |Added

 CC||k...@mitrah.ru

--- Comment #9 from Dmitri Koulikoff  ---
Does not sync with 4.14.6
libgcal-0.9.6-x86_64-1_SBo
akonadi-googledata-1.2.0-x86_64-1_SBo

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[kmail2] [Bug 354727] Kmail has default icon in the task manager

2015-11-04 Thread Lastique via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354727

--- Comment #5 from Lastique  ---
Also, for other applications icons look fine. I can see the described problem
only with Kmail.

-- 
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 354727] Kmail has default icon in the task manager

2015-11-04 Thread Lastique via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354727

--- Comment #4 from Lastique  ---
That is the case on at least two of my machines, both were recently upgraded
from Kubuntu 15.04 to 15.10.

-- 
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 354840] New: Kmail locks up

2015-11-04 Thread Eric Christensen via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354840

Bug ID: 354840
   Summary: Kmail locks up
   Product: kmail2
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: e...@christensenplace.us

Application: kmail (4.14.9)
KDE Platform Version: 4.14.11
Qt Version: 4.8.6
Operating System: Linux 4.1.10-100.fc21.x86_64 x86_64
Distribution: "Fedora release 21 (Twenty One)"

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

Creating a new message.  When I went to send the message the program just
halted.

-- Backtrace:
Application: KMail (kmail), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
81T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7fb8eba1c900 (LWP 3189))]

Thread 3 (Thread 0x7fb8780ed700 (LWP 3517)):
#0  0x7fb8e6dbc590 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fb8ddbd2c93 in JSC::BlockAllocator::blockFreeingThreadMain()
(this=0x1ee1b18) at
/usr/src/debug/webkit-qtwebkit-23/Source/JavaScriptCore/heap/BlockAllocator.cpp:128
#2  0x7fb8ddee2c16 in WTF::wtfThreadEntryPoint(void*) (param=0x19fa420) at
/usr/src/debug/webkit-qtwebkit-23/Source/WTF/wtf/ThreadingPthreads.cpp:196
#3  0x7fb8e6db752a in start_thread (arg=0x7fb8780ed700) at
pthread_create.c:310
#4  0x7fb8e537f22d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fb8772a2700 (LWP 3521)):
#0  0x7fb8e6dbf1cd in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fb8d751ed00 in g_wakeup_acknowledge (__nbytes=16,
__buf=0x7fb8772a1ac0, __fd=) at /usr/include/bits/unistd.h:44
#2  0x7fb8d751ed00 in g_wakeup_acknowledge (wakeup=0x17fa2c0) at
gwakeup.c:210
#3  0x7fb8d74db5fc in g_main_context_check
(context=context@entry=0x7fb8680009a0, max_priority=2147483647,
fds=fds@entry=0x7fb8680013e0, n_fds=n_fds@entry=1) at gmain.c:3579
#4  0x7fb8d74dbad3 in g_main_context_iterate
(context=context@entry=0x7fb8680009a0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3778
#5  0x7fb8d74dbc4c in g_main_context_iteration (context=0x7fb8680009a0,
may_block=1) at gmain.c:3842
#6  0x7fb8e718157e in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fb8680008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#7  0x7fb8e7150d81 in
QEventLoop::processEvents(QFlags)
(this=this@entry=0x7fb8772a1cd0, flags=...) at kernel/qeventloop.cpp:149
#8  0x7fb8e71510e5 in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fb8772a1cd0, flags=...) at kernel/qeventloop.cpp:204
#9  0x7fb8e7045bb9 in QThread::exec() (this=) at
thread/qthread.cpp:538
#10 0x7fb8e704841f in QThreadPrivate::start(void*) (arg=0x1ceb6a0) at
thread/qthread_unix.cpp:349
#11 0x7fb8e6db752a in start_thread (arg=0x7fb8772a2700) at
pthread_create.c:310
#12 0x7fb8e537f22d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fb8eba1c900 (LWP 3189)):
[KCrash Handler]
#6  0x7fb8e52b38d7 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:55
#7  0x7fb8e52b553a in __GI_abort () at abort.c:89
#8  0x7fb8e703da24 in qt_message_output(QtMsgType, char const*)
(msgType=msgType@entry=QtFatalMsg, buf=) at
global/qglobal.cpp:2359
#9  0x7fb8e703dbb9 in qt_message(QtMsgType, const char *, typedef
__va_list_tag __va_list_tag *) (msgType=msgType@entry=QtFatalMsg,
msg=msg@entry=0x7fb8e8667280 "Fatal Error: Accessed global static '%s *%s()'
after destruction. Defined at %s:%d", ap=ap@entry=0x7ffd586a6020) at
global/qglobal.cpp:2405
#10 0x7fb8e703e4a1 in qFatal(char const*, ...)
(msg=msg@entry=0x7fb8e8667280 "Fatal Error: Accessed global static '%s *%s()'
after destruction. Defined at %s:%d") at global/qglobal.cpp:2588
#11 0x7fb8e853bb69 in Akonadi::Control::widgetNeedsAkonadi(QWidget*)
(this=) at
/usr/src/debug/kdepimlibs-4.14.10/akonadi/control.cpp:75
#12 0x7fb8e853bb69 in Akonadi::Control::widgetNeedsAkonadi(QWidget*)
(widget=widget@entry=0x4f22a20) at
/usr/src/debug/kdepimlibs-4.14.10/akonadi/control.cpp:266
#13 0x7fb8ea78e0cf in KMMainWidget::KMMainWidget(QWidget*, KXMLGUIClient*,
KActionCollection*, KSharedPtr) (this=0x4f22a20,
parent=, aGUIClient=0x1daf320, actionCollection=0x19f48f0,
config=...) at /usr/src/debug/kdepim-4.14.9/kmail/kmmainwidget.cpp:245
#14 0x7fb8ea73cc08 in KMMainWin::KMMainWin(QWidget*) (this=0x1daf2c0,
__in_chrg=, __vtt_parm=) at
/usr/src/debug/kdepim-4.14.9/kmail/kmmainwin.cpp:63
#15 0x7fb8ea74da27 in KMKernel::openReader(bool)
(this=this@entry=0x7ffd586a7960, onlyCheck=onlyCheck@entry=false) at
/usr/src/debug/kdepim-4.14.9/kmail/kmkernel.cpp:536
#16 0x7fb8ea7520f4 in KMKernel::action(bool, b

[kontact] [Bug 354832] New: akkregator crash when Kontact is closed

2015-11-04 Thread Julian Schmidt via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354832

Bug ID: 354832
   Summary: akkregator crash when Kontact is closed
   Product: kontact
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: jul...@chipmusik.de

Application: kontact (5.0.2)

Qt Version: 5.4.2
Operating System: Linux 4.2.0-16-generic x86_64
Distribution: Ubuntu 15.10

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

- Unusual behavior I noticed:
read rss messages were not marked as read on opening before I closed kontact.
this happens about once a day, or once evry 2 days since the update to kubuntu
15.10.
akkregator seems out of sync. messages are not being marked as read. The number
of new messages shown in a feed does not correspond to the actual number of
unread messages in the feed. when kontact is closed -> crash. often even with a
corrupted feed list after a restart.

The crash can be reproduced sometimes.

-- 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 0x7f876abc2880 (LWP 2951))]

Thread 7 (Thread 0x7f876621d700 (LWP 2953)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f878644f48b in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7f878644f4c9 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7f8781bce6aa in start_thread (arg=0x7f876621d700) at
pthread_create.c:333
#4  0x7f8787341eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f871ebd3700 (LWP 2954)):
#0  0x7f87873368dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f8780f511ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f8780f512fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f8787e7729b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f8787e1d75a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f8787c3b3d4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f8787c402be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f8781bce6aa in start_thread (arg=0x7f871ebd3700) at
pthread_create.c:333
#8  0x7f8787341eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f871e1da700 (LWP 2955)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f878615d5b4 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7f878647f341 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7f8781bce6aa in start_thread (arg=0x7f871e1da700) at
pthread_create.c:333
#4  0x7f8787341eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f871d9ba700 (LWP 2956)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f878615e5e3 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7f878647f341 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7f8781bce6aa in start_thread (arg=0x7f871d9ba700) at
pthread_create.c:333
#4  0x7f8787341eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f871d1b9700 (LWP 2957)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f878615e5e3 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7f878647f341 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7f8781bce6aa in start_thread (arg=0x7f871d1b9700) at
pthread_create.c:333
#4  0x7f8787341eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f871c9b8700 (LWP 2958)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f878615e5e3 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7f878647f341 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7f8781bce6aa in start_thread (arg=0x7f871c9b8700) at
pthread_create.c:333
#4  0x7f8787341eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f876abc2880 (LWP 2951)):
[KCrash Handler]
#6  QString::QString (other=..., this=this@entry=0x7ffc98479020) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:811
#7  Akregator::SearchBar::text (this=0x2977460) at
../../../akregator/src/searchbar.cpp:125
#8  0x7f86fd565f4f in Akregator::MainWidget::saveProperties
(this=0x25be6e0, 

[kmail2] [Bug 354822] Opening link in mail directs user to received location header instead of link

2015-11-04 Thread Martin van Es via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354822

--- Comment #2 from Martin van Es  ---
Found the problem. It's the "in application based on the contents of the URL"
setting in Default Applications settings for Web Browser. Setting it "hard" to
Chrome solves the problem.

It turns out the inspecting launcher does a bad job opening the re-location
header instead of the original link.

-- 
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 354822] Opening link in mail directs user to received location header instead of link

2015-11-04 Thread Martin van Es via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354822

--- Comment #1 from Martin van Es  ---
It seems the same for links received in Skype, which also trigger a
notification now. Maybe not a kmail bug but a link notifier bug? Can someone
point me in the right direction to file this bug?

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


[kmail] [Bug 130773] unread messages in ignored threads are not marked as read on IMAP server

2015-11-04 Thread Nick Leverton via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=130773

Nick Leverton  changed:

   What|Removed |Added

 CC||n...@leverton.org

--- Comment #19 from Nick Leverton  ---
This is still an issue in KDE 4.14.

-- 
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 212897] Option to mark ignored messages read

2015-11-04 Thread Nick Leverton via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=212897

Nick Leverton  changed:

   What|Removed |Added

 CC||n...@leverton.org

--- Comment #6 from Nick Leverton  ---
Seems to have missed the cut for kmail on KDE4, any chance of getting this done
before KDE5 please ?

-- 
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 354822] New: Opening link in mail directs user to received location header instead of link

2015-11-04 Thread Martin van Es via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354822

Bug ID: 354822
   Summary: Opening link in mail directs user to received location
header instead of link
   Product: kmail2
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: b...@mrvanes.com

Chrome is my default browser. I've noticed a couple of times that clicking
links in kmail sent me to some sort of "you need to be logged in" page instead
of the content I was looking for. Copying the link and pasting it in Chrome
always brings me to the right location.

After some debugging, it turns out that since 5.0.2 (15.08.2-0ubuntu1 and/or
the update to Kubuntu Wily) kmail for shows a notification of the click action.
After some event tracking in Chrome I found that the link that kmail (or
notifier?) sent to Chrome was actually the location header of the first
request. This results in lost sessions which can be shown with the following
example:

I have a mail with a link that looks like this:
https://.xxx.xx/seminar_i_want_to_visit/access.html?sac=CA2A50DD905F&ck=personalpage

When accessed directly in Chrome, this page answers with a status 302 (found)
and a location header containing:
https://.xxx.xx/seminar_i_want_to_visit/personalpage.html?sid=e4ed2a3a-e8b5-466e-97c5-5c4efbd07390

Which in turn shows me my personal page for this seminar.

When clicked in kmail however, the FIRST request that Chrome receives is:
https://.xxx.xx/seminar_i_want_to_visit/personalpage.html?sid=e4ed2a3a-e8b5-466e-97c5-5c4efbd07390

Which sends me to a login page, because there is no session for sid
e4ed2a3a-e8b5-466e-97c5-5c4efbd07390 yet.

Clicking the link a second time in kmail (after having opened the page using
copy/paste before) brings me to the correct page, since there now is a valid
session on sid e4ed2a3a-e8b5-466e-97c5-5c4efbd07390.


Reproducible: Always

Steps to Reproduce:
1. Receive mail with personal link that forces a location header containing
session information
2. Click link in kmail
3. Watch page

Actual Results:  
Genereic page without session telling me to login

Expected Results:  
Personal page

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