[krita] [Bug 441940] The string "Export Directory :" in Storyboard docker's Export SVG dialogue is untranslatable

[Tyson Tan]

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

--- Comment #3 from Tyson Tan  ---
Thanks! I will internationalize that string today.

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

[lattedock] [Bug 442013] Dock/Panel set as Windows Can Cover hides like a window

[Michail Vourlakos]

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

Michail Vourlakos  changed:

   What|Removed |Added

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

--- Comment #1 from Michail Vourlakos  ---
nothing to do with Latte, you need to forward your request to plasma and kwin
if you want panels above specific fullscreen windows. Same thing should happen
with plasma panels also.

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

[plasmashell] [Bug 428999] Plasmashell is freezing when laptop is connected to an external monitor

[Christoph Schulz]

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

--- Comment #8 from Christoph Schulz  ---
After changing the setting to the non-threaded render loop, I haven't had any
freezes so far. Am I supposed to encounter any other problems with that setting
(with the exception of, say, performance issues)? Are there any known pitfalls?
Or can I simply use it "as is" without ever changing it back?

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

[krita] [Bug 441940] The string "Export Directory :" in Storyboard docker's Export SVG dialogue is untranslatable

[bugzilla_noreply]

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

tomtomtomreportin...@gmail.com changed:

   What|Removed |Added

 CC||tomtomtomreportingin@gmail.
   ||com

--- Comment #2 from tomtomtomreportin...@gmail.com ---
That string is from plugins/dockers/storyboarddocker/DlgExportStoryboard.cpp.
Line ~59.

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

[okular] [Bug 441927] Ability to have the toolbar show up on fullscreen mode

[Thiago Sueto]

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

--- Comment #2 from Thiago Sueto  ---
(In reply to Albert Astals Cid from comment #1)
> You don't mean fullscreen do you? i guess you mean presentation mode
> (ctrl+shift+p)? fullscreen (ctrl+shift+f) doesn't remove the annotation
> toolbar

I actually meant fullscreen, but I didn't notice the annotation toolbar behaved
differently from the default toolbar.

I originally edited the default toolbar to work as a button sidebar with only
the tools I wanted and it wouldn't show up in fullscreen mode, but the
annotation toolbar works so I'll edit that instead. Thanks.

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

[Discover] [Bug 440666] Will not start keeps crashing

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|BACKTRACE   |WORKSFORME

--- Comment #3 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

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

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

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

[systemsettings] [Bug 440658] incorrect resolution shown in preview

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

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

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

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

[kstars] [Bug 441112] Errors in KStars star chart

[Bug Janitor Service]

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

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

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

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

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

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

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

[krita] [Bug 441940] The string "Export Directory :" in Storyboard docker's Export SVG dialogue is untranslatable

[Tyson Tan]

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

Tyson Tan  changed:

   What|Removed |Added

Summary|Export Directory: in|The string "Export
   |Storyboard docker's Export  |Directory :" in Storyboard
   |SVG dialogue is |docker's Export SVG
   |untranslatable  |dialogue is untranslatable

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

[krita] [Bug 441940] Export Directory: in Storyboard docker's Export SVG dialogue is untranslatable

[Tyson Tan]

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

--- Comment #1 from Tyson Tan  ---
Weird enought, I've looked at
plugins/dockers/storyboarddocker/wdgexportstoryboard.ui

Between:

(#149) SVG file for specifying layout :

And

(#183) SVG file base name : 

There is only

(#166) Export File Name : 

But Krita only displays "Export Directory :"
So where did this "Export Directory :" string come from?

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

[kstars] [Bug 441684] ZWO Camera 1, 2 and 3 missing from KStars Windows version 3.5.4 stable

[Yves]

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

--- Comment #6 from Yves  ---
Hi Jasem,

Sorry for the delay... I will give a try with Ekos Debugger soon.

Yves


Le 30/08/21 05:55, Jasem Mutlaq   a écrit : 
> 
> https://bugs.kde.org/show_bug.cgi?id=441684
> 
> --- Comment #5 from Jasem Mutlaq  ---
> Please run KStars via Ekos Debugger and share the backtrace of the crash.
> 
> -- 
> You are receiving this mail because:
> You reported the bug.
>

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

[digikam] [Bug 438845] The storage location of this image is currently not available

[bugzilla_noreply]

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

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

   What|Removed |Added

   Platform|Other   |macOS (DMG)

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

[digikam] [Bug 438845] The storage location of this image is currently not available

[bugzilla_noreply]

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

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

   What|Removed |Added

Version|7.2.0   |7.4.0

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

[kdev-python] [Bug 442012] [python3] Keywords-only enforcement using `*,` partly breaks syntax highlighting

[Jan Paul Batrina]

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

Jan Paul Batrina  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #3 from Jan Paul Batrina  ---
Can confirm with KDevelop built from master and kdevelop-python 5.62 from the
KDE Neon repos.

The highlighting of arguments, class, etc. are provided by kdevelop's python
support plugin and the syntax-highlighting framework only provides basic syntax
highlighting in this case (e.g. in Kate, only 1, `cache`, and True will be
highlighted differently in the parameter list). Moved to kdev-python

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

[kdev-python] [Bug 442012] [python3] Keywords-only enforcement using `*,` partly breaks syntax highlighting

[Jan Paul Batrina]

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

Jan Paul Batrina  changed:

   What|Removed |Added

  Component|syntax  |Language support
Version|5.85.0  |5.6.2
 CC||jpmbatrin...@gmail.com
Product|frameworks-syntax-highlight |kdev-python
   |ing |
   Assignee|kwrite-bugs-n...@kde.org|m...@svenbrauch.de

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

[kate] [Bug 441603] Regression in Ruby indentation with regular expressions

[Jan Paul Batrina]

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

Jan Paul Batrina  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

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

[kate] [Bug 441603] Regression in Ruby indentation with regular expressions

[Jan Paul Batrina]

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

--- Comment #3 from Jan Paul Batrina  ---
Just tested with a Linux Mint 20.2 (based on Ubuntu 20.04) live usb I have
lying around, and there indeed the indentation worked properly with Kate 19.12
and KTextEditor 5.68.

In fact, the behavior there seems to be "smart" as it does not only take into
account the last /. For example, `if v =~ /re/` will only have one indent, but
`if  v =~ re/` and `if v =~ /re//` will both have two indentations as the last
/ is correctly identified as an unfinished division operator.

Since linuxmint is still somewhat a derivative of debian, it's still possible
that this correct behavior is limited to debian. I'll try to compile the same
versions later to see if it works there too, then maybe some other patch (not
directly to ruby.js) caused the behavior change.

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

[plasmashell] [Bug 440364] Right Click Bug On Dualhead System.

[Maluchi Ugokwe Jr.]

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

--- Comment #11 from Maluchi Ugokwe Jr.  ---
Thanks, Nate. One of those DUPLICATES actually *proves* that this is an
UPSTREAM issue.

I appreciate the confirmation. This is now objectively not a Plasma issue.

On Tue, Aug 31, 2021 at 6:20 PM Nate Graham 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=440364
>
> Nate Graham  changed:
>
>What|Removed |Added
>
> 
>  CC||marcel.r...@live.de
>
> --- Comment #10 from Nate Graham  ---
> *** Bug 436732 has been marked as a duplicate of this bug. ***
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[kwin] [Bug 439986] Maximized windows does not follow cursor.

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|REPORTED|ASSIGNED
 Ever confirmed|0   |1

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

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

[krita] [Bug 439908] Krita to support emojis in text entry

[bugzilla_noreply]

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

--- Comment #2 from rascon...@gmail.com ---
you are right to put it in a different colour text emoji if they appear,
thank you[image: image.gif]



[image: Mailtrack]

Remitente
notificado con
Mailtrack

05/09/21
03:42:19

El sáb, 17 jul 2021 a las 8:19, Alvin Wong ()
escribió:

> https://bugs.kde.org/show_bug.cgi?id=439908
>
> Alvin Wong  changed:
>
>What|Removed |Added
>
> 
>  CC||al...@alvinhc.com
>  Status|REPORTED|CONFIRMED
>  Ever confirmed|0   |1
>
> --- Comment #1 from Alvin Wong  ---
> You probably have black text on a black background. If you set the text to
> some
> other colour you would see the emoji rendered, but I know that's not the
> point...
>
> Colour emoji fonts are just OpenType SVG fonts. On Windows 10, the "Segoe
> UI
> Emoji" font is available and is supported by DirectWrite, which is what Qt
> uses. You will notice that the emoji is shown coloured in the text editor
> dialog. I can't say how it handles on Linux. There is something about our
> rendering of SVG text that causes the colour fonts to not be rendered in
> colour, but it's probably fixable.
>
> However, I would advice against intentionally using colour emoji for text
> in
> Krita even if this works. By having them inserted as text, you now depend
> on
> the emoji font being bundled by the system. If someone opens the file on
> another system, they might get a completely different look. I suggest
> adding
> the actual emoji as images (could be SVG) instead.
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[krita] [Bug 442019] Brush stroke irregular

[bugzilla_noreply]

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

tomtomtomreportin...@gmail.com changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |NOT A BUG

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

[krita] [Bug 442019] Brush stroke irregular

[josh godin]

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

--- Comment #3 from josh godin  ---
YES ha. Changing it to Windows 8 fixes the issue, according to some quick
rudimentary testing.

Sorry, I'm not too familiar with the program and hadn't explored the options.
Thank you for your help!

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

[krita] [Bug 442019] Brush stroke irregular

[bugzilla_noreply]

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

tomtomtomreportin...@gmail.com changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 CC||tomtomtomreportingin@gmail.
   ||com
 Status|REPORTED|NEEDSINFO

--- Comment #2 from tomtomtomreportin...@gmail.com ---
Does switching the tablet input API through Settings -> Configure Krita ->
Tablet Settings resolve your issue?

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

[krita] [Bug 442019] Brush stroke irregular

[josh godin]

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

--- Comment #1 from josh godin  ---
Created attachment 141301
  --> https://bugs.kde.org/attachment.cgi?id=141301=edit
Brush stroke behavior within Scratchpad. Seemingly normal.

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

[krita] [Bug 442019] New: Brush stroke irregular

[josh godin]

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

Bug ID: 442019
   Summary: Brush stroke irregular
   Product: krita
   Version: 4.4.8
  Platform: unspecified
OS: Microsoft Windows
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: Brush Engine/Bristle
  Assignee: krita-bugs-n...@kde.org
  Reporter: joshgo...@gmail.com
  Target Milestone: ---

Created attachment 141300
  --> https://bugs.kde.org/attachment.cgi?id=141300=edit
Brush stroke behavior on canvas. Brushes occasionally create a stroke which
shoots off canvas as well.

SUMMARY
Brush strokes are completely erratic when created on the canvas. However, brush
strokes are perfectly normal within the scratchpad in the brush settings
dialogue. If the error occurred in both places I would assume it's a driver
issue. But, since the scratchpad is perfect I suspect a bug. Worth noting, I
learn software in order to teach it to my students. On this workstation, I have
used the following programs (and others) without any brush behavior bugs:
Autodesk Sketchbook, Adobe Photoshop, Affinity Photo, Gimp, Inkscape, Clip
Studio.


STEPS TO REPRODUCE
I don't suspect the bug will reproduce outside of my system. I believe it's a
bug inherent to my particular type of drivers- Wacom ERM stylus drivers for
Windows 10. Here's the goofy steps ha.
1. Download latest Krita on a convertible PC with Wacom penabled screen
2. Download latest drivers
3. Paint

OBSERVED RESULT
Erratic brush behavior (all brushes).

EXPECTED RESULT
Correct brush behavior.

SOFTWARE/OS VERSIONS
Windows: Windows 10 Pro version 21h1, build 19043.1165
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[krita] [Bug 442018] KRITA: Transform tool: Transform operations always behave as if the anchor point was in the default location.

[bugzilla_noreply]

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

tomtomtomreportin...@gmail.com changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 Resolution|--- |WAITINGFORINFO
 CC||tomtomtomreportingin@gmail.
   ||com

--- Comment #2 from tomtomtomreportin...@gmail.com ---
It appears you have "Transform around pivot point" disabled. It's the anchor
icon in the Transform tool options. Alternatively you can hold Alt. Does
enabling it or holding Alt solve your problem?

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

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

[Michael Hamilton]

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

--- Comment #100 from Michael Hamilton  ---
(In reply to Guido Schmidt from comment #99)
> No Michael, this bug is not about kickoff only, it's about the plasmoids 
> in general that are attached to the startmenu. For instance the folder 
> view: It is ridiculously small, therefore shows only a few files, and 
> only the first part of their names. And it cannot be resized.
> Guido
> 
> 04.09.2021 23:25:22 Michael Hamilton :
> 
> > https://bugs.kde.org/show_bug.cgi?id=332512
> >
> > Michael Hamilton  changed:
> >
> >    What    |Removed |Added
> > 
> 
> >  CC|    |mich...@actrix.gen.nz
> >
> > --- Comment #98 from Michael Hamilton  ---
> > This seems to be an intractable issue (arguably showing an appalling 
> lack of
> > sensibility to real-world usability in the age of 4K monitors).  There 
> is an
> > alternative which works quite well and the author appears focused on 
> usability:
> > cupnoodle's Kickoff/Grid: https://store.kde.org/p/1317546 - I would 
> suggest
> > those seeking a resizable kickoff vote with their feet, which was 
> somewhat
> > officially suggested here 
> https://forum.kde.org/viewtopic.php?f=83=170175
> >
> > --
> > You are receiving this mail because:
> > You voted for the bug.

There is a solution for kickoff because I've cited one (and it does retain the
size over multiple sessions).  If there is a wider issue, I' not sure I agree
with it being a reason for deferring a kickoff usability improvement that is
long overdue (given 4K has been with us for some time now).  Perhaps this bug
should be split in two.

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

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

[Guido Schmidt]

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

--- Comment #99 from Guido Schmidt  ---
No Michael, this bug is not about kickoff only, it's about the plasmoids 
in general that are attached to the startmenu. For instance the folder 
view: It is ridiculously small, therefore shows only a few files, and 
only the first part of their names. And it cannot be resized.
Guido

04.09.2021 23:25:22 Michael Hamilton :

> https://bugs.kde.org/show_bug.cgi?id=332512
>
> Michael Hamilton  changed:
>
>    What    |Removed |Added
> 

>  CC|    |mich...@actrix.gen.nz
>
> --- Comment #98 from Michael Hamilton  ---
> This seems to be an intractable issue (arguably showing an appalling 
lack of
> sensibility to real-world usability in the age of 4K monitors).  There 
is an
> alternative which works quite well and the author appears focused on 
usability:
> cupnoodle's Kickoff/Grid: https://store.kde.org/p/1317546 - I would 
suggest
> those seeking a resizable kickoff vote with their feet, which was 
somewhat
> officially suggested here 
https://forum.kde.org/viewtopic.php?f=83=170175
>
> --
> You are receiving this mail because:
> You voted for the bug.

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

[dolphin] [Bug 442010] In a new instance, Dolphin freezes for a long period the first time trying to open a file, with no freezes on any subsequent files

[Kyle Devir]

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

--- Comment #3 from Kyle Devir  ---
The right-clicking freeze never unfreezes...

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

[dolphin] [Bug 442010] In a new instance, Dolphin freezes for a long period the first time trying to open a file, with no freezes on any subsequent files

[Kyle Devir]

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

--- Comment #2 from Kyle Devir  ---
Right-clicking in Dolphin also creates the freezing issue

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

[krita] [Bug 442018] KRITA: Transform tool: Transform operations always behave as if the anchor point was in the default location.

[bugzilla_noreply]

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

--- Comment #1 from accur...@protonmail.ch ---
Created attachment 141299
  --> https://bugs.kde.org/attachment.cgi?id=141299=edit
It's just as I said

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

[dolphin] [Bug 442010] In a new instance, Dolphin freezes for a long period the first time trying to open a file, with no freezes on any subsequent files

[Kyle Devir]

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

--- Comment #1 from Kyle Devir  ---
I've noticed that the exact same issue pops up when attempting to open Dolphin
from Konsole via "Open File Manager"

Wayland backend freezes and the connection dies. Using the XCB backend, initial
attempt freezes Konsole for a good 10 seconds, until it opens. Closing Dolphin
and trying again has an immediate outcome, without freezing.

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

[krita] [Bug 442018] New: KRITA: Transform tool: Transform operations always behave as if the anchor point was in the default location.

[bugzilla_noreply]

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

Bug ID: 442018
   Summary: KRITA: Transform tool: Transform operations always
behave as if the anchor point was in the default
location.
   Product: krita
   Version: 4.4.8
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Tools/Transform
  Assignee: krita-bugs-n...@kde.org
  Reporter: accur...@protonmail.ch
  Target Milestone: ---

SUMMARY

Transform operations always behave as if the anchor point was in the default
location.

STEPS TO REPRODUCE
1. Draw a straight line
2. Activate transform tool
3. Move anchor point
4. Do any other operation, such as scale, rotate, etc.
5. See that it doesn't move in respect to the anchor point

OBSERVED RESULT

The move and scale operations work as if the anchor was in the middle.

EXPECTED RESULT

I'd expect that the anchor point would actually have an effect in the
transformations.

SOFTWARE/OS VERSIONS
Linux: Fedora 34

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

[digikam] [Bug 382179] Keep in Add a Face Tag mode after adding a face tag

[Claudius]

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

--- Comment #13 from Claudius  ---
after working ~3 minutes with Ctrl+Click I am now pretty convinced that this
should be the standard behaviour. I just went through 40 images in the time I
usually need for 10.

no tooltip, no ctrl+click, just: I press that button, and it toggles on into
add face tag. (just like the button right next to it, that displays or hides
the existing face tags).

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

[digikam] [Bug 382179] Keep in Add a Face Tag mode after adding a face tag

[Claudius]

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

--- Comment #12 from Claudius  ---
I was reffered to this ticket because I created a duplicate (sorry, I did not
find this one myself).

I think, the ctrl shortcut absolutely needs a tooltip or something. I don't
think I would ever have tried that on my own.

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

[digikam] [Bug 442014] Request: Keyboard Shortcut for "add face tag"

[Claudius]

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

--- Comment #3 from Claudius  ---
thanks for the heads up! Didn't find that one while searching.

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

[krita] [Bug 442017] Deleting Workspaces/Window Layouts through the Workspaces and Layouts interface is annoying and unintuitive

[bugzilla_noreply]

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

--- Comment #1 from tomtomtomreportin...@gmail.com ---
Oh, and I don't think new workspaces/layouts should be activated when deleting
them either.

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

[krita] [Bug 442017] New: Deleting Workspaces/Window Layouts through the Workspaces and Layouts interface is annoying and unintuitive

[bugzilla_noreply]

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

Bug ID: 442017
   Summary: Deleting Workspaces/Window Layouts through the
Workspaces and Layouts interface is annoying and
unintuitive
   Product: krita
   Version: 5.0.0-beta1
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Resource Management
  Assignee: krita-bugs-n...@kde.org
  Reporter: tomtomtomreportin...@gmail.com
  Target Milestone: ---

SUMMARY
It can be rather annoying to delete Window Layouts through the typical
interface as selecting a Window Layout will often change the window and
deselect the particular layout in the interface, preventing you from quickly
deleting it. Thus, you have to activate the Window Layout/Workspace to be able
to delete them. There is also the fact that deleting a Window Layout/Workspace
will select a new Layout/Workspace thus making your interface annoyingly
conform to that selection on deletion.

This is not a regression as the behavior is the same in Krita 4.

STEPS TO REPRODUCE
1. Open the Workspaces and Window Layouts interface in the top-right button.
2. Click Dual Screen Editing window layout, intending to select it.

OBSERVED RESULT
The current window layout changes and the window layout itself in the interface
is deselected.

EXPECTED RESULT
Perhaps workspaces/layouts shouldn't activate on single-click, instead
activating on double-click (along with an explicit Apply button if
double-clicking isn't obvious enough).

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian sid
KDE Plasma Version: 5.21.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.12.11 (Appimage)

ADDITIONAL INFORMATION
Maybe there should also be a default Window Layout resource like how there's a
default Workspace resource.

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

[konsole] [Bug 442016] New: Copyright date is wrong

[Alexander Johansen]

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

Bug ID: 442016
   Summary: Copyright date is wrong
   Product: konsole
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: alej0hio2...@gmail.com
  Target Milestone: ---

SUMMARY
Konsole Copyright in about still shows 2020

STEPS TO REPRODUCE
1. Open Konsole
2. Press Help > About Konsole
3. Check the copyright date

OBSERVED RESULT
The copyright date shows 1997-2020. We are not in 2020 anymore.

EXPECTED RESULT
The copyright date should show 1997-2021.

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

ADDITIONAL INFORMATION

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

[digikam] [Bug 442014] Request: Keyboard Shortcut for "add face tag"

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

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

--- Comment #2 from Maik Qualmann  ---


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

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

[digikam] [Bug 382179] Keep in Add a Face Tag mode after adding a face tag

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||kde.b...@wolki.de

--- Comment #11 from Maik Qualmann  ---
*** Bug 442014 has been marked as a duplicate of this bug. ***

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

[digikam] [Bug 442014] Request: Keyboard Shortcut for "add face tag"

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
Use CTRL + left mouse button to draw face Region. 

Maik

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

[krita] [Bug 440193] Accessing the "predefined" tab in the brush editor crashes Krita (git 01f361d)

[Guilherme Rodrigues]

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

Guilherme Rodrigues  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |FIXED

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

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

[Michael Hamilton]

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

Michael Hamilton  changed:

   What|Removed |Added

 CC||mich...@actrix.gen.nz

--- Comment #98 from Michael Hamilton  ---
This seems to be an intractable issue (arguably showing an appalling lack of
sensibility to real-world usability in the age of 4K monitors).  There is an
alternative which works quite well and the author appears focused on usability:
cupnoodle's Kickoff/Grid: https://store.kde.org/p/1317546 - I would suggest
those seeking a resizable kickoff vote with their feet, which was somewhat
officially suggested here https://forum.kde.org/viewtopic.php?f=83=170175

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

[kwin] [Bug 442015] New: Screen looses content randomly, just black

[Simon Schmeisser]

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

Bug ID: 442015
   Summary: Screen looses content randomly, just black
   Product: kwin
   Version: 5.22.4
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: compositing
  Assignee: kwin-bugs-n...@kde.org
  Reporter: mail_to_...@gmx.de
  Target Milestone: ---

SUMMARY

Since about a week now (after running some system updates) my Notebooks screen
will suddenly turn black after something in between 1 min after plasma has
completely started (rare) and more often something between 10 min and 30 min.
The backlight is still on, I can adjust the brightness. Moving the mouse after
some idle time makes the screen turn on (changes from pitch black to backlit
black). I can ssh in and run commands. Videos in firefox continue playing and
can be paused/started by mouse clicks. I can often press the power button and
then enter and it will shutdown. Plymouth will shortly show the Kde neon logo
before the computer turns off.

Pressing Shift+Alt+F12 does nothing.

When I ssh in, kwin_x11 is still running.


STEPS TO REPRODUCE
1. Start Notebook
2. Do anything or nothing
3. empty/black screen

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
plasma-workspace 4:5.22.4-0xneon+20.04+focal+release+build42amd64   
Plasma Workspace for KF5
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: libkf5windowsystem-dev 
5.85.0-0xneon+20.04+focal+release+build22
Qt Version: libqt5core5a:amd64  5.15.2+p20.04+tunstable+git20210826.0127-0

ADDITIONAL INFORMATION

replacing kwin via ssh:
DISPLAY=:0 kwin_x11 --replace
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5127:46: this
compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5129:48: this
compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5131:48: this
compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5135:47: this
compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5137:46: this
compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5145:48: this
compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5149:46: this
compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5151:46: this
compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5155:45: this
compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5158:46: this
compose sequence is a duplicate of another; skipping line
kwin_xkbcommon: XKB: inet:224:50: unrecognized keysym "XF86FullScreen"
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 6184, resource
id: 29360235, major code: 18 (ChangeProperty), minor code: 0
OpenGL vendor string:   Intel
OpenGL renderer string: Mesa Intel(R) HD Graphics 620 (KBL GT2)
OpenGL version string:  4.6 (Compatibility Profile) Mesa 21.0.3
OpenGL shading language version string: 4.60
Driver: Intel
GPU class:  Kaby Lake
OpenGL version: 4.6
GLSL version:   4.60
Mesa version:   21.0.3
X server version:   1.20.11
Linux kernel version:   5.11
Requires strict binding:yes
GLSL shaders:   yes
Texture NPOT support:   yes
Virtual Machine:no
kwin_core: XCB error: 10 (BadAccess), sequence: 6327, resource id: 1956, major
code: 142 (Composite), minor code: 2 (RedirectSubwindows)

but nothing happens

in journalctl I can see some of these when the screen first goes blank:
Sep 04 22:26:15 sisBook kwin_x11[1182]: kwin_core: XCB error: 3 (BadWindow),
sequence: 4545, resource id: 14710390, major code: 129 (SHAPE), minor code: 8
(GetRectangles)
Sep 04 22:26:18 sisBook plasmashell[1264]: trying to show an empty dialog
Sep 04 22:26:19 sisBook kwin_x11[1182]: qt.qpa.xcb: QXcbConnection: XCB error:
3 (BadWindow), sequence: 14198, resource id: 41943045, major code: 18
(ChangeProperty), minor code: 0
Sep 04 22:26:19 sisBook systemd[1013]: Started Discover - Programmverwaltung.
Sep 04 22:26:19 sisBook kwin_x11[1182]: qt.qpa.xcb: QXcbConnection: XCB error:
3 (BadWindow), sequence: 14203, resource id: 41943046, major code: 18
(ChangeProperty), minor code: 0

[digikam] [Bug 442014] New: Request: Keyboard Shortcut for "add face tag"

[Claudius]

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

Bug ID: 442014
   Summary: Request: Keyboard Shortcut for "add face tag"
   Product: digikam
   Version: 7.3.0
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Usability-Keyboard
  Assignee: digikam-bugs-n...@kde.org
  Reporter: kde.b...@wolki.de
  Target Milestone: ---

Created attachment 141298
  --> https://bugs.kde.org/attachment.cgi?id=141298=edit
add face tag button in preview mode

In Digikam's preview mode, there is this button to add a face tag (see
screenshot below, I might have the wrong name for it).

This is a thing I use frequently and I would like to assign a keyboard shortcut
to this functionality. Currently, it does not come up in the keyboard shortcut
list.

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

[krusader] [Bug 392133] Huge memory consumption while doing nothing

[PhobosK]

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

--- Comment #39 from PhobosK  ---
Created attachment 141297
  --> https://bugs.kde.org/attachment.cgi?id=141297=edit
heaptrack.krusader.jpg

I found something very strange about this memory hog

It still happens on my system - right after krusader is started it has some
20-30 sec delay before its window is painted, the next 10 min it gets >200 Mb
mem usage and for an hour it ups to 1.5 Gb.

I found that there is mem leaking connected to KDirWatch, started by
KBookmarkManager.

The truth is I have around 50 bookmarks from diff protocols - sftp:/, file:/,
smb:/ - and some of them were old with missing paths. So I decided to leave
only those working - ~20 - but it didn't help.
I turned off the search in bookmarks too - but it didn't help either.

Krusader from my root profile with only 5 bookmarks with the file:/ protocol
doesn't have this memory problem + it starts (paints) the window almost
immediately after the start and memory usage stays at max 30 Mb for a long
time

I am sorry that I attach a screenshot only of heaptrack, but this is taken on
the 15 min of usage of krusader and is sorted by "Leaked" memory.

The system is: 
Krusader 2.7.2
KDE Frameworks 5.85.0
KDE Apps 21.08.1
Qt 5.15.2
The xcb windowing system

I do not know if it is relevant (I think KDirWatch is also dependent on it) but
because of baloo and idea I have set:
fs.inotify.max_user_watches = 524288

I hope this will help

Thanks

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

[digikam] [Bug 438845] The storage location of this image is currently not available

[Eric Moret]

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

--- Comment #18 from Eric Moret  ---
I can still reproduce this problem with latest build as of 9/1/2021

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

[lattedock] [Bug 442013] Dock/Panel set as Windows Can Cover hides like a window

[bugzilla_noreply]

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

ryu.ketsu...@outlook.com changed:

   What|Removed |Added

Summary|Dock/Panel set as Windows   |Dock/Panel set as Windows
   |Can Cover with window   |Can Cover hides like a
   |behavior|window

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

[lattedock] [Bug 442013] New: Dock/Panel set as Windows Can Cover with window behavior

[bugzilla_noreply]

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

Bug ID: 442013
   Summary: Dock/Panel set as Windows Can Cover with window
behavior
   Product: lattedock
   Version: git (master)
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: ryu.ketsu...@outlook.com
  Target Milestone: ---

Created attachment 141296
  --> https://bugs.kde.org/attachment.cgi?id=141296=edit
Three screenshots showing what I mean

SUMMARY
This requires a very specific set of steps to reproduce, specially now that
Overview is in development and it is where it is most visible.

First, if a panel is set as "Windows Can Cover", the "Show Desktop" call hides
it as if it were just any other window. One of the ways of hiding it is just by
entering Plasma's Edit Mode or by pressing the Show Desktop icon. Similarly,
the new Overview identifies the panel as a window and lists it on the Overview
as such. While I know that the issue with Overview could be result of being
still in development and in no way in a release candidate state, the part of
hiding the panel set as "Windows Can Cover" when in the Show Desktop call, is a
little of an odd behavior. Now it could possibly happen with other visibility
options but I only tested with this one.

Still on the Overview topic, it would be interesting if the docks/panels stayed
where they are when on overview instead of disappearing, kinda like how it
happens on Deepin 20 and Gnome 40

STEPS TO REPRODUCE
1. Just set a panel or dock with the behavior "Windows Can Cover"
2. Enter Plasma's Edit Mode or press the Show Desktop button on the panel

OBSERVED RESULT
Panel/dock is hidden as if it were a regular window

EXPECTED RESULT
Panel/dock stay on screen

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20210902
KDE Plasma Version: 5.22.80
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2
Kernel Version: 5.13.13-1-default (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i3-7020U CPU @ 2.30GHz
Memory: 11.5 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 620

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

[dolphin] [Bug 442010] In a new instance, Dolphin freezes for a long period the first time trying to open a file, with no freezes on any subsequent files

[Kyle Devir]

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

Kyle Devir  changed:

   What|Removed |Added

 CC||kyle.de...@mykolab.com

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

[konsole] [Bug 436264] "New Tab" menu item does nothing when only one profile exists

[nsprangers]

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

nsprang...@gmail.com  changed:

   What|Removed |Added

 CC||nsprang...@gmail.com

--- Comment #4 from nsprang...@gmail.com  ---
Submitted the above merge request.

A better fix would be for the "File > New Tab" menu item to become clickable
when there is only one profile.

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

[frameworks-syntax-highlighting] [Bug 442012] [python3] Keywords-only enforcement using `*,` partly breaks syntax highlighting

[Manuel Geißer]

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

--- Comment #2 from Manuel Geißer  ---
At first I was a bit puzzled by this issue because stopping syntax highlighting
first gave me the impression that there was a fault in my code.

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

[kmail2] [Bug 390002] Message viewer: attached .doc file is shown as encrypted

[Friedrich W. H. Kossebau]

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

--- Comment #8 from Friedrich W. H. Kossebau  ---
Thanks for the quick reply and research, Ingo. Okay, so we need to fix/improve
things on our side.  Only on my schedule for next week#'s WE to continue here,
so anyone is invited to have a look & go themselves until ;)

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

[frameworks-syntax-highlighting] [Bug 442012] [python3] Keywords-only enforcement using `*,` partly breaks syntax highlighting

[Manuel Geißer]

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

Manuel Geißer  changed:

   What|Removed |Added

 CC||geisse...@gmail.com

--- Comment #1 from Manuel Geißer  ---
Created attachment 141295
  --> https://bugs.kde.org/attachment.cgi?id=141295=edit
Without `*,` syntax

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

[frameworks-syntax-highlighting] [Bug 442012] New: [python3] Keywords-only enforcement using `*,` partly breaks syntax highlighting

[Manuel Geißer]

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

Bug ID: 442012
   Summary: [python3] Keywords-only enforcement using `*,` partly
breaks syntax highlighting
   Product: frameworks-syntax-highlighting
   Version: 5.85.0
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: syntax
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: geisse...@gmail.com
CC: walter.von.entfer...@posteo.net
  Target Milestone: ---

Created attachment 141294
  --> https://bugs.kde.org/attachment.cgi?id=141294=edit
With *, syntax

SUMMARY

Since Python 3, one can enforce the use of keyword arguments in method
definitions. This ensures that downstream code is proof against possible future
changes to the order of positional arguments. All arguments from a `*,` onwards
need to be preceeded with explicit keywords (cf.
https://www.vegardstikbakke.com/python-keyword-only/).

However, this syntax seems to partly break KDevelop's Python syntax
highlighting, with default arguments following the `*,` not being
recognised/highlighted anymore.

Example:
```python3
import os

class Backend:
AUTO = None

def run(
info,
tempdir,
*,
backend = Backend.AUTO,
n_processes = os.cpu_count()+1,
n_chunks = 1,
scaling = 1,
cache_name = 'cache',
verbose = True,
):
pass
```

STEPS TO REPRODUCE
1. Paste a Python code using the keyword-only enforcing `*,` into KDevelop, for
instance the above example.
2. Save it as $SOME_FILENAME.py for syntax highlighting to get active.
3. Remove the `*,` and see how syntax highlighting changes

OBSERVED RESULT
Default arguments after `*,` are not highlighted. Without `*,` they are.

EXPECTED RESULT
Default arguments should always be highlighted correctly, regardless of whether
there is a `*,` or not.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.3
Kernel Version: 5.11.0-27-generic (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION
Maybe this is rather a problem with KDevelop than with the syntax highlighting
framework. If you think so, feel free to move the issue.

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

[okular] [Bug 442003] missing plug-in for ODT

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |NOT A BUG
 CC||aa...@kde.org

--- Comment #1 from Albert Astals Cid  ---
Correct, there's no plugin to open it, so you get a warning. 

Exactly like if you ask for it to open an mp3 file.

I think that calligra may ship an okular+odt plugin, you may want to install it

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

[konsole] [Bug 436264] "New Tab" menu item does nothing when only one profile exists

[Bug Janitor Service]

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

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/utilities/konsole/-/merge_requests/474

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

[plasmashell] [Bug 442011] New: kf.plasma.core: findInCache with a lastModified timestamp of 0 is deprecated

[Timothée Ravier]

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

Bug ID: 442011
   Summary: kf.plasma.core: findInCache with a lastModified
timestamp of 0 is deprecated
   Product: plasmashell
   Version: 5.22.4
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: trav...@redhat.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

SUMMARY

In some cases (exact reproducible steps not found yet), Plasma will fail to
display any application icon on Fedora Kinoite.

On Fedora Kinoite, all files in /usr are set with the UNIX timestamp of 0.
Running plasmashell in a terminal will show that line repeatedly:

kf.plasma.core: findInCache with a lastModified timestamp of 0 is deprecated

Updating the timestamps on those files and running kbuildsyscoca5 temporarily
fixes the issue.

This is most likely due to a confusion in:
https://api.kde.org/frameworks/plasma-framework/html/theme_8cpp_source.html#l00280
where lastModified is here truly 0 and not left to the default value.

An option would be to use 1 instead when looking at a file with a 0 timestamp
in the calling code but I have not found where this function is called yet.

STEPS TO REPRODUCE
1. Clean icon cache
2. Set an application icon file, desktop entry, etc. timestamp to UNIX time 0
3. plasma-shell --replace

OBSERVED RESULT

Lots of:
kf.plasma.core: findInCache with a lastModified timestamp of 0 is deprecated

Application has no icon.

EXPECTED RESULT

Applications has an icon.

SOFTWARE/OS VERSIONS
Fedora Linux 35 & Rawhide
Linux/KDE Plasma: 5.22.4
KDE Plasma Version: 5.22.4
KDE Frameworks Version: 5.85
Qt Version: 5.15.2

ADDITIONAL INFORMATION
This is similar to https://bugs.kde.org/show_bug.cgi?id=429196 but I could not
get this working with the same workaround.

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

[gwenview] [Bug 441698] Gwenview fails to open RAW images (NEF, ARW, etc.) on ArchLinux

[Maximilian Schmeling]

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

--- Comment #8 from Maximilian Schmeling  ---
NO thumbnail or anything like that found in the exif.
Output of identify -verbose (if it is useful to you):
Image:
  Filename: blackbird.nef
  Format: NEF (Nikon Digital SLR Camera Raw Image File)
  Class: DirectClass
  Geometry: 4284x2844+0+0
  Units: Undefined
  Colorspace: sRGB
  Type: TrueColor
  Base type: Undefined
  Endianness: Undefined
  Depth: 16-bit
  Channel depth:
Red: 16-bit
Green: 16-bit
Blue: 16-bit
  Channel statistics:
Pixels: 12183696
Red:
  min: 0  (0)
  max: 65535 (1)
  mean: 26766.2 (0.408426)
  median: 26996 (0.411933)
  standard deviation: 8750.92 (0.13353)
  kurtosis: 6.56578
  skewness: 0.991362
  entropy: 0.890515
Green:
  min: 0  (0)
  max: 65535 (1)
  mean: 19808.2 (0.302254)
  median: 20141 (0.307332)
  standard deviation: 7053.62 (0.107631)
  kurtosis: 10.7367
  skewness: 1.84245
  entropy: 0.845379
Blue:
  min: 0  (0)
  max: 65535 (1)
  mean: 12425.3 (0.189598)
  median: 11672 (0.178103)
  standard deviation: 5535.46 (0.0844656)
  kurtosis: 13.9584
  skewness: 2.83654
  entropy: 0.807484
  Image statistics:
Overall:
  min: 0  (0)
  max: 65535 (1)
  mean: 19666.6 (0.300093)
  median: 19603 (0.299123)
  standard deviation: 7113.33 (0.108542)
  kurtosis: 3.63934
  skewness: 1.14002
  entropy: 0.847793
  Rendering intent: Perceptual
  Gamma: 0.454545
  Chromaticity:
red primary: (0.64,0.33)
green primary: (0.3,0.6)
blue primary: (0.15,0.06)
white point: (0.3127,0.329)
  Matte color: grey74
  Background color: white
  Border color: srgb(223,223,223)
  Transparent color: none
  Interlace: None
  Intensity: Undefined
  Compose: Over
  Page geometry: 4288x2844+2+0
  Origin geometry: +2+0
  Dispose: Undefined
  Iterations: 0
  Compression: Undefined
  Orientation: Undefined
  Profiles:
Profile-icc: 940 bytes
Profile-xmp: 6080 bytes
  Properties:
date:create: 2021-08-30T13:08:03+00:00
date:modify: 2008-05-31T18:10:12+00:00
dng:camera.model.name: D3
dng:create.date: 2008-05-09T15:56:53+00:00
dng:exposure.time: 1/1000.0
dng:f.number: 7.1
dng:focal.length.in.35mm.format: 1000 mm
dng:iso.setting: 1400.0
dng:lens: 600.0-600.0mm f/4.0-4.0
dng:lens.f.stops: 5.00
dng:lens.type: G VR
dng:make: Nikon
dng:max.aperture.at.max.focal: 4.0
dng:max.aperture.at.min.focal: 4.0
dng:max.aperture.value: 6.7
dng:max.focal.length: 600.0 mm
dng:min.focal.length: 600.0 mm
dng:ocal.length: 1000.0
dng:serial.number: 2004426
dng:software: Capture NX 2.0.0 M
dng:wb.rb.levels: 465.00 347.00 256.00 256.00
icc:copyright: Copyright (c) Eastman Kodak Company, 1999, all rights
reserved.
icc:description: ProPhoto RGB
icc:manufacturer: KODAK
icc:model: Reference Output Medium Metric(ROMM)  
MicrosoftPhoto:Rating: 0
photomechanic:Prefs: 0:0:0:006567
photomechanic:TimeCreated: 175653-0700
photoshop:DateCreated: 2008-05-09
signature: 5fbb8d79a4142398f35fb31018408ce9f545f3603f2a4b1a90fe1cba89db2bad
xap:Rating: 0
xapRights:Marked: True
xapRights:WebStatement: www.luminescentphoto.com
  Artifacts:
verbose: true
  Tainted: False
  Filesize: 18.2634MiB
  Number pixels: 12.1837M
  Pixels per second: 6.37156MP
  User time: 5.530u
  Elapsed time: 0:02.912
  Version: ImageMagick 7.1.0-5 Q16 x86_64 2021-08-22 https://imagemagick.org

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

[dolphin] [Bug 442010] New: In a new instance, Dolphin freezes for a long period the first time trying to open a file, with no freezes on any subsequent files

[Kyle Devir]

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

Bug ID: 442010
   Summary: In a new instance, Dolphin freezes for a long period
the first time trying to open a file, with no freezes
on any subsequent files
   Product: dolphin
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: kyle.de...@mykolab.com
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY

After opening a new instance, Dolphin will freeze for a good 10 or so seconds
upon trying to open any file, but eventually unfreezes, and the file opens
fine. Subsequent attempts to open files show no such freezes or delays. With
the Wayland backend, this was causing the Wayland connection to just die before
it could unfreeze, so I discovered this with the XCB backend.


STEPS TO REPRODUCE

1. Update to kdesrc-build master
2. Open fresh instance of Dolphin using XCB backend
3. Open any file ~ wait a long period for Dolphin to unfreeze and actually open
4. Open any other files, and notice immediate response


OBSERVED RESULT

Long delay with initial file opening.


EXPECTED RESULT

Normal response times


SOFTWARE/OS VERSIONS

Operating System: Arch Linux
KDE Plasma Version: 5.22.80
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2
Kernel Version: 5.14.1-arch1-1-custom (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: Radeon RX 580 Series

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

[gwenview] [Bug 441698] Gwenview fails to open RAW images (NEF, ARW, etc.) on ArchLinux

[Lapineige]

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

--- Comment #7 from Lapineige  ---
Maybe it's called thumbnail or something like that in NEF file exifs ?

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

[plasmashell] [Bug 420160] Session crashes when monitor goes into standby

[bugzilla_noreply]

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

--- Comment #50 from darkba...@linuxsystems.it ---
I don't know if it's related or a completely different bug, but if I attach an
external monitor and set it as my sole output (thus my laptop's screen goes
black) then as soon as I close the laptop lid it crashes.
My workaround is to attach the external monitor at boot and close the laptop's
lid in SDDM, before logging into Plasma. I'm using Arch Linux packages.

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

[kdenlive] [Bug 442009] New: Background for subtitles

[bugzilla_noreply]

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

Bug ID: 442009
   Summary: Background for subtitles
   Product: kdenlive
   Version: 21.08.1
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: vi.ku...@protonmail.com
  Target Milestone: ---

SUMMARY
Currently, the subtitles features prints the subtitle text without any
background. It is printed as simple text with an outline to help it stand out.
In some situations, this is not sufficient to help the text be fully legible.
It would be helpful if we could optionally set subtitles to have a background.
This background could have a color chosen by the user and with a chosen
transparency as well to not completely obstruct the video.

STEPS TO REPRODUCE
1. Add a video to the timeline
2. Add subtitles

OBSERVED RESULT
On certain videos, subtitles are hard to read.

EXPECTED RESULT
Desired, a translucent background behind the subtitle text to add a more
consistent background so the text is more legible.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.12.15
(available in About System)
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
N/A

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

[plasmashell] [Bug 420160] Session crashes when monitor goes into standby

[Zamundaaa]

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

Zamundaaa  changed:

   What|Removed |Added

 CC||xaver.h...@gmail.com

--- Comment #49 from Zamundaaa  ---
There have been a few related changes in KWin, and while plasmashell still
crashes, neither turning off the output nor having Screen Energy Savings kills
the session for me with git master. Can you check again?

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

[plasmashell] [Bug 441659] ownCloud client icon missing in systemtray

[Andy]

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

Andy  changed:

   What|Removed |Added

 CC||philoso...@freemail.hu

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

[gwenview] [Bug 441698] Gwenview fails to open RAW images (NEF, ARW, etc.) on ArchLinux

[Maximilian Schmeling]

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

--- Comment #6 from Maximilian Schmeling  ---
(In reply to Lapineige from comment #5)

> Could you run ```identify -verbose file.NEF  |grep review``` to see if
> several "Preview" are included in the Exifs ?

Nope, nothing is returned from ```identify -verbose file.NEF  |grep review```
(file.nef changed).

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

[Spectacle] [Bug 442008] New: Could not take a screenshot

[Pily Botello]

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

Bug ID: 442008
   Summary: Could not take a screenshot
   Product: Spectacle
   Version: 20.04.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: pily.bote...@gmail.com
CC: k...@david-redondo.de
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. When click -> Take a New Screeshot, display the following message: Could not
take a screenshot
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


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

ADDITIONAL INFORMATION

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

[konsole] [Bug 423136] Konsole crashes with multiple instances opened and changing profile settings

[nsprangers]

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

nsprang...@gmail.com  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED
 CC||nsprang...@gmail.com

--- Comment #1 from nsprang...@gmail.com  ---
I can reproduce this on version 21.11.70 (current git) but not on 21.08.0
(packaged with Manjaro).

It reliably crashes when selecting "Default [Read Only]" and clicking "Set as
default" with this error:

ASSERT: "_profiles.find(profile) != _profiles.cend()" in file
/home/nathan/kde/src/konsole/src/profile/ProfileManager.cpp, line 414

Cannot reproduce on 21.08.0 (Manjaro) version.

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

[plasmashell] [Bug 420160] Session crashes when monitor goes into standby

[bugzilla_noreply]

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

darkba...@linuxsystems.it changed:

   What|Removed |Added

 CC||darkba...@linuxsystems.it

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

[kcalc] [Bug 441986] Allow Resizing of KCalc

[Niklas Freund]

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

--- Comment #1 from Niklas Freund  ---
I'm trying to implement scaling myself now.
I've created a draft merge request over on GitLab.
https://invent.kde.org/utilities/kcalc/-/merge_requests/24

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

[okteta] [Bug 442007] New: Decoding table tool doesn't save preferences upon exit

[viktor]

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

Bug ID: 442007
   Summary: Decoding table tool doesn't save preferences upon exit
   Product: okteta
   Version: 0.26.6
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kosse...@kde.org
  Reporter: linux...@gmail.com
  Target Milestone: ---

SUMMARY
I'm using decoding table quite a lot and there is one annoying thing (may be
it's not a bug) - settings (endianness and "Unsigned as hexadecimal") are not
saved when closing Okteta. The tool itself will be shown (if left visible upon
exit), but its settings will not be restored - instead, default little
endianness and Unsigneds as hex will be used.

STEPS TO REPRODUCE
1. Open Okteta, enable Decoding table tool
2. Set desired endianness and (optionally) display of unsigneds as hex
3. Close Okteta
4. Run it again and check settings of Decoding table tool

OBSERVED RESULT
Settings of the Decoding tool are reset to defaults (little endianness, display
unsigneds as hex)

EXPECTED RESULT
Settings of the Decoding tool will be preserved

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.22.4
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2 with KDE patches

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

[Elisa] [Bug 442006] New: Add option to show artist and title of currently played song in the window title bar next to Elisa name.

[bugzilla_noreply]

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

Bug ID: 442006
   Summary: Add option to show artist and title of currently
played song in the window title bar next to Elisa
name.
   Product: Elisa
   Version: unspecified
  Platform: unspecified
OS: All
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: matthieu_gall...@yahoo.fr
  Reporter: dialan...@seznam.cz
  Target Milestone: ---

Created attachment 141293
  --> https://bugs.kde.org/attachment.cgi?id=141293=edit
VLC media player example

This is just a suggestion for a feature.

Add the artist and a title of the currently played song into the title bar of
the Elisa window.

Many other media players do that such as: Juk, VLC, Strawberry or Amarok. I
added VLC format into the attachments and I'm also adding  it here:

Artist - Title - App name

Even more awesome would be if we could customize what exactly is shown in the
window title bar.

There are two reasons why to implement this:

1. This data appear in the taskbar of users DE. User can see what is being
played just by looking on the taskbar.

2. Other apps can pull this data and use it. I use this with OBSs plugin tuna,
that searches all window titles for a keyword (VLC) and pulls the window title
so the recording includes the name of currently played song.

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

[krita] [Bug 441899] Pop-up palette doesn't dismiss itself at right click

[bugzilla_noreply]

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

tomtomtomreportin...@gmail.com changed:

   What|Removed |Added

   Keywords||regression
 CC||tomtomtomreportingin@gmail.
   ||com
 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #1 from tomtomtomreportin...@gmail.com ---
Can confirm. 

There is differing behavior depending on the form of the color selector like in
https://bugs.kde.org/show_bug.cgi?id=441154 . Behavior also differs between
mouse and stylus. With triangle selector and a stylus, right-click inside the
color selector area will never dismiss the pop-up palette, thus making it
regressive from 4.4.7. With wide gamut selector and a stylus, it will take two
clicks. With either selector and a mouse, it takes just one right-click.

In 4.4.7, the pop-up palette takes two clicks to dismiss only when in the brush
presets area, which I'm not sure is intended, but the selector area takes one
right-click regardless of mouse or stylus.

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

[kdenlive] [Bug 442005] New: 3 point balance don't work if connected external monitor

[repeat]

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

Bug ID: 442005
   Summary: 3 point balance don't work if connected external
monitor
   Product: kdenlive
   Version: 21.08.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: pereulo...@gmail.com
  Target Milestone: ---

SUMMARY
If I connect external monitor to notebook (display notebook primary on
right side) then can't get color by eyedropper tool usin effects "3 points
balance"


STEPS TO REPRODUCE
1. Connect external monitor to notebook with different resolution (1440x900
- notebook; 1920x1080 - external monitor)
2. Set notebook display as primary on right side
3. Run kdenlive at any monitor
4. Drop some footage to timeline
5. Add effects "3 point balance"
6. Pick up color by eyedropper tool

OBSERVED RESULT
wrong color (are most is blue or black)


EXPECTED RESULT
color are correctly


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Ubuntu 20.04.3 LTS (Xubuntu)

ADDITIONAL INFORMATION

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

[krita] [Bug 441959] Soft Proofing on krita 5 (beta 1) still has glitches, but now triggered by transparencies

[bugzilla_noreply]

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

tomtomtomreportin...@gmail.com changed:

   What|Removed |Added

 CC||tomtomtomreportingin@gmail.
   ||com
 Ever confirmed|0   |1
   Keywords||regression
 Status|REPORTED|CONFIRMED

--- Comment #2 from tomtomtomreportin...@gmail.com ---
Can confirm.

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

[systemsettings] [Bug 439375] The font management kcm is missing from system settings in wayland session

[Patrick Silva]

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

Patrick Silva  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

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

[krita] [Bug 442004] New: Out of Gamut Warnings doesn't work in Krita 5 beta 1

[Diogo]

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

Bug ID: 442004
   Summary: Out of Gamut Warnings doesn't work in Krita 5 beta 1
   Product: krita
   Version: 5.0.0-beta1
  Platform: Compiled Sources
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Color models
  Assignee: krita-bugs-n...@kde.org
  Reporter: dreat...@outlook.com
  Target Milestone: ---

Created attachment 141292
  --> https://bugs.kde.org/attachment.cgi?id=141292=edit
Image comparing the same file with the same definition in two versions of krita

SUMMARY
The "Out of Gamut Warnings" doesn't work in Krita 5 beta 1. It Works normally
on previous versions, including the latest stable 4.4.8
see attached image

STEPS TO REPRODUCE
1. just activate the out of gamut warnings ( CTRL+SHIFT+Y )
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


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

ADDITIONAL INFORMATION

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

[kdeplasma-addons] [Bug 439890] NOAA data no longer obtainable

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #4 from Nate Graham  ---
Works for me now too. Seems like the source data itself may be a bit unstable.
Sadly there's nothing we can do about that. :(

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

[okular] [Bug 442003] missing plug-in for ODT

[Christopher Yeleighton]

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

Christopher Yeleighton  changed:

   What|Removed |Added

URL||https://documentation.libre
   ||office.org/assets/Uploads/D
   ||ocumentation/en/DG4.3/ODT/D
   ||G4311-AdvancedDrawTechnique
   ||s.odt

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

[okular] [Bug 442003] New: missing plug-in for ODT

[Christopher Yeleighton]

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

Bug ID: 442003
   Summary: missing plug-in for ODT
   Product: okular
   Version: 21.08.1
  Platform: Flatpak
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: ODT backend
  Assignee: okular-de...@kde.org
  Reporter: giecr...@stegny.2a.pl
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. Tell Okular to open file DG4311-AdvancedDrawTechniques.odt!

OBSERVED RESULT
Error: Okular cannot find the plug-in necessary to open the document.

EXPECTED RESULT
Let Okular find the plug-in!

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: openSUSE Tumbleweed 20210901
(available in About System)
KDE Plasma Version: 5.22.4
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
No add-ons for Okular are available.

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

[gwenview] [Bug 441698] Gwenview fails to open RAW images (NEF, ARW, etc.) on ArchLinux

[bugzilla_noreply]

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

tagwer...@innerjoin.org changed:

   What|Removed |Added

 CC||tagwer...@innerjoin.org

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

[kwin] [Bug 424370] Closable window rule is not immediately applied to window decoration

[Ismael Asensio]

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

Ismael Asensio  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/plas
   ||ma/kwin/commit/436011e0ec92
   ||e461b7a9b8571e063b5b1765ed4
   ||9
 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED
   Version Fixed In||5.22.90

--- Comment #2 from Ismael Asensio  ---
Git commit 436011e0ec92e461b7a9b8571e063b5b1765ed49 by Ismael Asensio.
Committed on 04/09/2021 at 13:51.
Pushed by iasensio into branch 'master'.

X11Client: emit isCloseableChanged when updated

This allows the decoration buttons to be updated accordingly
when the status changes.

We also need to explicitely update allowed actions when rules
are applied, as `isCloseable` is not a settable property, but
an allowed action
FIXED-IN: 5.22.90

M  +6-2src/x11client.cpp

https://invent.kde.org/plasma/kwin/commit/436011e0ec92e461b7a9b8571e063b5b1765ed49

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

[gwenview] [Bug 441698] Gwenview fails to open RAW images (NEF, ARW, etc.) on ArchLinux

[Lapineige]

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

--- Comment #5 from Lapineige  ---
(In reply to Maximilian Schmeling from comment #4)
> but now the resolution is 120x160, which isn't much for a 24MP image.


Ok then that's clearly not the same issue.
ARW (Sony) files only contain a 1600*900px preview, hence that's what is
displayed. They also contain a much smaller version (maybe something similar to
120*160 actually). Maybe in your case Gwenview switched from one to another ?

Could you run ```identify -verbose file.NEF  |grep review``` to see if several
"Preview" are included in the Exifs ?

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

[krita] [Bug 441687] WinTab: Stylus input triggers single touch panning gesture

[Alvin Wong]

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

Alvin Wong  changed:

   What|Removed |Added

 CC||oscarbaech...@gmail.com

--- Comment #4 from Alvin Wong  ---
*** Bug 441145 has been marked as a duplicate of this bug. ***

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

[krita] [Bug 441145] Brush switches to hand tool on Krita 5.0

[Alvin Wong]

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

Alvin Wong  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
   Platform|Other   |Microsoft Windows
  Component|Tools/Selection |Tablets (tablet issues are
   ||only very rarely bugs in
   ||Krita!)
 Resolution|--- |DUPLICATE
 OS|Other   |Microsoft Windows
Version|unspecified |5.0.0-beta1
 CC||al...@alvinhc.com

--- Comment #1 from Alvin Wong  ---
Marking as duplicate, please let me know if this isn't actually happening with
WinTab mode for you.

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

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

[krita] [Bug 442000] Search box in Resource Chooser does not have a save button, Enter key doesn't work either.

[Tyson Tan]

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

--- Comment #2 from Tyson Tan  ---
Then we should probably remove that from the documentation as well.

But that section has been just updated for 5.0, so I thought it was a bug.

Shall we change this to a documentation bug instead?

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

[kdeconnect] [Bug 428060] problem copying file from Android KDE Connect 1.14.2 to Leap 15.2 kdeconnect-kde 20.04.2-lp152.2.3.1

[Ian Proudler]

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

Ian Proudler  changed:

   What|Removed |Added

 CC||i.proud...@oxon.org

--- Comment #4 from Ian Proudler  ---
SUMMARY
I used KDEconnect to copy a jpg-file with Dolphin from Galaxy A20e with Android
11. gimp says 
"Corrupt JPEG data: 10812 extraneous bytes before marker 0xd1
Opening 'Dolphin_20210904_100424.jpg' failed: JPEG image plug-in could not open
image (1. Sept 2020 patch) to my home directory. Only the first 0x1 bytes
are correct.
JPEG datastream contains no image"

I emailed the picture to myself. I can view the picture OK. cmp says
"email_20210904_100424.jpg Dolphin_20210904_100424.jpg differ: byte 32769, line
110"



STEPS TO REPRODUCE
1. connect to phone using KDEconnect
2. copy file with Dolphin to PC
3. open using gimp
4. mail file  to PC (Thunderbird) save file
5. cmp file1.jpg file2.jpg

OBSERVED RESULT
gimp says file is corrupt. cmp says files are different.

EXPECTED RESULT
gimp should display file. cmp should say files are indetical.

SOFTWARE/OS VERSIONS
Linux: Kubuntu 20.04
KDE Plasma Version: 5.18.5 
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8
KDEconnect app on phone: 1.17.0
KDEconnect on PC: 1.4-0ubuntu5


ADDITIONAL INFORMATION

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

[kphotoalbum] [Bug 442002] Right-Clicking a viewer produces a crash (probably reated to the VLC backend)

[Tobias Leupold]

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

Tobias Leupold  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/grap
   ||hics/kphotoalbum/commit/1b2
   ||60ad99c4e726ea9d27c5ea4cf6f
   ||adcb135dce

--- Comment #1 from Tobias Leupold  ---
Git commit 1b260ad99c4e726ea9d27c5ea4cf6fadcb135dce by Tobias Leupold.
Committed on 04/09/2021 at 15:49.
Pushed by tleupold into branch 'master'.

ViewerWidget: Check for a video currently being displayed

... when invoking the context menu to prevent a segfault if currently an
image is displayed.

M  +1-1Viewer/ViewerWidget.cpp

https://invent.kde.org/graphics/kphotoalbum/commit/1b260ad99c4e726ea9d27c5ea4cf6fadcb135dce

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

[gwenview] [Bug 441698] Gwenview fails to open RAW images (NEF, ARW, etc.) on ArchLinux

[Maximilian Schmeling]

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

--- Comment #4 from Maximilian Schmeling  ---
(In reply to Lapineige from comment #3)
> Isn't that the same as https://bugs.kde.org/show_bug.cgi?id=347574 ?
> 
> Displaying the Jpeg preview instead of the RAW file is a feature and not a
> bug, isn't it ?
> Then the "issue" is that the embedded jpeg preview is smaller than the RAW
> file, at least for ARW files, I guess it's the same for NEF files ?


A month ago I was able to view NEF images in (nearly?) full resolution, but now
the resolution is 120x160, which isn't much for a 24MP image.

But since `file` detects it as a TIFF image, Gwenview might not be able to
generate the JPEG preview.

I think if `file` would detect the image as `image/x-nikon-nef` the problem
would be solved, is there any way to simulate or fake the MIME type for
Gwenview to test it?

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

[kwin] [Bug 271686] Keyboard shortcut to move windows to activities

[Dashon]

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

Dashon  changed:

   What|Removed |Added

 CC||dashonww...@pm.me

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

[kphotoalbum] [Bug 442002] New: Right-Clicking a viewer produces a crash (probably reated to the VLC backend)

[Tobias Leupold]

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

Bug ID: 442002
   Summary: Right-Clicking a viewer produces a crash (probably
reated to the VLC backend)
   Product: kphotoalbum
   Version: GIT master
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: Viewer
  Assignee: kpab...@willden.org
  Reporter: t...@l3u.de
  Target Milestone: ---

Steps to reproduce:

- Open an image to launch the viewer
- Right-click it
--> Crash

Here's the backtrace:

Thread 1 "kphotoalbum" received signal SIGSEGV, Segmentation fault.
0x775ce640 in libvlc_media_get_state () from /usr/lib64/libvlc.so.5
(gdb) backtrace
#0  0x775ce640 in libvlc_media_get_state () at /usr/lib64/libvlc.so.5
#1  0x557a7208 in Viewer::VLCDisplay::isPaused() const
(this=0x564dc9c0)
at ../Viewer/VLCDisplay.cpp:99
#2  0x5566f91c in
Viewer::ViewerWidget::contextMenuEvent(QContextMenuEvent*)
(this=0x5724e620, e=0x7fffcb30) at ../Viewer/ViewerWidget.cpp:496
#3  0x7fffedab3ede in QWidget::event(QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#4  0x7fffedb6506e in QFrame::event(QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#5  0x7fffeda70193 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
()
at /usr/lib64/libQt5Widgets.so.5
#6  0x7fffeda7a066 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#7  0x7fffed075ba8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
()
at /usr/lib64/libQt5Core.so.5
#8  0x7fffedacfa92 in  () at /usr/lib64/libQt5Widgets.so.5
#9  0x7fffedad271c in  () at /usr/lib64/libQt5Widgets.so.5
#10 0x7fffeda70193 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
()
at /usr/lib64/libQt5Widgets.so.5
#11 0x7fffeda79210 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#12 0x7fffed075ba8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
()
at /usr/lib64/libQt5Core.so.5
#13 0x7fffed461170 in
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
() at /usr/lib64/libQt5Gui.so.5
#14 0x7fffed462a75 in
QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
() at /usr/lib64/libQt5Gui.so.5
#15 0x7fffed43c9db in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() at /usr/lib64/libQt5Gui.so.5
#16 0x7fffe5088c1a in  () at /usr/lib64/libQt5XcbQpa.so.5
#17 0x7fffe9546e9b in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#18 0x7fffe9547158 in  () at /usr/lib64/libglib-2.0.so.0

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

[plasmashell] [Bug 442001] New: The first app you open on a different desktop causes the tray icon to not appear, but the apps opened after have their icon.

[bugzilla_noreply]

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

Bug ID: 442001
   Summary: The first app you open on a different desktop causes
the tray icon to not appear, but the apps opened after
have their icon.
   Product: plasmashell
   Version: master
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: raspberr...@disroot.org
CC: mate...@gmail.com
  Target Milestone: 1.0

SUMMARY
Opening an app on a different desktop than #1 causes the tray icon to
disappear.

STEPS TO REPRODUCE
1. Switch to any desktop besides #1.
2. Open an app with a tray icon (Discord, NeoChat, anything)
3. Notice how the tray icon isn't there.
4. Open another app with a tray icon.
5. Notice how the tray icon IS there.

OBSERVED RESULT
The first app you open on a different desktop doesn't have a tray icon, but the
ones opened after that do.

EXPECTED RESULT
All apps with a tray icon opened on a different desktop, regardless of the
order opened, should have a tray icon.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux, Kernel 5.13.13-arch1-1
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2

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

[krita] [Bug 442000] Search box in Resource Chooser does not have a save button, Enter key doesn't work either.

[Halla Rempt]

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

Halla Rempt  changed:

   What|Removed |Added

 CC||ha...@valdyas.org

--- Comment #1 from Halla Rempt  ---
Well, actually intentionally removed that functionality, I'm afraid.

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

[kwin] [Bug 424370] Closable window rule is not immediately applied to window decoration

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[kdevelop] [Bug 441893] Closing a project with no VCS crashes KDevelop

[Igor Kushnir]

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

Igor Kushnir  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED
  Latest Commit||https://invent.kde.org/kdev
   ||elop/kdevelop/commit/d4f79c
   ||14e61c15e0b47b476423217f4c7
   ||b4414dc

--- Comment #8 from Igor Kushnir  ---
Git commit d4f79c14e61c15e0b47b476423217f4c7b4414dc by Igor Kushnir.
Committed on 03/09/2021 at 17:42.
Pushed by igorkushnir into branch 'master'.

Git Support plugin: don't crash on projects with another or no VCS

This fix eliminates two crashes:
* when a project w/o VCS is closed;
* when a file in a subversion project is saved.
Related: bug 441807

M  +3-1plugins/git/repostatusmodel.cpp
M  +1-1plugins/git/repostatusmodel.h

https://invent.kde.org/kdevelop/kdevelop/commit/d4f79c14e61c15e0b47b476423217f4c7b4414dc

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

[kdevelop] [Bug 441807] KDevelop crashes upon saving file in subversion project

[Igor Kushnir]

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

Igor Kushnir  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/kdev
   ||elop/kdevelop/commit/d4f79c
   ||14e61c15e0b47b476423217f4c7
   ||b4414dc
 Status|REPORTED|RESOLVED

--- Comment #3 from Igor Kushnir  ---
Git commit d4f79c14e61c15e0b47b476423217f4c7b4414dc by Igor Kushnir.
Committed on 03/09/2021 at 17:42.
Pushed by igorkushnir into branch 'master'.

Git Support plugin: don't crash on projects with another or no VCS

This fix eliminates two crashes:
* when a project w/o VCS is closed;
* when a file in a subversion project is saved.
Related: bug 441893

M  +3-1plugins/git/repostatusmodel.cpp
M  +1-1plugins/git/repostatusmodel.h

https://invent.kde.org/kdevelop/kdevelop/commit/d4f79c14e61c15e0b47b476423217f4c7b4414dc

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

[krita] [Bug 442000] New: Search box in Resource Chooser does not have a save button, Enter key doesn't work either.

[Tyson Tan]

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

Bug ID: 442000
   Summary: Search box in Resource Chooser does not have a save
button, Enter key doesn't work either.
   Product: krita
   Version: 5.0.0-beta1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Resource Management
  Assignee: krita-bugs-n...@kde.org
  Reporter: tyson...@tysontan.com
  Target Milestone: ---

Krita 5.0's Search box in Resource Chooser does not have a save button, Enter
key doesn't work either.

The save button has been mentioned in the document, which worked in 4.0:
https://docs.krita.org/zh_CN/reference_manual/resource_management.html#filtering

Without it, we can't save search results into a tag.

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

[kmymoney] [Bug 416164] Assign Multiple VAT's to a Category

[Simone Gaiarin]

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

Simone Gaiarin  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 CC||simg...@gmail.com
 Ever confirmed|0   |1

--- Comment #1 from Simone Gaiarin  ---
I agree that assigning multiple vat to a category would be useful. Moreover VAT
is a bit restrictive. For example on my income, I may want to track different
components besides VAT, for example:

Gross income
  VAT 5%
  Pension fund 2 %

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

[kwin] [Bug 347153] Java app (Netbeans, Intellij IDEA...) window losing focus when switching to another desktop and back

[Sender]

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

Sender  changed:

   What|Removed |Added

 CC||sen...@xsmail.com

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