[kmail2] [Bug 412606] kmail segmentation fault after having clicked on a mailto:sa...@company.com link in firefox or chrome browser as long as kmail is not already running.

2019-10-04 Thread Nick 
https://bugs.kde.org/show_bug.cgi?id=412606

Nick  changed:

   What|Removed |Added

Summary|kmail segmentation fault|kmail segmentation fault
   |after having clicked on a   |after having clicked on a
   |mailto:sa...@company.com|mailto:sa...@company.com
   |link in firefox browser.|link in firefox or chrome
   ||browser as long as kmail is
   ||not already running.

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

[kmail2] [Bug 412606] kmail segmentation fault after having clicked on a mailto:sa...@company.com link in firefox browser.

2019-10-04 Thread Nick 
https://bugs.kde.org/show_bug.cgi?id=412606

--- Comment #1 from Nick  ---
Important note. If kmail is already running you won't get a segmentation fault.
You need to close all instances of kmail and then click on a mailto: link in a
webpage.

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

[kmail2] [Bug 412606] New: kmail segmentation fault after having clicked on a mailto:sa...@company.com link in firefox browser.

2019-10-04 Thread Nick 
https://bugs.kde.org/show_bug.cgi?id=412606

Bug ID: 412606
   Summary: kmail segmentation fault after having clicked on a
mailto:sa...@company.com link in firefox browser.
   Product: kmail2
   Version: 5.12.1
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: nick.craig@gmail.com
  Target Milestone: ---

Application: kmail (5.12.1)

Qt Version: 5.12.3
Frameworks Version: 5.62.0
Operating System: Linux 4.15.0-65-generic x86_64
Distribution: KDE neon User Edition 5.16

-- Information about the crash:
Was using the Firefox browser and clicked on a link on a web page
"sa...@company.com". A dialogue box opens with a list of possible applications
to use of which kmail was one of them. I highlighted kmail, clicked the 'open
link' button and kmail crashed with a segmentation fault. 100% reproducable.

The kmail segmentation fault also happens if I use the Chrome browser.

The crash can be reproduced every time.

-- 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 0x7f2188adcbc0 (LWP 2957))]

Thread 20 (Thread 0x7f211a7fc700 (LWP 3004)):
#0  0x7f21bc1409f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x7f211a7fb908) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f21bc1409f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x7f211a7fb8b8, cond=0x7f211a7fb8e0) at pthread_cond_wait.c:502
#2  0x7f21bc1409f3 in __pthread_cond_wait (cond=0x7f211a7fb8e0,
mutex=0x7f211a7fb8b8) at pthread_cond_wait.c:655
#3  0x7f21a68cca49 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f21a68cd478 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f21a68cd50f in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7f21a688dfc8 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7f21a68907f6 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#8  0x7f21a6890b34 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#9  0x7f21a68cf561 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#10 0x7f21bc13a6db in start_thread (arg=0x7f211a7fc700) at
pthread_create.c:463
#11 0x7f21bc47388f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 19 (Thread 0x7f211affd700 (LWP 3003)):
#0  0x7f21bc4826ac in __lll_lock_wait_private () at
../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95
#1  0x7f21bc484474 in ___fprintf_chk (fp=0x7f21bc73f8b0
<_IO_stdfile_2_lock>, flag=1, format=0x7f219c1ac6a8 "[%s] %s\n") at
fprintf_chk.c:30
#2  0x7f219c1949ad in event_logv_ () at
/usr/lib/x86_64-linux-gnu/libevent-2.1.so.6
#3  0x7f219c194b44 in event_warn () at
/usr/lib/x86_64-linux-gnu/libevent-2.1.so.6
#4  0x7f219c19646c in  () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6
#5  0x7f219c18c114 in event_base_loop () at
/usr/lib/x86_64-linux-gnu/libevent-2.1.so.6
#6  0x7f21a68d2db4 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7f21a686d2db in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#8  0x7f21a689f311 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#9  0x7f21a68cf561 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#10 0x7f21bc13a6db in start_thread (arg=0x7f211affd700) at
pthread_create.c:463
#11 0x7f21bc47388f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 18 (Thread 0x7f211b7fe700 (LWP 3001)):
#0  0x7f21bc140ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f211b7fd710, expected=0, futex_word=0x7f211b7fd8f8) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7f21bc140ed9 in __pthread_cond_wait_common (abstime=0x7f211b7fd7b0,
mutex=0x7f211b7fd8a8, cond=0x7f211b7fd8d0) at pthread_cond_wait.c:533
#2  0x7f21bc140ed9 in __pthread_cond_timedwait (cond=0x7f211b7fd8d0,
mutex=0x7f211b7fd8a8, abstime=0x7f211b7fd7b0) at pthread_cond_wait.c:667
#3  0x7f21a68ccb17 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f21a68cd46a in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f21a68cd552 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7f21a688dfb1 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7f21a68904c7 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#8  0x7f21a6890ab4 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#9  0x7f21a68cf561 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#10 0x7f21bc13a6db in start_thread (arg=0x7f211b7fe700) at
pthread_create.c:463
#11 0x7f21bc47388f in clone () at

[kleopatra] [Bug 412569] Extended handling related to password confirmation omission

2019-10-04 Thread Ricky Tigg 
https://bugs.kde.org/show_bug.cgi?id=412569

--- Comment #4 from Ricky Tigg  ---
$ pinentry-gnome3 --version
pinentry-gnome3 (pinentry) 1.1.0
Copyright (C) 2016 g10 Code GmbH
License GPLv2+: GNU GPL version 2 or later 
This is free software: you [...]

On my system it is recent.

$ LANG=C rpm -qi pinentry-gnome3 | sed -n '11p;15,16p'
Build Date  : Fri Jul 26 21:44:20 2019
URL : http://www.gnupg.org/aegypten/
Bug URL : https://bugz.fedoraproject.org/pinentry

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

[kleopatra] [Bug 412569] Extended handling related to password confirmation omission

2019-10-04 Thread Andre Heinecke 
https://bugs.kde.org/show_bug.cgi?id=412569

--- Comment #3 from Andre Heinecke  ---
Ok this is definetly bad behavior of pinentry-gnome.

But I don't know pinentry-gnome enough to can say if it is with the GCR System
Prompter or if it is with the version of pinentry-gnome used. I tested with the
latest version of pinentry-gnome with the GCR System Prompter from debian
buster and for me the behavior differs a lot. And it is hard to explain why
from the changes to pinentry-gnome in the last years.

Yes the OK button is visible from the start, but when you click it you get the
error message saying that passwords dont match. When they match I can move on
and it works. I could not reproduce the operation canceld issue you see except
by clicking on cancel. 

What does "pinentry-gnome3 --version" yield for you?

This will give me a better idea who to forward this issue to.

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

[kleopatra] [Bug 412569] Extended handling related to password confirmation omission

2019-10-04 Thread Ricky Tigg 
https://bugs.kde.org/show_bug.cgi?id=412569

--- Comment #2 from Ricky Tigg  ---
Hey. You all interpreted correctly. I used Fedora, Gnone.

Once entering a password in only one field, be it the first or second, invoking
OK starts an endless process. At this state, 
1. Attempting to enter into the confirmation field a password won't be
operational;
2. OK button wss greyed out, while Cancel button alone was available.

Some observations:
– OK button has been in my tests available for being invoked right from the
beginning of the apparition of window illustrated by
kleopatra_3.1.4_failed_password_setting_1.png while no passwords had yet been
entered into any fields.

– The second field –the one aimed for password confirmation– was opened to
receive some content even while the first field –the one aimed to enter a
reference password– had been left blank. Yet during that operation, OK button
remained available.

Those reflections came to me:
– OK button could be greyed out right from the beginning until both fuels have
been supplied with some content which then make it at last available for beeing
invoked.

– The second field could be closed, eventually adding a greyed-out background
to it in order to make its state explicit, until a password has been entered
into the first field and user has switched to the second field.

– Once both fields have been supplied with content, invoking OK button would
process informations contained within these fields then check that they match
each other. In case they don't, a typical message related to the situation
would be exhibited, such as "Passwords do not match each other.", but without
the need to lead to a failure.

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

[kleopatra] [Bug 412569] Extended handling related to password confirmation omission

2019-10-04 Thread Andre Heinecke 
https://bugs.kde.org/show_bug.cgi?id=412569

--- Comment #1 from Andre Heinecke  ---
Hi,

thank you for your detailed report. I do not understand the problem correctly.

By password confirmation you mean the "Repeat" field.

If you omit the repeat field it still lets you advance with OK ?
Or is the order somehow messed up for you so if you hit enter then it cancels ?

I just tested with both pinentry-gnome3 (which you are using) and while it does
not grey out the OK button it does not let you advance with it.

Pinentry-qt (The "KDE'ish" pinentry which I maintain) greys out the OK button
if there is something wrong and Cancel comes last in the tab order.

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

[kdepim] [Bug 412592] New: kmail folder list last item cannot be resized

2019-10-04 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=412592

Bug ID: 412592
   Summary: kmail folder list last item cannot be resized
   Product: kdepim
   Version: 5.11.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: messagecore
  Assignee: kdepim-bugs@kde.org
  Reporter: d...@newtech.fi
  Target Milestone: ---

SUMMARY
Selecting Unread and Total in the folder list gives a display where the Total
field width can only be expanded - Never shrinked. Any attempt to shrink will
just bounce the marker back

STEPS TO REPRODUCE
1. Set up kmail with folder list (and in my case favourites) to the left.
2. Right click on the folder list header and select "unread" and "Total"
3. Expand the Total field slightly.
4. Try to shrink it back and watch kmail refusing to do that

OBSERVED RESULT
Cannot shrink the last "Total" field in the list

EXPECTED RESULT
Normal shrink by dragging separator should be possible

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Mageia 7
(available in About System)
KDE Plasma Version: 5.15.4
KDE Frameworks Version: KDE Frameworks 5.57.0
Qt Version: Qt 5.12.2

ADDITIONAL INFORMATION
Couldn't find a place for reporting kmail bugs. Putting it under PIM in hope of
someone finding the right place for the report.

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