[kmail2] [Bug 357295] New: Empty dialog on creating new "Maildir" account
https://bugs.kde.org/show_bug.cgi?id=357295 Bug ID: 357295 Summary: Empty dialog on creating new "Maildir" account Product: kmail2 Version: unspecified Platform: Ubuntu Packages URL: http://pix.academ.info/images/img/2015/12/29/f49102dc0 fdf4ca8cb0688cfb93736aa.png OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: f...@neonxp.info In create new account dialog I choosed "Maildir" and in next step I see blank dialog window with only one label "URL:" (like on screenshot). And when I click "Next" button new dialog, with label "Configuring new account", is stuck. Reproducible: Always Steps to Reproduce: 1. Select "Create new account wizzard" 2. Select "Maildir" account type 3. Click "Next" twice Actual Results: I see blank dialog with "Url:" label Expected Results: I think, it shoud give me able to select folder where my maildir located. -- 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 357269] Can't import custom message list aggregation and theme from older config
https://bugs.kde.org/show_bug.cgi?id=357269 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- What do you use to import it ? -- 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
[kdepim] [Bug 357283] kmail tool menu is different if started as standalone application than a kontact part
https://bugs.kde.org/show_bug.cgi?id=357283 Laurent Montel changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kdep ||im/f0ba9da055ace9d91ad1981e ||27a767806ca8c43b --- Comment #3 from Laurent Montel --- Git commit f0ba9da055ace9d91ad1981e27a767806ca8c43b by Montel Laurent. Committed on 29/12/2015 at 06:05. Pushed by mlaurent into branch 'master'. Fix Bug 357283 - kmail tool menu is different if started as standalone application than a kontact part M +1-0kaddressbook/kaddressbookpart.cpp M +2-1kaddressbook/mainwidget.h M +1-0kmail/kmail_part.cpp http://commits.kde.org/kdepim/f0ba9da055ace9d91ad1981e27a767806ca8c43b -- 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
[kdepim] [Bug 357283] kmail tool menu is different if started as standalone application than a kontact part
https://bugs.kde.org/show_bug.cgi?id=357283 --- Comment #2 from Laurent Montel --- Ok when we switch apps menu is not refreshed. Ok I will fix it soon. -- 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
[kdepim] [Bug 357283] kmail tool menu is different if started as standalone application than a kontact part
https://bugs.kde.org/show_bug.cgi?id=357283 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- indeed it's a bug if it doesn't appear in kontact. -- 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 338186] Since updating to the latest Kubuntu packages Kmail is not picking up imap mail.
https://bugs.kde.org/show_bug.cgi?id=338186 --- Comment #92 from Vladislav Vorobiev --- It seems that Christian Mollekopf isn't active. Any Idea how to reasignt this bug to somebody else who can fix it? -- 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 338186] Since updating to the latest Kubuntu packages Kmail is not picking up imap mail.
https://bugs.kde.org/show_bug.cgi?id=338186
--- Comment #91 from Vladislav Vorobiev ---
Why we see Status: RESOLVED FIXED
Version Fixed In:4.14.1
Nothing is fixed, I have here 4.14.10-2 and akonadi-server 1.13.0-8
I't happends every 3 minutes on my PC.
is a known problem with Courier IMAP.
akonadi_imap_resource_11(14518) RetrieveItemsTask::onFinalSelectDone: Server
bug: Your IMAP Server delivered an invalid UIDNEXT value. This is a known
problem with Courier IMAP.
akonadi_imap_resource_32(14536) RetrieveItemsTask::onFinalSelectDone: Server
bug: Your IMAP Server delivered an invalid UIDNEXT value. This is a known
problem with Courier IMAP.
akonadi_imap_resource_30(14532) RetrieveItemsTask::onFinalSelectDone: Server
bug: Your IMAP Server delivered an invalid UIDNEXT value. This is a known
problem with Courier IMAP.
akonadi_imap_resource_26(14523) RetrieveItemsTask::onFinalSelectDone: Server
bug: Your IMAP Server delivered an invalid UIDNEXT value. This is a known
problem with Courier IMAP.
akonadi_imap_resource_35(14540) RetrieveItemsTask::onFinalSelectDone: Server
bug: Your IMAP Server delivered an invalid UIDNEXT value. This is a known
problem with Courier IMAP.
akonadi_imap_resource_11(14518) RetrieveItemsTask::onFinalSelectDone: Server
bug: Your IMAP Server delivered an invalid UIDNEXT value. This is a known
problem with Courier IMAP.
akonadi_imap_resource_25(14522) RetrieveItemsTask::onFinalSelectDone: Server
bug: Your IMAP Server delivered an invalid UIDNEXT value. This is a known
problem with Courier IMAP.
akonadi_imap_resource_30(14532) RetrieveItemsTask::onFinalSelectDone: Server
bug: Your IMAP Server delivered an invalid UIDNEXT value. This is a known
problem with Courier IMAP.
akonadi_imap_resource_26(14523) RetrieveItemsTask::onFinalSelectDone: Server
bug: Your IMAP Server delivered an invalid UIDNEXT value. This is a known
problem with Courier IMAP.
akonadi_imap_resource_11(14518) RetrieveItemsTask::onFinalSelectDone: Server
bug: Your IMAP Server delivered an invalid UIDNEXT value. This is a known
problem with Courier IMAP.
akonadi_imap_resource_25(14522) RetrieveItemsTask::onFinalSelectDone: Server
bug: Your IMAP Server delivered an invalid UIDNEXT value. This is a known
problem with Courier IMAP.
akonadi_imap_resource_26(14523) RetrieveItemsTask::onFinalSelectDone: Server
bug: Your IMAP Server delivered an invalid UIDNEXT value. This is a known
problem with Courier IMAP.
akonadi_imap_resource_11(14518) RetrieveItemsTask::onFinalSelectDone: Server
bug: Your IMAP Server delivered an invalid UIDNEXT value. This is a known
problem with Courier IMAP.
akonadi_imap_resource_25(14522) RetrieveItemsTask::onFinalSelectDone: Server
bug: Your IMAP Server delivered an invalid UIDNEXT value. This is a known
problem with Courier IMAP.
akonadi_imap_resource_26(14523) RetrieveItemsTask::onFinalSelectDone: Server
bug: Your IMAP Server delivered an invalid UIDNEXT value. This is a known
problem with Courier IMAP.
akonadi_imap_resource_11(14518) RetrieveItemsTask::onFinalSelectDone: Server
bug: Your IMAP Server delivered an invalid UIDNEXT value. This is a known
problem with Courier IMAP.
akonadi_imap_resource_25(14522) RetrieveItemsTask::onFinalSelectDone: Server
bug: Your IMAP Server delivered an invalid UIDNEXT value. This is a known
problem with Courier IMAP.
213098 "2377" ""
213099 "2377" ""
akonadi_imap_resource_26(14523) RetrieveItemsTask::onFinalSelectDone: Server
bug: Your IMAP Server delivered an invalid UIDNEXT value. This is a known
problem with Courier IMAP.
akonadi_imap_resource_34(14539) RetrieveItemsTask::onFinalSelectDone: Server
bug: Your IMAP Server delivered an invalid UIDNEXT value. This is a known
problem with Courier IMAP.
continuing
request for item 213275 "19546" failed: "Unable to retrieve item from resource:
Did not receive a reply. Possible causes include: the remote application did
not send a reply, the message bus security policy blocked the reply, the reply
timeout expired, or the network connection was broken."
ItemRetrieverException : Unable to retrieve item from resource: Did not
receive a reply. Possible causes include: the remote application did not send a
reply, the message bus security policy blocked the reply, the reply timeout
expired, or the network connection was broken.
posting retrieval request for item 213251 there are 1 queues and 0 items
in mine
request for item 213251 still pending - waiting
processing retrieval request for item 213251 parts: ("RFC822") of resource:
"akonadi_imap_resource_28"
I fix it with
$ akonadictl stop
$ akonadictl start
every time and i have this probleme more or less progressive about one year.
Currently I think to drop kontact from my system and migrate to
thunderbirth
Kontact is Unusable, this issue is so important and kde-team don't take care to
fix it.
--
You are receiving this mail because:
You are on the CC list for the bug.
___
Kdepim-bugs
[kontact] [Bug 357284] New: kontact5 crash on exit
https://bugs.kde.org/show_bug.cgi?id=357284 Bug ID: 357284 Summary: kontact5 crash on exit Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: fschu...@gymnasium-himmelsthuer.de Application: kontact (5.1) Qt Version: 5.5.1 Operating System: Linux 4.1.13-5-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I exited the kontact5 application. KDE from openSUSE Leap 42.1 The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb459324800 (LWP 5242))] Thread 14 (Thread 0x7fb43b3e1700 (LWP 5243)): #0 0x7fb455fadc1d in poll () at /lib64/libc.so.6 #1 0x7fb44f753422 in () at /usr/lib64/libxcb.so.1 #2 0x7fb44f75500f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7fb43d5313c9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fb4568bc32f in () at /usr/lib64/libQt5Core.so.5 #5 0x7fb44f3300a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7fb455fb604d in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7fb433fff700 (LWP 5244)): #0 0x7fb44f33405f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb453b11733 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fb453b11759 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fb44f3300a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fb455fb604d in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7fb3ef58a700 (LWP 5245)): #0 0x7fb455fadc1d in poll () at /lib64/libc.so.6 #1 0x7fb44eb12e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fb44eb12f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fb456aeed8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fb456a95d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fb4568b761a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fb4568bc32f in () at /usr/lib64/libQt5Core.so.5 #7 0x7fb44f3300a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7fb455fb604d in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7fb3ecba4700 (LWP 5246)): #0 0x7fb44f33405f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb45381d75d in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fb453b40031 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fb44f3300a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fb455fb604d in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7fb3e7fff700 (LWP 5247)): #0 0x7fb44f33405f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb45381e733 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fb453b40031 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fb44f3300a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fb455fb604d in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7fb3d3fff700 (LWP 5250)): #0 0x7fb45696d7c0 in () at /usr/lib64/libQt5Core.so.5 #1 0x7fb456aed3b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #2 0x7fb456aed945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #3 0x7fb456aeeb5e in () at /usr/lib64/libQt5Core.so.5 #4 0x7fb44eb124ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #5 0x7fb44eb12d80 in () at /usr/lib64/libglib-2.0.so.0 #6 0x7fb44eb12f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #7 0x7fb456aeed8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #8 0x7fb456a95d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #9 0x7fb4568b761a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #10 0x7fb4568bc32f in () at /usr/lib64/libQt5Core.so.5 #11 0x7fb44f3300a4 in start_thread () at /lib64/libpthread.so.0 #12 0x7fb455fb604d in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7fb3d2ffd700 (LWP 5254)): #0 0x7fb44eb12931 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #1 0x7fb44eb12df8 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fb44eb12f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fb456aeed8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fb456a95d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fb4568b761a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fb4568bc32f in () at /usr/lib64/libQt5Core.so.5 #7 0x7fb44f3300a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7
[kdepim] [Bug 357283] New: kmail tool menu is different if started as standalone application than a kontact part
https://bugs.kde.org/show_bug.cgi?id=357283 Bug ID: 357283 Summary: kmail tool menu is different if started as standalone application than a kontact part Product: kdepim Version: GIT (master) Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: lftab...@yahoo.es The content of the menu is different if kmail is started as a standalone application or as a kontact component. The following components are different: - Address Book entrie does not appear if started inside kontact, this may be intended - The two wizards: anti-spam wizard and anti-virus wizard only appear if kmail is started as a standalone application and not inside kontact Reproducible: Always Steps to Reproduce: 1.start kmail, check tool menu 2.start kontact with kmail part, check tool menu 3. Actual Results: The tool menus are different Expected Results: At least the anti-spam anti-virus wizard should appear in both cases -- 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 357281] New: the date of a specific feed are completely wrong
https://bugs.kde.org/show_bug.cgi?id=357281 Bug ID: 357281 Summary: the date of a specific feed are completely wrong Product: akregator Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: hast0...@gmail.com Version 5.1 Reproducible: Always Steps to Reproduce: 1. get www.tagesschau.de as rss feed 2. see the items with date 2104 "Nach Flugzeugabsturz: Suche nach Opfern und Ursache".. 3. Actual Results: can not use this feed Expected Results: show the items with correct date -- 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 357277] New: Akregator crashed when opening a link in a news feed
https://bugs.kde.org/show_bug.cgi?id=357277 Bug ID: 357277 Summary: Akregator crashed when opening a link in a news feed 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: mr.min...@blueyonder.co.uk Application: akregator (4.14.10) KDE Platform Version: 4.14.10 Qt Version: 4.8.6 Operating System: Linux 4.1.13-5-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I clicked on a 'Complete Story' link in an article from a Daily Mirror newspaper news feed. 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 0x7f823799a800 (LWP 7315))] Thread 7 (Thread 0x7f820eefa700 (LWP 7342)): #0 0x7f822f64105f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f821b816eb6 in WTF::TCMalloc_PageHeap::scavengerThread() () at /usr/lib64/libQtWebKit.so.4 #2 0x7f821b816ee9 in () at /usr/lib64/libQtWebKit.so.4 #3 0x7f822f63d0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f823447104d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f81cdec6700 (LWP 7343)): #0 0x7fff2b3f9b26 in clock_gettime () #1 0x7f823447dc9d in clock_gettime () at /lib64/libc.so.6 #2 0x7f8235cdf097 in () at /usr/lib64/libQtCore.so.4 #3 0x7f8235dba3e9 in () at /usr/lib64/libQtCore.so.4 #4 0x7f8235db928b in () at /usr/lib64/libQtCore.so.4 #5 0x7f822e8218f1 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #6 0x7f822e821df8 in () at /usr/lib64/libglib-2.0.so.0 #7 0x7f822e821f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #8 0x7f8235db8fde in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #9 0x7f8235d8ad4f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #10 0x7f8235d8b045 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #11 0x7f8235c884df in QThread::exec() () at /usr/lib64/libQtCore.so.4 #12 0x7f8235c8abbf in () at /usr/lib64/libQtCore.so.4 #13 0x7f822f63d0a4 in start_thread () at /lib64/libpthread.so.0 #14 0x7f823447104d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f81cd045700 (LWP 7344)): #0 0x7f822f64105f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f821b589b3d in JSC::BlockAllocator::blockFreeingThreadMain() () at /usr/lib64/libQtWebKit.so.4 #2 0x7f821b83ea06 in WTF::wtfThreadEntryPoint(void*) () at /usr/lib64/libQtWebKit.so.4 #3 0x7f822f63d0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f823447104d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f81c7465700 (LWP 7363)): #0 0x7f822f641408 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f8235c8b084 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQtCore.so.4 #2 0x7f8235c7ebda in () at /usr/lib64/libQtCore.so.4 #3 0x7f8235c8abbf in () at /usr/lib64/libQtCore.so.4 #4 0x7f822f63d0a4 in start_thread () at /lib64/libpthread.so.0 #5 0x7f823447104d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f81c6c64700 (LWP 7364)): #0 0x7f822f641408 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f8235c8b084 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQtCore.so.4 #2 0x7f8235c7ebda in () at /usr/lib64/libQtCore.so.4 #3 0x7f8235c8abbf in () at /usr/lib64/libQtCore.so.4 #4 0x7f822f63d0a4 in start_thread () at /lib64/libpthread.so.0 #5 0x7f823447104d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f81c6463700 (LWP 7365)): #0 0x7f822f641408 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f8235c8b084 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQtCore.so.4 #2 0x7f8235c7ebda in () at /usr/lib64/libQtCore.so.4 #3 0x7f8235c8abbf in () at /usr/lib64/libQtCore.so.4 #4 0x7f822f63d0a4 in start_thread () at /lib64/libpthread.so.0 #5 0x7f823447104d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f823799a800 (LWP 7315)): [KCrash Handler] #6 0x7f821b48d3a7 in QtMIMETypeSniffer::~QtMIMETypeSniffer() () at /usr/lib64/libQtWebKit.so.4 #7 0x7f821a465a5c in WebCore::JSNodeOwner::isReachableFromOpaqueRoots(JSC::Handle, void*, JSC::SlotVisitor&) () at /usr/lib64/libQtWebKit.so.4 #8 0x7f821b588a9a in JSC::WeakBlock::visit(JSC::HeapRootVisitor&) () at /usr/lib64/libQtWebKit.so.4 #9 0x7f821b59633b in JSC::MarkedSpace::visitWeakSets(JSC::HeapRootVisitor&) () at /usr/lib64/libQt
[kmail2] [Bug 357276] kmail and kontact crashes on startup every time
https://bugs.kde.org/show_bug.cgi?id=357276 --- Comment #1 from somnium --- Here are some additonal information about the segfault: Application: KMail (kmail), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7375234840 (LWP 2384))] Thread 8 (Thread 0x7f73535d8700 (LWP 2385)): #0 0x7f73749d118d in poll () from /usr/lib/libc.so.6 #1 0x7f7368093ae2 in ?? () from /usr/lib/libxcb.so.1 #2 0x7f7368095757 in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7f73546e2379 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #4 0x7f73752deb8e in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f736b2684a4 in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f73749da13d in clone () from /usr/lib/libc.so.6 Thread 7 (Thread 0x7f7351790700 (LWP 2386)): #0 0x7f73749d118d in poll () from /usr/lib/libc.so.6 #1 0x7f736ad42fbc in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f736ad430cc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f737551654f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7f73754bd57a in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f73752d9be4 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7f73752deb8e in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7f736b2684a4 in start_thread () from /usr/lib/libpthread.so.0 #8 0x7f73749da13d in clone () from /usr/lib/libc.so.6 Thread 6 (Thread 0x7f7350ec8700 (LWP 2387)): #0 0x7f73749d118d in poll () from /usr/lib/libc.so.6 #1 0x7f736ad42fbc in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f736ad430cc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f737551654f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7f73754bd57a in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f73752d9be4 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7f73752deb8e in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7f736b2684a4 in start_thread () from /usr/lib/libpthread.so.0 #8 0x7f73749da13d in clone () from /usr/lib/libc.so.6 Thread 5 (Thread 0x7f7343fff700 (LWP 2389)): #0 0x7f73749d118d in poll () from /usr/lib/libc.so.6 #1 0x7f736ad42fbc in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f736ad430cc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f737551654f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7f73754bd57a in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f73752d9be4 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7f73752deb8e in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7f736b2684a4 in start_thread () from /usr/lib/libpthread.so.0 #8 0x7f73749da13d in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7f73437fe700 (LWP 2391)): #0 0x7f73749d118d in poll () from /usr/lib/libc.so.6 #1 0x7f736ad42fbc in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f736ad430cc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f737551654f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7f73754bd57a in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f73752d9be4 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7f73752deb8e in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7f736b2684a4 in start_thread () from /usr/lib/libpthread.so.0 #8 0x7f73749da13d in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7f7342ffd700 (LWP 2393)): #0 0x7f73749d118d in poll () from /usr/lib/libc.so.6 #1 0x7f736ad42fbc in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f736ad430cc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f737551654f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7f73754bd57a in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f73752d9be4 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7f73752deb8e in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7f736b2684a4 in start_thread () from /usr/lib/libpthread.so.0 #8 0x7f73749da13d in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7f7341ca8700 (LWP 2396)): #0 0x7f73749d118d in poll () from /usr/lib/libc.so.6 #1 0x7f736ad42fbc in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f736ad430cc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f737551654f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7f73754bd57a in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f73752d9be4 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7f73752deb8e in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7f736b2684a4 in start_thread () from /usr/lib/libpthread.so.0 #8 0x7f73749da13d in
[kmail2] [Bug 357276] New: kmail and kontact crashes on startup every time
https://bugs.kde.org/show_bug.cgi?id=357276 Bug ID: 357276 Summary: kmail and kontact crashes on startup every time Product: kmail2 Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: stam...@stampernet.de I have the newest versions of kde applications and frameworks in Arch Linux: Plasma 5.5.2, KDE Frameworks 5.17.0 and KDE Applications 5.12.0. Kmail and Kontact were crashing at first when i tried to change the Settings or tried to write a new mail. After that kmail and kontact are now crashing on startup every time. I suppose it has something to do with the spell checker and the none standard language, here german. Reproducible: Always Steps to Reproduce: 1. Start kmail or kontact Actual Results: kmail crashes with segfault Expected Results: kmail starts, new mails and settings work Here is the backtrace: *** Error in `kmail': free(): invalid pointer: 0x7f5344b32218 *** === Backtrace: = /usr/lib/libc.so.6(+0x72055)[0x7f5344263055] /usr/lib/libc.so.6(+0x779a6)[0x7f53442689a6] /usr/lib/libc.so.6(+0x7818e)[0x7f534426918e] /usr/lib/libKF5Libkleo.so.5(+0x968bd)[0x7f534113f8bd] /usr/lib/libKF5Libkleo.so.5(+0x9747a)[0x7f534114047a] /usr/lib/libKF5Libkleo.so.5(_ZN4Kleo20CryptoBackendFactory15scanForBackendsEP11QStringList+0xf5)[0x7f53410ff585] /usr/lib/libKF5Libkleo.so.5(_ZN4Kleo20CryptoBackendFactoryC1Ev+0x18e)[0x7f53410fffce] /usr/lib/libKF5Libkleo.so.5(_ZN4Kleo20CryptoBackendFactory8instanceEv+0x35)[0x7f53411000d5] /usr/lib/libkmailprivate.so.5(+0x1ca2a8)[0x7f53466a32a8] /usr/lib/libkmailprivate.so.5(+0x1d2818)[0x7f53466ab818] /usr/lib/libkmailprivate.so.5(+0x1e26c2)[0x7f53466bb6c2] /usr/lib/libkmailprivate.so.5(+0x1e3551)[0x7f53466bc551] /usr/lib/libkmailprivate.so.5(_ZN8KMKernel18recoverDeadLettersEv+0x4cc)[0x7f534659ea2c] kmail(main+0x107e)[0x4040de] /usr/lib/libc.so.6(__libc_start_main+0xf0)[0x7f5344211610] kmail(_start+0x29)[0x404809] === Memory map: 0040-00407000 r-xp fe:00 23629621 /usr/bin/kmail 00606000-00607000 r--p 6000 fe:00 23629621 /usr/bin/kmail 00607000-00608000 rw-p 7000 fe:00 23629621 /usr/bin/kmail 00fe7000-01d96000 rw-p 00:00 0 [heap] 7f52f800-7f52f8021000 rw-p 00:00 0 7f52f8021000-7f52fc00 ---p 00:00 0 7f52fd721000-7f52fd723000 r--p fe:00 23618702 /usr/share/locale/de/LC_MESSAGES/kconfigwidgets5.mo 7f52fd729000-7f52fd72e000 r-xp fe:00 25963103 /usr/lib/qt/plugins/pimcommon/pimcommon_tinyurlengineplugin.so 7f52fd72e000-7f52fd92d000 ---p 5000 fe:00 25963103 /usr/lib/qt/plugins/pimcommon/pimcommon_tinyurlengineplugin.so 7f52fd92d000-7f52fd92e000 r--p 4000 fe:00 25963103 /usr/lib/qt/plugins/pimcommon/pimcommon_tinyurlengineplugin.so 7f52fd92e000-7f52fd92f000 rw-p 5000 fe:00 25963103 /usr/lib/qt/plugins/pimcommon/pimcommon_tinyurlengineplugin.so 7f52fd931000-7f52fd937000 r-xp fe:00 25963104 /usr/lib/qt/plugins/pimcommon/pimcommon_isgdshorturlengineplugin.so 7f52fd937000-7f52fdb36000 ---p 6000 fe:00 25963104 /usr/lib/qt/plugins/pimcommon/pimcommon_isgdshorturlengineplugin.so 7f52fdb36000-7f52fdb37000 r--p 5000 fe:00 25963104 /usr/lib/qt/plugins/pimcommon/pimcommon_isgdshorturlengineplugin.so 7f52fdb37000-7f52fdb38000 rw-p 6000 fe:00 25963104 /usr/lib/qt/plugins/pimcommon/pimcommon_isgdshorturlengineplugin.so 7f52fdb39000-7f52fdb3f000 r-xp fe:00 25963106 /usr/lib/qt/plugins/pimcommon/pimcommon_ur1cashorturlengineplugin.so 7f52fdb3f000-7f52fdd3e000 ---p 6000 fe:00 25963106 /usr/lib/qt/plugins/pimcommon/pimcommon_ur1cashorturlengineplugin.so 7f52fdd3e000-7f52fdd3f000 r--p 5000 fe:00 25963106 /usr/lib/qt/plugins/pimcommon/pimcommon_ur1cashorturlengineplugin.so 7f52fdd3f000-7f52fdd4 rw-p 6000 fe:00 25963106 /usr/lib/qt/plugins/pimcommon/pimcommon_ur1cashorturlengineplugin.so 7f52fdd41000-7f52fdd45000 r-xp
[kmail2] [Bug 357269] New: Can't import custom message list aggregation and theme from older config
https://bugs.kde.org/show_bug.cgi?id=357269 Bug ID: 357269 Summary: Can't import custom message list aggregation and theme from older config Product: kmail2 Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: config dialog Assignee: kdepim-bugs@kde.org Reporter: j-kde_...@joel-hatsch.net Newest kmail version stores its kmail2rc in ~/.config instead of ~/.kde4/share/config Customised message aggregation and theming info were not imported into new config, nor can they be added by manually editing the kmail2rc file Reproducible: Always Steps to Reproduce: 1. export one of the 3 default themes to a file 2. edit that file, copy the theming from the old kmail2rc into it 3. change "Set3" to "Set0" :-) 4. import theme into kmail Actual Results: nothing happens, no error message, no new theme visible Expected Results: new theme available in the list just *any* way of importing data would make me happy :-) kmail 5.1 using KDE Frameworks 5.17.0 Qt 5.5.1 (built against 5.5.1) The xcb windowing system on arch linux -- 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 357266] New: Dangerous design problem for kaddressbook groups in case ~/.local/share/akonadi/ is blown away
https://bugs.kde.org/show_bug.cgi?id=357266 Bug ID: 357266 Summary: Dangerous design problem for kaddressbook groups in case ~/.local/share/akonadi/ is blown away Product: kaddressbook Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: bugh...@gluino.name CC: to...@kde.org Suppose you get a dumbass attack and blow away the Akonadi database in ~/.local/share/akonadi/ On restart, akonadi rebuilds the database. The basic contacts in kaddressbook are all fine. However, the *groups* now contain random contacts (embarrasing if you don't notice and use them without verification) or result in kaddressbook crashing when opened. This might be due to kaddressbook setting up groups using small-int identifiers into the Akonadi database (maybe?) instead of using UUIDs that would make it clear that the original contact entry has just gone away. It should be clear to Akonadi that the group has become dangerously messed up and no longer contain valid references. Safety first etc. P.S. This problem also occurs with the configuration of IMAP accounts (trash/draft/template folders and sending identities) - kmail starts up and does not complain at all but is all messed up underneath instead of insulting the issue with clear error messages. P.S. (The version of "kaddressbook" is "4.14.10.-7" which is not listed in Version (it stops at 4.13.2)??) Reproducible: Always Steps to Reproduce: I will have to reproduce it in actuality, but the steps would be: 1. Destroy ~/.local/share/akonadi/ 2. Restart 3. kaddressbook contacts messed up -- 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 338488] akonadi email-links do not open mail client window
https://bugs.kde.org/show_bug.cgi?id=338488 --- Comment #3 from JHF2442 --- see also https://bugs.kde.org/show_bug.cgi?id=357265 -- 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 357265] New: Unable to open akonadi links (URLs) to emails
https://bugs.kde.org/show_bug.cgi?id=357265 Bug ID: 357265 Summary: Unable to open akonadi links (URLs) to emails Product: Akonadi Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: j-kde_...@joel-hatsch.net CC: kdepim-bugs@kde.org, vkra...@kde.org see also bug https://bugs.kde.org/show_bug.cgi?id=338488 1) drag&drop email into dolphin -> file is created 2) click on the created file 3) destination can't be opened - error message Reproducible: Always Steps to Reproduce: see above Actual Results: when clicking on the file, error message is The file or folder No such collection. does not exist. Expected Results: email opens in kmail see also bug https://bugs.kde.org/show_bug.cgi?id=338488 created item has file name : akonadi:?item=69866&type=message⁄rfc822&parent=53.desktop and content : [Desktop Entry] Icon=unknown Name=akonadi:?item=69866&type=message/rfc822&parent=53 Type=Link URL[$e]=akonadi:?item=69866&type=message/rfc822&parent=53 -- 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 338488] akonadi email-links do not open mail client window
https://bugs.kde.org/show_bug.cgi?id=338488 JHF2442 changed: What|Removed |Added CC||j-kde_...@joel-hatsch.net --- Comment #2 from JHF2442 --- Same here when drag/dropping into dolphin created item has file name : akonadi:?item=69866&type=message⁄rfc822&parent=53.desktop and content : [Desktop Entry] Icon=unknown Name=akonadi:?item=69866&type=message/rfc822&parent=53 Type=Link URL[$e]=akonadi:?item=69866&type=message/rfc822&parent=53 when clicking on the file, error message is The file or folder No such collection. does not exist. Software info (arch linux) : kmail 5.1using KDE Frameworks 5.17.0 Qt 5.5.1 (built against 5.5.1) The xcb windowing system -- 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 357263] New: Crash when opening addressbook entry (group) from kmail
https://bugs.kde.org/show_bug.cgi?id=357263 Bug ID: 357263 Summary: Crash when opening addressbook entry (group) from kmail Product: kaddressbook Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: bugh...@gluino.name CC: to...@kde.org Application: kaddressbook (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 (Platform): Fedora RPMs -- Information about the crash: Opened addressbook group. Kmail displays a dialog saying that it is working Then crashes The addressbook seems to be foobared underneath though; addressbook group has wrong contents (that's why I wanted to open it) -- Backtrace: Application: KAddressBook (kaddressbook), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #6 0x7fc8ee7c39c8 in raise () at /lib64/libc.so.6 #7 0x7fc8ee7c565a in abort () at /lib64/libc.so.6 #8 0x7fc8ef0fdb5d in __gnu_cxx::__verbose_terminate_handler() () at /lib64/libstdc++.so.6 #9 0x7fc8ef0fb9a6 in () at /lib64/libstdc++.so.6 #10 0x7fc8ef0fb9f1 in () at /lib64/libstdc++.so.6 #11 0x7fc8ef0fbc59 in __cxa_rethrow () at /lib64/libstdc++.so.6 #12 0x7fc8ef794cfe in QEventLoop::exec(QFlags) () at /lib64/libQtCore.so.4 #13 0x7fc8ef79a6a9 in QCoreApplication::exec() () at /lib64/libQtCore.so.4 #14 0x00405560 in main () 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 357252] New: Kmail segfault when closing application
https://bugs.kde.org/show_bug.cgi?id=357252 Bug ID: 357252 Summary: Kmail segfault when closing application Product: kmail2 Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: p...@kc.rr.com Application: kmail (5.1) (Compiled from sources) Qt Version: 5.5.1 Operating System: Linux 4.1.13-5-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Close KMail - either by clicking on the close button on using the menu The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8745830940 (LWP 4763))] Thread 10 (Thread 0x7f871d508700 (LWP 4764)): #0 0x7f87428ad25d in poll () at /lib64/libc.so.6 #1 0x7f87354da422 in () at /usr/lib64/libxcb.so.1 #2 0x7f87354dc00f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f8720620ed9 in () at /opt/kde/lib64/libQt5XcbQpa.so.5 #4 0x7f87431b49ff in () at /opt/kde/lib64/libQt5Core.so.5 #5 0x7f87390e54a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f87428b5bad in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7f8716f66700 (LWP 4765)): #0 0x7f8738bc8cc0 in g_main_context_dispatch () at /opt/gnome/lib64/libglib-2.0.so.0 #1 0x7f8738bc9168 in () at /opt/gnome/lib64/libglib-2.0.so.0 #2 0x7f8738bc920c in g_main_context_iteration () at /opt/gnome/lib64/libglib-2.0.so.0 #3 0x7f87433d968b in QEventDispatcherGlib::processEvents(QFlags) () at /opt/kde/lib64/libQt5Core.so.5 #4 0x7f874338373a in QEventLoop::exec(QFlags) () at /opt/kde/lib64/libQt5Core.so.5 #5 0x7f87431afbbc in QThread::exec() () at /opt/kde/lib64/libQt5Core.so.5 #6 0x7f87431b49ff in () at /opt/kde/lib64/libQt5Core.so.5 #7 0x7f87390e54a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7f87428b5bad in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f86fa753700 (LWP 4795)): #0 0x7f87390eb07f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f873334d40b in () at /opt/kde/lib64/libQt5WebKit.so.5 #2 0x7f873334d449 in () at /opt/kde/lib64/libQt5WebKit.so.5 #3 0x7f87390e54a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f87428b5bad in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f86a9178700 (LWP 4805)): #0 0x7f87390eb07f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f873305b7b4 in () at /opt/kde/lib64/libQt5WebKit.so.5 #2 0x7f873337c491 in () at /opt/kde/lib64/libQt5WebKit.so.5 #3 0x7f87390e54a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f87428b5bad in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f86a8977700 (LWP 4806)): #0 0x7f87390eb07f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f873305c7e3 in () at /opt/kde/lib64/libQt5WebKit.so.5 #2 0x7f873337c491 in () at /opt/kde/lib64/libQt5WebKit.so.5 #3 0x7f87390e54a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f87428b5bad in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f86933fe700 (LWP 4811)): #0 0x7f8738c0b329 in g_mutex_lock () at /opt/gnome/lib64/libglib-2.0.so.0 #1 0x7f8738bc8b74 in g_main_context_check () at /opt/gnome/lib64/libglib-2.0.so.0 #2 0x7f8738bc90a8 in () at /opt/gnome/lib64/libglib-2.0.so.0 #3 0x7f8738bc920c in g_main_context_iteration () at /opt/gnome/lib64/libglib-2.0.so.0 #4 0x7f87433d968b in QEventDispatcherGlib::processEvents(QFlags) () at /opt/kde/lib64/libQt5Core.so.5 #5 0x7f874338373a in QEventLoop::exec(QFlags) () at /opt/kde/lib64/libQt5Core.so.5 #6 0x7f87431afbbc in QThread::exec() () at /opt/kde/lib64/libQt5Core.so.5 #7 0x7f87431b49ff in () at /opt/kde/lib64/libQt5Core.so.5 #8 0x7f87390e54a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f87428b5bad in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f868bfff700 (LWP 4820)): #0 0x7f87428a923d in read () at /lib64/libc.so.6 #1 0x7f872aa9bf75 in () at /usr/lib64/tls/libnvidia-tls.so.352.63 #2 0x7f8738c0a040 in () at /opt/gnome/lib64/libglib-2.0.so.0 #3 0x7f8738bc8c0c in g_main_context_check () at /opt/gnome/lib64/libglib-2.0.so.0 #4 0x7f8738bc90a8 in () at /opt/gnome/lib64/libglib-2.0.so.0 #5 0x7f8738bc920c in g_main_context_iteration () at /opt/gnome/lib64/libglib-2.0.so.0 #6 0x7f87433d968b in QEventDispatcherGlib::processEvents(QFlags) () at /opt/kde/lib64/libQt5Core.so.5 #7 0x7f874338373a in QEventLoop::exec(QFlags) () at /opt/kde/lib64/libQt5Core.so.5 #8 0x7f87431afbbc in QThread::exec() () at /opt/kde/lib64/libQt5Core.so.5
[kontact] [Bug 357243] New: Crash during exit
https://bugs.kde.org/show_bug.cgi?id=357243 Bug ID: 357243 Summary: Crash during exit Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ianse...@yahoo.co.uk Application: kontact (4.14.10) KDE Platform Version: 4.14.14 Qt Version: 4.8.7 Operating System: Linux 4.3.3-1-default x86_64 Distribution: "openSUSE Tumbleweed (20151124) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I had read a few emails without opening them (via message pane), updated the details of one contact, went back to email and changed folder to read some more unread emails, noticed there was a duplicate so i deleted it. then selected Exit -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6428e8f900 (LWP 3003))] Thread 4 (Thread 0x7f640a419700 (LWP 3004)): #0 0x7f642029007f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f6425550de6 in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/libQtWebKit.so.4 #2 0x7f6425550e19 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQtWebKit.so.4 #3 0x7f642028a4a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f6426331bdd in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f63c9afe700 (LWP 3005)): #0 0x7f642029007f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f64252ba5e9 in JSC::BlockAllocator::blockFreeingThreadMain() () from /usr/lib64/libQtWebKit.so.4 #2 0x7f64255788f6 in WTF::wtfThreadEntryPoint(void*) () from /usr/lib64/libQtWebKit.so.4 #3 0x7f642028a4a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f6426331bdd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f63b61f6700 (LWP 3053)): #0 0x7f642632924d in poll () from /lib64/libc.so.6 #1 0x7f641fcc1264 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f641fcc136c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f6426b2526e in QEventDispatcherGlib::processEvents (this=0x7f63b8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #4 0x7f6426af53e1 in QEventLoop::processEvents (this=this@entry=0x7f63b61f5ce0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f6426af56f5 in QEventLoop::exec (this=this@entry=0x7f63b61f5ce0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f64269eea59 in QThread::exec (this=) at thread/qthread.cpp:538 #7 0x7f64269f123c in QThreadPrivate::start (arg=0x2719f00) at thread/qthread_unix.cpp:352 #8 0x7f642028a4a4 in start_thread () from /lib64/libpthread.so.0 #9 0x7f6426331bdd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f6428e8f900 (LWP 3003)): [KCrash Handler] #6 operator QItemSelectionModel* (this=) at ../../src/corelib/kernel/qpointer.h:78 #7 QAbstractItemView::selectionModel (this=0x5065676100343932) at itemviews/qabstractitemview.cpp:766 #8 0x7f63bb39bf8c in MailCommon::FolderTreeWidget::selectedCollections (this=) at /usr/src/debug/kdepim-4.14.10/mailcommon/folder/foldertreewidget.cpp:243 #9 0x7f63bba46ca0 in KMMainWidget::updateFolderMenu (this=0x2b4c610) at /usr/src/debug/kdepim-4.14.10/kmail/kmmainwidget.cpp:3928 #10 0x7f63bbb470ca in KMMainWidget::qt_static_metacall (_o=, _c=, _id=, _a=0x7ffd96852c30) at /usr/src/debug/kdepim-4.14.10/build/kmail/moc_kmmainwidget.cpp:461 #11 0x7f6426b09f60 in QMetaObject::activate (sender=0x2b4c850, m=, local_signal_index=, argv=) at kernel/qobject.cpp:3576 #12 0x7f6426b0f973 in QObject::event (this=0x2b4c850, e=) at kernel/qobject.cpp:1262 #13 0x7f642750ef1c in QApplicationPrivate::notify_helper (this=this@entry=0x243c390, receiver=receiver@entry=0x2b4c850, e=e@entry=0x7ffd96853030) at kernel/qapplication.cpp:4565 #14 0x7f64275159ec in QApplication::notify (this=this@entry=0x7ffd96853c50, receiver=receiver@entry=0x2b4c850, e=e@entry=0x7ffd96853030) at kernel/qapplication.cpp:4351 #15 0x7f642824165a in KApplication::notify (this=0x7ffd96853c50, receiver=0x2b4c850, event=0x7ffd96853030) at /usr/src/debug/kdelibs-4.14.14/kdeui/kernel/kapplication.cpp:311 #16 0x7f6426af6a1d in QCoreApplication::notifyInternal (this=0x7ffd96853c50, receiver=0x2b4c850, event=event@entry=0x7ffd96853030) at kernel/qcoreapplication.cpp:955 #17 0x7f6426b275cf in sendEvent (event=0x7ffd96853030, receiver=) at kernel/qcoreapplication.h:231 #18 QTimerInfoList::activateTimers (this=0x2447cf0) at kernel/qeventdispatcher_unix.cpp:636 #19 0x7f6426b248f1 in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:193 #20 0x7f641fcc1097 in g_main_context_dispatch () from /usr/lib64/l
