[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"

[via KDE Bugzilla]

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

--- Comment #53 from andreas.sturmlech...@gmail.com ---
I've been wrestling with akonadi during the past months (15.12.0 - 16.04.1)
using `akonadictl fsck` and `akonadictl restart` whenever I clearly knew there
really was new mail on the (gmail) server while kmail kept silent - which could
happen several times a day. Today, by chance I've met an old friend again,
"Multiple merge candidates, aborting", so maybe it had been that problem all
the time. Above SQL query though revealed _a lot_ of duplicates, so maybe it is
the result of all the times akonadi goes on a 'several thousand new mails in
random subfolder' frenzy (also can happen a couple o' times a day). Either way,
I wouldn't delete them one by one, so I came up with another SQL statement:

DELETE FROM pimitemtable
WHERE pimitemtable.id in (
  SELECT id
  FROM pimitemtable
  LEFT OUTER JOIN (
SELECT MIN(pimitemtable.id) as RowId, pimitemtable.remoteId,
pimitemtable.collectionId
FROM pimitemtable
GROUP by pimitemtable.remoteId, pimitemtable.collectionId
  ) as KeepRows ON pimitemtable.id = KeepRows.RowId
  WHERE KeepRows.RowId IS NULL
)


Beware, this might kill n kittens if you ran it on your system.

-- 
You are receiving this mail because:
You are the assignee for the bug.
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 364005] New: ASSERT: "!mReadingFinished" when composing a message

[Christophe Giboudeaux via KDE Bugzilla]

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

Bug ID: 364005
   Summary: ASSERT: "!mReadingFinished" when composing a message
   Product: Akonadi
   Version: GIT (master)
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: server
  Assignee: kdepim-bugs@kde.org
  Reporter: cgiboude...@gmx.com

Using master, the crash is reproducible.

In KMail, press the "new message button", enter the beginning of an existing
address, let the autocompletion suggest something and select it.

Press enter, KMail then crashes :

23:09:29 - kmail2(3902) - akonadicore_log: : Received response for a job that
does not expect any more data, ignoring
23:09:29 - kmail2(3902) -  : ASSERT: "!mReadingFinished" in file
/kde/src/5/akonadiserver/src/core/jobs/job.cpp, line 67


#4  0x756f4f1e in qt_assert(char const*, char const*, int)
(assertion=, file=, line=) at
global/qglobal.cpp:2999
#5  0x7fffee7349a3 in Akonadi::JobPrivate::handleResponse(long long,
Akonadi::Protocol::Command const&) (this=0x317ab40, tag=7, response=...) at
/kde/src/5/akonadiserver/src/core/jobs/job.cpp:67
#6  0x7fffee6f656c in Akonadi::SessionPrivate::handleCommand(long long,
Akonadi::Protocol::Command const&) (this=0x2746ca0, tag=7, cmd=...) at
/kde/src/5/akonadiserver/src/core/session.cpp:143
#7  0x7fffee6f8257 in Akonadi::Session::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) (_o=0x1c629e0,
_c=QMetaObject::InvokeMetaMethod, _id=4, _a=0x7fff38004750) at
/kde/build/5/akonadiserver/src/core/moc_session.cpp:117
#8  0x759023d1 in QObject::event(QEvent*) (this=0x1c629e0, e=) at kernel/qobject.cpp:1256
#9  0x765fd30c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x1c629e0, e=0x7fff38005440) at
kernel/qapplication.cpp:3804
#10 0x76602486 in QApplication::notify(QObject*, QEvent*)
(this=0x7fffd1b0, receiver=0x1c629e0, e=0x7fff38005440) at
kernel/qapplication.cpp:3561
#11 0x758d66e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x1c629e0, event=event@entry=0x7fff38005440) at
kernel/qcoreapplication.cpp:1015
#12 0x758d84ca in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (event=0x7fff38005440, receiver=) at
kernel/qcoreapplication.h:225
#13 0x758d84ca in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=receiver@entry=0x0, event_type=event_type@entry=0,
data=0x628540) at kernel/qcoreapplication.cpp:1650
#14 0x758d8988 in QCoreApplication::sendPostedEvents(QObject*, int)
(receiver=receiver@entry=0x0, event_type=event_type@entry=0) at
kernel/qcoreapplication.cpp:1508
#15 0x75928733 in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=0x6bfd00) at kernel/qeventdispatcher_glib.cpp:270
#16 0x7fffea183227 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.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

[akregator] [Bug 364000] New: Akregator crashes during start

[Gabriel Rüeck via KDE Bugzilla]

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

Bug ID: 364000
   Summary: Akregator crashes during start
   Product: akregator
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: gabr...@rueeck.de

Application: akregator (4.14.10)
KDE Platform Version: 4.14.9
Qt Version: 4.8.6
Operating System: Linux 3.16.7-35-desktop x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
When I start Akregator, it crashes. If I repeat the action, the same behaviour
persists.
- Custom settings of the application:
If I start kontact and then click on Akregator, it works. But as stand-alone,
it does not work.

The crash can be reproduced every time.

-- Backtrace:
Application: Akregator (akregator), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fab99a877c0 (LWP 4450))]

Thread 4 (Thread 0x7fab6700 (LWP 4457)):
#0  0x7fab917a403f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fab7de71686 in WTF::TCMalloc_PageHeap::scavengerThread() () from
/usr/lib64/libQtWebKit.so.4
#2  0x7fab7de716b9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) ()
from /usr/lib64/libQtWebKit.so.4
#3  0x7fab917a00a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7fab965d500d in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7fab2edbf700 (LWP 4459)):
#0  0x7fab965ccbdd in poll () from /lib64/libc.so.6
#1  0x7fab90985be4 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fab90985cec in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fab97ea50de in QEventDispatcherGlib::processEvents
(this=0x7fab28e0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#4  0x7fab97e76e6f in QEventLoop::processEvents
(this=this@entry=0x7fab2edbee20, flags=...) at kernel/qeventloop.cpp:149
#5  0x7fab97e77165 in QEventLoop::exec (this=this@entry=0x7fab2edbee20,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7fab97d740bf in QThread::exec (this=) at
thread/qthread.cpp:538
#7  0x7fab97d7679f in QThreadPrivate::start (arg=0x28ed0e0) at
thread/qthread_unix.cpp:349
#8  0x7fab917a00a4 in start_thread () from /lib64/libpthread.so.0
#9  0x7fab965d500d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fab2cf20700 (LWP 4477)):
#0  0x7fab917a403f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fab7dbe3e7d in JSC::BlockAllocator::blockFreeingThreadMain() () from
/usr/lib64/libQtWebKit.so.4
#2  0x7fab7de991e6 in WTF::wtfThreadEntryPoint(void*) () from
/usr/lib64/libQtWebKit.so.4
#3  0x7fab917a00a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7fab965d500d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fab99a877c0 (LWP 4450)):
[KCrash Handler]
#5  0x7fab7dae7c37 in QtMIMETypeSniffer::~QtMIMETypeSniffer() () from
/usr/lib64/libQtWebKit.so.4
#6  0x7fab7cabcacc in
WebCore::JSNodeOwner::isReachableFromOpaqueRoots(JSC::Handle,
void*, JSC::SlotVisitor&) () from /usr/lib64/libQtWebKit.so.4
#7  0x7fab7dbe2dda in JSC::WeakBlock::visit(JSC::HeapRootVisitor&) () from
/usr/lib64/libQtWebKit.so.4
#8  0x7fab7dbf068b in
JSC::MarkedSpace::visitWeakSets(JSC::HeapRootVisitor&) () from
/usr/lib64/libQtWebKit.so.4
#9  0x7fab7dbe5ae5 in JSC::Heap::markRoots(bool) () from
/usr/lib64/libQtWebKit.so.4
#10 0x7fab7dbe76a5 in JSC::Heap::collect(JSC::Heap::SweepToggle) () from
/usr/lib64/libQtWebKit.so.4
#11 0x7fab7ddbaea2 in JSC::DefaultGCActivityCallback::doWork() () from
/usr/lib64/libQtWebKit.so.4
#12 0x7fab7dbea70d in JSC::HeapTimer::timerEvent(QTimerEvent*) () from
/usr/lib64/libQtWebKit.so.4
#13 0x7fab97e903b1 in QObject::event (this=0x7fab742b04c0, e=) at kernel/qobject.cpp:1193
#14 0x7fab96f9476c in QApplicationPrivate::notify_helper
(this=this@entry=0x22e1770, receiver=receiver@entry=0x7fab742b04c0,
e=e@entry=0x7ffc6a473350) at kernel/qapplication.cpp:4565
#15 0x7fab96f9acad in QApplication::notify (this=0x7ffc6a473790,
receiver=0x7fab742b04c0, e=0x7ffc6a473350) at kernel/qapplication.cpp:4351
#16 0x7fab988dde0a in KApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libkdeui.so.5
#17 0x7fab97e782ad in QCoreApplication::notifyInternal
(this=0x7ffc6a473790, receiver=0x7fab742b04c0, event=0x7ffc6a473350) at
kernel/qcoreapplication.cpp:953
#18 0x7fab97ea7cbc in sendEvent (event=, receiver=) at kernel/qcoreapplication.h:231
#19 QTimerInfoList::activateTimers (this=0x22d8330) at
kernel/qeventdispatcher_unix.cpp:636
#20 0x7fab97ea4f01 in timerSourceDispatch (source=) at
kernel/qeventdispatcher_glib.cpp:193
#21 0x7fab90985a04 in 

[kmail2] [Bug 357481] KMail doesn't honor the "always sign with GPG" flag in idendity when replying

[Christian Boltz via KDE Bugzilla]

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

Christian Boltz  changed:

   What|Removed |Added

 Status|RESOLVED|VERIFIED

--- Comment #12 from Christian Boltz  ---
I finally upgraded to KMail 5.2.1 (from KDE Applications 16.04.1), and the
signing defaults work as expected :-)

Thanks again for fixing this!

-- 
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 363723] Kmail crashes when "Server supports sieve" enabled

[Wouter Haffmans via KDE Bugzilla]

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

--- Comment #14 from Wouter Haffmans  ---
I have a similar crash (Arch Linux, see bug 363987 - already marked as dupe).
My setup has 4 different Kolab mailboxes and one GMail without Sieve support.

Account 1: a "Filters" enabled script, and a disabled "roundcube" script
Account 2: one disabled "Filters" script.
NOTE: The syntax checker of KMail succeeds, but trying to enable this one from
KMail results in an error: "Sieve operation failed. The server responded:
script errors:" (no further details)
Account 3: an enabled "Filters" script
Account 4: an enabled "roundcube" script

All scripts were edited through Roundcube.

-- 
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 363723] Kmail crashes when "Server supports sieve" enabled

[Wouter Haffmans via KDE Bugzilla]

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

Wouter Haffmans  changed:

   What|Removed |Added

 CC||wou...@simply-life.net

--- Comment #13 from Wouter Haffmans  ---
*** Bug 363987 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

[kontact] [Bug 363987] Kontact crashes on start-up

[Wouter Haffmans via KDE Bugzilla]

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

Wouter Haffmans  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #3 from Wouter Haffmans  ---


*** This bug has been marked as a duplicate of bug 363723 ***

-- 
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 363987] Kontact crashes on start-up

[Wouter Haffmans via KDE Bugzilla]

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

Wouter Haffmans  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=363723

--- Comment #2 from Wouter Haffmans  ---
Found possible (likely) duplicate: 363723

-- 
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 363987] Kontact crashes on start-up

[Wouter Haffmans via KDE Bugzilla]

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

--- Comment #1 from Wouter Haffmans  ---
Similar backtrace of another crash just now:

Thread 1 (Thread 0x7f4a22e0a840 (LWP 31842)):
[KCrash Handler]
#5  0x7f4a203f3d3e in QString::append(QString const&) () from
/usr/lib/libQt5Core.so.5
#6  0x7f49943117a3 in ?? () from /usr/lib/libKF5KSieveUi.so.5
#7  0x7f499431184e in ?? () from /usr/lib/libKF5KSieveUi.so.5
#8  0x7f4994311ffc in ?? () from /usr/lib/libKF5KSieveUi.so.5
#9  0x7f4a2056a77c in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
#10 0x7f499246d06b in
KManageSieve::SieveJob::gotScript(KManageSieve::SieveJob*, bool, QString
const&, bool) () from /usr/lib/libKF5KManageSieve.so.5
#11 0x7f499246b14d in
KManageSieve::SieveJob::Private::handleResponse(KManageSieve::Response const&,
QByteArray const&) () from /usr/lib/libKF5KManageSieve.so.5
#12 0x7f4992461d61 in ?? () from /usr/lib/libKF5KManageSieve.so.5
#13 0x7f4a2056b1d9 in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
#14 0x7f4a214b67bc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#15 0x7f4a214bb95f in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#16 0x7f4a2053d2e0 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#17 0x7f4a2053f25c in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/libQt5Core.so.5
#18 0x7f4a20593323 in ?? () from /usr/lib/libQt5Core.so.5
#19 0x7f4a1816cdd7 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#20 0x7f4a1816d040 in ?? () from /usr/lib/libglib-2.0.so.0
#21 0x7f4a1816d0ec in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#22 0x7f4a2059372f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#23 0x7f4a2053b4ca in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#24 0x7f4a20543a6c in QCoreApplication::exec() () from
/usr/lib/libQt5Core.so.5
#25 0x0040434f in ?? ()
#26 0x7f4a1f99e741 in __libc_start_main () from /usr/lib/libc.so.6
#27 0x00404859 in _start ()

-- 
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 363987] New: Kontact crashes on start-up

[Wouter Haffmans via KDE Bugzilla]

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

Bug ID: 363987
   Summary: Kontact crashes on start-up
   Product: kontact
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: wou...@simply-life.net

Application: kontact (5.2.1)

Qt Version: 5.6.0
Frameworks Version: 5.22.0
Operating System: Linux 4.5.4-1-ARCH x86_64
Distribution: "Arch Linux"

-- Information about the crash:
- What I was doing when the application crashed:
Launching Kontact (on Arch Linux, x64, Plasma)

Usually it takes several attempts for Kontact to start up correctly, after
which there aren't any further crashes.

- Custom settings of the application:
I have several Kolab agents set up, with Sieve scripts set up by Roundcube (see
backtrace; it mentions Sieve in there). The server-side has "Kolab 16"
installed on CentOS 7.

A possibly related side-effect may be that Sieve scripts sometimes don't load
correctly in KMail (i.e. I cannot configure them). The icon for some of the
accounts keeps on spinning attempting to load the scripts, so it seems.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kontact (kontact), signal: Aborted
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fdf4942f840 (LWP 31581))]

Thread 34 (Thread 0x7fdf2cbe8700 (LWP 31582)):
#0  0x7fdf4608168d in poll () from /usr/lib/libc.so.6
#1  0x7fdf3f5e08e0 in ?? () from /usr/lib/libxcb.so.1
#2  0x7fdf3f5e2679 in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#3  0x7fdf2f167bc9 in ?? () from /usr/lib/libQt5XcbQpa.so.5
#4  0x7fdf4698c1d8 in ?? () from /usr/lib/libQt5Core.so.5
#5  0x7fdf3efb4474 in start_thread () from /usr/lib/libpthread.so.0
#6  0x7fdf4608a69d in clone () from /usr/lib/libc.so.6

Thread 33 (Thread 0x7fdf24255700 (LWP 31583)):
#0  0x7ffdbcf72c59 in clock_gettime ()
#1  0x7fdf46097356 in clock_gettime () from /usr/lib/libc.so.6
#2  0x7fdf46a37d96 in ?? () from /usr/lib/libQt5Core.so.5
#3  0x7fdf46bb62f9 in QTimerInfoList::updateCurrentTime() () from
/usr/lib/libQt5Core.so.5
#4  0x7fdf46bb68a5 in QTimerInfoList::timerWait(timespec&) () from
/usr/lib/libQt5Core.so.5
#5  0x7fdf46bb7c3e in ?? () from /usr/lib/libQt5Core.so.5
#6  0x7fdf3e79150d in g_main_context_prepare () from
/usr/lib/libglib-2.0.so.0
#7  0x7fdf3e791efb in ?? () from /usr/lib/libglib-2.0.so.0
#8  0x7fdf3e7920ec in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#9  0x7fdf46bb874b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#10 0x7fdf46b604ca in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#11 0x7fdf469872f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#12 0x7fdf4525ba65 in ?? () from /usr/lib/libQt5DBus.so.5
#13 0x7fdf4698c1d8 in ?? () from /usr/lib/libQt5Core.so.5
#14 0x7fdf3efb4474 in start_thread () from /usr/lib/libpthread.so.0
#15 0x7fdf4608a69d in clone () from /usr/lib/libc.so.6

Thread 32 (Thread 0x7fdf22e3d700 (LWP 31584)):
#0  0x7fdf3efba09f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7fdf4392e7db in ?? () from /usr/lib/libQt5WebKit.so.5
#2  0x7fdf4392e819 in ?? () from /usr/lib/libQt5WebKit.so.5
#3  0x7fdf3efb4474 in start_thread () from /usr/lib/libpthread.so.0
#4  0x7fdf4608a69d in clone () from /usr/lib/libc.so.6

Thread 31 (Thread 0x7fded9df3700 (LWP 31585)):
#0  0x7ffdbcf72c59 in clock_gettime ()
#1  0x7fdf46097356 in clock_gettime () from /usr/lib/libc.so.6
#2  0x7fdf46a37d96 in ?? () from /usr/lib/libQt5Core.so.5
#3  0x7fdf46bb62f9 in QTimerInfoList::updateCurrentTime() () from
/usr/lib/libQt5Core.so.5
#4  0x7fdf46bb8018 in ?? () from /usr/lib/libQt5Core.so.5
#5  0x7fdf3e791a01 in g_main_context_check () from
/usr/lib/libglib-2.0.so.0
#6  0x7fdf3e791f74 in ?? () from /usr/lib/libglib-2.0.so.0
#7  0x7fdf3e7920ec in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#8  0x7fdf46bb874b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#9  0x7fdf46b604ca in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#10 0x7fdf469872f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#11 0x7fdf4698c1d8 in ?? () from /usr/lib/libQt5Core.so.5
#12 0x7fdf3efb4474 in start_thread () from /usr/lib/libpthread.so.0
#13 0x7fdf4608a69d in clone () from /usr/lib/libc.so.6

Thread 30 (Thread 0x7fded22be700 (LWP 31586)):
#0  0x7fdf3efba09f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7fdf4362dd84 in ?? () from /usr/lib/libQt5WebKit.so.5
#2  0x7fdf4395e481 in ?? () from /usr/lib/libQt5WebKit.so.5
#3  0x7fdf3efb4474 in 

[kmail2] [Bug 363976] New: kmail moans 'die ressource "XXXX" funktioniert nicht' because subdirectories tmp, new and cur are missing

[Dieter Jurzitza via KDE Bugzilla]

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

Bug ID: 363976
   Summary: kmail moans 'die ressource "" funktioniert nicht'
because subdirectories tmp, new and cur are missing
   Product: kmail2
   Version: 4.14.10
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: dieter.jurzi...@t-online.de

I struggled for quite a while analyzing a silly bug. Kmail2 worked but always
said
'Die Ressource "" funktioniert nicht'
on start and on entering arbitrary subfolders of  (say
/var/spool/mail/oscar) because I am using maildir format.
At the end of the day it showed that this message (not very helpful, indeed)
was caused by the fact that subdirectories were missing.
So, there was a directory "trash", but the directories "trash/new", "trash/cur"
and "trash/tmp" were missing. Why aren't they auto - generated - I cannot
imagine anything harmful from them, but an error message (that actually does
not give a pointer to the problem) is misleading and serves for nothing in this
case.
So, I'd suggest to auto-generate those folders if they are missing - and kmail
ought to know what is actually causing the error message so it should be
possible to add the folders at the right position.
Thank you for looking into this
take care




Dieter Jurzitza

Reproducible: Always


Actual Results:  
Error message "Die resource  funktioniert nicht" though it works.

Expected Results:  
Auto - generation of missing subdirectories tmp, cur, new.

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