[KScreen] [Bug 407058] KDE Plasma5 can't change resolution in VM after last update

2020-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=407058

h...@live.com changed:

   What|Removed |Added

 CC||h...@live.com

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

[KScreen] [Bug 415648] Cannot change VMWare guest resolution

2020-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=415648

h...@live.com changed:

   What|Removed |Added

 CC||h...@live.com

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

[kontact] [Bug 415634] kontact crash on opening settings

2020-02-17 Thread Eoghann Walker
https://bugs.kde.org/show_bug.cgi?id=415634

--- Comment #11 from Eoghann Walker  ---
Bug seems to be resolved with updates to:
KDE Framework 5.68.0
Qt 5.14.1
Kontact Version 5.13.3 (19.12.3)


On Tuesday, 18 February 2020 05:43:25 GMT you wrote:
> https://bugs.kde.org/show_bug.cgi?id=415634
> 
> --- Comment #10 from Wolfgang Bauer  ---
> (In reply to Morbid from comment #9)
> 
> > The same issue is present on Arch.
> > Operating System: Arch Linux
> > KDE Plasma Version: 5.18.0
> > KDE Frameworks Version: 5.67.0
> 
> I find it very likely that you actually experience bug#417396, which is a
> regression in KDE Frameworks 5.67 and is 100% reliable to crash kontact when
> opening the settings AFAICT (unlike this bug)...

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

[kwin] [Bug 417637] Black border while standalone QML KCMs are resized

2020-02-17 Thread Vlad Zahorodnii
https://bugs.kde.org/show_bug.cgi?id=417637

Vlad Zahorodnii  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #4 from Vlad Zahorodnii  ---
(In reply to Nate Graham from comment #3)
> Not a duplicate of that issue, because fixing that did not fix this.

No, it's a duplicate of bug 415839. See comment 31.

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

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

[kwin] [Bug 415839] Resizing apps results in flickering or controls jumping around

2020-02-17 Thread Vlad Zahorodnii
https://bugs.kde.org/show_bug.cgi?id=415839

--- Comment #32 from Vlad Zahorodnii  ---
*** Bug 417637 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 415839] Resizing apps results in flickering or controls jumping around

2020-02-17 Thread Vlad Zahorodnii
https://bugs.kde.org/show_bug.cgi?id=415839

--- Comment #31 from Vlad Zahorodnii  ---
(In reply to Michał Dybczak from comment #29)
> This isn't fixed. This is how it looks on Plasma 5.18.0
This issue can't be really fixed on X11. We can only work around some cases. If
an application uses a graphics API such as OpenGL or Vulkan to draw user
interface, then the client contents may still be rendered unsynchronized. For
what it's worth, one of the reasons why we have "resize" effect is because
resizing windows on X11 is lame.

I also would like to point out that such visual artifacts can't be seen on
Wayland because "each frame is perfect."

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

[lattedock] [Bug 417817] New: Notification in latte stop working

2020-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=417817

Bug ID: 417817
   Summary: Notification in latte stop working
   Product: lattedock
   Version: 0.9.8.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: ra...@foxmail.com
  Target Milestone: ---

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

SUMMARY
Notification in latte stop working.
Any notificatoin widget outside of latte, e.g. on the desktop or in the default
panel, will work.

STEPS TO REPRODUCE
1. Add a notification widget in latte

OBSERVED RESULT
1. Not working
EXPECTED RESULT
1. Working

SOFTWARE/OS VERSIONS
OS: Arch
KDE Plasma Version: 5.18.0
KDE Frameworks Version: 5.67.0
Qt Version: 5.14.1

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

[amarok] [Bug 392635] Compile error on KDE Neon 5.12: cannot convert ‘const wchar_t*’ to ‘TagLib::FileName

2020-02-17 Thread Serhiy Zahoriya
https://bugs.kde.org/show_bug.cgi?id=392635

--- Comment #6 from Serhiy Zahoriya  ---
Thank you, Myriam. Unfortunately this is beyond the scope of my current
familiarity with C++ and amarok source. I tried looking into it but it's some
old fork of amarok, before 2.0 and I don't know yet how to port these changes.

> else nobody will look at
Amarok FTBFS on newer systems which is critical. It's either someone will have
to look at it eventually or we can close this as unmaintained.

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

[Smb4k] [Bug 417754] Starts with error "The URL does not exist"

2020-02-17 Thread Alexander Reinholdt
https://bugs.kde.org/show_bug.cgi?id=417754

Alexander Reinholdt  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/smb
   ||4k/25ef2f3579386fa25674c20b
   ||c8f63471017e5d4b

--- Comment #2 from Alexander Reinholdt  ---
Git commit 25ef2f3579386fa25674c20bc8f63471017e5d4b by Alexander Reinholdt.
Committed on 18/02/2020 at 06:05.
Pushed by areinholdt into branch 'master'.

Stop Smb4K from reporting an error if the query for domains and workgroups
fails.

M  +8-0core/smb4kclient_p.cpp

https://commits.kde.org/smb4k/25ef2f3579386fa25674c20bc8f63471017e5d4b

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

[digikam] [Bug 417797] Batch video timestamp changing fails

2020-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=417797

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

   What|Removed |Added

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

--- Comment #3 from caulier.gil...@gmail.com ---
And please report if this will fix your workflow, to be able to close this
file.

Thanks in advance

Gilles Caulier

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

[digikam] [Bug 397901] Work-around for maximum number of images in an album

2020-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=397901

--- Comment #10 from caulier.gil...@gmail.com ---
Pete,

Your dysfunction is not reproducible here with plenty of albums including a
lots of items inside (some ahve more than 1000 photos)

Can you reproduce your problem using digiKAm Linux AppImage 7.0.0-beta3 ?

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

Gilles Caulier

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

[plasma-nm] [Bug 417816] Duplicate entry for currently connected wifi network

2020-02-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=417816

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #4 from Nate Graham  ---
All right.

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

[kdeconnect] [Bug 415881] Nothing happen when launching KDE connect SMS GUI

2020-02-17 Thread Anjani Kumar
https://bugs.kde.org/show_bug.cgi?id=415881

Anjani Kumar  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED
 CC||anjanik...@gmail.com

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

[plasma-nm] [Bug 417816] Duplicate entry for currently connected wifi network

2020-02-17 Thread Jan Grulich
https://bugs.kde.org/show_bug.cgi?id=417816

--- Comment #3 from Jan Grulich  ---
I have no idea, maybe you logged in with a different user? 

Can we close this bug now?

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

[kontact] [Bug 415634] kontact crash on opening settings

2020-02-17 Thread Wolfgang Bauer
https://bugs.kde.org/show_bug.cgi?id=415634

--- Comment #10 from Wolfgang Bauer  ---
(In reply to Morbid from comment #9)
> The same issue is present on Arch.
> Operating System: Arch Linux 
> KDE Plasma Version: 5.18.0
> KDE Frameworks Version: 5.67.0

I find it very likely that you actually experience bug#417396, which is a
regression in KDE Frameworks 5.67 and is 100% reliable to crash kontact when
opening the settings AFAICT (unlike this bug)...

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

[plasma-nm] [Bug 417816] Duplicate entry for currently connected wifi network

2020-02-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=417816

--- Comment #2 from Nate Graham  ---
I do indeed see two entries in the KCM.

Looks like I can delete the duplicate. But I guess the question remains: how
did it get created?

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

[digikam] [Bug 332903] Altering Geo-Data

2020-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=332903

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

   What|Removed |Added

 Resolution|DUPLICATE   |FIXED
   Version Fixed In||7.0.0

--- Comment #2 from caulier.gil...@gmail.com ---
Fixed with bug #324516

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

[digikam] [Bug 327466] Digikam crashes after launching alternate image processing software

2020-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=327466

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

   What|Removed |Added

 Resolution|DUPLICATE   |FIXED
   Version Fixed In||7.0.0

--- Comment #3 from caulier.gil...@gmail.com ---
Fixed with bug #327143

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

[plasma-nm] [Bug 417816] Duplicate entry for currently connected wifi network

2020-02-17 Thread Jan Grulich
https://bugs.kde.org/show_bug.cgi?id=417816

Jan Grulich  changed:

   What|Removed |Added

 CC||jgrul...@redhat.com

--- Comment #1 from Jan Grulich  ---
>From the log it looks the "Network Node" connection is there twice. Can you
open the KCM and verify there is just one?

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

[kompare] [Bug 417156] Compare button remains grayed out

2020-02-17 Thread Wolfgang Bauer
https://bugs.kde.org/show_bug.cgi?id=417156

--- Comment #7 from Wolfgang Bauer  ---
(In reply to Mike from comment #5)
> What "text" field?  Source and Destination? The ones where you choose the
> files? That doesn't do anything.

Quoting from the other bug report:
> As a temporary workaround after choosing files typing anything in either box
> (even a space) activates the button.

And yes, "either box" means the Source or Destination in the dialog shown on
your screen shot (not the file chooser), click on the text (showing the
file/folder path) and you should be able to edit it.

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

[plasma-nm] [Bug 417816] New: Duplicate entry for currently connected wifi network

2020-02-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=417816

Bug ID: 417816
   Summary: Duplicate entry for currently connected wifi network
   Product: plasma-nm
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: applet
  Assignee: jgrul...@redhat.com
  Reporter: n...@kde.org
  Target Milestone: ---

Created attachment 126116
  --> https://bugs.kde.org/attachment.cgi?id=126116=edit
Duplicate network

Everything from git master.

I see a duplicate entry for my currently connected wifi network. See attached
screenshot.

here's the log info shown when I open the applet:
plasma-nm: Requesting wifi scan on device "wlp1s0"
plasma-nm: New connection  "Network Node"  added
plasma-nm: New connection  "sunport"  added
plasma-nm: New connection  "NETGEAR73"  added
plasma-nm: New connection  "RRX Hotspot"  added
plasma-nm: New connection  "Free Wi-Fi Vodafone+DUSAirport"  added
plasma-nm: New connection  "Schloss-Gehrden"  added
plasma-nm: New connection  "Network Node"  added
plasma-nm: New connection  "ATL Free Wi-Fi"  added
plasma-nm: New wireless network  "Network Node"  added
plasma-nm: Item  "Network Node" : device changed to 
"/org/freedesktop/NetworkManager/Devices/2"
plasma-nm: Access point  "Network Node" : merged to  "Network Node"  connection
plasma-nm: Item  "Network Node" : device changed to 
"/org/freedesktop/NetworkManager/Devices/2"
plasma-nm: Item  "Network Node" : active connection state changed to  2
plasma-nm: Wireless scan on "wlp1s0" succeeded
plasma-nm: New wireless network  "CenturyLink4759_5G"  added
plasma-nm: New wireless network  "CenturyLink9149"  added
plasma-nm: New wireless network  "CenturyLink2600"  added
plasma-nm: New wireless network  "GreyWolf"  added
plasma-nm: New wireless network  "CenturyLink7734"  added
plasma-nm: New wireless network  "CenturyLink4738"  added
plasma-nm: Last scan finished  7541 ms ago and last request scan was sent 
10300 ms ago, Skipping scanning interface: "wlp1s0"
plasma-nm: Rescheduling a request scan for "wlp1s0" in 2459
plasma-nm: Requesting wifi scan on device "wlp1s0"
plasma-nm: Wireless scan on "wlp1s0" succeeded

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

[kate] [Bug 417811] click+hold on scrollbar thumb triggers scrolling to that point on the track instead of allowing drag

2020-02-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=417811

Nate Graham  changed:

   What|Removed |Added

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

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

[plasmashell] [Bug 417803] Clock needs more margin to the right when placed on a horizontal panel

2020-02-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=417803

Nate Graham  changed:

   What|Removed |Added

Summary|Clock needs more margin to  |Clock needs more margin to
   |the right   |the right when placed on a
   ||horizontal panel
 Ever confirmed|0   |1
 CC||n...@kde.org
   Severity|normal  |minor
 Status|REPORTED|CONFIRMED

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

[plasmashell] [Bug 417810] Navigating with arrow keys does not return to previous location in menu

2020-02-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=417810

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #1 from Nate Graham  ---
This was fixed in 5.17 IIRC.

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

[plasmashell] [Bug 417808] Start menu goes gray when navigating with arrow keys

2020-02-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=417808

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #2 from Nate Graham  ---
Fixed in 5.17.

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

[systemsettings] [Bug 416358] kcm_fonts: Cannot apply changes (button remains inactive)

2020-02-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=416358

Nate Graham  changed:

   What|Removed |Added

 CC||luanrodrigue...@gmail.com

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

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

[gwenview] [Bug 417815] Gwenview does not render SVG images correctly

2020-02-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=417815

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #2 from Nate Graham  ---


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

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

[gwenview] [Bug 336436] Switch to webkit or blink when rendering SVG files

2020-02-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=336436

Nate Graham  changed:

   What|Removed |Added

 CC||joey.joey...@gmail.com

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

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

[systemsettings] [Bug 417812] Save button won't enable on font settings

2020-02-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=417812

Nate Graham  changed:

   What|Removed |Added

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

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


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

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

[digikam] [Bug 397819] Digikam not showing date taken

2020-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=397819

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

   What|Removed |Added

 Resolution|--- |FIXED
   Version Fixed In||7.0.0
  Latest Commit||https://invent.kde.org/kde/
   ||digikam/commit/d6bb498d394d
   ||f90d203598840281293f1598568
   ||0
 Status|REPORTED|RESOLVED

--- Comment #5 from caulier.gil...@gmail.com ---
Git commit d6bb498d394df90d203598840281293f15985680 by Gilles Caulier.
Committed on 18/02/2020 at 05:05.
Pushed by cgilles into branch 'master'.

TableView: add Photo take date properties as configurable row to show in
list-view
FIXED-IN:7.0.0

M  +4-3NEWS
M  +2-1core/app/views/tableview/tableview_column_file.cpp
M  +50   -19   core/app/views/tableview/tableview_column_photo.cpp
M  +2-1core/app/views/tableview/tableview_column_photo.h
M  +1-0core/app/views/tableview/tableview_columnfactory.h
M  +4-4core/app/views/tableview/tableview_model.cpp

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

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

[digikam] [Bug 417797] Batch video timestamp changing fails

2020-02-17 Thread Jan van Bekkum
https://bugs.kde.org/show_bug.cgi?id=417797

--- Comment #2 from Jan van Bekkum  ---
Thanks, I'll do that.

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

[plasmashell] [Bug 415649] Change option to 'Open groups in popups, only when Task Manager is full'.

2020-02-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=415649

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In||5.19.0
 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://commits.kde.org/pla
   ||sma-desktop/c32b5a85cae6f99
   ||bb5097b16a25983fc611aecc6
 Resolution|--- |FIXED

--- Comment #5 from Nate Graham  ---
Git commit c32b5a85cae6f99bb5097b16a25983fc611aecc6 by Nate Graham, on behalf
of George Vogiatzis.
Committed on 18/02/2020 at 04:49.
Pushed by ngraham into branch 'master'.

[Applets/Task Manager] Fix and improve behavior tab layouts

Summary:
Fix the group layout.
Change rest of behavior tab layout.
Rename various labels and texts.
FIXED-IN: 5.19.0

Test Plan:
Before:
The indentation of option "Group only when the Task Manager is full"
is misleading.

Before:
{F7882775, layout=inline} {F7882776, layout=inline}

After:
{F7883513, layout=inline} {F7882780, layout=inline}

Reviewers: #vdg, #plasma, hein, ngraham

Reviewed By: #vdg, ngraham

Subscribers: plasma-devel

Tags: #plasma

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

M  +16   -19   applets/taskmanager/package/contents/ui/ConfigBehavior.qml

https://commits.kde.org/plasma-desktop/c32b5a85cae6f99bb5097b16a25983fc611aecc6

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

[plasma-nm] [Bug 417710] Odd spacing for "Wifi" and "Airplane mode" toggles

2020-02-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=417710

Nate Graham  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/pla
   ||sma-nm/88b8ce5e50b75daf025e
   ||b3e59cf1726cd74ba2d9
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #4 from Nate Graham  ---
Git commit 88b8ce5e50b75daf025eb3e59cf1726cd74ba2d9 by Nate Graham, on behalf
of George Vogiatzis.
Committed on 18/02/2020 at 04:42.
Pushed by ngraham into branch 'master'.

[Applet]Update toolbar's checkbox spacing

Summary:
Move the switchButton's icon smallSpacing left.
Make icon size smallMedium.

Test Plan:
Before:
{F8108357, size =full}
After:
{F8108335, size =full}

Reviewers: #plasma, #vdg, jgrulich, ngraham

Reviewed By: #vdg, jgrulich, ngraham

Subscribers: broulik, plasma-devel

Tags: #plasma

Maniphest Tasks: T10470

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

M  +7-9applet/contents/ui/SwitchButton.qml

https://commits.kde.org/plasma-nm/88b8ce5e50b75daf025eb3e59cf1726cd74ba2d9

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

[kdenlive] [Bug 417076] Timeline time scale is not correctly modified when loading or creating project with non-default frame rate

2020-02-17 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=417076

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

[lokalize] [Bug 377548] lokalize gives wrong spelling errors after colon :

2020-02-17 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=377548

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

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

[konsole] [Bug 401094] Malayalam rendering regression in Konsole 18.08

2020-02-17 Thread Rajeesh K V
https://bugs.kde.org/show_bug.cgi?id=401094

--- Comment #24 from Rajeesh K V  ---
(In reply to Kurt Hindenburg from comment #23)
> To clarify, this ping is for the update of GLASS file?  Is there a patch for
> the actual code changes?

The ping is for fixing complex script shaping, see topmost commits by Mariusz
here: https://invent.kde.org/mglebocki/konsole/tree/wip/complex-scripts-support

The update to GLASS file is nice to have, not urgent though.

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

[gwenview] [Bug 417815] Gwenview does not render SVG images correctly

2020-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=417815

--- Comment #1 from joey.joey...@gmail.com ---
Created attachment 126115
  --> https://bugs.kde.org/attachment.cgi?id=126115=edit
2nd svg attachment

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

[gwenview] [Bug 417815] New: Gwenview does not render SVG images correctly

2020-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=417815

Bug ID: 417815
   Summary: Gwenview does not render SVG images correctly
   Product: gwenview
   Version: 19.12.2
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: joey.joey...@gmail.com
  Target Milestone: ---

Created attachment 126114
  --> https://bugs.kde.org/attachment.cgi?id=126114=edit
1st svg attachment

SUMMARY
Some parts of .svg images, such as text, don't seem to be rendering correctly

STEPS TO REPRODUCE
1. Open the attached files in Eye of Gnome (eog) which renders it correctly
2. Open the files in Gwenview
3. Compare how the two image viewers render it side by side

OBSERVED RESULT
Text is not rendered in Gwenview

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.18.0
KDE Frameworks Version: 5.67.0
Qt Version: 5.14.1
Kernel Version: 5.5.4-zen1-1-zen
OS Type: 64-bit
Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz
Memory: 11.5 GiB of RAM


ADDITIONAL INFORMATION

Also, try running this command "systemd-analyze plot > plot.svg"
Notice how Gwenview does not render the svg correctly to some degree

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

[plasmashell] [Bug 417718] Pinning, launching, dragging icons reorder icons in unwanted ways.

2020-02-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=417718

Nate Graham  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |INTENTIONAL

--- Comment #3 from Nate Graham  ---
Thanks, that's helpful.

However this is just how the Task Manager works. If you want the icons to not
move around after being launched, you might be happier switching it with the
Icons-Only Task Manager.

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

[plasmashell] [Bug 417752] Limit the number of emojis remembered 0n the "Recent" page

2020-02-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=417752

Nate Graham  changed:

   What|Removed |Added

   Severity|normal  |wishlist
 Status|NEEDSINFO   |CONFIRMED
Summary|emoji picker does not have  |Limit the number of emojis
   |a button to delete the  |remembered 0n the "Recent"
   |recent ones |page
 Resolution|WAITINGFORINFO  |---
 Ever confirmed|0   |1

--- Comment #3 from Nate Graham  ---
It might make more sense to automatically delete the oldest ones after there
are, say, 20 or 30 or 40 entries. Let's do that instead.

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

[digikam] [Bug 417708] video export => geolocation is not exported

2020-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=417708

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

   What|Removed |Added

   Version Fixed In||7.0.0
 CC||caulier.gil...@gmail.com

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

[kwin] [Bug 417716] With non-breeze aurorae theme and "No Borders" setting it's no longer possible to get resize cursor on titlebar's upper edge

2020-02-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=417716

--- Comment #3 from Nate Graham  ---
Created attachment 126113
  --> https://bugs.kde.org/attachment.cgi?id=126113=edit
"No Borders" setting

Right here

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

[plasmashell] [Bug 410770] Settings window of touchpad indicator is broken

2020-02-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=410770

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In||5.18.1

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

[klipper] [Bug 417590] you need to double click copy to clipboard in English to copy them

2020-02-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=417590

Nate Graham  changed:

   What|Removed |Added

   Keywords||regression

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

[kwin] [Bug 415839] Resizing apps results in flickering or controls jumping around

2020-02-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=415839

--- Comment #30 from Nate Graham  ---
This bugfix primarily improved the behavior for QWidgets apps, AFAIK. QML apps
will need other fixes, as I understand it.

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

[frameworks-syntax-highlighting] [Bug 406821] Dark UI color theme breaks default LightTheme

2020-02-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=406821

Nate Graham  changed:

   What|Removed |Added

 CC||frankeba...@gmail.com

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

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

[dolphin] [Bug 417809] Preview text files inconsistent with pale text color schemes

2020-02-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=417809

Nate Graham  changed:

   What|Removed |Added

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

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


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

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

[krita] [Bug 417814] New: Measure Tool should have an option to make it stay after switching to another tool

2020-02-17 Thread Melvin Vermeeren
https://bugs.kde.org/show_bug.cgi?id=417814

Bug ID: 417814
   Summary: Measure Tool should have an option to make it stay
after switching to another tool
   Product: krita
   Version: 4.2.8
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Tool/Assistants
  Assignee: krita-bugs-n...@kde.org
  Reporter: m...@mel.vin
  Target Milestone: ---

SUMMARY
It's currently not possible to make the result of a measurement "stick" as you
switch to other tools, making it difficult to use it correctly. Ideally it
would behave somewhat like other assistants, creating a real object that can be
moved, deleted, etc.

STEPS TO REPRODUCE
1. Use measure tool to measure something.
2. Select the brush tool.

OBSERVED RESULT
Measurement result is gone, can't refer to the result while painting.

EXPECTED RESULT
Some way to make the result stick while continuing to paint.

SOFTWARE/OS VERSIONS
Krita 4.2.8, manual backport.

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

[krita] [Bug 417814] Measure Tool should have an option to make it stay after switching to another tool

2020-02-17 Thread Melvin Vermeeren
https://bugs.kde.org/show_bug.cgi?id=417814

Melvin Vermeeren  changed:

   What|Removed |Added

 CC||m...@mel.vin

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

[krita] [Bug 417813] Measure Tool should support setting the arbitrary base line to compare to

2020-02-17 Thread Melvin Vermeeren
https://bugs.kde.org/show_bug.cgi?id=417813

Melvin Vermeeren  changed:

   What|Removed |Added

 CC||m...@mel.vin

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

[krita] [Bug 417813] New: Measure Tool should support setting the arbitrary base line to compare to

2020-02-17 Thread Melvin Vermeeren
https://bugs.kde.org/show_bug.cgi?id=417813

Bug ID: 417813
   Summary: Measure Tool should support setting the arbitrary base
line to compare to
   Product: krita
   Version: 4.2.8
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Tool/Assistants
  Assignee: krita-bugs-n...@kde.org
  Reporter: m...@mel.vin
  Target Milestone: ---

Created attachment 126112
  --> https://bugs.kde.org/attachment.cgi?id=126112=edit
measuring a v in gimp

SUMMARY
The measure tool cannot measure between two non-horizontal lines.

STEPS TO REPRODUCE
1. Draw the letter V on a canvas, make it big.
1. Select the measure tool.
2. Try to measure an angle between between the two lines of the V.

OBSERVED RESULT
The measure tool snaps to perfect horizontal. Unless you draw one of the two
lines of your V perfectly horizontally it is not easy to measure the angle
between the two lines.

EXPECTED RESULT
Some method to specify two lines to measure angle between.

SOFTWARE/OS VERSIONS
Krita 4.2.8, manual backport.

ADDITIONAL INFORMATION
GIMP's measure tool can do this if you hold shift and click on the start point
after setting the first measurement line. See the attachment.

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

[plasmashell] [Bug 360478] Desktop widgets are permanently repositioned when fullscreen games lower display resolution

2020-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=360478

hoperidesal...@protonmail.ch changed:

   What|Removed |Added

 CC||hoperidesalone@protonmail.c
   ||h

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

[ksysguard] [Bug 384515] [ksysguardd]: Internal buffer too small to read '/proc/cpuinfo'

2020-02-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=384515

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In||5.19.0

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

[systemsettings] [Bug 417812] New: Save button won't enable on font settings

2020-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=417812

Bug ID: 417812
   Summary: Save button won't enable on font settings
   Product: systemsettings
   Version: 5.18.0
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_fonts
  Assignee: plasma-b...@kde.org
  Reporter: luanrodrigue...@gmail.com
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. Go to Fonts Settings
2. Change some config
3. Try to save 

OBSERVED RESULT
Save button stays disable 

EXPECTED RESULT
Enable save button after some config is changed

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

ADDITIONAL INFORMATION

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

[kate] [Bug 417811] New: click+hold on scrollbar thumb triggers scrolling to that point on the track instead of allowing drag

2020-02-17 Thread fantasai
https://bugs.kde.org/show_bug.cgi?id=417811

Bug ID: 417811
   Summary: click+hold on scrollbar thumb triggers scrolling to
that point on the track instead of allowing drag
   Product: kate
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: fantasai.b...@inkedblade.net
  Target Milestone: ---

SUMMARY
One common method of interacting with a scrollbar is to drag the thumb to the
desired position. This is currently broken in Kate because the click needed to
activate dragging behavior (triggered by click+hold of the mouse) changes the
scroll position. Point-and-click scrolling should be triggered on mouseup, not
mousedown, and not if there was a drag operation in between.

STEPS TO REPRODUCE
1. Open a multi-page document
2. Scroll partway down.
3. Click on the scrollbar and hold down the mouse, as if you're going to drag
the scrollbar thumb to scroll the document.
4. Pause and observe what happened...

OBSERVED RESULT

Notice that even before you drag the thumb, the page has scrolled to some
random other point, depending on where in the scrollbar thumb you happened to
click.


EXPECTED RESULT

Holding down the mouse key on the scrollbar thumb should have no effect on the
scroll position.
SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[neon] [Bug 417791] Snap package of cantor doesn't work on RHEL 7

2020-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=417791

--- Comment #11 from scx.m...@gmail.com ---
(In reply to Jonathan Riddell from comment #3)

Where is the snap repo for KDE apps (e.g. cantor, kolourpaint, okular, etc.)
and runtimes (kde-frameworks-5, kde-frameworks-5-core18,
kde-frameworks-5-core18-sdk, kde-frameworks-5-qt-5-14-core18,
kde-frameworks-5-qt-5-14-core18-sdk)?
I don't see the snap folder in app repositories.
https://cgit.kde.org/cantor.git/tree/

What is worse, I don't see kde-frameworks-5* repos at all.

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

[krita] [Bug 417673] Visible tiling artifacts from Filter Masks

2020-02-17 Thread M
https://bugs.kde.org/show_bug.cgi?id=417673

--- Comment #4 from M  ---
No, I can't reproduce the crash in master (git 9643b51) nor the latest stable
AppImage anymore, with any of the filters. I realize now Gaussian Highpass
isn't actually supposed to be in 4.2, it might have been residue from previous
builds since I didn't do a clean one. In which case sorry for the false alarm
:(

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

[frameworks-plasma] [Bug 332512] Plasma Popups aren't resizable, and if you force-resize them, they forget their size after the computer or plasmashell is restarted

2020-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=332512

russellp...@yandex.ru changed:

   What|Removed |Added

 CC||russellp...@yandex.ru

--- Comment #82 from russellp...@yandex.ru ---
After updating from 5.17.5 to 5.18.0 it's no longer possible to resize using
Alt+right mouse button.

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

[konsole] [Bug 401094] Malayalam rendering regression in Konsole 18.08

2020-02-17 Thread Kurt Hindenburg
https://bugs.kde.org/show_bug.cgi?id=401094

--- Comment #23 from Kurt Hindenburg  ---
To clarify, this ping is for the update of GLASS file?  Is there a patch for
the actual code changes?

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

[krita] [Bug 344143] Enabling OCIO makes the advanced colorselector unable to pick primaries

2020-02-17 Thread L. E. Segovia
https://bugs.kde.org/show_bug.cgi?id=344143

L. E. Segovia  changed:

   What|Removed |Added

 CC||a...@amyspark.me
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #2 from L. E. Segovia  ---
Unable to reproduce this with Krita in the 4.2 branch
(dac91dfbe735e35af2f7ce1fef930960915c6148), tried with RGB 8-bit and 32-bit
floating point. OpenColorIO-Configs commit was
0bb079c08be410030669cbf5f19ff869b88af953.

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

[plasmashell] [Bug 417810] New: Navigating with arrow keys does not return to previous location in menu

2020-02-17 Thread Jack
https://bugs.kde.org/show_bug.cgi?id=417810

Bug ID: 417810
   Summary: Navigating with arrow keys does not return to previous
location in menu
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: k...@davidedmundson.co.uk
  Reporter: j...@darvaltech.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

SUMMARY
When navigating through the application menu and submenus if I enter a submenu
and go back (left) then the selected item is the top entry always, I would
expect the item to be selected to be the item that I had entered from. I.e.
Item1 -> Item1-1, 1-2, 1-3
Item2 -> Item2-1, 2-2
Item3 -> Item3-1, 3-2, 3-3
If I enter the Item2 menu and then go back, the selected item will be #1.

STEPS TO REPRODUCE
1. Open kickoff and navigate through the menu to the second or third item in
the list.
2. Enter that second or third item and then hit back to go back to the top
level item.
3. Observe that the first item is selected.

OBSERVED RESULT
When returning the first item is always selected.

EXPECTED RESULT
The previously selected item should be selected i.e. enter off item2 -> item2
selected.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 19.10
KDE Plasma Version: 5.16.5
KDE Frameworks Version: 5.62.0
Qt Version: 5.12.4

ADDITIONAL INFORMATION
Linux Kernel: 5.3.0-29-generic 64 bit
Nvidia GTX1080

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

[krita] [Bug 400306] Internal Color Selector doesn't work in CMYK Float32 and LABA Float32 modes

2020-02-17 Thread L. E. Segovia
https://bugs.kde.org/show_bug.cgi?id=400306

L. E. Segovia  changed:

   What|Removed |Added

  Latest Commit|dffa076018d6bf98ec0e3d7c232 |https://invent.kde.org/krit
   |dc2825fd47c11   |a/kde/commit/dffa076018d6bf
   ||98ec0e3d7c232dc2825fd47c11

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

[plasmashell] [Bug 417808] Start menu goes gray when navigating with arrow keys

2020-02-17 Thread Jack
https://bugs.kde.org/show_bug.cgi?id=417808

--- Comment #1 from Jack  ---
Created attachment 126111
  --> https://bugs.kde.org/attachment.cgi?id=126111=edit
Shows application menu visibly grayed out

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

[dolphin] [Bug 417809] Preview text files inconsistent with pale text color schemes

2020-02-17 Thread Francis Lamonde
https://bugs.kde.org/show_bug.cgi?id=417809

Francis Lamonde  changed:

   What|Removed |Added

 CC||frankeba...@gmail.com

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

[krita] [Bug 400306] Internal Color Selector doesn't work in CMYK Float32 and LABA Float32 modes

2020-02-17 Thread L. E. Segovia
https://bugs.kde.org/show_bug.cgi?id=400306

L. E. Segovia  changed:

   What|Removed |Added

 CC||a...@amyspark.me
 Status|CONFIRMED   |RESOLVED
  Latest Commit||dffa076018d6bf98ec0e3d7c232
   ||dc2825fd47c11
 Resolution|--- |FIXED

--- Comment #3 from L. E. Segovia  ---
Fixed in my SoK project.

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

[dolphin] [Bug 417809] New: Preview text files inconsistent with pale text color schemes

2020-02-17 Thread Francis Lamonde
https://bugs.kde.org/show_bug.cgi?id=417809

Bug ID: 417809
   Summary: Preview text files inconsistent with pale text color
schemes
   Product: dolphin
   Version: 19.12.2
  Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: frankeba...@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

Created attachment 126110
  --> https://bugs.kde.org/attachment.cgi?id=126110=edit
Preview text files example

SUMMARY
This behavior is also noticeable on some previous versions of Dolphin/KDE.

Preview text files display white text on white icon files, therefore making the
preview unreadable.

See attached picture.


STEPS TO REPRODUCE
1. Enable TEXT FILES in PREVIEW tab of GENERAL section of Dolphin's CONFIGURE
menu
2. Apply a color scheme with white text or change your current color scheme to
use white text
2. Restart Dolphin or in some cases log-out and log back in to make sure
3. Preview text from text files, with and without extensions, .bashrc, .sh,
etc.

OBSERVED RESULT
When you choose a color scheme that uses white (or very pale) text and you
enable PREVIEW FOR TEXT FILES in Dolphin, what happens is that all text file
icons don't show the text preview, because all icons are white and the text is
white. Technically the text does display but it's white on white.

If you choose a color scheme with non-white text it will use that color to
preview text within the text icon files and then you can read the preview.

However for files with extensions, like .sh as example, the text previews just
fine, in BLACK and even with the colors associated to the commands, no matter
what color scheme is chosen.


EXPECTED RESULT
If the text file icons are white, then the text should always be black,
regardless of the color scheme. In the end, if you choose to preview text
files, the text should be able to preview, otherwise it breaks the feature.


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Kubuntu 19.10 - Kubuntu 20.04
(available in About System)
KDE Plasma Version: 5.18.0
KDE Frameworks Version: 5.67.0
Qt Version: 5.12.4

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 417808] New: Start menu goes gray when navigating with arrow keys

2020-02-17 Thread Jack
https://bugs.kde.org/show_bug.cgi?id=417808

Bug ID: 417808
   Summary: Start menu goes gray when navigating with arrow keys
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: k...@davidedmundson.co.uk
  Reporter: j...@darvaltech.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

SUMMARY
I've started navigating through the start menu with the arrow keys trying to
find a program which isn't available in search and the menu goes gray or into
some form of timeout after a few seconds of mouse inactivity. This probably
shouldn't occur if I'm still navigating with the keys.

STEPS TO REPRODUCE
1. Open the kickoff/start menu.
2. Navigate around using keys for a bit (+10sec).
3. Observe menu go gray.

OBSERVED RESULT
Menu goes gray as if it's inactive or timed out.

EXPECTED RESULT
When navigating with keys this should reset whatever activity timer the
gray/timeout is using so I can still see the menu at the same brightness.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 19.10
KDE Plasma Version: 5.16.5
KDE Frameworks Version: 5.62.0
Qt Version: 5.12.4

ADDITIONAL INFORMATION
Linux Kernel: 5.3.0-29-generic 64 bit
Nvidia GTX1080
Laptop plugged in and fully charged, no sleep modes enabled

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

[kwin] [Bug 417807] New: kwin crash after external monitor turned off and on again

2020-02-17 Thread Tim Richardson
https://bugs.kde.org/show_bug.cgi?id=417807

Bug ID: 417807
   Summary: kwin crash after external monitor turned off and on
again
   Product: kwin
   Version: 5.18.0
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: t...@tim-richardson.net
  Target Milestone: ---

Application: kwin_x11 (5.18.0)

Qt Version: 5.14.1
Frameworks Version: 5.67.0
Operating System: Linux 5.3.18-customrc6 x86_64
Windowing system: X11
Distribution: KDE neon User Edition 5.18

-- Information about the crash:
- What I was doing when the application crashed:
external monitor was turned off and then turned on again. The physical
connection did not change.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f734948ee80 (LWP 3955))]

Thread 7 (Thread 0x7f730bfff700 (LWP 5624)):
#0  0x7f7341d699f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x55c63af658b0) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f7341d699f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55c63af65860, cond=0x55c63af65888) at pthread_cond_wait.c:502
#2  0x7f7341d699f3 in __pthread_cond_wait (cond=0x55c63af65888,
mutex=0x55c63af65860) at pthread_cond_wait.c:655
#3  0x7f7345d5dd9b in QWaitConditionPrivate::wait(QDeadlineTimer)
(deadline=..., this=0x55c63af65860) at thread/qwaitcondition_unix.cpp:146
#4  0x7f7345d5dd9b in QWaitCondition::wait(QMutex*, QDeadlineTimer)
(this=, mutex=0x55c63ac05c90, deadline=...) at
thread/qwaitcondition_unix.cpp:225
#5  0x7f7345d5df19 in QWaitCondition::wait(QMutex*, unsigned long)
(this=this@entry=0x55c63ac05c98, mutex=mutex@entry=0x55c63ac05c90,
time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208
#6  0x7f7340e911d3 in QSGRenderThreadEventQueue::takeEvent(bool)
(wait=true, this=0x55c63ac05c88) at scenegraph/qsgthreadedrenderloop.cpp:255
#7  0x7f7340e911d3 in QSGRenderThread::processEventsAndWaitForMore()
(this=this@entry=0x55c63ac05bf0) at scenegraph/qsgthreadedrenderloop.cpp:905
#8  0x7f7340e91631 in QSGRenderThread::run() (this=0x55c63ac05bf0) at
scenegraph/qsgthreadedrenderloop.cpp:1000
#9  0x7f7345d577ec in QThreadPrivate::start(void*) (arg=0x55c63ac05bf0) at
thread/qthread_unix.cpp:342
#10 0x7f7341d636db in start_thread (arg=0x7f730bfff700) at
pthread_create.c:463
#11 0x7f7348e0488f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 6 (Thread 0x7f73279c7700 (LWP 23674)):
#0  0x7f7341d699f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x55c63acf5a24) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f7341d699f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55c63acf59d0, cond=0x55c63acf59f8) at pthread_cond_wait.c:502
#2  0x7f7341d699f3 in __pthread_cond_wait (cond=0x55c63acf59f8,
mutex=0x55c63acf59d0) at pthread_cond_wait.c:655
#3  0x7f7345d5dd9b in QWaitConditionPrivate::wait(QDeadlineTimer)
(deadline=..., this=0x55c63acf59d0) at thread/qwaitcondition_unix.cpp:146
#4  0x7f7345d5dd9b in QWaitCondition::wait(QMutex*, QDeadlineTimer)
(this=, mutex=0x55c63ace8410, deadline=...) at
thread/qwaitcondition_unix.cpp:225
#5  0x7f7345d5df19 in QWaitCondition::wait(QMutex*, unsigned long)
(this=this@entry=0x55c63ace8418, mutex=mutex@entry=0x55c63ace8410,
time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208
#6  0x7f7340e911d3 in QSGRenderThreadEventQueue::takeEvent(bool)
(wait=true, this=0x55c63ace8408) at scenegraph/qsgthreadedrenderloop.cpp:255
#7  0x7f7340e911d3 in QSGRenderThread::processEventsAndWaitForMore()
(this=this@entry=0x55c63ace8370) at scenegraph/qsgthreadedrenderloop.cpp:905
#8  0x7f7340e91631 in QSGRenderThread::run() (this=0x55c63ace8370) at
scenegraph/qsgthreadedrenderloop.cpp:1000
#9  0x7f7345d577ec in QThreadPrivate::start(void*) (arg=0x55c63ace8370) at
thread/qthread_unix.cpp:342
#10 0x7f7341d636db in start_thread (arg=0x7f73279c7700) at
pthread_create.c:463
#11 0x7f7348e0488f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 5 (Thread 0x7f7325644700 (LWP 4315)):
#0  0x7f7341d699f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x7f7345142fb8) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f7341d699f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x7f7345142f68, cond=0x7f7345142f90) at pthread_cond_wait.c:502
#2  0x7f7341d699f3 in __pthread_cond_wait (cond=0x7f7345142f90,
mutex=0x7f7345142f68) at pthread_cond_wait.c:655
#3  0x7f7344e4d944 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#4  0x7f7344e4d989 in  () at 

[frameworks-kio] [Bug 417806] New: Open/Save File dialogs do not adhere to current directory modification

2020-02-17 Thread Lastique
https://bugs.kde.org/show_bug.cgi?id=417806

Bug ID: 417806
   Summary: Open/Save File dialogs do not adhere to current
directory modification
   Product: frameworks-kio
   Version: 5.62.0
  Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Open/save dialogs
  Assignee: fa...@kde.org
  Reporter: andy...@mail.ru
CC: kdelibs-b...@kde.org
  Target Milestone: ---

SUMMARY

The Open/Save File dialogs do not notice the current directory field
modification by user and open/save the file to the original current directory.


STEPS TO REPRODUCE

1. Run an application that will use the common Save File dialog. For example,
Kate.
2. Invoke the Save File dialog. E.g. File -> Save As in Kate.
3. In the Save File dialog, click on the current directory input field at the
top and modify it by typing a new path.
4. Click on the file name input field and type the file name.
5. Click on the Save button.

OBSERVED RESULT

The new file is created at the original current directory, not the one I typed
at step 3.

EXPECTED RESULT

The Save File dialog should use the directory I typed. Preferably, when the
input field focus is lost, the dialog should update the directory view to the
directory I typed, so that the path and the directory view are in sync.

STEPS TO REPRODUCE

1. Run an application that will use the common Open File dialog. For example,
Kate.
2. Invoke the Open File dialog. E.g. File -> Open in Kate.
3. In the Open File dialog, click on the current directory input field at the
top and modify it by typing a new path.
4. Click on the file name input field or the directory view.
5. Click on the file name input field and type the file name.
6. Click on the Open button.

OBSERVED RESULT

At step 4, the directory view keeps showing the original current directory
contents, the dialog does not seem to register that the current directory was
updated. At step 6, the file is opened at the original current directory
(provided that the file exists at that location), not at the modified one.

EXPECTED RESULT

Same as with the Save File dialog.

SOFTWARE/OS VERSIONS
Linux: Kubuntu 19.10 x86_64
KDE Plasma Version: 5.16.5
KDE Frameworks Version: 5.62.0
Qt Version: 5.12.4

ADDITIONAL INFORMATION:

The current directory is updated if while typing the new path the user selects
one of the suggested auto-completion options and presses Enter. However, that
does not solve the problem because auto-completion does not appear in all cases
(e.g. not when you paste the path from clipboard or when you switch to another
window temporarily). Also, the user is reluctant to press Enter in a dialog as,
depending on the current focus, pressing Enter could immediately confirm the
whole file open/save operation.

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

[krita] [Bug 392508] color selector doesn't play nice with cmyk

2020-02-17 Thread L. E. Segovia
https://bugs.kde.org/show_bug.cgi?id=392508

L. E. Segovia  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|REOPENED|RESOLVED
 CC||a...@amyspark.me

--- Comment #18 from L. E. Segovia  ---
I tried to reproduce this with dffa076018d6bf98ec0e3d7c232dc2825fd47c11
(dac91dfbe735e35af2f7ce1fef930960915c6148 in the krita/4.2 branch), and also
pre-SoK with b8d34f4653974df50a6ecf7915f2cea5947a2259 unsuccessfully. The color
picker stays stable.

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

[kdeconnect] [Bug 417554] Like and Reply buttons switched for Facebook Messenger

2020-02-17 Thread Simon Redman
https://bugs.kde.org/show_bug.cgi?id=417554

Simon Redman  changed:

   What|Removed |Added

   Assignee|si...@ergotech.com  |albertv...@gmail.com
  Component|messaging-application   |common

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

[kdeconnect] [Bug 417554] Like and Reply buttons switched for Facebook Messenger

2020-02-17 Thread Simon Redman
https://bugs.kde.org/show_bug.cgi?id=417554

Simon Redman  changed:

   What|Removed |Added

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

--- Comment #1 from Simon Redman  ---


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

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

[kdeconnect] [Bug 409814] Reply-to SMS box is incorrectly opened when a single-sign-on SMS with a "Copy" button is clicked

2020-02-17 Thread Simon Redman
https://bugs.kde.org/show_bug.cgi?id=409814

Simon Redman  changed:

   What|Removed |Added

 CC||kyrawer...@gmail.com

--- Comment #3 from Simon Redman  ---
*** Bug 417554 has been marked as a duplicate of this bug. ***

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

[kdeconnect] [Bug 417198] KDEConnect SMS app is difficult to read with a Dark theme

2020-02-17 Thread Simon Redman
https://bugs.kde.org/show_bug.cgi?id=417198

--- Comment #6 from Simon Redman  ---
I don't know much about theming. My experience from other people has lead me to
the same conclusion as you have come to: That there is something strange with
the way Kirigami's theme and the Qt theme interact.

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

[klipper] [Bug 417590] you need to double click copy to clipboard in English to copy them

2020-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=417590

--- Comment #16 from jkhsjd...@totally.rip ---
(In reply to Michał Dybczak from comment #15)
> You are right. When I switched clipboard history to 1 and unchecked most of
> the settings (I'm unable to find 'Prevent empty clipboard', the translation
> probably is wrong) then the first click on 'Copy to clipboard in English'
> isn't working. Second one works, just like the bug described.
> 
> So now I can confirm, with certain settings' combination this bug does occur.

Thanks for confirming!
'Prevent empty clipboard' is the second option from the top under 'General
Configuration' btw.
See this screenshot: https://screens.totally.rip/2020/02/5e4b2b07156e0.png

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

[kalarm] [Bug 417733] Sound doesn't work in KAlarm

2020-02-17 Thread David Jarvie
https://bugs.kde.org/show_bug.cgi?id=417733

--- Comment #3 from David Jarvie  ---
Thanks for that information.

Note that package dependencies are the responsibility of distributions, so you
should report any missing dependent packages to Kubuntu.

The issue about the time column not being wide enough to display the whole time
has been fixed in KAlarm version 2.12.0 (KDE Applications 18.08).

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

[neon] [Bug 417791] Snap package of cantor doesn't work on RHEL 7

2020-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=417791

--- Comment #10 from scx.m...@gmail.com ---
(In reply to scx.mail from comment #7)
> Is it possible that the kde-frameworks-5-core18:kde-frameworks-5-core18-slot
> slot is not mounted because it is not compatible with the system?

Actually, it may be mounted and incompatible libs will be still invisible - as
if they didn't exist at all.
https://github.com/flathub/flathub/issues/805#issue-397165614
https://bugs.kde.org/show_bug.cgi?id=403042#c0

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

[systemsettings] [Bug 417802] "System Settings" crashed when I clicked on the "Close" button.

2020-02-17 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=417802

--- Comment #3 from David Edmundson  ---
==18016== Invalid read of size 8
==18016==at 0x798B9F3: load (atomic_base.h:740)
==18016==by 0x798B9F3:
std::atomic::load(std::memory_order) const
(atomic:519)
==18016==by 0x7989BDB: QObjectPrivate::ConnectionData*
QAtomicOps::loadRelaxed(std::atomic
const&) (qatomic_cxx11.h:239)
==18016==by 0x7986D0D:
QBasicAtomicPointer::loadRelaxed() const
(qbasicatomic.h:248)
==18016==by 0x797B8F9: QObject::~QObject() (qobject.cpp:1030)
==18016==by 0x797BE17: QObject::~QObject() (qobject.cpp:1119)
==18016==by 0x123BD7CD: void qDeleteAll::const_iterator>(QHash::const_iterator, QHash::const_iterator) (qalgorithms.h:320)
==18016==by 0x123BD712: void qDeleteAll >(QHash const&)
(qalgorithms.h:328)
==18016==by 0x123BB255: ItemsModel::Private::~Private()
(src/frameworks/knewstuff/src/qtquick/quickitemsmodel.cpp:46)
==18016==by 0x123B828E: ItemsModel::~ItemsModel()
(src/frameworks/knewstuff/src/qtquick/quickitemsmodel.cpp:99)
==18016==by 0x123B1C8A:
QQmlPrivate::QQmlElement::~QQmlElement() (qqmlprivate.h:111)
==18016==by 0x123B1CBB:
QQmlPrivate::QQmlElement::~QQmlElement() (qqmlprivate.h:109)
==18016==by 0x797D950: QObjectPrivate::deleteChildren() (qobject.cpp:2123)
==18016==  Address 0x2194a930 is 64 bytes inside a block of size 136 free'd
==18016==at 0x483A08B: operator delete(void*, unsigned long)
(vg_replace_malloc.c:595)
==18016==by 0x78C6496:
QAbstractItemModelPrivate::~QAbstractItemModelPrivate()
(qabstractitemmodel.cpp:507)
==18016==by 0x798A001:
QScopedPointerDeleter::cleanup(QObjectData*) (qscopedpointer.h:60)
==18016==by 0x7987180: QScopedPointer >::~QScopedPointer() (qscopedpointer.h:107)
==18016==by 0x797BDDE: QObject::~QObject() (qobject.cpp:997)
==18016==by 0x78C9023: QAbstractItemModel::~QAbstractItemModel()
(qabstractitemmodel.cpp:1541)
==18016==by 0x78CD84F: QAbstractListModel::~QAbstractListModel()
(qabstractitemmodel.cpp:3734)
==18016==by 0x12414AA6: KNSCore::CommentsModel::~CommentsModel()
(src/frameworks/knewstuff/src/core/commentsmodel.cpp:116)
==18016==by 0x12414ACB: KNSCore::CommentsModel::~CommentsModel()
(src/frameworks/knewstuff/src/core/commentsmodel.cpp:114)
==18016==by 0x797D950: QObjectPrivate::deleteChildren() (qobject.cpp:2123)
==18016==by 0x797BD65: QObject::~QObject() (qobject.cpp:1107)
==18016==by 0x12424AC8: KNSCore::Engine::~Engine()
(src/frameworks/knewstuff/src/core/engine.cpp:103)
==18016==  Block was alloc'd at
==18016==at 0x4838DEF: operator new(unsigned long)
(vg_replace_malloc.c:344)
==18016==by 0x78C8F4C: QAbstractItemModel::QAbstractItemModel(QObject*)
(qabstractitemmodel.cpp:1526)
==18016==by 0x78CD7D0: QAbstractListModel::QAbstractListModel(QObject*)
(qabstractitemmodel.cpp:3713)
==18016==by 0x124149F9:
KNSCore::CommentsModel::CommentsModel(KNSCore::Engine*)
(src/frameworks/knewstuff/src/core/commentsmodel.cpp:107)
==18016==by 0x1242B8BF:
KNSCore::Engine::commentsForEntry(KNSCore::EntryInternal const&)
(src/frameworks/knewstuff/src/core/engine.cpp:824)
==18016==by 0x123B9C7B: ItemsModel::data(QModelIndex const&, int) const
(src/frameworks/knewstuff/src/qtquick/quickitemsmodel.cpp:337)
==18016==by 0x123CBBF9:
KNewStuffQuick::CommentsModel::Private::resetConnections()
(src/frameworks/knewstuff/src/qtquick/commentsmodel.cpp:48)
==18016==by 0x123CB7C0: KNewStuffQuick::CommentsModel::componentComplete()
(src/frameworks/knewstuff/src/qtquick/commentsmodel.cpp:89)
==18016==by 0x56FC778:
QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&)
(qqmlobjectcreator.cpp:1410)
==18016==by 0x566E8EE: QQmlComponentPrivate::complete(QQmlEnginePrivate*,
QQmlComponentPrivate::ConstructionState*) (qqmlcomponent.cpp:969)
==18016==by 0x566EA08: QQmlComponentPrivate::completeCreate()
(qqmlcomponent.cpp:1005)
==18016==by 0x566FA7B: QQmlComponent::createObject(QQmlV4Function*)
(qqmlcomponent.cpp:1377)
==18016== 
==18016== Invalid write of size 8
==18016==at 0x798BB73: store (atomic_base.h:718)
==18016==by 0x798BB73:
std::atomic::store(QObjectPrivate::ConnectionData*,
std::memory_order) (atomic:510)
==18016==by 0x7989CDE: void
QAtomicOps::storeRelaxed(std::atomic&,
QObjectPrivate::ConnectionData*) (qatomic_cxx11.h:269)
==18016==by 0x7986ED0:
QBasicAtomicPointer::storeRelaxed(QObjectPrivate::ConnectionData*)
(qbasicatomic.h:249)
==18016==by 0x797BD3C: QObject::~QObject() (qobject.cpp:1104)
==18016==by 0x797BE17: QObject::~QObject() (qobject.cpp:1119)
==18016==by 0x123BD7CD: void qDeleteAll::const_iterator>(QHash::const_iterator, QHash::const_iterator) (qalgorithms.h:320)
==18016==by 0x123BD712: void qDeleteAll >(QHash const&)
(qalgorithms.h:328)
==18016==by 0x123BB255: ItemsModel::Private::~Private()
(src/frameworks/knewstuff/src/qtquick/quickitemsmodel.cpp:46)
==18016==by 0x123B828E: ItemsModel::~ItemsModel()

[neon] [Bug 417791] Snap package of cantor doesn't work on RHEL 7

2020-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=417791

--- Comment #9 from scx.m...@gmail.com ---
I can confirm that the following snaps are affected:
- kde-frameworks-5-core18
- kde-frameworks-5-core18-sdk
- kde-frameworks-5-qt-5-14-core18
- kde-frameworks-5-qt-5-14-core18-sdk

$ find -L /var/lib/snapd/snap/kde-frameworks-5*/*/usr/lib/*-linux-gnu -type f
-iname 'libQt5Core.so*' -print0 2>/dev/null | xargs -0 -I{} file '{}' | grep -Z
'ELF' | grep -Z 'for GNU/Linux ' | sort -z -fuV | grep -Z -Eva 'for GNU/Linux
(2\.6\.[0-9]+|3\.2\.0)'
/var/lib/snapd/snap/kde-frameworks-5-core18/30/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.12.3:
ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked
(uses shared libs), BuildID[sha1]=252fcd9f736251377f96e559b953f9cb4b8fbdec, for
GNU/Linux 3.17.0, stripped
/var/lib/snapd/snap/kde-frameworks-5-core18/32/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.12.3:
ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked
(uses shared libs), BuildID[sha1]=2742584b062a7248211733fb8a9365897d2db95a, for
GNU/Linux 3.17.0, stripped
/var/lib/snapd/snap/kde-frameworks-5-core18/current/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.12.3:
ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked
(uses shared libs), BuildID[sha1]=2742584b062a7248211733fb8a9365897d2db95a, for
GNU/Linux 3.17.0, stripped
/var/lib/snapd/snap/kde-frameworks-5-core18-sdk/31/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.12.3:
ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked
(uses shared libs), BuildID[sha1]=2742584b062a7248211733fb8a9365897d2db95a, for
GNU/Linux 3.17.0, stripped
/var/lib/snapd/snap/kde-frameworks-5-core18-sdk/current/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.12.3:
ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked
(uses shared libs), BuildID[sha1]=2742584b062a7248211733fb8a9365897d2db95a, for
GNU/Linux 3.17.0, stripped
/var/lib/snapd/snap/kde-frameworks-5-qt-5-14-core18/1/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.14.1:
ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked
(uses shared libs), BuildID[sha1]=71f6b46001655493cfef4fabf3a1afdea055f0af, for
GNU/Linux 3.17.0, stripped
/var/lib/snapd/snap/kde-frameworks-5-qt-5-14-core18/current/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.14.1:
ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked
(uses shared libs), BuildID[sha1]=71f6b46001655493cfef4fabf3a1afdea055f0af, for
GNU/Linux 3.17.0, stripped
/var/lib/snapd/snap/kde-frameworks-5-qt-5-14-core18-sdk/1/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.14.1:
ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked
(uses shared libs), BuildID[sha1]=71f6b46001655493cfef4fabf3a1afdea055f0af, for
GNU/Linux 3.17.0, stripped
/var/lib/snapd/snap/kde-frameworks-5-qt-5-14-core18-sdk/current/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.14.1:
ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked
(uses shared libs), BuildID[sha1]=71f6b46001655493cfef4fabf3a1afdea055f0af, for
GNU/Linux 3.17.0, stripped

However, kde-frameworks-5 is not affected.

$ find -L /var/lib/snapd/snap/kde-frameworks-5*/*/usr/lib/*-linux-gnu -type f
-iname 'libQt5Core.so*' -print0 2>/dev/null | xargs -0 -I{} file '{}' | grep -Z
'ELF' | grep -Z 'for GNU/Linux ' | sort -z -fuV | grep -Z -Ea 'for GNU/Linux
(2\.6\.[0-9]+|3\.2\.0)'
/var/lib/snapd/snap/kde-frameworks-5/27/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.11.0:
ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked
(uses shared libs), BuildID[sha1]=5e10a9ca057fb0497637959a6df4d07bfd8e9173, for
GNU/Linux 2.6.28, stripped
/var/lib/snapd/snap/kde-frameworks-5/current/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.11.0:
ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked
(uses shared libs), BuildID[sha1]=5e10a9ca057fb0497637959a6df4d07bfd8e9173, for
GNU/Linux 2.6.28, stripped

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

[systemsettings] [Bug 417802] "System Settings" crashed when I clicked on the "Close" button.

2020-02-17 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=417802

David Edmundson  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #2 from David Edmundson  ---
Edit, managed.

Open get new icons -> select -> comments -> close systemsettings

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

[systemsettings] [Bug 417802] "System Settings" crashed when I clicked on the "Close" button.

2020-02-17 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=417802

David Edmundson  changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk

--- Comment #1 from David Edmundson  ---
Can you reproduce it?

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

[krita] [Bug 414576] Zoom failure in 4.2.8 but not in 4.2.7.

2020-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=414576

--- Comment #23 from lemp...@gmail.com ---
(In reply to RamonMiranda from comment #22)
> I have been testing this and i have uploaded a video. Maybe helps maybe not. 
> https://drive.google.com/file/d/1hx8kwHQKX_0qYFXD55Sq-LXt6kB9hvSY/
> view?usp=sharing
> 
> 
> If you need more testing let me know please

So I gave it one more try to check in comparison to your video and I found the
difference.

It's in tablet drivers inside Krita, if I switch to win ink then everything is
smooth and works fine the problem is that pen pressure doesn't work for me like
that, if I turn win ink in my pen displays application then the lag is so
visible that I can barely zoom at any level, if I turn on win tab (which I
usually have, while having win ink off in drivers) then I'm at the situation
when it's a little bit choppy and freezes completely for several seconds at
about 10-5% zoom (if zoomed out quickly, Krita shows the zoom bar changing like
it's processing something for long until it changes zoom levels at these levels
of zoom).

I checked the same settings in the previous version 4.2.7 and everything is
perfectly smooth so I don't think my pen tablet's drivers are the cause here
but something has changed in Krita or is it possible for being it my drivers
although they are fine in all previous versions in the past 2.5 years (same
machine)?

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

[ark] [Bug 417805] New: ark crashed on closing child window

2020-02-17 Thread J Wiggins
https://bugs.kde.org/show_bug.cgi?id=417805

Bug ID: 417805
   Summary: ark crashed on closing child window
   Product: ark
   Version: 18.12.3
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: elvis.angelac...@kde.org
  Reporter: j.wiggin...@yahoo.com
CC: rthoms...@gmail.com
  Target Milestone: ---

Application: ark (18.12.3)

Qt Version: 5.9.7
Frameworks Version: 5.55.0
Operating System: Linux 4.12.14-lp151.28.36-default x86_64
Distribution: "openSUSE Leap 15.1"

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

Opened pptx to play media, crashed 3 times  when I closed child window, almost
but not everytime.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Ark (ark), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f05be861d80 (LWP 9959))]

Thread 3 (Thread 0x7f05a0afe700 (LWP 9963)):
#0  0x7f05b6c688ad in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f05a17a49ab in  () at /usr/lib64/dri/i965_dri.so
#2  0x7f05a17a46b7 in  () at /usr/lib64/dri/i965_dri.so
#3  0x7f05b6c62569 in start_thread () at /lib64/libpthread.so.0
#4  0x7f05ba91a9ef in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f05a3bb6700 (LWP 9961)):
#0  0x7f05ba91019b in poll () at /lib64/libc.so.6
#1  0x7f05b4ec91a9 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f05b4ec92bc in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f05bb2557fb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f05bb1fa79a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f05bb018d4a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f05b8b399e5 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x7f05bb01dc8d in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f05b6c62569 in start_thread () at /lib64/libpthread.so.0
#9  0x7f05ba91a9ef in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f05be861d80 (LWP 9959)):
[KCrash Handler]
#6  0x7f05bb140e0b in QUrl::QUrl(QUrl const&) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f058bba8880 in Phonon::MediaSource::url() const () at
/usr/lib64/libphonon4qt5.so.4
#8  0x7f058bdee86d in  () at /usr/lib64/qt5/plugins/dragonpart.so
#9  0x7f058bdef4e3 in  () at /usr/lib64/qt5/plugins/dragonpart.so
#10 0x7f058bdf4742 in  () at /usr/lib64/qt5/plugins/dragonpart.so
#11 0x7f058bdf5904 in  () at /usr/lib64/qt5/plugins/dragonpart.so
#12 0x7f058bdf775b in  () at /usr/lib64/qt5/plugins/dragonpart.so
#13 0x7f0599bdf930 in  () at /usr/lib64/qt5/plugins/arkpart.so
#14 0x7f0599bdf9f9 in  () at /usr/lib64/qt5/plugins/arkpart.so
#15 0x7f05bb22bf50 in QObject::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5
#16 0x7f05bbfe429b in QWidget::event(QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#17 0x7f05bc0f756b in QMainWindow::event(QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#18 0x7f05bd6289a1 in KMainWindow::event(QEvent*) () at
/usr/lib64/libKF5XmlGui.so.5
#19 0x7f05bd66e4c5 in KXmlGuiWindow::event(QEvent*) () at
/usr/lib64/libKF5XmlGui.so.5
#20 0x7f05bbfa53dc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#21 0x7f05bbfacca4 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#22 0x7f05bb1fc768 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#23 0x7f05bb1feedd in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib64/libQt5Core.so.5
#24 0x7f05bb2561b3 in  () at /usr/lib64/libQt5Core.so.5
#25 0x7f05b4ec8e87 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#26 0x7f05b4ec9230 in  () at /usr/lib64/libglib-2.0.so.0
#27 0x7f05b4ec92bc in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#28 0x7f05bb2557df in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#29 0x7f05bb1fa79a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#30 0x7f05bb203844 in QCoreApplication::exec() () at
/usr/lib64/libQt5Core.so.5
#31 0x56370171f984 in  ()
#32 0x7f05ba842f8a in __libc_start_main () at /lib64/libc.so.6
#33 0x563701720a2a in _start ()
[Inferior 1 (process 9959) detached]

Reported using DrKonqi

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

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

2020-02-17 Thread aaron
https://bugs.kde.org/show_bug.cgi?id=401677

aaron  changed:

   What|Removed |Added

 CC||skarlup...@gmail.com
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #39 from aaron  ---
Samsung Galexy S9
Android 10
Samsung Messages 11.0.00.291
KDEConnect Android App 1.13.7

Gnome Version: 3.34.2
DISTRIB_ID=ManjaroLinux
DISTRIB_RELEASE=19.0.0
DISTRIB_CODENAME=Kyria
DISTRIB_DESCRIPTION="Manjaro Linux"

GSConnect 31
Legacy Message Support = Disabled


I am able to view and send text messages from messaging menu.  I can see full
chat history and contacts. I can respond to messages and view conversation
scroll-back. 

Previously I could only see or reply to a sms message via the notification
pop-up.

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

[kamoso] [Bug 417804] New: Kamoso segfault on startup

2020-02-17 Thread Zack Emmert
https://bugs.kde.org/show_bug.cgi?id=417804

Bug ID: 417804
   Summary: Kamoso segfault on startup
   Product: kamoso
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: aleix...@kde.org
  Reporter: zemm...@librem.one
  Target Milestone: ---

Application: kamoso (3.2.3)

Qt Version: 5.13.2
Frameworks Version: 5.66.0
Operating System: Linux 5.4.12-200.fc31.x86_64 x86_64
Distribution: "Fedora release 31 (Thirty One)"

-- Information about the crash:
- What I was doing when the application crashed:
Attempting to open it. Application showed UI elements and a black rectangle in
place of the camera view, then crashed.

The crash can be reproduced every time.

-- Backtrace:
Application: Kamoso (kamoso), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fce3ae1f580 (LWP 31371))]

Thread 24 (Thread 0x7fcde37fe700 (LWP 31396)):
[KCrash Handler]
#6  0x7fce25dde377 in convert_ubyte () from /usr/lib64/dri/i965_dri.so
#7  0x7fce25dfdace in _mesa_format_convert () from
/usr/lib64/dri/i965_dri.so
#8  0x7fce25c6fdf8 in _mesa_texstore () from /usr/lib64/dri/i965_dri.so
#9  0x7fce25c7086c in store_texsubimage () from /usr/lib64/dri/i965_dri.so
#10 0x7fce25b39e77 in intel_upload_tex () from /usr/lib64/dri/i965_dri.so
#11 0x7fce25b3a55e in intelTexImage () from /usr/lib64/dri/i965_dri.so
#12 0x7fce25c589cc in teximage_err () from /usr/lib64/dri/i965_dri.so
#13 0x7fce25c5a7b2 in _mesa_TexImage2D () from /usr/lib64/dri/i965_dri.so
#14 0x7fce1870c94b in VideoMaterial::bindTexture(int, unsigned char const*)
() from /usr/lib64/gstreamer-1.0/gstkamosoqt5videosink.so
#15 0x7fce1870ca67 in VideoMaterial::bind() () from
/usr/lib64/gstreamer-1.0/gstkamosoqt5videosink.so
#16 0x7fce1870d055 in
VideoMaterialShader::updateState(QSGMaterialShader::RenderState const&,
QSGMaterial*, QSGMaterial*) () from
/usr/lib64/gstreamer-1.0/gstkamosoqt5videosink.so
#17 0x7fce40a803c6 in
QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*)
() from /lib64/libQt5Quick.so.5
#18 0x7fce40a81df5 in QSGBatchRenderer::Renderer::renderBatches() () from
/lib64/libQt5Quick.so.5
#19 0x7fce40a88242 in QSGBatchRenderer::Renderer::render() () from
/lib64/libQt5Quick.so.5
#20 0x7fce40a74d24 in QSGRenderer::renderScene(QSGBindable const&) () from
/lib64/libQt5Quick.so.5
#21 0x7fce40a751d3 in QSGRenderer::renderScene(unsigned int) () from
/lib64/libQt5Quick.so.5
#22 0x7fce40ab7212 in
QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () from
/lib64/libQt5Quick.so.5
#23 0x7fce40b1cadc in QQuickWindowPrivate::renderSceneGraph(QSize const&)
() from /lib64/libQt5Quick.so.5
#24 0x7fce40ac294f in QSGRenderThread::syncAndRender() () from
/lib64/libQt5Quick.so.5
#25 0x7fce40ac66f8 in QSGRenderThread::run() () from
/lib64/libQt5Quick.so.5
#26 0x7fce3eadad96 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#27 0x7fce3de014e2 in start_thread () from /lib64/libpthread.so.0
#28 0x7fce3e73c6d3 in clone () from /lib64/libc.so.6

Thread 23 (Thread 0x7fcde8ff9700 (LWP 31394)):
#0  0x7fce3e7371ed in syscall () from /lib64/libc.so.6
#1  0x7fce40624b93 in g_cond_wait () from /lib64/libglib-2.0.so.0
#2  0x7fce40761287 in gst_task_func () from /lib64/libgstreamer-1.0.so.0
#3  0x7fce40602704 in g_thread_pool_thread_proxy () from
/lib64/libglib-2.0.so.0
#4  0x7fce40601fc2 in g_thread_proxy () from /lib64/libglib-2.0.so.0
#5  0x7fce3de014e2 in start_thread () from /lib64/libpthread.so.0
#6  0x7fce3e73c6d3 in clone () from /lib64/libc.so.6

Thread 22 (Thread 0x7fcde97fa700 (LWP 31393)):
#0  0x7fce3e7371ed in syscall () from /lib64/libc.so.6
#1  0x7fce40624b93 in g_cond_wait () from /lib64/libglib-2.0.so.0
#2  0x7fce18166547 in gst_app_src_create () from /lib64/libgstapp-1.0.so.0
#3  0x7fce1b3be47d in gst_base_src_get_range () from
/lib64/libgstbase-1.0.so.0
#4  0x7fce1b3c155c in gst_base_src_loop () from /lib64/libgstbase-1.0.so.0
#5  0x7fce40761087 in gst_task_func () from /lib64/libgstreamer-1.0.so.0
#6  0x7fce40602704 in g_thread_pool_thread_proxy () from
/lib64/libglib-2.0.so.0
#7  0x7fce40601fc2 in g_thread_proxy () from /lib64/libglib-2.0.so.0
#8  0x7fce3de014e2 in start_thread () from /lib64/libpthread.so.0
#9  0x7fce3e73c6d3 in clone () from /lib64/libc.so.6

Thread 21 (Thread 0x7fcde9ffb700 (LWP 31392)):
#0  0x7fce3e7371ed in syscall () from /lib64/libc.so.6
#1  0x7fce40624b93 in g_cond_wait () from /lib64/libglib-2.0.so.0
#2  0x7fce18695ef6 in gst_queue_loop () from
/usr/lib64/gstreamer-1.0/libgstcoreelements.so
#3  0x7fce40761087 in gst_task_func () from 

[plasmashell] [Bug 417803] New: Clock needs more margin to the right

2020-02-17 Thread Potomac
https://bugs.kde.org/show_bug.cgi?id=417803

Bug ID: 417803
   Summary: Clock needs more margin to the right
   Product: plasmashell
   Version: 5.18.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Digital Clock
  Assignee: plasma-b...@kde.org
  Reporter: mister.free...@laposte.net
  Target Milestone: 1.0

Created attachment 126109
  --> https://bugs.kde.org/attachment.cgi?id=126109=edit
lack of right margin for the digital clock

SUMMARY
Since plasma 5.18 I notice that the clock doesn't have a right margin, it's too
close the screen border, and the setup icon (which was present to the right of
the clock on the previous versions of plasma) has disapeared.

This lack of right margin for the clock gives a weird look on the task bar,
when we looking at the clock, (see the attached file).

please add a slight right margin to the clock,or give the user the ability of
setting a right margin to the clock.

STEPS TO REPRODUCE
1. Update to the 5.18 version of plasma
2. After reconnection you will notice that the clock is too close to the screen
border (no right margin)



SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: archlinux, plasma 5.18
(available in About System)
KDE Plasma Version: 5.18
KDE Frameworks Version: 5.67.0
Qt Version:

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

[kompare] [Bug 417156] Compare button remains grayed out

2020-02-17 Thread Kevin Kofler
https://bugs.kde.org/show_bug.cgi?id=417156

Kevin Kofler  changed:

   What|Removed |Added

 CC|kevin.kof...@chello.at  |

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

[kompare] [Bug 417156] Compare button remains grayed out

2020-02-17 Thread Kevin Kofler
https://bugs.kde.org/show_bug.cgi?id=417156

Kevin Kofler  changed:

   What|Removed |Added

 CC||kevin.kof...@chello.at
 Status|REOPENED|RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #6 from Kevin Kofler  ---
Please stop reopening this bug. There is clearly nothing to fix in upstream
Kompare anymore, and this bug is definitely a duplicate.

You have not specified the distribution you are using, but since you mentioned
"dnf", I guess you are using Fedora. We have Kompare 19.12.2 in Rawhide now. No
updates for Fedora 30 and 31 have been issued so far though. I can check with
Rex Dieter what the plan for the KDE Release Service applications is there, and
I can possibly issue an update of Kompare specifically, or an update
backporting the fix. (If, on the other hand, you are still using Fedora 29 or
older, then your release is no longer supported and will not be updated.)

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

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

[kompare] [Bug 390024] "Compare" button not enabled on the initial dialog even after filling the file names

2020-02-17 Thread Kevin Kofler
https://bugs.kde.org/show_bug.cgi?id=390024

--- Comment #22 from Kevin Kofler  ---
*** Bug 417156 has been marked as a duplicate of this bug. ***

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

[kompare] [Bug 417156] Compare button remains grayed out

2020-02-17 Thread Mike
https://bugs.kde.org/show_bug.cgi?id=417156

Mike  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|DUPLICATE   |---

--- Comment #5 from Mike  ---
>>It's fixed in 19.08.

How does one get the 19.08?  dnf update kompare finds nothing

>> Btw, if you type anything into the text fields, the Compare button should 
>> get enabled, so that could be used as a workaround.

What "text" field?  Source and Destination? The ones where you choose the
files? That doesn't do anything.

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

[systemsettings] [Bug 417802] New: "System Settings" crashed when I clicked on the "Close" button.

2020-02-17 Thread Thomas Cicciu
https://bugs.kde.org/show_bug.cgi?id=417802

Bug ID: 417802
   Summary: "System Settings" crashed when I clicked on the
"Close" button.
   Product: systemsettings
   Version: 5.18.0
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: thomas.cic...@outlook.fr
  Target Milestone: ---

Application: systemsettings5 (5.18.0)

Qt Version: 5.13.2
Frameworks Version: 5.67.0
Operating System: Linux 5.3.0-40-generic x86_64
Windowing system: X11
Distribution: KDE neon User Edition 5.18

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

I just clicked on the "Close" button because I was done. I had just changed the
theme of the icons.

-- Backtrace:
Application: Configuration du système (systemsettings5), signal: Segmentation
fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f514678f800 (LWP 4063))]

Thread 12 (Thread 0x7f50f98bc700 (LWP 4128)):
#0  0x7f5141cd80b4 in __GI___libc_read (fd=38, buf=0x7f50f98bbb20,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27
#1  0x7f513b3d02d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f513b38b0b7 in g_main_context_check () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f513b38b570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f513b38b6dc in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f514262facb in QEventDispatcherGlib::processEvents
(this=0x7f50e4004b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7f51425cff9a in QEventLoop::exec (this=this@entry=0x7f50f98bbd30,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#7  0x7f51423eb3aa in QThread::exec (this=this@entry=0x55825411dae0) at
thread/qthread.cpp:531
#8  0x7f5140442ac6 in QQuickPixmapReader::run (this=0x55825411dae0) at
util/qquickpixmapcache.cpp:962
#9  0x7f51423ecb52 in QThreadPrivate::start (arg=0x55825411dae0) at
thread/qthread_unix.cpp:360
#10 0x7f513d74a6db in start_thread (arg=0x7f50f98bc700) at
pthread_create.c:463
#11 0x7f5141ce988f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 11 (Thread 0x7f50fadfe700 (LWP 4127)):
#0  0x7f513d7509f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x558253af9b24) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x558253af9ad0,
cond=0x558253af9af8) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x558253af9af8, mutex=0x558253af9ad0) at
pthread_cond_wait.c:655
#3  0x7f51423f3aeb in QWaitConditionPrivate::wait (deadline=...,
this=0x558253af9ad0) at thread/qwaitcondition_unix.cpp:146
#4  QWaitCondition::wait (this=, mutex=0x5582536e1dd0,
deadline=...) at thread/qwaitcondition_unix.cpp:225
#5  0x7f51423f3df9 in QWaitCondition::wait (this=this@entry=0x5582536e1dd8,
mutex=mutex@entry=0x5582536e1dd0, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:208
#6  0x7f51404c8ec8 in QSGRenderThreadEventQueue::takeEvent (wait=true,
this=0x5582536e1dc8) at scenegraph/qsgthreadedrenderloop.cpp:245
#7  QSGRenderThread::processEventsAndWaitForMore
(this=this@entry=0x5582536e1d50) at scenegraph/qsgthreadedrenderloop.cpp:710
#8  0x7f51404c92fa in QSGRenderThread::run (this=0x5582536e1d50) at
scenegraph/qsgthreadedrenderloop.cpp:739
#9  0x7f51423ecb52 in QThreadPrivate::start (arg=0x5582536e1d50) at
thread/qthread_unix.cpp:360
#10 0x7f513d74a6db in start_thread (arg=0x7f50fadfe700) at
pthread_create.c:463
#11 0x7f5141ce988f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 10 (Thread 0x7f50eb7fe700 (LWP 4123)):
#0  0x7f5141cd80b4 in __GI___libc_read (fd=27, buf=0x7f50eb7fdb70,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27
#1  0x7f513b3d02d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f513b38b0b7 in g_main_context_check () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f513b38b570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f513b38b6dc in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f514262facb in QEventDispatcherGlib::processEvents
(this=0x7f50d80954d0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7f51425cff9a in QEventLoop::exec (this=this@entry=0x7f50eb7fdd80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#7  0x7f51423eb3aa in QThread::exec (this=this@entry=0x55825093e180) at
thread/qthread.cpp:531
#8  0x7f513ff70815 in QQmlThreadPrivate::run (this=0x55825093e180) at
qml/ftw/qqmlthread.cpp:152
#9  0x7f51423ecb52 in QThreadPrivate::start (arg=0x55825093e180) at
thread/qthread_unix.cpp:360
#10 

[kompare] [Bug 417156] Compare button remains grayed out

2020-02-17 Thread Wolfgang Bauer
https://bugs.kde.org/show_bug.cgi?id=417156

--- Comment #4 from Wolfgang Bauer  ---
Btw, if you type anything into the text fields, the Compare button should get
enabled, so that could be used as a workaround.

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

[kompare] [Bug 390024] "Compare" button not enabled on the initial dialog even after filling the file names

2020-02-17 Thread Wolfgang Bauer
https://bugs.kde.org/show_bug.cgi?id=390024

--- Comment #21 from Wolfgang Bauer  ---
*** Bug 417156 has been marked as a duplicate of this bug. ***

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

[kompare] [Bug 417156] Compare button remains grayed out

2020-02-17 Thread Wolfgang Bauer
https://bugs.kde.org/show_bug.cgi?id=417156

Wolfgang Bauer  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|REOPENED|RESOLVED

--- Comment #3 from Wolfgang Bauer  ---
(In reply to Mike from comment #2)
> So... I ran sudo dnf install kompare just now, then ran dnf info kompare and
> it says kompare 19.04.3
It's fixed in 19.08.

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

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

[krita] [Bug 417040] No pressure at first stamp in floating dock mode

2020-02-17 Thread Igor
https://bugs.kde.org/show_bug.cgi?id=417040

--- Comment #6 from Igor  ---
(In reply to Boudewijn Rempt from comment #5)
> I'm sorry, but those links are broken :-(

Hmm, log is opened without problem, only image has a problem. I reuploaded
files to "yandex" https://yadi.sk/d/N0Nvg1auErvLgg

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

[digikam] [Bug 417797] Batch video timestamp changing fails

2020-02-17 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=417797

Maik Qualmann  changed:

   What|Removed |Added

Summary|Batch timestamp changing|Batch video timestamp
   |fails   |changing fails

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

[kinfocenter] [Bug 417798] Info Center crashed in findNICs()

2020-02-17 Thread Harald Sitter
https://bugs.kde.org/show_bug.cgi?id=417798

--- Comment #1 from Harald Sitter  ---
What's the output of `ip a` on your system?

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

[digikam] [Bug 318516] SCAN : Improve digiKam loading time [patch]

2020-02-17 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=318516

Maik Qualmann  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 CC||metzping...@gmail.com
   Version Fixed In||7.0.0
 Resolution|--- |FIXED

--- Comment #14 from Maik Qualmann  ---
I have ported and tested the patches to git/master. However, we now use a
delayed timer that gives even better results. I now close the bug report.

Maik

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

[systemsettings] [Bug 417515] In Application Style current style is not highlighted (no global theme)

2020-02-17 Thread Piotr Mierzwinski
https://bugs.kde.org/show_bug.cgi?id=417515

--- Comment #5 from Piotr Mierzwinski  ---
Created attachment 126108
  --> https://bugs.kde.org/attachment.cgi?id=126108=edit
my kdeglobals in Plasma 5.18.0

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

[plasmashell] [Bug 382760] Let users specify individual KRunner plugins from the full set

2020-02-17 Thread Jay Armstrong
https://bugs.kde.org/show_bug.cgi?id=382760

Jay Armstrong  changed:

   What|Removed |Added

 CC||j...@jayarmstrong.com

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

  1   2   3   4   >