[digikam] [Bug 415702] Cannot abort or stop find Duplicate process

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

--- Comment #7 from Maik Qualmann  ---
Git commit a69c33aa2a73eb875ca228ab70e97a8c197db89a by Maik Qualmann.
Committed on 01/01/2020 at 07:32.
Pushed by mqualmann into branch 'master'.

next try to fix signal/slot in the maintenance tool

M  +1-1core/utilities/maintenance/maintenancetool.cpp

https://invent.kde.org/kde/digikam/commit/a69c33aa2a73eb875ca228ab70e97a8c197db89a

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

[digikam] [Bug 415719] digiKam cannot save images in heic or heif format.

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

Maik Qualmann  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
  Latest Commit|https://invent.kde.org/kde/ |
   |digikam/commit/ca0034a9fde0 |
   |54ec65fa144607fbe38083b6c8a |
   |d   |
 Resolution|FIXED   |---
   Version Fixed In|7.0.0   |

--- Comment #11 from Maik Qualmann  ---
Unfortunately does not work under Windows, x265 returns a negative value as bit
depth.

Maik

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

[elisa] [Bug 415739] Elisa not able to scan Music Tracks from $HOME/Music

2019-12-31 Thread Animesh Koley
https://bugs.kde.org/show_bug.cgi?id=415739

--- Comment #3 from Animesh Koley  ---
Thanks Matthieu, follwed adding my directory in baloofilerc as written in
#407918
For now, music files imported successfully in Elisa.

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

[konsole] [Bug 405213] [regression] Closing a tab doesn't select the previously focused tab any more

2019-12-31 Thread Loïc Yhuel
https://bugs.kde.org/show_bug.cgi?id=405213

Loïc Yhuel  changed:

   What|Removed |Added

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

--- Comment #1 from Loïc Yhuel  ---
I don't know when it was fixed, but this is now working as previously on
19.08.2.

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

[digikam] [Bug 415643] Digikam crashes Face detection

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

--- Comment #18 from caulier.gil...@gmail.com ---
There is no crash anymore ?

Happy new year...

Gilles Caulier

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

[Phonon] [Bug 415751] Regression in default device handling for audio, caused by D22616

2019-12-31 Thread petrk
https://bugs.kde.org/show_bug.cgi?id=415751

--- Comment #3 from petrk  ---
Created attachment 124819
  --> https://bugs.kde.org/attachment.cgi?id=124819=edit
Mockup

Tested with fresh user account, same deal.
Either way, default devices are not reliable at being set if I disconnect them.

Here's original message I was supposed to send before reading your response:

New way of dealing with multiple sound cards is not very intuitive. I can't
consider it a wontfix I'm afraid, that's a regression from old way, it was
working same way since KDE 4 days.
Can't we have a list of sound cards with ability to set which one is the most
important to least important? It's not obvious in new applet now. All I get is
a star near currently set one.

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

[Mangonel] [Bug 415758] New: Please add hybrid-sleep to launcher->leave

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

Bug ID: 415758
   Summary: Please add hybrid-sleep to launcher->leave
   Product: Mangonel
   Version: unspecified
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: mangonel
  Assignee: martin.sandsm...@kde.org
  Reporter: coder-ingramy...@outlook.com
  Target Milestone: ---

Now it has 4 functions there: sleep, power off, hybrid and restart, and now we
need hybrid-sleep their.

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

[kio-gdrive] [Bug 415089] Dolphin Kio-gdrive authentication with Google account fails

2019-12-31 Thread Wulf
https://bugs.kde.org/show_bug.cgi?id=415089

Wulf  changed:

   What|Removed |Added

 CC||wulf.richa...@gmx.de

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

[KAccounts] [Bug 414219] Google Drive access not working

2019-12-31 Thread Wulf
https://bugs.kde.org/show_bug.cgi?id=414219

Wulf  changed:

   What|Removed |Added

 CC||wulf.richa...@gmx.de

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

[KAccounts] [Bug 415267] Completely disfunctional dialog in 19.12

2019-12-31 Thread Wulf
https://bugs.kde.org/show_bug.cgi?id=415267

Wulf  changed:

   What|Removed |Added

 CC||wulf.richa...@gmx.de

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

[kdenlive] [Bug 414617] video scrolling area in monitors

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

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

[krita] [Bug 415210] When I start up the app for the first time, image on the screen freezes for 5-10 seconds.

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

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

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

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

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

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

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

[amarok] [Bug 415243] I can not add any online stations to the play list

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

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

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

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

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

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

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

[kwin] [Bug 415266] Order virtual desktops for windows in "Present windows" as they are set up in virtual desktops / pager

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

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

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

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

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

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

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

[valgrind] [Bug 415757] vex x86->IR: unhandled instruction bytes: 0x66 0xF 0xCE 0x4F

2019-12-31 Thread Alex Henrie
https://bugs.kde.org/show_bug.cgi?id=415757

--- Comment #1 from Alex Henrie  ---
Created attachment 124818
  --> https://bugs.kde.org/attachment.cgi?id=124818=edit
Proposed patch

The attached patch fixes the unhandled instruction problem. Unfortunately,
Leawo then pops up the following error dialog:

A debugger has been found running in your system.
Please, unload it from memory and restart your program.

There's probably a way past this, but even if there isn't, Valgrind produced
several warnings about the Wine code that is executed up to that point. So if
this patch is accepted, even though it doesn't get Leawo working all the way on
Valgrind, it still would help me and other Wine developers to start to debug
it.

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

[valgrind] [Bug 415757] vex x86->IR: unhandled instruction bytes: 0x66 0xF 0xCE 0x4F

2019-12-31 Thread Alex Henrie
https://bugs.kde.org/show_bug.cgi?id=415757

Alex Henrie  changed:

   What|Removed |Added

 CC||dou...@gmail.com

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

[valgrind] [Bug 415757] New: vex x86->IR: unhandled instruction bytes: 0x66 0xF 0xCE 0x4F

2019-12-31 Thread Alex Henrie
https://bugs.kde.org/show_bug.cgi?id=415757

Bug ID: 415757
   Summary: vex x86->IR: unhandled instruction bytes: 0x66 0xF
0xCE 0x4F
   Product: valgrind
   Version: 3.15 SVN
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: vex
  Assignee: jsew...@acm.org
  Reporter: alexhenri...@gmail.com
  Target Milestone: ---

Created attachment 124817
  --> https://bugs.kde.org/attachment.cgi?id=124817=edit
16-bit bswap test case

Steps to reproduce (on Arch Linux):

1. If ~/.wine exists, delete it.

2. Clone Wine with `git clone git://source.winehq.org/git/wine.git`

3. Compile a 32-bit-only version of Wine by running `./configure && make -j8`

4. Download the Leawo Blu-ray Player installer from
https://www.leawo.com/blu-ray-player/

5. Run `./wine blurayplayer_setup.exe` and click through the setup wizard. On
the last screen, uncheck "Launch Leawo Blu-Ray Player".

6. Run `valgrind --trace-children=yes ./wine 'C:\Program Files\Leawo\Blu-ray
Player\Leawo Blu-ray Player.exe'`

The program exits almost immediately with the following error:

vex x86->IR: unhandled instruction bytes: 0x66 0xF 0xCE 0x4F
==84194== valgrind: Unrecognised instruction at address 0xd272c9a.
==84194==at 0xD272C9A: ???
==84194== Your program just tried to execute an instruction that Valgrind
==84194== did not recognise.  There are two possible reasons for this.
==84194== 1. Your program has a bug and erroneously jumped to a non-code
==84194==location.  If you are running Memcheck and you just saw a
==84194==warning about a bad jump, it's probably your program's fault.
==84194== 2. The instruction is legitimate but Valgrind doesn't handle it,
==84194==i.e. it's Valgrind's fault.  If you think this is the case or
==84194==you are not sure, please let us know and we'll try to fix it.
==84194== Either way, Valgrind will now raise a SIGILL signal which will
==84194== probably kill your program.
==84194== valgrind: Unrecognised instruction at address 0xd272c9a.
==84194==at 0xD272C9A: ???
==84194== Your program just tried to execute an instruction that Valgrind
==84194== did not recognise.  There are two possible reasons for this.
==84194== 1. Your program has a bug and erroneously jumped to a non-code
==84194==location.  If you are running Memcheck and you just saw a
==84194==warning about a bad jump, it's probably your program's fault.
==84194== 2. The instruction is legitimate but Valgrind doesn't handle it,
==84194==i.e. it's Valgrind's fault.  If you think this is the case or
==84194==you are not sure, please let us know and we'll try to fix it.
==84194== Either way, Valgrind will now raise a SIGILL signal which will
==84194== probably kill your program.
0009:err:seh:segv_handler Got unexpected trap 0
0009:err:module:LdrInitializeThunk "panda.dll" failed to initialize, aborting
0009:err:module:LdrInitializeThunk Initializing dlls for L"C:\\Program
Files\\Leawo\\Blu-ray Player\\Leawo Blu-ray Player.exe" failed, status c01d

The unrecognized instruction comes from closed-source Leawo code. 0F CE is
BSWAP and 66 is the 16-bit instruction prefix. According to the Intel and AMD
documentation, the result of a 16-bit BSWAP is undefined.[1][2] However, on all
Intel and AMD CPUs (since the 486 when BSWAP was added), a 16-bit BSWAP returns
the value 0.[3] The attached test program from Doug Johnson confirms this.
Because there is software in the wild that depends on this behavior, I think
Valgrind should return 0 as well.

[1]
https://www.intel.com/content/dam/www/public/us/en/documents/manuals/64-ia-32-architectures-software-developer-instruction-set-reference-manual-325383.pdf#page=214
[2] https://www.amd.com/system/files/TechDocs/24594.pdf#page=153
[3] https://gynvael.coldwind.pl/?id=268

$ sha256sum blurayplayer_setup.exe 
8b7eef385ba336b0a44fc6295c0f6e3d869555d9eb8c262f470cad2028ba7d4d

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

[kig] [Bug 401512] kig crashes with simple python script with a failing assertion

2019-12-31 Thread Maurizio Paolini
https://bugs.kde.org/show_bug.cgi?id=401512

--- Comment #12 from Maurizio Paolini  ---
(In reply to Maurizio Paolini from comment #11)
> actually, the patch is in
> 
[WRONG] > https://phabricator.kde.org/differential/revision/edit/26333/
> 
> I am not sure that I am using phabricator correctly and couldn't find a
> place where to indicate that it should be used against release/19.12

oops, pardon me, the URL of the revision is:

https://phabricator.kde.org/D26333

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

[kig] [Bug 401512] kig crashes with simple python script with a failing assertion

2019-12-31 Thread Maurizio Paolini
https://bugs.kde.org/show_bug.cgi?id=401512

--- Comment #11 from Maurizio Paolini  ---
actually, the patch is in

https://phabricator.kde.org/differential/revision/edit/26333/

I am not sure that I am using phabricator correctly and couldn't find a place
where to indicate that it should be used against release/19.12

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

[Breeze] [Bug 397215] Visual bug around the maximize/unmaximize button

2019-12-31 Thread TYY331
https://bugs.kde.org/show_bug.cgi?id=397215

--- Comment #15 from TYY331  ---
I have finally found a workaround, if you enable the FPS counter effect the bug
is gone while the effect is active.
Btw if you want to trigger the bug in the first place you have to trigger a GPU
workload, this is easy to do with a GPU benchmark tool, I use Unigine heaven
for testing, once the benchmark is running, open any window and move it around,
the bug is triggered every time.
Having the FPS counter effect enabled prevent the glitch from appearing.
I'm using the modesetting driver, i haven't tested it with the Intel driver
yet.

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

[digikam] [Bug 415643] Digikam crashes Face detection

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

--- Comment #17 from r...@gmx.de ---
(In reply to Maik Qualmann from comment #16)
> Have you already tested the last new snapshots?
> 
> https://files.kde.org/digikam/
> 
> Maik

Thank you, now i have tested with the actual beta. The same problem I tagged
manually about 100 faces and after recognition with digikam no detection.

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

[plasma-browser-integration] [Bug 415756] New: Option to disable Google Chrome download bar that automatically appears when download is started

2019-12-31 Thread Gabriel Fernandes
https://bugs.kde.org/show_bug.cgi?id=415756

Bug ID: 415756
   Summary: Option to disable Google Chrome download bar that
automatically appears when download is started
   Product: plasma-browser-integration
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Chrome
  Assignee: k...@privat.broulik.de
  Reporter: gabrielfer...@gmail.com
  Target Milestone: ---

Hello, it's really nice to have the download progress in plasma notifications,
but Google Chrome shows a bar at the bottom of the window whenever a download
starts (it's quite annoying as you have to manually close the bar every
download). The progress through plasma notifications is much nicer, but you
kinda stay with a duplicate in the download bar of chrome.
I discovered you can disable the bar showing in every download through
extensions api (it's actually the only way I found to disable the bar), so it
would be awesome if we had a checkbox in the extension for chrome options
letting us disable the download bar, so we stick just with the nicer download
progress in plasma.
It's really simple to do it, here how I did it, as an example:
https://gist.github.com/gabrielfern/bf21df5b56d574eebe7d53e6291e49f6

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

[elisa] [Bug 406470] Album names in Playlist are elided; should become multi-line strings instead

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

--- Comment #2 from Nate Graham  ---
I submitted a merge request to fix this:
https://invent.kde.org/kde/elisa/merge_requests/58

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

[elisa] [Bug 415207] Drag and drop between music list and play list

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

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

[elisa] [Bug 415755] Drag-and-drop items from main content view to playlist

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

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #1 from Nate Graham  ---


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

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

[elisa] [Bug 413359] Window is slow to resize

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

Nate Graham  changed:

   What|Removed |Added

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

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

[elisa] [Bug 415755] New: Drag-and-drop items from main content view to playlist

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

Bug ID: 415755
   Summary: Drag-and-drop items from main content view to playlist
   Product: elisa
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: matthieu_gall...@yahoo.fr
  Reporter: n...@kde.org
  Target Milestone: ---

Just like the title says. :)

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

[digikam] [Bug 415592] When renaming a tag, if I say no to updating, clicking Save won't trigger update again

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

Maik Qualmann  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |WORKSFORME
   Version Fixed In||7.0.0

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

[digikam] [Bug 415719] digiKam cannot save images in heic or heif format.

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

Maik Qualmann  changed:

   What|Removed |Added

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

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

[kdelibs] [Bug 252594] Accentuated letters in keyboard shortcuts get capitalized

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

--- Comment #10 from bugs.kde@qtn.33mail.com ---
As a workaround, since this bug has not been fixed, it is possible to use an
external tool to handle the keyboard sequence. For instance, to switch to the
2nd workspace with Win+é, one may use sxhkd with the rule:

super + eacute
   xdotool set_desktop 1

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

[digikam] [Bug 415603] Add "Face Recognition" optional item in toolbar

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

Maik Qualmann  changed:

   What|Removed |Added

   Version Fixed In||7.0.0
 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED
  Latest Commit||https://invent.kde.org/kde/
   ||digikam/commit/5e3bcfe82ad1
   ||10e0dc7178b59da85b4476d0abf
   ||5

--- Comment #2 from Maik Qualmann  ---
Git commit 5e3bcfe82ad110e0dc7178b59da85b4476d0abf5 by Maik Qualmann.
Committed on 31/12/2019 at 21:23.
Pushed by mqualmann into branch 'master'.

enable face recognition after detection
FIXED-IN: 7.0.0

M  +2-1NEWS
M  +1-1core/app/views/stack/itemiconview.cpp
M  +1-1core/libs/album/treeview/albumselectiontreeview.cpp

https://invent.kde.org/kde/digikam/commit/5e3bcfe82ad110e0dc7178b59da85b4476d0abf5

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

[KAccounts] [Bug 414219] Google Drive access not working

2019-12-31 Thread Andrius
https://bugs.kde.org/show_bug.cgi?id=414219

Andrius  changed:

   What|Removed |Added

 CC||ergonomic.c...@gmail.com

--- Comment #15 from Andrius  ---
*** Bug 415696 has been marked as a duplicate of this bug. ***

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

[KAccounts] [Bug 415696] Synchronization with Google does not work, through KAccounts.

2019-12-31 Thread Andrius
https://bugs.kde.org/show_bug.cgi?id=415696

Andrius  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|CONFIRMED   |RESOLVED

--- Comment #3 from Andrius  ---
Duplicate of Bug #414219

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

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

[KAccounts] [Bug 415696] Synchronization with Google does not work, through KAccounts.

2019-12-31 Thread Andrius
https://bugs.kde.org/show_bug.cgi?id=415696

Andrius  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

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

[KAccounts] [Bug 415696] Synchronization with Google does not work, through KAccounts.

2019-12-31 Thread Andrius
https://bugs.kde.org/show_bug.cgi?id=415696

Andrius  changed:

   What|Removed |Added

 CC||andrius...@gmail.com

--- Comment #2 from Andrius  ---
Same here, seems like google did this to a lot of applications, seems like KDE
KAccounts Provider needs verification on Google side.

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

[digikam] [Bug 415719] digiKam cannot save images in heic or heif format.

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

--- Comment #10 from Maik Qualmann  ---
The build for Win64 cannot contain the change yet, wait for tomorrow.

Maik

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

[digikam] [Bug 415719] digiKam cannot save images in heic or heif format.

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

tlteebken-...@outlook.com changed:

   What|Removed |Added

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

--- Comment #9 from tlteebken-...@outlook.com ---
Hi, the issue still repros on today's build of the 7.0 beta.  

I tried to save several different images in heic format, same error on all. 
Tried reducing 16-bit source images in .tif format to 8-bit, then save, same
result.

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

[digikam] [Bug 412894] Import window causes digiKam to hang in macOS

2019-12-31 Thread Bob
https://bugs.kde.org/show_bug.cgi?id=412894

--- Comment #7 from Bob  ---
OK, I can understand that. Could it be a little more defensive?  Maybe:
Check the size of the target and if too big ask for a folder?
Or just come back with a “too big” dialog?

There may actually be a bug there, too. Please consider the following:
1.  When I let it run for 3 days, it apparently corrupted the OS. Safari
and Apple App Store started crashing with “invalid instruction codes.
2.  On my system, it seems to generate multiple identities for mounted
disks remembered from previous instances. Most of the phantom disks show
“fail to connect” dialog. The phantoms don’t seem to agree exactly with
information I see in finder or disk utility. Could there be a file system
interface issue that’s making it worse?


On Tue, Dec 31, 2019 at 3:19 PM Maik Qualmann 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=412894
>
> --- Comment #6 from Maik Qualmann  ---
> The Import tool was designed to display images from cameras or memory
> cards. So
> for a few thousand images. But not for hard drives with tens of thousands
> of
> images. The thumbnail model cannot process this large number of images
> without
> a database and is getting slower and slower.
>
> Maik
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.

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

[plasmashell] [Bug 415404] Glitch when moving the cursor on vertical panel with autohide

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

--- Comment #1 from manuelcha...@gmail.com ---
Seems the problem is gone after removing the touch screen feature that was
enabled.

"The issue is reproducible on Arch Linux too. To solve it all you have to do is
disable the Touch Screen in Settings > Workspace > Desktop Behavior ... an
restart the session or the system.
Cheers!"

https://forum.manjaro.org/t/a-tiny-gap-margin-issue-kde/89325/22

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

[systemsettings] [Bug 415657] Can't set screen resolution to 1280x1024

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

--- Comment #2 from falling_failing_fall...@protonmail.com ---
So I finally found a way to set the screen positioning correctly.
In CVT, you have to type the maximum refresh rate.
So for 60 Hz, use 75 Hz :
cvt 1280 1024 75
sudo nano /etc/X11/xorg.conf to edit the config file.
Inside the config file, I found the "Monitor" section and I edited it :
Section "Monitor"
Identifier "Monitor0"
VendorName "Sony"
ModelName  "SDM-HS73"
HorizSync   28.0 - 80.0
VertRefresh 48.0 - 75.0
Modeline   "1280x1024_75.00"  138.75  1280 1368 1504 1728  1024 1027
1034 1072 -hsync +vsync
Option "DPMS"
EndSection

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

[digikam] [Bug 415719] digiKam cannot save images in heic or heif format.

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

--- Comment #8 from caulier.gil...@gmail.com ---
Daily bundle are published in this repository:

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

digiKam and Gimp must certainly use the same HEIF codec : libx265.

In digiKam the error come from this libray that we use to check the max color
depth in a specific way which return a wrong value, certainly due a bug in this
library.

For Gimp i don't know how the export plugin deal with the library, but there is
a chance to see a similar dysfunction.

Gilles Caulier

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

[digikam] [Bug 412894] Import window causes digiKam to hang in macOS

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

--- Comment #6 from Maik Qualmann  ---
The Import tool was designed to display images from cameras or memory cards. So
for a few thousand images. But not for hard drives with tens of thousands of
images. The thumbnail model cannot process this large number of images without
a database and is getting slower and slower.

Maik

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

[digikam] [Bug 415566] Use existing face rectangles to improve recognition

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

Maik Qualmann  changed:

   What|Removed |Added

   Version Fixed In||7.0.0
 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/kde/
   ||digikam/commit/7825abf662ba
   ||6257da8a5d680f21d1cb21f607f
   ||1
 Status|CONFIRMED   |RESOLVED

--- Comment #4 from Maik Qualmann  ---
Git commit 7825abf662ba6257da8a5d680f21d1cb21f607f1 by Maik Qualmann.
Committed on 31/12/2019 at 20:05.
Pushed by mqualmann into branch 'master'.

clear identities, a clean trainings data rebuild is now possible
FIXED-IN: 7.0.0

M  +2-1NEWS
M  +3-0core/libs/facesengine/facedb/facedb.h
M  +6-1core/libs/facesengine/facedb/facedb_identity.cpp
M  +2-0   
core/libs/facesengine/recognition/recognitiondatabase_training.cpp

https://invent.kde.org/kde/digikam/commit/7825abf662ba6257da8a5d680f21d1cb21f607f1

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

[kwin] [Bug 415750] KWin crashes randomly

2019-12-31 Thread Roman Gilg
https://bugs.kde.org/show_bug.cgi?id=415750

Roman Gilg  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kwi
   ||n/af3fbf343bb234d2205c17451
   ||4ddfd61d52ebb5b
 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Roman Gilg  ---
Git commit af3fbf343bb234d2205c174514ddfd61d52ebb5b by Roman Gilg.
Committed on 31/12/2019 at 19:34.
Pushed by romangilg into branch 'master'.

Remove buffer flip pending assert for now

The assert is still not always true.

M  +3-1composite.cpp

https://commits.kde.org/kwin/af3fbf343bb234d2205c174514ddfd61d52ebb5b

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

[digikam] [Bug 379959] Could not start database initializer

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

--- Comment #13 from Maik Qualmann  ---
Git commit 6d386540102043d2c70c98e5b20f24cde6531343 by Maik Qualmann.
Committed on 31/12/2019 at 19:32.
Pushed by mqualmann into branch 'master'.

change order from the "--defaults-file" option

M  +2-1core/libs/database/server/databaseserver.cpp

https://invent.kde.org/kde/digikam/commit/6d386540102043d2c70c98e5b20f24cde6531343

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

[digikam] [Bug 415643] Digikam crashes Face detection

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

--- Comment #16 from Maik Qualmann  ---
Have you already tested the last new snapshots?

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

Maik

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

[krita] [Bug 415747] Phantom off-canvas content with vector objects

2019-12-31 Thread Rebecca Breu
https://bugs.kde.org/show_bug.cgi?id=415747

--- Comment #2 from Rebecca Breu  ---
Created attachment 124815
  --> https://bugs.kde.org/attachment.cgi?id=124815=edit
Screenshots of moving and trimming

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

[krita] [Bug 415747] Phantom off-canvas content with vector objects

2019-12-31 Thread Rebecca Breu
https://bugs.kde.org/show_bug.cgi?id=415747

Rebecca Breu  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||rebe...@rbreu.de
 Status|REPORTED|CONFIRMED

--- Comment #1 from Rebecca Breu  ---
I can confirm this. I also noticed:

1. Undoing the move operation doesn't remove the artifacts
2. When I initially move one object outside the canvas, it only gets shown
partly in the preview, and trimming the image to the layer at that stage only
includes that part of my object too. After this trimming, my preview has this
image duplicated, and trimming again (without doing anything else in between)
makes the image bigger again in accordance with the preview but without any new
content showing up.

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

[digikam] [Bug 415643] Digikam crashes Face detection

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

--- Comment #15 from r...@gmx.de ---
Could i do something to help? Or should I stand by at the moment?

Best wishes to the New year.

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

[digikam] [Bug 379959] Could not start database initializer

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

--- Comment #12 from Maik Qualmann  ---
Works fine with MariaDB here, but of course we can change it.

Maik

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

[digikam] [Bug 379959] Could not start database initializer

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

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

   What|Removed |Added

Version|5.5.0   |6.4.0

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

[elisa] [Bug 415739] Elisa not able to scan Music Tracks from $HOME/Music

2019-12-31 Thread Matthieu Gallien
https://bugs.kde.org/show_bug.cgi?id=415739

--- Comment #2 from Matthieu Gallien  ---
Thanks for your report.
It is currently a duplicate of #407918

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

[digikam] [Bug 379959] Could not start database initializer

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

ayr...@gmail.com changed:

   What|Removed |Added

 CC||ayr...@gmail.com

--- Comment #11 from ayr...@gmail.com ---
I can confirm this issue still exists in digikam 6.4.0 (on archlinux).

My understanding is that the --defaults-file argument must come before any
other option on the commandline in both mysql and mariadb.

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

[kdevplatform] [Bug 409951] Missing component KDev::Tests required for Umbrello

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

--- Comment #1 from Ralf Habacker  ---
This is still an issue and need to be fixed.

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

[lattedock] [Bug 415752] system tray and issue with non exiting panel edit mode

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

andresdor...@gmail.com changed:

   What|Removed |Added

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

--- Comment #2 from andresdor...@gmail.com ---
(In reply to Michail Vourlakos from comment #1)
> 1. Your editing mode issue is fixed with Latte 0.9.6
> 2. Your systray issue probably occurred from a crash, the systray settings
> were lost and its half default settings also. You can try to remove
> it/restart Latte/and add a new one
> 3. If [2] does not fix your systray issue then you can send your latte
> layout file to check it out, I believe I can fix it for you without losing
> your other applets settings

thanks for the reply. yup 0.9.6 fixed the issue, unfortunately, it's not in
manjaro stable yet so I'm using the aur git package for now and I'll probably
just ignore all update to the git and then update to 0.9.6 when it hits manjaro
stable

got the system tray setting to save again and I no longer get that error
message on start I just deleted all of my layouts except the one I'm using so I
removed default and plasma. thanks again for your help

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

[plasmashell] [Bug 415754] New: When connecting to wifi the kde plasma crashes

2019-12-31 Thread Antonio Medina
https://bugs.kde.org/show_bug.cgi?id=415754

Bug ID: 415754
   Summary: When connecting to wifi the kde plasma crashes
   Product: plasmashell
   Version: 5.16.5
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: 3soft4...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.16.5)

Qt Version: 5.12.4
Frameworks Version: 5.62.0
Operating System: Linux 5.3.0-26-generic x86_64
Distribution: Ubuntu 19.10

-- Information about the crash:
- What I was doing when the application crashed: Logging in to the wifi network
iwlwifi driver
 108.775479] wlo1: RX AssocResp from 88:5a:06:f7:34:d3 (capab=0x431 status=0
aid=4)
[  108.777522] wlo1: associated
[  108.788374] wlo1: deauthenticating from 88:5a:06:f7:34:d3 by local choice
(Reason: 1=UNSPECIFIED)

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
futex_wait_cancelable (private=, expected=0,
futex_word=0x55c0e1b63d60) at ../sysdeps/unix/sysv/linux/futex-internal.h:80
[Current thread is 1 (Thread 0x7f8b4270e880 (LWP 4684))]

Thread 12 (Thread 0x7f8b125ed700 (LWP 4939)):
[KCrash Handler]
#6  0x7f8b29842178 in  () at
/usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kquickcontrolsaddons/libkquickcontrolsaddonsplugin.so
#7  0x7f8b4619c5c8 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f8b47e1dba4 in QQuickWindowPrivate::renderSceneGraph(QSize const&)
() at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#9  0x7f8b47dc4c68 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#10 0x7f8b47dc89d8 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#11 0x7f8b45fa9cc2 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7f8b4542c669 in start_thread (arg=) at
pthread_create.c:479
#13 0x7f8b45c2e323 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 11 (Thread 0x7f8b119ec700 (LWP 4915)):
#0  0x7f8b454332c6 in futex_wait_cancelable (private=,
expected=0, futex_word=0x55c0e3886000) at
../sysdeps/unix/sysv/linux/futex-internal.h:80
#1  0x7f8b454332c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=0x55c0e3885fb0, cond=0x55c0e3885fd8) at pthread_cond_wait.c:508
#2  0x7f8b454332c6 in __pthread_cond_wait (cond=0x55c0e3885fd8,
mutex=0x55c0e3885fb0) at pthread_cond_wait.c:638
#3  0x7f8b45fafdef in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f8b45fafee1 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f8b47dc87b9 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7f8b47dc8a1a in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#7  0x7f8b45fa9cc2 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f8b4542c669 in start_thread (arg=) at
pthread_create.c:479
#9  0x7f8b45c2e323 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 10 (Thread 0x7f8b13fff700 (LWP 4882)):
#0  0x7f8b454332c6 in futex_wait_cancelable (private=,
expected=0, futex_word=0x7f8b0805ac74) at
../sysdeps/unix/sysv/linux/futex-internal.h:80
#1  0x7f8b454332c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=0x55c0de8a5428, cond=0x7f8b0805ac48) at pthread_cond_wait.c:508
#2  0x7f8b454332c6 in __pthread_cond_wait (cond=0x7f8b0805ac48,
mutex=0x55c0de8a5428) at pthread_cond_wait.c:638
#3  0x7f8b481bfb22 in  () at /usr/lib/x86_64-linux-gnu/libxcb.so.1
#4  0x7f8b481c162a in xcb_wait_for_special_event () at
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#5  0x7f8b39d5531e in glPrimitiveBoundingBox () at
/usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
#6  0x7f8b39d55488 in glPrimitiveBoundingBox () at
/usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
#7  0x7f8b39d5669e in glPrimitiveBoundingBox () at
/usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
#8  0x7f8b39d575ec in glPrimitiveBoundingBox () at
/usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
#9  0x7f8b38e82eec in  () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#10 0x7f8b38e83679 in  () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#11 0x7f8b38e7f15b in  () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#12 0x7f8b47d85056 in QSGBatchRenderer::Renderer::renderBatches() () at
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#13 0x7f8b47d8a8e4 in QSGBatchRenderer::Renderer::render() () at
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#14 0x7f8b47d7b420 in QSGRenderer::renderScene(QSGBindable const&) () at
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#15 0x7f8b47d7b8e3 in QSGRenderer::renderScene(unsigned int) () at

[Phonon] [Bug 415751] Regression in default device handling for audio, caused by D22616

2019-12-31 Thread Harald Sitter
https://bugs.kde.org/show_bug.cgi?id=415751

Harald Sitter  changed:

   What|Removed |Added

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

--- Comment #2 from Harald Sitter  ---
When you only see a generic pulseaudio device that means either phonon was
built without pulseaudio support or it was disabled at runtime because (for
example) the glib event loop of Qt isn't working or being detected correctly.
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/Phonon outlines some
ways to get more context

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

[systemsettings] [Bug 342493] Accentuated characters used in shortcuts are considered as uppercase

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

bugs.kde@qtn.33mail.com changed:

   What|Removed |Added

 CC||bugs.kde@qtn.33mail.com

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

[kdelibs] [Bug 252594] Accentuated letters in keyboard shortcuts get capitalized

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

bugs.kde@qtn.33mail.com changed:

   What|Removed |Added

 CC||bugs.kde@qtn.33mail.com

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

[elisa] [Bug 415739] Elisa not able to scan Music Tracks from $HOME/Music

2019-12-31 Thread Animesh Koley
https://bugs.kde.org/show_bug.cgi?id=415739

Animesh Koley  changed:

   What|Removed |Added

 CC||animesh.koley.social@gmail.
   ||com

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

[lattedock] [Bug 415752] system tray and issue with non exiting panel edit mode

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

--- Comment #1 from Michail Vourlakos  ---
1. Your editing mode issue is fixed with Latte 0.9.6
2. Your systray issue probably occurred from a crash, the systray settings were
lost and its half default settings also. You can try to remove it/restart
Latte/and add a new one
3. If [2] does not fix your systray issue then you can send your latte layout
file to check it out, I believe I can fix it for you without losing your other
applets settings

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

[elisa] [Bug 415739] Elisa not able to scan Music Tracks from $HOME/Music

2019-12-31 Thread Animesh Koley
https://bugs.kde.org/show_bug.cgi?id=415739

--- Comment #1 from Animesh Koley  ---
Few More Info:

My /home/animesh/Music folder is symlinked from folder /mydata/Animesh/Music.
Actually in this /mydata some other partition is mounted and MP3s are placed
physically in /mydata/Animesh/Music.

When I am creating a folder actually in home partition and keeping files there
and giving the path then files are getting imported.

So the issue is when keeping files in some other partition than home partition.

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

[plasma-nm] [Bug 415753] Search bar in dropdown not translated

2019-12-31 Thread Tim Summerer
https://bugs.kde.org/show_bug.cgi?id=415753

Tim Summerer  changed:

   What|Removed |Added

 CC||summerer@gmail.com

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

[plasma-nm] [Bug 415753] New: Search bar in dropdown not translated

2019-12-31 Thread Tim Summerer
https://bugs.kde.org/show_bug.cgi?id=415753

Bug ID: 415753
   Summary: Search bar in dropdown not translated
   Product: plasma-nm
   Version: 5.17.4
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: applet
  Assignee: jgrul...@redhat.com
  Reporter: summerer@gmail.com
  Target Milestone: ---

SUMMARY
The text "Search..." inside the search box of the applet is not translated to
the language of the desktop.

STEPS TO REPRODUCE
1. Open network applet
2. Press the magnifying glass icon

OBSERVED RESULT
Grey text "Search..." inside the search box is in English

EXPECTED RESULT
Translated grey text e.g. "Suchen..." in German.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux stable kernel 5.4.6
(available in About System)
KDE Plasma Version: 5.17.4
KDE Frameworks Version: 5.65.0
Qt Version: 5.14.0

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

[lattedock] [Bug 415752] New: system tray and issue with non exiting panel edit mode

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

Bug ID: 415752
   Summary: system tray and issue with non exiting panel edit mode
   Product: lattedock
   Version: 0.9.5
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: andresdor...@gmail.com
  Target Milestone: ---

SUMMARY
system tray does not save settings for what to show and not show. (it is reset
upon every latte start) also getting a message about latte not closing
correctly. 
Also, opening panel settings will put me in edit mode for the panel and I can't
exit.
STEPS TO REPRODUCE
1. Open latte
2. Open panel settings
3. will go into edit mode and cannot exit
4. open system tray settings
5. customize settings to your liking
6. close latte dock with task manager sending end signal or reboot
7. get a message about latte not closing correctly
8. system tray settings are gone

OBSERVED RESULT
panel edit mode does not exit when exiting panel settings

system tray settings do not persist 

error about latte not closing correctly regardless if it was close by a reboot
shutdown, logout, or end signal 

EXPECTED RESULT

system tray settings persist 

exit edit mode when I close panel settings

no error on startup

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 5.46-2-MANJARO 18.1.5
(available in About System)
KDE Plasma Version:5.17.4 
KDE Frameworks Version: 5.65.0
Qt Version: 5.14.0

ADDITIONAL INFORMATION

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

[Plasma Vault] [Bug 386200] Import Vault

2019-12-31 Thread Tim Summerer
https://bugs.kde.org/show_bug.cgi?id=386200

Tim Summerer  changed:

   What|Removed |Added

 CC||summerer@gmail.com

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

[Phonon] [Bug 415751] Regression in default device handling for audio, caused by D22616

2019-12-31 Thread petrk
https://bugs.kde.org/show_bug.cgi?id=415751

--- Comment #1 from petrk  ---
After reading all comments in D22616 I tried phononsettings. It exposes all
devices as single pulseaudio device which is not very helpful.

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

[Phonon] [Bug 415751] Regression in default device handling for audio, caused by D22616

2019-12-31 Thread petrk
https://bugs.kde.org/show_bug.cgi?id=415751

petrk  changed:

   What|Removed |Added

Summary|Regression in default   |Regression in default
   |device handling for audio   |device handling for audio,
   ||caused by D22616

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

[Phonon] [Bug 415751] New: Regression in default device handling for audio

2019-12-31 Thread petrk
https://bugs.kde.org/show_bug.cgi?id=415751

Bug ID: 415751
   Summary: Regression in default device handling for audio
   Product: Phonon
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: settings
  Assignee: sit...@kde.org
  Reporter: pepk...@gmail.com
CC: myr...@kde.org
  Target Milestone: ---

SUMMARY
What I've noticed is that in recent update one page with default devices was
removed. It causes serious regression for my use case, maybe not directly.

So, I use USB DAC for headphones and it's not always plugged in to my laptop.
In the past I used to set which device is meant to have priority in playing
audio and it worked for years without need for my intervention.
Recently systemsettings tab responsible for setting default audio devices
hierarchy has been removed and it causes serious issues for me. Allow me to
explain below.

STEPS TO REPRODUCE
1. Set external USB audio as default
2. Disconnect it (default switches to internal)
3. Reconnect USB audio again (Sound should switch back to USB, but it stays on
internal instead)

OBSERVED RESULT

Settings forget that there used to be an USB device after it's disconnected,
requiring me to switch audio manually.


EXPECTED RESULT

Audio switches to external USB according to hierarchy set few years ago. Now I
see no option to do that by the way!



Proposal:

Bring back phonon applet with settings for hierarchy in audio inputs/outputs.
Or alternatively, introduce a feature allowing me to set which audio device is
more important, and make sure that it's not forgotten after it's disconnected.

Use cases:
USB DACs
Bluetooth Headsets

What I mean is tab from first screenshot here:
https://userbase.kde.org/Phonon/Handbook

Operating System: Arch Linux 
KDE Plasma Version: 5.17.4
KDE Frameworks Version: 5.65.0
Qt Version: 5.14.0
Kernel Version: 5.4.6-zen3-1-zen
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-3720QM CPU @ 2.60GHz
Memory: 15,6 GiB

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

[KAccounts] [Bug 414219] Google Drive access not working

2019-12-31 Thread Ed_FR38
https://bugs.kde.org/show_bug.cgi?id=414219

Ed_FR38  changed:

   What|Removed |Added

 CC||e...@free.fr

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

[kio-gdrive] [Bug 415089] Dolphin Kio-gdrive authentication with Google account fails

2019-12-31 Thread Ed_FR38
https://bugs.kde.org/show_bug.cgi?id=415089

Ed_FR38  changed:

   What|Removed |Added

 CC||e...@free.fr

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

[dolphin] [Bug 415523] Please, add option to disable "filename extesions are always visible"

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

--- Comment #7 from Nate Graham  ---
I admit it, you did warn me about this, and you were right. :)

In reply to Christoph Feck from comment #5)
> Also, to show the extension, middle-elision isn't ideal. It could elide at
> the point where the extension starts.
That's not a bad idea at all.

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

[kmymoney] [Bug 415746] Missing labeling in split window

2019-12-31 Thread Thomas Baumgart
https://bugs.kde.org/show_bug.cgi?id=415746

Thomas Baumgart  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |DOWNSTREAM

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

[digikam] [Bug 415702] Cannot abort or stop find Duplicate process

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

--- Comment #6 from Maik Qualmann  ---
Git commit c0a607061f979a712b685e81d6277a2463e8cf27 by Maik Qualmann.
Committed on 31/12/2019 at 16:16.
Pushed by mqualmann into branch 'master'.

try with add namespace to ProgressItem

M  +1-1core/utilities/maintenance/maintenancetool.cpp

https://invent.kde.org/kde/digikam/commit/c0a607061f979a712b685e81d6277a2463e8cf27

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

[kwin] [Bug 415750] New: KWin crashes randomly

2019-12-31 Thread Nicolas Fella
https://bugs.kde.org/show_bug.cgi?id=415750

Bug ID: 415750
   Summary: KWin crashes randomly
   Product: kwin
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: nicolas.fe...@gmx.de
  Target Milestone: ---

Application: kwin_x11 (5.17.80)
 (Compiled from sources)
Qt Version: 5.14.0
Frameworks Version: 5.66.0
Operating System: Linux 5.4.6-2-MANJARO x86_64
Windowing system: X11
Distribution: Manjaro Linux

-- Information about the crash:
- What I was doing when the application crashed:
Nothing particularly special. Running on X11 with all KDE stuff freshly built
from master

The crash can be reproduced every time.

-- Backtrace:
Application: KWin (kwin_x11), signal: Aborted
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f2ff0925880 (LWP 1610))]

Thread 8 (Thread 0x7f2fd700 (LWP 1710)):
#0  0x7f2ff68ecc45 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f2ff88f6f3c in  () at /usr/lib/libQt5Script.so.5
#2  0x7f2ff88f6f59 in  () at /usr/lib/libQt5Script.so.5
#3  0x7f2ff68e64cf in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f2ff4dac2d3 in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7f2fdd1ec700 (LWP 1707)):
#0  0x7f2ff68ecc45 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f2fdf027d0c in  () at /usr/lib/dri/i965_dri.so
#2  0x7f2fdf027908 in  () at /usr/lib/dri/i965_dri.so
#3  0x7f2ff68e64cf in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f2ff4dac2d3 in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7f2fdd9ed700 (LWP 1706)):
#0  0x7f2ff68ecc45 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f2fdf027d0c in  () at /usr/lib/dri/i965_dri.so
#2  0x7f2fdf027908 in  () at /usr/lib/dri/i965_dri.so
#3  0x7f2ff68e64cf in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f2ff4dac2d3 in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f2fde1ee700 (LWP 1705)):
#0  0x7f2ff68ecc45 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f2fdf027d0c in  () at /usr/lib/dri/i965_dri.so
#2  0x7f2fdf027908 in  () at /usr/lib/dri/i965_dri.so
#3  0x7f2ff68e64cf in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f2ff4dac2d3 in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f2fde9ef700 (LWP 1704)):
#0  0x7f2ff68ecc45 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f2fdf027d0c in  () at /usr/lib/dri/i965_dri.so
#2  0x7f2fdf027908 in  () at /usr/lib/dri/i965_dri.so
#3  0x7f2ff68e64cf in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f2ff4dac2d3 in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f2fed6b1700 (LWP 1701)):
#0  0x7f2ff4da1ae6 in ppoll () at /usr/lib/libc.so.6
#1  0x7f2ff54b8cc3 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f2ff54ba2dd in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f2ff546339c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f2ff5288e62 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f2ff7e2e249 in  () at /usr/lib/libQt5Qml.so.5
#6  0x7f2ff5289fd6 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f2ff68e64cf in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f2ff4dac2d3 in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f2fef3de700 (LWP 1671)):
#0  0x7f2ff4da1ae6 in ppoll () at /usr/lib/libc.so.6
#1  0x7f2ff54b8cc3 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f2ff54ba2dd in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f2ff546339c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f2ff5288e62 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f2ff670eb28 in  () at /usr/lib/libQt5DBus.so.5
#6  0x7f2ff5289fd6 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f2ff68e64cf in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f2ff4dac2d3 in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7f2ff0925880 (LWP 1610)):
[KCrash Handler]
#6  0x7f2ff4ce8f25 in raise () at /usr/lib/libc.so.6
#7  0x7f2ff4cd2897 in abort () at /usr/lib/libc.so.6
#8  0x7f2ff524e96c in  () at /usr/lib/libQt5Core.so.5
#9  0x7f2ff524dcf8 in qt_assert_x(char const*, char const*, char const*,
int) () at /usr/lib/libQt5Core.so.5
#10 0x7f2ff8e02f24 in KWin::Compositor::performCompositing()
(this=0x5648744619b0) at /home/nico/kde/src/kwin/composite.cpp:694
#11 0x7f2ff8e040c1 in KWin::X11Compositor::performCompositing()
(this=0x5648744619b0) at 

[digikam] [Bug 415719] digiKam cannot save images in heic or heif format.

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

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

   What|Removed |Added

  Latest Commit||https://invent.kde.org/kde/
   ||digikam/commit/ca0034a9fde0
   ||54ec65fa144607fbe38083b6c8a
   ||d
 Resolution|--- |FIXED
   Version Fixed In||7.0.0
 Status|CONFIRMED   |RESOLVED

--- Comment #7 from caulier.gil...@gmail.com ---
Git commit ca0034a9fde054ec65fa144607fbe38083b6c8ad by Gilles Caulier.
Committed on 31/12/2019 at 15:52.
Pushed by cgilles into branch 'master'.

use max bit depth returned by x265 API instead to loop over possible value.
FIXED-IN: 7.0.0

M  +6-11   core/dplugins/dimg/heif/dimgheifloader_save.cpp

https://invent.kde.org/kde/digikam/commit/ca0034a9fde054ec65fa144607fbe38083b6c8ad

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

[Skanlite] [Bug 415749] New: When selecting multiple scan areas only first area gets scanned ("Automatic Document Feeder")

2019-12-31 Thread keeper_dev
https://bugs.kde.org/show_bug.cgi?id=415749

Bug ID: 415749
   Summary: When selecting multiple scan areas only first area
gets scanned ("Automatic Document Feeder")
   Product: Skanlite
   Version: 2.1.0.1
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: kare.s...@iki.fi
  Reporter: keeper@gmail.com
  Target Milestone: ---

I have a Brother MFC-L2700 Printer/Scanner connected via network. It has a
"Document Feeder" along with a Flatbed Scanner.

Per default, "Automatic Document Feeder" is selected as Scan source (but still
the flatbed scanner is used, when there is no document in the feeder). 
When adding multiple areas to scan on a preview and clicking on scan
afterwards, only the first area is getting scanned.

STEPS TO REPRODUCE
1. Open skanlite and make sure "Automatic Document Feeder" is set as Scan
source
2. Create preview
3. Create scan area and click on "+"
4. Create additional scan area and click on "+" again
5. Click on "Scan"


OBSERVED RESULT
Only the first scan area is getting scanned


EXPECTED RESULT
All scan areas are getting scanned and saved in multiple files 
OR 
Prevent usage of scan areas along with "Automatic Document Feeder"-Scan source
and show a hint (in manual as well), that suggests to select flatbed as Scanner
source, since multiple area scanning is not working as expected, when
"Automatic Document Feeder" is selected.


SOFTWARE/OS VERSIONS
Xubuntu 18.04

ADDITIONAL INFORMATION
-

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

[systemsettings] [Bug 415748] New: System settings crash in window decoration. Updating system also in background.

2019-12-31 Thread Brian O'Callaghan
https://bugs.kde.org/show_bug.cgi?id=415748

Bug ID: 415748
   Summary: System settings crash in window decoration. Updating
system also in background.
   Product: systemsettings
   Version: 5.17.4
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: brianoc...@gmail.com
  Target Milestone: ---

Application: systemsettings5 (5.17.4)

Qt Version: 5.13.2
Frameworks Version: 5.64.0
Operating System: Linux 5.4.0-1.5-MANJARO-ARM aarch64
Distribution: Manjaro ARM

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

I was moving around the system settings impatiently as whilst I love KDE, it
takes me a while to configure! Was playing with window decorations when the app
crashed. Was also updating packages in another window.

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

Thread 13 (Thread 0x71f840e0 (LWP 4896)):
#0  0x9876d4c8 in QMutex::lock() () at /usr/lib/libQt5Core.so.5
#1  0x989d6578 in  () at /usr/lib/libQt5Core.so.5
#2  0x9625b3bc in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#3  0x9625be68 in  () at /usr/lib/libglib-2.0.so.0
#4  0x9625c104 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x989d66a4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x9896da44 in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x9876b184 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x979986c0 in  () at /usr/lib/libQt5Qml.so.5
#9  0x9876ce58 in  () at /usr/lib/libQt5Core.so.5
#10 0x96e085d4 in start_thread () at /usr/lib/libpthread.so.0
#11 0x9840841c in thread_start () at /usr/lib/libc.so.6

Thread 12 (Thread 0x7a31c0e0 (LWP 4893)):
#0  0x9876ba68 in  () at /usr/lib/libQt5Core.so.5
#1  0x989d654c in  () at /usr/lib/libQt5Core.so.5
#2  0x9625b3bc in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#3  0x9625be68 in  () at /usr/lib/libglib-2.0.so.0
#4  0x9625c104 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x989d66a4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x9896da44 in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x9876b184 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x979986c0 in  () at /usr/lib/libQt5Qml.so.5
#9  0x9876ce58 in  () at /usr/lib/libQt5Core.so.5
#10 0x96e085d4 in start_thread () at /usr/lib/libpthread.so.0
#11 0x9840841c in thread_start () at /usr/lib/libc.so.6

Thread 11 (Thread 0x7dbeb0e0 (LWP 3562)):
#0  0x983fab30 in read () at /usr/lib/libc.so.6
#1  0x962aef40 in  () at /usr/lib/libglib-2.0.so.0
#2  0x9625b9c0 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x9625bf08 in  () at /usr/lib/libglib-2.0.so.0
#4  0x9625c104 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x989d66a4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x9896da44 in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x9876b184 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x979986c0 in  () at /usr/lib/libQt5Qml.so.5
#9  0x9876ce58 in  () at /usr/lib/libQt5Core.so.5
#10 0x96e085d4 in start_thread () at /usr/lib/libpthread.so.0
#11 0x9840841c in thread_start () at /usr/lib/libc.so.6

Thread 10 (Thread 0x888a60e0 (LWP 3535)):
#0  0x962b415c in g_mutex_lock () at /usr/lib/libglib-2.0.so.0
#1  0x9625af14 in g_main_context_release () at
/usr/lib/libglib-2.0.so.0
#2  0x9625bf24 in  () at /usr/lib/libglib-2.0.so.0
#3  0x9625c104 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x989d66a4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x9896da44 in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x9876b184 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x979986c0 in  () at /usr/lib/libQt5Qml.so.5
#8  0x9876ce58 in  () at /usr/lib/libQt5Core.so.5
#9  0x96e085d4 in start_thread () at /usr/lib/libpthread.so.0
#10 0x9840841c in thread_start () at /usr/lib/libc.so.6

Thread 9 (Thread 0x8910a0e0 (LWP 3532)):
#0  0x96e0e880 in pthread_cond_wait@@GLIBC_2.17 () at
/usr/lib/libpthread.so.0
#1  0x8b293064 in  () at /usr/lib/dri/swrast_dri.so
#2  0x8b292e4c in  () at 

[digikam] [Bug 415719] digiKam cannot save images in heic or heif format.

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

--- Comment #6 from Maik Qualmann  ---
This value (x265_max_bit_depth) returns 8 bits for me, instead of the loop -
then saving heic works.

Maik

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

[krita] [Bug 415747] New: Phantom off-canvas content with vector objects

2019-12-31 Thread Ahab Greybeard
https://bugs.kde.org/show_bug.cgi?id=415747

Bug ID: 415747
   Summary: Phantom off-canvas content with vector objects
   Product: krita
   Version: nightly build (please specify the git hash!)
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Layers/Vector
  Assignee: krita-bugs-n...@kde.org
  Reporter: ahab.greybe...@hotmail.co.uk
  Target Milestone: ---

Created attachment 124814
  --> https://bugs.kde.org/attachment.cgi?id=124814=edit
Simple image file for convenient use

SUMMARY
This happens with the 4.2.8 and the Dec28 4.3.0 prealpha (git 3f0ff1a)
appimages and the Windows portable .zip packages.
It does not happen with version 4.2.6 or 4.2.7.1
However, see Additional Notes.

If a vector object is moved off-canvas and then moved back on-canvas, phantom
content is created off-canvas at the location where the object was moved to.
This content can be seen on the layer thumbnail and is included in the Move
Tool content bounding box.
It has an effect on the Trim operations and it affects .svg export.
It is removed when the image is Saved.

I attach a simple .kra file that can be used for convenience to demonstrate the
problem.

STEPS TO REPRODUCE
1. Open two-vector-objects.kra and use the Move tool to note that the extent of
content is limited to the circle and the rectangle on the canvas, as expected.
2. Zoom out a little so there is a good amount of off-canvas area on the
workspace, for ease of further manipulation.

3. Use the Select Shapes Tool to move the circle left to an off-canvas
location, then click on the canvas to clear the object selection.
4. Use the Move Tool to check the extent of content and note that it includes
the off-canvas circle, as would be expected.
At this stage, the layer thumbnail will have been updated to show the circle
and rectangle.

5. Use the Shapes Select Tool to move the rectangle close to the left edge of
the canvas, to get the shapes close together for convenience during the next
steps.
6. Use the Move Tool to move the rectangle and circle into the middle of the
canvas then press ruturn to finalise the move.
Note that the layer thumbnail shows a 'phantom' red circle off-canvas to the
left.

7. Use the Move Tool again and Note that the extent of content includes the
phanton red circle off-canvas to the left.
Move the content to the right so that the rectangle moves off canvas to the
right and note that there is nothing visible at the left side of the content
bounding box.

8. Move the content back to the left so that the rectangle and circle are in
the middle again.
Note that the layer thumbnail shows a complete or partial rectangle off-canvas
the the left.
Note that the Move Tool now indicates there is content off-canvas to the right.

9. Do Image -> Trim To Image Size and Note that this has no effect on the
phantom off-canvas content.
10. Do Layer -> Import/Export -> Save Vector Layer As SVG and save the .svg
file.

11. Do File -> New and make a new 2048 x 2048 image then do Layer ->
Import/Export -> Import Layer and open the saved .svg file.
Note that the circle and rectangle are badly offset. i.e, the phantom content
has affected the .svg export.
Close this new image without saving it, that was only for demonstration.

12. Do Image -> Trim to Current Layer and Note that the trim action is affected
by and takes account of the phantom off-canvas content.
13. Do Undo Crop (trim) Image to restore the original image size.
14. Do File -> Save then close the open image and then File -> Open to open it
again.
Note that the phantom content is now gone.

OBSERVED RESULT
See Steps to Reproduce

EXPECTED RESULT
The phantom content should not exist.

ADDITIONAL INFORMATION
With 4.2.6, phantom content is not created but the Move tool bounding box does
not include genuine off-canvas content. However, the Move Tool will cause
genuine off-canvas content to move.

With 4.2.7.1, there is temporary phantom off-canvas content as shown by the
layer thumbnail but this goes away when the Move Tool is used again after
moving the circle back on-canvas.

SOFTWARE/OS VERSIONS
Krita

 Version: 4.3.0-prealpha (git 3f0ff1a)
 Languages: en_GB, en, en, en_GB, en
 Hidpi: true

Qt

  Version (compiled): 5.12.5
  Version (loaded): 5.12.5

OS Information

  Build ABI: x86_64-little_endian-lp64
  Build CPU: x86_64
  CPU: x86_64
  Kernel Type: linux
  Kernel Version: 4.19.0-6-amd64
  Pretty Productname: Debian GNU/Linux 10 (buster)
  Product Type: debian
  Product Version: 10

OpenGL Info

  Vendor:  "NVIDIA Corporation" 
  Renderer:  "GeForce GTX 750 Ti/PCIe/SSE2" 
  Version:  "4.6.0 NVIDIA 418.74" 
  Shading language:  "4.60 NVIDIA" 
  Requested format:  QSurfaceFormat(version 3.0, options
QFlags(DeprecatedFunctions), depthBufferSize 24,
redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8,
stencilBufferSize 8, samples -1, 

[digikam] [Bug 415719] digiKam cannot save images in heic or heif format.

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

--- Comment #5 from caulier.gil...@gmail.com ---
The error come from this loop :

https://invent.kde.org/kde/digikam/blob/master/core/dplugins/dimg/heif/dimgheifloader_save.cpp#L69

... where the max bit depth available to encode to x265 try to be detected.

Mostly deployed, the 8 bits color depth is supported. By compilation option, a
10 or 12 bits color depth can be enabled. This must generate extra .so using
bit depth in file name. So, loop report an higher bit depth than 8 but fail to
found the relevant .so or .dll on the system.

But must starnge thing is the Windows version: MXE compile a 8 bits version and
no more, but the loop return a 12 bits color depth supported. Why ??? Probably
a bug in x265 API.

There is an alternative to this loop, using this API :

https://github.com/videolan/x265/blob/master/source/x265.h#L1908

...which must return the X265 max depth available.

Gilles

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

[kmymoney] [Bug 415746] Missing labeling in split window

2019-12-31 Thread Dennis McCanna
https://bugs.kde.org/show_bug.cgi?id=415746

--- Comment #2 from Dennis McCanna  ---
Directly from the PoP_Shop and installed from there.  Linux Pop= System76

Thanks for responding I will forward to them.


> On Dec 31, 2019, at 9:25 AM, Thomas Baumgart  wrote:
> 
> https://bugs.kde.org/show_bug.cgi?id=415746
> 
> Thomas Baumgart  changed:
> 
>   What|Removed |Added
> 
> Resolution|--- |WAITINGFORINFO
> Status|REPORTED|NEEDSINFO
> 
> --- Comment #1 from Thomas Baumgart  ---
> That seems to be a packaging/installation problem. In general these buttons
> have icons:
> https://docs.kde.org/stable5/en/extragear-office/kmymoney/details.ledgers.split.
> Where did you get that version from?
> 
> -- 
> You are receiving this mail because:
> You reported the bug.

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

[digikam] [Bug 415719] digiKam cannot save images in heic or heif format.

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

--- Comment #4 from Maik Qualmann  ---
The AppImage works. In my native digiKam version is libx265-3.2.1 installed
from a non-free repository.

Maik

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

[systemsettings] [Bug 415129] icon theme installed and applied via Discover is not highlighted

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

Nate Graham  changed:

   What|Removed |Added

  Latest Commit||https://cgit.kde.org/plasma
   ||-desktop.git/commit/?id=5b9
   ||8466e5ddcc10dc8dc65e7733308
   ||423b877183
 Status|CONFIRMED   |RESOLVED
   Version Fixed In||5.18.0
 Resolution|--- |FIXED

--- Comment #3 from Nate Graham  ---
author  Benjamin Port 2019-12-21 12:21:05
+0100
committer   Benjamin Port 2019-12-31
09:27:56 +0100
commit  5b98466e5ddcc10dc8dc65e7733308423b877183 (patch)
treebfd1818b7f4cfe1d947f37ace4b5126ee164157a
parent  097ad69d5e8b0b15af5ae6659ca53b964428fae6 (diff)
KCM Icons: correctly highlight themes installed from Discover
BUG: 415129

Test Plan: Try installing using plasma-changeicons executable (used by
discover) and from discover directly

Reviewers: #plasma, ngraham, apol

Subscribers: plasma-devel

Tags: #plasma

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

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

[telepathy] [Bug 399102] XMPP chat doesn't work, shows an KIOExec Error "File not found: data:text/html;..."

2019-12-31 Thread Simon Schmeisser
https://bugs.kde.org/show_bug.cgi?id=399102

Simon Schmeisser  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #3 from Simon Schmeisser  ---
I can confirm this on kde neon as well.

Whats interesting is that when I build ktp-text-ui from source it works just
fine. (using ktp-common-internals at kaffeine-spacebar branch if that matters)

The message dialog contains the code for the adium theme it seems

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

[Breeze] [Bug 397987] Add application/vnd.apple.pkpass icon

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

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In||5.66

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

[telepathy] [Bug 399102] XMPP chat doesn't work, shows an KIOExec Error "File not found: data:text/html;..."

2019-12-31 Thread Simon Schmeisser
https://bugs.kde.org/show_bug.cgi?id=399102

Simon Schmeisser  changed:

   What|Removed |Added

 CC||mail_to_...@gmx.de

--- Comment #2 from Simon Schmeisser  ---
Created attachment 124813
  --> https://bugs.kde.org/attachment.cgi?id=124813=edit
log messages

commandline output printed when receiving a message and opening ktp-text-ui

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

[kmymoney] [Bug 415746] Missing labeling in split window

2019-12-31 Thread Thomas Baumgart
https://bugs.kde.org/show_bug.cgi?id=415746

Thomas Baumgart  changed:

   What|Removed |Added

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

--- Comment #1 from Thomas Baumgart  ---
That seems to be a packaging/installation problem. In general these buttons
have icons:
https://docs.kde.org/stable5/en/extragear-office/kmymoney/details.ledgers.split.
Where did you get that version from?

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

[digikam] [Bug 415719] digiKam cannot save images in heic or heif format.

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #3 from Maik Qualmann  ---
I have the same error message here on Linux too.

Maik

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

[krita] [Bug 379339] My Krita keeps crashing

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

roadzs...@gmail.com changed:

   What|Removed |Added

 CC||roadzs...@gmail.com

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

[krita] [Bug 402629] krita keeps crashing, never has enough memory space.

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

roadzs...@gmail.com changed:

   What|Removed |Added

 CC||roadzs...@gmail.com

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

[digikam] [Bug 415719] digiKam cannot save images in heic or heif format.

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

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

   What|Removed |Added

Summary|Digikam cannot save images  |digiKam cannot save images
   |in heic or heif format. |in heic or heif format.

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

[digikam] [Bug 415719] Digikam cannot save images in heic or heif format.

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

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

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #2 from caulier.gil...@gmail.com ---
yes fully reproducible under Windows:

[3844] digikam.geoiface: 
[3844] digikam.metaengine: Exiv2 ( 2 ) :  Directory Minolta, entry 0x0088: Data
area exceeds data buffer, ignoring it.
[3844] 
[3844] digikam.general: startSavingAs called
[3844] digikam.general: Writing file to 
QUrl("file:///C:/Users/gilles/Pictures/METADATA/digiKam/photo-48.heic")
[3844] digikam.widgets: Trying to discover format based on filename '
"photo-48.heic" ', fallback =  0
[3844] digikam.widgets: Discovered format:  6
[3844] digikam.widgets: Format selected:  "photo-48.heic"
[3844] digikam.widgets: Trying to discover format based on filename '
"photo-48.heic" ', fallback =  0
[3844] digikam.widgets: Discovered format:  6
[3844] digikam.general: Trying to find a saving format from targetUrl = 
QUrl("file:///C:/Users/gilles/Pictures/METADATA/digiKam/photo-48.heic")
[3844] digikam.general: Qt Offered types:  "*.bmp *.bw *.cur *.icns *.ico *.pbm
*.pcx *.pgm *.pic *.png *.ppm *.rgb *.rgba *.sgi *.tga *.wbmp *.webp *.xbm
*.xpm *.tiff *.tif *.jpg *.jpeg *.jpe *.jp2 *.j2k *.jpx *.pgx *.pgf *.heic
*.heif"
[3844] digikam.general: Writable formats:  ("bmp", "bw", "cur", "icns", "ico",
"pbm", "pcx", "pgm", "pic", "png", "ppm", "rgb", "rgba", "sgi", "tga", "wbmp",
"webp", "xbm", "xpm", "tiff", "tif", "jpg", "jpeg", "jpe", "jp2", "j2k", "jpx",
"pgx", "pgf", "heic", "heif")
[3844] digikam.general: Possible format from local file:  "heic"
[3844] digikam.general: Using format from target url  "heic"
[3844] digikam.geoiface: 
[3844] digikam.general: Saving to :
"C:/Users/gilles/Pictures/METADATA/digiKam/EditorWindow-jYaqPR.digikamtempfile.heic"
( "heic" )
[3844] digikam.general: Saving file
"C:/Users/gilles/Pictures/METADATA/digiKam/EditorWindow-jYaqPR.digikamtempfile.heic"
at -1
[3844] digikam.dimg: Prepare Metadata to save for
"C:/Users/gilles/Pictures/METADATA/digiKam/photo-48.heic"
[3844] digikam.metaengine: JPEG image preview size: ( 1280 x 852 ) pixels -
65683 bytes
[3844] digikam.dimg: Saving to 
"C:/Users/gilles/Pictures/METADATA/digiKam/EditorWindow-jYaqPR.digikamtempfile.heic"
 with format:  "heic"
[3844] Check HEVC encoder for 16 bits encoding...
[3844] Check HEVC encoder for 14 bits encoding...
[3844] Check HEVC encoder for 12 bits encoding...
[3844] HEVC encoder max bits depth: 12
[3844] HEVC encoder setup...
[3844] HEIF set color profile...
[3844] Stored HEIF color profile size: 6924
[3844] HEIF setup data plane...
[3844] HEIF data container: 0x29b35bbe040
[3844] HEIF bytes per line: 18096
[3844] HEIF output bytes per color: 6
[3844] HEIF 16 to 8 bits coeff.   : 4
[3844] HEIF 8 to 16 bits coeff.   : 4
[3844] HEIF master image encoding...
[3844] Error while processing HEIF image: Encoder plugin generated an error:
Unsupported bit depth: Bit depth not supported by x265
[3844] digikam.general: error saving image '
C:/Users/gilles/Pictures/METADATA/digiKam/EditorWindow-jYaqPR.digikamtempfile.heic
[3844] digikam.general:
"C:/Users/gilles/Pictures/METADATA/digiKam/EditorWindow-jYaqPR.digikamtempfile.heic"
false true


Gilles Caulier

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

[KScreen] [Bug 391101] Wrong refresh rates in Displays settings

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

--- Comment #2 from grouchomarx...@gmail.com ---
I don't have this issue anymore.

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

[KScreen] [Bug 391101] Wrong refresh rates in Displays settings

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

grouchomarx...@gmail.com changed:

   What|Removed |Added

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

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

[digikam] [Bug 415719] Digikam cannot save images in heic or heif format.

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

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com

--- Comment #1 from caulier.gil...@gmail.com ---
Under Linux, no problem.

I used a JPEG file and exported to HEIC with image editor "save as..".

Which is the kind of input image format to convert in HEIF ?

Can you post the DebugView M$ tool text trace while digiKam is running and try
to generate the HEIF file ?

https://www.digikam.org/contribute/

Gilles Caulier

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

[kmymoney] [Bug 415746] New: Missing labeling in split window

2019-12-31 Thread Dennis McCanna
https://bugs.kde.org/show_bug.cgi?id=415746

Bug ID: 415746
   Summary: Missing labeling in split window
   Product: kmymoney
   Version: 5.0.6
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: database
  Assignee: kmymoney-de...@kde.org
  Reporter: winger4...@gmail.com
  Target Milestone: ---

Created attachment 124812
  --> https://bugs.kde.org/attachment.cgi?id=124812=edit
Screenshot of window

SUMMARY
Split section of ledger has 2 buttons below the split entry on the left side.
"I BELIEVE" they are supposed to have some form of labeling. On mine they are
blank and documentation said to look for them to enter the transaction.

STEPS TO REPRODUCE
1. Click on the split button
2. Enter & cancel buttons do not have labeling
3. 

OBSERVED RESULT
No labeling


EXPECTED RESULT
Should be labeled?


SOFTWARE/OS VERSIONS

Linux/PopOS

ADDITIONAL INFORMATION

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

[krita] [Bug 415213] Transform Tool Crashing Program After resizing

2019-12-31 Thread Stacey
https://bugs.kde.org/show_bug.cgi?id=415213

Stacey  changed:

   What|Removed |Added

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

--- Comment #10 from Stacey  ---
(In reply to Tymond from comment #7)
> @Stacey can you please check Krita Next version again? The version on the
> website is: 919-g3f0ff1a86c, but you can use a newer one, I just want to
> make sure you checked a fresh one since you didn't say what exact versions
> were those that you downloaded last time.
> 
> This bug might be either bug 414672 (which is fixed already in Krita Next
> version) or bug 415625 (which is not fixed), and I cannot determine it
> without seeing a backtrace or at least debug view log. (If it isn't fixed
> for you on Krita Next, that means it's not bug 414672, but it might be some
> other bug than bug 415625...)
> 
> - can you please try to find krita.log file? This one *must* exist and it
> will exist in the same location as kritacrash.log file: in %localappdata%/ .
> (You'll see you're (most probably) in c:/Users/[username]/AppData/Local/) If
> you find that file, check if you searched for the kritacrash.log file in
> this location; if not, please check if there is this file and attach both to
> this bug report. If you see only one of them, please attach one of them.
> 
> - please download DebugView program:
> https://docs.microsoft.com/en-us/sysinternals/downloads/debugview - it's
> from the Microsoft site so as safe as stuff on the internet can be. Unzip
> it. There will be a debugview.exe file - run it (and just let it run). Then
> run Krita and make it crash. Then copy everything that is visible on
> DebugView to a new text file in a Notepad and then attach this file here.

Thank you for the reply, I have tried Krita Next again and run into the same
issue. I cannot locate kritacrash file but have found krita.log so have
attached this. I have also run the debugview and attached the findings from
that. Many thanks!

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

[krita] [Bug 415213] Transform Tool Crashing Program After resizing

2019-12-31 Thread Stacey
https://bugs.kde.org/show_bug.cgi?id=415213

--- Comment #9 from Stacey  ---
Created attachment 124811
  --> https://bugs.kde.org/attachment.cgi?id=124811=edit
Krita log

Krita log following crash. Unable to locate kritacrash file, only file that
exists is krita.log

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

[kwin] [Bug 415718] close windows by double clicking the menu button not working

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

Patrick Silva  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

--- Comment #5 from Patrick Silva  ---
Confirmed here when I use an Aurorae window decoration (tested Breezemite).
It works as expected with Breeze.

Arch Linux, Plasma 5.17.4.

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

  1   2   >