[Akonadi] [Bug 397239] New: crash when searching with kmail

2018-08-07 Thread Martin Koller
https://bugs.kde.org/show_bug.cgi?id=397239

Bug ID: 397239
   Summary: crash when searching with kmail
   Product: Akonadi
   Version: GIT (master)
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: server
  Assignee: kdepim-bugs@kde.org
  Reporter: kol...@aon.at
  Target Milestone: ---

Application: akonadiserver (5.8.90)

Qt Version: 5.11.1
Frameworks Version: 5.48.0
Operating System: Linux 4.4.138-59-default x86_64
Distribution: "openSUSE Leap 42.3"

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

I opened the "find messages" dialog from kmail, selected "Search in all
folders", "Match all of the following" (default), "Complete Message" and
entered my search string and hit "Search", then I got the crash report
assistant tellig me akonadi crashed and kmail opens a dialog showing
"Cannot get search result. Cannot connect to the Akonadi service."

-- Backtrace:
Application: Akonadi Server (akonadiserver), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f048a6c8900 (LWP 25381))]

Thread 33 (Thread 0x7f0451ffb700 (LWP 2164)):
#0  0x7f0486e694a8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0


Thread 9 (Thread 0x7f04767fc700 (LWP 25461)):
[KCrash Handler]
#6  0x7f0487fe4f67 in raise () from /lib64/libc.so.6
#7  0x7f0487fe633a in abort () from /lib64/libc.so.6
#8  0x00643f8e in akMessageHandler (type=QtFatalMsg, context=...,
msg=...) at /home/KDE5/source/kde/pim/akonadi/src/shared/akdebug.cpp:177
#9  0x00646094 in (anonymous namespace)::RemoteLogger::dbusLogger
(type=QtFatalMsg, ctx=..., msg=...) at
/home/KDE5/source/kde/pim/akonadi/src/shared/akremotelog.cpp:178
#10 0x7f04759f4a24 in (anonymous namespace)::RemoteLogger::dbusLogger
(type=QtFatalMsg, ctx=..., msg=...) at
/home/KDE5/source/kde/pim/akonadi/src/shared/akremotelog.cpp:178
#11 0x7f0488c969bf in qt_message_print (message=..., context=...,
msgType=QtFatalMsg) at global/qlogging.cpp:1793
#12 qt_message(QtMsgType, const QMessageLogContext &, const char *, typedef
__va_list_tag __va_list_tag *) (msgType=msgType@entry=QtFatalMsg, context=...,
msg=msg@entry=0x7f0488f10788 "ASSERT: \"%s\" in file %s, line %d",
ap=ap@entry=0x7f04767fa318) at global/qlogging.cpp:365
#13 0x7f0488c7ff04 in QMessageLogger::fatal
(this=this@entry=0x7f04767fa3f0, msg=msg@entry=0x7f0488f10788 "ASSERT: \"%s\"
in file %s, line %d") at global/qlogging.cpp:877
#14 0x7f0488c7f576 in qt_assert (assertion=, file=, line=) at global/qglobal.cpp:3188
#15 0x0042da12 in Akonadi::Server::Connection::self () at
/home/KDE5/source/kde/pim/akonadi/src/server/connection.cpp:82
#16 0x005b086b in
Akonadi::Server::NotificationCollector::completeNotification
(this=0x7f04608d2af0, changeMsg=...) at
/home/KDE5/source/kde/pim/akonadi/src/server/storage/notificationcollector.cpp:545
#17 0x005b026f in
Akonadi::Server::NotificationCollector::dispatchNotification
(this=0x7f04608d2af0, msg=...) at
/home/KDE5/source/kde/pim/akonadi/src/server/storage/notificationcollector.cpp:580
#18 0x005acb1b in
Akonadi::Server::NotificationCollector::itemNotification (this=0x7f04608d2af0,
op=Akonadi::Protocol::ItemChangeNotification::Unlink, items=...,
collection=..., collectionDest=..., resource=..., parts=..., addedFlags=...,
removedFlags=..., addedTags=..., removedTags=..., addedRelations=...,
removedRelations=...) at
/home/KDE5/source/kde/pim/akonadi/src/server/storage/notificationcollector.cpp:373
#19 0x005ad719 in Akonadi::Server::NotificationCollector::itemsUnlinked
(this=0x7f04608d2af0, items=..., collection=...) at
/home/KDE5/source/kde/pim/akonadi/src/server/storage/notificationcollector.cpp:132
#20 0x004bda51 in Akonadi::Server::SearchManager::updateSearchImpl
(this=0x1fb8b80, collection=...) at
/home/KDE5/source/kde/pim/akonadi/src/server/search/searchmanager.cpp:374
#21 0x004bfb07 in
Akonadi::Server::SearchManager::updateSearch(Akonadi::Server::Collection
const&)::$_9::operator()() const (this=0x7f03f81740a0) at
/home/KDE5/source/kde/pim/akonadi/src/server/search/searchmanager.cpp:269
#22 0x004bfac9 in QtPrivate::FunctorCall,
QtPrivate::List<>, void,
Akonadi::Server::SearchManager::updateSearch(Akonadi::Server::Collection
const&)::$_9>::call(Akonadi::Server::SearchManager::updateSearch(Akonadi::Server::Collection
const&)::$_9&, void**) (f=..., arg=0x7f040f7fc530) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:128
#23 0x004bfaa1 in
QtPrivate::Functor::call,
void>(Akonadi::Server::SearchManager::updateSearch(Akonadi::Server::Collection
const&)::$_9&, void*, void**) (f=..., arg=0x7f040f7fc530) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:238
#24 0x004bf9dd in
QtPrivate::QFunctorSlotObject, void>::impl(int,

[kaddressbook] [Bug 397233] kaddressbook 5.8.80 beta1 presets the category filter with something unusable on start

2018-08-07 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=397233

Laurent Montel  changed:

   What|Removed |Added

 CC||mon...@kde.org
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Laurent Montel  ---
fixed in 5.9.0

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

[kaddressbook] [Bug 397233] New: kaddressbook 5.8.80 beta1 presets the category filter with something unusable on start

2018-08-07 Thread Mathias Homann
https://bugs.kde.org/show_bug.cgi?id=397233

Bug ID: 397233
   Summary: kaddressbook 5.8.80 beta1 presets the category filter
with something unusable on start
   Product: kaddressbook
   Version: GIT
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: mathias.hom...@opensuse.org
CC: to...@kde.org
  Target Milestone: ---

When i start kontact or kaddressbook "standalone", the category filter always
is preset to something that does not even exist as a category in my address
book, therefor making the list of addresses appear empty.

Workaround: click the "clear category filter" button, which sets the filter to
"All".

It seems that the list of categories got populated from the categories in my
CALENDAR, it contains a lot og categories that I used in calendar entries, but
never for addresses

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