[kleopatra] [Bug 387978] First time use Key generation Error

[John McMahon]

https://bugs.kde.org/show_bug.cgi?id=387978

--- Comment #3 from John McMahon  ---
Dear Andre Heinecke;
Due to health problems I was delayed replying to your message.I have not been
able to get back to our original Kleopatra problem and resolution tried running
Kleopatra on Laptop which has been borrowed by family member until After New
Years.

The kleopatra was started  via icon screen showed at bottom of Windows screen.
Bringing up a dialog which asks if you want to generate a key pair. Since I
never had a key-pair before, I needed a keypair generated. clicked on generate
keypair and then ran into problems.
Message after first first up of Kleopatra

Welcome to Kleopatra 3.0.1-gpg4win-3.0.2
Can this bug be put into deferred status awaiting more info?

John



From: Andre Heinecke

Sent: Monday, December 18, 2017 2:05 AM
To: monty...@hotmail.com
Subject: [kleopatra] [Bug 387978] First time use Key generation Error

https://bugs.kde.org/show_bug.cgi?id=387978

Andre Heinecke 
changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #2 from Andre Heinecke
 ---
Hi, thanks for your report but I can't reproduce this (generating a key is of
course part of our usual tests). So there must be something in your setup that
is unexpected.

Could you please try to shutdown kleopatra, move away the directory:
%APPDATA%\gnupg
then launch Kleopatra and try again. Maybe you have some corrupted files in
that directory, that could cause such a failure.

If this does not work please start the command line (Hit the Windows + R button
and enter cmd) and there run:

gpg --gen-key

And follow the instructions there. That might produce a better error.
Internally this is what Kleopatra would do in the end.

Best regards,
Andre

--
You are receiving this mail because:
You reported the bug.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[akregator] [Bug 388202] New: Akregator crash on open link by middle button

[EGD]

https://bugs.kde.org/show_bug.cgi?id=388202

Bug ID: 388202
   Summary: Akregator crash on open link by middle button
   Product: akregator
   Version: 5.7.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: egdf...@opensuse.org
  Target Milestone: ---

Application: akregator (5.7.0)

Qt Version: 5.9.3
Frameworks Version: 5.40.0
Operating System: Linux 4.14.6-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:

Akregator crash when i open link by middle button.
I set by setting open links in background tabs by middle bytton.

The crash can be reproduced every time.

-- Backtrace:
Application: Akregator (akregator), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fcbf04cf340 (LWP 30438))]

Thread 31 (Thread 0x7fcb20c87700 (LWP 30499)):
#0  0x7fcbe67a582d in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fcbbacbc06b in  () at /usr/lib64/dri/radeonsi_dri.so
#2  0x7fcbbacbbf87 in  () at /usr/lib64/dri/radeonsi_dri.so
#3  0x7fcbe679f558 in start_thread () at /lib64/libpthread.so.0
#4  0x7fcbec2e86df in clone () at /lib64/libc.so.6

Thread 30 (Thread 0x7fca9bfff700 (LWP 30498)):
#0  0x7fcbe67a582d in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fcbbacbc06b in  () at /usr/lib64/dri/radeonsi_dri.so
#2  0x7fcbbacbbf87 in  () at /usr/lib64/dri/radeonsi_dri.so
#3  0x7fcbe679f558 in start_thread () at /lib64/libpthread.so.0
#4  0x7fcbec2e86df in clone () at /lib64/libc.so.6

Thread 29 (Thread 0x7fcb22cc7700 (LWP 30478)):
#0  0x7fcbe67a582d in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fcbd94a4554 in  () at /usr/lib64/libQt5Script.so.5
#2  0x7fcbd94a4599 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7fcbe679f558 in start_thread () at /lib64/libpthread.so.0
#4  0x7fcbec2e86df in clone () at /lib64/libc.so.6

Thread 28 (Thread 0x7fcb23fff700 (LWP 30473)):
#0  0x7fcbe67a582d in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fcbdcd85ad5 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7fcbdcd85fb7 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7fcbdcd86d51 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7fcbdcd8341b in  () at /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7fcbe679f558 in start_thread () at /lib64/libpthread.so.0
#6  0x7fcbec2e86df in clone () at /lib64/libc.so.6

Thread 27 (Thread 0x7fcb557fa700 (LWP 30472)):
#0  0x7fcbec2f588f in __libc_enable_asynccancel () at /lib64/libc.so.6
#1  0x7fcbec2ddf16 in poll () at /lib64/libc.so.6
#2  0x7fcbe4926149 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fcbe492625c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fcbecc0d77b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7fcbecbb5c5a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7fcbec9e51ea in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7fcbec9e9dde in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fcbe679f558 in start_thread () at /lib64/libpthread.so.0
#9  0x7fcbec2e86df in clone () at /lib64/libc.so.6

Thread 26 (Thread 0x7fcb55ffb700 (LWP 30471)):
#0  0x7fcbcd017e4c in  () at /usr/lib64/pulseaudio/libpulsecommon-11.1.so
#1  0x7fcbcd018169 in  () at /usr/lib64/pulseaudio/libpulsecommon-11.1.so
#2  0x7fcbcd0189ef in  () at /usr/lib64/pulseaudio/libpulsecommon-11.1.so
#3  0x7fcbd5dc64b8 in pa_mainloop_dispatch () at /usr/lib64/libpulse.so.0
#4  0x7fcbd5dc688e in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0
#5  0x7fcbd5dc6910 in pa_mainloop_run () at /usr/lib64/libpulse.so.0
#6  0x7fcbd5dd4779 in  () at /usr/lib64/libpulse.so.0
#7  0x7fcbcd028438 in  () at /usr/lib64/pulseaudio/libpulsecommon-11.1.so
#8  0x7fcbe679f558 in start_thread () at /lib64/libpthread.so.0
#9  0x7fcbec2e86df in clone () at /lib64/libc.so.6

Thread 25 (Thread 0x7fcb567fc700 (LWP 30470)):
#0  0x7fcbe67a5b5c in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fcbdcdb43c2 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7fcbdcd7b4ce in  () at /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7fcbdcd564cb in  () at /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7fcbdcd52d48 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7fcbdcd6f78b in  () at /usr/lib64/libQt5WebEngineCore.so.5
#6  0x7fcbdcd87316 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#7  0x7fcbdcd8341b in  () at /usr/lib64/libQt5WebEngineCore.so.5
#8  0x7fcbe679f558 in start_thread () at /lib64/libpthrea

[Akonadi] [Bug 336581] accidental database loss causes Akonadi / KMail to silently break correct folder assignments

[Martin Steigerwald]

https://bugs.kde.org/show_bug.cgi?id=336581

--- Comment #13 from Martin Steigerwald  ---
(In reply to Frits Spieker from comment #12)

Dear Frits, please refrain from writing unrelated stuff into this bug report.
The bug report is about the effects of accidental database loss on folder
assignments and nothing else. It is not a discussion forum or a mailing list.
Using it for any random comment makes it more difficult to read by any of the
developers. Please use KDE Forum or preferably kdepim-users mailing list to
vent your frustration.

Have a Merry Christmas,
Martin

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 365119] KMail 2 does not add distribution lists/contact groups from KAdressbook properly (simple word, not addresses), or names are wrong

[BingMyBong]

https://bugs.kde.org/show_bug.cgi?id=365119

BingMyBong  changed:

   What|Removed |Added

 CC||bingmyb...@btinternet.com

--- Comment #4 from BingMyBong  ---
Unfortunately this is still the case on opensuse:tumbleweed:20171222
Qt: 5.9.3 KDE Frameworks: 5.40.0 - KDE Plasma:  5.11.4 - kwin 5.11.4
kmail2 5.7.0 - akonadiserver 5.7.0 

Its a bit limiting not being able to send emails to groups/distribution lists

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 388196] New: akonadi_control crash after login

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=388196

Bug ID: 388196
   Summary: akonadi_control crash after login
   Product: Akonadi
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Indexer
  Assignee: kdepim-bugs@kde.org
  Reporter: sunmo...@web.de
CC: chrig...@fastmail.fm, dvra...@kde.org
  Target Milestone: ---

Created attachment 109503
  --> https://bugs.kde.org/attachment.cgi?id=109503&action=edit
Akonadi self test log

Pls. refer to attached log

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 336581] accidental database loss causes Akonadi / KMail to silently break correct folder assignments

[Frits Spieker]

https://bugs.kde.org/show_bug.cgi?id=336581

Frits Spieker  changed:

   What|Removed |Added

 CC||s.pa...@spiekerbros.com

--- Comment #12 from Frits Spieker  ---
As to broken architecture... The dreaded KMail hanging with the message
"Retrieving message/ folder content screen" showing indefinitely is back. On
top of that KMail now always crashes when writing a new email using autofill
for the receiver (start typing the email address and when trying to select one
of the suggestions made, KMail will crash). I will search if a bug report has
been filed for that one and if not I will file it myself.

KMail/ Akonadi had been "OK-ish" for a couple of months (to the extent I even
removed my backup solution of Thunderbird), but it is back to being near
useless again.

-- 
You are receiving this mail because:
You are the assignee for the bug.