[krita] [Bug 456194] New: Align with Layer checkbox in Gradient Overlay deactivates itself when Layer Style is accessed again

2022-07-01 Thread varkatope
https://bugs.kde.org/show_bug.cgi?id=456194

Bug ID: 456194
   Summary: Align with Layer checkbox in Gradient Overlay
deactivates itself when Layer Style is accessed again
   Product: krita
   Version: 5.0.6
  Platform: Other
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Filter Layers
  Assignee: krita-bugs-n...@kde.org
  Reporter: chirn...@hotmail.com
  Target Milestone: ---

Created attachment 150312
  --> https://bugs.kde.org/attachment.cgi?id=150312&action=edit
Minimum reproduction .kra with one broken layer and one working layer

SUMMARY

Align with Layer checkbox in Gradient Overlay layer style unchecks itself and
deactivates the option when Layer Styles is accessed again, and SOMETIMES (I
know programmers love this word), this leads to the checkbox not being
checkable again.


STEPS TO REPRODUCE
1. Create new project and add either a paint or vector layer.
2. Draw a shape.
3. Add a layer style to this layer and check Gradient overlay. Make sure a
gradient is visible on the shape by adjusting scale and opacity.
4. Check Align with Layer and hit OK.
5. Move the shape around with the Move tool. The gradient should follow the
shape.
6. Access the Layer Style properties again and go to Gradient Overlay (it would
also be nice if the window opened back up on the last style you had open, by
the way).

OBSERVED RESULT
Align with Layer should now be unchecked. Usually it can be checked again, but
sometimes it stops being checkable, either after loading the file again, or
just randomly after performing some other actions, not sure. In which case the
gradient is also no longer tied to the shape and moving the shape no longer
moves the layer style.

The uncheckable problem seems kind of random, but the Align with Layer
definitely deactivates itself every time.

EXPECTED RESULT

The Align with Layer checkbox should stay checked, and should also not stop
being checkable.


SOFTWARE/OS VERSIONS
Windows: 10 Home, 21H2 (up to date)

ADDITIONAL INFORMATION

Using 5.0.6 on Windows, but also tried the 5.1.0 beta also on Windows, and
5.0.8 on Manjaro Linux. 5.1.0 did fix a crash I was having with the layer
styles, but the above problem remains.

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

[plasma-pa] [Bug 456164] When adjusting the volume of kde via a bluetooth headset the volume hud does not appear.

2022-07-01 Thread ratijas
https://bugs.kde.org/show_bug.cgi?id=456164

ratijas  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #1 from ratijas  ---
Absolutely a must-have feature. I noticed the lack of HUD just yesterday too.

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

[krunner] [Bug 442987] the selected item in the search results doesn't change rapidly enough to keep up with user input

2022-07-01 Thread Alexander Popel
https://bugs.kde.org/show_bug.cgi?id=442987

Alexander Popel  changed:

   What|Removed |Added

 CC||adamantga...@gmail.com

--- Comment #13 from Alexander Popel  ---
Noticed this bug too, pretty frustrating. I have an app that has 'Chat' in its
name. I also have Telegram Desktop installed that has 'Chat' in its categories.
When I quickly type 'chat' and press Enter - Telegram opens, but if I wait just
a bit, the other chat app jumps up and Enter selects it. Also, don't remember
this happening before 5.25.

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

[okular] [Bug 388228] Okular crashes when annotating a piece of text

2022-07-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=388228

--- Comment #15 from wangxinglong...@gmail.com ---
it seems that inserting text in pdf file with okular will result in this kind
of crash if I try to type Chinese character.

If I change the input method to English mode and typing letters and words, no
crash happens at all.

By the way, my computer is running arch linux, and my input method is
sogoupinyin.

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

[kwin] [Bug 445877] Kickoff shows up in the bottom middle instead of bottom left corner (only with Wayland)

2022-07-01 Thread SigHunter
https://bugs.kde.org/show_bug.cgi?id=445877

--- Comment #6 from SigHunter  ---
for me, this problem went away after I made sure the gentoo USE flag
USE=wayland is set globally for all packages and recompiling the concerning
packages

[ebuild   R] media-libs/vulkan-loader-1.3.216  USE="wayland*" 
[ebuild   R] x11-libs/libxkbcommon-1.4.1  USE="wayland*" 
[ebuild   R] dev-qt/qtgui-5.15.5  USE="wayland*" 
[ebuild   R] x11-libs/gtk+-3.24.34  USE="wayland*" 
[ebuild   R] media-libs/libsdl2-2.0.20-r1  USE="wayland* gles2*" 
[ebuild   R] kde-frameworks/kguiaddons-5.95.0  USE="wayland*" 
[ebuild   R] x11-misc/appmenu-gtk-module-0.7.3-r2  USE="wayland*" 
[ebuild   R] media-video/mpv-0.34.1-r1  USE="wayland*" 
[ebuild   R] app-misc/fastfetch-1.5.5  USE="wayland*" 
[ebuild   R] mail-client/thunderbird-bin-91.11.0  USE="wayland*" 
[ebuild   R] www-client/firefox-bin-102.0  USE="wayland*" 
[ebuild   R] kde-frameworks/plasma-5.95.0-r4  USE="wayland*" 
[ebuild   R] kde-plasma/oxygen-5.25.2  USE="wayland*" 
[ebuild   R] media-video/vlc-3.0.17.4  USE="wayland*" 

Not sure which package of those made it go away, but now the start menu opens
on the left bottom, like it should!
(it's not my bug report, so I can't/won't close it)

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

[kmymoney] [Bug 450927] Equities with zero balance option does not work

2022-07-01 Thread Thomas Baumgart
https://bugs.kde.org/show_bug.cgi?id=450927

--- Comment #9 from Thomas Baumgart  ---
Git commit b17daebdca0c0611e1f54659ae06a5a47a60ea90 by Thomas Baumgart.
Committed on 01/07/2022 at 07:43.
Pushed by tbaumgart into branch 'master'.

Improve closing investment accounts

One needed to close all security accounts first before one could close
the parent investment account. This change improves the process so that
an investment account can be closed with all sub-ordinate security
accounts in one go if the conditions to close an account apply to all
accounts to be closed (balance equal to zero, not referenced in
schedules, ...)

M  +29   -0kmymoney/mymoney/mymoneyfile.cpp
M  +9-2kmymoney/views/kaccountsview.cpp
M  +34   -14   kmymoney/views/kaccountsview_p.h

https://invent.kde.org/office/kmymoney/commit/b17daebdca0c0611e1f54659ae06a5a47a60ea90

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

[kmymoney] [Bug 450927] Equities with zero balance option does not work

2022-07-01 Thread Thomas Baumgart
https://bugs.kde.org/show_bug.cgi?id=450927

--- Comment #10 from Thomas Baumgart  ---
Git commit 7999c11a4e1dfcd1459ca7c9adcdecb3dd037150 by Thomas Baumgart.
Committed on 01/07/2022 at 07:57.
Pushed by tbaumgart into branch '5.1'.

Improve closing investment accounts

One needed to close all security accounts first before one could close
the parent investment account. This change improves the process so that
an investment account can be closed with all sub-ordinate security
accounts in one go if the conditions to close an account apply to all
accounts to be closed (balance equal to zero, not referenced in
schedules, ...)
(cherry picked from commit b17daebdca0c0611e1f54659ae06a5a47a60ea90)

M  +29   -0kmymoney/mymoney/mymoneyfile.cpp
M  +15   -3kmymoney/views/kaccountsview.cpp
M  +38   -18   kmymoney/views/kaccountsview_p.h

https://invent.kde.org/office/kmymoney/commit/7999c11a4e1dfcd1459ca7c9adcdecb3dd037150

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

[kwin] [Bug 452219] Low fps and high CPU usage on external monitor connected to NVIDIA when default GPU is Intel

2022-07-01 Thread Celeste
https://bugs.kde.org/show_bug.cgi?id=452219

Celeste  changed:

   What|Removed |Added

 CC||coelacant...@outlook.com

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

[systemsettings] [Bug 455944] The color scheme setting is lost after the second logout-login

2022-07-01 Thread mdyne
https://bugs.kde.org/show_bug.cgi?id=455944

mdyne  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #6 from mdyne  ---
I installed Fedora Rawhide KDE (which is a development version of Fedora 37)
with KDE Plasma Version 5.25.2. The bug is fixed there.

Thank you for the information.

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

[kdevelop] [Bug 395856] Semantic highlighting uses hardcoded colors that cannot be changed

2022-07-01 Thread Milian Wolff
https://bugs.kde.org/show_bug.cgi?id=395856

Milian Wolff  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/kdev
   ||elop/kdevelop/commit/54b3be
   ||95cd66f9cf0141031a5d97d4b6a
   ||5dc8031
 Status|ASSIGNED|RESOLVED

--- Comment #27 from Milian Wolff  ---
Git commit 54b3be95cd66f9cf0141031a5d97d4b6a5dc8031 by Milian Wolff, on behalf
of Martin Seher.
Committed on 01/07/2022 at 08:28.
Pushed by mwolff into branch 'master'.

Configurable semantic colors

Add a page under _Color Themes -> Highlighting Text Styles -> KDevelop/Semantic
Colors_ that allows the configuration of the semantic highlight colors.
- When the _Local colorization intensity_ is bigger than zero then the rainbow
colors are used for local variables like before, overwriting the corresponding
configured colors
- A _Global colorization intensity_ less then 255 (max) will still cause a
blending of the global colors
- _Bold font for declarations_ will make the declarations bold in addition to
the bold settings from the config dialog

So a _Local colorization intensity_ of 0 and a _Global colorization intensity_
of 255 should be set when the exact configured colors are desired.

See also:
https://invent.kde.org/kdevelop/kdevelop/uploads/500467bc355906d363e3a76a9044e138/ColorConfig.png

M  +1-0kdevplatform/language/CMakeLists.txt
M  +15   -5kdevplatform/language/highlighting/codehighlighting.cpp
M  +3-0kdevplatform/language/highlighting/codehighlighting.h
M  +133  -5kdevplatform/language/highlighting/colorcache.cpp
M  +9-0kdevplatform/language/highlighting/colorcache.h
M  +3-0kdevplatform/language/highlighting/configurablecolors.cpp
A  +42   -0   
kdevplatform/language/highlighting/syntax/kdevelop-semantic-colors.xml
A  +5-0kdevplatform/language/highlighting/syntax/syntax.qrc
M  +10   -15   plugins/contextbrowser/contextbrowser.cpp
M  +2-2plugins/contextbrowser/contextbrowser.h

https://invent.kde.org/kdevelop/kdevelop/commit/54b3be95cd66f9cf0141031a5d97d4b6a5dc8031

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

[kde] [Bug 456195] New: On screen keyboard shown upon log in and taking over whole screen

2022-07-01 Thread Aleksa Savic
https://bugs.kde.org/show_bug.cgi?id=456195

Bug ID: 456195
   Summary: On screen keyboard shown upon log in and taking over
whole screen
   Product: kde
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: savicaleks...@gmail.com
  Target Milestone: ---

SUMMARY
I'm on Fedora 36, using Plasma 5.25.2. Also happened in 5.25.1. When logging
out, the virtual on screen keyboard takes up the whole screen. I can press
enter and then it clears up, shows the user account choosing screen for a split
second and logs me in (I don't have a password set, so that's normal).


STEPS TO REPRODUCE
1. Log in normally (I have auto login to X11 enabled)
2. Log out
3. You'll see the virtual keyboard that won't close

OBSERVED RESULT

Seeing a virtual keyboard.

EXPECTED RESULT

Being able to choose user and session.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 36
KDE Plasma Version: 5.25.2
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.3
Kernel Version: 5.18.7-200.fc36.x86_64 (64-bit)
Graphics Platform: X11
Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor
Memory: 62.6 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2
Manufacturer: GIGABYTE

ADDITIONAL INFORMATION

Not sure what the correct category for the login subsystem is, so putting it
under kde.

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

[filelight] [Bug 456177] Optional pie chart corresponding to number of files

2022-07-01 Thread postix
https://bugs.kde.org/show_bug.cgi?id=456177

--- Comment #2 from postix  ---
(In reply to Harald Sitter from comment #1)
> Seems too niche a feature for the amount of work unfortunately.

Since the number of files contained per folder is counted anyway, isn't it just
the number (#files <--> file size) which should change in the pie chart in the
end?

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

[kmail2] [Bug 456196] New: Title formatting not properly restored for HTML messages (templates, edit as new)

2022-07-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=456196

Bug ID: 456196
   Summary: Title formatting not properly restored for HTML
messages (templates, edit as new)
   Product: kmail2
   Version: 5.20.2
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: composer
  Assignee: kdepim-b...@kde.org
  Reporter: missol...@protonmail.com
  Target Milestone: ---

SUMMARY

When opening a previously saved HTML message in the composer to edit it
(whether it is a template in the templates folder of the email account, or a
regular email that the user wants to "Edit as new"), all the rich formatting
related to titles is not properly restored. To be specific:

If some text has the style "Title" applied to it, after saving the message as a
template and reopening it in the composer, the text will now have the style
"Basic text" and will only be bold (its font size has decreased: the text is as
small as Basic Text). The same happens when editing a message as new. 

>From a user perspective, the main nuisance is in the template use case since
the goal of templates is to have the formatting all set up in advance. Beyond a
permanent fix, I would appreciate a temporary workaround if any exists as this
is really affecting quality of life for email intensive workflows (customer
service, sales, etc...).


STEPS TO REPRODUCE
1. Create a new message with Rich Text, insert some text and give it the
"Title" style 
2. Save the message as Template
3. Open the message again in the composer to edit it by double clicking it in
the folder template or by using the "Edit as New" option

OBSERVED RESULT

The title has now been switched back to the style "Basic text" and while its
boldness is still there, its font size has decreased (it now has the font-size
of basic text)

EXPECTED RESULT

The title style should still be present after reopening the message in the
composer.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Tumbleweed 20220625
(available in About System)
KDE Plasma Version: 5.25.1
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.2
Kernel version: 5.18.6-1-default (64-bit)

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

[kwin] [Bug 456133] Touching a running application in WindowHeap-based effects using a touchscreen doesn't switch to it

2022-07-01 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=456133

Bug Janitor Service  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED

--- Comment #3 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/plasma/kwin/-/merge_requests/2601

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

[valgrind] [Bug 456171] [PATCH] FreeBSD: Don't record address errors when accessing the 'kern.ps_strings' sysctl struct

2022-07-01 Thread obiwac
https://bugs.kde.org/show_bug.cgi?id=456171

obi...@gmail.com  changed:

   What|Removed |Added

 Attachment #150290|0   |1
is obsolete||

--- Comment #2 from obi...@gmail.com  ---
Created attachment 150313
  --> https://bugs.kde.org/attachment.cgi?id=150313&action=edit
Quick patch II: Le retour

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

[valgrind] [Bug 456171] [PATCH] FreeBSD: Don't record address errors when accessing the 'kern.ps_strings' sysctl struct

2022-07-01 Thread obiwac
https://bugs.kde.org/show_bug.cgi?id=456171

--- Comment #3 from obi...@gmail.com  ---
All done! Sorry about, I'm completely new to this codebase 😅

Is there a comprehensive document somewhere about the dos and don'ts/what's
convention for future reference?

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

[krita] [Bug 455570] Krita plus 5.1.0 prealpha : complex brush outline causes intolerable performance lag

2022-07-01 Thread Dmitry Kazakov
https://bugs.kde.org/show_bug.cgi?id=455570

Dmitry Kazakov  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap
   |hics/krita/commit/bef36adac |hics/krita/commit/2130f06ac
   |9ed3934c68431da838045041fa4 |829aa8bedb4f9c85956aa246e75
   |a31d|ca44

--- Comment #13 from Dmitry Kazakov  ---
Git commit 2130f06ac829aa8bedb4f9c85956aa246e75ca44 by Dmitry Kazakov.
Committed on 01/07/2022 at 09:03.
Pushed by dkazakov into branch 'master'.

Fix extremely slow outline rendering with fuzzy brushes

If the brush is very fuzzy, then it may generate too many polygons,
which would make QPainterPath::toSubpathPolygons() extremely slow
(especially on Windows due to slow memory allocations). And since
we call this function on every frame render it may make Krita GUI
stutter a lot.

To workaround this issue this patch implements a special class
KisOptimizedBrushOutline. Its main purpose is to make sure that
the brush outline cache is stored in already prepared format
of QVector, so that we wouldn't have to convert
QPainterPath into polygons on every frame generation.

The class also makes sure that the original set of polygons is
immutable, so no extra allocations happen while the outline is
passed from the brush to the GUI rendering code. It is implemented
via storing the transformation and extra paths in separate objects.

M  +2-1libs/brush/kis_auto_brush.cpp
M  +1-1libs/brush/kis_auto_brush.h
M  +5-4libs/brush/kis_brush.cpp
M  +2-1libs/brush/kis_brush.h
M  +2-2libs/brush/kis_imagepipe_brush.cpp
M  +1-1libs/brush/kis_imagepipe_brush.h
M  +1-0libs/image/CMakeLists.txt
A  +135  -0libs/image/brushengine/KisOptimizedBrushOutline.cpp  *
A  +110  -0libs/image/brushengine/KisOptimizedBrushOutline.h  *
M  +4-3libs/image/brushengine/kis_paintop_settings.cpp
M  +3-2libs/image/brushengine/kis_paintop_settings.h
M  +4-4libs/ui/opengl/KisOpenGLCanvasRenderer.cpp
M  +2-1libs/ui/opengl/KisOpenGLCanvasRenderer.h
M  +1-1libs/ui/opengl/kis_opengl_canvas2.cpp
M  +2-1libs/ui/opengl/kis_opengl_canvas2.h
M  +15   -2libs/ui/tool/kis_tool.cc
M  +4-1libs/ui/tool/kis_tool.h
M  +3-2libs/ui/tool/kis_tool_freehand.cc
M  +3-3libs/ui/tool/kis_tool_freehand.h
M  +6-5libs/ui/tool/kis_tool_freehand_helper.cpp
M  +4-4libs/ui/tool/kis_tool_freehand_helper.h
M  +17   -11   libs/ui/tool/kis_tool_paint.cc
M  +6-5libs/ui/tool/kis_tool_paint.h
M  +12   -7   
plugins/paintops/defaultpaintops/duplicate/kis_duplicateop_settings.cpp
M  +1-1   
plugins/paintops/defaultpaintops/duplicate/kis_duplicateop_settings.h
M  +3-2plugins/paintops/deform/kis_deform_paintop_settings.cpp
M  +1-1plugins/paintops/deform/kis_deform_paintop_settings.h
M  +3-1plugins/paintops/experiment/kis_experiment_paintop_settings.cpp
M  +1-1plugins/paintops/experiment/kis_experiment_paintop_settings.h
M  +5-4plugins/paintops/gridbrush/kis_grid_paintop_settings.cpp
M  +1-1plugins/paintops/gridbrush/kis_grid_paintop_settings.h
M  +2-1plugins/paintops/hairy/kis_hairy_paintop_settings.cpp
M  +1-1plugins/paintops/hairy/kis_hairy_paintop_settings.h
M  +5-4plugins/paintops/libpaintop/kis_brush_based_paintop_settings.cpp
M  +2-2plugins/paintops/libpaintop/kis_brush_based_paintop_settings.h
M  +3-9plugins/paintops/libpaintop/kis_current_outline_fetcher.cpp
M  +10   -8plugins/paintops/libpaintop/kis_current_outline_fetcher.h
M  +3-3plugins/paintops/mypaint/MyPaintPaintOpSettings.cpp
M  +1-1plugins/paintops/mypaint/MyPaintPaintOpSettings.h
M  +3-3plugins/paintops/roundmarker/kis_roundmarkerop_settings.cpp
M  +1-1plugins/paintops/roundmarker/kis_roundmarkerop_settings.h
M  +4-4plugins/paintops/sketch/kis_sketch_paintop_settings.cpp
M  +1-1plugins/paintops/sketch/kis_sketch_paintop_settings.h
M  +3-2plugins/paintops/spray/kis_spray_paintop_settings.cpp
M  +1-1plugins/paintops/spray/kis_spray_paintop_settings.h
M  +1-0plugins/tools/basictools/kis_tool_move.cc
M  +1-1plugins/tools/selectiontools/KisToolSelectMagnetic.cc
M  +1-0plugins/tools/selectiontools/kis_tool_select_path.cc
M  +4-4   
plugins/tools/tool_enclose_and_fill/subtools/KisToolBasicBrushBase.cpp
M  +1-1   
plugins/tools/tool_enclose_and_fill/subtools/KisToolBasicBrushBase.h
M  +1-0plugins/tools/tool_transform2/kis_tool_transform.cc

The files marked with a * at the end have a non valid license. Please read:
https://community.kde.org/Policies/Licensing_Policy and use the headers which
are listed at that page.


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

[krita] [Bug 455570] Krita plus 5.1.0 prealpha : complex brush outline causes intolerable performance lag

2022-07-01 Thread Dmitry Kazakov
https://bugs.kde.org/show_bug.cgi?id=455570

Dmitry Kazakov  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap
   |hics/krita/commit/2130f06ac |hics/krita/commit/f58beab32
   |829aa8bedb4f9c85956aa246e75 |9ecc38e2c2472bf69bc5a43bafe
   |ca44|7e57

--- Comment #14 from Dmitry Kazakov  ---
Git commit f58beab329ecc38e2c2472bf69bc5a43bafe7e57 by Dmitry Kazakov.
Committed on 01/07/2022 at 09:04.
Pushed by dkazakov into branch 'krita/5.1'.

Fix extremely slow outline rendering with fuzzy brushes

If the brush is very fuzzy, then it may generate too many polygons,
which would make QPainterPath::toSubpathPolygons() extremely slow
(especially on Windows due to slow memory allocations). And since
we call this function on every frame render it may make Krita GUI
stutter a lot.

To workaround this issue this patch implements a special class
KisOptimizedBrushOutline. Its main purpose is to make sure that
the brush outline cache is stored in already prepared format
of QVector, so that we wouldn't have to convert
QPainterPath into polygons on every frame generation.

The class also makes sure that the original set of polygons is
immutable, so no extra allocations happen while the outline is
passed from the brush to the GUI rendering code. It is implemented
via storing the transformation and extra paths in separate objects.

M  +2-1libs/brush/kis_auto_brush.cpp
M  +1-1libs/brush/kis_auto_brush.h
M  +5-4libs/brush/kis_brush.cpp
M  +2-1libs/brush/kis_brush.h
M  +2-2libs/brush/kis_imagepipe_brush.cpp
M  +1-1libs/brush/kis_imagepipe_brush.h
M  +1-0libs/image/CMakeLists.txt
A  +135  -0libs/image/brushengine/KisOptimizedBrushOutline.cpp  *
A  +110  -0libs/image/brushengine/KisOptimizedBrushOutline.h  *
M  +4-3libs/image/brushengine/kis_paintop_settings.cpp
M  +3-2libs/image/brushengine/kis_paintop_settings.h
M  +4-4libs/ui/opengl/KisOpenGLCanvasRenderer.cpp
M  +2-1libs/ui/opengl/KisOpenGLCanvasRenderer.h
M  +1-1libs/ui/opengl/kis_opengl_canvas2.cpp
M  +2-1libs/ui/opengl/kis_opengl_canvas2.h
M  +15   -2libs/ui/tool/kis_tool.cc
M  +4-1libs/ui/tool/kis_tool.h
M  +3-2libs/ui/tool/kis_tool_freehand.cc
M  +3-3libs/ui/tool/kis_tool_freehand.h
M  +6-5libs/ui/tool/kis_tool_freehand_helper.cpp
M  +4-4libs/ui/tool/kis_tool_freehand_helper.h
M  +17   -11   libs/ui/tool/kis_tool_paint.cc
M  +6-5libs/ui/tool/kis_tool_paint.h
M  +12   -7   
plugins/paintops/defaultpaintops/duplicate/kis_duplicateop_settings.cpp
M  +1-1   
plugins/paintops/defaultpaintops/duplicate/kis_duplicateop_settings.h
M  +3-2plugins/paintops/deform/kis_deform_paintop_settings.cpp
M  +1-1plugins/paintops/deform/kis_deform_paintop_settings.h
M  +3-1plugins/paintops/experiment/kis_experiment_paintop_settings.cpp
M  +1-1plugins/paintops/experiment/kis_experiment_paintop_settings.h
M  +5-4plugins/paintops/gridbrush/kis_grid_paintop_settings.cpp
M  +1-1plugins/paintops/gridbrush/kis_grid_paintop_settings.h
M  +2-1plugins/paintops/hairy/kis_hairy_paintop_settings.cpp
M  +1-1plugins/paintops/hairy/kis_hairy_paintop_settings.h
M  +5-4plugins/paintops/libpaintop/kis_brush_based_paintop_settings.cpp
M  +2-2plugins/paintops/libpaintop/kis_brush_based_paintop_settings.h
M  +3-9plugins/paintops/libpaintop/kis_current_outline_fetcher.cpp
M  +10   -8plugins/paintops/libpaintop/kis_current_outline_fetcher.h
M  +3-3plugins/paintops/mypaint/MyPaintPaintOpSettings.cpp
M  +1-1plugins/paintops/mypaint/MyPaintPaintOpSettings.h
M  +3-3plugins/paintops/roundmarker/kis_roundmarkerop_settings.cpp
M  +1-1plugins/paintops/roundmarker/kis_roundmarkerop_settings.h
M  +4-4plugins/paintops/sketch/kis_sketch_paintop_settings.cpp
M  +1-1plugins/paintops/sketch/kis_sketch_paintop_settings.h
M  +3-2plugins/paintops/spray/kis_spray_paintop_settings.cpp
M  +1-1plugins/paintops/spray/kis_spray_paintop_settings.h
M  +1-0plugins/tools/basictools/kis_tool_move.cc
M  +1-1plugins/tools/selectiontools/KisToolSelectMagnetic.cc
M  +1-0plugins/tools/selectiontools/kis_tool_select_path.cc
M  +4-4   
plugins/tools/tool_enclose_and_fill/subtools/KisToolBasicBrushBase.cpp
M  +1-1   
plugins/tools/tool_enclose_and_fill/subtools/KisToolBasicBrushBase.h
M  +1-0plugins/tools/tool_transform2/kis_tool_transform.cc

The files marked with a * at the end have a non valid license. Please read:
https://community.kde.org/Policies/Licensing_Policy and use the headers which
are listed at that page.


https://invent.kde.org/graphics/krita/comm

[kwin] [Bug 447840] Touchegg-provided gestures don't work in WindowHeap-based effects on X11 anymore

2022-07-01 Thread Hyuk
https://bugs.kde.org/show_bug.cgi?id=447840

Hyuk  changed:

   What|Removed |Added

 Status|CONFIRMED   |REPORTED
 Ever confirmed|1   |0

--- Comment #23 from Hyuk  ---
(In reply to Nate Graham from comment #22)
> I'm sorry you're having issues. I suspect compositing got disabled (perhaps
> due to Bug 432038), so as a first step, you should see if you can re-enable
> it with Alt+Shift+F12.
> 
> But more generally, this isn't the right place to ask for help about issues
> like that, because this bugzilla ticket is about Touchegg-provided gestures
> not working in WindowHeap-based effects on X11 anymore. I'm glad to help you
> further, but let's doing it using real-time chat in an appropriate user
> support channel. #kde on Matrix/IRC or @kdecommunity on Telegram would work.

Hi Nate,

Thanks a lot for your quick reply. I've already tried Alt+Shift+F12, "kwin_x11
--replace &", and "Compositor -> Compositing: Enable on startup" as a  very
first step last night but no luck. :( 
One thing that I noticed is "Enable on startup" setting gets unchecked once I
close and reopen the system settings window. 

As for chatting on Matrix/IRC, I'm sorry but I've never used it before. How
does it work? So I need telegram to log in to the channel? 

Many thanks for your assistance.

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

[krita] [Bug 455570] Krita plus 5.1.0 prealpha : complex brush outline causes intolerable performance lag

2022-07-01 Thread Dmitry Kazakov
https://bugs.kde.org/show_bug.cgi?id=455570

Dmitry Kazakov  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap
   |hics/krita/commit/f58beab32 |hics/krita/commit/2130f06ac
   |9ecc38e2c2472bf69bc5a43bafe |829aa8bedb4f9c85956aa246e75
   |7e57|ca44

--- Comment #15 from Dmitry Kazakov  ---
Hi, Stephen!

I have fixed the problem that was triggered by the "moo bubble" brush. That
stutter should go now. Though I haven't even checked the part of the bug that
is related to 1700px brushes, because Krita officially doesn't support brushes
bigger that 1000px. Usage of such brushes is "at your own risk" :)

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

[Akonadi] [Bug 336581] accidental database loss causes Akonadi / KMail to silently break correct folder assignments

2022-07-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=336581

missol...@protonmail.com changed:

   What|Removed |Added

 CC||missol...@protonmail.com

--- Comment #14 from missol...@protonmail.com ---
Just to confirm that the issue is still there for Kmail 5.20.2. The akonadi
database gets corrupted randomly (happened to me after a distro upgrade that
otherwise went perfectly fine) and after removing Akonadi's corrupted data
folders and syncing again, all folder associations were messed up. 

Can't way for the day when our whole company can start relying on KDE PIM's
framework. It looks very promising and the vision behind akonadi is brilliant,
but this data corruption issue is a deal breaker. I hope you manage to fix this
soon, stability and durability are so important for this kind of application. 

If a solution is known but what is lacking is manpower, please let the
community know so that we can try to organize sponsorship. This is such a
critical issue (I am referring to the data corruption. Folder assignment is
more a symptom. If data corruption wasn't there in the first place, folder
assignment mix up wouldn't be an issue. I feel it would probably be better to
fix the fragility of the storage system to make such symptoms non-issues by
removing a vast class of failure modes rather than rather than trying to come
up with global ids).

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

[krita] [Bug 456197] New: Pattern is loaded only after the brush is selected. Default brushes

2022-07-01 Thread RamonMiranda
https://bugs.kde.org/show_bug.cgi?id=456197

Bug ID: 456197
   Summary: Pattern is loaded only after the brush is selected.
Default brushes
   Product: krita
   Version: 5.0.6
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Resource Management
  Assignee: krita-bugs-n...@kde.org
  Reporter: mirandagrap...@gmail.com
  Target Milestone: ---

Created attachment 150314
  --> https://bugs.kde.org/attachment.cgi?id=150314&action=edit
The patterns in .png to be replaced. They need to be renamed but .pat is what
the brush looks for

SUMMARY
Pattern is loaded only after the brush is selected. Default brushes.  
g) Dry Textured Creases   
h) Chalk Details
These brushes are afected and create 2 issues. Lag while loading the texture
the first time. And second if i create a variant from them and save it with
different name. If i restart Krita and i select the variant first, the texture
is not created. Tested from Scratch in Windows 10 and Kubuntu 


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT
The brushstroke has no texture until i 

EXPECTED RESULT
Those patterns must be created by default. (added in attachment) They are named
as .pat Extension maybe is related with that? 
I add the images in png format 

SOFTWARE/OS VERSIONS
Windows: 10
macOS: 
Linux/KDE Plasma: Kubuntu
(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.

[krita] [Bug 456197] Pattern is loaded only after the brush is selected. Default brushes

2022-07-01 Thread RamonMiranda
https://bugs.kde.org/show_bug.cgi?id=456197

--- Comment #1 from RamonMiranda  ---
Created attachment 150315
  --> https://bugs.kde.org/attachment.cgi?id=150315&action=edit
This is for pastel details

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

[valgrind] [Bug 456171] [PATCH] FreeBSD: Don't record address errors when accessing the 'kern.ps_strings' sysctl struct

2022-07-01 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=456171

--- Comment #4 from Paul Floyd  ---
Thanks again. Do you know where the memory that memcheck is complaining about
comes from?

I'll do some tests with konsole/xterm and see what they do.

As for documentation, README_DEVELOPERS, README_DEVELOPERS_processes and
README.freebsd are a good start. There's some good stuff in docs/internals.
After that, there are the mailing lists and their archives.

For "live" questions, #valgrind-dev in Libera.Chat IRC is the best (Valgrind is
very old-school).

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

[dolphin] [Bug 456198] New: Display of target of relative symbolic links is incorrect

2022-07-01 Thread Paul Worrall
https://bugs.kde.org/show_bug.cgi?id=456198

Bug ID: 456198
   Summary: Display of target of relative symbolic links is
incorrect
   Product: dolphin
   Version: 22.04.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: bars: status
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: p.r.worr...@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

STEPS TO REPRODUCE
1. Navigate in Dolphin to /var/spool
2. Hover over or select the item called "mail" (this is actually a symbolic
link to "../mail")

OBSERVED RESULT
Status bar says it's a link to "file:///var/spool/mail" (i.e. a link to
itself!)

EXPECTED RESULT
Status bar says it's a link to "file:///var/mail

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.25
KDE Plasma Version: 5.25.2
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.5
Kernel Version: 5.13.0-51-generic (64-bit)
Graphics Platform: X11
Processors: 2 × AMD A6-6400K APU with Radeon(tm) HD Graphics
Memory: 7.7 GiB of RAM
Graphics Processor: AMD CEDAR
Manufacturer: NOVATECH LTD
Product Name: BB-64004H
System Version: V1.0

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

[lattedock] [Bug 456199] New: Panel indicator line remain when panel is hidden or visible

2022-07-01 Thread Alvaro
https://bugs.kde.org/show_bug.cgi?id=456199

Bug ID: 456199
   Summary: Panel indicator line remain when panel is hidden or
visible
   Product: lattedock
   Version: 0.10.8
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: panabu...@gmail.com
  Target Milestone: ---

Created attachment 150316
  --> https://bugs.kde.org/attachment.cgi?id=150316&action=edit
Issue Video

SUMMARY
***
When I move the pointer slowly to the panel to make it visible, the panel
indicator line will be still visible when it should be hidden
***
I'm attaching a video with the problem that it will explain better for itself

STEPS TO REPRODUCE
1. Move slowly the pointer where the panel is to make it visible
2. Make the panel visible
3. Move the pointer out of the panel to hide it

OBSERVED RESULT
Panel indicator line still visible

EXPECTED RESULT
Panel indicator line should be hidden

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.18.6-1-MANJARO (64-bit)
KDE Plasma Version: 5.24.1
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.5

ADDITIONAL INFORMATION
Graphics Platform: X11

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

[lattedock] [Bug 456199] Panel indicator line remain when panel is hidden or visible

2022-07-01 Thread Alvaro
https://bugs.kde.org/show_bug.cgi?id=456199

Alvaro  changed:

   What|Removed |Added

 CC||panabu...@gmail.com

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

[valgrind] [Bug 456200] New: Valgrind should not required neon (simd) on armhf

2022-07-01 Thread Mathieu Malaterre
https://bugs.kde.org/show_bug.cgi?id=456200

Bug ID: 456200
   Summary: Valgrind should not required neon (simd) on armhf
   Product: valgrind
   Version: 3.20 GIT
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: ma...@debian.org
  Target Milestone: ---

SUMMARY

valgrind is currently configured to build with: -mcpu=cortex-a8
Since gcc-11 (and above) this means the compiler is free to include simd (neon)
instruction. Since neon is not stricly required to run valgrind on armhf,
please reduce requirement.



STEPS TO REPRODUCE

% git clone 
% ./autogen.sh && ./configure && make
% ./vg-in-place
Illegal instruction.

OBSERVED RESULT

neon instructions is present in the binaries.

Program received signal SIGILL, Illegal instruction.
vgPlain_am_startup (sp_at_startup=3204445696) at
m_aspacemgr/aspacemgr-linux.c:1626
1626   init_nsegment(&seg);
(gdb) x/i $pc
=> 0x58071090 :  vmov.i32d16, #0 ; 0x

EXPECTED RESULT

valgrind should run on neon-less armhf.

SOFTWARE/OS VERSIONS

% cat /proc/cpuinfo
model name  : ARMv7 Processor rev 2 (v7l)
Features: half thumb fastmult vfp edsp thumbee vfpv3 tls idiva idivt
vfpd32 lpae

ADDITIONAL INFORMATION

Complete thread on valgrind-users

https://sourceforge.net/p/valgrind/mailman/valgrind-users/thread/CA%2B7wUsyP0aTmfQMi3ro0AeXvRW8v2G1UYsLoFxpvi_RCUrbdJQ%40mail.gmail.com/#msg37673816

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

[valgrind] [Bug 456200] Valgrind should not required neon (simd) on armhf

2022-07-01 Thread Mathieu Malaterre
https://bugs.kde.org/show_bug.cgi?id=456200

--- Comment #1 from Mathieu Malaterre  ---
Here is a suggested patch:

 % sed -i -e 's/cortex-a8/generic-armv7-a+vfpv3-d16/g' Makefile.all.am

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

[krita] [Bug 456201] New: Crash after a right click on a group layer

2022-07-01 Thread David REVOY
https://bugs.kde.org/show_bug.cgi?id=456201

Bug ID: 456201
   Summary: Crash after a right click on a group layer
   Product: krita
   Version: 5.1.0-beta1
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: Layer Stack
  Assignee: krita-bugs-n...@kde.org
  Reporter: i...@davidrevoy.com
  Target Milestone: ---

Hi,
Here is a specific crash: it works only on a specific Krita file, after opening
and right-clicking on a folded layer group named "frame". I tried to remove
other layer to make a smaller file, but doing so fixed the layer stack because
after that I wasn't able to reproduce.

To reproduce:
===
1. Download and extract
https://www.peppercarrot.com/extras/temp/2022-07-01_E37P04_crash-right-click-on-frame-layer.zip
2. When the Krita file open, it might prompt for a missing link to a text
layer; it's not related to the bug, select no.
3. Right click on the folded group layer named "frame" on top of layer stack
(original intent was to color this group to grey in the layer stack)

Result:
==
Krita crashes. Sometime, the right-click menu of the layer stack appears
briefly but Krita crashes anyway. 

Expected:

Access the right-click menu, no crash and being able to color the group layer
with grey color slot.

LOGS:
=
GDB:
```
GNU gdb (GDB) Fedora 12.1-1.fc36
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /home/deevad/sources/krita/krita-testing...
(No debugging symbols found in /home/deevad/sources/krita/krita-testing)
Starting program: /home/deevad/sources/krita/krita-testing
/home/deevad/peppercarrot/webcomics/new-ep37_Phoenix-Tears/E37P04.kra
/usr/bin/AppImageLauncher: /lib64/libcurl.so.4: no version information
available (required by
/usr/bin/../lib/x86_64-linux-gnu/appimagelauncher/libappimageupdate.so)
[Detaching after fork from child process 7800]
process 7797 is executing new program:
/usr/lib/x86_64-linux-gnu/appimagelauncher/binfmt-bypass
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[Detaching after fork from child process 7806]
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
krita.general: convertAndSetBlendMode: Curve conversion is not implemented yet
QObject::startTimer: Timers cannot have negative intervals
Could not find platform independent libraries 
Could not find platform dependent libraries 
Consider setting $PYTHONHOME to [:]
/tmp/.mount_krita-OxCsZi/usr/lib/krita-python-libs/krita added to PYTHONPATH
profileForCsIdWithFallbackImpl couldn't fetch a fallback profile for  
QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout
QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout
QImage::scaled: Image is a null image
[Inferior 1 (process 7797) exited normally]
Missing separate debuginfos, use: dnf debuginfo-install
appimagelauncher-2.2.0-travis995~0f91801.x86_64
(gdb) 
```

KRITA LOGS:
==
```
SESSION: 01 Jul 2022 11:33:15 +0200. Executing

[valgrind] [Bug 456200] Valgrind should not required neon (simd) on armhf

2022-07-01 Thread Mathieu Malaterre
https://bugs.kde.org/show_bug.cgi?id=456200

Mathieu Malaterre  changed:

   What|Removed |Added

  Latest Commit||022dfeee73726d92ecc0349ebe4
   ||2d7b52132b8e5

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

[valgrind] [Bug 456200] Valgrind should not required neon (simd) on armhf

2022-07-01 Thread Mathieu Malaterre
https://bugs.kde.org/show_bug.cgi?id=456200

Mathieu Malaterre  changed:

   What|Removed |Added

URL||https://bugs.debian.org/cgi
   ||-bin/bugreport.cgi?bug=1014
   ||091#12

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

[krita] [Bug 456201] Crash after a right click on a group layer

2022-07-01 Thread Halla Rempt
https://bugs.kde.org/show_bug.cgi?id=456201

Halla Rempt  changed:

   What|Removed |Added

 CC||ha...@valdyas.org

--- Comment #1 from Halla Rempt  ---
I cannot open the file because of the missing file layer:

krita(100321)/(default) unknown: ASSERT: "channelFlags.isEmpty()
||((quint32)channelFlags.count() == colorSpace()->channelCount())" in file
/home/halla/dev/krita/libs/image/kis_layer.cc, line 342

Thread 1 "krita" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x752ef859 in __GI_abort () at abort.c:79
#2  0x7579c455 in QMessageLogger::fatal(char const*, ...) const ()
   from /home/halla/dev/deps/lib/libQt5Core.so.5
#3  0x7579b827 in qt_assert(char const*, char const*, int) ()
   from /home/halla/dev/deps/lib/libQt5Core.so.5
#4  0x76c9d2f8 in KisLayer::setChannelFlags (this=,
channelFlags=...)
at /home/halla/dev/krita/libs/image/kis_layer.cc:342
#5  0x7fffc85efdd1 in KisKraLoader::loadNode (this=0x57e72080,
element=..., image=...)
at /home/halla/dev/krita/plugins/impex/libkra/kis_kra_loader.cpp:921
#6  0x7fffc85f14e3 in KisKraLoader::loadNodes (this=0x57e72080,
element=..., image=..., parent=...)
at /home/halla/dev/krita/plugins/impex/libkra/kis_kra_loader.cpp:756
#7  0x7fffc85f2663 in KisKraLoader::loadXML (this=0x57e72080,
imageElement=...)
at /home/halla/dev/krita/plugins/impex/libkra/kis_kra_loader.cpp:297
#8  0x7fffc862b83a in KraConverter::loadXML (this=0x7fffc050, doc=...,
store=)
at /home/halla/dev/krita/plugins/impex/libkra/kra_converter.cpp:374
#9  0x7fffc862db31 in KraConverter::buildImage
(this=this@entry=0x7fffc050, io=0x7fffbf50, 
io@entry=0x7fffc110) at
/home/halla/dev/krita/plugins/impex/libkra/kra_converter.cpp:87
#10 0x7fffc864e3ce in KraImport::convert (this=,
document=0x59406b20, io=0x7fffc110)
at /home/halla/dev/krita/plugins/impex/kra/kra_import.cpp:30
#11 0x77c4ef9c in KisImportExportManager::doImport
(this=0x59bc2940, location=..., filter=...)
at /home/halla/dev/krita/libs/ui/KisImportExportManager.cpp:665
#12 0x77c507ba in KisImportExportManager::convert (this=0x59bc2940,
direction=, 
location=..., realLocation=..., mimeType=..., showWarnings=,
exportConfiguration=..., 
isAsync=, isAdvancedExporting=)
at /home/halla/dev/krita/libs/ui/KisImportExportManager.cpp:376
#13 0x77c5158b in KisImportExportManager::importDocument
(this=this@entry=0x59bc2940, location=..., 
mimeType=...) at /home/halla/dev/krita/libs/global/kis_shared_ptr.h:206
#14 0x77c36065 in KisDocument::openFile (this=0x59406b20)
at /home/halla/dev/krita/libs/ui/KisDocument.cpp:1860
#15 0x77c36ad9 in KisDocument::openPathInternal (this=0x59406b20,
path=...)
at /home/halla/dev/krita/libs/ui/KisDocument.cpp:2416
#16 0x77c3c2d9 in KisDocument::openPath
(this=this@entry=0x59406b20, _path=..., flags=..., 
flags@entry=...) at /home/halla/dev/krita/libs/ui/KisDocument.cpp:1796
#17 0x77c60045 in KisMainWindow::openDocumentInternal (this=, path=..., flags=...)
at /home/halla/dev/krita/libs/ui/KisMainWindow.cpp:1024
#18 0x77c6063d in KisMainWindow::openDocument (this=0x57945270,
path=..., flags=...)
at /home/halla/dev/krita/libs/ui/KisMainWindow.cpp:998
#19 0x77c60a75 in KisMainWindow::slotFileOpen (this=0x57945270,
isImporting=false)
at /home/halla/dev/krita/libs/ui/KisMainWindow.cpp:1637
#20 0x759cb0f0 in QMetaObject::activate(QObject*, int, int, void**) ()
   from /home/halla/dev/deps/lib/libQt5Core.so.5
#21 0x763cfa36 in QAction::triggered(bool) () from
/home/halla/dev/deps/lib/libQt5Widgets.so.5
#22 0x763d20f2 in QAction::activate(QAction::ActionEvent) ()
   from /home/halla/dev/deps/lib/libQt5Widgets.so.5
#23 0x763d29bf in QAction::event(QEvent*) () from
/home/halla/dev/deps/lib/libQt5Widgets.so.5
#24 0x763d60d6 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
()
   from /home/halla/dev/deps/lib/libQt5Widgets.so.5
#25 0x763df5d0 in QApplication::notify(QObject*, QEvent*) ()
   from /home/halla/dev/deps/lib/libQt5Widgets.so.5
#26 0x77c1c7c5 in KisApplication::notify (this=0x7fffd570,
receiver=0x59d4d320, 
event=0x7fffce40) at
/home/halla/dev/krita/libs/ui/KisApplication.cpp:761
#27 0x7599f6ea in QCoreApplication::notifyInternal2(QObject*, QEvent*)
()
   from /home/halla/dev/deps/lib/libQt5Core.so.5
#28 0x75dbb93e in QShortcutMap::dispatchEvent(QKeyEvent*) ()
--Type  for more, q to quit, c to continue w

[krita] [Bug 456201] Crash after a right click on a group layer

2022-07-01 Thread Halla Rempt
https://bugs.kde.org/show_bug.cgi?id=456201

--- Comment #2 from Halla Rempt  ---
After unzipping and removing the file layer, I can load the file, but
right-clicking on the frame group layer doesn't lead to a crash anymore.

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

[digikam] [Bug 456202] New: Browsing behaviour - selected picture when changing pane

2022-07-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=456202

Bug ID: 456202
   Summary: Browsing behaviour - selected picture when changing
pane
   Product: digikam
   Version: 7.7.0
  Platform: unspecified
OS: Microsoft Windows
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Thumbs-IconView
  Assignee: digikam-bugs-n...@kde.org
  Reporter: paolo.dellu...@yahoo.it
  Target Milestone: ---

SUMMARY
in the DAMs I used before, the same picture stayed selected no matter where I
went: albums, folders etc.
Here if I scroll to a certain picture in an "Album" (folder) and then select
e.g. the "Date" pane, it goes back to the last position I was in when browsing
that pane.
The rationale is that I want to go from a specific camera to all pictures taken
with different cameras in the same moment, or viceversa. It is particularly
useful when browsing in a view with few photos and then going in a view that
holds a lot of them.


STEPS TO REPRODUCE
1. Click on "Album" in the left pane
2. Scroll to desired picture, select it
3. Click on "Date", or "Timeline"

OBSERVED RESULT
The picture that is selecte is the one that was last selected when using that
particular view

EXPECTED RESULT
The selected picture should be the one I selected in the other pane, or at
least an option should exist to make the program do that.

SOFTWARE/OS VERSIONS
Windows: 7.7.0, but was the same on 7.6.0 and 7.5.0
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
This is the default behaviour in LR, for instance.

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

[lattedock] [Bug 456199] Panel indicator line remain when panel is hidden or visible

2022-07-01 Thread Alvaro
https://bugs.kde.org/show_bug.cgi?id=456199

Alvaro  changed:

   What|Removed |Added

 Blocks||456203


Referenced Bugs:

https://bugs.kde.org/show_bug.cgi?id=456203
[Bug 456203] Panel indicator line is shown in the wrong place
-- 
You are receiving this mail because:
You are watching all bug changes.

[lattedock] [Bug 456203] New: Panel indicator line is shown in the wrong place

2022-07-01 Thread Alvaro
https://bugs.kde.org/show_bug.cgi?id=456203

Bug ID: 456203
   Summary: Panel indicator line is shown in the wrong place
   Product: lattedock
   Version: 0.10.8
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: panabu...@gmail.com
CC: mvourla...@gmail.com, panabu...@gmail.com
Depends on: 456199
  Target Milestone: ---

Created attachment 150317
  --> https://bugs.kde.org/attachment.cgi?id=150317&action=edit
Issue Video

SUMMARY
***
When I move the pointer to where the panel is, it isn't showing the panel
indicator line in the place it suppose to be, instead it will show above of it
***
I'm attaching a video with the problem that it will explain better for itself



STEPS TO REPRODUCE
1. Move  the pointer where the panel is to make it visible
2. Make the panel visible

OBSERVED RESULT
Panel indicator line isn't where the panel is

EXPECTED RESULT
Panel indicator line should be where the panel is

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.18.6-1-MANJARO (64-bit)
KDE Plasma Version: 5.24.1
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.5

ADDITIONAL INFORMATION
Graphics Platform: X11


Referenced Bugs:

https://bugs.kde.org/show_bug.cgi?id=456199
[Bug 456199] Panel indicator line remain when panel is hidden or visible
-- 
You are receiving this mail because:
You are watching all bug changes.

[lattedock] [Bug 456203] Panel indicator line is shown in the wrong place

2022-07-01 Thread Alvaro
https://bugs.kde.org/show_bug.cgi?id=456203

--- Comment #1 from Alvaro  ---
Created attachment 150318
  --> https://bugs.kde.org/attachment.cgi?id=150318&action=edit
Panel

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

[kdeconnect] [Bug 452002] KDE Connect reports an error when logging into the system.

2022-07-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=452002

--- Comment #2 from ironman...@naver.com ---
Created attachment 150319
  --> https://bugs.kde.org/attachment.cgi?id=150319&action=edit
New crash information added by DrKonqi

kdeconnectd (21.12.3) using Qt 5.15.3

KDE Connect crashes on startup, not always, but very often. Although restarting
KDE Connect afterward works fine

-- Backtrace (Reduced):
#4  0x7f4386708d34 in (anonymous namespace)::constData (d=...) at
kernel/qvariant.cpp:361
#5  qVariantToHelper > (handlerManager=,
d=) at kernel/qvariant.cpp:2669
#6  QVariant::toMap() const (this=0x5612ec6d54f8) at kernel/qvariant.cpp:2721
#7  0x7f437857f7a8 in ConnectivityReportPlugin::receivePacket(NetworkPacket
const&) (np=, this=) at
./plugins/connectivity-report/connectivity_reportplugin.cpp:44
#8  ConnectivityReportPlugin::receivePacket(NetworkPacket const&)
(this=, np=) at
./plugins/connectivity-report/connectivity_reportplugin.cpp:40

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

[kdeconnect] [Bug 452002] KDE Connect reports an error when logging into the system.

2022-07-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=452002

ironman...@naver.com changed:

   What|Removed |Added

 CC||ironman...@naver.com

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

[krita] [Bug 453243] Canvas projection often isn't updated properly after undoing/redoing

2022-07-01 Thread Halla Rempt
https://bugs.kde.org/show_bug.cgi?id=453243

Halla Rempt  changed:

   What|Removed |Added

 CC||ha...@valdyas.org

--- Comment #2 from Halla Rempt  ---
I don't think it actually is a regression, though...

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

[krita] [Bug 453243] Canvas projection often isn't updated properly after undoing/redoing

2022-07-01 Thread Halla Rempt
https://bugs.kde.org/show_bug.cgi?id=453243

Halla Rempt  changed:

   What|Removed |Added

  Component|General |Layer Stack

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

[kdeconnect] [Bug 449276] kdeconnectd intermittent crash while in the background

2022-07-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=449276

ironman...@naver.com changed:

   What|Removed |Added

 CC||ironman...@naver.com

--- Comment #21 from ironman...@naver.com ---
Created attachment https://bugsfiles.kde.org/attachment.cgi?id=150319
It was originally reported to other thread, but I'm re-reporting it here, as
the other thread is marked as duplicate
Below is original contents from the other thread

kdeconnectd (21.12.3) using Qt 5.15.3

KDE Connect crashes on startup, not always, but very often. Although restarting
KDE Connect afterward works fine

-- Backtrace (Reduced):
#4  0x7f4386708d34 in (anonymous namespace)::constData (d=...) at
kernel/qvariant.cpp:361
#5  qVariantToHelper > (handlerManager=,
d=) at kernel/qvariant.cpp:2669
#6  QVariant::toMap() const (this=0x5612ec6d54f8) at kernel/qvariant.cpp:2721
#7  0x7f437857f7a8 in ConnectivityReportPlugin::receivePacket(NetworkPacket
const&) (np=, this=) at
./plugins/connectivity-report/connectivity_reportplugin.cpp:44
#8  ConnectivityReportPlugin::receivePacket(NetworkPacket const&)
(this=, np=) at
./plugins/connectivity-report/connectivity_reportplugin.cpp:40

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

[krita] [Bug 453243] Canvas projection often isn't updated properly after undoing/redoing

2022-07-01 Thread Halla Rempt
https://bugs.kde.org/show_bug.cgi?id=453243

Halla Rempt  changed:

   What|Removed |Added

   Assignee|krita-bugs-n...@kde.org |dimul...@gmail.com
 Status|REPORTED|ASSIGNED
 Ever confirmed|0   |1

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

[krita] [Bug 453243] Canvas projection often isn't updated properly after undoing/redoing

2022-07-01 Thread Halla Rempt
https://bugs.kde.org/show_bug.cgi?id=453243

Halla Rempt  changed:

   What|Removed |Added

  Component|Layer Stack |OpenGL Canvas

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

[konsole] [Bug 455166] URL matching regressions

2022-07-01 Thread SvenK
https://bugs.kde.org/show_bug.cgi?id=455166

SvenK  changed:

   What|Removed |Added

 CC||sv...@svenk.org

--- Comment #9 from SvenK  ---
Another annoying thing which recently changed is that URLs
http://127.0.0.1:4000/  used to be properly parsed but now are interpreted as
http://127.0.0.1, i.e. the port is missing. These kind of URLs typically appear
in static site generators, kubernetes, etc.

See also ticket https://bugs.kde.org/show_bug.cgi?id=430938 which proposes
regexpes to fix this on a personal level.

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

[kdeconnect] [Bug 449276] kdeconnectd intermittent crash while in the background

2022-07-01 Thread 林博仁
https://bugs.kde.org/show_bug.cgi?id=449276

--- Comment #22 from 林博仁(Buo-ren, Lin)  ---
(In reply to ironman466 from comment #21)
> Created attachment https://bugsfiles.kde.org/attachment.cgi?id=150319
> It was originally reported to other thread, but I'm re-reporting it here, as
> the other thread is marked as duplicate

As the code is already fixed upstream, you should instead notify the downstream
distribution to backport the patch.

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

[kmymoney] [Bug 451677] crashes on new category with a double colon

2022-07-01 Thread Thomas Baumgart
https://bugs.kde.org/show_bug.cgi?id=451677

Thomas Baumgart  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/offi
   ||ce/kmymoney/commit/6c446284
   ||b68bc96cef7b4e9a3d1100f3f7c
   ||f6de0
 Status|REPORTED|RESOLVED
   Version Fixed In||5.1.3

--- Comment #2 from Thomas Baumgart  ---
Git commit 6c446284b68bc96cef7b4e9a3d1100f3f7cf6de0 by Thomas Baumgart.
Committed on 01/07/2022 at 10:36.
Pushed by tbaumgart into branch '5.1'.

Prevent to create a category with a double colon in the name
FIXED-IN: 5.1.3

M  +18   -17   kmymoney/dialogs/knewaccountdlg.cpp
M  +1-1kmymoney/widgets/kmymoneyselector.cpp

https://invent.kde.org/office/kmymoney/commit/6c446284b68bc96cef7b4e9a3d1100f3f7cf6de0

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

[digikam] [Bug 456202] Browsing behaviour - selected picture when changing pane

2022-07-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=456202

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com
   Platform|unspecified |Microsoft Windows

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

[konsole] [Bug 456204] New: Zmodem receive feature doesn't work

2022-07-01 Thread Li-Wen Hsu
https://bugs.kde.org/show_bug.cgi?id=456204

Bug ID: 456204
   Summary: Zmodem receive feature doesn't work
   Product: konsole
   Version: 22.04.2
  Platform: Other
OS: FreeBSD
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: lwhsu@lwhsu.org
  Target Milestone: ---

SUMMARY

When downloading a file from remote machine with zmodem, there is no window
pops out and asks where to save file.

STEPS TO REPRODUCE
1. Use konsole and ssh login a remove machine
2. Use lsz to send a file with zmodem

OBSERVED RESULT
Session is blocking.

EXPECTED RESULT
A windows pops out and ask where to save file.

SOFTWARE/OS VERSIONS
FreeBSD: 13.1-RELEASE
(available in About System)
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.94.0
Qt Version: 5.15

ADDITIONAL INFORMATION
Reverting
https://invent.kde.org/utilities/konsole/-/commit/5557840822b193d1df48c145e3f1182993a30632
restores the old behavior.

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

[kdesrc-build] [Bug 456205] New: Add build / initial-setup support for Linux Mint: "kdesrc-build does not know your distribution (linuxmint)"

2022-07-01 Thread Pe Ta
https://bugs.kde.org/show_bug.cgi?id=456205

Bug ID: 456205
   Summary: Add build / initial-setup support for Linux Mint:
"kdesrc-build does not know your distribution
(linuxmint)"
   Product: kdesrc-build
   Version: Git
  Platform: Mint (Ubuntu based)
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: setup wizard
  Assignee: mp...@kde.org
  Reporter: p@tandlers.de
  Target Milestone: ---

I tried to start KDE development and followed the instructions at
https://community.kde.org/Get_Involved/development
but `kdesrc-build` complains that it does not know linuxmint as distribution.

```zsh
❯ ./kdesrc-build --initial-setup
 - Installing system packages for linuxmint...
Installing packages for linux/20.3
 * Packages could not be installed, because kdesrc-build does not know your
distribution (linuxmint)
```

I did not look at the source yet, but I expect that Mint is kind of similar to
ubuntu, so the ubuntu way should quite likely work.

```zsh
❯ cat /etc/os-release
NAME="Linux Mint"
VERSION="20.3 (Una)"
ID=linuxmint
ID_LIKE=ubuntu
PRETTY_NAME="Linux Mint 20.3"
VERSION_ID="20.3"
HOME_URL="https://www.linuxmint.com/";
SUPPORT_URL="https://forums.linuxmint.com/";
BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/";
PRIVACY_POLICY_URL="https://www.linuxmint.com/";
VERSION_CODENAME=una
UBUNTU_CODENAME=focal
```
SOFTWARE/OS VERSIONS

kdesrc-build: commit 5311b64bdaf70fe16d506a8baa16ad527b9a (HEAD -> master,
origin/master, origin/HEAD)
Date:   Mon Jun 27 00:46:45 2022 +

Operating System: Linux Mint 20.3
KDE Plasma Version: 5.18.8
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8
Kernel Version: 5.13.0-51-generic
OS Type: 64-bit

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

[kdesrc-build] [Bug 456205] Add build / initial-setup support for Linux Mint: "kdesrc-build does not know your distribution (linuxmint)"

2022-07-01 Thread Peta
https://bugs.kde.org/show_bug.cgi?id=456205

Peta  changed:

   What|Removed |Added

 CC||p@tandlers.de

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

[valgrind] [Bug 456200] Valgrind should not required neon (simd) on armhf

2022-07-01 Thread Mathieu Malaterre
https://bugs.kde.org/show_bug.cgi?id=456200

--- Comment #2 from Mathieu Malaterre  ---
Correction, the actual patch should be:

sed -i -e 's/cortex-a8/generic-armv7-a/g' Makefile.all.am

There's no need for the fpu selection to be specified as generic-armv7-a
defaults to vfpv3-d16.

Credits:
Richard Earnshaw 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928224#60

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

[lattedock] [Bug 453363] [wayland] latte crashes on wayland when turn on external monitor: a TV connected via HDMI

2022-07-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=453363

--- Comment #18 from cellst...@gmail.com ---
(In reply to Michail Vourlakos from comment #17)
> 
> *** This bug has been marked as a duplicate of bug 451028 ***

I understand policies, but policies cannot hinder workflow with unreasonable
request from end-users.
Otherwise the end result is that bugs will stay in the application unresolved,
even if reported.
kde bugtracker happily accepted my bug report and confirmed, latter-dock bug
tracker did not.

This is wasting people time (yours and mine) with unreasonable request.
Maybe its time to review some of the policies.

best of luck

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

[valgrind] [Bug 456200] Valgrind should not require neon (simd) on armhf

2022-07-01 Thread Mathieu Malaterre
https://bugs.kde.org/show_bug.cgi?id=456200

Mathieu Malaterre  changed:

   What|Removed |Added

Summary|Valgrind should not |Valgrind should not require
   |required neon (simd) on |neon (simd) on armhf
   |armhf   |

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

[lattedock] [Bug 456199] Panel indicator line remain when panel is hidden or visible

2022-07-01 Thread Michail Vourlakos
https://bugs.kde.org/show_bug.cgi?id=456199

Michail Vourlakos  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |UPSTREAM

--- Comment #1 from Michail Vourlakos  ---
this is  a kwin issue. Latte is not responsible for that line

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

[lattedock] [Bug 456203] Panel indicator line is shown in the wrong place

2022-07-01 Thread Michail Vourlakos
https://bugs.kde.org/show_bug.cgi?id=456203
Bug 456203 depends on bug 456199, which changed state.

Bug 456199 Summary: Panel indicator line remain when panel is hidden or visible
https://bugs.kde.org/show_bug.cgi?id=456199

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |UPSTREAM

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

[kmymoney] [Bug 450426] OFX import is broken on MS-Windows

2022-07-01 Thread Dawid Wróbel
https://bugs.kde.org/show_bug.cgi?id=450426

--- Comment #31 from Dawid Wróbel  ---
> I have no problem with introducing a new build system, but TEST, TEST, TEST !
> And it's not like there are not oodles of tools available nowadays to
> automate the testing either.
> 
>   *   Run unit tests
>   *   Automated deploys to a build server
>   *   Virtual guests for testing on other platforms

You realize how condescending you sound? Like we don't know these tools? I made
it pretty clear we do this in our free time, as in: time is the factor here,
not knowledge, which you so happily imply.

Please, do not comment back here unless you have something helpful to add.

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

[lattedock] [Bug 456199] Panel indicator line remain when panel is hidden or visible

2022-07-01 Thread Alvaro
https://bugs.kde.org/show_bug.cgi?id=456199

--- Comment #2 from Alvaro  ---
(In reply to Michail Vourlakos from comment #1)
> this is  a kwin issue. Latte is not responsible for that line

But Latte is directly interacting with it, isn't? Should I report a kwin issue?

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

[lattedock] [Bug 456199] Panel indicator line remain when panel is hidden or visible

2022-07-01 Thread Michail Vourlakos
https://bugs.kde.org/show_bug.cgi?id=456199

--- Comment #3 from Michail Vourlakos  ---
(In reply to Alvaro from comment #2)
> (In reply to Michail Vourlakos from comment #1)
> > this is  a kwin issue. Latte is not responsible for that line
> 
> But Latte is directly interacting with it, isn't? Should I report a kwin
> issue?

there is already a kwin issue but I dont remember its id

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

[kwin] [Bug 455814] Display will not wake from DPMS since 5.25 (Wayland Nvidia)

2022-07-01 Thread Andrej Halveland
https://bugs.kde.org/show_bug.cgi?id=455814

Andrej Halveland  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/plas
   ||ma/kwin/-/merge_requests/25
   ||99/diffs?commit_id=ad7b90ef
   ||437c621dff993ea9bc6120ba64d
   ||bccd5

--- Comment #12 from Andrej Halveland  ---
The merge request @ https://invent.kde.org/plasma/kwin/-/merge_requests/2599
did indeed fix the issue for me.

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

[kdesrc-build] [Bug 456205] Add build / initial-setup support for Linux Mint: "kdesrc-build does not know your distribution (linuxmint)"

2022-07-01 Thread Peta
https://bugs.kde.org/show_bug.cgi?id=456205

--- Comment #1 from Peta  ---
Hm, found that in
https://invent.kde.org/sdk/kdesrc-build/-/blob/master/modules/ksb/FirstRun.pm#L388
the distros are listed
Without having verified, I would expect that ubuntu has ID_LIKE=debian

Now, Linux Mint points the ID_LIKE to ubuntu, but not to debian. I guess that's
why it fails. There is no double redirect supported by `/etc/os-release`, so a
manual work-around is required.

Is  debian supported? #L389 "# This is woefully incomplete and not very
useful."

Seems to be related to https://invent.kde.org/sdk/kdesrc-build/-/issues/89

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

[plasma-pa] [Bug 455283] plasma-pa 5.25.0 applet hides virtual devices by default

2022-07-01 Thread Alexandre CATTEAU
https://bugs.kde.org/show_bug.cgi?id=455283

Alexandre CATTEAU  changed:

   What|Removed |Added

 CC||alexandre.catt...@gmail.com

--- Comment #5 from Alexandre CATTEAU  ---
Just to add another use case where virtual devices are useful in applet: I use
pulseaudio-dlna to add virtual audio devices corresponding to DLNA renderers
(or "players") on local network. It allows for example to punctually move an
audio source to an output device in another room. And doing so with the
drag'n'drop feature of the applet is just perfect. ;)

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

[kio-extras] [Bug 456206] New: SEGFAULT in kioslave5 when navigating to "man:re_syntax(n)" page

2022-07-01 Thread Igor Kushnir
https://bugs.kde.org/show_bug.cgi?id=456206

Bug ID: 456206
   Summary: SEGFAULT in kioslave5 when navigating to
"man:re_syntax(n)" page
   Product: kio-extras
   Version: 22.04.2
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: default
  Assignee: plasma-b...@kde.org
  Reporter: igor...@gmail.com
  Target Milestone: ---

SUMMARY
Loading the "re_syntax(n)" man page in KHelpCenter or KDevelop consistently
crashes kioslave5. Many (all?) other man pages are loaded correctly.

STEPS TO REPRODUCE
1. Open KHelpCenter and search for "re_syntax".
2. Click the found link: "re_syntax(n) - Syntax of Tcl regular expressions".

OBSERVED RESULT
1. "kioslave5 - The KDE Crash Handler" drkonqi  window appears.
2. KHelpCenter displays "The requested operation could not be completed
Unexpected Program Termination" page.

EXPECTED RESULT
The "re_syntax(n)" man page is loaded without errors.

SOFTWARE/OS VERSIONS
Manjaro GNU/Linux, Xfce, with latest updates
KDE Frameworks Version: 5.95
Qt Version: 5.15.5+kde

BACKTRACE
Application: kioslave5 (kioslave5), signal: Segmentation fault

[KCrash Handler]
#4  0x7ff16f6bf1b2 in QVector::resize (this=this@entry=0x7ff16f6db0d8
, asize=-1) at /usr/include/qt/QtCore/qvector.h:437
#5  0x7ff16f6b6867 in QStack::pop (this=0x7ff16f6db0d8 )
at /usr/include/qt/QtCore/qstack.h:63
#6  scan_request (c=c@entry=0x561c30dee108 "el .ds qo u\n.TH re_syntax n
\"8.1\" Tcl \"Tcl Built-In Commands\"\n.BS\n.SH NAME\nre_syntax \\- Syntax of
Tcl regular expressions\n.BE\n.SH DESCRIPTION\n.PP\nA \\fIregular
expression\\fR describes strings of charac"...) at
/usr/src/debug/kio-extras-22.04.2/man/man2html.cpp:3863
#7  0x7ff16f6b21e1 in scan_troff (c=c@entry=0x561c30dee0e7
"\\w\no''\\w'\\C'^o''' .ds qo \\C'^o'\n.el .ds qo u\n.TH re_syntax n \"8.1\"
Tcl \"Tcl Built-In Commands\"\n.BS\n.SH NAME\nre_syntax \\- Syntax of Tcl
regular expressions\n.BE\n.SH DESCRIPTION\n.PP\nA \\fIregular expressi"...,
san=san@entry=true, result=result@entry=0x7ffd96a72228) at
/usr/src/debug/kio-extras-22.04.2/man/man2html.cpp:5852
#8  0x7ff16f6b346e in scan_expression (c=0x561c30dee0e9 "\no''\\w'\\C'^o'''
.ds qo \\C'^o'\n.el .ds qo u\n.TH re_syntax n \"8.1\" Tcl \"Tcl Built-In
Commands\"\n.BS\n.SH NAME\nre_syntax \\- Syntax of Tcl regular
expressions\n.BE\n.SH DESCRIPTION\n.PP\nA \\fIregular expression"...,
c@entry=0x561c30dee0e6 "'\\w\no''\\w'\\C'^o''' .ds qo \\C'^o'\n.el .ds qo
u\n.TH re_syntax n \"8.1\" Tcl \"Tcl Built-In Commands\"\n.BS\n.SH
NAME\nre_syntax \\- Syntax of Tcl regular expressions\n.BE\n.SH
DESCRIPTION\n.PP\nA \\fIregular express"...,
result=result@entry=0x7ffd96a722c8, numLoop=numLoop@entry=0) at
/usr/src/debug/kio-extras-22.04.2/man/man2html.cpp:2812
#9  0x7ff16f6b62a9 in scan_expression (result=0x7ffd96a722c8,
c=0x561c30dee0e6 "'\\w\no''\\w'\\C'^o''' .ds qo \\C'^o'\n.el .ds qo u\n.TH
re_syntax n \"8.1\" Tcl \"Tcl Built-In Commands\"\n.BS\n.SH NAME\nre_syntax \\-
Syntax of Tcl regular expressions\n.BE\n.SH DESCRIPTION\n.PP\nA \\fIregular
express"...) at /usr/src/debug/kio-extras-22.04.2/man/man2html.cpp:2984
#10 scan_request (c=c@entry=0x561c30dee0e3 "ie '\\w\no''\\w'\\C'^o''' .ds qo
\\C'^o'\n.el .ds qo u\n.TH re_syntax n \"8.1\" Tcl \"Tcl Built-In
Commands\"\n.BS\n.SH NAME\nre_syntax \\- Syntax of Tcl regular
expressions\n.BE\n.SH DESCRIPTION\n.PP\nA \\fIregular expr"...) at
/usr/src/debug/kio-extras-22.04.2/man/man2html.cpp:3888
#11 0x7ff16f6b21e1 in scan_troff (c=c@entry=0x561c30dec941 "\n'\\\"\n'\\\"
Copyright (c) 1998 Sun Microsystems, Inc.\n'\\\" Copyright (c) 1999 Scriptics
Corporation\n'\\\"\n'\\\" See the file \"license.terms\" for information on
usage and redistribution\n'\\\" of this file, and f"..., san=san@entry=false,
result=result@entry=0x0) at
/usr/src/debug/kio-extras-22.04.2/man/man2html.cpp:5852
#12 0x7ff16f6bd0ec in scan_man_page (man_page=man_page@entry=0x561c30e29df0
"\n'\\\"\n'\\\" Copyright (c) 1998 Sun Microsystems, Inc.\n'\\\" Copyright (c)
1999 Scriptics Corporation\n'\\\"\n'\\\" See the file \"license.terms\" for
information on usage and redistribution\n'\\\" of this file, and f"...) at
/usr/src/debug/kio-extras-22.04.2/man/man2html.cpp:6086
#13 0x7ff16f6cc8ef in MANProtocol::get (this=0x7ffd96a72930, url=...) at
/usr/src/debug/kio-extras-22.04.2/man/kio_man.cpp:503
#14 0x7ff1749d8046 in KIO::SlaveBase::dispatch(int, QByteArray const&) ()
from /usr/lib/libKF5KIOCore.so.5
#15 0x7ff1749d00ae in KIO::SlaveBase::dispatchLoop() () from
/usr/lib/libKF5KIOCore.so.5
#16 0x7ff16f6c5fac in kdemain (argc=, argv=0x7ffd96a72a70)
at /usr/src/debug/kio-extras-22.04.2/man/kio_man.cpp:746
#17 0x561c304a5207 in ?? ()
#18 0x7ff17424e290 in ?? () from /usr/lib/libc.so.6
#19 0x7ff17424e34a in __libc_start_main () from /usr/lib/libc.so.6
#20 0x561c304a5465 in ?? ()
[Inferior 1 (

[kde] [Bug 456207] New: KTorrent crashes when clicking "Continue" after being informed that a certificate is not verifyable

2022-07-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=456207

Bug ID: 456207
   Summary: KTorrent crashes when clicking "Continue" after being
informed that a certificate is not verifyable
   Product: kde
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: 847...@gmail.com
  Target Milestone: ---

Application: ktorrent (21.12.3)

Qt Version: 5.15.3
Frameworks Version: 5.92.0
Operating System: Linux 5.15.0-40-generic x86_64
Windowing System: X11
Distribution: Ubuntu 22.04 LTS
DrKonqi: 5.24.4 [KCrashBackend]

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

Apparently I use a torrent containing some sort of certificate. KTorrent warns
me in a popup-window (which always appears after some time), that the
certificate cannot be verified. When I click "Continue" the program crashes
immediately.

I will update this report with more information the next time I encounter the
popup.

The crash can be reproduced every time.

-- Backtrace:
Application: KTorrent (ktorrent), signal: Segmentation fault

[KCrash Handler]
#4  0x7f893619e77e in KIO::SlaveInterface::d_func (this=) at
./src/core/slaveinterface.h:202
#5  KIO::SlaveInterface::sendMessageBoxAnswer (this=0x0, result=result@entry=4)
at ./src/core/slaveinterface.cpp:380
#6  0x7f8936152b66 in KIO::UserNotificationHandler::processRequest
(this=) at ./src/core/usernotificationhandler.cpp:94
#7  0x7f8934ada40e in QObject::event (this=0x7f8936287180 <(anonymous
namespace)::Q_QGS_globalUserNotificationHandler::innerFunction()::holder>,
e=0x560b687798f0) at kernel/qobject.cpp:1314
#8  0x7f893559c713 in QApplicationPrivate::notify_helper (this=, receiver=0x7f8936287180 <(anonymous
namespace)::Q_QGS_globalUserNotificationHandler::innerFunction()::holder>,
e=0x560b687798f0) at kernel/qapplication.cpp:3637
#9  0x7f8934aace2a in QCoreApplication::notifyInternal2
(receiver=0x7f8936287180 <(anonymous
namespace)::Q_QGS_globalUserNotificationHandler::innerFunction()::holder>,
event=0x560b687798f0) at kernel/qcoreapplication.cpp:1064
#10 0x7f8934aaff17 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x560b65391c40) at
kernel/qcoreapplication.cpp:1821
#11 0x7f8934b06a57 in postEventSourceDispatch (s=0x560b654e8b70) at
kernel/qeventdispatcher_glib.cpp:277
#12 0x7f8932f53d1b in g_main_dispatch (context=0x7f8928005010) at
../../../glib/gmain.c:3417
#13 g_main_context_dispatch (context=0x7f8928005010) at
../../../glib/gmain.c:4135
#14 0x7f8932fa86f8 in g_main_context_iterate.constprop.0
(context=context@entry=0x7f8928005010, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4211
#15 0x7f8932f513c3 in g_main_context_iteration (context=0x7f8928005010,
may_block=1) at ../../../glib/gmain.c:4276
#16 0x7f8934b060a8 in QEventDispatcherGlib::processEvents
(this=0x560b654ed6a0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#17 0x7f8934aab74b in QEventLoop::exec (this=this@entry=0x7ffc6f8e3bb0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#18 0x7f8934ab3ce4 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#19 0x560b63c538b8 in ?? ()
#20 0x7f89342bfd90 in __libc_start_call_main
(main=main@entry=0x560b63c4eba0, argc=argc@entry=1,
argv=argv@entry=0x7ffc6f8e4278) at ../sysdeps/nptl/libc_start_call_main.h:58
#21 0x7f89342bfe40 in __libc_start_main_impl (main=0x560b63c4eba0, argc=1,
argv=0x7ffc6f8e4278, init=, fini=,
rtld_fini=, stack_end=0x7ffc6f8e4268) at ../csu/libc-start.c:392
#22 0x560b63c552c5 in ?? ()
[Inferior 1 (process 173113) detached]

Possible duplicates by query: bug 453820, bug 452654, bug 449121, bug 449120,
bug 443666.

Reported using DrKonqi
This report was filed against 'kde' because the product 'ktorrent' could not be
located in Bugzilla. Add it to drkonqi's mappings file!

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

[frameworks-kxmlgui] [Bug 456208] New: KMainWindow saves auto settings too often: this can freeze applications

2022-07-01 Thread Amaury Pouly
https://bugs.kde.org/show_bug.cgi?id=456208

Bug ID: 456208
   Summary: KMainWindow saves auto settings too often: this can
freeze applications
   Product: frameworks-kxmlgui
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: amaury.po...@gmail.com
  Target Milestone: ---

Created attachment 150320
  --> https://bugs.kde.org/attachment.cgi?id=150320&action=edit
example code to reproduce

DISCLAIMER:

I don't know if this qualifies as a "bug" or not, but I think it does highlight
a problem either with the framework or with users of the framework. This
"problem" explains https://bugs.kde.org/show_bug.cgi?id=451059

SUMMARY

KMainWindow saves the auto settings on various event. Most problematic is that
it triggers a save on many visibility events:
https://github.com/KDE/kdelibs/blob/1c5b25966136b6099665477616fb4d38a98fd7ef/kdeui/widgets/kmainwindow.cpp

In most cases, this is not an issue except under this, unfortunately not
uncommon, situation: switching virtual desktops of many windows using the same
config file. More precisely, assume N windows of the same application (for
example okular) are in a first desktop. All those windows share the same
configuration file. If one switching virtual desktop for example, potentially
all N windows will receive a visibility event notification. Hence all will
trigger the setSettingsDirty(), which will launch a timeout that will
eventually saveAutoSaveSettings(). This will .sync() on the autoSaveGroup. The
sync() will all happen almost at the same time and, eventually, all N-1 of them
will block in QLockFile trying to acquire a lock. The logic in QLockFile
(qtbase/src/corelib/io/qlockfile.cpp) doubles the timer every times it fails.
This means that in the unlucky, but not so rare event, where every process
blocks, this will wait 2^N*100 ms. In practice, I have managed to reach more
than 5 seconds freezes with 10 windows. There might be other ways the auto
settings are saved, I think what I described above is correct, based on playing
around with gdb.

A caveat is that the settings are saved only if something changed (ie settings
are dirty). Simply moving a window is sufficient. For a more complex UI such as
the one used by okular, it seems that simply switching desktops is sufficient
to makes settings dirty, I am not entirely sure why/how.

To simplify the reproducibility of this problem, I have written a trivial
application (attached). It runs a timer and measures when the timer is not
called then prints a message. Since the saving codes runs on the main thread,
blocking on QLockFile freezes the main thread and prevents from dispatching the
timer event.

STEPS TO REPRODUCE
1. compile the application: cmake -G 'Unix Makefiles' && make
2. run 10 copies of the application: 
 for i in {1..10}; do ./example_bug& done
3. This should already print some very large delays, showing that the saving
mecanism triggers some long waits
4. Manually move each of the windows
5. Switching to another virtual desktop and switch back
6. This should print some huge delays
7. close all windows: kilall example_bug

OBSERVED RESULT

Some windows freezes for 5seconds or more, here is the output:
time elapsed: 212 ms
time elapsed: 233 ms
time elapsed: 285 ms
time elapsed: 300 ms
time elapsed: 384 ms
time elapsed: 201 ms
time elapsed: 387 ms
time elapsed: 386 ms
time elapsed: 406 ms
time elapsed: 806 ms
time elapsed: 1619 ms
time elapsed: 3209 ms
time elapsed: 6412 ms

EXPECTED RESULT

Windows should not freeze.

ADDITIONAL INFORMATION
I have not specified any version for Qt/KDE because based on the source code of
kmainwindow, I suspect this has been an issue for a long time. Any recent
version of Qt/KF5 will trigger this issue.

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

[kwin] [Bug 437089] On Wayland, Windows that were closed when maximized will open in the maximized position, but not the maximized state

2022-07-01 Thread soredake
https://bugs.kde.org/show_bug.cgi?id=437089

soredake  changed:

   What|Removed |Added

 CC||ndrzj1...@relay.firefox.com

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

[ktorrent] [Bug 456207] KTorrent crashes when clicking "Continue" after being informed that a certificate is not verifyable

2022-07-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=456207

847...@gmail.com changed:

   What|Removed |Added

  Component|general |general
Version|unspecified |21.12.3
   Assignee|unassigned-b...@kde.org |joris.guis...@gmail.com
Product|kde |ktorrent

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

[kwin] [Bug 392375] Restored sessions with maximized windows does not remember their unmaximized size

2022-07-01 Thread soredake
https://bugs.kde.org/show_bug.cgi?id=392375

soredake  changed:

   What|Removed |Added

 CC||ndrzj1...@relay.firefox.com

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

[kwin] [Bug 434116] De-maximizing a window that was maximized on launch positions it according to the placement mode even if the window wants to position itself

2022-07-01 Thread soredake
https://bugs.kde.org/show_bug.cgi?id=434116

soredake  changed:

   What|Removed |Added

 CC||ndrzj1...@relay.firefox.com

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

[frameworks-knotifications] [Bug 456178] [Feature request] Add option to select monitor to display notifications

2022-07-01 Thread Nicolas Fella
https://bugs.kde.org/show_bug.cgi?id=456178

Nicolas Fella  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE
 CC||nicolas.fe...@gmx.de

--- Comment #1 from Nicolas Fella  ---


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

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

[plasmashell] [Bug 446961] Add option to select screen in custom notification positioning UI

2022-07-01 Thread Nicolas Fella
https://bugs.kde.org/show_bug.cgi?id=446961

Nicolas Fella  changed:

   What|Removed |Added

 CC||linx.system@gmail.com

--- Comment #6 from Nicolas Fella  ---
*** Bug 456178 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 456178] [Feature request] Add option to select monitor to display notifications

2022-07-01 Thread Nicolas Fella
https://bugs.kde.org/show_bug.cgi?id=456178

Nicolas Fella  changed:

   What|Removed |Added

Product|frameworks-knotifications   |plasmashell
Version|unspecified |5.25.2
  Component|general |Notifications
   Assignee|kdelibs-b...@kde.org|plasma-b...@kde.org
 CC||k...@privat.broulik.de
   Target Milestone|--- |1.0

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

[krita] [Bug 455570] Krita plus 5.1.0 prealpha : complex brush outline causes intolerable performance lag

2022-07-01 Thread stephen
https://bugs.kde.org/show_bug.cgi?id=455570

--- Comment #16 from stephen  ---
(In reply to Dmitry Kazakov from comment #15)
> Hi, Stephen!
> 
> I have fixed the problem that was triggered by the "moo bubble" brush. That
> stutter should go now. Though I haven't even checked the part of the bug
> that is related to 1700px brushes, because Krita officially doesn't support
> brushes bigger that 1000px. Usage of such brushes is "at your own risk" :)

Thank you a lot Dmitry ! God blesses you!
Also good to know that Krita officially doesn't support brushes bigger than
1000 px.
I wasn't aware of that.

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

[kwin] [Bug 456133] Touching a running application in WindowHeap-based effects using a touchscreen doesn't switch to it

2022-07-01 Thread Vlad Zahorodnii
https://bugs.kde.org/show_bug.cgi?id=456133

Vlad Zahorodnii  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/plas
   ||ma/kwin/commit/56d3b2ddc44c
   ||5a3590bbfd4bb9dc6cdd4be853c
   ||0
 Status|ASSIGNED|RESOLVED

--- Comment #4 from Vlad Zahorodnii  ---
Git commit 56d3b2ddc44c5a3590bbfd4bb9dc6cdd4be853c0 by Vlad Zahorodnii, on
behalf of Marco Martin.
Committed on 01/07/2022 at 12:13.
Pushed by vladz into branch 'master'.

Set all timestamps for all touch events

in order for qml pointerhandlers to work correctly, they need
timestamps in all events (to decide for instance when to emit a
tapped or doubletapped)

M  +2-4src/libkwineffects/kwinoffscreenquickview.cpp

https://invent.kde.org/plasma/kwin/commit/56d3b2ddc44c5a3590bbfd4bb9dc6cdd4be853c0

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

[plasma-nm] [Bug 420237] Airplane mode cannot be toggled without Wi-Fi adapter

2022-07-01 Thread Alexandre CATTEAU
https://bugs.kde.org/show_bug.cgi?id=420237

Alexandre CATTEAU  changed:

   What|Removed |Added

Version|5.20.3  |5.25.2

--- Comment #2 from Alexandre CATTEAU  ---
Still present on:
Arch Linux
KDE Plasma Version: 5.25.2
KDE Frameworks Version: 5.95
Qt Version: 5.15.5

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

[kwin] [Bug 456133] Touching a running application in WindowHeap-based effects using a touchscreen doesn't switch to it

2022-07-01 Thread Vlad Zahorodnii
https://bugs.kde.org/show_bug.cgi?id=456133

Vlad Zahorodnii  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
   |ma/kwin/commit/56d3b2ddc44c |ma/kwin/commit/b079c8caa23f
   |5a3590bbfd4bb9dc6cdd4be853c |8b40733a45159f51607928596a4
   |0   |b

--- Comment #5 from Vlad Zahorodnii  ---
Git commit b079c8caa23f8b40733a45159f51607928596a4b by Vlad Zahorodnii, on
behalf of Marco Martin.
Committed on 01/07/2022 at 12:16.
Pushed by vladz into branch 'Plasma/5.25'.

Set all timestamps for all touch events

in order for qml pointerhandlers to work correctly, they need
timestamps in all events (to decide for instance when to emit a
tapped or doubletapped)


(cherry picked from commit 56d3b2ddc44c5a3590bbfd4bb9dc6cdd4be853c0)

M  +2-4src/libkwineffects/kwinoffscreenquickview.cpp

https://invent.kde.org/plasma/kwin/commit/b079c8caa23f8b40733a45159f51607928596a4b

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

[KScreen] [Bug 394930] Dual monitor setup remembered correctly after reboot, but applied wrongly

2022-07-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=394930

k...@zottel.net changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #6 from k...@zottel.net ---
(In reply to Nate Graham from comment #5)
> Does this still happen in Plasma 5.25? We did a lot of multimonitor
> robustness work in that release. Could you test? Thanks!

It works now, thanks!

Actually, it's been working for a few months now. I just updated to 5.25.2 and
it still works. :-)

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

[lattedock] [Bug 456141] [wayland / nvidia proprietary] latte-dock has intensive artfacts/strobes and hangs when adding default panel

2022-07-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=456141

--- Comment #7 from lankylonk...@gmail.com ---
(In reply to Michail Vourlakos from comment #6)
> waiting artifacts screenshot

it strobes, thus no ability to snap it

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

[xdg-desktop-portal-kde] [Bug 456055] ROBLOX ISNT WORKING :(

2022-07-01 Thread Nicolas Fella
https://bugs.kde.org/show_bug.cgi?id=456055

--- Comment #7 from Nicolas Fella  ---
Git commit 8c0c1f4b8e32546579c98dd6f9731c02a06f92be by Nicolas Fella.
Committed on 01/07/2022 at 12:13.
Pushed by nicolasfella into branch 'master'.

Don't treat KJob::UserDefinedError as unknown error

KIO's jobs use UserDefinedError in several places for errors where there is no
specific error code

When converting the error code to string it is treated as unknown, suggesting
to report a bug to bugs.kde.org

However, the way we use UserDefinedError it's not necessarily a KDE bug, we use
it for example when a desktop file's executable is not found

Instead treat it the same as ERR_SLAVE_DEFINED, i.e. show the message, but
without the special text around it

M  +2-0src/core/job_error.cpp

https://invent.kde.org/frameworks/kio/commit/8c0c1f4b8e32546579c98dd6f9731c02a06f92be

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

[lattedock] [Bug 456141] [wayland / nvidia proprietary] latte-dock has intensive artfacts/strobes and hangs when adding default panel

2022-07-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=456141

--- Comment #8 from lankylonk...@gmail.com ---
when the dock is appear or disappear, there is a flash occuping the lower end
of the screen, i reckon the more severe bug is when i add a panel the dock
instantly hangs

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

[lattedock] [Bug 456141] [wayland / nvidia proprietary] latte-dock has intensive artfacts/strobes and hangs when adding default panel

2022-07-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=456141

--- Comment #9 from lankylonk...@gmail.com ---
Created attachment 150321
  --> https://bugs.kde.org/attachment.cgi?id=150321&action=edit
when add a dock of panel, the dock hangs indefinitely

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

[Powerdevil] [Bug 451867] System no longer able to suspend after March 22 system update.

2022-07-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=451867

--- Comment #2 from lnx...@westlot.net ---
This is still an issue with the latest Neon kernel (5.13.0-52).  I again tried
all kernel updates between 0-35 and 0-52, and sleep does not work in any of
them.

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

[Elisa] [Bug 456209] New: Check description

2022-07-01 Thread Alex
https://bugs.kde.org/show_bug.cgi?id=456209

Bug ID: 456209
   Summary: Check description
   Product: Elisa
   Version: 22.04.2
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: baloo
  Assignee: matthieu_gall...@yahoo.fr
  Reporter: fworl...@protonmail.com
  Target Milestone: ---

Created attachment 150322
  --> https://bugs.kde.org/attachment.cgi?id=150322&action=edit
Video content - bugs of Elisa player

1. Bugs when I trying to select SINGLE track to play. Bug with a progress bar
when playing audio.

2. Bugs with navigation. All described in video. See attachments.

/* That's an excellent player, I want to use it for a long time. Please fix
this bugs in next releases. */

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

[Powerdevil] [Bug 451867] System no longer able to suspend after March 22 system update.

2022-07-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=451867

--- Comment #3 from lnx...@westlot.net ---
(In reply to lnxusr from comment #2)
> This is still an issue with the latest Neon kernel (5.13.0-52).  I again
> tried all kernel updates between 0-35 and 0-52, and sleep does not work in
> any of them.

Any other than 0-35, that is.

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

[konsole] [Bug 456204] Zmodem receive feature doesn't work

2022-07-01 Thread Tobias C. Berner
https://bugs.kde.org/show_bug.cgi?id=456204

Tobias C. Berner  changed:

   What|Removed |Added

 CC||tcber...@freebsd.org

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

[krita] [Bug 456201] Crash after a right click on a group layer

2022-07-01 Thread David REVOY
https://bugs.kde.org/show_bug.cgi?id=456201

--- Comment #3 from David REVOY  ---
Thank you. 

> [...] removing the file layer, I can load the file [...]

Here I can still open the file with 5.1(beta1)appimage even after moving it to
another directory (I'm prompted for the missing 'txt' layer too but I can skip
it). So, if you couldn't open this one, it might be another issue about reading
missing file layer.

> but right-clicking on the frame group layer doesn't lead to a crash anymore.

Good, maybe this right-click menu crash issue is fixed then in Git~master. I'll
try to test it with a recent build too.

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

[kdesrc-build] [Bug 456205] Add build / initial-setup support for Linux Mint: "kdesrc-build does not know your distribution (linuxmint)"

2022-07-01 Thread Harald Sitter
https://bugs.kde.org/show_bug.cgi?id=456205

Harald Sitter  changed:

   What|Removed |Added

 CC||sit...@kde.org

--- Comment #2 from Harald Sitter  ---
(In reply to Peta from comment #1)
> There is no double redirect supported by
> `/etc/os-release`, so a manual work-around is required.

ID_LIKE=

__A space-separated list of operating system identifiers__ in the same
syntax as the ID= setting. It should list identifiers of operating systems that
are closely related to the local operating system in regards to packaging and
programming interfaces, for example listing one or more OS identifiers the
local OS is a derivative from. An OS should generally only list other OS
identifiers it itself is a derivative of, and not any OSes that are derived
from it, though symmetric relationships are possible. Build scripts and similar
should check this variable if they need to identify the local operating system
and the value of ID= is not recognized. Operating systems should be listed in
order of how closely the local operating system relates to the listed ones,
starting with the closest. This field is optional.

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

[valgrind] [Bug 248998] ARMv5 and v6 support

2022-07-01 Thread Mathieu Malaterre
https://bugs.kde.org/show_bug.cgi?id=248998

Mathieu Malaterre  changed:

   What|Removed |Added

 CC||ma...@debian.org

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

[plasma-systemmonitor] [Bug 440234] Wish: Aggregations across apps/procs

2022-07-01 Thread Jan Molnar
https://bugs.kde.org/show_bug.cgi?id=440234

--- Comment #4 from Jan Molnar  ---
There is another use case: situations no one anticipated / not yet implemented.

Kubuntu 22.04 migrated Firefox from deb to snap and now it is _not_ displayed
in Applications, so I have no idea how much it consumes. The issue is primarily
elsewhere, Firefox should be displayed in applications, but such not
anticipated / not yet implemented things are common.

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

[kwin] [Bug 447840] Touchegg-provided gestures don't work in WindowHeap-based effects on X11 anymore

2022-07-01 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=447840

--- Comment #24 from Nate Graham  ---
See https://community.kde.org/Matrix and https://community.kde.org/Telegram

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

[kwin] [Bug 445877] Kickoff shows up in the bottom middle instead of bottom left corner (only with Wayland)

2022-07-01 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=445877

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #7 from Nate Graham  ---
Can anyone else (including the reporter) confirm that?

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

[plasmashell] [Bug 456128] Icon for Steam Proton Game appears in Task Switcher when clicking on OBS's System Tray icon

2022-07-01 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=456128

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #8 from Nate Graham  ---
Thanks. How strange.

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

[plasmashell] [Bug 456128] Icon for Steam Proton Game appears in Task Switcher when clicking on OBS's System Tray icon

2022-07-01 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=456128

Nate Graham  changed:

   What|Removed |Added

  Component|Task Manager and Icons-Only |XembedSNIProxy
   |Task Manager|
 CC||mate...@gmail.com

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

[kwin] [Bug 425327] No Border warning box still has placeholder string

2022-07-01 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=425327

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #4 from Nate Graham  ---
Can confirm that it's fixed now.

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

[kwin] [Bug 455992] spice-vdagentd/spice-vdagent does not start

2022-07-01 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=455992

--- Comment #10 from Nate Graham  ---
Ok. So how did you turn on autostart for the app? Something in the app itself?

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

[plasmashell] [Bug 455924] Plasmashell (KRunner/Kickoff) refuse to launch '.exe' files.

2022-07-01 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=455924

--- Comment #5 from Nate Graham  ---
Yeah, that's what we're trying to figure out how to do.

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

[kwin] [Bug 452786] WAYLAND - Secondary monitors show black screen, no wallpaper, no panels, and no windows. Only cursor.

2022-07-01 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=452786

--- Comment #8 from Nate Graham  ---
Hooray! Glad to hear it.

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

[KScreen] [Bug 394930] Dual monitor setup remembered correctly after reboot, but applied wrongly

2022-07-01 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=394930

--- Comment #7 from Nate Graham  ---
Hooray! Glad to hear it.

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

[konsole] [Bug 455166] URL matching regressions

2022-07-01 Thread Ahmad Samir
https://bugs.kde.org/show_bug.cgi?id=455166

--- Comment #10 from Ahmad Samir  ---
(In reply to SvenK from comment #9)
> Another annoying thing which recently changed is that URLs
> http://127.0.0.1:4000/  used to be properly parsed but now are interpreted
> as http://127.0.0.1, i.e. the port is missing. These kind of URLs typically
> appear in static site generators, kubernetes, etc.
> 

That is already fixed in master.

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

  1   2   3   >