[kdepim] [Bug 376283] Can't compile kde-apps/kldap-16.12.2:5, kde-apps/kcalcore-16.12.2:5
https://bugs.kde.org/show_bug.cgi?id=376283 --- Comment #5 from Ural--- The update 16.12.2 also failed, until I enabled -fPIC. without PIE with fPIC all compiled fine. Thanks -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 376283] Can't compile kde-apps/kldap-16.12.2:5, kde-apps/kcalcore-16.12.2:5
https://bugs.kde.org/show_bug.cgi?id=376283 Laurent Montelchanged: What|Removed |Added Resolution|--- |UPSTREAM Status|UNCONFIRMED |RESOLVED CC||mon...@kde.org --- Comment #4 from Laurent Montel --- As to gentoo :) It compiles fine here. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 376333] New: KMail crashed while opening on KDE Neon distribution (fresh install)
https://bugs.kde.org/show_bug.cgi?id=376333 Bug ID: 376333 Summary: KMail crashed while opening on KDE Neon distribution (fresh install) Product: kmail2 Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: mhdmath...@gmail.com Target Milestone: --- Application: kmail (5.4.2) Qt Version: 5.7.1 Frameworks Version: 5.30.0 Operating System: Linux 4.4.0-62-generic x86_64 Distribution: KDE neon LTS User Edition 5.8 -- Information about the crash: - What I was doing when the application crashed: After installing KMail and MySQL, KMail crashes every time when opened. - Unusual behavior I noticed: When opening from terminal, these lines printed out: ~$: kmail org.kde.pim.kidentitymanagement: IdentityManager: There was no default identity. Marking first one as default. Could not find QtWebEngineProcess *** KMail got signal 6 (Exiting) *** Dead letters dumped. KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kmail path = /usr/bin pid = 6550 KCrash: Arguments: /usr/bin/kmail KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 QSocketNotifier: Invalid socket 10 and type 'Read', disabling... QSocketNotifier: Invalid socket 19 and type 'Read', disabling... QSocketNotifier: Invalid socket 11 and type 'Read', disabling... [1]+ Stopped kmail ~$: - Custom settings of the application: I haven't changed any setting of the application. Just changed the couple of plasma themes. But I guess that's not the problem. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0335973a00 (LWP 6172))] Thread 5 (Thread 0x7f0329dec700 (LWP 6181)): #0 0x7f0365279b5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f0359cde38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0359cde49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0365daf75b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0365d5a0ba in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0365b89f64 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0365b8eb48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f035ba376ba in start_thread (arg=0x7f0329dec700) at pthread_create.c:333 #8 0x7f036528582d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f032a5ed700 (LWP 6177)): #0 0x7f0365dad3d0 in QTimerInfoList::updateCurrentTime() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f0365dad945 in QTimerInfoList::timerWait(timespec&) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f0365daed0e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f0359cdd91d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f0359cde2bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f0359cde49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f0365daf75b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f0365d5a0ba in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f0365b89f64 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f0365b8eb48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f035ba376ba in start_thread (arg=0x7f032a5ed700) at pthread_create.c:333 #11 0x7f036528582d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f032adee700 (LWP 6176)): #0 0x7f0365279b5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f0359cde38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0359cde49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0365daf75b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0365d5a0ba in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0365b89f64 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0365b8eb48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f035ba376ba in start_thread (arg=0x7f032adee700) at pthread_create.c:333 #8 0x7f036528582d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f032bfff700 (LWP 6175)): #0
[kmail2] [Bug 376309] New: kmail2 locked on imap mails migration (5.4.2)
https://bugs.kde.org/show_bug.cgi?id=376309 Bug ID: 376309 Summary: kmail2 locked on imap mails migration (5.4.2) Product: kmail2 Version: 5.4.1 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: fabio.coa...@gmail.com Target Milestone: --- Kmail locks when moving several emails from local folder to remote IMAP server Scenario: I have several local folders that I want to move to remote imap folders. If I move only some messages (say, < 10-20), the operation is completed. Moving more messages (no exact number though) the process seems to get stuck forever. The progress bar on sx bottom remains open and nothing happens; even waiting for hours does not allow the operation to complete. Please note that looking at the size of messages moved, it would take only some minutes to move them, not hours. One suspect is that at somepoint the network gets slow (I'm trying in some location with poor connectivity), the upload gets hogged and kmail is not able to recover. I'd rather prefer kmail to throw an error, if really is not able to complete the operation, that should be the ideal situation :). In the same network, other mail clients are able to complete a similar operation. (tested thunderbird/mac, outlook/mac-win) Distro: gentoo Kmail: 5.4.2 akonadi 16.12.2 Plasma 5.9.1 Gcc 5.4.0 I can perform tests and give more info, just let me know -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 376156] Deleting messages in IMAP account with server side folders enabled isn't possible
https://bugs.kde.org/show_bug.cgi?id=376156 EGDchanged: What|Removed |Added CC||egd.f...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 376286] New: Add a "Mark as read" button in the new mail notification
https://bugs.kde.org/show_bug.cgi?id=376286 Bug ID: 376286 Summary: Add a "Mark as read" button in the new mail notification Product: kmail2 Version: 5.4.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: tterrani...@gmail.com Target Milestone: --- Now the notification only displays a "Read mail" button. It would be great if we could mark it as read from the notification. -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 376283] Can't compile kde-apps/kldap-16.12.2:5, kde-apps/kcalcore-16.12.2:5
https://bugs.kde.org/show_bug.cgi?id=376283 --- Comment #3 from Ural--- Created attachment 103951 --> https://bugs.kde.org/attachment.cgi?id=103951=edit kldap build log -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 376283] Can't compile kde-apps/kldap-16.12.2:5, kde-apps/kcalcore-16.12.2:5
https://bugs.kde.org/show_bug.cgi?id=376283 --- Comment #2 from Ural--- Created attachment 103950 --> https://bugs.kde.org/attachment.cgi?id=103950=edit build.log -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #69 from Achim Bohnet--- On Donnerstag, 9. Februar 2017 18:28:10 CET you wrote: > https://bugs.kde.org/show_bug.cgi?id=338658 > > I'm on Gentoo and have kde-apps/libkdepim-16.12.1 installed. There is no > version 5.4.1 available. Don't confuse the KDE Applications Release version with the Program version. It's often the same but not always. kde applications 16.12.1 release contains 5.4.1: Kmail -> Help -> About Kmail, or $ kmail --version kmail2 5.4.1 $ dpkg -l kmail\* | tail -1 ii kmail 4:16.12.1-0neon+16.04+build7 amd64full featured graphical email client Some (most?) PIM maintainers don't want to set the version of their Program to the same version as the KDE Applications Release. IMHO confusing for users. Achim -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.
[kdepim] [Bug 376283] Can't compile kde-apps/kldap-16.12.2:5, kde-apps/kcalcore-16.12.2:5
https://bugs.kde.org/show_bug.cgi?id=376283 --- Comment #1 from Ural--- Created attachment 103949 --> https://bugs.kde.org/attachment.cgi?id=103949=edit build.log -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 376283] New: Can't compile kde-apps/kldap-16.12.2:5, kde-apps/kcalcore-16.12.2:5
https://bugs.kde.org/show_bug.cgi?id=376283 Bug ID: 376283 Summary: Can't compile kde-apps/kldap-16.12.2:5, kde-apps/kcalcore-16.12.2:5 Product: kdepim Version: unspecified Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: uralz...@autistici.org Target Milestone: --- Hi. I received an update on gentoo today, but these 2 packages fails to compile. Attached build.logs Is this bug system is updated? Only 5.4.x version listed as latest. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 362803] Can't change KMail Message List font size with custom font settings.
https://bugs.kde.org/show_bug.cgi?id=362803 --- Comment #14 from Maurice Batey--- Many thanks, Christoph! -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 376275] New: akregator crash while fetching all feeds
https://bugs.kde.org/show_bug.cgi?id=376275 Bug ID: 376275 Summary: akregator crash while fetching all feeds Product: akregator Version: 5.4.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: hemat...@gmx.de Target Milestone: --- Application: akregator (5.4.1) Qt Version: 5.7.1 Frameworks Version: 5.30.0 Operating System: Linux 4.9.8-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: this is a possible duplicate of 375743, but the crash reporting assistant doesn't let me select this bug as a possible duplicate. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5c9cf87940 (LWP 2807))] Thread 25 (Thread 0x7f5bf2239700 (LWP 2969)): #0 0x7f5c91bbb10f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f5c836fa974 in ?? () from /usr/lib64/libQt5Script.so.5 #2 0x7f5c836fa9b9 in ?? () from /usr/lib64/libQt5Script.so.5 #3 0x7f5c91bb5454 in start_thread () from /lib64/libpthread.so.0 #4 0x7f5c98a8337f in clone () from /lib64/libc.so.6 Thread 24 (Thread 0x7f5bf336c700 (LWP 2945)): #0 0x7f5c91bbb10f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f5c876930d9 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f5c87693719 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f5c876938d0 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f5c8769046c in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f5c91bb5454 in start_thread () from /lib64/libpthread.so.0 #6 0x7f5c98a8337f in clone () from /lib64/libc.so.6 Thread 23 (Thread 0x7f5bf3dab700 (LWP 2943)): #0 0x7f5c91bbb10f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f5c87160950 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f5c87149770 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f5c87149afb in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f5c8714577a in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f5c883df79e in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f5c883e1b54 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f5c883e1ba5 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f5c883e1c79 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #9 0x7f5c8767bdba in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #10 0x7f5c87666855 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #11 0x7f5c87693e8a in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #12 0x7f5c8769046c in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #13 0x7f5c91bb5454 in start_thread () from /lib64/libpthread.so.0 #14 0x7f5c98a8337f in clone () from /lib64/libc.so.6 Thread 22 (Thread 0x7f5c3cff9700 (LWP 2931)): #0 0x7f5c993849c9 in std::__atomic_base::compare_exchange_strong (__m2=, __m1=std::memory_order_release, __p2=0x0, __p1=@0x7f5c3cff8a28: 0x1, this=0x22c3320) at /usr/include/c++/6/bits/atomic_base.h:752 #1 std::atomic ::compare_exchange_strong (__m=std::memory_order_release, __p2=0x0, __p1=@0x7f5c3cff8a28: 0x1, this=0x22c3320) at /usr/include/c++/6/atomic:475 #2 QAtomicOps ::testAndSetRelease (currentValue=, newValue=0x0, expectedValue=0x1, _q_value=...) at ../../src/corelib/arch/qatomic_cxx11.h:299 #3 QBasicAtomicPointer::testAndSetRelease (currentValue=, newValue=0x0, expectedValue=, this=0x22c3320) at ../../src/corelib/thread/qbasicatomic.h:261 #4 QBasicMutex::fastTryUnlock (current=, this=0x22c3320) at thread/qmutex.h:92 #5 QMutex::unlock (this=this@entry=0x22c3320) at thread/qmutex.cpp:277 #6 0x7f5c995b0911 in QMutexLocker::unlock (this=) at ../../src/corelib/thread/qmutex.h:147 #7 QMutexLocker::~QMutexLocker (this=, __in_chrg=) at ../../src/corelib/thread/qmutex.h:141 #8 QThreadData::canWaitLocked (this=0x22c32f0) at ../../src/corelib/thread/qthread_p.h:253 #9 postEventSourcePrepare (s=0x7f5bf40012d0, timeout=0x7f5c3cff8ab4) at kernel/qeventdispatcher_glib.cpp:259 #10 0x7f5c8fe79d6d in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #11 0x7f5c8fe7a7ab in ?? () from /usr/lib64/libglib-2.0.so.0 #12 0x7f5c8fe7a99c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #13 0x7f5c995b118b in QEventDispatcherGlib::processEvents (this=0x7f5bf40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #14 0x7f5c9955aaea in QEventLoop::exec (this=this@entry=0x7f5c3cff8c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #15 0x7f5c99388813 in QThread::exec (this=) at thread/qthread.cpp:507 #16 0x7f5c9938d4c8