[kleopatra] [Bug 340144] New: BUG1: Verify signs signed with subkeys fails.
https://bugs.kde.org/show_bug.cgi?id=340144 Bug ID: 340144 Summary: BUG1: Verify signs signed with subkeys fails. Product: kleopatra Version: 2.2.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: jo...@jsp.cat CC: m...@kde.org Dear all, to try it you can use a general PGP key with subkeys. I Sign a file using my key that has a subkeys and it seems to be signed correctly using the correct subkey BUT if I ferify it an error appears: Signed on 2014-10-20 10:27 with unknown certificate 0x6E6CFF09AAE35EE3. The signature is invalid: System error and the 0x6E6CFF09AAE35EE3 is the correct subkey used to Sign it. Regards, Jordi -- 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 340145] New: BUG2: Certity with subkeys fails
https://bugs.kde.org/show_bug.cgi?id=340145 Bug ID: 340145 Summary: BUG2: Certity with subkeys fails Product: kleopatra Version: 2.2.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: jo...@jsp.cat CC: m...@kde.org Dear all, this is related with my BUG1. Always using keys with subkeys. Now the problema is that when I want to certify a certificate using my key that have subkeys this error apperas: Certificate Expires But it is not true because there are a lot of subkeys (the first one are obviously expired, some of them are revoked) and the last one are correct. I am using subkeys created by PGP. Regards, Jordi -- 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 340146] New: IMPROVEMENT1: Manage subkeys
https://bugs.kde.org/show_bug.cgi?id=340146 Bug ID: 340146 Summary: IMPROVEMENT1: Manage subkeys Product: kleopatra Version: 2.2.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: jo...@jsp.cat CC: m...@kde.org Dear all, I think that is necessary to manage subkeys correctly. For security reasons, I think that people should have the primary kay and several subkeys with temporary validation window. In order to create, delete or revoke subkeys that belongs to primary key. this is the usual managment of the keys and a good example is review PGP Desktop in order to manage it efficiently. Kind regards, Jordi -- 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 401078] New: Akregator fails at startup
https://bugs.kde.org/show_bug.cgi?id=401078 Bug ID: 401078 Summary: Akregator fails at startup Product: akregator Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: jpe...@ival.com Target Milestone: --- Application: akregator (5.9.3) Qt Version: 5.11.2 Frameworks Version: 5.51.0 Operating System: Linux 4.19.1-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: starting app in opensuse tumbleweed with recent update. Posible new version of qt The crash can be reproduced every time. -- Backtrace: Application: Akregator (akregator), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa391576a40 (LWP 27167))] Thread 21 (Thread 0x7fa35e7fc700 (LWP 27196)): #0 0x7fa3a4439da4 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #1 0x7fa3a43f2969 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #2 0x7fa3a43f2ef0 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7fa3a43f306c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7fa3a736cadb in QEventDispatcherGlib::processEvents (this=0x7fa30c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #5 0x7fa3a7319adb in QEventLoop::exec (this=this@entry=0x7fa35e7fbb60, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #6 0x7fa3a7168de6 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #7 0x7fa3a71729b7 in QThreadPrivate::start (arg=0x55998500fb40) at thread/qthread_unix.cpp:367 #8 0x7fa3a5671554 in start_thread () from /lib64/libpthread.so.0 #9 0x7fa3a6c51ccf in clone () from /lib64/libc.so.6 Thread 20 (Thread 0x7fa35effd700 (LWP 27195)): #0 0x7fa3a6c5f026 in pthread_mutex_unlock () from /lib64/libc.so.6 #1 0x7fa39635792e in pa_mutex_unlock () from /usr/lib64/pulseaudio/libpulsecommon-12.2.so #2 0x7fa39a9389a3 in ?? () from /usr/lib64/libpulse.so.0 #3 0x7fa39a92a1e0 in pa_mainloop_poll () from /usr/lib64/libpulse.so.0 #4 0x7fa39a92a82e in pa_mainloop_iterate () from /usr/lib64/libpulse.so.0 #5 0x7fa39a92a8e0 in pa_mainloop_run () from /usr/lib64/libpulse.so.0 #6 0x7fa39a9388f9 in ?? () from /usr/lib64/libpulse.so.0 #7 0x7fa396358658 in ?? () from /usr/lib64/pulseaudio/libpulsecommon-12.2.so #8 0x7fa3a5671554 in start_thread () from /lib64/libpthread.so.0 #9 0x7fa3a6c51ccf in clone () from /lib64/libc.so.6 Thread 19 (Thread 0x7fa35f7fe700 (LWP 27194)): #0 0x7fa3a56774dc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fa39ede4c69 in base::ConditionVariable::Wait () at ./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:71 #2 0x7fa39ede6a18 in base::WaitableEvent::TimedWaitUntil () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:223 #3 0x7fa39ede6aaf in base::WaitableEvent::Wait () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:154 #4 0x7fa39edb323f in base::MessagePumpDefault::Run () at ./../../3rdparty/chromium/base/message_loop/message_pump_default.cc:57 #5 0x7fa39edd89ab in base::RunLoop::Run () at ./../../3rdparty/chromium/base/run_loop.cc:130 #6 0x7fa39edfb774 in base::Thread::Run () at ./../../3rdparty/chromium/base/threading/thread.cc:255 #7 base::Thread::ThreadMain () at ./../../3rdparty/chromium/base/threading/thread.cc:338 #8 0x7fa39edf71c1 in ThreadFunc () at ./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:75 #9 0x7fa3a5671554 in start_thread () from /lib64/libpthread.so.0 #10 0x7fa3a6c51ccf in clone () from /lib64/libc.so.6 Thread 18 (Thread 0x7fa35700 (LWP 27193)): #0 0x7fa3a56774dc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fa39ede4c69 in base::ConditionVariable::Wait () at ./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:71 #2 0x7fa39f83dd18 in cc::SingleThreadTaskGraphRunner::Run () at ./../../3rdparty/chromium/cc/raster/single_thread_task_graph_runner.cc:123 #3 0x7fa39edfe2e6 in base::SimpleThread::ThreadMain () at ./../../3rdparty/chromium/base/threading/simple_thread.cc:68 #4 0x7fa39edf71c1 in ThreadFunc () at ./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:75 #5 0x7fa3a5671554 in start_thread () from /lib64/libpthread.so.0 #6 0x7fa3a6c51ccf in clone () from /lib64/libc.so.6 Thread 17 (Thread 0x7fa364ff9700 (LWP 27192)): #0 0x7fa3a56774dc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fa39ede4c69 in base::ConditionVariable::Wait () at ./../../3rdparty/chromium/base/synchronizatio
[Bug 171102] New: kmail crashes when writing and email
http://bugs.kde.org/show_bug.cgi?id=171102 Summary: kmail crashes when writing and email Product: kmail Version: unspecified Platform: SuSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: [EMAIL PROTECTED] Version: Kmail 1.10.1 (using KDE 4.1.1) OS:Linux Installed from:SuSE RPMs When I'm writing and new email or answer and email, when I'm typing kmail crash. -- Configure bugmail: http://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 171102] kmail crashes when writing and email
http://bugs.kde.org/show_bug.cgi?id=171102 --- Comment #2 from Jordi relats 2008-09-15 16:11:39 --- I will install the debug packages, in the mean time I have seen that happens if I have enabled autocorrection, and there is more than two words there are wrong. -- Configure bugmail: http://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
