[kontact] [Bug 418707] New: Kontact crashes on first startup
https://bugs.kde.org/show_bug.cgi?id=418707 Bug ID: 418707 Summary: Kontact crashes on first startup Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: marava...@yahoo.fr Target Milestone: --- Application: kontact (5.13.2 (19.12.2)) Qt Version: 5.14.1 Frameworks Version: 5.67.0 Operating System: Linux 5.5.7-1-default x86_64 Windowing system: X11 Distribution: openSUSE Tumbleweed -- Information about the crash: Kontact crashes on first run after OpenSUSE VM (VirtualBox) installation. The Account Assistant starts nonetheless. 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 0x7f7b47635a80 (LWP 2436))] Thread 24 (Thread 0x7f7aef325700 (LWP 2537)): #0 0x7f7b53c82795 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f7b4de54ddc in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x in ?? () Thread 23 (Thread 0x7f7aefb26700 (LWP 2536)): #0 0x7f7b5620c9c7 in __lll_lock_wait_private () from /lib64/libc.so.6 #1 0x7f7b561f4b2e in buffered_vfprintf () from /lib64/libc.so.6 #2 0x7f7b561f1a44 in __vfprintf_internal () from /lib64/libc.so.6 #3 0x7f7b562945cf in __fprintf_chk () from /lib64/libc.so.6 #4 0x7f7b49ff8f2e in event_logv_ () from /usr/lib64/libevent-2.1.so.7 #5 0x7f7b49ffbb15 in event_warn () from /usr/lib64/libevent-2.1.so.7 #6 0x7f7b49ffd678 in ?? () from /usr/lib64/libevent-2.1.so.7 #7 0x7f7b4a00e086 in event_base_loop () from /usr/lib64/libevent-2.1.so.7 #8 0x7f7b4de5cad6 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #9 0x00010077007c in ?? () #10 0x7f7aefb25990 in ?? () #11 0x7f7aefb25988 in ?? () #12 0x in ?? () Thread 22 (Thread 0x7f7af0327700 (LWP 2508)): #0 0x7f7b5627bacf in poll () from /lib64/libc.so.6 #1 0x7f7b531932fe in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f7b5319341f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f7b54eabc6b in QEventDispatcherGlib::processEvents (this=0x7f7b2df0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f7b54e53bfb in QEventLoop::exec (this=this@entry=0x7f7af0326b20, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #5 0x7f7b54c7e62e in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #6 0x7f7b54c7f6f8 in QThreadPrivate::start (arg=0x558cb330bc60) at thread/qthread_unix.cpp:342 #7 0x7f7b53c7befa in start_thread () from /lib64/libpthread.so.0 #8 0x7f7b562863bf in clone () from /lib64/libc.so.6 Thread 21 (Thread 0x7f7af1538700 (LWP 2505)): #0 0x7f7b562774fc in read () from /lib64/libc.so.6 #1 0x7f7b531da20f in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f7b53192e57 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f7b531932a2 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f7b5319341f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f7b54eabc6b in QEventDispatcherGlib::processEvents (this=0x7f7b24039870, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f7b54e53bfb in QEventLoop::exec (this=this@entry=0x7f7af1537b20, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #7 0x7f7b54c7e62e in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #8 0x7f7b54c7f6f8 in QThreadPrivate::start (arg=0x558cb32e0d90) at thread/qthread_unix.cpp:342 #9 0x7f7b53c7befa in start_thread () from /lib64/libpthread.so.0 #10 0x7f7b562863bf in clone () from /lib64/libc.so.6 Thread 20 (Thread 0x7f7af1d46700 (LWP 2502)): #0 0x7f7b53192df4 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #1 0x7f7b531932a2 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f7b5319341f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f7b54eabc6b in QEventDispatcherGlib::processEvents (this=0x7f7b180020e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f7b54e53bfb in QEventLoop::exec (this=this@entry=0x7f7af1d45b20, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #5 0x7f7b54c7e62e in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #6 0x7f7b54c7f6f8 in QThreadPrivate::start (arg=0x558cb329efc0) at thread/qthread_unix.cpp:342 #7 0x7f7b53c7befa in start_thread () from /lib64/libpthread.so.0 #8 0x7f7b562863bf in clone () from /lib64/libc.so.6 Thread 19 (Thread
[akregator] [Bug 399570] Akregator crashes after clicking on link in an open tab
https://bugs.kde.org/show_bug.cgi?id=399570 Pierre Maraval changed: What|Removed |Added CC||marava...@yahoo.fr -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 390206] Kontact crash on Kmail message search
https://bugs.kde.org/show_bug.cgi?id=390206 --- Comment #2 from Pierre Maraval <marava...@yahoo.fr> --- The "Filter by status" function and the Tag selector both work flawlessly. Only the search typing field causes the crash. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 390206] Kontact crash on Kmail message search
https://bugs.kde.org/show_bug.cgi?id=390206 --- Comment #1 from Pierre Maraval <marava...@yahoo.fr> --- The "Filter by status" function and the Tag selector both work flawlessly. Only the search typing field causes the crash. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 390206] New: Kontact crash on Kmail message search
https://bugs.kde.org/show_bug.cgi?id=390206 Bug ID: 390206 Summary: Kontact crash on Kmail message search Product: kontact Version: 5.5.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: marava...@yahoo.fr Target Milestone: --- Application: kontact (5.5.2) Qt Version: 5.6.2 Frameworks Version: 5.32.0 Operating System: Linux 4.4.104-39-default x86_64 Distribution: "openSUSE Leap 42.3" -- Information about the crash: - What I was doing when the application crashed: Reading mails on Kmail on OpenSUSE Leap 42.3 - Unusual behavior I noticed: Typing into the search field in the message list (of IMAP accounts) and pressing Enter or waiting a little makes Kontact crash. The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5882988780 (LWP 26806))] Thread 24 (Thread 0x7f571b7fe700 (LWP 2148)): #0 0x7f587b389478 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5872b889b2 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f5872b963f6 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f5872b965e6 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f5872b9031e in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f587b384724 in start_thread () at /lib64/libpthread.so.0 #6 0x7f587f3e3c1d in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7f574d628700 (LWP 26875)): #0 0x7f587a76bf25 in g_thread_self () at /usr/lib64/libglib-2.0.so.0 #1 0x7f587a74637c in g_main_context_acquire () at /usr/lib64/libglib-2.0.so.0 #2 0x7f587a7471d5 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f587a74742c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f587fefd1ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f587feaabfb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f587fce5f5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f587fceaa29 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f587b384724 in start_thread () at /lib64/libpthread.so.0 #9 0x7f587f3e3c1d in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7f574f769700 (LWP 26870)): #0 0x7f587b3890cf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5872b925d9 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f5872b92d9d in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f5872b935c0 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f5872b9031e in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f587b384724 in start_thread () at /lib64/libpthread.so.0 #6 0x7f587f3e3c1d in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7f5766cdb700 (LWP 26838)): #0 0x7f587f3db37d in poll () at /lib64/libc.so.6 #1 0x7f587a747314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f587a74742c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f587fefd1ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f587feaabfb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f587fce5f5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f587fceaa29 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f587b384724 in start_thread () at /lib64/libpthread.so.0 #8 0x7f587f3e3c1d in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7f57674dc700 (LWP 26837)): #0 0x7f587f3db37d in poll () at /lib64/libc.so.6 #1 0x7f587a747314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f587a74742c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f587fefd1ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f587feaabfb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f587fce5f5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f587fceaa29 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f587b384724 in start_thread () at /lib64/libpthread.so.0 #8 0x7f587f3e3c1d in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7f576835f700 (LWP 26836)): #0 0x7f587f3d73fd in read () at /lib64/libc.so.6 #1 0x7f587a787750 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f587a746e49 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f587a7472a8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f587a74742c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f587fefd1ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f587feaabfb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7
[korganizer] [Bug 375080] Crash when trying tu use every to-do action and New-Event or New-Journal
https://bugs.kde.org/show_bug.cgi?id=375080 --- Comment #4 from Pierre Maraval <marava...@yahoo.fr> --- Workaround found for Kubuntu 17.04: Update to PIM 16.12.3 (Kontact 5.4.3) by using the backports as described here: http://kubuntu.org/news/kde-pim-update-now-available-for-zesty-zapus-17-04/ Downside: Sorry no backtrace :\ -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 375080] Crash when trying tu use every to-do action and New-Event or New-Journal
https://bugs.kde.org/show_bug.cgi?id=375080 Pierre Maraval <marava...@yahoo.fr> changed: What|Removed |Added CC||marava...@yahoo.fr --- Comment #3 from Pierre Maraval <marava...@yahoo.fr> --- Kubuntu 17.04 Kontact 5.2.3 Steps to reproduce: 1. Open Kontact 2. Go to Calendar 3. Add New Event to remote or local calendar (Crash) 4. Open Kontact again 5. Go to Calendar (Crash) Using Akonadi-console or Kontact Settings one can delete the bugging resource to stop Steps 4 and 5 to lead to a crash. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 324424] i can not select my S/MIME certificate for Email Signature
https://bugs.kde.org/show_bug.cgi?id=324424 Pierre Maraval marava...@yahoo.fr changed: What|Removed |Added CC||marava...@yahoo.fr --- Comment #4 from Pierre Maraval marava...@yahoo.fr --- The List only displays certificates for which you have the private key installed. A direct solution is to install the private key via gpg/gpgsm. I had the same Problem. It turned out the certificate was badly imported in Kleopatra, because Kleopatra, gpg (and gpg2) can't handle pcks#12 cert+key files (so i could only import the certificate via the browser, because exporting the private key was only possible in pk12 format). So I had to convert the certificate-and-privatekey.p12 file to extract the key, which i then installed in gpg. It worked, I didn't even have to import it into Kleopatra. Finally I can send S/MIME mails. But the problem is in Kleopatra and/or gpg. -- 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 324424] i can not select my S/MIME certificate for Email Signature
https://bugs.kde.org/show_bug.cgi?id=324424 --- Comment #5 from Pierre Maraval marava...@yahoo.fr --- And I still don't know why I could select a certificate for encryption (encryption didn't work for me though, but I could select the certificate in the list). -- 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 300142] Kmail can't render a html signature
https://bugs.kde.org/show_bug.cgi?id=300142 Pierre Maraval marava...@yahoo.fr changed: What|Removed |Added CC||marava...@yahoo.fr --- Comment #12 from Pierre Maraval marava...@yahoo.fr --- Same problem on Kubuntu 13.10, Kmail Version 4.11.5. Another aspect of this bug (I think) is that Kmail doesn't digitally sign the html signature correctly (HTML signature with inline images (data:image/gif;base64) ). So the sent signed email is invalid, even for other clients which otherwise can render html signatures in Kmail-sent mails. -- 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
[kmail] [Bug 150875] KMail says it can The signature is valid, but the key's validity is unknown. when that's not true
https://bugs.kde.org/show_bug.cgi?id=150875 Pierre Maraval marava...@yahoo.fr changed: What|Removed |Added CC||marava...@yahoo.fr --- Comment #5 from Pierre Maraval marava...@yahoo.fr --- It only means that you didn't sign the key... I agree it is a bad thing and should be corrected because it incites people to sign each and every key without the Very careful checking signing should require... You can fully trust a sender and/or his/her key without having done a careful footprint checking and signed his/her key. -- 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 182807] Left/middle mouse click always opens link in current tab (e.g. instead of background/external) regardless of setting
https://bugs.kde.org/show_bug.cgi?id=182807 Pierre Maraval marava...@yahoo.fr changed: What|Removed |Added CC||marava...@yahoo.fr --- Comment #20 from Pierre Maraval marava...@yahoo.fr --- Kubuntu 12.04.2 LTS KDE and Akregator 4.8.5 Default Browser rekonq, browser option in Akregator Open with Default browser Akregator doesn't use the right option between Open in new Tab, Open n external Browser, and Open in background Tab Setting both options (left click AND middlemouse) to Open in background Tab makes the middlemouse option work as expected, but the left click opens in external browser. -Options Left click : Open in Tab Middlemouse : Open in Background tab -Result Left click : Open in external browser Middlemouse : Open in new (activated) tab -Options Left click : Open in external browser Middlemouse : Open in Background tab -Result Left click : Open in external browser - OK Middlemouse : Open in new tab -Options Left click : Open in new tab Middlemouse : Open in new tab -Result Left click : Open in external browser Middlemouse : Open in new tab - OK -Options Left click : Open in Background tab Middlemouse : Open in new tab -Result Left click : Open in external browser Middlemouse : Open in new Background tab -This setting brings the most messed up result... -Options Left click : Open in external browser Middlemouse : Open in new tab -Result Left click : Open in external browser -OK Middlemouse : Open in new tab -OK -This one is perfectly OK -Options Left click : Open in external browser Middlemouse : Open in external browser -Result Left click : Open in external browser -OK Middlemouse : Open in external browser -OK -This one is perfectly OK too -- 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
