[kdevelop] [Bug 365437] Rename local variable using "Rename" assistant breaks code

[Igor Kushnir]

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

Igor Kushnir  changed:

   What|Removed |Added

 CC||igor...@meta.ua

--- Comment #6 from Igor Kushnir  ---
I have experienced similar Rename bugs in KDevelop 5.5.0:
1) it always inserted spaces between the renamed variable and parentheses;
2) sometimes it inserted out-of-place braces.

After some debugging I determined that Source Formatter kicks in during the
Rename variable refactoring in DocumentChangeSetPrivate::generateNewText():

if (formatter && (formatPolicy == DocumentChangeSet::AutoFormatChanges
  || formatPolicy ==
DocumentChangeSet::AutoFormatChangesKeepIndentation)) {
... }


GrepOutputModel sets formatPolicy to DocumentChangeSet::NoAutoFormat, so
Find/Replace in Files does not cause such bugs. Neither does simple
KTextEditor's Replace within a file.

It turned out that my Source Formatter for the C++ Language was set to the
default Artistic Style->1TBS. After switching to Artistic Style->Qt, at least
the easily reproducible space insertion issue is gone. Not sure about the
spurious braces yet.

Piotr, have you tried reproducing this bug and Bug 317299 with different C++
Source Formatters configured in KDevelop settings?

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

[ark] [Bug 419009] Cann't create 7z archive for folder

[Konstantin]

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

--- Comment #5 from Konstantin  ---
I found why archive not created:
If exit link in folder (content) as example:
 hard  …  wineTMP  prefix  dosdevices  ls -l
итого 0
lrwxrwxrwx 1 hard hard 10 мар 20 10:01 c: -> ../drive_c
lrwxrwxrwx 1 hard hard 10 мар 20 10:01 com1 -> /dev/ttyS0
lrwxrwxrwx 1 hard hard 10 мар 20 10:01 com10 -> /dev/ttyS9
lrwxrwxrwx 1 hard hard 11 мар 20 10:01 com11 -> /dev/ttyS10
lrwxrwxrwx 1 hard hard 11 мар 20 10:01 com12 -> /dev/ttyS11
lrwxrwxrwx 1 hard hard 11 мар 20 10:01 com13 -> /dev/ttyS12
lrwxrwxrwx 1 hard hard 11 мар 20 10:01 com14 -> /dev/ttyS13

Or any other links

 hard  …  wineTMP  prefix  drive_c  ls -l
итого 24
lrwxrwxrwx  1 hard hard   20 мар 20 10:01  Games -> ../../game_info/data
drwxrwxr-x  3 hard hard 4096 мар  8 16:34  ProgramData

If i remove it all is ok, archive created.

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

[ark] [Bug 419009] Cann't create 7z archive for folder

[Konstantin]

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

--- Comment #4 from Konstantin  ---
When create tar.gz - all is ok for selected folder
When create 7z - not
But i check for empty folder, and try archive it - all is ok. Maybe this is
p7zip bug.
I try found why my folder not archived.

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

[ark] [Bug 419009] Cann't create 7z archive for folder

[Konstantin]

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

--- Comment #3 from Konstantin  ---
 hard  ~  ls -l /usr/bin/7z
-rwxr-xr-x 1 root root 39 авг 10  2019 /usr/bin/7z

p7zip-full/focal,now 16.02+dfsg-7 amd64 [installed]
p7zip-rar/focal,now 16.02-3 amd64 [installed]
p7zip/focal,now 16.02+dfsg-7 amd64 [installed]

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

[ark] [Bug 419009] Cann't create 7z archive for folder

[Konstantin]

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

--- Comment #2 from Konstantin  ---
Created attachment 126901
  --> https://bugs.kde.org/attachment.cgi?id=126901=edit
Ark Modules

Ark Modules

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

[ark] [Bug 419009] Cann't create 7z archive for folder

[Konstantin]

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

Konstantin  changed:

   What|Removed |Added

Summary|Cann't crate 7z archive for |Cann't create 7z archive
   |folder  |for folder

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

[kio-extras] [Bug 364708] kioexec error on sftp

[Fred Wells]

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

Fred Wells  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED

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

[plasmashell] [Bug 418318] The hover state should be clarifying, but not main

[Bug Janitor Service]

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

--- 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.

[kio-extras] [Bug 364708] kioexec error on sftp

[Bug Janitor Service]

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

--- Comment #3 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.

[kio-extras] [Bug 418472] Duplicating files on remote connections results in the copy having ".part" in the name

[Bug Janitor Service]

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

--- 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.

[kio-extras] [Bug 376867] sftp connect issue "Failed to resolve hostname = (Name or service not known)"

[Bug Janitor Service]

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

--- Comment #6 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.

[krita] [Bug 418925] Audio bug

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

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

--- Comment #9 from Bug Janitor Service  ---
Thanks for your comment!

Automatically switching the status of this bug to REPORTED so that the KDE team
knows that the bug is ready to get confirmed.

In the future you may also do this yourself when providing needed information.

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

[kio-extras] [Bug 395739] SFTP hangs after restarting remote device

[Bug Janitor Service]

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

--- 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.

[kio-extras] [Bug 406691] Can't follow symbolic links in SFTP locations

[Bug Janitor Service]

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

--- Comment #3 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.

[krita] [Bug 344142] Changing the Advanced color selector resets OCIO config

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #6 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now 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

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

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

[plasmashell] [Bug 411729] Greek accents and dead keys do not work in Debian Stable

[Jose María Galdós]

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

Jose María Galdós  changed:

   What|Removed |Added

 CC||txemafi...@gmail.com

--- Comment #3 from Jose María Galdós  ---
Same problem in Spanish tilde keys (áéíóú). Only affects Wayland, Xwayland
applications work correctly.


Operating System: Manjaro Linux 
KDE Plasma Version: 5.18.3
KDE Frameworks Version: 5.67.0
Qt Version: 5.14.1
Kernel Version: 5.5.8-1-MANJARO
Window System: Wayland

Locale:
  System Locale: LANG=es_MX.UTF-8
  LC_TIME=es_ES.UTF-8
   VC Keymap: us-acentos
  X11 Layout: us
   X11 Model: pc105
 X11 Variant: intl

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

[kio-extras] [Bug 404890] copy file failed on remote sftp host

[ovl]

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

ovl  changed:

   What|Removed |Added

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

--- Comment #5 from ovl  ---
Yes, the problem still exists in kde-extras 19.12.3-1

libssh - 0.9.3-1
linssh2 - 1.9.0-2

I can reproduce this with dolphin as well, copy/paste lead to zero size file.

Last version kde-extras without this problem was 18.08.3-2

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

[elisa] [Bug 416131] Elisa doesn't export the Album Art to the Media Player applet

[D. Debnath]

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

--- Comment #13 from D. Debnath  ---
I tried to run kdesrc-build and it's failing to install (compiled successfully)
with the following error:
CMake Error at cmake_install.cmake:41 (file):
file INSTALL cannot copy file
"/home/debnath/kde/src/elisa/org.kde.elisa.desktop" to
"/usr/share/applications/org.kde.elisa.desktop": Permission denied.

I believe, this is trying to replace the desktop file of my stable Elisa app
from my distro, which is not what it should be doing.

​Also, I tried to kdesrc-run elisa which gives the following error:
QQmlApplicationEngine failed to load component
qrc:/qml/ElisaMainWindow.qml:182:13: Type HeaderBar unavailable
qrc:/qml/HeaderBar.qml:307:25: Type SimplePlayListView unavailable
qrc:/qml/SimplePlayListView.qml:100:13: Type PlayListEntry unavailable
qrc:/qml/PlayListEntry.qml:72:27: Type MediaTrackMetadataView unavailable
qrc:/qml/MediaTrackMetadataView.qml:49:5: EditableTrackMetadataModel is not a
type

From: Matthieu Gallien 
Sent: 20 March 2020 3:04 AM
To: d_debn...@outlook.com 
Subject: [elisa] [Bug 416131] Elisa doesn't export the Album Art to the Media
Player applet

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

--- Comment #12 from Matthieu Gallien  ---
https://invent.kde.org/kde/elisa/-/merge_requests/105 is a candidate fix
pending review.

Please test if you can ?

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

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

[lattedock] [Bug 418766] Latte dock is randomly crashing when I interact with it ever since the 0.9.9 update

[bugzilla_noreply]

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

andresdor...@gmail.com changed:

   What|Removed |Added

 Resolution|UPSTREAM|---
 Status|RESOLVED|REOPENED

--- Comment #9 from andresdor...@gmail.com ---
this started to come back even though i been using the plasma theme for the
window buttons i dont even think this has to do with windows button applet
anymore

https://gist.github.com/zany130/a6939fd4bf3607cb7ccafb34b9f721aa

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

[kontact] [Bug 419035] New: Kontact Crashes Opening Settings

[Bryant Stafford]

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

Bug ID: 419035
   Summary: Kontact Crashes Opening Settings
   Product: kontact
   Version: 5.11.3
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: bryant.staff...@outlook.com
  Target Milestone: ---

Application: kontact (5.11.3)

Qt Version: 5.13.2
Frameworks Version: 5.67.0
Operating System: Linux 5.5.8-200.fc31.x86_64 x86_64
Distribution: Fedora 31 (KDE Plasma)

-- Information about the crash:
- What I was doing when the application crashed: Setting up my email accounts,
tried to open settings to change the settings on one account.

- Custom settings of the application: None that I'm aware of.

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc9ccbf6940 (LWP 45067))]

Thread 37 (Thread 0x7fc95b7fe700 (LWP 45527)):
#0  0x7fc9d9a4a07a in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fc9d2ceb5a6 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () from /lib64/libQt5WebEngineCore.so.5
#2  0x7fc9d2cebf83 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks
const&) () from /lib64/libQt5WebEngineCore.so.5
#3  0x7fc9d2cec101 in base::WaitableEvent::TimedWait(base::TimeDelta
const&) () from /lib64/libQt5WebEngineCore.so.5
#4  0x7fc9d2ca3c81 in
base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) ()
from /lib64/libQt5WebEngineCore.so.5
#5  0x7fc9d2ca6b52 in base::internal::SchedulerWorker::RunWorker() () from
/lib64/libQt5WebEngineCore.so.5
#6  0x7fc9d2ca7414 in base::internal::SchedulerWorker::RunPooledWorker() ()
from /lib64/libQt5WebEngineCore.so.5
#7  0x7fc9d2cee42a in base::(anonymous namespace)::ThreadFunc(void*) ()
from /lib64/libQt5WebEngineCore.so.5
#8  0x7fc9d9a434e2 in start_thread () from /lib64/libpthread.so.0
#9  0x7fc9daa6e6d3 in clone () from /lib64/libc.so.6

Thread 36 (Thread 0x7fc87191b700 (LWP 45185)):
#0  0x7fc9d9a49d45 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fc9d2ceb4ac in base::ConditionVariable::Wait() () from
/lib64/libQt5WebEngineCore.so.5
#2  0x7fc9d2cebf90 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks
const&) () from /lib64/libQt5WebEngineCore.so.5
#3  0x7fc9d2cec0bf in base::WaitableEvent::Wait() () from
/lib64/libQt5WebEngineCore.so.5
#4  0x7fc9d2ca3c56 in
base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) ()
from /lib64/libQt5WebEngineCore.so.5
#5  0x7fc9d2ca6eeb in base::internal::SchedulerWorker::RunWorker() () from
/lib64/libQt5WebEngineCore.so.5
#6  0x7fc9d2ca7454 in base::internal::SchedulerWorker::RunSharedWorker() ()
from /lib64/libQt5WebEngineCore.so.5
#7  0x7fc9d2cee42a in base::(anonymous namespace)::ThreadFunc(void*) ()
from /lib64/libQt5WebEngineCore.so.5
#8  0x7fc9d9a434e2 in start_thread () from /lib64/libpthread.so.0
#9  0x7fc9daa6e6d3 in clone () from /lib64/libc.so.6

Thread 35 (Thread 0x7fc872b81700 (LWP 45150)):
#0  0x7fc9d9048887 in g_main_context_acquire () from
/lib64/libglib-2.0.so.0
#1  0x7fc9d90496d5 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7fc9d9049953 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7fc9db011843 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7fc9dafbb1db in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7fc9dae0bc45 in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7fc9dae0cd96 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#7  0x7fc9d9a434e2 in start_thread () from /lib64/libpthread.so.0
#8  0x7fc9daa6e6d3 in clone () from /lib64/libc.so.6

Thread 34 (Thread 0x7fc873382700 (LWP 45147)):
#0  0x7fc9dc23f589 in __tls_get_addr () from /lib64/ld-linux-x86-64.so.2
#1  0x7fc9dae0c33a in QThreadData::current(bool) () from
/lib64/libQt5Core.so.5
#2  0x7fc9db0116fe in postEventSourcePrepare(_GSource*, int*) () from
/lib64/libQt5Core.so.5
#3  0x7fc9d9049279 in g_main_context_check () from /lib64/libglib-2.0.so.0
#4  0x7fc9d90497c2 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#5  0x7fc9d9049953 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#6  0x7fc9db011843 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#7  0x7fc9dafbb1db in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#8  0x7fc9dae0bc45 in QThread::exec() () from /lib64/libQt5Core.so.5
#9  0x7fc9dae0cd96 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#10 0x7fc9d9a434e2 

[lattedock] [Bug 419034] New: Right click doesn’t work with Notes widget within Latte-dock

[Jazz]

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

Bug ID: 419034
   Summary: Right click doesn’t work with Notes widget within
Latte-dock
   Product: lattedock
   Version: 0.9.9
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: iguanamiy...@yahoo.com
  Target Milestone: ---

SUMMARY
I use latte-dock (as a panel) and I use a Note widget in it. When you try to
select a text in Notes widget and right click on it, the whole latte-dock
completely disappears. It gets weirder when you left-click the Notes widget
right after... the whole user experience of latte-dock gets messed up by that
bug on my Manjaro KDE/Plasma.

Any workaround, or solution for that?

STEPS TO REPRODUCE
1. Select any text in a Notes widget
2. Right click on it
3. Left click on Notes icon

OBSERVED RESULT
In step 2 the whole panel minimizes.
In step 3 it displays the widget with the right-click context menu and then
suddenly the whole dock minimizes again!


EXPECTED RESULT
The dock should not minimize after I click the widget (in steps 2, or 3).

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro KDE Plasma
KDE Plasma Version: 5.18.3
KDE Frameworks Version: 5.67.0
Qt Version: 5.14.1

ADDITIONAL INFORMATION

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

[systemsettings] [Bug 419033] OpenVPN passwords not saved (with libnm0 1.10.6 in Kubuntu 18.04)

[aslam karachiwala]

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

aslam karachiwala <4s...@mythicflow.com> changed:

   What|Removed |Added

   Platform|Ubuntu Packages |Kubuntu Packages

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

[systemsettings] [Bug 419033] OpenVPN passwords not saved (with libnm0 1.10.6 in Kubuntu 18.04)

[aslam karachiwala]

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

aslam karachiwala <4s...@mythicflow.com> changed:

   What|Removed |Added

 CC||4s...@mythicflow.com

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

[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus

[bugzilla_noreply]

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

sima...@gmail.com changed:

   What|Removed |Added

 CC||sima...@gmail.com

--- Comment #127 from sima...@gmail.com ---
(In reply to Luca Carlon from comment #125)
> This is the deb package I use on Kubuntu 19.10:
> https://bugfreeblog.page.link/libqt5gui5_5124. This package should be
> enough. If anything goes wrong, just do:
> 
> sudo apt-get install --reinstall libqt5gui5
> 
> to get the previous one back.
> If you prefer however not to rely on prebuilt packages, rebuilding is a
> matter of a few commands. You do not have to do anything to Plasma/kwin,
> there is no ABI change.

Hi! I was wondering if you could help me install the qt update you provided,
because when I try to open the file it shows this https://imgur.com/a/yGJ6YwB

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

[systemsettings] [Bug 419033] New: OpenVPN passwords not saved (with libnm0 1.10.6 in Kubuntu 18.04)

[aslam karachiwala]

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

Bug ID: 419033
   Summary: OpenVPN passwords not saved (with libnm0 1.10.6 in
Kubuntu 18.04)
   Product: systemsettings
   Version: 5.12.8
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_networkmanagement
  Assignee: jgrul...@redhat.com
  Reporter: 4s...@mythicflow.com
CC: plasma-b...@kde.org
  Target Milestone: ---

SUMMARY
After adding credentials to an OpenVPN connection configuration, if one selects
"Store password for this use only (encrypted)" and clicks Apply, the password
is not saved (e.g., in the designated, open kwallet). This is a recent change
in behavior.

STEPS TO REPRODUCE
1. System Settings > Connections
2. Pick an existing OpenVPN connection (or import a *.openvpn) that needs a
password but the password field is empty.
3. Enter the valid username and password in the respective fields.
4. Select "Store password for this use only (encrypted)" under the password
field.
5. Click the Apply button.
6. Close System Settings.
6. Try connecting to the OpenVPN connection.

OBSERVED RESULT
Dialog appears asking for password. Returning to the configuration panel of the
connection in System Settings > Connections shows an empty password field.

EXPECTED RESULT
The password dialog should not appear and the connection should be attempted
with the saved credentials. The username and password fields in connection
configuration panel should persistently show the credentials.

SOFTWARE/OS VERSIONS:
OS: Kubuntu 18.04
(available in About System)
KDE Plasma Version: 5.12.9
KDE Frameworks Version: 5.47.0
Qt Version: 5.9.5

ADDITIONAL INFORMATION
This is new behavior. Saving the password used to work correctly until
recently.

Related: Bug #396795 – This addresses a bug in a later version of
NetworkManager (1.20) in Ubuntu 19.10 and higher. This bug report is for
Kubuntu 18.04 (LTS).

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

[krita] [Bug 418282] Palette docker does not refresh correctly after a color is added from color picker

[Dmitry Kazakov]

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

Dmitry Kazakov  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/kde/
   ||krita/commit/43c06ea3a54761
   ||b965ba860981c3ce7fe24dc640
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Dmitry Kazakov  ---
Git commit 43c06ea3a54761b965ba860981c3ce7fe24dc640 by Dmitry Kazakov, on
behalf of Ashwin Dhakaita.
Committed on 19/03/2020 at 23:15.
Pushed by dkazakov into branch 'master'.

Fix Palette Docker to refresh correctly after a color is added from color
picker

The palette docker does not refresh correctly after any color
is added through color picker. Don't know if this is the right
approach to solve the problem but have solved it by setting
PaletteDocker as an observer for PaletteResourceServer and triggering
an update signal whenever the palette in the palette server is
updated using color picker.

M  +35   -0plugins/dockers/palettedocker/palettedocker_dock.cpp
M  +10   -1plugins/dockers/palettedocker/palettedocker_dock.h
M  +3-0plugins/tools/basictools/kis_tool_colorpicker.cc

https://invent.kde.org/kde/krita/commit/43c06ea3a54761b965ba860981c3ce7fe24dc640

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

[frameworks-baloo] [Bug 400704] Baloo indexing I/O introduces serious noticable delays

[Oded Arbel]

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

Oded Arbel  changed:

   What|Removed |Added

 CC||o...@geek.co.il

--- Comment #29 from Oded Arbel  ---
Same problem here - Baloo eats up all IO even when reporting "idle". This has
become a problem only in the last year or so. I'm using a pretty beefy i7
device with an NVME and while Baloo is enabled the computer often is slow and
freezes from time to time. Looking at CPU usage I see `baloo_file` takes
50%~80% CPU, and loadavg is around 3~4.5 (on 4 core system).

Looking at IO:
---8<---
$ pidstat -G balo[o] -dl 5 1; balooctl status
Linux 5.4.0-17-generic (vesho)  03/20/2020  _x86_64_(8 CPU)

12:48:52 AM   UID   PID   kB_rd/s   kB_wr/s kB_ccwr/s iodelay  Command
12:48:57 AM  1000 80482  26164.94  64858.96  0.00 170 
/usr/bin/baloo_file 

Average:  UID   PID   kB_rd/s   kB_wr/s kB_ccwr/s iodelay  Command
Average: 1000 80482  26164.94  64858.96  0.00 170 
/usr/bin/baloo_file 
Baloo File Indexer is running
Indexer state: Idle
Total files indexed: 297,288
Files waiting for content indexing: 0
Files failed to index: 0
Current size of index is 2.56 GiB
8<

So balooctl reports "Idle" while baloo_file pushes >60Mbit/sec to the drive and
does not insignificant reading.

In .xsession-errors log I can see a lot of messages like this:

8<
org.kde.baloo.engine: DocumentDB::get 307907124573241397 MDB_NOTFOUND: No
matching key/data pair found
8<

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

[elisa] [Bug 418072] Lyrics display sometimes doesn't show newlines

[Matthieu Gallien]

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

--- Comment #4 from Matthieu Gallien  ---
Do you by chance still have tracks showing the bug ?

I would like to be sure what is going on to fix it in Elisa code.

I will try to identify a possible fix even without such data.

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

[frameworks-baloo] [Bug 362622] baloo ignores "exclude folders[$e]=$HOME/"

[Oded Arbel]

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

Oded Arbel  changed:

   What|Removed |Added

 CC||o...@geek.co.il

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

[kwin] [Bug 419032] New: [Wayland] kwin uses VR headset as monitor

[bugzilla_noreply]

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

Bug ID: 419032
   Summary: [Wayland] kwin uses VR headset as monitor
   Product: kwin
   Version: 5.18.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: farmb...@googlemail.com
  Target Milestone: ---

SUMMARY
When attaching a HMD device to my graphics card kwin will use it as monitor.

STEPS TO REPRODUCE
1. Start KDE with Plasma/Wayland session
2. attach a HMD device (like Vavle index)
3. 

OBSERVED RESULT
all applications are switched to the "second monitor"

EXPECTED RESULT
kwin ignores the HMD display

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Gentoo, Kernel 5.5.6
(available in About System)
KDE Plasma Version: 5.18.3
KDE Frameworks Version: 5.68.0
Qt Version: 5.14.1

ADDITIONAL INFORMATION

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

[elisa] [Bug 408480] Albums, artists and songs view empty on first start

[Matthieu Gallien]

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

--- Comment #3 from Matthieu Gallien  ---
Do you still reproduce this bug ?

I would believe that the 19.12.3 as packaged in Debian do not suffer from this
bug.

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

[okular] [Bug 419030] Crash exiting presentation mode

[Albert Astals Cid]

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

--- Comment #3 from Albert Astals Cid  ---
> this it the version supported by the current LTS version of Ubuntu via apt.

This is your problem, if you are using old versions of code, you don't get
fixes we have done in the last two years. Stop using the LTS version of Ubuntu
or accept that you don't get bugfixes.

> If I install the snap version of okular (1.9.3)

I've no idea about how the snap package is made sorry, in any case that would
be a different issue.

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

[okular] [Bug 419030] Crash exiting presentation mode

[Giampiero Salvi]

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

--- Comment #2 from Giampiero Salvi  ---
(In reply to Albert Astals Cid from comment #1)
> Your okular is ancient
> 
> *** This bug has been marked as a duplicate of bug 393478 ***

Hi Albert,
this it the version supported by the current LTS version of Ubuntu via apt.

If I install the snap version of okular (1.9.3), that is supposed to be the
most recent version available on Ubuntu 18.04, the program does not crash, but
it does not play videos either in presentation mode.

I get this warning then:

WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin
could not be loaded

I tried configuring backends but I could not find anything related to Phonon.

Could you give me a hint?

By the way, I had read the bug that you claim is a duplicate of this, before
filing this but. However, I did not think it was a duplicate bug. The behavior
was different and also the kind of files were different (in my case it was the
audio crashing the program). Of course I may be wrong.
Thank you
Giampiero

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

[elisa] [Bug 416170] Optional feature to Minimize Elisa to the system tray

[Matthieu Gallien]

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

--- Comment #8 from Matthieu Gallien  ---
(In reply to Christoph Cullmann from comment #7)
> Thanks a lot for taking care of this!

Thanks for your support

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

[systemsettings] [Bug 419031] New: system settings

[Christopher]

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

Bug ID: 419031
   Summary: system settings
   Product: systemsettings
   Version: 5.18.3
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: vlcmstn...@gmail.com
  Target Milestone: ---

Application: systemsettings5 (5.18.3)
 (Compiled from sources)
Qt Version: 5.14.1
Frameworks Version: 5.67.0
Operating System: Linux 5.4.24-1-MANJARO x86_64
Windowing system: X11
Distribution: Manjaro Linux

-- Information about the crash:
- What I was doing when the application crash
turning off bluetooth disabling file transfer options it seems like i may have
been hacked im not 100%

-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8531886cc0 (LWP 8501))]

Thread 22 (Thread 0x7f84aeffd700 (LWP 8594)):
#0  0x7f8535f9cabf in poll () at /usr/lib/libc.so.6
#1  0x7f8533f6c7a0 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f8533f6c871 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f85365550ec in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f85364fb57c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f853631fe62 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f85355c3f89 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7f8536320fd6 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f8534b7d46f in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f8535fa73d3 in clone () at /usr/lib/libc.so.6

Thread 21 (Thread 0x7f84d3422700 (LWP 8521)):
#0  0x7f8535f9cabf in poll () at /usr/lib/libc.so.6
#1  0x7f8533f6c7a0 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f8533f6c871 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f85365550ec in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f85364fb57c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f853631fe62 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f85355c3f89 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7f8536320fd6 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f8534b7d46f in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f8535fa73d3 in clone () at /usr/lib/libc.so.6

Thread 20 (Thread 0x7f85112fd700 (LWP 8520)):
#0  0x7f8535f9cabf in poll () at /usr/lib/libc.so.6
#1  0x7f8533f6c7a0 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f8533f6c871 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f85365550ec in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f85364fb57c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f853631fe62 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f85355c3f89 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7f8536320fd6 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f8534b7d46f in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f8535fa73d3 in clone () at /usr/lib/libc.so.6

Thread 19 (Thread 0x7f8511afe700 (LWP 8519)):
#0  0x7f8534b83cf5 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f8522ae8704 in  () at /usr/lib/dri/swrast_dri.so
#2  0x7f8522ae8688 in  () at /usr/lib/dri/swrast_dri.so
#3  0x7f8534b7d46f in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f8535fa73d3 in clone () at /usr/lib/libc.so.6

Thread 18 (Thread 0x7f85122ff700 (LWP 8518)):
#0  0x7f8534b83cf5 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f8522ae8704 in  () at /usr/lib/dri/swrast_dri.so
#2  0x7f8522ae8688 in  () at /usr/lib/dri/swrast_dri.so
#3  0x7f8534b7d46f in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f8535fa73d3 in clone () at /usr/lib/libc.so.6

Thread 17 (Thread 0x7f8512b00700 (LWP 8517)):
#0  0x7f8534b83cf5 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f8522ae8704 in  () at /usr/lib/dri/swrast_dri.so
#2  0x7f8522ae8688 in  () at /usr/lib/dri/swrast_dri.so
#3  0x7f8534b7d46f in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f8535fa73d3 in clone () at /usr/lib/libc.so.6

Thread 16 (Thread 0x7f8513301700 (LWP 8516)):
#0  0x7f8534b83cf5 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f8522ae8704 in  () at /usr/lib/dri/swrast_dri.so
#2  0x7f8522ae8688 in  () at /usr/lib/dri/swrast_dri.so
#3  0x7f8534b7d46f in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f8535fa73d3 in clone () at /usr/lib/libc.so.6

Thread 15 (Thread 0x7f8513b02700 (LWP 8515)):
#0  0x7f8534b83cf5 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f8522ae8704 in  () at 

[kwin] [Bug 418517] Titlebar text does not update correctly when title is fully to the left and no buttons are placed there.

[bugzilla_noreply]

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

--- Comment #4 from park.db...@gmail.com ---
Noto Sans 12. Have tried others; same bug.

On Thu, Mar 19, 2020 at 5:06 AM Vlad Zahorodnii 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=418517
>
> --- Comment #3 from Vlad Zahorodnii  ---
> What font do you use for titlebar text?
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[ark] [Bug 419009] Cann't crate 7z archive for folder

[Elvis Angelaccio]

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

Elvis Angelaccio  changed:

   What|Removed |Added

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

--- Comment #1 from Elvis Angelaccio  ---
Do you have p7zip installed?

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

[elisa] [Bug 416131] Elisa doesn't export the Album Art to the Media Player applet

[Matthieu Gallien]

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

--- Comment #12 from Matthieu Gallien  ---
https://invent.kde.org/kde/elisa/-/merge_requests/105 is a candidate fix
pending review.

Please test if you can ?

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

[okular] [Bug 419030] Crash exiting presentation mode

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

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

--- Comment #1 from Albert Astals Cid  ---
Your okular is ancient

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

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

[okular] [Bug 393478] crash when I exit presentation mode and enter again

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 CC||giampisa...@gmail.com

--- Comment #19 from Albert Astals Cid  ---
*** Bug 419030 has been marked as a duplicate of this bug. ***

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

[k3b] [Bug 418814] Ripping CD fails on tracks containing question marks

[Albert Astals Cid]

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

--- Comment #3 from Albert Astals Cid  ---
Honestly i don't think it's k3b issue to circunvent issues with filesystems.

Can you double check if you can create manually a file that contains a ? in
your ntfs drive?

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

[okular] [Bug 418994] Content disappears while zooming in PDFs

[Albert Astals Cid]

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

--- Comment #4 from Albert Astals Cid  ---
Is that a hidpi screen?

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

[digikam] [Bug 418939] Crash when search faces

[Maik Qualmann]

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

--- Comment #11 from Maik Qualmann  ---
The link to https://hastebin.com is currently not working, I will try again
later.

Maik

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

[okular] [Bug 419030] New: Crash exiting presentation mode

[Giampiero Salvi]

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

Bug ID: 419030
   Summary: Crash exiting presentation mode
   Product: okular
   Version: 1.3.3
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: giampisa...@gmail.com
  Target Milestone: ---

SUMMARY
Audio is not properly closed when exiting presentation mode. This causes okular
to crash every time you have audiovisual content in the presentation.

STEPS TO REPRODUCE
1. download the example presentation from
https://github.com/giampierosalvi/slides_with_video  
2. open it in okular and start presentation mode
3. exit presentation mode

OBSERVED RESULT
I have been trying to use both the apt and the snap version of okular in Ubuntu
18.04 to display presentations created with latex/beamer that include
audiovisual content. The apt version works fine as long as I do not exit the
presentation mode. Every time I exit presentation mode it crashes with the
following message:

pa_write() failed while trying to wake up the mainloop: Bad file descriptor
pa_write() failed while trying to wake up the mainloop: Bad file descriptor
pa_write() failed while trying to wake up the mainloop: Bad file descriptor
Assertion 'pa_close(fds[1]) == 0' failed at pulsecore/core-util.c:2647,
function pa_close_pipe(). Aborting.

The snap version is even worse: every time I try to play audiovisual content,
okular crashes with a long list of messages like this:

ALSA lib conf.c:3916:(snd_config_update_r) Cannot access file
/usr/share/alsa/alsa.conf
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM default
[55e08eacc8d0] alsa audio output error: cannot open ALSA device "default":
No such file or directory
[55e08eacc8d0] main audio output error: Audio output failed
[55e08eacc8d0] main audio output error: The audio device "default" could
not be used:
No such file or directory.
[55e08eacc8d0] main audio output error: module not functional
[7f1e7c1a4360] main decoder error: failed to create audio output
[7f1e600a56f0] main video output error: video output creation failed
Segmentation fault (core dumped)

EXPECTED RESULT
The program should not crash

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Ubuntu 18.04.4
(available in About System)
KDE Plasma Version: I am running Gnome 3.28.2 (so all the KDE libraries are
installed by apt when I install okular)

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 419029] New: Make taskbar mute/unmute ability optional

[João Vidal da Silva]

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

Bug ID: 419029
   Summary: Make taskbar mute/unmute ability optional
   Product: plasmashell
   Version: 5.18.3
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: joao.vidal.si...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 126898
  --> https://bugs.kde.org/attachment.cgi?id=126898=edit
printscreen of taskbar

Even without plasma-browser-integration there's the ability to click the
sound-icon on a task to mute/unmute that application.
I always have many tasks filling the taskbar, resulting in a small area per
task (see attachment).
More often than not, when clicking a task to raise it's window I just end up
muting it.
For this reason I'd like to have the option to disable the sound-icon's action.

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

[kate] [Bug 419028] LSP Client reports "Failed to start server:"

[bugzilla_noreply]

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

gl.ivanov...@gmail.com changed:

   What|Removed |Added

 CC||gl.ivanov...@gmail.com

--- Comment #1 from gl.ivanov...@gmail.com ---
I don't have it in this particular setup, but I have experimented with Python
language server as well with the same result. So it isn't specific to clangd
and potentially affects all language servers.

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

[kate] [Bug 419028] New: LSP Client reports "Failed to start server:"

[bugzilla_noreply]

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

Bug ID: 419028
   Summary: LSP Client reports "Failed to start server:"
   Product: kate
   Version: unspecified
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: gl.ivanov...@gmail.com
  Target Milestone: ---

SUMMARY
I have installed nightly build #766 (Version 20.07.70) on Windows 10. I also
have LLVM installed and added to PATH. I can launch clangd from command line,
but LSP Client fails to start it for some reason.

STEPS TO REPRODUCE
1. Enable LSP Client plugin.
2. Open any C source file.

OBSERVED RESULT
[2020-03-19T22:23:51] [Error] [LSP Client]
Failed to start server: clangd -log=error --background-index

EXPECTED RESULT
LSP server should start and work or there should be more information for
troubleshooting.

SOFTWARE/OS VERSIONS
Windows: 10
KDE Frameworks Version: 5.67.0
Qt Version: 5.14.1

ADDITIONAL INFORMATION

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

[frameworks-kio] [Bug 418258] ssh:// links not working in Plasma 5.18.2 and Frameworks 5.67.0

[Ahmad Samir]

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

Ahmad Samir  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://commits.kde.org/kio
   ||/14b7f2c7ee72bbf500625122a4
   ||b51c81f02e421f
   Version Fixed In||5.69

--- Comment #7 from Ahmad Samir  ---
Git commit 14b7f2c7ee72bbf500625122a4b51c81f02e421f by Ahmad Samir.
Committed on 19/03/2020 at 20:37.
Pushed by ahmadsamir into branch 'master'.

[DesktopExecParser] Open {ssh,telnet,rlogin}:// urls with ktelnetservice

Summary: Extend krununittest to test ktelnetservice.

Test Plan:
$ kde-open5 ssh://user@1.1.1.1
  outputs:
  command= "ktelnetservice5 %u" args= ("ktelnetservice5 %u",
"ssh://user@1.1.1.1")
  kf5.kio.core: couldn't create slave: "klauncher said: Unknown protocol
'ssh'.\n"

and you get a message box with "File not found: ssh://user@1.1.1.1".

Apply diff then try again, now a terminal window is launched by
ktelnetservice5 and ssh is invoked as expected.

FIXED-IN: 5.69

Reviewers: #frameworks, dfaure, sitter, meven, feverfew, ngraham

Reviewed By: dfaure, feverfew, ngraham

Subscribers: ngraham, kde-frameworks-devel

Tags: #frameworks

Differential Revision: https://phabricator.kde.org/D27999

M  +25   -0autotests/krununittest.cpp
M  +1-0autotests/krununittest.h
M  +3-0src/core/desktopexecparser.cpp

https://commits.kde.org/kio/14b7f2c7ee72bbf500625122a4b51c81f02e421f

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

[khotkeys] [Bug 417495] Application launcher shortcuts well recorded but launch nothing

[Luca Weiss]

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

Luca Weiss  changed:

   What|Removed |Added

 CC||l...@z3ntu.xyz

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

[kmymoney] [Bug 418334] Request: Use latest values to fill in transaction

[Thomas Baumgart]

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

Thomas Baumgart  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kmy
   ||money/029de47016d17a9d6d01a
   ||6a79f4a92bf8e7af97a
   Version Fixed In||5.0.9
 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #4 from Thomas Baumgart  ---
Git commit 029de47016d17a9d6d01a6a79f4a92bf8e7af97a by Thomas Baumgart.
Committed on 19/03/2020 at 20:15.
Pushed by tbaumgart into branch '5.0'.

Fix autofill to use latest transaction not earliest

The logic to auto fill a transaction with data from a previous
transaction to the same payee was using the first transaction when the
option "With previously most often used transaction for the payee" was
selected.

This change will instruct KMyMoney to use the latest transaction
instead.
FIXED-IN: 5.0.9

M  +1-0kmymoney/dialogs/stdtransactioneditor.cpp

https://commits.kde.org/kmymoney/029de47016d17a9d6d01a6a79f4a92bf8e7af97a

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

[korganizer] [Bug 419027] New: Outlook Calendar support

[bugzilla_noreply]

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

Bug ID: 419027
   Summary: Outlook Calendar support
   Product: korganizer
   Version: 5.11.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: techxga...@outlook.com
  Target Milestone: ---

SUMMARY
As an Outlook user, I save a lot of my calendars there, and I don't use Google
nor Facebook

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 19.10
KDE Plasma Version: 5.18.3
KDE Frameworks Version: 5.67.0
Qt Version: 5.12.4
Kernel Version: 5.3.0-42-generic
OS Type: 64-bit
Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz
Memory: 15.6 GiB of RAM

ADDITIONAL INFORMATION

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

[digikam] [Bug 418939] Crash when search faces

[Clon]

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

--- Comment #10 from Clon  ---
Crash similar with digikam-7.0.0-beta3-20200318T054830-x86-64.appimage

https://hastebin.com/esunihofac.sql

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

[kio-extras] [Bug 370370] "Copy to ..." won't work for an sftp connection

[Toralf Förster]

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

--- Comment #8 from Toralf Förster  ---
cannot test this b/c sftp does not work at all since few releases (see the
appropriate bug)

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

[kdeconnect] [Bug 419026] New: File Modified time same as tx time

[bugzilla_noreply]

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

Bug ID: 419026
   Summary: File Modified time same as tx time
   Product: kdeconnect
   Version: 1.3.3
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: android-application
  Assignee: albertv...@gmail.com
  Reporter: pierre...@yahoo.com
  Target Milestone: ---

SUMMARY
Transferring a file from Android to KDE, the modified timestamp is the same as
the transfer time and the creation timestamp is empty when it lands on the PC.

Not if Android KDEconnect or KDE's KDEconnect or maybe both are at fault.

STEPS TO REPRODUCE
1. Transferring a file from Android to KDE.

OBSERVED RESULT
the modified timestamp is the same as the transfer time and the creation
timestamp is empty

EXPECTED RESULT
-When the file land in KDE the modified timestamp and the creation timestamp
should stay the same as it is on Android.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Leap 15.1
(available in About System)
KDE Plasma Version: 5.12.8
KDE Frameworks Version: 5.55.0
Qt Version: 5.9.7

ADDITIONAL INFORMATION

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

[digikam] [Bug 384396] Display faces sorted by similarity (pre-grouped) instead of album/time/..

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #17 from Maik Qualmann  ---
The digiKam Icon View knows categories. I would find it better if the person
name is the category and thus the people are grouped. That would be much
clearer.

Maik

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

[digikam] [Bug 384485] Face Regions are deleted when unconfirmed face suggestion is rejected by user

[Kartik]

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

Kartik  changed:

   What|Removed |Added

 CC||kartikx2...@gmail.com

--- Comment #10 from Kartik  ---
On a somewhat related issue, whenever we delete a tag from a confirmed face.
For eg. If I had confirmed a suggestion, but later realized it is incorrect. I
will do a Remove Tag -> People/Kartik.

I think this should return the image back to unknown, however it rejects the
image as a face. We will have to scan it again, to get it back to unknown.

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

[digikam] [Bug 349564] Add support of face tags group

[bugzilla_noreply]

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

--- Comment #6 from caulier.gil...@gmail.com ---
Use another Linux account, As 7.0.0 has difference between 6.x in database
schema. Do not use yet in production.

Prepare a set of image to test. create a small collection and try to play with
Face management as expected...

Gilles Caulier

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

[digikam] [Bug 384396] Display faces sorted by similarity (pre-grouped) instead of album/time/..

[MarcP]

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

--- Comment #16 from MarcP  ---
Hi Kartik. This is quite ambitious! 

Since digikam can already "group" pictures, why not just grouping them by
similarity inside Unknown/Unconfirmed, without creating subtags? When the user
enters Unknown/Unconfirmed, they will see all the groups (the groups with the
most people could be showed first), and then they could enter a name (or
confirm the suggestion). The user could also expand or collapse a particular
group to see the containing pictures.

Although I believe that the "group" option is disabled for faces.

Another issue will be obtaining the similarity value. I guess that every new
face that is detected should be compared with the rest of the faces in the
Unknown/Unconfirmed categories and, if the similarity is superior to 0.95 (for
instance), then add that face to the group.

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

[digikam] [Bug 384396] Display faces sorted by similarity (pre-grouped) instead of album/time/..

[Kartik]

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

Kartik  changed:

   What|Removed |Added

 CC||kartikx2...@gmail.com

--- Comment #15 from Kartik  ---
Hello all, I would like to work on this bug. 

I noticed that Google Photos resolves this in a very efficient manner, it does
not show you the entire "Unknown" Collection, instead only individual
collections of people that are currently unknown, but the algorithm has
concluded to be the same.

Maybe this is something we can incorporate into DigiKam? I was thinking of
creating a hierarchy within the Unknown tag, where each sub-tag will display
face-tags of people that are similar (or the same).

The user could reject if the person is not the same as the rest, in which case
the person would move into the misc. unknown tag. 

There are a few issues to this, firstly I'm not sure whether it's ideal to
create a hierarchy within the unknown tag, furthermore, I'm not sure what I'd
name these subtags.

I'd be grateful for any suggestions regarding this.

Thanks 
Kartik

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

[digikam] [Bug 349564] Add support of face tags group

[Martin Tlustos]

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

--- Comment #5 from Martin Tlustos  ---
I'll try an appimage. What would you suggest I'd do after downloading? Rescan a
folder that contains double face tags?

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

[elisa] [Bug 416170] Optional feature to Minimize Elisa to the system tray

[Christoph Cullmann]

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

--- Comment #7 from Christoph Cullmann  ---
Thanks a lot for taking care of this!

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

[Akonadi] [Bug 415991] mail archive job crash

[Tim Folger]

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

Tim Folger  changed:

   What|Removed |Added

 CC||t...@timfolger.net

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

[krita] [Bug 392343] Text editor's Font-Style droplist and Bold button are broken

[Tyson Tan]

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

--- Comment #6 from Tyson Tan  ---
Today I found out what broke the droplist workaround, as well as discovering a
new workaround to make use of font styles.



### What broke the droplist workaround:

For some reason, now in 4.3.0prealpha, whenever I tried to input some letters
inside the Text Editor's font name droplist, the moment I put the second
letter, all new letters (the first and second letter I just input) get
HIGHLIGHTED. So now if I input a third letter, the previous two letters are
deleted.



### Workaround 1:

Press Left Arrow key to cancel the highlight state and move the input cursor to
the end. Do this once every two letters are input.

To input "Bold":
1) Input "B" and "o"
2) Press Left arrow
3) Input "l"
4) Press Left arrow
5) Input "d"
6) Press Left arrow

If the added letters match a style name, it will be activated.



### Workaround 2:

Tool options panel of the Text tool has a font droplist as well, and that
droplist for some reason lists EVERY font style. In this way we can determine a
font with its native style before we create the actual text.



### The missing Bold style:

Curiously though, this droplist in Tool options doesn't list any font's Bold
style! I wonder whether the Bold ones were linked to/confused with the Bold 
button in Text Editor's toolbar, which in turn broke both ways as a result?

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

[krita] [Bug 419025] Krita closes on autosave

[bugzilla_noreply]

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

--- Comment #1 from ja...@thisart.net ---
Created attachment 126897
  --> https://bugs.kde.org/attachment.cgi?id=126897=edit
Krita configuration

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

[cirkuit] [Bug 417932] ambiguous shortcuts

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 Resolution|--- |NOT A BUG
 Status|REPORTED|RESOLVED

--- Comment #1 from Christoph Feck  ---
KTikZ is unrelated to Circuit.

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

[krita] [Bug 419025] New: Krita closes on autosave

[bugzilla_noreply]

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

Bug ID: 419025
   Summary: Krita closes on autosave
   Product: krita
   Version: 4.2.8
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: ja...@thisart.net
  Target Milestone: ---

Created attachment 126896
  --> https://bugs.kde.org/attachment.cgi?id=126896=edit
Krita System Information from Help Menu

SUMMARY
Krita closes without any warning on every autosave

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


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

ADDITIONAL INFORMATION
Also tried Krita 4.2.9-beta1 with the same result.
Works perfect with deactivated autosave.
KritaSystemInformation from Help-Menu attached.

kritacrash.log says:


---

Error occurred on Wednesday, March 18, 2020 at 13:36:50.

krita.exe caused an Access Violation at location 7FFCAA9134E4 in module
libKF5Archive.dll Reading from location 0010.

AddrPC   Params
7FFCAA9134E4 0045 00B1F258 0031 
libKF5Archive.dll!0x34e4 KArchiveDirectory::addEntryV2+0x14
7FFCAA9239EB 00B1F318 00B1F3A8 00B1F398 
libKF5Archive.dll!0x139eb KZip::doPrepareWriting+0x48b
7FFCAA9121A1 00B1F440 00B1F4D8 203BB570 
libKF5Archive.dll!0x21a1 KArchive::prepareWriting+0x51
7FFCAD40BB69 0008 00BE 0053 
libkritastore.dll!0xbb69 KoLegacyZipStore::openWrite+0xa9
7FFCAD4049C0 48921F00 45E054D0 00B1F660 
libkritastore.dll!0x49c0 KoStore::open+0x740
7FFCB47EB2C0 00B1F8A0 7FFCB48161E8 00B1F570 
libkritalibkra.dll!0x2b2c0
KisKraSaveVisitor::savePaintDeviceFrame+0xf0
7FFCB47DC755  0008 48CD2980 
libkritalibkra.dll!0x1c755 KisKraSaveVisitor::savePaintDevice+0xf5
7FFCB47DD9CE 2038D7B0 7FFCA6064B1E 0034 
libkritalibkra.dll!0x1d9ce KisKraSaveVisitor::saveSelection+0x11e
7FFCB47DDED3 00B1F978 7FFCD2559DA0 0002 
libkritalibkra.dll!0x1ded3 KisKraSaveVisitor::visit+0x13
7FFCA606A5AC 00B1F880 7FFCB47DCA36 0008 
libkritaimage.dll!0x19a5ac KisNodeVisitor::visitAllInverse+0x3c
7FFCB47DF1FF 0030 0001 00B1F978 
libkritalibkra.dll!0x1f1ff KisKraSaveVisitor::visit+0x7f
7FFCB47D8F0B 4891F1D0 003C 00B1F980 
libkritalibkra.dll!0x18f0b KisKraSaver::saveBinaryData+0xdb
7FFCBA05B734 7FFCA486F320 0003 00B1FBA0 
kritakraexport.dll!0xb734 KraConverter::buildFile+0x2f4
7FFCBA053E62   7FFCA44F1540 
kritakraexport.dll!0x3e62 KraExport::convert+0xa2
7FFCA2D9085C  0010 20058C58 
libkritaui.dll!0x2f085c KisImportExportManager::doExportImpl+0x16c
7FFCA2D90C0E  48CD16A0  
libkritaui.dll!0x2f0c0e KisImportExportManager::doExport+0x8e
7FFCA2E60791 0010 48CD16A0 45BA90E0 
libkritaui.dll!0x3c0791
QtConcurrent::RunFunctionTask::run+0xb1
7FFCA44F8620 424AE360 45BA9000  
Qt5Core.dll!0x28620 QThreadPool::tryStart+0x520
7FFCA44F163F    
Qt5Core.dll!0x2163f QThread::qt_metacall+0x69f
7FFCD2467BD4    
KERNEL32.DLL!0x17bd4 BaseThreadInitThunk+0x14
7FFCD332CED1    
ntdll.dll!0x6ced1 RtlUserThreadStart+0x21

00014000-000140F7E000 krita.exe
7FFCD32C-7FFCD34B ntdll.dll 6.2.18362.719
7FFCD245-7FFCD2502000 KERNEL32.DLL  6.2.18362.329
7FFCD10C-7FFCD1363000 KERNELBASE.dll6.2.18362.719
7FFCCE6B-7FFCCE73F000 apphelp.dll   6.2.18362.1
7FFCD254-7FFCD25DE000 msvcrt.dll7.0.18362.1
7FFCC992-7FFCC996 libkritaglobal.dll
7FFCC34F-7FFCC3624000 libkritawidgetutils.dll
6144-6145A000 libgcc_s_seh-1.dll
7FFCC343-7FFCC348E000 libKF5ConfigCore.dll
6FC4-6FDA5000 libstdc++-6.dll
7FFCD292-7FFCD2AB4000 USER32.dll6.2.18362.719
7FFCD0B7-7FFCD0B91000 win32u.dll6.2.18362.719
7FFCD2CD-7FFCD2CF6000 GDI32.dll 6.2.18362.1
7FFCD0EC-7FFCD1054000 gdi32full.dll 6.2.18362.719
7FFCD0BA-7FFCD0C3E000 msvcp_win.dll 6.2.18362.387
7FFCD0D9-7FFCD0E8A000 ucrtbase.dll  6.2.18362.387
7FFCA5ED-7FFCA6411000 libkritaimage.dll

[okular] [Bug 417909] RFE: Text and page background - dark themed

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|REPORTED|RESOLVED

--- Comment #2 from Christoph Feck  ---
Right, changing colors requires post-processing, but the option is already
there.

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

[Breeze] [Bug 419024] Breeze Icons fails to build on Android cross-compile

[bugzilla_noreply]

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

--- Comment #1 from mt...@outlook.com ---
Created attachment 126895
  --> https://bugs.kde.org/attachment.cgi?id=126895=edit
CMake Output of build

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

[Breeze] [Bug 419024] New: Breeze Icons fails to build on Android cross-compile

[bugzilla_noreply]

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

Bug ID: 419024
   Summary: Breeze Icons fails to build on Android cross-compile
   Product: Breeze
   Version: 5.18.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Icons
  Assignee: visual-des...@kde.org
  Reporter: mt...@outlook.com
CC: kain...@gmail.com
  Target Milestone: ---

Created attachment 126894
  --> https://bugs.kde.org/attachment.cgi?id=126894=edit
Error log of build

SUMMARY
When cross-compiling breeze-icons to Android on Windows host the build fails.
It succeeded in version 5.67.0.

STEPS TO REPRODUCE
git clone https://anongit.kde.org/extra-cmake-modules.git
git -C extra-cmake-modules checkout tags/v5.68.0 -b v5.68.0
mkdir build\extra-cmake-modules
pushd build\extra-cmake-modules
cmake -DCMAKE_INSTALL_PREFIX=C:/Users/mtmcp/Temp
-DCMAKE_PREFIX_PATH=D:/Qt/5.12.6/android_x86;C:/Users/mtmcp/Temp
-DCMAKE_TOOLCHAIN_FILE=D:/Android/android-ndk-r19c/build/cmake/android.toolchain.cmake
-DCMAKE_FIND_ROOT_PATH=D:/Qt/5.12.6/android_x86;C:/Users/mtmcp/Temp
-DANDROID_ABI=x86 -DANDROID_PLATFORM=android-16 -DBUILD_SHARED_LIBS=OFF -G
Ninja C:/Users/mtmcp/Temp/extra-cmake-modules
cmake --build . --target install
popd

git clone https://anongit.kde.org/breeze-icons.git
git -C breeze-icons checkout tags/v5.68.0 -b v5.68.0
mkdir build\breeze-icons
pushd build\breeze-icons
cmake -DCMAKE_INSTALL_PREFIX=C:/Users/mtmcp/Temp
-DCMAKE_PREFIX_PATH=D:/Qt/5.12.6/android_x86;C:/Users/mtmcp/Temp
-DCMAKE_TOOLCHAIN_FILE=D:/Android/android-ndk-r19c/build/cmake/android.toolchain.cmake
-DCMAKE_FIND_ROOT_PATH=D:/Qt/5.12.6/android_x86;C:/Users/mtmcp/Temp
-DANDROID_ABI=x86 -DANDROID_PLATFORM=android-16 -DBUILD_SHARED_LIBS=OFF -G
Ninja C:/Users/mtmcp/Temp/breeze-icons

OBSERVED RESULT
-- Check for working C compiler:
D:/Android/android-ndk-r19c/toolchains/llvm/prebuilt/windows-x86_64/bin/clang.exe
-- Check for working C compiler:
D:/Android/android-ndk-r19c/toolchains/llvm/prebuilt/windows-x86_64/bin/clang.exe
-- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler:
D:/Android/android-ndk-r19c/toolchains/llvm/prebuilt/windows-x86_64/bin/clang++.exe
-- Check for working CXX compiler:
D:/Android/android-ndk-r19c/toolchains/llvm/prebuilt/windows-x86_64/bin/clang++.exe
-- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
--

Installing in C:/Users/mtmcp/Temp. Run
C:/Users/mtmcp/Temp/build/breeze-icons/prefix.sh to set the environment for
BreezeIcons.
-- Could not set up the appstream test. appstreamcli is missing.
-- Setting build type to 'Debug' as none was specified.
-- Looking for __GLIBC__
-- Looking for __GLIBC__ - not found
-- Performing Test _OFFT_IS_64BIT
-- Performing Test _OFFT_IS_64BIT - Failed
-- Performing Test HAVE_DATE_TIME
-- Performing Test HAVE_DATE_TIME - Success
CMake Error at icons/CMakeLists.txt:20 (add_dependencies):
  Cannot add target-level dependencies to non-existent target
  "breeze-validate-svg".

  The add_dependencies works for top-level logical targets created by the
  add_executable, add_library, or add_custom_target commands.  If you want to
  add file-level dependencies see the DEPENDS option of the add_custom_target
  and add_custom_command commands.


CMake Error at icons-dark/CMakeLists.txt:20 (add_dependencies):
  Cannot add target-level dependencies to non-existent target
  "breeze-validate-svg".

  The add_dependencies works for top-level logical targets created by the
  add_executable, add_library, or add_custom_target commands.  If you want to
  add file-level dependencies see the DEPENDS option of the add_custom_target
  and add_custom_command commands.


-- The following REQUIRED packages have been found:

 * ECM (required version >= 5.68.0), Extra CMake Modules.,

 * Qt5Core
 * Qt5Test
 * Qt5 (required version >= 5.12.0)

-- The following features have been disabled:

 * 24x24 generation, 'bash' is required to generate 24x24 variants

-- Configuring incomplete, errors occurred!
See also "C:/Users/mtmcp/Temp/build/breeze-icons/CMakeFiles/CMakeOutput.log".
See also "C:/Users/mtmcp/Temp/build/breeze-icons/CMakeFiles/CMakeError.log".

EXPECTED RESULT
Expected build should succeed like version 5.67.0

SOFTWARE/OS VERSIONS
Windows: 10
Android: android-ndk-r19c
Qt Version: 5.12.6

ADDITIONAL INFORMATION

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

[krita] [Bug 419022] Circle to quickly choose tool does not select tool, needs double click to stay open

[Postix]

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

--- Comment #1 from Postix  ---
Button "two" = Right Mouse button

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

[plasmashell] [Bug 419023] New: Filename in tooltip should span width of tooltip

[Michael D]

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

Bug ID: 419023
   Summary: Filename in tooltip should span width of tooltip
   Product: plasmashell
   Version: 5.18.3
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: nortex...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 126893
  --> https://bugs.kde.org/attachment.cgi?id=126893=edit
Showing cut-off filename that could span width of tooltip

I use the tooltip to see the filename when it does not fit in the task manager
"button". However, the filename is often cut off in the tooltip when it could
span the entire width of the tooltip (modulo padding). I've attached a
screenshot illustrating this.

Separate issue: there shouldn't be ellipses ("...") after "On desktop 4", and
there isn't in the tooltip for other windows on the same desktop.

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

[krita] [Bug 419022] Circle to quickly choose tool does not select tool, needs double click to stay open

[Postix]

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

Postix  changed:

   What|Removed |Added

 CC||pos...@posteo.eu

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

[krita] [Bug 419022] New: Circle to quickly choose tool does not select tool, needs double click to stay open

[Postix]

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

Bug ID: 419022
   Summary: Circle to quickly choose tool does not select tool,
needs double click to stay open
   Product: krita
   Version: 4.2.8
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: pos...@posteo.eu
  Target Milestone: ---

Created attachment 126892
  --> https://bugs.kde.org/attachment.cgi?id=126892=edit
Screen recording

SUMMARY

I just bought a graphics tablet (Wacom Intuos) with a two button pen and tested
Krita. Button "two" opens this circle to select a tool or color. 

Pressing button two, opens the circle. Releasing it, closes it.
While holding it down it stays open and the cursor can be moved to select a
tool (in theory). But tipping the pen (simulating a click) on the tablet does
nothing but close the circle.

However, there's the chance to let the circle stay open: By quickly double
clicking the button two. 
If it stays open then (without holding down button two), a tool or  a color can
actually be selected.
Unfortunately double clicking does not reliable make the circle stay opened. 

Please see the video.


SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux 
KDE Plasma Version: 5.18.3
KDE Frameworks Version: 5.69.0
Qt Version: 5.14.1
Kernel Version: 5.5.8-1-MANJARO

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

[konsole] [Bug 415724] Feature Requests

[Thomas Baumgart]

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

Thomas Baumgart  changed:

   What|Removed |Added

Product|kmymoney|konsole
  Component|general |general
   Assignee|kmymoney-de...@kde.org  |konsole-de...@kde.org

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

[valgrind] [Bug 418004] Grail code additions break ppc64

[Carl Love]

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

Carl Love  changed:

   What|Removed |Added

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

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

[valgrind] [Bug 418004] Grail code additions break ppc64

[Carl Love]

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

--- Comment #4 from Carl Love  ---
Patch committed.

commit c4c289ae994dfb8195e8b4889746d5e3d8296d25 (HEAD -> master, origin/master,
origin/HEAD)
Author: Carl Love 
Date:   Wed Mar 18 12:29:20 2020 -0500

additional grail' fixes for ppc32 and ppc64

The grail changes introduce a kludge call for ppc64.  The call fails
on some tests as the flatten call generates adds

addStmtToIRSB(bb, IRStmt_WrTmp(t1,
IRExpr_ITE(flatten_Expr(bb, ex->Iex.ITE.cond),
   flatten_Expr(bb, ex->Iex.ITE.iftrue),
   flatten_Expr(bb, ex->Iex.ITE.iffalse;

for V128 expressions.  Iex_ITE isn't supported for V128 type.  This patch
adds the needed V128 support for the Iex_ITE expressions.

Bugzilla 418004

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

[valgrind] [Bug 418004] Grail code additions break ppc64

[Carl Love]

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

Carl Love  changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

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

[valgrind] [Bug 418004] Grail code additions break ppc64

[Carl Love]

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

Carl Love  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #5 from Carl Love  ---
Closing

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

[elisa] [Bug 416170] Optional feature to Minimize Elisa to the system tray

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In||20.04.0

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

[kwin] [Bug 415256] Random Segmentation fault while Firefox open

[bugzilla_noreply]

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

pyro4h...@gmail.com changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|BACKTRACE   |FIXED

--- Comment #5 from pyro4h...@gmail.com ---
Thank you for your reply. I haven't had this Segfault since my last comment on
2020-01-30. So one and a half month. I suspect it got fixed (or I now have more
good luck)

Closing

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

[lattedock] [Bug 418431] latte-dock show all running apps ( all activities ) but only launchers from current activity

[Alexandre Pereira]

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

--- Comment #4 from Alexandre Pereira  ---
I should give more info, but just as more info, since sooner or later
activities/virtual desktops is going to change upstream.

I am actually using it this way on Wayland and working ( meaning it shows the
launchers of current activity, but also running apps of all activities/virtual
desktops ).

This is working by just filtering tasks by "current activity" only, and of
course only on wayland.

The only nitpick i would prefer, would be that other activities launchers when
running would be placed on a special place ( most right side or left side ) and
not in the middle of the taskmanager area ( where they are positioned if I
remove the "currenct activity filter" ).

Anyway never mind this, I will wait for what will happen to activities on
wayland.

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

[krita] [Bug 419021] Crash on closing a document

[Tymond]

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

--- Comment #2 from Tymond  ---
Created attachment 126891
  --> https://bugs.kde.org/attachment.cgi?id=126891=edit
gdb backtrace - thread apply all bt full

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

[kwin] [Bug 418951] The composer breaks down after you unlock the pc

[Vlad Zahorodnii]

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

--- Comment #23 from Vlad Zahorodnii  ---
The provided glxinfo log contains MAX_VIEWPORT_DIMS with normal values. I'm
still pretty sure that the driver provides garbage GL_MAX_VIEWPORT_DIMS when we
call viewportLimitsMatched().

Is there any chance you could build kwin with 348e72c56ec?

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

[kwin] [Bug 418951] The composer breaks down after you unlock the pc

[Vlad Zahorodnii]

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

--- Comment #22 from Vlad Zahorodnii  ---
Git commit 348e72c56ec7e157cec15d8e27065e4194490d89 by Vlad Zahorodnii.
Committed on 19/03/2020 at 14:40.
Pushed by vladz into branch 'Plasma/5.18'.

[scenes/opengl] Print a debug message when viewport limits aren't met

Summary:
This may help with debugging why compositing is suspended.

Test Plan: Compiles.

Reviewers: #kwin, davidedmundson

Reviewed By: #kwin, davidedmundson

Subscribers: kwin

Tags: #kwin

Differential Revision: https://phabricator.kde.org/D28139

M  +3-2plugins/scenes/opengl/scene_opengl.cpp

https://commits.kde.org/kwin/348e72c56ec7e157cec15d8e27065e4194490d89

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

[krita] [Bug 419021] Crash on closing a document

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org

--- Comment #1 from Boudewijn Rempt  ---
This is the only relevant bit of the backtrace

Thread 2738 (Thread 0x7fff8bb05700 (LWP 5864)):
#0  0x0064 in  ()
#1  0x76c33fec in
KisCanvasUpdatesCompressor::putUpdateInfo(KisSharedPtr)
(this=0x6f4d9a10, info=...) at
/home/tymon/kritadev/krita/libs/global/kis_shared_ptr.h:179
#2  0x76c2b174 in KisCanvas2::startUpdateCanvasProjection(QRect const&)
(this=0x76fb64a8, rc=...) at /usr/include/c++/8/bits/atomic_base.h:295
#3  0x748e86db in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x75eee4c2 in KisImage::sigImageUpdated(QRect const&)
(this=this@entry=0x82de9ff0, _t1=...) at
/home/tymon/kritadev/build/libs/image/kritaimage_autogen/EWIEGA46WW/moc_kis_image.cpp:702
#5  0x75ce1005 in KisImage::notifyProjectionUpdated(QRect const&)
(rc=..., this=0x82de9ff0) at
/home/tymon/kritadev/krita/libs/image/kis_image.cc:2013
#6  0x75ce1005 in KisImage::notifyProjectionUpdated(QRect const&)
(this=0x82de9ff0, rc=...) at
/home/tymon/kritadev/krita/libs/image/kis_image.cc:2003
#7  0x75cc271e in KisUpdateScheduler::continueUpdate(QRect const&)
(this=, rect=...) at
/home/tymon/kritadev/krita/libs/image/kis_update_scheduler.cpp:457
#8  0x75ef5b1b in non-virtual thunk to KisUpdateJobItem::run() () at
/usr/include/c++/8/bits/atomic_base.h:295
#9  0x7470ef71 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x74716c87 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x71992164 in start_thread (arg=) at
pthread_create.c:486
#12 0x73fe3def in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

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

[krita] [Bug 419021] New: Crash on closing a document

[Tymond]

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

Bug ID: 419021
   Summary: Crash on closing a document
   Product: krita
   Version: git master
  Platform: Mint (Ubuntu based)
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Color models
  Assignee: krita-bugs-n...@kde.org
  Reporter: tamtamy.tym...@gmail.com
  Target Milestone: ---

Created attachment 126890
  --> https://bugs.kde.org/attachment.cgi?id=126890=edit
gdb backtrace - thread apply all bt

SUMMARY
I was just closing documents that I was making a mockup
(https://phabricator.kde.org/M168) in. Some of them were with vector shapes,
some only pixel, some of them 32bit with linear profiles, some of them 8bit
integer sRGB, some of them converted from 32bit to 8bit. The one that Krita
crashed on seems to be still 32bit.



STEPS TO REPRODUCE
???

OBSERVED RESULT
Crash

EXPECTED RESULT
No crash! :)

SOFTWARE/OS VERSIONS
Linux Mint 19.3
Krita master a481571


ADDITIONAL INFORMATION
Backtrace in the attachment.

Parts of the backtrace below:

#0  0x0064 in  ()
#1  0x76c33fec in
KisCanvasUpdatesCompressor::putUpdateInfo(KisSharedPtr)
(this=0x6f4d9a10, info=...) at
/home/tymon/kritadev/krita/libs/global/kis_shared_ptr.h:179
#2  0x76c2b174 in KisCanvas2::startUpdateCanvasProjection(QRect const&)
(this=0x76fb64a8, rc=...) at /usr/include/c++/8/bits/atomic_base.h:295
#3  0x748e86db in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x75eee4c2 in KisImage::sigImageUpdated(QRect const&)
(this=this@entry=0x82de9ff0, _t1=...) at
/home/tymon/kritadev/build/libs/image/kritaimage_autogen/EWIEGA46WW/moc_kis_image.cpp:702
#5  0x75ce1005 in KisImage::notifyProjectionUpdated(QRect const&)
(rc=..., this=0x82de9ff0) at
/home/tymon/kritadev/krita/libs/image/kis_image.cc:2013
#6  0x75ce1005 in KisImage::notifyProjectionUpdated(QRect const&)
(this=0x82de9ff0, rc=...) at
/home/tymon/kritadev/krita/libs/image/kis_image.cc:2003
#7  0x75cc271e in KisUpdateScheduler::continueUpdate(QRect const&)
(this=, rect=...) at
/home/tymon/kritadev/krita/libs/image/kis_update_scheduler.cpp:457
#8  0x75ef5b1b in non-virtual thunk to KisUpdateJobItem::run() () at
/usr/include/c++/8/bits/atomic_base.h:295
#9  0x7470ef71 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x74716c87 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x71992164 in start_thread (arg=) at
pthread_create.c:486
#12 0x73fe3def in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95


Thread 2739 (Thread 0x7fff80b34700 (LWP 5865)):
#0  0x7fffd4e79101 in cmsEvalToneCurveFloat () at
/usr/lib/x86_64-linux-gnu/liblcms2.so.2
#1  0x7fffd4e8259d in  () at /usr/lib/x86_64-linux-gnu/liblcms2.so.2
#2  0x7fffd4e81e52 in  () at /usr/lib/x86_64-linux-gnu/liblcms2.so.2
#3  0x7fffd4e8f480 in  () at /usr/lib/x86_64-linux-gnu/liblcms2.so.2
#4  0x7fffd4e8ffc6 in cmsDoTransform () at
/usr/lib/x86_64-linux-gnu/liblcms2.so.2
#5  0x72b9bee2 in KoColorSpace::convertPixelsTo(unsigned char const*,
unsigned char*, KoColorSpace const*, unsigned int,
KoColorConversionTransformation::Intent,
QFlags) const (this=, src=0x7fff13eff010
"իT?իT?իT?\315\314\314>իT?իT?իT?\315\314\314>իT?իT?իT?\315\314\314>իT?իT?իT?\315\314\314>իT?իT?իT?\315\314\314>իT?իT?իT?\315\314\314>իT?իT?իT?\315\314\314>իT?իT?իT?\315\314\314>իT?իT?իT?\315\314\314>իT?իT?իT?\315\314\314>իT?իT?իT?\315\314\314>իT?իT?իT?\315\314\314>իT?իT?"...,
dst=0x7fff130ff010
"\334Hk?\006Ok?\357Ek?\315\314\314>\334Hk?\006Ok?\357Ek?\315\314\314>\334Hk?\006Ok?\357Ek?\315\314\314>\334Hk?\006Ok?\357Ek?\315\314\314>\334Hk?\006Ok?\357Ek?\315\314\314>\334Hk?\006Ok?\357Ek?\315\314\314>\334Hk?\006Ok?\357Ek?\315\314\314>\334Hk?\006Ok?\357Ek?\315\314\314>\334Hk?\006Ok?\357Ek?\315\314\314>\334Hk?\006Ok?\357Ek?\315\314\314>\334Hk?\006Ok?\357Ek?\315\314\314>\334Hk?\006Ok?\357Ek?\315\314\314>\334Hk?\006Ok?"...,
dstColorSpace=0x6e378a00, numPixels=65536,
renderingIntent=KoColorConversionTransformation::IntentPerceptual,
conversionFlags=...)
at /home/tymon/kritadev/krita/libs/pigment/KoColorSpace.cpp:430
#6  0x7fffd598ce31 in
KoColorSpaceAbstract::convertPixelsTo(unsigned char const*,
unsigned char*, KoColorSpace const*, unsigned int,
KoColorConversionTransformation::Intent,
QFlags) const
(this=0x599ec4e0, src=0x7fff13eff010
"իT?իT?իT?\315\314\314>իT?իT?իT?\315\314\314>իT?իT?իT?\315\314\314>իT?իT?իT?\315\314\314>իT?իT?իT?\315\314\314>իT?իT?իT?\315\314\314>իT?իT?իT?\315\314\314>իT?իT?իT?\315\314\314>իT?իT?իT?\315\314\314>իT?իT?իT?\315\314\314>իT?իT?իT?\315\314\314>իT?իT?իT?\315\314\314>իT?իT?"...,
dst=0x7fff130ff010

[krita] [Bug 412740] Krita leaks memory on exporting multiple pages from the comics manager

[wolthera]

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

--- Comment #11 from wolthera  ---
Crash after making a text shape. This one also happens when you...

1. make a new document
2. then a text shape (this does not crash, as the new doc is made via krita
cpp, not python)
3. then open a document via python.


Thread 1 "krita" received signal SIGSEGV, Segmentation fault.
0x70344bff in qHash (t=,
seed=1882038691)
at /usr/include/x86_64-linux-gnu/qt5/QtCore/qhashfunctions.h:119
119 { return qHash(t) ^ seed; }
(gdb) thread apply all backtrace

Thread 165 (Thread 0x7fff8a7fc700 (LWP 28064)):
#0  0x7fffeb4dced9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fff8a7fbbf0, expected=0, 
futex_word=0x603c6bf0) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  __pthread_cond_wait_common (abstime=0x7fff8a7fbca0, mutex=0x603c6ba0,
cond=0x603c6bc8) at pthread_cond_wait.c:533
#2  __pthread_cond_timedwait (cond=0x603c6bc8, mutex=0x603c6ba0,
abstime=0x7fff8a7fbca0) at pthread_cond_wait.c:667
#3  0x72e79d2a in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x72e79ee6 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x72e77275 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x72e737ec in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fffeb4d66db in start_thread (arg=0x7fff8a7fc700) at
pthread_create.c:463
#8  0x7255088f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 162 (Thread 0x7fff8b7fe700 (LWP 28061)):
#0  0x7fffeb4dced9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fff8b7fdbf0, expected=0, 
futex_word=0x60437a34) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  __pthread_cond_wait_common (abstime=0x7fff8b7fdca0, mutex=0x604379e0,
cond=0x60437a08) at pthread_cond_wait.c:533
#2  __pthread_cond_timedwait (cond=0x60437a08, mutex=0x604379e0,
abstime=0x7fff8b7fdca0) at pthread_cond_wait.c:667
#3  0x72e79d2a in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x72e79ee6 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x72e77275 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x72e737ec in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fffeb4d66db in start_thread (arg=0x7fff8b7fe700) at
pthread_create.c:463
#8  0x7255088f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 16 (Thread 0x7fff9b4cf700 (LWP 24574)):
#0  0x72543bf9 in __GI___poll (fds=0x7fff8c002de0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fffe9bd85c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fffe9bd86dc in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x730c20db in
QEventDispatcherGlib::processEvents(QFlags) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7306163a in
QEventLoop::exec(QFlags) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x72e72317 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x72e737ec in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fffeb4d66db in start_thread (arg=0x7fff9b4cf700) at
pthread_create.c:463
#8  0x7255088f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 15 (Thread 0x7fff9bcd0700 (LWP 24565)):
#0  0x72543bf9 in __GI___poll (fds=0x7fff94006140, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fffe9bd85c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fffe9bd86dc in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x730c20bc in
QEventDispatcherGlib::processEvents(QFlags) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7306163a in
QEventLoop::exec(QFlags) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x72e72317 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fffd4c4ca86 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#7  0x72e737ec in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
---Type  to continue, or q  to quit---
#8  0x7fffeb4d66db in start_thread (arg=0x7fff9bcd0700) at
pthread_create.c:463
#9  0x7255088f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 14 (Thread 0x7fffb0ebc700 (LWP 24556)):
#0  0x72543bf9 in __GI___poll (fds=0x7fff9c0029e0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fffe9bd85c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fffe9bd86dc in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x730c20bc in

[krita] [Bug 412740] Krita leaks memory on exporting multiple pages from the comics manager

[wolthera]

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

wolthera  changed:

   What|Removed |Added

 Resolution|FIXED   |---
   Assignee|griffinval...@gmail.com |b...@valdyas.org
 Status|RESOLVED|REOPENED

--- Comment #10 from wolthera  ---
Reopening because 1. we still leak documents, and 2. there's now an interesting
plethora of crashes related to the document not being found.

Crash while batch exporting:
=
Thread 1 "krita" received signal SIGSEGV, Segmentation fault.
0x76b2cb1a in KisView::document (this=0x0) at
/home/wolthera/krita/src/libs/ui/KisView.cpp:623
623 return d->document;
(gdb) thread apply all backtrace

Thread 818 (Thread 0x7fff6dffb700 (LWP 16056)):
#0  0x7fffeb4dced9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fff6dffabf0, expected=0, 
futex_word=0x7fff68e83bc4) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  __pthread_cond_wait_common (abstime=0x7fff6dffaca0, mutex=0x7fff68e83b70,
cond=0x7fff68e83b98) at pthread_cond_wait.c:533
#2  __pthread_cond_timedwait (cond=0x7fff68e83b98, mutex=0x7fff68e83b70,
abstime=0x7fff6dffaca0) at pthread_cond_wait.c:667
#3  0x72e79d2a in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x72e79ee6 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x72e77275 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x72e737ec in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fffeb4d66db in start_thread (arg=0x7fff6dffb700) at
pthread_create.c:463
#8  0x7255088f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 817 (Thread 0x7fff6f7fe700 (LWP 16055)):
#0  0x7fffeb4dc9f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x6663c464)
at ../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x6663c410,
cond=0x6663c438) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x6663c438, mutex=0x6663c410) at
pthread_cond_wait.c:655
#3  0x72e79d9b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x72e79f19 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x72e74386 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x72e7528e in QReadWriteLock::tryLockForRead(int) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7500949d in QReadLocker::relock (this=0x7fff6f7fd730)
at /usr/include/x86_64-linux-gnu/qt5/QtCore/qreadwritelock.h:106
#8  0x75009521 in QReadLocker::QReadLocker (this=0x7fff6f7fd730, 
areadWriteLock=0x75939ab8 <(anonymous
namespace)::Q_QGS_s_instance::innerFunction()::holder+216>)
at /usr/include/x86_64-linux-gnu/qt5/QtCore/qreadwritelock.h:125
#9  0x7500c538 in KisTileDataStore::registerTileData (
this=0x759399e0 <(anonymous
namespace)::Q_QGS_s_instance::innerFunction()::holder>, td=0x7fff61a9eeb0)
at /home/wolthera/krita/src/libs/image/tiles3/kis_tile_data_store.cc:142
#10 0x7500c72d in KisTileDataStore::duplicateTileData (
this=0x759399e0 <(anonymous
namespace)::Q_QGS_s_instance::innerFunction()::holder>, rhs=0x679da6d0)
at /home/wolthera/krita/src/libs/image/tiles3/kis_tile_data_store.cc:196
#11 0x750061e7 in KisTileData::clone (this=0x679da6d0)
at /home/wolthera/krita/src/libs/image/tiles3/kis_tile_data.h:88
#12 0x750055ea in KisTile::lockForWrite (this=0x7fff61aa2310)
at /home/wolthera/krita/src/libs/image/tiles3/kis_tile.cc:251
#13 0x75017e84 in KisTileDataWrapper::KisTileDataWrapper
(this=0x7fff6f7fd8e0, dm=0x679e9480, x=1024, y=3072, 
type=KisTileDataWrapper::WRITE) at
/home/wolthera/krita/src/libs/image/tiles3/kis_tile_data_wrapper.h:62
#14 0x75013652 in KisTiledDataManager::writeBytesBody
(this=0x679e9480, data=0x7fff61a16db0 "", x=1024, y=3072, 
width=256, height=256, dataRowStride=1024) at
/home/wolthera/krita/src/libs/image/tiles3/kis_tiled_data_manager_p.h:61
#15 0x75016a44 in KisTiledDataManager::writeBytes (this=0x679e9480,
data=0x7fff61a16db0 "", x=1024, y=3072, 
width=256, height=256, dataRowStride=-1) at
/home/wolthera/krita/src/libs/image/tiles3/kis_tiled_data_manager.cc:698
#16 0x75342e22 in KisDataManager::writeBytes (this=0x679e9480,
data=0x7fff61a16db0 "", x=1024, y=3072, w=256, 
h=256, dataRowStride=-1) at
/home/wolthera/krita/src/libs/image/kis_datamanager.h:277
#17 0x7534a524 in
KisPaintDevice::Private::KisPaintDeviceStrategy::writeBytesImpl
(this=0x665f7a80, 

[krita] [Bug 419020] Crash after making a text shape. [gdb backtrace]

[wolthera]

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

wolthera  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED

--- Comment #1 from wolthera  ---


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

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

[krita] [Bug 412740] Krita leaks memory on exporting multiple pages from the comics manager

[wolthera]

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

--- Comment #9 from wolthera  ---
*** Bug 419020 has been marked as a duplicate of this bug. ***

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

[digikam] [Bug 349564] Add support of face tags group

[bugzilla_noreply]

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

--- Comment #4 from caulier.gil...@gmail.com ---
Martin,

It will be better to check with current 7.0.0-beta3 available here :

https://files.kde.org/digikam/

... as we work a lots to improve face engine in this future version.

Thanks in advance

Gilles Caulier

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

[systemsettings] [Bug 417488] Broken fonts and fuzzy theme previews in multiple system settings

[bugzilla_noreply]

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

p.van.damme1...@gmail.com changed:

   What|Removed |Added

 CC||p.van.damme1...@gmail.com

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

[digikam] [Bug 349564] Add support of face tags group

[Martin Tlustos]

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

--- Comment #3 from Martin Tlustos  ---
I just checked in digikam 6.4.0, the problem is still there. 

A more in-depth-description: the same face is tagged twice. There are two
frames around the same face. They can have the same name, or a different.

I suspect that this can happen if one re-runs the face recognition process
twice (as I did in an attempt to find faces that had not been recognized during
the first run).

To prevent such behavior, digikam should have the rule that the same face can
not have two face-tags, and that the same name can not appear twice in the same
image (which shouldn't be possible until you are doing an artistic image
retouching).

Also, there should/could/would be nice if there was a process to clean up
images would double tagging.

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

[krita] [Bug 419020] New: Crash after making a text shape. [gdb backtrace]

[wolthera]

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

Bug ID: 419020
   Summary: Crash after making a text shape. [gdb backtrace]
   Product: krita
   Version: git master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: Tool/Text
  Assignee: krita-bugs-n...@kde.org
  Reporter: griffinval...@gmail.com
  Target Milestone: ---

SUMMARY
Crash after making a text shape.

git e6f5b4a

GDB backtrace
==
Thread 1 "krita" received signal SIGSEGV, Segmentation fault.
0x70344bff in qHash (t=,
seed=1882038691)
at /usr/include/x86_64-linux-gnu/qt5/QtCore/qhashfunctions.h:119
119 { return qHash(t) ^ seed; }
(gdb) thread apply all backtrace

Thread 165 (Thread 0x7fff8a7fc700 (LWP 28064)):
#0  0x7fffeb4dced9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fff8a7fbbf0, expected=0, 
futex_word=0x603c6bf0) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  __pthread_cond_wait_common (abstime=0x7fff8a7fbca0, mutex=0x603c6ba0,
cond=0x603c6bc8) at pthread_cond_wait.c:533
#2  __pthread_cond_timedwait (cond=0x603c6bc8, mutex=0x603c6ba0,
abstime=0x7fff8a7fbca0) at pthread_cond_wait.c:667
#3  0x72e79d2a in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x72e79ee6 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x72e77275 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x72e737ec in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fffeb4d66db in start_thread (arg=0x7fff8a7fc700) at
pthread_create.c:463
#8  0x7255088f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 162 (Thread 0x7fff8b7fe700 (LWP 28061)):
#0  0x7fffeb4dced9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fff8b7fdbf0, expected=0, 
futex_word=0x60437a34) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  __pthread_cond_wait_common (abstime=0x7fff8b7fdca0, mutex=0x604379e0,
cond=0x60437a08) at pthread_cond_wait.c:533
#2  __pthread_cond_timedwait (cond=0x60437a08, mutex=0x604379e0,
abstime=0x7fff8b7fdca0) at pthread_cond_wait.c:667
#3  0x72e79d2a in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x72e79ee6 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x72e77275 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x72e737ec in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fffeb4d66db in start_thread (arg=0x7fff8b7fe700) at
pthread_create.c:463
#8  0x7255088f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 16 (Thread 0x7fff9b4cf700 (LWP 24574)):
#0  0x72543bf9 in __GI___poll (fds=0x7fff8c002de0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fffe9bd85c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fffe9bd86dc in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x730c20db in
QEventDispatcherGlib::processEvents(QFlags) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7306163a in
QEventLoop::exec(QFlags) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x72e72317 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x72e737ec in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fffeb4d66db in start_thread (arg=0x7fff9b4cf700) at
pthread_create.c:463
#8  0x7255088f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 15 (Thread 0x7fff9bcd0700 (LWP 24565)):
#0  0x72543bf9 in __GI___poll (fds=0x7fff94006140, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fffe9bd85c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fffe9bd86dc in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x730c20bc in
QEventDispatcherGlib::processEvents(QFlags) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7306163a in
QEventLoop::exec(QFlags) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x72e72317 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fffd4c4ca86 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#7  0x72e737ec in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
---Type  to continue, or q  to quit---
#8  0x7fffeb4d66db in start_thread (arg=0x7fff9bcd0700) at
pthread_create.c:463
#9  0x7255088f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 14 (Thread 0x7fffb0ebc700 (LWP 24556)):
#0  0x72543bf9 in __GI___poll (fds=0x7fff9c0029e0, nfds=1, 

[systemsettings] [Bug 418604] If the currently applied Colour Scheme is not found, Apply is never enabled when selecting other colour schemes

[Cyril Rossi]

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

--- Comment #5 from Cyril Rossi  ---
Sure, I can cherry-pick the commit and merge into 5.18 branch.

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

[krita] [Bug 418925] Audio bug

[Boudewijn Rempt]

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

--- Comment #8 from Boudewijn Rempt  ---
As I said:

* the full output of help->system information for bug reports, 

* a link to the audio file you're trying to use so I can test with that file

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

[systemsettings] [Bug 235630] pointer acceleration in KDE should be optional

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #10 from Nate Graham  ---
There is now a flat acceleration setting in the libinput KCM.

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

[systemsettings] [Bug 327674] mouse acceleration profile bug

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=327674
Bug 327674 depends on bug 235630, which changed state.

Bug 235630 Summary: pointer acceleration in KDE should be optional
https://bugs.kde.org/show_bug.cgi?id=235630

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED

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

[krita] [Bug 418925] Audio bug

[bugzilla_noreply]

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

--- Comment #7 from nathanneb...@gmail.com ---
What information do you need ?

Le jeu. 19 mars 2020 à 10:20, Boudewijn Rempt  a
écrit :

> https://bugs.kde.org/show_bug.cgi?id=418925
>
> Boudewijn Rempt  changed:
>
>What|Removed |Added
>
> 
>  Status|REPORTED|NEEDSINFO
>  Resolution|--- |WAITINGFORINFO
>
> --- Comment #6 from Boudewijn Rempt  ---
> I still need the information I asked for.
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[elisa] [Bug 416131] Elisa doesn't export the Album Art to the Media Player applet

[Matthieu Gallien]

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

Matthieu Gallien  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED

--- Comment #11 from Matthieu Gallien  ---
I will work on that for the next stable release.

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