[akregator] [Bug 336417] Akregator crashes when being closed

2014-10-21 Thread David Faure
https://bugs.kde.org/show_bug.cgi?id=336417

--- Comment #23 from David Faure fa...@kde.org ---
Git commit b92a3688d91d76b7c0ffcb3775b232ed96062fc9 by David Faure.
Committed on 21/10/2014 at 07:22.
Pushed by dfaure into branch 'KDE/4.14'.

Delete the part from the mainwindow, not from the mainwidget.

This is a fix for kontact crashes on quit introduced by c5b703e7c
because I confused mainwindow and mainwidget. It restores a behavior
closer to before 8fc0d948f6e1, where the part was deleted by the mainwindow.

M  +0-2akregator/src/mainwidget.cpp
M  +7-0akregator/src/mainwindow.cpp
M  +1-0akregator/src/mainwindow.h

http://commits.kde.org/kdepim/b92a3688d91d76b7c0ffcb3775b232ed96062fc9

-- 
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 339393] Akonadi fail to fetch IMAP folder content with over 100MiB of messages (akonadi try to fetch too many UIDs at once)

2014-10-21 Thread boris.sh.1983+kde.bugzilla
https://bugs.kde.org/show_bug.cgi?id=339393

--- Comment #8 from boris.sh.1983+kde.bugzi...@gmail.com ---
Hi Andre, 

Your patch does solve the problem of Exchange choking on large UID search,
however the inital bug of unable to sync over 100 Mib folder is not solved yet.

It does split the search job as expected, yet when exchange disconnects the
session we do not continue from the last fetched uid.

After the next akonadi restart, retrieveitemstask will trigger refetching of
the dir and and not from the last uid in the collection.

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


[kaddressbook] [Bug 332358] Regression: Baloo for tags messes up categories/groups when syncing with external collections (e.g. owncloud)

2014-10-21 Thread mau
https://bugs.kde.org/show_bug.cgi?id=332358

--- Comment #9 from mau b-m...@gmx.ch ---
Akonadi is definitively actively maintained, think of e.g. imap or caldav which
reveived many bugfixes in the last couple of weeks. Also Kmail  Co. (thanks
Laurent).

But who should be working on this bug, Laurent as well? If yes, could you
please invest 5 minutes to look into this? As I wrote in comment 7, the
conversion is already in place, just not applied for the synchronization to the
outside world.

It would be very nice to get this fixed for Debian Jessie!

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


[kaddressbook] [Bug 332358] Regression: Baloo for tags messes up categories/groups when syncing with external collections (e.g. owncloud)

2014-10-21 Thread Larx
https://bugs.kde.org/show_bug.cgi?id=332358

--- Comment #10 from Larx throwa...@online.de ---
Glad to hear that something is going on. CardDAV and CalDAV, as you mention it,
is also a pain with Akonadi, making it impossible to use it with ownCloud,
eGroupware and so on. I was just wondering as all those errors aren't exactly
new, but some showstoppers have been there for years, literally...

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


[kaddressbook] [Bug 332358] Regression: Baloo for tags messes up categories/groups when syncing with external collections (e.g. owncloud)

2014-10-21 Thread mau
https://bugs.kde.org/show_bug.cgi?id=332358

--- Comment #11 from mau b-m...@gmx.ch ---
I'm using akonadi with ownCloud, exactly to synchronize calendars and addresses
across several devices; calendars are working fine since the lastest update.
Also synchronizing contacts is working to some extent - even changing photos
works after patching oc (just changing 2 lines in a php file). This bug is the
last one I'm currently facing!

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


[kaddressbook] [Bug 332358] Regression: Baloo for tags messes up categories/groups when syncing with external collections (e.g. owncloud)

2014-10-21 Thread Fuchs
https://bugs.kde.org/show_bug.cgi?id=332358

--- Comment #12 from Fuchs deve...@fuchsnet.ch ---
Talking to the developers at Randa I was told that this was going to be looked
into. 

Apparently that still didn't happen, and yes, it's a shame that a bug that can
lead to data loss / data corruption manages to stay for over half a year, plus
that leaving baloo basically unusable in kaddressbook and korganizer ...

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


[kaddressbook] [Bug 332358] Regression: Baloo for tags messes up categories/groups when syncing with external collections (e.g. owncloud)

2014-10-21 Thread Fabian
https://bugs.kde.org/show_bug.cgi?id=332358

--- Comment #13 from Fabian mays...@web.de ---
Nice to see that something is going on here.

I would like to discuss if it make sense at all to store this akonadi url as
internal reference. The only benefit I see is the possibility to rename
categories without loosing their associated elements. But this can also be
achieved with some kind of refactoring. On the downside developers of each
export and sync adapter have to care for the correct conversion. 
I think removing the akonadi url at all will be the faster and less error-prone
solution. But I have no insight in the architecture of akonadi...

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


[kaddressbook] [Bug 332358] Regression: Baloo for tags messes up categories/groups when syncing with external collections (e.g. owncloud)

2014-10-21 Thread Larx
https://bugs.kde.org/show_bug.cgi?id=332358

--- Comment #14 from Larx throwa...@online.de ---
Bug still unconfirmed?!

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


[kaddressbook] [Bug 332358] Regression: Baloo for tags messes up categories/groups when syncing with external collections (e.g. owncloud)

2014-10-21 Thread Marcel Meyer
https://bugs.kde.org/show_bug.cgi?id=332358

Marcel Meyer mey...@fs.tum.de changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #15 from Marcel Meyer mey...@fs.tum.de ---
*** This bug has been confirmed by popular vote. ***

-- 
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 340207] New: Kontact crash on start-up

2014-10-21 Thread sebastiaan.vandenbore
https://bugs.kde.org/show_bug.cgi?id=340207

Bug ID: 340207
   Summary: Kontact crash on start-up
   Product: kontact
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: sebastiaan.vandenb...@gmail.com

Application: kontact (4.12.5)
KDE Platform Version: 4.12.5 (Compiled from sources)
Qt Version: 4.8.5
Operating System: Linux 3.14.14-gentoo x86_64
Distribution (Platform): Gentoo Packages

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

Waiting for kontact to launch, no other desktop apps running.
Always starts with Summary module.

The crash can be reproduced sometimes.

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

Thread 4 (Thread 0x7fc8b5cc6700 (LWP 31843)):
#0  0x7fc8c5b7344c in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fc8c8bc4fed in WTF::TCMalloc_PageHeap::scavengerThread
(this=0x7fc8c957c300 WTF::pageheap_memory) at wtf/FastMalloc.cpp:2495
#2  0x7fc8c8bc50f9 in WTF::TCMalloc_PageHeap::runScavengerThread
(context=optimized out) at wtf/FastMalloc.cpp:1618
#3  0x7fc8c5b6f1da in start_thread () from /lib64/libpthread.so.0
#4  0x7fc8cb266d7d in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7fc8b53c5700 (LWP 31844)):
#0  0x7fc8cb25d29d in poll () from /lib64/libc.so.6
#1  0x7fc8c4f507dc in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fc8c4f50904 in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fc8cc662f3e in QEventDispatcherGlib::processEvents
(this=0x7fc8b8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#4  0x7fc8cc63381f in QEventLoop::processEvents
(this=this@entry=0x7fc8b53c4e70, flags=...) at kernel/qeventloop.cpp:149
#5  0x7fc8cc633aa8 in QEventLoop::exec (this=this@entry=0x7fc8b53c4e70,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7fc8cc536300 in QThread::exec (this=optimized out) at
thread/qthread.cpp:536
#7  0x7fc8cc538a7c in QThreadPrivate::start (arg=0x10b4f50) at
thread/qthread_unix.cpp:338
#8  0x7fc8c5b6f1da in start_thread () from /lib64/libpthread.so.0
#9  0x7fc8cb266d7d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fc857fff700 (LWP 11972)):
#0  0x7fc8c5b7344c in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fc86cf3f5c7 in QTWTF::TCMalloc_PageHeap::scavengerThread
(this=0x7fc86d24c660 QTWTF::pageheap_memory) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#2  0x7fc86cf3f5f9 in QTWTF::TCMalloc_PageHeap::runScavengerThread
(context=optimized out) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#3  0x7fc8c5b6f1da in start_thread () from /lib64/libpthread.so.0
#4  0x7fc8cb266d7d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fc8cdd07780 (LWP 31842)):
[KCrash Handler]
#6  QString (other=..., this=0x7fff8b9514d0) at
/usr/include/qt4/QtCore/qstring.h:725
#7  KontactInterface::Plugin::identifier (this=0x9c25f24) at
/var/tmp/portage/kde-base/kdepimlibs-4.12.5/work/kdepimlibs-4.12.5/kontactinterface/plugin.cpp:103
#8  0x7fc8cd4f7c04 in Kontact::MainWindow::activateInitialPluginModule() ()
from /usr/lib64/libkontactprivate.so.4
#9  0x0040434a in _start ()

The reporter indicates this bug may be a duplicate of or related to bug 298328.

Possible duplicates by query: bug 324131, bug 322264, bug 320449, bug 315612,
bug 313028.

Reported using DrKonqi

-- 
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 340208] New: 4.14.2: Save encrypted attachements does not work

2014-10-21 Thread Axel Braun
https://bugs.kde.org/show_bug.cgi?id=340208

Bug ID: 340208
   Summary: 4.14.2: Save encrypted attachements does not work
   Product: kmail2
   Version: 4.14.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: crypto
  Assignee: kdepim-bugs@kde.org
  Reporter: axel.br...@gmx.de

Receive a mail with several attachments (encrypted as well) and choose right
mouse-button - Save attachments.
Result: It saves a file 'encrypted.asc' instead of the (decrypted) attachments.
Each attachment has to be selected individually :-(

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 316153] can't move or delete messages in imap inbox

2014-10-21 Thread Félim Whiteley
https://bugs.kde.org/show_bug.cgi?id=316153

Félim Whiteley fe...@whiteley.ie changed:

   What|Removed |Added

 CC||fe...@whiteley.ie

--- Comment #19 from Félim Whiteley fe...@whiteley.ie ---
This is also effecting me as of last night, Kubuntu 14.04 with the latest
backported KDE 4.14.2

- I'm not using disconnected IMAP.
- I use IMAP also on my phone, I deleted about 12 mails on my phone, one was
still marked as unread, they now show above my Inbox folder in Kmail in the
account folder for that account, parent folder... not sure what to call it.

- I get the following errors if I try to go into that folder or try to remove
items from it: 
1. WT-Felim: Select failed, server replied: A007367 NO Client tried to access
nonexistent namespace. ( Mailbox name should probably be prefixed with: INBOX.
) 
2. WT-Felim: Fetch failed, server replied: A007368 BAD No mailbox selected. 

On my phone or via web interface to my IMAP account it's not possible to go
above the Inbox.

Is there any way via akonadis mysql interface or the like to remove these. It's
a pain to remove the entire inbox. I had a look in the DB but there's too much
for guesswork.

-- 
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 316153] can't move or delete messages in imap inbox

2014-10-21 Thread Félim Whiteley
https://bugs.kde.org/show_bug.cgi?id=316153

--- Comment #20 from Félim Whiteley fe...@whiteley.ie ---
Sorry hit save before I was done...

I meant to add, I am unable to move or copy/delete any mail in the folder as I
immediatly get a popup warning me it doesn't exist and the above errors.

Once I have clicked in here in general Kmail stops functioning correctly. Going
into folders causes huge periods of busy indicator on the folder I have clicked
on and the message list is blank for a very long time.

I am only using local subscriptions not server side.

I'll leave it in this state if there is anything you want me to do to help you
trouble shoot it. It's annoying but not stopping me for the time being. I
rather I could help you clear the bug.

Cheers,

Félim

-- 
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 337855] Kmail constantly crashes at startup

2014-10-21 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=337855

Christoph Feck christ...@maxiom.de changed:

   What|Removed |Added

   Severity|normal  |crash

--- Comment #1 from Christoph Feck christ...@maxiom.de ---
Application: kmail (4.13.2)
KDE Platform Version: 4.13.2
Qt Version: 4.8.6
Operating System: Linux 3.13.0-32-generic i686
Distribution: Ubuntu 14.04.1 LTS

-- Information about the crash:
When i try to launch kmailit constantly crashes

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1.
[Current thread is 1 (Thread 0xafe3e780 (LWP 11688))]

Thread 3 (Thread 0xaca49b40 (LWP 11691)):
#0  0xb776f424 in __kernel_vsyscall ()
#1  0xb5859d4b in pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187
#2  0xb5ed18ec in __pthread_cond_wait (cond=0xb3ceccb0, mutex=0xb3cecc98) at
forward.c:149
#3  0xb34749ac in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4
#4  0xb34749ff in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4
#5  0xb5855f70 in start_thread (arg=0xaca49b40) at pthread_create.c:312
#6  0xb5ec470e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129

Thread 2 (Thread 0xac0b9b40 (LWP 11692)):
#0  0xb776f424 in __kernel_vsyscall ()
#1  0xb5859d4b in pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187
#2  0xb5ed18ec in __pthread_cond_wait (cond=0xac1967dc, mutex=0xac1967c4) at
forward.c:149
#3  0xb34a39f3 in WTF::ThreadCondition::wait(WTF::Mutex) () from
/usr/lib/i386-linux-gnu/libQtWebKit.so.4
#4  0xb317f574 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4
#5  0xb348a7c6 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4
#6  0xb34a3369 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4
#7  0xb5855f70 in start_thread (arg=0xac0b9b40) at pthread_create.c:312
#8  0xb5ec470e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129

Thread 1 (Thread 0xafe3e780 (LWP 11688)):
[KCrash Handler]
#7  0xb6ee1a5b in KMMainWidget::setupActions (this=this@entry=0x9369b10) at
../../kmail/kmmainwidget.cpp:3630
#8  0xb6ee6cb6 in KMMainWidget::KMMainWidget (this=0x9369b10, parent=0x9125130,
aGUIClient=0x9125160, actionCollection=0x92b5790, config=...) at
../../kmail/kmmainwidget.cpp:266
#9  0xb6e8e351 in KMMainWin::KMMainWin (this=0x9125130, __in_chrg=optimized
out, __vtt_parm=optimized out) at ../../kmail/kmmainwin.cpp:67
#10 0xb6e9f4f6 in KMKernel::openReader (this=this@entry=0xbfe59744,
onlyCheck=onlyCheck@entry=false) at ../../kmail/kmkernel.cpp:532
#11 0xb6ea39ec in KMKernel::action (this=0xbfe59744, mailto=mailto@entry=false,
check=false, to=..., cc=..., bcc=..., subj=..., body=..., messageFile=...,
attachURLs=..., customHeaders=..., replyTo=..., inReplyTo=...) at
../../kmail/kmkernel.cpp:1343
#12 0xb6ea44ac in KMKernel::handleCommandLine (this=0xbfe59744,
noArgsOpensReader=noArgsOpensReader@entry=true) at ../../kmail/kmkernel.cpp:441
#13 0x0804aaf1 in KMailApplication::newInstance (this=0xbfe5972c) at
../../kmail/main.cpp:87
#14 0xb750b07f in KUniqueApplicationAdaptor::newInstance
(this=this@entry=0x91ab7f0, asn_id=..., args=...) at
../../kdeui/kernel/kuniqueapplication.cpp:442
#15 0xb750b106 in KUniqueApplicationAdaptor::qt_static_metacall
(_o=_o@entry=0x91ab7f0, _id=_id@entry=0, _a=_a@entry=0xbfe58e9c,
_c=QMetaObject::InvokeMetaMethod) at ./kuniqueapplication_p.moc:57
#16 0xb750b393 in qt_static_metacall (_a=0xbfe58e9c, _id=0,
_c=QMetaObject::InvokeMetaMethod, _o=0x91ab7f0) at
./kuniqueapplication_p.moc:100
#17 KUniqueApplicationAdaptor::qt_metacall (this=0x91ab7f0,
_c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfe58e9c) at
./kuniqueapplication_p.moc:101
#18 0xb592421e in QDBusConnectionPrivate::deliverCall
(this=this@entry=0x91121e0, object=object@entry=0x91ab7f0, msg=...,
metaTypes=..., slotIdx=4) at qdbusintegrator.cpp:951
#19 0xb592548e in QDBusConnectionPrivate::activateCall (this=0x91121e0,
object=0x91ab7f0, flags=337, msg=...) at qdbusintegrator.cpp:856
#20 0xb5925b97 in QDBusConnectionPrivate::activateObject (this=0x91121e0,
node=..., msg=..., pathStartPos=16) at qdbusintegrator.cpp:1427
#21 0xb5925f78 in QDBusActivateObjectEvent::placeMetaCall (this=0x9420010) at
qdbusintegrator.cpp:1541
#22 0xb62206fb in QObject::event (this=this@entry=0xbfe5972c,
e=e@entry=0x9420010) at kernel/qobject.cpp:1194
#23 0xb620ba9a in QCoreApplication::event (this=0xbfe5972c, e=0x9420010) at
kernel/qcoreapplication.cpp:1765
#24 0xb64b4d0f in QApplication::event (this=0xbfe5972c, e=0x9420010) at
kernel/qapplication.cpp:2549
#25 0xb64af7f4 in QApplicationPrivate::notify_helper (this=0x912c958,
receiver=0xbfe5972c, e=0x9420010) at kernel/qapplication.cpp:4567
#26 0xb64b62d3 in QApplication::notify (this=0xbfe5972c,

[kontact] [Bug 333725] Kontact crashed out of the blue

2014-10-21 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=333725

--- Comment #2 from Christoph Feck christ...@maxiom.de ---
*** Bug 337611 has been marked as a duplicate of 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


[kmail2] [Bug 261559] KMail stopped recognizing KWallet for password for specific SMTP server

2014-10-21 Thread Volker Kuhlmann
https://bugs.kde.org/show_bug.cgi?id=261559

Volker Kuhlmann list0...@paradise.net.nz changed:

   What|Removed |Added

 CC||list0...@paradise.net.nz

--- Comment #21 from Volker Kuhlmann list0...@paradise.net.nz ---
Not fixed
kmail-4.10.5-1.100.2.x86_64
openSUSE 12.3
kmail uses passwords from kwallet for IMAP retrieval, and by the looks of it
for other SMTP servers, but there's always one for which it doesn't.

It's been driving me nuts...

-- 
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 261559] KMail stopped recognizing KWallet for password for specific SMTP server

2014-10-21 Thread Dimitrios Glentadakis
https://bugs.kde.org/show_bug.cgi?id=261559

Dimitrios Glentadakis dgl...@free.fr changed:

   What|Removed |Added

 CC|dgl...@free.fr  |

-- 
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 261559] KMail stopped recognizing KWallet for password for specific SMTP server

2014-10-21 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=261559

--- Comment #22 from Laurent Montel mon...@kde.org ---
4.10.5 is very old.
But could you explain me how to reproduce it.
Which is the exact message error?

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