[kleopatra] [Bug 316306] Kleopatra segfaults when trusting a previously untrusted root certificate
https://bugs.kde.org/show_bug.cgi?id=316306 --- Comment #3 from A. Sala --- In my case, it seems that 4.10.3 (in Kubuntu 13.04) does not segfault, too... however, it does not trust the certificate I tried to trust, so this has been not solved correctly as the expected action (import it on the trusted certificate list) does not yet occur. -- 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
[kleopatra] [Bug 316306] Kleopatra segfaults when trusting a previously untrusted root certificate
https://bugs.kde.org/show_bug.cgi?id=316306 A. Sala changed: What|Removed |Added Severity|crash |normal -- 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 313684] kmail crashes when forwarding email
https://bugs.kde.org/show_bug.cgi?id=313684 A. Sala changed: What|Removed |Added CC||as...@isa.upv.es -- 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 313684] kmail crashes when forwarding email
https://bugs.kde.org/show_bug.cgi?id=313684 --- Comment #2 from A. Sala --- Created attachment 79895 --> https://bugs.kde.org/attachment.cgi?id=79895&action=edit New crash information added by DrKonqi kmail (4.10.3) on KDE Platform 4.10.3 using Qt 4.8.4 - What I was doing when the application crashed: Forwarding a (quite complex) HTML email. -- Backtrace (Reduced): #6 0x7feb158a3037 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #7 0x7feb158a6698 in __GI_abort () at abort.c:90 [...] #9 0x7feb158eca46 in malloc_printerr (ptr=0x7927ba0, str=0x7feb159f3a00 "free(): invalid next size (fast)", action=3) at malloc.c:4902 #10 _int_free (av=, p=0x7927b90, have_lock=0) at malloc.c:3758 #11 0x7feb16a4e145 in free (alignment=8, x=) at ../../include/QtCore/../../src/corelib/tools/qvector.h:99 -- 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 313684] kmail crashes when forwarding email
https://bugs.kde.org/show_bug.cgi?id=313684 --- Comment #3 from A. Sala --- (complement to comment #2) The crack happened on clicking the "forward" button (well, the "adjunto" one in Spanish locale, F keystroke). After log-out and log-in again, forwarding the problematic email did NOT reproduce the 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
[Akonadi] [Bug 315985] Akonadi nepomuk Feeder not detecting nepomukserver on startup
https://bugs.kde.org/show_bug.cgi?id=315985 A. Sala changed: What|Removed |Added CC||as...@isa.upv.es --- Comment #15 from A. Sala --- I have 4.10.3 and Akonadi Nepomuk feeder in Akonadi console is, too "Waiting for Nepomuk Server to start..." whereas actually: asala@pitblau3:~$ ps -e | grep nepo 23346 ?00:00:00 nepomukserver 23350 ?00:00:35 nepomukservices 23478 ?00:00:00 nepomukcontroll 23779 ?00:00:00 akonadi_nepomuk 24033 ?00:00:01 nepomukservices 24037 ?00:00:43 nepomukservices Restarting agent, it did it. So, seems that some 4.10.3 configurations may be still broken. -- 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 315985] Akonadi nepomuk Feeder not detecting nepomukserver on startup
https://bugs.kde.org/show_bug.cgi?id=315985 --- Comment #16 from A. Sala --- Just in case, I came here googling from blank Kmail searches... After the restart thing, imap searches in kmail didn't work, either. -- 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 320140] New: Kmail crash (unknown reason)
https://bugs.kde.org/show_bug.cgi?id=320140 Bug ID: 320140 Summary: Kmail crash (unknown reason) Classification: Unclassified Product: kmail2 Version: 4.10.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: as...@isa.upv.es Application: kmail (4.10.3) KDE Platform Version: 4.10.3 Qt Version: 4.8.4 Operating System: Linux 3.8.0-21-generic x86_64 Distribution: Ubuntu 13.04 -- Information about the crash: - What I was doing when the application crashed: I just searched for an email keyword on a "lot" (8 years of mail, 2 gigabytes) of folders. Worked correctly. Deselected the long list of folders and clicked on my main "inbox". Removed the keyword I was searching for from the search box and voila, crash. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f842cbd9800 (LWP 12386))] Thread 6 (Thread 0x7f8405621700 (LWP 12396)): #0 0x7f8429f6d3cd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f84221c61dc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f84221c66ba in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f840c67e4f6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7f84221e9eb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f8427871f8e in start_thread (arg=0x7f8405621700) at pthread_create.c:311 #6 0x7f8429f79e1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 5 (Thread 0x7f83f63e6700 (LWP 21574)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f841e318585 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f841e3185d9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f8427871f8e in start_thread (arg=0x7f83f63e6700) at pthread_create.c:311 #4 0x7f8429f79e1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 4 (Thread 0x7f83a9cd7700 (LWP 21575)): #0 0x7f84221c34ab in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f84221c589f in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f84221c60fe in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f84221c6304 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f842a908036 in QEventDispatcherGlib::processEvents (this=0x7f83a40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #5 0x7f842a8d838f in QEventLoop::processEvents (this=this@entry=0x7f83a9cd6d50, flags=...) at kernel/qeventloop.cpp:149 #6 0x7f842a8d8618 in QEventLoop::exec (this=this@entry=0x7f83a9cd6d50, flags=...) at kernel/qeventloop.cpp:204 #7 0x7f842a7da410 in QThread::exec (this=this@entry=0x1514d30) at thread/qthread.cpp:542 #8 0x7f842a8b9edf in QInotifyFileSystemWatcherEngine::run (this=0x1514d30) at io/qfilesystemwatcher_inotify.cpp:256 #9 0x7f842a7dcbec in QThreadPrivate::start (arg=0x1514d30) at thread/qthread_unix.cpp:338 #10 0x7f8427871f8e in start_thread (arg=0x7f83a9cd7700) at pthread_create.c:311 #11 0x7f8429f79e1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 3 (Thread 0x7f83a8c47700 (LWP 21576)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f841e05ea09 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f841e346cee in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f8427871f8e in start_thread (arg=0x7f83a8c47700) at pthread_create.c:311 #4 0x7f8429f79e1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 2 (Thread 0x7f83a3d46700 (LWP 24530)): #0 __libc_enable_asynccancel () at ../nptl/sysdeps/unix/sysv/linux/x86_64/cancellation.S:65 #1 0x7f8429f6d3c2 in poll () at ../sysdeps/unix/syscall-template.S:81 #2 0x7f84221c61dc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f84221c6304 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f842a908036 in QEventDispatcherGlib::processEvents (this=0x7f83980008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #5 0x7f842a8d838f in QEventLoop::processEvents (this=this@entry=0x7f83a3d45d80, flags=...) at kernel/qeventloop.cpp:149 #6 0x7f842a8d8618 in QEventLoop::exec (this=this@entry=0x7f83a3d45d80, flags=...) at kernel/qeventloop.cpp:204 #7 0x7f842a7da410 in QThread::exec (this=) at thread/qthread.cpp:542 #8 0x7f842a7dcbec in QThreadPrivate::start (arg=0x13c41d0) at thread/qthread_unix.cpp:338 #9 0x7f8427871f8e in start_thread (arg=0x7f83a3d46700) at pthread_create.c:311 #10 0x7f8429f7
[Bug 312532] New: KMail crashed when creating a new folder (3rd level) on a maildir structure.
https://bugs.kde.org/show_bug.cgi?id=312532 Bug ID: 312532 Summary: KMail crashed when creating a new folder (3rd level) on a maildir structure. Classification: Unclassified Product: kmail2 Version: 4.9.4 Hardware: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: as...@isa.upv.es Application: kmail (4.9.4) KDE Platform Version: 4.9.4 Qt Version: 4.8.3 Operating System: Linux 3.5.0-21-generic x86_64 Distribution: Ubuntu 12.10 -- Information about the crash: - What I was doing when the application crashed: Creating a new folder entitled 2012 in LocalFolders/Archive. After confirming the name, Kmail crashed. Restarting Kmail showed the folder actually existed. Creating further subdirectories after restarting LocalFolders/Archive/2012/Sent, etc. did no longer crash Kmail. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f85c874b7c0 (LWP 5608))] Thread 5 (Thread 0x7f85be767700 (LWP 5609)): #0 0x7f85ded8e303 in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f85d723ad84 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f85d723b1e2 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f85c56c34a6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7f85d725e645 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f85dc64de9a in start_thread (arg=0x7f85be767700) at pthread_create.c:308 #6 0x7f85ded99cbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #7 0x in ?? () Thread 4 (Thread 0x7f85af994700 (LWP 5933)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f85d3950b2d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f85d3950c39 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f85dc64de9a in start_thread (arg=0x7f85af994700) at pthread_create.c:308 #4 0x7f85ded99cbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 3 (Thread 0x7f85af093700 (LWP 5934)): #0 0x7f85ded8c8bd in read () at ../sysdeps/unix/syscall-template.S:82 #1 0x7f85d727715f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f85d723a914 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f85d723ad22 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f85d723aea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f85df724c16 in QEventDispatcherGlib::processEvents (this=0x7f85a80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x7f85df6f52bf in QEventLoop::processEvents (this=this@entry=0x7f85af092dc0, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f85df6f5548 in QEventLoop::exec (this=0x7f85af092dc0, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f85df5f6b10 in QThread::exec (this=) at thread/qthread.cpp:501 #9 0x7f85df5f9aec in QThreadPrivate::start (arg=0x15e22f0) at thread/qthread_unix.cpp:338 #10 0x7f85dc64de9a in start_thread (arg=0x7f85af093700) at pthread_create.c:308 #11 0x7f85ded99cbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #12 0x in ?? () Thread 2 (Thread 0x7f85ad951700 (LWP 5943)): #0 0x7f85ded8e303 in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f85d723ad84 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f85d723aea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f85df724c16 in QEventDispatcherGlib::processEvents (this=0x7f859c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f85df6f52bf in QEventLoop::processEvents (this=this@entry=0x7f85ad950d90, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f85df6f5548 in QEventLoop::exec (this=0x7f85ad950d90, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f85df5f6b10 in QThread::exec (this=) at thread/qthread.cpp:501 #7 0x7f85df6d59af in QInotifyFileSystemWatcherEngine::run (this=0x16f5ff0) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7f85df5f9aec in QThreadPrivate::start (arg=0x16f5ff0) at thread/qthread_unix.cpp:338 #9 0x7f85dc64de9a in start_thread (arg=0x7f85ad951700) at pthread_create.c:308 #10 0x7f85ded99cbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 1 (Thread 0x7f85c874b7c0 (LWP 5608)): [KCrash Handler] #6 QSortFilterProxyModelPrivate::updateChildrenMapping (this=this@entry=0x232b620, source_parent=..., parent_mapping=parent_mapping@entry=0x3706fd0, orient
[kmail2] [Bug 295043] openpgp signature of expired key is shown as invalid
https://bugs.kde.org/show_bug.cgi?id=295043 A. Sala changed: What|Removed |Added CC||as...@isa.upv.es --- Comment #2 from A. Sala --- I confirm this occurs also in Kmail 4.9.5, in Ubuntu 12.10. -- 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 64424] More fine grained color coding of GPG/PGP signed messages in KMail (wishlist)
https://bugs.kde.org/show_bug.cgi?id=64424 A. Sala changed: What|Removed |Added CC||as...@isa.upv.es --- Comment #12 from A. Sala --- At least part of these requests still apply to the version of Kmail shipped in KDE 4.9.5, as follows: The issue with "expired signatures" signaled as "bad signature" in red should be, indeed, better handled (at least yellow, or arguably "green" if signature valid when the message was received by Kmail --I guess not "time when sent" because that can be spoofed--). I think this is a "bug" because signed messages before expiration are valid even if the signature later expires. In fact, that is what reporters of bug 295043 think, too. Please update status of either this wishlist and/or the referred bug accordingly. So, apart from the other cases, information on expired signatures should be clearer... I guess "yellow" with extended info such as "warning: public key expired on 2013/02/04, but was valid at the time of message reception". Maybe a similar warning with revocations... -- 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
[kleopatra] [Bug 316306] New: Kleopatra segfaults when trusting a previously untrusted root certificate
https://bugs.kde.org/show_bug.cgi?id=316306 Bug ID: 316306 Summary: Kleopatra segfaults when trusting a previously untrusted root certificate Classification: Unclassified Product: kleopatra Version: 2.1.1 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: as...@isa.upv.es CC: m...@kde.org Application: kleopatra (2.1.1) KDE Platform Version: 4.10.1 Qt Version: 4.8.3 Operating System: Linux 3.5.0-25-generic x86_64 Distribution: Ubuntu 12.10 -- Information about the crash: - What I was doing when the application crashed: I imported all certificates in /usr/share/ca-certificates/mozilla. Nothing was shown... I rebooted and they were shown. Now, the root certificates are untrusted. Selecting one and with right-clicking trying to move it to the trusted root certificates crashes Kleopatra. I tried it with three different crt's and the behaviour is repeated. The crash can be reproduced every time. -- Backtrace: Application: Kleopatra (kleopatra), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc7a64f57c0 (LWP 11636))] Thread 4 (Thread 0x7fc79ec90700 (LWP 11637)): #0 0x7fc7b78a9d2d in read () at ../sysdeps/unix/syscall-template.S:82 #1 0x7fc7b035a15f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc7b031d914 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc7b031dd22 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fc7b031dea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fc7b4ef8c46 in QEventDispatcherGlib::processEvents (this=0x7fc7980008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x7fc7b4ec92ef in QEventLoop::processEvents (this=this@entry=0x7fc79ec8fd90, flags=...) at kernel/qeventloop.cpp:149 #7 0x7fc7b4ec9578 in QEventLoop::exec (this=0x7fc79ec8fd90, flags=...) at kernel/qeventloop.cpp:204 #8 0x7fc7b4dcab40 in QThread::exec (this=) at thread/qthread.cpp:501 #9 0x7fc7b4ea99df in QInotifyFileSystemWatcherEngine::run (this=0x1169570) at io/qfilesystemwatcher_inotify.cpp:248 #10 0x7fc7b4dcdb1c in QThreadPrivate::start (arg=0x1169570) at thread/qthread_unix.cpp:338 #11 0x7fc7b78a2e9a in start_thread (arg=0x7fc79ec90700) at pthread_create.c:308 #12 0x7fc7b4270cbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #13 0x in ?? () Thread 3 (Thread 0x7fc79e48f700 (LWP 11685)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:215 #1 0x7fc7b4dcdfd7 in wait (time=2000, this=0x111d560) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=, mutex=0x116c570, time=2000) at thread/qwaitcondition_unix.cpp:158 #3 0x005b5584 in (anonymous namespace)::ReaderStatusThread::run (this=0x116c560) at ../../kleopatra/smartcard/readerstatus.cpp:543 #4 0x7fc7b4dcdb1c in QThreadPrivate::start (arg=0x116c560) at thread/qthread_unix.cpp:338 #5 0x7fc7b78a2e9a in start_thread (arg=0x7fc79e48f700) at pthread_create.c:308 #6 0x7fc7b4270cbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #7 0x in ?? () Thread 2 (Thread 0x7fc78f750700 (LWP 11702)): #0 0x7fc7b4265303 in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7fc7b031dd84 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc7b031dea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc7b4ef8c46 in QEventDispatcherGlib::processEvents (this=0x7fc7840008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7fc7b4ec92ef in QEventLoop::processEvents (this=this@entry=0x7fc78f74fd90, flags=...) at kernel/qeventloop.cpp:149 #5 0x7fc7b4ec9578 in QEventLoop::exec (this=0x7fc78f74fd90, flags=...) at kernel/qeventloop.cpp:204 #6 0x7fc7b4dcab40 in QThread::exec (this=) at thread/qthread.cpp:501 #7 0x7fc7b4ea99df in QInotifyFileSystemWatcherEngine::run (this=0x15e94d0) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7fc7b4dcdb1c in QThreadPrivate::start (arg=0x15e94d0) at thread/qthread_unix.cpp:338 #9 0x7fc7b78a2e9a in start_thread (arg=0x7fc78f750700) at pthread_create.c:308 #10 0x7fc7b4270cbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 1 (Thread 0x7fc7a64f57c0 (LWP 11636)): [KCrash Handler] #6 QSortFilterProxyModelPrivate::updateChildrenMapping (this=this@entry=0x1508c90, source_parent=..., parent_mapping=parent_mapping@entry=0x150f850, orient=orient@entry=Qt::Vertical, start=start@entry=0, end=end@entry=0, delta_item_count=delta_item_count@entry
[kmail] [Bug 64424] More fine grained color coding of GPG/PGP signed messages in KMail (wishlist)
https://bugs.kde.org/show_bug.cgi?id=64424 --- Comment #13 from A. Sala --- After updating today, the above issue (comment 12) does apply (expired signature flagged in red as "bad") to KDE 4.10.1. So, the wishlist (if anyone is still listening to this old thread), is still valid as of KDE 4.10. -- 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 295043] openpgp signature of expired key is shown as invalid
https://bugs.kde.org/show_bug.cgi?id=295043 --- Comment #3 from A. Sala --- And in Kmail shipped with KDE 4.10.1, 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
[kmail2] [Bug 64424] More fine grained color coding of GPG/PGP signed messages in KMail (wishlist)
https://bugs.kde.org/show_bug.cgi?id=64424 --- Comment #15 from A. Sala --- (in reply to comment #14) Well, I think that one thing is the "bug" which is well detailed in 295043: a signature "neither expired, nor revoked" at "the time of Kmail receiving 1st time the message" should be "valid", according to the trust of the signature. So, indeed, that is a BUG: a valid signature is flagged as invalid by Kmail. In fact, 295043 is a duplicate of 59626: this issue is hanging around since __2003__, wow!!! So, then, a different issue is how do deal with that bug in the user interface. Of course, it will be up to the developer which fixes the bug, and maybe he will think on an easier/different solution as the proposed here. Thus, this "bug 64424" (wishlist for user interface) suggests to give by default additional information such as different colour for two possible issues "valid at the time of reception, but now expired", "valid at the time of reception, but now revoked", which combined with the original trust level might make the user think about double-checking. So, in general, I think that they are not "exactly" the same: 295403 requires correcting the bug in whatever way kde developers think of. 64424 suggests how to do it via potential further information in the user interface that would fix the bug and provide more accurate info to the user. So, I guess that bug 295403 should be marked as a "subset" of this one, similarly to bug 59626. To summarise my interpretation of 64424 whishlist: Kmail2 provides NOW different colours for a- openpgp encrypted b- openpgp signed valid trusted c- openpgp signed valid untrusted d- openpgp signed cannot check validity e- openpgp wrong signature although default for c,d are the same (yellow). Bug 295403 says that some messages are wrongly flagged as "e". I aggree. This "wishlist" suggests a new set of status variables and associated colours and text in Kmail message display, at least consisting of: a- openpgp encrypted b- openpgp valid signature ultimately trusted (green default) c- openpgp valid signature untrusted (even c1, c2... for several trust levels? too complicated maybe) (yellow default) d- openpgp signed cannot check validity (yellow default) e- openpgp valid when received, now expired (might be green by default: expired without revocation doesn't raise any particular suspicion) f- openpgp valid when received, revoked at a later date (might be red/orange by default... revoked signatures must raise suspicion, but the Kmail _text_ info must not be the same as "g") g- openpgp bad signature Disclaimer: I am neither a crypto expert at all, nor a software developer... I'm a plain end user playing with gpg signatures "just to learn", and I am not knowledgeable on the policies for setting kde bug status... so others will be able to make better suggestions and do the right "fusion" between this and 295403... but somebody might have a look at this 10-year-old pending thing... -- 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 318906] New: KMail replies by default to "sender" instead of "From" in distribution lists: unintended list spamming frequent
https://bugs.kde.org/show_bug.cgi?id=318906 Bug ID: 318906 Summary: KMail replies by default to "sender" instead of "From" in distribution lists: unintended list spamming frequent Classification: Unclassified Product: kmail2 Version: 4.10.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: as...@isa.upv.es When receiving mails from a distribution list, the field "sender" is usually the list server agent. However, the field "From" is the actual submitter of the message. To avoid abusing the list, the default reply should be reply to the "From" address. Reproducible: Always Steps to Reproduce: 1. Select a list message in the inbox 2. Press "R" or select "Reply" Actual Results: Actual behaviour: Default Reply replies to the whole list (wrong, in my opinion). Reply to Author, Reply All: correct behaviour. Expected Results: Expected behaviour: 1. "Reply" action opens composer window with "TO:" extracted from "From:" field in original message (same default as "reply to author"). [Or, perhaps, a dialog reply to list or reply to author?] ... Other Clients do like this (Dynamic Mail webmail). Here you have a message header causing this behaviour. Return-Path: Received: from smtpx.upv.es (smtpxv.cc.upv.es [158.42.249.46]) by acentauri.cc.upv.es (Cyrus v2.3.16-Invoca-RPM-2.3.16-4) with LMTPA; Thu, 25 Apr 2013 09:46:13 +0200 X-Sieve: CMU Sieve 2.3 Received: from mx.upv.es (mx4.cc.upv.es [158.42.250.194]) by smtpx.upv.es (8.14.3/8.14.3) with ESMTP id r3P7kDib027685; Thu, 25 Apr 2013 09:46:13 +0200 Received: from mail2.dit.upm.es (lists.dit.upm.es [138.4.2.25]) by mx.upv.es (8.14.3/8.14.3) with ESMTP id r3P7k5mU016662 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 25 Apr 2013 09:46:10 +0200 Received: from mail2.dit.upm.es (localhost.localdomain [127.0.0.1]) by mail2.dit.upm.es (8.14.2/8.14.2) with ESMTP id r3P7ckPs010640; Thu, 25 Apr 2013 09:38:51 +0200 Received: from mail.dit.upm.es (mail.dit.upm.es [IPv6:2001:720:1500:42:215:c5ff:fef6:86e4]) by mail2.dit.upm.es (8.14.2/8.14.2) with ESMTP id r3P7cjgn010637 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 25 Apr 2013 09:38:45 +0200 Received: from relay.dit.upm.es (relay.dit.upm.es [IPv6:2001:720:1500:42:21d:9ff:fef0:9725]) by mail.dit.upm.es (8.14.2/8.14.2) with ESMTP id r3P7cjHo006890 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 25 Apr 2013 09:38:45 +0200 Received: from relay.upm.es (euclides.ccupm.upm.es [138.100.198.17]) by relay.dit.upm.es (8.14.2/8.14.2) with ESMTP id r3P7ccuU017317 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 25 Apr 2013 09:38:38 +0200 Received: from smtpsalv.upv.es (smtpsal1.cc.upv.es [158.42.249.61]) by relay.upm.es (8.14.3/8.14.3/euclides-002) with ESMTP id r3P7cX5u016856 for ; Thu, 25 Apr 2013 09:38:38 +0200 Authentication-Results: relay.upm.es; dkim=pass (2048-bit key) header.i=@upv.es; dkim-adsp=temperror Received: from smtpx.upv.es (smtpxv.cc.upv.es [158.42.249.46]) by smtpsalv.upv.es (8.14.4/8.14.4) with ESMTP id r3P7cIJx024846 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 25 Apr 2013 09:38:18 +0200 Received: from smtp.upv.es (celaeno.cc.upv.es [158.42.249.55]) by smtpx.upv.es (8.14.3/8.14.3) with ESMTP id r3P7cI83021736 for ; Thu, 25 Apr 2013 09:38:18 +0200 Received: from localhost (wm2.cc.upv.es [158.42.249.57]) by smtp.upv.es (8.13.6/8.13.6) with ESMTP id r3P7cHTo015968 for ; Thu, 25 Apr 2013 09:38:17 +0200 Received: from cpohimac01.isa.upv.es (cpohimac01.isa.upv.es [158.42.16.26]) by webmail.upv.es (Horde Framework) with HTTP; Thu, 25 Apr 2013 09:38:17 +0200 Message-ID: <20130425093817.35761zz7up8oo...@webmail.upv.es> Date: Thu, 25 Apr 2013 09:38:17 +0200 From: Francesc Xavier Blasco Ferragud To: "automat...@dit.upm.es" MIME-Version: 1.0 Content-Disposition: inline User-Agent: Dynamic Internet Messaging Program (DIMP) H3 (1.1.6) Received-SPF: Pass (relay.upm.es: domain of xbla...@isa.upv.es designates 158.42.249.61 as permitted sender) receiver=relay.upm.es; client-ip=158.42.249.61; envelope-from=; helo=smtpsalv.upv.es; X-SpamDIT-Info: -2.596 () AWL, BAYES_00, SPF_HELO_PASS - changed by relay.dit.upm.es X-SpamDIT-Flag: NO X-Scanned-By: MIMEDefang 2.65 on 138.4.2.15 Subject: [Automatica] =?iso-8859-1?q?Inscripci=F3n_en_la_II_Jornada_conexi?= =?iso-8859-1?q?=F3n_Universidad_Industria_en_Ingenier=EDa_de_Control?= X-BeenThere: automat...@dit.upm.es X-Mailman-Version: 2.1.9 Precedence: list List-Id: Socios del CEA List-Unsubscribe:
[Bug 297858] KMail crashes when moving a folder
https://bugs.kde.org/show_bug.cgi?id=297858 A. Sala changed: What|Removed |Added CC||as...@isa.upv.es -- 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
[Bug 297858] KMail crashes when moving a folder
https://bugs.kde.org/show_bug.cgi?id=297858 --- Comment #3 from A. Sala --- Created attachment 70826 --> https://bugs.kde.org/attachment.cgi?id=70826&action=edit New crash information added by DrKonqi kmail (4.8.2) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1 - What I was doing when the application crashed: Under KMail 4.8.2 (from Kubuntu ppa), I was moving a "big" MailDir archive folder (all mail from one year) to another empty folder --I wanted to change the archive folder organization--. Kmail crashed many times during my reorganization, once for each folder movement, basically ... well, maybe one or two out of ten times, it didn't crash. I hope resulting mail is not corrupt (after restarting KMail, the operation seems to have completed successfully)... There was no hint in the user interface that some operations were under way so while waiting for the directories to dissapear from the old location, I continued work in many cases ... -- Backtrace (Reduced): #6 size (this=0x3000310034) at ../../include/QtCore/../../src/corelib/tools/qvector.h:137 #7 QSortFilterProxyModelPrivate::proxy_to_source (this=0x19897c0, proxy_index=...) at itemviews/qsortfilterproxymodel.cpp:370 #8 0x7f07eb910abd in QSortFilterProxyModel::mapToSource (this=, proxyIndex=) at itemviews/qsortfilterproxymodel.cpp:2502 #9 0x7f07eb911d4d in QSortFilterProxyModelPrivate::store_persistent_indexes (this=) at itemviews/qsortfilterproxymodel.cpp:996 #10 0x7f07eb912b73 in QSortFilterProxyModelPrivate::_q_sourceLayoutAboutToBeChanged (this=0x19897c0) at itemviews/qsortfilterproxymodel.cpp:1244 -- 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
[Bug 302223] New: Kmail crashed at startup
https://bugs.kde.org/show_bug.cgi?id=302223 Bug ID: 302223 Severity: crash Version: 4.8.4 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kmail crashed at startup Classification: Unclassified OS: Linux Reporter: as...@isa.upv.es Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kmail2 Application: kmail (4.8.4) KDE Platform Version: 4.8.4 (4.8.4) Qt Version: 4.8.1 Operating System: Linux 3.2.0-25-generic x86_64 Distribution: Ubuntu 12.04 LTS -- Information about the crash: - What I was doing when the application crashed: Starting Kmail 4.8.4 after logging in. Subsequent Kmail starts worked out OK, so this might be a low-priority issue. The crash does not seem to be reproducible. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:39 [Current thread is 1 (Thread 0x7f63091637c0 (LWP 5545))] Thread 7 (Thread 0x7f62e6fc5700 (LWP 5547)): #0 0x7f63064ab0bd in read () at ../sysdeps/unix/syscall-template.S:82 #1 0x7f62fed928cf in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f62fed57ba4 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f62fed57fd6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f62fed5849a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f62e6fca98b in ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so #6 0x7f62fed799e5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f6303f87e9a in start_thread (arg=0x7f62e6fc5700) at pthread_create.c:308 #8 0x7f63064b84bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #9 0x in ?? () Thread 6 (Thread 0x7f62e63b9700 (LWP 5548)): #0 0x7f63064acb03 in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f62fed58036 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f62fed5849a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f62ecf62406 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7f62fed799e5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f6303f87e9a in start_thread (arg=0x7f62e63b9700) at pthread_create.c:308 #6 0x7f63064b84bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #7 0x in ?? () Thread 5 (Thread 0x7f62d705b700 (LWP 5586)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f62fb44bdec in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f62fb44bf19 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f6303f87e9a in start_thread (arg=0x7f62d705b700) at pthread_create.c:308 #4 0x7f63064b84bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 4 (Thread 0x7f62d675a700 (LWP 5587)): #0 0x7f63064acb03 in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f62fed58036 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f62fed58164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6306e43426 in QEventDispatcherGlib::processEvents (this=0x7f62d8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f6306e12c82 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f6306e12ed7 in QEventLoop::exec (this=0x7f62d6759dc0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f6306d11fa7 in QThread::exec (this=) at thread/qthread.cpp:501 #7 0x7f6306d14fcb in QThreadPrivate::start (arg=0xfe0ae0) at thread/qthread_unix.cpp:298 #8 0x7f6303f87e9a in start_thread (arg=0x7f62d675a700) at pthread_create.c:308 #9 0x7f63064b84bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #10 0x in ?? () Thread 3 (Thread 0x7f6289263700 (LWP 5694)): #0 0x7f63064acb03 in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f62fed58036 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f62fed58164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6306e43426 in QEventDispatcherGlib::processEvents (this=0x7f62840008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f6306e12c82 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f6306e12ed7 in QEventLoop::exec (this=0x7f6289262d90, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f6306d11fa7 in QThread::exec (this=) at thread/qthread.cpp:501 #7 0x7f6306df29ff in QInotifyFileSystemWatcherEngine::run (this=0x14ea180) at io/qfilesystemwatcher_ino
