[akregator] [Bug 383404] The content pane does not respect the Breeze dark theme
https://bugs.kde.org/show_bug.cgi?id=383404 Manu changed: What|Removed |Added CC||manuavazq...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 383686] akregator causing desktop effects restart
https://bugs.kde.org/show_bug.cgi?id=383686 Manu changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 383686] akregator causing desktop effects restart
https://bugs.kde.org/show_bug.cgi?id=383686 --- Comment #4 from Manu --- No, I cannot reproduce it anymore. I had already completely forgotten about this :) Cheers. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 422580] Kmail crashes when trying to reply an empty mail with a docx attached
https://bugs.kde.org/show_bug.cgi?id=422580 --- Comment #2 from Manu --- I just tried to create one but I wasn't able to: I sent myself the same file which was sent to me and crashed Kmail on reply...but it's not crashing Kmail when it's coming from me :-/ When I compare the file received from myself and that received from someone else, in the latter case the vertical color bar next to the attachment is orange, whereas in the former it's green, but I don't know the meaning of that (spam-related?). About sending the file, it's not an option since it contains private stuff...sorry, but anyway it doesn't seem the file is enough to reproduce the problem. If you can think of something I could try, I will give it a shot. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 422580] New: Kmail crashes when trying to reply an empty mail with a docx attached
https://bugs.kde.org/show_bug.cgi?id=422580 Bug ID: 422580 Summary: Kmail crashes when trying to reply an empty mail with a docx attached Product: kmail2 Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: manuavazq...@gmail.com Target Milestone: --- Application: kmail (5.13.3 (19.12.3)) (Compiled from sources) Qt Version: 5.14.2 Frameworks Version: 5.70.0 Operating System: Linux 5.4.38-gentoo x86_64 Windowing system: X11 Distribution: "Gentoo Base System release 2.6" -- Information about the crash: - What I was doing when the application crashed: I press the button to reply an e-mail - Custom settings of the application: Nothing out of the standar. The only thing, I'm just using Noto fonts with size 12 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 0x7f99bc203ac0 (LWP 181205))] Thread 25 (Thread 0x7f993abfe700 (LWP 181370)): #0 0x7f99cb86b95a in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f99c4823936 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7cab in () #3 0x27a13837 in () #4 0x7c8a in () #5 0x27a13c1f in () #6 0x in () Thread 24 (Thread 0x7f993b3ff700 (LWP 181369)): #0 0x7f99cb86b95a in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f99c4823936 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7cac in () #3 0x23710936 in () #4 0x7c8b in () #5 0x23710d1e in () #6 0x in () Thread 23 (Thread 0x7f3a5700 (LWP 181368)): #0 0x7f99cb86b95a in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f99c4823936 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7cab in () #3 0x27a0c831 in () #4 0x7c8a in () #5 0x27a0c831 in () #6 0x in () Thread 22 (Thread 0x7f9983fff700 (LWP 181367)): #0 0x7f99cb86b95a in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f99c4823936 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7cab in () #3 0x29bae94b in () #4 0x7c8a in () #5 0x29baed33 in () #6 0x in () Thread 21 (Thread 0x7f99837fe700 (LWP 181366)): #0 0x7f99cb86b95a in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f99c4823936 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7cab in () #3 0x2842b79e in () #4 0x7c8a in () #5 0x2842b79e in () #6 0x in () Thread 20 (Thread 0x7f9948d7d700 (LWP 181265)): #0 0x7f99cdfa204f in write () at /lib64/libc.so.6 #1 0x7f99cdf33d05 in _IO_file_write () at /lib64/libc.so.6 #2 0x7f99cdf33096 in () at /lib64/libc.so.6 #3 0x7f99cdf34406 in _IO_file_xsputn () at /lib64/libc.so.6 #4 0x7f99cdf20548 in () at /lib64/libc.so.6 #5 0x7f99cdf1d5f4 in () at /lib64/libc.so.6 #6 0x7f99cdfbef37 in __fprintf_chk () at /lib64/libc.so.6 #7 0x7f99bf06af96 in () at /usr/lib64/libevent-2.1.so.7 #8 0x7f99bf06b1bd in event_warn () at /usr/lib64/libevent-2.1.so.7 #9 0x7f99bf06c958 in () at /usr/lib64/libevent-2.1.so.7 #10 0x7f99bf062769 in event_base_loop () at /usr/lib64/libevent-2.1.so.7 #11 0x7f99c482ae4e in () at /usr/lib64/libQt5WebEngineCore.so.5 #12 0x0001005b006e in () #13 0x7f9948d7c950 in () #14 0x7f9948d7c948 in () #15 0x in () Thread 19 (Thread 0x7f994a87e700 (LWP 181262)): #0 0x7f99cdfa657f in poll () at /lib64/libc.so.6 #1 0x7f99cae4b3ee in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f99cae4b50f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f99ce5b38db in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f99ce55e3db in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f99ce3b246e in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f99ce3b349b in () at /usr/lib64/libQt5Core.so.5 #7 0x7f99cb864fa7 in start_thread () at /lib64/libpthread.so.0 #8 0x7f99cdfb0dbf in clone () at /lib64/libc.so.6 Thread 18 (Thread 0x7f994b7ff700 (LWP 181249)): #0 0x7f99cb86b635 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f99c482383c in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x in () Thread 17 (Thread 0x7f996e7fc700 (LWP 181245)): #0 0x7f99cb86b635 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpt
[kmail2] [Bug 413318] New: Kmail crashes when trying to reply an empty e-mail with a (pdf) file attached
https://bugs.kde.org/show_bug.cgi?id=413318 Bug ID: 413318 Summary: Kmail crashes when trying to reply an empty e-mail with a (pdf) file attached Product: kmail2 Version: 5.11.3 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: manuavazq...@gmail.com Target Milestone: --- Application: kmail (5.11.3) (Compiled from sources) Qt Version: 5.12.5 Frameworks Version: 5.60.0 Operating System: Linux 4.19.72-gentoo x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: I opened an e-mail that was empty except for an attached pdf. I pressed "Reply" in the toolbar, and Kmail crashed. 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 0x7f4968058a40 (LWP 8140))] Thread 26 (Thread 0x7f48f0e92700 (LWP 8205)): #0 0x7f497793310c in pthread_cond_wait () at /lib64/libpthread.so.0 #1 0x7f496dcc573a in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /usr/lib64/libQt5Script.so.5 #2 0x7f496dcc5759 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f497792c408 in start_thread () at /lib64/libpthread.so.0 #4 0x7f4979fa2f4f in clone () at /lib64/libc.so.6 Thread 25 (Thread 0x7f48f1aff700 (LWP 8192)): #0 0x7f4979f92800 in read () at /lib64/libc.so.6 #1 0x7f4976f83f50 in g_wakeup_acknowledge () at /usr/lib64/libglib-2.0.so.0 #2 0x7f4976f3d22f in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f4976f3d700 in g_main_context_iterate.isra () at /usr/lib64/libglib-2.0.so.0 #4 0x7f4976f3d87c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f497a50b44b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f497a4b951b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f497a32c106 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f497a32d322 in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #9 0x7f497792c408 in start_thread () at /lib64/libpthread.so.0 #10 0x7f4979fa2f4f in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7f48f2448700 (LWP 8189)): #0 0x7f49779334f9 in pthread_cond_timedwait () at /lib64/libpthread.so.0 #1 0x7f4970dea2f7 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f4970deacaa in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f4970dead92 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f4970e003f1 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f4970e00bc6 in base::internal::SchedulerWorker::RunWorker() () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f4970e00e94 in base::internal::SchedulerWorker::RunPooledWorker() () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f4970dec861 in base::(anonymous namespace)::ThreadFunc(void*) () at /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f497792c408 in start_thread () at /lib64/libpthread.so.0 #9 0x7f4979fa2f4f in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7f48f3fff700 (LWP 8186)): #0 0x7f49779334f9 in pthread_cond_timedwait () at /lib64/libpthread.so.0 #1 0x7f4970dea2f7 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f4970deacaa in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f4970dead92 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f4970e003f1 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f4970e00877 in base::internal::SchedulerWorker::RunWorker() () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f4970e00e94 in base::internal::SchedulerWorker::RunPooledWorker() () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f4970dec861 in base::(anonymous namespace)::ThreadFunc(void*) () at /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f497792c408 in start_thread () at /lib64/libpthread.so.0 #9 0x7f4979fa2f4f in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7f4914ff9700 (LWP 8172)): #0 0x7f497793310c in pthread_cond_wait () at /lib64/libpthread.so.0 #1 0x7f4970dea229 in base::ConditionVariable::Wait() () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f4970deacb8 in base::WaitableEvent::TimedWaitUntil(
[akregator] [Bug 383686] akregator causing desktop effects restart
https://bugs.kde.org/show_bug.cgi?id=383686 --- Comment #1 from Manu --- For what is worth, I just tried with nouveau (1.0.15) and akregator crashes. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 383686] New: akregator causing desktop effects restart
https://bugs.kde.org/show_bug.cgi?id=383686 Bug ID: 383686 Summary: akregator causing desktop effects restart Product: akregator Version: 5.5.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: manuavazq...@gmail.com Target Milestone: --- Hi, I have just updated to kde applications 17.04.3, and now akregator causes desktop effects to restart (I just need to start akregator and check on 3 or 4 different sources). Well, the pop-up notification says "desktop effects have been restarted", but they are actually gone, and the task bar looks ugly-gray. When this happens, dmesg shows NVRM: Xid (PCI::01:00): 31, Ch 0070, engmask 0101, intr 1000 If I disable "Compositor during startup", everything is fine (but I have no desktop effects). I'm on Gentoo Linux, Qt 5.7.1, KDE Frameworks 5.34, nvidia-drivers-384.59. For what is worth, a Fedora user reported a similar issue https://lists.fedoraproject.org/archives/list/k...@lists.fedoraproject.org/thread/ROYS2NGD2TCGN5YLM7CQOPVN5XCLESP6/ Cheers. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 300648] New: Kmail crashed during log in
https://bugs.kde.org/show_bug.cgi?id=300648 Bug ID: 300648 Severity: crash Version: 4.8.3 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kmail crashed during log in Classification: Unclassified OS: Linux Reporter: manuavazq...@gmail.com Hardware: Compiled Sources Status: UNCONFIRMED Component: general Product: kmail2 Application: kmail (4.8.3) KDE Platform Version: 4.8.3 (4.8.3) (Compiled from sources) Qt Version: 4.8.1 Operating System: Linux 3.2.12-gentoo x86_64 Distribution: "Gentoo Base System release 2.1" -- Information about the crash: - What I was doing when the application crashed: I had just logged in into my KDE sesion and I have Kmail saved in my session -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [Current thread is 1 (Thread 0x7fb258820760 (LWP 3708))] Thread 4 (Thread 0x7fb23e2f1700 (LWP 3792)): #0 0x7fb2539a954c in pthread_cond_wait () from /lib64/libpthread.so.0 #1 0x7fb24a330584 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/qt4/libQtWebKit.so.4 #2 0x7fb2539a4d0c in start_thread () from /lib64/libpthread.so.0 #3 0x7fb255b4564d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fb23d9d8700 (LWP 3793)): #0 0x7fb255b3c8d3 in poll () from /lib64/libc.so.6 #1 0x7fb24e670b84 in g_main_context_iterate.clone.6 () from /usr/lib64/libglib-2.0.so.0 #2 0x7fb24e671041 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fb2564c5176 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/qt4/libQtCore.so.4 #4 0x7fb256494ff2 in QEventLoop::processEvents(QFlags) () from /usr/lib64/qt4/libQtCore.so.4 #5 0x7fb2564952a5 in QEventLoop::exec(QFlags) () from /usr/lib64/qt4/libQtCore.so.4 #6 0x7fb2563930e8 in QThread::exec() () from /usr/lib64/qt4/libQtCore.so.4 #7 0x7fb25639575b in QThreadPrivate::start(void*) () from /usr/lib64/qt4/libQtCore.so.4 #8 0x7fb2539a4d0c in start_thread () from /lib64/libpthread.so.0 #9 0x7fb255b4564d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fb1fc531700 (LWP 3795)): [KCrash Handler] #6 0x7fb256390ea1 in QMutex::lock() () from /usr/lib64/qt4/libQtCore.so.4 #7 0x7fb24ef6fa2c in Soprano::Error::ErrorCache::clearError() const () from /usr/lib64/libsoprano.so.4 #8 0x7fb24ef6ff80 in Soprano::Error::ErrorCache::setError(Soprano::Error::Error const&) const () from /usr/lib64/libsoprano.so.4 #9 0x7fb247896bc1 in Soprano::Client::DBusModel::executeQuery(QString const&, Soprano::Query::QueryLanguage, QString const&) const () from /usr/lib64/libsopranoclient.so.1 #10 0x7fb24ec92a72 in Nepomuk::MainModel::executeQuery(QString const&, Soprano::Query::QueryLanguage, QString const&) const () from /usr/lib64/libnepomuk.so.4 #11 0x7fb24ecb1743 in Nepomuk::Types::EntityPrivate::load() () from /usr/lib64/libnepomuk.so.4 #12 0x7fb24ecb5542 in Nepomuk::Types::ClassPrivate::load() () from /usr/lib64/libnepomuk.so.4 #13 0x7fb24ecb0634 in Nepomuk::Types::EntityPrivate::init() () from /usr/lib64/libnepomuk.so.4 #14 0x7fb24ecb6ba2 in Nepomuk::Types::Class::isSubClassOf(Nepomuk::Types::Class const&) () from /usr/lib64/libnepomuk.so.4 #15 0x7fb24ec85054 in Nepomuk::ResourceData::loadType(QUrl const&) () from /usr/lib64/libnepomuk.so.4 #16 0x7fb24ec8886d in Nepomuk::ResourceData::load() () from /usr/lib64/libnepomuk.so.4 #17 0x7fb24ec890a6 in Nepomuk::ResourceData::property(QUrl const&) () from /usr/lib64/libnepomuk.so.4 #18 0x7fb24ec9ce23 in Nepomuk::Resource::property(QUrl const&) const () from /usr/lib64/libnepomuk.so.4 #19 0x7fb25206de15 in MessageCore::NepomukResourceRetrieverRunnable::run() () from /usr/lib64/libmessagecore.so.4 #20 0x7fb256389cb0 in QThreadPoolThread::run() () from /usr/lib64/qt4/libQtCore.so.4 #21 0x7fb25639575b in QThreadPrivate::start(void*) () from /usr/lib64/qt4/libQtCore.so.4 #22 0x7fb2539a4d0c in start_thread () from /lib64/libpthread.so.0 #23 0x7fb255b4564d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fb258820760 (LWP 3708)): #0 0x7fb255b3c8d3 in poll () from /lib64/libc.so.6 #1 0x7fb24c6997c0 in socket_do_iteration () from /usr/lib64/libdbus-1.so.3 #2 0x7fb24c6986ad in _dbus_transport_do_iteration () from /usr/lib64/libdbus-1.so.3 #3 0x7fb24c686dd5 in _dbus_connection_do_iteration_unlocked () from /usr/lib64/libdbus-1.so.3 #4 0x7fb24c687d59 in _dbus_connection_block_pending_call () from /usr/lib64/libdbus-1.so.3 #5 0x7fb24c68741e in dbus_connection_send_with_reply_and_block () from /usr/lib64/libdbus-1.so.3 #6 0x7fb253be2d77 in QDBusConnectionPrivate::sendWithReply(QDBusMessage const&, int, int) () from /usr/lib64/qt4/libQtDBus.so.4 #7 0x7fb253bcfe23 in QDBusConnection::call(QDBusMessage const&, QDBus::CallMode, int) const () from /usr/lib64/qt4/libQtD
[Bug 240218] Filter "From" by "is not in address book" does not work anymore
https://bugs.kde.org/show_bug.cgi?id=240218 Manu changed: What|Removed |Added CC||manu2@yahoo.com --- Comment #6 from Manu 2010-12-12 04:49:58 --- Have the exact same issue with Mandriva 2010.1 and that same filter: 0 = "From" "is in address book" the versions are: Kmail 1.13.3 KDE 4.4.3 I have tried to change the address book from vxard file to akonadi format without any sucess (the adress book works, but the filter still pretends none of the emails is coming from an address book person) -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 198561] Kmail crashes after getting stuck loading an imap account / on start [null KIO::Slave::slaveProtocol, KIO::Scheduler::*, KMail::SearchJob::searchCompleteFolder]
https://bugs.kde.org/show_bug.cgi?id=198561 Manu changed: What|Removed |Added CC||emmanuel_legr...@yahoo.fr -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 198561] Kmail crashes after getting stuck loading an imap account / on start [null KIO::Slave::slaveProtocol, KIO::Scheduler::*, KMail::SearchJob::searchCompleteFolder]
https://bugs.kde.org/show_bug.cgi?id=198561 --- Comment #24 from Manu 2010-10-18 14:24:06 --- Created an attachment (id=52649) --> (http://bugs.kde.org/attachment.cgi?id=52649) New crash information added by DrKonqi kmail (1.13.5) on KDE Platform 4.5.1 (KDE 4.5.1) using Qt 4.7.0 - What I was doing when the application crashed: Searching imap (free.fr) mail ; there was first a « wrong caracter search message » as i enter the word « coopérative » (maybe the « é »), then i tried « cooperative » and then Kmail crashes. -- Backtrace (Reduced): #7 QString (this=0x0) at /usr/include/qt4/QtCore/qstring.h:727 #8 KIO::Slave::protocol (this=0x0) at ../../kio/kio/slave.cpp:181 #9 0xb52e85f1 in KIO::SchedulerPrivate::assignJobToSlave (this=0x8b694d0, slave=0x0, job=0x903e498) at ../../kio/kio/scheduler.cpp:1205 #10 0xb52e8721 in KIO::Scheduler::assignJobToSlave (slave=0x0, job=0x903e498) at ../../kio/kio/scheduler.cpp:816 #11 0xb6ec91e3 in KMail::SearchJob::searchCompleteFolder (this=0x9391518) at ../../kmail/searchjob.cpp:95 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 163760] Unrealistic displaying of certificates located on OpenPGP smart cards
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=163760 --- Additional Comments From emerald bluewin ch 2008-06-13 13:49 --- Hi again Mark :o) I don't know here how to initiate a move on the right direction. I agree that, at least at the moment, all these messages are coming from gpg and thus Kleopatra itself cannot influence the smart card management. We could of course simply remove my entry on Kleopatra bugs report system and then start a topic on gpg side. >From the other side, in my opinion it is not necessarily a good idea to assign >(and consequently centralise) all smartcard related tasks to a piece of software that is external to the front-end application. Typically, the smartcard reader initialisation should be made by the front-end itself (what will happen for instance if several front-ends are used simultaneously?). I think pcsc was made to manage this kind of things and I don't really see an advantage adding a new software-layer. Of course scdaemon should still be used but only to treat the smartcard related objects that concerns the certificates, keys and other crypto-objects; so I can imagine that a collaboration between gpg and kleopatra communities may be very helpful, but how to initiate it? What's your point of view? With warmest regards, Manu Favre P.S. I not familiar in working in an open source environment, so if some of proposals seem strange to you, please be understanding :o| [bugs.kde.org quoted mail] ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 163760] New: Unrealistic displaying of certificates located on OpenPGP smart cards
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=163760 Summary: Unrealistic displaying of certificates located on OpenPGP smart cards Product: kleopatra Version: unspecified Platform: unspecified OS/Version: MS Windows Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: emerald bluewin ch Version: 1.9.2-beta (svn-812909, 2008-05-26) (using 4.00.80 (KDE 4.0.80 >= (KDE 4.1 Beta1), compiled sources) Compiler: i586-mingw32msvc-gcc OS:Microsoft Windows (i686) release 5.0 (2000 Professional) There is in my opinion a large range of possible improvements for the way Kleopatra manages smartcards, here are some of my thinkings (to be completed by community): - Add in tabs display a user friendly icon for each certificate. The icon should indicate wether the certificate contains or not a private key and wether the certificated is located on the computer or on the smart card. - Here above mentionned displaying should react dynamically to the insertion of the smart card (i.e. for a certificate xyz stored in a smart card: if smart card present -> display icon of the certificate with smartcard idiom + "private key available", when smart card removed -> display icon of the certificate without smartcard idiom and without "private key available") - PCSC session: At the moment Kleopatra just tries to access to the first available pcsc reader and gives up with error message "card not present" if the first pcsc reader does not contain an OpenPGP compatible smart card. Actually it is possible anyway to specify the reader that must be choosen in gpg.conf but in my opinion this is a bit boring in some cases. Proposal: spool all available pcsc readers and make a "candidate list" of all reader where an OpenPGP smart card is actually inserted, if the candidate list contains only one candidate then automatically select it. If no candidates found -> Error message "no available card". - ? ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 163757] New: Kleopatra self-tests gives unaccurate results
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=163757 Summary: Kleopatra self-tests gives unaccurate results Product: kleopatra Version: unspecified Platform: unspecified OS/Version: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: emerald bluewin ch Version: 1.9.2-beta (svn-812909, 2008-05-26) (using 4.00.80 (KDE 4.0.80 >= (KDE 4.1 Beta1), compiled sources) Compiler: i586-mingw32msvc-gcc OS:Microsoft Windows (i686) release 5.0 (2000 Professional) Running self-test in Kleopatra gives sometimes uncorrect result. As an example, "scdaemon configuration check" is displayed as failed but the use of the daemon runs in deed correctly (encryption, decryption, key genaration and so on) ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
