[digikam] [Bug 410862] Crash when starting appimage build 6.3.0-git-20190812T053738-x86-64

2019-08-12 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=410862

Maik Qualmann  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
   Version Fixed In||6.3.0
 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/kde/
   ||digikam/commit/68a91eb80289
   ||38e6f8fb7bf1d4e7f4a70f11a08
   ||f

--- Comment #1 from Maik Qualmann  ---
Git commit 68a91eb8028938e6f8fb7bf1d4e7f4a70f11a08f by Maik Qualmann.
Committed on 13/08/2019 at 05:50.
Pushed by mqualmann into branch 'master'.

fix crash in new function when the album list is empty
FIXED-IN: 6.3.0

M  +2-1NEWS
M  +1-1core/app/main/digikamapp.cpp

https://invent.kde.org/kde/digikam/commit/68a91eb8028938e6f8fb7bf1d4e7f4a70f11a08f

-- 
You are receiving this mail because:
You are watching all bug changes.

[Breeze] [Bug 406502] Bad icon to go from 8 to 16 bits

2019-08-12 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=406502

caulier.gil...@gmail.com changed:

   What|Removed |Added

   Assignee|digikam-bugs-n...@kde.org   |visual-des...@kde.org
  Component|Usability-Themes|Icons
Version|6.2.0   |unspecified
Product|digikam |Breeze

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 410862] Crash when starting appimage build 6.3.0-git-20190812T053738-x86-64

2019-08-12 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=410862

caulier.gil...@gmail.com changed:

   What|Removed |Added

  Component|general |Bundle-AppImage
 CC||caulier.gil...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney] [Bug 410865] Access to german online banking requires product key

2019-08-12 Thread Ralf Habacker
https://bugs.kde.org/show_bug.cgi?id=410865

--- Comment #3 from Ralf Habacker  ---
Git commit 3b5c6d136d1391a2d38c89a53f9b8f6aaa6dc97a by Ralf Habacker.
Committed on 13/08/2019 at 04:58.
Pushed by habacker into branch '4.8'.

Raise minimum required version of AqBanking5.0

the German online banking users have to use a registered software from
mid-September onwards and the institutions are allowed according to EU
regulations to reject/refuse access by non-registered client
applications.

To be able to support this process KMyMoney requires a newer version of
AqBanking which has been released lately.

Backported from commit cd00fe960c70c6cd905cdafc2575598020bfbbc6.

M  +4-4CMakeLists.txt

https://commits.kde.org/kmymoney/3b5c6d136d1391a2d38c89a53f9b8f6aaa6dc97a

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney] [Bug 410865] Access to german online banking requires product key

2019-08-12 Thread Ralf Habacker
https://bugs.kde.org/show_bug.cgi?id=410865

Ralf Habacker  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kmy
   ||money/3741b0e6d8e8297e2d7d5
   ||dfe25e2a0290617a2e7

--- Comment #1 from Ralf Habacker  ---
Git commit c1d97f88cc88893a0a4b83df78fccefea71e3ed0 by Thomas Baumgart.
Committed on 18/08/2019 18:02.
Pushed by tbaumgart into branch '5.0'.

Added registration with ZKA (https://www.hbci-zka.de/)
German banks soon require the application to be registered with ZKA in
order to use the their FinTS interface.

This implements the necessary functionality to be in line with the
requirements.

https://commits.kde.org/kmymoney/c1d97f88cc88893a0a4b83df78fccefea71e3ed0

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney] [Bug 410865] Access to german online banking requires product key

2019-08-12 Thread Ralf Habacker
https://bugs.kde.org/show_bug.cgi?id=410865

Ralf Habacker  changed:

   What|Removed |Added

 Resolution|--- |FIXED
   Version Fixed In||4.8.4, 5.0.6
 Status|REPORTED|RESOLVED

--- Comment #2 from Ralf Habacker  ---
Git commit 3741b0e6d8e8297e2d7d5dfe25e2a0290617a2e7 by Ralf Habacker.
Committed on08/08/2019 23:18
Pushed by rhabacker into branch '4.8'.

Added registration with ZKA (https://www.hbci-zka.de/)
German banks soon require the application to be registered with ZKA in
order to use the their FinTS interface.

This implements the necessary functionality to be in line with the
requirements.

Backported to 4.8

https://commits.kde.org/kmymoney/3741b0e6d8e8297e2d7d5dfe25e2a0290617a2e7

-- 
You are receiving this mail because:
You are watching all bug changes.

[amarok] [Bug 410375] Amarok crash at start again and again

2019-08-12 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=410375

--- Comment #4 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 410326] Your software did not work on elementaryos distribution

2019-08-12 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=410326

--- Comment #2 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[amarok] [Bug 410266] Amarok crashed by starting

2019-08-12 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=410266

--- Comment #2 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 410356] Discover

2019-08-12 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=410356

--- Comment #2 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes

2019-08-12 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=374890

--- Comment #12 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 368689] Syntax highlighting is correct on load but breaks with editing.

2019-08-12 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=368689

--- Comment #12 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney] [Bug 410865] New: Access to german online banking requires product key

2019-08-12 Thread Ralf Habacker
https://bugs.kde.org/show_bug.cgi?id=410865

Bug ID: 410865
   Summary: Access to german online banking requires product key
   Product: kmymoney
   Version: 4.8.3
  Platform: Other
OS: MS Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: onlinebanking
  Assignee: kmymoney-de...@kde.org
  Reporter: ralf.habac...@freenet.de
  Target Milestone: ---

from https://mail.kde.org/pipermail/kmymoney-devel/2019-August/023608.html

The German online banking users have received notice from their banks that due
to EU regulations, from mid-September onwards (Sept 14th) the banking client 
software has to use a registered product key, otherwise the bank server
connection will be refused.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 410549] PPA's without a valid release file will cause Discover to stop displaying all APT repositories

2019-08-12 Thread leftcrane
https://bugs.kde.org/show_bug.cgi?id=410549

--- Comment #2 from leftcrane  ---
Created attachment 122094
  --> https://bugs.kde.org/attachment.cgi?id=122094=edit
illustration of issue (no update, no sources etc.)

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 410549] PPA's without a valid release file will cause Discover to stop displaying all APT repositories

2019-08-12 Thread leftcrane
https://bugs.kde.org/show_bug.cgi?id=410549

--- Comment #1 from leftcrane  ---
OK, after a restart/logout, Discover no longer displays apt updates - and for
some reason is offering to install a bunch of backends which are already
installed, with the install button grayed out. So at the moment, Discover is
completely broken on my machine.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 410864] New: Krita crashes when opening calibration image

2019-08-12 Thread Isaac A.
https://bugs.kde.org/show_bug.cgi?id=410864

Bug ID: 410864
   Summary: Krita crashes when opening calibration image
   Product: krita
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: is...@isaacs.site
  Target Milestone: ---

Application: krita (4.1.8)

Qt Version: 5.12.4
Frameworks Version: 5.60.0
Operating System: Linux 5.2.7-200.fc30.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
Steps to reproduce:
- Download http://displaycal.net/icc-color-management-test/sRGB_Gray.jpg
- Open it in Krita, any method works

Krita immediately crashes after opening this specific image

The crash can be reproduced every time.

-- Backtrace:
Application: Krita (krita), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3f6a1f1cc0 (LWP 30814))]

Thread 22 (Thread 0x7f3ef92f3700 (LWP 30838)):
#0  0x7f3f6f0975c7 in poll () from /lib64/libc.so.6
#1  0x7f3f6cd451de in ?? () from /lib64/libglib-2.0.so.0
#2  0x7f3f6cd45313 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7f3f6f639bf3 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7f3f6f5e39eb in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7f3f6f43c635 in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7f3f57b53e4a in ?? () from /lib64/libQt5Quick.so.5
#7  0x7f3f6f43d786 in ?? () from /lib64/libQt5Core.so.5
#8  0x7f3f6d5cb5a2 in start_thread () from /lib64/libpthread.so.0
#9  0x7f3f6f0a2303 in clone () from /lib64/libc.so.6

Thread 21 (Thread 0x7f3f0affd700 (LWP 30837)):
#0  0x7f3f6f0975c7 in poll () from /lib64/libc.so.6
#1  0x7f3f6cd451de in ?? () from /lib64/libglib-2.0.so.0
#2  0x7f3f6cd45313 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7f3f6f639bf3 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7f3f6f5e39eb in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7f3f6f43c635 in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7f3f5786ca69 in ?? () from /lib64/libQt5Qml.so.5
#7  0x7f3f6f43d786 in ?? () from /lib64/libQt5Core.so.5
#8  0x7f3f6d5cb5a2 in start_thread () from /lib64/libpthread.so.0
#9  0x7f3f6f0a2303 in clone () from /lib64/libc.so.6

Thread 20 (Thread 0x7f3efbfff700 (LWP 30836)):
#0  0x7f3f6f09cfad in syscall () from /lib64/libc.so.6
#1  0x7f3f6f43fe00 in ?? () from /lib64/libQt5Core.so.5
#2  0x7f3f6f43fb76 in QSemaphore::tryAcquire(int, int) () from
/lib64/libQt5Core.so.5
#3  0x7f3f6e658d9a in KisTileDataSwapper::run() () from
/lib64/libkritaimage.so.17
#4  0x7f3f6f43d786 in ?? () from /lib64/libQt5Core.so.5
#5  0x7f3f6d5cb5a2 in start_thread () from /lib64/libpthread.so.0
#6  0x7f3f6f0a2303 in clone () from /lib64/libc.so.6

Thread 19 (Thread 0x7f3f0b7fe700 (LWP 30832)):
#0  0x7f3f6f0975c7 in poll () from /lib64/libc.so.6
#1  0x7f3f6cd451de in ?? () from /lib64/libglib-2.0.so.0
#2  0x7f3f6cd45313 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7f3f6f639bf3 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7f3f6f5e39eb in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7f3f6f43c635 in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7f3f6d5fbf4a in ?? () from /lib64/libQt5DBus.so.5
#7  0x7f3f6f43d786 in ?? () from /lib64/libQt5Core.so.5
#8  0x7f3f6d5cb5a2 in start_thread () from /lib64/libpthread.so.0
#9  0x7f3f6f0a2303 in clone () from /lib64/libc.so.6

Thread 18 (Thread 0x7f3f0bfff700 (LWP 30831)):
#0  0x7f3f6d5d14d5 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f3f565616fb in ?? () from /usr/lib64/dri/radeonsi_dri.so
#2  0x7f3f5656130b in ?? () from /usr/lib64/dri/radeonsi_dri.so
#3  0x7f3f6d5cb5a2 in start_thread () from /lib64/libpthread.so.0
#4  0x7f3f6f0a2303 in clone () from /lib64/libc.so.6

Thread 17 (Thread 0x7f3f30ff9700 (LWP 30830)):
#0  0x7f3f6d5d14d5 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f3f565616fb in ?? () from /usr/lib64/dri/radeonsi_dri.so
#2  0x7f3f5656130b in ?? () from /usr/lib64/dri/radeonsi_dri.so
#3  0x7f3f6d5cb5a2 in start_thread () from /lib64/libpthread.so.0
#4  0x7f3f6f0a2303 in clone () from /lib64/libc.so.6

Thread 16 (Thread 0x7f3f317fa700 (LWP 30829)):
#0  0x7f3f6d5d14d5 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f3f565616fb in ?? () from /usr/lib64/dri/radeonsi_dri.so
#2  0x7f3f5656130b in ?? () from /usr/lib64/dri/radeonsi_dri.so
#3  0x7f3f6d5cb5a2 in 

[plasmashell] [Bug 410648] plasmashell crashed when I refused to enter the password of WiFi

2019-08-12 Thread Alexander Potashev
https://bugs.kde.org/show_bug.cgi?id=410648

Alexander Potashev  changed:

   What|Removed |Added

 CC||aspotas...@gmail.com

--- Comment #1 from Alexander Potashev  ---
possible duplicate of bug #409709

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 410005] Plasmashell crashes, probably related to the network manager (plasma-nm)

2019-08-12 Thread Alexander Potashev
https://bugs.kde.org/show_bug.cgi?id=410005

--- Comment #3 from Alexander Potashev  ---
possible duplicate of bug #409709

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 410078] Plasma crashed after clicking 'Disconnect'

2019-08-12 Thread Alexander Potashev
https://bugs.kde.org/show_bug.cgi?id=410078

Alexander Potashev  changed:

   What|Removed |Added

 CC||aspotas...@gmail.com

--- Comment #1 from Alexander Potashev  ---
possible duplicate of bug #409709

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 410635] Crash on Wifi Network Change

2019-08-12 Thread Alexander Potashev
https://bugs.kde.org/show_bug.cgi?id=410635

Alexander Potashev  changed:

   What|Removed |Added

 CC||aspotas...@gmail.com

--- Comment #1 from Alexander Potashev  ---
possible duplicate of bug #409709

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 410005] Plasmashell crashes, probably related to the network manager (plasma-nm)

2019-08-12 Thread Alexander Potashev
https://bugs.kde.org/show_bug.cgi?id=410005

Alexander Potashev  changed:

   What|Removed |Added

 CC||aspotas...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 409735] plasmashell segmentation fault in PlotSGNode::bind() at plotter.cpp:695 of kf5-kdeclarative-5.59.0-2.fc30 on Wayland

2019-08-12 Thread Alexander Potashev
https://bugs.kde.org/show_bug.cgi?id=409735

Alexander Potashev  changed:

   What|Removed |Added

 CC||aspotas...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 409709] KDE Plasma crashed upon disconnecting from a network

2019-08-12 Thread Alexander Potashev
https://bugs.kde.org/show_bug.cgi?id=409709

Alexander Potashev  changed:

   What|Removed |Added

 CC||aspotas...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 405067] Plasma crashed when removing one of two plasma dashboards under wayland

2019-08-12 Thread Alexander Potashev
https://bugs.kde.org/show_bug.cgi?id=405067

Alexander Potashev  changed:

   What|Removed |Added

 CC||aspotas...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 366653] Plasmashell crash while dragging control bar

2019-08-12 Thread Alexander Potashev
https://bugs.kde.org/show_bug.cgi?id=366653

Alexander Potashev  changed:

   What|Removed |Added

 CC||aspotas...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 364766] Graphics distorted after suspend/resume with nvidia

2019-08-12 Thread Alexander Potashev
https://bugs.kde.org/show_bug.cgi?id=364766

Alexander Potashev  changed:

   What|Removed |Added

 CC||aspotas...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[korganizer] [Bug 188848] the reminder popup should have a timeout before accepting keystrokes

2019-08-12 Thread Filipus Klutiero
https://bugs.kde.org/show_bug.cgi?id=188848

Filipus Klutiero  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=410863

-- 
You are receiving this mail because:
You are watching all bug changes.

[korganizer] [Bug 410863] New: Incidence is automatically selected in reminder window, allowing for accidental postponing and dismissal

2019-08-12 Thread Filipus Klutiero
https://bugs.kde.org/show_bug.cgi?id=410863

Bug ID: 410863
   Summary: Incidence is automatically selected in reminder
window, allowing for accidental postponing and
dismissal
   Product: korganizer
   Version: 5.10.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: reminder daemon (korgac)
  Assignee: kdepim-b...@kde.org
  Reporter: chea...@gmail.com
  Target Milestone: ---

When a reminder is triggered, its incidence is automatically selected in the
reminder window. This means that if a reminder triggers while the reminder
window is already showing, several incidences can become selected, so that
actions (postponing and dismissal) will affect all.

One particularly likely scenario is the following.
A user arrives to his PC after 2 reminders triggered. He selects the first
incidence, postpones by a duration of x. He then postpones the second incidence
by the same duration of x.

x time after he postponed the first reminder, the reminder for that same
incidence triggers again. The user moves the cursor over the Dismiss button.
Just before the user presses the button, x time after the second reminder was
postponed, the reminder for the second incidence triggers again. The user
pushes the Dismiss button while both incidences are selected, accidentally
dismissing the second incidence's reminder.

Not selecting incidences by default would already solve most of this bug, but
ticket #188848 covers a different scenario which is worth considering when
solving is best.

SOFTWARE/OS VERSIONS

Linux: 5.0.0
KDE Plasma Version: 5.15.4
KDE Frameworks Version: 5.56.0
Qt Version: 5.12.2

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 410862] Crash when starting appimage build 6.3.0-git-20190812T053738-x86-64

2019-08-12 Thread IWBR
https://bugs.kde.org/show_bug.cgi?id=410862

IWBR  changed:

   What|Removed |Added

 CC||iwannaber...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 410862] New: Crash when starting appimage build 6.3.0-git-20190812T053738-x86-64

2019-08-12 Thread IWBR
https://bugs.kde.org/show_bug.cgi?id=410862

Bug ID: 410862
   Summary: Crash when starting appimage build
6.3.0-git-20190812T053738-x86-64
   Product: digikam
   Version: 6.3.0
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: digikam-bugs-n...@kde.org
  Reporter: iwannaber...@gmail.com
  Target Milestone: ---

SUMMARY

I downloaded and tried the most recent appimage build for x64
(6.3.0-git-20190812T053738-x86-64). It seems to crash at startup in my computer
(Ubuntu 18.04 LTS).

If I start it from command line in debug mode, this is the full output I get
(including backtrace). I hope it helps:





user@user-TM1703:~/Applications$
./digikam-6.3.0-git-20190812T053738-x86-64_4338a3f6f7f40768c9c5fc4baf344970.appimage
debug

(AppImageLauncher:21162): GLib-GIO-CRITICAL **: 01:39:30.114:
g_converter_convert: assertion 'outbuf_size > 0' failed

(AppImageLauncher:21162): Gtk-CRITICAL **: 01:39:30.114: Unable to load
resource for composite template for type 'GtkDialog': No s'ha pogut
descomprimir el recurs «/org/gtk/libgtk/ui/gtkdialog.ui»

(AppImageLauncher:21162): Gtk-CRITICAL **: 01:39:30.114:
gtk_widget_class_bind_template_child_full: assertion
'widget_class->priv->template != NULL' failed

(AppImageLauncher:21162): Gtk-CRITICAL **: 01:39:30.114:
gtk_widget_class_bind_template_child_full: assertion
'widget_class->priv->template != NULL' failed

(AppImageLauncher:21162): Gtk-CRITICAL **: 01:39:30.114:
gtk_widget_class_bind_template_child_full: assertion
'widget_class->priv->template != NULL' failed

(AppImageLauncher:21162): Gtk-CRITICAL **: 01:39:30.114:
gtk_widget_class_bind_template_child_full: assertion
'widget_class->priv->template != NULL' failed

(AppImageLauncher:21162): Gtk-CRITICAL **: 01:39:30.114:
gtk_widget_class_bind_template_callback_full: assertion
'widget_class->priv->template != NULL' failed
-- digiKam Linux AppImage Bundle
-- Use 'help' as CLI argument to know all available options for digiKam
application.
-- Note: to integrate this bundle to your desktop, use AppImageLauncher.
libudev.so.0 
-- Preloading shared libs: 
Starting digiKam into GDB...
Use 'bt' command on debugger prompt to get a crash backtrace.
Use 'q' command to quit debugger session.
GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from digikam...done.
Starting program: /tmp/.mount_digikasuEFNg/usr/bin/digikam 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffd8f00700 (LWP 21734)]
[New Thread 0x7fffd3fff700 (LWP 21740)]
Digikam::DXmlGuiWindow::setupIconTheme: Breeze icons resource file found
Digikam::DXmlGuiWindow::setupIconTheme: Breeze-dark icons resource file found
Digikam::ApplicationSettings::setApplicationFont: Switch to application font: 
QFont( "Ubuntu,12,-1,5,50,0,0,0,0,0,Regular" )
Digikam::AlbumWatch::AlbumWatch: AlbumWatch is disabled
[New Thread 0x7fffd2700700 (LWP 21751)]
Digikam::AlbumManager::setDatabase: Database Parameters:
   Type: "QSQLITE"
   DB Core Name: "/home/user/Imatges/digikam4.db"
   DB Thumbs Name:   "/home/user/Imatges/thumbnails-digikam.db"
   DB Face Name: "/home/user/Imatges/recognition.db"
   DB Similarity Name:   "/home/user/Imatges/similarity.db"
   Connect Options:  ""
   Host Name:""
   Host port:-1
   Internal Server:  false
   Internal Server Path: ""
   Internal Server Serv Cmd: ""
   Internal Server Init Cmd: ""
   Username: ""
   Password: ""

[New Thread 0x7fffd1eff700 (LWP 21752)]
[Thread 0x7fffd1eff700 (LWP 21752) exited]
Digikam::DbEngineConfigSettingsLoader::readConfig: Loading SQL code from config
file "/tmp/.mount_digikasuEFNg/usr/share/digikam/database/dbconfig.xml"
Digikam::DbEngineConfigSettingsLoader::readConfig: Checking XML version ID =>
expected:  3  found:  3
Digikam::CoreDbSchemaUpdater::update: Core database: running schema update
Digikam::CoreDbSchemaUpdater::startUpdates: Core database: have a structure
version  10

[Breeze] [Bug 410854] Monochrome "computer" icon is used no matter what icon resolution is used

2019-08-12 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=410854

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org
 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #1 from Nate Graham  ---
Confirmed, that's very odd. You can see the issue in Cuttlefish, too. Maybe
some kind of conflict with the Plasma theme icon with the same name?

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 410844] Okular segfault

2019-08-12 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=410844

Albert Astals Cid  changed:

   What|Removed |Added

 CC||aa...@kde.org
 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO

--- Comment #1 from Albert Astals Cid  ---
We're going to need the file

-- 
You are receiving this mail because:
You are watching all bug changes.

[telepathy] [Bug 390964] Crash when clicking [Settings -> Configure Chat Application...] version 17.12.2

2019-08-12 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=390964

danjar...@gmail.com changed:

   What|Removed |Added

 CC||danjar...@gmail.com

--- Comment #9 from danjar...@gmail.com ---
I use KdeNEON and it is frustrating that this package is not updated, to avoid
this error, along with the text-ui viewer, I run the following script.


apt install pidgin-sipe kde-telepathy

# (you need activate "dep-src" en /etc/apt/source.list)

mkdir ktp-text-ui-fix
cd ktp-text-ui-fix
apt install build-essential devscripts
apt source kde-telepathy-text-ui
apt build-dep kde-telepathy-text-ui
cd ktp-text-ui-*
patch -p1 << "EOF"
--- a/lib/adium-theme-view.cpp
+++ b/lib/adium-theme-view.cpp
@@ -68,6 +68,8 @@ bool AdiumThemePage::acceptNavigationRequest(const QUrl ,
QWebEnginePage::Na
 Q_EMIT nextConversation();
 } else if (url.fragment() == QLatin1String("x-prevConversation")) {
 Q_EMIT prevConversation();
+} else if (url.scheme() == QLatin1String("data")) {
+return true;
 } else {
 QDesktopServices::openUrl(url);
 }
EOF
patch -p1 << "EOF"
--- a/app/chat-window.cpp
+++ b/app/chat-window.cpp
@@ -53,6 +53,7 @@
 #include 
 #include 
 #include 
+#include 

 #include 
 #include 
@@ -760,7 +761,9 @@ void ChatWindow::showSettingsDialog()
 KSettings::Dialog *dialog = new KSettings::Dialog(this);

 KPageWidgetItem *configPage =
dialog->addModule(QLatin1String("kcm_ktp_chat_appearance"));
-KCModuleProxy *proxy = qobject_cast(configPage->widget());
+QScrollArea *moduleScroll =
qobject_cast(configPage->widget());
+Q_ASSERT(moduleScroll);
+KCModuleProxy *proxy =
qobject_cast(moduleScroll->widget());
 Q_ASSERT(proxy);

 connect(proxy->realModule(), SIGNAL(reloadTheme()),
@@ -770,7 +773,9 @@ void ChatWindow::showSettingsDialog()
 dialog->addModule(QLatin1String("kcm_ktp_chat_messages"));

 KPageWidgetItem *otrConfigPage =
dialog->addModule(QLatin1String("kcm_ktp_chat_otr"));
-proxy = qobject_cast(otrConfigPage->widget());
+moduleScroll = qobject_cast(otrConfigPage->widget());
+Q_ASSERT(moduleScroll);
+proxy = qobject_cast(moduleScroll->widget());
 Q_ASSERT(proxy);
 QVariant value;
 value.setValue(m_proxyService);
EOF

debchange -i

# (you need change the first line with: ktp-text-ui (4:17.12.3-0ubuntu2)
bionic; urgency=medium)

dpkg-source --commit
debuild -us -uc -i -I
cd ..
dpkg -i kde-telepathy-text-ui_*.deb

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app

2019-08-12 Thread Ovidiu-Florin BOGDAN
https://bugs.kde.org/show_bug.cgi?id=404990

Ovidiu-Florin BOGDAN  changed:

   What|Removed |Added

 CC||ovidiu@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[Plasma SDK] [Bug 410861] New: Wayland generic icon in window decoration and task switcher

2019-08-12 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=410861

Bug ID: 410861
   Summary: Wayland generic icon in window decoration and task
switcher
   Product: Plasma SDK
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: plasmathemeexplorer
  Assignee: plasma-b...@kde.org
  Reporter: bugsefor...@gmx.com
CC: giorgos.tsiapalio...@kde.org
  Target Milestone: ---

Created attachment 122093
  --> https://bugs.kde.org/attachment.cgi?id=122093=edit
screenshot

SUMMARY


STEPS TO REPRODUCE
1. oepn Plasma theme explorer on Wayland
2. press alt+tab and hold alt key
3. 

OBSERVED RESULT
Wayland generic icon in task switcher and window decoration.

EXPECTED RESULT
plasma theme explorer shows its own icon in task switcher and windows
decoration.

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.16.80
KDE Frameworks Version: 5.62.0
Qt Version: 5.12.3

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 406022] add timeline support for conventional mouse wheel navigation

2019-08-12 Thread S. Christian Collins
https://bugs.kde.org/show_bug.cgi?id=406022

S. Christian Collins  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |MOVED

--- Comment #1 from S. Christian Collins  ---
This bug report has been moved and updated here:
https://invent.kde.org/kde/kdenlive/issues/332

-- 
You are receiving this mail because:
You are watching all bug changes.

[lattedock] [Bug 410858] Full screen window goes under Latte Dock despite it's set to always visible

2019-08-12 Thread Michail Vourlakos
https://bugs.kde.org/show_bug.cgi?id=410858

--- Comment #1 from Michail Vourlakos  ---
1. Screenshot of the issue
2. Screenshot of your full multi-screen setup
3. You mean maximized OR full screen window, they are different
4. Screenshot of how you think it should work

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 399923] Segmentation fault during face detection

2019-08-12 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=399923

--- Comment #171 from timo...@zoho.com ---
Overcommit is set to the default setting ("however much the kernel heuristic
sees fit"):

$ cat /proc/sys/vm/overcommit_memory
0
$ cat /proc/sys/vm/overcommit_ratio
50

The machine has 8G of ram, though I have reproduced it on my 16G laptop as
well.

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 406485] KDE forgets my display settings after reboot

2019-08-12 Thread Neros
https://bugs.kde.org/show_bug.cgi?id=406485

Neros  changed:

   What|Removed |Added

 CC||cont...@neros.fr

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 410860] New: Kmail is dropping receive account settings.

2019-08-12 Thread Chris
https://bugs.kde.org/show_bug.cgi?id=410860

Bug ID: 410860
   Summary: Kmail is dropping receive account settings.
   Product: Akonadi
   Version: 5.11.90
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: IMAP resource
  Assignee: kdepim-b...@kde.org
  Reporter: crgla...@gmail.com
  Target Milestone: ---

Application: akonadi_imap_resource (5.11.90)

Qt Version: 5.13.0
Frameworks Version: 5.61.0
Operating System: Linux 4.12.14-lp151.28.10-default x86_64
Distribution: "openSUSE Leap 15.1"

-- Information about the crash:
Kmail has been dropping receive account settings for Gmail accounts (to mme
this random as to which account gets dropped)  The net result is that when I
try to re-eneter credentials the message the "Sign in with Google temporaily
disabled for this app  This app has not been verified by Google in order to use
Google Sign In.

I have five other email accounts all IMAP on Gmail.  Only one is having this
problem.

The crash can be reproduced every time.

-- Backtrace:
Application: akonadi_imap_resource_11 (akonadi_imap_resource), signal:
Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f151b023940 (LWP 1501))]

Thread 21 (Thread 0x7f14b6ffd700 (LWP 1923)):
#0  0x7f1511db3bdb in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f1509787376 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () at
./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:127
#2  0x7f1509787d07 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks
const&) () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:230
#3  0x7f1509787e72 in base::WaitableEvent::TimedWait(base::TimeDelta
const&) () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:162
#4  0x7f150973f2f1 in
base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) ()
at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:37
#5  0x7f150974231d in base::internal::SchedulerWorker::RunWorker() () at
./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:303
#6  0x7f1509742a14 in base::internal::SchedulerWorker::RunPooledWorker() ()
at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:229
#7  0x7f1509789f65 in ThreadFunc() () at
./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:81
#8  0x7f1511dad569 in start_thread () at /lib64/libpthread.so.0
#9  0x7f15151169ef in clone () at /lib64/libc.so.6

Thread 20 (Thread 0x7f1487fff700 (LWP 1922)):
#0  0x7f1511db3bdb in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f1509787376 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () at
./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:127
#2  0x7f1509787d07 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks
const&) () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:230
#3  0x7f1509787e72 in base::WaitableEvent::TimedWait(base::TimeDelta
const&) () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:162
#4  0x7f150973f2f1 in
base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) ()
at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:37
#5  0x7f150974231d in base::internal::SchedulerWorker::RunWorker() () at
./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:303
#6  0x7f1509742a14 in base::internal::SchedulerWorker::RunPooledWorker() ()
at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:229
#7  0x7f1509789f65 in ThreadFunc() () at
./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:81
#8  0x7f1511dad569 in start_thread () at /lib64/libpthread.so.0
#9  0x7f15151169ef in clone () at /lib64/libc.so.6

Thread 19 (Thread 0x7f1450ecf700 (LWP 1586)):
#0  0x7f1511db38ad in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f150978728a in base::ConditionVariable::Wait() () at
./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:75
#2  0x7f1509787d1c in base::WaitableEvent::TimedWaitUntil(base::TimeTicks
const&) () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:232
#3  0x7f1509787e2f in base::WaitableEvent::Wait() () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:155
#4  0x7f150973f2c5 in
base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) ()
at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:35
#5  0x7f150974231d in base::internal::SchedulerWorker::RunWorker() () at

[valgrind] [Bug 410599] Non-deterministic behaviour of pth_self_kill_15_other test

2019-08-12 Thread Philippe Waroquiers
https://bugs.kde.org/show_bug.cgi?id=410599

--- Comment #5 from Philippe Waroquiers  ---
(In reply to Stefan Maksimovic from comment #4)
> Created attachment 122077 [details]
> pth_self_kill.patch v2
> 
> Thanks Philippe, validating the test through memcheck slipped my mind.
> 
> I've updated the patch by initializing the variables reported by memcheck,
> it should be fine now.

The patch looks ok to me and can be pushed.
Thanks for the work

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 349554] Deform brush does not take canvas rotation into consideration

2019-08-12 Thread vanyossi
https://bugs.kde.org/show_bug.cgi?id=349554

vanyossi  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|ASSIGNED|RESOLVED

--- Comment #6 from vanyossi  ---
I can't reproduce the bug as described in the bugreport or anyother way I
thinked about. Closing.

Please reopen if you still get this behaviour

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 406502] Bad icon to go from 8 to 16 bits

2019-08-12 Thread Alexandre Belz
https://bugs.kde.org/show_bug.cgi?id=406502

--- Comment #2 from Alexandre Belz  ---
Okay,  Maik,
as i saw that no progress was done on this point, i read again my bug report
and notice that indeed it was attached to Breeze product while i expected
Digikam.
i thought that Breeze was another SW, and that it was a misconfiguration from
me on the bug report. Hence my modification.

Sorry if i was wrong.
Feel free to change it back to Breeze.

Best regards.
Alexandre.


 Message d'origine 
De : Maik Qualmann 
Date : 12/08/2019 18:38 (GMT+01:00)
À : alexandre.b...@live.fr
Objet : [digikam] [Bug 406502] Bad icon to go from 8 to 16 bits

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

Maik Qualmann  changed:

   What|Removed |Added

Version|6.1.0   |6.2.0

--- Comment #1 from Maik Qualmann  ---
@Alexandre

I assigned the bug to the Breeze team, why did you bring the bug back to
digiKam? We are not the creators of the icon set and can not fix this problem.

Maik

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

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 357443] black/invisible squares on systray and top left of screen after kwin restarted

2019-08-12 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=357443

Nate Graham  changed:

   What|Removed |Added

   Keywords||usability

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 402130] Krita hangs on flood fill (+ gdb backtrace)

2019-08-12 Thread vanyossi
https://bugs.kde.org/show_bug.cgi?id=402130

vanyossi  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #6 from vanyossi  ---
this no longer happens in 8e5a3ed.

Setting as resolved.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 409818] For float bit depths, some fraction inputs convert too early, making it impossible to type in some fractions

2019-08-12 Thread Jasper
https://bugs.kde.org/show_bug.cgi?id=409818

Jasper  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED
   Assignee|krita-bugs-n...@kde.org |firebea...@gmail.com
 CC||firebea...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[gwenview] [Bug 324597] Rotating and saving a JPEG image changes the image itself, not the EXIF orientation tag

2019-08-12 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=324597

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|CONFIRMED   |NEEDSINFO

--- Comment #4 from Nate Graham  ---
This appears to be fixed as of Gwenview 19.04.0. Please verify.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Breeze] [Bug 344746] Drop-down arrow not visible anymore for ToolButtons with dropdown menus that appear without press-and-hold

2019-08-12 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=344746

Nate Graham  changed:

   What|Removed |Added

Summary|Drop-down arrow not visible |Drop-down arrow not visible
   |anymore for buttons with|anymore for ToolButtons
   |dropdown menus  |with dropdown menus that
   ||appear without
   ||press-and-hold

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-nm] [Bug 410859] plasmashell hangs for multiple seconds while nmcli is also slow to respond

2019-08-12 Thread Alexander Potashev
https://bugs.kde.org/show_bug.cgi?id=410859

--- Comment #1 from Alexander Potashev  ---
The nmcli unresponsiveness might be due to horrible problems with my VPN server
(DDoS attack against the data center) which I connect to using
networkmanager+openvpn.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 410857] grouped video and audio crashed while video is locked and audio deleted

2019-08-12 Thread emohr
https://bugs.kde.org/show_bug.cgi?id=410857

emohr  changed:

   What|Removed |Added

 CC||fritzib...@gmx.net
 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED
  Flags||Brainstorm+

--- Comment #1 from emohr  ---
Thank you for reporting. Confirmed. It happen on Windows as well. I opened
issue https://invent.kde.org/kde/kdenlive/issues/331

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-nm] [Bug 410859] New: plasmashell hangs for multiple seconds while nmcli is also slow to respond

2019-08-12 Thread Alexander Potashev
https://bugs.kde.org/show_bug.cgi?id=410859

Bug ID: 410859
   Summary: plasmashell hangs for multiple seconds while nmcli is
also slow to respond
   Product: plasma-nm
   Version: 5.15.5
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: applet
  Assignee: jgrul...@redhat.com
  Reporter: aspotas...@gmail.com
  Target Milestone: ---

SUMMARY
plasmashell hangs for multiple seconds while nmcli is also slow to respond.

STEPS TO REPRODUCE
1. Somehow get to a situation when "nmcli c" takes multiple seconds to return
results.
2. Click on the plasma-nm icon in Plasma system tray.

OBSERVED RESULT
The panel is only opened after several seconds, at the same time when "nmcli c"
un-hangs if run in parallel on command line. The whole Plasma panel is
unresponsive, IOW it's not only the plasma-nm applet which is affected by this
kind of freeze.

EXPECTED RESULT
Plasma shell should be responsive at any point in time. Plasma-nm should also
open its popup immediately when clicking on the tray icon, even if
networkmanager is slow to respond. The popup window should probably indicate if
it's currently showing outdated information, e.g. more than several seconds
old.

SOFTWARE/OS VERSIONS
Operating System: Fedora 30
KDE Plasma Version: 5.15.5
KDE Frameworks Version: 5.59.0
Qt Version: 5.12.4
Kernel Version: 5.1.17-300.fc30.x86_64
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz
Memory: 15,4 ГиБ

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 410796] Convert to PNG - Fail to Process Item/Create File

2019-08-12 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=410796

--- Comment #7 from vikto...@gmail.com ---
OK, so when a RAW file is loaded with 16-bit, it defaults to Pro Photo.
And when a RAW file is loaded with 8-bit, it defaults to sRGB.

Would it be better to accept the user selection - you mean, ignore the defaults
and just use the DigiKam setup?

First may I point out that sRGB suits my task just fine. My purpose with trying
sRGB 2.1 was to try something else when some prints I ordered came back a bit
too red. However, in the interest of making Color Management less confusing, I
think there are three points of discussion here?

1. Since the Color Management Settings inside the Queue Settings were ignored
when I tried to export to PNG, when are they not ignored? Is it necessary for
these settings to be there after the Color Management section was moved from
the RAW settings to its own section in DigiKam 6.0?

I have not been able to find any documentation on when these settings apply.

2. Should DigiKam use default Color Space Profiles when it encounters external
Profiles? If it is broken, then it seems that the solution is to fix it.
However, my limited experience with Color Management tells me that the ability
to customize the working color space is not as important as the ability to
customize the final color space. 

It would be nice if there was a way to notify the user of such a behavior. In
the Editor, the Working color space can be shown in the Status bar. In the
Batch Process, the working color space (or soon to be forced working color
space) can be shown in a separate Color Management tab (like in DigiKam
Preferences) in the Queue Settings.  

3. What to do when a LibPNG does not support a color space profile?
It would have been nice if one of the 4 messages I received was "unsupported
color profile".

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 410760] While copying files which dolphin, the graphics hangs up

2019-08-12 Thread Moritz
https://bugs.kde.org/show_bug.cgi?id=410760

--- Comment #6 from Moritz  ---
I'd like ti add an stack, but I am on vacation.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 410852] Conflict between Kopete and any kde-l10n packages

2019-08-12 Thread Antonio Rojas
https://bugs.kde.org/show_bug.cgi?id=410852

Antonio Rojas  changed:

   What|Removed |Added

 CC||aro...@archlinux.org
 Resolution|--- |DOWNSTREAM
 Status|REPORTED|RESOLVED

--- Comment #1 from Antonio Rojas  ---
Please report this to your distribution

-- 
You are receiving this mail because:
You are watching all bug changes.

[lattedock] [Bug 410858] Full screen window goes under Latte Dock despite it's set to always visible

2019-08-12 Thread Andras
https://bugs.kde.org/show_bug.cgi?id=410858

Andras  changed:

   What|Removed |Added

 CC||andrasszerencs...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[lattedock] [Bug 410858] New: Full screen window goes under Latte Dock despite it's set to always visible

2019-08-12 Thread Andras
https://bugs.kde.org/show_bug.cgi?id=410858

Bug ID: 410858
   Summary: Full screen window goes under Latte Dock despite it's
set to always visible
   Product: lattedock
   Version: 0.9.1
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: andrasszerencs...@gmail.com
  Target Milestone: ---

Hi,
this bug is quite related I think:
https://bugs.kde.org/show_bug.cgi?id=348043

Latte Dock: 0.9.1
KDE neon 5.16
KDE Plasma version: 5.16.4
KDE Frameworks Version: 5.61.0
Qt Version: 5.12.3
Kernel Version: 4.15.5-55-generic

monitors' position if it's related info maybe:
Option "metamodes" "DVI-D-0: 1440x900_75 +0+1260 {ForceCompositionPipeline=On,
ForceFullCompositionPipeline=On}, HDMI-0: nvidia-auto-select +1440+0
{ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}, DP-0:
nvidia-auto-select +1440+1080 {ForceCompositionPipeline=On,
ForceFullCompositionPipeline=On}"

In the case above the problem occurs when additional monitor is set above the
primary one with Latte Dock placed on the top. It works when I switch between
always visible and other visibility settings but it's happening whenever Latte
is restarted.
Let me know if I should attach more details, thanks.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 348043] Maximized windows are covered by plasma panel in "always visible mode".

2019-08-12 Thread Andras
https://bugs.kde.org/show_bug.cgi?id=348043

Andras  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REOPENED|RESOLVED

--- Comment #49 from Andras  ---
Sorry, I'm just realized later this bug is about plasmashell and not latte dock
uhh, excuse me, please close it again

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 348043] Maximized windows are covered by plasma panel in "always visible mode".

2019-08-12 Thread Andras
https://bugs.kde.org/show_bug.cgi?id=348043

Andras  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|FIXED   |---
 CC||andrasszerencs...@gmail.com

--- Comment #48 from Andras  ---
(In reply to Martin Flöser from comment #45)
Hm, unfortunately yes it's happening on a newer plasma so I reopen this bug,
sorry if I'm wrong about it.
Latte Dock: 0.9.1
KDE neon 5.16
KDE Plasma version: 5.16.4
KDE Frameworks Version: 5.61.0
Qt Version: 5.12.3
Kernel Version: 4.15.5-55-generic

monitors' position if it's related info maybe:
Option "metamodes" "DVI-D-0: 1440x900_75 +0+1260 {ForceCompositionPipeline=On,
ForceFullCompositionPipeline=On}, HDMI-0: nvidia-auto-select +1440+0
{ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}, DP-0:
nvidia-auto-select +1440+1080 {ForceCompositionPipeline=On,
ForceFullCompositionPipeline=On}"

In this case the Problem occurs when additional monitor is set above the
primary one with latte dock placed on the top. It works when I switch between
always visible and other visibility settings.

Let me know if I should attach some specific details about this system, thanks.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 409954] KIO FTP: kioclient hangs while copying file over existing file [copy() did not call finished() or error()]

2019-08-12 Thread Simone
https://bugs.kde.org/show_bug.cgi?id=409954

Simone  changed:

   What|Removed |Added

 CC||simonebondi...@gmail.com

--- Comment #7 from Simone  ---
Can confirm. The dialogs either do not show or show after a long delay, but the
FTP connections stay alive and have to be manually closed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[LabPlot2] [Bug 410855] Repeated Random Values

2019-08-12 Thread Alexander Semke
https://bugs.kde.org/show_bug.cgi?id=410855

Alexander Semke  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/lab
   ||plot/c7d667f5be0fb68c7ab716
   ||a63f43516984f52ffc
 Status|CONFIRMED   |RESOLVED
   Version Fixed In||2.7

--- Comment #1 from Alexander Semke  ---
Git commit c7d667f5be0fb68c7ab716a63f43516984f52ffc by Alexander Semke.
Committed on 12/08/2019 at 18:03.
Pushed by asemke into branch 'master'.

[spreadsheet] seed the random number generator with the current time in
order not to generate repetitive numbers in the spreadsheet.
FIXED-IN: 2.7

M  +1-0ChangeLog
M  +1-0src/kdefrontend/spreadsheet/RandomValuesDialog.cpp

https://commits.kde.org/labplot/c7d667f5be0fb68c7ab716a63f43516984f52ffc

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 410841] IMAP folders are Offline

2019-08-12 Thread Juraj
https://bugs.kde.org/show_bug.cgi?id=410841

Juraj  changed:

   What|Removed |Added

 CC||sgd.or...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[LabPlot2] [Bug 410855] Repeated Random Values

2019-08-12 Thread Alexander Semke
https://bugs.kde.org/show_bug.cgi?id=410855

Alexander Semke  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 410856] wayland: kwin uses 100% cpu when idle

2019-08-12 Thread Miroslav Spehar
https://bugs.kde.org/show_bug.cgi?id=410856

--- Comment #2 from Miroslav Spehar  ---
*disabled baloo

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 410856] wayland: kwin uses 100% cpu when idle

2019-08-12 Thread Miroslav Spehar
https://bugs.kde.org/show_bug.cgi?id=410856

--- Comment #1 from Miroslav Spehar  ---
Created attachment 122091
  --> https://bugs.kde.org/attachment.cgi?id=122091=edit
kubuntu htop showing cpu usage

same thing happens on kubuntu with latest updates. i uninstalled
plasma-discover and disabled ubuntu.

cpu spike is triggered when kscreen locker kicks in

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 410857] New: grouped video and audio crashed while video is locked and audio deleted

2019-08-12 Thread Stanley
https://bugs.kde.org/show_bug.cgi?id=410857

Bug ID: 410857
   Summary: grouped video and audio crashed while video is locked
and audio deleted
   Product: kdenlive
   Version: 19.04.3
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: stanmichaelre...@gmail.com
  Target Milestone: ---

SUMMARY

grouped video and audio crashed while video is locked and audio deleted

STEPS TO REPRODUCE
1. group video and audio
2. lock the video on the timeline
3. delete the audio grouped to the video

OBSERVED RESULT

kdenlive become unresponsive

EXPECTED RESULT

would notify that it cant be deleted because the video that it is grouped is
locked and cant be deleted

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 4.19.60-1-MANJARO
(available in About System)
KDE Plasma Version: 5.16.3
KDE Frameworks Version: 5.60.0
Qt Version: 5.13.0

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 385880] Global Menu: does not work under wayland and causes a black screen when trying to enter its setting

2019-08-12 Thread fedor1113
https://bugs.kde.org/show_bug.cgi?id=385880

fedor1113  changed:

   What|Removed |Added

 CC||fedor1113-pub...@yandex.com

--- Comment #20 from fedor1113  ---
Confirm again.
Under Manjaro testing. With latte-dock.
Apart from that, Wayland experience seems to be pretty smooth.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 399923] Segmentation fault during face detection

2019-08-12 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=399923

--- Comment #170 from Maik Qualmann  ---
Please post the output of:

cat /proc/sys/vm/overcommit_memory

and:

cat /proc/sys/vm/overcommit_ratio

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 410767] Crash 5.4.0 appimage

2019-08-12 Thread Wood
https://bugs.kde.org/show_bug.cgi?id=410767

--- Comment #8 from Wood  ---
(In reply to Friedrich W. H. Kossebau from comment #7)
> I would be interested in the value of the QModelIndex arguments passed to
> QAbstractProxyModel::data and even more the one passed to
> QuickOpenModel::data. The r & c member values are of most interest to me.
> 
> Looking around at the code I found a possible code path which might lead to
> bogus ActionsQuickOpenItem objects due to out-of-bounds array access. But
> not sure yet how it could be reached or rather triggered from the backtrace,
> having the values of those QModelIndex arguments would at least prove that
> code path is reached here.
> 
> Still no idea why the quickopen code is run here at all. The
> QCoreApplicationPrivate::sendThroughObjectEventFilters might give a hint
> though,  perhaps something is broken in the logic of QuickOpenLineEdit which
> does a
> qApp->installEventFilter(this);
> call though tries to unregister when not active...

Unfortunately I lost the coredump file (got cleaned-up automatically this
weekend).

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 410856] New: wayland: kwin uses 100% cpu when idle

2019-08-12 Thread Miroslav Spehar
https://bugs.kde.org/show_bug.cgi?id=410856

Bug ID: 410856
   Summary: wayland: kwin uses 100% cpu when idle
   Product: kwin
   Version: 5.16.4
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: mspe...@gmail.com
  Target Milestone: ---

Created attachment 122090
  --> https://bugs.kde.org/attachment.cgi?id=122090=edit
htop showing cpu usage

SUMMARY
100% cpu usage when left to be idle in VM. 
when screen is activated, cpu usage drops.


STEPS TO REPRODUCE
1. install basic archlinux desktop with kde plasma
2. login into wayland session
3. disable baloo
4. leave the machine for a while

OBSERVED RESULT
100% cpu usage in kwin

EXPECTED RESULT
minimal cpu usage for kwin


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: latest
KDE Plasma Version: 5.16.4
KDE Frameworks Version: 5.60
Qt Version: 5.13

ADDITIONAL INFORMATION
journal | grep kwin

Aug 03 18:03:17 vm-arch kernel: kwin_wayland[450]: segfault at 128 ip
7f645d812e9c sp 7ffd89473ee0 error 4 in
libkwin.so.5.16.4[7f645d66f000+1eb000]
Aug 03 18:03:17 vm-arch kernel: audit: type=1701 audit(1564848197.113:57):
auid=1000 uid=1000 gid=998 ses=2 pid=450 comm="kwin_wayland"
exe="/usr/bin/kwin_wayland" sig=11 res=1
Aug 03 18:03:17 vm-arch audit[450]: ANOM_ABEND auid=1000 uid=1000 gid=998 ses=2
pid=450 comm="kwin_wayland" exe="/usr/bin/kwin_wayland" sig=11 res=1
Aug 03 18:05:32 vm-arch kernel: audit: type=1701 audit(1564848332.356:38):
auid=1000 uid=1000 gid=998 ses=2 pid=448 comm="QDBusConnection"
exe="/usr/bin/kwin_wayland" sig=11 res=1
Aug 03 18:05:32 vm-arch audit[448]: ANOM_ABEND auid=1000 uid=1000 gid=998 ses=2
pid=448 comm="QDBusConnection" exe="/usr/bin/kwin_wayland" sig=11 res=1
Aug 11 12:22:16 vm-arch audit[3307]: ANOM_ABEND auid=1000 uid=1000 gid=998
ses=2 pid=3307 comm="QDBusConnection" exe="/usr/bin/kwin_wayland" sig=11 res=1
Aug 11 12:22:16 vm-arch kernel: audit: type=1701 audit(1565518936.686:44):
auid=1000 uid=1000 gid=998 ses=2 pid=3307 comm="QDBusConnection"
exe="/usr/bin/kwin_wayland" sig=11 res=1
Aug 11 12:36:50 vm-arch audit[450]: ANOM_ABEND auid=1000 uid=1000 gid=998 ses=2
pid=450 comm="QDBusConnection" exe="/usr/bin/kwin_wayland" sig=11 res=1
Aug 11 12:36:50 vm-arch kernel: audit: type=1701 audit(1565519810.083:42):
auid=1000 uid=1000 gid=998 ses=2 pid=450 comm="QDBusConnection"
exe="/usr/bin/kwin_wayland" sig=11 res=1
Available platform plugins are:
wayland-org.kde.kwin.qpa, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc,
wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.
Aug 11 12:49:23 vm-arch kdeinit5[750]: kio_smb: dirp->name  kwin.txt  
"kwin.txt"  ' "" '   8
Aug 11 12:49:23 vm-arch kdeinit5[750]: kio_smb: updateCache  "/red/kwin.txt"
Aug 11 12:49:24 vm-arch kdeinit5[743]: kio_smb: dirp->name  kwin.txt  
"kwin.txt"  ' "" '   8
Aug 11 12:49:24 vm-arch kdeinit5[743]: kio_smb: updateCache  "/red/kwin.txt"
Aug 11 12:51:10 vm-arch systemsettings5[758]: org.kde.kcoreaddons: Error
loading plugin "kcm_kwindecoration" "The shared library was not found." 
Aug 11 12:51:10 vm-arch systemsettings5[758]: Module 'org.kde.kwin.decoration'
does not contain a module identifier directive - it cannot be protected from
external registrations.
Aug 11 12:51:13 vm-arch systemsettings5[758]: KActivitiesStats( 0x55c343144b00
) ResultModelPrivate::onResultScoreUpdated  result added:
"kcm:kwindecoration.desktop" score: 0 last: 1565520673 first: 1565520673
Aug 11 12:55:09 vm-arch audit[451]: ANOM_ABEND auid=1000 uid=1000 gid=998 ses=2
pid=451 comm="QDBusConnection" exe="/usr/bin/kwin_wayland" sig=11 res=1
Aug 11 12:55:09 vm-arch kernel: audit: type=1701 audit(1565520909.576:44):
auid=1000 uid=1000 gid=998 ses=2 pid=451 comm="QDBusConnection"
exe="/usr/bin/kwin_wayland" sig=11 res=1
Aug 11 13:27:19 vm-arch audit[450]: ANOM_ABEND auid=1000 uid=1000 gid=998 ses=2
pid=450 comm="QDBusConnection" exe="/usr/bin/kwin_wayland" sig=11 res=1
Aug 11 13:27:19 vm-arch kernel: audit: type=1701 audit(1565522839.420:45):
auid=1000 uid=1000 gid=998 ses=2 pid=450 comm="QDBusConnection"
exe="/usr/bin/kwin_wayland" sig=11 res=1
Aug 11 13:28:03 vm-arch audit[453]: ANOM_ABEND auid=1000 uid=1000 gid=998 ses=2
pid=453 comm="QDBusConnection" exe="/usr/bin/kwin_wayland" sig=11 res=1
Aug 11 13:28:03 vm-arch kernel: audit: type=1701 audit(1565522883.836:42):
auid=1000 uid=1000 gid=998 ses=2 pid=453 comm="QDBusConnection"
exe="/usr/bin/kwin_wayland" sig=11 res=1
   Available platform plugins are:
wayland-org.kde.kwin.qpa, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc,
wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.
Aug 11 13:29:02 vm-arch systemsettings5[660]: org.kde.kcoreaddons: Error
loading plugin "kcm_kwindecoration" "The 

[LabPlot2] [Bug 410855] New: Repeated Random Values

2019-08-12 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=410855

Bug ID: 410855
   Summary: Repeated Random Values
   Product: LabPlot2
   Version: 2.6.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: backend
  Assignee: alexander.se...@web.de
  Reporter: ameya.patwardha...@gmail.com
  Target Milestone: ---

Created attachment 122089
  --> https://bugs.kde.org/attachment.cgi?id=122089=edit
file which demonstrate repetitive random values

SUMMARY
Random values generated using the same function (eg. Flat, gaussian, etc.) are
always the same i.e. Row 1 always gives same value 'a', row 2 always gives same
value 'b', etc. This persists even across different files. 
See code KDE/labplot 
labplot/src/kdefrontend/spreadsheet/RandomValuesDialog.cpp
gsl_rng_set is the function that seeds the random value generator. This
function is not used anywhere leading to the repetitive values. The seed value
should be taken from the current time. This function should be used after
gsl_rng* r = gsl_rng_alloc(T);


STEPS TO REPRODUCE
1. New spreadsheet
2. Generate Data -> Random values
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 406502] Bad icon to go from 8 to 16 bits

2019-08-12 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=406502

Maik Qualmann  changed:

   What|Removed |Added

Version|6.1.0   |6.2.0

--- Comment #1 from Maik Qualmann  ---
@Alexandre

I assigned the bug to the Breeze team, why did you bring the bug back to
digiKam? We are not the creators of the icon set and can not fix this problem.

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 407797] Unseting act un new/unread crashes kmail

2019-08-12 Thread Kamil Dudka
https://bugs.kde.org/show_bug.cgi?id=407797

--- Comment #6 from Kamil Dudka  ---
(In reply to Kamil Dudka from comment #5)
The same scenario worked fine for me now with kmail 5.11.3 but I am not sure
whether it was upgrade of kmail or something else that fixed it for me...

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 410767] Crash 5.4.0 appimage

2019-08-12 Thread Friedrich W. H. Kossebau
https://bugs.kde.org/show_bug.cgi?id=410767

--- Comment #7 from Friedrich W. H. Kossebau  ---
I would be interested in the value of the QModelIndex arguments passed to
QAbstractProxyModel::data and even more the one passed to QuickOpenModel::data.
The r & c member values are of most interest to me.

Looking around at the code I found a possible code path which might lead to
bogus ActionsQuickOpenItem objects due to out-of-bounds array access. But not
sure yet how it could be reached or rather triggered from the backtrace, having
the values of those QModelIndex arguments would at least prove that code path
is reached here.

Still no idea why the quickopen code is run here at all. The
QCoreApplicationPrivate::sendThroughObjectEventFilters might give a hint
though,  perhaps something is broken in the logic of QuickOpenLineEdit which
does a
qApp->installEventFilter(this);
call though tries to unregister when not active...

-- 
You are receiving this mail because:
You are watching all bug changes.

[Breeze] [Bug 410854] New: Monochrome "computer" icon is used no matter what icon resolution is used

2019-08-12 Thread Efe Ciftci
https://bugs.kde.org/show_bug.cgi?id=410854

Bug ID: 410854
   Summary: Monochrome "computer" icon is used no matter what icon
resolution is used
   Product: Breeze
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: Icons
  Assignee: visual-des...@kde.org
  Reporter: efecif...@gmail.com
CC: kain...@gmail.com
  Target Milestone: ---

Created attachment 122088
  --> https://bugs.kde.org/attachment.cgi?id=122088=edit
A screenshot which shows how monochrome "computer" icon is used in higher icon
resolutions

SUMMARY
There are two variations of "computer" icon in Breeze icon theme: a monochrome
icon for 16x16 and 22x22 resolutions and a colorful icon for 32x32 and higher
resolutions. The "computer" icon stays monochrome no matter what zoom level is
used. Tested with Dolphin (places panel, folder contents) and Desktop.

STEPS TO REPRODUCE
1a. Choose "Create New" -> "Link to Application" in Dolphin/Desktop
or;
1b. Choose "Add Entry" in Dolphin places panel
2. From the list to choose an icon, select "Devices" -> "computer"
3. Accept changes by clicking OK to close the properties window.

OBSERVED RESULT
The newly created link displays monochrome "computer" icon in all icon
resolutions (16x16, 22x22, 32x32, 48x48...)

EXPECTED RESULT
The newly created link should display monochrome "computer" icon only in 16x16
and 22x22 icon resolutions and colorful "computer" icon in resolutions 32x32
and higher.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE neon 5.16
KDE Plasma Version: 5.16.4
KDE Frameworks Version: 5.61.0
Qt Version: 5.12.3

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History

2019-08-12 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=401677

josh.phelps2...@gmail.com changed:

   What|Removed |Added

 CC||josh.phelps2...@gmail.com
  Alias||aidenxy

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 406502] Bad icon to go from 8 to 16 bits

2019-08-12 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=406502

caulier.gil...@gmail.com changed:

   What|Removed |Added

 CC||caulier.gil...@gmail.com
  Component|general |Usability-Themes

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 408880] bezier Curve error

2019-08-12 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=408880

--- Comment #5 from caulier.gil...@gmail.com ---
Please yes, try with current released 6.2.0, just to be sure. 

Thanks in advance

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 410815] Changing speed can only be done in single percentage increments using up-down.

2019-08-12 Thread emohr
https://bugs.kde.org/show_bug.cgi?id=410815

emohr  changed:

   What|Removed |Added

  Flags||Brainstorm+
 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1
 CC||fritzib...@gmx.net

--- Comment #1 from emohr  ---
Thank you for reporting. Issue is known
https://invent.kde.org/kde/kdenlive/issues/173. 

Workaround: Menu Timeline > Current Clip > Edit Duration -> here you can change
the speed by keyboard.

-- 
You are receiving this mail because:
You are watching all bug changes.

[korganizer] [Bug 410752] korganizer should use "better" intervals for reminders

2019-08-12 Thread Mathias Homann
https://bugs.kde.org/show_bug.cgi?id=410752

--- Comment #6 from Mathias Homann  ---
(In reply to Laurent Montel from comment #5)
> Do you think that it's ok for you to use same combobox in reminder dialog
> box ?

that would in my eyes be the perfect solution: why present the user with two
different versions of the same question...?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kstars] [Bug 410094] Kstars sometimes fails to wait for a slew to happen before slew is regarded as complete on the mount tool.

2019-08-12 Thread Jasem Mutlaq
https://bugs.kde.org/show_bug.cgi?id=410094

--- Comment #14 from Jasem Mutlaq  ---
Created attachment 122087
  --> https://bugs.kde.org/attachment.cgi?id=122087=edit
align debug patch

I don't think we should opt for the hack-workaround just yet. Can you please
apply this patch and share the log again? Hopefully it sheds more light on the
issue.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 410654] menu items and notification go blank

2019-08-12 Thread down hill
https://bugs.kde.org/show_bug.cgi?id=410654

--- Comment #2 from down hill  ---
 Chris,
a major upgrade on 8/11/19   1.x Gs  seemed to fix whatever was the problem.
sorry for the grief.
*DHF*


On Tuesday, August 6, 2019, 6:25:22 PM EDT, Christoph Feck
 wrote:  

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

Christoph Feck  changed:

          What    |Removed                    |Added

            Status|REPORTED                    |NEEDSINFO
        Resolution|---                        |WAITINGFORINFO

--- Comment #1 from Christoph Feck  ---
Please read https://community.kde.org/Get_Involved/Issue_Reporting

You didn't even state for which application you see an issue.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 410793] Settings dialog is too high for very space constrained screens

2019-08-12 Thread Boudewijn Rempt
https://bugs.kde.org/show_bug.cgi?id=410793

--- Comment #8 from Boudewijn Rempt  ---
No, you should either use a nightly build, or wait until this change makes it
into the next release -- end of this month, actually. Nightlies are here:
https://binary-factory.kde.org/job/Krita_Nightly_Windows_Build/

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 410853] New: Discover

2019-08-12 Thread Auriga
https://bugs.kde.org/show_bug.cgi?id=410853

Bug ID: 410853
   Summary: Discover
   Product: Discover
   Version: 5.16.4
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: discover
  Assignee: lei...@leinir.dk
  Reporter: aur...@gmx.com
CC: aleix...@kde.org
  Target Milestone: ---

SUMMARY
When I start Discover, a text appears indicating that it has no engine.
Thanks for your help.

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 410767] Crash 5.4.0 appimage

2019-08-12 Thread Friedrich W. H. Kossebau
https://bugs.kde.org/show_bug.cgi?id=410767

--- Comment #6 from Friedrich W. H. Kossebau  ---
(In reply to David Redondo from comment #5)
> This happens not only in the Appimage. Just hit this when using the neon
> package.

Same backtrace? Do you remember what you did?

The best idea I have so far is that QuickOpenModel::data() does not protect
against being called with an invalid index (here coming from direct mapping
call from QAbstractProxyModel), or rather QuickOpenModel::getItem not against
being called with row == -1, where it would return a out-of-array-bounds item
for ActionsQuickOpenProvider then. Though only if that provider is first in the
list, where it gets added as last and would be only first if all the othes are
disabled...

-- 
You are receiving this mail because:
You are watching all bug changes.

[Falkon] [Bug 410835] FALKON_PLUGIN_PATH is not actually treated as a search path

2019-08-12 Thread Alexei Robyn
https://bugs.kde.org/show_bug.cgi?id=410835

--- Comment #2 from Alexei Robyn  ---
My intended use is packaging Falkon and third-party plugins separately. I'm
looking at improving the packaging of Falkon in nixpkgs to account for
third-party plugins, and the Nix approach to packaging stores individual
packages in isolated FHS-like subtrees.

Right now I have a kind of meta package that symlinks a set of plugins into a
single directory, and wraps falkon to set $FALKON_PLUGIN_PATH to that directory
of symlinks. If it were instead treated as a search path, I could just point it
directly to the individual plugin directories, which would be preferable.

On non-Nix-based distros, I could also see this being useful for allowing
people to use plugins from both system and user sources.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 406502] Bad icon to go from 8 to 16 bits

2019-08-12 Thread Alexandre Belz
https://bugs.kde.org/show_bug.cgi?id=406502

Alexandre Belz  changed:

   What|Removed |Added

 OS|All |MS Windows
   Platform|unspecified |MS Windows

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 406502] Bad icon to go from 8 to 16 bits

2019-08-12 Thread Alexandre Belz
https://bugs.kde.org/show_bug.cgi?id=406502

Alexandre Belz  changed:

   What|Removed |Added

Version|unspecified |6.1.0
   Assignee|visual-des...@kde.org   |digikam-bugs-n...@kde.org
  Component|Icons   |general
Product|Breeze  |digikam

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 410852] New: Conflict between Kopete and any kde-l10n packages

2019-08-12 Thread Mark Fraser
https://bugs.kde.org/show_bug.cgi?id=410852

Bug ID: 410852
   Summary: Conflict between Kopete and any kde-l10n packages
   Product: kopete
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kopete-bugs-n...@kde.org
  Reporter: mfraz74+...@gmail.com
  Target Milestone: ---

If I try to install a kde-l10n package such as kde-l10n-engb with kopete-data
installed it isn't allowed due to package breakage.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.16.4
KDE Frameworks Version: 5.60.0
Qt Version: 5.12.2

ADDITIONAL INFORMATION

aptitude why-not kde-l10n-engb
i   kopete  Depends kopete-data (= 4:18.12.3-0ubuntu2)
iBA kopete-data Breaks  kde-l10n-engb (< 4:18.04.0~)

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 408880] bezier Curve error

2019-08-12 Thread Alexandre Belz
https://bugs.kde.org/show_bug.cgi?id=408880

--- Comment #4 from Alexandre Belz  ---
I understand @Maik, but here it's not a complex curve with many points.
I'm just trying to setup a classical "S Curve" , with Black levels starting a
higher than (0;0;0).
I succeeded to do it with Darktable but not with Digikam.

I've seen you've released a new code.
Should I retry with official release 6.2 recently published ?

Alex

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 410793] Settings dialog is too high for very space constrained screens

2019-08-12 Thread Galaxy Silver
https://bugs.kde.org/show_bug.cgi?id=410793

--- Comment #7 from Galaxy Silver  ---
 Hello! I appreciate that the both of you are replying to my bug, but I don't
know what can I do with the latest info/link you provided to me? Should I
change the app's code? I mean, I'm fine with the buttons being blocked rather
than ruining the whole app because I'm not tech-savvy enough, I never changed
or copied and pasted code to Krita before, despite it being open source.
(Also, yes, the display scaling isn't helping, mine is in the lowest setting,
if you're wondering...)On Monday, August 12, 2019, 02:08:48 PM GMT+7,
Boudewijn Rempt  wrote:  

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

Boudewijn Rempt  changed:

          What    |Removed                    |Added

      Latest Commit|                            |https://invent.kde.org/kde/
                  |                            |krita/commit/14d3ca274c700d
                  |                            |369b7f3094e35dcc4a45cfc509
            Status|CONFIRMED                  |RESOLVED
        Resolution|---                        |FIXED

--- Comment #6 from Boudewijn Rempt  ---
Git commit 14d3ca274c700d369b7f3094e35dcc4a45cfc509 by Boudewijn Rempt.
Committed on 12/08/2019 at 07:08.
Pushed by rempt into branch 'master'.

Split the display settings page in tabs

M  +545  -458  libs/ui/forms/wdgdisplaysettings.ui

https://invent.kde.org/kde/krita/commit/14d3ca274c700d369b7f3094e35dcc4a45cfc509

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kcoreaddons] [Bug 410851] New: K_PLUGIN_FACTORY_DECLARATION_WITH_BASEFACTORY_SKEL doesn't use basefactory

2019-08-12 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=410851

Bug ID: 410851
   Summary: K_PLUGIN_FACTORY_DECLARATION_WITH_BASEFACTORY_SKEL
doesn't use basefactory
   Product: frameworks-kcoreaddons
   Version: 5.61.0
  Platform: Other
OS: FreeBSD
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mp...@kde.org
  Reporter: gr...@kde.org
CC: kdelibs-b...@kde.org
  Target Milestone: ---

The macro K_PLUGIN_FACTORY_DECLARATION_WITH_BASEFACTORY_SKEL defined in
kpluginfactory.h takes a parameter baseFactory, which isn't used. Although it's
not documented, the name suggests that it should be used when using factories
derived from a subclass of KPluginFactory. K_PLUGIN_FACTORY_DECLARATION calls
that macro with baseFactory set to KPluginFactory, so that doesn't seem all-too
far-fetched.

Because it doesn't use baseFactory, using subclasses of KPluginFactory is more
work than strictly necessary (e.g. instead of using
K_PLUGIN_FACTORY_DECLARATION_WITH_BASEFACTORY_SKEL you need to write out the
definition it has, substituting the base class in the right spot).

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-nm] [Bug 410703] [Wayland] Standalone plasma-nm KCM freezes after manual resizing

2019-08-12 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=410703

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In||5.17.0

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 409954] KIO FTP: kioclient hangs while copying file over existing file [copy() did not call finished() or error()]

2019-08-12 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=409954

Nate Graham  changed:

   What|Removed |Added

 CC||nortex...@gmail.com

--- Comment #6 from Nate Graham  ---
*** Bug 410357 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 410357] Dolphin no longer asks to overwrite files on remote ftp server and the copy hangs

2019-08-12 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=410357

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org
 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED

--- Comment #4 from Nate Graham  ---


*** This bug has been marked as a duplicate of bug 409954 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kinit] [Bug 410119] Discover app store closed itself and Plasma shown a notification about kinit5 crash

2019-08-12 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=410119

Patrick Silva  changed:

   What|Removed |Added

Version|5.60.0  |5.61.0

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 410838] [regression] Using move tool with lab 16 bit float is slow, and hangs krita when enabling instant preview

2019-08-12 Thread Dmitry Kazakov
https://bugs.kde.org/show_bug.cgi?id=410838

Dmitry Kazakov  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/kde/
   ||krita/commit/dcdef2ea1163a5
   ||b764e4bb9acebed95a0c52101f
 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Dmitry Kazakov  ---
Git commit dcdef2ea1163a5b764e4bb9acebed95a0c52101f by Dmitry Kazakov.
Committed on 12/08/2019 at 13:45.
Pushed by dkazakov into branch 'master'.

Fix lags in Move Tool when using tablet device

Now the Move Tool uses the same FSP-limiting compression as the freehand
tool does. The relevant code has been moved into a special class
KisAsyncronousStrokeUpdateHelper, which implements a logic of issuing
threshold events.

Bascially, all the sources of event (tablet move and async update from
KisAsyncronousStrokeUpdateHelper) now try to initiate a canvas update.
If enough time has passed and previous updates has finished, then a new
update is started.

One more important change: now actual layer offset change is executed in
the same exclusive job as the updates (with limited FPS), therefore, it
avoids garbage-looking leftovers of the intemediate move states.

M  +5-0libs/image/kis_image.cc
M  +8-0libs/image/kis_image.h
M  +2-0libs/image/kis_image_interfaces.h
M  +5-0libs/image/kis_update_scheduler.cpp
M  +2-0libs/image/kis_update_scheduler.h
M  +1-0libs/ui/CMakeLists.txt
M  +3-1libs/ui/tests/FreehandStrokeBenchmark.cpp
M  +2-1libs/ui/tests/KisPaintOnTransparencyMaskTest.cpp
M  +2-1libs/ui/tests/freehand_stroke_test.cpp
A  +76   -0libs/ui/tool/KisAsyncronousStrokeUpdateHelper.cpp [License:
GPL (v2+)]
A  +85   -0libs/ui/tool/KisAsyncronousStrokeUpdateHelper.h [License:
GPL (v2+)]
M  +2-1libs/ui/tool/kis_figure_painting_tool_helper.cpp
M  +9-20   libs/ui/tool/kis_tool_freehand_helper.cpp
M  +0-1libs/ui/tool/kis_tool_freehand_helper.h
M  +4-2libs/ui/tool/strokes/freehand_stroke.cpp
M  +0-23   libs/ui/tool/strokes/freehand_stroke.h
M  +45   -11   libs/ui/tool/strokes/move_stroke_strategy.cpp
M  +16   -2libs/ui/tool/strokes/move_stroke_strategy.h
M  +3-2libs/ui/widgets/kis_preset_live_preview_view.cpp
M  +15   -0plugins/tools/basictools/kis_tool_move.cc
M  +3-0plugins/tools/basictools/kis_tool_move.h

https://invent.kde.org/kde/krita/commit/dcdef2ea1163a5b764e4bb9acebed95a0c52101f

-- 
You are receiving this mail because:
You are watching all bug changes.

[neon] [Bug 410779] Slow or unreliable downloads of KDE Neon release images and lack of adoption of Metalink

2019-08-12 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=410779

Nate Graham  changed:

   What|Removed |Added

 Resolution|NOT A BUG   |MOVED

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 410850] KMail hangs when retreiving messages, then crashes on "Quit"

2019-08-12 Thread Jason Franklin
https://bugs.kde.org/show_bug.cgi?id=410850

--- Comment #1 from Jason Franklin  ---
Created attachment 122084
  --> https://bugs.kde.org/attachment.cgi?id=122084=edit
New crash information added by DrKonqi

kmail (5.9.3) using Qt 5.11.3

- What I was doing when the application crashed:

This is the same as my earlier report.  I was reading email from my linked
Gmail account, and KMail
stopped in the middle of retreiving messages.

- Unusual behavior I noticed:

KMail showed a message that it was retreiving messages and then did nothing. 
With File >Quit
KMail generated a crash report.

- Custom settings of the application:

Encrypted/signed email for most communication and a local mail setup that
stores most of my
deleted/archived email.

-- Backtrace (Reduced):
#6  0x7f5d5d95ecd4 in QWebEngineView::page() const () from
/lib/x86_64-linux-gnu/libQt5WebEngineWidgets.so.5
#7  0x7f5d5d95edf1 in QWebEngineView::setHtml(QString const&, QUrl const&)
() from /lib/x86_64-linux-gnu/libQt5WebEngineWidgets.so.5
#8  0x7f5d60ff9dcf in MessageViewer::ViewerPrivate::displaySplashPage
(this=0x56325c318750, templateName=..., data=..., domain=...) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qchar.h:88
#9  0x7f5d60ffa21f in MessageViewer::ViewerPrivate::displaySplashPage
(this=0x56325c318750, message=...) at
./messageviewer/src/viewer/viewer_p.cpp:839
#10 0x7f5d60ffdb53 in MessageViewer::ViewerPrivate::itemFetchResult
(this=0x56325c318750, job=) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qchar.h:88

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 410850] KMail hangs when retreiving messages, then crashes on "Quit"

2019-08-12 Thread Jason Franklin
https://bugs.kde.org/show_bug.cgi?id=410850

Jason Franklin  changed:

   What|Removed |Added

 CC||jason.frank...@quoininc.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 410850] New: KMail hangs when retreiving messages, then crashes on "Quit"

2019-08-12 Thread Jason Franklin
https://bugs.kde.org/show_bug.cgi?id=410850

Bug ID: 410850
   Summary: KMail hangs when retreiving messages, then crashes on
"Quit"
   Product: kmail2
   Version: 5.9.3
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: jason.frank...@quoininc.com
  Target Milestone: ---

Application: kmail (5.9.3)

Qt Version: 5.11.3
Frameworks Version: 5.54.0
Operating System: Linux 4.19.0-5-amd64 x86_64
Distribution: Debian GNU/Linux 10 (buster)

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

My KMail set up connects to a Gmail account, and I was just checking my mail. 
I switched folders
a couple of times as usual.

- Unusual behavior I noticed:

I saw a multi-colored message that read "KMail is retreiving messages" or
something to that effect.
Then, it just sat there and did nothing.

I then went to File > Quit to stop the application, and the crash report was
generated.

- Custom settings of the application:

I use encrypted/signed mail for most of my communication. I also have a local
mail folder that stores most
mail when it's been archived or deleted.

The crash can be reproduced sometimes.

-- 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 0x7f5c1cd7ef00 (LWP 1473))]

Thread 28 (Thread 0x7f5bfca49700 (LWP 2345)):
#0  futex_reltimed_wait_cancelable (private=0, reltime=0x7f5bfca48400,
expected=0, futex_word=0x7f5bfca485e8) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  __pthread_cond_wait_common (abstime=0x7f5bfca484a0, mutex=0x7f5bfca48598,
cond=0x7f5bfca485c0) at pthread_cond_wait.c:533
#2  __pthread_cond_timedwait (cond=0x7f5bfca485c0, mutex=0x7f5bfca48598,
abstime=0x7f5bfca484a0) at pthread_cond_wait.c:667
#3  0x7f5c2aea2a37 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f5c2aea530a in base::WaitableEvent::TimedWaitUntil(base::TimeTicks
const&) () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f5c2aea53f2 in base::WaitableEvent::TimedWait(base::TimeDelta
const&) () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7f5c2aea9981 in
base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) ()
from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7f5c2aeaae61 in base::internal::SchedulerWorker::Thread::ThreadMain()
() from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#8  0x7f5c2aeb3c81 in base::(anonymous namespace)::ThreadFunc(void*) ()
from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#9  0x7f5c31451fa3 in start_thread (arg=) at
pthread_create.c:486
#10 0x7f5c33a1d4cf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 27 (Thread 0x7f5be37fe700 (LWP 2343)):
#0  futex_reltimed_wait_cancelable (private=0, reltime=0x7f5be37fd400,
expected=0, futex_word=0x7f5be37fd5e8) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  __pthread_cond_wait_common (abstime=0x7f5be37fd4a0, mutex=0x7f5be37fd598,
cond=0x7f5be37fd5c0) at pthread_cond_wait.c:533
#2  __pthread_cond_timedwait (cond=0x7f5be37fd5c0, mutex=0x7f5be37fd598,
abstime=0x7f5be37fd4a0) at pthread_cond_wait.c:667
#3  0x7f5c2aea2a37 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f5c2aea530a in base::WaitableEvent::TimedWaitUntil(base::TimeTicks
const&) () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f5c2aea53f2 in base::WaitableEvent::TimedWait(base::TimeDelta
const&) () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7f5c2aea9981 in
base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) ()
from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7f5c2aeaae61 in base::internal::SchedulerWorker::Thread::ThreadMain()
() from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#8  0x7f5c2aeb3c81 in base::(anonymous namespace)::ThreadFunc(void*) ()
from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#9  0x7f5c31451fa3 in start_thread (arg=) at
pthread_create.c:486
#10 0x7f5c33a1d4cf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 26 (Thread 0x7f5b7bfff700 (LWP 1703)):
#0  futex_wait_cancelable (private=0, expected=0, futex_word=0x7f5c28a0afb8) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x7f5c28a0af68,
cond=0x7f5c28a0af90) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x7f5c28a0af90, mutex=0x7f5c28a0af68) at
pthread_cond_wait.c:655
#3  0x7f5c28914e6a in ?? () from /lib/x86_64-linux-gnu/libQt5Script.so.5
#4  0x7f5c28914e89 in ?? () from 

  1   2   >